HPE Compute Solutions, Rev. 21.41 Lab Guide

HPE Compute Solutions
Lab guide
Rev. 21.41
Confidential – For Training Purposes Only
Use of this material to deliver training without prior written permission from HPE is prohibited.
Ó Copyright 2021 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for HPE products
and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall
not be liable for technical or editorial errors or omissions contained herein.
This is an HPE copyrighted work that may not be reproduced without the written permission of Hewlett
Packard Enterprise. You may not use these materials to deliver training to any person outside of your
organization without the written permission of HPE.
Microsoft Windows Server®, Microsoft SQL Server®, Microsoft Excel®, Microsoft Hyper-V, Microsoft Internet
Explorer, Microsoft Terminal Services®, Microsoft System Center® and Windows PowerShell® are used with
permission from Microsoft.
VMware ESX® and ESXi®, VMware vSphere and vSphere Client®, VMware vCenter®, VMware Operations
Manager, and VMware vRealize Operations Manager® are trademarks or registered trademarks in the United
States and certain other countries.
Intel® is a trademark of Intel Corporation in the United States and other countries.
Red Hat®, Red Hat Enterprise Linux®, and Red Hat Linux KVM hypervisor® are trademarks or registered
trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
All other trademarks are the property of their respective owners.
Printed in USA
HPE Compute Solutions

Lab guide
November 2021
Contents
Lab 0: Accessing the HPE Partner Ready Lab

Learning objective ........................................................................................................................................................................................................................... 2
Requirement........................................................................................................................................................................................................................................ 2
Accessing the HPE Partner Ready Lab ............................................................................................................................................................................... 2
Lab 1: Exploring HPE Synergy and HPE Superdome Flex setup

Learning objectives ......................................................................................................................................................................................................................... 2
Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Exploring HPE Synergy setup ......................................................................................................................................................................... 3
Exercise 2: Exploring HPE Superdome Flex system .................................................................................................................................................... 7
Summary ............................................................................................................................................................................................................................................... 9
Lab 2: Installing an operating system on HPE Superdome Flex

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Preparing HPE Superdome Flex for an operating system installation .................................................................................... 3
Exercise 2: Installing ESXi on HPE Superdome Flex.................................................................................................................................................... 8
Exercise 3: Configuring ESXi and scaling up an HPE Superdome Flex nPar ................................................................................................ 9
Summary ............................................................................................................................................................................................................................................ 11
Lab 3: Configuring HPE Synergy

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Creating an IP pool for management network ....................................................................................................................................... 3
Exercise 2: Creating networks and network sets, using HPE OneView ........................................................................................................... 4
Exercise 3: Creating logical interconnect groups .......................................................................................................................................................... 8
Exercise 4: Creating an enclosure group ......................................................................................................................................................................... 11
Exercise 5: Creating a logical enclosure ........................................................................................................................................................................... 14
Rev. 21.41 | © Copyright 2021 Hewlett Packard Enterprise Development LP | Confidential – For Training Purposes Only
Contents
Exercise 6: Exploring logical interconnects ................................................................................................................................................................... 15

Exercise 7: Modifying a logical interconnect group .................................................................................................................................................. 16
Exercise 8: Adding SAN managers and modifying HPE OneView networks ............................................................................................. 18
Exercise 9: Adding HPE Storage components ............................................................................................................................................................. 21
Summary ............................................................................................................................................................................................................................................ 23
Lab 4: Managing storage for HPE compute solutions

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Basic storage management using array management tools ......................................................................................................... 3
Exercise 2: Importing CPGs and virtual volumes to HPE OneView .................................................................................................................... 5
Exercise 3: Working with volume templates using HPE OneView ...................................................................................................................... 6
Exercise 4: Managing volumes using HPE OneView ................................................................................................................................................... 8
Exercise 5: Optimizing virtual volumes ............................................................................................................................................................................ 10
Summary ............................................................................................................................................................................................................................................ 11
Lab 5: Working with HPE OneView server profiles

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Creating a server profile for an HPE Synergy compute node ...................................................................................................... 3
Exercise 2: Configuring MPIO for the Windows operating system ..................................................................................................................... 6
Exercise 3: Working with data volumes and snapshot functionality ................................................................................................................. 7
Exercise 4: Working with downlink aggregation............................................................................................................................................................ 9
Summary ............................................................................................................................................................................................................................................ 12
Lab 6: Configuring iLO Federation

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Configuring iLO Federation .............................................................................................................................................................................. 3
Summary ............................................................................................................................................................................................................................................... 5
Lab 7: Working with HPE OneView for VMware vCenter Server

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Verify proper integration of the required components .................................................................................................................... 3
Exercise 2: Preparing an OS Deployment Plan ............................................................................................................................................................... 5
Exercise 3: Preparing a server profile template ............................................................................................................................................................. 6
Exercise 4: Preparing HPE Synergy compute nodes for ESXi system deployment .................................................................................. 8
Rev. 21.41 TOC-2 Confidential – For Training Purposes Only

Contents
Exercise 5: Deploying an ESXi system using HPE OneView for VMware vCenter Server..................................................................... 9
Exercise 6: Working with HPE OneView for VMware vCenter Server ............................................................................................................ 11
Summary ............................................................................................................................................................................................................................................ 13
Lab 8: Working with a virtualization workload

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Prepare HPE Synergy compute nodes for VMWare vSAN deployment ................................................................................. 3
Exercise 2: Deploying a vSAN witness node .................................................................................................................................................................... 6
Exercise 3: Configuring a two-node vSAN cluster with a witness node........................................................................................................... 8
Exercise 4: Working with VMware virtualization ........................................................................................................................................................ 10
Summary ............................................................................................................................................................................................................................................ 14
Lab 9: Working with HPE Storage Integration Pack for VMware vCenter
Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Configure HPE Storage Integration Pack for VMware vCenter ................................................................................................... 3
Exercise 2: Configuring vVols and VMFS datastores using HPE Storage Integration Pack for VMware vCenter .................. 4
Exercise 3: Explore other functionalities of HPE Storage Integration Pack for VMware vCenter .................................................. 9
Summary ............................................................................................................................................................................................................................................ 11
Lab 10: Working with VMware vSphere Lifecycle Manager

Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Updating ESXi systems using a baseline .................................................................................................................................................. 3
Exercise 2: Create a cluster and switch to image-based management ............................................................................................................ 5
Summary ............................................................................................................................................................................................................................................... 8
Lab 11: Working with the PowerShell Library for HPE OneView
Requirement........................................................................................................................................................................................................................................ 2
Exercise 1: Reverting HPE OneView DCS to its initial state ................................................................................................................................... 3
Exercise 2: Configuring DCS using PowerShell scripts .............................................................................................................................................. 4
Reference materials ........................................................................................................................................................................................................................ 6
Summary ............................................................................................................................................................................................................................................... 7

Contents
This page intentionally left blank.

Accessing the HPE Partner Ready
Lab
Lab 0
Rev. 21.41
Confidential - For Training Purposes Only
Accessing the HPE Partner Ready Lab Page 2
Learning objective
After completing this lab, you should be able to access the HPE Partner Ready Remote Lab.
Requirement
To complete this lab, you must have:
• Internet access
• Supported web browser, such as Google Chrome
• VPN credentials (supplied by instructor)
Accessing the HPE Partner Ready Lab

The lab environment that you will use might vary. Your instructor will provide the appropriate access method to
connect to a remote lab environment. This environment will be configured for you to complete the exercises in this
guide.
Rev. 21.41
Exploring HPE Synergy and HPE
Superdome Flex setup
Lab 1
Rev. 21.41
Exploring HPE Synergy and HPE Superdome Flex setup Page 2
Learning objectives
After completing this lab, you should be able to:
• Explore an existing HPE Synergy setup in HPE OneView
• Explore an existing HPE Superdome Flex setup
Requirement
To complete this lab, you must have access to the HPE Partner Ready lab environment.
NOTE
This lab is performed on real equipment. Do not modify any object that you did not create.
Rev. 21.41
Exercise 1: Exploring HPE Synergy setup

In this exercise, you explore an existing HPE Synergy setup, using the HPE OneView interface. HPE Synergy
components are discovered during hardware setup, which has been completed already. Each student has been
assigned three HPE Synergy compute nodes. Refer to the table below and locate the servers allocated to you:
Student Servers allocated
Student01 Frame 1: Server in bays 1, 2, and 3
1. The HPE OneView interface can be used to manage various HPE Synergy components. To explore an existing
enclosure setup, complete the following steps:
a. Open Google Chrome and click the Synergy bookmark. Confirm the security exception, if prompted.
b. Log in using the HPE Synergy credentials from the Class Info – Seat XX document located on the desktop.
Replace XX with your group number.
c. From the HPE OneView main menu, navigate to SERVERS, and select Enclosures. You should see three HPE
Synergy frames.
d. From the list on the left side, click the first frame and note the number and the type of management appliances
and interconnect modules.
e. Repeat the previous step for the second and third frames.
Rev. 21.41
f. Click the first frame again, and from the drop-down menu next to the name of the frame, select Frame Link
Topology. You should see a diagram similar to this.
g. Based on the FLM topology discovered, draw the connections on the diagram below.
Rev. 21.41
2. To explore the HPE Synergy compute nodes, complete the following steps:
a. Navigate to SERVERS, and select Server Hardware.
b. Are there any compute modules other than HPE Synergy 480 Gen 10?
___________________________________________________________________________________________________
c. Do all of them share the same server hardware type?
___________________________________________________________________________________________________
d. Navigate to SERVERS, and select Server Hardware Types.
e. How many different server hardware type definitions are available for HPE Synergy 480 Gen10?
___________________________________________________________________________________________________
f. Write down the type and location of the mezzanine adapters.
___________________________________________________________________________________________________
g. Navigate to SERVERS, and select Server Hardware.
h. Refer to the table at the beginning of this lab and click one of the servers allocated to your group.
i. What is the status of this server? If there are any error messages or warnings, notify your instructor.
___________________________________________________________________________________________________
j. Explore the configuration of this server, and note the amount of memory.
___________________________________________________________________________________________________
k. How does the fact that both CPUs are installed affect this node?
___________________________________________________________________________________________________
3. To explore in-frame storage components, complete the following steps:
a. Navigate to STORAGE, and select Drive Enclosures.
b. How many D3940 Storage Modules are available?
___________________________________________________________________________________________________
c. In total, how many drives are installed in the D3940 Storage Modules? Are there any SSD drives installed?
___________________________________________________________________________________________________
d. Are there redundant storage IO module adapters in any D3940 Storage Modules?
___________________________________________________________________________________________________
Rev. 21.41
4. To explore the available interconnect modules in HPE Synergy frames, complete the following steps:
a. Navigate to NETWORKING, and select Interconnects.
b. Locate the HPE Virtual Connect module in the first frame.
c. What is the speed of ports L1 and L2? What is their purpose?

___________________________________________________________________________________________________
___________________________________________________________________________________________________
d. Navigate around the interconnects and identify the master modules, and their locations. How many master
modules are installed in this configuration?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
e. Navigate to NETWORKING, and select Logical Interconnect Groups. How many LIGs are there? What is the
purpose of a LIG?
___________________________________________________________________________________________________
f. Navigate to NETWORKING, and select Logical Interconnects. How many LIs are created? When are they
created?
___________________________________________________________________________________________________
5. Take 10-15 minutes to explore the other options available within the HPE OneView interface.
Rev. 21.41
Exercise 2: Exploring HPE Superdome Flex system

In this exercise, you explore an HPE Superdome Flex setup, using the Rack Management Controller (RMC) CLI.
1. To connect to the RMC CLI, complete the following steps:
a. Start PuTTY located on the desktop of your management server.
b. Enter rmc.hpe.local as the hostname and click Open.
c. If a “server’s host key is not cached in the registry” error displays, click Yes to add the key to the PuTTY cache.
d. Log in using the RMC credentials from the Class Info – Seat XX document. Replace XX with your group
number. Note that the username and password are case sensitive. You should see the RMC CLI.
e. Execute the show complex command. You will see that you have one RMC and two Baseboard
Management Controllers (BMCs). Make a note of the RMC and BMC IDs (r00…). Is the system nPartition (nPar)
capable?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
f. Execute the show network command. The eth1 address is for the RMC. The BaseIO section shows the IP
addresses of the two BMCs. Record the RMC and BMC IP addresses below. Did the BMCs acquire their IP
addresses statically or automatically?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
g. Execute the show npar command. Are there any existing nPars?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
h. Execute the show health command. Are the RMC and BMCs healthy? If not, discuss possible reasons with
your instructor.
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
Rev. 21.41
i. Execute the show power command. Are any chassis powered on?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
j. Take 5-10 minutes to explore other CLI commands such as help and apropos.
2. To explore a BMC, complete the following steps:
a. Open Google Chrome and click the BMC1 bookmark. Confirm the security exception, if prompted.
b. Log in using BMC1 credentials from the Class Info – Seat XX document. Replace XX with your group number.
c. What are the two options presented on the main screen?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
d. Log out from the BMC or close the browser tab.
Rev. 21.41
Summary
In this lab, you explored an existing HPE Synergy setup using the HPE OneView interface and an HPE Superdome
Flex setup using the RMC CLI and BMC interface.
Rev. 21.41
Rev. 21.41
Installing an operating system on
HPE Superdome Flex
Lab 2
Rev. 21.41
Installing an operating system on HPE Superdome Flex Page 2
Learning objectives
• Prepare an HPE Superdome Flex nPar for an operating system installation
• Install and configure ESXi on an HPE Superdome Flex nPar
• Expand an nPar with a second chassis
Requirement
NOTE
This lab is performed on real equipment. Do not interact with any object that you did not create.
Rev. 21.41
Exercise 1: Preparing HPE Superdome Flex for an operating system installation

In this exercise, you install ESXi on an HPE Superdome Flex nPar in a boot from SAN (BfS) configuration. You create
an nPar, prepare a boot volume on HPE 3PAR, present it to HPE Superdome Flex and deploy an ESXi system.
1. To create an nPar on HPE Superdome Flex, complete the following steps:
a. Start PuTTY, located on the desktop of your management server.
b. Input rmc.hpe.local as the hostname and click Open.
c. If a “server’s host key is not cached in the registry” message is displayed, click Yes to add the key to the
PuTTY cache.
d. Log in using RMC credentials from the Class Info – Seat XX document. Replace XX with your group number.
Note that the username and password are case sensitive. You should see the RMC CLI.
e. Execute the command show chassis and write down both of the BMC IDs.
___________________________________________________________________________________________________
___________________________________________________________________________________________________
f. Execute the command create npar pnum=p1 chassis=<BMC1> to create an nPar. Replace
<BMC1> with the lowest BMC ID identified in the previous step. You can execute the command apropos
npar to get guidance with command syntax.
g. Execute the command show npar and verify that the nPar has been created successfully.
2. To prepare for an operating system installation on your HPE Superdome Flex nPar, complete the following steps:
b. Log in using the BMC credentials from the Class Info – Seat XX document located on the desktop of your
management server. Replace XX with your group number.
c. Click Launch KVM interface to open the remote console.
d. Return to the RMC CLI session and execute the command power on npar pnum=p1 to power on the
newly created nPar. Note that it can take several minutes for output to appear on the console.
e. Wait until the boot sequence is completed and the UEFI Shell prompt appears. Type exit and press Enter to
access the Superdome Flex Boot Manager.
f. Use the arrow keys to select Boot Maintenance Manager and press Enter.
g. Press Enter again to select Boot options on the next screen.
h. Use the arrow keys select Delete Boot Option and press Enter.
Rev. 21.41
i. If there are any boot options, select all of them using the space bar and arrow keys and select Commit
Changes and Exit.
j. Return to the RMC CLI and execute the command power reset npar pnum=p1 to reboot the nPar.
3. To configure your HPE Superdome Flex nPar for boot from SAN, complete the following steps:
a. After reboot, at the UEFI Shell prompt, input exit and press Enter to access the Superdome Flex Boot
Manager.
b. On the boot manager screen, use the arrow keys to highlight Device Manager, and press Enter.
c. Use the arrow keys to highlight the first HPE SN1100Q 16Gb 2p FC HBA, and press Enter.
d. Use the arrow keys to highlight Boot Settings, and press Enter.
Rev. 21.41
e. Verify that the Adapter Driver is enabled. If the Adapter Driver is not enabled, use the arrow keys to highlight
Adapter Driver, and press Enter. Use the arrow keys to highlight Enabled, press Enter, press the function key
F10, and type Y to save the configuration changes.
f. Press ESC twice to return to the Device Manager screen.

