Dell Chassis Management Controller Firmware Version 3.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this publication is subject to change without notice. © 2010 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . What’s New For This Release . . . . . . . . . . . . . . 19 . . . . . . . . . . . . . . 20 Security Features . . . . . . . . . . . . . . . . . . . . 21 Chassis Overview . . . . . . . . . . . . . . . . . . . . 22 CMC Management Features . Hardware Specifications TCP/IP Ports . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . 23 . . . . . . . . 24 . . . . . . . . . . . . . . . . . .
Basic CMC Network Connection . . . . . . . . . . Daisy-chain CMC Network Connection 31 . . . . . . . . 35 . . . . . . . . . . . . 35 Installing Remote Access Software on a Management Station . . . . . . . . . . . Installing RACADM on a Linux Management Station . Uninstalling RACADM From a Linux Management Station . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . . . . . . . 37 Configuring a Web Browser . Proxy Server Microsoft Phishing Filter . . . . .
Adding SNMP and E-mail Alerts Configuring Remote Syslog . . . . . . . . . . . 52 . . . . . . . . . . . . 52 . . . 53 . . . . . . . . . . . . . . 53 Understanding the Redundant CMC Environment. About the Standby CMC Active CMC Election Process Obtaining Health Status of Redundant CMC . . . . . 3 . . . . . . . . . . . 54 . . . . . . . . . . . . . 54 Configuring CMC to Use Command Line Consoles . . . . . . . . . . . . . . . . . . . . . 55 . . . . .
4 Using the RACADM Command Line Interface . . . . . . . . . . . . . . . . . . . . . 69 . . . . . . . . . 69 Logging in to the CMC . . . . . . . . . . . . . . . 70 Starting a Text Console . . . . . . . . . . . . . . . 70 . . . . . . . . . . . . . . . . . . . . . 70 Using a Serial, Telnet, or SSH Console Using RACADM . RACADM Subcommands . . . . . . . . . . . . . . Accessing RACADM Remotely . . . . . . . . . . . Enabling and Disabling the RACADM Remote Capability . . . . . . . . . . . . .
Deleting the Public Keys . . . . . . . . . . . . . . 92 Logging in Using Public Key Authentication . . . . . . . . . . . . . . . . . 92 Enabling a CMC User With Permissions Disabling a CMC User . . . . . . 93 . . . . . . . . . . . . . . . 93 . . . . . . . . 94 . . . . . . . . . . . . . 94 Configuring SNMP and E-mail Alerting . Configuring Multiple CMCs in Multiple Chassis . . . . . . . . . . . . . . . . 95 . . . . . . . . . . . . . . . . . . . 97 Creating a CMC Configuration File .
Disabling an Individual Member at the Member Chassis . . . . . . . . . . . . . . . . . 110 . . . . . . . . . . . . 110 . . . . . . . . . . . . . . . . . 110 . . . . . . . . . . . . . . . . . . 112 Chassis Component Summary . Chassis Graphics Chassis Health Selected Component Information . . . . . . . . . . . 113 Monitoring System Health Status . . . . . . . . . . . 119 Viewing Chassis and Component Summaries . . . . . . . . . . . . Viewing Power Budget Status . . . . . . . . 119 . . . . .
Configuring CMC Network Properties . . . . . . . . . 142 Setting Up Initial Access to CMC . . . . . . . . . . 142 Configuring the Network LAN Settings . . . . . . . 143 . . . . . . . . . . . . . 151 . . . . . . . . . . . . . . . . . . . . 153 Configuring CMC Network Security Settings . . . . . Configuring VLAN Adding and Configuring CMC Users . User Types . . . . . . . . . . 154 . . . . . . . . . . . . . . . . . . . . . 154 Adding and Managing Users . . . . . . . . . . . .
Uploading a Server Certificate . . . . . . . . . . 178 Uploading Webserver Key and Certificate . . . . . . . . . . . . . . . . . . . . . 178 . . . . . . . . . . . 179 . . . . . . . . . . . . . . . . . . 179 Viewing a Server Certificate Managing Sessions Configuring Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 . . . . . . . . . . . . . 189 Configuring Power Budgeting . Managing Firmware Updates . . . . . 189 . . . . . . . . . . . . . . . .
6 Using FlexAddress . Activating FlexAddress . . . . . . . . . . . . . . . . Deactivating FlexAddress . . . . . . . . . . 220 . . . . . . . . . . . . . . . 221 Deactivating FlexAddress 222 . . . . . . . . Additional FlexAddress Configuration for Linux . . . . . . . . . . . . . . . . 223 . . . . . . . . . . . . . 223 . . . . . . . . 224 . . . . . . . . . 224 . . . . . . . . . . . . . . 224 . . . . . . . . . . . . . . . . . . 228 Viewing FlexAddress Status Using the CLI .
Standard Schema Versus Extended Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 242 . . . . . . . . 244 Standard Schema Active Directory Overview. Configuring Standard Schema Active Directory to Access CMC . Configuring CMC With Standard Schema Active Directory and Web Interface . . . . . . . 244 Configuring CMC With Standard Schema Active Directory and RACADM . . . . . . . . . . 247 . . . . . . . . . . . . . 248 Extended Schema Overview . Active Directory Schema Extensions . . .
Configuring the Browser For Single Sign-On Login . . . . Logging into CMC Using Single Sign-On . . . . . . 277 . . . . . . . . . . 278 . . . . . . . . . . . . . . . 278 . . . . . . . . . . . . . . . . 278 Configuring Smart Card Two-Factor Authentication . . . . . . . . . . . . System Requirements. Configuring Settings Configuring Active Directory . Configuring CMC . . . . . . . . . . . 279 . . . . . . . . . . . . . . . . . .
No Redundancy Mode . . . . . . . . . . . . . . Power Budgeting for Hardware Modules Server Slot Power Priority Settings. 293 . . . . . . . 295 Dynamic Power Supply Engagement . . . . . . . 296 Redundancy Policies. . . . . . . . . . . . . . . . . . 298 AC Redundancy . . . . . . . . . . . . . . . . . . 298 Power Supply Redundancy . No Redundancy . . . . . . . . . . . . 298 . . . . . . . . . . . . . . . . . 299 Power Conservation and Power Budget Changes . . . . . . . . . . . . . . . . .
10 Using the iKVM Module . Overview . . . . . . . . . . . . . 333 . . . . . . . . . . . . . . . . . . . . . . . . 333 . . . . . . . . . . . . . . . . 333 Security . . . . . . . . . . . . . . . . . . . . . . . 333 Scanning . . . . . . . . . . . . . . . . . . . . . . 333 iKVM User Interface Server Identification Video . . . . . . . . . . . . . . . . 334 . . . . . . . . . . . . . . . . . . . . . . . . 334 Plug and Play . . . . . . . . . . . . . . . . . . . . FLASH Upgradable . . . . . . .
11 I/O Fabric Management . Fabric Management . . . . . . . . . . . . 361 . . . . . . . . . . . . . . . . . . 362 Invalid Configurations . . . . . . . . . . . . . . . . . Invalid Mezzanine Card (MC) Configuration . . . . . . . . . . . . . . . . . . . Invalid IOM-Mezzanine Card (MC) Configuration . . . . . . . . . . . 364 . . . . . . . . . 364 . . . . . . . . . . . . . . . 364 . . . . . . . . . . . . . . . . 365 Fresh Power-up Scenario Viewing the Health Status of an Individual IOM . . . . .
Configuring E-mail Alerts . . . . . . . . . . . . . . . . . . 388 . . . . . . . 389 . . . . . . . . . . . 389 First Steps to Troubleshooting a Remote System Monitoring Power and Executing Power Control Commands on the Chassis . . . . Viewing Power Budget Status Executing a Power Control Operation Power Troubleshooting . . . . . . . 389 . . . . . . . . . . . . . . . . . 389 Viewing Chassis Summaries . . . . . . . . . . . . . . Viewing Chassis and Component Health Status . . . . . . . . . . .
Troubleshooting Alerting 13 Diagnostics . . . . . . . . . . . . . . . 416 . . . . . . . . . . . . . . . . . . . . . . 417 Using the LCD Panel Interface . . . . . . . . . . . . . 417 LCD Navigation . . . . . . . . . . . . . . . . . . . . . 417 Main Menu . . . . . . . . . . . . . . . . . . . . 418 LCD Setup Menu . . . . . . . . . . . . . . . . . Language Setup Screen Default Screen 419 . . . . . . . . . . . . . . . . . . 419 Graphical Server Status Screen . . . . . . . . .
1 Overview The Dell Chassis Management Controller (CMC) is a hot-pluggable systems management hardware and software solution designed to provide remote management capabilities and power control functions for Dell PowerEdge M1000e chassis systems. You can configure the CMC to send e-mail alerts or SNMP trap alerts for warnings or errors related to temperatures, hardware misconfigurations, power outages, and fan speeds.
CMC Management Features The CMC provides the following management features: 20 • Redundant CMC Environment. • Dynamic Domain Name System (DDNS) registration for IPv4 and IPv6. • Remote system management and monitoring using SNMP, a Web interface, iKVM, Telnet or SSH connection. • Support for Microsoft Active Directory authentication — Centralizes CMC user IDs and passwords in Active Directory using the Standard Schema or an Extended Schema.
• Support for WS-Management. • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade. For more information, see "Using FlexAddress" on page 217. • Graphical display of chassis component status and health. • Support for single and multi-slot servers. • Update multiple iDRAC management consoles firmware at once.
• Limited IP address range for clients connecting to the CMC • Secure Shell (SSH), which uses an encrypted layer for higher security • Single Sign-on, Two-Factor Authentication, and Public Key Authentication Chassis Overview Figure 1-1 shows the facing edge of a CMC (inset) and the locations of the CMC slots in the chassis. Figure 1-1.
Hardware Specifications TCP/IP Ports You must provide port information when opening firewalls for remote access to a CMC. Table 1-1. CMC Server Listening Ports Port Number Function 22* SSH 23* Telnet 80* HTTP 161 SNMP Agent 443* HTTPS * Configurable port Table 1-2.
Supported Remote Access Connections Table 1-3.
Supported Web Browsers The following Web Browsers are supported for CMC 3.1: • Microsoft Internet Explorer 8.0 for Windows 7, Windows Vista, Windows XP, and Windows Server 2003 family. • Microsoft Internet Explorer 7.0 for Windows 7, Windows Vista, Windows XP, and Windows Server 2003 family. • Mozilla Firefox 1.5 (32-bit) – limited functionality. For the latest information on supported Web browsers, see the Dell Systems Software Support Matrix located on the Dell Support website at support.dell.
management domain or area of functionality. Additionally, Dell has defined a number of model and profile extensions that provide interfaces for additional capabilities. Access to WS-Management requires logging in using local user privileges with basic authentication over Secured Socket Layer (SSL) protocol at port 443. For information on setting user accounts, see the Session Management database property section in the Command Line Reference Guide for iDRAC6 and CMC.
The CMC WS-MAN implementation uses SSL on port 443 for transport security, and supports basic authentication. For information on setting user accounts, see the cfgSessionManagement database property section in the Command Line Reference Guide for iDRAC6 and CMC. Web services interfaces can be utilized by leveraging client infrastructure, such as Windows WinRM and Powershell CLI, open source utilities like WSMANCLI, and application programming environments like Microsoft .NET.
• Documentation specific to your third-party management console application. • The Dell OpenManage Server Administrator’s User’s Guide provides information about installing and using Server Administrator. • The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy.
2 Installing and Setting Up the CMC This section provides information about how to install your CMC hardware, establish access to the CMC, configure your management environment to use the CMC, and guides you through the next steps for configuring the CMC: • Set up initial access to the CMC • Access the CMC through a network • Add and configure CMC users • Update the CMC firmware For more information about installing and setting up redundant CMC environments see "Understanding the Redundant CMC Env
Checklist for Integration of a Chassis The following steps enable you to setup the chassis accurately: 1 Your CMC and the management station where you use your browser must be on the same network, which is called the management network. Cable the CMC Ethernet port labelled GB to management network. NOTE: Do not place a cable in the CMC Ethernet port labelled STK. For more information to cable the STK port, see "Understanding the Redundant CMC Environment" on page 53.
Each CMC has two RJ-45 Ethernet ports, labeled GB (the uplink port) and STK (the stacking or cable consolidation port). With basic cabling, you connect the GB port to the management network and leave the STK port unused. CAUTION: Connecting the STK port to the management network can have unpredictable results. Cabling GB and STK to the same network (broadcast domain) can cause a broadcast storm.
Figure 2-1.
Figure 2-2, Figure 2-3, and Figure 2-4 show examples of incorrect cabling of the CMC. Figure 2-2. Incorrect Cabling for CMC Network Connection - 2 CMCs Figure 2-3.
Figure 2-4. Incorrect Cabling for CMC Network Connection - 2 CMCs Follow these steps to daisy-chain up to four chassis: 1 Connect the GB port of the active CMC in the first chassis to the management network. 2 Connect the GB port of the active CMC in the second chassis to the STK port of the active CMC in the first chassis. 3 If you have a third chassis, connect the GB port of its active CMC to the STK port of the active CMC in the second chassis.
Installing Remote Access Software on a Management Station You can access the CMC from a management station using remote access software, such as the Telnet, Secure Shell (SSH), or serial console utilities provided on your operating system or using the Web interface. To use remote RACADM from your management station, install remote RACADM using the Dell Systems Management Tools and Documentation DVD that is available with your system.
3 To mount the DVD to a required location, use the mount command or a similar command. NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. You need to mount the DVD-ROM manually and then run the executables. 4 Navigate to the SYSMGMT/ManagementStation/linux/rac directory. To install the RAC software, type the following command: rpm -ivh *.
Your CMC and the management station where you use your browser must be on the same network, which is called the management network. Depending on your security requirements, the management network can be an isolated, highly secure network. NOTE: Ensure that security measures on the management network, such as firewalls and proxy servers, do not prevent your Web browser from accessing the CMC.
3 Click Advanced and then click the Network tab. 4 Click Settings. 5 Select the Manual Proxy Configuration. 6 In the No Proxy for field, type the addresses for CMCs and iDRACs on the management network to the comma-separated list. You can use DNS names and wildcards in your entries. Microsoft Phishing Filter If the Microsoft Phishing Filter is enabled in Internet Explorer 7 on your management system, and your CMC does not have Internet access, accessing the CMC may be delayed by a few seconds.
Downloading Files From CMC With Internet Explorer When you use Internet Explorer to download files from the CMC you may experience problems when the Do not save encrypted pages to disk option is not enabled. Follow these steps to enable the Do not save encrypted pages to disk option: 1 Start Internet Explorer. 2 Click Tools Internet Options, then click Advanced. 3 Scroll to the Security section and check Do not save encrypted pages to disk.
The CMC is connected to the management network. All external access to the CMC and iDRACs is accomplished through the CMC. Access to the managed servers, conversely, is accomplished through network connections to I/O modules (IOMs). This allows the application network to be isolated from the management network. NOTE: It is recommended to isolate chassis management from the data network. Dell cannot support or guarantee uptime of a chassis that is improperly integrated into your environment.
You can perform the initial network configuration of the CMC before or after the CMC has an IP address.
The LCD is located on the bottom left corner on the front of the chassis. Figure 2-5 illustrates the LCD panel. Figure 2-5. LCD Display 1 2 3 4 1 LCD screen 2 selection ("check") button 3 scroll buttons (4) 4 status indicator LED The LCD screen displays menus, icons, pictures, and messages. A status indicator LED on the LCD panel provides an indication of the overall health of the chassis and its components. • 42 Solid blue indicates good health.
• Blinking amber indicates that at least one component has a fault condition. • Blinking blue is an ID signal, used to identify one chassis in a group of chassis. Navigating in the LCD Screen The right side of the LCD panel contains five buttons: four arrow buttons (up, down, left, and right) and a center button. • To move between screens, use the right (next) and left (previous) arrow buttons. At any time while using the Configuration Wizard, you can return to a previous screen.
4 Press the center button to continue to the CMC Network Settings screen. 5 Select your network speed (10Mbps, 100Mbps, Auto (1 Gbps)) using the down arrow button. NOTE: The Network Speed setting must match your network configuration for effective network throughput. Setting the Network Speed lower than the speed of your network configuration increases bandwidth consumption and slows network communication. Determine whether your network supports the above network speeds and set it accordingly.
8 Select the mode in which you want the CMC to obtain the NIC IP addresses: Dynamic Host Configuration Protocol (DHCP) The CMC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. The CMC is assigned a unique IP address allotted over your network. If you have selected the DHCP option, press the center button. The Configure iDRAC? screen appears; go to step 10.
Set the DNS IP Address using the right or left arrow keys to move between positions, and the up and down arrow keys to select a number for each position. When you have finished setting the DNS IP address, press the center button to continue. 10 Indicate whether you want to configure iDRAC: – No: Skip to step 13. – Yes: Press the center button to proceed. You can also configure iDRAC from the CMC GUI. 11 Select the Internet Protocol (IPv4, IPv6, or both) that you want to use for the servers.
the installed servers, highlight the No icon and press the center button and continue to step c. c On the next iDRAC Configuration screen, to apply all iDRAC network settings to newly installed servers, highlight the Accept/Yes icon and press the center button; when a new server is inserted into the chassis, the LCD prompts the user on whether to automatically deploy the server using the previously configured network settings/policies.
Accessing the CMC Through a Network After you have configured the CMC network settings, you can remotely access the CMC using any of the following interfaces: • Web interface • Telnet console • SSH • Remote RACADM NOTE: Since telnet is not as secure as the other interfaces, it is disabled by default. Enable Telnet using web, ssh, or remote RACADM. Table 2-1. CMC Interfaces Interface Description Web interface Provides remote access to the CMC using a graphical user interface.
NOTE: The CMC default user name is root and the default password is calvin. You can access the CMC and iDRAC Web interfaces through the CMC Network Interface using a supported Web browser; you can also launch them from the Dell Server Administrator or Dell OpenManage IT Assistant. For a list of supported Web browsers, see the Supported Browsers section in the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com/manuals.
NOTE: During updates of CMC firmware, it is normal for some or all of the fan units in the chassis to spin at 100%. NOTE: The firmware update, by default, retains the current CMC settings. During the update process, you have the option to reset the CMC configuration settings back to the factory default settings. NOTE: If you have redundant CMCs installed in the chassis, it is important to update both to the same firmware version.
Configuring CMC Properties You can configure CMC properties such as power budgeting, network settings, users, and SNMP and e-mail alerts using the Web interface or RACADM. For more information about using the Web interface, see "Accessing the CMC Web Interface" on page 103. For more information about using RACADM, see "Using the RACADM Command Line Interface" on page 69. CAUTION: Using more than one CMC configuration tool at the same time may generate unexpected results.
Adding and Configuring Users You can add and configure CMC users using either RACADM or the CMC Web interface. You can also utilize Microsoft Active Directory to manage users. For instructions on adding and configuring public key users for the CMC using RACADM, see "Using RACADM to Configure Public Key Authentication over SSH" on page 89. For instructions on adding and configuring users using the Web interface, see "Adding and Configuring CMC Users" on page 154.
Understanding the Redundant CMC Environment You can install a standby CMC that takes over if your active CMC fails. Your redundant CMC may be pre-installed or can be added at a later date. It is important that the CMC network is properly cabled to ensure full redundancy or best performance. Failovers can occur when you: • Run the RACADM cmcchangeover command. (See the cmcchangeover command section in the Command Line Reference Guide for iDRAC6 and CMC. • Run the RACADM racreset command on the active CMC.
Active CMC Election Process There is no difference between the two CMC slots; that is, slot does not dictate precedence. Instead, the CMC that is installed or booted first assumes the role of the active CMC. If AC power is applied with two CMCs installed, the CMC installed in CMC chassis slot 1 (the left) normally assumes the active role. The active CMC is indicated by the blue LED.
3 Configuring CMC to Use Command Line Consoles This section provides information about the CMC command line console (or serial/Telnet/Secure Shell console) features, and explains how to set up your system so you can perform systems management actions through the console. For information on using the RACADM commands in CMC through the command line console, see "Using the RACADM Command Line Interface" on page 69.
Using a Serial, Telnet, or SSH Console When you connect to the CMC command line, you can enter these commands: Table 3-1. CMC Command Line Commands Command Description racadm RACADM commands begin with the keyword racadm and are followed by a subcommand, such as getconfig, serveraction, or getsensorinfo. See "Using the RACADM Command Line Interface" on page 69 for details on using RACADM. connect Connects to the serial console of a server or I/O module.
When an error occurs during the login procedure, the SSH client issues an error message. The message text is dependent on the client and is not controlled by the CMC. Review the RACLog messages to determine the cause of the failure. NOTE: OpenSSH should be run from a VT100 or ANSI terminal emulator on Windows. You can also run OpenSSH using Putty.exe. Running OpenSSH at the Windows command prompt does not provide full functionality (that is, some keys do not respond and no graphics are displayed).
The CMC SSH implementation supports multiple cryptography schemes, as shown in Table 3-2. Table 3-2.
Configuring Terminal Emulation Software Your CMC supports a serial text console from a management station running one of the following types of terminal emulation software: • Linux Minicom. • Hilgraeve’s HyperTerminal Private Edition (version 6.3). Perform the steps in the following subsections to configure the required type of terminal software. Configuring Linux Minicom Minicom is a serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0.
8 In the Modem Dialing and Parameter Setup menu, press to clear the init, reset, connect, and hangup settings so that they are blank, and then press to save each blank value. 9 When all specified fields are clear, press to exit the Modem Dialing and Parameter Setup menu. 10 Select Save setup as config_name and press . 11 Select Exit From Minicom and press . 12 At the command shell prompt, type minicom .
Connecting to Servers or I/O Modules With the Connect Command The CMC can establish a connection to redirect the serial console of server or I/O modules. For servers, serial console redirection can be accomplished in several ways: • Using the CMC command line and the connect, or racadm connect command. For more information about connect, see the racadm connect command in the Command Line Reference Guide for iDRAC6 and CMC. • Using the iDRAC Web interface serial console redirection feature.
Table 3-4. Mapping I/O Modules to Switches I/O Module Label Switch A1 switch-a1 A2 switch-a2 B1 switch-b1 B2 switch-b2 C1 switch-c1 C2 switch-c2 NOTE: There can only be one IOM connection per chassis at a time. NOTE: You cannot connect to pass-throughs from the serial console. To connect to a managed server serial console, use the command connect server-n, where -n is the slot number of the server; you can also use the racadm connect server-n command.
Serial communication in the BIOS is OFF by default. To redirect host text console data to Serial over LAN, you must enable console redirection through COM1. To change the BIOS setting: 1 Boot the managed server. 2 Press to enter the BIOS setup utility during POST. 3 Scroll down to Serial Communication and press .
serial --unit=1 --speed=57600 terminal --timeout=10 serial 2 Append two options to the kernel line: kernel............. console=ttyS1,57600 3 If the /etc/grub.conf contains a splashimage directive, comment it out. The following example shows the changes described in this procedure. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes # to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, e.g.
root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 initrd /boot/initrd-2.4.9-e.3.img When you edit the /etc/grub.conf file, follow these guidelines: • Disable GRUB's graphical interface and use the text-based interface; otherwise, the GRUB screen is not displayed in console redirection. To disable the graphical interface, comment out the line starting with splashimage.
# 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc l1:1:wait:/etc/rc.d/rc l2:2:wait:/etc/rc.d/rc l3:3:wait:/etc/rc.d/rc l4:4:wait:/etc/rc.d/rc l5:5:wait:/etc/rc.d/rc l6:6:wait:/etc/rc.d/rc 0 1 2 3 4 5 6 # Things to run in every runlevel.
# Run gettys in standard runlevels co:2345:respawn:/sbin/agetty -h -L 57600 ttyS1 ansi 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 # xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon Edit the file /etc/securetty, as follows: • Add a new line, with the name of the serial tty for COM2: ttyS1 The followi
tty10 tty11 ttyS1 68 Configuring CMC to Use Command Line Consoles
Using the RACADM Command Line Interface 4 RACADM provides a set of commands that allow you to configure and manage the CMC through a text-based interface. RACADM can be accessed using a Telnet/SSH or serial connection, using the Dell CMC console on the iKVM, or remotely using the RACADM command line interface installed on a management station.
Logging in to the CMC After you have configured your management station terminal emulator software and managed node BIOS, perform the following steps to log in to the CMC: 1 Connect to the CMC using your management station terminal emulation software. 2 Type your CMC user name and password, and then press . You are logged in to the CMC. Starting a Text Console You can log in to the CMC using Telnet or SSH through a network, serial port, or a Dell CMC console through the iKVM.
RACADM Subcommands Table 4-1 provides a brief list of common subcommands used in RACADM. For a complete list of RACADM subcommands, including syntax and valid entries, see the RACADM Subcommands chapter in the Command Line Reference Guide for iDRAC6 and CMC. NOTE: The connect command is available as both—RACADM command and builtin CMC command. The exit, quit, and logout commands are built-in CMC commands, not RACADM commands. None of these commands can be used with remote RACADM.
Table 4-1. RACADM Subcommands (continued) Command Description feature Displays active features and feature deactivation. featurecard Displays feature card status information. fwupdate Performs system component firmware updates, and displays firmware update status. getassettag Displays the asset tag for the chassis. getchassisname Displays the name of the chassis. getconfig Displays the current CMC configuration properties.
Table 4-1. RACADM Subcommands (continued) Command Description getsysinfo Displays general CMC and system information. gettracelog Displays the CMCtrace log. If used with the -i option, the command displays the number of entries in the CMC trace log. getversion Displays the current software version, model information, and whether or not the device can be updated. ifconfig Displays the current CMC IP configuration. krbkeytabupload Uploads a Kerberos Keytab to the CMC.
Table 4-1. RACADM Subcommands (continued) Command Description setslotname Sets the name of a slot in the chassis. setsysinfo Sets the name and location of the chassis. sshpkauth Uploads up to 6 different SSH public keys, deletes existing keys, and views the keys already in the CMC. sslcertdownload Downloads a certificate authority-signed certificate. sslcertupload Uploads a certificate authority-signed certificate or server certificate to the CMC.
Table 4-2. Remote RACADM Subcommand Options (continued) Option Description -i Instructs RACADM to interactively query the user for user name and password. -u Specifies the user name that is used to authenticate the command transaction. If the -u option is used, the -p option must be used, and the -i option (interactive) is not allowed. -p Specifies the password used to authenticate the command transaction. If the -p option is used, the -i option is not allowed.
Enabling and Disabling the RACADM Remote Capability NOTE: Dell recommends that you run these commands at the chassis. The RACADM remote capability on the CMC is enabled by default. In the following commands, -g specifies the configuration group the object belongs to, and -o specifies the configuration object to configure.
If you do not know your user ID, try different values for n. NOTE: The RACADM remote capability is supported only on management stations through a supported browser. For more information, see the Supported Browsers section in the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com/manuals. NOTE: When using the RACADM remote capability, you must have write permissions on the folders where you are using the RACADM subcommands involving file operations.
Using RACADM to Configure the CMC NOTE: In order to configure CMC the first time, you must be logged in as user root to execute RACADM commands on a remote system. Another user can be created with priviliges to configure the CMC. The CMC Web interface is the quickest way to configure the CMC (see "Using the CMC Web Interface" on page 103).
Viewing Current IPv4 Network Settings To view a summary of NIC, DHCP, network speed, and duplex settings, type: racadm getniccfg or racadm getconfig -g cfgCurrentLanNetworking Viewing Current IPv6 Network Settings To view a summary of the network settings, type: racadm getconfig -g cfgIpv6LanNetworking To view IPv4 and IPv6 addressing information for the chassis type: racadm getsysinfo By default, the CMC requests and obtains a CMC IP address from the Dynamic Host Configuration Protocol (DHCP) server auto
To view IP address and DHCP, MAC address, and DNS information for the chassis, type: racadm getsysinfo Configuring the Network LAN Settings NOTE: To perform the following steps, you must have Chassis Configuration Administrator privilege. NOTE: The LAN settings, such as community string and SMTP server IP address, affect both the CMC and the external settings of the chassis.
To enable/disable the CMC IPv6 addressing, type: racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 1 racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 0 NOTE: The CMC IPv6 addressing is disabled by default. By default, for IPv4, the CMC requests and obtains a CMC IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically. You can disable the DHCP feature and specify static CMC IP address, gateway, and subnet mask.
Enabling or Disabling DHCP for the CMC Network Interface Address When enabled, the CMC’s DHCP for NIC address feature requests and obtains an IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically. This feature is enabled by default. You can disable the DHCP for NIC address feature and specify a static IP address, subnet mask, and gateway. For more information, see "Setting Up Initial Access to the CMC" on page 78.
For IPv6, to set the preferred and secondary DNS IP Server addresses, type: racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer1 racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer2 Configuring DNS Settings (IPv4 and IPv6) • CMC Registration — To register the CMC on the DNS server, type: racadm config -g cfgLanNetworking -o cfgDNSRegisterRac 1 NOTE: Some DNS servers only register names of 31 characters or fewer.
You can disable auto negotiation and specify the duplex mode and network speed by typing: racadm config -g cfgNetTuning -o cfgNetTuningNicAutoneg 0 racadm config -g cfgNetTuning -o cfgNetTuningNicFullDuplex where: is 0 (half duplex) or 1 (full duplex, default) racadm config -g cfgNetTuning -o cfgNetTuningNicSpeed where: is 10 or 100(default).
You can also specify both the VLAN ID and the VLAN priority with a single command: racadm setniccfg -v For example: racadm setniccfg -v 1 7 Removing the CMC VLAN To remove the CMC VLAN, disable the VLAN capabilities of the external chassis management network: racadm config -g cfgLanNetworking -o cfgNicVLanEnable 0 You can also remove the CMC VLAN using the following command: racadm setniccfg -v Setting up a Server VLAN Specify the VLAN ID and priority of a particular server with
Removing a Server VLAN To remove a server VLAN, disable the VLAN capabilities of the specified server's network: racadm setniccfg -m server- -v The valid values for are 1-16. For example: racadm setniccfg -m server-1 -v Setting the Maximum Transmission Unit (MTU) (IPv4 and IPv6) The MTU property allows you to set a limit for the largest packet that can be passed through the interface.
Enabling IP Range Checking (IPv4 Only) IP filtering compares the IP address of an incoming login to the IP address range that is specified in the following cfgRacTuning properties: • cfgRacTuneIpRangeAddr • cfgRacTuneIpRangeMask A login from the incoming IP address is allowed only if both the following are identical: • cfgRacTuneIpRangeMask bit-wise and with incoming IP address • cfgRacTuneIpRangeMask bit-wise and with cfgRacTuneIpRangeAddr Using RACADM to Configure Users Before You Begin You can c
NOTE: When you manually enable or disable a user with the RACADM config subcommand, you must specify the index with the -i option. Observe that the cfgUserAdminIndex object displayed in the previous example contains a # character. Also, if you use the racadm config -f racadm.cfg command to specify any number of groups/objects to write, the index cannot be specified. A new user is added to the first available index.
To verify that the user was added successfully with the correct privileges, type the following command: racadm getconfig –g cfgUserAdmin –i 2 Using RACADM to Configure Public Key Authentication over SSH Before You Begin You can configure up to 6 public keys that can be used with the service username over SSH interface. Before adding or deleting public keys, be sure to use the view command to see what keys are already set up so a key is not accidentally overwritten or deleted.
For example, if two public keys are set up one with comment PC1 and one with comment PC2: racadm getssninfo Type User SSH PC1 x.x.x.x IP Address 06/16/2009 09:00:00 Login Date/Time SSH PC2 x.x.x.x 06/16/2009 09:00:00 For more information on the sshpkauth, see the Command Line Reference Guide for iDRAC6 and CMC. Generating Public Keys for Windows Before adding an account, a public key is required from the system that accesses the CMC over SSH.
Generating Public Keys for Linux The ssh-keygen application for Linux clients is a command line tool with no graphical user interface. Open a terminal window and at the shell prompt type: ssh-keygen –t rsa –b 1024 –C testing where, –t option must be dsa or rsa. –b option specifies the bit encryption size between 768 and 4096. –C option allows modifying the public key comment and is optional. the passphrase is optional. Follow the instructions.
Adding the Public Keys To add a public key to the CMC using the file upload (-f) option, type: racadm sshpkauth –i svcacct –k 1 –p 0xfff –f NOTE: You can only use the file upload option with remote RACADM. For more information, see "Accessing RACADM Remotely" on page 74 and subsequent sections. For public key privileges, see Table 3-1 in the Database Property chapter of Dell Chassis Management Controller Administrator Reference Guide.
ssh service@ racadm getsel When you log in using the service account, if a passphrase was set up when creating the public/private key pair, you may be prompted to enter that passphrase again. If a passphrase is used with the keys, both Windows and Linux clients provide methods to automate that as well. For Windows clients, you can use the Pageant application. It runs in the background and makes entering the passphrase transparent. For Linux clients, you can use the sshagent.
Configuring SNMP and E-mail Alerting You can configure the CMC to send SNMP event traps and/or e-mail alerts when certain events occur on the chassis. For more information and instructions, see "Configuring SNMP Alerts" on page 379 and "Configuring Email Alerts" on page 385. You can specify the trap destinations as appropriately-formatted numeric addresses (IPv6 or IPv4), or Fully-qualified domain names (FQDNs). Choose a format that is consistent with your networking technology/infrastructure.
3 Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database. 4 Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5 Reset the target CMC that was configured. At the command prompt, type: racadm reset The getconfig -f myfile.cfg subcommand (step 1) requests the CMC configuration for the active CMC and generates the myfile.cfg file.
parsed for correctness, and all errors display. Write commands are not transmitted to the CMC if an error is found in the .cfg file. You must correct all errors before any configuration can take place. To check for errors before you create the configuration file, use the -c option with the config subcommand. With the -c option, config only verifies syntax and does not write to the CMC. Follow these guidelines when you create a .
Parsing Rules • Lines that start with a hash character (#) are treated as comments. A comment line must start in column one. A "#" character in any other column is treated as a # character. Some modem parameters may include # characters in their strings. An escape character is not required. You may want to generate a .cfg from a racadm getconfig -f .cfg command, and then perform a racadm config -f .cfg command to a different CMC, without adding escape characters.
[cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object value} • The .cfg parser ignores an index object entry. You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the first available index for that group. The racadm getconfig -f .cfg command places a comment in front of index objects, allowing you to see the included comments.
This configuration file can be used as an example and as a starting point for your unique .cfg file. Modifying the CMC IP Address When you modify the CMC IP address in the configuration file, remove all unnecessary = entries. Only the actual variable group’s label with [ and ] remains, including the two = entries pertaining to the IP address change. Example: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.10.110 cfgNicGateway=10.35.10.
Using RACADM to Configure Properties on iDRAC RACADM config/getconfig commands support the -m option for the following configuration groups: • cfgLanNetworking • cfgIPv6LanNetworking • cfgRacTuning • cfgRemoteHosts • cfgSerial • cfgSessionManagement NOTE: For more information on the property default values and ranges, see the Integrated Dell Remote Access Controller 6 (iDRAC6) Enterprise for Blade Servers User Guide.
Troubleshooting Table 4-3 lists common problems related to remote RACADM. Table 4-3. Using Serial/ RACADM Commands: Frequently Asked Questions Question Answer After performing a CMC reset (using the RACADM racreset subcommand), I enter a command and the following message is displayed: You must wait until the CMC completes the reset before issuing another command.
Table 4-3. Using Serial/ RACADM Commands: Frequently Asked Questions (continued) Question Answer While I was using remote RACADM, the prompt changed to a ">" and I cannot get the "$" prompt to return. If you type a non-matched double quotation mark (") or a non-matched single quotation (’) in the command, the CLI changes to the ">" prompt and queue all commands.
Using the CMC Web Interface 5 CMC provides a Web interface that enables you to configure CMC properties and users, perform remote management tasks, and troubleshoot a remote (managed) system for problems. For everyday chassis management, use the CMC Web interface. This chapter provides information about how to perform common chassis management tasks using the CMC Web interface.
To access the CMC Web interface over IPv6: 1 Open a supported Web browser window. For the latest information on supported Web browsers, see the Dell Systems Software Support Matrix located on the Dell Support website at support.dell.com/manuals. 2 Type the following URL in the Address field, and then press : https://[] NOTE: While using IPv6, you must enclose the in square brackets ([ ]).
You can log in as either a CMC user or as a Directory user. To log in: 1 In the Username field, type your user name: • CMC user name: • Active Directory user name: \, / or @. • LDAP user name: NOTE: This field is case sensitive. 2 In the Password field, type your CMC user password or Active Directory user password. NOTE: This field is case-sensitive. 3 Optionally, select a session timeout.
To set the chassis name: 1 Log in to the CMC Web interface. The Chassis Health page displays. 2 Click the Setup tab. The General Chassis Settings page displays. 3 Type the new name in the Chassis Name field, and then click Apply. Setting the Date and Time on CMC You can set the date and time manually, or you can synchronize the date and time with a Network Time Protocol (NTP) server. 1 Log in to the CMC Web interface. The Chassis Health page displays. 2 Click the Setup tab.
The Chassis Component Summary section (also entitled "Chassis Health" when the overall chassis information is shown) displays the graphics and their associated information. You can hide this entire section by clicking the Close icon. The left half of the Chassis Component Summary section displays the graphics and Chassis Quick Links. The right half of this section displays information, links, and actions related to the selected component.
Setting up a Chassis Group The Chassis Group is set up with the GUI: 1 Log in with administrator privileges to the chassis planned as the leader. 2 Click Setup Group Administration. The Chassis Group page is displayed. 3 In the Chassis Group page, under Role, select Leader. A field to add the group name is displayed. 4 Enter the Group name in the Group Name field, and then click Apply. NOTE: The same rules that apply for a domain name apply to the group name.
The status of the new member is displayed by selecting the Group in the tree. Details are available by clicking on the chassis image or the details button. NOTE: The credentials entered for a member are passed securely to the member chassis, to establish a trust relationship between the member and lead chassis. The credentials are not persisted on either chassis, and are never exchanged again after the initial trust relationship is established.
The member chassis may not receive the message, if a network issue prevents contact between the leader and the member. In this case, disable the member from the member chassis to complete the removal. See the sub-section “Disabling an Individual Member at the Member Chassis” for the procedure. Disabling an Individual Member at the Member Chassis Sometimes a member cannot be removed from a group by the lead chassis. This can happen if network connectivity to the member is lost.
Table 5-1. Server Icon States Icon Description Server is powered on and is operating normally. Server is off. Server is reporting a non-critical error. Server is reporting a critical error.
Table 5-1. Server Icon States Icon Description No server is present. The Chassis Quick Links are displayed below the Chassis Graphics. Table 5-2.
Table 5-3. Chassis Page Information Field Description Model Displays the model of the Chassis LCD panel. Firmware Displays the firmware version of the active CMC. Service Tag Displays the service tag of the chassis. The service tag is a unique identifier that the manufacturer provides for support and maintenance. Asset Tag Displays the asset tag for the chassis. Input Power Amount of power that the chassis consumes presently. Power Cap User-assigned maximum Input Power to be consumed.
Table 5-4. Health and Performance Information - Servers Item Description Power State On/Off state of the server. See Table 5-23 for details on the various types of power states. Health Displays the text equivalent of the health icon. Power Consumption Amount of power that the server consumes at present. Power Allocated Amount of power budgeted for the server. Temperature Temperature read from the server temperature sensor. Table 5-5.
Table 5-6. Quick Links - Servers Item Description Server Status Navigate to Server Overview Properties Status Launch Remote Invokes a Keyboard-Video-Mouse (KVM) session on the server if Console the server supports this operation. Launch iDRAC GUI Invokes an iDRAC management console for the server. Power On Server Apply power to a server that is in the "Off" state. Power Off Server Remove power from a server that is in the "On" state.
Table 5-9. Quick Links - I/O Modules Item Description IOM Status Navigate to I/O Modules Properties Status Launch IOM GUI If the Launch IOM GUI link is present for a particular I/O module, clicking it launches the IOM management console for that I/O module in a new browser window or tab. Table 5-10. Active CMC Health and Performance Item Description Redundancy Mode Displays failover readiness of the standby CMC.
Table 5-12. Quick Links - CMC Item Description CMC Status Navigate to Chassis Controller Properties Status Networking Navigate to Chassis Overview Network Network Firmware Update Navigate to Chassis Overview Update Firmware Update Table 5-13. iKVM Health and Performance Item Description OSCAR Console Displays whether the rear panel VGA connector is enabled (Yes or No) for access to CMC. Table 5-14. iKVM Properties Item Description Name Displays the name of the iKVM.
Table 5-17. Fan Properties Item Description Lower Critical Threshold Speed below which the fan is considered to have failed. Upper Critical Threshold Speed above which the fan is considered to have failed. Table 5-18. Quick Links - Fan Item Description Fan Status Navigate to Fans Properties Status Table 5-19.
Table 5-22. LCD Health and Performance Item Description LCD Health Displays the presence and health of the LCD panel. Chassis Health Displays the text description of Chassis Health. There are no Quick Links for the LCD. Monitoring System Health Status Viewing Chassis and Component Summaries CMC displays a graphical representation of the chassis on the Chassis Health page that provides a visual overview of installed component status.
The Chassis Health page provides an overall health status for the chassis, active and standby CMCs, sever modules, IO Modules (IOMs), fans, iKVM, power supplies (PSUs), and LCD assembly. More detailed information for each component is displayed by clicking on that component. For instructions on viewing chassis and components summaries, see "Viewing Chassis Summaries" on page 392.
To view health status for all servers using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed. The left section of Chassis Graphics depicts the front view of the chassis and contains the health status of all servers. Server health status is indicated by the overlay of the server subgraphic: • No overlay - server is present, powered on and communicating with CMC; there is no indication of an adverse condition.
Table 5-23. All Servers Status Information (continued) Item Health Description OK Displays that the server is present and communicating with CMC. In the event of a communication failure between CMC and the server, CMC cannot obtain or display health status for the server. Informational Displays information about the server when no change in health status (OK, Warning, Critical) has occurred.
Table 5-23. Item All Servers Status Information (continued) Description Launch Left click the button to launch the iDRAC management console for iDRAC GUI a server in a new browser window or tab. This icon is only displayed for a server where all of the following conditions are met: • The server is present. • The chassis power is on. • The LAN interface on the server is enabled.
Editing Slot Names The Slot Names page allows you to update slot names in the chassis. Slot names are used to identify individual servers. When choosing slot names, the following rules apply: • Names may contain a maximum of 15 non-extended ASCII characters (ASCII codes 32 through 126). • Slot names must be unique within the chassis. No two slots may have the same name. • Strings are not case-sensitive. Server-1, server-1, and SERVER-1 are equivalent names.
To edit a slot name: 1 Log in to the CMC Web interface. 2 Select Server Overview in the Chassis menu in the system tree. 3 Click Setup Slot Names. The Slot Names page displays. 4 Type the updated or new name for a slot in the Slot Name field. Repeat this action for each slot you want to rename. 5 Click Apply. 6 To restore the default slot name (SLOT-01 to SLOT-16, based on the server's slot position) to the server, press Restore Default Value.
Table 5-24. Boot Devices Boot Device Description PXE Boot from a Preboot Execution Environment (PXE) protocol on the network interface card. Hard Drive Boot from the hard drive on the server. Local CD/DVD Boot from a CD/DVD drive on the server. Virtual Floppy Boot from the virtual floppy drive. The floppy drive (or a floppy disk image) is on another computer on the management network, and is attached using the iDRAC GUI console viewer.
Viewing the Health Status of an Individual Server The health status for an individual server can be viewed in two ways: from the Chassis Graphics section on the Chassis Health page or the Server Status page. The Chassis Health page provides a graphical overview of an individual server installed in the chassis. To view health status for individual servers using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed.
The Server Status page (separate from the Servers Status page) provides an overview of the server and a launch point to the Web interface for the Integrated Dell Remote Access Controller (iDRAC), which is the firmware used to manage the server. NOTE: To use the iDRAC user interface, you must have an iDRAC user name and password. For more information about iDRAC and the using the iDRAC Web interface, see the Integrated Dell Remote Access Controller Firmware User’s Guide.
Table 5-25. Individual Server Status - Properties (continued) Item Health Description OK Displays that the server is present and communicating with CMC. In the event of a communication failure between CMC and the server, CMC cannot obtain or display health status for the server. Informational Displays information about the server when no change in health status (OK, Warning, Critical) has occurred. Warning Displays that only warning alerts have been issued, and corrective action must be taken.
Table 5-26. Individual Server Status - iDRAC System Event Log Item Description Severity OK Indicates a normal event that does not require corrective actions. Informational Indicates an informational entry on an event in which the Severity status has not changed. Unknown Indicates an unknown/uncategorized event. Warning Indicates a non-critical event for which corrective actions must be taken soon to avoid system failures.
Table 5-28. Individual Server Status - IPv4 iDRAC Network Settings Item Description Enabled Indicates if the IPv4 protocol is used on the LAN (Yes). If the server does not support IPv6, the IPv4 protocol is always enabled and this setting is not displayed. DHCP Enabled Indicates whether Dynamic Host Configuration Protocol (DHCP) is enabled (Yes) or disabled (No).
Table 5-30. Individual Server Status - WWN/MAC Address Item Description Slot Displays the slot(s) occupied by the server on the chassis. Location Displays the location occupied by the Input/Output modules. The six locations are identified by a combination of the group name (A, B, or C) and slot number (1 or 2). Location names are: A1, A2, B1, B2, C1, or C2. Fabric Displays the type of the I/O fabric.
To view health status of the IOMs using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status for the IOMs. IOM health status is indicated by the overlay of the IOM subgraphic: • No overlay - IOM is present, powered on and communicating with CMC; there is no indication of an adverse condition.
To view health status for all fans using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status of all fans. Fan health status is indicated by the overlay of the fan subgraphic: • No overlay - the fan is present and running; there is no indication of an adverse condition.
You can also view the Fan Status page by clicking the status link in the fan information Quick Links on the right side of the page. Table 5-31. Fans Health Status Information Item Description Name Displays the fan name in the format FAN-n, where n is the fan number. Present Indicates whether the fan unit is present (Yes or No). Health OK Indicates that the fan unit is present and communicating with CMC.
To view health status for the iKVM using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status of the iKVM. iKVM health status is indicated by the overlay of the iKVM subgraphic: • No overlay - iKVM is present, powered on and communicating with CMC; there is no indication of an adverse condition.
Viewing the Health Status of the PSUs The health status of the PSUs associated with the chassis can be viewed in two ways: from the Chassis Component Summary section on the Chassis Health page or the Power Supply Status page. The Chassis Health page provides a graphical overview of all PSUs installed in the chassis. To view health status for all PSUs using Chassis Graphics: 1 Log in to the CMC Web interface. The Chassis Health page is displayed.
You can also view the PSU Status page by clicking the status link in the PSU Quick Links on the right side of the chassis graphics. Table 5-32. Power Supply Health Status Information Item Description Name Displays the name of the PSU: PS-n, where n is the power supply number. Present Indicates whether the power supply is present (Yes or No). Health OK Indicates that the PSU is present and communicating with CMC. Indicates that the health of the PSU is OK.
Table 5-33. System Power Status (continued) Item Description Redundancy Displays the power supply redundancy status. Values include: No: Power Supplies are not redundant. Yes: Full Redundancy in effect. Viewing Status of the Temperature Sensors The Temperature Sensors Status page displays the status and readings of the temperature probes on the entire chassis (chassis and servers). NOTE: The temperature probes value cannot be edited.
Table 5-34. Temperature Sensors Health Status Information (continued) Item Description Warning Indicates that only warning alerts have been issued, and corrective action must be taken. If corrective actions are not taken, then critical or severe failures that can affect the integrity of the module may occur. Severe Indicates that one failure alert has been issued. Severe status represents a system failure on the module and corrective action must be taken immediately.
• Grayed Out - the LCD is present and not powered on. It is not communicating with CMC and there is no adverse condition. 2 Move the cursor over the LCD subgraphic. The corresponding text hint or screen tip, which provides additional information on the LCD is displayed. 3 Click the LCD subgraphic to select the LCD's information and display it to the right side of the chassis graphics.
WWN/MAC Addresses The WWN/MAC Address section displays the WWN/MAC information that is assigned to all servers, even if those server slots are currently empty. Location displays the location of the slot occupied by the Input/Output modules. The six slots are identified by a combination of the group name (A, B, or C) and slot number (1 or 2): slot names A1, A2, B1, B2, C1, or C2. iDRAC is the server's integrated management controller. Fabric displays the type of the I/O fabric.
3 Click the Network tab. The Network Configuration page appears. 4 Enable or disable DHCP for CMC by selecting or clearing the Use DHCP (For CMC Network Interface IP Address) check box. 5 If you disabled DHCP, type the IP address, gateway, and subnet mask. 6 Click Apply Changes at the bottom of the page. Configuring the Network LAN Settings NOTE: You must have Chassis Configuration Administrator privilege to set up CMC network settings.
Table 5-35. Network Settings Setting Description CMC MAC Address Displays the chassis’ MAC address, which is a unique identifier for the chassis over the computer network. Enable CMC Network Interface Enables the Network Interface of CMC. Default: Enabled. If this option is checked: • CMC communicates with and is accessible over the computer network. • The Web interface, CLI (remote RACADM), WSMAN, Telnet, and SSH associated with CMC are available.
Table 5-35. Network Settings (continued) Setting Description DNS CMC Name Displays the CMC name only when Register CMC on DNS is selected. The default CMC name is CMC_service_tag, where service tag is the service tag of the chassis, for example: CMC-00002. The maximum number of characters is 63. The first character must be a letter (a-z, A-Z), followed by an alphanumeric (a-z, A-Z, 0-9) or a hyphen (-) characters. Use DHCP for DNS Domain Name Uses the default DNS domain name.
Table 5-35. Network Settings (continued) Setting Description Network Speed Set the network speed to 100 Mbps or 10 Mbps to match your network environment. NOTE: The Network Speed setting must match your network configuration for effective network throughput. Setting the Network Speed lower than the speed of your network configuration increases bandwidth consumption and slows network communication. Determine whether your network supports the above network speeds and set it accordingly.
Table 5-36. IPv4 Settings Setting Description Enable IPv4 Allow CMC to use the IPv4 protocol to communicate on the network. Clearing this box does not prevent IPv6 networking from occurring. Default: Checked (enabled) DHCP Enable Enables CMC to request and obtain an IP address from the IPv4 Dynamic Host Configuration Protocol (DHCP) server automatically.
Table 5-36. IPv4 Settings (continued) Setting Description Static Gateway Specifies the IPv4 gateway for the CMC Network Interface. NOTE: The Static IP Address, Static Subnet Mask, and Static Gateway fields are active only if DHCP Enable (the property field preceding these fields) is disabled (unchecked). In that case, you must manually type the Static IP Address, Static Subnet Mask, and Static Gateway for CMC to use over the network.
Table 5-36. IPv4 Settings (continued) Setting Description Static Preferred DNS Server Specifies the static IP address for the preferred DNS Server. The Static Preferred DNS Server is implemented only when Use DHCP to Obtain DNS Server Addresses is disabled. Static Alternate DNS Server Specifies the static IP address for the alternate DNS Server. The Static Alternate DNS Server is implemented only when Use DHCP to obtain DNS Server addresses is disabled.
Table 5-37. IPv6 Settings Setting Description Enable IPv6 Allows CMC to use the IPv6 protocol to communicate on the network. Unchecking this box does not prevent IPv4 networking from occurring. Default: Checked (enabled) AutoConfiguration Enable Allows CMC to use the IPv6 protocol to obtain IPv6 related address and gateway settings from an IPv6 router configured to provide this information. CMC then has a unique IPv6 address on your network.
Table 5-37. IPv6 Settings (continued) Setting Description Static Preferred DNS Server Specifies the static IPv6 Address for the preferred DNS Server. The entry for Static Preferred DNS Server is considered only when Use DHCP to Obtain DNS Server Addresses is disabled or unchecked. There is an entry for this Server in both IPv4 and IPv6 configuration areas. Static Alternate DNS Specifies the static IPv6 Address for the alternate DNS Server Server.
Table 5-38. Network Security Page Settings (continued) Settings Description IP Range Mask Defines a specific range of IP addresses that can access the CMC, a process called IP range checking. IP range checking allows access to CMC only from clients or management stations whose IP addresses are within the user-specified range. All other logins are denied. For example: IP range mask: 255.255.255.0 (11111111.11111111.11111111.00000000) IP range address:192.168.0.255 (11000000.10101000.00000000.
Configuring VLAN VLANs are used to allow multiple virtual LANs to co-exist on the same physical network cable and to segregate the network traffic for security or load management purposes. When you enable the VLAN functionality, each network packet is assigned a VLAN tag. 1 Log in to the Web interface. 2 Click the Network tabVLAN subtab. The VLAN Tag Settings page displays. VLAN tags are chassis properties. They remain with the chassis even when a component is removed.
Adding and Configuring CMC Users To manage your system with CMC and maintain system security, create unique users with specific administrative permissions (or role-based authority). For additional security, you can also configure alerts that are e-mailed to specific users when a specific system event occurs. User Types There are two types of users: CMC users and iDRAC users. CMC users are also known as "chassis users." Since iDRAC resides on the server, iDRAC users are also known as "server users.
Table 5-40. User Types (continued) Privilege Description Chassis Configuration Administrator User can add or change data that: • Identifies the chassis, such as chassis name and chassis location • Is assigned specifically to the chassis, such as IP mode (static or DHCP), static IP address, static gateway, and static subnet mask • Provides services to the chassis, such as date and time, firmware update, and CMC reset. • Is associated with the chassis, such as slot name and slot priority.
Table 5-40. User Types (continued) Privilege Description Server Administrator This a blanket privilege granting a CMC user all rights to perform any operation on any servers present in the chassis. When a user with Server Administrator privilege issues an action to be performed on a server, the CMC firmware sends the command to the targeted server without checking the user's privileges on the server.
Table 5-40. User Types (continued) Privilege Description Server Administrator (continued) Server Configuration Administrator: • Set IP address • Set gateway • Set subnet mask • Set first boot device Configure Users: • Set iDRAC root password • iDRAC reset Server Control Administrator: • Power on • Power off • Power cycle • Graceful shutdown • Server Reboot Test Alert User User can send test alert messages. Debug Command Administrator User can execute system diagnostic commands.
The CMC user groups provide a series of user groups that have pre-assigned user privileges. NOTE: If you select Administrator, Power User, or Guest User, and then add or remove a privilege from the pre-defined set, the CMC Group automatically changes to Custom. . Table 5-41.
Table 5-41. CMC Group Privileges (continued) User Group Privileges Granted Custom Select any combination of the following permissions: • CMC Login User • Chassis Configuration Administrator • User Configuration Administrator • Clear Logs Administrator • Chassis Control Administrator (Power Commands) • Super User • Server Administrator • Test Alert User • Debug Command Administrator • Fabric A Administrator • Fabric B Administrator • Fabric C Administrator None Table 5-42. No assigned permissions.
Table 5-42.
Users can be logged in through Web interface, Telnet serial, SSH, and iKVM sessions. A maximum of 22 active sessions (Web interface, Telnet serial, SSH, and iKVM, in any combination) can be divided among users. NOTE: For added security, it is strongly recommended that you change the default password of the root (User 1) account. The root account is the default administrative account that ships with CMC. To change the default password for the root account, click User ID 1 to open the User Configuration page.
Table 5-43. General User Settings for Configuring a New or Existing CMC Username and Password (continued) Property Description User Name Sets or displays the unique CMC user name associated with the user. The user name can contain up to 16 characters. CMC user names cannot include forward slash (/) or period (.) characters. NOTE: If you change the user name, the new name does not appear in the user interface until your next login.
Configuring and Managing Microsoft Active Directory Certificates NOTE: To configure Active Directory settings for CMC, you must have Chassis Configuration Administrator privilege. NOTE: For more information about Active Directory configuration and how to configure Active Directory with Standard Schema or Extended Schema, see "Using the CMC Directory Service" on page 241. You can use the Microsoft Active Directory service to configure your software to provide access to CMC.
Table 5-44. Common Settings (continued) Field Description Enable Smart Card Enables Active Directory inter-operation based on the Kerberos Login Authentication supported by a Dell-supplied, auto-installed browser plug-in and Smart Card usage. To enable Smart Card, select the check box. To disable Smart Card, clear the check box. If you enable Smart Card, you must also configure your Microsoft Windows Client Workstation to correctly operate with Smart Card Reader functionality.
Table 5-44. Common Settings (continued) Field Description Enable SSL Certificate Validation Enables SSL certificate validation for CMC's Active Directory SSL connection. To disable the SSL certificate validation, clear the check box. Warning: Disabling this feature may expose the authentication to a man-in-the-middle attack. The browser operation requires that CMC be accessed through a HTTP URL which contains a fully qualified domain address for CMC, that is http://cmc-6g2wxf1.dom.net.
Table 5-44. Common Settings (continued) Field Description Enabling Smart Card enforces a Smart Card Only policy for browser authentication. All other methods of browser authentication such as Local or Active Directory username/password authentication are restricted. If the Smart Card Only usage enforcement policy is to be adopted, it is important that the Smart Card operation be fully validated before all other access methods to CMC are disabled.
Standard Schema Settings Displayed when Microsoft Active Directory (Standard Schema) is selected, this section presents the role groups with associated names, domains, and privileges for any role groups that have already been configured. To change the settings for a role group, click the role group button in the Role Groups list. NOTE: If you click a role group link prior to applying any new settings you have made, you lose those settings.
• CMC Domain Name - Displays the DNS name (string) of the domain where the Active Directory RAC Device Object resides. The CMC domain name must be a valid domain name consisting of x.y, where x is a 1-256 character ASCII string with no blank spaces between characters, and y is a valid domain type such as com, edu, gov, int, mil, net, or org. Managing Active Directory Certificates This sections displays the properties for the Active Directory certificate that was recently uploaded to the CMC.
Kerberos Keytab You can upload a Kerberos Keytab generated on the associated Active Directory Server. You can generate the Kerberos Keytab from the Active Directory Server by executing the ktpass.exe utility. This keytab establishes a trust relationship between the Active Directory Server and CMC. NOTE: CMC does not have a Kerberos Keytab for Active Directory. You must upload a currently generated Kerberos Keytab. See "Configuring Single Sign-On" on page 272 for detailed information.
The following configuration options are available. Table 5-45. Common Settings Setting Description Generic LDAP Enabled Enables the generic LDAP service on CMC. Use Distinguished Name to Search Group Membership Specifies the distinguished name (DN) of LDAP groups whose members are allowed access to the device. Enable SSL Certificate Validation If checked, CMC uses the CA certificate to validate the LDAP server certificate during SSL handshake.
Table 5-45. Common Settings (continued) Setting Description Network Timeout (seconds) Sets the time in seconds after which an idle LDAP session is automatically closed. Search Timeout (seconds) Sets the time in seconds after which a search is automatically closed. Selecting Your LDAP Servers You can configure the server to use with Generic LDAP in two ways. Static Servers allows the administrator to place a FQDN or IP address within the field.
Managing LDAP Group Settings The table in the Group Settings section lists role groups, displaying associated names, domains, and privileges for any role groups that are already configured. • To configure a new role group, click a role group name that does not have a name, domain, and privilege listed. • To change the settings for an existing role group, click the role group name. When you click a role group name, the Configure Role Group page appears.
Use the following controls to upload and download this certificate: • Upload - Initiates the upload process for the certificate. This certificate, which you obtain from your LDAP server, grants access to CMC. • Download - Initiates the download process. You are prompted for the location to save the file. When you select this option and click Next, a File Download dialog box appears. Use this dialog box to specify a location on your management station or shared network for the server certificate.
The CMC Web server includes a Dell self-signed SSL digital certificate (Server ID). To ensure high security over the Internet, replace the Web server SSL certificate by submitting a request to CMC to generate a new Certificate Signing Request (CSR). Certificate Signing Request (CSR) A CSR is a digital request to a certificate authority (referred to as a CA in the Web interface) for a secure server certificate.
Generating a New Certificate Signing Request To ensure security, it is strongly recommended that you obtain and upload a secure server certificate to CMC. Secure server certificates ensure the identity of a remote system and that information exchanged with the remote system cannot be viewed or changed by others. Without a secure server certificate, CMC is vulnerable to access from unauthorized users. Table 5-46.
To obtain a secure server certificate for CMC, you must submit a Certificate Signing Request (CSR) to a certificate authority of your choice. A CSR is a digital request for a signed, secure server certificate containing information about your organization and a unique, identifying key.
Table 5-47. Generate Certificate Signing Request (CSR) Page Options Field Description Common Name The exact name being certified (usually the Web server's domain name, for example, www.xyzcompany.com/). Valid: Alphanumeric characters (A–Z, a–z, 0–9); hyphens, underscores, and periods. Not valid: Non-alphanumeric characters not noted above (such as, but not limited to, @ # $ % & *); characters used primarily in non-English languages, such as ß, å, é, ü.
Table 5-47. Generate Certificate Signing Request (CSR) Page Options (continued) Field Description Country The country where the organization applying for certification is located. Email Your organization's e-mail address. You may type any e-mail address you want to have associated with the CSR. The e-mail address must be valid, containing the at (@) sign (example: name@xyzcompany.com). NOTE: This e-mail address is an optional field.
NOTE: CMC resets and becomes temporarily unavailable after the certificate has been uploaded successfully. To avoid disconnecting other users during a reset, notify authorized users who might log into CMC and check for active sessions in the Sessions page under the Network tab. Viewing a Server Certificate From the SSL Main Menu page, select View Server Certificate, and then click Next. The View Server Certificate page displays.
Table 5-49. Sessions Properties Property Description Session ID Displays the sequentially generated ID number for each instance of a login. Username Displays the user's login name (local user or Active Directory user). Examples of Active Directory user names are name@domain.com, domain.com/name, domain.com\name. IP Address Displays the user’s IP address. Session Type Describes the session type: Telnet, serial, SSH, Remote RACADM, SMASH CLP, WSMAN, or a GUI session.
To configure CMC services: 1 Log in to the CMC Web interface. 2 Click the Network tab. 3 Click the Services subtab. The Services page appears. 4 Configure the following services as required: • CMC serial console (Table 5-50) • Web server (Table 5-51) • SSH (Table 5-52) • Telnet (Table 5-53) • Remote RACADM (Table 5-54) • SNMP (Table 5-55) • Remote Syslog (Table 5-56) 5 Click Apply, and then update all default time outs and maximum time out limits Table 5-50.
Table 5-50. CMC Serial Console Settings (continued) Setting Description Idle Timeout Displays the number of seconds before an idle serial session is automatically disconnected. A change to the Timeout setting takes effect at the next login; it does not affect the current session. Timeout Range: 0 or 60 to 10800 seconds. To disable the Timeout feature, enter 0. Default: 1800 seconds Baud Rate Displays the data speed on the external serial port on the CMC.
Table 5-50. CMC Serial Console Settings (continued) Setting Description History Size Buffer Displays the maximum size of the serial history buffer, which holds the last characters written to the Serial Console. Default: 8192 characters Login Command Specifies the serial command that is automatically executed when a user logs into the CMC Serial Console interface. Example: connect server-1 Default: [Null] Table 5-51.
Table 5-51. Web Server Settings (continued) Setting Description Idle Timeout Displays the number of seconds before an idle Web user interface session is automatically disconnected. A change to the Timeout setting takes effect at the next login; it does not affect the current session. Timeout range: 60 to 10800 seconds. Default: 1800 seconds HTTP Port Number Displays the default port used by CMC that listens for a server connection.
Table 5-52. SSH Settings Setting Description Enabled Enables the SSH on CMC. Default: Checked (enabled) Max Sessions The maximum number of simultaneous SSH sessions allowed for the chassis. A change to this property takes effect at the next login; it does not affect current Active Sessions (including your own).
Table 5-53. Telnet Settings Setting Description Enabled Enables Telnet console interface on CMC. Default: Unchecked (disabled) Max Sessions Displays the maximum number of simultaneous Telnet sessions allowed for the chassis. A change to this property takes effect at the next login; it does not affect current Active Sessions (including your own).
Table 5-54. Remote RACADM Settings Setting Description Enabled Enables the remote RACADM utility access to CMC. Default: Checked (enabled) Max Sessions Displays the maximum number of simultaneous RACADM sessions allowed for the chassis. A change to this property takes effect at the next login; it does not affect current Active Sessions (including your own).
Table 5-56. Remote Syslog Configuration Setting Description Enabled Enables the transmission and remote capture of CMC log and Hardware log entries to the specified server(s). Valid values: Checked (enabled), unchecked (disabled) Default: unchecked (disabled) Syslog Server 1 The first of three possible servers to host a copy of the CMC and hardware log entries. Specified as a Host Name, an IPv6 address, or an IPv4 address.
Managing Firmware Updates This section describes how to use the Web interface to update firmware. The following Chassis components can be updated using the GUI or RACADM commands: • CMC — active and standby • iKVM • iDRAC • IOM infrastructure devices When you update firmware, there is a recommended process to follow that can prevent a loss of service if the update fails. See "Installing or Updating the CMC Firmware" on page 49 for guidelines to follow before you use the instructions in this section.
To view the updatable server components: 1 Log in to the Web interface. For more information, see "Accessing the CMC Web Interface" on page 103. 2 Click Server Overview in the system tree. 3 Click the Update tab. The Server Component Update appears. Updating Firmware NOTE: To update firmware on CMC, you must have Chassis Configuration Administrator privilege. NOTE: The firmware update retains the current CMC and iKVM settings.
run the updated image, only the standby CMC has that image. In general, it is highly recommended to maintain identical firmware versions for the active and standby CMCs. NOTE: To avoid disconnecting other users during a reset, notify authorized users who might log in to CMC and check for active sessions in the Sessions page. To open the Sessions page, select Chassis in the tree, click the Network tab, and then click the Sessions subtab.
• Update status displays in the Update State field; this field is automatically updated during the file transfer process. NOTE: The update may take several minutes for CMC. 5 For a standby CMC, when the update is complete the Update State field displays "Done". For an active CMC, during the final phases of the firmware update process, the browser session and connection with CMC is lost temporarily as the active CMC is taken offline.
• Do not use the Refresh button or navigate to another page during the file transfer. • To cancel the process, click Cancel File Transfer and Update - this option is available only during file transfer. • Update status displays in the Update State field; this field is automatically updated during the file transfer process. NOTE: The update may take up to two minutes for the iKVM. When the update is complete, iKVM resets and the new firmware is displayed on the Firmware Update page.
based on connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer displays. Additional instructions to follow: • Do not use the Refresh button or navigate to another page during the file transfer. • Update status displays in the Update State field; this field is automatically updated during the file transfer process. NOTE: No file transfer timer is displayed when updating IOMINF firmware.
• To cancel the process, click Cancel File Transfer and Update - this option is available only during file transfer. • Update status displays in the Update State field; this field is automatically updated during the file transfer process. NOTE: The update may take several minutes for CMC or Server.
• To cancel the process, click Cancel File Transfer and Update - this option is available only during file transfer. • Update status displays in the Update State field; this field is automatically updated during the file transfer process. NOTE: It can take up to ten minutes to update the iDRAC firmware. Managing iDRAC CMC provides the Deploy iDRAC page to allow the user to configure installed and newly inserted server's iDRAC network configuration settings.
Table 5-57. QuickDeploy Settings Setting Description QuickDeploy Enabled Enables/disables the QuickDeploy feature that automatically applies the iDRAC settings configured on this page to newly inserted servers; the auto configuration must be confirmed locally on the LCD panel. NOTE: This includes the root user password if the Set iDRAC Root Password on Server Insertion box is checked.
Table 5-57. QuickDeploy Settings (continued) Setting Description Starting iDRAC IPv4 Address (Slot 1) Specifies the static IP address of the iDRAC of the server in slot 1 of the enclosure. The IP address of each subsequent iDRAC is incremented by 1 for each slot from slot 1's static IP address. In the case where the IP address plus the slot number is greater than the subnet mask, an error message is displayed. NOTE: The subnet mask and the gateway are not incremented like the IP address.
6 To update the table to the last saved QuickDeploy settings, and restore the iDRAC Network settings to the current values for each installed server, click Refresh. NOTE: Clicking the Refresh button deletes all iDRAC QuickDeploy and iDRAC Network configuration settings that have not been saved. The QuickDeploy feature only executes when it is enabled, and a server is inserted in the chassis.
iDRAC Network Settings The iDRAC Network Settings section of the Deploy iDRAC page contains a table listing all installed server’s iDRAC IPv4 and IPv6 network configuration settings. Using this table you can configure the iDRAC network configurations settings for each installed server. The initial values displayed for each of the fields are the current values read from the iDRAC. Changing a field and clicking Apply iDRAC Network Settings saves the changed field to the iDRAC.
Table 5-58. iDRAC Network Settings (continued) Setting Description Change Root Password Enables (when checked) the ability to change the password of the iDRAC root user. The iDRAC Root Password and Confirm iDRAC Root Password fields must be provided for this operation to be successful. DHCP If selected DHCP is used to acquire the iDRAC IP address, subnet mask and default gateway, otherwise the values defined in the iDRAC network configuration fields are used.
6 To deploy the setting to iDRAC, click Apply iDRAC Network Settings button. If you made changes to the QuickDeploy settings, they are also saved. 7 To restore the iDRAC Network settings to the current values for each installed server, and update the QuickDeploy table to the last saved QuickDeploy settings click Refresh. NOTE: Clicking Refresh button deletes all iDRAC QuickDeploy and iDRAC Network configuration settings that have not been saved.
The remote console feature is supported only when all of the following conditions are met: • The chassis power is on. • Server is PowerEdge M610, M610X, M710, M710HD, or M910. • The LAN interface on the server is enabled. • The iDRAC version is 2.20 or later. • The host system is installed with JRE (Java Runtime Environment) 6 Update 16 or later. • The browser on host system allows pop-up windows (pop-up blocking is disabled). NOTE: Remote Console can also be launched from the iDRAC GUI.
A user may be able to launch iDRAC GUI without having to login a second time, as this feature utilizes single sign-on. Single sign-on policies are described below. • A CMC user who has server administrative privilege, is automatically logged into iDRAC using single sign-on. Once on the iDRAC site, this user is automatically granted Administrator privileges. This is true even if the same user does not have an account on iDRAC, or if the account does not have the Administrator’s privileges.
FlexAddress This section describes the FlexAddress Web interface screens. FlexAddress is an optional upgrade that allows server modules to replace the factoryassigned WWN/MAC ID with a WWN/MAC ID provided by the chassis. NOTE: You must purchase and install the FlexAddress upgrade to have access to the configuration screens. If the upgrade has not been purchased and installed, the following text is displayed on the Web interface: Optional feature not installed.
To view whether FlexAddress is active for the chassis: 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 103). 2 Click Chassis Overview in the system tree. 3 Click the Setup tab. The General Setup page appears. The FlexAddress entry has a value of Active or Not Active; a value of active means that the feature is installed on the chassis. A value of not active means that the feature is not installed and not in use on the chassis.
Viewing Server FlexAddress Status FlexAddress status information can also be displayed for each individual server. The server level information displays a FlexAddress status overview for that server. To view FlexAddress server information: 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 103). 2 Expand Server Overview in the system tree. All of the servers (1–16) appear in the expanded Servers list. 3 Click the server you want to view. The Server Status page displays.
Table 5-59. Status Page Information Health OK Indicates that FlexAddress is present and providing status to CMC. In the event of a communication failure between CMC and FlexAddress, CMC cannot obtain or display health status for FlexAddress. Informational Displays information about FlexAddress when no change in health status (OK, Warning, Critical) has occurred. Warning Indicates that only warning alerts have been issued, and corrective action must be taken.
Configuring FlexAddress If you purchase FlexAddress with your chassis, is installed and active when you power up your system. If you purchase FlexAddress separately, you must install the SD feature card using the instructions in the Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification document. See support.dell.com/manuals for this document. The server must be off before you begin configuration. You can enable or disable FlexAddress on a per fabric basis.
NOTE: If no fabrics are selected, FlexAddress is not be enabled for the selected slots. The Select Slots for Chassis-Assigned WWN/MACs page displays an Enabled check box for each slot in the chassis (1 - 16). 6 Click the Enabled check box for each slot you want to enable FlexAddress on. If you want to select all slots, use the Select/Deselect All check box. To disable a slot, click the Enabled check box to clear the selection.
Remote File Sharing The Remote Virtual Media File Share option maps a file from a share drive on the network to one or more servers through CMC to deploy or update an operating system. When connected, the remote file is accessible as if it is on the local system. Two types of media are supported: floppy drives and CD/DVD drives. 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 103). 2 Click Server Overview in the system tree.
Table 5-60. Remote File Sharing Settings (continued) Setting Description Slot Identifies the location of the slot. Slot numbers are sequential from 1 to 16 (for the 16 available slots in the chassis). Name Displays the name of the slot. Slots are named depending on their position in the chassis. Model Displays the model name of the server. Power State Displays the power status of the server: N/A – CMC has not yet determined the power state of the server.
Frequently Asked Questions Table 5-61 lists the frequently asked questions while managing or recovering a remote system. . Table 5-61. Managing and Recovering a Remote System Question Answer When accessing the CMC Web interface, I get a security warning stating the host name of the SSL certificate does not match the host name of CMC. CMC includes a default CMC server certificate to ensure network security for the Web interface and remote RACADM features.
Table 5-61. Managing and Recovering a Remote System (continued) Question Answer Why are the remote RACADM and Web-based services unavailable after a property change? It may take a minute for the remote RACADM services and the Web interface to become available after the CMC Web server resets.
Table 5-61. Managing and Recovering a Remote System (continued) Question Answer The following message is displayed for unknown reasons: As part of discovery, IT Assistant attempts to verify the device’s get and set community names. In IT Assistant, you have the get community name = public and the set community name = private. By default, the community name for the CMC agent is public.
Using the CMC Web Interface
6 Using FlexAddress The FlexAddress feature is an optional upgrade that allows server modules to replace the factory-assigned World Wide Name and Media Access Control (WWN/MAC) network IDs with WWN/MAC IDs provided by the chassis. Every server module is assigned unique WWN and/or MAC IDs as part of the manufacturing process.
Activating FlexAddress FlexAddress is delivered on a Secure Digital (SD) card that must be inserted into CMC to activate the feature. To activate the FlexAddress feature, software updates may be required; if you are not activating FlexAddress these updates are not required. The updates, which are listed in the table below, include server module BIOS, I/O mezzanine BIOS or firmware, and CMC firmware. You must apply these updates before you enable FlexAddress.
NOTE: Any system ordered after June 2008 has the correct firmware versions. To ensure proper deployment of the FlexAddress feature, update the BIOS and the firmware in the following order: 1 Update all mezzanine card firmware and BIOS. 2 Update server module BIOS. 3 Update iDRAC firmware on the server module. 4 Update all CMC firmware in the chassis; if redundant CMCs are present, ensure both are updated.
Verifying FlexAddress Activation To ensure proper activation of FlexAddress, RACADM commands can be used to verify the SD feature card and FlexAddress activation. Use the following RACADM command to verify the SD feature card and its status: racadm featurecard -s Table 6-1. Status Messages Returned by featurecard -s Command Status Message Actions No feature card inserted. Check CMC to verify that the SD card was properly inserted.
The command returns the following status message: Feature = FlexAddress Date Activated = 8 April 2008 - 10:39:40 Feature installed from SD-card SN = 01122334455 If there are no active features on the chassis, the command returns a message: racadm feature -s No features active on the chassis. Dell Feature Cards may contain more than one feature.
Deactivating FlexAddress Use the following RACADM command to deactivate the FlexAddress feature and restore the SD card: racadm feature -d -c flexaddress The command returns the following status message upon successful deactivation: feature FlexAddress is deactivated on the chassis successfully.
= 0 or 1 Where 0 is disable and 1 is enable. Use the following RACADM command to enable or disable slots: racadm setflexaddr [-i ] = 1 to 16 = 0 or 1 Where 0 is disable and 1 is enable. For additional information on the command, see the setflexaddr command section of the Command Line Reference Guide for iDRAC6 and CMC.
Use the following RACADM command to display FlexAddress status for the entire chassis: racadm getflexaddr To display FlexAddress status for a particular slot: racadm getflexaddr [-i ] = 1 to 16 See "Configuring FlexAddress Using the CLI" on page 222 for additional details on FlexAddress configuration. For additional information on the command, see the getflexaddr command section of the Command Line Reference Guide for iDRAC6 and CMC.
The Web interface displays an error that states: This feature card was activated with a different chassis. It must be removed before accessing the FlexAddress feature.
The original feature card is no longer eligible for deactivation on that or any other chassis, unless Dell Service re-programs the original chassis service tag back into a chassis, and CMC that has the original feature card is made active on that chassis. • The FlexAddress feature remains activated on the originally bound chassis. The binding of that chassis feature is updated to reflect the new service tag.
9 What happens if a chassis with a single CMC is downgraded with firmware prior to 1.10? • The FlexAddress feature and configuration is removed from the chassis. • The feature card used to activate the feature on this chassis is unchanged, and remains bound to the chassis. When this chassis’s CMC firmware is subsequently upgraded to 1.
12 I have the SD card properly installed and all the firmware/software updates installed. I see that FlexAddress is active, but I can’t see anything on the server deployment screen to deploy it? What is wrong? This is a browser caching issue; shut down the browser and relaunch. 13 What happens to FlexAddress if I need to reset my chassis configuration using the RACADM command, racresetcfg? The FlexAddress feature is still be activated and ready to use. All fabrics and slots is selected as default.
Table 6-2. FlexAddress Commands and Output (continued) Situation Command SD card in the active $racadm featurecard -s CMC module that is bound to the same service tag. Output The feature card inserted is valid and contains the following feature(s) FlexAddress: The feature card is bound to this chassis SD card in the active $racadm featurecard -s CMC module that is not bound to any service tag.
Table 6-2.
FlexAddress DELL SOFTWARE LICENSE AGREEMENT This is a legal agreement between you, the user, and Dell Products L.P. or Dell Global B.V. ("Dell"). This agreement covers all software that is distributed with the Dell product, for which there is no separate license agreement between you and the manufacturer or owner of the software (collectively the "Software"). This agreement is not for the sale of Software or any other intellectual property.
The Software is protected by United States copyright laws and international treaties. You may make one copy of the Software solely for backup or archival purposes or transfer it to a single hard disk provided you keep the original solely for backup or archival purposes.
AND ALL ACCOMPANYING WRITTEN MATERIALS. This limited warranty gives you specific legal rights; you may have others, which vary from jurisdiction to jurisdiction. IN NO EVENT SHALL DELL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF USE OR INABILITY TO USE THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
documentation with only those rights set forth herein. Contractor/manufacturer is Dell Products, L.P., One Dell Way, Round Rock, Texas 78682. GENERAL This license is effective until terminated. It terminates upon the conditions set forth above or if you fail to comply with any of its terms. Upon termination, you agree that the Software and accompanying materials, and all copies thereof, is destroyed. This agreement is governed by the laws of the State of Texas. Each provision of this agreement is severable.
Using FlexAddress Plus 7 The FlexAddress Plus is a new feature added to the feature card version 2.0. It is an upgrade from FlexAddress feature card version 1.0. FlexAddress Plus contains more MAC addresses than the FlexAddress feature. Both features allow the chassis to assign WWN/MAC (World Wide Name/Media Access Control) addresses to Fibre Channel and Ethernet devices. Chassis assigned WWN/MAC addresses are globally unique and specific to a server slot.
FlexAddress vs FlexAddress Plus FlexAddress has 208 addresses divided into 16 server slots, thus each slot is allocated with 13 MACs. FlexAddress Plus has 2928 addresses divided into 16 server slots, thus each slot is allocated with 183 MACs. The table below shows the provision of the MAC addresses in both the features. Fabric A Fabric B Fabric C iDRAC Management Total MACs FlexAddress 4 4 4 1 13 FlexAddress 60 Plus 60 60 3 183 Figure 7-1.
Scheme 1 and Scheme 2 MAC Address Allocation For backward compatibility with FA, the addresses in FA+ are divided into two groups: the first group has 208 addresses and the second group has 2928 addresses. In the first group, 13 MACs are allocated to each of the 16 slots in the same way FA does. In the second group, 183 MACs are allocated for each slot. The allocation of the 13 MAC addresses of the first group for each server is divided as: one for iDRAC and four for each fabric, A, B, and C.
If a chassis currently has FA activated, FA does not need to be deactivated in order to add FA+. In this case, the MAC address allocations are applied as follows: • The MAC addresses of scheme 1 are allocated from FA of the feature card 1.0. There is no change in the previous WWN/MAC configuration. • The additional MAC addresses of scheme 2 are allocated from the scheme 2 addresses of FA+.
Fabric A port 2: 00:FA:AE:58:59:2E (from FA) 00:FA:AE:58:59:2F (from FA) 00:FB:AE:58:5A:00 (from FA+) 00:FB:AE:58:5A:01 (from FA+) Fabric B port 1: 00:FA:AE:58:59:30 (from FA) 00:FA:AE:58:59:31 (from FA) Fabric B port 2: 00:FA:AE:58:59:32 (from FA) 00:FA:AE:58:59:33 (from FA) Fabric C port 1: 00:FA:AE:58:59:34 (from FA) 00:FA:AE:58:59:35 (from FA) Fabric C port 2: 00:FA:AE:58:59:36 (from FA) 00:FA:AE:58:59:37 (from FA) When a chassis with no previous FA—either it has never been activated or it was
Fabric B port 2: 00:FB:AE:58:59:32 (FA) 00:FB:AE:58:59:33 (FA) Fabric C port 1: 00:FB:AE:58:59:34 (FA) 00:FB:AE:58:59:35 (FA) Fabric C port 2: 00:FB:AE:58:59:36 (FA) 00:FB:AE:58:59:37 (FA) 240 Using FlexAddress Plus
8 Using the CMC Directory Service A directory service maintains a common database of all information needed for controlling network users, computers, printers, and so on. If your company uses the Microsoft Active Directory service software or the LDAP Directory Service software, you can configure CMC to use directory based user authentication.
Standard Schema Active Directory Overview Using standard schema for Active Directory integration requires configuration on both Active Directory and CMC. On the Active Directory side, a standard group object is used as a role group. A user who has CMC access is a member of the role group. In order to give this user access to a specific CMC card, the role group name and its domain name need to be configured on the specific CMC card.
Table 8-1.
NOTE: The bit mask values are used only when setting Standard Schema with the RACADM. NOTE: For more information about user privileges, see "User Types" on page 154. There are two ways to enable Standard Schema Active Directory: • With the CMC Web interface. See "Configuring CMC With Standard Schema Active Directory and Web Interface" on page 244. • With the RACADM CLI tool. See "Configuring CMC With Standard Schema Active Directory and RACADM" on page 247.
5 In the Common Settings section: a Select the Enable Active Directory check box. b Type the Root Domain Name. NOTE: The Root domain name must be a valid domain name using the x.y naming convention, where x is a 1–256 character ASCII string with no spaces between characters, and y is a valid domain type such as com, edu, gov, int, mil, net, or org. c Type the Timeout in seconds. Timeout range is 15–300 seconds. Default timeout period is 90 seconds.
14 Upload your domain forest Root certificate authority-signed certificate into CMC. In the Certificate Management section, type the file path of the certificate or browse to the certificate file. Click the Upload button to transfer the file to CMC. NOTE: The File Path value displays the relative file path of the certificate you are uploading. You must type the absolute file path, which includes the full path and the complete file name and file extension.
Configuring CMC With Standard Schema Active Directory and RACADM To configure the CMC Active Directory Feature with Standard Schema using the RACADM CLI, use the following commands: 1 Open a serial/Telnet/SSH text console to the CMC, and type: racadm config -g cfgActiveDirectory -o cfgADEnable 1 racadm config -g cfgActiveDirectory -o cfgADType 2 racadm config -g cfgActiveDirectory -o cfgADRootDomain racadm config -g cfgStandardSchema -i -o cfgSSADRoleGroupName
2 Specify a DNS server using one of the following options: • If DHCP is enabled on CMC and you want to use the DNS address obtained automatically by the DHCP server, type the following command: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1 • If DHCP is disabled on CMC or you want manually to input your DNS IP address, type the following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm c
You can extend the Active Directory database by adding your own unique Attributes and Classes to address your company’s environment-specific needs. Dell has extended the schema to include the necessary changes to support remote management Authentication and Authorization. Each Attribute or Class that is added to an existing Active Directory Schema must be defined with a unique ID. To maintain unique IDs across the industry, Microsoft maintains a database of Active Directory Object Identifiers (OIDs).
The RAC Device object is the link to the RAC firmware for querying Active Directory for authentication and authorization. When a RAC is added to the network, the Administrator must configure the RAC and its device object with its Active Directory name so users can perform authentication and authorization with Active Directory. Additionally, the Administrator must add the RAC to at least one Association Object in order for users to authenticate.
The Association Object allows for as many or as few users and/or groups as well as RAC Device Objects. However, the Association Object only includes one Privilege Object per Association Object. The Association Object connects the "Users" who have "Privileges" on the RACs (CMCs). Additionally, you can configure Active Directory objects in a single domain or in multiple domains. For example, you have two CMCs (RAC1 and RAC2) and three existing Active Directory users (user1, user2, and user3).
To configure the objects for the single domain scenario: 1 Create two Association Objects. 2 Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs. 3 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privilege. 4 Group user1 and user2 into Group1. 5 Add Group1 as Members in Association Object 1 (A01), Priv1 as Privilege Objects in A01, and RAC1, RAC2 as RAC Devices in A01.
Figure 8-4. Setting Up Active Directory Objects in Multiple Domains Domain1 Domain2 AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 To configure the objects for the multiple domain scenario: 1 Ensure that the domain forest function is in Native or Windows 2003 mode. 2 Create two Association Objects, A01 (of Universal scope) and A02, in any domain. Figure 8-4 shows the objects in Domain2. 3 Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs.
6 Add Group1 as Members in Association Object 1 (A01), Priv1 as Privilege Objects in A01, and RAC1, RAC2 as RAC Devices in A01. 7 Add User3 as Members in Association Object 2 (A02), Priv2 as Privilege Objects in A02, and RAC2 as RAC Devices in A02. Configuring Extended Schema Active Directory to Access Your CMC Before using Active Directory to access your CMC, configure the Active Directory software and CMC: 1 Extend the Active Directory schema (see "Extending the Active Directory Schema" on page 254).
You can extend your schema using one of the following methods: • Dell Schema Extender utility • LDIF script file If you use the LDIF script file, the Dell organizational unit is not be added to the schema.
4 Click Next to run the Dell Schema Extender. 5 Click Finish. The schema is extended. To verify the schema extension, use the Microsoft Management Console (MMC) and the Active Directory Schema Snap-In to verify that the following exist: • Classes — see Table 8-2 through Table 8-7 • Attributes — see Table 8-8 See your Microsoft documentation for more information on how to enable and use the Active Directory Schema Snap-In the MMC. Table 8-2.
Table 8-4. dellAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.1.1.2 Description Represents the Dell Association Object. The Association Object provides the connection between the users and the devices. Class Type Structural Class SuperClasses Group Attributes dellProductMembers dellPrivilegeMember Table 8-5. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines Authorization Rights (privileges) for the CMC device.
Table 8-6. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description Container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges Table 8-7. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description The main class from which all Dell products are derived. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 8-8.
Table 8-8. List of Attributes Added to the Active Directory Schema (continued) Assigned OID/Syntax Object Identifier Single Valued Attribute: dellIsCardConfigAdmin Description: TRUE if the user has Card Configuration rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.4 TRUE Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: dellIsLoginUser Description: TRUE if the user has Login rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.3 TRUE Boolean (LDAPTYPE_BOOLEAN 1.3.
Table 8-8. List of Attributes Added to the Active Directory Schema (continued) Assigned OID/Syntax Object Identifier Single Valued Attribute: dellIsTestAlertUser Description: TRUE if the user has Test Alert User rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.10 TRUE Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: dellIsDebugCommandAdmin Description: TRUE if the user has Debug Command Admin rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.
Table 8-8. List of Attributes Added to the Active Directory Schema (continued) Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.6.2.1 Integer (LDAPTYPE_INTEGER) Attribute: dellPermissionsMask2 OID: 1.2.840.113556.1.8000.1280.1.6.2.
The Microsoft Management Console (MMC) appears. 2 In the Console 1 window, click File (or Console on systems running Windows 2000). 3 Click Add/Remove Snap-in. 4 Select the Active Directory Users and Computers Snap-In and click Add. 5 Click Close and click OK. Adding CMC Users and Privileges to Active Directory Using the Dell-extended Active Directory Users and Computers Snap-In, you can add CMC users and privileges by creating RAC, Association, and Privilege objects.
3 Type a name for the new object. 4 Select Privilege Object. 5 Click OK. 6 Right-click the privilege object that you created, and select Properties. 7 Click the RAC Privileges tab and select the privileges that you want the user to have. For more information about CMC user privileges, see "User Types" on page 154. Creating an Association Object The Association Object is derived from a Group and must contain a Group Type. The Association Scope specifies the Security Group Type for the Association Object.
2 Select the Users tab and click Add. 3 Type the user or User Group name and click OK. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a RAC device. Only one privilege object can be added to an Association Object. Adding Privileges 1 Select the Privileges Object tab and click Add. 2 Type the Privilege Object name and click OK. Click the Products tab to add one or more RAC devices to the association.
NOTE: The Root domain name must be a valid domain name using the x.y naming convention, where x is a 1–256 character ASCII string with no spaces between characters, and y is a valid domain type such as com, edu, gov, int, mil, net, or org. c Type the Timeout time in seconds. Configuration range: 15–300 seconds.
NOTE: You must apply your settings before continuing to the next step, in which you navigate to another page. If you do not apply the settings, you lose the settings you entered when you navigate to the next page. 9 In the Manage Certificates section, type the file path of the certificate in the text field, or click Browse to select the certificate file. Click the Upload button to transfer the file to CMC. NOTE: The File Path value displays the relative file path of the certificate you are uploading.
• Manually configure a DNS server IP address by leaving the Use DHCP to Obtain DNS Server Addresses check box unchecked and then typing your primary and alternate DNS server IP addresses in the fields provided. 14 Click Apply Changes. The CMC Extended Schema Active Directory feature configuration is complete.
NOTE: When you use the Specify Server option, the host name in the certificate authority-signed certificate is not matched against the name of the specified server. This is particularly useful if you are a CMC administrator, because it enables you to enter a host name as well as an IP address. After you enable the Specify Server option, you can specify an LDAP server and global catalog with IP addresses or fully qualified domain names (FQDNs) of the servers.
racadm config -g cfgLanNetworking -o cfgDNSServer2 The Extended Schema feature configuration is complete. Frequently Asked Questions Table 8-9. Using CMC With Active Directory: Frequently Asked Questions Question Answer Can I log into CMC using Active Directory across multiple trees? Yes. The CMC’s Active Directory querying algorithm supports multiple trees in a single forest.
Table 8-9. Using CMC With Active Directory: Frequently Asked Questions (continued) Question Answer I created and uploaded a new RAC certificate and now the Web interface does not launch. If you use Microsoft Certificate Services to generate the RAC certificate, you may have inadvertently chose User Certificate instead of Web Certificate when creating the certificate.
Table 8-9. Using CMC With Active Directory: Frequently Asked Questions (continued) Question What can I do if I cannot log into CMC using Active Directory authentication? How do I troubleshoot the issue? Answer 1 Ensure that you use the correct user domain name during a login and not the NetBIOS name. 2 If you have a local CMC user account, log into CMC using your local credentials.
Configuring Single Sign-On Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows 7, and Windows Server 2008 can use Kerberos, a network authentication protocol, as an authentication method allowing users who have signed in to the domain an automatic or single sign-on to subsequent applications such as Exchange. Starting with CMC version 2.10, CMC can use Kerberos to support two additional types of login mechanisms—single sign-on and Smart Card login.
Client Systems • For only Smart Card login, the client system must have the Microsoft Visual C++ 2005 redistributable. For more information see www.microsoft.com/downloads/details.aspx?FamilyID= 32BC1BEEA3F9-4C13-9C99-220B62A191EE&displaylang=en • For Single Sign-On and Smart Card login, the client system must be a part of the Active Directory domain and Kerberos Realm. CMC • CMC must have firmware version 2.
Run the ktpass utility—part of Microsoft Windows—on the domain controller (Active Directory server) where you want to map CMC to a user account in Active Directory. For example, C:\>ktpass -princ HTTP/cmcname.domain_name.com@REALM_NAME.COM -mapuser dracname -crypto DES-CBC-MD5 -ptype KRB5_NT_PRINCIPAL -pass * -out c:\krbkeytab NOTE: The cmcname.domainname.com must be lower case as required by RFC and the REALM name, @REALM_NAME must be uppercase.
To upload the keytab file: 1 Navigate to the User Authentication tab Directory Services subtab. Ensure that Microsoft Active Directory Standard or Extended Schema is selected. If not, select your preference and click Apply. 2 Click Browse on the Kerberos Keytab Upload section, navigate to the folder where the keytab file is saved and click Upload. When the upload is complete, a message box is displayed indicating a successful or failed upload.
Configuring the Browser For Single Sign-On Login Single Sign-on is supported on Internet Explorer versions 6.0 and later and Firefox versions 3.0 and later. NOTE: The following instructions are applicable only if CMC uses Single Sign-On with Kerberos authentication. Internet Explorer 1 In the Internet Explorer, select ToolsInternet Options. 2 On the Security tab, under Select a zone to view or change security settings, select Local Intranet. 3 Click Sites. The Local Intranet dialog box is displayed.
Logging into CMC Using Single Sign-On NOTE: You cannot use the IP address to log into the Single Sign-On or Smart Card login. Kerberos validates your credentials against the Fully Qualified Domain Name (FQDN). 1 Log into the client system using your network account. 2 Access the CMC Web page using https:// For example, cmc-6G2WXF1.cmcad.lab where cmc-6G2WXF1 is the cmc-name cmcad.lab is the domain-name.
Configuring Smart Card Two-Factor Authentication Traditional authentication schemes use user name and password to authenticate users. Two-factor-authentication, on the other hand, provides a higher-level of security by requiring users to have a password or PIN and a physical card containing a private key or digital certificate. Kerberos, a network authentication protocol, uses this two-factor authentication mechanism allowing systems to prove their authenticity.
Configuring Active Directory 1 Set up Kerberos realm & Key Distribution Center (KDC) for Active Directory, if not already configured (ksetup). NOTE: Ensure a robust NTP and DNS infrastructure to avoid issues with clock drift & reverse lookup. 2 Create Active Directory users for each CMC, configured to use Kerberos DES encryption but not pre-authentication. 3 Register the CMC users to the Key Distribution Center with Ktpass (this also outputs a key to upload to CMC).
Enabling Smart Card Authentication 1 Navigate to the User Authentication tab Directory Services subtab. Ensure that Microsoft Active Directory Standard or Extended Schema is selected. 2 In the Common Settings Section, select: • Smart Card — this option requires that you insert a Smart Card into reader and enter the PIN number. NOTE: All command line out-of-band interfaces including secure shell (SSH), Telnet, Serial, and remote RACADM remain unchanged for this option.
Logging into CMC Using Smart Card NOTE: You cannot use the IP address to log into the Single Sign-On or Smart Card login. Kerberos validates your credentials against the Fully Qualified Domain Name (FQDN). 1 Log into the client system using your network account. 2 Access the CMC Web page using https:// For example, cmc-6G2WXF1.cmcad.lab where cmc-6G2WXF1 is the cmc-name cmcad.lab is the domain-name.
(Ctrl-Alt-Del) screen and check to see if Windows detects the Smart Card and displays the PIN dialog-box. Incorrect Smart Card PIN Check to see if the Smart Card has been locked out due to too many attempts with an incorrect PIN. In such cases, the issuer of the Smart Card in the organization is able to help you get a new Smart Card. Unable to Log into CMC as an Active Directory User If you cannot log into CMC as an Active Directory user, try logging into CMC without enabling the Smart Card logon.
Figure 8-5. Configuration of CMC with Generic LDAP Configuration on Generic LDAP Side Role Group Configuration on CMC Side Role Group Name and Domain Name Role Definition User Configuring the Generic LDAP Directory to Access CMC The CMC's Generic LDAP implementation uses two phases in granting access to a user. Phase 1 begins with user authentication, followed by phase 2 for user authorization.
4 Unbind and perform a bind with the user's DN and password. 5 If the bind fails, then the login fails. If these steps succeed then the user is considered authenticated. The next phase is authorization. CMC stores a maximum of 5 groups and their corresponding privileges. A user has the option to be added to multiple groups within the directory service. If the user is a member of multiple groups, then the user obtains the privileges of all their groups.
Table 8-10. Common Settings Setting Description Generic LDAP Enabled Enables the generic LDAP service on CMC. Use Distinguished Name to Search Group Membership Specifies the distinguished name (DN) of LDAP groups whose members are allowed access to the device. Enable SSL Certificate Validation If checked, CMC uses the CA certificate to validate the LDAP server certificate during SSL handshake.
Table 8-10. Common Settings (continued) Setting Description Network Timeout (seconds) Sets the time in seconds after which an idle LDAP session is automatically closed. Search Timeout (seconds) Sets the time in seconds after which a search is automatically closed. Selecting Your LDAP Servers You can configure the server to use with Generic LDAP in two ways. Static Servers allows the administrator to place a FQDN or IP address within the field.
Managing LDAP Group Settings The table in the Group Settings section lists role groups, displaying associated names, domains, and privileges for any role groups that are already configured. • To configure a new role group, click a role group name that does not have a name, domain, and privilege listed. • To change the settings for an existing role group, click the role group name. When you click a role group name, the Configure Role Group page appears.
Configuring Generic LDAP Directory Service Using RACADM NOTE: This feature supports both IPv4 and IPv6. There are many options to configure LDAP logins. In most of the cases, some options can be used with their default settings. NOTE: It is highly recommended to use the 'racadm testfeature -f LDAP' command to test the LDAP settings for first time setups. This feature supports both IPv4 and IPv6.
9 Power Management Overview The Dell PowerEdge M1000e server enclosure is the most power-efficient modular server enclosure in the market. It is designed to include highlyefficient power supplies and fans, has an optimized layout so that air flows more easily through the system, and contains power-optimized components throughout the enclosure.
When you configure a system for AC redundancy, the PSUs are divided into grids: PSUs in slots 1, 2, and 3 are in the first grid while PSUs in slots 4, 5, and 6 are in the second grid. CMC manages power so that if there is a failure of either grid the system continues to operate without any degradation. AC redundancy also tolerates failures of individual PSUs.
NOTE: In the event of a single PSU failure in this configuration, the remaining PSUs in the failing grid are marked as Online. In this state, any of the remaining PSUs can fail without interrupting operation of the system. If a PSU fails, the chassis health is marked non-critical. If the smaller grid cannot support the total chassis power allocations then AC redundancy status is reported as No Redundancy and Chassis health is displayed as Critical.
No Redundancy Mode The no redundancy mode is the factory default setting for 3 PSU configuration and indicates that the chassis does not have any power redundancy configured. In this configuration, the overall redundancy status of the chassis always indicates No Redundancy. CMC does not require the PSU units to be present in any specific PSU slot positions when No Redundancy is configured. NOTE: All PSUs in the chassis are Online if DPSE is disabled when in No Redundancy mode.
When you enable DPSE, the extra PSUs may be placed in Standby mode to increase efficiency and save power. For more information, see "Dynamic Power Supply Engagement" on page 296. Power Budgeting for Hardware Modules Figure 9-4 illustrates a chassis that contains a six-PSU configuration. The PSUs are numbers 1-6, starting on the left-side of the enclosure. Figure 9-4.
iDRAC provides CMC with its power envelope requirements before powering up the server. The power envelope consists of the maximum and minimum power requirements necessary to keep the server operating. iDRAC’s initial estimate is based on its initial understanding of components in the server. After operation commences and further components are discovered, iDRAC may increase or decrease its initial power requirements.
Configuration changes, such as an additional server in the chassis, may require the System Input Power Cap to be increased. Power needs in a modular enclosure also increase when thermal conditions change and the fans are required to run at higher speed, which causes them to consume additional power. Insertion of I/O modules and iKVM also increases the power needs of the modular enclosure.
If an administrator manually powers on the low priority server modules before the higher priority ones, then the low priority server modules are the first modules to have their power allocation lowered down to the minimum value, in order to accommodate the higher priority servers. So after the available power for allocation is exhausted, then CMC reclaims power from lower or equal priority servers until they are at their minimum power level.
DPSE can be enabled for all three power supply redundancy configurations explained above — No Redundancy, Power Supply Redundancy, and AC Redundancy. • In a No Redundancy configuration with DPSE, the M1000e can have up to five power supply units in Standby state. In a six PSU configuration, some PSU units are placed in Standby and stay unutilized to improve power efficiency.
Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis. The following redundancy policies are configurable with or without dynamic PSU engagement: • AC Redundancy • Power Supply Redundancy • No Redundancy The default redundancy configuration for a chassis depends on how many PSUs it contains, as shown in Table 9-1. Table 9-1.
No Redundancy Power in excess of what is necessary to power the chassis is available, even on a failure, to continue to power the chassis. CAUTION: The No Redundancy mode uses optimum PSUs when DPSE is enabled for the requirements of the chassis. Failure of a single PSU could cause servers to lose power and data in this mode. Power Conservation and Power Budget Changes CMC performs power conservation when the user-configured maximum power limit is reached.
In maximum power conservation mode, all servers start functioning at their minimum power levels, and all subsequent server power allocation requests are denied. In this mode, the performance of powered on servers may be degraded. Additional servers cannot be powered on, regardless of server priority. The system is restored to full performance when the user or an automated command line script clears the maximum conservation mode.
Using the Web Interface Verify that the 110 V circuit is rated for the current expected, and then perform the following steps: 1 Click Chassis Overview in the system tree. 2 Click Power Configuration. 3 Select Allow 110 VAC Operation and click Apply. Using RACADM Verify that your 110 V circuit is rated for the expected current, and then perform the following steps: 1 Open a serial/Telnet/SSH text console to CMC and log in.
To disable Server Performance Over Power Redundancy, perform the following steps: 1 Click Chassis Overview in the system tree. 2 Click Power Configuration. 3 Clear Server Performance Over Power Redundancy and click Apply. Using RACADM To enable Server Performance Over Power Redundancy, perform the following steps: 1 Open a serial/Telnet/SSH text console to CMC and log in.
3 Select Power Remote Logging, to enable you to log power events to a remote host. 4 Specify the required logging interval (1–1440 minutes). 5 Click Apply, to save changes.
PSU Failure With Degraded or No Redundancy Policy CMC decreases power to servers when an insufficient power event occurs, such as a PSU failure. After decreasing power on servers, CMC re-evaluates the power needs of the chassis. If power requirements are still not met, CMC powers off lower priority servers. Power for higher priority servers is restored incrementally while power needs remain within the power budget.
Table 9-2. CMC Response When a Server Power-On is Attempted Worst Case Power CMC Response is Available Server Power On Yes No power conservation is required Allowed No Perform power conservation: • Power required for new server is available Allowed • Power required for new server is not available Disallowed If a PSU fails, it results in a non-critical health state and a PSU failure event is generated. The removal of a PSU results in a PSU removal event.
Table 9-3. Chassis Impact from PSU Failure or Removal (continued) PSU Configuration Dynamic PSU Firmware Response Engagement Power Supply Redundancy Enabled CMC alerts you of loss of Power Supply Redundancy. PSUs in standby mode (if any) are turned on to compensate for power budget lost from PSU failure or removal. No Redundancy Enabled Decrease power to low priority servers, if needed.
Table 9-4.
Redundancy Status and Overall Power Health The redundancy status is a factor in determining the overall power health. When the power redundancy policy is set, for example, to AC Redundancy and the redundancy status indicates that the system is operating with redundancy, the overall power health is typically OK. However, if the conditions for operating with AC redundancy cannot be met, the redundancy status is No, and the overall power health is Critical.
To view health status for all PSUs using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status of all PSUs. PSU health status is indicated by the color of the PSU subgraphic: • Green — PSU is present, powered on and communicating with CMC; there is no indication of an adverse condition. • Amber — Indicates a PSU failure.
Table 9-6. Power Supplies (continued) Item Description Health OK Indicates that the PSU is present and communicating with CMC. In the event of a communication failure between CMC and the power supply, CMC cannot obtain or display health status for the PSU. Warning Indicates that only Warning alerts have been issued, and corrective action must be taken. If corrective actions are not taken, it could lead to critical or severe power failures that can affect the integrity of the chassis.
Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getpminfo For more information about getpminfo, including output details, see the Command Line Reference Guide for iDRAC6 and CMC on the Dell Support website at support.dell.com/manuals. Viewing Power Consumption Status CMC provides the actual input power consumption for the entire system on the Power Consumption Status page.
Table 9-8. Real-Time Power Statistics Item Description System Input Power Displays the current cumulative power consumption of all modules in the chassis measured from the input side of the PSUs. The value for system input power is indicated in both watts and BTU/h units. Peak System Power Displays the maximum system level input power consumption since the value was last cleared.
Table 9-8. Real-Time Power Statistics (continued) Item Description Minimum System Displays the date and time recorded when the minimum system Power Start Time power consumption value was last cleared. The timestamp is displayed in the format hh:mm:ss MM/DD/YYYY, where hh is hours (0-24), mm is minutes (00-60), ss is seconds (00-60), MM is the month (1-12), DD is the day (1-31), and YYYY is the year.
Table 9-9. Real-Time Energy Statistics Status Item Description System Energy Consumption Displays the current cumulative energy consumption for all modules in the chassis measured from the input side of the power supplies. The value is displayed in KWh and it is a cumulative value. System Energy Consumption Start Time Displays the date and time recorded when the system energy consumption value was last cleared, and the new measurement cycle began.
Table 9-11. Server Modules Item Description Slot Displays the location of the server module. The Slot is a sequential number (1–16) that identifies the server module by its location within the chassis. Name Displays the server name. The server name can be redefined by the user. Present Displays whether the server is present in the slot (Yes or No). If this field displays Extension of # (where the # is 1-8), then number that follows it is the main slot of a multi-slot server.
Table 9-12 through Table 9-15 describe the information displayed on the Power Budget Status page. See "Configuring Power Budget and Redundancy" on page 320 for information about configuring the settings for this information. Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getpbinfo For more information about getpbinfo, including output details, see the getpbinfo command section in the Command Line Reference Guide for iDRAC6 and CMC. Table 9-12.
Table 9-12. System Power Policy Configuration (continued) Item Description Redundancy Policy Displays the current redundancy configuration: AC Redundancy, Power Supply Redundancy, and No Redundancy. AC Redundancy — Power input is load-balanced across all PSUs. Half of them should be cabled to one AC grid and the other half should be cabled to another grid. When the system is running optimally in AC Redundancy mode, power is load-balanced across all active supplies.
Table 9-13. Power Budgeting Item Description System Input Max Power Capacity Maximum input power that the available power supplies can supply to the system (in watts). Input Redundancy Reserve Displays the amount of redundant power (in watts) in reserve that can be utilized in the event of an AC grid or power supply unit (PSU) failure.
Table 9-14. Server Modules Item Description Slot Displays the location of the server module. The Slot is a sequential number (1–16) that identifies the server module by its location within the chassis. Name Displays the server name. The server name is defined by the user. Type Displays the type of the server. Priority Displays the priority level allotted to the server slot in the chassis for power budgeting.
Table 9-15. Chassis Power Supplies Item Description Name Displays the name of the PSU in the format PS-n, where n, is the PSU number. Power State Displays the power state of the PSU — Initializing, Online, Stand By, In Diagnostics, Failed, Unknown, or Absent (missing). Input Volts Displays the present input voltage of the power supply. Input Current Displays the present input current of the power supply. Output Rated Power Displays the maximum output power rating of the power supply.
Table 9-16. Configurable Power Budget/Redundancy Properties Item Description System Input Power Cap System Input Power Cap is the maximum AC power that the system is allowed to allocate to servers and chassis infrastructure. It can be configured by the user to any value that exceeds the minimum power needed for servers that are powered on and the chassis infrastructure; configuring a value that falls below the minimum power needed for servers and the chassis infrastructure fails.
Table 9-16. Configurable Power Budget/Redundancy Properties (continued) Item Description Redundancy Policy This option allows you to select one the following options: • No Redundancy: Power from the power supplies is used to power the entire chassis, including the chassis, servers, I/O modules, iKVM, and CMC. No power supplies must be kept in reserve. NOTE: The No Redundancy mode uses only the minimum required number of power supplies at a time.
Table 9-16. Configurable Power Budget/Redundancy Properties (continued) Item Description Enable Dynamic Power Supply Engagement On selection, enables dynamic power management. In Dynamic Engagement mode, the power supplies are turned ON (online) or OFF (standby) based on power consumption, optimizing the energy consumption of the entire chassis. For example, your power budget is 5000 watts, your redundancy policy is set to AC redundancy mode, and you have six power supply units.
where is 0 (No Redundancy), 1 (AC Redundancy), 2 (Power Supply Redundancy). The default is 0. For example, the following command: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy 1 sets the redundancy policy to 1. • To enable or disable dynamic PSU engagement, type: racadm config -g cfgChassisPower -o cfgChassisDynamicPSUEngagementEnable where is 0 (disable), 1 (enable). The default is 0.
Using the Web Interface 1 Log in to the CMC Web interface. 2 Select Servers Overview in the system tree. The Servers Status page appears. 3 Click Power Server Priority. The Server Priority page appears, listing all of the servers in your chassis. 4 Select a priority level (1–9, with 1 holding the highest priority) for one, multiple, or all servers. The default value is 1. You can assign the same priority level to multiple servers. 5 Click Apply to save your changes.
4 Click the Configuration subtab. The Budget/Redundancy Configuration page appears. 5 Type a budget value of up to 11637 watts in the System Input Power Cap text field. NOTE: The power budget is limited to a maximum of which ever set of three PSUs that is the weakest.. If you attempt to set an AC power budget value that exceeds this value, CMC displays a failure message. NOTE: When value changes are specified in watts, the submitted value will exactly reflect what is actually applied.
Server Power Reduction to Maintain Power Budget CMC reduces power allocations of lower priority servers when additional power is needed to maintain the system power consumption within the user-configured System Input Power Cap. For example, when a new server is engaged, CMC may decrease power to low priority servers to allow more power for the new server.
5 Click the corresponding radio buttons to select one of the following Power Control Operations: • Power On System — Turns on the chassis power (the equivalent of pressing the power button when the chassis power is OFF). This option is disabled if the chassis is already powered ON. NOTE: This action powers on the chassis and other subsystems (iDRAC on the servers, IOMs, and iKVM). Servers do not power on. • Power Off System — Turns off the chassis power.
Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m chassis where is powerup, powerdown, powercycle, nongraceshutdown or reset. Executing Power Control Operations on an IOM You can remotely execute a reset or power cycle on an individual IOM. NOTE: To perform power management actions, you must have Chassis Control Administrator privilege. Using the Web Interface 1 Log in to the CMC Web interface. 2 Select I/O Modules Overview.
Executing Power Control Operations on a Server NOTE: To perform power management actions, you must have Chassis Control Administrator privilege. CMC enables you to remotely perform several power management actions, for example, an orderly shutdown, on an individual server in the chassis. Using the Web Interface 1 Log in to the CMC Web interface. 2 Expand Server Overview in the system tree, and then select the server on which you want to execute a power control operation. The Server Status page displays.
• Reset Server (warm boot) — Reboots the server without powering off. This option is disabled if the server is powered off. • Power Cycle Server (cold boot) — Powers off and then reboots the server. This option is disabled if the server is powered off. 6 Click Apply. A dialog box appears requesting confirmation. 7 Click OK to perform the power management action (for example, cause the server to reset).
The overall power health is at least in Non-Critical state when the chassis is operating in 110V mode and the user has not acknowledged the 110V operation. The "Warning" icon is displayed on the GUI main page when in Non-Critical state. Mixed 110V and 220V operation is not supported. If CMC detects that both voltages are in use then one voltage is selected and those power supplies connected to the other voltage are powered off and marked as failed.
Using the iKVM Module 10 Overview The local access KVM module for your Dell M1000e server chassis is called the Avocent Integrated KVM Switch Module, or iKVM. The iKVM is an analog keyboard, video, and mouse switch that plugs into your chassis. It is an optional, hot-pluggable module to the chassis that provides local keyboard, mouse, and video access to the servers in the chassis, and to the active CMC’s command line.
Server Identification CMC assigns slots names for all servers in the chassis. Although you can assign names to the servers using the OSCAR interface from a tiered connection, CMC assigned names take precedence, and any new names you assign to servers using OSCAR is overwritten. CMC identifies a slot by assigning it a unique name. To change slot names using the CMC Web interface, see "Editing Slot Names.
iKVM Connection Precedences Only one iKVM connection is available at a time. The iKVM assigns an order of precedence to each type of connection so that when there are multiple connections, only one connection is available while others are disabled. The order of precedence for iKVM connections is as follows: 1 Front panel 2 ACI 3 Rear Panel For example, if you have iKVM connections in the front panel and ACI, the front panel connection remains active while the ACI connection is disabled.
Using OSCAR This section provides an overview of the OSCAR interface. Navigation Basics . Table 10-1. OSCAR Keyboard and Mouse Navigation Key or Key Sequence Result • Any of these key sequences can open OSCAR, depending on your Invoke OSCAR settings. You can enable two, three, or all of these key sequences by selecting boxes in the Invoke • - OSCAR section of the Main dialog box, and then clicking • - OK.
Table 10-1. OSCAR Keyboard and Mouse Navigation (continued) Key or Key Sequence Result , +<0> Immediately disconnects a user from a server; no server is selected. Status flag displays Free. (This action only applies to the =<0> on the keyboard and not the keypad.) , Immediately turns on screen saver mode and prevents access to that specific console, if it is password protected. Up/Down Arrow keys Moves the cursor from line to line in lists.
Changing the Display Behavior Use the Menu dialog box to change the display order of servers and set a Screen Delay Time for OSCAR. To access the Menu dialog box: 1 Press to launch OSCAR. The Main dialog box appears. 2 Click Setup and then Menu. The Menu dialog box appears. To choose the default display order of servers in the Main dialog box: 1 Select Name to display servers alphabetically by name. or Select Slot to display servers numerically by slot number. 2 Click OK.
Table 10-3. Flag OSCAR Status Flags Description Flag type by name Flag indicating that the user has been disconnected from all systems Flag indicating that Broadcast mode is enabled To access the Flag dialog box: 1 Press . The Main dialog box appears. 2 Click Setup and then Flag. The Flag dialog box appears. To specify how the status flag displays: 1 Select Displayed to show the flag all the time or Displayed and Timed to display the flag for only five seconds after switching.
Managing Servers With iKVM The iKVM is an analog switch matrix supporting up to 16 servers. The iKVM switch uses the OSCAR user interface to select and configure your servers. In addition, the iKVM includes a system input to establish a CMC command line console connection to CMC. Peripherals Compatibility and Support The iKVM is compatible with the following peripherals: • Standard PC USB keyboards with QWERTY, QWERTZ, AZERTY, and Japanese 109 layouts. • VGA monitors with DDC support.
To access the Main dialog box: Press to launch the OSCAR interface. The Main dialog box appears. or If a password has been assigned, the Password dialog box appears. Type your password and click OK. The Main dialog box appears. For more information about setting a password, see "Setting Console Security" on page 344. NOTE: There are four options for invoking OSCAR.
Selecting Servers Use the Main dialog box to select servers. When you select a server, the iKVM reconfigures the keyboard and mouse to the proper settings for that server. • To select servers: Double-click the server name or the slot number. or If the display order of your server list is by slot (that is, the Slot button is depressed), type the slot number and press .
To configure OSCAR for soft switching: 1 Press to launch the OSCAR interface. The Main dialog box appears. 2 Click Setup and then Menu. The Menu dialog box appears. 3 Select Name or Slot for the Display/Sort Key. 4 Type the desired delay time in seconds in the Screen Delay Time field. 5 Click OK. To soft switch to a server: • To select a server, press .
Preemption Warning Normally, a user connected to a server console through the iKVM and another user connected to the same server console through the iDRAC GUI console redirection feature both have access to the console and are able to type simultaneously. To prevent this scenario, the remote user, before starting the iDRAC GUI console redirection, can disable the local console in the iDRAC Web interface.
Setting or Changing the Password 1 Single-click and press or double-click in the New field. 2 Type the new password in the New field and then press . Passwords are case sensitive and require 5–12 characters. They must include at least one letter and one number. Legal characters are: A–Z, a–z, 0–9, space, and hyphen. 3 In the Repeat field, type the password again, and then press . 4 Click OK if you only want to change your password, and then close the dialog box.
Logging In 1 Press to launch OSCAR. The Password dialog box appears. 2 Type your password and then click OK. The Main dialog box appears. Setting Automatic Logout You can set OSCAR to automatically log out of a server after a period of inactivity. 1 In the Main dialog box, click Setup and then Security. 2 In the Inactivity Time field, enter the length of time you want to stay connected to a server before it automatically disconnects you. 3 Click OK.
3 Select Energy if your monitor is ENERGY STAR compliant; otherwise select Screen. CAUTION: Monitor damage may result from the use of Energy mode with monitors not compliant with Energy Star. 4 Optional: To activate the screen saver test, click Test. The Screen Saver Test dialog box displays. Click OK to start the test. The test takes 10 seconds. When it concludes, you are returned to the Security dialog box. NOTE: Enabling screen saver mode disconnects the user from a server; no server is selected.
To reset a lost or forgotten password using RACADM, open a serial/Telnet/SSH text console to CMC, log in, and type: racadm racresetcfg -m kvm NOTE: Using the racresetcfg command resets the Front Panel Enable and Dell CMC Console Enable settings, if they are different from the default values. For more information about the racresetcfg subcommand, see the racresetcfg section in the Command Line Reference Guide for iDRAC6 and CMC.
To add servers to the scan list: 1 Press . The Main dialog box appears. 2 Click Setup and then Scan. The Scan dialog box appears, listing of all servers in the chassis. 3 Select the box next to the servers you wish to scan. or Double-click the server name or slot. or Press and the number of the server you wish to scan. You can select up to 16 servers.
To cancel scan mode: 1 If OSCAR is open and the Main dialog box is displayed, select a server in the list. or If OSCAR is not open, move the mouse or press any key on the keyboard. Scanning stops at the currently selected server. or Press . The Main dialog box appears; select a server in the list. 2 Click the Commands button. The Commands dialog box appears. 3 Clear the Scan Enable box.
3 Enable mouse and/or keyboard for the servers that are to receive the broadcast commands by selecting the boxes. or Press the up or down arrow keys to move the cursor to a target server. Then press to select the keyboard box and/or to select the mouse box. Repeat for additional servers. 4 Click OK to save the settings and return to the Setup dialog box. Click or press to return to the Main dialog box. 5 Click Commands. The Commands dialog box appears.
To enable or disable access to the iKVM from the front panel using the Web interface: 1 Log in to the CMC Web interface. 2 Select iKVM in the system tree. The iKVM Status page displays. 3 Click the Setup tab. The iKVM Configuration page displays. 4 To enable, select the Front Panel USB/Video Enabled check box. To disable, clear the Front Panel USB/Video Enabled check box. 5 Click Apply to save the setting.
• Green - iKVM is present, powered on and communicating with the CMC; there is no indication of an adverse condition. • Amber - iKVM is present, but may or may not be powered on, or may or may not be communicating with CMC; an adverse condition may exist. • Gray - iKVM is present and not powered on. It is not communicating with CMC and there is no indication of an adverse condition. 3 Use the cursor to hover over the iKVM subgraphic and a corresponding text hint or screen tip is displayed.
Table 10-5. iKVM Status Information (continued) Item Description Rear Panel Connected Indicates whether the monitor is connected to the rear panel VGA connector (Yes or No). This information is provided to CMC so it can determine whether a local user has rear-panel access to the chassis. Tiering Port Connected The iKVM supports seamless tiering with external KVM appliances from Dell and Avocent using built-in hardware.
based on connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer displays. Additional instructions to follow: • Do not use the Refresh button or navigate to another page during the file transfer. • To cancel the process, click Cancel File Transfer and Update - this option is available only during file transfer. • Update status displays in the Update State field; this field is automatically updated during the file transfer process.
Table 10-6. Troubleshooting iKVM Problem Likely Cause and Solution The message "User has been disabled by CMC control" appears on the monitor connected to the front panel. The front panel connection has been disabled by CMC. You can enable the front panel using either the CMC Web interface or RACADM. To enable the front panel using the Web interface: 1 Log in to the CMC Web interface. 2 Select iKVM in the system tree. 3 Click the Setup tab. 4 Select the Front Panel USB/Video Enabled check box.
Table 10-6. Troubleshooting iKVM (continued) Problem Likely Cause and Solution The message "User has been disabled as another appliance is currently tiered" appears on the monitor connected to the rear panel. A network cable is connected to the iKVM ACI port connector and to a secondary KVM appliance. The iKVM’s amber LED is blinking. There are three possible causes: Only one connection is allowed at a time. The ACI tiering connection has precedence over the rear panel monitor connection.
Table 10-6. Troubleshooting iKVM (continued) Problem Likely Cause and Solution My iKVM is tiered through the ACI port to an external KVM switch, but all of the entries for the ACI connections are unavailable. The front panel connection is enabled and has a monitor connected. Because the front panel has precedence over all other iKVM connections, the ACI and rear panel connectors are disabled. All of the states are showing a yellow dot in the OSCAR interface.
Table 10-6. Troubleshooting iKVM (continued) Problem Likely Cause and Solution In the OSCAR menu, the Dell CMC connection is displaying a red X, and I cannot connect to CMC. There are two possible causes: The Dell CMC console has been disabled. In this case, you can enable it using either the CMC Web interface or RACADM. To enable the Dell CMC console using the Web interface: 1 Log in to the CMC Web interface. 2 Select iKVM in the system tree. 3 Click the Setup tab.
Using the iKVM Module
I/O Fabric Management 11 The chassis can hold up to six I/O modules (IOMs), each of which can be pass-through or switch modules. The IOMs are classified into three groups—A, B, and C. Each group has two slots—Slot 1 and Slot 2. The slots are designated with letters, from left to right, across the back of the chassis: A1 | B1 | C1 | C2 | B2 | A2. Each server has slots for two mezzanine cards (MCs) to connect to the IOMs. The MC and the corresponding IOM must have the same fabric.
Fabric Management Fabric management helps avoid electrical, configuration, or connectivity related problems due to installation of an IOM or MC that has an incompatible fabric type from the chassis' established fabric type. Invalid hardware configurations could cause electric or functional problems to the chassis or its components. Fabric management prevents invalid configurations from powering on. Figure 11-1 shows the location of IOMs in the chassis.
CMC creates entries in both the hardware log and CMC logs for invalid hardware configurations. For example: • An Ethernet MC connected to a Fibre Channel IOM is an invalid configuration. However, an Ethernet MC connected to both an Ethernet switch and an Ethernet pass-through IOM installed in the same IOM group is a valid connection. • A Fibre Channel pass-through IOM and a fibre channel switch IOM in slots B1 and B2 is a valid configuration if the first MCs on all of the servers are also fibre channel.
Invalid Mezzanine Card (MC) Configuration An invalid MC configuration occurs when a single server’s LOM or MC is not supported by its corresponding IOM. In this case, all the other servers in the chassis can be running, but the server with the mismatched MC card does not be allowed to power on. The power button on the server flashes Amber to alert a fabric mismatch. For information about CMC and hardware logs, see "Viewing the Event Logs" on page 398.
Monitoring IOM Health The health status for the IOMs can be viewed in two ways: from the Chassis Graphics section on the Chassis Status page or the I/O Modules Status page. The Chassis Graphics page provides a graphical overview of the IOMs installed in the chassis. To view health status of the IOMs using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed.
4 Click the Status subtab. The I/O Modules Status page displays. Table 11-1. I/O Modules Status Information Item Description Slot Displays the location of the I/O module in the chassis by group number (A, B, or C) and Bank (1 or 2). IOM Enumeration: A1, A2, B1, B2, C1, or C2. Present Displays whether the IOM is present (Yes or No). Health OK Indicates that the IOM is present and communicating with CMC.
Table 11-1. I/O Modules Status Information (continued) Item Description Fabric Displays the type of fabric for the IOM: Gigabit Ethernet, 10GE XAUI, 10GE KR, 10GE XAUI KR, FC 4 Gbps, FC 8 Gbps, SAS 3 Gbps, SAS 6 Gbps, Infiniband SDR, Infiniband DDR, Infiniband QDR, PCIe Bypass Generation 1, PCIe Bypass Generation 2. NOTE: Knowing the fabric types of the IOMs in your chassis is critical in preventing IOM mismatches within the same group.
Viewing the Health Status of an Individual IOM The I/O Module Status page (separate from the I/O Modules Status page) provides an overview of an individual IOM. To view the health status of an individual IOM: 1 Log in to the CMC Web interface. 2 Expand I/O Modules in the system tree. All of the IOMs (1–6) appear in the expanded I/O Modules list. 3 Click the IOM you want to view in the I/O Modules list in the system tree. 4 Click the Status subtab. The I/O Modules Status page displays. Table 11-2.
Table 11-2. I/O Module Health Status Information (continued) Item Description Warning Indicates that warning alerts have been issued, and corrective action must be taken. If corrective actions are not taken, it could lead to critical or severe failures that can affect the integrity of the IOM. Examples of conditions causing Warnings: IOM fabric mismatch with the server's mezzanine card fabric; invalid IOM configuration, where the newly installed IOM does not match the existing IOM on the same group.
Table 11-2. I/O Module Health Status Information (continued) Item Description MAC Address Displays the MAC address for the IOM. The MAC address is a unique address assigned to a device by the hardware vendor as a means for identification. NOTE: Pass-throughs do not have MAC addresses. Only switches have MAC addresses. Role Displays the I/O module stacking membership when modules are linked together: • Member - the module is part of a stack set • Master - the module is a primary access point.
To configure the network settings for an individual IOM: 1 Log in to the CMC Web interface. 2 Click I/O Modules in the system tree. Click the Setup subtab. The Configure I/O Modules Network Settings page displays. 3 To configure network settings for I/O modules, type/select values for the following properties, and then click Apply. NOTE: Only IOMs that are powered on can be configured. NOTE: The IP address set on the IOMs from CMC is not saved to the switch's permanent startup configuration.
Table 11-3. Configure I/O Module Network Settings (continued) Item Description DHCP Enabled Enables the IOM on the chassis to request and obtain an IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically. Default: Checked (enabled). If this option is checked, the IOM retrieves IP configuration (IP address, subnet mask, and gateway) automatically from a DHCP server on your network.
Troubleshooting IOM Network Settings The following list contains troubleshooting items for IOM network settings: • CMC can read the IP address setting too quickly after a configuration change; it displays 0.0.0.0 after clicking Apply. You must hit the refresh button in order to see if the IP address is set correctly on the switch. • If an error is made in setting the IP/mask/gateway, the switch does not set the IP address and returns a 0.0.0.0 in all fields.
I/O Fabric Management
12 Troubleshooting and Recovery Overview This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC Web interface. • Gathering Configuration information, error status and error logs. • Managing power on a remote system. • Viewing chassis information. • Viewing the event logs. • Using the Diagnostic Console. • Reset Components. • Troubleshooting Network Time Protocol (NTP) problems. • Troubleshooting network problems.
Usage racadm racdump The racdump subcommand displays the following information: • General system/RAC information • CMC information • Chassis information • Session information • Sensor information • Firmware build information Supported Interfaces • CLI RACADM • Remote RACADM • Telnet RACADM RACDUMP command can be run remotely from the serial, Telnet, or SSH console command prompt or through a normal command prompt.
Table 12-1.
racadm -i -r NOTE: The -i option instructs RACADM to interactively prompt for user name and password. Without the -i option, you must provide the user name and password in the command using the -u and -p options. For example: racadm -r 192.168.0.120 -u root -p calvin racdump racadm -i -r 192.168.0.
Using the Web Interface To enable blinking for one, multiple, or all component LEDs: 1 Log in to the CMC Web interface. 2 Click Chassis in the system tree. 3 Click the Troubleshooting tab. 4 Click the Identify subtab. The Identify page displays, featuring a list of all components on the chassis. 5 To enable blinking for a component LED, check the box beside the device name and then click Blink. 6 To disable blinking for a component LED, check the box beside the device name and then click UnBlink.
You can configure CMC to generate event traps. Table 12-2 provides an overview of the events that trigger SNMP and e-mail alerts. For information on e-mail alerts, see "Configuring E-mail Alerts" on page 385. NOTE: Starting with CMC version 2.10, SNMP is now IPv6 enabled. You can include an IPv6 address or fully qualified domain name (FQDN) in the destination for an event alert. Table 12-2.
Table 12-2. Chassis Events That Can Generate SNMP and Email Alerts (continued) Event Description IOM Absent An expected IOM is not present. IOM Failure The IOM is not functioning. Firmware Version Mismatch There is a firmware mismatch for the chassis or server firmware. Chassis Power Threshold Error Power consumption within the chassis reached the System Input Power Cap. SDCARD Absent There is no media in the CMC’s Secure Digital (SD) card slot, and a configured CMC feature requires it.
6 Type a valid address in an empty Destination field. NOTE: A valid address is an address that receives the trap alerts. Use the "quad-dot" IPv4 format, standard IPv6 address notation, or FQDN. For example: 123.123.123.123 or 2001:db8:85a3::8a2e:370:7334 or dell.com 7 Type the SNMP Community String to which the destination management station belongs. NOTE: The community string on the Chassis Event Alert Destinations page differs from the community string on the Chassis Network Services page.
racadm config -g cfgAlerting -o cfgAlertingFilterMask where is a hex value between 0x0 and 0xffffffff. To obtain the mask value, use a scientific calculator in hex mode and add the second values of the individual masks (1, 2, 4, etc.) using the key. For example, to enable trap alerts for Battery Probe Warning (0x2), Power Supply Failure (0x1000), and KVM failure (0x80000), key 2 1000 200000 and press the <=> key.
Table 12-3. Event Traps Filter Masks (continued) Event Filter Mask Value IOM Failure 0x200000 Firmware Version Mismatch 0x00400000 Chassis Power Threshold Error 0x01000000 SDCARD Absent 0x02000000 SDCARD Error 0x04000000 Chassis Group Error 0x8000000 4 Enable traps alerting by typing: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value 1–4. The index number is used by CMC to distinguish up to four configurable destinations for traps alerts.
You can configure up to four destinations to receive traps alerts. To add more destinations, repeat steps 2–6. NOTE: The commands in steps 2–6 overwrites any existing settings configured for the index you specify (1–4). To determine whether an index has previously configured values, type: racadm getconfig -g cfgTraps -i . If the index is configured, values appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName objects.
5 Click the Email Alert Settings subtab. The Email Alert Destinations page displays. 6 Specify the SMTP server IP address: a Locate the SMTP (Email) Server field, and then type the SMTP hostname or IP address. NOTE: You must configure the SMTP e-mail server to accept relayed emails from the CMC's IP address, a feature which is normally turned off in most mail servers due to security concerns.
To send a test e-mail to an e-mail alert destination: 1 Log in to the CMC Web interface. 2 Select Chassis in the system tree. 3 Click the Alerts tab. The Chassis Events page appears. 4 Click the Email Alert Settings subtab. The Email Alert Destinations page displays. 5 Click Send in the Destination Email Address column beside the destination. Using RACADM 1 Open a serial/Telnet/SSH text console to CMC and log in.
where is a valid e-mail address, and is the index value you specified in step 4. 6 Specify the name of the party receiving the e-mail alert by typing: racadm config -g cfgEmailAlert -o cfgEmailAlertEmailName -i where is the name of the person or group receiving the e-mail alert, and is the index value you specified in step 4 and step 5. The e-mail name can contain up to 32 alphanumeric characters, dashes, underscores, and periods.
Monitoring Power and Executing Power Control Commands on the Chassis You can use the Web interface or RACADM to: • View the system’s current power status. • Perform an orderly shutdown through the operating system when rebooting, and power the system on or off. For information about power management on CMC and configuring power budget, redundancy, and power control, see "Power Management" on page 289.
– • • • 390 Resolution B: Check if all power supplies are properly connected to the two AC grids; power supplies in side 1 need to be connected to one AC grid, those in side 2 need to be connected to the other AC grid, and both AC grids need to be working. AC Redundancy is lost when one of the AC grids is not functioning. Problem: The PSU state is displayed as Failed (No AC), even when an AC cord is connected and the power distribution unit is producing good AC output.
• – Resolution C: Check the max power conservation setting. If this is set then servers are allowed to power on. For more details, see the power configuration settings. – Resolution D: Check the server slot power priority of the slot associated with the newly inserted server, and ensure it is not lower than any other server slot power priority.
• Problem: The least priority servers lost power after a PSU failure. – • Resolution: This is expected behavior if the enclosure power policy was configured to No Redundancy. To avoid a future power supply failure causing servers to power off, ensure that the chassis has at least four power supplies and is configured for the Power Supply Redundancy policy to prevent PSU failure from impacting server operation.
Table 12-4. Chassis Summary Item Description Name Displays the name of the chassis. The name identifies the chassis on the network.For information on setting the name of the chassis, see "Editing Slot Names" on page 124. Model Displays the chassis model or manufacturer. For example, PowerEdge 2900. Service Tag Displays the service tag of the chassis. The service tag is a unique identifier provided by the manufacturer for support and maintenance. Asset Tag Displays the asset tag of the chassis.
Table 12-5. CMC Summary (continued) Item Description MAC Address Displays the MAC address for the CMC Network Interface. The MAC address is a unique identifier for CMC over the network. IP Address Displays the IP address of the CMC Network Interface. Gateway Displays the gateway of the CMC Network Interface. Subnet Mask Displays the subnet mask of the CMC Network Interface.
Table 12-5. CMC Summary (continued) Item Description Standby CMC Information Present Displays (Yes, No) whether a second (standby) CMC is installed. Standby Firmware Version Displays the CMC firmware version installed on the standby CMC. Table 12-6. iKVM Summary Item Description Present Displays whether the iKVM module is present (Yes or No). Name Displays the name of the iKVM. The name identifies the iKVM on the network. Manufacturer Displays the iKVM model or manufacturer.
Table 12-7. IOM Summary Item Description Location Displays the slot occupied by the IOMs. Six slots are identified by group name (A, B, or C) and slot number (1 or 2). Slot names: A-1, A-2, B-1, B-2, C-1, or C-2. Present Displays whether the IOM is present (Yes or No). Name Displays the name of the IOM. Fabric Displays the type of fabric. Power Status Displays the power status of the IOM: On, Off, or N/A (Absent). Service Tag Displays the service tag of the IOM.
Viewing Chassis and Component Health Status Using the Web Interface To view chassis and component health summaries: 1 Log in to the CMC Web interface. 2 Select Chassis in the system tree. The Chassis Health page displays. The Chassis Graphics section provides a graphical view of the front and rear of the chassis. This graphical representation provides a visual overview of the components installed within the chassis and its corresponding status.
Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getmodinfo Viewing the Event Logs The Hardware Log and CMC Log pages display system-critical events that occur on the managed system. Viewing the Hardware Log CMC generates a hardware log of events that occur on the chassis. You can view the hardware log using the Web interface and remote RACADM. NOTE: To clear the hardware log, you must have Clear Logs Administrator privilege.
To view the hardware log: 1 Log in to the CMC Web interface. 2 Click Chassis in the system tree. 3 Click the Logs tab. 4 Click the Hardware Log subtab. The Hardware Log page displays. To save a copy of the hardware log to your managed station or network: 1 Click Save Log. A dialog box opens. 2 Select a location for a text file of the log. NOTE: Because the log is saved as a text file, the graphical images used to indicate severity in the user interface do not appear.
Table 12-8. Hardware Log Information (continued) Item Description Date/Time Displays the exact date and time the event occurred (for example, Wed May 02 16:26:55 2007). If no date/time appears, then the event occurred at System Boot. Description Provides a brief description, generated by CMC, of the event (for example, Redundancy lost, Server inserted). Using RACADM 1 Open a serial/Telnet/SSH text console to CMC and log in.
4 Click the CMC Log subtab. The CMC Log page displays. 5 To save a copy of the CMC log to your managed station or network, click Save Log. A dialog box opens; select a location for a text file of the log. Table 12-9. CMC Log Information Command Result Source Displays the interface (such as CMC) that caused the event. Date/Time Displays the exact date and time the event occurred (for example, Wed May 02 16:26:55 2007).
To execute a diagnostic CLI command, type the command into the Enter RACADM Command field, and then click Submit to execute the diagnostic command. A diagnostic results page appears. To return to the Diagnostic Console page, click Go Back to Diagnostic Console Page or Refresh. The Diagnostic Console supports the commands listed in Table 12-10 as well as the RACADM commands. Table 12-10. Supported Diagnostic Commands Command Result arp Displays the contents of the address resolution protocol (ARP) table.
To access the Diagnostic Console page: 1 Log in to the CMC Web interface. 2 Click Chassis in the system tree. 3 Click the Troubleshooting tab. 4 Click the Reset Components subtab. The Reset Components page displays. The CMC Summary section of the Reset Components page displays the following information: Table 12-11. Attribute Health CMC Summary Description OK CMC is present and communicating with its components.
5 The Virtual Reseat Server section of the Reset Components page displays the following information: Table 12-12. Virtual Reseat Server Attribute Description Slot Displays the slot occupied by the server in the chassis. Slot names are sequential IDs, from 1 to 16, to help identify the location of the server in the chassis. Name Displays the name of the server in each slot. Present Displays whether the server is present in the slot (Yes or No).
Table 12-12. Virtual Reseat Server Attribute Description iDRAC Status Displays the status of the server iDRAC embedded management controller: • N/A - Server is not present, or the chassis is not powered on. • Ready - iDRAC is ready and operating normally. • Corrupted - iDRAC firmware is corrupted. Use the iDRAC firmware update utility to repair the firmware. • Failed - Unable to communicate with iDRAC. Use the Virtual Reseat check box to clear the error.
Troubleshooting Network Time Protocol (NTP) Errors After configuring CMC to synchronize its clock with a remote time server over the network, it may take 2-3 minutes before a change in the date and time occurs. If after this time there is still no change, it may be necessary to troubleshoot a problem. CMC may not be able to synchronize its clock for a number of reasons: • There could be a problem with the NTP Server 1, NTP Server 2, and NTP Server 3 settings.
If an ‘*’ is not displayed against one of the configured servers, something may not be set up properly. The output of the above command also contains detailed NTP statistics that may be useful in debugging why the server does not synchronize. If you attempt to configure an NTP server that is Windows based, it may help to increase the MaxDist parameter for ntpd.
Interpreting LED Colors and Blinking Patterns The LEDs on the chassis provide information by color and blinking/not blinking: • Steadily glowing, green LEDs indicate that the component is powered on. If the green LED is blinking, it indicates a critical but routine event, such as a firmware upload, during which the unit is not operational. It does not indicate a fault. • A blinking amber LED on a module indicates a fault on that module.
Table 12-13.
Table 12-13.
Observing the LEDs to Isolate the Problem Facing the front of CMC as it is installed in the chassis, you see two LEDs on the left side of the card. Top LED — The top green LED indicates power. If it is NOT on: 1 Verify that you have AC present to at least one power supply. 2 Verify that the CMC card is seated properly. You can release/pull on the ejector handle, remove CMC, reinstall CMC making sure the board is inserted all the way and the latch closes correctly.
and then press . Sample prompts: recover1[self test] CMC 1 self test failure recover2[Bad FW images] CMC2 has corrupted images • If the prompt indicates a self test failure, there are no serviceable components on CMC. CMC is bad and must returned to Dell. • If the prompt indicates Bad FW Images, then follow the steps in "Recovering the Firmware Image" on page 412 to fix the problem. Recovering the Firmware Image CMC enters recover mode when a normal CMC OS boot is not possible.
Troubleshooting Network Problems The internal CMC trace log allows you to debug CMC alerting and networking. You can access the trace log using the CMC Web interface (see "Using the Diagnostic Console") or RACADM (see "Using the RACADM Command Line Interface" and the gettracelog command section in the Command Line Reference Guide for iDRAC6 and CMC. The trace log tracks the following information: • DHCP — Traces packets sent to and received from a DHCP server.
To perform management actions, a user with Administrator privileges is required. If the administrator account password is forgotten, it can be reset using the PASSWORD_RST jumper on the CMC board. The PASSWORD_RST jumper uses a two-pin connector as shown in Figure 12-1.
Figure 12-1. Password Reset Jumper Location PASSWORD_RSET Table 12-14. CMC Password Jumper Settings PASSWORD_RSET (default) The password reset feature is disabled. The password reset feature is enabled. 3 Slide the CMC module into the enclosure. Reattach any cables that were disconnected. NOTE: Ensure that the CMC module becomes the active CMC, and remains the active CMC until the remaining steps are completed.
4 If the jumpered CMC module is the only CMC, then simply wait for it to finish rebooting. If you have redundant CMCs in your chassis, then initiate a changeover to make the jumpered CMC module active. On the GUI interface: a Navigate to the Chassis page, click the Power tab Control subtab. b Select the Reset CMC (warm boot) button. c Click Apply. CMC automatically fails over to the redundant module, and that module now becomes active.
Diagnostics 13 The LCD panel helps you to diagnose problems with any server or module in the chassis. If there is a problem or fault with the chassis or any server or other module in the chassis, the LCD panel status indicator blinks amber. On the Main Menu an icon with an amber background displays next to the menu item—Server or Enclosure—that leads to the faulty server or module.
Table 13-1. LCD Panel Navigational Icons Icon Normal Icon Icon Name and Description Highlighted Back. Highlight and press the center button to return to the previous screen. Accept/Yes. Highlight and press the center button to accept a change and return to the previous screen. Skip/Next. Highlight and press the center button to skip any changes and go to the next screen. No. Highlight and press the center button to answer "No" to a question and go to the next screen. Rotate.
LCD Setup Menu The LCD Setup menu displays a menu of items that can be configured: • Language Setup — choose the language you want to use for LCD screen text and messages. • Default Screen — choose the screen that displays when there is no activity on the LCD panel. 1 Use the up and down arrow buttons to highlight an item in the menu or highlight the Back icon if you want to return to the Main menu. 2 Press the center button to activate your selection.
The currently active default screen is highlighted in light blue. 1 Use the up and down arrow buttons to highlight the screen you want to set to the default. 2 Press the center button. The Accept icon is highlighted. 3 Press the center button again to confirm the change. The Default Screen is displayed. Graphical Server Status Screen The Graphical Server Status screen displays icons for each server installed in the chassis and indicates the general health status for each server.
Graphical Module Status Screen The Graphical Module Status screen displays all modules installed in the rear of the chassis and provides summary health information for each module.
Module Status Screen The Module Status screen displays information and error messages about a module. See "LCD Module and Server Status Information" on page 433 and "LCD Error Messages" on page 426 for messages that can appear on this screen. Use the up and down arrow keys to move through messages. Use the left and right arrow keys to scroll messages that do not fit on the screen. Highlight the Back icon and press the center button to return to the Graphical Module Status screen.
Diagnostics The LCD panel helps you to diagnose problems with any server or module in the chassis. If there is a problem or fault with the chassis or any server or other module in the chassis, the LCD panel status indicator blinks amber. On the Main Menu a blinking icon with an amber background displays next to the menu item—Server or Enclosure—that leads to the faulty server or module.
Figure 13-1.
Table 13-2. LCD Hardware Trouble Shooting Items Symptom Issue Recovery Action Alert screen message CMC Not Responding and Loss of communication from CMC to the LCD front panel. Check that CMC is booting; then, reset CMC using GUI or RACADM commands. Alert screen message CMC Not Responding and LCD module communications is stuck during a CMC fail-over or reboots. Review the hardware log using the GUI or RACADM commands. Look for a message that states: Can LED is blinking amber.
Front Panel LCD Messages This section contains two subsections that list error and status information that is displayed on the front panel LCD. Error messages on the LCD have a format that is similar to the System Event Log (SEL) viewed from the CLI or Web interface.
Table 13-4. Enclosure/Chassis Status Screen Severity Message Cause Critical Fan is removed. This fan is required for proper cooling of the enclosure/chassis. Warning Power supply redundancy is degraded. One or more PSU have failed or removed and the system can no longer support full PSU redundancy. Critical Power supply redundancy is lost. One or more PSU have failed or removed and the system is no longer redundant. Critical The power supplies are not redundant.
Table 13-5. Fan Status Screens Severity Message Cause Critical Fan RPM is operating The speed of the specified fan is less than the lower critical not sufficient to provide enough threshold. cooling to the system. Critical Fan RPM is operating The speed of the specified fan is to greater than the upper critical high, usually due to a broken fan threshold. blade. Table 13-6.
Table 13-8. PSU Status Screens Severity Message Cause Critical Power supply failed. The PSU has failed. Critical The power input for power supply Loss of AC power or AC cord is lost. unplugged. Warning Power supply is operating at 110 volts, and could cause a circuit breaker fault. Table 13-9. Power supply is plug into a 110 volt source. Server Status Screen Severity Message Cause Warning Server temperature is getting cool.
Table 13-9. Server Status Screen (continued) Severity Message Critical The CPU voltage is outside of the allowable range. Critical The system board voltage is outside of the allowable range. Critical The mezzanine card voltage is outside of the allowable range. Critical The storage voltage is outside of the allowable range. Critical CPU has an internal error (IERR). CPU failure.
Table 13-9. Server Status Screen (continued) Severity Message Cause Critical The system board fail-safe voltage This event is generated when the is outside of the allowable range. system board voltages are not at normal levels. Critical The watchdog timer expired. The iDRAC watchdog timer expires and no action is set. Critical The watchdog timer reset the system.
Table 13-9. Server Status Screen (continued) Severity Message Cause Critical An I/O channel check NMI was detected on a component at bus device function . A critical interrupt is generated in the I/O Channel. Critical An I/O channel check NMI wa detected on a component at slot . A critical interrupt is generated in the I/O Channel. Critical A PCI parity error was detected on Parity error was detected on the a component at bus PCI bus.
Table 13-9. Server Status Screen (continued) Severity Message Cause Critical Memory redundancy is lost. Critical A bus fatal error was detected on a Fatal error is detected on the PCIe component at bus bus. device function . Critical A software NMI was detected on a Chip error is detected. component at bus device function . Critical Failed to program virtual MAC address on a component at bus device function .
Table 13-10. CMC Status (continued) Item Description Firmware Version Only displays on an active CMC. Displays Standby for the standby CMC. IP4 Displays current IPv4 enabled state only on an active CMC. IP4 Address: Only displays if IPv4 is enabled only on an active CMC. IP6 Displays current IPv6 enabled state only on an active CMC. IP6 Local Address: Only displays if IPv6 is enabled only on an active CMC.
Table 13-12. Fan Status Item Description Name/Location Example: Fan1, Fan2, etc. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. RPM Current fan speed in RPM. Table 13-13. PSU Status Item Description Name/Location Example: PSU1, PSU2, etc. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. Status Offline, Online, or Standby.
Table 13-15. iKVM Status Item Description Name iKVM. No Error If there are no errors, then No Errors is displayed; otherwise error messages are listed. The critical errors are listed first, and then the warnings. For more information see "LCD Error Messages". Status Off or On. Model/Manufacture A description of the iKVM model. Service Tag The factory-assigned service tag. Part Number The Manufacturer part number. Firmware Version iKVM firmware version.
Table 13-16. Server Status (continued) Item Description Service Tag Displays if iDRAC finished booting. BIOS Version Server BIOS firmware version. Last POST Code Displays the last server BIOS POST code messages string. iDRAC Firmware Version Displays if iDRAC finished booting. NOTE: iDRAC version 1.01 is displayed as 1.1. There is no iDRAC version 1.10. IP4 Displays the current IPv4 enabled state. IP4 Address: Only displays if IPv4 is enabled.
The information in Table 13-16 is dynamically updated. If the server does not support this feature, then the following information does not appear, else Server Administrator options are as follows: • Option “None” = No strings must be displayed on the LCD. • Option “Default” = No Effect. • Option “Custom” = Allows you to enter a string name for the server. The information is displayed only if iDRAC has finished booting.
Index A ACI, 335 Activating FlexAddress Plus, 235 Active Directory, 241 adding CMC users, 262 configuring access to the CMC, 254 configuring and managing certificates, 163 extending schemas, 254 objects, 249 schema extensions, 248 using with standard schema, 242 viewing a server certificate, 179 CMC configuring, 264 creating a configuration file, 95 downloading firmware, 49 feature sets, 20 installing, 29 log, 400 redundant environment, 53 setting up, 29 CMC VLAN, 84 command line console features, 55 addi
E H Enabling or Disabling DCHP, 82 hardware log, 398 hardware specifications, 23 F fabric management, 361 I feature sets of CMC, 20 I/O fabric, 361 featurecard, 220 iDRAC recovering firmware, 195 firmware downloading, 49 managing, 189 updating, CMC, 190 updating, iKVM, 192 updating, IOM infrastructure device, 193 updating, Server iDRAC, 194 FlexAddress, 217 activating, 218 activation verification, 220 configuring using CLI, 222 deactivating, 221 license agreement, 231 Linux configuration, 223 trou
N Network LAN Settings, 80 network properties configuring manually, 78 configuring using racadm, 78 parsing rules, 97 Red Hat Enterprise Linux configuring for serial console redirection, 63 redundant environment, 53 remote access connection (RAC), 24 O OSCAR, 333 remote RACADM configuring, 48 P S parsing rules, 97 Secure Sockets Layer (SSL) about, 173 password disabling, 413 reset jumper location, 415 power budgeting configuring, 49 power conservation, 299 proxy server, 37 R RAC see Remote Access C
SNMP alerts adding and configuring, 379 specifications hardware, 23 standard schema using with Active Directory, 242 T telnet console using, 56 U Using FlexAddress Plus, 236 V Viewing Current IPv4 Network Settings, 79 Viewing Current IPv6 Network Settings, 79 W web browser configuring, 36 supported browsers, 25 web interface accessing, 103 configuring email alerts, 385 WS-Management, 25 442 Index
