PowerEdge FX2 Chassis Management at Server

Transcription

1 PowerEdge FX2 Chassis Management at Server Dell Engineering and Technical Marketing Chris Poblete, Rajeswari Ayyaswamy March 2015

2 THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. PRODUCT WARRANTIES APPLICABLE TO THE DELL PRODUCTS DESCRIBED IN THIS DOCUMENT MAY BE FOUND AT: Performance of network reference architectures discussed in this document may vary with differing deployment conditions, network loads, and the like. Third party products may be included in reference architectures for the convenience of the reader. Inclusion of such third party products does not necessarily constitute Dell s recommendation of those products. Please consult your Dell representative for additional information. Trademarks used in this text: Dell, the Dell logo, Dell Boomi, Dell Precision,OptiPlex, Latitude, PowerEdge, PowerVault, PowerConnect, OpenManage, EqualLogic, Compellent, KACE, FlexAddress, Force10 and Vostro are trademarks of Dell Inc. Other Dell trademarks may be used in this document. Cisco Nexus, Cisco MDS, Cisco NX- 0S, and other Cisco Catalyst are registered trademarks of Cisco System Inc. EMC VNX, and EMC Unisphere are registered trademarks of EMC Corporation. Intel, Pentium, Xeon, Core and Celeron are registered trademarks of Intel Corporation in the U.S. and other countries. AMD is a registered trademark and AMD Opteron, AMD Phenom and AMD Sempron are trademarks of Advanced Micro Devices, Inc. Microsoft, Windows, Windows Server, Internet Explorer, MS-DOS, Windows Vista and Active Directory are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell Inc. in the United States and other countries. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Citrix, Xen, XenServer and XenMotion are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware, Virtual SMP, vmotion, vcenter and vsphere are registered trademarks or trademarks of VMware, Inc. in the United States or other countries. IBM is a registered trademark of International Business Machines Corporation. Broadcom and NetXtreme are registered trademarks of Broadcom Corporation. Qlogic is a registered trademark of QLogic Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and/or names or their products and are the property of their respective owners. Dell disclaims proprietary interest in the marks and names of others. 2 PowerEdge FX2 Chassis Management at Server

3 Table of contents 1 Chassis Management at Server Overview How do you configure CMAS? Configure CMAS in CMC Configure CMAS in idrac Configure Shared Component Update in idrac What can you do with CMAS? Configure CMC networking from server Chassis sensor inventory and monitoring from idrac CMC firmware update from idrac CMC event proxy via idrac CMC racadm command proxy via idrac A Appendix A.1 Glossary A.2 Troubleshooting A.3 Additional resources PowerEdge FX2 Chassis Management at Server

4 1 Chassis Management at Server Overview Chassis Management at Server, or CMAS, is the ability to manage and monitor the server and the chassis from the server s idrac. It breaks the tradition of one way chassis-server management where idrac manages only the server while CMC manages the chassis plus a limited server management such as power control. PowerEdge FX2 is unique because it allows shared infrastructure management in the server s idrac through CMAS. How is CMAS useful? a. CMAS is useful out of the box to configure CMC networking from a server during POST. b. CMAS provides chassis sensor inventory and monitoring from the server s idrac. c. CMAS allows CMC firmware update from the server s idrac. d. CMAS allows CMC event proxy via the server s idrac. e. CMAS allows CMC racadm command proxy via the server s idrac. The following table shows the hardware and software requirements for CMAS feature. Component Chassis Chassis Management Controller Sleds Management Controller Requirement PowerEdge FX2 PowerEdge FX2s CMC version 1.10 or later PowerEdge FM120 PowerEdge FC430 PowerEdge FC630 PowerEdge FC830 idrac7 version or later idrac8 version or later 4 PowerEdge FX2 Chassis Management at Server