g. Repeat steps c to f for the second HPE SN1100Q 16Gb 2p FC HBA.
h. Press Escape until you return to the Boot Manager menu. Use the arrow keys to highlight Reset, and press
Enter to initiate the reset.
NOTE
If the Adapter Driver was already set to Enabled, a reset is not required, and you can select Continue from
the Boot Manager menu.
i. When the nPar has rebooted to the UEFI shell, input exit and press Enter to access the Superdome Flex
Boot Manager.
j. On the boot manager screen, use the arrow keys to highlight Device Manager, and press Enter.
k. Use the arrow keys to highlight the first HPE SN1100Q 16Gb 2p FC HBA, and press Enter.
l. Use the arrow keys to select Scan Fibre Devices, and press Enter. When the scan is complete, press ESC to
return to the HPE SN1100Q 16Gb 2p FC HBA screen.
Rev. 21.41
m. Select WWN Database, and press Enter.

n. Use the arrow and Enter keys to set the Drive 0 WWPN and LUN numbers as shown in the graphic below.
Press F10 to save the configuration, and enter y to confirm.
NOTE: On the system you are using you may see slightly different WWNs. For example,
20330002AC025DF2 and 21330002AC025DF2. This is a result of different port numbers
being used on the FC HBA.
NOTE: The first four digits of the WWPN represent:

• First digit: Always 2 for Primera and 3PAR arrays
• Second digit: Node number
• Third digit: PCIe slot number
• Fourth digit: Port number
The HPE Primera array you will be booting from has two nodes, each with its own WWPN.
You should have just set the first FC adapter to boot from the first node, via the FC HBA in
PCIe slot 3, using port 1 of the HBA (2031…).
NOTE: The graphic above shows that the Drive 0 is offline. This will change when you
have completed the steps below.
o. Return to the Device Manager screen, select the second HPE SN1100Q 16Gb 2p FC HBA, and press Enter.
Repeat steps l to n to configure the BfS settings for the second port, except this time, use the WWN for the
second Primera node, via the FC HBA in PCIe slot 3, using port 2 of the FC HBA (2132…).
p. Press Escape to return to the Boot Manager menu. Use the arrow keys to highlight Reset, and press Enter to
initiate the reset.
q. When the UEFI shell reappears, check the WWN database for both FC HBAs again, and you should see that
Drive 0 is online.
Rev. 21.41
r. Press Escape until you return to the Boot Manager menu, and select Continue to return to the UEFI Shell.
Rev. 21.41
Exercise 2: Installing ESXi on HPE Superdome Flex

In this exercise you deploy ESXi 7.0U2 on your HPE Superdome Flex nPar. This ESXi version supports up to 16 CPUs
and 24TB of the memory.
1. To install ESXi on your HPE Superdome Flex nPar, complete the following steps:
a. Open Google Chrome, and click the BMC1 bookmark. Confirm the security exception, if prompted.
b. Log in using BMC credentials from the Class Info – Seat XX document located on the desktop of your
c. Click Launch KVM interface to open a remote console.
d. If the system is at the UEFI shell, type exit and press Enter.
e. In the BMC browser window, click Download Virtual Media Application. If you receive a warning message,
select Keep. The file JViewer-sa.jar is downloaded to the default download location.
f. In the bottom-left of the Chrome browser, click the JViewer-sa.jar file to open it.
g. In the Launch window, enter the hostname of BMC1 as documented in the Class Info file on the desktop of
your management server, leave the Secure Web Port set to 1443, and input the BMC username and password.
Click Launch.
h. In the Untrusted Connection pane, click Yes. After a couple of seconds, the Virtual Media application window
appears.
i. Click Browse for CD/DVD Media: I, and select the VMware-ESXi-7.0.2-17867351-HPE-702.0.0.10.7.0.17-
SuperdomeFlex-May2021.iso file located in the ClassFiles folder on the desktop of your management server.
Click Open, then click Connect.
j. Return to the BMC1 window, and on the Boot Options screen use the arrow keys to highlight Boot Manager
Menu, and press Enter.
k. On the Boot Manager Menu screen, use the arrow keys to scroll through the list of devices, and select UEFI
USB Device 0. Press Enter to start booting from that device.
l. Wait until ESXi loads and press Enter to continue.
m. Press F11 to accept the end-user license agreement.
n. Use the arrow keys select the 250GiB volume, and press Enter.
o. Press Enter to continue with the default keyboard layout.
p. Input P@ssw0rd as the password and confirm it.
q. Press F11 to start the installation.
2. Wait until installation is completed and press Enter to reboot the system.
Rev. 21.41
Exercise 3: Configuring ESXi and scaling up an HPE Superdome Flex nPar

In this exercise you configure a static IP address for the ESXi system installed on your HPE Superdome Flex nPar. You
also scale up your nPar by adding an additional HPE Superdome Flex chassis.
1. To configure a static IP address for the ESXi system, complete the following steps:
b. Log in using the BMC credentials from the Class Info – Seat XX document located on the desktop of your
c. Click Launch KVM interface to open the remote console.
d. Press F2 and input P@ssw0rd as the password, and press Enter.
e. Use the arrow keys to select Configure Management Network and press Enter.
f. Use the arrow keys to select IPv4 Configuration and press Enter.
g. Use the arrow keys to select Set static IPv4 address and network configuration and press space.
h. Use the arrow keys to navigate between IPv4, Subnet Mask, and Default Gateway. Populate them with the
values from the Class Info – Seat XX document located on the desktop of your management server. Replace
XX with your group number. Use the values for ESXi00.
i. Press Enter when done.
j. Use the arrow keys to select DNS Configuration and press Enter.
k. Use the arrow keys to select Use the following DNS server addresses and hostname and press space.
l. Use the arrow keys to navigate between Primary DNS Server, Alternative DNS Server and Hostname.
Populate them with the values from the Class Info – Seat XX document located on the desktop. Replace XX
with your group number. Use values for ESXi00.
m. Click ESC and Y to restart the management network.
n. Open a new tab in Google Chrome and navigate to https://esxi00.hpe.local/ui. Confirm the security
exception if prompted and input root as the login name and P@ssw0rd as the password.
o. Click OK to close the message.
p. Write down the amount of memory and number of CPUs.
___________________________________________________________________________________________________
___________________________________________________________________________________________________
q. Close the browser tab.
Rev. 21.41
2. To add an additional HPE Superdome Flex chassis to your existing nPar, complete the following steps:
a. Navigate to the BMC screen and if the session expired, open the KVM interface again. Press F12 to shut down
ESXi, input P@ssw0rd to log in, and press F2. Wait until the system is powered off.
b. Navigate back to the RMC CLI (PuTTY session) if necessary, and reconnect to the RMC. Execute the command
show npar and verify that the nPar is powered off.
c. Execute the command show chassis and identify the second chassis which is not a part of an nPar.
d. Execute the command modify npar pnum=p1 add_chassis=XX, where XX should be replaced
with the BMC ID identified in the previous step, for example r091i28b.
e. Execute the command power on npar pnum=p1 to power on the extended nPar.
f. Open a new tab in a Google Chrome and navigate to https://esxi00.hpe.local/ui. Confirm the security
exception if prompted and input root as the login name and P@ssw0rd as the password.
g. Click OK to close the message.
h. Check the amount of memory and CPU capacity in your nPar. You should find that both of them have been
increased as a result of you adding a second HPE Superdome Flex chassis.
Rev. 21.41
Summary
In this lab, you prepared HPE Superdome Flex for an operating system installation, you installed and configured ESXi
on HPE Superdome Flex, and finally you expanded an nPar with second chassis.
Rev. 21.41
Rev. 21.41
Configuring HPE Synergy
Lab 3
Rev. 21.41
Configuring HPE Synergy Page 2
Learning objectives
• Create an IP address range for the management network
• Configure various types of networks and network sets
• Create logical interconnect groups
• Create an enclosure group
• Create a logical enclosure
• Explore logical interconnects
• Modify a logical interconnect group
• Add a SAN manager and modify an FC network
• Add an HPE Storage array
Requirement
NOTE
This lab is performed on the HPE Synergy simulator.
Rev. 21.41
Exercise 1: Creating an IP pool for management network

In this exercise, you create an IP address pool for the management network. This pool can be used to provide IP
addresses for iLOs in HPE Synergy compute modules and interconnect modules if applicable.
1. To prepare an IP address pool for a management network, complete the following steps:
a. Open Google Chrome and click the Synergy-Simulator bookmark. Confirm the security exception, if
prompted.
b. Log in using Synergy Simulator credentials from the Class Info – Seat XX document located on the desktop of
your management server. Replace XX with your group number.
c. Click the HPE OneView main menu, and select Settings.
d. Locate the Addresses and Identifiers section, hover your mouse over it, and click Edit.
e. A management subnet matching the HPE OneView management network has already been created. Click the
green pencil icon next to the existing subnet.
f. Click Add address range.
g. Enter Mgmt-Range in the name field. Enter 10.32.X.200 to 10.32.X.220 as the IP Address range,
where X is replaced with your group number, and click Add.
h. On the next screen, click Update.
i. Click OK to save the changes.
Rev. 21.41
Exercise 2: Creating networks and network sets, using HPE OneView

In this exercise, you define networks in HPE OneView. Using the graphical user interface, you create several networks
(one of each type and a management network). To create the remaining networks, you use a PowerShell script that
automates the process. These networks will be added to the logical interconnect group and will become available to
HPE Synergy compute nodes.
1. To create the HPE OneView management network, complete the following steps:
prompted.
c. From the HPE OneView main menu, in the NETWORKING section, select Networks.
d. Click + Create network to create a new network.
e. Enter Mgmt as the name of the network.
f. Set the network type to Ethernet by clicking the appropriate radio button.
g. From the drop-down menu next to VLAN, ensure Tagged is selected.
h. Enter 15 as the VLAN ID.
i. Associate the network with the IPv4 subnet ID that you created in the previous exercise (10.32.X.0).
j. From the drop-down menu next to Purpose, select Management.
k. Leave the other parameters at their default settings.
l. Click Create.
2. To create an FC network, complete the following steps:
a. Click + Create network.
b. Enter SAN-A as the name of the network.
c. Set the network type to Fibre Channel by clicking the appropriate radio button.
d. From the drop-down menu next to Fabric type, ensure Fabric attach is selected.
e. Leave the other parameters at their default settings. Click Create.
3. To create an FCoE network, complete the following steps:
b. Enter FCoE-A as the name of the network.
c. Set the network type to FCoE by clicking the appropriate radio button.
d. Enter 155 as the VLAN ID.
Rev. 21.41
4. To create an Ethernet network, complete the following steps:

b. Enter Production-A as the name of the network.
c. Set the network type to Ethernet by clicking the appropriate radio button.
d. From the drop-down menu next to VLAN, ensure Tagged is selected.
e. Enter 1101 as the VLAN ID.
f. Leave the other parameters at their default settings. Click Create.
5. To create an RoCE network, complete the following steps:
b. Enter RoCE-A as the name of the network.
c. Set the network type to RoCE by clicking the appropriate radio button.
d. Enter 255 as the VLAN ID.
f. You should have five networks visible.
Rev. 21.41
6. The remaining networks are created using a PowerShell script. To create additional networks, complete the
followings steps:
a. Start Windows PowerShell and type
cd C:\Users\Administrator\Desktop\ClassFiles\PSScripts to enter the folder
containing the PowerShell scripts. You can use the Tab key to auto-complete the name of the folder.
b. Type .\1-Networks.ps1 and press Enter.
c. Wait until the script has completed and return to HPE OneView. Navigate to the NETWORKING section and
select Networks. You should see the additional networks created by the PowerShell script. Using PowerShell
scripts can significantly speed up the configuration process.
Rev. 21.41
7. Network sets are aggregated networking objects that contain networks. A network set is an object you can assign
to network connections within server profiles to greatly simplify multiple network configuration management
tasks. To create a network set, complete the following steps:
a. From the HPE OneView main menu, in the NETWORKING section, select Network Sets.
b. Click + Create network set.
c. Enter Production-AB as the name, and ensure the type is set to Regular. Regular network sets support
up to 1000 VLANs, whereas large network sets can support up to 4034 VLANs.
d. Click Add networks to add networks to the network set.
e. Holding down the CTRL key, select Production-A and Production-B, and click Add.
f. Verify that both networks are added and click Create to create the network set. You will create a second
network set using a PowerShell script.
8. To create the second network set using a PowerShell script, complete the following steps:
a. Return to the PowerShell window, type .\2-Network-set.ps1 and press Enter. This script will create a
second network set.
b. Return to the Network Sets screen in HPE OneView, and verify that both network sets are visible.
Rev. 21.41
Exercise 3: Creating logical interconnect groups

In this exercise, you create LIGs that work as configuration templates for interconnect modules. You create one of
them using the HPE OneView interface. The other LIGs and uplink sets are created using PowerShell scripts.
1. To create the first LIG, complete the following steps:
prompted.
c. Navigate to the NETWORKING section and select Logical Interconnect Groups. You define the first LIG using
the HPE OneView interface.
d. Click + Create logical interconnect group.
e. Enter LIG-ETH as the LIG name, and select Virtual Connect SE 100Gb F32 Module for Synergy as the
Interconnect type.
f. Set the Enclosure count to 2.
g. Set the Interconnect bay set to 3.
h. Set the Redundancy to Highly available.
i. Set the Downlink speed to 50Gb/s.
j. Click Select interconnects. Review the other settings and leave them at their default values. Scroll up to the
top of the window, and under Logical Interconnect Group, click Add uplink set.
k. Enter NS-Uplink-AB as the name and select Ethernet as the type. Leave the other settings at their
default settings.
l. Scroll down to the Network Sets section. Instead of adding a network to the uplink set, you add a network set.
Click Add network set.
m. Select the Production-AB network set and click Add.
n. The Networks section above the Network Set section is populated with the networks from the network set.
o. In the Native column, mark the checkbox next to the Production-A network.
p. Scroll down to the Uplink Ports section and click Add uplink ports.
q. Enter Q1:2 in the search field and select port Q1:2 from interconnect bay 3. Click Add.
r. Click Create to add the uplink set and click Add uplink set again.
s. Enter NS-Uplink-CD as the name and select Ethernet as the type. Leave the other settings at their
default settings.
t. Scroll down to the Network Sets section. Instead of adding a network to the uplink set, you add a network set.
Click Add network set.
u. Select the Production-CD network set and click Add. The Networks section above the Network Set section is
populated with networks from the network set.
Rev. 21.41
v. In the Native column, mark the checkbox next to the Production-C network.
w. Scroll down to the Uplink Ports section and click Add uplink ports.
x. Enter Q1:3 in the search field and select port Q1:3 from interconnect bay 6. Click Add.
y. Click Create to add the uplink set.
z. On the Create Logical Interconnect Group window, click Create. The LIG is created. You create the remaining
uplink sets and LIGs using PowerShell scripts in the following steps.
2. To create the remaining logical interconnect groups, complete the following steps:
a. Go back to the PowerShell window, and reopen, if necessary. Enter .\3-Creating-LIGs.ps1 and press
Enter. This script creates the following LIGs:
• LIG for 12 Gb SAS switches installed in the first fabric (interconnects 1 and 4)
• LIG for VC FC 16 Gb modules installed in the first fabric (interconnects 1 and 4)
• LIG for VC FC 32 Gb modules installed in the second fabric (interconnects 2 and 5)
b. Go back to the HPE OneView interface and verify that all LIGs have been created. Most of the uplink sets are
missing, and they will be created using the next PowerShell script.
c. Go back to the PowerShell window, and reopen, if necessary. Enter .\4-Creating-UplinkSets.ps1
and press Enter. This script creates the remaining uplink sets on the rest of the LIGs.
Rev. 21.41
d. Go back to the HPE OneView interface and verify that the additional uplink sets have been added to LIG-ETH.
Explore the remaining LIGs, and verify that the additional uplinks have been created.
Rev. 21.41
Exercise 4: Creating an enclosure group

