Top Banner
HP iLO Federation User Guide Abstract This guide provides information about configuring and using the HP iLO Federation features in the HP iLO 4 firmware. This document is intended for system administrators, HP representatives, and HP Authorized Channel Partners who are involved in configuring and using HP iLO 4 and HP ProLiant Gen8 servers. For information about other HP iLO 4 features, see the HP iLO 4 User Guide at the following website: h t tp://w w w .hp .co m/go/ilo/doc s . HP Part Number: 767159-001 Published: February 2014 Edition: 1
45
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Ilo

HP iLO Federation User Guide

AbstractThis guide provides information about configuring and using the HP iLO Federation features in the HP iLO 4 firmware. Thisdocument is intended for system administrators, HP representatives, and HP Authorized Channel Partners who are involved inconfiguring and using HP iLO 4 and HP ProLiant Gen8 servers. For information about other HP iLO 4 features, see the HP iLO4 User Guide at the following website: http://www.hp.com/go/ilo/docs.

HP Part Number: 767159-001Published: February 2014Edition: 1

Page 2: Ilo

© Copyright 2014 Hewlett-Packard Development Company, L.P

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Page 3: Ilo

Contents1 About iLO Federation..................................................................................5

Using iLO Federation.................................................................................................................52 Configuring iLO Federation with the iLO web interface....................................7

Configuring iLO Federation........................................................................................................7iLO Federation network requirements......................................................................................7Configuring the multicast options...........................................................................................8Viewing iLO Federation group memberships............................................................................9Managing iLO Federation group membership..........................................................................9Removing an iLO system from an iLO Federation group...........................................................10

Configuring enclosure support for iLO Federation........................................................................10Using OA to configure Enclosure iLO Federation Support........................................................10Verifying server iLO Federation capability.............................................................................11

3 Configuring iLO Federation with RIBCL scripts...............................................13GET_FEDERATION_MULTICAST................................................................................................13

GET_FEDERATION_MULTICAST parameters..........................................................................13GET_FEDERATION_MULTICAST runtime errors.......................................................................13GET_FEDERATION_MULTICAST return messages....................................................................13

SET_FEDERATION_MULTICAST.................................................................................................13SET_FEDERATION_MULTICAST parameters...........................................................................14SET_FEDERATION_MULTICAST runtime errors........................................................................14

GET_FEDERATION_ALL_GROUPS.............................................................................................14GET_FEDERATION_ALL_GROUPS parameters........................................................................15GET_FEDERATION_ALL_GROUPS runtime errors....................................................................15GET_FEDERATION_ALL_GROUPS return messages.................................................................15

GET_FEDERATION_ALL_GROUPS_INFO...................................................................................15GET_FEDERATION_ALL_GROUPS_INFO parameters..............................................................15GET_FEDERATION_ALL_GROUPS_INFO runtime errors...........................................................15GET_FEDERATION_ALL_GROUPS_INFO return messages.......................................................16

GET_FEDERATION_GROUP.....................................................................................................16GET_FEDERATION_GROUP parameters................................................................................17GET_FEDERATION_GROUP runtime errors............................................................................17GET_FEDERATION_GROUP return messages.........................................................................17

ADD_FEDERATION_GROUP....................................................................................................17ADD_FEDERATION_GROUP parameters...............................................................................18ADD_FEDERATION_GROUP runtime errors...........................................................................18

MOD_FEDERATION_GROUP...................................................................................................18MOD_FEDERATION_GROUP parameters..............................................................................19MOD_FEDERATION_GROUP runtime errors..........................................................................19

DELETE_FEDERATION_GROUP.................................................................................................19DELETE_FEDERATION_GROUP parameters...........................................................................20DELETE_FEDERATION_GROUP runtime errors........................................................................20

4 Using the iLO Federation features...............................................................21Using the iLO Federation multi-system view.................................................................................21

Viewing server health and model information........................................................................21Viewing critical and degraded servers..................................................................................21

Viewing the iLO Federation Multi-System Map............................................................................22Using the iLO Federation Virtual Media feature...........................................................................23

Connecting scripted media for groups..................................................................................23Viewing and ejecting scripted media for groups.....................................................................24Viewing servers affected by a Group Virtual Media action......................................................25

Contents 3

Page 4: Ilo

Using the iLO Federation group power feature............................................................................25Changing the power state for multiple servers........................................................................25Viewing servers affected by the Virtual Power Button...............................................................27

Configuring iLO Federation group power settings........................................................................27Configuring Automatic Group Power Capping settings............................................................29

Using the iLO Federation firmware update feature.......................................................................29Updating firmware for multiple servers..................................................................................30Viewing servers affected by a Group Firmware Update...........................................................31

5 Using iLO Federation with other HP utilities..................................................33Using iLO Federation with HP SUM...........................................................................................33Using iLO Federation with HP Intelligent Provisioning...................................................................38

6 Troubleshooting........................................................................................39Query errors occur on iLO Federation pages..............................................................................39A timeout error is displayed on the Multi-System Map page..........................................................39A 502 error is displayed on the Multi-System Map page..............................................................40A 403 error is displayed on the Multi-System Map page..............................................................40iLO peers are not displayed.....................................................................................................40iLO peers are displayed with IPv6 addresses on IPv4 networks.....................................................40

7 Support and other resources......................................................................41Information to collect before you contact HP...............................................................................41How to contact HP..................................................................................................................41Registering for Software Technical Support and Update Service....................................................41

How to use Software Technical Support and Update Service....................................................41HP Support Center..................................................................................................................41HP authorized resellers............................................................................................................42Related information.................................................................................................................42

Glossary....................................................................................................43Index.........................................................................................................44

4 Contents

Page 5: Ilo

1 About iLO FederationUsing iLO Federation

iLO Federation enables you to manage multiple servers from one system running the iLO webinterface.iLO 4 firmware version 1.40 and later supports the following iLO Federation features:

• Group health status

• Group Virtual Media

• Group power control

• Automatic group power capping

• Group firmware updateFor iLO Federation configuration instructions, see “Configuring iLO Federation” (page 7).When using the iLO Federation features, note the following:

• You can use the iLO web interface or RIBCL scripts to configure iLO Federation. Use the iLOweb interface to configure one iLO at a time. Use RIBCL scripts to perform configurationprocedures on a batch of iLO systems.

◦ For information about configuring iLO Federation with the iLO web interface, see“Configuring iLO Federation with the iLO web interface” (page 7).

◦ For information about configuring iLO Federation with RIBCL scripts, see “ConfiguringiLO Federation with RIBCL scripts” (page 13).

• When you select a group from the Selected Group list on an iLO Federation page:

The servers that will be affected by a change on the Group Virtual Media, Group Power,and Group Firmware Update pages are listed in the Affected Systems table.

◦ The information displayed on iLO Federation pages applies to all of the servers in theselected group.

◦ The changes you make on iLO Federation pages apply to all of the servers in the selectedgroup.

◦ The group that is selected in the Selected Group list is saved in a cookie and remainspersistent, even when you log out of iLO.

• After you select a group, you can filter the servers in the list in order to view server informationor perform actions on a subset of the servers in the selected group.When you filter the list of servers:

◦ The information displayed on iLO Federation pages applies to all of the servers in theselected group that meet the filter criteria.

◦ The changes you make on iLO Federation pages apply to all of the servers in the selectedgroup that meet the filter criteria.

◦ The filter settings are saved in a cookie and remain persistent, even when you log out ofiLO.

You can use the following criteria to filter the servers in a group:

◦ Health status—Click a health status link to select servers with a specific health status.

◦ Model—Click a server model number link to select servers matching the selected model.

Using iLO Federation 5

Page 6: Ilo

◦ Server name—Click a server name to filter by an individual server.

◦ Firmware information—Click a firmware version or flash status to select servers matchingthe selected firmware version or status.

◦ Option ROM Measuring—Click an Option ROM Measuring value to select servers basedon their TPM status.If you have one or more servers with a TPM, use this filter to exclude servers with OptionROM Measuring enabled. If you attempt a system ROM or option ROM update on aserver with Option ROM Measuring enabled, iLO prompts you to cancel the update,verify that you have a recovery key, and suspend BitLocker before the update. Failure tofollow these instructions might result in lost access to your data.

• Any user can view information on iLO Federation pages, but a license is required to makechanges. For more information about iLO licensing, see the following website: http://www.hp.com/go/ilo/licensing.

