Dell Chassis Management Controller Version 1.10 Manual

Dell Chassis Management Controller Version

1.1 for PowerEdge FX2/FX2s User's Guide

Notes, Cautions, and Warnings

NOTE: A NOTE indicates important information that helps you make better use of your computer.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

2014 - 12

Rev. A00

Contents

1 Overview............................................................................................................... 11

Key Features.........................................................................................................................................12

What Is New In This Release......................................................................................................... 12

Management Features...................................................................................................................12

Security Features............................................................................................................................13

Chassis Overview.................................................................................................................................13

Supported Remote Access Connections............................................................................................15

Supported Platforms........................................................................................................................... 16

Supported Web Browsers....................................................................................................................16

Managing Licenses ............................................................................................................................. 16

Types of Licenses...........................................................................................................................16

Acquiring Licenses.........................................................................................................................16

License Operations........................................................................................................................16

Licensable Features In CMC.......................................................................................................... 17

License Component State or Condition and Available Operations............................................ 18

Viewing Localized Versions of the CMC Web Interface.................................................................... 19

Supported Management Console Applications................................................................................. 19

How to Use this User's Guide............................................................................................................. 19

Other Documents You May Need...................................................................................................... 19

Accessing documents from Dell support site....................................................................................20

2 Installing and Setting Up CMC.........................................................................22

Installing CMC Hardware....................................................................................................................22

Checklist To Set up Chassis.......................................................................................................... 22

Using Remote Access Software From a Management Station....................................................24

Remote RACADM Installation.......................................................................................................26

Installing Remote RACADM on a Windows Management Station...............................................27

Installing Remote RACADM on a Linux Management Station.....................................................27

Uninstalling Remote RACADM From a Linux Management Station............................................27

Configuring a Web Browser..........................................................................................................28

Downloading and Updating CMC Firmware................................................................................29

Setting Chassis Physical Location and Chassis Name................................................................. 29

Setting Date and Time on CMC....................................................................................................29

Configuring LEDs to Identify Components on the Chassis........................................................ 30

Configuring CMC Properties........................................................................................................ 30

Configuring Front Panel................................................................................................................ 31

Configuring Chassis Management at Server Mode............................................................................31

Configuring Chassis Management at Server Using CMC Web Interface.................................... 31

Configuring Chassis Management at Server Mode Using RACADM...........................................32

3 Logging in to CMC..............................................................................................33

Configure Public Key Authentication Over SSH.................................................................................33

Generating Public Keys for Systems Running Windows..............................................................33

Generating Public Keys for Systems Running Linux.................................................................... 34

Accessing CMC Web Interface...........................................................................................................34

Logging Into CMC as a Local User, Active Directory User, or LDAP User........................................ 35

Logging in to CMC Using a Smart Card.............................................................................................36

Logging Into CMC Using Single Sign-on........................................................................................... 36

Logging In To CMC Using Serial, Telnet, Or SSH Console................................................................37

Logging in to CMC Using Public Key Authentication........................................................................ 37

Multiple CMC Sessions....................................................................................................................... 38

4 Updating Firmware............................................................................................ 39

Signed CMC Firmware Image.............................................................................................................39

Downloading CMC Firmware.............................................................................................................40

Viewing Currently Installed Firmware Versions.................................................................................40

Viewing Currently Installed Firmware Versions Using CMC Web Interface............................... 40

Viewing Currently Installed Firmware Versions Using RACADM.................................................40

Updating the CMC Firmware..............................................................................................................40

Updating CMC Firmware Using Web Interface............................................................................ 41

Updating CMC Firmware Using RACADM.................................................................................... 41

Updating the CMC Using DUP........................................................................................................... 42

Updating Chassis Infrastructure Firmware.........................................................................................42

Updating Chassis Infrastructure Firmware Using CMC Web Interface.......................................42

Updating Chassis Infrastructure Firmware Using RACADM........................................................ 43

Updating Server iDRAC Firmware.......................................................................................................43

Updating Server iDRAC Firmware Using Web Interface.............................................................. 43

Updating Server Component Firmware....................................................................................... 43

Enabling Lifecycle Controller....................................................................................................... 46

Choosing Server Component Firmware Update Type Using CMC Web Interface.................... 47

Filtering Components for Firmware Updates...............................................................................47

Viewing Firmware Inventory......................................................................................................... 47

Saving Chassis Inventory Report Using CMC Web Interface...................................................... 49

Configuring Network Share Using CMC Web Interface..............................................................49

Lifecycle Controller Job Operations............................................................................................50

5 Viewing Chassis Information and Monitoring Chassis and

Component Health................................................................................................56

Viewing Chassis and Component Summaries...................................................................................56

Chassis Graphics........................................................................................................................... 56

Selected Component Information................................................................................................57

Viewing Server Model Name and Service Tag............................................................................. 58

Viewing Chassis Summary..................................................................................................................58

Viewing Chassis Controller Information and Status..........................................................................58

Viewing Information and Health Status of All Servers.......................................................................58

Viewing Information and Health Status of the IOMs.........................................................................59

Viewing Information and Health Status of Fans................................................................................ 59

Configuring Fans...........................................................................................................................60

Viewing Front Panel Properties.......................................................................................................... 60

Viewing KVM Information and Health Status.....................................................................................60

Viewing Information and Health Status of Temperature Sensors.....................................................61

6 Configuring CMC................................................................................................62

Enabling or Disabling DHCP for the CMC Network Interface Address............................................ 62

Enabling the CMC Network Interface................................................................................................ 63

Enabling or Disabling DHCP for DNS IP Addresses...........................................................................64

Setting Static DNS IP addresses..........................................................................................................64

Viewing and Modifying CMC Network LAN Settings.........................................................................64

Viewing and Modifying CMC Network LAN Settings Using CMC Web Interface.......................65

Viewing and Modifying CMC Network LAN Settings Using RACADM........................................ 65

Configuring DNS Settings (IPv4 and IPv6)..........................................................................................65

Configuring Auto Negotiation, Duplex Mode, and Network Speed (IPv4 and IPv6)........................66

Configuring Management Port 2....................................................................................................... 66

Configuring Management Port 2 Using CMC Web Interface......................................................66

Configuring Management Port 2 Using RACADM............................................................................. 67

Configuring Services........................................................................................................................... 67

Configuring Services Using RACADM.......................................................................................... 68

Configuring CMC Extended Storage Card.........................................................................................68

Setting Up Chassis Group...................................................................................................................69

Adding Members To Chassis Group.............................................................................................69

Removing a Member from the Leader......................................................................................... 70

Disbanding a Chassis Group.........................................................................................................70

Disabling an Individual Member at the Member Chassis.............................................................70

Launching the Web page of a Member Chassis or Server........................................................... 71

Propagating Leader Chassis Properties to Member Chassis........................................................71

Synchronizing a New Member With Leader Chassis Properties..................................................72

Server Inventory for MCM group.................................................................................................. 72

Saving Server Inventory Report.....................................................................................................72

Configuring Multiple CMCs Using RACADM......................................................................................73

Parsing Rules..................................................................................................................................73

Modifying the CMC IP Address..................................................................................................... 75

7 Configuring Servers............................................................................................76

Configuring Slot Names......................................................................................................................76

Configuring iDRAC Network Settings.................................................................................................77

Configuring iDRAC QuickDeploy Network Settings.................................................................... 77

QuickDeploy IP Address Assignments For Servers......................................................................80

Modifying iDRAC Network Settings for Individual Server iDRAC................................................80

Modifying iDRAC Network Settings Using RACADM....................................................................81

Configuring iDRAC VLAN Tag Settings.........................................................................................81

Configuring iDRAC VLAN Tag Settings Using Web Interface...................................................... 81

Configuring iDRAC VLAN Tag Settings Using RACADM..............................................................82

Setting First Boot Device.....................................................................................................................82

Setting First Boot Device For Multiple Servers Using CMC Web Interface................................. 83

Setting First Boot Device For Individual Server Using CMC Web Interface................................ 83

Setting First Boot Device Using RACADM....................................................................................84

Configuring Sled Network Uplink.......................................................................................................84

Deploying Remote File Share............................................................................................................. 84

Configuring Server FlexAddress..........................................................................................................85

Configuring Profile Settings Using Server Configuration Replication.............................................. 85

Accessing Profile Page..................................................................................................................86

Managing Stored Profiles..............................................................................................................86

Adding or Saving Profile................................................................................................................86

Applying Profile..............................................................................................................................87

Importing Profile........................................................................................................................... 88

Exporting Profile............................................................................................................................88

Editing Profile................................................................................................................................ 88

Viewing Profile Settings................................................................................................................ 89

Viewing Stored Profile Settings.................................................................................................... 89

Viewing Profile Log....................................................................................................................... 89

Completion Status And Troubleshooting.................................................................................... 89

Quick Deploy of Profiles...............................................................................................................90

Assigning Server Profiles to Slots ................................................................................................ 90

Launching iDRAC using Single Sign-On.......................................................................................91

Launching Remote Console from Server Status Page...................................................................... 92

8 Configuring CMC To Send Alerts.................................................................... 93

Enabling Or Disabling Alerts............................................................................................................... 93

Enabling Or Disabling Alerts Using CMC Web Interface............................................................. 93

Enabling Or Disabling Alerts Using RACADM...............................................................................93

Filtering Alerts................................................................................................................................93

Configuring Alert Destinations........................................................................................................... 94

Configuring SNMP Trap Alert Destinations..................................................................................94

Configuring E-Mail Alert Settings................................................................................................. 95

9 Configuring User Accounts and Privileges....................................................98

Types of Users.....................................................................................................................................98

Modifying Root User Administrator Account Settings.....................................................................102

Configuring Local Users................................................................................................................... 102

Configuring Local Users Using CMC Web Interface..................................................................102

Configure Local Users Using RACADM...................................................................................... 102

Configuring Active Directory Users..................................................................................................103

Supported Active Directory Authentication Mechanisms......................................................... 103

Standard Schema Active Directory Overview............................................................................ 104

Configuring Standard Schema Active Directory........................................................................ 105

Extended Schema Active Directory Overview........................................................................... 105

Configuring Extended Schema Active Directory....................................................................... 105

Configuring Generic LDAP Users..................................................................................................... 105

Configuring the Generic LDAP Directory to Access CMC........................................................ 105

Configuring Generic LDAP Directory Service Using CMC Web Interface................................ 105

Configuring Generic LDAP Directory Service Using RACADM..................................................106

10 Configuring CMC For Single Sign-On Or Smart Card Login..................108

System Requirements....................................................................................................................... 108

Client Systems.............................................................................................................................109

CMC.............................................................................................................................................109

Prerequisites For Single Sign-On Or Smart Card Login.................................................................. 109

Generating Kerberos Keytab File......................................................................................................109

Configuring CMC For Active Directory Schema.............................................................................. 110

Configuring Browser For SSO Login.................................................................................................110

Internet Explorer..........................................................................................................................110

Mozilla FireFox............................................................................................................................. 110

Configuring Browser For Smart Card Login.....................................................................................110

Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM... 111

Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface..... 111

Uploading Keytab File........................................................................................................................ 111

Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM...112

11 Configuring CMC to Use Command Line Consoles................................. 113

CMC Command Line Console Features...........................................................................................113

CMC Command Line Interface Commands...............................................................................113

Using Telnet Console With CMC...................................................................................................... 114

Using SSH With CMC...................................................................................................................114

Supported SSH Cryptography Schemes..................................................................................... 114

Configure Public Key Authentication Over SSH......................................................................... 115

Configuring Terminal Emulation Software.......................................................................................116

Connecting to Servers or I/O Module Using Connect Command..................................................116

Configuring the Managed Server BIOS for Serial Console Redirection.....................................117

Configuring Windows for Serial Console Redirection............................................................... 118

Configuring Linux for Server Serial Console Redirection During Boot..................................... 118

Configuring Linux for Server Serial Console Redirection After Boot.........................................119

12 Using FlexAddress and FlexAddress Plus Cards........................................ 121

About FlexAddress............................................................................................................................. 121

About FlexAddress Plus................................................................................................................121

Verifying FlexAddress Activation................................................................................................. 122

Deactivating FlexAddress............................................................................................................ 123

Configuring FlexAddress...................................................................................................................124

Configuring FlexAddress for Chassis-Level Fabric and Slots.....................................................124

Viewing World Wide Name/Media Access Control (WWN/MAC) IDs....................................... 124

Command Messages.........................................................................................................................124

FlexAddress DELL SOFTWARE LICENSE AGREEMENT.................................................................... 126

Viewing WWN/MAC Address Information........................................................................................128

Viewing Basic WWN/MAC Address Information Using Web Interface........................................... 129

Viewing Advanced WWN/MAC Address Information Using Web Interface....................................129

Viewing WWN/MAC Address Information Using RACADM.............................................................130

13 Managing Fabrics............................................................................................132

Monitoring IOM Health..................................................................................................................... 132

Configuring Network Settings for IOM.............................................................................................132

Configuring Network Settings for IOM Using CMC Web Interface...........................................133

Configuring Network Settings for IOM Using RACADM............................................................ 133

Viewing I/O Module Uplink and Downlink Status Using Web Interface......................................... 133

Viewing I/O Module FCoE Session Information Using Web Interface............................................134

Resetting IOM to Factory Default Settings.......................................................................................134

Updating IOM Software Using CMC Web Interface........................................................................ 134

14 Using VLAN Manager..................................................................................... 136

Assigning VLAN to IOM.....................................................................................................................136

Configuring VLAN settings on IOMs Using CMC Web Interface ....................................................136

Viewing the VLAN settings on IOMs Using CMC Web Interface..................................................... 137

Viewing the Current VLAN Settings on IOMs Using CMC Web Interface.......................................137

Removing VLANs for IOMs Using CMC Web Interface....................................................................137

Updating Untagged VLANs for IOMs Using CMC Web Interface....................................................138

Resetting VLANs for IOMs Using CMC Web Interface.....................................................................138

15 Managing and Monitoring Power................................................................139

Redundancy Policies.........................................................................................................................140

Grid Redundancy Policy..............................................................................................................140

No Redundancy Policy................................................................................................................140

Redundancy Alerting Only Policy...............................................................................................140

PSU Failures.................................................................................................................................140

Default Redundancy Configuration................................................................................................. 140

Multi-node Sled Adaptation..............................................................................................................140

Chassis Power Limit Monitoring....................................................................................................... 141

Viewing Power Consumption Status................................................................................................ 141

Viewing Power Consumption Status Using CMC Web Interface.............................................. 141

Viewing Power Consumption Status Using RACADM................................................................141

Viewing Power Budget Status Using CMC Web Interface...............................................................141

Viewing Power Budget Status Using RACADM................................................................................ 141

Redundancy Status and Overall Power Health................................................................................ 142

Power Management After PSU Failure....................................................................................... 142

Power Supply and Redundancy Policy Changes in System Event Log.....................................142

Configuring Power Budget and Redundancy............................................................................ 143

Executing Power Control Operations........................................................................................ 145

Executing Power Control Operations for Multiple Servers Using CMC Web Interface........... 145

Executing Power Control Operations on the IOM.................................................................... 146

16 Viewing PCIe Slots..........................................................................................147

Viewing PCIe Slot Properties Using CMC Web Interface................................................................ 147

Viewing PCIe Slot Properties Using RACADM................................................................................. 148

17 Troubleshooting and Recovery................................................................... 149

Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP.......................149

Supported Interfaces...................................................................................................................149

Downloading SNMP Management Information Base (MIB) File................................................150

First Steps to Troubleshoot a Remote System...........................................................................150

Troubleshooting Alerts................................................................................................................ 151

Viewing Event Logs......................................................................................................................151

Using Diagnostic Console...........................................................................................................152

Resetting Components............................................................................................................... 152

Saving or Restoring Chassis Configuration................................................................................ 152

Troubleshooting Network Time Protocol (NTP) Errors............................................................. 153

Interpreting LED Colors and Blinking Patterns...........................................................................154

Troubleshooting Network Problems.......................................................................................... 157

General Troubleshooting.................................................................................................................. 157

18 Frequently Asked Questions.........................................................................158

RACADM............................................................................................................................................ 158

Managing and Recovering a Remote System.................................................................................. 159

Active Directory.................................................................................................................................160

IOM.....................................................................................................................................................161

Event and Error Messages................................................................................................................. 161

Overview

The Dell Chassis Management Controller (CMC) for PowerEdge FX2/FX2s is a Systems Management hardware and software solution for managing the PowerEdge FX2/FX2s chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.

The CMC enables an IT administrator to:

• View inventory.

• Perform configuration and monitoring tasks.

• Remotely turn on and turn off chassis and servers.

• Enable alerts for events on servers and components in the server module.

• View the PCIe mapping information.

• Provide a one–many management interface to the iDRACs and I/O modules in the chassis.

The CMC provides multiple System Management functions for servers. Power and thermal management are the primary functions of CMC, which are listed as follows:

• Enclosure-level real-time automatic power and thermal management.

– The CMC reports real-time power consumption, which includes logging high and low points with

a time stamp.

– The CMC supports setting an optional enclosure maximum power limit (System Input Power Cap),

which alerts and takes actions such as limiting the power consumption of servers, and/or preventing the turning on of new servers to keep the enclosure under the defined maximum power limit.

– The CMC monitors and automatically controls the functions of cooling fans based on actual

ambient and internal temperature measurements.

– The CMC provides comprehensive enclosure inventory and status or error reporting.

• The CMC provides a mechanism for centralized configuration of the:

– Network and security setting of the PowerEdge FX2/FX2s enclosure. – Power redundancy and power ceiling settings. – I/O switch and iDRAC network settings. – First boot device on the server module. – I/O fabric consistency checks between the I/O module and servers. CMC also disables

components, if necessary, to protect the system hardware. – User access security. – PCIe slots.

You can configure CMC to send email alerts or SNMP trap alerts for warnings or errors such as temperature, hardware misconfiguration, power outage, and fan speed.

Key Features

The CMC features are grouped into management and security features.

What Is New In This Release

This release of CMC for Dell PowerEdge FX2/FX2s supports:

• 13th generation Blade Servers.

• Enhanced WWN/MAC Address Inventory that includes WWN/MAC addresses assigned to a LOM/ Select Network Adapter (SNA) using the iDRAC IO Identity feature.

• Viewing status of NIC Partitions as part of the WWN/MAC Address Inventory independent of the OS.

• Using directories in the remote NFS/CIFS directory for server profiles and custom repository of DUPs.

• Option to use an external library (CIFS/NFS directory) to update repositories and profiles.

• Option to view and use captured profiles stored on an external library.

• Enhanced WWN/MAC Address Inventory using the iDRAC IO Identity feature.

• Enforcement of signature checking for CMC firmware images.

• Updating CMC using DUP

Management Features

CMC provides the following management features:

• Dynamic Domain Name System (DDNS) registration for IPv4 and IPv6.

• Login management and configuration for local users, Active Directory, and LDAP.

• Remote system management and monitoring using SNMP, a web interface, integrated KVM, Telnet, or SSH connection.

• Monitoring — Provides access to system information and status of components.

• Access to system event logs — Provides access to the hardware log and chassis log.

• Firmware updates for various chassis components — Enables you to update the firmware for CMC, iDRAC on servers, and chassis infrastructure.

• Firmware update of server components such as BIOS, network controllers, and so on across multiple servers in the chassis using Lifecycle Controller.

• Dell OpenManage software integration — Enables you to launch the CMC web interface from Dell OpenManage Server Administrator or OpenManage Essentials (OME) 1.2.

• CMC alert — Alerts you about potential managed node issues through Remote syslog email message or SNMP trap.

• Remote power management — Provides remote power management functions, such as turn off and reset of any chassis component, from a management console.

• Power usage reporting.

• Secure Sockets Layer (SSL) encryption — Provides secure remote system management through the web interface.

• Launch point for the Integrated Dell Remote Access Controller (iDRAC) web interface.

• Support for WS-Management.

• Multi-node Sled adaptation. PowerEdge FM120x4 is a multi-node Sled.

• Chassis Power Limit Monitoring.

• iDRAC IO Identity feature support for enhanced WWN/MAC Address Inventory.

• FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/ MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade.

• Graphical display of chassis component status and health.

• Support for single and multi-slot servers.

• iDRAC single sign-on.

• Network time protocol (NTP) support.

• Enhanced server summary, power reporting, and power control pages.

• Multi-chassis management, allows up to 19 other chassis to be visible from the lead chassis.

NOTE: Multi-Chassis Management is not supported on IPv6 networks.

Security Features

The CMC provides the following security features:

• Password-level security management — Prevents unauthorized access to a remote system.

