HPE Apollo Platform Manager User Guide

Transcription

1 HPE Apollo Platform Manager User Guide Abstract This guide provides installation and operation guidance for the HPE Apollo Platform Manager. This guide is for the person who installs, administers, and troubleshoots servers and storage systems. Part Number: Published: September 2017 Edition: 4

2 Copyright 2014, 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.

3 Contents Navigation tips Introduction...13 HPE Apollo Platform Manager overview APM kit contents...14 APM front view APM rear view APM connections...16 Required connections...18 Connecting to the HPE Apollo 2000 system...18 Connecting to the HPE Apollo a6000 system...19 Identifying the RDM1 ports Identifying the RDM2 and RDM3 ports...21 HPE APM utility module for HPE Apollo Utility module products Utility module hardware components...23 HPE SL Advanced Power Manager Rack Distribution Module HPE Intelligent Modular PDU-Managed Extension Bar...24 Using RJ-45 connections...25 Naming and numbering conventions...25 Rack chassis numbering Automatic discovery Installation and configuration Prequisites for installation...29 APM installation guidelines...29 Configuring the serial port Configuring the APM Using the configuration wizard...30 Network configuration...31 Setting a static IP address Setting the default network gateway...31 Showing the IP address...31 Verifying network communication Security configuration Protocol configuration User accounts...32 Adding an account...32 Removing an account...33 Showing accounts...33 RADIUS authorization...33 Adding a RADIUS server Configuring a RADIUS server...34 Enabling a RADIUS server Disabling a RADIUS server...34 Showing a RADIUS server...34 Removing a RADIUS server Contents 3

4 Using the GUI Enabling the APM GUI Accessing the GUI...35 Secure web access...36 Accounts...36 Accessing the User Maintenance page Adding a new user Deleting a user account Changing a user account password...39 Changing passwords Interface components...42 Icon classifications and color status indicators...43 Main menu navigation bar APM Information...45 Resetting the APM...46 Upgrading the firmware...46 Linked APMs...47 Power Usage Report Viewing power usage by chassis Setting a power baseline...50 Setting a global power cap...52 Setting a power cap by zone...53 Adding a power zone Adding or removing a chassis from a power zone...54 Removing a power zone Log...55 Inventory/Single Sign-On...57 Configuration Modifying configuration settings...59 Cooling Distribution (CDU) Rack Thermal Status Consolidated Management Ports Component details...65 Rack Distribution Module...66 Component details...67 Alerts Viewing alerts with the Consolidated Management Port page Alert classifications Viewing the Alert Log...69 Logging off...70 Accessing help Using the Command Line Interface Command line conventions Accessing the APM CLI...72 Accessing the CLI using SSH...72 Accessing the CLI using Telnet...73 Accessing the CLI using the APM serial port...73 Saving configurations General commands Working with passwords Enabling APM passwords...74 Setting APM passwords Contents

5 Disabling APM passwords Changing APM passwords...75 Resetting factory settings for APM...75 Working with zones...76 Showing zones...76 Adding zones Saving zones Removing zones Basic configuration information...77 Showing configurations...78 Showing information Showing the version...78 Showing the name Setting the name...79 Showing the time Setting the time...79 Setting the session timeout...79 Setting the UID LED...79 Reboot and Reset commands Rebooting and resetting factory settings...80 Performing a reset Performing a reset buddy...80 Clearing the screen...80 Exiting, logging out, or quitting APM...80 Resetting factory settings...80 Topology and inventory...80 Showing the rack Showing thermal status...85 Showing the MAC address Showing the icdu...88 Showing the icdu status...88 Showing the icdu full status Linked APM modules...91 Enable Linked APM Disable Linked APM...92 Show APM Add APM...92 Remove APM...92 Set APM target...93 Using the help...93 Using ilo Single Sign-On ilo Single Sign-On overview...94 Requirements for using SSO...94 Security access modes...94 Enabling SSO...94 Showing the SSO certificate...95 Disabling SSO Logging...96 Overview of logging...96 Internal logging...96 Showing and clearing the event log...96 Showing and clearing the fault log...98 Contents 5

6 External logging...99 Power capping Power capping overview Power capping requirements Power capping and measurement tolerance Invalidating a power baseline APM and APM Distribution Module cabling Rack level power capping Power baseline Setting power capping Creating APM power mappings Power capping with zones Power baselines and zones Power commands Displaying the rack power status Setting power Polling servers for power values Disabling the polling of servers for power values Using SNMP SNMP overview SNMP commands Enabling SNMP Displaying SNMP parameters Setting the SNMP read-only community string Setting the SNMP read-write community string Setting the SNMP contact Setting the SNMP location Setting SNMP trap destinations SNMP support of cpqhoswrunningtable Using XML XML overview XML headers XML output Data types Response definitions Response Status MSG Enabling XML Showing and resetting keys Logging in through XML Modifying the user account Interacting with the APM using XML Requesting firmware version Requesting configuration information Modifying configuration information Modify Telnet Modify SSH Modify DHCP Set IP address Contents

7 Set rack name Set timeout Requesting rack topology Rack topology for DC power shelf Rack topology for UPS Rack topology for 5-port PDU Rack topology for 60A PDU Rack topology for Apollo DC power Requesting rack information Rack information for PDM devices Requesting power load information Requesting compute node power status Requesting compute power node status Requesting and modifying pollpower information Requesting the MAC address Modifying the UID Modifying the UID of the APM Modifying the UID of the chassis Modifying the UID of PDM devices Requesting the event log Clearing the event log Requesting the fault log Clearing the fault log Requesting thermal status Requesting thermal setpoints Requesting icdu information Requesting Linked APM information Requesting baseline information Requesting zone information Setting a global power cap Setting a power cap for a specific zone Requesting the onboard clock Setting the onboard clock Resetting APM Using APM RESTful API APM RESTful API overview Tips for using the RESTful API Accessing the APM RESTful API RESTful API discovery RESTful API Authentication Basic authentication Redfish session login authentication RESTful API eventing RESTful API commands Firmware Upgrading the firmware Troubleshooting Devices not discovered Alert messages Contents 7

8 8 Contents CLI commands Add account Add APM Add icdu Add RADIUS server Add zone Clear faults Clear log Clear screen Disable Ethernet Disable Linked APM Disable NTP Disable password Disable pollpower Disable RADIUS Disable Redfish Disable Redfish discovery Disable SNMP Disable SSH Disable SSO Disable Telnet Disable XML Enable Ethernet Enable GUI Enable Linked APM Enable NTP Enable password Enable pollpower Enable RADIUS Enable Redfish Enable Redfish discovery Enable SNMP Enable SSO Enable SSH Enable telnet Enable XML Enable XML secure Exit Help Logout Ping Quit Reboot Reboot CM Remove account Remove APM Remove icdu Remove RADIUS server Remove SSO Remove zone Reset Reset buddy Reset factory Reset keys...147

9 Reset port Save Save config Save zones Set APM target Set door close front Set door open front Set door close rear Set door open rear Set IP Set asset info Set gateway Set name Set NTP server Set NTP poll Set password Set power Set power baseline Set power cap Set power cap mode Set power cap poll Set RADIUS pollnum Set RADIUS pollsec Set serial Set SNMP contact Set SNMP location Set SNMP RO Set SNMP RW Set SNMP trapdest Set syslog Set time Set timeout Show accounts Show APM Show asset info Show config Show faults Show icdu Show icdu full Show icdu status Show info Show ilo Show keys Show log Show MAC address Show name Show NTP server Show NTP poll Show power Show power baseline Show rack Show RADIUS Show servers Show SNMP Show SSO certificate Show syslog Show thermal status Contents 9

10 Show time Show topology Show version Show zones Upgrade image XML commands Disable pollpower Disable Telnet Disable SSH Enable DHCP Enable pollpower Enable SSH Enable Telnet Get all compute node power Get APM information Get compute node Get configuration Get firmware version Get icdu info Get ilo IP address Get node identification Get power load Get rack information Get rack topology Get session information Get thermal status Login Poll power Modify all compute node power Modify compute node power Modify configuration Modify user Reset APM Set power cap mode Set power cap poll RESTful API Data Model Reference Resource map RESTful API Data Model Reference RESTful API Data Model Reference /redfish/v1/accountservice/accounts /redfish/v1/accountservice/accounts/{username} /redfish/v1/chassis /redfish/v1/chassis/hpe-apm /redfish/v1/chassis/rdm{rdmport}enc{dmport} /redfish/v1/chassis/rdm{rdmport}enc{dmport}/power /redfish/v1/chassis/rdm{rdmport}enc{dmport}/thermal /redfish/v1/chassis/rdm{rdmport}enc{dmport}node{node} /redfish/v1/managers /redfish/v1/managers/hpe-apm /redfish/v1/managers/hpe-apm/ethernetinterfaces /redfish/v1/managers/hpe-apm/ethernetinterfaces/{item} /redfish/v1/managers/hpe-apm/logservices Contents

11 /redfish/v1/managers/hpe-apm/logservices/events /redfish/v1/managers/hpe-apm/logservices/events/entries /redfish/v1/managers/hpe-apm/networkprotocol /redfish/v1/managers/hpe-apm/serialinterfaces /redfish/v1/managers/hpe-apm/serialinterfaces/{item} /redfish/v1/managers/rdm{rdmport}enc{dmport} /redfish/v1/managers/rdm{rdmport}enc{dmport}node{node} /redfish/v1/sessionservice /redfish/v1/sessionservice/sessions /redfish/v1/sessionservice/sessions/{item} /redfish/v1/systems /redfish/v1/systems/rdm{rdmport}enc{dmport}node{node} Data Model Type reference overview Navigating the data model AccountService Chassis Managers Systems Message reference overview Supported MIB objects Supported cpqrack MIB objects Supported cpqhostos MIB objects Supported rfc1213 MIB objects PDU identity table PDU input table Support and other resources Accessing Hewlett Packard Enterprise Support Accessing updates Customer self repair Remote support Warranty information Regulatory information Documentation feedback Contents 11

12 Navigation tips Navigating in the HTML document To navigate through the documentation sequentially: Click the Next arrow ( ) for the next topic. Click Previous arrow ( ) for the previous topic. Navigating using the Internet browser toolbar: To return to the last page you viewed, click Back on the browser toolbar. To return to one of the last nine pages you viewed in this session, click the down arrow to the side of the Back or Forward button on the browser toolbar, and then click the page you want from the list. Navigating to documentation on the Hewlett Packard Enterprise website From the URLs in this guide, you may need to make several selections to get to your specific documentation. For online access to technical documentation, self-help resources, live chat assistance, community forums of IT experts, technical knowledge base, remote monitoring and diagnostic tools, go to For the latest versions of selected technical documentation, go to 12 Navigation tips

13 Introduction HPE Apollo Platform Manager overview The HPE Apollo Platform Manager is a rack-level point of contact for HPE ProLiant Scalable System and HPE Apollo administration. Rack management features Automatic chassis and device discovery with topographic views Time-stamped, rack-level event logging Rack and chassis shared power and thermal component management Integrated serial connector for server console and ancillary device access Integrated Gb Ethernet switch for server ilo consolidation Server management features Server health monitoring ilo Single Sign-On access Server FRU data reporting ilo IP address and PXE MAC address listings Power management features Power control and measurement at the server, chassis, and rack level PDU-level power outlet control and current measurement Rack-level static or dynamic power capping DC Power Shelf management and integration with UPS subsystem NOTE: The use of the term "server" represents nodes, server trays, server nodes, and cartridges. For a full description of APM features and support, see the QuickSpecs on the Hewlett Packard Enterprise website. Introduction 13

14 APM kit contents Item 1 APM Description 2 Mounting brackets (2) 3 Terminal blocks (2) 4 Power cords (2) 5 Bracket mounting screws, T-20 (2) 1 6 Rack mounting screws, (2) 1 7 Cage nuts (2) 1 8 This document 1 1 Not shown APM front view Supporting the dense, optimized Apollo product line, APM offers a rack level management solution that consolidates many IT features and infrastructure control and monitoring capabilities into a single unified interface. The connectors on the front panel of the APM provide the hardware connectivity that enables these product capabilities (see APM Rack Features). 14 APM kit contents

15 Table 1: APM Rack Features Qty Feature Feature Description 10 Consolidated Management Ports Consolidates Ethernet, serial, and necessary hardware signaling connections from the APM to each Apollo chassis controller 6 Power Distribution Module ports Interfaces directly to rack mounted power feed infrastructure 3 External serial terminal server connections 2 Rack Distribution Module (RDM) ports Establishes backward compatibility to Moonshot and SLseries server chassis 1 ilo consolidation Ethernet port - Serial and Ethernet access ports Supports APM Item Description 1 Consolidated Management Ports 1 through 10 (RDM1) 2 Power LED 3 Serial management for top of rack switch 4 RDM3 port for APM distribution module 5 RDM2 port for APM distribution module 6 ilo port 7 UID 8 Health LED 9 Reset button 10 Ethernet Management port Table Continued Introduction 15

16 Item Description 11 Service port 12 Serial console port 13 microsd slot 14 Power Distribution Module ports NOTE: Hewlett Packard Enterprise recommends configuring the APM such that it controls only one rack. The APM has six power distribution ports and two RDM ports on the front of the unit. Each RDM port has 10 connections to SL Scalable System enclosures. APM rear view Item Description 1 Power plugs 1 and 2 2 On-Generator and AUX signals (reserved for future use) 3 Redundant reset (reserved for future use) APM connections APM offers new rack-level management solutions that consolidate IT control, monitoring, and console access to hosted server, storage, fabric, and power resources to a single wire at the chassis level. APM provides connections as follows: 10 Consolidated Management Ports connect to each Apollo chassis-mounted rack. 6 Power Distribution Module ports interface directly to the rack-mounted power-feed infrastructure, such as UPS units, PDUs, or distributed DC power shelves. Redundant Reset port connects to another APM module (Buddy). 16 APM rear view

