How do I properly identify a server in SIM 5.0

[RobSmith]

Could someone lay our a sure-fire way to get a server correctly identified in SIM, ie, system type, os, all that happy junk.

I'm looking for a more or less no-fail method to apply to my entire environment in one go. I have far too many servers to be fiddling with each one individually.

Thanks for your assistance.

--Rob

[David Claypool]

If it's a ProLiant server running Windows and has the ProLiant Support Pack properly installed, then 'Configure or Repair agents...' will correct all of the communications settings and trusts for HP SIM to get all of the information it needs to identify the system.

[RobSmith]

What about for VM's in the environment. My success rate for ID'ing these is around 50%.

What I have done so far, as a universal answer is:

1. Install System Homepage and VC Agent, (and SIM Agent if its a physical machine instead of VM)
2. Install openSSH
3. Configure and Repair Agents

I feel like somethings still missing, as my identification is still a bit off.

[David Claypool · Accepted solution]

There is a step by step guide to configuring VMs for recognition in 'Deploying a VMware Virtual Infrastructure with HP ProLiant servers, storage, and management' available from http://www.hp.com/solutions/vmware

[Ferry Steenvoorde]

What always works:

-if you are using certificates, export on the HPSIM server the "HPSIM server certificate" (Options, Security, Certificates, Server Certificate, Export). The file that is saved is a plain ASCII-file.

-verify on the Managed System if the name of the HPSIM-server can be resolved (local HOSTS-file, DNS, whatever)

-verify on the HPSIM-server that both the servername of the Managed System, and the name of the ILO-board can be resolved.

-configure on the Managed System the local SNMP-service. Traps are sent to the IP-address of the HPSIM-server, community's are the same as used on the HPSIM-server (case sensitive), SNMP-security allows one community with READ WRITE access.

-if there is a firewall between the HPSIM-server and the Managed System, verify with TELNET if the following ports are open:
--ICMP (ping, HPSIM --> Managed System)
--161 (snmp, HPSIM --> Managed System)
--162 (snmp trap, Managed System --> HPSIM))
--280 (status update, HPSIM <--> Managed System)
--2301 (http, HPSIM <--> Managed System)
--2381 (https, HPSIM <--> Managed System)
Syntax on Command Prompt: telnet

-install the latest Support Pack on the Managed System.
IMPORTANT: first configure the items in "All Configurable Components!!
--Configure the "HP System Management Homepage". "Local Access" for Administrators is quite nice.
Import the HPSIM server certificate if required.
--Add the HPSIM-servername and login credentials for Version Control Manager
--For "HP Insight Management Agents", enable the SNMP-sets
--After installation, reboot the managed system.

-Verify on the HPSIM-server that:
--the IP-address of the managed server is in the discovery range
--the IP-address of the ILO-board of the managed system is in the discovery ranges.

-did you install the latest MIB Upgrade Pack on the HPSIM-server? You can download it from the driver download page for any type of Proliant server.

-Start Automatic Discovery on the HPSIM-server.

If all of the requirements above are met, you should have your servers recognised.


Sometimes, HPSIM is a bit messing around with systems that have previously been Discovered as "Unknown". In that case, delete the system from HPSIM and __REBOOT_THE_HPSIM_SERVER__. After that, the system will be rediscovered correctly.

All of the settings above can be set during an unattended setup of a server. For existing systems, you might look for deployment tools like Altiris or the HP implementation of it.

[RobSmith]

Its looking like the issue with the VM's was caused by the WMI login.
They seem to be ID'ing ok now. I also ran the MIB update, no harm in doing that at any rate. Thank you all, especially for the end to end, no-fail ID technique.

[RobSmith]

Thanks again!