solid green (only for power button)

The server is powered on. Absence of the green LED means the server is not powered on.

solid blue

iDRAC6 is healthy.

flashing amber

iDRAC6 has detected a fault condition or may be in the process of updating firmware.

flashing blue

A user has activated the locator ID for this server.

Alert messages from the systems management software

See the systems management software documentation.

Messages in the System Event Log

See "Checking the System Event Log (SEL)."

Messages in the start-up POST codes

See "Checking the Post Codes."

Messages on the last crash screen

See "Viewing the Last System Crash Screen."

Alert Messages on the Server Status Screen in the LCD

See "Checking the Server Status Screen for Error Messages."

Messages in iDRAC6 Log

See "Viewing iDRAC6 Log."

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.

A question mark icon indicates that the status is unknown.

Print

Prints the SEL in the sort order that it appears in the window.

Clear Log

Clears 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.

Refresh

Reloads the SEL screen.

Print

Prints the Post Code screen.

Refresh

Reloads the Post Code screen.

Print

Prints the Last Crash Screen screen.

Save

Opens a pop-up window that enables you to save the Last Crash Screen to a directory of your choice.

Delete

Deletes the Last Crash Screen screen.

Refresh

Reloads the Last Crash Screen screen.

Select the boot sequence

Allows you to select the boot sequence to load and play.

• Boot Capture 1 — Loads the most recent boot sequence.
• Boot Capture 2 — Loads the (second most recent) boot sequence that occurred prior to Boot Capture 1.
• Boot Capture 3 — Loads the (third most recent) boot sequence that occurred prior to Boot Capture 2.

Save As

Creates a compressed .zip file that contains all boot capture images of the current sequence. The user must have administrator privileges to perform this action.

Previous Screen

Takes you to previous screen, if any, in the replay console.

Play

Starts the screenplay from current screen in the replay console.

Pause

Pauses the screenplay on the current screen being displayed in the replay console.

Stop

Stops the screenplay and loads the first screen of that boot sequence.

Next Screen

Takes you to next screen, if any, in the replay console.

Print

Prints the Boot Capture image that appears on the screen.

Refresh

Reloads the Boot Capture screen.

Warning

System Board Ambient Temp: Temperature sensor for System Board, warning event

Server ambient temperature crossed a warning threshold

Critical

System Board Ambient Temp: Temperature sensor for System Board, failure event

Server ambient temperature crossed a failure threshold

Critical

System Board CMOS Battery: Battery sensor for System Board, failed was asserted

CMOS battery is not present or has no voltage

Warning

System Board System Level: Current sensor for System Board, warning event

Current crossed a warning threshold

Critical

System Board System Level: Current sensor for System Board, failure event

Current crossed a failure threshold

Critical

CPU<number> <voltage sensor name>: Voltage sensor for CPU<number>, state asserted was asserted

Voltage out of range

Critical

System Board <voltage sensor name>: Voltage sensor for System Board, state asserted was asserted

Voltage out of range

Critical

CPU<number> <voltage sensor name>: Voltage sensor for CPU<number>, state asserted was asserted

Voltage out of range

Critical

CPU<number> Status: Processor sensor for CPU<number, IERR was asserted

CPU failure

Critical

CPU<number> Status: Processor sensor for CPU<number>, thermal tripped was asserted

CPU overheated

Critical

CPU<number> Status: Processor sensor for CPU<number, configuration error was asserted

Incorrect processor type or in wrong location

Critical

CPU<number> Status: Processor sensor for CPU<number>, presence was deasserted

Required CPU is missing or not present

Critical

System Board Video Riser: Module sensor for System Board, device removed was asserted

Required module was removed

Critical

Mezz B<slot number> Status: Add-in Card sensor for Mezz B<slot number>, install error was asserted

Incorrect Mezzanine card installed for IO fabric

Critical

Mezz C<slot number> Status: Add-in Card sensor for Mezz C<slot number>, install error was asserted