In this exercise, you configure an enclosure group. An enclosure group is a logical resource that defines a consistent
configuration for an enclosure or a set of enclosures making up a logical enclosure.
1. Before a logical enclosure can be created, an enclosure group must be created. To create an enclosure group,
complete the following steps:
prompted.
c. To create an enclosure group, from the main menu, navigate to the SERVERS section, and select Enclosure
Groups.
d. Click + Create enclosure group.
e. Enter Synergy-EG as the name and set the enclosure count to 2.
f. Mark the radio button next to Managed externally for IPv4 and IPv6 iLO / interconnect configuration.
g. Scroll down to the Interconnect Bay Configuration. You should see a diagram for both frames. Select LIG-ETH
for the third interconnect in Enclosure 1. It spans the LIG configuration on both frames. Do not click Create yet.
2. HPE Synergy additionally supports SAS and FC connectivity. Both are defined per frame. When setting up an
enclosure group, make sure that the SAS and FC connectivity is defined for each frame. To define FC and SAS
connectivity for this setup, complete the following steps:
a. For the first enclosure, from the drop-down menu next to interconnect 1, select LIG-FC16. The LIG for
interconnect 4 will be populated automatically.
Rev. 21.41
b. For the first enclosure, from the drop-down menu next to interconnect 2, select LIG-FC32. The LIG for
interconnect 5 will be populated automatically.
Rev. 21.41
c. For the second enclosure, from the drop-down menu next to interconnect 1, select LIG-SAS. The LIG for
interconnect 4 is populated automatically.
d. For the second enclosure, from the drop-down menu next to interconnect 2, select LIG-FC32. The LIG for
interconnect 5 is populated automatically.
e. Click Create to create the enclosure group.

f. Verify that the enclosure group has been created successfully.
Rev. 21.41
Exercise 5: Creating a logical enclosure

In this exercise, you create a logical enclosure. A logical enclosure contains the configuration intended for a set of
physical enclosures. Its initial values are taken from an enclosure group and applied to the physical enclosures. For
HPE Synergy, a logical enclosure can contain between one and five frames.
1. To create a logical enclosure, complete the following steps:
prompted.
c. Navigate to the SERVERS section and select Logical Enclosures from the menu.
d. Click + Create logical enclosure.
e. Enter Synergy-LE as the name. From the Enclosures drop-down menu, select the two available frames.
f. Use Synergy-EG as the Enclosure group.
g. From the drop-down menu next to Firmware baseline, select Manage manually.
h. Leave the IP address settings at their default values, and click Create to configure the logical enclosure. This
process takes between 10 to 15 minutes.
i. Wait until the logical enclosure is configured.
2. If the logical enclosure creation fails, or some components are not in a normal state, consult your instructor.
Rev. 21.41
Exercise 6: Exploring logical interconnects

In this exercise, you explore the logical interconnects created together with a logical enclosure. A logical interconnect
represents the available networks, uplink sets, and stacking links for a set of physical interconnects in a single
enclosure or a frame link topology. A logical interconnect represents a set of physical modules that we treat as one
entity from a management perspective.
To explore logical interconnects, complete the following steps:
1. Navigate to the NETWORKING section and select Logical Interconnects from the menu.
2. You should see five logical interconnects. Why do you see five logical interconnects?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. Select the Synergy-LE-LIG-ETH logical interconnect and click Actions. Review the available options.
4. From the drop-down menu next Synergy-LE-LIG-ETH, select Stacking Links.
5. You should see two stacking links. What is the purpose of the stacking links?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
6. Explore the other options within this logical interconnect, but do not perform any action that may be destructive.
7. Select Synergy-LE-LIG-FC32-1 and click Actions. What is the purpose of the “Redistribute logins” option?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
Rev. 21.41
Exercise 7: Modifying a logical interconnect group

In this exercise, you modify a LIG, and apply these changes to the existing configuration. Changing a LIG allows you
to update the configuration of multiple logical enclosures, using this configuration template. You will add a new
network to an existing network set, and add additional uplink ports to an existing uplink set.
1. To create an additional network, and modify a network set, complete the following steps:
prompted.
c. Navigate to the NETWORKING section and select Networks from the menu.
d. You will see a number of networks already created. Click + Create network to add one more network.
e. Enter Production-E as the name and select Ethernet as the type.
f. Select Tagged for VLAN, and enter 1105 for the VLAN ID.
g. Leave the other parameters at their default settings. Click Add to network sets to add this network to a
network set.
h. Select the Production-AB network set and click Add.
i. Verify that the network has been added to the correct network set and click Create.
2. To add additional uplink ports for an existing uplink set, complete the following steps:
a. Navigate to the NETWORKING section and select Logical Interconnect Groups.
b. Click LIG-ETH and verify that NS-Uplink-AB has three networks. When you add a network to a network set, it
automatically updates uplink sets as well.
c. Navigate to the NETWORKING section and select Logical Interconnects.
d. Click the Synergy-LE-LIG-ETH logical interconnect and verify that NS-Uplink-AB has three networks. The
change to the LIG was propagated automatically.
e. Navigate to the NETWORKING section and select Logical Interconnect Groups.
f. Click LIG-ETH, and from the Actions menu, select Edit.
g. Click the green pencil icon next to NS-Uplink-AB.
h. Scroll down to the Uplink Ports section and click Add uplink ports.
i. Enter Q1:2 in the search field and select port Q1:2 from interconnect 6.
j. Click Add.
k. Click OK to save changes.
l. Repeat steps g to k for NS-Uplink-CD, and add port Q1:3 from interconnect 3.
Rev. 21.41
3. The LIG has been modified, but these changes are not propagated to the logical interconnect. To update the
logical interconnect configuration, complete the following steps:
a. Navigate to the NETWORKING section and select Logical Interconnects.
b. The Synergy-LE-LIG-ETH logical interconnect should have a warning message, and the state should change
to yellow. Click the yellow banner, and read the message. It should inform you that the logical interconnect is
inconsistent with the logical interconnect group, LIG-ETH.
c. Click the Synergy-LE-LIG-ETH logical interconnect.
d. From the Actions menu, select Update from group. After this has been completed, this process applies
changes made to the LIG to the logical interconnect.
e. Review the automatic updates that will be made, and click Yes, update.
f. Mark the checkbox next to I have read and understand all of the implications, and click Yes, update one
more time to start the process.
g. Wait until the process completes. This should take about three to five minutes. Your logical interconnect
should now be consistent with the LIG.
Rev. 21.41
Exercise 8: Adding SAN managers and modifying HPE OneView networks

In this exercise, you use the HPE OneView interface and PowerShell scripts to add supported SAN managers to HPE
OneView. SAN managers are required if you want to automatically configure zoning on switches.
1. To add SAN managers to HPE OneView, complete the following steps:
prompted.
c. Navigate to STORAGE and select SAN Managers.
d. Click + Add SAN manager.
e. Select Brocade FOS Switch as the SAN manager type. You will add other SAN managers for this environment
using a PowerShell script.
f. Enter 172.18.19.1 as the IP address.
g. Enter dcs as the username and dcs as the password.
h. Click Add. After several seconds, the Brocade FOS Switch SAN manager is added to HPE OneView.
i. Click + Add SAN manager one more time to add a Cisco SAN manager.
j. Select Cisco as the SAN manager type.
k. Enter 172.18.20.1 as the IP address.
l. Set the security level to Authentication.
m. Enter dcs-SHA as the username and dcsdcsdcs as the password.
n. Click Add. Further Cisco SAN managers will be added using a PowerShell script.
o. Start the PowerShell Library for OneView, if necessary, and navigate to the ClassFiles folder. Input
.\5-SAN-Manager.ps1 and press Enter. The PowerShell script adds the remaining SAN managers.
Rev. 21.41
p. Verify that all SAN managers have been added.
q. From the main menu, navigate to the STORAGE section and select SANs. You should see all the SANs
imported through the SAN managers. If the SAN is in a discovered state, it means that it is not associated with
any HPE OneView network and automated zoning for this SAN will not work.
Rev. 21.41
2. To enable the auto-zoning functionality, the HPE OneView network must be associated with a SAN, imported
together with a SAN manager. To prepare the network for auto-zoning, complete the following steps:
a. From the main menu, navigate to NETWORKING, and select Networks.
b. Click SAN-A and from the Actions menu, select Edit.
c. From the drop-down menu next to Associated SAN, select VSAN30.
d. Click OK to save changes.
e. Click SAN-B and from the Actions menu, select Edit.
f. From the drop-down menu next to Associated SAN, select VSAN31.
g. Click OK to save the changes.
h. Go back to the STORAGE section and select SANs again.
i. SANs VSAN30 and VSAN31 should be in a managed state.
Rev. 21.41
Exercise 9: Adding HPE Storage components

In this exercise, you add HPE Storage arrays to HPE OneView. You will add some of them using the HPE OneView
interface, and the remaining arrays will be added using PowerShell scripts.
1. HPE OneView supports only HPE storage arrays. To add an HPE array to HPE OneView, complete the following
steps:
prompted.
c. From the main menu, navigate to STORAGE and select Storage Systems.
d. Click + Add storage system.
e. From the drop-down menu next to Storage system type, select StoreServ.
f. Enter 172.18.11.11 as the host name.
g. Enter dcs as both the username and password.
h. Click Connect.
i. From the drop-down menu next to Storage domain, select TestDomain.
j. After the virtual domain is selected, all available CPGs will be presented. Scroll down to the Storage Pools
section and click Select all to make all of them managed by HPE OneView. Only managed CPGs can be used
for volume provisioning.
k. Click Add to add the storage system to HPE OneView.
l. Navigate to STORAGE and select Storage Pools. Verify that all visible CPGs are in managed mode.
m. Navigate to STORAGE and select Storage Systems.
n. Click + Add storage system one more time to add an HPE Nimble array.
o. From the drop-down menu next to Storage system type select Nimble.
p. Enter 172.18.29.1 as the host name.
q. Enter dcs as both username and password.
r. Click Connect.
s. Scroll down to the Storage Pools section and click Select all to add the only storage pool as managed by HPE
OneView. Only managed CPGs can be used for volume provisioning.
t. Click Add to add the storage system to HPE OneView.
u. Remaining storage systems are added using a PowerShell script. Go back to the PowerShell Library for
OneView window, and enter .\6-Storage-Systems.ps1 then press Enter. It will add the remaining
3PAR and StoreVirtual systems.
v. Navigate to STORAGE and select Storage Systems. Verify that additional arrays have been added.
Rev. 21.41
w. Navigate to STORAGE and select Storage Pools. Verify that additional storage pools were imported together
with arrays.
2. After all storage systems are added, you must modify the port settings. In a production environment, it can be
done when adding a storage system to HPE OneView. To set the port for an HPE 3PAR array, complete the
following steps:
a. Navigate to STORAGE, and select Storage Systems,
b. Click ThreePAR-1, and from the Actions menu, select Edit.
c. From the drop-down menu next to port 0:4:1, in the Expected SAN/Network column, select the FCoE-A
network.
d. From the drop-down menu next to port 1:4:1, in the Expected SAN/Network column, select the FCoE-A
network.
e. From the drop-down menu next to port 0:4:2, in the Expected SAN/Network column, select the FCoE-B
network.
f. From the drop-down menu next to port 1:4:2, in the Expected SAN/Network column, select the FCoE-B
network.
g. Click OK to save the changes.
Rev. 21.41
Summary
During this lab, you used HPE OneView to perform the following configuration tasks:
• Add an IP address range for the management network
• Configure various types of networks and network sets
• Create logical interconnect groups
• Create an enclosure group
• Create a logical enclosure
• Explore logical interconnects
• Modify a logical interconnect group
• Add SAN manager and modified FC networks
• Add HPE storage arrays
Rev. 21.41
Rev. 21.41
Managing storage for HPE compute
solutions
Lab 4
Rev. 21.41
Learning objectives
• Perform basic storage management using array management tools
• Import CPGs and virtual volumes to HPE OneView
• Work with volume templates
• Manage volumes using HPE OneView
• Optimize a virtual volume
Requirement
NOTE
Rev. 21.41
Exercise 1: Basic storage management using array management tools

In this exercise, you perform basic storage management using the array management tool SSMC. You create a CPG
and a set of volumes.
1. To create a new CPG, complete the following steps:
a. Open Google Chrome and click the Primera & 3PAR SSMC bookmark. Confirm the security exception, if
prompted.
b. Log in using the SSMC credentials from the Class Info – Seat XX document located on the desktop of your
c. Click close if the navigation tutorial appears.
d. Click the Primera & 3PAR SSMC banner at the top left part of the screen to expand the main menu.
e. At the right side of the main menu, click show all. The main menu expands and presents additional
configuration options.
f. From the BLOCK PERSONA section click Common Provisioning Groups.
g. You will see a number of CPGs already present. Some of them are created automatically based on the available
types of drives and some of them are created by other students as this array is shared. Do not interact with
the existing objects. Click + Create CPG to create a new CPG.
h. Enter XX-NL-CPG as the name, where XX should be replaced with your group number.
i. Scroll down to Allocation Settings.
j. From the drop-down menu next to Device type, select NL.
k. From the drop-down menu next to RAID type, select RAID 1.
l. From the drop-down menu next to Availability, select Magazine (Lower).
m. Click Create to create a new CPG based on NL capacity.
n. Click + Create CPG again.
o. Enter XX-SSD-CPG as the name, where XX should be replaced with your group number.
p. Scroll down to Allocation Settings.
q. From the drop-down menu next to Device type, select SSD.
r. From the drop-down menu next to RAID type, select RAID 5.
s. From the drop-down menu next to Availability, select Magazine (Lower).
t. Click Create to create a new CPG based on SSD capacity.
Rev. 21.41
2. To create a new virtual volume, complete the following steps:

a. Click the Primera & 3PAR SSMC banner at top left part of the screen to expand the main menu.
b. From the BLOCK PERSONA section click Virtual Volumes.
c. You will see a number of virtual volumes already created. Some of them are system drives and some of them
are created by other students as this array is shared. Do not interact with the existing objects. Click + Create
virtual volume to create a new virtual volume.
d. Enter XX-NL-Vol as the name, where XX should be replaced with your group number.
e. From the drop-down menu next to Provisioning select Fully Provisioned.
f. From the drop-down menu next to CPG select XX-NL-CPG, where XX should be replaced with your group
number.
g. Enter 10 as the volume size. This volume will be used to demonstrate different SSMC and HPE OneView
functionalities and a small capacity will be sufficient for this.
h. Click Create to create the virtual volume.
i. Click + Create virtual volume again to create a second virtual volume.
j. Enter XX-SSD-Vol as the name, where XX should be replaced with your group number.
k. Verify that Provisioning is set to Thin Provisioned (default value).
l. Click the switch next to Dedup to enable deduplication for this volume.
m. From the drop-down menu next to CPG select XX-SSD-CPG, where XX should be replaced with your group
number.
n. Enter 100 as the volume size.
o. Click Create to create the virtual volume. You should have two volumes created, one using NL capacity and a
second one using SSD capacity.
Rev. 21.41
Exercise 2: Importing CPGs and virtual volumes to HPE OneView

In this exercise, you import the CPGs and virtual volumes you created in the previous exercise to HPE OneView. An
HPE 3PAR and HPE Primera are imported to HPE OneView already.
1. To add your newly create CPGs to HPE OneView, complete the following steps:
b. Log in using the HPE Synergy credentials from the Class Info – Seat XX document located on the desktop of
c. From the HPE OneView main menu, in the STORAGE section, select Storage Systems.
d. Click K32-3PAR and from the Actions menu select Refresh.
e. From the HPE OneView main menu, in the STORAGE section, select Storage Pools.
f. You should see all of the CPGs configured on this array. Click XX-NL-CPG, where XX should be replaced with
your group number. It should be in the Discovered state. This means that volume provisioning is not enabled
for this storage pool. From the Actions menu select Edit.
g. Change the state to Managed by clicking the appropriate radio button and click OK to save the changes.
Changing the state to managed enables volume provisioning for this pool using HPE OneView.
h. Repeat steps f and g to enable volume provisioning for XX-SSD-CPG, where XX should be replaced with your
group number.
2. Volumes created using array management tools can be imported to HPE OneView. To add existing 3PAR
volumes to HPE OneView, complete the following steps:
a. From the HPE OneView main menu, in the STORAGE section, select Volumes.
b. Click + Add volume.
c. From the drop-down menu next to Storage system select K32-3PAR.
d. In the field next to the Storage system volume name enter XX-NL-Vol, where XX should be replaced with
your group number.
e. Keep sharing type set to Private, click Add and wait until the volume is added.
f. Repeat steps b to e to add XX-SSD-Vol, where XX should be replaced with your group number. This time, in
step e, select Shared rather than Private.
Rev. 21.41
Exercise 3: Working with volume templates using HPE OneView

