Users Guide

98 Managing and Recovering a Remote System
Troubleshooting Alerting Problems
You can use logged SNMP trap information to troubleshoot a particular type
of DRAC 4 alert. SNMP trap deliveries are logged in the Trace Log by default.
However, since SNMP does not confirm delivery of traps, it is best to trace the
packets on the managed system using a network analyzer or a tool such as
Microsoft’s snmputil.
DRAC 4 Log Messages
DRAC 4 Log messages can be used by administrators to debug alerting from
the DRAC 4. Table 4-31 provides a list of the DRAC 4 log message ID
numbers, messages, and suggested actions to take.
NOTE: In Table 4-31, the character "L" is sometimes displayed in the Message ID
column. "L" represents the severity level or type of the message, which can be one
of the following: W (warning), E (error), S (severe), F (fatal), or A (always).
0x5041 EHOSTUNREACH: The destination host could not be reached.
0x5046 ENIDOWN: NI_INIT returned -1.
0x5047 ENMTU: The MTU is invalid.
0x5048 ENHWL: The hardware length is invalid.
0x5049 ENNOFIND: The route specified cannot be found.
0x504A ECOLL: Collision in select call; these conditions already selected by
another task.
0x504B ETID: The task ID is invalid.
Table 4-30. DRAC 4 Network Error Codes
(continued)
Error Code Description