CMS not trusted

[Richard Ward_5]

Hi All,

I'm fairly new to the whole Insight Manager system, and I'm having a re-occuring problem.

I've followed the instructions as per the manual and have got the system installed, but keep getting the same problem.
Which is when I attempt to create/deploy the initial support pack (Deploy->Deploy Drivers...->Initial Proliant Support...), I get to step 3 and my CMS is showing as not trusted!
How do I go about changing this, I'm obviously missing something very simple but for the life of me I haven't been able to find what!!

Any help greatly appreciated!

Richard

[Christian Mentschik]

hi,
a simple way is to make a trust with certificates from the SIM. you go to the web agents (http://hostname:2301), then to settings, http server, options, then Trusted Certificates. check the box Secure Trust Modes: Trust By Certificate. then go to the Trusted Certificates List, type the name of SIM server an push the GET CERT button. after this you will have a trust between the server and the SIM.

hope this help

best regards christian

[Richard Ward_5]

Hi Christian,

Thanks for that. I'm having the problem on the CMS itself.

I've followed the instructions that you gave, it all went as you described, but the computer still shows as untrusted.

Richard

[Christian Mentschik]

yes, but the SIM server is also a managed server and so it need the same (also a certificat). the trust is only possible with certificates.

christian

[Joel Rubenstein]

After you setup the trust relationships you should go to Options--> Status Polling --> Software Status Polling and run a software status poll. By default this task is only run once a week.

[Richard Ward_5]

Hi Joel/Christian

I've gone into the Status polling menu and performed the poll, but still no change.

However, when I selected the CMS as the target machine, under the Type it is listed as unmanaged. Is this ok??

[Joel Rubenstein · Accepted solution]

If you go to the CMS System Page it will indicate the protocols detected during discovery / Identification. If SNMP is not listed then SIM will be unable to determine the system type. The possible reasons of this include 1. a mismatch between the SNMP configuration in SIM and in the Windows SNMP agent. 2. If the CMS is a Windows 2003 server then check the SNMP Service properties security and either set "accept packets from any host" or if "accept packs from these hosts" insure that localhost is listed. If you make any changes to the SNMP configuration the SNMP service must be restarted.

To rerun the Identification task Options--> Discovery--> Identify Systems

[Richard Ward_5]

Ahaa!
Yes that's got the problem sorted out, thanks very much!

I'll probably be back soon though with my next problem though!

Thanks again,

Richard

[KEITH LUKEN_1]

I also found that if you trust by Name the VC Agent lieks to have the fully qualifed name, not just the short name.