Chassis Management Controller Version 1.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview....................................................................................................................13 What Is New In This Release............................................................................................................... 14 Key Features.........................................................................................................................................14 Management Features.............................................................
Configuring Initial CMC Network................................................................................................. 29 Interfaces and Protocols to Access CMC...........................................................................................33 Launching CMC Using Other Systems Management Tools........................................................ 34 Downloading and Updating CMC Firmware......................................................................................
Enabling or Disabling Warning Message to Change Default Login Password Using RACADM........................................................................................................................................ 48 4 Updating Firmware................................................................................................ 49 Downloading CMC Firmware.............................................................................................................
Viewing Information and Health Status of All Servers....................................................................... 65 Viewing Health Status and Information for Individual Server........................................................... 66 Viewing Information and Health Status of the IOM.......................................................................... 66 Viewing Information and Health Status For Individual I/O Module..................................................
Chassis Group Inventory and Firmware Version..........................................................................83 Viewing Chassis Group Inventory ............................................................................................... 84 Viewing Selected Chassis Inventory Using Web Interface.......................................................... 84 Viewing Selected Server Component Firmware Versions Using Web Interface........................ 84 Configuring Multiple CMCs Using RACADM.......
Configuring CMC To Send Alerts..................................................................... 103 Enabling Or Disabling Alerts............................................................................................................. 103 Enabling Or Disabling Alerts Using CMC Web Interface........................................................... 103 Enabling Or Disabling Alerts Using RACADM.............................................................................103 Filtering Alerts..........
Configuring CMC SSO Or Smart Card Login For Active Directory Users Using RACADM.......136 11 Configuring CMC to Use Command Line Consoles................................... 137 CMC Command Line Console Features...........................................................................................137 CMC Command Line Interface Commands...............................................................................137 Using Telnet Console With CMC...........................................................
Managing Power Control Operation for I/O Modules.....................................................................162 Enabling or Disabling LED Blinking for I/O Modules....................................................................... 163 14 Managing and Monitoring Power...................................................................165 Redundancy Policies.........................................................................................................................
Executing Power Control Operations on IOM Using CMC Web Interface............................... 179 Executing Power Control Operations on the IOM Using RACADM..........................................180 15 Managing Chassis Storage................................................................................181 Viewing Status of the Storage Components.................................................................................... 181 Viewing the Storage Topology......................................
First Steps to Troubleshoot a Remote System.................................................................................194 Power Troubleshooting.............................................................................................................. 194 Troubleshooting Alerts..................................................................................................................... 196 Viewing Event Logs......................................................................................
Overview 1 The Dell Chassis Management Controller (CMC) for Dell PowerEdge VRTX is a Systems Management hardware and software solution for managing the PowerEdge VRTX chassis. The CMC has its own microprocessor and memory and is powered by the modular chassis into which it is plugged.
– User access security. – Storage components, including the fault-tolerant mode for the storage controllers. – PCIe slots. You can configure CMC to send email alerts or SNMP trap alerts for warnings or errors such as temperature, hardware misconfiguration, power outage, fan speed, and blowers. What Is New In This Release This release of CMC for Dell PowerEdge VRTX supports: • Fault-tolerant (Active/Passive) mode for shared storage “Shared PERC 8”. • M820 Server Platform support.
• • • • • • • • • • • FlexAddress feature — Replaces the factory-assigned World Wide Name/Media Access Control (WWN/ MAC) IDs with chassis-assigned WWN/MAC IDs for a particular slot, an optional upgrade. Graphical display of chassis component status and health. Support for single and multi-slot servers. LCD iDRAC configuration wizard supports for iDRAC network configuration. iDRAC single sign-on. Network time protocol (NTP) support. Enhanced server summary, power reporting, and power control pages.
Item Indicator, Button, or Connector 1 Status/identification indicator (CMC 1) 2 Power indicator (CMC 1) 3 CMC connector ports (2) 4 Power indicator (CMC 2) 5 Status/identification indicator (CMC 2) A Back Panel view of the chassis is given here with a table that lists the parts and devices available in the CMC.
Item Indicator, Button, or Connector 7 I/O module ports 8 PSU 4 9 PSU 3 10 PSU 1 11 PSU 2 A Front Panel view of the chassis is given here with a table that lists the parts and devices available in the CMC. Figure 1. Front-Panel Features And Indicators—3.5 Inch Hard Disk Drive Chassis Ite m Indicator, Button, or Connector Description 1 USB connectors (2) Allows a keyboard and mouse to be connected to the system.
Ite m Indicator, Button, or Connector Description 4 Selection ("check") button Selects and saves an item on the LCD screen and moves to the next screen. 5 Enclosure power-on indicator, power button The power-on indicator glows when the enclosure power is on. The power button controls the PSU output to the system. 6 Hard disk drives (HDD) 2.5 inch hard drive enclosure Up to twenty five 2.5 inch hot-swappable hard disk drives. 3.5 inch hard drive enclosure Up to twelve 3.
Supported Platforms CMC supports modular servers designed for the PowerEdge VRTX platform. For information about compatibility with CMC, see the documentation for your device. For the latest supported platforms, see the Dell Chassis Management Controller (CMC) Version 1.00 for Dell PowerEdge VRTX Release Notes available at dell.com/support/manuals.
License Operations Before you perform the license management tasks, make sure to acquire the licenses. For more information, see the Overview and Feature Guide available at support.dell.com. NOTE: If you have purchased a system with all the licenses pre-installed, then license management is not required.
Before importing a license, make sure to store a valid license file on the local system or on a network share that is accessible from the CMC. The license is either embedded, or sent through an email from the Self-Service Web Portal, or from the License Key Management tool. The Licensing page displays the licenses that are associated to devices, or the licenses that are installed, but the device is not present in the system.
Slot Resource Management No Yes Enclosure-level power capping No* Yes *For non-default power cap setting, only Restore Power Cap is allowed with an Express license. Restore Power Cap will reset the Power Cap settings to factory default. Dynamic Power Supply Engagement No* Yes *For non-default DPSE settings, only Restore DPSE is allowed with an Express license. Restore DPSE will reset the DPSE to factory default.
• The RACADM commands: The RACADM command or the object that you must use is provided here. For more information about a RACADM command, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide available at dell.com/support/manuals. Other Documents You May Need To access the documents from the Dell Support site. Along with this Reference Guide, you can access the following guides available at dell.com/support/manuals.
system setup placemat that shipped with your system. Download the QRL application from your mobile platform to enable the application on your mobile device. Updates are sometimes included with the system to describe changes to the system, software, and/or documentation. Always read the updates first, because they often supersede information in other documents.
Installing and Setting Up CMC 2 This section provides information about how to install your CMC hardware, establish access to CMC, configure your management environment to use CMC, and guides you through the tasks for configuring a CMC: • Set up initial access to CMC. • Access CMC through a network. • Add and configure CMC users. • Update CMC firmware. For more information about installing and setting up redundant CMC environments, see Understanding Redundant CMC Environment.
8. Provide each iDRAC with an IP address in the CMC web interface, and enable the LAN and IPMI interface. NOTE: iDRAC LAN interface on some servers are disabled by default. This information can be found on the CMC web interface under Server Overview → Setup. This might be an advanced license option; in which case you must use the SetUp feature for each server). 9. Provide the IO module with an IP address in the CMC web interface.
5. For help about the RACADM command, type racadm help after you run the previous commands. For more information about RACADM, see the Chassis Management Controller for Dell PowerEdge VRTX RACADM Command Line Reference Guide. NOTE: When using the RACADM remote capability, you must have the 'write' permission on the folders where you are using the RACADM subcommands, involving the file operations. For example, racadm getconfig -f . Uninstalling RACADM From a Linux Management Station 1.
5. In the Exceptions section, add the addresses for CMCs and iDRACs on the management network to the semicolon-separated list. You can use DNS names and wildcards in your entries. Mozilla FireFox To edit the exception list in Mozilla Firefox version 19.0: 1. Start Mozilla Firefox. 2. Click Tools → Options (for systems running on Windows), or click Edit → Preferences (for systems running on Linux). 3. Click Advanced, and then click the Network tab. 4. Click Settings. 5.
Enabling Animations In Internet Explorer When transferring files to and from the web interface, a file transfer icon spins to show transfer activity. While using Internet explorer, you have to configure the browser to play animations. To configure Internet Explorer to play animations: 1. Start Internet Explorer. 2. Click Tools → Internet Options → Advanced. 3. Go to the Multimedia section, and then select the Play animations in web pages option.
• Remote RACADM • CMC web interface • LCD Panel interface CMC supports both IPv4 and IPv6 addressing modes. The configuration settings for IPv4 and IPv6 are independent of each other. Configuring CMC Network Using LCD Panel Interface You can use the LCD panel interface to set up the CMC network. NOTE: You can customize the orientation of an LCD display (for rack or tower mode) by keeping the up-down buttons pressed for two seconds. Alternately, you can also use the right-left buttons.
For effective network throughput, the network speed setting must match your network configuration. Setting the network speed lower than the speed of your network configuration increases bandwidth consumption and slows down the network communication. Determine whether or not your network supports the above network speeds and set it accordingly.
– Both — The options DHCP or Static are displayed. – IPv6 — The iDRAC Configuration panel is displayed. Go to step 15. 13. Select DHCP or Static. Dynamic Host Configuration Protocol (DHCP) iDRAC retrieves IP configuration (IP address, mask, and gateway) automatically from a DHCP server on your network. The iDRAC is assigned a unique IP address allotted over your network. Press the center button. The IPMI Over LAN panel is displayed.
18. On the IP Summary panel, after the 30 second wait panel, review the IP addresses you provided to make sure the addresses are correct. To correct a setting, press the left arrow icon, and then press the center key to return to the screen for that setting. After correcting an IP address, press the center button. When you have confirmed that the settings you entered are accurate, press the center button, and then press the center button. The Main Menu panel id displayed.
Interface Description NOTE: Telnet is not a secure protocol and is disabled by default. Telnet transmits all data, including passwords in plain text. When transmitting sensitive information, use the SSH interface. SSH Use SSH to run RACADM commands. It provides the same capabilities as the Telnet console using an encrypted transport layer for higher security. The SSH service is enabled by default on CMC and can be disabled.
Downloading and Updating CMC Firmware To download the CMC firmware, see Downloading CMC Firmware. To update the CMC firmware, see Updating CMC Firmware. Setting Chassis Physical Location and Chassis Name You can set the chassis location in a data center and the chassis name to identify the chassis on the network (default name is Dell Rack System). For example, an SNMP query on the chassis name returns the name you configure.
Configuring LEDs to Identify Components on the Chassis You can enable the LEDs of components (chassis, servers, physical disk drives, virtual disks, and I/O Modules) to blink so that you can identify the component on the chassis. NOTE: To modify these settings, you must have the Chassis Configuration Administrator privilege.
Configuring iDRAC Launch Method Using CMC Web Interface To configure the iDRAC launch method from the General Chassis Settings page: 1. In the left pane, click Chassis Overview → Setup. The General Chassis Settings page is displayed. 2. In the drop-down menu for the iDRAC Launch Method property, select IP Address or DNS. 3. Click Apply. NOTE: A DNS-based launch is used for any particular iDRAC only if: – The chassis setting is DNS.
• IP address blocking • Number of login attempts allowed • Timespan for the lockout failure counts to occur • Lockout penalty time • To enable user blocking feature, use: racadm config -g cfgRacTuning -o • 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: ra
NOTE: For information about installing a CMC, see the VRTX Owner’s Manual. For instructions about installing CMC firmware on your standby CMC, see Updating Firmware. CMC Failsafe Mode Similar to the failover protection offered by the redundant CMC, the PowerEdge VRTX enclosure enables the fail-safe mode to protect the servers and I/O module from not functioning. The fail-safe mode is enabled when a CMC is not in control of the chassis.
• Power button • LCD • DVD drive Configuring Power Button To configure the chassis power button: 1. In the left pane, click Chassis Overview → Front Panel → Setup. 2. On the Front Panel Configuration page, under the Power Button Configuration section, select the Disable Chassis Power Button option, and then click Apply. The chassis power button is disabled. Configuring LCD 1. In the left pane, clickChassis Overview → Front Panel → Setup . 2.
To map the server to the KVM using the LCD — From the Main Menu screen on the LCD, go to KVM Mapping, select the server that must be mapped, and then press OK. Mapping a Server to a DVD Drive To map the server to the chassis DVD drive: 1. 2. In the left pane, click Chassis Overview → Front Panel → Setup . On the Front Panel Configuration page, under the DVD Drive Configuration section: From the DVD Mapped drop-down menu, select one of the servers.
Logging in to CMC 3 You can log in to CMC as a CMC local user, as a Microsoft Active Directory user, or as an LDAP user. The default user name and password is root and calvin respectively. You can also log in using Single SignOn or a Smart Card. Accessing CMC Web Interface Before you log in to CMC using the web interface, make sure that you have configured a supported web browser (Internet Explorer or Firefox) and the user account is created with the required privileges.
To log in as a local user, Active Directory user, or LDAP user. 1. In the Username field, type your user name: – CMC user name: – Active Directory user name: \, / or @. – LDAP user name: NOTE: This field is case-sensitive. 2. In the Password field, type the user password. NOTE: For Active Directory user, the Username field is case-sensitive. 3. Optionally, select a session timeout.
3. Type the PIN and click Submit. NOTE: If the smart card user is present in Active Directory, an Active Directory password is not required. Else, you have to log in by using an appropriate username and password. You are logged in to CMC with your Active Directory credentials. Logging in to CMC Using Single Sign-on When Single Sign-On (SSO) is enabled, you can log in to CMC without providing your domain user authentication credentials, such as user name and password.
console on the KVM, or remotely using the RACADM command line interface installed on a management station. The RACADM interface is classified as: • Remote RACADM — Allows you to run RACADM commands on a management station with the -r option and the DNS name or IP address of the CMC. NOTE: Remote RACADM is included on the Dell Systems Management Tools and Documentation DVD and is installed on a management station.
Changing Default Login Password The warning message that prompts you to change the default password is displayed if: • You log in to CMC with Configure Users privilege. • Default password warning feature is enabled. • Default user name and password for any currently enabled account are root and calvin respectively. The same warning message is displayed if you log in using Active Directory or LDAP.
Enabling or Disabling Default Password Warning Message You can enable or disable the display of the default password warning message. To do this, you must have Configure Users privilege. Enabling or Disabling Default Password Warning Message Using Web Interface To enable or disable the display of the default password warning message after logging in to iDRAC: 1. Go to Chassis Controller → User Authentication → Local Users . The Users page is displayed. 2.
Updating Firmware 4 You can update firmware for: • CMC — active and standby • Chassis infrastructure • I/O Module • iDRAC7 You can update firmware for the following server components: • iDRAC • BIOS • Lifecycle Controller • 32–bit diagnostics • Operating System Drivers Pack • Network Interface Controllers • RAID controllers Downloading CMC Firmware Before beginning the firmware update, download the latest firmware version from support.dell.com, and save it to your local system.
Viewing Currently Installed Firmware Versions Using RACADM To view the IP information for iDRAC and CMC, and the CMC service- or asset tag using RACADM, run the racadm getsysinfo sub-command. For more information about other RACADM commands, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide. Updating the CMC Firmware You can update the CMC firmware using web interface or RACADM. The firmware update, by default, retains the current CMC settings.
Updating CMC Firmware Using Web Interface NOTE: Before you update the CMC firmware, make sure that you turn on the chassis, but turn off all the servers in the chassis. To update the CMC firmware using the CMC web interface: 1. In the left pane, go to any of the following pages: – Chassis Overview → Update 2.
Updating Chassis Infrastructure Firmware Using CMC Web Interface 1. Go to any of the following pages: – Chassis Overview → Update. 2. – Chassis Overview → Chassis Controller → Update. On the Firmware Update page, in the Chassis Infrastructure Firmware section, in the Update Targets column, select the option, and then click Apply Chassis Infrastructure Firmware. 3. On the Firmware Update page, click Browse, and then select the appropriate chassis infrastructure firmware. 4.
Updating Server iDRAC Firmware Using Web Interface To update the iDRAC firmware in the server: 1. Go to any of the following pages: – Chassis Overview → Update. – Chassis Overview → Chassis Controller → Update. – Chassis Overview → I/O Module Overview → Update. The Firmware Update page is displayed. NOTE: You can also update server iDRAC firmware using Chassis Overview → Server Overview → Update. For more information, see Updating Server Component Firmware. 2.
Dell Update Packages (DUPs) are used to perform the firmware updates using Lifecycle Controller. The Operating System Driver Pack component DUP exceeds this limit and must be updated separately using the Extended Storage feature. The Lifecycle Controller provides module update support for iDRAC7 and later servers. The iDRAC firmware must be at version 2.3 or later to update firmware using Lifecycle Controller.
The Server Component Update page enables you to update various firmware components on the server. To use the features and functions on this page, you must have: • For CMC: The Server Administrator privilege. • For iDRAC: The Configure iDRAC privilege and Log in to iDRAC privilege. In case of insufficient privileges, you can only view the firmware inventory of components and devices on the server. You cannot select any components or devices for any type of Lifecycle Controller operation on the server.
Filtering Components for Firmware Updates Using CMC Web Interface To filter the devices: 1. In the left pane, go to Server Overview, and then click Update . 2.
Viewing Firmware Inventory Using CMC Web Interface To view the firmware inventory: 1. In the left pane, click Server Overview, and then click Update. 2. On the Server Component Update page, view the firmware inventory details in the Component/ Device Firmware Inventory section. On this page, you can view the following information: – Servers that currently do not support the Lifecycle Controller service are listed as Not Supported.
Field Description Rollback Version Displays the rollback version of component or device on the server. Job Status Displays the job status of any operations that are scheduled on the server. The job status is continuously updated dynamically. If a job completion with state completed is detected, then the firmware versions for the components and devices on that server are automatically refreshed in case there has been a change of firmware version on any of the components or devices.
operation is interrupted. An interruption, especially during an update operation may cause the firmware image file upload to be terminated before proper completion. After an operation has been submitted for scheduling, ensure that the confirmation message indicating that the operation has been successfully scheduled is acknowledged. Reinstalling Server Component Firmware You can reinstall the firmware image of the currently installed firmware for selected components or devices across one or more servers.
NOTE: For iDRAC and Operating System Driver packs firmware update, make sure the Extended Storage feature is enabled. It is recommended to clear the job queue before initializing a server component firmware update. A list of all jobs on the servers is available on the Lifecycle Controller Jobs page. This page enables deletion of single or multiple jobs or purging of all jobs on the server. BIOS updates are specific to the model of the server.
5. Select one of the following options: – Reboot Now - Restart the server immediately. – On Next Reboot - Manually restart the server at a later time. NOTE: This task is not valid for Lifecycle Controller and 32–bit Diagnostics firmware update. A server restart operation is performed immediately for these devices. 6. Click Update. The firmware version is updated for the selected component or device.
Recovering iDRAC Firmware Using CMC iDRAC firmware is typically updated using iDRAC interfaces such as the iDRAC web interface, the SM-CLP command line interface, or operating system specific update packages downloaded from support.dell.com. For more information, see the iDRAC7User’s Guide. Early generations of servers can have corrupted firmware recovered using the new update iDRAC firmware process. When CMC detects corrupted iDRAC firmware, it lists the server on the Firmware Update page.
Viewing Chassis Information and Monitoring Chassis and Component Health 5 You can view information and monitor the health of the following: • Active and standby CMCs • All severs and individual servers • IO Module • Fans • Power Supply Units (PSUs) • Temperature sensors • Hard disk drives • LCD assembly • Storage controllers • PCIe devices Viewing Chassis and Component Summaries When you log in to the CMC web interface, the Chassis Health page displays the health of the chassis and its
If your chassis is configured as a Group Lead, the Group Health page is displayed after login. It displays the chassis level information and alerts. All active, critical, and non-critical alerts are displayed. Chassis Graphics The chassis is represented by the front and back views (the upper and lower images respectively). Servers, DVDs, HDDs, KVMs, and LCD are shown in the front view and the remaining components are shown in the back view.
• Health and Performance, and Properties — Displays the active, critical, and non-critical events as displayed by the hardware logs and the performance data that vary with time. • Properties — Displays the component properties that do not vary with time, or that change only infrequently. • Quick Links — Provides links to navigate to the most frequently accessed pages, and also the most frequently performed actions. Only links applicable to the selected component are displayed in this section.
Viewing Health Status and Information for Individual Server To view health status for individual servers, do any of the following: 1. Go to Chassis Overview → Properties → Health. The Chassis Health page displays a graphical overview of all the servers installed in the chassis. Server health status is indicated by the overlay of the server subgraphic. Move the cursor to hover over an individual server subgraphic. A corresponding text hint or screen tip provides additional information for that server.
Viewing Information and Health Status For Individual I/O Module To view health status of the individual I/O Modules, 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 I/O Modules. I/O Module health status is indicated by the overlay of the I/O Module subgraphic.
To view the health status of fans, in the CMC Web interface, do any of the following: 1. Go to Chassis Overview. The Chassis Health page is displayed. The lower section of chassis graphics provides the left view of the chassis and contains the health status of the fans. Fan health status is indicated by the overlay of the fan sub-graphic. Move the cursor over the fan sub-graphic. The text hint provides additional information about a fan.
When enabled, ECM will only increase the cooling capacity to the server slots within the chassis. It is also important to note that ECM is not designed to provide increased cooling to the servers at all times. Even with ECM enabled, the higher blower speeds will only be seen when the increased cooling is needed. Examples of this situation include high levels of server utilization or stress, and high ambient temperatures. By default, ECM is off.
3. Click the LCD sub-graphic to view the LCD information in the right pane. For more information, see the Online Help. Alternatively, go to Chassis Overview → Front Panel → Properties → Status. On the Status page, under the LCD Properties, you can view the status of the LCD available on the chassis. For more information, see Online Help.
Configuring CMC 6 Chassis Management Controller enables you to configure properties, set up users, and alerts to perform remote management tasks. Before you begin configuring the CMC, you must first configure the CMC network settings to allow CMC to be managed remotely. This initial configuration assigns the TCP/IP networking parameters that enable access to the CMC. For more information, see Setting Up Initial Access to CMC. You can configure CMC using Web interface or RACADM.
NOTE: Changing the CMC network settings may disconnect your current network connection. NOTE: You must have Chassis Configuration Administrator privilege to set up CMC network settings. Viewing and Modifying CMC Network LAN Settings Using CMC Web Interface To view and modify the CMC LAN network settings using CMC Web interface: 1. In the left pane, click Chassis Overview, and then click Network. The Network Configuration page displays the current network settings. 2.
By default, for IPv4, the CMC requests and automatically obtains a CMC IP address from the Dynamic Host Configuration Protocol (DHCP) server. You can disable the DHCP feature and specify static CMC IP address, gateway, and subnet mask.
For IPv6, to set the preferred and secondary DNS IP Server addresses, type: racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer1 racadm config -g cfgIPv6LanNetworking -o cfgIPv6DNSServer2 Configuring DNS Settings (IPv4 and IPv6) • CMC Registration — To register the CMC on the DNS server, type: racadm config -g cfgLanNetworking -o cfgDNSRegisterRac 1 NOTE: Some DNS servers only register names of 31 characters or fewer.
NOTE: IPv6 requires a minimum MTU of 1280. If IPv6 is enabled, and cfgNetTuningMtu is set to a lower value, the CMC uses an MTU of 1280. Configuring CMC Network and Login Security Settings The IP address blocking and User blocking features in CMC allow you to prevent security issues due to password guessing attempts. This feature enables you to block a range of IP addresses and users who can access CMC. By deafult, the IP address blocking feature is enabled in CMC.
NOTE: • To enable the IP range checking feature, use the following property under cfgRacTuning group: cfgRacTuneIpRangeEnable <0/1> • To specify the range of IP addresses that you want to block from accessing CMC, use the following property under cfgRacTuning group: cfgRacTuneIpRangeAddr • To specify the IP Range Mask that you want to block from accessing CMC, use the following property under cfgRacTuning group: cfgRacTuneIpRangeMask Configuring Virtual LAN Tag Properties for CMC Virtual LANfunctional
Configuring Virtual LAN Tag Properties for CMC Using Web Interface To configure Virtual LAN(VLAN) for CMC using the CMC Web interface: 1. Go to any of the following pages: – In the left pane, click Chassis Overview and click Network → VLAN. – In the left pane, click Chassis Overview → Server Overview and click Network → VLAN. The VLAN Tag Settings page is displayed. VLAN tags are chassis properties. They remain with the chassis even when a component is removed. 2.
NOTE: Because the network transport for the forwarded log entries is UDP, there is no guaranteed delivery of log entries, nor is there any feedback to CMC about whether the log entries were received successfully. Configuring Services Using CMC Web Interface To configure CMC services using CMC web interface: 1. In the left pane, click Chassis Overview, and then click Network → Services. The Services Management page is displayed. 2.
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 left pane, go to Chassis Overview, and then click Chassis Controller → Flash Media. 2.
4. Type the group name in the Group Name field, and then click Apply. NOTE: The same rules that apply for a domain name apply to the group name. When the chassis group is created, the GUI automatically switches to the Chassis Group page. The left pane indicates the group by the group name and the lead chassis, and the unpopulated member chassis appear in the left pane. Adding Members To Chassis Group After the Chassis Group is set up, to add members to the group: 1.
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. The lead chassis can be assigned as a leader or member of a new group. If a network issue prevents contact between the leader and the member, the member chassis may not receive the message. In this case, disable the member from the member chassis to complete the removal process.
5. In the Propagation Properties section, select the categories of lead configuration properties to be propagated to member chassis. Select only those setting categories that you want identically configured, across all members of the chassis group. For example, select Logging and Alerting Properties category, to enable all chassis in the group to share the logging and alerting configuration settings of the lead chassis. 6. Click Save.
Table 6. Server Module Inventory Field Descriptions Data Field Example Chassis Name Data Center Chassis Leader Chassis IP Address 192.168.0.1 Slot Location 1 Slot Name SLOT-01 Host Name Corporate Webserver NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Operating System Windows Server 2008 NOTE: Requires a Server Administrator agent running on the Server; otherwise shown as blank. Model PowerEdgeM610 Service Tag 1PB8VF1 Total System Memory 4.
• CPLD • USC • Diagnostics • OS Drivers • RAID • NIC NOTE: The inventory information displayed for the chassis group, member chassis, servers, and server components is updated every time a chassis is added or removed from the group. Viewing Chassis Group Inventory To view the chassis group using CMC web interface, in the left pane, select Group. Click Properties → Firmware Version. The Chassis Group Firmware Version page displays all the chassis in the group.
NOTE: Some configuration files contain unique CMC information (such as the static IP address) that must be modified before you export the file to other CMCs. 1. Use RACADM to query the target CMC that contains the desired configuration. NOTE: The generated configuration file is myfile.cfg. You can rename the file. The .cfg file does not contain user passwords. When the .cfg file is uploaded to the new CMC, you must re-add all passwords. 2.
The parser reads in all of the indexes from the CMC for that group. Any objects within that group are modifications when the CMC is configured. If a modified object represents a new index, the index is created on the CMC during configuration. • You cannot specify a desired index in a .cfg file. Indexes may be created and deleted. Over time, the group may become fragmented with used and unused indexes. If an index is present, it is modified. If an index is not present, the first available index is used.
remains unmodified. Any character to the right of the = (for example, a second =, a #, [, ], and so on) is taken as-is. These characters are valid modem chat script characters. [cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object value} • The .cfg parser ignores an index object entry. You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the first available index for that group. The racadm getconfig -f .
This file is updated as follows: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.9.143 # comment, the rest of this line is ignored cfgNicGateway=10.35.9.1 The command racadm config -f .cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.
Configuring Servers 7 You can configure the following settings of a server: • Slot Names • iDRAC Network Settings • DRAC Virtual LAN Tag Settings • First Boot Device • Server FlexAddress • Remote File Share • BIOS Settings Using Server Clone Configuring Slot Names Slot names are used to identify individual servers. When choosing slot names, the following rules apply: • Names may contain a maximum of 15 non-extended ASCII characters (ASCII codes 32 through 126).
To edit a slot name using the CMC Web interface: 1. In the left pane, go to Chassis Overview → Server Overview → Setup → Slot Names. 2. On the Slot Names page, edit the slot name, in the Slot Name field. 3. To use a server’s host name as slot name, select the Use Host Name for the Slot name option. This overrides the static slot names with the server’s Host Name (or system name), if available. This requires the OMSA agent to be installed on the server.
To enable and set the iDRAC QuickDeploy settings: 1. In the left pane, click Server Overview → Setup → iDRAC. 2. On the Deploy iDRAC page, in the QuickDeploy Settings section, specify the settings mentioned in the following table. For more information about the fields, see the Online Help. Table 7.
Setting Description Starting iDRAC IPv4 Address (Slot 1) Specifies the static IP address of iDRAC in the server, in slot 1 of the enclosure. The IP address of each subsequent iDRAC is incremented by 1 for each slot from slot 1's static IP address. In the case where the IP address plus the slot number is greater than the subnet mask, an error message is displayed. NOTE: The subnet mask and the gateway are not incremented such as the IP address. For example, if the starting IP address is 192.168.0.
3. Click Save QuickDeploy Settings to save the settings. If you have made changes to the iDRAC network setting, click Apply iDRAC Network Settings to deploy the settings to the iDRAC. The QuickDeploy feature only executes when it is enabled, and a server is inserted in the chassis. If Set iDRAC Root Password on Server Insertion and QuickDeploy Enabled are enabled, the user is prompted using the LCD interface to allow or not allow the password change.
• • • • • cfgIPv6LanNetworking cfgRacTuning cfgRemoteHosts cfgSerial cfgSessionManagement For more information about the property default values and ranges, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals. Configuring iDRAC Virtual LAN Tag Settings Virtual LAN (VLAN) tags enable multiple VLANs to coexist on the same physical network cable and to segregate the network traffic for security or load management purposes.
to the server and used as its first boot device of that server. This device can be set as the default first-boot device or an one-time device so that you can boot an image to perform tasks such as running diagnostics or reinstalling an operating system. You can set the first boot device for the next boot only or for all subsequent reboots. You can also set the first boot device for the server.
Setting First Boot Device For Individual Server Using CMC Web Interface NOTE: To set the first boot device for servers, you must have Server Administrator privileges or Chassis Configuration Administrator privileges and iDRAC login privileges. To set the first boot device for individual servers: 1. In the left pane, click Server Overview, and then click the server for which you want to set the first boot device. 2. Go to Setup → First Boot Device. The First Boot Device page is displayed. 3.
3. To connect to a remote file share, click Connect. To connect a remote file share, you must provide the path, user name, and password. A successful operation allows access to the media. Click Disconnect to disconnect a previously-connected remote file share. Click Deploy to deploy the media device. NOTE: Before you click the Deploy button, make sure that you save all the working files, because this action restarts the server.
• Export stored profiles to a remote file share. • Delete stored profiles. • Deploy selected profiles to the target devices using Quick Deploy option. • Display the log activity for recent server profile tasks. Accessing 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 left pane, go to Chassis Overview → Server Overview. Click Setup → Profiles.
3. Click Apply Profile. A warning message is displayed that applying a new server profile overwrites the current settings and also reboots the selected servers. You are prompted to confirm if you want to continue the operation. NOTE: To perform server cloning operations on servers, 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 servers.
Viewing Profile Settings To view Profile settings for a selected server, go to the Server Profiles page. In the Server Profiles section, click View in the Server Profile column for the required server. The View Settings page is displayed. For more information on the displayed settings, see the Online Help. NOTE: The CMC Server Configuration Replication feature retrieves and displays the settings for a specific server, only if the Collect System Inventory on Restart (CSIOR) option is enabled.
Assigning Server Profiles to Slots The Server Profiles page enables you to assign server profiles to slots. To assign a profile to the chassis slots: 1. In the Server Profiles page, go to the Profiles for Quick Deploy section. The current profile assignments are displayed for the slots in the select boxes contained in the Server Profile column. 2. From the drop-down menu, select the profile to assign to the required slot. You can select profiles to apply to multiple slots. . 3. Click Assign.
Launching iDRAC from Server Status Page To launch the iDRAC management console for an individual server: 1. In the left pane, expand Server Overview. All four servers appear in the expanded Servers Overview list. 2. Click the server for which you want to launch the iDRAC Web interface. 3. On the Server Status page, click Launch iDRAC GUI. The iDRAC Web interface is displayed. For information about the field descriptions, see the Online Help.
Configuring CMC To Send Alerts 8 You can set alerts and actions for certain events that occur on the chassis. An event is generated when a device or service’s status has changed or an error condition is detected. If an event matches an event filter and you have configured this filter to generate an alert message (email alert or SNMP trap), then an alert is sent to one or more configured destinations such as email address, IP address, or an external server. To configure CMC to send alerts: 1.
NOTE: To apply chassis events configuration changes, you must have the Alert Configuration privilege. 1. In the left pane, click Chassis Overview → Alerts. 2. On the Chassis Events page, under the Alerts Filter section, select one or more of the following categories: – System Health – Storage – Configuration – Audit 3.
Configuring SNMP Trap Alert Destinations Using CMC Web Interface To configure IPv4 or IPv6 alert destination settings using CMC Web interface: 1. In the left pane, click Chassis Overview → Alerts → Trap Settings. 2. On the Chassis Event Alert Destinations page, type the following: – In the Destination field, type a valid IP address. Use the quad-dotted IPv4 format, standard IPv6 address notation, or FQDN. For example: 123.123.123.123 or 2001:db8:85a3::8a2e:370:7334 or dell.com.
4. Enable traps alerts: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value between 1–4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualified Domain Names (FQDNs). 5.
3. Click Apply to save the settings. 4. Click Send under Test E-mail to send a test email to the specified email alert destination. Configuring EMail Alert Settings Using RACADM To send a test email to an email alert destination using RACADM: 1. Open a serial/Telnet/SSH text console to CMC and log in. 2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 NOTE: Only one filter mask may be set by both SNMP and email alerting.
9 Configuring User Accounts and Privileges You can set up 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. The default user name is rootand the password is calvin. As an administrator, you can set up user accounts to allow other users to access the CMC.
Privilege Description strictly chassis properties relating to the slots rather than the servers themselves. For this reason, slot names and slot priorities can be added or changed whether or not servers are present in the slots. 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. The previous slot name and priority remain with the previous chassis.
Privilege Description granted on the server. Based on the privileges responding from the server, CMC firmware decides if the user has the right to perform the action. Listed below are the privileges and the actions on the server to which the Server Administrator is entitled. These rights are applied only when the chassis user does not have the Server Administrative privilege on the chassis.
User Group Privileges Granted Power User • • • • Server Administrator Test Alert User Debug Command Administrator Fabric A Administrator • • • Login Clear Logs Administrator Chassis Control Administrator (Power commands) Server Administrator Test Alert User Fabric A Administrator • • • Guest User Login Custom Select any combination of the following permissions: • • • • • • • • • None CMC Login User Chassis Configuration Administrator User Configuration Administrator Clear Logs Administrator Chas
Privilege Set Administrator Permissions Power User Permissions Guest User Permissions Debug Command Administrator Yes No No Fabric A Administrator Yes Yes No Modifying Root User Administrator Account Settings For added security, it is strongly recommended that you change the default password of the root (User 1) account. The root account is the default administrative account that is shipped with CMC. To change the default password for the root account: 1.
You can configure up to 16 users in the CMC property database. Before you manually enable a CMC user, verify if any current users exist. If you are configuring a new CMC or if you have used the racadm racresetcfg command, the only current user is root with the password calvin. The racresetcfg subcommand resets all configuration parameters to the default values. Any earlier changes are lost. NOTE: Users can be enabled and disabled over time, and disabling a user does not delete the user from the database.
racadm config -g cfgUserAdmin -i 2 -o cfgUserAdminEnable 1 To verify that the user was successfully added with the correct privileges, run the following command: racadm getconfig –g cfgUserAdmin –i 2 For more information about the RACADM commands, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide available at dell.com/support/manuals. Disabling CMC User When using RACADM, users must be disabled manually on an individual-basis.
• • 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.
NOTE: For more information about user privileges, see Types of Users. Configuring Standard Schema Active Directory To configure CMC for an Active Directory login access: 1. On an Active Directory server (domain controller), open Active Directory Users and Computers Snap-in. 2. Using the CMC Web interface or RACADM: a) Create a group or select an existing group. b) Configure the role privileges. 3. Add the Active Directory user as a member of the Active Directory group to access CMC.
9. If you have enabled Single Sign-On (SSO), in the Kerberos Keytab section, click Browse, specify the keytab file and click Upload. When the upload is complete, a message is displayed indicating a successful or failed upload. 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.
Configuring Active Directory With Standard Schema Using RACADM At the RACADM command prompt, run the following commands: – Using config command: racadm config -g cfgActiveDirectory -o cfgADEnable 1 racadm config -g cfgActiveDirectory -o cfgADType 2 racadm config -g cfgStandardSchema -i -o cfgSSADRoleGroupName racadm config -g cfgStandardSchema -i -o cfgSSADRoleGroupDomain racadm config -g cfgStandardSchema -i -o cfgSSADRol
In this case, you must upload the CA certificate using the following RACADM command: racadm sslcertupload -t 0x2 -f NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog FQDN. Make sure that DNS is correctly configured. Extended Schema Active Directory Overview Using the extended schema solution requires the Active Directory schema extension.
You can create as many or as few association objects as required. However, you must create at least one Association Object, and you must have one RAC device object for each RAC (CMC) on the network that you want to integrate with Active Directory. The Association Object allows as many or as few users and/or groups as well as RAC Device Objects. However, the Association Object only includes one Privilege Object per Association Object.
schema, make sure that you have Schema Admin privileges on the Schema Master Flexible Single Master Operation (FSMO) Role Owner of the domain forest. You can extend your schema using one of the following methods: • Dell Schema Extender utility • LDIF script file If you use the LDIF script file, the Dell organizational unit is not added to the schema.
OID 1.2.840.113556.1.8000.1280.1.7.1.1 This configuration enables CMC to send Lightweight Directory Access Protocol (LDAP) queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellSchemaVersion dellRacType Table 15. delliDRACAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.7.1.2 Description Represents the Dell Association Object. The Association Object provides the connection between the users and the devices.
OID 1.2.840.113556.1.8000.1280.1.1.1.4 SuperClasses User Attributes dellRAC4Privileges Table 18. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description The main class from which all Dell products are derived. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 19.
Assigned OID/Syntax Object Identifier Single Valued 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.7) Attribute: dellIsServerResetUser TRUE Description: TRUE if the user has Server Reset rights on the device. OID: 1.2.840.113556.1.8000.1280.1.1.2.7 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.
Assigned OID/Syntax Object Identifier Single Valued OID: 1.2.840.113556.1.8000.1280.1.1.2.14 Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) Attribute: dellPermissionsMask1 OID: 1.2.840.113556.1.8000.1280.1.6.2.1 Integer (LDAPTYPE_INTEGER) Attribute: dellPermissionsMask2 OID: 1.2.840.113556.1.8000.1280.1.6.2.
4. Select Privilege Object and click OK. 5. Right-click the privilege object that you created, and then select Properties. 6. Click the RAC Privileges tab and assign the privileges for the user or group. For more information about CMC user privileges, see Types of Users. Creating Association Object The Association Object is derived from a Group and must contain a Group Type. The Association Scope specifies the Security Group Type for the Association Object.
NOTE: For information about the various fields, see the Online Help. 1. In the left pane, click, Chassis Overview → User Authentication → Chassis Overview → Directory Services. 2. Select Microsoft Active Directory (Extended Schema). The settings to be configured for extended schema is displayed on the same page. 3. In the Common Settings section, specify the following: – Select Enable Active Directory and enter the timeout value for Active Directory in the AD Timeout field.
11. If Use DHCP for CMC Network Interface IP Address, is enabled, do one of the following: – Select Use DHCP to Obtain DNS Server Addressesto enable the DNS server addresses to be obtained automatically by the DHCP server. – Manually configure a DNS server IP address by leaving the Use DHCP to Obtain DNS Server Addresses check box unchecked and then typing your primary and alternate DNS server IP addresses in the fields provided. 12. Click Apply Changes.
To enable the LDAP user to access a specific CMC card, the role group name and its domain name must be configured on the specific CMC card. You can configure a maximum of five role groups in each CMC. A user has the option to be added to multiple groups within the directory service. If a user is a member of multiple groups, then the user obtains the privileges of all their groups. For information about the privileges level of the role groups and the default role group settings, see Types of Users.
3. Specify the following: NOTE: For information about the various fields, see the Online Help. – Common Settings – Server to use with LDAP: * Static server — Specify the FQDN or IP address and the LDAP port number. * 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.
CMC can be configured to optionally query a DNS server for SRV records. If the cfgLDAPSRVLookupEnable property is enabled, the cfgLDAPServer property is ignored. The following query is used to search the DNS for SRV records: _ldap._tcp.domainname.com ldap in the above query is the cfgLDAPSRVLookupServiceName property. cfgLDAPSRVLookupDomainName is configured to be domainname.com.
10 Configuring CMC For Single Sign-On Or Smart Card Login This section provides information to configure CMC for Smart Card login and Single Sign-On (SSO) login for Active Directory users. SSO uses Kerberos as an authentication method allowing users, who have signed in as an automatic- or single sign-on to subsequent applications such as Exchange.
• For Single Sign-On or smart card login, the client system must be a part of the Active Directory domain and Kerberos Realm. CMC • Each CMC must have an Active Directory account. • CMC must be a part of the Active Directory domain and Kerberos Realm. Prerequisites For Single Sign-On Or Smart Card Login The pre-requisites to configure SSO or Smart Card logins are: • Set up the kerberos realm and Key Distribution Center (KDC) for Active Directory (ksetup).
For information about configuring CMC for Extended Schema Active Directory, see Extended Schema Active Directory Overview. Configuring Browser For SSO Login Single Sign-On (SSO) is supported on Internet Explorer versions 6.0 and later, and Firefox versions 3.0 and later. NOTE: The following instructions are applicable only if CMC uses Single Sign-On with Kerberos authentication. Internet Explorer To configure Internet Explorer for Single Sign-On: 1.
NOTE: For information about the options, see the Online Help. 1. While configuring Active Directory to set up user account, perform the following additional steps: – Upload the keytab file. – To enable SSO, select the Enable Single Sign-On option. – To enable smart card login, select the Enable Smart-Card Login option. NOTE: If these two options are selected, all command line out-of-band interfaces, including secure shell (SSH), Telnet, Serial, and remote RACADM remain unchanged . Click Apply. 2.
11 Configuring CMC to Use Command Line Consoles This section provides information about the CMC command line console (or serial/Telnet/Secure Shell console) features, and explains how to set up the system so that you can perform systems management actions through the console. For information about using the RACADM commands in CMC through the command line console, see Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide.
Using Telnet Console With CMC You can have up to four Telnet sessions with CMC at a time. If your management station is running Microsoft Windows XP or Microsoft Windows Server 2003, you may experience an issue with the characters in a CMC Telnet session. This issue may occur as a frozen login where the return key does not respond and the password prompt does not appear. To fix this issue, download hotfix 824810 from support.microsoft.com.
Scheme Type Scheme • • • • • • RIJNDAEL192-CBC AES128-CBC RIJNDAEL128-CBC BLOWFISH-128-CBC 3DES-192-CBC ARCFOUR-128 Message Integrity • • • • HMAC-SHA1-160 HMAC-SHA1-96 HMAC-MD5-128 HMAC-MD5-96 Authentication Password Configure Public Key Authentication Over SSH You can configure up to six public keys that can be used with the service username over an SSH interface.
To use the PuTTY Key Generator to create a basic key for clients running Windows: 1. Start the application and select SSH-2 RSA or SSH-2 DSA for the type of key to generate (SSH-1 is not supported). 2. Enter the number of bits for the key. The number should be between 768 and 4096. NOTE: CMC may not display a message if you add keys less than 768 or greater than 4096, but when you try to log in, these keys it fails. 3. Click Generate and move the mouse in the window as directed.
To add a public key using the text upload option, enter: racadm sshpkauth –i svcacct –k 1 –p 0xfff –t “” Deleting Public Keys To delete a public key, run the following command: racadm sshpkauth –i svcacct –k 1 –d To delete all public keys, run the following command: racadm sshpkauth –i svcacct –k all –d Configuring Terminal Emulation Software CMC supports a serial text console from a management station running one of the following types of terminal emulation software: • Linux Minicom.
12. To exit Minicom, press , , . Make sure that the Minicom window displays a login prompt. When the login prompt appears, your connection is successful. You are now ready to login and access the CMC command line interface. Required Minicom Settings See the following table to configure any version of Minicom. Table 22.
When you reference the IOM in the connect command, the IOM is mapped to switch as shown in the following table. Table 23. Mapping IO Module to Switches IO Module Label Switch A1 switch-a1 or switch- 1 NOTE: At a time, there can be only one IOM connection per chassis. NOTE: You cannot connect to pass-throughs from the serial console. To connect to a managed-server serial console, run the command connect server-n, where n is 1–4. You can also use the racadm connect server-n command.
Configuring Windows for Serial Console Redirection There is no configuration necessary for servers running the Microsoft Windows Server versions, starting with Windows Server 2003. Windows receives information from the BIOS, and enable the Special Administration Console (SAC) console one COM1. Configuring Linux for Server Serial Console Redirection During Boot The following steps are specific to the Linux GRand Unified Bootloader (GRUB). Similar changes are necessary for using a different boot loader.
3. If the /etc/grub.conf contains a splashimage directive, comment it out. The following example shows the changes described in this procedure. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes # to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, e.g. # root (hd0,0) # kernel /boot/vmlinuz-version ro root= /dev/sdal # initrd /boot/initrd-version.
# # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you # do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.
vc/7 vc/8 vc/9 vc/10 vc/11 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 ttyS1 147
Using FlexAddress and FlexAdress Plus Cards 12 This section provides information about FlexAddress, FlexAddress Plus Cards, and configuring and using these the cards. NOTE: An Enterprise License must be installed on the CMC to use the Flexaddress feature. About FlexAddress The FlexAddress feature is an optional upgrade that allows server modules to replace the factoryassigned World Wide Name and Media Access Control (WWN/MAC) network IDs with WWN/MAC IDs provided by the chassis.
About FlexAddress Plus The FlexAddress Plus is a new feature added to the feature card version 2.0. It is an upgrade from FlexAddress feature card version 1.0. FlexAddress Plus contains more MAC addresses than the FlexAddress feature. Both features allow the chassis to assign World Wide Name/Media Access Control (WWN/MAC) addresses to Fibre Channel and Ethernet devices. Chassis assigned WWN/MAC addresses are globally unique and specific to a server slot.
4. Insert the SD card into the passive module for a redundant CMC module system or into the single CMC module for a non-redundant system. For instructions about the SD card installation, see the Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification document. NOTE: The SD card contains a FlexAddress feature.
Table 25. Status Messages Returned by the 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 feature card inserted is valid and contains the following feature(s) FlexAddress: bound. No action required.
If you run the deactivation command without installing an SD card, or with a card from a different chassis installed, the feature is deactivated and change is not made to the card. To deactivate the FlexAddress feature and restore the SD card: racadm feature -d -c flexaddress The command returns the following status message if it is successfully deactivated: feature FlexAddress is deactivated on the chassis successfully.
NOTE: If Fabric A is enabled, unpopulated slots display chassis-assigned MAC addresses for Fabric A. WWN/MAC Addresses Displays FlexAddress configuration for each slot in the chassis. Information displayed includes: • • • • Slot number and location. FlexAddress is active or not active. Fabric type. Server-assigned and chassis-assigned WWN/MAC addresses in use. A green check mark indicates the active address type, either server-assigned or chassis-assigned.
Chassis Management Controller (CMC) Secure Digital (SD) Card Technical Specification document available at dell.com/support/manuals. The server must be turned off before you begin configuration. You can enable or disable FlexAddress on a per-fabric–basis. Additionally, you can enable or disable the feature on a per-slot–basis. After you enable the feature on a per-fabric–basis, you can select slots to be enabled.
To enable or disable slots, use the following RACADM command: racadm setflexaddr [-i where, = 1 or 4 and = 0 or 1 0 is disable and 1 is enable. For more information about the setflexaddr command, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide. NOTE: If you purchase the FlexAddress or FlexAddressPlus feature with your Dell PowerEdge VRTX, it is pre-installed and enabled for all slots and fabrics.
Situation Command Output SD card in the active CMC module that is not bound to any service tag. $racadm featurecard -s The feature card inserted is valid and contains the following feature(s) FlexAddress:not bound FlexAddress feature not active on the chassis for any reason (No SD card inserted/ corrupt SD card/ after feature deactivated /SD card bound to a different chassis).
bound by the terms of this agreement. If you do not agree to these terms, promptly return all Software items (disks, written materials, and packaging) and delete any preloaded or embedded Software. You may use one copy of the Software on only one computer at a time. If you have multiple licenses for the Software, you may use as many copies at any time as you have licenses. "Use" means loading the Software in temporary memory or permanent storage on the computer.
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.
Managing Fabrics 13 The chassis supports a fabric type, which is Fabric A. Fabric A is used by the single I/O Module, and is always connected to the on-board Ethernet adapters of the servers. The chassis has only one I/O module (IOM), where the IOM is a pass-through or switch module. The I/O Module is classified as group A. Chassis IOM uses a discrete data path called Fabric, and it is named A. The Fabric A supports only Ethernet.
Configuring Network Settings for IOM You can specify the network settings for the interface used to manage the IOM. For Ethernet switches, the out-of-band management port (IP address) is configured. The in-band management port (that is, VLAN1) is not configured using this interface. Before configuring the network settings for the IOM, make sure the IOM is turned on. To configure the network setting of IOM in Group A, you must have the Fabric A Administrator privileges.
Enabling or Disabling LED Blinking for I/O Modules For information to enable LED blinking for I/O Module(s), see Configuring LEDs to Identify Components on the Chassis.
Managing and Monitoring Power 14 The Dell PowerEdge VRTX chassis is the most power-efficient modular server enclosure. It is designed to include highly-efficient power supplies and fans, has an optimized layout for the air to flow more easily through the system, and contains power-optimized components throughout the enclosure.
• Power supply redundancy Grid Redundancy Policy The purpose of the Grid redundancy policy is to enable a modular enclosure system to operate in a mode in which it can tolerate AC power failures. These failures may originate in the AC power grid, the cabling and delivery, or a PSU itself. When you configure a system for Grid redundancy, the PSUs are divided into grids: PSUs in slots 1 and 2 are in the first grid while PSUs in slots 3 and 4 are in the second grid.
increased PSU life, and reduced heat generation. To use this feature, you must have an Enterprise License. CMC monitors total enclosure power allocation, and moves the PSUs into Standby state, causing the total power allocation of the chassis to be delivered through fewer PSUs. As the online PSUs are more efficient when running at higher utilization, it improves their efficiency and longevity of the standby PSUs.
Grid Redundancy In Grid redundancy mode with four PSUs, all four PSUs are active. The two PSUs must connect to one AC power grid, while the other two PSUs are connect to the other AC power grid. CAUTION: To avoid a system failure, and for Grid redundancy to work effectively, there must be a balanced set of PSUs properly cabled to separate AC grids. If one AC grid fails, the PSUs on the functioning AC grid take over, without interrupting the servers or infrastructure.
enclosure can supply. To help datacenters allocate power for their enclosures, the PowerEdge VRTX allows you to specify a System Input Power Cap to make sure that the overall chassis AC power draw stays within a given threshold point. CMC first makes sure that enough power is available to run the fans, I/O module, storage adapters, physical disk drive, main board, and CMC itself. This power allocation is called the Input Power Allocated to Chassis Infrastructure.
to the minimum value, in order to accommodate the higher priority servers. Therefore, after the available power for allocation is exhausted, CMC reclaims power from lower or equal priority servers until they are at their minimum power level. NOTE: I/O module, fans, and mainboard, physical disk drives, storage adapters are given the highest priority. CMC reclaims power only from the lower-priority devices to meet the power needs of a higher-priority device or server.
NOTE: You can also view the power redundancy status under Power Supplies. Viewing Power Consumption Status Using RACADM To view power consumption status using RACADM: Open a serial/Telnet/SSH text console to CMC, log in, and type: racadm getpminfo Viewing Power Budget Status Using CMC Web Interface To view power budget status using CMC Web interface, in the left pane go to Chassis Overview and click Power → Budget Status.
remove more than one PSU, CMC again evaluates the power requirements when the second PSU is removed to determine the firmware response. If power requirements are still not met, CMC may turn off the low-priority servers. Limits • CMC does not support automated power-down of a low-priority server to allow turning-on of a higher priority server; however, you can perform user-initiated turn-offs. • Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis.
Table 29. Chassis Impact from PSU Failure or Removal PSU Configuration Dynamic PSU Engagement Firmware Response Grid Redundancy Disabled CMC alerts you about loss of Grid redundancy. Power Supply Redundancy Disabled CMC alerts you about loss of power supply redundancy. Grid Redundancy Enabled CMC alerts you about loss of Grid Redundancy. PSUs in standby mode (if any) are turned on to compensate for power budget lost from the PSU failure or removal.
You can configure the following: • System Input Power Cap • Redundancy Policy • Enable Dynamic Power Supply Engagement • Disable Chassis Power Button • Max Power Conservation Mode • Remote Power Logging • Remote Power Logging Interval • Server Based Power Management Power Conservation and Power Budget CMC conserves power when the user-configured maximum power limit is reached.
• Overall power consumption exceeds the configurable System Input Power Cap. • A power failure occurs in a non-redundant configuration. 110V PSUs AC Operation By default, the 110V PSU AC Operation feature is available. However, a combination of 110V and 220V operation is not supported. If CMC detects that both voltages are input, one voltage value is selected and those power supplies connected to the other voltage level are turned off and indicated as not functioning.
Configuring Power Budget and Redundancy Using CMC Web Interface NOTE: To perform power management actions, you must have the Chassis Configuration Administrator privilege. To configure power budget: 1. In the left pane, click Chassis Overview → Power → Configuration. 2. On the Budget/Redundancy Configuration page, select any or all of the following properties as appropriate. For information about the field descriptions, see the Online Help.
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 1 (Grid Redundancy), and 2 (Power Supply Redundancy). The default value is 2.
– To enable remote power management by Open Manage Power Center (OPMC), type: racadm config -g cfgChassisPower -o cfgChassisServerBasedPowerMgmtMode 1 – To restore CMC power management, type: racadm config -g cfgChassisPower -o cfgChassisServerBasedPowerMgmtMode 0 For information about RACADM commands for chassis power, see the config, getconfig, getpbinfo, and cfgChassisPower sections in the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide.
Executing Power Control Operations on a Server You can remotely perform power management actions for multiple servers at a time or an individual server in the chassis. NOTE: To perform power management actions, you must have the Chassis Configuration Administrator privilege. Executing Power Control Operations for Multiple Servers Using CMC Web Interface To execute power control operation for multiple servers using the Web interface: 1. In the left pane, click Server Overview → Power.
Executing Power Control Operations on the IOM Using RACADM To execute power control operations on the IOM using RACADM, open a serial/Telnet/SSH text console to CMC, log in, and type: racadm chassisaction -m switch where indicates the operation you want to execute: power cycle.
Managing Chassis Storage 15 On the Dell PowerEdge VRTX, you can perform the following operations: • View the status of physical disks drives and storage controllers. • View the properties of controllers, physical disk drives, virtual disks, and enclosures. • Set up controllers, physical disk drives, and virtual disks. • Assign virtual adapters. • Troubleshoot controller, physical disk drives, and virtual disks. • Update storage components.
Viewing Fault-tolerant Troubleshooting Information of SPERC Using CMC Web Interface To view the attributes that indicate the correct functioning of fault-tolerant features of a SPERC: 1. In the left pane, click Chassis Overview → Storage → Troubleshooting → Setup Troubleshooting. The Storage Setup Troubleshooting page is displayed. 2. On the Storage Setup Troubleshooting page, you can: – View the following attributes when the controller is in fault-tolerant mode: * Two Shared PERCs detected.
• Virtual disks are created and they are assigned as Virtual Adapter 1, Virtual Adapter 2, Virtual Adapter 3, or Virtual Adapter 4. For more information, see Applying Virtual Adapter Access Policy to Virtual Disks. NOTE: • You can map only one virtual adapter to one server at a time. • Without an appropriate license, you can unmap a VA–server assignment, or map the VA to the default serve, only. • The default mapping is VA1–Server Slot 1, VA2–Server Slot 2, VA3–Server Slot 3, and VA4–Server Slot 4.
failover process since the redundant components(controllers) are not used during normal operating conditions. High Availability with fault-tolerance provides the following benefits: • Provides uptime for all storage applications even when a controller stops functioning. • Provides access to critical functions of the chassis at all times. • Enables server to handle situations when controller stops functioning are becomes faulty.
To import or clear the foreign configuration: 1. In the left pane, click Chassis Overview → Storage → Controllers → Setup. 2. On the Controller Setup page, in the Foreign Configuration section, for the respective controller, click: – Clear Foreign Configuration to clear the existing configuration of the disk. – Import/Recover to import the disk with the foreign configuration.
Viewing Physical Disk Properties Using the CMC Web Interface Make sure that physical disks are installed on the chassis. To view the properties of physical disk drives: 1. In the left pane, go to Chassis Overview → Storage → Physical Disks. The Properties page is displayed. 2. To view properties of all the physical disk drives, under the Physical Disks section, click the .
For more information about using RACADM commands, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide. Recovering Physical Disks To recover a physical disks: 1. In the CMC Web Interface, go to Chassis Overview → Storage → Physical Disks → Setup. 2.
3. Click Apply. You can now assign virtual adapters to server slots. For more information, see the Assigning Virtual Adapters to Slots section in this User's Guide. Modifying Virtual Disk Properties Using CMC Web Interface To modify the virtual disk properties: 1. In the left pane, click Chassis Overview → Storage → Virtual Disks → Manage. 2. On the Manage Virtual Disks page, from the Virtual Disk Actions drop-down menu, select one of the following actions, and then click Apply.
Managing PCIe Slots 16 By default, all slots are unmapped. You can do the following: • View the status of all PCIe Slots in the chassis. • Assign or remove an assigned PCIe slot from the servers. Consider the following before assigning a PCIe slot to a server: • An empty PCIe slot cannot be assigned to a server that is turned on. • A PCIe slot with an adapter assigned to a server cannot be assigned to another server if the currentlyassigned server (source) is turned on.
• You can map the server slots to any of the 8 PCIe slots. • A full-height server has both upper and lower mezzanines populated. Else, during POST will stop when the or is displayed on the page for you to press any one of the keys. • For full-height servers you can map a maximum of two PCIE slots to upper and two to lower mezzanines. By default, all PCIe mappings to slot 3 will go to the lower mezzanines. • Server slot number is displayed as Slot-01, Slot-02, and so on.
• The powered state of PCIe cards is extended for a pre-defined time period in the following scenarios: – After the associated server is turned off. – After a CMC stops functioning. – After a CMC or server is restarted. NOTE: At the end of the time period, the PCIe cards power-down. This power-down enables the blade node to DC power cycle without causing a long power-up delay associated with PCIe card power-on and initialization.
Configuring PCIe Ride-through Properties Status Using RACADM You can configure the PCIe power ride-through properties, by running the following commands: • To disable the Ride-through feature, run the command, racadm setpciecfg ridethru –d • To enable the Ride-through feature, run the command, racadm setpciecfg ridethru –e • To reset the Ride-through timeout property, run the command, racadm setpciecfg ridethru – t • To set the acceptable timeout range, run the command, racadm setpciecfg he
Troubleshooting and Recovery 17 This section explains how to perform tasks related to recovering and troubleshooting problems on the remote system using the CMC web interface. • Viewing chassis information. • Viewing the event logs. • Gathering configuration information, error status, and error logs. • Using the diagnostic console. • Managing power on a remote system. • Managing Lifecycle Controller jobs on a remote system. • Reset components.
Subsystem RACADM Command General System/RAC information getsysinfo Session information getssninfo Sensor information getsensorinfo Switches information (IO Module) getioinfo Mezzanine card information (Daughter card) getdcinfo All modules information getmodinfo Power budget information getpbinfo KVM information getkvminfo NIC information (CMC module) getniccfg Redundancy information getredundancymode Trace log information gettracelog RAC event log getraclog System event log getsel
allocations for the chassis to maintain Grid redundancy. (For full Grid Redundancy operation, make sure that a full PSU configuration of four power supplies is available.) – Resolution B: Check if all power supplies are properly connected to the two AC grids; power supplies in side 1 must be connected to one AC grid, those in side 2 must be connected to the other AC grid, and both AC grids must be working. Grid Redundancy is lost when one of the AC grids is not functioning.
– Resolution: To avoid a future power supply failure causing servers to power off, make sure that the chassis has at least three power supplies and is configured for the Power Supply Redundancy policy to prevent PSU failure from impacting server operation. • Problem: Overall server performance decreases when the ambient temperature increases in the data center.
NOTE: Since the log is saved as a text file, the graphical images used to indicate severity in the user interface do not appear. In the text file, severity is indicated with the words OK, Informational, Unknown, Warning, and Severe. The date and time entries appear in ascending order. If appears in the Date/Time column, it means that the event occurred during the turn-on or turn—off of any of the modules, when a date or time is not available. To clear the hardware log, click Clear Log.
To access the Diagnostic Console: 1. In the left pane, click Chassis Overview → Troubleshooting → Diagnostics. The Diagnostic Console page displays. 2. In the Command text box, type a command and click Submit. For information about the commands, see the Online Help. The diagnostic results page appears. Resetting Components You can reset the active CMC, or virtually reseat servers making them to behave as if they were removed and reinserted.
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. • Invalid host name or IP address may have been accidentally entered. • Network connectivity problem that prevents CMC from communicating with any of the configured NTP servers. • DNS problem, preventing any of the NTP server host names from being resolved.
Interpreting LED Colors and Blinking Patterns The LEDs on the chassis provide the following status of a component: • Steadily glowing green LEDs indicate that the component is turned on. If the green LED is blinking, it indicates a critical but routine event, such as a firmware upload, during which the unit is not operational. It does not indicate a fault. • 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.
Component LED Color, Blinking Pattern Status IOM (Pass through) Green, glowing steadily Turned on Green, blinking Not used 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 Turned off Amber, glowing steadily Fan type not recognized, update the CMC firmware Amber, blinking Fan fault; t
– Verify that the CMC card is seated properly. You can release or pull the ejector handle, remove the CMC, reinstall the CMC making sure that the board is inserted all the way and the latch closes correctly. • Lower-left LED — This LED is multi-colored. When CMC is active and running, and there are no problems, the bottom LED is blue. If it is amber, a fault is detected. The fault may be caused by any of the following three events: – A core failure. In this case, the CMC board must be replaced.
NOTE: In recover mode, you cannot ping CMC normally because there is no active network stack. The recover ping command allows you to ping to the TFTP server to verify the LAN connection. You may need to use the recover reset command after setniccfg on some systems. Troubleshooting Network Problems The internal CMC trace log allows you to debug CMC alerts and networking. You can access the trace log using the CMC Web interface or RACADM.
Using LCD Panel Interface 18 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 2. LCD Display 1. 3. LCD screen Scroll buttons (4) 2.
Table 32. LCD Panel Navigational Icons Icon Normal Icon Highlighted Icon Name and Description Back — Highlight and press the center button to return to the previous screen. Accept/Yes — Highlight and press the center button to accept a change and return to the previous screen. Skip/Next — Highlight and press the center button to skip any changes and go to the next screen. No — Highlight and press the center button to answer "No" to a question and go to the next screen.
DVD Mapping By using this page, you can view the DVD to server mapping information, map another server to the DVD drive on the chassis, or unmap the existing connection. To give a server access to the DVD, select DVD mapping from the main menu, navigate to the required server, and then press the center Check button. The DVD drive can be mapped to the server slot only if the DVD is enabled for that server slot. DVD drive can also be unmapped to prevent the use by any of the server slots.
LCD Language The LCD Language screen allows you to select the language used for LCD panel messages. The currently active language is highlighted with a light blue background. 1. Use the up, down, left, and right arrow buttons to highlight the desired language. 2. Press the center button. The Accept icon appears and is highlighted. 3. Press the center button to confirm the change. The LCD Setup menu is displayed.
Status information on the LCD includes descriptive information about the modules in the chassis. The tables in this section describe the information that is displayed for each component. LCD Module and Server Status Information The tables in this section describe status items that are displayed on the front panel LCD for each type of component in the chassis. Table 33. CMC Status Item Description Name/Location Example: CMC1, CMC2. No Errors If there are no errors, No Errors is displayed.
Table 35. Fan Status Item Description Name/Location Example: Fan1, Fan2, and so on. Error Messages If there are no errors, No Errors is displayed. Else, error messages are listed where critical ones are first listed, and then the warning-related. RPM Current fan speed in RPM. Table 36. PSU Status Item Description Name/Location Example: PSU1, PSU2, and so on. Error Messages If there are no errors, No Errors is displayed.
Item Description Unmapped Displayed if the KVM is not mapped to any of the servers. Table 39. DVD Mapping Status Item Description Server Displays a list of servers to which the DVD can be mapped. Error Messages If there are no errors, No Errors is displayed. Else, error messages are listed where critical ones are first listed, and then the warningrelated. Mapped Displays a list of servers mapped to a DVD, if any. Slot Indicates the server slot to which the DVD is mapped to.
Table 42. PCIe Card Status Item Description PCIe Card Displays the PCIe Card name in the format PCIe Card , where 'n' is the PCIe Card number. Example: PCIe Card 1, PCIe Card 2, and so on. Error Messages If there are no errors, No Errors is displayed. Else, error messages are listed where critical ones are first listed, and then the warning-related. Working Status On or Off — Indicates whether the PCIe Card is functioning. Name: Name of the PCIe Card.
Item Description BIOS Version Server BIOS firmware version. Last POST Code Displays the last server BIOS POST code messages string. iDRAC Firmware Version Displays if iDRAC finished booting. NOTE: iDRAC version 1.01 is displayed as 1.1. There is no iDRAC version 1.10. IP4 Displays the current IPv4 enabled state. IP4 Address: Only displays if IPv4 is enabled. IP6 Only displays if iDRAC supports IPv6. Displays current IPv6-enabled state.
Frequently Asked Questions 19 This section lists the frequently asked questions about the following: • RACADM • Managing and Recovering a Remote System • Active Directory • FlexAddress and FlexAddressPlus • IOM RACADM After performing a CMC reset (using the RACADM racreset subcommand), when a command is entered, the following message is displayed: racadm Transport: ERROR: (RC=-1) What does this message mean? Another command must be issued only after CMC completes the reset.
The CMC web server is reset after the following occurrences: • Changing the network configuration or network security properties using the CMC web user interface. • The cfgRacTuneHttpsPort property is changed (including when a config -f changes it). • racresetcfg is used or a chassis configuration backup is restored. • CMC is reset. • A new SSL server certificate is uploaded. My DNS server doesn’t register my CMC? Some DNS servers only register names with a maximum of 31 characters.
4. Type a CMC name in the DNS CMC Name field. 5. Click Apply Changes. Active Directory Does Active Directory support CMC login across multiple trees? Yes. The CMC’s Active Directory querying algorithm supports multiple trees in a single forest. Does the login to CMC using Active Directory work in mixed mode (that is, the domain controllers in the forest run different operating systems, such as Microsoft Windows 2000 or Windows Server 2003)? Yes.
Feature Card Chassis Service Tag = YYYYYYYY An entry is added to the CMC log that states: cmc : feature 'FlexAddress@YYYYYYYY' not activated; chassis ID='XXXXXXXX' What happens if the feature card is removed and a non-FlexAddress card is installed? No activation or modifications to the card should occur. The card is ignored by CMC.
This is a browser caching issue. Log off from the browser and relaunch. What happens to FlexAddress if I need to reset my chassis configuration using the RACADM command, racresetcfg? The FlexAddress feature will still be activated and ready to use. All fabrics and slots are selected as default. NOTE: It is highly recommended that you turn off your chassis before running the RACADM command racresetcfg.
