Dell Chassis Management Controller Version 2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview.........................................................................................................................11 Key Features......................................................................................................................................................................11 What is new in this release..........................................................................................................................................
Configuring chassis management at server mode............................................................................................................ 32 Configuring chassis management at server using CMC web interface....................................................................... 32 Configuring chassis management at server mode using RACADM............................................................................. 32 3 Logging into CMC..........................................................
Viewing chassis summary.................................................................................................................................................53 Viewing chassis controller information and status............................................................................................................ 53 Viewing information and health status of all servers.........................................................................................................
Applying Chassis Configuration Profiles......................................................................................................................68 Exporting Chassis Configuration Profiles.................................................................................................................... 68 Editing Chassis Configuration Profiles........................................................................................................................
Clearing Boot Identity Profiles.................................................................................................................................... 87 Viewing Stored Boot Identity Profiles..........................................................................................................................87 Importing Boot Identity Profiles..................................................................................................................................
Configuring the generic LDAP directory to access CMC...........................................................................................103 Configuring generic LDAP directory service using CMC web interface..................................................................... 103 Configuring generic LDAP directory service using RACADM.....................................................................................104 11 Configuring CMC for Single Sign-On or Smart Card login.......................
Viewing basic WWN or MAC address information using web interface........................................................................... 122 Viewing advanced WWN or MAC address information using web interface.................................................................... 122 Viewing WWN or MAC address information using RACADM...........................................................................................123 14 Managing Fabrics..............................................................
Configuring power budget and redundancy.............................................................................................................. 135 Executing Power Control Operations........................................................................................................................ 137 Executing Power Control Operations for Multiple Servers Using CMC Web Interface...............................................137 Executing Power Control Operations on the IOM........................
1 Overview The Dell Chassis Management Controller (CMC) for Dell EMC PowerEdge FX2/FX2s is a Systems Management hardware and software solution for managing the PowerEdge FX2/FX2s chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged. The CMC enables an IT administrator to: • View inventory. • Perform configuration and monitoring tasks. • Remotely turn on and turn off chassis and servers.
What is new in this release This release of CMC for Dell EMC PowerEdge FX2/FX2s supports: • Displaying fan speed and temperature information using WSMan. • Integrating the LLDP opensource daemon to forward the LLDP packets to iDRAC through VLAN. • Transferring CMC dumplogs to iDRAC. • Using PCIe retimer mezzanine card. • Using the Fault Tolerant Redundancy (FTR) option to request for new power.
• Centralized user authentication through: – Active Directory using Standard Schema or an Extended Schema (optional). – Hardware-stored user IDs and passwords. • Role-based authority — Enables an administrator to configure specific privileges for each user. • User ID and password configuration through the web interface. Web interface supports 128-bit SSL 3.0 encryption and 40-bit SSL 3.0 encryption (for countries where 128-bit is not acceptable). NOTE: Telnet does not support SSL encryption.
Figure 2. Chassis front panel Table 2. Chassis front panel — components Item Indicator, Button, or Connector 1 System identification button 2 Enclosure power-on indicator, power button 3 Diagnostic indicators 4 KVM select button 5 Compute sled 6 Video connector 7 USB connector 8 Storage sled Supported remote access connections The following table lists the supported remote access connections. Table 3.
Connection Serial port Features • • Network interface for the iDRAC and I/O Modules (IOMs). Support for Telnet/SSH command console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands. • Support for serial console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands. Support for binary interchange for applications specifically designed to communicate with a binary protocol to a particular type of IOM.
Servers BIOS iDRAC Lifecycle Controller PowerEdge FM120 1.5 2.40.40.40 2.40.40.40 PowerEdge FC640 1.0.0 3.10.10.10 3.10.10.10 Supported Firmware Versions for Server Component Update The following table lists the supported firmware versions for server components when CMC PowerEdge FX2/FX2s firmware is updated from 1.4 to 2.0 version but the server components are not updated to the next version. Table 5.
Platforms Model FC430 FC630 FC830 FC640 5719 QP 1G Yes Yes Yes Yes 5720 DP 1G Yes No No Yes 57416 DP 10G No No No Yes 57414 DP 25G No No No Yes 57412 DP 10G No No No Yes BCOM QP 1G Yes Yes Yes Yes LightPulse LPE12002 FC8 HBA Yes Yes Yes Yes LightPulse LPe15002B-M8–D DP 8G Gen 5 Yes Yes Yes Yes LPe16002 Dual Port FC 16 HBA Yes Yes Yes Yes LightPulse LPE12000 FC 8 HBA No Yes Yes Yes LightPulse LPe 15000B-M8–D SP 8G Gen 5 No Yes Yes Yes LPE 16000 Sing
Platforms Model FC430 FC630 FC830 FC640 QLE2742 FC32 SFP+ HBA No Yes Yes Yes QLE2740 FC32 SP HBA No Yes Yes Yes QLE2692 FC16 DP HBA Yes Yes Yes Yes PCIE SF852P DP 10G Yes Yes Yes Yes INTEL OPA x16 LP No No Yes Yes Managing licenses The CMC features are available based on the license (CMC Express or CMC Enterprise) purchased. Only licensed features are available in the interfaces that allow you to configure or use CMC. For example, CMC web interface, RACADM, WS-MAN, and so on.
License operations Before you perform the license management tasks, make sure to acquire the licenses. For more information, see the Acquiring Licenses section and Overview and Feature Guide available at dell.com/support.
Feature Express Enterprise 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 FlexAddress Enablement No Yes One-to-many Server Firware Update No Yes One-to-many configuration for iDRAC
Other documents you may need To access the documents from the Dell Support site. Along with this Reference Guide, you can access the following guides available at dell.com/support/manuals. • The CMC FX2/FX2s Online Help provides information about using the web interface. To access the Online Help, click Help on the CMC web interface. • The Chassis Management Controller Version 2.
• a. Go to Dell.com/Support/Home. b. Click Choose from all products. c. From All products section, click Software & Security, and then click the required link from the following: – Enterprise Systems Management – Remote Enterprise Systems Management – Serviceability Tools – Dell Client Command Suite – Connections Client Systems Management d. • To view a document, click the required product version. Using search engines: – Type the name and version of the document in the search box.
2 Installing and setting up CMC This section provides information about how to install your CMC hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the tasks for configuring a CMC: • Set up initial access to CMC. • Access CMC through a network. • Add and configure CMC users. • Update CMC firmware. Installing CMC hardware The CMC is pre-installed on your chassis and hence no installation is required.
NOTE: Do not turn on the servers. 7. The default CMC network configuration is Static with the CMC IP address 192.168.0.120. If you want to change the network configuration to DHCP, connect a serial cable to serial port on the CMC. For more information on serial connection, refer to Serial interface/protocol setup in Using Remote Access Software From a Management Station section.
Table 9. Daisy-chained storage sleds 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.
Interface/ Protocol Description • Software flow control: No Remote RACADM CLI Remote RACADM is a client utility that runs on a management station. It uses the out-of-band network interface to run RACADM commands on the managed system and uses the HTTPs channel. The –r option runs the RACADM command over a network, it requires CMC IP, username and password.
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.
Uninstalling remote RACADM from a Linux management station 1. Log in as root to the system where you want to uninstall the management station features. 2. Run the following rpm query command to determine which version of the DRAC tools is installed: rpm -qa | grep mgmtst-racadm 3. Verify the package version to be uninstalled and uninstall the feature by using the rpm -e rpm -qa | grep mgmtstracadm command.
Downloading and updating CMC firmware To download the CMC firmware, see Downloading CMC Firmware. To update the CMC firmware, see Updating CMC Firmware. Setting chassis physical location and chassis name You can set the chassis location in a data center and the chassis name to identify the chassis on the network (default name is cmc“Service Tag”). For example, an SNMP query on the chassis name returns the name you configure.
When a compute sled is performing an identify action, the front LED of the connected storage sled also flashes the identify pattern. If a storage sled is in split-single mode and is connected to two compute nodes, it shall flash the identify pattern if either of the two compute nodes is performing an identify action. If you start an identify action using OMSS or iDRAC for a compute sled, drive or enclosure, the storage sled associated with them also performs the identify action.
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. On the Front Panel Configuration page, under the KVM Configuration section, for KVM Mapped option, select the desired server from the drop down list. 5. Click Apply.
3 Logging into CMC You can log in to CMC as a CMC local user, as a Microsoft Active Directory user, or as an LDAP user. You can also log in using Single 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.
3. Click Generate and move the mouse in the window as directed. After the key is created, you can modify the key comment field. You can also enter a passphrase to make the key secure. Ensure that you save the private key. 4. You have two options for using the public key: • Save the public key to a file to upload later. • Copy and paste the text from the Public key for pasting window when adding the account using the text option.
To log in as a local user, Active Directory user, or LDAP user. 1. In the Username field, type your user name: • CMC user name: NOTE: The CMC user name can contain only alphanumeric characters and certain special characters. The at (@) symbol and following special characters are not supported: – Forward slash (/) – Backward slash (/) – Semicolon (;) – Backward Quote (`) – Quotations (“) • Active Directory user name: \, / or @.
NOTE: If you changed the default HTTPS port number (port 80), access the CMC web page using :, where cmcname is the CMC host name for CMC, domain-name is the domain name, and port number is the HTTPS port number. 2. Insert the smart card and click Login. The PIN dialog box is displayed. 3. Type the PIN and click Submit. NOTE: If the smart card user is present in Active Directory, an Active Directory password is not required.
• Logging in: ssh service@ or ssh service@, where IP_address is the CMC IP address. • Sending RACADM commands: ssh service@ racadm getversion and ssh service@ racadm getsel When you log in using the service account, if a passphrase was set up when creating the public or private key pair, you may be prompted to enter that passphrase again. If the passphrase is used with the keys, client systems running Windows and Linux provide methods to automate the method.
4 Updating firmware You can update firmware for: • The CMC • Chassis infrastructure • I/O Module You can update firmware for the following server components: • BIOS • iDRAC7 • iDRAC8 • Lifecycle Controller • 32–bit diagnostics • Operating system Drivers Pack • Network Interface Controllers • RAID controllers Signed CMC firmware image The CMC firmware includes a signature. The CMC firmware performs a signature verification step to ensure the authenticity of the uploaded firmware.
• Chassis Overview → Server Overview → Server Component Update The Firmware Update page displays the current version of the firmware for each listed component and allows you to update the firmware to the latest version. If the chassis contains an earlier generation server, whose iDRAC is in recovery mode or if CMC detects that iDRAC has corrupted firmware, then the earlier generation iDRAC is also listed on the Firmware Update page.
connection speed. When the internal update process begins, the page automatically refreshes and the Firmware update timer is displayed. For more information about the various firmware status, see Online Help. 5. For the CMC, during the final phases of the firmware update process, the browser session and connection with CMC is lost temporarily because the CMC is not connected to the network. You must log in after a few minutes, when the CMC has restarted.
• Chassis Overview → Update. 2. • Chassis Overview → Chassis Controller → Update. On the Firmware Update page, in the Chassis Infrastructure Firmware section, in the Update Targets column, select the option, and then click Apply Chassis Infrastructure Firmware. 3. On the Firmware Update page, click Browse, and then select the appropriate chassis infrastructure firmware. 4. Click Begin Firmware Update, and then click Yes.
Updating server component firmware The one-to-many update feature in CMC enables you to update server component firmware across multiple servers. You can update the server components using the Dell Update Packages available on the 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.
NOTE: The Single Click all blade update method has the following benefits: • Enables you to update all the components on all the blade servers with minimal clicks. • All the updates are packaged in a directory. This avoids individual upload of each component’s firmware. • Faster and consistent method of updating the server components.
Enabling Lifecycle Controller You can enable the Lifecycle Controller service when turning on a server: • For iDRAC servers, on the boot console, to access System Setup, press the key. • On the System Setup Main Menu page, go to iDRAC Settings → Lifecycle Controller, click Enabled. Go to the System Setup Main Menu page and click Finish to save the settings. • Cancelling System Services enables you to cancel all scheduled jobs that are pending and remove them from the queue.
• Automatic filtering is important for firmware updates of Network Interface Controllers (NIC) and RAID Controllers. These device categories have different types and models. Similarly, the firmware update images (DUP) may be available in optimized forms, where a single DUP may be programmed to update multiple types or models of devices of a given category.
Field Description 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 job status is continuously updated dynamically.
• 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.
5. Click Reinstall. The firmware version is reinstalled for the selected component or device. Rolling back server component firmware You can install the firmware image of the previously installed firmware for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller for a rollback operation. The availability is subject to the version compatibility logic of the Lifecycle Controller.
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.
The Component/Device Firmware Inventory section displays the current firmware versions of the components and devices across all the servers present in the chassis and firmware versions of the DUPs available in the Network Share. NOTE: Click Collapse against a slot to collapse the component and device firmware details for the specific slot. Alternatively, to view all the details again, click Expand. 6.
5 Viewing chassis information and monitoring chassis and component health You can view information and monitor the health of the following: • CMC • All severs and individual servers • IO Modules • Fans • Power Supply Units (PSUs) • Temperature sensors • PCIe devices • Storage sleds 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.
The following table lists the component properties and information displayed on the Chassis Health page in web interface. NOTE: In Multi-Chassis Management (MCM), all the Quick Links associated with the servers are not displayed. Table 13.
Component Fans IOM Slot Health and Performance Properties Properties • Power Status Quick Links • Speed • Warning Threshold • Fans Status • PWM (% of Max) • Critical Threshold • Fan Configuration • Fan Offset • Power State • Model • Role • Service Tag IOM Status Viewing server model name and Service Tag You can view the model name and Service Tag of each server instantly using the following steps: 1.
Viewing information and health status of storage sleds To view the health status of storage sleds: In the left pane, click Chassis Overview → Server Overview, and select the storage sled. The Storage Array Status page displays the storage sled properties and the list of storage nodes connected to the compute sled. For more information, see Online Help. 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.
over the fan sub-graphic. The text hint provides additional information about a fan. Click the fan sub-graphic to view the fan information in the right pane. 2. Go to Chassis Overview → Fans. The Fans Status page provides the status, speed measurements in revolutions per minute (RPMs), and threshold values of the fans in the chassis. There can be one or more fans. NOTE: In the event of a communication failure between CMC and the fan unit, CMC cannot obtain or display the health status for the fan unit.
On the Status page, under the KVM Properties section, you can view the status and properties of a KVM associated with the chassis. For more information, see the Online Help. Viewing information and health status of temperature sensors To view the health status of the temperature sensors: In the left pane, click Chassis Overview → Temperature Sensors. The Temperature Sensors Status page displays the status and readings of the temperature probes on the entire chassis (chassis and servers).
6 Configuring CMC Chassis Management Controller enables you to configure properties, set up users, and alerts to perform remote management tasks. Before you begin configuring the CMC, you must first configure the CMC network settings to allow CMC to be managed remotely. This initial configuration assigns the TCP/IP networking parameters that enable access to the CMC. You can configure CMC using Web interface or Setting up Initial Access to CMC RACADM.
Setting static DNS IP addresses NOTE: The static DNS IP addresses settings are not valid unless the DCHP for DNS address feature is disabled.
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. To disable only CMC network access, disable both CMC IPv4 and CMC IPv6. NOTE: The CMC NIC is enabled by default.
NOTE: If a DNS Domain name is not specified then the maximum number of characters is 63. If a domain name is specified then the number of characters in CMC name plus the number of characters in the DNS Domain Name must be less than or equal to 63 characters. • DNS Domain Name — The default DNS domain name is a single blank character. To set a DNS domain name, type: racadm config -g cfgLanNetworking -o cfgDNSDomainName where < name > is a string of up to 254 alphanumeric characters and hyphens.
Configuring Management Port 2 using RACADM To specify Redundant operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 1 command. To specify Stacking operation, use racadm config –g cfgNetTuning –o cfgNetTuningNicRedundant 0 command. By default, the Management Port 2 is set for Stacking.
Enabling FIPS Mode Using RACADM To enable FIPS mode, run the following command: racadm config –g cfgRacTuning –o cfgRacTuneFipsModeEnable 1 . Disabling FIPS Mode To disable FIPS mode, reset CMC to the default factory settings. Configuring services You can configure and enable the following services on CMC: • CMC serial console — Enable access to CMC using the serial console. • Web Server — Enable access to CMC web interface. Disabling the web server also disables Remote RACADM.
For more information about these objects, see the Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals. If the firmware on the server does not support a feature, configuring a property related to that feature displays an error. For example, using RACADM to enable remote syslog on an unsupported iDRAC displays an error message.
4. Type the group name in the Group Name field, and then click Apply. NOTE: The same rules that apply for a domain name apply to the group name. When the chassis group is created, the GUI automatically switches to the Chassis Group page. The left pane indicates the group by the group name and the lead chassis, and the unpopulated member chassis appear in the left pane. NOTE: When the chassis group is created, the Chassis Overview item in the tree structure is replaced with the name of the lead chassis.
If a network issue prevents contact between the leader and the member, the member chassis may not receive the message. In this case, disable the member from the member chassis to complete the removal process. Disabling an individual Member at the Member chassis Sometimes a member cannot be removed from a group by the lead chassis. This can happen if network connectivity to the member is lost. To remove a member from a group at the member chassis: 1.
If On-Change Propagation is selected, the member chassis take on the properties of the leader. If Manual Propagation is selected, click Propagate whenever you want to propagate the chosen settings to member chassis. For more information on propagation of leader chassis properties to member chassis, see the Online Help. 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.
• Save the current chassis configuration settings to an XML file on the network share or local management station. • Restore the chassis configuration. • Import chassis profiles (XML files) to the network share from a local management station. • Export chassis profiles (XML files) from the network share to a local management station. • Apply, edit, delete, or export a copy of the profiles stored on the network share.
NOTE: If you change the FIPS mode in the chassis configuration profile, the DefaultCredentialMitigation is enabled. Viewing Stored Chassis Configuration Profiles To view the chassis configuration profiles stored on the network share, go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles → Stored Profiles section, select the profile and click View in the View Profile column. The View Settings page is displayed.
3. Click OK. Deleting Chassis Configuration Profiles You can delete a chassis configuration profile that is stored on the network share. To delete a chassis configuration profile, perform the following tasks: 1. Go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles → Stored Profiles section, select the required profile and then click Delete Profile. A warning message is displayed indicating that deleting a profile would delete the selected profile permanently. 2.
You can import chassis configuration profiles from network share through remote RACADM interface. 1. To import the chassis configuration profiles from CIFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml –l // xx.xx.xx.xx/PATH –u USERNAME –p PASSWORD 2. To import the chassis configuration profiles from NFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml –l xx.xx.xx.
3. Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database. 4. Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5. Reset the target CMC that was configured. At the command prompt, type: racadm reset The getconfig -f myfile.cfg subcommand requests the CMC configuration for the CMC and generates the myfile.cfg file.
NOTE: A NULL string (identified by two " characters) directs the CMC to delete the index for the specified group. To view the contents of an indexed group, run the following command: racadm getconfig -g -i • For indexed groups the object anchor must be the first object after the [ ] pair.
7 Configuring servers You can configure the following settings of a server: • Slot Names • iDRAC Network Settings • DRAC VLAN Tag Settings • First Boot Device • Server FlexAddress • Remote File Share • BIOS Settings Using Server Clone 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).
For more information about the OMSA agent, see the Dell OpenManage Server Administrator User's Guide available at dell.com/support/manuals. 4. To use the iDRAC DNS name as slot name, select Use iDRAC DNS Name for Slot Name option. This option replaces the static slot names with the respective iDRAC DNS names, if it is available. If iDRAC DNS names are not available, the default or edited slot names are displayed.
Setting Description Enable iDRAC IPMI over LAN Enables or disables the IPMI over LAN channel for each iDRAC present in the chassis. By default, this option is selected. Enable iDRAC IPv4 DHCP Enables or disables DHCP for each iDRAC present in the chassis. If this option is enabled, the fields QuickDeploy IP, QuickDeploy Subnet Mask, and QuickDeploy Gateway are disabled, and cannot be modified since DHCP is used to automatically assign these settings for each iDRAC.
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: Figure 3. Two full-width sleds in the chassis • Four half-width sleds in the chassis: Figure 4. 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. Figure 5.
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.
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.
Boot Device Description Remote File Share Boot from remote file share. BIOS Boot Manager Boot using the BIOS boot manager. Lifecycle Controller Boot using the Lifecycle controller. Local Floppy Boot from a floppy disk in the local floppy disk drive. Setting first boot device for multiple servers using CMC web interface NOTE: To set the first boot device for servers, you must have the Server Administrator privileges or Chassis Configuration Administrator privileges, and the iDRAC login privileges.
• Isolated networks: Uplink configuration where each node’s LOM1 is mapped to IOM A1 and LOM2 is mapped to IOM A2. • Enhanced Network Adapter Isolation: Uplink configuration for enhanced security in multi-tenant configurations. This configuration isolates the individual network adapters with a dedicated IOM port mapped to the LOM of each node. Only the LOM1 on each node is operational. NOTE: While downgrading from CMC version 1.
The server cloning feature supports iDRAC7 and iDRAC8 Servers. Earlier generation RAC servers are listed, but are greyed out on the main page, and are not enabled to use this feature. To use the server configurations replication feature: • iDRAC must have the minimum version that is required. iDRAC7 servers require version 1.57.57. iDRAC8 servers require version 2.05.05. • Server must be turned on. You can: • View profile settings on a server or from a saved profile. • Save a profile from a server.
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.
For more information, see the Online Help. Exporting profile You can export a stored server profile to a specified path on a management station. To export a stored profile: 1. Go to the Server Profiles page. In the Stored Profiles section, select the required profile, and then click Export Copy of Profile. A File Download message is displayed prompting you to open or save the file. 2. Click Save or Open to export the profile to the required location.
To enable CSIOR, after rebooting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes. To enable CSIOR on: 1. 12th generation servers — After rebooting the server, from the F2 setup, select iDRAC Settings → Lifecycle Controller, enable CSIOR and save the changes. 2. 13th generation servers —After rebooting the server, when prompted, press F10 to access Lifecycle Controller.
NOTE: 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 then Server Profile. Selecting this option allows you to apply the server profile assigned when a new server is inserted in the chassis. 2. From the drop-down menu, select the profile to assign to the required slot. You can select profiles to apply to multiple slots. 3. Click Assign Profile. The profile gets applied to the selected slots.
– Boot the server with the new Boot Identity settings to quickly recover the workload. Saving Boot Identity Profiles You can save boot identity profiles in the CMC network share. Number of profiles that you can store depends on the availability of MAC addresses. For more information, see Configuring Network Share Using CMC Web Interface. For Emulex Fibre Channel (FC) cards, the Enable/Disable Boot From SAN attribute in the Option ROM is disabled by default.
NOTE: To perform server configuration replication operations on the server, 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 server. To complete the server configuration replication operation, enable the CSIOR option on the server. 4. Click OK to apply the boot identity profile to the selected server. The selected profile is applied to the server and the server is rebooted immediately.
To delete a stored profile, perform the following tasks:: 1. Go to the Server Profiles page. In the Boot Identity Profiles → Stored Profiles section, select the required profile, and then click Delete Profile. A warning message is displayed indicating that deleting a profile would delete the selected profile permanently. 2. Click OK to delete the selected profile. For more information, see the CMC Online Help.
For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help. Removing MAC Addresses You can remove a range of MAC addresses from the network share by using the Remove MAC Addresses option available in the CMC web interface. NOTE: You cannot remove MAC addresses if they are active on the node or are assigned to a profile. To remove MAC addresses from the network share: 1. Go to the Server Profiles page.
In MCM, while launching the iDRAC web interface from a member chassis, the user credentials of the leader and member chassis must be the same. Else, the current member chassis session is aborted and the member chassis login page is displayed. 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.
8 Configuring storage sleds Half-width storage sleds that are used in the FX2s chassis contain the following: • One or two RAID controllers • Maximum of 16 disk drives You can configure individual storage sleds containing two RAID controllers to operate in the following modes: • Split-single • Split-dual • Joined NOTE: Do not insert a storage sled in slot 1 of the chassis as it is not a valid location for storage sleds. NOTE: This section is applicable only to dual-controller storage modules.
3. Under Components, select one of the following options: • Split Dual Host • Split Single Host • Joined NOTE: Power off the compute sled before configuring the storage sled. Click Server Power Control at the top of the page to power off the compute sled. For more information, see the Online Help. 4. Click Apply. Configuring storage sleds using RACADM You can connect storage sleds with compute sleds using the config or getconfig RACADM command with the cfgStorageModule option.
9 Configuring CMC to send alerts You can set alerts and actions for certain events that occur on the chassis. An event occurs when the status of a system component is greater than the pre-defined condition. If an event matches an event filter and you have configured this filter to generate an alert message (email alert or SNMP trap), then an alert is sent to one or more configured destinations such as email address, IP address, or an external server. To configure CMC to send alerts: 1.
NOTE: For more information on configuring SNMP protocol and trap format, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. Configuring SNMP Trap Alert Destinations Using CMC Web Interface To configure IPv4 or IPv6 alert destination settings using CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Alerts → Trap Settings. The Chassis Event Alert Destinations page is displayed. 2.
NOTE: The commands in steps 2–5 overwrites any existing settings configured for the index specified (1–4). To determine whether an index has previously configured values, type: racadm getconfig -g cfgTraps -i . If the index is configured, values appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName objects. 6. To test an event trap for an alert destination, type: racadm testtrap -i where is a value 1–4 representing the alert destination you want to test.
where is the name of the person or group receiving the email alert, and is the index value specified in step 4 and step 5. The email name can contain up to 32 alphanumeric characters, dashes, underscores, and periods. Spaces are not valid. 6. Setup the SMTP host: racadm config -g cfgRemoteHosts -o cfgRhostsSmtpServerIpAddr host.domain where host.domain is the FQDN. You can configure up to four destination email addresses to receive email alerts.
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 User Configuration Administrator User can: Clear Logs Administrator User can clear the hardware log and CMC log. Chassis Control Administrator (Power Commands) CMC users with the Chassis Power Administrator privilege can perform all power-related operations. They can control chassis power operations, including power on, power off, and power cycle.
Privilege Description Test Alert User User can send test alert messages. Debug Command Administrator User can execute system diagnostic commands. Fabric A Administrator User can set and configure the Fabric A IOM. The CMC user groups provide a series of user groups that have pre-assigned user privileges. NOTE: If you select Administrator, Power User, or Guest User, and then add or remove a privilege from the pre-defined set, the CMC Group automatically changes to Custom. Table 18.
Privilege Set Administrator Permissions Power User Permissions Guest User Permissions Clear Logs Administrator Yes Yes No Chassis Control Administrator (Power commands) Yes Yes No Server Administrator Yes Yes No Test Alert User Yes Yes No Debug Command Administrator Yes No No 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.
NOTE: Users can be enabled and disabled over time, and disabling a user does not delete the user from the database. To verify if a user exists, open a Telnet/SSH text console to the CMC, log in, and then type the following command once for each index of 1–16: racadm getconfig -g cfgUserAdmin -i NOTE: You can also type racadm getconfig -f and view or edit the myfile.cfg file, which includes all the CMC configuration parameters.
Role Group Default Privilege Level Permissions Granted • • • • • • • User Configuration Administrator Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator • • • • • • CMC Login User Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Fabric A Administrator Bit Mask 2 None 0x00000ed9 3 None CMC Login User 0x00000001 4 None No assig
A CMC administrator can now integrate the LDAP server user logins with CMC. This integration requires configuration on both LDAP server and CMC. On the LDAP server, a standard group object is used as a role group. A user who has CMC access becomes a member of the role group. Privileges are still stored on CMC for authorization similar to the working of the Standard Schema setup with Active Directory support.
Configuring generic LDAP directory service using RACADM To configure the LDAP directory service, use the objects in cfgLdap and cfgLdapRoleGroup RACADM groups. There are many options to configure LDAP logins. In most of the cases, some options can be used with their default settings. NOTE: It is highly recommended to use the racadm testfeature -f LDAP command to test the LDAP settings for first time setups. This feature supports both IPv4 and IPv6.
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.
Prerequisites for Single Sign-On or Smart Card login The pre-requisites to configure SSO or Smart Card logins are: • Setup the Kerberos realm and Key Distribution Center (KDC) for Active Directory (ksetup). • A robust NTP and DNS infrastructure to avoid issues with clock drift and reverse lookup. • Configure CMC with Active Directory standard schema role group with authorized members.
4. In the Proxy server section, select the Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections) option, and then click Advanced. 5. In the Exceptions section, add the addresses for CMCs and iDRACs on the management network to the semicolon-separated list. You can use DNS names and wildcards in your entries. Mozilla Firefox To edit the exception list in Mozilla Firefox version 19.0: 1. Start Mozilla Firefox. 2.
A command success indicates that CMC is able to acquire Kerberos credentials and access the user's Active Directory account. If the command is not successful, resolve the error and run the command again. For more information, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide on dell.com/support/manuals.
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.
NOTE: CMC does not support SSH version 1. When an error occurs during the CMC login, the SSH client issues an error message. The message text is dependent on the client and is not controlled by CMC. Review the RACLog messages to determine the cause of the failure. NOTE: OpenSSH must be run from a VT100 or ANSI terminal emulator on Windows. You can also run OpenSSH using Putty.exe.
When using the public key comment section of the public key, remember that only the first 16 characters are utilized by the CMC. The public key comment is used by the CMC to distinguish SSH users when using the RACADM getssninfo command, because all the PKA users use the service username to log in. For example, if two public keys are set up one with comment PC1 and one with comment PC2: racadm getssninfo Type User IP Address Date/Time SSH PC1 x.x.x.x 09:00:00 SSH PC2 x.x.x.
NOTE: The connect command provides the –b (binary) option. The –b option passes raw binary data, and cfgSerialConsoleQuitKey is not used. Additionally, when connecting to a server using the CMC serial console, transitions in the DTR signal (for example, if the serial cable is removed to connect a debugger) will not result in you exiting the application. NOTE: If the IOM does not support console redirection, the connect command displays an empty console.
5. Save the changes and exit. The managed system restarts. Configuring Windows for serial console redirection There is no configuration necessary for servers running the Microsoft Windows Server versions, starting with Windows Server 2003. Windows receives information from the BIOS, and enable the Special Administration Console (SAC) console one COM1. Configuring Linux for server serial console redirection during boot The following steps are specific to the Linux GRand Unified Bootloader (GRUB).
The example shows console=ttyS1,57600 added to only the first option. Configuring Linux for server serial console redirection after boot Edit the /etc/inittab file as follows: Add a new line to configure agetty on the COM2 serial port: co:2345:respawn:/sbin/agetty -h -L 57600 ttyS1 ansi The following example shows the file with the new line. # # inittab This file describes how the INIT process # should set up the system in a certain # run-level.
# xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon Edit the /etc/securettyfile as follows: Add a new line, with the name of the serial tty for COM2: ttyS1 The following example shows a sample file with the new line. vc/1 vc/2 vc/3 vc/4 vc/5 vc/6 vc/7 vc/8 vc/9 vc/10 vc/11 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 ttyS1 Managing CMC using iDRAC RACADM proxy CMC can be managed using iDRAC RACADM proxy when CMC is not on the network.
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.
Verifying FlexAddress activation To view the FlexAddress feature activation status, run the following RACADM command: racadm featurecard -s Feature Name = FlexAddress Date/time Activated = 05 Oct 2013 - 11:50:49 Feature installed from SD-card serial number = CN0H871T1374036T00MXA00 Feature Name = FlexAddressPlus Date/time Activated = 05 Oct 2013 - 11:50:49 Feature installed from SD-card serial number = CN0H871T1374036T00MXA00 Feature Name = ExtendedStorage Current Status = redundant, active Date/time Activa
Deactivating FlexAddress The FlexAddress feature can be deactivated and the SD card returned to a pre-installation state by using a RACADM command. There is no deactivation function within the Web interface. Deactivation returns the SD card to its original state where it can be installed and activated in another chassis. The term FlexAddress, in this context, implies both FlexAddress and FlexAddressPlus.
Viewing World Wide Name or Media Access Control IDs The WWN/MAC Summary page allows you to view the World Wide Name (WWN) configuration and Media Access Control (MAC) address of a slot in the chassis. Command messages The following table lists the RACADM commands and output for common FlexAddress situations. Table 26. FlexAddress commands and output Situation Command Output SD card in the CMC module is bound to another 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.
A portion of this CD may contain open source software, which you can use under the terms and conditions of the specific license under which the open source software is distributed. THIS OPEN SOURCE SOFTWARE IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT IS PROVIDED "AS IS" WITHOUT ANY EXPRESSED OR IMPLIED WARRANTY; INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
• Basic Mode — In this mode you can view Server Slot, Fabric, Protocol, WWN/MAC addresses, and Partition Status. Only Active MAC addresses are displayed in WWN/MAC address field. You can filter using any or all of the fields displayed. • Advanced Mode — In this mode you can view all the fields displayed in the basic mode and all the MAC types (Server Assigned, Flex Address, and IO Identity). You can filter using any or all of the fields displayed.
4. Click the against a slot or click Expand/Collapse All to expand or collapse the attributes listed for a specific slot or all the slots in the WWN/MAC Addresses table. 5. From the Server Slot drop-down menu, select All Servers or a specific Slot to view the WWN/MAC Addresses attributes for all servers or servers in specific slots only respectively. 6.
For more information on the getflexaddr and getmacaddress subcommand, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.
14 Managing Fabrics The chassis supports two fabric types: Fabric A1 and Fabric A2, which are used by the two I/O Modules, and are always connected to the on-board Ethernet adapters of the servers. NOTE: In the PowerEdge FX2s chassis, fabrics B and C are the PCIe connection to the PCIe Extension cards. Following IO Modules are supported: • 1GbE pass-through • 10GbE pass-through • I/O Aggregator Both the Fabrics support only Ethernet.
NOTE: The length of the SNMP community string can be in the ASCII value range of 33–125 characters. 3. Click Apply. The network settings are configured for the IOM. NOTE: If allowed, you can reset the VLANs, network properties, and IO ports to its default configuration values. Configuring network settings for IOM using RACADM To configure the network settings for an IOM by using RACADM, set the date and time.
To reset the selected IOMs to factory default settings using the CMC Web interface: 1. In the system tree, go to I/O Module Overview and click Setup or expand I/O Module Overview in the system tree, select the IOM, and click Setup. The Deploy I/O Modules page displays the IOM(s) that are powered on. 2. For the required IOM(s), click Reset. A warning message is displayed. 3. Click OK to continue.
Launching IOA/MXL GUI from the I/O Module Overview page In the directory tree, go to I/O Module Overview. On the I/O Module Status page, click Launch I/O Module GUI. The IOA/MXL login page is displayed. Launching IOA/MXL GUI from the I/O Module Status page In the directory tree, under the I/O Module Overview, click an IOA/MXL switch. On the I/O Module Status page, click Launch I/O Module GUI. The IOA/MXL login page is displayed.
15 Using VLAN Manager You can assign or view the VLAN settings on the IOMs by using the VLAN Manager option. NOTE: This feature is supported only on Dell PowerEdge I/O Aggregator. After the mode of the I/O Aggregator is changed to standalone from stacking, remove the startup configuration and reload the I/O Aggregator. You need not save the system configuration while reloading the I/O Aggregator.
The network settings are configured for the IOM(s). Viewing the VLAN settings on IOMs using CMC web interface To view the VLAN settings on IOM(s) using the CMC Web interface: 1. Go to I/O Module Overview, and click Setup → VLAN Manager. The VLAN Manager page is displayed. The Summary VLANs of All Ports section displays information about the current VLAN settings for the IOMs. 2. Click Save to save the VLAN settings to a file.
An Operation Successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field. Resetting VLANs for IOMs using CMC web interface To reset VLANs for IOM(s) to default configurations using the CMC Web interface: 1. Go to I/O Module Overview, and click Setup → VLAN Manager. The VLAN Manager page is displayed. 2. In the Select I/O Module section, select the required IOMs. 3.
16 Managing and monitoring power The PowerEdge FX2/FX2s chassis is the most power-efficient server enclosure. It is designed to include highly efficient power supplies and fans, has an optimized layout for the air to flow more easily through the system, and contains power-optimized components throughout the enclosure.
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. These failures may originate in the AC power grid, the cabling and delivery, or a Power Supply Unit (PSU) itself. When you configure a system for Grid Redundancy, connect PSUs 1 and 2 to separate power grids.
NOTE: If the Maximum Power Conversation Mode (MPCM) is enabled on the chassis, all power requests from a blade server are denied. The blade server is not powered on if there is any action in the iDRAC or blade server requiring the host to start the power cycle. Viewing power consumption status CMC provides the actual input power consumption for the entire system. Viewing power consumption status using CMC web interface In the left pane, click Chassis Overview → Power → Power Monitoring.
Power supply and Redundancy policy changes in system event log Changes in the power supply state and power redundancy policy are recorded as events. Events related to the power supply that record entries in the system event log (SEL) are power supply insertion and removal, power supply input insertion and removal, and power supply output assertion and de-assertion. The following table lists the SEL entries that are related to power supply changes: Table 27.
3. • Redundancy Policy • Disable Chassis Power Button • Max Power Conservation Mode Click Apply to save the changes. Configuring power budget and Redundancy using RACADM NOTE: To perform power management actions, you must have the Chassis Configuration Administrator privilege. To enable and set the redundancy policy: 1. Open a serial/Telnet/SSH text console to CMC and log in. 2.
The power remote logging feature is dependent on previously configured remote syslog hosts having been . Logging to one or more remote syslog hosts must be enabled, otherwise power consumption is logged. This can be done either through the web GUI or the RACADM CLI. For more information, see the remote syslog configuration instructions.
• Reset Server (warm boot) • Power Cycle Server (cold boot) For information about the options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3. Click Apply. A dialog box appears requesting for confirmation. 4. Click OK to perform the power management action (for example, reset the server). Executing Power Control Operations on the IOM You can remotely reset or turn on an IOM. NOTE: To perform power management actions, you must have the Chassis Control Administrator privilege.
17 Configuring PCIe slots The PowerEdge FX2/FX2s chassis optionally contain eight PCIe slots where each PCIe slot is assigned to a specific sled. By default, all PCIe slots are mapped. You can enable or disable the assignment of PCIe slots to the servers using the CMC web interface or RACADM commands. The following tables list the PCIe mapping for full-width, half-width, and quarter-width compute sleds. Table 29.
PCIe Slot Mapping for quarter-width sleds (PowerEdge FC430) PCIe slot-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. NOTE: The Agent-free monitoring feature is not available for the PCIe PERC and Network cards in the Chassis PCIe slots.
– PCIe slots mapped to FW sled-3 (PCIe slots 1 through 4) are reassigned to sled–1. Sled-1 now maps to PCIe slots 1 though 8. • PCIe reassignment in half-width (HW) FC630: – PCIe slots mapped to HW sled-3 (PCIe slots 5 and 6) are reassigned to sled-1. Sled-1 now maps to PCIe slots 5 through 8. – PCIe slots mapped to HW sled-4 (PCIe slots 1 and 2) are reassigned to sled-2. Sled-2 now maps to PCIe slots 1 through 4.
18 Troubleshooting and recovery This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC web interface. • Viewing chassis information. • Viewing the event logs. • Gathering configuration information, error status, and error logs. • Using the diagnostic console. • Managing power on a remote system. • Managing Lifecycle Controller jobs on a remote system. • Reset components.
Table 32.
– Resolution B: Check that the PSU is connected to the same voltage as the other PSUs. If CMC detects a PSU operating at a different voltage, the PSU is turned off and marked Failed. • Problem: Inserted a new server into the enclosure with sufficient power supplies, but the server does not power on. – Resolution A: Check for the system input power cap setting—it might be configured too low to allow any additional servers to be powered up.
To access the Diagnostic Console: 1. In the left pane, click Chassis Overview → Troubleshooting → Diagnostics. The Diagnostic Console page displays. 2. In the Command text box, type a command and click Submit. For information about the commands, see the Online Help. The diagnostic results page appears. Resetting Components You can reset the CMC, or to virtually reset servers making them to behave as if they were removed and reinserted.
You can also check the ntpd status by typing the following racadm command: racadm getractime –n If the ‘*’ is not displayed for one of the configured servers, the settings may not be configured correctly. The output of this command contains detailed NTP statistics that may be useful in debugging the problem. If you attempt to configure a Windows-based NTP server, it may help to increase the MaxDist parameter for ntpd.
Component LED Color, Blinking Pattern Status Turned off IOM (Common) IOM (Pass through) Fan PSU Blue, glowing steadily Server is selected on the KVM Blue, blinking User-enabled module identifier Amber, glowing steadily Not used 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 N
Component LED Color, Blinking Pattern Status PCI Blue, dark Turned On Blue, blinking PCI identification is in progress.
recover ping 192.168.0.100 recover fwupdate -g -a 192.168.0.100 NOTE: Connect the network cable to the left most RJ45. NOTE: In recover mode, you cannot ping CMC normally because there is no active network stack. The recover ping command allows you to ping to the TFTP server to verify the LAN connection. You may need to use the recover reset command after setniccfg on some systems. Troubleshooting Network Problems The internal CMC trace log allows you to debug CMC alerts and networking.
• Problem: Not able to import, export, or delete storage module licenses. Resolution: Chassis configuration privilege is required to import, export, and delete storage module licenses. Resetting Forgotten Administrator Password CAUTION: Many repairs may only be done by a certified service technician. Perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team.
Table 35. CMC Password Jumper Settings J_PWORD (default) The password reset feature is disabled. The password reset feature is enabled. 3. Slide the CMC module into the enclosure. Reattach any cables that were disconnected. NOTE: Make sure that the CMC module is active until the remaining steps are completed. 4. Wait for the CMC to finish rebooting. In the web interface, in the system tree, go to Chassis Overview and click Power → Control, select the Reset CMC (warm boot), and click Apply. 5.
19 Frequently asked questions 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.
To ensure that the CSR matches the registered DNS CMC name: 1. In the left pane, click Chassis Overview. 2. Click Network. The Network Configuration page appears. 3. Select the Register CMC on DNS option. 4. Type a CMC name in the DNS CMC Name field. 5. Click Apply Changes. Why are the remote RACADM and Web-based services unavailable after a property change? It may take a minute for the remote RACADM services and the web interface to become available after the CMC Web server resets.
Yes. The domain forest function level must be in Native mode or Windows 2003 mode. In addition, the groups among Association Object, RAC user objects, and RAC Device Objects (including Association Object) must be universal groups. Can these Dell-extended objects (Dell Association Object, Dell RAC Device, and Dell Privilege Object) be in different domains? The Association Object and the Privilege Object must be in the same domain.