In this exercise you use HPE OneView for volume management. You work with volume templates and perform a
variety of management actions on the volumes.
1. To simplify volume creation using HPE OneView, volume templates can be used. To create a volume template,
complete the following steps:
c. From the HPE OneView main menu, in the STORAGE section, select Volume Templates.
d. Click + Create volume template.
e. In the field next to Name enter XX-Private-NL, where XX should be replaced with your group number.
f. From the drop-down menu next to Storage pool select XX-NL-CPG, where XX should be replaced with your
group number.
g. Next to the Capacity option click the open padlock icon to close it. This means that when provisioning a
volume using this template, the user cannot change the volume size. In the field next to Capacity, enter 16 as
the volume size.
h. In the field next to Sharing click the open padlock icon again and leave sharing set to Private.
i. Leave the other parameters at their defaults and click Create to create the volume template.
j. Click + Create volume template again.
k. In the field next to Name enter XX-Shared-SSD, where XX should be replaced with your group number.
l. From the drop-down menu next to Storage pool select XX-SSD-CPG, where XX should be replaced with your
group number.
m. In the field next to Capacity click the open padlock icon that should now close. This means that when
provisioning a volume using this template, the user cannot change the volume size. Enter 100 as the volume
size.
n. In the field next to Sharing click the open padlock icon again and set sharing to Shared.
o. In the Advanced section click the checkbox next to Enable deduplication.
p. Leave all other parameters at their defaults and click Create to create the volume template.
Rev. 21.41
2. To test volume template functionality, complete the following steps:

a. Click the XX-Private-NL volume template and from the Actions menu select Create volume.
b. In the field next to Name enter XX-FromTemplate, where XX should be replaced with your group number
and click Create. Note that you cannot change any of the volume parameters, as all of them were locked within
the template.
c. Wait until the volume has been created.
Rev. 21.41
Exercise 4: Managing volumes using HPE OneView

In this exercise you manage volumes using HPE OneView. You grow a volume and delete a volume.
1. Using HPE OneView you can increase (but not decrease) the size of virtual volumes. To increase the size of a
virtual volume, complete the following steps:
c. From the HPE OneView main menu, in the STORAGE section, select Volumes.
d. Click the XX-FromTemplate volume, where XX should be replaced with your group number and from the
Actions menu select Edit. You cannot change any parameters, including size, as defined by the volume
template.
e. From the HPE OneView main menu, in the STORAGE section, select Volume Templates.
f. Click the XX-Private-NL volume template, where XX should be replaced with your group number and from
the Actions menu select Edit.
g. Next to the Capacity option click the padlock icon to open it (this allows you to change volume size) and click
OK.
h. From the HPE OneView main menu, in the STORAGE section, select Volumes.
i. Click the XX-FromTemplate volume, where XX should be replaced with your group number and from the
Actions menu select Edit.
j. Now you should be able to change the volume size. Enter 54 as the new volume size and click OK. Verify that
the size of this volume is now 54GiB.
k. Open a new tab in Google Chrome, and click the Primera & 3PAR SSMC bookmark. Confirm the security
exception, if prompted
l. Log in using the SSMC credentials from the Class Info – Seat XX document located on the desktop of your
m. Click the Primera & 3PAR SSMC banner at the top left part of the screen to expand the main menu.
n. From the BLOCK PERSONA section click Virtual Volumes.
o. Click the XX-FromTemplate volume, where XX should be replaced with your group number and verify that
the new size is visible in SSMC.
Rev. 21.41
2. HPE OneView can be used to delete virtual volumes. Volumes can be deleted from HPE OneView only (un-import
procedure) or they can be deleted from HPE OneView and the storage system. To un-import the volume and
delete the volume, complete the following steps:
a. Navigate back to HPE OneView used to manage the HPE Synergy platform.
b. From the HPE OneView main menu, in the STORAGE section, select Volumes.
c. Click the XX-FromTemplate volume, where XX should be replaced with your group number, and from the
Actions menu, select Delete.
d. Make sure that the radio button next to OneView and the storage system is selected and click Yes, delete.
e. Navigate back to SSMC and from the BLOCK PERSONA section, click Virtual Volumes. Verify that the
XX-FromTemplate volume, where XX should be replaced with your group number, is deleted from the
storage system also.
f. Navigate back to HPE OneView and click XX-NL-Vol, where XX should be replaced with your group number
and from the Actions menu, select Delete.
g. This time make sure that the radio button next to OneView only is selected and click Yes, delete.
h. Navigate back to SSMC and verify that XX-NL-Vol, where XX should be replaced with your group number, is
still available on the storage system.
Rev. 21.41
Exercise 5: Optimizing virtual volumes

In this exercise you optimize virtual volumes using the tune operation. You move a virtual volume between CPGs with
different characteristics.
1. To optimize a virtual volume, complete the following steps:
a. Open Google Chrome and click the Primera & 3PAR SSMC bookmark. Confirm the security exception, if
prompted.
b. Log in using the SSMC credentials from the Class Info – Seat XX document located on the desktop of your
c. Click the Primera & 3PAR SSMC banner at the top left part of the screen to expand the main menu.
d. From the BLOCK PERSONA section click Virtual Volumes.
e. Click the XX-NL-Vol volume, where XX should be replaced with your group number, and from the Actions
menu, select Tune.
f. On the Tune screen, locate the CPG section and click the radio button next to Move to another CPG. This
option allows you to move the selected virtual volume from the NL CPG to the SSD CPG.
g. From the drop-down menu next to Move to, select XX-SSD-CPG where XX should be replaced with your
group number.
h. Click Tune to confirm the change. Wait until the process is completed and verify that the volume has been
moved to the selected CPG.
i. Click the XX-NL-Vol volume, where XX should be replaced with your group number and from the Actions
menu select Tune. This time you will change the CPG for copy space.
j. Locate the Virtual Volumes section and click the radio button next to Copy space.
k. On the Tune screen, locate the CPG section and click the radio button next to Move to another CPG. This
option allows you to move the selected virtual volume from the NL CPG to the SSD CPG.
l. From the drop-down menu next to Move to, select XX-SSD-CPG where XX should be replaced with your group
number.
m. Click Tune to confirm the change. Wait until the process is complete and verify that the copy space has been
moved to the selected CPG.
Rev. 21.41
Summary
During this lab you performed basic storage management using array management tools, imported CPGs and virtual
volumes to HPE OneView, worked with volume templates, managed volumes using HPE OneView and optimized a
virtual volume.
Rev. 21.41
Rev. 21.41
Working with HPE OneView server
profiles
Lab 5
Rev. 21.41
Working with HPE OneView server profiles Page 2
Learning objectives
• Create a server profile for an HPE Synergy compute node
• Configure MPIO for the Windows operating system
• Prepare a data volume for a compute node and test snapshot functionality
• Manage downlink aggregation
Requirement
NOTE
Rev. 21.41
Exercise 1: Creating a server profile for an HPE Synergy compute node

In this exercise, you create a server profile for an HPE Synergy compute node. To boot the compute node, you use an
existing volume with the Windows operating system installed. As you have only one Windows machine, you do not
need a server profile template.
1. To create a server profile for an HPE Synergy compute node, complete the following steps:
c. From the HPE OneView main menu, in the SERVERS section, select Server profiles and click + Create profile.
d. In the field next to Name enter XX-Windows, where XX should be replaced with your group number.
e. From the drop-down menu next to Server profile template select None.
f. From the drop-down menu next to Server hardware, select the first server allocated to your group. Refer to the
table below. Server hardware type and enclosure group will be populated automatically. If the server is
powered on, power it off.
Rev. 21.41
2. To define Ethernet connections within your server profile, complete the following steps:
a. Scroll down to the Connections section and click Add connection.
b. In the field next to Name enter Mgmt-A.
c. From the drop-down menu next to Network, select StudentXX-Mgmt, where XX should be replaced with your
group number.
d. Leave the other parameters at their defaults and click Add + to add another connection.
e. In the field next to Name enter Mgmt-B.
f. From the drop-down menu next to Network, select StudentXX-Mgmt, where XX should be replaced with your
group number.
g. Leave the other parameters at their defaults and click Add + to add another connection.
3. To define Fibre Channel connections within a server profile, complete the following steps:
a. In the field next to Name enter FC-A.
b. From the drop-down menu next to Function type select Fibre Channel.
c. From the drop-down menu next to Network, select FC-Net-A.
d. From the drop-down menu next to Boot select FC primary and make sure that Managed volume is selected in
the Boot from section.
e. Leave the other parameters at their defaults and click Add + button to add another FC connection.
f. In the field next to Name enter FC-B.
g. From the drop-down menu next to Function type select Fibre Channel.
h. From the drop-down menu next to Network, select FC-Net-B.
i. From the drop-down menu next to Boot select FC secondary and make sure that Managed volume is selected
in the Boot from section.
j. Leave the other parameters at their defaults and click Add. You should have four connections defined.
4. To add a boot volume to the server profile, complete the following steps:
a. Scroll down to the SAN Storage section and click the checkbox next to Manage SAN Storage.
b. From the drop-down menu next to Host OS type, select Windows Server 2019 and click Add volume.
c. From the drop-down menu next to Attach Volume select K32-SXX-WindowsBoot, where XX should be
replaced with your group number.
d. From the drop-down menu next to Boot select Primary and click Add.
Rev. 21.41
5. To configure all remaining server profile options, complete the following steps:
a. Scroll down to the Boot Settings section and from the drop-down menu next to Boot mode select
UEFI optimized.
b. Scroll down to the Advanced section, and set the MAC addresses and WWN addresses to Physical. In the lab
environment selecting physical WWNs or MAC addresses may be greyed out if the virtual pools are disabled in
HPE OneView.
c. Click Create to create the server profile.

d. Wait until the server profile has been created.
e. Click your server profile and from the Actions menu select Power on.
Rev. 21.41
Exercise 2: Configuring MPIO for the Windows operating system

In this exercise you install and configure MPIO.
1. To check current disk status, complete the following steps:
a. From the HPE OneView main menu, from the SERVERS section, select Server Profiles.
b. Click XX-Windows, where XX should be replaced with your group number.
c. If necessary, from the Actions menu, select Launch HTML5 console. Confirm the security exception, if
prompted.
d. If necessary, click the menu icon in the top left corner of the console window, select Power and click
Momentary Press to power the system on.
e. After the console has opened and the system has finished booting, click the Keyboard from the console top
menu, press CTRL-ALT-DEL, and type P@ssw0rd as the password. Press Enter.
f. If you see a message about Windows Admin Center, click the checkbox next to Don’t show this message
again and close the message.
g. In the Server Manager, click Tools and select Computer Management.
h. In Computer Management click Disk Management.
i. You should see one 80GB drive in an online state and 3 disks with the same size but in offline mode. In fact,
this is the same drive, but MPIO is not installed and the OS can see four copies of the same drive. This can be
fixed by installing and configuring MPIO. Close Computer Management window and return to Server Manager.
You may see additional drives depending on the server configuration.
2. To configure MPIO for the Windows operating system, complete the following steps:
a. In the Server Manager, click Manage and select Add Roles and Features.
b. Click Next four times to get to the screen where you can select server features.
c. Click the checkbox next to Multipath I/O and click Next. If the checkbox is already greyed out, close the Add
Roles and Features Wizard and skip to step g.
d. Select the checkbox next to Restart the destination server automatically if required. If a restart is required
it will be done automatically. Click Yes to confirm.
e. Click Install to install MPIO. After MPIO is installed, the server will reboot.
f. Wait for the reboot to be completed and log in to Windows, click Close at the installation progress screen.
g. In the Server Manager, click Tools and select MPIO.
h. On the MPIO Devices tab click Add.
i. Enter 3PARdataVV and click OK. Click OK two more times if necessary.
j. Reboot the server.
k. In the Server Manager, click Tools and select Computer Management.
l. In Computer Management click Disk Management. The boot volume should display correctly.
Rev. 21.41
Exercise 3: Working with data volumes and snapshot functionality

In this exercise you prepare a data volume on HPE 3PAR, present it to the Windows server and test array-based
snapshot functionality.
1. To create a data volume for your Windows system, complete the following steps:
a. Open Google Chrome, and click the Synergy bookmark. Confirm the security exception, if prompted.
c. From the HPE OneView main menu, in the STORAGE section, select Volumes.
d. Click + Create volume and enter XX-DataVolume, where XX should be replaced with your group number.
e. From the drop-down menu next to Volume template select XX-Private-NL. All the fields for the volume will be
populated. Click Create to create the volume.
f. Open a new tab in Google Chrome and click the Primera & 3PAR SSMC bookmark. Confirm the security
exception, if prompted.
g. Log in using the SSMC credentials from the Class Info – Seat XX document located on the desktop of your
h. Click the Primera & 3PAR SSMC banner in the top left part of the screen to expand the main menu.
i. From the BLOCK PERSONA section click Virtual Volumes. Verify that the new volume has been created.
j. From the HPE OneView main menu, in the SERVERS section, select Server Profiles.
k. Click XX-Windows, where XX should be replaced with your group number and from the Actions menu select
Edit.
l. Scroll-down to the SAN Storage section and click Add volume.
m. Expand the drop-down menu next to Attach Volume and select XX-DataVolume, where XX should be
replaced with your group number. Click Add to add this volume to your server profile. Note that the server is
powered on.
n. Click OK to save the changes to the server profile.
o. Return to the Windows iLO console. If necessary, in the Server Manager, click Tools, select Computer
Management and click Disk Management.
p. From the Action menu select Rescan Disks. Scroll down and you should see the 16GB volume that you added
to the server profile.
2. To prepare this volume for snapshot testing, complete the following steps:
a. Right-click the 16 GB disk and select Online.
b. Right-click the drive again and select Initialize Disk. Ensure that GPT is selected and click OK to initialize the
volume.
c. Right click the unallocated space and select New Simple Volume. Click Next three times.
Rev. 21.41
d. Enter DataVolume as the Volume label. Click Next and Finish.

e. Navigate to the DataVolume using Windows Explorer and create a folder with the name Folder created for
snapshot testing. You will use it to test the snapshot functionality.
3. To test snapshot functionality, complete the following steps:
a. Return to HPE OneView and from the main menu, in the STORAGE section, select Volumes.
b. Click XX-DataVolume, where XX should be replaced with your group number and from the Actions menu
select Create snapshot.
c. Enter a snapshot description and click Create.
d. From the menu next to the server profile name select Snapshots and verify that the snapshot has been
created.
e. To test the snapshot feature, navigate to the DataVolume using Windows Explorer and delete the folder with
the name Folder created for snapshot testing.
f. Return to HPE OneView and click Revert next to the snapshot name. You will get the message that the
volume cannot be reverted when the server profile has enabled storage paths to the volume. Click Close.
g. From the HPE OneView main menu, in the SERVERS section, select Server Profiles.
h. Click XX-Windows, where XX should be replaced with your group number and from the Actions menu select
Edit.
i. Scroll-down to the SAN Storage section and click the green pencil icon next to XX-DataVolume, where XX
should be replaced with your group number, to edit this volume.
j. Remove the checkboxes for both paths in the Enabled column. Click OK to accept the changes and disconnect
the volume. Click OK, and click OK again when the warning message is displayed.
k. Return to HPE OneView and from the main menu, in the STORAGE section, select Volumes.
l. Click XX-DataVolume, where XX should be replaced with your group number. From the menu next to the
server profile name select Snapshots and click Revert next to the snapshot name.
m. Click Yes, revert. The revert process should be completed instantly. If reverting to the snapshot was
successful, the deleted folder should be available again. To test it, the volume must be reconnected.
n. From the HPE OneView main menu, in the SERVERS section, select Server Profiles.
o. Click XX-Windows, where XX should be replaced with your group number. From the Actions menu select Edit.
p. Scroll down to the SAN Storage section and click the green pencil icon next to XX-DataVolume, where XX
should be replaced with your group number, to edit this volume.
q. Click the checkboxes for both paths in the Enabled column to reconnect the volume. Click OK two times.
r. Return to the Windows Server iLO console and in the Server Manager, click Tools and select Computer
Management.
s. Click Disk Management and from the Action menu select Rescan Disks to discover the reverted drive.
t. Open Windows explorer and verify that the deleted folder is accessible, proving that the snapshot functionality
has worked correctly.
Rev. 21.41
Exercise 4: Working with downlink aggregation

In this exercise you configure LACP over s-channel within the server profile and configure required NIC teaming
options at the operating system level.
1. To configure a Link Aggregation Group, complete the following steps:
c. From the HPE OneView main menu, in the SERVERS section, select Server Profiles.
d. Click XX-Windows, where XX should be replaced with your group number and from the Actions menu select
Edit.
e. Scroll-down to the Connections section and click the green pencil next to Mgmt-A.
f. From the drop-down menu, next to Link aggregation group select LAG1 and click OK.
g. Repeat steps e and f for the Mgmt-B connection.
h. Click OK to save the changes to the server profile. Wait until the changes have been applied.
2. For a proper LAG configuration, appropriate NIC teaming options must be configured. To configure the required
NIC teaming options, complete the following steps:
a. Log in to your Windows system and from the Server Manager, select Local Server from the menu on the left
hand side.
b. Click Disabled next to the NIC Teaming option.
c. From the Tasks menu in the TEAMS section select New Team.
d. Enter Team01 as the name of your team and select both adapters.
e. Click the Additional Properties menu and from the drop-down menu next to Teaming mode select LACP and
from the drop-down menu next to Load balancing mode select Dynamic. Click OK to configure the team.
f. After enabling a LAG in a server profile, you may see your server profile in a critical state with the following
message.
g. After configuration, the NIC teaming error on the server profile will disappear.
Rev. 21.41
3. To test the NIC teaming configuration, complete the following steps:

a. Return to the Windows console and if necessary, from the Actions menu, select Launch HTML5 console.
b. After the console has opened and the system has finished booting, from the console top menu bar click
Keyboard, press CTRL-ALT-DEL and type P@ssw0rd as the password. Press Enter.
c. Right-click the network adapter icon, and select Open Network & Internet Settings.
d. Click Ethernet and select Network and Sharing Center.

e. Click Change adapter settings, and right-click the Team-01 adapter that was created when you configured
NIC teaming.
f. Select Properties and double-click Internet Protocol Version 4 (TCP/IPv4).
g. Set the IP properties for ESXi01, as defined in the Class Info – Seat XX document located on the desktop of
your management server, where XX should be replaced with your group number.
h. Click OK when all parameters have been configured. Click Close.
i. To test NIC teaming functionality, open a command prompt and execute the ping command with the –t
parameter. Ping the IP address configured in step g. If ping does not work, disable the firewall for the active
connection.
Rev. 21.41
j. From the Server Manager, select Local Server from the menu on the left hand side.
k. Click Enabled next to the NIC Teaming option. It will take you to the NIC team.
l. Click the first network adapter in the ADAPTERS AND INTERFACES section and from the TASKS menu click
Disable.
m. Return to the command prompt with the ping command running and you should see that none of the pings are
lost.
n. Click the first network adapter in the ADAPTERS AND INTERFACES section and from the TASKS menu click
Enable.
o. You may test the NIC team by disabling the second network adapter.
4. To prepare for subsequent labs you need to delete your XX-Windows server profile. To delete it, complete the
following steps:
a. Return to HPE OneView used to manage HPE Synergy and from the HPE OneView main menu, in the
SERVERS section, select Server Profiles.
b. Click XX-Windows, where XX should be replaced with your group number and from the Actions menu select
Power off.
c. Click Press and hold and wait until server is powered off.
d. From the Actions menu select Delete and click Yes, delete.
Rev. 21.41
Summary
During this lab you created a server profile for an HPE Synergy compute node, configured MPIO for the Windows
operating system, prepared a data volume for the compute node and tested snapshot functionality. You also
managed downlink aggregation.
Rev. 21.41
Configuring iLO Federation
Lab 6
Rev. 21.41
Configuring iLO Federation Page 2
Learning objectives
After completing this lab, you should be able to configure iLO Federation.
Requirement
NOTE
Rev. 21.41
Exercise 1: Configuring iLO Federation

In this exercise, you configure and test iLO Federation functionality. Once configured, you will be able to perform
actions on groups of iLO management processors. For iLO Federation setup, you will use the three compute nodes
assigned to your group.
1. To configure iLO Federation, complete the following steps:
b. Log in using HPE Synergy credentials from the Class Info – Seat XX document located on the desktop of your
c. From the HPE OneView main menu, in the SERVERS section, select Server hardware.
d. Locate and click the first server allocated to your group.
e. Click the iLO address to open the iLO interface. Confirm the security exception if prompted.
f. From the menu on the left, click Power & Thermal. Make sure that the server is powered off. If not, click Press
and Hold and confirm by clicking OK. Systems do not have to be powered on to join a Federation Group.
g. From the menu on the left, click iLO Federation. On the Setup tab, click Join Group.
h. Enter XX-Federation as the Group Name, where XX should be replaced with your group number.
i. Enter P@ssw0rd as the Group Key and Group Key Confirmation.
j. In the Group Permissions, click the checkbox next to select all.
Rev. 21.41
k. Scroll down and click Join Group.

l. You will be returned to the iLO Federation – Setup screen. In the Multicast Options locate Multicast
Announcement Interval (seconds/minutes)* and click the drop-down menu. Change the interval to 30s.
m. Click Apply.
n. Repeat steps c to m for the second and third server allocated to your group.
o. After around 30 seconds your three servers should show up in the newly created iLO Federation group.
2. To test the iLO Federation, complete the following steps:
a. From any iLO click iLO Federation from the menu on the left.
b. Click Multi-System View and from the drop-down menu under Select Group, select XX-Federation, where XX
should be replaced with your group number. You should see the three systems that you added to the group.
c. Click the Group Power tab and click Momentary Press button to power on all servers.
d. Click Yes, power on to confirm the procedure. All of the servers in the federation will power on. Verify that all
of your systems are booting.
e. Explore the other available options from the iLO Federation section.
Rev. 21.41
Summary
During this lab you created an iLO Federation group and used it to power on systems in that group. You also
explored other options available through the federation.
Rev. 21.41
Rev. 21.41
Working with HPE OneView for
VMware vCenter Server
Lab 7
Rev. 21.41
Working with HPE OneView for VMware vCenter Server Page 2
Learning objectives
• Verify proper integration of the required components
• Prepare an OS Deployment Plan
• Prepare a server profile template
• Prepare HPE Synergy compute nodes for ESXi deployment
• Deploy an ESXi system using HPE OneView for VMware vCenter Server
• Use grow and shrink cluster functionalities
Requirement
NOTE
Rev. 21.41
Exercise 1: Verify proper integration of the required components

In this exercise you verify that all required components (vCenter Server, HPE OneView and HPE OneView for VMware
vCenter Server) are properly integrated. To use HPE OneView for vCenter Server, it must be integrated with vCenter
Server, and HPE OneView credentials must be added to the vCenter Server.
1. To verify proper HPE OneView for VMware vCenter Server integration with vCenter Server, complete the
following steps:
a. Open Google Chrome and click the HPE OneView for VMware vCenter bookmark. Confirm the security
exception, if prompted.
b. Log in using the OV4VC credentials from the Class Info – Seat XX document located on the desktop of your
c. At the top of the screen, on the left-hand side, click HPE OneView for VMware vCenter to expand the main
menu.
d. From the Managers section, click vCenters.
e. Verify that sXX-vcenter-a.hpe.local and sXX-vcenter-b.hpe.local are present, where XX should be replaced
with your group number..
f. Open a new tab in Google Chrome and click the vCenter-a bookmark. Confirm the security exception, if
prompted.
g. Log in using the vCenter-a credentials from the Class Info – Seat XX document located on the desktop of
your management server. Replace XX with your group number. Click the vSphere Client banner and verify
that the components highlighted in the image below are visible. If this is the case, the plugin is properly
installed. Stay logged in to the vCenter Server.
Rev. 21.41
2. To verify that HPE OneView credentials have been added properly to the vCenter Server, complete the following
steps:
a. On the Shortcuts screen in the vCenter Server, from the Administration section, click HPE OneView for
vCenter.
b. From the menu on the left-hand side, from the HPE OneView for VMware vCenter section, select OneView
Credentials. Verify that the HPE OneView credentials have been added.
Rev. 21.41
Exercise 2: Preparing an OS Deployment Plan

In this exercise you prepare an OS Deployment Plan that you will use to deploy the ESXi system to HPE Synergy
compute nodes.
1. To prepare an OS Deployment Plan, complete the following steps:
a. Open a new tab in Google Chrome and click the vCenter-a bookmark. Confirm the security exception, if
prompted.
b. Log in using vCenter-a credentials from the Class Info – Seat XX document located on the desktop of your
c. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, from the Administration
section click HPE OneView for vCenter.
d. From the menu on the left-hand side, from the HPE OneView for VMware vCenter section, select
Deployment.
e. Click + CREATE OS BUILD PLAN.
f. When the new window opens, enter XX-ESXi7.0U1-Deployment as the OS build plan name, where XX
should be replaced with your group number.
g. Enter ESXi 7.0 U1 Deployment Plan as the description.
h. Enter ESXi 7.0 U1 as the Type and x64 as the Architecture.
i. Click Create, and then click OK to close the message window.
j. Select your OS build plan, and click Browse to upload the ESXi image.
k. On the desktop of your management server, navigate to the ClassFiles folder, and select the ESXi ISO image
VMware-ESXi-7.0.1-17551050-HPE-701.0.0.10.7.5.16-May2021-Synergy.
l. Click START UPLOAD.
m. If there is a certificate error message, click OK, then ACCEPT CERTIFICATE. Confirm the security exception if
prompted.
NOTE
If a new browser tab opens and displays OV4VC service is up and running, return to the original tab without
closing the new tab, and proceed to the next step.
n. Repeat steps j to l to upload the ESXi image.

o. The upload starts. Wait until the image upload completes. It should take around 10 seconds.
2. Verify that the OS build plan has been created and that the image has been uploaded.
Rev. 21.41
Exercise 3: Preparing a server profile template

In this exercise you prepare a server profile template, which is required for ESXi deployment using HPE OneView for
VMware vCenter Server.
1. To prepare a server profile template, complete the following steps:
b. Log in using HPE Synergy credentials from the Class Info – Seat XX document. Replace XX with your group
number.
c. From the HPE OneView main menu, navigate to SERVERS, and select Server Profile Templates.
d. Click + Create server profile template.
e. Enter XX-ESXi-OVVC as the name, where XX should be replaced with your group number. The HPE
Synergy platform is shared by all students, so following the proper naming convention is critical.
f. Optionally, enter the description: Server Profile Template for ESXi cluster nodes.
g. In the Server Profile section, enter the server profile description of your choice.
h. Select SY 480 Gen10 1 as the server hardware type, and select the only available Enclosure group.
i. Leave the default settings for Affinity.
j. Leave the default settings for the OS Deployment and Firmware sections.
k. Scroll down to the Connections section and from the menu next to Consistency checking select Exact match.
l. In the Connections section, click Add connection to add an Ethernet connection.
m. In the Add Connection window, enter Management-A as the name.
n. Select Ethernet as the function type, and from the drop-down menu next to Network, select StudentXX-
Mgmt (VLAN 32XX), where XX should be replaced with your group number. Make sure that you use the
correct network, otherwise your servers will have no connection to the management network.
o. Leave the other parameters at their default settings, and click Add.
p. You will return to the main server profile template screen.
q. Scroll down to the Boot Settings section, and select UEFI Optimized as the boot mode.
Rev. 21.41
r. Scroll down to the Advanced section and set the MAC addresses and WWN addresses to Physical.
s. Leave all other parameters at their default settings. Click Create to create the server profile template.
2. Verify that server profile template has been created and is accessible.
Rev. 21.41
Exercise 4: Preparing HPE Synergy compute nodes for ESXi system deployment
In this exercise you prepare HPE Synergy compute nodes for ESXi deployment using HPE OneView for VMware
vCenter Server.
1. To prepare HPE Synergy compute nodes for ESXi deployment using HPE OneView for VMware vCenter Server,
complete the following steps.
b. Log in using HPE Synergy credentials from the Class Info – Seat XX document located on the desktop of
c. From the HPE OneView main menu, navigate to SERVERS, and select Server Hardware.
d. Select the first server allocated to your group, and verify that the server is powered off.
e. If the server is powered on, from the Actions menu, select Power off.
f. When prompted, select the Press and hold option.
2. Repeat steps d to f for the second and third server. Make sure that you interact only with the servers allocated to
your group.
Rev. 21.41
Exercise 5: Deploying an ESXi system using HPE OneView for VMware vCenter
Server
In this exercise you deploy one ESXi system using HPE OneView for VMware vCenter Server.
1. To deploy an ESXi system using HPE OneView for VMware vCenter Server, complete the following steps:
prompted.
Deployment.
e. Select XX-ESXi7.0U1-Deployment as the OS build plan name, where XX should be replaced with your group
number.
f. At the bottom of the screen, click DEPLOY OS.
g. The Deploy OS window opens. From the drop-down menu next to OneView, select the only available instance.
h. From the drop-down menu next to HPE Server Hardware, select the first server assigned to your group. This
is the server that was used to run Windows in a previous lab exercise.
i. Enter P@ssw0rd as the Host Password.
j. From the drop-down menu next to Server Profile Template, select XX-ESXi-OVVC, where XX should be
k. Enter XX-ESXi-01 as the Server Profile name, where XX should be replaced with your group number.
l. Next to Network Config, click the radio button next to Static.
Rev. 21.41
m. Enter the network settings for the esxi01 system. You can find this information in the Class Info – Seat XX
document located on the desktop of your management server. Note that the screenshot below is just for your
reference; do not use the values from the screenshot for your deployment.
n. Click DEPLOY.
o. Click CONFIRM.
p. The deployment operation is triggered. Click OK to accept the message.
2. To monitor the installation process, complete the following steps:
a. Return to HPE OneView managing the HPE Synergy platform.
b. From the SERVERS section, select Server Profiles.
c. Click your server profile name that you created in step 1, and from the Actions menu, select Launch HTML5
console.
d. Monitor the process. Do not reboot the system, do not disconnect virtual media, and do not interact with the
system in any other way. The server will reboot several times. During the deployment, you may see some
warning messages that can be ignored. Wait until the installation is finished. Note that your console may time
out and you may have to reopen it. Note: If you are prompted for credentials, close the HTML5 console tab in
your browser and repeat step c.
Rev. 21.41
Exercise 6: Working with HPE OneView for VMware vCenter Server

