ProLiant Server Tools and Troubleshooting

ProLiant Server Tools and
Troubleshooting
Lab guide
Rev. 14.21
HP Confidential – For training purposes only
Use of this material to deliver training without prior written permission from HP is prohibited.
© Copyright 2014 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for
HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
This is an HP copyrighted work that may not be reproduced without the written permission of
HP. You may not use these materials to deliver training to any person outside of your
organization without the written permission of HP.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Oracle and
Java are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark
of The Open Group.
Printed in the USA
ProLiant Server Tools and Troubleshooting
Lab guide
April 2014
HP Confidential — For training purposes only
Contact HP Education for customer training materials.
Contents
Lab 0 — Navigating the HPVL training environment

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
HPVL equipment ................................................................................................................... 1
Introduction .......................................................................................................................... 2
Accessing the HP Virtual Lab environment .......................................................................... 3
Preparing CMS working computer for the labs .................................................................. 11
Exiting the HPVL environment............................................................................................ 14
Summary ............................................................................................................................. 16
Lab 1 — Using HP integrated Lights-Out 4
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 2
Exercise 1—Using key features of the HP iLO 4 Web Administration Interface.................. 3
Exercise 2—Using Integrated Remote Console ................................................................. 34
Learning check .................................................................................................... 50
Summary ............................................................................................................................. 51
Resources............................................................................................................................ 52
Lab 2 — Configuring servers using Option ROM
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Using the ROM-Based Setup Utility ................................................................. 2
Exercise 2—Setting up iLO by using the iLO RBSU............................................................. 19
Exercise 3—Configuring a logical drive with the Option ROM Configuration for Arrays... 26
Summary ............................................................................................................................. 37
Resources............................................................................................................................ 38
Lab 3 — Setting up systems with HP Intelligent Provisioning
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Accessing and configuring the HP Intelligent Provisioning ............................. 2
Exercise 2—Using the HP Smart Storage Administrator ................................................... 12
Exercise 3—Reviewing the Intelligent Provisioning maintenance menu options ............ 37
Exercise 4—Reinstalling HP Intelligent Provisioning ........................................................ 51
Summary ............................................................................................................................. 58
Resources............................................................................................................................ 58
Rev. 14.21 HP Confidential – For training purposes only i

Lab 4 — Offline systems update with HP SPP boot image

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Downloading the SPP from the HP website..................................................... 2
Exercise 2—Reviewing the HP SUM features and discovering the targets ......................... 8
Summary ............................................................................................................................. 24
Resources............................................................................................................................ 24
Lab 5a — Provisioning systems with Red Hat Enterprise Linux 6.5
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Installing the Red Hat Enterprise Linux 6.5 operating system using HP
Intelligent Provisioning ........................................................................................................ 2
Summary ............................................................................................................................. 17
Resources............................................................................................................................ 17
Lab 5b — Provisioning systems with SUSE Linux Enterprise Server 11
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Installing the SUSE Linux Enterprise Server 11 operating system using HP
Summary ............................................................................................................................. 33
Resources............................................................................................................................ 34
Lab 6 — Provisioning systems with Windows 2012 R2 and HP Intelligent
Provisioning Deployment Settings Packages
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Installing the Windows Server 2012 R2 operating system using HP
Exercise 2—Managing the HP IP deployment settings ..................................................... 16
Sharing OS distribution files ....................................................................................... 16
Creating and modifying a deployment setting ........................................................... 20
Summary ............................................................................................................................. 35
Resources............................................................................................................................ 36
Lab 7 — Online systems update with HP SUM technology
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Reviewing the HP SUM features and discovering the targets ......................... 2
Exercise 2—Creating and reviewing the HP SUM reports .................................................. 22
Exercise 3—Installing HP SPP on the target server with HP SUM ..................................... 26
Summary ............................................................................................................................. 40
Resources............................................................................................................................ 40
ii HP Confidential – For training purposes only Rev. 14.21

Contents
Lab 8 — Configuring continuous system monitoring

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1—Using the Agentless Management Service ...................................................... 2
Exercise 2—Exploring the HP System Management Homepage and HP Insight
Diagnostics in online mode................................................................................................... 6
Exercise 3—Accessing the iLO using the HP Lights-Out Online Configuration utility ....... 20
Saving an iLO configuration ........................................................................................ 24
Resetting the iLO chip by using HPONCFG GUI............................................................ 26
Exercise 4—Using the HPONCFG utility to configure iLO by CLI ........................................ 29
Summary ............................................................................................................................. 38
Resources............................................................................................................................ 38
Rev. 14.21 HP Confidential – For training purposes only Contents – iii

iv HP Confidential – For training purposes only Rev. 14.21

Navigating the HPVL training environment
Lab 0
Objectives
After completing this lab, you should be able to:
 Access the HP Virtual Lab (HPVL) environment and identify the components in the
HPVL for course exercises
 Prepare your CMS VM computer for the exercises
 Exit the HPVL environment
Requirements
To complete this lab, you will need:
 Internet access to the HPVL equipment
 Login credentials
Note
Installing the web browser plug-ins requires administrative credentials on
your local system.
HPVL equipment
Each lab group has the following components:
 Central Management Server (CMS) computer, a landing virtual machine (VM) on a
VMware ESXi host that is running the Microsoft Windows Server 2008 R2 operating
system
 One HP ProLiant eighth-generation (Gen8) target server to be managed
The following components are connected to the VLAN networks that you will use for the
lab exercises:
 One NIC of the CMS landing computer and HP integrated Lights-Out (iLO) port on the
target server connected to the Management network
 Other NIC of the CMS landing computer and one NIC of the target server connected
to the Production network
 Dynamic Host Configuration Protocol (DHCP) service for the Production network
enabled on CMS
Rev. 14.21 HP Confidential – For training purposes only L0 – 1

Introduction
You will be assigned a CMS server, which is a virtual machine (VM) running Windows
Server 2008 R2, and a target server to configure and deploy an operating system and
updates. Your CMS is the landing computer and contains all required software. The target
server is configured with the devices and iLO credentials that you need for these labs.
Note
The IP addresses shown in the pictures are for illustration purposes only. Your
IP addresses might differ. Use your assigned IP addressing in the exercises. IP
addresses in screenshots might be partly blurred to avoid confusion.
L0 – 2 HP Confidential – For training purposes only Rev. 14.21

Accessing the HP Virtual Lab environment

To access the HP Virtual Lab (HPVL) environment:
1. Open an Internet web browser and enter http://www.hp.com/go/hpvl in the
address field. Click Access Virtual Lab Environment link on the displayed page.

2. In the HPVL Access Portals field, type your username and click Logon to access the
appropriate access portal for your class.
Note
You might have to click continue to accept a security alert if it appears.
3. The HPVL Access screen displays. Enter your user name and password supplied, and
click the Logon button.

4. Connecting to the HPVL requires you to install one or two plug-ins at some point
(depending on your browser, and if you have previously accessed the HPVL).
If you are prompted during the login process, like in the following example, click
Install.
Note
Depending on your browser, the plug-ins might require that you close and
restart your browser.
5. The HP Virtual Lab Welcome page displays. Click the Terminal Servers icon, to
configure parameters, if needed.
Note
By default, the used window size is 90% of your display size. You would
probably want to choose your target resolution by using this option.

6. In the upper-right menu, click Options.
7. From the drop-down list, you might select your preferred screen resolution, color
depth, or select to Disable local drive access option (usually not needed).
The screen resolutions option page enables you to set the screen resolution or
select a specific percentage of the desktop that the HPVL application will use. Your
selection will vary depending on your desktop native resolution and other running
applications. At least 1280x1024 is recommended (the lab equipment is set to this
resolution, and some forms might not be fully visible if resolution is lower), with a
True Color (24 bit) color depth.

8. After setting these options, click the Home link (the name might vary), and return to
the welcome screen.
9. From the HP Virtual Lab Welcome page, in the Terminal Servers section, click the
HPVL Access link for Windows RDP web client.
10. On the Access a Lab Group page, click the link for your assigned lab group (the name
might vary).

11. Your assigned HPVL lab group page displays. Read the information provided on the
lab group page and note the following conditions:
• The CMS server (VM) will be your landing computer from where you will access
the target server and run the majority of lab exercises.
• The CMS server is on the Management network (10.0.10.xxx) with the iLO port
of the target server. Its IP address (10.0.10.10) and credentials are provided.
• There is also a Production network (192.168.0.xxx) where one NIC of the target
server is connected, and also one NIC (192.168.0.1) of the CMS, with the DHCP
service enabled. You might use this network after deploying OS to target.
• For all lab exercises, use the IP addresses defined on your lab group page.
• All credentials, user names, and passwords that you will initially need are
defined on your lab group page.
Note
IP addressing for each lab group is unique. Always refer to your HPVL lab
group page for your assigned IP addresses and server names.
! Important
Do not change any of the HPVL-assigned IP addresses like the one for the iLO.

12. Use Remote Desktop Access drop-down menu to connect with Student Desktop VM
in the desired screen resolution.
Lab group page
Note
The IP addressing might differ in your lab group, IPs in pictures are partly
blurred to not confuse you. Refer to your HPVL login page for the appropriate
values.

13. When the Remote Desktop login displays, enter the user name and password as
provided on your HPVL lab group page, such as “Administrator” and “hp” and
press Enter or click OK to log in to your CMS computer.
After a few seconds, your CMS desktop window appears.

Preparing CMS working computer for the labs

All of the required software for this course is already installed on your CMS. Only some
large common files needed for the exercises are kept on a network share as a central
repository.
You will now copy those files to your local CMS storage for further use:
1. Start Windows File Manager by clicking icon in the taskbar (or from Start menu).
2. Select a drive mapped to the share “Software_Depot”, and right-click a folder named
classfiles on that drive. From the menu, select Copy.

3. Select your CMS storage drive Local Disk (C:), right-click, and select Paste to copy
classfiles folder from share server to your C: disk root folder.
The copying will begin. It might take 5-10 minutes to transfer 10 GB of data,
especially if many users are copying at the same time. Wait until it is finished.

When copying is completed, you should have C:\classfiles folder on your CMS. The
content of that folder will be examined and used in the following exercises.

Exiting the HPVL environment

To exit the HPVL environment:
1. At the end of each day or when your lab work is complete, close all of your open
Remote Desktop (RDP) sessions. To do this, click the “X” in the command bar and
then click OK to close the Microsoft Windows RDP session and preserve your work
and state.
Note
In full screen (maximized) window, access a yellow drop-down command bar
by hovering your cursor near the top of the screen.

2. On your lab group information page, scroll-down to the bottom and click Exit Lab to
log off of the Deployment Server.
! Important
You must exit the lab using this procedure. If you just close the window, your
session will be left active and you might not be able to log in and use it again
until the session is closed automatically after a predefined time-out (usually
several minutes).
3. Close the F5 Application Access window and click Logout on the Welcome to HP
Virtual Labs screen.

Summary
In this introductory lab, your working environment is presented with log in procedure and
initial environment settings explained. You prepared your CMS working computer for the
exercises by copying necessary files from a network share. Then, you learned how to log
out properly and close the remote session with HPVL environment.

Using HP integrated Lights-Out 4
Lab 1
Objectives
 Describe and use the key features of the HP integrated Lights-Out (iLO) 4 web user
interface (UI)
 Use Integrated Remote Console (IRC) and differentiate the capabilities of the two
main graphical versions
Requirements
To complete the exercises in this lab, you will need:
 Access to the HP Virtual Lab (HPVL) environment
 Central Management Server (CMS) computer, running the Microsoft Windows Server
2008 R2 operating system (or later) with installed:
 Internet Explorer 8 or 10 (JavaScript, Cookies and pop-up windows enabled)
 Java Runtime Environment (32-bit)
 One accessible target HP ProLiant eighth-generation (Gen8) server with the latest
firmware and an iLO Advanced license enabled
 The iLO IP address and credentials for a target server (available on the HPVL login
page) with at least the iLO 4 configuration privilege
Note
IP addressing might be different in the lab groups. Always refer to your HPVL
login page for the proper values. Parts of the addresses might be blurred
here in screenshots to not confuse you

Introduction
The HP iLO Management Engine is the set of HP ProLiant Gen8 embedded management
features that support the complete lifecycle of the server, from initial deployment and
ongoing management to service alerting and remote support.
HP iLO 4 is one feature of the HP iLO Management Engine. The HP iLO subsystem includes
an intelligent microprocessor, secure memory, and a dedicated network interface. This
design makes HP iLO independent of the host server and its operating system.
The HP iLO management processors for HP ProLiant servers virtualize system controls to
simplify server setup, health monitoring, power and thermal control, and remote
administration. HP iLO enables and manages the Active Health System and also features
Agentless Management. When enabled, Simple Network Management Protocol (SNMP)
alerts are sent directly by HP iLO, regardless of the host operating system or whether a
host operating system is installed.
Understanding iLO is critical for users responsible for the administration of the HP
ProLiant servers.

Exercise 1—Using key features of the HP iLO 4 Web

Administration Interface
In this exercise, you will review the Web Administration Interface of iLO.
Note
Some of the features explored in this lab require an optional iLO Advanced
License. For a complete list of features in all licensing models, see Appendix
in the “HP iLO 4 User Guide” or visit Licenses section at HP website
http://www.hp.com/go/ilo
Note
Screens and features within iLO might vary depending on the version of the
iLO 4 firmware installed.
1. Access the HPVL environment as explained in the previous exercise. On the Access a
Lab Group page, click the link for your assigned lab group (the name might vary).
2. To access your CMS server, open a drop-down menu for Remote Desktop Access to
Virtual Machine and select the desired screen resolution.

3. Enter your credentials provided on the HTML Lab Group page.
After a few seconds, your CMS desktop window appears. You might maximize it.

4. On your CMS, start Internet Explorer from the desktop or Start menu button. In the
web browser address field, enter the iLO IP address of the target HP ProLiant Gen8
server provided for your lab group (example: 10.0.10.10) and press Enter. If a
Certificate Error displays, click Continue to this website link.
Note
The iLO web interface requires a supported web browser:
The following settings must be enabled in any browser: JavaScript, cookies,

and pop-up windows.

5. At the iLO Login screen, enter your user name (example: student) and password
(example: hp) as provided on your HPVL login page, and click Log In.

6. The Information → Overview screen displays. This screen provides general

information about your ProLiant server. Notice a field with the currently active
sessions (you should see your session and the IP address from where you accessed
the iLO), the Power On/Off and System Health indicators, the iLO firmware version, IP
address, license and other basic information, including the server name.
Note
The iLO web interface groups similar tasks for easy navigation and workflow.
The interface is organized in a navigational tree view located on the left side
of the page. Each high-level iLO branch has a submenu that is displayed by
clicking the + icon to the left of that branch. Each menu topic displays a page
title that describes the information or settings available on that page.

7. Click and examine the controls at the bottom right of the browser window. These
controls are available from any iLO page.
• Power—Menu to access the iLO Virtual Power options.
• UID—Turning the Unit ID light on or off.
• Health icon—Overall health status for the monitored server subsystems.
Select any component to get more information about the component status.
When the server is powered on, these controls look like this:
These options will be explained later.

8. (optional) If the server is initially powered off, you will see an orange indicator at the
bottom. Click the indicator and select Momentary Press to power on the server (this
command behaves like pressing the physical power button). Then, confirm with OK.

9. Click the ? icon in the upper-right corner of the page to access page-specific help.
This icon is available on all iLO pages and the content changes accordingly.
A new instance of the web browser opens with the help information about items on
that iLO page.

10. Select Information → System Information in the left menu. This screen displays
health information about ProLiant server. Click each tab to discover the health status
of the various hardware components. The information that you see might vary
depending on whether the Agentless Management Service (AMS) is installed.
Note
In this lab, the operating system is not yet deployed, so AMS is not installed.
You will review the System Information tabs in later activities.
Question 1: How many processors are available in your server, name and speed?
________________________________________________________________
Question 2: How much memory is available? Is it HP SmartMemory certified?
Question 3: How many local disks are present? What is the RAID controller type?
________________________________________________________________

11. As an example of how detailed the system information is, consider the 3D
temperature graph display. You can move the cursor over the circles that represent
server temperature sensors in the graph. Scroll-down to see the more detailed
temperature table with alert thresholds settings.
Question: What is the peak temperature inside your server, in Celsius and
Fahrenheit? Which of the sensors read that temperature?
________________________________________________________________

12. Select Information → iLO Event Log. The Event Log records significant events
detected by the iLO subsystem: server power outage, server reset, unauthorized
login attempts, browser and Remote Console logins, virtual power and power-cycle
events, clearing the log, creating or deleting a user, registering for Insight Remote...
etc. Use the entries in the log to assist you with problem diagnosis and to review iLO
operation.
13. You can view the log in CSV format by clicking View CSV and then copying and
pasting displayed content to another application. (Do not use Notepad because end
of lines are Linux formatted, use WordPad instead.)
You might clear the log by clicking Clear Event Log button on the right.

