HP Systems Insight Manager 6.3 User Guide

Solution: If you want Systems Insight Manager to display the same name as the host name of the
full DNS name, you must use the modify command to modify it.
-------------------------------------------------------------
If an iLO or Onboard Administrator was discovered prior to enabling/configuring Single Sign-on
(SSO), re-identification is required for SSO communication to work between Systems Insight
Manager and the iLO/OA.
-------------------------------------------------------------
If an Onboard Administrator is discovered with Discover systems in an enclosure when Onboard
Administrator is discovered option enabled, then the percentage completion of the discovery task
in which the Onboard Administrator IP address is part of, fluctuates. Initially, the percentage
completion is higher, but as the discovery of iLOs are triggered, the overall percentage completion
comes down. As the iLO discovery completes, the percentage completion moves higher and finally
becomes 100% and task status becomes complete.
-------------------------------------------------------------
Some systems, such as Cisco Fibre Channel switches, that support both SNMP and SMI-S protocols
can appear as two separate systems within Systems Insight Manager.
-------------------------------------------------------------
Systems Insight Manager currently does not support an association of management processor to
server if the system is based on PA-RISC because a management processor is only supported on
HP Integrity systems. This will not be supported until a new release of firmware for the PA-RISC
systems.
-------------------------------------------------------------
If the partition has a vPar already created and been discovered by Systems Insight Manager but
the IP address used by the vPar has been moved to a stand-alone server, Systems Insight Manager
will not delete the association to the complex or the management processor; the reason is the
partition still has vPar defined within the partition.
Linux servers
When a Linux server is discovered as an unmanaged system:
1. Be sure to make the changes similar to the following in the /etc/hosts file on the discovered
system before installing agents:
#Do not remove the following line, or various programs
#that require network functionality will fail.
127.0.0.1 localhost
172.24.30.34 HPSIM.wbemqa.com HPSIM
Note: Replace the IP address, host name, and alias previously listed with your localhost IP
address, DNS name, and host name.
2. Install agents.
3. Verify that the following lines are entered in the /etc/snmp/snmpd.conf file. If not, stop
the SNMP service, enter them manually, and restart the SNMP service.
rwcommunity private
rocommunity public
Note: The community strings used should match those community strings on the CMS.
After completing these steps, the system is discovered properly.
-------------------------------------------------------------
To discover detailed information for Linux running on ProLiant systems, you can do one of the
following:
• Install the Linux ProLiant agents on the system.
• Update the snmpd.conf file. If you choose this option and do not update the snmpd.conf
file, LINUX appears in the Operating system name column on the system table view page,
instead of the true operating system name, such as Red Hat Advanced Server.
158 Troubleshooting