• Centralized user authentication through:

– Active Directory using Standard Schema or an Extended Schema (optional). – Hardware-stored user IDs and passwords.

• Role-based authority — Enables an administrator to configure specific privileges for each user.

• User ID and password configuration through the web interface. Web interface supports 128-bit SSL

3.0 encryption and 40-bit SSL 3.0 encryption (for countries where 128-bit is not acceptable).

NOTE: Telnet does not support SSL encryption.

• Configurable IP ports (if applicable).

• Login failure limits per IP address, with login blocking from the IP address when the limit is exceeded.

• Configurable session auto time out, and more than one simultaneous sessions.

• Limited IP address range for clients connecting to CMC.

• Secure Shell (SSH), which uses an encrypted layer for higher security.

• Single Sign-on, Two-Factor Authentication, and Public Key Authentication.

• CMC Signed Image — Used to protect the firmware image from undetected modification using digital signature.

Chassis Overview

A Back Panel view of the chassis is given here with a table that lists the parts and devices available in the CMC.

Figure 1.

Item Indicator, Button, or Connector

Serial connector

Ethernet connector Gb1

Ethernet connector STK/Gb2 (stack)

System identification button

Low-profile PCIe expansion slots

Power supply (PSU1)

Power supply (PSU2)

I/O module (2)

I/O module ports

I/O module indicators

A Front Panel view of the chassis is given here with a table that lists the parts and devices available in the CMC.

Item Indicator, Button, or Connector

KVM select button

System identification button

Item Indicator, Button, or Connector

Diagnostic indicators

Enclosure power-on indicator, power button

Sleds

Video connector

USB connector

Supported Remote Access Connections

The following table lists the supported Remote Access Connections.

Table 1. Supported Remote Access Connections

Connection Features

CMC Network Interface ports

• Gb ports: Dedicated network interface for the CMC web interface. The CMC has two RJ-45 Ethernet ports:

– Gb1 (the uplink port) – Gb2 (the stacking or cable consolidation port). The STK/Gb2 port

can also be used for CMC NIC failover.

NOTE: Ensure that the CMC setting is changed from default

Stacking to Redundant to implement NIC failover. CAUTION: Connecting the STK/Gb2 port to the

management network will have unpredictable results if the CMC setting is not changed from default Stacking to Redundant, to implement NIC failover. In the default Stacking mode, cabling the Gb1 and STK/Gb2 ports to the same network (broadcast domain) can cause a broadcast storm. A broadcast storm can also occur if the CMC setting is changed to Redundant mode, but the cabling is daisy chained between chassis in the Stacking mode. Ensure that the cabling model matches the CMC setting for the intended usage.

• DHCP support.

• SNMP traps and e-mail event notification.

• Network interface for the iDRAC and I/O Modules (IOMs).

• Support for Telnet/SSH command console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands.

Serial port

• Support for serial console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands.

• Support for binary interchange for applications specifically designed to communicate with a binary protocol to a particular type of IOM.

• Serial port can be connected internally to the serial console of a server, or I/O module, using the connect (or racadm connect) command.

Supported Platforms

The CMC supports the PowerEdge FX2 and FX2s chassis models. The supported platforms are PowerEdge FC630 and PowerEdge FM120x4. For information about compatibility with CMC, see the documentation for your device.

For the latest supported platforms, see the Dell Chassis Management Controller (CMC) Version 1.1 for

Dell PowerEdge FX2/FX2s Release Notes available at dell.com/support/manuals.

Supported Web Browsers

For the latest information about supported web browsers, see the Dell Chassis Management Controller (CMC) Version 1.1 for Dell PowerEdge FX2/FX2s Release Notes located at dell.com/support/manuals.

Managing Licenses

The CMC features are available based on the license (CMC Express or CMC Enterprise) purchased. Only licensed features are available in the interfaces that allow you to configure or use CMC. For example, CMC Web interface, RACADM, WS-MAN, and so on. CMC license management and firmware update functionality is always available through CMC Web interface and RACADM.

Types of Licenses

The types of licenses offered are:

• 30 day evaluation and extension — The license expires after 30 days that can be extended for 30 days. Evaluation licenses are duration-based, and the timer runs when power is applied to the system.

• Perpetual — The license is bound to the service tag and is permanent.

Acquiring Licenses

Use any of the following methods to acquire the licenses:

• E-mail — License is attached to an e-mail that is sent after requesting it from the technical support center.

• Self-service portal — A link to the Self-Service Portal is available from CMC. Click this link to open the licensing Self-Service Portal on the internet from where you can purchase licenses. For more information, see the online help for the self-service portal page.

• Point-of-sale — License is acquired while placing the order for a system.

License Operations

Before you perform the license management tasks, make sure to acquire the licenses. For more information, see the Acquiring Licenses section and Overview and Feature Guide available at support.dell.com.

NOTE: If you have purchased a system with all the licenses pre-installed, then license management is not required.

You can perform the following licensing operations using CMC, RACADM, and WS-MAN for one-to-one license management, and Dell License Manager for one-to-many license management:

• View — View the current license information.

• Import — After acquiring the license, store the license in a local storage and import it into CMC using one of the supported interfaces. The license is imported if it passes the validation checks.

NOTE: For a few features, a CMC restart may be required to enable the features.

• Export — Export the installed license into an external storage device back up or to reinstall it after a service part is replaced. The file name and format of the exported license is <EntitlementID>.xml

• Delete — Delete the license that is assigned to a component if the component is missing. After the license is deleted, it is not stored in CMC and the base product functions are enabled.

• Replace — Replace the license to extend an evaluation license, change a license type such as an evaluation license with a purchased license, or extend an expired license.

• An evaluation license may be replaced with an upgraded evaluation license or with a purchased license.

• A purchased license may be replaced with an updated license or with an upgraded license. For more information, see Dell Software License Management Portal available at HTTPS://WWW.DELL.COM/ SUPPORT/LICENSING/US/EN/19

• Learn More — Learn more about an installed license, or the licenses available for a component installed in the server.

NOTE: For the Learn More option to display the correct page, make sure that *.dell.com is added to the list of Trusted Sites in the Security Settings. For more information, see the Internet Explorer help documentation.

NOTE: If you try to install the PowerEdge FM120x4 license on PowerEdge FC630, the license installation fails. For more information on licensing refer Integrated Dell Remote Access Controller (iDRAC) User’s Guide .

Licensable Features In CMC

A list of CMC features that are enabled on the basis of your license is given here in the table.

Feature Express Enterprise

CMC Network Yes Yes

CMC Serial Port Yes Yes

RACADM (SSH, Local, and Remote) Yes Yes

WS-MAN Yes Yes

SNMP Yes Yes

Telnet Yes Yes

SSH Yes Yes

Web-based Interface Yes Yes

Email Alerts Yes Yes

CMC Settings Backup No Yes

CMC Settings Restore Yes Yes

Remote Syslog No Yes

Directory Services No Yes

Single Sign-On Support No Yes

Two-Factor Authentication No Yes

PK Authentication No Yes

Remote File Share No Yes

Enclosure level power capping No Yes

Multi-chassis management No Yes

FlexAddress Enablement No Yes

One-to-many Server Firware Update

One-to-many configuration for iDRAC

No Yes

License Component State or Condition and Available Operations

The following table provides the list of license operations available based on the license state or condition.

Table 1. License Operations Based on State and Condition

License/ Component state or condition

Non-administrator login

Active license Yes Yes Yes Yes Yes

Expired license No Yes Yes Yes Yes

License installed but component missing

Import Export Delete Replace Learn More

No Yes No No Yes

No Yes Yes No Yes

Viewing Localized Versions of the CMC Web Interface

To view localized versions of the CMC web interface, read through your web browser's documentations. To view the localized versions, set the browser to the desired language.

Supported Management Console Applications

The CMC supports integration with Dell OpenManage Console. For more information, see the OpenManage Console documentation available at dell.com/support/manuals.

How to Use this User's Guide

The contents of this User's Guide enable you to perform the tasks by using:

• The Web interface: Only the task-related information is given here. For information about the fields and options, see the CMC for Dell PowerEdge FX2/FX2s Online Help that you can open from the Web interface.

• The RACADM commands: The RACADM command or the object that you must use is provided here. For more information about a RACADM command, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/ manuals.

Accessing documents from Dell support site

You can access the required documents in one of the following ways:

• Using the following links:

– For all Enterprise Systems Management documents — dell.com/softwaresecuritymanuals – For Enterprise Systems Management documents — dell.com/openmanagemanuals – For Remote Enterprise Systems Management documents — dell.com/esmmanuals – For OpenManage Connections Enterprise Systems Management documents — dell.com/

OMConnectionsEnterpriseSystemsManagement

– For Serviceability Tools documents — dell.com/serviceabilitytools – For Client Systems Management documents — dell.com/clientsystemsmanagement – For OpenManage Connections Client Systems Management documents — dell.com/

connectionsclientsystemsmanagement

• From the Dell Support site:

a. Go to dell.com/support/home. b. Under General support section, click Software & Security. c. In the Software & Security group box, click the required link from the following:

– Enterprise Systems Management – Remote Enterprise Systems Management – Serviceability Tools

– Client Systems Management – Connections Client Systems Management

d. To view a document, click the required product version.

• Using search engines:

– Type the name and version of the document in the search box.

Installing and Setting Up CMC

This section provides information about how to install your CMC hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the tasks for configuring a CMC:

• Set up initial access to CMC.

• Access CMC through a network.

• Add and configure CMC users.

• Update CMC firmware.

Installing CMC Hardware

The CMC is pre-installed on your chassis and hence no installation is required.

Checklist To Set up Chassis

The following tasks enable you to accurately setup the chassis:

1. The CMC and the management station, where you use your browser, must be on the same network,

which is called the management network. Connect an Ethernet network cable from the port labelled

GB1 to the management network.

Management Network: CMC and the iDRAC (on each server) and the network management ports

for the switch I/O module are connected to a common internal network in the PowerEdge FX2/FX2s chassis. This allows the management network to be isolated from the server data network.

Application Network: Access to the managed servers is accomplished through network connections to the I/O module (IOM). This allows the application network to be isolated from the management network. It is important to separate this traffic for uninterrupted access to chassis management.

NOTE: It is recommended to isolate chassis management from the data network. Due to the potential of traffic on the data network, the management interfaces on the internal management network can be saturated by traffic intended for servers. This results in CMC and iDRAC communication delays. These delays may cause unpredictable chassis behavior, such as CMC displaying iDRAC as offline even when it is up and running, which in turn causes other unwanted behavior. If physically isolating the management network is impractical, the other option is to separate CMC and iDRAC traffic to a separate VLAN. CMC and individual iDRAC network interfaces can be configured to use a VLAN.

2. The STK/Gb2 port can also be used for CMC NIC failover. Ensure that the CMC setting is changed

from default Stacking to Redundant to implement NIC failover. For more information, see

Configuring Management Port 2

CAUTION: Connecting the STK/Gb2 port to the management network will have unpredictable results if the CMC setting is not changed from default Stacking to Redundant, to implement NIC failover. In the default Stacking mode, cabling the Gb1 and STK/Gb2 ports to the same network (broadcast domain) can cause a broadcast storm. A broadcast storm can also occur if the CMC setting is changed to Redundant mode, but the cabling is daisy chained between chassis in the Stacking mode. Ensure that the cabling model matches the CMC setting for the intended usage.

3. Install the I/O module in the chassis and connect the network cable to the I/O module.

4. Insert the servers in the chassis.

5. Connect the chassis to the power source.

6. To power on the chassis, press the power button or use the following interfaces after completing

the task 6. Using the Web interface, go to Chassis Overview → Power → Control → Power Control

Options

You can also power on the chassis using the command line interface, use racadm chassisaction powerup command to accomplish it.

7. The default CMC network configuration is Static with the CMC IP address 192.168.0.120. If you want

to change the network configuration to DHCP, connect a serial cable to serial port on the CMC. For more information on serial connection, refer to Serial interface/protocol setup in Using Remote

Access Software From a Management Station section.

After the serial connection is established, login and use the command racadm setniccfg —d to change the network configuration to DHCP. CMC takes 30 to 60 seconds approximately to obtain the IP address from the DHCP server.

→ Power On System. Click Apply.

NOTE: Do not turn on the servers.

To view the DHCP assigned CMC IP address, use one of the following methods:

• To view CMC IP address using serial connection with CMC, perform the following steps:

1. Connect one end of the serial null modem cable to the serial connector on the back of the chassis.

2. Connect the other end of the cable to the management system serial port.

3. After the connection is established, login to CMC using default root account credentials.

4. Run the racadm getniccfg command. In the output displayed, search for Current IP Address.

• To view CMC IP address by connecting the server using KVM, perform the following steps:

1. Connect to a server in the chassis using KVM.

NOTE: For more details on how to connect a server through KVM, see Accessing

Server Using KVM.

2. Turn on the server.

3. Make sure the server is set to boot in Unified Extensible Firmware Interface (UEFI) mode.

4. Press F2 to access the System Setup page.

5. In the System Setup page, click iDRAC Settings → System Summary.

The CMC IP address is displayed in the Chassis Management Controller section.

For more information about iDRAC Settings page in the iDRAC GUI, see the Dell Integrated Dell Remote Access Controller (iDRAC) User’s Guide .

8. Connect to the CMC IP address by using a web browser by typing the default root account credential.

9. Configure iDRAC network settings as required. by default, iDRAC LAN is enabled with static IP configured. To determine the default static IP address with an Enterprise license, go to Server Overview → Setup → iDRAC. You can also determine the static IP address with an Express license. Go to

Server Overview → Server-Slot → Setup → iDRAC.

10. Provide the IO module with an external management IP address(if applicable) in the CMC web interface. You can get the IP address by clicking I/O Module Overview, and then clicking Setup.

11. Connect to each iDRAC through the web interface using default root account credential to complete any necessary configuration.

12. Turn on the servers and install the operating system.

NOTE: The default local account credential is root (user name) and calvin (user password).

Using Remote Access Software From a Management Station

You can access CMC from a management station using various remote access software. Here is a list of remote access softwares by Dell which is available from your Operating System.

Interface/Protocol Description

Serial CMC supports a serial text console that can be

launched using any terminal emulation software. Following are couple of examples of terminal emulation software that can used to connect to CMC.

• Linux Minicom

• Hilgraeve’s HyperTerminal for Windows

Connect one end of the serial null modem cable (present at both ends) to the serial connector on the back of the chassis. Connect the other end of the cable to management station serial port. For more information on connecting cables, refer to the back panel of the chassis in Chassis Overview section.

Configure your terminal emulation software with the following parameters:

• Baud rate: 115200

• Port: COM1

• Data: 8 bit

• Parity: None

• Stop: 1 bit

• Hardware flow control: Yes

• Software flow control: No

Remote RACADM CLI Remote RACADM is a client utility that runs on a

management station. It uses the out-of-band network interface to run RACADM commands on the managed system and uses the HTTPs channel. The –r option runs the RACADM command over a network, it requires CMC IP, username and password.

To use remote RACADM from your management station, install remote RACADM using the Dell Systems Management Tools and Documentation DVD that is available with your system. For more information on Remote RACADM

Web Interface Provides remote access to CMC using a graphical

user interface. The Web interface is built into the CMC firmware and is accessed through the NIC interface from a supported web browser on the management station. For a list of supported Web browsers, see the Supported Browsers section in the Dell System Software Support Matrix at dell.com/support/manuals.

Telnet Provides command line access to CMC through

the network. The RACADM command line interface and the connect command, which is used to connect to the serial console of a server or IO module, are available from the CMC command line.

NOTE: Telnet is not a secure protocol and is disabled by default. Telnet transmits all data, including passwords in plain text.

SNMP Simple Network Management Protocol (SNMP) is a

set of protocol definitions for managing devices on the networks. The CMC provides access to SNMP, which allows you to use SNMP tools to query the CMC for Systems Management information. The CMC MIB file can be downloaded from the CMC Web interface, go to Chassis Overview → Network

→ Services → SNMP. See the Dell OpenManage SNMP Reference Guide for more information

about the CMC MIB.

The following example show how the net-snmp

snmpget

service tag from the CMC.

snmpget -v 1 -c <CMC community name> <CMC IP address>.

1.3.6.1.4.1.674.10892.2.1.1.6.0

WS-MAN The WSMAN Services is based on the Web Services

for Management (WSMAN) protocol to perform one-to-many systems management tasks. You can use WS-MAN client such as WinRM client (Windows) or the OpenWSMAN client (Linux) to use the LC-Remote Services functionality. You can also use Power Shell and Python script the WSMAN interface.

WSMAN is a Simple Object Access Protocol (SOAP)–based protocol used for systems management. CMC uses WS–Management to convey Distributed Management Task Force

command can be used to get the chassis

(DMTF) Common Information Model (CIM)–based management information. The CIM information defines the semantics and information types that can be modified in a managed system.

The CMC WS-MAN implementation uses SSL on port 443 for transport security, and supports basic authentication. The data available through WSManagement is provided by CMC instrumentation interface mapped to the DMTF profiles and extension profiles.

NOTE: The SSL port used for transport security is the same as the CMC HTTPS port.

For more information, see:

• MOFs and Profiles — delltechcenter.com/

page/DCIM.Library

• DTMF Web site — dmtf.org/standards/profiles/

• WS-MAN Release notes file.

• www.wbemsolutions.com/

ws_management.html

• DMTF WS-Management Specifications:

www.dmtf.org/standards/wbem/wsman

For client connection using Microsoft WinRM, the minimum required version is 2.0. For more information, refer to the Microsoft article, <support.microsoft.com/kb/968929>.

Launching CMC Using Other Systems Management Tools

You can also launch CMC from the Dell Server Administrator or Dell OpenManage Essentials. To access CMC interface using Dell Server Administrator, launch Server Administrator on your

management station. In the left pane of the Server Administrator home page, click System → Main

System Chassis → Remote Access Controller. For more information, see the Dell Server Administrator User’s Guide at dell.com/support/manuals.

Remote RACADM Installation

To use remote RACADM from your management station, install remote RACADM using the Dell Systems Management Tools and Documentation DVD that is available with your system. This DVD includes the

following Dell OpenManage components:

• DVD root — Contains the Dell Systems Build and Update Utility.

• SYSMGMT — Contains the systems management software products including Dell OpenManage

Server Administrator.

• Docs — Contains documentation for systems, systems management software products, peripherals,

and RAID controllers.

• SERVICE — Contains the tools required to configure your system, and delivers the latest diagnostics

and Dell-optimized drivers for your system.

For information about installing Dell OpenManage software components, see the Dell OpenManage Installation and Security User's Guide available at dell.com/support/manuals. You can also download the latest version of the Dell DRAC Tools from support.dell.com.

Installing Remote RACADM on a Windows Management Station

If you are using the DVD, run <path>\SYSMGMT\ManagementStation\windows\DRAC\<.msi file name> If you have downloaded the software from support.dell.com:

1. Extract the downloaded file and execute the .msi file provided.

Depending on the version downloaded, the file will be named DRAC.msi, RACTools.msi, or RACTools64Bit.msi.

2. Accept the license agreement. Click Next.

3. Select the location where it is to be installed. Click Next.

4. Click Install.

The installing window appears.

5. Click Finish.

Open an administrative command prompt, type racadm and press Enter. If you get the RACADM help instructions, it implies that the software is installed correctly.

Installing Remote RACADM on a Linux Management Station

1. Log in as root to the system running a supported Red Hat Enterprise Linux or SUSE Linux Enterprise

Server operating system where you want to install the managed system components.

2. Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive.

3. To mount the DVD to a required location, use the mount command or a similar command.

NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are auto-mounted with the -

noexec mount

You need to mount the DVD-ROM manually, and then run the commands.

4. Navigate to the SYSMGMT/ManagementStation/linux/rac directory. To install the RAC software,

type the following command:

rpm -ivh *.rpm

5. For help about the RACADM command, type racadm help after you run the previous commands.

For more information about RACADM, see the Chassis Management Controller for Dell PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

NOTE: When using the RACADM remote capability, you must have the 'write' permission on the folders where you are using the RACADM subcommands, involving the file operations. For example, racadm getconfig -f <file name>.

option. This option does not allow you to run any executable from the DVD.

Uninstalling Remote RACADM From a Linux Management Station

1. Log in as root to the system where you want to uninstall the management station features.

2. Run the following rpm query command to determine which version of the DRAC tools is installed:

rpm -qa | grep mgmtst-racadm

3. Verify the package version to be uninstalled and uninstall the feature by using the rpm -e rpm -qa

| grep mgmtst-racadm

command.

Configuring a Web Browser

