Dell™ Chassis Management Controller Firmware Version 1.2 User Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2008 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 CMC Overview . . . . . . . . . . . . . . . . . . . . . CMC Management Features . . . . . . . . . . . . . . . 25 Security Features . . . . . . . . . . . . . . . . . . . . 26 Chassis Overview . . . . . . . . . . . . . . . . . . . . 27 Hardware Specifications TCP/IP Ports . . . . . . . . . . . . . . . . 28 . . . . . . . . . . . . . . . . . . . . 28 Supported Remote Access Connections Supported Platforms . . . . . . . . . 29 . . . . . . . . . . . . . . . . . .
Installing Remote Access Software on a Management Station . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing RACADM on a Linux Management Station . . . . . . . . . . . . . . . . . . . . . . . . 36 Uninstalling RACADM From a Linux Management Station . . . . . . . . . . . . . . . . . . . . . . . . 37 Configuring a Web Browser . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . . . . . ® Phishing Filter . . . . . . . . . . . . .
Understanding the Redundant CMC Environment. About the Standby CMC . . . 55 . . . . . . . . . . . . . . 55 Primary CMC Election Process . 3 . . . . . . . . . . 56 Planning Deployment of Redundant CMCs . . . . . 56 Obtaining Health Status of Redundant CMC . . . . 56 . . . . . 57 . . . . . 57 . . . . . . . . . . . . 58 Configuring CMC to Use Command Line Consoles . . . . . . . . . . . . . . . .
4 Using the RACADM Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . 69 . . . . . . . . . . . . 70 . . . . . . . . . . . . . . . 70 Using a Serial or Telnet Console Logging in to the CMC . . . . . . . . . . . . . . 70 . . . . . . . . . . . . . . . . . . . . . 70 Starting a Text Console . Using RACADM. RACADM Subcommands . . . . . . . . . . . . . . Accessing RACADM Remotely . . . . . . . . . . . Enabling and Disabling the RACADM Remote Capability . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . Command updates for CMC 1.20 . 5 . . . . . . . . . . . . Using the CMC Web Interface . 91 . . . . . . . . 93 . . . . . . . . . . . 93 . . . . . . . . . . . . . . . . . . . . . 94 Accessing the CMC Web Interface Logging In . 90 Logging Out . . . . . . . . . . . . . . . . . . . . . Configuring Basic CMC Settings Setting the Chassis Name . . . . . . . . . . . . 95 . . . . . . . . . . . . . 95 . . . . . . 95 . . . . . . . . . . .
Configuring CMC Network Properties . . . . . . . . . Setting Up Initial Access to the CMC . . . . . . . Configuring the Network LAN Settings . . . . . . . . . . . . . . . 120 . . . . . . . . . . . . . . . . . . . . 120 Adding and Managing Users . . . . . . . . . . . Configuring and Managing Microsoft Active Directory Certificates . . . . . . . . . . . . 127 . . . . . 130 Configuring Active Directory (Standard Schema and Extended Schema) . . . . . . . . . . . . . .
Viewing the Current Firmware Versions Updating Firmware . . . . . . 151 . . . . . . . . . . . . . . . . . 152 . . . 157 . . . . . . . . . . . . . . . . . . . . . . . 158 Recovering iDRAC Firmware Using the CMC FlexAddress Viewing FlexAddress Status Configuring FlexAddress . . . . . . . . . . . . 159 . . . . . . . . . . . . . . 163 Chassis-Level Fabric and Slot FlexAddress Configuration . . . . . . . . . . . . . . . . . . . 164 . . . . . . . . . . . . . . 165 . . . . . . . . . . . . . . .
7 Using the CMC With Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . Active Directory Schema Extensions . 185 . . . . . . . . . 185 . . 185 . . . . . . . . . . . . . 186 Extended Schema Versus Standard Schema. Extended Schema Overview . Active Directory Schema Extensions . . . . . . . . . . . 186 . . . . . . . . 187 Overview of the RAC Schema Extensions Active Directory Object Overview Configuring Extended Schema Active Directory to Access Your CMC . . . . . . . .
8 Power Management Overview . . . . . . . . . . . . . . . . 215 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 . . . . . . . . . . . . 216 Redundancy Policies . . . . . . . . . . . . . . . . . . 217 AC Redundancy . . . . . . . . . . . . . . . . . . . 217 Power Budgeting for Hardware Modules Dynamic PSU Engagement . . . . . . . . . . . . . 218 . . . . . . . . . . . . . . . . . . 218 Power Supply Redundancy . No Redundancy . Power Conservation and Power Budget Changes. . . .
Plug and Play . . . . . . . . . . . . . . . . . . . FLASH Upgradable . . . . . . . . . . . . . . . . Physical Connection Interfaces . . . . . . . . . . . . iKVM Connection Precedences . . . . . . . . . 246 . . . . . . . . . . . . . . . . . . . . . 247 Navigation Basics. . . . . . . . . . . . . . . . . 247 Configuring OSCAR . . . . . . . . . . . . . . . . 249 . . . . . . . . . . . . . . . . . 251 252 . . . . . . . . . . . . . 255 . . . . . . . . . . . . . .
Fresh Power-up Scenario Monitoring IOM Health . . . . . . . . . . . . . . . . 276 . . . . . . . . . . . . . . . . . 276 Viewing the Health Status of an Individual IOM . . . . . . . . . . . . . . . . . . . . . Troubleshooting IOM Network Settings 11 Troubleshooting and Recovery Overview . . . . . 279 . . . . . . 284 . . . . . . . 285 . . . . . . . . . . . . . . . . . . . . . . . . Chassis Monitoring Tools . . . . . . . . . . . . . . . . Configuring LEDs to Identify Components on the Chassis .
Troubleshooting a Non-responsive CMC . . . . . . . Observing the LEDs to Isolate the Problem . . . . Obtain Recovery Information From the DB-9 Serial Port . . . . . . . . . . . . . . . . . . . 310 Recovering the Firmware Image . . . . . . . . . 311 Troubleshooting Network Problems . . . . . . . . . . 312 . . . . . . . . . . . 312 . . . . . . . . . . . . . . . 315 Troubleshooting Alerting A RACADM Subcommands . . . . . . . . . . . . 317 . . . . . . . . . . . . . . . . 317 . . . . . . .
getconfig . . . . . . . . . . . . . . . . . . . . . . . . . 332 getdcinfo . . . . . . . . . . . . . . . . . . . . . . . . . 335 getflexaddr . getioinfo . . . . . . . . . . . . . . . . . . . . . . . 337 . . . . . . . . . . . . . . . . . . . . . . . . . 339 . . . . . . . . . . . . . . . . . . . . . . . 340 . . . . . . . . . . . . . . . . . . . . . . . . . . 340 getkvminfo . getled. getmacaddress. . . . . . . . . . . . . . . . . . . . . . 342 . . . . . . . . . . . . . . . . . . . . . . .
help and help . . . . . . . . . . . . . . . 360 ifconfig . . . . . . . . . . . . . . . . . . . . . . . . . 361 netstat . . . . . . . . . . . . . . . . . . . . . . . . . 361 . . . . . . . . . . . . . . . . . . . . . . . . . . 362 ping . racdump . . . . . . . . . . . . . . . . . . . . . . . . 363 racreset . . . . . . . . . . . . . . . . . . . . . . . . . 366 racresetcfg . . . . . . . . . . . . . . . . . . . . . . . 367 serveraction . . . . . . . . . . . . . . . . . . . . . .
testemail . testtrap . . . . . . . . . . . . . . . . . . . . . . . . . 383 . . . . . . . . . . . . . . . . . . . . . . . . . 384 B CMC Property Database Group and Object Definitions . . . . . . . . . . . . . . Displayable Characters 385 . . . . . . . . . . . . . . . . . 385 . . . . . . . . . . . . . . . . . . 385 . . . . . . . . . . . . . . . . . . . . . 386 idRacInfo (read only). #idRacType . . . #idRacProductInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 . . . .
cfgCurrentLanNetworking (read only) . . . . . . . . . 390 . . . . . . . . . . . . 390 # cfgNicCurrentNetmask . . . . . . . . . . . . . 391 # cfgNicCurrentGateway . . . . . . . . . . . . . 391 # cfgNicCurrentIpAddress . . . . . . . . . 391 # cfgDNSCurrentServer1 . . . . . . . . . . . . . 391 # cfgDNSCurrentServer1 . . . . . . . . . . . . . 391 # cfgNicCurrentDhcpWasUsed . # cfgDNSCurrentDomainName . cfgRemoteHosts . . . . . . . . . 391 . . . . . . . . . . . . . . . . . . . . 391 . .
cfgSerial . . . . . . . . . . . . . . . . . . . . . . . . . cfgSerialBaudRate . . . . . . . . . . . . . . . . . cfgSerialConsoleEnable . . . . . . . . . . . . . . cfgSerialConsoleQuitKey . . . . . . . . . . . . . . 399 399 . . . . . . . . . . . . 399 399 . . . . . . . . . . . . . . . 400 . . . . . . . . . . . . . . . . 400 . . . . . . . . . . . . . . . . . . . . . . 400 cfgSerialSshEnable . cfgNetTuningNicSpeed . . . . . . . . . . . . . . . cfgNetTuningNicFullDuplex cfgNetTuningNicMtu .
cfgRacTuneHttpPort . . . . . . . . . . . . . . . cfgRacTuneHttpsPort . . . . . . . . . . . . . . . 405 cfgRacTuneTelnetPort . . . . . . . . . . . . . . 405 . . . . . . . . . . . . . . . 405 cfgRacTuneSshPort . . . . . . . . . . . . 406 cfgRacTuneIpRangeAddr . . . . . . . . . . . . . 406 cfgRacTuneIpRangeMask . . . . . . . . . . . . 406 . . . . . . . . . . . . . 406 cfgRacTuneIpRangeEnable . cfgRacTuneIpBlkEnable cfgRacTuneIpBlkFailCount . . . . . . . . . . . . . . . . . . . . . .
cfgStandardSchema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 . . . . . . . . . . . . . 412 # cfgSSADRoleGroupIndex . cfgSSADRoleGroupName cfgSSADRoleGroupDomain . . . . . . . . . . . . 412 . . . . . . . . . . . 413 . . . . . . . . . . . . . . . . . . . . 413 cfgSSADRoleGroupPrivilege . cfgChassisPower 412 # cfgChassisInPower . . . . . . . . . . . . . . . . # cfgChassisPeakPower . . . . . . . . . . . . . . 413 . . . . . . . . 414 . . . . . . . . . . . . . .
cfgServerInfo . . . . . . . . . . . . . . . . . . . . . . # cfgServerInfoIndex . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 418 . . . . . . . . . . . . . . . . . 419 # cfgServerServiceTag # cfgServerBmcMacAddress . . . . . . . . . . . 419 # cfgServerNic1MacAddress . . . . . . . . . . . 419 # cfgServerNic2MacAddress . . . . . . . . . . . 419 . . . . . . . . . . . . . . . . . 419 cfgServerPriority cfgServerNicEnable . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . 428 . . . . . . . . . . . . . . . 431 . . . . . . . . . . . . . . . . . . 432 LCD Hardware Troubleshooting . Front Panel LCD Messages LCD Error Messages . LCD Module and Server Status Information . Glossary Index 428 . . . . . . . . . . . . . . . . . . . . . . . 442 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
CMC 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 M1000e chassis systems. You can configure the CMC to send email alerts or SNMP trap alerts for warnings or errors related to temperatures, hardware misconfigurations, power outages, and fan speeds.
• Dell OpenManage™ software integration — Enables you to launch the CMC Web interface from Dell OpenManage Server Administrator or IT Assistant • CMC alert — Alerts you to potential managed node issues through an e-mail message or SNMP trap • Remote power management — Provides remote power management functions, such as shutdown and reset on any chassis component, from a management console • Power usage reporting • Secure Sockets Layer (SSL) encryption — Provides secure remote system management thro
• Web interface supports 128-bit SSL 3.0 encryption and 40-bit SSL 3.0 encryption (for countries where 128-bit is not acceptable) NOTE: Telnet does not support SSL encryption.
Hardware Specifications TCP/IP Ports You must provide port information when opening firewalls for remote access to a CMC. Table 1-1 identifies the ports on which the CMC listens for server connections. Table 1-2 identifies the ports that the CMC uses as clients. 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 lists the connection features. Table 1-3.
For the latest information on supported Web browsers, see the Dell OpenManage Server Administrator Compatibility Guide located on the Dell Support website at support.dell.com. Table 1-4. Supported Web Browsers Operating System Supported Web Browser Windows® Internet Explorer® 6.0 (32-bit) with Service Pack 2 (SP2) for Windows XP and Windows 2003 R2 SP2 only. Internet Explorer 7.0 for Windows Vista®, Windows XP, and Windows 2003 R2 SP2 only. Linux Mozilla Firefox 1.
The data available through WS-Management is a subset of data provided by the CMC instrumentation interface mapped to the following DMTF profiles version 1.0.
For specific WS-Management support, see your management application documentation. Additional documentation is available on the Web: • www.wbemsolutions.com/ws_management.html • DMTF WS-Management Specifications: www.dmtf.org/standards/wbem/wsman • DMTF Management Profiles: www.dmtf.org/standards/profiles/ Other Documents You May Need In addition to this User’s Guide, the following documents provide additional information about the setup and operation of the CMC.
• The Rack Installation Guide and Rack Installation Instructions included with your rack solution describe how to install your system into a rack. • The Hardware Owner’s Manual provides information about system features and describes how to troubleshoot the system and install or replace system components. • Systems management software documentation describes the features, requirements, installation, and basic operation of the software.
CMC Overview
Installing and Setting Up the CMC This section provides information about how to install your CMC hardware, establish access to the CMC, and configure your management environment to use the CMC.
Installing Remote Access Software on a Management Station You can access the CMC using the Telnet, Secure Shell (SSH), or serial console utilities provided on your operating system or using the Web interface. If you want to use remote RACADM from your management station, you will need to install it. Your system includes the Dell Systems Management Tools and Documentation DVD.
or sh srvadmin-install.sh -x The script installs the typical software suite for your system configuration. NOTE: You can log the output of the RPM installation by adding 2>&1 | tee -a /var/log/srvadmin.log to the above shell script execution. The resulting command is sh srvadmin-install.sh 2>&1|tee -a /var/log/srvadmin.log 5 Start the Server Administrator services with the sh srvadminservices.sh start command. NOTE: The Dell Systems Management Tools and Documentation DVD contains version 5.
For example, if the rpm package name is srvadmin-racadm5, then type: rpm -e srvadmin-racadm5 Configuring a Web Browser You can configure and manage the CMC and the servers and modules installed in the chassis through a Web browser. See "Supported Web Browsers" on page 29 for a list of the Web browsers you can use with the CMC. Your CMC and the management station where you use your browser must be on the same network, which is called the management network.
5 In the Exceptions section, add the addresses for CMCs and iDRACs on the management network to the semicolon-separated list. You can use DNS names and wildcards in your entries. Mozilla FireFox Follow these steps to edit the exception list in Mozilla FireFox: 1 Start FireFox. 2 Click Tools→ Options…→ Advanced, then click the Network tab. 3 Click Settings…. 4 In the No Proxy for field, add the addresses for CMCs and iDRACs on the management network to the comma-separated list.
Follow these steps to disable CRL fetching: 1 Start Internet Explorer. 2 Click Tools→ Internet Options…, then click Advanced. 3 Scroll to the Security section and uncheck Check for publisher’s certificate revocation. 4 Click OK. 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.
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. If you have one chassis, connect the CMC, and the standby CMC if present, to the management network.
Create separate chains for the CMCs in the primary CMC slot and the second CMC slot. Figure 2-1 illustrates the arrangement of cables for four daisy-chained chassis, each with CMCs in the primary and secondary slots.
Figure 2-1.
Follow these steps to daisy-chain up to four chassis: 1 Connect the GB1 port of the primary CMC in the first chassis to the management network. 2 Connect the GB1 port of the primary CMC in the second chassis to the STK port of the primary CMC in the first chassis. 3 If you have a third chassis, connect the GB1 port of its primary CMC to the STK port of the primary CMC in the second chassis. 4 If you have a fourth chassis, connect the GB1 port of its primary CMC to the STK port of the third chassis.
If you configure initial network settings after the CMC has an IP address, you can use any of the following interfaces: • Command line interfaces (CLIs) such as a serial console, Telnet, SSH, or the Dell CMC Console via iKVM • Remote RACADM • The CMC Web interface Configuring Networking Using the LCD Configuration Wizard NOTE: The option to configure the CMC using the LCD Configuration Wizard is available only until the CMC is deployed or the default password is changed.
Figure 2-2. LCD Display 3 2 1 4 1 LCD screen 2 scroll buttons (4) 3 selection ("check") button 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. 46 • Solid blue indicates good health. • Blinking amber indicates that at least one component has a fault condition.
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. • To scroll through options on a screen, use the down and up arrow buttons. • To select and save an item on a screen and move to the next screen, use the center button.
5 Select the duplex mode (half or full) that matches your network environment. NOTE: The network speed and duplex mode settings are not available if Auto Negotiation is set to On or 1000MB (1Gbps) is selected. NOTE: If auto negotiation is turned on for one device but not the other, then the device using auto negotiation can determine the network speed of the other device, but not the duplex mode; in this case, duplex mode defaults to the half duplex setting during auto negotiation.
Static You manually enter the IP address, gateway, and subnet mask in the screens immediately following. If you have selected the Static option, press the center button to continue to the next CMC Network Settings screen, then: a Set the Static IP Address by 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 Static IP Address, press the center button to continue.
NOTE: You cannot set a static IP address for the iDRAC using the LCD Configuration Wizard. To set a static IP address, use the CMC Web interface or RACADM. When you have made your selection, press the center button. The IP Summary screen displays, listing the IP addresses you provided. 9 On the IP Summary screen, review the IP addresses you provided to make sure the addresses are accurate.
Table 2-1 describes each CMC network interface. Table 2-1. CMC Interfaces Interface Description Web interface Provides remote access to the CMC using a graphical user interface. The Web interface is built into the CMC firmware and is accessed through the NIC interface from a supported Web browser on the management station. For a list of supported Web browsers, see "Supported Web Browsers" on page 29.
To access the CMC interface using Dell Server Administrator, launch Server Administrator on your management station. From the system tree on the left pane of the Server Administrator home page, click System→ Main System Chassis→ Remote Access Controller. For more information, see your Dell Server Administrator User’s Guide. To access the CMC command line using Telnet or SSH, see "Configuring CMC to Use Command Line Consoles" on page 57.
You can use the RACADM getsysinfo command (see "getsysinfo" on page 357) or the Chassis Summary page (see "Viewing the Current Firmware Versions" on page 151) to view the current firmware versions for the CMCs installed in your chassis. If you have a standby CMC, it is recommended that you update the firmware in the standby CMC first. When the standby CMC has been updated, swap the CMCs’ roles so that the newly updated CMC becomes the primary CMC and the CMC with the older firmware becomes the standby.
NOTICE: Using more than one CMC configuration tool at the same time may generate unexpected results. Configuring Power Budgeting The CMC offers a power budgeting service that allows you to configure power budget, redundancy, and dynamic power for the chassis. The chassis ships with either three or six power supply units (PSUs). If your chassis has only three PSUs, you can add up to three more.
For instructions on using Active Directory with your CMC, see "Using the CMC With Microsoft Active Directory" on page 185. Adding SNMP and Email Alerts You can configure the CMC to generate SNMP and/or email alerts when certain chassis events occur. For more information, see "Configuring SNMP Alerts" on page 286 and "Configuring Email Alerts" on page 291. Understanding the Redundant CMC Environment You can install a standby CMC that takes over if your primary CMC fails.
Primary 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.
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 via the command line console, see "Using the RACADM Command Line Interface" on page 69.
Using a Serial or Telnet Console The CMC serial or telnet console enables you to turn on, turn off, or reset the server and access server logs. When you connect to the CMC command line, you are able to 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.
NOTE: OpenSSH should be run from a VT100 or ANSI terminal emulator on Windows. Running OpenSSH at the Windows command prompt does not provide full functionality (that is, some keys do not respond and no graphics are displayed). For Linux, run SSH Client Services to connect to CMC with any shell. Four simultaneous SSH sessions are supported at any given time.
Table 3-2.
Perform the steps in the following subsections to configure your type of terminal software. If you are using Microsoft Telnet, configuration is not required. Configuring Linux Minicom for Serial Console Emulation Minicom is a serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0. Other Minicom versions may differ slightly but require the same basic settings.
12 When all specified fields are clear, press to exit the Modem Dialing and Parameter Setup menu. 13 Select Save setup as config_name and press . 14 Select Exit From Minicom and press . 15 At the command shell prompt, type minicom . To expand the Minicom window to 80 x 25, drag the corner of the window. 16 Press , , to exit Minicom. Ensure that the Minicom window displays a command prompt such as [iDRAC\root]#.
To fix this issue, download hotfix 824810 from the Microsoft Support website at support.microsoft.com. See Microsoft Knowledge Base article 824810 for more information. Configuring Linux for Server Serial Console Redirection During Boot The following steps are specific to the Linux GRand Unified Bootloader (GRUB). Similar changes would be necessary for using a different boot loader.
timeout=10 #splashimage=(hd0,2)/grub/splash.xpm.gz serial --unit=1 --speed=57600 terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp) root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600 initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 s initrd /boot/initrd-2.4.9-e.3.im When you edit the /etc/grub.
The following example shows the file with the new line. # # inittab This file describes how the INIT process # should set up the system in a certain # run-level. # # Author: Miquel van Smoorenburg # Modified for RHS Linux by Marc Ewing and # Donnie Barnes # # Default runlevel.
# When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it.
vc/8 vc/9 vc/10 vc/11 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 ttyS1 Connecting to Modules With the Connect Command While in a command line connection, the CMC supports the connect command to establish a serial connection to server and IOM modules. Connection to server modules is only provided for operating system debugging.
There are up to six IOMs on the managed system. To connect to an IOM, type: connect switch-n where n is an IOM label a1, a2, b1, b2, c1, and c2. IOMs are labeled A1, A2, B1, B2, C1, and C2. (See Table 10-1 for an illustration of the placement of IOMs in the chassis.) When you reference the IOMs in the connect command, the IOMs are mapped to switches as shown in Table 3-4. Table 3-4.
Using the RACADM Command Line Interface 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.
Using a Serial or Telnet Console You can log in to the CMC either through a serial or Telnet/SSH connection, or through Dell CMC console on iKVM. To configure the CMC for serial or remote access, see "Configuring CMC to Use Command Line Consoles" on page 57. Commonly used subcommand options are listed in Table 4-2. A complete list of RACADM subcommands is listed in "RACADM Subcommands" on page 317.
When run without options or subcommands, RACADM displays syntax information and instructions on how to access subcommands and help. To list syntax and command-line options for individual subcommands, type: racadm help 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 "RACADM Subcommands" on page 317.
Table 4-1. RACADM Subcommands (continued) Command Description deploy Deploys a server by specifying required properties. 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 (Dell internal Displays the CMCtrace log. If used with the -i option, use only) the command displays the number of entries in the CMC trace log. ifconfig Displays the current CMC IP configuration. netstat Displays the routing table and the current connections.
Table 4-1. RACADM Subcommands (continued) Command Description sslcsrgen Generates and downloads the SSL CSR. sslresetcfg Regenerates the self-signed certificate used by the CMC Web GUI. testemail Forces the CMC to send an email over the CMC NIC. testtrap Forces the CMC to send an SNMP over the CMC NIC. Accessing RACADM Remotely Table 4-2 lists the options for the remote RACADM subcommands. Table 4-2.
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 getsysinfo racadm -i -r 192.168.0.
Before you try to access RACADM remotely, confirm that you have permissions to do so. To display your user privileges, type: racadm getconfig -g cfguseradmin -i n where n is your user ID (1–16). 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. See "Supported Web Browsers" on page 29 for more information.
Configuring CMC Network Properties Setting Up Initial Access to the CMC Before you can begin configuring the CMC, you must first configure the CMC network settings to allow the CMC to be managed remotely. This initial configuration assigns the TCP/IP networking parameters that enable access to the CMC. This section explains how to perform the initial CMC network configuration using RACADM commands. All of the configuration described in this section can be performed using the front panel LCD.
Viewing Current Network Settings To view a summary of NIC, DHCP, network speed, and duplex settings, type: racadm getniccfg or racadm getconfig -g cfgCurrentLanNetworking 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.
Enabling or Disabling DHCP for DNS IP Addresses By default, the CMC’s DHCP for DNS address feature is disabled. When enabled, this feature obtains the primary and secondary DNS server addresses from the DHCP server. Using this feature, you do not have to configure static DNS server IP addresses.
where is a string of up to 63 alphanumeric characters and hyphens; the name must begin with a letter. For example, cmc-1, d-345. • DNS Domain Name. The default DNS domain name is a single blank character. To set a DNS domain name, type: racadm config -g cfgLanNetworking -o cfgDNSDomainName where is a string of up to 254 alphanumeric characters and hyphens; the DNS domain name must begin with a letter. For example: p45, a-tz-1, r-id-001.
Setting the SMTP Server IP Address You can enable the CMC to send email alerts using Simple Mail Transfer Protocol (SMTP) to a specified IP address. To enable this feature, type: racadm config -g cfgRemoteHosts -o cfgRhostsFwUpdateIpAddr where is the IP address of the network SMTP server.
Using RACADM to Configure Users Before You Begin You can configure up to 16 users in the CMC property database. Before you manually enable a CMC user, verify if any current users exist. If you are configuring a new CMC or you ran the RACADM racresetcfg command, the only current user is root with the password calvin. The racresetcfg subcommand resets the CMC back to the original defaults.
specify any number of groups/objects to write, the index cannot be specified. A new user is added to the first available index. This behavior allows more flexibility in configuring a second CMC with the same settings as the main CMC. Adding a CMC User To add a new user to the CMC configuration, you can use a few basic commands. Perform the following procedures: 1 Set the user name. 2 Set the password. 3 Set the user privileges.
Enabling a CMC User With Permissions To enable a user with specific administrative permissions (role-based authority), first locate an available user index by performing the steps in "Before You Begin" on page 82. Next, type the following command lines with the new user name and password. NOTE: See Table B-1 for a list of valid bit mask values for specific user privileges. The default privilege value is 0, which indicates the user has no privileges enabled.
1 Use RACADM to query the target CMC that contains the desired configuration. NOTE: The generated configuration file is myfile.cfg. You can rename the file. NOTE: The .cfg file does not contain user passwords. When the .cfg file is uploaded to the new CMC, you must re-add all passwords. Open a Telnet/SSH text console to the CMC, log in, and type: racadm getconfig -f myfile.cfg NOTE: Redirecting the CMC configuration to a file using getconfig -f is only supported with the remote RACADM interface.
Creating a CMC Configuration File The CMC configuration file, .cfg, is used with the racadm config -f .cfg command to create a simple text file. The command allows you to build a configuration file (similar to an .ini file) and configure the CMC from this file. You may use any file name, and the file does not require a .cfg extension (although it is referred to by that designation in this subsection). NOTE: For more information about the getconfig subcommand, see "getconfig" on page 332.
• Use the racresetcfg subcommand to configure both CMCs with identical properties. Use the racresetcfg subcommand to reset the CMC to original defaults, and then run the racadm config -f .cfg command. Ensure that the .cfg file includes all desired objects, users, indexes, and other parameters. See "CMC Property Database Group and Object Definitions" on page 385 for a complete list of objects and groups.
The following example displays a group name, object, and the object’s property value: [cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object name} {object value} • All parameters are specified as "object=value" pairs with no white space between the object, =, or value. White spaces that are included after the value are ignored. A white space inside a value string remains unmodified. Any character to the right of the = (for example, a second =, a #, [, ], and so on) is taken as-is.
To view the contents of an indexed group, use the following command: racadm getconfig -g -i • For indexed groups the object anchor must be the first object after the [ ] pair. The following are examples of the current indexed groups: [cfgUserAdmin] cfgUserAdminUserName= If you type racadm getconfig -f .cfg, the command builds a .cfg file for the current CMC configuration.
# comment, the rest of this line is ignored cfgNicGateway=10.35.9.1 The command racadm config -f .cfg parses the file and identifies any errors by line number. A correct file will update the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update. Use this file to download company-wide changes or to configure new systems over the network with the command, racadm getconfig -f .cfg.
Table 4-3. Using the Serial and RACADM Commands: Frequently Asked Questions (continued) Question Answer When I use the RACADM subcommands, I get errors that I do not understand. You may encounter one or more of the following errors when using RACADM: • Local error messages — Problems such as syntax, typographical errors, and incorrect names. Example: ERROR: Use the RACADM help subcommand to display correct syntax and usage information.
• gettracelog/gettraclog/getsel – • getsensorinfo – • • • -s and -G deprecated serveraction – -s is now -m to specify a server – -A applies the serveraction command to all servers in the enclosure – graceshutdown deprecated fwupdate – added {-f } to specify FTP server IP address and username and password – added -c to cancel firmware update getpbinfo – • -A and -o do not generate additional output; provide backwards compatibility for existing
Using the CMC Web Interface The CMC provides a Web interface that enables you to configure the 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.
Logging In NOTE: To log in to the CMC, you must have a CMC account with Log In to CMC privilege. NOTE: The default CMC user name is root, and the password is calvin. The root account is the default administrative account that ships with the CMC. For added security, Dell strongly recommends that you change the default password of the root account during initial setup. NOTE: The CMC does not support extended ASCII characters, such as ß, å, é, ü, or other characters used primarily in non-English languages.
Configuring Basic CMC Settings Setting the Chassis Name You can set the name used to identify the chassis on the network. (The default name is "Dell Rack System.") For example, an SNMP query on the chassis name will return the name you configure. To set the chassis name: 1 Log in to the CMC Web interface. The Component 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.
Figure 5-1. Example of Chassis Graphics in the Web Interface The Component Health page provides an overall health status for the chassis, primary and stand-by CMCs, iKVM, PSUs, fans, and I/O modules (IOMs). The Chassis Summary page provides a text-based overview of the chassis, primary and stand-by CMCs, iKVM, and IOMs. For instructions on viewing chassis and components summaries, see "Viewing Chassis Summaries" on page 295.
Viewing the Health Status of All Servers The health status for all servers can be viewed in two ways: from the Chassis Graphics section on the Chassis Status page or the Servers Status page. Chassis Graphics provides a graphical overview of all servers installed in the chassis. To view health status for all servers using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed.
Table 5-1. All Servers Status Information (continued) Item Description Health OK Indicates that the server is present and communicating with the CMC. Informational Displays information about the server when no change in health status has occurred. Health (continued) Name Warning Indicates that only warning alerts have been issued, and corrective action must be taken within the time frame set by the administrator.
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 printable ASCII characters (ASCII codes 32 through 126), excluding the double quote (", ASCII 34).
NOTE: The slot name setting in the CMC Web interface always overrides any change you make to the display name in the iDRAC interface. To edit a slot name: 1 Log in to the CMC Web interface. 2 Select Servers in the Chassis menu in the system tree. 3 Click the Setup tab. 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.
Table 5-2. Boot Devices (continued) Boot Device Description 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. Virtual CD/DVD Boot from a virtual CD/DVD drive or CD/DVD ISO image. The optical drive or ISO image file is located on another computer or disk available on the management network and is attached using the iDRAC GUI console viewer.
4 If you want the server to boot from the selected device every time it boots, uncheck the Boot Once checkbox for the server. If you want the server to boot from the selected device only on the next boot cycle, select the Boot Once checkbox for the server. 5 Click Apply. 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 Status page or the Server Status page.
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 Version 1.00 User’s Guide. To view the health status of an individual server: 1 Log in to the CMC Web interface. 2 Expand Servers 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-3. Individual Server Status Information (continued) Item Description Health OK Indicates that the server is present and communicating with the CMC. In the event of a communication failure between the CMC and the server, the CMC cannot obtain or display health status for the server. Informational Displays information about the server when no change in health status (OK, Warning, Severe) has occurred.
Viewing the Health Status of IOMs 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.
The health status of the fans can be viewed in two ways: from the Chassis Graphics section on the Chassis Status page or the Fans Status page. The Chassis Graphics page provides a graphical overview of all fans installed in the chassis. To view health status for all fans using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed. The right section of Chassis Graphics depicts the rear view of the chassis and contains the health status of all fans.
Table 5-4 provides descriptions of the information provided on the Fans Status page. Table 5-4. Fans Health Status Information Item Description Present Indicates whether the fan unit is present (Yes or No). Health OK Indicates that the fan unit is present and communicating with the CMC. In the event of a communication failure between the CMC and the fan unit, the CMC cannot obtain or display health status for the fan unit. Severe Indicates at least one Failure alert has been issued.
To view health status for the iKVM using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed. The right 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 color of the iKVM subgraphic: • Green - iKVM is present, powered on and communicating with the CMC; there is no indication of an adverse condition.
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 right 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 the CMC; there is no indication of an adverse condition.
Table 5-5 provides descriptions of the information provided on the Power Supply Status page. Table 5-5. Power Supply Health Status Information Item Description Present Indicates whether the power supply is present (Yes or No). Health OK Indicates that the PSU is present and communicating with the CMC. Indicates that the health of the PSU is OK. In the event of a communication failure between the CMC and the fan unit, the CMC cannot obtain or display health status for the PSU.
To view the health status of the temperature probes: 1 Log in to the CMC Web interface. 2 Select Temperature Sensors in the system tree. The Temperature Sensors Information page displays. Table 5-6 provides descriptions of the information provided on the Temperature Sensors Information page. Table 5-6. Temperature Sensors Health Status Information Item Description Present Indicates whether the sensor is present (Yes) or absent (No) in the chassis.
NOTE: Refer to "Using FlexAddress" on page 169 for more information on the FlexAddress feature. WWN/MAC Addresses The WWN/MAC Address section displays WWN/MAC information for all servers. 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. Fabric displays the type of the I/O fabric.
NOTE: If you have two CMCs (primary and standby) on the chassis, and they are both connected to the network, the standby CMC automatically assumes the network settings in the event of failover of the primary CMC. 1 Log in to the Web interface. 2 Click the Network/Security tab. 3 Configure the CMC network settings described in Table 5-7. 4 Click Apply Changes. To configure IP range and IP blocking settings, click the Advanced Settings button (see "Configuring CMC Network Security Settings" on page 118).
Table 5-7. 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 NIC Enables the NIC of the CMC. Default: Enabled. If this option is checked: • The CMC communicates with and is accessible over the computer network. • The Web interface, CLI (remote RACADM), WSMAN, Telnet, and SSH associated with the CMC are available.
Table 5-7. Network Settings (continued) Setting Description Use DHCP (For CMC NIC IP Address) Enables the CMC 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 CMC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. The CMC will always have a unique IP address allotted over your network.
Table 5-7. Network Settings (continued) Setting Description Use DHCP to Obtain DNS Server Addresses Obtains the primary and secondary DNS server addresses from the DHCP server instead of the static settings. Default: Unchecked (disabled) by default NOTE: If Use DHCP (For NIC IP Address) is enabled, then enable the Use DHCP to Obtain DNS Server Addresses property. If this option is checked, the CMC retrieves its DNS IP address automatically from a DHCP server on your network.
Table 5-7. 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 number 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-7. Network Settings (continued) Setting Description Duplex Mode Set the duplex mode to full or half to match your network environment. Implications: If Auto Negotiation is turned On for one device but not the other, then the device using auto negotiation can determine the network speed of the other device, but not the duplex mode. In this case, duplex mode defaults to the half duplex setting during auto negotiation. such a duplex mismatch will result in a slow network connection.
Table 5-8. 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 the CMC only from clients or management stations whose IP addresses are within the userspecified 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.
Adding and Configuring CMC Users To manage your system with the 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-9. User Types Privilege Description CMC Login User Users who have the CMC Login User privilege can log in to CMC. A user with only the login privilege can view all of the CMC data but cannot add or modify data or execute commands. It is possible for a user to have other privileges without the login privilege. This feature is useful when a user is temporarily disallowed to login. When that user’s login privilege is restored, the user retains all the other privileges previously granted.
Table 5-9. User Types (continued) Privilege Description User Configuration Administrator Users who have the User Configuration Administrator privilege can: • Add a new user • Delete an existing user • Change a user's password • Change a user's privileges • Enable or disable a user's login privilege but retain the user's name and other privileges in the database. Clear Logs Administrator CMC users who have the Clear Administrator privilege can clear the hardware log and CMC log.
Table 5-9. User Types (continued) Privilege Description Server Administrator The Server Administrator privilege is a blanket privilege granting a CMC user all rights to perform any operation on any servers present in the chassis. When a user with CMC 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-9. User Types (continued) Privilege Description Server Administrator (continued) Server Configuration Administrator: • Set IP address • Set gateway • Set subnet mask • Set first boot device User Configuration Administrator: • Set iDRAC root password • iDRAC reset Server Control Administrator: • Power on • Power off • Power cycle • Graceful shutdown • Server Reboot Test Alert User CMC users who have the Test Alert User privilege can send test alert messages.
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-10.
Table 5-10. 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 No assigned permissions. Table 5-11.
Table 5-11.
NOTE: For added security, Dell strongly recommends that you change the default password of the root (User 1) account. The root account is the default administrative account that ships with the CMC. To change the default password for the root account, click User ID 1 to open the User Configuration page. Help for that page is available through the Help link at the top right corner of the page.
Table 5-12. General User Settings (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. Any user logging in after you apply the new user name will be able to see the change immediately.
To refresh the contents of the User Configuration page, click Refresh. To print the contents of the User Configuration page, click Print. Configuring and Managing Microsoft Active Directory Certificates NOTE: To configure Active Directory settings for the CMC, you must have Chassis Configuration Administrator privilege.
Table 5-13. Active Directory Main Menu Page Options (continued) Field Description Download Certificate Download a CMC server certificate to your management station or shared network using Windows Download Manager. 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.
Table 5-14. Active Directory Common Settings Properties Setting Description Root Domain Name Specifies the domain name used by Active Directory. The root domain name is the fully qualified root domain name for the forest. 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.
7 If you selected Extended Schema, type the following required information in the Extended Schema Settings section, and then proceed directly to step 9. If you selected Standard Schema, proceed to step 8. • CMC Device Name – The name that uniquely identifies the CMC card in Active Directory. The CMC name must be the same as the common name of the new CMC object you created in your Domain Controller. The name must be a 1–256 character ASCII string with no spaces between characters. Default: null (empty).
Table 5-15. Active Directory Schema Options (continued) Setting Description Use Extended Schema Uses Extended Schema with Active Directory, which uses Dell-defined Active Directory objects. Before configuring CMC to use the Active Directory Extended Schema option, you must first configure the Active Directory software: 1 Extend the Active Directory schema. 2 Extend the Active Directory Users and Computers Snapin. 3 Add CMC users and their privileges to Active Directory.
To configure the Role Groups for Active Directory, click the individual Role Group (1–5). See Table 5-10 and Table 5-9). NOTE: To save the settings on the Active Directory Configuration and Management page, you have to click Apply before proceeding to the Custom Role Group page. Uploading an Active Directory Certificate Authority-Signed Certificate From the Active Directory Main Menu page: 1 Select Upload AD Certificate, and then click Next. The Certificate Upload page displays.
Table 5-16. Active Directory CA Certificate Information (continued) Field Description Valid From Certificate issue date. Valid To Certificate expiration date. To refresh the contents of the View Active Directory CA Certificate page, click Refresh. To print the contents of the View Active Directory CA Certificate page, click Print.
This encryption process provides a high level of data protection. The CMC employs the 128-bit SSL encryption standard, the most secure form of encryption generally available for Internet browsers in North America. 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 the CMC to generate a new Certificate Signing Request (CSR).
NOTE: Any server certificate you upload must be current (not expired) and signed by a certificate authority. 1 Log in to the Web interface. 2 Click the Network/Security tab, and then click the SSL sub-tab. The SSL Main Menu page appears. Use the SSL Main Menu page options to generate a CSR to send to a certificate authority. The CSR information is stored on the CMC firmware.
To obtain a secure server certificate for the 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-18. 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-18. 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 email address. You may type any email address you want to have associated with the CSR. The email address must be valid, containing the at (@) sign (example: name@xyzcompany.com). Uploading a Server Certificate 1 From the SSL Main Menu page, select Upload Server Certificate, and then click Next.
Table 5-19. Certificate Information (continued) Field Description notBefore Issue date of the certificate notAfter Expiration date of the certificate To refresh the contents of the View Server Certificate page, click Refresh. To print the contents of the View Server Certificate page, click Print. Managing Sessions The Sessions page displays all current instances of connections to the chassis and allows you to terminate any active session.
Table 5-20. Sessions Properties (continued) Property Description Terminate Allows you to terminate any of the sessions listed, except for your own. To terminate the associated session, click the trash can icon . This column is displayed only if you have Chassis Configuration Administrator privileges. To terminate the session, click the trash can icon on the line that describes the session.
4 Configure the following services as required: • CMC serial console (Table 5-21) • Web server (Table 5-22) • SSH (Table 5-23) • Telnet (Table 5-24) • Remote RACADM (Table 5-25) 5 Click Apply; update all default time outs and maximum time out limits. Table 5-21. CMC Serial Console Settings Setting Description Enabled Enables Telnet console interface on the CMC.
Table 5-21. CMC Serial Console Settings (continued) Setting Description Escape Key Allows you to specify the Escape key combination that terminates serial/text console redirection when using the connect com2 command. Default: ^\ (Hold and type a backslash (\) character) NOTE: The caret character ^ represents the key.
Table 5-22. Web Server Settings Setting Description Enabled Enables Web Server services (access through remote RACADM and the Web interface) for the CMC. Default: Checked (enabled) Max Sessions Indicates the maximum number of simultaneous Web user interface sessions allowed for the chassis. A change to the Max Sessions property takes effect at the next login; it does not affect current Active Sessions (including your own).
Table 5-22. Web Server Settings (continued) Setting Description HTTP Port Number Indicates the default port used by the CMC that listens for a server connection. NOTE: When you provide the HTTP address on the browser, the Web server automatically redirects and uses HTTPS.
Table 5-23. SSH Settings Setting Description Enabled Enables the SSH on the 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-24. Telnet Settings Setting Description Enabled Enables Telnet console interface on the CMC. Default: Unchecked (disabled) Max Sessions Indicates 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-25. Remote RACADM Settings Setting Description Enabled Enables the remote RACADM utility access to the CMC. Default: Checked (enabled) Max Sessions Indicates 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).
Managing Firmware This section describes how to use the Web interface to update firmware. The following components can be updated using the GUI or RACADM commands: • CMC - primary and standby. • iKVM • iDRAC (boot-block mode only) • 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.
To view firmware versions: 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 93). 2 Click Chassis in the system tree. 3 Click the Update tab. The Updatable Components page appears. Updating Firmware NOTE: To update firmware on the CMC, you must have Chassis Configuration Administrator privilege. NOTE: The firmware update retains the current CMC and iKVM settings.
NOTE: To avoid disconnecting other users during a reset, notify authorized users who might log in to the CMC and check for active sessions by viewing the Sessions page. To open the Sessions page, select Chassis in the tree, click the Network/Security tab, and then click the Sessions sub-tab. Help for that page is available through the Help link at the top right corner of the page. NOTE: When transferring files to and from the CMC, the file transfer icon spins during the transfer.
• Update status displays in the Update State field; this field is automatically updated during the file transfer process. Certain older browsers do not support these automatic updates. To manually refresh the Update State field, click Refresh. NOTE: The update may take several minutes for the CMC. 5 For a standby (secondary) CMC, when the update is complete the Update State field displays "Done".
on connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer displays. Additional items to note: • 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.
on connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer displays. Additional items to note: • 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.
on connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer displays. Additional items to note: • 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: If the iDRAC MAC address has been lost or corrupted, it must be set to a valid address before you can recover the iDRAC firmware using the CMC. You can use the IPMI config params command to set a MAC address. The MAC address is the fifth parameter of the command. It must be set to a 6-byte address that is unique on your management network. Refer to the documentation for your IPMI utility (for example, ipmitool or ipmish) for help executing the command. Follow these steps to update the iDRAC firmware.
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 will be displayed on the Web interface: Optional feature not installed. See the Dell Chassis Management Controller Users Guide for information on the chassis-based WWN and MAC address administration feature. To purchase this feature, please contact Dell at www.dell.com.
Use the following steps to display a FlexAddress status overview for each server module: 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 93). 2 Click Servers in the system tree. Click the Properties tab, WWN/MAC sub-tab. 3 The FlexAddress Summary page is displayed. This page allows you to view the WWN configuration and MAC addresses for all slots in the chassis.
Use the following steps to view FlexAddress server information: 1 Log in to the Web interface (see "Accessing the CMC Web Interface" on page 93). 2 Expand Servers 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. 4 Click the Setup tab, and the FlexAddress sub-tab. The FlexAddress Status page is displayed. This page allows you to view the WWN configuration and MAC addresses for the selected server.
Health OK Indicates that FlexAddress is present and providing status to the CMC. In the event of a communication failure between the CMC and FlexAddress, the CMC cannot obtain or display health status for FlexAddress. Informational Displays information about FlexAddress when no change in health status (OK, Warning, Severe) has occurred. Warning Indicates that only warning alerts have been issued, and corrective action must be taken within the time frame set by the administrator.
5 For additional information, click the Help link and review "Using FlexAddress" on page 169. Configuring FlexAddress If you purchase FlexAddress with your chassis, it will be 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 for this document.
4 The Select Fabrics for Chassis-Assigned WWN/MACs displays a check box for Fabric A, Fabric B, and Fabric C. 5 Click the check box for each fabric you want to enable FlexAddress on. To disable a fabric, click the check box to clear the selection. NOTE: If no fabrics are selected, FlexAddress will 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 Apply to save the changes. For additional information, click the Help link and review "Using FlexAddress" on page 169. Frequently Asked Questions Table 5-26 lists frequently asked questions and answers. Table 5-26. Managing and Recovering a Remote System: Frequently Asked Questions 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 the CMC.
Table 5-26. Managing and Recovering a Remote System: Frequently Asked Questions (continued) Question Answer For more information about generating CSRs and issuing certificates, see "Securing CMC Communications Using SSL and Digital Certificates" on page 136. 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-26. Managing and Recovering a Remote System: Frequently Asked Questions (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
Using FlexAddress The FlexAddress feature is an optional upgrade introduced in CMC 1.1 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 MAC IDs as part of the manufacturing process.
Activating FlexAddress FlexAddress is delivered on a Secure Digital (SD) card that must be inserted into the CMC to provide the chassis-assigned WWN/MAC IDs. To activate the FlexAddress feature, perform several required updates; 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: If the CMC firmware that supports FlexAddress (version 1.10 or later) is not installed, the feature will not be activated. See the Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification document for SD card installation instructions. NOTE: The SD card contains a FlexAddress feature. Data contained on the SD card is encrypted and may not be duplicated or altered in any way as it may inhibit system function and cause the system to malfunction.
The following table lists the status messages returned by the command. Table 6-1. Status Messages Returned by featurecard -s Command Status Message Actions No feature card inserted. Check the CMC to verify that the SD card was properly inserted. In a redundant CMC configuration, make sure the CMC with the SD feature card installed is the active CMC and not the standby CMC. The feature card inserted is valid and No action required.
If there are no active features on the chassis, the command will return a message: racadm feature -s No features active on the chassis. After you have run both commands, the FlexAddress feature activation is verified. For further information on the RACADM commands, see "feature" on page 326 and "featurecard" on page 327. Deactivating FlexAddress The FlexAddress feature can be deactivated and the SD card returned to a pre-installation state using a RACADM command.
Viewing FlexAddress Status Using the CLI You can use the command line interface to view FlexAddress status information. You can view status information for the entire chassis or for a particular slot.
= = A, B, C 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 "setflexaddr" on page 370.
Troubleshooting FlexAddress This section contains troubleshooting information for FlexAddress. 1 If a feature card is removed, what will happen? Nothing will happen. Feature cards can be removed and stored or may be left in place. 2 If a feature card that was used in one chassis is removed and put into another chassis, what will happen? The Web interface will display an error that states: This feature card was activated with a different chassis. It must be removed before accessing the FlexAddress feature.
Current Chassis Service Tag = XXXXXXXX Feature Card Chassis Service Tag = YYYYYYYY Dell Service will need to program the original chassis service tag back into the chassis and reset the CMC. 5 What if I have two feature cards installed in my redundant CMC system? Will I get an error? The feature card in the active CMC will be active and installed in the chassis. The second card will be ignored by CMC. 6 Does the SD card have a write protection lock on it? Yes it does.
10 In a chassis with redundant CMCs, if you are replacing a CMC unit with one that has firmware prior to 1.10, the following procedure must be used to ensure the current FlexAddress feature and configuration will NOT be removed. a Ensure the active CMC firmware is always version 1.10 or later. b Remove the standby CMC and insert the new CMC in its place. c From the Active CMC, upgrade the standby CMC firmware to 1.10 later. NOTE: If a user does not update the standby CMC firmware to 1.
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.
You may use one copy of the Software on only one computer at a time. If you have multiple licenses for the Software, you may use as many copies at any time as you have licenses. "Use" means loading the Software in temporary memory or permanent storage on the computer. Installation on a network server solely for distribution to other computers is not "use" if (but only if) you have a separate license for each computer to which the Software is distributed.
implied warranty, so this limitation may not apply to you. The entire liability of Dell and its suppliers, and your exclusive remedy, shall be (a) return of the price paid for the Software or (b) replacement of any disk not meeting this warranty that is sent with a return authorization number to Dell, at your cost and risk. This limited warranty is void if any disk damage has resulted from accident, abuse, misapplication, or service or modification by someone other than Dell.
THE COPYRIGHT HOLDERS, OR THE CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTUTUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILTIY, WHETHER IN CONTRACT, STRICT LIABITLY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILTIY OF SUCH DAMAGE. .U.S.
Using FlexAddress
Using the CMC With Microsoft Active Directory 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, you can configure the software to provide access to the CMC. This allows you to add and control CMC user privileges to your existing users in your Active Directory software.
Extended Schema Overview There are two ways to enable Extended Schema Active Directory: • Using the CMC Web interface. For instructions, see "Configuring the CMC With Extended Schema Active Directory and the Web Interface" on page 201. • Using the RACADM CLI tool. For instructions, see "Configuring the CMC With Extended Schema Active Directory and RACADM" on page 203. Active Directory Schema Extensions The Active Directory data is a distributed database of Attributes and Classes.
The Association property links together users or groups with a specific set of privileges to one or more RAC devices. This model provides an Administrator maximum flexibility over the different combinations of users, RAC privileges, and RAC devices on the network without adding too much complexity.
Figure 7-1. Typical Setup for Active Directory Objects Association Object User(s) Group(s) Privilege Object RAC Device Object(s) RAC Privilege Object 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).
Figure 7-2. Setting Up Active Directory Objects in a Single Domain AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 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.
Domain1, and user2 and user 3 are in Domain2. In this scenario, configure user1 and user 2 with administrator privileges to both CMCs and configure user3 with login privileges to the RAC2 card. Figure 7-3. 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.
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 the CMC: 1 Extend the Active Directory schema (see "Extending the Active Directory Schema" on page 191).
The LDIF files and Dell Schema Extender are located on your Dell Systems Management Tools and Documentation DVD in the following respective directories: • :\SYSMGMT\ManagementStation\support\ OMActiveDirectory_Tools\\LDIF Files • :\SYSMGMT\ManagementStation\support\ OMActiveDirectory_ Tools\\Schema Extender To use the LDIF files, see the instructions in the readme included in the LDIF_Files directory.
Table 7-1. Class Definitions for Classes Added to the Active Directory Schema Class Name Assigned Object Identification Number (OID) dellRacDevice 1.2.840.113556.1.8000.1280.1.1.1.1 dellAssociationObject 1.2.840.113556.1.8000.1280.1.1.1.2 dellRACPrivileges 1.2.840.113556.1.8000.1280.1.1.1.3 dellPrivileges 1.2.840.113556.1.8000.1280.1.1.1.4 dellProduct 1.2.840.113556.1.8000.1280.1.1.1.5 Table 7-2. dellRacDevice Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 7-4. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines Authorization Rights (privileges) for the CMC device. Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsTestAlertUser dellIsDebugCommandAdmin dellPermissionMask1 dellPermissionMask2 Table 7-5. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 7-7. List of Attributes Added to the Active Directory Schema Assigned OID/Syntax Object Identifier Single Valued Attribute: dellPrivilegeMember Description: List of dellPrivilege objects that belong to this attribute. OID: 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellProductMembers Description: List of dellRacDevices objects that belong to this role.
Table 7-7. List of Attributes Added to the Active Directory Schema (continued) Assigned OID/Syntax Object Identifier Single Valued Attribute: dellIsUserConfigAdmin Description: TRUE if the user has User Configuration Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.5 TRUE Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: delIsLogClearAdmin Description: TRUE if the user has Clear Logs Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.
Table 7-7. List of Attributes Added to the Active Directory Schema (continued) Assigned OID/Syntax Object Identifier Single Valued Attribute: dellRacType Description: This attribute is the Current Rac Type for the dellRacDevice object and the backward link to the dellAssociationObjectMembers forward link. OID: 1.2.840.113556.1.8000.1280.1.1.2.13 TRUE Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.
For more information about the Active Directory User’s and Computers Snap-In, see your Microsoft documentation. Installing the Administrator Pack You must install the Administrator Pack on each system that is managing the Active Directory CMC Objects. If you do not install the Administrator Pack, you cannot view the Dell RAC Object in the container.
Creating a RAC Device Object 1 In the MMC Console Root window, right-click a container. 2 Select New→ Dell RAC Object. The New Object window appears. 3 Type a name for the new object. The name must be identical to the CMC Name that you will type in step 8a of "Configuring the CMC With Extended Schema Active Directory and the Web Interface" on page 201. 4 Select RAC Device Object. 5 Click OK.
For example, if you select Universal, the association objects are only available when the Active Directory Domain is functioning in Native Mode or above. 1 In the Console Root (MMC) window, right-click a container. 2 Select New→ Dell RAC Object. This opens the New Object window. 3 Type a name for the new object. 4 Select Association Object. 5 Select the scope for the Association Object. 6 Click OK.
Adding RAC Devices or RAC Device Groups To add RAC devices or RAC device groups: 1 Select the Products tab and click Add. 2 Type the RAC device or RAC device group name and click OK. 3 In the Properties window, click Apply and click OK. Configuring the CMC With Extended Schema Active Directory and the Web Interface 1 Log in to the CMC Web interface. 2 Select Chassis in the system tree. 3 Click the Network/Security tab, and then click the Active Directory subtab.
7 Select the Use Extended Schema radio button in the Active Directory Schema Selection area. 8 In the Extended Schema Settings section: a Type the CMC Name. The CMC Name uniquely identifies the CMC card in Active Directory. The CMC Name must be the same as the common name of the new CMC object you created in your Domain Controller. The CMC Name must be a 1–256 character ASCII string with no spaces between characters. b Type the CMC Domain Name (example: cmc.com).
16 If Use DHCP (for NIC IP Address) is enabled (checked), do one of the following: • Select Use DHCP to Obtain DNS Server Addresses to enable the DNS server addresses to be obtained automatically by the DHCP server., or • 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. 17 Click Apply Changes.
Optional: If you want to specify an LDAP or Global Catalog server instead of using the servers returned by the DNS server to search for a user name, type the following command to enable the Specify Server option: racadm config -g cfgActiveDirectory -o cfgADSpecifyServerEnable 1 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.
• If DHCP is disabled on the CMC, or if DHCP is enabled but you want to specify your DNS IP address manually, type following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSServer2 The Extended Schema feature configuration is complete.
Figure 7-4.
Table 7-8.
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 120. There are two ways to enable Standard Schema Active Directory: • With the CMC Web interface. See "Configuring the CMC With Standard Schema Active Directory and Web Interface" on page 208. • With the RACADM CLI tool. See "Configuring the CMC With Standard Schema Active Directory and RACADM" on page 211.
5 In the Common Settings section: a Select the Enable Active Directory check box. b Type the ROOT Domain Name. The ROOT Domain Name is the fully qualified root domain name for the forest. 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.
13 Click Apply to save the Role Group settings. 14 Click Go Back To Active Directory Configuration and Management. 15 Click Go Back To Active Directory Main Menu. 16 Upload your domain forest Root certificate authority-signed certificate into the CMC. a Select the Upload Active Directory CA Certificate check box and then click Next. b In the Certificate Upload page, type the file path of the certificate or browse to the certificate file.
Configuring the 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 Telnet/SSH text console to the CMC, log in, 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
• If DHCP is disabled on the 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 config -g cfgLanNetworking -o cfgDNSServer2 Frequently Asked Questions Table 7-9 lists frequently asked questions and answers about using Active Directory with the CMC. Table 7-9.
Table 7-9. Using CMC With Active Directory: Frequently Asked Questions (continued) Question Answer Can these Dell-extended objects (Dell Association Object, Dell RAC Device, and Dell Privilege Object) be in different domains? The Association Object and the Privilege Object must be in the same domain. The Dellextended Active Directory Users and Computers Snap-In forces you to create these two objects in the same domain. Other objects can be in different domains.
Table 7-9. Using CMC With Active Directory: Frequently Asked Questions (continued) Question Answer What can I do if I cannot log into the CMC using Active Directory authentication? How do I troubleshoot the issue? 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 the CMC using your local credentials.
Power Management Overview The M1000e chassis ships with either three power supply units (PSUs) or six, the maximum. If your chassis has three PSUs, you can add up to three more. The PSUs supply power to the chassis and all the modules in the chassis: CMC, IOM, iKVM, fans, front panel LCD and servers. The CMC manages the power budget for all the chassis modules.
Figure 8-1. Chassis With Six-PSU Configuration PSUs Dynamic PSU Engagement Dynamic PSU engagement is a configurable option that enables the CMC to conserve power by powering-off unused PSUs and keeping them in Standby mode in case more power is required. This saves power by increasing the utilization of the PSUs that remain active so that they are used more efficiently.
To maintain optimal efficiency, the CMC uses this information to determine how many PSUs are required to power a given configuration and place excess PSUs on standby. If new modules are installed, the CMC may, depending on need and optimization, turn on new supplies. Redundancy Policies The redundancy policy is a configurable set of properties that determine how the CMC manages power to the chassis.
NOTICE: In AC Redundancy mode, a difference in the number of PSUs between the two AC grids (for example, three PSUs on one AC grid and two on the other AC grid) will cause a degradation in the redundancy. Power Supply Redundancy The capacity of a PSU in the chassis is kept as a spare, ensuring that a failure of any one PSU will not cause the servers or chassis to power-down. Power Supply Redundancy mode requires four PSUs to operate correctly; any additional PSUs will not be utilized.
NOTE: To set the redundancy policy, see "Configuring Power Budget and Redundancy" on page 233. Figure 8-2.
Figure 8-3. No Redundancy Power Grid #1 Power Supply #1 Power Supply #2 Power Supply #3 Empty Slot #4 Empty Slot #5 Empty Slot #6 Chassis DC Power Bus Single Power Grid: No protection against grid or power supply failure New Server Engagement Policy When a new server is powered on, the CMC may need to decrease power to lower priority servers to allow more power for the new server if adding the new server exceeds the power available for the system.
• If enough power is freed by reducing power to the existing servers, the freed power is allocated to the new server and the server is allowed to power up. Table 8-2 describes the actions taken by the CMC when a new server is powered on in the scenario described above. Table 8-2.
Table 8-3. Chassis Impact from PSU Failure or Removal (continued) PSU Configuration Dynamic PSU Firmware Response Engagement No Redundancy Enabled Decrease power to low priority servers, if needed. PSU Removals With a No Redundancy Policy The CMC may begin conserving power when a user removes a PSU or a PSU AC cord. The CMC decreases power to the lower priority servers until power allocation is supported by the remaining PSUs in the chassis.
Viewing the Health Status of the PSUs The Power Supply Status page displays the status and readings of the PSUs associated with the chassis. For more information about CMC power management, see "Power Management" on page 215. Using the Web Interface The PSU health status can be viewed in two ways: from the Chassis Graphics section on the Chassis Status page or the Power Supply Status page. The Chassis Graphics page provides a graphical overview of all PSUs installed in the chassis.
Table 8-4 provides descriptions of the information provided on the Power Supply Status page. Table 8-4. Power Supply Health Status Information Item Description Present Indicates whether the PSU is Present or Absent. Health OK Indicates that the PSU is present and communicating with the CMC. In the event of a communication failure between the CMC and the fan unit, the CMC cannot obtain or display health status for the PSU.
Using the Web Interface NOTE: To perform power management actions, you must have Chassis Control Administrator privilege. 1 Log in to the CMC Web interface. 2 Select Chassis in the system tree. 3 Click the Power Management tab. The Power Budget Status page displays. Table 8-5 through Table 8-11 describe the information displayed on the Power Budget Status page. See "Configuring Power Budget and Redundancy" on page 233 for information about configuring the settings for this information.
Table 8-5. Real-Time Power Statistics (continued) Item Description Peak System Power Start Displays the date and time recorded when the peak system 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. This value is reset with the Reset Peak/Min Power Statistics button and also when the CMC resets or fails over.
Table 8-5. Real-Time Power Statistics (continued) Item Description System Idle Power Displays the estimated power consumption of the chassis when it is in idle state. The idle state is defined as the state of the chassis while it's ON and all modules are consuming power while in the idle state. This is an estimated value and not a measured value.
Table 8-6. Real-Time Energy Statistics Status (continued) Item Description System Energy Start Time Displays the date and time recorded when the system energy consumption value was last cleared, and the new measurement cycle began. 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 8-8. System Power Policy Configuration Item Description System Input Power Cap Displays the user configured maximum power consumption limit for the entire system (chassis, CMC, servers, I/O modules, power supply units, iKVM, and fans). The CMC will enforce this limit via reduced server power allocations, or by powering off lower priority server modules. The value for system input power cap is displayed in watts, BTU/h and percent units.
Table 8-8. System Power Policy Configuration (continued) Item Description Redundancy Policy Indicates the current redundancy configuration: AC Redundancy, Power Supply Redundancy, and No Redundancy. AC Redundancy — Power input is load-balanced across all PSUs. Three of the PSUs are connected to one AC grid and the other three are connected to another grid. When the system is running optimally in AC Redundancy mode, power is load-balanced across all active supplies.
Table 8-9. 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 8-10. 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. Type Displays the type of the server. Priority Indicates the priority level allotted to the server slot in the chassis for power budgeting.
Table 8-11. System Power Supplies Item Description Name Displays the name of the PSU in the format PS-n, where n, is the PSU number. Power State Indicates the power state of the PSU — On, Initializing, Online, Stand By, In Diagnostics, Failed, Redundant, 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.
Table 8-12. Configurable Power Budget/Redundancy Properties Item Description Surplus for Peak Performance The surplus for peak performance value is the difference between the System Input Power Cap and the Power Required for Peak Performance (sum of the Maximum Input Power Allocated to Servers and the Maximum Input Power Allocated to Chassis Infrastructure). The value for surplus for peak performance is indicated in both the watts and BTU/h units.
Table 8-12. Configurable Power Budget/Redundancy Properties (continued) 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 will fail.
Table 8-12. Configurable Power Budget/Redundancy Properties (continued) Item Description Redundancy Policy This option will allow you to select one the following options: • No Redundancy: Power from all three power supplies on one AC circuit (grid) is used to power-on the entire chassis, including the chassis, servers, I/O modules, iKVM, and CMC. NOTE: The No Redundancy mode uses only three power supplies at a time. If 3 PSUs are installed, then there is no backup available.
Table 8-12. Configurable Power Budget/Redundancy Properties (continued) Item Description Enable Dynamic Power Supply Engagement Enables (when checked) dynamic power management. In Dynamic Engagement mode, the power supplies are turned ON or OFF 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.
• To select a redundancy policy, type: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy where is 0 (No Redundancy), 1 (AC Redundancy), 2 (Power Supply Redundant). The default is 0. For example, the following command: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy 1 sets the redundancy policy to 1.
Using the Web Interface 1 Log in to the CMC Web interface. 2 Select Servers in the system tree. The Servers Status page appears. 3 Click the Power Management tab. 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.
5 Type a budget value of up to 7928 watts in the System Input Power Cap text field. NOTE: The power budget is limited to a maximum of three PSUs out of a total of six PSUs. If you attempt to set a AC power budget value that exceeds the power capacity of your chassis, the CMC will display a failure message. NOTE: When value changes are specified in watts, the submitted value will exactly reflect what is actually applied.
Throttling is executed in two cases: • Overall power consumption exceeds the configurable maximum power limit (see "Setting the Power Budget" on page 239) • A power failure occurs in a non-redundant configuration For information about assigning priority levels to servers, see "Executing Power Control Operations on the Chassis" on page 241. Executing Power Control Operations on the Chassis NOTE: To perform power management actions, you must have Chassis Control Administrator privilege.
NOTE: This action powers off the chassis (chassis, servers, IOMs, iKVM, and power supplies). The CMCs remain powered on, but in virtual standby state; a power supply unit and fans provide cooling for the CMCs in this state. The power supply will also provide power to the fans that will be running at low speed. • Power Cycle System (cold boot) — Powers off and then reboots the system (cold boot). This option is disabled if the chassis is already powered OFF.
Using the Web Interface 1 Log in to the CMC Web interface. 2 Select I/O Modules. The I/O Modules Status page displays. 3 Click the Power Management tab. The Power Control page displays. 4 Select the operation you want to execute (reset or power cycle) from the drop-down menu beside the IOM in the list. 5 Click Apply. A dialog box appears requesting confirmation. 6 Click OK to perform the power management action (for example, cause the IOM to power cycle).
4 Power Status displays the power status of the server (one of the following): • N/A - The CMC has not yet determined the power state of the server. • Off - Either the server is off or the chassis is off. • On - Both chassis and server are on. • Powering On - Temporary state between Off and On. When the action completes successfully, the Power State will be On. • Powering Off - Temporary state between On and Off. When the action completes successfully, the Power State will be Off.
Using the iKVM Module 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.
The CMC identifies a slot by assigning it a unique name. To change slot names using the CMC Web interface, see "Editing Slot Names" on page 99. To change a slot name using RACADM, see "setslotname" on page 376. Video The iKVM video connections support video display resolutions ranging from 640 x 480 at 60 Hz up to 1280 x 1024 at 60 Hz. Plug and Play The iKVM supports Display Data Channel (DDC) Plug and Play, which automates video monitor configuration, and is compliant with the VESA DDC2B standard.
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. If you have ACI and rear connections, the ACI connection takes precedence. Tiering Through the ACI Connection The iKVM allows tiered connections with servers and the iKVM’s CMC command line console, either locally through a Remote Console Switch port or remotely through the Dell RCS® software.
Table 9-1. OSCAR Keyboard and Mouse Navigation (continued) Key or Key Sequence Result Closes the current dialog box without saving changes and returns to the previous dialog box. In the Main dialog box, closes the OSCAR interface and returns to selected server. In a message box, it closes the pop-up box and returns to the current dialog box.
Configuring OSCAR Table 9-2 describes the features available from the OSCAR Setup menu for configuring your servers. Table 9-2. OSCAR Setup Menu Features Feature Purpose Menu Changes the server listing between numerically by slot or alphabetically by name. Security • Sets a password to restrict access to servers. • Enables a screen saver and set an inactivity time before the screen saver appears and set the screen save mode. Flag Changes display, timing, color, or location of the status flag.
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. To assign one or more key sequences for OSCAR activation: 1 Select a key sequence from the Invoke OSCAR menu. 2 Click OK. The default key to invoke OSCAR is .
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. NOTE: If you select Timed by itself, the flag is not displayed. 2 Select a flag color from the Display Color section. Options are black, red, blue, and purple.
• Standard USB pointing devices. • Self-powered USB 1.1 hubs connected to the local USB port on the iKVM. • Powered USB 2.0 hubs connected to the Dell M1000e chassis’ front panel console. NOTE: You can use multiple keyboards and mice on the iKVM local USB port. The iKVM aggregates the input signals. If there are simultaneous input signals from multiple USB keyboards or mice, it may have unpredictable results. NOTE: The USB connections are solely for supported keyboard, mouse, and USB hubs.
Viewing the Status of Your Servers The status of the servers in your chassis is indicated in the right columns of the Main dialog box. The following table describe the status symbols. Table 9-4. OSCAR Interface Status Symbols Symbols Description (Green dot.) Server is online. (Red X.) Server is offline or absent from chassis. (Yellow dot.) Server is not available. (Green A or B.) Server is being accessed by the user channel indicated by the letter: A=rear panel, B=front panel.
• To disconnect the user from a server: Press to access OSCAR and then click Disconnect. or Press and then <0>. This leaves you in a free state, with no server selected. The status flag on your desktop, if active, displays Free. See "Controlling the Status Flag" on page 250. Soft Switching Soft switching is switching between servers using a hotkey sequence.
Video Connections The iKVM has video connections on the front and rear panels of the chassis. The front panel connection signals take precedence over that of the rear panel. When a monitor is connected to the front panel, the video connection does not pass through to the rear panel, and an OSCAR message displays stating that the rear panel KVM and ACI connections are disabled.
Use the Security dialog box to lock your console with password protection, set or change your password, or enable the screen saver. NOTE: If the iKVM password is lost or forgotten, you can reset it to the iKVM factory default using the CMC Web interface or RACADM. See "Clearing a Lost or Forgotten Password" on page 258. Accessing the Security Dialog Box 1 Press . The Main dialog box appears. 2 Click Setup and the Security. The Security dialog box appears.
CAUTION: Monitor damage may result from the use of Energy mode with monitors not compliant with Energy Star. 5 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. 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.
Enabling Screen Saver Mode With No Password Protection NOTE: If your console is password protected, you must first remove password protection. Follow the steps in the previous procedure before following the steps below. 1 Select Enable Screen Saver. 2 Type the number of minutes (1 through 99) that you want to delay activation of the screen saver. 3 Select Energy if your monitor is ENERGY STAR compliant; otherwise select Screen.
To reset a lost or forgotten iKVM password using the CMC Web interface: 1 Log in to the CMC Web interface. 2 Select iKVM from the Chassis submenu. 3 Click the Setup tab. The iKVM Configuration page displays. 4 Click Restore Default Values. You can then change the password from the default using OSCAR. See "Setting or Changing the Password" on page 256.
To display version information: 1 Press . The Main dialog box appears. 2 Click Commands and then Display Versions. The Version dialog box appears. The top half of the Version dialog box lists the subsystem versions in the appliance. 3 Click or press to close the Version dialog box. Scanning Your System In scan mode, the iKVM automatically scans from slot to slot (server to server).
or Click the Clear button to remove all servers from the Scan list. 2 Click the Add/Remove button, and then click OK. To start Scan mode: 1 Press . The Main dialog box appears. 2 Click Commands. The Command dialog box appears. 3 Select the Scan Enable box. 4 Click OK. A message appears indicating that the mouse and keyboard have been reset. 5 Click to close the message box. To cancel scan mode: 1 If OSCAR is open and the Main dialog box is displayed, select a server in the list.
To broadcast to servers: 1 Press . The Main dialog box appears. 2 Click Setup and then Broadcast. The Broadcast dialog box appears. NOTE: Broadcasting keystrokes: When using keystrokes, the keyboard state must be identical for all servers receiving a broadcast for the keystrokes to be interpreted identically. Specifically, the and modes must be the same on all keyboards.
Managing iKVM From the CMC Enabling or Disabling the Front Panel To enable or disable access to the iKVM from the front panel using RACADM, open a Telnet/SSH text console to the CMC, log in, and type: racadm config -g cfgKVMInfo -o cfgKVMFrontPanelEnable where is 1 (enable) or 0 (disable). For more information about the config subcommand, see "config" on page 322. To enable or disable access to the iKVM from the front panel using the Web interface: 1 Log in to the CMC Web interface.
Viewing the iKVM Status and Properties The local access KVM module for your Dell M1000e server chassis is called the Avocent® Integrated KVM Switch Module, or iKVM. The health status of the iKVM associated with the chassis can be viewed on the Chassis Properties Health page under the Chassis Graphics section. To view health status for the iKVM using Chassis Graphics: 1 Log in to the CMC Web interface. 2 The Chassis Status page is displayed.
Table 9-5. iKVM Status Information Item Description Presence Indicates whether the iKVM module is Present or Absent. Power State Indicates the power status of the iKVM: On, Off, or N/A (Absent). Name Displays the product name of the iKVM. Manufacturer Displays in the manufacturer of the iKVM. Part Number Displays the part number for the iKVM. The part number is a unique identifier provided by the vendor. Firmware Version Indicates the firmware version of the iKVM.
To update the iKVM firmware using the CMC Web interface: 1 Log in to the CMC Web interface. 2 Click Chassis in the system tree. 3 Click the Update tab. The Updatable Components page displays. 4 Click the iKVM name. The Firmware Update page appears. 5 In the Firmware Image field, enter the path to the firmware image file on your management station or shared network, or click Browse to navigate to the file location. NOTE: The default iKVM firmware image name is ikvm.
For example: racadm fwupdate -gua 192.168.0.10 -d ikvm.bin -m kvm For more information about the fwupdate subcommand, see "fwupdate" on page 329. Troubleshooting NOTE: If you have an active console redirection session and a lower resolution monitor is connected to the iKVM, the server console resolution may reset if the server is selected on the local console. If the server is running a Linux operating system, an X11 console may not be viewable on the local monitor.
Table 9-6. Troubleshooting iKVM (continued) Problem Likely Cause and Solution The rear panel access does not work. The front panel setting is enabled by the CMC, and a monitor is currently connected to the front panel. Only one connection is allowed at a time. The front panel connection has precedence over ACI and the rear panel. For more information about connection precedence, see "iKVM Connection Precedences" on page 246.
Table 9-6. Troubleshooting iKVM (continued) Problem Likely Cause and Solution The iKVM’s amber LED is blinking. There are three possible causes: There is problem with the iKVM, for which the iKVM requires reprogramming. To fix the problem, follow the instructions for updating iKVM firmware (see "Updating the iKVM Firmware" on page 265). The iKVM is reprogramming the CMC Console Interface. In this case, the CMC Console is temporarily unavailable and represented by a yellow dot in the OSCAR interface.
Table 9-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 9-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 the 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 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.
Figure 10-1 shows the location of IOMs in the chassis. The location of each IOM in the chassis is indicated by its group number (A, B, or C) and slot number (1 or 2). On the chassis, the IOM slot names are marked A1, A2, B1, B2, C1, or C2. Figure 10-1. Rear View of a Chassis, Showing the Location of the IOMs Slots A1, B1, C1 Slots C2, B2, A2 The CMC creates entries in both the hardware log and CMC logs for invalid hardware configurations.
NOTE: Fabric verification for server MCs (mezzanine cards) is performed only when the chassis is powered on. When the chassis is on standby power, the iDRACs on the server modules remain powered off and thus are unable to report the server's MC fabric type. The MC fabric type may not be reported in the CMC user interface until the iDRAC on the server is powered on.
For information about the CMC and hardware logs, see "Viewing the Event Logs" on page 300. Fresh Power-up Scenario When the chassis is plugged in and powered up, the I/O modules have priority over the servers. The first IOM in each group is allowed to power up before the others. At this time, no verification of their fabric types is performed. If there is no IOM on the first slot of a group, the module on the second slot of that group powers up.
3 Use the cursor to hover over an individual IOM subgraphic and a corresponding text hint or screen tip is displayed. The text hint provides additional information on that IOM. 4 The IOM subgraphic is hyperlinked to the corresponding CMC GUI page to provide immediate navigation to the I/O Module Status page associated with that IOM. To view the health status of all IOMs using the I/O Modules Status page: 1 Log in to the CMC Web interface. 2 Select I/O Modules in the Chassis menu in the system tree.
Table 10-1 provides descriptions of the information provided on the I/O Modules Status page. Table 10-1. I/O Modules Health Status Information Item Description Present Indicates whether the IOM is Present or Absent. Health OK Indicates that the IOM is present and communicating with the CMC. In the event of a communication failure between the CMC and the server, the CMC cannot obtain or display health status for the IOM.
Table 10-1. I/O Modules Health Status Information (continued) Item Description Fabric Indicates 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.
Table 10-2 provides descriptions of the information provided on the I/O Module Status page. Table 10-2. I/O Module Health Status Information Item Description Name Displays name of the IOM. Present Indicates whether the IOM is Present or Absent. Health OK Indicates that the IOM is present and communicating with the CMC. In the event of a communication failure between the CMC and the server, the CMC cannot obtain or display health status for the IOM.
Table 10-2. I/O Module Health Status Information (continued) Item Description Warning Indicates that only warning alerts have been issued, and corrective action must be taken within the time frame set by the administrator. If corrective actions are not taken within the administrator-specified time, it could lead to critical or severe failures that can affect the integrity of the IOM.
Table 10-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: Passthroughs 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.
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 the CMC is not saved to the switch's permanent startup configuration. To save the IP address configuration permanently, you must enter the connect switch-n RACADM command or use a direct interface to the IOM GUI to save this address to the startup configuration file. Table 10-3.
Troubleshooting IOM Network Settings The following list contains troubleshooting items for IOM network settings: • The CMC can read the IP address setting too quickly after a configuration change; it will display 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 will not set the IP address and will return a 0.0.0.0 in all fields.
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.
4 Click the Identify sub-tab. 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. Using RACADM Open a Telnet/SSH text console to the CMC, log in, and type: racadm setled -m [-l ] where specifies the module whose LED you want to configure.
Table 11-1. Chassis Events That Can Generate SNMP and Email Alerts (continued) Event Description Temperature Probe Warning The temperature is approaching excessively high or low limits. Temperature Probe Failure The temperature is either too high or too low for proper operation. Redundancy Degraded Redundancy for the fans and/or power supplies has been reduced. Redundancy Lost No redundancy remains for the fans and/or power supplies.
NOTE: For added security, Dell strongly recommends that you change the default password of the root (User 1) account. The root account is the default administrative account that ships with the CMC. To change the default password for the root account, click User ID 1 to open the User Configuration page. Help for that page is available through the Help link at the top right corner of the page. 1 Log in to the CMC Web interface. 2 Select Chassis in the system tree. 3 Click the Alert Management tab.
Using RACADM 1 Open a Telnet/SSH text console to the CMC and log in. NOTE: Only one filter mask may be set both SNMP and email alerting. You may skip step 2 if you have already selected filter mask. 2 Enable alerting by typing: racadm config -g cfgAlerting -o cfgAlertingEnable 1 3 Specify the events for which you want the CMC to generate by typing: racadm config -g cfgAlerting -o cfgAlertingFilterMask where is a hex value between 0x0 and 0x003fffdf.
Table 11-2. Event Traps Filter Masks (continued) Event Filter Mask Value Hardware Log Failure 0x4000 Hardware Log Warning 0x8000 Server Absent 0x10000 Server Failure 0x20000 KVM Absent 0x40000 KVM Failure 0x80000 IOM Absent 0x100000 IOM Failure 0x200000 Firmware mismatch 0x400000 4 Enable traps alerting by typing: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value 1–4.
NOTE: The commands in steps 2–6 will overwrite 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 will appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName objects. To test an event trap for an alert destination: racadm testtrap -i where is a value 1–4 representing the alert destination you want to test.
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 email 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. For instructions as to how to accomplish this in a secure manner, refer to the documentation that came with your SMTP server.
Using RACADM 1 Open a Telnet/SSH text console to the CMC and log in. 2 Enable alerting by typing: racadm config -g cfgAlerting -o cfgAlertingEnable 1 NOTE: Only one filter mask may be set by both SNMP and email alerting. You may skip step 3 if you have already set a filter mask.
You can configure up to four destination email addresses to receive email alerts. To add more email addresses, repeat steps 2–6. NOTE: The commands in steps 2–6 will overwrite any existing settings configured for the index you specify (1–4). To determine whether an index has previously configured values, type: racadm getconfig -g cfgEmailAlert -i . If the index is configured, values will appear for the cfgEmailAlertAddress and cfgEmailAlertEmailName objects.
Executing a Power Control Operation For instructions on powering on, powering off, resetting, or power-cycling the system using the CMC Web interface or RACADM, see "Executing Power Control Operations on the Chassis" on page 241, "Executing Power Control Operations on an IOM" on page 242, and "Executing Power Control Operations on a Server" on page 243.
Table 11-3. Chassis Summary (continued) Item Description System Power Status Displays the system power status. Table 11-4. CMC Summary Item Description Primary CMC Information Name Displays the name of the CMC. For example, Primary CMC or Standby CMC. Description Provides a brief description of the purpose of the CMC. Date/Time Indicates the date and time set on the active or primary CMC. Location Indicates the slot location of the active or primary CMC.
Table 11-4. CMC Summary (continued) Item Description DNS Domain Name Indicates the DNS Domain name. 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 11-5. iKVM Summary Item Description Present Indicates whether the iKVM module is present (Yes or No). Name Displays the name of the iKVM. The name identifies the iKVM on the network.
Table 11-6. IOM Summary Item Description Location Indicates 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 Indicates whether the IOM is present (Yes or No). Name Displays the name of the IOM. Fabric Displays the type of fabric. Power Status Indicates the power status of the IOM: On, Off, or N/A (Absent). Service Tag Displays the service tag of the IOM.
overview of the components installed within the chassis and its corresponding status. Each graphic displays a real-time representation of the installed components. The component state is indicated by the color of the component subgraphic. • Green - the component is present, powered on and communicating with the CMC; there is no indication of an adverse condition.
Table 11-7. Health Status Indicators (continued) Item Description Warning Indicates that only Warning alerts have been issued, and corrective action must be taken within the time frame set by the administrator. If corrective actions are not taken within administrator-specified time, it could lead to a component failure, communication failure between the component and the CMC, and a critical or severe failure that could affect the integrity of the chassis.
NOTE: You can configure the CMC to send email or SNMP traps when specific events occur. For information on configuring CMC to send alerts, see "Configuring SNMP Alerts" on page 286 and "Configuring Email Alerts" on page 291.
To clear the hardware log: Click Clear Log. NOTE: The CMC creates a new log entry indicating that the log was cleared. Table 11-8. Hardware Log Information 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 a noncritical event for which corrective actions should be taken soon to avoid system failures.
Viewing the CMC Log The CMC generates a log of chassis-related events. NOTE: To clear the hardware log, you must have Clear Logs Administrator privilege. Using the Web Interface You can view, save a text file version of, and clear the CMC log in the CMC Web interface. You can re-sort the log entries by Source, Date/Time, or Description by clicking the column heading. Subsequent clicks on the column headings reverse the sort.
Using RACADM 1 Open a Telnet/SSH text console to the CMC and log in. 2 To view the hardware log, type: racadm getraclog To clear the hardware log, type: racadm clrraclog Firmware Update Error Codes The CMC log can also display error codes as part of the log information. The table below contains the firmware update CMC log error codes. Table 11-10.
Table 11-10.
Using the Diagnostic Console The Diagnostic Console page enables an advanced user, or a user under the direction of technical support, to diagnose issues related to the chassis hardware using CLI commands. NOTE: To modify these settings, you must have Debug Command Administrator privilege. 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 Diagnostics sub-tab. The Diagnostic Console page displays.
Table 11-11. Supported Diagnostic Commands (continued) Command Result gettracelog Displays the trace log (may take a few seconds to display the log). The gettracelog -i command returns the number of records in the trace log. The gettracelog -A command returns the trace log without the record numbers. NOTE: This command is for Dell internal use only. NOTE: For more information about the gettracelog command, see "gettracelog" on page 359.
Table 11-12.
Table 11-12.
Troubleshooting a Non-responsive CMC NOTE: It is not possible to log in to the standby CMC using a serial console. If you cannot log in to the CMC using any of the interfaces (the Web interface, Telnet, remote RACADM, or serial), you can verify CMC functionality by observing the LEDs on the CMC, obtaining recovery information using the DB-9 serial port, or recovering the CMC firmware image.
To obtain recovery information: 1 Install a NULL modem cable between the CMC and a client machine. 2 Open a terminal emulator of your choice (such as HyperTerminal or Minicom). Set up: 8 bits, no parity, no flow control, baud rate 115200. A core memory failure will display an error message every 5 seconds. 3 Press . If a recovery prompt appears, additional information is available. The prompt will indicate the CMC slot number and failure type.
recover ping 192.168.0.100 recover fwupdate -g -a 192.168.0.100 NOTE: Connect the network cable to the left most RJ45 NOTE: In recover mode, you cannot ping the CMC normally because there is no active network stack. The recover ping command allows you to ping to the TFTP server to verify the LAN connection. You may need to use the recover reset command after setniccfg on some systems.
To perform management actions, a user with Administrator privileges is required. The CMC software has a user account password protection security feature that may be disabled if the administrator account password is forgotten. If the administrator account password is forgotten, it can be recovered using the PASSWORD_RSET jumper on the CMC board. The CMC board has a two-pin password reset connector as shown in Figure 11-1.
Figure 11-1. Password Reset Jumper Location PASSWORD_RSET Table 11-13. 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. 4 Initiate a changeover to make the module active using the GUI interface to perform the following steps: 314 a Navigate to the Chassis page, click the Power Management tab Control sub tab.
5 The CMC automatically fails over to the redundant module, and that module now becomes active. Log into the active CMC using the default administrator username of root and password of calvin, and restore any necessary user account settings. The existing accounts and passwords are not disabled and are still active. After you have completed any account updates, remove the 2-pin jumper and replace the jumper plug. NOTE: Make sure the CMC module is in a passive state before you begin.
Troubleshooting and Recovery
RACADM Subcommands "?" and "? " NOTE: To use this subcommand, you must have CMC Login User privilege. Description ? lists all of the subcommands you can use with the racadm command and a one-line description of each subcommand. ? displays the syntax for the specified command. NOTE: You can also use the help and help commands to obtain the same information.
clrraclog -- clear the CMC log clrsel -- clear the System Event Log (SEL) cmcchangeover -- Changes the redundant state of the CMC from active to standby and vice versa config -- modify CMC configuration properties LEDs on a module ...
Example • racadm arp Address HWtype HWaddress Flags Mask Iface 143.166.152.3 ether 00:07:84:A7:CE:BC C eth0 143.166.152.2 ether 00:07:84:7B:9F:FC C eth0 143.166.152.1 ether 00:00:0C:07:AC:0A C eth0 143.166.152.113 ether 00:15:C5:48:9C:1D C eth0 chassisaction NOTE: To use this subcommand, you must have Chassis Control Administrator privilege. Description Executes a power action on the chassis, iKVM, or a server.
Table A-1. chassisaction Subcommand Options (continued) Option Description Specifies the action you want to execute on the specified module. may be one of the following: • powerdown — (Chassis only) Powers down the chassis. • powerup — (Chassis only) Powers up the chassis. • powercycle — Power cycles the module. • nongraceshutdown — (Chassis only) Shutdown the chassis non-gracefully. • reset — Performs a hard reset of the module.
clrsel NOTE: To use this subcommand, you must have Clear Logs Administrator privilege. Description Removes all existing records from the system events log (SEL, or hardware log). A new log entry is added to record the date and time when the log was cleared, and the user who cleared the log. NOTE: To view the hardware log, use getsel. For information about the hardware log, see "Viewing the Hardware Log" on page 300.
config NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege. Description Sets the CMC configuration parameters individually or in a batch as part of a configuration file. If the data is different, that CMC object is written with the new value. Usage racadm config -g -o
Property Groups NOTE: Appendix B, "CMC Property Database Group and Object Definitions" on page 385, provides details about the property groups. See also "getconfig" on page 332. Table A-3 lists the property groups that can be specified with the -g option. . Table A-3.
Output The config subcommand generates error output when it encounters any of the following: • Invalid syntax, group name, object name, index, or other invalid database members • Insufficient user privileges • RACADM CLI failures • The config subcommand returns an indication of how many configuration objects were written out of how many total objects were in the .cfg file. Examples • racadm config -g cfgLanNetworking -o cfgNicIpAddress 10.35.10.
NOTE: This subcommand is valid only if the DHCP option is disabled for the specified server. When DHCP is enabled, the server automatically obtains an IP address, subnet mask, and gateway from the DHCP server. To determine whether DHCP is enabled for the server, use getniccfg (see "getniccfg" on page 345). To enable or disable DCHP, use setniccfg (see "setniccfg" on page 373).
Example • racadm deploy server-8 -s 192.168.0.20 255.255.255.0 192.168.0.1 The server was deployed successfully. NOTE: The deploy command generates an error when used on the extension slot of a multi-slot server. • racadm deploy -m server-9 192.168.0.11 255.255.255.0 192.168.0.1 ERROR: Server in slot 9 is an extension of the server in slot 1. feature NOTE: To use this subcommand to deactivate FlexAddress, you must have Chassis Configuration Administrator privilege.
Table A-5. feature Subcommand Options Option Description -d -c Deactivates feature. -s Lists active features. Example • racadm feature -d -c flexaddress feature FlexAddress is deactivated on the chassis successfully • racadm feature -s Feature = FlexAddress Date Activated = 8 April 2008 - 10:39:40 Feature installed from SD card SN = 01122334455 featurecard NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege.
Table A-6. Status Messages Returned by featurecard -s Command Status Message Actions No feature card inserted. Check the CMC to verify that the SD card was properly inserted. In a redundant CMC configuration, make sure the CMC with the SD feature card installed is the active CMC and not the standby CMC. The feature card inserted is valid and No action required.
Example racadm featurecard -s • racadm featurecard -s The feature card inserted is valid and contains the following feature(s) FlexAddress: The feature card is bound to this chassis fwupdate NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege. Description Updates the firmware on the iKVM, primary CMC, (if applicable) the standby CMC, the server iDRAC, and the IOM infrastructure device. Also performs updates to iDRAC firmware when the existing firmware is corrupted.
Table A-8. fwupdate Subcommand Options Option Description -d Specifies the source path where the firmware image resides. Default: local directory on CMC if -g option is absent. If -g is used, defaults to directory configured on the TFTP server -g Downloads the firmware update using the TFTP server. -u Performs firmware update operation (used with -g). -a (used with -g).
Example • racadm fwupdate -g -u -a 192.168.0.120 -d firmimg.cmc -m cmc-active TFTP firmware update has been initiated. This update process may take several minutes to complete. Firmware update complete. • racadm fwupdate -s -m cmc-active Firmware update in progress. NOTE: The fwupdate command generates an error when used on the extension slot of a multi-slot server. • racadm fwupdate -g -u -a 192.168.0.120 -d update m server-9 ERROR: Server in slot 9 is an extension of the server in slot 1.
Table A-9. getassettag Subcommand Options Option Description -m Specifies the module whose asset tag you want to view. Legal value: chassis Because there is only one legal value, you can obtain the same output if you do not include this option. Example • racadm getassettag -m chassis or racadm getassettag chassis 78373839–33 getchassisname NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the name of the chassis.
Description Displays CMC configuration parameters and allows you to save CMC configuration groups to a .cfg file. Usage racadm getconfig -g racadm getconfig -g -o
Table A-11 lists the property groups that can be specified with the getconfig subcommand -g option. Table A-11. Property Groups for the getconfig Subcommand Property Group Description idRacInfo (read only) Displays version, build number, and product information for the CMC. cfgLanNetworking Configures network related properties. cfgCurrentLanNetworking (read only) Displays the current CMC NIC properties. cfgRemoteHosts Enables/disables and configures firmware updates and SMTP email alerting.
Output This subcommand generates error output upon encountering either of the following: • Invalid syntax, group name, object name, index, or other invalid database members • RACADM CLI transport failures If errors are not encountered, this subcommand displays the contents of the specified configuration. Examples: • racadm getconfig -g cfgLanNetworking Displays all of the configuration properties (objects) that are contained in the group cfgLanNetworking (see "cfgLanNetworking" on page 387).
NOTE: Fabric verification for server DCs is performed only when the chassis is powered on. When the chassis is on standby power, the iDRACs on the server modules remain powered off and thus are unable to report the server's DC fabric type. The DC fabric type may not be reported in the CMC user interface until the iDRAC on the server is powered on. Usage racadm getdcinfo NOTE: The example output below is for a system with multi-slot servers.
server-8 Not Present None N/A server-9 Extension(1) Infiniband DDR OK server-10 Not Present None N/A server-11 Not Present None N/A server-12 Not Present None N/A server-13 Not Present None N/A server-14 Not Present None N/A server-15 Not Present None N/A server-16 Not Present None N/A None N/A FibreChannel 8 OK None N/A None N/A None N/A None N/A None N/A None N/A None N/A getflexaddr NOTE: To use this subcommand, you must have CMC Login User privilege.
Table A-12. getflexaddr Subcommand Options Option Description -i Specifies the slot information to be displayed.
• Fabric-B iSCSI enabled Fabric-C fiber channel enabled racadm getflexaddr -i 1 Slot-1 flexaddress enabled = 1 slot1-A1 Gigabit Ethernet 00:1E:C9:FF:E3:21 iSCSI 00:1E:C9:FF:E3:22 slot1-A2 Gigabit Ethernet 00:1E:C9:FF:E3:23 iSCSI 00:1E:C9:FF:E3:24 slot1-B1 Gigabit Ethernet 00:1E:C9:FF:E3:25(active) iSCSI 00:1E:C9:FF:E3:26(active) slot1-B2 Gigabit Ethernet 00:1E:C9:FF:E3:27(active) iSCSI 00:1E:C9:FF:E3:28(active) slot1-C1 Fiber Channel 4 20:01:00:1
Example racadm getioinfo switch-1 Ethernet Passthrough OK switch-2 Gigabit Ethernet Present None Not Present None Not Present None Not Present None Not Present None Not Present ON N/A N/A switch-3 N/A N/A N/A switch-4 N/A N/A N/A switch-5 N/A N/A N/A switch-6 N/A N/A N/A N/A getkvminfo NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays iKVM module information.
Description Displays the LED settings on a module: blinking, not blinking, or unknown (for empty slots). Usage racadm getled -m Table A-13 describes the getled subcommand options. Table A-13. getled Subcommand Options Option Description -m Specifies the module whose LED settings you want to view.
getmacaddress NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the MAC/WWN addresses for all modules or for a specified module. Usage racadm getmacaddress [-m ] [<-t iscsi] racadm getmacaddress [-a] Options Table A-14 describes the getmacaddress subcommand options. Table A-14. getmacaddress Subcommand Options Option Description -m Specifies the module whose MAC address you want to view.
00:11:43:FD:B7:2B server-9 Extension(1) 00:11:43:FD:B7:2D N/A 00:11:43:FD:B7:2C getmodinfo NOTE: To use this subcommand, you must have CMC Login User privilege. The service tag field is blank for modules that do not have service tags. Description Displays configuration and status information for all modules or a specified module (server, switch, CMC, fan unit, or power supply unit) in the chassis.
Example • racadm getmodinfo -m switch-1 Switch-1 • Present OK ABC1234 Present ON Present ON Present ON Present ON Present ON Present ON Present ON Present ON Present ON Present ON Present Online Not Present N/A Present Online Not Present N/A Not Present N/A Not Present N/A Present Primary Not Present N/A Not Present N/A Not Present N/A Not Present N/A Not Present N/A Not Present N/A Not Present N/A Not Present N/A Present OFF Present ON Pre
Server-15 Server-16 KVM Present Present Present ON ON ON OK OK OK getniccfg NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays network settings for a server, switch, or the chassis. NOTE: The getniccfg subcommand will display an error message if the operation is not successful. Usage racadm getniccfg [-m ] Options Table A-16 describes the getniccfg subcommand options. Table A-16.
Static Gateway Current IP Address Current Subnet Mask Current Gateway Speed Duplex • 192.168.0.1 10.35.155.160 255.255.255.0 10.35.155.1 Autonegotiate Autonegotiate racadm getniccfg -m server-1 DHCP Enabled IP Address Subnet Mask Gateway • = = = = = = = = = = 0 192.168.0.135 255.255.255.0 192.168.0.1 racadm getniccfg -m server-9 ERROR: Server in slot 9 is an extension of the server in slot 1. getpbinfo NOTE: To use this subcommand, you must have CMC Login User privilege.
Redundancy Policy = None Dynamic PSU Engagement Enabled = No System Input Max Power Capacity = 0 W Input Redundancy Reserve = 0 W Input Power Allocated to Servers = 0 W Input Power Allocated to Chassis Infrastructure = 51 watts Total Input Power Available for Allocation = 0 W Standby Input Power Capacity = 0 W [Chassis Power Supply Status Table]
13 14 15 16 SLOT-13 SLOT-14 SLOT-15 SLOT-16 N/A ON ON ON N/A 342 W 140 W 125 W 5 5 5 5 N/A N/A N/A getpminfo NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays power management status information.
Overall Power Health Redundancy = OK = No [System Power Policy Configuration] System Input Power Cap BTU/hr | 10%) Surplus for Peak Performance BTU/hr) Redundancy Policy Dynamic PSU Engagement Enabled = 7928 W (7928 = 7000 W (6130 = None = No [Power Budgeting] System Input Max Power Capacity Input Redundancy Reserve Input Power Allocated to Servers Input Power Allocated to Chassis Infrastructure Total Input Power Available for Allocation Standby Input Power Capacity = = = = = = 0 W 0 W 0 W 51W 0 W 0 W
Table A-17. getraclog Subcommand Options Open Description (none) Displays the entire CMC log, including the record number, time stamp, source, and description of each event. -s Specifies the starting record used for the display -c Specifies the maximum number of entries to be returned. -i Displays the number of entries in the CMC log. -m Displays one screen of information at a time and prompts the user to continue to next screen (similar to the UNIX more command).
Usage racadm getractime [-d] [-z] Options Table A-18 describes the getractime subcommand options. Table A-18. getractime Subcommand Options Option Description (None) Displays the date and time using the same format as the UNIX® date command. -d Displays the date and time as a sequence of numeric digits, in the following format: YYYYMMDDhhmmss. -z Appends the current active time zone name to the display. For example, PST8PDT (Western United States), 279 (Seoul), 329 (Sydney).
Usage racadm getredundancymode Example racadm getredundancymode Redundant getsel NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the system event log (SEL, also called the hardware log) entries. The default output display shows the record number, timestamp, severity, and description of each event.
Example • racadm getsel -i Total Records: 28 • racadm getsel -s 1 -c 1 Sun Sep 16 02:51:11 2007 normal Server Blade 12 Presence module sensor for Server Blade, device inserted was asserted getsensorinfo NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays status for the specified sensors.
PWR 2 PS-2 Online OK PWR PWR 3 4 PS-3 PS-4 Online Slot Empty OK N/A PWR PWR 5 6 PS-5 PS-6 Failed OK Slot Empty getslotname NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the name of a specified slot (indicated by slot number) in the chassis. Usage racadm getslotname -i Options Table A-20 describes the getslotname subcommand options. Table A-20.
Description Displays information about an active user session, including user name, IP address (if applicable), and session type (for example, serial, SSH, or Telnet), and login date and time. Options allow you to view a list of currently active or pending users and summary session table information.
KVM root 11/28/2007 18:44:51 SSH root 11/28/2007 23:22:37 • 169.254.31.30 10.9.72.252 racadm getssninfo -A \Telnet\root\143.166.174.19\05/01/2007 02:13:59 • racadm getssninfo -A -u * \KVM\root\169.254.31.30\11/28/2007 18:44:51 \SSH\root\10.9.72.252\11/28/2007 23:22:37 getsvctag NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the service tag information, if present, for one or all modules on the chassis.
Examples • racadm getsvctag Chassis switch-1 switch-2 switch-3 switch-4 switch-5 switch-6 server-1 server-2 server-3 server-4 server-5 server-6 server-7 server-8 server-9 server-10 server-11 server-12 server-13 server-14 server-15 server-16 • ABC1234 abc123 N/A N/A 0000014 Extension(1) N/A N/A N/A 1234567 N/A racadm getsvctag -m switch-1 switch-1 ABC1234 getsysinfo NOTE: To use this subcommand, you must have CMC Login User privilege.
Usage racadm getsysinfo [-d] [-c] [-A] Options Table A-23. getsysinfo Subcommand Options Option Description -d Displays CMC information. -c Displays chassis information. -A Suppresses headers and labels in the output.
"15" "143.166.152.39" "143.166.152.1" "255.255.255.0" "1" "00:11:43:FD:B4:39" "0.0.0.0" "0.0.0.0" "0" "1" "cmc-51186" "" gettracelog NOTE: This command is for Dell internal use only. NOTE: To use this subcommand, you must have CMC Login User privilege. Description Displays the diagnostic trace log for the CMC. The default output display shows the record number, timestamp, source, and description. The timestamp begins at midnight, January 1 and increases until the system boots.
Example • racadm gettracelog -c 5 Nov 28 04:40:41 cmc syslogd 1.4.1: restart.
racadm getsysinfo [-d] [-c] [-A] -d : show CMC information -c : show chassis information -A : do not show headers or labels ifconfig NOTE: To use this subcommand, you must have Administrator privilege. Description Display network interface information. Usage racadm ifconfig Examples racadm ifconfig eth0 0F Link encap:Ethernet HWaddr 00:55:AB:39:10: inet addr:10.35.155.160 Bcast:10.35.155.25 Mask:255.255.255.
Description Display routing table and network statistics. Usage racadm netstat Examples racadm netstat Kernel IP routing table Destination Gateway MSS Window irtt Iface 10.35.155.0 * 0 0 0 eth0 default 10.35.155.1 0 0 0 eth0 Genmask Flags 255.255.255.0 U 0.0.0.0 UG ping NOTE: To use this subcommand, you must have Administrator privilege. Description Send ICMP echo packets to a destination on the network. Usage racadm ping Examples racadm ping 10.9.72.252 PING 10.9.72.252 (10.9.72.
racdump NOTE: To use this subcommand, you must have Administrator privilege. Description Displays the comprehensive chassis status and configuration state information, as well as historic event logs. Used for post deployment configuration verification and during debugging sessions.
===================================================== ========================== General System/RAC Information ===================================================== ========================== CMC Information: CMC Date/Time = Wed, 28 Nov 2007 11:55:49 PM Primary CMC Version = X08 Standby CMC Version = N/A Last Firmware Update = Wed Nov 21 21:37:56 2007 Hardware Version = 2 Current IP Address = 10.35.155.160 Current IP Gateway = 10.35.155.1 Current IP Netmask = 255.255.255.
Type SSH User root IP Address 10.9.72.252 Login Date/Time 11/28/2007 23:40:53 KVM root 169.254.31.
racreset NOTE: To use this subcommand, you must have Administrator privilege. Description Issues a soft or hard reset to the CMC. The reset event is written into the CMC log. When this command is executed without the hard option, racreset executes a soft reset. A hard reset performs a deep reset operation on the CMC. A hard reset should only be performed as a last-case resort to recover the CMC. NOTICE: You must reboot your system after performing a hard reset of the CMC. See "racreset" on page 366.
• racadm racreset hard Executes a hard reset sequence on the CMC. racresetcfg NOTE: To use this subcommand, you must have Administrator privilege. NOTE: Power off the chassis before running this command. Description Removes all database property entries on the CMC or iKVM and restores the default factory configuration. After restoring the database properties, the CMC resets automatically. The iKVM also resets automatically when racresetcfg is used to restore its default properties.
Example racadm racresetcfg -m kvm The configuration has initiated restoration to factory defaults. serveraction NOTE: To use this subcommand, you must have Administrator privilege. Description Executes a server reset, power-up, power-down, or powercycle on the specified server. Usage racadm serveraction [-m ] racadm serveraction [-a] Options Table A-27 describes the serveraction subcommand options. Table A-27.
Table A-27. serveraction Subcommand Options (continued) Option Description Specifies the action. may be one of the following: • powerdown — Powers down the server. • powerup — Powers up the server. • powercycle — Issues a power-cycle operation on the server. • hardreset — Performs a reset (reboot) operation on the server. • graceshutdown — Shuts down the server gracefully. • powerstatus — Displays current power status (Online, Off) of the server.
setassettag NOTE: To use this subcommand, you must have Administrator privilege. Description Sets the N-byte ASCII asset tag for the chassis. Usage racadm setassettag -m chassis Options Table A-28 describes the setassettag subcommand options. Table A-28. setassettag Subcommand Options Option Command -m Specifies the module whose asset tag you want to set.
Description Enables/disables FlexAddress on a particular slot/fabric. NOTE: If the fabric type is determined to be Infiniband, the operation is canceled and the command returns an error. If the FlexAddress feature is not activated, the command will return an error. NOTE: The server must be powered off to change the slot state. All servers must be powered off to change the fabric state.
setled NOTE: To use this subcommand, you must have Administrator privilege. Description Sets the state (blinking or not blinking) of the LED on the specified module. Usage racadm setled -m -l Options Table A-30 describes the setled subcommand options. Table A-30. setled Subcommand Options Option Description -m Specifies the module whose LED you want to configure.
setniccfg NOTE: To use this subcommand, you must have Administrator privilege. Description Sets the IP configuration for the specified module. Usage racadm setniccfg [-m ] [-d] [-o] [-s ] [-k ] racadm setniccfg [-m ] -d racadm setniccfg [-m ] -s racadm setniccfg [-m ] -o racadm setniccfg [-m ] -k [ ] Options Table A-31 describes the setniccfg subcommand options.
Table A-31. setniccfg Subcommand Options (continued) Option Description -s Enables static IP settings by specifying the IP address, subnet mask, and gateway. , , and must be typed as dot-separated strings. If this option is not supplied, the existing static settings are used. -o Disables the Ethernet management port completely. -k Specifies the speed and duplex for the NIC.
Usage racadm setractime -d racadm setractime -l [-z ] Options Table A-32 describes the setractime subcommand options. Table A-32. setractime Subcommand Options Option Description -d Sets the time in the string yyyymmddhhmmss.
Table A-32. setractime Subcommand Options (continued) Option Description -l Sets the local date and time in the string yyyymmddhhmmss where: • yyyy is a the year • mm is the month • dd is the day • hh is the hour • mm is the minute • ss is the second NOTE: Setting the time using the -l and -z options is recommended. This command format allows the CMC to fully support local time zones, including the ability to automatically adjust the CMC time to the local Daylight Savings Time.
Table A-33. setslotname Subcommand Options Option Description Indicates the location of the slot in the chassis. Legal values: 1–16 The new name to assign to the slot. Example racadm setslotname -i 3 mserver3 The slot name was set successfully. setsysinfo NOTE: To use this subcommand, you must have Administrator privilege. Description Sets the name or location of the chassis.
sslcertdownload NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege. Description Downloads an SSL certificate from the RAC to the client’s file system. Usage racadm sslcertdownload -t -f Options Table A-35 describes the sslcertdownload subcommand options. Table A-35.
Description Uploads a custom SSL server or certificate authority-signed certificate from the client to the CMC. Usage racadm sslcertupload -t -f Options Table A-36 describes the sslcertupload subcommand options. Table A-36. sslcertupload Subcommand Options Option Description -t Specifies the type of certificate to upload: 1 — Server certificate 2 — Certificate authority-signed certificate -f Specifies the file name of the certificate to be uploaded.
Options Table A-37 describes the sslcertview subcommand options. Table A-37. sslcertview Subcommand Options Option Description -t Specifies the type of certificate to view, either the Microsoft Active Directory certificate or server certificate. 1 — server certificate 2 — Microsoft Active Directory certificate -A Suppresses headers and labels in the output. Restrictions The sslcertupload subcommand can only be executed from a local client.
sslcsrgen NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege. Description Generates and downloads an SSL certificate signing request (CSR) from the CMC to your management station or shared network. You can use the CSR to create a custom SSL certificate for transactions on the CMC. Usage racadm sslcsrgen [-g] racadm sslcsrgen [-g] [-f ] racadm sslcsrgen [-s] Options Table A-38 describes the sslcsrgen subcommand options. Table A-38.
Restrictions The sslcsrgen subcommand can only be executed from a local client and cannot be used in the serial, Telnet, or SSH interface. Example • racadm sslcsrgen -s CSR generation in progress. • racadm sslcsrgen -g -f c:\csr\csrtest.txt The csr was generated successfully. sslresetcfg NOTE: To use this subcommand, you must have Chassis Configuration Administrator privilege. Description Regenerates the self-signed certificate used by the CMC Web GUI.
testemail Table A-39. sslcsrgen Subcommand Options Option Description -g Generates a new CSR. The -g option cannot be used with the -s option. -s Returns the status of a CSR generation process: • CSR was generated successfully. • CSR does not exist. • CSR generation in progress. The -s option cannot be used with the -g option. -f Specifies the filename where the CSR will be downloaded. Can only be used with the -g option.
Example racadm testemail -i 1 Test email sent successfully. testtrap NOTE: To use this subcommand, you must have Test Alert User privilege. Description Tests the CMC SNMP trap alerting feature by sending a test trap from the CMC to a specified destination trap listener on the network. NOTE: This command is valid only if SNMP alerts are enabled on the CMC. For more information about SNMP alerts, see "Configuring SNMP Alerts" on page 286.
CMC Property Database Group and Object Definitions The CMC property database contains the configuration information for the CMC. Data is organized by associated object, and objects are organized by object group. The IDs for the groups and objects that the property database supports are listed in this section. Use the group and object IDs with the RACADM subcommands config (see "config" on page 322) and getconfig (see "getconfig" on page 332) to configure the CMC.
Synopsis racadm getconfig -g idRacInfo #idRacType Identifies the remote access controller type as the CMC. #idRacProductInfo Uses a text string to identify the product, for example, Chassis Management Controller. #idRacDescriptionInfo A text description of the RAC type. #idRacVersionInfo A string containing the current product firmware version. #idRacBuildInfo The current RAC firmware build version. #idRacName A user-assigned name that identifies the CMC.
cfgLanNetworking NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. NOTE: You can configure any setting that is not preceded by the hash sign (#) in the output. To modify a configurable object, use the -o option. Description Displays information for and configures network related properties. Synopsis racadm getconfig -g cfgLanNetworking cfgNicEnable Enables or disables the CMC NIC.
cfgNicGateway Assigns a static gateway for the CMC IP address. This property is used only if cfgNicUseDhcp is set to 0 (false). • Legal value: A string representing a valid gateway. For example, 192.168.0.1. cfgNicUseDhcp Enables or disables the use of DHCP (Dynamic Host Configuration Protocol) by the CMC for the NIC. If set to 0, then DHCP is disabled and IP addresses are statically assigned. If set to 1, then DHCP is enabled and IP address are automatically assigned.
cfgDNSServer2 (Read/Write) NOTE: To modify this property, you must have Configure CMC permission. Retrieves DNS server 2 IP address. This parameter is only valid if cfgDNSServersFromDHCP is set to 0 (false). • Configuration options: A string representing a valid IP address, for example: 192.168.0.20. • Default: 0.0.0.0 NOTE: cfgDNSServer1 and cfgDNSServer2 may be set to identical values while swapping addresses. cfgDNSRacName Displays the CMC name.
cfgDNSRegisterRac Registers the CMC name on the DNS server. • Configuration options: 1 (true), 0 (false) • Default: 0 Example racadm getconfig -g cfgLanNetworking cfgNicEnable=1 cfgNicIpAddress=192.168.22.101 cfgNicNetmask=255.255.255.0 cfgNicGateway=192.168.22.101 cfgNicUseDhcp=1 #cfgNicMacAddress=00:00:00:00:00:01 cfgDNSServersFromDHCP=0 cfgDNSServer1=192.168.0.5 cfgDNSServer2=192.168.0.
# cfgNicCurrentNetmask Displays the static subnet mask for the CMC IP address. # cfgNicCurrentGateway Displays the static gateway for the CMC IP address. # cfgNicCurrentDhcpWasUsed Indicates whether DHCP is used to configure the NIC: 1 — address is static. 0 — address was obtained from the DHCP server. # cfgDNSCurrentServer1 Displays the IP address for DNS server 1. # cfgDNSCurrentServer1 Displays the IP address for DNS server 2. # cfgDNSCurrentDomainName Displays the DNS domain name.
NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. Description Enables/disables and configures firmware updates and SMTP email alerting. cfgRhostsFwUpdateTftpEnable Enables or disables CMC firmware updates from a network TFTP server. • Configuration options: 1 (true), 0 (false) • Default: 1 cfgRhostsFwUpdateIpAddr The IP address of the network SMTP server. The SMTP server transmits e-mail alerts from the CMC (if the alerts are configured and enabled).
Example racadm getconfig -g cfgRemoteHosts cfgRhostsFwUpdateTftpEnable=1 cfgRhostsFwUpdateIpAddr=127.0.0.1 cfgRhostsFwUpdatePath=m13_0417.bin cfgRhostsSmtpServerIpAddr=localhost.localdomain cfgUserAdmin NOTE: In the current CMC firmware version, the objects cfgUserAdminEnable and cfgUserAdminPrivilege are interrelated; changing the value of one property causes the value of the other property to change. For example, if a user does not have login privilege, the user is disabled by default.
cfgUserAdminUserName Displays/sets the name of the user for the specified index name. The user index is created by writing a string into this name field if the index is empty. Writing a string of double quotation marks ("") deletes the user at that index. To change the name, you must delete and then re-create the name. The string cannot contain "/" (forward slash), "\" (backslash), "." (period), "@" ("at") or quotations marks. Legal value: String of up to 16 characters # cfgUserAdminPassword Write only.
Table B-1. Bit Masks for User Privileges (continued) User Privilege Privilege Bit Mask User Configuration Administrator 0x0000004 Clear Logs Administrator 0x0000008 Chassis Control Administrator 0x0000010 Super User 0x0000020 Server Administrator 0x0000040 Test Alert User 0x0000080 Debug Command Administrator 0x0000100 Fabric A Administrator 0x0000200 Fabric B Administrator 0x0000400 Fabric C Administrator 0x0000800 Table B-2.
Description Configures CMC email alerting. # cfgEmailAlertIndex Read only. Displays the unique index of an alert instance. Configuration range: 1–4 Default: This parameter is populated based on the existing instances. cfgEmailAlertEnable Enables or disables CMC email alerting. Configuration options: 1 (enable), 0 (disable) Default: 0 (disabled) # cfgEmailAlertAddress Read only. Indicates the destination email address for the email alerts.
cfgSessionManagement NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. Description Displays current settings for and configures idle timeout properties for Web server, Telnet, SSH, and RACADM sessions. Changes to idle timeout settings take effect at the next login. To disable idle timeout for a connection, set this property to 0.
Default: 30 seconds Example racadm getconfig -g cfgSessionManagement cfgSsnMgtWebserverTimeout=0 cfgSsnMgtTelnetIdleTimeout=0 cfgSsnMgtSshIdleTimeout=300 cfgSsnMgtRacadmTimeout=0 cfgSerial NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. Description Displays information for and configures serial parameters. Objects cfgSerialBaudRate Sets the baud rate on the CMC serial port.
cfgSerialConsoleQuitKey Specifies the key or key combination that terminates the serial text console.
Configuration range: 0–8192 Default: 8192 cfgSerialTelnetEnable Enables or disables the Telnet console interface on the CMC. Configuration options: 1 (true), 0 (false) Default: 0 cfgSerialSshEnable Enables or disables the secure shell (SSH) interface on the CMC.
cfgNetTuningNicSpeed Specifies the speed for the CMC NIC. This property is used only if cfgNetTuningNicAutoNeg is set to 0 (disabled). Configuration options: 10 or 100 Default: 100 cfgNetTuningNicFullDuplex Specifies the duplex setting for the CMC NIC. This property is used only if cfgNetTuningNicAutoNeg is set to 0 (disabled). Configuration options: 0 (half duplex), 1 (full duplex) Default: 1 cfgNetTuningNicMtu Specifies the size in bytes of the maximum transmission unit used by the CMC NIC.
cfgOobSnmp NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. NOTE: You can configure any setting that is not preceded by the hash sign (#) in the output. To modify a configurable object, use the -o option. Description Enables or disables SNMP traps for the CMC. cfgOobSnmpAgentEnable Enables or disables the SNMP agent in the CMC.
Description Displays information for and configures delivery of SNMP traps for a specific user. # cfgTrapsIndex Read only. Indicates the unique index of an alert instance. cfgTrapsEnable Enables or disables event traps on the CMC. Configuration options: 1 (true), 0 (false) cfgTrapsAlertDestIpAddr Sets the IP address that will receive the alert. Configuration options: A string representing a valid IP address. For example, 192.168.0.20.
Description Enables or disables SNMP event trap alerting and sets the event filter. cfgAlertingEnable Enables or disables event traps on the CMC. Configuration options: 1 (true), 0 (false) cfgAlertingFilterMask Configuration options: Hex values 0x0–0x007fffff. For information on hex values for events, see Table 11-2. Default: 0x3ff8db cfgAlertingSourceEmailName Email address used to send email notifications when an event occurs.
cfgRacTuneRemoteRacadmEnable Enables or disables the Remote RACADM interface in the CMC. Configuration options: 1 (true), 0 (false) Default: 1 cfgRacTuneWebserverEnable Enables and disables the CMC Web server. If this property is set to 0 (FALSE, or disabled), you cannot access the CMC through client Web browsers or remote RACADM. This property has no effect on the Telnet/SSH/serial or local RACADM interfaces.
Configuration range: 10–65535 Default: 22 cfgRacTuneIpRangeEnable Enables or disables the IP address Range validation feature of the CMC. Configuration options: 1 (true), 0 (false) Default: 0 cfgRacTuneIpRangeAddr Specifies the acceptable IP address bit pattern in positions determined by the 1's in the range mask property (cfgRacTuneIpRangeMask). Configuration options: IP address-formatted string. For example, 192.168.0.44. Default: 192.168.1.1 cfgRacTuneIpRangeMask Specifies the IP range mask property.
cfgRacTuneIpBlkFailWindow Defines the time span in seconds within which the failed attempts are counted. When the failure attempts age to this limit, the failures are dropped from the count. Configuration range: 2–65535 Default: 60 cfgRacTuneIpBlkPenaltyTime Defines the time span in seconds during which session requests from an IP address with excessive failures are rejected.
cfgRacTuneIpBlkFailWindow=60 cfgRacTuneIpBlkPenaltyTime=300 cfgRacTuneTimezoneOffset=0 cfgRacTuneDaylightOffset=0 cfgRacSecurity NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. Description Configures settings related to the CMC SSL certificate signing request (CSR) feature. NOTE: You must configure the properties in this group before you can generate a CSR from the CMC.
cfgRacSecCsrOrganizationUnit Specifies the CSR Organization Unit (OU). Legal value: String of up to 254 characters. Default: [null] cfgRacSecCsrLocalityName Specifies the CSR Locality (L). Legal value: String of up to 254 characters. Default: [null] cfgRacSecCsrStateName Specifies the CSR State Name (S). Legal value: String of up to 254 characters. Default: [null] cfgRacSecCsrCountryCode Specifies the CSR Country Code (CC). Legal value: String of up to 254 characters.
cfgRacSecStateName= cfgRacSecCountryCode= cfgRacSecEmailAddr= cfgActiveDirectory NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. NOTE: You can configure any setting that is not preceded by the hash sign (#) in the output. To modify a configurable object, use the -o option. Description Configures Microsoft® Active Directory® properties.
cfgADAuthTimeout Specifies the number of seconds to wait for Active Directory authentication requests to complete before timing out. Configuration range: 15–300 Default: 120 cfgADType Indicates the schema type (extended or standard) to use with Active Directory. Configuration options: 1 (extended), 2 (standard) Default: 1 (extended) cfgADSpecifyServerEnable Allows you to enable/disable and specify an LDAP server or a global catalog server.
cfgADRacName= cfgADRacAuthTimeout=300 cfgADRacType=0x4 cfgADRacSpecifyServerEnable=1 cfgRacADDomainController=192.168.1.1 cfgRacADGlobalCatalog=127.0.0.1 cfgStandardSchema NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. NOTE: You can configure any setting that is not preceded by the hash sign (#) in the output. To modify a configurable object, use the -o option.
cfgSSADRoleGroupPrivilege Specifies the bit mask numbers (see Table B-1) to set role-based authority privilege for a Role Group. Configuration range: 0x00000000–0x000001ff Default: [null] Example racadm getconfig -g cfgStandardSchema # cfgSSADRoleGroupIndex=1 cfgSSADRoleGroupName=blsys-1 cfgSSADRoleGroupDomain= cfgSSADRolGroupPrivilege=3081 cfgChassisPower NOTE: Use this object with the config or getconfig subcommands.
# cfgChassisPeakPowerTimestamp Read only. The timestamp recorded when the peak system power value occurred. # cfgChassisMinPower Read only. The minimum system level power consumption value (in watts) over the time since the value was last cleared. # cfgChassisMinPowerTimestamp Read only. The timestamp recorded when the minimum system power occurred. # cfgChassisPowerStatus Read only. Indicates the power status of the chassis.
cfgChassisPowerCapBTU Indicates the maximum power consumption limit (in BTU/hr) for the entire chassis. The command will generate an error if blade throttling is necessary to achieve the power goal based on the value for this setting. Configuration range: 9445-27051 BTU/hr Default: 27051 BTU/hr cfgChassisPowerCapFBTU Indicates the maximum power consumption limit (in BTU/hr) for the entire chassis.
cfgChassisRedundancyPolicy Sets the redundancy policy of the chassis. Configuration options: 0 (no redundancy), 1 (AC redundancy), 2 (power supply redundancy). Default: 0 (no redundancy) cfgChassisDynamicPSUEngagementEnable Enables or disables dynamic engagement. Configuration options: 0 (disabled), 1 (enabled) Default: 0 (disabled) # cfgChassisInMaxPowerCapacity Read only. Indicates the total chassis power budget (in watts) available for chassis operation. # cfgChassisInRedundancyReserve Read only.
# cfgChassisStandbyInPowerCapacity Read only. Indicates the amount of power (in watts) available for powering up any hardware modules that are either added to the chassis or powered up (if they are already present in the chassis). # cfgChassisPowerClear Write only. To reset cfgChassisMinPower and cfgChassisMaxPowerCapacity, set this object to 1. # cfgChassisPowerClearTimestamp Read only. Time stamp when cfgChassisMinPower and cfgChassisMaxPowerCapacity were reset.
cfgChassisDynamicPSUEngagementEnable=0 # cfgChassisInMaxPowerCapacity=0 W # cfgChassisInRedundancyReserve=0 W # cfgChassisInPowerServerAllocation=0 W # cfgChassisInfrastructureInPowerAllocation=51 W # cfgChassisTotalInPowerAvailable=0 W # cfgChassisStandbyInPowerCapacity=0 W # cfgChassisPowerClear=******** (Write-Only) # cfgChassisPowerClearTimestamp=18:00:00 12/31/1969 cfgChassisPowerButtonEnable=1 cfgSystemEnergyConsumptionClear = ****(Write-Only) • racadm config -g cfgChassisPower -o cfgChassisPowerClea
cfgServerName Specifies the name of the specified server. Configuration options: String of alphanumeric characters, periods, and dashes; maximum of 15 characters. Default: SLOT- # cfgServerBmcMacAddress Read only. Displays the BMC MAC address of the specified server. # cfgServerNic1MacAddress Read only. Displays the MAC address of the server NIC. # cfgServerNic2MacAddress Read only. Displays the MAC address of the server NIC.
cfgServerDNSRegisterIMC Enables or disables DNS name registration for the integrated management controller, iDRAC. Configuration options: 0 (disable), 1 (enable) cfgServerDNSIMCName Displays the DNS domain name for the integrated Remote Access Controller, iDRAC. #cfgServerRootPassword Write only. Displays the password for iDRAC as a series of asterisks (*). It cannot be seen or displayed after this property is written.
# cfgServerNic2MacAddress=00:11:43:FD:B7:2A cfgServerPriority=1 cfgServerNicEnable=N/A cfgServerIPMIOverLanEnable=N/A # cfgServerPowerBudgetAllocation=N/A cfgKVMInfo NOTE: Use this object with the config or getconfig subcommands. NOTE: To use this object property, you must have Chassis Configuration Administrator privilege. NOTE: You can configure any setting that is not preceded by the hash sign (#) in the output. To modify a configurable object, use the -o option.
CMC Property Database Group and Object Definitions
Using the LCD Panel Interface You can use the LCD panel to perform configuration and diagnostics, and to obtain status information about the chassis and its contents. LCD Navigation Use the buttons to the right of the LCD screen to operate the LCD panel. The up, down, left, and right arrow buttons change the selected menu items or icons on the screen. The selected item is shown with a light blue background or border. The center button activates the selected item.
Table C-1. LCD Panel Navigational Icons (continued) Icon Normal Icon Icon Name and Description Highlighted Component Identify. Blinks the blue LED on a component. NOTE: There will be a blinking blue rectangle around this icon when Component Identify is enabled. Main Menu From the Main menu you can navigate to one of the following screens: • LCD Setup Menu — select the language to use and the LCD screen that displays when no one is using the LCD. • Server — displays status information for servers.
3 Press the center button to confirm the change. The LCD Setup menu is displayed. Default Screen The Default Screen allows you to change the screen that the LCD panel displays when there is no activity at the panel. The factory default screen is the Main Menu.
To view the status screen for a server: 1 Use the arrow buttons to highlight the desired server. 2 Press the center button. The Server Status screen displays. To return to the Main Menu: 1 Use the arrow buttons to highlight the Back icon. 2 Press the center button. 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.
Enclosure Menu Screen From this screen you can navigate to the following screens: • Module Status screen • Enclosure Status screen • IP Summary screen • Main Menu 1 Use the navigation buttons to highlight the desired item. (Highlight the Back icon to return to the Main Menu.) 2 Press the center button. The selected screen displays. Module Status Screen The Module Status screen displays information and error messages about a module.
Use the up and down arrow buttons to scroll through the list. Use the left and right arrow buttons to scroll selected messages that are longer than the screen. Use the up and down arrow buttons to select the Back icon and press the center button to return to the Enclosure menu. Diagnostics The LCD panel helps you to diagnose problems with any server or module in the chassis.
Figure C-1.
Symptom Issue Recovery Action Alert screen message CMC Not Responding and LED is blinking amber Loss of communication from CMC to the LCD front panel Check that the CMC is booting; then, reset the CMC using GUI or RACADM commands. Alert screen message CMC Not Responding and LED is solid amber or is off LCD front panel stuck in Disconnect and reconnect boot block during a CMC the front panel circuit board failover to the I/O panel cable from front panel. Reset the CMC using GUI or RACADM commands.
Symptom Issue Recovery Action Blank LCD and LED off The front panel circuit board cable or the I/O panel cable are not connected properly; or one or both are faulty. Review the hardware log using the GUI or RACADM commands. Look for messages that state: Control Panel FPC Cable: Cable sensor for Control Panel, configuration error was asserted Control Panel I/O Cable: Cable sensor for Control Panel, configuration error was asserted Check that the cables are connected properly.
LCD Error Messages Table C-2. CMC Status Screens Severity Message Cause Critical CMC Battery: Battery CMC CMOS battery is missing or sensor for CMC, failed was no voltage. asserted Critical CMC CPU Temp: Temperature sensor for CMC, failure event Critical CMC Ambient Temp: CMC Ambient temperature Temperature sensor for CMC, exceeded the critical threshold.
Table C-3. Enclosure/Chassis Status Screen (continued) Severity Message Cause Critical Power Supply Redundancy: PS Redundancy sensor for Power Supply, redundancy lost was asserted One or more PSU have failed or removed and the system is no longer redundant. Critical Power Supply Redundancy: PS Redundancy sensor for Power Supply, non-redundant: insufficient resources One or more PSU have failed or removed and the system lacks sufficient power to maintain normal operations.
Table C-5. IOM Status Screens Severity Message Cause Warning I/O Module Status: The IO module was good, but now Module sensor for I/O Module, having fabric mismatch or link transition to non-critical from OK tuning mismatch. was asserted Critical I/O Module Status: Module sensor for I/O Module, transition to critical from less severe was asserted The I/O module has a fault. The same error can also happen if the I/O module is thermal-tripped. Table C-6.
Table C-8. Server Status Screen Severity Message Cause Warning System Board Ambient Temp: Temperature sensor for System Board, warning event Server Ambient temperature crossed a warning threshold. Critical System Board Ambient Temp: Temperature sensor for System Board, failure event Server Ambient temperature crossed a failing threshold. Critical System Board CMOS Battery: Battery sensor for System Board, failed was asserted CMOS battery is not present or has no voltage.
Table C-8. Server Status Screen (continued) Severity Message Critical CPU Status: Processor Incorrect processor type or in sensor for CPU, wrong location. configuration error was asserted Critical CPU Status: Processor Required CPU is missing or not sensor for CPU, present. presence was de-asserted Critical System Board Video Riser: Module Required module was removed.
Table C-8. Server Status Screen (continued) Severity Message Cause Critical System Board OS Watchdog: Watchdog sensor for System Board, power off was asserted The iDRAC watchdog detected that the system has crashed (timer expired because no response was received from Host) and the action is set to power off.
Table C-8. Server Status Screen (continued) Severity Message Cause NonCPU Protocol Err: Processor Recoverable sensor, transition to nonrecoverable was asserted The processor protocol entered a non-recoverable state. NonCPU Bus PERR: Processor sensor, Recoverable transition to non-recoverable was asserted The processor bus PERR entered a non-recoverable state.
Table C-8. Server Status Screen (continued) Severity Message Cause Critical PCIE Fatal Err: Critical Event Fatal error is detected on the PCIE sensor, bus fatal error was asserted bus. Critical Chipset Err: Critical Event sensor, Chip error is detected. PCI PERR was asserted Warning Mem ECC Warning: Memory sensor, transition to non-critical from OK () was asserted Correctable ECC errors have increased from a normal rate.
Table C-8.
Table C-8.
Table C-8. Server Status Screen (continued) Severity Message Cause Critical LinkT/ FlexAddr: Link Tuning sensor, failed to get link tuning or flex address data from BMC/iDRAC was asserted Failed to obtain linking tuning or FlexAddress information from BMC/iDRAC Critical LinkT/ FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or flex address (Mezz XX) was asserted PCI device Option ROM for a NIC does not support link tuning or the FlexAddress feature.
Table C-10. Chassis/Enclosure Status Item Description User Define Name Example: “Dell Rack System”. This is settable via CMC CLI or Web GUI Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings.
Table C-12. 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 Maximum Wattage Maximum Wattage that PSU can supply to the system Table C-13. IOM Status Item Description Name/Location Example: IOM A1, IOM B1.
Table C-14. iKVM Status (continued) Item Description Part Number The manufacturer part number. Firmware Version The iKVM firmware version. Table C-15. Server Status Item Description Name/Location Example: Server 1, Server 2. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. Slot Name CMC slot name. Example SLOT-01. Note: this is settable via CMC CLI or Web GUI. Name User settable name of the server.
Using the LCD Panel Interface
Glossary Active Directory Active Directory is a centralized and standardized system that automates network management of user data, security, and distributed resources, and enables interoperation with other directories. Active Directory is designed especially for distributed networking environments. ARP Address resolution protocol, a method for finding a host’s Ethernet address from its Internet address.
certificate to the applicant that uniquely identifies that applicant for transactions over networks and on the Internet. CD Compact disc Certificate Signing Request (CSR) A digital request to a certificate authority for a secure server certificate. CLI Command Line interface DHCP Dynamic host configuration protocol, a means of dynamically allocating IP addresses to computers on a network.
FQDN Fully qualified domain name, a domain name that specifies a module’s absolute position in the DNS tree hierarchy. Microsoft® Active Directory® only supports an FQDN of 64 bytes or fewer. FSMO Flexible single master operation, a Microsoft Active Directory domain controller task that guarantees atomicity of an extension operation. GB1 The uplink port on the chassis. GMT Greenwich Mean Time. GMT is the standard time common to every place in the world.
IOMINF I/O module infrastructure device. IP Internet Protocol. IP is the network layer for TCP/IP. IP provides packet routing, fragmentation, and reassembly. IPMB Intelligent platform management bus, which is used in systems management technology. Kbps Kilobits per second, a data transfer rate.
MC Mezzanine card Microsoft Active Directory A centralized, standardized system that automates network management of user data, security, and distributed resources, and enables interoperation with other directories. Active Directory is designed especially for distributed networking environments. NIC Network interface card, an adapter circuit board installed in a computer to provide a physical connection to a network.
RPM Red Hat Package Manager, a package-management system for the Red Hat Enterprise Linux operating system. RPM manages the installation of software packages. It is similar to an installation program. SEL System event log or hardware log SMTP Simple mail transfer protocol, used to transfer electronic mail between systems— usually over an Ethernet. SNMP Simple network management protocol, designed to manage nodes on an IP network. iDRACs are SNMP-managed devices (nodes).
TFTP Trivial file transfer protocol, a simple file transfer protocol used for downloading boot code to diskless devices or systems. UPS Uninterruptible power supply USB Universal serial bus, a serial bus standard to interface devices. UTC Universal Coordinated Time. See GMT. vKVM Virtual keyboard-video-mouse console VLAN Virtual local area network VNC Virtual network computing VT-100 Video Terminal 100, which is used by the most common terminal emulation programs.
Glossary
Index A cfgAlerting, 403 ACI, 247 CMC configuring, 201, 208 creating a configuration file, 86 downloading firmware, 52 feature sets, 25 installing, 35 log, 303 redundant environment, 55 setting up, 35 Active Directory, 185-212 adding CMC users, 198 configuring access to the CMC, 191 configuring and managing certificates, 130 extending schemas, 191 objects, 187 schema extensions, 186 using with standard schema, 205 command line console features, 57 adding SNMP alerts, 286 configuration file creating,
firmware downloading, 52 managing, 151 updating, CMC, 152 updating, iKVM, 154 updating, IOM infrastructure device, 155 updating, Server iDRAC, 156 FlexAddress, 169 activating, 170 activation verification, 171 configuring using CLI, 174 deactivating, 173 license agreement, 180 Linux configuration, 175 troubleshooting, 176 viewing status using CLI, 174 Wake-On-LAN, 175 frequently asked questions managing and recovering a remote system, 165 using the CMC with Active Directory, 212 iKVM, 245 installing CMC, 35
O R OSCAR, 245 RAC see Remote Access Connection, 29 P RACADM uninstalling from Linux management station, 37 parsing rules, 87 password disabling, 312 reset jumper location, 314 power budgeting configuring, 52 power conservation, 218 property database groups cfgActiveDirectory, 410 cfgChassisPower, 413 cfgCurrentLanNetworking, 390 cfgEmailAlert, 395 cfgKVMInfo, 421 cfgLanNetworking, 387 cfgNetTuning, 400 cfgOobSnmp, 402 cfgRacSecurity, 408 cfgRacTuning, 404 cfgRemoteHosts, 391 cfgSerial, 398 cfgServerI
RACADM subcommands (continued) getsel, 352 getsensorinfo, 353 getslotname, 354 getssninfo, 354 getsvctag, 356 getsysinfo, 357 gettracelog, 359 help, 360 ifconfig, 361 racdump, 363 racreset, 366 racresetcfg, 367 serveraction, 368 setchassisname, 369 setflexaddr, 370 setled, 372 setniccfg, 373 setractime, 374 setslotname, 376 setsysinfo, 377 sslcertdownload, 378 sslcertupload, 378 sslcertview, 379 sslcsrgen, 381 sslresetcfg, 382 testemail, 383 testtrap, 384 racadm utility configuring network properties, 77 pa
specifications hardware, 28 sslcertdownload, 378 standard schema using with Active Directory, 205 T telnet console using, 58 W web browser configuring, 38 supported browsers, 29 web interface accessing, 93 configuring email alerts, 291 WS-Management, 30 Index 459
Index
