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............................................................................................................... 11 Key Features.........................................................................................................................................12 What is new in this release............................................................................................................ 12 Management features....................................................................
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............................................ 35 3 Logging into CMC.............................................................................................. 36 Configure public key authentication over SSH..............
Viewing chassis and component summaries.....................................................................................58 Chassis graphics............................................................................................................................ 58 Selected component information................................................................................................ 59 Viewing server model name and Service Tag......................................................................
Configuring multiple CMCs using RACADM...................................................................................... 76 Parsing rules...................................................................................................................................76 Modifying the CMC IP address..................................................................................................... 78 7 Configuring servers..................................................................................
Configuring storage sleds using CMC web interface........................................................................ 97 Configuring storage sleds using RACADM......................................................................................... 97 Managing storage sleds using iDRAC RACADM proxy...................................................................... 97 Viewing storage array status...........................................................................................................
Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM....... 117 Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface..... 117 Uploading Keytab file.........................................................................................................................117 Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM....... 118 12 Configuring CMC to use Command Line consoles............................
Resetting IOM to factory default settings.........................................................................................141 Updating IOM software using CMC web interface.......................................................................... 141 15 Using VLAN Manager..................................................................................... 143 Assigning VLAN to IOM.....................................................................................................................
Downloading SNMP Management Information Base (MIB) file.................................................159 First steps to troubleshoot a remote system..............................................................................159 Troubleshooting Alerts............................................................................................................... 160 Viewing Event Logs.....................................................................................................................
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: • PowerEdge FC830 and PowerEdge FC430 compute sleds. • PowerEdge FD332 and the following features that are supported for storage sleds: – Multiple compute-storage sled mappings. – Identification of storage sleds along with compute nodes. – Module reporting for storage sleds. – Move storage sleds to different slots or chassis.
• Multi-node Sled adaptation. PowerEdge FM120x4 is a multi-node Sled. • Chassis Power Limit Monitoring. • iDRAC IO Identity feature support for enhanced WWN/MAC Address Inventory. • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/ MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade. • Graphical display of chassis component status and health. • Support for single and multi-slot servers. • iDRAC single sign-on.
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.
Storage sled licenses You can also purchase storage sled licenses to manage RAID controllers in CMC. The storage sled licenses can be installed at the factory or purchased online. Following are the supported storage sled license types: • One RAID controller and one HBA controller (RAID/HBA) • Both RAID controllers Storage sled licenses can be used for one or two RAID controllers. If a license is assigned to RAID on a single controller, the license is applicable only to the first controller.
NOTE: If you have purchased a system with all the licenses pre-installed, then license management is not required. You can perform the following licensing operations using CMC, RACADM, and WS-MAN for one-to-one license management, and Dell License Manager for one-to-many license management: • View — View the current license information for CMC and storage sleds. • Import — After acquiring the license, store the license in a local storage and import it into CMC using one of the supported interfaces.
CMC Serial Port Yes Yes RACADM (SSH, Local, and Remote) Yes Yes WS-MAN Yes Yes SNMP Yes Yes Telnet Yes Yes SSH Yes Yes Web-based Interface Yes Yes Email Alerts Yes Yes CMC Settings Backup No Yes CMC Settings Restore Yes Yes Remote Syslog No Yes Directory Services No Yes Single Sign-On Support No Yes Two-Factor Authentication No Yes PK Authentication No Yes Remote File Share No Yes Enclosure level power capping No Yes Multi-chassis management No Yes FlexAd
License/ Component state or condition Import Export Delete Replace Learn More Non-administrator login No Yes No No Yes Active license Yes Yes Yes Yes Yes Expired license No Yes Yes Yes Yes License installed but component missing No Yes Yes No Yes Viewing localized versions of the CMC web interface To view localized versions of the CMC web interface, read through your web browser's documentations. To view the localized versions, set the browser to the desired language.
• The Dell OpenManage Server Administrator’s User’s Guide provides information about installing and using Server Administrator. • The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy. • Dell systems management application documentation provides information about installing and using the systems management software.
• From the Dell Support site: a. Go to dell.com/support/home. b. Under Select a product section, click Software & Security. c. In the Software & Security group box, click the required link from the following: – Enterprise Systems Management – Remote Enterprise Systems Management – Serviceability Tools – Client Systems Management – Connections Client Systems Management d. • To view a document, click the required product version.
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.
Setting chassis physical location and chassis name using RACADM To set the chassis name, location, date, and time by using the command line interface, see the setsysinfo and setchassisname commands. For example racadm setsysinfo —c chassisname or racadm setsysinfo —c chassislocation For more information, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.
Configuring LED blinking using CMC web interface To enable blinking for one, multiple, or all component LEDs: • In the left pane, go to any of the following pages: – Chassis Overview → Troubleshooting. – Chassis Overview → Chassis Controller → Troubleshooting. – Chassis Overview → Server Overview → Troubleshooting. NOTE: Only servers can be selected on this page. To enable blinking of a component LED, select the respective component , and then click Blink.
Accessing a server using KVM To map a Server to KVM from web interface: 1. Connect a monitor to the video connector and a keyboard to USB connector located on the front of the chassis. 2. In the left pane, click Chassis Overview → Front Panel → Setup. 3. On the Front Panel Configuration page, under the KVM Configuration section, select Enable KVM Mapping option. 4.
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 2.
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 on FM120x4 (12th generation of servers) • iDRAC8 on FC630 (13th generation of servers) • Lifecycle Controller • 32–bit diagnostics • Operating System Drivers Pack • Network Interface Controllers • RAID controllers Signed CMC firmware image The CMC firmware includes a signature.
Downloading CMC firmware Before beginning the firmware update, download the latest firmware version from support.dell.com, and save it to your local system. It is recommended to follow the following update order while updating firmware for the chassis: • • • Blade components firmware CMC firmware Chassis infrastructure firmware Viewing currently installed firmware versions You can view the currently installed firmware versions using the CMC web interface or RACADM.
firmware file transfer time may be as high as 30 minutes. To set the idle timeout value, see Configuring Services. During CMC firmware updates, it is normal for some or all of the fan units in the chassis to rotate at 100% speed. To avoid disconnecting other users during a reset, notify authorized users who may log in to CMC and check for active sessions on the Sessions page. To open the Sessions page, click Chassis Overview in the left pane, click Network, and then click the Sessions.
For more information about RACADM commands, see Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. Updating the CMC using DUP You can update the firmware of the CMC using Dell Update Package (DUP) through the following components: • 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.
• Do not click the Refresh icon, or navigate to another page during the file transfer. • The Update State field displays the firmware update status. When the update is complete, connection to the CMC is lost as the entire Chassis is reset. Refresh the web interface to login again. Go to Chassis Overview → Chassis Controller. After the update is complete the updated Mainboard firmware version is displayed. .
local system or on a network share. This operation is enabled by leveraging the Lifecycle Controller functionality on the server. The Lifecycle Controller service is available on each server and is facilitated by iDRAC. You can manage the firmware of the components and devices on the servers using the Lifecycle Controller service. The Lifecycle Controller uses an optimization algorithm to update the firmware that efficiently reduces the number of restarts.
server components in a single operation. You can setup a custom remote repository of firmware DUPs and binary images using the Dell Repository Manager and share it on the Network Share. Alternatively, use the Dell Repository Manager (DRM) to check for the latest available firmware updates. The Dell Repository Manager (DRM) ensures that the Dell systems are up-to-date with the latest BIOS, driver, firmware, and software. You can search for the latest updates available from the Support site (support.dell.
If Lifecycle Controller service is disabled on the server, the Component/Device Firmware Inventory section displays: Lifecycle Controller may not be enabled.
• Update from File • Update from Network Share Filtering components for firmware updates Information about all the components and devices across all servers is retrieved at one time. To manage this large amount of information, Lifecycle Controller provides various filtering mechanisms. NOTE: To use this feature, you must have an Enterprise License.
• 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 Individual Storage Sleds Properties • Service Tag • 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
A tool tip, if available, is displayed with the model name and Service Tag of the storage sled. 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 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.
Configuring multiple CMCs using RACADM Using RACADM, you can configure one or more CMCs with identical properties. When you query a specific CMC card using its group ID and object ID, RACADM creates the racadm.cfg configuration file from the retrieved information. By exporting the file to one or more CMCs, you can configure your controllers with identical properties in a minimal amount of time.
For example: # # This is a comment [cfgUserAdmin] cfgUserAdminPageModemInitString= • All group entries must be surrounded by open- and close-brackets ([ and ]). The starting [ character that denotes a group name must be in column one. This group name must be specified before any of the objects in that group. Objects that do not include an associated group name generate an error.
This is the list of the indexed groups that exhibit this behavior and their corresponding key properties: – cfgUserAdmin — cfgUserAdminUserName – cfgEmailAlert — cfgEmailAlertAddress – cfgTraps — cfgTrapsAlertDestIPAddr – cfgStandardSchema — cfgSSADRoleGroupName – cfgServerInfo — cfgServerBmcMacAddress Modifying the CMC IP address When you modify the CMC IP address in the configuration file, remove all unnecessary = entries.
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 settings, and then to apply the server profile assigned when a new server is inserted in the chassis. Set iDRAC Root Password on Server Insertion Select the option to change iDRAC root password to match the value provided in the iDRAC Root Password field, when a server is inserted.
Setting Description of each subsequent iDRAC is incremented by 1 for each slot from slot 1's static IP address. In the case where the IP address plus the slot number is greater than the subnet mask, an error message is displayed. NOTE: The subnet mask and the gateway are not incremented such as the IP address. For example, if the starting IP address is 192.168.0.250 and the subnet mask is 255.255.0.0 then the QuickDeploy IP address for slot 4c is 192.168.0.265. If the subnet mask is 255.255.255.
QuickDeploy IP address assignments for servers The following tables show the way that the QuickDeploy IP addresses assigned to the servers based on the sleds present in the FX2/FX2s Chassis: • Two full-width sleds in the chassis: • Four half-width sleds in the chassis: • Eight quarter-width sleds in the chassis: NOTE: The Reserved QuickDeploy IPAddresses must be set to a minimum of 8. • Four FM120x4 sleds in the chassis: NOTE: The Reserved QuickDeploy IPAddresses must be set to 16.
Modifying iDRAC Network Settings for individual server iDRAC Using this feature, you can configure the iDRAC network configurations settings for each installed server. The initial values displayed for each of the fields are the current values read from the iDRAC. To use this feature, you must have an Enterprise License. To modify the iDRAC Network Settings: 1. In the left pane, click Server Overview, and then click Setup.
NOTE: The iDRAC VLAN settings from CMC are effective only when iDRAC NIC selection is set on the iDRAC for Chassis (dedicated) LOM mode. Configuring iDRAC VLAN tag settings using web interface To configure VLAN for server: 1. Go to any of the following pages: • In the left pane, click Chassis Overview → Network → VLAN. 2. • In the left pane, click Chassis Overview → Server Overview and click Setup → VLAN.
NOTE: The first boot device setting in CMC web Interface overrides the system BIOS boot settings. The boot device that you specify must exist and contain a bootable media. You can set the following devices for first boot. However, to set a device as a default first-boot device, select Default. To not to override the server firmware version if the firmware version running on the server is same as the version available in the first boot device, select None. You can set the following devices for first boot.
Setting first boot device for individual server using CMC web interface NOTE: To set the first boot device for servers, you must have Server Administrator privileges or Chassis Configuration Administrator privileges and iDRAC login privileges. To set the first boot device for individual servers: 1. In the left pane, click Server Overview, and then click the server for which you want to set the first boot device. 2. Go to Setup → First Boot Device. The First Boot Device page is displayed. 3.
To perform a remote file share operation (connect, disconnect, or deploy), you must have the Chassis Configuration Administrator or Server Administrator privileges. To use this feature, you must have an Enterprise license. To configure the remote file share: 1. In the left pane, click Server Overview → Setup → Remote File Share. 2. On the Deploy Remote File Share page, type appropriate data in the fields.
• iDRAC must have the minimum version that is required. iDRAC7 servers require version 1.57.57. iDRAC8 servers require version 2.05.05. • Server must be turned on. You can: • View profile settings on a server or from a saved profile. • Save a profile from a server. • Apply a profile to other servers. • Import stored profiles from a management station or remote file share. • Edit the profile name and description. • Export stored profiles to a management station or remote file share.
3. Select Extended Storage or Network Share as the location to save the profile. NOTE: The Network Share option is enabled and the details are displayed in the Stored Profiles section only if the network share is mounted and is accessible. If the Network Share is not connected, configure the Network Share for the chassis. To configure the Network Share, click Edit in the Stored Profiles section. For more information, see Configuring Network Share Using CMC web Interface 4.
A warning message is displayed that applying a new server profile overwrites the current settings and also reboots the selected servers. You are prompted to confirm if you want to continue the operation. NOTE: To perform server cloning operations on servers, the CSIOR option must be enabled for the servers. If CSIOR option is disabled, a warning message is displayed that CSIOR is not enabled for the servers. To complete the blade cloning operation, make sure to enable CSIOR option on the servers. 4.
Editing profile You can edit the name and description of a server profile that is stored on the CMC nonvolatile media (SD Card). To edit a stored profile: 1. Go to the Server Profiles page. In the Stored Profiles section, select the required profile and then click Edit Profile. The Edit BIOS Profile — section is displayed. 2. Edit the profile name and description of the server profile as required and then click Edit Profile.
Completion status and troubleshooting To check the completion status of an applied BIOS profile: 1. In the left pane, click Chassis Overview → Server Overview → Setup → Profiles. 2. On the Server Profiles page, note down the Job ID (JID) of the submitted job from the Recent Profile Log section. 3. In the left pane, click Server Overview → Troubleshooting → Lifecycle Controller Jobs. Search for the same JID in the Jobs table.
NOTE: • A slot that does not have any profile assigned to it is indicated by the term "No Profile Selected" that appears in the select box. • To remove a profile assignment from one or more slots, select the slots and click Remove Assignment. A message is displayed warning you that removing a profile from the slot or slots removes the XML configuration settings in the profile from any servers inserted in the slots when Quick Deploy Profiles feature is enabled. Click OK to remove the profile assignments.
Launching iDRAC from Server Status page To launch the iDRAC management console for an individual server: 1. In the left pane, expand Server Overview. All four servers appear in the expanded Servers Overview list. 2. Click the server for which you want to launch the iDRAC Web interface. 3. On the Servers Status page, click Launch iDRAC GUI. The iDRAC Web interface is displayed. For information about the field descriptions, see the CMC for Dell PowerEdge FX2/FX2s Online Help.
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.
For more information, see the RACADM Command Line Reference Guide for iDRAC and CMC available at dell.com/support/manuals.
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 12.
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 13.
• 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 (available in PowerEdge FX2/FX2s) 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 (1–6) 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.
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 Open Manage 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 is 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.
Redundancy status and overall power health The redundancy status is a factor in determining the overall power health. When the power redundancy policy is set, for example, to grid redundancy and the redundancy status indicates that the system is operating with redundancy, the overall power health is typically OK. However, if the conditions for operating with grid redundancy cannot be met, the redundancy status is No, and the overall power health is Critical.
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 17.
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 164 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 P
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.
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.