Note
The Severity column displays the importance of the detected event:
• Informational—The event provides background information.
• Caution—The event is significant, but does not indicate performance
degradation.
• Critical—The event indicates a service loss or imminent service loss.
Immediate attention is needed.
14. Select Information → Integrated Management Log (IML). The IML contains a record
of events that have occurred on the server, generated by the system ROM and
services like the iLO health driver including operating system information. Use the
entries in the log to assist you with problem diagnosis. You might add your own
maintenance notes by clicking Add Maintenance Note or mark an event as Repaired.
For example, add a maintenance note: “Reviewing iLO4 IML data...” Click OK.
Note
The Severity column has also Informational, Caution, and Critical events,
plus an additional one:
• Repaired—A Caution or Critical event has undergone corrective action.

15. Select Information → Active Health System Log. The HP Active Health System
monitors changes in the server hardware or system configuration and records
events to a log that holds up to 1 GB of data (enough for approximately two years,
when the log is full new data overwrites oldest data in the log.)
You might download part of the log (or the entire Active Health System Log) and
send it to HP Support for analysis and troubleshooting. The entire log is usually a
large file, so enter the range of days to be included (the default is last seven days).
Optionally, add the contact information to include, and then download the log file.
Note
By downloading and sending the Active Health System data to HP, you agree
to have HP use the data for analysis, technical resolution, and quality
improvements. The data that is collected is managed according to the HP
Privacy Statement, available at http://www.hp.com/go/privacy.

16. Scroll-down the Active Health System Log screen and click Show Advanced Settings.
Review the additional options to enable or disable, clear, or download the entire log.

17. Select Information → Diagnostics. This screen describes features for

troubleshooting analysis and resolution. It displays iLO self-test results and enables
you to reset iLO, generate a non-maskable interrupt (NMI) to the system, or
configure redundant ROM by swapping between Active ROM and Backup ROM.
Caution
Do not reset iLO at this time. It would reboot the iLO and terminate your
current session.
Note
Important sections of the diagnostics screen include:
• iLO Self-Test Results—The results of internal iLO diagnostics with the
status of each self-test listed in the Status column. Not all tests are run
on all systems.
• Reset iLO—The Reset button, which enables you to reboot the iLO
processor. Using Reset does not make any configuration changes, but it
ends any active connections to iLO and interrupts any firmware updates
in progress.
• Non-Maskable Interrupt (NMI) button—The Generate NMI to System
button, which enables you to stop the operating system for debugging.
Use it only in extreme cases in which the operating system is not
functioning properly.

18. Select Information → Location Discovery Services. It is a rack U location discovery

solution for HP Intelligent Series racks. If available, it reports and displays the rack
ID and the server U position, with some additional information listed.
19. Select Information → Insight Agent. As explained, HP Insight Management Agents

support a browser interface for access to run-time management data through the
HP System Management Homepage (SMH). The SMH provides an intuitive interface
to review in-depth hardware configuration and status data, performance metrics,
system thresholds, and software version control information. Your target server is
not booted yet into an operating system with agents, so the SMH is not accessible.

20. Select Remote Console → Remote Console. This option redirects the host server
console to the network client browser, providing full text or graphical mode video
(depending on the license), keyboard, and mouse access to the remote host server.
For the full features, an iLO Advanced License must be installed, as it is in this HPVL
environment. Two options for Remote Console access are by using .NET or Java.
Note
You will explore and use Remote Consoles in the next exercise.

21. Select Virtual Media → Virtual Media. The iLO Virtual Media provides an iLO Virtual
Floppy/USB key and Virtual CD/DVD-ROM that can be used to boot a remote host
server from standard media located anywhere on the network. It supports USB mass
storage devices in general. Virtual media is local media provided to a server by
means of the Integrated Remote Console (IRC) menu, or a URL pointing to a
networked file server.

22. Select Virtual Media → Boot Order. This feature enables you to set the server boot
options. To rearrange the boot order list of available boot devices, you will select
one, click Up and Down buttons as needed, and save new order by clicking Apply.
For this exercise, move the Hard Disk Drive device up to the first place and Apply.
To make a temporary change valid only for the next server reset, you would select a
device from the Select One-Time Boot Option list and click the Apply button.
Other options include:
• Boot to System RBSU—enables loading the system ROM-Based Setup Utility
(RBSU) during the next boot.
• Server Reset—performs reboot of the server. If a one-time boot option is
specified, that setting takes precedence over the Server Boot Order.

23. Select Power Management → Server Power. This screen enables you to view and
control the power state of the server by “pressing” the Virtual Power buttons,
emulating physical buttons on a server.
• Momentary Press—the same as pressing the physical power button on server.
Depending on the operating system, this should initiate a graceful shutdown,
or be ignored. HP recommends using system commands to complete a graceful
operating system shutdown before attempting to shut down by using this
Virtual Power button.
• Press and Hold—the same as pressing the physical power button for 5 seconds
and then releasing it. The server is powered off regardless of the operating
system graceful shutdown features.
• Reset—forces the server to warm-boot (reset). This option circumvents the
graceful shutdown features of the operating system.
• Cold Boot—immediately removes power from the server for approximately 6
seconds. Using this option also circumvents the graceful shutdown.
Note
Only the option Momentary Press is available when the server is powered off.
The Virtual Power buttons are also available at the bottom right corner by
clicking Power, and they are also available in the Remote Console.

On this screen there are also options to adjust System Power Restore Settings
(when the power is restored after outage). You might force Power On or Power Off
always, or the Last Power State (if the server was turned on or off, it will keep that
state when the power is restored). Power-On Delay might also be set, for example
to not start all servers at the same time when power is restored in a datacenter.
24. Select Power Management → Power Meter. This screen enables you to view the
server power consumption over time, in 24-Hour and 20-Minute History Graphs
(average values are blue and maximums red) and tables when you scroll-down.
Question: What was the peak power consumption of your server in the past 24h?
________________________________________________________________
25. Select Power Management → Power Settings. This screen enables you to view and
control the power management features of the server.
• Power Regulator Settings dynamically modify processor frequency and voltage
levels, based on operating conditions, to provide power savings with minimal
effect on performance.
• Power Capping Settings show measured power values. You might enable and
set a power cap value (limits for the maximum power available to the server) or
set a warning triggers for peak or average power consumption.
Note
The power options include:
• HP Dynamic Power Savings Mode—Automatically varies processor
speed and power usage based on processor utilization, allowing the
reduction of power consumption with little impact to performance.
• HP Static Low Power Mode—Reduces processor speed and power
usage.
• HP Static High Performance Mode—Sets processors to run at
maximum power or performance at all times, regardless of the
operating system policy.
• OS Control Mode—Sets processors to run at maximum power or
performance at all times, unless the operating system enables a power
management policy.

26. Select Network → iLO Dedicated Network Port. iLO is accessed over the dedicated
management network (as the best practice) through a web browser or by means of a
command line interface (CLI) using the Secure Shell (SSH) protocol. In either case,
iLO network settings are required and available in these tabs.
The Summary tab shows the name of iLO network interface in use (iLO Dedicated or
Shared Network Port), information, and link state. The other tabs enable users to
configure the network parameters: General, IPv4, IPv6, and Simple Network Time
Protocol (SNTP).
Note
The Shared Network Port uses a NIC that is built into the server. The NIC
handles server network traffic and might, if iLO is configured to do so, handle
iLO traffic at the same time. Only, the best practice is to have an iLO
dedicated management network for security and reliability reasons.
The iLO Dedicated Network Port and the iLO Shared Network Port cannot
operate simultaneously. If the iLO Dedicated Network Port is enabled, then
the iLO Shared Network Port is disabled, and vice versa.

27. Select Remote Support → Registration. When automated Remote Support is

registered and enabled, Active Health System information is sent to HP periodically
through a configured Insight Remote Support server for troubleshooting and quality
improvements.
Hosting device is not available in this test environment. When a server is registered,
you would use the Remote Support → Service Events page to monitor service
events, send test events, and set the maintenance mode (when events are flagged
as not requiring action).
The Remote Support → Data Collections page shows information about the data
that is sent to HP, and it enables you to manually initiate the data sending.

28. Select Administration → Firmware. This screen shows the firmware version of the
iLO and allows to perform an upgrade. You would click Browse and upload a
prepared .bin firmware file (unavailable, this is not to be executed at this time).
Note
In a later exercise, you will see how to upgrade the firmware with an HP
Service Pack for ProLiant (SPP) and by using the HP Smart Update Manager
(HP SUM) engine, which ensures that all dependencies are met in the process.
Question: What is the iLO firmware release deployed in your server?

________________________________________________________________

29. Select Administration → Licensing. This screen shows the licensing and enables
you to enter your License Key and activate the iLO Advanced features. This server is
already licensed with a provided iLO 4 Advanced Activation Key.

30. Select Administration → User Administration. This screen enables you to control
which local users or directory group accounts are allowed to access the various
features in iLO and with what privilege level. Click ? (help) in the upper-right corner
to discover what the various account privileges allow.
! Important
The Administer User Accounts privilege is required to modify user settings.
Without that privilege you might manage only your own account by clicking
Edit. Do not change password or other settings.

31. Select Administration → Access Settings. This screen controls how iLO might be
accessed for all iLO users, and it allows complete customization of the iLO external
access methods for specialized environments.
The Service section enables you to configure SSH and Simple Network Management
Protocol (SNMP) Access settings (changing these settings usually also requires
configuration of the used web browser).
IPMI/DCMI, if enabled, allows you to send industry-standard Intelligent Platform
Management Interface (IPMI) and Data Center Management Interface (DCMI)
commands over the LAN.

32. Scroll down the Access Settings screen and review various access settings that are
configurable. Click ? (help) in the top-right to review all options and default values.

33. There is also a Language tab on this screen for installing and uninstalling language
packs and selecting the default language for all users, and also the current language
for this session only.
34. Select Administration → Security. This screen enables you to configure various
security settings for iLO 4. Navigate through the tabs to discover the security setting
options. Click ? (help) in the upper-right corner for more information. Only iLO
Administrator has privilege to modify most of the settings on this page.

35. Select Administration → Management. This screen enables you to modify how iLO
4 will generate SNMP alerts and forward them to an appropriate destination in
response to an event. By default, Agentless Management is selected in HP ProLiant
Gen8 servers with or without the Agentless Management Service (AMS). In your
environment, you will enter optional information to track the servers and roles.
The Insight Management Agents, SNMP traps, mail alerts and remote logging might
also be configured here.

Note
When using the HP ProLiant BL servers (not in this environment), you would
have an additional BL c-Class → Active Onboard Administrator screen, only
available on blade servers, providing high-level information and enabling you
to launch the Onboard Administrator GUI. The use of Onboard Administrator
in an HP BladeSystem enclosure is outside of the scope in this course.

Exercise 2—Using Integrated Remote Console

The iLO Integrated Remote Console (IRC) feature enables an administrator to connect to
the console of a ProLiant server remotely. With Remote Console access, you will observe
power-on self-test (POST) boot messages, as the remote host server restarts and initiate
ROM-based setup routines to configure the remote host server hardware. The graphical
remote consoles (if licensed) also enable you to view and control the host server beyond
POST. This includes installing and monitoring an operating system installation.
Note
Depending on the ProLiant model, an iLO Advanced License might be required
to access the remote console beyond POST and to use the graphics mode and
full Remote Console features.
The two main graphical consoles that are available are the .NET Integrated Remote
Console (IRC) and Java Integrated Remote Console (Java IRC). Linux users requiring a
Text Console (or Virtual Serial Port) use SSH to access iLO and CLI commands to launch
the console.
1. If you have logged out of your target blade iLO 4, complete the following steps:
a. Connect to the HPVL, and from your login page access CMS.
b. Open a web browser, and in the URL field, enter the iLO 4 IP address of your
target blade (ignore any certificate errors that might display).
c. At the iLO login screen, enter your iLO credentials and click Log In.

2. From the main menu in the left pane, select Remote Console.
• The .NET IRC might be run from a Windows client only and requires the .NET
Framework (3.5 or later) full profile to be installed.
• Java IRC requires Java to be installed. It can be used from a Linux or a Windows
client. Click the Java tab to review the requirements for Java IRC.
Additionally, the Remote Console is accessible by using:

• Stand-alone Remote Console (HPLOCONS)—provides full iLO IRC functionality
directly from your Windows desktop, if installed, without going through the iLO
web interface.
• iLO Mobile Application for iOS and Android devices—provides IRC access from
a supported mobile phone or a tablet.

3. Select the Launch tab. In the Integrated Remote Console area click Launch button.
The following message displays for a moment. It takes a minute or so for the
connection to be established.
4. If this is your first time accessing the IRC, when you launch the IRC from a non-
Secure Sockets Layer (SSL) connection, the browser displays a Security Warning.
Click Run.

The Integrated Remote Console plug-in will load.
5. Then, a black Integrated Remote Console window displays, indicating that the
system is trying to authenticate the access and establish a video connection.
Monitor the process in the status bar at the bottom of the screen.
Note
When a .NET IRC or Java IRC session is active, UID blinks on the iLO web page.
Note
For easier reading and to save the toner in printed versions of this document,
black background screenshots are inverted to white background.

6. Within a few seconds, the Remote Console access will be established. If your target
server was powered on at the beginning of this lab and does not have an operating
system installed, you will see the boot cycling procedure on the screen.
Note
If the server is powered off, use the IRC menu Power Switch, as shown in the
next step, to power it on.
Notice the current POST codes from the server displaying in the console status bar.
Also notice the IRC screen resolution at the bottom-left corner. If you double-click
that information, the screen size will be set to be the same as on the source server.

7. From the upper-left menu, select Power Switch. Notice the ability to control power
to the ProLiant server by virtual power buttons from the Integrated Remote Console
menu.
Note
If the server is powered off, nothing is displayed and Momentary Press is the
only option available in the Power Switch menu. Use to power on the server.

8. Select Keyboard from the menu and notice the special keys and combinations that
might be sent from the IRC virtual keyboard to the target server.

9. Select Virtual Drives from the menu and then Image File CD ROM/DVD. This options
allows you to mount an ISO image file as a virtual CD-ROM/DVD on the target server.

10. A window displays showing you files located on the server from which you are
accessing the iLO (in this case, your CMS). Browse to the c:\classfiles\SPP folder,
select SPP .ISO file available (example: HP_Service_Pack_for_Proliant_2013.09.0-
0_744345-001_spp_2013.09.0-SPP2013090.2013_0830.30.iso), and click Open to
mount it.
Note
Virtual Drives (.ISO images) might be also bootable. They are used for
updating firmware, deploying operating systems, and many other tasks.

11. Open the Virtual Drives menu and clear the Image File CD-ROM/DVD check box to
unmount the drive. You will use this procedure later in the exercises.
The activity of a Virtual Drive is monitored, so you can check the status in the status
bar at the bottom-right corner. The middle indicator is the virtual drive (the left
indicator is for the health status, and one on the right is for the power), except when
it is URL-mounted.
Note
If the target server is in a rebooting cycle, it might start the boot procedure
from the virtual DVD drive you just attached, before you did unmount. In that
case, unmount the drive and select Power Switch → Reset to stop it.

12. At the bottom of the .NET IRC screen, notice the controls for recording and playing
back video streams of the server events. You might load and play pre-recorded file,
or review the Server Startup and Server Prefailure sequences which are captured
automatically in the iLO 4 memory for troubleshooting purposes.
Click Play button, select Server Startup and click Start.

13. The time of a recording is displayed in the lower right area. Use the control buttons
on status bar to pause or rewind the playback. To stop, click the Play button again.
14. After stopping, you will be offered to save the image from iLO storage to the other
place. Use the C:\classfiles folder on CMS and name it for example: iLO Startup.
Note
When needed you would load that file later by pressing Play button on the
IRC screen and selecting From file option in the Playback Source dialog.

15. The Record feature is used to record an iLO 4 session of your choice. Click the Record
button at the bottom, select C:\classfiles folder on your CMS and provide a file name
to save the video stream. Stop the recording by clicking the Record button again.
16. Ensure that all Virtual Drives are unmounted (unchecked) and close the IRC window.

17. At the iLO WEB Administration interface, click the Launch button in the Java
Integrated Remote Console section of the Remote Console screen.
18. At the Security Warning, select Always trust content from this publisher and then
click Yes.

19. Select Always trust content from this publisher again (if appears) and then click
Run.
20. The Java Integrated Remote Console opens. It has some similar features (examine
the menu) as the .NET version and some differences. For example, it cannot capture
and playback a video stream or share a remote console with another user. After
reviewing this screen, close the Java IRC window.