17 The following figure shows the APM unit connected to ten unique chassis through the Consolidated Management Ports. RDM connectors are provided for backwards compatibility with HPE ProLiant SL chassis. The APM connects to the system components using various cables. Purchase cables required for connecting the APM to the system separately based on the rack configuration needs. Table 2: APM connections Item Component Connects to 1 HPE Apollo a6000 Chassis The RDM1 connector on the APM 2 HPE Apollo a2000 Chassis The Power Distribution Module ports on the APM 3 HPE Apollo a6000 Power Shelf The Power Distribution Module ports on the APM 4 PDU The Power Distribution Module ports on the APM 5 APM 6 HPE ProLiant SL Series Chassis Chassis connector on the RDM Table Continued Introduction 17

18 Item Component Connects to 7 HPE ProLiant SL Series Chassis Chassis connector on the RDM 8 HPE Moonshot 1500 Chassis Chassis connector on the RDM 9 HPE Intelligent Modular PDU Managed Extension Bar The Power Distribution Module port on the APM 10 Management Network Ethernet port on the APM 11 Terminal Serial console port on the APM 12 RDM RDM2 or RDM3 port on the APM RDM or APM 1 port on the product chassis 1 Some products might identify this as the SL APM port. IMPORTANT: If you have an APM connected to an Apollo a6000 Chassis or an Apollo 2000 Chassis, do not connect the APM ilo port and the enclosure ilo port to the network at the same time. Connecting both ports at the same time results in a loopback condition. NOTE: APM operations classify the ten Consolidated Management cable ports as RDM1. For more information, see "Identifying the RDM1 ports." Required connections Connection APM to chassis APM to power device 1 APM to management and production networks APM to RDM RDM to chassis Required cables Consolidated Management cables Micro DB9-to-DB9 cable or Micro DB9-to-Micro DB9 cable Ethernet cable RJ-45 cable included with the RDM These cables are attached to the RDM. 1 Power devices include a power shelf, PDU, HPE Intelligent Extension Bar, or other power devices, if installed. Connecting to the HPE Apollo 2000 system Procedure 1. Connect the APM to the network (shown in red). 2. Connect the APM to the RCM modules (shown in blue). 18 Required connections

19 IMPORTANT: If you have an APM connected to an Apollo a6000 Chassis or an Apollo 2000 Chassis, do not connect the ilo port of the APM and the ilo port of the enclosure to the network at the same time. Having both ports connected at the same time results in a loopback condition. Connecting to the HPE Apollo a6000 system Procedure 1. Connect the APM to the network (shown in green). 2. Connect the APM to the chassis (shown in red). 3. Connect the APM to the power shelf (shown in blue). Connecting to the HPE Apollo a6000 system 19

20 IMPORTANT: If you have an APM connected to an Apollo a6000 Chassis or an Apollo 2000 Chassis, do not connect the ilo port of the APM and the ilo port of the enclosure to the network at the same time. Having both ports connected at the same time results in a loopback condition. Identifying the RDM1 ports For products using APM, connect the chassis to one of the corresponding consolidated management ports (RDM1) on the APM module. 20 Identifying the RDM1 ports

21 Identifying the RDM2 and RDM3 ports Consolidated management ports (RDM1) are used only for products designed to work with APM when a separate RDM is not required. When connecting the APM module to an RDM, always use either the RDM2 or RDM3 ports. Item Description 1 RDM2 port 2 RDM3 port HPE APM utility module for HPE Apollo 8000 The utility module serves as a central location for gathering and monitoring data for the Apollo 8000 system, including: Managing rack Ethernet infrastructure via an embedded 160 port, 1 GB switch Gathering data from the f8000 rack sensors Controlling power output and fan speed for each management module cell Updating component status within APM Maintaining alarm conditions within APM One utility module is installed in each f8000 rack within the HPE Apollo 8000 System. Identifying the RDM2 and RDM3 ports 21

22 The utility module might appear different based on the model installed. For more information on the different models available, see "Utility module products." Utility module products There are two utility module products that can be installed in the HPE Apollo 8000 System. Although they might appear different and have slightly different features, their basic functionality within the HPE Apollo 8000 System is the same. For the purpose of clarity in this document, when removing and replacing spare parts, the components will be referred to as shown in the following illustration and table. 22 Utility module products

23 Item Description 1 HPE Apollo 8000 Utility Module v1 (Apollo 8000 UM1) 2 HPE Apollo 8000 Utility Module v2 (Apollo 8000 UM2) Utility module hardware components For more information about the utility module hardware components and functionality, see the HPE Apollo 8000 System User Guide or HPE Apollo 8000 System Maintenance and Service Guide on the Hewlett Packard Enterprise website. HPE SL Advanced Power Manager Rack Distribution Module The distribution module includes a connector bay for the APM and cables for SL Scalable Series servers. It is backward compatible with SL APM. The following servers and chassis require the use of the distribution module: HPE Moonshot System HPE ProLiant SL2500 Scalable System HPE ProLiant SL4500 Server Series HPE ProLiant SL6500 Scalable System For more information, see the Hewlett Packard Enterprise website. Utility module hardware components 23

24 Item Description 1 Standard CAT-5 cable connection to the RDM2 or RDM3 ports on APM 2 SL Scalable Series server connectors 3 Power (green) LED, which indicates connection to port 4 Activity (amber) LED, which indicates activity to APM Distribution Module The HPE Apollo a6000 Chassis connects directly to the Consolidated Management Ports (RDM1). For more information, see "Naming and numbering conventions." HPE Intelligent Modular PDU-Managed Extension Bar The extension bar provides power management for external devices. The extension bar can be used with HPE cable part number SF672A, connects to one of the six available PDM ports on the APM. The total rating of the Intelligent Extension Bar is 16 A. 24 HPE Intelligent Modular PDU-Managed Extension Bar

25 Item Description 1 Green power indicators (one for each outlet) 2 Blue UID indicators (one for each outlet) m (8 ft) input power cord 4 Five managed 10 A, IEC-320 C13 outlets 5 Blue UID indicator for the Intelligent Extension Bar 6 Green power indicator for the Intelligent Extension Bar 7 Reset button 1 1 When you press the Reset button, power to the managed outlets is maintained. Management functionality is momentarily lost while the Intelligent Extension Bar resets. Using RJ-45 connections One APM can connect up to two APM Rack Distribution Modules. Each RDM connects up to ten chassis with an RJ-45 connection or an 8 pin standard connector that comes with the RDM. Naming and numbering conventions The following figure shows an example of the basic APM configuration and node numbering convention on a scalable system enclosure. The SL APM Distribution Module allows you to extend the functionality of the APM to more than one rack or ten Apollo chassis. For more information, see "HPE SL Advanced Power Manager Rack Distribution Module." Using RJ-45 connections 25

26 Item Description 1 HPE Apollo a6000 Chassis 2 HPE ProLiant SL Series Chassis 3 HPE ProLiant SL Series Chassis 4 HPE Moonshot 1500 Chassis 5 PDU 6 HPE Intelligent Modular PDU Managed Extension Bar 7 SL APM Distribution Module When entering commands that require specific port and node numbers (for example, SET POWER ON) the parameters are three numbers in sequence. The first number is the rack number (1 for all chassis that are plugged into the Consolidated Management Cable ports and 2 or 3 for chassis that are connected to an RDM that in turn is plugged into the RDM2 or RDM3 port on the APM). 26 Introduction

27 NOTE: Parameters must have spaces between them. For example, to power on SL server node 3 that is connected to RDM port 4, which is connected to APM RDM port 2, enter the following command: SET POWER ON Where: 2 is the APM port 4 is the SL APM Distribution Module port 3 is the SL server node To power on the Apollo 2000 server in bay 2 connected to consolidated management cable port 6 on the APM, enter the following command: SET POWER ON All the parameters must have spaces between them. NOTE: APM operations classify the ten Consolidated Management cable ports as RDM1. For more information, see "Identifying the RDM1 ports." Rack chassis numbering If you number the chassis in your rack or data center, then APM will display the chassis numbering, based on the APM Distribution Module port connection. Item Description 1 APM Distribution Module 2 APM connection 3 Connections to SL and Apollo series enclosures The APM commands SHOW TOPOLOGY and SHOW RACK display the SL series and Apollo series enclosures connected with number, based on the APM port connection. Rack chassis numbering 27

28 For example: SHOW TOPOLOGY 1: Enclosure Product Name :HPE ProLiant SL6500 Product SKU : Serial Number: UID :off Status : 1 : Compute node (active) 2 : Compute node (active) 3 : Compute node (active) 4 : Compute node (active) 5 : Compute node (active) 6 : Compute node (active) 7 : Compute node (active) 8 : Compute node (active) 2: Enclosure Product Name :HPE ProLiant SL6500 Product SKU : Serial Number: UID :off Status : 1 : Compute node (active) 2 : Compute node (active) ** ** 3: Enclosure Product Name :HPE ProLiant SL6500 Product SKU : Serial Number: UID :off Status : 1 : Compute node (active) **** Automatic discovery APM employs an automatic discovery process that identifies all SL series servers in the attached enclosures. The discovery process also has a simple fault detection mechanism. If any node has faults detected (for example, power supply failure), the discovery response data reports the fault. For a list of alert messages, see "Alert messages." 28 Automatic discovery

29 Installation and configuration Prequisites for installation Before installing and configuring the APM for the first time: Review the APM installation guidelines. If you are using a remote-logging server, verify that the remote syslog server for connecting to the remote syslog server is available. Provide serial terminal access, which is required for the initial setup of the APM. Before SSH, Telnet, or the GUI are made available, configure the APM using the serial console CLI. Configure the serial port for initial setup. APM installation guidelines The APM can be installed in the front of the rack or in the rear of the rack. Always install the APM with the connectors facing the outside of the rack. For more information on installing the APM, see the HPE Apollo Platform Manager Installation Instructions that accompany the option kit. Configuring the serial port Procedure Configure the serial port with the following settings: Baud rate Data bits 8 Stop bits 1 Parity None Flow control None To change the serial baud rate after the initial configuration: 1. Enter the SET SERIAL <BAUD_RATE> command, where <BAUD_RATE> is the baud rate setting to be used. 2. Reboot the APM. 3. Change the settings on the client to match the settings on the APM. Configuring the APM APM must be configured using the serial console CLI before SSH, Telnet, or the GUI are available. For more information, see "Configuring the serial port." NOTE: If configuring for the first time from the serial port, the LOGIN prompt does not appear. Instead, the CLI prompt appears. The Administrator account must be enabled and configured by setting a password as part of the CONFIG command. When the APM boots, a LOGIN prompt appears. Enter Administrator as the user account: Login: Administrator Installation and configuration 29

30 You can initially configure the APM in the following ways: Enter the CONFIG command to use the configuration wizard. The wizard provides a step-by-step process for configuring the APM. For more information, see "Using the configuration wizard." Enter the configuration manually, and then type SAVE to commit them to nonvolatile memory. Duplicate the configuration of another APM using the SHOW CONFIG command. Using the configuration wizard Procedure 1. After the APM boots, enter Administrator at the LOGIN: prompt. 2. Enter the CONFIG command, and then complete the remaining prompts. 3. Select Y or N to set the onboard clock. If you select Y, you will be prompted for the following information: Month Enter a value between 1 to 12, and then press the Enter key. Day Enter a value between 1 to 31, and then press the Enter key. Year Enter the four-digit year, and then press the Enter key. Hour Enter a value between 0 to 23, and then press the Enter key. Minutes Enter a value between 0 to 59, and then press the Enter key. 4. Select Y or N to name the APM. Naming the APM is optional. This is the name that appears in log entries on the syslog server as well as the CLI prompt. a. If you select Y, enter a name for the APM. System names can be up to 80 characters long. It can include uppercase letters, lowercase letters, underscores (_), dashes (-), and numerical values between 0 to 9. Dashes (-) are not supported as the first character. b. Press the Enter key to save the name. 5. Select Y to enable password protection. APM has no default password. a. If you select Y, enter a password. Passwords must be between 8 and 40 characters, and can include the following: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numbers between 0 to 9 b. To save and enable the password, press the Enter key. 6. Configure the Ethernet port or proceed with reviewing and saving the enabled configuration: 30 Using the configuration wizard

31 a. Select DHCP or static. b. Enter an IP address if static. If the static IP address is invalid, DHCP is assumed. c. Enter an IP address mask if static. If the IP address mask is invalid, DHCP is assumed. 7. Enable Telnet access (optional). 8. Enable SSH access (optional). 9. Enable GUI access (optional). NOTE: ENABLE XML SECURE is automatically enabled when the GUI is enabled. For more information, see "Enabling XML." 10. To review the enabled configuration before saving it, select Y. 11. To save the new configuration, select Y. All settings relating to the APM Ethernet and serial interfaces are persistent and stored in the APM. Network configuration APM supports both DHCP and static IP addresses. To view the MAC address, enter SHOW INFO. For more information, see "Showing configurations." Setting a static IP address To set a static IP address and subnet mask, enter the SET IP <ip_address> <subnet_mask> command, where <ip_address> is the IP address and <subnet_mask> is the subnet mask. To return to DHCP, enter the SET IP DHCP command. Setting the default network gateway To set the network default gateway, enter the SET GATEWAY <ip_address> command, where <ip_address> is the IP address. To clear the gateway, enter the SET GATEWAY NONE command. NOTE: If DHCP is enabled, the APM disallows the default gateway from being set since the DHCP configuration includes the gateway. Showing the IP address To show the IP address, enter SHOW IP. The following information appears: IP Address appears in x.x.x.x format IP Mask appears in x.x.x.x format Gateway appears in x.x.x.x format Verifying network communication To verify the network communication is working, enter PING <IP address>, where <IP address> is the IP address you want to test. Network configuration 31

32 Security configuration The network interface is disabled when password protection is removed. For more information about passwords, see "Working with passwords." Protocol configuration APM supports SSH and Telnet. Working with the SSH configuration To enable SSH access, enter ENABLE SSH. To disable SSH access, enter DISABLE SSH. Working with the Telnet configuration To enable Telnet access, enter ENABLE TELNET. To disable Telnet, enter DISABLE TELNET. User accounts APM supports ten local accounts in addition to the default Administrator account on a single APM. The account username must be between 2 to 32 characters and can contain: Uppercase letters Lowercase letters Numbers between 0 to 9 Underscores (_) Dashes (-) Adding an account Procedure 1. Enter the ADD ACCOUNT command. For example: HPE APM> add account "user1" Password must be at least 8 characters Note: password will not show. Enter account "user1" password: Enter account "user1" password (again): Saving password..done. Account user1 enabled HPE APM> The account username must be between 2 to 32 characters and can include: Uppercase letters Lowercase letters Numbers between 0 to 9 Underscores (_) Dashes (-) 32 Security configuration

