Dell Chassis Management Controller Firmware Version 4.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2013 Dell Inc.
Contents Notes, Cautions, and Warnings...................................................................................................2 1 Overview.....................................................................................................................................13 What Is New In This Release.................................................................................................................................14 Key Features........................................................
Setting Chassis Physical Location and Chassis Name...........................................................................................32 Setting Chassis Physical Location and Chassis Name Using Web Interface..................................................32 Setting Chassis Physical Location and Chassis Name Using RACADM..........................................................33 Setting Date and Time on CMC.............................................................................................
Updating Server iDRAC Firmware Using RACADM..........................................................................................48 Updating Server Component Firmware..................................................................................................................48 Enabling Lifecycle Controller...........................................................................................................................49 Filtering Components for Firmware Updates.............................
Configuring Virtual LAN Tag Properties for CMC Using RACADM..................................................................68 Configuring Services..............................................................................................................................................69 Configuring Services Using CMC Web Interface.............................................................................................69 Configuring Services Using RACADM..............................................
Configuring Remote File Share...............................................................................................................................91 Configuring BIOS Settings Using Server Clone......................................................................................................92 Accessing BIOS Profile Page...........................................................................................................................93 Adding or Saving Profile...........................
10 Configuring CMC For Single Sign-On Or Smart Card Login............................................131 System Requirements...........................................................................................................................................131 Client Systems................................................................................................................................................132 CMC................................................................................
Configuring FlexAddress.......................................................................................................................................153 Wake-On-LAN with FlexAddress...................................................................................................................153 Configuring FlexAddress for Chassis-Level Fabric and Slots........................................................................153 Configuring FlexAddress for Server-Level Slots.......................
Peripherals Compatibility and Support...........................................................................................................172 Viewing and Selecting Servers......................................................................................................................172 Video Connections.........................................................................................................................................174 Preemption Warning.....................................
Server Performance Over Power Redundancy..............................................................................................193 Remote Logging..............................................................................................................................................193 External Power Management........................................................................................................................194 Configuring Power Budget and Redundancy Using CMC Web Interface..
Enclosure Status Screen................................................................................................................................219 IP Summary Screen........................................................................................................................................219 Diagnostics...........................................................................................................................................................219 LCD Hardware Troubleshooting..
Overview 1 The Dell Chassis Management Controller (CMC) is a systems management hardware and software solution for managing multiple Dell blade chassis. It is a hot-pluggable module that sits at the back of Dell PowerEdge M1000e chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.
What Is New In This Release This release of CMC supports: • Cisco FEX switch • FC16 switch — Brocade M6505 • Mezzanine cards – QLogic FC16 2P QME2662 – Emulex FC16 LPm16002B-D • One-to- many agent free, OS independent firmware update capability for supported 12G Fibre Channel (FC) mezzanine cards • Updating firmware for Dell PowerEdge M IO Aggregator • Saving the BIOS configuration information to the hard disk and restoring the information to the same or different server.
• Secure Sockets Layer (SSL) encryption — Provides secure remote system management through the Web interface. • Launch point for the Integrated Dell Remote Access Controller (iDRAC) Web interface. • Support for WS-Management. • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade. • Graphical display of chassis component status and health.
1 GB Port 2 STK Port CMC Port Information The following TCP/IP ports are required to remotely access CMC through firewalls. These are the ports CMC listens to for connections. Table 1. CMC Server Listening Ports Port Number Function 22* SSH 23* Telnet 80* HTTP 161 SNMP Agent 443* HTTPS * Configurable port The following table lists the ports that CMC uses as a client. Table 2.
Port Number Function 514* Remote syslog 636 LDAPS 3269 LDAPS for global catalog (GC) * Configurable port Minimum CMC Version The following table lists the minimum CMC version required to enable the listed Blade Servers. Table 3. Minimum CMC Version for Blade Servers Servers Minimum version of CMC PowerEdge M600 CMC 1.0 PowerEdge M605 CMC 1.0 PowerEdge M805 CMC 1.2 PowerEdge M905 CMC 1.2 PowerEdge M610 CMC 2.0 PowerEdge M610x CMC 3.0 PowerEdge M710 CMC 2.0 PowerEdge M710HD CMC 3.
IOM Switches Minimum version of CMC Dell 10/100/1000Mb Ethernet Pass-Through CMC 1.0 Dell 4Gbps FC Pass-Through Module CMC 1.0 Dell 8/4Gbps FC SAN Module CMC 1.2 Dell 10Gb Ethernet Pass-Through CMC 2.1 Dell 10Gb Ethernet Pass-Through II CMC 3.0 Dell 10Gb Ethernet Pass-Through-K CMC 3.0 Brocade M4424 CMC 1.0 Brocade M5424 CMC 1.2 Cisco Catalyst CBS 3130X-S CMC 1.0 Cisco Catalyst CBS 3130G CMC 1.0 Cisco Catalyst CBS 3032 CMC 1.0 Dell Force10 MXL 10/40GbE CMC 4.
Table 5. Supported Remote Access Connections Connection Features CMC Network Interface ports • • • • • • • Serial port • • • Other connections • GB port: Dedicated network interface for the CMC Web interface.
Other Documents You May Need In addition to this guide, you can access the following guides available at dell.com/support/manuals. Select Choose from a list of all Dell products and click Continue. Click Software → Monitors → Electronics & Peripherals → Software : • Click Remote Enterprise System Management and then click Dell Chassis Management Controller Version 4.3 to view: – The CMC Online Help provides information about using the Web interface.
Installing and Setting Up CMC 2 This section provides information about how to install your CMC hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the next steps for configuring the CMC: • • • • Set up initial access to CMC. Access CMC through a network. Add and configure CMC users. Update CMC firmware. For more information about installing and setting up redundant CMC environments, see Understanding Redundant CMC Environment.
8. Provide each iDRAC with an IP address in the CMC Web interface and enable the LAN and IPMI interface. NOTE: iDRAC LAN interface on some servers are disabled by default. 9. Provide each IO module with an IP address in the CMC Web interface. 10. Connect to each iDRAC through the Web browser and provide final configuration of iDRAC. Default user name is root and password is calvin. 11. Connect to each IO module through the Web browser and provide final configuration of the IO module. 12.
1 Management Network 2 Standby CMC 3 Active CMC The following figures provide examples of incorrect cabling of CMC.
To daisy-chain up to four chassis: 1. Connect the GB port of the active CMC in the first chassis to the management network. 2. Connect the GB port of the active CMC in the second chassis to the STK port of the active CMC in the first chassis. 3. If you have a third chassis, connect the GB port of its active CMC to the STK port of the active CMC in the second chassis. 4. If you have a fourth chassis, connect the GB port of its active CMC to the STK port of the third chassis. 5.
Installing RACADM on a Linux Management Station 1. Log in as root to the system running a supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components. 2. Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive. 3. To mount the DVD to a required location, use the mount command or a similar command.
Proxy Server To browse through a proxy server that does not have access to the management network, you can add the management network addresses to the browser’s exception list. This instructs the browser to bypass the proxy server while accessing the management network. Internet Explorer To edit the exception list in Internet Explorer: 1. Start Internet Explorer. 2. Click Tools → Internet Options → Connections . 3. In the Local Area Network (LAN) settings section, click LAN Settings. 4.
3. Scroll to the Security section, clear the Check for publisher’s certificate revocation checkbox, and click OK. Downloading Files From CMC With Internet Explorer When you use Internet Explorer to download files from CMC you may experience problems when the Do not save encrypted pages to disk option is not enabled. To enable the Do not save encrypted pages to disk option: 1. Start Internet Explorer. 2. Click Tools → Internet Options , then click Advanced. 3.
and provides greater redundancy. The daisy-chain connection type uses fewer ports on the management network but introduces dependencies between CMCs, reducing the redundancy of the system. NOTE: Failure to cable CMC properly in a redundant configuration can cause loss of management and create broadcast storms.
accordingly. If the network configuration does not match any of these values, it is recommended to use Auto Negotiation (the Auto option) or refer to your network equipment manufacturer. Press the center button to continue to the next CMC Network Settings screen. 5. Select the duplex mode (half or full) that matches the network environment. NOTE: The network speed and duplex mode settings are not available if Auto Negotiation is set to On or 1000MB (1Gbps) is selected.
10. Select the Internet Protocol (IPv4, IPv6, or both) that you want to use for the servers. Dynamic Host Configuration Protocol (DHCP) iDRAC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. The iDRAC is assigned a unique IP address allotted over your network.Press the center button. Static You manually enter the IP address, gateway, and subnet mask in the screens immediately following.
NOTE: Using more than one interface at the same time may generate unexpected results. Table 6. CMC Interfaces Interface Description Web interface Provides remote access to CMC using a graphical user interface. The Web interface is built into the CMC firmware and is accessed through the NIC interface from a supported Web browser on the management station. For a list of supported Web browsers, see the Supported Browsers section in the Readme at dell.com/support/manuals.
Interface Description defines the semantics and information types that can be modified in a managed system. The CMC WS-MAN implementation uses SSL on port 443 for transport security, and supports basic authentication. The data available through WS-Management is provided by CMC instrumentation interface mapped to the DMTF profiles and extension profiles. For more information, see the following: • • • • • MOFs and Profiles — delltechcenter.com/page/DCIM.Library DTMF Web site — dmtf.
NOTE: The Chassis Location field is optional. It is recommended to use the Data Center, Aisle, Rack, and Rack Slot fields to indicate the physical location of the chassis. 3. Click Apply. The settings are saved. Setting Chassis Physical Location and Chassis Name Using RACADM To set the chassis name or location, date and time using the command line interface, see the setsysinfo and setchassisname commands. For more information, see RACADM Command Line Reference Guide for iDRAC7 and CMC.
The Identify page is displayed. 2. To enable blinking for a component LED, select required component and click Blink. 3. To disable blinking for a component LED, clear the required component and click UnBlink. Configuring LED Blinking Using RACADM Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm setled -m [-l ] where specifies the module whose LED you want to configure.
About Standby CMC The standby CMC is identical to and is maintained as a mirror of the active CMC. The active and standby CMCs must both be installed with the same firmware revision. If the firmware revisions differ, the system reports as redundancy degraded. The standby CMC assumes the same settings and properties of the active CMC. You must maintain the same firmware version on both CMCs, but you do not need to duplicate configuration settings on the standby CMC.
Obtaining Health Status of Redundant CMC You can view the health status of the standby CMC in the Web interface. For more information about accessing CMC health status in the Web interface, see Viewing Chassis Information and Monitoring Chassis and Component Health.
Logging In to CMC 3 You can log in to CMC as a CMC local user, as a Microsoft Active Directory user, or as an LDAP user. The default user name and password is root and calvin, respectively. You can also log in using Single Sign-On or Smart Card.
Logging Into CMC as Local User, Active Directory User, or LDAP User To log in to CMC, you must have a CMC account with Log In to CMC privilege. The default CMC user name is root, and the password is calvin. The root account is the default administrative account that ships with CMC. NOTE: For added security, it is strongly recommended that you change the default password of the root account during initial setup.
To log in to CMC as an Active Directory user using smart card: 1. Log in to CMC using the link https://. The CMC Login page is displayed prompting you to insert the smart card. 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, domainname is the domain name, and port number is the HTTPS port number. 2. Insert the smart card and click Login.
After you have configured your management station terminal emulator software and managed node BIOS, perform the following steps to log in to CMC: 1. Connect to the CMC using your management station terminal emulation software. 2. Type your CMC user name and password, and press . You are logged in to the CMC.
Multiple CMC Sessions The following table provides the list of multiple CMC sessions that are possible using the various interfaces. Table 7.
Updating Firmware 4 You can update firmware for the following: • CMC - active and standby • iKVM • IOMs You can update firmware for the following server components: • iDRAC - iDRACs earlier than iDRAC6 must be updated using the recovery interface. iDRAC6 firmware can also be updated with the recovery interface, but is deprecated for iDRAC6 and future versions.
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 → Update • Chassis Overview → I/O Module Overview → Update • Chassis Overview → iKVM → Update The Firmware Update page displays the current version of the firmware for each listed component and allows you to update the f
To avoid disconnecting other users during a reset, notify authorized users who may log in to CMC and check for active sessions in the Sessions page. To open the Sessions page, select Chassis in the tree, click the Network tab, and then click the Sessions subtab. When transferring files to and from CMC, the file transfer icon spins during the transfer. If your icon is animated, make sure that your browser is configured to allow animations. For instructions, see Allow Animations in Internet Explorer.
Updating iKVM Firmware The iKVM resets and becomes temporarily unavailable after the firmware is successfully uploaded. Related Links Downloading CMC Firmware Viewing Currently Installed Firmware Versions Updating iKVM Firmware Using CMC Web Interface To update the iKVM firmware using in the CMC Web interface: 1. Go to any of the following pages: – Chassis Overview → Update – Chassis Overview → Chassis Controller → Update – Chassis Overview → iKVM → Update The Firmware Update page is displayed. 2.
NOTE: CMC allows IOM infrastructure device firmware (IOMINF) updates only if it detects that the IOMINF firmware is out-ofdate with the image contained in CMC file system. If the IOMINF firmware is up-to-date, CMC prevents IOMINF updates. Up-to-date IOMINF devices are not listed as updatable devices.
Viewing Currently Installed Firmware Versions Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server using CMC Web interface: 1. Go to any of the following pages: – Chassis Overview → Update – Chassis Overview → Chassis Controller → Update – Chassis Overview → iKVM → Update The Firmware Update page is displayed. You can also update server iDRAC firmware at Chassis Overview → Server Overview → Update .
Dell Update Packages (DUPs) are used to perform the firmware updates using Lifecycle Controller. The default CMC configuration has a 48 MB limit on the size of the DUP. The OS-Driver Pack component DUP exceeds this limit and must be updated separately using the Extended Storage feature. The Lifecycle Controller provides module update support for iDRAC6 and later servers. The iDRAC firmware version must be 3.20 or later to update firmware using Lifecycle Controller.
The Server Component Update page enables you to update various firmware components on your system. To use the features and functions on this page, you must have: • For CMC: Server Administrator privilege. • For iDRAC: Configure iDRAC privilege and Log in to iDRAC privilege. In case of insufficient privileges, you can only view the firmware inventory of components and devices on the server. You cannot select any components or devices for any kind of Lifecycle Controller operation on the server.
The Firmware Inventory section displays only the associated components or devices across all servers present in the chassis. The filter is a pass filter; this means that it only permits components or devices associated with the filter and excludes all others. After the filtered set of components and devices is displayed in the inventory section, further filtering may occur when a component or device is selected for update.
To automate this action, iDRAC Configuration Utility (for iDRAC6) or the iDRAC Settings Utility (for iDRAC7) provides an option that can be accessed through the boot console: – * For iDRAC6 servers, on the boot console, when prompted with the message Press for Remote Access Setup within 5 sec., press . Then, on the setup screen, enable Collect System Inventory on Restart. * For iDRAC7 servers, on the boot console, select F2 for System Setup.
• Re-install • Rollback • Update • Delete Jobs Only one type of operation can be performed at a time. Components and devices that are not supported may be listed as part of the inventory, but do not permit Lifecycle Controller operations. To perform the Lifecycle Controller operations, you must have: • For CMC: Server Administrator privilege. • For iDRAC: Configure iDRAC privilege and Log in to iDRAC privilege.
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.
The Server Component Update page is displayed. 2. Filter the component or device (optional). 3. 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.
Viewing Chassis Information and Monitoring Chassis and Component Health 5 You can view information and monitor the health for the following: • Active and standby CMCs • All severs and individual servers • Storage arrays • All IO Modules (IOMs) and individual IOMs • Fans • iKVM • Power supplies (PSUs) • Temperature sensors • LCD assembly Viewing Chassis Component Summaries When you log in to the CMC Web interface, the Chassis Health page allows you to view the health of the chassis and it
Chassis Graphics The chassis is represented by front and back views (the upper and lower images, respectively). Servers and the LCD are shown in the front view and the remaining components are shown in the back view. Component selection is indicated by a blue cast and is controlled by clicking the image of the required component. When a component is present in the chassis, an icon of that component type is shown in the graphics in the position (slot) where the component has been installed.
Icon Description No server is present. 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 shown by the hardware logs and the performance data that vary with time. Properties — Displays the component properties that do not vary with time or change only infrequently.
The Servers Status page provides overviews of the servers in the chassis. For more information, see the CMC Online Help. Viewing Health Status and Information for Individual Server To view health status for individual servers, do any of the following: 1. Go to Chassis Overview → Properties → Health . 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.
Viewing Information and Health Status For Individual IOM To view health status of the individual IOMs, in the CMC Web interface, do any of the following: 1. Go to Chassis Overview → Properties → Health . The Chassis Health page is displayed. The lower section of Chassis Graphics depicts the rear view of the chassis and contains the health status for the IOMs. IOM health status is indicated by the overlay of the IOM subgraphic. Move the cursor to hover over the individual IOM subgraphic.
Move the cursor over an iKVM subgraphic and a corresponding text hint or screen tip is displayed. The text hint provides additional information for the iKVM. Click the iKVM subgraphic to view the iKVM information on the right. 2. Go to Chassis Overview → iKVM → Properties . The iKVM Status page displays the status and readings of the iKVM associated with the chassis. For more information, see the CMC Online Help.
Configuring CMC 6 CMC enables you to configure CMC properties, set up users, and set up alerts to perform remote management tasks. Before you begin configuring the CMC, you must first configure the CMC network settings to allow the CMC to be managed remotely. This initial configuration assigns the TCP/IP networking parameters that enable access to the CMC. For more information, see Setting Up Initial Access to CMC. You can configure CMC using Web interface or RACADM.
Viewing and Modifying CMC Network LAN Settings The LAN settings, such as community string and SMTP server IP address, affect both the CMC and the external settings of the chassis. If you have two CMCs (active and standby) on the chassis, and they are connected to the network, the standby CMC automatically assumes the network settings of the active CMC in the event of failover. When IPv6 is enabled at boot time, three router solicitations are sent every four seconds.
To enable/disable the CMC IPv4 addressing, type: racadm config -g cfgLanNetworking -o cfgNicIPv4Enable 1 racadm config -g cfgLanNetworking -o cfgNicIPv4Enable 0 NOTE: The CMC IPv4 addressing is enabled by default. To enable/disable the CMC IPv6 addressing, type: racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 1 racadm config -g cfgIpv6LanNetworking -o cfgIPv6Enable 0 NOTE: The CMC IPv6 addressing is disabled by default.
To disable the DHCP for DNS address feature for IPv6 and specify static preferred and alternate DNS server addresses, type: racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServersFromDHCP6 0 Setting Static DNS IP addresses NOTE: The Static DNS IP addresses settings are not valid unless the DCHP for DNS address feature is disabled.
where: is 10 or 100 (default). Setting the Maximum Transmission Unit (MTU) (IPv4 and IPv6) The MTU property allows you to set a limit for the largest packet that can be passed through the interface. To set the MTU, type: racadm config -g cfgNetTuning -o cfgNetTuningMtu where is a value between 576–1500 (inclusive; default is 1500). NOTE: IPv6 requires a minimum MTU of 1280. If IPv6 is enabled, and cfgNetTuningMtu is set to a lower value, the CMC uses an MTU of 1280.
Configuring Virtual LAN Tag Properties for CMC Using Web Interface To configure VLAN for CMC using the CMC Web interface: 1. Go to any of the following pages: – In the system tree, go to Chassis Overview and click Network → VLAN. – In the system tree, go to Chassis Overview → Server Overview and click Network → VLAN. The VLAN Tag Settings page is displayed. VLAN tags are chassis properties. They remain with the chassis even when a component is removed. 2.
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. If you disable the option, use local RACADM to re-enable the Web Server, since disabling the Web Server also disables remote RACADM. • SSH — Enable access to CMC through firmware RACADM. • Telnet — Enable access to CMC through firmware RACADM • RACADM — Enable access to CMC using RACADM.
3. Click Apply, and then update all default time outs and maximum time out limits. Configuring Services Using RACADM To enable and configure the various services, use the following RACADM objects: • cfgRacTuning • cfgRacTuneRemoteRacadmEnable For more information about these objects, see RACADM Command Line Reference Guide for iDRAC7 and CMC 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.
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. The Chassis group features are: • The Chassis Group page displays images portraying the front and back of each chassis, a set for the leader and a set for each member.
6. Enter the corresponding password in the Password field. 7. Click Apply. 8. Repeat step 4 through step 8 to add a maximum of eight members. The new members’ Chassis Names appear in the Members dialog box. The status of the new member is displayed by selecting the Group in the tree. Details are available by clicking on the chassis image or the details button.
3. Select None, and then click Apply. Launching a Member Chassis’s or Server’s Web page Links to a member chassis’s Web page, a server’s Remote Console or the server iDRAC’s Web page within the group are available through the lead chassis’s group page. You can use the same user name and password that was used to log in to the lead chassis, to log in to the member device. If the member device has the same login credentials then no additional login is required.
Server Inventory for MCM group 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. The report contains data for: • All servers currently in all the group chassis (including the leader.) • Empty slots and extension slots (including full height and double width blades.) Saving Server Inventory Report To save the server inventory report using CMC Web interface: 1.
Data Field Example Operating System Windows Server 2008 NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Model PowerEdgeM610 Service Tag 1PB8VF1 Total System Memory 4.0 GB NOTE: Requires CMC 4.0 (or higher) on member; otherwise shown as blank. # of CPUs 2 NOTE: Requires CMC 4.0 (or higher) on member; otherwise shown as blank. CPU Info Intel (R) Xeon (R) CPU E5502 @1.87GHzn NOTE: Requires CMC 4.0 (or higher) on member; otherwise shown as blank.
Login Type Certificate Type How to Obtain NOTE: CMC ships with a default self-signed SSL server certificate. The CMC Web server and Virtual Console use this certificate. Related Links Secure Sockets Layer (SSL) Server Certificates Secure Sockets Layer (SSL) Server Certificates CMC includes a Web server that is configured to use the industry-standard SSL security protocol to transfer encrypted data over the Internet.
Viewing Server Certificate Generating a New Certificate Signing Request To ensure security, it is strongly recommended that you obtain and upload a secure server certificate to CMC. Secure server certificates ensure the identity of a remote system and that information exchanged with the remote system cannot be viewed or changed by others. Without a secure server certificate, CMC is vulnerable to access from unauthorized users.
1. In the system tree, go to Chassis Overview, and then click Network → SSL. The SSL Main Menu is displayed. 2. Select Upload Server Certificate Based on Generated CSR option and click Next. 3. Click Choose File and specify the certificate file. 4. Click Apply. If the certificate is invalid, an error message is displayed. NOTE: The File Path value displays the relative file path of the certificate you are uploading.
Viewing Server Certificate Using Web Interface In the CMC Web interface, go to Chassis Overview → Network → SSL , select View Server Certificate and click Next. The View Server Certificate page displays the SSL server certificate currently in use. For more information, see CMC Online Help. Viewing Server Certificate Using RACADM To view the SSL server certificate, use the sslcertview command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.
Creating a CMC Configuration File The CMC configuration file, .cfg, is used with the racadm config -f .cfgcommand to create a simple text file. The command allows you to build a configuration file (similar to a .ini file) and configure the CMC from this file. You may use any file name, and the file does not require a .cfg extension (although it is referred to by that designation in this subsection).
Parsing Rules • Lines that start with a hash character (#) are treated as comments. A comment line must start in column one. A "#" character in any other column is treated as a # character. Some modem parameters may include # characters in their strings. An escape character is not required. You may want to generate a .cfg from a racadm getconfig -f .cfg command, and then perform a racadm config -f .cfg command to a different CMC, without adding escape characters.
• For indexed groups the object anchor must be the first object after the [ ] pair. The following are examples of the current indexed groups: [cfgUserAdmin] cfgUserAdminUserName= • When using remote RACADM to capture the configuration groups into a file, if a key property within a group is not set, the configuration group is not saved as part of the configuration file.
Viewing and Terminating CMC Sessions Using Web Interface To view or terminate a session using Web interface: 1. In the system tree, go to Chassis Overview and click Network → Sessions. The Sessions page displays the session ID, username, IP address, and session type. For more information about these properties, see the CMC Online Help. 2. To terminate the session, click Terminate for a session.
Configuring Server 7 You can do the following for the server: • Configuring Slot Names • Configuring iDRAC Network Settings • Configuring iDRAC VLAN Tag Settings • Setting First Boot Device • Configuring Server FlexAddress • Configuring Remote File Share • Configuring BIOS Settings Using Server Clone Configuring Slot Names Slot names are used to identify individual servers.
1. In the system tree, go to Chassis Overview → Server Overview and then click Setup → Slot Names. The Slot Names page is displayed. 2. In the Slot Name field, edit the slot name. Repeat this step for each slot you want to rename. 3. To use the server’s host name as slot name, select Use Host Name for the Slot Name option. This override the static slot names with the server’s Host Name (or system name), if it is available. This requires the OMSA agent to be installed on the server.
Setting Description password value is assigned to a server's iDRAC root user password when the server is inserted into chassis. The password can have 1 to 20 printable (including spaces) characters. Confirm iDRAC Root Password Verifies the password entered into the iDRAC Root Password field. Enable iDRAC LAN Enables or disables the iDRAC LAN channel. By default, this option is disabled. Enable iDRAC IPv4 Enables or disables IPv4 on iDRAC. By default, this option is enabled.
Setting Description stateless address auto configuration. By default, this option is enabled. 3. iDRAC IPv6 Gateway Specifies the default IPv6 gateway to be assigned to the iDRACs. The default value is "::". iDRAC IPv6 Prefix Length Specifies the prefix length to be assigned for the IPv6 addresses on the iDRAC. The default value is 64. Click Save QuickDeploy Settings to save the settings.
Modifying iDRAC Network Settings Using RACADM RACADM config or getconfig commands support the -m option for the following configuration groups: • cfgLanNetworking • cfgIPv6LanNetworking • cfgRacTuning • cfgRemoteHosts • cfgSerial • cfgSessionManagement For more information on the property default values and ranges, see the RACADM Command Line Reference Guide for iDRAC7 and CMC.
• To remove a server VLAN, disable the VLAN capabilities of the specified server's network: racadm setniccfg -m server- -v The valid values for are 1-16. For example: racadm setniccfg -m server-1 -v Setting First Boot Device You can specify the CMC first boot device for each server.
Setting First Boot Device Using RACADM Setting First Boot Device For Multiple Servers Using CMC Web Interface NOTE: To set the first boot device for servers, you must have Server Administrator privileges or Chassis Configuration Administrator privileges and iDRAC login privileges. To set the first boot device for multiple servers using the CMC Web interface: 1. In the system tree, go to Server Overview, and then click Setup → First Boot Device. A list of servers is displayed. 2.
To configure the remote file share using CMC Web interface: 1. In the system tree, go to Server Overview, and then click Setup → Remote File Sharing. The Deploy Remote File Share page is displayed. Enter the result of your step here (optional). 2. Specify the required settings. For more information, see the CMC Online Help. 3. Click Connect to connect to a remote file share. To connect a remote file share, you must provide the path, user name, and password.
Viewing Profile Log Completion Status and Troubleshooting Accessing BIOS Profile Page You can add, manage, and apply BIOS profiles to one or more servers using the BIOS Profile page. To access the BIOS Profile page using the CMC Web interface, in the system tree, go to Chassis Overview → Server Overview and click Setup → Profiles. The BIOS Profiles page is displayed.
Applying Profile When stored profiles are available in the non-volatile media on the CMC, to initiate a server cloning operation, you can apply a Stored Profile to one or more servers. NOTE: If a server does not support Lifecycle Controller or the chassis is powered off, you cannot apply a profile to the server. To apply a profile to one or more server(s): 1. In the BIOS Profiles page, in the Save and Apply Profiles section, select the servers for which you want to apply the selected profile.
For more information, see the CMC Online Help. Editing Profile You can edit the name and description of a BIOS profile that is stored on the CMC non-volatile media (SD Card). To edit a stored profile: 1. In the BIOS Profile page, in the Manage Profiles on SD Card section, select the required profile and then click Edit Profile. The Edit BIOS Profile — section is displayed. 2. Edit the profile name and description of the BIOS Profile as required and then click Edit Profile.
Viewing Profile Log To view the profile log, in the BIOS Profiles page, see the Recent Profile Log section that lists the 10 latest profile log entries directly from server cloning operations. Each recent profile log displays the severity, the time and date when server cloning operation was submitted, and the description of the cloning log message. The log entries are also available in the RAC log. To view the other available entries, click Go to Profile Log. The Profile Log page is displayed.
Launching iDRAC from Server Status Page To launch the iDRAC management console for an individual server: 1. In the system tree, expand Server Overview. All of the servers (1–16) appear in the expanded Servers list. 2. Click the server for which you want to launch the iDRAC Web interface. The Server Status page is displayed. 3. Click Launch iDRAC GUI. The iDRAC Web interface is displayed.
Configuring CMC To Send Alerts 8 You can set alerts and actions for certain events that occur on the managed system. 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 (e-mail alert or SNMP trap), then an alert is sent to one or more configured destinations. To configure CMC to send alerts: 1. Enable the global chassis event alerts. 2.
Configuring Alert Destinations The management station uses Simple Network Management Protocol (SNMP) to receive data from CMC. You can configure the IPv4 and IPv6 alert destinations, e-mail settings, and SMTP server settings, and test these settings. Before configuring the e-mail alert or SNMP trap settings, make sure that you have Chassis Configuration Administrator privilege.
3. Specify the events for which alerts must be generated: racadm config -g cfgAlerting -o cfgAlertingFilterMask where is a hex value between 0x0 and 0xffffffff. To obtain the mask value, use a scientific calculator in hex mode and add the second values of the individual masks (1, 2, 4, and so on) using the key.
where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualified Domain Names (FQDNs). 5. Specify a destination IP address to receive the traps alert: racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr -i where is a valid destination, and is the index value specified in step 4. 6.
Configuring E-Mail Alert Settings Using RACADM To send a test e-mail to an e-mail alert destination using RACADM : 1. Open a serial/Telnet/SSH text console to CMC and log in. 2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 NOTE: Only one filter mask may be set by both SNMP and e-mail alerting. You may skip step 3 if you have already set a filter mask. 3.
Configuring User Accounts and Privileges 9 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 local administrator account. This default user name is root and the password is calvin. As an administrator, you can setup user accounts to allow other users to access CMC.
Privilege Description • • Provides services to the chassis, such as date and time, firmware update, and CMC reset. Is associated with the chassis, such as slot name and slot priority. Although these properties apply to the servers, they are strictly chassis properties relating to the slots rather than the servers themselves. For this reason, slot names and slot priorities can be added or changed whether or not servers are present in the slots.
Privilege Description Based on the privileges responding from the server, CMC firmware decides if the user has the right to perform the action. Listed below are the privileges and the actions on the server to which the Server Administrator is entitled. These rights are applied only when the chassis user does not have the Server Administrative privilege on the chassis.
User Group Privileges Granted Power User • • • • Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator • • • • • • • • Login Clear Logs Administrator Chassis Control Administrator (Power commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator Guest User Login Custom Select any combination of the following permissions: • • • • • • • • • • • None CMC Login User Chassis Configuration Administrator
Privilege Set Administrator Permissions Power User Permissions Guest User Permissions Debug Command Administrator Yes No No Fabric A Administrator Yes Yes No Fabric B Administrator Yes Yes No Fabric C Administrator Yes Yes No Modifying Root User Administrator Account Settings For added security, it is strongly recommended that you change the default password of the root (User 1) account. The root account is the default administrative account that ships with CMC.
Configure Local Users Using RACADM NOTE: You must be logged in as user root to execute RACADM commands on a remote Linux system. You can configure up to 16 users in the CMC property database. Before you manually enable a CMC user, verify if any current users exist. If you are configuring a new CMC or if you have used the racadm racresetcfg command, the only current user is root with the password calvin. The racresetcfg subcommand resets all configuration parameters to the original defaults.
racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 2 123456 racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminPrivilege 0x00000001 racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminEnable 1 To verify that the user was added successfully with the correct privileges, use the following commands: racadm getconfig –g cfgUserAdmin –i 2 For more information on the RACADM commands, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals.
Supported Active Directory Authentication Mechanisms You can use Active Directory to define CMC user access using two methods: • • Standard schema solution that uses Microsoft’s default Active Directory group objects only. Extended schema solution that has customized Active Directory objects provided by Dell. All the access control objects are maintained in Active Directory. It provides maximum flexibility to configure user access on different CMCs with varying privilege levels.
Role Group Default Privilege Level Permissions Granted • • • • • • • 2 None • • • • • • • • Bit Mask Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator 0x00000ed9 CMC Login User Clear Logs Administrator Chassis Control Administrator (Power Commands) Server Administrator Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator 3 None CMC Login
Configuring Active Directory With Standard Schema Using CMC Web Interface NOTE: For information about the various fields, see the CMC Online Help. 1. In the system tree, go to Chassis Overview, and then click User Authentication → Directory Services. The Directory Services page is displayed. 2. Select Microsoft Active Directory (Standard Schema). The settings to be configured for standard schema is displayed on the same page. 3. Specify the following: 4.
racadm config -g cfgStandardSchema -i -o cfgSSADRoleGroupDomain racadm config -g cfgStandardSchema -i -o cfgSSADRoleGroupPrivilege racadm sslcertupload -t 0x2 -f racadm sslcertdownload -t 0x1 -f NOTE: For bit mask number values, see the database property chapter of the RACADM Command Line Reference Guide for iDRAC7 and CMC 2.
provides an administrator maximum flexibility over the different combinations of users, RAC privileges, and RAC devices on the network without much complexity. When there are two CMCs on the network that you want to integrate with Active Directory for authentication and authorization, create at least one association object and one RAC device object for each CMC.
To configure the objects for the single domain scenario: 1. Create two Association Objects. 2. Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs. 3. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privilege. 4. Group user1 and user2 into Group1. 5. Add Group1 as Members in Association Object 1 (A01), Priv1 as Privilege Objects in A01, and RAC1, RAC2 as RAC Devices in A01. 6.
1. Ensure that the domain forest function is in Native or Windows 2003 mode. 2. Create two Association Objects, A01 (of Universal scope) and A02, in any domain. The figure Setting Up Active Directory Objects in Multiple Domains shows the objects in Domain2. 3. Create two RAC Device Objects, RAC1 and RAC2, to represent the two CMCs. 4. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privilege. 5. Group user1 and user2 into Group1.
Using Dell Schema Extender CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file. To make sure that the Dell Schema Extender utility functions properly, do not modify the name of this file. 1. In the Welcome screen, click Next. 2. Read and understand the warning and click Next. 3. Select Use Current Log In Credentials or enter a user name and password with schema administrator rights. 4. Click Next to run the Dell Schema Extender. 5. Click Finish. The schema is extended.
OID 1.2.840.113556.1.8000.1280.1.7.1.2 Attributes dellProductMembers dellPrivilegeMember Table 22. : dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines the privileges (Authorization Rights) for CMC device. Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsTestAlertUser dellIsDebugCommandAdmin dellPermissionMask1 dellPermissionMask2 Table 23.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.1 Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellProductMembers FALSE Description: List of dellRacDevices objects that belong to this role. This attribute is the forward link to the dellAssociationMembers backward link. Link ID: 12070 OID: 1.2.840.113556.1.8000.1280.1.1.2.2 Distinguished Name: (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.11 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: dellSchemaVersion TRUE Description: The Current Schema Version is used to update the schema. OID: 1.2.840.113556.1.8000.1280.1.1.2.12 Case Ignore String(LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.
Related Links Adding Objects to Association Object Creating RAC Device Object Creating Privilege Object Creating Association Object Creating RAC Device Object To create RAC device object: 1. In the MMC Console Root window, right-click a container. 2. Select New → Dell Remote Management Object Advanced. The New Object window is displayed. 3. Enter a name for the new object.
Adding RAC Devices or RAC Device Groups Adding Users or User Groups To add users or user groups: 1. Right-click the Association Object and select Properties. 2. Select the Users tab and click Add. 3. Enter the user or user group name and click OK. Adding Privileges To add privileges: 1. Select the Privileges Object tab and click Add. 2. Enter the privilege object name and click OK.
5. In the Extended Schema Settings section, enter the CMC device name and the domain name. 6. If you have enabled certificate validation, you must upload the domain forest root certificate authority-signed certificate to CMC. In the Manage Certificates section, type the file path of the certificate or browse to the certificate file. Click Upload to upload the file to CMC. NOTE: The File Path value displays the relative file path of the certificate you are uploading.
After you enable the Specify Server option, you can specify an LDAP server and global catalog with IP addresses or fully qualified domain names (FQDNs) of the servers. The FQDNs consist of the host names and the domain names of the servers.
Figure 2. Configuration of CMC with Generic LDAP Configuring the Generic LDAP Directory to Access CMC The CMC's Generic LDAP implementation uses two phases in granting access to a user—user authentication and then user authorization. Authentication of LDAP Users Some directory servers require a bind before any searches can be performed against a specific LDAP server. To authenticate a user: 1. Optionally bind to the Directory Service. The default is an anonymous bind. 2.
1. In the system tree, go to Chassis Overview, and then click User Authentication → Directory Services. 2. Select Generic LDAP. The settings to be configured for standard schema is displayed on the same page. 3. Specify the following: NOTE: For information about the various fields, see the CMC Online Help. – Common Settings – Server to use with LDAP: * Static server — Specify the FQDN or IP address and the LDAP port number.
CMC can be configured to optionally query a DNS server for SRV records. If the cfgLDAPSRVLookupEnable property is enabled the cfgLDAPServer property is ignored. The following query is used to search the DNS for SRV records: _ldap._tcp.domainname.com ldap in the above query is the cfgLDAPSRVLookupServiceName property. cfgLDAPSRVLookupDomainName is configured to be domainname.com. For more information about the RACADM objects, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.
Configuring CMC For Single Sign-On Or Smart Card Login 10 This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. Starting with CMC version 2.10, CMC supports Kerberos based Active Directory authentication to support Smart Card and SSO logins. SSO uses kerberos as an authentication method allowing users who have signed in to the domain 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 • CMC must have firmware version 2.10 or later. • Each CMC must have an Active Directory account.
1. Run the ktpass utility on the domain controller (Active Directory server) where you want to map CMC to a user account in Active Directory. 2. Use the following ktpass command to create the Kerberos keytab file: C:\>ktpass -princ HTTP/cmcname.domain_name.com@REALM_NAME.COM - mapuser dracname -crypto DES-CBC-MD5 -ptype KRB5_NT_PRINCIPAL -pass * -out c: \krbkeytab NOTE: The cmcname.domainname.com must be lower case as required by RFC and the @REALM_NAME must be uppercase.
Configuring Browser For Smart Card Login Mozilla Firefox — CMC 2.10 does not support Smart Card login through the Firefox browser. Internet Explorer — Ensure that the Internet Browser is configured to download Active-X plug-ins. Configuring CMC SSO Or Smart Card Login For Active Directory Users You can use CMC Web interface or RACADM to configure CMC SSO or smart card login.
3. In the Kerberos Keytab section, click Browse, select keytab file, and click Upload . When the upload is complete, a message is displayed indicating whether the keytab file is successfully uploaded or not.
11 Configuring CMC to Use Command Line Consoles This section provides information about the CMC command line console (or serial/Telnet/Secure Shell console) features, and explains how to set up the system so that you can perform systems management actions through the console. For information on using the RACADM commands in CMC through the command line console, see RACADM Command Line Reference Guide for iDRAC7 and CMC.
Using Telnet Console With CMC You can have up to four Telnet sessions with CMC at a time. If your management station is running Windows XP or Windows 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 the Microsoft Support website at support.microsoft.com.
Scheme Type Message Integrity Authentication Scheme • • • • • • RIJNDAEL192-CBC AES128-CBC RIJNDAEL128-CBC BLOWFISH-128-CBC 3DES-192-CBC ARCFOUR-128 • • • • HMAC-SHA1-160 HMAC-SHA1-96 HMAC-MD5-128 HMAC-MD5-96 Password Configure Public Key Authentication over SSH You can configure up to 6 public keys that can be used with the service username over SSH interface.
Generating Public Keys for Windows Before adding an account, a public key is required from the system that accesses the CMC over SSH. There are two ways to generate the public/private key pair: using PuTTY Key Generator application for clients running Windows or sshkeygen CLI for clients running Linux. This section describes simple instructions to generate a public/private key pair for both applications. For additional or advanced usage of these tools, see the application Help.
Adding Public Keys To add a public key to the CMC using the file upload -f option, type: racadm sshpkauth –i svcacct –k 1 –p 0xfff –f NOTE: You can only use the file upload option with remote RACADM. For more information, see RACADM Command Line Reference Guide for iDRAC7 and CMC.
5. Press , and then set the Bps/Par/Bits option to 115200 8N1. 6. Press , and then set Hardware Flow Control to Yes and set Software Flow Control to No. To exit the Serial Port Setup menu, press . 7. Select Modem and Dialing and press . 8. In the Modem Dialing and Parameter Setup menu, press to clear the init, reset, connect, and hangup settings so that they are blank, and then press to save each blank value. 9.
There are up to six IOMs on the managed system. To connect to an IOM: connect switch-n where n is an IOM label A1, A2, B1, B2, C1, and C2. (See Figure 13-1 for an illustration of the placement of IOMs in the chassis.) When you reference the IOMs in the connect command, the IOMs are mapped to switches as shown in the following table. Table 29.
3. Scroll down to Serial Communication and press . In the pop-up dialog box, the serial communication list displays these options: – – – off on without console redirection on with console redirection via COM1 Use the arrow keys to navigate between these options. 4. Ensure that On with console redirection via COM1 is enabled. 5. Enable Redirection After Boot (default value is disabled). This option enables BIOS console redirection across subsequent reboots. 6. Save the changes and exit.
timeout=10 #splashimage=(hd0,2)/grub/splash.xpm.gz serial --unit=1 --speed=57600 terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp) root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600 initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 initrd /boot/initrd-2.4.9-e.3.img When you edit the /etc/grub.
l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly.
Using FlexAddress and FlexAdress Plus Cards 12 This section provides information about FlexAddress and FlexAddress Plus cards, how to configure and use these cards. Related Links About Flexaddress About FlexAddress Plus FlexAddress and FlexAddress Plus Comparison About Flexaddress The FlexAddress feature is an optional upgrade that allows server modules to replace the factory-assigned World Wide Name and Media Access Control (WWN/MAC) network IDs with WWN/MAC IDs provided by the chassis.
FlexAddress and FlexAddress Plus Comparison FlexAddress has 208 addresses divided into 16 server slots, thus each slot is allocated with 13 MACs. FlexAddress Plus has 2928 addresses divided into 16 server slots, thus each slot is allocated with 183 MACs. The following table shows the provision of the MAC addresses in both the features. Fabric A Fabric B Fabric C iDRAC Management Total MACs FlexAddress 4 4 4 1 13 FlexAddress Plus 60 60 60 3 183 Figure 3.
Component Minimum Required Version FC Mezzanine card - Emulex LPe1105M4, FC8 BIOS 3.03a3 and firmware 2.72A2 or later Server Module BIOS • • • • • • • PowerEdge M600 – BIOS 2.02 or later PowerEdge M605 – BIOS 2.03 or later PowerEdge M805 PowerEdge M905 PowerEdge M610 PowerEdge M710 PowerEdge M710hd PowerEdgeM600/M605 LAN on motherboard (LOM) • • Boot code firmware 4.4.1 or later iSCSI boot firmware 2.7.11 or later iDRAC • • Version 1.50 or later for PowerEdge xx0x systems Version 2.
Activating FlexAddress Plus FlexAddress Plus is delivered on the FlexAddress Plus Secure Digital (SD) card along with the FlexAddress feature. NOTE: The SD card labeled FlexAddress only contains FlexAddress and the card labeled FlexAddress Plus contains FlexAddress and FlexAddress Plus. The card must be inserted into CMC to activate the feature. Some servers, such as the PowerEdge M710HD, may require more MAC addresses than FA can provide to CMC, depending on how they are configured.
Dell Feature Cards may contain more than one feature. Once any feature included on a Dell Feature Card has been activated on a chassis, any other features that may be included on that Dell Feature Card cannot be activated on a different chassis.
The General Chassis Settings page is displayed. The FlexAddress has a value Active or Not Active. The value Active indicates the feature is installed on the chassis and Not Active indicates the feature is not installed and not in use on the chassis. Use the following RACADM command to display FlexAddress status for the entire chassis: racadm getflexaddr To display FlexAddress status for a particular slot: racadm getflexaddr [-i ] where is a value from 1– 16.
Configuring FlexAddress FlexAddress is an optional upgrade that allows server modules to replace the factory-assigned WWN/MAC ID with a WWN/MAC ID provided by the chassis. NOTE: In this section, the term FlexAddress also indicates FlexAddress Plus. You must purchase and install the FlexAddress upgrade to configure the FlexAddress. If the upgrade is not purchased and installed, the following text is displayed on the Web interface: Optional feature not installed.
The Deploy FlexAddress page is displayed. 2. In the Select Fabrics for Chassis-Assigned WWN/MACs section, select the fabric type for which you want to enable FlexAddress. To disable, clear the option. NOTE: If no fabrics are selected, FlexAddress is not enabled for the selected slots. The Select Slots for Chassis-Assigned WWN/MACs page is displayed. 3. Select the Enabled option for the slot for which you want to enable FlexAddress. To disable, clear the option.
where, = 1 to 16 = A, B, C = 0 or 1 0 is disable and 1 is enable. Additional FlexAddress Configuration for Linux When changing from a server-assigned MAC ID to chassis-assigned MAC ID on Linux-based operating systems, additional configuration steps may be required: • SUSE Linux Enterprise Server 9 and 10 — You may need to run Yet Another Setup Tool (YAST) on the Linux system to configure the network devices and then restart the network services.
Table 31. FlexAddress Commands and Output Situation Command Output SD card in the active CMC module is bound to another service tag. $racadm featurecard -s The feature card inserted is valid and contains the following feature(s) FlexAddress: The feature card is bound to another chassis, svctag = SD card SN = SD card in the active CMC module that is bound to the same service tag.
be bound by the terms of this agreement. If you do not agree to these terms, promptly return all Software items (disks, written materials, and packaging) and delete any preloaded or embedded Software. You may use one copy of the Software on only one computer at a time. If you have multiple licenses for the Software, you may use as many copies at any time as you have licenses. "Use" means loading the Software in temporary memory or permanent storage on the computer.
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Managing I/O Fabric 13 The chassis can have up to six I/O modules (IOMs), where each IOM is a pass-through or switch module. The IOMs are classified into three groups—A, B, and C. Each group has two slots—Slot 1 and Slot 2. The slots are designated with letters, from left to right, across the back of the chassis: A1 | B1 | C1 | C2 | B2 | A2. Each server has slots for two mezzanine cards (MCs) to connect to the IOMs. The MC and the corresponding IOM must have the same fabric.
The following figure shows the location of IOMs in the chassis. The location of each IOM is indicated by its group number (A, B, or C). These discrete fabric paths are split into two IO Banks, bank one and two. On the chassis, the IOM slot names are marked A1, A2, B1, B2, C1, and C2. Figure 4. Rear View of a Chassis, Showing the Location of the IOMs 1 Bank 1 (Slots A1, B1, C1) 2 Bank 2 (Slots A2, B2, C2) CMC creates entries in both the hardware log and CMC logs for invalid hardware configurations.
Fabric verification for server IOMs and MCs is performed only when the chassis is powered on. When the chassis is on standby power, the iDRACs on the server modules remain powered off and thus are unable to report the server's MC fabric type. The MC fabric type may not be reported in the CMC user interface until the iDRAC on the server is powered on. Additionally, if the chassis is powered on, fabric verification is performed when a server or IOM is inserted (optional).
NOTE: For Ethernet switches, the in-band (VLAN1) and out-of-band management IP addresses cannot be the same or on the same network; this results in the out-of-band IP address not being set. See the IOM documentation for the default in-band management IP address. NOTE: Do not configure I/O module network settings for Ethernet pass-through and Infiniband switches. Configuring Network Settings for IOMs Using CMC Web Interface NOTE: This feature is supported on PowerEdge M I/O Aggregator IOM only.
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.
Managing VLAN for IOM Virtual LANs (VLANs) for IOMs allow you to separate users into individual network segments for security and other reasons. By using VLANs you can isolate the networks for individual users on a 32 port switch. You can associate selected ports on a switch with selected VLAN and treat these ports as a separate switch. CMC Web Interface allows you to configure the in-band management ports (VLAN) on the IOMs.
8. Click Apply. 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. In the system tree, 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.
The VLANs assigned to the selected IOMs are removed. An Operation Successful message is displayed. The current VLAN settings that are assigned to the IOMs are displayed in the VLAN Assignment Summary field. Updating Untagged VLANs for IOMs Using CMC Web Interface To update untagged VLANs for IOM(s) using the CMC Web interface: 1. In the system tree, go to I/O Module Overview and click Setup → VLAN Manager . The VLAN Manager page is displayed. 2.
Configuring and Using iKVM 14 The local access KVM module for the Dell M1000e server chassis is called the Avocent Integrated KVM Switch Module, or iKVM. The iKVM is an analog keyboard, video, and mouse switch that plugs into the chassis. It is an optional, hotpluggable module to the chassis that provides local keyboard, mouse, and video access to the servers in the chassis, and to the active CMC’s command line.
Physical Connection Interfaces You can connect to a server or the CMC CLI console through the iKVM from the chassis front panel, an Analog Console Interface (ACI), and the chassis rear panel. NOTE: The ports on the control panel on the front of the chassis are designed specifically for the iKVM, which is optional. If you do not have the iKVM module, you cannot use the front control panel ports. iKVM Connection Precedences Only one iKVM connection is available at a time.
1. Press . The Main dialog box is displayed. If a password is assigned, the Password dialog box appears after clicking . 2. Type the password and click OK. The Main dialog box appears. NOTE: There are four options for invoking OSCAR. You can enable one, multiple, or all of these key sequences by selecting boxes in the Invoke OSCAR section of the Main dialog box. Related Links Setting Console Security Navigation Basics Navigation Basics Table 32.
Key or Key Sequence Result / Moves the cursor to the top (Home) or bottom (End) of a list. Deletes characters in a text box. Number Keys Type from the keyboard or keypad. Disabled. To change case, use the key. Configuring Oscar You can configure the OSCAR settings using the Setup dialog box. Accessing Setup Dialog Box To access the Setup dialog box: 1. Press to launch the OSCAR interface. The Main dialog box is displayed. 2. Click Setup.
3. 4. To choose the default display order of servers, do one of the following: – Select Name to display servers alphabetically based on the name. – Select Slot to display servers numerically by slot number. Click OK. Assigning Key Sequences for OSCAR To assign one or more key sequences for OSCAR activation, select a key sequence from the Invoke OSCAR menu and click OK. The default key to invoke OSCAR is .
7. Left-click on the title bar and drag it to the desired location on the desktop and then right-click to return to the Flag dialog box. 8. Click OK and again click OK to save the settings. To exit without saving the changes, click . Managing Servers With iKVM The iKVM is an analog switch matrix supporting up to 16 servers. The iKVM switch uses the OSCAR user interface to select and configure the servers.
Viewing Server Status The right columns of the Main dialog box indicates the server status in the chassis. The following table describe the status symbols. Table 33. OSCAR Interface Status Symbols Symbols Description Server is online. Server is offline or absent from chassis. Server is not available. Server is being accessed by the user channel indicated by the letter: • • A=rear panel B=front panel Selecting Servers Use the Main dialog box to select the servers.
The Main dialog box appears. 2. Click Setup and then Menu. The Menu dialog box appears. 3. Select Name or Slot for the Display/Sort Key. 4. Type the desired delay time in seconds in the Screen Delay Time field. 5. Click OK. Soft Switching to a Server To soft switch to a server: • To select a server, press .
Setting Console Security OSCAR enables you to configure security settings on the iKVM console. You can setup a screen saver mode that engages after the console remains unused for a specified delay time. Once engaged, the console remains locked until you press any key or move the mouse. Enter the screen saver password to continue. Use the Security dialog box to lock the console with a password, set or change the password, or enable the screen saver.
– If the mode is set to Screen, the OSCAR flag bounces around the screen for the duration of the test. Before the test starts, a warning popup box displays the following message: "Energy mode may damage a monitor that is not ENERGY STAR compliant. However, once started, the test can be quit immediately via mouse or keyboard interaction." CAUTION: Monitor damage may result from the use of Energy mode with monitors not compliant with Energy Star. 5. Optional: To activate the screen saver test, click Test.
To immediately turn on the screen saver, press and then press . Clearing Lost or Forgotten Password When the iKVM password is lost or forgotten, you can reset it to the iKVM factory default, and then change the password. You can reset the password using either the CMC Web interface or RACADM. To reset a lost or forgotten iKVM password using the CMC Web interface, in the system tree, go to Chassis Overview → iKVM, click Setup tab, and then click Restore Default Values.
Adding Servers to the Scan List Removing Server from Scan List Starting the Scan Mode Cancelling Scan Mode Adding Servers to the Scan List To add servers to the scan list: 1. Press . The Main dialog box is displayed. 2. Click Setup and then Scan. The Scan dialog box is displayed listing all servers in the chassis. 3. Perform one of the following functions: – Select the servers you want to scan – Double-click the server name or slot. 4.
If OSCAR is not open, move the mouse or press any key on the keyboard The Main dialog box is displayed. Select a server in the list. 2. Click Commands. The Commands dialog box is displayed. 3. Clear the Scan Enable option and click OK. Broadcasting to Servers You can simultaneously control more than one server in the system to make sure that all selected servers receive identical input.
• Update iKVM Firmware • Enable or disable access to iKVM from front panel • Enable or disable access to iKVM from the Dell CMC console Related Links Updating iKVM Firmware Enabling or Disabling Access to iKVM from Front Panel Viewing iKVM Information and Health Status Enabling Access to iKVM from the Dell CMC Console Enabling or Disabling Access to iKVM from Front Panel You can enable or disable access to iKVM from the front panel using the CMC Web interface or RACADM.
Managing and Monitoring Power 15 The Dell PowerEdge M1000e server enclosure is the most power-efficient modular server enclosure. It is designed to include highly-efficient power supplies and fans, has an optimized layout for the air ro flow more easily through the system, and contains power-optimized components throughout the enclosure.
Viewing Power Budget Status Redundancy Status and Overall Power Health Configuring Power Budget and Redundancy Executing Power Control Operations You can execute the following power control operation for the chassis, servers, and IOMs. Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis.
In the event of a single PSU failure in this configuration, the remaining PSUs in the failing grid are marked as Online. In this state, any of the remaining PSUs can fail without interrupting operation of the system. If a PSU fails, the chassis health is marked non-critical. If the smaller grid cannot support the total chassis power allocations, then AC redundancy status is reported as No Redundancy and Chassis health is displayed as Critical.
Figure 7. No Redundancy with three PSUs in the chassis A PSU failure brings other PSUs out of Standby mode, as needed, to support the chassis power allocations. If you have four PSUs, and require only three, then in the event that one fails, the fourth PSU is brought online. A chassis can have all six PSUs online. When you enable DPSE, the extra PSUs may be placed in Standby mode to increase efficiency and save power. For more information, see Default Redundancy Configuration.
NOTE: In a three PSU configuration, server load may prevent any PSUs from transitioning to Standby • In a Power Supply Redundancy configuration, the enclosure always keeps an additional PSU powered on and marked Online in addition to the PSUs required to power the enclosure. Power utilization is monitored and up to 284 Managing and Monitoring Power four PSUs could be moved to Standby state depending on the overall system load.
No Redundancy Power in excess of what is necessary to power the chassis is available, even on a failure, to continue to power the chassis. CAUTION: The No Redundancy mode uses optimum PSUs when DPSE is enabled for the requirements of the chassis. Failure of a single PSU could cause servers to lose power and data in this mode. Power Budgeting For Hardware Modules CMC offers a power budgeting service that allows you to configure power budget, redundancy, and dynamic power for the chassis.
consumption. Depending on the actual power requirements, the iDRAC power envelope may change over time. iDRAC requests a power step-up only if the servers are fully consuming the allocated power. Under heavy load the performance of the server’s processors may be degraded to ensure power consumption stays lower than the user-configured System Input Power Cap.
to accommodate the higher priority servers. Therefore, after the available power for allocation is exhausted, then CMC reclaims power from lower or equal priority servers until they are at their minimum power level. NOTE: I/O modules, fans, and iKVM (if present) are given the highest priority. CMC reclaims power only from lower priority devices to meet the power needs of a higher priority module or server.
Viewing Power Budget Status You can view the power budget status using the CMC Web interface or RACADM. Viewing Power Budget Status Using CMC Web Interface To view power budget status using CMC Web interface, in the system tree go to Chassis Overview and click Power → Budget Status. The Power Budget Status page displays the system power policy configuration, power budget details, budget allocated for server modules, and chassis power supply details. For more information, see the CMC Online Help.
PSU, CMC evaluates power needs again when the second PSU is removed to determine the firmware response. If power requirements are still not met, CMC may power off the lower priority servers. Limits • CMC does not support automated power-down of a lower priority server to allow power up of a higher priority server; however, you can perform user-initiated power-downs. • Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis.
PSU Configuration Dynamic PSU Engagement Firmware Response No Redundancy Disabled Decrease power to low priority servers, if needed. AC Redundancy Enabled CMC alerts you of loss of AC Redundancy. PSUs in standby mode (if any) are turned on to compensate for power budget lost from the PSU failure or removal. Power Supply Redundancy Enabled CMC alerts you of loss of Power Supply Redundancy. PSUs in standby mode (if any) are turned on to compensate for power budget lost from PSU failure or removal.
You can configure the following: • System Input Power Cap • Redundancy Policy • Server Performance Over Power Redundancy • Enable Dynamic Power Supply Engagement • Disable Chassis Power Button • Allow 110 VAC Operation • Max Power Conservation Mode • Remote Power Logging • Remote Power Logging Interval • Server Based Power Management Related Links Power Conservation and Power Budget Maximum Power Conservation Mode Server Power Reduction to Maintain Power Budget 110V PSUs AC Operation Ser
The system is restored to full performance when the maximum conservation mode is cleared. Server Power Reduction to Maintain Power Budget CMC reduces power allocations of lower priority servers when additional power is needed to maintain the system power consumption within the user-configured System Input Power Cap. For example, Managing and Monitoring Power 297 when a new server is engaged, CMC may decrease power to low priority servers to allow more power for the new server.
External Power Management CMC Power management is optionally controlled by the Power Measure, Mitigate, and Manage Console (PM3). For more information, see the PM3 User’s Guide.
3. – Server Performance Over Power Redundancy – Enable Dynamic Power Supply Engagement – Disable Chassis Power Button – Allow 110 VAC Operation – Max Power Conservation Mode – Enable Remote Power Logging 300 Managing and Monitoring Power – Remote Power Logging Interval Click Apply to save the changes. Configuring Power Budget and Redundancy Using RACADM NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege.
– Enable 110 VAC PSUs: racadm config -g cfgChassisPower -o cfgChassisAllow110VACOperation 1 – Enable Server Performance Over Power Redundancy: racadm config -g cfgChassisPower -o cfgChassisPerformanceOverRedundancy 1 – Disable Server Performance Over Power Redundancy: racadm config -g cfgChassisPower -o cfgChassisPerformanceOverRedundancy 0 – To enable the power remote logging feature, enter the following command: racadm config -g cfgRemoteHosts -o cfgRhostsSyslogPowerLoggingEnabled 1 – To specify
NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. Executing Power Control Operations on the Chassis Using Web Interface To execute power control operations on the chassis using the CMC Web interface: 1. In the system tree, go to Chassis Overview and click Power → Control . The Chassis Power Control page is displayed. 2. Select one of the following power control operations. For information about each option, see the CMC Online Help. 3.
A dialog box appears requesting confirmation. 4. Click OK to perform the power management action (for example, cause the server to reset). Executing Power Control Operations on a Server Using CMC Web Interface To execute power control operation for an individual server using the CMC Web interface: 1. In the system tree, go to Chassis Overview and click Server Overview. 2. Click on the server for which you want to execute the power control operation, and then click the Power tab.
Executing Power Control Operations on IOMs Using RACADM To execute power control operations on an IOM using RACADM, open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m switch- where is a number 1-6 and specifies the IOM (A1, A2, B1, B2, C1, C2), and indicates the operation you want to execute: powercycle or reset.
Troubleshooting and Recovery 16 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.
Subsystem RACADM Command General System/RAC information getsysinfo Session information getssinfo Sensor information getsensorinfo Switches information (IO Module) getioinfo Mezzanine card information (Daughter card) getdcinfo All modules information getmodinfo Power budget information getpbinfo KVM information getkvminfo NIC information (CMC module) getniccfg Redundancy information getredundancymode Trace log information gettracelog RAC event log gettraclog System event log getsel
Additionally the capacity of each side must be enough to support the total power allocations for the chassis to maintain AC redundancy. (For full AC Redundancy operation, ensure that a full PSU configuration of six power supplies is available.) – • • • • Problem: The PSU state is displayed as Failed (No AC), even when an AC cord is connected and the power distribution unit is producing good AC output. – Resolution A: Check and replace the AC cord.
• Problem: The least priority servers lost power after a PSU failure. – • Resolution: This is expected behavior if the enclosure power policy was configured to No Redundancy. To avoid a future power supply failure causing servers to power off, ensure that the chassis has at least four power supplies and is configured for the Power Supply Redundancy policy to prevent PSU failure from impacting server operation.
Viewing Hardware Logs Using CMC Web Interface You can view, save, and clear the hardware log. You can sort the log entries based on Severity, Date/Time, or Description by clicking the column heading. Subsequent clicks on the column headings reverse the sort. To view the hardware logs using CMC Web interface, in the system tree, go to Chassis Overview and click Logs → Hardware Log . The Hardware Log page is displayed.
Using Diagnostic Console You can diagnose issues related to the chassis hardware using CLI commands if you an advanced user or a user under the direction of technical support. NOTE: To modify these settings, you must have Debug Command Administrator privilege. To access the Diagnostic Console using the CMC Web interface: 1. In the system tree, go to Chassis Overview and click Troubleshooting → Diagnostics. The Diagnostic Console page displays. 2. In the Command text box, enter a command and click Submit.
NOTE: The default backup file name contains the Chassis' service tag. This backup file can be used later, to restore the settings and certificates for this chassis only. 3. To restore the chassis configuration, click Choose File, specify the backup file, and click Restore. NOTE: CMC does not reset upon restoring configuration, however CMC services may take some time to effectively impose any changed or new configuration. After successful completion, all current sessions are closed.
For information on how to enter the gettracelog command to review the trace log using the CMC Web interface, see Using Diagnostic Console. Interpreting LED Colors and Blinking Patterns The LEDs on the chassis provide the component status as per the following: • Steadily glowing, green LEDs indicate that the component is powered on. If the green LED is blinking, it indicates a critical but routine event, such as a firmware upload, during which the unit is not operational. It does not indicate a fault.
Component IOM (Pass through) Fan PSU LED Color, Blinking Pattern Meaning Green, blinking Firmware is being uploaded Green, dark Powered off Blue, glowing steadily Normal/stack master Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault/stack slave Green, glowing steadily Powered on Green, blinking Not used Green, dark Powered off Blue, glowing steadily Normal Blue, blinking User-enabled module identifier Amber,
Troubleshooting Non-responsive CMC If you cannot log in to CMC using any of the interfaces (the Web interface, Telnet, SSH, remote RACADM, or serial), you can verify the CMC functionality observing the LEDs on CMC, obtaining recovery information using the DB-9 serial port, or recovering the CMC firmware image. NOTE: It is not possible to log in to the standby CMC using a serial console.
Recovering Firmware Image CMC enters recover mode when a normal CMC operating boot is not possible. In recover mode, a small subset of commands are available that allow you to reprogram the flash devices by uploading the firmware update file, firmimg.cmc. This is the same firmware image file used for normal firmware updates. The recovery process displays its current activity and boots to the CMC OS upon completion.
To perform management actions, a user with Administrator privileges is required. If the administrator account password is forgotten, it can be reset using the PASSWORD_RST jumper on the CMC board. The PASSWORD_RST jumper uses a two-pin connector as shown in the following figure.
Table 39. CMC Password Jumper Settings PASSWORD_RSE T (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 becomes the active CMC, and remains the active CMC until the remaining steps are completed. 4. If the jumpered CMC module is the only CMC, then wait for it to finish rebooting.
17 Using LCD Panel Interface You can use the LCD panel on the chassis to perform configuration and diagnostics, and to obtain status information about the chassis and its contents. The following figure illustrates the LCD panel. The LCD screen displays menus, icons, pictures, and messages. Figure 10.
• • To scroll through options on a screen, use the down and up arrow buttons. To select and save an item on a screen and move to the next screen, use the center button. The up, down, left, and right arrow buttons change the selected menu items or icons on the screen. The selected item is shown with a light blue background or border. When messages displayed on the LCD screen are longer than what fits on the screen, use the left and right arrow buttons to scroll the text left and right.
Graphical Server Status Screen Graphical Module Status Screen Enclosure Menu Screen Module Status Screen Enclosure Status Screen IP Summary Screen Main Menu From the Main menu, you can navigate to one of the following screens: • LCD Setup Menu — select the language to use and the LCD screen that displays when no one is using the LCD. • Server — displays status information for servers. • Enclosure — displays status information for the chassis. Use the up and down arrow buttons to highlight an item.
1. Use the up and down arrow buttons to highlight the screen you want to set to the default. 2. Press the center button. The Accept icon is highlighted. 3. Press the center button again to confirm the change. The Default Screen is displayed. Graphical Server Status Screen The Graphical Server Status screen displays icons for each server installed in the chassis and indicates the general health status for each server.
Use the navigation buttons to highlight the desired item (highlight the Back icon to return to the Main Menu) and press the center button. The selected screen displays. Module Status Screen The Module Status screen displays information and error messages about a module. For messages that can appear on this screen, see LCD Module and Server Status Information and LCD Error Messages. Use the up and down arrow keys to move through messages.
Figure 11. Removing and Installing LCD Module 1 cable cover 2 LCD module 3 ribbon cable 4 hinges (2) 5 screws (2) Table 41. LCD Hardware Troubleshooting Items Symptom Issue Recovery Action Alert screen message CMC Not Responding and LED is blinking amber. Loss of communication from CMC to the LCD front panel. Check that CMC is booting; then, reset CMC using GUI or RACADM commands. Alert screen message CMC Not Responding and LED is solid amber or is off.
• The control panel cable is not connected, or is improperly connected. Reseat cables. LCD screen message No CMC Found. No CMC is present in the chassis. Insert a CMC into the chassis or reseat existing CMC if present. Front Panel LCD Messages This section contains two subsections that list error and status information that is displayed on the front panel LCD. Error messages on the LCD have a format that is similar to the System Event Log (SEL) viewed from the CLI or Web interface.
Severity Message Cause Critical The power supplies are not redundant. Insufficient resources to maintain normal operations. One or more PSU have failed or removed and the system lacks sufficient power to maintain normal operations. This could cause servers to power down. Warning The control panel ambient temperature is greater than the upper warning threshold. Chassis/Enclosure intake temperature exceeded the warning threshold.
Table 47. PSU Status Screens Severity Message Cause Critical Power supply failed. The PSU has failed. Critical The power input for power supply is lost. Loss of AC power or AC cord unplugged. Warning Power supply is operating at 110 volts, Power supply is plug into a 110 volt source. and could cause a circuit breaker fault. Table 48. Server Status Screen Severity Message Cause Warning The system board ambient temperature is less Server temperature is getting cool.
Severity Message Cause Critical Mezz B Status: Add-in Card sensor for Mezz B, install error was asserted. Incorrect Mezzanine card installed for IO fabric. Critical Mezz C Status: Add-in Card sensor for Mezz C, install error was asserted. Incorrect Mezzanine card installed for IO fabric. Critical Drive is removed. Storage Drive was removed. Critical Fault detected on Drive . Storage Drive failed.
Severity Message Cause Critical A PCI parity error was detected on a component at slot . Parity error was detected on the PCI bus. Critical A PCI system error was detected on a PCI error detected by device. component at bus device function . Critical A PCI system error was detected on a component at slot . PCI error detected by device. Critical Persistent correctable memory error logging disabled for a memory device at location .
Table 49. CMC Status Item Description Example: CMC1, CMC2 Name/Location. No Errors If no error occurs then “No Errors” is displayed, else lists error messages. Firmware Version Only displays on an active CMC. Displays Standby for the standby CMC. IP4 Displays current IPv4 enabled state only on an active CMC. IP4 Address: Only displays if IPv4 is enabled only on an active CMC.
Table 52. PSU Status Item Description Name/Location Example: PSU1, PSU2, etc. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. Status Offline, Online, or Standby. Maximum Wattage Maximum Wattage that PSU can supply to the system. Table 53. IOM Status Item Description Name/Location Example: IOM A1, IOM B1. etc.
Table 55. Server Status Item Description Example: Server 1, Server 2, etc. Name/Location. No Errors If there are no errors, then No Errors is displayed; otherwise error messages are listed. The critical errors are listed first, and then the warnings. For more information, see "LCD Error Messages". Slot Name Chassis slot name. For example, SLOT-01. NOTE: You can set this table through the CMC CLI or Web GUI. Name Name of the server, which the user can set through Dell OpenManage.
Frequently Asked Questions 18 This section lists the frequently asked questions for the following: • RACADM • Managing and Recovering a Remote System • Active Directory • FlexAddress and FlexAddressPlus • iKVM • 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 address this security concern, upload a CMC server certificate issued to the IP address of CMC. When generating the certificate signing request (CSR) to be used for issuing the certificate, ensure that the common name (CN) of the CSR matches the IP address of CMC (for example, 192.168.0.120) or the registered DNS CMC name. To ensure that the CSR matches the registered DNS CMC name: 1. In the System tree, click Chassis Overview. 2. Click the Network tab, and then click Network.
Active Directory Does Active Directory support CMC login across multiple trees? 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.
No activation or modifications to the card should occur. The card is ignored by CMC.
How can a SD card be recovered if the SD card was not in the chassis when the deactivation command was executed on the FlexAddress? The issue is that the SD card cannot be used to install FlexAddress on another chassis if it was not in CMC when FlexAddress was deactivated. To recover use of the card, insert the card back into a CMC in the chassis that it is bound to, reinstall FlexAddress, and then deactivate FlexAddress, again.
The iKVM is tiered through the ACI port to an external KVM switch, but all of the entries for the ACI connections are unavailable. All of the states are showing a yellow dot in the OSCAR interface. The front panel connection is enabled and has a monitor connected. Because the front panel has precedence over all other iKVM connections, the ACI and rear panel connectors are disabled.
