Dell Chassis Management Controller Version 6.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview........................................................................................................................ 14 What is new in this release................................................................................................................................................ 14 Key Features.....................................................................................................................................................................
Setting Date and Time on CMC........................................................................................................................................34 Setting Date and Time on CMC Using CMC Web Interface........................................................................................34 Setting Date and Time on CMC Using RACADM........................................................................................................
Updating IOM Coprocessor Using CMC Web Interface..............................................................................................48 Updating IOM Firmware Using RACADM................................................................................................................... 48 Updating Server iDRAC Firmware Using Web Interface....................................................................................................49 Updating Server iDRAC Firmware Using RACADM..................
Configuring CMC Network and Login Security Settings................................................................................................... 72 Configuring IP Range Attributes Using CMC Web Interface ...................................................................................... 72 Configuring IP Range Attributes Using RACADM....................................................................................................... 73 Configuring Virtual LAN Tag Properties for CMC...............
Parsing Rules..............................................................................................................................................................89 Configuring Multiple CMCs through RACADM Using Configuration File...........................................................................89 Creating a CMC Configuration File.............................................................................................................................90 Parsing Rules.....................
Importing Boot Identity Profiles................................................................................................................................. 110 Exporting Boot Identity Profiles................................................................................................................................. 110 Deleting Boot Identity Profiles...................................................................................................................................
Configuring CMC SSO Or Smart Card Login For Active Directory Users Using Web Interface................................. 143 Configuring CMC SSO Login Or Smart Card Login For Active Directory Users Using RACADM............................... 144 11 Configuring CMC to Use Command Line Consoles......................................................145 CMC Command Line Console Features..........................................................................................................................
Monitoring IOM Health................................................................................................................................................... 168 Viewing Input Output Module Uplink and Downlink Status Using Web Interface.............................................................168 Viewing Input Output Module FCoE Session Information Using Web Interface...............................................................
Managing iKVM From CMC............................................................................................................................................188 Enabling or Disabling Access to iKVM from Front Panel............................................................................................188 Enabling Access to iKVM from the Dell CMC Console.............................................................................................. 189 15 Managing and Monitoring Power................
Gathering Configuration Information, Chassis Status, and Logs Using RACDUMP.........................................................208 Supported Interfaces............................................................................................................................................... 208 Downloading SNMP Management Information Base File......................................................................................... 209 First Steps to Troubleshoot a Remote System......................
Single Sign On................................................................................................................................................................239 19 Use Case Scenarios................................................................................................... 240 Chassis Basic Configuration and Firmware Update.........................................................................................................
1 Overview The Dell Chassis Management Controller (CMC) for Dell EMC PowerEdge M1000e chassis is a systems management hardware and software solution for managing multiple Dell server chassis. It is a hot-pluggable card that is installed 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.
• Transferring CMC dumplogs to iDRAC. Key Features The CMC features are grouped into management and security features. Management Features The CMC provides the following management features: • Redundant CMC environment. • Dynamic Domain Name System (DDNS) registration for IPv4 and IPv6. • Remote system management and monitoring using SNMP, a Web interface, iKVM, Telnet, or SSH connection. • Monitoring — Provides access to system information and status of components.
Security Features CMC provides the following security features: • Password-level security management — Prevents unauthorized access to a remote system. • Centralized user authentication through: – Active Directory using Standard Schema or an Extended Schema (optional.) – Hardware-stored user IDs and passwords. • Role-based authority — Enables an administrator to configure specific privileges for each user. • User ID and password configuration through the Web interface.
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 2. 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 3.
Servers Minimum version of CMC PowerEdge M910 CMC 2.3 PowerEdge M915 CMC 3.2 PowerEdge M420 CMC 4.1 PowerEdge M520 CMC 4.0 PowerEdge M620 CMC 4.0 PowerEdge M820 CMC 4.11 PowerEdge PSM4110 CMC 4.11 PowerEdge M630 CMC 5.0 PowerEdge M830 CMC 5.0 PowerEdge M640 CMC 6.0 The following table lists the minimum CMC version required to enable the listed IOMs. Table 5. Minimum CMC Version for IOMs IOM Switches Minimum version of CMC PowerConnect M6220 CMC 1.0 PowerConnect M6348 CMC 2.
IOM Switches Minimum version of CMC Brocade M6505 CMC 4.3 Cisco Nexus B22DELL CMC 4.3 Latest Firmware Versions for This Release The following table lists the latest firmware versions for BIOS, iDRAC, and Lifecycle Controller that support the servers listed: Table 6. Latest Firmware Versions for BIOS, iDRAC, and Lifecycle Controller Servers BIOS iDRAC Lifecycle Controller PowerEdge M600 2.4.0 1.65 Not Applicable PowerEdge M605 5.4.1 1.65 Not Applicable PowerEdge M805 2.3.3 1.
Connection Serial port Features • Support for Telnet/SSH command console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands. • Support for serial console and RACADM CLI commands including system boot, reset, power-on, and shutdown commands. Support for binary interchange for applications designed to communicate with a binary protocol to a particular type of IOM.
Supported Management Console Applications The CMC supports integration with Dell OpenManage IT Assistant. For more information, see the IT Assistant documentation set available on the Dell Support Web site at dell.com/support/manuals. 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.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page. 4. Select the appropriate service or support link based on your need.
2 Installing and Setting Up CMC This section provides information about how to install the PowerEdge M1000e Chassis Management Controller (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.
10. Connect to each iDRAC and provide final configuration of iDRAC. Default user name is root and password is calvin. 11. Connect to each I/O module through the Web browser and provide final configuration of the I/O module. 12. Turn on the servers and install the operating system. Basic CMC Network Connection CAUTION: Connecting the STK port to the management network can have unpredictable results. Cabling GB and STK to the same network (broadcast domain) can cause a broadcast storm.
Figure 2. Daisy-chained CMC network 1 Management Network 2 Standby CMC 3 Active CMC The following figures provide examples of incorrect cabling of CMC. Figure 3. Incorrect cabling for CMC network — 2 CMCs Figure 4.
Figure 5. Incorrect cabling for CMC network — 2 CMCs 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.
4. Navigate to the SYSMGMT/ManagementStation/linux/rac directory. To install the RAC software, type the following command: rpm -ivh *.rpm 5. For help on the RACADM command, type racadm help after you run the previous commands. For more information about RACADM, see Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
6. In the Exceptions section, add the addresses for CMCs and iDRACs on the management network as a semicolon-separated list. You can use DNS names and wildcards in your entries. Mozilla FireFox To edit the exception list in Mozilla Firefox version 3.0: 1. Start Mozilla Firefox. 2. Click Tools → Options (for systems running Windows) or click Edit → Preferences (for systems running Linux). 3. Click Advanced and then click the Network tab. 4. Click Settings. 5.
Setting Up Initial Access to CMC To manage CMC remotely, connect CMC to your management network and then configure CMC network settings. NOTE: To manage the M1000e solution, it must be connected to your management network. For information to configure CMC network settings, see Configuring Initial CMC Network. This initial configuration assigns the TCP/IP networking parameters that enable access to CMC.
Configuring CMC Network Using LCD Panel Interface NOTE: The option to configure CMC using the LCD panel is available only until CMC is deployed or the default password is changed. If the password is not changed, you can continue to use the LCD to reset the configurations of the CMC causing a possible security risk. The LCD panel is on the bottom-left corner on the front of the chassis. To set up a network using the LCD panel interface: 1. Press the chassis power button to turn it on.
• When you have confirmed the accuracy of the settings you entered, press the center button. The Register DNS? screen appears. NOTE: If the Dynamic Host Configuration Protocol (DHCP) mode is selected for CMC IP configuration, then DNS registration is also enabled by default. 8. If you selected DHCP in the previous step, go to step 10. To register your DNS server’s IP address, press the center button to proceed. If you have no DNS, press the right arrow key.
NOTE: After you have completed network set up through the LCD Configuration Wizard, the Wizard is no longer available. Interfaces and Protocols to Access CMC After you have configured CMC network settings, you can remotely access CMC using various interfaces. The following table lists the interfaces that you can use to remotely access CMC. NOTE: Since telnet is not as secure as the other interfaces, it is disabled by default. Enable Telnet using Web, ssh, or remote RACADM.
Interface Description The CMC WSMan 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.org/standards/profiles/ WSMan release notes or Read Me file. www.wbemsolutions.com/ws_management.
Setting Date and Time on CMC You can set the date and time manually, or you can synchronize the date and time with a Network Time Protocol (NTP) server. Setting Date and Time on CMC Using CMC Web Interface To set the date and time on CMC using the CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Setup → Date/Time. The Date/Time page is displayed. 2.
• 0 — not blinking (default) • 1 — blinking Configuring CMC Properties You can configure CMC properties such as power budgeting, network settings, users, and SNMP and email alerts using the Web interface or RACADM. Configuring iDRAC Launch Method Using CMC Web Interface To configure the iDRAC launch method from the General Chassis Settings page: 1. In the system tree, click Chassis Overview → Setup. The General Chassis Settings page is displayed. 2.
• To enable user blocking feature, use: racadm config -g cfgRacTuning -o cfgRacTuneUserBlkEnable <0|1> • To enable IP blocking feature, use: racadm config –g cfgRacTuning –o cfgRacTuneIPBlkEnable <0|1> • To specify the number of login attempts, use: racadm config –g cfgRacTuning –o cfgRacTuneIpBlkFailCount • To specify the time span within which, lockout fail count failures must occur, use: racadm config –g cfgRacTuning –o cfgRacTuneIpBlkFailWindow • To specify value for lockout penalty time, use:
• You cannot turn on newly installed blades. • You cannot access existing blades remotely. • Chassis cooling fans run at 100% for thermal protection of the components. • Blade performance reduces to limit power consumption until management of the CMC is restored. The following are some of the conditions that can result in CMC management loss: • CMC removal — Chassis management resumes after replacing CMC, or after failover to standby CMC.
3 Logging In to CMC 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.
NOTE: • For added security, it is strongly recommended that you change the default password of the root account during initial setup. • When Certificate Validation is enabled, Fully Qualified Domain Name (FQDN) of the system should be provided. If certificate validation is enabled and IP address is provided for the Domain Controller, then the login is not successful. CMC does not support extended ASCII characters, such as ß, å, é, ü, or other characters used primarily in non-English languages.
• Upload a Trusted Certificate Authority (CA) certificate (CA-signed Active Directory certificate) to CMC. • Configure the DNS server. • Enable Active Directory login. • Enable Smart Card login. 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
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.
Related link Configure Public Key Authentication over SSH Multiple CMC Sessions The following table provides the list of multiple CMC sessions that are possible using the various interfaces. Table 9.
Changing Default Login Password Using RACADM To change the password, run the following RACADM command: racadm config –g cfgUserAdmin –o cfgUserAdminPassword –i where, is a value from 1 to 16 (indicates the user account) and is the new user–defined password. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
4 Updating Firmware 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.
For more information on the update sequence for M1000e chassis, see the CMC Firmware 5.0 Release Notes on support site. Signed CMC Firmware Image For M1000e CMC version 5.0 and later, the firmware includes a signature. The CMC firmware performs a signature verification step to ensure the authenticity of the uploaded firmware. The firmware update process is successful only if the firmware image is authenticated by CMC to be a valid image from the service provider and has not been altered.
NOTE: CMC firmware update or roll back is supported only for the firmware versions 3.10, 3.20, 3.21, 4.0, 4.10, 4.11, 4.30, 4.31, 4.45, 4.5, 5.0, and later. For any version other than these, first update to any of these versions, and then update to the required version. The Active CMC resets and becomes temporarily unavailable after the firmware has been uploaded successfully. If a standby CMC is present, the standby and active roles swap. The standby CMC becomes the active CMC.
• Do not click the Refresh icon or navigate to another page during the file transfer. • To cancel the process, click Cancel File Transfer and Update. This option is available only during file transfer. • The Update State field displays the firmware update status. NOTE: The update may take several minutes for CMC. 6. For a standby CMC, when the update is complete the Update State field displays Done.
Updating iKVM Firmware Using RACADM To update iKVM firmware using RACADM, use the fwupdate subcommand. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Updating IOM Infrastructure Device Firmware By performing this update, the firmware for a component of the IOM device is updated, but not the firmware of the IOM device itself; the component is the interface circuitry between the IOM device and CMC.
Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server using in the CMC Web interface: 1. Go to any of the following pages: • Chassis Overview → Update • Chassis Overview → Chassis Controller → Update • Chassis Overview → I/O Module Overview → Update • Chassis Overview → iKVM → Update The Firmware Update page is displayed. You can also update server iDRAC firmware at Chassis Overview → Server Overview → Update .
NOTE: • While selecting the individual server components for update, make sure that there are no dependencies between the selected components. If not, selecting some components that have dependencies on other components for update may cause the server to stop functioning abruptly. • Make sure to update the server components in the recommended order. If not, the process of component firmware update may become unsuccessful.
• Other components NOTE: When you update the firmware versions for all the server components at one time, the update sequence is handled by Lifecycle Controller. Supported Firmware Versions for Server Component Update The following section provides the supported component versions for CMC firmware update and Server Component Update. The following table lists the supported firmware versions for server components when CMC Firmware is updated from 5.2 to 6.
Platform M620 M820 M630 M830 Server Component Current Component Version (N-1 Version) Lifecycle Controller 2.41.40.40 Diagnostics 4225A2 BIOS 2.32 iDRAC 2.41.40.40 Lifecycle Controller 2.41.40.40 Diagnostics 4231A0 BIOS 2.5.2 NIC 7.8.15 iDRAC 2.41.40.40 Lifecycle Controller 2.41.40.40 Diagnostics 4231A0 BIOS 2.3.2 iDRAC 2.41.40.40 Lifecycle Controller 2.41.40.40 Diagnostics 4239.44 BIOS 2.4.2 iDRAC 2.41.40.40 Lifecycle Controller 2.41.40.
Platform M910 M710HD M420 M520 M620 M820 M630 M830 M640 Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) BIOS 6.3.0 6.4.0 iDRAC 3.80 A00 3.85 A00 Lifecycle Controller 1.6.5.12 A00 1.7.5.4 Diagnostics 5158A3 5162A0 BIOS 2.9.0 2.10.0 iDRAC 3.80 A00 3.85 A00 Lifecycle Controller 1.6.5.12 A00 1.7.5.4 Diagnostics 5158A3 5162A0 BIOS 7.0.0 8.0.0 NIC 7.8.15 20.6.18 iDRAC 2.41.40.40 2.50.50.50 Lifecycle Controller 2.41.40.
Platform Server Component Previous Component Version (N-1 Version) Updated Component Version (N Version) Diagnostics Not Applicable 4301.13 (YFXV5) BIOS Not Applicable 1.0.0 Enabling Lifecycle Controller You can enable the Lifecycle Controller service during the server boot process: • For iDRAC 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 System Services.
If the update file image size is greater, the job status indicates that the download has failed. If multiple server component updates are attempted on a server, the combined size of all the firmware update files may also exceed 48MB. In such a case, one of the component updates fails as its update file is truncated. To update multiple components on a server, it is recommended to update the Lifecycle Controller and 32-Bit Diagnostics components together first.
Few devices such as Network Interface Controllers (NICs) and RAID Controllers contain many types and models. The update selection logic automatically filters the relevant device type or model based on the initially selected devices. The primary reason for this automatic filtering behavior is that only one firmware image file for the category can be specified. NOTE: The update size limitation of either a single DUP or combined DUPs can be ignored if the Extended Storage feature is installed and enabled.
5. Click Check for Updates to view the firmware updates available in the network share. The Component/Device Firmware Inventory section displays the current firmware versions of the components and devices across all the servers present in the chassis and firmware versions of the DUPs available in the Network Share. 6. In the Component/Device Firmware Inventory section, select the check box against Select/Deselect All to select all the supported servers.
• Network I/F Controller • RAID Controller 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.
• Options to perform the various Lifecycle Controller operations such as Update, Rollback, Reinstall, and Job Deletion are available. 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. The following table displays the component and devices information on the server: Table 13.
Configuring Network Share Using CMC Web Interface To configure or edit the Network Share location or credentials: 1. In the CMC Web interface, in the system tree, go to Server Overview and then click Network Share. The Edit Network Share page is displayed. 2.
operation has been submitted for scheduling, ensure that the confirmation popup message indicating that the operation has been successfully scheduled is acknowledged.
3. In the Component/Device Update Filter section, filter the component or device (optional). For more information see Filtering Components for Firmware Updates Using CMC Web Interface. 4. In the Job Status column, a check box displayed next to the job status indicates that a Lifecycle Controller job is in progress and currently is in the indicated state. You can select the job for a deletion operation. 5. Click Job Deletion. The jobs are deleted for the selected components or devices.
5 Viewing Chassis Information and Monitoring Chassis and Component Health 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 its
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. Empty positions are shown with a charcoal gray background. The component icon visually indicates the state of the component. Other components display icons that visually represent the physical component.
NOTE: In Multi-Chassis Management (MCM), all the Quick Links associated with the servers are not displayed. Table 15.
Viewing Chassis Summary You can view the summary of the installed components in the chassis. To view the chassis summary information, in the CMC Web interface, go to Chassis Overview → Properties → Summary. The Chassis Summary page is displayed. For more information, see the CMC Online Help. Viewing Chassis Controller Information and Status To view the chassis controller information and status, in the CMC Web interface, go to Chassis Overview → Chassis Controller → Properties → Status.
The Storage Array Status page provides the health status and properties of the storage array. For more information, see the CMC Online Help. Viewing Information and Health Status of All IOMs To view health status of the 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.
NOTE: In the event of a communication failure between CMC and the fan unit, CMC cannot obtain or display health status for the fan unit. For more information, see the CMC Online Help. Viewing iKVM Information and Health Status The local access KVM module for the Dell M1000e server chassis is called the Avocent Integrated KVM Switch Module, or iKVM. To view the health status of the iKVMs associated with the chassis, do any of the following: 1. Go to Chassis Overview → Properties → Health.
6 Configuring CMC 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.
When IPv6 is enabled at boot time, three router solicitations are sent every four seconds. If external network switches are running the Spanning Tree Protocol (SPT), the external switch ports may be blocked for more than twelve seconds in which the IPv6 router solicitations are sent. In such cases, there may be a period when IPv6 connectivity is limited, until router advertisements are gratuitously sent by the IPv6 routers.
For an IPv4 network, to disable DHCP and specify static CMC IP address, gateway, and subnet mask, type: racadm racadm racadm racadm config config config config -g -g -g -g cfgLanNetworking cfgLanNetworking cfgLanNetworking cfgLanNetworking -o -o -o -o cfgNicUseDHCP 0 cfgNicIpAddress cfgNicGateway cfgNicNetmask By default, for IPv6, the CMC requests and obtains a CMC IP address from the IPv6 Autoconfiguration mechanism automatically.
NOTE: The following settings are valid only if you have registered the CMC on the DNS server by setting cfgDNSRegisterRac to 1. • CMC Name — By default, the CMC name on the DNS server is cmc-. To change the CMC name on the DNS server, type: racadm config -g cfgLanNetworking -o cfgDNSRacName where is a string of up to 63 alphanumeric characters and hyphens. For example: cmc-1, d-345. NOTE: If a DNS Domain name is not specified, then the maximum number of characters is 63.
To configure the IP range attributes using CMC Web interface: 1. In the system tree, go to Chassis Overview and click Network → Network. The Network Configuration page is displayed. 2. In the IPv4 Settings section, click Advanced Settings. The Log in Security page is displayed. Alternatively, to access the Log in Security page, in the system tree, go to Chassis Overview, click Security → Log in. 3. To enable the IP range checking feature, in the IP Range section, select the IP Range Enabled option. 4.
You can also access this page from the Chassis Overview → Servers → Setup → VLAN subtab. Configuring Virtual LAN Tag Properties for CMC Using RACADM 1. Enable the VLAN capabilities of the external chassis management network: racadm config -g cfgLanNetworking -o cfgNicVLanEnable 1 2. Specify the VLAN ID for the external chassis management network: racadm config -g cfgLanNetworking -o cfgNicVlanID The valid values for are 1– 4000 and 4021– 4094. Default is 1.
• • • • • • • • Web GUI RACADM WSMan SSH v2 SMTP Kerberos NTP Client NFS NOTE: SNMP is not FIPS-compliant. In FIPS mode, all SNMP features except Message Digest algorithm version 5 (MD5) authentication work. Enabling FIPS Mode Using CMC Web Interface To enable FIPS: 1. In the left pane, click Chassis Overview. The Chassis Health page is displayed. 2. On the menu bar, click Network. The Network Configuration page is displayed. 3.
If the Web server resets, wait at least one minute for the services to become available again. A Web server reset usually happens as a result of any of the following events: • Network configuration or network security properties are changed through the CMC Web user interface or RACADM. • Web Server port configuration is changed through the Web user interface or RACADM. • CMC is reset. • A new SSL server certificate is uploaded.
# cfgSsnMgtTelnetActiveSessions=N/A # cfgSsnMgtTelnetTimeout=N/A Configuring CMC Extended Storage Card You can enable or repair the optional Removable Flash Media for use as an extended non-volatile storage. Some CMC features depend on extended nonvolatile storage for their operation. To enable or repair the Removable Flash Media using the CMC Web interface: 1. In the System tree, go to Chassis Overview, and then click Chassis Controller → Flash Media. The Removable Flash Media page is displayed. 2.
Related link Adding Members to Chassis Group Removing a Member from the Leader Disbanding a Chassis Group Disabling an Individual Member at the Member Chassis Launching a Member Chassis’s or Server’s Web page Propagating Leader Chassis Properties to Member Chassis Adding Members to Chassis Group After the Chassis Group is setup, you can add members to the group: 1. Login with chassis administrator privileges to the leader chassis. 2. Select the Lead chassis in the tree. 3.
3. Click Setup → Group Administration. 4. In the Chassis Group page, under Role, select None, and then click Apply. The lead chassis then communicates to all the members that they have been removed from the group. Finally the lead chassis discontinues its role. It can now be assigned as a member or a leader of another group. The member chassis may not receive the message, if a network issue prevents contact between the leader and the member.
6. Click Save. If On-Change Propagation is selected, the member chassis take on the properties of the leader. If Manual Propagation is selected, click Propagate whenever you want to propagate the chosen settings to member chassis. For more information on Propagation of leader chassis properties to member chassis, see the CMC Online Help.
Operating System Microsoft Windows Server 2012, Standard x64 Edition NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Model PowerEdgeM630 Service Tag 1PB8VF2 Total System Memory 4.0 GB # of CPUs 2 NOTE: Requires CMC 5.0 (or higher). NOTE: Requires CMC 5.0 (or higher). CPU Info Intel (R) Xeon (R) CPU E5–2690 v3@2.60 GHz Data Format The inventory report is generated in a .
The Firmware View Filter section displays the server inventory for the selected chassis and the firmware versions of all the server components. Viewing Selected Server Component Firmware Versions Using Web Interface To view the firmware versions of selected server components using CMC Web interface: 1. In the system tree, select Group. Click Properties → Firmware Version. The Chassis Group Firmware Version page displays all the chassis in the group. 2.
• Allow the client to authenticate itself to the server. • Allow both systems to establish an encrypted connection. This encryption process provides a high level of data protection. CMC employs the 128-bit SSL encryption standard, the most secure form of encryption generally available for Internet browsers in North America. The CMC Web server includes a Dell self-signed SSL digital certificate (Server ID).
CAUTION: When a new CSR is generated, it overwrites any previous CSR on CMC. If a pending CSR is overwritten before its server certificate is granted from a certificate authority, CMC does not accept the server certificate because the information it uses to authenticate the certificate has been lost. Take caution when generating a CSR to prevent overwriting any pending CSR. Generating a New Certificate Signing Request Using Web Interface To generate a CSR using the CMC Web interface: 1.
The Web server certificate is an essential component used by the SSL encryption process. It authenticates itself to an SSL-enabled client, and allows the client to authenticate itself to the server, thereby enabling both the systems to establish an encrypted connection. NOTE: To upload a Web server key and server certificate, you must have Chassis Configuration Administrator privileges.
• Apply, edit, delete, or export a copy of the profiles stored on the network share. Saving Chassis Configuration You can save the current chassis configuration to an XML file on a network share or local management station. The configurations include all the chassis properties that can be modified using the CMC web interface and RACADM commands. You can also use the XML file that is saved to restore the configuration on the same chassis or to configure other chassis.
Viewing Stored Chassis Configuration Profiles To view the chassis configuration profiles stored on the network share, go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles → Stored Profiles section, select the profile and click View in the View Profile column. The View Settings page is displayed. For more information on the displayed settings, see the CMC Online Help.
Deleting Chassis Configuration Profiles You can delete a chassis configuration profile that is stored on the network share. To delete a chassis configuration profile, perform the following tasks: 1. Go to the Chassis Configuration Profiles page. In the Chassis Configuration Profiles → Stored Profiles section, select the required profile and then click Delete Profile. 2. Click OK to delete the selected profile.
1. To import the chassis configuration profiles from CIFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml –l // xx.xx.xx.xx/PATH –u USERNAME –p PASSWORD 2. To import the chassis configuration profiles from NFS network share, type the following: racadm –r xx.xx.xx.xx –u USERNAMECMC –p PASSWORDCMC set –f clone.xml –t xml –l xx.xx.xx.
4. Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5. Reset the target CMC that was configured. At the command prompt, type: racadm reset The getconfig -f myfile.cfg subcommand (step 1) requests the CMC configuration for the active CMC and generates the myfile.cfg file. If required, you can rename the file or save it to a different location.
Related link Parsing Rules 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 .
This is the list of the indexed groups that exhibit this behavior and their corresponding key properties: – – – – – cfgUserAdmin — cfgUserAdminUserName cfgEmailAlert — cfgEmailAlertAddress cfgTraps — cfgTrapsAlertDestIPAddr cfgStandardSchema — cfgSSADRoleGroupName cfgServerInfo — cfgServerBmcMacAddress Modifying the CMC IP Address When you modify the CMC IP address in the configuration file, remove all unnecessary = entries.
For more information about these commands, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide available at dell.com/support/manuals. Configuring Enhanced Cooling Mode for Fans The Enhanced Cooling Mode (ECM) feature provides additional cooling support using the third generation M1000e fans. The Enhanced Cooling Mode (ECM) for fans is available only when all nine fan slots are populated with the new third generation M1000e fans.
An operation successful message is displayed after the ECM option is successfully enabled or disabled. The ECM mode does not get enabled if: • The extra power required for supported fans is not available. • Any of the fans in the chassis does not support ECM. • MPCM is already enabled. An alert message with the reason for ECM not getting enabled is displayed . NOTE: If you try to enable MPCM when ECM is enabled, the ECM mode changes to enabled but unsupported state.
7 Configuring Server You can do the following on 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.
To edit a slot name using the CMC Web interface: 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 host name of the server as slot name, select Use Host Name for Slot Name option. This option replaces the static slot names with the host names (or system names) of the server, if it is available.
Setting Description • • Server Profile Only— Select this option to apply server profile assigned when a new server is inserted in the chassis. Quick Deploy and Server Profile — Select this option to first apply the iDRAC network settings, and then to apply the server profile assigned when a new server is inserted in the chassis.
Setting Description NOTE: The subnet mask and the gateway are not incremented like the IP address. For example, if the starting IP address is 192.168.0.250 and the subnet mask is 255.255.0.0 then the QuickDeploy IP address for slot 15 is 192.168.0.265.
The following figure shows the QuickDeploy IP addresses assignment to the servers when there are 16 half height severs in a M1000e chassis: The following figure shows the QuickDeploy IP addresses assignment to the servers when there are 32 quarter height severs in a M1000e chassis: Configuring Reserved QuickDeploy IP Addresses Using RACADM To modify the number of static IP addresses allocated for servers on the chassis using RACADM, use the following command: racadm deploy –q -n where is the
• cfgLanNetworking • cfgIPv6LanNetworking • cfgRacTuning • cfgRemoteHosts • cfgSerial • cfgSessionManagement For more information on the property default values and ranges, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Configuring iDRAC VLAN Tag Settings VLANs are used to allow multiple virtual LANs to co-exist on the same physical network cable and to segregate the network traffic for security or load management purposes.
Setting First Boot Device You can specify the CMC first boot device for each server. This may not be the actual first boot device for the server or even represent a device present in that server; instead it represents a device sent by CMC to the server and used as its first boot device for that server. You can set the default boot device and set a one-time boot device so that you can boot an image to perform tasks such as running diagnostics or reinstalling an operating system.
3. If you want the server to boot from the selected device every time it boots, clear the Boot Once option for the server. If you want the server to boot from the selected device only on the next boot cycle, select the Boot Once option for the server. 4. Click Apply to save the settings.
• The file is selected as the first boot device for the servers. • The server is restarted. • Power is applied to the server if the server is turned off. Configuring Profile Settings Using Server Configuration Replication The server configurations replicating feature allows you to apply all profile settings from a specified server to one or more servers. Profile settings that can be replicated are those profile settings which can be modified and are intended to be replicated across servers.
Related link Accessing Server Profiles Page Adding or Saving Profile Applying Profile Viewing Profile Settings Viewing Profile Log Completion Status, Log View, and Troubleshooting Accessing Server Profiles Page You can add, manage, and apply server profiles to one or more servers using the Server Profiles page. To access the Server Profiles page using the CMC Web interface, in the system tree, go to Chassis Overview → Server Overview. Click Setup → Profiles. The Server Profiles page is displayed.
Applying Profile Server cloning is possible only when server profiles are available as stored profiles in the nonvolatile media on the CMC or stored on the remote share. To initiate a server configuration 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 servers: 1. Go to the Server Profiles page.
• Local or Network Share if the source file is on an SD card. NOTE: The Network Share option is enabled and the details are displayed in the Stored Profiles section only if the network share is mounted and is accessible. If the Network Share is not connected, configure the Network Share for the chassis. To configure the Network Share, click Edit in the Stored Profiles section. For more information, see Configuring Network Share Using CMC Web Interface.
• 13th generation servers —After rebooting the server, when prompted, press F10 to access Lifecycle Controller. Go to the Hardware Inventory page by selecting Hardware Configuration → Hardware Inventory. On the Hardware Inventory page, click Collect System Inventory on Restart. Related link Accessing Server Profiles Page Viewing Stored Profile Settings To view profile settings of server profiles stored on the CMC nonvolatile media (SD Card) or on a network share, go to the Server Profiles page.
3. Click Assign Profile. The profile is assigned to the selected slots NOTE: • A slot that does not have any profile assigned to it is indicated by the term “No Profile Selected” that appears in the select box.
Saving Boot Identity Profiles You can save boot identity profiles in the CMC network share. Number of profiles that you can store depends on the availability of MAC addresses. For more information, see Configuring Network Share Using CMC Web Interface. For Emulex Fibre Channel (FC) cards, the Enable/Disable Boot From SAN attribute in the Option ROM is disabled by default. Enable the attribute in the Option ROM and apply the boot identify profile to the server for booting from SAN.
NOTE: To perform server configuration replication operations on the server, the CSIOR option must be enabled for the servers. If CSIOR option is disabled, a warning message is displayed that CSIOR is not enabled for the server. To complete the server configuration replication operation, enable the CSIOR option on the server. 4. Click OK to apply the boot identity profile to the selected server. The selected profile is applied to the server and the server is rebooted immediately.
To delete a stored profile, perform the following tasks:: 1. Go to the Server Profiles page. In the Boot Identity Profiles → Stored Profiles section, select the required profile, and then click Delete Profile. A warning message is displayed indicating that deleting a profile would delete the selected profile permanently. 2. Click OK to delete the selected profile. For more information, see the CMC Online Help.
For more information, see the CMC Online Help. Removing MAC Addresses You can remove a range of MAC addresses from the network share by using the Remove MAC Addresses option available in the CMC web interface. NOTE: You cannot remove MAC addresses if they are active on the node or are assigned to a profile. To remove MAC addresses from the network share: 1. Go to the Server Profiles page. In the Boot Identity Profiles → Manage Virtual MAC Address Pool section, click Remove MAC Addresses. 2.
In MCM, while launching the iDRAC web interface from a member chassis, the user credentials of the leader and member chassis must be the same. Else, the current member chassis session is aborted and the member chassis login page is displayed. Related link Launching iDRAC From Servers Status Page Launching iDRAC from Server Status Page Launching iDRAC From Servers Status Page To launch the iDRAC management console from the Servers Status page: 1. In the system tree, click Server Overview.
Launching Remote Console from Servers Status Page To launch a remote console from the Servers Status page: 1. In the system tree, go to Server Overview, and then click Properties → Status. The Servers Status page is displayed. 2. 114 Click Launch Remote Console for the required server.
8 Configuring CMC To Send Alerts 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 (email 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.
Related link Configuring SNMP Trap Alert Destinations Configuring Email Alert Settings Configuring SNMP Trap Alert Destinations You can configure the IPv6 or IPv4 addresses to receive the SNMP traps. Configuring SNMP Trap Alert Destinations Using CMC Web Interface To configure IPv4 or IPv6 alert destination settings using CMC Web interface: 1. In the system tree, go to Chassis Overview, and then click Alerts → Trap Settings. The Chassis Event Alert Destinations page is displayed. 2.
Table 19. Event Traps Filter Masks 4.
NOTE: CMC uses a default SNMP community string as public. To ensure higher security, it is recommended to change the default community string and set a value which is not blank. You can configure up to four destinations to receive traps alerts. To add more destinations, repeat steps 2–6. NOTE: The commands in steps 2–6 overwrites any existing settings configured for the index specified (1–4). To determine whether an index has previously configured values, type: racadm getconfig -g cfgTraps -i .
4. Enable email alert generation: racadm config -g cfgEmailAlert -o cfgEmailAlertEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destination email addresses. 5. Specify a destination email address to receive the email alerts: racadm config -g cfgEmailAlert -o cfgEmailAlertAddress -i 6.
9 Configuring User Accounts and Privileges You can setup user accounts with specific privileges (role-based authority) to manage your system with CMC and maintain system security. By default CMC is configured with a 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 When a server is moved to a different chassis, it inherits the slot name and priority assigned to the slot it occupies in the new chassis. Its previous slot name and priority remain with the previous chassis. NOTE: CMC users with the Chassis Configuration Administrator privilege can configure power settings. However, the Chassis Control Administrator privilege is needed to perform chassis power operations, including power on, power off, and power cycle.
Privilege Description • • • • • Power on Power off Power cycle Graceful shutdown Server Reboot Test Alert User User can send test alert messages. Debug Command Administrator User can execute system diagnostic commands. Fabric A Administrator User can set and configure the Fabric A IOM, which resides in either slot A1 or slot A2 of the I/O slots. Fabric B Administrator User can set and configure the Fabric B IOM, which resides in either slot B1 or slot B2 of the I/O slots.
User Group Privileges Granted • • • • • None Test Alert User Debug Command Administrator Fabric A Administrator Fabric B Administrator Fabric C Administrator No assigned permissions Table 22.
Configuring Local Users Using CMC Web Interface To add and configure local CMC users: NOTE: You must have Configure Users permission to create a CMC user. 1. In the system tree, go to Chassis Overview, and then click User Authentication → Local Users. The Users page is displayed. 2. In the User ID column, click a user ID number. NOTE: User ID 1 is the root user account that is shipped by default with CMC. This cannot be changed. The User Configuration page is displayed. 3.
The following example describes how to add a new user named "John" with a "123456" password and login privileges to the CMC.
• 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 • • • • Bit Mask Test Alert User Fabric A Administrator Fabric B Administrator Fabric C Administrator 3 None CMC Login User 0x00000001 4 None No assigned permissions 0x00000000 5 None No assigned permissions 0x00000000 NOTE: The Bit Mask values are used only when setting Standard Schema with the RACADM. NOTE: For more information about user privileges, see Types of Users.
10. Click Apply. The CMC Web server automatically restarts after you click Apply. 11. Log out and then log in to CMC to complete the CMC Active Directory configuration. 12. Select Chassis in the system tree, and navigate to the Network tab. The Network Configuration page appears. 13. Under Network Settings, if Use DHCP (for CMC Network Interface IP Address) is selected, select Use DHCP to obtain DNS server address.
extensions to the schema, they can be guaranteed to be unique and not to conflict with each other. To extend the schema in Microsoft's Active Directory, Dell received unique OIDs, unique name extensions, and uniquely linked attribute IDs for the attributes and classes that are added into the directory service. • Dell extension: dell • Dell base OID: 1.2.840.113556.1.8000.
administrator privilege to both CMCs and give user3 a login privilege to the RAC2 card. The following figure illustrates how you set up the Active Directory objects in this scenario. When adding Universal Groups from separate domains, create an Association Object with Universal Scope. The Default Association objects created by the Dell Schema Extender Utility are Domain Local Groups and does not work with Universal Groups from other domains. Figure 9.
To configure the objects for the multiple domain scenario: 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.
5. Click Finish. The schema is extended. To verify the schema extension, use the MMC and the Active Directory Schema Snap-in to verify that the classes and attributes exist. For more information on classes and attributes, see Classes and Attributes. See the Microsoft documentation for details about using the MMC and the Active Directory Schema Snap-in. Classes and Attributes Table 24.
OID 1.2.840.113556.1.8000.1280.1.1.1.3 Attribute dellIsLoginUser s dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsTestAlertUser dellIsDebugCommandAdmin dellPermissionMask1 dellPermissionMask2 Table 28. : dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description Used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges Table 29.
Assigned OID/Syntax Object Identifier Single Valued Attribute: dellIsUserConfigAdmin TRUE Description: TRUE if the user has User Configuration Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.5 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Attribute: delIsLogClearAdmin TRUE Description: TRUE if the user has Clear Logs Administrator rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.6 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
For 64-bit Windows Operating Systems, the Snap-in installer is located under::\SYSMGMT\ManagementStation \support\OMActiveDirect ory_SnapIn64 For more information about the Active Directory Users and Computers Snap-in, see Microsoft documentation. Adding CMC Users and Privileges to Active Directory Using the Dell-extended Active Directory Users and Computers Snap-in, you can add CMC users and privileges by creating RAC device, association, and privilege objects.
Adding Objects to Association Object Using the Association Object Properties window, you can associate users or user groups, privilege objects, and RAC devices or RAC device groups. If your system is running on Microsoft Windows 2000 mode or higher, use Universal Groups to span domains with your user or RAC objects. You can add groups of Users and RAC devices. The procedure for creating Dell-related groups and non-Dell-related groups is identical.
NOTE: You must apply the settings before continuing. If you do not apply the settings, the settings are lost when you navigate to the next page. 5. In the Extended Schema Settings section, type 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.
To specify an LDAP server, type: racadm config -g cfgActiveDirectory -o cfgADDomainController To specify a Global Catalog server, type: racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog NOTE: Setting the IP address as 0.0.0.0 disables CMC from searching for a server. NOTE: You can specify a list of LDAP or global catalog servers separated by commas. CMC allows you to specify up to three IP addresses or host names.
Figure 11. 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.
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. – DNS server — Specify the DNS server to retrieve a list of LDAP servers by searching for their SRV record within the DNS. The following DNS query is performed for SRV records: _[Service Name]._tcp.
10 Configuring CMC For Single Sign-On Or Smart Card Login This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. 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 to have an automatic or single sign-on to subsequent applications such as Exchange.
CMC • CMC must have firmware version 2.10 or later. • Each CMC must have an Active Directory account. • CMC must be a part of the Active Directory domain and Kerberos Realm. Prerequisites For Single Sign-On Or Smart Card Login The pre-requisites to configure SSO or Smart Card logins are: • Setup the kerberos realm and Key Distribution Center (KDC) for Active Directory (ksetup). • A robust NTP and DNS infrastructure to avoid issues with clock drift and reverse lookup.
Configuring Browser For SSO Login Single Sign-On (SSO) is supported on Internet Explorer versions 6.0 and later and Firefox versions 3.0 and later. NOTE: The following instructions are applicable only if CMC uses Single Sign-On with Kerberos authentication. Internet Explorer To configure Internet Explorer for Single Sign-On: 1. In the Internet Explorer, select Tools → Internet Options. 2. On the Security tab, under Select a zone to view or change security settings, select Local Intranet. 3.
The settings are saved. You can test the Active Directory using Kerberos authentication using the RACADM command: testfeature -f adkrb -u @ where is a valid Active Directory user account. A command success indicates that CMC is able to acquire Kerberos credentials and access the user's Active Directory account. If the command is not successful, resolve the error and run the command again.
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 Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
In the command line interface, you can manage session timeouts using the racadm command, racadm getconfig -g cfgSessionManagement. For more information, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide. Using SSH With CMC SSH is a command line session that includes the same capabilities as a Telnet session, but with session negotiation and encryption to improve security. The CMC supports SSH version 2 with password authentication.
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. Before adding or deleting public keys, be sure to use the view command to see what keys are already set up so that a key is not accidentally overwritten or deleted. The service username is a special user account that can be used when accessing the CMC through SSH.
• Save the public key to a file to upload later. • Copy and paste the text from the Public key for pasting window when adding the account using the text option. Generating Public Keys for Systems Running Linux The ssh-keygen application for Linux clients is a command line tool with no graphical user interface. Open a terminal window and at the shell prompt type: ssh-keygen –t rsa –b 2048 –C testing where, –t must be rsa. –b specifies the bit encryption size between 2048 and 4096.
Perform the steps in the following subsections to configure the required type of terminal software. Configuring Linux Minicom Minicom is a serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0. Other Minicom versions may differ slightly but require the same basic settings. See the information in the Required Minicom Settings section to configure other versions of Minicom. Configuring Minicom Version 2.
• iDRAC Web interface serial console redirection feature. • iDRAC Serial Over LAN (SOL) functionality. In a serial, Telnet, SSH console, the CMC supports the connect command to establish a serial connection to server or IOM modules. The server serial console contains both the BIOS boot and setup screens, and the operating system serial console. For I/O modules, the switch serial console is available.
Configuring the Managed Server BIOS for Serial Console Redirection It is necessary to connect to the managed server using the iKVM (see Managing Servers With iKVM ) or establish a Remote Console session from the iDRAC Web interface (see the iDRAC User’s Guide on dell.com/support/manuals). Serial communication in the BIOS is OFF by default. To redirect host text console data to Serial over LAN, you must enable console redirection through COM1. To change the BIOS setting: 1. Boot the managed server. 2.
# #boot=/dev/sda default=0 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.
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. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it.
12 Using FlexAddress and FlexAdress Plus Cards This section provides information about FlexAddress and FlexAddress Plus cards, how to configure and use these cards. Related link About Flexaddress About FlexAddress Plus FlexAddress and FlexAddress Plus Comparison About Flexaddress If a server is replaced, the FlexAddress for the slot remains the same for the given server slot.
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. Table 35.
Component PowerEdgeM600/M605 LAN on motherboard (LOM) iDRAC CMC Minimum Required Version • • PowerEdge M710 PowerEdge M710hd • • Boot code firmware 4.4.1 or later iSCSI boot firmware 2.7.11 or later • • Version 1.50 or later for PowerEdge xx0x systems Version 2.10 or later for PowerEdge xx1x systems Version 1.10 or later NOTE: Any system ordered after June 2008 has the correct firmware versions.
Verifying FlexAddress Activation Use the following RACADM command to verify the SD feature card and its status: racadm featurecard -s Table 37. Status Messages Returned by featurecard -s Command Status Message Actions No feature card inserted. Check CMC to verify that the SD card was properly inserted. In a redundant CMC configuration, ensure that the CMC with the SD feature card installed is the active CMC and not the standby CMC.
The command returns the following status message if it is successfully deactivated: feature FlexAddress is deactivated on the chassis successfully. If the chassis is not powered-down prior to execution, the command fails with the following error message: ERROR: Unable to deactivate the feature because the chassis is powered ON For further information on the command, see the feature command section of the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
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.
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.
Alternatively, click Server Overview → Slot → Setup → FlexAddress to view the WWN/MAC Address information for a specific server slot. The FlexAddress page is displayed. 2. In the WWN/MAC Addresses table, click Export to save the WWN/MAC addresses locally. 3. Click the against a slot or click Expand/Collapse All to expand or collapse the attributes listed for a specific slot or all the slots in the WWN/MAC Addresses table. 4.
Viewing WWN or MAC Address Information Using RACADM To view WWN/MAC address information for all servers or specific servers using RACADM, use the getflexaddr and getmacaddress subcommands. To display Flexaddress for the entire chassis, use the following RACADM command: racadm getflexaddr To display Flexaddress status for a particular slot, use the following RACADM command: racadm getflexaddr [-i ] where is a value from 1 to 16.
WWN or MAC Addresses The WWN/MAC Address section displays the WWN/MAC information that is assigned to all servers, even if those server slots are currently empty. • Location displays the location of the slot occupied by the Input/Output modules. The six slots are identified by a combination of the group name (A, B, or C) and slot number (1 or 2): slot names A1, A2, B1, B2, C1, or C2. iDRAC is the server's integrated management controller. • Fabric displays the type of the I/O fabric.
Situation Command Output Changing the slot/fabric FlexAddress settings while the server modules are powered ON. $racadm setflexaddr -i 1 1 ERROR: Unable to perform the set operation because it affects a powered ON server FlexAddress DELL SOFTWARE LICENSE AGREEMENT This is a legal agreement between you, the user, and Dell Products L.P. or Dell Global B.V. ("Dell").
OR OTHER PECUNIARY LOSS) ARISING OUT OF USE OR INABILITY TO USE THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Because some jurisdictions do not allow an exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you. OPEN SOURCE SOFTWARE A portion of this CD may contain open source software, which you can use under the terms and conditions of the specific license under which the open source software is distributed.
13 Managing Input Output Fabric 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.
Figure 13. Rear View of a Chassis, Showing the Location of the IOMs Table 39. Locations of IOMs at the rear of a chassis 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. For example: • An Ethernet MC connected to a Fibre Channel IOM is an invalid configuration.
Invalid Configurations There are three types of invalid configurations: • Invalid MC or LOM configuration, where a newly installed fabric type of the server is different from the existing IOM fabric, that is, LOM or MC of a single server is not supported by its corresponding IOM. In this case, all the other servers in the chassis are running, but the server with the mismatched MC card cannot be turned on. The power button on the server flashes amber to alert a fabric mismatch.
All the IOMs (1–6) appear in the expanded list. 2. Click the IOM (slot) you want to view and click Properties → FCoE. The FCoE I/O Module page specific to the IOM slot is displayed. 3. In the Select Port drop-down, select the required port number for the selected IOM and click Show Sessions. The FCoE Session Information section displays the FCoE session information for the switch. NOTE: This section displays FCoE information, only if active FCoE sessions are running on the I/O Aggregator.
The Deploy I/O Modules page displays the IOMs that are powered on. 2. For the required IOMs, enable DHCP, enter the IP address, subnet mask, and gateway address. 3. For IOMs that are manageable, enter root password, SNMP RO Community string, and Syslog Server IP Address. For information about the fields, see CMC Online Help. NOTE: The IP address set on the IOMs from CMC is not saved to the switch's permanent startup configuration.
NOTE: This feature is supported on PowerEdge M I/O Aggregator IOM only. Other IOMs including MXL 10/40GbE are not supported. To update the IOM Infrastructure device software, in the CMC Web interface: 1. Go to Chassis Overview → I/O Module Overview → Update. The IOM Firmware Update page is displayed.
Input Output Aggregator Module You can view details of the IOM and Flex Modules on the CMC RACADM, and Chassis Health, I/O Module Status, and I/O Module Overview pages. CMC reports information about the flex modules in the IOA by reading the flex module information during its initial negotiation with the IOA. The reading happens by sending XML commands during the initial negotiation. CMC saves the flex module information in the shared memory.
Related link Configuring VLAN settings on IOMs Using CMC Web Interface Viewing the VLAN settings on IOMs Using CMC Web Interface Viewing the Current VLAN Settings on IOMs Using CMC Web Interface Adding Tagged VLANs for IOMs Using CMC Web Interface Removing VLANs for IOMs Using CMC Web Interface Updating Untagged VLANs for IOMs Using CMC Web Interface Resetting VLANs for IOMs Using CMC Web Interface Configuring Management VLAN on IOMs Using Web Interface You can manage the IO Aggregator in-band through a VL
Configuring VLAN settings on IOMs Using CMC Web Interface NOTE: You can configure VLAN settings only on PowerEdge M I/O Aggregator IOM. Other IOMs including MXL 10/40GbE are not supported. To configure 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 displays the IOM(s) that are turned on and the available ports. 2.
Adding Tagged VLANs for IOMs Using CMC Web Interface To add tagged 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. In the Step 1: Select I/O Module section, select the required IOMs. 3. In the Step 2: Specify Port Range section, select the range of fabric ports to be assigned to the selected IOM(s). For information about the fields, see CMC Online Help. 4.
Resetting VLANs for IOMs Using CMC Web Interface To reset VLANs for IOM(s) to default configurations 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. In the Step 1: Select I/O Module section, select the required IOMs. 3. In the Step 3: Edit VLANs section, select Reset VLANs in the drop down list and click Apply.
14 Configuring and Using iKVM 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, hot-pluggable 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.
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. The iKVM assigns an order of precedence for each type of connection so that when there are multiple connections, only one connection is available while the others are disabled. The order of precedence for iKVM connections is: 1.
Navigation Basics Table 40. : OSCAR Keyboard and Mouse Navigation Key or Key Sequence Result • Any of these key sequences opens OSCAR depending on the Invoke OSCAR settings. You can enable two, three, or all of these key sequences by selecting boxes in the Invoke OSCAR section of the Main dialog box, and then clicking OK. • • • - - - - Opens the Help screen for the current dialog box.
Table 41. Setup dialog box — features Feature Purpose Menu Changes the server listing between numerically by slot or alphabetically by name. Security • • Flag Changes display, timing, color, or location of the status flag. Language Changes the language for all OSCAR screens. Broadcast Sets up to simultaneously control multiple servers through keyboard and mouse actions. Scan Sets up a custom scan pattern for up to 16 servers. Sets a password to restrict access to servers.
Table 42. Flag display Flag Description Flag type by name. Flag indicating that the user is disconnected from all systems. Flag indicating that Broadcast mode is enabled. To set the display of the status flag: 1. Press to launch OSCAR. The Main dialog box appears. 2. Click Setup and then Flag. The Flag dialog box appears. 3. Select Displayed to always display the flag or Displayed and Timed to display the flag for only five seconds after switching.
NOTE: You can use multiple keyboards and mice on the iKVM local USB port. The iKVM aggregates the input signals. If there are simultaneous input signals from multiple USB keyboards or mice, it may have unpredictable results. NOTE: The USB connections are solely for supported keyboard, mouse, and USB hubs. iKVM does not support data transmitted from other USB peripherals. Viewing and Selecting Servers When you launch OSCAR, the Main dialog box appears.
dialog box is displayed after is pressed) and if you press the key sequences before that time has elapsed, the OSCAR interface does not display. Related link Configuring Soft Switching Soft Switching to a Server Configuring Soft Switching To configure OSCAR for soft switching: 1. Press to launch the OSCAR interface. 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.
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.
Setting Automatic Logout You can set OSCAR to automatically log out of a server after a period of inactivity. 1. In the Main dialog box, click Setup and then Security. 2. In the Inactivity Time field, enter the length of time you want to stay connected to a server before it automatically disconnects you. 3. Click OK. Removing Password Protection From the Console To remove password protection from your console: 1. In the Main dialog box, click Setup and then Security. 2.
Changing the Language Use the Language dialog box to change the OSCAR text to display in any of the supported languages. The text immediately changes to the selected language on all of the OSCAR screens. To change the OSCAR language: 1. Press . The Main dialog box appears. 2. Click Setup and then Language. The Language dialog box appears. 3. Select the required language and click OK.
Removing Server from Scan List To remove a server from the Scan list: 1. 2. In the Scan dialog box, do one of the following: • Select the server to be removed. • Double-click the server name or slot. • Click Clear to remove all servers from the Scan list. Click Add/Remove, and then click OK. Starting the Scan Mode To start the scan mode: 1. Press . The Main dialog box is displayed. 2. Click Commands. The Command dialog box is displayed. 3. Select the Scan Enable option. 4.
3. Enable mouse and/or keyboard for the servers that are to receive the broadcast commands by selecting the boxes. or Press the up or down arrow keys to move the cursor to a target server. Then, press to select the keyboard box and/or to return to the Main dialog box. The Commands dialog box is displayed. 7.
Enabling Access to iKVM from the Dell CMC Console To enable access to the CMC CLI from iKVM using the CMC Web interface, in the system tree, go to Chassis Overview → iKVM and click Setup tab. Select the Allow access to CMC CLI from iKVM option, and click Apply to save the setting.
15 Managing and Monitoring Power The Dell PowerEdge M1000e server enclosure is the most power-efficient modular server enclosure. It is designed to include highlyefficient power supplies and fans, has an optimized layout for the air to flow more easily through the system, and contains poweroptimized components throughout the enclosure.
Related link Redundancy Policies Dynamic Power Supply Engagement Default Redundancy Configuration Power Budgeting For Hardware Modules Viewing Power Consumption Status Viewing Power Budget Status Redundancy Status and Overall Power Health Configuring power budget and redundancy Executing Power Control Operations Redundancy Policies Redundancy policy is a configurable set of properties that determine how CMC manages power to the chassis.
health is marked non-critical. If the smaller grid cannot support the total chassis power allocations, then grid redundancy status is reported as No Redundancy and Chassis health is displayed as Critical. Power Supply Redundancy Policy The power supply redundancy policy is useful when redundant power grids are not available, but you may want to be protected against a single PSU failure bringing down your servers in a modular enclosure. The highest capacity PSU is kept in online reserve for this purpose.
Extended Power Performance Extended Power Performance (EPP) mode enables allocation of 30% additional power in a configuration of six Power Supply Units (PSUs), to the M1000e chassis, than the redundant power in a Grid Redundancy configuration using 3000 W AC PSUs. However, the power allocated to servers is automatically reduced in the event of an AC grid failure or a PSU failure, so that the servers are not powered off.
Dynamic Power Supply Engagement Dynamic Power Supply Engagement (DPSE) mode is disabled by default. DPSE saves power by optimizing the power efficiency of the PSUs supplying power to the chassis. This also increases the PSU life, and reduces heat generation. CMC monitors total enclosure power allocation, and moves the PSUs to Standby state. Moving the PSUs to standby state: • Enables delivery of the total power allocation of the chassis through fewer PSUs.
Three PSUs No Redundancy Disabled Grid Redundancy In Grid Redundancy mode with six PSUs, all six PSUs are active. The three PSUs on the left must connect to one input power grid, while the three PSUs on the right connect to another power grid. CAUTION: To avoid a system failure and for Grid Redundancy to work effectively, there must be a balanced set of PSU properly cabled to separate grids.
CMC allocates power to the CMC infrastructure and the servers in the chassis. CMC infrastructure consists of components in the chassis, such as fans, I/O modules, and iKVM (if present). The chassis may have up to 16 servers that communicate to the chassis through the iDRAC. For more information, see the iDRAC User’s Guide at support.dell.com/manuals. iDRAC provides CMC with its power envelope requirements before powering up the server.
may be not be allocated enough power to run at their maximum performance or they may not even power on at all, depending on how low the system input power cap is set and the server power requirements. If an administrator manually powers on the low priority server modules before the higher priority ones, then the low priority server modules are the first modules to have their power allocation lowered down to the minimum value, in order to accommodate the higher priority servers.
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.
New Server Engagement Policy If a new server that is turned on exceeds the power available for the chassis, CMC may decrease the power to the low-priority servers. This allows more power for the new server. This happens if: • The administrator had configured a power limit for the chassis that is below the power required for full power allocation to the servers. • Insufficient power is available for the worst-case power requirement of all servers in the chassis.
The following table lists the SEL entries that are related to power supply changes: Table 47. SEL Events for Power Supply Changes Power Supply Event System Event Log (SEL) Entry Insertion Power supply is present. Removal Power supply is absent. Grid or Power Supply Redundancy lost Power supply redundancy is lost. Grid or Power Supply Redundancy regained The power supplies are redundant. Input power received The input power for power supply has been restored.
Configuring power budget and redundancy You can configure the power budget, redundancy, and dynamic power of the entire chassis (chassis, servers, I/O modules, iKVM, CMC, and power supplies), which uses six power supply units (PSUs). The power management service optimizes power consumption and re-allocates power to different modules based on the requirement.
In maximum power conservation mode, all servers start functioning at their minimum power levels, and all subsequent server power allocation requests are denied. In this mode, the performance of powered on servers may be degraded. Additional servers cannot be powered on, regardless of server priority. The system is restored to full performance when the maximum conservation mode is cleared.
When external power management is enabled, Dell OpenManage Power Center manages: • Server Power of supported M1000e servers • Server Priority of supported M1000e servers • System Input Power Capacity • Maximum Power Conservation Mode The CMC continues to maintain or manage: • Redundancy Policy • Remote Power Logging • Server Performance over Power Redundancy • Dynamic Power Supply Engagement • Server Power of 11th generation and earlier servers Dell OpenManage Power Center then manages pri
Configuring Power Budget and Redundancy Using RACADM NOTE: To perform power management actions, you must have Chassis Configuration Administrator privilege. To enable and set the redundancy policy: 1. Open a serial/Telnet/SSH text console to CMC and log in. 2. Set properties as needed: • To select a redundancy policy, type: racadm config -g cfgChassisPower -o cfgChassisRedundancyPolicy where is 0 (No Redundancy), 1 (Grid Redundancy), 2 (Power Supply Redundancy). The default is 0.
• To determine the power remote logging interval, type the following command: racadm getconfig -g cfgRemoteHosts -o cfgRhostsSyslogPowerLoggingInterval The power remote logging feature is dependent on remote syslog hosts having been previously configured. Logging to one or more remote syslog hosts must be enabled, otherwise power consumption is logged. This can be done either through the Web interface or the RACADM CLI.
AC Power Recovery If the AC power supply of a system is disrupted, the chassis is restored to the previous power state before the AC power loss. The restoration to the previous power state is the default behavior.
5. Click OK to perform the power management action (for example, cause the server to reset).
16 Troubleshooting and Recovery This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC Web interface. • Viewing chassis information. • Viewing the event logs. • Gathering configuration information, error status, and error logs. • Using the Diagnostic Console. • Managing power on a remote system. • Managing Lifecycle Controller jobs on a remote system. • Resetting components.
Table 49.
– Resolution B: Ensure that all power supplies are properly connected to the two AC grids. Power supplies in side 1 need to be connected to one AC grid, those in side 2 need to be connected to the other AC grid, and both AC grids must be working. Grid Redundancy is lost when one of the AC grids is not functioning. • Problem: The PSU state is displayed as Failed (No AC), even when an AC cable is connected and the power distribution unit is producing good AC output.
SNMP does not confirm delivery of traps, use a network analyzer or a tool such as Microsoft’s snmputil to trace the packets on the managed system. Related link Configuring CMC To Send Alerts Viewing Event Logs You can view hardware and CMC logs for information on system-critical events that occur on the managed system. Related link Viewing Hardware Log Viewing CMC Log and Enhanced Chassis Log Viewing Hardware Log CMC generates a hardware log of events that occur on the chassis.
Viewing CMC Log and Enhanced Chassis Log CMC generates a log of the chassis-related events and enhanced logging of the chassis when the Enable Enhanced Logging and Events option is enabled. To view enhanced logging of the chassis in the Chassis Log page, select the Enable Enhanced Logging and Events option in the General Settings page. To enable or disable the feature using RACADM, use the cfgRacTuneEnhancedLog object.
The Diagnostic Console page is displayed. 2. In the Command text box, enter a command and click Submit. For information about the commands, see the CMC Online Help. A diagnostic results page is displayed. Resetting Components You can reset the active CMC, reset iDRAC without rebooting the operating system, or to virtually reseat servers causing them to behave as if they were removed and reinserted.
Troubleshooting Network Time Protocol Errors After configuring CMC to synchronize the clock with a remote time server over the network, it may take 2-3 minutes before a change in the date and time occurs. If after this time there is still no change, it may be necessary to troubleshoot a problem. CMC may not be able to synchronize the clock for the following reasons: • Problem with the NTP Server 1, NTP Server 2, and NTP Server 3 settings.
• A blinking amber LED on a module indicates a fault on that module. • Blue, blinking LEDs are configurable by the user and used for identification. For more information about configuration, see Downloading SNMP Management Information Base (MIB) File. Table 50.
Component Fan PSU LED Color, Blinking Pattern Status Green, dark Powered off Blue, glowing steadily Normal Blue, blinking User-enabled module identifier Amber, glowing steadily Not used Amber, blinking Fault Blue, dark No fault Green, glowing steadily Fan working Green, blinking Not used Green, dark Powered off Amber, glowing steadily Fan type not recognized, update CMC firmware Amber, blinking Fan fault; tachometer out of range Amber, dark Not used (Oval) Green, glowing steadil
NOTE: A normal CMC boot or reset takes over a minute to fully boot into its operating system and be available for login. The blue LED is enabled on the active CMC. In a redundant, two-CMC configuration, only the top green LED is enabled on the standby CMC. Obtain Recovery Information From DB-9 Serial Port If the bottom LED is amber, recovery information is available from the DB-9 serial port located on the front of CMC. To obtain recovery information: 1.
The trace log may also contain CMC firmware-specific error codes that are related to the internal CMC firmware, not the managed system’s operating system. Resetting Administrator Password CAUTION: Many repairs may only be done by a certified service technician. You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team.
Figure 18. Password Reset Jumper Location Table 51. CMC Password Jumper Settings PASSWORD_RSET (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 19. LCD Display Table 52.
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. The icons described in the following table are used to navigate between LCD screens. Table 53.
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. Press the center button to activate your selection.
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.
Enclosure Status Screen The Enclosure Status screen displays information and error messages about the enclosure. For messages that can appear on this screen, see LCD Error Messages. Use the up and down arrow keys to move through messages. Use the left and right arrow keys to scroll messages that do not fit on the screen. Highlight the Back icon and press the center button to return to the Enclosure Status screen.
Figure 20. Removing and Installing LCD Module Table 54. LCD Module — components 1 cable cover 2 LCD module 3 ribbon cable 4 hinges (2) 5 screws (2) Table 55. 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.
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 All event logging is disabled. The Chassis/Enclosure cannot store events to the logs. This usually indicates a problem with the control panel or control panel cable. Warning Log is full. Chassis has detected that only one more entry can be added to the CEL (hardware log) before it is full. Warning Log is almost full. Chassis event log is 75% full. Table 58.
Severity Message Cause Warning The system board ambient temperature is greater than the upper warning threshold. Server temperature is getting warm. Critical The system board ambient temperature is greater than the upper critical threshold. Server temperature is getting too hot. Critical The system board Current Latch current is outside of the allowable range Current crossed a failing threshold. Critical The system board battery failed. CMOS battery is not present or has no voltage.
Severity Message Cause Critical Log is full. The SEL device detects that only one entry can be added to the SEL before it is full. Warning Persistent correctable memory errors detected on a memory device at location . Warning Persistent correctable memory error rate has increased for a memory device at location . Correctable ECC errors reach a critical rate. Critical Multi-bit memory errors detected on a memory device at location .
Severity Message Cause Critical Failed to program virtual MAC address on a component at bus device function . Flex address could be programmed for this device. Critical Device option ROM on mezzanine card failed to support Link Tuning or FlexAddress. Option ROM does not support Flex address or linking tuning. Critical Failed to get Link Tuning or FlexAddress data from iDRAC. NOTE: For information on other server related LCD messages, see "Server User Guide".
Item Description Service Tag The factory-assigned service tag. CMC redundancy Non-Redundant or Redundant. mode PSU redundancy mode Non-Redundant, AC Redundant, or DC Redundant. Table 65. Fan Status Item Description Name/Location Example: Fan1, Fan2, and so on. Error Messages If no error then "No Errors" is shown; otherwise error messages are listed, critical errors first, then warnings. RPM Current fan speed in RPM. Table 66.
Item Description Service Tag The factory-assigned service tag. Part Number The Manufacturer part number. Firmware Version iKVM firmware version. Hardware Version iKVM hardware version. NOTE: This information is dynamically updated Table 69. Server Status Item Description Example: Server 1, Server 2, Name/Location. etc. No Errors If there are no errors then the message “No Errors” is displayed, else error messages are listed. Critical errors are listed first, followed by warnings.
• Option “Custom” = Allows you to enter a string name for the server. The information is displayed only if iDRAC has completed booting. For more information on this feature, see the Chassis Management Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide at dell.com/support/manuals.
18 Frequently Asked Questions 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) This message indicates that another command must be issued only after CMC completes the reset.
To ensure that the CSR matches the registered DNS CMC name: 1. In the CMC Web interface, go to the System tree, click Chassis Overview. 2. Click the Network tab, and then click Network. The Network Configuration page appears. 3. Select the Register CMC on DNS option. 4. Type the CMC name in the DNS CMC Name field. 5. Click Apply Changes. For more information about generating CSRs and issuing certificates, see Obtaining Certificates.
Yes. The domain forest function level must be in Native mode or Windows 2003 mode. In addition, the groups among Association Object, RAC user objects, and RAC Device Objects (including Association Object) must be universal groups. Can these Dell-extended objects (Dell Association Object, Dell RAC Device, and Dell Privilege Object) be in different domains? The Association Object and the Privilege Object must be in the same domain.
Yes it does. Before installing the SD card into the CMC module, verify the write protection latch is in the unlock position. The FlexAddress feature cannot be activated if the SD card is write protected. In this situation, the $racadm feature -s command returns this message: No features active on the chassis. ERROR: read only file system What happens if there is no SD card in the active CMC module? The $racadm featurecard -s command returns this message: No feature card inserted.
racadm config -g cfgKVMInfo -o cfgKVMAccesToCMCEnable 1 The rear panel access does not work. Why? The front panel setting is enabled by CMC, and a monitor is currently connected to the front panel. Only one connection is allowed at a time. The front panel connection has precedence over ACI and the rear panel. For more information about connection precedence, see iKVM Connection Precedences.
• Entering an invalid subnet mask. • Setting the default gateway to an address that is not on a network that is directly connected to the switch. For more information on IOM network settings, see the Dell PowerConnect M6220 Switch Important Information document and the Dell PowerConnect 6220 Series Port Aggregator White Paper at dell.com/support/manuals. Single Sign On Though CMC is setup to allow Single Sign-On (SSO), the browser displays a blank page.
19 Use Case Scenarios This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Chassis Basic Configuration and Firmware Update This scenario guides you to perform the following tasks: • Bring up the chassis with basic configurations. • Verify that hardware is being detected by CMC without any errors. • Update firmware for CMC, IOMs, and server components. 1. CMC is pre-installed on your chassis and hence no installation is required.
Update Firmware for Management Consoles Without Servers Downtime You can update firmware for management consoles for CMC, iDRAC and Lifecycle Controller without downtime on the servers: 1. In a scenario, where both the primary and the standby CMC is present, you can update the CMC firmware without servers or IOMs downtime. 2. To update firmware on the primary CMC, see the Updating Firmware section. When you update firmware on the primary CMC, the standby CMC takes on the role of the primary CMC.
– Server Based Power Management (SBPM) – Redundancy Policy: Power Supply Redundancy or No Redundancy – Max Power Conservation Mode (MPCM). – Dynamic Power Supply Engagement (DPSE). – System Input Power Cap is set to value less than or equal to 13300W or (45381 BTU/h) . • The chassis does not have six 3000W PSUs or all the PSUs do not support EPP , the EPP option is grayed out and not available for selection.
Scenario 5: Trying to enable EPP from the disabled start condition, when other power configuration settings are set. • Enabling EPP on a 3000W AC PSU when System Input Power Cap is low racadm config -g cfgchassispower -o cfgChassisEPPEnable This feature is not supported while System Input Power Cap is set equal to 13300 W (45381 BTU/h).