33 After you enter this command with a valid new username, a prompt asking for a password appears. 2. Enter the password. If you do not specify a password, and the username does not already exist, then you are prompted to enter a password. Passwords must be between 8 and 40 characters and can include: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numbers between 0 to 9 3. Enter the password again. The new account is available for system login. All user accounts have the same permissions. NOTE: Login accounts and passwords are stored separately from the APM configuration. The SHOW CONFIG command will not reveal any ADD ACCOUNT commands. Removing an account To remove an account, enter the REMOVE ACCOUNT <username> command, where: "<username>" is the account username. This command removes the specified account from the system. If the user does not exist, then an error message appears. The Administrator account cannot be deleted. Showing accounts To show the existing defined accounts, including the reserved Administrator account, enter the SHOW ACCOUNTS command. For example: HPE APM> show accounts Administrator user1 HPE APM> RADIUS authorization APM supports the RADIUS authentication protocol. When RADIUS is enabled, it is used to verify login requests to APM through SSH, Telnet, serial console, the GUI, or the RESTful API. Removing an account 33

34 Adding a RADIUS server To add a RADIUS server, enter the ADD RADIUS SERVER <ip_address> <shared_secret> command. This command specifies an initial or additional RADIUS server to the APM list of authentication servers. The authentication proceeds in the same order that these servers were added to the configuration. No more than five RADIUS servers can be added for authentication purposes. Port 1812 is assumed. The IP address must match the location of the RADIUS server. The shared secret must be specified in quotes and must match the string that has been programmed into the RADIUS server when receiving authentication requests from APM. Configuring a RADIUS server To set the number of times APM polls each of the RADIUS servers indicated in the ADD RADIUS SERVER command, enter the SET RADIUS POLLNUM command. To set the number of seconds APM waits for a reply from the RADIUS server, enter the SET RADIUS POLLSEC command. These settings can only be set globally and cannot be applied to each individual RADIUS server. Enabling a RADIUS server To enable APM as a RADIUS client, enter the ENABLE RADIUS command. All login attempts through SSH, Telnet, and the serial console are authenticated through the list of RADIUS servers that were indicated with the ADD RADIUS SERVER command. Authentication is also verified against the local password if the RADIUS servers indicate no access. Disabling a RADIUS server To disable RADIUS authentication on APM, enter the DISABLE RADIUS command. Authentication through RADIUS no longer takes place, but password checking is still done against the local password if that is still enabled. This command does not clear out the configured RADIUS servers. Showing a RADIUS server To show the currently configured RADIUS server, enter the SHOW RADIUS command. To show the currently configured RADIUS parameter, use the SHOW CONFIG command. Removing a RADIUS server To remove a RADIUS server, enter the REMOVE RADIUS SERVER <index> command. This command removes the previously added RADIUS server that matches the index indicated with the SHOW RADIUS command. RADIUS authentication is no longer attempted against this server. 34 Adding a RADIUS server

35 Using the GUI Enabling the APM GUI A web-based GUI is available to support the APM. The APM GUI is disabled by factory default. To enable the GUI, enter the following commands: Procedure SET PASSWORD ENABLE PASSWORD SET IP <ADDRESS> ENABLE ETHERNET ENABLE XML SECURE ENABLE GUI SAVE Accessing the GUI Procedure 1. Launch any supported browser: Internet Explorer 11 and later Firefox 29 and later Chrome 35 and later 2. Browse to address], where [IP address] is the IP address of the APM. The application splash screen appears. 3. Enter a valid Login Name and Password to log in. Using the GUI 35

36 Secure web access An SSL certificate is required before you can configure the APM to use a secure web access. Self-certified or third-party certifications are supported. Accounts There are two account types: Administrator Standard user The features available are based on the type of account accessed during the session login. Accessing the User Maintenance page Procedure The User Maintenance page is accessible only to Administrator accounts. From User Maintenance page, administrators can: Add new users Delete users Change user account passwords 1. Click the user icon at the top right of the screen. 36 Secure web access

37 2. Click Accounts. Adding a new user APM supports a maximum of ten user accounts. Procedure 1. Enter a user name in the User Name field. The username must be between 2 to 32 characters and can include: Uppercase letters Lowercase letters Numbers between 0 to 9 Underscores (_) Dashes (-) 2. Click Add New User. The password window appears. 3. Enter the password in the New Password and Re-enter Password fields. Adding a new user 37

38 Passwords must be between 8 and 40 characters and can include: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numbers between 0 to 9 4. Click Submit. Deleting a user account Procedure 1. Locate the username in the Users pane. 2. Click Delete User. 38 Deleting a user account

39 3. Do one of the following: Click OK to delete the user account. Click Cancel to exit. Changing a user account password Procedure 1. Locate the user name in the Users pane. 2. Click Change Password. 3. Enter the password in the New Password and Re-enter Password fields. Changing a user account password 39

40 Passwords must be between 8 and 40 characters and can include: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numbers between 0 to 9 4. Do one of the following: Click Submit to change the password. Click Cancel to exit. Changing passwords Procedure The GUI can be used to change the password when the login uses a local account. Passwords for remotelyauthenticated logins cannot be changed using APM. Administrator accounts can use the User Maintenance page to change passwords for local user accounts. For more information, see "Accessing the User Maintenance page." 1. From the Main menu navigation bar on the left side of the screen, click Configuration. The Configuration Setting page appears. 40 Changing passwords

41 2. In the Password box, enter the new password in both fields. Passwords must be between 8 and 40 characters and can include: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numbers between 0 to 9 3. To save the settings, click Submit. Using the GUI 41

42 Interface components Item Component Description 1 APM name Identifies the APM 2 Consolidated management ports Provides an overview of the chassis connected to the consolidated management ports and any connected PDM ports Identifies any active alerts 3 Main menu navigation bar Provides simple navigation access to the available screens and configuration options for the APM 4 General overview Provides an overview of the components connected to the APM, including any active alerts Table Continued 42 Interface components

43 Item Component Description 5 Layout Provides an overview of the components connected to the APM 6 UID light Turns off and on the APM UID light by chassis 7 Active alerts Provides a list of all active alerts for the components connected to the APM 8 Log in and out Accesses the log in and log out screen to change users 9 Online help Accesses the online help for the APM interface Icon classifications and color status indicators The following icons appear on the graphical depictions throughout the GUI interface. The icon indicates the type of component or sensor, and the color indicates the status. Typically, the status can be defined by the following colors: Gray Component is not installed or communicating data. Blue Component status remains constant, and color does not change to indicate status. Green Component is within normal operating parameters. Yellow Component is issuing an alarm. Red Component has a critical condition or has failed. The exceptions are noted in the following table. Icon Component or sensor Status indicators Fan 1 Gray Green Yellow Red DC power supply 1 Gray Green Yellow Red AC power supply 1 Gray Green Yellow Red Water valve Gray Blue Green Yellow Red Table Continued Icon classifications and color status indicators 43

44 Temperature sensor Gray Blue Green Yellow Red Relative humidity sensor Gray Blue Green Yellow Red Dew point sensor Gray Blue Green Yellow Red Door position sensor 12 Gray Green Yellow Red Door lock sensor 1 Gray Green Yellow Red Pressure sensor Gray Blue Green Yellow Red Water leak detection sensor 1 Gray Green All three leak detection sensors are clear Yellow One of the leak detection sensors is indicating a leak Red Two or more leak detection sensors are indicating a leak 1 Component indicates a health status and cannot show a blue, constant status. 2 The door position sensor icon is either open or closed, to indicate the status of the door being open or closed. 44 Using the GUI

45 Main menu navigation bar The Main menu navigation bar is located on the left side of the screen. To go directly to an APM page, click: APM information Linked APMs Power Usage Report Event Log Inventory/Single Sign-On Configuration Cooling Distribution (CDU) Rack Thermal Status (only in f8000 rack systems) APM Information The System Information page displays the basic APM information and all active sessions on the APM. It also includes the ability to reset the APM. To access the System Information page, from the Main menu navigation bar on the left side of the screen, select System Information. Main menu navigation bar 45

46 Resetting the APM Resetting the APM reboots the APM firmware. Procedure 1. From the Main menu navigation bar on the left side of the screen, click System Information. The System Information page appears. 2. Click Reset. A new window appears prompting you to confirm the reset. 3. Click one of the following: OK Resets the APM Cancel Returns to the Reset page without resetting the APM When the APM is reset, the APM web server is briefly unreachable. After a reset, you must log in to the APM again. Upgrading the firmware 46 Resetting the APM

47 Procedure 1. From the Main menu navigation bar on the left side of the screen, select System Information. The System Information page appears. 2. Select the method by which to upgrade the firmware. If selecting TFTP or FTP, enter the IP address of the server where the image is stored in the IP Address: field. If selecting HTTP or HTTPS, enter the location of the image in the Image/URL: field. 3. Click Upgrade. Linked APMs Procedure The Linked APM page displays the connections between linked APMs. This feature is available if, after configuring APM on your network: XML Secure is enabled from the APM CLI. GUI is enabled from the APM CLI. Single Sign-on is enabled from the APM CLI. NOTE: Single Sign-on, a capability in the APM firmware (v3.0 or later), allows any HPE ilo in the rack to be seen from the APM GUI. APM creates a security certificate on your system or you use and the existing one (if one exists). Linked APM is enabled from the Linked APM page of the APM GUI. More information: "Enable XML secure" "Enable GUI" "Enable SSO" To enable the Linked APM feature and view linked APMs, complete the following procedure. From the Main menu navigation bar on the left side of the screen, click Linked APMs. The Linked APMs page appears. Linked APMs 47

48 Any Linked APMs appear under Domain Entities. If Linked APMs are enabled, click one of the available Linked APMs to access the GUI interface for that APM through Single Sign-On. If Linked APMs are not enabled, click the green Enable button in the highlighted error, or see "Configuration" for more options. Power Usage Report The Power Usage Report provides the current distribution of power and power usage for all components connected to the APM. From the Power Usage Report page, you can do the following: 48 Power Usage Report

49 View power usage by chassis. Set the power baseline. Set a global power cap. Set the power cap by zone. Add a power zone. Add or remove a chassis from a power zone. Remove a power zone. To access the Power Usage Report, click Power Usage Report from the Main menu navigation bar on the left side of the screen. If power polling is enabled, the Power Usage Report page appears and might appear different, depending on the devices configured. If power polling is not enabled, the following message appears. Click Enable to enable power polling and load the Power Usage Report page. Viewing power usage by chassis To view power usage by chassis, select > next to the Rack column. Viewing power usage by chassis 49

50 The top half of the Power Usage screen shows the power wattage legend key, Total Node Power pie chart, and the Total Node Power graph. The bottom half of the Power Usage screen shows how much power each node is currently using upon selecting > to expand node details. Hovering over a selection of pie displays a pop-up window that shows all the nodes within that wattage range and their corresponding wattage. Example: In the Example, the screen shows: One node in the wattage range. The remaining nodes are functioning in the 1-99 wattage range. A line graph that displays the current polling power wattage for the selected chassis. The range slider allows the user to adjust the wattage range at which to view the polling power chart. The horizontal bar chart displays the current average wattage per node in the chassis and the max wattage recorded per node. All charts with real-time power polling information as changes occur within the rack. Setting a power baseline Prerequisites Procedure Before running a baseline calibration, verify that all machines in the configuration are powered on and running processes typical of the type of workload that you expect them to run in a production environment. 1. Select a chassis, and click Set Baseline. 50 Setting a power baseline

51 2. Review the prerequisites and performance information, and then click OK to set a new power baseline. The message Baselining in Progress... appears while the process completes. Using the GUI 51

52 3. After the baselining process completes, click OK. Setting a global power cap Power caps can be set globally or by zone. Procedure 1. Click Set Cap. 2. Enter a value between the minimum and maximum cap values. 52 Setting a global power cap

53 3. Click Set Cap. Setting a power cap by zone Procedure Power caps can be set globally or by zone. You must add a zone before assigning a power cap value. For more information, see "Adding a power zone." If a zone contains only one chassis, the entire power cap is assigned to that chassis. If a zone contains more than one chassis, the APM assigns cap values to the chassis based on the power capping mode? 1. Select a zone, and then click Set Cap. 2. Enter the power capping value, and then press Enter. If the power cap value entered is too small, the APM generates an error. Adding a power zone Procedure 1. Click Add Zone. Setting a power cap by zone 53

54 2. Enter a name for the zone in New Zone, and then select the check boxes next to each chassis included in the new zone. 3. Click Add. A new power zone is created. Adding or removing a chassis from a power zone Procedure 1. Click Edit next to the zone to be changed. 2. Do one of the following: To add an unassigned chassis to the zone, check the box next to the chassis. If a chassis is already assigned to a zone, the check box next to the chassis number is not available for selection. To add an available, different zone, first, remove the chassis from the current zone. To remove a chassis from the zone, clear the check box next to the chassis. 54 Adding or removing a chassis from a power zone

55 3. Click Edit. Removing a power zone Procedure 1. Highlight the zone to be removed. 2. Click Remove Zone. Any chassis that were assigned to the zone are now unassigned and available to be added to another zone. Log The Log page displays the last 100 events either following the last visit you made to the page or after you select RERESH LOG. To access the Log, from the Main menu navigation bar on the left side of the screen, click Log. The Log page appears. The system filters warning and critical entries (in the left column) for each fault log entry displayed. Removing a power zone 55

56 Log entry status symbol Description Normal - No action required. Warning - Investigate and remediate (if necessary). Critical - Investigate and repair. Additional/Other information - No action required. The Log does not poll automatically, so it must be refreshed to get the latest event entries. To refresh the Log, click RERESH LOG. To clear the Log, click CLEAR LOG. All entries in the system are cleared from the log, including any faults. To sort entries by Fan/Thermal, Power, Infrastructure, Server, or Fabric categories, click the pull-down menu. 56 Using the GUI

