Dell Drac 5 User Guide

							Recovering and Troubleshooting the Managed System281
Baseboard Management Controller
Table 16-6 describes the Baseboard Management Controller properties.
Using the System Event Log (SEL)
The SEL Log page displays system-critical events that occur on the managed 
system. 
To view the System Event Log:
1
In the System tree, click System.
2Click the Logs tab and then click System Event Log.
The 
System Event Log page displays the event severity and provides other 
information as shown in Table 16-7.
3Click the appropriate System Event Log page button to continue 
(see Table 16-8).
Table 16-6. BMC Information Fields
Field Description
NameBaseboard Management Controller.
IPMI VersionIntelligent Platform Management Interface (IPMI) version.
Number of Possible 
Active SessionsMaximum number of session that can be active at the 
same time.
Number of Current 
Active SessionsTotal number of current active sessions.
Firmware VersionVe r s i o n  o f  t h e  B M C  f i r m w a r e .
LAN EnabledLAN Enabled or LAN Disabled.
Table 16-7. Status Indicator Icons
Icon/Category Description
A green check mark indicates a healthy (normal) status condition.
A yellow triangle containing an exclamation point indicates a 
warning (noncritical) status condition.
A red X indicates a critical (failure) status condition. 
						

							282Recovering and Troubleshooting the Managed System
Using the Command Line to View System Log
racadm getsel -i
The getsel -i command displays the number of entries in the SEL.
racadm getsel 
 NOTE: If no arguments are specified, the entire log is displayed.
 
NOTE: See getsel on page 323 for more information on the options you can use.
The clrsel command removes all existing records from the SEL.
racadm clrsel
A question mark icon indicates that the status is unknown.
Date/TimeThe date and time that the event occurred. If the date is blank, then 
the event occurred at System Boot. The format is mm/dd/yyyy 
hh:mm:ss, based on a 24-hour clock.
DescriptionA brief description of the event
Table 16-8. SEL Page Buttons
Button Action
PrintPrints the SEL in the sort order that it appears in the window. 
Clear LogClears the SEL.
NOTE: The Clear Log button appears only if you have Clear Logs 
permission.
Save As Opens a pop-up window that enables you to save the SEL 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.
RefreshReloads the SEL page.  Table 16-7. Status Indicator Icons 
(continued)
Icon/Category Description 
						

							Recovering and Troubleshooting the Managed System283
Using the POST and Operating System Boot 
Capture Logs
This feature of the DRAC 5 allows you to play back a stop motion video of 
the last three instances of the BIOS POST and operating system boot.
To view the POST and operating system Boot Capture logs:
1
In the System tree, click System.
2Click the Logs tab and then click Boot Capture tab.
3Select the log number of the POST or operating system Boot Capture log.
The video of the logs is played on a new screen.
4Click Stop to stop the video.
Viewing the Last System Crash Screen
 CAUTION: The last crash screen feature requires the managed system with the 
Auto Recovery feature configured in Server Administrator. In addition, ensure that 
the Automated System Recovery feature is enabled using the DRAC. Navigate to 
the Services page under the Configuration tab in the Remote Access section to 
enable this feature.
The Last Crash Screen page displays the most recent crash screen, which 
includes information about the events that occurred before the system crash. 
The last system crash information is saved in DRAC 5 memory and is 
remotely accessible. 
To view the Last Crash Screen page:
1
In the System tree, click System.
2Click the Logs tab and then click Last Crash. 
						

							284Recovering and Troubleshooting the Managed System
The Last Crash Screen page provides the following buttons (see Table 16-9) 
in the top-right corner of the screen:
 NOTE: Due to fluctuations in the Auto Recovery timer, the Last Crash Screen may 
not be captured when the System Reset Timer is set to a value less than 30 
seconds. Use Server Administrator or IT Assistant to set the System Reset Timer to 
at least 30 seconds and ensure that the Last Crash Screen functions properly. See 
Configuring the Managed System to Capture the Last Crash Screen on page 257 
for additional information.  Table 16-9. Last Crash Screen Page Buttons
Button Action
PrintPrints the Last Crash Screen page.
SaveOpens a pop-up window that enables you to save the Last 
Crash Screen to a directory of your choice.
DeleteDeletes the Last Crash Screen page.
RefreshReloads the Last Crash Screen page. 
						

							Recovering and Troubleshooting the DRAC 5285
17
Recovering and Troubleshooting 
the DRAC 5
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 L og 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):
1
In the System tree, click Remote Access.
2Click the Logs tab and then click RAC Log.
The RAC L og provides the information listed in Table 17-1. 
						

							286Recovering and Troubleshooting the DRAC 5
Using the RAC Log Page Buttons
The RAC Log page provides the buttons listed in Table 17-2.
Table 17-1. RAC Log Page Information
Field Description
Date/ TimeThe 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. 
SourceThe interface that caused the event.
DescriptionA brief description of the event and the user name that logged into 
the DRAC 5.
Table 17-2. RAC Log Buttons
Button Action
PrintPrints the RAC Log page. 
Clear LogClears 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.
RefreshReloads the RAC Log page. 
						

							Recovering and Troubleshooting the DRAC 5287
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.
racadm getraclog [options]
 NOTE: For more information, see getraclog on page 321.
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 17-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:
1
In the System tree, click Remote Access.
2Click the Diagnostics tab.
Table 17-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  r e f r e s h  t h e  Diagnostic Console page, click Refresh. To execute another 
command, click Go Back to Diagnostics Page.
Table 17-3. Diagnostic Commands
Command Description
arpDisplays the contents of the Address Resolution Protocol 
(ARP) table. ARP entries may not be added or deleted. 
ifconfigDisplays the contents of the network interface table. 
						

							288Recovering and Troubleshooting the DRAC 5
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:
1
In the System tree, click Remote Access.
2Click the Diagnostics tab.
3Ty p e  t h e  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 on page 325 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. netstatPrints 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 
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. 
gettracelogDisplays the DRAC 5 trace log. See gettracelog on page 325 
for more information. Table 17-3. Diagnostic Commands 
(continued)
Command Description 
						

							Recovering and Troubleshooting the DRAC 5289
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 on page 317 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.
See the coredump on page 302 and coredumpdelete on page 303 for more 
information. 
						

							290Recovering and Troubleshooting the DRAC 5