LG 02jul15 PDF

HP BladeSystem c-Class
Infrastructure
Lab guide
Rev. 15.31
HP Confidential For training purposes only
Use of this material to deliver training without prior written permission from HP is prohibited.
Copyright 2015 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.
Printed in the United States of America
HP BladeSystem c-Class Infrastructure
Lab guide
July 2015
HP Confidential For training purposes only.
Contact HP Education for customer training materials.
Contents
Lab 1Using the HP Power Advisor

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1Installing and using the HP Power Advisor ...................................................... 2
Select a rack .................................................................................................................. 7
Select an enclosure ....................................................................................................... 9
Configure the enclosure.............................................................................................. 11
Install the server blades ............................................................................................. 13
Configure the server blades........................................................................................ 15
Review and save the configuration ............................................................................ 20
Exercise 2Building your HPVL enclosure rack ................................................................ 25
Resources............................................................................................................................ 25
Lab 2Using the Onboard Administrator GUI

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Exercise 1Configuring the HP BladeSystem c7000 enclosure using the Onboard
Administrator ........................................................................................................................ 2
Exercise 2Performing configuration management ....................................................... 18
Saving the enclosure settings .................................................................................... 18
Restoring the enclosure settings ............................................................................... 20
Exercise 3Updating the Onboard Administrator firmware ............................................ 22
Exercise 4Accessing the server blade iLOs through the Onboard Administrator .......... 27
Exercise 5Locating parts information ............................................................................ 30
Exercise 6Using the OA system log ................................................................................ 31
Lab 3Using the Onboard Administrator CLI

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Exercise 1Connecting to the Onboard Administrator CLI using SSH ................................ 2
Exercise 2Updating the Onboard Administrator firmware .............................................. 5
Exercise 3Using the Onboard Administrator CLI .............................................................. 9
Exercise 4Saving the Onboard Administrator configuration to an FTP/TFTP server
(optional) ............................................................................................................................ 19
Exercise 5Restoring the Onboard Administrator configuration from an FTP/TFTP
server (optional) ................................................................................................................. 21
Rev. 15.31
Lab 4Using the Insight Display

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
c7000 enclosure configuration..................................................................................... 1
c3000 enclosure configuration (provided for reference only) ..................................... 2
Introduction .......................................................................................................................... 2
Exercise 1Accessing the HP BladeSystem c-Class Insight Display .................................. 3
Accessing the Insight Display directly .......................................................................... 3
Accessing the Insight Display through the Onboard Administrator ............................ 3
Exercise 2Navigating the Insight Display ......................................................................... 7
Using the navigation buttons ....................................................................................... 7
Using the Main Menu Help............................................................................................. 8
Exercise 3Using the Insight Display Main Menu options .................................................. 9
Setting the Enclosure UID on ........................................................................................ 9
Using the Health Summary screen ............................................................................. 10
Setting the Enclosure UID off ..................................................................................... 11
Accessing the Enclosure Info screen .......................................................................... 12
Accessing the Blade or Port Info screen ..................................................................... 14
Changing the User Note screen (optional).................................................................. 16
Using the USB Key Menu options ................................................................................ 18
Updating the OA firmware .................................................................................. 18
Saving a configuration to a USB device .............................................................. 22
Restoring a configuration from a USB device ..................................................... 24
Using the Health Summary screen during an error or alert condition (paper-based
exercise) ...................................................................................................................... 25
Lab 5HP BladeSystem c-Class Port Mapping for the c7000 Enclosure
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Exercise 1Exploring port mapping for half-height server blades in the c7000 enclosure
............................................................................................................................................... 2
Exercise 2Exploring port mapping for full-height server blades in the c7000 enclosure
(paper-based exercise) ....................................................................................................... 10
AppendixAnswers ........................................................................................................... 14
Exercise 1 .................................................................................................................... 14
Exercise 2 .................................................................................................................... 15
Lab 6Installing and configuring the HP ProCurve 6120 Blade Switch

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 2
Exercise 1Accessing the HP ProCurve 6120 Switch ......................................................... 3
Management interfaces and user access (privilege) levels ......................................... 3
Accessing the Web Browser Interface .......................................................................... 6
Accessing the Web Browser Interface directly through the web browser ........... 6
Accessing the Web Browser Interface through the Onboard Administrator GUI . 9
Accessing the CLI through a Telnet connection.......................................................... 12
Exercise 2Backing up and restoring the switch configuration....................................... 14
ii
Rev. 15.31
Contents
Exercise 3Configuring the HP ProCurve 6120 Blade Switch .......................................... 19

Overview of the running-config and startup-config files .......................................... 19
Viewing the current configuration files ...................................................................... 20
Using the CLI to reconfigure the switch ...................................................................... 24
Specifying the software (firmware image) and configuration file to use when booting
the switch .................................................................................................................... 27
Exercise 4Restoring the switch to factory default settings........................................... 30
Exercise 5Flashing the switch firmware......................................................................... 31
Lab 7Virtual Connect

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Exercise 1Viewing the Virtual Connect domain configuration ......................................... 2
Connecting to the VCM GUI ........................................................................................... 2
Examining the networks and their assigned uplink ports............................................ 5
Exercise 2Assigning, unassigning, and moving server profiles ....................................... 8
Exercise 3Backing up the Virtual Connect configuration ............................................... 21
Exercise 4Restoring the Virtual Connect configuration ................................................. 24
Exercise 5Using the Virtual Connect Support Utility ...................................................... 27
Exercise 6Updating the Virtual Connect firmware ......................................................... 34
Exercise 7Resetting the Virtual Connect Manager ......................................................... 36
Exercise 8Copying server profiles .................................................................................. 39
Additional information on Virtual Connect......................................................................... 42
Lab 8Installing and configuring the Brocade 4Gb/8Gb SAN Switch

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 2
Exercise 1Accessing and configuring the Brocade 4Gb/8Gb SAN Switch ........................ 3
Accessing the switch using a Telnet connection .......................................................... 3
Setting the IP address ................................................................................................... 8
Backing up the switch configuration .......................................................................... 10
Restoring switch configuration from backup ............................................................. 13
Exercise 2Maintaining the Brocade 4Gb/8Gb SAN switch .............................................. 15
Accessing the Brocade SwitchExplorer interface ....................................................... 15
Flashing the switch firmware using the Brocade SwitchExplorer ............................. 18
Flashing the switch firmware using CLI (for your reference only) ............................. 24
Resetting the switch factory-default settings ........................................................... 25
Rev. 15.31
iii
Lab 9HP BladeSystem c-Class Enclosure-Based USB Devices

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 2
Exercise 1Accessing and using the enclosure-based USB device with the Onboard
Administrator GUI ................................................................................................................. 3
Exercise 2 Accessing and using the enclosure-based USB device with the Insight
Display (optional).................................................................................................................. 8
Lab 10Using the HP Service Pack for ProLiant

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Verifying the DHCP service ........................................................................................... 2
Exercise 1Using the HP Service Pack for ProLiant remotely............................................ 4
Using the GUI to update firmware ................................................................................ 4
Using the GUI to update software ............................................................................... 18
Using the CLI command line ........................................................................................ 28
Using the CLI input file (optional) ............................................................................... 30
Exercise 2Using the HP Service Pack for ProLiant from USB in the offline mode ......... 31
Attaching the ISO image to the server blade using the Onboard Administrator GUI
..................................................................................................................................... 31
Using the HP Service Pack for ProLiant in the interactive mode................................ 35
Using the HP Service Pack for ProLiant in the automatic (unattended) mode .......... 40
Exercise 3Using the HP Service Pack for ProLiant locally in the online mode............... 43
Lab 11Reinstalling HP Intelligent Provisioning

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
ExerciseReinstalling HP Intelligent Provisioning ............................................................. 2
Lab 12Installing Microsoft Windows Server 2012 R2 with HP Intelligent

Provisioning
Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
ExerciseInstalling Microsoft Windows Server 2012 using HP Intelligent Provisioning ... 2
Resources............................................................................................................................ 17
Lab 13 Using the HP ProLiant Gen9 servers UEFI tools

Objectives.............................................................................................................................. 1
Requirements ....................................................................................................................... 1
Introduction .......................................................................................................................... 1
Exercise 1Accessing and examining the UEFI ROM .......................................................... 3
Exercise 2Accessing and using the UEFI shell interface ................................................ 12
Exercise 3Enabling and using the flash memory partition ............................................ 15
Resources............................................................................................................................ 24
iv
Rev. 15.31
Contents
AppendixClassroom Configuration Guide

Introduction .......................................................................................................................... 1
Table of contents .................................................................................................................. 1
Classroom configuration ...................................................................................................... 2
Team stations and lab equipment configuration ................................................................. 3
Equipment assignments ............................................................................................... 3
Labgroup details ................................................................................................... 3
Interconnects ................................................................................................................ 4
Device bays and iLO addresses ..................................................................................... 4
User accounts and passwords ...................................................................................... 5
Onboard Administrator ................................................................................................. 5
Network cabling ............................................................................................................ 5
Network definitions ...................................................................................................... 5
DHCP .............................................................................................................................. 6
FTP................................................................................................................................. 6
Telnet/SSH .................................................................................................................... 6
Software location.......................................................................................................... 6
HP Virtual Labs (HPVL) specific instructions ........................................................................ 7
Learner-specific information ........................................................................................ 7
Prerequisites ................................................................................................................. 7
Accessing the HPVL environment ................................................................................. 8
Connecting to the enclosure Onboard Administrator ................................................ 15
Connecting to the server blade iLOs ........................................................................... 17
Exiting HPVL ................................................................................................................ 19
Rev. 15.31
vi
Rev. 15.31
Using the HP Power Advisor

Lab 1
Objectives
After completing this lab, you should be able to:
Explain how to configure an HP BladeSystem c-Class enclosure using the HP Power

Advisor
Describe how to build an HP Virtual Lab (HPVL) enclosure rack
Requirements
To complete this lab, you will need:
A supported Internet browser
Internet access to the HP website or Internet access to the HP Virtual Lab equipment
Note
This lab is optional and it can be executed on your PC at any time. It cannot be
executed in the HPVL environment (no Internet access policy).
Introduction
The HP Power Advisor is a tool provided by HP to assist in the estimation of power
consumption and in the proper selection of components such as power supplies at the
system, rack, and multi-rack levels. Additional features of the tool include a condensed
bill of materials, a cost of ownership calculator, and a power report.
HP Power Advisor version 6.x includes the new HP ProLiant Gen 9 servers and options as
well as a new Smart Update feature that automatically updates your application when
opened.
Note
The Smart Update feature requires Internet access, which is not available in
the HPVL environment.
The Power Advisor website is http://www.hp.com/go/hppoweradvisor.
Note
Screenshots and IP addresses in this lab document are for your reference and
might differ slightly from the ones you will see on your screen during these
HPVL lab exercises. Always refer to your HPVL login page for your assigned IP
address or server bay number.
Rev. 15.31
L1 1
Exercise 1Installing and using the HP Power Advisor

In this exercise, you will install the HP Power Advisor utility on your CMS server. You can
choose to complete this lab on your local computer instead.
Note
There is also an online version of HP Power Advisor at website

https://paonline56.itcs.hp.com/.
The Power Advisor installation executable can be downloaded from
http://sizers.houston.hp.com/sb/installs/HPPowerAdvisor.zip.
After the installation, you will run the utility and follow these procedure steps:
Select a rack
Select an enclosure
Configure the enclosure
Install the server blades
Configure the server blades
Review and save the configuration
Important
If you download and install the HP Power Advisor locally, you must enable
Adobe AIR. See the HP Power Advisor Download and Installation Guide for
instructions.
The HP Power Advisor installation executable has been downloaded to your CMS server.
L1 2
1.
Access the HPVL environment and log into your CMS server.
2.
Start Windows File Explorer and execute as administrator HPPowerAdvisor.exe ,

which is in the C:\classfiles\Power Advisor folder, to begin the installation.
Rev. 15.31
Rev. 15.31
3.
At the Welcome screen, click Next.
4.
At the License Agreement screen, accept the agreement and click Next.
L1 3
L1 4
5.
Accept the default customer information and click Next.
6.
Accept the default destination folder and click Next.
Rev. 15.31
Rev. 15.31
7.
Click Install and after the installation.
8.
Click Finish to close the wizard.
9.
Double-click the icon created on the CMS desktop to start the Power Advisor
application.
L1 5
10. Enter your profile information (if asked) and click OK to continue. For the purposes of
this lab, you can enter any name and email address.
11. The main Power Advisor screen displays. Select your data center input power
voltage and click Go.
L1 6
Rev. 15.31
Select a rack
To begin the process, select a rack on the left side of the screen, enter the information
needed, and click OK.
Note
Notice the options at the lower left of the screen, which enable you to select
enclosures.
Rev. 15.31
L1 7
The rack displays in the working area, with its height in U.

Note
The U measurement for racks refers to rack units, where 1U = 1.75 in. or
44.45 mm.
L1 8
Rev. 15.31
Select an enclosure
1.
Rev. 15.31
Click Enclosures on the left side of the screen and click an available c7000 enclosure
to add to the rack.
L1 9
2.
L1 10
Click the enclosure to highlight it (a green border displays) and then click the Config
button on the right side of the screen to configure the selected device.
Rev. 15.31
Configure the enclosure

1.
Rev. 15.31
When the Configure C7000 Enclosure menu displays, click Config.
L1 11
2.
Configure the enclosure components:
Power supply
Click the Add button to add the required number and type of power
supplies. For N+N power redundancy, the number must be even.
General configuration:
Select the number of cooling fans (notice the Minimum Fans limit)
Select the power phase and power redundancy settings
Select Redundant Onboard Administrators (OAs)
Interconnects:
Select the interconnects used in the enclosure
After the configuration is finished, click Save.
L1 12
Rev. 15.31
Install the server blades

1.
Rev. 15.31
The servers are available in the panel on the left side of the screen. Click the server
you want to populate in the enclosure. By default, you can configure the enclosure
with individual servers. For this exercise, select Make All Bays same as 1 to replicate
the selected server in all bays.
L1 13
2.
L1 14
This example has all device bays populated with the HP ProLiant BL460c Gen8
servers. Click Save.
Rev. 15.31
Configure the server blades

1.
Rev. 15.31
Click Config to return to the Configuration screen.
L1 15
2.
L1 16
Highlight the first server (in Bay 1) and click Config.
Rev. 15.31
3.
Rev. 15.31
Select the appropriate processors (CPU), memory, storage, and available ports
settings on the left side of the screen. Notice that the allowed quantities depend on
the type of server. Review the selected options on the right side of the screen and
click Save.
L1 17
4.
L1 18
Click Save again.
Rev. 15.31
5.
Rev. 15.31
You can save the configuration to your CMS desktop; otherwise, after you exit, your
configuration will be lost and you will have to start over. Click the Save button beside
Report at the top of the screen. Saved configurations can be loaded later.
L1 19
Review and save the configuration

1.
L1 20
Click the Power Report tab and enter the approximate costs and lifecycle. Select the
Total Cost of Ownership option to see the complete costs and then click the
Generate Report button.
Rev. 15.31
2.
Rev. 15.31
Export the generated report as HTML and save the file to your desktop.
L1 21
3.
L1 22
Generate a Bill of Materials (BOM) by clicking the BOM tab and then Generate BOM.
Rev. 15.31
4.
Rev. 15.31
After the report is generated, click Export BOM and save the file in HTML format (for
example) to your desktop.
L1 23
5.
L1 24
Close the HP Power Advisor utility by clicking the X in the upper right corner.
Examine the saved reports on the desktop by double-clicking them to open them in
a web browser.
Rev. 15.31
Exercise 2Building your HPVL enclosure rack

Working with the skills you gained in the preceding exercise, build a configuration that
looks exactly like your enclosure in HPVL. Use the Power Advisor results and then
compare them to the power reports provided by the OA.
Resources
For more information, refer to the following resources:
Rev. 15.31
WebsitesHP Power Advisor homepage at

http://www.hp.com/go/HPPowerAdvisor
Documentstechnical white paper, HP Power Advisor, available at the HP Power
Advisor homepage
L1 25
L1 26
Rev. 15.31
Using the Onboard Administrator GUI

Lab 2
Objectives
Configure the HP BladeSystem c7000 enclosure using the Onboard Administrator
Perform configuration management
Update the Onboard Administrator firmware
Access the server blade iLOs through the Onboard Administrator
Locate parts information
Use the OA system log
Requirements
To complete this lab, you will need one management server (CMS) and one c7000
enclosure with these components:
Power supplies installed in the correct power supply bays
Cooling fans installed in the correct fan bays
One or more half-height server blades
One or more full-height server blades
At least one Onboard Administrator module with current version of the firmware
One Ethernet interconnect
Additionally, you need the Classroom Configuration Guide.

Note
The Classroom Configuration Guide provides the environment and login

information necessary to execute this lab.
Screenshots in this lab document are for your reference and might slightly
differ from the ones you will see during execution of these HPVL lab
exercises.
The HP BladeSystem Onboard Administrator User Guide is available at the HP
BladeSystem Technical Resources page. Refer to
http://www.hp.com/go/bladesystem/documentation website for more
information.
Rev. 15.31
L2 1
Exercise 1Configuring the HP BladeSystem c7000

enclosure using the Onboard Administrator
In this exercise, you will configure the c7000 enclosure and its Onboard Administrator
using the Onboard Administrator First Time Setup Wizard.
Note
To use the Onboard Administrator, you need to first configure it. When you
log in to the Onboard Administrator GUI for the first time, the First Time
Setup Wizard will display. However, the wizard will only display on the initial
configuration of the Onboard Administrator. To manually launch the wizard
for an enclosure with an already configured Onboard Administrator, click the
Wizards link in the Onboard Administrator GUI homepage.
To configure the BladeSystem c7000 enclosure using the Onboard Administrator First
Time Setup Wizard:
1.
If necessary, log into your CMS with administrative credentials.
2.
Open your browser and log into the Onboard Administrator GUI with administrative
credentials. Ignore any security warnings.
Note
Refer to the Classroom Configuration Guide for the IP address of the Onboard
Administrator and the administrative credentials.
The Onboard Administrator ships with a toe tag that contains login
information. If you are setting up the Onboard Administrator for a new
enclosure for the first time, use the information from this tag.
L2 2
Rev. 15.31
3.
Important
The default user and password are embedded in the firmware and do not
change if the enclosure settings are reset to factory defaults.
Depending on the state of the Onboard Administrator, either the Onboard

Administrator homepage displays (if the OA module has already been configured) or
the First Time Setup Wizard displays (if the OA module is still unconfigured).
If necessary, click Wizards o First Time Setup to launch the First Time Setup
Wizard.
Rev. 15.31
L2 3
L2 4
4.
At the Welcome screen, click Next.
5.
Leave the FIPS Mode OFF, scroll-down and click Next at the bottom.
Rev. 15.31
Rev. 15.31
6.
At the Enclosure Selection screen, click Next.
7.
Using the Onboard Administrator GUI, you can save configuration scripts and
replicate settings to other enclosures in the same rack. Because no configuration
scripts for this environment have been saved, leave the fields blank, and click Skip.
L2 5
8.
The Rack and Enclosure Settings screen enables you to update the Rack Name,
Enclosure Name, and Asset Tag. Review the information on the screen and click Skip.
Note
When performing this exercise outside the classroom, ensure that the value
for the Asset Tag field does not have any space.
9.
L2 6
At the Administrator Account Setup screen, leave the fields blank in both sections
and click Next.
Rev. 15.31
WARNING
Do not enable PIN protection as it may cause issues later in the lab execution.
10. At the Local User Accounts screen, you have three buttons:
Newopens the User Settings screen, allowing you to add a new user to the
selected enclosure.
Editopens the User Settings screen, allowing you to change the settings for
the selected user.
Deleteremoves the accounts. If you attempt to delete the last remaining

Administrator account, a warning displays stating that one Administrator
account must remain and the delete action is canceled.
Click New to display the User Settings screen.
Rev. 15.31
L2 7
11. At the User Settings screen, add a new user with username student01 and
password password) with Administrator privileges. If student01 already exists,
delete that account first. Select the User Enabled and Onboard Administrator Bays
checkboxes to give the new user full permissions within all Onboard Administrators,
devices, and interconnect bays. Then, click Add User at the bottom of the screen.
12. The Local User Accounts screen should display the new user. Click Next.
L2 8
Rev. 15.31
13. The server blade iLO ports and interconnect module management ports can obtain
IP addresses on the management network in three ways:
DHCP address
Static IP address
Enclosure Bay IP Addressing (EBIPA)
When a server blade or interconnect module is inserted into a bay that has
Enclosure Bay IP Addressing (EBIPA) enabled, that iLO or Interconnect management
port will get the specific IP address from the Onboard Administrator if that device is
configured for DHCP.
Note
If the component is configured for a static IP address, an EBIPA assignment to

that bay will have no effect.
At the EBIPA, click Next.
Rev. 15.31
L2 9
14. By selecting checkboxes, you are enabling the Enclosure Bay IP Addressing (IPv4 and
IPv6) for Server Bay iLO Processors and Interconnect modules in this enclosure.
Review the EBIPA configuration and click Skip, and Skip again for IPv6 addressing.
Note
The administrator sets an independent range for server blade bays and
interconnect module bays. The first address in a range is assigned to the first
bay and then to consecutive bays through the range.
L2 10
Rev. 15.31
15. Access to enclosures can be controlled by LDAP groups in addition to local accounts.
For this exercise, do NOT change any setting and click Skip to continue configuring
the enclosure.
Note
When performing this exercise outside of this classroom, if you want to

create LDAP groups, click Next at the Directory Groups screen.
Rev. 15.31
L2 11
16. Because you did not create any LDAP groups in the previous step, click Skip at the
Directory Settings screen to continue configuring the enclosure.
L2 12
Rev. 15.31
17. The default Onboard Administrator network setting is Use DHCP for all
Active/Standby Onboard Administrators. In this HPVL environment, the Active
Onboard Administrator Network Settings option is set to use static IP settings. Click
Skip to continue configuring the enclosure.
WARNING
Do NOT change the network settings for the Onboard Administratorthe