57 Entries are sorted by the selected option. Inventory/Single Sign-On The Inventory/Single Sign-On page displays all MAC address information and statuses for all nodes connected to the APM. To access the Inventory/Single Sign-On page: From the Main menu navigation bar on the left side of the screen, click Inventory/Single Sign-On. The Inventory/Single Sign-On page appears. If SSO is not enabled, then a basic PXE MAC Address is the only address that appears for each monitored rack. Inventory/Single Sign-On 57

58 If SSO is enabled and connected to ilo, then the additional ilo information also appears. If you click the ilo IP address, a new window opens taking you directly to the ilo page (using SSO). At the top right of the Inventory/Single Sign-On page, additional options are available. Click the CSV icon (1) to download the entire inventory into a csv file. Click the Filter icon (2) to adjust the inventory you view on the page. 58 Using the GUI

59 Configuration The Configuration Setting page displays the available options for configuration, based on the type of account in which you logged. To access the Configuration Setting page, click Configuration from the Main menu navigation bar on the left side of the screen. Modifying configuration settings The current configuration settings appear in gray text to the right of the field box. After changing a configuration setting, check the gray text to verify the change was saved and updated. Configuration 59

60 Procedure 1. To modify the the date and time from the Onboard Clock section of the Configuration Setting screen, either: Enter the current Date and Time into the appropriate fields, or Click the green Use GMT time box to automatically populate the Date and Time fields. All fields must be populated to save changes to the Onboard Clock. 2. To modify the time out feature from the Device section of the Configuration Setting screen, use the up and down arrows to set the amount of time in seconds to pass before the APM times out. 3. To modify the APM name, enter a new name in the Apollo Platform Manager Name field. 4. To modify the password: a. Enter the New Password. b. Confirm the entry in the Re-enter Password field. 5. To modify the PollPower settings, click the Enable Pollpower slider in the Power box: Yes Enable PollPower No Disable PollPower 6. To modify the Power Cap Mode settings, select a mode from the drop-down menu in the Power box: None There is no power protection among the chassis connected to the APM. Default This mode protects against brown out due to a power supply loss and allows the chassis or rack to continue running at reduced performance in the event of a power supply loss. 60 Using the GUI

61 Fixed The total wattage is divided equally among the chassis connected to the APM or can be zone specific. To set power cap values, see "Setting power cap values." Variable The total wattage can move around among the chassis connected to the APM or can be zone specific. To set power cap values, see "Setting power cap values." Redundant If the power supplies of half of the chassis are lost, performance is reduced to protect the chassis against a brown out. 7. To modify the Power Cap Poll frequency, enter the amount of time in seconds in the Power box. 8. To modify the Ethernet settings: a. Use the sliders to enable or disable DHCP, Telnet, and SSH. b. Assign ethernet configurations accordingly. If the Enable Linked APMs field in the Linked APM box is set to Yes, the IP address cannot be changed. 9. To modify the Linked APM settings, enable or disable linked APMs using the Enable Linked APMs slider. 10. Click Submit to save the updated configuration within APM. All settings are persistent and stored in the APM. Using the GUI 61

62 Cooling Distribution (CDU) The Cooling Distribution Unit page displays a graphical representation of the status of the HPE Apollo 8000 System icdu. The status includes the following data for both the supply and return water: Valve positions Temperature Outlet flow Pressure CDU air temperature CDU cooling fan output CDU relative humidity CDU dew point temperature VFD pump (VFD pump output and lock-out status) Vacuum pump (Lock-out set point and lock-out status) Facility leak detector* Emergency power off* Door position* Door locks* Rack temperature sensors* Battery* (*Items appear if the Thermal Controller is present.) The Cooling Distribution (CDU) menu option appears for other Apollo systems but is functional only for the HPE Apollo 8000 System icdu. For detailed descriptions of icon classifications and status indications, see "Icon classifications and color status indicators." Rack Thermal Status The Rack Thermal Status page displays a graphical representation of the status of the thermal components and sensors only in the f8000 rack. Click the rack icon to display the Rack Thermal Status page. 62 Cooling Distribution (CDU)

63 The Rack Thermal Status page appears. Thermal rack status includes the following data: Temperature Water pressure Leaks Flow Emergency power off Door position Door locks Valve position and status Hover the mouse over any icon to see the specific sensor name. Using the GUI 63

64 For detailed descriptions of icon classifications and status indications, see "Icon classifications and color status indicators." Consolidated Management Ports The Main Screen defaults to show the Consolidated Management Ports screen. The Consolidated Management Ports screen of the APM interface includes a graphical representation of the components connected to and managed by the APM. To access the Consolidated Management Ports page: 1. Click Consolidated Management Ports on the left of the screen. 2. Select the name of the APM that you want to access. The Consolidated Management Ports page appears. The following information is displayed: General: Chassis count Total number of chassis connected to the APM consolidated management ports Server count Total number of servers connected to the APM consolidated management ports 64 Consolidated Management Ports

65 Compute alerts Active alerts on the servers (Enclosure 1-10) connected to the APM, such as an unhealthy fan or power supply Infrastructure alerts Active alerts on the PDM ports (PDM 1-6) connected to the APM, such as a malfunctioning PDM port Layout: The graphical representation of the alert classification indicates the amount and severity of alerts for the managed components of the APM. For more information, see "Alert classifications." Names of connected components Overview of which ports have components connected Component details Each component listed under Layout can be selected to view additional component details. Examples of components that might appear include: PDU UPS HPE ipdu Intelligent Extension Bar High Voltage DC Power Shelf To view component details, click the component box to display the information related to that component. Depending on the managed component, the detailed information displayed differs. Example of HPE ipdu Intelligent Extension Bar details Example of High Voltage DC Power Shelf details Component details 65

66 To manage the selected component, perform any of the following: Click the green power icon to power off the managed component. The power icon no longer appears green, indicating there is no power available to the component. Click the light bulb icon to illuminate the UID LED on the managed component. The light bulb icon appears blue if the UID LED is illuminated on the managed component. If there is an active alert on the managed component, selecting the component box provides additional information regarding the alert. For more information, see "Alert classifications." Rack Distribution Module The Rack Distribution Module page of the APM interface includes a graphical representation of the components connected to and managed by the APM. To access the Rack Distribution Module page: 1. Click Rack Distribution Module and module number on the left of the screen. 2. Select the name of the APM you want to access. The Rack Distribution Module page appears. 66 Rack Distribution Module

67 The following information is displayed: General: Chassis count Total number of chassis connected to the rack distribution module Server count Total number of servers connected to the rack distribution module Compute alerts Active alerts on the servers connected to the rack distribution module, such as an unhealthy fan or power supply Layout: The graphical representation of the alert classification indicates the amount and severity of alerts for the managed components of the APM. For more information, see "Alert classifications." Names of connected servers Overview of which ports have components connected Component details Each component listed under Layout can be selected to view additional component details. 1. Click the component box to display the information related to that component. A new page opens and displays information relevant to that component. 2. To see the status of the components, scroll over the graphical representations. The status updates within the circle. Warning Example Component details 67

68 Alerts If an active alert is on the managed component, clicking the component box provides additional information regarding the alert. For more information, see "Alert classifications." There are many alerts that can register within APM. These alerts can be viewed from the: Consolidated Management Port page Alert Log For more information on specific alert messages, see "Alert messages." Viewing alerts with the Consolidated Management Port page Procedure 1. Click Consolidated Management Ports on the left of the screen. 2. Click the name of the APM that you want to access. The Consolidated Management Ports page appears. 68 Alerts

69 All active alerts appear under the General section. For more information on the specific alert details, either select the alerting device from the Consolidated Management Ports page, or see the Event Log page. Alert classifications The graphical color-coded alert display represents all the ports connected to the APM. Each port has its own slice-of-the-pie chart and is color-coded based on its current status. The color assigned indicates the level of attention and support required to manage the alert: Gray No device is connected to the port. No attention is required. Green A device is connected to the port and is working within normal operating parameters. No attention is required. Yellow A device is connected to the port and is issuing a warning, such as a nonoperating fan within a server. Review the alerting condition. Red A device is connected to the port and is issuing a critical error. Immediate action is required. For more specific information about alerting devices, select the alerting device on the Consolidated Management Port page, or view the Event Log page. Viewing the Alert Log Click the alert icon at the top right of the screen: Alert classifications 69

70 The Alert Log appears and displays the last 100 active events, including the specific alert logged within APM. The status of the each log entry displayed in the far left column of the list is filtered by warning and critical entries. Log entry status symbol Description Normal - No action required Warning - Investigate and remediate, if necessary Critical - Investigate and repair Additional/Other information The Log does not poll automatically, so it must be refreshed to get the latest event entries. To refresh the Log, click RERESH LOG. To clear the alert log, click Clear Log. All entries in the system are cleared from the log, including any faults. Logging off Log off the APM when no longer accessing the APM or to change users. 70 Logging off

71 Procedure 1. Click the user icon at the top right of the screen. 2. Click Logout. 3. Do one of the following: Click OK to continue logging off the APM. Click Cancel. Accessing help To locate basic instructions and information about the APM interface, an online help file is available. Procedure To access the Help file, click the help icon at the top right of the screen. The online HELP file opens in a new window. Accessing help 71

72 Using the Command Line Interface Command line conventions CLI input is case insensitive except when otherwise noted. The CLI uses a simple, case insensitive syntax: verb noun "<argument>" Each command follows the conventions listed in the following table. Symbol <lower case> UPPER CASE Description Denotes the variable within the angle brackets that must be substituted with a value, such as a user name. Symbols must be removed. Denotes input to be entered as shown. Unless noted, symbol is not case sensitive. Used to separate input options. { } Denotes a list of mandatory choices that you must make. For example, SET GATEWAY {NONE <ip_address>} must be in the form of either of the following: SET GATEWAY NONE SET GATEWAY <ip_address> [ ] Denotes an optional argument or set of characters. " " Encloses command arguments that contain spaces. When a command syntax includes arguments enclosed in double quotes, the quotation marks are required even if the argument contains no spaces. Accessing the APM CLI You can access the APM CLI using the following methods: SSH Telnet APM serial port Accessing the CLI using SSH Procedure You can access the CLI using any SSH client. 1. Start a session and connect to the APM. 2. Log in to the APM using a valid account name and password. 72 Using the Command Line Interface

73 3. Enter commands for APM at the CLI command prompt. 4. Terminate the remote access session by closing the communication software or entering one of the following at the CLI command prompt: EXIT LOGOUT QUIT Accessing the CLI using Telnet Procedure You can access the CLI using any Telnet client. 1. Start a session and connect to the APM. 2. Log in to the APM using a valid account name and password. 3. Enter commands for APM at the CLI command prompt. 4. Terminate the remote access session by closing the communication software or entering one of the following at the CLI command prompt: EXIT LOGOUT QUIT Accessing the CLI using the APM serial port Procedure You can access the APM through a physical connection to the serial port using any serial terminal client. 1. Verify that the client settings are configured to match the serial port. For more information, see "Serial Port Configuration." 2. Start a session and connect to the APM. 3. Log in to the APM using a valid account name and password. 4. Enter commands for APM at the CLI command prompt. 5. Terminate the remote access session by closing the communication software or entering one of the following at the CLI command prompt: EXIT LOGOUT QUIT Saving configurations You must save your configurations. Otherwise, the configuration will be lost when you reset or reboot the APM. To save a configuration, enter the SAVE command. General commands The following sections contain common commands for setting up and operating the APM: Working with passwords Working with zones Accessing the CLI using Telnet 73