21. At the iLO WEB Administration interface, click the Hot Keys tab on Remote Console
screen. This tab enables you to define up to six hot keys to use during IRC sessions.
Hot keys are active during Remote Console sessions, and each hot key represents a
combination of up to five different keys that are sent to the host server when that
hot key is pressed. If a hot key combination is not defined (NONE), it will be
interpreted as the original key press.

Learning check
Question 1: When you use the Press and Hold virtual button, will the operating
system preserve unsaved data?
________________________________________________________________
Question 2: How much iLO storage is reserved for HP Active Health System events
data to be recorded?
________________________________________________________________
Question 3: Where in the iLO web administration interface would you set the
minimal password length for users access?
________________________________________________________________
Question 4: What sequences are captured automatically and pre-recorded in the iLO
4 memory for troubleshooting purposes?
________________________________________________________________

Summary
In this lab, you reviewed the features of the HP integrated Lights-Out (iLO) 4 web user
interface (UI), available settings options and provided information for diagnostics and
troubleshooting.
You also examined .NET Integrated Remote Console (IRC) and Java Integrated Remote
Console (Java IRC) features while connected to a ProLiant server remotely and observed
power-on self-test (POST) process.

Resources
For more information, refer to the following websites:
 HP Integrated Lights-Out (iLO) at http://www.hp.com/go/ilo
 HP ProLiant Gen8 Server Management at
http://www.hp.com/go/proliantgen8/docs
 HP Service Pack for ProLiant at http://www.hp.com/go/spp
 HP SUM product page at http://www.hp.com/go/hpsum
 HP iLO Management Engine at http://www.hp.com/go/ilomanagementengine
 HP iLO video demonstrations at http://www.hp.com/go/ilo/videos
 iLO Mobile Application for iOS and Android devices at
http://www.hp.com/go/ilo/mobileapp

Configuring servers using Option ROM
Lab 2
Objectives
 Configure systems by using the ROM-based setup utility (RBSU)
 Configure HP integrated Lights-Out (iLO) 4 by using the iLO RBSU
 Configure local disk drives by using the Option ROM Configuration for Arrays (ORCA)
Requirements
• Internet Explorer 8 or 10 (JavaScript, Cookies and pop-up windows enabled)
 One accessible target HP ProLiant eighth-generation (Gen8) server with a RAID
controller, local disks, latest firmware and iLO Advanced license enabled
page) with at least an iLO 4 configuration privilege
Introduction
The tools and concepts explored in this lab are accessible during a HP ProLiant Gen8
server boot procedure and are part of the preliminary steps in configuring a single
server. They include the system RBSU, the iLO RBSU, and the ORCA utility.

Exercise 1—Using the ROM-Based Setup Utility

HP ProLiant servers have ROM-based setup utility (RBSU), a configuration tool embedded
in the system ROM. To access RBSU, press F9 at the console of the ProLiant server during
its startup sequence.
RBSU performs a wide range of configuration activities that can include:
 Displaying system information
 Resetting and configuring system parameters
 Configuring system devices and installed options
 Selecting the devices boot order and boot controller order
In this exercise, you will discover the RBSU and examine its key configuration options.
Note
Screens and features within RBSU might vary depending on the server model
and firmware version installed.
1. If you logged out of CMS server after the last exercise, access your CMS server from
the HPVL login page by opening a drop-down menu for Remote Desktop Access to
Virtual Machine and selecting the desired screen resolution.
Then, enter your credentials.

2. Open Microsoft Internet Explorer and, in the address field, enter the iLO IP address of
your target server. If there is a Certificate Error, click Continue to this website.
3. At the iLO Login screen enter ILO user name (example: student) and password
(example: hp), as provided on your HPVL login page, and click Log In.

4. Select Remote Console in the left pane, and click Launch button to start .NET
Integrated Remote Console, as explained in the previous exercise.

5. If your target server is in reboot cycling mode, from the console screen menu in the
upper-left corner select Power Switch → Reset to restart the boot sequence from
the beginning.
If the target server is powered off, turn it on from the HP Integrated Remote Console
(IRC) menu by selecting Power Switch → Momentary Press.
If the target server is running an operating system, try the Momentary Press option
to allow a graceful shut down of the operating system (if the Intelligent Platform
Management Interface [IPMI] driver is loaded), or use the appropriate command
from inside the operating system.
If the target server is not responding, try the Press and Hold virtual key and shut it
down by force (removing power). After waiting for several seconds, use Momentary
Press to turn it on again.

6. Observe that in iLO 4, the console displays video boot progress messages very early,
almost immediately after restart. The power-on self-test (POST) codes are available
in the console status bar at the bottom of the screen, and more information is visible
on the screen from the start.

7. Follow the boot sequence on the console and wait for the F9 Setup option to be
offered at the bottom of the screen (in text mode it appears on the right side). Then,
press F9 (if necessary, click inside the console screen first to have it in focus) and it
will change to F9 Pressed. Wait for the boot sequence to finish all of the required
steps before it enters RBSU.
Note
When starting from iLO, you might specify the “Boot to System RBSU” option
in the Virtual Media → Boot Order menu. Your server then boots to RBSU
next time without any additional actions.
Note
For easier reading and to save the toner in printed versions of this document,
dark backgrounds in screenshots have been inverted to light colors.

Note
In a graphical boot mode, F9 Setup key to enter RBSU appears at bottom left,
it will inverse the label color in response to the selection.
If you omitted to select Setup option in time, in this environment the server
will automatically reboot if booting device is missing at the moment. You
might then select F9 again. Or, restart the server and start from beginning.

When you enter the ROM-Based Setup Utility, the following screen displays.
Note
Depending on your target server properties, the displayed parameters will
differ.

8. If you are accessing the target server RBSU for the first time, or if you are unsure of
the current RBSU settings, it might be a good practice to reset RBSU to the system
defaults. Scroll down using the cursor keys, select System Default Options →
Restore Default System Settings, and press Enter.
! Important
In this HPVL environment, you can restore to the default settings. In other
environments, that might cause problems if the servers are already
configured.
9. If a warning displays, press Enter. Confirm the restore by selecting Yes, Select to
Restore and then press Enter.
The system reboots. Be patient and wait for the system to configure itself
automatically. This process might take a minute to complete.

10. At boot-up, press F9 again and return to the RBSU.

11. After restoring the system defaults, adjust the system date and time to the
appropriate values. Scroll down to the Date and Time and press Enter. Type the date
and time consistent with your CMS server (at bottom-right corner) as a reference.

12. An important option is the boot search order that the server uses to look for a
bootable device. Open the Standard Boot Order (IPL) menu option. To change the
boot order of a device, scroll to the device and press Enter to select it, then select
the new position in boot order where you want the device to be and press Enter.
For practice, try to move a (rarely used) Floppy Drive (A:) to the bottom of the list,
and press ESC to close the menu.
! Important
Do not change the boot order of the other devices (CD-ROM, hard drive,
network adapter, and so on) that will be used later for deploying the
operating system and updates.

13. After selecting the boot order of available device types, from the RBSU main menu,
select Boot Controller Order. Review the sequence that displays through this option
and select which of the mass storage devices should be used as the primary boot
controller.
In this HPVL environment, HP Smart Array Controller should be first in the list. The
server will first attempt to boot the operating system from a hard disk attached to
the primary boot controller.
Press ESC to return to the main menu.

14. Select Server Availability and press Enter, then select ASR Status. To access the
RBSU help system, press the F1 key to discover what the current option does. Then,
press ESC to leave the Help display.
15. As an example for this exercise, change the ASR Timeout option, which sets a
timeout limit for resetting a server that is not responding. When the server has not
responded in the selected amount of time, the server automatically reboots. Scroll
to ASR Timeout, press Enter, select the value of your choice, and press Enter.

16. For practice, scroll to Thermal Shutdown (next option) and press F1 to discover
more. Then, press ESC twice, until you are returned back to the main RBSU menu.
17. Select Advanced Options → Advanced System ROM Options and press Enter. Scroll
to ROM Selection and press Enter. ProLiant servers have Redundant ROM and when
necessary (not now!) you might switch back to the previous version of ROM content.

18. Press ESC and select Virtual Install Disk. The Virtual Install Disk might contain
drivers specific to the server. When enabled, Microsoft Windows Server locates the
required drivers to install, eliminating the need for the user intervention. Modifying
this value is not required now. Press ESC until you return to the main RBSU screen.

19. Select Server Security from the main menu. The system password might be set or
changed on this screen, leave it as it is for now.
Instead, check whether the Intelligent Provisioning option is enabled. This option
enables you to enter and use the HP Intelligent Provisioning functionality of Gen8
(or newer) servers by pressing the F10 key during a startup sequence.
Note
You will access Intelligent Provisioning in a later exercise.

20. Explore the other areas of the RBSU menu, using the F1 key for a help. When you
have finished exploring, select ESC from the main menu and press F10 to exit the
RBSU and reboot to the new configuration.
Note
There is no option to discard any changes when exiting. All changes in RBSU
are applied automatically.
Note
For explanation of all available RBSU options, use the “HP ROM-Based Setup
Utility User Guide” referenced at the end of this lab.

Exercise 2—Setting up iLO by using the iLO RBSU

In this exercise, you will learn to configure iLO 4 by means of the iLO RBSU, which is also
accessible during the startup sequence. This tool is primarily used to set up iLO for the
first time and to configure its network parameters, so it will become accessible from the
management network.
In this training environment, settings are already provided by the HPVL. You will only
review the setup options to see that they are basic, and not as in-depth as in the iLO web
browser administration interface examined in the previous lab.
1. From IRC of your target server, select the Reset command in the menu to restart the
boot procedure. Configuration for iLO by means of the iLO RBSU is early in the
startup sequence, so wait for the prompt and press the F8 key.
Note
You should be prepared to press the key on time with the IRC window in
focus.

Note
Also in a graphical boot mode: F8 key to enter iLO 4 Advanced configuration.
2. When the integrated Lights-Out 4 screen displays, you will use the arrow keys to
move and open the drop-down menu and press the Enter key to select options.

3. From the menu, select Network → NIC and TCP/IP and press Enter. Review the
network port parameters. Notice that your iLO IP address is specified here. Press ESC
to go one step back without changing anything (already configured by HPVL).
4. Select Network → DNS/DHCP and press Enter.

5. Press F1 to view the advanced network settings. Review the parameters and press
F1 again to see the Dynamic Host Configuration Protocol (DHCP) Negotiation Results.
DHCP is not enabled in this environment and iLO should use the static IP assignment
as the best practice. Press ESC twice to return to the main menu without saving any
changes.

6. Select User → Add. For this exercise, create an iLO account with your nickname or
any other alphanumeric term not already used (in this example: test), with a
password “password” (verify by entering the same password again), and full iLO
privileges. Press F10 to save the new user.
Note
Notice that you might create an administrator level iLO user if the console
access is available during a server boot procedure.

7. Select User → Edit. Verify that your new created user is in the list of all users. You
might change the entered user parameters through this screen, when needed.
You might also delete a user from this list by selecting User → Remove, but be
careful to not do that at this time.
Note
If you switch to the iLO Web Browser Interface and select Administration →
User Administration, you will see your newly created user. (Notice that you
could not do this from the iLO web interface without administrator privilege.)

8. Without making any other changes in the iLO RBSU, select File → Exit. Press Enter
to confirm your exit. The boot process will continue from where it was interrupted.

Exercise 3—Configuring a logical drive with the Option

ROM Configuration for Arrays
In this exercise, you will use the Option ROM Configuration for Arrays (ORCA). ORCA
enables you to perform basic configuration of the disk array and then create the logical
drives.
Before proceeding with an operating system installation, you need to ensure that at
least one logical drive is ready.
In most cases, the ORCA utility automatically configures the array with a default setting
based on the number of drives connected to the Smart Array Controller during the setup:
 If there is only one drive, it configures RAID 0.
 If there are two drives, it configures RAID 1.
 If there are three to six drives, it configures RAID 5 or RAID 6.
If more than six are drives attached, ORCA must be run manually. For more in-depth and
user-friendly array configuration options, the HP Smart Storage Administrator (SSA)
utility is available as part of the Intelligent Provisioning Maintenance.
Note
You will use the Intelligent Provisioning Maintenance in a later exercise.

1. From the IRC menu of your target server, select the Reset command. Skip the option
to access the iLO RBSU (F8) which you used in the previous exercise, and wait for
another “Press <F8>” prompt to run the Option ROM Configuration for Arrays Utility.
When that prompt displays, press the F8 key.
Note
Click inside the console window to have it in focus before pressing the F8 key.
Depending on your ProLiant server, you might have to press any key to view
the messages when prompted with the message “Press any key to view
Option ROM messages.”

Note
Also in a graphical boot mode: Press F8 key to enter ORCA utility.
2. When the Option ROM Configuration for Arrays screen displays, use the arrow keys
to move around the screen. Open the menu options by selecting (highlighting them)
and then by pressing the Enter key.

3. Select View Logical Drive option and press Enter. Explore the available logical
drives, RAID level, capacity, and status.

4. Press Enter to view the logical drive details. Discover how many physical drives are
available, and in which bays they reside. Press ESC twice to return to the ORCA menu.

5. Highlight Select Boot Volume, press Enter, then select Direct Attached Storage.
Verify that your logical drive is available for the boot volume and the shared storage
is not available in this environment. Press ESC and return to the main menu.

Note
Direct attached storage is connected directly to the drive controller (or
through an expander to the drive controller), like in this HPVL environment
where you have four local drives. It is also possible to directly attach storage
within the server chassis or in an external chassis (like the HP MDS600).

6. Select the Cache Settings option, which allows you to enable the write-cache option,
even if it is not battery-backed. Press ESC and return to the main menu.

7. From the main menu, select Delete Logical Drive.
! Important
In the HPVL environment, you can delete a logical drive on an unprovisioned
server. In other environments, verify if it might not cause a problem.
Press the F8 key to delete your logical drive, and confirm the selection by pressing
the F3 key.
After the configuration is saved, press Enter to return to the main menu.

8. Select Create Logical Drive. Review the available options for creating a logical drive.
Note
All options on this screen are only visible if physical drives are available.
Because your existing logical drive was deleted in the previous step, you only
see the options for creating a logical drive.
Review the default options for four disk drives attached. Then, select a simpler
configuration:
• Two physical drives in Bay 1 and Bay 2
• Parity Group Count: None selected
• RAID 0
• Spare: None selected
• Maximum Boot partition: Disable (4GB maximum)
You will configure arrays in more details later in the exercise. Now, create the logical
drive by pressing Enter.
Press F8 to save the configuration, then Enter to return to the main menu.

9. Select the Manage License Keys option, which enables you to view and add license
keys when needed. The license keys are for the HP Smart Array Advanced Pack
(SAAP) license. All of these options are also available in the SSA.
10. Keep pressing ESC until you exit the ORCA utility. The booting procedure continues.
Summary
In this lab, you reviewed the configuration utilities embedded in system which are
available during boot procedures. You examined ROM-based setup utility (RBSU), the
main options in menu and how to change parameters when needed.
You accessed the HP integrated Light-Out (iLO) 4 Advanced utility, reviewed the iLO
network parameters and created a new iLO user with administrative privileges.
Then, you accessed the Option ROM Configuration for Arrays (ORCA) utility, examined the
available disk drives and options, deleted a logical drive and created a new one with
different configuration parameters.

Resources
For more information, access the HP Support websites and refer to the following
resources:
 “HP ROM-Based Setup Utility User Guide” at http://www.hp.com/support/rbsu
 “Configuring Arrays on HP Smart Array Controllers Reference Guide” at
http://www.hp.com/support/CASAC_RG_en, which is also available on the
Documentation CD provided in the controller kit with your HP Smart Array Controller

Setting up systems with HP Intelligent Provisioning
Lab 3
Objectives
 Access and configure the HP Intelligent Provisioning functionality
 Configure logical drives by using the HP Smart Storage Administrator (SSA)
 Describe the functionality of the HP Intelligent Provisioning maintenance menu
options
 Update or reinstall HP Intelligent Provisioning embedded in the target server
Requirements
• Internet Explorer 8 or 10 (JavaScript, Cookies and pop-up windows enabled)
firmware and HP integrated Lights-Out (iLO) Advanced license enabled
Introduction
Installing a production operating system (provisioning) on an HP ProLiant server requires
configuring the hardware, installing the operating system, and updating various HP
specific components. One key benefit provided by HP ProLiant Gen8 servers is the
Intelligent Provisioning functionality, which is an embedded set of tools that enable
single-server assisted hardware preparation and operating system installation.
In this lab, you will explore the functionality of Intelligent Provisioning, use the SSA to
prepare a logical drive, and configure your system for provisioning. Also, you will learn
how to reinstall or update HP Intelligent Provisioning feature.

Exercise 1—Accessing and configuring the

