HP Systems Insight Manager

Product information

• You must be able to ping the device from the server where HP Systems Insight Manager is running. 
• Community strings must match - make sure HP Systems Insight Manager & managed systems are using the same one. Note that community strings are case sensitive. 
• Under Microsoft Windows NT and Windows 2000, one community name on the device must be set to READ CREATE. Note that you do not have to use this to the community string in HP Systems Insight Manager (a community string set to READ is all that is required.) The Management Agents connect to themselves using SNMP and require one string set to READ CREATE. 
• The HP Systems Insight Manager system must be allowed to make SNMP requests to the device - make sure the SNMP security settings aren't preventing this. Under Microsoft Windows NT and Windows 2000, either the "Allow SNMP packets from any host" must be selected or the address of the Insight Manager 7 server must be in the list of allowed hosts. 
• If you are using IP-specific security (as in the second part of d above) localhost (127.0.0.1) must also be allowed to make SNMP requests to the host. The Management Agents connect to themselves using SNMP and thus need to be able to get in. 
• The Management Agents must be installed and running properly on the servers you are trying to manage. For Windows systems, check the Event Log to make absolutely sure they are running (you should see a few 'Agents started' messages and no errors.) 
• Routers/Switches in the network must pass SNMP traffic on ports 161/162 and 7.

mxconfigrepo –a 

The platform where the CMS is installed needs SSH to be installed and running for HP SIM to operate. For managed systems, SSH or OpenSSH is only required when a task is run which actually makes changes on the managed system. This could include tools from the Tool menu including CLI options, or where changes are made to multiple systems. SSH is not required on managed systems for basic discovery, inventory or identification.

HP SIM 4.0 does not support this configuration. Both applications use the same or similar ports so conflicts would occur.

The device association code in HP SIM relies heavily on properly configured SNMP agents on the servers and some data from the iLO itself. The DNS and SNMP names are listed to help users find systems in the list and for display purposes. These names will not display if SNMP is not configured, the community name is not entered, or there is a community name mismatch. Summary – this problem has typically been caused by a miss-configured DNS server or missing entries in the DNS server.  

1. For DNS names, the DNS server used on your network must allow reverse lookups. The systems to be managed must have registered themselves with the DNS server. Correct registration for a specific system can be checked by following these steps:
   A) Open a command prompt and run nslookup <ip> using the IP of the target system. The response should return both a name and an IP.
   B) Run ping against the name returned from the nslookup. An IP address will be resolved and then the ping will be run against it.
   C) Compare the IP address that appears when running the ping – is this IP the same as the one used when you ran nslookup in step A?
   If the IP addresses are different - then HP SIM will only show the original IP address in the System Lists and not the friendly name. The IP mismatch indicates that the DNS server configuration may be at fault. 
   
   
2. Another method to renew DNS registration is to (from the system itself) use the ipconfig command. At a command prompt, type:
   ipconfig /registerdns
   Or, type ipconfig /registerdns [adapter]
   
   Where adapter is the name of a specific network adapter installed on the computer for which you want to renew or update registrations.
   
   The ipconfig /registerdns command provides you with a means to manually initiate dynamic registration for the DNS names and IP addresses configured at a computer. This option can assist in troubleshooting a failed DNS name registration or in resolving a dynamic update problem between a client and the DNS server without requiring a client reboot. You can go to the Microsoft website at http://microsoft.com and search on "DNS registration" for further information. 
   
   
3. The last solution is to add the IP address and name to the HOSTS file on your CMS platform. 

1. HP SIM user detects a problem with a device or a group of devices
2. User selects “Repair Agent settings” tool from the HP SIM menu which presents the task wizard UI asking:
   1. Administrative credentials for the device(s) such as administrator user name and password as well as domain name.
   2. Whether to repair SNMP settings such as the Read community string and setting the trap destination to the CMS.
   3. Whether to repair the trust relationship by setting it to trust by certificate and installing the certificate for the CMS.
   4. Whether to repair the administrator password for legacy agents
3. The local CMS-side tool connects natively using Windows remote management APIs to the device, copies over the Repair Agent Settings repair tool and data file (containing HP SIM community strings, trust relationship data, etc), starts up a remote launcher service causing the repair tool to run.
4. The repair tool runs on the device and attempts to update all the settings. It generates a file containing results.
5. The local CMS-side tool scans target devices for existence of result files, read them, and sends the contents to standard output to be included as the task output. Once a particular target’s results file is retrieved, the tool remotely removes the target service and all of its files.

• You upgraded from HP SIM 5.0 SP3 to SP4,
• AND... you had not installed HP SIM in the default directory (i.e. c:\program files\....)