74 Basic configuration information Reboot and reset commands Topology and inventory Linked APM modules Using the help For a complete list of commands available to the APM, see "CLI commands." Working with passwords APM has a password recovery mechanism through the reset switch. If you press the reset switch for more than 5 seconds, the APM reboots and proceeds in the password recovery mode. In the password recovery mode, the APM boots up without asking for a password. All network access is disabled and access is available only through the serial console. Initially, or after resetting the APM to factory settings, the APM is configured only for access through the Administrator account. If password access to the APM is enabled, the password for the administrator account is stored in the APM. Similarly, if other local accounts are created on the APM, or if the account is configured for remote authentication with RADIUS, this configuration is stored in the APM. If the APM is moved to another rack, the accounts, passwords, and remote access configuration move with the APM. Enabling network access to the APM requires that password access is enabled. For more information on working with APM passwords using the CLI, see the following: Enabling APM passwords Setting APM passwords Disabling APM passwords Changing APM passwords Resetting factory settings for APM Enabling APM passwords Procedure SSH, Telnet, and serial port access require the password feature to be enabled. To enable the password protection feature, enter the ENABLE PASSWORD command. Setting APM passwords Procedure 1. To set the password for the current login, enter the SET PASSWORD command. 2. Enter a password. The password must be between 8 and 40 characters, and can include: Uppercase letters Lowercase letters Underscores (_) Dashes (-) At signs (@) Pound signs (#) 74 Working with passwords

75 Carets (^) Ampersands (&) Exclamation points (!) Plus symbols (+) Equal symbols (=) Tilde (~) Numerical values between 0 to 9 3. Press the Enter key. The password is saved and enabled. Alternatively, you can set the password by entering SET PASSWORD < password >. For example, enter the following: SET PASSWORD "alphabravo" When entering a password in this manner, you must include quotation marks around the password being set. This form of command is useful for scripted setup. Disabling APM passwords This command can only be run from the serial console. To disable the password, enter the DISABLE PASSWORD command. This command disables the password protection feature. If the password is disabled, all network interfaces are disabled and access is available only via the serial console. Changing APM passwords Do one of the following: To change the password of the current user, enter the SET PASSWORD "<newpassword>" command. This changes the password of the current user to "<newpassword>". To change the password of a specific user, enter SET PASSWORD ACCOUNT "<user>" "<newpassword>". This command changes the password of the "<user>" to a "<newpassword>". NOTE: Only the Administrator can add or remove an account. You can change your own password, but only the Administrator can change another user's password. Resetting factory settings for APM Procedure This command restores the APM to factory settings, including disabling password-protected access and disabling network access, and then performs a reboot. 1. Enter the RESET FACTORY command. 2. Do one of the following: Enter Y at the prompt to reset the APM. Enter N to cancel. Disabling APM passwords 75

76 WARNING: When you enter the RESET FACTORY command, APM erases your entire configuration. Before resetting factory defaults, consider saving your configuration. Use the SHOW CONFIG command to view configuration details. NOTE: This command can be run only from the serial console. Working with zones APM supports collecting multiple chassis into zones, which allows them to be managed as a single unit. For more information on working with zones using the CLI, see the following: Showing zones Adding zones Saving zones Removing zones Showing zones To display all the currently defined zones and their respective member chassis, enter the SHOW ZONES command. For example: HPE APM> show zones Zone BLUE: Platform Manager port 1: all Dist. Module ports included Zone RED: Platform Manager port 1: Dist. Module port 2 HPE APM> Adding zones To add one or more chassis to a zone, enter: ADD ZONE "<zone_name>" "[[<PORT#> <DMPORT#>]] [<PORT#> ALL] [ALL]" For example: HPE APM> add zone "red" 1 2 Zone RED does not exist, would you like to create it? (Y/N) -> Yes Note: there currently is no physical chassis plugged into Platform Manager port 1, Dist. Module port 2 RED zone added Zone definition changed, do you want to save this data to the EEPROM? (Y/N) -> No Note: You can also save zone data to the EEPROM at any time with the SAVE ZONES command HPE APM> If the zone does not already exist, then it will be automatically created, and the specified chassis will be added to it. You can create up to four zones. 76 Working with zones

77 The parameters enable the addition of all chassis on all APM ports, all the chassis plugged into an APM port through an APM Distribution Module, or one or more specific chassis on a specified APM port and APM Distribution Module port. The syntax is similar to other APM commands such as SHOW POWER or SHOW RACK in how APM and APM Distribution Module ports are specified. When adding a chassis to a zone, the chassis does not have to be present and plugged into the APM. The APM issues a message if the hardware is not present. For APM operations that might use zones (for example, SET POWER BASELINE), only those chassis that exist and are defined in the zone are considered for the operation. For example: ADD ZONE "my_zone" 1 5 Adds the chassis plugged into Consolidated Management port 5 on the APM to zone MY_ZONE. If MY_ZONE did not already exist, it will be created. ADD ZONE "my_zone" 1 all Adds all the chassis plugged into the Consolidated Management ports on the APM. ADD ZONE "my_zone" all Adds all chassis connected to the APM to zone MY_ZONE. ADD ZONE BLUE 1 ALL 2 ALL 3 1 Adds all the chassis plugged into the Consolidated Management ports on the APM, all the chassis plugged into the APM Distribution Module that is plugged into APM port 2, and the chassis plugged into the first port of the APM Distribution module that is plugged into APM port 3. For more information, see the ADD ZONE command. Zones cannot overlap. Saving zones To commit the defined zones and their member chassis to the on-board EEPROM, enter the SAVE ZONES command. You can define and save up to four zones. These zones are automatically loaded from the EEPROM when the APM is reset. Removing zones To remove one or more chassis from a zone definition, enter: REMOVE ZONE "<zone_name>" "[[<PORT#> <DMPORT#>]] [<PORT#> ALL] [ALL]" If no more chassis exist in the zone after the target chassis is removed, then the zone is automatically deleted. The syntax for indicating which chassis is to be removed is identical to the ADD ZONE command. For example: The REMOVE ZONE "my_zone" ALL command removes all chassis from the zone MY_ZONE. This command also deletes the zone definition of MY_ZONE because no chassis is associated with it. The REMOVE ZONE "my_zone" 1 ALL command removes all chassis plugged into the Consolidated Management ports on the APM. For more information, see the REMOVE ZONE command. Basic configuration information The following commands are available to show or set basic APM configuration: Saving zones 77

78 Showing configurations Showing information Showing the version Showing the name Setting the name Showing the time Setting the time Setting the session timeout Setting the UID LED Showing configurations To show the configuration, enter: SHOW CONFIG The output of this command is a script of commands that can be used to recreate the current configuration. Showing information To show information about the APM itself, enter: SHOW INFO Information including the following is displayed: Manufacturer Product Name Part Number Spare Part Number Serial Number FRU File ID Showing the version To show the version, enter: SHOW VERSION For example, the following text appears: APM-D4C9EFCB00B4> show version HPE Apollo Platform Manager (c) Copyright 2016 Hewlett Packard Enterprise Development LP All rights reserved Version 2.30 Build time was Apr , 11:58:04 To show the HPE Power Management Controller Utility hardware and firmware versions as well as the license status of all servers in the enclosures, enter SHOW VERSION ALL. Showing the name To show the name, enter SHOW NAME. The name appears. 78 Showing configurations

79 For example, the following text appears on the screen: APM> show name APM Setting the name To set the name that appears in the log and syslog entries, enter SET NAME "<name>". For example: SET NAME "alphabravo" System names can be up to 80 characters and can include uppercase letters, lowercase letters, underscores (_), dashes (-), and numerical values between 0-9. Dashes (-) are not supported as the first character. To save the power manager name, press the Enter key. Naming the APM is optional. The name that appears in log entries on the syslog server, as well as the CLI prompt, is the APM name. Showing the time To show the time, enter SHOW TIME. The time appears. For example, the following text appears: APM> show time MON OCT 31 12:56: Setting the time To set the time, enter: SET TIME <month> <day> <year> <hour> <minute> Enter the hour in 24 hour format. For example, enter 3:00 p.m. as 15. APM does not automatically adjust for Daylight Savings Time. Setting the session timeout To set the inactivity timeout, enter: SET TIMEOUT {<timeout_value> NONE} where <timeout_value> is the timeout value measured in seconds. For example, to set a 30 second timeout, enter: SET TIMEOUT 30 If you specify NONE, then no timeouts are set. For example, enter: SET TIMEOUT NONE Setting the UID LED To activate the UID LED on the APM, enter: SET UID ON To deactivate the UID LED, enter: SET UID OFF If the command specifies an APM port and Distribution Module port, then the UID of that indicated chassis is turned on or off. Setting the name 79

80 Reboot and Reset commands The following commands are available to reboot or reset the APM: Performing a reboot Performing a reset Performing a reset buddy Clearing the screen Exiting, logging out, or quitting Resetting factory settings Rebooting and resetting factory settings To reboot, enter REBOOT. Unsaved configuration settings are lost. Performing a reset To reset, enter RESET. Unsaved configuration settings are lost. Performing a reset buddy To reset or reboot the other APM module (the Buddy, if connected), enter RESET BUDDY. Clearing the screen To clear the session screen, CLEAR SCREEN. Exiting, logging out, or quitting APM To exit enter one of the following: EXIT, LOGOUT, enter QUIT. Resetting factory settings NOTE: This command can be run only from the serial console. NOTE: Resetting the APM to factory defaults also disables APM RESTful API access. To reset the factory settings, enter RESET FACTORY. All configuration, accounts, zone definitions, and password settings will be lost. Password access will be disabled. Network access will be prevented due to disabled password. Topology and inventory APM collects information from connected enclosures, including: Apollo enclosure product names Apollo enclosure product identifiers (SKU) Apollo enclosure serial numbers Node MAC addresses To view topology and inventory information, do any the following: 80 Reboot and Reset commands

81 Showing the rack Showing the servers Showing topology Showing thermal status Showing the MAC address Showing the icdu Showing the icdu status Showing the icdu full status Showing the rack To show the contents of the rack, enter SHOW RACK. The rack information appears, including the product name, product SKU, and product serial number of the chassis. This command produces the same result as the SHOW TOPOLOGY command. To show a particular rack, enter SHOW RACK, followed by the APM port. For example, enter: SHOW RACK 2 4 For example, output similar to the following will appear: APM-D4C9EFCB00B4> show rack 1: Dist. Module 1: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off Status : 1 : Compute node (active) 2 : Compute node (active) 3 : Compute node (active) : Compute node (active) 20 : Compute node (active) Power supply slot 1 is empty Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good Fan slot 2 is occupied, status good Fan slot 3 is occupied, status good Fan slot 4 is occupied, status good Fan slot 5 is occupied, status good 2: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : Compute node (active) 2 : Compute node (active) 3 : Compute node (active) : (unused) 20 : (unused) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Showing the rack 81

82 Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 3: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : (unused) 2 : (unused) 3 : Compute node (active) : Compute node (active) 20 : Compute node (active) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 4: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : Compute node (active) 2 : Compute node (active) 3 : Compute node (active) : (unused) 20 : (unused) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 5: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : (unused) 2 : (unused) 3 : (unused) : Compute node (active) 20 : Compute node (active) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 6: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : Compute node (active) 82 Using the Command Line Interface

83 2 : Compute node (active) 3 : Compute node (active) : Compute node (active) 20 : Compute node (active) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 7: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : (unused) 2 : (unused) 3 : Compute node (active) : Compute node (active) 20 : Compute node (active) Power supply slot 1 is occupied, status good Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 8: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off 1 : Compute node (active) 2 : (unused) 3 : Compute node (active) : (unused) 20 : (unused) Power supply slot 1 is empty Power supply slot 2 is occupied, status good Fan slot 1 is occupied, status good... Fan slot 5 is occupied, status good 9: Product Name :THERM CTRL Product SKU : Serial Number:PECUR0ALM6D00F UID :off Status : 10: Product Name :THERM CTRL Product SKU : Serial Number:PECUR0ALM6D00N UID :off Status : 2: (vacant) 3: (vacant) 4: (vacant)... 9: [PDM1] HVDC Power Shelf Using the Command Line Interface 83

84 Firmware Rev : 68 Hardware Rev : 0 Rectifiers: 1: V Rectifier 2: V Rectifier 3: V Rectifier 4: V Rectifier Power Meter: 1: 480V power meter 2: 480V power meter 10: [PDM2] HVDC Power Shelf Firmware Rev : 68 Hardware Rev : 0 Rectifiers: 1: V Rectifier 2: V Rectifier 3: V Rectifier 4: V Rectifier Power Meter: 1: 480V power meter 2: 480V power meter Showing the servers To show the servers, enter SHOW SERVERS. The server information appears and includes information that APM receives from ilo when SSO is enabled, such as health status, server identification information, and ilo IP addresses. This information also displays in the GUI on the Inventory page. APM> show servers 1: Dist. Module 1: Enclosure Product Name :HPE Apollo 4520 Gen9 Product SKU : B22 Serial Number:USE15453AC UID :off Servers : 1 : Compute node (active) Host MAC: FC:15:B4:7A:8E:08 Serial Number: USE152813A, Host Name: TestServer1, Asset Tag: Not Set Health=OK, State=Enabled ilo IP address: IPv4= , IPv6=fe80::5265:f3ff:fe65:c922 2 : Compute node (active) Host MAC: FC:15:B4:7A:8D:28 Serial Number: USE , Host Name: TestServer2, Asset Tag: Not Set Health=OK, State=Enabled ilo IP address: IPv4= , IPv6=fe80::5265:f3ff:fe65:c8c0 2: (vacant) 3: (vacant) 4: (vacant) 5: (vacant) 84 Using the Command Line Interface

85 6: (vacant) 7: (vacant) 8: (vacant) 9: (vacant) 10: (vacant) 2: (vacant) 3: (vacant) 4: (vacant) 5: (vacant) 6: (vacant) 7: (vacant) 8: (vacant) Showing topology To show the topology of everything that connects to the APM, enter SHOW TOPOLOGY. This command produces the same results as the SHOW RACK command. Showing thermal status To show the status of thermal components on an Apollo 8000 system, enter SHOW THERMAL STATUS. The thermal status of all components is displayed. For example, output similar to the following will appear: xample, output similar to the following will appear: Upper Rack Zone: Sensor Index Status Leak Detector 0 no leaks Leak Detector 1 no leaks Leak Detector 2 no leaks Door Sensor 0 opened ( front ) Door Sensor 1 opened ( rear ) Valve Sensor 0 not present Valve Sensor 1 not present Water Temp (RTD) degc ( supply ) Water Temp (RTD) degc ( intermediate ) Water Temp (RTD) degc ( return -bot ) Flow ( mv reading) Temp-Humid -board degc, %RH Dew Point Temp degc Air Temp degc (Dev 0:0 ) Air Temp degc (Dev 2:0 ) DC/DC Power Supply mv (PS 0 - present - OK) DC/DC Power Supply mv (PS 1 - present - OK) Control Index Status Door Lock 0 closed ( front ) Door Lock 1 closed ( rear ) Valve Control 0 not present Valve Control 1 not present EPO 0 running Fan State Health RPM R1 Status R2 Status Fan mv Fan % Showing thermal status 85

86 1 : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy Cell Fan % Lower Rack Zone: Sensor Index Status Leak Detector 0 no leaks Leak Detector 1 leaks detected Leak Detector 2 no leaks Door Sensor 0 (not present) Door Sensor 1 (not present) Valve Sensor 0 opened (supply) Valve Sensor 1 opened (return) Water Temp (RTD) degc ( supply ) Water Temp (RTD) degc ( intermediate ) Water Temp (RTD) degc ( return -bot ) Flow ( mv reading) Temp-Humid -board degc, %RH Dew Point Temp degc Air Temp degc (Dev 0:0 ) Air Temp degc (Dev 2:0 ) DC/DC Power Supply mv (PS 0 - present - OK) DC/DC Power Supply mv (PS 1 - present - OK) Control Index Status Door Lock 0 not present Door Lock 1 not present Valve Control 0 opened (supply- AUTO) Valve Control 1 opened (return- AUTO) EPO 0 running Fan State Health RPM R1 Status R2 Status Fan mv Fan % : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy Using the Command Line Interface

87 9 : Fan installed healthy healthy healthy : Fan installed healthy healthy healthy Cell Fan % Showing the MAC address To show the MAC address, enter SHOW MACADDR. The MAC address appears. The MAC address information appears following each module listing. To show a particular MAC address, enter SHOW MACADDR and then the APM port or both the APM port and APM Distribution Module port. For example, enter: SHOW MACADDR 2 4 The following text might appear on screen. APM-D4C9EFCB00B4> show macaddr 1: Dist. Module 1: Enclosure Product Name :Apollo 8000 Product SKU : Serial Number: UID :off Status : 1 : Compute node (active) Host MAC: 38:EA:A7:9C:10:A6 2 : Compute node (active) Host MAC: 38:EA:A7:9C:10:22 3 : Compute node (active) Host MAC: 38:EA:A7:9C:10:8A 4 : Compute node (active) Host MAC: 38:EA:A7:9C:10:96 5 : Compute node (active) Host MAC: 38:EA:A7:9C:11:0A 6 : Compute node (active) Host MAC: 38:EA:A7:9C:10:E8 7 : Compute node (active) Host MAC: 38:EA:A7:9C:10:1C 8 : Compute node (active) Host MAC: 38:EA:A7:9C:10:08 9 : Compute node (active) Host MAC: 38:EA:A7:9C:10:92 10 : Compute node (active) Host MAC: 38:EA:A7:9C:10:C8 11 : Compute node (active) Host MAC: 38:EA:A7:9C:10:D6 12 : Compute node (active) Host MAC: 38:EA:A7:9C:10:EC 13 : Compute node (active) Host MAC: 38:EA:A7:9C:10:7E 14 : Compute node (active) Host MAC: 38:EA:A7:9C:10:82 15 : Compute node (active) Host MAC: 38:EA:A7:9C:10:3E 16 : Compute node (active) Host MAC: 38:EA:A7:9C:10:D4 17 : Compute node (active) Host MAC: 38:EA:A7:9C:11:0E 18 : Compute node (active) Host MAC: 38:EA:A7:9C:10:B8 19 : Compute node (active) Host MAC: 38:EA:A7:9C:10:86 20 : Compute node (active) Host MAC: 38:EA:A7:9C:10:8E Power supply slot 1 is occupied, status bad Power supply slot 2 is occupied, status bad Fan slot 1 is occupied, status good Fan slot 2 is occupied, status good Fan slot 3 is occupied, status good Fan slot 4 is occupied, status good Fan slot 5 is occupied, status good Showing the MAC address 87

88 Showing the icdu To show the status of all icdus, enter SHOW ICDU. The IP address of all icdus being monitored appears. For example, the following text might appear: Index IP Address Showing the icdu status To show the status of icdu components, enter SHOW ICDU STATUS. The status of all icdu components appear. For example, the following text might appear: Cooling Distribution Unit #1 (IP: ): Facility Water Side 6.00 : B04 Facility Inlet Temperature : PT23 icdu Facility Inlet Pressure : Facility Heat Exchanger differential pressure : PT25 icdu Facility Outlet Pressure : B03 Facility Outlet Temperature : Water Regulation Valve output IT Water Side : B02 IT Pump discharge temperature : PT24 IT Pump discharge temperature : pump water pressure differential display : pump water differential pressure set point : PT21 IT HEX Outlet water pressure : B01 IT HEX Outlet Temperature : Pump supply temp set point Pump Status : Pump VFD output 4.80 : PT22 Reservoir Pressure false : vfd is locked out false : vacuum pump on false : vacuum pump lockout false : Air Inlet Valve is on false : Isolation Valve1 is open false : Isolation Valve 2 is open Showing the icdu full status To show the full status of the icdu, enter SHOW ICDU FULL. The complete status for the icdu appears. For example, the following text might appear: Cooling Distribution Unit #1 (IP: ): Reg Value Description Bypass Valve output Water Regulation Valve output Pump VFD output Facility Heat Exchanger differential pressure 88 Showing the icdu

89 B03 Facility Outlet Temperature B04 Facility Inlet Temperature IT Heat Exchanger differential pressure B02 IT Pump discharge temperature B01 IT HEX Outlet Temperature pump water pressure differential display PT22 Reservoir Pressure BMS_facility water regulation valve control value BMS pump bypass valve control value BMS vfd control signal Pump supply temp set point pump water differential pressure set point vacuum pressure cut_in vacuum pressure cut_out vacuum pressure set point vacuum pump lockout offset PT24 IT Pump discharge temperature PT23 icdu Facility Inlet Pressure PT25 icdu Facility Outlet Pressure PT21 IT HEX Outlet water pressure Low icdu differential pressure alarm point High icdu differential pressure alarm point High facility Inlet temp alarm point High facility Outlet temp alarm point Air Inlet solenoid cut in based on vac pressure Air Inlet solenoid cut out based on vac pressure plan status variable for BMS VFD Control Location VFD current VFD DC Voltage VFD Temperature VFD External Reference (control signal) VFD Fault word VFD Fault word VFD Fault word VFD Frequency VFD kwh Count motor nominal current (Rated) motor nominal frequency (Rated) motor nominal power (Rated) motor nominal speed (Rated) motor nominal voltage (Rated) VFD MWH Count VFD Output Voltage VFD Power Reading VFD Run Time VFD Speed motor information reported by Modbus VFD Torque Software Version Air Inlet solenoid ON time Air Inlet solenoid OFF time 0001 false BMS is offline 0002 false high water alarm 0003 false alarm leak detection 0004 false Modbus offline 0005 false tank overflow alarm Using the Command Line Interface 89

90 0006 false VFD Alarm 0007 false pump bypass valve on 0008 true vacuum pressure okay 0009 false vacuum pump on 0010 false vacuum pump enable out 0011 true vfd is on 0012 true vfd enable 0013 false BMS is active and communicating 0014 false BMS vacuum pump control (0 = OFF 1 = ON) 0015 true Unit on command 0016 false vacuum pump lockout 0017 false vfd is locked out 0018 false Switch in HAND position 0019 true Switch in AUTO position 0020 false low water alarm 0021 false low pump differential pressure alarm 0022 false high pump differential pressure alarm 0023 false High facility inlet pressure alarm 0024 false High facility Outlet pressure alarm 0025 true icdu #1 is lead unit 0026 false icdu #2 is lead unit 0027 false Trigger new rotation manually 0028 true Isolation Valve Output 0029 false Isolation Valve1 is open 0030 false Trigger new rotation based on time 0031 false isolation valve failure to open alarm 0032 true isolation valve output is on 0033 false rotation alarm - rotation failed to occur 0034 false isolation valve failure to close alarm 0035 false Flexrack Isolation Valve is open 0036 true icdu1 is on plan and ok to run 0037 false icdu2 is on plan and ok to run 0038 false Isolation Valve 2 is open 0039 true Isolation Valve 1 is closed 0040 true Isolation Valve 2 is closed 0041 false Air Inlet Valve Output 0042 true Middle vacuum tank level warning 0043 false Air Inlet Valve is on 0044 false leak alarm based on vacuum pressure 0045 true plan communications offline 0046 false icdu in critical 0047 true icdu in warning/degraded 0048 false Loss of iso valve open signal during operation 0049 false Low vacuum pressure alarm 0050 false Vacuum pump run time exceeded timer 0051 false Low Facility HEX differential pressure alarm icdu water tank level High IT discharge temperature set point Low facility HEX diff pressure alarm set point icdu water tank volume Level to start filling tank Level to stop filling tank Tank level band Address of controller in plan network Alarm history display only Alarm history display only Alarm history display only 90 Using the Command Line Interface

91 Alarm history display only Alarm history display only Pressure units 0=psig, 1=psia, 2=kpag, 3=kpaa Tank volume units 0=gallon, 1=liter Alarm history display only Pump speed algorithm 0=local DP, 1=freq, 2=torque BMS_Current day BMS_Current month BMS_Current year BMS_Current hour BMS_Current minute 0052 true plan communications offline (cable broken) alarm enable 0053 false Clock type (0=pCO 1=Network) 0054 false In lead/lag rotation type 0055 true In parallel operation type 0056 false Toggle previous alarm 0057 false Toggle next alarm 0058 false Reset alarm log 0062 true Facility isolation valve output status 0063 true Facility isolation valve output command 0064 false icdu water fill valve output command 0065 false icdu water fill valve status 0066 false Facility isolation valve 1 is open (status) supply 0067 false Facility isolation valve 1 is closed (status) supply 0068 false Facility isolation valve 2 is open (status) return 0069 false Facility isolation valve 2 is closed (status) return 0070 false Facility leak detection #1 alarm 0071 false Facility leak detection #2 alarm 0077 false Facility isolation valve failure to close alarm 0078 false Facility isolation valuve failure to open alarm 0079 true Allow time rotations 0080 false Tank fill valve runtime alarm 0081 false High IT discharge temperature alarm 0082 false Modbus offline (VFD comm) 0083 false VFD current overload alarm 0084 false Tank leveling active 0085 false Temp units 0=celcius 1=fahrenheit Linked APM modules The Linked APM feature enables communication between different APMs. Using XML commands through a secure HTTPS link, the APMs establish a trust pair, allowing the paired modules to receive information from one another. A group of Linked APMs can receive information from any of the APMs within the group. Therefore, a user can log into one of the APMs and get information about any other APM within the Linked APM group. Not all CLI commands function in the Linked APM target. The following commands allow users to access Linked APMs: CLEAR FAULTS CLEAR LOG RESET CM SET ASSETINFO SET FAULTS SET POWER Linked APM modules 91

92 SET POWER BASELINE SET POWER CAPS SHOW ASSETINFO SHOW FAULTS (limited to 20 log entries) SHOW INFO SHOW MACADDR SHOW LOG (limited to 20 log entries) SHOW POWER SHOW POWER BASELINE SHOW POWER CAP SHOW RACK SHOW SERVERS SHOW TOPOLOGY Enable Linked APM To turn on the Linked APM interface, enter ENABLE LINKED APM. Disable Linked APM Show APM Add APM To turn off the Linked APM interface, enter DISABLE LINKED APM. To see information from the APMs in the Linked group, enter SHOW APM. The following information appears: Linked APM IP address Assigned Linked APM target number Fault logs and alerts per chassis Time stamp of most recent update or communication NOTE: Linked APM must be enabled before an APM can be added to a Linked group. For more information, see "Enable Linked APM." NOTE: To add an APM to a Linked group, the APM must have XML Secure enabled. To enable it, enter the ENABLE XML SECURE command. For more information, see "Enabling XML." To add an APM to a Linked group, enter ADD APM. This command requires the IP address and Administrator password of the target APM. When adding an APM to a Linked group, the user must be in the same target Linked group. You cannot add an APM from a different group. For more information, see "Set APM target." Remove APM To remove a linked-to APM, enter REMOVE APM <INDEX>. 92 Enable Linked APM

93 To remove the APM that the user is logged into from a Linked APM group, enter REMOVE APM 0. The IP address of the APM is removed from the Linked APM group. If the APM is reset to factory default settings, it is also removed from the group. For more information, see "Resetting factory settings." Set APM target Each CLI session can set its own Linked APM target. When a CLI session is opened, the target is always the APM that the CLI sessions is connected to. To select a different Linked APM group target, enter SET APM TARGET. Using the help To access the help, enter: HELP Each command has its own listings. For example, after the HELP CLEAR command is entered, the following appears: APM> help clear CLEAR FAULTS LOG SCREEN Empty log entries Empty the fault log Empty system log Clear the screen Set APM target 93

94 Using ilo Single Sign-On ilo Single Sign-On overview HPE ilo SSO integrates rack-level management with server-level management, to present a simple, uniform management system. SSO enables users to view the APM GUI, and then navigate to either infrastructurelevel data or specific server-level data. HPE Apollo systems automate security and management systems at the rack-level between the rack APM and the ilo-based hardware installed on the Apollo-based servers. APM is directly cabled to the controllers embedded in all HPE Apollo chassis using two-way communication, and therefore create a rack-level security domain where credentials are established through APM. If configured, this direct hardware relationship securely establishes a trust relationship between APM and ilo. SSO must be enabled, however, upon being enabled, all servers that are cabled within that rack are automatically included within the rack secure domain, and can be configured or accessed through APM. Requirements for using SSO The factory configuration for APM has SSO disabled. For ilo SSO to function, the following features must be enabled via CLI command: ENABLE ETHERNET ENABLE PASSWORD SET IP <ADDRESS> ENABLE XML SECURE ENABLE GUI ENABLE SSO Security access modes Multiple options exist for configuring the APM access modes: APM and ilo access is physically separate; therefore, both ilo and APM have separate security credentials. APM and ilo access is physically separate, but SSO is enabled and both ports are plugged into the same management network. Enabling SSO Procedure 1. Verify that the correct firmware versions are installed: HPE ilo 2.4 and above APM version Using the CLI commands, verify that the prerequisites are enabled: ENABLE ETHERNET ENABLE PASSWORD SET IP <ADDRESS> 94 Using ilo Single Sign-On

95 ENABLE XML SECURE ENABLE GUI ENABLE SSO After all CLI commands have been entered and SSO is enabled, the x.509 certificate is automatically generated and sent to ilo. To automatically use SSO and login to ilo within the GUI, click the IP addresses on either the Consolidated Management Ports page or the Inventory/Single Sign-On page. If SSO is enabled at startup, APM performs the sequence of events it performs when executing the ENABLE SSO command. If SSO is already enabled, and the user re-enters the ENABLE SSO command, a new message appears: An SSO key already exists. Do you want to generate a new certificate? (Y/N) Whether the user selects Y or N, APM will resend the certificate to ilo. Showing the SSO certificate To show the SSO certificate, enter the SHOW SSO CERTIFICATE command. The output displays the public SSO certificate if a technician wants to install the certificate on a server in a different rack. Disabling SSO Using the CLI, enter the DISABLE SSO command. A prompt appears asking if you would like to remove the SSO certificate: N The certificate is maintained and can be used to enable SSO in the future. Y The certificate is removed. If SSO is re-enabled, a new certificate will be generated. Showing the SSO certificate 95

96 Logging Overview of logging Logging enables you to see the following information in APM: Actions taken Events Time when the action was taken or event occurred APM has the following types of logs: Event logs, where APM records events. Fault logs, where APM records internal errors. These internal errors create alerts in which the red LED illuminates. For a list of alert messages, see "Alert messages." You can issue commands for both internal and external logging. Use an external syslog server for: Redundant copy of events and logs Not limiting the events list to only the last 500 events To ensure the correct time stamping in your logs, use the SET TIME command. For more information, see "Setting the time." Internal logging The APM has an internal 100 KB battery-backed memory to record logging events that have occurred in the rack. The fault log is stored in a separate 16 KB battery-backed area. Both logs are persistent through power loss or reboot of the unit. Showing and clearing the event log To show the event log, enter SHOW LOG. As an example, the following text might appear on screen: > show log Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 2 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 3 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 4 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 5 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 6 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 7 Nov 6 11:51:25 SLAPM system.0: Server found in chassis at Dist. Module #2, port 3, slot 8 Nov 6 11:51:25 SLAPM system.0: Power supply found in chassis at Dist. Module #2, port 3, slot 1 Nov 6 11:51:25 SLAPM system.0: Power supply found in chassis at Dist. Module #2, port 3, slot 2 96 Logging

97 Nov 6 11:51:25 SLAPM system.0: Power supply found in chassis at Dist. Module #2, port 3, slot 3 Nov 6 11:51:25 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 3, slot 1 status is good Nov 6 11:51:25 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 3, slot 2 status is good Nov 6 11:51:25 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 3, slot 3 status is good Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 1 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 2 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 3 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 4 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 5 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 6 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 7 Nov 6 11:51:25 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 3, slot 8 Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 1 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 2 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 3 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 4 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 5 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 6 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 7 status is OK Nov 6 11:51:25 SLAPM system.0: Fan in chassis at Dist. Module #2, port 3, slot 8 status is OK Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 1 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 2 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 3 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 4 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 5 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 6 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 7 Nov 6 11:51:26 SLAPM system.0: Server found in chassis at Dist. Module #2, port 6, slot 8 Nov 6 11:51:26 SLAPM system.0: Power supply found in chassis at Dist. Module Logging 97

98 #2, port 6, slot 1 Nov 6 11:51:26 SLAPM system.0: Power supply found in chassis at Dist. Module #2, port 6, slot 2 Nov 6 11:51:26 SLAPM system.0: Power supply found in chassis at Dist. Module #2, port 6, slot 3 Nov 6 11:51:26 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 6, slot 1 status is good Nov 6 11:51:26 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 6, slot 2 status is good Nov 6 11:51:26 SLAPM system.0: Power supply in chassis at Dist. Module #2, port 6, slot 3 status is good Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 1 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 2 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 3 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 4 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 5 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 6 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 7 Nov 6 11:51:26 SLAPM system.0: Fan found in chassis at Dist. Module #2, port 6, slot 8 Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 1 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 2 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 3 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 4 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 5 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 6 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 7 status is OK Nov 6 11:51:26 SLAPM system.0: Fan in chassis at Dist. Module #2, port 6, slot 8 status is OK Nov 6 11:51:27 SLAPM system: Local user Administrator logged in Nov 6 07:46:51 SLAPM Administrator: Ethernet interface enabled Nov 6 07:47:00 SLAPM Administrator: Telnet interface enabled Nov 6 07:47:00 SLAPM Administrator: ssh interface enabled Nov 6 07:47:05 SLAPM Administrator: Configuration was saved To clear the event log, enter CLEAR LOG. Showing and clearing the fault log To show the fault log, enter SHOW FAULTS. 98 Showing and clearing the fault log

99 As an example, the following text might appear on screen: > show faults May 4 19:43:43 APM-D4C9EFCB01CA system.0: Platform Manager Power Supply 1 is non operational May 5 01:42:20 APM-D4C9EFCB01CA system.0: Timeout waiting for Dist. Module mutex on Platform Manager port 3 May 6 03:51:16 APM-D4C9EFCB01CA system: Failed login attempt with user 'Administrator' from To clear the fault log, enter CLEAR FAULTS. External logging To show the syslog server address configuration information, enter SHOW SYSLOG. To set the syslog server address configuration, enter SET SYSLOG <ip_address>. Using an existing syslog server provides: Redundant copy of events and logs No limits to number of events that can be logged External logging 99

100 Power capping Power capping overview HPE Scalable System products, including HPE ProLiant SL Series, HPE Moonshot Series, and HPE Apollo Series provide a power capping feature that operates at the server enclosure level. With APM, the enclosure-level power capping feature can be expanded without the need to use the PPIC.EXE utility. A global power cap can be applied to all enclosures with one APM command, or different caps can be applied to user-defined groups by using flexible zones within the same rack. NOTE: Hewlett Packard Enterprise recommends configuring the APM such that it controls only one rack. Power capping requirements All nodes in the chassis must have ilo Scale Out or ilo Advanced License. Power capping and measurement tolerance The average chassis power level displayed by APM will not exceed 5% above the chassis power cap. NOTE: The power baseline process is required for power capping functionality to work properly. All servers must be powered on and running an expected typical workload before starting the power baseline process. Because the baseline process caps the servers briefly, performance is temporarily impacted while power is measured and the baseline established. As with any measurement system, variations in temperature, input power, and system loads will impact the accuracy of the power calculations. All power reading displayed by this utility has a -/+ 5% tolerance. However, meter errors can be both positive and negative, so guardband for meter tolerance, as a percentage of the cap, can approach zero as the number of servers increases. Invalidating a power baseline Since power baselines are global, the APM monitors the domains for changes in server and power supply presence when a power baseline has been established. If a change occurs (for example, if a new server is installed), then the APM detects this change and invalidates the current power baseline. This invalidation prevents any new caps from being set but does not disable any existing caps that are set. If a baseline has been invalidated due to changing hardware in the APM domain, the following options are available: If the change was caused by replacement of equipment (for example, a failed power supply was removed and a new one inserted), then you can restore the old baseline. This process is done by resetting APM and forcing it to reread and recompare the existing power baseline from the resident EEPROM. Use the SET POWER BASELINE command or the GUI Power Baseline feature to establish a new power baseline when the domain configuration changes due to: An SL Power Management Controller (SL Chassis) Firmware update. Power supply addition or removal. New server or enclosure installation or de-installation. Memory addition or removal from the tray. 100 Power capping

101 CPU addition or removal from the tray. GPU addition or removal from the tray. APM and APM Distribution Module cabling All supported SL enclosures and servers that are wired to the APM through one or more APM Distribution Modules can participate in power capping and monitoring. Separate power cap settings can be made for as many or as few of the enclosures as desired, but the power baseline process must operate as a global process that interacts with every supported enclosure that the APM is connected to through the APM distribution modules. Rack level power capping The rack level power cap is a power cap set at the APM level and, despite the name, can encompass a partial rack, a rack, or multiple racks. These domains are established by the reach of the APM and distribution module connections to the support SL enclosures combined with any optional zone definitions that may have been created. The term rack level power cap is used generically in this document to refer to any power cap that has been set at the APM level. The power capping feature has two main processes to it. The first process establishes a power baseline. The second process sets a power cap against the previously established power baseline. Power baseline The power baseline is a calibration that indicates the range of how little power the chassis can consume at their maximum allowable power cap and how much power they can consume when completely uncapped. The minimum value is derived by capping the servers at their maximum internally allowable cap setting, running the enclosure fans up to 90% of capacity, and then measuring the power consumption of the chassis at the power supply level. After a power baseline is established for all enclosures, the baseline is committed to the APM onboard EEPROM so that it becomes persistent when APM is reset during operation. NOTE: The power baseline process is required for power capping functionality to work properly. All servers must be powered on and running an expected typical workload before starting the power baseline process. Because the baseline process will cap the servers briefly, performance will be impacted while power is measured and the baseline established. After established and saved in the EEPROM, the baseline data can be examined at any time using the SHOW POWER BASELINE command. For example: > show power baseline APMPort DMPort Serial Number Min Cap Max Cap Set Cap Slots Populated CNK71600K (8) If an APM has baseline data in its EEPROM and it is reset, APM re-reads that baseline data back into memory as it boots back up. After the subsequent device discovery, APM compares the baseline data in the EEPROM to the actual rack contents to ensure that they did not change while it was offline or that it was not relocated to another rack. The APM validates the following items from the saved baseline data in the following instances: APM and APM Distribution Module cabling 101

102 The chassis listed in the baseline is present. The chassis has the same populated server slots. If a power cap had been set, then it is the power cap currently set on the chassis. If any of these do not match after a reset, then the APM logs an error to the log, indicating the mismatch in the baseline data, and the baseline data is invalidated. However, it is not erased from the EEPROM to provide you the chance to re-install any chassis or servers that invalidated the baseline data. To remove baseline data from the EEPROM, use the SET POWER BASELINE NONE command. After this command is used, the only way to re-establish a power baseline is to use the SET POWER BASELINE command or the GUI Power Baseline feature. If a power cap is currently in place, the SET POWER BASELINE NONE command cannot be used. The power cap must first be removed (SET POWER CAP NONE), then the baseline can be removed. If a power cap is currently in place and a SET POWER BASELINE command is issued, then any current power caps are removed in the calibration. New power caps can be established following the calibration process, assuming the new baseline data is saved to the EEPROM. The following text is an example output when an advanced license is installed on all chassis: > set power baseline Before running a baseline calibration - ensure that your configuration has all machines turned on and are running processes that are typical of the type of workload you expect them to run in a production environment. This process will briefly impact the performance of the servers that are being baseline calibrated as well as temporarily speed up the fans. Are you sure you wish to set a new power baseline for this system? (Y/N/Q) -> Yes Baselining power for servers located in chassis Power Manager port 1, Dist. Module port 1 Calibrating...done. Minimum cap value for this chassis is 777 Maximum cap value for this chassis is 3558 Setting power capping Use the SET POWER CAP command to specify a power cap. The command takes an AC wattage range that must be between the minimum and maximum values that were set with the SET POWER BASELINE command and are shown with the SHOW POWER BASELINE command. The following example illustrates the Consolidated Management Ports 1 through 10 (RDM1) and Power Distribution Module ports. 102 Setting power capping

103 > show power baseline Power Cap mode: FIXED All values listed are in AC watts APMPort DMPort Serial Number Min Cap Max Cap Set Cap Slots Populated CNK71600K (8) A power cap can be set between the minimum cap value of 585 and the maximum cap value of In this example, the cap applies only to the chassis located at APM Port 1, DM Port 2 because that is the only chassis that met the prerequisites for power capping. Under circumstances with many chassis, the allowable cap range would fall between the total minimum and total maximum values. Under normal circumstances, the average chassis power level might be up to 5% above the chassis power cap. However, the cap value might vary under extreme power usage situations. When running the baseline calibration, the target system (all nodes in chassis) must be running at the production level load. The following example shows mixed Power Management Controller (SL Chassis) Firmware version 4.3 and earlier: > show power MDM Port Node Avg Min Max n/a 206 (DC watts) n/a 203 (DC watts) n/a 208 (DC watts) n/a 206 (DC watts) n/a 207 (DC watts) n/a 210 (DC watts) n/a 225 (DC watts) n/a 225 (DC watts) 1 2 (no enclosure present) n/a 337 (DC watts) n/a 340 (DC watts) n/a 324 (DC watts) n/a 315 (DC watts) Power capping 103

104 n/a 351 (DC watts) n/a 344 (DC watts) n/a 325 (DC watts) n/a 346 (DC watts) 1 3 Fans 20 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) n/a 188 (DC watts) (empty) n/a 186 (DC watts) (empty) (empty) (empty) (empty) (empty) 1 4 Fans 14 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) 1 5 (no enclosure present) 1 6 (no enclosure present) 1 7 (no enclosure present) 1 8 (no enclosure present) 1 9 (no enclosure present) 1 10 (no enclosure present) 2 1 (no enclosure present) 2 2 (no enclosure present) 2 3 (no enclosure present) 2 4 (no enclosure present) 2 5 (no enclosure present) 2 6 (no enclosure present) 2 7 (no enclosure present) 2 8 (no enclosure present) 2 9 (no enclosure present) 2 10 (no enclosure present) 3 (no Dist. Module present) 4 (no Dist. Module present) 5 (no Dist. Module present) 6 (no Dist. Module present) 7 (no Dist. Module present) 8 (no Dist. Module present) Total servers = 18 Total chassis = 3 PDM Port Load (AC watts) (AC watts) (AC watts) (AC watts) (AC watts) 2 (no PDM Extension present) Power capping