HP Intelligent Provisioning
In this exercise, you will boot to the embedded Intelligent Provisioning, perform the
initial setup, review the system information, and explore the basic features and options.
This lab will be completed from the Integrated Remote Console (IRC) of your target
sever.
1. If you logged out of the HPVL environment after the previous lab exercise, log in and
use a web browser to access the iLO Web Administration Interface, as explained in a
previous module. Select Remote Console in the left pane, and click Launch to start
.NET Integrated Remote Console.
Note
While working in the Integrated Remote Console screen, sometimes you
might need to hold the mouse button a bit longer than usual when clicking
around options and menus to be accepted.

2. If your target server is in reboot cycling mode, from the console screen menu at the
upper-left corner select Power Switch → Reset to restart the boot sequence from
the beginning. (If the server is powered off, use the Momentary Press button.)
3. Follow the boot sequence on the console screen and wait for the F10 (Intelligent
Provisioning) option to appear. Press the F10 key to enter Intelligent Provisioning.

Note
In a graphical boot mode, F10 key to enter RBSU appears at bottom left, it
will inverse the label color in response to the selection.
If you miss the opportunity to press the key on time, wait to see if you have
another chance after the boot attempt, or reset the server and start from the
beginning.

When you access HP IP for the first time, the initial Set Preferences screen is shown,
with configuration options.

4. Click the drop-down arrows beside the Interface Language and the Keyboard
Language fields (you might need to press the mouse button a bit longer in IRC) to
review the HP IP interface languages available. Leave English (US) selected.
5. Leave all of the options unchanged in the Initial Networks Settings area.

In another environment, you might select a NIC for network access with the option
to Use Proxy if needed. This is not required in the HPVL environment. You could also
select options for configuring network parameters (such as DHCP Auto-
Configuration, IPv4 Static, or IPv6 Static). The iLO Network Settings (DHCP Auto-
Configuration, IPv4 Static, or Off) are already configured in the HPVL environment.
Do not change these settings.
Caution
Changes to the system are active as soon as you make a selection from this
screen. For example, turning the iLO off would be activated immediately and
prevent you from using the iLO to complete these lab exercises.
6. Click the drop-down arrow beside the System Software Update field to display the
available options for the Intelligent Provisioning software or target server firmware
updates.
Note that the HP website might be used, or you could set up your own repository, or
disable the System Software Update. In this training environment, you do not have
an HTTP/FTP repository configured or Internet HP website access, so select Disable.

7. Click the READ button to display the End User License Agreement (EULA). You must
accept it to use Intelligent Provisioning. When you accept it, the Accept End User
License Agreement option becomes enabled, and the right arrow at the bottom of
the page changes, allowing you to proceed to the next step.

8. Verify all of the options on the Set Preferences screen:

• Interface and Keyboard language: English (US)
• EULA: Accepted
• Initial Network Settings and iLO Network Settings: Unchanged
• System Software Update: Disabled
Click the Continue arrow in the bottom-right corner to accept the configuration
options on this page, initialize networking, and proceed to step 2, Activation.

9. In step 2 you can activate the Intelligent Provisioning or disable it. Of course, for this
lab select Activate and click the bottom-right arrow to proceed.
10. On the Quick Setup for HP Insight Remote Support screen, select Connect Later (it is
not accessible in the HPVL environment), and continue to the next screen.

11. The Intelligent Provisioning Home screen displays. Explore the Intelligent
Provisioning navigational icons at the top-right of the window: Home, Help, System
Information, and Power. Click and review each icon to find the available options.
12. In the System Information window, review the information, and notice the installed
HP IP version. Then close that window by clicking the “X” in the top-right corner.

Exercise 2—Using the HP Smart Storage Administrator

Before installing an operating system, a logical drive must be configured. Disks attached
to the HP Smart Array Controller might be basically configured via Option ROM during the
startup sequence as shown in the previous lab. In this exercise you will explore the HP
Smart Storage Administrator (HP SSA) which has much more features and is a more user
friendly tool than Option ROM Configuration for Arrays (ORCA).
Note
Starting with the Intelligent Provisioning 1.50+, this tool replaced HP Array
Configuration Utility and Array Diagnostics Utility (ACU/ADU) used previously.
The Smart Storage Administrator is available both offline and online for the Microsoft
Windows and Linux operating systems, with similar functionality, and it is also embedded
as part of the Intelligent Provisioning technology in the HP ProLiant Gen8 servers.
As mentioned, HP SSA automatically suggests the optimum configuration for an
unconfigured system, allows online array capacity expansion, spares assignments, RAID
or stripe size migration.
In this exercise, you will use the HP SSA to configure and create a logical drive manually.
1. From the Intelligent Provisioning home screen, select Perform Maintenance.

2. On the Maintenance screen (which you will explore in the next exercise), select HP
Smart Storage Administrator (SSA), and wait a couple seconds to load.
The HP SSA screen opens. Note the ? (Help) icon available at the top-right corner.

3. On the left side, click your HP ProLiant server, or select it from the top-left menu.
4. On the right side, there is the Actions area providing commands that pertain to the
entire server rather than just one controller. Click the Diagnose button.

5. To view the diagnostics report, select Array Diagnostic Report on the left side, then
click View Diagnostic Report on the right.
Note
By clicking Save Diagnostic Report button, you might also save it directly to
a removable device (USB or floppy) only, which is not attached here.
Note
On this screen, there is also SmartSSD Wear Gauge Report, a special tool for
Solid State Drives (SSD), which are not available in this environment, to
provide information about SSD usage and estimated lifetime information.
You might try this option and receive a status.

6. A very detailed report displays. Scroll-down to review, and click Close at the bottom.
7. From the drop-down menu at the top-left corner, select your Smart Array controller,
in this example Smart Array P420i in Embedded Slot.

8. The current status of your controller is displayed on the right side (in the previous
lab you used two disks to create a logical drive by ORCA utility, leaving two drives
unassigned). Click View more details link, review the content, and click Close.

9. The Diagnose button in the Actions area provides a similar report as in server
diagnostics previously, only limited to this controller. Click the Configure button.
10. Click Arrays icon on the left to see a currently defined array. Then, click Unassigned
Drives to display that information. Return to Smart Array P420i screen with the list
of available Actions in the middle pane (the right pane shows status as before).

11. To start defining a new configuration from scratch, delete a logical drive previously
defined with ORCA utility. Click Clear Configuration button (read the note beneath).
Read the warning, and confirm with the Clear button.
A report shows that controller is cleared and in its default state. Click Finish.

12. Now, all available drives are unassigned. You need to define an array of drives before
creating a new logical drive. Click Create Array (read the information beneath).
13. Available physical drives are displayed, sorted by a selected parameter. For this
exercise, select three disk drives (leave one unchecked). Then, click Create Array.

14. After an Array is created, the options for creating a logical drive are displayed. HP
SSA utility will select the best practice (optimum) configuration for your array. Since
three physical drives are available, RAID 5 level is offered as the best trade-off
between available disk space and reliability.
Hover with your cursor over (What’s this...?) signs to read more information about
every option. Select RAID 0 and watch how available Size is changing.
Set RAID 5 level again, and Custom Size of 2 GiB only to make drive transformation
faster in the later exercises (it might take hours if you use the maximum size!). Leave
all other options as HP SSA recommends, and click the Create Logical Drive button.

15. A logical drive creation report displays. You might finish the procedure here, or since
you have one more unused physical drive, click Manage Spare Drives button.
16. Select the last physical disk drive to be a dedicated spare drive and click Save.

17. Review the selected configuration and logical drive capacity. Click Finish.
18. Hover your cursor over Smart Array notification to read the status message. All
Status messages are available in the right pane: View all status messages link.

19. Click the Modify Controller Settings button in Actions area. Various priority levels
display where you might optimize your configuration. Hover cursor above (What’s
this...?) labels for more information. Enable Physical Drive Write Cache State
option which improves drive performance, only additional precautions must be
taken to ensure data integrity (not crucial in test environment). Click Save Settings.
When the configuration report displays, click Finish.

20. Click Advanced Controller Settings button on the home page. Again, review the
available options. Change Monitor and Performance Analysis Delay option to 30
minutes and click OK. Then, click Finish on the displayed configuration report.
21. Click Modify Spare Activation Mode and read the information about two modes.
Leave the Failure Spare Activation option. Click OK.

22. Now, release the spare drive by unchecking it in Manage Spare Drives.
... and click Finish on the displayed report.

23. Add the drive to data drives (Manage Data Drives appears) to expand the Array.

24. Notice the change in Array capacity, used and unused space. Click Finish.
25. Click Logical Drive, the transforming process is in progress and might take a minute
for this small logical drive size. After the process is completed, an option to extend a
logical drive is available, and also to migrate RAID level or Strip size.

26. Click the Migrate RAID/Strip Size button.
27. Change RAID level to RAID 1+0 (for example). Click OK and Finish.

28. After several seconds Logical Drive is transformed. Click Extend Logical Drive.
29. Enter a new logical drive size (it must be bigger) or Maximum Size. Click OK.

30. Read the warning, and click Yes, then Finish. Verify the results.

31. Return to Smart Array → Configure screen. The Clear Configuration button was
used at the beginning of this exercise. For the following exercises and additional
practice, click the Clear Configuration button and confirm to erase the current Array
and Logical Drive. Create a new one by executing the following steps:
1. Create Array and select all four drives available.
2. Use RAID 6 (ADG), which is the default RAID level this time
Note
RAID Advanced Data Guarding (ADG) is a patented HP technology which
provides the highest level of data protection while still delivering a high level
of disk capacity utilization. It is implemented on the selected Smart Array
controllers, allowing greater fault tolerance than RAID 1+0 or RAID 5, and
lower implementation cost than RAID 1+0.
3. Create Logical Drive and Finish.

Verify results by comparing with the following picture.
Question: What is the array used space and size of a new logical drive?
________________________________________________________________

32. Select Smart Array → Set Boot Controller to enable booting OS from the logical
drive attached to this controller. Confirm with OK, read the report and click Finish.
33. Click Set Bootable Logical Drive/Volume to select logical drive from where OS boot
will start. Select your Local - Logical Drive 1 as Primary Boot. Click OK and Finish.

34. The Manage Device Identification LEDs helps you to easier locate physical disk
drives. Select All Physical Drives and Turn off when application exits. Click OK.
Read the information displayed and click Finish.

35. In the left pane, click Cache Manager in Tools area. Select Controller Cache in the
middle pane to display caching information, and click the Caching Settings button.
36. Read the information about available options. Adjust Cache Ratio to 50% Read /
50% Write and Enable Write Cache When Battery Not Present. Click OK and Finish.

37. Click License Manager in the Tools area, where you might add the license key to
enable advanced features (like HP SmartCache), depending on your controller type.
38. Click X icon in the top-right corner to Exit the HP SSA utility and return to main
menu. Confirm with the OK button.

Exercise 3—Reviewing the Intelligent Provisioning

maintenance menu options
This exercise provides a brief overview of the HP IP Perform Maintenance menu options.
Many of these options will be examined in later lab modules.
1. After finishing the previous exercise, you should be at the Intelligent Provisioning
Maintenance screen. If not, follow the instructions provided in Exercise 1 of this lab.
Note
A summary of that procedure is to access IRC, start a server reboot cycle,
press F10 to enter the Intelligent Provisioning functionality, and select
Perform Maintenance from the home screen menu.
Click the icon next to the first item on the left: Active Health System download.