Incorrect Mezzanine card installed for I/O fabric

Critical

Backplane Drive <number>: Drive Slot sensor for Backplane, drive removed

Storage drive was removed

Critical

Backplane Drive <number>: Drive Slot sensor for Backplane, drive fault was asserted

Storage drive failed

Critical

System Board PFault Fail Safe: Voltage sensor for System Board, state asserted was asserted

This event is generated when the system board voltages are not at normal levels

Critical

System Board OS Watchdog: Watchdog sensor for System Board, timer expired was asserted

iDRAC6 watchdog timer expired and no action is set

Critical

System Board OS Watchdog: Watchdog sensor for System Board, reboot was asserted

iDRAC6 watchdog detected that the system has crashed (timer expired because no response was received from Host) and the action is set to reboot

Critical

System Board OS Watchdog: Watchdog sensor for System Board, power off was asserted

iDRAC6 watchdog detected that the system has crashed (timer expired because no response was received from Host) and the action is set to power off

Critical

System Board OS Watchdog: Watchdog sensor for System Board, power cycle was asserted

iDRAC6 watchdog detected that the system has crashed (timer expired because no response was received from Host) and the action is set to power cycle

Critical

System Board SEL: Event Log sensor for System Board, log full was asserted

The SEL device detects that only one entry can be added to the SEL before it is full

Warning

ECC Corr Err: Memory sensor, correctable ECC
( <DIMM Location> ) was asserted

Correctable ECC errors reached a critical rate

Critical

ECC Uncorr Err: Memory sensor, uncorrectable ECC
( <DIMM Location> ) was asserted

An uncorrectable ECC error was detected

Critical

I/O Channel Chk: Critical Event sensor, I/O channel check NMI was asserted

A critical interrupt is generated in the I/O Channel

Critical

PCI Parity Err: Critical Event sensor, PCI PERR was asserted

Parity error was detected on the PCI bus

Critical

PCI System Err: Critical Event sensor, PCI SERR
( <Slot number or PCI Device ID>) was asserted

PCI error detected by device

Critical

SBE Log Disabled: Event Log sensor, correctable memory error logging disabled was asserted

Single bit error logging is disabled when too many SBE get logged

Critical

Logging Disabled: Event Log sensor, all event logging disabled was asserted

All error logging is disabled

Non-Recoverable

CPU Protocol Err: Processor sensor, transition to non-recoverable was asserted

The processor protocol entered a non-recoverable state

Non-Recoverable

CPU Bus PERR: Processor sensor, transition to non-recoverable was asserted

The processor bus PERR entered a non-recoverable state

Non-Recoverable

CPU Init Err: Processor sensor, transition to non-recoverable was asserted

The processor initialization entered a non-recoverable state

Non-Recoverable

CPU Machine Chk: Processor sensor, transition to non-recoverable was asserted

The processor machine check entered a non-recoverable state

Critical

Memory Spared: Memory sensor, redundancy lost
( <DIMM Location> ) was asserted

Memory spare is no longer redundant

Critical

Memory Mirrored: Memory sensor, redundancy lost
( <DIMM Location> ) was asserted

Mirrored memory is no longer redundant

Critical

Memory RAID: Memory sensor, redundancy lost
( <DIMM Location> ) was asserted

RAID Memory is no longer redundant

Warning

Memory Added: Memory sensor, presence ( <DIMM Location> ) was deasserted

Added memory module was removed

Warning

Memory Removed: Memory sensor, presence ( <DIMM Location> ) was deasserted

Memory module was removed

Critical

Memory Cfg Err: Memory sensor, configuration error
( <DIMM Location> ) was asserted

Memory configuration is incorrect for the system

Warning

Mem Redun Gain: Memory sensor, redundancy degraded
( <DIMM Location> ) was asserted

Memory redundancy is downgraded but not lost

Critical

PCIE Fatal Err: Critical Event sensor, bus fatal error was asserted