105 The following example uses the power distribution module. > show power pdm PDM port 1 PDM Port Load (AC watts) (AC watts) (AC watts) (AC watts) (AC watts) PDM port 2 PDU: STI Serial TrueRMS PDU Part Number: QL192A Serial Number: ADFV Asset tag: SCI Lab PDU Firmware rev: 1.0a Infeed Amps: 60 Number of Infeeds: 4 Switched Outlets: 6 Infeeds: 01: Amps drawn: Status: On Load: Normal 02: Amps drawn: Status: On Load: Normal 03: Amps drawn: Status: On Load: Normal 04: Amps drawn: Status: N/A Load: Normal Switched ports: 01: Enabled 02: Enabled 03: Enabled 04: Enabled 05: Enabled 06: Enabled > show power 1 3 MDM Port Node Avg Min Max n/a 337 (DC watts) n/a 340 (DC watts) n/a 324 (DC watts) n/a 315 (DC watts) n/a 351 (DC watts) n/a 344 (DC watts) n/a 325 (DC watts) n/a 346 (DC watts) 1 3 Fans 20 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) Total servers = 8 Total chassis = 1 Total fan wattage = 20 (DC watts) Total system wattage = 2033 (DC watts) Total system wattage = 2148 (AC watts) > show power baseline All values listed are in AC watts APMPort DMPort Serial Number Min Cap Max Cap Set Cap Slots Populated Power capping 105

