Dell PowerEdge M1000e Chassis Management Controller Firmware Version 5.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your 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. © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview........................................................................................................................ 14 What is new in this release................................................................................................................................................14 Key Features.....................................................................................................................................................................
Setting Date and Time on CMC....................................................................................................................................... 34 Setting Date and Time on CMC Using CMC Web Interface....................................................................................... 34 Setting Date and Time on CMC Using RACADM.......................................................................................................
Updating IOM Coprocessor Using CMC Web Interface............................................................................................. 48 Updating IOM Firmware Using RACADM................................................................................................................... 48 Updating Server iDRAC Firmware Using Web Interface...................................................................................................49 Updating Server iDRAC Firmware Using RACADM...................
Configuring CMC Network and Login Security Settings...................................................................................................73 Configuring IP Range Attributes Using CMC Web Interface ......................................................................................74 Configuring IP Range Attributes Using RACADM....................................................................................................... 74 Configuring Virtual LAN Tag Properties for CMC.................
Parsing Rules............................................................................................................................................................. 90 Configuring Multiple CMCs through RACADM Using Configuration File........................................................................... 91 Creating a CMC Configuration File............................................................................................................................. 91 Parsing Rules...................
Importing Boot Identity Profiles................................................................................................................................. 112 Exporting Boot Identity Profiles................................................................................................................................. 112 Deleting Boot Identity Profiles...................................................................................................................................
Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface................................ 145 Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM.............................. 146 11 Configuring CMC to Use Command Line Consoles......................................................147 CMC Command Line Console Features..........................................................................................................................
Monitoring IOM Health................................................................................................................................................... 170 Viewing I/O Module Uplink and Downlink Status Using Web Interface........................................................................... 170 Viewing I/O Module FCoE Session Information Using Web Interface.............................................................................
Managing iKVM From CMC............................................................................................................................................190 Enabling or Disabling Access to iKVM from Front Panel........................................................................................... 190 Enabling Access to iKVM from the Dell CMC Console...............................................................................................191 15 Managing and Monitoring Power................
Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP.........................................................210 Supported Interfaces................................................................................................................................................210 Downloading SNMP Management Information Base (MIB) File................................................................................ 211 First Steps to Troubleshoot a Remote System.........................
Single Sign On.................................................................................................................................................................241 19 Use Case Scenarios................................................................................................... 242 Chassis Basic Configuration and Firmware Update........................................................................................................
1 Overview The Dell Chassis Management Controller (CMC) for Dell PowerEdge M1000e chassis is a systems management hardware and software solution for managing multiple Dell server chassis. It is a hot-pluggable card that is installed at the back of Dell PowerEdge M1000e chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.
• Disabling AC Power Recovery. • Updating the OpenSSL open source package to version 1.0.2f. • Updating the OpenSSH open source package to version 7.1p1. • Updating glibc to version 2.23 to address new security vulnerabilities. • TLS 1.2 and TLS 1.1 by default. • User configuration option to enable TLS 1.0 using RACADM. • Configuring SNMPv3 using RACADM. • Querying the health status of the chassis components using WSMan. • Initiating Quick Deploy of blade through RACADM commands.
• Support for single and multi-slot servers. • LCD iDRAC configuration wizard support for iDRAC network configuration. • iDRAC single sign-on. • Network time protocol (NTP) support. • Enhanced server summary, power reporting, and power control pages. • Forced CMC failover and virtual reseat of servers. • iDRAC reset without rebooting the operating system.
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 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.0 PowerEdge M710HD CMC 3.
IOM Switches Minimum version of CMC 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.0 Cisco Catalyst CBS 3032 CMC 1.0 Dell Force10 MXL 10/40GbE CMC 4.11 Dell PowerEdge M I/O Aggregator CMC 4.2 Mellanox M2401G DDR Infiniband Switch CMC 1.0 Mellanox M3601Q QDR Infiniband Switch CMC 2.
Servers BIOS iDRAC Lifecycle Controller PowerEdge M830 2.2.5 2.40.40.40 2.40.40.40 NOTE: Array Software version 6.0.4 supports PowerEdge PSM4110. Supported Remote Access Connections The following table lists the supported Remote Access Controllers. Table 7. Supported Remote Access Connections Connection Features CMC Network Interface ports • • • • • • • Serial port • • • Other connections • GB port: Dedicated network interface for the CMC Web interface.
• Mozilla Firefox 41 • Google Chrome 49 • Google Chrome 50 NOTE: By default, TLS 1.1 and TLS 1.2 are supported in this release. However, to enable TLS 1.0 use the following racadm command: $ racadm config -g cfgRacTuning -o cfgRacTuneTLSProtocolVersionEnable TLSv1.0+ Viewing Localized Versions of the CMC Web Interface To view localized versions of the CMC Web interface: 1. Open the Windows Control Panel. 2. Double-click the Regional Options icon. 3.
• The Hardware Owner’s Manual provides information about system features and describes how to troubleshoot the system and install or replace system components. • Systems management software documentation describes the features, requirements, installation, and basic operation of the software. • Documentation for any components you purchased separately provides information to configure and install these options. • Chassis Management Controller Version 5.
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.
10. Connect to each iDRAC and provide final configuration of iDRAC. Default user name is root and password is calvin. 11. Connect to each I/O module through the Web browser and provide final configuration of the I/O module. 12. Turn on the servers and install the operating system. Basic CMC Network Connection CAUTION: Connecting the STK port to the management network can have unpredictable results. Cabling GB and STK to the same network (broadcast domain) can cause a broadcast storm.
1 Management Network 2 Standby CMC 3 Active CMC The following figures provide examples of incorrect cabling of CMC.
To daisy-chain up to four chassis: 1. Connect the GB port of the active CMC in the first chassis to the management network. 2. Connect the GB port of the active CMC in the second chassis to the STK port of the active CMC in the first chassis. 3. If you have a third chassis, connect the GB port of its active CMC to the STK port of the active CMC in the second chassis. 4. If you have a fourth chassis, connect the GB port of its active CMC to the STK port of the third chassis. 5.
rpm -ivh *.rpm 5. For help on the RACADM command, type racadm help after you run the previous commands. For more information about RACADM, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. NOTE: When using the RACADM remote capability, you must have write permission on the folders where you are using the RACADM subcommands involving file operations, for example: racadm getconfig -f Uninstalling RACADM From a Linux Management Station 1.
Mozilla FireFox To edit the exception list in Mozilla Firefox version 3.0: 1. Start Mozilla Firefox. 2. Click Tools → Options (for systems running Windows) or click Edit → Preferences (for systems running Linux). 3. Click Advanced and then click the Network tab. 4. Click Settings. 5. Select the Manual Proxy Configuration. 6. In the No Proxy for field, type the addresses for CMCs and iDRACs on the management network as a comma-separated list. You can use DNS names and wildcards in your entries.
Setting Up Initial Access to CMC To manage CMC remotely, connect CMC to your management network and then configure CMC network settings. NOTE: To manage the M1000e solution, it must be connected to your management network. For information to configure CMC network settings, see Configuring Initial CMC Network. This initial configuration assigns the TCP/IP networking parameters that enable access to CMC.
Configuring CMC Network Using LCD Panel Interface NOTE: The option to configure CMC using the LCD panel is available only until CMC is deployed or the default password is changed. If the password is not changed, you can the continue to use the LCD to reset the configurations of the CMC causing a possible security risk. The LCD panel is located on the bottom-left corner on the front of the chassis. To set up a network using the LCD panel interface: 1. Press the chassis power button to turn it on.
setting, navigate to the left arrow button then press the center key to return to the screen for that setting. After making a correction, press the center button. • When you have confirmed the accuracy of the settings you entered, press the center button. The Register DNS? screen appears. NOTE: If the Dynamic Host Configuration Protocol (DHCP) mode is selected for CMC IP configuration, then DNS registration is also enabled by default. 8. If you selected DHCP in the previous step, go to step 10.
CMC and iDRACs are now available on the network. You can access the CMC on the assigned IP address using the Web interface or CLIs such as a serial console, Telnet, and SSH. NOTE: After you have completed network setup through the LCD Configuration Wizard, the Wizard is no longer available. Interfaces and Protocols to Access CMC After you have configured CMC network settings, you can remotely access CMC using various interfaces.
Interface Description (Windows) or the Open WSMan client (Linux) to use the LC-Remote Services functionality. You can also use Power Shell and Python to script to the WSMan interface. Web Services for Management (WS-Management) is a Simple Object Access Protocol (SOAP)–based protocol used for systems management. CMC uses WS–Management to convey Distributed Management Task Force (DMTF) Common Information Model (CIM)– based management information.
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.
• server-nx where n = 1-8 and x = a, b, c, or d • switch-n where n=1–6 • cmc-active and specifies whether the LED should blink. Configuration options: • 0 — not blinking (default) • 1 — blinking Configuring CMC Properties You can configure CMC properties such as power budgeting, network settings, users, and SNMP and email alerts using the Web interface or RACADM.
• User blocking • IP address blocking • Number of login attempts allowed • Timespan for the lockout failure counts to occur • Lockout penalty time • To enable user blocking feature, use: racadm config -g cfgRacTuning -o cfgRacTuneUserBlkEnable <0|1> • To enable IP blocking feature, use: racadm config –g cfgRacTuning –o cfgRacTuneIPBlkEnable <0|1> • To specify the number of login attempts, use: racadm config –g cfgRacTuning –o cfgRacTuneIpBlkFailCount • To specify the time span within which
CMC Failsafe Mode The M1000e enclosure enables the fail-safe mode to protect the blades and I/O modules from failures. The fail-safe mode is enabled when no CMC is in control of the chassis. During the CMC failover period or during a single CMC management loss: • You cannot turn on newly installed blades. • You cannot access existing blades remotely. • Chassis cooling fans run at 100% for thermal protection of the components.
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.
NOTE: • For added security, it is strongly recommended that you change the default password of the root account during initial setup. • When Certificate Validation is enabled, Fully Qualified Domain Name (FQDN) of the system should be provided. If certificate validation is enabled and IP address is provided for the Domain Controller, then the login is not successful. CMC does not support extended ASCII characters, such as ß, å, é, ü, or other characters used primarily in non-English languages.
• Upload a Trusted Certificate Authority (CA) certificate (CA-signed Active Directory certificate) to CMC. • Configure the DNS server. • Enable Active Directory login. • Enable Smart Card login. To log in to CMC as an Active Directory user using smart card: 1. Log in to CMC using the link https://. The CMC Login page is displayed prompting you to insert the smart card. NOTE: If you changed the default HTTPS port number (port 80), access the CMC Web page using
After you have configured your management station terminal emulator software and managed node BIOS, perform the following steps to log in to CMC: 1. Connect to the CMC using your management station terminal emulation software. 2. Type your CMC user name and password, and press . You are logged in to the CMC.
Table 9. Multiple CMC Sessions Interface Maximum Sessions per Interface CMC Web Interface 4 RACADM 4 Telnet 4 SSH 4 WS-MAN 4 iKVM 1 Serial 1 Changing Default Login Password The warning message that prompts you to change the default password is displayed if: • • • You log in to CMC with Configure Users privilege. Default password warning feature is enabled. Default user name and password for any currently enabled account are root and calvin respectively.
For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Enabling or Disabling Default Password Warning Message You can enable or disable the display of the default password warning message. To do this, you must have Configure Users privilege. Enabling or Disabling Default Password Warning Message Using Web Interface To enable or disable the display of the default password warning message after logging in to iDRAC: 1.
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.
• CMC firmware For more information on the update sequence for M1000e chassis, see the CMC Firmware 5.0 Release Notes on support site. Signed CMC Firmware Image For M1000e CMC version 5.0 and later, the firmware includes a signature. The CMC firmware performs a signature verification step to ensure the authenticity of the uploaded firmware. The firmware update process is successful only if the firmware image is authenticated by CMC to be a valid image from the service provider and has not been altered.
NOTE: CMC firmware update or roll back is supported only for the firmware versions 3.10, 3.20, 3.21, 4.0, 4.10, 4.11, 4.30, 4.31, 4.45, 4.5, 5.0, and later. For any version other than these, first update to any of these versions, and then update to the required version. The Active CMC resets and becomes temporarily unavailable after the firmware has been uploaded successfully. If a standby CMC is present, the standby and active roles swap. The standby CMC becomes the active CMC.
NOTE: The update may take several minutes for CMC. 6. For a standby CMC, when the update is complete the Update State field displays Done. For an active CMC, during the final phases of the firmware update process, the browser session and connection with CMC is lost temporarily as the active CMC is taken offline. You must log in again after a few minutes, when the active CMC has rebooted. After CMC resets, the new firmware is displayed on the Firmware Update page.
Updating IOM Infrastructure Device Firmware By performing this update, the firmware for a component of the IOM device is updated, but not the firmware of the IOM device itself; the component is the interface circuitry between the IOM device and CMC. The update image for the component resides in the CMC file system, and the component displays as an updatable device on the CMC Web interface only if the current revision on the component and the component image on CMC do not match.
Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server using in 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. You can also update server iDRAC firmware at Chassis Overview → Server Overview → Update .
NOTE: • While selecting the individual server components for update, make sure that there are no dependencies between the selected components. If not, selecting some components that have dependencies on other components for update may cause the server to stop functioning abruptly. • Make sure to update the server components in the recommended order. If not, the process of component firmware update may become unsuccessful..
• Other components NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecycle Controller. Supported Firmware Versions for Server Component Update The following section provides the supported component versions for CMC firmware update and Server Component Update. The following table lists the supported firmware versions for server components when CMC Firmware is updated from 5.1 to 5.
M520 M620 M820 M630 M830 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.8.6 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.7.6 NIC 7.6.15 iDRAC 1.45.45 Lifecycle Controller 1.1.5.165 Diagnostics 4225A2 BIOS 1.6.6 iDRAC Not Applicable Lifecycle Controller Not Applicable Diagnostics Not Applicable BIOS Not Applicable iDRAC 2.05.05.05 Lifecycle Controller 2.05.05.05 Diagnostics 4239A16_4239.24 BIOS 0.4.
M910 M710HD M420 M520 M620 M820 M630 M830 Diagnostics 5154A0 5158A3 BIOS 6.2.3 6.3.0 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 2.7.9 2.9.0 iDRAC 3.42_A00 3.50 A00 Lifecycle Controller 1.5.5.27 1.6.0.73 Diagnostics 5154A0 5158A3 BIOS 6.0.3 7.0.0 NIC 7.6.15 7.8.15 iDRAC 1.45.45 1.50.50 Lifecycle Controller 1.1.5.165 1.3.0.850 Diagnostics 4225A2 4231A0 BIOS 1.6.6 2.0.22 NIC 7.6.15 7.8.15 iDRAC 1.45.
• For iDRAC servers, on the boot console, when prompted with the message Press for Remote Access Setup within 5 sec., press . Then, on the setup screen, enable System Services. • For iDRAC servers, on the boot console, select F2 for System Setup. On the setup screen, select iDRAC Settings and then select System Services. Cancelling System Services enables you to cancel all scheduled jobs that are pending and remove them from the queue.
Component Name Firmware Rollback Out-of-band— Supported? (Yes or System Restart No) Required? In-band—System Restart Required? Lifecycle Controller GUI—Restart Required? Diagnostics No No No No OS Driver Pack No No No No 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
6. Select one of the following options: • Reboot Now - Reboot immediately. The firmware update is applied immediately • On Next Reboot - Manually reboot the server at a later time. The firmware update is applied after the next reboot. NOTE: This step is not valid for Lifecycle Controller and 32-bit Diagnostics firmware update. A server reboot is not required for these devices. 7. Click Update. The firmware version is updated for the selected component or device.
• 8. Reboot Now — Updates are scheduled and the server is rebooted, immediately applying the updates to the server components. • On Next Reboot — Updates are scheduled but are applied only after the next server reboot. Click Update to schedule firmware updates for the available components of the selected servers. A message is displayed based on the type of updates contained and asking you to confirm if you want to continue. 9.
the servers with only their BIOS component. If a BIOS component on one of the servers is selected, the inventory is further filtered to display the servers that match the model name of the selected server. If no filter is selected and a selection for update of a component or device is made on the inventory section, then the filter associated with that selection is automatically enabled.
Table 12. : Component and Devices Information Field Description Slot Displays the slot occupied by the server in the chassis. Slot numbers are sequential IDs, from 1 to 16 (for the 16 available slots in the chassis), that help to identify the location of the server in the chassis. When there are fewer than 16 servers occupying slots, only those slots populated by servers are displayed. Name Displays the name of the server in each slot. Model Displays the model of the server.
The Edit Network Share page is displayed. 2. In the Network Share Settings section, configure the following settings as required: • Protocol • IP Address or Host Name • Share Name • Update folder • File Name (optional) NOTE: File Name is optional only when the default catalog file name is catalog.xml. If the catalog file name is changed then the new name must be entered in this field. • Profile Folder • Domain Name • User Name • Password For more information, see the CMC Online Help. 3.
Related links Re-installing Server Component Firmware Rolling Back Server Component Firmware Upgrading Server Component Firmware Deleting Scheduled Server Component Firmware Jobs 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.
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. You can select the job for a deletion operation. 5. Click Job Deletion. The jobs are deleted for the selected components or devices.
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 Viewing Chassis Component Summaries When you log in to the CMC Web interface, the Chassis Health page allows you to view the health of the chassis and its
controlled by clicking the image of the required component. When a component is present in the chassis, an icon of that component type is shown in the graphics in the position (slot) where the component has been installed. Empty positions are shown with a charcoal gray background. The component icon visually indicates the state of the component. Other components display icons that visually represent the physical component.
The following table lists the component properties and information displayed on the Chassis Health page in Web interface.
Viewing Chassis Summary You can view the summary of the installed components in the chassis. To view the chassis summary information, in the CMC Web interface, go to Chassis Overview → Properties → Summary. The Chassis Summary page is displayed. For more information, see the CMC Online Help. Viewing Chassis Controller Information and Status To view the chassis controller information and status, in the CMC Web interface, go to Chassis Overview → Chassis Controller → Properties → Status.
The Storage Array Status page provides the health status and properties of the storage array. For more information, see the CMC Online Help. Viewing Information and Health Status of All IOMs To view health status of the 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.
NOTE: In the event of a communication failure between CMC and the fan unit, CMC cannot obtain or display health status for the fan unit. For more information, see the CMC Online Help. Viewing iKVM Information and Health Status The local access KVM module for the Dell M1000e server chassis is called the Avocent Integrated KVM Switch Module, or iKVM. To view the health status of the iKVMs associated with the chassis, do any of the following: 1. Go to Chassis Overview → Properties → Health.
3. Click the LCD subgraphic to view the LCD information on the right. 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.
When IPv6 is enabled at boot time, three router solicitations are sent every four seconds. If external network switches are running the Spanning Tree Protocol (SPT), the external switch ports may be blocked for more than twelve seconds in which the IPv6 router solicitations are sent. In such cases, there may be a period when IPv6 connectivity is limited, until router advertisements are gratuitously sent by the IPv6 routers.
For an IPv4 network, to disable DHCP and specify static CMC IP address, gateway, and subnet mask, type: racadm racadm racadm racadm config config config config -g -g -g -g cfgLanNetworking cfgLanNetworking cfgLanNetworking cfgLanNetworking -o -o -o -o cfgNicUseDHCP 0 cfgNicIpAddress cfgNicGateway cfgNicNetmask By default, for IPv6, the CMC requests and obtains a CMC IP address from the IPv6 Autoconfiguration mechanism automatically.
NOTE: Some DNS servers only register names of 31 characters or fewer. Make sure the designated name is within the DNS required limit. NOTE: The following settings are valid only if you have registered the CMC on the DNS server by setting cfgDNSRegisterRac to 1. • CMC Name — By default, the CMC name on the DNS server is cmc-.
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.
• 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. 2. In the CMC section, enable VLAN for CMC, set the priority and assign the ID. For more information about the fields, see the CMC Online Help. 3. Click Apply. The VLAN tag settings are saved.
NOTE: CMC supports enabling FIPS mode, but the feature is not validated. By default, the FIPS mode is disabled. When you enable FIPS, the CMC is reset to the default settings. When FIPS is enabled, the minimum key size for OpenSSL FIPS is SSH-2 RSA 2048 bits. NOTE: You cannot update the PSU firmware when a chassis is FIPS enabled. For more information, see CMC Online Help. The following features/applications support FIPS.
• SNMP — Enable CMC to send SNMP traps for events. • Remote Syslog — Enable CMC to log events to a remote server. NOTE: When modifying CMC service port numbers for SSH, Telnet, HTTP, or HTTPS, avoid using ports commonly used by OS services such as port 111. See Internet Assigned Numbers Authority (IANA) reserved ports at http:// www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml.
Similarly, when displaying the iDRAC properties using the RACADM getconfig command, the property values are displayed as N/A for an unsupported feature on the server.
To set up the Chassis Group using the CMC Web interface: 1. Log in with chassis administrator privileges to the chassis planned as the leader. 2. Click Setup → Group Administration. The Chassis Group page is displayed. 3. In the Chassis Group page, under Role, select Leader. A field to add the group name is displayed. 4. Enter the group name in the Group Name field, and then click Apply. NOTE: The same rules that apply for a domain name apply to the group name.
The lead chassis then communicates to the member or members, if more than one is selected, that it has been removed from the group. The member name is removed. 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. Related links Disabling an Individual Member at the Member Chassis Disbanding a Chassis Group To disband a chassis group from the lead chassis: 1.
3. Click Setup → Group Administration. 4. In the Chassis Properties Propagation section, select one of the propagation types: • On-Change Propagation — Select this option for automatic propagation of the selected chassis property settings. The property changes are propagated to all current group members, whenever lead properties are changed. • 5. Manual Propagation — Select this option for manual propagation of the chassis group leader properties with its members.
Table 14. : Blade Inventory Field Descriptions Data Field Example Chassis Name Data Center Chassis Leader Chassis IP Address 192.168.0.1 Slot Location 1 Slot Name SLOT-01 Host Name Corporate Webserver 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.
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. 2.
Login Type Certificate Type How to Obtain 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. Related links Secure Sockets Layer (SSL) Server Certificates Secure Sockets Layer (SSL) Server Certificates CMC includes a Web server that is configured to use the industry-standard SSL security protocol to transfer encrypted data over the Internet.
NOTE: Any server certificate you upload must be current (not expired) and signed by a certificate authority. Related links Generating a New Certificate Signing Request Uploading Server Certificate Viewing Server Certificate Generating a New Certificate Signing Request To ensure security, it is strongly recommended that you obtain and upload a secure server certificate to CMC.
Uploading Server Certificate Using CMC Web Interface To upload a server certificate using the CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Network → SSL. The SSL Main Menu is displayed. 2. Select Upload Server Certificate Based on Generated CSR option and click Next. 3. Click Choose File and specify the certificate file. 4. Click Apply. If the certificate is invalid, an error message is displayed.
NOTE: The server certificate displays the common name as the rack name appended with the domain name, if available. Else, only the rack name is displayed. Viewing Server Certificate Using RACADM To view the SSL server certificate, use the sslcertview command. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals.
Restoring Chassis Configuration Profile You can restore the configuration of a chassis by importing the backup file (.xml or .bak) on the local management station or the network share to which the chassis configurations were saved. The configurations include all the properties available through the CMC web interface, RACADM commands, and settings. To restore the chassis configuration, perform the following tasks: 1. Go to the Chassis Configuration Profiles page.
To export a stored profile, perform the following tasks: 1. Go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles → Stored Profiles section, select the required profile and then click Export Copy of Profile. A File Download message is displayed prompting you to open or save the file. 2. Click Save or Open to export the profile to the required location. Editing Chassis Configuration Profiles You can edit chassis configuration profile name of a chassis.
1. To export the chassis configuration profiles as clone.xml file to CIFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC get –f clone.xml –t xml –l // xx.xx.xx.xx/PATH –u USERNAME –p PASSWORD 2. To export the chassis configuration profiles as clone.xml file to NFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC get –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.
Follow these guidelines when you create a .cfg file: • If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various indexes. The parser reads in all of the indexes from the CMC for that group. Any objects within that group are modifications when the CMC is configured. If a modified object represents a new index, the index is created on the CMC during configuration. • You cannot specify a desired index in a .cfg file. Indexes may be created and deleted.
The racadm getconfig -f .cfg command places a comment in front of index objects, allowing you to see the included comments. NOTE: You may create an indexed group manually using the following command: racadm config -g name> • -o -i
NOTE: Anchor is a reserved word and should not be used in the .cfg file. Viewing and Terminating CMC Sessions You can view the number of users currently logged in to iDRAC and terminate the user sessions. NOTE: To terminate a session, you must have Chassis Configuration Administrator privilege. Viewing and Terminating CMC Sessions Using Web Interface To view or terminate a session using Web interface: 1. In the system tree, go to Chassis Overview and click Network → Sessions.
The Advanced Fan Configurations page is displayed. NOTE: If ECM is disabled and all the fans in the chassis do not support ECM, then the Setup tab to access the Advanced Fan Configurations page is not displayed. 2. In the Fans Configuration section, from the Enhanced Cooling Mode drop-down menu select Enable or Disable. For more information about the field descriptions, see the CMC Online Help.
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 Configuring Slot Names Slot names are used to identify individual servers.
To edit a slot name using the CMC Web interface: 1. In the system tree, go to Chassis Overview → Server Overview and then click Setup → Slot Names. The Slot Names page is displayed. 2. In the Slot Name field, edit the slot name. Repeat this step for each slot you want to rename. 3. To use the host name of the server as slot name, select Use Host Name for Slot Name option. This option replaces the static slot names with the host names (or system names) of the server, if it is available.
Setting Description • • Set iDRAC Root Password on Server Insertion Specifies whether a server’s iDRAC root password must be changed to the value provided in the iDRAC Root Password field when the server is inserted. iDRAC Root Password When Set iDRAC Root Password on Server Insertion and QuickDeploy Enabled options are selected, this password value is assigned to a server's iDRAC root user password when the server is inserted into chassis.
Setting Description NOTE: Note the following: • • • • The values of the number of IP addresses that are less than the minimum value required for a server type are grayed out. If you select an option that is lesser than the default value of the number of IP addresses reserved, an error message is displayed warning that reducing the number of IP addresses prevents quick deploy of profiles to higher capacity servers. A warning message is logged in the CMC hardware log (SEL) and an SNMP alert is generated.
3. Setting Description iDRAC IPv6 Prefix Length Specifies the prefix length to be assigned for the IPv6 addresses on the iDRAC. The default value is 64. Use CMC DNS Settings Enables the CMC DNS Server settings ( IPv4 and IPv6) that are propagated to iDRAC when a blade server is inserted in the chassis. Click Save QuickDeploy Settings to save the settings. If you have made changes to the iDRAC network setting, click Apply iDRAC Network Settings to deploy the settings to the iDRAC.
To view current settings for the number of reserved IP addresses and the Use CMC DNS Settings for servers on the chassis using RACADM, use the following command: racadm deploy –q To modify the Use the CMC DNS Settings option to enable quick deploy for servers on the chassis using RACADM, use the following command: racadm deploy -q -e For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.
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. • 2. 3.
Boot Device Description 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. Virtual CD/DVD Boot from a virtual CD/DVD drive or CD/DVD ISO image. The optical drive or ISO image file is located on another computer or disk available on the management network and is attached using the iDRAC GUI console viewer.
To enable boot once for a device, use the cfgServerBootOnce object. For more information about these objects, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals. Configuring Server FlexAddress For information to configure FlexAddress for servers, see Configuring FlexAddress for Server-Level Slots.
– CMC version 4.45 and 12th generation servers with iDRAC and Lifecycle Controller 2 version 1.1 or greater. – CMC version 5.0 and 13th generation servers with iDRAC with Lifecycle Controller 2.00.00.00 or later The server configurations replication feature supports iDRAC and later servers. Earlier generation RAC servers are listed but are grayed out on the main page, and are not enabled to use this feature.
NOTE: If a remote share is available, you can store a maximum of 100 profiles using the CMC extended storage and remote share. For more information see Configuring Network Share Using CMC Web Interface. Removing or disabling the nonvolatile extended storage media prevents access to stored profile and disables the Server Configuration feature. To add or save a profile: 1. Go to the Server Profiles page.
The selected profile is applied to the server(s) and the server(s) may be rebooted immediately, if necessary. For more information, see the CMC Online Help. Related links Accessing Server Profiles Page Importing Profile You can import a server profile that is stored on a management station to CMC. To import a stored profile on a remote file share to CMC: 1. In the Server Profiles page, in the Stored Profiles section, click Import Profile. The Import Server Profile section is displayed. 2.
To edit a stored profile: 1. Go to the Server Profiles page. In the Stored Profiles section, select the required profile and then click Edit Profile. 2. Edit the profile name and description of the server profile as required and then click Save Profile. The Edit Server Profile — section is displayed. For more information, see the CMC Online Help. Deleting Profile You can delete a server profile that is stored on the CMC nonvolatile media (SD Card) or on the Network Share.
Completion Status, Log View, and Troubleshooting To check the completion status of an applied server profile: 1. In the Server Profiles page, note down the Job ID (JID) of the submitted job from the Recent Profile Log section. 2. In the system tree, go to Server Overview and click Troubleshooting → Lifecycle Controller Jobs. Look up the same JID in the Jobs table. 3. Click View Log link to view the results of Lclogview from the iDRAC Lifecycle Controller for the specific server.
NOTE: • If an assigned profile is on the Network Share which is not accessible when a server is inserted in the slot, the LCD displays a message that the assigned profile is not available for Slot . • 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. If the Network Share is not connected, configure the Network Share for the chassis.
3. In the Base Profile Name and Number of Profiles fields, enter the profile name and the number of profiles that you want to save. NOTE: While saving a boot identity profile, the standard ASCII extended character set is supported. However, the following special characters are not supported: ), “, ., *, >, <, \, /, :, |, #, ?, and , 4. Select a MAC address for the base profile from the Virtual MAC Address drop-down and click Save Profile.
3. Click OK to clear the boot identity profile from the selected server. The clear operation disables the IO Identity and persistence policy of the server. On completion of the clear operation, the server is powered off. Viewing Stored Boot Identity Profiles To view the boot identity profiles stored on the network share, go to the Server Profiles page. In the Boot Identity Profiles → Stored Profiles section, select the profile and click View in the View Profile column. The View Settings page is displayed.
NOTE: The virtual MAC Addresses are managed in the vmacdb.xml file in the network share. A hidden lock file (.vmacdb.lock) is added and removed from the network share to serialize boot identity operations from multiple chassis. 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.
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. In the Boot Identity Profiles → Manage Virtual MAC Address Pool section, select the active MAC address(es) that you want to deactivate. 2. Click Deactivate MAC Address(es).
• The chassis power is on. • Servers that support iDRAC. • The LAN interface on the server is enabled. • The iDRAC version is 2.20 or later. • The host system is installed with JRE (Java Runtime Environment) 6 Update 16 or later. • The browser on host system allows pop-up windows (pop-up blocking is disabled). Remote Console can also be launched from the iDRAC Web interface. For more details, see iDRAC User’s Guide.
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. 2.
Related links Configuring SNMP Trap Alert Destinations Configuring Email Alert Settings Configuring SNMP Trap Alert Destinations You can configure the IPv6 or IPv4 addresses to receive the SNMP traps. Configuring SNMP Trap Alert Destinations Using CMC Web Interface To configure IPv4 or IPv6 alert destination settings using CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Alerts → Trap Settings. The Chassis Event Alert Destinations page is displayed. 2.
Table 18. Event Traps Filter Masks 4.
NOTE: CMC uses a default SNMP community string as public. To ensure higher security, it is recommended to change the default community string and set a value which is not blank. You can configure up to four destinations to receive traps alerts. To add more destinations, repeat steps 2–6. NOTE: The commands in steps 2–6 overwrites any existing settings configured for the index specified (1–4). To determine whether an index has previously configured values, type: racadm getconfig -g cfgTraps -i .
4. Enable email alert generation: racadm config -g cfgEmailAlert -o cfgEmailAlertEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destination email addresses. 5. Specify a destination email address to receive the email alerts: racadm config -g cfgEmailAlert -o cfgEmailAlertAddress -i where is a valid email address, and is the index value you specified in step 4. 6.
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 priorities can be added or changed whether or not servers are present in the slots. When a server is moved to a different chassis, it inherits the slot name and priority assigned to the slot it occupies in the new chassis. Its previous slot name and priority remain with the previous chassis. NOTE: CMC users with the Chassis Configuration Administrator privilege can configure power settings.
Privilege Description Configure Users: • • Set iDRAC root password iDRAC reset Server Control Administrator: • • • • • Power on Power off Power cycle Graceful shutdown Server Reboot Test Alert User User can send test alert messages. Debug Command Administrator User can execute system diagnostic commands. Fabric A Administrator User can set and configure the Fabric A IOM, which resides in either slot A1 or slot A2 of the I/O slots.
User Group Privileges Granted 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 Administrator Fabric C Administrator No assigned permissions Table 21.
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. Before you create a CMC local user, verify if any current users exist. You can set user names, passwords, and roles with the privileges for these users. The user names and passwords can be changed using any of the CMC secured interfaces (that is, Web interface, RACADM or WS-MAN).
The "#" character in the command objects indicates that it is a read only object. Also, if you use the racadm config -f racadm.cfg command to specify any number of groups or objects to write, the index cannot be specified. A new user is added to the first available index. This behavior allows more flexibility in configuring a second CMC with the same settings as the main CMC. Adding CMC User Using RACADM To add a new user to the CMC configuration, perform the following: 1. Set the user name. 2.
Configuring Active Directory Users If your company uses the Microsoft Active Directory software, you can configure the software to provide access to CMC, allowing you to add and control CMC user privileges to your existing users in your directory service. This is a licensed feature. NOTE: Using Active Directory to recognize CMC users is supported on the Microsoft Windows 2000 and Windows Server 2003 operating systems. Active Directory over IPv6 and IPv4 is supported on Windows 2008.
Role Group Default Privilege Level Permissions Granted • • • • • • • • • 2 None • • • • • • • • Bit Mask User Configuration Administrator Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator CMC Login User Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Admin
• • 4. Enable Active Directory, enter the root domain name, and the timeout value. If you want the directed call to search the domain controller and global catalog, select the Search AD Server to search (Optional) option and specify the domain controller and global catalog details. Click Apply to save the settings. NOTE: You must apply the settings before continuing. If you do not apply the settings, the settings are lost when you navigate to the next page. 5.
• If DHCP is disabled on CMC or you want manually to input your DNS IP address, type the following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSServer2 Extended Schema Active Directory Overview Using the extended schema solution requires the Active Directory schema extension.
The Association Object allows as many or as few users and/or groups as well as RAC Device Objects. However, the Association Object only includes one Privilege Object per Association Object. The Association Object connects the Users who have Privileges on 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).
The following figure provides an example of Active Directory objects in multiple domains. In this scenario, you have two CMCs (RAC1 and RAC2) and three existing Active Directory users (user1, user2, and user3). User1 is in Domain1, and user2 and user 3 are in Domain2. In this scenario, configure user1 and user 2 with administrator privileges to both CMCs and configure user3 with login privileges to the RAC2 card. To configure the objects for the multiple domain scenario: 1.
• Dell Schema Extender utility • LDIF script file If you use the LDIF script file, the Dell organizational unit is not added to the schema. The LDIF files and Dell Schema Extender are located on your Dell Systems Management Tools and Documentation DVD in the following respective directories: • DVDdrive:\SYSMGMT\ManagementStation\support\OMActiveDirectory_Tools\Remote_Management\LDIF_Files • :\SYSMGMT\ManagementStation\support\OMActiveDirector y_Tools\Remote_Management\Schema Extender To us
Table 25. : delliDRACAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.7.1.2 Description Represents the Dell Association Object. The Association Object provides the connection between the users and the devices. Class Type Structural Class SuperClasses Group Attributes dellProductMembers dellPrivilegeMember Table 26. : dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines the privileges (Authorization Rights) for CMC device.
Assigned OID/Syntax Object Identifier Single Valued Description: List of dellPrivilege objects that belong to this attribute. OID: 1.2.840.113556.1.8000.1280.1.1.2.1 Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellProductMembers FALSE Description: List of dellRacDevices objects that belong to this role. This attribute is the forward link to the dellAssociationMembers backward link. Link ID: 12070 OID: 1.2.840.113556.1.8000.1280.1.1.2.2 Distinguished Name: (LDAPTYPE_DN 1.3.
Assigned OID/Syntax Object Identifier Single Valued Description: The Current Schema Version is used to update the schema. OID: 1.2.840.113556.1.8000.1280.1.1.2.12 Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.905) Attribute: dellRacType TRUE Description: This attribute is the Current Rac Type for the dellRacDevice object and the backward link to the dellAssociationObjectMembers forward link. OID: 1.2.840.113556.1.8000.1280.1.1.2.13 Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.
Creating RAC Device Object To create RAC device object: 1. In the Console Root (MMC) window, right-click a container. 2. Select New → Dell Remote Management Object. The New Object window is displayed. 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.
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. 2.
9. Log in to the CMC Web interface. 10. Select Chassis in the system tree, click the Network tab, then click the Network subtab. The Network Configuration page is displayed. 11. If Use DHCP for CMC Network Interface IP Address, is enabled, select one of the following: • Select Use DHCP to Obtain DNS Server Addresses option to enable the DNS server addresses to be obtained automatically by the DHCP server.
• If DHCP is enabled on CMC and you want to use the DNS address obtained automatically by the DHCP server, type the following command: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1 • If DHCP is disabled on CMC, or if DHCP is enabled but you want to specify your DNS IP address manually, type following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSSe
To authenticate a user: 1. Optionally bind to the Directory Service. The default is an anonymous bind. 2. Search for the user based upon their user login. The default attribute is uid. If more than one object is found, then the process returns an error. 3. Unbind and perform a bind with the user's DN and password. If the bind fails, then the login fails. If these steps succeed, the user is authenticated. Authorization of LDAP Users To authorize a user: 1.
Configuring Generic LDAP Directory Service Using RACADM To configure the LDAP directory service, use the objects in cfgLdap and cfgLdapRoleGroup RACADM groups. There are many options to configure LDAP logins. In most of the cases, some options can be used with their default settings. NOTE: It is highly recommended to use the racadm testfeature -f LDAP command to test the LDAP settings for first time setups. This feature supports both IPv4 and IPv6.
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.
CMC • CMC must have firmware version 2.10 or later. • Each CMC must have an Active Directory account. • CMC must be a part of the Active Directory domain and Kerberos Realm. Prerequisites For Single Sign-On Or Smart Card Login The pre-requisites to configure SSO or Smart Card logins are: • Setup the kerberos realm and Key Distribution Center (KDC) for Active Directory (ksetup). • A robust NTP and DNS infrastructure to avoid issues with clock drift and reverse lookup.
Configuring Browser For SSO Login Single Sign-On (SSO) is supported on Internet Explorer versions 6.0 and later and Firefox versions 3.0 and later. NOTE: The following instructions are applicable only if CMC uses Single Sign-On with Kerberos authentication. Internet Explorer To configure Internet Explorer for Single Sign-On: 1. In the Internet Explorer, select Tools → Internet Options. 2. On the Security tab, under Select a zone to view or change security settings, select Local Intranet. 3.
2. NOTE: All command line out-of-band interfaces including secure shell (SSH), Telnet, Serial, and remote RACADM remain unchanged if this option is selected. Click Apply. The settings are saved. You can test the Active Directory using Kerberos authentication using the RACADM command: testfeature -f adkrb -u @ where is a valid Active Directory user account. A command success indicates that CMC is able to acquire Kerberos credentials and access the user's Active Directory account.
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.
To fix this issue, download hotfix 824810 from support.microsoft.com. You can also see the Microsoft Knowledge Base article 824810 for more information. Using SSH With CMC SSH is a command line session that includes the same capabilities as a Telnet session, but with session negotiation and encryption to improve security. The CMC supports SSH version 2 with password authentication. SSH is enabled on the CMC by default. NOTE: CMC does not support SSH version 1.
Configure Public Key Authentication over SSH You can configure up to 6 public keys that can be used with the service username over SSH interface. Before adding or deleting public keys, be sure to use the view command to see what keys are already set up so that a key is not accidentally overwritten or deleted. The service username is a special user account that can be used when accessing the CMC through SSH.
• Save the public key to a file to upload later. • Copy and paste the text from the Public key for pasting window when adding the account using the text option. Generating Public Keys for Systems Running Linux The ssh-keygen application for Linux clients is a command line tool with no graphical user interface. Open a terminal window and at the shell prompt type: ssh-keygen –t rsa –b 2048 –C testing where, –t must be rsa. –b specifies the bit encryption size between 2048 and 4096.
Perform the steps in the following subsections to configure the required type of terminal software. Configuring Linux Minicom Minicom is a serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0. Other Minicom versions may differ slightly but require the same basic settings. See the information in the Required Minicom Settings section to configure other versions of Minicom. Configuring Minicom Version 2.
• 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. CAUTION: When executed from the CMC serial console, the connect -b option stays connected until the CMC resets. This connection is a potential security risk.
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 iDRAC User’s Guide on dell.com/support/manuals). Serial communication in the BIOS is OFF by default. To redirect host text console data to Serial over LAN, you must enable console redirection through COM1. To change the BIOS setting: 1. Boot the managed server. 2.
# #boot=/dev/sda default=0 timeout=10 #splashimage=(hd0,2)/grub/splash.xpm.gz serial --unit=1 --speed=57600 terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp) root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600 initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 initrd /boot/initrd-2.4.9-e.3.
ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it.
12 Using FlexAddress and FlexAdress Plus Cards This section provides information about FlexAddress and FlexAddress Plus cards, how to configure and use these cards. Related links About Flexaddress About FlexAddress Plus FlexAddress and FlexAddress Plus Comparison About Flexaddress If a server is replaced, the FlexAddress for the slot remains the same for the given server slot.
FlexAddress and FlexAddress Plus Comparison FlexAddress has 208 addresses divided into 16 server slots, thus each slot is allocated with 13 MACs. FlexAddress Plus has 2928 addresses divided into 16 server slots, thus each slot is allocated with 183 MACs. The following table shows the provision of the MAC addresses in both the features. Fabric A Fabric B Fabric C iDRAC Management Total MACs FlexAddress 4 4 4 1 13 FlexAddress Plus 60 60 60 3 183 Figure 4.
Component PowerEdgeM600/M605 LAN on motherboard (LOM) iDRAC CMC Minimum Required Version • • • • PowerEdge M905 PowerEdge M610 PowerEdge M710 PowerEdge M710hd • • Boot code firmware 4.4.1 or later iSCSI boot firmware 2.7.11 or later • • Version 1.50 or later for PowerEdge xx0x systems Version 2.10 or later for PowerEdge xx1x systems Version 1.10 or later NOTE: Any system ordered after June 2008 has the correct firmware versions.
Verifying FlexAddress Activation Use the following RACADM command to verify the SD feature card and its status: racadm featurecard -s Table 34. 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 command returns the following status message if it is successfully deactivated: feature FlexAddress is deactivated on the chassis successfully. 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.
where, = 1 to 16 = A, B, C = 0 or 1 0 is disable and 1 is enable. Additional FlexAddress Configuration for Linux When changing from a server-assigned MAC ID to chassis-assigned MAC ID on Linux-based operating systems, additional configuration steps may be required: • SUSE Linux Enterprise Server 9 and 10 — You may need to run Yet Another Setup Tool (YAST) on the Linux system to configure the network devices and then restart the network services.
Viewing Basic WWN/MAC Address Information Using Web Interface To view WWN/MAC Address information for each server slot or all servers in a chassis, in the basic mode: 1. Click Server Overview → Properties → WWN/MAC. The WWN/MAC Summary page displays the WWN/MAC Address Information. Alternatively, click Server Overview → Slot → Setup → FlexAddress to view the WWN/MAC Address information for a specific server slot. The FlexAddress page is displayed. 2.
8. In the WWN/MAC Addresses field, enter the MAC address to view only the slots associated with the specific MAC address. Alternately, partially enter the MAC address entries to view the associated slots. For example, enter 4A to view the slots with MAC addresses that contain 4A. 9. From the Partition Status drop-down menu, select the status of the partitions to display servers with the selected partition status.
Fabric Configuration The Fabric Configuration section displays the type of Input/Output fabric that is installed for Fabric A, Fabric B, and Fabric C. A green check mark indicates that the fabric is enabled for FlexAddress. The FlexAddress feature is used to deploy chassis assigned and slot persistent WWN/MAC addresses to various fabrics and slots within the chassis. This feature is enabled on a per fabric and per slot basis. NOTE: For more information on the FlexAddress feature, see About Flexaddress.
Situation Command Output Guest user attempts to set FlexAddress on slots or fabrics. $racadm setflexaddr [-f ] $racadm setflexaddr [-i ] ERROR: Insufficient user privileges to perform operation Deactivating FlexAddress feature with chassis powered ON. $racadm feature -d -c flexaddress ERROR: Unable to deactivate the feature because the chassis is powered ON Guest user tries to deactivate the feature on the chassis.
Dell does NOT warrant that the functions of the Software meets your requirements or that operation of the Software is uninterrupted or error free. You assume responsibility for selecting the Software to achieve your intended results and for the use and results obtained from the Software.
13 Managing I/O 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.
Figure 5. Rear View of a Chassis, Showing the Location of the IOMs Bank 1 (Slots A1, B1, C1) 1 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. However, an Ethernet MC connected to both an Ethernet switch and an Ethernet pass-through IOM installed in the same IOM group is a valid connection.
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.
3. In the Select Port drop-down, select the required port number for the selected IOM and click Show Sessions. The FCoE Session Information section displays the FCoE session information for the switch. NOTE: This section displays FCoE information, only if active FCoE sessions are running on the I/O Aggregator.
NOTE: The IP address set on the IOMs from CMC is not saved to the switch's permanent startup configuration. To save the IP address configuration permanently, you must enter the connect switch-n command, or racadm connect switch -n RACADM command, or use a direct interface to the IOM GUI to save this address to the startup configuration file. NOTE: The SNMP community string can have any printable character whose ASCII value is the range, 33–125. 4. Click Apply.
To update the IOM Infrastructure device software, in the CMC Web interface: 1. Go to Chassis Overview → I/O Module Overview → Update. The IOM Firmware Update page is displayed. Alternatively, go to any of the following: • • • Chassis Overview → Update Chassis Overview → Chassis Controller → Update Chassis Overview → iKVM → Update The Firmware Update page is displayed, which provides a link to access the IOM Firmware Update page. 2.
CMC reports information about the flex modules in the IOA by reading the flex module information during its initial negotiation with the IOA. The reading happens by sending XML commands during the initial negotiation. CMC saves the flex module information in the shared memory. There can be a maximum of two flex modules: • FlexIO Module 1 • FlexIO Module 2 All IOM software that support the command revision 4 support the Flex IO module information XML command.
Configuring Management VLAN on IOMs Using Web Interface You can manage the IO Aggregator in-band through a VLAN. This VLAN must be deployed prior to use. CMC allows in-band management VLAN deployment. The switch’s in-band management VLAN requires the following basic configuration of settings to be applied: • Enable • VLAN ID • Priority NOTE: Configuring the management VLAN on the Vlan Settings page requires Chassis Configuration privileges.
3. In the Step 2: Specify Port Range section, select the range of fabric ports to be assigned to the selected IOM(s). For information about the fields, see CMC Online Help 4. Select the Select or Deselect All option to apply the changes to all or no IOMs. or Select the check box for the specific slots to select the required IOMs. 5. In the Step 3: Edit VLANs section, type the VLAN IDs for the IOMs. Provide VLAN IDs in the range 1-4094. VLAN IDs can be typed as a range or separated by a comma.
5. In the Step 3: Edit VLANs section, select Add Tagged VLANs in the drop down list and click Apply. The tagged VLANs are assigned to the selected IOMs. The operation successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field. 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.
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. Enabling or Disabling LED Blinking for IOMs For information to enable LED blinking for IOM(s), see Configuring LEDs to Identify Components on the Chassis.
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.
NOTE: The ports on the control panel on the front of the chassis are designed specifically for the iKVM, which is optional. If you do not have the iKVM module, you cannot use the front control panel ports. iKVM Connection Precedences Only one iKVM connection is available at a time. The iKVM assigns an order of precedence for each type of connection so that when there are multiple connections, only one connection is available while the others are disabled. The order of precedence for iKVM connections is: 1.
Navigation Basics Table 36. : OSCAR Keyboard and Mouse Navigation Key or Key Sequence Result • Any of these key sequences opens OSCAR depending on the Invoke OSCAR settings. You can enable two, three, or all of these key sequences by selecting boxes in the Invoke OSCAR section of the Main dialog box, and then clicking OK. • • • - - - - Opens the Help screen for the current dialog box.
Feature Purpose Menu Changes the server listing between numerically by slot or alphabetically by name. Security • • Flag Changes display, timing, color, or location of the status flag. Language Changes the language for all OSCAR screens. Broadcast Sets up to simultaneously control multiple servers through keyboard and mouse actions. Scan Sets up a custom scan pattern for up to 16 servers.
Flag Description Flag type by name. Flag indicating that the user is disconnected from all systems. Flag indicating that Broadcast mode is enabled. To set the display of the status flag: 1. Press to launch OSCAR. The Main dialog box appears. 2. Click Setup and then Flag. The Flag dialog box appears. 3. Select Displayed to always display the flag or Displayed and Timed to display the flag for only five seconds after switching.
NOTE: The USB connections are solely for supported keyboard, mouse, and USB hubs. iKVM does not support data transmitted from other USB peripherals. Viewing and Selecting Servers When you launch OSCAR, the Main dialog box appears. Use the Main dialog box to view, configure, and manage servers through the iKVM. You can view the servers by name or by slot. The slot number is the chassis slot number the server occupies. The Slot column indicates the slot number in which a server is installed.
dialog box is displayed after is pressed) and if you press the key sequences before that time has elapsed, the OSCAR interface does not display. Related links Configuring Soft Switching Soft Switching to a Server Configuring Soft Switching To configure OSCAR for soft switching: 1. Press to launch the OSCAR interface. The Main dialog box appears. 2. Click Setup and then Menu. The Menu dialog box appears. 3. Select Name or Slot for the Display/Sort Key. 4.
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.
Setting Automatic Logout You can set OSCAR to automatically log out of a server after a period of inactivity. 1. In the Main dialog box, click Setup and then Security. 2. In the Inactivity Time field, enter the length of time you want to stay connected to a server before it automatically disconnects you. 3. Click OK. Removing Password Protection From the Console To remove password protection from your console: 1. In the Main dialog box, click Setup and then Security. 2.
Changing the Language Use the Language dialog box to change the OSCAR text to display in any of the supported languages. The text immediately changes to the selected language on all of the OSCAR screens. To change the OSCAR language: 1. Press . The Main dialog box appears. 2. Click Setup and then Language. The Language dialog box appears. 3. Select the required language and click OK.
Removing Server from Scan List To remove a server from the Scan list: 1. 2. In the Scan dialog box, do one of the following: • Select the server to be removed. • Double-click the server name or slot. • Click Clear to remove all servers from the Scan list. Click Add/Remove, and then click OK. Starting the Scan Mode To start the scan mode: 1. Press . 2. Click Commands. The Main dialog box is displayed. The Command dialog box is displayed. 3. Select the Scan Enable option. 4.
3. Enable mouse and/or keyboard for the servers that are to receive the broadcast commands by selecting the boxes. or Press the up or down arrow keys to move the cursor to a target server. Then, press to select the keyboard box and/or to return to the Main dialog box. 7.
Enabling Access to iKVM from the Dell CMC Console To enable access to the CMC CLI from iKVM using the CMC Web interface, in the system tree, go to Chassis Overview → iKVM and click Setup tab. Select the Allow access to CMC CLI from iKVM option, and click Apply to save the setting.
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 poweroptimized components throughout the enclosure.
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 redundancy Executing Power Control Operations Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis.
health is marked non-critical. If the smaller grid cannot support the total chassis power allocations, then grid redundancy status is reported as No Redundancy and Chassis health is displayed as Critical. Power Supply Redundancy Policy The power supply redundancy policy is useful when redundant power grids are not available, but you may want to be protected against a single PSU failure bringing down your servers in a modular enclosure. The highest capacity PSU is kept in online reserve for this purpose.
Extended Power Performance (EPP) Extended Power Performance mode enables allocation of 30% additional power in a configuration of six Power Supply Units (PSUs), to the M1000e chassis, than the redundant power in a Grid Redundancy configuration using 3000 W AC PSUs. However, the power allocated to servers is automatically reduced in the event of an AC grid failure or a PSU failure, so that the servers are not powered off.
Dynamic Power Supply Engagement Dynamic Power Supply Engagement (DPSE) mode is disabled by default. DPSE saves power by optimizing the power efficiency of the PSUs supplying power to the chassis. This also increases the PSU life, and reduces heat generation. CMC monitors total enclosure power allocation, and moves the PSUs to Standby state. Moving the PSUs to standby state: • Enables delivery of the total power allocation of the chassis through fewer PSUs.
Three PSUs No Redundancy Disabled Grid Redundancy In Grid Redundancy mode with six PSUs, all six PSUs are active. The three PSUs on the left must connect to one input power grid, while the three PSUs on the right connect to another power grid. CAUTION: To avoid a system failure and for Grid Redundancy to work effectively, there must be a balanced set of PSU properly cabled to separate grids.
CMC allocates power to the CMC infrastructure and the servers in the chassis. CMC infrastructure consists of components in the chassis, such as fans, I/O modules, and iKVM (if present). The chassis may have up to 16 servers that communicate to the chassis through the iDRAC. For more information, see the iDRAC User’s Guide at support.dell.com/manuals. iDRAC provides CMC with its power envelope requirements before powering up the server.
may be not be allocated enough power to run at their maximum performance or they may not even power on at all, depending on how low the system input power cap is set and the server power requirements. If an administrator manually powers on the low priority server modules before the higher priority ones, then the low priority server modules are the first modules to have their power allocation lowered down to the minimum value, in order to accommodate the higher priority servers.
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.
New Server Engagement Policy If a new server that is turned on exceeds the power available for the chassis, CMC may decrease the power to the low-priority servers. This allows more power for the new server. This happens if: • The administrator had configured a power limit for the chassis that is below the power required for full power allocation to the servers. • Insufficient power is available for the worst-case power requirement of all servers in the chassis.
The following table lists the SEL entries that are related to power supply changes: Table 41. SEL Events for Power Supply Changes Power Supply Event System Event Log (SEL) Entry Insertion Power supply is present. Removal Power supply is absent. Grid or Power Supply Redundancy lost Power supply redundancy is lost. Grid or Power Supply Redundancy regained The power supplies are redundant. Input power received The input power for power supply has been restored.
Configuring power budget and redundancy You can configure the power budget, redundancy, and dynamic power of the entire chassis (chassis, servers, I/O modules, iKVM, CMC, and power supplies), which uses six power supply units (PSUs). The power management service optimizes power consumption and re-allocates power to different modules based on the requirement.
In maximum power conservation mode, all servers start functioning at their minimum power levels, and all subsequent server power allocation requests are denied. In this mode, the performance of powered on servers may be degraded. Additional servers cannot be powered on, regardless of server priority. The system is restored to full performance when the maximum conservation mode is cleared.
When external power management is enabled, Dell OpenManage Power Center manages: • Server Power of supported M1000e servers • Server Priority of supported M1000e servers • System Input Power Capacity • 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 pri
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.
• 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. Logging to one or more remote syslog hosts must be enabled, otherwise power consumption is logged. This can be done either through the Web interface or the RACADM CLI.
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. The restoration to the previous power state is the default behavior.
5. Click OK to perform the power management action (for example, cause the server to 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.
Subsystem RACADM Command General System/RAC information getsysinfo Session information getssinfo Sensor information getsensorinfo Switches information (IO Module) getioinfo Mezzanine card information (Daughter card) getdcinfo All modules information getmodinfo Power budget information getpbinfo KVM information getkvminfo NIC information (CMC module) getniccfg Redundancy information getredundancymode Trace log information gettracelog RAC event log gettraclog System event log getsel
• Problem: The PSU state is displayed as Failed (No AC), even when an AC cable is connected and the power distribution unit is producing good AC output. – Resolution A: Check and replace the AC cable. Check and confirm that the power distribution unit providing power to the power supply is operating as expected. If the failure still persists, call Dell customer service for replacement of the power supply. – Resolution B: Check that the PSU is connected to the same voltage as the other PSUs.
Related links Configuring CMC To Send Alerts Viewing Event Logs You can view hardware and CMC logs for information on system-critical events that occur on the managed system. Related links Viewing Hardware Log Viewing CMC Log and Enhanced Chassis Log Viewing Hardware Log CMC generates a hardware log of events that occur on the chassis. You can view the hardware log using the Web interface and remote RACADM. NOTE: To clear the hardware log, you must have Clear Logs Administrator privilege.
and Events option in the General Settings page. To enable or disable the feature using RACADM, use the cfgRacTuneEnhancedLog object. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals. NOTE: To clear the CMC log, you must have Clear Logs Administrator privilege. Related links Viewing Event Logs Viewing CMC Logs Using the Web Interface You can view, save, and clear the CMC log.
Resetting Components You can reset the active CMC, reset iDRAC without rebooting the operating system, or to virtually reseat servers causing them to behave as if they were removed and reinserted. If the chassis has a standby CMC, resetting the active CMC causes a failover and the standby CMC becomes active. NOTE: To reset components, you must have Debug Command Administrator privilege. To reset the components using the CMC Web interface: 1.
• Network connectivity problem that prevents CMC from communicating with any of the configured NTP servers. • DNS problem, preventing any of the NTP server host names from being resolved. To troubleshoot NTP related problems, check the CMC Trace Log. This log contains error messages for NTP related failures.
Component iKVM Server IOM (Common) IOM (Pass through) LED Color, Blinking Pattern Status Green, dark Powered off Blue, glowing steadily Active Blue, blinking User-enabled module identifier 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 Gre
Component LED Color, Blinking Pattern Status Fan Green, glowing steadily Fan working Green, blinking Not used Green, dark Powered off 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 D
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. 3. Press . A core memory failure displays an error message every 5 seconds. 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 10. Password Reset Jumper Location Table 44. 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 11.
The up, down, left, and right arrow buttons change the selected menu items or icons on the screen. The selected item is shown with a light blue background or border. When messages displayed on the LCD screen are longer than what fits on the screen, use the left and right arrow buttons to scroll the text left and right. The icons described in the following table are used to navigate between LCD screens. Table 45.
Main Menu From the Main menu, you can navigate to one of the following screens: • LCD Setup Menu — select the language to use and the LCD screen that displays when no one is using the LCD. • Server — displays status information for servers. • Enclosure — displays status information for the chassis. Use the up and down arrow buttons to highlight an item. Press the center button to activate your selection.
Graphical Server Status Screen The Graphical Server Status screen displays icons for each server installed in the chassis and indicates the general health status for each server.
Enclosure Status Screen The Enclosure Status screen displays information and error messages about the enclosure. For messages that can appear on this screen, see LCD Error Messages. Use the up and down arrow keys to move through messages. Use the left and right arrow keys to scroll messages that do not fit on the screen. Highlight the Back icon and press the center button to return to the Enclosure Status screen.
Figure 12. Removing and Installing LCD Module 1 cable cover 2 LCD module 3 ribbon cable 4 hinges (2) 5 screws (2) Table 46. LCD Hardware Troubleshooting Items Symptom Issue Recovery Action Alert screen message CMC Not Responding and LED is blinking amber. Loss of communication from CMC to the LCD front panel. Check that CMC is booting; then, reset CMC using GUI or RACADM commands. Alert screen message CMC Not Responding and LED is solid amber or is off.
LCD screen message No CMC Found. No CMC is present in the chassis. Insert a CMC into the chassis or reseat existing CMC if present. Front Panel LCD Messages This section contains two subsections that list error and status information that is displayed on the front panel LCD. Error messages on the LCD have a format that is similar to the System Event Log (SEL) viewed from the CLI or Web interface.
Severity Message Cause Critical All event logging is disabled. The Chassis/Enclosure cannot store events to the logs. This usually indicates a problem with the control panel or control panel cable. Warning Log is full. Chassis has detected that only one more entry can be added to the CEL (hardware log) before it is full. Warning Log is almost full. Chassis event log is 75% full. Table 49.
Severity Message Cause Warning The system board ambient temperature is greater than the upper warning threshold. Server temperature is getting warm. Critical The system board ambient temperature is greater than the upper critical threshold. Server temperature is getting too hot. Critical The system board Current Latch current is outside of the allowable range Current crossed a failing threshold. Critical The system board battery failed. CMOS battery is not present or has no voltage.
Severity Message Cause received from Host) and the action is set to power cycle. Critical Log is full. The SEL device detects that only one entry can be added to the SEL before it is full. Warning Persistent correctable memory errors detected on a memory device at location . Warning Persistent correctable memory error rate has increased for a memory device at location . Correctable ECC errors reach a critical rate.
Severity Message Cause Critical Failed to program virtual MAC address on a component at bus device function . Flex address could be programmed for this device. Critical Device option ROM on mezzanine card failed to support Link Tuning or FlexAddress. Option ROM does not support Flex address or linking tuning. Critical Failed to get Link Tuning or FlexAddress data from iDRAC. NOTE: For information on other server related LCD messages, see "Server User Guide".
CMC redundancy mode Non-Redundant or Redundant. PSU redundancy mode Non-Redundant, AC Redundant, or DC Redundant. Table 56. Fan Status Item Description Name/Location Example: Fan1, Fan2, and so on. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. RPM Current fan speed in RPM. Table 57. PSU Status Item Description Name/Location Example: PSU1, PSU2, and so on.
Service Tag The factory-assigned service tag. Part Number The Manufacturer part number. Firmware Version iKVM firmware version. Hardware Version iKVM hardware version. NOTE: This information is dynamically updated Table 60. 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.
The information is displayed only if iDRAC has completed booting. For more information on this feature, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide at dell.com/support/manuals.
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 RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) This message indicates that another command must be issued only after CMC completes the reset.
To ensure that the CSR matches the registered DNS CMC name: 1. In the CMC Web interface, go to the System tree, click Chassis Overview. 2. Click the Network tab, and then click Network. The Network Configuration page appears. 3. Select the Register CMC on DNS option. 4. Type the CMC name in the DNS CMC Name field. 5. Click Apply Changes. For more information about generating CSRs and issuing certificates, see Obtaining Certificates.
Yes. The domain forest function level must be in Native mode or Windows 2003 mode. In addition, the groups among Association Object, RAC user objects, and RAC Device Objects (including Association Object) must be universal groups. Can these Dell-extended objects (Dell Association Object, Dell RAC Device, and Dell Privilege Object) be in different domains? The Association Object and the Privilege Object must be in the same domain.
Yes it does. Before installing the SD card into the CMC module, verify the write protection latch is in the unlock position. The FlexAddress feature cannot be activated if the SD card is write protected. In this situation, the $racadm feature -s command returns this message: No features active on the chassis. ERROR: read only file system What happens if there is no SD card in the active CMC module? The $racadm featurecard -s command returns this message: No feature card inserted.
racadm config -g cfgKVMInfo -o cfgKVMAccesToCMCEnable 1 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.
• Entering an invalid subnet mask. • Setting the default gateway to an address that is not on a network that is directly connected to the switch. For more information on IOM network settings, see the Dell PowerConnect M6220 Switch Important Information document and the Dell PowerConnect 6220 Series Port Aggregator White Paper at dell.com/support/manuals. Single Sign On Though CMC is setup to allow Single Sign-On (SSO), the browser displays a blank page.
19 Use Case Scenarios This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Chassis Basic Configuration and Firmware Update This scenario guides you to perform the following tasks: • Bring up the chassis with basic configurations. • Verify that hardware is being detected by CMC without any errors. • Update firmware for CMC, IOMs, and server components. 1. CMC is pre-installed on your chassis and hence no installation is required.
Update Firmware for Management Consoles Without Servers Downtime You can update firmware for management consoles for CMC, iDRAC and Lifecycle Controller without downtime on the servers: 1. In a scenario, where both the primary and the standby CMC is present, you can update the CMC firmware without servers or IOMs downtime. 2. To update firmware on the primary CMC, see the Updating Firmware section. When you update firmware on the primary CMC, the standby CMC takes on the role of the primary CMC.
– Server Based Power Management (SBPM) – Redundancy Policy: Power Supply Redundancy or No Redundancy – Max Power Conservation Mode (MPCM). – Dynamic Power Supply Engagement (DPSE). – System Input Power Cap is set to value less than or equal to 13300W or (45381 BTU/h) . • The chassis does not have six 3000W PSUs or all the PSUs do not support EPP , the EPP option is grayed out and not available for selection.
Max Power Conservation Mode (MPCM) can be enabled on 3000W AC PSU configuration, using RACADM CLI with existing interface. There is no change to RACADM CLI interface for enabling MPCM, while EPP is enabled. Scenario 5: Trying to enable EPP from the disabled start condition, when other power configuration settings are set.