Other HP utilities take advantage of the iLO Federation features:

• HP Smart Update Manager (HP SUM) 6.3.0 includes a Technology Preview of the integratediLO Federation features. The Technology Preview provides view-only access to the followingfeatures:

◦ Discover and view information about servers in an iLO Federation group. For each serverin a group, you can view the installed versions of the following firmware types:– iLO

– BIOS

– Power Pic

– CPLD

◦ View the Deploy page for an iLO Federation group. The Deploy feature is not enabledin this Technology Preview.

For information about viewing the iLO Federation features in HP SUM, see “Using iLOFederation with HP SUM” (page 33).

• HP Intelligent Provisioning 1.60 includes a Technology Preview of the integrated iLO Federationfeature. The Technology Preview provides view-only access to the following feature:

◦ Store server profiles on the network. If you store a server profile on a server that is in aniLO Federation group, the other servers in that group can access and use the server profile.

For information about viewing the iLO Federation feature in Intelligent Provisioning, see “UsingiLO Federation with HP Intelligent Provisioning” (page 38).

6 About iLO Federation

Page 7: Ilo

2 Configuring iLO Federation with the iLO web interfaceConfiguring iLO Federation

iLO uses multicast discovery, peer-to-peer communication, and iLO Federation groups tocommunicate with other iLO systems.

• Each multicast announcement is approximately 300 bytes, and you can configure the timebetween announcements on the Group Configuration page.

• iLO Federation groups allow iLO to encrypt and sign messages to other iLOs in the samegroup.

• iLO Federation groups can overlap, span racks and data centers, and group servers of thesame type.

• An iLO system can be in up to 10 iLO Federation groups.

• iLO systems in multiple locations can be managed together if the network is configured toforward multicast traffic.

• If you want to use server blades in an enclosure with iLO Federation, you must configureEnclosure iLO Federation Support in the Onboard Administrator web interface. This feature issupported in OA 4.11 or later. For more information, see “Configuring enclosure support foriLO Federation” (page 10).

When data is loaded on an iLO Federation page in the iLO web interface, a request for data issent from the iLO system running the web interface to the iLO’s peers, and from those peers toother peers, and so on until all of the data for the selected iLO Federation group is retrieved.Use the iLO web interface on each iLO system to configure group memberships and multicastoptions. The settings on the Group Configuration page apply to the local iLO system only. Youmust configure these settings on each iLO system that will use the iLO Federation features.

TIP: You can use RIBCL XML scripts to view and configure group memberships and multicastoptions for a batch of iLO systems. For more information, see“Configuring iLO Federation withRIBCL scripts” (page 13).

When you configure group memberships, you must specify the privileges that members of a grouphave over the local managed server. For example, if you add the local iLO system to group1, andassign the Virtual Power and Reset privilege, the users of other iLO systems in group1 can use theGroup Power features to change the power state of the managed server. If the local iLO systemdoes not grant the Virtual Power and Reset privilege to a group, then the users of other iLOs in thegroup cannot use the Group Power features to change the power state of the managed server. Ifthe iLO Security Override Switch is set on the managed server, the users of other iLOs in group1can use any iLO Federation feature to change the state of the server, regardless of the assignedgroup privileges.All iLO systems are automatically added to the DEFAULT group, which is granted the Login privilegefor each group member. You can edit or delete the DEFAULT group membership.For information about using iLO Federation, see “Using iLO Federation” (page 5).

iLO Federation network requirementsWhen you use iLO Federation, note the following network requirements:

• The iLO Federation features are not supported with the iLO Shared Network Port configuration.

• iLO Federation supports both IPv4 and IPv6.

Configuring iLO Federation 7

Page 8: Ilo

• If the switches in your network include the option to enable or disable multicast traffic, ensurethat multicast traffic is enabled. This is required for iLO Federation and other HP products todiscover the iLOs on the network.

• For iLOs that are separated by Layer 3 switches, configure the switches to forward SSDPmulticast traffic between networks.

• UDP port 1900 must be configured as a firewall exception to allow iLO Federation multicasttraffic.

Configuring the multicast optionsYou must configure the multicast options for each iLO system that will be added to an iLO Federationgroup.Use the following procedure to configure multicast options for one iLO system at a time. To useRIBCL scripts to view and configure multicast options on a batch of iLO systems, see“SET_FEDERATION_MULTICAST” (page 13) and “GET_FEDERATION_MULTICAST” (page 13).1. Navigate to the iLO Federation→Group Configuration page, as shown in Figure 1 (page 8).

Figure 1 Group Configuration page

2. Configure the following options in the Multicast Options section:• iLO Federation Management—Select Enabled or Disabled.

The default setting is Enabled. Selecting Disabled will disable the iLO Federation featuresfor the local iLO system.

• Multicast Discovery—Select Enabled or Disabled.Selecting Disabled will disable the iLO Federation features for the local iLO system.

• Multicast Announcement Interval (seconds/minutes)—Sets the frequency at which iLOannounces itself on the network. Select a value of 30 seconds to 30 minutes. The defaultvalue is 10 minutes.Network changes and changes you make on this page will take effect after the nextmulticast announcement.

8 Configuring iLO Federation with the iLO web interface

Page 9: Ilo

Selecting Disabled will disable the iLO Federation features for the local iLO system.

• IPv6 Multicast Scope—Select the multicast discovery scope. The following values aresupported: Link, Site, and Organization.

IMPORTANT: Do not select the Global value. This value is not supported.

• Multicast Time To Live (TTL)—Specifies the number of switches that can be traversed beforemulticast discovery is stopped. The default value is 5.

3. Click Apply to save the settings.

IMPORTANT: To ensure that multicast discovery works correctly, make sure that all iLO systemsin the same group use the same values for Multicast Time to Live (TTL) and IPv6 Multicast Scope.

Viewing iLO Federation group membershipsUse the iLO web interface to view the group memberships of one iLO system.You can also use RIBCL scripts to view information about groups. For more information, see“GET_FEDERATION_GROUP” (page 16), “GET_FEDERATION_ALL_GROUPS” (page 14), and“GET_FEDERATION_ALL_GROUPS_INFO” (page 15).To view the group memberships of a local iLO system, navigate to the iLO Federation→GroupConfiguration page, as shown in Figure 1 (page 8).The Group Membership for this iLO table lists the name of each group that includes the local iLOsystem and the privileges granted to the group by the local iLO system. Table 1 (page 9) lists theavailable privileges.

Table 1 Group privileges

Login—Enables members of a group to log in to iLO.

Remote Console Access—Enables members of a group to remotely access the host system RemoteConsole, including video, keyboard, and mouse control.

Virtual Media—Enables members of a group to use scripted Virtual Media with the local iLO system.

Virtual Power and Reset—Enables members of a group to power-cycle or reset the local iLO system.

Configure iLO Settings—Enables members of a group to configure most iLO settings, includingsecurity settings, and to remotely update firmware.

Administer User Accounts—Enables members of a group to add, edit, and delete iLO user accounts.

Managing iLO Federation group membershipAn iLO system can be a member of up to 10 groups, and there is no limit to the number of iLOsthat can be in a group.Use the following procedure to configure iLO Federation group membership for one iLO system.To use RIBCL scripts to configure group memberships for a batch of iLO systems, see“ADD_FEDERATION_GROUP” (page 17) and “MOD_FEDERATION_GROUP” (page 18).1. Navigate to the iLO Federation→Group Configuration page, as shown in Figure 1 (page 8).

Configuring iLO Federation 9

Page 10: Ilo

2. Do one of the following:• Click New to create a new group membership.

• Select a group membership, and then click Edit.3. Enter the following information:

• Group Name—The group name.

• Group Key—The group password. The password can be up to 39 characters.

• Group Key Confirm—Confirm the group password.4. Select from the following permissions when you are adding or editing a group membership.

The permissions granted to the group by the local iLO system control the tasks users of otheriLOs in the group can perform on the managed server.

• Administer User Accounts

• Remote Console Access

• Virtual Power and Reset

• Virtual Media

• Configure iLO Settings

• Login PrivilegeFor a description of these permissions, see Table 1 (page 9).

5. Click Add Group or Update Group to save the settings.