2. On this screen, the Active Health System (AHS) telemetry data from the server might
be downloaded onto a USB key in the form of an Active Health System log file
(hp_serial#_date.ahs). HP support uses that log file for problem resolution.
You might select the data range to be downloaded (or the entire AHS log) and also
fill in the contact information before sending it to HP Support. The content is
encrypted and accessible by HP Support only, except that contact information. In this
environment a USB key is not attached (click Rescan icon), so select Cancel.
Note
When a server is registered for Insight Remote Support, iLO or the Insight RS
Hosting Device sends Active Health System information to HP every 7 days,
and sends configuration information every 30 days.
3. Skip the next menu item, Intelligent Provisioning Preferences. You already
configured those preferences initially when logging in for the first time.
4. The Smart Storage Administrator (SSA) was the topic in the previous exercise.

5. Click Quick Configs. Notice the Current Power Profile. You will select a profile later
when configuring and installing operating system, leave No Change. Click Cancel.
The Quick Configs screen enables you to select a Power Profile with the basic policy
for balancing performance and power usage in the server. These settings are also
configurable directly or indirectly through the ROM-based setup utility (RBSU). Click
the ? (help icon) for more details about this and other tools.
The Quick Configs profiles are prepared in the RBSU → HP Power Profile menu:
• Balanced Power and Performance (the default)—provides the optimum
settings to maximize power savings with minimal performance impact for most
operating systems and applications.
• Minimum Power Usage—enables power reduction mechanisms that might
affect performance negatively. This mode guarantees a lower maximum power
usage by the system.
• Maximum Performance—disables all power management options that might
affect performance negatively.

Note
To customize the individual settings, you would press the F9 key during
server reboot to enter RBSU and use Power Management Options.
6. HP Insight Remote Support provides automatic submission of hardware events to

HP to prevent downtime and enable faster issue resolution. This was the second
screen in the initial HP IP configuration, where you elected to register later because
the HP Insight Remote Support server is not available in this environment.

7. The Firmware Update selection enables you to update the drivers and agents stored
in Intelligent Provisioning and to update the firmware of your target server
components. Because you selected “Disable” in the “System Software Update” field
of the HP Intelligent Provisioning Preferences, this option is grayed out. You will
perform updates in upcoming labs by using HP Service Pack for ProLiant (SPP).

8. The Deployment Settings is a list of profiles (settings) defined for easier OS

deployments. You will create and manage these settings in later exercises. You will
also use a deployment settings package for the automated remote OS installations.

9. Click the Insight Diagnostics icon. After a brief system scan (couple minutes), a
Survey tab displays with detailed information about your system.
Note
HP Insight Diagnostics provides a comprehensive suite of offline (the user-
installed OS is not running) system and component tests, providing in-depth
testing of critical hardware components for devices such as processors,
memory, and hard drives without OS interference.

Workaround note
If an error message displays, indicating that a previous instance of Insight
Diagnostics did not exit properly and you should wait 10 minutes and rerun
Insight Diagnostics, as a workaround, click Exit Diagnostics in the upper-
right part of the screen. Insight Diagnostics reloads and you are brought in.
10. Review the content of Survey, then from the View Level drop-down menu, select
Advanced instead of Summary, and notice the change in the information displayed.
Explore the Categories menu to the right and narrow your search to Memory.
Question: Is the Advanced ECC memory mode configured in your system? When a
memory module was produced and who is the manufacturer?
________________________________________________________________

11. On the Diagnose tab, select All Devices and click Diagnose to examine the devices.
12. After the diagnostics have been completed, the screen switches automatically to the
Status tab. Review the information displayed.

13. Click the Test tab, which is only available in this offline mode (from HP IP or HP SPP).
Tests can be performed selectively or completely, unattended or interactively,
immediately or scheduled. Select the following items on the Quick Test tab:
• Test Mode: Unattended
• Number of Loops: 1
• Device to test: Total memory - Test all available memory
Click Begin Testing.
Note
These tests are non-destructive and safe, only do not offer full functionality
(example: cannot do a write test to disks).
You will also access the Insight Diagnostics utility in online mode from the
installed operating system in a later lab exercise.

Wait a few minutes for the test to complete. Monitor the progress and results.
14. After completion, the report is displayed again in the Status tab.

15. In the Log tab, various logs are collected (probably empty at this time), including the
Integrated Management Log (IML) which you examined in the previous iLO labs.
Review the Admin tab with options to clear the logs, then click Exit Diagnostics.
Note
Again, Insight Diagnostics is also available online as a web-based application.
16. The iLO Configuration Utility, from the Maintenance menu, enables you to change
iLO settings through Intelligent Provisioning instead of accessing the iLO RBSU at
system boot, or through iLO web interface.

Examine the content of this screen and notice the options are familiar from the
previous labs. iLO Configuration by means of HP IP is more user friendly than the iLO
RBSU method, and it allows a reset and reboot of iLO. Neither configuration is as
detailed as the iLO WEB Browser Interface method you examined first. Click Exit.
17. The Erase option enables you to use Erase Utility to clear hard drives, the Active
Health System logs or to reset RBSU settings.

The utility sets the system to its original factory state. Existing data and
configuration are lost. Do not do that! Click Cancel to exit this screen.

Exercise 4—Reinstalling HP Intelligent Provisioning

It might be necessary to update the servers to the latest HP IP version or to reinstall it if
issues have occurred. In this exercise, you will upgrade the embedded HP Intelligent
Provisioning on your target server.
In a production environment, you would access the Intelligent Provisioning home page at
http://www.hp.com/go/intelligentprovisioning and from there you would download
the HP IP image file. In this HPVL environment, an image is already available on CMS.
Updating the Intelligent Provisioning is performed offline by booting from the Intelligent
Provisioning recovery media and the installation begins automatically. Since you have an
.ISO file, you will first map it through IRC as a target server virtual DVD drive and reboot.
1. If you are not in the Integrated Remote Console, access the iLO of you target server
and start it. From the IRC menu, select Virtual Drives → Image File CD-ROM/DVD.

2. Browse to the c:\classfiles\Intelligent Provisioning folder of your local disk and

select the HPIP160.2014_0113.271.iso file. Click Open.
A virtual drive should be now enabled and mounted with the HP Intelligent
Provisioning image file. When you restart the target server, it will boot from that
image, following the specified server boot order.

3. If you are still in HP IP, click the Power button at top-right corner and select Reboot.
Note
If you are not in HP IP, select Power Switch → Reset from the IRC menu.

4. The server boots from the virtual drive (after following the boot order) and HP IP
update starts automatically. Notice the virtual drive activity indicator is blinking.
Wait approximately 10 minutes for the update to finish. When the flashing is
complete, a short message displays about removing CD and the server reboots.

5. In this case, “removing CD” means unmounting Virtual Drive connected to the image.
Make sure to uncheck your Virtual Drives → Image File (CD-ROM/DVD).
6. While the target server is in a reboot cycle, press F10 to enter HP IP again.

7. The HP Intelligent Provisioning loads. After determining settings, a main menu

appears. Click the System information icon at the top-right corner.
8. Compare a new Intelligent Provisioning version with a previous one at this lab
beginning. Close the information window.

9. Notice a slightly improved UI design and explore around to find some other changes.
For example, some options now require a newer iLO release to match.
Upgrading the iLO functionality will be in your next lab.

Summary
In this lab, you examined the HP Intelligent Provisioning functionality of HP ProLiant
Gen8 (or newer) servers.
You accessed the HP IP from the boot procedure, performed an initial setup, and
reviewed all available tools and utilities. By using HP Smart Storage Administrator you
configured disks Array and created a logical drive for your future OS deployments.
Then, you executed an HP IP upgrade (reinstall) procedure by booting the target server
from a provided HP IP installation image file as a virtual drive.
Resources
For more information, refer to the following resources:
 Websites
• HP Intelligent Provisioning at http://www.hp.com/go/intelligentprovisioning
 Documents
• “HP Intelligent Provisioning User Guide” at http://www.hp.com/go/ilo/docs
• “Configuring Arrays on HP Smart Array Controllers Reference Guide” at
http://www.hp.com/support/CASAC_RG_en

Offline systems update with HP SPP boot image
Lab 4
Objectives
 Explain how to download the HP Service Pack for ProLiant (SPP) ISO file from the
HP website
 Explain how to use the HP SPP bootable ISO file as a virtual drive to start an update
 Perform offline firmware update on an HP ProLiant target server
Requirements
 A local computer to access the HP website
 One accessible target HP ProLiant eighth-generation (Gen8) server and HP
integrated Lights-Out (iLO) Advanced license enabled
 An HP Service Pack for ProLiant (SPP) ISO bootable image file
Introduction
Before installing an operating system, the best practice for any new target server is to
first update the firmware to ensure that it is at the supported level.
Also, after deploying an operating system on your server, it is recommended that you
update the firmware, operating system–specific drivers, utilities, and management
agents on a regular basis. These updates provide new features, support for new devices,
technologies, and issues fixing. Periodically updating your servers is a vital part of the
maintenance and troubleshooting and it is part of the HP support requirements policy.
The HP SPP is a comprehensive software and firmware update solution for HP ProLiant
servers. It provides a complete bootable ISO file that combines drivers, utilities,
management agents, and firmware for supported operating systems and server models.
The SPP is also available as subset ISO files that contain specific supported operating
system drivers and utilities. These files are smaller in size for download and not bootable
so can be used for online updates only on servers running a proper operating system.

Exercise 1—Downloading the SPP from the HP website

First, you need to become familiar with the locations where the SPP, hot fixes, and other
available information are distributed.
! Important
This exercise should be performed on your local computer because the HP
websites are not accessible from the HPVL environment. You might bypass
the steps where the lab directs you do download the SPP in the HPVL
environment, and consider it for reference only.
1. Navigate to http://www.hp.com/go/spp using a web browser from your local

computer. This is the home page for HP SPPs. Notice the main areas of the page,
which includes a link to a download section, the Smart Update Video Library with
tutorials and demos, and sections for an overview, news, and other information.

2. Click the Download link.

HP SPPs are released several times each year. Review the Release Summary
section. Notice the current version of the SPP that is available for your server. Also
notice an MD5 Checksum value to verify the file integrity after the download. Click
the link under Full ISO Image title.
Note
You might also access this web page by entering
http://www.hp.com/go/spp/download in your browser.

3. In the next step, you are asked to sign in with your HP Passport (credentials) to
access the HP software. If you do not have an account yet, you would start Create an
account procedure. Otherwise, enter your User ID and Password. Then, click Sign in.
4. After entering the necessary Customer information, click Next at the bottom.

5. In a production environment, you would select a product and click the Download
button. In this HPVL environment, access to the Internet is disabled and the
necessary files for the exercises have already been downloaded to your CMS.

6. On the HP Service Pack for ProLiant Download home page, explore the other options
that are available:
• Hot Fixes & Advisories—The important hot fixes, resolved and open Customer
Advisories (CA) published between SPP releases. These components are tested
against the SPP. For example, in the Hot Fixes section you will find important
updates released after the current SPP, and Known Limitations.
• Release Archive—All the SPPs released within the one-year support window,
and some outside of the support window.
• Documentation—Manuals in downloadable .PDF files.
• Videos— A collection of short videos on the HP Service Pack for ProLiant (SPP)
and its components.

Note
Because of the file size, it is recommended that you verify integrity of the
SPP image file with MD5SUM utility before use. The MD5SUM.exe file is saved
in your CMS folder C:\classfiles. For the current SPP .ISO version, start
Command Prompt and type the following two commands:
cd \classfiles\SPP
c:\classfiles\md5sum.exe
HP_Service_Pack_for_Proliant_2014.02.0-0_761723-
001_spp_2014.02.0-SPP2014020.2014_0128.5.iso
(Copy/paste this command line to Command Prompt, or simply run
SPPcheck.bat available in SPP folder with this command content).
The checksum should be: 450e5e7a9e64644b4e65fb7b89363617

Exercise 2—Reviewing the HP SUM features and

discovering the targets
There are several ways to deploy HP SPP components. It might be done online or offline,
in interactive or automatic modes, to local or remote targets:
 Online mode—You can start the HP SUM utility on a Windows- or Linux-hosted
operating system, and update:
• A local target server (where the HP SUM is actually running).
• Remote target servers that are accessible through a network while running an
operating system.
 Offline mode—The server boots a small Linux kernel from an SPP bootable image
(only the full ISO bootable SPP release) using a boot drive, .ISO file as virtual drive,
or a PXE boot from the network. When starting the procedure, you might select the:
• Automatic mode, where HP SUM updates components without any interaction.
• Interactive mode, following an on-screen instruction guide, and selecting the
options.
In this exercise, you will boot your remote target server from the provided SPP image on
your CMS, start an offline update in interactive mode, review and select options.
1. As in previous labs, access iLO port of your target server. Select Remote Console in
the left pane, and click Launch to start the Integrated Remote Console (IRC).

2. From the IRC menu, select Virtual Drives → Image File CD-ROM/DVD.
3. Browse to the C:\classfiles\SPP folder of your CMS local disk and select the
HP_Service_Pack_for_Proliant_2014.02.0-0_761723-001_spp_2014.02.0-
SPP2014020.2014_0128.5.iso file. Click Open.

A virtual drive should be now enabled and mounted with the HP SPP image file.
When you restart the target server, it will boot from that image.

4. If you are still in HP IP, click the Power button at top-right corner and select Reboot.
Note
If you are not in HP IP, select Power Switch → Reset from the IRC menu.

5. The server boots from the virtual drive (after following the boot order) and HP SPP
image starts. On the initial screen you have 30 seconds to choose Interactive
Firmware Update or Automatic Firmware Update will be started without your
intervention. Select Interactive Firmware Update (use your arrow keys).
Loading HP SPP might take 15 to 20 minutes, depending on the environment.

6. When HP Service Pack for ProLiant is loaded, read and accept the End User License
Agreement (EULA) by checking Accept option with your cursor. Then, click Next.
7. On the next screen, you might select which of the available tools to use (that you
remember from the HP IP content in the previous lab). Select Firmware Update.

8. A “Localhost Guided Update” mode is started and begins with the Step 1: creating an
inventory of baseline and node. Depending on the environment and number of
updates, it might take 10 minutes. Then click Next.

9. The Step 2 is a review of the deployment summary. A baseline library list with the
proposed firmware upgrades is displayed, with Selected option for every ready to
proceed (green icon). Click the question mark ? (Help) at the top-right corner, and
open Help on this page guide, review it and click X in the top-right corner to close.

10. In the deployment summary list, optional or up-to-date items are not highlighted.
Open the Actions menu at the upper-right corner, and click Advanced options.

11. Here, it is possible to force Rewrite or Downgrade components (leave it unchecked)

for Firmware or Software when needed, and adjust reboot options. Select Reboot
nodes after installation to If needed, Reboot delay of 60 seconds, then click OK.
Note
Downgrade: allows you to globally downgrade all of the components to an
older firmware without clicking Force for each in the baseline library list.
Rewrite: allows you to force rewrite of the current firmware versions.
Reboot delay: the number of seconds to wait before beginning the reboot.
The list will be re-analyzed with the new selected options.
Note
Configuring components in Localhost Guided Update mode is not supported.

12. From the Actions menu, select Reports.
13. Review the options, and click Generate to create an HTML report.

It might take a minute to complete.
14. When the reports are completed, scroll-down or select Reports Center from the top
menu. Take some time to examine the reports and their structure. Then, click Close.
Question: How many components will be upgraded on your target server?
________________________________________________________________
Question: Is there any Failed Dependency reported?
________________________________________________________________

15. Scroll-down to the bottom of the Step 2 screen. You might Analyze again, return
Back to Step 1, or Start Over. Click Deploy to begin the firmware upgrade process.
16. Deployment is the Step 3. Monitor the progress of installation, it might take 10
minutes, depending on the needed updates.

17. At one moment, a restart is required and you will lose Integrated Remote Console.
This message might appear, or not.
18. Wait a few minutes and refresh web browser with the iLO home page. Notice a new
firmware version displayed on the welcome screen. Log in using your credentials.
Note
After your IRC session is terminated, Virtual Drive is not available anymore,
server will cycle in the reboot order, not starting HP SPP offline update again.

19. After logging in, notice the new version information, and some new options available
now. For example, iLO Federation section is added in iLO 4 version 1.40 (and later).
Note
iLO Federation Management enables you to manage multiple servers from
one system running the iLO web interface, when they are in the same iLO
Federation Management group. You might use the iLO web interface on one
system to manage all of the iLO systems in the group, according to privileges
that are assigned to members of a group.
In this test environment, only one target server is available.

20. In the Administration section, notice a new feature Key Manager.
Note
The Key Manager page enables you to connect to an operational key
manager, change redundancy settings, view the key manager connection
settings, test the connection, and view key management events.
iLO 4 v1.40 (and later) supports HP Enterprise Secure Key Manager, which
might be used in conjunction with HP Secure Encryption. HP Enterprise
Secure Key Manager generates, stores, serves, controls and audits access to
data encryption keys. It enables you to protect and preserve access to
business-critical, sensitive, data-at-rest encryption keys.
This and other features are part of an iLO licensing package. For more
information about iLO licensing visit http://www.hp.com/go/ilo/licensing

Summary
In this lab, you learned how to locate and download HP Service Pack for ProLiant.
Then, you used a prepared HP SPP image to update firmware in your HP ProLiant target
server. You configured a virtual drive mapping to the HP SPP image file and performed a
firmware upgrade in offline local booting mode.
Resources
 Websites
• HP Service Pack for ProLiant (HP SPP) home page: http://www.hp.com/go/spp
• Software and drivers from HP Support: http://www.hp.com/go/support
• Documentation for HP SPP: http://www.hp.com/go/spp/documentation
 Documents
• “HP Service Pack for ProLiant User Guide”
• “HP ProLiant and Integrity Firmware Management Best Practices Planning
Guide”

Provisioning systems with Red Hat Enterprise Linux 6.5
Lab 5a (optional)
Objectives
After completing this lab, you should be able to explain how to perform a Red Hat
Enterprise Linux 6.5 installation on HP ProLiant Gen8 target server by using HP
Intelligent Provisioning wizard for deployment configuration.
Requirements
firmware and iLO Advanced license enabled
 Red Hat Enterprise Linux 6.5 Server distribution in ISO file
Introduction
After you have configured the hardware for a new ProLiant server, HP Intelligent
Provisioning assists you with the operating system installation. You might use the
embedded wizard for assistance to perform Linux OS installation on the target.
In this lab, you will use HP Intelligent Provisioning to install the Red Hat Enterprise Linux
6.5 Server (RHEL) operating system.
Rev. 14.21 HP Confidential – For training purposes only L5a – 1

Exercise 1—Installing the Red Hat Enterprise Linux 6.5

operating system using HP Intelligent Provisioning
To install Red Hat Enterprise Linux 6.5 Server (RHEL), you will mount a virtual drive with
the RHEL image, and use the HP IP wizard to start the deployment. This lab will be
completed from the Integrated Remote Console (IRC) of your target server.
1. If you have logged out of the HPVL environment, complete the following steps to
access the IRC of your target server:
a. From the HPVL login page, access your CMS by selecting CMS remote desktop.
b. Log in to your CMS with your appropriate credentials.
c. Open Microsoft Internet Explorer and, in the address field, enter the iLO IP
address of your target server.
d. Log in to the iLO WEB Administration Browser with your appropriate credentials.
e. Select Remote Console → Remote Console in the left pane, and click Launch to
start .NET IRC.
f. If you are not booted into Intelligent Provisioning:
1. Reboot your server by selecting Power Switch/Reset from IRC menu.
2. When prompted, press F10 to access HP Intelligent Provisioning
Note
A hint: it might be tricky to press F10 on time, try to keep pressing in advance.
Accept End User License Agreement, if asked.
g. Click the Home icon (if needed) to access the starting HP IP menu.
L5a – 2 HP Confidential – For training purposes only Rev. 14.21

2. From the IRC menu, click Virtual Drives and select Image File CD-ROM/DVD.
3. Browse your CMS local disk and navigate to the C:\classfiles\OS\RHEL 6 Update 5\
folder. Select the provided OS image file RHEL6.5-20131111.0-Server-x86_64-
DVD1.iso and click Open.

4. Ensure that a virtual drive is mounted. Click Configure and Install.

5. The Hardware Settings screen displays. In the System Profiles field, select Balanced
Power and Performance.
Note
This is already the Current System Profile, so selecting No Change would be
acceptable as well.
The System Profile options include:

• Balanced Power and Performance—optimum settings to maximize power
savings with minimal impact to performance for most operating systems and
applications.
negatively affect performance. This mode guarantees a lower maximum power
negatively affect performance.
Note
A hint: remember to hold the mouse button pressed a bit longer in IRC/HP IP.

6. The next option on the Hardware Settings screen is System Software Update. In this
environment, there is no external network access. Select Skip Update.
7. The Array Configuration was prepared in a previous lab. To make sure the disks are
cleaned, select Recommended. Then, click the lower-right corner arrow to continue.

8. Confirm to reset all disks with the OK button. Wait a few seconds to be completed.
9. The HP Intelligent Provisioning install wizard reads the available media and
automatically displays the supported operating system family, in this case Red Hat
Linux.
In the Install Method area, three installation options are available:
• Recommended
• Customized
• Manual
Select the Manual installation for Linux. As the Source Media Type leave Disc
selected. Click the arrow in the lower-right corner of the screen to continue.
Note
Linux might be installed only by using the Manual Install and Disc media.

10. After the system scan for drives has completed, a warning is displayed. Verify
information and click Continue.
The HP IP prepares the disk partition and copies necessary files.

When initial copying is completed, a reboot is performed automatically.
11. After rebooting the installation continues. You are asked to test media, use Tab and
Enter to select Skip in this environment.

12. Red Hat Enterprise Linux 6 GUI appears. Click Next to continue.
Note
A hint: navigate your cursor close to the Linux cursor arrow inside the
window, and click to take control.

13. In this exercise, select English language and English keyboard, click Next.

14. Keep Basic Storage Devices option and click Next.
15. For this exercise, keep the default hostname, click Next.

16. Use a proposed time zone, click Next.
17. For the root password enter password, confirm by entering again, then click Next.
When a Weak Password warning appears, click Use it Anyway.

18. For the type of installation, select Use All Space, then click Next.
Confirm with Write changes to disk.
Formatting filesystem begins.

19. Select the default RHEL installation Basic Server, click Next.
The installation process begins, it might take 10 minutes.

20. When the installation is completed, click Reboot.
After reboot, you might login as a user root with a defined password (password)

Summary
In this lab, you learned how to use HP Intelligent Provisioning wizard to assist you in
configuring and installing Red Hat Enterprise Linux 6.5 Server deployment.
Resources
 Websites
• Red Hat Enterprise Linux web page at
http://www.redhat.com/products/enterprise-linux/
 Documents


Provisioning systems with SUSE Linux Enterprise
Server 11
Lab 5b (optional)
Objectives
After completing this lab, you should be able to explain how to perform a SUSE Linux
Enterprise Server 11 installation by using HP Intelligent Provisioning wizard for
deployment configuration.
Requirements
 SUSE Linux Enterprise Server 11 distribution in ISO file
 SUSE Linux Enterprise Server 11 kISO boot image for HP ProLiant Gen8 servers
Introduction
embedded wizard for assistance to perform Linux OS installation on the target.
In this lab, you will use HP Intelligent Provisioning to install the SUSE Linux Enterprise
Server 11 (SLES 11) operating system. SLES requires the use of HP kISO installer for HP
ProLiant Gen 8 servers. This kISO file contains all of the necessary drivers to support
SUSE installation onto a Gen8 server and provides installation services, which are not
provided on the generic SLES installation DVD. The kISO is available on HP.com and on
SUSE.com websites (referenced at the end of this document).
Rev. 14.21 HP Confidential – For training purposes only L5b – 1

Exercise 1—Installing the SUSE Linux Enterprise Server

11 operating system using HP Intelligent Provisioning
To install SUSE Linux Enterprise Server 11 (SLES 11), you will mount a virtual drive with
the kISO initial drivers image required for HP ProLiant Gen8 servers, and use the HP IP
wizard to start the deployment. Then, you will continue with a standard SLES installation
disk image. This lab will be completed from the Integrated Remote Console (IRC) of your
target server.
access the IRC of your target server:
start .NET IRC.
2. When prompted, press F10 to access HP Intelligent Provisioning
Note
L5b – 2 HP Confidential – For training purposes only Rev. 14.21

Provisioning systems with SUSE Linux Enterprise Server 11

3. Browse your CMS local disk and navigate to the C:\classfiles\OS\SUSE 11 SP2\
folder. Select the provided OS image file hp_proliant_gen8-sle11sp2-x86_64-
1.1.iso and click Open.

Note
acceptable as well.

applications.
Note

environment, there is no external network access. Select Skip Update.
7. The Array Configuration was prepared in a previous lab. To make sure the disks are
cleaned, select Recommended. Then, click the lower-right corner arrow to continue.

8. Confirm to reset the disks with OK. Wait a few seconds to be completed.
automatically displays the supported operating system family, in this case SUSE
Linux Enterprise.
• Recommended
• Customized
• Manual
Select the Manual installation for Linux. As the Source Media Type leave Disc
selected. Click the arrow in the lower-right corner of the screen to continue.
Note

10. After the system scan for drives has completed, a warning is displayed.
Workaround note
There is a known issue with some versions of HP IP and kISO start image,
when SLES attempts installation on Virtual Install Drive instead of Smart
Array disk drives, and fails.
As a workaround in this exercise, you will enter RBSU during the restart and
disable VID, before continuing to kISO boot image.
Click Continue to restart.

11. During the reboot, press F9 (Setup) key to enter RBSU.
12. When RBSU loads, select Advanced Options, then Advanced System ROM Options.

13. Select Virtual Install Disk and change to Disabled.
14. Keep pressing Esc (three times) and confirm to exit with F10 key.

The system reboots and follows the boot order until it loads kISO from Virtual Drive.
15. When a menu appears, press the F3 key to select a Video Mode resolution.

16. Scroll with the arrow keys to select the resolution 1024x768 and press Enter.
17. Once the Video Mode is showing 1024x768, select Installation and press Enter.

The Linux installation begins.

After a couple minutes, the system will prompt you to change DVDs.

18. Change your Virtual Drives assignment (deselect the current Image File, then select
Image File again) to map SLES-11-SP2-DVD-x86_64-GM-DVD1.iso file in the
C:\classfiles\OS\SUSE 11 SP2\ folder on your CMS. Click Open.
19. After changing the virtual drive image, press Enter or OK at the SUSE Linux prompt.

The installation continues.

20. When prompted, accept the License Terms by checking that option and click Next.
Note
A hint: navigate your cursor close to the Linux cursor arrow inside the
window, then click to take control and move it slowly.
or press Alt+A keys to select “I Agree...” option, then Alt+N for the Next button.

21. Checking ISO File is not required in this environment. Follow the SUSE Linux Next (or
Alt+N) prompts and continue the installation.
22. Select the New Installation mode, then press Alt+N or click Next.

23. Select the time zone as proposed and click Next.
24. Select the Physical Machine scenario and click Next.

25. After the system is analyzed, click Install (or press Alt+I).
26. Click the I Agree button for package license (or press Alt+A).

27. Confirm installation with Install (or Alt+I).
The installation will begin. It might take one hour or more to complete.

You can follow the process and monitor the installed packages.
28. After deployment, the system will reboot and let you choose the root password.
Enter password and confirm with password. Select Next and confirm with Yes.

29. For this exercise use the default options (deployment will not be used). Select Next.

30. Make sure to skip Internet access and updates, because it is not accessible here.

31. Select Local user authentication method and click Next.
32. You might create a new user of your choice and click Next.

33. Review the Release Notes and click Next.
34. The system hardware configuration is analyzed. Click Next.

35. In this exercise, you might skip cloning the system. Click Finish.
36. Log in as your defined user (or root), with the defined password for that user.

The system is ready to use.

37. For the following exercises, be sure to re-enable Virtual Install Disk again in RBSU.
Reboot your server by selecting Power Switch/Reset from IRC menu. Or, use the
shutdown command from the operating system, then select Restart.

38. While the target server is rebooting, access RBSU by pressing F9 (Setup) key. Select
Advanced Options, then Advanced System ROM Options.

39. Select Virtual Install Disk and change it back to Enabled.
40. Keep pressing Esc and confirm exit with F10 key.

41. When the server reboots, enter HP Intelligent Provisioning by pressing F10 key.

Summary
In this lab, you were practicing to configure and install SUSE Linux Enterprise 11 Server
operating system to your target.

Resources
 Websites
• SUSE Linux Enterprise Server web site at https://www.suse.com/
• SUSE kISO driver kit at drivers.suse.com/hp/HP-ProLiant-Gen8
 Documents

Provisioning systems with Windows 2012 R2 and HP
Intelligent Provisioning Deployment Settings Packages
Lab 6
Objectives
 Explain how to perform a Microsoft Windows Server 2012 R2 installation by using
HP Intelligent Provisioning wizard for deployment configuration
 Describe how to manage and prepare HP Intelligent Provisioning (IP) Deployment
Settings Packages for automatic HP IP deployments on other servers
Requirements
 Microsoft Windows 2012 Standard distribution in ISO file
Introduction
embedded wizard for step-by-step configuration of the operating system deployment
and to perform an automated installation on the target.
Deployment Settings Packages are used for configuring the automated installations and
saving them for later use or for transferring them (by a USB key) to another server.
In this lab, you will use HP Intelligent Provisioning to install the Microsoft Windows 2012
operating system, and explore the HP IP Deployment Settings feature for creating and
reusing Deployment Settings Packages when provisioning servers.

Exercise 1—Installing the Windows Server 2012 R2

operating system using HP Intelligent Provisioning
To install Windows Server 2012, you will mount a virtual drive with the operating system
(OS) distribution files, and use the HP IP wizard to configure the deployment. This lab will
be completed from the Integrated Remote Console (IRC) of your target server.
access the HP Intelligent Provisioning on your target server:
start .NET IRC.
2. When prompted, press F10 to access HP Intelligent Provisioning.
Note
If HP IP cannot load, check if you enabled again Virtual Disk Drive in RBSU.

Provisioning systems with Windows 2012 R2 and HP Intelligent Provisioning Deployment Settings Packages
3. Browse your CMS local disk and navigate to the C:\classfiles\OS\Windows 2012
Standard and DataCenter\ folder. Select the provided OS image file
SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X
19-05182.iso and click Open.


Note
acceptable as well.

applications.
Note

environment, the most current versions are already installed, and there is no
external network access anyway. Select Skip Update.
7. For the Array Configuration, select Recommended Settings to make sure the disks
are cleaned. Then, click the lower-right corner arrow to continue.

8. Confirm to reset all disks with the OK button. Wait a few seconds to be completed.
automatically displays the supported operating system family, in this case Microsoft
Windows.
• Recommended
• Customized
• Manual
Select the Customized installation. This enables you to specify whether to install
the HP Management agents. As the Source Media Type leave Disc selected. Click the
arrow in the lower-right corner of the screen to continue.
Note

10. After the system scan for drives has completed, enter the necessary information in
the OS Information screen for the deployment to proceed. Verify the operating
system selected, and enter or select the following items:
• Operating System Family: Microsoft Windows Server 2012 R2
• Operating System: Microsoft Windows Server 2012 R2 Standard x64 Edition
• OS Language: US English
• OS Keyboard: US English
• Computer Name: TestTarget
• Administrator password (enter in both fields): password
• Time Zone: (GMT-05:00) Eastern Time (US and Canada)
• Organization name: HP
• Owner Name: HP
Click the arrow in the lower-right corner of the screen to continue.

11. If you selected Customized Install, the next OS Information screen displays the
option to Install AMS (Agentless Management Service), and for Windows 2008
family might also offer Simple Network Management Protocol (SNMP), or Web-
Based Enterprise Management (WBEM) agents. Select Yes and Continue.
Note
The AMS can run concurrently with the HP operating system-based
management software, but HP recommends running only one: either AMS or
the operating system-based management software. Running both
concurrently consumes more memory and processor cycles. In addition,
using both Agentless Management and the SNMP agents might result in
different alerts or duplicate alerts in HP Systems Insight Manager (HP SIM).
In this training, you will use both AMS and the HP SNMP Management Agents
so you can better understand the differences between them.

12. A final verification of the deployment configuration. Click Continue when ready.
The Windows installation begins. Intelligent Provisioning copies the required files to
the logical drive on your target server. A progress bar displays, so you can monitor
the process. It takes up to half an hour to finish this step.

When the copying has finished, the target server is restarted and the Windows setup
procedure begins.
13. When prompted, accept the End User License Agreement (EULA) and click Next.

14. The installation continues and target server will reboot several times. This step
takes approximately 10 minutes.
After installing the default Windows options, HP tools and drivers are also added. It
might take approximately 15 minutes.

When finished, a Windows restart is performed after a one-minute notification.
Windows Server 2012 R2 is installed and ready to use.

15. From the Virtual Drives menu in the console, verify that Image File CD-ROM/DVD is
unmounted.
Note
As you remember, CD-ROM was higher than the hard drive in the RBSU boot
order. The server should boot from the local hard drive from now.
16. From the console Keyboard menu, select CTRL-ALT-DEL and send that key
combination to sign in.

17. Enter the Administrator password that you provided in the IP settings for this
deployment (password). You are logged in.

Exercise 2—Managing the HP IP deployment settings

The deployment settings in HP Intelligent Provisioning might be saved and reused. Also,
the settings might be exported from one HP ProLiant Gen8 server to a USB key and then
transferred to other servers.
In this exercise, you will configure the deployment setting management options. Then,
you will create server configuration packages with all of the options necessary for
automated single-server provisioning.
Note
To reuse the server settings, HP iLO scripting might also be used.
Sharing OS distribution files

For this exercise, you will need to share a folder where an .ISO file with Windows
distribution is located.
1. On your CMS, open Microsoft Windows Explorer and select the C:\classfiles\ folder.
From the classfiles menu, select Share with → Specific people.

2. Ensure that your user name is listed (in this case Administrator) and click Share.
3. The folder is now shared, with the address \\<your_CMS>\classfiles, where

<your_CMS> is the IP address (or DNS name) of your CMS. Click Done.

4. With Intelligent Provisioning, operating system deployments occur over the

Production network. In a Deployment Settings Package, the IP address and share of
a server should be specified at one step. So, you need the CMS IP address on
Production Network.
Note
In this environment CMS IP address is already set to: 192.168.0.1
It might be obtained by following the next several steps. To open the Network and
Sharing Center, click the network icon in the task bar of your CMS at bottom-right
corner, and select that option.
5. The CMS has NICs on both the Management network (PSTT Management Network)
and the Production network (PSTT Production Network). For this exercise, click the
PSTT Production Network link.

6. Click Details.
7. Write down the IPv4 address of this port on the Production network for later use.
Click Close → Close, and exit the Network and Sharing Center.

Creating and modifying a deployment setting

1. Access the Intelligent Provisioning for your target server, as explained previously:
a. Open the IRC window.
b. From the upper left menu, under Power Switch, select Momentary Press to
perform an orderly shutdown of installed Windows 2012 R2.
Note
Or you might use shut-down command in Windows. Start by moving cursor to
the top-right or bottom-right desktop corner to open Charm Bar, select the
Settings icon, then the Power icon and Shut down.
c. Select Momentary Press again to power on the server.

d. As the server is booting, press F10 when prompted to access the Intelligent
Provisioning, before entering the installed production OS.
From the main HP Intelligent Provisioning menu, select Perform Maintenance.

2. On the Maintenance screen, click Deployment Settings.

3. On the Deployment Settings screen, you might create and edit deployment settings
from scratch, or modify an existing setting as a starting point. There are some
predefined settings recommended for (and applicable to) the current server. To
manage these deployment settings, click Manage.
Note
This is an example of available deployment settings. The content for your
server might vary.

4. The next screen displays a list of available settings on the local server on the left
side and settings on a shared storage on the right side. The shared storage might be
an attached USB key or HP Federated iLO.
Note
A USB Key is not attached in this environment. It would require someone to
physically move the key around. That is one method to transfer Deployment
Settings from one server to another.
By selecting a configuration and then clicking the icons in the middle, the
commands for settings management listed will be executed.

An HP Federation iLO is offered to store Deployments. Then, the same profile might
be installed on any other server in the Federation Group by selecting from the menu.
Bringing the profile on a USB key to each server is not needed.
Note
As you remember, HP Federated iLO is a new option introduced with iLO 4
1.40+ providing a cloud-based management system for any HP server
environment. If enabled, the target server becomes a member of a group
(DEFAULT group, if not specified otherwise) and share settings.

5. For this exercise, click the + icon to create a new deployment setting.
6. Enter the name Test_Win for this setting name. Then, click Save.

7. A new Test_Win setting displays in the Local Server list. Double-click it to start
editing it.
Note
You might have an issue with this release when you try to click once in the
Deployment Settings Package. It could go to the edit screen after the first
click, and it might be difficult to select a name and apply other commands.
Note
The setting to edit is also selectable from a drop-down list in the upper-right
part of the screen.

8. The setting categories are listed on the left side of the screen, and should be familiar
from the previous exercises and reviews. Clicking a category displays the associated
data fields on the right. The fields are optional, might be left unchanged or blank.
Click Version Information. You might add some notes in this screen, if you want to.
9. Click Firmware Update. Leave the default value of No Update.
10. Click Array Configuration to review those options, leave them unchanged. You
examined options and created an array in a previous exercise.

11. Click Operating System. Select Microsoft Windows from the Operating System
Family drop-down list on the right side of the screen.
12. Options display for setting a media location and credentials on the local network
from where the operating system files will be retrieved during installation. The
Windows Media Share and FTP site are supported. Leave the Install media location
as SMB/CIFS (Windows Share) and click Browse.

13. Enter the operating system sharing location you created at the beginning of this
exercise. Use the IP address of your CMS Production NIC, which you noted earlier.
• Server Name/IP Address: 192.168.0.1
• Share Name: classfiles
• Network Share User: Administrator
• Network Share Password: hp
Note
In a production environment, you might create a dedicated username for this.
After entering the information, click Next to select the operating system image.

14. Locate your operating system image on Windows share. In this case, point to:
SPP\OS\Windows 2012 Standard and
DataCenter\SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64
Bit_English_Core_MLF_X19-05182.iso file. Click Select and the wizard
verifies its content.

15. Enter the Product Key: N4CM4-V7WVF-BB26H-QHBYP-DC9CJ
! Important
This product key is provided for this training only, and you will find it in the
OS folder in a file “Windows 2012 R2 Standard License.txt”.
Then, click Save.
16. Click Remote Support. Leave this item disabled because it is not available in this
HPVL environment.

17. Click ROM Settings. Leave all the options unchanged.

In a production environment, this screen would enable you to reset the system ROM
to its default settings before installation. There are also options for the power
profile, boot order, SATA RAID, Virtual Install Disk (VID).
18. Click System Options. Leave these options at their default settings.
In a production environment, you could use this screen to select the interface
language, accept the EULA by default, and enable or disable Intelligent Provisioning
access with the F10 key during boot.
Click Save to finish this new Deployment Settings Package. Then, click Exit.

Do not reinstall Windows server at this time. In a production environment, you

might attach a USB key and save the Deployment Settings Package for later use or
on another server. In this version, the package is automatically saved in HP
Federation iLO of this server and available for all target servers in the same group.

Note
In this HPVL environment, handling the USB keys is not practical, so a typical
Deployment Settings Package is transferred to C:\classfiles\Intelligent
Provisioning\Test_Win.zip for you to review its content.
Select the archive in Windows Explorer left pane, right-click the .xml files in
the right pane, and then Open them in Internet Explorer for a review.

Summary
In this lab, you learned how to use HP Intelligent Provisioning wizard to assist you in
configuring a Microsoft Windows Server 2012 R2 deployment. You performed the
production OS installation by using a virtual drive mapped to an OS image, and logged in.
Then, you prepared an HP Intelligent Provisioning Deployment Settings Package to be
used in automated reinstallation or deployments to other target servers.

Resources
 Websites
 Documents

Online systems update with HP SUM technology
Lab 7
Objectives
 Explain how to use the HP Smart Update Manager (HP SUM) to manage target server
updates
 Explain how to use HP SUM reports and configure the HP SPP deployments
 Perform remote target server update in online mode
Requirements
 One accessible target HP ProLiant eighth-generation (Gen8) server running a
production Windows operating system with the HP iLO Advanced license enabled
 An HP Service Pack for ProLiant (SPP) ISO file
 A local computer to access the HP website
Introduction
As you exercised in a previous lab, the best practice for any new server before installing
an operating system is to update the firmware first, to ensure that it is at the supported
level, and then to install the operating system.
After deploying an operating system on your server, it is recommended that you update
the firmware, operating system–specific drivers, utilities, and management agents on a
regular basis. The updates provide new features, support for new devices, technologies,
and bug fixes. Periodically updating your servers is a vital part of the maintenance and
troubleshooting, and it is part of the HP support requirements policy.
The HP SPP is a comprehensive software and firmware update solution for HP ProLiant
servers. It provides a complete bootable ISO file that combines drivers, utilities,
management agents, and firmware for supported operating systems and server models.
The SPP is also available as subset ISO files that contain specific supported operating
system drivers and utilities. These files are smaller in size for download but are not
bootable and can be used for online updates only.

Exercise 1—Reviewing the HP SUM features and

discovering the targets
As explained before, there are several ways to run HP SUM and deploy HP SPP
components: online or offline, in interactive or automatic modes, to local or remote
targets. In a previous lab you performed offline firmware update on a target server in
local mode before deploying an operating system.
In this lab, you will use the HP SPP 2014.02 repository to install updates on your target
server already running Microsoft Windows production OS, by HP SUM technology and
interactive GUI. You will access the provided SPP image on your CMS, start the HP SUM
utility online to find and examine your remote target server, create reports and review
available options.
After the review, the update will be started. Because your server is already updated with
the latest firmware in a previous lab, in this exercise you will update necessary tools and
drivers for the installed operating system.
1. Access the iLO port of your target server. Select Remote Console → Remote Console
in the left pane and click Launch to start the Integrated Remote Console (IRC).

2. If the server is still in the HP Intelligent Provisioning environment (after a previous

lab), click the power icon on the upper-right part of the screen and select Reboot.
Ensure that no bootable Virtual Drives are activated in the IRC menu.
3. After a reboot, your target server should be running the installed Windows operating
system from its local drive. Select Keyboard → CTRL-ALT-DEL in the IRC menu and
log in using as Administrator using your password (password).

4. Before proceeding, you need to turn off the firewall on the target server to allow full
HP SUM access, just in case. In the Server Manager application, select from the menu
Tools → Windows Firewall with Advanced Security.
5. Click Windows Firewall Properties and disable the Domain, Private, and Public
profiles (in all three tabs) by setting Firewall state to Off. Then, click OK.

Windows Firewall should be off now.
6. Back to your CMS (working computer), start Windows Explorer and browse to the
C:\classfiles\SPP folder. To access the SPP files, you must mount .ISO file using the
installed Virtual Clone Drive utility.
• To mount the .ISO:
1) Right-click the HP_Service_Pack_for_Proliant_2014.02.0-0_761723-
001_spp_2014.02.0-SPP2014020.2014_0128.5.iso file.
2) From the menu, select Mount (Virtual CloneDrive E:) or Mount VCD...
• If a virtual drive is already mounted after the previous exercises, unmount it, or
just remount it with the new image.