In this exercise you create a VMware cluster and use HPE OneView for VMware vCenter Server to grow and shrink
the cluster.
1. To configure the VMware cluster and add ESXi systems, complete the following steps:
prompted.
c. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, and in the Inventories
section click Host and Clusters.
d. Right-click sXX-vcenter-a.hpe.local, where XX is replaced with your group number, and select New
Datacenter.
e. Enter Training as the datacenter name and click OK.
f. Right-click the Training datacenter and select New Cluster. Enter ClusterXX as cluster name, where XX
g. Do not enable any cluster functionalities and click NEXT. Click FINISH.
h. Right-click ClusterXX, where XX should be replaced with your group number and select Add Hosts.
i. Enter esxi01.hpe.local as the IP address or FQDN. Enter root as the username and P@ssw0rd as
the password. Click NEXT.
j. Click the checkbox next to esxi01.hpe.local and click OK when the security alert appears.
k. Click NEXT, then click FINISH.
l. Wait until the host has been added. It will be added in maintenance mode.
m. Once added, right-click the host and from Maintenance Mode, select Exit Maintenance Mode.
2. To import a cluster and enable HPE OneView for VMware vCenter Server operations, complete the following
steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, from the Inventories
section, click Host and Clusters.
b. Right-click ClusterXX, where XX should be replaced with your group number, and from HPE Server
Management Actions select Import Cluster. HPE OneView for VMware vCenter Server operations are
available only for imported clusters.
c. From the drop-down menu next to OS Deployment Plan, select XX-ESXi7.0U1-Deployment, where XX
d. In the field next to ESXi Root Password enter P@ssw0rd.
e. Next to Hostname To Register click the Enable radio button, and click IMPORT.
f. Click OK and wait until the cluster has been imported.
Rev. 21.41
3. HPE OneView for VMware vCenter Server can be used to add new nodes to the cluster. To grow the VMware
cluster, complete the following steps:
a. Right-click ClusterXX, where XX should be replaced with your group number, and from HPE Server
Management Actions select Grow Cluster.
b. Click the checkbox next to the second server assigned to your group and click NEXT.
c. On the Cluster Preferences screen click NEXT.
d. On the Custom Attributes screen click NEXT.
e. On the next screen enter the network settings for the second ESXi system. You can find this information in
the Class Info – Seat XX document located on the desktop of your management server. Enter esxi02 as
the hostname and click NEXT. Click FINISH.
f. Click OK to begin the deployment process.
g. You can monitor the deployment process as you did in the previous exercise. You should see two nodes in
your cluster.
h. Repeat steps a to g to deploy node esxi03.
4. HPE OneView for VMware vCenter Server can be used to remove nodes from the cluster. To shrink your VMware
cluster, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, in the Inventories section,
click Host and Clusters.
b. Right-click ClusterXX, where XX should be replaced with your group number, and from HPE Server
Management Actions select Shrink Cluster.
c. Click the checkbox next to esxi03.hpe.local and click SHRINK.
d. Click YES to confirm the delete process. Click OK.
e. The host will be removed from the vCenter Server, and the server profile associated with that host will be
deleted from HPE OneView. You should have esxi01 and esxi02 remaining in your cluster.
5. Once the cluster is imported for HPE OneView for VMware vCenter Server management, additional objects will be
created in HPE OneView. To check them, complete the following steps:
c. From the HPE OneView main menu, navigate to HYPERVISORS and select Hypervisor Cluster Profiles.
Verify that a profile for your cluster has been created.
d. From the HPE OneView main menu, navigate to HYPERVISORS and select Hypervisor Profiles. Verify that
profiles for the cluster nodes have been created.
Rev. 21.41
Summary
During this lab you verified proper integration of the required components (vCenter Server, HPE OneView and HPE
OneView for VMware vCenter Server), prepared an OS Deployment Plan and server profile template. You prepared
HPE Synergy compute nodes for ESXi deployment and deployed an ESXi system using HPE OneView for VMware
vCenter Server. You also used grow and shrink cluster functionalities from HPE OneView for VMware vCenter Server.
Rev. 21.41
Rev. 21.41
Working with a virtualization
workload
Lab 8
Rev. 21.41
Working with the virtualization workload Page 2
Learning objectives
• Prepare HPE Synergy compute nodes for VMWare vSAN deployment
• Deploy a vSAN witness node
• Configure a two-node vSAN cluster with a witness node
• Work with basic VMware virtualization features
Requirement
NOTE
Rev. 21.41
Exercise 1: Prepare HPE Synergy compute nodes for VMWare vSAN deployment
In this exercise you prepare two HPE Synergy compute nodes for VMWare vSAN deployment. You add additional
connections to the server profiles and create logical JBODs to provide cache and capacity tiers.
1. To modify connections in the server profile template, complete the following steps:
c. From the HPE OneView main menu, navigate to SERVERS, and select Server Profile Templates.
d. Click XX-ESXi-OVVC server profile template, where XX should be replaced with your group number, and
from the Actions menu select Edit.
e. Scroll down to the Connections section and click Add connection.
f. Enter Management-B as the connection name.
g. Select Ethernet as the function type, and from the drop-down menu next to Network, select
StudentXX-Mgmt (VLAN 32XX), where XX should be replaced with your group number. You are adding a
second connection to the management network to provide redundancy.
h. Click Add + to add another connection.
i. Enter vSAN-A as the connection name.
j. From the drop-down menu next to the Network, select StudentXX-vSAN, where XX should be replaced with
your group number.
k. Click Add + to add another connection.
l. Enter vSAN-B as the connection name.
m. From the drop-down menu next to the Network, select StudentXX-vSAN, where XX should be replaced with
your group number.
n. Click Add + to add another connection.
o. Enter FC-A as the connection name, and make sure that the Function type is set to Fibre Channel.
p. From the drop-down menu next to the Network, select FC-Net-A.
q. Click Add + to add another connection.
r. Enter FC-B as the connection name, and make sure that the Function type is set to Fibre Channel.
s. From the drop-down menu next to the Network, select FC-Net-B.
t. Click Add to finish adding new connections.
u. This returns you to the server profile template screen. Click OK to save the changes. Accept the warning that
the server profile template is being used by existing server profiles.
Rev. 21.41
2. Because you changed the server profile template, all server profiles deployed will report an inconsistency. To
make all profiles consistent (this procedure adds additional connections only), complete the following steps:
a. From the HPE OneView main menu, navigate to SERVERS, and select Server Profiles. Locate the server
profile for the second cluster node that was deployed using the grow cluster functionality (it should be named
ClusterXX-nodeY, where XX should be replaced with your group number) and from the Actions menu select
Edit.
b. In the field next to Name, replace the old name with XX-ESXi-02, where XX should be replaced with your
group number. Click OK to save the changes.
c. Click the XX-ESXi-01 server profile, where XX should be replaced with your group number, and from the
Actions menu select Power off. You have to power off the server to add new connections.
d. Click Momentary press for a graceful shutdown.
e. Using the same method power off XX-ESXi-02 server, where XX should be replaced with your group number.
f. Click the XX-ESXi-01 server profile, where XX should be replaced with your group number, and from the
Actions menu select Update from template. Click Yes, update.
g. Repeat step f for the XX-ESXi-02 server profile, where XX should be replaced with your group number, and
wait until both server profiles are consistent with the server profile template.
3. To provide storage capacity for the VMware vSAN, you must edit each profile and present drives from the D3940
storage module. To present storage capacity for the vSAN setup, complete the following steps:
a. From the SERVERS section, navigate to Server Profiles.
b. Click the XX-ESXi-01 server profile, where XX should be replaced with your group number.
c. From the Actions menu, select Edit.
d. Scroll down to the Local Storage section.
e. Click the pencil icon next to SAS Mezz 1 storage controller.
f. In the new window, select the checkbox next to Manage Mezz 1 storage controller.
g. Click Add logical JBOD.
h. At the Add Logical JBOD screen, select New Logical JBOD as the type.
i. Enter XX-CacheTier-01 as the name, where XX should be replaced with your group number.
j. Set the Number of physical drives to 1.
k. Leave Select drives by as the default (Drive type).
l. From the drop-down menu next to Drive type, select 1920 GB SAS SSD as the type.
m. Next to Erase on delete, select Yes.
n. Unselect the checkbox next to Permanent.
o. Click Add +.
p. At the Add Logical JBOD screen, select New Logical JBOD as the type.
Rev. 21.41
q. Enter XX-CapacityTier-01 as the name, where XX should be replaced with your group number.
r. Set the Number of physical drives to 1.
s. Leave Select drives by at the default (Drive type).
t. From the drop-down menu next to Drive type, select 1200 GB SAS HDD as the type.
u. Next to Erase on delete, select Yes. Unselect the checkbox next to the Permanent option.
v. Click Add, and then click OK.
w. This returns you to the server profile edit screen. Click OK to save the changes.
x. Click OK one more time to accept the changes and to create Logical JBODs for this server.
4. Repeat the same steps for the other profiles:
a. For the XX-ESXi-02 server profile, create Logical JBODs with the names: XX-CacheTier-02 and XX-
CapacityTier-02, where XX should be replaced with your group number.
b. All your servers should now have Logical JBODs assigned. Power on both servers from the Actions menu
using Power on.
Rev. 21.41
Exercise 2: Deploying a vSAN witness node

In this exercise you deploy a vSAN witness node to the ESXi system running on HPE Superdome Flex.
1. To add an ESXi system running on HPE Superdome Flex to the vCenter Server, complete the following steps:
prompted.
b. Log in using the vCenter-a credentials from the Class Info – Seat XX document located on the desktop of
c. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, from the Inventories
section click Hosts and Clusters.
d. Right-click the Training datacenter and select Add host.
e. Enter esxi00.hpe.local as the host name and click NEXT.
f. Enter root as the username and P@ssw0rd as the password. Click NEXT.
g. Click YES at the security alert.
h. Click NEXT to proceed.
i. At the licensing screen click NEXT.
j. At the lockdown mode screen click NEXT.
k. At the VM location screen click NEXT.
l. Click Finish to add the ESXi system to the vCenter Server inventory. Do not add this system to the cluster.
2. To deploy a vSAN witness node, complete the following steps:
a. In the vCenter Server right-click esxi00.hpe.local and select Deploy OVF Template.
b. Click the radio button next to Local file and click UPLOAD FILES.
c. Navigate to the ClassFiles folder located on the desktop of your management server and select
VMware-VirtualSAN-Witness-7.0U1-16850804.ova and click Open.
d. Click NEXT.
e. Enter vSAN-WitnessXX as the virtual machine name, where XX should be replaced with your group
number, and click NEXT.
f. At the select a compute resource screen, make sure that esxi00.hpe.local is selected and click NEXT.
g. At the Review details screen click NEXT.
h. At the License agreements screen, click the checkbox next to I accept all license agreements and click
NEXT.
i. At the Configuration screen retain all default values and click NEXT.
j. At the Select storage screen, click the only available datastore, and from the drop-down menu next to Select
virtual disk format, select Thin Provision. Click NEXT.
k. At the Select networks screen, retain all default values and click NEXT.
Rev. 21.41
l. At the Customize template screen enter P@ssw0rd as the password and password confirmation.
m. From the drop-down menu below Which network will be used for vSAN Traffic, select Management.
n. Populate the Management Network section using values for the Witness Node from the Class Info – Seat XX
document located on the desktop of your management server. Click NEXT.
o. Click FINISH.
p. Wait until the OVF is deployed and power on the VM.
3. A witness node is a virtual machine running nested ESXi. You can add the witness node to the vCenter inventory
like a regular ESXi system. To add the witness node to the datacenter object, complete the following steps:
b. In the vCenter Server view, right-click the Training datacenter object and select Add host. Make sure that
you do not add the witness node to the cluster itself.
c. Enter witness.hpe.local as the host name and click NEXT.
d. Enter root as the username and P@ssw0rd as the password. Click NEXT.
e. Click YES at the security alert.
f. Click NEXT to proceed.
g. At the licensing screen make sure that the embedded license is used (do not apply the evaluation license) and
click NEXT.
h. At the lockdown mode screen click NEXT.
i. At the VM location screen click NEXT.
j. Click Finish to add the ESXi system to the vCenter Server inventory.
Rev. 21.41
Exercise 3: Configuring a two-node vSAN cluster with a witness node

In this exercise, you configure a two-node vSAN cluster with a witness node. This kind of setup is especially useful for
ROBO environments. Before configuring vSAN functionality, networking must be configured for both ESXi systems
participating in the cluster.
1. To configure a redundant management network and networking for the vSAN cluster, complete the following
steps:
c. From the HPE OneView main menu, navigate to SERVERS, and select Server Profiles.
d. Click the XX-ESXi-01 server profile and from the drop-down menu next to the server profile name select
Connections. Expand the Management-B, vSAN-A and vSAN-B connections and note the physical MAC
address associated with each connection. You will use them to identify NICs in the vCenter Server. Write down
these MAC addresses in the table below, and repeat the same procedure for the XX-ESXi-02 server profile,
where in both cases, XX should be replaced with your group number.
Connection esxi01.hpe.local esxi02.hpe.local
Management-B
vSAN-A
vSAN-B
e. Return to the vCenter Server and click esxi01.hpe.local, click the Configure tab, and from the Networking
section, click Physical adapters. Using the table above, match connections with the vmnic by comparing MAC
addresses and record the vmnic identifiers below.
Connection esxi01.hpe.local esxi02.hpe.local
Management-B
vSAN-A
vSAN-B
f. From the networking section click Virtual switches, and click MANAGE PHYSICAL ADAPTERS.
g. Click the + sign and select the network adapter that you associated with the Management-B connection. Click
OK. It will add redundant connectivity for the management network.
h. Click OK one more time. Note that a second network adapter is added to the virtual switch.
i. On the same screen, click ADD NETWORKING.
j. On the first screen, make sure that the radio button next to VMkernel Network Adapter is selected and click
NEXT.
Rev. 21.41
k. On the next screen, click the radio button next to New standard switch and click NEXT.
l. Click the + sign and using CTRL select both available network adapters. Click OK to proceed.
m. Click NEXT.
n. Enter vSAN as the Network label, click the checkbox next to vSAN functionality and click NEXT.
o. On the next screen, click the radio button next to Use static IPv4 settings and populate IPv4 and subnet
mask using values using the Class Info – Seat XX document located on the desktop of your management
server.
p. Click FINISH on the last screen.
q. Repeat steps f to p for esxi02.hpe.local.
2. To configure a vSAN cluster based on two nodes, complete the following steps:
prompted.
d. Click ClusterXX, where XX should be replaced with your group number, then click the Configure tab.
e. In the vSAN section click Services.
f. Click CONFIGURE VSAN. If you see a request for feedback about vSAN, click CLOSE.
g. Click the radio button next to Two node vSAN cluster and click NEXT.
h. Click NEXT on the Services screen.
i. From the drop-down menu next to Flash drives select Cache tier. For HDD drives select Capacity tier.
j. Click NEXT.
k. Expand sXX-vcenter-a.hpe.local inventory, where XX should be replaced with your group number, and click
witness.hpe.local. Click NEXT.
l. Click the radio button next to the 10GB drive in the cache tier section, click the radio button next to the
350GB drive in the capacity tier section. Click NEXT to proceed.
m. Click FINISH on the last screen. Wait until vSAN has been configured.
n. Click the Summary tab and if there is a warning that vSAN health alarms are suppressed, click Reset to
Green.
o. Click the vSphere Client banner and on the Shortcuts screen, from the Inventories section, click Storage and
verify that the vSAN Datastore is present.
Rev. 21.41
Exercise 4: Working with VMware virtualization

In this exercise you configure various virtual components, including networking, storage and advanced technologies
like vMotion. You also use Storage vMotion and deploy some virtual machines.
1. To deploy a VM from an OVF template, complete the following steps:
prompted.
b. Log in using the vCenter-a credentials from the Class Info – Seat XX document located on the desktop of
c. Click the vSphere Client banner, and from the Inventories section of the Shortcuts screen in the vCenter
Server, click Hosts and Clusters.
d. Right-click ClusterXX, where XX should be replaced with your group number and select Deploy OVF
Template.
e. Click the radio button next to Local file and click UPLOAD FILES. Navigate to the ClassFiles folder located on
the desktop of your management server and select CentOS8.ova and click NEXT.
f. Change the name to CentOS8 and click NEXT.
g. Expand the available cluster and click esxi01.hpe.local. Click NEXT.
h. Click NEXT.
i. Click datastore1 on the storage screen and click NEXT.
j. Click NEXT on the networking screen, keeping default settings.
k. Click FINISH.
l. Repeat steps d to k to import Windows2016_Template.ova with Windows2016 as the VM name.
m. Power on both VMs.
2. A shared datastore is required for advanced technologies like vMotion, HA cluster and load-balancing cluster. To
configure a shared datastore, complete the following steps:
c. From the HPE OneView main menu, navigate to SERVERS, and select Server Profiles.
d. Click the XX-ESXi-01 server profile, where XX should be replaced with your group number, and from the
Actions menu select Edit.
e. Scroll down to the SAN Storage section and click the checkbox next to Manage SAN Storage.
f. From the drop-down menu next to Host OS type select VMware (ESXi) and click Add volume.
g. From the drop-down menu next to Attach Volume select XX-SSD-Vol, where XX should be replaced with
your group number, and click Add.
h. Click OK to save changes to the server profile.
Rev. 21.41
i. Repeat steps d to h for XX-ESXi-02 server profile, where XX should be replaced with your group number.
j. Return to the vCenter Server and log in, if necessary. Click esxi01.hpe.local.
k. Click the Configure tab, and from the Storage section select Storage Adapters. Click any FC adapter, then
click Rescan adapter.
l. Click the Devices tab and verify that you see a 100GiB 3PAR volume.
m. Repeat steps j to l for esxi02.hpe.local.
n. Right-click your cluster and from the Storage menu, select New Datastore. Make sure that VMFS is selected
and click NEXT.
o. Enter Shared-DS as the datastore name and from the drop-down menu next to Select a host, select
esxi01.hpe.local.
p. Click the radio button next to the 100GiB drive and click NEXT.
q. At the VMFS version screen, click NEXT.
r. At the Partition configuration screen, click NEXT. Click FINISH to create the datastore.
s. Click esxi01.hpe.local then the Datastores tab and verify that Shared-DS is visible.
t. Repeat step s for esxi02.hpe.local.
3. To move a virtual machine to the shared datastore you can use Storage vMotion. This enables you to move a
powered-on virtual machine’s files to a different datastore. To migrate a VM, complete the following steps:
a. Right-click the Windows2016 virtual machine and select Migrate.
b. Click the radio button next to Change storage only and click NEXT.
c. Click Shared-DS and click NEXT. Click FINISH to start Storage vMotion.
d. Wait until the VM has been migrated. Click the Windows2016 VM again and click the Datastores tab, verify
that it is located on the Shared-DS.
4. To move a virtual machine between ESXi systems you can use vMotion. Before vMotion can be used, it must be
enabled. To configure vMotion, complete the following steps:
a. Click esxi01.hpe.local and click the Configure tab.
b. From the Networking section click VMkernel adapters. Click the three dots next to vmk0 and select Edit…
Rev. 21.41
c. Click the checkbox next to vMotion and click OK.
d. Repeat steps a to c for esxi02.hpe.local.