Fatal error is detected on the PCIE bus

Critical

Chipset Err: Critical Event sensor, PCI PERR was asserted

Chip error is detected

Warning

Mem ECC Warning: Memory sensor, transition to non-critical from OK (<DIMM Location> ) was asserted

Correctable ECC errors have increased from a normal rate

Critical

Mem ECC Warning: Memory sensor, transition to critical from less severe ( <DIMM Location> ) was asserted

Correctable ECC errors have reached a critical rate

Critical

POST Err: POST sensor, No memory installed

No memory detected on board

Critical

POST Err: POST sensor, Memory configuration error

Memory detected but is not configurable

Critical

POST Err: POST sensor, Unusable memory error

Memory configured but not usable

Critical

POST Err: POST sensor, Shadow BIOS failed

System BIOS shadow failure

Critical

POST Err: POST sensor, CMOS failed

CMOS failure

Critical

POST Err: POST sensor, DMA controller failed

DMA controller failure

Critical

POST Err: POST sensor, Interrupt controller failed

Interrupt controller failure

Critical

POST Err: POST sensor, Timer refresh failed

Timer refresh failure

Critical

POST Err: POST sensor, Programmable interval timer error

Programmable interval timer error

Critical

POST Err: POST sensor, Parity error

Parity error

Critical

POST Err: POST sensor, SIO failed

SIO failure

Critical

POST Err: POST sensor, Keyboard controller failed

Keyboard controller failure

Critical

POST Err: POST sensor, System management interrupt initialization failed

System Management Interrupt initialization failure

Critical

POST Err: POST sensor, BIOS shutdown test failed

BIOS shutdown test failure

Critical

POST Err: POST sensor, BIOS POST memory test failed

BIOS POST memory test failure

Critical

POST Err: POST sensor, Dell remote access controller configuration failed

Dell Remote Access Controller configuration failure

Critical

POST Err: POST sensor, CPU configuration failed

CPU configuration failure

Critical

POST Err: POST sensor, Incorrect memory configuration

Incorrect memory configuration

Critical

POST Err: POST sensor, POST failure

General failure after video

Critical

Hdwar version err: Version Change sensor, hardware incompatibility was asserted

Incompatible hardware was detected

Critical

Hdwar version err: Version Change sensor, hardware incompatibility (BMC firmware) was asserted

Hardware is incompatible with the firmware

Critical

Hdwar version err: Version Change sensor, hardware incompatibility (BMC firmware and CPU mismatch) was asserted

CPU and firmware not compatible

Critical

Mem Overtemp: Memory sensor, correctable ECC <DIMM Location> was asserted

Memory module overheating

Critical

Mem Fatal SB CRC: Memory sensor, uncorrectable ECC was asserted

South bridge memory failed

Critical

Mem Fatal NB CRC: Memory sensor, uncorrectable ECC was asserted

North bridge memory failed

Critical

WatchDog Timer: Watchdog sensor, reboot was asserted

Watch dog timer caused system to reboot

Critical

WatchDog Timer: Watchdog sensor, timer expired was asserted

Watch dog timer expired but no action taken

Warning

Link Tuning: Version Change sensor, successful software or
F/W change was deasserted

Failed to update link tuning setting for proper NIC operation

Warning

Link Tuning: Version Change sensor, successful hardware change <device slot number> was deasserted

Failed to update link tuning setting for proper NIC operation

Critical

