Users Guide
Table Of Contents
- Dell Chassis Management Controller Version 2.0 for PowerEdge FX2 and FX2s User's Guide
- Contents
- Overview
- Key Features
- Chassis overview
- Supported remote access connections
- Supported platforms
- Supported web browsers
- Supported firmware versions
- Supported Firmware Versions for Server Component Update
- Supported Network Adapters
- Managing licenses
- Viewing localized versions of the CMC web interface
- Supported management console applications
- How to use this Guide
- Other documents you may need
- Accessing support content from the Dell EMC support site
- Installing and setting up CMC
- Installing CMC hardware
- Checklist to set up chassis
- Daisy chain FX2 CMC network connection
- 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
- Installing CMC hardware
- Logging into CMC
- Configure public key authentication over SSH
- Accessing CMC web interface
- Logging into CMC as a local user, active directory user, or LDAP user
- Logging into CMC using a smart card
- Logging into CMC using Single Sign-On
- Logging into CMC using serial, Telnet, or SSH console
- Logging into CMC using public key authentication
- Multiple CMC sessions
- Updating firmware
- Signed CMC firmware image
- Downloading CMC firmware
- Viewing currently installed firmware versions
- Updating the CMC firmware
- Updating the CMC using DUP
- Updating chassis infrastructure firmware
- 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
- Reinstalling server component firmware
- Rolling back server component firmware
- Upgrading server component firmware
- Upgrading server component firmware from file using CMC web interface
- Server component single click update using network share
- Pre-requisites for using network share update mode
- Upgrading server component firmware from network share using CMC web interface
- Deleting Scheduled Server Component Firmware Jobs
- Recovering iDRAC firmware using CMC
- Viewing chassis information and monitoring chassis and component health
- Viewing chassis and component summaries
- Viewing chassis summary
- Viewing chassis controller information and status
- Viewing information and health status of all servers
- Viewing information and health status of storage sleds
- Viewing information and health status of the IOMs
- Viewing information and health status of fans
- Viewing front panel properties
- Viewing KVM information and health status
- Viewing information and health status of temperature sensors
- Configuring CMC
- Enabling or disabling DHCP for the CMC Network Interface Address
- Enabling or disabling DHCP for DNS IP addresses
- Setting static DNS IP addresses
- Viewing and modifying CMC network LAN settings
- Configuring IPv4 and IPv6 DNS settings
- Configuring auto negotiation, duplex mode, and network speed for IPv4 and IPv6
- Configuring Management Port 2
- Configuring Management Port 2 using RACADM
- Federal Information Processing Standards
- Configuring services
- Configuring CMC extended storage card
- Setting up Chassis Group
- Adding members to Chassis Group
- Removing a member from the leader
- Disbanding a Chassis Group
- Disabling an individual Member at the Member chassis
- Launching the web page of a Member chassis or server
- Propagating Leader chassis properties to Member chassis
- Synchronizing a new Member with Leader chassis properties
- Server inventory for MCM group
- Saving server inventory report
- Chassis Configuration Profiles
- Saving Chassis Configuration
- Restoring Chassis Configuration Profile
- Viewing Stored Chassis Configuration Profiles
- Importing Chassis Configuration Profiles
- Applying Chassis Configuration Profiles
- Exporting Chassis Configuration Profiles
- Editing Chassis Configuration Profiles
- Deleting Chassis Configuration Profiles
- Configuring Multiple CMCs through RACADM Using Chassis Configuration Profiles
- Configuring multiple CMCs using RACADM
- Configuring servers
- Configuring slot names
- Configuring iDRAC network settings
- Configuring iDRAC QuickDeploy network settings
- QuickDeploy IP address assignments for servers
- Modifying iDRAC Network Settings for individual server iDRAC
- Modifying iDRAC network settings using RACADM
- Configuring iDRAC VLAN tag settings
- Configuring iDRAC VLAN tag settings using web interface
- Configuring iDRAC VLAN tag settings using RACADM
- Setting first boot device
- Configuring sled network uplink
- Deploying remote file share
- Configuring server FlexAddress
- Configuring profile settings using server configuration replication
- Accessing Profile page
- Managing stored profiles
- Adding or saving profile
- Applying profile
- Importing profile
- Exporting profile
- Editing profile
- Viewing profile settings
- Viewing stored profile settings
- Viewing profile log
- Completion status and troubleshooting
- Quick Deploy of profiles
- Assigning server profiles to slots
- Boot Identity Profiles
- Saving Boot Identity Profiles
- Applying Boot Identity Profiles
- Clearing Boot Identity Profiles
- Viewing Stored Boot Identity Profiles
- Importing Boot Identity Profiles
- Exporting Boot Identity Profiles
- Deleting Boot Identity Profiles
- Managing Virtual MAC Address Pool
- Creating MAC Pool
- Adding MAC Addresses
- Removing MAC Addresses
- Deactivating MAC Addresses
- Launching iDRAC using Single Sign-On
- Launching remote console from server status page
- Configuring storage sleds
- Configuring CMC to send alerts
- Configuring user accounts and privileges
- Configuring CMC for Single Sign-On or Smart Card login
- System requirements
- Prerequisites for Single Sign-On or Smart Card login
- Generating Kerberos keytab file
- Configuring CMC for Active Directory schema
- Configuring browser for SSO login
- Configuring browser for Smart Card login
- Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM
- Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface
- Uploading Keytab file
- Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM
- Configuring CMC to use Command Line consoles
- Using FlexAddress and FlexAddress Plus cards
- About FlexAddress
- Configuring FlexAddress
- Command messages
- FlexAddress DELL SOFTWARE LICENSE AGREEMENT
- Viewing WWN or MAC address information
- Viewing basic WWN or MAC address information using web interface
- Viewing advanced WWN or MAC address information using web interface
- Viewing WWN or MAC address information using RACADM
- Managing Fabrics
- Monitoring IOM health
- Configuring network settings for IOM
- Viewing Input Output module uplink and downlink status using web interface
- Viewing Input Output module FCoE session information using web interface
- Resetting IOM to factory default settings
- Updating IOM software using CMC web interface
- IOA or MXL GUI
- Input Output Aggregator Module
- Using VLAN Manager
- Assigning VLAN to IOM
- Configuring VLAN settings on IOMs using CMC web interface
- Viewing the VLAN settings on IOMs using CMC web interface
- Viewing the current VLAN settings on IOMs using CMC web interface
- Removing VLANs for IOMs using CMC web interface
- Updating untagged VLANs for IOMs using CMC web interface
- Resetting VLANs for IOMs using CMC web interface
- Managing and monitoring power
- Redundancy policies
- Default Redundancy configuration
- Multi-node sled adaptation
- Chassis power limit monitoring
- Viewing power consumption status
- Viewing power budget status using CMC web interface
- Viewing power budget status using RACADM
- Redundancy status and overall power health
- Configuring PCIe slots
- Troubleshooting and recovery
- Gathering configuration information, chassis status, and logs using RACDUMP
- Supported interfaces
- Downloading SNMP Management Information Base file
- First steps to troubleshoot a remote system
- Troubleshooting Alerts
- Viewing Event Logs
- Using Diagnostic Console
- Resetting Components
- Saving or Restoring Chassis Configuration
- Troubleshooting Network Time Protocol Errors
- Interpreting LED colors and blinking patterns
- Troubleshooting Network Problems
- General troubleshooting
- Resetting Forgotten Administrator Password
- Gathering configuration information, chassis status, and logs using RACDUMP
- Frequently asked questions
Grid Redundancy policy
The Grid Redundancy policy is also knows as 1+1 policy, for one active and one spare PSU.
The purpose of the Grid Redundancy policy is to enable an enclosure system to operate in a mode in which the enclosure can
tolerate AC power failures. These failures may originate in the AC power grid, the cabling and delivery, or a Power Supply Unit
(PSU) itself. When you configure a system for Grid Redundancy, connect PSUs 1 and 2 to separate power grids.
In this mode, the CMC ensures that power usage is maintained such that the system continues to operate with no degradation
if there is a failure of either the grid or a single PSU. Server power-on is limited to the available power of a single PSU. If at any
time redundancy cannot be maintained (such as if a PSU is removed or fails) alerts are triggered, the chassis health becomes
Critical.
No Redundancy policy
The No Redundancy policy is also known as 2+0 policy.
In this mode, all the power of both PSUs is available and used, but there is no assurance that a PSU or grid failure does not
affect system operation.
Redundancy Alerting Only policy
The Redundancy Alerting Only policy permits server power-on to use the capacity of both PSUs, while alerting on actual
conditions such as removal or failure of a PSU, or actual power consumption exceeding the capabilities of a single PSU. This is
the default policy.
Fault Tolerant Redundancy
This policy uses the power capacity limits of a Single Power Supply Unit (PSU) similar to the Grid Redundancy policy. In this
mode, the sub-system peak power of the CPU is replaced with a new IccMax limit. This policy is applicable only to Dell's 14th
generation of blade servers.
PSU failures
PSU failures of any type are always alerted, regardless of the selected redundancy policy.
Default Redundancy configuration
Redundancy Alerting Only is the default redundancy configuration for a chassis and two PSUs.
Multi-node sled adaptation
The PowerEdge FM120x4 is a multi-node, half-width sled that can accommodate four servers with the associated iDRAC with
independent processors. It is designed for optimal power efficiency and the processors cannot be removed. The processors in
PowerEdge FM120 share a common power infrastructure, for example, a single power and temperature sensors for the entire
sled.
Chassis power limit monitoring
OpenManage Power Center (OMPC) can be used to monitor and control power consumption of the machines in a data center.
PowerEdge FX2/FX2s enables OMPC by providing a provision to set the power cap for the chassis, and bounds to guide the
setting of the power cap. The lower and upper bounds for the power cap are set by the CMC and cannot be configured.
136
Managing and monitoring power