e. vMotion will work only for the virtual machines located on the shared datastore. Click the Windows2016
virtual machine and click the Summary tab. Note the host on which the virtual machine is running.
f. Click esxi02.hpe.local and click the Configure tab.
g. From the networking section, click Virtual switches. If the VM Network is not present, complete steps h to l.
Otherwise, continue with step m.
h. Click ADD NETWORKING
i. Click Virtual Machine Port Group for a Standard Switch. It will allow you to add new port group for VMs.
Click NEXT.
j. On the next screen click NEXT.
k. Keep VM Network as the Network label and click NEXT.
l. On the last screen click FINISH.
m. Right-click this virtual machine and select Migrate. Select Change compute resource only and click NEXT.
n. Select the opposite host to the one the VM is running on and click NEXT.
o. Click NEXT on the networking screen.
p. Leave the default settings at the priority screen and click NEXT.
q. Click FINISH to start the migration. After the migration is finished, click the Summary tab and verify that the
virtual machine is running on esxi02.hpe.local.
Rev. 21.41
5. To effectively deploy virtual machines, VM templates can be used. To create a VM template and deploy virtual
machines from it, complete the following steps:
a. Right-click the CentOS8 virtual machine and from the Clone section, select Clone to Template.
b. Enter CentOS8-Template as the VM template name and click NEXT.
c. Expand your cluster, click esxi01.hpe.local and click NEXT.
d. Click Shared-DS on the datastore selection and click NEXT.
e. Click FINISH to create the VM template.
f. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, from the Inventories
section click VMs and Templates. Verify that the CentOS8-Template is created.
g. To deploy a new VM from this template, right-click the template and select New VM from This Template.
h. Enter CentOS8-Clone as the VM name and click NEXT.
i. Expand your cluster, click esxi01.hpe.local then click NEXT.
j. Click Shared-DS on the datastore selection and click NEXT.
k. At the clone option screen, click NEXT. In a production environment you have to customize the guest
operating system, otherwise, you will have two or more virtual machines with the same hostname and other
settings.
l. Click FINISH to deploy a VM from the template.
6. To test the vSAN datastore, you migrate a virtual machine to the vSAN datastore. To migrate a VM, complete the
following steps:
a. Right-click the CentOS8-Clone virtual machine and select the Migrate option.
b. Click the radio button next to Change storage only and click NEXT.
c. Click vsanDatastore and click NEXT. Click FINISH to start storage vMotion.
d. Wait until the VM has been migrated. Click that VM again and click the Datastores tab and verify that it is
located on the vsanDatastore.
Rev. 21.41
Summary
During this lab you prepared HPE Synergy compute nodes for vSAN deployment, deployed a vSAN witness node,
configured a two-node vSAN cluster with a witness node, and worked with basic VMware virtualization features like
vMotion, Storage vMotion or templates, datastores and clones.
Rev. 21.41
Working with HPE Storage
Integration Pack for VMware
vCenter
Lab 9
Rev. 21.41
Working with HPE Storage Integration Pack for VMware vCenter Page 2
Learning objectives
• Configure HPE Storage Integration Pack for VMware vCenter
• Create VMFS and vVols datastores
• Explore other functionalities of HPE Storage Integration Pack for VMware vCenter
Requirement
NOTE
Rev. 21.41
Exercise 1: Configure HPE Storage Integration Pack for VMware vCenter

In this exercise, you add a storage system and vCenter Servers to HPE Storage Integration Pack for VMware vCenter.
1. To add vCenter Servers to HPE Storage Integration Pack for VMware vCenter, complete the following steps:
a. Open Google Chrome and click the HPE Storage Integration Pack for VMware vCenter bookmark. Confirm
the security exception, if prompted.
b. Log in using the SIP4VC credentials from the Class Info – Seat XX document located on the desktop of your
c. At the top of the screen, on the left-hand side, click HPE Storage Integration Pack for VMware vCenter to
expand the main menu.
d. From the MANAGERS section, click vCenters.
e. Click + Add vCenter.
f. Enter sXX-vcenter-a.hpe.local as the Name. Enter administrator@vsphere.local as
the username and P@ssw0rd as the password. Replace XX with your group number.
g. Click Add.
h. Click Accept on the certificate warning. Click Yes, refresh data when prompted.
i. Repeat steps c to h to add the second vCenter server: sXX-vcenter-b.hpe.local. Replace XX with your group
number.
2. To add storage systems to HPE Storage Integration Pack for VMware vCenter, complete the following steps:
a. At the top of the screen, on the left-hand side, click HPE Storage Integration Pack for VMware vCenter to
b. From the INFRASTRUCTURE section select Storage Systems.
c. Click + Add storage system.
d. Select Primera / 3PAR StoreServ as the array type.
e. Enter the FQDN of the first array next to IP / Host name. You can find it the Class Info – Seat XX document
located on the desktop of your management server. Replace XX with your group number.
f. Enter studentXX as the username, where XX should be replaced with your group number.
g. Enter P@ssw0rd as the password.
h. Click Connect. When prompted with a certificate message, click Accept.
i. All CPGs available on the storage box will be displayed. Click the switch below Permission for each storage
pool and make sure they are all are set to Allow provisioning.
j. Click Add then click Yes, refresh data.
Rev. 21.41
Exercise 2: Configuring vVols and VMFS datastores using HPE Storage Integration
Pack for VMware vCenter
In this exercise you configure vVols using HPE Storage Integration Pack for VMware vCenter.
1. Before configuring vVols or a VMFS datastore, you have to modify advanced parameters for all ESXi systems. To
configure these advanced settings, complete the following steps:
a. Open Google Chrome and click the vCenter-a bookmark. Confirm the security exception, if prompted.
c. Click the vSphere Client banner, and on the Shortcuts screen in the vCenter Server click Hosts and Clusters.
d. Expand your cluster and select esxi01.hpe.local. Click the Configure tab.
e. From the System section click Advanced System Settings.
f. Click EDIT located in the right-top corner of the screen.
g. In the search field enter Qfull. You should see two parameters: Disk.QFullSampleSize and
Disk.QFullThreshold. Click the value field next to Disk.QFullSampleSize and enter 32. Click OK.
h. Click EDIT located in the right-top corner of the screen one more time.
i. In the search field enter enableblock. You should see one parameter: VMFS3.EnableBlockDelete.
j. Click the value field next to VMFS3.EnableBlockDelete and enter 1. Click OK.
k. Repeat steps d to j for the second member of the cluster.
2. To prepare the configuration for HPE Storage Integration Pack for VMware vCenter, complete the following
steps:
c. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server click HPE Storage. If you
don’t see this plugin, log out from the vCenter and log back in.
d. Click the Settings tab and click OneView credentials.
e. Click the green + sign and enter the HPE OneView host name and credentials (use the HPE OneView
credentials that you used to manage the HPE Synergy platform).
f. Click Test to validate the credentials. Click OK after a successful test.
g. Click Save to add these credentials.
h. Click the Storage tab, then click Details.
i. Check if Storage systems’s VASA status is enabled (it should be enabled)
j. Check if there is a certificate listed in the VASA Storage Certificates section (the certificate should be
present).
Rev. 21.41
k. Click Register next to vCenter storage provider status.

l. Click Register one more time.
m. Click OK. The vCenter storage provider status should change to Registered, Online.
3. Before creating a VMFS or vVol datastore, you have to verify that all components are properly configured. To
check the configuration, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen, in the vCenter Server, click HPE Storage.
b. From the top menu select Config checker.
c. Click the icon next to Last Checked to start a configuration test. Click OK to start the process. Wait until the
process is completed (you may need to refresh the interface to see the results). Verify that all tests are
completed successfully.
4. To create a vVol datastore, complete the following steps:

a. Navigate to the Hosts and Clusters view and right-click ClusterXX cluster, where XX should be replaced with
your group number.
b. From the All HPE Storage Actions menu select Create VVOL Datastore.
c. On the first wizard screen, make sure that your cluster is selected, and click NEXT.
d. Click the radio button next to New Storage Container.
Rev. 21.41
e. Enter XX-StorageContainer as the Storage Container Name, where XX should be replaced with your
group number.
f. Select the only available array and click NEXT.
g. Enter XX-vVol-Datastore as the datastore name, where XX should be replaced with your group
number. Click NEXT.
h. Click FINISH on the last screen.
i. Click OK and observe the process in the Recent Tasks section. This process should not take longer than 30
seconds.
j. Navigate to the Storage view and verify that the new vVol datastore is present and accessible.
5. To test the vVol datastore, complete the following steps:
a. Click the vSphere Client banner and from the Inventories section of the Shortcuts screen, in the vCenter
Server, click Hosts and Clusters.
b. Expand the inventory and right-click the Windows2016 virtual machine, then select Migrate.
c. Select the radio button next to Change storage only and click NEXT.
d. Select XX-vVol-Datastore, where XX should be replaced with your group number and click NEXT. Click
FINISH to start Storage vMotion.
e. Wait until the VM has been migrated. Click the Windows2016 VM again and select the Datastores tab, verify
that it is located on the XX-vVol-Datastore, where XX should be replaced with your group number.
f. Open Google Chrome and click the Primera & 3PAR SSMC bookmark. Confirm the security exception, if
prompted.
g. Log in using the SSMC credentials from the Class Info – Seat XX document located on the desktop of your
Rev. 21.41
h. Click the Primera & 3PAR SSMC banner to open the main menu. At the right side of the main menu, click
show all. The main menu expands and presents additional configuration options. Click Storage Containers.
Click XX-StorageContainer, where XX should be replaced with your group number, and verify its status.
6. HPE Storage Integration Pack for VMware vCenter can be used to create a VMFS datastore. Datastores will be
automatically presented to all ESXi systems within a cluster. To create a VMFS datastore, complete the following
steps:
a. In the vCenter server, navigate to the Hosts and Clusters view and right-click the ClusterXX cluster, where
XX should be replaced with your group number.
b. From the All HPE Storage Actions menu, click Create VMFS Datastore.
c. Make sure that your cluster is selected and click NEXT.
d. Enter 120 as the datastore capacity and XX-SSD-CPG as the storage pool, where XX should be replaced with
your group number. Click NEXT.
e. Enter XX-VMFS-Datastore as the datastore name, where XX should be replaced with your group
number. Click NEXT.
f. Click FINISH to create the datastore. Click OK to observe the task results.
g. Navigate to the Storage view and verify that the new VMFS datastore is present and accessible.
h. You can use SSMC to verify that the volume has been created and exported to your ESXi systems.
Rev. 21.41
Exercise 3: Explore other functionalities of HPE Storage Integration Pack for

VMware vCenter
In this exercise you explore other functionalities of HPE Storage Integration Pack for VMware vCenter such as
creating a VM from a template, scheduling VMFS datastore snapshots and scheduling VM snapshots.
1. Before you deploy multiple VMs from a template using HPE Storage Integration Pack for VMware vCenter you
must first make sure that the template is available. To refresh HPE Storage Integration Pack for VMware vCenter
information, complete the following steps:
a. Open Google Chrome and click the HPE Storage Integration Pack for VMware vCenter bookmark. Confirm
the security exception, if prompted.
b. Log in using SIP4VC credentials from the Class Info – Seat XX document located on the desktop of your
c. At the top of the screen, on the left-hand side, click HPE Storage Integration Pack for VMware vCenter to
d. From the Managers section, click vCenters.
e. Click the first vCenter Server and from the Actions menu select Refresh.
f. Click the second vCenter Server and from the Actions menu select Refresh.
2. To deploy multiple VMs from a template using HPE Storage Integration Pack for VMware vCenter, complete the
following steps:
a. In the vCenter server, navigate to the Hosts and Clusters view and right-click the ClusterXX cluster, where
XX should be replaced with your group number.
b. From the All HPE Storage Actions menu select Create VM from Template.
c. Click NEXT on the first screen.
d. Enter 5 as the number of virtual machines to be created, select the CentOS8-Template and click NEXT.
e. Select the XX-SSD-CPG storage pool, where XX should be replaced with your group number. Click NEXT.
f. Enter XX-VM as the virtual machine name, where XX should be replaced with your group number. The
system will automatically add a # to the virtual machine names to make them unique.
g. Enter XX-SIP-DS as the datastore name, where XX should be replaced with your group number and click
NEXT.
h. Click FINISH. Click OK and observe the deployment process. You should see a new datastore created and 5
virtual machines deployed. Verify that these components have been created by navigating to the Storage and
VMs, and Templates views.
Rev. 21.41
3. To schedule VMFS datastore snapshots, complete the following steps:

a. Navigate to the Hosts and Clusters view and right-click the ClusterXX cluster, where XX should be replaced
with your group number.
b. From the All HPE Storage Actions menu select Schedule VMFS Datastore Snapshot.
c. Click the checkbox next to XX-SIP-DS, where XX should be replaced with your group number. Click NEXT.
d. Enter XX-Schedule as the Job Name (Prefix), where XX should be replaced with your group number.
e. From the drop-down menu next to Frequency, select Hourly.
f. In the field next to Execution on, enter 1. In the field next to Retention Days, enter 1.
g. Click the calendar icon next to End Time and select next day. Enter the end time of your choice and click
ADD SCHEDULE.
h. Click NEXT, FINISH and OK.
i. Continue with the remaining lab exercises and after one hour, return to the SSMC and verify that the
snapshot has been created.
4. To schedule snapshots for multiple VMs, complete the following steps:
a. Navigate to the Hosts and Clusters view and right-click the ClusterXX cluster, where XX should be replaced
with your group number.
b. From the All HPE Storage Actions menu select Schedule VM Snapshot.
c. Click the checkbox next to all of the virtual machines you created in step 2. They have XXY-VM name, XX
should be replaced with your group number and Y will have values from 1 to 5. Click NEXT.
d. Enter XX-VM-Schedule as the Job Name (Prefix), where XX should be replaced with your group number.
e. From the drop-down menu next to Frequency, select Hourly.
f. In the field next to Execution on, enter 1.
g. Click the calendar icon next to End Time and select next day. Enter the end time of your choice and click
ADD SCHEDULE.
h. Click NEXT, FINISH and OK.
i. Continue with the remaining lab exercises and after one hour, return to the snapshot manager for one of the
selected VMs and verify that the snapshot has been created.
5. If time permits, explore the other options of HPE Storage Integration Pack for VMware vCenter Server. To explore
additional options, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server click HPE Storage.
b. Navigate around the available options, and verify that the components you created such as datastores, vVols
and VMs are visible.
Rev. 21.41
Summary
During this lab you configured HPE Storage Integration Pack for VMware vCenter Server and used it to create VMFS
and vVol datastores. You used it also to deploy multiple VMs using a template, to schedule VMFS datastore
snapshots, and to schedule VM snapshots.
Rev. 21.41
Working with VMware vSphere
Lifecycle Manager
Lab 10
Rev. 21.41
Working with VMware Lifecycle Manager Page 2
Learning objectives
• Update ESXi systems using a baseline
• Create a cluster and switch to image-based management
Requirement
NOTE
Rev. 21.41
Exercise 1: Updating ESXi systems using a baseline