5 2 How do you configure CMAS? Chassis Management at Server feature requires enablement from two sides. The CMAS setting must be enabled both in CMC and in idrac for the feature to work. The default CMAS setting on both sides is Enabled. That means you are able to use the CMAS capabilities out of the box or when you reset configurations to default. 2.1 Configure CMAS in CMC In CMC, Chassis Management at Server feature supports the following settings: Mode None Monitor Manage and Monitor Description Disables CMAS feature Enables read-only access to chassis shared infrastructure data from idrac Enables chassis shared infrastructure management from idrac (default value) Note: To modify CMAS in CMC, the user must have the Login and Chassis Configuration privileges. The settings can be configured using racadm or the CMC web UI. Using racadm Use the property cfgractunechassismgmtatserver from group cfgractuning. This property is numeric. The numeric descriptions is as follows: Value Description 0 None 1 Monitor 2 Manage and Monitor (default value) Example command to get the current value: $ racadm getconfig -g cfgractuning -o cfgractunechassismgmtatserver Example command to configure a new value (example Monitor): $ racadm config -g cfgractuning -o cfgractunechassismgmtatserver 1 Using web UI Login to CMC web UI and go to Chassis Overview > Setup > General > General Chassis Settings and look for the property Chassis Management at Server Mode. 5 PowerEdge FX2 Chassis Management at Server

6 Figure 1 Configure CMAS in CMC 2.2 Configure CMAS in idrac The CMAS configuration in idrac supports the following settings: Mode Disabed Enabled Description Disables CMAS feature for this idrac Allow chassis shared infrastructure management from this idrac Note: To modify CMAS setting in idrac, the user must have the Server Control privilege. License required is base license. The settings can be configured using racadm or the CMC web UI. 6 PowerEdge FX2 Chassis Management at Server

7 Using racadm To configure CMAS, use the property System.ChassisControl.ChassisManagementMonitoring. The property may be set as numeric or as enumeration. Use the following table for reference: Numeric Value Enumeration Value 0 Disabled 1 Enabled (default value) Example command to get the current value: /admin1-> racadm get System.ChassisControl.ChassisManagementMonitoring Example command to configure a new value (example Enabled): /admin1-> racadm set System.ChassisControl.ChassisManagementMonitoring 1 Using web UI Login to idrac web UI and go to Overview > idrac Settings > CMC > Chassis Management at Server and look for the Capability from idrac. 7 PowerEdge FX2 Chassis Management at Server

8 Figure 2 Configure CMAS in idrac 2.3 Configure Shared Component Update in idrac Shared Component Update is a feature that allows users to update CMC firmware from idrac through the Chassis Management at Server feature. Shared Component Update in idrac supports the following settings: Mode Disabed Enabled Description Disables shared component update from idrac Allow CMC firmware update through host OS and Lifecycle Controller from idrac. Prerequisite: Property System.ChassisControl.ChassisManagementMonitoring must be Enabled first. 8 PowerEdge FX2 Chassis Management at Server

9 Note: To modify Shared Component Update setting in idrac, the user must have the Server Control privilege. License required is base license. Requires idrac firmware version or later The settings can be configured using racadm or the CMC web UI. Using racadm To configure Shared Component Update, use the property idrac.update.enablesharedcompupdate. The property may be set as numeric or as enumeration. Use the following table for reference: Numeric Value Enumeration Value 0 Disabled (default value) 1 Enabled Example command to get the current value: /admin1-> racadm get idrac.update.enablesharedcompupdate Example command to configure a new value (example Enabled): /admin1-> racadm set idrac.update.enablesharedcompupdate 1 Using web UI Login to idrac web UI and go to Overview > idrac Settings > Update and Rollback > Firmware > Settings > CMC Firmware Updating Settings and look for the Allow CMC Updates through OS and Lifecycle Controller. 9 PowerEdge FX2 Chassis Management at Server

10 Figure 3 Configure shared component update in idrac 10 PowerEdge FX2 Chassis Management at Server

11 3 What can you do with CMAS? 3.1 Configure CMC networking from server Out of the box, PowerEdge FX2 CMC network configuration is set to static IP address. Once a network cable is connected to the CMC port 1, you can access the CMC using the static IP address This is also the default IP address which is set when you reset CMC configuration to default settings. PowerEdge FX2 chassis does not have an LCD panel like its predecessors PowerEdge M1000e and VRTX. So how is this done in FX2? Requires Manage and Monitor mode in CMC Either out of the box or after resetting configuration of CMC and idrac, the steps to configure CMC networking from a server are: 1. Attach a monitor and keyboard in the KVM right panel of the chassis. Alternatively, you can use remote console redirection via idrac. 2. Choose a server in any slot and use the KVM select button located in the Control left panel of the chassis to cycle the selection of KVM to the server. 3. Power on the server using the sled power button. 4. Press F2 to go to System Setup. 5. Get current IP address of CMC. a) Once in System Setup, select: idrac Settings > System Summary b) Scroll down the page to the bottom to see Chassis Management Controller section. c) Snapshot below shows you what you see in this page. 6. Configure network settings of CMC. a) Once in System Setup, select: idrac Settings > CMC Settings > CMC Network b) Snapshots below shows you what you can configure in the Network page. Snapshots 11 PowerEdge FX2 Chassis Management at Server

