Version Control Agent Trust Relationship Problem

[Richard Layton]

Anyone know how to fix a Version Control Agent Trust Relationship Problem? I can login directly to it but I can't access from Insight manager itself.

Thanks

[Ed Cox]

The next time you login directly...go to the System's Homepage and choose Settings from the top tab. Then Options from the bottom. Then click the link for Trusted Server Certificates List and check to see if the SIM server is listed. If not... add it.
Also...
This may not be an issue with your network, but I have seen in the past that if your target server and the SIM server don't agree on the proper time and date, then you can't establish trust.
Ed

[Richard Layton]

I have that setting set to trust all. Also that only effects the agents web server, it does nothing for the version control agent.

Thanks for the reply!

[Ed Cox]

The VCA has no trust on it's own...it works through the general trust the server has with the SIM server. The only two things the VCA has to know are:
A. Machine name of the VCR
B. Web agent password of the Administrator account that resides on the VCR.

[Roman Lazarev]

Richard, have you figured out what the problem is? I'm haveing the same issue. Can you please leat me know how you resolved it i'm at a304489@fmr.com Thank you!

[Jon Ward]

Is it that there is not a link in hp Systems Insight Manager or that it errors out. If it errors out, what is the error?

SNMP must be installed and it's security set to either Accept SNMP Packets From Any Host or Accept SNMP Packets From These Hosts and localhost and the Insight Manager address specified in the hosts list.

[Rob Buxton]

What are you seeing from the HPSIM Screen?
Hover over the icon and you should just get text.
Note if you've fixed things up, e.g. SNMP, Trust Certificates, the Software Status Polling task may need to run to update the status flag on the IM Server. Until that is done you still see the I Icon. Try running this process once you've made the changes.

[Richard Layton]

I see a blue upside down question mark, or a "i" I cant tell which it is. I have connected directly to the host and connect to the vc from there and I get no errors. But if done through the SIM it gives me this error.

"NOTICE: The Version Control Agent (VCA) has not been detected on the target system. On a Windows system, the easiest way to install and configure the VCA and associated agents is to create an Install ProLiant Support Pack task. The Version Control Agent cannot be installed on HP-UX systems.

If the VCA is already installed on the target system, then run Automatic Discovery or Identification so that the agents are added to the database."

[Ed Cox]

Richard,
Have you gone to the Logs pull down menu > View All Scheduled Tasks? Under there you will see at the bottom of the tasks, one called Software Version Status polling. This will force SIM to go out and poll the VCAs and update that SW column you mentioned earlier.
This specific task runs when it sees a new system or every 7 days.
Ed

[Richard Layton]

I ran that and the same devices show the problem.

[Ed Cox]

Hover your mouse over one of the question marks in the SW column... what does it say?
As for the error message...it states in part:

If the VCA is already installed on the target system, then run Automatic Discovery or Identification so that the agents are added to the database."

Try running "Daily Device Identification" from the Logs>All Scheduled Tasks area.
Ed

[Richard Layton]

It says VC agent not found

[Ed Cox]

Gotcha...
And does it still show that after you ran the Daily Device Identification task?

[Richard Layton]

yes, even after I run that

[Ed Cox]

Hmmmm...
On one of the servers that still show the i under the SW column...click on the i and where does it take you?

[Jon Ward]

Try changing the trust mode to by certificate or by name and see if it works with those.

[Richard Layton]

When I click on the i I get this message

"NOTICE: The Version Control Agent (VCA) has not been detected on the target system. On a Windows system, the easiest way to install and configure the VCA and associated agents is to create an Install ProLiant Support Pack task. The Version Control Agent cannot be installed on HP-UX systems.

If the VCA is already installed on the target system, then run Automatic Discovery or Identification so that the agents are added to the database."

[Jon Ward]

Is the HP Version Control Agent running as a service in the Services Applet?

If it is already present and started, try restarting it to see if the service is responsive.

[Diego Viganò]

Hi, i had the same problem of "Trust Failed" with VCA from SIM. I fixed it running "software status polling" from "options" - "status polling".
Bye,
DV

[Sabina Elizabeth Patton]

We see the same thing on many of our servers. We either have a trust message the "i" or the "?"

I have tried all of the things stated in the threads above.

One thing I wonder is if it doesn't deal well with polling over a WAN circuit.

[James D. Young]

I have had this problem and at was able to get it fixed after lots of playing around with it.

If you have a system that works already, then set your SNMP to accept from all, and set your HTTP Server Options in the local to accept Trust All. Then replicate the settings from the working server.

If none of them work I would set your SNMP to either all or I lock mine down to 127.0.0.1, localhost, and the name or ip of the HPSIM Server.

For HTTP Server Options I use the following.
Local Access and Adminitrator. Trust by Certificate, enter the certificate created from within HPSIM in the Insight Manager 7 Certificate Data section.

Once I made sure all these were working on one, then opened up the others and replicated it to them.

I have about 100 servers that are HP/Compaq. So far I have had little problem since I got this all working.

[Martijn Dessing]

Same problem,
HP dl380, G3, G4 G5
Support Pack 7.70
HP SIM 5.1 SP1
Have only 1 of 30 registered servers that can be connected to Version Control Agent through SIM homepage.
Tried everything and all of the above, imported new certs etc. changed trust method. Can't find the difference with other servers.

Anyone has a methodical view for troubleshooting this typical problem?

[mark q]

I get the same thing too, I have two identical servers, one works one doesn't, both are set exactly the same, same vcagent, all services are running,

sim sees one and doesn't see the other, and when I launch it the same way on both, one works the other doesn't

I ran identify against both, the one that's not working says there's no smh and the one that does says there is.

but I can go https://servername:2381 on both and they work fine...???

any ideas this is really annoying.

[Carlsberg]

Hi ,
These are the steps I normally go through if things doen't work as they should with SMH and VCA.
Verify SNMP settings.
Check local firewall is not blocking SNMP or 2301 and 2381 ports.
Login to SMH
Set trust mode to trust by cert.
Either import or manually copy the cert file to c:\hp\smh\certs.
Restart SMH if you do a manual copy.
Login to SMH - > VCA -> Change agent settings.
Type the VCRM server name and user credentials.
It will prompt you to choose for the reference pack if everything is ok.

Hope this helps.

[jfh777]

I had this issue also. Here are the issues I faced and the steps I took to solve it. Thanks to all who posted before me.

I had the white circled "i" as the SW status on my target server. It indicated "Version Control Agent Trust Relationship Problem". I connected to that server's Systems Management Homepage (from the link in SIM), and the cert I needed installed automatically.

At that point the Version Control status was unknown. I changed the VC Agent settings to point to my software repository server. I closed out and returned to SIM. I then went to Options, Status Polling, Software Status Polling, and polled my target.

Once it completed, I then had a yellow triangle with an exclamation mark. That's fine though - it is caused by not specifying a control version in my agent setup on that server.

So then I chose Options, Identify Systems and ran that against my target. From there, the report stated "The system did not respond to SNMP, verify security settings and community strings."

On the server, I went into Add/Remove Programs and added SNMP. From there, went into "Manage My Computer", Services... double-clicked the SNMP service and edited its community properties to match my SIM server.

At this point I can install via SIM. Hope this is helpful to someone else!

Regards,
Justin