106 (8) (8) > show power MDM Port Node Avg Min Max (no enclosure present) 1 2 (no enclosure present) n/a 337 (DC watts) n/a 340 (DC watts) n/a 324 (DC watts) n/a 315 (DC watts) n/a 351 (DC watts) n/a 344 (DC watts) n/a 325 (DC watts) n/a 346 (DC watts) 1 3 Fans 21 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) n/a 188 (DC watts) (empty) n/a 186 (DC watts) (empty) (empty) (empty) (empty) (empty) 1 4 Fans 14 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) 1 5 (no enclosure present) 1 6 (no enclosure present) 1 7 (no enclosure present) 1 8 (no enclosure present) 1 9 (no enclosure present) 1 10 (no enclosure present) 2 1 (no enclosure present) 2 2 (no enclosure present) 2 3 (no enclosure present) 2 4 (no enclosure present) 2 5 (no enclosure present) 2 6 (no enclosure present) 2 7 (no enclosure present) 2 8 (no enclosure present) 2 9 (no enclosure present) 2 10 (no enclosure present) 3 (no Dist. Module present) 4 (no Dist. Module present) 5 (no Dist. Module present) 6 (no Dist. Module present) 7 (no Dist. Module present) 8 (no Dist. Module present) Total servers = Power capping