7. A virtual BD-ROM drive displays in the resources of your working computer, with the
content of the HP SPP image. Select that BD-ROM drive.
The content and folder structure of the SPP package displays. Some elements of the
content are explained in the following table.

8. To start HP SUM utility, browse to the \hp\swpackages folder and as Administrator

execute hpsum.bat (disable the hiding option for file extensions in the Windows
Explorer settings, if needed).
Note
If you already ran HP SUM, it stores information between sessions, including
nodes and user credentials. To clear that information, you would run the
clean-cache.bat script in the same folder before starting (not needed now!).

9. The script will select and run an appropriate HP SUM engine for your environment,
and access it by opening a web page in your web browser.
Note
Do not open HP SUM in more than one browser tab or window or run HP SUM
CLI commands when the GUI is open.
Notice the http://localhost:63001 address of the HP SUM GUI in the
address bar of the browser, to access it while the HP SUM engine is running.
HP SUM displays the Home screen with Localhost Guided Update, Baseline Library,
and Nodes options displayed, and also selectable from the menu on top left.
Note
• Localhost Guided Update—allows you to update the localhost using
the default baseline to apply. The default baseline is the directory
from which you are running HP SUM. You used this method for a
target offline update by virtual drive booting previously (HP SUM is
now started on CMS which is not your target for upgrades).
• Baseline Library—displays the baselines and additional packages
you will use to update your nodes, including the HP SPP, or custom
baselines.
• Nodes—hardware environment components. This screen displays
the nodes that you have added to HP SUM and HP SUM can manage.
• There is a Get Started button that launches Localhost Guided
Update.
For Intranet settings click Don’t show this message again at the bottom, if appears.