Removing an iLO system from an iLO Federation groupUse the following procedure to remove an iLO system from an iLO Federation group. To use RIBCLscripts to remove group memberships, see “DELETE_FEDERATION_GROUP” (page 19).1. Navigate to the iLO Federation→Group Configuration page, as shown in Figure 1 (page 8).2. Select the check box next to the group membership that you want to delete.3. Click Delete.

The following message appears:Are you sure you want to delete the selected group(s)?

4. Click OK.

Configuring enclosure support for iLO FederationIf you want to use server blades in an enclosure with iLO Federation, the Enclosure iLO FederationSupport setting must be enabled in the Onboard Administrator software. This setting is requiredto allow peer-to-peer communication between the server blades in an enclosure. Enclosure iLOFederation Support is enabled by default. Onboard Administrator 4.11 or later is required to usethis feature.

Using OA to configure Enclosure iLO Federation SupportUse the following procedure to configure an enclosure for iLO Federation Support.1. Log in to the OA web interface (https://<OA hostname or IP address>).2. Navigate to the Enclosure Information→Network Access page, and then click the Protocols

tab, as shown in Figure 2 (page 11).

10 Configuring iLO Federation with the iLO web interface

Page 11: Ilo

Figure 2 OA Enclosure Settings page

3. Select the Enable Enclosure iLO Federation Support check box, and then click Apply.

TIP: You can also use the CLI to enable or disable Enclosure iLO Federation Support. To enablethe setting, enter ENABLE ENCLOSURE_ILO_FEDERATION_SUPPORT. To disable the setting,enter DISABLE ENCLOSURE_ILO_FEDERATION_SUPPORT. For more information about usingthe OA CLI, see the HP BladeSystem Onboard Administrator Command Line Interface User Guideat the following website: http://www.hp.com/go/oa.

Verifying server iLO Federation capabilityUse the following procedure to verify that a blade server is configured for iLO Federation support.1. Log in to the OA web interface (https://<OA hostname or IP address>).2. Navigate to the Device Bays→<Device Name>→iLO page, as shown in Figure 3 (page 12).

Configuring enclosure support for iLO Federation 11

Page 12: Ilo

Figure 3 iLO Federation Capable setting

3. Verify that the iLO Federation Capable setting shows the value Yes.

12 Configuring iLO Federation with the iLO web interface

Page 13: Ilo

3 Configuring iLO Federation with RIBCL scriptsYou can view and configure iLO Federation settings by using RIBCL scripts. For detailed informationabout using iLO scripts, see the HP iLO 4 Scripting and Command Line GuideFor information about using the HPQLOCFG utility to send RIBCL scripts to a batch of servers, seethe HP iLO 4 Scripting and Command Line Guide. To use another tool to send scripts to a batchof servers, see the tool documentation.This chapter describes the available iLO Federation scripts.You can download sample scripts from the following website: http://www.hp.com/support/ilo4.

GET_FEDERATION_MULTICASTUse the GET_FEDERATION_MULTICAST command to retrieve the current federation multicastoptions. The response includes values for Multicast Discovery, Multicast Announcement Interval,IPv6 Multicast Scope, and Multicast TTL. The command must appear within a RIB_INFO commandblock, and RIB_INFO MODE must be set to read.For example:<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_FEDERATION_MULTICAST/> </RIB_INFO> </LOGIN></RIBCL>

GET_FEDERATION_MULTICAST parametersNone

GET_FEDERATION_MULTICAST runtime errorsNone

GET_FEDERATION_MULTICAST return messagesThe following response is typical of the data returned from the GET_FEDERATION_MULTICASTcommand:<?xml version="1.0"?><RIBCL VERSION="2.23"><RESPONSE STATUS="0x0000" MESSAGE='No error' /><GET_FEDERATION_MULTICAST> <MULTICAST_DISCOVERY_ENABLED VALUE="Yes"/> <MULTICAST_ANNOUNCEMENT_INTERVAL VALUE="60"/> <IPV6_MULTICAST_SCOPE VALUE="Site"/> <MULTICAST_TTL VALUE="255"/></GET_FEDERATION_MULTICAST></RIBCL>

SET_FEDERATION_MULTICASTEnter the SET_FEDERATION_MULTICAST to set federation multicast options, including MulticastDiscovery, Multicast Announcement Interval, IPv6 Multicast Scope, and Multicast TTL.

GET_FEDERATION_MULTICAST 13

Page 14: Ilo

NOTE: Disabling multicast discovery or announcements disables iLO federation features.All devices in a federated group must have the same scope and TTL to properly enable peerdiscovery.

For example:<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <SET_FEDERATION_MULTICAST> <MULTICAST_DISCOVERY_ENABLED VALUE="Yes"/> <MULTICAST_ANNOUNCEMENT_INTERVAL VALUE="30"/> <IPV6_MULTICAST_SCOPE VALUE="Site"/> <MULTICAST_TTL VALUE="255"/> </SET_FEDERATION_MULTICAST> </RIB_INFO> </LOGIN></RIBCL>

SET_FEDERATION_MULTICAST parametersMULTICAST_DISCOVERY_ENABLED enables or disables multicast discovery. Value must be eitherYes (enabled) or No (disabled). When enabled, this parameter makes the iLO discoverable asfederated on the network. When disabled, iLO Federation features are unavailable.MULTICAST_ANNOUNCEMENT_INTERVAL sets the number of seconds between each multicastavailability announcement on the network. Valid values are Disabled, 30, 60, 120, 300, 600,900, and 1800 seconds. When disabled, iLO Federation features are unavailable.IPV6_MULTICAST_SCOPE sets the scope of multicast discovery. Valid values are Link (link-local),Site (site-local), and Organization (organization-local). All devices in a federated group musthave the same scope to properly enable peer discovery.MULTICAST_TTL sets the time to live, limiting the number of switches that can be traversed beforethe multicast discovery is stopped. Any value between 1 and 255 can be used. All devices in afederated group must have the same TTL to properly enable peer discovery.

SET_FEDERATION_MULTICAST runtime errorsSome possible SET_FEDERATION_MULTICAST error messages include:• The MULTICAST_ANNOUNCEMENT_INTERVAL VALUE is invalid.

• The IPV6_MULTICAST_SCOPE VALUE is invalid.

• The MULTICAST_TTL VALUE is invalid. Valid values are between 1 and255.

• User does not have correct privilege for action. CONFIG_ILO_PRIVrequired.

GET_FEDERATION_ALL_GROUPSUse the GET_FEDERATION_ALL_GROUPS command to retrieve a list of all iLO 4 Federation groupnames. The command must appear within a RIB_INFO command block, and RIB_INFO MODEmust be set to read.For example:

<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_FEDERATION_ALL_GROUPS/> </RIB_INFO>

14 Configuring iLO Federation with RIBCL scripts

Page 15: Ilo

</LOGIN></RIBCL>

GET_FEDERATION_ALL_GROUPS parametersNone

GET_FEDERATION_ALL_GROUPS runtime errorsNone

GET_FEDERATION_ALL_GROUPS return messagesThe following response is typical of the data returned from the GET_FEDERATION_ALL_GROUPScommand:<?xml version="1.0"?><RIBCL VERSION="2.23"><RESPONSE STATUS="0x0000" MESSAGE='No error' /><GET_FEDERATION_ALL_GROUPS> <GROUP_NAME VALUE="Group1"/> <GROUP_NAME VALUE="Group2"/></GET_FEDERATION_ALL_GROUPS></RIBCL>

GET_FEDERATION_ALL_GROUPS_INFOUse GET_FEDERATION_ALL_GROUPS_INFO to retrieve a list of all Federation group names andthe associated privileges for each group. To retrieve the privileges of a single specified group, useGET_FEDERATION_GROUP.Besides the group name, the returned group privileges include:• User account administration

• Remote console access

• Virtual power and reset

• Virtual media

• iLO setting configuration

• Login privilegeThe command must appear within a RIB_INFO command block, and RIB_INFO MODE must beset to read.For example:

<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_FEDERATION_ALL_GROUPS_INFO/> </RIB_INFO> </LOGIN></RIBCL>

GET_FEDERATION_ALL_GROUPS_INFO parametersNone.

GET_FEDERATION_ALL_GROUPS_INFO runtime errorsNone

GET_FEDERATION_ALL_GROUPS_INFO 15

Page 16: Ilo

GET_FEDERATION_ALL_GROUPS_INFO return messagesThe following response is typical of the data returned from theGET_FEDERATION_ALL_GROUPS_INFO command:<?xml version="1.0"?><RIBCL VERSION="2.23"><RESPONSE STATUS="0x0000" MESSAGE='No error' /><GET_FEDERATION_ALL_GROUPS_INFO> <FEDERATION_GROUP> <GROUP_NAME VALUE="Group1"/> <ADMIN_PRIV VALUE="Yes"/> <REMOTE_CONS_PRIV VALUE="Yes"/> <RESET_SERVER_PRIV VALUE="Yes"/> <VIRTUAL_MEDIA_PRIV VALUE="Yes"/> <CONFIG_ILO_PRIV VALUE="Yes"/> <LOGIN_PRIV VALUE="Yes"/> </FEDERATION_GROUP> <FEDERATION_GROUP> <GROUP_NAME VALUE="Group2"/> <ADMIN_PRIV VALUE="Yes"/> <REMOTE_CONS_PRIV VALUE="Yes"/> <RESET_SERVER_PRIV VALUE="No"/> <VIRTUAL_MEDIA_PRIV VALUE="No"/> <CONFIG_ILO_PRIV VALUE="Yes"/> <LOGIN_PRIV VALUE="Yes"/> </FEDERATION_GROUP></GET_FEDERATION_ALL_GROUPS_INFO></RIBCL>

GET_FEDERATION_GROUPUse GET_FEDERATION_GROUP to retrieve the privileges granted to a specified Federated group.To retrieve the privileges granted to all groups, use GET_FEDERATION_ALL_GROUPS_INFO.Besides the group name, the return includes the following group privileges:• User account administration

• Remote console access

• Virtual power and reset

• Virtual media

• iLO setting configuration

• Login privilegeThe command must appear within a RIB_INFO command block, and RIB_INFO MODE must beset to read.For example:

<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_FEDERATION_GROUP GROUP_NAME="groupname"/> </RIB_INFO> </LOGIN></RIBCL>

16 Configuring iLO Federation with RIBCL scripts

Page 17: Ilo

GET_FEDERATION_GROUP parametersGROUP_NAME—The name of the group to be displayed. The name must be from 1 to 31 characterslong.

GET_FEDERATION_GROUP runtime errorsGET_FEDERATION_GROUP returns the following message if the value specified for GROUP_NAMEdoes not match any existing groups:Group name not found.

GET_FEDERATION_GROUP return messagesThe following response is typical of the data returned from the GET_FEDERATION_GROUPcommand:<?xml version="1.0"?><RIBCL VERSION="2.23"><RESPONSE STATUS="0x0000" MESSAGE='No error' /><GET_FEDERATION_GROUP> <FEDERATION_GROUP> <GROUP_NAME VALUE="Group2"/> <ADMIN_PRIV VALUE="Yes"/> <REMOTE_CONS_PRIV VALUE="Yes"/> <RESET_SERVER_PRIV VALUE="No"/> <VIRTUAL_MEDIA_PRIV VALUE="No"/> <CONFIG_ILO_PRIV VALUE="Yes"/> <LOGIN_PRIV VALUE="Yes"/> </FEDERATION_GROUP></GET_FEDERATION_GROUP></RIBCL>

ADD_FEDERATION_GROUPUse ADD_FEDERATION_GROUP to add a new Federation group membership and associatedprivileges. The command must appear within a RIB_INFO command block, and RIB_INFO MODEmust be set to write.For example:<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <ADD_FEDERATION_GROUP GROUP_NAME="groupname" GROUP_KEY="groupkey"> <ADMIN_PRIV VALUE="Yes"/> <REMOTE_CONS_PRIV VALUE="Yes"/> <RESET_SERVER_PRIV VALUE="Yes"/> <VIRTUAL_MEDIA_PRIV VALUE="Yes"/> <CONFIG_ILO_PRIV VALUE="Yes"/> <LOGIN_PRIV VALUE="Yes"/> </ADD_FEDERATION_GROUP> </RIB_INFO> </LOGIN></RIBCL>

NOTE: HP iLO 4 supports a maximum of 10 Federation groups. To remove a Federation group,use DELETE_FEDERATION_GROUP.

ADD_FEDERATION_GROUP 17

Page 18: Ilo

ADD_FEDERATION_GROUP parametersGROUP_NAME—The name of the group to be added. The name must be from 1 to 31 characterslong.GROUP_KEY—The password to set for the group to be added. The password must be 1 to 31characters long.ADMIN_PRIV—Administer User Accounts—Enables members of a group to add, edit, and deleteiLO user accounts.REMOTE_CONS_PRIV—Remote Console Access—Enables members of a group to remotely accessthe host system Remote Console, including video, keyboard, and mouse control.RESET_SERVER_PRIV—Virtual Power and Reset—Enables members of a group to power-cycle orreset the local iLO system.VIRTUAL_MEDIA_PRIV—Virtual Media—Enables members of a group to use scripted Virtual Mediawith the local iLO system.CONFIG_ILO_PRIV—Configure iLO Settings—Enables members of a group to configure most iLOsettings, including security settings, and to remotely update firmware.LOGIN_PRIV—Login—Enables members of a group to log in to iLO.

ADD_FEDERATION_GROUP runtime errors• The GROUP_NAME must not be left blank.

• The GROUP_NAME is too long.

• The GROUP_KEY must not be left blank.

• The GROUP_KEY is too long.

• Group membership already exists.

• Cannot add group membership. Maximum number of memberships reached:10.

MOD_FEDERATION_GROUPUse MOD_FEDERATION_GROUP to modify an existing Federation group membership andassociated privileges. The command must appear within a RIB_INFO command block, and RIB_INFOMODE must be set to write.

NOTE: All parameters are optional. Any Federation property not explicitly modified retains itsold value.

For example:<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <MOD_FEDERATION_GROUP GROUP_NAME="groupname"> <GROUP_NAME VALUE="newgroupname"/> <GROUP_KEY VALUE="newgroupkey"/> <ADMIN_PRIV VALUE="Yes"/> <REMOTE_CONS_PRIV VALUE="Yes"/> <RESET_SERVER_PRIV VALUE="Yes"/> <VIRTUAL_MEDIA_PRIV VALUE="Yes"/> <CONFIG_ILO_PRIV VALUE="Yes"/> <LOGIN_PRIV VALUE="Yes"/> </MOD_FEDERATION_GROUP> </RIB_INFO> </LOGIN></RIBCL>

18 Configuring iLO Federation with RIBCL scripts

Page 19: Ilo

MOD_FEDERATION_GROUP parametersGROUP_NAME—The name of the group to be changed, or the new name to be given to thespecified Federation group, depending on the parameters’ location. The name must be from 1 to31 characters long.GROUP_KEY—The new password to set for the group. The password must be 1 to 31 characterslong.ADMIN_PRIV—Administer User Accounts—Enables members of a group to add, edit, and deleteiLO user accounts.REMOTE_CONS_PRIV—Remote Console Access—Enables members of a group to remotely accessthe host system Remote Console, including video, keyboard, and mouse control.RESET_SERVER_PRIV—Virtual Power and Reset—Enables members of a group to power-cycle orreset the local iLO system.VIRTUAL_MEDIA_PRIV—Virtual Media—Enables members of a group to use scripted Virtual Mediawith the local iLO system.CONFIG_ILO_PRIV—Configure iLO Settings—Enables members of a group to configure most iLOsettings, including security settings, and to remotely update firmware.LOGIN_PRIV—Login—Enables members of a group to log in to iLO.

MOD_FEDERATION_GROUP runtime errorsSome possible MOD_FEDERATION_GROUP error messages include:• The GROUP_NAME must not be left blank.

NOTE: This error only appears if the value in the <MOD_FEDERATION_GROUPGROUP_NAME="groupname"> command is left blank. This error does not appear ifnewgroupname in the parameter setting <GROUP_NAME VALUE="newgroupname"/> isleft blank or the line is omitted. In that case, the original group name is retained.

• Group name not found.

• The GROUP_NAME is too long.

• The GROUP_KEY must not be left blank.

• The GROUP_KEY is too long.

• Group membership already exists.

• User does not have correct privilege for action. CONFIG_ILO_PRIVrequired.

DELETE_FEDERATION_GROUPUse DELETE_FEDERATION_GROUP to remove the iLO from a Federation group membership. Thecommand must appear within a RIB_INFO command block, and RIB_INFO MODE must be set towrite.For example:<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <DELETE_FEDERATION_GROUP GROUP_NAME="groupname"/> </RIB_INFO> </LOGIN></RIBCL>

DELETE_FEDERATION_GROUP 19

Page 20: Ilo

DELETE_FEDERATION_GROUP parametersGROUP_NAME—The name of the Federation group to be deleted. The name must be from 1 to31 characters long and must already exist as a membership group.

DELETE_FEDERATION_GROUP runtime errorsPossible runtime errors returned by DELETE_FEDERATION_GROUP include:• If the value specified for GROUP_NAME does not match any existing groups: Group name

not found.

• User does not have correct privilege for action. CONFIG_ILO_PRIVrequired.

20 Configuring iLO Federation with RIBCL scripts

Page 21: Ilo

4 Using the iLO Federation featuresUsing the iLO Federation multi-system view

The Multi-System View page provides a summary of the server models, server health, and criticaland degraded systems in an iLO Federation group.

Viewing server health and model informationTo view summary information for a group of servers:1. Navigate to the iLO Federation→Multi-System View page, as shown in Figure 4 (page 21).

Figure 4 Multi-System View page

2. Select a group from the Selected Group menu.3. Optional: To filter the list of servers, click a health status, server model, or server name link.

The following information is displayed for the servers in the selected group that meet the filtercriteria (if filters are used).

• Health—The number of servers in each listed health status. The percentage of the totalnumber of servers that is in the listed health status is also displayed.For a list of the possible health status values, see the HP iLO 4 User Guide.

• Model—The list of servers, grouped by the server model number. The percentage of thetotal number of servers for each model number is also displayed.

• Critical and Degraded Systems—The list of servers with a status of Critical or Degraded.For more information, see “Viewing critical and degraded servers” (page 21).

Viewing critical and degraded serversTo view details about the servers in a group that are in the critical or degraded state:1. Navigate to the iLO Federation→Multi-System View page, as shown in Figure 4 (page 21).2. Select a group from the Selected Group menu.

Using the iLO Federation multi-system view 21

Page 22: Ilo

3. Optional: To filter the list of servers, click a health status, server model, or server name link.The following information is displayed for the critical and degraded servers in the selectedgroup that meet the filter criteria (if filters are used).

• Server Name—The server name defined by the host operating system.

• System Health—The server health status.

• Server Power—The server power status.

• UID Indicator—The server UID status.

• System ROM—The installed HP ProLiant System ROM.

• iLO Hostname—The fully qualified network name assigned to the iLO subsystem. Clickthe iLO link to open the iLO web interface for the server.

• IP Address—The network IP address of the iLO subsystem. Click the iLO link to open theiLO web interface for the server.

4. Click Next or Previous to view more servers in the list.

Viewing the iLO Federation Multi-System MapThe Multi-System Map page displays information about the iLO systems in a selected group.The Summary section lists the number of other iLO systems in the group, and the iLO Peers tablelists the iLO systems that the local iLO has identified as its closest neighbors or peers. The localiLO identifies its peers via multicast discovery.For more information about multicast discovery, see “Configuring iLO Federation” (page 7).To view the Multi-System Map:1. Navigate to the iLO Federation→Multi-System Map page, as shown in Figure 5 (page 22).

Figure 5 Multi-System Map page

22 Using the iLO Federation features

Page 23: Ilo

2. Select a group from the Selected Group menu.The following information is displayed for each iLO peer:

• #—The peer number.

• UUID—The server UUID.

• Last Seen—The time stamp of the last communication from the server.

• Last Error—A description of the most recent communication error between the listed serverand the group.

• URL—The URL to start the iLO web interface for the listed iLO.

• IP—The iLO IP address.

For information about errors that might occur on this page, see “A 403 error is displayed on theMulti-System Map page” (page 40), “A timeout error is displayed on the Multi-System Map page”(page 39), and “A 502 error is displayed on the Multi-System Map page” (page 40).

Using the iLO Federation Virtual Media featureThe Group Virtual Media feature enables you to connect scripted media that can be accessed bythe servers in an iLO Federation group.A license is required if you want to make changes on the Group Virtual Media page. For moreinformation about iLO licensing, see the following website: http://www.hp.com/go/ilo/licensing.When you use Group Virtual Media, note the following:

• You can connect scripted media to the iLO systems in an iLO Federation group. Scripted mediasupports only 1.44 MB floppy images (.img) and CD/DVD-ROM images (.iso). The imagemust be located on a web server on the same network as iLO.

• If you want to use the iLO Federation Virtual Media feature with an iLO Federation group,ensure that each member of the group has granted the Virtual Media privilege to the group.For more information about privileges, see “Configuring iLO Federation” (page 7).

• Only one of each type of media can be connected to a group at the same time.

• You can view, connect, eject, or boot from scripted media. Scripted media refers to connectingimages hosted on a web server by using a URL. iLO will accept URLs in HTTP or HTTPS format.FTP is not supported.

• Before you use the iLO Virtual Media feature, review the operating system considerations inthe HP iLO 4 User Guide.

Connecting scripted media for groupsTo connect scripted media:

Using the iLO Federation Virtual Media feature 23

Page 24: Ilo

1. Navigate to the iLO Federation→Group Virtual Media page, as shown in Figure 6 (page 24).

Figure 6 Group Virtual Media page

2. Select a group from the Selected Group menu.All of the systems in the selected group will be affected by the changes you make on this page.

3. Enter the URL for the scripted media in the Scripted Media URL box in the Connect VirtualFloppy section (.img files) or the Connect CD/DVD-ROM section (.iso files).

4. Select the Boot on Next Reset check box if the servers in the group should boot to this imageonly on the next server reboot.The image will be ejected automatically on the second server reboot so that the servers donot boot to this image twice.If this check box is not selected, the image will remain connected until it is manually ejected,and the servers will boot to it on all subsequent server resets, if the system boot options areconfigured accordingly.

5. Click Insert Media.

Viewing and ejecting scripted media for groupsWhen scripted media is connected to the systems in an iLO Federation group, the following detailsare listed in the Virtual Floppy Status section and Virtual CD/DVD-ROM Status section:

• Image Inserted—The Virtual Media type that is connected. Scripted media is displayed whenscripted media is connected.

• Connected—Indicates whether a Virtual Media device is connected.

• Image URL—The URL that points to the connected scripted media.To eject scripted media devices:1. Navigate to the iLO Federation→Group Virtual Media page.2. Select a group from the Selected Group menu.

All of the systems in the selected group will be affected by the changes you make on this page.3. Click the Eject Media button in the Virtual Floppy Status section or Virtual CD/DVD-ROM Status

section.

24 Using the iLO Federation features

Page 25: Ilo

Viewing servers affected by a Group Virtual Media actionThis section provides the following details about the servers that will be affected by changes youmake on the Group Virtual Media page.

• Server Name—The server name defined by the host operating system.

• Server Power—The server power state (ON or OFF).

• UID Indicator—The state of the UID. The UID helps you identify and locate a system, especiallyin high-density rack environments. The possible states are UID ON, UID OFF, and UID BLINK.

• iLO Hostname—The fully qualified network name assigned to the iLO subsystem. Click the iLOlink to open the iLO web interface for the server.

• IP Address—The network IP address of the iLO subsystem. Click the iLO link to open the iLOweb interface for the server.

Using the iLO Federation group power featureThe Group Power feature enables you to manage the power of multiple servers from a systemrunning the iLO web interface. This feature allows you to do the following:

• Power off, reset, or power cycle a group of servers that are in the ON or Reset state. For moreinformation, see “Changing the power state for multiple servers” (page 25).

• Power on a group of servers that are OFF. For more information, see “Changing the powerstate for multiple servers” (page 25).

• View the list of servers that will be affected by a Virtual Power Button push. For moreinformation, see “Viewing servers affected by the Virtual Power Button” (page 27).

A license is required if you want to make changes on the Group Power page. For more informationabout iLO licensing, see the following website: http://www.hp.com/go/ilo/licensing.If you want to use the iLO Federation Group Power feature with an iLO Federation group, ensurethat each member of the group has granted the Virtual Power and Reset privilege to the group.For more information about privileges, see “Configuring iLO Federation” (page 7).

Changing the power state for multiple serversThe Virtual Power Button section on the Group Power page displays a summary of the currentpower state of the grouped servers, including the total number of servers that are in the ON, OFF,or Reset status. The System Power summary indicates the state of the server power when the pageis first opened. Use the browser refresh feature to update the System Power information.Some of the Virtual Power Button options do not shut down the operating system gracefully. Beforeyou use the Virtual Power Button options, you must initiate an operating system shutdown by usingthe Remote Console.To change the power state for a group of servers:

Using the iLO Federation group power feature 25

Page 26: Ilo

1. Navigate to the iLO Federation→Group Power page, as shown in Figure 7 (page 26).

Figure 7 Group Power page

2. Select a group from the Selected Group menu.The grouped servers are listed by power state with a counter that shows the total number ofservers in each state.All of the servers in the selected group will be affected by the changes you make on this page.For information about viewing the list of affected servers, see “Viewing servers affected bythe Virtual Power Button” (page 27).

3. Do one of the following:• To change the power state for servers that are in the ON or Reset state, click one of the

following buttons on the left side of the page:

◦ Momentary Press —The same as pressing the physical power button.Some operating systems might be configured to initiate a graceful shutdown after amomentary press, or to ignore this event. HP recommends using system commandsto complete a graceful operating system shutdown before you attempt to shut downby using the Virtual Power button.

◦ Press and Hold—The same as pressing the physical power button for 5 seconds andthen releasing it.The servers in the selected group are powered off as a result of this operation. Usingthis option might circumvent the graceful shutdown features of the operating system.This option provides the ACPI functionality that some operating systems implement.These operating systems behave differently depending on a short press or long press.

26 Using the iLO Federation features

Page 27: Ilo

◦ Reset—Forces the servers in the selected group to warm-boot: CPUs and I/O resourcesare reset. Using this option circumvents the graceful shutdown features of the operatingsystem.

◦ Cold Boot—Immediately removes power from the servers in the selected group.Processors, memory, and I/O resources lose main power. The servers will restartafter approximately 6 seconds. Using this option circumvents the features for gracefulshutdown of the operating system.

• To change the power state for servers that are OFF, click the Momentary Press button onthe right side of the page. This button is labeled Power On.

NOTE: The Press and Hold, Reset, and Cold Boot options are not available for serversthat are OFF.

A confirmation dialog box appears.

4. Click OK to proceed with the Virtual Power Button push.iLO displays a progress bar while the grouped systems respond to the Virtual Power Buttonpush. The progress bar indicates the number of servers that successfully accepted the command.The Command Results section displays the command status and results, including error messagesrelated to the Virtual Power Button push.

Viewing servers affected by the Virtual Power ButtonThe Affected Systems table provides the following details about the servers that will be affected bya Virtual Power Button push.

• Server Name—The server name defined by the host operating system.

• Server Power—The server power state (ON or OFF).

• UID Indicator—The state of the UID. The UID helps you identify and locate a system, especiallyin high-density rack environments. The possible states are UID ON, UID OFF, and UID BLINK.

• iLO Hostname—The fully qualified network name assigned to the iLO subsystem. Click the iLOlink to open the iLO web interface for the server.

• IP Address—The network IP address of the iLO subsystem. Click the iLO link to open the iLOweb interface for the server.

Click Next or Previous to view more servers in the list.

Configuring iLO Federation group power settingsThe group power settings feature enables you to set dynamic power caps for your grouped servers.When using Automatic Group Power Capping, note the following:

• When a group power cap is set, the grouped systems share power in order to stay below thepower cap. More power is allocated to busy servers and less power is allocated to serversthat are idle.

• The power caps that you set for a group operate concurrently with the power caps that youcan set on the Power Settings page for an individual server.

• When a power cap is set, the average power reading of the grouped servers must be at orbelow the power cap value.

• If you want to configure power capping settings for an iLO Federation group, ensure that eachmember of the group has granted the Configure iLO Settings privilege to the group. For moreinformation about privileges, see “Configuring iLO Federation” (page 7).

Configuring iLO Federation group power settings 27

Page 28: Ilo

• A license is required if you want to make changes on the Group Power Settings page. Formore information about iLO licensing, see the following website: http://www.hp.com/go/ilo/licensing.

• You cannot use the iLO web interface to configure group power capping settings for SL servers.Use one of the following tools to configure the power capping settings for SL servers:

◦ Power Interface Control Utility—This utility is available at the following website: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?prodTypeId=15351&prodSeriesId=4324034&swItem=MTX-cb0c48d305d24a4dbe80e5eecc&prodNameId=5037746.

◦ HP ProLiant SL Advanced Power Manager—For more information, see the HP ProLiant SLAdvanced Power Manager User Guide.

The HP Automatic Group Power Capping Settings section enables you to view measured powervalues, set a power cap, and disable power capping.

• The Measured Power Values section lists the following:

Maximum Available Power—The total power supply capacity for all servers in a group◦◦ Peak Observed Power—The maximum observed power for all servers in a group

◦ Minimum Observed Power—The minimum observed power for all servers in a group

During POST, the ROM runs two power tests that determine the peak and minimum observedpower values.

• Use the Power Cap Thresholds as guidelines for configuring the Power Cap Value.

Maximum Power Cap—The maximum power available for the servers in a group. Theservers in a group must not exceed this value.

◦ Minimum High-Performance Cap—The maximum power that the servers in a group usein their current configuration. A power cap set to this value does not affect serverperformance.

◦ Minimum Power Cap—The minimum power that the servers in a group use. A power capset to this value reduces the server power usage to the minimum, which results in serverperformance degradation.

• The Power Cap Value section allows you to configure the power capping settings. Forinstructions, see “Configuring Automatic Group Power Capping settings” (page 29).

The Current State section shows the current power consumption.

• Present Power Reading—The current power reading for all servers in a group.

• Present Power Cap—The configured power cap for all servers in a group. This value is 0 ifthe power cap is not configured.

28 Using the iLO Federation features

Page 29: Ilo

Configuring Automatic Group Power Capping settings1. Navigate to the iLO Federation→Group Power Settings page, as shown in Figure 8 (page

29).

Figure 8 Group Power Settings page

2. Select a group from the Selected Group menu.All of the systems in the selected group will be affected by the changes you make on this page.

3. Select the Enable power capping check box.4. Enter the Power Cap Value in watts, BTU/hr, or as a percentage.

The percentage is the difference between the maximum and minimum power values. Thepower cap value cannot be set below the server minimum power value.When values are displayed in watts, click Show values in BTU/hr to change the display toBTU/hr. When values are displayed in BTU/hr, click Show values in Watts to change thedisplay to watts.

5. Click Apply.

Using the iLO Federation firmware update featureThe Group Firmware Update feature enables you to update the firmware of multiple servers froma system running the iLO web interface.A license is required if you want to make changes on the Group Firmware Update page. For moreinformation about iLO licensing, see the following website: http://www.hp.com/go/ilo/licensing.This feature allows you to do the following:

• View the number of servers with each supported firmware version. The percentage of the totalnumber of servers with the listed firmware version is also displayed.

• View the flash status for the grouped servers. The percentage of the total number of serverswith the listed flash status is also displayed.

• View the TPM status for the grouped servers in the Option ROM Measuring section. Thepercentage of the total number of servers with the listed TPM status is also displayed.

• Update the firmware. The following firmware types are supported:

iLO◦◦ HP ProLiant System ROM

Using the iLO Federation firmware update feature 29

Page 30: Ilo

◦ System Programmable Logic Device

◦ SL Chassis Firmware

For more information, see “Updating firmware for multiple servers” (page 30).

• View the list of servers that will be affected by a firmware update. For more information, see“Viewing servers affected by a Group Firmware Update” (page 31).

Updating firmware for multiple serversTo update the firmware of servers in an iLO Federation group:1. Download a supported type of firmware from the following website: http://www.hp.com/

support.2. Save the firmware file to a web server.3. Navigate to the iLO Federation→Group Firmware Update page.4. Select a group from the Selected Group menu.

All of the systems in the selected group will be affected by the changes you make on this page.5. Optional: Click a firmware version, flash status, or Option ROM Measuring status link to filter

the list of affected systems.

30 Using the iLO Federation features

Page 31: Ilo

6. In the Firmware Update section, enter the URL to the firmware file on your web server, andthen click the Update Firmware button.The Flash Status section is updated and a message similar to the following appears, as shownin Figure 9 (page 31).Flashing Firmware Image, please wait...

Figure 9 Group Firmware Update page

This message and the percent complete value apply to all of the affected servers.When the update is complete, the Firmware Information section is updated.

Viewing servers affected by a Group Firmware UpdateThis section provides the following details about the servers that will be affected by a firmwareupdate.

• Server Name—The server name defined by the host operating system.

• System ROM—The installed HP ProLiant System ROM.

Using the iLO Federation firmware update feature 31

Page 32: Ilo

• iLO Firmware Version—The installed iLO firmware version.

• iLO Hostname—The fully qualified network name assigned to the iLO subsystem. Click the iLOlink to open the iLO web interface for the server.

• IP Address—The network IP address of the iLO subsystem. Click the iLO link to open the iLOweb interface for the server.

32 Using the iLO Federation features

Page 33: Ilo

5 Using iLO Federation with other HP utilitiesMost iLO Federation tasks can be performed by using the iLO web interface or iLO scripts. Youcan also experience the benefits of iLO Federation in HP SUM and HP Intelligent Provisioning.HP SUM 6.3.0 and Intelligent Provisioning 1.60 include a Technology Preview of the integratediLO Federation features. This preview allows read-only access to the iLO Federation features. Youcan view and interact with the iLO Federation features in the product interfaces, but you cannotuse the features to make configuration changes on your servers.

Using iLO Federation with HP SUMHP SUM is a technology included in many HP products for installing and updating firmware andsoftware on HP ProLiant servers. You can download HP SUM at the following website: http://hp.com/go/hpsum/download.To view the iLO Federation Technology Preview features in HP SUM:1. Start HP SUM.2. If a baseline was not added in a previous run of HP SUM, add a baseline to the Baseline

Library.For instructions, see the HP Smart Update Manager User Guide.

3. Select the deployment type iLO Federation in the main menu, as shown in Figure 10 (page33).

Figure 10 HP SUM main menu

The iLO Federation page opens.

Using iLO Federation with HP SUM 33

Page 34: Ilo

4. Click Add Node.The Add New page appears with the iLO Federation node type selected, as shown inFigure 11 (page 34).

Figure 11 Add New page

5. Enter the IP address of an iLO node that is part of an iLO Federation group.If the node is not in an iLO Federation group, or if the group does not exist, this node will betreated like a regular iLO node.

6. Enter an iLO Federation group name in the iLO Federation Group Name box.7. Optional: Select a baseline or additional package.8. Optional: Select an existing HP SUM group.9. Enter the username and password for a local user account on the iLO system you entered in

step 4.10. Click Add.

HP SUM verifies the credentials and that the group exists. When this process is finished, theOverview page for the node appears, as shown in Figure 12 (page 35).

34 Using iLO Federation with other HP utilities

Page 35: Ilo

Figure 12 Overview page before Inventory

11. Click Inventory.The Inventory page appears.

12. Select a baseline in the Baseline to Apply section.The baseline will be used to evaluate whether the servers in the group need to be updated.The Overview page updates and displays a summary count of all of the types of servers inthe group, as shown in Figure 13 (page 36).

Using iLO Federation with HP SUM 35

Page 36: Ilo

Figure 13 Overview page after Inventory

13. Select from the following firmware types in the View all versions of menu:• Installed iLO

• Installed BIOS

• Installed Power Pic

• Installed CPLDSelecting a firmware type updates the screen to show specific details about the selected type.For example, Figure 14 (page 37) shows the installed CPLD firmware versions.

36 Using iLO Federation with other HP utilities

Page 37: Ilo

Figure 14 Viewing CPLD firmware versions

14. Click the Ready for deployment message to view more details, and then click Review anddeploy updates.The Deploy page appears, as shown in Figure 15 (page 37).

Figure 15 Deploy page

The Deploy feature is view-only in the iLO Federation Technology Preview.

Using iLO Federation with HP SUM 37

Page 38: Ilo

For more information about HP SUM, see the HP Smart Update Manager User Guide at the followingwebsite: http://www.hp.com/go/hpsum/documentation.

Using iLO Federation with HP Intelligent ProvisioningIntelligent Provisioning is a single-server deployment tool embedded in HP ProLiant Gen8 serversthat replaces the SmartStart CDs and Smart Update Firmware DVD used with previous generationsof HP ProLiant servers. Intelligent Provisioning simplifies HP ProLiant server setup, providing areliable and consistent way to deploy HP ProLiant servers.When iLO Federation is configured, you can store Intelligent Provisioning server profiles on thenetwork. If a profile is stored by a server that is managed by an iLO Federation group, you caninstall the same profile on any other managed server in the same group. Select the profile on theDeployment Settings page, as shown in Figure 16 (page 38). This streamlines the deploymentprocess because you do not need to connect a USB key containing the profile to each new server.

Figure 16 Select a Deployment dialog box

NOTE: The menu item for iLO Federation lets you see how this feature is designed to work, butdoes not let you get profiles from the network.

For more information about Intelligent Provisioning, see the HP Intelligent Provisioning User Guideat the following website: http://www.hp.com/go/intelligentprovisioning/docs

38 Using iLO Federation with other HP utilities

Page 39: Ilo

6 TroubleshootingQuery errors occur on iLO Federation pages

Issue: When you open an iLO Federation page, iLO peers and associated data might be missingfrom the page, and the following error is displayed:Errors occurred during query, returned data may be incomplete orinconsistent.This error might occur when a network communication error, configuration problem, or failed iLOsystem prevents the retrieval of data from all systems in an iLO Federation group.Suggested action 1: Wait for twice the configured multicast interval, and then refresh the iLOFederation page. If an iLO system was reconfigured and can no longer communicate with the localiLO, it will be dropped its from its peer relationships after they expire, which should eliminate thequery error.Suggested action 2: Check the Multi-System Map page for errors. The Multi-System Map page canhelp you to identify communication problems between iLO peers. For more information, see “Viewingthe iLO Federation Multi-System Map” (page 22), “A 502 error is displayed on the Multi-SystemMap page” (page 40), “A timeout error is displayed on the Multi-System Map page” (page 39),and “A 403 error is displayed on the Multi-System Map page” (page 40).Suggested action 3: If you are using server blades in an enclosure, verify that Enclosure iLOFederation Support is configured on the Enclosure Settings→Network Access→Protocols page inthe Onboard Administrator web interface. You must have OA 4.11 or later to configure this setting.This is required to allow peer-to-peer communication between the server blades in an enclosure.For more information, see “Configuring enclosure support for iLO Federation” (page 10).Suggested action 4: Verify that the switches on the network are configured to allow communicationbetween iLO peers. For more information, see “iLO Federation network requirements” (page 7).Suggested action 5: If you recently changed the network routes, subnet mask, IP address, or HTTPport for an iLO peer, verify that the iLO peer has a communication path to the local iLO.For more information about iLO network settings, see the HP iLO 4 User Guide.For more information about the iLO HTTP port setting, see the HP iLO 4 User Guide.Suggested action 6: Ensure that communication between the local iLO and the peer with the erroris not blocked by an intermediate firewall or a change to the iLO network configuration and HTTPport setting.

A timeout error is displayed on the Multi-System Map pageIssue: The Multi-System Map page might display a Timed Out error for a peer of the local iLOin the following situations:

• The local iLO system has a peer that has another peer that has failed.

• An intermediate firewall is preventing communication between the local iLO and a peer.

• Network configuration changes are preventing communication between the local iLO and apeer.

• The enclosure that contains the peer is not configured for iLO Federation support.Suggested action 1: Remove or repair the failed peer.Suggested action 2: Verify that the network is configured to allow communication between the iLOpeers.Suggested action 3: Verify that the enclosure that contains an iLO server blade peer is configuredfor iLO Federation support on the Enclosure Settings→Network Access→Protocols page in theOnboard Administrator web interface. You must have OA 4.11 or later to configure this setting.

Query errors occur on iLO Federation pages 39

Page 40: Ilo

This is required to allow peer-to-peer communication between the server blades in an enclosure.For more information, see “Configuring enclosure support for iLO Federation” (page 10)

A 502 error is displayed on the Multi-System Map pageIssue: The Multi-System Map page shows a 502 error.This error indicates that the listed peer rejected a request from the local iLO.Suggested action: Ensure that communication between the local iLO and the peer with the error isnot blocked by an intermediate firewall or a change to the iLO network configuration and HTTPport setting.

A 403 error is displayed on the Multi-System Map pageIssue: The Multi-System Map page shows a 403 Forbidden/Authorization error.This error occurs when the group key on the local iLO does not match the group key on a peeriLO.Suggested action: Ensure that the group key matches for all of the iLOs that are members of theselected group.

iLO peers are not displayedIssue: iLO peers (systems in the same group as the local iLO) are not displayed on iLO Federationpages.Suggested action 1: Ensure that the group key matches for all of the iLOs that are members of theselected group.Suggested action 2: Wait for twice the configured multicast interval, and then refresh the iLOFederation page. If an iLO system was reconfigured and can no longer communicate with the localiLO, it will be dropped its from its peer relationships after they expire, which should eliminate thequery error.Suggested action 3: If you are using server blades in an enclosure, verify that Enclosure iLOFederation Support is configured on the Enclosure Settings→Network Access→Protocols page inthe Onboard Administrator web interface. You must have OA 4.11 or later to configure this setting.This is required to allow peer-to-peer communication between the server blades in an enclosure.For more information, see “Configuring enclosure support for iLO Federation” (page 10).Suggested action 4: Verify that the switches on the network are configured to allow communicationbetween iLO peers. For more information, see “iLO Federation network requirements” (page 7).Suggested action 5: Ensure that communication between the local iLO and the peer with the erroris not blocked by an intermediate firewall or a change to the iLO network configuration and HTTPport setting.

iLO peers are displayed with IPv6 addresses on IPv4 networksIssue: iLO peers on an IPv4 network are displayed with IPv6 addresses on iLO Federation pages.Suggested action: If the network is configured to use IPv4 only, verify that the iLO Client Applicationsuse IPv6 first check box is not selected on the iLO Dedicated Network Port→IPv6 page.

40 Troubleshooting

Page 41: Ilo

7 Support and other resourcesInformation to collect before you contact HP

Be sure to have the following information available before you contact HP:

• Software product name

• Hardware product model number

• Operating system type and version

• Applicable error message

• Third-party hardware or software

• Technical support registration number (if applicable)

• Active Health System log

How to contact HPUse the following methods to contact HP technical support:

• See the Contact HP worldwide website:http://www.hp.com/go/assistance

• Use the Get Help from HP link on the HP Support Center website:http://www.hp.com/go/hpsc

• In the United States, call +1 800 334 5144 to contact HP by telephone. This service is available24 hours a day, 7 days a week. For continuous quality improvement, conversations might berecorded or monitored.

Registering for Software Technical Support and Update ServiceInsight Management software products include 1 year of 24 x 7 HP Software Technical Supportand Update Service. This service provides access to HP technical resources for assistance inresolving software implementation or operations problems.The service also provides access to software updates and reference manuals in electronic format.With this service, iLO Advanced and iLO Advanced for BladeSystem customers benefit fromexpedited problem resolution as well as proactive notification and delivery of software updates.For more information about this service, see the following website: http://www.hp.com/services/insight.If you received a license entitlement certificate, registration for this service occurs after onlineredemption of the license certificate or key.

How to use Software Technical Support and Update ServiceAfter you are registered, you will receive a service contract in the mail. The contract contains theCustomer Service phone number and your SAID. You will need your SAID when you call fortechnical support. By using your SAID, you can also go to the HP Support Center website to viewyour contract online.

HP Support CenterJoin the discussion. The HP Support Center at http://www.hp.com/go/hpsc is a community-based,user-supported tool for HP customers to participate in discussions among the customer communityabout HP products. For discussions related to iLO Advanced and iLO Advanced for BladeSystemsoftware, see the Management Software and System Tools area.

Information to collect before you contact HP 41

Page 42: Ilo

HP authorized resellersFor the name of the nearest HP authorized reseller, see the following sources:

• In the United States, see the HP U.S. service locator website:http://www.hp.com/service_locator

• In other locations, see the Contact HP worldwide website:http://www.hp.com/go/assistance

Related information

Documents• HP iLO 4 User Guide

• HP iLO 4 Scripting and Command Line Guide

• HP iLO 4 Release Notes

• HP Intelligent Provisioning User Guide

• HP Smart Update Manager User Guide

• HP Service Pack for ProLiant User Guide

• HP BladeSystem Onboard Administrator User Guide

• HP BladeSystem Onboard Administrator Command Line Interface User Guide

Websites• HP ProLiant Gen8 Server Management: http://www.hp.com/go/proliantgen8/docs

• HP iLO Management Engine: http://www.hp.com/go/ilomgmtengine/docs

• HP Intelligent Provisioning: http://www.hp.com/go/intelligentprovisioning/docs

• HP SUM: http://www.hp.com/go/hpsum

• HP Service Pack for ProLiant: http://www.hp.com/go/spp/documentation

• HP iLO 4: http://www.hp.com/go/ilo/docs

• HP iLO University videos: http://www.hp.com/go/ilo/videos

• HP Onboard Administrator: http://www.hp.com/go/oa

42 Support and other resources

Page 43: Ilo

GlossaryBIOS Basic Input/Output System.Cookie A small, unscriptable text file placed on your hard drive by a website to preserve specific settings.

When you return to the site, your system opens the cookie with the previously saved settings sothey can be passed along to the site. Cookies are also used to store session data temporarily.

HPQLOCFG HP Lights-Out Configuration Utility.iLO Integrated Lights-Out.OA Onboard Administrator.RIBCL Remote Insight Board Command Language.SAID Service Agreement Identifier.TPM Trusted Platform Module.UID Unit identification.

43

Page 44: Ilo

Index

Aauthorized resellerTechnical support, 41

Automatic Group Power Cappingusing with iLO Federation, 27

CconfiguringEnclosure iLO Federation Support, 10group memberships, 9iLO Federation, 7iLO Federation group memberships, 9iLO Federation with scripts, 13multicast options, 8

EEnclosure iLO Federation Supportconfiguring, 10verifying, 11

FFederation see iLO Federationfirmwareupdating with iLO Federation, 29

Ggroup membershipsmanaging, 9removing, 10viewing, 9

HHP SUMTechnology preview, 33

IiLOupdating firmware, 29

iLO Federationaffected servers, 27firmware update, 31Virtual Media, 25Virtual Power, 27

Automatic Group Power Capping, 27changing server power state, 25configuring, 7configuring multicast options, 8managing group memberships, 9multi-system map, 22network requirements, 7power management, 25removing group memberships, 10RIBCL scripts, 13server blade requirement, 10updating firmware, 29

using, 5viewing critical and degraded servers, 21viewing group memberships, 9viewing server health, 21viewing server models, 21Virtual Media, 23

Intelligent ProvisioningTechnology preview, 38

Mmulticast optionsconfiguring, 8

Nnetwork requirements, 7

OOnboard Administratorconfiguring iLO Federation support, 10

overviewiLO Federation, 5

PpowerAutomatic Group Power Capping, 27group power, 25

RRIB_INFOADD_FEDERATION_GROUP, 17parameters, 18runtime errors, 18

DELETE_FEDERATION_GROUP, 19parameters, 20runtime errors, 20

GET_FEDERATION_ALL_GROUPS, 14parameters, 15return messages, 15runtime errors, 15

GET_FEDERATION_ALL_GROUPS_INFO, 15parameters, 15return messages, 16runtime errors, 15

GET_FEDERATION_GROUP, 16parameters, 17return messages, 17runtime errors, 17

GET_FEDERATION_MULTICAST, 13parameters, 13return messages, 13runtime errors, 13

MOD_FEDERATION_GROUP, 18parameters, 19runtime errors, 19

SET_FEDERATION_MULTICAST, 13parameters, 14

44 Index

Page 45: Ilo

runtime errors, 14

Sscripts see RIB_INFOconfiguring iLO Federation, 13

server bladesverifying iLO Federation capability, 11

serversAutomatic Group Power Capping, 27changing the power state, 25connecting Virtual Media, 23group power, 25health status, 21updating firmware, 29

supportTechnical support, 41

Ttechnical supportTechnical support, 41

Technology previewHP SUM, 33Intelligent Provisioning, 38

telephone numbersTechnical support, 41

TPMviewing status, 29

troubleshooting, 22403 error, 40502 error, 40peers not displayed, 40query errors, 39timeout error, 39

VVirtual Mediausing with iLO Federation, 23

Virtual Power Buttonusing with iLO Federation, 25viewing affected servers, 27

45