Dell Chassis Management Controller Version 1.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview............................................................................................................... 12 Key Features.........................................................................................................................................13 What is new in this release............................................................................................................ 13 Management features....................................................................
Configuring LEDs to identify components on the chassis.......................................................... 36 Configuring CMC properties.........................................................................................................37 Configuring front panel.................................................................................................................37 Configuring chassis management at server mode............................................................................
Viewing chassis information and monitoring chassis and component health........................................................................................................................61 Viewing chassis and component summaries..................................................................................... 61 Chassis graphics............................................................................................................................ 61 Selected component information..............
Synchronizing a new Member with Leader chassis properties................................................... 78 Server inventory for MCM group.................................................................................................. 78 Saving server inventory report...................................................................................................... 78 Chassis Configuration Profiles......................................................................................................
Importing profile........................................................................................................................... 99 Exporting profile............................................................................................................................99 Editing profile.............................................................................................................................. 100 Viewing profile settings......................................................
Configuring SNMP trap alert destinations.................................................................................. 113 Configuring e-mail alert settings................................................................................................ 114 10 Configuring user accounts and privileges................................................. 116 Types of users....................................................................................................................................
Configure public key authentication over SSH.......................................................................... 133 Configuring terminal emulation software........................................................................................134 Connecting to servers or I/O module using Connect command...................................................134 Configuring the managed server BIOS for serial console redirection......................................
Viewing the VLAN settings on IOMs using CMC web interface...................................................... 157 Viewing the current VLAN settings on IOMs using CMC web interface......................................... 157 Removing VLANs for IOMs using CMC web interface.....................................................................157 Updating untagged VLANs for IOMs using CMC web interface..................................................... 158 Resetting VLANs for IOMs using CMC web interface...
Saving or Restoring Chassis Configuration................................................................................ 174 Troubleshooting Network Time Protocol (NTP) Errors............................................................. 175 Interpreting LED colors and blinking patterns............................................................................176 Troubleshooting Network Problems..........................................................................................
Overview 1 The Dell Chassis Management Controller (CMC) for PowerEdge FX2/FX2s is a Systems Management hardware and software solution for managing the PowerEdge FX2/FX2s chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged. The CMC enables an IT administrator to: • View inventory. • Perform configuration and monitoring tasks. • Remotely turn on and turn off chassis and servers.
Key Features The CMC features are grouped into management and security features. What is new in this release This release of CMC for Dell PowerEdge FX2/FX2s supports: • Creating and deploying a Boot Identity Profiles library, from iSCSI, FC, or FCoE configurations, to enable quick restore of workload to a spare server. • Launching IOA and MXL Graphical User Interface (GUI) from the Chassis Overview and I/O Module Overview pages. • UC-APL certified IOMs with limited access in secure environments.
• Chassis Power Limit Monitoring. • iDRAC IO Identity feature support for enhanced WWN/MAC Address Inventory. • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/ MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade. • Graphical display of chassis component status and health. • Support for single and multi-slot servers. • iDRAC single sign-on. • Network time protocol (NTP) support.
Figure 1. 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. 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 1.
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.
Supported firmware versions The following table lists the firmware versions for BIOS, iDRAC, and Lifecycle Controller that support the servers listed: Table 2. Latest Firmware Versions for BIOS, iDRAC, and Lifecycle Controller Servers BIOS iDRAC Lifecycle Controller PowerEdge FC830 1.1.5 2.20.20.20 2.20.20.20 PowerEdgeFC630 1.2.5 2.20.20.20 2.20.20.20 PowerEdgeFC430 1.1.5 2.20.20.20 2.20.20.20 PowerEdgeFM120 1.3.0 2.20.20.20 2.20.20.
Platform Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) FM120x4 iDRAC 2.20.20.20 2.20.20.20 Lifecycle Controller 2.20.20.20 2.20.20.20 Diagnostics 4247A0 4247A0 BIOS 1.3.0 1.3.0 Supported Network Adapters The following table lists the supported network adapters for PowerEdge FX2/FX2s. Table 4.
Platforms Model FC420 FC620 FC430 FC630 FC830 578 10S 10G BASE-T Yes Yes Yes Yes Yes QLE2660 SP FC 16 HBA No No No Yes Yes QLE2662 DP FC16 HBA No No Yes 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.
• E-mail — License is attached to an e-mail that is sent after requesting it from the technical support center. • Self-service portal — A link to the Self-Service Portal is available from CMC. Click this link to open the licensing Self-Service Portal on the internet from where you can purchase licenses. For more information, see the online help for the self-service portal page. • Point-of-sale — License is acquired while placing the order for a system.
NOTE: If you try to install the PowerEdge FM120x4 license on PowerEdge FC630, the license installation fails. For more information on licensing refer Integrated Dell Remote Access Controller (iDRAC) User’s Guide . Licensable features in CMC A list of CMC features that are enabled on the basis of your license is given here in the table.
One-to-many configuration for iDRAC No Yes License component state or condition and available operations The following table provides the list of license operations available based on the license state or condition. Table 1.
• 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 1.2 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 1.2 Release Notes, available at dell.
– For OpenManage Connections Enterprise Systems Management documents — Dell.com/ OMConnectionsEnterpriseSystemsManagement – For Serviceability Tools documents — Dell.com/ServiceabilityTools – For OpenManage Connections Client Systems Management documents — Dell.com/ DellClientCommandSuiteManuals • From the Dell Support site: a. Go to Dell.com/Support/Home. b. Under Select a product section, click Software & Security. c.
Installing and setting up CMC 2 This section provides information about how to install your CMC hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the tasks for configuring a CMC: • Set up initial access to CMC. • Access CMC through a network. • Add and configure CMC users. • Update CMC firmware. Installing CMC hardware The CMC is pre-installed on your chassis and hence no installation is required.
CAUTION: Connecting the STK/Gb2 port to the management network will have unpredictable results if the CMC setting is not changed from default Stacking to Redundant, to implement NIC failover. In the default Stacking mode, cabling the Gb1 and STK/Gb2 ports to the same network (broadcast domain) can cause a broadcast storm. A broadcast storm can also occur if the CMC setting is changed to Redundant mode, but the cabling is daisy chained between chassis in the Stacking mode.
9. Configure iDRAC network settings as required. by default, iDRAC LAN is enabled with static IP configured. To determine the default static IP address with an Enterprise license, go to Server Overview → Setup → iDRAC. You can also determine the static IP address with an Express license. Go to Server Overview → Server-Slot → Setup → iDRAC. 10. Provide the IO module with an external management IP address(if applicable) in the CMC web interface.
1 Management Network 2 Active CMC The following figure illustrates an example of incorrect cabling of CMC in stacking mode.
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.
the back of the chassis. Connect the other end of the cable to management station serial port. For more information on connecting cables, refer to the back panel of the chassis in Chassis Overview section.
CMC MIB file can be downloaded from the CMC Web interface, go to Chassis Overview → Network → Services → SNMP. See the Dell OpenManage SNMP Reference Guide for more information about the CMC MIB. The following example show how the net-snmp snmpget command can be used to get the chassis service tag from the CMC. snmpget -v 1 -c . 1.3.6.1.4.1.674.10892.2.1.1.6.
Launching CMC using other systems management tools You can also launch CMC from the Dell Server Administrator or Dell OpenManage Essentials. To access CMC interface using Dell Server Administrator, launch Server Administrator on your management station. In the left pane of the Server Administrator home page, click System → Main System Chassis → Remote Access Controller. For more information, see the Dell Server Administrator User’s Guide at dell.com/support/manuals.
NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are auto-mounted with the noexec mount option. This option does not allow you to run any executable from the DVD. You need to mount the DVD-ROM manually, and then run the commands. 4. Navigate to the SYSMGMT/ManagementStation/linux/rac directory. To install the RAC software, type the following command: rpm -ivh *.rpm 5. For help about the RACADM command, type racadm help after you run the previous commands.
happen if you are using the browser or another interface such as remote RACADM. To disable the phishing filter: 1. Start Internet Explorer. 2. Click Tools → Phishing Filter, and then click Phishing Filter Settings. 3. Select the Disable Phishing Filter option and click OK. Downloading files from CMC with Internet Explorer When you use Internet Explorer to download files from the CMC, you may experience problems when the Do not save encrypted pages to disk option is not enabled.
For example racadm setsysinfo —c chassisname or racadm setsysinfo —c chassislocation For more information, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. Setting date and time on CMC You can manually set the date and time, or you can synchronize the date and time with a Network Time Protocol (NTP) server. Setting date and time on CMC using CMC web interface To set the date and time on CMC: 1. In the left pane, click Chassis Overview → Setup → Date/Time.
– Chassis Overview → Server Overview → Troubleshooting. NOTE: Only servers can be selected on this page. To enable blinking of a component LED, select the respective component , and then click Blink. To disable blinking of a component LED, deselect the server, and then click Unblink. Configuring LED blinking using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm setled -m [-l ], where specifies the module whose LED you want to configure.
4. On the Front Panel Configuration page, under the KVM Configuration section, for KVM Mapped option, select the desired server from the drop down list. 5. Click Apply. To map a Server to KVM using racadm, useracadm config -g cfgKVMInfo -o cfgKvmMapping [server slot #] command. To view the current KVM mapping using racadm, use racadm getconfig -g cfgKVMInfo.
Logging into CMC 3 You can log in to CMC as a CMC local user, as a Microsoft Active Directory user, or as an LDAP user. You can also log in using Single Sign-On or a Smart Card. Configure public key authentication over SSH You can configure up to six public keys that can be used with the service username over an SSH interface. Before adding or deleting public keys, make sure to use the view command to see what keys are already set up, so that a key is not accidentally overwritten or deleted.
To use the PuTTY Key Generator to create a basic key for clients running Windows: 1. Start the application and select SSH-2 RSA or SSH-2 DSA for the type of key to generate (SSH-1 is not supported). 2. Enter the number of bits for the key. RSA key size should be between 768 and 4096 and the recommended DSA key size is 1024. NOTE: 3. • CMC may not display a message if you add keys less than 768 or greater than 4096, but when you try to log in with these keys, it fails.
For the latest information on supported web browsers, see the Dell Systems Software Support Matrix located at dell.com/support/manuals. 2.
4. Optionally, select a session timeout. This is the duration for which you can stay logged in with no activity before you are automatically logged out. The default value is the Web Service Idle Timeout. 5. Click OK. You are logged into CMC with the required user privileges. You cannot log in to the Web interface with different user names in multiple browser windows on a single workstation. Logging into CMC using a smart card To use this feature, you must have an Enterprise License.
Before logging in to CMC using SSO, make sure that: • • You have logged in to your system using a valid Active Directory user account. Single Sign-On option is enabled during the Active Directory configuration. To log in to CMC using SSO: 1. Log in to the client system using your network account. 2. Access the CMC web interface by using: https:// For example, cmc-6G2WXF1.cmcad.lab,, where cmc-6G2WXF1 is the cmc-name and cmcad.lab is the domain name.
client systems running Windows and Linux provide methods to automate the method. On client systems running Windows, you can use the Pageant application. It runs in the background and makes entering the passphrase transparent. For client systems running Linux, you can use the ssh agent. For setting up and using either of these applications, see their product documentation. Multiple CMC sessions A list of multiple CMC sessions that are possible by using the various interfaces is given here. Table 5.
Updating firmware 4 You can update firmware for: • The CMC • Chassis infrastructure • I/O Module • PERC • Expander and HDD You can update firmware for the following server components: • BIOS • iDRAC7 • iDRAC8 • Lifecycle Controller • 32–bit diagnostics • Operating system Drivers Pack • Network Interface Controllers • RAID controllers Signed CMC firmware image The CMC firmware includes a signature.
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. Updating CMC firmware using web interface To update the CMC firmware using the CMC web interface: 1. In the left pane, go to any of the following pages: • 2.
• 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.
Updating chassis infrastructure firmware using RACADM To update chassis infrastructure firmware using RACADM, use the fwupdate sub-command. 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.
The Lifecycle Controller provides module update support for iDRAC7 and later servers. The iDRAC firmware must be at version 2.3 or later to update firmware using Lifecycle Controller. Dell Update Packages (DUPs) are used to perform the firmware updates using Lifecycle Controller. The Operating System Driver Pack component DUP exceeds this limit and must be updated separately using the Extended Storage feature.
EXTRAS/M/WHITE_PAPERS/20438118/DOWNLOAD on the Dell Tech Center. For information on saving the inventory file that DRM uses as input to create the repositories, see Saving Chassis Inventory Report Using CMC Web Interface NOTE: The Single Click all blade update method has the following benefits: • Enables you to update all the components on all the blade servers with minimal clicks. • All the updates are packaged in a directory. This avoids individual upload of each component’s firmware.
Server component update sequence In case of individual component updates, you must update the firmware versions for the server components in the following sequence: • iDRAC • Lifecycle Controller • BIOS • Diagnostics (optional) • OS Driver Pack (optional) • RAID • NIC • CPLD • Other Components NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecycle Controller.
• Update from Network Share Filtering components for firmware updates Information about all the components and devices across all servers is retrieved at one time. To manage this large amount of information, Lifecycle Controller provides various filtering mechanisms. NOTE: To use this feature, you must have an Enterprise License.
• A hyperlink is provided to an alternative page, where you can directly update only the iDRAC firmware. This page supports only iDRAC firmware update and not any other component and device on the server. iDRAC firmware update is not dependent on the Lifecycle Controller service. • If the inventory of components and devices do not reflect what is physically installed on the server, you must invoke the Lifecycle Controller when the server is in the boot process.
Field Description Job Status Displays the job status of any operations that are scheduled on the server. The job status is continuously updated dynamically. If a job completion with state completed is detected, then the firmware versions for the components and devices on that server are automatically refreshed in case there has been a change of firmware version on any of the components or devices.
• Profile Folder • Domain Name • User Name • Password For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3. Click Test Directory to verify whether the directories are readable and writeable. 4. Click Test Network Connection to verify if the network share location is accessible. 5. Click Apply to apply the changes to the network share properties. NOTE: Click Back to return to the Server Component Update page.
Reinstalling server component firmware You can reinstall the firmware image of the currently installed firmware for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller. Re-installing server component firmware using web interface To reinstall a server component firmware: 1. In the left pane, click Server Overview → Update. 2. On the Server Component Update page, click the appropriate type in the Choose Update Type section. 3.
It is recommended to clear the job queue before initializing a server component firmware update. A list of all jobs on the servers is available on the Lifecycle Controller Jobs page. This page enables deletion of single or multiple jobs or purging of all jobs on the server. BIOS updates are specific to the model of the server. Sometimes, even though a single Network Interface Controller (NIC) device is selected for firmware update on a server, the update may get applied to all the NIC devices on the server.
6. 7. Select one of the following options: • Reboot Now — Reboot immediately. The firmware update is applied immediately • On Next Reboot — Manually reboot the server at a later time. The firmware update is applied after the next reboot. NOTE: This step is not valid for Lifecycle Controller and 32-bit Diagnostics firmware update. A server reboot is not required for these devices. Click Update. The firmware version is updated for the selected component or device.
The Inventory.xml file is saved on an external system. The Dell Repository Manager uses the inventory.xml file to create customized bundles of updates. This Repositry is stored in the CIFS or NFS Share configured by CMC. For information on creating a repository using the Dell Repository Manger see the Dell Repository Manager Data Center Version 1.8 User’s Guide and the Dell Repository Manager Business Client Version 1.8 User’s Guide available at dell.com/support/manuals. 5.
Viewing chassis information and monitoring chassis and component health 5 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 Viewing chassis and component summaries When you log in to the CMC web interface, the Chassis Health page displays the health of the chassis and its components.
component. Other components display icons that visually represent the physical component. Pausing the cursor over a component displays a tool tip with additional information about that component. Selected component information Information for the selected component is displayed in three independent sections: • Health and Performance, and Properties — Displays the active, critical, and non-critical events as displayed by the hardware logs and the performance data that vary with time.
Component Heath and Performance Properties Storage Sleds Properties • Asset Tag • Number of Controllers Quick Links – Physical Disk Slots – Connected to Server – Controller Mode Capability • Power Supply Units Power Status Intrusion State Capacity • Power Supply Status • Power Consumption • System Budget PCIe Devices • Installed • Model • PCIe Status • Assigned • Mapping • PCIe Setup • Vendor ID • Device ID • Slot Type • Module Type • Fabric • Power Status Fans IOM
Viewing chassis summary To view the chassis summary information, in the left pane, click Chassis Overview → Properties → Summary. The Chassis Summary page is displayed. For more information about this page, see the CMC for Dell PowerEdge FX2/FX2s Online Help. Viewing chassis controller information and status To view the chassis controller information and status, in the CMC Web interface, click Chassis Overview → Chassis Controller. The Chassis Controller Status page is displayed.
Viewing information and health status of fans CMC controls the speed of the chassis fan by increasing or decreasing the fan speed on the basis of system events. You can run the fan in three modes such as Low, Medium, and High (fan offset). For more information about configuring a fan, see the CMC for Dell PowerEdge FX2/FX2s Online Help. To set up the properties of fans by using RACADM commands, type the following command at the CLI interface.
correspond to a fan speed offset (increase) of 20%, 50%, and 100% of the maximum speed respectively. There are also minimum speeds setup for each option, which are 35% for Low, 65% for Medium, and 100% for High. Using the Medium Fan Offset setting for example, increases the speed of fans by 50% of its maximum speed. The increase is above the speed already set by the system for cooling on the basis of installed hardware configuration.
NOTE: The temperature probes value cannot be edited. Any change beyond the threshold generates an alert that causes the fan speed to vary. For example, if the CMC ambient temperature probe exceeds the threshold, the speed of the fans on the chassis increases.
Configuring CMC 6 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.
Enabling the CMC network interface To enable or disable the CMC network interface for both IPv4 and IPv6, type: racadm config -g cfgLanNetworking -o cfgNicEnable 1 racadm config -g cfgLanNetworking -o cfgNicEnable 0 NOTE: If you disable CMC network interface, the disable operation performs the following actions: • Disables the network interface access to out-of-band chassis management, including iDRAC and IOM management. • Prevents the down link status detection.
Enabling or disabling DHCP for DNS IP addresses By default, the CMC’s DHCP for DNS address feature is disabled. When enabled, this feature obtains the primary and secondary DNS server addresses from the DHCP server. While using this feature, you do not have to configure static DNS server IP addresses.
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.
Configuring auto negotiation, duplex mode, and network speed (IPv4 and IPv6) When enabled, the auto negotiation feature determines whether the CMC automatically sets the duplex mode and network speed by communicating with the nearest router or switch. By default, auto negotiation feature is enabled.
3. Click Apply Changes. • When Management Port 2 is set for Redundant but is cabled for Stacking, the downstream CMCs (further from the top-of-rack switch) does not have a network link. • When Management Port 2 is set for Stacking but is cabled for Redundant (two connections to the TOR switch), routing loops could cause a network storm. Configuring Management Port 2 using RACADM To specify Redundant operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 1 command.
NOTE: To modify service settings, you must have the Chassis Configuration Administrator privilege. Remote syslog is an additional log target for CMC. After you configure the remote syslog, each new log entry generated by CMC is forwarded to the respective destinations. NOTE: Because the network transport for the forwarded log entries is UDP, there is no guaranteed delivery of log entries, nor is there any feedback to CMC about whether the log entries were received successfully.
For more information about these options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3. Click Apply to apply the selected option. Setting up Chassis Group CMC enables you to monitor multiple chassis from a single lead chassis. When a chassis group is enabled, CMC in the lead chassis generates a graphical display of the status of the lead chassis and all member chassis within the chassis group. To use this feature, you must have an Enterprise License.
5. In the User Name field, enter a user name with chassis administrator privileges for the member chassis. 6. Type the corresponding password in the Password field. 7. Optionally, select Sync New Member with Leader Properties to push leader properties to the member. For more information about adding members to chassis group, see Synchronizing a New Member With Leader Chassis Propertie. 8. Click Apply. 9. To add a maximum of eight members, complete the tasks in step 4 through step 8.
Launching the web page of a Member chassis or server You can access the web page of the member chassis, remote console of the server, or the web page of the iDRAC server from the lead chassis group page. If the member device has the same login credentials as the lead chassis, you can use the same credentials to access the member device. NOTE: Single Sign On and Smart Card Login are not supported in Multiple Chassis Management.
Synchronizing a new Member with Leader chassis properties You can apply the properties from the leader to a newly added member chassis of a group. To synchronize a new member with the leader properties: 1. Log in with administrator privileges to the leader chassis. 2. Select the lead chassis in the tree structure. 3. Click Setup → Group Administration. 4. While adding a new member to the group, in the Chassis Group page, select Sync New Member with Leader Properties. 5. Click Apply.
Chassis Configuration Profiles The Chassis Configuration Profiles feature enables you to configure the chassis with the chassis configuration profiles stored in the network share or local management station, and also restore configuration of the chassis. To access the Chassis Configuration Profiles page in the CMC web interface, in the system tree, go to Chassis Overview and click Setup → Profiles. The Chassis Configuration Profiles page is displayed.
NOTE: To view the settings that are saved to the XML file, in the Stored Profiles section, select the saved profile and click View in the View Profiles column. 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.
3. Click OK to apply the profile to the chassis. 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.
The import and export operation to and from the network share can be done through local RACADM as well as remote RACADM. Whereas, the import and export operation to and from the local management can be done only through remote RACADM interface. 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.
You can import chassis configuration profiles from local management station through remote RACADM interface. 1. To export the chassis configuration profiles as clone.xml file, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml Parsing Rules You can manually edit properties of an exported XML file of chassis configuration profiles. An XML file contains the following properties: • System Configuration, which is the parent node.
NOTE: Redirecting the CMC configuration to a file using getconfig -f is only supported with the remote RACADM interface. 3. Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database. 4. Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5. Reset the target CMC that was configured.
• The .cfg parser ignores an index object entry. You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the first available index for that group. The racadm getconfig -f .cfg command places a comment in front of index objects, allowing you to see the included comments.
# [cfgLanNetworking] cfgNicIpAddress=10.35.9.143 # comment, the rest of this line is ignored cfgNicGateway=10.35.9.1 The command racadm config -f .cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update. Use this file to download company-wide changes or to configure new systems over the network with the command, racadm getconfig -f .cfg.
Configuring servers 7 You can configure the following settings of a server: • Slot Names • iDRAC Network Settings • DRAC VLAN Tag Settings • First Boot Device • Server FlexAddress • Remote File Share • BIOS Settings Using Server Clone Configuring slot names Slot names are used to identify individual servers. When choosing slot names, the following rules apply: • Names may contain a maximum of 15 non-extended ASCII characters (ASCII codes 32 through 126).
The slot name setting in the CMC web interface always overrides any change you make to the display name in the iDRAC interface. To edit a slot name using the CMC Web interface: 1. In the left pane, go to Chassis Overview → Server Overview → Setup → Slot Names. 2. On the Slot Names page, edit the slot name, in the Slot Name field. 3. To use a server’s host name as slot name, select the Use Host Name for the Slot name option.
Setting Description • • root user password if Change Root Password is selected. Server Profile Only — Select this option to apply server profile assigned when a new server is inserted in the chassis. Quick Deploy and Server Profile — Select this option to first apply the iDRAC network settings, and then to apply the server profile assigned when a new server is inserted in the chassis.
Setting Description network. Quick Deploy feature does not work for servers that are inserted into slots for which there is no reserved static IPv4 address. Starting iDRAC IPv4 Address (Slot 1) Specifies the static IP address of iDRAC in the server, in slot 1 of the enclosure. The IP address of each subsequent iDRAC is incremented by 1 for each slot from slot 1's static IP address. In the case where the IP address plus the slot number is greater than the subnet mask, an error message is displayed.
The QuickDeploy feature only executes when it is enabled, and a server is inserted in the chassis. To copy the QuickDeploy settings into the iDRAC Network Settings section, click Auto-Populate Using QuickDeploy Settings. The QuickDeploy network configurations settings are copied into the corresponding fields in the iDRAC Network Configuration Settings table.
• Top row contains full-width sleds and bottom row contains only quarter-width sleds: NOTE: The Reserved QuickDeploy IPAddresses must be set to a minimum of 8. Modifying iDRAC Network Settings for individual server iDRAC Using this feature, you can configure the iDRAC network configurations settings for each installed server. The initial values displayed for each of the fields are the current values read from the iDRAC. To use this feature, you must have an Enterprise License.
Configuring iDRAC VLAN tag settings VLANs are used to allow multiple virtual LANs to co-exist on the same physical network cable and to segregate the network traffic for security or load management purposes. When you enable the VLAN functionality, each network packet is assigned a VLAN tag. VLAN tags are chassis properties. They remain with the chassis even when a component is removed.
device or an one-time device so that you can boot an image to perform tasks such as running diagnostics or reinstalling an operating system. You can set the first boot device for the next boot only or for all subsequent reboots. You can also set the first boot device for the server.
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.
• Enhanced Network Adapter Isolation: Uplink configuration for enhanced security in multi-tenant configurations. This configuration isolates the individual network adapters with a dedicated IOM port mapped to the LOM of each node. Only the LOM1 on each node is operational. 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.
modified and are intended to be replicated across servers. The following three profile groups for servers are displayed and can be replicated: • BIOS — This group includes only the BIOS settings of a server. • BIOS and Boot — This group includes the BIOS and the Boot settings of a server. • All Settings — This version includes all the settings of the server and components on that server. These profiles are generated from: – 12th generation servers with iDRAC7 1.57.
Adding or saving profile Before copying the properties of a server, first capture the properties to a stored profile. Create a stored profile and provide a name and optional description for each profile. You can save a maximum of 16 stored profiles on the CMC nonvolatile extended storage media. NOTE: If a remote share is available, you can store a maximum of 100 profiles using the CMC extended storage and remote share.
The operation status, slot number, slot name, and model name is displayed for each server in the Apply Profile table. NOTE: If a server does not support Lifecycle Controller or the chassis is turned off, you cannot apply a profile to the server. To apply a profile to one or more servers: 1. Go to the Server Profiles page. In the Save and Apply Profiles section, select the server or servers for which you want to apply the selected profile. The Select Profile drop-down menu gets enabled.
A message is displayed prompting you to select the destination of the file: • Local or Network Share if the source file is on a SD card. 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.
To enable CSIOR on: 1. 12th generation servers — After rebooting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes. 2. 13th generation servers —After rebooting the server, when prompted, press F10 to access Lifecycle Controller. Go to the Hardware Inventory page by selecting Hardware Configuration → Hardware Inventory. On the Hardware Inventory page, click Collect System Inventory on Restart.
Assigning server profiles to slots The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots: 1. In the Server Profiles page, click Profiles for QuickDeploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Assign Profile column.
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. The main advantage of this feature is the use of a virtual MAC address pool that is unique and shared across all chassis. This feature allows you to manage server operations online without physical intervention if the server stops functioning.
NOTE: While saving a boot identity profile, the standard ASCII extended character set is supported. However, the following special characters are not supported: ), “, ., *, >, <, \, /, :, |, #, ?, and , 4. Select a MAC address for the base profile from the Virtual MAC Address drop-down and click Save Profile. The number of templates created are based on the number of profiles you specify.
To clear boot identity profiles: 1. Go to the Server Profiles page. In the Boot Identity profiles section, select the server from which you want to clear the boot identity profile. NOTE: This option is enabled only if any of the servers are selected and boot identity profiles are applied to the selected servers. 2. Click Clear Identity. 3. Click OK to clear the boot identity profile from the selected server. The clear operation disables the IO Identity and persistence policy of the server.
A warning message is displayed indicating that deleting a profile would delete the selected profile permanently. 2. Click OK to delete the selected profile. For more information, see the CMC Online Help. Managing Virtual MAC Address Pool You can create, add, remove, and deactivate MAC addresses by using the Managing Virtual MAC Address Pool. You can only use unicast MAC addresses in the Virtual MAC Address Pool. The following MAC address ranges are allowed in CMC.
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. 4. Click OK to add MAC addresses. For more information, see the CMC Online Help.
true even if the same user does not have an account on iDRAC, or if the account does not have the Administrator’s privileges. • A CMC user who does NOT have the server administrative privilege, but has the same account on iDRAC is automatically logged into iDRAC using single sign-on. Once on the iDRAC site, this user is granted the privileges that were created for the iDRAC account.
Configuring storage sleds 8 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.
Viewing storage array status In the left pane, click Chassis Overview → Server Overview → . The Storage Array Status page is displayed in the right pane. You can also access the Storage Array Status page from the Chassis Health page. 1. On the Chassis Health page, click a storage sled on the front panel image. The details of the storage sled are displayed at the bottom of the right pane. 2. Under Quick Links, click Storage Array Status. For more information, see the Online Help.
Configuring CMC to send alerts 9 You can set alerts and actions for certain events that occur on the chassis. An event occurs when the status of a system component is greater than the pre-defined condition. If an event matches an event filter and you have configured this filter to generate an alert message (email alert or SNMP trap), then an alert is sent to one or more configured destinations such as email address, IP address, or an external server. To configure CMC to send alerts: 1.
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.
NOTE: Only one filter mask may be set for both SNMP and email alerting. You can skip step 2 if you have already selected the filter mask. 2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 3. Enable traps alerts: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts.
If your network has an SMTP server that releases and renews IP address leases periodically, and the addresses are different, then there is a duration when this property setting does not work due to change in the specified SMTP server IP address. In such cases, use the DNS name. Configuring 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.
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 assigned specifically to the chassis, such as IP mode (static or DHCP), static IP address, static gateway, and static subnet mask. Provides services to the chassis, such as date and time, firmware update, and CMC reset. Is associated with the chassis, such as slot name and slot priority. Although these properties apply to the servers, they are strictly chassis properties relating to the slots rather than the servers themselves.
Privilege Description When a CMC user who does not have Server Administrator privilege issues an action to be performed on a server, CMC sends a command to the targeted server with the user’s login name and password. If the user does not exist on the server, or if the password does not match, the user is denied the ability to perform the action. If the user exists on the target server and the password matches, the server responds with the privileges of which the user was granted on the server.
User Group Privileges Granted Power User • • • • Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator • • • Login Clear Logs Administrator Chassis Control Administrator (Power commands) Server Administrator Test Alert User Fabric A Administrator • • • Guest User Login Custom Select any combination of the following permissions: • • • • • • • • • None CMC Login User Chassis Configuration Administrator User Configuration Administrator Clear Logs Administrator Chas
Privilege Set Administrator Permissions Power User Permissions Guest User Permissions Fabric A Administrator Yes Yes No Modifying root user administrator account settings For added security, it is strongly recommended that you change the default password of the root (User 1) account. The root account is the default administrative account that is shipped with CMC. To change the default password for the root account: 1. In the left pane, click Chassis Overview, and then click User Authentication. 2.
If you are configuring a new CMC or if you have used the racadm racresetcfg command, the only current user account is default root account. The racresetcfg subcommand resets all configuration parameters to the default values. Any earlier changes are lost. NOTE: Users can be enabled and disabled over time, and disabling a user does not delete the user from the database.
• 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. Standard schema Active Directory overview As shown in the following figure, using standard schema for Active Directory integration requires configuration on both Active Directory and CMC.
NOTE: For more information about user privileges, see Types of Users. 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. Create a group or select an existing group. b. Configure the role privileges. 3. Add the Active Directory user as a member of the Active Directory group to access CMC.
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. 3. Specify the following: The settings to be configured for standard schema is displayed on the same page. NOTE: For information about the various fields, see the Online Help. • Common Settings • Server to use with LDAP: – Static server — Specify the FQDN or IP address and the LDAP port number.
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.1 • $ racadm config -g cfgLDAP -o cfgLDAPBaseDN dc= company,dc=com CMC can be configured to optionally query a DNS server for SRV records. If the cfgLDAPSRVLookupEnable property is enabled, the cfgLDAPServer property is ignored.
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.
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.aspx?FamilyID= 32BC1BEEA3F9-4C13-9C99-220B62A191EE&displaylang=en • For Single Sign-On or smart card login, the client system must be a part of the Active Directory domain and Kerberos Realm. CMC • Each CMC must have an Active Directory account. • CMC must be a part of the Active Directory domain and Kerberos Realm.
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 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 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 -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 Interface
To upload the keytab file: 1. In the left pane, click Chassis Overview → User Authentication → Directory Services. 2. Select Microsoft Active Directory (Standard Schema). 3. In the Kerberos Keytab section, click Browse, select a keytab file, and click Upload. When the upload is complete, a message is displayed indicating whether the keytab file is successfully uploaded or not.
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.
Command Description exit, logout, and quit All the commands perform the same action. They end the current session and return to a login commond line interface. 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.
Table 15.
For more information about the sshpkauth, see the Chassis Management Controller for PowerEdge FX2/FX2s Command Line Reference Guide. Configuring terminal emulation software CMC supports a serial text console that can be launched using any terminal emulation software. Following are the examples of terminal emulation software that can used to connect to CMC. 1. Linux Minicom 2.
NOTE: If the IOM does not support console redirection, the connect command displays an empty console. In that case, to return to the CMC console, type the Escape sequence. The default console escape sequence is <\>. To connect to an IOM: connect switch-n where n is an IOM label A1. When you reference the IOM in the connect command, the IOM is mapped to switch as shown in the following table. Table 16.
• off • on without console redirection • on with console redirection via COM1 To navigate between these options, press the appropriate arrow keys. NOTE: Make sure that the On with console redirection via COM1 option is selected. 4. Enable Redirection After Boot (default value is disabled). This option enables BIOS console redirection across subsequent reboots. 5. Save the changes and exit. The managed system restarts.
terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp) root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600 initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 initrd /boot/initrd-2.4.9-e.3.img When you edit the /etc/grub.
l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly.
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.
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 FlexAddress allows CMC to assign WWN/MAC IDs to a particular slot and override the factory IDs. Hence, if the server module is replaced, the slot based WWN/MAC IDs remain the same.
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: bound to another chassis, svctag=ABC1234, SD card SN = 1122334455. Remove the SD card; locate and install the SD card for the current chassis. 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.
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 card SN = SD card in the CMC module that is bound to the same service tag. $racadm featurecard -s The feature card inserted is valid and contains the following feature(s) FlexAddress: bound SD card in the CMC module that is not bound to any service tag.
FlexAddress DELL SOFTWARE LICENSE AGREEMENT This is a legal agreement between you, the user, and Dell Products L.P. or Dell Global B.V. ("Dell"). This agreement covers all software that is distributed with the Dell product, for which there is no separate license agreement between you and the manufacturer or owner of the software (collectively the "Software"). This agreement is not for the sale of Software or any other intellectual property.
other than Dell. Any replacement disk is warranted for the remaining original warranty period or thirty (30) days, whichever is longer. Dell does NOT warrant that the functions of the Software meets your requirements or that operation of the Software is uninterrupted or error free. You assume responsibility for selecting the Software to achieve your intended results and for the use and results obtained from the Software.
Texas. Each provision of this agreement is severable. If a provision is found to be unenforceable, this finding does not affect the enforceability of the remaining provisions, terms, or conditions of this agreement. This agreement is binding on successors and assigns. Dell agrees and you agree to waive, to the maximum extent permitted by law, any right to a jury trial with respect to the Software or this agreement.
• 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. In both the Basic mode and the Advanced mode, the WWN/MAC Addresses information is displayed in a collapsed form. Click the against a slot or click Expand/Collapse All to view the information for a specific slot or all the slots.
The WWN/MAC Summary page displays the WWN/MAC Address Information. 2. From the View drop-down menu, select Advanced, to view the WWN/MAC Addresses attributes in detailed view. In the WWN/MAC Addresses table displays Server Slot, Fabric, Protocol, WWN/MAC addresses, MAC address assignment type — Server assigned, FlexAddress, or I/O Identity MAC, and Partition Status. A green check mark indicates the active address type, either server-assigned, chassis-assigned, or remote assigned. MAC.
To display the iSCSI MAC for a specific server, use the following RACADM command: racadm getmacaddress [-m [-x]] [-t iscsi] To display the user-defined MAC and WWN address, use the following RACADM command: racadm getmacaddress -c io-identity racadm getmacaddress -c io-identity -m server -2 To display Ethernet and iSCSI MACS addresses of all LOMs or mezzanine cards, use the following RACADM command: racadm getmacaddress -a To display the console assigned MAC/WWN of all LOMs or mezzanine cards, use
Managing Fabrics 14 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. 2. If allowed, type the root password, SNMP RO Community string, and Syslog Server IP Address for the IOM.
Viewing I/O 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. 3.
The Firmware Update page is displayed, which provides a link to access the IOM Firmware and Software page. 2. In the IOM Firmware Update page, in the Firmware section, select the check box in the Update column for the IOM you want to update the software and click Apply Firmware Update. Alternatively, to rollback to the earlier versions of the software, select the check box in the Rollback column. 3. Select the software image for the software update, using the Browse option.
I/O Aggregator Module You can view details of IOM and Fixed Modules on the RACADM interface, Chassis Health, IOM Overview, and IOM Status pages. This information can also be viewed from CMC RACADM. You can view the fixed module information as a tooltip when you select an IOM on the Chassis Health, IOM Status, and IOM Overview pages.
Using VLAN Manager 15 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. Assigning VLAN to IOM Virtual LAN (VLAN) for IOMs allows you to separate users into individual network segments for security and other reasons. By using VLANs you can isolate the networks for individual users on a 32 port switch.
• 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. 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. NOTE: The CMC Managed VLANs section displays the summary of all VLANs assigned to the IOMs. 8. Click Apply.
An Operation Successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field. 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. 2. In the Select I/O Module section, select the required IOMs. 3.
Managing and monitoring power 16 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.
Chassis power limit monitoring OpenManage Power Center (OMPC) can be used to monitor and control power consumption of the machines in a data center. PowerEdge FX2/FX2s enables OMPC by providing a provision to set the power cap for the chassis, and bounds to guide the setting of the power cap. The lower and upper bounds for the power cap are set by the CMC and cannot be configured. NOTE: The lower bound is the minimum power needed to operate the chassis given the current configuration.
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.
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). The power management service optimizes power consumption and reallocates power to different modules on the basis of 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 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 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. 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 20.
PCIe Slot Mapping for quarter-width sleds (PowerEdge FC430) PCIe slot-3 1d PCIe slot-4 1c 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.
For example, to view the properties of PCIe device 1, run the following command. • racadm getpciecfg -c pcie.chassisslot.1 To view the existing PCIe configuration settings, run the following command: racadm getconfig –g cfgPCIe NOTE: The PCIe card is not powered on if the Mezzanine card is not present in the associated Sled. 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.
• 1 — Enable • 0 — Disable To enable a PCIe reassignment, run the following command: racadm config –g cfgPCIe –o cfgPCIeReassignmentEnable 1 To disable a PCIe reassignment, run the following command: racadm config –g cfgPCIe –o cfgPCIeReassignmentEnable 0 For more information, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/Manuals.
Troubleshooting and recovery 18 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.
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.
– Resolution B: Check if all power supplies are properly connected to the two AC grids: the power supply in side 1 must be connected to one AC grid, the one in side 2 must be connected to the other AC grid, and both AC grids must be working. Grid Redundancy is lost when one of the AC grids is not functioning. • Problem: The PSU state is displayed as Failed (No AC), even when an AC cord is connected and the power distribution unit is producing good AC output. – Resolution A: Check and replace the AC cord.
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.
To disable NTP, type: racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 0 To enable NTP, type: racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 1 If the NTP servers are configured correctly and this entry is present in the trace log, then this confirms that CMC is not able to synchronize with any of the configured NTP servers.
Component IOM (Common) IOM (Pass through) Fan PSU LED Color, Blinking Pattern Status Amber, blinking Fault Blue, dark No fault Green, glowing steadily Turned on Green, blinking Firmware is being uploaded Green, dark Turned off Blue, glowing steadily Normal/stack master Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault/stack slave Green, glowing steadily Turned on Green, blinking Not used Green, dark Powere
Component LED Color, Blinking Pattern Status PCI Blue, dark Turned On Blue, blinking PCI identification is in progress.
Recovering Firmware Image CMC enters recover mode when a normal CMC operating boot is not possible. In recover mode, a small subset of commands are available that allow you to reprogram the flash devices by uploading the firmware update file, fx2_cmc.bin. This is the same firmware image file used for normal firmware updates. The recovery process displays its current activity and boots to the CMC OS upon completion.
• Problem: Storage module is not detected on insertion. Storage module inserted and the associated server powered on, is not detected Resolution: . Ensure that the associated server is power cycled after the storage module is inserted. • Problem: Storage module is inserted and the associated server is power cycled, but the storage module is not detected. Resolution: Check the chassis log for more details about the failure.
NOTE: Make sure that the CMC module is in a passive state before you begin. To perform management actions, a user with Administrator privileges is required. If the administrator account password is forgotten, it can be reset using the J_PWORD jumper on the CMC board. The J_PWORD jumper uses a two-pin connector as shown in the following figure.
Table 24. CMC Password Jumper Settings J_PWORD (default) The password reset feature is disabled. The password reset feature is enabled. 3. Slide the CMC module into the enclosure. Reattach any cables that were disconnected. NOTE: Make sure that the CMC module is active until the remaining steps are completed. 4. Wait for the CMC to finish rebooting. In the web interface, in the system tree, go to Chassis Overview and click Power → Control, select the Reset CMC (warm boot), and click Apply. 5.
Frequently asked questions 19 This section lists the frequently asked questions about the following: • RACADM • Managing and Recovering a Remote System • Active Directory • IOM RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) What does this message mean? Another command must be issued only after CMC completes the reset.
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.
Remote Access: SNMP Authentication Failure As part of discovery, IT Assistant attempts to verify the device’s get and set community names. In IT Assistant, the get community name = public and the set community name = private. By default, the community name for the CMC agent is public. When IT Assistant sends out a set request, the CMC agent generates the SNMP authentication error because it only accepts requests from community = public. Change the CMC community name using RACADM.
Yes. All SSL certificates for Active Directory servers in the forest must be signed by the same root certificate authority-signed certificate, because CMC only allows upload of one trusted certificate authority-signed SSL certificate. The Web interface does not launch after a new RAC certificate is created and uploaded. If Microsoft Certificate Services is used to generate the RAC certificate, the User Certificate option may have been used instead of Web Certificate, when creating the certificate.
