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...................................................................................................... 35 Configuring chassis management at server using CMC web interface.............................................................. 35 Configuring chassis management at server mode using RACADM.....................................................................36 3 Logging into CMC...................................................................................
Viewing chassis summary............................................................................................................................................... 60 Viewing chassis controller information and status.......................................................................................................60 Viewing information and health status of all servers...................................................................................................
Applying Chassis Configuration Profiles.................................................................................................................. 76 Exporting Chassis Configuration Profiles................................................................................................................ 77 Editing Chassis Configuration Profiles..................................................................................................................... 77 Deleting Chassis Configuration Profiles.
Clearing Boot Identity Profiles.................................................................................................................................. 97 Viewing Stored Boot Identity Profiles......................................................................................................................98 Importing Boot Identity Profiles...............................................................................................................................
Configuring the generic LDAP directory to access CMC.................................................................................... 115 Configuring generic LDAP directory service using CMC web interface.............................................................116 Configuring generic LDAP directory service using RACADM..............................................................................116 11 Configuring CMC for Single Sign-On or Smart Card login..............................................
Viewing basic WWN or MAC address information using web interface..................................................................138 Viewing advanced WWN or MAC address information using web interface..........................................................138 Viewing WWN or MAC address information using RACADM...................................................................................139 14 Managing Fabrics............................................................................................
Configuring power budget and redundancy..........................................................................................................153 Executing Power Control Operations.................................................................................................................... 155 Executing Power Control Operations for Multiple Servers Using CMC Web Interface.................................. 155 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 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 documents from the Dell EMC support site Key Features The CMC features are grouped into management and security features.
• 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.
Figure 1. Chassis back panel 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. Chassis front panel — components Item Indicator, Button, or Connector 1 System identification button 2 Enclosure power-on indicator, power button 3 Diagnostic indicators 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.
Connection Features • • • • Serial port • • • 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.
Table 4. Latest Firmware Versions for BIOS, iDRAC, and Lifecycle Controller Servers BIOS iDRAC Lifecycle Controller PowerEdge FC830 2.7.1 2.52.52.52 2.52.52.52 PowerEdge FC630 2.7.1 2.52.52.52 2.52.52.52 PowerEdge FC430 2.7.1 2.52.52.52 2.52.52.52 PowerEdge FM120 1.70 2.52.52.52 2.52.52.52 PowerEdge FC640 1.37 3.18.18.18 3.18.18.
Platform FC640 Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) BIOS 1.6.0 1.7.0 iDRAC 3.15.15.15 3.21.21.21 Lifecycle Controller 3.15.15.15 3.21.21.21 Diagnostics 4301A13 4301A13 BIOS 1.3.7 1.4.8 Supported Network Adapters The following table lists the supported network adapters for PowerEdge FX2/FX2s. Table 6.
Platforms Model FC430 FC630 FC830 FC640 i350 QP 1G Yes Yes Yes Yes X520 DP 10G SFP+ No Yes No Yes X710 DP 10GBE SFP+ (Fortville) Yes Yes Yes Yes CX3 DP 40GbE QSFP+ Yes Yes Yes Yes CX3 DP 10GbE DA/SFP+ Yes Yes Yes Yes CX3 MCX354–A-FCBT No No No No QLE2560 FC8 Single HBA No Yes Yes Yes 578 10S 10G BASE-T Yes Yes Yes Yes QLE2660 SP FC 16 HBA No Yes Yes Yes QLE2662 DP FC16 HBA Yes Yes Yes Yes QLG SFP DP 10G No No No Yes QLG BT DP 10G No No No Yes
are stored in the persistent store. For more information, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals. The log messages for all storage sled license activities are stored in the CMC log file. NOTE: Storage sled licenses are required to change the FD33xS and FD33xD RAID controllers from HBA mode to RAID mode.
For storage sleds, the new license overwrites the existing license in the CMC license manager and the storage sled persistent store. Power off the storage sleds before replacing the license. The licensed features are available only after the RAID controller is reset at the next host reboot. • 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.
Feature Express Enterprise Enclosure level power capping No Yes Multi-chassis management No Yes FlexAddress Enablement No Yes One-to-many Server Firware Update No Yes 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 8.
• The CMC FX2/FX2s Online Help provides information about using the web interface. To access the Online Help, click Help on the CMC web interface. • The Chassis Management Controller Version 2.0 for Dell PowerEdge FX2/FX2s RACADM Command Line Reference Guide provides information about using the FX2/FX2s–related RACADM features. • The Dell Chassis Management Controller (CMC) for Dell PowerEdge FX2/FX2s Version 2.0 Release Notes, available at dell.
– Serviceability Tools – Dell Client Command Suite – 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.
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.
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 > 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.
Daisy chain FX2 CMC network connection If you have multiple chassis in a rack, you can reduce the number of connections to the management network by daisy-chaining up to ten chassis together. You can reduce the number of management network uplink connections required from ten to one. When daisy-chaining chassis together, GB is the uplink port and STK is the stacking (cable consolidation) port.
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 • 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. NOTE: The Chassis Location field is optional.
When a compute sled is performing an identify action, the front LED of the connected storage sled also flashes the identify pattern. If a storage sled is in split-single mode and is connected to two compute nodes, it shall flash the identify pattern if either of the two compute nodes is performing an identify action. If you start an identify action using OMSS or iDRAC for a compute sled, drive or enclosure, the storage sled associated with them also performs the identify action.
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.
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 – cfgRacTuneCha
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 •
• Chassis infrastructure firmware 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
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. A blue cast indicates the component selection 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.
• 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.
Component Fans IOM Slot Health and Performance Properties Properties • Device ID • Slot Type • Module Type • Fabric • 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
• • 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.
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 through RACADM Using Chassis Configuration Profiles • 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.
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 80The 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.
3 Setting Description iDRAC IPv6 Prefix Length Specifies the prefix length to be assigned for the IPv6 addresses on the iDRAC. The default value is 64. Use CMC DNS Settings Enables the CMC DNS Server settings ( IPv4 and IPv6) that are propagated to iDRAC when a blade server is inserted in the chassis. Click Save QuickDeploy Settings to save the settings. If you have made changes to the iDRAC network setting, click Apply iDRAC Network Settings to deploy the settings to the iDRAC.
• 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. Quarter-width sleds in top row and half-width sleds in bottom row • Top row contains only full-width sleds and bottom row contains only half-width sleds: Figure 8.
• 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.
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.
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.
NOTE: While downgrading from CMC version 1.3 or later, if the Sled network uplink configuration is set to Enhanced Network Adapter Isolation, then the Sled network uplink configuration is blank in CMC 1.2 or earlier versions.
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.
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.
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.
The Edit BIOS Profile — 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 results displayed for the completion or failure are similar to the information displayed in the iDRAC Lifecycle Controller log for the specific server. 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.
The boot identity profiles contain the NIC or FC settings that are required to boot a server from a SAN target device and unique virtual MAC and WWN. As these are available across multiple chassis through a CIFS or NFS share, you can quickly and remotely move an identity from a non-functional server in a chassis to a spare server located in the same or another chassis and thus enabling it to boot with the operating system and applications of the failed server.
A progress indicator indicates that the save operation is in progress. After the action is complete, Operation Successful message is displayed. NOTE: The process to gather the settings occurs 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 Boot Identity Profiles You can apply boot identity profile settings if the boot identity profiles are available as stored profiles on the network share.
Viewing Stored Boot Identity Profiles To view the boot identity profiles stored on the network share, go to the Server Profiles page. In the Boot Identity Profiles > Stored Profiles section, select the profile and click View in the View Profile column. The View Settings page is displayed. For more information on the displayed settings, see the CMC Online Help. Importing Boot Identity Profiles You can import boot identity profiles that are stored on the management station to the network share.
To view the Manage Virtual MAC Address option by the CMC web interface, in the system tree, go to Chassis Overview > Server Overview. Click Setup > Profiles > Boot Identity Profiles. The Manage Virtual MAC Address Pool section is displayed. NOTE: The virtual MAC Addresses are managed in the vmacdb.xml file in the network share. A hidden lock file (.vmacdb.lock) is added and removed from the network share to serialize boot identity operations from multiple chassis.
4 Click OK to remove MAC addresses. Deactivating MAC Addresses You can deactivate MAC addresses that are active by using the Deactivate MAC Address(es) option in the CMC web interface. NOTE: Use the Deactivate MAC Address(es) option only if the server is not responding to the Clear Identity action or the MAC address is not used in any server. To remove MAC addresses from the network share: 1 Go to the Server Profiles page.
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.
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 • • • 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.
Privilege Description • • • 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.
User Group Privileges Granted • • • • • • None Clear Logs Administrator 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.
NOTE: If you are using Active Directory on Microsoft Windows 2003, make sure that you have the latest service packs and patched installed on the client system. If you are using Active Directory on Microsoft Windows 2008, make sure that you have installed SP1 along with the following hot fixes: Windows6.0-KB951191-x86.msu for the KTPASS utility. Without this patch the utility generates bad keytab files. Windows6.0-KB957072-x86.msu for using GSS_API and SSL transactions during an LDAP bind.
NOTE: The cmcname.domainname.com must be in lowercase as required by RFC and the @REALM_NAME must be in uppercase. In addition, CMC supports the DES-CBC-MD5 and AES256-SHA1 types of cryptography for Kerberos authentication. A keytab file is generated that must be uploaded to CMC. NOTE: The keytab contains an encryption key and must be kept secure. For more information about the ktpass utility, see the Microsoft website.
Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM In addition to the steps performed while configuring Active Directory, run the following command to enable SSO: racadm config -g cfgActiveDirectory -o cfgADSSOEnable 1 In addition to the steps performed while configuring Active Directory, use the following objects to enable smart card login: • cfgSmartCardLogonEnable • cfgSmartCardCRLEnable Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web In
Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM In addition to the steps performed while configuring Active Directory, run the following command to enable SSO: racadm config -g cfgActiveDirectory -o cfgADSSOEnable 1 In addition to the steps performed while configuring Active Directory, use the following objects to enable smart card login: • cfgSmartCardLogonEnable • cfgSmartCardCRLEnable 122 Configuring CMC for Single Sign-On or Smart Card login
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.
About FlexAddress Plus Each FlexAddress Plus feature card contains unique pool of MAC/WWNs that allow the chassis to assign World Wide Name/Media Access Control (WWN/MAC) addresses to Fibre Channel and Ethernet devices. Chassis assigned WWN/MAC addresses are globally unique and specific to a server slot. 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.
Table 25. Status Messages Returned by the featurecard -s Command Status Message Actions No feature card inserted. Check CMC to verify that the SD card was properly inserted. The feature card inserted is valid and contains the following feature(s) FlexAddress: bound. No action required. The feature card inserted is valid and contains the following feature(s) FlexAddress: bound to another chassis, svctag=ABC1234, SD card SN = 1122334455.
Configuring FlexAddress FlexAddress is an optional upgrade that allows server modules to replace the factory-assigned WWN/MAC ID with a WWN/MAC ID provided by the chassis. NOTE: By using the racresetcfg subcommand, you can reset the Flex Address of a CMC to its factory-default setting, which is “disabled”.
Situation Command Output Number> SD card SN = SD card in the CMC module that is bound to the same service tag. The feature card inserted is valid and contains the following feature(s) $racadm featurecard -s FlexAddress: bound SD card in the CMC module that is not bound to any service tag.
packet(s), installing or downloading the Software, or using the Software that has been preloaded or is embedded in your product, you agree to be bound by the terms of this agreement. If you do not agree to these terms, promptly return all Software items (disks, written materials, and packaging) and delete any preloaded or embedded Software. You may use one copy of the Software on only one computer at a time.
FITNESS FOR A PARTICULAR PURPOSE.
• Basic Mode — In this mode you can view Server Slot, Fabric, Protocol, WWN/MAC addresses, and Partition Status. Only Active MAC addresses are displayed in WWN/MAC address field. You can filter using any or all of the fields displayed. • Advanced Mode — In this mode you can view all the fields displayed in the basic mode and all the MAC types (Server Assigned, Flex Address, and IO Identity). You can filter using any or all of the fields displayed.
3 In the WWN/MAC Addresses table, click Export to save the WWN/MAC addresses locally. 4 Click the against a slot or click Expand/Collapse All to expand or collapse the attributes listed for a specific slot or all the slots in the WWN/MAC Addresses table. 5 From the Server Slot drop-down menu, select All Servers or a specific Slot to view the WWN/MAC Addresses attributes for all servers or servers in specific slots only respectively.
To display the chassis assigned WWN/MAC address, use the following RACADM command: racadm getmacaddress -c flexaddress To display the MAC/WWN addresses for all LOMs or mezzanine cards, use the following RACADM command: racadm getmacaddress -c factory For more information on the getflexaddr and getmacaddress subcommand, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.
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.
5 In the Edit VLANs section, enter the VLAN IDs for the IOMs. Enter VLAN IDs in the range 1-4094. VLAN IDs can be entered as a range or separated by a comma. 6 Select one of the following options from the drop-down menu as required: 7 • 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.
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 status and overall power health 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.
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.
Viewing power budget status using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getpbinfo 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.
Table 28. SEL events for power redundancy policy changes Power Policy Event System Event Log (SEL) Entry Redundancy lost Power supply redundancy is lost. Redundancy regained The power supplies are redundant. 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).
• To select a redundancy policy, type: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy where is 0 (No Redundancy), 1 (Grid Redundancy), and 3 (Redundancy Alerting Only). The default value is 3.
Executing Power Control Operations You can execute the following power control operation for the chassis, servers, and IOM. NOTE: Power control operations affect the entire chassis. 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).
• Power Off Server • Reset Server (warm boot) • Power Cycle Server (cold boot) For information about the options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3 Click Apply. A dialog box appears requesting for confirmation. 4 Click OK to perform the power management action (for example, reset the server). Executing Power Control Operations on the IOM You can remotely reset or turn on an IOM.
If the Budget/Redundancy Configuration > Disable AC Power Recovery option is selected, the chassis remains powered off after the AC recovery. In case, the blade servers are not configured to automatic power-up, you may have to power them on manually.
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.
Supported interfaces • CLI RACADM • Remote RACADM • 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.
Power Troubleshooting The following information helps you to troubleshoot power supply and power-related issues: • • • • • Problem: Configured the Power Redundancy Policy to Grid Redundancy, and a Power Supply Redundancy Lost event was raised. – 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.
event: log cleared was asserted Wed May 09 16:06:00 2007 warning System Software event: predictive failure was asserted Wed May 09 15:26:31 2007 critical System Software event: log full was asserted Wed May 09 15:47:23 2007 unknown System Software event: unknown event 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.
NOTE: Flexaddress information, server profiles, and extended storage are not saved or restored with the Chassis Configuration. It is recommended to save the Server Profiles that are important separately from the chassis using either a remote file share or a copy saved to a local workstation. For more details on performing these operation, see Adding or Saving Profile 1 In the left pane, click Chassis Overview > Setup > Chassis Backup. The Chassis Backup page is displayed.
If the NTP server IP address is not configured, you may see a trace log entry similar to the following: Jan 8 19:59:24 cmc ntpd[1423]: Cannot find existing interface for address 1.2.3.4 Jan 8 19:59:24 cmc ntpd[1423]: configuration of 1.2.3.
Component IOM (Pass through) Fan PSU PCI Storage sled LED Color, Blinking Pattern Status Amber, blinking Fault Blue, dark No fault/stack slave Green, glowing steadily Turned on Green, blinking Not used Green, dark Powered off Blue, glowing steadily Normal 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 st
Observing LEDs to Isolate the Problem The CMC has an LED which changes color to indicate: Table 34. LED color indicators Color Description Blue Normal operation Blue, blinking ID (0.5 second on, 0.5 second off) Amber Chassis fault summary Amber, blinking Chassis fault with concurrent ID Obtain Recovery Information from DB-9 Serial Port If the CMC LED is amber, recovery information is available from the DB-9 serial port located on the front of CMC.
NOTE: In recover mode, you cannot ping CMC normally because there is no active network stack. The recover ping command allows you to ping to the TFTP server to verify the LAN connection. You may need to use the recover reset command after setniccfg on some systems. 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.
• 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
An error message Not Found is displayed while using the $ logout and $ quit commands. 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.
racadm getconfig -g cfgOobSnmp To set the CMC community name, use the following command: racadm config -g cfgOobSnmp -o cfgOobSnmpAgentCommunity To prevent SNMP authentication traps from being generated, enter input community names that are accepted by the agent. Since CMC only allows one community name, enter the same get and set community name for IT Assistant discovery setup. Active Directory Does Active Directory support CMC login across multiple trees? Yes.
Click the Refresh icon to see if the IP address is set correctly on the switch. If an error is made in setting the IP/mask/gateway, the switch does not set the IP address and returns a 0.0.0.0 in all fields. 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.