In this exercise, you import an updated ESXi image and use it to update an individual host. Before you do this,
you will disable vSAN cluster, and delete an existing cluster.
1. To disable vSAN cluster, complete the following steps:
c. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, click Storage.
d. Click vsanDatastore and click the VMs tab. If there are any virtual machines, migrate them using Storage
vMotion to the Shared-DS. During the migration, from the drop-down menu next to VM Storage Policy select
Datastore Default.
e. Click the vSphere Client banner, and on the Shortcuts screen in the vCenter Server, select Hosts and
Clusters.
f. Click your cluster and select the Configure tab.
g. In the menu on the left of the navigation section, within the vSAN section click Services.
h. Click the TURN OFF VSAN button located on the upper-right part of the screen.
i. Click TURN OFF to confirm the process. Wait until vSAN is disabled. You may need to refresh the screen to
confirm that vSAN is turned off.
2. To delete an existing cluster, complete the following steps:
a. From the Hosts and Clusters view, verify that all virtual machines within your cluster are powered off, and if
they are not, power them off.
b. Right-click esxi01.hpe.local and from the Maintenance Mode menu, select Enter Maintenance mode.
c. Click OK to enter maintenance mode.
d. Click OK one more time to confirm.
e. Repeat steps b to d for esxi02.hpe.local.
f. When both ESXi systems are in maintenance mode, drag and drop them into the Training datacenter.
g. Right-click your cluster and select Delete. Click YES to complete the process.
3. Before you update an ESXi system, you have to add an image to the VMware Lifecycle Manager. To add an
image, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, click Lifecycle Manager.
Make sure that you do not click HPE infrastructure Lifecycle Manager.
b. Click the Imported ISOs tab and click IMPORT ISO.
c. In the new window, click BROWSE and navigate to the ClassFiles folder located on the desktop of your
management server. You should see several ISO images. Select the VMware-ESXi-7.0.2-17867351-HPE-
702.0.0.10.7.5.14-May2021-Synergy image and click Open.
Rev. 21.41
d. Wait until image has been imported. Shortly you should see the image imported in the Imported ISOs section.
4. To update an ESXi system using an imported image, you need to create a baseline. To create a baseline and
attach it to the ESXi system, complete the following steps:
a. You should be still in the Lifecycle Manager section after the ISO image is uploaded. Select the radio button
next to the ISO image you uploaded, and click the NEW BASELINE option.
b. Enter ESXi-7.0-U2 in the field next to Name.
c. Leave Upgrade selected as Content and click NEXT.
d. You should see one ISO image (the one you imported in the previous exercise). Click NEXT on this screen.
e. Click FINISH on the last screen.
f. Click the Baselines tab and verify that the baseline you created is visible.
5. To update an ESXi system you must attach a baseline to the ESXi node and perform remediation. To attach the
baseline and remediate the host, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, click Hosts and Clusters.
b. Click esxi01.hpe.local (it should be in maintenance mode) and click the Updates tab.
c. Locate the Attached Baselines section and expand the ATTACH drop-down menu. Select Attach Baseline or
Baseline Group.
d. Click the checkbox next to ESXi-7.0-U2 and click ATTACH.
e. If there are any baselines attached, detach them by clicking the checkbox next to them, then click DETACH.
Click the checkbox next to the vCenter name and click DETACH.
f. On the same screen, locate the Host Compliance section and click CHECK COMPLIANCE. Potentially you will
see a message that compliance was never checked.
g. After several seconds you should see that this host is not compliant with the attached baseline.
h. Click PRE-CHECK REMEDIATION and verify that host does not have any issues that may prevent completion
of remediation.
i. Click DONE.
j. On the same screen locate and note the ESXi version installed on this host. It should be version 7.0.1.
k. In the Attached Baselines section click the checkbox next to ESXi-7.0-U2 baseline and click REMEDIATE.
l. Click the checkbox next to I accept the terms and license agreement and click OK.
m. On the next screen click REMEDIATE. Before doing this, you may review available options.
n. Wait until remediation is completed and verify that the ESXi version has changed to 7.0.2.
o. Repeat steps a to n for esxi02.hpe.local. You should have both ESXi systems at version 7.0.2.
Rev. 21.41
Exercise 2: Create a cluster and switch to image-based management

In this exercise you create a new cluster and manage it using an image. The image will be imported as an offline
package.
1. To import an ESXi image to the vLCM depot, complete the following steps:
a. Click the vSphere Client banner and on the Shortcuts screen in the vCenter Server, click the Lifecycle
Manager icon.
b. From the Actions menu select Import Updates.
c. Click BROWSE and navigate to the ClassFiles folder located on the desktop of your management server.
d. Click the VMware-ESXi-7.0.2-17867351-HPE-702.0.0.10.7.5.14-May2021-Synergy zip file and select
Open. Wait until the image has been imported.
e. Once the ESXi image has been imported, click VENDOR ADDONS and click the radio button next to the latest
version of HPE Synergy Server Customization. You may need to navigate to the next page using the arrows in
the bottom right corner of the VENDOR ADDONS section. Review the list of HPE components included in the
image.
2. To build a new image-based cluster, complete the following steps:
d. Right-click the Training datacenter and select New Cluster.
e. Enter Image-Cluster as the name and do not enable any cluster functionalities.
f. Click the checkbox next to Manage all hosts in the cluster with a single image.
g. Click the radio button next to Compose a new image and click NEXT.
h. On the Image screen, from the drop-down menu next to ESXi Version select 7.0 U2a - 17867351.
i. From the drop-down menu next to Vendor Addon (optional) select HPE Synergy Server Customization and
click NEXT.
j. Click FINISH.
k. Drag and drop both ESXi systems to the newly created cluster.
l. Select the newly created cluster and click the Updates tab. In the Image Compliance section, click CHECK
COMPLIANCE. Because you updated both of them in the previous exercise, both of them should be compliant
with the image.
Rev. 21.41
m. Right-click each ESXi system and from the Maintenance Mode menu select Exit Maintenance Mode. When
both systems exit maintenance mode, all warnings on the cluster level should be fixed.
3. Now deploy one more ESXi system with ESXi 7.0.1 and add it to the existing cluster. To deploy an additional
system, complete the following steps:
prompted.
Deployment.
e. Select XX-ESXi7.0U1-Deployment as the OS build plan name, where XX should be replaced with your group
number.
f. At the bottom of the screen, click DEPLOY OS.
g. The Deploy OS window opens. From the drop-down menu next to OneView, select the only available instance.
h. From the drop-down menu next to HPE Server Hardware, select the third server assigned to your group. This
is the server that used to run Windows.
i. Enter P@ssw0rd as the Host Password.
j. From the drop-down menu next to Server Profile Template, select XX-ESXi-OVVC, where XX should be
k. Enter XX-ESXi-99 as the Server Profile name, where XX should be replaced with your group number.
l. Next to Network Config, click the radio button next to Static.
m. Enter the network settings for the esxi03 system. You can find this information in the Class Info text file
located on the desktop of your management server.
n. Click DEPLOY.
o. Click CONFIRM.
p. The deployment operation is triggered. Click OK to accept the message.
4. To monitor the installation process, complete the following steps:
a. Return to HPE OneView managing HPE Synergy.
b. From the SERVERS section, select Server Profiles.
c. Click the server profile name that you created in a previous step, and from the Actions menu, select Launch
HTML5 console.
d. Monitor the process. Do not reboot the system, do not disconnect virtual media, and do not interact with the
system in any other way. The server will reboot several times. During the deployment, you may see some
Rev. 21.41
warning messages that can be ignored. Wait until the installation is finished. Note that your console may
timeout and you will have to re-open it.
5. To add the newly deployed node to the cluster, complete the following steps:
a. Right-click Image-Cluster and select Add Hosts.
b. Enter esxi03.hpe.local as the IP address or FQDN. Enter root as the username and P@ssw0rd as
the password. Click NEXT.
c. Click the checkbox next to esxi03.hpe.local and click OK on the security alert. Click Next.
d. Make sure that radio button next to Don’t import an image is selected and click NEXT.
e. Click FINISH.
f. Wait until the host is added. It will be added in maintenance mode.
g. Once added, right-click this host and from Maintenance Mode, select Exit Maintenance Mode.
NOTE
If you receive a certificate-related error when adding a host to the vCenter Server, complete the following
steps:
• Connect to ESXi using the Host Client
• Select the Manage tab
• Select Advanced Settings
• Locate the option Config.HostAgent.ssl.keyStore.allowSelfSigned
• Edit the value from false to true
• Reboot the ESXi host
• Retry adding the ESXi host to vCenter Server or the certificate renew operation
6. The last node added to the cluster is deployed with ESXi 7.0.1, while the cluster is associated with the ESXi 7.0.2
image. To check if all nodes are compliant with the image associated with the cluster, complete the following
steps:
b. Click Image-Cluster and select the Updates tab.
c. In the Image Compliance section, you should see the message: 1 of 3 hosts’ compliance status is unknown.
Click CHECK COMPLIANCE.
d. Wait until the compliance check is done. You should see that esxi03.hpe.local is not compliant with the image
cluster. Click REMEDIATE ALL.
e. Click START REMEDIATION to initiate the process.
f. Wait until the remediation process is complete. All ESXi servers should be compliant with the image
associated with the cluster
Rev. 21.41
Summary
During this lab you updated ESXi systems using a baseline, created a new cluster and configured image-based
management for this cluster.
Rev. 21.41
Working with the PowerShell
Library for HPE OneView
Lab 11
Rev. 21.41
Working with PowerShell Library for HPE OneView Page 2
Learning objectives
• Revert HPE OneView DCS to its initial state
• Configure HPE OneView DCS using PowerShell scripts
Requirement
NOTE
This lab is performed on the DCS.
Rev. 21.41
Exercise 1: Reverting HPE OneView DCS to its initial state

In this exercise you revert HPE OneView DCS to its initial state.
1. To revert DCS to its initial state with hardware discovered only, complete the following steps:
a. On the management server open Google Chrome, if necessary, and navigate to https://10.32.0.101/webjea
b. Log in using the credentials from the Class Info – Seat XX document located on the desktop of your
c. Click Synergy DCS Start-of-Class – Seat XX, where XX should be replaced with your group number, and click
Submit.
d. Wait for the message Reset succeeded.
2. Access your DCS, and verify that no components are configured.
Rev. 21.41
Exercise 2: Configuring DCS using PowerShell scripts

In this exercise you configure HPE OneView DCS using PowerShell scripting.
1. Before starting the configuration, read the customer requirements below. The customer needs you to create
PowerShell scripts to perform the following tasks:
a. Create an IP address range for the management network with the name Mgmt-Range and the following IP
address range: 10.32.X.200 – 10.32.X.220. Where X should be replaced with your group number.
b. Create an IP address range for the management network with the name Mgmt-Range and the following IP
address range: 192.168.20.200 - 192.168.20.220.
c. Create a network named Mgmt associated with the Mgmt-Range IP range, with VLAN ID 15 and purpose set
to Management.
d. Create four Fibre Channel networks with the following names: SAN-A, SAN-B, SAN-C and SAN-D. All of them
should be Fabric Attached, with the Link Stability interval set to 30 sec. Bandwidth should be set to 8000 and
maximum bandwidth to 20000.
e. Create two FCoE networks with the following names: FCoE-A and FCoE-B. FCoE-A should be configured with
VLAN 155, while FCoE-B should be configured with VLAN 156.
f. Create four Ethernet networks with the following names: Production-A (VLAN 1102), Production-B (VLAN
1103), Production-C (VLAN 1104), and Production-D (VLAN 1105). All of them should be configured for
General purpose, a typical bandwidth of 2500 and maximum of 20000.
g. Create two network sets with the following names: Production-AB (including networks Production-A and
Production-B) and Production-CD (including networks Production-C and Production-D). Bandwidth should be
configured as: typical bandwidth 2500 and maximum 20000.
h. Create a Logical Interconnect Group for Ethernet matching the existing HPE Synergy setup named LIG-ETH.
i. Create a Logical Interconnect Group for SAS connectivity named LIG-SAS.
j. Create a Logical Interconnect Group for 16Gb and 32Gb Virtual Connect FC named LIG-FC16 and LIG-FC32.
k. For LIG-ETH, create an uplink set named NS-Uplink-AB associated with the Production-AB network set and
ports: Enclosure1:Bay3:Q1.2 and Enclosure2:Bay6:Q1.2. It should be configured with Exact match
consistency. The LACP timer should be set to Short and LACP distribute uplink ports should be enabled.
l. For LIG-ETH, create an uplink set named NS-Uplink-CD associated with the Production-CD network set and
ports: Enclosure1:Bay3:Q1.3 and Enclosure2:Bay6:Q1.3. It should be configured with Exact match
consistency. The LACP timer should be set to Short and LACP distribute uplink ports should be enabled.
m. For LIG-ETH, create an uplink set named FCoE-A associated with the FCoE-A network and
Enclosure1:Bay3:Q1.1 uplink port. FEC Mode should be set to auto.
n. For LIG-ETH, create an uplink set named FCoE-B associated with the FCoE-B network and
Enclosure2:Bay6:Q1.1 uplink port. FEC Mode should be set to auto.
o. For LIG-FC32, create two uplink sets: one named Fabric-A associated with the SAN-A network and Bay2:1
uplink port. The second named Fabric-B associated with the SAN-B network and Bay5:1 uplink port.
Rev. 21.41
p. For LIG-FC16, create two uplink sets: one named Fabric-C associated with the SAN-C network and Bay1:1
uplink port. The second named Fabric-D associated with the SAN-D network and Bay4:1 uplink port.
q. Create a new Enclosure Group named Synergy-EG, matching the existing HPE Synergy setup, assuming that
iLO IP addresses are managed externally.
r. Create a Logical Enclosure named Synergy-LE using the recently created Enclosure Group.
s. Upload the SPP from the ClassFiles directory to HPE OneView.
2. Create a PowerShell script for each individual task, as it will be easier to troubleshoot them. You can use the
existing scripts located in the ClassFiles directory and the reference materials provided below to aid you.
Rev. 21.41
Reference materials
This section provides helpful materials that can be used to create the required scripts.
NOTE
HPE OneView PowerShell Library information including examples accessible at:
https://hpe-docs.gitbook.io/posh-hpeoneview/cmdlets/v6.10
The following cmdlets can be used to prepare your scripts:

• Connect-OVMgmt
• New-OVAddressPoolRange
• Get-OVAddressPoolSubnet
• New-OVNetwork
• New-OVNetworkSet
• New-OVLogicalInterconnectGroup
• New-OVUplinkSet
• Get-OVLogicalInterconnectGroup
• Set-OVUplinkSet
• New-OVUplinkSet
• Get-OVLogicalInterconnectGroup
• Get-OVNetwork
• New-OVEnclosureGroup
• Get-OVEnclosureGroup
• New-OVLogicalEnclosure
• Add-OVBaseline
• Disconnect-OVMgmt
Rev. 21.41
Summary
During this lab you created reverted DCS to its initial state and configured it using PowerShell scripts.
Rev. 21.41
Rev. 21.41

HPE Compute Solutions, Rev. 21.41 Lab Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HPE Compute Solutions, Rev. 21.41 Lab Guide

Uploaded by

Copyright:

Available Formats

HPE Compute Solutions

All other trademarks are the property of their respective owners.

HPE Compute Solutions

Lab 0: Accessing the HPE Partner Ready Lab

Lab 1: Exploring HPE Synergy and HPE Superdome Flex setup

Lab 2: Installing an operating system on HPE Superdome Flex

Lab 3: Configuring HPE Synergy

Exercise 6: Exploring logical interconnects ................................................................................................................................................................... 15

Lab 4: Managing storage for HPE compute solutions

Lab 5: Working with HPE OneView server profiles

Lab 6: Configuring iLO Federation

Lab 7: Working with HPE OneView for VMware vCenter Server

Rev. 21.41 TOC-2 Confidential – For Training Purposes Only

Lab 8: Working with a virtualization workload

Lab 10: Working with VMware vSphere Lifecycle Manager

Rev. 21.41 TOC-3 Confidential – For Training Purposes Only

This page intentionally left blank.

Rev. 21.41 TOC-4 Confidential – For Training Purposes Only

Accessing the HPE Partner Ready Lab

Exercise 1: Exploring HPE Synergy setup

c. What is the speed of ports L1 and L2? What is their purpose?

Exercise 2: Exploring HPE Superdome Flex system

This page intentionally left blank.

Exercise 1: Preparing HPE Superdome Flex for an operating system installation

f. Press ESC twice to return to the Device Manager screen.

m. Select WWN Database, and press Enter.

NOTE: The first four digits of the WWPN represent:

Exercise 2: Installing ESXi on HPE Superdome Flex

Exercise 3: Configuring ESXi and scaling up an HPE Superdome Flex nPar

This page intentionally left blank.

Exercise 1: Creating an IP pool for management network

Exercise 2: Creating networks and network sets, using HPE OneView

4. To create an Ethernet network, complete the following steps:

Exercise 3: Creating logical interconnect groups

Exercise 4: Creating an enclosure group

e. Click Create to create the enclosure group.

Exercise 5: Creating a logical enclosure

Exercise 6: Exploring logical interconnects

Exercise 7: Modifying a logical interconnect group

Exercise 8: Adding SAN managers and modifying HPE OneView networks

p. Verify that all SAN managers have been added.

Exercise 9: Adding HPE Storage components

This page intentionally left blank.

Exercise 1: Basic storage management using array management tools

2. To create a new virtual volume, complete the following steps:

Exercise 2: Importing CPGs and virtual volumes to HPE OneView

Exercise 3: Working with volume templates using HPE OneView

2. To test volume template functionality, complete the following steps:

Exercise 4: Managing volumes using HPE OneView

Exercise 5: Optimizing virtual volumes

This page intentionally left blank.

Exercise 1: Creating a server profile for an HPE Synergy compute node

c. Click Create to create the server profile.

Exercise 2: Configuring MPIO for the Windows operating system

Exercise 3: Working with data volumes and snapshot functionality

d. Enter DataVolume as the Volume label. Click Next and Finish.

Exercise 4: Working with downlink aggregation

3. To test the NIC teaming configuration, complete the following steps:

d. Click Ethernet and select Network and Sharing Center.

Exercise 1: Configuring iLO Federation

k. Scroll down and click Join Group.

This page intentionally left blank.

Exercise 1: Verify proper integration of the required components

Exercise 2: Preparing an OS Deployment Plan