107 Total chassis = 2 Total fan wattage = 35 (DC watts) Total system wattage = 2265 (DC watts) Total system wattage = 2425 (AC watts) PDM Port Load (AC watts) (AC watts) (AC watts) (AC watts) (AC watts) 2 (no PDM Extension present) In the following example, the cap is set to 1500 AC watts. This information is saved as part of the baseline data to the onboard APM EEPROM. When multiple chassis are present and a valid rack-level cap is given, APM does the following: 1. Computes the total cap as a percentage against the sum of the eligible chassis maximum power values. 2. For each chassis, multiplies the percentage computed in step 1 against each chassis individual maximum power value. 3. Programs the result into the chassis. 4. Repeats steps 2-3 for each eligible chassis. To remove a power cap, use SET POWER CAP NONE. This action removes all power cap settings from all the servers. Creating APM power mappings Zones are collections of APM enclosures that can be given unique names that can be referred to for power capping purposes. Zones provide the APM user with the capability of distinguishing groups of enclosures as targets for power or management operations. When zones are defined, they are strictly a boundary definition that is kept within the APM for its purposes. Zones can be added or removed with the ADD ZONE and REMOVE ZONE commands. When the first ADD references a zone name that does not exist, the zone is automatically created and the indicated ports are populated into the newly created zone. Subsequent ADD ZONE commands that reference the same zone name cause the specified ports to be added to the existing zone. No limit exists for the number of ports other than the maximum APM supports in hardware that can be added to a zone. Multiple port listings can be used with a single ADD ZONE command, or multiple ADD ZONE commands can be used with each command adding new ports to the zone previously defined by the first ADD ZONE command. To remove zone references to ports, use the REMOVE ZONE command. When the last port is removed from a zone, the zone is automatically deleted. A zone cannot exist where no ports are assigned to it, and zone port definitions cannot overlap (that is, the same SL chassis cannot exist in more than one zone). Defining zones is an optional function, and is useful for applying power caps to some chassis while excluding others or applying different power caps to different groups or single SL chassis. Since APM zones are merely definitions of user defined APM group boundaries (and by extension any chassis that are plugged into those ports), they ignore the actual physical presence of enclosures as they are being defined in the APM CLI or GUI. Empty APM ports can be included in a zone. If an enclosure is plugged into that port later, it automatically is part of that zone. A reminder message will be printed if a zone is mapped to a APM port that currently has no SL enclosure plugged into it. Creating APM power mappings 107

108 After zone mappings have been completed with the ADD ZONE and REMOVE ZONE commands, the SHOW ZONES command can be used, for example: > show zones Zone RED: Power Manager port 1: Dist. Module port 1 Zone BLUE: Power Manager port 1: Dist. Module port 2 Dist. Module port 3 Zone GREEN: Power Manager port 2: all Dist. Module ports included Zone YELLOW: Power Manager port 3: Dist. Module port 1 > > show zones After a zone mapping has been completed, it can be saved to the APM onboard EEPROM with the SAVE ZONES command. This action makes the zone definitions persistent across APM resets. It automatically reloads on reboot. If SAVE ZONES is not used, the zone data is lost if the APM is reset. If a zone needs to be deleted, the REMOVE ZONE <zone name> ALL command can be used. This causes all ports to be removed from the zone definition, and the zone itself is deleted. As with all zone mapping modifications, to make it persistent across APM resets, enter SAVE ZONES. Power capping with zones If zones are defined as described the Zone Example 1 (assuming a power baseline is established for the rack), then SET POWER CAP can accept a zone name as a parameter after the wattage value. Otherwise, if you opt to remove power capping, then choose NONE. Zone Example: > show zones Zone BLUE: Power Manager port 1: Dist. Module port 2 Dist. Module port 3 Zone GREEN: Power Manager port 2: all Dist. Module ports included Zone YELLOW: Power Manager port 3: Dist. Module port 1 > show power baseline APMPort DMPort Serial Number Min Cap Max Cap Set Cap Slots Populated (8) 1 2 CNK71600K (8) > set power cap 2000 blue New cap represents 84 percent of the max cap of eligible entities. Apply cap (Y/N) -> 108 Power capping with zones

109 The Zone Example output sets a power cap only to those chassis that are in the zone defined as BLUE. If all caps must be removed from a zone, then SET POWER CAP NONE can be used. Set Power Example > set power cap none blue Remove power cap(s)? (Y/N) -> The Set Power command removes all power cap settings from the APM chassis resident on APM port 1 and distribution module ports 2 and 3, or zone blue. Since only a single chassis matches that description, the operation only affects that one chassis. If a cap is set using a zone, then the zone is removed, and the cap is unaffected. A new zone may be created that both: Includes some or all former zone ports, Sets caps against the new zone. Zones are strictly a defined set of SL enclosures that can be used to specify which machines are being considered for a cap. They are a vehicle for enabling multiple caps and/or exclusion areas to be created within a single APM domain of enclosures with respect to power capping. Power baselines and zones The power baseline cannot be created with respect to a zone. The baseline is a singular separate entity that is saved into the APM EEPROM. Zones can use portions of the established baseline when considering power caps, but the baseline is established globally. Power commands NOTE: You must also have an HPE ProLiant s6500 Chassis or later with BIOS support required. The power commands use the APM port number, the distribution module port number, and server node port number as input parameters. NOTE: APM operations classify the 10 Consolidated Management cable ports as RDM1. For more information, see "Identifying the RDM1 ports." In the following figure, the APM port 2 is connected to the APM Distribution Module port 4. The distribution module port is connected to the SL enclosure and server node 8. Power baselines and zones 109

110 Item Description 1 APM 2 APM Distribution Module 3 SL series enclosure 4 Bay 4 of a 4U chassis SL6500 Scalable System enclosure with eight 1U halfwidth nodes Displaying the rack power status Enter SHOW POWER, and then optionally the specific APM port, or both the APM and the APM Distribution Module ports. For example: SHOW POWER (to show all power) SHOW POWER 2 (to show the power for the APM port number) SHOW POWER 2 4 (to show the power for the APM port number and the APM Distribution Module port number This command also displays: Fan power per chassis in DC watts Chassis total in DC watts Chassis total in AC watts Chassis cap in AC watts (if one is set) The total of the averages is shown as well as the "average of averages" that was already there The average max power is shown as well as the total of the max column A total count of all the servers and chassis listed Total fan wattage for the listing Total system wattage in DC watts Total system wattage in AC watts 110 Displaying the rack power status

111 For example, the following text might appear on screen: MDM Port Node Avg Min Max (no Dist. Module present) 2 1 (no enclosure present) 2 2 (no enclosure present) 2 3 (no enclosure present) n/a 165 (DC watts) (empty) n/a 242 (DC watts) (empty) (empty) (empty) n/a 72 (DC watts) n/a 86 (DC watts) 2 4 Fans 35 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (empty) n/a 94 (DC watts) n/a 179 (DC watts) (empty) n/a 169 (DC watts) (empty) n/a 0 (DC watts) (empty) 2 5 Fans 235 (DC watts) (Chassis total - DC watts) (Chassis total - AC watts) (Chassis cap - AC watts) 2 6 (no enclosure present) 2 7 (no enclosure present) 2 8 (no enclosure present) 2 9 (no enclosure present) 2 10 (no enclosure present) 3 (no Dist. Module present) 4 (no Dist. Module present) 5 (no Dist. Module present) 6 (no Dist. Module present) 7 (no Dist. Module present) 8 (no Dist. Module present) Setting power Power management enables you to turn on and off single or multiple nodes within the rack. To turn a server node on or off, use the SET POWER command: SET POWER {ON OFF ENABLE DISABLE} {ALL <PORT#> <DMPORT#> {<NODE#> ALL}} where: ALL is used when the command applies to all nodes. You can also use ALL when the command applies to all the server nodes in a particular enclosure. <PORT#> refers to the APM, PDM1, or PDM2 port numbers. <DMPORT#> refers to the APM Distribution Module port number or the HPE Intelligent Modular PDU Extension Bar outlet number. Setting power 111

112 <NODE#> refers to the server node. For example, to power on server node 3, enter: SET POWER ON To power off server node 3, enter: SET POWER DISABLE When you power on a particular server enclosure, you must include either the node number or ALL in the command. To power on the server nodes in the enclosure, enter: SET POWER ON 2 4 ALL To power on all nodes connecting to the chassis on all APM Distribution Module ports, enter: SET POWER ON ALL SNMP traps denoted by an asterisk (*) are not supported on the HPE ProLiant s6500 Chassis. The SET POWER ON ALL and SET POWER OFF ALL commands are not supported on APM 1.54 on the HPE Moonshot 1500 Chassis. To power on the PDU ports, enter: SET POWER ON PDM To power off PDU ports, enter: SET POWER OFF PDM Polling servers for power values Polling reduces response times for power intensive server processes. For example, when APM retrieves power from a rack server, it is done at the time that the user requests the value. While real-time retrieval ensures the most accurate timely power consumption numbers and provides a great scaling capability, the retrieval process can become slow. This latency occurs when large numbers of detailed power values are needed quickly. Similar power requirements are made with the APM when the Power Usage Report page of the GUI is presented. To alleviate slow response times, when enabled, the Poll Power feature switches the value retrieving process on demand to polling the power values periodically. Afterwards, it retrieves them from a cache when requested by the user. In comparison to the previous method, this method reduces system response times. The Power Usage Report page of the GUI requires that you enable Poll Power for the best response and responsiveness. Poll Power can also be convenient when SNMP or other programmed queries from the APM demand the fastest possible response times. Poll Power can be enabled or disabled from the GUI configuration page or from the CLI using the ENABLE POLLPOWER and DISABLE POLLPOWER commands. To enable a background process that polls each server for its average, minimum, and maximum power values, enter ENABLE POLLPOWER. Polling these values increases the performance of SNMP queries of these power values. The poll cycle time varies depending on how many server chassis are plugged into the APM system. The more chassis that are present, the less frequently each server is polled. If POLLPOWER is enabled, then an SNMP request for any of these values on any resident server returns the last polled value. This process is done in place of requesting the real-time values from the server at the time the system makes the request. 112 Polling servers for power values

113 Disabling the polling of servers for power values To disable the background process that is polling each server for power usage, enter DISABLE POLLPOWER. The DISABLE POLLPOWER setting is the default. Disabling the polling of servers for power values 113

114 Using SNMP SNMP overview The architectural model for SNMP contains these components: At least one network management station with manager software. A network management station is a host running an application that manages the network. The network management applications request information from the agents, put the information into a database, and then translate messages into a readable format. Network Agents. Network agents are managed devices containing agent software. Agents might be hosts, gateway systems, or media devices such as bridges, hubs, or multiplexors. These agents perform the network management functions requested by the network management stations. Network management protocol. SNMP enables network management stations to monitor and control network devices. Stations and agents use SNMP to exchange management information. SNMP describes how agents and managers communicate and defines the types of information that can be exchanged. SNMP commands The following sections contain commands used to adjust SNMP configurations. Enabling SNMP Displaying SNMP parameters Setting the SNMP read-only community string Setting the SNMP write-only community string Setting the SNMP contact Setting the SNMP location Setting SNMP trap destinations Enabling SNMP To enable the SNMP protocol stack and agent in APM, enter ENABLE SNMP. To disable the SNMP protocol stack and agent, enter DISABLE SNMP. When you enter DISABLE SNMP, APM no longer responds to SNMP. This state is the default. Displaying SNMP parameters Enter SHOW SNMP. As an example, the following text might appear on screen: > show snmp SNMP agent is enabled SNMP Read-only community string is "public" SNMP Read-write community string is "private" SNMP traps are sent to SNMP system group values: SysDescription: HPE Apollo Platform Manager sysuptime: syscontact: sysname: alphabravo syslocation: Chicago If you have not set a particular group value, the space for that value is left blank. In this example, no contact information has been entered. 114 Using SNMP

115 Setting the SNMP read-only community string To set the SNMP read-only community string, enter SET SNMP RO "<community_string>". For example, enter: SET SNMP RO "alphabravo" Setting the SNMP read-write community string To set the SNMP read-write community string, enter SET SNMP RW "<community_string>". For example, enter: SET SNMP RW "alphabravo" Setting the SNMP contact To set the syscontact field, enter the SET SNMP CONTACT "<syscontact>" command. For example, enter: SET SNMP CONTACT "alphabravo" The string cannot exceed 80 characters. Setting the SNMP location To set the syslocation field, enter the SET SNMP LOCATION "<syslocation>" command. For example, enter: SET SNMP LOCATION "alphabravo" The string cannot exceed 80 characters. Setting SNMP trap destinations To set the IP address for SNMP traps, enter the SET SNMP TRAPDEST "[ <ip_addresses>[...] NONE> ]" command. For example, enter: SET SNMP TRAPDEST x.x.x.x You can set up to four SNMP traps at once. For example, enter: SET SNMP TRAPDEST x.x.x.x y.y.y.y z.z.z.z a.a.a.a If you specify NONE, then no traps are set. For example, enter: SET SNMP TRAPDEST NONE APM supports the following SNMP traps: cpqracknamechanged cpqrackenclosureremoved cpqrackenclosureinserted cpqrackenclosurefanremoved * cpqrackenclosurefaninserted * cpqrackenclosurefanfailed cpqrackenclosurefanok cpqrackpowersupplyfailed cpqrackpowersupplyok Setting the SNMP read-only community string 115

116 cpqrackpowersupplyremoved cpqrackpowersupplyinserted cpqrackserverbladeremoved cpqrackserverbladeinserted * Not supported on HPE ProLiant s6500 Chassis SNMP support of cpqhoswrunningtable The first element of this SNMP table lists the APM base firmware itself under cpqhoswrunningname and cpqhoswrunningdesc with cpqhoswrunningversion listing the correct version of the APM firmware. The following components are listed in the cpqhoswrunningtable: SNMP SSH syslogd Telnet The table entry cpqhoswrunningstate is set to either Running (2) or Stopped (3) to reflect whether that service is enabled or not. The SNMP service is listed as "Running" when accessed through this MIB item. All other items in this table are unsupported and will return their respective static return value for unknown. The rows appear in this order: APM base firmware Telnet SSH SNMP syslogd The following figure shows a sample table view of cpqhoswrunningtable. 116 SNMP support of cpqhoswrunningtable