network settings have already been configured using static IP addresses.
Changing this information may disable access to the Onboard Administrator
and will delay the lab progress for everyone in the labgroup until resolved.
Rev. 15.31
L2 13
18. Input the values for the SNMP Settings:

Note
You may skip this step if HP SIM is not part of your environment.
System Location: c-Class Training
System Contact: Joe User
Read Community: public
Write Community: private
Engine ID String do not change
Add the SNMP Alert Destinations (if not present):
IP Address: 192.168.200.x (IP address of your DL360 server)
Click Next to accept the new settings or Skip if no settings were changed.
L2 14
Rev. 15.31
19. At the Power Management screen, review the power management options available
for your enclosure. Do NOT change any setting unless requested by your instructor.
Verify that the Power Mode is set to AC Redundant. Click Skip at the bottom.
Note
When performing this lab outside the classroom, always choose a power
management option that maximizes the available redundancy of your
enclosure.
Rev. 15.31
L2 15
Note
The Dynamic Power mode automatically places unused power supplies in the
standby mode to increase enclosure power supply efficiency, thereby
minimizing enclosure power consumption during lower power demand.
Increased power demands automatically return standby power supplies to
full performance.
20. At the Finish screen, click Finish.
L2 16
Rev. 15.31
The Rack Overview page displays, similar to the screenshot below.
Rev. 15.31
L2 17
Exercise 2Performing configuration management

In this exercise, you will perform the enclosure configuration management using the
Onboard Administrator GUI. Specifically, you will save and restore the enclosure settings
from a saved configuration file.
Saving the enclosure settings

The Configuration Scripts screen of the Onboard Administrator GUI enables you to save
the enclosure configuration in a file. You can then use that file to automate enclosure
configuration.
To save the enclosure settings in a file on a USB key plugged into the Onboard
Administrator module:
1.
Your Onboard Administrator module has a USB key inserted. At the Onboard
Administrator GUI, in the Systems and Devices pane, expand Enclosure Information
o Enclosure Settings and click Configuration Scripts.
Note
If the USB key is not attached, ask HPVL support to check and insert the key.
L2 18
Rev. 15.31
Rev. 15.31
2.
Scroll down to the Save Configuration section and type MyEnclosure.cfg in the
File Name field. The filename provided must not contain any spaces and it must have
a .cfg extension. Click Apply to save the enclosure configuration on the USB key. This
can take around 5 minutes and you may not get the pop-up when this operation is
completed.
3.
At the Message from webpage screen, click OK.
L2 19
Restoring the enclosure settings

To set up a selected enclosure using a saved configuration file:
1.
If necessary, at the Onboard Administrator GUI, in the Systems and Devices pane,
expand Enclosure Information o Enclosure Settings and click Configuration
Scripts.
2.
At the Configuration Management screen, you have these options:

a.
Local fileBrowse to the configuration file or enter the path of the

configuration file into the textbox. The maximum number of characters in the
file path is 256. Click Upload after entering the file path or after browsing.
b.
URLEnter the http:// path to the configuration file if it is located on a web

server. The maximum number of characters in the file path is 256.
Click Apply after entering the URL.
c.
USB FileSelect the previously saved configuration file that is stored on a USB
key inserted into the Onboard Administrator module.
Use the USB File option and load the MyEnclosure.cfg file by clicking Apply.
L2 20
Rev. 15.31
The Onboard Administrator GUI displays the following message and applies the
saved configuration. It might take a couple of minutes.
When completed, the Onboard Administrator GUI returns to the Configuration

Results screen.
Rev. 15.31
L2 21
Exercise 3Updating the Onboard Administrator

firmware
In this exercise, you will update the Onboard Administrator firmware using the OA GUI.
Make sure the Pop Up blocker in your browser is turned off before starting this exercise.
It is in the Internet Options menu of your browser.
L2 22
Rev. 15.31
To flash the Onboard Administrator firmware:
Rev. 15.31
1.
In the Systems and Devices pane, expand Enclosure Information o Active Onboard
Administrator and select Firmware Update.
2.
Scroll down to the Local File section and click the Browse button,.
L2 23
L2 24
3.
Browse to the C:\classfiles\Firmware\OA folder, select the hpoa440.bin file, and

click Open.
4.
After selecting, click Upload to begin the upload process.
Rev. 15.31
5.
At the Message from webpage screen, click OK. Notice that you will lose OA
connections during update.
The Onboard Administrator displays the type of activity and its progress.
Note
The flashing process updates both the active and the standby Onboard
Administrator modules. The standby module is updated and reset first,
followed by the active module.
This process might take up to 10 minutes.
Rev. 15.31
L2 25
When the operation completes, the Onboard Administrator modules reset.
Your OA GUI session will reset as well and you will return to the OA GUI login screen.
Note
Updating OA firmware might result in problems accessing the OA GUI from

your browser. If you are experiencing such problems, clear your browsing
history by using the Tools o Internet Options o General or Tools o Delete
Browsing History in Internet Explorer (depending on the version of Internet
Explorer).
L2 26
Rev. 15.31
Exercise 4Accessing the server blade iLOs through

the Onboard Administrator
In this exercise, you will access the server blade iLOs using the Onboard Administrator
GUI.
To do so:
Rev. 15.31
1.
If not connected, access the Onboard Administrator GUI and log in with
administrative credentials.
2.
In the Systems and Devices panel, expand Enclosure Information o Device Bays o
<#. Server Blade> o iLO. If the selected Server Blade is G7 model, you will access
iLO 3. If the Server Blade is Gen8 or Gen9, you will access iLO 4.
L2 27
3.
At the iLO Device Bay # screen, select Web Administration. A new tab in web
browser will open. Ignore any security warnings and continue.
Note
If you are logged into the Onboard Administrator with administrative

credentials, the Onboard Administrator automatically connects you to the iLO
management port without a need to enter iLO credentials.
L2 28
Rev. 15.31
The iLO Overview page displays.
4.
Rev. 15.31
Click Sign Out at the top right corner and close the iLO window.
L2 29
Exercise 5Locating parts information

In this exercise, you will retrieve the part number and serial number information from
several HP BladeSystem c-Class enclosure components using the Onboard Administrator
GUI.
To locate the enclosure parts information:
1.
Use the Onboard Administrator GUI to find a power supply and record its serial
number, part number, and spare part number so that a spare can be ordered. Record
the information here.
Serial Number: .................................................................................................................
Part Number: ...................................................................................................................
Spare Part Number: .........................................................................................................
2.
Record these details about the specific interconnect devices:

Interconnect bay number 1
Product Name: .................................................................................................................
Part Number: ...................................................................................................................
Serial Number: .................................................................................................................
Product Name: .................................................................................................................
Part Number: ...................................................................................................................
Serial Number: .................................................................................................................
Product Name: .................................................................................................................
Part Number: ...................................................................................................................
Serial Number: .................................................................................................................
L2 30
Rev. 15.31
Exercise 6Using the OA system log

To use the Onboard Administrator system log:
1.
At the Onboard Administrator GUI, in the Systems and Devices pane (on the left),
expand Active Onboard Administrator and click System Log.
The System Log displays logged information of events within the Onboard
Administrator. Events are logged from the top of the list to the bottom, with the
most recent logged event appearing at the top of the list. The system log can be
scrolled utilizing the scroll bar on the right side of the log screen (if the log is larger
than the display box).
Note
The log has a maximum capacity of 18.42 KB and automatically deletes the
oldest logged event first (first in, first out).
Rev. 15.31
L2 31
2.
L2 32
Review the system log, notice the Clear Log button but do not clear the list.
Rev. 15.31
3.
Rev. 15.31
Select the Log Options tab. On this tab, you can enable remote system logging,
which is a feature that can be used to send Onboard Administrator syslog messages
to a remote server on the network for persistent storage. The syslog messages are
sent from Onboard Administrator using the UDP protocol on a port that can be
specified by the user. The default remote syslog port is 514. Leave remote system
logging disabled (unchecked).
L2 33
L2 34
Rev. 15.31
Using the Onboard Administrator CLI

Lab 3
Objectives
Connect to the Onboard Administrator CLI using Telnet
Update the Onboard Administrator firmware
Use the Onboard Administrator command line interface (CLI) to retrieve and change
the Onboard Administrator configuration
Save the Onboard Administrator configuration to an FTP/TFTP server (optional)
Restore the Onboard Administrator configuration from an FTP/TFTP server
(optional)
Requirements
Additionally, you need an FTP/TFTP server running on the same network as the Onboard
Administrator module and the Classroom Configuration Guide.
Note

Images from this lab document are for your reference and might slightly
exercises.
The HP BladeSystem Onboard Administrator User Guide is available at the HP
BladeSystem Technical Resources page. Refer to
http://www.hp.com/go/bladesystem/documentation website for more
information.
Rev. 15.31
L3 1
Exercise 1Connecting to the Onboard Administrator

CLI using SSH
In this exercise, you will connect to the Onboard Administrator command-line interface
using SSH.
To connect to the OA module using a SSH connection:
1.
2.
At your CMS, launch PuTTY using the desktop shortcut or from the Start menu.
3.
Select SSH for the connection type to connect to the Onboard Administrator CLI. In
the Host Name field, type <OA IP address> (for example, 192.168.200.100),
keep the Port configuration unchanged (Port 22), and click Open.
Note
Refer to the Classroom Configuration Guide for the IP address of the OA.
L3 2
Rev. 15.31
4.
If the PuTTY Security Alert screen appears, click Yes to continue. This dialog will
appear the first time you are accessing the OA from your CMS.
5.
At the login prompt, enter the administrative credentials (for example,

Administrator/password) and press Enter to log in.
Note
There is no echo while typing a password.
Rev. 15.31
L3 3
6.
At the prompt, type SET SESSION TIMEOUT 1400 and press Enter to increase
your session timeout from its default value of 60 seconds.
Note
Onboard Administrator commands are not case sensitive (except for user
names).
L3 4
Rev. 15.31
Exercise 2Updating the Onboard Administrator

firmware
In this exercise, you will use the Onboard Administrator command-line interface and an
FTP/TFTP server to update the Onboard Administrator firmware.
Complete these steps:
1.
Using Windows Explorer, copy the hpoa440.bin file (the Onboard Administrator
firmware file) from the C:\Classfiles\Firmware\OA folder to the C:\ftproot folder.
This action makes the firmware file available on the FTP/TFTP server.
2.
If not logged in, log into the Onboard Administrator CLI with administrative
credentials.
3.
At the prompt, you may enter:

update image ftp://<FTP_username>:<FTP_password>@<IP
address of FTP server>/hpoa440.bin
Or, if the firmware is current and you wish to overwrite it, use the FORCE parameter:
update image force ftp://<FTP_username>:<FTP_password>@<IP
address of FTP server>/hpoa440.bin
Use the anonymous user name without a password for this exercise. Press Enter.
Example
This example uses the anonymous ftp user account with no password (the FTP
server IP address might differ):
update image ftp://anonymous:@192.168.200.1/hpoa440.bin
or
update image force
ftp://anonymous:@192.168.200.1/hpoa440.bin
Note
If a redundant Onboard Administrator module is present, this command will

flash and validate its firmware before attempting to flash the active Onboard
Administrator firmware.
HTTP and File Transfer Protocol (FTP) can be also used for this upgrade.
Rev. 15.31
L3 5
The flashing process begins with the Standby Onboard Administrator and displays
its progress.
Note
If you used the FORCE parameter, at the Are you sure you want to downgrade
the firmware prompt, type yes and press Enter.
L3 6
Rev. 15.31
The flashing process continues with the Active Onboard Administrator.
When the flashing process completes, you will be disconnected from the Onboard
Administrator CLI.
Rev. 15.31
L3 7
4.
Wait a couple of minutes, start PuTTY again and log back in with administrative
credentials as before.
5.
At the prompt, type show oa info and press Enter. This command displays the
active Onboard Administrator information. What is the firmware version of the active
Onboard Administrator?
..........................................................................................................................................
6.
At the prompt, type show oa info all and press Enter. What type of information
is displayed? (Scroll up if necessary.)
..........................................................................................................................................
L3 8
Rev. 15.31
Exercise 3Using the Onboard Administrator CLI

In this exercise, you will use the Onboard Administrator command-line interface
commands to obtain help, to retrieve current enclosure settings, and to manipulate the
enclosure settings.
Complete these steps:
1.
If necessary, log into the Onboard Administrator CLI with administrative credentials.
2.
To get the list of available commands, type help and press Enter.
Note
To see the current parameters, use the show command. To change the
settings, use the set command.
Rev. 15.31
L3 9
3.
To see the current configuration, type show config and press Enter. Press the
space bar to continue scrolling through the information, or q to quit.
4.
Type show rack name and press Enter to display the name of the rack that was set
by the Onboard Administrator First Time Configuration Wizard.
Note
The rack names might differ depending on your lab group.
L3 10
Rev. 15.31
5.
Rev. 15.31
Type show enclosure status to check the enclosure status. Press the space bar
to scroll to the bottom of the information.
L3 11
L3 12
6.
To display the enclosure information, including its current name, type show
enclosure info and press Enter.
7.
To name the enclosure, type set enclosure name <new enclosure name> and
press Enter. Use the existing enclosure name for the new name.
Rev. 15.31
Rev. 15.31
8.
To change the redundancy mode to Not Redundant, you would type set power mode
powersupply and press Enter.
9.
All commands have many parameters and you can always use the help option to get
more detailed information for each command. For example:
a.
help set
b.
help show
L3 13
10. To view the status of all server blades installed in the enclosure, type show server
status all and press Enter.
Note
To view the status of a specific server blade, type show server status
<bay number> and press Enter.
L3 14
Rev. 15.31
11. To view the temperature of the CPUs and memory in all installed server blades, type
show server temp all and press Enter.
Note
To view the temperature of a specific server blade, enter show server

temp <bay number> and press Enter.
12. To view the serial number of a specific server blade, type show device
serial_number blade <bay number> and press Enter.
Rev. 15.31
L3 15
13. To view which users have serial console sessions in progress for each interconnect,
enter show interconnect sessions and press Enter.
14. To view the information about and current status of the specified enclosure fan, type
show enclosure fan <fan number> and press Enter.
L3 16
Rev. 15.31
15. To view the complete enclosure information, type show enclosure info and press
Enter.
16. To view the complete information about the installed power supplies, type show
enclosure powersupply all and press Enter.
Note
To view the information for a specific power supply, enter show enclosure
powersupply <bay number> and press Enter.
Rev. 15.31
L3 17
17. To view the status of the installed Onboard Administrator modules, type show oa
status all and press Enter.
L3 18
Rev. 15.31
Exercise 4Saving the Onboard Administrator

configuration to an FTP/TFTP server (optional)
In this exercise, you will learn how to use the Onboard Administrator CLI to save the
current runtime configuration of the OA with UPLOAD CONFIG command to your FTP
server.
Syntax of the command is:
UPLOAD CONFIG {"<url>" | USB "<filename>"}
Access level needed to run UPLOAD CONFIG command is OA Administrator.
UPLOAD CONFIG command uploads a script to the specified URL which duplicates the
current OA runtime configuration. Supported protocols are FTP, TFTP, and USB. The URL
should be formatted as: protocol://host/path/filename. If your FTP server
does not support anonymous logins, you can specify a user name and password within
the URL formatted as: ftp://username:password@host/path/filename. To
save a configuration file to a USB key, use the USB command and provide a filename.
1.
From the PuTTY, SSH, or Telnet session, type:

upload config ftp://192.168.200.1/oa/MyOAConfig.txt
This command used the anonymous FTP account for its execution and saved the
current OA configuration to the C:\ftproot\OA folder. You can also use the
Administrator FTP user account, with credentials Administrator/password,
to execute the upload config command, and the results are the same. Syntax with
the Administrator FTP account would be:
upload config
ftp://Administrator:password@192.168.200.1/oa/MyOAConfig.
txt
Rev. 15.31
L3 19
2.
L3 20
Use a Linux-compatible editor such as AB-Edit or WordPad editor to view the

MyOAConfig.txt file stored in the C:\ftproot\OA folder.
Rev. 15.31
Exercise 5Restoring the Onboard Administrator

configuration from an FTP/TFTP server (optional)
In this exercise, you will learn how to use the Onboard Administrator CLI to restore the
configuration uploaded by the Onboard Administrator UPLOAD CONFIG command. The
assumption is that you have saved the configuration by completing Exercise 4.
Note
This exercise assumes that you have this configuration file already generated
and stored in the C:\ftproot\OA folder of your FTP server.
Important
Before proceeding with this exercise, consult with your instructor to ensure it
is OK to restore the OA configuration in your classroom environment.
Follow these steps:

1.
Using PuTTY, connect to the Onboard Administrator CLI and log in with
2.
At the Onboard Administrator CLI prompt, type:

download config ftp://<FTP_username>:<FTP_password>@<FTP
server IP address>/<Configuration_file.txt>
Press Enter.
Example
If anonymous is used for the FTP access, use:
download config ftp://192.168.200.1/oa/myoaconfig.txt
Rev. 15.31
L3 21
3.
L3 22
It might take a couple of minutes to execute. When completed, type quit and press
Enter.
Rev. 15.31
Using the Insight Display

Lab 4
Objectives
Access the HP BladeSystem c-Class Insight Display
Navigate the Insight Display
Use the Insight Display Main Menu options
Requirements
To complete this lab, you need one management server (CMS) and one HP BladeSystem
c-Class enclosure either c3000 or c7000, with the configuration described below. This
lab provides instructions for the c7000 enclosure only, as this enclosure is available in
your classroom environment. Using the Insight Display with the c3000 enclosure is
similar.
Note

exercises.
c7000 enclosure configuration

The c7000 enclosure should have these components:
Note
This lab was written using Onboard Administrator firmware 4.40 (dated Dec
08, 2014).
Rev. 15.31
L4 1
c3000 enclosure configuration (provided for reference only)

The c3000 enclosure should have these components:
Introduction
The Insight Display component of the c3000/c7000 enclosure enables you to specify the
initial enclosure configuration and view the health and operational status of the
enclosure.
If the enclosure is not configured, the Insight Display will display the Enclosure Settings
screen. You use this screen to specify various enclosure specifications, including the
enclosure name and the Onboard Administrator IP address.
The color of the Insight Display screen varies with the state of the enclosure:
BlueThe Insight Display illuminates blue when the enclosure is powered up for
the first time. At this point, the enclosure UID illuminates automatically. You can
also illuminate the enclosure UID manually by selecting Turn Enclosure UID on from
the Insight Display Main Menu or by pressing the enclosure UID button on the
management interposer (Onboard Administrator sleeve).
When the enclosure UID is illuminated, the Insight Display flashes blue after two
minutes of inactivity. Pressing any button on the Insight Display stops the flashing
and reactivates the screen.
GreenThe Insight Display illuminates green when no error or alert conditions exist
and the enclosure is operating normally.
AmberThe Insight Display is amber when it detects an error or alert condition. The
error details are displayed on the screen.
BlankThe Insight Display has a two-minute inactivity period. If no action is taken
and no alert condition exists, the light of the Insight Display turns off after two
minutes. Pressing any button on the display panel reactivates the screen.
L4 2
Important
The Insight Display has two modes to notify if an error condition exists.
Normally, the Insight Display flashes amber, indicating an error or alert
condition. If the enclosure UID is on and an error or alert condition exists, the
Insight Display remains blue. The enclosure UID takes priority over the alert
and a red X displays in the lower-left corner of the screen.
Rev. 15.31
Exercise 1Accessing the HP BladeSystem c-Class

Insight Display
In this exercise, you will access the Insight Display remotely through the Onboard
Administrator. The OA GUI enables access to the Insight Display, but you must have the
OA already configured with an IP address and have the appropriate access rights.
Note
Updating OA firmware can result in problems accessing the OA GUI from your
browser. If you are experiencing such problems, clear your browsing history
by using the Tools o Internet Options o General or Tools o Delete
Browsing History in Internet Explorer (depending on the version of Internet
Explorer).
Accessing the Insight Display directly

The Insight Display panel is available in the front of the HP BladeSystem c-Class
enclosure. Because such access requires a physical presence, it is not covered in this lab.
However, it is very similar to the access through the Onboard Administrator.
Accessing the Insight Display through the Onboard Administrator

One method of accessing the Insight Display is through the Onboard Administrator GUI.
However, you can use this method only if an IP address has already been assigned to the
Onboard Administrator.
Important
To access the Onboard Administrator GUI, either 1) the OA IP address must be

configured through the Insight Display, or 2) the OA must have an IP address
assigned via DHCP.
To access the Insight Display through the Onboard Administrator GUI:

