Dell Chassis Management Controller Version 2.0 for PowerEdge FX2 and FX2s User's Guide September 2017 Rev.
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 Chapter 1: Overview..................................................................................................................... 11 Key Features....................................................................................................................................................................... 12 What is new in this release........................................................................................................................................
Chapter 3: Logging into CMC...................................................................................................... 33 Configure public key authentication over SSH.......................................................................................................... 33 Generating public keys for systems running Windows.......................................................................................33 Generating public keys for systems running Linux.....................................
Configuring fans.......................................................................................................................................................... 55 Viewing front panel properties.......................................................................................................................................55 Viewing KVM information and health status..............................................................................................................
Modifying the CMC IP address................................................................................................................................ 73 Chapter 7: Configuring servers....................................................................................................75 Configuring slot names.................................................................................................................................................... 75 Configuring iDRAC network settings...........
Chapter 8: Configuring storage sleds.......................................................................................... 93 Configuring storage sleds in split-single mode...........................................................................................................93 Configuring storage sleds in split-dual mode..............................................................................................................93 Configuring storage sleds in joined mode.............................
Uploading Keytab file.......................................................................................................................................................110 Configuring CMC SSO login or Smart Card login for Active Directory users using RACADM...................... 110 Chapter 12: Configuring CMC to use Command Line consoles..................................................... 111 CMC Command Line console features.............................................................................
Viewing the current VLAN settings on IOMs using CMC web interface........................................................... 133 Removing VLANs for IOMs using CMC web interface...........................................................................................133 Updating untagged VLANs for IOMs using CMC web interface..........................................................................133 Resetting VLANs for IOMs using CMC web interface...........................................................
Chapter 19: Frequently asked questions.....................................................................................156 RACADM............................................................................................................................................................................156 Managing and recovering a remote system.............................................................................................................. 157 Active Directory.................................
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.
Key Features The CMC features are grouped into management and security features. 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.
○ 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. ● ● ● ● ● ● ● Configurable IP ports (if applicable).
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.
Table 3. Supported remote access connections (continued) Connection Features ● ● ● ● Serial port Redundant mode, but the cabling is daisy chained between chassis in the Stacking mode. Ensure that the cabling model matches the CMC setting for the intended usage. DHCP support. SNMP traps and e-mail event notification. 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.
Table 4. Latest Firmware Versions for BIOS, iDRAC, and Lifecycle Controller Servers BIOS iDRAC Lifecycle Controller PowerEdge FC830 2.2.5 2.40.40.40 2.40.40.40 PowerEdge FC630 2.2.5 2.40.40.40 2.40.40.40 PowerEdge FC430 2.2.5 2.40.40.40 2.40.40.40 PowerEdge FM120 1.5 2.40.40.40 2.40.40.40 PowerEdge FC640 1.0.0 3.10.10.10 3.10.10.
Table 5. Supported Server Component Versions for Server Component Update to N version Platform Server Component Previous Component Version (N-1 Updated Component Version (N Version) Version) Lifecycle Controller Not Applicable 3.10.10.10 Diagnostics Not Applicable 4301.13 (YFXV5) BIOS Not Applicable 1.0.0 Supported Network Adapters The following table lists the supported network adapters for PowerEdge FX2/FX2s. Table 6.
Table 6.
NOTE: Storage sled licenses are required to change the FD33xS and FD33xD RAID controllers from HBA mode to RAID mode. Types of licenses The types of licenses offered are: ● 30–day evaluation and extension — The license expires after 30 days that can be extended for 30 days. Evaluation licenses are duration-based, and the timer runs when power is applied to the system. These licenses are not applicable to storage sleds. ● Perpetual — The license is bound to the Service Tag and is permanent.
NOTE: For the Learn More option to display the correct page, make sure that *.dell.com is added to the list of Trusted Sites in the Security Settings. For more information, see the Internet Explorer help documentation. NOTE: If you try to install the PowerEdge FM120x4 license on PowerEdge FC630, the license installation fails. For more information on licensing refer Integrated Dell Remote Access Controller (iDRAC) User’s Guide .
License component state or condition and available operations The following table provides the list of license operations available based on the license state or condition. Table 8.
● The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy. ● Dell systems management application documentation provides information about installing and using the systems management software. The following system documents provide more information about the system in which CMC PowerEdge FX2/FX2s is installed: ● The safety instructions that came with your system provide important safety and regulatory information.
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.
You can also power on the chassis using the command line interface, use racadm chassisaction powerup command to accomplish it. NOTE: Do not turn on the servers. 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.
Table 10. CMC Interfaces Interface/ Protocol Description Telnet Provides command line access to CMC through the network. The RACADM command line interface and the connect command, which is used to connect to the serial console of a server or IO module, are available from the CMC command line. NOTE: Telnet is not a secure protocol and is disabled by default. Telnet transmits all data, including passwords in plain text.
● Docs — Contains documentation for systems, systems management software products, peripherals, and RAID controllers. ● SERVICE — Contains the tools required to configure your system, and delivers the latest diagnostics and Dell-optimized drivers for your system. For information about installing Dell OpenManage software components, see the Dell OpenManage Installation and Security User's Guide available at dell.com/support/manuals.
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 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. Setting chassis physical location and chassis name using web interface To set the chassis location and chassis name using the CMC web interface: 1.
NOTE: To modify these settings, you must have the Debug Administrator privilege on a CMC. 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.
Accessing a server using KVM To 1. 2. 3. 4. map a Server to KVM from web interface: Connect a monitor to the video connector and a keyboard to USB connector located on the front of the chassis. In the left pane, click Chassis Overview > Front Panel > Setup. On the Front Panel Configuration page, under the KVM Configuration section, select Enable KVM Mapping option.
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.
1. Start the application and select SSH-2 RSA 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. NOTE: ● 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. ● CMC accepts RSA keys up to key strength 4096, but the recommended key strength is 1024. 3. Click Generate and move the mouse in the window as directed.
Logging into CMC as a local user, active directory user, or LDAP user To log in to CMC, you must have a CMC account with the Log In to CMC privilege. The default root account is the default administrative account that ships with CMC. NOTE: For added security, it is recommended that you change the default password of the root account during initial setup. NOTE: When Certificate Validation is enabled, FQDN of the system should be provided.
● Configure the DNS server. ● Enable Active Directory login. ● Enable Smart Card login. To log in to CMC as an Active Directory user using a smart card: 1. Log in to CMC using the link https://. The CMC Login page is displayed asking you to insert a smart card. NOTE: If you changed the default HTTPS port number (port 80), access the CMC web page using
Logging into CMC using public key authentication You can log in to the CMC over SSH without typing a password. You can also send a single RACADM command as a command line argument to the SSH application. The command line options behave similar to the remote RACADM, because the session ends after the command is completed. Before logging in to CMC over SSH, make sure that the public keys are uploaded. To use this feature, you must have an Enterprise License.
4 Updating firmware You can update firmware for: ● The CMC ● Chassis infrastructure ● I/O Module You can update firmware for the following server components: ● BIOS ● iDRAC7 ● iDRAC8 ● Lifecycle Controller ● 32–bit diagnostics ● Operating system Drivers Pack ● Network Interface Controllers ● RAID controllers Topics: • • • • • • • Signed CMC firmware image Downloading CMC firmware Viewing currently installed firmware versions Updating the CMC firmware Updating the CMC using DUP Updating chassis infrastruct
Viewing currently installed firmware versions using CMC web interface In ● ● ● the CMC web interface, go to any of the following pages to view the current firmware versions: Chassis Overview > Update Chassis Overview > Chassis Controller > Update 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.
● Chassis Overview > Update ● Chassis Overview > Chassis Controller > Update 2. On the Firmware Update page, in the CMC Firmware section, select the required components under the Update Targets column for the CMC you want to update, and then click Apply CMC Update. 3. In the Firmware Image field, enter the path to the firmware image file on the management station or shared network, or click Browse to browse through to the file location. The default name of the CMC firmware image file is fx2_cmc.bin. 4.
Updating chassis infrastructure firmware The chassis infrastructure update operation updates the Main Board component. NOTE: Before you update the Chassis Infrastructure firmware, turn off all the servers in the chassis if required. Updating chassis infrastructure firmware using CMC web interface 1. Go to any of the following pages: ● Chassis Overview > Update. ● Chassis Overview > Chassis Controller > Update. 2.
You can also update server iDRAC firmware using Chassis Overview > Server Overview > Update. For more information, see Upgrading Server Component Firmware 2. To update the iDRAC7 or iDRAC8 firmware, in the iDRAC Enterprise Firmware section, click the Update link of the server for which you want to update the firmware. The Server Component Update page is displayed. To continue, see Updating Server Component Firmware.
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. ● Enables you to maintain a standard image with the required updates versions of the server components that can be used to update multiple servers in a single operation.
NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecycle Controller. 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.
Sometimes, a BIOS firmware update image may be compatible across a number of server models. Such optimizations are ignored in case this compatibility is no longer true in the future. ● Automatic filtering is important for firmware updates of Network Interface Controllers (NIC) and RAID Controllers. These device categories have different types and models.
Table 12. Component and Devices Information 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.
● 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. Lifecycle Controller job operations NOTE: To use this feature, you must have an Enterprise License.
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. It also assumes the previous update was facilitated by the Lifecycle Controller. NOTE: To use this feature, you must have an Enterprise License.
4. In the Update column, select the checkbox(es) for the component or device for which you want to update the firmware to the next version. Use the CRTL key shortcut to select a type of component or device for update across all the applicable servers. Pressing and holding the CRTL key highlights all the components in yellow. While the CRTL key is pressed down, select the required component or device by enabling the associated check box in the Update column.
2. In the Choose Update Type section, select Update from Network Share. For more information, see Choosing Server Component Firmware Update Type. 3. If the Network Share is not connected, configure the Network Share for the chassis. To configure or edit the network share details, in the Network Share Properties table click Edit. For more information see Configuring Network Share Using CMC Web Interface. 4.
5 Viewing chassis information and monitoring chassis and component health You can view information and monitor the health of the following: ● CMC ● All severs and individual servers ● IO Modules ● Fans ● Power Supply Units (PSUs) ● Temperature sensors ● PCIe devices ● Storage sleds Topics: • • • • • • • • • • Viewing Viewing Viewing Viewing Viewing Viewing Viewing Viewing Viewing Viewing chassis and component summaries chassis summary chassis controller information and status information and health statu
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. ● Properties — Displays the component properties that do not vary with time, or that change only infrequently.
Table 13.
The Chassis Controller Status page is displayed. For more information, see the CMC for Dell PowerEdge FX2/FX2s Online Help. Viewing information and health status of all servers To view the health status of all the servers, do one of the following: ● Click Chassis Overview. The Chassis Health page displays a graphical overview of all the servers installed in the chassis. Server health status is indicated by the overlay of the server subgraphic.
● A fan stops functioning. ● A fan is removed from the chassis. NOTE: During updates of CMC or iDRAC firmware on a server, some or all of the fan units in the chassis rotates at 100%. This is normal. To view the health status of fans, in the CMC Web interface, do any of the following: 1. Go to Chassis Overview. The Chassis Health page is displayed. The upper right section of chassis graphics provides the top left view of the chassis and contains the health status of the fans.
Viewing KVM information and health status To view the health status of the KVMs associated with the chassis, do any of the following: Click Chassis Overview > Front Panel. 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.
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.
You can enable the DHCP to obtain an IP address from the DHCP server automatically. 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.
3. Click Apply Changes for each section to apply the settings. Viewing CMC network LAN settings using RACADM To view IPv4 settings, use the object cfgCurrentLanNetworking with the following subcommands: ● getniccfg ● getconfig To view IPv6 settings, use the cfgIpv6LanNetworking with the getconfig subcommand. To view IPv4 and IPv6 addressing information for the chassis, use the getsysinfo subcommand.
For an IPv6 network, to disable the Autoconfiguration feature and specify a static CMC IPv6 address, gateway, and prefix length, type: racadm config -g cfgIPv6LanNetworking cfgIPv6AutoConfig 0 racadm config -g cfgIPv6LanNetworking cfgIPv6Address racadm config -g cfgIPv6LanNetworking cfgIPv6PrefixLength 64 racadm config -g cfgIPv6LanNetworking cfgIPv6Gateway -o -o -o -o Configuring IPv4 and IPv6 DNS settings ● CMC Registration — To register the CMC on the DNS server, type: rac
< speed > is 10 or 100 (default). Configuring Management Port 2 The second network port on the CMC can be used for daisy-chaining CMCs together for cable reduction, or as a redundant port for failover networking operation. Management Port 2 may be connected to the top-of-rack (TOR) switch or to another switch. There is no requirement that the two CMC NIC ports be connected to the same subnet.
● access control If any of the properties depend on cryptographic algorithms, then FIPS must approve these algorithms. By default, the FIPS mode is disabled. When FIPS is enabled, the minimum key size for OpenSSL FIPS is SSH-2 RSA 2048 bits. NOTE: PSU firmware update is not supported when the FIPS mode is enabled in the chassis. For more information, see CMC Online Help. The following features/applications support FIPS.
NOTE: When modifying CMC service port numbers for SSH, Telnet, HTTP, or HTTPS, avoid using commonly used ports by OS services such as port 111. See Internet Assigned Numbers Authority (IANA) reserved ports at http://www.iana.org/ assignments/service-names-port-numbers/service-names-port-numbers.xhtml. CMC includes a web server that is configured to use the industry-standard SSL security protocol to accept and transfer encrypted data from and to clients over the Internet.
● Repair active controller media ● Stop using flash media for storing chassis data For more information about these options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 3. Click Apply to apply the selected option. Setting up Chassis Group CMC enables you to monitor multiple chassis from a single lead chassis. When a chassis group is enabled, CMC in the lead chassis generates a graphical display of the status of the lead chassis and all member chassis within the chassis group.
NOTE: The credentials entered for a member are passed securely to the member chassis to establish a trust relationship between the member and lead chassis. The credentials are not persisted on either chassis, and are never exchanged again after the initial trust relationship is established. Removing a member from the leader You can remove a member from the group from the lead chassis. To remove a member: 1. Log in with chassis administrator privileges to the leader chassis. 2.
If you try logging in to the member chassis using Launch CMC when both the leader and chassis are FIPS enabled or disabled, you are directed to the Chassis Group Health page. Else, you are directed to the Login page of the member chassis. If a server in a chassis is the required destination: a. Select the image of the destination chassis. b. In the chassis image that is displayed in the Health section, select the server. c. In the box labeled Quick Links, select the destination device.
Table 14. Configuration Service Properties Property Navigation Chassis alerts In the left pane, click Chassis Overview, and then click Alerts. Server inventory for MCM group A group is a lead chassis that has 0 to 19 chassis group members. The Chassis Group Health page displays all the member chassis and allows you to save the server inventory report to a file, using standard browser download capability.
“, ., *, >, <, \, /, :, and | 2. Select one of the following profile types from the Profile Type option: ● Replace — Includes attributes of the entire CMC configuration except write-only attributes such as user passwords and service tags. This profile type is used as a backup configuration file to restore the complete chassis configuration including identity information such as IP addresses. ● Clone — Includes all the Replace type profile attributes.
Applying Chassis Configuration Profiles You can apply chassis configuration to the chassis if the chassis configuration profiles are available as stored profiles on the network share. To initiate a chassis configuration operation, you can apply a stored profile to a chassis. To apply a profile to a chassis, perform the following tasks: 1. Go to the Chassis Configuration Profiles page. In the Stored Profiles section, select the stored profile that you want to apply. 2. Click Apply Profile.
NOTE: By default, the export is done as clone type. You can use the –—clone to get the clone type profile in XML file. The import and export operation to and from the network share can be done through local RACADM as well as remote RACADM. Whereas, the import and export operation to and from the local management can be done only through remote RACADM interface. Exporting Chassis Configuration profiles You can export chassis configuration profiles to network share by using the get command. 1.
1. To export the chassis configuration profiles as clone.xml file, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml Parsing Rules You can manually edit properties of an exported XML file of chassis configuration profiles. An ● ● ● XML file contains the following properties: System Configuration, which is the parent node. component, which is the primary child node. Attributes, which contains name and value. You can edit these fields.
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. If required, you can rename the file or save it to a different location.
NOTE: You may create an indexed group manually using the following command: racadm config -g name> -o -i
The command racadm config -f .cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update. Use this file to download company-wide changes or to configure new systems over the network with the command, racadm getconfig -f .cfg. NOTE: Anchor is a reserved word and should not be used in the .cfg file.
7 Configuring servers You can configure the following settings of a server: ● Slot Names ● iDRAC Network Settings ● DRAC VLAN Tag Settings ● First Boot Device ● Server FlexAddress ● Remote File Share ● BIOS Settings Using Server Clone Topics: • • • • • • • • • Configuring slot names Configuring iDRAC network settings Setting first boot device Configuring sled network uplink Deploying remote file share Configuring server FlexAddress Configuring profile settings using server configuration replication Launch
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. This overrides the static slot names with the server’s Host Name (or system name), if available. This requires the OMSA agent to be installed on the server. For more information about the OMSA agent, see the Dell OpenManage Server Administrator User's Guide available at dell.com/support/manuals. 4.
Table 15. QuickDeploy settings 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. 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. Configuring iDRAC VLAN tag settings using RACADM ● Specify the VLAN ID and priority of a particular server with the following command: racadm setniccfg -m server- -v The valid values for are 1–4.
Table 16. Boot Devices Boot Device Description 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. 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.
For more information about these objects, see the Chassis Management Controller for PowerEdge FX2s RACADM Command Line Reference Guide available at dell.com/support/manuals. Configuring sled network uplink You can configure the Sled Network Uplink only on the PowerEdge FM120x4 sleds that contain an internal network switch.
Configuring profile settings using server configuration replication The server configurations replicating feature allows you to apply all profile settings from a specified server to one or more servers. Profile settings that can be replicated are those profile settings which can be modified and are intended to be replicated across servers. The following three profile groups for servers are displayed and can be replicated: ● BIOS — This group includes only the BIOS settings of a server.
Removing or disabling the non-volatile extended storage media prevents access to Stored Profiles, and disables the Server Cloning feature. To add a profile: 1. Go to the Server Profiles page. In the Server Profiles section, click Apply and Save Profiles. 2. Select the server from whose settings you want to generate the profile, and then click Save Profile. The Save Profile section is displayed. 3. Select Extended Storage or Network Share as the location to save the profile.
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.
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. NOTE: The CMC Server Configuration Replication feature retrieves and displays the settings for a specific server, only if the Collect System Inventory on Restart (CSIOR) option is enabled.
Assigning server profiles to slots The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots: 1. In the Server Profiles page, click Profiles for QuickDeploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Assign Profile column.
○ Clear the boot identity from the non-functioning server to avoid duplicating the MAC addresses in case the server recovers. ○ Apply the boot identity of a failed server to a spare standby server. ○ 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.
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.
Deleting Boot Identity Profiles You can delete a boot identity profile that is stored on the network share. 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.
4. Click OK to add MAC addresses. 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.
● the iDRAC network connection experiences a problem 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.
Configuring storage sleds using CMC web interface 1. In the left pane, click Chassis Overview > Server Overview and click a storage sled. The details of the storage sled are displayed. 2. In the menu on the right side, click Setup. The Storage Configuration page is displayed. You can also access the Storage Configuration page by selecting a storage sled on the Chassis Health page. Under Quick Links, click Storage Array Setup. 3.
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 1. 2. 3. 4.
Configuring SNMP trap alert destinations You can configure the IPv6 or IPv4 addresses to receive the SNMP traps. 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.
5. Specify the community name: racadm config -g cfgTraps -o cfgTrapsCommunityName -i where is the SNMP community to which the chassis belongs, and is the index value specified in steps 4 and 5. NOTE: CMC uses a default SNMP community string as public. To ensure higher security, it is recommended to change the default community string and set a value which is not blank. You can configure up to four destinations to receive traps alerts.
2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 3. Enable email alert generation: racadm config -g cfgEmailAlert -o cfgEmailAlertEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destination email addresses. 4.
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.
Table 17. User Types (continued) Privilege Description NOTE: CMC users with the Chassis Configuration Administrator privilege can configure power settings. However, the Chassis Control Administrator privilege is required to perform chassis power operations, including power on, power off, and power cycle. User Configuration Administrator User can: ● Add a new user. ● Change the password of a user. ● Change the privileges of a user.
Table 17. User Types Privilege Description ● Server Reboot Test Alert User User can send test alert messages. Debug Command Administrator User can execute system diagnostic commands. Fabric A Administrator User can set and configure the Fabric A IOM. The CMC user groups provide a series of user groups that have pre-assigned user privileges.
Table 19.
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.
Table 20.
Configuring generic LDAP users CMC provides a generic solution to support Lightweight Directory Access Protocol (LDAP)-based authentication. This feature does not require any schema extension on your directory services. 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.
7. Click Apply to save the role group settings, click Go Back To Configuration page, and then select Generic LDAP. 8. If you have selected Certificate Validation Enabled option, then in the Manage Certificates section, specify the CA certificate to validate the LDAP server certificate during SSL handshake and click Upload. The certificate is uploaded to CMC and the details are displayed. 9. Click Apply. The generic LDAP directory service is configured.
11 Configuring CMC for Single Sign-On or Smart Card login This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. SSO uses Kerberos as an authentication method allowing users, who have signed in as an automatic- or single sign-on to subsequent applications such as Exchange.
Client Systems ● For only Smart Card login, the client system must have the Microsoft Visual C++ 2005 redistributable. For more information see www.microsoft.com/downloads/details.aspx?FamilyID= 32BC1BEEA3F9-4C13-9C99-220B62A191EE&displaylang=en ● For Single Sign-On or smart card login, the client system must be a part of the Active Directory domain and Kerberos Realm. CMC ● Each CMC must have an Active Directory account. ● CMC must be a part of the Active Directory domain and Kerberos Realm.
For information about configuring CMC for Extended Schema Active Directory, see Extended Schema Active Directory Overview. Configuring browser for SSO login Single Sign-On (SSO) is supported on Internet Explorer versions 6.0 and later, and Firefox versions 3.0 and later. NOTE: The following instructions are applicable only if CMC uses Single Sign-On with Kerberos authentication. Internet Explorer To edit the exception list in Internet Explorer: 1. Start Internet Explorer. 2.
Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface To configure Active Directory SSO or smart card login for CMC: NOTE: For information about the options, see the CMC for Dell PowerEdge FX2/FX2s Online Help. 1. While configuring Active Directory to setup a user account, perform the following additional steps: ● Upload the keytab file. ● To enable SSO, select the Enable Single Sign-On option. ● To enable smart card login, select the Enable Smart-Card Login option.
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.
If your management station is running Microsoft Windows XP or Microsoft Windows Server 2003, you may experience an issue with the characters in a CMC Telnet session. This issue may occur as a frozen login where the return key does not respond and the password prompt does not appear. To fix this issue, download hotfix 824810 from support.microsoft.com. For more information, you can also see Microsoft Knowledge Base article 824810.
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. The service username is a special user account that can be used when accessing the CMC through SSH.
In a serial, Telnet, SSH console, CMC supports the connect command to establish a serial connection to a server or I/O module. The server serial console contains both the BIOS boot and setup screens, and the operating system serial console. For the I/O module, the switch serial console is available. There is a single IOM on the chassis. CAUTION: When run from the CMC serial console, the connect -b option stays connected until the CMC resets. This connection is a potential security risk.
● 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.
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.conf file, follow these guidelines: ● Disable GRUB's graphical interface and use the text-based interface. Else, the GRUB screen is not displayed in console redirection. To disable the graphical interface, comment out the line starting with splashimage.
System Shutting Down" # If power was restored before the shutdown kicked in, cancel it.
Table 24. CMC-iDRAC privileges mapping CMC Privilege iDRAC privilege required for proxy operation Server Administrator System Control Test Alert User System Operations Debug Command Administrator Debug Fabric x Administrator (where x is A, B, or C) System Control For more information, see the Dell Chassis Management Controller Version 2.0 for PowerEdge FX2/FX2s RACADM Command Line Reference Guide.
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.
range. The mac_count tag is the total number of MAC addresses that the SD card allocates. To determine the total MAC range allocated, use the following formula: + - 1 = For example: (starting_mac)00:18:8B:FF:DC:FA + (mac_count)0xCF – 1 = (ending_mac)00:18:8B:FF:DD:C8 NOTE: Lock the SD card prior to inserting in the USB Memory Card Reader to prevent accidently modifying any of the contents. You must unlock the SD card before inserting into CMC.
Table 25. Status Messages Returned by the featurecard -s Command Status Message Actions 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. To reactivate on the current chassis, enter racadm racreset until the CMC module with the feature card installed becomes active. Dell Feature Cards may contain more than one feature.
can select slots to be enabled. For example, if Fabric-A is enabled, any slots that are enabled have FlexAddress enabled only on Fabric-A. All other fabrics use the factory-assigned WWN/MAC on the server. NOTE: When the FlexAddress feature is deployed for the first time on a given server module, it requires a power- down and power-up sequence for FlexAddress to take effect. FlexAddress on Ethernet devices is programmed by the server module BIOS.
Table 26. FlexAddress commands and output Situation Command Output Deactivating FlexAddress feature with chassis powered ON. $racadm feature -d -c flexaddress ERROR: Unable to deactivate the feature because the chassis is powered ON Guest user tries to deactivate the feature on the chassis. $racadm feature -d -c flexaddress ERROR: Insufficient user privileges to perform operation Changing the slot/fabric FlexAddress settings while the server modules are powered ON.
ninety (90) days from the date you receive the Software. Some jurisdictions do not allow limits on the duration of an implied warranty, so this limitation may not apply to you. The entire liability of Dell and its suppliers, and your exclusive remedy, shall be (a) return of the price paid for the Software or (b) replacement of any disk not meeting this warranty that is sent with a return authorization number to Dell, at your cost and risk.
○ iDRAC management controller is considered as part of Management Fabric and is shown along with rest of Fabrics. ○ A check mark against the component indicates that the fabric is enabled for FlexAddress or FlexAddressPlus. ● Protocol that is being used on the NIC Adapter port. For example, LAN, iSCSI, FCoE, and so on. ● Fibre Channel World Wide Name (WWN) configuration and Media Access Control (MAC) addresses of a slot in the chassis.
Viewing advanced WWN or MAC address information using web interface To view WWN/MAC Address Information for each server slot or all servers in a chassis, in the advanced mode: 1. Click Server Overview > Properties > WWN/MAC 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.
To display the iSCSI MAC addresses for all servers, use the following RACADM command: racadm getmacaddress -t iscsi 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
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.
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. If allowed, type the root password, SNMP RO Community string, and Syslog Server IP Address for the IOM.
The FCoE I/O Module page specific to the IOM slot is displayed. 3. In the Select Port drop-down, select the required port number for the selected IOM and click Show Sessions. The selected option retrieves the FCoE session information for the switch, and present it to the user as a table. The FCoE Session Information section displays the FCoE session information for the switch. NOTE: The I/O Aggregator also displays the active FCoE sessions when the switch is using the protocol.
You can launch the MXL/IOA GUI from the Chassis Overview, I/O Module Overview, and I/O Module Status pages. NOTE: While logging in to the MXL application for the first time, you are prompted to customize the password. Launching IOA/MXL GUI from the Chassis Overview page Go to the Chassis Overview > Quick Links > Launch I/O Module GUI. The IOA/MXL login page is displayed. Launching IOA/MXL GUI from the I/O Module Overview page In the directory tree, go to I/O Module Overview.
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.
● Reset to all VLANs ● Show VLANs 7. 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. The network settings are configured for the IOM(s).
2. In the Select I/O Module section, select the required IOMs. 3. In the Specify Port Range section, select the range of fabric ports to be assigned to the selected IOM(s). 4. Select the Select or Deselect All option to apply the changes to all or no IOMs. or Select the check box against the specific slots to select the required IOMs. 5. In the Edit VLANs section, select Update the Untagged VLANs in the drop down list and click Apply.
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: The lower bound is the minimum power needed to operate the chassis given the current configuration. The upper bound reflects the maximum power available in the current redundancy policy. 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.
the redundancy status is No, and the overall power health is Critical. This is because the system is not able to operate in accordance with the configured redundancy policy. NOTE: CMC does not perform a pre-check of these conditions when you change the redundancy policy to or from grid redundancy. So, configuring the redundancy policy may immediately result in redundancy lost or a regained condition.
Power conservation and power budget If the power usage exceeds the System Input Power Cap, the power supplied to the servers by the PSU is reduced to maintain the nominal level. Configuring power budget and Redundancy using CMC web interface NOTE: To perform power management actions, you must have the Chassis Configuration Administrator privilege. To configure power budget: 1. In the left pane, click Chassis Overview > Power > Configuration. 2.
● To enable the maximum power consumption mode, type: racadm config -g cfgChassisPower -o cfgChassisMaxPowerConservationMode 1 ● To restore normal operation, type: racadm config -g cfgChassisPower -o cfgChassisMaxPowerConservationMode 0 ● To enable the power remote logging feature, enter the following command: racadm config -g cfgRemoteHosts -o cfgRhostsSyslogPowerLoggingEnabled 1 ● To specify the desired logging interval, enter the following command: racadm config -g cfgRemoteHosts -o cfgRhostsSyslogPowerL
● ● ● ● Power Off System Power Cycle System (cold boot) Reset CMC (warm boot) Non-Graceful Shutdown 3. Click Apply. A dialog box appears asking you for a confirmation. 4. Click OK to perform the power management action (for example, cause the system to reset). Executing Power Control Operations on the Chassis Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m chassis where is powerup, powerdown, powercycle, nongraceshutdown, or reset.
Executing Power Control Operations on the IOM Using RACADM To execute power control operations on the IOM using RACADM, open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m switch where indicates the operation you want to execute: power cycle. For information about RACADM commands, see the Dell Chassis Management Controller for PowerEdge FX2/FX2s RACADM Command Line Reference Guide. available at dell.com/support/manuals.
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.
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. Agent-free monitoring is the systems management solution for Dell’s 12th generation of PowerEdge servers.
assigned to the compute sleds in the lower bay earlier, are mapped to corresponding compute sleds in the upper bay. Following are some examples for PCIe reassignment: ● PCIe reassignment in full-width (FW) FC830: ○ 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.
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. ● Troubleshooting Network Time Protocol (NTP) problems.
Table 32.
○ 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. ● Problem: Available power keeps changing, even when the enclosure configuration has not changed.
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. NOTE: To reset components, you must have Debug Command Administrator privilege.
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. Before changing this parameter, understand all the implications, since the default setting must be large enough to work with most NTP servers.
Table 33.
Table 33. LED Color and Blinking Patterns Component Storage sled LED Color, Blinking Pattern Status Blue, blinking PCI identification is in progress.
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.100 NOTE: Connect the network cable to the left most RJ45.
Resolution: When in split-dual host mode, each host that is connected to the storage sled RAID must be power cycled for the RAID firmware change to be effective. ● Problem: PCIe slot reassignment option is disabled in the GUI. Resolution: Ensure that all hosts in the chassis are powered on. If you attempt changing this setting from RACADM while a host is powered on, an error message is displayed. The chassis configuration administrator privilege is required to change this setting.
NOTE: Electrostatic discharge (ESD) events can damage CMC. Under certain conditions, ESD may build up on your body or an object, and then discharge into your CMC. To prevent ESD damage, take precautions to discharge static electricity from your body while handling and accessing CMC outside the Chassis. 2. Remove the jumper plug from the password reset connector, and insert a 2-pin jumper to enable the default administrator account. To locate the password jumper on the CMC board, see the following figure.
19 Frequently asked questions This section lists the frequently asked questions about the following: ● ● ● ● RACADM Managing and Recovering a Remote System Active Directory IOM Topics: • • • • • RACADM Managing and recovering a remote system Active Directory IOM Event and error messages RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) What does this message mean? Anothe
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.
Yes. The CMC’s Active Directory querying algorithm supports multiple trees in a single forest. Does the login to CMC using Active Directory work in mixed mode (that is, the domain controllers in the forest run different operating systems, such as Microsoft Windows 2000 or Windows Server 2003)? Yes. In mixed mode, all objects used by the CMC querying process (among user, RAC Device Object, and Association Object) must be in the same domain.