12 Figure 4 CMC current settings in System Setup Figure 5 CMC network settings (part 1 of 3) 12 PowerEdge FX2 Chassis Management at Server

13 Figure 6 CMC network settings (part 2 of 3) Figure 7 CMC network settings (part 3 of 3) 3.2 Chassis sensor inventory and monitoring from idrac The following chassis sensor information is shared for idrac through CMAS: a. Chassis fans b. Chassis power supply c. Chassis ambient temperature The above sensor information is available to all interfaces where sensors such as CPU are reported. a. idrac web UI b. Lifecycle Controller (F10) c. idrac racadm d. WSMAN (CIM_View, CIM_Sensor) 13 PowerEdge FX2 Chassis Management at Server

14 e. IPMI sensors f. idrac SNMP Snapshots Figure 8 Chassis fans and power supplies in idrac web UI 14 PowerEdge FX2 Chassis Management at Server

15 Figure 9 Chassis fans and power supplies in Hardware Inventory under idrac web UI. 15 PowerEdge FX2 Chassis Management at Server

16 Figure 10 Chassis fans and power supplies in Hardware Inventory under Lifecycle Controller (F10) page. 3.3 CMC firmware update from idrac Using CMAS feature and with additional configuration in idrac, the CMC firmware can be updated from the Sled through all supported update interfaces. a. Supported host OS (refer to idrac User s Guide for the list) b. Web UI c. racadm d. WSMAN e. Lifecycle Controller Requires idrac firmware version or later Manage and Monitor mode in CMC Shared Component Update enabled in idrac When Shared Component Update is enabled in idrac, the CMC firmware component is added to the Firmware Inventory list. 16 PowerEdge FX2 Chassis Management at Server

17 Similar to other component when updating through idrac or Lifecycle Controller, provide the EXE update file of the CMC update package. You can get this from the PowerEdge FX2 driver download from support.dell.com. Snapshots Figure 11 CMC firmware in the Firmware inventory list under Lifecycle Controller 3.4 CMC event proxy via idrac Using CMAS capability, all CMC events logged to the chassis log can be sent from CMC to idrac. With the proxy feature, CMC events can be monitored via idrac alert mechanism without placing CMC on the network. Requires CMC firmware version 1.20 or later idrac firmware version or later When CMAS is enabled, CMC events are forwarded to idrac and logged to the idrac s Lifecycle Log. For each event originating from CMC and given the matching category, type and severity, an alert from idrac and an alert from CMC can be sent if both have alerts configured and enabled. Configure the alerts on both sides properly to prevent duplicates. Example CMC event: Clear system event log (SEL) This event corresponds to the alert filter described in the table below when looking at the web UI. Filter In CMC In idrac 17 PowerEdge FX2 Chassis Management at Server

18 Category System Health System Health Event/Alert Sys Event Log Sys Event Log Severity Informational Informational Alert targets are configured independently in CMC and idrac. For example, CMC could be configured to send an alert for this event, while idrac could be configured to send SNMP trap for this event. How do I limit PSU/fan alerts to come from a single server? There are two ways to accomplish this. One way is to enable CMAS on the server you want as your source and then disable CMAS on the other servers using the information in Section 2.2 on how to Configure CMAS in idrac, In this scenario, only one idrac in the chassis has access to components shared by CMAS feature but it guarantees that any alerts associated with shared components will come from only one idrac. Note that if you remove the sled containing this idrac, you lose access to CMAS features. The other way is to leave CMAS enabled in all idrac in the chassis but disable all alerts associated to PSU and fans in each of the idrac except from the idrac that you want as your source. But PSU and fans are not the only source of events that come from CMC. There are other CMC events such as clear System Event Log (SEL) that have similar events in idrac. There is no option to disable a particular event originating from either CMC or idrac. Choose one of the two ways described above that best fits your needs. 3.5 CMC racadm command proxy via idrac Using CMAS capability, idrac racadm proxy feature can redirect CMC racadm commands to CMC via idrac. With the proxy feature, CMC configuration and inventory can be accomplished without placing CMC on the network. Requires Racadm tool version 8.1 or later CMC firmware version 1.20 or later idrac firmware version or later The proxy feature works with local and remote racadm only. Local racadm is racadm that is run from the host OS and targets the host idrac. Remote racadm is racadm that is run from any host OS and targets a remote (requires IP address) idrac. It does not work with firmware racadm, one that runs via ssh to idrac or CMC. The CMC racadm commands that you can run with the proxy feature depends on the CMAS setting. If the setting is disabled, then the proxy commands will not work. If the setting is Monitor only, then you can only send monitoring CMC commands. If the setting is Manage and Monitor, then you can send monitoring and configuration CMC commands. 18 PowerEdge FX2 Chassis Management at Server