1.
2.
Open your browser and in the address field, type the IP address of the Onboard
Administrator (for example, https://192.168.200.100). Press Enter.
Note
Administrator.
Rev. 15.31
L4 3
L4 4
3.
At the Onboard Administrator login screen, type the administrator credentials (for
example, Administrator/password) and click Sign In.
4.
The Onboard Administrator homepage displays. If the Onboard Administrator First

Time Setup wizard launches, click Cancel to exit the wizard. Notice the Insight
Display link in Rack Topology or Systems and Devices sections.
Rev. 15.31
5.
Click the Insight Display link to launch the Insight Display.
6.
The Insight Display screen appears. Click the OK button to activate if needed.
!
Rev. 15.31
Important
There is an option to set an access PIN for the Insight Display (the PIN Code
option). Do NOT set this option, or other learners will be prevented from
accessing the Insight Display.
L4 5
Do NOT enable the button lock (the Lock Buttons option) which completely
disables button functionality. This feature is only configurable from the Web
interface.
7.
If your Insight Display shows the Health Summary screen first, choose Back o OK to
navigate to the Main Menu.
Note
In your HPVL environment, the Insight Display Main Menu might be different
due to the different version of the OA firmware.
L4 6
Rev. 15.31
Exercise 2Navigating the Insight Display

In this exercise, you will learn how to navigate the Insight Display using the navigation
buttons and to use the Main Menu help.
Important
Alert your instructor if you encounter any errors while navigating the Insight
Display. If your enclosure has errors, the Insight Display color will be amber
instead of green.
Using the navigation buttons

1.
Click OK to access the Main Menu. To navigate across the Insight Display menu
options, use the navigation buttonsUp and Down or Forward and Backward.
Note
If accessing the Insight Display through the Onboard Administrator GUI, click
the Up and Down or Forward and Backward buttons to make a selection.
To change any enclosure setting using the Insight Display, first navigate the cursor
(clicking the navigation buttons) to the relevant menu option. Doing this will move
the yellow highlighter to the relevant menu option. Next, you can press the OK
button to access the relevant menu option and perform a specific action for that
item.
Note
Depending on the access rights to the Insight Display, the enclosure type, and
the firmware version supported by the enclosure, the navigation buttons and
the OK button may be aligned at the bottom or the right of the display. Their
functionality, however, remains the same.
Rev. 15.31
L4 7
Using the Main Menu Help

You can also refer to the Main Menu Help for more information on how to navigate within
the Insight Display. The Main Menu Help provides information on the Insight Display
screen color and its meaning.
To access the Main Menu Help:
L4 8
1.
At the Main Menu screen, navigate to the Help option and click OK.
2.
The Help: Main Menu screen displays, where the Back button is outlined in yellow by
default. At the Help: Main Menu screen, click OK to return to the Main Menu.
Rev. 15.31
Exercise 3Using the Insight Display Main Menu

options
In this exercise, you will learn how to navigate the Insight Display Main Menu.
Specifically, you will:
Set the Enclosure UID on and off
Use the Health Summary screen
Access the Enclosure Info screen
Access the Blade or Port Info screen
Change the User Note screen
Use the USB Key Menu options
Use the Health Summary screen during an error or alert condition
Setting the Enclosure UID on

To enable the Enclosure UID:
1.
At the Insight Display Main Menu, check the status of the enclosure UID option (it
indicates whether the Enclosure UID is on or off). You can also determine the status
of this option by the background colorgreen indicates that the UID is off, whereas
blue indicates that the UID is on.
If the UID option is off, navigate to Turn Enclosure UID on and click OK.
What happened to the background color of the Insight Display?

..........................................................................................................................................
Note
The Main Menu screen displays Turn Enclosure UID off when the enclosure
UID is active and displays "Turn Enclosure UID on" when the enclosure UID is
off. Selecting Turn Enclosure UID on illuminates the rear enclosure UID LED
and changes the color of the Insight Display screen to blue. Selecting Turn
Enclosure UID off turns off the rear enclosure UID LED and changes the color
of the Insight Display screen to green or amber, depending on the condition
of the enclosure.
Rev. 15.31
L4 9
Using the Health Summary screen

The Health Summary screen displays the current condition of the enclosure. There are
two methods of accessing the Health Summary screen:
Selecting Health Summary from the Main Menu
Selecting the Health Summary icon from any Insight Display screen
Note
The Health Summary icon is a white checkmark in a green circle ( ) if the

enclosure health is OK or a yellow triangle with exclamation mark ( ) if the
enclosure has some health issues, aligned at the lower left corner of the
navigation bar. Selecting this icon enables you to access the Health Summary
screen, at any time, from any screen in the Insight Display.
To view the health summary of your enclosure:
1.
L4 10
At the Main Menu, navigate to Health Summary and click OK, or navigate to the
Health Summary icon and then click OK.
Rev. 15.31
2.
When the enclosure is operating normally, the Health Summary screen displays
devices as green. The View Alert button is grayed out and only the Back to Main
Menu button is active on the navigation bar. Click OK to return to the Main Menu.
Setting the Enclosure UID off

To disable the Enclosure UID, at the Main Menu, navigate to Turn Enclosure UID off and
click OK.
What is the background color of the Insight Display?

..........................................................................................................................................
Rev. 15.31
L4 11
Accessing the Enclosure Info screen

To view the enclosure information:
1.
At the Main Menu, navigate to Enclosure Info and click OK.
The Enclosure Info screen displays.

Note
The displayed content might differ depending on your lab group.
L4 12
Rev. 15.31
The Enclosure Info screen provides a variety of information about the enclosure,
including:
2.
Rev. 15.31
IP addresses
The Onboard Administrator active network IP address
The Active OA service port IP address
Important
Health status
Current ambient temperature
Present power consumption
Enclosure name
Enclosure Serial Number
Rack name
The enclosure uplink port on the top enclosure of linked enclosures or

individual unlinked enclosures allows temporary service port access to all
linked Onboard Administrators using any of the linked active Onboard
Administrator service IP addresses.
Click OK to return to the Main Menu.
L4 13
Accessing the Blade or Port Info screen

To view blade or port information:
1.
At the Main Menu, navigate to Blade or Port Info and click OK.
2.
At the View: Blade and Port Info screen, select a blade with the Up or Down buttons
(for example, blade #05), and click OK twice.
The selected server blade details display.
3.
L4 14
Click OK to go Back.
Rev. 15.31
4.
To view the ports used by this server blade, navigate to Port Info and click OK.
The rear ports of server blade 5 information displays.
Rev. 15.31
5.
Click OK.
6.
Repeat these steps for a full-height server blade instead. Determine which device
bay has a half-height server blade installed by referring to the Classroom
Configuration Guide.
7.
When done, navigate to the Main Menu.
L4 15
Changing the User Note screen (optional)

Note
This exercise is optional and you may read through it instead of performing it
on the live equipment.
The User Note screen of the Insight Display can display six lines of text, each containing a
maximum of 16 characters. You can use this screen to display helpful information such
as contact phone numbers or other important information.
To explore the User Note screen:
1.
At the Main Menu, navigate to View User Note and click OK.
The User Note screen displays.
L4 16
Rev. 15.31
2.
You can change the text on the User Note screen through the Onboard Administrator
GUI. In OA GUI, select the User Note tab, enter your text, click Apply, and click View
User Note.
!
3.
Important
Avoid the use of special characters in the User Notes section. They become
embedded in the XML data read by HP Systems Insight Manager (SIM) and can
cause issues with SIMs ability to identify the enclosure.
You can also change the User Note screen background bitmap. As a service to your
customers, you could place their logo on the Insight Display. First, save their logo as
a 320 x 240 .bmp file. Then, select the Background tab, upload it to the Onboard
Administrator, and click Apply. The customer logo should appear. Press OK to return
to the Main Menu.
Note
The default text is white, so a darker background works best.

Rev. 15.31
L4 17
Using the USB Key Menu options

The USB Key Menu offers you to:
Update the OA firmware
Save a configuration to a USB device
Restore a configuration from a USB device
Updating the OA firmware

Note
You have already flashed the OA firmware twice. So, feel free to read steps 15 on the next few pages and begin again with step 6.
Note
The screenshots shown in this document are for your reference only and
might slightly differ from those you will see during execution. One such
difference is the version of the bin file you will be using to update the OA
through the Insight Display.
To update the OA firmware using the Insight Display:
1.
L4 18
At the Main Menu, navigate to USB Key Menu and click OK.
Rev. 15.31
Rev. 15.31
2.
At the USB Key Menu, navigate to Update OA Firmware and click OK.
3.
Available firmware will be listed. Select the displayed .bin file and click OK.
L4 19
4.
L4 20
At the Confirm Operation screen, confirm the firmware update operation, and click
OK o OK. The following images are stages in the OA firmware update through
Insight Display.
Rev. 15.31
The following screen image is from the Internet Explorer after the OA update.
Rev. 15.31
L4 21
5.
After OA has been rebooted, you need to log into the OA GUI again and access the
Insight Display in order to continue with the exercises.
6.
Navigate again to the Insight Display USB Key Menu.
Saving a configuration to a USB device

To use the Insight Display to save the Onboard Administrator configuration to a USB
device:
1.
L4 22
At the USB Key Menu, navigate to Save Configuration and click OK.
Rev. 15.31
2.
At the Save OA Configuration screen, navigate to OK and click OK.
This action saves the configuration to the attached USB device and displays the
following confirmation screen.
3.
Rev. 15.31
Click OK to return to the USB Key Menu.
L4 23
Restoring a configuration from a USB device
Important
Restoring a configuration from a USB device exercise is for your reference

only. The exercise shows you how to do the restore, but has you cancel out of
the process. If you follow the exercise it wont disrupt the other team on your
enclosure.
Discuss any of your questions or concerns with your instructor before
proceeding.
To restore a configuration from a USB device:
L4 24
1.
At the USB Key Menu, navigate to Restore Configuration and click OK.
2.
At the Restore OA Configuration screen, select usb:/d1/Students.cfg (or the

configuration file you just saved) and click OK.
Rev. 15.31
3.
At the Confirm Operation screen, navigate to Cancel and click OK. (If you wanted to
proceed, you would navigate to OK and click OK.)
4.
Navigate back to the Main Menu and log out of the Onboard Administrator GUI.
Using the Health Summary screen during an error or alert condition

(paper-based exercise)
When an error or alert condition is detected, the Health Summary screen displays the
total number of error conditions and their locations. The following screenshots simulate
an error on the classroom equipment if a fan was removed or a power cord was
disconnectedfollow these steps as a paper-based exercise; do NOT try to execute
these steps in the HPVL environment.
Note
Because the UID (blue) always has priority over alerts, the Insight Display
remains blue, but there is a health indicator at the lower left when an alert or
failure condition is detected.
1.
Rev. 15.31
At the Main Menu, navigate to Turn Enclosure UID off and click OK.
L4 25
The Insight Display changes immediately to amber.
2.
Navigate back and select the Health Summary option. Note that the Insight Display
shows the number and type of failures and marks their location in red.
Health Summary (c7000 enclosure)
Health Summary (c3000 enclosure)
L4 26
Rev. 15.31
3.
Select View Alert from the navigation bar and press OK to view each individual error
condition. The Insight Display displays each error condition in the order of severity.
Critical alerts display first, followed by caution alerts.
Power Errors: Summary (c7000 enclosure)
Location Error: Summary (c3000 enclosure)
Rev. 15.31
L4 27
4.
Select Details to view the details of the error and press OK.
Power Error (c7000 enclosure)
Location Error (c3000 enclosure)
5.
Discuss the system response if the fans were reinserted or if the power cord was
reconnected.
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
L4 28
Rev. 15.31
6.
Rev. 15.31
By selecting Fix and OK, you will get suggestions on how to mitigate the error; in
addition, you may select Help and OK to view the help of the fix suggested.
L4 29
L4 30
Rev. 15.31
HP BladeSystem c-Class Port Mapping for the c7000

Enclosure
Lab 5
Objectives
After completing this lab, you should be able to determine the server blade port mapping
within the HP BladeSystem c7000 enclosure using the HP BladeSystem Onboard
Administrator GUI.
Requirements
To complete this lab, you will need one management server and one c7000 enclosure
with these components:

Note

exercises.
Rev. 15.31
L5 1
Exercise 1Exploring port mapping for half-height

server blades in the c7000 enclosure
In this exercise, you will use the Onboard Administrator GUI to explore port mapping
between half-height server blades and the interconnect bays in the c7000 enclosure. You
will also be presented customer scenarios where port mapping is an issue.
The following graphic outlines the port mapping for half-height server blades in a c7000
enclosure. Observe the pathways from the embedded network interface cards (NICs) and
the mezzanine slots to the interconnect bays 1 through 8.
Half-height server blade port mapping (c7000 enclosure)
Perform these steps:

1.
If necessary, log into your management server (CMS) with administrative credentials.
2.
At the CMS, log into the Onboard Administrator GUI with administrative credentials.
Note
Refer to the Using HP BladeSystem c-Class Onboard Administrator GUI lab

guide for steps to log into the Onboard Administrator GUI.
L5 2
Rev. 15.31
HP BladeSystem c-Class Port Mapping for the c7000 Enclosure
3.
Rev. 15.31
In the Systems and Devices pane, expand Enclosure Information o Device Bays,
select and expand a half-height server blade, and click Port Mapping. For example,
select a server in Bay 9 which has a mezzanine card installed.
L5 3
4.
To increase the viewing area by hiding the graphical representation of the enclosure,
click
L5 4
in the front of the enclosure name.
Rev. 15.31
The Port Mapping Device Bay # screen displays.
5.
At the Port Mapping Device Bay # screen, identify the ports on the interconnect
bays that are assigned to your server blade and record these values.
Server blade device bay: ..................................................................................................
Embedded Port 1: ............................................................................................................
Embedded Port 2: ............................................................................................................
Note
Port number in this graphical view corresponds to the device bay number. The
lit LEDs on interconnect modules 3-8, if any, indicate that the server blade
has one or more mezzanine cards installed (in the above example, mezzanine
slot 2 is populated).
Also, the suggested or correct answers are provided at the end of the
module.
6.
If your view is different from the screenshot above, explain the differences:
..........................................................................................................................................
..........................................................................................................................................
Rev. 15.31
L5 5
L5 6
7.
To find out the exact ports for a particular NIC in this graphical form, uncheck all
ports and check a single port to see where that port maps.
8.
Click the Table View tab to view port mapping in a tabular form.
Rev. 15.31
9.
In the Systems and Devices pane, expand Interconnect Bays, select and expand the
device in interconnect bay 1, and click Port Mapping.
Port mapping for that interconnect device displays.
Rev. 15.31
L5 7
Note
Newer server blades have FlexNICs. A FlexNIC port can become four separate
ports that share a physical connection to an interconnect device. One port
can show four addresses using the physical connection.
10. What maps to port 9 of this interconnect device?
Server blade in device bay: ..............................................................................................
Embedded NIC or mezzanine? .........................................................................................
Which port of the embedded NIC or mezzanine? ............................................................
11. Ignore the physical interconnects actually installed in your environment to answer
the following question. If a four-port NIC mezzanine card is installed into mezzanine
slot 2, which ports will be mapped to which interconnect module for that mezzanine
card?
..........................................................................................................................................
..........................................................................................................................................
L5 8
Rev. 15.31
12. For this step, refer to the Port Mapping screen below. A customer has installed a
four-port NIC mezzanine card into mezzanine slot 2 of a half-height server blade but
is unable to access all ports. The interconnect bays are populated as shown. What is
the reason?
..........................................................................................................................................
13. On your lab equipment, at the Port Mapping Interconnect Bay 1 screen, identify the
Device ID (MAC address) of the embedded NIC port 1 on the server blade in device
bay 9.
.......................................................................................................... (answers will vary)
Rev. 15.31
L5 9
Exercise 2Exploring port mapping for full-height

server blades in the c7000 enclosure (paper-based
exercise)
In this exercise, you will use the Onboard Administrator GUI to explore port mapping
between full-height server blades and the interconnect bays in the c7000 enclosure. You
will also be presented customer scenarios where port mapping is an issue.
The following graphic outlines the port mapping for full-height server blades in a c7000
enclosure. Observe the pathways from the embedded network interface cards (NICs) and
mezzanine slots to the interconnect bays 1 through 8.
Full-height server blade port mapping (c7000 enclosure)
L5 10
Rev. 15.31
Using the Onboard Administrator GUI, perform these steps:

1.
Rev. 15.31
In the Systems and Devices pane, expand Enclosure Information o Device Bays,
select and expand a full-height server blade, and click Port Mapping Information.
L5 11
The Port Mapping Device Bay # screen displays.
2.
At the Port Mapping Device Bay # screen, identify the ports on the interconnect
Server blade device bay: ..................................................................................................
Embedded Port 1: ............................................................................................................
Embedded Port 2: ............................................................................................................
Embedded Port 3: ............................................................................................................
Embedded Port 4: ............................................................................................................
L5 12
Rev. 15.31
3.
For this step, refer to the Port Mapping screen below. A customer has installed a
two-port NIC mezzanine card into mezzanine slot 1 and 2. If the customer installs an
Ethernet interconnect module in bay 3, which port of which mezzanine card will be
mapped?
Note
Refer to the diagram provided at the beginning of this exercise for help
answering this question.
..........................................................................................................................................
4.
Using the preceding graphic, if the customer installs a four-port NIC into mezzanine
slot 2, what interconnect bays map to ports 3 and 4 of this mezzanine card?
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
Rev. 15.31
L5 13
AppendixAnswers
Exercise 1
Step 5: At the Port Mapping Device Bay # screen, identify the ports on the interconnect
Server blade device bay: n
Embedded Port 1: interconnect 1, port n
Embedded Port 2: interconnect 2, port n
Step 10: What maps to port 9 of this interconnect device?

Server blade in device bay: server blade in device bay 9
Embedded NIC or mezzanine? embedded NIC
Which port of the embedded NIC or mezzanine? port 1
Step 11: If a four-port NIC mezzanine card is installed into mezzanine slot 2, which ports
will be mapped to which interconnect module for that mezzanine card?
Mezz 2, port 1 maps to interconnect 5
Step 12: Refer to the Port Mapping screen below. A customer has installed a four-port
NIC mezzanine card into mezzanine slot 2 of a half-height server blade but is unable to
access all ports. The interconnect bays are populated as shown. What is the reason?
no interconnect in bay 8
L5 14
Rev. 15.31
Exercise 2
Step 2: At the Port Mapping Device Bay # screen, identify the ports on the interconnect
Server blade device bay: server bay 7
Embedded Port 1: interconnect bay 1, port 15
Step 3: Refer to the Port Mapping screen below. A customer has installed a two-port NIC
mezzanine card into mezzanine slot 1 and 2. If the customer installs an Ethernet
interconnect module in bay 3, which port of which mezzanine card will be mapped?
Mezz 1, port 1 is mapped to interconnect 3, port 7
Mezz 1, port 2 is mapped to interconnect 4, port 7
If interconnect bays 5 and 6 have Ethernet modules, the mapping will be as follows:
Mezz 2, port 1 mapped to interconnect 5, port 7
Mezz 2, port 2 mapped to interconnect 6, port 7
If there are Fibre Channel interconnects in bays 5 and 6, which may be the case in the
diagram, then there will be an error.
Step 4: If the customer installs a four-port NIC mezzanine card in slot 2 instead of a twoport NIC mezzanine card, then where the port 3 and 4 of the four-port NIC mezzanine
card will be mapped?
Mezz 2, ports 3 & 4 will not map anywhere since there are no modules in
interconnect bays 7 & 8
Rev. 15.31
L5 15
L5 16
Rev. 15.31
Installing and configuring the HP ProCurve 6120 Blade

Switch
Lab 6
Objectives
Access the HP ProCurve 6120 Blade Switch
Backup and restore the switch configuration
Configure the switch
Restore the switch to factory default settings
Flash the switch firmware
Requirements
To complete this lab, you will need one management server (CMS) and:
HP BladeSystem c-Class enclosure with the HP ProCurve 6120XG or 6120G/XG

switch installed in one of its interconnect bays
Central Management Server (CMS) with the Ethernet connectivity to the Onboard
Administrator
Classroom Configuration Guide
Note

exercises.
Rev. 15.31
L6 1
Introduction
Deploying an HP ProCurve 6120 switch requires extensive knowledge of the network on
which you are installing the BladeSystem solution. For example, understanding the
design of the physical network, details of spanning tree protocol settings, and
configuration of virtual LANs (VLANs) are all critical to a successful implementation of
the switch on the network.
Note
For more information on planning the interconnect configuration, refer to the

HP ProCurve 6120 Switches Management and Configuration Guide document.
L6 2
Rev. 15.31
Installing and Configuring the HP ProCurve 6120 Blade Switch
Exercise 1Accessing the HP ProCurve 6120 Switch

In this exercise, you will access and log into the ProCurve 6120 switch using a Telnet
connection (CLI) and the Onboard Administrator GUI.
Management interfaces and user access (privilege) levels

You can manage (configure the switch and monitor status and performance) the
ProCurve 6120 switch through several management interfaces:
Menu interfacea menu-driven interface that offers a subset of switch commands

through the built-in VT-100/ANSI console. The menu interface can be activated
using the menu command within the CLI.
CLIa command line interface that offers a full set of switch commands through
the VT-100/ANSI console built into the switch. The CLI is a text-based command
interface for configuring and monitoring the switch. It gives you access to the
switchs full set of commands while providing the same password protection that is
used in the web browser interface and the menu interface.
Note
CLI commands are not case-sensitive.
Rev. 15.31
L6 3
Web browser interfacea switch interface that offers status information and a
subset of switch commands through a standard web browser. The OA GUI provides a
URL to the ProCurve 6120 switch web browser interface.
URL in Onboard Administrator GUI
Web interface
ProCurve Manager (PCM)a Windows-based network management solution

included in-box with all manageable ProCurve devices. Its features include
automatic device discovery, network status summary, topology and mapping, and
device management.
ProCurve Manager Plus (PCM+)a complete Windows-based network
management solution that provides both the basic features offered with PCM as
well as more advanced management features, including in-depth traffic analysis,
group and policy management, configuration management, device software
updates, and advanced VLAN management. ProCurve includes a copy of PCM+ inbox for a 30-day trial.
For most of the exercises, you will use the CLI and the Web browser interface.
L6 4
Rev. 15.31
The CLI offers these privilege levels to help protect the switch from unauthorized access:
OperatorAt this level, you can examine the current configuration and move
between interfaces without being able to change the configuration. The >
character represents the Operator-level prompt. For example:
ProCurve> _
ManagerThis privilege level gives you three additional levels of access:
Manager
Global Configuration
Context Configuration
The # character represents the Manager prompt. For example:

ProCurve# _
Privilege levels control the type of access to the CLI. To implement this control, you must
set at least a Manager password. Without a Manager password configured, anyone
having serial port, Telnet, or web browser access to the switch can reach all CLI levels.
Note
Pressing the Clear button on the front of the switch removes password
protection.
Note
The user details provided above are only examples. When executing this lab,
refer to the Classroom Configuration Guide for any specific naming
conventions and environment-specific values.
CLI is accessed through the switch console, and in the switchs factory default state, it is
the default interface when you start a console session. You can access the console outof-band by directly connecting a terminal device to the switch, or in-band by using Telnet
either from a terminal device or through the web browser interface.
Note
ProCurve switches also provide the ability to use the connect

interconnect x command from the Onboard Administrator CLI.
Rev. 15.31
L6 5
Accessing the Web Browser Interface

You can access the ProCurve 6120 Web Browser Interface either directly, by specifying
the switch IP address in your browser, or through the Onboard Administrator GUI.
Accessing the Web Browser Interface directly through the web browser
To access the ProCurve 6120 Web Browser Interface directly (using the switch IP
address):
1.
2.
Open a browser, type http://<ProCurve 6120 switch IP address> in the

address field and press Enter.
!
3.
Important
Do not use https://< ProCurve 6120 switch IP address>.
At the login window, enter credentials to login to the ProCurve switch (for example,
admin/password). Click OK to continue.
Note
When executing this lab, refer to the Classroom Configuration Guide for
correct username and password.
L6 6
Rev. 15.31
If the Authentication Required window displays, enter the username and password,
for example admin/password, and click OK to continue.
The ProCurve 6120 Web Browser Interface displays.
Rev. 15.31
L6 7
When you access the switchs Web Browser Interface for the first time, the Alert log
contains a First Time Installation alert, as shown in the graphic above. This gives
you information about first time installations, and provides an immediate
opportunity to set passwords for security and to specify a Fault Detection policy,
which determines the types of messages that will be displayed in the Alert Log.
4.
Double-click First Time Installation in the Alert log. The Web Browser Interface then
displays the First-Time Install window (this window opens in the background; thus,
minimize the main ProCurve 6120XG Blade Switch window).
Note
If your browser blocks pop-up windows and you receive the Pop-up blocked.
To see this pop-up or additional options click here message, click the
message, select Always Allow Pop-ups from This Site, and click Yes.
5.
L6 8
Click Cancel and close the ProCurve 6120 Web Browser Interface.
Rev. 15.31
Accessing the Web Browser Interface through the Onboard Administrator GUI
To access the ProCurve 6120 Web Browser Interface through the Onboard Administrator
GUI:
Rev. 15.31
1.
Open a browser, type http://<Onboard Administrator IP address> in

the address field, and press Enter.
2.
At the HP BladeSystem Onboard Administrator login screen, enter the administrative

credentials and click Sign In.
3.
In the Systems and Devices pane, expand Enclosure Information o Interconnect

Bays o HP ProCurve 6120XG Blade Switch and click Management Console.
L6 9
4.
At the login window, enter credentials to log into the ProCurve switch (for example,
admin/password). Click OK to continue.
Note
When executing this lab, refer to the Classroom Configuration Guide for
correct username and password.
5.
L6 10
At the Authentication Required window, enter the username and password (for
example, admin/password). Click OK to continue.
Rev. 15.31
The ProCurve 6120 Web Browser Interface displays.
6.
Rev. 15.31
Close the ProCurve 6120 Web Browser Interface.
L6 11
Accessing the CLI through a Telnet connection

A Telnet connection offers the convenience of accessing the switch from any workstation
connected to the network. By default, Telnet is enabled on the switch. After the IP
parameters are configured, you can access the CLI using a Telnet connection.
To establish a Telnet connection with the switch using PuTTY:
L6 12
1.
2.
At the PuTTY Configuration screen, enter the IP address of your target ProCurve
switch in the Host Name (or IP address) field, select Telnet as the connection type,
and click Open.
Rev. 15.31
3.
At the initial screen, where you are presented with a Login Prompt, enter your
credentials to login.
The ProCurve 6120XG Blade Switch# prompt displays.
4.
Rev. 15.31
Close the PuTTY window and click OK to confirm closing the session.
L6 13
Exercise 2Backing up and restoring the switch

configuration
In this exercise, you will download and upload the ProCurve 6120 switch configurations
through the ProCurve Web Browser Interface.
As mentioned previously, you can store up to three configuration (startup-config) files in
the flash memory of the ProCurve 6120 Blade Switch series.
From the Web Browser Interface Upload/Download page, you can download, upload,
delete, and rename configuration files:
L6 14
1.
If necessary, connect to the Web Browser Interface as explained previously.
2.
Select the Configuration o Upload/Download tabs.
3.
At the Upload/Download tab, select the config configuration file from the
Configuration: dropdown menu and click Download to back up the chosen
configuration file.
Rev. 15.31
4.
Rev. 15.31
At the File Download popup screen, select Save as and save the configuration file in
the C:\classfiles\Firmware\HP ProCurve 6120XG folder with the file
name teamX, where X is the number of your team. Click Save o Close.
L6 15
5.
Browse to the C:\classfiles\Firmware\HP ProCurve 6120XG folder on

your CMS and check if the configuration file is backed up.
To upload or restore to a certain switch configuration, you need to upload configuration

file to your switch. For this process, you will again use the ProCurve Web Browser
Interface:
L6 16
Important
The switch can have up to three configuration files. You cannot add a new
configuration file if three files already exists within the switch. In this case,
you must delete one first.
You can, however, overwrite an existing configuration file if the name is the
same.
Rev. 15.31
Rev. 15.31
6.
At the Web Browser Interface Upload/Download page, click Upload.
7.
Type teamX or the name of the configuration file you have specified in the previous
exercise, browse to the C:\classfiles\Firmware\HP Procurve 6120XG
folder, select your saved configuration file to be uploaded, and click Upload.
L6 17
Upon successful configuration upload, the switch will reboot with the uploaded
configuration. It might take a couple of minutes.
During the reboot process, the switch might not be accessible.
L6 18
Rev. 15.31
Exercise 3Configuring the HP ProCurve 6120 Blade

Switch
Overview of the running-config and startup-config files
The switch maintains two configuration filesthe running-config file and the startupconfig file.
The running-config file exists in volatile memory and controls switch operation. If no
configuration changes have been made in the CLI since the switch was last booted, the
running-config file is identical to the startup-config file.
The startup-config file exists in flash (non-volatile) memory and is used to preserve the
most recently-saved configuration as the permanent configuration.
Note
Booting the switch replaces the current running-config file with a new
running-config file that is an exact copy of the current startup-config file.
Rev. 15.31
In the CLI, the write memory command overwrites the current startup-config file
with the contents of the current running-config file.
In the menu interface, the Save command overwrites both the running-config file
and the startup-config file with the changes you have specified in the menu
interface screen.
L6 19
In the Web Browser Interface, the Apply Changes button overwrites both the
running-config file and the startup-config file with the changes you have specified in
the Web Browser Interface window.
Note
Using the CLI instead of the menu or Web Browser Interface gives you the
option of changing the running configuration without affecting the startup
configuration. This allows you to test the change without making it
permanent. When you are satisfied that the change is satisfactory, you can
make it permanent by executing the write memory command.
Viewing the current configuration files

The show commands are used to view the configuration for individual features, such as
port status or Spanning Tree Protocol. However, to view either the entire startup-config
file or the entire running-config file, use these commands:
show configdisplays a listing of the current startup-config file.
show running-configdisplays a listing of the current running-config file.
write terminaldisplays a listing of the current running-config file.
show config statuscompares the startup-config file to the running-config

file and lists one of the following results:
If the two configurations are the same, you will see:

Running configuration is the same as the startup
configuration.
If the two configurations are different, you will see:

Running configuration has been changed and needs to be
saved.
To view current running-config of the switch:

1.
If necessary, use PuTTY to connect to the assigned ProCurve 6120 switch to access
the switch CLI interface.
Note
Refer to the Classroom Configuration Guide for the switch assigned to your
team, its IP address, and login credentials.
L6 20
Rev. 15.31
2.
At the ProCurve 6120 Switch Manager prompt, type show running-config and
press Enter.
The running configuration of the switch displays. You may press Space for the next
page of the configuration information, next line will be visible if you press Enter,
and you may quit listing by pressing ControlC to get back to the switch Manager
prompt. Do not exit the session yet.
Rev. 15.31
L6 21
3.
L6 22
To show specific port information, use the show interface <x> command. Issue
the show interface 2 command and press Enter.
Rev. 15.31
4.
Rev. 15.31
Issue the show interface 17 command and press Enter.
L6 23
Using the CLI to reconfigure the switch

The following four steps reconfigure the switchthey permanently change the switch
configuration by entering the change in the startup-config file.
Note
These steps are provided here for your reference. Do not attempt to execute
them. You will have a chance to try these steps under the Example section
below.
a. Use the appropriate CLI commands to reconfigure the desired switch parameters.
This updates the selected parameters in the running-config file.
b. Use the appropriate show commands to verify that you have correctly made the
desired changes.
c. Observe the switchs performance with the new parameter settings to verify the
effect of your changes.
d. When you are satisfied that you have the correct parameter settings, use the write
memory command to copy your changes to the startup-config file.
Example
You want to disable a certain port on the ProCurve 6120 switch (port 2 in the running
configuration) which causes port 2 to block all traffic.
1.
L6 24
If necessary, use PuTTY to connect into the assigned ProCurve 6120 switch to access
the CLI interface. At the prompt, type config and press Enter at the prompt to
enter the next privilege level (Global Configuration) of the switch.
Rev. 15.31
Rev. 15.31
2.
Type interface 2 disable and press Enter to update the running-config file.
3.
Before you save this configuration, type show runningconfig and press Enter
to verify that you correctly made the desired change. Press Space to return to the
prompt.
L6 25
L6 26
4.
Type write memory and press Enter to save the configuration in the startupconfig file.
5.
Type exit and press Enter to exit the Global Configuration privilege level.
Rev. 15.31
Specifying the software (firmware image) and configuration file to

use when booting the switch
You can store up to three configuration (startup-config) files in the flash memory of the
ProCurve 6120 Blade Switch series. These three locations are referred to as active,
primary, and secondary.
1.
Rev. 15.31
At the ProCurve 6120XG Blade Switch prompt, type show config files and press
Enter to see the list of the available switch configurations.
L6 27
2.
For the next boot, you may select either the primary or the secondary firmware
image and any of the available configuration files. In this step, you will use the
secondary image and the config configuration file. Type boot system flash
secondary config config and press Enter.
3.
Press y for device reboot. If offered to save the current configuration, type y. The
switch will then reboot and your connection terminates.
Note
If you use the connect interconnect x command to connect to the

switch instead of PuTTY/Telnet, then the whole boot process remains visible.
For troubleshooting, this is the preferred way so that you can monitor for
boot errors.
L6 28
Rev. 15.31
4.
Rev. 15.31
After the switch reboots, log into the switch CLI, type show config files and
press Enter to see the changes in the active switch configuration file.
L6 29
Exercise 4Restoring the switch to factory default

settings
In this exercise, you will learn how to reset the HP ProCurve 6120 switch to its factorydefault settings.
Reloading the factory settings clears all settings and restores them to the initial values
that were present when the switch was purchased.
Note
When performing this exercise outside the classroom, it is recommended

that the switch is disconnected from the network before restoring it to the
factory defaults.
To restore the HP ProCurve 6120 switch settings to factory defaults:
1.
If necessary, use PuTTY to connect into the assigned ProCurve 6120 switch to access
the CLI interface. At the ProCurve 6120XG Blade Switch prompt, type config and
press Enter to enter the Global Configuration privilege level.
2.
Type erase startup-config and press Enter.
3.
Press y to replace the current configuration with the factory default configuration
and reboot the switch. The switch reboots and your connection terminates.
Note
If you use the connect interconnect x command to connect to the

switch instead of PuTTY/Telnet, then the whole boot process remains visible.
For troubleshooting, this is the preferred way so that you can monitor for
boot errors.
L6 30
Rev. 15.31
Exercise 5Flashing the switch firmware

In this exercise, you will update the ProCurve 6120 switch firmware through the
ProCurve Web Browser Interface. The same can be done by using other management
interfaces as well, such as the CLI.
1.
By either using the web browser through the OA or directly accessing the ProCurve
Web Browser Interface, click the Configuration tab.
Note
Refer to the Classroom Configuration Guide for the switch assigned to your
team, its IP address and login credentials.
Rev. 15.31
L6 31
2.
L6 32
At the configuration page, click the Upload/Download tab to access the software
(firmware) and configuration file management of the ProCurve 6120 switch. At the
Upload/Download page, scroll down, select the Primary software image under the
Destination dropdown menu, and click Upload.
Rev. 15.31
3.
Browse to the C:\Classfiles\Firmware\HP ProCurve 6120XG folder,

select the Z_14_51.swi firmware image to upload, and click Upload.
After the image upload, the switch will reboot.
Rev. 15.31
L6 33
4.
Repeat the same steps to flash the other image (secondary).
Note
The Upload and reboot processes can take several minutes. You can watch
the boot process in the serial console to know when it is done.
L6 34
Rev. 15.31
Virtual Connect
Lab 7
Objectives
View the Virtual Connect domain configuration
Manipulate the server profiles
Back up the Virtual Connect configuration
Restore the Virtual Connect configuration
Use the Virtual Connect Support Utility
Update the Virtual Connect firmware
Reset the Virtual Connect Manager
Requirements
To complete the exercises in this lab, you need:
A personal computer with a supported browser, connected to the HP internal

network
An HP BladeSystem c7000 enclosure with Virtual Connect FlexFabric modules in
bays 1 and 2
Note
The screenshots presented in the Classroom Configuration Guide may differ

from those presented in this lab.
Rev. 15.31
L7 1
Exercise 1Viewing the Virtual Connect domain

configuration
In this exercise, you will use the Virtual Connect Manager (VCM) to view the configuration
of the Virtual Connect (VC) domain.
For this exercise, you need the following login information:
OA IP address: ..................................................................................................................
OA username: ...................................................................................................................
OA password: ...................................................................................................................
Virtual Connect domain username: .................................................................................
Virtual Connect domain password: ..................................................................................
Note
You can find above information in the Classroom Configuration Guide. The VC
domain username/password are in the Classroom Configuration Guide listed
as the VC FlexFabric module.
Connecting to the VCM GUI

To connect to the VCM GUI:
L7 2
1.
Launch your browser, enter http://<OA IP address> in the address field, and
press Enter.
2.
If a website security certificate notice displays, click Continue to this web site.
3.
Log into the OA GUI using administrative account credentials (OA username and OA
password from above).
Rev. 15.31
Virtual Connect
4.
Click the Virtual Connect Manager link at the bottom of the Systems and Devices
frame on the left of the OA GUI screen or in Rack Topology overview on the right.
Another web browser tab or window opens for the Virtual Connect Manager.
5.
Rev. 15.31
If a website security certificate notice displays, click Continue to this website.
L7 3
6.
Log into the VCM using the Virtual Connect domain credentials.
The Virtual Connect Manager window displays.
L7 4
Rev. 15.31
Virtual Connect
Examining the networks and their assigned uplink ports

Each network defined within VCM can have one or more uplinks and be part of one or
more Network Access Groups.
Network Access Groups are defined by the network administrator and associated with a
set of networks that can be shared by a single server. Each server profile is associated
with one Network Access Group. A network cannot be assigned to the server profile
unless it is a member of the Network Access Group associated with that server profile. A
Network Access Group can contain multiple networks.
1.
Rev. 15.31
Click the Ethernet Networks link under Connections in the left navigation frame.
L7 5
2.
L7 6
On the External Connections tab, click on the name of one of the listed Ethernet
networks in the Ethernet Networks column to view the uplink port details for that
network. Also, look at the information on the Overview tab for the selected
network.
Rev. 15.31
Virtual Connect
3.
Click each network in the Ethernet Networks column and write down the uplink port
and the Network Access Groups information for these networks in the table below.
Toggle between Overview and Uplink Ports tabs as necessary.
Ethernet network name
Rev. 15.31
Uplink Ports
Network Access Groups
Important
Do not make any changes to the VC domain settings in the VCM at this time.
L7 7
Exercise 2Assigning, unassigning, and moving server

profiles
The server profile provides a link between the server and the networks and fabrics
defined in VC. The server profile can include MAC and WWN addresses as well as boot
parameters for the various connection protocols supported by VC. After being defined,
the server profile can be assigned to any server blade within the Virtual Connect domain.
VCM supports up to 256 profiles within the domain.
A Virtual Connect server profile consists of connections that group attributes related to
server connectivity for the various protocols supported by Virtual Connect modules.
These protocols are Ethernet, iSCSI, Fibre Channel over Ethernet (FCoE), and Fibre
Channel.
When a server profile is assigned to a server blade, VCM configures the connections with
the appropriate MAC/WWN addresses and boot settings. USE BIOS is an option for all
connection boot settings that preserves the options set in the RBSU or through other
configuration utilities. Virtual Connect Manager automatically connects the server blade
Ethernet, iSCSI, FCoE, and Fibre Channel ports to the specified networks and SAN fabrics.
This server profile can then be re-assigned to another server blade as needed, while
maintaining the server's network and SAN identity and connectivity.
VCM can be configured so that server blades use server factory default MACs/WWNs or
Virtual Connect-administered MACs/WWNs. These administered values override the
default MAC addresses and WWNs when a server profile is assigned to a server, and
appear to pre-boot environments and the host operating system software as the
hardware addresses. To use administered MAC/WWN addresses, you may select a range
of HP pre-defined or user-specified MAC addresses, which were done during the setup of
this lab.
If a server blade is moved from a Virtual Connect-managed enclosure to a non-Virtual
Connect enclosure, all ports automatically return to the original factory default MAC
addresses and WWNs. This feature prevents duplicate MAC addresses and WWNs from
appearing in the data center because of a server blade redeployment.
In this exercise, you will examine VC for Ethernet connection protocol, which provides the
ability to assign VC-assigned MAC addresses, and configure PXE boot settings as well as
allocate bandwidth on FlexFabric connections.
L7 8
Rev. 15.31
Virtual Connect
Rev. 15.31
1.
Click Server Profiles under Connections in the left navigation frame.
2.
Locate the Shared_Server profile and review the profile information which is
available on this page. You can see that this profile is assigned to the server in bay 9,
that MAC and WAN addresses are VC-DEFINED (they will be assigned by the VC), and
the Network Access Group is set to Default.
L7 9
Note
Within the VCM GUI and CLI, you can define Network Access Groups to manage
groups of networks. Association of a Network Access Group with a server
profile allows you to clearly define the separation of networks by designated
function and to prevent unintended network-server connections. You can
assign only one Network Access Group to each server profile, but you can
assign the same Network Access Group to multiple server profiles.
Ethernet networks and server profiles that you do not assign to a specific
Network Access Group automatically go into to the default Network Access
Group for the domain. All server profiles can reach all networks within the
default Network Access Group. The ability of Network Access Groups to
isolate networks also plays an important security role.
Since you already have information on Network Access Groups and server profiles,
answer these questions:
What is the Network Access Group for Backup_Server profile?
..........................................................................................................................................
Is it possible for network defined in the Backup_Server profile to reach the networks
defined on Shared_Server profile? Explain.
..........................................................................................................................................
3.
Under the Hardware section in the left navigation frame, expand Students and click
Device Bays.
Note that you have four ProLiant BL460c G7 server blades, one BL460c G1 server
blade, two BL460c Gen8 server blades, two BL460c Gen9 blades and two BL860c
Integrity server blades.
L7 10
Rev. 15.31
Virtual Connect
Rev. 15.31
4.
On the Device Bays Summary screen, click Bay 9 link to display the information
about the ProLiant BL460c G1 server blade.
5.
On the Bay 9 (ProLiant BL460c G1) screen, scroll down to display Server Ethernet
Adapter Information. Note the number and the type of Ethernet adapters available.
L7 11
Note
You are using the ProLiant BL460c G1 server blade just to emphasize the
difference between ProLiant G1 and G7. Do not modify or change
configuration for the server blade in bay 9 (ProLiant BL460c G1). Notice you
have Power control functions for the blade built into the VC GUI here.
6.
Back on the Device Bays Summary screen, click Bay 4 to display information for the
ProLiant BL460c G7 server blade. Scroll down to display Server Ethernet Adapter
information.
What is the difference between ProLiant BL460c G7 and ProLiant BL460c G1 server
blades regarding the number and type of available Ethernet adapters?
..........................................................................................................................................
..........................................................................................................................................
L7 12
Rev. 15.31
Virtual Connect
7.
Click Server Profiles under Connections in the left navigation frame. Find profile
Development_Profile_01 assigned to the server in bay 4 and select Delete from the
Action column on the far right.
8.
When the Confirmation dialog appears, type the name of server profile you want to
remove (Development_Profile_01) and click Cancel to cancel profile deleting.
Note
At this moment, you do not want to delete the defined server profile. This is
the reason you are canceling the confirmation dialog.
9.
Rev. 15.31
Select Edit for Development_Profile_01.
L7 13
10. At the Edit Server Profile: Development_Profile_01 window, under the Ethernet
Adapter Connections section, note the MAC addresses and Allocated Bandwidth. Click
the icons on the far right to examine PXE options for both ports.
11. Answer these questions:

How are the MAC addresses of listed Ethernet Adapter Connections assigned on this
server profile?
a.
Hardware based
b.
Assigned by VC
What is the maximum number of Ethernet Adapter Connections which can be

defined for profile assigned to ProLiant BL460c G7 server blade if no FCoE is used?
..........................................................................................................................................
..........................................................................................................................................
L7 14
Rev. 15.31
Virtual Connect
12. Under the Profile section, open the drop down menu in Network Access Group
column.
What Network Access Groups are available?

..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
13. Click Interconnect Bays under Hardware o Students in the left navigation frame.
Check the Interconnect Bays Summary section. Note the number of VC
interconnects, type of modules, and firmware versions.
Rev. 15.31
L7 15
14. In the Interconnect Bays Summary section, click Bay 1 (LAN+SAN). Explore the
Uplink Ports Information as well as the Server Ports Information.
Note
Looking at the profile assignment, you can determine that profile

Development_Server_Profile_01 is assigned to the server blade in bay 4, and
profile Development_Server_Profile_02 is assigned to the server blade in bay
5. In the following steps, you will change profile assignment to switch
assigned profiles between bay 4 and bay 5.
L7 16
Rev. 15.31
Virtual Connect
Important
Before changing or moving the server profiles, ensure that affected server
blades are powered down.
15. If necessary, back on the Device Bays screen, click Bay 4 to display the information
about the ProLiant BL460c G7 server blade. Scroll down to display the Server
Ethernet Adapter information and write down the Server Ethernet Adapter
information for ProLiant server blade in Bay 4.
Ethernet Adapter
Port
MAC Address
Network
16. Back on the Device Bays screen, click Bay 5 to display the information about the
ProLiant BL460c G7 server blade. Scroll down to display the Server Ethernet Adapter
information and write down the Server Ethernet Adapter information for ProLiant
server blade in Bay 5.
Ethernet Adapter
Port
Mac Address
Network
Note
To unassign and/or reassign a profile, the affected server blades have to be

powered down. You will need to power off server blades in bay 4 and bay 5
before you proceed. Verify that the Power button/Power status is orange.
17. To unassign the server profile from the ProLiant server blade in bay 4, back at the
Server Profiles window, click Edit in the row displaying the profile
Development_Profile_01.
Rev. 15.31
L7 17
18. In the Edit Server Profile: Development_Profile_01 screen, scroll down to the Assign
Profile to Server Bay section, click the arrow in the Server Selection column and
select Unassign from the drop-down menu.
19. Click Apply & Close to confirm.
20. Wait a minute for VC to save changes to the Server Profile.
Server bay assignment for Development_Profile_01 changes to Unassigned.

21. Repeat the previous steps to un-assign profile Development_Profile_02 from the
server in bay 5.
Profiles Development_Profile_01 and Development_Profile_02 list as unassigned.
Note
In the following steps, you will assign profiles to server blades in bay 4 and 5
for profile Development_Profile_01 to map to server blade in bay 5 and
server profile Development_Profile_02 to map to server in Bay 4. This
assignment is opposite to the profile assignment at the beginning of this
module.
L7 18
Rev. 15.31
Virtual Connect
22. On the Server Profiles page, click Edit in the row displaying server profile
23. On the Edit Server Profile: Development _Profile_01 page, scroll down to the Assign
Profile to Server Bay section. Click Unassigned to open the drop-down menu and
select Students o Bay 5 (ProLiant BL460c G7). Click Apply & Close to confirm.
24. On the Server Profiles page, click Edit in the row displaying server profile
25. Assign the Development_Profile_02 server profile to the server in bay 4 (ProLiant
BL460c G7). Click Apply & Close to confirm.
Server profile assignment should now match the screen below:
Rev. 15.31
L7 19
Note
Now that you have switched Server Profile Assignments between the server
blades in bay 4 and bay 5, you will collect the information about MAC
addresses and compare to the information collected at the beginning of
exercise 2.
26. Click Device Bays under the Hardware section in the left navigation frame.
27. On the Device Bays screen, click Bay 4 and collect this information:
Ethernet Adapter
Port
MAC Address
Network
28. Back at the Device Bays screen, click Bay 5 and collect this information:
Ethernet Adapter
Port
MAC Address
Network
29. Looking at the information collected in exercise 2, answer these questions:

What happened to the MAC addresses after moving server profiles? Explain.
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
If you have defined FCoE HBA connections within the server profile, what will happen
to WWN addresses after moving server profiles? Explain.
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
Note
Using the steps described in exercise 2, you could perform profile-related

operations on Integrity BL860c server blades located in enclosure bays 7 and
8. Although these server blades are Integrity based, from the Virtual Connect
Manager point of view, the procedure is the same.
L7 20
Rev. 15.31
Virtual Connect
Exercise 3Backing up the Virtual Connect

configuration
Virtual Connect configuration backup and restore operations are performed from the
Virtual Connect Manager. In this exercise, you will practice backing up the VC domain
configuration.
Rev. 15.31
1.
Ensure you are still connected to the Virtual Connect Manager. If not, reconnect as
described in the previous exercise.
2.
Click the Backup/Restore link under Domain Settings in the left navigation menu.
L7 21
L7 22
3.
At the Backup/Restore page, click Backup Configuration. Leave the Encryption Key
field blank. Confirm with OK.
4.
When the Internet Explorer file download security warning appears, open the dropdown menu and select Save as.
Rev. 15.31
Virtual Connect
5.
Rev. 15.31
At the Save As dialog, navigate to the C:\temp folder and click Save. Use the default
file name.
L7 23
Exercise 4Restoring the Virtual Connect

configuration
In this exercise, you will restore the saved Virtual Connect configuration.
!
1.
L7 24
Important
The server blades attached to the Virtual Connect modules must be powered
off first.
Use the Onboard Administrator GUI and gracefully power off all server blades in the
enclosure that are not already shutdown.
a.
Click + in front of the device bays.
b.
Click one of the server blades in the list.
c.
Click the Virtual Devices tab in the right panel.
d.
Click the Momentary Press button and wait until the power LEDs in the
enclosure front view on the right turn from green to orange (the assumption is
that the ACPI drivers are loaded).
e.
Repeat these steps for each server blade in the list until all are powered off. All
server blades must be powered off for the restore operation to work.
2.
Return to the Virtual Connect Manager screen and, if necessary, click

Backup/Restore in the left navigation menu.
3.
At the Backup/Restore page, scroll down to the Restore Domain Configuration

section. Click Browse and browse to the C:\Classfiles\Firmware\Virtual Connect
folder (not the C:\temp folder).
4.
Select the vcConfig-Students_vc_domain_c-Class_lab configuration file and click

Open.
5.
In the Restore Domain Configuration section, select the Ignore enclosure serial
number in restored configuration file checkbox. Also, ensure that the Encryption
key field is blank and the other Ignore checkbox is unselected.
Rev. 15.31
Virtual Connect
Rev. 15.31
6.
Click Restore Configuration.
7.
In the Confirm popup window, type the name of the current Virtual Connect domain
(Students_vc_domain) and click OK.
L7 25
Note
The VCM configuration cannot be restored from an even interconnect bay

(you might check by IP address which VC module is accessed). If necessary,
reset VC with the failover option from the top navigation menu (see exercise
7 for step-by-step instructions).
The restore operation starts and logs you out of the Virtual Connect Manager. The
VCM screen clears and the Restore domain is in progress message displays.
When the restore operation completes, the main Virtual Connect Manager login
page displays without the Loading, please wait message or the animated
progress bar.
8.
L7 26
Log back into Virtual Connect Manager.
Rev. 15.31
Virtual Connect
Exercise 5Using the Virtual Connect Support Utility

To complete a VC firmware update using the Virtual Connect Support Utility (VCSU), you
install the VCSU software for Windows on a PC or laptop connected to the enclosure
management network. For this lab exercise, the VCSU software (vcsu-1.11.0-x86.msi)
has already been installed on the CMS (running Microsoft Windows Server 2008 R2).
Note
There are many requirements for the VC firmware update that must be met
but they are out of the scope of this lab exercise.
At minimum, the VC domain configuration backup must be done, which you just
completed. VCSU automatically creates a backup of the Virtual Connect domain
configuration during the firmware update process to a file on the computer where VCSU
is installed (typically under C:\Program Files (x86)\Hewlett-Packard\Virtual Connect
Support Utility\). Also, you need to ensure that the health of the VC domain is OK before
performing the firmware update by verifying the status of all VC Ethernet and FlexFabric
modules:
Health = OK
IP Connectivity = Passed
Module Configuration = In Sync
Domain Configuration = In Sync (Primary and Backup modules only)

Note
Set the screen buffer on the Windows command prompt to more than the
default 300 lines so you do not lose the output from the VCSU.
Rev. 15.31
L7 27

1.
At your assigned CMS, click Start o All Programs o Hewlett-Packard o Virtual

Connect Support Utility o Virtual Connect Support Utility Interactive.
A command prompt window opens with the following screen:
L7 28
Rev. 15.31
Virtual Connect
2.
Enter the help command to display the list of VCSU commands and their
descriptions. You may need to scroll the window to see all commands.
3.
To run a health check for the Virtual Connect domain using VCSU, enter
healthcheck at the prompt and press Enter.
a.
At each prompt, enter your assigned equipment information. Use the OA

module IP address, username, and password that you wrote at the beginning of
this exercise as well as Virtual Connect domain credentials.
b.
The healthcheck command writes the information to the screen (shown on the
next page) and also to a log file in the VCSU install directory (C:\Program Files
(x86)\Hewlett-Packard Company\Virtual Connect Support Utility\).
Note
Total execution time of the healthcheck command can be several minutes.

Two to five minutes is normal.
Rev. 15.31
L7 29
If the Health = OK, IP Connectivity = Passed, Module Configuration = In Sync, and

Domain Configuration = In Sync, you can proceed with the firmware update.
Note
The healthcheck command is primarily used to check the health of the Virtual
Connect domain before a firmware upgrade. If the health of any module is not
listed as 'Ok, Passed and In Sync,' then that problem must be fixed before
upgrading the firmware.
L7 30
Rev. 15.31
Virtual Connect
4.
Press Enter to exit the interactive VCSU session and close the window.
Note
The VCSU can be run in two ways:

Interactive mode runs one command and prompts you for the required input.
Command line mode runs more than one command and you must enter a command with all
appropriate qualifiers.
5.
Restart the VCSU interactive mode.
6.
Enter the version command to display the current module firmware version on
the target configuration. Enter the OA IP address and username/password and the
VC domain username/password when prompted.
Note
Total execution time of the version command can be up to several minutes.
The version information is shown for the Virtual Connect FlexFabric Ethernet switch
modules but not for the other modules because the VCSU utility does not know how
to query them for their firmware version information.
Rev. 15.31
L7 31
7.
Click Start o All Programs o Hewlett-Packard o Virtual Connect Support Utility

o Virtual Connect Support Utility Command Prompt to run VSCU in the
command line mode.
You will use the collect command which will contact the OA using the supplied
credentials and execute the SHOW ALL command from the OA CLI, saving the
output to the oaShowAll.txt file in the current directory. It will also contact the
primary VC Manager using the supplied credentials and execute several VC-related
commands, saving the output to the vcmShowAll.txt file.
Note
The exact syntax of the VCSU collect command is:

vcsu -a collect -i <OA_IP> -u <OA_USER> -p <OA_PWD>
-vcu <VCM_USER> -vcp <VCM_PWD>
<OA_IP> - Onboard Administrator IP address
<OA_USER> - Onboard Administrator username
<OA_PWD> - Onboard Administrator password
<VCM_USER> - VCM username
<VCM_PWD> - VCM password
8.
Enter the properly formatted collect command at the prompt (all on one line), for
example:
vcsu -a collect -i 192.168.200.100 -u Administrator -p
password -vcu Administrator -vcp password
Because the same filenames (oaShowAll.txt and vcmShowAll.txt) are used each
time the collect command is run, the files are overwritten unless they are saved
somewhere else first. These files are usually requested by Support engineers to
troubleshoot problems with Virtual Connect.
The log files that are generated for each VCSU session are basically screen captures
of the session.
9.
Open Windows Explorer from the Start menu and browse to the VCSU install folder.
Note the path given in the output above.
10. Double-click the oaShowAll.txt file to open it in Notepad or AB-Edit. Review the
information collected in the file and close it when done.
L7 32
Rev. 15.31
Virtual Connect
11. Double-click the vcmShowAll.txt file to open it in Notepad or AB-Edit. Review the
information collected in that file and close it when done.
12. Enter the exit command to close the VSCU command window.
Rev. 15.31
L7 33
Exercise 6Updating the Virtual Connect firmware

In this exercise, you will update the firmware on the Virtual Connect FlexFabric modules.
This exercise uses the same IP address/username/password information that you used
previously.
Note
Before performing a firmware update at a customer site, the current

configuration should be backed up and the health of all VC modules should
report as OK in the output of the healthcheck command.
1.
Click Start o All Programs o Hewlett-Packard o Virtual Connect Support Utility

o Virtual Connect Support Utility Interactive to run VCSU in the interactive
mode.
2.
Enter the update command to update the firmware on the VC modules.
3.
Enter the OA IP address/username/password when prompted.
4.
The firmware package location is at C:\classfiles\Firmware\Virtual

Connect\vcfwall441.bin
5.
At the configuration backup password (optional) prompt, do not enter a password.

Instead, press Enter.
6.
Enter version when prompted for the Force Update option and press Enter. The
version option forces the update of the same version firmware (the modules in the
lab are likely at the same firmware version).
7.
Press Enter when prompted for the other options to accept the default values.
8.
When prompted, enter the credentials for the Virtual Connect domain and press
Enter.
9.
Enter YES when prompted about continuing the update and press Enter.
Note
The firmware update process might take 20 to 50 minutes.
L7 34
Rev. 15.31
Virtual Connect
10. When the update completes, press Enter to exit the VCSU interactive mode.
11. Close all open windows.
12. Log out of the CMS.
Rev. 15.31
L7 35
Exercise 7Resetting the Virtual Connect Manager

After performing the upgrade through the VCSU, failover happens. In case that you have
two VCM modules with IP addresses 192.168.200.101 and 192.168.200.102 assigned,
and you start the VCSU firmware upgrade having 192.168.200.101 as active controller,
after finishing the upgrade the VCM module 192.168.200.102 will become active.
Since you want to have the same configuration before and after the firmware upgrade,
you will perform the VCM failover.
L7 36
1.
Log into the Virtual Connect Manager through the OA interface.
2.
The Virtual Connect Manager will open running on the active VC module. Note the IP
address of the active VCM.
Rev. 15.31
Virtual Connect
Rev. 15.31
3.
To fail back the Virtual Connect module, from the Virtual Connect Manager, select
Tools o Reset Virtual Connect Manager.
4.
At the Reset Virtual Connect Manager window, select Force Failover check box and
click Yes to continue.
5.
Wait for Virtual Connect Manager to finish failover procedure.
L7 37
6.
L7 38
After the failover procedure finishes, through the OA interface open the Virtual
Connect Manager again. Notice the IP address of the active VC module.
Rev. 15.31
Virtual Connect
Exercise 8Copying server profiles

In this exercise, you will learn how to copy and rename server profiles.
1.
Click Device bays under Hardware in the left navigation frame. Note two ProLiant
Gen8 server blades that are available with no server profile assigned.
Note
There are also two ProLiant Gen9 servers without profiles you will use later.
Rev. 15.31
L7 39
L7 40
2.
Click Server Profiles under Connections in the left navigation frame. Click on the
Action pull-down menu of the Development_Profile_01 and click Copy.
3.
Copy of the Development_Profile_01 will open in Define Server Profile window.

Rename copied profile to Development_Profile_03 without changing any other
settings.
4.
Scroll down and assign new server profile to ProLiant Gen8 server blade in bay 6.
Make sure the server blade is powered down before you apply the new server profile.
Rev. 15.31
Virtual Connect
5.
Rev. 15.31
The same way, make a copy of the Production_Server_Profile_01 and rename it to

Production_Server_Profile_03. Then, apply the new Production_Server_Profile_03
to the ProLiant Gen8 server blade in bay 3.
L7 41
Additional information on Virtual Connect

For additional information, refer to:
L7 42
HP Virtual Connect Version 4.40/4.41 User Guide, P/N: 798322-002, March 2015
HP Virtual Connect Support Utility 1.11.0 User Guide, P/N 805652-001, February
2015
Rev. 15.31
Installing and configuring the Brocade 4Gb/8Gb SAN

Switch
Lab 8
Objectives
Access and configure the Brocade 4Gb/8Gb SAN Switch
Access the switch using Telnet
Set the IP address
Back up the switch configuration
Restore switch configuration from backup
Maintain the Brocade 4Gb/8Gb SAN Switch
Access the switch using Brocade SwitchExplorer
Flash the switch firmware using the Brocade SwitchExplorer
Restore the switch factory-default settings
Requirements
To complete this lab, you will need one management server (CMS) and:
HP BladeSystem c-Class enclosure with the Brocade 4Gb/8Gb SAN Switch (HP Bseries 8/24c SAN Switch) (both the module and the switch software) installed in one
of its interconnect bays
FTP server

Note

exercises.
Rev. 15.31
L8 1
Introduction
The Brocade 4Gb/8Gb SAN Switch is fully compatible with HP B-Series and Brocade
fabrics and with other switches in the enclosure. The Brocade 4Gb/8Gb SAN Switch can
function as the only switch in the fabric. It supports heterogeneous fabrics and is hotpluggable.
The Brocade SwitchExplorer Graphical User Interface (GUI) and the Fabric OS Command
Line Interface (CLI) offer complete fabric management tools for HP StorageWorks
Storage Area Networks (SANs).
For more information about HP storage solutions, visit the website:
http://www.hp.com/go/storage
L8 2
Rev. 15.31
Installing and Configuring the Brocade 4Gb/8Gb SAN Switch
Exercise 1Accessing and configuring the Brocade

4Gb/8Gb SAN Switch
In this exercise, you will identify where the Brocade SAN switch is installed, access the
switch using Telnet, set the IP address of the switch, back up the switch configuration,
and perform optional operational tasks on the switch.
Accessing the switch using a Telnet connection

To access the switch using Telnet:
1.

Note
If you have enabled Microsoft Telnet, you may use it instead of PuTTY.
2.
3.
At the PuTTY Configuration window, in the Host Name (or IP address) field, enter the
IP address of the Onboard Administrator and click Open.
Note
Administrator as well as the administrative credentials.
Rev. 15.31
L8 3
4.
If the PuTTY Security Alert window appears, click Yes to continue.
Note
The PuTTY Security Alert window will appear the first time you are accessing
OA. After you click Yes, PuTTY will store the public key of the OA in registry,
and you will not be prompted again for that IP address.
5.
L8 4
At the login prompt, type the administrative credentials (for example,

Administrator/password) and press Enter. You will connect to the Onboard
Administrator CLI.
Rev. 15.31
6.
Using either the Onboard Administrator GUI or the Classroom Configuration Guide,
determine the location of the Brocade 4Gb/8Gb SAN Switch. You can also type show
interconnect list and press Enter at the Onboard Administrator CLI to display
the list of installed interconnects.
Interconnect bay numbers for the Brocade switch: ........................................................

Note
Refer to the Classroom Configuration Guide for the interconnect switch

assignments.
Rev. 15.31
L8 5
7.
At the prompt, type connect interconnect #, where # corresponds to the

interconnect bay of the switch, and press Enter. For example: connect
interconnect 5
!
8.
Important
Some commands are case sensitive and must be entered exactly as shown.
At the Press [Enter] to display the switch console prompt (when applicable), press
Enter a few times until you get the console login prompt.
Note
Notice in the picture that to break the Serial port connection, you need to
enter the keys Control+Shift+Underscore.
L8 6
Rev. 15.31
9.
At the console login prompt, enter the administrative credentials (for example,
admin/password) and press Enter. If prompted to change the password, press
Enter and type password as the new password (the same password will be
accepted).
Note
Refer to the Classroom Configuration Guide for the login credentials.
If your login is successful, you will receive the admin> prompt.
Rev. 15.31
L8 7
Setting the IP address

To set the IP address of the switch:
L8 8
1.
At the admin> prompt, type ipaddrset and press Enter.
2.
At the Ethernet IP Address [192.168.200.105] prompt, you would type a new IP

address of the switch. However, press Enter instead to accept the default IP address.
3.
At the Ethernet Subnetmask [255.255.255.0] prompt, you would type a new subnet
mask for the switch. However, press Enter instead to accept the default subnet
mask.
4.
At the Gateway IP Address [192.168.200.1] prompt, you would type a new gateway
IP address for the switch. However, press Enter instead to accept the default
gateway IP address.
Rev. 15.31
Rev. 15.31
5.
At the DHCP [On] prompt, you would type a new value, on or off, for the DHCP
option. The value in [] within the prompt displays the options current value. Leave
this option at its current value (On) by pressing Enter.
6.
At the admin> prompt, type ipaddrshow and press Enter. This command displays
the current IP configuration settings.
L8 9
Backing up the switch configuration

HP recommends regular backups, because they ensure that a recent configuration is
available for download to replacement switches. Configuration backup is also
recommended prior to performing a firmware upgrade.
Back up the configuration to an FTP server by entering configUpload and following the
prompts. After disabling the switch using the switchDisable command, you can
restore the switch using the configDownload command. The configuration file for
restoring should originate from the same switch.
To back up the switch configuration to your FTP server:
L8 10
1.
At the admin> prompt, type help configUpload and press Enter.
2.
Explore the syntax of this command. Press q to quit help.
3.
At the admin> prompt, type configUpload and press Enter.
4.
At the Protocol (scp, ftp, local) [ftp] prompt, type ftp and press Enter.
5.
At the Server Name or IP Address [host] prompt, type the IP address of your FTP
server (for example, 192.168.200.1) and press Enter.
6.
At the User Name [user] prompt, type anonymous and press Enter.
7.
At the File Name [config.txt] prompt, if you accessed switch in bay 5, type
Brocade4Gb-cfg.txt; if in bay 6, type Brocade8Gb-cfg.txt. Press Enter.
8.
At the Section (all|chassis [all]) prompt, type all and press Enter.
9.
At the Password prompt, type leave blank and press Enter.
Rev. 15.31
The switch uploads its configuration to the specified file on the FTP server, displays
a success message, and returns to the switch prompt.
Rev. 15.31
L8 11
10. Using Windows Explorer, browse to the C:\ftproot folder and open the Brocade4Gbcfg.txt or Brocade8Gb-cfg.txt file with a Linux-compatible editor such as AB-Edit or
WordPad. Following is a sample file.
11. Close the file and return to your CLI session.
L8 12
Rev. 15.31
Restoring switch configuration from backup

Restore the configuration from an FTP server by loading the configuration file saved in
the previous section. After disabling the switch using the switchdisable command,
you can restore the switch using the configdownload command. The configuration
file for restoring should originate from the same switch.
To restore the switch configuration from your FTP server:
Rev. 15.31
1.
At the admin> prompt, type switchdisable and press Enter.
2.
At the admin> prompt, type configdownload and press Enter.
3.
At the Protocol (scp, ftp, local) [ftp] prompt, type ftp and press Enter.
4.
At the Server Name or IP Address prompt, type 192.168.200.1 and press Enter.
5.
At the User Name prompt, type anonymous and press Enter.
6.
At the File Name prompt, type <name of the file you uploaded
previously> and press Enter. Example: Brocade4Gb-cfg.txt or
Brocade8Gb-cfg.txt
7.
At the Section (all|chassis [all]): prompt, type all and press Enter.
8.
Confirm download of backed-up configuration by pressing y, and then press Enter.
9.
At the Password prompt, leave blank and press Enter.
L8 13
10. After you have restored the switch configuration successfully, at the admin>
prompt, type switchenable and press Enter.
11. Break the Serial connection by using Control+Shift+Underscore, and then
type D. Then type exit to close OA CLI session.
L8 14
Rev. 15.31
Exercise 2Maintaining the Brocade 4Gb/8Gb SAN

switch
In this exercise, you will perform maintenance tasks on the Brocade SAN switch, such as:
Accessing the Brocade SwitchExplorer interface
Flashing the switch firmware using the Brocade SwitchExplorer
Resetting the switch to factory-default settings
Accessing the Brocade SwitchExplorer interface

To access the Brocade SwitchExplorer from the Onboard Administrator GUI:
1.
Log into the Onboard Administrator GUI with administrative credentials.

Note
Refer to the Classroom Configuration Guide for login credentials.

2.
Rev. 15.31
In the Systems and Devices pane, expand Enclosure Information o Interconnect

Bays o 5 or 6. Then, click Management Console.
L8 15
3.
If a Warning Security screen displays, check the Always trust content from this
publisher option and click Run.
4.
At the Please Login screen, enter administrative credentials (for example,

admin/password) and click OK.
Note
Refer to the Classroom Configuration Guide for the login credentials.
The Brocade SwitchExplorer opens in a new window.
L8 16
Rev. 15.31
5.
From the Tasks toolbar, click Switch Admin.
The Switch Administrator screen displays. Leave this screen open.
Rev. 15.31
L8 17
Flashing the switch firmware using the Brocade SwitchExplorer

To flash the switch firmware using the Brocade SwitchExplorer:
1.
L8 18
Using Windows Explorer, copy the C:\Classfiles\Firmware\B-Series Fibre Channel

switches (Brocade)\v6.2.2f folder to the C:\ftproot folder. There should be many
subdirectories in this folder containing firmware for many Brocade switches.
Rev. 15.31
2.
Return to the Brocade SwitchExplorer. You should be at the Switch Administrator

screen. There, click the Firmware Download tab.
What is the current version of the firmware?

Primary partition: ............................................................................................................
Secondary partition: ........................................................................................................
Rev. 15.31
L8 19
3.
4.
L8 20
In the Download New Firmware section:

a.
Type the IP address of your FTP server in the Host Name or IP field (for
example, 192.168.200.1).
b.
Type anonymous in the User Name field.
c.
Leave blank Password field.
d.
Ensure the File Transfer Protocol (FTP) is selected in the Protocol Type field.
e.
Type \v6.2.2f in the Specify Firmware Path field. You do not need to specify
the C:\TFTP-Root path because it is already known to the FTP server. Also, you
do not need to specify a subfolder within the v6.2.2f folder because the utility
can find the necessary files there on its own.
f.
Click Download.
At the Confirm Firmware Download screen, click Yes.
Rev. 15.31
The Switch Administrator screen displays related messages and progress.
The firmware download process takes approximately 510 minutes but may take up
to 30 minutes as indicated. Your patience is required here.
Note
You can monitor the update process by connecting to the switch with CLI and
issuing the firmwareDownloadStatus command.
You may lose the connection before you get to the screenshot on the page. If so, just log
back in to see the process complete.
Rev. 15.31
L8 21
When the firmware download completes, the session terminates automatically.

When this happens, you are presented with these messages:
5.
L8 22
At the Alert popup window, click OK.
Rev. 15.31
6.
Log back into Brocade SwitchExplorer and use the Switch Administrator to confirm
the firmware update.
Note
After the firmware update, the switch IP address in the OA GUI may not be
correct. You can, however, connect to the OA CLI (using Telnet) and then issue
the connect interconnect x command to determine the switch address
assigned by EBIPA. If you issue the reboot command to reboot the switch,
the OA GUI will update with the correct switch IP address.
The screenshots below show resetting the switch using the OA GUI.
7.
Rev. 15.31
Close Switch Administrator and log out of the Brocade SwitchExplorer. Also log out of
the Onboard Administrator GUI and close the associated window.
L8 23
Flashing the switch firmware using CLI (for your reference only)
To download the switch firmware from an FTP server or from a local Network File Server
(NFS) directory to the switch's nonvolatile storage area, you can Telnet into the switch or
connect the serial line to a PC. Then, you would run this command:
firmwaredownload [[-sbni] host,user,pfile,passwd]
The new firmware is in the form of RPM packages with names defined in a pfile. A pfile is
a binary file that contains specific firmware information (time stamp, platform code,
version, and so forth) and the names of firmware packages to be downloaded. These
packages are made available periodically to add features or to remedy defects.
The HP Storage SAN switches have two partitions of nonvolatile storage areas
primary and secondary to store two firmware images. Firmware download always
loads the new image into the secondary partition and swaps the secondary partition to
be the primary. It then reboots the Controller Processor (CP) and activates the new
image. Finally, it performs firmware commit automatically to copy the new image to the
other partition unless "-s" is used.
The command supports both non-interactive and interactive modes. If it is invoked
without any command line parameters, or if there are any syntax errors in the
parameters, the command will go into the interactive mode in which the user is
prompted for inputs.
Note
HP recommends that before upgrading the switch firmware, you save a copy
of the switch configuration file to the FTP server using the configUpload
command.
L8 24
Rev. 15.31
Resetting the switch factory-default settings

Use the following procedure to reset the Brocade SAN switch to factory-default settings.
The configDefault command is used to reset some of the switch functional
configuration parameters to their default values. All parameters are set to defaults
except for:
Ethernet MAC address, IP address, subnet mask, and gateway address
License keys and OEM customization
SNMP configuration
System name
World Wide Name and zoning configuration
Quickloop configuration
Password (firmware 2.6 and higher)

Caution
The configDefault command resets the switch to factory-default settings, not to HP

default settings.
Within a fabric, all B-series switches must use the HP default setting of ON for In-Order
Rev. 15.31
Delivery (IOD). Dynamic Load Sharing (DLS) must be set to the HP default setting of ON for
non-Continuous Access configurations and OFF for Continuous Access configurations (HP
Storage EVA and XP).
HP-UX reserves domain ID 8. Thus, it is not recommended to use dynamic domain
assignments. Use static domain assignment and start with domain ID of 10.
Within a fabric, assign a unique domain number (domain ID) and a unique World Wide Name
(WWN) to each switch. All switch configuration parameters for the same switch models
must be the same. Do not configure any switches with a domain ID of 8 (reserved by HPUX).
1.
If necessary, log into your Brocade SAN switch with PuTTY (Telnet) and log in with
2.
At the admin> prompt, type switchDisable and press Enter.
L8 25
L8 26
3.
At the admin> prompt, type configDefault and press Enter.
4.
At the admin> prompt, type switchEnable and press Enter.
Rev. 15.31
Rev. 15.31
5.
At the admin> prompt, type cfgclear and press Enter. This command explicitly
deletes zoning information on the Brocade SAN switch. Confirm this operation by
typing yes and pressing Enter.
6.
Because some configuration parameters are cached by the system, you need to
reboot the switch. At the admin> prompt, type reboot and press Enter.
7.
If you are logged directly into the SAN switch with PuTTY, close the PuTTY window. If
logged through the OA connect interconnect command, use the Control+Shift+_
keyboard sequence and type D for Disconnect from the Brocade switch. To finish the
OA CLI session, type exit, and press Enter.
L8 27
L8 28
Rev. 15.31
HP BladeSystem c-Class Enclosure-Based USB Devices

Lab 9
Objectives
After completing this lab, you should be able to access and use the HP BladeSystem cClass enclosure-based USB devices with the Insight Display and the Onboard
Administrator GUI.
Requirements
USB storage device inserted into the Onboard Administrator USB port with a sample
ISO image
Note
The specific content (ISO image(s)) on this USB device is only required to
demonstrate how to connect to, use, and disconnect from the enclosurebased USB device. It does not serve any other purpose in this lab.
Note

exercises.
Rev. 15.31
L9 1
Introduction
The HP BladeSystem c3000 and c7000 enclosures have a USB port in the front of the
enclosure (c3000) or in the rear of the enclosure (c7000) to which you can attach a USB
storage device such as a CD/DVD-ROM or a USB storage key. In addition to the external
USB port, the c3000 enclosure might have an actual USB-based physical drive installed.
To use this storage device, you need to connect it to one or multiple server blades by
using the Insight Display or Onboard Administrator GUI. You can then use it to:
Perform operating system installations
Install additional software
Perform critical operating system updates and patches
Update server platform ROMs
The enclosure-based USB support offers local drive access to server blades by using the
virtual media scripting capability of HP Integrated Lights-Out (iLO). The USB support
connects directly to the USB of the server blade and provides significantly improved data
throughput as compared to iLO virtual media that uses physical disks or ISO files over a
network connection.
Additionally, you can view the USB device status by using the Health Summary screen
provided by the Insight Display. The Health Summary screen displays the USB device as a
color-coded DVD icon.
L9 2
Rev. 15.31
Exercise 1Accessing and using the enclosure-based

USB device with the Onboard Administrator GUI
In this exercise, you will learn how to access and use the enclosure-based USB device
with the Onboard Administrator GUI.
Rev. 15.31
1.
At the Onboard Administrator GUI homepage, in the Systems and Devices pane,
expand Enclosure Information o Enclosure Settings and click DVD Drive to access
the DVD Drive screen. Review the information presented on this screen.
2.
Explore the Device List table which displays all server blades (listed by bay number)
installed in the enclosure. Using this table, you can:
Determine the power state of the server blade (the Power State column)
Launch the Integrated Remote Console (IE) or the Remote Console Applet (Java)
(the Remote Console column). Do not launch it at this time.
Identify the iLO DVD status (the iLO DVD Status column)
Determine if a server blade is accessing the physical DVD or virtual media URL
(the Device or Image URL column)
L9 3
3.
L9 4
Power on/off server blades (the Virtual Power pull-down menu)
Configure one-time boot settings for server blades (the One Time Boot pulldown menu)
Connect or disconnect the physical DVD medium to server blades (the DVD pulldown menu). In your environment, the SPP version shown on the USB medium
might differ.
After exploring features available, select one or more server blades assigned to your
team by clicking the checkbox in the front of the server blade bay number. This
action highlights the entire row.
Rev. 15.31
4.
From the DVD drop-down menu, select Connect to

d1/817787_001_spp_2015.04.0....iso. This selection represents a USB storage
device (key) with the SPP .iso image that is part of your classroom environment. The
contents of the USB device may, however, vary. Your USB key will probably have an
ISO image containing SPP or full name of the downloaded SPP ISO. Use that file.
Also, should a DVD-ROM drive be connected to the USB port instead, your option
would be Connect to Enclosure DVD.
Note
If the SPP image file is not available, ask HPVL support to check the attached
USB key format and content.
5.
Rev. 15.31
Wait for the iLO DVD Status and Device or Image URL columns to update. The iLO
DVD Status column should display Connected. The Device or Image URL column
should display:
Enclosure DVD (if you connected to a DVD drive)
http://xxx.xxx.xxx.xxx/media/usbkey/d1/xxx (if you connected to an ISO

image on a USB storage key)
L9 5
6.
If the server blade has an operating system, you can launch the Integrated Remote
Console (IRC), log in, and see if the server blade mounted the specified ISO image.
Note
If the server was powered off and you turn it on, depending on boot order it
might boot to the attached virtual CD Drive with HP SPP boot image. More
about this in the following steps.
Is the specified ISO image mounted?...............................................................................

Note
If the Integrated Remote Console would not launch directly because of the
IE9 security issues, as a workaround click the Web Administration link in
Device Bays o <server> o iLO to access the iLO and start IRC from there.
L9 6
Rev. 15.31
Note
Completion of the following steps is optional.

7.
8.
To have the server blade boot from the attached ISO image:
a.
If the server blade is powered off, power it on by selecting the checkbox in the
front of the server blade bay number and clicking Momentary Press from the
Virtual Power drop-down list.
b.
If the server blade is booted into an operating system, connect to it and restart
it.
To monitor the server blade as it boots, select either Integrated Remote Console or
Remote Console in the Remote Console drop-down list and click the Launch link.
If you booted a ProLiant server blade from the SPP ISO image, the server blade
boots from the HP Service Pack for ProLiant and updates its firmware automatically
(if any of the firmware was out-of-date). When the update is finished, the enclosure
DVD disconnects automatically. You can monitor this activity using the Integrated
Remote Console and close it when finished.
Note
One advantage of the enclosure-based USB device is that you can place an
ISO image of the HP Service Pack for ProLiant DVD onto the USB device,
connect ProLiant server blades within the enclosure to it, and boot them from
this image to automatically update the firmware of selected ProLiant server
blades in the enclosure with relatively few mouse clicks.
HP recommends connecting no more than 8 blades at a time to a USB key
image. For server updates, the best practice is to run the SPP online first (if
an OS is present), then to reboot it in order to update any firmware that could
not be done online.
Note
OA supports FAT32 and EXT2 file systems only for USB keys. If your ISO image
is large, you might need to reformat USB key for EXT2 (Linux) file system.
9.
Depending on what is executed from the USB device, it automatically disconnects or

stays connected. If you need to manually disconnect the USB device, from the DVD
drop-down menu, select Disconnect Blade from DVD/iso. At the Are you sure dialog
box, confirm your action by clicking OK.
10. Sign out from the Onboard Administrator GUI and close your browser session.
Rev. 15.31
L9 7
Exercise 2 Accessing and using the enclosure-based

USB device with the Insight Display (optional)
In this exercise, you will learn how to access and use the enclosure-based USB device
with the Insight Display. Because your equipment is remote, you will access the Insight
Display through the Onboard Administrator GUI.
1.
2.
Using your browser, connect to the Onboard Administrator GUI and log in with
Note
Administrator and the administrative credentials.
3.
L9 8
At the Onboard Administrator GUI homepage, click Insight Display.
Rev. 15.31
Rev. 15.31
4.
If necessary, navigate to the Insight Display Main Menu. You may need to click the
OK button to activate the Insight Display first.
5.
At the Main Menu screen, select Health Summary and click OK.
L9 9
The Health Summary screen displays, showing the state of the USB device (the USB
device is presented by the DVD icon in the middle of the screen).
The color of the DVD icon on the Insight Display varies with the status of the USB
device:
Blackdevice is not installed in the enclosure.
Light graydevice is present but no media is loaded.
Dark greenmedia is present but the device is not connected to server bays.
Light greendevice contains media and is connected to server bays.
What is the current status of your USB device? ..............................................................

..........................................................................................................................................
L9 10
6.
Navigate back to the Main Menu.
7.
To connect a USB Key Image/DVD drive to a server blade using the Insight Display, at
the Main Menu screen, navigate to the Enclosure Settings option and click OK.
Rev. 15.31
8.
Navigate to the DVD Drive option and click OK.
9.
Select a single blade or ALL Blades option to connect USB key to a single blade
server or to all and click OK.
10. At either one Blade DVD Connection Insight Display screens, select Cancel.
Note
Insight Display options are covered in more detail in the HP BladeSystem cClass Insight Display lab.
11. Return to the Onboard Administrator GUI homepage.
Rev. 15.31
L9 11
L9 12
Rev. 15.31
Using the HP Service Pack for ProLiant

Lab 10
Objectives
Use the HP Service Pack for ProLiant (SPP) to remotely deploy firmware to the
Onboard Administrator modules and server blade iLOs with HP System Update
Manager (SUM) GUI and CLI
Use the HP Service Pack for ProLiant from USB in the offline mode
Use the HP Service Pack for ProLiant locally in the online mode
Requirements
USB key containing the SPP ISO image connected to the primary OA
Additionally, you will need the Classroom Configuration Guide and the HP Service Pack
for ProLiant ISO image stored on your CMS.
Note

Screenshots this lab document are for your reference and might slightly
exercises.
Note
This lab was written using the HP Service Pack for ProLiant 2015.04.0
Rev. 15.31
L10 1
Verifying the DHCP service

Before using the HP SPP tools, verify that DHCP service is running on your CMS work
computer. It might be needed to find the nodes later in this lab.
L10 2
1.
2.
Start the Server Manager application at the lower left corner or Start menu.
3.
Click the DHCP Server role in the Roles Summary section.
Rev. 15.31
4.
Rev. 15.31
If the DHCP Service is stopped, click the Start button to run it.
L10 3
Exercise 1Using the HP Service Pack for ProLiant

remotely
In this exercise, you will deploy firmware for the following HP BladeSystem c-Class
infrastructure components using the HP Service Pack for ProLiant:
Onboard Administrator module
Server blades
You will use the HP Service Pack for ProLiant remotely from your CMS. To deploy drivers
to target server blades they need to be running and have an operating system installed.
In all cases, the HP Service Pack for ProLiant uses the HP Smart Update Manager (HP
SUM) for the actual firmware maintenance.
Note
When updating the HP BladeSystem c-Class infrastructure firmware, it should

be noted that several firmware components have prerequisites which require
the firmware version of another component to be at a specific level.
Hence, it should be ensured that the firmware is updated in a sequential
manner so that such prerequisites are met. Using the HP Service Pack for
ProLiant ensures that component firmware is updated in the correct
sequence which ensures that all updates are successful.
Using the GUI to update firmware

To use the graphical user interface of HP SUM:
1.
L10 4
Using the Windows Explorer, navigate to C:\classfiles\HP Service Pack for ProLiant
(SPP) and select the SPP ISO image file.
Rev. 15.31
Rev. 15.31
2.
Right-click the ISO file and select Mount o Virtual CloneDrive E: (for example), or
use the Open icon in the toolbar.
3.
Using Windows Explorer, navigate to C:\classfiles and create subfolder

C:\classfiles\OS\SPP.
L10 5
4.
L10 6
Open a second Windows Explorer window and navigate to BD-ROM Drive (E:) with
SPP. Copy the contents of HP SPP DVD to C:\classfiles\OS\SPP.
Rev. 15.31
5.
Using Windows Explorer, open C:\classfiles\OS\SPP, go to the

C:\classfiles\OS\SPP\hp\swpackages folder and run the hpsum.bat file (as
administrator, if not logged in) to launch the HP Smart Update Manager engine.
The script starts and launches the appropriate HP Smart Update Manager engine.
Rev. 15.31
L10 7
6.
L10 8
Access to the HP SUM engine is opened in a web browser window. At the initial
screen, click Get started.
Rev. 15.31
7.
For the deployment mode keep Interactive. You will use the default HPSUM location
and baseline. So, click OK.
The inventory of baseline will start and after that the inventory of node.
Rev. 15.31
L10 9
8.
After the initial inventory is completed, open the main menu in the top left corner
and select Nodes.
Note
A node is any device that has firmware/software components installed on it.

A server is an example of a node. A node could also be an iLO management
processor, an Onboard Administrator (OA) or a Virtual Connect module.
L10 10
Rev. 15.31
9.
Localhost is already added as a node, but you will update the enclosure
infrastructure and target servers instead. From the Actions menu in the upper right
select Add.
10. As the first node, add your Onboard Administrator. Enter OA IP address and select
type From a drop-down list, select Find nodes on network with an IP range.
Rev. 15.31
L10 11
11. To find other nodes easier, keep Auto Add Associated Nodes checked. You might
optionally select Baseline firmware or Additional Packages (not part of the baseline
bundle). In this case, you will use only the provided HP SPP content.
12. Scroll down and enter administrator credentials for the selected node (Onboard
Administrator). Skip the option to assign node to node groups. Click the Add button.
L10 12
Rev. 15.31
13. The node is found and the next step is to start inventory. Select Inventory from the
Actions menu or task notification area.
14. Verify the selected options and click the Inventory button.
Rev. 15.31
L10 13
15. The inventory process starts and might take a couple of minutes to discover nodes
associated to OA (servers, interconnect modules). Some nodes are not discovered as
unsupported types, for example HP ProCurve blade switches in bays 3 and 4. Some
other nodes are discovered but not identified by HP SUM (marked with the red dots)
because credentials are not provided, for example SAN switches in bays 5 and 6.
Some of the nodes might not need any updates (marked with green squares). Blade
servers are discovered by their iLOs.
Browse the nodes in the list by selecting and clicking Review/Deploy in the Actions
menu or task notification area. The inventory shows that nodes are already at the
baseline versions if they are updated previously.
L10 14
Rev. 15.31
16. Most of the nodes are up-to-date and have Force option if you insist to downgrade
or rewrite the current firmware with the selected baseline. Notice the additional
options available for some node types. For example, VC modules have Activation
order and Activation Delay. You already updated VC firmware in a previous lab,
forcing rewrite is not necessary, so click Cancel.
Rev. 15.31
L10 15
17. For this exercise, select any of the blade servers, click Review/Deploy, then enable
Force to rewrite the current firmware and click the Deploy button.
The deployment starts and you can follow the progress in notification area.
L10 16
Rev. 15.31
18. After a few minutes, the deployment is completed and the node marked with a little
green rectangle instead of the yellow triangle. You can also access the log.
19. After reviewing the log, click Close.
Rev. 15.31
L10 17
Using the GUI to update software

As you might noticed, the OA associated nodes are blade servers iLOs which you updated.
If you have some blade servers up and running an operating system, you might discover
their NICs and deploy software (tools and drivers) updates online. For this exercise, you
might first start a couple of G7 blade servers which have Windows OS installed.
1.
L10 18
On the HP Smart Update Manager go to the Nodes screen and select Actions o Add.
Rev. 15.31
Rev. 15.31
2.
For the type of add, this time select an IP range to search for nodes.
3.
Click the Find Nodes button.
L10 19
4.
Consult your Classroom Configuration Guide to find the DHCP IP range reserved for
blade servers NICs in your enclosure. Enter the start and stop IPs and click Search.
After some time, the found blade servers (up and running OS) nodes are listed.
L10 20
Rev. 15.31
Note
You might compare found DNS Node Names with Device Bays in OA GUI.
5.
Rev. 15.31
For this exercise, select one of the nodes and click Add Nodes.
L10 21
L10 22
6.
Enter administrator credentials to access the target server (consult your Classroom
Configuration Guide) and click the Add button.
7.
Then, click Close and return to the Nodes screen.
Rev. 15.31
Rev. 15.31
8.
Perform the Inventory process for the added node as before.
9.
Then, select Review/Deploy.
L10 23
10. Review the Installation options where you can select Downgrade or Rewrite for
firmware or software or both.
11. Scroll down to review the Baseline Library components already selected for
upgrade or might be Forced. Examine the Reboot Options, then click Deploy.
L10 24
Rev. 15.31
As before, you can follow the deployment in the task notification area.
Updating all other discovered nodes is done in a similar way.
Rev. 15.31
L10 25
12. To provide credentials where needed, you should select that node and in the Actions
menu (or notification area) click Edit. For example, a Brocade SAN switch.
13. Scroll down, enter credentials (consult Classroom Configuration Guide) and click OK.
L10 26
Rev. 15.31
After some time the inventory is done and the node should be recognized.
Rev. 15.31
L10 27
Using the CLI command line

The HP SUM CLI and Input file modes allow you to deploy updates from a baseline to the
local and remote nodes. These methods require the silent command option.
In CLI mode, add all parameters in one command line to execute the entire sequence on
multiple nodes without any user interaction. The general command line syntax is:
hpsum /s /use_location <baseline_directory> /r
(for Linux use two hyphens instead of slash)

Parameters:
/sinitiates the CLI (silent) mode instead of GUI
/targetprovides the node IP address with optional details, like user credentials
/on_failed_dependencywhat to do if a failed dependency is encountered
/rtells whether to reboot a node after deploying updates
/reportgenerates HP SUM reports
/hlaunches the HP SUM CLI help file.
To use the command line interface of HP SUM to silently update a remote node from the
baseline folder:
1.
L10 28
At your CMS, open a Command Prompt window and change your current directory to
C:\classfiles\OS\SPP\hp\swpackages.
Rev. 15.31
2.
At the prompt, you should type a command line in general format:

hpsum /s /target <ip_address> /targettype <type> /user
<userid> /passwd <password>
where:
/targettype <type>an optional parameter, <type> might be: Windows,
Linux, iLO, HPUX, fc_switch, oa, SD2, virtual_connect (primary module), sas_switch,
VMware, Moonshot.
For example, to update a blade server iLO:
hpsum /s /target 192.168.200.11 /targettype iLO /user
Administrator /passwd password
(verify these parameters by consulting your Classroom Configuration Guide)
Wait until the command completes.
3.
Repeat the previous command for the remaining target devices you wish to update.
This is an optional step.
4.
At the prompt, type exit and press Enter to close the Command Prompt window.
Note
These actions produce the same results as the previous exercise, but by using
the HP SUM command line interface.
Note
The log files after execution are save by default to folder:

%SYSTEMDRIVE%\CPQSYSTEM\hp\log\<device_net_Address>
Rev. 15.31
L10 29
Using the CLI input file (optional)

Use Input file mode to add all parameters to a text file, and then call HP SUM using the
inputfile command with the text file name as the parameter. Using the Input file
method allows you to provide a larger number of nodes to update.
HP SUM CLI with Input files allows you to create file scripts for updating multiple nodes
within a single operation. After creating a script file in plain text editor, use it with the
inputfile <filename> parameter in an HP SUM command line.
For example (in Windows): hpsum /inputfile <filename>
You can add full paths. Enclose the <filename> field in double quotes to enable paths
with spaces.
The Input file content is similar to markup languages that require headers and trailers to
match.
1. (optional step) You can prepare a sample Input file using Notepad or other editor:
#Input file sample
SILENT = YES
SKIPTARGET = NO
SOURCEPATH = C:\classfiles\OS\SPP\HP\swpackages
REBOOTALLOWED = YES
REBOOTDELAY = 30
REBOOTMESSAGE = Install complete, server will reboot in 30
seconds
[TARGETS]
HOST = 192.168.200.14
UID = Administrator
PWD = password
[END]
[TARGETS]
HOST = 192.168.200.15
UID = Administrator
PWD = password
[END]
2. (optional step) After an Input file is created and saved, you would execute the
following command from C:\classfiles\OS\SPP\HP\swpackages folder:
hpsum /inputfile <filename>
Note
To modify an Input file without editing the file, use all of the command line
options along with the Input file. The command line options take precedence
over the commands in the Input file.
For more information and details use the HP Smart Update Manager CLI Guide
Version 7.2.0 document, HP Part Number: 814105-001, March 2015.
L10 30
Rev. 15.31

from USB in the offline mode
In this exercise, you will deploy firmware to the target server blade hardware
components using the HP Service Pack for ProLiant ISO image stored on the USB key
connected to the BladeSystem c-Class enclosure.
Attaching the ISO image to the server blade using the Onboard
Administrator GUI
To boot the HP Service Pack for ProLiant on the target server blade:
Rev. 15.31
1.
Using your browser, connect to the Onboard Administrator GUI and log in with
2.
As explained in a previous lab, at HP BladeSystem Onboard Administrator main page,

navigate to Enclosure Information o Enclosure Settings o DVD Drive.
L10 31
3.
At the Enclosure Settings screen, select the checkbox representing the bay number
of your target ProLiant server blade (for example, bay 1) and use the DVD pull-down
menu to connect to the USB key containing the ISO image.
The iLO DVD Status value changes to Connected.
4.
From the Device List screen, click Launch to start the Integrated Remote Console of
the target server with the connected ISO image.
Note
If the Integrated Remote Console would not launch directly because of the
IE9 security issues, as a workaround click the Web Administration link in
Device Bays o <server> o iLO to access the iLO and start IRC from there.
L10 32
Rev. 15.31
5.
From the Integrated Remote Console menu, reboot the server if it is powered on. If it
is powered off, select Power Switch o Momentary Press and watch the server
booting. You might also continue to use the power control functions in the DVD drive
menu Virtual Power of the OA.
Rev. 15.31
Important
If the target server blade has an operating system, it is recommended to

issue the reboot from within the operating system.
L10 33
6.
When the target ProLiant server blade booted successfully from the HP Service Pack
for ProLiant image, you are presented with two options:
Automatic Firmware Update Version 2015.04.0
Interactive Firmware Update Version 2015.04.0

Note
When the 30-second timeout expires, the default option (Automatic

Firmware Update) will launch. To stop the timer, either select the desired
option or use the arrow keys to move your selection.
L10 34
Rev. 15.31
Using the HP Service Pack for ProLiant in the interactive mode

To use the HP Service Pack for ProLiant in the interactive mode:
1.
Scroll down to select Interactive Firmware Update Version 2015.04.0 and press
Enter.
The HP Service Pack for ProLiant begins to boot
Rev. 15.31
L10 35
L10 36
2.
At the initial screen, select the preferred language and accept the EULA. Then, click
Next.
3.
Click Firmware Update.
Rev. 15.31
4.
After HP SUM is loaded (it might take a couple of minutes), Inventory of baseline and
Inventory of node (localhost) are performed. It might take several minutes. When
the process is complete, click the Next button.
Note
The screen might go black for inactivity. Just click inside or press any key.
Rev. 15.31
L10 37
5.
Review the Deployment Summary. If node is already at baseline version, you might
Force some of the packages to rewrite. Then, click Deploy.
The deployment starts.
L10 38
Rev. 15.31
6.
When completed, check View log. Then click Reboot and confirm.
Note
Usually, you would uncheck Virtual Drive (or Disconnect DVD in OA). This time
let it boot again to review the Automatic mode of SPP.
Rev. 15.31
L10 39
Using the HP Service Pack for ProLiant in the automatic (unattended)

mode
To use the HP Service Pack for ProLiant in the automatic (unattended) mode:
1.
Using the steps provided earlier in this exercise, mount the HP Service Pack for
ProLiant (the ISO image) using the Onboard Administrator GUI (if not mounted) and
boot the target server blade from it.
2.
At the following screen, select Automatic Firmware Update Version 2015.04.0 and
press Enter or wait until HP SUM automatically starts the boot process after 30
seconds.
The HP Service Pack for ProLiant begins to boot.
L10 40
Rev. 15.31
HP SUM analyzes the system for unattended installation and proceeds with
inventory.
Rev. 15.31
L10 41
If updates are required, HP SUM automatically proceeds and restarts the system.
3.
L10 42
Check if the Virtual Drive is automatically disconnected or use the OA GUI to

disconnect from the USB key and boot the server blade from PXE or the local
operating system (if applicable).
Rev. 15.31

locally in the online mode
If your target server blade has an operating system, such as Microsoft Windows Server
2008 R2, you can use the HP Service Pack for ProLiant and HP SUM in the online mode.
Both GUI and CLI methods are supported.
The steps are similar to the steps provided in the previous exercisesyou can map a
network drive to a location containing the HP Service Pack for ProLiant, or the ISO image,
copy the DVD or ISO image contents to your local hard drive, or use Virtual Media. Then,
launch the HP Service Pack for ProLiant or HP SUM directly. Use the appropriate
interfaceGUI or CLIas described in the previous exercises.
1.
Rev. 15.31
If necessary, log into the Onboard Administrator GUI with administrative privileges.
L10 43
2.
L10 44
At the HP BladeSystem Onboard Administrator screen, navigate to the server blade

you want to use to run HP Service Pack for ProLiant in the online mode. Under
Systems and Devices, expand Enclosure Information o Device Bays o 1. UP03STUDENTS-2 (for example). At the Device Bay Information screen, check if the target
server blade is up and running. To finish this lab, the server blade must be running
with an operating system.
Rev. 15.31
3.
To attach the HP Service Pack for ProLiant ISO image stored on the USB key
connected to the enclosure, select the Virtual Devices tab, and scroll down to the
Connect to Device option. From the drop-down menu, select Connect to
usb://d1/SPP.iso and click Apply.
The iLO DVD Status value changes to Connected and the Device or Image URL value
displays the URL of the mounted ISO image.
Rev. 15.31
L10 45
4.
Scroll down and click Integrated Remote Console.
The Integrated Remote Console opens in a new window. Ignore security warnings.
L10 46
5.
Log into the target server blade by sending the Ctrl+Alt+Del sequence from the
Integrate Remote Console GUI.
6.
Log in with administrative credentials. Ignore any Windows registration screens.
7.
If necessary, close the Initial Configuration Tasks and Server Manager windows.
Rev. 15.31
8.
Using Windows Explorer on the remote server, navigate to the assigned virtual drive,
for example E:\hp\swpackages. Locate hpsum.bat and double-click to launch it.
9. Wait for the HP Smart Update Manager GUI to start. It might take several minutes. If
required allow the blocked content by adding website to the trusted sites zone.
Rev. 15.31
L10 47
9.
At the HP SUM home screen, scroll down and click the Get started button.
10. Keep the Interactive mode selected and click OK.
L10 48
Rev. 15.31
HP SUM starts Inventory of baseline and then Inventory of node (in this case
localhost is the remote server).
11. After the Inventory process is done, click Next.
Rev. 15.31
L10 49
12. Review the content for deployment. If the node is already at baseline version, you
might Force some of the components to be deployed and click the Deploy button.
13. When the deployment is done, you can view the log file and the click Reboot.
Confirm with Yes, Reboot.
L10 50
Rev. 15.31
14. Make sure to disconnect virtual drive from the IRC menu or OA web page. If not,
depending on boot order the server might boot to SPP image in offline update mode.
15. After the target server has booted, close the Integrated Remote Console window,
sign out and close the Onboard Administrator GUI.
Rev. 15.31
L10 51
L10 52
Rev. 15.31
Reinstalling HP Intelligent Provisioning

Lab 11
Objectives
After completing this lab, you should be able to reinstall HP Intelligent Provisioning.
Requirements
Access to the HP Virtual Lab (HPVL) environment
HP ProLiant Gen8 or Gen9 server
HP Intelligent Provisioning recovery media ISO file
Introduction
Although not often, there may be times when you need to reinstall or upgrade HP
Intelligent Provisioning manually. In this lab, you will use the Intelligent Provisioning
Media to reinstall Intelligent Provisioning.
Note
You may see the screenshots in inverted colors, which is done for readability
and printing purposes to save your printer toner.
Rev. 15.31
L11 1
ExerciseReinstalling HP Intelligent Provisioning

To reinstall HP Intelligent Provisioning:
1.
Access the Integrated Remote Console window of your team-assigned ProLiant Gen8
server and select Virtual Drives o Image file CD-ROM/DVD from the menu.
2.
Navigate to the C:\classfiles\Intelligent Provisioning folder, highlight the

Intelligent Provisioning Update DVD media iso file HPIP162.2015_0325.33.iso, and
click Open.
Note
The other file HPIP210.2015_0118.82.iso is for ProLiant Gen9 servers.
L11 2
Rev. 15.31
3.
Use the Power Switch menu from the Integrated Remote Console window and reset
the server if it is powered on or power on the server if it is off.
4.
Press F11 when prompted to access the Default Boot Override Options.
Note
This step depends on your boot order and might not be necessary if booting
from CD-ROM is on top.
5.
Rev. 15.31
The Boot Menu displays. Press 1 to select One Time Boot to CD-ROM and boot to the
virtual image.
L11 3
The program will begin loading automatically.
The Update process will establish communication with iLO, verify system settings,
and start update (flash) process automatically. It might take up to 10 minutes.
L11 4
Rev. 15.31
Once the update is complete, system reboots automatically and reminds you to
remove CDROM (or disconnect from the image you mounted using virtual media).
6.
Rev. 15.31
During reboot, press F10 to access Intelligent Provisioning.
L11 5
7.
L11 6
If the Set Preferences screen displays:
Accept the EULA, if not accepted already.
Set the System Software Update to Disable (in this environment).
Press the lower-right arrow to continue.
Rev. 15.31
8.
Rev. 15.31
Accept the Activate Intelligent Provisioning and Remote Support register later
options, if asked. Then, the Intelligent Provisioning Home screen displays.
L11 7
9.
L11 8
To reboot or shutdown the server, click the Power icon in the top-right corner.
Rev. 15.31
Installing Microsoft Windows Server 2012 R2 with HP

Intelligent Provisioning
Lab 12
Objectives
After completing this lab, you should be able to install Microsoft Windows Server 2012
R2 with HP Intelligent Provisioning.
Requirements
Your team-assigned HP ProLiant Gen8 server
Microsoft Windows Server 2012 R2 Standard distribution in an 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 can use the
embedded wizard for step-by-step configuration of the operating system deployment
and to perform an automated installation on the server.
Deployment Settings Packages are used for configuring the automated installations and
saving them for later use or for transferring (by an USB key) them to another server.
In this lab, you will use HP Intelligent Provisioning to install the Microsoft Windows
Server 2012 R2 operating system. You may also explore the HP Intelligent Provisioning
Deployment Settings option for creating and reusing Deployment Settings Packages
when provisioning servers.
Rev. 15.31
L12 1
ExerciseInstalling Microsoft Windows Server 2012

using HP Intelligent Provisioning
To install Microsoft Windows Server 2012 R2 to your target ProLiant Gen8 server, you
will mount a virtual drive with the operating system (OS) distribution files and use the HP
Intelligent Provisioning wizard.
This exercise will be completed from the Integrated Remote Console (IRC) of your target
server. Perform these steps:
1.
If you have logged out of the HPVL environment, complete these steps to access the
IRC of your target server:
a.
Log into your CMS server with your credentials.
b.
Open Microsoft Internet Explorer and log into the OA of your c7000 enclosure.
c.
From the OA, expand the Device Bays pane. Then, expand your team-assigned
ProLiant Gen8 server in either bay 3 or 6, and connect to the Integrated Remote
Console (IRC) of the assigned server.
If you are not booted into Intelligent Provisioning:
L12 2
a.
Reboot your server by selecting Power Switch/Reset from the IRC
b.
When prompted, press F10 for Intelligent Provisioning.
c.
Click the Home icon to go to the main HP Intelligent Provisioning menu, if you
are not already there.
Rev. 15.31
Installing Microsoft Windows Server 2012 R2 with HP Intelligent Provisioning
Rev. 15.31
2.
From the Integrated Remote Console menu at the top-left of the screen, click Virtual
Drives and select Image File CD-ROM/DVD.
3.
Browse your local disk to folder C:\classfiles\OS_ISO\Windows 2012 R2Server and

select the ISO file. Click Open.
L12 3
4.
L12 4
Ensure that a virtual drive is mounted. Click Configure and Install.
Rev. 15.31
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:
Rev. 15.31
Balanced Power and PerformanceOptimum settings to maximize power

savings with minimal impact to performance for most operating systems and
applications.
Minimum Power UsageEnables power reduction mechanisms that might

negatively affect performance. This mode guarantees a lower maximum power
usage by the system.
Maximum PerformanceDisables all power management options that might

negatively affect performance.
L12 5
6.
The next option on the Hardware Settings screen is System Software Update. In this
environment, the most current (at the time of lab creation) versions are already
installed, and there is no external network access. Select Skip Update.
7.
The last option on the Hardware Settings screen enables you to select the Array
Configuration. Select Keep Current Setting. Also, keep the available target
controller.
Then, click the arrow in the lower-right corner of the screen to continue.
L12 6
Rev. 15.31
8.
The HP Intelligent Provisioning install wizard reads the available media and
automatically displays the supported operating system family, in this case Microsoft
Windows.
In the Install Method area, three installation options are available:
Recommended
Customized
Manual
Select the Customized installation. This enables you to specify whether to install
the HP Management agents. Click the arrow in the lower-right corner of the screen
to continue.
Note
Linux can be installed only by using the Manual Install and Disc media.
Rev. 15.31
L12 7
9.
After the system scan has completed, enter the necessary information for the
deployment to proceed in the OS Information screen. Verify the operating system
selected and enter or select the following items:
Computer Name (operating system and your lab group number): WIN2012R2LGxx (where xx is your labgroup number). For example: WIN2012R2-LG01
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.
L12 8
Rev. 15.31
10. If you selected Customized Install, the next OS Information screen displays the
following installation option:
Install AMSWhen this option is selected, the Agentless Management Service

(AMS) is installed.
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 could result in
different alerts or duplicate alerts in HP Systems Insight Manager (HP SIM) 7.
Select Yes for the Install AMS. Then, click arrow in the lower-right corner of the
screen to continue.
Rev. 15.31
L12 9
11. When the Review window displays, verify that the installation information is correct.
At the bottom of the screen, click the left arrow to go back and change any
installation options, if needed. Click the right arrow when you are ready to continue.
L12 10
Rev. 15.31
The Windows installation begins. Intelligent Provisioning will partition the disk,
install the disk driver, and copy the required files to the logical drive on your target
server. A progress bar displays so you can monitor the process. It takes
approximately 30 minutes to finish this step.
Note
The window might go blank for user inactivity. Click inside or press any key.
Rev. 15.31
L12 11
When the copying has finished, the target server is restarted, and the Windows
setup procedure continues. This step takes approximately 10 minutes.
L12 12
Rev. 15.31
12. When prompted, accept the License Terms and click Next.
The installation will continue. Your target server might reboot several times.
Rev. 15.31
L12 13
In one of the steps, HP system drivers and tools are deployed. Ignore any warnings
or hpkeyclick messages that might display. This will take approximately 10 minutes.
L12 14
Rev. 15.31
Windows Server 2012 R2 is installed and ready to use. Verify if Image File CDROM/DVD is unmounted because it is not needed anymore.
13. From the console Keyboard menu, select CTRL-ALT-DEL key combination to sign in.
Rev. 15.31
L12 15
14. Enter the Administrator password that you provided in the Intelligent Provisioning
settings for deployment (password).
15. The Windows Server 2012 R2 Server Manager Dashboard appears. After reviewing,
you can log off and close the target server IRC.
L12 16
Rev. 15.31
Resources
For more information, refer to these resources:
Documents
Rev. 15.31
HP Intelligent Provisioning User Guide:

http://www.hp.com/go/intelligentprovisioning/docs
Websites
HP Intelligent Provisioning: http://www.hp.com/go/intelligentprovisioning
Installing Windows Server 2012 R2: https://technet.microsoft.com/enus/library/hh831620.aspx
L12 17
L12 18
Rev. 15.31
Using the HP ProLiant Gen9 servers UEFI tools

Lab 13
Objectives
After completing this lab, you should be able to use the HP UEFI System Utilities menu
items of HP ProLiant Gen9 servers, the HP UEFI Embedded Shell command-line interface,
and install common operating systems.
Requirements
Your team-assigned HP ProLiant Gen9 server
VMware ESXi boot image in an ISO file
Introduction
This lab explores the HP UEFI System Utilities menu items of the HP ProLiant Gen9
servers, the HP UEFI Embedded Shell command-line interface and install common
operating systems.
The legacy BIOS of the HP ProLiant Gen9 servers has been replaced with a UEFI ROM
offering:
Rev. 15.31
Better menu navigation experience (F9/System Utilities does it all):
No need to wait for the F8 time window to configure the iLO.
Intelligent Provisioning menus (F10) are accessible from a submenu of the

F9/System Utilities. Hence, there is no need to look for the F10 key during the
boot process.
Boot Menu (F11) is also accessible from the F9/System Utilities menu.
Add-on cards configuration utilities (Emulex, QLogic, etc.) can be accessed from
the UEFI shell. Hence, there is no risk to miss the right CTRL-E, Ctrl-Q, or CTRL-S
options during boot.
One look and feel (UEFI) but two boot modes:
UEFI boot mode: boot loader on EFI System Partition (ESP). This is the default
on the ProLiant Gen9 servers.
Legacy BIOS boot mode: boot loader on MBR.
Increased server security, flexibility, stability, and much more.
L13 1
To help you navigate through the UEFI menus, here is a high-level picture of the main
menus accessible via the F9 key:
L13 2
Rev. 15.31
Exercise 1Accessing and examining the UEFI ROM

To access the UEFI menus, you will start the Integrated Remote Console window on one
of your ProLiant Gen9 servers and boot to the UEFI ROM options. Perform these steps:
1.
If you have logged out of the HPVL environment, complete these steps to access the
IRC of your target server:
a.
Log into your CMS server with your credentials.
b.
Open Microsoft Internet Explorer and log into the OA of your c7000 enclosure.
c.
From the OA, expand the Device Bays pane. Then, expand your team-assigned
ProLiant Gen9 server in either bay 11 or 14, and connect to the Integrated
Remote Console (IRC) of the assigned server.
Note
If the Integrated Remote Console does not launch directly because of the IE9
security issues, as a workaround, click the Web Administration link instead
to access the iLO and start the Remote Console from there.
Rev. 15.31
L13 3
2.
In the Integrated Remote Console menu at the top-left of the screen, click Power
Switch and select Momentary Press to power on the server (or restart the server if
it is already powered on).
3.
Wait for the pre-boot menu to appear and press the F9 key to access the System
Utilities.
Note
Some screenshot are in inverted colors for better readability and printing.
L13 4
Rev. 15.31
4.
Rev. 15.31
If there are some important notifications or errors, an additional menu will appear,
offering to press the F2 key and view the information. For example, some
configuration might be missing and you can ignore it for this exercise.
L13 5
L13 6
5.
In both cases, you will end in the System Utilities menu. Notice the QR-coded link for
the Online Help in the lower right corner. Use the cursor keys to select One-Time
Boot Menu which is now accessible here without pressing the F11 key during boot.
6.
Review the boot entry list. Then, press ESC and return to the System Utilities.
Rev. 15.31
Rev. 15.31
7.
Select the System Information option and review the displayed content. Press ESC.
8.
Select the Embedded Applications menu and just note the possibility of reaching
Intelligent Provisioning from here. Dont go there at this time or you would have to
reset the system to return back and waste some time.
L13 7
9.
Select the Integrated Management Log (IML) option and note the possibility of
viewing or resetting IML from this menu. Press ESC and return to Embedded
Applications.
10. Also notice the Firmware Update option which displays the devices available to
update. Use the ESC key to return to the System Utilities menu.
11. In System Utilities, select the System Configuration (top) entry. From here, you can
enter the iLO 4 Configuration Utility (again, no need to wait for the F8 window time
during boot). Note that this System Configuration menu gives the possibility to
configure the embedded LOMs, mezzanines (if available), and Smart Arrays.
L13 8
Rev. 15.31
12. Select the Embedded RAID: Smart Array entry and notice the possibility of
launching the HP Smart Storage Administrator (HP SSA) application. Hence, there is
no need to reset the system and launch this application by means of the F10 key and
the Smart Provisioning menus. Again, do not launch the HP SSA at this time unless
you need it.
Instead, review the Device Information screen for the Smart HBA Controller, then
press ESC twice and return to the System Configuration menu.
13. Enter the BIOS/Platform Configuration (RBSU) menu, which offers similar options
as the legacy ROM Based Setup Utility (RBSU) menus.
Rev. 15.31
L13 9
14. Examine the list and notice that most of the tasks included in the legacy ROM-Based
Setup Utility (RBSU) shipping with previous ProLiant generations are available from
this BIOS/Platform Configuration menus.
For example, find the following menu item locations and write down the current
setup:
Boot Mode configuration (UEFI or Legacy, Optimized Boot enabled or not):

_______________________________________________________________
PCI Devices Enabled and Disabled:

_______________________________________________________________
Server Information (Name, Power-On Logo):

_______________________________________________________________
15. Access the System Default Options at the bottom of the BIOS/Platform
Configuration screen.
L13 10
Rev. 15.31
16. HP ProLiant Gen9 servers ship with the UEFI Boot Mode enabled by default both in
the firmware and the hard-wired dip switch (SW7) on the motherboard. HP
recommends that the Boot mode switch stays in sync with the firmware UEFI Boot
Mode variable. If a customer modifies this switch to ON, the default boot mode
becomes Legacy. Hence, a Restore Default Manufacturing Settings action sets the
Boot Mode to Legacy upon restoration of the manufacturing settings.
Review the available options without changing anything. Use the ESC key until you
return to the System Utilities main menu.
Note
The Restore Default Manufacturing Settings command can be used as a last

troubleshooting step if some UEFI configuration options are not working.
Rev. 15.31
L13 11
Exercise 2Accessing and using the UEFI shell

interface
The UEFI allows the start of a powerful command line shell application, enabling the
launch of scripts, administrative tasks (for example, firmware updates), and
troubleshooting commands. In this exercise, you will become familiar with the flexibility
provided by this shell related to boot devices and file systems.
L13 12
1.
From the System Utilities menu, select Embedded Applications and launch the
Embedded UEFI Shell.
2.
Upon entering, the UEFI Shells test for a User Physical Presence to prevent
corrupting the server using some malicious scripts. If you do not press any key
during the countdown, the Shell assumes there is no physical user presence and
prevents any malicious modification settings (i.e. modification of Secure Boot
settings).
Rev. 15.31
3.
As noted, type help b to display the list of all possible commands with a page per
page display mode. Press the Space bar to display the next page or type Q to quit.
4.
The UEFI is able to identify FAT-formatted disk partitions containing operating

system boot loaders. Those partitions are called EFI System Partitions (ESP). The
UEFI is able as well to associate a friendly name with the ESPs and thus facilitate
their browsing.
The mapping between unfriendly names (BLKx or long unique identifiers) and more
friendly strings happens automatically when the UEFI Shell is launched. However, to
be sure that drivers are correctly bound to all devices and started correctly, issue
connect -r at the Shell prompt.
Rev. 15.31
L13 13
L13 14
5.
Next, execute map -r to map the available file systems. Probably no partitions are
available at this moment.
6.
Now, exit the UEFI shell interface and return to UEFI GUI by typing exit.
7.
Press ESC and return to the main System Utilities menu.
Rev. 15.31
Exercise 3Enabling and using the flash memory

partition
HP iLO 4 stores files such as Active Health System data and the Intelligent Provisioning
software in the non-volatile flash memory that is embedded on the system board. This
flash memory is called the iLO NAND. ProLiant Gen9 servers ship with a 4GB iLO NAND
and allow the customer to use a 1GB partition as if it was an SD-card attached to the
server to store shell scripts or boot VMware ESXi (UEFI Mode only).
When the Embedded User Partition is enabled, you can access it through the server
operating system. By default, the Embedded User Partition is not enabled, so in this
exercise, you will first enable it using the UEFI GUI. Then, you will install the VMware ESXi
hypervisor OS on that flash partition. Perform these steps:
Rev. 15.31
1.
Navigate to System Utilities o System Configuration o BIOS/Platform

Configuration (RBSU) o System Options o USB Options and enable the Embedded
User Partition by selecting Enabled and pressing Enter.
2.
Press ESC three times and save the changes with Y when asked.
L13 15
L13 16
3.
Return to the System Utilities menu and select Reboot the System.
4.
Hit the F9 key during reboot to access the System Utilities again. Select Embedded
Applications and launch the Embedded UEFI Shell.
5.
Type map -r again and you should see your enabled flash partition. Note that you
see this device as a raw BLK device since it is not formatted.
Rev. 15.31
Rev. 15.31
6.
Use the IRC menu on the top, open Virtual Drives and select Image File CDROM/DVD.
7.
Navigate to your CMS folder C:\classfiles\OS_ISO\VMware ESXi, select the provided

VMware-ESXi ISO image, and click Open.
8.
Type map -r again and you should see some new content.
L13 17
9.
Your new assigned Virtual CDROM is probably mapped as FS0:. To access it from UEFI
shell, type FS0:. The prompt will change like in DOS (if you remember).
10. Type ls (or dir) to list the content. Then, type cd EFI and cd BOOT to find the
boot loader file.
L13 18
Rev. 15.31
11. To start the VMware installation, type BOOTx64.EFI and press Enter.
The installation process begins.
12. Confirm the installation by pressing Enter when asked.
Rev. 15.31
L13 19
13. Press F11 to accept the End User License Agreement (EULA).
14. The system is scanned for available disks. Select HP iLO Media... (1.00 GiB) and
press Enter.
Workaround note
If the HP iLO Media is not recognized for some reason, cancel the installation
process and as a troubleshooting step, you can try Restore Default
Manufacturing Settings as explained in exercise 1, step 16 of this lab.
After restoring and rebooting, start again exercise 3 from the first step.
L13 20
Rev. 15.31
15. (optional) If the embedded partition is not cleared after the previous class and an
existing ESXi installation is found, select the Install option when asked.
16. Select the US Default keyboard layout and press Enter.
17. Provide a password for the root user (password), press Tab, repeat again, and
press Enter. Read the warning and confirm the installation by pressing the F11 key.
The installation process continues and can take 10 minutes.
Rev. 15.31
L13 21
18. When the installation completes, press Enter to reboot.
19. While rebooting, make sure that the Virtual Drive is unchecked.
L13 22
Rev. 15.31
The server boots to the VMware ESXi hypervisor OS from the embedded flash drive.
Note
In a production environment, some additional setup is required, such as the

server should have a VC profile with connectivity assigned and VMware ESXi
must be configured for the planned virtual machines.
Rev. 15.31
L13 23
Resources
For more information, refer to these resources:
Websites
HP ProLiant Gen9 servers: http://www.hp.com/go/proliantgen9
HP Unified Extensible Firmware Interface: http://www.hp.com/go/uefi
Documents
L13 24
HP ProLiant Gen9 servers: http://www.hp.com/go/proliantgen9/docs
Rev. 15.31

Student handout for HPVL equipment
Introduction
This document contains information about the HPVL equipment used during virtual
delivery of your class and how to connect to it.
Table of contents
Introduction .......................................................................................................................... 1
Table of contents .................................................................................................................. 1
Classroom configuration ...................................................................................................... 2
Team stations and lab equipment configuration ................................................................. 3
Equipment assignments ............................................................................................... 3
Labgroup details ................................................................................................... 3
Interconnects ................................................................................................................ 4
Device bays and iLO addresses ..................................................................................... 4
User accounts and passwords ...................................................................................... 5
Onboard Administrator ................................................................................................. 5
Network cabling ............................................................................................................ 5
Network definitions ...................................................................................................... 5
DHCP .............................................................................................................................. 6
FTP................................................................................................................................. 6
Telnet/SSH .................................................................................................................... 6
Software location.......................................................................................................... 6
HP Virtual Labs (HPVL) specific instructions ........................................................................ 7
Learner-specific information ........................................................................................ 7
Prerequisites ................................................................................................................. 7
Accessing the HPVL environment ................................................................................. 8
Connecting to the enclosure Onboard Administrator ................................................ 15
Connecting to the server blade iLOs ........................................................................... 17
Exiting HPVL ................................................................................................................ 19
Rev. 15.31
A01 1
Classroom configuration
The classroom equipment and its configuration are depicted in the graphic below.
Detailed information about the configuration is available on the pages that follow.
A01 2
Rev. 15.31
Team stations and lab equipment configuration

Equipment assignments
Team
Equipment
Central Management Server

(CMS) DL360
Name
NIC 1
NIC 2
NIC 3 PCI slot (b)
NIC 4 PCI slot (a)
Virtual Connect
Ethernet interconnects
SAN interconnects bays

Device bays 1, 2, 4 and 5
Device bays 3 and 6
Device bays 7 and 8
Device bays 9
Device bays 10
Device bays 11 and 14
ProLiant DL360 G5
Station1
HPVL-reserved (no IP)
192.168.200.1
10.99.178.x
HPVL-assigned
HP VC FlexFabric 10Gb/24
Port Module in interconnect
bay 1
HP VC FlexFabric 10Gb/24
Port Module in interconnect
bay 2
HP ProCurve 6210XG Blade
Switch in interconnect bay 3
Switch in interconnect bay 4
Brocade 4/24 SAN Switch in
interconnect bay 5
Brocade 8/24 SAN Switch in
interconnect bay 6
BL460c G7
BL460c Gen8
BL860c
BL460c Gen1
SB40c
BL460c Gen9
Labgroup details
VNC and RDP

connections
CMS Server
Labgroups 1, 2 and 3:
Rack Team
VNC username
VNC password
RDP username
RDP password
NIC 2 management network
NIC 3 Network (Link B)
Administrator
Password1
Administrator
password
192.168.200.1
10.99.178.x
10.99.178.110 to
10.99.178.150
<see instructor>
password
NIC 3 Network (Link B)

Server name
Administrator password
Rev. 15.31
A01 3
Interconnects
Interconnect
Switch (IP address)
bay
HP VC FlexFabric 10Gb/24-Port
Module (192.168.200.101)
Switch (192.168.200.103)
Brocade 4/24 SAN Switch
(192.168.200.105)
Empty
1
3
5
7
Interconnect
Switch (IP address)
bay
2
4
6
8
HP VC FlexFabric 10Gb/24-Port
Module (192.168.200.102)
Switch (192.168.200.104)
Brocade 8/24c SAN Switch
(192.168.200.106)
Empty
Note
All IP addresses will be assigned using EBIPA. Students will run an OA

configuration script to standardize the OA settings.
Device bays and iLO addresses

Device bay
Device
iLO address
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
BL460c G7
BL460c G7
BL460c Gen8
BL460c G7
BL460c G7
BL460c Gen8
BL860c
BL860c
BL460c G1
SB40c
BL460c Gen9
Empty
Empty
BL460c Gen9
Empty
Empty
192.168.200.11
192.168.200.12
192.168.200.13
192.168.200.14
192.168.200.15
192.168.200.16
192.168.200.17
192.168.200.18
192.168.200.19
n/a
192.168.200.21
192.168.200.22
192.168.200.23
192.168.200.24
192.168.200.25
192.168.200.26
Note
All IP addresses will be assigned using EBIPA. Students will run an OA

configuration script to standardize the OA settings.
A01 4
Rev. 15.31
User accounts and passwords

Component
User account
Password
CMS
Onboard Administrator
ProCurve switch
Brocade SAN switches
Target Windows operating system
Target Linux operating system
VC FlexFabric
Target HPUX operating system
Administrator
Administrator
admin
admin
Administrator
root
Administrator
root
password
password
password
password
password
password
password
hp
Note
When you have the opportunity to supply a new password, use lowercase
password (without the quotes).
Onboard Administrator
OA 1
OA 2
192.168.200.100
192.168.200.200
Note
The USB port has an attached USB key containing the Service Pack for
ProLiant and OA firmware .bin file.
Network cabling
Component
Destination
NIC 3 Private Network (Link B)

(10.99.178.x)
(ProLiant DL360)
NIC 2 MGMT Network (192.168.200.x)
(ProLiant DL360)
NIC 1 Access to HPVL
(ProLiant DL360)
NIC 4 HPVL Student Network (Link A)
(ProLiant DL360)
OA1 (192.168.200.100)
OA2 (192.168.200.200)
Plugs into the Virtual Connect Module uplink port X5 in

interconnect bay 1
Plugs into the racks ProCurve switch (management network)
Plugs into the HPVL network
Plugs into the HPVL network
Network definitions
Rev. 15.31
Network name
Destination
Deployment
Deployment DHCP range
Management
HPVL
10.99.178.x
10.99.178.110-10.99.178.150
192.168.200.x
HPVL-dependent
A01 5
DHCP
DHCP is configured on CMS server and bound to 10.99.178.x NIC 3
DHCP scope is 10.99.178.110 10.99.178.150
FTP
FTP server is configured (FileZilla FTP Server) it is bound to all CMS NICs with two user
accounts:
Administrator/password
anonymous
Telnet/SSH
On CMS server you have the following:
PuTTY
Windows OS based Telnet, enabled
Reflection Telnet
Software location
The software you need for the class is located in the Classfiles folder on the C: drive of
the CMS (C:\classfiles).
A01 6
Rev. 15.31
HP Virtual Labs (HPVL) specific instructions

Learner-specific information
The username and password information for you to access the HP Virtual Lab (HPVL) will
be provided by either your reservation (self-paced) or your instructor (ILT). You will also
be assigned a specific set of equipment called a labgroup. Record that information
below:
HPVL username: ..............................................................................................................
HPVL login: ......................................................................................................................
Labgroup: ........................................................................................................................
Prerequisites
Ensure that the computer you use to access the HPVL meets the requirements described
in the Connection Reference Guide (das_guide.pdf) document available at:
http://hpvl.usa.hp.com/access.htm
Rev. 15.31
A01 7
Accessing the HPVL environment

To access the HPVL:
A01 8
1.
Open an Internet web browser and enter http://www.hp.com/go/hpvl in the

address field. Click the Access Virtual Lab Environment link on the displayed page.
2.
In the HPVL Access Portals field, type your user name and click Logon to access the
appropriate access portal for your class.
Rev. 15.31
Note
You might have to click Continue to accept a security alert.

3.
The HPVL Access screen displays with your user name. Enter the password supplied
by your instructor 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 this example, click Install.
Note
Depending on your browser, the plug-ins might require that you close and
restart your browser.
Rev. 15.31
A01 9
5.
The Select Desktop Size page displays. Click to open the drop-down menu and select
your preferred desktop size, if needed.
Note
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.
By default, the used window size is 90% of your current display size. At least
1280x1024 or larger is recommended (the lab equipment is set to this
resolution and some forms might not be fully visible if resolution is lower).
6.
A01 10
Then, click the Continue button.
Rev. 15.31
Note
If your login session expires due to inactivity, click the Start a new session
link, and enter your login credentials again.
7.
From the HP Virtual Labs Welcome page, click a button to select RDP Desktop if
using Windows to access, or Java Desktop if accessing with Mac/Linux.
The F5 Application Access Windows Internet Explorer window displays.
Rev. 15.31
A01 11
Use:
8.
A01 12
The top-right Minimize, Maximize, and Close buttons to change your view or
close the window.
The Toggle Scrollbar link to enable/disable the scrollbar.
CTRL+ALT+BREAK on your keyboard to toggle for a window and full-screen

view.
The Close link to close the window.
At the Choose a Lab Group screen, click the link corresponding to your labgroup.
Labgroup assignments are done by the HPVL team or by your instructor.
Rev. 15.31
9.
At the labgroup-specific screen (below), you have a number of options:
Hover your mouse pointer over a DL360 server to expose available links to that
systems options, such as:
VNC connection
Remote Desktop connection
iLO Access
Note
The Remote Desktop option is preferable by some learners because it

responds better than VNC. If you use the Remote Desktop option, one person
from your team logs in using this option and shares his/her desktop using the
HPVR breakout room.
Rev. 15.31
A01 13
Hover over the link, for example, VNC Connection, to expose the login
credentials.
Scroll down to the Shadow User Session section to learn about and activate a
Shadow User Session.
Scroll down to the bottom of this page and find the Exit Lab button. Do NOT
click the Exit lab button at this time. At the end of each lab session, return to
this page and click the Exit Lab button before complete closing out the Remote
Desktop Protocol session.
To log into the operating system running on the CMS, click the VNC connection
or RDP 1280x1024 (recommended) link exposed by hovering over the
appropriate DL360 picture. If using the VNC Viewer at Authentication [No
Encryption] screen type your password and click OK.
Note
Multiple students can use the same VNC connection to the same server. One
student can perform actions while other students can watch those actions.
On the other hand, RDP connection might provide better performance.
x
A01 14
Log into DL360 server (CMS) by using credential provided by the instructor, or
see section User accounts and passwords in this document.
Rev. 15.31
Connecting to the enclosure Onboard Administrator

To connect to the enclosure Onboard Administrator:
1.
Ensure that you have logged into the HPVL and your teams DL360 server (CMS).
2.
At your CMS, open Internet Explorer and enter the following URL in the address field:
https://<Onboard_Administrator_IP_address>/
Rev. 15.31
A01 15
3.
Enter your login credentials and click Sign In.

The Onboard Administrator GUI displays.
A01 16
Rev. 15.31
Connecting to the server blade iLOs

To connect to the server blade iLO 3/4 processors, you can either enter the iLO 3/4 IP
address directly into the address field of the Internet Explorer running on your CMS and
provide iLO credentials or use the Onboard Administrator GUI:
Rev. 15.31
1.
Ensure that you are logged into your team server (CMS) in the HPVL.
2.
Ensure that you are connected to the Onboard Administrator GUI. Refer to the
previous section for details.
3.
At the Onboard Administrator GUI, in the Systems and Devices pane, expand
Enclosure Information o Device Bays.
A01 17
A01 18
4.
Under Device Bays, expand your server blade and click iLO.
5.
From the iLO Remote Management screen, select the appropriate option to connect
to iLO 3/4. Typically, that is the Web Administration or Integrated Remote Console
(IRC).
6.
Close the IRC screen and log out from the OA, but do NOT log out from the CMS.
Rev. 15.31
Exiting HPVL
When you are finished with your lab, log out from the CMS and from HPVL. For exiting
your lab, follow the instructions in the Connection Reference Guide (das_guide.pdf)
document.
Rev. 15.31
A01 19
A01 20
Rev. 15.31

LG 02jul15 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

LG 02jul15 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

HP BladeSystem c-Class

Copyright 2015 Hewlett-Packard Development Company, L.P.

Lab 1Using the HP Power Advisor

Lab 2Using the Onboard Administrator GUI

Lab 3Using the Onboard Administrator CLI

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

Lab 4Using the Insight Display

Lab 6Installing and configuring the HP ProCurve 6120 Blade Switch

HP Confidential For training purposes only

Exercise 3Configuring the HP ProCurve 6120 Blade Switch .......................................... 19

Lab 7Virtual Connect

Lab 8Installing and configuring the Brocade 4Gb/8Gb SAN Switch

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

Lab 9HP BladeSystem c-Class Enclosure-Based USB Devices

Lab 10Using the HP Service Pack for ProLiant

Lab 11Reinstalling HP Intelligent Provisioning

Lab 12Installing Microsoft Windows Server 2012 R2 with HP Intelligent

Lab 13 Using the HP ProLiant Gen9 servers UEFI tools

HP Confidential For training purposes only

AppendixClassroom Configuration Guide

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

HP Confidential For training purposes only

Using the HP Power Advisor

Explain how to configure an HP BladeSystem c-Class enclosure using the HP Power

A supported Internet browser

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

Exercise 1Installing and using the HP Power Advisor

There is also an online version of HP Power Advisor at website

Configure the enclosure

Install the server blades

Configure the server blades

Review and save the configuration

Start Windows File Explorer and execute as administrator HPPowerAdvisor.exe ,

HP Confidential For training purposes only

Using the HP Power Advisor

At the Welcome screen, click Next.

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

Accept the default customer information and click Next.

Accept the default destination folder and click Next.

HP Confidential For training purposes only

Using the HP Power Advisor

Click Install and after the installation.

Click Finish to close the wizard.

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

HP Confidential For training purposes only

Using the HP Power Advisor

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

The rack displays in the working area, with its height in U.

HP Confidential For training purposes only

Using the HP Power Advisor

HP Confidential For training purposes only

HP BladeSystem c-Class Infrastructure

HP Confidential For training purposes only

Using the HP Power Advisor

Configure the enclosure

When the Configure C7000 Enclosure menu displays, click Config.