This section explains how to perform tasks related to recovering and troubleshooting a crashed DRAC 5.
You can use one of the following tools to troubleshoot your DRAC 5:
RAC Log
Diagnostic Console
Trace Log
racdump
coredump
Using the RAC Log
The RAC Log is a persistent log maintained in the DRAC 5 firmware. The log contains a list of user actions (such as log in, log out, and security policy changes) and alerts issued by the DRAC 5. The oldest entries are overwritten when the log becomes full.
To access the RAC Log from the DRAC 5 user interface (UI):
In the System tree, click Remote Access.
Click the Logs tab and then click RAC Log.
The RAC Log provides the information listed in Table 16-1.
Table 16-1. RAC Log Page Information
Field
Description
Date/ Time
The date and time (for example, Dec 19 16:55:47).
When the DRAC 5 initially starts and is unable to communicate with the managed system, the time will be displayed as System Boot.
Source
The interface that caused the event.
Description
A brief description of the event and the user name that logged into the DRAC 5.
Using the RAC Log Page Buttons
The RAC Log page provides the buttons listed in Table 16-2.
Table 16-2. RAC Log Buttons
Button
Action
Print
Prints the RAC Log page.
Clear Log
Clears the RAC Log entries.
NOTE: The Clear Log button only appears if you have Clear Logs
permission.
Save As
Opens a pop-up window that enables you to save the RAC Log to a directory of your choice.
NOTE: If you are using Internet Explorer and encounter a problem
when saving, be sure to download the Cumulative Security Update
for Internet Explorer, located on the Microsoft Support website at
support.microsoft.com.
Refresh
Reloads the RAC Log page.
Using the Command Line
Use the getraclog command to view the RAC log entries.
racadm getraclog -i
The getraclog -i command displays the number of entries in the DRAC 5 log.
You can use the clrraclog command to clear all entries from the RAC log.
racadm clrraclog
Using the Diagnostic Console
The DRAC 5 provides a standard set of network diagnostic tools (see Table 16-3) that are similar to the tools included with Microsoft® Windows® or Linux-based systems. Using the DRAC 5 Web-based interface, you can access the network debugging tools.
To access the Diagnostic Console page:
In the System tree, click Remote Access.
Click the Diagnostics tab.
Table 16-3 describes the options that are available on the Diagnostic Console page. Type a command and click Submit. The debugging results appear in the Diagnostic Console page.
To refresh the Diagnostic Console page, click Refresh. To execute another command, click Go Back to Diagnostics Page.
Table 16-3. Diagnostic Commands
Command
Description
arp
Displays the contents of the Address Resolution Protocol (ARP) table. ARP entries may not be added or deleted.
ifconfig
Displays the contents of the network interface table.
netstat
Prints the content of the routing table. If the optional interface number is provided in the text field to the right of the netstat option, then netstat prints additional information regarding the traffic across the interface, buffer usage, and other network interface information.
ping <IP Address>
Verifies that the destination IP address is reachable from the DRAC 5 with the current routing-table contents. A destination IP address must be entered in the field to the right of this option. An Internet control message protocol (ICMP) echo packet is sent to the destination IP address based on the current routing-table contents.
gettracelog
Displays the DRAC 5 trace log. See "gettracelog" for more information.
Using the Trace Log
The internal DRAC 5 Trace Log is used by administrators to debug DRAC 5 alerting and networking issues.
To access the Trace Log from the DRAC 5 Web-based interface:
In the System tree, click Remote Access.
Click the Diagnostics tab.
Type the gettracelog command, or the racadm gettracelog command in
the Command field.
NOTE: You can use this command from the command line interface also. See
"gettracelog" for more information.
The Trace Log tracks the following information:
DHCP — Traces packets sent to and received from a DHCP server.
IP — Traces IP packets sent and received.
The trace log may also contain DRAC 5 firmware-specific error codes that are related to the internal DRAC 5 firmware, not the managed system's operating system.
NOTE: The DRAC 5 will not echo an ICMP (ping) with a packet size larger than
1500 bytes.
Using the racdump
The racadm racdump command provides a single command to get dump, status, and general DRAC 5 board information.
NOTE: This command is available only on Telnet and SSH interfaces. For more
inform, see the "racdump" command.
Using the coredump
The racadm coredump command displays detailed information related to any recent critical issues that have occurred with the RAC. The coredump information can be used to diagnose these critical issues.
If available, the coredump information is persistent across RAC power cycles and will remain available until either of the following conditions occur:
The coredump information is cleared using the coredumpdelete subcommand.
Another critical condition occurs on the RAC. In this case, the coredump information will be relative to the last critical error that occurred.
The racadm coredumpdelete command can be used to clear any currently resident coredump data stored in the RAC.
