Dell PowerEdge M1000e Chassis Management Controller Firmware Version 4.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2013 Dell Inc. All Rights Reserved.
Contents 1 Overview.....................................................................................................................................15 What Is New In This Release................................................................................................................................. 16 Key Features........................................................................................................................................................... 16 Management Features.......
Setting Chassis Physical Location and Chassis Name...........................................................................................36 Setting Chassis Physical Location and Chassis Name Using Web Interface..................................................36 Setting Chassis Physical Location and Chassis Name Using RACADM..........................................................37 Setting Date and Time on CMC.............................................................................................
Updating CMC Firmware Using Web Interface................................................................................................51 Updating CMC Firmware Using RACADM........................................................................................................51 Updating iKVM Firmware........................................................................................................................................52 Updating iKVM Firmware Using CMC Web Interface........................
Configuring CMC....................................................................................................................... 75 Viewing and Modifying CMC Network LAN Settings............................................................................................. 76 Viewing and Modifying CMC Network LAN Settings Using CMC Web Interface............................................76 Viewing and Modifying CMC Network LAN Settings Using RACADM.....................................................
Creating a CMC Configuration File................................................................................................................... 93 Parsing Rules................................................................................................................................................... 94 Modifying the CMC IP Address........................................................................................................................ 95 Viewing and Terminating CMC Sessions........
Configuring CMC To Send Alerts..........................................................................................115 Enabling Or Disabling Alerts................................................................................................................................. 115 Enabling Or Disabling Alerts Using CMC Web Interface............................................................................... 115 Enabling Or Disabling Alerts Using RACADM...............................................
Using Telnet Console With CMC...........................................................................................................................153 Using SSH With CMC............................................................................................................................................154 Supported SSH Cryptography Schemes........................................................................................................ 154 Configure Public Key Authentication over SSH.......
Viewing I/O Module FCoE Session Information Using Web Interface................................................................. 178 Viewing Stacking Information for Dell PowerEdge M I/O Aggregator................................................................. 178 Configuring Network Settings for IOM(s)............................................................................................................. 178 Configuring Network Settings for IOMs Using CMC Web Interface...............................
15 Managing and Monitoring Power...................................................................................... 199 Redundancy Policies............................................................................................................................................ 200 Grid Redundancy Policy................................................................................................................................. 200 Power Supply Redundancy Policy.......................................
16 Troubleshooting and Recovery...........................................................................................219 Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP............................................. 219 Supported Interfaces..................................................................................................................................... 219 Downloading SNMP Management Information Base (MIB) File................................................
RACADM...............................................................................................................................................................249 Managing and Recovering a Remote System...................................................................................................... 249 Active Directory....................................................................................................................................................
Overview 1 The Dell Chassis Management Controller (CMC) for Dell PowerEdge M1000e chassis is a systems management hardware and software solution for managing multiple Dell server chassis. It is a hot-pluggable card that is installed at the back of Dell PowerEdge M1000e chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.
What Is New In This Release This release of CMC supports: • Single Click all blade update using Network Share mode • 3000 W AC PSUs • Extended Power Performance for 3000 W AC PSUs • Configuration of the number of reserved IP addresses used by quick deploy for the servers in the chassis • Enhanced Cooling Mode for next generation fans • Pre-enabling power-on of 13th generation servers (link tuning update) for evaluation without upgrading CMC firmware to later versions Key Features The CMC feature
• • • • • • Enhanced server summary, power reporting, and power control pages. Forced CMC failover and virtual reseat of servers. iDRAC reset without rebooting the operating system. Support for storage array configuration using RACADM — Allows you to configure IP, join or create group, and select fabric for storage arrays using RACADM. Multi-chassis management: – capability to view up to eight other chassis from the lead chassis.
1 GB Port 2 STK Port CMC Port Information The following TCP/IP ports are required to remotely access CMC through firewalls. These are the ports CMC listens to for connections. Table 1. CMC Server Listening Ports Port Number Function 22* SSH 23* Telnet 80* HTTP 161 SNMP Agent 443* HTTPS * Configurable port The following table lists the ports that CMC uses as a client. Table 2.
Servers Minimum version of CMC PowerEdge M905 CMC 1.2 PowerEdge M610 CMC 2.0 PowerEdge M610x CMC 3.0 PowerEdge M710 CMC 2.0 PowerEdge M710HD CMC 3.0 PowerEdge M910 CMC 2.3 Power Edge M915 CMC 3.2 PowerEdge M420 CMC 4.1 PowerEdge M520 CMC 4.0 PowerEdge M620 CMC 4.0 PowerEdge M820 CMC 4.11 PowerEdge PSM4110 CMC 4.11 The following table lists the minimum CMC version required to enable the listed IOMs. Table 4.
IOM Switches Minimum version of CMC Dell PowerEdge M I/O Aggregator CMC 4.2 Mellanox M2401G DDR Infiniband Switch CMC 1.0 Mellanox M3601Q QDR Infiniband Switch CMC 2.0 Mellanox M4001F/M4001Q FDR/QDR Infiniband Switch CMC 4.0 Mellanox M4001T FDR10 Infiniband Switch CMC 4.1 Brocade M6505 CMC 4.3 Cisco Nexus B22DELL CMC 4.
Table 6. Supported Remote Access Connections Connection Features CMC Network Interface ports • • • • • • • Serial port • • • Other connections • GB port: Dedicated network interface for the CMC Web interface. Two 10/100/1000 Mbps ports; one for management and the other for chassis to chassis cable consolidation. STK: Uplink port for chassis to chassis management network cable consolidation. 10 Mbps/100 Mbps/1 Gbps Ethernet through CMC GbE port. DHCP support. SNMP traps and email event notification.
Supported Management Console Applications The CMC supports integration with Dell OpenManage IT Assistant. For more information, see the IT Assistant documentation set available on the Dell Support Web site at dell.com/support/manuals. Other Documents You May Need In addition to this guide, you can access the following guides available at dell.com/support/manuals. Select Choose from a list of all Dell products and click Continue.
Updates are sometimes included with the system to describe changes to the system, software, and/or documentation. Always read the updates first because they often supersede information in other documents. Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options.
Installing and Setting Up CMC 2 This section provides information about how to install the PowerEdge M1000e Chassis Management Controller (CMC) hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the next steps for configuring the CMC: • Set up initial access to CMC. • Access CMC through a network. • Add and configure CMC users. • Update CMC firmware.
7. Connect to the CMC IP address and provide default username (root) and password (calvin). 8. Provide each iDRAC with an IP address in the CMC Web interface and enable the LAN and IPMI interface. NOTE: iDRAC LAN interface on some servers are disabled by default. 9. Provide each I/O module with an IP address in the CMC Web interface. 10. Connect to each iDRACand provide final configuration of iDRAC. Default user name is root and password is calvin. 11.
1 Management Network 2 Standby CMC 3 Active CMC The following figures provide examples of incorrect cabling of CMC.
To daisy-chain up to four chassis: 1. Connect the GB port of the active CMC in the first chassis to the management network. 2. Connect the GB port of the active CMC in the second chassis to the STK port of the active CMC in the first chassis. 3. If you have a third chassis, connect the GB port of its active CMC to the STK port of the active CMC in the second chassis. 4. If you have a fourth chassis, connect the GB port of its active CMC to the STK port of the third chassis. 5.
Installing RACADM on a Linux Management Station 1. Log in as root to the system running a supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components. 2. Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive. 3. To mount the DVD to a required location, use the mount command or a similar command.
Proxy Server To browse through a proxy server that does not have access to the management network, you can add the management network addresses to the exception list of the browser. This instructs the browser to bypass the proxy server while accessing the management network. Internet Explorer To edit the exception list in Internet Explorer: 1. Start Internet Explorer. 2. Click Tools → Internet Options → Connections . 3. In the Local Area Network (LAN) settings section, click LAN Settings.
To disable CRL fetching: 1. Start Internet Explorer. 2. Click Tools → Internet Options and then click Advanced. 3. Scroll to the Security section, clear the Check for publisher’s certificate revocation check box, and click OK. Downloading Files From CMC With Internet Explorer When you use Internet Explorer to download files from CMC you may experience problems when the Do not save encrypted pages to disk option is not enabled. To enable the Do not save encrypted pages to disk option: 1.
If you have more than one chassis you can choose between the basic connection, where each CMC is connected to the management network, or a daisy-chained chassis connection, where the chassis are connected in series and only one CMC is connected to the management network. The basic connection type uses more ports on the management network and provides greater redundancy.
network communication. Determine whether your network supports the above network speeds and set it accordingly. If the network configuration does not match any of these values, it is recommended to use Auto Negotiation (the Auto option) or refer to your network equipment manufacturer. Press the center button to continue to the next CMC Network Settings screen. 5. Select the duplex mode (half or full) that matches the network environment.
You can also configure iDRAC from the CMC GUI. 10. Select the Internet Protocol (IPv4, IPv6, or both) that you want to use for the servers. Dynamic Host Configuration Protocol (DHCP) iDRAC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. The iDRAC is assigned a unique IP address allotted over your network.Press the center button. Static You must manually enter the IP address, gateway, and subnet mask in the screens following immediately.
NOTE: Using more than one interface at the same time may generate unexpected results. Table 7. CMC Interfaces Interface Description Web interface Provides remote access to 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 the Supported Browsers section in the Readme at dell.com/support/manuals.
Interface Description defines the semantics and information types that can be modified in a managed system. The CMC WS-MAN implementation uses SSL on port 443 for transport security, and supports basic authentication. The data available through WS-Management is provided by CMC instrumentation interface mapped to the DMTF profiles and extension profiles. For more information, see the following: • • • • • MOFs and Profiles — delltechcenter.com/page/DCIM.Library DTMF Web site — dmtf.
3. Click Apply. The settings are saved. Setting Chassis Physical Location and Chassis Name Using RACADM To set the chassis name or location, date and time using the command line interface, see the setsysinfo and setchassisname commands. For more information, see RACADM Command Line Reference Guide for iDRAC7 and CMC. Setting Date and Time on CMC You can set the date and time manually, or you can synchronize the date and time with a Network Time Protocol (NTP) server.
Configuring LED Blinking Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm setled -m [-l ] where specifies the module whose LED you want to configure. Configuration options: • server-nx where n = 1-8 and x = a, b, c, or d • switch-n where n=1–6 • cmc-active and specifies whether the LED should blink.
3. To enable the user blocking or IP blocking feature, in the Login Lockout Policy section, select Lockout by User Name or Lockout by IP Address (IPV4) . The options to set the other login lockout policy attributes are activated. 4. Enter the required values for login lockout policy attributes in the activated fields — Lockout Fail Count, Lockout Fail Window , and Lockout Penalty Time. For more information, see the CMC Online Help. 5. To save these settings, click Apply.
Related Links About Standby CMC CMC Failsafe Mode Active CMC Election Process Obtaining Health Status of Redundant CMC About Standby CMC The standby CMC is identical to and is maintained as a mirror of the active CMC. The active and standby CMCs must both be installed with the same firmware revision. If the firmware revisions differ, the system reports as redundancy degraded. The standby CMC assumes the same settings and properties of the active CMC.
Obtaining Health Status of Redundant CMC You can view the health status of the standby CMC in the Web interface. For more information about accessing CMC health status in the Web interface, see Viewing Chassis Information and Monitoring Chassis and Component Health.
Logging In to CMC 3 You can log in to CMC as a CMC local user, as a Microsoft Active Directory user, or as an LDAP user. The default user name and password is root and calvin, respectively. You can also log in using Single Sign-On or Smart Card.
Logging Into CMC as Local User, Active Directory User, or LDAP User To log in to CMC, you must have a CMC account with Log In to CMC privilege. The default CMC user name is root, and the password is calvin. The root account is the default administrative account that ships with CMC. NOTE: For added security, it is strongly recommended that you change the default password of the root account during initial setup.
• Enable Smart Card login. To log in to CMC as an Active Directory user using smart card: 1. Log in to CMC using the link https://. The CMC Login page is displayed prompting you to insert the smart card. NOTE: If you changed the default HTTPS port number (port 80), access the CMC Web page using :, where cmcname is the CMC host name for CMC, domainname is the domain name, and port number is the HTTPS port number. 2.
After you have configured your management station terminal emulator software and managed node BIOS, perform the following steps to log in to CMC: 1. Connect to the CMC using your management station terminal emulation software. 2. Type your CMC user name and password, and press . You are logged in to the CMC.
Configure Public Key Authentication over SSH Multiple CMC Sessions The following table provides the list of multiple CMC sessions that are possible using the various interfaces. Table 8. Multiple CMC Sessions Interface Number of Sessions CMC Web Interface 4 RACADM 4 Telnet 4 SSH 4 WSMAN 4 iKVM 1 Serial 1 Changing Default Login Password The warning message that prompts you to change the default password is displayed if: • You log in to CMC with Configure Users privilege.
3. – Special characters: +, &, ?, >, -, }, |, ., !, (, ', ,, _,[, ", @, #, ), *, ;, $, ], /, §, %, =, <, :, {, I, \ In the Confirm Password field, type the password again. 4. Click Continue. The new password is configured and you are logged in to CMC. NOTE: Continue is enabled only if the passwords provided in the New Password and Confirm Password fields match. For information about the other fields, see the CMC Online Help.
Updating Firmware 4 You can update firmware for the following: • CMC - active and standby • iKVM • IOMs You can update firmware for the following server components: • iDRAC - iDRACs earlier than iDRAC6 must be updated using the recovery interface. iDRAC6 firmware can also be updated with the recovery interface, but is deprecated for iDRAC6 and future versions.
Viewing Currently Installed Firmware Versions Using CMC Web Interface In the CMC Web interface, go to any of the following pages to view the current firmware versions: • Chassis Overview → Update • Chassis Overview → Chassis Controller → Update • Chassis Overview → Server Overview → Update • Chassis Overview → I/O Module Overview → Update • Chassis Overview → iKVM → Update The Firmware Update page displays the current version of the firmware for each listed component and allows you to update the f
When transferring files to and from CMC, the file transfer icon spins during the transfer. If your icon is animated, make sure that your browser is configured to allow animations. For instructions, see Allow Animations in Internet Explorer. If you experience problems downloading files from CMC using Internet Explorer, enable the Do not save encrypted pages to disk option. For instructions, see Downloading Files From CMC With Internet Explorer.
Updating iKVM Firmware The iKVM resets and becomes temporarily unavailable after the firmware is successfully uploaded. Related Links Downloading CMC Firmware Viewing Currently Installed Firmware Versions Updating iKVM Firmware Using CMC Web Interface To update the iKVM firmware using in the CMC Web interface: 1. Go to any of the following pages: – Chassis Overview → Update – Chassis Overview → Chassis Controller → Update – Chassis Overview → iKVM → Update The Firmware Update page is displayed. 2.
CMC allows IOM infrastructure device firmware (IOMINF) updates only if it detects that the IOMINF firmware is out-ofdate with the image contained in CMC file system. If the IOMINF firmware is up-to-date, CMC prevents IOMINF updates. Up-to-date IOMINF devices are not listed as updatable devices.
Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server using CMC Web interface: 1. Go to any of the following pages: – Chassis Overview → Update – Chassis Overview → Chassis Controller → Update – Chassis Overview → iKVM → Update The Firmware Update page is displayed. You can also update server iDRAC firmware at Chassis Overview → Server Overview → Update . For more information, see the Updating Server Component Firmware. 2.
NOTE: To update component firmware, the CSIOR option must be enabled for servers. To enable CSIOR on: • • 11th generation servers — After restarting the server, from the Ctrl-E setup, select System Services, enable CSIOR, and then save the changes. 12th generation servers and later— After restarting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller , enable CSIOR and save the changes.
Lifecycle Controller Job Operations Updating IOM Infrastructure Device Firmware Server Component Update Sequence In case of individual component updates, you must update the firmware versions for the server components in the following sequence: • iDRAC • Lifecycle Controller • Diagnostics (optional) • OS Driver Packs (optional) • BIOS • NIC • RAID • Other components NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecy
M910 M710HD M420 M520 M620 M820 Diagnostics 5154A0 BIOS 6.2.3 iDRAC 3.42_A00 Lifecycle Controller 1.5.5.27 Diagnostics 5154A0 BIOS 2.7.9 iDRAC 2.7.9 Lifecycle Controller 1.5.5.27 Diag 5154A0 BIOS 6.0.3 NIC 7.6.15 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.6.6 NIC 7.6.15 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.8.6 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.7.6 NIC 7.6.
M610x M710 M910 M710HD M420 M520 M620 M820 58 Diagnostics 5154A0 5158A3 BIOS 6.2.3 6.3.0 NIC 7.6.15 7.8.15 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 6.2.3 6.3.0 NIC 7.6.15 7.8.15 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 6.2.3 6.3.0 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 2.7.9 2.9.0 iDRAC 3.
Diagnostics 4225A2 4231A0 BIOS 1.6.6 2.0.21 Enabling Lifecycle Controller You can enable the Lifecycle Controller service during the server boot process: • For iDRAC6 servers, on the boot console, when prompted with the message Press for Remote Access Setup within 5 sec., press . Then, on the setup screen, enable System Services. • For iDRAC7 servers, on the boot console, select F2 for System Setup. On the setup screen, select iDRAC Settings and then select System Services.
get applied to all the NIC devices on the server. This behavior is inherent in the lifecycle controller functionality and particularly the programming contained with the Dell Update Package (DUP). Currently, Dell Update Packages (DUP) that are less than 48MB in size are supported. If the update file image size is greater, the job status indicates that the download has failed.
Upgrading Server Component Firmware From File Using CMC Web Interface To upgrade the server components firmware version to the next version using the Update from File method: 1. In the CMC Web interface, in the system tree, go to Server Overview and then click Update → Server Component Update . The Server Component Update page is displayed. 2. In the Choose Update Type section, select Update from File. For more information, see Choosing Server Component Update Type 3.
5. Click Check for Updates to view the firmware updates available in the network share. The Component/Device Firmware Inventory section displays the current firmware versions of the components and devices across all the servers present in the chassis and firmware versions of the DUPs available in the Network Share. 6. In the Component/Device Firmware Inventory section, select the check box against Select/Deselect All to select all the supported servers.
3. In the Component/Device Update Filter section, select one or more of the following: – BIOS – iDRAC – Lifecycle Controller – 32-Bit Diagnostics – OS Driver Pack – Network I/F Controller – RAID Controller The Firmware Inventory section displays only the associated components or devices across all servers present in the chassis. The filter is a pass filter; this means that it only permits components or devices associated with the filter and excludes all others.
components and devices information and allows you to verify the currently installed components and devices. This occurs when: * The server iDRAC firmware is updated to newly introduce the Lifecycle Controller functionality to the server management. * The new devices are inserted into the server.
For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/ support/manuals. Saving Chassis Inventory Report Using CMC Web Interface To save the chassis inventory report: 1. In the system tree, go to Server Overview, and then click Update → Server Component Update. The Server Component Update page is displayed. 2. Click Save Inventory. The Inventory.xml file is saved on an external system. NOTE: The Dell Repository Manager Application uses the Inventory.
6. Click Apply to apply the changes to the network share properties. NOTE: Click Return to Server Component Update to return to the Server Component Update page. Lifecycle Controller Job Operations You can perform Lifecycle Controller operations such as: • Re-install • Rollback • Update • Delete Jobs Only one type of operation can be performed at a time. Components and devices that are not supported may be listed as part of the inventory, but do not permit Lifecycle Controller operations.
3. In the Current Version column, select the checkbox for the component or device for which you want to re-install the firmware. 4. Select one of the following options: 5. – Reboot Now - Reboot immediately. – On Next Reboot - Manually reboot the server at a later time. Click Reinstall. The firmware version is re-installed for the selected component or device.
Recovering iDRAC Firmware Using CMC iDRAC firmware is typically updated using iDRAC interfaces such as the iDRAC Web interface, the SM-CLP command line interface, or operating system specific update packages downloaded from support.dell.com. For more information, see the iDRAC User’s Guide. Early generations of servers can have corrupted firmware recovered using the new update iDRAC firmware process. When CMC detects corrupted iDRAC firmware, it lists the server on the Firmware Update page.
Viewing Chassis Information and Monitoring Chassis and Component Health 5 You can view information and monitor the health for the following: • Active and standby CMCs • All severs and individual servers • Storage arrays • All IO Modules (IOMs) and individual IOMs • Fans • iKVM • Power supplies (PSUs) • Temperature sensors • LCD assembly Viewing Chassis Component Summaries When you log in to the CMC Web interface, the Chassis Health page allows you to view the health of the chassis and it
Chassis Graphics The chassis is represented by front and back views (the upper and lower images, respectively). Servers and the LCD are shown in the front view and the remaining components are shown in the back view. Component selection is indicated by a blue cast and is controlled by clicking the image of the required component. When a component is present in the chassis, an icon of that component type is shown in the graphics in the position (slot) where the component has been installed.
Icon Description No server is present. Selected Component Information Information for the selected component is displayed in three independent sections: • Health and Performance and Properties — Displays the active critical and non-critical events as shown by the hardware logs and the performance data that vary with time. • Properties — Displays the component properties that do not vary with time or change only infrequently.
The Servers Status page provides overviews of the servers in the chassis. For more information, see the CMC Online Help. Viewing Health Status and Information for Individual Server To view health status for individual servers, do any of the following: 1. Go to Chassis Overview → Properties → Health . The Chassis Health page displays a graphical overview of all the servers installed in the chassis. Server health status is indicated by the overlay of the server subgraphic.
Viewing Information and Health Status For Individual IOM To view health status of the individual IOMs, in the CMC Web interface, do any of the following: 1. Go to Chassis Overview → Properties → Health . The Chassis Health page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status for the IOMs. IOM health status is indicated by the overlay of the IOM subgraphic. Move the cursor to hover over the individual IOM subgraphic.
Move the cursor over an iKVM subgraphic and a corresponding text hint or screen tip is displayed. The text hint provides additional information for the iKVM. Click the iKVM subgraphic to view the iKVM information on the right. 2. Go to Chassis Overview → iKVM → Properties . The iKVM Status page displays the status and readings of the iKVM associated with the chassis. For more information, see the CMC Online Help.
Configuring CMC 6 CMC enables you to configure CMC properties, set up users, and set up alerts to perform remote management tasks. Before you 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. For more information, see Setting Up Initial Access to CMC. You can configure CMC using Web interface or RACADM.
Viewing and Modifying CMC Network LAN Settings The LAN settings, such as community string and SMTP server IP address, affect both the CMC and the external settings of the chassis. If you have two CMCs (active and standby) on the chassis, and they are connected to the network, the standby CMC automatically assumes the network settings of the active CMC in the event of failover. When IPv6 is enabled at boot time, three router solicitations are sent every four seconds.
racadm config -g cfgLanNetworking -o cfgNicIPv4Enable 0 NOTE: The CMC IPv4 addressing is enabled by default. To enable/disable the CMC IPv6 addressing, type: racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 1 racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 0 NOTE: The CMC IPv6 addressing is disabled by default. By default, for IPv4, the CMC requests and obtains a CMC IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically.
Setting Static DNS IP addresses NOTE: The Static DNS IP addresses settings are not valid unless the DCHP for DNS address feature is disabled.
Setting the Maximum Transmission Unit (MTU) (IPv4 and IPv6) The MTU property allows you to set a limit for the largest packet that can be passed through the interface. To set the MTU, type: racadm config -g cfgNetTuning -o cfgNetTuningMtu where is a value between 576–1500 (inclusive; default is 1500). NOTE: IPv6 requires a minimum MTU of 1280. If IPv6 is enabled, and cfgNetTuningMtu is set to a lower value, the CMC uses an MTU of 1280.
IP filtering compares the IP address of an incoming login to the IP address range that is specified.
3. Then, specify the VLAN priority for the external chassis management network: racadm config -g cfgLanNetworking -o cfgNicVLanPriority The valid values for are 0–7. Default is 0. For example: racadm config -g cfgLanNetworking -o cfgNicVLanPriority 7 You can also specify both the VLAN ID and the VLAN priority with a single command: racadm setniccfg -v For example: racadm setniccfg -v 1 7 4.
NOTE: Since the network transport for the forwarded log entries is UDP, there is no guaranteed delivery of log entries, nor is there any feedback to CMC whether the log entries were received successfully. Configuring Services Using CMC Web Interface To configure CMC services using CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Network → Services. The Services page is displayed. 2.
To enable or repair the Removable Flash Media using the CMC Web interface: 1. In the System tree, go to Chassis Overview, and then click Chassis Controller → Flash Media. The Removable Flash Media page is displayed. 2.
Adding Members to Chassis Group Removing a Member from the Leader Disbanding a Chassis Group Disabling an Individual Member at the Member Chassis Launching a Member Chassis’s or Server’s Web page Propagating Leader Chassis Properties to Member Chassis Adding Members to Chassis Group After the Chassis Group is setup, you can add members to the group: 1. Login with chassis administrator privileges to the leader chassis. 2. Select the Lead chassis in the tree. 3. Click Setup → Group Administration. 4.
Disbanding a Chassis Group To disband a chassis group from the lead chassis: 1. Login with administrator privileges to the leader chassis. 2. Select the Lead chassis in the tree. 3. Click Setup → Group Administration. 4. In the Chassis Group page, under Role, select None, and then click Apply. The lead chassis then communicates to all the members that they have been removed from the group. Finally the lead chassis discontinues its role. It can now be assigned as a member or a leader of another group.
5. – On-Change Propagation — Select this option for automatic propagation of the selected chassis property settings. The property changes are propagated to all current group members, whenever lead properties are changed. – Manual Propagation — Select this option for manual propagation of the chassis group leader properties with its members. The lead chassis property settings are propagated to group members only when a lead chassis administrator clicks Propagate.
NOTE: If a server is inserted while the chassis is powered off, the model number is not displayed anywhere in the Web interface until the chassis is powered back. The following table lists the specific data fields and specific requirements for fields to be reported for each server: Table 13. : Blade Inventory Field Descriptions Data Field Example Chassis Name Data Center Chassis Leader Chassis IP Address 192.168.0.
• iDRAC • CPLD • USC • Diagnostics • OS Drivers • RAID • NIC NOTE: The inventory information displayed for the chassis group, member chassis, servers, and server components is updated every time a chassis is added or removed from the group. Viewing Chassis Group Inventory To view the chassis group using CMC Web interface, in the system tree, select Group. Click Properties → Firmware Version. The Chassis Group Firmware Version page displays all the chassis in the group.
Obtaining Certificates The following table lists the types of certificates based on the login type. Table 14.
• A self-signed certificate is not present • The self-signed certificate is corrupt • The self-signed certificate is expired (within 30 day window) The self-signed certificate displays the common name as where cmcname is the CMC host name and domain-name is the domain name. If domain name is not available it displays only the Partially Qualified Domain Name (PQDN), which is the CMC host name.
CAUTION: When a new CSR is generated, it overwrites any previous CSR on CMC. If a pending CSR is overwritten before its server certificate is granted from a certificate authority, CMC does not accept the server certificate because the information it uses to authenticate the certificate has been lost. Take caution when generating a CSR to prevent overwriting any pending CSR. Generating a New Certificate Signing Request Using Web Interface To generate a CSR using the CMC Web interface: 1.
NOTE: To upload a Web server key and server certificate, you must have Chassis Configuration Administrator privileges. Uploading Webserver Key and Certificate Using CMC Web Interface To upload a webserver key and certificate using the CMC Web interface: 1. In the system tree, go to Chassis Overview and click Network → SSL. The SSL Main Menu is displayed. 2. Select Upload Web Key and Certificate option and click Next. 3. Specify the Private Key File and the Certificate File by clicking Choose File.
NOTE: Some configuration files contain unique CMC information (such as the static IP address) that must be modified before you export the file to other CMCs. 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. The .cfg file does not contain user passwords. When the .cfg file is uploaded to the new CMC, you must re-add all passwords. 2.
• If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various indexes. The parser reads in all of the indexes from the CMC for that group. Any objects within that group are modifications when the CMC is configured. If a modified object represents a new index, the index is created on the CMC during configuration. • You cannot specify a desired index in a .cfg file. Indexes may be created and deleted.
character to the right of the = (for example, a second =, a #, [, ], and so on) is taken as-is. These characters are valid modem chat script characters. [cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object value} • The .cfg parser ignores an index object entry. You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the first available index for that group. The racadm getconfig -f .
This file is updated as follows: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.9.143 # 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 updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.
• Blade server configurations with high Thermal Design Power (TDP) processors. • Workloads where performance is a critical. • Systems deployed in environments where the inlet temperature exceeds 30°C [86°F]. , NOTE: In the Enhanced Cooling Mode (ECM), the new generation fans provide superior cooling features when compared to current generation fans of M1000e chassis.
NOTE: If you try to enable MPCM when ECM is enabled, the ECM mode changes to enabled but unsupported state. Configuring Enhanced Cooling Mode for Fans Using RACADM To enable and configure the Enhanced Cooling Mode for fans, use the following RACADM object under the cfgThermal group: cfgThermalEnhancedCoolingMode For example, to enable the ECM mode, use: racadm config –g cfgThermal –o cfgThermalEnhancedCoolingMode 1 In case of errors, an error message is displayed.
Configuring Server 7 You can do the following for the server: • Configuring Slot Names • Configuring iDRAC Network Settings • Configuring iDRAC VLAN Tag Settings • Setting First Boot Device • Configuring Server FlexAddress • Configuring Remote File Share • Configuring BIOS Settings Using Server Clone Configuring Slot Names Slot names are used to identify individual servers.
To edit a slot name using the CMC Web interface: 1. In the system tree, go to Chassis Overview → Server Overview and then click Setup → Slot Names. The Slot Names page is displayed. 2. In the Slot Name field, edit the slot name. Repeat this step for each slot you want to rename. 3. To use the server’s host name as slot name, select Use Host Name for the Slot Name option. This override the static slot names with the server’s Host Name (or system name), if it is available.
Setting Description Set iDRAC Root Password on Server Insertion Specifies whether a server’s iDRAC root password must be changed to the value provided in the iDRAC Root Password field when the server is inserted. iDRAC Root Password When Set iDRAC Root Password on Server Insertion and QuickDeploy Enabled options are selected, this password value is assigned to a server's iDRAC root user password when the server is inserted into chassis.
Setting Description NOTE: Note the following: – – – – The values of the number of IP addresses that are less than the minimum value required for a server type are grayed out. If you select an option that is lesser than the default value of the number of IP addresses reserved, an error message is displayed warning that reducing the number of IP addresses prevents quick deploy of profiles to higher capacity servers. A warning message is logged in the CMC hardware log (SEL) and an SNMP alert is generated.
3. Setting Description Enable iDRAC IPv6 Enables IPv6 addressing for each iDRAC present in the chassis that is IPv6 capable. Enable iDRAC IPv6 Autoconfiguration Enables the iDRAC to obtain IPv6 settings (address and prefix length) from a DHCPv6 server and also enables stateless address auto configuration. By default, this option is enabled. iDRAC IPv6 Gateway Specifies the default IPv6 gateway to be assigned to the iDRACs. The default value is "::".
To modify the iDRAC Network Settings using the CMC Web interface: 1. In the system tree, go to Server Overview, and then click Setup → iDRAC. The Deploy iDRAC page is displayed. The iDRAC Network Settings section lists all installed server’s iDRAC IPv4 and IPv6 network configuration settings. 2. Modify the iDRAC network settings as required for the server(s). NOTE: You must select the Enable LAN option to specify the IPv4 or IPv6 settings. For information about the fields, see CMC Online Help. 3.
3. Click Apply to save the settings. Configuring iDRAC VLAN Tag Settings Using RACADM • Specify the VLAN ID and priority of a particular server with the following command: racadm setniccfg -m server- -v The valid values for are 1 – 16. The valid values for are 1 – 4000 and 4021 – 4094. Default is 1. The valid values for are 0 – 7. Default is 0.
Boot Device Description 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. iSCSI Boot from an Internet Small Computer System Interface (iSCSI) device. Local SD Card Boot from the local SD (Secure Digital) card - for servers that support iDRAC6 and iDRAC7 systems only.
To enable boot once for a device, use the cfgServerBootOnce object. For more information about these objects, see the RACADM Command Line Reference Guide for iDRAC and CMC available at dell.com/support/manuals. Configuring Server FlexAddress For information to configure FlexAddress for servers, see Configuring FlexAddress for Server-Level Slots.
• – CMC version 4.45 with 11G servers – CMC version 4.45 and 12G servers with Lifecycle Controller 2 version earlier than 1.1 All Settings — This version includes all the settings of the server and components on that server. These profiles are generated from CMC version 4.45 and 12G servers with iDRAC7 and Lifecycle Controller 2 version 1.1 or greater. The server configurations replication feature supports iDRAC6 and iDRAC7 servers.
Completion Status and Troubleshooting Adding or Saving Profile Before cloning the properties of a server, first capture the properties to a stored profile. Create a stored profile and provide a name and optional description for each profile. You can save a maximum of 16 stored profiles on the CMC nonvolatile extended storage media. Removing or disabling the nonvolatile extended storage media prevents access to stored profile and disables the Server Cloning feature. To add or save a profile: 1.
Accessing Server Profiles Page Importing Profile You can import a server profile that is stored on a remote file share to CMC. To import a stored profile on a remote file share to CMC: 1. In the Server Profiles page, in the Profiles on SD Card section, click Import Profile. The Import Server Profile section is displayed. 2. Click Browse to access the profile from the required location and then click Import Profile. For more information, see the CMC Online Help.
Viewing Profile Settings To view Profile settings for a selected server, go to the Server Profiles page. In the Server Profiles section, click View in the Server Profile column for the required server. The View Settings page is displayed. For more information on the displayed settings, see the CMC Online Help. NOTE: The CMC Server Cloning application retrieves and displays the settings for a specific server, only if the Collect System Inventory on Restart (CSIOR) option is enabled.
Assigning Server Profiles to Slots The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots: 1. In the Server Profiles page, go to the Profiles for Quick Deploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Server Profile column. 2. From the drop-down list, select the profile to assign to the required slot. You can select profiles to apply to multiple slots. . 3. Click Assign.
Launching iDRAC From Servers Status Page To launch the iDRAC management console from the Servers Status page: 1. In the system tree, click Server Overview. The Servers Status page is displayed. 2. Click Launch iDRAC for the server you want to launch the iDRAC Web interface. NOTE: iDRAC launch can be configured through the IP address or the DNS name. The default method is using the IP address. Launching iDRAC from Server Status Page To launch the iDRAC management console for an individual server: 1.
3. Click Launch Remote Console. Launching Remote Console from Servers Status Page To launch a remote console from the Servers Status page: 1. In the system tree, go to Server Overview, and then click Properties → Status. 2. Click Launch Remote Console for the required server. The Servers Status page is displayed.
Configuring CMC To Send Alerts 8 You can set alerts and actions for certain events that occur on the managed system. An event occurs when the status of a system component is greater than the pre-defined condition. If an event matches an event filter and you have configured this filter to generate an alert (email alert or SNMP trap), then an alert is sent to one or more configured destinations. To configure CMC to send alerts: 1. Enable the global chassis event alerts. 2.
You can configure the IPv4 and IPv6 alert destinations, email settings, and SMTP server settings, and test these settings. Before configuring the email alert or SNMP trap settings, make sure that you have Chassis Configuration Administrator privilege. Related Links Configuring SNMP Trap Alert Destinations Configuring Email Alert Settings Configuring SNMP Trap Alert Destinations You can configure the IPv6 or IPv4 addresses to receive the SNMP traps.
To obtain the mask value, use a scientific calculator in hex mode and add the second values of the individual masks (1, 2, 4, and so on) using the key. For example, to enable trap alerts for Battery Probe Warning (0x2) , Power Supply Failure (0x1000) , and KVM failure (0x80000) , key 2 1000 80000 and press the <=> key. The resulting hex value is 81002, and the mask value for the RACADM command is 0x81002. Table 17. Event Traps Filter Masks 4.
5. Specify a destination IP address to receive the traps alert: racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr -i where is a valid destination, and is the index value specified in step 4. 6. Specify the community name: racadm config -g cfgTraps -o cfgTrapsCommunityName -i where is the SNMP community to which the chassis belongs, and is the index value specified in steps 4 and 5.
Configuring Email Alert Settings Using RACADM To send a test email to an email alert destination using RACADM : 1. Open a serial/Telnet/SSH text console to CMC and log in. 2. Enable alert generation: 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. 3.
Configuring User Accounts and Privileges 9 You can setup user accounts with specific privileges (role-based authority) to manage your system with CMC and maintain system security. By default CMC is configured with a local administrator account. This default user name is root and the password is calvin. As an administrator, you can setup user accounts to allow other users to access CMC.
Privilege Description • • Provides services to the chassis, such as date and time, firmware update, and CMC reset. Is associated with the chassis, such as slot name and slot priority. Although these properties apply to the servers, they are strictly chassis properties relating to the slots rather than the servers themselves. For this reason, slot names and slot priorities can be added or changed whether or not servers are present in the slots.
Privilege Description Based on the privileges responding from the server, CMC firmware decides if the user has the right to perform the action. Listed below are the privileges and the actions on the server to which the Server Administrator is entitled. These rights are applied only when the chassis user does not have the Server Administrative privilege on the chassis.
User Group Privileges Granted Power User • • • • Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator • • • • • • • • Login Clear Logs Administrator Chassis Control Administrator (Power commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator Guest User Login Custom Select any combination of the following permissions: • • • • • • • • • • • None CMC Login User Chassis Configuration Administrator
Privilege Set Administrator Permissions Power User Permissions Guest User Permissions Debug Command Administrator Yes No No Fabric A Administrator Yes Yes No Fabric B Administrator Yes Yes No Fabric C Administrator Yes Yes No Modifying Root User Administrator Account Settings For added security, it is strongly recommended that you change the default password of the root (User 1) account. The root account is the default administrative account that ships with CMC.
The user is created with the required privileges. Configuring Local Users Using RACADM NOTE: You must be logged in as user root to execute RACADM commands on a remote Linux system. 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 if you have used the racadm racresetcfg command, the only current user is root with the password calvin.
racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 2 123456 racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminPrivilege 0x00000001 racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminEnable 1 To verify that the user was added successfully with the correct privileges, use the following commands: racadm getconfig –g cfgUserAdmin –i 2 For more information on the RACADM commands, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals.
Supported Active Directory Authentication Mechanisms You can use Active Directory to define CMC user access using two methods: Standard schema solution that uses Microsoft’s default Active Directory group objects only. Extended schema solution that has customized Active Directory objects provided by Dell. All the access control objects are maintained in Active Directory. It provides maximum flexibility to configure user access on different CMCs with varying privilege levels.
Role Group Default Privilege Level Permissions Granted • • • • • • 2 None • • • • • • • • Bit Mask Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator CMC Login User Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator 0x00000ed9 3 None CMC Login User 0x00000001 4 None No assigned permissi
– 4. If you want the directed call to search the domain controller and global catalog, select the Search AD Server to search (Optional) option and specify the domain controller and global catalog details. Click Apply to save the settings. NOTE: You must apply the settings before continuing. If you do not apply the settings, the settings are lost when you navigate to the next page. 5. In the Standard Schema Settings section, click a Role Group. The Configure Role Group page is displayed. 6.
NOTE: For bit mask number values, see the database property chapter of the RACADM Command Line Reference Guide for iDRAC7 and CMC 2.
Directory name so that users can perform authentication and authorization with Active Directory. Additionally, the administrator must add the RAC to at least one association object for users to authenticate. The following figure shows that the association object provides the connection that is needed for the authentication and authorization. NOTE: The RAC privilege object applies to DRAC 4, DRAC 5, and CMC. You can create as many or as few association objects as required.
To configure the objects for the single domain scenario: 1. Create two Association Objects. 2. Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs. 3. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privilege. 4. Group user1 and user2 into Group1. 5. Add Group1 as Members in Association Object 1 (A01), Priv1 as Privilege Objects in A01, and RAC1, RAC2 as RAC Devices in A01. 6.
1. Ensure that the domain forest function is in Native or Windows 2003 mode. 2. Create two Association Objects, A01 (of Universal scope) and A02, in any domain. The figure Setting Up Active Directory Objects in Multiple Domains shows the objects in Domain2. 3. Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs. 4. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privilege. 5. Group user1 and user2 into Group1.
Using Dell Schema Extender CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file. To make sure that the Dell Schema Extender utility functions properly, do not modify the name of this file. 1. In the Welcome screen, click Next. 2. Read and understand the warning and click Next. 3. Select Use Current Log In Credentials or enter a user name and password with schema administrator rights. 4. Click Next to run the Dell Schema Extender. 5. Click Finish. The schema is extended.
OID 1.2.840.113556.1.8000.1280.1.7.1.2 Attributes dellProductMembers dellPrivilegeMember Table 25. : dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines the privileges (Authorization Rights) for CMC device. Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsTestAlertUser dellIsDebugCommandAdmin dellPermissionMask1 dellPermissionMask2 Table 26.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.1 Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellProductMembers FALSE Description: List of dellRacDevices objects that belong to this role. This attribute is the forward link to the dellAssociationMembers backward link. Link ID: 12070 OID: 1.2.840.113556.1.8000.1280.1.1.2.2 Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.11 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: dellSchemaVersion TRUE Description: The Current Schema Version is used to update the schema. OID: 1.2.840.113556.1.8000.1280.1.1.2.12 Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.
Related Links Adding Objects to Association Object Creating RAC Device Object Creating Privilege Object Creating Association Object Creating RAC Device Object To create RAC device object: 1. In the Console Root (MMC) window, right-click a container. 2. Select New → Dell Remote Management Object Advanced. The New Object window is displayed. 3. Enter a name for the new object.
You can add groups of Users and RAC devices. The procedure for creating Dell-related groups and non-Dell-related groups is identical. Related Links Adding Users or User Groups Adding Privileges Adding RAC Devices or RAC Device Groups Adding Users or User Groups To add users or user groups: 1. Right-click the Association Object and select Properties. 2. Select the Users tab and click Add. 3. Enter the user or user group name and click OK. Adding Privileges To add privileges: 1.
NOTE: Domain controller and global catalog servers that are not correctly configured for all domains and applications may produce unexpected results during the functioning of the existing applications/domains. 4. Click Apply to save the settings. NOTE: You must apply the settings before continuing. If you do not apply the settings, the settings are lost when you navigate to the next page. 5. In the Extended Schema Settings section, type the CMC device name and the domain name. 6.
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.
added to multiple groups within the directory service. If a user is a member of multiple groups, then the user obtains the privileges of all their groups. For information about the privileges level of the role groups and the default role group settings, see Types of Users. The following figure illustrates configuration of CMC with Generic LDAP. Figure 2.
NOTE: You must have Chassis Configuration Administrator privilege. 1. In the system tree, go to Chassis Overview, and then click User Authentication → Directory Services. 2. Select Generic LDAP. The settings to be configured for standard schema is displayed on the same page. 3. Specify the following: NOTE: For information about the various fields, see the CMC Online Help. – Common Settings – Server to use with LDAP: * Static server — Specify the FQDN or IP address and the LDAP port number.
• $ racadm config -g cfgLDAP -o cfgLDAPBaseDN dc= company,dc=com CMC can be configured to optionally query a DNS server for SRV records. If the cfgLDAPSRVLookupEnable property is enabled the cfgLDAPServer property is ignored. The following query is used to search the DNS for SRV records: _ldap._tcp.domainname.com ldap in the above query is the cfgLDAPSRVLookupServiceName property. cfgLDAPSRVLookupDomainName is configured to be domainname.com.
Configuring CMC For Single Sign-On Or Smart Card Login 10 This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. Starting with CMC version 2.10, CMC supports Kerberos based Active Directory authentication to support Smart Card and SSO logins. SSO uses kerberos as an authentication method allowing users who have signed in to the domain to have an automatic or single sign-on to subsequent applications such as Exchange.
Client Systems • For only Smart Card login, the client system must have the Microsoft Visual C++ 2005 redistributable. For more information see www.microsoft.com/downloads/details.aspx?FamilyID= 32BC1BEEA3F9-4C13-9C99-220B62A191EE&displaylang=en • For Single Sign-On or smart card login, the client system must be a part of the Active Directory domain and Kerberos Realm. CMC • CMC must have firmware version 2.10 or later. • Each CMC must have an Active Directory account.
NOTE: The cmcname.domainname.com must be lower case as required by RFC and the @REALM_NAME must be uppercase. In addition, CMC supports the DES-CBC-MD5 type of cryptography for Kerberos authentication. A keytab file is generated that must be uploaded to CMC. NOTE: The keytab contains an encryption key and must be kept secure. For more information on the ktpass utility, see the Microsoft website.
Configuring CMC SSO Or Smart Card Login For Active Directory Users You can use CMC Web interface or RACADM to configure CMC SSO or smart card login. Related Links Prerequisites For Single Sign-On Or Smart Card Login Uploading the Keytab File Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface To configure Active Directory SSO or smart card login for CMC: NOTE: For information about the options, see the CMC Online Help. 1.
Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM In addition to the steps performed while configuring Active Directory, run the following command to enable SSO: racadm -g cfgActiveDirectory -o cfgADSSOEnable 1 In addition to the steps performed while configuring Active Directory, use the following objects to enable smart card login: • cfgSmartCardLogonEnable • cfgSmartCardCRLEnable 151
11 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 the system so that you can perform systems management actions through the console. For information on using the RACADM commands in CMC through the command line console, see RACADM Command Line Reference Guide for iDRAC7 and CMC.
If your management station is running Microsoft Windows XP or Windows 2003, you may experience an issue with the characters in a CMC Telnet session. This issue may occur as a frozen login where the return key does not respond and the password prompt does not appear. To fix this issue, download hotfix 824810 from support.microsoft.com. You can also see the Microsoft Knowledge Base article 824810 for more information.
Scheme Type Scheme • • 3DES-192-CBC ARCFOUR-128 Message Integrity • • • • HMAC-SHA1-160 HMAC-SHA1-96 HMAC-MD5-128 HMAC-MD5-96 Authentication Password Configure Public Key Authentication over SSH You can configure up to 6 public keys that can be used with the service username over SSH interface. Before adding or deleting public keys, be sure to use the view command to see what keys are already set up so that a key is not accidentally overwritten or deleted.
This section describes simple instructions to generate a public/private key pair for both applications. For additional or advanced usage of these tools, see the application Help. To use the PuTTY Key Generator to create the basic key for systems running Windows clients: 1. Start the application and select SSH-2 RSA or SSH-2 DSA for the type of key to generate (SSH-1 is not supported). 2. Enter the number of bits for the key. The number should be between 768 and 4096.
To add a public key using the text upload option, type: racadm sshpkauth –i svcacct –k 1 –p 0xfff –t “” Deleting Public Keys To delete a public key type: racadm sshpkauth –i svcacct –k 1 –d To delete all public keys type: racadm sshpkauth –i svcacct –k all –d Enabling Front Panel to iKVM Connection For information and instructions on using the iKVM front panel ports, see Enabling or Disabling Access to iKVM from Front Panel Configuring Terminal Emulation Software The CMC supports a seria
10. Select Exit From Minicom and press . 11. At the command shell prompt, type minicom . 12. Press , , or to exit Minicom. Ensure that the Minicom window displays a login prompt. When the login prompt appears, your connection is successful. You are now ready to login and access the CMC command line interface. Required Minicom Settings See the following table to configure any version of Minicom. Table 31.
Table 32. : Mapping I/O Modules to Switches I/O Module Label Switch A1 switch-a1 or switch- 1 A2 switch-a2 or switch-2 B1 switch-b1 or switch-3 B2 switch-b2 or switch-4 C1 switch-c1 or switch-5 C2 switch-c2 or switch-6 NOTE: There can only be one IOM connection per chassis at a time. NOTE: You cannot connect to pass-throughs from the serial console. To connect to a managed server serial console, use the command connect server-, where n is 1-8 and x is a,b, c, or d.
4. Ensure that On with console redirection via COM1 is enabled. 5. Enable Redirection After Boot (default value is Disabled). This option enables BIOS console redirection across subsequent reboots. 6. Save the changes and exit. The managed server reboots. Configuring Windows for Serial Console Redirection There is no configuration necessary for servers running the Microsoft Windows Server versions, starting with Windows Server 2003.
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 initrd /boot/initrd-2.4.9-e.3.img When you edit the /etc/grub.conf file, follow these guidelines: – – Disable GRUB's graphical interface and use the text-based interface; otherwise, the GRUB screen is not displayed in console redirection. To disable the graphical interface, comment out the line starting with splashimage.
# 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.
Using FlexAddress and FlexAdress Plus Cards 12 This section provides information about FlexAddress and FlexAddress Plus cards, how to configure and use these cards. Related Links About Flexaddress About FlexAddress Plus FlexAddress and FlexAddress Plus Comparison About Flexaddress The FlexAddress feature is an optional upgrade that allows server modules to replace the factory-assigned World Wide Name and Media Access Control (WWN/MAC) network IDs with WWN/MAC IDs provided by the chassis.
FlexAddress and FlexAddress Plus Comparison FlexAddress has 208 addresses divided into 16 server slots, thus each slot is allocated with 13 MACs. FlexAddress Plus has 2928 addresses divided into 16 server slots, thus each slot is allocated with 183 MACs. The following table shows the provision of the MAC addresses in both the features. Fabric A Fabric B Fabric C iDRAC Management Total MACs FlexAddress 4 4 4 1 13 FlexAddress Plus 60 60 60 3 183 Figure 3.
Component Minimum Required Version FC Mezzanine card - Emulex LPe1105M4, FC8 BIOS 3.03a3 and firmware 2.72A2 or later Server Module BIOS • • • • • • • PowerEdge M600 – BIOS 2.02 or later PowerEdge M605 – BIOS 2.03 or later PowerEdge M805 PowerEdge M905 PowerEdge M610 PowerEdge M710 PowerEdge M710hd PowerEdgeM600/M605 LAN on motherboard (LOM) • • Boot code firmware 4.4.1 or later iSCSI boot firmware 2.7.11 or later iDRAC • • Version 1.50 or later for PowerEdge xx0x systems Version 2.
Activating FlexAddress Plus FlexAddress Plus is delivered on the FlexAddress Plus Secure Digital (SD) card along with the FlexAddress feature. NOTE: The SD card labeled FlexAddress only contains FlexAddress and the card labeled FlexAddress Plus contains FlexAddress and FlexAddress Plus. The card must be inserted into CMC to activate the feature. Some servers, such as the PowerEdge M710HD, may require more MAC addresses than FA can provide to CMC, depending on how they are configured.
Dell Feature Cards may contain more than one feature. Once any feature included on a Dell Feature Card has been activated on a chassis, any other features that may be included on that Dell Feature Card cannot be activated on a different chassis.
The General Chassis Settings page is displayed. The FlexAddress has a value Active or Not Active. The value Active indicates that the feature is installed on the chassis and Not Active indicates that the feature is not installed and not in use on the chassis. Use the following RACADM command to display FlexAddress status for the entire chassis: racadm getflexaddr To display FlexAddress status for a particular slot: racadm getflexaddr [-i ] where is a value from 1– 16.
Configuring FlexAddress FlexAddress is an optional upgrade that allows server modules to replace the factory-assigned WWN/MAC ID with a WWN/MAC ID provided by the chassis. NOTE: In this section, the term FlexAddress also indicates FlexAddress Plus. You must purchase and install the FlexAddress upgrade to configure the FlexAddress. If the upgrade is not purchased and installed, the following text is displayed on the Web interface: Optional feature not installed.
The Deploy FlexAddress page is displayed. 2. In the Select Fabrics for Chassis-Assigned WWN/MACs section, select the fabric type for which you want to enable FlexAddress. To disable, clear the option. NOTE: If no fabrics are selected, FlexAddress is not enabled for the selected slots. The Select Slots for Chassis-Assigned WWN/MACs page is displayed. 3. Select the Enabled option for the slot for which you want to enable FlexAddress. To disable, clear the option.
where, = 1 to 16 = A, B, C = 0 or 1 0 is disable and 1 is enable. Additional FlexAddress Configuration for Linux When changing from a server-assigned MAC ID to chassis-assigned MAC ID on Linux-based operating systems, additional configuration steps may be required: • SUSE Linux Enterprise Server 9 and 10 — You may need to run Yet Another Setup Tool (YAST) on the Linux system to configure the network devices and then restart the network services.
Table 34. FlexAddress Commands and Output Situation Command Output SD card in the active CMC module is bound to another service tag. $racadm featurecard -s The feature card inserted is valid and contains the following feature(s) FlexAddress: The feature card is bound to another chassis, svctag = SD card SN = SD card in the active CMC module that is bound to the same service tag.
be bound by the terms of this agreement. If you do not agree to these terms, promptly return all Software items (disks, written materials, and packaging) and delete any preloaded or embedded Software. 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.
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Managing I/O Fabric 13 The chassis can have up to six I/O modules (IOMs), where each IOM is a pass-through or switch module. 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.
The following figure shows the location of IOMs in the chassis. The location of each IOM is indicated by its group number (A, B, or C). These discrete fabric paths are split into two IO Banks, bank one and two. On the chassis, the IOM slot names are marked A1, A2, B1, B2, C1, and C2. Figure 4. Rear View of a Chassis, Showing the Location of the IOMs 1 Bank 1 (Slots A1, B1, C1) 2 Bank 2 (Slots A2, B2, C2) CMC creates entries in both the hardware log and CMC logs for invalid hardware configurations.
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. Additionally, if the chassis is powered on, fabric verification is performed when a server or IOM is inserted (optional). If a fabric mismatch is detected, the server or IOM is allowed to power on and the status LED flashes Amber.
NOTE: Make sure that the I/O Aggregator has valid configurations so that the port link status is up. This page displays the status of the I/O Aggregator. If the status is down, it implies that the server ports on I/O Aggregator may be down due to invalid configurations. Viewing I/O Module FCoE Session Information Using Web Interface You can view the FCoE session information for Dell PowerEdge M I/O Aggregator using the CMC Web interface: 1.
NOTE: For Ethernet switches, the in-band (VLAN1) and out-of-band management IP addresses cannot be the same or on the same network; this results in the out-of-band IP address not being set. See the IOM documentation for the default in-band management IP address. NOTE: Do not configure I/O module network settings for Ethernet pass-through and Infiniband switches. Configuring Network Settings for IOMs Using CMC Web Interface NOTE: This feature is supported on PowerEdge M I/O Aggregator IOM only.
The Deploy I/O Modules page displays the IOM(s) that are powered on. 2. For the required IOM(s), click Reset. A warning message is displayed. 3. Click OK to continue.
NOTE: The FTOS or IOM software version is displayed in the format X-Y(A-B). For example, 8-3(1-4). If the Rollback Version of the FTOS image is an old image which uses the old version string format 8-3-1-4, then the Current Version is displayed as 8-3(1-4). Managing VLAN for IOM Virtual LANs (VLANs) for IOMs allow you to separate users into individual network segments for security and other reasons. By using VLANs you can isolate the networks for individual users on a 32 port switch.
The valid values for are 0 – 7. Default is 0. For example: racadm setniccfg -m switch -1 -v 1 7 For example: • To remove an IOM VLAN, disable the VLAN capabilities of the specified IOM's network: racadm setniccfg -m switch- -v The valid values for are 1 – 6. For example: racadm setniccfg -m switch-1 -v Configuring VLAN settings on IOMs Using CMC Web Interface NOTE: You can configure VLAN settings only on PowerEdge M I/O Aggregator IOM.
Viewing the VLAN settings on IOMs Using CMC Web Interface To view the VLAN settings on IOM(s) using the CMC Web interface: 1. In the system tree, go to I/O Module Overview and click Setup → VLAN Manager. The VLAN Manager page is displayed. The Summary VLANs of All Ports section displays information about the current VLAN settings for the IOMs. 2. Click Save to save the VLAN settings to a file.
Updating Untagged VLANs for IOMs Using CMC Web Interface To update untagged VLANs for IOM(s) using the CMC Web interface: 1. In the system tree, go to I/O Module Overview and click Setup → VLAN Manager . The VLAN Manager page is displayed. 2. In the Step 1: Select I/O Module section, select the required IOMs. 3. In the Step 2: Specify Port Range section, select the range of fabric ports to be assigned to the selected IOM(s). For information about the fields, see CMC Online Help. 4.
Configuring and Using iKVM 14 The local access KVM module for the 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 the chassis. It is an optional, hotpluggable 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.
Physical Connection Interfaces You can connect to a server or the CMC CLI console through the iKVM from the chassis front panel, an Analog Console Interface (ACI), and the chassis rear panel. NOTE: The ports on the control panel on the front of the chassis are designed specifically for the iKVM, which is optional. If you do not have the iKVM module, you cannot use the front control panel ports. iKVM Connection Precedences Only one iKVM connection is available at a time.
If a password is assigned, the Password dialog box appears after clicking . 2. Type the password and click OK. The Main dialog box appears. NOTE: There are four options for invoking OSCAR. You can enable one, multiple, or all of these key sequences by selecting boxes in the Invoke OSCAR section of the Main dialog box. Related Links Setting Console Security Navigation Basics Navigation Basics Table 35.
Key or Key Sequence Result Number Keys Type from the keyboard or keypad. Disabled. To change case, use the key. Configuring Oscar You can configure the OSCAR settings using the Setup dialog box. Accessing Setup Dialog Box To access the Setup dialog box: 1. Press to launch the OSCAR interface. The Main dialog box is displayed. 2. Click Setup. The Setup dialog box is displayed.
– 4. Select Slot to display servers numerically by slot number. Click OK. Assigning Key Sequences for OSCAR To assign one or more key sequences for OSCAR activation, select a key sequence from the Invoke OSCAR menu and click OK. The default key to invoke OSCAR is . Setting Screen Delay Time for OSCAR To set a screen delay time for the OSCAR, after you press enter the number of seconds (0 through 9) to delay the OSCAR display and click OK.
To exit without saving the changes, click . Managing Servers With iKVM The iKVM is an analog switch matrix supporting up to 16 servers. The iKVM switch uses the OSCAR user interface to select and configure the servers. In addition, the iKVM includes a system input to establish a CMC command line console connection to CMC.
Viewing Server Status The right columns of the Main dialog box indicates the server status in the chassis. The following table describe the status symbols. Table 36. OSCAR Interface Status Symbols Symbols Description Server is online. Server is offline or absent from chassis. Server is not available. Server is being accessed by the user channel indicated by the letter: • • A=rear panel B=front panel Selecting Servers Use the Main dialog box to select the servers.
Configuring Soft Switching To configure OSCAR for soft switching: 1. Press to launch the OSCAR interface. The Main dialog box appears. 2. Click Setup and then Menu. The Menu dialog box appears. 3. Select Name or Slot for the Display/Sort Key. 4. Type the desired delay time in seconds in the Screen Delay Time field. 5. Click OK. Soft Switching to a Server To soft switch to a server: • To select a server, press .
Setting Console Security OSCAR enables you to configure security settings on the iKVM console. You can setup a screen saver mode that engages after the console remains unused for a specified delay time. Once engaged, the console remains locked until you press any key or move the mouse. Enter the screen saver password to continue. Use the Security dialog box to lock the console with a password, set or change the password, or enable the screen saver.
– If the mode is set to Screen, the OSCAR flag bounces around the screen for the duration of the test. Before the test starts, a warning popup box displays the following message: "Energy mode may damage a monitor that is not ENERGY STAR compliant. However, once started, the test can be quit immediately via mouse or keyboard interaction." 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.
To immediately turn on the screen saver, press and then press . Clearing Lost or Forgotten Password When the iKVM password is lost or forgotten, you can reset it to the iKVM factory default, and then change the password. You can reset the password using either the CMC Web interface or RACADM. To reset a lost or forgotten iKVM password using the CMC Web interface, in the system tree, go to Chassis Overview → iKVM, click Setup tab, and then click Restore Default Values.
Removing Server from Scan List Starting the Scan Mode Cancelling Scan Mode Adding Servers to the Scan List To add servers to the scan list: 1. Press . The Main dialog box is displayed. 2. Click Setup and then Scan. The Scan dialog box is displayed listing all servers in the chassis. 3. 4. 5. Perform one of the following functions: – Select the servers you want to scan – Double-click the server name or slot. – Press and the number of the servers you want to scan.
The Main dialog box is displayed. Select a server in the list. 2. Click Commands. The Commands dialog box is displayed. 3. Clear the Scan Enable option and click OK. Broadcasting to Servers You can simultaneously control more than one server in the system to make sure that all selected servers receive identical input.
• Enable or disable access to iKVM from front panel • Enable or disable access to iKVM from the Dell CMC console Related Links Updating iKVM Firmware Enabling or Disabling Access to iKVM from Front Panel Viewing iKVM Information and Health Status Enabling Access to iKVM from the Dell CMC Console Enabling or Disabling Access to iKVM from Front Panel You can enable or disable access to iKVM from the front panel using the CMC Web interface or RACADM.
Managing and Monitoring Power 15 The Dell PowerEdge M1000e server enclosure is the most power-efficient modular server enclosure. It is designed to include highly-efficient power supplies and fans, has an optimized layout for the air to flow more easily through the system, and contains power-optimized components throughout the enclosure.
Viewing Power Budget Status Redundancy Status and Overall Power Health Configuring Power Budget and Redundancy Executing Power Control Operations You can execute the following power control operation for the chassis, servers, and IOMs. Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis.
health is marked non-critical. If the smaller grid cannot support the total chassis power allocations, then grid redundancy status is reported as No Redundancy and Chassis health is displayed as Critical. Power Supply Redundancy Policy The power supply redundancy policy is useful when redundant power grids are not available, but you may want to be protected against a single PSU failure bringing down your servers in a modular enclosure. The highest capacity PSU is kept in online reserve for this purpose.
Figure 7. No Redundancy with three PSUs in the chassis A PSU failure brings other PSUs out of Standby mode, as needed, to support the chassis power allocations. If you have four PSUs, and require only three, then in the event that one fails, the fourth PSU is brought online. A chassis can have all six PSUs online. When you enable DPSE, the extra PSUs may be placed in Standby mode to increase efficiency and save power. For more information, see Default Redundancy Configuration.
SPOPR, cannot be enabled. You are prompted to disable Extended Power Performance feature before any of these three features can be enabled. Firmware downgrade to version lower than CMC 4.5 firmware is blocked by CMC 4.5 firmware when the chassis is equipped with 3000W AC PSUs. The reason for this is that CMC firmware versions earlier than CMC 4.5 do not support 3000W AC PSUs.
DPSE can be enabled for all three power supply redundancy configurations — No Redundancy, Power Supply Redundancy, and Grid Redundancy. • In a No Redundancy configuration with DPSE, the M1000e can have up to five power supply units in Standby state. In a six PSU configuration, some PSU units are placed in Standby and stay unutilized to improve power efficiency. Removal or failure of an online PSU in this configuration causes a PSU in Standby state to become Online.
Additional PSUs, if present, are utilized to improve power efficiency of the system if DPSE is enabled. Subsequent failures after loss of redundancy may cause the servers in the chassis to power down. No Redundancy Power in excess of what is necessary to power the chassis is available, even on a failure, to continue to power the chassis. CAUTION: The No Redundancy mode uses optimum PSUs when DPSE is enabled for the requirements of the chassis.
consumption. Depending on the actual power requirements, the iDRAC power envelope may change over time. iDRAC requests a power step-up only if the servers are fully consuming the allocated power. Under heavy load the performance of the server’s processors may be degraded to ensure power consumption stays lower than the user-configured System Input Power Cap.
to accommodate the higher priority servers. Therefore, after the available power for allocation is exhausted, then CMC reclaims power from lower or equal priority servers until they are at their minimum power level. NOTE: I/O modules, fans, and iKVM (if present) are given the highest priority. CMC reclaims power only from lower priority devices to meet the power needs of a higher priority module or server.
Viewing Power Budget Status You can view the power budget status using the CMC Web interface or RACADM. Viewing Power Budget Status Using CMC Web Interface To view power budget status using CMC Web interface, in the system tree go to Chassis Overview and click Power → Budget Status. The Power Budget Status page displays the system power policy configuration, power budget details, budget allocated for server modules, and chassis power supply details. For more information, see the CMC Online Help.
• CMC does not support automated power-down of a lower priority server to allow power up of a higher priority server; however, you can perform user-initiated power-downs. • Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis. You can select any of the three PSU redundancy configuration settings listed in Default Redundancy Configuration.
PSU Configuration Dynamic PSU Engagement Firmware Response Power Supply Redundancy Enabled CMC alerts you of loss of Power Supply Redundancy. PSUs in standby mode (if any) are turned on to compensate for power budget lost from PSU failure or removal. No Redundancy Enabled Decrease power to low priority servers, if needed. Power Supply and Redundancy Policy Changes in System Event Log Changes in the power supply state and power redundancy policy are recorded as events.
FRU error Power supply failed. Unacknowledged 110V operation detected Power supply low input voltage (110) was asserted. 110V operation acknowledged Power supply low input voltage (110) was de-asserted. Events related to changes in the power redundancy status that record entries in the SEL are redundancy loss and redundancy regain for the modular enclosure that is configured for either an Grid Redundancy power policy or Power Supply Redundancy power policy.
Power Conservation and Power Budget CMC conserves power when the user-configured maximum power limit is reached. When the demand for power exceeds the user configured System Input Power Cap, CMC reduces power to servers in reverse-priority order. This allows power for higher priority servers and other modules in the chassis. If all or multiple slots in the chassis are configured with the same priority level, CMC decreases power to servers in increasing slot number order.
The overall power health is at least in Non-Critical state when the chassis is operating in 110V mode and the user has not enabled the 110V operation. The "Warning" icon is displayed on the Web interface main page when in Non-Critical state. Mixed 110V and 220V operation is not supported. If CMC detects that both voltages are in use, then one voltage is selected and those power supplies connected to the other voltage are powered off and marked as failed.
When Dell OpenManage Power Center management of power is disabled, the CMC reverts to the server priority settings before the external management was enabled. NOTE: When Dell OpenManage Power Center management is disabled, CMC does not revert to the earlier setting of the maximum chassis power. See the CMC log for the earlier setting to manually restore the value.
where is a number between 2715–16685 representing the maximum power limit in Watts. The default is 16685. For example, the following command sets the System Input Power Cap to 5400 watts: racadm config -g cfgChassisPower -o cfgChassisPowerCap 5400 . – To enable or disable dynamic PSU engagement, type: racadm config -g cfgChassisPower -o cfgChassisDynamicPSUEngagementEnable where is 0 (disable), 1 (enable). The default is 0.
Executing Power Control Operations You can execute the following power control operation for the chassis, servers, and IOMs. NOTE: Power control operations affect the entire chassis.
Executing Power Control Operations for Multiple Servers Using CMC Web Interface To execute power control operation for multiple servers using the Web interface: 1. In the system tree, go to Server Overview and click Power → Control . The Power Control page is displayed. 2.
NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. Executing Power Control Operations on IOMs Using CMC Web Interface To execute power control operations on an IOM using the CMC Web interface: 1. In the system tree, go to Chassis Overview → I/O Module Overview and click Power. The Power Control page is displayed. 2. For the IOM in the list, from the drop-down menu, select the operation you want to execute (reset or power cycle). 3. Click Apply.
Troubleshooting and Recovery 16 This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC Web interface. • Viewing chassis information. • Viewing the event logs. • Gathering configuration information, error status, and error logs. • Using the Diagnostic Console. • Managing power on a remote system. • Managing Lifecycle Controller jobs on a remote system. • Resetting components.
Subsystem RACADM Command General System/RAC information getsysinfo Session information getssinfo Sensor information getsensorinfo Switches information (IO Module) getioinfo Mezzanine card information (Daughter card) getdcinfo All modules information getmodinfo Power budget information getpbinfo KVM information getkvminfo NIC information (CMC module) getniccfg Redundancy information getredundancymode Trace log information gettracelog RAC event log gettraclog System event log getsel
Redundancy. (For full Grid Redundancy operation, ensure that a full PSU configuration of six power supplies is available.) – • • • • Problem: The PSU state is displayed as Failed (No AC), even when an AC cable is connected and the power distribution unit is producing good AC output. – Resolution A: Check and replace the AC cable. Check and confirm that the power distribution unit providing power to the power supply is operating as expected.
• Problem: Overall server performance decreases when the ambient temperature increases in the data center. – Resolution: This can occur if the System Input Power Cap has been configured to a value that results in an increased power need by fans having to be made up by reduction in the power allocation to the servers. User can increase the System Input Power Cap to a higher value that allow for additional power allocation to the fans without an impact on server performance.
NOTE: Since the log is saved as a text file, the graphical images used to indicate severity in the user interface do not appear. In the text file, severity is indicated with the words OK, Informational, Unknown, Warning, and Severe. The date and time entries appear in ascending order. If appears in the Date/Time column, it means that the event occurred during shut down or start up of any of the modules, when no date or time is available. To clear the hardware log, click Clear Log.
The Diagnostic Console page is displayed. 2. In the Command text box, enter a command and click Submit. . For information about the commands, see the CMC Online Help. A diagnostic results page is displayed. Resetting Components You can reset the active CMC, reset iDRAC without rebooting the operating system, or to virtually reseat servers causing them to behave as if they were removed and reinserted.
Troubleshooting Network Time Protocol (NTP) Errors After configuring CMC to synchronize the clock with a remote time server over the network, it may take 2-3 minutes before a change in the date and time occurs. If after this time there is still no change, it may be necessary to troubleshoot a problem. CMC may not be able to synchronize the clock for the following reasons: • Problem with the NTP Server 1, NTP Server 2, and NTP Server 3 settings.
Interpreting LED Colors and Blinking Patterns The LEDs on the chassis provide the following component status: • Steadily glowing, green LEDs indicate that the component is powered on. If the green LED is blinking, it indicates a critical but routine event, such as a firmware upload, during which the unit is not operational. It does not indicate a fault. • A blinking amber LED on a module indicates a fault on that module.
Component IOM (Pass through) Fan PSU LED Color, Blinking Pattern Status Green, dark Powered off Blue, glowing steadily Normal/stack master Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault/stack slave Green, glowing steadily Powered on Green, blinking Not used Green, dark Powered off Blue, glowing steadily Normal Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking
NOTE: It is not possible to log in to the standby CMC using a serial console. Observing LEDs to Isolate the Problem Facing the front of CMC as it is installed in the chassis, there are two LEDs on the left side of the card: • • Top LED — The top green LED indicates power. If it is not on: – Verify that you have AC present to at least one power supply. – Verify that the CMC card is seated properly.
When you type recover and then press at the recovery prompt, the recover reason and available subcommands display. An example recover sequence may be: recover getniccfg recover setniccfg 192.168.0.120 255.255.255.0 192.168.0.1 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 CMC normally because there is no active network stack.
The administrator account is temporarily reset regardless if the administrator account was removed, or if the password was changed. NOTE: When the PASSWORD_RST jumper is installed, a default serial console configuration is used (rather than configuration property values), as follows: cfgSerialBaudRate=115200 cfgSerialConsoleEnable=1 cfgSerialConsoleQuitKey=^\ cfgSerialConsoleIdleTimeout=0 cfgSerialConsoleNoAuth=0 cfgSerialConsoleCommand="" cfgSerialConsoleColumns=0 1.
NOTE: Make sure that the CMC module becomes the active CMC, and remains the active CMC until the remaining steps are completed. 4. If the jumpered CMC module is the only CMC, then wait for it to finish rebooting. If there is a redundant CMCs in the chassis, then initiate a changeover to make the jumpered CMC module active. In the Web interface, in the system tree, go to Chassis Overview and click Power → Control, select the Reset CMC (warm boot), and click Apply.
17 Using LCD Panel Interface You can use the LCD panel on the chassis to perform configuration and diagnostics, and to obtain status information about the chassis and its contents. The following figure illustrates the LCD panel. The LCD screen displays menus, icons, pictures, and messages. Figure 10.
• • 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. 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. When messages displayed on the LCD screen are longer than what fits on the screen, use the left and right arrow buttons to scroll the text left and right.
Graphical Server Status Screen Graphical Module Status Screen Enclosure Menu Screen Module Status Screen Enclosure Status Screen IP Summary Screen 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. • Enclosure — displays status information for the chassis. Use the up and down arrow buttons to highlight an item.
1. Use the up and down arrow buttons to highlight the screen you want to set to the default. 2. Press the center button. The Accept icon is highlighted. 3. Press the center button again to confirm the change. The Default Screen is displayed. Graphical Server Status Screen The Graphical Server Status screen displays icons for each server installed in the chassis and indicates the general health status for each server.
• Main Menu Use the navigation buttons to highlight the desired item (highlight the Back icon to return to the Main Menu) and press the center button. The selected screen displays. Module Status Screen The Module Status screen displays information and error messages about a module. For messages that can appear on this screen, see LCD Module and Server Status Information and LCD Error Messages. Use the up and down arrow keys to move through messages.
Figure 11. Removing and Installing LCD Module 1 cable cover 2 LCD module 3 ribbon cable 4 hinges (2) 5 screws (2) Table 45. LCD Hardware Troubleshooting Items 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 CMC is booting; then, reset CMC using GUI or RACADM commands. Alert screen message CMC Not Responding and LED is solid amber or is off.
• The control panel cable is not connected, or is improperly connected. Reseat cables. LCD screen message No CMC Found. No CMC is present in the chassis. Insert a CMC into the chassis or reseat existing CMC if present. Front Panel LCD Messages This section contains two subsections that list error and status information that is displayed on the front panel LCD. Error messages on the LCD have a format that is similar to the System Event Log (SEL) viewed from the CLI or Web interface.
Severity Message Cause Critical The power supplies are not redundant. Insufficient resources to maintain normal operations. One or more PSU have failed or removed and the system lacks sufficient power to maintain normal operations. This could cause servers to power down. Warning The control panel ambient temperature is greater than the upper warning threshold. Chassis/Enclosure intake temperature exceeded the warning threshold.
Table 51. PSU Status Screens Severity Message Cause Critical Power supply failed. The PSU has failed. Critical The power input for power supply is lost. Loss of AC power or AC cord unplugged. Warning Power supply is operating at 110 volts, Power supply is plug into a 110 volt source. and could cause a circuit breaker fault. Table 52. Server Status Screen Severity Message Cause Warning The system board ambient temperature is less Server temperature is getting cool.
Severity Message Cause Critical Mezz B Status: Add-in Card sensor for Mezz B, install error was asserted. Incorrect Mezzanine card installed for IO fabric. Critical Mezz C Status: Add-in Card sensor for Mezz C, install error was asserted. Incorrect Mezzanine card installed for IO fabric. Critical Drive is removed. Storage Drive was removed. Critical Fault detected on Drive . Storage Drive failed.
Severity Message Cause Critical A PCI parity error was detected on a component at slot . Parity error was detected on the PCI bus. Critical A PCI system error was detected on a PCI error detected by device. component at bus device function . Critical A PCI system error was detected on a component at slot . PCI error detected by device. Critical Persistent correctable memory error logging disabled for a memory device at location .
Table 53. CMC Status Item Description Example: CMC1, CMC2 Name or Location. No Errors If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. Firmware Version Only displays on an active CMC. Displays Standby for the standby CMC. IP4 Displays current IPv4 enabled state only on an active CMC. IP4 Address: Only displays if IPv4 is enabled only on an active CMC.
RPM Current fan speed in RPM. Table 56. PSU Status Item Description Name/Location Example: PSU1, PSU2, and so on. Error Messages If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. Status Offline, Online, or Standby. Maximum Wattage Maximum Wattage that PSU can supply to the system. Table 57. IOM Status Item Description Name/Location Example: IOM A1, IOM B1. and so on.
NOTE: This information is dynamically updated Table 59. Server Status Item Description Example: Server 1, Server 2, etc. Name/Location. No Errors If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. For more information see LCD Error Messages. Slot Name Chassis slot name. For example, SLOT-01. NOTE: You can set this table through the CMC CLI or Web interface.
The information is displayed only if iDRAC has completed booting. For more information on this feature, see the RACADM Command Line Reference Guide for iDRAC7 and CMC at dell.com/support/manuals.
Frequently Asked Questions 18 This section lists the frequently asked questions for the following: • RACADM • Managing and Recovering a Remote System • Active Directory • FlexAddress and FlexAddressPlus • iKVM • IOM RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) This message indicates that another command must be issued only after CMC completes the reset.
To address this security concern, upload a CMC server certificate issued to the IP address of CMC. When generating the certificate signing request (CSR) to be used for issuing the certificate, ensure that the common name (CN) of the CSR matches the IP address of CMC (for example, 192.168.0.120) or the registered DNS CMC name. To ensure that the CSR matches the registered DNS CMC name: 1. In the CMC Web interface, go to the System tree, click Chassis Overview. 2.
Active Directory Does Active Directory support CMC login across multiple trees? Yes. The CMC’s Active Directory querying algorithm supports multiple trees in a single forest. Does the login to CMC using Active Directory work in mixed mode (that is, the domain controllers in the forest run different operating systems, such as Microsoft Windows 2000 or Windows Server 2003)? Yes.
No activation or modifications to the card should occur. The card is ignored by CMC.
NOTE: If the standby CMC firmware is not updated to 1.10 or later and a failover occurs, the FlexAddress feature is not configured. The feature must be reactivated and reconfigured again. How can a SD card be recovered if the SD card was not in the chassis when the deactivation command was executed on the FlexAddress? The issue is that the SD card cannot be used to install FlexAddress on another chassis if it was not in CMC when the FlexAddress was deactivated.
• The iKVM firmware has detected a hardware error. For additional information, view the iKVM status. The iKVM is tiered through the ACI port to an external KVM switch, but all of the entries for the ACI connections are unavailable. All of the states are showing a yellow dot in the OSCAR interface. 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.
bar of the browser. The browser redirects you to the https (secure mode) and enables you to log in to the CMC. Both http and https are valid for the browsers. If you save the URL as a bookmark, you do not have to any text after the last forward slash in the example. If you still cannot log in using the SSO, see the Configuring CMC SSO or Smart Card Login for Active Directory Users section.
Use Case Scenarios 19 This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Chassis Basic Configuration and Firmware Update This scenario guides you to perform the following tasks: • Bring up the chassis with basic configurations. • Verify that hardware is being detected by CMC without any errors. • Update firmware for CMC, IOMs, and server components. 1. CMC is pre-installed on your chassis and hence no installation is required.
3. Save the existing configurations of a server to an external storage card, using the CMC Web interface. For information, see the Adding or Saving Profile section. 4. Apply the configurations saved on the external storage card to the required server, using the CMC Web interface . For information, see the Applying Profile section.
– Allow 110 VAC Operation. • Selecting the check box to enable Server Based Power Management (SBPM), displays the following message: Checking the Server Based Power Management Mode option will set your power cap to max value, server priorities to default priority, and disables Max Power Conservation Mode.
• Changing Power Redundancy Policy from Grid Redundancy Policy to PSU Redundancy Policy on a 3000W AC PSU racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy 2 This feature is not supported while Extended Power Performance is enabled. • Changing Power Redundancy Policy from Grid Redundancy Policy to No Redundancy Policy on a 3000W AC PSU racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy 0 This feature is not supported while Extended Power Performance is enabled.
