20 troubleshooting snmp problems – HP Insight Control Software for Linux User Manual
Page 250
Figure 23-2 PXE configuration files
6.
PXE boot the managed server as described in
7.
Monitor the HP Insight Control user interface and the server's remote console and verify
that the server has been successfully rediscovered and associated with its management
processor.
8.
If the server does not have a valid OS installed on it, power off the server when it has
completed its discovery.
9.
If the server does have an OS installed, immediately install the ProLiant Support Pack (see
the HP Insight Control for Linux Support Matrix for the current supported version), either
manually through the remote console or by selecting the following:
Deploy
→Deploy Drivers, Firmware, and Agents→Install ProLiant Support Pack (PSP)...
When this procedure is complete, the server is present in HP SIM and the association with the
management processor is restored.
23.20 Troubleshooting SNMP problems
NOTE:
This section applies only to systems with iLO-based management processors.
HP SIM requires that a managed system is running the agents listed in
so
that it can make and maintain the management processor to server association. To verify that
SNMP is configured properly on a managed system, follow these steps:
1.
Verify that the agents listed in
are running on the managed system:
# /bin/ps
2.
On the CMS, run the snmpwalk command to verify that SNMP is configured correctly. If
the snmpwalk command fails, SNMP is not configured properly. In the following example,
pluto.example.com
is a managed system.
# snmpwalk -Os -c public -v 1 pluto.example.com system
sysDescr.0 = STRING: Linux pluto.example.com 2.6.9-67.ELsmp
#1 SMP Wed Nov 7 13:58:04 EST 2007 i686
sysObjectID.0 = OID: netSnmpAgentOIDs.10
250
Troubleshooting