LinkT/FlexAddr: Link Tuning sensor, failed to program virtual MAC address (Bus # Device # Function #) was asserted

FlexAddress could not be programmed for this device

Critical

LinkT/FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or flex address (Mezz <location>) was asserted

Option ROM does not support FlexAddress or linking tuning

Critical

LinkT/FlexAddr: Link Tuning sensor, failed to get link tuning or flex address data from BMC/iDRAC6 was asserted

Failed to obtain linking tuning or FlexAddress information from BMC/iDRAC6

Critical

LinkT/FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or FlexAddress (Mezz XX) was asserted

This event is generated when the PCI device Option ROM for a NIC does not support link tuning or the Flex addressing feature

Critical

LinkT/FlexAddr: Link Tuning sensor, failed to program the virtual MAC address (<location>) was asserted

This event is generated when the BIOS fails to program the virtual MAC address on the given NIC device

Critical

I/O Fatal Err: Fatal IO Group sensor, fatal IO error (<location>)

This event is generated in association with a CPU IERR and indicates which device caused the CPU IERR

Warning

PCIE NonFatal Er: Non Fatal I/O Group sensor, PCIe error (<location>)

This event is generated in association with a CPU IERR

Date/Time

The date and time (for example, Dec 19 16:55:47).

iDRAC6 sets its clock from the managed server's clock. When iDRAC6 initially starts and is unable to communicate with the managed server, the time is displayed as the string System Boot.

Source

The interface that caused the event.

Description

A brief description of the event and the user name that logged in to iDRAC6.

Print

Prints iDRAC6 Log screen.

Clear Log

Clears iDRAC6 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 iDRAC6 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 iDRAC6 Log screen.

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.

ping <IP Address>

Verifies that the destination IP address is reachable from iDRAC6 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.

ping6 <IPv6 Address>

Verifies that the destination IPv6 address is accessible from iDRAC6 with the current routing–table contents. A destination IPv6 address must be entered in the field to the right of this option. An ICMP (Internet control message protocol) echo packet is sent to the destination IPv6 address based on the current routing–table contents.

traceroute <IP Address>

Used to determine the route taken by packets across an IP network.

traceroute6 <IPv6 Address>

Used to determine the route taken by packets across an IPv6 network.

gettracelog

Displays iDRAC6 trace log. See "gettracelog" for more information.

Power On System

Turns on the system power (equivalent to pressing the power button when the system power is off).

Power Off System

Turns off the system power (equivalent to pressing the power button when the system power is on).

NMI (Non-Masking Interrupt)

Sends a high-level interrupt to the operating system, which causes the system to halt operation to allow for critical diagnostic or troubleshooting activities.

Graceful Shutdown

Attempts to cleanly shut down the operating system, then powers off the system. It requires an ACPI (Advanced Configuration and Power Interface) aware operating system, which allows for system directed power management.

NOTE: A graceful shutdown of the server operating system may not be possible when the server software stops responding, or if you are not logged as an administrator at a local Windows console. In these cases, you must specify a forced reboot instead of a graceful shutdown of Windows. In addition, depending on the version of the Windows OS, there might be a policy configured around the shutdown process that modifies shutdown behavior when triggered from iDRAC6. See Microsoft's documentation for the local computer policy "Shutdown: Allow system to be shut down without having to login."

Reset System (warm boot)

Reboots the system without powering off (warm boot).

Power Cycle System (cold boot)

Powers off, then reboots the system (cold boot).

The LED on the server is blinking amber.

Check the SEL for messages and then clear the SEL to stop the blinking LED.

From iDRAC6 Web interface:

• See "Checking the System Event Log (SEL)"

From SM-CLP:

• See "SEL Management"

From iDRAC6 Configuration Utility:

• See "System Event Log Menu"

There is a blinking blue LED on the server.

A user has activated the locator ID for the server. This is a signal to help them identify the server in the chassis. See "Identifying the Managed Server in the Chassis" for information about this feature.

How can I find the IP address of iDRAC6?

From CMC Web interface:

1. Click Chassis® Servers, then click the Setup tab.
2. Click Deploy.
3. Read the IP address for your server from the table that is displayed.

From the iKVM:

1. Reboot the server and enter iDRAC6 Configuration Utility by pressing <Ctrl><E>.
2. Watch for the IP address which displays during BIOS POST.
3. Select the "Dell CMC" console in the OSCAR to log in to CMC through a local serial connection. CMC RACADM commands can be issued from this connection. See the Dell Chassis Management Controller Administrator Reference Guide for a complete list of CMC RACADM subcommands.
4. Use the local RACADM getsysinfo command to view iDRAC6 IP address.

For example:

$ racadm getniccfg -m server-1

DHCP Enabled = 1
IP Address = 192.168.0.1
Subnet Mask = 255.255.255.0
Gateway = 192.168.0.1

From local RACADM:

Enter the following command at a command prompt:

racadm getsysinfo

From the LCD:

1. On the Main Menu, highlight Server and press the check button.
2. Select the server whose IP address you seek and press the check button.

How can I find the IP address of CMC?

From iDRAC6 Web interface:

• Click System® Remote Access® CMC.

CMC IP address is displayed on the CMC Summary screen.

From the iKVM:

• Select the "Dell CMC" console in the OSCAR to log in to CMC through a local serial connection. CMC RACADM commands can be issued from this connection. See the Dell Chassis Management Controller Administrator Reference Guide for a complete list of CMC RACADM subcommands

$ racadm getniccfg -m chassis

NIC Enabled = 1
DHCP Enabled = 1
Static IP Address = 192.168.0.120
Static Subnet Mask = 255.255.255.0
Static Gateway = 192.168.0.1
Current IP Address = 10.35.155.151
Current Subnet Mask = 255.255.255.0
Current Gateway = 10.35.155.1
Speed = Autonegotiate
Duplex = Autonegotiate

NOTE: The above action can also be performed with remote RACADM.

iDRAC6 network connection is not working.

• Ensure that the LAN cable is connected to CMC.
• Ensure that NIC settings, IPv4 or IPv6 settings, and either Static or DHCP is enabled for your network.

I inserted the server into the chassis and pressed the power button, but nothing happened.

• iDRAC6 requires upto 2 minutes to initialize before the server can power up.
• Check CMC power budget. The chassis power budget may have exceeded.

I have forgotten iDRAC6 administrative user name and password.

You must restore iDRAC6 to its default settings.

1. Reboot the server and press <Ctrl><E> when prompted to enter iDRAC6 Configuration Utility.
2. On iDRAC6 Configuration Utility menu, highlight Reset to Default and press <Enter>.

NOTE: You can also reset iDRAC6 from local RACADM by issuing racadm racresetcfg.

For more information, see "Reset to Default."

How can I change the name of the slot for my server?

1. Log in to CMC Web interface.
2. Open the Chassis tree and click Servers.
3. Click the Setup tab.
4. Enter the new name for the slot in the row for your server.
5. Click Apply.

When starting a console redirection session from iDRAC6 Web interface, an ActiveX security popup appears.

iDRAC6 may not be a trusted site. To prevent the security popup from appearing every time you begin a console redirection session, add iDRAC6 to the trusted site list in the client browser:

1. Click Tools® Internet Options® Security® Trusted sites.
2. Click Sites and enter the IP address or the DNS name of iDRAC6.
3. Click Add.
4. Click Custom Level.
5. In the Security Settings window, select Prompt under Download unsigned ActiveX Controls.

When I start a console redirection session, the viewer screen is blank.

If you have Virtual Media privilege but not Console Redirection privilege, you are able to start the viewer so that you can access the virtual media feature, but the managed server's console will not display.

iDRAC6 is not responding during boot.

Remove and reinsert the server.

Check CMC Web interface to see if iDRAC6 appears as an upgradable component. If it does, follow the instructions in "Updating iDRAC6 Firmware Using CMC."

If this does not correct the problem, contact technical support.

When attempting to boot the managed server, the power indicator is green, but there is no POST or no video at all.

This can happen if any of the following conditions is true:

• Memory is not installed or is inaccessible.
• The CPU is not installed or is inaccessible.
• The video riser card is missing or improperly connected.

Also, look for error messages in iDRAC6 log from iDRAC6 Web interface or from the LCD.