VCA trust relationship problem.

[David cheng_3]

I have this problem with about 50 servers with my domain. How would I fix it in one shot ?
Do I have to go to each targeted server to reset the SNMP setting ??

thanks

[Michael Tsang_1]

Yes, I have got the same problem. No matter I have follow the instruction from the HP site and change every settings. The trust still can't establish.

[David cheng_3]

I setup the CMS's global SNMP to trust all and install OpenSSH. Nevertheless, they still having the trust relationship...HMmm

[NJK-Work]

Hi David,

I had this same problem when I first upgraded to version 4.1 from IM 7.2. But, after a while it just started working.

However, to try to provide some useful information for you, you might want to try the following:

1) Make sure the trust relationship with the server itself is working. For example, can you connect to the System Management Page of a remote server from SIM 4.2 console without being prompted to login? If you can, you know you have a valid trust relatioship between the managed server and SIM 4.2 console.

2) If the above is not working, try to get that problem fixed first before trying to get the VCRM working (I believe the two are related, so once you get this working you should be able to get the other working). Make sure you have imported the certificate from the SIM server into the management agents of the remote server (assuming you are using certificate based trusts).

3) Once you get the above working, try pushing out a VC agent configuration to the remote servers using "Configure..." then "Replicate Agent Settings" from the menu in SIM 4.2. As a source, select a server that IS working to replicate the VC Agent settings from to the servers that are not working.

Let me know how far you get with this and we can go from there.

PS - I dont use SSH (I could never get it to install on remote machines) so I dont think you need SSH to get any of the VCRM stuff working (since I works fine for me without SSH).

Nelson

[Michael Ranson]

Nice work, Replicating the agent settings fixed some of my issues too :)