Dell Chassis Management Controller Version 6.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. © 2008 - 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview.......................................................................................................................................................14 What is new in this release.............................................................................................................................................. 15 Key Features..........................................................................................................................................................
Setting Date and Time on CMC.....................................................................................................................................35 Setting Date and Time on CMC Using CMC Web Interface................................................................................ 35 Setting Date and Time on CMC Using RACADM.................................................................................................. 35 Configuring LEDs to Identify Components on the Chassis...............
Updating IOM Coprocessor Using CMC Web Interface....................................................................................... 52 Updating IOM Firmware Using RACADM............................................................................................................... 52 Updating Server iDRAC Firmware Using Web Interface.............................................................................................52 Updating Server iDRAC Firmware Using RACADM...................................
Configuring CMC Network and Login Security Settings............................................................................................ 82 Configuring IP Range Attributes Using CMC Web Interface .............................................................................. 83 Configuring IP Range Attributes Using RACADM..................................................................................................83 Configuring Virtual LAN Tag Properties for CMC....................................
Parsing Rules............................................................................................................................................................. 101 Configuring Multiple CMCs through RACADM Using Configuration File................................................................102 Creating a CMC Configuration File........................................................................................................................ 102 Parsing Rules.................................
Importing Boot Identity Profiles..............................................................................................................................125 Exporting Boot Identity Profiles..............................................................................................................................125 Deleting Boot Identity Profiles................................................................................................................................
Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface.................... 164 Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM................. 165 11 Configuring CMC to Use Command Line Consoles.................................................................................... 166 CMC Command Line Console Features......................................................................................................................
Monitoring IOM Health.................................................................................................................................................. 194 Viewing Input Output Module Uplink and Downlink Status Using Web Interface.................................................. 194 Viewing Input Output Module FCoE Session Information Using Web Interface.................................................... 195 Viewing Stacking Information for Dell PowerEdge M Input Output Aggregator.........
Managing iKVM From CMC.......................................................................................................................................... 217 Enabling or Disabling Access to iKVM from Front Panel..................................................................................... 217 Enabling Access to iKVM from the Dell CMC Console........................................................................................ 217 15 Managing and Monitoring Power..............................
Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP..............................................239 Supported Interfaces...............................................................................................................................................240 Downloading SNMP Management Information Base File...................................................................................240 First Steps to Troubleshoot a Remote System.........................................
Single Sign On................................................................................................................................................................ 272 19 Use Case Scenarios.................................................................................................................................. 273 Chassis Basic Configuration and Firmware Update...................................................................................................
1 Overview The Dell Chassis Management Controller (CMC) for Dell EMC PowerEdge M1000e chassis is a systems management hardware and software solution for managing multiple Dell server chassis. It is a hot-pluggable card that is installed at the back of Dell PowerEdge M1000e chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.
• Latest Firmware Versions for This Release • Supported Remote Access Connections • Supported platforms • Supported Management Station Web Browsers • Viewing Localized Versions of the CMC Web Interface • Supported Management Console Applications • Other Documents You May Need • Contacting Dell • Social Media Reference What is new in this release This release of CMC for Dell EMC PowerEdge M1000e supports: • Updating the Linux kernel open source package to version 4.9.31.
• Support for WS-Management. • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/MAC) IDs with chassisassigned WWN/MAC IDs for a particular slot, an optional upgrade. • iDRAC IO Identity feature support for enhanced WWN/MAC Address Inventory. • Graphical display of chassis component status and health. • Support for single and multi-slot servers. • LCD iDRAC configuration wizard support for iDRAC network configuration. • iDRAC single sign-on.
Figure 1. CMC slot locations in chassis Table 1. CMC slot location details 1 GB Port 2 STK Port CMC Port Information The following TCP/IP ports are required to remotely access CMC through firewalls. These are the ports CMC listens to for connections. Table 2. CMC Server Listening Ports Port Number Function 22* SSH 23* Telnet 80* HTTP 161 SNMP Agent 443* HTTPS * Configurable port The following table lists the ports that CMC uses as a client. Table 3.
Port Number Function 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 4. Minimum CMC Version for Blade Servers Servers Minimum version of CMC PowerEdge M600 CMC 1.0 PowerEdge M605 CMC 1.0 PowerEdge M805 CMC 1.2 PowerEdge M905 CMC 1.2 PowerEdge M610 CMC 2.0 PowerEdge M610x CMC 3.0 PowerEdge M710 CMC 2.
IOM Switches Minimum version of CMC 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.0 Brocade M5424 CMC 1.2 Cisco Catalyst CBS 3130X-S CMC 1.0 Cisco Catalyst CBS 3130G CMC 1.
Servers BIOS iDRAC Lifecycle Controller PowerEdge M910 2.9.0 3.50 1.6 Power Edge M915 3.2.2 3.80 1.7.5.4 PowerEdge M420 2.3.3 2.40.40.40 2.40.40.40 PowerEdge M520 2.4.2 2.40.40.40 2.40.40.40 PowerEdge M620 2.5.4 2.40.40.40 2.40.40.40 PowerEdge M820 2.3.3 2.40.40.40 2.40.40.40 PowerEdge M630 2.7.1 2.52.52.52 2.52.52.52 PowerEdge M830 2.7.1 2.52.52.52 2.52.52.52 PowerEdge M640 1.0.0 3.10.10.10 3.10.10.10 NOTE: Array Software version 6.0.4 supports PowerEdge PSM4110.
Supported Management Station Web Browsers For the latest information on supported web browsers, see the Chassis Management Controller Version 6.1 Release Notes at dell.com/ cmcmanuals. • Microsoft Internet Explorer 11 • Microsoft EDGE • Safari version 8.0.8 • Safari version 9.0.3 • Mozilla Firefox 57 • Mozilla Firefox 58 • Google Chrome 62 • Google Chrome 63 NOTE: By default, TLS 1.1 and TLS 1.2 are supported in this release. However, to enable TLS 1.
– The Dell OpenManage SNMP Reference Guide for iDRAC and Chassis Management Controller provides information about SNMP MIBs. – The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy. The following system documents available at dell.
2 Installing and Setting Up CMC 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.
1 Ensure that CMC and the management station where you use your browser are on the same network, which is called the management network. Connect an Ethernet network cable from the CMC port labelled GB to the management network. NOTE: Do not place a cable in CMC Ethernet port labelled STK. For more information to cable the STK port, see Understanding Redundant CMC Environment. 2 Install the I/O modules in the chassis and connect the cables. 3 Insert the servers in the chassis.
Figure 2. Daisy-chained CMC network 1 Management Network 2 Standby CMC 3 Active CMC The following figures provide examples of incorrect cabling of CMC. Figure 3.
Figure 4. Incorrect cabling for CMC network — single CMC Figure 5. Incorrect cabling for CMC network — 2 CMCs 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.
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. You can also download the latest version of the Dell DRAC Tools from dell.com/ support. Installing RACADM on a Linux Management Station 1 Log in as root to the system running a supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components.
Proxy Server To browse through a proxy server that does not have access to the management network, you can add the management network addresses to the exception list of the browser. This instructs the browser to bypass the proxy server while accessing the management network. Internet Explorer To edit the exception list in Internet Explorer: 1 Start Internet Explorer. 2 Click Tools > Internet Options > Connections. 3 In the Local Area Network (LAN) settings section, click LAN Settings.
the Internet is not accessible, this feature can cause a delay of several seconds when you access the CMC using the browser or a command line interface such as remote RACADM. To disable CRL fetching: 1 Start Internet Explorer. 2 Click Tools > Internet Options and then click Advanced. 3 Scroll to the Security section, clear the Check for publisher’s certificate revocation check box, and click OK.
If you have one chassis, connect CMC and the standby CMC to the management network. If you have a redundant CMC, use another network cable and connect the GB CMC port to a second port of the management network. If you have more than one chassis you can choose between the basic connection, where each CMC is connected to the management network, or a daisy-chained chassis connection, where the chassis are connected in series and only one CMC is connected to the management network.
whether your network supports the above network speeds and set it accordingly. If the network configuration does not match any of these values, it is recommended to use Auto Negotiation (the Auto option) or refer to your network equipment manufacturer. Press the center button to continue to the next CMC Network Settings screen. 5 Select the duplex mode (half or full) that matches the network environment.
Static You must manually enter the IP address, gateway, and subnet mask in the screens following immediately. If you have selected the Static option, press the center button to continue to the next iDRAC Network Settings screen, then: • Set the Static IP Address by using the right or left arrow keys to move between positions, and the up and down arrow keys to select a number for each position. This address is the static IP of the iDRAC located in the first slot.
Interface Description 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 Chassis LCD Panel Use this command line utility to manage CMC and its components. You can use remote or firmware RACADM: • Remote RACADM is a client utility that runs on a management station.
Interface Description WinRM tool sets a default response timeout of 60 seconds for all WSMan commands it sends out. WinRM does not allow varying this timeout interval. Using “winrm set winrm/config @{MaxTimeoutms ="80000"}” does not change the timeout due to a bug in the WinRM tool. Therefore, it is recommended that WinRM is not used for commands that may take more than one minute to complete execution.
Setting Chassis Physical Location and Chassis Name Using RACADM To set the chassis name or location, date and time using the command line interface, see the setsysinfo and setchassisname commands. For more information, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Setting Date and Time on CMC You can set the date and time manually, or you can synchronize the date and time with a Network Time Protocol (NTP) server.
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. Configuring LED Blinking Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm setled -m [-l ] where specifies the module whose LED you want to configure.
Configuring Login Lockout Policy Attributes Using CMC Web Interface NOTE: To perform the following steps, you must have Chassis Configuration Administrator privilege. 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.
• 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.
NOTE: You can configure the enclosure either with a single CMC or with redundant CMCs. In redundant CMC configurations, if the primary CMC loses communication with the enclosure or the management network, the standby CMC takes over chassis management. Active CMC Election Process There is no difference between the two CMC slots; that is, slot does not dictate precedence. Instead, CMC that is installed or booted first assumes the role of the active CMC.
3 Logging In to CMC 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.
where is the IP address for CMC and is the HTTPS port number. The CMC Login page is displayed. Related links Configuring Web Browser Logging Into CMC as Local User, Active Directory User, or LDAP User 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.
Related links 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.
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. NOTE: If you have changed the default HTTPS port number (port 80), access the CMC Web interface using
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. For more information about RACADM, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. For more information about configuring multiple CMCs, see Configuring Multiple CMCs Using RACADM.
• 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. Active Directory and LDAP accounts are not considered when determining if any (local) account has root and calvin as the credentials. A warning message is also displayed when you log in to CMC using SSH, Telnet, remote RACADM, or the Web interface.
The Users page is displayed. 2 In the Default Password Warning section, select Enable, and then click Apply to enable the display of the Default Password Warning page when you log in to CMC. if not, select Disable. Alternatively, if this feature is enabled and you do not want to display the warning message for subsequent login operations, on the Default Password Warning page, select the Do not show this warning again option, and then click Apply.
4 Updating Firmware 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.
The following software components are included with the CMC firmware package: • Compiled CMC firmware code and data • Web interface, JPEG, and other user interface data files • Default configuration files Alternatively, use the Dell Repository Manager (DRM) to check for the latest available firmware updates. The Dell Repository Manager (DRM) ensures that the Dell systems are up-to-date with the latest BIOS, driver, firmware, and software.
If the chassis contains an earlier generation server whose iDRAC is in recovery mode or if CMC detects that iDRAC has corrupted firmware, then the earlier generation iDRAC is also listed on the Firmware Update page. 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.
Related links Downloading CMC Firmware Viewing Currently Installed Firmware Versions Updating CMC Firmware Using Web Interface To update the CMC firmware using the CMC Web interface: 1 Go to any of the following pages: • Chassis Overview > Update • Chassis Overview > Chassis Controller > Update • Chassis Overview > I/O Module Overview > Update • Chassis Overview > iKVM > Update The Firmware Update page is displayed.
Updating iKVM Firmware Using CMC Web Interface To update the iKVM firmware using the CMC Web interface: 1 Go to any of the following pages: • Chassis Overview > Update • Chassis Overview > Chassis Controller > Update • Chassis Overview > iKVM > Update The Firmware Update page is displayed. 2 In the iKVM Firmware section, select the check box in the Update Targets column for the iKVM you want to update the firmware and click Apply iKVM Update.
Updating IOM Coprocessor Using CMC Web Interface To update the IOM Infrastructure device firmware, in the CMC Web interface: 1 Go to Chassis Overview > I/O Module Overview > Update. The IOM Firmware Update page is displayed.
4 In the Firmware Image field, enter the path to the firmware image file on the management station or shared network, or click Browse to navigate to the file location. The default iDRAC firmware image name is firming.imc. 5 Click Begin Firmware Update and then click Yes to continue. The Firmware Update Progress section provides firmware update status information. A status indicator displays on the page while the image file uploads. File transfer time varies based on connection speed.
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.
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 6.0 to 6.1 version but the server components are not updated to the next version. NOTE: CMC firmware update from 6.0 to 6.
Platform M710HD M420 M520 M620 M820 M630 56 Updating Firmware Server Component Current Component Version (N-1 Version) Diagnostics 5158A3 BIOS 3.2.2 iDRAC 3.50 A00 Lifecycle Controller 1.6.0.73 Diagnostics 5158A3 BIOS 8.0.0 iDRAC 2.52.52.52 Lifecycle Controller 2.52.52.52 Diagnostics 4231A0 BIOS 2.4.2 NIC 19.2.0 iDRAC 2.52.52.52 Lifecycle Controller 2.52.52.52 Diagnostics 4231A0 BIOS 2.4.2 NIC 19.2.0 iDRAC 2.52.52.52 Lifecycle Controller 2.52.52.
Platform Server Component Current Component Version (N-1 Version) M830 iDRAC 2.52.52.52 Lifecycle Controller 2.52.52.52 Diagnostics 4239.44 BIOS 2.5.4 iDRAC 3.15.15.15 Lifecycle Controller 3.15.15.15 Diagnostics 4301A13 BIOS 1.3.7 M640 The following table lists the supported firmware versions for server components in a scenario where the existing CMC Firmware version is 6.0 and the server components are updated from N-1 version to N version.
Platform Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) M910 iDRAC 3.50 A00 3.85 A00 Lifecycle Controller 1.6.0.73 1.7.5.4 Diagnostics 5158A3 5162A0 BIOS 2.10.0 2.11.0 iDRAC 3.50 A00 3.85 A00 Lifecycle Controller 1.6.0.73 1.7.5.4 Diagnostics 5158A3 5162A0 BIOS 3.2.2 3.3.1 iDRAC 3.50 A00 3.85 A00 Lifecycle Controller 1.6.0.73 1.7.5.4 Diagnostics 5158A3 5162A0 BIOS 8.0.0 8.2.0 NIC 7.8.15 20.6.18 iDRAC 2.52.52.52 2.
Platform Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) M820 iDRAC 2.52.52.52 2.60.60.60 Lifecycle Controller 2.52.52.52 2.60.60.60 Diagnostics 4231A0 4247A1 BIOS 2.6.1 2.6.1 iDRAC 2.52.52.52 2.60.60.60 Lifecycle Controller 2.52.52.52 2.60.60.60 Diagnostics 4239.44 4239A36 BIOS 2.6.0 2.7.1 iDRAC 2.52.52.52 2.60.60.60 Lifecycle Controller 2.52.52.52 2.60.60.60 Diagnostics 4239.44 4239A36 BIOS 2.5.4 2.7.1 iDRAC 3.15.15.
In case of insufficient privileges, you can only view the firmware inventory of components and devices on the server. You cannot select any components or devices for any kind of Lifecycle Controller operation on the server. Choosing Server Component Firmware Update Type Using CMC Web Interface To select the type of server component update type: 1 In the system tree, go to Server Overview, and then click Update > Server Component Update. The Server Component Update page is displayed.
Component Name Firmware Rollback Supported? (Yes or No) Out-of-band — System Restart Required? In-band — System Restart Required? Lifecycle Controller GUI — Restart Required? Lifecycle Controller No No No Yes BIOS Yes Yes Yes Yes RAID Controller Yes Yes Yes Yes Backplanes Yes Yes Yes Yes Enclosures Yes Yes No Yes NIC Yes Yes Yes Yes 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
Few devices such as Network Interface Controllers (NICs) and RAID Controllers contain many types and models. The update selection logic automatically filters the relevant device type or model based on the initially selected devices. The primary reason for this automatic filtering behavior is that only one firmware image file for the category can be specified. 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.
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. This Rrepositry is stored in the CIFS or NFS Share configured by CMC. For information on creating a repository using the Dell Repository Manger, see the Dell Repository Manager Data Center Version 1.
Filtering Components for Firmware Updates Using CMC Web Interface To filter the devices: 1 In the system tree, go to Server Overview, and then click Update > Server Component Update. The Server Component Update page is displayed. 2 In the Choose Update Type section, select Update from File.
The Server Component Update page is displayed. 2 View the firmware inventory details in the Component/Device Firmware Inventory section. Table provides: • Servers that currently do not support the Lifecycle Controller service are listed as Not Supported. A hyperlink is provided to an alternative page where you can directly update only the iDRAC firmware. This page supports only iDRAC firmware update and not any other component and device on the server.
Field Description additional information of the current job status. This information can be viewed by clicking or hovering over the icon. Update Selects the component or device for firmware update on the server.
NOTE: If you are using CIFS that is registered with a domain, and are accessing the CIFS using the IP with the CIFS local user credentials, it is mandatory to enter the hostname or host IP in the Domain Name field. For more information, see the CMC Online Help. 3 Click Test Directory to verify whether the directories are readable and writeable. 4 Click Test Network Connection to verify if the network share location is accessible.
Re-installing Server Component Firmware You can re-install the firmware image of the currently installed firmware for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller. Re-installing Server Component Firmware Using Web Interface To re-install Server Component Firmware: 1 In the system tree, go to Server Overview, and then Click > Update > Server Component Update. The Server Component Update page is displayed.
NOTE: You cannot perform the job deletion operation for the Update from Network Share mode of server component update. 3 In the Component/Device Update Filter section, filter the component or device (optional). For more information see Filtering Components for Firmware Updates Using CMC Web Interface. 4 In the Job Status column, a check box displayed next to the job status indicates that a Lifecycle Controller job is in progress and currently is in the indicated state.
5 Viewing Chassis Information and Monitoring Chassis and Component Health 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 Topics: • Viewing Chassis Component Summaries • Viewing Chassis Summary • Viewing Chassis Controller Information and Status • Viewing Information an
Figure 6. Example of Chassis Graphics in the Web Interface To view the chassis health, go to Chassis Overview > Properties > Health. It displays the overall health status for the chassis, active and standby CMCs, sever modules, IO Modules (IOMs), fans, iKVM, power supplies (PSUs), temperature sensors, and LCD assembly. Detailed information for each component is displayed when you click on that component. In addition, the latest events in the CMC Hardware Log are also displayed.
Icon Description Server is reporting a non-critical error. Server is reporting a critical error. No server is present. Table 15. Server Icon States in 14th generation systems Icon Description Server is powered on and is operating normally. Server is off. Server is reporting a non-critical error.
Icon Description Server is reporting a critical error. No server is present. NOTE: By default, the server state icons for Dell's 13th generation PowerEdge systems are displayed if, you insert a 14th generation PowerEdge server when the chassis is turned off.
Component OSCAR Console iKVM Power Supply Units Fans IOM Slot Heath and Performance Properties Power Status • Speed Properties Quick Links • CPU Information • Server Component Update • Total System Memory • Name • iKVM Status • Part Number • Firmware Update • Firmware • Hardware • Power Supply Status • Power Consumption • System Budget • Fans Status Capacity • Lower Critical Threshold • Upper Critical Threshold • Power State • Model • Role • Service Tag IOM
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. For more information, see the CMC Online Help. 2 Go to Chassis Overview > Server Overview > Properties > Status. The Servers Status page provides overviews of the servers in 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. IOM health status is indicated by the overlay of the IOM subgraphic. Move the cursor to hover over the individual IOM subgraphic.
subgraphic and a corresponding text hint or screen tip is displayed. The text hint provides additional information for the iKVM. Click the iKVM subgraphic to view the iKVM information on the right. 2 Go to Chassis Overview > iKVM > Properties. The iKVM Status page displays the status and readings of the iKVM associated with the chassis. For more information, see the CMC Online Help.
6 Configuring CMC 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.
Related links Logging In to CMC Viewing and Modifying CMC Network LAN Settings Configuring CMC Network and Login Security Settings Configuring Virtual LAN Tag Properties for CMC Configuring Services Configuring LEDs to Identify Components on the Chassis Setting Up Chassis Group Configuring Server Managing Input Output Fabric Configuring and Using iKVM Obtaining Certificates Configuring User Accounts and Privileges Configuring CMC To Send Alerts Managing and Monitoring Power Configuring Multiple CMCs through
For more information about the subcommands and objects, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
Enabling or Disabling DHCP for the CMC Network Interface Address When enabled, the CMC’s DHCP for NIC address feature requests and obtains an IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically. This feature is enabled by default. You can disable the DHCP for NIC address feature and specify a static IP address, subnet mask, and gateway. For more information, see Setting Up Initial Access to CMC.
where is a string of up to 63 alphanumeric characters and hyphens. For example: cmc-1, d-345. NOTE: If a DNS Domain name is not specified, then the maximum number of characters is 63. If a domain name is specified, then the number of characters in CMC name plus the number of characters in the DNS Domain Name must be less than or equal to 63 characters. • DNS Domain Name — The default DNS domain name is a single blank character.
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 Using Web Interface To configure VLAN for CMC 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. • In the system tree, go to Chassis Overview > Server Overview and click Network > VLAN. The VLAN Tag Settings page is displayed. VLAN tags are chassis properties. They remain with the chassis even when a component is removed.
You can also remove the CMC VLAN using the following command: racadm setniccfg -v Federal Information Processing Standards The agencies and contractors of the Federal government of the United States use Federal Information Processing Standards (FIPS), a computer security standard, which is related to all applications that have communicative interfaces. The 140–2 comprises of four levels — Level 1, Level 2, Level 3, and Level 4.
Enabling FIPS Mode Using RACADM To enable FIPS mode, run the following command: racadm config –g cfgRacTuning –o cfgRacTuneFipsModeEnable 1 . Disabling FIPS Mode To disable FIPS mode, reset CMC to the default factory settings. 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.
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 Under Group Management, enter the member’s IP address or DNS name in the Hostname/IP Address field. NOTE: For MCM to function properly, you must use the default HTTPS port (443) on all group members and the leader chassis.
The lead chassis then communicates to all the members that they have been removed from the group. Finally the lead chassis discontinues its role. It can now be assigned as a member or a leader of another group. The member chassis may not receive the message, if a network issue prevents contact between the leader and the member. In this case, disable the member from the member chassis to complete the removal.
Select only those setting categories that you want identically configured, across all members of the chassis group. For example, select Logging and Alerting Properties category, to enable all chassis in the group to share the logging and alerting configuration settings of the lead chassis. 6 Click Save. If On-Change Propagation is selected, the member chassis take on the properties of the leader.
Chassis IP Address 192.168.0.1 Slot Location 1 Slot Name SLOT-01 Host Name Corporate web server NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Operating System Microsoft Windows Server 2012, Standard x64 Edition NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Model PowerEdgeM630 Service Tag 1PB8VF2 Total System Memory 4.0 GB # of CPUs 2 NOTE: Requires CMC 5.0 (or higher). NOTE: Requires CMC 5.
Viewing Chassis Group Inventory To view the chassis group using CMC Web interface, in the system tree, select Group. Click Properties > Firmware Version. The Chassis Group Firmware Version page displays all the chassis in the group. Viewing Selected Chassis Inventory Using Web Interface To view the selected chassis inventory using CMC Web interface: 1 In the system tree, select Group. click Properties > Firmware Version. The Chassis Group Firmware Version page displays all the chassis in the group.
Login Type Certificate Type How to Obtain • Trusted CA certificate — This certificate is issued by a CA. Active Directory user login Trusted CA certificate This certificate is issued by a CA. Local User login SSL Certificate Generate a CSR and get it signed from a trusted CA. NOTE: CMC ships with a default self-signed SSL server certificate. The CMC Web server and Virtual Console use this certificate.
certificate authority issues a certificate to the applicant that uniquely identifies that applicant for transactions over networks and on the Internet. After the certificate authority approves the CSR and sends you a certificate, you must upload the certificate to the CMC firmware. The CSR information stored on the CMC firmware must match the information contained in the certificate. NOTE: To configure SSL settings for CMC, you must have Chassis Configuration Administrator privilege.
Uploading Server Certificate After generating a CSR, you can upload the signed SSL server certificate to the CMC firmware. CMC resets after the certificate is uploaded. CMC accepts only X509, Base 64 encoded Web server certificates. CAUTION: During the certificate upload process, CMC is not available. 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.
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.
Saving Chassis Configuration You can save the current chassis configuration to an XML file on a network share or local management station. The configurations include all the chassis properties that can be modified using the CMC web interface and RACADM commands. You can also use the XML file that is saved to restore the configuration on the same chassis or to configure other chassis. NOTE: Server and iDRAC settings are not saved or restored with the chassis configuration.
Viewing Stored Chassis Configuration Profiles To view the chassis configuration profiles stored on the network share, go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles > Stored Profiles section, select the profile and click View in the View Profile column. The View Settings page is displayed. For more information on the displayed settings, see the CMC Online Help.
The Edit Profile window is displayed. 2 Enter a desired profile name in the Profile Name field and click Edit Profile. Operation Successful message is displayed. 3 Click OK. Deleting Chassis Configuration Profiles You can delete a chassis configuration profile that is stored on the network share. To delete a chassis configuration profile, perform the following tasks: 1 Go to the Chassis Configuration Profiles page.
Importing Chassis Configuration profiles You can import chassis configuration profiles from network share to another chassis by using the set command. 1 To import the chassis configuration profiles from CIFS network share, type the following: racadm set –f clone.xml –t xml –l //xx.xx.xx.xx/PATH –u USERNAME –p PASSWORDCMC 2 To import the chassis configuration profiles from NFS network share, type the following: racadm set –f clone.xml –t xml –l xx.xx.xx.
Configuring Multiple CMCs through RACADM Using Configuration File Using configuration file, you can configure one or more CMCs with identical properties through RACADM.. When you query a specific CMC card using its group ID and object ID, RACADM creates the racadm.cfg configuration file from the retrieved information. By exporting the file to one or more CMCs, you can configure your controllers with identical properties in a minimal amount of time.
The entire file is parsed for correctness, and all errors display. Write commands are not transmitted to the CMC if an error is found in the .cfg file. You must correct all errors before any configuration can take place. To check for errors before you create the configuration file, use the -c option with the config subcommand. With the -c option, config only verifies syntax and does not write to the CMC. Follow these guidelines when you create a .
groups as defined in the database property chapter of the Chassis Management Controller for Dell PowerEdge M1000e RACADM 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.
[cfgLanNetworking] cfgNicIpAddress=192.168.2.110 cfgNicGateway=192.168.2.1 This file is updated as follows: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=192.168.1.143 # comment, the rest of this line is ignored cfgNicGateway=192.168.1.1 The command racadm config -f .cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.
• Cooling equivalent to previous generations of M1000e fans at the same power, when the ECM feature is disabled. ECM mode is recommended for: • Blade server configurations with high Thermal Design Power (TDP) processors. • Workloads where performance is a critical. • Systems deployed in environments where the inlet temperature exceeds 30°C [86°F].
• MPCM is already enabled. An alert message with the reason for ECM not getting enabled is displayed . NOTE: If you try to enable MPCM when ECM is enabled, the ECM mode changes to enabled but unsupported state.
7 Configuring Server 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 Topics: • Configuring Slot Names • Configuring iDRAC Network Settings • Configuring iDRAC VLAN Tag Settings • Setting First Boot Device • Configuring Server FlexAddress • Configuring Rem
NOTE: To change a slot name, you must have Chassis Configuration Administrator privilege. The slot name setting in the Web interface resides on CMC only. If a server is removed from the chassis, the slot name setting does not remain with the server. 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.
Table 18. : QuickDeploy Settings Setting Description QuickDeploy Enabled Enables or disables the QuickDeploy feature that automatically applies the iDRAC settings configured on this page to newly inserted servers. The auto configuration must be confirmed locally on the LCD panel. NOTE: This includes the root user password if the Set iDRAC Root Password on Server Insertion box is checked. By default, this option is disabled.
Setting Description NOTE: Note the following: • • • • The values of the number of IP addresses that are less than the minimum value required for a server type are grayed out. If you select an option that is lesser than the default value of the number of IP addresses reserved, an error message is displayed warning that reducing the number of IP addresses prevents quick deploy of profiles to higher capacity servers. A warning message is logged in the CMC hardware log (SEL) and an SNMP alert is generated.
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. NOTE: Changes made to QuickDeploy fields are immediate, but changes made to one or more iDRAC server network configuration settings may require a couple of minutes to propagate from CMC to iDRAC.
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 In the system tree, go to Server Overview, and then click Setup > iDRAC. The Deploy iDRAC page is displayed.
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. 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. For more information about the fields, see the CMC Online Help.
You can set the following devices for first boot. Table 19. : Boot Devices Boot Device Description PXE Boot from a Preboot Execution Environment (PXE) protocol on the network interface card. Hard Drive Boot from the hard drive on the server. Local CD/DVD Boot from a CD/DVD drive on the server. Virtual Floppy Boot from the virtual floppy drive. The floppy drive (or a floppy disk image) is on another computer on the management network, and is attached using the iDRAC GUI console viewer.
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. 3 From the First Boot Device drop-down menu, select the boot device you want to use for each server. 4 If you want the server to boot from the selected device every time it boots, clear the Boot Once option for the server.
• The server is restarted. • Power is applied to the server if the server is turned off. Configuring Profile Settings Using Server Configuration Replication The server configurations replicating feature allows you to apply all profile settings from a specified server to one or more servers. Profile settings that can be replicated are those profile settings which can be modified and are intended to be replicated across servers.
Accessing Server Profiles Page You can add, manage, and apply server profiles to one or more servers using the Server Profiles page. To access the Server Profiles page using the CMC Web interface, in the system tree, go to Chassis Overview > Server Overview. Click Setup > Profiles. The Server Profiles page is displayed.
Applying Profile Server cloning is possible only when server profiles are available as stored profiles in the nonvolatile media on the CMC or stored on the remote share. To initiate a server configuration operation, you can apply a stored profile to one or more servers. NOTE: If a server does not support Lifecycle Controller or the chassis is powered off, you cannot apply a profile to the server. To apply a profile to one or more servers: 1 Go to the Server Profiles page.
NOTE: If the source profile is on the SD card, then a warning message is displayed that if the profile is exported, then the description is lost. Press OK to continue exporting the profile. A message is displayed prompting you to select the destination of the file: • Local or Network Share if the source file is on an SD card. 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.
NOTE: The CMC Server Cloning application retrieves and displays the settings for a specific server, only if the Collect System Inventory on Restart (CSIOR) option is enabled. To enable CSIOR on: • • • 11th generation servers — After rebooting the server, from the Ctrl-E setup, select System Services, enable CSIOR and save the changes. 12th generation servers — After rebooting the server, from the F2 setup, select iDRAC Settings > Lifecycle Controller, enable CSIOR and save the changes.
NOTE: Assigning Server Profiles to Slots The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots: 1 In the Server Profiles page, click Profiles for QuickDeploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Assign Profile column.
• Initial setup – Create a range of virtual MAC addresses. To create a MAC address, you must have Chassis Configuration Administrator and Server Administrator privileges. – Save boot identity profile templates and customize the boot identity profiles on the network share by editing and including the SAN boot parameters that are used by each server. – Prepare the servers that use initial configuration before applying their Boot Identity profiles.
Applying Boot Identity Profiles You can apply boot identity profile settings if the boot identity profiles are available as stored profiles on the network share. To initiate a boot identity configuration operation, you can apply a stored profile to a single server. NOTE: If a server does not support Lifecycle Controller or the chassis is powered off, you cannot apply a profile to the server. To apply a profile to a server, perform the following tasks: 1 Go to the Server Profiles page.
Importing Boot Identity Profiles You can import boot identity profiles that are stored on the management station to the network share. To import a stored profile on to the network share from the management station, perform the following tasks: 1 Go to the Server Profiles page. In the Boot Identity Profiles > Stored Profiles section, click Import Profile. The Import Profile section is displayed. 2 Click Browse to access the profile from the required location and then click Import Profile.
Creating MAC Pool You can create MAC pool in the network by using the Manage Virtual MAC Address Pool option available in the CMC web interface. NOTE: The Create MAC Pool section is displayed only if the MAC address database (vmacdb.xml) is not available in the network share. In this case, the Add MAC Address and Remove MAC Address options are disabled. To create a MAC pool: 1 Go to the Server Profiles page. In the Boot Identity Profiles > Manage Virtual MAC Address Pool section.
Deactivating MAC Addresses You can deactivate MAC addresses that are active by using the Deactivate MAC Address(es) option in the CMC web interface. NOTE: Use the Deactivate MAC Address(es) option only if the server is not responding to the Clear Identity action or the MAC address is not used in any server. To remove MAC addresses from the network share: 1 Go to the Server Profiles page.
Launching iDRAC From Servers Status Page To launch the iDRAC management console from the Servers Status page: 1 In the system tree, click Server Overview. The Servers Status page is displayed. 2 Click Launch iDRAC for the server you want to launch the iDRAC Web interface. NOTE: iDRAC launch can be configured through the IP address or the DNS name. The default method is using the IP address.
All servers (1–16) appear in the expanded servers list. 2 Click the server for which you want to launch the remote console. The Server Status page is displayed. 3 Click Launch Remote Console. Launching Remote Console from Servers Status Page To launch a remote console from the Servers Status page: 1 In the system tree, go to Server Overview, and then click Properties > Status. The Servers Status page is displayed. 2 Click Launch Remote Console for the required server.
8 Configuring CMC To Send Alerts 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.
Enabling Or Disabling Alerts Using RACADM To enable or disable generating alerts, use the cfgAlertingEnable RACAM object. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. 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.
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.
4 Event Filter Mask Value 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.
If your network has an SMTP server that releases and renews IP address leases periodically, and the addresses are different, then there is a duration when this property setting does not work due to change in the specified SMTP server IP address. In such cases, use the DNS name. Configuring Email Alert Settings Using CMC Web Interface To configure the email alert settings using Web interface: 1 In the system tree, go to Chassis Overview, and then click Alerts > E-mail Alert Settings.
NOTE: The commands in steps 2–6 overwrite any existing settings configured for the index you specify (1–4). To determine whether an index has previously configured values, type:xracadm getconfig -g cfgEmailAlert — I . If the index is configured, values appear for the cfgEmailAlertAddress and cfgEmailAlertEmailName objects. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals.
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 log in. 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 Listed below are the privileges and the actions on the server to which the Server Administrator is entitled. These rights are applied only when the chassis user does not have the Server Administrative privilege on the chassis.
User Group Privileges Granted • • • • • Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator Guest User Login Custom Select any combination of the following permissions: • • • • • • • • • • • None CMC Login User Chassis Configuration Administrator User Configuration Administrator Clear Logs Administrator Chassis Control Administrator (Power commands) Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator Fabric B A
The Users page is displayed. 2 In the User ID column, click user ID 1. NOTE: User ID 1 is the root user account that is shipped by default with CMC. This cannot be changed. The User Configuration page is displayed. 3 Select Change Password check box. 4 Type the new password in the Password and Confirm Password fields. 5 Click Apply. The password is changed for user ID 1. Configuring Local Users You can configure up to 16 local users in CMC with specific access permissions.
Several parameters and object IDs are displayed with their current values. Two objects of importance are: # cfgUserAdminIndex=XX cfgUserAdminUserName= 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.
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 Type the following commands with the new user name and password.
Figure 7. CMC configuration with Active Directory Standard Schema 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 are defined on each CMC card and not in the Active Directory. You can configure up to five role groups in each CMC.
NOTE: The Bit Mask values are used only when setting Standard Schema with the RACADM. NOTE: For more information about user privileges, see Types of Users. Configuring Standard Schema Active Directory To configure CMC for a Active Directory login access: 1 On an Active Directory server (domain controller), open the Active Directory Users and Computers Snap-in. 2 Using the CMC Web interface or RACADM: a b 3 Create a group or select an existing group. Configure the role privileges.
14 Click Apply Changes. The CMC Standard Schema Active Directory feature configuration is complete.
Each attribute or class that is added to an existing Active Directory Schema must be defined with a unique ID. To maintain unique IDs across the industry, Microsoft maintains a database of Active Directory Object Identifiers (OIDs) so that when companies add extensions to the schema, they can be guaranteed to be unique and not to conflict with each other.
The Association Object allows as many or as few users and/or groups and RAC Device Objects. However, the Association Object only includes one Privilege Object per Association Object. The Association Object connects the Users who have Privileges on RACs (CMCs). Additionally, you can configure Active Directory objects in a single domain or in multiple domains. For example, you have two CMCs (RAC1 and RAC2) and three existing Active Directory users (user1, user2, and user3).
Figure 10. Setting Up Active Directory Objects in Multiple Domains 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.
Extending Active Directory Schema Extending your Active Directory schema adds a Dell organizational unit, schema classes and attributes, and example privileges and association objects to the Active Directory schema. Before you extend the schema, make sure that you have Schema Admin privileges on the Schema Master Flexible Single Master Operation (FSMO) Role Owner of the domain forest.
Table 26. : dellRacDevice Class OID 1.2.840.113556.1.8000.1280.1.7.1.1 Descripti Represents the Dell RAC device. The RAC must be configured as delliDRACDevice in Active Directory. This configuration on enables CMC to send Lightweight Directory Access Protocol (LDAP) queries to Active Directory. Class Type Structural Class SuperCla dellProduct sses Attribute dellSchemaVersion s dellRacType Table 27. : delliDRACAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.7.1.
OID 1.2.840.113556.1.8000.1280.1.1.1.3 dellPermissionMask2 Table 29. : dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description Used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges Table 30. : 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.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.3 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: dellIsUserConfigAdmin TRUE 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.
Assigned OID/Syntax Object Identifier Single Valued Description: List of dellAssociationObjectMembers that belong to this Product. This attribute is the backward link to the dellProductMembers Linked attribute. Link ID: 12071 OID: 1.2.840.113556.1.8000.1280.1.1.2.14 Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellPermissionsMask1 OID: 1.2.840.113556.1.8000.1280.1.6.2.1 Integer (LDAPTYPE_INTEGER) Attribute: dellPermissionsMask2 OID: 1.2.840.113556.1.8000.1280.1.6.2.
3 Enter a name for the new object. The name must be identical to the CMC name that you provide in "Configuring Active Directory With Extended Schema Using CMC Web Interface”. 4 Select RAC Device Object and click OK. Creating Privilege Object To create privilege object: NOTE: You must create a privilege object in the same domain as the related association object. 1 In the Console Root (MMC) window, right-click a container. 2 Select New > Dell Remote Management Object.
Adding Privileges To add privileges: 1 Select the Privileges Object tab and click Add. 2 Enter the privilege object name and click OK. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to an RAC device. Only one privilege object can be added to an Association Object. Adding RAC Devices or RAC Device Groups To add RAC devices or RAC device groups: 1 Select the Products tab and click Add.
The SSL certificates for the domain controllers must be signed by the root certificate authority-signed certificate. The root certificate authority-signed certificate must be available on the management station accessing CMC. CAUTION: SSL certificate validation is required by default. Disabling this certificate is risky. 7 If you have enabled Single Sign-On (SSO), in the Kerberos Keytab section, click Browse, specify the keytab file and click Upload.
To specify a Global Catalog server, type: racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog NOTE: Setting the IP address as 0.0.0.0 disables CMC from searching for a server. NOTE: You can specify a list of LDAP or global catalog servers separated by commas. CMC allows you to specify up to three IP addresses or host names.
Figure 11. 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.
Configuring Generic LDAP Directory Service Using CMC WebBased Interface To configure the generic LDAP directory service: NOTE: You must have Chassis Configuration Administrator privilege. 1 In the system tree, go to Chassis Overview, and then click User Authentication > Directory Services. 2 Select Generic LDAP. The settings to be configured for standard schema is displayed on the same page. 3 Specify the following: NOTE: For information about the various fields, see the CMC Online Help.
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.1 • $ racadm config -g cfgLDAP -o cfgLDAPBaseDN dc= company,dc=com CMC can be configured to optionally query a DNS server for SRV records. If the cfgLDAPSRVLookupEnable property is enabled the cfgLDAPServer property is ignored.
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.
• Kerberos Key Distribution Center (packaged with the Active Directory Server software). • DHCP server (recommended). • The DNS server reverse zone must have an entry for the Active Directory server and CMC. Client Systems • For only Smart Card login, the client system must have the Microsoft Visual C++ 2005 redistributable. For more information see www.microsoft.com/downloads/details.
NOTE: The cmcname.domainname.com must be lower case as required by RFC and the @REALM_NAME must be uppercase. In addition, CMC supports the DES-CBC-MD5 type of cryptography for Kerberos authentication. A keytab file is generated that must be uploaded to CMC. NOTE: The keytab contains an encryption key and must be kept secure. For more information on the ktpass utility, see the Microsoft website.
Internet Explorer — Ensure that the Internet Browser is configured to download Active-X plug-ins. Configuring CMC SSO Or Smart Card Login For Active Directory Users You can use CMC Web interface or RACADM to configure CMC SSO or smart card login.
When the upload is complete, a message is displayed indicating whether the keytab file is successfully uploaded or not.
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 NOTE: You can also use the racadm connect command. 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.
Table 33.
Related links Generating Public Keys for Systems Running Windows Generating Public Keys for Systems Running Linux RACADM Syntax Notes for CMC Viewing Public Keys Adding Public Keys Deleting Public Keys Generating Public Keys for Systems Running Windows Before adding an account, a public key is required from the system that accesses the CMC over SSH.
• For the –i option, the parameter must be svcacct. All other parameters for -i fail in CMC. The svcacct is a special account for public key authentication over SSH in CMC. • To log in to the CMC, the user must be service. Users of the other categories do have access to the public keys entered using the sshpkauth command. Viewing Public Keys To view the public keys that you have added to the CMC, type: racadm sshpkauth –i svcacct –k all –v To view one key at a time, replace all with a number from 1 – 6.
Configuring Minicom Version 2.0 NOTE: For best results, set the cfgSerialConsoleColumns property to match the number of columns. Be aware that the prompt consumes two characters. For example, for an 80-column terminal window: racadm config –g cfgSerial –o cfgSerialConsoleColumns 80. 1 If you do not have a Minicom configuration file, go to the next step. If you have a Minicom configuration file, type minicom and skip to step 12. 2 At the Linux command prompt, type minicom -s.
• iDRAC Web interface serial console redirection feature. • iDRAC Serial Over LAN (SOL) functionality. In a serial, Telnet, SSH console, the CMC supports the connect command to establish a serial connection to server or IOM modules. The server serial console contains both the BIOS boot and setup screens, and the operating system serial console. For I/O modules, the switch serial console is available.
Related links Configuring the Managed Server BIOS for Serial Console Redirection Configuring Windows for Serial Console Redirection Configuring Linux for Server Serial Console Redirection During Boot Configuring Linux for Server Serial Console Redirection After Boot Configuring the Managed Server BIOS for Serial Console Redirection It is necessary to connect to the managed server using the iKVM (see Managing Servers With iKVM ) or establish a Remote Console session from the iDRAC Web interface (see the iDR
3 If the /etc/grub.conf contains a splashimage directive, comment it out. The following example shows the changes described in this procedure. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes # to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, e.g. # root (hd0,0) # kernel /boot/vmlinuz-version ro root= /dev/sdal # initrd /boot/initrd-version.
# Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you # do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.
tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 ttyS1 176 Configuring CMC to Use Command Line Consoles
12 Using FlexAddress and FlexAdress Plus Cards This section provides information about FlexAddress and FlexAddress Plus cards, how to configure and use these cards.
The FlexAddress feature card contains a range of MAC addresses. Before installing FlexAddress, you can determine the range of MAC addresses contained on a FlexAddress feature card by inserting the SD card into an USB Memory Card Reader and viewing the pwwn_mac.xml file. This clear text XML file on the SD card contains an XML tag mac_start that is the first starting hex MAC address that is used for this unique MAC address range.
Figure 12. FlexAdress (FA) vs FlexPlusAddress (FA+) Features 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. Apply these updates before you enable FlexAddress.
Component Minimum Required Version CMC Version 1.10 or later NOTE: Any system ordered after June 2008 has the correct firmware versions. To make sure proper deployment of the FlexAddress feature, update the BIOS and the firmware in the following order: 1 Update all mezzanine card firmware and BIOS. 2 Update server module BIOS. 3 Update iDRAC firmware on the server module. 4 Update all CMC firmware in the chassis; if redundant CMCs are present, ensure both are updated.
Table 38. Status Messages Returned by featurecard -s Command Status Message Actions No feature card inserted. Check CMC to verify that the SD card was properly inserted. In a redundant CMC configuration, ensure 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.
If the chassis is not powered-down prior to execution, the command fails with the following error message: ERROR: Unable to deactivate the feature because the chassis is powered ON For further information on the command, see the feature command section of the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
Configuring FlexAddress for Chassis-Level Fabric and Slots Using CMC Web Interface To enable or disable fabrics and slots to use the FlexAddress feature using the CMC Web interface: 1 In the system tree, go to Server Overview, and then click Setup > FlexAddress. The Deploy FlexAddress page is displayed. 2 In the Select Fabrics for Chassis-Assigned WWN/MACs section, select the fabric type for which you want to enable FlexAddress. To disable, clear the option.
All the servers (1–16) appear in the expanded Servers list. 2 Click the server you want to view. The Server Status page displays. 3 Click the Setup tab, and the FlexAddress subtab. The FlexAddress page is displayed. 4 From the FlexAddress Enabled drop-down menu, select Yes to enable FlexAddress or select No to disable FlexAddress. 5 Click Apply to save the changes. For more information, see the CMC Online Help.
You can view the WWN/MAC Address inventory using the Web interface or the RACADM CLI. Based on the interface, you can filter the MAC address and know which WWN/MAC address is in use for that function or partition. If the adapter has NPAR enabled, you can view which partitions are enabled or disabled. Using the Web interface, you can view the WWN/MAC Addresses information for specific slots using the FlexAddress page (Click Server Overview > Slot > Setup > FlexAddress).
Viewing Advanced WWN or MAC Address Information Using Web Interface To view WWN/MAC Address Information for each server slot or all servers in a chassis, in the advanced mode: 1 Click Server Overview > Properties > WWN/MAC. The WWN/MAC Summary page displays the WWN/MAC Address Information. 2 From the View drop-down menu, select Advanced, to view the WWN/MAC Addresses attributes in detailed view.
To display the iSCSI MAC addresses for all servers, use the following RACADM command: racadm getmacaddress -t iscsi To display the iSCSI MAC for a specific server, use the following RACADM command: racadm getmacaddress [-m [-x]] [-t iscsi] To display the user-defined MAC and WWN address, use the following RACADM command: racadm getmacaddress -c io-identity racadm getmacaddress -c io-identity -m server -2 To display the console assigned MAC/WWN of all LOMs or mezzanine cards, use the following RACAD
A green check mark in the Server-Assigned or in Chassis-Assigned columns indicates the type of active addresses. Chassis-assigned addresses are assigned when FlexAddress is activated on the chassis, and represents the slot-persistent addresses. When ChassisaAssigned addresses are checked, those addresses are used even if one server is replaced with another server. Command Messages The following table lists the RACADM commands and output for common FlexAddress situations. Table 39.
FlexAddress DELL SOFTWARE LICENSE AGREEMENT This is a legal agreement between you, the user, and Dell Products L.P. or Dell Global B.V. ("Dell"). This agreement covers all software that is distributed with the Dell product, for which there is no separate license agreement between you and the manufacturer or owner of the software (collectively the "Software"). This agreement is not for the sale of Software or any other intellectual property.
PECUNIARY LOSS) ARISING OUT OF USE OR INABILITY TO USE THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Because some jurisdictions do not allow an exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you. OPEN SOURCE SOFTWARE A portion of this CD may contain open source software, which you can use under the terms and conditions of the specific license under which the open source software is distributed.
13 Managing Input Output Fabric 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.
Related links Fabric Management Overview Invalid Configurations Fresh Power-up Scenario Monitoring IOM Health Configuring Network Settings for IOMs Managing VLAN for IOM Managing Power Control Operation for IOMs Enabling or Disabling LED Blinking for IOMs Resetting IOM to Factory Default Settings Fabric Management Overview Fabric management helps avoid electrical, configuration, or connectivity-related problems due to installation of an IOM or MC that has an incompatible fabric type from the chassis' estab
Figure 13. Rear View of a Chassis, Showing the Location of the IOMs Table 40. Locations of IOMs at the rear of a chassis 1 Bank 1 (Slots A1, B1, C1) 2 Bank 2 (Slots A2, B2, C2) CMC creates entries in both the hardware log and CMC logs for invalid hardware configurations. For example: • An Ethernet MC connected to a Fibre Channel IOM is an invalid configuration.
Invalid Configurations There are three types of invalid configurations: • Invalid MC or LOM configuration, where a newly installed fabric type of the server is different from the existing IOM fabric, that is, LOM or MC of a single server is not supported by its corresponding IOM. In this case, all the other servers in the chassis are running, but the server with the mismatched MC card cannot be turned on. The power button on the server flashes amber to alert a fabric mismatch.
Viewing Input Output Module FCoE Session Information Using Web Interface You can view the FCoE session information for Dell PowerEdge M I/O Aggregator using the CMC Web interface: 1 In the system trees, go to Chassis Overview and expand I/O Module Overview. All the IOMs (1–6) appear in the expanded list. 2 Click the IOM (slot) you want to view and click Properties > FCoE. The FCoE I/O Module page specific to the IOM slot is displayed.
NOTE: Do not configure I/O module network settings for Ethernet pass-through and Infiniband switches. Configuring Network Settings for IOMs Using CMC Web Interface NOTE: This feature is supported on PowerEdge M I/O Aggregator IOM only. Other IOMs including MXL 10/40GbE are not supported. To configure the network settings for IOM(s) using the CMC web interface: 1 In the system tree, go to I/O Module Overview and click Setup or expand I/O Module Overview, select the IOM, and click Setup.
Related links Fabric Management Overview Invalid Configurations Fresh Power-up Scenario Monitoring IOM Health Configuring Network Settings for IOMs Managing VLAN for IOM Managing Power Control Operation for IOMs Enabling or Disabling LED Blinking for IOMs Updating IOM Software Using CMC Web Interface You can update the IOM software by selecting the required software image from a specified location. You can also rollback to an earlier software version.
NOTE: While logging into the IOA application for the first time, you are prompted to customize the password. Launching IOA GUI from the Chassis Overview page Go to the Chassis Overview > Quick Links > Launch I/O Module GUI. The IOA login page is displayed. Launching IOA GUI from the I/O Module Overview page In the directory tree, go to I/O Module Overview. On the I/O Module Status page, click Launch I/O Module GUI. The IOA login page is displayed.
While changing the mode of an IOA that has a static IP, from stacking to standalone, ensure that the network for the IOA is changed to DHCP. Else, the static IP is duplicated on all the IOAs. When the IOMs are in stacking mode, the stack ID is the same as the master IOM burned in the MAC during the initial power-on. The stack ID does not change when the IOM modes change.
Configuring Management VLAN on IOMs Using RACADM To configure management VLAN on IOMs using RACADM, use the racadm setniccfg –m switch-n -v command. • Specify the VLAN ID and priority of a particular IOM with the following command: racadm setniccfg -m switch - -v The valid values for are 1 – 6. The valid values for are 1 – 4000 and 4021 – 4094. Default is 1. The valid values for are 0 – 7. Default is 0.
For information about the fields, see CMC Online Help NOTE: The Summary VLANs of All Ports section displays information about the IOMs present in the Chassis and the assigned VLANs. Click Save to save a csv file of the summary of the current VLAN settings. NOTE: The CMC Managed VLANs section displays the summary of all VLANs assigned to the IOMs. 8 Click Apply. The network settings are configured for the IOM(s).
Removing VLANs for IOMs Using CMC Web Interface To remove VLANs from IOM(s) using the CMC Web interface: 1 In the system tree, go to I/O Module Overview and click Setup > VLAN Manager. The VLAN Manager page is displayed. 2 In the Step 1: Select I/O Module section, select the required IOMs. 3 In the Step 3: Edit VLANs section, select Remove VLANs in the drop down list and click Apply. The VLANs assigned to the selected IOMs are removed. An Operation Successful message is displayed.
The VLANs are assigned to the selected IOMs according to the default configurations. An Operation Successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field. NOTE: The Reset to All VLANs option is not supported in IOAs in Virtual Link Trunking (VLT) mode. Managing Power Control Operation for IOMs For information to set the power control operation for IOM(s), see Executing Power Control Operations on an IOM.
14 Configuring and Using iKVM 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.
Related links Using OSCAR Managing Servers With iKVM 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.
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 Up/Down Arrow keys Moves the cursor from line to line in lists. Right/Left Arrow keys Moves the cursor within the columns when editing a text box. / Moves the cursor to the top (Home) or bottom (End) of a list. Deletes characters in a text box. Number Keys Type from the keyboard or keypad. Disabled. To change case, use the key. Configuring OSCAR You can configure the OSCAR settings using the Setup dialog box.
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. • Select Slot to display servers numerically by slot number. Click OK. Assigning Key Sequences for OSCAR To assign one or more key sequences for OSCAR activation, select a key sequence from the Invoke OSCAR menu and click OK.
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. The Set Position Flag is displayed. 7 Left-click on the title bar and drag it to the desired location on the desktop and then right-click to return to the Flag dialog box. 8 Click OK and again click OK to save the settings.
Viewing Server Status The right columns of the Main dialog box indicates the server status in the chassis. The following table describes the status symbols. Table 44. OSCAR Interface Status Symbols Symbols Description Server is online. Server is offline or absent from chassis. Server is not available. Server is being accessed by the user channel indicated by the letter: • • A=rear panel B=front panel Selecting Servers Use the Main dialog box to select the servers.
The Main dialog box appears. 2 Click Setup and then Menu. The Menu dialog box appears. 3 Select Name or Slot for the Display/Sort Key. 4 Type the desired delay time in seconds in the Screen Delay Time field. 5 Click OK. Soft Switching to a Server To soft switch to a server: • To select a server, press .
Setting Console Security OSCAR enables you to configure security settings on the iKVM console. You can setup a screen saver mode that engages after the console remains unused for a specified delay time. Once engaged, the console remains locked until you press any key or move the mouse. Enter the screen saver password to continue. Use the Security dialog box to lock the console with a password, set or change the password, or enable the screen saver.
• If the mode is set to Screen, the OSCAR flag bounces around the screen for the duration of the test. Before the test starts, a warning popup box displays the following message: "Energy mode may damage a monitor that is not ENERGY STAR compliant. However, once started, the test can be quit immediately via mouse or keyboard interaction." CAUTION: Monitor damage may result from the use of Energy mode with monitors not compliant with Energy Star. 5 Optional: To activate the screen saver test, click Test.
Clearing Lost or Forgotten Password When the iKVM password is lost or forgotten, you can reset it to the iKVM factory default, and then change the password. You can reset the password using either the CMC Web interface or RACADM. To reset a lost or forgotten iKVM password using the CMC Web interface, in the system tree, go to Chassis Overview > iKVM, click Setup tab, and then click Restore Default Values. You can change the password from the default using OSCAR. For more information see Setting Password.
Related links Adding Servers to the Scan List Removing Server from Scan List Starting the Scan Mode Cancelling Scan Mode Adding Servers to the Scan List To add servers to the scan list: 1 Press . The Main dialog box is displayed. 2 Click Setup and then Scan. The Scan dialog box is displayed listing all servers in the chassis. 3 Perform one of the following functions: • Select the servers you want to scan • Double-click the server name or slot.
Cancelling Scan Mode To cancel the scan mode: 1 If OSCAR is open and the Main dialog box is displayed, select a server in the list. or If OSCAR is not open, move the mouse or press any key on the keyboard The Main dialog box is displayed. Select a server in the list. 2 Click Commands. The Commands dialog box is displayed. 3 Clear the Scan Enable option and click OK.
Managing iKVM From CMC You can do the following: • View iKVM status and properties • Update iKVM Firmware • Enable or disable access to iKVM from front panel • Enable or disable access to iKVM from the Dell CMC console Related links Updating iKVM Firmware Enabling or Disabling Access to iKVM from Front Panel Viewing iKVM Information and Health Status Enabling Access to iKVM from the Dell CMC Console Enabling or Disabling Access to iKVM from Front Panel You can enable or disable access to iKVM from
15 Managing and Monitoring Power The Dell PowerEdge M1000e server enclosure is the most power-efficient modular server enclosure. It is designed to include highlyefficient 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.
• Server Slot Power Priority Settings • Viewing Power Consumption Status • Viewing Power Budget Status • Redundancy Status and Overall Power Health • Configuring power budget and redundancy • Executing Power Control Operations Related links Redundancy Policies 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 redu
Figure 14. 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.
CMC does not require the PSU units to be present in any specific PSU slot positions when No Redundancy is configured. NOTE: All PSUs in the chassis are Online if DPSE is disabled when in No Redundancy mode. When DPSE is enabled all active PSUs in the chassis are listed as Online and additional PSUs may be turned to Standby to increase the system's power efficiency. Figure 16.
Performance mode is enabled, any of these other three features, DPSE, SBPM or SPOPR, cannot be enabled. You are prompted to disable Extended Power Performance feature before any of these three features can be enabled. Firmware downgrade to version earlier than CMC 4.5 firmware is blocked by the current firmware when the chassis is equipped with 3000W AC PSUs. The reason for this is that CMC firmware versions earlier than CMC 4.5 do not support 3000W AC PSUs.
NOTE: In a three PSU configuration, server load may prevent any PSUs from transitioning to Standby • In a Power Supply Redundancy configuration, the enclosure always keeps an additional PSU powered on and marked Online in addition to the PSUs required to turn on the enclosure. Power utilization is monitored and up to four PSUs could be moved to Standby state depending on the overall system load. In a six PSU configuration, a minimum of two power supply units are always turned on.
No Redundancy Power in excess of what is necessary to power the chassis is available, even on a failure, to continue to power the chassis. CAUTION: The No Redundancy mode uses optimum PSUs when DPSE is enabled for the requirements of the chassis. Failure of a single PSU could cause servers to lose power and data in this mode. Power Budgeting For Hardware Modules CMC offers a power budgeting service that allows you to configure power budget, redundancy, and dynamic power for the chassis.
power requirements, the iDRAC power envelope may change over time. iDRAC requests a power step-up only if the servers are fully consuming the allocated power. Under heavy load the performance of the server’s processors may be degraded to ensure power consumption stays lower than the userconfigured System Input Power Cap.
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. If you move the server to a new slot, you must re-configure the priority for the new slot location. NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege.
Viewing Power Budget Status You can view the power budget status using the CMC Web interface or RACADM. Viewing Power Budget Status Using CMC Web Interface To view power budget status using CMC Web interface, in the system tree go to Chassis Overview and click Power > Budget Status. The Power Budget Status page displays the system power policy configuration, power budget details, budget allocated for server modules, and chassis power supply details. For more information, see the CMC Online Help.
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.
The following table provides the firmware response to a PSU power down or removal as it applies to various PSU redundancy configurations. Table 47. Chassis Impact from PSU Failure or Removal PSU Configuration Dynamic PSU Engagement Firmware Response Grid Redundancy Disabled CMC alerts you of loss of Grid Redundancy. Power Supply Redundancy Disabled CMC alerts you of loss of Power Supply Redundancy. No Redundancy Disabled Decrease power to low priority servers, if needed.
Power Supply Event System Event Log (SEL) Entry Communication failure Cannot communicate with power supply . Communication restored Communication has been restored to power supply . Failure to communicate status data Cannot obtain status information from power supply . Status data communication restored Power supply status information successfully obtained. Over/Under-temperature The temperature for power supply is outside of range.
Related links Power Conservation and Power Budget Maximum Power Conservation Mode Server Power Reduction to Maintain Power Budget 110V PSUs AC Operation Server Performance Over Power Redundancy Remote Logging External Power Management Configuring Power Budget and Redundancy Using CMC Web Interface Configuring Power Budget and Redundancy Using RACADM Power Conservation and Power Budget CMC conserves power when the user-configured maximum power limit is reached.
CMC reduces server power allocation in two cases: • Overall power consumption exceeds the configurable System Input Power Cap. • A power failure occurs in a non-redundant configuration. 110V PSUs AC Operation Some PSUs support operation with 110V AC input. This input can exceed the allowed limit for the branch circuit. If any PSUs are connected to 110V AC, the user needs to set CMC for normal operation of the enclosure.
• Maximum Power Conservation Mode The CMC continues to maintain or manage: • Redundancy Policy • Remote Power Logging • Server Performance over Power Redundancy • Dynamic Power Supply Engagement • Server Power of 11th generation and earlier servers Dell OpenManage Power Center then manages prioritization and power of supported M1000e servers and later blade servers in the chassis from the budget available after allocation of power to chassis infrastructure and prior generation blade servers.
Configuring Power Budget and Redundancy Using RACADM NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. To enable and set the redundancy policy: 1 Open a serial/Telnet/SSH text console to CMC and log in. 2 Set properties as needed: • To select a redundancy policy, type: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy where is 0 (No Redundancy), 1 (Grid Redundancy), 2 (Power Supply Redundancy). The default is 0.
where n is 1-1440 minutes. • To determine if the power remote logging feature is enabled, type the following command: racadm getconfig -g cfgRemoteHosts -o cfgRhostsSyslogPowerLoggingEnabled • To determine the power remote logging interval, type the following command: racadm getconfig -g cfgRemoteHosts -o cfgRhostsSyslogPowerLoggingInterval The power remote logging feature is dependent on remote syslog hosts having been previously configured.
4 Click OK to perform the power management action (for example, perform a system to reset). Executing Power Control Operations on the Chassis Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m chassis where is powerup, powerdown,powercycle,nongraceshutdown,, or reset. AC Power Recovery If the AC power supply of a system is disrupted, the chassis is restored to the previous power state before the AC power loss.
Executing Power Control Operations on a Server Using CMC Web Interface To execute power control operation for an individual server using the CMC Web interface: 1 In the system tree, go to Chassis Overview and click Server Overview. 2 Click on the server for which you want to execute the power control operation, and then click the Power tab. The Server Power Management page is displayed.
where is a number 1-6 and specifies the IOM (A1, A2, B1, B2, C1, C2), and indicates the operation you want to execute: powercycle or reset.
16 Troubleshooting and Recovery 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.
• CMC information • Chassis information • Session information • Sensor information • Firmware build information Supported Interfaces • CLI RACADM • Remote RACADM • Telnet RACADM 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. Table 50.
First Steps to Troubleshoot a Remote System The following questions are commonly used to troubleshoot high-level problems in the managed system: • Is the system powered on or off? • If powered on, is the operating system functioning, crashed, or frozen? • If powered off, did the power turn off unexpectedly? 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 S
power supplies are connected to other AC Grid. If two PSUs are improperly connected, such as PSU3 and PSU4 are connected to the wrong AC grids, an AC grid failure causes loss of power to the least priority servers. • Problem: The least priority servers lost power after a PSU failure. – Resolution: This is expected behavior if the enclosure power policy was configured to No Redundancy.
Viewing Hardware Logs Using CMC Web Interface You can view, save, and clear the hardware log. You can sort the log entries based on Severity, Date/Time, or Description by clicking the column heading. Subsequent clicks on the column headings reverse the sort. To view the hardware logs using CMC Web interface, in the system tree, go to Chassis Overview and click Logs > Hardware Log. The Hardware Log page is displayed.
Viewing CMC Logs Using RACADM To view the CMC log information using RACADM, open a serial, Telnet, SSH text console to CMC, log in, and type: racadm getraclog You can view the enhanced chassis log by using this command racadm chassislog view To clear the CMC log, type: racadm clrraclog Viewing Enhanced Chassis Logs Using the Web Interface To view enhanced logging of the chassis the Enable Enhanced Logging and Events option in the General Settings page must be enabled.
The Reset Components page is displayed. 2 To reset the active CMC, in the CMC Status section, click Reset/Failover CMC. If a standby CMC is present and a chassis is fully redundant, a failover occurs causing the standby CMC to become active. 3 To reset the iDRAC only, without rebooting the Operating System, in the Reset Server section, click iDRAC Reset in the Reset dropdown menu for the servers, whose iDRAC you want to reset, and then click Apply Selections.
You can also check the ntpd status by typing the following racadm command: racadm getractime –n If the ‘*’ is not displayed for one of the configured servers, the settings may not be configured correctly. The output of this command contains detailed NTP statistics that may be useful in debugging the problem. If you attempt to configure a Windows-based NTP server, it may help to increase the MaxDist parameter for ntpd.
Component iKVM Server IOM (Common) IOM (Pass through) Fan LED Color, Blinking Pattern Status Amber, glowing steadily Not used Amber, blinking Fault Blue, dark Standby Green, glowing steadily Powered on Green, blinking Firmware is being uploaded Green, dark Powered off 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 B
Component PSU LED Color, Blinking Pattern Status Amber, glowing steadily Fan type not recognized, update CMC firmware Amber, blinking Fan fault; tachometer out of range 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
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.
Resetting Administrator Password CAUTION: Many repairs may only be done by a certified service technician. You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Figure 18. Password Reset Jumper Location Table 52. CMC Password Jumper Settings PASSWORD_RSET (default) The password reset feature is disabled. The password reset feature is enabled. 3 Slide the CMC module into the enclosure. Reattach any cables that were disconnected. NOTE: Make sure that the CMC module becomes the active CMC, and remains the active CMC until the remaining steps are completed. 4 If the jumpered CMC module is the only CMC, then wait for it to finish rebooting.
17 Using LCD Panel Interface You can use the LCD panel on the chassis to perform configuration and diagnostics, and to obtain status information about the chassis and its contents. The following figure illustrates the LCD panel. The LCD screen displays menus, icons, pictures, and messages. Figure 19. LCD Display Table 53.
Related links LCD Navigation Diagnostics LCD Hardware Troubleshooting Front Panel LCD Messages LCD Error Messages LCD Module and Server Status Information 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.
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.
Default Screen The Default Screen allows you to change the screen that the LCD panel displays when there is no activity at the panel. The factory default screen is the Main Menu. You can choose from the following screens to display: • • • • Main Menu Server Status (front graphical view of the chassis) Module Status (rear graphical view of the chassis) Custom (Dell logo with chassis name) The currently active default screen is highlighted in light blue.
To view the Graphical Server Status screen, highlight the rotate icon, and press the center button. To view the status screen for a module, use the up, down, left, and right arrow buttons to highlight the desired module, and press the center button. The Module Status screen displays. To return to the Main Menu, use the arrow buttons to highlight the Back icon, press the center button. The Main Menu displays.
Diagnostics The LCD panel helps you to diagnose problems with any server or module in the chassis. If there is a problem or fault with the chassis or any server or other module in the chassis, the LCD panel status indicator blinks amber. On the Main Menu an icon with an amber background displays next to the menu item—Server or Enclosure—that leads to the faulty server or module.
Table 56. LCD Hardware Troubleshooting Items Symptom Issue Recovery Action Alert screen message CMC Not Loss of communication from CMC to the Check that CMC is booting; then, reset CMC using GUI or RACADM commands. Responding and LED is blinking amber. LCD front panel. Alert screen message CMC Not LCD module communications is stuck Responding and LED is solid amber or during a CMC fail-over or reboots. is off. Review the hardware log using the GUI or RACADM commands.
Severity Message Cause Warning A firmware or software incompatibility detected between Firmware between the two devices does not match in order to system BIOS in slot and CMC. support one or more features. Warning A firmware or software incompatibility detected between Firmware between the two devices does not match in order to CMC 1 and CMC 2. support one or more features. Table 58. Enclosure/Chassis Status Screen Severity Message Cause Critical Fan is removed.
Table 60. IOM Status Screens Severity Message Cause Warning A fabric mismatch detected on I/O module . The IO module fabric does not match that of the server or the redundant I/O module. Warning A link tuning failure detected on I/O module . The IO module could not be set to correctly use the NIC on one or more servers. 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 thermal-tripped. Table 61.
Severity Message Cause 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. Critical The storage voltage is outside of the allowable range.
Severity Message Cause Critical An I/O channel check NMI was detected on a component at bus device function . A critical interrupt is generated in the I/O Channel. Critical An I/O channel check NMI wa detected on a component at slot . A critical interrupt is generated in the I/O Channel. Critical A PCI parity error was detected on a component at bus device function . Parity error was detected on the PCI bus.
Table 64. CMC Status Item Description Example: CMC1, CMC2 Name or Location. No Errors If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. Firmware Version Only displays on an active CMC. Displays Standby for the standby CMC. IP4 Displays current IPv4 enabled state only on an active CMC. IP4 Address: Only displays if IPv4 is enabled only on an active CMC.
Item Description RPM Current fan speed in RPM. Table 67. PSU Status Item Description Name/Location Example: PSU1, PSU2, and so on. Error Messages If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. Status Offline, Online, or Standby. Maximum Wattage Maximum Wattage that PSU can supply to the system. Table 68. IOM Status Item Description Name/Location Example: IOM A1, IOM B1. and so on.
Table 70. Server Status Item Description Example: Server 1, Server 2, etc. Name/Location. No Errors If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings. For more information see LCD Error Messages. Slot Name Chassis slot name. For example, SLOT-01. NOTE: You can set this table through the CMC CLI or Web interface. Name Name of the server, which the user can set through Dell OpenManage.
18 Frequently Asked Questions This section lists the frequently asked questions for the following: • RACADM • Managing and Recovering a Remote System • Active Directory • FlexAddress and FlexAddressPlus • iKVM • IOM Topics: • RACADM • Managing and Recovering a Remote System • Active Directory • FlexAddress and FlexAddressPlus • iKVM • IOM • Single Sign On RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is
The logout and quit commands are not supported in the CMC RACADM interface. 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.
Change the CMC community name using RACADM. To see the CMC community name, use the following command: racadm getconfig -g cfgOobSnmp To set the CMC community name, use the following command: racadm config -g cfgOobSnmp -o cfgOobSnmpAgentCommunity To prevent SNMP authentication traps from being generated, enter input community names that are accepted by the agent. Since CMC only allows one community name, enter the same get and set community name for IT Assistant discovery setup.
There is no visible change if a feature card is removed. Feature cards can be removed and stored or may be left in place. What happens if a feature card that was used in one chassis is removed and put into another chassis? The Web interface displays the following error message: This feature card was activated with a different chassis. It must be removed before accessing the FlexAddress feature.
The server module needs to be powered down before it can be used with FlexAddress. After the server BIOS update is complete, the server module does not get chassis-assigned addresses until the server has been power cycled. What happens if a chassis with a single CMC is downgraded with firmware prior to 1.10? • The FlexAddress feature and configuration is removed from the chassis. • The feature card used to activate the feature on this chassis is unchanged, and remains bound to the chassis.
The rear panel access does not work. Why? The front panel setting is enabled by CMC, and a monitor is currently connected to the front panel. Only one connection is allowed at a time. The front panel connection has precedence over ACI and the rear panel. For more information about connection precedence, see iKVM Connection Precedences. The message "User has been disabled as another appliance is currently tiered" appears on the monitor connected to the rear panel.
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. If an error is made in setting the IP,mask, or /gateway, the switch does not set the IP address and returns a 0.0.0.0 in all fields.
19 Use Case Scenarios This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Topics: • Chassis Basic Configuration and Firmware Update • Backup the CMC Configurations and Server Configurations.
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.
• 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. Max Power Conservation Mode option will force servers into a low power, limited performance mode and disable server power up. Press OK to continue.
• Enabling Server Based Power Mangement (SBMP) on a 3000W AC PSU racadm config -g cfgChassisPower -o cfgChassisServerBasedPowerMgmtMode 1 This feature is not supported while Extended Power Performance is enabled. • Enabling Dynamic Power Supply Engagement on a 3000W AC PSU racadm config -g cfgChassisPower -o cfgChassisDynamicPSUEngagementEnable 1 This feature is not supported while Extended Power Performance is enabled.