10. From the home page, or from the top menu, select Baseline Library.
11. The details for available baselines are displayed. In this case it is only one, HP SPP
2014.02, on the left side. HP SUM examines the content and displays the inventory
on the right. Scroll-down or select shortcuts under a status bar to review the list.

12. Notice the Actions menu at the upper-right. From there, you might Add baselines,
Delete a selected one, or Create custom baselines. To examine the options, select
Add in Actions menu (or click + Add Baselines button in the left pane).
13. On this screen, you would select the location type and browse/enter to location of
any additional baselines and add it (not available in this environment). Click Close.

Note
Browse HP SUM Server Path—This is a directory or file share that the system
running HP SUM can access.
UNC path (for example \\host\dir)—This location uses UNC paths that the
system can access (only supported in Windows systems).
Download from hp.com—After specifying an empty directory, a list of
available baselines is retrieved from hp.com where you select what you want
to download and store (not accessible in this isolated environment).
HP SUM begins to inventory a baseline as soon as you add it. To minimize the
impact on system resources, adding other baselines is not recommended
until one baseline inventory process is finished.
14. Click Create custom option in Actions menu to review that feature.

15. On this screen, you would start with available baseline (or baselines), apply filters to
select a subset of all components, save the output as a new baseline (to an empty
directory), or create new ISO images (bootable or non-bootable) for deployments.
Review the available options and filters (click ? icon for online help). Select Close.
Note
Creating a custom baseline allows you to deploy specific updates, minimize
the size of update baselines, bootable or non-bootable ISOs and standardize
the updates that you deploy to your environment. You might select filters:
• Firmware only, Software only, or Both
• Critical, Recommended, or Optional updates.
• Updates for the specific system Architecture, OS Type, or Device
Type.
HP SUM does not automatically add the custom created baseline to the
Baseline Library, you would use the Add a baseline procedure.

16. To select the nodes (in this exercise you have one target server) from the top menu
go to Nodes page. By default, localhost (CMS) where HP SUM is running is added and
cannot be deleted. To add your target server iLO, select Add from the Actions menu,
or click + Add Node button.

17. HP SUM might search and find multiple nodes on network within an IP range. In this
exercise, you will provide a single iLO IP address of your target server. So, select Add
a single node by IP/DNS name. Enter IP of iLO as specified on HPVL login page
(10.0.10.10). To make the detection faster, specify the exact target type: iLO.
18. Leave the Auto Add Associated Nodes option checked. Select Baseline from a drop-
down menu (only one available), and enter credentials for target server iLO
(username: student, password: hp). Then, click Add button.

19. HP SUM will access (scout) the target and add it to the nodes list. To examine the
added target, select it on the left and in the Actions menu, click Inventory.
Verify the already provided information, and confirm with the Inventory button.
(Here you might also select Baselines/Additional Package, if not selected already.)

20. The inventory is started and might take a minute. You might follow a current task in
the yellow task bar.
21. After examining the target server iLO, General section is updated on the screen.
Then next step is to review the inventory by user and deploy any updates. Select
that option from the task bar link, or in menu Actions → Review/Deploy.

22. You should see that iLO is already updated to the same firmware level (in a previous
lab when you used the offline virtual drive booting method), so this update might
only be forced by clicking a Force button next to the component. There is no need for
that, select Cancel and return to the main page.
Note
Installation and Force options you examined during the offline update.
Associated Nodes are not available in this environment, for example it might
be Onboard Administrator (OA) module for blade servers, or Intelligent Power
Distribution Unit (iPDU) etc.

23. To access the installed Windows Server OS on the target, HP SUM will use its
Production Network NIC port. In this environment, DHCP service for Production
Network is running on your CMS with a configured IP address pool: 192.168.0.2-
192.168.0.9. You might optionally verify the DHCP service role, or access target
server NIC port properties (through IRC) and note the used IP address.
Instead, you will utilize HP SUM finding nodes feature. Click + Add node again, select
as the type of add Find nodes on network with an IP range. Then, click Find Nodes.
24. Enter IP Start Address 192.168.0.2, IP End Address 192.168.0.9, and click
the Search button.

25. After a few seconds, HP SUM will fine one node in the specified IP range (the exact IP
address might vary). Click that node to select it, then click the Add Nodes button.
26. Select your Baseline from the list. Credentials are needed to access the Windows
operating system of the target server and perform updates. Enter Username
Administrator and Password password. Then, click Add.

27. After this node is also added, click Close. Then Close again to return back to the
Nodes screen. Select this new node in the left pane and start Actions → Inventory.
28. Select your Baseline and confirm with the Inventory button.

29. The inventory might take 5 minutes. Monitor in the task bar as self-inventory is
performed for various components, and notice how new information appears in the
node properties areas. When the procedure is finished, review and deploy is offered.
Before deployment, you will review Reports which HP SUM generates.

Exercise 2—Creating and reviewing the HP SUM

reports
After discovering and examining the target devices, HP SUM is ready to proceed with
updates. Before proceeding, generate HPSUM reports and review their content. Reports
give details about the node firmware, software, and driver details, components you
might install, failed dependencies, and updates HP SUM installs.
1. Select your target server on the left (the IP address might vary), and from the menu
upper-right, select Actions → Reports.
Note
To generate a report for more than one node, you would press CTRL and
select all the nodes you want.

2. From the Generate report screen you select the report types you want to view:
• Firmware details—firmware versions currently installed on the node.
• Deploy preview—components that HP SUM can install on the node.
• Failed Dependency details—any failed dependencies on the node.
• Last deploy details—details about what HP SUM installed on a node.
and in which format (HTML, XML, or CSV). Topics that are not valid for your server are
grayed out. The Run in Background option allows you to continue other work and
monitor the task in Activity screen from the top menu.
Select all available report types, HTML format, and click Generate.

3. After a minute, reports are generated. Scroll down to the Reports Center area and
review them by clicking the View Details links. They open in the new browser tabs.
4. In the Deploy preview report, click Updates to be Applied Report link, scroll-down
and review. To close a report, click Close button in the top-left corner.

Note
In these reports you will find all the details about firmware, drivers, software,
versions, dependencies, whether the update is needed for every component
and how critical it is, what versions are available in HP SPP, and other useful
information when you are deciding what to update.
Question 1: How many updates are ready in the Firmware report? How many are
recommended and optional? Is there any critical update?
________________________________________________________________
Question 2: In the Updates to be Applied Report, how many components need

installation, and how many are already installed?
________________________________________________________________
Question 3: Is there any failed dependencies listed?
________________________________________________________________
5. Close the reports windows and click Close on report generation screen to return to
the HP SUM Nodes screen.

Exercise 3—Installing HP SPP on the target server with

HP SUM
The next procedure is to select which Smart Components in HP SPP to install. Because
your HPVL target server is already current, you might select some optional components
or force the installation to overwrite the existing files.
1. On the Nodes screen, select your target server and click Actions → Review/Deploy.

2. Click Installation Options to examine parameters:

• Downgrade—allows downgrade all of the components in the node to an older
firmware version without clicking Force for each component in the baseline list.
• Rewrite—allows to rewrite the current firmware version to components in the
node without clicking Force for each component in the baseline library list.
Click Force options can be applied to and review options:
• Firmware—to downgrade or rewrite firmware software only.
• Software—to downgrade or rewrite firmware software only.
Do not check any of these options.

3. In the Associated Node Details field, you would select nodes for update (there are
no associated nodes in this environment).
In the Baseline Library section, all updates are listed. If a component is up-to-date
already, you might only force a rewrite by clicking the Force button next to that
component. Optional, not installed components have a Select button.
For this course, install HP Insight Management Agents for Windows Server x64
Editions. Scroll-down, find this component, and click Select. It becomes Selected.
...and HP Insight Management WBEM Providers for Windows Server x64 Editions.
Note
As mentioned before, HP AMS can run concurrently with the HP OS-based
management software like SNMP or WBEM, but HP recommends running only
one. Running more than one concurrently consumes memory and processor
cycles, and might result in different alerts or duplicate alerts in HP Systems
Insight Manager (HP SIM).
For this training, you install them all to better understand the differences.

4. Scroll-down to the bottom of the list and notice the Reboot Options area. For this
exercise select If needed from the menu, and set 60 seconds reboot delay. Then,
click Analysis to verify once again your choices before the deployment.
5. The analysis noticed a problem with HP Insight Management Agents. Click a red dot
next to this component. It seems that SNMP service is not activated on the target.

6. We need that component for the later monitoring labs, so now you will practice a
troubleshooting. Access your target server by remote console (IRC), and in Server
Manager, select Manage → Add Roles and Features option.
7. Follow the installation procedure by clicking Next until you select Features.


8. In the Features step, locate SNMP Service and select it. Confirm with Add Features.

9. Click Next and then Install.

10. After the feature installation is completed, click Close.
11. Return to HP SUM screen in your CMS web browser. Now, you must repeat the
Inventory steps (steps 27-29 in Exercise 1) for your target server, so the HP SUM
might retrieve new information about the running services.

12. Start again Deploy/Review from Action menu, add HP Insight Management Agents
and HP Insight Management WBEM Providers. Then, click the Analysis button.
13. This time, all components should be ready to update (a green mark). Click Deploy.

14. The deployment will start. Go to the Activity screen from the top menu.

15. After a minute, the deployment will complete.
Note
Already up-to-date (not forced) components are skipped.

16. Return to the Nodes screen and in General section for this node, scroll-down to find
and click the View log button.
17. On the installation logs screen, click View log for the installed components.

18. Scroll through the logs and then click the Close button.
The target server is in “green” status.

Summary
In this lab you were updating a target server by using HP SUM in remote target server
online mode. You examined the main HP SUM features, reviewed baselines, added and
discovered nodes.
After examining the inventory and reports, you configured HP SPP deployment, started
HP SUM analysis and made the corrections where needed. Then, you performed the
server update.
Resources
 Websites
• HP Service Pack for ProLiant (HP SPP) home page: http://www.hp.com/go/spp
• Software and drivers from HP Support: http://www.hp.com/go/support
• Documentation for HP SPP: http://www.hp.com/go/spp/documentation
 Documents
• “HP Service Pack for ProLiant User Guide”
• “HP ProLiant and Integrity Firmware Management Best Practices Planning
Guide”

Configuring continuous system monitoring
Lab 8
Objectives
 Describe the functionality of the Agentless Management Service (AMS) on a running
Microsoft Windows server
 Identify key features of the HP System Management Homepage (SMH) and
HP Insight Diagnostics
 Explain how to use the HP Lights-Out Online Configuration (HPONCFG) utility in GUI
