Dell PowerEdge M1000e Chassis Management Controller Firmware Version 5.
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. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview...............................................................................................................14 What Is New In This Release............................................................................................................... 15 Key Features.........................................................................................................................................15 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..........................................................................................................
Viewing Currently Installed Firmware Versions Using RACADM................................................. 51 Updating CMC Firmware.....................................................................................................................51 Updating CMC Firmware Using Web Interface............................................................................ 52 Updating CMC Firmware Using RACADM....................................................................................
Viewing LCD Information and Health................................................................................................ 79 6 Configuring CMC................................................................................................81 Viewing and Modifying CMC Network LAN Settings.........................................................................82 Viewing and Modifying CMC Network LAN Settings Using CMC Web Interface.......................
Configuring Multiple CMCs Using RACADM................................................................................... 100 Creating a CMC Configuration File.............................................................................................101 Parsing Rules............................................................................................................................... 102 Modifying the CMC IP Address...................................................................................
Configuring CMC To Send Alerts.................................................................. 126 Enabling Or Disabling Alerts............................................................................................................. 126 Enabling Or Disabling Alerts Using CMC Web Interface........................................................... 126 Enabling Or Disabling Alerts Using RACADM.............................................................................
CMC Command Line Console Features.......................................................................................... 165 CMC Command Line Commands.............................................................................................. 165 Using Telnet Console With CMC......................................................................................................166 Using SSH With CMC...........................................................................................................
Monitoring IOM Health..................................................................................................................... 194 Viewing I/O Module Uplink and Downlink Status Using Web Interface......................................... 195 Viewing I/O Module FCoE Session Information Using Web Interface............................................195 Viewing Stacking Information for Dell PowerEdge M I/O Aggregator...........................................
Enabling or Disabling Access to iKVM from Front Panel........................................................... 216 Enabling Access to iKVM from the Dell CMC Console.............................................................. 217 15 Managing and Monitoring Power................................................................218 Redundancy Policies......................................................................................................................... 219 Grid Redundancy Policy...........
Executing Power Control Operations on an IOM..................................................................... 239 16 Troubleshooting and Recovery...................................................................240 Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP...................... 240 Supported Interfaces..................................................................................................................
18 Frequently Asked Questions.........................................................................271 RACADM............................................................................................................................................ 271 Managing and Recovering a Remote System.................................................................................. 272 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 hotpluggable 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: • Support for 13th generation servers. NOTE: For more information on the applicable servers, see the Dell Chassis Management Controller (CMC) Version 5.0 for Dell PowerEdge M1000e Release Notes available at dell.com/ support/manuals. • iDRAC and Lifecycle Controller firmware update for 13th generation servers using a single iDRAC firmware package. • Option to use an external library (CIFS/NFS directory) to store server profiles.
• CMC alert — Alerts you about potential managed node issues through an email message or SNMP trap. • Remote power management — Provides remote power management functions, such as shut down and reset on any chassis component, from a management console. • Power usage reporting. • Secure Sockets Layer (SSL) encryption — Provides secure remote system management through the Web interface. • Launch point for the Integrated Dell Remote Access Controller (iDRAC) Web interface.
• Configurable session auto time out, and more than one simultaneous sessions. • Limited IP address range for clients connecting to CMC. • Secure Shell (SSH), which uses an encrypted layer for higher security. • Single Sign-on, Two-Factor Authentication, and Public Key Authentication. Chassis Overview The following figure shows the facing edge of a CMC (inset) and the locations of the CMC slots in the chassis.
The following table lists the ports that CMC uses as a client. Table 2. CMC Client Port Port Number Function 25 SMTP 53 DNS 68 DHCP-assigned IP address 69 TFTP 162 SNMP trap 514* Remote syslog 636 LDAPS 3269 LDAPS for global catalog (GC) * Configurable port Minimum CMC Version The following table lists the minimum CMC version required to enable the listed Blade Servers. Table 3. Minimum CMC Version for Blade Servers Servers Minimum version of CMC PowerEdge M600 CMC 1.
Table 4. Minimum CMC Version for IOMs IOM Switches Minimum version of CMC PowerConnect M6220 CMC 1.0 PowerConnect M6348 CMC 2.1 PowerConnect M8024 CMC 1.2 PowerConnect M8024-k CMC 3.2 PowerConnect M8428-k CMC 3.1 Dell 10/100/1000Mb Ethernet Pass-Through CMC 1.0 Dell 4Gbps FC Pass-Through Module CMC 1.0 Dell 8/4Gbps FC SAN Module CMC 1.2 Dell 10Gb Ethernet Pass-Through CMC 2.1 Dell 10Gb Ethernet Pass-Through II CMC 3.0 Dell 10Gb Ethernet Pass-Through-K CMC 3.0 Brocade M4424 CMC 1.
Servers BIOS iDRAC Lifecycle Controller PowerEdge M805 2.3.3 1.65 Not Applicable PowerEdge M905 2.3.3 1.65 Not Applicable PowerEdge M610 6.3.0 3.50 1.6 PowerEdge M610x 6.3.0 3.50 1.6 PowerEdge M710 6.3.0 3.50 1.6 PowerEdge M710HD 7.0.0 3.50 1.6 PowerEdge M910 2.9.0 3.50 1.6 Power Edge M915 3.0.4 3.50 1.6 PowerEdge M420 2.0.22 1.50.50 1.3.0 PowerEdge M520 2.0.22 1.50.50 1.3.0 PowerEdge M620 2.0.19 1.50.50 1.3.0 PowerEdge M820 2.0.21 1.50.50 1.3.
Connection Features Other connections • Access to the Dell CMC console through the Avocent Integrated KVM Switch Module (iKVM). Supported Platforms CMC supports modular systems designed for the PowerEdge M1000e platform. For information about compatibility with CMC, see the documentation for your device. For the latest supported platforms, see the Chassis Management Controller Version 5.0 Release Notes located at dell.com/support/manuals.
• Click Remote Enterprise System Management and then click Dell Chassis Management Controller Version 5.0 to view: – The CMC Online Help provides information about using the Web interface. – The Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification provides minimum BIOS and firmware version, installation and usage information.
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. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to dell.com/support. 2. Select your support category. 3.
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.
NOTE: Do not turn on the servers. 6. Using the LCD panel on the front of the system, provide CMC with a static IP address or configure it for DHCP. 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.
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.
• • Docs — Contains documentation for systems, systems management software products, peripherals, and RAID controllers. SERVICE — Contains the tools required to configure your system, and delivers the latest diagnostics and Dell-optimized drivers for your system. For information about installing Dell OpenManage software components, see the Dell OpenManage Installation and Security User's Guide available on the DVD or at dell.com/support/manuals.
operating system, some Internet Explorer settings can interfere with connectivity even though you use a command line interface to access the management network.
happen if you are using the browser or another interface such as remote RACADM. Follow these steps to disable the phishing filter: 1. Start Internet Explorer. 2. Click Tools → Phishing Filter, and then click Phishing Filter Settings. 3. Select the Disable Phishing Filter check box and click OK. Certificate Revocation List (CRL) Fetching If your CMC has no access to the Internet, disable the certificate revocation list (CRL) fetching feature in Internet Explorer.
Ensure that CMC and iDRAC on each server and the network management ports for all switch I/O Modules are connected to a common internal network in the M1000e chassis. This allows the management network to be isolated from the server data network. It is important to separate this traffic for uninterrupted access to chassis management. CMC is connected to the management network. All external access to CMC and iDRACs is accomplished through CMC.
• Remote RACADM • CMC Web interface CMC supports both IPv4 and IPv6 addressing modes. The configuration settings for IPv4 and IPv6 are independent of one another. Configuring CMC Network Using LCD Panel Interface NOTE: The option to configure CMC using the LCD panel is available only until CMC is deployed or the default password is changed. If the password is not changed, you can the continue to use the LCD to reset the configurations of the CMC causing a possible security risk.
Dynamic Host Configuration Protocol (DHCP) CMC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. CMC is assigned to a unique IP address allotted over your network. If you have selected the DHCP option, press the center button. The Configure iDRAC screen appears; go to step 9.
• • 11. select a number for each position. This address is the static IP of the iDRAC located in the first slot. The static IP address of each subsequent iDRAC is calculated as a slot number increment of this IP address. When you have finished setting the Static IP Address, press the center button to continue. Set the subnet mask, and then press the center button. Set the gateway, and then press the center button. • Select whether to Enable or Disable the IPMI LAN channel.
Interface Description 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 Chassis Management Controller Version 5.0 Release Notes at dell.com/support/manuals. Remote RACADM command line interface Use this command line utility to manage CMC and its components.
Interface Description 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.org/standards/profiles/ • WS-MAN release notes or Read Me file. • www.wbemsolutions.com/ws_management.
The General Chassis Settings page is displayed. 2. Type the location properties and the chassis name. For more information, see the CMC Online Help. NOTE: The Chassis Location field is optional. It is recommended to use the Data Center, Aisle, Rack, and Rack Slot fields to indicate the physical location of the chassis. 3. Click Apply. The settings are saved.
NOTE: Only servers can be selected on this page. • Chassis Overview → I/O Module Overview → Troubleshooting → Identify. The Identify page is displayed. 2. To enable blinking for a component LED, select required component and click Blink. 3. To disable blinking for a component LED, clear the required component and click UnBlink.
The Log in Security enables you to configure the IP range attributes for CMC login using the CMC Web interface. To configure the IP range attributes using CMC Web interface: 1. In the system tree, go to Chassis Overview and click Network → Network. The Network Configuration page is displayed. 2. In the IPv4 Settings section, click Advanced Settings. Alternatively, to access the Log in Security page, in the system tree, go to Chassis Overview, click Security → Log in.
• Run the RACADM cmcchangeover command. (See the cmcchangeover command section in the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide). • Run the RACADM racreset command on the active CMC. (See the racreset command section in the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide). • Reset the active CMC from Web interface.
• CMC reset — Chassis management resumes after CMC reboots or chassis fails over to the standby CMC. • CMC failover command issued — Chassis management resumes after the chassis fails over to the standby CMC. • CMC firmware update — Chassis management resumes after CMC reboots or chassis fails over to the standby CMC. It is recommended that you update the standby CMC first so that there is only one failover event.
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 Using Smart Card Logging Into CMC Using Single Sign-on 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.
Configuring User Accounts and Privileges Accessing CMC Web Interface Logging Into CMC Using Smart Card You can log in to CMC using a smart card. Smart cards provide Two Factor Authentication (TFA) that provide two-layers of security: • Physical smart card device. • Secret code such as a password or PIN. Users must verify their credentials using the smart card and the PIN. NOTE: You cannot use the IP address to log in to CMC using Smart Card login.
• You have logged in to your system using a valid Active Directory user account. • Single Sign-On option is enabled during Active Directory configuration. To log in to CMC using Single Sign-on: 1. Log in to the client system using your network account. 2. Access the CMC Web interface using: https:// For example, cmc-6G2WXF1.cmcad.lab, where cmc-6G2WXF1 is the cmc-name and cmcad.lab is the domain-name.
• Remote RACADM — Allows you to run RACADM commands on a management station with the -r option and the DNS name or IP address of the CMC. • Firmware RACADM — Allows you to log in to the CMC using Telnet, SSH, a serial connection, or the iKVM. With Firmware RACADM, you run the RACADM implementation that is part of the CMC firmware. You can use remote RACADM commands in scripts to configure multiple CMCs. CMC does not have support for scripting. Therefore, you cannot run the scripts directly on the CMC.
Interface Maximum Sessions per Interface WS-MAN 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. • Default password warning feature is enabled. • Default user name and password for any currently enabled account are root and calvin respectively. The same warning message is displayed if you log in using Active Directory or LDAP.
where, is a value from 1 to 16 (indicates the user account) and is the new user–defined password. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Enabling or Disabling Default Password Warning Message You can enable or disable the display of the default password warning message. To do this, you must have Configure Users privilege.
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.
DRM to search for latest firmware updates, see Using Dell Repository Manager to Search for the Latest Updates on the Dell Support Site on the Dell Tech Center. For information on saving the inventory file that DRM uses as input to create the repositories, see Saving Chassis Inventory Report Using CMC Web Interface Saving Chassis Inventory Report Using CMC Web Interface.
Viewing Currently Installed Firmware Versions Using RACADM To view the currently installed firmware versions using RACADM, use the getkvminfo subcommand. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Updating CMC Firmware You can update CMC firmware using Web interface or RACADM. The firmware update, by default, retains the current CMC settings.
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 CMC Firmware Using RACADM To update CMC firmware using RACADM, use the fwupdate subcommand. For more information, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Updating iKVM Firmware The iKVM resets and becomes temporarily unavailable after the firmware is successfully uploaded.
Updating IOM Infrastructure Device Firmware By performing this update, the firmware for a component of the IOM device is updated, but not the firmware of the IOM device itself; the component is the interface circuitry between the IOM device and CMC. The update image for the component resides in the CMC file system, and the component displays as an updatable device on the CMC Web interface only if the current revision on the component and the component image on CMC do not match.
Updating IOM Firmware Using RACADM To update IOM infrastructure device firmware using RACADM, use the fwupdate subcommand. For more information, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server using in the CMC Web interface: 1.
Updating Server iDRAC Firmware Using RACADM To update iDRAC firmware using RACADM, use the fwupdate subcommand. For more information, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide for iDRAC and CMC. Updating Server Component Firmware The one-to-many update feature in CMC enables you to update server component firmware across multiple servers.
NOTE: The Single Click all blade update method has the following benefits: • Enables you to update all the components on all the blade servers with minimal clicks. • All the updates are packaged in a directory. This avoids individual upload of each component’s firmware. • Faster and consistent method of updating the server components.
NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecycle Controller. Supported Firmware Versions for Server Component Update The following section provides the supported component versions for CMC firmware update and Server Component Update. The following table lists the supported firmware versions for server components when CMC Firmware is updated from 4.5 to 5.0 version but the server components are not updated to the next version.
M710HD M420 M520 M620 M820 M630 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.15 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.
Lifecycle Controller Not Applicable Diagnostics Not Applicable BIOS Not Applicable The following table lists the supported firmware versions for server components in a scenario where the existing CMC Firmware version is 5.0 and the server components are updated from N-1 version to N version. NOTE: Server components firmware update from N-1 version to N version is successful when the CMC firmware is at version 4.
M710HD M420 M520 M620 M820 Diagnostics 5154A0 5158A3 BIOS 2.7.9 2.9.0 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 6.0.3 7.0.0 NIC 7.6.15 7.8.15 iDRAC 1.45.45 1.50.50 Lifecycle Controller 1.1.5.165 1.3.0.850 Diagnostics 4225A2 4231A0 BIOS 1.6.6 2.0.22 NIC 7.6.15 7.8.15 iDRAC 1.45.45 1.50.50 Lifecycle Controller 1.1.5.165 1.3.0.850 Diagnostics 4225A2 4231A0 BIOS 1.8.6 2.0.22 NIC 7.6.15 7.8.15 iDRAC 1.45.
M630 iDRAC Not Applicable 2.05.05.05 Lifecycle Controller Not Applicable 2.05.05.05 Diagnostics Not Applicable 4239A16_4239.24 BIOS Not Applicable 0.4.3 Enabling Lifecycle Controller You can enable the Lifecycle Controller service during the server boot process: • • For iDRAC 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.
NOTE: For iDRAC and OS Driver packs firmware update, make sure the Extended Storage feature is enabled. It is recommended to clear the job queue before initializing a server component firmware update. A list of all jobs on the server(s) is available on the Lifecycle Controller Jobs page. This page enables deletion of single or multiple jobs or purging of all jobs on the server. See the Troubleshooting section, "Managing Lifecycle Controller jobs on a remote system" .
iDRAC Yes **No *No *No Power Supply Unit Yes Yes Yes Yes CPLD No Yes Yes Yes FC Cards Yes Yes Yes Yes PCIe SSD Yes Yes Yes Yes * Indicates that though a system restart is not required, iDRAC must be restarted to apply the updates. iDRAC communication and monitoring will temporarily be interrupted. ** When iDRAC is updated from version 1.30.30 or later, a system restart is not necessary. However, firmware versions of iDRAC earlier than 1.30.
NOTE: The update size limitation of either a single DUP or combined DUPs can be ignored if the Extended Storage feature is installed and enabled. For information on enabling extended storage, see Configuring CMC Extended Storage Card. 5. Specify the firmware image file for the selected components or devices. This is a Microsoft Windows Dell Update Package (DUP) file. 6. Select one of the following options: • Reboot Now - Reboot immediately.
The Server Component Update page is displayed. 2. In the Choose Update Type section, select Update from Network Share. For more information, see Choosing Server Component Update Type. 3. Click Save Inventory to export the chassis inventory file that contains the components and firmware details. The Inventory.xml file is saved on an external system. The Dell Repository Manager uses the inventory.xml file to create customized bundles of updates.
• If the BIOS filter is selected, only the BIOS inventory for all servers is displayed. If the set of servers consists of a number of server models, and a server is selected for BIOS update, the automatic filtering logic automatically removes all the other servers that do not match with the model of the selected server. This ensures that the selection of the BIOS firmware update image (DUP) is compatible with the correct model of the server.
For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals. Viewing Firmware Inventory You can view the summary of the firmware versions for all components and devices for all servers currently present in the chassis along with their status. Viewing Firmware Inventory Using CMC Web Interface To view the firmware inventory: 1.
Field Description chassis), that help to identify the location of the server in the chassis. When there are less than 16 servers occupying slots, only those slots populated by servers are displayed. Name Displays the name of the server in each slot. Model Displays the model of the server. Component/Device Displays a description of the component or device on the server. If the column width is too narrow the mouse-over tool provides a view of the description.
Configuring Network Share Using CMC Web Interface To configure or edit the Network Share location or credentials: 1. In the CMC Web interface, in the system tree, go to Server Overview and then click Network Share. The Edit Network Share page is displayed. 2.
Sometimes, when an operation is in the process of being submitted for scheduling through another session or context, another operation is attempted. In this case, a confirmation popup message is displayed indicating the situation and the operation must not be submitted. Wait for the operation in process to complete and then submit the operation again. Do not navigate away from the page after an operation is submitted for scheduling.
3. In the Rollback Version column, select the check box for the component or device for which you want to roll back 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 Rollback. The previously installed firmware version is re-installed for the selected component or device.
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 its components.
displayed when you click on that component. In addition, the latest events in the CMC Hardware Log are also displayed. For more information, see the CMC Online Help. If your chassis is configured as a Group Lead, the Group Health page is displayed after login. It displays the chassis level information and alerts. All active critical and non-critical alerts are displayed. Chassis Graphics The chassis is represented by front and back views (the upper and lower images, respectively).
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.
Power Supply Units Power Status Fans • IOM Slot Speed • Firmware • Hardware Capacity • Lower Critical Threshold • Upper Critical Threshold • Power State • Model • Role • Service Tag • Power Supply Status • Power Consumption • System Budget • Fans Status IOM Status Viewing Server Model Name and Service Tag You can view the model name and service tag of each server instantly using the following steps: 1. Expanding Servers in the System tree.
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. Move the cursor to hover over an individual server subgraphic. A corresponding text hint or screen tip provides additional information for that server.
The I/O Module Status page provides overviews of all IOMs associated with the chassis. For more information, see the CMC Online Help. 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.
To view the health status of the iKVMs associated with the chassis, do any of the following: 1. Go to Chassis Overview → Properties → Health. The Chassis Health page is displayed. The lower section of chassis graphics provides the rear view of the chassis and contains the health status of the iKVM. iKVM health status is indicated by the overlay of the iKVM subgraphic. Move the cursor over an iKVM subgraphic and a corresponding text hint or screen tip is displayed.
The Chassis Health page is displayed. The top section of Chassis Graphics depicts the front view of the chassis. LCD health status is indicated by the overlay of the LCD subgraphic. 2. Move the cursor over the LCD subgraphic. The corresponding text hint or screen tip provides additional information on the LCD. 3. Click the LCD subgraphic to view the LCD information on the right. 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.
Configuring Multiple CMCs Using 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.
NOTE: If you disable CMC network interface, the disable operation performs the following actions: • Disables the network interface access to out-of-band chassis management, including iDRAC and IOM management. • Prevents the down link status detection. • To disable only CMC network access, disable both CMC IPv4 and CMC IPv6. NOTE: The CMC NIC is enabled by default.
You can disable the DHCP for NIC address feature and specify a static IP address, subnet mask, and gateway. For more information, see Setting Up Initial Access to CMC. Enabling or Disabling DHCP for DNS IP Addresses By default, the CMC’s DHCP for DNS address feature is disabled. When enabled, this feature obtains the primary and secondary DNS server addresses from the DHCP server. While using this feature, you do not have to configure static DNS server IP addresses.
• DNS Domain Name — The default DNS domain name is a single blank character. To set a DNS domain name, type: racadm config -g cfgLanNetworking -o cfgDNSDomainName where is a string of up to 254 alphanumeric characters and hyphens. For example: p45, atz-1, r-id-001.
Configuring IP Range Attributes Using CMC Web Interface NOTE: To perform the following task, you must have Chassis Configuration Administrator privilege. To configure the IP range attributes using CMC Web interface: 1. In the system tree, go to Chassis Overview and click Network → Network. The Network Configuration page is displayed. 2. In the IPv4 Settings section, click Advanced Settings. The Log in Security page is displayed.
Configuring Virtual LAN Tag Properties for CMC VLANs are used to allow multiple virtual LANs to co-exist on the same physical network cable and to segregate the network traffic for security or load management purposes. When you enable the VLAN functionality, each network packet is assigned a VLAN tag. Configuring Virtual LAN Tag Properties for CMC Using Web Interface To configure VLAN for CMC using the CMC Web interface: 1.
4. To remove the CMC VLAN, disable the VLAN capabilities of the external chassis management network: racadm config -g cfgLanNetworking -o cfgNicVLanEnable 0 You can also remove the CMC VLAN using the following command: racadm setniccfg -v Configuring Services You can configure and enable the following services on CMC: • CMC Serial console — Enable access to CMC using the serial console. • Web Server — Enable access to CMC Web interface.
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. Configure the following services as required: • CMC serial console • Web server • SSH • Telnet • Remote RACADM • SNMP • Remote Syslog For information about the fields, see CMC Online Help. 3. Click Apply, and then update all default time outs and maximum time out limits.
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.
Disabling an Individual Member at the Member Chassis 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.
Propagating Leader Chassis Properties to Member Chassis You can apply the properties from the leader to the member chassis of a group. To synchronize a member with the leader properties: 1. Login with administrator privileges to the leader chassis. 2. Select the Lead chassis in the tree. 3. Click Setup → Group Administration. 4.
To get the most accurate server inventory report: • • The Chassis Group leader chassis and all Chassis Group member chassis must be in Chassis Power State On. All servers in the associated chassis must be powered on.
→ From Text in MS Excel. After the inventory report is imported into MS Excel, and if a message is displayed prompting for additional information, select comma-delimited to import the file into MS Excel. Chassis Group Inventory and Firmware Version The Chassis Group Firmware Version page displays the group inventory and firmware versions of the servers and the server components in the chassis. This page also enables you to organize the inventory information and filter the firmware versions view.
NOTE: The firmware versions of USC, Diagnostics, OS Drive, RAID devices, and NIC devices of servers are not available if: • The server belongs to the 10th generation of PowerEdge servers. These servers do not support Lifecycle Controller. • The server belongs to the 11th generation of PowerEdge servers, but the iDRAC firmware does not support Lifecycle Controller. • The CMC firmware version of a member chassis is earlier to version 4.45.
• Allow the client to authenticate itself to the server. • Allow both systems to establish an encrypted connection. This encryption process provides a high level of data protection. CMC employs the 128-bit SSL encryption standard, the most secure form of encryption generally available for Internet browsers in North America. The CMC Web server includes a Dell self-signed SSL digital certificate (Server ID).
Generating a New Certificate Signing Request To ensure security, it is strongly recommended that you obtain and upload a secure server certificate to CMC. Secure server certificates ensure the identity of a remote system and that information exchanged with the remote system cannot be viewed or changed by others. Without a secure server certificate, CMC is vulnerable to access from unauthorized users.
NOTE: If you upload a certificate and try to view it immediately, an error message is displayed indicating that the requested operation cannot be performed. This happens because the web server is in the process of restarting with the new certificate. After the web server restarts, the certificate is uploaded successfully and you can view the new certificate. After uploading a certificate, you may experience a delay of around one minute before being able to view the uploaded certificate.
NOTE: Only X509, Base-64 encoded certificates are accepted by CMC. Certificates using other encoding schemes such as DER, are not accepted. Uploading a new certificate replaces the default certificate you received with your CMC. CMC resets and becomes temporarily unavailable after the certificate has been uploaded successfully. To avoid disconnecting other users during a reset, notify authorized users who might log into CMC and check for active sessions in the Sessions page under the Network tab.
NOTE: Redirecting the CMC configuration to a file using getconfig -f is only supported with the remote RACADM interface. 3. Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database. 4. Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5. Reset the target CMC that was configured.
Indexes may be created and deleted. Over time the group may become fragmented with used and unused indexes. If an index is present, it is modified. If an index is not present, the first available index is used. This method allows flexibility when adding indexed entries where you do not need to make exact index matches between all the CMCs being managed. New users are added to the first available index. A .
Command Line Reference Guide . The following example displays a group name, object, and the object’s property value: [cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object name} {object value} • All parameters are specified as "object=value" pairs with no white space between the object, =, or value. White spaces that are included after the value are ignored. A white space inside a value string remains unmodified.
Example: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.10.110 cfgNicGateway=10.35.10.1 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.
Configuring Enhanced Cooling Mode for Fans The Enhanced Cooling Mode (ECM) feature provides additional cooling support using the third generation M1000e fans. The Enhanced Cooling Mode (ECM) for fans is available only when all nine fan slots are populated with the new third generation M1000e fans. The new third generation M1000e fans provide: • Superior cooling to the installed blades compared to previous M1000e fan generations, when the ECM feature is enabled.
• ECM is already enabled and the fan configuration is changed to Mixed Mode or all fans do not support ECM mode. In this case, the ECM mode can be disabled, but cannot be enabled again until all fans in the chassis support ECM. NOTE: The Enhanced Cooling Mode and the Apply options are grayed out if: • ECM mode is already disabled and fan configuration consists of unsupported fans along with supported fans. The information section displays a message listing the fans that are incompatible with ECM feature.
Configuring Server 7 You can do the following on 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.
The slot name setting does not extend to the optional iKVM. The slot name information is available through the iKVM FRU. The slot name setting in the CMC Web interface always overrides any change you make to the display name in the iDRAC interface. To edit a slot name 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.
Setting Description NOTE: This includes the root user password if the Set iDRAC Root Password on Server Insertion box is checked. By default, this option is disabled. Action When Server is Inserted Select one of the following options from the list: • • • • No Action — No action is performed when the server is inserted. QuickDeploy Only— Select this option to apply iDRAC network settings when a new server is inserted in the chassis.
Setting Description Mask, and QuickDeploy Gateway are disabled, and cannot be modified since DHCP is used to automatically assign these settings for each iDRAC. By default, this option is disabled. Reserved QuickDeploy IP Addresses Enables you to select the number of static IPv4 addresses reserved for the iDRACs in the chassis. The IPv4 addresses starting from Starting iDRAC IPv4 Address (Slot 1) are considered as reserved and assumed to be unused elsewhere in the same network.
Setting Description NOTE: The subnet mask and the gateway are not incremented like the IP address. For example, if the starting IP address is 192.168.0.250 and the subnet mask is 255.255.0.0 then the QuickDeploy IP address for slot 15 is 192.168.0.265.
NOTE: When there is a LAN or IPMI over LAN difference, the user is prompted to accept the QuickDeploy IP address setting. If the difference is the DHCP setting, the user is prompted to accept the DHCP QuickDeploy setting. To copy the QuickDeploy settings into the iDRAC Network Settings section, click Auto-Populate Using QuickDeploy Settings. The QuickDeploy network configurations settings are copied into the corresponding fields in the iDRAC Network Configuration Settings table.
For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals. Modifying iDRAC Network Settings for Individual Server iDRAC Using this table you can configure the iDRAC network configurations settings for each installed server. The initial values displayed for each of the fields are the current values read from the iDRAC. To modify the iDRAC Network Settings using the CMC Web interface: 1.
Configuring iDRAC VLAN Tag Settings Using Web Interface To configure VLAN for server using the CMC Web interface: 1. Go to any of the following pages: • In the system tree, go to Chassis Overview and click Network → VLAN. • 2. 3. In the system tree, go to Chassis Overview → Server Overview and click Network → VLAN. The VLAN Tag Settings page is displayed. In the iDRAC section, enable VLAN for the servers, set the priority and enter the ID.
The boot device that you specify must exist and contain bootable media. You can set the following devices for first boot. Table 16. : Boot Devices Boot Device Description PXE Boot from a Preboot Execution Environment (PXE) protocol on the network interface card. Hard Drive Boot from the hard drive on the server. Local CD/DVD Boot from a CD/DVD drive on the server. Virtual Floppy Boot from the virtual floppy drive.
Setting First Boot Device For Individual Server Using CMC Web Interface To set the first boot device for servers, you must have Server Administrator privileges or Chassis Configuration Administrator privileges and iDRAC login privileges. To set the first boot device for individual server using the CMC Web interface: 1. In the system go to Server Overview, and then click the server for which you want to set the first boot device. 2. Go to Setup → First Boot Device. The First Boot Device page is displayed.
Click Disconnect to disconnect a previously connected remote file share. Click Deploy to deploy the media device. NOTE: Save all working files before selecting the Deploy option to deploy the media device, because this action causes the server to be restarted. This action involves the following: • The remote file share is connected. • The file is selected as the first boot device for the servers. • The server is restarted. • Power is applied to the server if the server is turned off.
• Saving a profile from a server iDRAC with Lifecycle Controller 2 version 1.1 and later results in a All Settings profile. Saving a profile from a server with iDRAC version 3.2 and iDRAC with Lifecycle Controller 2 version 1.0 will result in a BIOS and Boot profile. You can: • View profile settings on a server or from a saved profile. • Save a profile from a server. • Apply a profile to other servers. • Import stored profiles from a management station or remote file share.
To add or save a profile: 1. Go to the Server Profiles page. In the Server Profiles section, select the server from whose settings you want to generate the profile, and then click Save Profile. The Save Profile section is displayed. 2. Select Extended Storage or Network Share as the location to save the profile. NOTE: The Network Share option is enabled and the details are displayed in the Stored Profiles section only if the network share is mounted and is accessible.
A warning message is displayed that applying a new server profile overwrites the current settings and also reboots the selected servers. You are prompted to confirm if you want to continue the operation. NOTE: To perform server configuration replication operations on servers, the CSIOR option must be enabled for the servers. If CSIOR option is disabled, a warning message is displayed that CSIOR is not enabled for the servers.
4. • If you select Local, a dialog box appears allowing you to save the profile to a local directory. • If you select Extended Storage or Network Share, a Save Profile dialog box is displayed. Click Save Profile to save the profile to the selected location. Editing Profile You can edit the name and description of a server profile that is stored on the CMC nonvolatile media (SD Card) or the name of a server profile stored on the remote share. To edit a stored profile: 1.
Viewing Stored Profile Settings To view profile settings of server profiles stored on the CMC nonvolatile media (SD Card) or on a network share, go to the Server Profiles page. In the Stored Profiles section, click View in the View Profile column for the required profile. The View Settings page is displayed. For more information on the displayed settings, see the CMC Online Help. Viewing Profile Log To view the profile log, in the Server Profiles page, see the Recent Profile Log section.
NOTE: You can perform the Quick Deploy action only if the Action When Server is Inserted option in the Deploy iDRAC page is set to Server Profile or Quick Deploy and Server Profile. Selecting one of these options allows to apply the server profile assigned when a new server is inserted in the chassis. 2. From the drop-down menu, select the profile to assign to the required slot. You can select a profile to apply to multiple slots. 3. Click Assign Profile.
NOTE: The term "the same account" in this context means that the user has the same login name with a matching password for CMC and for iDRAC. The user who has the same login name without a matching password, is considered to have the same account. NOTE: Users may be prompted to log in to iDRAC (see the third Single Sign-on policy bullet above). NOTE: If the iDRAC network LAN is disabled (LAN Enabled = No), single sign-on is not available.
Launching Remote Console from Servers Status Page Launching Remote Console from Chassis Health Page To launch a remote console from the CMC Web interface, do any of the following: 1. In the system tree, go to Chassis Overview, and then click Properties → Health. The Chassis Health page is displayed. 2. Click on the specified server in the chassis graphic. 3. In the Quicklinks section, click the Launch Remote Console link to launch the remote console.
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.
Configuring Alert Destinations The management station uses Simple Network Management Protocol (SNMP) to receive data from CMC. 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.
Configuring SNMP Trap Alert Destinations Using RACADM To configure IP alert destination using RACADM: 1. Open a serial/Telnet/SSH text console to CMC and log in. NOTE: Only one filter mask may be set for both SNMP and email alerting. You can skip step 2 if you have already selected the filter mask. 2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 3.
4. Event Filter Mask Value Firmware Version Mismatch 0x400000 Chassis Power Threshold Error 0x1000000 SDCARD Absent 0x2000000 SDCARD Error 0x4000000 Chassis Group Error 0x8000000 Server Sleeve Absent 0x10000000 Fabric Mismatch 0x20000000 Enable traps alerts: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts.
You must configure the SMTP email server to accept relayed emails from the CMC IP address, a feature which is normally turned off in most mail servers due to security concerns. For instructions to do this in a secure manner, see the documentation that was provided with the SMTP server. NOTE: If your mail server is Microsoft Exchange Server 2007, make sure that iDRAC domain name is configured for the mail server to receive the email alerts from iDRAC. NOTE: Email alerts support both IPv4 and IPv6 addresses.
6. Specify the name of the person receiving the email alert: racadm config -g cfgEmailAlert -o cfgEmailAlertEmailName -i where is the name of the person or group receiving the email alert, and is the index value specified in step 4 and step 5. The email name can contain up to 32 alphanumeric characters, dashes, underscores, and periods. Spaces are not valid. 7. Setup the SMTP host: racadm config -g cfgRemoteHosts -o cfgRhostsSmtpServerIpAddr host.
9 Configuring User Accounts and Privileges 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 It is possible for a user to have other privileges without the CMC Login User privilege. This feature is useful when a user is temporarily not allowed to login. When that user’s CMC Login User privilege is restored, the user retains all the other privileges previously granted. Chassis Configuration Administrator User can add or change data that: • • • • Identifies the chassis, such as chassis name and chassis location.
Privilege Description Without the Server Administrator privilege, a user created on the chassis can only execute a command on a server when all of the following conditions are true: • The same user name exists on the server. • The same user name must have the same password on the server. • The user must have the privilege to execute the command.
Privilege Description Fabric C Administrator User can set and configure the Fabric C IOM, which resides in either slot C1 or slot C2 of the I/O slots. The CMC user groups provide a series of user groups that have pre-assigned user privileges. NOTE: If you select Administrator, Power User, or Guest User, and then add or remove a privilege from the pre-defined set, the CMC Group automatically changes to Custom. Table 19.
User Group Privileges Granted None No assigned permissions Table 20.
Configuring Local Users You can configure up to 16 local users in CMC with specific access permissions. Before you create a CMC local user, verify if any current users exist. You can set user names, passwords, and roles with the privileges for these users. The user names and passwords can be changed using any of the CMC secured interfaces (that is, Web interface, RACADM or WS-MAN).
If the cfgUserAdminUserName object has no value, that index number, which is indicated by the cfgUserAdminIndex object, is available for use. If a name is displayed after the "=", that index is taken by that user name. When you manually enable or disable a user with the racadm config subcommand, you must specify the index with the -i option. The "#" character in the command objects indicates that it is a read only object. Also, if you use the racadm config -f racadm.
racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminPrivilege 0x0 A null string of double quote characters ("") instructs CMC to remove the user configuration at the specified index and reset the user configuration to the original factory defaults. Enabling CMC User With Permissions To enable a user with specific administrative permissions (role-based authority): 1. Locate an available user index using the command syntax: racadm getconfig -g cfgUserAdmin -i 2.
In Active Directory, a standard group object is used as a role group. A user who has CMC access is a member of the role group. To give this user access to a specific CMC card, the role group name and its domain name need to be configured on the specific CMC card. The role and the privilege level is defined on each CMC card and not in the Active Directory. You can configure up to five role groups in each CMC. The following table shows the default role group privileges. Table 21.
Role Group Default Privilege Level Permissions Granted • • • • • • Bit Mask Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator 3 None CMC Login User 0x00000001 4 None No assigned permissions 0x00000000 5 None No assigned permissions 0x00000000 NOTE: The Bit Mask values are used only when setting Standard Schema with the RACADM.
6. Specify the group name, domain, and privileges for a role group. 7. Click Apply to save the role group settings and then click Go Back To Configuration page. 8. If you have enabled certificate validation, you must upload the domain forest root certificate authority-signed certificate to CMC. In the Manage Certificates section, type the file path of the certificate or browse to the certificate file. Click Upload to upload the file to CMC.
• If DHCP is enabled on CMC and you want to use the DNS address obtained automatically by the DHCP server, type the following command: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1 • If DHCP is disabled on CMC or you want manually to input your DNS IP address, type the following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSServer2
However, each association object can be linked (or, may link users, groups of users, or RAC device objects) to only one privilege object. This example allows an administrator to control each user’s privileges on specific CMCs. The RAC device object is the link to RAC firmware for querying Active Directory for authentication and authorization.
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.
To configure the objects for the multiple domain scenario: 1. Ensure that the domain forest function is in Native or Windows 2003 mode. 2. Create two Association Objects, A01 (of Universal scope) and A02, in any domain. 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.
To use the LDIF files, see the instructions in the readme included in the LDIF_Files directory. You can copy and run the Schema Extender or LDIF files from any location. 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.
Table 24. : delliDRACAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.7.1.2 Description Represents the Dell Association Object. The Association Object provides the connection between the users and the devices. Class Type Structural Class SuperClasses Group Attributes dellProductMembers dellPrivilegeMember Table 25. : dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines the privileges (Authorization Rights) for CMC device.
Table 27. : dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description The main class from which all Dell products are derived. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 28. : List of Attributes Added to the Active Directory Schema Assigned OID/Syntax Object Identifier Single Valued Attribute: dellPrivilegeMember FALSE Description: List of dellPrivilege objects that belong to this attribute. OID: 1.2.840.113556.1.8000.1280.1.1.2.
Assigned OID/Syntax Object Identifier Single Valued Description: TRUE if the user has User Configuration Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.5 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: delIsLogClearAdmin TRUE Description: TRUE if the user has Clear Logs Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.6 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
Assigned OID/Syntax Object Identifier Single Valued Attribute: dellRacType TRUE Description: This attribute is the Current Rac Type for the dellRacDevice object and the backward link to the dellAssociationObjectMembers forward link. OID: 1.2.840.113556.1.8000.1280.1.1.2.13 Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.905) Attribute: dellAssociationMembers FALSE Description: List of dellAssociationObjectMembers that belong to this Product.
• Create a RAC device Object • Create a Privilege Object • Create an Association Object • Add objects to an Association Object 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. 3. Enter a name for the new object.
Adding Objects to Association Object Using the Association Object Properties window, you can associate users or user groups, privilege objects, and RAC devices or RAC device groups. If your system is running on Microsoft Windows 2000 mode or higher, use Universal Groups to span domains with your user or RAC objects. You can add groups of Users and RAC devices. The procedure for creating Dell-related groups and nonDell-related groups is identical.
• Enable Active Directory, provide the root domain name, and the timeout value. • 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. NOTE: Setting the IP address as 0.0.0.0 disables CMC from searching for a server. NOTE: You can specify a list of domain controller or global catalog servers separated by commas.
Configuring Active Directory With Extended Schema Using RACADM To configure the CMC Active Directory with Extended Schema using the RACADM: 1.
• If DHCP is enabled on CMC and you want to use the DNS address obtained automatically by the DHCP server, type the following command: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1 • If DHCP is disabled on CMC, or if DHCP is enabled but you want to specify your DNS IP address manually, type following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSSe
Figure 2. Configuration of CMC with Generic LDAP Configuring the Generic LDAP Directory to Access CMC The CMC's Generic LDAP implementation uses two phases in granting access to a user—user authentication and then user authorization. Authentication of LDAP Users Some directory servers require a bind before any searches can be performed against a specific LDAP server. To authenticate a user: 1. Optionally bind to the Directory Service. The default is an anonymous bind. 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. 3. Specify the following: The settings to be configured for standard schema is displayed on the same page. 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.
NOTE: It is highly recommended to use the racadm testfeature -f LDAP command to test the LDAP settings for first time setups. This feature supports both IPv4 and IPv6. The required property changes include enabling LDAP logins, setting the server FQDN or IP, and configuring the base DN of the LDAP server. • $ racadm config -g cfgLDAP -o cfgLDAPEnable 1 • $ racadm config -g cfgLDAP -o cfgLDAPServer 192.168.0.
10 Configuring CMC For Single Sign-On Or Smart Card Login 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.
NOTE: If you are using Active Directory on Windows 2003, make sure that you have the latest service packs and patches installed on the client system. If you are using Active Directory on Windows 2008, make sure that you have installed SP1 along with the following hot fixes: Windows6.0-KB951191-x86.msu for the KTPASS utility. Without this patch the utility generates bad keytab files. Windows6.0-KB957072-x86.msu for using GSS_API and SSL transactions during an LDAP bind.
Before generating a keytab file, you must create an Active Directory user account for use with the mapuser option of the ktpass command. You must use the same name as the CMC DNS name, to which you upload the generated keytab file. To generate a keytab file using the ktpass tool: 1. Run the ktpass utility on the domain controller (Active Directory server) where you want to map CMC to a user account in Active Directory. 2.
Mozilla Firefox 1. In Firefox, type about:config in the address bar. NOTE: If the browser displays the This might void your warranty warning, click I'll be careful. I promise. 2. In the Filter text box, type negotiate. The browser displays a list of preference names limited to those containing the word negotiate. 3. From the list, double-click network.negotiate-auth.trusted-uris. 4. In the Enter string value dialog box, type the CMC's domain name and click OK.
again. For more information, see RACADM Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide on dell.com/support/manuals. Uploading the Keytab File The Kerberos keytab file serves as the CMC's user name and password credentials to the Kerberos Data Center (KDC), which in turns allows access to the Active Directory. Each CMC in the Kerberos realm must be registered with the Active Directory and must have a unique keytab file.
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 Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
Command Description exit, logout, and quit All the commands perform the same action. They end the current session and return to a login prompt. Using Telnet Console With CMC You can have up to four Telnet sessions with CMC at a time. 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.
Supported SSH Cryptography Schemes To communicate with CMC using SSH protocol, it supports multiple cryptography schemes listed in the following table. Table 30.
Date/Time SSH 09:00:00 SSH 09:00:00 PC1 x.x.x.x 06/16/2009 PC2 x.x.x.x 06/16/2009 For more information on the sshpkauth, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
where, –t must be dsa or rsa. –b specifies the bit encryption size between 768 and 4096. –c allows modifying the public key comment and is optional. The is optional. After the command completes, use the public file to pass to the RACADM for uploading the file. RACADM Syntax Notes for CMC When using the racadm sshpkauth command, ensure the following: • For the –i option, the parameter must be svcacct. All other parameters for -i fail in CMC.
Configuring Terminal Emulation Software The CMC supports a serial text console from a management station running one of the following types of terminal emulation software: • Linux Minicom. • Hilgraeve’s HyperTerminal Private Edition (version 6.3). Perform the steps in the following subsections to configure the required type of terminal software. Configuring Linux Minicom Minicom is a serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0.
Table 31. : Minicom Settings Setting Description Required Setting Bps/Par/Bits 115200 8N1 Hardware flow control Yes Software flow control No Terminal emulation ANSI Modem dialing and parameter settings Clear the init, reset, connect, and hangup settings so that they are blank Connecting to Servers or I/O Modules Using Connect Command CMC can establish a connection to redirect the serial console of server or I/O modules.
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.
• On without console redirection • On with console redirection via COM1 Use the arrow keys to navigate between these options. 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.
root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600 initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 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.
ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it.
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 If a server is replaced, the FlexAddress for the slot remains the same for the given server slot.
For example: (starting_mac)00188BFFDCFA + (mac_count)0xCF - 1 = (ending_mac)00188BFFDDC8 NOTE: Lock the SD card prior to inserting in the USB Memory Card Reader to prevent accidently modifying any of the contents. You must unlock the SD card before inserting into CMC. About FlexAddress Plus The FlexAddress Plus is a new feature added to the feature card version 2.0. It is an upgrade from FlexAddress feature card version 1.0. FlexAddress Plus contains more MAC addresses than the FlexAddress feature.
Activating FlexAddress FlexAddress is delivered on a Secure Digital (SD) card that must be inserted into CMC to activate the feature. To activate the FlexAddress feature, software updates may be required; if you are not activating FlexAddress these updates are not required. The updates (listed in the following table) include server module BIOS, I/O mezzanine BIOS or firmware, and CMC firmware. You must apply these updates before you enable FlexAddress.
NOTE: If CMC firmware that supports FlexAddress (version 1.10 or later) is not installed, the feature is not activated. See the Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification document for SD card installation instructions. NOTE: The SD card contains a FlexAddress feature. Data contained on the SD card is encrypted and may not be duplicated or altered in any way as it may inhibit system function and cause the system to malfunction.
Status Message Actions that the CMC with the SD feature card installed is the active CMC and not the standby CMC. The feature card inserted is valid and contains the following feature(s) FlexAddress: The feature card is bound to this chassis. No action required. The feature card inserted is valid and contains the Remove the SD card; locate and install the SD card following feature(s) FlexAddress: The feature card for the current chassis.
To deactivate the FlexAddress feature and restore the SD card: racadm feature -d -c flexaddress The command returns the following status message if it is successfully deactivated: feature FlexAddress is deactivated on the chassis successfully.
Wake-On-LAN with FlexAddress When the FlexAddress feature is deployed for the first time on a given server module, it requires a powerdown and power-up sequence for FlexAddress to take effect. FlexAddress on Ethernet devices is programmed by the server module BIOS. For the server module BIOS to program the address, it needs to be operational which requires the server module to be powered up.
For more information on setflexaddr command, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. at dell.com/support/manuals. Configuring FlexAddress for Server-Level Slots At the server level, you can enable or disable the FlexAddress feature for individual slots. Configuring FlexAddress for Server-Level Slots Using CMC Web Interface To enable or disable an individual slot to use the FlexAddress feature using the CMC Web interface: 1.
• Fabric Configuration NOTE: – Fabric A displays the type of the Input/Output fabric installed. If Fabric A is enabled, unpopulated slots display chassis-assigned MAC addresses for Fabric A. – iDRAC management controller is not a fabric, but its FlexAddress is considered as a fabric. – A check mark against the component indicates that the fabric is enabled for FlexAddress or FlexAddressPlus. • Protocol that is being used on the NIC Adapter port. For example, LAN, iSCSI, FCoE, and so on.
Viewing Basic WWN/MAC Address Information Using Web Interface To view WWN/MAC Address information for each server slot or all servers in a chassis, in the basic mode: 1. Click Server Overview → Properties → WWN/MAC. The WWN/MAC Summary page displays the WWN/MAC Address Information. Alternatively, click Server Overview → Slot → Setup → FlexAddress to view the WWN/MAC Address information for a specific server slot. The FlexAddress page is displayed. 2.
4. Click the against a slot or click Expand/Collapse All to expand or collapse the attributes listed for a specific slot or all the slots in the WWN/MAC Addresses table. 5. From the Server Slot drop-down menu, select All Servers or a specific Slot to view the WWN/MAC Addresses attributes for all servers or servers in specific slots only respectively. 6.
To display the console assigned MAC/WWN of all LOMs or mezzanine cards, use the following RACADM command: racadm getmacaddress -c all To display the chassis assigned WWN/MAC address, use the following RACADM command: racadm getmacaddress -c flexaddress To display the MAC/WWN addresses for all LOMs or mezzanine cards, use the following RACADM command: racadm getmacaddress -c factory To display the Ethernet and iSCSI MAC/WWN addresses for all iDRAC/LOMs/mezzanine cards, use the following RACADM command: racad
Command Messages The following table lists the RACADM commands and output for common FlexAddress situations. Table 34. FlexAddress Commands and Output Situation Command Output SD card in the active CMC module is bound to another service tag.
Situation Command $racadm setflexaddr -i 1 Changing the slot/fabric 1 FlexAddress settings while the server modules are powered ON. Output ERROR: Unable to perform the set operation because it affects a powered ON server FlexAddress DELL SOFTWARE LICENSE AGREEMENT This is a legal agreement between you, the user, and Dell Products L.P. or Dell Global B.V. ("Dell").
transferable. Any implied warranties are limited to ninety (90) days from the date you receive the Software. Some jurisdictions do not allow limits on the duration of an implied warranty, so this limitation may not apply to you. The entire liability of Dell and its suppliers, and your exclusive remedy, shall be (a) return of the price paid for the Software or (b) replacement of any disk not meeting this warranty that is sent with a return authorization number to Dell, at your cost and risk.
GENERAL This license is effective until terminated. It terminates upon the conditions set forth above or if you fail to comply with any of its terms. Upon termination, you agree that the Software and accompanying materials, and all copies thereof, is destroyed. This agreement is governed by the laws of the State of Texas. Each provision of this agreement is severable.
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.
Invalid hardware configurations can cause electric or functional problems to the chassis or its components. Fabric management prevents invalid configurations from powering on. 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.
• A Fibre Channel pass-through IOM and a fibre channel switch IOM in slots B1 and B2 is a valid configuration if the first MCs on all of the servers are also fibre channel. In this case, CMC powers-on the IOMs and the servers. However, certain fibre channel redundancy software may not support this configuration; not all valid configurations are necessarily supported configurations. Fabric verification for server IOMs and MCs is performed only when the chassis is powered on.
Viewing I/O Module Uplink and Downlink Status Using Web Interface You can view the Dell PowerEdge M I/O Aggregator 's uplink and downlink status information using the CMC Web interface: 1. Go to Chassis Overview and expand I/O Module Overview in the system tree. All the IOMs (1–6) appear in the expanded list. 2. Click the IOM (slot) you want to view. The I/O Module Status page specific to the IOM slot is displayed. The I/O Module Uplink Status and I/O Module Downlink Status tables are displayed.
The racadm getioinfo command with the -s option enables you to view the I/O Aggregator related stacking information for the switches present in the chassis and their stacked units in both the local chassis and external chassis.
4. Click Apply. The network settings are configured for the IOM(s). NOTE: For IOMs that are manageable, you can reset the VLANs, network properties, and IO ports to default configurations. Configuring Network Settings for IOMs Using RACADM To configure the network settings for IOMs using RACADM, set the date and time. See the deploy command section in the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
To update the IOM Infrastructure device software, in the CMC Web interface: 1. Go to Chassis Overview → I/O Module Overview → Update. The IOM Firmware Update page is displayed. Alternatively, go to any of the following: • Chassis Overview → Update • Chassis Overview → Chassis Controller → Update • Chassis Overview → iKVM → Update The Firmware Update page is displayed, which provides a link to access the IOM Firmware Update page. 2.
Configuring Management VLAN on IOMs Using Web Interface You can manage the IO Aggregator in-band through a VLAN. This VLAN must be deployed prior to use. CMC allows in-band management VLAN deployment. The switch’s in-band management VLAN requires the following basic configuration of settings to be applied: • Enable • VLAN ID • Priority NOTE: Configuring the management VLAN on the Vlan Settings page requires Chassis Configuration privileges.
Configuring VLAN settings on IOMs Using CMC Web Interface NOTE: You can configure VLAN settings only on PowerEdge M I/O Aggregator IOM. Other IOMs including MXL 10/40GbE are not supported. To configure 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 displays the IOM(s) that are turned on and the available ports. 2.
Viewing the Current VLAN Settings on IOMs Using CMC Web Interface To view the current VLAN settings on IOMs 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 Edit VLANs section, select Show VLANs in the drop down list and click Apply. An Operation Successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field.
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. Select the Select/Deselect All option to apply the changes to all or no IOMs. or Select the check box against the specific slots to select the required IOMs. 5. In the Step 3: Edit VLANs section, select Update the Untagged VLANs in the drop down list and click Apply.
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, hot-pluggable module to the chassis that provides local keyboard, mouse, and video access to the servers in the chassis, and to the active CMC’s command line.
Managing iKVM From CMC Updating iKVM Firmware 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.
Configuring OSCAR Launching OSCAR To launch OSCAR: 1. Press . The Main dialog box is displayed. 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.
Key or Key Sequence Result , + <0> Immediately disconnects a user from a server; no server is selected. Status flag displays Free. (This action only applies to the =<0> on the keyboard and not the keypad.) Immediately turns on screen saver mode and prevents access to that specific console, if it is password protected. Up/Down Arrow keys Moves the cursor from line to line in lists.
Changing Display Behavior Use the Menu dialog box to change the display order of servers and set a screen delay time for OSCAR. To change the display behavior: 1. Press to launch OSCAR. The Main dialog box is displayed. 2. Click Setup and then Menu. The Menu dialog box is displayed. 3. To choose the default display order of servers, do one of the following: • 4. Select Name to display servers alphabetically based on the name.
The Flag dialog box appears. 3. Select Displayed to always display the flag or Displayed and Timed to display the flag for only five seconds after switching. NOTE: If you select Timed by itself, the flag is not displayed. 4. In the Display Color section, select a flag color. Options are black, red, blue, and purple. 5. In Display Mode, select Opaque for a solid color flag or Transparent to see the desktop through the flag. 6. To position the status flag on the desktop, click Set Position.
chassis slot number the server occupies. The Slot column indicates the slot number in which a server is installed. NOTE: The Dell CMC command line occupies Slot 17. Selecting this slot displays the CMC command line, where you can execute RACADM commands or connect to the serial console of server or I/O modules. NOTE: Server names and slot numbers are assigned by CMC.
Soft Switching Soft switching is switching between servers using a hotkey sequence. Press to soft switch to a server and then type the first few characters of its name or number. If you have previously set a delay time (the number of seconds before the Main dialog box is displayed after is pressed) and if you press the key sequences before that time has elapsed, the OSCAR interface does not display.
Preemption Warning Normally, a user connected to a server console through the iKVM and another user connected to the same server console through the iDRAC Web interface console redirection feature both have access to the console and are able to type simultaneously. To prevent this scenario, before starting the iDRAC Web interface console redirection, the remote user can disable the local console in the iDRAC Web interface.
Setting Password To set the password: 1. Single-click and press or double-click in the New field. 2. Type the new password and press . Passwords are case sensitive and require 5–12 characters. They must include at least one letter and one number. Legal characters are: A–Z, a–z, 0–9, space, and hyphen. 3. In the Repeat field, type the password again, and press . 4. Click OK and close the dialog box. Password-protecting the Console To password-protect the console: 1.
Enabling Screen Saver Mode With No Password Protection NOTE: If your console is password-protected, you must first remove password protection. Remove the password before enabling screen saver mode with no password protection. To enable Screen Saver mode without password protection: 1. Select Enable Screen Saver. 2. Type the number of minutes (1 through 99) that you want to delay activation of the screen saver. 3. Select Energy if your monitor is ENERGY STAR compliant, if not select Screen.
The Main dialog box appears. 2. Click Setup and then Language. The Language dialog box appears. 3. Select the required language and click OK. Displaying Version Information Use the Version dialog box to display the iKVM firmware and hardware versions, and to identify the language and keyboard configuration. To display version information: 1. Press . The Main dialog box is displayed. 2. Click Commands and then Display Versions. The Version dialog box is displayed.
2. • Select the server to be removed. • Double-click the server name or slot. • Click Clear to remove all servers from the Scan list. Click Add/Remove, and then click OK. Starting the Scan Mode To start the scan mode: 1. Press . The Main dialog box is displayed. 2. Click Commands. The Command dialog box is displayed. 3. Select the Scan Enable option. 4. Click OK. A message is displayed indicating that the mouse and keyboard have been reset. 5. Click to close the message box.
The Main dialog box is displayed. 2. Click Setup and then Broadcast. The Broadcast dialog box is displayed. 3. Enable mouse and/or keyboard for the servers that are to receive the broadcast commands by selecting the boxes. or Press the up or down arrow keys to move the cursor to a target server. Then, press to select the keyboard box and/or
3. Click Apply to save the setting. Enabling or Disabling Access to iKVM From Front Panel Using RACADM To enable or disable access to the iKVM from the front panel using RACADM, open a serial/Telnet/SSH text console to CMC, log in, and type: racadm config -g cfgKVMInfo -o cfgKVMFrontPanelEnable where is 1 (enable) or 0 (disable). For more information about the config subcommand, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
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.
Dynamic Power Supply Engagement Default Redundancy Configuration Power Budgeting For Hardware Modules Viewing Power Consumption Status Viewing Power Budget Status Redundancy Status and Overall Power Health Configuring Power Budget and Redundancy Executing Power Control Operations Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis.
Figure 5. PSUs per grid and a power failure on grid 1 In the event of a single PSU failure in this configuration, the remaining PSUs in the failing grid are marked as Online. In this state, the PSUs in the Redundant Grid if not in failed state, help in functioning of the system without interruption. If a PSU fails, the chassis health is marked non-critical.
status of the chassis always indicates no redundancy. The figure below illustrates no redundancy mode is the factory default setting for three PSU configuration. CMC does not require the PSU units to be present in any specific PSU slot positions when No Redundancy is configured. NOTE: All PSUs in the chassis are Online if DPSE is disabled when in No Redundancy mode.
six 2700W AC PSU configuration, the additional power available in standard fan configurations mode, is 1023W. The EPP additional power available is 2700W, which can be used to increase server performance only.
• Enables delivery of the total power allocation of the chassis through fewer PSUs. • Increases the efficiency of the online PSUs as they run at higher utilization. • Improves the efficiency and durability of the standby PSUs. To operate remaining PSUs at their maximum efficiency: • No Redundancy mode with DPSE is highly power efficient, with optimal PSUs online. PSUs that are not needed are placed in standby mode. • PSU Redundancy mode with DPSE also provides power efficiency.
Table 37. Default Redundancy Configuration PSU Configuration Default Redundancy Policy Default Dynamic PSU Engagement Setting Six PSUs Grid Redundancy Disabled Three PSUs No Redundancy Disabled Grid Redundancy In Grid Redundancy mode with six PSUs, all six PSUs are active. The three PSUs on the left must connect to one input power grid, while the three PSUs on the right connect to another power grid.
Figure 8. Chassis With Six-PSU Configuration CMC maintains a power budget for the enclosure that reserves the necessary wattage for all installed servers and components. CMC allocates power to the CMC infrastructure and the servers in the chassis. CMC infrastructure consists of components in the chassis, such as fans, I/O modules, and iKVM (if present). The chassis may have up to 16 servers that communicate to the chassis through the iDRAC. For more information, see the iDRAC User’s Guide at support.dell.
Infrastructure. Following Chassis Infrastructure, the servers in an enclosure are powered up. Any attempt to set a System Input Power Cap less than the actual consumption fails. If necessary for the total power budget to stay below the value of the System Input Power Cap, CMC allocates servers a value less than their maximum requested power.
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. Assigning Priority Levels to Servers Server priority levels determine which servers the CMC draws power from when additional power is required. NOTE: The priority you assign to a server is linked to the slot and not to the server itself.
Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getpminfo 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.
PSU Removals With Degraded or No Redundancy Policy CMC may begin conserving power when you remove a PSU or a PSU AC cable. CMC decreases power to the lower priority servers until power allocation is supported by the remaining PSUs in the chassis. If you remove more than one PSU, CMC evaluates power needs again when the second PSU is removed to determine the firmware response. If power requirements are still not met, CMC may turn off the lower priority servers.
If the subsequent power capacity or the user power capacity is greater than the server allocations, servers have degraded performance or, in a worse case, servers may be powered down. Both conditions are in reverse-priority order, that is, the lower priority servers are powered down first. The following table provides the firmware response to a PSU power down or removal as it applies to various PSU redundancy configurations. Table 39.
Input over-current An over current fault detected on power supply . Input under-current An undercurrent fault detected on power supply . DC output under-voltage An output under voltage fault detected on power supply DC output over-current An output over current fault detected on power supply . DC output under-current An output under current fault detected on power supply . Communication failure Cannot communicate with power supply .
You can configure the following: • System Input Power Cap • Redundancy Policy • Extended Power Performance • Server Performance Over Power Redundancy • Dynamic Power Supply Engagement • Disable Chassis Power Button • Allow 110 VAC Operation • Max Power Conservation Mode • Remote Power Logging • Remote Power Logging Interval • Server Based Power Management Related Links Power Conservation and Power Budget Maximum Power Conservation Mode Server Power Reduction to Maintain Power Budget 11
In maximum power conservation mode, all servers start functioning at their minimum power levels, and all subsequent server power allocation requests are denied. In this mode, the performance of powered on servers may be degraded. Additional servers cannot be powered on, regardless of server priority. The system is restored to full performance when the maximum conservation mode is cleared.
Remote Logging Power consumption can be reported to a remote syslog server. Total chassis power consumption, minimum, maximum, and average power consumption over a collection period can be logged. For more information on enabling this feature and configuring the collection and logging interval, see the Executing Power Control Operations section. External Power Management CMC Power management is optionally controlled by the Dell OpenManage Power Center.
Configuring Power Budget and Redundancy Using CMC Web Interface NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. To configure power budget using the Web interface: 1. In the system tree, go to Chassis Overview, and then click Power → Configuration The Budget/Redundancy Configuration page is displayed. 2. Select any or all of the following properties as required. For information about each of the fields, see CMC Online Help. • 3.
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.
For information about RACADM commands for chassis power, see the config, getconfig, getpbinfo, and cfgChassisPower sections in the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. 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.
NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. 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.
where specifies the server by its slot number (server-1 through server-16) in the chassis, and is the operation you want to execute: powerup, powerdown, powercycle, graceshutdown, or hardreset. Executing Power Control Operations on an IOM You can remotely execute a reset or power cycle on an individual IOM. NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege.
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.
Racdump includes the following subsystems and aggregates the following RACADM commands. For more information on racdump, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
Power Troubleshooting The following information helps you to troubleshoot power supply and power-related issues: • Problem: Configured the Power Redundancy Policy to Grid Redundancy, and a Power Supply Redundancy Lost event was raised. – Resolution A: This configuration requires at least one power supply in side 1 (the left three slots) and one power supply in side 2 (the right three slots) to be present and functional in the modular enclosure.
– Resolution: The enclosure has 2000 W of surplus power available in the current configuration, and the System Input Power Cap can be safely reduced by this amount being reported without impacting server performance. • Problem: A subset of servers lost power after an AC Grid failure, even when the chassis was operating in the Grid Redundancy configuration with six power supplies.
Examples of hardware log entries critical System Software event: redundancy lost Wed May 09 15:26:28 2007 normal System Software event: log cleared was asserted Wed May 09 16:06:00 2007 warning System Software event: predictive failure was asserted Wed May 09 15:26:31 2007 critical System Software event: log full was asserted Wed May 09 15:47:23 2007 unknown System Software event: unknown event Related Links Viewing Event Logs Viewing Hardware Logs Using CMC Web Interface You can view, save, and clear the
Viewing CMC Logs Using the Web Interface You can view, save, and clear the CMC log. You can sort the log entries based on Source, Date/Time, or Description by clicking the column heading. Subsequent clicks on the column headings reverse the sort. To view the CMC log using the CMC Web interface, in the system tree, go to Chassis Overview and click Logs → CMC Log. The CMC Log page is displayed.
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.
NOTE: The default backup file name contains the Chassis' service tag. This backup file can be used later, to restore the settings and certificates for this chassis only. To restore the chassis configuration, click Choose File, specify the backup file, and click Restore. NOTE: • CMC does not reset upon restoring configuration, however CMC services may take some time to effectively impose any changed or new configuration. After successful completion, all current sessions are closed.
To disable NTP, type: racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 0 To enable NTP, type: racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 1 If the NTP servers are configured correctly and this entry is present in the trace log, then this confirms that CMC is not able to synchronize with any of the configured NTP servers.
Component Server IOM (Common) IOM (Pass through) Fan LED Color, Blinking Pattern Status Amber, glowing steadily Not used Amber, blinking Fault Amber, dark No fault Green, glowing steadily Powered on Green, blinking Firmware is being uploaded Green, dark Powered off Blue, glowing steadily Normal Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault Green, glowing steadily Powered on Green, blinking Firmware is
Component PSU LED Color, Blinking Pattern Status Amber, dark Not used (Oval) Green, glowing steadily AC OK (Oval) Green, blinking Not used (Oval) Green, dark AC Not OK Amber, glowing steadily Not used Amber, blinking Fault Amber, dark No fault (Circle) Green, glowing steadily DC OK (Circle) Green, dark DC Not OK Troubleshooting Non-responsive CMC If you cannot log in to CMC using any of the interfaces (the Web interface, Telnet, SSH, remote RACADM, or serial), you can verify the CMC fu
To obtain recovery information: 1. Install a NULL modem cable between the CMC and a client machine. 2. Open a terminal emulator of your choice (such as HyperTerminal or Minicom). Set up 8 bits, no parity, no flow control, and baud rate 115200. A core memory failure displays an error message every 5 seconds. 3. Press . If a recovery prompt appears, additional information is available. The prompt indicates the CMC slot number and failure type.
• DDNS — Traces dynamic DNS update requests and responses. • Configuration changes to the network interfaces. The trace log may also contain CMC firmware-specific error codes that are related to the internal CMC firmware, not the managed system’s operating system. Resetting Administrator Password CAUTION: Many repairs may only be done by a certified service technician.
cfgSerialConsoleCommand="" cfgSerialConsoleColumns=0 1. Press the CMC release latch on the handle and move the handle away from the module front panel. Slide the CMC module out of the enclosure. NOTE: Electrostatic discharge (ESD) events can damage CMC. Under certain conditions, ESD may build up on your body or an object, and then discharge into your CMC. To prevent ESD damage, you must take precautions to discharge static electricity from your body while handling and accessing CMC outside the Chassis. 2.
5. Log into the active CMC using the default administrator username:root and password: calvin, and restore any necessary user account settings. The existing accounts and passwords are not disabled and are still active. 6. Perform the required management actions, including creating a new administrator password. 7. Remove the 2-pin PASSWORD_RST jumper and replace the jumper plug. a. Press in the CMC release latch on the handle and move the handle away from the module front panel.
Using LCD Panel Interface 17 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.
LCD Navigation The right side of the LCD panel contains five buttons: four arrow buttons (up, down, left, and right) and a center button. • To move between screens, use the right (next) and left (previous) arrow buttons. At any time while using the panel, you can return to a previous screen. • To scroll through options on a screen, use the down and up arrow buttons. • To select and save an item on a screen and move to the next screen, use the center button.
NOTE: There is a blinking blue rectangle around this icon when Component Identify is enabled. A status indicator LED on the LCD panel provides an indication of the overall health of the chassis and its components. • Solid blue indicates good health. • Blinking amber indicates that at least one component has a fault condition. • Blinking blue is an ID signal, used to identify one chassis in a group of chassis.
Language Setup Screen The Language Setup screen allows you to select the language used for LCD panel messages. The currently active language is highlighted with a light blue background. 1. Use the up, down, left, and right arrow buttons to highlight the desired language. 2. Press the center button. The Accept icon appears and is highlighted. 3. Press the center button to confirm the change. The LCD Setup menu is displayed.
Graphical Module Status Screen The Graphical Module Status screen displays all modules installed in the rear of the chassis and provides summary health information for each module.
Highlight the Back icon and press the center button to return to the Enclosure Status screen. IP Summary Screen The IP Summary screen shows IP information for CMC and iDRAC of each installed server. Use the up and down arrow buttons to scroll through the list. Use the left and right arrow buttons to scroll selected messages that are longer than the screen. Use the up and down arrow buttons to select the Back icon and press the center button to return to the Enclosure menu.
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 Loss of communication from CMC to the LCD front panel. Responding and LED is blinking amber. Check that CMC is booting; then, reset CMC using GUI or RACADM commands.
faulty; or the LCD module is faulty. • • The LCD module cable is not connected, or is improperly connected. 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.
Table 47. Enclosure/Chassis Status Screen Severity Message Cause Critical Fan is removed. This fan is required for proper cooling of the enclosure/chassis. Warning Power supply redundancy is degraded. One or more PSU have failed or removed and the system can no longer support full PSU redundancy. Critical Power supply redundancy is lost. One or more PSU have failed or removed and the system is no longer redundant. Critical The power supplies are not redundant.
Severity Message Cause Critical A failure is detected on I/O module . The I/O module has a fault. The same error can also happen if the I/O module is thermaltripped. Table 50. iKVM Status Screen Severity Message Cause Warning Console is not available for Local KVM. Minor failure, such as corrupted firmware. Critical Local KVM can not detect any hosts. USB host enumeration failure. Critical OSCAR, on screen display is not functional for the Local KVM. OSCAR failure.
Severity Message Cause Warning The storage battery is low. ROMB battery is low. Critical The storage battery failed. CMOS battery is not present or has no voltage. Critical The CPU voltage is outside of the allowable range. Critical The system board voltage is outside of the allowable range. Critical The mezzanine card voltage is outside of the allowable range.
Severity Message Cause no response was received from Host) and the action is set to power off. Critical The watchdog timer power cycled the system. The iDRAC watchdog detected that the system has crashed (timer expired because no response was received from Host) and the action is set to power cycle. Critical Log is full. The SEL device detects that only one entry can be added to the SEL before it is full.
Severity Message Cause NonRecoverable CPU machine check detected. The processor machine check entered a non-recoverable state. Critical Memory redundancy is lost. Critical A bus fatal error was detected on a component at bus device function . Fatal error is detected on the PCIe bus. Critical A software NMI was detected on a component at bus device function . Chip error is detected.
IP6 Global Address:
Only displays if IPv6 is enabled only on an active CMC. MAC: Displays the CMC's MAC address. Table 54. Chassis or Enclosure Status Item Description User Define Name Example: “Dell Rack System”. You can set this option through the CMC Command Line Interface (CLI) or Web interface. 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.Table 57. IOM Status Item Description Name/Location Example: IOM A1, IOM B1. 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. For more information see LCD Error Messages. Status Off or On. Model Model of the IOM. Fabric Type Networking type. IP address Only shows if IOM is On. This value is zero for a pass through type IOM.
NOTE: You can set this table through the CMC CLI or Web interface. Name Name of the server, which the user can set through Dell OpenManage. The name is displayed only if iDRAC has finished booting, and the server supports this feature, else iDRAC booting messages are displayed. Model Number Displays if iDRAC finished booting. Service Tag Displays if iDRAC finished booting. BIOS Version Server BIOS firmware version. Last POST Code Displays the last server BIOS POST code messages string.
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.
Managing and Recovering a Remote System While accessing the CMC Web interface, a security warning stating that the host name of the SSL certificate does not match the host name of CMC is displayed. CMC includes a default CMC server certificate to ensure network security for the Web interface and remote RACADM features.
Why is the following message displayed for unknown reasons? Remote Access: SNMP Authentication Failure As part of discovery, IT Assistant attempts to verify the device’s get and set community names. In IT Assistant, the get community name = public and the set community name = private. By default, the community name for the CMC agent is public. When IT Assistant sends out a set request, the CMC agent generates the SNMP authentication error because it only accepts requests from community = public.
Yes. All SSL certificates for Active Directory servers in the forest must be signed by the same root certificate authority-signed certificate, because CMC only allows upload of one trusted certificate authority-signed SSL certificate. The Web interface does not launch after a new RAC certificate is created and uploaded. If Microsoft Certificate Services is used to generate the RAC certificate, the User Certificate option may have been used instead of Web Certificate when creating the certificate.
This feature card was activated with a different chassis. It must be removed before accessing the FlexAddress feature. Current Chassis Service Tag = XXXXXXXX Feature Card Chassis Service Tag = YYYYYYYY The original feature card is no longer eligible for deactivation on that or any other chassis, unless Dell Service re-programs the original chassis service tag back into a chassis, and CMC that has the original feature card is made active on that chassis.
• Remove the standby CMC and insert the new CMC in its place. • From the Active CMC, upgrade the standby CMC firmware to 1.10 or later. 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.
Only one connection is allowed at a time. The front panel connection has precedence over ACI and the rear panel. For more information about connection precedence, see iKVM Connection Precedences. The message "User has been disabled as another appliance is currently tiered" appears on the monitor connected to the rear panel. Why? A network cable is connected to the iKVM ACI port connector and to a secondary KVM appliance. Only one connection is allowed at a time.
Initially, wait for 60 seconds. If the server is still initializing, the slot name appears as soon as initialization is complete, and the server can be selected. If, after 60 seconds, OSCAR still indicates that the slot is initializing, remove and then re-insert the server in the chassis. This action allows iDRAC to reinitialize. IOM After a configuration change, sometimes CMC displays the IP address as 0.0.0.0. Click the Refresh icon to see if the IP address is set correctly on the switch.
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.
Backup the CMC Configurations and Server Configurations. 1. To back up Chassis configuration, see Saving or Restoring Chassis Configuration section. 2. To save the configurations of a server, use the Server Cloning feature of CMC. For information, see the Configuring Profile Settings Using Server Clone. 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.
• • Changing the System Input Power Cap value to less than or equal to 13300 W, displays the following message: System Input Power Cap cannot be set to less than or equal to 13300 W (45381 BTU/h) while Extended Power Performance is enabled. Selecting the check box to enable Max Power Conservation Mode (MPCM) displays the following message: Enabling Max Power Conservation Mode will deactivate Extended Power Performance.
Available Power in EPP Pool Used Power in EPP Pool EPP Percent - Available = 3167 W (10806 BTU/h) = 0 W (0 BTU/h) = 100.
• Enabling EPP on a 3000W AC PSU when SBPM is Enabled racadm config -g cfgChassisPower -o cfgChassisEPPEnable 1 This feature is not supported while Server Based Power Management is enabled. • Enabling EPP on a 3000W AC PSU when MPCM is Enabled racadm config -g cfgChassisPower -o cfgChassisEPPEnable 1 This feature is not supported while Max Power Conservation Mode is enabled.
