Users Guide

96 Managing and Recovering a Remote System
The Diagnostic Console page provides buttons (see Table 4-29) in the
top-right corner of the screen.
Troubleshooting Network Problems
The internal DRAC 4 Trace Log can be used by administrators to debug
alerting, or networking from the DRAC 4. The Trace Log can be accessed
from the DRAC 4 Web-based interface by clicking the Diagnostics tab, and
typing the gettracelog command. The Trace Log will appear and tracks the
following information:
• DHCP — Traces packets sent to and received from a DHCP server.
• IP — Traces IP packets sent and received.
NOTE: In the DRAC 4 Trace Log, nonprintable ASCII characters are translated to
printable ASCII characters. If the character code is less than 0x20, or between 0x7f
and 0xa0 (inclusive), the value 0x40 is exclusive and the character before printing,
after a "^" is added to the beginning. As a result, the ASCII carriage return
character, 0xd, is printed as "^M" in the Trace Log.
NOTE: The DRAC 4 will not echo an ICMP (ping) with a packet size larger than
1500 bytes.
The trace log may also contain DRAC 4 firmware-specific error codes (relating
to the internal DRAC 4 firmware, not the managed system’s operating system).
Use Table 4-30 to help diagnose network problems reported by the internal
DRAC 4 operating system.
Table 4-29. Diagnostic Console Page Buttons (Top Right)
Button Action
Refresh Reloads the Diagnostic Console page.
Table 4-30. DRAC 4 Network Error Codes
Error Code Description
0x5006 ENXIO: No such address.
0x5009 EBADS: The socket descriptor is invalid.
0x500D EACCESS: Permission denied.
0x5011 EEXIST: Duplicate entry exists.