Dell Chassis Management Controller Version 2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2013 - 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview....................................................................................................................................................... 11 Key Features......................................................................................................................................................................12 What is new in this release..................................................................................................................................
Configuring chassis management at server mode.......................................................................................................34 Configuring chassis management at server using CMC web interface.............................................................. 34 Configuring chassis management at server mode using RACADM.................................................................... 35 3 Logging into CMC...................................................................................
Viewing chassis summary............................................................................................................................................... 59 Viewing chassis controller information and status.......................................................................................................59 Viewing information and health status of all servers...................................................................................................
Applying Chassis Configuration Profiles.................................................................................................................. 75 Exporting Chassis Configuration Profiles................................................................................................................ 76 Editing Chassis Configuration Profiles.....................................................................................................................76 Deleting Chassis Configuration Profiles..
Clearing Boot Identity Profiles.................................................................................................................................. 97 Viewing Stored Boot Identity Profiles......................................................................................................................97 Importing Boot Identity Profiles................................................................................................................................
Configuring the generic LDAP directory to access CMC.....................................................................................114 Configuring generic LDAP directory service using CMC web interface............................................................ 115 Configuring generic LDAP directory service using RACADM..............................................................................115 11 Configuring CMC for Single Sign-On or Smart Card login..............................................
Viewing basic WWN or MAC address information using web interface..................................................................136 Viewing advanced WWN or MAC address information using web interface..........................................................136 Viewing WWN or MAC address information using RACADM................................................................................... 137 14 Managing Fabrics...........................................................................................
Configuring power budget and redundancy..........................................................................................................150 Executing Power Control Operations..................................................................................................................... 151 Executing Power Control Operations for Multiple Servers Using CMC Web Interface.................................. 152 Executing Power Control Operations on the IOM............................................
1 Overview The Dell Chassis Management Controller (CMC) for Dell EMC 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.
• 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 documents from the Dell EMC support site Key Features The CMC features are grouped into management and security features.
• FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/MAC) IDs with chassisassigned WWN/MAC IDs for a particular slot, an optional upgrade. • 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.
Table 1. Chassis back panel — components Item Indicator, Button, or Connector 1 Serial connector 2 Ethernet connector Gb1 3 Ethernet connector STK/Gb2 (stack) 4 System identification button 5 Low-profile PCIe expansion slots 6 Power supply (PSU1) 7 Power supply (PSU2) 8 I/O module (2) 9 I/O module ports 10 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. Figure 2. Chassis front panel Table 2.
Item Indicator, Button, or Connector 4 KVM select button 5 Compute sled 6 Video connector 7 USB connector 8 Storage sled Supported remote access connections The following table lists the supported remote access connections. Table 3. 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).
For the latest supported platforms, see the Dell Chassis Management Controller (CMC) Version 2.0 for Dell PowerEdge FX2/FX2s Release Notes available at dell.com/cmcmanuals. Supported web browsers For the latest information about supported web browsers, see the Dell Chassis Management Controller (CMC) Version 2.1 for Dell PowerEdge FX2/FX2s Release Notes at dell.com/cmcmanuals. • Microsoft Internet Explorer 11 • Microsoft EDGE • Safari version 8.0.8 • Safari version 9.0.
Platform FC630 FC830 FM120x4 FC640 Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) Lifecycle Controller 2.52.52.52 2.60.60.60 Diagnostics 4239.44 4239A36 BIOS 2.6.0 2.7.1 iDRAC 2.52.52.52 2.52.52.52 Lifecycle Controller 2.52.52.52 2.52.52.52 Diagnostics 4239.44 4239A36 BIOS 2.6.0 2.7.1 iDRAC 2.52.52.52 2.60.60.60 Lifecycle Controller 2.52.52.52 2.60.60.60 Diagnostics 4239.44 4239A36 BIOS 2.6.0 2.7.1 iDRAC 2.52.52.
Platforms Model FC430 FC630 FC830 FC640 57416 DP 10G No No No Yes 57414 DP 25G No No No Yes 57412 DP 10G No No No Yes BCOM QP 1G Yes Yes Yes Yes LightPulse LPE12002 FC8 HBA Yes Yes Yes Yes LightPulse LPe15002B-M8–D DP 8G Gen 5 Yes Yes Yes Yes LPe16002 Dual Port FC 16 HBA Yes Yes Yes Yes LightPulse LPE12000 FC 8 HBA No Yes Yes Yes LightPulse LPe 15000B-M8–D SP 8G Gen 5 No Yes Yes Yes LPE 16000 Single Port FC 16 HBA No Yes Yes Yes LPE 31K0 FC16 1P No Ye
Platforms Model FC430 FC630 FC830 FC640 QLE2692 FC16 DP HBA Yes Yes Yes Yes PCIE SF852P DP 10G Yes Yes Yes Yes INTEL OPA x16 LP No No Yes Yes 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.
• 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 dell.com/support.
Feature Express Enterprise 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 Fl
License/Component state or condition Import Export Delete Replace Learn More Expired license No Yes Yes Yes Yes License installed but component missing 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.
• The setup placemat shipped with your system provides information about the initial system setup and configuration. • The server module's Owner's Manual provides information about the server module's features and describes how to troubleshoot the server module and install or replace the server module's components. This document is available online at dell.com/ poweredgemanuals. • The rack documentation included with your rack solution describes how to install your system into a rack, if required.
2 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.
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 > Power On System. Click Apply. You can also power on the chassis using the command line interface, use racadm chassisaction powerup command to accomplish it. NOTE: Do not turn on the servers.
When daisy-chaining chassis together, GB is the uplink port and STK is the stacking (cable consolidation) port. Connect the Gb ports to the management network or to the STK port of CMC in a chassis that is closer to the network. Connect the STK port only to a Gb port further from the chain or network. The following figure illustrates the arrangement of cables for four daisy-chained chassis, each with active CMCs. Table 9.
Following are the steps to daisy-chain four FX2 CMC modules: 1 Connect the GB port of the FX2 CMC in the first chassis to the management network. 2 Connect the GB port of the FX2 CMC in the second chassis to the STK port of the FX2 CMC in the first chassis. 3 If you have a third chassis, connect the GB port of its FX2 CMC to the STK port of the FX2 CMC in the second chassis. 4 If you have a fourth chassis, connect the GB port of its FX2 CMC to the STK port of the FX2 CMC in the third chassis.
Interface/ Protocol Remote RACADM CLI Description • Data: 8 bit • Parity: None • Stop: 1 bit • Hardware flow control: Yes • Software flow control: No 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.
Interface/ Protocol Description • DMTF WS-Management Specifications: www.dmtf.org/standards/wbem/wsman WinRM tool sets a default response timeout of 60 seconds for all WSMan commands it sends out. WinRM does not allow varying this timeout interval. Using “winrm set winrm/config @{MaxTimeoutms ="80000"}” does not change the timeout due to a bug in the WinRM tool. Therefore, it is recommended that WinRM is not used for commands that may take more than one minute to complete execution.
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.
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.
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 CMC Online Help. You can view the chassis name while logging in to CMC using SSH, by selecting Show Chassis Name in SSH Prompt.
Configuring LEDs to identify components on the chassis You can enable the LEDs of components (chassis, servers, storage sleds, 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. When a compute sled is performing an identify action, the front LED of the connected storage sled also flashes the identify pattern.
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.
• Monitor — This mode enables you to monitor the chassis components but you cannot perform any firmware update through iDRAC, OS, iDRAC RACADM proxy, 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, iDRAC RACADM, or Lifecycle Controller.
3 Logging into 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 SignOn or a Smart Card.
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.
For the latest information on supported web browsers, see the Dell Systems Software Support Matrix located at dell.com/support/ manuals.
Logging into 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.
NOTE: If you have changed the default HTTPS port number (port 80), access the CMC web interface using :, 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.
4 Updating firmware You can update firmware for: • The CMC • Chassis infrastructure • I/O Module You can update firmware for the following server components: • BIOS • iDRAC7 • iDRAC8 • Lifecycle Controller • 32–bit diagnostics • Operating system Drivers Pack • Network Interface Controllers • RAID controllers Topics: • Signed CMC firmware image • Downloading CMC firmware • Viewing currently installed firmware versions • Updating the CMC firmware • Updating the CMC using DUP •
Viewing currently installed firmware versions You can view the currently installed firmware versions using the CMC web interface or RACADM.
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. NOTE: In a chassis supported by 2400W AC PSUs, if you attempt to update/downgrade the firmware with a version which the 2400W AC PSUs do not support, an error message is displayed. The 2400W AC PSUs support CMC 1.
• iDRAC RACADM proxy • 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 example, racadm fwupdate . 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.
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 page by selecting Hardware Configuration > Hardware Inventory.
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.
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.
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.
Field Description 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. Update Click to select the component or device for firmware update on the server.
• Password • SMB Version NOTE: The SMB Version option is available only if the Protocol type is CIFS. NOTE: If you are using CIFS that is registered with a domain, and are accessing the CIFS using the IP with the CIFS local user credentials, it is mandatory to enter the hostname or host IP in the Domain Name field. For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3 Click Test Directory to verify whether the directories are readable and writeable.
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.
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.
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.
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).
5 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 Storage sleds Topics: • • • • • • • • • • 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
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.
NOTE: In Multi-Chassis Management (MCM), all the Quick Links associated with the servers are not displayed. Table 13.
Component Fans IOM Slot Health and Performance Properties Properties • Power Status Quick Links • Speed • Warning Threshold • Fans Status • PWM (% of Max) • Critical Threshold • Fan Configuration • Fan Offset • Power State • Model • Role • Service Tag 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
Viewing information and health status of storage sleds To view the health status of storage sleds: In the left pane, click Chassis Overview > Server Overview, and select the storage sled. The Storage Array Status page displays the storage sled properties and the list of storage nodes connected to the compute sled. For more information, see Online Help.
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.
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).
6 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.
• Configuring multiple CMCs using RACADM 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 or disabling DHCP for DNS IP addresses By default, the CMC’s DHCP for DNS address feature is disabled.
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.
For an IPv4 network, to disable DHCP and specify static CMC IP address, gateway, and subnet mask, type: racadm racadm racadm racadm config config config config -g -g -g -g cfgLanNetworking cfgLanNetworking cfgLanNetworking cfgLanNetworking -o -o -o -o cfgNicUseDHCP 0 cfgNicIpAddress cfgNicGateway cfgNicNetmask By default, the DHCP is disabled.
< duplex mode > is 0 (half duplex) or 1 (full duplex, default) racadm config -g cfgNetTuning -o cfgNetTuningNicSpeed where: < speed > is 10 or 100 (default). 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.
Level 1, Level 2, Level 3, and Level 4. The FIPS 140–2 series stipulate that all communicative interfaces must have the following security properties: • authentication • confidentiality • message integrity • non-repudiation • availability • access control If any of the properties depend on cryptographic algorithms, then FIPS must approve these algorithms. By default, the FIPS mode is disabled. When FIPS is enabled, the minimum key size for OpenSSL FIPS is SSH-2 RSA 2048 bits.
Disabling FIPS Mode To disable FIPS mode, reset CMC to the default factory settings. Configuring services You can configure and enable the following services on CMC: • CMC serial console — Enable access to CMC using the serial console. • Web Server — Enable access to CMC web interface. Disabling the web server also disables Remote RACADM. • SSH — Enable access to CMC through firmware RACADM.
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.
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.
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.
• 5 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.
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.
Restoring Chassis Configuration Profile You can restore the configuration of a chassis by importing the backup file (.xml or .bak) on the local management station or the network share to which the chassis configurations were saved. The configurations include all the properties available through the CMC web interface, RACADM commands, and settings. To restore the chassis configuration, perform the following tasks: 1 Go to the Chassis Configuration Profiles page.
Exporting Chassis Configuration Profiles You can export chassis configuration profiles that are saved on the network share to a specified path on a management station. To export a stored profile, perform the following tasks: 1 Go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles > Stored Profiles section, select the required profile and then click Export Copy of Profile. A File Download message is displayed prompting you to open or save the file.
Exporting Chassis Configuration profiles You can export chassis configuration profiles to network share by using the get command. 1 To export the chassis configuration profiles as clone.xml file to CIFS network share by using get command, type the following: racadm get –f clone.xml –t xml –l //xx.xx.xx.xx/PATH –u USERNAME –p PASSWORDCMC 2 To export the chassis configuration profiles as clone.xml file to NFS network share by using get command, type the following: racadm get –f clone.xml –t xml –l xx.xx.
• System Configuration, which is the parent node. • component, which is the primary child node. • Attributes, which contains name and value. You can edit these fields. For example, you can edit the Asset Tag value as follows: PAGE 79The 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 .
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.
7 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 Topics: • Configuring slot names • Configuring iDRAC network settings • Setting first boot device • Configuring sled network uplink • Deploying remote file share • Configuring server FlexAddress • Configuring profile settings using server configurati
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.
Setting Description • Quick Deploy and Server Profile — Select this option to first apply the iDRAC network 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.
Setting Description iDRAC IPv6 Prefix Length Specifies the prefix length to be assigned for the IPv6 addresses on the iDRAC. The default value is 64. Use CMC DNS Settings Enables the CMC DNS Server settings ( IPv4 and IPv6) that are propagated to iDRAC when a blade server is inserted in the chassis. Enable iDRAC DNS Name Select Enable iDRAC DNS Name to apply the iDRAC DNS name to the blade servers inserted in the chassis. You can provide the iDRAC DNS prefix, which the CMC appends with the slot name.
NOTE: The Reserved QuickDeploy IPAddresses must be set to a minimum of 8. Figure 5. Eight quarter-width sleds in the chassis • Four FM120x4 sleds in the chassis: NOTE: The Reserved QuickDeploy IPAddresses must be set to 16. Figure 6. Four FM120x4 sleds in the chassis • Top row contains only quarter-width sleds and bottom row contains only half-width sleds: NOTE: The Reserved QuickDeploy IPAddresses must be set to a minimum of 8. Figure 7.
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.
The valid values for are 1–4. The valid values for are 1–4000 and 4021–4094. Default is 1. The valid values for 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- -v The valid values for are 1–16.
Boot Device Description BIOS Boot Manager Boot using the BIOS boot manager. Lifecycle Controller Boot using the Lifecycle controller. Local Floppy Boot from a floppy disk in the local floppy disk drive. 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.
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.
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.
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.
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.
3 4 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. Click Save Profile to save the profile to the selected location.
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.
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.
For Emulex Fibre Channel (FC) cards, the Enable/Disable Boot From SAN attribute in the Option ROM is disabled by default. Enable the attribute in the Option ROM and apply the boot identify profile to the server for booting from SAN. To save a profile, perform the following tasks: 1 Go to the Server Profiles page. In the Boot Identity Profiles section, select the server that has the required settings with which you want to generate the profile and select FQDD from the FQDD drop-down menu.
The selected profile is applied to the server and the server is rebooted immediately. For more information, see the CMC Online Help. NOTE: You can apply a boot identity profile to only one NIC FQDD partition in a server at a time. To apply the same boot identity profile to a NIC FQDD partition in another server, you must clear it from the server where it is first applied.
Deleting Boot Identity Profiles You can delete a boot identity profile that is stored on the network share. To delete a stored profile, perform the following tasks:: 1 Go to the Server Profiles page. In the Boot Identity Profiles > Stored Profiles section, select the required profile, and then click Delete Profile. A warning message is displayed indicating that deleting a profile would delete the selected profile permanently. 2 Click OK to delete the selected profile.
To add MAC addresses to the network share: 1 Go to the Server Profiles page. In the Boot Identity Profiles > Manage Virtual MAC Address Pool section, click Add MAC Addresses. 2 Enter the starting MAC address of the MAC address pool in the Starting MAC Address field. 3 Enter the count of the MAC addresses that you want to add, in the Number of MAC Addresses field. The valid values are from 1 to 3000. 4 Click OK to add MAC addresses.
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.
8 Configuring storage sleds Half-width storage sleds that are used in the FX2s chassis contain the following: • One or two RAID controllers • Maximum of 16 disk drives You can configure individual storage sleds containing two RAID controllers to operate in the following modes: • Split-single • Split-dual • Joined NOTE: Do not insert a storage sled in slot 1 of the chassis as it is not a valid location for storage sleds. NOTE: This section is applicable only to dual-controller storage modules.
Configuring storage sleds in joined mode In joined mode, the RAID controllers are mapped to a single compute sled. However, only one controller is enabled and all the disk drives are connected to it. Configuring storage sleds using CMC web interface 1 In the left pane, click Chassis Overview > Server Overview and click a storage sled. The details of the storage sled are displayed. 2 In the menu on the right side, click Setup. The Storage Configuration page is displayed.
For more information, see the Online Help.
9 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.
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.
3 Enable traps alerts: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualified Domain Names (FQDNs).
Configuring e-mail alert settings using CMC web interface To configure the e-mail 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.
10 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.
Privilege Description • • 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. Is associated with Active Directory (AD) such as managing AD certificate, and configuring AD groups, domains, and privileges.
Privilege Description • • 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.
User Group Privileges Granted • • • • • None Chassis Control Administrator (Power commands) Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator No assigned permissions Table 19.
To add and configure local CMC users: 1 In the left pane, click Chassis Overview, and then click User Authentication. 2 On the Local Users page, in the User ID column, click a user ID number. The User Configuration page is displayed. NOTE: User ID 1 is the root user account that is shipped by default with a CMC. This cannot be changed. 3 Enable the user ID and specify the user name, password, and access privileges for the user. For more information about the options, see the Online Help.
Supported Active Directory authentication mechanisms You can use Active Directory to define CMC user access using two methods: • Standard schema solution that uses Microsoft’s default Active Directory group objects only. • Extended schema solution that has customized Active Directory objects provided by Dell. All the access control objects are maintained in Active Directory. It provides maximum flexibility to configure user access on different CMCs with varying privilege levels.
Configuring standard schema Active Directory To configure CMC for an Active Directory login access: 1 On an Active Directory server (domain controller), open Active Directory Users and Computers Snap-in. 2 Using the CMC Web interface or RACADM: a b 3 Create a group or select an existing group. Configure the role privileges. Add the Active Directory user as a member of the Active Directory group to access CMC.
Configuring generic LDAP directory service using CMC web interface To configure the generic LDAP directory service: NOTE: You must have the Chassis Configuration Administrator privilege. 1 In the left pane, click Chassis Overview > User Authentication > Directory Services. 2 Select Generic LDAP. The settings to be configured for standard schema is displayed on the same page. NOTE: The Windows-based directory servers do not allow anonymous login. Hence, enter the bind DN name and password.
NOTE: It is highly recommended to use the racadm testfeature -f LDAP command to test the LDAP settings for first time setups. This feature supports both IPv4 and IPv6. The required property changes include enabling LDAP logins, setting the server FQDN or IP, and configuring the base DN of the LDAP server. • $ racadm config -g cfgLDAP -o cfgLDAPEnable 1 • $ racadm config -g cfgLDAP -o cfgLDAPServer 192.168.0.
11 Configuring CMC for Single Sign-On or Smart Card login This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. SSO uses Kerberos as an authentication method allowing users, who have signed in as an automatic- or single sign-on to subsequent applications such as Exchange.
• Kerberos Key Distribution Center (packaged with the Active Directory Server software). • DHCP server (recommended). • The DNS server reverse zone must have an entry for the Active Directory server and CMC. Client Systems • For only Smart Card login, the client system must have the Microsoft Visual C++ 2005 redistributable. For more information see www.microsoft.com/downloads/details.
Configuring CMC for Active Directory schema For information about configuring CMC for Active Directory standard schema, see Configuring Standard Schema Active Directory. For information about configuring CMC for Extended Schema Active Directory, see Extended Schema Active Directory Overview. Configuring browser for SSO login Single Sign-On (SSO) is supported on Internet Explorer versions 6.0 and later, and Firefox versions 3.0 and later.
• cfgSmartCardCRLEnable Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface To configure Active Directory SSO or smart card login for CMC: NOTE: For information about the options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 1 2 While configuring Active Directory to setup a user account, perform the following additional steps: • Upload the keytab file. • To enable SSO, select the Enable Single Sign-On option.
12 Configuring CMC to use Command Line consoles This section provides information about the CMC command line console (or serial/Telnet/Secure Shell console) features, and explains how to set up the system so that you can perform systems management actions through the console. For information about using the RACADM commands in CMC through the command line console, see Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.
Using Telnet console with CMC You can have up to four Telnet sessions with CMC at a time. If your management station is running Microsoft Windows XP or Microsoft Windows Server 2003, you may experience an issue with the characters in a CMC Telnet session. This issue may occur as a frozen login where the return key does not respond and the password prompt does not appear. To fix this issue, download hotfix 824810 from support.microsoft.com.
Scheme Type Scheme • ARCFOUR-128 Message Integrity • • • • HMAC-SHA1-160 HMAC-SHA1-96 HMAC-MD5-128 HMAC-MD5-96 Authentication Password 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.
• Port: COM1 • Data: 8 bit • Parity: None • Stop: 1 bit • Hardware flow control: Yes • Software flow control: No Connecting to servers or Input Output module using Connect command CMC can establish a connection to redirect the serial console of a server or I/O module. For servers, serial console redirection can be accomplished using: • CMC command line interface (CLI) or the RACADM connect command.
The connect server-n command enables the user to access the server's serial port. After this connection is established, the user can view the server's console redirection through CMC's serial port that includes both the BIOS serial console and the operating system serial console. NOTE: To view the BIOS boot screens, serial redirection has to be enabled in the servers’ BIOS setup. Also, you must set the terminal emulator window to 80×25. Otherwise, the characters on the page are not properly displayed.
Edit the /etc/grub.conf file as follows: 1 Locate the general setting sections in the file and type the following two new lines: serial --unit=1 --speed=57600 terminal --timeout=10 serial 2 Append two options to the kernel line: kernel console=ttyS1,57600 3 If the /etc/grub.conf contains a splashimage directive, comment it out. The following example shows the changes described in this procedure. # grub.
The following example shows the file with the new line. # # inittab This file describes how the INIT process # should set up the system in a certain # run-level. # # Author: Miquel van Smoorenburg # Modified for RHS Linux by Marc Ewing and # Donnie Barnes # # Default runlevel.
The following example shows a sample file with the new line. vc/1 vc/2 vc/3 vc/4 vc/5 vc/6 vc/7 vc/8 vc/9 vc/10 vc/11 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 ttyS1 Managing CMC using iDRAC RACADM proxy CMC can be managed using iDRAC RACADM proxy when CMC is not on the network. The following table lists the mapping of CMC privileges with iDRAC privileges for the proxy operation. Table 24.
13 Using FlexAddress and FlexAddress Plus cards This section provides information about FlexAddress and how to use FlexAddress Plus card to configure FlexAddress. NOTE: The FlexAddress feature is licensed. This feature license is included in the Enterprise License.
Before installing FlexAddress, you can determine the range of MAC addresses contained on a FlexAddress feature card by inserting the SD card into an USB Memory Card Reader and viewing the pwwn_mac.xml file. This clear text XML file on the SD card contains an XML tag mac_start that is the first starting hex MAC address that is used for this unique MAC address range. The mac_count tag is the total number of MAC addresses that the SD card allocates.
Status Message Actions The feature card inserted is valid and contains the following feature(s) FlexAddress: not bound. The feature card can be moved to another chassis or can be reactivated on the current chassis. To reactivate on the current chassis, enter racadm racreset until the CMC module with the feature card installed becomes active. Dell Feature Cards may contain more than one feature.
For example, if Fabric-A is enabled, any slots that are enabled have FlexAddress enabled only on Fabric-A. All other fabrics use the factoryassigned WWN/MAC on the server. NOTE: When the FlexAddress feature is deployed for the first time on a given server module, it requires a power- down and power-up sequence for FlexAddress to take effect. FlexAddress on Ethernet devices is programmed by the server module BIOS.
Situation Command Output Guest user attempts to set FlexAddress $racadm setflexaddr [-f ] on slots/fabrics. ERROR: Insufficient user privileges to perform operation $racadm setflexaddr [-i ] Deactivating FlexAddress feature with chassis powered ON. $racadm feature -d -c flexaddress ERROR: Unable to deactivate the feature because the chassis is powered ON Guest user tries to deactivate the feature on the chassis.
product if you retain no copies and the recipient agrees to the terms hereof. Any transfer must include the most recent update and all prior versions. You may not reverse engineer, decompile or disassemble the Software. If the package accompanying your computer contains compact discs, 3.5" and/or 5.25" disks, you may use only the disks appropriate for your computer.
This license is effective until terminated. It terminates upon the conditions set forth above or if you fail to comply with any of its terms. Upon termination, you agree that the Software and accompanying materials, and all copies thereof, is destroyed. This agreement is governed by the laws of the State of Texas. Each provision of this agreement is severable.
Viewing basic WWN or MAC address information using web interface To view WWN/MAC Address information for each server slot or all servers in a chassis, in the basic mode: 1 Click Server Overview > Properties > WWN/MAC The WWN/MAC Summary page displays the WWN/MAC Address Information. Alternatively, click Server Overview > Slot > Setup > FlexAddress to view the WWN/MAC Address information for a specific server slot. The FlexAddress page is displayed.
8 In the WWN/MAC Addresses field, enter the MAC address to view only the slots associated with the specific MAC address. Alternately, partially enter the MAC address entries to view the associated slots. For example, enter 4A to view the slots with MAC addresses that contain 4A. 9 From the Partition Status drop-down menu, select the status of the partitions to display servers with the selected partition status.
14 Managing Fabrics The chassis supports two fabric types: Fabric A1 and Fabric A2, which are used by the two I/O Modules, and are always connected to the on-board Ethernet adapters of the servers. NOTE: In the PowerEdge FX2s chassis, fabrics B and C are the PCIe connection to the PCIe Extension cards. Following IO Modules are supported: • 1GbE pass-through • 10GbE pass-through • I/O Aggregator Both the Fabrics support only Ethernet.
Configuring network settings for IOM using CMC web interface To configure the network settings for I/O Module: 1 In the left pane, click Chassis Overview, click I/O Module Overview, and then click Setup. Alternatively, to configure the network settings of the available I/O modules that is A1 and A2, click A1 Gigabit Ethernet or A2 Gigabit Ethernet, and then click Setup. On the Configure I/O Module Network Settings page, type appropriate data, and then click Apply.
Viewing Input Output module FCoE session information using web interface You can view the FCoE session information for Dell PowerEdge M I/O Aggregator using the CMC web interface. To do this: 1 Go to Chassis Overview > I/O Module Overview. All the IOMs (2) appear in the expanded list. 2 Click the IOM (slot) you want to view. Click Properties > FCoE. The FCoE I/O Module page specific to the IOM slot is displayed.
NOTE: Do not click the Refresh icon or navigate to another page during the file transfer. NOTE: The file transfer timer is not displayed when updating IOMINF firmware. NOTE: The FTOS or IOM software version is displayed in the format X-Y(A-B). For example, 8-3(1-4). If the Rollback Version of the FTOS image is an old image which uses the old version string format 8-3-1-4, then the Current Version is displayed as 8-3(1-4).
While changing the mode of an IOA that has a static IP, from stacking to standalone, ensure that the network for the IOA is changed to DHCP. Else, the static IP is duplicated on all the IOAs. When the IOMs are in stacking mode, the stack ID is the same as the master IOM burned in the MAC during the initial power-on. The stack ID does not change when the IOM modes change.
15 Using VLAN Manager You can assign or view the VLAN settings on the IOMs by using the VLAN Manager option. NOTE: This feature is supported only on Dell PowerEdge I/O Aggregator. After the mode of the I/O Aggregator is changed to standalone from stacking, remove the startup configuration and reload the I/O Aggregator. You need not save the system configuration while reloading the I/O Aggregator.
6 7 Select one of the following options from the drop-down menu as required: • Add Tagged VLANs • Remove VLANs • Update untagged VLANs • Reset to all VLANs • Show VLANs Click Save to save the new settings made to the VLAN Manager page. NOTE: The Summary VLANs of All Ports section displays information about the IOMs present in the Chassis and the assigned VLANs. Click Save to save a csv file of the summary of the current VLAN settings.
Updating untagged VLANs for IOMs using CMC web interface To update untagged VLANs for IOM(s) using the CMC web interface: NOTE: The untagged VLANs cannot be set to a VLAN ID that is already tagged. 1 Go to, I/O Module Overview , and click Setup > VLAN Manager. The VLAN Manager page is displayed. 2 In the Select I/O Module section, select the required IOMs. 3 In the Specify Port Range section, select the range of fabric ports to be assigned to the selected IOM(s).
16 Managing and monitoring power The PowerEdge FX2/FX2s chassis is the most power-efficient server enclosure. It is designed to include highly efficient power supplies and fans, has an optimized layout for the air to flow more easily through the system, and contains power-optimized components throughout the enclosure.
Redundancy policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis. The following redundancy policies are configurable: • Grid Redundancy • No Redundancy • Redundancy Alerting Only 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.
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.
For more information about getpbinfo, including output details, see the getpbinfo command section in the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. Redundancy status and overall power health The redundancy status is a factor in determining the overall power health.
Configuring power budget and redundancy You can configure the power budget, redundancy, and dynamic power of the entire chassis (chassis, servers, I/O module, CMC, PCIe, and chassis infrastructure). The power management service optimizes power consumption and reallocates power to different modules based on the requirement.
For example, the following command sets the redundancy policy to : racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy 1 • To set the power budget value, type: racadm config -g cfgChassisPower -o cfgChassisPowerCap where is a number between the Current runtime Chassis Burden and 3371, representing the maximum power limit in Watt. The default is 3371.
Executing Power Control Operations on the Chassis CMC enables you to remotely perform several power management actions, such as an orderly shutdown on the entire chassis (chassis, servers, IOM, and PSUs). Executing Power Control Operations on the Chassis Using Web Interface To execute power control operations on the chassis using the CMC web interface: 1 In the left pane, click Chassis Overview > Power > Control. The Chassis Power Control page is displayed.
4 Click OK to perform the power management action (for example, reset the server). NOTE: The modular blade servers are in throttle state during CMC reboot or failover. Executing Power Control Operations on the IOM You can remotely reset or turn on an IOM. NOTE: To perform power management actions, you must have the Chassis Control Administrator privilege.
17 Configuring PCIe slots The PowerEdge FX2/FX2s chassis optionally contain eight PCIe slots where each PCIe slot is assigned to a specific sled. By default, all PCIe slots are mapped. You can enable or disable the assignment of PCIe slots to the servers using the CMC web interface or RACADM commands. The following tables list the PCIe mapping for full-width, half-width, and quarter-width compute sleds. Table 29.
PCIe Slot Mapping for quarter-width sleds (PowerEdge FC430) PCIe slot-5 3b PCIe slot-6 3a PCIe slot-7 1b PCIe slot-8 1a NOTE: PCIe management is supported only for PowerEdge FX2s and not PowerEdge FX2. For more information about mapping PCIe slots, see the Dell PowerEdge FD332 Owner’s Manual. For more information about managing PCIe slots, see the CMC for Dell PowerEdge FX2/FX2s Online Help.
PCIe reassignment The PCIe reassignment feature enables you to map PCIe slots assigned to compute sleds in the lower bays to compute sleds in the upper bays. You can enable or disable the PCIe reassignment option using CMC web interface, CMC WSMan, or RACADM. You must have the chassis configuration privilege to configure or modify the reassignment settings. Power off all compute sleds in the chassis before modifying the reassignment settings.
18 Troubleshooting and recovery This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC web interface. • Viewing chassis information. • Viewing the event logs. • Gathering configuration information, error status, and error logs. • Using the diagnostic console. • Managing power on a remote system. • Managing Lifecycle Controller jobs on a remote system. • Reset components.
• Telnet RACADM racdump includes the following subsystems and aggregates the following RACADM commands. For more information about racdump, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. Table 32.
– Resolution A: This configuration requires the power supply in side 1 (the left slot) and the power supply in side 2 (the right slot) to be present and functional in the enclosure. Additionally the capacity of each supply must be enough to support the total power allocations for the chassis to maintain Grid redundancy.
Viewing Chassis Log CMC generates a log of the chassis-related events. NOTE: To clear the chassis log, you must have the Clear Logs Administrator privilege. Using Diagnostic Console You can diagnose issues related to the chassis hardware using CLI commands if you are an advanced user or a user under the direction of technical support. NOTE: To modify these settings, you must have the Debug Command Administrator privilege.
NOTE: CMC does not reset upon restoring configuration, however CMC services may take some time to effectively impose any changed or new configuration. After successful completion, all current sessions are closed. Troubleshooting Network Time Protocol Errors After configuring CMC to synchronize the clock with a remote time server over the network, it may take 2-3 minutes before a change in the date and time occurs. If after this time there is still no change, it may be necessary to troubleshoot a problem.
Interpreting LED colors and blinking patterns The LEDs on the chassis provide the following status of a component: • A blinking amber LED on a module indicates a fault on that module. • Blue, blinking LEDs are configurable by the user and used for identification. For more information about configuration, see CMC_Stmp_Configuring LEDs to Identify Components on the Chassis. Table 33.
Component Fan PSU PCI Storage sled LED Color, Blinking Pattern Status Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault Green, glowing steadily Fan working Green, blinking Not used Green, dark Turned off Amber, glowing steadily Fan type not recognized, update the CMC firmware Amber, blinking Fan fault; tachometer out of range Amber, dark Not used (Oval) Green, glowing steadily AC OK (Oval) Green, blinking No
Color Description Amber, blinking Chassis fault with concurrent ID Troubleshooting Network Problems The internal CMC trace log allows you to debug CMC alerts and networking. You can access the trace log using the CMC Web interface or RACADM. See the gettracelog command section in the RACADM Command Line Reference Guide for iDRAC and CMC. The trace log tracks the following information: • DHCP — Traces packets sent to and received from a DHCP server.
• Problem: PCIe slot reassignment enabled and host is powered on, but the PCIe slots are not powered on. Resolution: Check the Chassis Log for warning messages associated with outdated BIOS, iDRAC, or unsupported host. • Problem: Not able to import, export, or delete storage module licenses. Resolution: Chassis configuration privilege is required to import, export, and delete storage module licenses.
NOTE: Electrostatic discharge (ESD) events can damage CMC. Under certain conditions, ESD may build up on your body or an object, and then discharge into your CMC. To prevent ESD damage, take precautions to discharge static electricity from your body while handling and accessing CMC outside the Chassis. 2 Remove the jumper plug from the password reset connector, and insert a 2-pin jumper to enable the default administrator account. To locate the password jumper on the CMC board, see the following figure.
19 Frequently asked questions This section lists the frequently asked questions about the following: • RACADM • Managing and Recovering a Remote System • Active Directory • IOM Topics: • RACADM • Managing and recovering a remote system • Active Directory • IOM • Event and error messages RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) What does this messag
Managing and recovering a remote system When accessing the CMC Web interface, a security warning stating that the host name of the SSL certificate does not match the host name of CMC is displayed. CMC includes a default CMC server certificate to ensure network security for the web interface and remote RACADM features.
To set the CMC community name, use the following command: racadm config -g cfgOobSnmp -o cfgOobSnmpAgentCommunity To prevent SNMP authentication traps from being generated, enter input community names that are accepted by the agent. Since CMC only allows one community name, enter the same get and set community name for IT Assistant discovery setup. Active Directory Does Active Directory support CMC login across multiple trees? Yes.
Common errors are: • Setting the out-of-band IP address to be the same as, or on the same network as, the in-band management IP address. • Entering an invalid subnet mask. • Setting the default gateway to an address that is not on a network, which is directly connected to the switch.
