HP Systems Insight Manager - Manual (Page 187)

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
rocommunity6 public
Note: The community strings used should match those community strings on the CMS.
4. Verify that the system listens to connections on all interfaces. These settings are found in the
/etc/snmp/snmpd.conf
file. If not, stop the SNMP service, perform the below changes,
and restart the SNMP service.
# Listen for connections from the local system only
# agentAddress udp:127.0.0.1:161 //comment this entry if present
# Listen for connections on all interfaces (both IPv4 *and* IPv6) agentAddress
udp:161,udp6:[::1]:161 //add this entry if not present
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.
To solve this issue:
1.
Stop the SNMP daemon.
2. Add the following line to the /etc/snmp/snmpd.conf file:
rocommunity public
3. Restart SNMP.
Enclosure table view page
iLO's do not appear in the enclosure table view page. However, to access the iLO from this view,
click the status icon in the MP column of the associated server.
Event
When you subscribe for WBEM events from either the command line (mxwbemsub) or the GUI
(Options
→Events→Subscribe to WBEM Events), you might receive the error message String
index out of range .
Solution: Verify if the name of the local host resolves to a fully qualified name through DNS. The
command needs the FQDN name to work properly.
-------------------------------------------------------------
To enable non-administrative users to delete or clear events, you can create a toolbox with the
Clear Events and Delete Events tools.
Enclosure table view page 187