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 © 2014 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 Using RACADM........................................... 32 3 Logging in to CMC..............................................................................................33 Configure Public Key Authentication Over SSH.................................................................................33 Generating Public Keys for Systems Running Windows..............................................................
Selected Component Information................................................................................................57 Viewing Server Model Name and Service Tag............................................................................. 58 Viewing Chassis Summary.................................................................................................................. 58 Viewing Chassis Controller Information and Status.......................................................................
7 Configuring Servers............................................................................................76 Configuring Slot Names......................................................................................................................76 Configuring iDRAC Network Settings.................................................................................................77 Configuring iDRAC QuickDeploy Network Settings....................................................................
Configuring E-Mail Alert Settings................................................................................................. 95 9 Configuring User Accounts and Privileges....................................................98 Types of Users.....................................................................................................................................98 Modifying Root User Administrator Account Settings.....................................................................
Configuring Terminal Emulation Software.......................................................................................116 Connecting to Servers or I/O Module Using Connect Command..................................................116 Configuring the Managed Server BIOS for Serial Console Redirection.....................................117 Configuring Windows for Serial Console Redirection...............................................................
Redundancy Policies.........................................................................................................................140 Grid Redundancy Policy..............................................................................................................140 No Redundancy Policy................................................................................................................140 Redundancy Alerting Only Policy.................................................................
Managing and Recovering a Remote System.................................................................................. 159 Active Directory.................................................................................................................................160 IOM.....................................................................................................................................................161 Event and Error Messages.........................................................
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: • 13th generation Blade Servers. • Enhanced WWN/MAC Address Inventory that includes WWN/MAC addresses assigned to a LOM/ Select Network Adapter (SNA) using the iDRAC IO Identity feature. • Viewing status of NIC Partitions as part of the WWN/MAC Address Inventory independent of the OS.
• 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.
Item Indicator, Button, or Connector 3 Diagnostic indicators 4 Enclosure power-on indicator, power button 5 Sleds 6 Video connector 7 USB connector Supported Remote Access Connections The following table lists the supported Remote Access Connections. Table 1. Supported Remote Access Connections Connection Features CMC Network Interface ports • Gb ports: Dedicated network interface for the CMC web interface.
Supported Platforms The CMC supports the PowerEdge FX2 and FX2s chassis models. The supported platforms are PowerEdge FC630 and PowerEdge FM120x4. For information about compatibility with CMC, see the documentation for your device. For the latest supported platforms, see the Dell Chassis Management Controller (CMC) Version 1.1 for Dell PowerEdge FX2/FX2s Release Notes available at dell.com/support/manuals.
• View — View the current license information. • Import — After acquiring the license, store the license in a local storage and import it into CMC using one of the supported interfaces. The license is imported if it passes the validation checks. NOTE: For a few features, a CMC restart may be required to enable the features. • Export — Export the installed license into an external storage device back up or to reinstall it after a service part is replaced.
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 FlexAddress Enablement No Yes One-to-many Server Firware Update No Yes One-to-many configuration for iDRAC No Yes License Component State or Condition and Available Operations The following table provides the list of l
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. Supported Management Console Applications The CMC supports integration with Dell OpenManage Console. For more information, see the OpenManage Console documentation available at dell.com/support/manuals.
• The setup placemat shipped with your system provides information about the initial system setup and configuration. • The server module's Owner's Manual provides information about the server module's features and describes how to troubleshoot the server module and install or replace the server module's components. This document is available online at dell.com/poweredgemanuals. • The rack documentation included with your rack solution describes how to install your system into a rack, if required.
– Client Systems Management – Connections Client Systems Management d. • To view a document, click the required product version. Using search engines: – Type the name and version of the document in the search box.
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.
To use remote RACADM from your management station, install remote RACADM using the Dell Systems Management Tools and Documentation DVD that is available with your system. For more information on Remote RACADM Web Interface Provides remote access to CMC using a graphical user interface. The Web interface is built into the CMC firmware and is accessed through the NIC interface from a supported web browser on the management station.
(DMTF) Common Information Model (CIM)–based management information. The CIM information defines the semantics and information types that can be modified in a managed system. The CMC WS-MAN implementation uses SSL on port 443 for transport security, and supports basic authentication. The data available through WSManagement is provided by CMC instrumentation interface mapped to the DMTF profiles and extension profiles. NOTE: The SSL port used for transport security is the same as the CMC HTTPS port.
For information about installing Dell OpenManage software components, see the Dell OpenManage Installation and Security User's Guide available at dell.com/support/manuals. You can also download the latest version of the Dell DRAC Tools from support.dell.com. Installing Remote RACADM on a Windows Management Station If you are using the DVD, run \SYSMGMT\ManagementStation\windows\DRAC\<.msi file name> If you have downloaded the software from support.dell.com: 1.
Configuring a Web Browser You can configure and manage CMC, servers, and modules installed in the chassis through a web browser. See the “Supported Browsers" section in the Dell Systems Software Support Matrix at dell.com/ support/manuals. The CMC and the management station where you use your browser must be on the same network, which is called the management network. On the basis of your security requirements, the management network can be an isolated and highly secure network.
To configure Internet Explorer to play animations: 1. Start Internet Explorer. 2. Click Tools → Internet Options → Advanced. 3. Go to the Multimedia section, and then select the Play animations in web pages option. Downloading and Updating CMC Firmware To download the CMC firmware, see Downloading CMC Firmware. To update the CMC firmware, see Updating CMC Firmware.
Setting Date and Time on CMC Using RACADM To set the date and time using the command line interface, see the config command and cfgRemoteHosts database property group sections in the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals. For example racadm setractime -l 20140207111030. To read the date and time use racadm getractime command.
Configuring Front Panel You can use the front panel page to configure: • Power button • KVM Configuring Power Button To configure the chassis power button: 1. In the left pane, click Chassis Overview → Front Panel → Setup. 2. On the Front Panel Configuration page, under the Power Button Configuration section, select the Disable Chassis Power Button option, and then click Apply. The chassis power button is disabled. Accessing a Server Using KVM To map a Server to KVM from Web Interface: 1.
• None — This mode does not enable you to monitor or manage the chassis component through iDRAC, OS, or Lifecycle Controller. • Monitor — This mode enables you to monitor the chassis components but you cannot perform any firmware update through iDRAC, OS, or Lifecycle Controller. • Manage and Monitor — This mode enables you to monitor the chassis components and update the CMC firmware using DUP through iDRAC, OS, or Lifecycle Controller.
Logging in to 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 in to 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 version of the CMC using Dell Update Package (DUP) through the following components: • iDRAC • 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.
Choosing Server Component Firmware Update Type Using CMC Web Interface To select the type of server component update type: 1. In the system tree, go to Server Overview, and then click Update → Server Component Update. The Server Component Update page is displayed. 2.
Viewing Firmware Inventory Using CMC Web Interface To view the firmware inventory: 1. In the left pane, click Server Overview, and then click Update. 2. On the Server Component Update page, view the firmware inventory details in the Component/ Device Firmware Inventory section. On this page, you can view the following information: • If the server is listed as Not Ready, it indicates that when the firmware inventory was retrieved, the iDRAC on the server was still initializing.
Field Description Model Displays the model of the server. Component/ Device Displays a description of the component or device on the server. If the column width is too narrow, the mouse-over tool provides a view of the description. Current Version Displays the current version of component or device on the server. Rollback Version Displays the rollback version of component or device on the server. Job Status Displays the job status of any operations that are scheduled on the server.
The Edit Network Share page is displayed. 2. In the Network Share Settings section, configure the following settings as required: • Protocol • IP Address or Host Name • Share Name • Update folder • File Name (optional) NOTE: File Name is optional only when the default catalog file name is catalog.xml. If the catalog file name is changed then the new name must be entered in this field.
indicating the situation and the operation must not be submitted. Wait for the operation in process to complete and then submit the operation again. Do not navigate away from the page after an operation is submitted for scheduling. If an attempt is made, a confirmation message is displayed allowing the intended navigation to be cancelled. Otherwise, the operation is interrupted.
Upgrading Server Component Firmware You can install the next version of the firmware image for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller for a rollback operation. To use this feature, you must have an Enterprise License. NOTE: For iDRAC and Operating System Driver packs firmware update, make sure the Extended Storage feature is enabled.
Few devices such as Network Interface Controllers (NICs) and RAID Controllers contain many types and models. The update selection logic automatically filters the relevant device type or model based on the initially selected devices. The primary reason for this automatic filtering behavior is that only one firmware image file for the category can be specified. NOTE: The update size limitation of either a single DUP or combined DUPs can be ignored if the Extended Storage feature is installed and enabled.
Upgrading Server Component Firmware From Network Share Using CMC Web Interface To upgrade the server components firmware version to the next version using the Update from Network Share mode: 1. In the CMC Web interface, in the system tree, go to Server Overview and then click Update → Server Component Update. The Server Component Update page is displayed. 2. In the Choose Update Type section, select Update from Network Share. For more information, see Choosing Server Component Firmware Update Type. 3.
Deleting Scheduled Server Component Firmware Jobs Using the Web Interface To delete scheduled server component firmware jobs: 1. In the left pane, click Server Overview, and then click Update. 2. On the Server Component Update page, filter the component or device (optional). 3. In the Job Status column, if a check box is displayed next to the job status, it implies that a Lifecycle Controller job is in progress and currently in the indicated state. It can be selected for a job-deletion operation. 4.
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 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. It displays a graphical view 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.
Componen t Heath and Performance Properties Properties Quick Links PCIe Devices • Installed • Model • PCIe Status • Assigned • Mapping • PCIe Setup • Vendor ID • Device ID • Slot Type • Module Type • Fabric • Power Status Fans IOM Slot • Speed • Warning Threshold • Fans Status • PWM (% of Max) • Critical Threshold • Fan Configuration • Fan Offset • Power State • Model IOM Status • Role • Service Tag Viewing Server Model Name and Service Tag You can view
• Click Chassis Overview → Server Overview. The Servers Status page provides an overview of the servers in the chassis. For more information, see the Online Help. Viewing Information and Health Status of the IOMs To view health status of the IOMs, in the CMC Web interface, do any of the following: 1. Click Chassis Overview . The Chassis Health page is displayed. The graphics in the left pane displays the rear, front, and top view of the chassis and contains the health status for the IOM.
The Fans Status page provides the status, speed measurements in revolutions per minute (RPMs), and threshold values of the fans in the chassis. There can be one or more fans. NOTE: In the event of a communication failure between CMC and the fan unit, CMC cannot obtain or display the health status for the fan unit. NOTE: The following message is displayed when both the fans are not present in the slots or if a fan is rotating at a low speed: Fan is less than the lower critical threshold.
On the Status page, under the KVM Properties section, you can view the status and properties of a KVM associated with the chassis. For more information, see the Online Help. Viewing Information and Health Status of Temperature Sensors To view the health status of the temperature sensors: In the left pane, click Chassis Overview → Temperature Sensors. The Temperature Sensors Status page displays the status and readings of the temperature probes on the entire chassis (chassis and servers).
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.
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. The Chassis group features are: • Displays images portraying the front and back of each chassis, a set for the leader and a set for each member.
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. The chassis names of the new members appear in the Members dialog box.
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. 78 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: NOTE: For QuickDeploy to assign IP addresses to the bottom sled, the Reserved QuickDeploy IPAddresses field must be set to 4 for the bottom sled iDRAC.
To modify the iDRAC Network Settings: 1. In the left pane, click Server Overview, and then click Setup. On the Deploy iDRAC page the iDRAC Network Settings section lists the iDRAC IPv4 and IPv6 network configuration settings of all the installed servers. 2. Modify the iDRAC network settings as required for the servers. NOTE: You must select the Enable LAN option to specify the IPv4 or IPv6 settings. For information about the fields, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3.
2. • In the left pane, click Chassis Overview → Server Overview and click Setup → VLAN. On the VLAN Tag Settings page, in the iDRAC section, enable VLAN for the servers, set the priority and enter the ID. For more information about the fields, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3. Click Apply to save the settings.
You can set the following devices for first boot. Table 6. Boot Devices Boot Device Description PXE Boot from a Preboot Execution Environment (PXE) protocol on the Network Interface Card. Hard Drive Boot using a Hard disk drive. Local CD/DVD Boot from a CD or DVD drive on the server. BIOS Setup Boot during the BIOS setup. Virtual Floppy Boot from a virtual floppy disk. Virtual CD/DVD Boot from a Virtual CD or DVD drive. Local SD Card Boot from the local SD (Secure Digital) card.
3. From the First Boot Device drop-down menu, select the boot device you want to use for each server. 4. If you want the server to boot from the selected device every time it boots, clear the Boot Once option for the server. If you want the server to boot from the selected device only on the next boot cycle, select the Boot Once option for the server 5. Click Apply to save the settings. Setting First Boot Device Using RACADM To set the first boot device, use the cfgServerFirstBootDevice object.
Click Disconnect to disconnect a previously-connected remote file share. Click Deploy to deploy the media device. NOTE: Before you click the Deploy button, make sure that you save all the working files, because this action restarts the server. When you click Deploy, the following tasks are executed: • The remote file share is connected. • The file is selected as the first boot device for the servers. • The server is restarted. • Power is supplied to the server if the server is turned off.
• Export stored profiles to a management station or remote file share. • Delete stored profiles. • Deploy selected profiles to the target devices using Quick Deploy option. • Display the log activity for recent server profile tasks. Accessing Profile Page You can add, manage, and apply profiles to one or more servers using the Profile page. To access the Profile page using the CMC Web interface, in the left pane, click Chassis Overview → Server Overview → Setup → Profiles.
NOTE: When saving a Server Profile the list of characters that are not supported for the Profile Name include the character hash (#), comma (,) and question mark (?). The standard ASCII extended character set is supported. The following special characters are not supported: ), “, ., *, >, <, \, /, :, and | CMC communicates with the LC to get the available server profile settings and store them as a named profile. A progress indicator indicates that the Save operation is in progress.
Importing Profile You can import a server profile that is stored on a management station to CMC. To import a stored profile from CMC: 1. In the Server Profiles page, in the Stored Profiles section, click Import Profile. The Import Server Profile section is displayed. 2. Click Browse to access the profile from the required location and then click Import Profile. For more information, see the Online Help. Exporting Profile You can export a stored server profile to a specified path on a management station.
NOTE: You can edit the profile description only for profiles stored on SD cards. For more information, see the Online Help. Viewing Profile Settings To view Profile settings for a selected server, go to the Server Profiles page. In the Server Profiles section, click View in the Server Profile column for the required server. The View Settings page is displayed. For more information on the displayed settings, see the Online Help.
Quick Deploy of Profiles The Quick Deploy feature enables you to assign a stored profile to a server slot. Any server supporting server configuration replication that is inserted into a slot is configured using the profile assigned to that slot. You can perform the Quick Deploy action only if the Action When Server is Inserted option in the Deploy iDRAC page is set to Server Profile or Quick Deploy and Server 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.
Launching iDRAC from Servers Status Page To launch the iDRAC management console from the Servers Status page: 1. In the left pane, click Server Overview. 2. On the Servers Status page, click Launch iDRAC for the server you want to launch the iDRAC Web interface. Launching Remote Console from Server Status Page To launch a remote console for an individual server: 1. In the left pane, expand Server Overview. All the four servers appear in the expanded servers' list. 2.
Configuring CMC To Send Alerts 8 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 Email Alert Settings Using CMC Web Interface To configure the email 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.
9 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.
10 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.
11 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.
12 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 13 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. On the Configure I/O Module Network Settings page, type appropriate data, and then click Apply. 2.
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 14 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 15 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 purpose of the Grid Redundancy policy is to enable an enclosure system to operate in a mode in which it can tolerate AC power failures. These failures may originate in the AC power grid, the cabling and delivery, or a PSU itself.
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.
16 Viewing 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. PCIe slots cannot be reassigned or unassigned to the servers. PCIe Slot Mapping for PowerEdge FC630 PCIe slot-1 4 PCIe slot-2 4 PCIe slot-3 2 PCIe slot-4 2 PCIe slot-5 3 PCIe slot-6 3 PCIe slot-7 1 PCIe slot-8 1 NOTE: PCIe management is supported only for PowerEdge FX2s and not PowerEdge FX2.
Viewing PCIe Slot Properties Using RACADM You can view a PCIe slot assignment to a server by using the RACADM commands. Some of the commands are given here. For more information about the RACADM commands, see theDell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/Manuals. NOTE: The PCIe card name will be displayed only after the BIOS completes POST in the associated sSled. Until then, the device name will be displayed as Unknown.
Troubleshooting and Recovery 17 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. Amber, blinking Fault Troubleshooting Non-responsive CMC If you cannot log in to CMC using any of the interfaces (the web interface, Telnet, SSH, remote RACADM, or serial), you can verify the CMC functionality observing the LEDs on CMC, obtaining recovery information using the DB-9 serial port, or recovering the CMC firmware image.
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. When you type recover and then press at the recovery prompt, the recover reason and available sub-commands display. An example recover sequence may be: recover getniccfg recover setniccfg 192.168.0.120 255.255.255.0 192.168.0.1 recover ping 192.168.0.100 recover fwupdate -g -a 192.168.0.
Frequently Asked Questions 18 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.