You can configure and manage CMC, servers, and modules installed in the chassis through a web browser. See the “Supported Browsers" section in the Dell Systems Software Support Matrix at dell.com/ support/manuals.

The CMC and the management station where you use your browser must be on the same network, which is called the management network. On the basis of your security requirements, the management network can be an isolated and highly secure network.

NOTE: Make sure that the security measures on the management network such as firewalls and proxy servers, do not prevent your web browser from accessing the CMC.

Some browser features can interfere with connectivity or performance, especially if the management network does not have a route to the Internet. If your management station is running on a Windows operating system, some Internet Explorer settings can interfere with connectivity, even though you use a command line interface to access the management network.

NOTE: To address security issues, Microsoft Internet Explorer strictly monitors the time on its cookie management. To support this, the time on your computer that runs Internet Explorer must be synchronized with the time on the CMC.

Proxy Server

To browse through a proxy server that does not have access to the management network, you can add the management network addresses to the exception list of the browser. This instructs the browser to bypass the proxy server while accessing the management network.

Microsoft Phishing Filter

If the Microsoft Phishing Filter is enabled in Internet Explorer on your management system, and your CMC does not have Internet access, accessing CMC may be delayed by a few seconds. This delay can happen if you are using the browser or another interface such as remote RACADM. To disable the phishing filter:

1. Start Internet Explorer.

2. Click Tools → Phishing Filter, and then click Phishing Filter Settings.

3. Select the Disable Phishing Filter option and click OK.

Downloading Files From CMC With Internet Explorer

When you use Internet Explorer to download files from the CMC, you may experience problems when the Do not save encrypted pages to disk option is not enabled.

To enable the Do not save encrypted pages to disk option:

1. Start Internet Explorer.

2. Click Tools → Internet Options → Advanced.

3. In the Security section, select the Do not save encrypted pages to disk option.

Enabling Animations In Internet Explorer

When transferring files to and from the web interface, a file transfer icon spins to show transfer activity. While using Internet explorer, you have to configure the browser to play animations.

To configure Internet Explorer to play animations:

1. Start Internet Explorer.

2. Click Tools → Internet Options → Advanced.

3. Go to the Multimedia section, and then select the Play animations in web pages option.

Downloading and Updating CMC Firmware

To download the CMC firmware, see Downloading CMC Firmware. To update the CMC firmware, see Updating CMC Firmware.

Setting Chassis Physical Location and Chassis Name

You can set the chassis location in a data center and the chassis name to identify the chassis on the network (default name is cmc-“Service Tag”). For example, an SNMP query on the chassis name returns the name you configure.

Setting Chassis Physical Location and Chassis Name Using Web Interface

To set the chassis location and chassis name using the CMC web interface:

1. In the left pane, go to Chassis Overview, and then click Setup.

2. On the General Chassis Settings page, type the location properties and the chassis name. For more

information about setting chassis properties, see the

NOTE: The Chassis Location field is optional. It is recommended to use the Data Center, Aisle,

Rack, and Rack Slot fields to indicate the physical location of the chassis.

3. Click Apply. The settings are saved.

CMC Online Help.

Setting Chassis Physical Location and Chassis Name Using RACADM

To set the chassis name, location, date, and time by using the command line interface, see the setsysinfo and setchassisname commands.

For example racadm setsysinfo —c chassisname or racadm setsysinfo —c

chassislocation

For more information, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

Setting Date and Time on CMC

You can manually set the date and time, or you can synchronize the date and time with a Network Time Protocol (NTP) server.

Setting Date and Time on CMC Using CMC Web Interface

To set the date and time on CMC:

1. In the left pane, click Chassis Overview → Setup → Date/Time.

2. To synchronize the date and time with a Network Time Protocol (NTP) server, on the Date/Time

page, select Enable NTP and specify up to three NTP servers. To manually set the date and time, clear the Enable NTP option, and then edit the Date and Time fields.

3. Select the Time Zone from the drop-down menu, and then click Apply.

Setting Date and Time on CMC Using RACADM

To set the date and time using the command line interface, see the config command and

cfgRemoteHosts database property group sections in the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals.

For example racadm setractime -l 20140207111030.

To read the date and time use racadm getractime command.

Configuring LEDs to Identify Components on the Chassis

You can enable the LEDs of components (chassis, servers, and I/O Modules) to blink so that you can identify the component on the chassis.

NOTE: To modify these settings, you must have the Debug Administrator privilege on a CMC.

Configuring LED Blinking Using CMC Web Interface

To enable blinking for one, multiple, or all component LEDs:

• In the left pane, go to any of the following pages:

Chassis Overview → Troubleshooting.

– – Chassis Overview → Chassis Controller → Troubleshooting. – Chassis Overview → Server Overview → Troubleshooting.

NOTE: Only servers can be selected on this page.

To enable blinking of a component LED, select the respective component , and then click Blink. To disable blinking of a component LED, deselect the server, and then click Unblink.

Configuring LED Blinking Using RACADM

Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm setled -m <module> [-l <ledState>], where <module> specifies the module whose

LED you want to configure. Configuration options:

• server-n where n = 1-4 (PowerEdge FM120x4), and server-nx where n = 1–4 and x = a to b

(PowerEdge FC630).

• switch-1

• cmc-active

and <ledState> specifies whether or not 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 commands.

Configuring Front Panel

You can use the front panel page to configure:

• Power button

• KVM

Configuring Power Button

To configure the chassis power button:

1. In the left pane, click Chassis Overview → Front Panel → Setup.

2. On the Front Panel Configuration page, under the Power Button Configuration section, select the

Disable Chassis Power Button option, and then click Apply.

The chassis power button is disabled.

Accessing a Server Using KVM

To map a Server to KVM from Web Interface:

1. Connect a monitor to the video connector and a keyboard to USB connector located on the front of the chassis.

2. In the left pane, click Chassis Overview → Front Panel → Setup.

3. On the Front Panel Configuration page, under the KVM Configuration section, select Enable KVM Mapping option.

4. On the Front Panel Configuration page, under the KVM Configuration section, for KVM Mapped option, select the desired server from the drop down list.

5. Click Apply.

To map a Server to KVM using racadm, useracadm config -g cfgKVMInfo -o cfgKvmMapping [server slot #] command.

To view the current KVM mapping using racadm, use racadm getconfig -g cfgKVMInfo.

Configuring Chassis Management at Server Mode

This feature provides the ability to manage and monitor the chassis shared components and chassis nodes as rack servers. When this feature is enabled, you can manage and monitor the chassis fans, power supplies, temperature sensors, update and configure the CMC firmware through the following components:

• iDRAC

• Blade Server Operating System

• Lifecycle Controller

Configuring Chassis Management at Server Using CMC Web Interface

To enable chassis management at server mode:

1. In the left pane, click Chassis Overview → Setup → General.

2. In the General Chassis Settings page, from the Chassis Management at Server Mode drop-down,

select one of the following modes:

• None — This mode does not enable you to monitor or manage the chassis component through

iDRAC, OS, or Lifecycle Controller.

• Monitor — This mode enables you to monitor the chassis components but you cannot perform

any firmware update through iDRAC, OS, or Lifecycle Controller.

• Manage and Monitor — This mode enables you to monitor the chassis components and update

the CMC firmware using DUP through iDRAC, OS, or Lifecycle Controller.

Configuring Chassis Management at Server Mode Using RACADM

To enable the Chassis Management at server using RACADM, use the following commands:

• To disable Chassis Management at Server mode, use:

racadm config –g cfgRacTuning – cfgRacTuneChassisMgmtAtServer 0

• To change Chassis Management at Server mode to monitor, use:

racadm config –g cfgRacTuning – cfgRacTuneChassisMgmtAtServer 1

• To change Chassis Management at server mode to manage and monitor, use:

racadm config –g cfgRacTuning – cfgRacTuneChassisMgmtAtServer 2

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. You can also log in using Single Sign-On or a Smart Card.

Configure Public Key Authentication Over SSH

You can configure up to six public keys that can be used with the service username over an SSH interface. Before adding or deleting public keys, make 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. When the PKA over SSH is set up and used correctly, you need not enter username or passwords to log in to the CMC. This can be very useful to set up automated scripts to perform various functions.

NOTE: There is no GUI support for managing this feature, you can use only the RACADM.

When adding new public keys, make sure that the existing keys are not already at the index, where the new key is added. CMC does not perform checks to ensure previous keys are deleted before a new one is added. As soon as a new key is added, it is automatically in effect as long as the SSH interface is enabled.

When using the public key comment section of the public key, remember that only the first 16 characters are utilized by the CMC. The public key comment is used by the CMC to distinguish SSH users when using the RACADM getssninfo command, because all the PKA users use the service username to log in.

For example, if two public keys are set up one with comment PC1 and one with comment PC2:

racadm getssninfo Type User IP Address Login Date/Time SSH PC1 x.x.x.x 06/16/2009 09:00:00 SSH PC2 x.x.x.x 06/16/2009 09:00:00

For more information about the sshpkauth, see the Chassis Management Controller for PowerEdge FX2/FX2s Command Line Reference Guide.

Generating Public Keys for Systems Running Windows

Before adding an account, a public key is required from the system that accesses the CMC over SSH. There are two ways to generate the public/private key pair: using PuTTY Key Generator application for clients running Windows or ssh-keygen CLI for clients running Linux.

This section describes simple instructions to generate a public/private key pair for both applications. For additional or advanced usage of these tools, see the application Help.

To use the PuTTY Key Generator to create a basic key for clients running Windows:

1. Start the application and select SSH-2 RSA or SSH-2 DSA for the type of key to generate (SSH-1 is not

supported).

2. Enter the number of bits for the key. RSA key size should be between 768 and 4096 and the

recommended DSA key size is 1024.

NOTE:

• CMC may not display a message if you add keys less than 768 or greater than 4096, but when you try to log in with these keys, it fails.

• For DSA keys greater than 2048, use the following racadm command. CMC accepts RSA keys up to key strength 4096, but the recommended key strength is 1024.

racadm -r 192.168.8.14 -u <default root account username> -p <default root account password> sshpkauth -i svcacct -k 1 -p 0xfff -f dsa_2048.pub

3. Click Generate and move the mouse in the window as directed.

After the key is created, you can modify the key comment field.

You can also enter a passphrase to make the key secure. Ensure that you save the private key.

4. You have two options for using the public key:

• 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 1024 –C testing

where,

–t must be dsa or rsa.

–b specifies the bit encryption size between 768 and 4096.

–c allows modifying the public key comment and is optional.

The < passphrase > is optional. After the command completes, use the public file to pass to the RACADM for uploading the file.

Accessing CMC Web Interface

Before you log in to CMC using the web interface, make sure that you have configured a Supported Web

Browser and the user account is created with the required privileges.

NOTE: If you are using Microsoft Internet Explorer, connect using a proxy, and if you see the error The XML page cannot be displayed, you must disable the proxy to continue.

To access the CMC web interface:

1. Open a web browser supported on your system.

For the latest information on supported web browsers, see the Dell Systems Software Support Matrix located at dell.com/support/manuals.

2. In the Address field, type the following URL, and then press <Enter>:

• To access CMC using IPv4 address: https://<CMC IP address> If the default HTTPS port number (port 443) was changed, type: https://<CMC IP

address>:<port number>

• To access CMC using IPv6 address: https://[<CMC IP address>] If the default HTTPS port number (port 443) was changed, type: https://[<CMC IP

address>]:<port number>, where <CMC IP address> is the IP address for CMC and <port number> is the HTTPS port number.

The CMC Login page appears.

NOTE: While using IPv6, you must enclose the CMC IP address in parenthesis ([ ]).

Logging Into CMC as a Local User, Active Directory User, or LDAP User

To log in to CMC, you must have a CMC account with the Log In to CMC privilege. The default root account is the default administrative account that ships with CMC.

NOTE: For added security, it is strongly recommended that you change the default password of the root account during initial setup.

NOTE: When Certificate Validation is enabled, FQDN of the system should be provided. If certificate validation is enabled and IP address is provided for the Domain Controller, then the login will fail.

CMC does not support extended ASCII characters, such as ß, å, é, ü, or other characters used primarily in non-English languages.

To log in as a local user, Active Directory user, or LDAP user.

1. In the Username field, type your user name:

• CMC user name: <user name>

NOTE: The CMC user name can contain only alphanumeric characters and certain special characters. The at (@) symbol and following special characters are not supported:

– Forward slash (/) – Backward slash (/) – Semicolon (;) – Backward Quote (`) – Quotations (“)

• Active Directory user name: <domain>\<user name>, <domain>/<user name> or <user>@<domain>.

• LDAP user name: <user name>

NOTE: This field is case-sensitive.

2. In the Password field, type the user password.

NOTE: For Active Directory user, the Username field is case-sensitive.

3. In the Domain field, from the drop-down menu, select the required domain.

4. Optionally, select a session timeout. This is the duration for which you can stay logged in with no activity before you are automatically logged out. The default value is the Web Service Idle Timeout.

5. Click OK. You are logged into CMC with the required user privileges. You cannot log in to the Web interface with different user names in multiple browser windows on a

single workstation.

Logging in to CMC Using a Smart Card

To use this feature, you must have an Enterprise License. You can log in to CMC using a smart card. Smart cards provide Two Factor Authentication (TFA) that provide two-layers of security:

• Physical smart card device.

• Secret code such as a password or PIN.

Users must verify their credentials using the smart card and the PIN.

NOTE: You cannot use the IP address to log in to CMC using the Smart Card login. Kerberos validates your credentials based on the Fully Qualified Domain Name (FQDN).

Before you log in as an Active Directory user using a Smart Card, make sure to:

• 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 a smart card:

1. Log in to CMC using the link https://<cmcname.domain-name>. The CMC Login page is displayed asking you to insert a smart card.

NOTE: If you changed the default HTTPS port number (port 80), access the CMC web page using <cmcname.domain-name>:<port number>, where cmcname is the CMC host name for CMC, domain-name is the domain name, and port number is the HTTPS port number.

2. Insert the smart card and click Login. The PIN dialog box is displayed.

3. Type the PIN and click Submit.

NOTE: If the smart card user is present in Active Directory, an Active Directory password is not required. Else, you have to log in by using an appropriate username and password.

You are logged in to CMC with your Active Directory credentials.

Logging Into CMC Using Single Sign-on

When Single Sign-On (SSO) is enabled, you can log in to CMC without providing your domain user authentication credentials, such as user name and password. To use this feature, you must have an Enterprise License.

NOTE: You cannot use the IP address to log in to the SSO. Kerberos validates your credentials against the Fully Qualified Domain Name (FQDN).

Before logging in to CMC using SSO, make sure that:

• You have logged in to your system using a valid Active Directory user account.

• Single Sign-On option is enabled during the Active Directory configuration.

To log in to CMC using SSO:

1. Log in to the client system using your network account.

2. Access the CMC web interface by using: https://<cmcname.domain-name>

For example, cmc-6G2WXF1.cmcad.lab,, where cmc-6G2WXF1 is the cmc-name and cmcad.lab is the domain name.

NOTE: If you have changed the default HTTPS port number (port 80), access the CMC web interface using <cmcname.domain-name>:<port number>, where the cmcname is the CMC host name for CMC, domain-name is the domain name, and port number is the HTTPS port number.

CMC logs you in, using the Kerberos credentials that were cached by your browser when you logged in using your valid Active Directory account. If the login is unsuccessful, the browser is redirected to the normal CMC login page.

NOTE: If you are not logged in to the Active Directory domain and are using a browser other than Internet Explorer, the login is unsuccessful and the browser displays a only blank page.

Logging In To CMC Using Serial, Telnet, Or SSH Console

You can log in to CMC through a serial, Telnet, or SSH connection. After you configure your management station terminal emulator software, perform the following tasks to

1. Connect to CMC using your management station terminal emulation software.

2. Type your CMC user name and password, and then press <Enter>.

You are logged in to CMC.

Logging in to CMC Using Public Key Authentication

You can log in to the CMC over SSH without typing a password. You can also send a single RACADM command as a command line argument to the SSH application. The command line options behave similar to the remote RACADM, because the session ends after the command is completed.

Before logging in to CMC over SSH, make sure that the public keys are uploaded. To use this feature, you must have an Enterprise License.

For example:

• Logging in: ssh service@<domain> or ssh service@<IP_address>, where IP_address is the

CMC IP address.

• Sending RACADM commands: ssh service@<domain> racadm getversion and ssh

service@<domain> racadm getsel

When you log in using the service account, if a passphrase was set up when creating the public or private key pair, you may be prompted to enter that passphrase again. If the passphrase is used with the keys,

client systems running Windows and Linux provide methods to automate the method. On client systems running Windows, you can use the Pageant application. It runs in the background and makes entering the passphrase transparent. For client systems running Linux, you can use the ssh agent. For setting up and using either of these applications, see their product documentation.

Multiple CMC Sessions

A list of multiple CMC sessions that are possible by using the various interfaces is given here.

Table 2. Multiple CMC Sessions

Interface Number of Sessions

CMC web interface 4

RACADM 4

Telnet 4

SSH 4

Updating Firmware

You can update firmware for:

• The CMC

• Chassis infrastructure

• I/O Module

• PERC

• Expander and HDD

You can update firmware for the following server components:

• BIOS

• iDRAC7 on FM120x4 (12th generation of servers)

• iDRAC8 on FC630 (13th generation of servers)

• Lifecycle Controller

• 32–bit diagnostics

• Operating System Drivers Pack

• Network Interface Controllers

• RAID controllers

Signed CMC Firmware Image

The CMC 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. The firmware update process is stopped if CMC cannot verify the signature of the uploaded firmware image. A warning event is then logged and an appropriate error message is displayed.

When you try to upgrade CMC firmware version, CMC Firmware Update Process verifies the firmware image in the selected version for the signature from the service provider. The firmware update is stopped, if the signature is not found or if the verification of the image is not successful. A warning event is logged and an appropriate error message is displayed.

When a firmware downgrade to a earlier version is attempted, CMC Firmware Update Process verifies the firmware image in the earlier versions for the signature from the service provider. The firmware downgrade is stopped, if the computed signature of the earlier version is not recognized by the current CMC firmware. CMC firmware logs a warning event and an appropriate error message is displayed.

Downloading CMC Firmware

Before beginning the firmware update, download the latest firmware version from support.dell.com, and save it to your local system.

It is recommended to follow the following update order while updating firmware for the chassis:

• Blade components firmware

• CMC firmware

• Chassis infrastructure firmware

Viewing Currently Installed Firmware Versions

You can view the currently installed firmware versions using the CMC web interface or RACADM.

Viewing Currently Installed Firmware Versions Using CMC Web Interface

In the CMC web interface, go to any of the following pages to view the current firmware versions:

• Chassis Overview → Update

• Chassis Overview → Chassis Controller → Update

• Chassis Overview → Server Overview → Server Component Update

The Firmware Update page displays the current version of the firmware for each listed component and allows you to update the firmware to the latest version.

If the chassis contains an earlier generation server, whose iDRAC is in recovery mode or if CMC detects that iDRAC has corrupted firmware, then the earlier generation iDRAC is also listed on the Firmware

Update page.

Viewing Currently Installed Firmware Versions Using RACADM

You can view the currently installed firmware versions using racadm getversion command. For more information about other RACADM commands, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

Updating the CMC Firmware

You can update the CMC firmware using web interface or RACADM. The firmware update, by default, retains the current CMC settings.

NOTE: To update firmware on CMC, you must have the Chassis Configuration Administrator privilege.

NOTE: You cannot update the CMC firmware if the firmware image file does not contain a verification signature or it contains a verification signature, which is not valid or corrupted.

NOTE: You cannot downgrade the CMC firmware to an earlier version if the computed signature of that earlier version is not recognized by the current CMC firmware.

If a Web user interface session is used to update system component firmware, the Idle Timeout (0, 60–

10800) setting must be set to a higher value to accommodate the file transfer time. In some cases, the

firmware file transfer time may be as high as 30 minutes. To set the idle timeout value, see Configuring

Services.

During CMC firmware updates, it is normal for some or all of the fan units in the chassis to rotate at 100% speed.

To avoid disconnecting other users during a reset, notify authorized users who may log in to CMC and check for active sessions on the Sessions page. To open the Sessions page, click Chassis Overview in the left pane, click Network, and then click the Sessions.

When transferring files to and from CMC, the file transfer icon spins during the transfer. If your icon is not animated, make sure that your browser is configured to allow animations. For more information about allowing animations in the browser, see Allow Animations in Internet Explorer.

Updating CMC Firmware Using Web Interface

To update the CMC firmware using the CMC web interface:

1. In the left pane, go to any of the following pages:

• Chassis Overview → Update

• Chassis Overview → Chassis Controller → Update

2. On the Firmware Update page, in the CMC Firmware section, select the required components under the Update Targets column for the CMC you want to update, and then click Apply CMC Update.

3. In the Firmware Image field, enter the path to the firmware image file on the management station or shared network, or click Browse to browse through to the file location. The default name of the CMC firmware image file is fx2_cmc.bin.

4. Click Begin Firmware Update, and then click Yes. The Firmware Update Progress section provides firmware update status information. A status indicator displays on the page while the image file is uploaded. File transfer time varies based on the connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer is displayed. For more information about the various firmware status, see Online Help.

5. For the CMC, during the final phases of the firmware update process, the browser session and connection with CMC is lost temporarily because the CMC is not connected to the network. You must log in after a few minutes, when the CMC has restarted. After CMC resets, the new firmware version is displayed on the

Firmware Update page.

NOTE: After the firmware update, delete the files from the web browser cache. For instructions about clearing the browser cache, see the web browser’s online help.

Additional instructions:

• During a file transfer, do not click the Refresh icon or navigate to another page.

• To cancel the process, select the Cancel File Transfer and Update option. This option is available only

during file transfer.

• The Update State field displays the firmware update status.

NOTE: The update process may take several minutes.

Updating CMC Firmware Using RACADM

To update CMC firmware using RACADM, use the fwupdate subcommand. For example, racadm fwupdate <options> <firmware image>.

For more information about RACADM commands, see Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

Updating the CMC Using DUP

You can update the firmware version of the CMC using Dell Update Package (DUP) through the following components:

• iDRAC

• Blade Server Operating System

• Lifecycle Controller

For more information about updating CMC through iDRAC, see Integrated Dell Remote Access Controller User’s Guide.

Before you update the CMC using DUP, make sure:

• The CMC firmware package is available as DUP on a Local system or network share.

• Chassis Management at Server Mode is set to Manage and Monitor.

For more information, see Configuring Chassis Management at Server Mode

• For updates through OS or Lifecycle Controller, the iDRAC option Enable Shared Components

Update through OS/USC must be enabled. For more information on how to enable is this option, see Integrated Dell Remote Access Controller User’s Guide.

NOTE: When you update the CMC using DUP, the updates to the IOM Coprocessor available in the CMC image are applied on the next chassis power-up cycle.

Updating Chassis Infrastructure Firmware

The chassis infrastructure update operation updates the Main Board component.

NOTE: Before you update the Chassis Infrastructure firmware, turn off all the servers in the chassis if required.

Updating Chassis Infrastructure Firmware Using CMC Web Interface

1. Go to any of the following pages:

• Chassis Overview → Update.

• Chassis Overview → Chassis Controller → Update.

2. On the Firmware Update page, in the Chassis Infrastructure Firmware section, in the Update Targets column, select the option, and then click Apply Chassis Infrastructure Firmware.

3. On the Firmware Update page, click Browse, and then select the appropriate chassis infrastructure

firmware.

4. Click Begin Firmware Update, and then click Yes. The Firmware Update Progress section provides firmware update status information. While the

image file uploads, a status indicator displays on the page. File transfer time varies on the basis of connection speed. When the internal update process begins, the page automatically refreshes and the firmware update timer is displayed.

Additional instructions to follow:

• Do not click the Refresh icon, or navigate to another page during the file transfer.

• The Update State field displays the firmware update status.

When the update is complete, connection to the CMC is lost as the entire Chassis is reset. Refresh the web interface to login again. Go to Chassis Overview → Chassis Controller.

After the update is complete the updated Mainboard firmware version is displayed.

Updating Chassis Infrastructure Firmware Using RACADM

To update chassis infrastructure firmware using RACADM, use the fwupdate sub-command. For example, racadm fwupdate <options> <firmware image>.

For more information about using the RACADM commands, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

NOTE: To update the chassis infrastructure firmware, make sure the servers are turned off.

Updating Server iDRAC Firmware

You can update firmware for iDRAC7 or iDRAC8. To use this feature:

• You must have an Enterprise License.

• The iDRAC7 firmware version must be 1.57.57 or later.

• The iDRAC8 firmware version must be 2.05.05 or later.

The iDRAC (on a server) resets and is temporarily unavailable after a firmware update.

Updating Server iDRAC Firmware Using Web Interface

To update the iDRAC firmware in the server:

1. Go to any of the following pages:

• Chassis Overview → Update.

• Chassis Overview → Chassis Controller → Update.

The Firmware Update page is displayed.

NOTE: You can also update server iDRAC firmware using Chassis Overview → Server Overview →

Update. For more information, see Upgrading Server Component Firmware

2. To update the iDRAC7 or iDRAC8 firmware, in the iDRAC<revision number> Enterprise Firmware

section, click the Update link of the server for which you want to update the firmware. The Server Component Update page is displayed. To continue, see Updating Server Component

Firmware.

Updating Server Component Firmware

The one-to-many update feature in CMC enables you to update server component firmware across multiple servers. You can update the server components using the Dell Update Packages available on the

local system or on a network share. This operation is enabled by leveraging the Lifecycle Controller functionality on the server.

The Lifecycle Controller service is available on each server and is facilitated by iDRAC. You can manage the firmware of the components and devices on the servers using the Lifecycle Controller service. The Lifecycle Controller uses an optimization algorithm to update the firmware that efficiently reduces the number of restarts.

The Lifecycle Controller provides module update support for iDRAC7 and later servers. The iDRAC firmware must be at version 2.3 or later to update firmware using Lifecycle Controller.

Dell Update Packages (DUPs) are used to perform the firmware updates using Lifecycle Controller. The Operating System Driver Pack component DUP exceeds this limit and must be updated separately using the Extended Storage feature.

NOTE: Before using the Lifecycle Controller–based update feature, server firmware versions must be updated. You must also update the CMC firmware before updating the server component firmware modules.

NOTE: To update component firmware, the CSIOR option must be enabled for servers. To enable CSIOR on:

• 12th generation servers and later— After restarting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes.

• 13th generation servers —After rebooting the server, when prompted, press F10 to access Lifecycle Controller. Go to the

→ Hardware Inventory. On the Hardware Inventory page, click Collect System Inventory on Restart.

Hardware Inventory page by selecting Hardware Configuration

The Update from File method enables you to update the server component firmware using DUP files stored on a local system. You can select the individual server components to update the firmware using the required DUP files. You can update large number of components at a time by using an SD Card to store DUP file of more than 48 MB memory size.

NOTE: Note the following:

• While selecting the individual server components for update, make sure that there are no dependencies between the selected components. Else, 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. Else, the process of component firmware update may become unsuccessful.

Always update the server component firmware modules in the following order:

– iDRAC – Lifecycle Controller – BIOS

The Single Click all blade update or the Update from Network Share method enables you to update the server component firmware using DUP files stored on a network share. You can use the Dell Repository Manager (DRM) based update feature to access the DUP files stored on a network share and update the

server components in a single operation. You can setup a custom remote repository of firmware DUPs and binary images using the Dell Repository Manager and share it on the Network Share. Alternatively, use the Dell Repository Manager (DRM) to check for the latest available firmware updates. The Dell Repository Manager (DRM) ensures that the Dell systems are up-to-date with the latest BIOS, driver, firmware, and software. You can search for the latest updates available from the Support site (support.dell.com) for supported platforms based on Brand and Model or a Service Tag. You can download the updates or build a repository from the search results. For more information on using the DRM to search for latest firmware updates, refer to http://en.community.dell.com/TECHCENTER/ EXTRAS/M/WHITE_PAPERS/20438118/DOWNLOAD on the Dell Tech Center. For information on saving the inventory file that DRM uses as input to create the repositories, see Saving Chassis Inventory Report

Using CMC Web Interface

NOTE: The Single Click all blade update method has the following benefits:

• Enables you to update all the components on all the blade servers with minimal clicks.

• All the updates are packaged in a directory. This avoids individual upload of each component’s firmware.

• Faster and consistent method of updating the server components.

• Enables you to maintain a standard image with the required updates versions of the server components that can be used to update multiple servers in a single operation.

• You can copy the directories of updates from the Dell Server Update Utility (SUU) download DVD or create and customize the required update versions in the Dell Repository Manager (DRM). You do not need the latest version of the Dell Repository Manager to create this directory. However, Dell Repository Manager version 1.8 provides an option to create a repository (directory of updates) based on the inventory that was exported from the servers in the chassis. For information on creating a repository using the Dell Repository Manger see the

Manager Data Center Version 1.8 User’s Guide and the Dell Repository Manager Business Client Version 1.8 User’s Guide available at dell.com/support/manuals.

Dell Repository

It is recommended to update the CMC firmware before updating the server component firmware modules. After updating the CMC firmware, in the CMC Web interface, you can update the server component firmware on the Update page. It is also recommended to select all the component modules of a server to be updated together. This enables Lifecycle Controller to use its optimized algorithms to update the firmware, reducing the number of reboots.

To update the server component firmware, using the CMC Web interface, click Chassis Overview → Server Overview → Update → Server Component Update.

If the server does not support the Lifecycle Controller service, the Component/Device Firmware Inventory section displays Not Supported. For the latest generation servers, install the Lifecycle Controller firmware and update the iDRAC firmware to enable the Lifecycle Controller service on the server. For earlier generation servers, this upgrade is not possible.

Normally, the Lifecycle Controller firmware is installed using an appropriate installation package that is executed on the server operating system. For supported servers, a special repair or installation package with an .usc file extension is available. This file enables you to install the Lifecycle Controller firmware through the firmware update facility available on the native iDRAC Web browser interface.

You can also install Lifecycle Controller firmware through an appropriate installation package executed on the server OS. For more information, see the Dell Lifecycle Controller User’s Guide.

Chassis Overview → Server Overview → Update → Server Component

If Lifecycle Controller service is disabled on the server, the Component/Device Firmware Inventory section displays:

Lifecycle Controller may not be enabled.

Server Component Update Sequence

In case of individual component updates, you must update the firmware versions for the server components in the following sequence:

• iDRAC

• Lifecycle Controller

• BIOS

• Diagnostics (optional)

• OS Driver Pack (optional)

• RAID

• NIC

• CPLD

• 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.

Enabling Lifecycle Controller

You can enable the Lifecycle Controller service when turning on a server:

• For iDRAC servers, on the boot console, to access System Setup, press the <F2> key.

• On the System Setup Main Menu page, go to iDRAC Settings → Lifecycle Controller, click Enabled. Go to the System Setup Main Menu page and click Finish to save the settings.

• Cancelling System Services enables you to cancel all scheduled jobs that are pending and remove them from the queue. For more information about the Lifecycle Controller and supported server components, and device firmware management, see Lifecycle Controller-Remote Services Quick Start Guide or delltechcenter.com/page/Lifecycle+Controller.

• The Server Component Update page enables you to update various firmware components on the server. To use the features and functions on this page, you must have:

– For CMC: The Server Administrator privilege.

– For iDRAC: The configure iDRAC privilege and log in to iDRAC privilege.

In case of insufficient privileges, you can only view the firmware inventory of components and devices on the server. You cannot select any components or devices for any type of Lifecycle Controller operation on the server.

Choosing Server Component Firmware Update Type Using CMC Web Interface

To select the type of server component update type:

1. In the system tree, go to Server Overview, and then click Update → Server Component Update. The

Server Component Update page is displayed.

2. In the Choose Update Type section, select the required update method:

• Update from File

• Update from Network Share

Filtering Components for Firmware Updates

Information about all the components and devices across all servers is retrieved at one time. To manage this large amount of information, Lifecycle Controller provides various filtering mechanisms.

NOTE: To use this feature, you must have an Enterprise License.

The Component/Device Update Filter section in the Server Component Update page that allows you to filter the information based on the component, is available only for the Update by File mode.

These filters enable you to:

• Select one or more categories of components or devices for easy viewing.

• Compare firmware versions of components and devices across the server.

• To narrow the category of a particular component or device based on types or models, automatically filter the selected components and devices.

NOTE: Automatic filtering feature is important while using the Dell Update Package (DUP). The update programming of a DUP can be based on the type or model of a component or device. The automatic filtering behavior is designed to minimize the subsequent selection decisions after an initial selection is made.

Following are some examples where the filtering mechanisms are applied:

• If the BIOS filter is selected, only the BIOS inventory of all the servers is displayed. If the set of servers consists of a number of server models, and a server is selected for BIOS update, the automatic filtering logic automatically removes all the other servers that do not match with the model of the selected server. This makes sure that the selection of the BIOS firmware update image (DUP) is compatible with the correct model of the server.

Sometimes, a BIOS firmware update image may be compatible across a number of server models. Such optimizations are ignored in case this compatibility is no longer true in the future.

• Automatic filtering is important for firmware updates of Network Interface Controllers (NIC) and RAID Controllers. These device categories have different types and models. Similarly, the firmware update images (DUP) may be available in optimized forms, where a single DUP may be programmed to update multiple types or models of devices of a given category.

Viewing Firmware Inventory

You can view the summary of the firmware versions for all components and devices for all servers currently present in the chassis along with their status.

NOTE: To use this feature, you must have an Enterprise License.

Viewing Firmware Inventory Using CMC Web Interface

To view the firmware inventory:

1. In the left pane, click Server Overview, and then click Update.

2. On the Server Component Update page, view the firmware inventory details in the Component/

Device Firmware Inventory section. On this page, you can view the following information:

• If the server is listed as Not Ready, it indicates that when the firmware inventory was retrieved, the

iDRAC on the server was still initializing. Wait for the iDRAC to be fully operational, and then refresh the page for the firmware inventory to be retrieved again.

• A hyperlink is provided to an alternative page, where you can directly update only the iDRAC firmware. This page supports only iDRAC firmware update and not any other component and device on the server. iDRAC firmware update is not dependent on the Lifecycle Controller service.

• If the inventory of components and devices do not reflect what is physically installed on the server, you must invoke the Lifecycle Controller when the server is in the boot process. This helps to refresh the internal components and devices information and allows you to verify the currently-installed components and devices. This occurs when:

– The server iDRAC firmware is updated to newly introduce the Lifecycle Controller

functionality to the server management.

– The new devices are inserted into the server.

To automate this action for the iDRAC Settings Utility you have an option that can be accessed through the boot console:

1. On the boot console, to access System Setup, press <F2>.

2. On the System Setup Main Menu page, click iDRAC Settings → Collect System Inventory on

Restart, select Enabled, go back to the System Setup Main Menu page, and then click Finish to save the settings.

• Options to perform the various Lifecycle Controller operations such as Update, Rollback, Reinstall, and Job Deletion are available. Only one type of operation can be performed at a time. Components and devices that are not supported may be listed as part of the inventory, but do not permit Lifecycle Controller operations.

The following table displays the component and devices information on the server:

Table 3. Component and Devices Information

Field Description

Slot Displays the slot occupied by the server in the chassis. Slot numbers are sequential

IDs for the four available slots in the chassis:

• 1, 1a, 1b, 1c, 1d

• 2, 2a, 2b, 2c, 2d

• 3, 3a, 3b, 3c, 3d

• 4, 4a, 4b, 4c, 4d

This numbering scheme helps you to identify the location of the server in the chassis. When there are less than four servers occupying slots, only those slots populated by servers are displayed.

Name Displays the name of the server in each slot.

Field Description

Model Displays the model of the server.

Component/ Device

Current Version

Rollback Version

Job Status Displays the job status of any operations that are scheduled on the server. The job

Update Click to select the component or device for firmware update on the server.

Displays a description of the component or device on the server. If the column width is too narrow, the mouse-over tool provides a view of the description.

Displays the current version of component or device on the server.

Displays the rollback version of component or device on the server.

status is continuously updated dynamically. If a job completion with state completed is detected, then the firmware versions for the components and devices on that server are automatically refreshed in case there has been a change of firmware version on any of the components or devices. An information icon is also presented adjacent to the current state, which provides additional information about the current job status. This information can be viewed by clicking or pausing the mouse over the icon.

Viewing Firmware Inventory Using RACADM

To view firmware inventory using RACADM, use the getversion command:

racadm getversion -l [-m <module>] [-f <filter>]

For more information, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals.

Saving Chassis Inventory Report Using CMC Web Interface

To save the chassis inventory report:

1. In the system tree, go to Server Overview, and then click Update → Server Component Update. The Server Component Update page is displayed.

2. Click Save Inventory Report. The Inventory.xml file is saved on an external system.

NOTE: The Dell Repository Manager Application uses the Inventory.xml file as an input to create a repository of updates for all the blades available in the chassis. This repository can be later exported to a network share. Update from Network Share mode of firmware update uses this network share to update the components of all the servers. You must have CSIOR enabled on the individual servers and save the chassis inventory report every time there is a change to the chassis hardware and software configuration.

Configuring Network Share Using CMC Web Interface

To configure or edit the Network Share location or credentials:

1. In the CMC Web interface, in the system tree, go to Server Overview and then click Network Share.

The Edit Network Share page is displayed.

2. 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 for Dell PowerEdge FX2/FX2s Online Help.

3. Click Test Directory to verify whether the directories are readable and writeable.

4. Click Test Network Connection to verify if the network share location is accessible.

5. Click Apply to apply the changes to the network share properties.

NOTE:

Click Back to return to the Server Component Update page.

Lifecycle Controller Job Operations

NOTE: To use this feature, you must have an Enterprise License.

You can perform Lifecycle Controller operations such as:

• Re-install

• Rollback

• Update

• Delete Jobs

Only one type of operation can be performed at a time. Components and devices that are not supported may be listed as part of the inventory, but do not permit Lifecycle Controller operations.

To perform the Lifecycle Controller operations, you must have:

• For CMC: Server Administrator privilege.

• For iDRAC: Configure iDRAC privilege and Log in to iDRAC.

A Lifecycle Controller operation scheduled on a server may take 10 to 15 minutes to complete. The process involves several server reboots during which the firmware installation is performed, which also includes a firmware verification stage. You can view the progress of this process using the server console. If there are several components or devices that need to be updated on a server, you can consolidate all the updates into one scheduled operation thus minimizing the number of reboots required.

Sometimes, when an operation is in the process of being submitted for scheduling through another session or context, another operation is attempted. In this case, a confirmation message is displayed

indicating the situation and the operation must not be submitted. Wait for the operation in process to complete and then submit the operation again.

Do not navigate away from the page after an operation is submitted for scheduling. If an attempt is made, a confirmation message is displayed allowing the intended navigation to be cancelled. Otherwise, the operation is interrupted. An interruption, especially during an update operation may cause the firmware image file upload to be terminated before proper completion. After an operation has been submitted for scheduling, ensure that the confirmation message indicating that the operation has been successfully scheduled is acknowledged.

Reinstalling Server Component Firmware

You can reinstall the firmware image of the currently installed firmware for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller.

Re-installing Server Component Firmware Using Web Interface

To reinstall a server component firmware:

1. In the left pane, click Server Overview → Update.

2. On the Server Component Update page, click the appropriate type in the Choose Update Type

section.

3. In the Current Version column, select the option for the component or device for which you want to reinstall the firmware.

4. Select one of the following options:

• Reboot Now — Restart the server immediately.

• On Next Reboot — Manually restart the server at a later time.

5. Click Reinstall. The firmware version is reinstalled for the selected component or device.

Rolling Back Server Component Firmware

You can install the firmware image of the previously installed firmware for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller for a rollback operation. The availability is subject to the version compatibility logic of the Lifecycle Controller. It also assumes the previous update was facilitated by the Lifecycle Controller.

NOTE: To use this feature, you must have an Enterprise License.

Rolling Back Server Component Firmware Using the CMC Web Interface

To roll back the server component firmware version to an earlier version:

1. In the left pane, click Server Overview → Update.

2. On the Server Component Update page, click the appropriate type in the Choose Update Type

section.

3. In the Rollback Version column, select the option for the component or device for which you want to roll back the firmware.

4. Select one of the following options:

• Reboot Now — Restart the server immediately.

• On Next Reboot - Manually restart the server at a later time.

5. Click Rollback. The previously installed firmware version is reinstalled for the selected component or device.

Upgrading Server Component Firmware

You can install the next version of the firmware image for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller for a rollback operation. To use this feature, you must have an Enterprise License.

NOTE: For iDRAC and Operating System Driver packs firmware update, make sure the Extended Storage feature is enabled.

It is recommended to clear the job queue before initializing a server component firmware update. A list of all jobs on the servers is available on the Lifecycle Controller Jobs page. This page enables deletion of single or multiple jobs or purging of all jobs on the server.

BIOS updates are specific to the model of the server. Sometimes, even though a single Network Interface Controller (NIC) device is selected for firmware update on a server, the update may get applied to all the NIC devices on the server. This behavior is inherent in the Lifecycle Controller functionality and particularly the programming contained with the Dell Update Package (DUP). Currently, Dell Update Packages (DUP) that are less than 85 MB in size are supported.

If the update file image size is greater, the job status indicates that the download has failed. If multiple server component updates are attempted on a server, the combined size of all the firmware update files may also exceed 85 MB. In such a case, one of the component updates fails as its update file is truncated. To update multiple components on a server, it is recommended to update the Lifecycle Controller and 32-Bit Diagnostics components together first. These do not require a server reboot and are relatively quick to complete. The other components can then be updated together.

All Lifecycle Controller updates are scheduled for immediate execution. However, the system services can delay this execution sometimes. In such situations, the update fails as a result of the remote share that is hosted by the CMC being no longer available.

Upgrading Server Component Firmware From File Using CMC Web Interface

To upgrade the server components firmware version to the next version using the Update from File method:

1. In the CMC Web interface, in the system tree, go to Server Overview and then click Update → Server Component Update.

The Server Component Update page is displayed.

2. In the Choose Update Type section, select Update from File. For more information, see Choosing

Server Component Firmware Update Type

3. In the Component/Device Update Filter section, filter the component or device (optional). For more information see CMC_Stmp_Filtering Components for Firmware Updates

4. In the Update column, select the checkbox(es) for the component or device for which you want to update the firmware to the next version. Use the CRTL key shortcut to select a type of component or device for update across all the applicable servers. Pressing and holding the CRTL key highlights all the components in yellow. While the CRTL key is pressed down, select the required component or device by enabling the associated check box in the

A second table is displayed that lists the selected type of component or device and a selector for the firmware image file. For each type of component, one selector for the firmware image file is displayed.

Update column.

Few devices such as Network Interface Controllers (NICs) and RAID Controllers contain many types and models. The update selection logic automatically filters the relevant device type or model based on the initially selected devices. The primary reason for this automatic filtering behavior is that only one firmware image file for the category can be specified.

NOTE: The update size limitation of either a single DUP or combined DUPs can be ignored if the Extended Storage feature is installed and enabled. For information on enabling extended storage, see Configuring CMC Extended Storage Card

5. Specify the firmware image file for the selected component(s) or devic(es). This is a Microsoft Windows Dell Update Package (DUP) file.

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.

Server Component Single Click Update Using Network Share

The Servers or server component update from a network share using Dell Repository Manager and Dell PowerEdge FX2/FX2s modular chassis integration simplifies the update by using customized bundle firmware, so that you can deploy faster and more easily. Update from a network share provides flexibility to update all the 12G server components at the same time with a single catalog either from a CIFS or from a NFS.

This method provides a quick and easy way to build a custom repository for connected systems that you own using the Dell Repository Manager and the chassis inventory file exported using the CMC Web interface. DRM enables you to create a fully customized repository that only includes the update packages for the specific system configuration. You can also build repositories that contain updates for only out-of-date devices, or a baseline repository that contains updates for all the devices. You can also create update bundles for Linux or Windows based on the update mode required. DRM enables you to save the repository to a CIFS or NFS share. The CMC Web interface enables you to configure the credentials and location details for the share. Using the CMC Web interface, you can then perform the server components update for a single server or multiple servers.

Pre-requisites for Using Network Share Update Mode

The following pre-requisites are required to update server component firmware using Network Share mode:

• The servers must have iDRAC Enterprise license

• Lifecycle controller must be enabled on servers..

• Dell Repository Manager 1.8 or later must be installed on the system.

• You must have CMC Administrator privileges.

Upgrading Server Component Firmware From Network Share Using CMC Web Interface

To upgrade the server components firmware version to the next version using the Update from Network Share mode:

1. In the CMC Web interface, in the system tree, go to Server Overview and then click Update → Server Component Update.

The Server Component Update page is displayed.

2. In the Choose Update Type section, select Update from Network Share. For more information, see

Choosing Server Component Firmware Update Type.

3. If the Network Share is not connected, configure the Network Share for the chassis. To configure or edit the network share details, in the Network Share Properties table click Edit. For more information see Configuring Network Share Using CMC Web Interface.

4. Click Save Inventory Report to export the chassis inventory file that contains the components and firmware details.

The Inventory.xml file is saved on an external system. The Dell Repository Manager uses the inventory.xml file to create customized bundles of updates. This Repositry is stored in the CIFS or NFS Share configured by CMC. For information on creating a repository using the Dell Repository Manger see the Dell Repository Manager Data Center Version 1.8 User’s Guide and the Dell

Repository Manager Business Client Version 1.8 User’s Guide available at dell.com/support/manuals.

5. Click Check for Updates to view the firmware updates available in the network share.

The Component/Device Firmware Inventory section displays the current firmware versions of the components and devices across all the servers present in the chassis and firmware versions of the DUPs available in the Network Share.

NOTE: Click Collapse against a slot to collapse the component and device firmware details for the specific slot. Alternatively, to view all the details again, click Expand.

6. In the Component/Device Firmware Inventory section, select the check box against Select/ Deselect All to select all the supported servers. Alternatively, select the check box against the server

for which you want to update the server component firmware. You cannot select individual components for the server.

7. Select one of the following options to specify if a system reboot is required after the updates are scheduled:

• 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.

8. 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. Click OK to continue and complete scheduling the firmware update for the selected servers.

NOTE: The Job Status column displays the job status of the operations scheduled on the server. The job status is dynamically updated.

Deleting Scheduled Server Component Firmware Jobs

NOTE: To use this feature, you must have an Enterprise License.

You can delete jobs scheduled for the selected components and/or devices across one or more servers.

Deleting Scheduled Server Component Firmware Jobs Using the Web Interface

To delete scheduled server component firmware jobs:

1. In the left pane, click Server Overview, and then click Update.

2. On the Server Component Update page, filter the component or device (optional).

3. In the Job Status column, if a check box is displayed next to the job status, it implies that a Lifecycle

Controller job is in progress and currently in the indicated state. It can be selected for a job-deletion operation.

4. Click Delete Job. The jobs are deleted for the selected components or devices.

Recovering iDRAC Firmware Using CMC

iDRAC firmware is typically updated using iDRAC interfaces such as the iDRAC web interface, the SM-CLP command line interface, or operating system specific update packages downloaded from

support.dell.com. For more information, see the Dell Integrated Dell Remote Access Controller (iDRAC) User’s Guide .

Viewing Chassis Information and Monitoring Chassis and Component Health

You can view information and monitor the health of the following:

• CMC

• All severs and individual servers

• IO Modules

• Fans

• Power Supply Units (PSUs)

• Temperature sensors

• PCIe devices

Viewing Chassis and Component Summaries

When you log in to the CMC web interface, the Chassis Health page displays the health of the chassis and its components. It displays a graphical view of the chassis and its components. It is dynamically updated, and the component sub-graphic overlays and text hints are automatically changed to reflect the current state.

To view the chassis health, click Chassis Overview. The system displays the overall health status of the chassis, CMC, server modules, IO Modules (IOM), fans, power supply units (PSUs), and PCIe devices. Detailed information about each component is displayed when you click that component. In addition, the latest events in the CMC Hardware Log are also displayed. For more information, see the Dell Integrated Dell Remote Access Controller (iDRAC) User’s Guide .

If your chassis is configured as a Group Lead, the Group Health page is displayed after login. It displays the chassis level information and alerts. All active, critical, and non-critical alerts are displayed.

Chassis Graphics

The chassis is represented by the front, back, and the top views (the upper and lower images respectively). Servers, and KVMs are shown in the front view and the remaining components are shown in the back view. Component selection is indicated by a blue cast and is controlled by clicking the image of the required component. When a component is present in the chassis, an icon of the component type is displayed 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. Pausing the cursor over a component displays a tool tip with additional information about that component.

Selected Component Information

Information for the selected component is displayed in three independent sections:

• Health and Performance, and Properties — Displays the active, critical, and non-critical events as

displayed by the hardware logs and the performance data that vary with time.

• Properties — Displays the component properties that do not vary with time, or that change only

infrequently.

• Quick Links — Provides links to navigate to the most frequently accessed pages, and also the most

frequently performed actions. Only links applicable to the selected component are displayed in this section.

The following table lists the component properties and information displayed on the Chassis Health page in Web interface.

ComponentHeath and Performance

CMC • MAC Address

All Servers and Individual Servers

Properties

• IPv4

• IPv6

• Power State

• Power Consumtion

• Health

• Power Allocated

• Temperature

Properties Quick Links

• Firmware

• Standby Firmware

• Last Update

• Hardware

• Name

• Model

• Service Tag

• Host Name

• iDRAC

• CPLD

• BIOS

• OS

• CPU Information

• Total System Memory

• CMC Status

• Networking

• Firmware Update

• Server Status

• Launch Remote Console

• Launch iDRAC GUI

• Power Off Server

• Graceful Shutdown

• Remote File Share

• Deploy iDRAC Network

• Server Component Update

NOTE: Quick links for Power Off Server and Graceful Shutdown are displayed only if the Server Power state is On. If the Server Power State is Off, then the quick link for Power On Server is displayed instead.

Power Supply Units

Power Status Capacity

• Power Supply Status

• Power Consumption

• System Budget

ComponentHeath and Performance

Properties

Properties Quick Links

PCIe Devices

Fans • Speed

IOM Slot • Power State

• Installed

• Assigned

• PWM (% of Max)

• Fan Offset

• Role

• Model

• Mapping

• Vendor ID

• Device ID

• Slot Type

• Module Type

• Fabric

• Power Status

• Warning Threshold

• Critical Threshold

• Model

• Service Tag

• PCIe Status

• PCIe Setup

• Fans Status

• Fan Configuration

IOM Status

Viewing Server Model Name and Service Tag

You can view the model name and service tag of each server instantly using the following steps:

1. In the left pane, under Server Overview tree node, all the servers (SLOT-01 to SLOT-04) appear in

the servers list. If a server is not present in a slot, the corresponding image in the graphic is grayed out.

2. Pause the cursor over the slot name or slot number of a server. A tool tip is displayed with the server’s model name and service tag (if available).

Viewing Chassis Summary

To view the chassis summary information, in the left pane, click Chassis Overview → Properties → Summary.

The Chassis Summary page is displayed. For more information about this page, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Viewing Chassis Controller Information and Status

To view the chassis controller information and status, in the CMC Web interface, click Chassis Overview → Chassis Controller.

The Chassis Controller Status page is displayed. For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Viewing Information and Health Status of All Servers

To view the health status of all the servers, do one of the following:

• Click Chassis Overview. The Chassis Health page displays a graphical overview of all the servers

installed in the chassis. Server health status is indicated by the overlay of the server subgraphic. For more information about the chassis health, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

• Click Chassis Overview → Server Overview. The Servers Status page provides an overview of the

servers in the chassis. For more information, see the Online Help.

Viewing Information and Health Status of the IOMs

To view health status of the IOMs, in the CMC Web interface, do any of the following:

1. Click Chassis Overview .

The Chassis Health page is displayed. The graphics in the left pane displays the rear, front, and top view of the chassis and contains the health status for the IOM. IOM health status is indicated by the overlay of the IOM sub-graphic. Move the cursor over the individual IOM sub-graphic. The text hint provides additional information about that IOM. Click the IOM sub-graphic to view the IOM information in the right pane.

2. Go to Chassis Overview → I/O Module Overview .

The I/O Module Status page provides an overview of IOM associated with the chassis. For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Viewing Information and Health Status of Fans

CMC controls the speed of the chassis fan by increasing or decreasing the fan speed on the basis of system events. You can run the fan in three modes such as Low, Medium, and High (fan offset). For more information about configuring a fan, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

To set up the properties of fans by using RACADM commands, type the following command at the CLI interface.

racadm fanoffset [-s <off|low|medium|high>]

NOTE: The CMC monitors the temperature sensors in the chassis and automatically adjust the fan speed as needed. When overridden using this command, the CMC will always run the fan to the selected speed even though the chassis does not require the fans to run at that speed. However, you can override to maintain a minimum fan speed by the racadm fanoffset command.

For more information about the RACADM commands, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals.

CMC generates an alert and increases the fan speeds when the following events occur:

• CMC ambient temperature threshold is exceeded.

• A fan stops functioning.

• A fan is removed from the chassis.

NOTE: During updates of CMC or iDRAC firmware on a server, some or all of the fan units in the chassis rotates at 100%. This is normal.

To view the health status of fans, in the CMC Web interface, do any of the following:

1. Go to Chassis Overview.

The Chassis Health page is displayed. The upper right section of chassis graphics provides the top left view of the chassis and contains the health status of the fans. Fan health status is indicated by the overlay of the fan sub-graphic. Move the cursor over the fan sub-graphic. The text hint provides additional information about a fan. Click the fan sub-graphic to view the fan information in the right pane.

2. Go to Chassis Overview → Fans.

The Fans Status page provides the status, speed measurements in revolutions per minute (RPMs), and threshold values of the fans in the chassis. There can be one or more fans.

NOTE: In the event of a communication failure between CMC and the fan unit, CMC cannot obtain or display the health status for the fan unit.

NOTE: The following message is displayed when both the fans are not present in the slots or if a fan is rotating at a low speed:

Fan <number> is less than the lower critical threshold.

For more information, see the Online Help.

Configuring Fans

Fan Offset — This feature allows you to increase the airflow delivery to the PCIe card slots. An example

usage of the Fan Offset is when you use high-power or custom PCIe cards that require more cooling than normal. The Fan Offset feature has options of Off, Low, Medium, and High. These settings correspond to a fan speed offset (increase) of 20%, 50%, and 100% of the maximum speed respectively. There are also minimum speeds setup for each option, which are 35% for Low, 65% for Medium, and 100% for High.

Using the Medium Fan Offset setting for example, increases the speed of fans by 50% of its maximum speed. The increase is above the speed already set by the system for cooling on the basis of installed hardware configuration.

With any of the Fan Offset options enabled, the power consumption will be increased. The system will be louder with the Low offset, noticeably louder with the Medium offset, and significantly louder with the High offset. When the Fan Offset option is not enabled, the fan speeds will be reduced to the default speeds required for system cooling for the installed hardware configuration.

To set the offset feature, go to Chassis Overview → Fans → Setup. On the Advanced Fan Configuration page, from the Value drop-down menu corresponding to Fan Offset, select appropriately.

For more information about the Fan Offset feature, see the Online Help.

For setting up these features by using RACADM commands, user the following command:

racadm fanoffset [-s <off|low|medium|high>]

Viewing Front Panel Properties

To view the front panel properties:

1. In the left pane, click Chassis Overview → Front Panel.

2. On the Properties page, you can view the following:

• Power Button Properties

• KVM Properties

• Front Panel Indicators

Viewing KVM Information and Health Status

To view the health status of the KVMs associated with the chassis, do any of the following:

Click Chassis Overview → Front Panel.

On the Status page, under the KVM Properties section, you can view the status and properties of a KVM associated with the chassis. For more information, see the Online Help.

Viewing Information and Health Status of Temperature Sensors

To view the health status of the temperature sensors:

In the left pane, click Chassis Overview → Temperature Sensors. The Temperature Sensors Status page displays the status and readings of the temperature probes on

the entire chassis (chassis and servers). For more information, see Online Help.

NOTE: The temperature probes value cannot be edited. Any change beyond the threshold generates an alert that causes the fan speed to vary. For example, if the CMC ambient temperature probe exceeds the threshold, the speed of the fans on the chassis increases.

Configuring CMC

Chassis Management Controller enables you to configure properties, set up users, and alerts to perform remote management tasks.

Before you begin configuring the CMC, you must first configure the CMC network settings to allow CMC to be managed remotely. This initial configuration assigns the TCP/IP networking parameters that enable access to the CMC.

You can configure CMC using Web interface or Setting up Initial Access to CMC RACADM.

NOTE: When you configure CMC for the first time, you must be logged in as root user to execute RACADM commands on a remote system. Another user can be created with privileges to configure CMC.

After setting up the CMC and performing the basic configurations, you can do the following:

• Modify the network settings, if required.

• Configure interfaces to access CMC.

• Setup chassis groups, if required.

• Configure servers, I/O module, or front panel.

• Configure VLAN settings.

• Obtain the required certificates.

• Add and configure CMC users with privileges.

• Configure and enable e-mail alerts and SNMP traps.

• Set the power cap policy, if required.

NOTE: The following characters cannot be used in the property strings of both the CMC interfaces (GUI and CLI):

• &#

• < and > together

• ; (semicolon)

Enabling or Disabling DHCP for the CMC Network Interface Address

When enabled, the CMC’s DHCP for NIC address feature requests and obtains an IP address from the Dynamic Host Configuration Protocol (DHCP) server automatically. This feature is disabled by default.

You can enable the DHCP to obtain an IP address from the DHCP server automatically.

Enabling the CMC Network Interface

To enable or disable the CMC network interface for both IPv4 and IPv6, type:

racadm config -g cfgLanNetworking -o cfgNicEnable 1 racadm config -g cfgLanNetworking -o cfgNicEnable 0

NOTE: If you disable CMC network interface, the disable operation performs the following actions:

• Disables the network interface access to out-of-band chassis management, including iDRAC and IOM management.

• Prevents the down link status detection.

To disable only CMC network access, disable both CMC IPv4 and CMC IPv6.

NOTE: The CMC NIC is enabled by default.

To enable or disable the CMC IPv4 addressing, type:

racadm config -g cfgLanNetworking -o cfgNicIPv4Enable 1 racadm config -g cfgLanNetworking -o cfgNicIPv4Enable 0

NOTE: The CMC IPv4 addressing is enabled by default.

To enable or disable the CMC IPv6 addressing, type:

racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 1 racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 0

NOTE: The CMC IPv6 addressing is disabled by default.

For an IPv4 network, to disable DHCP and specify static CMC IP address, gateway, and subnet mask, type:

racadm config -g cfgLanNetworking -o cfgNicUseDHCP 0 racadm config -g cfgLanNetworking -o cfgNicIpAddress <static IP address> racadm config -g cfgLanNetworking -o cfgNicGateway <static gateway> racadm config -g cfgLanNetworking -o cfgNicNetmask <static subnet mask>

By default, the DHCP is disabled. To enable DHCP and use the DHCP server on the network to assign iDRAC or CMC IPv4 address, subnet mask, and gateway, type:

racadm config -g cfgLanNetworking -o cfgNicUseDHCP 1

By default, for IPv6, the CMC requests and automatically obtains a CMC IP address from the IPv6 autoconfiguration mechanism.

For an IPv6 network, to disable the Autoconfiguration feature and specify a static CMC IPv6 address, gateway, and prefix length, type:

racadm config -g cfgIPv6LanNetworking -o cfgIPv6AutoConfig 0 racadm config -g cfgIPv6LanNetworking -o cfgIPv6Address <IPv6 address> racadm config -g cfgIPv6LanNetworking -o cfgIPv6PrefixLength 64 racadm config -g cfgIPv6LanNetworking -o cfgIPv6Gateway <IPv6 address>

Enabling or Disabling DHCP for DNS IP Addresses

By default, the CMC’s DHCP for DNS address feature is disabled. When enabled, this feature obtains the primary and secondary DNS server addresses from the DHCP server. While using this feature, you do not have to configure static DNS server IP addresses.

To enable the DHCP for DNS address feature and specify the static preferred and alternate DNS server addresses, type:

racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1

To enable the DHCP for DNS address feature for IPv6 and specify the static preferred and alternate DNS server addresses, type:

racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServersFromDHCP6 1

Setting Static DNS IP addresses

NOTE: The static DNS IP addresses settings are not valid unless the DCHP for DNS address feature is disabled.

For IPv4, to set the preferred primary and secondary DNS IP server addresses, type:

racadm config -g cfgLanNetworking -o cfgDNSServer1 <IP-address> racadm config -g cfgLanNetworking -o cfgDNSServer2 <IPv4-address>

For IPv6, to set the preferred and secondary DNS IP Server addresses, type:

racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer1 <IPv6-address> racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer2 <IPv6-address>

Viewing and Modifying CMC Network LAN Settings

The LAN settings, such as community string and SMTP server IP address, affect both the CMC and the external settings of the chassis.

When IPv6 is enabled at boot time, three router solicitations are sent after every four seconds. If external network switches are running the Spanning Tree Protocol (STP), the external switch ports may be blocked for more than 12 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.

NOTE: Changing the CMC network settings may disconnect your current network connection.

NOTE: You must have Chassis Configuration Administrator privilege to set up CMC network settings.

Viewing and Modifying CMC Network LAN Settings Using CMC Web Interface

To view and modify the CMC LAN network settings using CMC Web interface:

1. In the left pane, click Chassis Overview, and then click Network. The Network Configuration page

displays the current network settings.

2. Modify the general, IPv4, or IPv6 settings as required. For more information, see the Online Help.

3. Click Apply Changes for each section to apply the settings.

Viewing and Modifying CMC Network LAN Settings Using RACADM

To view IPv4 settings, use the object cfgCurrentLanNetworking with the following subcommands:

• getniccfg

• getconfig

To view IPv6 settings, use the cfgIpv6LanNetworking with the getconfig subcommand.

To view IPv4 and IPv6 addressing information for the chassis, use the getsysinfo subcommand.

For more information about the subcommands and objects, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

Configuring DNS Settings (IPv4 and IPv6)

• CMC Registration — To register the CMC on the DNS server, type:

racadm config -g cfgLanNetworking -o cfgDNSRegisterRac 1

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-<service tag>. To change the

CMC name on the DNS server, type:

racadm config -g cfgLanNetworking -o cfgDNSRacName <name>

where < name > is a string of up to 63 alphanumeric characters and hyphens. For example: cmc-1, d-345.

NOTE: If a DNS Domain name is not specified then the maximum number of characters is 63. If a domain name is specified then the number of characters in CMC name plus the number of characters in the DNS Domain Name must be less than or equal to 63 characters.

• DNS Domain Name — The default DNS domain name is a single blank character. To set a DNS

domain name, type:

racadm config -g cfgLanNetworking -o cfgDNSDomainName <name>

where < name > is a string of up to 254 alphanumeric characters and hyphens. For example: p45, atz-1, r-id-001.

Configuring Auto Negotiation, Duplex Mode, and Network Speed (IPv4 and IPv6)

When enabled, the auto negotiation feature determines whether the CMC automatically sets the duplex mode and network speed by communicating with the nearest router or switch. By default, auto negotiation feature is enabled.

You can disable auto negotiation and specify the duplex mode and network speed by typing:

racadm config -g cfgNetTuning -o cfgNetTuningNicAutoneg 0 racadm config -g cfgNetTuning -o cfgNetTuningNicFullDuplex <

where:

< duplex mode > is 0 (half duplex) or 1 (full duplex, default)

racadm config -g cfgNetTuning -o cfgNetTuningNicSpeed <speed>

where:

< speed > is 10 or 100 (default).

duplex mode>

Configuring Management Port 2

The second network port on the CMC can be used for daisy-chaining CMCs together for cable reduction, or as a redundant port for failover networking operation. Management Port 2 may be connected to the top-of-rack (TOR) switch or to another switch. There is no requirement that the two CMC NIC ports be connected to the same subnet.

The CMC cannot be cabled for Management Network Port redundancy prior to actually configuring it for this operation. The CMC must use the standard single network connection for deployment, after which the second redundant connection may be made.

NOTE: When Management Port 2 is set for Redundant but is cabled for Stacking, the downstream CMCs (further from the TOR switch) will not have a network link.

NOTE: When Management Port 2 is set for Stacking but is cabled for Redundant (two connections to the TOR switch), routing loops could cause a network storm.

To specify Redundant operation, use racadm config –g cfgNetTuning –o

cfgNetTuningNicRedundant 1

To specify Stacking operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 0 command.

By default, the Management Port 2 is set for Stacking.

command.

Configuring Management Port 2 Using CMC Web Interface

To configure Management Port using CMC Web Interface:

1. In the left pane, click Chassis Overview → Network, and then click the Network tab.

2. On the Network Configuration page, in the General Settings section, next to Management Port 2, select either Redundant or Stacking.

3. Click Apply Changes.

• When Management Port 2 is set for Redundant but is cabled for Stacking, the downstream CMCs

(further from the top-of-rack switch) does not have a network link.

• When Management Port 2 is set for Stacking but is cabled for Redundant (two connections to the

TOR switch), routing loops could cause a network storm.

Configuring Management Port 2 Using RACADM

To specify Redundant operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 1 command.

To specify Stacking operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 0 command.

By default, the Management Port 2 is set for Stacking.

Configuring Services

You can configure and enable the following services on CMC:

• CMC serial console — Enable access to CMC using the serial console.

• Web Server — Enable access to CMC web interface. Disabling the web server also disables Remote

RACADM.

• SSH — Enable access to CMC through firmware RACADM.

• Telnet — Enable access to CMC through firmware RACADM

• Remote RACADM — Enable access to CMC using RACADM.

• SNMP — Enable CMC to send SNMP traps for events.

• Remote Syslog — Enable CMC to log events to a remote server. To use this feature, you must have an

Enterprise license.

NOTE: When modifying CMC service port numbers for SSH, Telnet, HTTP, or HTTPS, avoid using commonly used ports 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/servicenames-port-numbers.xhtml.

CMC includes a web server that is configured to use the industry-standard SSL security protocol to accept and transfer encrypted data from and to clients over the Internet. The web server includes a Dell self-signed SSL Digital Certificate (Server ID), and is responsible for accepting and responding to secure HTTP requests from clients. This service is required by the web interface and remote RACADM CLI tool for communicating with CMC.

If the web server resets, wait at least one minute for the services to become available again. A web server reset usually happens as a result of any of the following events:

• Network configuration or network security properties are changed through the CMC web user

interface or RACADM.

• Web server port configuration is changed through the web user interface or RACADM.

• CMC is reset.

• A new SSL server certificate is uploaded.

NOTE: To modify service settings, you must have the Chassis Configuration Administrator privilege.

Remote syslog is an additional log target for CMC. After you configure the remote syslog, each new log entry generated by CMC is forwarded to the respective destinations.

NOTE: Because the network transport for the forwarded log entries is UDP, there is no guaranteed delivery of log entries, nor is there any feedback to CMC about whether the log entries were received successfully.

Configuring Services Using RACADM

To enable and configure the various services, use the following RACADM objects:

• cfgRacTuning

• cfgRacTuneRemoteRacadmEnable

For more information about these objects, see the Chassis Management Controller for PowerEdge FX2/ FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals.

If the firmware on the server does not support a feature, configuring a property related to that feature displays an error. For example, using RACADM to enable remote syslog on an unsupported iDRAC displays an error message.

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.

For example:

$ racadm getconfig -g cfgSessionManagement -m server-1 # cfgSsnMgtWebServerMaxSessions=N/A # cfgSsnMgtWebServerActiveSessions=N/A # cfgSsnMgtWebServerTimeout=N/A # cfgSsnMgtSSHMaxSessions=N/A # cfgSsnMgtSSHActiveSessions=N/A # cfgSsnMgtSSHTimeout=N/A # cfgSsnMgtTelnetMaxSessions=N/A # cfgSsnMgtTelnetActiveSessions=N/A # cfgSsnMgtTelnetTimeout=N/A

Configuring CMC Extended Storage Card

You can enable or repair the optional Removable Flash Media for use as an extended non-volatile storage. Some CMC features depend on extended nonvolatile storage for their operation.

To enable or repair the Removable Flash Media using the CMC web interface:

1. In the left pane, go to Chassis Overview, and then click Chassis Controller → Flash Media.

2. On the Removable Flash Media page, from the drop-down menu, select one of the following as

appropriate:

• Repair active controller media

• Stop using flash media for storing chassis data

For more information about these options, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

3. Click Apply to apply the selected option.

Setting Up Chassis Group

CMC enables you to monitor multiple chassis from a single lead chassis. When a chassis group is enabled, CMC in the lead chassis generates a graphical display of the status of the lead chassis and all member chassis within the chassis group. To use this feature, you must have an Enterprise License.

The Chassis group features are:

• Displays images portraying the front and back of each chassis, a set for the leader and a set for each

member.

• Health concerns for the leader and members of a group are recognized by red or yellow overlays and

an X or an ! on the component with the symptoms. Details are visible below the chassis image when you click the chassis image or Details.

• Quick launch links are available to open web pages for member chassis or servers.

• A server and Input/Output inventory is available for a group.

• A selectable option is available to synchronize a new member’s properties to the leader’s properties

when the new member is added to the group.

A chassis group may contain a maximum of 19 members. Also, a leader or member can only participate in one group. You cannot join a chassis, either as a leader or member, that is part of a group to another group. You can delete the chassis from a group and add it later to a different group.

To set up the Chassis Group using the CMC web interface:

1. Log in with chassis administrator privileges to the leader chassis.

2. Click Setup → Group Administration.

3. On the Chassis Group page, under Role, select Leader. A field to add the group name is displayed.

4. Type 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.

When the chassis group is created, the GUI automatically switches to the Chassis Group page. The left pane indicates the group by the group name and the lead chassis, and the unpopulated member chassis appear in the left pane.

NOTE: When the chassis group is created, the Chassis Overview item in the tree structure is replaced with the name of the lead chassis.

Adding Members To Chassis Group

After the Chassis Group is setup, add members to the group by doing the following:

1. Log in with chassis administrator privileges to the leader chassis.

2. Select the lead chassis in the tree.

3. Click Setup → Group Administration.

4. Under Group Management, enter the member’s IP address or DNS name in the Hostname/IP

Address field.

NOTE: For MCM to function properly, you must use the default HTTPS port (443) on all group members and the leader chassis.

5. In the User Name field, enter a user name with chassis administrator privileges for the member

chassis.

6. Type the corresponding password in the Password field.

7. Optionally, select Sync New Member with Leader Properties to push leader properties to the

member. For more information about adding members to chassis group, see Synchronizing a New

Member With Leader Chassis Propertie.

8. Click Apply.

9. To add a maximum of eight members, complete the tasks in step 4 through step 8. The chassis

names of the new members appear in the Members dialog box.

NOTE: The credentials entered for a member are passed securely to the member chassis to establish a trust relationship between the member and lead chassis. The credentials are not persisted on either chassis, and are never exchanged again after the initial trust relationship is established.

Removing a Member from the Leader

You can remove a member from the group from the lead chassis. To remove a member:

1. Log in with chassis administrator privileges to the leader chassis.

2. In the left pane, select the lead chassis.

3. Click Setup → Group Administration.

4. From the Remove Members list, select the member’s name to be deleted, and then click Apply.

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.

Disbanding a Chassis Group

To disband a chassis group from the lead chassis:

1. Log in with administrator privileges to the leader chassis.

2. Select the lead chassis in the left pane.

3. Click Setup → Group Administration.

4. In the Chassis Group page, under Role, select None, and then click Apply.

The lead chassis then communicates to all the members that they have been removed from the group. The lead chassis can be assigned as a leader or member of a new group.

If a network issue prevents contact between the leader and the member, the member chassis may not receive the message. In this case, disable the member from the member chassis to complete the removal process.

Disabling an Individual Member at the Member Chassis

Sometimes a member cannot be removed from a group by the lead chassis. This can happen if network connectivity to the member is lost. To remove a member from a group at the member chassis:

1. Log in with chassis administrator privileges to the member chassis.

2. In the left pane, click Chassis Overview → Setup → Group Administration.

3. Select None, and then click Apply.

Launching the Web page of a Member Chassis or Server

You can access the web page of the member chassis, remote console of the server, or the web page of the iDRAC server from the lead chassis group page. If the member device has the same login credentials as the lead chassis, you can use the same credentials to access the member device.

NOTE: Single Sign On and Smart Card Login are not supported in Multiple Chassis Management. Launching members by Single Sign On from Lead chassis requires a common username/password between Lead and members. Use of common username/password works only with Active Directory, local, and LDAP users.

To navigate to member devices:

1. Log in to the lead chassis.

2. Select Group: name in the tree.

3. If a member CMC is the required destination, select Launch CMC for the required chassis.

If a server in a chassis is the required destination:

a. Select the image of the destination chassis. b. In the chassis image that appears in the Health section, select the server. c. In the box labeled Quick Links, select the destination device. A new window is displayed with the

destination page or login screen.

Propagating Leader Chassis Properties to Member Chassis

You can apply the properties from the leader to the member chassis of a group. To synchronize a member with the leader properties:

1. Login with administrator privileges to the leader chassis.

2. Select the Lead chassis in the tree.

3. Click Setup → Group Administration.

4. 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.

• Manual Propagation — Select this option for manual propagation of the chassis group leader properties with its members. The lead chassis property settings are propagated to group members only when a lead chassis administrator clicks Propagate.

5. In the Propagation Properties section, select the categories of lead configuration properties to be

propagated to member chassis. Select only those setting categories that you want identically configured, across all members of the

chassis group. For example, select Logging and Alerting Properties category, to enable all chassis in the group to share the logging and alerting configuration settings of the lead chassis.

6. Click Save. If On-Change Propagation is selected, the member chassis take on the properties of the leader. If

Manual Propagation is selected, click Propagate whenever you want to propagate the chosen settings to member chassis. For more information on propagation of leader chassis properties to member chassis, see the Online Help.

Synchronizing a New Member With Leader Chassis Properties

You can apply the properties from the leader to a newly added member chassis of a group. To synchronize a new member with the leader properties:

1. Log in with administrator privileges to the leader chassis.

2. Select the lead chassis in the tree structure.

3. Click Setup → Group Administration.

4. While adding a new member to the group, in the Chassis Group page, select Sync New Member with Leader Properties.

5. Click Apply. The member takes on the properties of the leader.

The following configuration service properties of several systems within the chassis are affected after synchronization:

Table 4. Configuration Service Properties

Property Navigation

SNMP configuration

Chassis remote logging

User authentication using LDAP and Active Directory services

Chassis alerts In the left pane, click Chassis Overview, and then

In the left pane, click Chassis Overview → Network → Services → SNMP.

In the left pane, click Chassis Overview → Network → Services → Remote Syslog.

In the left pane, click Chassis Overview → User

Authentication

click Alerts.

→ Directory Services.

Server Inventory for MCM group

A group is a lead chassis that has 0 to 19 chassis group members. The Chassis Group Health page displays all the member chassis and allows you to save the server inventory report to a file, using standard browser download capability. The report contains data for:

• All servers currently in all the group chassis (including the leader).

• Empty slots and extension slots.

Saving Server Inventory Report

To save the server inventory report using the CMC web interface:

1. In the left pane, select the Group.

2. On the Chassis Group Health page, click Save Inventory Report. The File Download dialog box is

displayed asking you to open or save the file.

3. Click Save and specify the path and file name for the server module inventory report.

NOTE: The chassis group leader and chassis group member chassis, and the server module in the associated chassis, must be turned on to get the most accurate server module inventory report.

Configuring Multiple CMCs Using RACADM

Using RACADM, you can configure one or more CMCs with identical properties. 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.

NOTE: Some configuration files contain unique CMC information (such as the static IP address) that must be modified before you export the file to other CMCs.

1. Use RACADM to query the target CMC that contains the desired configuration.

NOTE: The generated configuration file is myfile.cfg. You can rename the file. The .cfg file does not contain user passwords. When the .cfg file is uploaded to the new CMC, you must re-add all passwords.

2. Open a Telnet/SSH text console to the CMC, log in, and type:

racadm getconfig -f myfile.cfg

NOTE: Redirecting the CMC configuration to a file using getconfig -f is only supported with the remote RACADM interface.

3. Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database.

4. Use the newly created configuration file to modify a target CMC. At the command prompt, type:

racadm config -f myfile.cfg

5. Reset the target CMC that was configured. At the command prompt, type:

racadm reset

The getconfig -f myfile.cfg subcommand requests the CMC configuration for the CMC and generates the myfile.cfg file. If required, you can rename the file or save it to a different location.

You can run the getconfig command to perform the following actions:

• Display all configuration properties in a group (specified by group name and index).

• Display all configuration properties for a user by user name.

The config subcommand loads the information into other CMCs. The Server Administrator uses the config command to synchronize the user and password database.

Parsing Rules

• Lines that start with a hash character (#) are treated as comments.

A comment line must start in column one. A "#" character in any other column is treated as a # character.

Some modem parameters may include # characters in their strings. An escape character is not required. You may want to generate a .cfg from a racadm getconfig -f <filename> .cfg command, and then perform a racadm config -f <filename> .cfg command to a different CMC, without adding escape characters.

For example:

# # This is a comment [cfgUserAdmin] cfgUserAdminPageModemInitString= <Modem init # not a comment>

• All group entries must be surrounded by open- and close-brackets ([ and ]).

The starting [ character that denotes a group name must be in column one. This group name must be specified before any of the objects in that group. Objects that do not include an associated group name generate an error. The configuration data is organized into groups as defined in the database property chapter of the RACADM Command Line Reference Guide for iDRAC and CMC. The following example displays a group name, object, and the object’s property value:

[cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object name} {object value}

• All parameters are specified as "object=value" pairs with no white space between the object, =, or

value. White spaces that are included after the value are ignored. A white space inside a value string remains unmodified. Any character to the right of the = (for example, a second =, a #, [, ], and so on) is taken as-is. These characters are valid modem chat script characters.

[cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object value}

• The .cfg parser ignores an index object entry.

You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the first available index for that group.

The racadm getconfig -f <filename>.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 <groupname> -o <anchored object> -i <index 1-16> <unique anchor name>

• The line for an indexed group cannot be deleted from a .cfg file. If you do delete the line with a text

editor, RACADM stops when it parses the configuration file and alert you of the error. You must remove an indexed object manually using the following command:

racadm config -g <groupname> -o <objectname> -i <index 1-16> ""

NOTE: A NULL string (identified by two " characters) directs the CMC to delete the index for the specified group.

To view the contents of an indexed group, run the following command:

racadm getconfig -g <groupname> -i <index 1-16>

• For indexed groups the object anchor must be the first object after the [ ] pair. The following are

examples of the current indexed groups:

[cfgUserAdmin] cfgUserAdminUserName= <USER_NAME>

• When using remote RACADM to capture the configuration groups into a file, if a key property within a

group is not set, the configuration group is not saved as part of the configuration file. If these configuration groups are needed to be cloned onto other CMCs, the key property must be set before executing the getconfig -f command. Alternatively, you can manually enter the missing properties into the configuration file after running the getconfig -f command. This is true for all the RACADM–indexed groups.

This is the list of the indexed groups that exhibit this behavior and their corresponding key properties:

– cfgUserAdmin — cfgUserAdminUserName – cfgEmailAlert — cfgEmailAlertAddress – cfgTraps — cfgTrapsAlertDestIPAddr – cfgStandardSchema — cfgSSADRoleGroupName – cfgServerInfo — cfgServerBmcMacAddress

Modifying the CMC IP Address

When you modify the CMC IP address in the configuration file, remove all unnecessary <variable> = <value> entries. Only the actual variable group’s label with [ and ] remains, including the two <variable> = <value> entries pertaining to the IP address change.

Example:

# # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.10.110 cfgNicGateway=10.35.10.1

This file is updated as follows:

# # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.9.143 # comment, the rest of this line is ignored cfgNicGateway=10.35.9.1

The command racadm config -f <myfile>.cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.

Use this file to download company-wide changes or to configure new systems over the network with the command, racadm getconfig -f <myfile>.cfg.

NOTE: Anchor is a reserved word and should not be used in the .cfg file.

Configuring Servers

You can configure the following settings of a server:

• Slot Names

• iDRAC Network Settings

• DRAC VLAN Tag Settings

• First Boot Device

• Server FlexAddress

• Remote File Share

• BIOS Settings Using Server Clone

Configuring Slot Names

Slot names are used to identify individual servers. When choosing slot names, the following rules apply:

• Names may contain a maximum of 15 non-extended ASCII characters (ASCII codes 32 through 126).

Also standard, and special characters are allowed in the names.

• Slot names must be unique within the chassis. Slots should not have the same name.

• Strings are not case-sensitive. Server-1, server-1, and SERVER-1 are equivalent names.

• Slot names must not begin with the following strings:

– Switch– Fan– PS– DRAC– MC– Chassis – Housing-Left – Housing-Right – Housing-Center

• The strings Server-1 through Server-4 may be used, but only for the corresponding slot. For

example, Server-3 is a valid name for slot 3, but not for slot 4. However, Server-03 is a valid name for any slot.

NOTE: To change a slot name, you must have the Chassis Configuration Administrator privilege.

The slot name setting in the web interface resides on CMC only. If a server is removed from the chassis, the slot name setting does not remain with the server.

The slot name setting in the CMC web interface always overrides any change you make to the display name in the iDRAC interface.

To edit a slot name using the CMC Web interface:

1. In the left pane, go to Chassis Overview → Server Overview → Setup → Slot Names.

2. On the Slot Names page, edit the slot name, in the Slot Name field.

3. To use a server’s host name as slot name, select the Use Host Name for the Slot name option. This

overrides the static slot names with the server’s Host Name (or system name), if available. This requires the OMSA agent to be installed on the server. For more information about the OMSA agent, see the

4. To save the settings, click Apply.

To restore the default slot name (SLOT-01 through SLOT-4) on the basis of a server's slot position) to a server, click Restore Default Value.

Dell OpenManage Server Administrator User's Guide available at dell.com/support/manuals.

Configuring iDRAC Network Settings

To use this feature, you must have an Enterprise License. You can configure the iDRAC network configuration setting of a server. You can use the QuickDeploy settings to configure the default iDRAC network configuration settings and root password for severs that are installed later. These default settings are the iDRAC QuickDeploy settings.

For more information about iDRAC, see the iDRAC User’s Guide at dell.com/support/manuals.

Configuring iDRAC QuickDeploy Network Settings

Use the QuickDeploy Settings to configure the network settings for newly inserted servers. To enable and set the iDRAC QuickDeploy settings:

1. In the left pane, click Server Overview → Setup → iDRAC.

2. On the Deploy iDRAC page, in the QuickDeploy Settings section, specify the settings mentioned in

the following table. For more information about the fields, see the Online Help.

Table 5. QuickDeploy Settings

Setting Description

Action When Server is Inserted Select one of the following options from the list:

• No Action — No action is performed when

the server is inserted.

• QuickDeploy Only — Select this option to

apply iDRAC network settings when a new server is inserted in the chassis. The specified auto-deployment settings are used to configure the new iDRAC, which includes the root user password if Change Root Password is selected.

• Server Profile Only — Select this option to

apply server profile assigned when a new server is inserted in the chassis.

• Quick Deploy and Server Profile — Select

this option to first apply the iDRAC network

Setting Description

settings, and then to apply the server profile assigned when a new server is inserted in the chassis.

Set iDRAC Root Password on Server Insertion Select the option to change iDRAC root

password to match the value provided in the iDRAC Root Password field, when a server is inserted.

iDRAC Root Password When the 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 a chassis. The password can have 1 to 20 printable (including white spaces) characters.

Confirm iDRAC Root Password Allows you to retype the password provided in

the Password field.

Enable iDRAC LAN Enables or disables the iDRAC LAN channel. By

default, this option is cleared.

Enable iDRAC IPv4 Enables or disables IPv4 on iDRAC. By default,

this option is selected.

Enable iDRAC IPMI over LAN Enables or disables the IPMI over LAN channel

for each iDRAC present in the chassis. By default, this option is selected.

Enable iDRAC IPv4 DHCP Enables or disables DHCP for each iDRAC

present in the chassis. If this option is enabled, the fields QuickDeploy IP, QuickDeploy Subnet Mask, and QuickDeploy Gateway are disabled, and cannot be modified since DHCP is used to automatically assign these settings for each iDRAC. To select this option, you must select the Enable iDRAC IPv4 option. Quick Deploy IP address option is provided with two values 4 and

Reserved QuickDeploy IP Address Select the number of static IPv4 addresses

reserved for iDRACs in the chassis. The IPv4 addresses starting from Starting iDRAC IPv4 Address (Slot 1) are considered as reserved and assumed to be unused elsewhere in the same network. Quick Deploy feature does not work for servers that are inserted into slots for which there is no reserved static IPv4 address.

Starting iDRAC IPv4 Address (Slot 1) Specifies the static IP address of iDRAC in the

server, in slot 1 of the enclosure. The IP address

Setting Description

of each subsequent iDRAC is incremented by 1 for each slot from slot 1's static IP address. In the case where the IP address plus the slot number is greater than the subnet mask, an error message is displayed.

NOTE: The subnet mask and the gateway are not incremented such as the IP address.

For example, if the starting IP address is

192.168.0.250 and the subnet mask is

255.255.0.0 then the QuickDeploy IP address

for slot 4c is mask is 255.255.255.0, the QuickDeploy IP

address range is not fully within QuickDeploy Subnet

displayed when you click Save QuickDeploy Settings or Auto-Populate Using QuickDeploy Settings.

iDRAC IPv4 Netmask Specifies the QuickDeploy subnet mask that is

assigned to all newly inserted servers.

iDRAC IPv4 Gateway Specifies the QuickDeploy default gateway that

is assigned to all the DRAC present in the chassis.

192.168.0.265. If the subnet

error message is

Enable iDRAC IPv6 Enables IPv6 addressing for each iDRAC present

in the chassis that is IPv6 capable.

Enable iDRAC IPv6 Autoconfiguration Enables the iDRAC to obtain IPv6 settings

(address and prefix length) from a DHCPv6 server and also enables stateless address auto configuration. By default, this option is enabled.

iDRAC IPv6 Gateway Specifies the default IPv6 gateway to be assigned

to the iDRACs. The default value is "::".

iDRAC IPv6 Prefix Length Specifies the prefix length to be assigned for the

IPv6 addresses on the iDRAC. The default value is 64.

3. 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.

The QuickDeploy feature only executes when it is enabled, and a server is inserted in the chassis.

To copy the QuickDeploy settings into the iDRAC Network Settings section, click Auto-Populate Using QuickDeploy Settings. The QuickDeploy network configurations settings are copied into the corresponding fields in the iDRAC Network Configuration Settings table.

NOTE: Changes made to QuickDeploy fields are immediate, but changes made to one or more iDRAC server network configuration settings may require a couple of minutes to propagate from CMC to iDRAC. Clicking Refresh early may display only partially correct data for one or more iDRAC servers.

QuickDeploy IP Address Assignments For Servers

The following tables show the way that the QuickDeploy IP addresses assigned to the servers based on the sleds present in the FX2/FX2s Chassis:

• Two full-width sleds in the chassis:

• Four half-width sleds in the chassis:

NOTE: For QuickDeploy to assign IP addresses to the bottom sled, the Reserved QuickDeploy IPAddresses field must be set to 4 for the bottom sled iDRAC.

• Eight quarter-width sleds in the chassis:

• Four FM120x4 sleds in the chassis:

• Top row contains only quarter-width sleds and bottom row contains only half-width sleds:

• Top row contains only full-width sleds and bottom row contains only half-width sleds:

• Top row contains full-width sleds and bottom row contains only quarter-width sleds:

Modifying iDRAC Network Settings for Individual Server iDRAC

Using this feature, you can configure the iDRAC network configurations settings for each installed server. The initial values displayed for each of the fields are the current values read from the iDRAC. To use this feature, you must have an Enterprise License.

To modify the iDRAC Network Settings:

1. In the left pane, click Server Overview, and then click Setup. On the Deploy iDRAC page the iDRAC Network Settings section lists the iDRAC IPv4 and IPv6 network configuration settings of all the

installed servers.

2. Modify the iDRAC network settings as required for the servers.

NOTE: You must select the Enable LAN option to specify the IPv4 or IPv6 settings. For information about the fields, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

3. To deploy the setting to iDRAC, click Apply iDRAC Network Settings. Any changes made to the QuickDeploy Settings are also saved.

The iDRAC Network Settings table reflects future network configuration settings; the values shown for installed servers may or may not be the same as the currently installed iDRAC network configuration settings. Click Refresh to update the iDRAC Deploy page with each installed iDRAC network configuration settings after changes are made.

NOTE: Changes made to QuickDeploy fields are immediate, but changes made to one or more iDRAC server network configuration settings may require a couple of minutes to propagate from CMC to iDRAC. Clicking Refresh too soon may display only partially correct data for a one or more iDRAC servers.

Modifying iDRAC Network Settings Using RACADM

RACADM config or getconfig commands support the -m <module> option for the following configuration groups:

• cfgLanNetworking

• cfgIPv6LanNetworking

• cfgRacTuning

• cfgRemoteHosts

• cfgSerial

• cfgSessionManagement

For more information about the property default values and ranges, see the Dell Integrated Dell Remote

Access Controller (iDRAC) RACADM Command Line Reference Guide and Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/

support/manuals.

Configuring iDRAC VLAN Tag Settings

VLANs are used to allow multiple virtual LANs to co-exist on the same physical network cable and to segregate the network traffic for security or load management purposes. When you enable the VLAN functionality, each network packet is assigned a VLAN tag. VLAN tags are chassis properties. They remain with the chassis even when a component is removed.

Configuring iDRAC VLAN Tag Settings Using Web Interface

To configure VLAN for server:

1. Go to any of the following pages:

• In the left pane, click Chassis Overview → Network → VLAN.

• In the left pane, click Chassis Overview → Server Overview and click Setup → VLAN.

2. On the VLAN Tag Settings page, 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 for Dell PowerEdge FX2/FX2s Online Help.

3. Click Apply to save the settings.

Configuring iDRAC VLAN Tag Settings Using RACADM

• Specify the VLAN ID and priority of a particular server with the following command:

racadm setniccfg -m server-<n> -v <VLAN id> <VLAN priority>

The valid values for <n> are 1–4.

The valid values for <VLAN> are 1–4000 and 4021–4094. Default is 1.

The valid values for <VLAN priority> are 0–7. Default is 0.

For example:

racadm setniccfg -m server-1 -v 1 7

For example:

• To remove a server VLAN, disable the VLAN capabilities of the specified server's network:

racadm setniccfg -m server-<n> -v

The valid values for <n> are 1–16.

For example:

racadm setniccfg -m server-1 -v

Setting First Boot Device

You can specify the CMC first boot device for each server. This may not be the actual first boot device for the server, or may not even represent a device present in that server. It represents a device sent by CMC to the server and used as its first boot device of that server. This device can be set as the default first-boot device or an one-time device so that you can boot an image to perform tasks such as running diagnostics or reinstalling an operating system.

You can set the first boot device for the next boot only or for all subsequent reboots. You can also set the first boot device for the server. The system boots from the selected device on the next and subsequent reboots and remains as the first boot device in the BIOS boot order, until it is changed again either from the CMC web interface or from the BIOS boot sequence.

NOTE: The first boot device setting in CMC web Interface overrides the system BIOS boot settings.

The boot device that you specify must exist and contain a bootable media.

You can set the following devices for first boot. However, to set a device as a default first-boot device, select Default.

To not to override the server firmware version if the firmware version running on the server is same as the version available in the first boot device, select None.

You can set the following devices for first boot.

Table 6. Boot Devices

Boot Device Description

PXE Boot from a Preboot Execution Environment (PXE) protocol on the Network Interface

Card.

Hard Drive Boot using a Hard disk drive.

Local CD/DVD

BIOS Setup Boot during the BIOS setup.

Virtual Floppy Boot from a virtual floppy disk.

Virtual CD/DVD

Local SD Card

Remote File Share

BIOS Boot Manager

Lifecycle Controller

Local Floppy Boot from a floppy disk in the local floppy disk drive.

Boot from a CD or DVD drive on the server.

Boot from a Virtual CD or DVD drive.

Boot from the local SD (Secure Digital) card.

Boot from remote file share.

Boot using the BIOS boot manager.

Boot using the Lifecycle controller.

Setting First Boot Device For Multiple Servers Using CMC Web Interface

NOTE: To set the first boot device for servers, you must have the Server Administrator privileges or Chassis Configuration Administrator privileges, and the iDRAC login privileges.

To set the first boot device for multiple servers:

1. In the left pane, click Server Overview → Setup → First Boot Device. A list of servers is displayed.

2. In the First Boot Device column, from the drop-down menu corresponding to a server, select the

boot device you want to use for a server.

3. If you want the server to boot from the selected device every time it boots, clear the Boot Once option for the server. If you want the server to boot from the selected device only on the next boot cycle, select the Boot Once option for the server.

4. Click Apply to save the settings.

Setting First Boot Device For Individual Server Using CMC Web Interface

NOTE: To set the first boot device for servers, you must have Server Administrator privileges or Chassis Configuration Administrator privileges and iDRAC login privileges.

To set the first boot device for individual servers:

1. In the left pane, click Server Overview, and then click the server for which you want to set the first boot device.

2. Go to Setup → First Boot Device. The First Boot Device page is displayed.

3. From the First Boot Device drop-down menu, select the boot device you want to use for each server.

4. If you want the server to boot from the selected device every time it boots, clear the Boot Once option for the server. If you want the server to boot from the selected device only on the next boot cycle, select the

5. Click Apply to save the settings.

Boot Once option for the server

Setting First Boot Device Using RACADM

To set the first boot device, use the cfgServerFirstBootDevice object.

To enable boot once for a device, use the cfgServerBootOnce object.

For more information about these objects, see the Chassis Management Controller for PowerEdge FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals.

Configuring Sled Network Uplink

You can configure the Sled Network Uplink only on the PowerEdge FM120x4 sleds that contain an internal network switch.

To configure the Sled Network Uplink, go to Chassis Overview → Server Overview → Setup → Sled

Network Uplink

Select one of the following values for Sled network uplink configuration Property:

• Standard (aggregated): Uplink configuration where all four IOM uplink ports are configured in a single

trunk group and all LOMs are mapped to that group. This is selected by default.

• Network adapter isolation (enhanced security): Uplink configuration similar to standard, but routing

between local nodes is not allowed.

• Isolated networks: Uplink configuration where each node’s LOM1 is mapped to IOM A1 and LOM2 is

mapped to IOM A2.

Deploying Remote File Share

The Remote Virtual Media File Share feature maps a file from a share drive on the network to one or more servers through CMC to deploy or update an operating system. When connected, the remote file is accessible similar to a file that you can access on a local server. Two types of media are supported: floppy drives and CD/DVD drives.

To perform a remote file share operation (connect, disconnect, or deploy), you must have the Chassis Configuration Administrator or Server Administrator privileges. To use this feature, you must have an Enterprise license.

To configure the remote file share:

1. In the left pane, click Server Overview → Setup → Remote File Share.

2. On the Deploy Remote File Share page, type appropriate data in the fields. For more information

about the field descriptions, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

3. To connect to a remote file share, click Connect. To connect a remote file share, you must provide

the path, user name, and password. A successful operation allows access to the media.

Click Disconnect to disconnect a previously-connected remote file share.

Click Deploy to deploy the media device.

NOTE: Before you click the Deploy button, make sure that you save all the working files, because this action restarts the server.

When you click Deploy, the following tasks are executed:

• The remote file share is connected.

• The file is selected as the first boot device for the servers.

• The server is restarted.

• Power is supplied to the server if the server is turned off.

Configuring Server FlexAddress

For information about configuring FlexAddress for servers, see Configuring FlexAddress for Chassis-Level

Fabric and Slots Using CMC Web Interface. To use this feature, you must have an Enterprise License.

Configuring Profile Settings Using Server Configuration Replication

The server configurations replicating feature allows you to apply all profile settings from a specified server to one or more servers. Profile settings that can be replicated are those profile settings which can be modified and are intended to be replicated across servers. The following three profile groups for servers are displayed and can be replicated:

• BIOS — This group includes only the BIOS settings of a server.

• BIOS and Boot — This group includes the BIOS and the Boot settings of a server.

• All Settings — This version includes all the settings of the server and components on that server. These

profiles are generated from:

– 12th generation servers with iDRAC7 1.57.57 or later and Lifecycle Controller 2 version 1.1 or later – 13th generation servers with iDRAC8 2.05.05 with Lifecycle Controller 2.00.00.00 or later.

The server cloning feature supports iDRAC7 and iDRAC8 Servers. Earlier generation RAC servers are listed, but are greyed out on the main page, and are not enabled to use this feature.

To use the server configurations replication feature:

• iDRAC must have the minimum version that is required. iDRAC7 servers require version 1.57.57.

iDRAC8 servers require version 2.05.05.

• Server must be turned on.

You can:

• View profile settings on a server or from a saved profile.

• Save a profile from a server.

• Apply a profile to other servers.

• Import stored profiles from a management station or remote file share.

• Edit the profile name and description.

• Export stored profiles to a management station or remote file share.

• Delete stored profiles.

• Deploy selected profiles to the target devices using Quick Deploy option.

• Display the log activity for recent server profile tasks.

Accessing Profile Page

You can add, manage, and apply profiles to one or more servers using the Profile page. To access the Profile page using the CMC Web interface, in the left pane, click Chassis Overview →

Server Overview → Setup → Profiles. The Profiles page is displayed.

Managing Stored Profiles

You can edit, view, or delete BIOS profiles. To manage the stored profiles of a CMC:

1. In the left pane, click Chassis Overview → Server Overview → Setup → Profiles.

2. On the Profiles page, in the Apply Profile section, click Manage Profiles. The Manage BIOS Profiles

page is displayed.

• To edit a profile, click Edit.

• To view BIOS settings, click View.

• To delete a profile, click Delete. For more information about the field descriptions, see the CMC for

Dell PowerEdge FX2/FX2s Online Help.

Adding or Saving Profile

Before copying the properties of a server, first capture the properties to a stored profile. Create a stored profile and provide a name and optional description for each profile. You can save a maximum of 16 stored profiles on the CMC nonvolatile extended storage media.

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 non-volatile extended storage media prevents access to Stored Profiles, and disables the Server Cloning feature.

To add a profile:

1. Go to the Server Profiles page. In the Server Profiles section, click Apply and Save Profiles.

2. Select the server from whose settings you want to generate the profile, and then click Save Profile. The Save Profile section is displayed.

3. Select Extended Storage or Network Share as the location to save the profile.

NOTE: The Network Share option is enabled and the details are displayed in the Stored Profiles section only if the network share is mounted and is accessible. If the Network Share is not connected, configure the Network Share for the chassis. To configure the Network Share, click Edit in the Stored Profiles section. For more information, see Configuring Network Share Using

CMC web Interface

4. In the Profile Name and Description fields, enter the profile name and description (optional), and click Save Profile.

NOTE: When saving a Server Profile the list of characters that are not supported for the Profile Name

include the character hash (#), comma (,) and question mark (?).

The standard ASCII extended character set is supported. The following special characters are not supported:

), “, ., *, >, <, \, /, :, and |

CMC communicates with the LC to get the available server profile settings and store them as a named profile.

A progress indicator indicates that the Save operation is in progress. After the action is complete, a message, "Operation Successful" is displayed.

NOTE: The process to gather the settings runs in the background. Hence, it may take some time before the new profile is displayed. If the new profile is not displayed, check the profile log for errors.

Applying Profile

Server cloning is possible only when server profiles are available as stored profiles in the nonvolatile media on the CMC or stored on the remote share. To initiate a server cloning operation, you can apply a stored profile to one or more servers.

The operation status, slot number, slot name, and model name is displayed for each server in the Apply Profile table.

NOTE: If a server does not support Lifecycle Controller or the chassis is turned off, you cannot apply a profile to the server.

To apply a profile to one or more servers:

1. Go to the Server Profiles page. In the Save and Apply Profiles section, select the server or servers for which you want to apply the selected profile.

The Select Profile drop-down menu gets enabled.

NOTE: The Select Profile drop-down menu displays all available profiles and sorted by type, including those that are on the repository and SD card.

2. From the Select Profile drop-down menu, select the profile that you want to apply. The Apply Profile option gets enabled.

3. Click Apply Profile. A warning message is displayed that applying a new server profile overwrites the current settings and

also reboots the selected servers. You are prompted to confirm if you want to continue the operation.

NOTE: To perform server cloning operations on servers, the CSIOR option must be enabled for the servers. If CSIOR option is disabled, a warning message is displayed that CSIOR is not enabled for the servers. To complete the blade cloning operation, make sure to enable CSIOR option on the servers.

4. Click OK to apply the profile to the selected server. The selected profile is applied to the servers and the servers may be rebooted immediately, if

necessary. For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Importing Profile

You can import a server profile that is stored on a management station to CMC. To import a stored profile from CMC:

1. In the Server Profiles page, in the Stored Profiles section, click Import Profile. The Import Server Profile section is displayed.

2. Click Browse to access the profile from the required location and then click Import Profile. For more information, see the Online Help.

Exporting Profile

You can export a stored server profile to a specified path on a management station. To export a stored profile:

1. Go to the Server Profiles page. In the 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.

NOTE: If the source profile is on the SD card, then a warning message is displayed that if the profile is exported, then the description is lost. Press OK to continue exporting the profile.

A message is displayed prompting you to select the destination of the file:

• Local or Network Share if the source file is on a SD card.

Network Share Using CMC web Interface

• Local or SD Card if the source file is on the Network Share.

For more information, see the Online Help.

3. Select Local, Extended Storage, or Network Share as the destination location based on the options displayed.

• If you select Local, a dialog box appears allowing you to save the profile to a local directory.

• If you select Extended Storage or Network Share, a Save Profile dialog box is displayed.

4. Click Save Profile to save the profile to the selected location.

Editing Profile

You can edit the name and description of a server profile that is stored on the CMC nonvolatile media (SD Card).

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.

The Edit BIOS Profile — <Profile Name> section is displayed.

2. Edit the profile name and description of the server profile as required and then click Edit Profile.

NOTE: You can edit the profile description only for profiles stored on SD cards.

For more information, see the Online Help.

Viewing Profile Settings

To view Profile settings for a selected server, go to the Server Profiles page. In the Server Profiles section, click View in the Server Profile column for the required server. The View Settings page is displayed.

For more information on the displayed settings, see the Online Help.

NOTE: The CMC Server Configuration Replication feature retrieves and displays the settings for a specific server, only if the Collect System Inventory on Restart (CSIOR) option is enabled.

To enable CSIOR, after rebooting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes.

To enable CSIOR on:

1. 12th generation servers — After rebooting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes.

2. 13th generation servers —After rebooting the server, when prompted, press F10 to access Lifecycle Controller. Go to the Hardware Inventory page by selecting Hardware Configuration → Hardware Inventory. On the Hardware Inventory page, click Collect System Inventory on Restart.

Viewing Stored Profile Settings

To view profile settings of the stored server profiles, go to the Server Profiles page. In the Server Profiles section, click View in the View Profile column for the required server. The View Settings page is displayed. For more information on the displayed settings, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Viewing Profile Log

To view the profile log, in the Server Profiles page, see the Recent Profile Log section. This section lists the 10 latest profile log entries directly from server cloning operations. Each log entry displays the severity, the time and date of submission of the server configuration replication operation, and the replication log message description. The log entries are also available in the RAC log. To view the other available entries, click Go to Profile Log. The Profile Log page is displayed. For more information, see the Online Help.

Completion Status And Troubleshooting

To check the completion status of an applied BIOS profile:

1. In the left pane, click Chassis Overview → Server Overview → Setup → Profiles.

2. On the Server Profiles page, note down the Job ID (JID) of the submitted job from the Recent Profile Log section.

3. In the left pane, click Server Overview → Troubleshooting → Lifecycle Controller Jobs. Search for

the same JID in the Jobs table. For more information about performing Lifecycle Controller jobs using CMC, see Lifecycle Controller Job Operations.

Quick Deploy of Profiles

The Quick Deploy feature enables you to assign a stored profile to a server slot. Any server supporting server configuration replication that is inserted into a slot is configured using the profile assigned to that slot. You can perform the Quick Deploy action only if the Action When Server is Inserted option in the Deploy iDRAC page is set to Server Profile or Quick Deploy and Server Profile. Selecting this option allows to apply the server profile assigned when a new server is inserted in the chassis. To go to the Deploy iDRAC page, select Server Overview → Setup → iDRAC . Profiles that can be deployed are contained in the SD card.

NOTE: To set up the profiles for quick deploy, you must have Chassis Administrator privileges.

Assigning Server Profiles to Slots

The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots:

1. In the Server Profiles page, click Profiles for QuickDeploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Assign

Profile column.

NOTE: You can perform the Quick Deploy action only if the Action When Server is Inserted option in the Deploy iDRAC page is set to Server Profile or Quick Deploy then Server Profile. Selecting this option allows to apply the server profile assigned when a new server is inserted in the chassis.

2. From the drop-down menu, select the profile to assign to the required slot. You can select profiles to apply to multiple slots.

3. Click Assign Profile. The profiles gets applied to the selected slots.

NOTE: When the FM120x4 sled is inserted, the stored profile assigned to the server slot is applied to all the four servers.

NOTE:

• A slot that does not have any profile assigned to it is indicated by the term "No Profile Selected" that appears in the select box.

• To remove a profile assignment from one or more slots, select the slots and click Remove Assignment. A message is displayed warning you that removing a profile from the slot or slots removes the XML configuration settings in the profile from any servers inserted in the slots when Quick Deploy Profiles feature is enabled. Click OK to remove the profile assignments.

• To remove all profile assignments from a slot, in the drop-down menu, select No Profile Selected.

NOTE: When a profile is deployed to a server using the Quick Deploy Profile feature, the progress and results of the application are retained in the Profile Log.

NOTE: The Network Share option is enabled and the details are displayed in the Stored Profiles section

only if the network share is mounted and is accessible. If the Network Share is not connected, configure the Network Share for the chassis. To configure the Network Share, click Edit in the Stored Profiles section. For more information see Configuring Network Share Using CMC Web

Interface

Launching iDRAC using Single Sign-On

CMC provides limited management of individual chassis components, such as servers. For complete management of these individual components, CMC provides a launch point for the server’s management controller (iDRAC) web-based interface.

A user may be able to launch iDRAC web interface without having to login a second time, as this feature utilizes single sign-on. Single sign-on policies are:

• A CMC user who has server administrative privilege, is automatically logged into iDRAC using single sign-on. Once on the iDRAC site, this user is automatically granted Administrator privileges. This is true even if the same user does not have an account on iDRAC, or if the account does not have the Administrator’s privileges.

• A CMC user who does NOT have the server administrative privilege, but has the same account on iDRAC is automatically logged into iDRAC using single sign-on. Once on the iDRAC site, this user is granted the privileges that were created for the iDRAC account.

• A CMC user who does not have the server administrative privilege, or the same account on the iDRAC, does NOT automatically logged into iDRAC using single sign-on. This user is directed to the iDRAC login page when the Launch iDRAC GUI is clicked.

NOTE: The term "the same account" in this context means that the user has the same login name with a matching password for CMC and for iDRAC. The user who has the same login name without a matching password, is considered to have the same account.

NOTE: Users may be prompted to log in to iDRAC (see the third Single Sign-on policy bullet above).

NOTE: If the iDRAC network LAN is disabled (LAN Enabled = No), single sign-on is not available.

If the server is removed from the chassis, the iDRAC IP address is changed, or the iDRAC network connection experiences a problem, then clicking Launch iDRAC GUI may display an error page.

Launching iDRAC from Server Status Page

To launch the iDRAC management console for an individual server:

1. In the left pane, expand Server Overview. All four servers appear in the expanded Servers Overview

list.

2. Click the server for which you want to launch the iDRAC Web interface.

3. On the Servers Status page, click Launch iDRAC GUI.

The iDRAC Web interface is displayed. For information about the field descriptions, see the CMC for Dell PowerEdge FX2/FX2s Online Help.

Launching iDRAC from Servers Status Page

To launch the iDRAC management console from the Servers Status page:

1. In the left pane, click Server Overview.

2. On the Servers Status page, click Launch iDRAC for the server you want to launch the iDRAC Web

interface.

Launching Remote Console from Server Status Page

To launch a remote console for an individual server:

1. In the left pane, expand Server Overview. All the four servers appear in the expanded servers' list.

2. Click the server for which you want to launch the remote console.

3. On the Server Status page, click Launch Remote Console.

NOTE: The Launch Remote Console button or link is enabled only if the server has Enterprise license installed.

Configuring CMC To Send Alerts

You can set alerts and actions for certain events that occur on the chassis. 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 message (email alert or SNMP trap), then an alert is sent to one or more configured destinations such as email address, IP address, or an external server.

To configure CMC to send alerts:

1. Enable the Chassis Event Alerts option.

2. Optionally, filter the alerts based on category or severity.

3. Configure the email alert or SNMP trap settings.

4. Enable chassis event alerts to send an e-mail alert, or SNMP traps to configured destinations.

Enabling Or Disabling Alerts

To send alerts to configured destinations, you must enable the global alerting option. This property overrides the individual alert setting.

Make sure that the SNMP or email alert destinations are configured to receive the alerts.

Enabling Or Disabling Alerts Using CMC Web Interface

To enable or disable generating alerts:

1. In the left pane, click Chassis Overview → Alerts.

2. On the Chassis Events page, under the Chassis Alert Enablement section, select the Enable Chassis

Event Alerts option to enable, or clear the option to disable the alert.

3. To save the settings, click Apply.

Enabling Or Disabling Alerts Using RACADM

To enable or disable generating alerts, use the cfgIpmiLanAlertEnable RACADM object. For more information, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.

Filtering Alerts

You can filter alerts on the basis of category and severity.

Configuring Alert Destinations

The management station uses Simple Network Management Protocol (SNMP) to receive data from CMC.

You can configure the IPv4 and IPv6 alert destinations, email settings, and SMTP server settings, and test these settings.

Before configuring the email alert or SNMP trap settings, make sure that you have the Chassis Configuration Administrator privilege.

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. Enter the following:

• In the Destination field, enter a valid IP address. Use the quad-dot IPv4 format, standard IPv6

address notation, or FQDN. For example: 123.123.123.123 or 2001:db8:85a3::8a2e:370:7334 or dell.com.

Choose a format that is consistent with the networking technology or infrastructure. The Test Trap functionality cannot detect incorrect choices based on the current network configuration (example, use of an IPv6 destination in an IPv4-only environment).

• In the Community String field, enter a valid community string to which the destination

management station belongs. This community string differs from the community string on the Chassis → Network → Services

page. The SNMP traps community string is the community that CMC uses for outbound traps destined to management stations. The community string on the Chassis → Network → Services page is the community string that management stations use to query the SNMP daemon on CMC.

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.

• Under Enabled , select the check box corresponding to the destination IP to enable the IP

address to receive the traps. You can specify up to four IP addresses.

3. Click Apply to save the settings.

4. To test whether the IP address is receiving the SNMP traps, click Send in the Test SNMP Trap

column. The IP alert destinations are configured.

Configuring SNMP Trap Alert Destinations Using RACADM

To configure IP alert destination using RACADM:

1. Open a serial/Telnet/SSH text console to CMC and log in.

NOTE: Only one filter mask may be set for both SNMP and email alerting. You can skip step 2 if you have already selected the filter mask.

2. Enable alert generation:

racadm config -g cfgAlerting -o cfgAlertingEnable 1

3. Enable traps alerts:

racadm config -g cfgTraps -o cfgTrapsEnable 1 -i <index>

where <index> is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualified Domain Names (FQDNs).

4. Specify a destination IP address to receive the traps alert:

racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr <IP address> -i <index>

where <IP address> is a valid destination, and <index> is the index value specified in step 3.

5. Specify the community name:

racadm config -g cfgTraps -o cfgTrapsCommunityName <community name> -i <index>

where <community name> is the SNMP community to which the chassis belongs, and <index> is the index value specified in steps 4 and 5.

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–5.

NOTE: The commands in steps 2–5 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 <index>. If the index is configured, values appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName objects.

6. To test an event trap for an alert destination, type:

racadm testtrap -i <index>

where <index> is a value 1–4 representing the alert destination you want to test.

If you are not sure of the index number, use:

racadm getconfig -g cfgTraps -i <index>

Configuring E-Mail Alert Settings

When CMC detects a chassis event, such as an environmental warning or a component failure, it can be configured to send an e-mail alert to one or more e-mail addresses.

You must configure the SMTP email server to accept relayed emails from the CMC IP address, a feature which is normally turned off in most mail servers due to security concerns. For instructions to do this in a secure manner, see the documentation that was provided with the SMTP server.

NOTE: If your mail server is Microsoft Exchange Server 2007, make sure that CMC domain name is configured for the mail server to receive the email alerts from CMC.

NOTE: Email alerts support both IPv4 and IPv6 addresses. The DRAC DNS Domain Name must be specified when using IPv6.

If your network has an SMTP server that releases and renews IP address leases periodically, and the addresses are different, then there is a duration when this property setting does not work due to change in the specified SMTP server IP address. In such cases, use the DNS name.

Configuring Email Alert Settings Using CMC Web Interface

To configure the email alert settings using Web interface:

1. In the system tree, go to Chassis Overview, and then click Alerts → E-mail Alert Settings.

2. Specify the SMTP email server settings and the email address(es) to receive the alerts. For information

about the fields, see the CMC Online Help.

3. Click Apply to save the settings.

4. Click Send under Test E-mail to send a test email to the specified email alert destination.

Configuring Email Alert Settings Using RACADM

To send a test email to an email alert destination using RACADM:

1. Open a serial/Telnet/SSH text console to CMC and log in.

2. Enable alert generation:

racadm config -g cfgAlerting -o cfgAlertingEnable 1

3. Enable email alert generation:

racadm config -g cfgEmailAlert -o cfgEmailAlertEnable 1 -i <index>

where <index> is a value between 1–4. CMC uses the index number to distinguish up to four configurable destination email addresses.

4. Specify a destination email address to receive the email alerts:

racadm config -g cfgEmailAlert -o cfgEmailAlertAddress <email address> -i <index>

where <email address> is a valid email address, and <index> is the index value you specified in step 4.

5. Specify the name of the person receiving the email alert:

racadm config -g cfgEmailAlert -o cfgEmailAlertEmailName <email name> -i <index>

where <email name> is the name of the person or group receiving the email alert, and <index> is the index value specified in step 4 and step 5. The email name can contain up to 32 alphanumeric characters, dashes, underscores, and periods. Spaces are not valid.

6. Setup the SMTP host:

racadm config -g cfgRemoteHosts -o cfgRhostsSmtpServerIpAddr host.domain

where host.domain is the FQDN. You can configure up to four destination email addresses to receive email alerts. To add more email

addresses, repeat step 2 – step 5.

NOTE: The commands in steps 2–5 overwrite any existing settings configured for the index you specify (1–4). To determine whether an index has previously configured values, type:xracadm

getconfig -g cfgEmailAlert — I

the cfgEmailAlertAddress and cfgEmailAlertEmailName objects.

<index> . If the index is configured, values appear for

For more information, see the RACADM Command Line Reference Guide for iDRAC and CMC available at dell.com/support/manuals.

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 default root account. As an administrator, you can set up user accounts to allow other users to access the CMC.

You can set up a maximum of 16 local users, or use directory services such as Microsoft Active Directory or LDAP to setup additional user accounts. Using a directory service provides a central location for managing authorized user accounts.

CMC supports role-based access to users with a set of associated privileges. The roles are administrator, operator, read-only, or none. The role defines the maximum privileges available.

Types of Users

There are two types of users:

• CMC users or chassis users

• iDRAC users or server users (since the iDRAC resides on a server)

CMC and iDRAC users can be local or directory service users.

Except where a CMC user has Server Administrator privilege, privileges granted to a CMC user are not automatically transferred to the same user on a server, because server users are created independently from CMC users. In other words, CMC Active Directory users and iDRAC Active Directory users reside on two different branches in the Active Directory tree. To create a local server user, the Configure Users must log in to the server directly. The Configure Users cannot create a server user from CMC or vice versa. This rule protects the security and integrity of the servers.

Table 7. User Types

Privilege Description

CMC Login User User can log in to CMC and view all the CMC data, but cannot add

or modify data or execute commands. It is possible for a user to have other privileges without the CMC

Login User privilege. This feature is useful when a user is temporarily not allowed to login. When that user’s CMC Login User privilege is restored, the user retains all the other privileges previously granted.

Chassis Configuration Administrator

User can add or change data that:

• Identifies the chassis, such as chassis name and chassis location.

Privilege Description

• Is assigned specifically to the chassis, such as IP mode (static or DHCP), static IP address, static gateway, and static subnet mask.

• Provides services to the chassis, such as date and time, firmware update, and CMC reset.

• Is associated with the chassis, such as slot name and slot priority. Although these properties apply to the servers, they are strictly chassis properties relating to the slots rather than the servers themselves. For this reason, slot names and slot priorities can be added or changed whether or not servers are present in the slots.

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. The previous slot name and priority remain with the previous chassis.

NOTE: CMC users with the Chassis Configuration Administrator privilege can configure power settings. However, the Chassis Control Administrator privilege is required to perform chassis power operations, including power on, power off, and power cycle.

User Configuration Administrator User can:

• Add a new user.

• Change the password of a user.

• Change the privileges of a user.

• Enable or disable the login privilege of a user but retain the name and other privileges of the user in the database.

Clear Logs Administrator User can clear the hardware log and CMC log.

Chassis Control Administrator

(Power Commands)

Server Administrator This is a blanket privilege, granting a CMC user all rights to perform

CMC users with the Chassis Power Administrator privilege can perform all power-related operations. They can control chassis power operations, including power on, power off, and power cycle.

NOTE: To configure power settings, the Chassis Configuration Administrator privilege is needed.

any operation on any servers present in the chassis. When a user with Server Administrator privilege issues an action to

be performed on a server, the CMC firmware sends the command to the targeted server without checking the privileges of a user on the server. In other words, the Server Administrator privilege overrides any lack of administrator privileges on the server.

Without the Server Administrator privilege, a user created on the chassis can only execute a command on a server when all of the following conditions are true:

• The same user name exists on the server.

• The same user name must have the same password on the server.

• The user must have the privilege to execute the command.

Privilege Description

When a CMC user who does not have Server Administrator privilege issues an action to be performed on a server, CMC sends a command to the targeted server with the user’s login name and password. If the user does not exist on the server, or if the password does not match, the user is denied the ability to perform the action.

If the user exists on the target server and the password matches, the server responds with the privileges of which the user was granted on the server. Based on the privileges responding from the server, CMC firmware decides if the user has the right to perform the action.

Listed below are the privileges and the actions on the server to which the Server Administrator is entitled. These rights are applied only when the chassis user does not have the Server Administrative privilege on the chassis.

Server Configuration Administrator:

• Set IP address

• Set gateway

• Set subnet mask

• Set first boot device

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.

The CMC user groups provide a series of user groups that have pre-assigned user privileges.

NOTE: If you select Administrator, Power User, or Guest User, and then add or remove a privilege from the pre-defined set, the CMC Group automatically changes to Custom.

Table 8. CMC Group Privileges

User Group Privileges Granted

Administrator

• CMC Login User

• Chassis Configuration Administrator

• User Configuration Administrator

• Clear Logs Administrator

100

Dell Chassis Management Controller Version 1.10 Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Overview

Key Features

What Is New In This Release

Management Features

Security Features

Chassis Overview

Supported Remote Access Connections

Supported Platforms

Supported Web Browsers

Managing Licenses

Types of Licenses

Acquiring Licenses

License Operations

Licensable Features In CMC

License Component State or Condition and Available Operations

Viewing Localized Versions of the CMC Web Interface

Supported Management Console Applications

How to Use this User's Guide

Other Documents You May Need

Accessing documents from Dell support site

Installing and Setting Up CMC

Installing CMC Hardware

Checklist To Set up Chassis

Using Remote Access Software From a Management Station

Remote RACADM Installation

Installing Remote RACADM on a Windows Management Station

Installing Remote RACADM on a Linux Management Station

Uninstalling Remote RACADM From a Linux Management Station

Configuring a Web Browser

Downloading and Updating CMC Firmware

Setting Chassis Physical Location and Chassis Name

Setting Date and Time on CMC

Configuring LEDs to Identify Components on the Chassis

Configuring CMC Properties

Configuring Front Panel

Configuring Chassis Management at Server Mode

Configuring Chassis Management at Server Using CMC Web Interface

Configuring Chassis Management at Server Mode Using RACADM

Logging in to CMC

Configure Public Key Authentication Over SSH

Generating Public Keys for Systems Running Windows

Generating Public Keys for Systems Running Linux

Accessing CMC Web Interface

Logging Into CMC as a Local User, Active Directory User, or LDAP User

Logging in to CMC Using a Smart Card

Logging Into CMC Using Single Sign-on

Logging In To CMC Using Serial, Telnet, Or SSH Console

Logging in to CMC Using Public Key Authentication

Multiple CMC Sessions

Updating Firmware

Signed CMC Firmware Image

Downloading CMC Firmware

Viewing Currently Installed Firmware Versions

Viewing Currently Installed Firmware Versions Using CMC Web Interface

Viewing Currently Installed Firmware Versions Using RACADM

Updating the CMC Firmware

Updating CMC Firmware Using Web Interface

Updating CMC Firmware Using RACADM

Updating the CMC Using DUP

Updating Chassis Infrastructure Firmware

Updating Chassis Infrastructure Firmware Using CMC Web Interface

Updating Chassis Infrastructure Firmware Using RACADM

Updating Server iDRAC Firmware

Updating Server iDRAC Firmware Using Web Interface

Updating Server Component Firmware

Enabling Lifecycle Controller

Choosing Server Component Firmware Update Type Using CMC Web Interface

Filtering Components for Firmware Updates

Viewing Firmware Inventory

Saving Chassis Inventory Report Using CMC Web Interface

Configuring Network Share Using CMC Web Interface

Lifecycle Controller Job Operations

Viewing Chassis Information and Monitoring Chassis and Component Health

Viewing Chassis and Component Summaries

Chassis Graphics

Selected Component Information