mode
 Explain how to use the HPONCFG command line interface (CLI) to configure
HP integrated Lights-Out (iLO)
Requirements
 An installed Windows operating system with HP monitoring tools on a target server
Introduction
The HP iLO Management Engine includes HP Agentless Management, the Active Health
System, Intelligent Provisioning, as well as the traditional remote management and
control capabilities delivered with the new, improved iLO 4 management processor.
HP iLO 4 and Agentless Management are components of the HP ProActive Insight
architecture built into HP ProLiant Gen8 servers. The diagnostic tools, operating system
agents and providers, and HP SMH enable ProLiant servers to be proactively monitored.

Exercise 1—Using the Agentless Management Service

Agentless Management enables you to monitor core hardware and related alerts. In a
traditional agent-based solution, the agent is typically installed on the target host
operating system to collect data. In this solution, the management software operates
within the iLO firmware instead of the host operating system and frees resources on the
host operating system. In addition, monitoring of key subsystems works even without an
installed host operating system, or before one is loaded.
To collect additional operating system data that are outside the scope of iLO 4
monitoring, an optional AMS might be installed in the host operating system. It retrieves
specific host information such as:
 Operating system information
 Host NIC information (IP addresses and Link Up or Down traps)
 Drivers and firmware versions of installed software
 Information about disk drives directly attached to the chipset
The AMS does not require any system management protocol. It communicates directly to
the iLO 4 using the HP iLO Channel Interface. It is part of the HP Service Pack for ProLiant
(HP SPP), which installs AMS by default. It might run concurrently with the operating
system-based management software, but in a production environment it is
recommended to install only one because of the resources that would be used and the
possibility of duplicated alerts.
In this exercise, you will locate the AMS in your target server (host) services and verify
that it is started.

1. Access the iLO and start Remote Console (IRC). Log in to your target server OS as
Administrator using your specified Windows credentials (password: password).
2. After you have logged in, Server Manager is started by default. If it does not start, on
the taskbar at the bottom-left of the screen, click its icon. Select Local Server.

3. In the right pane, scroll down and locate the Services area. Enter HP in the Services
search field to filter the list of all available services and show only HP named.
4. Observe that HP AMS has been installed, and verify that it is Running / Automatic.

5. Enter SNMP in the search field and verify that the Simple Network Management
Protocol (SNMP) Service is also running.
6. Enter agent in the search field and observe which other agents are installed. Then,
close the Server Manager application and access the Windows Server desktop.

Exercise 2—Exploring the HP System Management

Homepage and HP Insight Diagnostics in online mode
The HP System Management Homepage (SMH) enables you to view in-depth hardware
configuration and status data, performance metrics, system thresholds, diagnostics, and
software version control information using a single intuitive interface. For HP ProLiant
servers, the SMH offers similar functionality for Windows and Linux operating systems.
1. On the Windows Server 2012 R2 desktop of your target server, double-click the HP
System Management Homepage.
If you are not on the desktop, but in the Start screen of Windows 2012, type HP in
Search and the installed applications will be filtered. Locate the HP SMH and run it.
Note
The SMH can be also opened from a web browser by entering
https://localhost:2381 in the address field.

2. Skip the Internet Explorer settings. If a certificate issue displays, click Continue to
this website. Select In the future, do not show this warning and click OK.
Note
Internet Explorer might block the access to this site. If asked, add it to the
Trusted sites list by clicking Add → Add and Close.

3. Log in to HP SMH as Administrator and use the password you defined during your
Windows installation (example: password).
4. Verify that your Management Processor is Integrated Lights-Out 4 and the Data
Source is WBEM.

5. The Home screen enables you to quickly determine if your server is having any
hardware issues. A green check mark indicates a healthy component. Components
with issues display in the “Component Status Summary” and their requisite category
with a caution indicator. Example: only one NIC is connected, the others are down.
6. Scroll-down to the System box and click Show All.

7. Review the System box content, then click Memory.
8. In the Board Summary table, click Physical Memory for Processor Board 1.

Question 1: How many memory modules are used, which capacity and speed?
________________________________________________________________
9. Go to the System screen by clicking System in the “breadcrumb trail” navigation.
10. Click Processors.

Question 1: How many memory processors, cores and threads are available?
________________________________________________________________
11. Return to the Home page. Explore items of your choice within the Home tab.

12. Click the Logs tab, then select Integrated management Logs (IML). You already
reviewed IML before, when examining iLO 4 Web Browser Interface.

13. Click the Webapps tab, then HP Insight Diagnostics in the Other Agents area.
14. A new web browser tab opens (click Continue to this website if you are prompted).
HP Insight Diagnostics will be loaded after the system is examined.

You already used Insight Diagnostics in the Perform Maintenance options of

Intelligent Provisioning in the offline mode. Now, you will access it in the online
mode from a running operating system.

15. Examine the options not available in the offline version. For example, clicking Save
at the bottom of the screen enables you to save survey session output to your local
computer (in offline mode it was saved to a USB key only). The Schedule Captures
option enables you to save the configurations on a regular basis, so you might
compare and analyze them.

16. On the Survey tab, select Architecture from the Categories drop-down menu. Scroll
down to discover all of the internal components of the server.

17. Click the Diagnose tab. Select Logical Drive 1 and then click the Diagnose button.
The Status tab becomes active, and displays the results of the test.

18. When you have finished exploring HP Insight Diagnostics, close the web browser and
return to the SMH. Review the remaining menu tabs, Help for example. Exit the SMH
by clicking Sign Out in the upper-right corner. Close the web browser.

Exercise 3—Accessing the iLO using the HP Lights-Out

Online Configuration utility
When performing an assisted operating system installation by means of the Intelligent
Provisioning (for example), or after applying SPP updates, most software (drivers and
utilities) are automatically installed. You might also add them manually, after the
installation of a supported operating system, as a separate step.
One of the tools you might use is the HP Lights Out Online Configuration (HPONCFG)
utility, which is available for both Microsoft Windows and Linux with similar functionality.
HPONCFG enables an administrator to configure local iLO from within the operating
system itself (which means it can be only used online), without accessing the iLO through
the management port with a web browser, which requires the iLO credentials and access
to the management network.
The HPONCFG utility might perform operations by using Remote Insight Board Command
Language (RIBCL) scripts that send commands to the iLO on a local computer. That way,
batch processing is possible, enabling you to run many jobs with prepared scripts in
succession.
For Windows, there is also a graphical user interface (GUI) to use the utility, although it
has fewer capabilities than the scripting language.
In this exercise, you will examine the HPONCFG GUI, review its options, and perform a
reset of the iLO. Because HPONCFG is accessing the iLO from the installed operating
system on the host itself.
1. Access the Start screen on Windows 2012 by moving the cursor to the bottom-left
corner and clicking the Start icon, or by moving the cursor to the top-right or
bottom-right corners and selecting Start from the Charms bar.

2. Start typing HP and the search function will offer lists of the matching applications,
settings, and files. In the Apps list, click HP Lights-Out Online Configuration Utility.
3. At the Integrated Lights-Out Summary screen, notice the information provided for
the iLO of your server.

4. From the menu, select Network → Standard Network Settings. Review the network
configuration but do not make any modifications.
5. Select User from the menu and review the defined iLO users and their properties and
privileges.

6. During previous exercises with the iLO ROM-Based Setup Utility (RBSU) configuration
utility, you created a new user with your nickname (or another term). Select that
user (in this example: test), and click View/Modify. The properties on the right side
of the screen become editable. For this exercise, deselect the Administer User
Accounts privilege and then click Apply.

Saving an iLO configuration

1. From the menu, select Settings → Capture/Restore Configuration.
2. At the File Path field, click Browse. In the dialog box that opens, navigate to the
Desktop, right-click in the right pane, and create a new folder “iLO_Scripts”.

3. Open that folder and create a file named “iLO_Config.xml” to save the iLO
configuration.
4. Click the Capture button to save the configuration to a file, then click OK.
The iLO configuration is now saved in a file. Notice that on the same HPONCFG
screen you have an option to Restore iLO Configuration from a supplied file.
Resetting the iLO chip by using HPONCFG GUI

The next steps enable you to discover what happens to iLO if you use the HPONCFG GUI
tool to do a reset. Sometimes an iLO management chip might become unresponsive or
not working correctly. Using HPONCFG is one method for resetting the chip.
1. To observe what will happen, keep your IRC window with HPONCFG open, and on
your CMS server, access the iLO web interface with your web browser.

2. Return to the IRC window of the target server, and in the HPONCFG menu, select
Summary → Reset iLO/Set to Factory Defaults. Then click the Reset button (do not
click Set to Defaults).
3. Confirm with Yes.

Notice that you will lose the IRC access to the server (it is connected through the iLO
which is resetting), and you will be also logged out of the iLO web browser.
4. Wait approximately one minute and then log in back to the iLO Web Browser
Interface. Click iLO Event Log. Review the last events written in the log.

Exercise 4—Using the HPONCFG utility to configure iLO

by CLI
This exercise introduces you to the concept of the command line interface (CLI).
In addition to the GUI, the HP Lights-Out Online Configuration Utility is also a tool for
communicating with an iLO processor through a CLI. The utility is used in a similar way
across Windows, Linux, and VMware hosts.
The scripting tools provide a method for configuring multiple iLO systems, incorporating
a standard configuration in the deployment process, and controlling servers and
subsystems. For example, using the scripting tools enables you to:
 Change the administrator password on all your iLO systems
 Configure Lightweight Directory Access Protocol (LDAP) directory service settings
 Control the servers power state
 Attach a virtual media CD/DVD to the host server
 Update the iLO firmware
 Retrieve power consumption data
 Issue various configuration and control commands
To use HPONCFG as a scripting tool, you must run it from the command line prompt as an
administrator (or root in Linux) on the host server. The utility reads a provided .xml file
with the commands in the Remote Insight Board Command Language (RIBCL), and
produces a log file with the results.
From the iLO website (a link is provided at the end of this module), you might download
various sample scripts for common tasks, and modify them to suit your needs. You will
also find user guides for scripting.

1. Access the target server again by the Integrated Remote Console through the iLO.
2. Close the HP Lights-Out Online Configuration Utility. Open the iLO_Scripts folder on
your Desktop and right-click the iLO_config.xml file that you created in the previous
exercise. From the menu, select Open with → Notepad.

3. Notice that the generated file is an RIBCL script format. Scroll through the file to
discover the various settings saved in it.
4. Then, select File → New from the Notepad menu to create your own script.

5. The following is an example script. You will find more scripts to be downloaded from
the iLO website referenced at the end of this lab.
Note
Instead of retyping, this script has been made available on your CMS server,
only Copy/Paste is not working in IRC window. So, start Windows Explorer on
the target server and access your CMS at \\192.168.0.1\classfiles. Use your
CMS credentials to open Add_User.xml file in Notepad and then copy it.
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="student" PASSWORD="hp">
<USER_INFO MODE="write">
<ADD_USER
USER_NAME="Test2"
USER_LOGIN="test2"
PASSWORD="password">
<ADMIN_PRIV value ="N"/>
<REMOTE_CONS_PRIV value ="Y"/>
<RESET_SERVER_PRIV value ="N"/>
<VIRTUAL_MEDIA_PRIV value ="N"/>
<CONFIG_ILO_PRIV value="Yes"/>
</ADD_USER>
</USER_INFO>
</LOGIN>
</RIBCL>

6. Notice that the USER_LOGIN and PASSWORD values are iLO credentials in these labs
(verify that they match yours). The script adds a new user to iLO, with the name
“test2” and the password “password” (or you might use your own terms) with
some privileges. The script in Notepad should look like the following screenshot.
7. From the Notepad menu, select File → Save as (or Copy/Paste the file Add_User.xml
from CMS), click Desktop in the left pane, then double-click to open the iLO_Scripts
folder in the right pane. Save the file with the name “Add_User.xml”.

8. To open a Command Prompt window, move your cursor to the top-right (or bottom-
right) corner and select Search from the Charms bar. Enter cmd and the search will
find the Command Prompt application. Click to run it.

9. At the command prompt, enter the following command to add a folder and make the
hponcfg.exe utility visible from any location:
PATH ”c:\program files\hp\hponcfg\hponcfg.exe”;%PATH%
Enter the hponcfg command to verify that it is accessible and to review its syntax.

10. Change the directory to the Desktop\iLO_Scripts folder by entering the command:
cd Desktop\iLO_Scripts
Enter dir to verify that your two .xml files are there.
Type the following command (including the quotes) to check if hponcfg is there and
review the help: ”\Program Files\hp\hponcfg\hponcfg.exe”

11. Now, run your Add_User script by entering the command:

”\Program Files\hp\hponcfg\hponcfg.exe” /f Add_User.xml
(repeat the previously entered line by F3 key or up arrow, then add parameters)
Wait a few seconds the HPONCFG utility to execute the script through the iLO driver.
12. Open the HP Lights-Out Online Configuration Utility GUI again (by moving your
cursor to a right corner to display the Charms bar, searching hp and selecting it). In
the User menu, confirm that a new user is added with the requested privileges.
13. Close all of the running programs and windows in the IRC of your target server, and
then close the IRC.

Summary
In this lab you were accessing the installed Agentless Management Service (AMS) which
helps iLO to collect data from inside Windows OS. You were examining HP System
Management Homepage (SMH) on the host with HP Insight Diagnostics in online mode.
You were using HP Lights-Out Online Configuration (HPONCFG) utility in GUI mode to
examine its features. Then, you created an RIBCL script example, saved to an .XML file
and started HPONCFG utility in command line mode to execute that script.
Resources
 Website
• HP Integrated Lights-Out (iLO) at http://www.hp.com/go/ilo
 Documents
• “HP System Management Homepage User Guide”
• “HP iLO 4 Scripting and Command Line Guide”
• Resources → Support section: “iLO Sample Scripts for Windows”
• “HP Systems Insight Manager Technical Reference Guide”

ProLiant Server Tools and Troubleshooting

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ProLiant Server Tools and Troubleshooting

Hochgeladen von

Copyright:

Verfügbare Formate

ProLiant Server Tools and

Lab 0 — Navigating the HPVL training environment

Rev. 14.21 HP Confidential – For training purposes only i

Lab 4 — Offline systems update with HP SPP boot image

ii HP Confidential – For training purposes only Rev. 14.21

Lab 8 — Configuring continuous system monitoring

Rev. 14.21 HP Confidential – For training purposes only Contents – iii

iv HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L0 – 1

L0 – 2 HP Confidential – For training purposes only Rev. 14.21

Accessing the HP Virtual Lab environment

Rev. 14.21 HP Confidential – For training purposes only L0 – 3

L0 – 4 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L0 – 5

6. In the upper-right menu, click Options.

L0 – 6 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L0 – 7

L0 – 8 HP Confidential – For training purposes only Rev. 14.21

Lab group page

Rev. 14.21 HP Confidential – For training purposes only L0 – 9

After a few seconds, your CMS desktop window appears.

L0 – 10 HP Confidential – For training purposes only Rev. 14.21

Preparing CMS working computer for the labs

Rev. 14.21 HP Confidential – For training purposes only L0 – 11

L0 – 12 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L0 – 13

Exiting the HPVL environment

L0 – 14 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L0 – 15

L0 – 16 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 1

L1 – 2 HP Confidential – For training purposes only Rev. 14.21

Exercise 1—Using key features of the HP iLO 4 Web

Rev. 14.21 HP Confidential – For training purposes only L1 – 3

3. Enter your credentials provided on the HTML Lab Group page.

L1 – 4 HP Confidential – For training purposes only Rev. 14.21

The following settings must be enabled in any browser: JavaScript, cookies,

Rev. 14.21 HP Confidential – For training purposes only L1 – 5

L1 – 6 HP Confidential – For training purposes only Rev. 14.21

6. The Information → Overview screen displays. This screen provides general

Rev. 14.21 HP Confidential – For training purposes only L1 – 7

These options will be explained later.

L1 – 8 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 9

Question 2: How much memory is available? Is it HP SmartMemory certified?

L1 – 10 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 11

L1 – 12 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 13

L1 – 14 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 15

17. Select Information → Diagnostics. This screen describes features for

L1 – 16 HP Confidential – For training purposes only Rev. 14.21

18. Select Information → Location Discovery Services. It is a rack U location discovery

19. Select Information → Insight Agent. As explained, HP Insight Management Agents

Rev. 14.21 HP Confidential – For training purposes only L1 – 17

L1 – 18 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 19

L1 – 20 HP Confidential – For training purposes only Rev. 14.21

Rev. 14.21 HP Confidential – For training purposes only L1 – 21

Rev. 14.21 HP Confidential – For training purposes only L1 – 23

L1 – 24 HP Confidential – For training purposes only Rev. 14.21

27. Select Remote Support → Registration. When automated Remote Support is

Rev. 14.21 HP Confidential – For training purposes only L1 – 25