Trust issues even though i've tried trust all...

[Magnus Appelgren]

Hi

I'm having a hard time getting the software status in my sim. I have tried everything i can think about and read lots of threads here. Nothing works. Still says "Security Trust Issue" on all my proliant servers except the sim which is also the vcrm. If i browse to a servers vcagent i can manually install from the repository which is good but still no stauts in cim...

Any idea would be appreciated!

Magnus Appelgren

[Scott Shaffer]

Have you tried running the 'Configure or Repair Agents' tool against one of the servers? This tool will fully configure the server for management including SNMP and trust relationships (which are required for Version Control to work.)

Once this is done, you might have to manualy execute the Software Status Polling task against this server as well.

Oh, I assume you're running HPSIM 4.2 SP2 but if not, please update to this version - there are a number of enhancements that make this the easiest version to use.

[Steven A. Becker]

I have had the same issues as Magnus. I updated to SP2 and tried the configure and Repair tool and Software Polling Status tool, but to no avail.

Any other ideas would be greatly appreciated.

Thanks,

Steve

[FrankW]

By any chance, does the managed server have more than one IP address? I'm having these trust issues in SIM but the vcagent on the managed servers is working just fine (manually). I noticed though that I cannot reach the system management homepage with the FQDN server name, but if I pick one of the other 3 IP addresses assigned to that machine then it works fine! I have no options set in the IP Binding (security), but obviously the homepage is not binding to all available addresses.

[Brent Seizer]

I would recheck the SNMP settings.
On the managed servers, ensure that the CMS server is listed as a host to accept SNMP from, as well as local host.
On the CMS ensure that the server is accepting from any host.
On both machines, ensure that their is a read community name that both servers agree on the name.
On both machines, ensure that their is a read/write community name that both servers agree on the name.

Good luck.

[FrankW]

It has been my experience that SNMP is configured correctly here, and that it also worked just fine before the new version of SHM came along. Also, doing a "repair" has absolutely no effect. The original problem as stated by Magnos still remains.

I'ld also like to point out that I have the same scenario as Magnus, and that "localhst:2381/vcagent" operations work just fine.

[Sakti Chakravarty]

I think your problem lies with incorrectly configured HP Support Pack components.

Using the RDU, you can deploy just these components to a system (I found this was sufficient to get systems talking to the CMS, but no reboot was required):

(1) HP System Management Homepage
(2) Version Control Agent
(3) HP Insight Management Agents

You need to ensure these components are properly configured before deploying them to your systems. (1) contains information about the Trust method and CMS certificate (if required), so if you get this part right, your Trust issue should disappear.