19 Note: The --proxy" option must be the last item in the command line. Example command to get CMC sensor information using local racadm: # racadm getsensorinfo --proxy Example command to get CMC sensor information using remote racadm: # racadm -r u root -p XXX getsensorinfo --proxy Example command to set the power redundancy policy of the chassis using local racadm: # racadm config -g cfgchassispower -o cfgchassisredundancypolicy 1 --proxy Example command to set the configuration mode of the storage sled in slot 4 to single-split host using remote racadm: # racadm -r u root -p XXX config -g cfgstoragemodule -m storage-4 -o cfgstoragemodulestoragemode 2 --proxy If the minimum software requirement is not met, the proxy option has no effect on the racadm command. In other words, the command is processed by idrac. If CMC is not connected to the network, the import, export and file operation commands that require access to network shares such as TFTP will not work. The credential provided to the racadm tool must be the idrac credential. The privileges associated with the idrac credential is mapped to CMC privilege when forwarding the command to CMC. For example, if a CMC command requires Chassis Control Administrator and Server Administrator privileges, then the user running the racadm proxy request need to have the System Control privilege. The mapping of privileges are as follows: idrac privilege Login Configure Configure User Logs System Control System Control System Operations Debug System Control Maps to CMC privilege CMC Login User Chassis Configuration Administrator User Configuration Administrator Clear Logs Administrator Chassis Control Administrator Server Administrator Test Alert User Debug Command Administrator Fabric Administrator 19 PowerEdge FX2 Chassis Management at Server

20 A Appendix A.1 Glossary Term CMAS CMC idrac IPMI racadm sled WSMAN Description Chassis management at server the feature that allows chassis management from idrac. Chassis management controller out-of-band systems management of PowerEdge chassis. Integrated Dell remote accesss controller out-of-band systems management of PowerEdge server. Intelligent platform management interface standard specification for management and monitoring of computer systems. Command line tool for idrac and CMC. A container that is inserted into a modular server chassis. A compute sled contains a server, also called a blade. Web services for management standard specification for management and monitoring of computer systems. See A.2 Troubleshooting Symptom You see the error in idrac: RAC0709: Unable to retrieve the fan information. Power on the server. If the server is already powered on, wait for a few minutes and refresh the page Recommendation In addition to what is already suggested in the message, check if the Chassis Management at Server setting is configured in CMC and in idrac (See Section 2). You see the error while updating CMC firmware in the host OS: The shared components could not be updated through operating system because CMC and/or idrac is not configured to enable this behavior Check if the Chassis Management at Server setting is configured in CMC and in idrac (See Section 2). 20 PowerEdge FX2 Chassis Management at Server

21 A.3 Additional resources Support.dell.com is focused on meeting your needs with proven services and support. DellTechCenter.com is an IT Community where you can connect with Dell Customers and Dell employees for the purpose of sharing knowledge, best practices, and information about Dell products and installations. Referenced or recommended Dell publications: Learn more about PowerEdge FX2 chassis and its components See Manuals and Documentation for your PowerEdge FX2/FX2s Get an overview of the Dell Systems Management offerings Dell OpenManage Systems Management Overview Guide at dell.com/openmanagemanuals Learn more about Systems Management solution for managing the PowerEdge chassis Chassis Management Controller at dell.com/esmmanual Learn more about Systems Management solution for managing the PowerEdge servers Remote Access Controller at dell.com/esmmanual Know about the RACADM subcommands and supported RACADM interfaces RACADM Command Line Reference Guide for idrac and CMC at dell.com/esmmanual 21 PowerEdge FX2 Chassis Management at Server