HPE Compute Solutions

Learner 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

Learner guide
November 2021
Contents

Module 0: Course overview and introduction

Learning objectives ......................................................................................................................................................................................................................... 2
About this course ............................................................................................................................................................................................................................. 3
Prerequisites ............................................................................................................................................................................................................................... 3
About this certification ................................................................................................................................................................................................................. 3
Course objectives ............................................................................................................................................................................................................................. 3
HPE exam preparation sources ............................................................................................................................................................................................... 4
HPE exam preparation checklist ............................................................................................................................................................................................. 5
HPE Partner Ready Certification and Learning program ......................................................................................................................................... 6
Activity: Navigating resources for HPE partners .......................................................................................................................................................... 8
Psychological principles used in this course ................................................................................................................................................................. 10
Agenda—Day 1 .............................................................................................................................................................................................................................. 11
Agenda—Day 2 .............................................................................................................................................................................................................................. 11
Agenda—Day 3 .............................................................................................................................................................................................................................. 12
Agenda—Day 4 .............................................................................................................................................................................................................................. 12
Agenda—Day 5 .............................................................................................................................................................................................................................. 13
Learner materials .......................................................................................................................................................................................................................... 14
Summary ............................................................................................................................................................................................................................................ 15
Lab exercise...................................................................................................................................................................................................................................... 16
Prelearning check.......................................................................................................................................................................................................................... 17

Module 1: HPE compute product portfolio

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
Health Service Provider ....................................................................................................................................................................................................... 3
Workload-oriented approach .................................................................................................................................................................................................... 4
Compute workloads solutions strategy ...................................................................................................................................................................... 4

Rev. 21.41 | © Copyright 2021 Hewlett Packard Enterprise Development LP | Confidential – For Training Purposes Only
Contents

Addressing customer challenges.................................................................................................................................................................................... 5

Activity: Working with the HPE Core Compute Playbook ........................................................................................................................................ 6
Learning check................................................................................................................................................................................................................................... 8
HPE compute product portfolio .............................................................................................................................................................................................. 9
HPE Synergy infrastructure ........................................................................................................................................................................................... 10
HPE Synergy components............................................................................................................................................................................................... 10
HPE Synergy 12000 Frame front ............................................................................................................................................................................... 11
HPE Synergy 12000 rear ................................................................................................................................................................................................. 13
Synergy management subsystem ............................................................................................................................................................................... 14
Frame Link Module .............................................................................................................................................................................................................. 15
HPE Synergy Composer.................................................................................................................................................................................................... 17
Management ring.................................................................................................................................................................................................................. 19
Learning check................................................................................................................................................................................................................................ 21
HPE Synergy connectivity options ............................................................................................................................................................................. 22
Master/satellite architecture .......................................................................................................................................................................................... 22
Logical enclosure .................................................................................................................................................................................................................. 23
Growing a logical enclosure ............................................................................................................................................................................................ 24
HPE Synergy fabric configuration .............................................................................................................................................................................. 24
HPE best practices for ICM population .................................................................................................................................................................... 25
HPE Virtual Connect SE 100 Gb F32 Module...................................................................................................................................................... 26
HPE Synergy 50 Gb Interconnect Link Module .................................................................................................................................................. 28
Fibre channel connectivity options ............................................................................................................................................................................ 30
HPE Synergy Virtual Connect SE 32 Gb FC Module ........................................................................................................................................ 30
Brocade 32 Gb Fibre Channel SAN Switch Module for HPE Synergy.................................................................................................... 31
Learning check................................................................................................................................................................................................................................ 32
HPE Synergy Composable Storage ............................................................................................................................................................................ 33
In-frame storage solution................................................................................................................................................................................................. 33
HPE Primera, HPE Alletra 9000, and HPE 3PAR .............................................................................................................................................. 37
HPE MSA, HPE Nimble, and HPE Alletra 6000 .................................................................................................................................................. 40
Learning check................................................................................................................................................................................................................................ 42
HPE Synergy compute modules .................................................................................................................................................................................. 43
Synergy compute modules.............................................................................................................................................................................................. 43
SY480 Gen10 Plus compute node ............................................................................................................................................................................. 44
SY480 Gen10 and SY660 Gen10 compute nodes ........................................................................................................................................... 45
HPE Synergy Graphics Accelerator Options......................................................................................................................................................... 46
HPE Synergy solution use cases .................................................................................................................................................................................. 48

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

Contents

Activity: Validating a proposal .............................................................................................................................................................................................. 49

Learning check................................................................................................................................................................................................................................ 51
HPE ProLiant Gen10 Plus portfolio ........................................................................................................................................................................... 52
Rack and tower systems ................................................................................................................................................................................................... 52
HPE ProLiant Gen10 Plus servers with AMD CPUs ......................................................................................................................................... 54
HPE ProLiant Gen10 Plus servers with Intel® CPUs ........................................................................................................................................ 56
Workload solutions highlighted for Gen10 Plus ................................................................................................................................................. 59
Pensando Distributed Services Platform ................................................................................................................................................................ 60
ProLiant security ................................................................................................................................................................................................................... 61
Learning check................................................................................................................................................................................................................................ 62
HPE Superdome Flex.......................................................................................................................................................................................................... 63
HPE Superdome Flex Server family ........................................................................................................................................................................... 63
HPE Superdome Flex Server building blocks ....................................................................................................................................................... 64
HPE Superdome Flex chassis ........................................................................................................................................................................................ 65
HPE Superdome Flex Base IO ....................................................................................................................................................................................... 66
HPE Superdome Flex Server chassis management .......................................................................................................................................... 67
HPE Superdome Flex IO subsystem .......................................................................................................................................................................... 67
Rack Management Controller ........................................................................................................................................................................................ 68
Embedded Rack Management Controller............................................................................................................................................................... 69
HPE Superdome Flex 280 Server ............................................................................................................................................................................... 70
HPE Superdome Flex 280 overview .......................................................................................................................................................................... 71
Complementary platforms for demanding four-socket workloads.......................................................................................................... 73
HPE Superdome Flex 280 management................................................................................................................................................................. 75
Linux deployment on HPE Superdome Flex server.......................................................................................................................................... 76
Windows 2019 deployment on HPE Superdome Flex server .................................................................................................................... 77
Supported VMware vSphere versions ...................................................................................................................................................................... 79
Supported sockets configuration on HPE Superdome Flex family.......................................................................................................... 80
Supported memory configuration on HPE Superdome Flex family ........................................................................................................ 81
Learning check................................................................................................................................................................................................................................ 82
Activity: Managing HPE Superdome Flex 280 ............................................................................................................................................................ 83
Learning check................................................................................................................................................................................................................................ 85
HPE SimpliVity ....................................................................................................................................................................................................................... 86
HPE SimpliVity hyperconverged node..................................................................................................................................................................... 86
Data efficiency technologies in HPE SimpliVity ................................................................................................................................................. 87
HPE SimpliVity Data Virtualization Platform ....................................................................................................................................................... 88
HPE SimpliVity global deduplication ........................................................................................................................................................................ 89

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

Contents

Primary global deduplication: IO reduction ........................................................................................................................................................... 90

HPE SimpliVity key architecture concepts ............................................................................................................................................................ 91
HPE SimpliVity product family ..................................................................................................................................................................................... 94
Learning check................................................................................................................................................................................................................................ 97
HPE Apollo 2x00 and 4x00............................................................................................................................................................................................ 98
HPE Apollo 2000 Gen10 Plus server nodes ......................................................................................................................................................... 98
Apollo 2000 Gen10 Plus ............................................................................................................................................................................................... 100
Apollo 2000 Gen10 Plus—Flexible storage....................................................................................................................................................... 101
HPE Apollo 4200 Gen10 Plus/4510 Gen10 Server...................................................................................................................................... 102
Activity: Meeting with the customer ............................................................................................................................................................................... 104
Learning check............................................................................................................................................................................................................................. 105
Summary ......................................................................................................................................................................................................................................... 107
Lab exercises ................................................................................................................................................................................................................................ 107
Prelearning check....................................................................................................................................................................................................................... 108

Module 2: Configuring HPE Synergy solutions

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
HPE Virtual Connect for HPE Synergy technologies .................................................................................................................................................. 4
Virtual Connect technology ............................................................................................................................................................................................... 4
Virtual ID pools.......................................................................................................................................................................................................................... 5
HPE VC configurations for fault tolerance and load balancing .................................................................................................................... 6
Active-standby setup ............................................................................................................................................................................................................ 6
Active-active setup ................................................................................................................................................................................................................. 7
Multi-module link aggregation......................................................................................................................................................................................... 8
M-LAG support ......................................................................................................................................................................................................................... 9
Advanced Virtual Connect features ........................................................................................................................................................................... 10
Storm control........................................................................................................................................................................................................................... 10
Loop protection ..................................................................................................................................................................................................................... 11
Pause flood protection ...................................................................................................................................................................................................... 11
LLDP IP address mode ...................................................................................................................................................................................................... 11
LLDP tagging .......................................................................................................................................................................................................................... 12
Dynamic DNS .......................................................................................................................................................................................................................... 12
IGMP settings .......................................................................................................................................................................................................................... 13
IGMP Multicast VLAN ........................................................................................................................................................................................................ 14
IGMP proxy reporting......................................................................................................................................................................................................... 14

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

Contents

IGMP multicast flood prevention ................................................................................................................................................................................. 14

Utilization sampling ............................................................................................................................................................................................................. 15
sFlow ............................................................................................................................................................................................................................................ 16
SNMP ........................................................................................................................................................................................................................................... 18
Quality of Service (QoS) ................................................................................................................................................................................................... 19
Dot1p ........................................................................................................................................................................................................................................... 20
DSCP............................................................................................................................................................................................................................................. 20
DSCP and Dot1p ................................................................................................................................................................................................................... 20
NTP client and port flap protection ........................................................................................................................................................................... 21
Learning check................................................................................................................................................................................................................................ 23
HPE Synergy hardware setup process ............................................................................................................................................................................. 25
Hardware installation and setup.................................................................................................................................................................................. 25
HPE Synergy Composer2 ................................................................................................................................................................................................ 26
Initial HPE OneView setup using console access ............................................................................................................................................... 27
Initial HPE OneView setup using VNC access ..................................................................................................................................................... 29
Zero Touch Provisioning for HPE Composer2 .................................................................................................................................................... 30
HPE Synergy hardware setup ....................................................................................................................................................................................... 31
Activity: HPE OneView setup, configuration, and interoperability .................................................................................................................. 33
Learning check................................................................................................................................................................................................................................ 35
Configuring HPE Synergy components ........................................................................................................................................................................... 36
HPE Synergy configuration flow.................................................................................................................................................................................. 36
Creating IP address pools ................................................................................................................................................................................................ 38
Creating networks and network sets ........................................................................................................................................................................ 39
Creating networks in HPE OneView .......................................................................................................................................................................... 39
Creating Ethernet networks ........................................................................................................................................................................................... 40
Various types of Ethernet networks .......................................................................................................................................................................... 42
Creating Fibre Channel networks ................................................................................................................................................................................ 43
Creating FCoE networks ................................................................................................................................................................................................... 45
Creating RoCE networks................................................................................................................................................................................................... 46
Creating network sets ........................................................................................................................................................................................................ 48
Learning check................................................................................................................................................................................................................................ 50
Creating logical resources: Logical interconnect groups............................................................................................................................... 51
Creating logical interconnect groups ........................................................................................................................................................................ 51
LIG for a Virtual Connect SE 40 Gb F8/100 Gb F32 Module ..................................................................................................................... 52
Creating uplink sets within logical interconnect groups................................................................................................................................ 54
LIG for Synergy Virtual Connect FC modules ...................................................................................................................................................... 57

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

Contents

Creating a LIG for Synergy SAS modules ............................................................................................................................................................... 58

Learning check................................................................................................................................................................................................................................ 59
Creating logical resources: Enclosure groups ...................................................................................................................................................... 60
Creating an enclosure group .......................................................................................................................................................................................... 60
Creating logical resources: Logical enclosures .................................................................................................................................................... 62
Creating a logical enclosure............................................................................................................................................................................................ 62
Logical interconnects ......................................................................................................................................................................................................... 64
Activity: Logical interconnects .............................................................................................................................................................................................. 66
Learning check................................................................................................................................................................................................................................ 68
Automation with REST API and PowerShell scripting............................................................................................................................................. 69
HPE OneView resource model ...................................................................................................................................................................................... 69
HPE OneView REST operations ................................................................................................................................................................................... 70
Creating resources (POST) ............................................................................................................................................................................................. 70
Reading resources (GET) ................................................................................................................................................................................................. 70
Updating resources (PUT) .............................................................................................................................................................................................. 70
Updating resources (PATCH) ....................................................................................................................................................................................... 70
Deleting resources (DELETE) ....................................................................................................................................................................................... 70
HPE OneView REST API ................................................................................................................................................................................................... 71
cURL CLI utility ...................................................................................................................................................................................................................... 73
Postman ..................................................................................................................................................................................................................................... 74
HPE OneView PowerShell Library .............................................................................................................................................................................. 75
Activity: Meeting with the customer .................................................................................................................................................................................. 77
Learning check................................................................................................................................................................................................................................ 79
Summary ............................................................................................................................................................................................................................................ 82
Lab exercise...................................................................................................................................................................................................................................... 82
Prelearning check.......................................................................................................................................................................................................................... 83

Module 3: Managing storage for HPE compute solutions

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
HPE Storage concepts .................................................................................................................................................................................................................. 4
HPE Storage array positioning ........................................................................................................................................................................................ 4
OS virtualization—Logical view....................................................................................................................................................................................... 5
Chunklet concept ..................................................................................................................................................................................................................... 6
Logical disks ............................................................................................................................................................................................................................... 7
System-wide sparing ............................................................................................................................................................................................................. 7

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

Contents

RAID concepts ........................................................................................................................................................................................................................... 8

High availability enclosure (cage) vs. high availability drive (magazine)............................................................................................... 9
CPG creation ............................................................................................................................................................................................................................ 10
Virtual volume creation ..................................................................................................................................................................................................... 12
Thin provisioning overview............................................................................................................................................................................................. 14
Triple+ Parity and integrated spare .......................................................................................................................................................................... 17
HPE Nimble HF-Series Triple+ Parity....................................................................................................................................................................... 18
HPE data reduction technologies ............................................................................................................................................................................... 19
Deduplication with Express Indexing........................................................................................................................................................................ 19
Compression ............................................................................................................................................................................................................................ 20
Data packing ............................................................................................................................................................................................................................ 20
Compaction .............................................................................................................................................................................................................................. 20
Activity: HPE Alletra architecture and features .......................................................................................................................................................... 21
Learning check................................................................................................................................................................................................................................ 22
Multipathing concepts................................................................................................................................................................................................................ 23
Automatic path failover .................................................................................................................................................................................................... 24
Load balancing ....................................................................................................................................................................................................................... 25
Microsoft MPIO ...................................................................................................................................................................................................................... 26
Learning check................................................................................................................................................................................................................................ 28
Storage management options in HPE OneView ......................................................................................................................................................... 29
Storage management using HPE OneView ........................................................................................................................................................... 29
Learning check................................................................................................................................................................................................................................ 30
Storage components supported in HPE OneView ..................................................................................................................................................... 31
Supported HPE Storage components in HPE OneView................................................................................................................................. 31
Supported SAN switches .................................................................................................................................................................................................. 32
Connection methods ........................................................................................................................................................................................................... 33
Learning check................................................................................................................................................................................................................................ 34
Managing storage components using HPE OneView .............................................................................................................................................. 35
Storage management functionalities ........................................................................................................................................................................ 35
Adding supported storage components ................................................................................................................................................................. 35
Adding managed storage systems ............................................................................................................................................................................. 36
Managing storage pools for HPE Primera and HPE 3PAR .......................................................................................................................... 38
Managing storage pools for HPE Nimble ............................................................................................................................................................... 40
Configuring system ports on HPE 3PAR/Primera............................................................................................................................................. 42
Automatic port group assignment ............................................................................................................................................................................. 44
Learning check................................................................................................................................................................................................................................ 46

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

Contents

Adding SAN managers ...................................................................................................................................................................................................... 47

SAN states ................................................................................................................................................................................................................................ 50
Associating a SAN with a network.............................................................................................................................................................................. 51
Changing SAN settings ..................................................................................................................................................................................................... 52
Activity: HPE OneView storage management features .......................................................................................................................................... 54
Learning check................................................................................................................................................................................................................................ 55
Managing volumes ............................................................................................................................................................................................................... 56
Volume operations ............................................................................................................................................................................................................... 56
Volume template for HPE Primera/HPE 3PAR ................................................................................................................................................... 57
Volume template for StoreVirtual ............................................................................................................................................................................... 58
Volume template for HPE Nimble ............................................................................................................................................................................... 59
Creating a volume ................................................................................................................................................................................................................ 61
Importing a storage volume ........................................................................................................................................................................................... 62
Growing volume capacity ................................................................................................................................................................................................. 63
Creating snapshots and clones ..................................................................................................................................................................................... 64
Deleting volume attachments and volumes .......................................................................................................................................................... 66
HPE OneView shared storage ....................................................................................................................................................................................... 67
Learning check................................................................................................................................................................................................................................ 69
Managing logical JBODs ................................................................................................................................................................................................... 70
HPE OneView LJBOD—Synergy D3940................................................................................................................................................................. 70
Activity: Meeting with the customer .................................................................................................................................................................................. 72
Learning check................................................................................................................................................................................................................................ 73
Summary ............................................................................................................................................................................................................................................ 75
Lab exercise...................................................................................................................................................................................................................................... 75
Prelearning check.......................................................................................................................................................................................................................... 76

Module 4: Working with HPE OneView server profiles

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
Server profile template and server profile concepts ................................................................................................................................................... 4
Server profile .............................................................................................................................................................................................................................. 4
Server profile template ......................................................................................................................................................................................................... 6
Consistency checking in server profile templates ................................................................................................................................................ 7
Learning check................................................................................................................................................................................................................................... 9
Creating a server profile template ...................................................................................................................................................................................... 10
General and server profile section .............................................................................................................................................................................. 10

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

Contents

OS deployment and firmware section....................................................................................................................................................................... 12

Connections section ............................................................................................................................................................................................................ 15
Adding a connection ........................................................................................................................................................................................................... 17
Adding an Ethernet connection ................................................................................................................................................................................... 18
Link Aggregation Group ................................................................................................................................................................................................... 22
Downlink aggregation ........................................................................................................................................................................................................ 23
Adding a Fibre Channel connection........................................................................................................................................................................... 24
Adding an iSCSI connection............................................................................................................................................................................................ 26
Learning check................................................................................................................................................................................................................................ 27
Configuring local storage ................................................................................................................................................................................................. 28
Configuring an integrated storage controller ...................................................................................................................................................... 29
Adding a logical drive for an integrated controller........................................................................................................................................... 30
Configuring a mezzanine SAS controller ................................................................................................................................................................ 31
Adding a logical JBOD ....................................................................................................................................................................................................... 32
Adding a logical drive......................................................................................................................................................................................................... 34
SAN storage section............................................................................................................................................................................................................ 36
Creating a new volume on demand............................................................................................................................................................................ 38
Learning check................................................................................................................................................................................................................................ 39
Boot settings section .......................................................................................................................................................................................................... 40
BIOS settings section.......................................................................................................................................................................................................... 42
iLO settings section ............................................................................................................................................................................................................. 44
Advanced settings section .............................................................................................................................................................................................. 46
Activity: HPE OneView server profiles ............................................................................................................................................................................. 48
Learning check................................................................................................................................................................................................................................ 49
Managing server profiles .......................................................................................................................................................................................................... 50
Creating a server profile from a template .............................................................................................................................................................. 51
Modifying a server profile template........................................................................................................................................................................... 52
Server profile inconsistent with server profile template................................................................................................................................ 53
Fixing profile inconsistencies ......................................................................................................................................................................................... 54
Creating a server profile template from a server profile ............................................................................................................................... 56
Copying and editing a server profile ......................................................................................................................................................................... 57
Changing the server hardware type and enclosure group ........................................................................................................................... 58
Reapplying the server profile online ......................................................................................................................................................................... 59
Deleting a server profile ................................................................................................................................................................................................... 60
Activity: Managing server profiles ...................................................................................................................................................................................... 61
Learning check................................................................................................................................................................................................................................ 63

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

Contents

Managing hypervisor cluster profiles ................................................................................................................................................................................ 64

Hypervisor cluster profile management using HPE OneView.................................................................................................................... 64
Hypervisor cluster profiles .............................................................................................................................................................................................. 66
Hypervisor manager and hypervisor profiles....................................................................................................................................................... 68
Activity: Meeting with the customer .................................................................................................................................................................................. 69
Learning check................................................................................................................................................................................................................................ 70
Summary ............................................................................................................................................................................................................................................ 72
Lab exercise...................................................................................................................................................................................................................................... 72
Prelearning check.......................................................................................................................................................................................................................... 73

Module 5: Managing HPE compute products

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
HPE management approach and tools ................................................................................................................................................................................ 4
Pivot from product-centric to customer-centric.................................................................................................................................................... 4
HPE management products ....................................................................................................................................................................................................... 5
iLO 5 management processor .......................................................................................................................................................................................... 5
Information .................................................................................................................................................................................................................................. 6
System Information ................................................................................................................................................................................................................ 9
Firmware and OS software repository ...................................................................................................................................................................... 11
iLO Federation ........................................................................................................................................................................................................................ 13
Power and thermal management ................................................................................................................................................................................ 16
Performance management .............................................................................................................................................................................................. 19
Security management ........................................................................................................................................................................................................ 21
HPE OneView and Synergy frame Information................................................................................................................................................... 24
Lifecycle management with Intelligent Provisioning ....................................................................................................................................... 25
Demo: Active Health System Viewer ................................................................................................................................................................................. 27
Learning check................................................................................................................................................................................................................................ 28
HPE OneView integration with VMware and Microsoft products ............................................................................................................ 29
HPE OneView for VMware vCenter Server............................................................................................................................................................ 29
Separation of server and storage modules ............................................................................................................................................................ 31
HPE OneView requirements for managing devices ......................................................................................................................................... 32
HPE Server Hardware—Network Diagram ............................................................................................................................................................ 33
Import Cluster ......................................................................................................................................................................................................................... 34
Un-Import Cluster ................................................................................................................................................................................................................. 35
Grow Cluster ............................................................................................................................................................................................................................ 36

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

Contents

Update cluster firmware baseline ............................................................................................................................................................................... 37

Proactive HA ........................................................................................................................................................................................................................... 39
HPE Storage Integration Pack for VMware vCenter ........................................................................................................................................ 41
Storage Integration Pack for VMware vCenter features ............................................................................................................................... 42
HPE OneView integrations for Microsoft System Center ............................................................................................................................. 43
HPE OneView integrations for Microsoft ............................................................................................................................................................... 44
Learning check................................................................................................................................................................................................................................ 45
HPE OneView Global Dashboard ................................................................................................................................................................................ 46
HPE OneView for large, mixed, and distributed environments ................................................................................................................. 46
Activity: Licensing management products ..................................................................................................................................................................... 47
Learning check................................................................................................................................................................................................................................ 49
iLO Amplifier Pack and HPE InfoSight ..................................................................................................................................................................... 50
iLO Amplifier Pack description ..................................................................................................................................................................................... 50
HPE InfoSight.......................................................................................................................................................................................................................... 54
Wealth of server health and performance data .................................................................................................................................................. 55
HPE InfoSight features ...................................................................................................................................................................................................... 56
Example 1: Support for part failures ......................................................................................................................................................................... 57
Example 2: Prevention of drive failure and data loss ...................................................................................................................................... 57
Example 3: Detection of dictionary attacks........................................................................................................................................................... 58
Activity: Meeting with the customer .................................................................................................................................................................................. 59
Learning check................................................................................................................................................................................................................................ 60
Summary ............................................................................................................................................................................................................................................ 62
Lab exercise...................................................................................................................................................................................................................................... 62
Prelearning check.......................................................................................................................................................................................................................... 63

Module 6: Working with virtualization workloads

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
Foundation VMware virtualization components and technologies .................................................................................................................... 4
VMware ESXi Hypervisor .................................................................................................................................................................................................... 4
VMware vCenter Server ....................................................................................................................................................................................................... 5
VMware licensing ..................................................................................................................................................................................................................... 7
Accessing an individual ESXi server ............................................................................................................................................................................. 8
Accessing the VMware vCenter Server....................................................................................................................................................................... 9
Navigating in vCenter ........................................................................................................................................................................................................ 10
VMware datastore ................................................................................................................................................................................................................ 11

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

Contents

VMware networking ............................................................................................................................................................................................................ 13

Standard vSwitch .................................................................................................................................................................................................................. 13
vSphere distributed switch ............................................................................................................................................................................................. 14
Activity: VMware licensing....................................................................................................................................................................................................... 15
Learning check................................................................................................................................................................................................................................ 17
VMware vSAN and vVols ................................................................................................................................................................................................. 18
VMware vSAN introduction ............................................................................................................................................................................................ 18
Data access............................................................................................................................................................................................................................... 19
High availability ..................................................................................................................................................................................................................... 19
Scale-out storage .................................................................................................................................................................................................................. 19
vSAN cluster requirements ............................................................................................................................................................................................. 20
Two-node vSAN cluster with witness node .......................................................................................................................................................... 22
vSphere vVols ......................................................................................................................................................................................................................... 23
How vVols transforms storage in vSphere ............................................................................................................................................................ 25
Simplified vVols setup with HPE Storage integration Pack ........................................................................................................................ 26
Learning check................................................................................................................................................................................................................................ 27
VMware solutions certified on HPE compute resources ........................................................................................................................................ 28
VMware and HPE .................................................................................................................................................................................................................. 28
VMware Cloud Foundation 4 with Tanzu ............................................................................................................................................................... 29
vSAN ReadyNode ................................................................................................................................................................................................................. 30
Activity: Meeting with the customer .................................................................................................................................................................................. 31
Learning check................................................................................................................................................................................................................................ 32
Summary ............................................................................................................................................................................................................................................ 34
Lab exercises ................................................................................................................................................................................................................................... 34
Prelearning check.......................................................................................................................................................................................................................... 35

Module 7: Managing the solution lifecycle

Learning objectives ......................................................................................................................................................................................................................... 2
Customer scenario ........................................................................................................................................................................................................................... 3
Managing the HPE Synergy lifecycle ................................................................................................................................................................................... 4
Updating HPE OneView....................................................................................................................................................................................................... 5
HPE OneView update............................................................................................................................................................................................................ 5
HPE OneView Update Readiness Checker................................................................................................................................................................ 6
Image-based updates ............................................................................................................................................................................................................ 7
HPE OneView milestone releases .................................................................................................................................................................................. 7
HPE OneView recommended update paths ............................................................................................................................................................ 8

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

Contents

Learning check................................................................................................................................................................................................................................... 9
Activity: Using the HPE OneView Update Readiness Checker........................................................................................................................... 10
Using support and troubleshooting tools .............................................................................................................................................................. 11
Activity log................................................................................................................................................................................................................................ 11
Activity statuses .................................................................................................................................................................................................................... 12
Creating a support dump ................................................................................................................................................................................................. 13
Support dumps....................................................................................................................................................................................................................... 14
HPE OneView backup ........................................................................................................................................................................................................ 16
Scheduled remote appliance backup ........................................................................................................................................................................ 18
HPE Remote Support ......................................................................................................................................................................................................... 20
Refresh procedure ................................................................................................................................................................................................................ 23
Downloading the MAC table .......................................................................................................................................................................................... 24
HPE OneView maintenance console ......................................................................................................................................................................... 25
Learning check................................................................................................................................................................................................................................ 27
Updating HPE Synergy firmware ................................................................................................................................................................................ 28
Firmware repository ............................................................................................................................................................................................................ 28
Firmware bundle types and file formats ................................................................................................................................................................. 29
Logical enclosure firmware update ............................................................................................................................................................................ 31
Interconnect firmware update activation for logical enclosures ............................................................................................................... 32
Logical Interconnect firmware update ..................................................................................................................................................................... 33
Server firmware update .................................................................................................................................................................................................... 36
Learning check................................................................................................................................................................................................................................ 37
Migrating to HPE Composer2 ....................................................................................................................................................................................... 38
Composer compatibility and support........................................................................................................................................................................ 38
HPE Synergy migration overview ............................................................................................................................................................................... 40
Learning check................................................................................................................................................................................................................................ 42
Implementing the update process using vSphere Lifecycle Manager ........................................................................................................... 43
vSphere Lifecycle Manager............................................................................................................................................................................................. 43
HPE Infrastructure Lifecycle Manager ..................................................................................................................................................................... 44
Learning check................................................................................................................................................................................................................................ 45
Managing the firmware for HPE Superdome Flex family ...................................................................................................................................... 46
Firmware update for Superdome Flex systems .................................................................................................................................................. 46
Learning check................................................................................................................................................................................................................................ 48
HPE Pointnext Tech Care proposition.............................................................................................................................................................................. 49
HPE Pointnext Services .................................................................................................................................................................................................... 49
Changed customer focus .................................................................................................................................................................................................. 50

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

Contents

Why make changes to the Operational Services Portfolio? ......................................................................................................................... 51

What is HPE Pointnext Tech Care? ............................................................................................................................................................................ 52
A simpler portfolio................................................................................................................................................................................................................ 53
Digital experience with HPE InfoSight and DCE ................................................................................................................................................ 55
Easy access to experts....................................................................................................................................................................................................... 56
Your customers getting the most from their HPE product.......................................................................................................................... 58
HPE Pointnext Tech Care—Key points ................................................................................................................................................................... 59
Services from HPE—Portfolio positioning ............................................................................................................................................................. 60
General features .................................................................................................................................................................................................................... 61
Hardware service features .............................................................................................................................................................................................. 64
Software service features ................................................................................................................................................................................................ 68
Optional features .................................................................................................................................................................................................................. 69
HPE Datacenter Care Service ........................................................................................................................................................................................ 70
What it means for your customers ............................................................................................................................................................................. 72
Activity: Meeting with the customer .................................................................................................................................................................................. 73
Learning check................................................................................................................................................................................................................................ 74
Summary ............................................................................................................................................................................................................................................ 76
Lab exercises ................................................................................................................................................................................................................................... 76

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

Course overview and introduction
Module 0

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 2

Learning objectives
After completing this module, you should be able to:
• Describe the purpose and content of the HPE Compute Solutions class
• Explain the psychological principles used in this course
• Discuss the exam preparation checklist

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 3

About this course

The ideal candidate for this five-day course is anyone who needs to learn how to describe, position, recommend,
and demonstrate HPE compute technologies to meet a customer’s technical and business requirements.
Typical candidates are:
• Consultants
• Field Engineers
• Systems Engineers
• Solutions Integrators
Prerequisites
To get the most benefit from this course, you need prior experience with implementing IT solutions and a
working knowledge of individual HPE Composable Infrastructure components, including:
• Servers, storage, networking, IT operations, software, security, and services
• HPE OneView
• HPE Virtual Connect
It is recommended to also have an HPE ATP - Hybrid IT Solutions V2 or V1 certification.

About this certification

This course prepares you for the HPE ASE - Compute Solutions V1 certification. The recommended preparation
for the HPE0-S59 exam is the Exam Preparation Guide for HPE0-S59.
To view certification requirements, visit http://certification-learning.hpe.com/tr/index.html.

Course objectives
The purpose of the course is to teach the candidate how to:
• Plan and design server solutions
• Install, configure, and set up HPE compute solutions
• Troubleshoot HPE compute solutions
• Manage, monitor, and maintain HPE compute solutions

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 4

HPE exam preparation sources

HPE exam preparation sources

To prepare for an exam, different sources are available:

• The best option is to attend the authorized HPE training, which provides comprehensive knowledge for all
topics covered during the exam
• An exam taker’s experience can help them with passing the exam
• The official HPE Exam Preparation Guide covers exam content and provides sample items
• HPE Press study guides and books are great sources of the knowledge required for an exam

NOTES
• To access HPE Recommended Trainings, go to: https://www.mylearninghpe.com/
• To access HPE Exam Preparation Guide, go to: http://certification-learning.hpe.com/tr/certifications
• To access HPE Study Guides and books, go to: https://hpepress.hpe.com

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 5

HPE exam preparation checklist

HPE exam preparation checklist

Before taking an exam, review and acknowledge the exam preparation checklist. Note that using any
unauthorized materials for exam preparation can result in certificate revocation.

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 6

HPE Partner Ready Certification and Learning program

HPE Certification and Learning website

Success today is defined by the ability and skill to turn ideas into value faster than the competition. HPE Partner
Ready Certification and Learning can equip you and your team with the knowledge, skills, and continuous
learning needed to identify and capitalize on these new opportunities.
HPE Partner Ready Certification and Learning can open doors by providing you and your team with the most
sought-after IT skills and knowledge. You get the hands-on experience you need to start quickly. You will also
learn how to design solutions that increase your value to your customer and your employer.

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 7

HPE Partner Ready Certification and Learning gives you:

• A focus on the knowledge and skill-building activities in the leading technologies, products, and solutions that
drive customer change
• Access to training where and how you want it: self-paced web learning, traditional classroom, video on-demand,
live virtual instructor led, hands-on labs, or dedicated on-site training
• A learning curriculum of unprecedented breadth and depth that capitalizes on HPE’s long-standing, world-
leading IT solution expertise
• Personalized learning plans that allow you to customize your training according to your level of expertise and
technology areas of interest
• Respect from earning advanced HPE certifications and the technical knowledge and know-how that comes from
them
• A supportive global community of IT professionals

NOTE
For more information on certification requirements, visit the Certification and Learning site at:
http://certification-learning.hpe.com/tr/index.html.

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 8

Activity: Navigating resources for HPE partners

The purpose of this activity is to verify that you have valid credentials and to log in to the key resources available
to HPE partners.
1. Navigate to: https://certification-learning.hpe.com/tr/index.html. This is a gateway to other resources
available to HPE partners.
2. Click My Learning portal on the right-hand side of the screen, or navigate to:
https://www.mylearninghpe.com/hpcpbenefits/redirect.aspx?id=rhn-LearningCenter.

3. Log in to the portal, and answer the following questions:

a. How many certifications do you currently hold, and what are they?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

b. What is your certification level?

___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

4. Click Access The Learning Center on the right-hand side. Search for the HPE ASE – Compute Solutions V1
certification, and answer the following questions:
a. What are the requirements for achieving the HPE ASE – Compute Solutions V1 certification?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 9

b. What is the exam number that you must pass to achieve this certification? Are there any other
requirements?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

5. Navigate to https://techpro.hpe.com to access Tech Pro (log in, if necessary). What is your membership level?
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 10

Psychological principles used in this course

Psychological principles used in the design of this course include:
• Spaced repetition of key concepts—Spaced repetition has been shown to increase retention
• Interleaving of related but different topics—Introducing different (but related) topics during learning
sessions has been shown to stimulate interest and increase retention
• Retrieval practice—Learning checks (self-testing) are important features for strengthening medium- to long-
term memory
• Generative learning—The final learning check question in each module is a “Write a summary of the key
concepts presented in this module” question. This encourages learners to revisit the content that has just been
covered and to evaluate the relative importance of each topic. This has been shown to increase retention
• Desirable difficulty—Each module concludes with prelearning check questions (based on content that has not
yet been covered in class). These open-ended questions present difficulty to many of the learners and get them
thinking about potential answers (some of which may be incorrect). After teaching the content in the following
module (thus providing the answer to the prelearning check question), the question appears again as a learning
check, and the instructor should encourage the learners to compare their “before” answers to their “after” (now
that they know the correct answer). This has been shown to enhance long-term retention
Recent research has shown that learners’ attention span varies throughout lessons (learning episodes) in a fairly
predictable way. For example, for a learning episode of 40 minutes, the amount of time the learners are engaged
and learning effectively (prime time) is approximately 30 minutes. This means that they are not engaged for
around 10 minutes (down time).
Also, learning episodes have been shown to consist of two prime times—prime time 1 and prime time 2—
separated by a period of down time. So, for a 40-minute learning episode prime time 1 lasts for around 20
minutes, followed by down time of around 10 minutes, followed by prime time 2 of around 10 minutes.
It has been shown that using the prime time to teach new material and using learning checks and short activities
during down time keeps learners engaged and learning optimally. The lessons in this course have been designed
using this principle, and you will find learning check questions and short activities around 20 minutes into a 40-
minute learning episode, with more learning check questions at the end of the module. In addition, most of the
modules in this course have lab exercises where you can practice the skills you have learned.
Find out more about these principles from the books:
• Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger, and Mark A. McDaniel.
ISBN-10: 0674729013
• How the Brain Learns by David A. Sousa. ISBN-10: 1506346308

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 11

Agenda—Day 1

Agenda—Day 2

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 12

Agenda—Day 3

Agenda—Day 4

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 13

Agenda—Day 5

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 14

Learner materials

Learner and lab guides

Training participants each receive two books:

• Learner guide with embedded learning checks and activities
• Lab guide with online hands-on labs

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 15

Summary
This module described the purpose and content of the Using HPE OneView course:
• This is a 5-day instructor-led course that prepares you for the HPE ASE - Compute Solutions V1 certification
• This course uses principles outlined in the books Make It Stick: The Science of Successful Learning and How the
Brain Learns:
– Spaced repetition of key concepts
– Interleaving of related but different topics
– Generative learning
– Desirable difficulty
– Prime time and down time during learning episodes

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 16

Lab exercise
Open your lab guide, and complete Lab 0: Accessing the HPE Partner Ready lab.

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 17

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We need a solution designed
and matched with a given workload. HPE offers only general-purpose servers and solutions.”

How should you respond?

___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a statement: “We need a server solution to
support a virtualization project that needs a 16 socket-system and 24 TB of memory. HPE does not provide
such a solution.”

How should you respond?

___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________
___________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Course overview and introduction Page 18

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio
Module 1

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 2

Learning objectives
After completing this module, you should be able to:
• Describe the workload-oriented approach for HPE compute products
• Explain and recommend the HPE compute product portfolio:
– HPE Synergy, including:
– Infrastructure
– Connectivity options
– Composable storage
– Compute modules
– HPE ProLiant Gen10 Plus portfolio
– HPE Superdome Flex
– HPE SimpliVity
– HPE Apollo 2x00 and 4x00

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 3

Customer scenario

When working your way through this course, it is helpful to keep a customer in mind. You can imagine the
customer’s business and technical needs within the context of a real-world scenario, and apply what you learn as
the business grows and evolves through the course.
Consider the following fictitious customer as you work through this module. Use it as a model when trying to
integrate a solution to meet the customer’s business and technical objectives. Refer to it as you engage with
activities and labs throughout this course.
Health Service Provider
Health Service Provider (HSP) is a company that provides various medical services for healthcare businesses in
five U.S. states. HSP is growing, and they plan to expand their IT environment, but their legacy infrastructure and
compute solution does not meet their requirements. They need to understand the features and benefits of the
various HPE compute solutions before they decide which platform to use for a specific workload. HSP has asked
you for help and called a meeting to discuss the challenges they are facing and their desired business outcomes.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 4

Workload-oriented approach
Customer decision criteria can be either platform or workload centric.

Compute workloads solutions strategy

Customer decision making criteria

Customer decision making criteria can be workload or platform oriented. A platform is a software framework on
top of infrastructure to assist in the hosting of workloads in an effective and efficient manner. A workload is a
software application, or a group of software applications that operate together to deliver a defined function or set
of functions.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 5

Addressing customer challenges

HPE platform and workload-oriented solutions

HPE hybrid cloud and container platforms provide your customer with many benefits, including the ability to:
• Integrate across data sets and business groups
• Unify operations and management
• Provide stability to scale anywhere
• Reduce management complexity
Workload-oriented solutions cover areas like virtual desktop infrastructure (VDI), data management and
analytics, and transcoding/visualization, which are typically part of bigger artificial intelligence (AI) systems. HPE
applies automation and security across workloads and platforms.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 6

Activity: Working with the HPE Core Compute Playbook

HPE Core Compute playbook

Participants will work by themselves on this activity. During this activity, you will explore one of the workload
playbooks.
1. Open the Play Book - HPE Core Compute.pdf file located in your class package.
2. Answer the following questions:
a. Which Gen10 Plus platforms are well suited for VDI workloads?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 7

b. How can an HPE GreenLake and HPE Core Compute solution help customers?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

c. Which security component offers fully offloaded encryption for all data-in-motion and flow, based on
granular real-time network visibility?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

d. Why do HPE solutions target specific workloads?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 8

Learning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We need a solution designed
and matched with a given workload. HPE offers only general-purpose servers and solutions.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 9

HPE compute product portfolio

HPE offers a wide compute portfolio to support any kind and any size of workload. The portfolio includes:
• HPE Synergy:
– Infrastructure
– Connectivity options
– Composable storage
– Compute modules
• HPE ProLiant Gen10 Plus portfolio
• HPE Superdome Flex
• HPE SimpliVity
• HPE Apollo 2x00 and 4x00

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 10

HPE Synergy infrastructure

The HPE Synergy infrastructure offers simplified management and increased scalability.
HPE Synergy components

HPE Synergy components with external storage options

HPE Synergy combines hardware infrastructure, software, and services to deliver a single composable
infrastructure platform that enables customers to be well positioned for the cloud. The HPE Synergy platform
reduces operational complexity for traditional workloads and increases operational speed for emerging
applications and services. Using a single interface, HPE Synergy composes physical and virtual compute, storage,
and fabric pools into any configuration for any application. The extensible platform easily enables a broad range
of applications and operational models such as virtualization, hybrid cloud, and DevOps.
HPE Synergy is based on the following components:
• HPE Synergy frame
• HPE Composer
• Compute modules
• Composable fabric
• In-frame and external storage solutions

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 11

HPE Synergy 12000 Frame front

HPE Synergy 12000 Frame front view

The HPE Synergy 12000 Frame is the base for an HPE Synergy intelligent infrastructure with embedded
management and scalable links that can expand to meet business demand. The frame is the base infrastructure
that pools resources of compute, storage, fabric, cooling, and power. It can manage, assemble, and scale resources
on demand by using the HPE Synergy frame with an embedded management solution, combining the HPE
Synergy Composer and Frame Link Modules (FLMs). The HPE Synergy frame is designed to meet today’s needs
and future needs with continuing enhancements to compute and fabric bandwidths, including photonics-ready
capabilities.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 12

HPE Synergy components accessible from the frame front include:

1. Management appliances (up to two per frame)
2. D3940 Storage Module (up to five in a single frame, if Gen10 or later compute nodes are used)
3. Full-height server blade (up to six in a single frame)
4. Half-height server blade (up to 12 in a single frame)
5. Optional GPU expansion module
6. Synergy console connector
NOTE
The numbers in the list above correspond to the preceding graphic.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 13

HPE Synergy 12000 rear

HPE Synergy 12000 Frame rear view

HPE Synergy components accessible from the frame rear include:

1. Two interconnect modules located in slots 1 and 4, formulating fabric 1
2. Two interconnect modules located in slots 2 and 5, formulating fabric 2
3. Two interconnect modules located in slots 3 and 6, formulating fabric 3
4. 10 fans
5. 6 power supplies
6. Two FLMs (one included, the second must be purchased separately)
NOTE
The numbers in the list above correspond to the preceding graphic.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 14

Synergy management subsystem

HPE Synergy management components

Key components of the HPE Synergy management subsystem include:

• HPE Composer, running HPE OneView
• Frame Link Modules:
– HPE Synergy 4-port FLM
– HPE Synergy 2-port FLM

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 15

Frame Link Module

HPE Synergy 4-port FLM

A single FLM is the minimum required to manage a frame. For high availability (HA), or to connect multiple
frames together, each frame must have two FLMs installed. In a HA configuration, one FLM takes on the active
redundancy role, and the second takes on the standby redundancy role. The active FLM serves as the primary
manager of the frame. Both the active and the standby FLMs participate in providing connectivity for
management traffic communications.
NOTE
Both FLMs in a frame must be the same type. HPE Synergy 4-port FLMs cannot be mixed with HPE 2-port
Synergy FLMs in a frame.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 16

Frame link module MGMT port

FLM MGMT ports connect frames to the management network for remote administration. At least one MGMT
port must be connected to the management network. HPE recommends connecting a minimum of two MGMT
ports from separate frames in a management ring for HA.
When an HPE Synergy Image Streamer appliance is installed in a frame, both MGMT ports are used to connect
the HPE Synergy Image Streamer appliance to either an HPE Virtual Connect SE 100 Gb F32 Module for HPE
Synergy or an HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy for compute module boot storage
traffic. When an HPE Synergy Image Streamer is installed in a frame, the MGMT ports are automatically dedicated
to the HPE Synergy Image Streamer for OS deployment. In a management ring (frame link topology), with one or
more frames, one FLM connected to the management network is assigned the active role and the second FLM
connected to the management network is assigned the standby role. Only the active FLM connects the
management ring (frame link topology) to the management network. The status of the active FLM is monitored
by all FLMs in a management ring (frame link topology). If the active FLM MGMT link is lost, the active role is
assigned to the standby FLM.
Frame link module LINK port
The FLM LINK port provides a scalable, fault-tolerant management network backbone for connecting one or
more frames. FLM LINK ports carry all management traffic between linked frames. They also carry multiple
private virtual LANs (VLANs) for HPE Synergy Composer and HPE Synergy Image Streamer redundancy. FLM
LINK ports are connected in a management ring (frame link topology) for fault tolerance. The FLMs in a
management ring monitor the status of the ring and manage the LINK ports to provide fault tolerant connectivity
around the ring while preventing network loops.
Key functions of the HPE Synergy FLM include:
• Scaling the environment by linking Synergy frames together in a management ring
• Separation of the data and management networks
• Auto-discovery of resources by collecting asset and inventory information of components in linked frames
• Control and monitoring of the thermal and power infrastructure resources in an HPE Synergy frame
• Providing an out-of-band management interface to HPE OneView
• Reporting the health status for each component installed in a frame
• Hosting the HPE Synergy Console user interface
When designing an HPE Synergy solution, consider the following rules:
• A redundant HPE Synergy management ring requires a pair of Composers. The Composers must be the same
generation for each management ring
• The HPE Synergy Composer2 is compatible with both the 2-port FLM and the 4-port FLM
• The HPE Synergy Composer (first generation) is not compatible with the 4-port FLM within a single frame. HPE
Synergy frames that contain the Composer (first generation) require the 2-port FLM
• Options for the FLMs include the 2-port FLM and the 4-port FLM
• Each HPE Synergy frame with a management ring requires two FLMs. FLMs within the same frame must be of
the same generation
• A management ring can contain mixed FLM configurations (frames with two 2-port FLMs and frames with
two 4-port FLMs
Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 17

HPE Synergy Composer

HPE Synergy Composer2

HPE Synergy Composer provides enterprise-level management to compose and deploy system resources to meet
your customer’s application needs. The Composer management appliance uses software-defined intelligence from
embedded HPE OneView to aggregate compute, storage, and fabric resources in a manner that scales to meet
your customer’s application needs, instead of being restricted to the fixed ratios of traditional resource offerings.
This capability to quickly match resources to workloads, and then to rapidly make changes, provides your
customer with infrastructure-as-code control for integration, automation, and customization to meet their IT
needs.
HPE Synergy Composer provides native infrastructure management for efficiently matching compute, storage,
and fabric resources:
• HPE Synergy Composer2 runs HPE OneView
• HPE Synergy Composer2 management appliance delivers an updated architecture with Unified Extensible
Firmware Interface (UEFI) and HPE Integrated Lights-Out (iLO) 5
• Secure Boot in HPE Synergy Composer2 prevents tampering by validating the OS bootloader and OS kernel (as
well as kernel modules and drivers)
• Secure Start in Composer2 validates the iLO 5 firmware and UEFI BIOS, using the Silicon Root of Trust for
attack resilience
Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 18

HPE Synergy Composer2 is a second-generation management appliance that provides enhanced capabilities.
The HPE Synergy management infrastructure is designed for HA operations. Redundancy is designed into all
aspects of the management system. For example, pairs of HPE Composer appliances provide failover (active-
standby) for enterprise HA. Also, FLMs define the multiframe management ring and are redundantly
implemented for HA operations.
Monitoring, health, and maintenance
HPE Composer provides a streamlined, modern alert management architecture that simplifies monitoring. When
managed resources are added to the appliance, they are automatically discovered, inventoried, and set up for
monitoring, including the automatic registration of SNMP traps and scheduling of health data collection. For
example, HPE Synergy compute modules are monitored immediately without requiring additional configuration
or discovery steps.
All monitoring and management of data center devices is agentless and out-of-band for increased security and
reliability. No OS software is required, no open SNMP ports on the host OS are required, and zero downtime
updates can be performed.
HPE Composer also provides proactive alert notifications via email. Administrators can configure alert filters and
email identifications to match new alerts to filter criteria and then send an email to the identified contact. Your
customer can also view all of their alerts, filter their alerts, and search their alerts, using HPE Smart Search. Alerts
can be assigned to specific users and annotated with notes from administrators. Notifications or traps can be
automatically forwarded to enterprise monitoring consoles or to centralized SNMP trap collectors.
Self-diagnostic capabilities allow HPE Synergy Composer to be aware if a hardware component is misconfigured
or failing. The Synergy management infrastructure itself knows what has failed. For example, if a module is not
properly seated or a component fails, HPE Synergy acknowledges the event and notifies administrators.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 19

Management ring

HPE Synergy management ring

Even in a single-frame configuration, the best practice is to design a redundant solution with two HPE Composers
and two FLMs. Although there is a 10 GbE connection between the two FLMs across the midplane of the Synergy
12000 frame, the two modules must be cabled together using the link port to complete the management ring. In
addition to being connected to each other, the FLMs are also connected to the management network, using the
uplink port.
This redundant design maintains operational use of the HPE Synergy management network, eliminating a single
point of failure. This design also allows FLM firmware to be updated without disrupting the entire system.
Connection locations in a single-frame management ring are:
• Frame link connection location:
– FLM 1 link port to FLM 2 link port
• Management network connection locations:
– FLM 1 management port to management network
– FLM 2 management port to management network
To scale this one-frame configuration to a two-frame configuration, the existing management ring must be
disconnected. Then the FLM in the first frame must be cabled to the FLMs in the second frame, creating a
management ring across the frames. The FLMs then auto-discover all the devices within the additional frame.
As a best practice, one of the HPE Composers should be moved to the second frame. One of the uplinks should
also be moved to an FLM in the second frame. This creates a highly redundant management ring that spans the
physical architecture and creates one logical unit from which the IT staff can compose resources.
A benefit to the newly configured ring is that new frames are automatically discovered and inventoried.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 20

To move to a three-frame configuration, the cabling that connects the FLMs needs to be adjusted before adding
the additional frame. The FLMs are connected as follows:
• Frame 1 FLM 2 link port to frame 2 FLM 1 link port
• Frame 2 FLM 2 link port to frame 3 FLM 1 link port
• Frame 3 FLM 2 link port to frame 1 FLM 1 link port
The FLMs auto-discover components in the third frame, dynamically adding resources into the same pool. This
configuration is highly available because the HPE Composers are spread across the composable infrastructure
and multiple uplinks are connected to the management data center.
Whether the environment is configured with two frames per rack or three, customers can expand their
infrastructure without adding management complexity. They can simply move frame link cables to provide a
single, redundant management ring across enclosures and then manage the solution through a pair of HPE
Composers.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 21

Learning check
2. How many redundant fabrics does the HPE Synergy frame have?
A. 1
B. 2
C. 3
D. 4

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 22

HPE Synergy connectivity options

HPE Synergy offers multiple connectivity options, including HPE Virtual Connect (VC) technology.
Master/satellite architecture

Master/satellite architecture in HPE Synergy

In the HPE Synergy fabric, the master module is a low-latency device that handles all network intelligence. It
enables east/west traffic to scale without effecting the existing workload performance. The HPE Virtual Connect
SE 40 Gb F8 Module for Synergy or HPE Virtual Connect SE 100 Gb F32 Module for Synergy operates as a
master module. Two master modules are used for redundancy, and in a multiframe configuration, they should be
physically located in two different frames for maximum HA. If both master modules are located in the same frame,
this configuration is only redundant and does not provide HA. In case of whole frame failure, both master
modules are not available, which affects connectivity for compute nodes located in the other frames.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 23

The satellite modules are simply interconnect modules (ICMs) that amplify the electrical signals to help provide
the right level of signal integrity to get the signals from and to the compute modules, through the midplane of the
frame, through the satellite module, and through cables that connect the satellite modules to the master switch
module. Satellite modules help facilitate the connections of the other switch ports to compute modules in the
other frames. All traffic from the compute node connected to the satellite module is switched within the master
module. HPE Synergy 10, 20, or 25/50 Gb Interconnect Link Modules operate as satellite modules.
Satellite modules:
• Decrease the number of required components
• Streamline fabric management at an enterprise scale
• Maximize the use of network resources
• Require fewer ports at the data center aggregation layer
• Consolidate data center network connections
• Scale network bandwidth across multiple Synergy frames
After a satellite module is connected to a master module, it automatically extends the serializer/deserializer
(SerDes) functions of the respective compute modules in that satellite frame to the master module. Ultimately, all
compute modules in the satellite frame become extended ports of the master module. The satellite module uses
retimers to ensure signal integrity.
The HPE Synergy master/satellite approach used by the data network provides many benefits:
• Reduces hardware complexity and cost
• Maximizes data throughput and minimizes latency
• Simplifies management
• Efficiently scales fabrics up to five frames:
– 10 Gb/25 Gb connectivity—Five frames
– 20 Gb/50 Gb connectivity—Three frames
• Frames connected using master/satellite architecture formulate a logical enclosure
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 are applied to the physical enclosures. If the intended configuration in the logical
enclosure does not match the actual configuration on the enclosures, the logical enclosure becomes inconsistent.
A logical enclosure can be used to manage firmware, create a support dump, and apply updates made to the
logical enclosure configuration.
After Synergy frames are discovered automatically during hardware setup, your customer must manually create a
logical enclosure. The logical enclosure must contain the number of Synergy frames that are connected together
with interconnect link cables. For example, if three Synergy frames are cabled together, your customer should
create a logical enclosure that contains all three Synergy frames.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 24

Growing a logical enclosure

The HPE Synergy grow functionality enables users to increase compute capacity by adding enclosures to an HPE
Synergy logical enclosure without interrupting network traffic. The grow functionality is applicable only for
growing the VC network logical interconnect portion of a logical enclosure. Your customer can physically grow the
HPE Synergy configuration from a single frame to a maximum of five HPE Synergy frames using Interconnect
Link Modules.
In HPE OneView, the logical growth occurs by growing the logical enclosure. The HPE Synergy frames are added
to the logical enclosure by associating a new enclosure group with the logical enclosure and performing an
update from the group. HPE OneView completes the change without disassociating frames from the existing
logical enclosures or causing an outage to the existing environment.
HPE Synergy fabric configuration

HPE Synergy fabric configuration

HPE Synergy fabric innovation centers on a disaggregated rack-scale architecture that reduces complexity,
increases performance, simplifies operations, and improves availability.
HPE Synergy composable fabric offers one-step, template-based operations that allow an entire infrastructure to
be quickly and accurately configured with zero impact on availability. Standardized resource templates can be
configured, provisioned, and released as business needs demand. In fact, resource needs can be requested,
approved, and provisioned on demand. This means resource utilization is no longer a topic of budget
conversations.
The composable fabric comprises a single high port count switch that acts as the Top of Rack (ToR)—or even
multi-rack—switch (or VC module). Some uplinks from the switch module connect to an Ethernet LAN or are used
as Fibre Channel (FC)/Fibre Channel over Ethernet (FCoE) connections. The downlink ports are connected to the
compute modules.
Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 25

HPE Synergy provides three redundant fabrics. Fabric 1 utilizes interconnect modules located in slots 1 and 4,
Fabric 2 uses interconnect modules in slots 2 and 5. Finally, Fabric 3 uses interconnect modules in slots 3 and 6.
HPE best practices for ICM population

Populating interconnect modules in HPE Synergy

HPE Synergy compute modules do not have any embedded network adapters, but each of them has a specific
number of mezzanine connectors. Half-height compute modules provide three mezzanine slots, while full-height
compute modules provide six mezzanine slots.
The HPE Synergy frame supports three fabrics, utilizing (in total) six interconnect modules. The graphic above
presents the best practices for populating interconnect modules.
Serial Attached SCSI (SAS) connectivity is supported only in the first fabric. If your customer plans this kind of
connection, it can be configured only in this fabric. Ethernet connectivity should be configured with the third
mezzanine card, mapped to the third fabric.
Mezzanine two and fabric two can support any type of connectivity except SAS, but to use this mezzanine slot,
the compute modules must have a second processor installed.
NOTE
The HPE Synergy 40 Gb F8 Switch Module was retired on January 11, 2021.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 26

HPE Virtual Connect SE 100 Gb F32 Module

HPE Virtual Connect SE 100 Gb F32 module ports

The HPE Virtual Connect SE 100 Gb F32 Module for Synergy is a fundamental building block of HPE Composable
Infrastructure. Its disaggregated, rack-scale design uses a master/satellite architecture to consolidate data center
network connections, reduce hardware, and scale network bandwidth across multiple HPE Synergy frames.
This HPE VC SE 100 Gb F32 Module is the master (also known as primary) module, and the HPE Synergy 50 Gb
Interconnect Link Module is the satellite module. The master module contains intelligent networking capabilities
that extend connectivity to additional frames through satellite modules. This eliminates the need for ToR
switches and substantially reduces cost. This reduction in switching equipment also simplifies the management of
the fabric at scale, while consuming fewer ports at the data center aggregation layer.
The HPE VC SE 100 Gb F32 Module eliminates up to 95% of network sprawl at the compute module edge with
one device that converges traffic inside frames and directly connects to external LANs. Using the midplane of the
Synergy frame, each HPE VC SE 100 Gb F32 Module provides two downlink connections (or lanes) connecting up
to 12 compute modules that are housed in the 12 vertical device bays on the front side of each Synergy
frame. Each downlink can be configured as Ethernet or FCoE.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 27

A FC upgrade license needs to be purchased separately to enable the FC uplink functionality. Up to six QSFP28
ports are provided on each module for uplinks. Each port provides 100 Gbps Ethernet bandwidth. Additionally,
each of the six QSFP28 uplink ports can be configured using splitter cables as 4x25 Gbps Ethernet or 4x32 Gbps
FC for connection to upstream Ethernet and FC switches.
Since the maximum bandwidth of any QSFP28 port is 100 Gbps, when 4x32 Gbps FC connections are used, each
of the FC connections signals for 32 Gbps speed and setup, but is limited to only 25 Gbps bandwidth for that
connection. If a full 32 Gbps bandwidth is desired for any QSFP28 port, then an HPE QSFP28/SFP28 adapter
with a 32 Gbps FC transceiver is needed to populate the QSFP28 port. The HPE Virtual Connect SE 100 Gb F32
Module reduces the number of components required, compared to traditional and other converged network
solutions by eliminating the need for separate Ethernet and FC switches and cables.
Also, VC wire-once connection management is built in, enabling the tasks of adds, moves, and replacements of
compute modules in minutes instead of days or weeks. The master/satellite disaggregated architecture removes
fixed ratios of interconnects in every frame and allows for extending networking resource pools for VC to satellite
frames.
HPE Virtual Connect SE 100 Gb F32 Module provides:
• High performance, low latency:
– 6.40 Tbps switching capacity
– 300 ns for port-to-port latency
• Converged and resilient fabrics:
– Ethernet, FCoE, FC, Remote Direct Memory Access (RDMA), and Internet Small Computer System Interface
(iSCSI)
– Multi-chassis Link Aggregation (M-LAG) for resilient fabric
• Multiframe composable
• Upgrade to 32 Gb/s FC via a license on demand
• Supports 4820C and 6820C converged network adapters

4820C and 6820C converged network adapters

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 28

HPE Synergy 50 Gb Interconnect Link Module

HPE Synergy 50 Gb Interconnect Link Module

The HPE Synergy 50 Gb Interconnect Link Module, the satellite module, is designed for HPE Composable
Infrastructure. Based on disaggregated, rack-scale design, it uses a master/satellite architecture to consolidate
data center network connections, reduce hardware, and scale network bandwidth across multiple HPE Synergy
frames. This module extends HPE composable fabric up to four additional satellite frames with 25/50 Gb
connectivity to Synergy compute modules and replaces a fixed ratio of interconnects in each frame by extending
the fluid pool of network resources.
Master modules contains intelligent networking capabilities that extend connectivity to frames equipped with
satellite modules. This reduces the need for ToR switches and substantially decreases cost. The reduction in
components simplifies fabric management at scale while consuming fewer ports at the data center aggregation
layer.
Performance features of the HPE Synergy 50 Gb Interconnect Link Module include:
• 12 x 25 Gb or 12 x 50 Gb (two lanes of 25 Gb) Ethernet downlinks (traversing the midplane) to compute
module converged network adapters
• The Flex host bus adapter (HBA) can be configured to transport either FCoE/Converged Enhanced Ethernet
(CEE) or Accelerated iSCSI protocol
• Each FlexNIC and FlexHBA is recognized by the compute module as a PCIe physical function device with
adjustable speeds from 250 Mb to 25 Gb, in 250 Mb increments, when connected to a two-port converged
network adapter or any Flex-25/50 NIC from 500 Mb to 50 Gb, in 500 Mb increments, when connected to a
dual-port 25/50 Gb converged network adapter

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 29

Management features of the HPE Synergy 50 Gb Interconnect Link Module include:

• Integrated composer-based HPE OneView included with every frame, providing out-of-the-box VC
configuration and management
• Preconfigure compute modules IO configurations prior to their installation for easy deployment
• Move, add, or change compute module network connections on the fly without impacting LAN and SAN
administrator
• Provisioned storage resource associated directly to a specific virtual machine (VM)—even if the virtual server is
reallocated within a frame
• Compute module-side N-Port ID Virtualization (NPIV) removes the storage management constraint of a single
physical HBA on a compute module and does not add to SAN switch domains or require traditional SAN
management
• Licensing support for native FC through HPE Synergy Composer, powered by HPE OneView

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 30

Fibre channel connectivity options

FC connectivity options for HPE Synergy

HPE Synergy supports FC connectivity through HPE Virtual Connect modules or Brocade switches:
• HPE Virtual Connect SE 32 Gb FC Module (fully managed, using HPE OneView)
• HPE Brocade FC Switch Module for Synergy (not supported in HPE OneView)

HPE Synergy Virtual Connect SE 32 Gb FC Module

The HPE Virtual Connect SE 32 Gb FC Module for HPE Synergy is a SAN interconnect with a wire-once, change-
ready technology. The FC module, in conjunction with HPE Synergy composer powered by HPE OneView, allows
workloads to be moved or managed without modifying the network. HPE OneView provides an intuitive
management console for seamless connectivity between Synergy compute modules and 32 Gb FC SAN fabrics.
For high-performance, enterprise data center environments, the HPE Virtual Connect SE 32 Gb FC module or the
alternative, the Brocade 32 Gb FC SAN Switch Module for HPE Synergy, are the best choices for applications
demanding low-latency, high IO performance, that is, flash storage. The quad small form-factor pluggable (QSFP)
ports significantly simplify cabling infrastructure, reduce cabling from four to one, and help reduce power
attributed to optics transceivers by 2.5x.
If deployment costs are a concern, by adopting the HPE Synergy frame and Gen 6 32 Gb FC technology, your
customer can reduce costs and simplify connections to SANs, consolidate their network connections, and enable
their administrators to add, replace, and recover compute modules resources dynamically. The integrated
Synergy design frees up rack space and reduces power and cooling requirements.
The HPE Synergy Virtual Connect SE 32 Gb FC Module is protected by HPE Services 3-Year Next Business Day
9x5 Hardware Support.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 31

Brocade 32 Gb Fibre Channel SAN Switch Module for HPE Synergy

The Brocade 32 Gb Fibre Channel SAN Switch Module for HPE Synergy represents a composable and integrated
FC interconnect module with Gen6 technology that simplifies integration of the HPE Synergy chassis into a SAN.
It provides breakthrough application performance, operational stability, and simplified manageability to meet the
stringent business requirements with 32 Gb FC technology for HPE Composable Infrastructure. It is ideal for
enterprises planning to deploy 32 Gb FC to meet growing bandwidth demands of high-density
virtualization/applications, utilizing all-flash arrays (AFAs). It is also ideal for customers looking to deploy
scalable, private cloud storage networks, using HPE Synergy for workloads.
The Brocade 32 Gb FC Switch for HPE Synergy provides industry-leading performance with <900 ns frame
latency for fast switching, switching bandwidth up to 896 Gbps, and a maximum throughput of 512 Gbps to
enable demanding applications and high-density server virtualization. It provides scalability with 16 external
optical ports (two QSFP ports and eight SFP+ [enhanced small form-factor pluggable] ports), each supporting
32 Gb, 16 Gb and 8 Gb FC speeds that customers can utilize on-demand, paralleling their business growth. The
QSFP ports support a break-out cable for connection to standard SFP+ ports. It provides simplified
manageability, utilizing the advanced Web Tools to simplify fabric setup and on-going maintenance for SAN
administrators.
The Power Pack+ SAN management software option enables customers to manage data flow and maintain
optimized application performance. With the HPE PowerPack+ software, the customers can also utilize IO Insight
software for proactive and real-time monitoring of storage and application-level IO and VM Insight software to
optimize VM workloads and ensure that service-level objectives are met. The Brocade 32 Gb FC Switch Module
for HPE Synergy is nonvolatile memory express (NVMe) ready and provides next-generation storage connectivity
to the existing storage network. This helps customers transition applications and dynamically migrate to NVMe
on demand, continuing with the existing 16 Gb and 32 Gb SAN to run NVMe without code changes. The Brocade
32 Gb FC Switch Module for HPE Synergy also lowers the total cost of ownership (TCO) as it hot-plugs into the
back of the HPE Synergy frame. This frees up rack space, enables shared power and cooling, and reduces cabling,
thereby resulting in significant infrastructure savings.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 32

Learning check
3. What is the maximum number of frames in a logical enclosure with 25 Gb connectivity?
A. 1
B. 2
C. 3
D. 4
E. 5

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 33

HPE Synergy Composable Storage

The HPE Synergy platform supports in-frame storage and multiple external solutions.
In-frame storage solution

HPE D3940 Storage Module for HPE Synergy

The HPE Synergy D3940 Storage Module is a direct-attached storage module with 40 small form factor (SFF)
drive bays designed for use in HPE Synergy 12000 frames. Through the HPE Synergy 12 Gb SAS Connection
Module, it provides composable storage for up to 10 compute modules in a single frame. Synergy storage is
optimized for use as either a direct-attached storage array or as software-defined storage (SDS), using HPE
StoreVirtual Virtual Storage Appliance (VSA) or similar solutions.
HPE Synergy is a single infrastructure of physical and virtual pools of compute, storage, and fabric resources, and
a single management interface that allows IT staff to instantly assemble and reassemble resources in any
configuration. HPE Synergy eliminates hardware and operational complexity so IT staff can precisely deliver
infrastructure to applications faster and with greater flexibility.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 34

HPE Synergy in-frame storage connectivity diagram

HPE Synergy storage enables a variety of workloads by permitting multiple drive types to be configured in the
same storage module. HPE Synergy D3940 Storage Modules support a family of 12 G SAS or 6 G *SATA HDD
and SSD Smart Drives. Storage modules connect to compute modules within a frame through the Synergy 12 Gb
SAS Connection Module. Any number of drive bays in a storage module can be composed with any compute
module containing a Smart Array controller connected to the SAS fabric, allowing for efficient utilization of
available drives. Synergy storage can scale to 200 SFF drives with five storage modules in a single HPE Synergy
12000 Frame.
Adding a second IO adapter and second SAS connection module provides a redundant path to SAS drives inside
the storage module, ensuring HA. The modular design of the Synergy D3940 Storage Module allows it to slide
out from the frame to service drives or IO adapters without interrupting operation of other drives within the
module. Additionally, the HPE Synergy D3940 Storage Module is optimized for SSDs, using a high-performance
SAS connection with sixteen 12 Gb/s SAS lanes. This allows a single HPE Synergy storage module to deliver as
much as eight times the bandwidth of other JBOD (just a bunch of disks) options, reaching up to 2 million
input/output operations per second (IOPS).

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 35

The HPE Synergy D3940 Storage Module provides a large, efficient pool of storage resources that can be
allocated to meet changing server workloads and business needs. Within the frame, an administrator can create
virtual JBODs or virtual drives for any compute module, remap connections, or change personalities—all done
with stored profiles. Together, the D3940 Storage Module and the 12 Gb SAS Connection Module fully integrate
with other HPE Synergy hardware and software components and are managed and configured with HPE Synergy
Composer. The D3940 Storage Module provides leading storage density and flexibility to configure storage to
meet business needs. A modular design simplifies serviceability and can be configured with dual HPE Synergy 12
Gb SAS Flexible Storage IO Adapters for HA.
NOTE
*SATA drives (and some value SAS drives) have a single port limitation, making them more vulnerable to
failure than dual port SAS drives. HPE recommends dual port SAS drives for the HPE Synergy D3940
Storage Module. However, not all workloads require HA, so HPE continues to offer lower cost SATA drives
and value SAS drives.

HPE Synergy 12 Gb SAS Connection Module

The HPE Synergy 12 Gb SAS Connection Module connects Synergy compute modules to in-frame storage
resources. In conjunction with the Synergy D3940 Storage Module, the HPE Synergy SAS Connection Module
connects composable direct-attached storage for up to 10 compute modules in a single frame.
The HPE Synergy 12 Gb SAS Connection Module dynamically creates virtual JBODs for any compute module in
the HPE Synergy 12000 Frame, remaps connections, and is all done with stored profiles. The connection module
provides in-frame connectivity between Synergy compute modules and up to up to five storage modules. Two
connection modules can be added to each HPE Synergy 1200 Frame, providing redundant paths to the storage
modules.

Each 12 Gb SAS module provides twelve internal SAS ports, each consisting of four 12 GB/s SAS channels,
ensuring a non-blocking fabric, even when connected storage modules are fully populated with SSDs.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 36

HPE Smart Array P416ie-m SR

The HPE Smart Array P416ie-m SR Gen10 Controller, supporting 12 Gb/s SAS and PCIe 3.0, provides enterprise-
class storage performance, reliability, security, and efficiency needed to address your customer’s evolving data
storage needs while supporting advanced RAID levels with 2 GB flash-backed write cache (FBWC). This controller
operates in mixed mode, which combines RAID and HBA operations simultaneously and offers enhanced security
by encrypting data-at-rest on any drive with HPE Smart Array SR Secure Encryption.
It has eight external SAS lanes, providing connections to SAS or SATA drives in the HPE Synergy D3940, and
eight internal SAS lanes, providing connections to drives inside the HPE Synergy compute modules.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 37

HPE Primera, HPE Alletra 9000, and HPE 3PAR

HPE Primera array

HPE Primera is a Tier 0 enterprise storage solution that delivers the extreme resiliency and performance of high-
end storage with the agility of the cloud. Powered by the intelligence of HPE InfoSight, HPE Primera delivers
instant access to data with storage that sets up in minutes, upgrades transparently, and is delivered as a
service. Ensure always-fast and always-on storage for all mission-critical applications.
HPE Primera comprises three models: HPE Primera 630, HPE Primera 650, and HPE Primera 670. Each model is
available as an all-flash version (A630, A650 and A670) or converged flash version (C630, C650, C670). Future
proof and NVM Express over Fabrics (NVMeoF) ready, HPE Primera can be configured as an all-NVMe or as a
SAS/NVMe flash array.
HPE Primera comes standard with HPE Proactive Care and a 100% data availability guarantee without requiring
special contracts or onerous terms. Your customer can ensure that no disruptions are ever felt with app-aware
resiliency, guaranteed across all models of HPE Primera. If your customer experiences less than 100% availability,
HPE works with them to resolve the issue and provide financial credit to apply toward a future purchase of HPE
Primera products.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 38

HPE Alletra 9000 array

HPE Alletra 9000 is ideally suited for mission-critical workloads with extreme latency sensitivity and availability
requirements. It overcomes the agility vs. reliability tradeoff between the public cloud and traditional enterprise
storage by providing a modern, as-a-service experience through HPE GreenLake, combined with intelligence and
automation that ensures applications are always-on and available. It features a unique, massively parallel,
multinode, and all-active platform with all volumes active on all media, controllers, and host ports at all times.
Your customer can achieve unconstrained scalability for consolidating traditional and next-generation mission-
critical applications with predictable performance and ultra-low latency, backed by a 100% availability
guarantee. They can also eliminate cost and complexity from business continuity and disaster recovery with fully
active bi-directional replication.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 39

HPE 3PAR array

The HPE 3PAR StoreServ 8000 Storage family offers flexible enterprise Tier 1 storage at a midrange price. It
delivers the performance advantages of a purpose-built, flash-optimized architecture without compromising
resiliency, efficiency, or data mobility. The new HPE 3PAR Gen5 Thin Express application-specific integrated
circuit (ASIC) provides silicon-based hardware acceleration of thin technologies, including inline deduplication, to
reduce acquisition and operational costs by up to 75% without compromising performance. With unmatched
versatility, performance, and density, HPE 3PAR StoreServ 8000 Storage gives your customer a range of options
that support true convergence of block and file protocols, all-flash array performance, and the use of spinning
media to further optimize costs. It offers rich, Tier 1 data services, quad-node resiliency, seamless data mobility
between systems, HA through a complete set of persistent technologies, and simple and efficient data protection
with a flat backup to HPE StoreOnce Backup appliances. Four models are available: 8200, 8400, 8440, and 8450.
Your customer can start small and grow without painful upgrades down the road. They can enjoy the timeless
3PAR experience by starting small and seamlessly migrating to a new system or upgrading for greater scalability.
HPE 3PAR StoreServ 9000 Storage is an enterprise-class flash array that helps your customers consolidate
primary storage workloads—for file, block, and object protocols—offering flexible IO host connectivity without
compromising performance, scalability, data services, or resiliency. This newest 3PAR model, based on proven
3PAR architecture, is purpose built for all-flash consolidation, delivering the performance, simplicity, and agility
needed to support your customer’s Hybrid IT environments. HPE 3PAR StoreServ 9000 Storage is available in a
single all-flash model, the 9450, that offers rich Tier 1 data services, quad-node resiliency, fine-grained Quality of
Service (QoS), seamless data mobility between systems, HA through a complete set of persistent technologies,
and simple and efficient data protection with a flat backup to HPE StoreOnce Backup appliances.
The HPE 3PAR StoreServ 20000 Storage family offers enterprise flash arrays ready for massive consolidation of
today's most demanding workloads with greater than three million IOPS for an eight-node system, sub-
millisecond latencies, a 4X density advantage, and scalability to 24 PB of usable capacity. The family's flash-first
architecture features the HPE 3PAR Thin Express ASIC for silicon-based hardware acceleration of thin
technologies, including inline deduplication to reduce acquisition and operational costs by up to 75% without
compromising performance. With HPE Memory-Driven Flash, a new class of enterprise storage that empowers
data at the speed of memory, your customers can accelerate application response times with storage class
memory (SCM). The 3PAR StoreServ 20000 utilizes NVMe protocol to access SCM as an extended cache for
latency-sensitive applications, and the 3PAR NVMe 750 GB SCM module is very easy to install. A choice of
models provide a range of options that support true convergence of block and file protocols, offering flexible host
connectivity while providing all-flash array performance and the use of SSDs with spinning media for unmatched
versatility. Enhanced Tier 1 storage capabilities for always-on data access and fine-grained QoS controls ensure
predictable service levels for all workload types while bi-directional data mobility enables virtually limitless elastic
Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 40

pools of storage to support the most rigorous on-demand infrastructure. Four models are available: 20450,
20800, 20850, and 20840.

HPE MSA, HPE Nimble, and HPE Alletra 6000

HPE MSA array

With extreme simplicity, speed, and affordability, alongside enterprise class reliability and effortless cloud backup,
HPE MSA Gen 6 is the best choice for small to medium-sized businesses everywhere. MSA solutions are not
supported in HPE OneView.

HPE Nimble array

HPE Nimble Storage All-Flash Arrays combine a flash-efficient architecture with HPE InfoSight predictive
analytics to achieve fast, reliable access to data and 99.9999% guaranteed availability. Radically simple to deploy
and use, the arrays are cloud-ready, providing data mobility to the cloud through HPE Cloud Volumes. Your
customer’s storage investment made today will support them well into the future, thanks to HPE technology and
business-model innovations. HPE Nimble Storage All-Flash Arrays include all-inclusive licensing, easy upgrades,
and flexible payment options—while also being future-proofed for new technologies, such as NVMe and SCM.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 41

HPE Alletra 6000 array

The HPE Alletra 6000 array delivers fast, consistent performance and industry-leading data efficiency. It enables
IT departments to shift from owning and maintaining data infrastructure to simply accessing and utilizing it on-
demand, as a service via HPE GreenLake. Your customer can eliminate performance and efficiency trade-offs with
no configurations to adjust—just always-on data services. They can get resilient storage with intelligence and a
no single-point-of-failure platform that together deliver 99.9999% availability guaranteed. Your customer can
deliver on recovery service-level agreements (SLAs) with fast, integrated app-aware backup and recovery—on
premises and in the cloud.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 42

Learning check
4. Which statement HPE Synergy about in-frame storage is true?
A. SAS switches are configured through a CLI, as they are not managed using HPE OneView.
B. Mixing SAS and SATA drives in the same logical JBOD is fully supported.
C. Any number of the drives can be presented to any server from the same frame.
D. If a D3940 module is installed in a frame, this frame cannot have an FC array connected.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 43

HPE Synergy compute modules

HPE Synergy provides three compute modules with two form factors.
Synergy compute modules

HPE Synergy compute node portfolio

The three compute nodes in the HPE Synergy portfolio are:

• SY 480 Gen10 Plus—This two-socket system supports the third generation of the Intel® Xeon® Scalable Family
of processors
• SY 480 Gen10—This two-socket system supports the second generation of the Intel® Xeon® Scalable Family of
processors
• SY 660 Gen 10—This four-socket system supports the second generation of the Intel® Xeon® Scalable Family
of processors

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 44

SY480 Gen10 Plus compute node

HPE Synergy 480 Gen10 Plus compute module

The HPE Synergy 480 Gen10 Plus compute module provides the performance, scalability, density optimization,
storage simplicity, and configuration flexibility to power a variety of workloads, including business processing, IT
infrastructure, web infrastructure, and high-performance computing.
The HPE Synergy 480 Gen10 Plus compute module delivers superior capacity, efficiency, and flexibility in a two-
socket, half-height form factor to support demanding workloads.
HPE Synergy 480 Gen10 Plus compute module features include:
• Optional drive cage options for two or four drives or driveless for your customer’s SAN and vSAN workloads
• HPE NS204i-d Gen10+ Boot Controller with two M.2 480 GB drives included, designed for VMware® hardware
RAID requirements; operates with most of the drive cage options
• PCIe GPU front cage option for single GPU workloads, plus new GPU PCIe expansion modules for two, four, and
eight standard PCIe GPUs
• Intel® third generation of Intel® Xeon® Scalable family of processors
• 32 memory DIMMs for up to 16 memory DIMMs per processor, up to 4 TB max with 8 GB to 256 GB capacities
at speeds up to 3200 MT/s
• PCIe 4.0 throughout the module to provide the best performance for boot, storage, and IO

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 45

SY480 Gen10 and SY660 Gen10 compute nodes

HPE Synergy 480 Gen10 and 660 Gen10 compute modules

HPE Synergy supports both two-socket and four-socket compute modules that provide the performance,
scalability, density optimization, storage simplicity, and configuration flexibility to power a variety of workloads,
including business processing, IT infrastructure, web infrastructure, and high-performance computing.
The HPE Synergy 660 Gen10 compute module delivers agility, control, and security in a four-socket, full-height
form factor to support demanding workloads and virtualization density. Powered by two or four Intel® Xeon®
Scalable family processors, 48 slots for HPE DDR4 SmartMemory supporting up to 6 TB, flexible storage
controller options with up to four SFF drives (eight micro form factor [uFF] drives) and/or up to four internal M.2
drives, and six IO mezzanine slots. This compute module is designed to create a pool of flexible compute capacity
within a composable infrastructure. This makes the HPE Synergy 660 Gen10 compute module the ideal platform
for virtualization density, HA, and scale-up enterprise workloads.
The HPE Synergy 480 Gen10 compute module delivers superior capacity, efficiency, and flexibility in a two-
socket, half-height form factor to support demanding workloads. Powered by the latest Intel® Xeon® Scalable
processors, HPE DDR4 SmartMemory supporting up to 3 TB, flexible storage controller options, three IO
connectors, and designed to create a pool of flexible compute capacity within a composable infrastructure the
HPE Synergy 480 Gen10 compute module is the ideal platform for general-purpose enterprise workload
performance now and in the future.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 46

HPE Synergy Graphics Accelerator Options

HPE Synergy 480 Compute Module with HPE Synergy 480 Multi MXM Expansion Module

HPE Synergy 480 Graphics Accelerator Options deliver data center deployments of graphics workstations to
improve the user experience for designers and geophysicists with 3D visualization requirements or high-density
task and knowledge-worker deployments of VDI and virtualized applications, supporting over a thousand user
sessions per rack.
The Graphics Accelerator Options are paired with the HPE Synergy 480 Compute Module to provide a wide
variety of deployment options, operating environments, and remote access methods. If applications require GPU
acceleration, the Synergy platform provides the most-popular options to meet the needs of virtually any
environment.
The Graphics Accelerators are supported in three different form factors:
• Mezzanine Graphics Adapter
• Multi MXM Graphics Expansion Module
• x16 PCIe Graphics Expansion Module

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 47

Mezzanine Graphics Adapter

The GPU Mezzanine Adapter is installed in the Synergy 480 Compute Module in the Mezz1 slot. Available GPU
options include:
• NVIDIA Tesla M6 - NVIDIA Grid compatible MXM server GPU
• NVIDIA Quadro M3000SE GPU
• AMD FirePro S7100X GPU
A maximum of one GPU can be installed in the compute module.
Multi MXM Graphics Expansion Module
The Synergy 480 Multi MXM Graphics Expansion Module provides high GPU density with up to six 100-watt
MXM form factor GPUs in a single-wide, half-height module that directly attaches to the HPE Synergy 480
Compute Module via the Mezz1 slot, forming a double-wide module. GPUs can be added in the field in pairs. So, a
minimum configuration can be field upgraded to add four or six GPUs. Supported GPUs include:
• NVIDIA Tesla M6
• NVIDIA Quadro M3000SE
• AMD FirePro S7100X
The Multi MXM module has two pass-through Mezz slots (4 and 5) that allow connection of modules to the Mezz
1 and 2 slots on the compute module.
x16 PCIe Graphics Expansion Module
The Synergy 480 x16 PCIe Graphics Expansion Module supports either one or two full-length, full-height, double-
wide GPUs. Each GPU can be up to 300 watts each. Currently, the NVIDIA Quadro M5000 is supported.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 48

HPE Synergy solution use cases

HPE Synergy use cases

HPE Synergy supports a variety of workloads: general purpose virtualization, client virtualization, SDS, and many
others, as illustrated in the graphic above. HPE provides Reference Architectures based on the HPE Synergy
platform for many of these workloads.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 49

Activity: Validating a proposal

During this activity, you will analyze customer requirements, assess a potential solution proposed by a junior
architect, and recommend changes to the proposal.
HSP plans to deploy a large virtualization project on the HPE Synergy platform, and they requested a high-level
proposal. A junior architect has prepared a proposal, and your task is to validate it against the customer
requirements.
Customer requirements
The customer requirements include:
• 30 compute nodes with the maximum number of cores available to support the virtualization workload
• Redundancy within the management subsystem
• An in-frame storage solution to support vSAN
• A redundant networking subsystem with the ability to virtualize WWNs
• Access to an external FC-based array
• Simplified management with the minimum number of objects to manage
The proposal
A junior architect included the following components in the proposal:
• 3 x HPE Synergy 12000 frames
• 2 x HPE Virtual Connect SE 100 Gb F32 Modules for Synergy
• 4 x HPE Synergy 20 Gb Interconnect Link Modules
• 3 x HPE D3940 Storage Module with the maximum number of drives
• 6 x HPE Composer2
• 30 x HPE OneView Advanced licenses
• 30 x SY 660 Gen10 compute modules, each with four CPUs
Your task
Review the junior architect’s proposal, and recommend and justify any changes you wish to make.
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 50

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 51

Learning check
5. Which statement about the SY480 Gen10 Plus compute module is true?
A. It does not support connectivity to the D3940 Storage Module.
B. It supports the third generation of the Intel® Xeon® Scalable Family.
C. It does not support connectivity to a Nimble array.
D. It supports a new generation of AMD CPUs with 64 cores.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 52

HPE ProLiant Gen10 Plus portfolio

HPE released Gen10 Plus systems with the latest Intel and AMD CPUs.
Rack and tower systems

HPE ProLiant portfolio

The HPE industry standard server portfolio consists of:

• MicroServers
• 10 series servers
• 100 series servers
• 300 series servers
• 500 series servers
The HPE ProLiant ML family of servers delivers simple, efficient business value and is the ideal choice for remote
or branch offices and growing businesses. Industry-leading compute innovations include simple management and
storage tools, along with proven configurations that provide easy remote access and improved energy efficiencies
to lower your customer’s TCO. Integrated with a simplified but comprehensive management suite and industry-
leading support, the ProLiant tower portfolio delivers more business value and helps increase IT staff productivity
and expedite service delivery. In addition, the complete, right-sized tower portfolio includes financing options,
services, and a channel network to significantly increase the speed of IT operations and enable IT to respond to
business needs faster.
The HPE ProLiant tower portfolio delivers:
• Simplicity with easy-to-use tools, processes, and support to help server administrators keep hardware running
• Efficiency that office managers need to help improve employee productivity
• Affordability to increase business agility and help acquire and retain customers
The DL family of servers are the most flexible, reliable, and performance-optimized ProLiant rack servers. HPE
provides industry-leading compute innovations, the HPE ProLiant Gen10 Plus rack portfolio, with flexible choices
and versatile design, along with improved energy efficiencies, ultimately lowers your customer’s TCO.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 53

Integrated with a simplified, but comprehensive management suite and industry-leading support, the ProLiant
Gen10 and Gen10 plus rack portfolio delivers a more reliable, fast, and secure infrastructure solution; helps
increase IT staff productivity; and accelerates service delivery. In addition, the rack portfolio is performance-
optimized for multi-application workloads to significantly increase the speed of IT operations and enable IT to
respond to business needs of any size, faster.
HPE ProLiant MicroServer Gen10 Plus delivers an affordable, compact yet powerful entry-level server that your
customer can customize for on-premises, hybrid cloud, or even workloads demanding data center performance. It
is the most compact MicroServer that HPE has launched so far, and it can be placed flat or vertically, depending
on your customer’s space. The latest Intel® Xeon® E and Pentium® processors deliver compute performance as
well as security and remote management into the server with the HPE iLO Silicon Root of Trust. Along with other
enhancements, such as 4x 1 GbE onboard NICs and USB 3.2 Gen2 Type-A, whether your customer wants a
general-purpose server, a NAS, or even a virtualization server, they will be surprised at how much they can get
out of this small and affordable server.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 54

HPE ProLiant Gen10 Plus servers with AMD CPUs

HPE ProLiant Gen10 Plus, based on AMD CPUs

HPE ProLiant Gen10 Plus servers, based on AMD CPUs, are optimized for given workloads, as illustrated in the
above graphic.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 55

The HPE ProLiant DL3xx Gen10 Plus Servers are redefining price/performance with the new math for virtualized
compute. Powered by the latest AMD EPYC 7003 Series Processors, these servers offer greater processing
power, faster memory speeds up to 3200 MT/s, and increased data transfer rates with PCIe Gen4 capabilities.
HPE ProLiant DL325 Gen10 Plus v2 Server
The HPE ProLiant DL325 Gen10 Plus v2 Server is a secure and versatile single-socket server for virtualization,
IO-intensive, and storage-intensive workloads. In addition, the chassis is smaller compared to the previous
generation, providing better compatibility to your customer’s infrastructure. Tri-mode RAID controller support
provides flexibility support across SAS/SATA/NVMe types of storage options.
This 1P, 1U server delivers an exceptional balance of processor, memory, and IO for 2P performance at 1P TCO.
Your customer can get the most out of their virtualized environment with this versatile server.
HPE ProLiant DL345 Gen10 Plus Server
This 1P, 2U server has been designed with flexibility while delivering a high core count and large memory
footprint. Your customer should choose this purpose-built platform for virtualization, High Performance Compute
(HPC), and memory-centric workloads.
HPE ProLiant DL365 Gen10 Plus Server

This 2P, 1U server has been designed with flexibility while delivering a high core count and large memory
footprint. Choose this purpose-built platform for virtualization, High Performance Compute, and memory centric
workloads.
HPE ProLiant DL385 Gen10 Plus v2 Server
This 2P, 2U server has been designed with flexibility while delivering a high core count and large memory
footprint. Your customer should choose this purpose-built platform for virtualization, HPC, and memory-centric
workloads.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 56

HPE ProLiant Gen10 Plus servers with Intel® CPUs

HPE ProLiant Gen10 Plus servers based on Intel® CPUs are optimized for workloads as outlined below.
HPE ProLiant DL110 Gen10 Plus Telco Server

Telco server for Open RAN

Customized for edge applications requiring high bandwidth and low latency such as 5G cellular processing
(virtualized radio access network, or vRAN), the HPE ProLiant DL110 Gen10 Plus Telco server is based on an
open, standards-compliant infrastructure and offers dense IO capabilities with PCIe Gen4 speed, acceleration, and
powerful compute driven by third-generation Intel® Xeon® Scalable Processors.
The HPE ProLiant DL110 Gen10 Plus Server provides a reduced footprint with a compact, short depth, 1U/1P
front accessible chassis and ruggedized with NEBS Level 3 compliance for harsh environments. Delivering the
trusted HPE ProLiant experience with embedded HPE iLO management and security via the HPE Silicon Root of
Trust, the HPE ProLiant DL110 Gen10 Plus is ready for Communication Service Provider's 5G deployments.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 57

HPE ProLiant DL360 Gen10 Plus Server

Rack-optimized dense solution

Adaptable for diverse workloads and environments, the compact 1U HPE ProLiant DL360 Gen10 Plus Server
delivers enhanced performance with the correct balance of expandability and density. Designed for supreme
versatility and resiliency while backed by a comprehensive warranty, the HPE ProLiant DL360 Gen10 Plus Server
is ideal for IT infrastructure, either physical, virtual, or containerized.
The HPE ProLiant DL360 Gen10 Plus Server supports third-generation Intel® Xeon® Scalable Processors with up
to 40 cores, plus 3200 MT/s HPE DDR4 SmartMemory up to 4.0 TB per socket. With PCIe Gen4 and Intel®
Software Guard Extensions (SGX) support on the dual-socket segment, the HPE ProLiant DL360 Gen10 Plus
Server complements the ProLiant Gen10 family by delivering premium compute, memory, IO, and security
capabilities for customers focused on performance and the highest security.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 58

HPE ProLiant DL380 Gen10 Plus Server

Accelerator-optimized solution

Adaptable for diverse workloads and environments, the secure 2P, 2U HPE ProLiant DL380 Gen10 Plus Server
delivers world-class performance with the correct balance of expandability and scalability. Designed for supreme
versatility and resiliency while being backed by a comprehensive warranty make it ideal for multiple
environments from containers to cloud to Big Data.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 59

Workload solutions highlighted for Gen10 Plus

Workload/platform matching with Gen10 Plus

The above graphic presents workload and platform categories matched with refreshed Gen10 Plus systems.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 60

Pensando Distributed Services Platform

Pensando benefits

The Pensando Distributed Services Platform is architected to address the challenges for all types of workloads
(containerized, virtualized, and bare-metal) in a cloud environment. The Pensando Distributed Services Platform
includes an innovative domain-specific architecture as an intelligent accelerator on the server’s PCIe bus, allowing
full control of network forwarding and data path/pipeline programmability.
The Pensando Distributed Services Card (DSC) is based on a custom-designed, domain-specific programmable
processor, providing highly optimized hardware for packet processing, and offering a broad suite of software-
defined networking, security, telemetry, and storage services. The Pensando DSC operates at 100 Gb wire-speed
with high-performance, low-latency, low jitter, and the highest scalability targeted for the largest cloud providers.
in addition to advanced software-defined network and security services, Pensando provides data plane
programmability through the DSC, via a P4-programmable data pipeline that allows for customization of each
layer of the cloud provider’s infrastructure stack. Cloud providers can now take full control and assume full
ownership of all elements of the network and storage stack.
The Pensando Policy and Services Manager (PSM) controls all aspects of the deployed services, including
lifecycle and health monitoring of DSCs. Resources can be automatically provisioned, and new software-defined
services can be deployed from a single pane of glass. The PSM handles seamless distribution of access control
lists (ACLs) and stateful firewall policies, network configuration settings, encryption keys, and so on to active
distributed services nodes to consistently manage network performance while also ensuring policy compliance.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 61

ProLiant security

HPE ProLiant security options

The following security technologies are present in Gen10 Plus systems:

• TPM 2.0—The Trusted Platform Module (TPM) is a hardware-based system security feature that can securely
store information, such as passwords and encryption keys, which can be used to authenticate the platform.
TPMs securely store artifacts used to authenticate the platform. These artifacts can include passwords,
certificates, or encryption keys. Your customer can also use a TPM to store platform measurements to make
sure that the platform remains trustworthy. For servers configured with a TPM, it enables the firmware and
operating system to take measurements of all phases of the boot process
• Self-encrypting drive (SED)—With an SED, the encryption keys themselves never leave the confines of the
SED hardware and therefore are safe from OS-level attacks
• Device attestation—Attestation helps to determine if a system’s integrity is intact. With VMware, the
attestation process, combined with vSphere Trust Authority (vTA), prevents secure workloads from moving to
a host that failed the attestation process

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 62

Learning check
6. Which AMD-based HPE ProLiant Gen10 Plus Server is positioned as a cost-effective VDI solution?
A. HPE ProLiant DL325
B. HPE ProLiant DL345
C. HPE ProLiant DL365
D. HPE ProLiant DL385

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 63

HPE Superdome Flex

HPE Superdome Flex delivers an unmatched combination of flexibility, performance, and reliability for critical
environments of any size.
HPE Superdome Flex Server family

HPE Superdome Flex family

HPE Superdome Flex is a breakthrough server for diverse, data-intensive, and converging workloads, with a
modular, building-block architecture for cost-efficient growth. The HPE Superdome Flex family has two models:
the HPE Superdome Flex and the HPE Superdome Flex 280.
The HPE Superdome Flex Server model scales seamlessly from four to 32 sockets in four-socket increments in a
single system and delivers from 768 GB to 48 TB shared memory. It features the first- and second-generation
Intel® Xeon® Scalable Processors in both Gold and Platinum variants.
The HPE Superdome Flex 280 Server starts at two sockets and scales up to eight sockets, as a single system in
two-socket increments. The server utilizes a modular, scale-up 5U building block/chassis with two or four third-
generation Intel® Xeon® Scalable Processors in a glueless architecture. Superdome Flex 280 is designed to deliver
64 GB to 24 TB of shared memory, using dynamic random-access memory (DRAM) or combining DRAM with
Persistent Memory.
Both models in the Superdome Flex family share a modular architecture design as well as management and
security frameworks. In addition, they offer a unique set of reliability, availability, and serviceability (RAS)
capabilities—not present in other standard x86 servers—to deliver the highest levels of availability for critical
workloads. The family of servers can handle SAP HANA®, Oracle, Microsoft SQL Server, and Epic (electronic
healthcare records provider) user demand while delivering real-time analytics. Customers can comb through
massive Internet of Things (IoT) and AI datasets at the edge or in the core, and they can also tackle complex

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 64

problems holistically as a standalone HPC workhorse or within petascale clusters. With the Superdome Flex 280,
HPE can address smaller environments and with more granular scale.
HPE Superdome Flex Server building blocks

HPE Superdome Flex chassis

The HPE Superdome Flex Server consists of the following components:

• Chassis
– Base
– Partition expansion
– Expansion
• IO subsystem
• Rack Management Controller (RMC) or embedded RMC

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 65

HPE Superdome Flex chassis

HPE Superdome Flex Server chassis

A Superdome Flex Server complex contains one or more Superdome Flex Server chassis in a rack in which each
contains individual compute, memory, networking, and storage resources. An nPartition, or nPar, is created and
managed using the RMC.
There are three types of Superdome Flex Server chassis:
• Base chassis—A chassis that includes Base IO that provides drive bays, network ports, and USB ports. Each
HPE Superdome Flex Server system is required to have one base chassis. It must be placed in the lowest U
position in the rack, and it must always contain Base IO. HPE tracks warranty of the server against this chassis
• Partition expansion chassis—An add-on chassis to scale-up the capacity of a partitionable system. Each
additional nPar after the first requires at least one partitionable chassis. Each partitionable chassis adds
compute resources plus Base IO features for creating and booting an nPar. After it is installed, the partitionable
chassis may be flexibly grouped to create multiple nPars within the system without being recabled
• Expansion chassis—Adds more compute capacity, but no Base IO features. This is an add-on chassis for
scalable configuration to add more compute capacity and, as such, cannot host a new nPar. However, it can be
converted to a partitionable chassis with additional hardware and cabling

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 66

HPE Superdome Flex Base IO

HPE Superdome Flex Base IO

The IO subsystem design of the HPE Superdome Flex Server provides Base IO functionality. It also provides built-
in, hot-swappable boot drives to ease deployment and minimize costs. Of course, a customer may also choose to
boot from a SAN, as is often recommend for SAP HANA, or they may even choose network boot options via a
Preboot eXecution Environment (PXE).
HPE Superdome Flex Base IO, as illustrated in the graphic above, provides the following features to the base
chassis of the HPE Superdome Flex Server Complex:
• Built-in boot storage provided via four hot-swappable 2.5" HDDs/SSDs
• One DVD-ROM/RW drive for OS/driver installation
• Two general-purpose 10 GbE LAN ports
• Two general-purpose 1 GbE LAN ports
• Four USB 3.0 ports
• OS console serial, Video Graphics Array (VGA), and Kernel-based Virtual Machine (KVM) LAN ports
• One RMC LAN port for connection to the management LAN
• One Baseboard Management Controller (BMC) console port for initial system setup, password recovery, and
debugging
Each nPar contains one or more chassis, and the chassis in the nPar located in the lowest U-position in the rack is
called the monarch chassis for that nPar. nPars may contain up to seven expansion chassis, depending on the
customer configuration. If the system is to be divided into multiple nPars, then each nPar needs at least one base
or partitionable chassis. Configuring an nPar with two chassis for failover purposes increases overall system
availability by allowing for automatic reconfiguration and reboot in the unlikely event of a chassis deconfiguration
event.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 67

HPE Superdome Flex Server chassis management

Each HPE Superdome Flex Server chassis includes a Platform Controller Hub (PCH) chip and BMC to provide all
the features required to tie the chassis into the HPE Superdome Flex Server RMC, the HPE Superdome Flex
Server’s primary management primary component. The PCH chip provides initial reset functionality and real-time
clock functionality. The BMC provides the bulk of hard partitioning capabilities and error handling. The BMC
hardware and firmware also provide remote server management capabilities over an Ethernet management
network. The BMC of each chassis interfaces directly with the RMC to provide the processing power needed to
manage a large and flexible system like the HPE Superdome Flex Server.
HPE Superdome Flex IO subsystem

HPE Superdome Flex IO options

HPE achieves breakthrough system performance in its mission-critical server solutions by maintaining a balance
between processing power, memory capacity/performance, crossbar interconnectivity, and system IO capabilities.
Each HPE Superdome Flex Server chassis can be equipped with either a 16-slot or 12-slot IO bulkhead to provide
multiple stand-up PCIe 3.0 card options and flexibility to maintain that vitally important system balance for any
given workload. The graphic above shows the layouts for both the 16-slot and 12-slot IO bulkhead options.
The 16-slot IO bulkhead provides nine low profile x8 and seven low profile x16 PCIe 3.0 card slots. The IO
bulkhead utilizes the available 48 PCIe lanes per processor to the maximum degree possible with as much as
110 GB/s per chassis of IO bandwidth available.
The 12-slot IO bulkhead provides four full-height x8, four full-height x16, three low profile x8, and one low profile
x16 PCIe 3.0 card slots. The IO bulkhead provides sufficient extra power capacity to support ~ 300 W full-height,
double-width GPU cards for those high-demand HPC/high-performance technical computing (HPTC) workloads
or for machine learning (ML) as the ultimate neural net training engine.
With either IO bulkhead selection, the IO design provides direct connections between the processors and the card
slots without the need for bus repeaters or retimers that could add latency or reduce bandwidth. Hence, HPE
Superdome Flex customers can rest assured that they will get the best per-card performance possible.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 68

Rack Management Controller

Connecting chassis to RMC

The HPE Superdome Flex Server is managed through the HPE Superdome Flex RMC. The RMC is a 1U appliance
providing connectivity to every chassis in the system. It provides the ability to manage the partitioning of the
system and component inventory and health. While each chassis has its own BMC, HPE Superdome Flex Server’s
RMC collectively manages all chassis and the system fabric with the aid of each chassis BMC, avoiding the need to
drill down when managing individual nodes. RMC is required regardless of the number of chassis for partitionable
systems. RMC is also required for non-partitionable systems with three or more chassis.
HPE Superdome Flex Server RMC’s built-in analysis engine is constantly analyzing all hardware to detect faults,
predict failures, and initiate automatic recovery actions as well as sending notifications to administrators and HPE
Insight Remote Support and HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 69

Within the HPE Superdome Flex Server, the RMC or embedded RMC (eRMC) provides:
• Analysis engine
• Firmware manager
• Secure shell (SSH)-based CLI
• System power, boot sequencing, and control
• Environmental control and monitoring
• HPE nPar management (RMC only)
• Fault and error message information
• Alerting capability, using Redfish events and alerts, Remote Support, or SNMP
• A console for each HPE nPar (available via the web console feature or SSH)
• Virtual media and web console for each nPar
• Industry-standard Redfish interface for scripting access and tool support
Embedded Rack Management Controller

Two chassis management stacking

The RMC is a 1U appliance providing connectivity to every chassis in the system. In one- and two-chassis
configurations (four and eight sockets, respectively), the HPE Superdome Flex Server can run the end-to-end
RMC functionality on one of the BMC management processors, thereby connecting the two chassis. The
functionality is identical to a larger configuration, but the requirement for and cost of a separate 1U RMC
appliance for the system is eliminated.
The eRMC only supports a single hardware partition (HPE nPar) configured for the system. To divide an HPE
Superdome Flex enclosure into two or more nPars, or to grow to more than two chassis, your customer must use
the 1U RMC appliance. To set up eRMC, connect RMC ports together, connect one end of an Ethernet cable into
the MGMT port on the base chassis BMC, and connect the other end into the management network.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 70

HPE Superdome Flex 280 Server

HPE Superdome Flex business value

The HPE Superdome Flex 280 Server’s modular architecture scales cost-efficiently to meet future growth. With
six Intel® Ultra Path Interconnect (UPI) links per processor, it provides higher bandwidth and faster data rates
than prior generations. Designed to support 64 GB to 24 TB of shared memory, it is an ideal choice for in-memory
data analytics. Customers can choose between high-performance all-DRAM systems or a combination of DRAM
and Persistent Memory with Intel® Optane™ Persistent Memory 200 series, depending on workload requirements.
Extreme Superdome RAS, including advanced memory resiliency, Firmware First problem diagnosis, analysis
engine, and auto self-healing ensures the highest reliability for mission critical apps. Superior security, including
the Silicon Root of Trust, protects your customer’s workloads and data against firmware attacks and malware.
Optional deployment with HPE GreenLake provides flexible as-a-service consumption while maintaining on-
premises control.
NOTE
With six UPI links, the third-generation Intel® Xeon® Scalable Processor architecture delivers twice the UPI
links than the second-generation Intel® Xeon® Scalable Processor architecture. The maximum data rate is
3200 MT/s @ 1 DPC, which is 9% higher than with the second-generation Intel® Xeon® Scalable Processors.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 71

HPE Superdome Flex 280 overview

HPE Superdome Flex scalability

HPE Superdome Flex 280 is positioned for small and medium-size enterprise environments. It can:
• Meet business demands with high performance. In fact, this is the best performing four- and eight-socket server
in the HPE Server portfolio
• Scale up with better cost efficiency to address future growth because it starts at two sockets and scales to
eight sockets in two-socket increments, so it offers granular scalability to address growth efficiently
• Leverage GPUs, fast IO, and internal storage. Some competitor offerings do not offer GPU support, whereas
Superdome Flex 280 does. Also, the IO system is well balanced to optimize performance
• Guard against downtime with extreme Superdome RAS: Superdome Flex 280 has a unique set of RAS features
that are not present in other standard x86 servers
• Protect against firmware attacks and malware with superior security, including the HPE Silicon Root of Trust
• Consume as a service while maintaining on-premises control with HPE GreenLake, so your customer can get the
cloud experience while deploying on premises
• Preserve cash and align payments with deployment through HPE Financial Services, especially important for
customers needing this flexibility
• Support standard operating systems: SUSE, Red Hat®, Microsoft Windows, Oracle Linux®, and standard
virtualization technologies such as VMware and KVM

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 72

Specifications of the server:

• Two to eight sockets in a single system; scale in two-socket increments
• 5U, four-socket modular building block
• Third-generation Intel® Xeon® Scalable Processors, the only HPE platform being refreshed with this processor
• Designed to deliver 64 GB to 24 TB of shared memory, using DRAM only or in combination with Persistent
Memory (latest version)
This new server in the HPE compute portfolio can address four-socket workloads and complements the HPE
ProLiant DL500 series: the DL580 and DL560.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 73

Complementary platforms for demanding four-socket workloads

HPE Superdome Flex 280 four-socket server

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 74

HPE ProLiant four-socket servers

HPE Superdome Flex 280 complements the 2U ProLiant DL560 Gen10 server and 4U ProLiant DL580 Gen10
server in the four-socket space. The HPE Superdome Flex 280 is the only four-socket+ platform in the HPE
portfolio to feature third-generation Intel® Xeon® Scalable Processors and is the upgrade path for the ProLiant
DL580 installed base.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 75

HPE Superdome Flex 280 management

HPE Superdome Flex 280 web management interface

HPE Superdome Flex 280 has a web-based management interface. This interface is available only for HPE
Superdome Flex 280. It simplifies monitoring and management procedures for this system.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 76

Linux deployment on HPE Superdome Flex server

The HPE Superdome Flex Server supports the following Linux operating systems:

Linux OS Supported versions

Red Hat Enterprise Linux RHEL 7.3 to 7.9, RHEL 8.0 to 8.4
Oracle Linux 8 8.0 to 8.4
Oracle Linux 7 7.3 to 7.9
Oracle Linux UEK Oracle Linux 7.9, 8.0 to 8.4 UEK6, Oracle Linux 7.7, 7.8, 7.9, UEK 5
SUSE Linux Enterprise Server SLES 15 up to SP3, SLES 12 SP2 to SP5

All supported Linux OS versions support the maximum HPE Superdome Flex Server configuration of 32
processor sockets and 24 TB memory. HPE Foundation Software consists of software packages specifically
designed to ensure the smooth operation of the HPE Superdome Flex Server, including Data Collection Daemon
(DCD).

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 77

Windows 2019 deployment on HPE Superdome Flex server

Installing Windows Server 2019 on HPE Superdome Flex technical white paper

Microsoft Windows Server 2019 is the most recent Microsoft OS designed for hybrid cloud environments. With a
rich set of features and enabled for the latest technologies, this version can utilize all the components that are
part of HPE Superdome Flex Servers, including Persistent Memory, to offer an outstanding solution for Windows-
based applications that require growing and/or large and mission-critical environments.
Certified for Windows Server 2019 since March 2019, HPE Superdome Flex Server can scale up or scale out
Windows Server environments with its four-socket modular building blocks. Each building block can be
customized to match the workload requirements with a choice of memory size and capacity, processor and core
count, and amount and type of IO devices.
The HPE Superdome Flex Server can be used in a single chassis configuration and can be expanded up to four
chassis in total forming a server with 16 sockets (the Microsoft Windows Server limitation). Also, HPE nPars are
fully supported; servers can grow over time up to the maximum supported size with this operating system, that is,
16 processors and up to 24 TB of RAM.
Both Windows Server 2019 Standard Edition and Datacenter Edition are supported—the choice depends on
applications and business requirements. Windows Server 2019 and Windows Server 2016 are also supported on
HPE Superdome Flex 280.
The following rules apply when deploying Windows Server 2019 to the HPE Superdome Flex:
• Microsoft Windows Server 2019 can be installed manually or in an automated fashion (using PXE boot)
• Your customer should use the latest HPE Superdome Flex IO Service Pack version to install or update drivers,
software, and IO firmware with HPE Smart Update Manager (SUM)
• Configuration of the primary boot adapter is mandatory to install Windows on a bootable device
• HPE Persistent Memory is only supported with the Intel® Xeon® Scalable processor family second- and third-
generations (62xx and 82xx)

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 78

VMware deployment on HPE Superdome Flex

Running VMware vSphere® on HPE Superdome Flex systems technical white paper

VMware vSphere has multiple deployment options. Your customer can choose the options that best meet the
needs of their environment. They can use either an interactive or a scripted installation when installing the
software.
VMware vSphere ISO image options
VMware vSphere offers various image (ISO file) options. Your customer can use the VMware base image, or their
own custom image. HPE recommends building a custom image that includes all the new/updated drivers.
• VMware vSphere Hypervisor (ESXi ISO) image (VMware base image)—The VMware base image includes
the base VMware ESXi™ hypervisor image and default set of drivers. This image does not include HPE value-
add components or new or updated drivers. HPE recommends using a custom ISO image that includes new or
updated drivers to support the storage and network hardware included in the server
• Custom ISO image—Your customers can create their own ISO image for deploying VMware vSphere. To create
a custom ISO image, they should use the VMware Image Builder included with VMware vSphere Power CLI.
Your customer should start with the VMware base depot and then customize it to include the VMware vSphere
Installation Bundles (VIBs), delivering HPE value-add components that need to be loaded at boot time. VIBs
include all the updated drivers. The output of Image Builder is a custom ISO image that includes the VMware
base image and all the added VIBs
VMware 7.0 supports up to 24 TB of memory and 768 logical CPUs. Refer to the configuration maximums before
deploying VMware, as maximum values may change.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 79

Supported VMware vSphere versions

HPE Superdome Flex servers, based on Intel® Xeon® scalable 61xx or 81xx series processors (first-generation
Intel® Xeon® Scalable processors), Intel® Xeon® scalable 62xx or 82xx series processors (second-generation Intel®
Xeon® Scalable processors), and HPE Superdome Flex 280 servers, based on Intel® Xeon® scalable 53xx, 63xx, or
83xx series processors (third-generation Intel® Xeon® Scalable processors), support the following VMware
vSphere distributions:

VMware vSphere HPE Superdome Flex HPE Superdome Flex HPE Superdome Flex
releases (first-generation Intel® (second-generation 280 (third-generation
Xeon® Scalable Intel® Xeon® Scalable Intel® Xeon® Scalable
processors) processors processors)

VMware vSphere 6.5 U1 ✔

VMware vSphere 6.5 U2 ✔
VMware vSphere 6.5 U3 ✔
VMware vSphere 6.7 ✔
VMware vSphere 6.7 U1 ✔
VMware vSphere 6.7 U2 ✔
VMware vSphere 6.7 U3 ✔ ✔
VMware vSphere 7.0 ✔ ✔
VMware vSphere 7.0 U1 ✔ ✔ ✔
VMware vSphere 7.0 U2 ✔ ✔ ✔

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 80

Supported sockets configuration on HPE Superdome Flex family

The table below presents the VMware vSphere version and servers with the maximum socket configurations
supported:

VMware vSphere HPE Superdome Flex HPE Superdome Flex HPE Superdome Flex
releases (first-generation Intel® (second-generation 280 (third-generation
Xeon® Scalable Intel® Xeon® Scalable Intel® Xeon® Scalable
processors) processors processors)

VMware vSphere 6.5 U1 4 and 8

VMware vSphere 6.5 U2 4 and 8
VMware vSphere 6.5 U3 4 and 8
VMware vSphere 6.7 4 and 8
VMware vSphere 6.7 U1 4 and 8
VMware vSphere 6.7 U2 4 and 8
VMware vSphere 6.7 U3 4 and 8 4 and 8
VMware vSphere 7.0 4 and 8 4 and 8
VMware vSphere 7.0 U1 4 and 8 4 and 8 2, 4, and 8
VMware vSphere 7.0 U2 4 and 8 4, 8, 12 and 16 2, 4, and 8

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 81

Supported memory configuration on HPE Superdome Flex family

The memory limits supported by VMware vSphere on the HPE Superdome Flex family of servers, based on Intel®
Xeon® Scalable processors, are presented in the table below:

VMware vSphere HPE Superdome Flex HPE Superdome Flex HPE Superdome Flex
releases (first-generation Intel® (second-generation 280 (third-generation
Xeon® Scalable Intel® Xeon® Scalable Intel® Xeon® Scalable
processors) processors processors)

VMware vSphere 6.5 U1 6 TB

VMware vSphere 6.5 U2 6 TB
VMware vSphere 6.5 U3 6 TB
VMware vSphere 6.7 6 TB
VMware vSphere 6.7 U1 6 TB
VMware vSphere 6.7 U2 6 TB
VMware vSphere 6.7 U3 6 TB 12 TB
VMware vSphere 7.0 6 TB 12 TB
VMware vSphere 7.0 U1 6 TB 12 TB 12 TB
VMware vSphere 7.0 U2 6 TB 24 TB 24 TB

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 82

Learning check
7. You are in a meeting with a customer, and they challenge you with a statement: “We need a server solution to
support a virtualization project that needs a 16 socket-system and 24 TB of memory. HPE does not provide
such a solution.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 83

Activity: Managing HPE Superdome Flex 280

Participants will work by themselves on this activity. During this activity, you will explore the HPE Superdome
Flex 280 management interface.
1. Start the HPE Superdome Flex 280 simulator using the shortcut on the desktop of your management server.
2. Open Google Chrome and use the Superdome Flex 280 Simulator bookmark to access the simulator.
3. Answer the following questions:
a. How many nPartitions are present?
__________________________________________________________________________________________________________

b. Which chassis has a critical health error?

__________________________________________________________________________________________________________

c. Which subsystems in that chassis are not healthy?

__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 84

d. Which chassis is a base chassis?

__________________________________________________________________________________________________________

e. What type of chassis is the second chassis?

__________________________________________________________________________________________________________

f. Which menu option can be used to reboot RMC?

__________________________________________________________________________________________________________

g. Which menu option can be used to generate a certificate signing request?

__________________________________________________________________________________________________________

h. Which menu option can be used to open a remote console for a given nPar?
__________________________________________________________________________________________________________

i. Can a secure boot be enabled from the Hardware menu?

__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 85

Learning check
8. What is the maximum number of the CPU sockets that the HPE Superdome Flex 280 supports?
A. 4
B. 8
C. 16
D. 32

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 86

HPE SimpliVity
HPE SimpliVity offers a comprehensive, fully integrated solution that includes software-defined compute, storage,
and storage networking.
HPE SimpliVity hyperconverged node

HPE SimpliVity 380 node

An HPE SimpliVity hyperconverged node is an x86 server that is the basic hardware building block of the HPE
SimpliVity HCI solution.
• HPE SimpliVity nodes are based on HPE ProLiant or Apollo platforms
• The customer has a choice of Intel® or AMD-based HPE SimpliVity nodes
• HPE SimpliVity nodes are available in two variants:
– Software-optimized nodes
– Hardware-optimized nodes
• HPE SimpliVity nodes can be grouped together to formulate VMware clusters with support for VMware HA and
Dynamic Resource Scheduler (DRS) functionalities
• HPE SimpliVity clusters are part of HPE SimpliVity Federation

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 87

Data efficiency technologies in HPE SimpliVity

HPE SimpliVity nodes

The HPE SimpliVity data architecture is a globally aware file system and object store with data optimization
techniques and data services. By virtualizing how data is stored beneath the hypervisor, it abstracts data from its
underlying hardware, enabling hypervisor and x86 hardware independence. It shifts policies and management
from an infrastructure component orientation, usually logical unit numbers (LUNs) or datastores, to the
application workload and VM level. HPE SimpliVity uses the following technologies to improve data efficiency:
• Deduplication—Deduplication is the process of reducing disk workload, replication bandwidth, and storage
capacity by eliminating redundant data and retaining only one unique instance of the data on disk.
Deduplication helps deliver a lightweight, mobile data structure and is therefore key to solving a complexity
crisis by addressing the root cause
• Compression—Compression is the process of reducing the size of a given data set, providing a more
condensed format. It provides complementary value to deduplication by further reducing the disk workload,
network bandwidth, and storage capacity
• Optimization—Optimization is the intelligent treatment of data on its anticipated use by an application.
Systems that can identify file types and make real-time decisions about where to store that data can deliver
overall improved storage efficiency, performance, and bandwidth usage
Deduplication, compression, and optimization have several key benefits that address the core requirements of
today’s data center:
• Dramatic bandwidth reduction—Deduplicating, compressing, and optimizing all data at inception and keeping
it in this state when transferring to a remote site makes the transfer itself more efficient and saves significant
network bandwidth resources
• Enhanced data mobility—A fundamental principle of server virtualization is the mobility of VMs, but the
unoptimized data structures can significantly affect mobility in a traditional infrastructure environment due to
their size. When the data is deduplicated and compressed, it is easier to create point-in-time copies, move VMs
from one system to another, and move data to different data centers across the globe
• Efficient storage utilization—Required capacity can be reduced significantly in standard primary use cases,
based on the effective use of deduplication, compression, and optimization
• Enhanced performance—Since data is deduplicated, compressed, and optimized in real-time before it is
written to disk, it helps eliminate unnecessary writes to disk that saves IO and improves overall performance

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 88

Deduplication technologies have historically been designed to optimize disk storage capacity. When introduced to
the market in the mid-2000s, deduplication was applied mostly for backup. In this use case, optimizing for
capacity is crucial, given massive redundancy of data and the ever-increasing volume of data to be backed up and
retained. In primary storage systems, optimizing for disk capacity is a relatively lower priority. Disk IOPS are
usually a more expensive system resource than disk capacity.
HPE SimpliVity Data Virtualization Platform

HPE SimpliVity “chemistry”

Deduplication can be explained using chemistry terms. Imagine that you need to store “water” on a deduplicated
datastore. To do it, you need to store two atoms of hydrogen and one atom of oxygen. Because on a deduplicated
datastore, only unique data is stored, we only store one copy of the hydrogen atom and one oxygen atom.
If you want to store a “sugar” compound on a deduplicated datastore, you need six carbon atoms, 12 hydrogen
atoms, and six oxygen atoms. As we store only unique data on the datastore, only one carbon particle is added. In
the last example, we want to store a “soda” compound on the datastore, which is a mix of water and sugar. As all
components needed to create the soda compound are already stored on the datastore, no extra atoms are stored.
In this case, it means that instead storing 54 atoms, you store only these three, which are unique. This process
represents a large saving in storage capacity.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 89

HPE SimpliVity global deduplication

HPE SimpliVity “chemistry” replicated to second data center

If you customer wants to preserve their data by replicating them to a remote data center, they can transfer only
these three unique atoms, as they enable the rebuilding of all of the compounds. This helps your customer save a
large amount of bandwidth between the data centers.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 90

Primary global deduplication: IO reduction

Total IO savings with HPE SimpliVity

In a traditional environment, the largest IO consumer is usually backup traffic. Every night, when backups run, any
data that has changed since the last backup (at the very least) needs to be read off the array and sent across the
network to the backup storage location. This creates a significant spike every night, which is the reason backups
are generally only scheduled after regular business hours. With HPE SimpliVity, leveraging deduplication on
primary storage greatly reduces IO.
By taking local backups via metadata, HPE SimpliVity can take full backups of the VMs with essentially no
additional IO to the VM, thus eliminating the largest spike of IO. Also, by deduplicating all data inline and utilizing
this deduplicated data to perform full, independent backups through metadata and move only unique data to
remote sites, HPE SimpliVity is able to drastically reduce the local and remote IO, and thus shrink the amount of
hardware needed to support a remote data center. Since deduplication never writes the same block twice, it has a
read- and write-avoidance effect on all data protection, meaning zero IO to create a logical VM copy in a 100%
inline deduplicated environment.
In a traditional environment, when data is replicated to a remote site, the data that has changed must be read
from the array and sent across the WAN. This results in additional IO.
With HPE SimpliVity, by intelligently moving only unique data between data centers, less data needs to be read
off of the disks. This results in minimal IO to replicate data between sites. The global deduplication and
compression reduction ratio can greatly contribute to storage savings.
The traditional storage array-level or VMware vSphere snapshots are quick and often used as a short-term
recovery point. While these snapshots do have little impact, they must still be accounted for.
Since HPE SimpliVity backups can be taken in seconds and have no performance impact on the VM running, they
make an easy replacement for local snapshots. Local protection can now utilize a zero-IO backup engine,
obsoleting snapshots for short Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 91

This leaves just the primary application workload, with a small data protection overhead. However, things get
even better when we consider the fact that all data, not just data protection, is deduplicated and compressed in a
SimpliVity environment. This reduces the IO profile even further. Also, compression significantly amplifies data
reduction and deduplication is even more efficient when VMs are similar (common OS binaries, libraries, apps, and
so on) and have redundant data within a single VM and among all VMs in the local cluster, reducing the primary
footprint even more.
This is how HPE SimpliVity can greatly reduce the IO needs of the storage layer. IO reduction is possible with a
data protection engine that exploits inline data reduction. The required back-end footprint for each node is
greatly reduced. Relatively large original workloads, when run on HPE SimpliVity, require significantly less
resources.
HPE SimpliVity key architecture concepts

HPE SimpliVity 2600

To better understand HPE SimpliVity, we need to introduce key architecture concepts and components.
HPE Virtual Controller
The HPE SimpliVity Virtual Controller (VC), a VM-based controller running on the hypervisor, is the foundational
software of the HPE SimpliVity hyperconverged infrastructure (HCI). Every HPE SimpliVity node has a single VC
running on it. The VC runs the HPE SimpliVity software and supports VMware vStorage APIs for Array
Integration (VAAI)-NAS plug-in.
The VC can be managed via a CLI, which is accessed via an SSH session from a terminal emulator. A single CLI
session (to a VC) provides full visibility and management across an entire HPE SimpliVity Federation.
The VC is also responsible for presenting NFS datastores to all HPE SimpliVity nodes and participates heavily in
the read/write processes.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 92

Compute node
HPE SimpliVity compute nodes are non-hyperconverged servers that plug into an HPE SimpliVity cluster and
provide additional compute capacity, while consuming the storage provided by the HPE SimpliVity nodes.
A standard VMware ESXi host is any server that is not an HPE SimpliVity node. These standard ESXi hosts can
exist in your customer’s vCenter Server environment in addition to the HPE SimpliVity nodes. They are also called
compute nodes, and they are especially useful for workloads that are not constrained by storage resources.
If your customer’s VMware vCenter® Server contains standard ESXi hosts, they can enable them to access the
HPE SimpliVity datastores. This allows them to use VMware vSphere vMotion® and Storage vMotion® to migrate
VMs running on a standard host to another host in the SimpliVity cluster with no disruption to users (as long as
the VM guest operating system is supported by HPE SimpliVity).
If your customer’s cluster includes standard hosts that use HPE SimpliVity datastores, they can manually install
the HPE SimpliVity VAAI-NAS plugin on those hosts. This plugin improves performance and frees up memory
when cloning VMs.
HPE SimpliVity Cluster
HPE SimpliVity clusters allow your customer to share resources among nodes and associated VMs. HPE
SimpliVity nodes must reside in one cluster per data center; they cannot reside outside a cluster. At least two
HPE SimpliVity nodes are required in a cluster to share data and ensure HA for continuous operation. After a
cluster includes one or more HPE SimpliVity nodes, it functions differently than a standard vCenter Server cluster.
A standard VM cluster functions as a distributed computing system that has processing power and memory. A
cluster with HPE SimpliVity nodes also requires a shared storage system. This means that all of the hosts in the
cluster need to share the same HPE SimpliVity datastore to deduplicate the data in the datastore.
Your customer should not move HPE SimpliVity nodes to another cluster within the same data center, as HPE
SimpliVity options will not function as expected. The VMs will lose HA compliance and the datastore will no
longer be accessible to the VMs that used to reside on the host your customer moved. If your customer needs to
move an HPE SimpliVity node to another cluster, they must remove the node from the Federation, and redeploy it
in the new cluster.
HPE SimpliVity Federation
An HPE SimpliVity Federation is a virtual group that represents a group of networked HPE SimpliVity nodes. A
Federation enables your customer to manage their HCI deployed in multiple sites as a single entity. A Federation
can be configured as one of the following types:
• Centrally managed—To support larger Federations, this option uses a VM called the Management Virtual
Appliance (MVA). The MVA is a dedicated VM that provides centralized management and coordination of
operations across clusters of HPE SimpliVity nodes for high-scale configurations. Your customer can deploy a
new centrally managed Federation or convert from an existing peer-managed Federation
• Peer managed—Designed for smaller Federations, your customer can deploy and manage a single VMware
vCenter Server with 32 HPE SimpliVity nodes. To scale the Federation beyond 32 hosts, your customer can
leverage an Enhanced Link Mode and link up to five vCenter Servers with a maximum of 32 HPE SimpliVity
nodes in each vCenter Server

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 93

HPE SimpliVity Datastore

When configuring an HPE SimpliVity cluster, one or more datastores must be created to present the storage to
the hypervisor. Each datastore is presented as an NFS datastore with a common namespace across all the VCs in
the HPE SimpliVity cluster. Virtual Machine File System (VMFS) datastores are not supported. These datastores
are logical constructs within the HPE SimpliVity Data Virtualization Platform (DVP) layer and are utilized as a
communication channel between the hypervisor and the DVP. Since the datastores are virtual, they can be
created with no ties to the actual underlying storage capacity. Your customer should refer to configuration
guidelines for the maximum number of datastores supported in a cluster and Federation. The SimpliVity
datastores can be resized online, larger or smaller, with no disruption to storage availability or performance.
Each datastore has a single default backup policy associated with it. This backup policy acts as the default
backup policy that is applied to any VMs stored on it. Creating multiple datastores provides a mechanism for easy
application of different default SimpliVity backup policies to VMs.
Deduplication is not bound by datastores since it happens across all data in an HPE SimpliVity cluster. Similarly,
replication is not limited by datastores since it is defined at the VM level (via a SimpliVity backup policy to a
remote cluster).

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 94

HPE SimpliVity product family

HPE SimpliVity portfolio

HPE SimpliVity offers various different models to match customer sizes and requirements. In general, there are
three families: SimpliVity 380, SimpliVity 325, and SimpliVity 2600, each of them with unique positioning.
The HPE SimpliVity 380, based on the HPE ProLiant DL380 Gen10 Server, is a compact, scalable, 2U rack-
mounted building block that delivers integrated server, storage, and storage networking services. Adaptable for
diverse virtualized workloads, the secure 2U HPE SimpliVity 380 Gen10 delivers world-class performance with
the correct balance of expandability and scalability. It also provides a complete set of advanced functionalities
that enable dramatic improvements to the efficiency, management, protection, and performance—at a fraction of
the cost and complexity of today's traditional infrastructure stack. HPE SimpliVity 380 models are software
optimized.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 95

The HPE SimpliVity 325 Gen10, based on the HPE ProLiant DL325 Gen10 Server, is a compact, scalable, 1U
rack-mounted building block that delivers integrated server, storage, and storage networking services. The HPE
SimpliVity 325 Gen10 Server is the secure and versatile single-socket server for virtualization and IO intensive
workloads and is ideal for remote office or space-constrained locations. This 1P, 1U server delivers an exceptional
balance of processor, memory, and IO for 2P performance at 1P TCO. Your customers can get the most out of
their virtualized environment with this versatile server, delivering a low hypervisor software cost and low cost per
VM.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 96

HPE SimpliVity portfolio

The HPE SimpliVity 2600 solution dramatically simplifies IT by combining infrastructure and advanced data
services for virtualized workloads into a building block that delivers server, storage, and storage networking
services. The HPE SimpliVity 2600 is based on the Apollo 2000 Gen10 system. This is a 2U modular chassis with
shared power, cooling, and front-disk enclosure. It also delivers a complete set of advanced functionalities that
enables dramatic improvements to the efficiency, management, protection, and performance of virtualized
workloads at a fraction of the cost and complexity of today’s traditional infrastructure stack.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 97

Learning check
9. Which HPE SimpliVity offering is positioned for backup/archive and longer-term SimpliVity backups?
A. HPE SimpliVity 380G
B. HPE SimpliVity 325
C. HPE SimpliVity 2600
D. HPE SimpliVity 380H

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 98

HPE Apollo 2x00 and 4x00

HPE provides various different Apollo systems to support different workloads, including HPC and object storage.
HPE Apollo 2000 Gen10 Plus server nodes

HPE Apollo 2000 Gen10 Plus portfolio

The HPE Apollo 2000 Gen10 Plus System is a dense, multi-server platform that packs incredible performance
and workload flexibility into a small datacenter space, while delivering the efficiencies of a shared infrastructure. It
is designed to provide a bridge to scale-out architecture for traditional data centers, so enterprise and medium-
size enterprise customers can achieve the space-saving value of density-optimized infrastructure in a cost-
effective and nondisruptive manner.
The Apollo 2000 Gen10 Plus offers a density optimized, shared infrastructure with a flexible scale-out
architecture to support a variety of workloads from remote site systems to large HPC clusters and everything in
between. HPE iLO 5 provides built-in, firmware-level server security with the Silicon Root of Trust. It can be
deployed cost-effectively starting with a single 2U, shared infrastructure chassis and configured with a variety of
storage options to meet the configuration needs of a wide variety of scale-out workloads. The Apollo 2000
Gen10 Plus System delivers up to four times the density of a traditional rack mount server with up to four
ProLiant Gen10 Plus independent servers per 2U mounted in standard racks with rear-aisle serviceability access.
A 42U rack can house up to 20 Apollo n2X00 series chassis accommodating up to 80 servers per rack.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 99

HPE ProLiant XL220n Gen10 Plus Server

The HPE ProLiant XL220n Gen10 Plus Server provides:
• 2P/1U half width server tray built on third-generation Intel® Xeon® Scalable processors. With choices from eight
to 40 cores up to 3.5 GHz CPU speed and power ratings up to 270 W (some CPUs may require direct liquid
cooling [DLC]). The tray has eight memory channels per socket, 3200 MT/s memory, two PCIe Gen4 slots, an
OCP3.0 slot, and multiple networking options, including high speed fabric
• Optional USB Mezz Riser Kit
• Separate NIC and iLO ports
• Up to four server trays per chassis
HPE ProLiant XL225n Gen10 Plus Server
The HPE ProLiant XL225n Gen10 Plus Server provides:
• 2P/1U half width server tray built on the AMD EPYC 7002 and EPYC 7003 processors. With choices from eight
to 64 cores, up to 3.7 Ghz base and 4.1 Ghz turbo CPU speed and power ratings 280 W
• The tray has eight memory channels per socket, 3200 MT/s memory, two PCIe Gen4 slots, an OCP3.0 slot, and
multiple networking options, including high speed fabric
• Optional USB Mezz Riser Kit
• NIC/shared iLO network port
• Up to four server trays are supported per chassis
HPE ProLiant XL290n Gen10 Plus Server
The HPE ProLiant XL290n Gen10 Plus Server provides:
• 2P/2U half-width server tray built on third-generation Intel® Xeon® Scalable processors. With choices from
eight to 40 cores up to 3.5 GHz CPU speed and power ratings up to 270 W (some CPUs may require DLC)
• The tray has eight memory channels per socket, 3200 MT/s memory, two PCIe Gen4 slots, an OCP3.0 slot, and
multiple networking options, including high speed fabric
• Optional USB Mezz Riser Kit
• Separate NIC and iLO ports
• Up to two server trays per 2U

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 100

Apollo 2000 Gen10 Plus

HPE Apollo 2000 Gen10 Plus comparison

The table above presents a comparison of HPE Apollo Gen10 systems.

NOTE
HPE Apollo Gen10 Plus systems are available with Intel® and AMD CPUs.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 101

Apollo 2000 Gen10 Plus—Flexible storage

Apollo 2000 Gen10 Plus storage options

The n2600 chassis offers multiple back plane options, including zero and eight SFF SAS/SATA/NVMe good for a
variety of HPC applications and 24 SFF SAS/SATA drives ideal for enterprise workloads. Each chassis supports
five single rotor fans, includes an integrated Rack Consolidation Module, and supports up to 1600 W power
supplies.
The n2400 chassis offers no storage support for those implementations that require the highest bin processors
for HPC workloads. Each chassis supports five single rotor fans, includes integrated Rack Consolidation
Management (RCM), and supports up to 1600 W power supplies.
NOTE
The RCM module kit allows iLO aggregation at the chassis level, and the port for the HPE Apollo Platform
Manager is optional on all chassis. The RCM Module consists of 2 iLO ports for redundancy. It can also be
daisy chained to connect to a ToR management switch.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 102

HPE Apollo 4200 Gen10 Plus/4510 Gen10 Server

HPE Apollo 4200/4510 Gen10

The HPE Apollo 4200 Gen10 Plus System, like the other members of the HPE Apollo 4000 Systems family, is
specifically designed to unlock the business value of data stemming from digital transformation (DX) and data
infrastructure modernization, at any scale, and with ideal economics. It is designed for both ends of the data-
centric workload spectrum—from deeper data lakes and archives to performance-demanding ML, data analytics,
hyperconverged infrastructure, and cache-intensive workloads. The HPE Apollo 4200 Gen10 Plus System
provides the data infrastructure foundation for any successful data-driven organization.
The HPE Apollo 4510 Gen10 System offers revolutionary storage density and accessibility in a 4U rack mount
form factor. Fitting in HPE Standard 1075 mm racks and featuring a front-drawer design for its bulk data drives,
it has one of the highest capacities of any 4U storage server with standard rack depth. When your customer is
running Big Data solutions, such as object storage, data analytics, deep archive, or other data-intensive
workloads, the HPE Apollo 4510 Gen10 System allows them to save valuable data center space.
Its unique density-optimized and easy-access design accommodates a wide array of configuration choices, with
support for two Intel® Xeon® Processors, 16 DIMM slots, four IO expansion slots, 60 LFF bulk storage drive slots,
two SFF drive slots, and two M.2 internal drive slots.

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 103

The use cases for both systems include:

• Big Data analytics:
– Density-optimized platform
– Hyperscale in reduced footprint
– Highest level of performance and efficiency
– NVMe support for metadata and caching
• Scale-out SDS:
– Software delivered on industry-standard hardware
– Scale affordably and accommodate PBs of data
– Provides architectural flexibility with both scale-up and scale-out solutions
• Backup and archive:
– Compatible with multiple backup and archive applications
– Converged scale-out storage for backup and archive
• Density-optimized storage:
– Space and cost savings due to density-optimized infrastructure
– Plug-and-play integration in existing data center—reduced implementation time

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 104

Activity: Meeting with the customer

Participants will work as a group on this activity. After presenting the HPE compute portfolio, HSP has asked you
to verify if they understand everything correctly.
Answer the following questions, and decide if the statements are true or false:
1. True or false: HPE Superdome Flex cannot be managed using HPE OneView. ________________________

2. True or false: HPE Synergy has Intel®- and AMD-based compute nodes. ________________________

3. What is the maximum number of frames that can be added to a logical enclosure? ________________________

4. True or false: HPE SimpliVity does not support AMD CPUs. ________________________

5. Which data efficiency technologies are used in HPE SimpliVity?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

6. Which CPUs are used in Apollo Gen10 Plus systems?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

7. Which mezzanine slot supports SAS connectivity for HPE Synergy compute nodes? ________________________

8. True or false: The HPE Superdome Flex 280 has the same management interface as the HPE Superdome
Flex. ________________________

9. True or false: The HPE ProLiant DL345 is a four-socket server with AMD CPUs. ________________________

10. What is the purpose of the HPE Synergy Composer2?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 105

Learning check
10. Which Apollo 2000 Gen10 Plus system supports AMD processors?
A. XL290n
B. XL220n
C. XL225n
D. XL170r

11. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 106

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 107

Summary
• Today, IT decision makers are responding less to the technical capabilities of solutions, and more to solutions’
abilities to deliver real-world outcomes for the workloads your customers use every day. HPE provides an
optimized compute platform for any type of workload
• The HPE compute portfolio consists of HPE Synergy, HPE ProLiant Gen10 Plus, HPE Superdome Flex, HPE
SimpliVity, and HPE Apollo. These servers provide solutions for everything from entry-level needs to backup
and archive to high performance computing

Lab exercises
Open your lab guide, and complete:
• Lab 1: Exploring HPE Synergy and HPE Superdome Flex setup
• Lab 2: Installing an operating system on HPE Superdome Flex

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 108

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “HPE Virtual Connect only
works with HPE Networking components and does not offer advanced functionalities like sFlow.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a statement: “Initial setup of HPE Synergy
always requires a technician present on site. We have many remote offices and having a technician available
can be quite difficult. It will delay the deployment process.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 109

3. You are in a meeting with a customer, and they challenge you with a statement: “We plan to deploy multiple
HPE Synergy frames with the same configuration, but we are afraid that changing the uplink set for all of
them will be time consuming.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. You are in a meeting with a customer, and they challenge you with a statement: “We have multiple branch
offices running the HPE Synergy platform. All the configuration changes are developed in the HQ. We are
afraid that propagating them to the branch offices will be time consuming and can result in significantly
different configurations.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
HPE compute product portfolio Page 110

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy
solutions
Module 2

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 2

Learning objectives
After completing this module, you should be able to:
• Explain HPE Virtual Connect (VC) for HPE Synergy technologies
• Perform an HPE Synergy hardware setup
• Configure HPE Synergy components
• Describe automation with REST application programming interface (API) and PowerShell scripting

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 3

Customer scenario

HSP purchased HPE Synergy to replace legacy infrastructure, based on HPE BladeSystem. Setup of the initial
solution will be done by HPE. They are growing, and they plan to open offices in an additional 10 U.S. states, and
they need an infrastructure to support infrastructure services and several other workloads.
HSP plans to use HPE Synergy at the new sites, and they want to learn how to configure HPE Synergy in case
they must do it on their own. They have asked you for help and asked for a demonstration of how to configure
the HPE Synergy platform.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 4

HPE Virtual Connect for HPE Synergy technologies

HPE Synergy supports HPE Virtual Connect as interconnect modules (ICMs).

Virtual Connect technology

HPE Virtual Connect SE 100 Gb F32 Module for Synergy

HPE VC technology provides a wire-once, edge-safe, and change-ready environment that makes it easy for
administrators to manage dynamic network environments. HPE VC technology virtualizes compute module
connectivity by adding a hardware abstraction layer that removes the direct coupling between servers and a LAN
or SAN network infrastructure.
HPE VC features include:
• Uses server profiles that define compute node identity
• Replaces factory WWNs and MACs with virtual ones assigned by HPE OneView
• Enables serial number virtualization
• Uses standard Ethernet networking to carry virtual LAN (VLAN) tagged and untagged traffic through the
composable fabric. Each network and fabric must be defined within HPE OneView

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 5

Virtual ID pools

Virtual ID pools in HPE OneView

A default set of virtual identification (ID) pools for MAC addresses, WWNs, and serial numbers are provided at
appliance startup. If your customer needs additional addresses or identifiers, they can add auto-generated
ID pools or custom ID pool ranges.
An ID pool is a collection of one or more ranges that your customer can randomly generate or specify to provide
large address spaces. The pools are composed of address and ID ranges. Your customer can individually enable or
disable a range, or remove any unused range of addresses and make them unavailable. ID pool ranges do not
conflict with physical IDs, provided the virtual ranges your customer creates exclude the physical ID ranges.
Virtual IDs are available only for HPE Synergy, and they are provided through HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 6

HPE VC configurations for fault tolerance and load balancing

HPE VC provides several levels of fault tolerance and load distribution for Ethernet network topologies
associated with uplink ports and compute module NIC ports. The configurations include:
• Active-standby
• Active-active
• Multi-module link aggregation (M-LAG)
Active-standby setup

Traffic flow for HPE VC active-standby configuration

Active-standby is a legacy method of using HPE VC technology for a compute module-to-network interconnect.
The graphic above shows a basic network architecture, using one logical interconnect (LI) in a redundant, active-
standby configuration. Note that there is no link aggregation configured on the Top of Rack (ToR) switches. The
upstream network switch connects a network to a single port on each HPE VC ICM.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 7

Active-active setup

Traffic flow for HPE VC active-active configuration

Active-active is another method of connecting HPE VC to the data center. Active-active configurations require
two LIs and use all available uplinks across the ICMs, maximizing bandwidth to external networks and reducing
the oversubscription rates for compute module-to-core network traffic. There are no stacking links, and compute
modules are responsible for load balancing across ICMs cross-connected to the uplink infrastructure.
The issue with active-active is that link errors between the ICM and ToR would not be detected by the server,
causing a black hole for traffic until the failed link is repaired. To address this potentially crippling fault, HPE has
created the SmartLink feature. SmartLink enables a compute module to discover a fault in a path and redirect
traffic accordingly.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 8

Multi-module link aggregation

Traffic flow for M-LAG without ToR-to-ICM cross-connects

As an alternative active-active configuration, HPE Synergy VC ICMs allow M-LAG configurations that logically
aggregate ports across multiple modules for increased bandwidth and higher availability. M-LAGs can be
implemented for uplink and downlink traffic flow.
The graphic above shows the traffic flow using uplink M-LAG without cross-connecting the ToRs and ICMs. Green
arrows indicate traffic flow from Compute Module X Port 1 to Compute Module Y Port 1 while orange arrows
denote traffic flow from Compute Module X Port 2 to Compute Module Y Port 2. ICM A Port Q1 is aggregated
with ICM B Port Q2 (for both LI 1 and LI 2) for increased bandwidth and availability. All uplinks across ICMs are
enabled, allowing the ICMs to provide load balancing and failover functions.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 9

M-LAG support

Single-homed and multi-homed M-LAG with single LIG

Multichassis link aggregation (M-LAG) technologies allow the creation of Link Aggregation Control Protocol
(LACP) groups on the upstream switch that spans multiple Synergy VC modules:
• Single-homed configuration
• Multi-homed configuration
To form an M-LAG, make sure that:
• The switch is 802.1d compliant
• A trunk between different ICMs is created
• Intelligent Resilient Framework (IRF) /virtual Port Channel (vPC) ToR links are included
• ICM cluster links (using Q7 and Q8 ports) are included
• A single logical interconnect group (LIG)/LI and a single uplink set spanning both master ICMs are defined
M-LAG constraint: A LIG cannot contain networks with the same VLAN ID.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 10

Advanced Virtual Connect features

Advanced VC settings

If HPE VC modules for HPE Synergy are used, the following features can be configured:
• Storm control
• Loop protection
• Pause flood protection
• Link Layer Discovery Protocol (LLDP) IP address mode
• LLDP tagging
• Dynamic Domain Name System (DNS)
Storm control
A network traffic storm occurs when packets flood a physical interface, creating excessive traffic and degrading
network performance.
If a threshold is reached, the storm control setting allows an administrator to suppress excessive inbound
multicast, broadcast, and destination lookup failure (DLF) packets. The threshold is provided by the user and is
configured in packets per second. If incoming multicast, broadcast, or DLF traffic exceeds the threshold during a
polling interval, the offending traffic is blocked until the start of the next polling interval. This threshold protects
against broadcast storms causing disruption to Layer 2 networks from being propagated further.
The storm control setting is enabled or disabled on the Logical Interconnect Groups and Logical Interconnects
screens as part of the Interconnect Settings panel.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 11

Loop protection
The loop protection feature enables detection of loops on the subport and then disables the subport. Depending
on the role of the HPE VC Ethernet port, HPE VC can use several loop avoidance mechanisms.
HPE OneView network loop protection uses two methods to detect loops:
• The interconnect monitors the subports for special packets transmitted from upstream devices
• The interconnect reviews and intercepts common loop detection frames used in other switches, such as Cisco,
to prevent loop protection on the upstream switch, where externally generated frames are used to detect a
loop condition
When network loop protection is enabled on the Logical Interconnects screen, and a loop detection frame is
received on a subport, the subport is disabled immediately until an administrative action is taken.
The administrative action involves resolving the loop condition and clearing the loop protection error condition.
The loop detected status on a server can be cleared by editing the server profile and unassigning all networks
from the connection corresponding to the server in the loop detected state or by selecting Reset port
protection action on the Interconnects screen.
Pause flood protection
Pause flood protection, when enabled, detects pause flood conditions on uplink port, detects and protects pause
flood conditions on server downlink ports, and disables the server downlink port.
Ethernet switch interfaces use pause frame-based flow control mechanisms to control data flow. When a pause
frame is received on a flow control enabled interface, the transmit operation is stopped for the pause duration
specified in the pause frame. All other frames destined for this interface are queued up. If another pause frame is
received before the previous pause timer expires, the pause timer is refreshed to the new pause duration value. If
a steady stream of pause frames is received for extended periods of time, the transmit queue for that interface
continues to grow until all queuing resources are exhausted. This condition severely impacts the switch operation
on other interfaces. In addition, all protocol operations on the switch are impacted because of the inability to
transmit protocol frames. Both port pause and priority-based pause frames can cause the same resource
exhaustion condition.
VC interconnects provide the ability to analyze server downlink ports for pause flood conditions, and take
protective action by disabling the port.
The default polling interval is 30 seconds and is not customer configurable. The SNMP agent supports trap
generation when a pause flood condition is detected or cleared.
LLDP IP address mode
Network administrators require full control and flexibility over the IP address formats that are sent in the LLDP
payload. This option allows an administrator to select the management IP address type to be communicated
through the LLDP.
The LLDP IP address mode setting allows administrators to support IPv4-only, IPv6-only, or both IPv4 and IPv6
environments. This setting allows IPv4, IPv6, or both the addresses as the management IP address to be
communicated through the LLDP payload on uplinks, downlinks, stacking links, and s-channels.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 12

LLDP tagging
LLDP tagging, when enabled, uses the management IP address of the lowest numbered Ethernet bay location in
the LI. This IP address is transmitted in tagged LLDP frames on the downlink ports and untagged frames on the
uplinks and stacking link ports.
LLDP tagging is available for the following interconnects:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
When enabled, based on the LLDP IP address mode, HPE OneView obtains the IP address of the HPE Virtual
Connect SE 40 Gb F8 Module for HPE Synergy and the HPE Virtual Connect SE 100 Gb F32 Module for HPE
Synergy in the lowest number bay location in the LI and advertises this address as the management address
type–length–value (TLV) for all the Virtual Connect SE 40 Gb F8 Modules for Synergy and for all the HPE Virtual
Connect SE 100 Gb F32 Modules for HPE Synergy, respectively, in the LI.
When disabled, by default, each VC interconnect advertises its master interconnect IP address as the LLDP
management address TLV.
Dynamic DNS
The DNS is a method for mapping a hostname to its IP address. The DNS allows users to enter more readily
memorable and intuitive hostnames, rather than IP addresses, to identify devices connected to a network.
A hostname resolution can be either static or dynamic:
• In a static resolution, a local table is defined on the interconnect that associates hostnames with their IP
addresses. Static tables can be used to speed up the resolution of frequently queried hosts
• A dynamic resolution requires that the interconnect query a DNS server located elsewhere on the network.
Dynamic name resolution takes more time than static name resolution, but requires far less configuration and
management
Dynamic DNS update configuration support enables the HPE Virtual Connect SE 100 Gb F32 Module for HPE
Synergy interconnects to update the DNS server when the IP address or hostname is changed. This functionality
is applicable for both IPv4 as well as IPv6 addresses. Your customer can enable or disable the Dynamic DNS
feature. By default, this feature is enabled.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 13

IGMP settings

IGMP settings within a LIG

The Internet Group Management Protocol (IGMP) snooping feature allows interconnects or VLAN interfaces to
analyze the IGMP IP multicast membership activities, and configure hardware Layer 2 switching behavior of
multicast traffic to optimize network resource usage. Currently, IGMP v1, v2 (RFC 2236), and IGMPv3 are
supported.
IGMP snooping can be enabled on:
• All the interconnects
• The specific VLAN tagged network
• A range of VLAN tagged networks associated with the LI

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 14

IGMP Multicast VLAN

IGMP Multicast VLAN (MVLAN) provides an efficient distribution of multicast streams on Layer 2 networks.
MVLAN reduces the amount of bandwidth required for forwarding multicast traffic between the interconnect and
upstream routers. The Multicast VLANs option is disabled by default on the interconnects. MVLAN configuration
is supported only on the HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy.
MVLAN uses a port-based MVLAN approach. The MVLAN configuration is effective only when IGMP snooping is
enabled on all or a subset of VLANs. Your customer can configure an MVLAN, and assign a range of multicast
group addresses with the MVLAN on the interconnect. The MVLAN must be associated with any one of the
uplinks sets before assigning multicast group addresses. The downlink ports must be members of the MVLAN
your customer has configured to work as receiver ports for the hosts. The downlink traffic with hosts is untagged.
The interconnect receives one copy of each multicast stream and then replicates the stream only to the hosts
that want to receive it. All other types of multicast traffic are forwarded without modifications. Your customer can
configure multiple MVLANs, but they must have separate and distinct multicast groups. Your customer can add
MVLANs from either the Logical Interconnects or Logical Interconnect Groups screen.
IGMP proxy reporting
IGMP snooping with proxy reporting or report suppression actively filters the IGMP packets, reducing the load on
the multicast router. The IGMP proxy reporting is effective only when IGMP snooping is enabled for all or a subset
of VLANs. The IGMP proxy reporting is enabled by default.
The IGMP proxy reporting option is supported only on the following interconnects:
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
Your customer can enable or disable the IGMP proxy reporting configuration on the Logical
Interconnect or Logical Interconnect Groups screen.
• Enabled—The host reports are filtered to minimize traffic to the upstream multicast router
• Disabled—The host reports are not filtered. All the host reports are forwarded to the upstream multicast
router
IGMP multicast flood prevention
By default, unregistered IGMP multicast traffic traversing VC Ethernet modules are flooded on the configured
Ethernet or RDMA over Converged Ethernet (RoCE) network. The IGMP multicast flood prevention option
prevents the flooding of unregistered multicast traffic. The IGMP multicast flood prevention setting is effective
only when IGMP snooping is enabled for all or a subset of VLANs. When enabled, unregistered multicast traffic
from uplinks is dropped, and traffic from the server ports is redirected to the active uplink port. IGMP multicast
flood prevention is disabled by default.
The IGMP multicast flood prevention option is supported only on the following interconnects:
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 15

Utilization sampling

Utilization sampling settings within a LIG

The Utilization Sampling settings control the data collection rate for all port statistics on the Interconnects
screen. The port statistics display as graphs when the pointer is hovered over the Utilization screen component.
The utilization data collected is based on the sample count and the sample interval value. The default values
provide an hour's worth of data. Your customer can increase or decrease the frequency of the sample interval,
and increase or decrease the number of samples to be stored. The adjustment of either value controls the length
of the overall time for which data is available.
For HPE VC FC Modules, utilization sampling is always enabled and cannot be disabled. The default sampling rate
for HPE VC FC Module is one sample every minute. The sample collection rate for HPE VC FC Modules cannot be
set.
In addition to specifying time between samples of utilization data, the interval between samples specifies the
frequency at which data is refreshed on the Interconnects screen.
The utilization sampling option allows your customer to specify the number of samples to be collected per hour
and provides a total sampling history. The total sampling history is based on the specified number of samples and
the interval between samples.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 16

sFlow

sFlow settings within a LIG

Sampled flow (sFlow) is a technology for monitoring traffic in data networks containing switches and routers. The
sFlow monitoring feature helps to configure an Ethernet or RoCE network to send sFlow traffic to a list of
specified collectors. The sFlow can be configured only on Ethernet ICMs in HPE Synergy.
The sFlow system consists of a sFlow agent embedded in an Ethernet ICM and a remote sFlow collector. The
sFlow agent collects interface counter information and packet information and encapsulates the sampled
information in sFlow packets. When the sFlow packet buffer is full, or the aging timer (fixed to one second)
expires, the sFlow agent encapsulates the sFlow packets in the User Datagram Protocol (UDP) datagrams. The
UDP datagrams are then sent to the specified sFlow collector. The sFlow collector analyzes the information and
displays the results. One sFlow collector can monitor multiple sFlow agents.
sFlow provides the following sampling mechanisms:
• Flow sampling—Obtains packet information
• Counter polling—Obtains interface counter information
Flow sampling directions:
• Ingress—Ensures that the incoming packets are actually from the networks from which they claim to originate
• Egress—Monitors and restricts the outgoing packets of information from one network to another

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 17

The sFlow setup primarily involves:

1. Configuring an Ethernet or RoCE network that is part of an uplink set.
2. Configuring the IP address of an sFlow agent.
3. Adding collectors, and defining packet, and header sizes.
4. Adding ports, and enabling sampling and pooling function on ICM ports.
The sampled data is delivered through a configured network to a collector. The collector identity and network
data are associated with the sFlow agent. The sFlow configuration is supported on the following devices:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
sFlow limitations include:
• The IPv4 address of an sFlow agent and an interconnect management interface cannot be in the same subnet
• The maximum number of ports that can be sampled or polled per LI is 196
• The sFlow monitoring is suspended on an ICM when the CPU usage crosses a predetermined threshold. The
sFlow monitoring resumes after the CPU usage falls below the lower threshold
• A maximum of three sFlow collectors are supported per LI

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 18

SNMP

SNMP settings within a LIG

Network management systems use SNMP to monitor network-attached devices for conditions that require
administrator attention. By configuring settings on the Logical Interconnect Groups and Logical Interconnects
screens, your customer can enable third-party SNMP managers to monitor (read only) network status information
from the interconnects.
An SNMP manager typically manages many devices, and each device can have many objects. It is impractical for
the manager to poll information from every object on every device. Instead, each SNMP agent on a managed
device notifies the manager without solicitation by sending a message known as an event trap.
HPE OneView enables your customer to control the ability of SNMP managers to read values from an
interconnect. Your customer can designate the SNMP manager to which traps will be forwarded. By default,
SNMP is enabled with no trap destinations set.
When your customer creates an LI, it inherits the SNMP settings from its LIG. To customize the SNMP settings at
the LI level, your customer should use the Logical Interconnects screen or REST APIs.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 19

LIG and LI settings support SNMPv1, SNMPv2, and SNMPv3 protocols for forwarding traps, as well as for user
read-only access to the interconnect management information base (MIB).
SNMPv3 provides a more secure administrative framework than the previous SNMP versions. Your customer can
enable SNMPv3 forwarding for trap and inform notifications, and define SNMPv3 users and multiple trap
forwarding destination addresses, using both IPv4 and IPv6 addresses. Your customer is prompted to enter
configuration settings when specifying trap forwarding destinations. The authentication protocols Message
Digest 5 (MD5), Secure Hash Algorithm 1 (SHA1), and Secure Hash Algorithm 2 (SHA2) are supported. Privacy is
ensured by either the Data Encryption Standard (DES) or the Advanced Encryption Standard (AES) methods of
data encryption. Based on the security level, your customer defines passwords for authentication and for privacy.
SNMP is available for HPE Synergy, if HPE VC interconnects are used.
Quality of Service (QoS)

QoS settings within a LIG

Quality of Service (QoS) is a set of service requirements that the network must meet to ensure an adequate
service level for data transmission. The QoS provides a guaranteed delivery system for network traffic.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 20

The QoS feature helps to:

• Configure traffic queues for different network traffic, based on the priority
• Categorize and prioritize ingress traffic
• Adjust priority settings for egress traffic
Your customer can use these settings to ensure that important traffic is prioritized and handled first, before less
important traffic. After categorizing and classifying the network traffic, your customer can assign priorities and
schedule transmission.
QoS configuration is defined in the LIG and propagated to the LI. QoS statistics are collected by the
interconnects. On an HPE Synergy 12000 Frame, QoS configuration is available for the following interconnects:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
QoS configuration is only supported on VC Ethernet and VC FlexFabric interconnects on HPE BladeSystem
c7000 enclosures.
Uplink and downlink ports can be configured for ingress traffic classification, based on the values of dot1p,
Differentiated Services Code Point (DSCP), or both in the Ethernet and IP headers respectively.
Dot1p
Dot1p is a 3-bit field called the Priority Code Point (PCP) within an Ethernet frame header when using VLAN
tagged frames as defined by IEEE 802.1Q. Eight different classes of service are available as expressed through
the 3-bit PCP field.
DSCP
DSCP is a field in an IP packet that enables different levels of service to be assigned to network traffic.
DSCP and Dot1p
For IP traffic, use DSCP, and for non-IP traffic, use dot1p priority.
For an end-to-end QoS, all the hops along the way must be configured with similar QoS policies of classification
and traffic management.
In an end-to-end QoS policy, the traffic prioritization provides the following benefits:
• Greater bandwidth ensures a higher priority for the associated traffic in the queue. At the interconnect, the
packets are egressed based on the associated queue bandwidth
• Egress dot1p remarking helps to achieve priority at the next hops in the network. If the queue egress traffic is
remarked to a dot1p value, and that dot1p value is mapped to a queue in the next hops with higher bandwidth,
then the packets in the end-to-end network are treated with higher priority

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 21

NTP client and port flap protection

NTP and port flap protection settings within a LIG

HPE OneView provides the ability to configure the Network Time Protocol (NTP) client parameters through LIs.
The NTP client helps keep device clocks synchronized with that of an NTP server.
The configuration parameters include time zone, clock format, NTP client version, authentication algorithm, and
addressing mode.
Time adjustment and synchronization require authentication. Authentication allows NTP clients to verify that the
server is trusted. By default, authentication is disabled. Your customer must enable and configure the device to
authenticate the time sources to which the local clock is synchronized. NTP authentication works by using a key,
which is configured by the user. Your customer must configure the authentication algorithm, the value of which is
based on the authentication mode that they select.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 22

The following are the various modes and the supported authentication algorithms:
• Federal Information Processing Standards (FIPS) mode—SHA1 and SHA384
• Commercial National Security Algorithm Suite (CNSA) mode—SHA384
• Legacy mode—MD5, SHA1, and SHA384
Port flapping is a condition where network ports have gone down and come back up in quick succession. Stacking
ports and Link Aggregation Group (LAG) ports both have flap detection and notifications. These features are
available on the HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy and the HPE Virtual Connect SE 100
Gb F32 Module for HPE Synergy interconnects.
When LAG flapping is detected on uplink or downlink ports, or port flapping on stacking ports, the Interconnects
screen displays an alert. The alert lists the ports that triggered the port flapping. These alerts are cleared
automatically if the flapping is not detected for a predefined amount of time. Downlink ports must be associated
with a Virtual Port Link Aggregation Group (VPLAG) ID to detect if the LAG is flapping.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 23

Learning check
1. Which HPE Virtual Connect technology can be used to configure traffic queues for different network traffic,
based on priority?
A. IGMP
B. Port flapping
C. Quality of Service
D. LLDP tagging

2. Which statement about M-LAG setup is true?

A. In a multi-homed M-LAG configuration, downlink ports from HPE Virtual Connect are connected to a
single switch.
B. In a single-homed M-LAG configuration, uplink ports from HPE Virtual Connect are connected to different
switches.
C. LLDP tagging cannot be enabled if M-LAG is configured between HPE Virtual Connect modules in the
same frame.
D. A multi-homed M-LAG configuration provides a higher level of redundancy than a single-homed
M-LAG configuration.

3. Which technology control allows an administrator to suppress excessive inbound multicast, broadcast, and
destination lookup failure packets?
A. Private VLAN
B. Storm control
C. IGMP snooping
D. Pause flood protection

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 24

4. You are in a meeting with a customer, and they challenge you with a statement: “HPE Virtual Connect only
works with HPE Networking components and does not offer advanced functionalities like sFlow.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 25

HPE Synergy hardware setup process

HPE Synergy provides a simplified hardware setup process to speed up platform deployment.

Hardware installation and setup

HPE Synergy console

General steps involved with the on-site HPE Synergy installation:

• Building up the frame by inserting the compute, storage, fabric, and other components
• Connecting the fabric and management network cables
Additional steps for the installation technician:
• Access the Hardware Setup screen from the Synergy console
• Assign Composer IP addresses
• Complete hardware discovery
• Resolve any hardware setup errors
• Confirm inventory in HPE OneView
• Update system software

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 26

HPE Synergy Composer2

HPE Synergy Composer2 installed in the HPE Synergy frame

HPE Synergy Composer provides the enterprise-level management to compose and deploy system resources to
your customer’s application needs. The Composer management appliance uses software-defined intelligence from
embedded HPE OneView to aggregate compute, storage and fabric resources in a manner that scales to your
customer’s application needs, instead of being restricted to the fixed ratios of traditional resource offerings. This
capability to quickly match resources to workloads, and then to rapidly make changes, provides your customers
with infrastructure-as-code (IaC) control for integration, automation, and customization to meet their IT needs.
HPE Synergy Composer manages your customer’s hybrid cloud environment with IaC control. HPE Synergy
Composer2 is a key management appliance for the HPE Synergy solution, running an embedded version of HPE
OneView. At least one HPE Synergy Composer module must be installed (although it is highly recommended to
have two for redundancy). Based on an HPE ProLiant server, the HPE Synergy Composer2 management
appliance delivers an updated architecture with Unified Extensible Firmware Interface (UEFI) and HPE Integrated
Lights Out (iLO) 5.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 27

Initial HPE OneView setup using console access

HPE Synergy Console in an HPE Synergy frame

After installing and connecting the physical components of HPE Synergy to the data center, the on-site personnel
can connect to the HPE Synergy console using either a notebook computer or a video monitor, keyboard, and
mouse. The HPE Synergy console provides access to HPE OneView running on an HPE Synergy Composer
appliance. A connection can also be made to the CLI management consoles of non-VC interconnects.
When HPE Synergy hardware is properly installed and cabled, HPE OneView setup can be started:
1. Connect to the HPE Synergy Console using a laptop computer or a keyboard, video monitor, and mouse.
2. From the HPE Synergy Console, click Connect to start HPE OneView.
3. Click Hardware Setup.
4. Edit the HPE OneView networking settings.
5. Configure the hardware in HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 28

As hardware discovery proceeds, HPE OneView might detect errors in the configuration and operation of the
hardware. Errors are indicated with yellow or red icons. Clicking the device type in the discovered hardware list
allows your customer to drill down into problem areas to inspect the affected resource or device. Alerts often
provide recommended actions to take that are likely to correct the error. Examples of issues that your customer
can troubleshoot, using the hardware setup, include:
• Faulty hardware such as memory, processors, disks, fans, and power supplies
• High temperature conditions
• Backplane connector seating
• Component connectivity, such as:
– Link faults
– Mezzanine ports
– Interconnect module downlinks and uplinks
– Link module management port status
– Link module link ports
– Server hardware and interconnect module management processor port links
Zero Touch Provisioning, using DHCP, is available for HPE Composer2. The administrator can access an HPE
Synergy Composer2 appliance remotely to perform First Time Setup (FTS) and provision the HPE Synergy
hardware out of the box without physical access to the data center.
After connecting the frame link topology to the management network, each Composer2 is accessible through:
• A DHCP assigned address, if a DHCP server is on the network
• The IPv6 link-local address
After FTS is initiated, hardware discovery is performed, and your customer can access the appliance with the
address they configured for the appliance.
Before FTS is performed, there are three options to retrieve the IP address assigned to a Composer2:
• DHCP server
• Simple Service Discovery Protocol (SSDP)
• Maintenance console

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 29

Initial HPE OneView setup using VNC access

Accessing console through Virtual Network Computing (VNC)

When HPE Synergy hardware is properly installed and cabled, HPE OneView setup can be started:
1. Connect to the HPE Synergy Console using a laptop computer.
2. Wait for a Frame Link Module (FLM) to assign an IP address from DHCP.
3. Run VNC and connect to 192.168.10.1:5900.
4. Click Hardware Setup.
5. Edit the HPE OneView networking settings.
6. Configure the hardware in HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 30

Zero Touch Provisioning for HPE Composer2

Checking HPE Composer IP address using console

Zero Touch Provisioning for HPE Composer2 enables the HPE Synergy Composer2 to automatically retrieve an
IP address utilizing a DHCP server:
• IP address can be used to launch the provisioning process
• Only applies to HPE Synergy Composer2
After an IP address is assigned to HPE Composer, using remote access, the HPE Synergy startup process can be
performed.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 31

HPE Synergy hardware setup

Initializing hardware setup from the console connection

FTS is performed directly on the console interface of the HPE Composer. During the setup process, the FLMs
connect to the HPE Composer. HPE Composer automatically discovers all hardware in its management domain
during the hardware setup phase. The FLMs provide details on the status and resources available in the frame or
multiple linked frames, and HPE Composer shows the startup screen.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 32

HPE Synergy hardware discovery process

After hardware discovery is complete and the HPE OneView networking is configured, all remaining management
operations should be performed by using a supported browser connection to HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 33

Activity: HPE OneView setup, configuration, and interoperability

Hardware discovery in HPE OneView

Participants will work by themselves on this activity. HSP has challenged you with some questions regarding HPE
OneView setup, configuration, and interoperability. Answer the following questions:
1. How is HPE OneView used to manage the deployed HPE Synergy platform?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. How can the HPE Composer CLI be accessed?

__________________________________________________________________________________________________________

3. How can a forgotten password be reset?

__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 34

4. If HPE OneView on an HPE Synergy system becomes corrupted, how can it be recovered?
__________________________________________________________________________________________________________

5. How often should hardware discovery be used to refresh hardware information?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

6. Can a single HPE Superdome Flex be managed, using HPE OneView running on the Synergy Composer?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

7. What are the benefits of HPE Composer2?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 35

Learning check
5. You are in a meeting with a customer, and they challenge you with a statement: “Initial setup of HPE Synergy
always requires a technician present on site. We have many remote offices and having a technician available
can be quite difficult. It will delay the deployment process.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 36

Configuring HPE Synergy components

HPE Synergy configuration is performed using HPE OneView.

HPE Synergy configuration flow

Configuration steps in the HPE OneView main menu

After initial configuration of HPE OneView is finished, the administrator can start logical configuration. Not all of
the steps are mandatory and depend on the hardware platform that will be managed using HPE OneView.
High-level steps that an administrator takes to configure HPE OneView are:
1. Create IP address pools for management. The management network and IP pool associated with this network
is an optional component if HPE Image Streamer is not a part of the solution. The management network can
be used to assign IP addresses for Integrated Lights-Out (iLO) and interconnects modules (if applicable),
when HPE Image Streamer is not used.
2. Creating networks and network sets involve creating a management network that is associated with the
subnets containing the address pools created in the previous step. Networks and network sets can also be
created for presenting software-defined networking VLANs to the compute modules via server profiles.
Media types supported are Ethernet, FC, and FCoE and RoCE. In addition, network sets can be established.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 37

3. To enable the automated zoning feature, the administrator can integrate HPE OneView with a supported
SAN manager. This is also an optional step. If a customer does not have HPE Storage managed using HPE
OneView, or storage is connected directly to HPE Synergy, an external SAN manager is not required.
4. Import storage components such as HPE Primera, HPE Alletra, HPE 3PAR StoreServ, HPE Nimble storage, or
Virtual Storage Appliance (VSA) clusters. Depending on the storage type used, your customer may also
import any existing logical unit numbers (LUNs) and storage pools.
5. Create LIGs. This step involves creating a configuration template for ICMs. There are three types of LIGs,
categorized by media type:
a. FCoE/Ethernet
b. Native FC
c. Serial Attached SCSI (SAS)
6. Create enclosure groups. Enclosure groups allow admins to combine multiple types of LIGs into an extended,
rack-scale fabric architecture. For example, one enclosure group could contain a SAS fabric for the HPE
Synergy D3940 Storage Module and VC master/satellite modules for network connectivity, and another
enclosure group could contain VC master/satellite modules and discrete Virtual Connect FC modules for
dedicated FC connectivity. Multiple enclosure group designs can be managed by a single Synergy Composer
domain. Enclosure groups should be created for any unique hardware or logical configuration.
7. Create logical enclosures. Logical enclosures are created when the intended design of the enclosure group
and its LIG are applied to physical frames. The Synergy master/satellite fabric capabilities enable multiple
frames to be combined in a logical enclosure. Logical enclosures may have from one to five frames.
8. Create server profiles and templates. Server profiles define the identity of the servers. To simplify the
creation and change management process, a server profile template can be created and used for server
profile provisioning.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 38

Creating IP address pools

Creating IP address pools using HPE OneView

Use an IPv4 or IPv6 address pool in a variety of applications:

• Create an IPv4 or IPv6 subnet with one or more IPv4 or IPv6 address ranges your customer defines. To assign
static IP addresses to device bays, associate these IP ranges with an enclosure group, in which case IP
addresses are assigned to the iLO of the server hardware populating these bays. IP ranges are also associated
with interconnect bays, in which case IP addresses are assigned to the ICMs. Interconnects and iLOs share the
same IP address pool
• Associate an IPv4 or IPv6 subnet with an Ethernet or RoCE network. If this is an Internet Small Computer
Systems Interface (iSCSI) network used as a deployment network, HPE Synergy Image Streamer appliances can
consume an IP address from one of the ranges for management of the appliance
Important restrictions when configuring IP pools include:
• Your customer cannot use IPv4 addresses in the reserved range of 172.30.254.0 to 172.30.254.255. HPE
OneView uses this range on an internal, private VLAN within the enclosure domain
• For Image Streamer, assign IPv4 addresses as deployment addresses (iSCSI initiators) for servers to boot from
their OS volumes hosted on Image Streamer appliances
• IPv6 does not support loopback, multicast, and link-local addresses

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 39

Creating networks and network sets

HPE OneView enables the definition of network and networks sets.
Creating networks in HPE OneView

Adding a network using HPE OneView

HPE OneView networks define connections that route data across the IT infrastructure. Your customer can create
a single Ethernet, RoCE, FC, or FCoE network, a multiple tagged Ethernet, or RoCE networks at one time. To
define a network:
1. From the HPE OneView main menu, select Networks.
2. Click + Create network.
3. Select the network type, and provide the required information.
A management network is a special type of network available only for HPE Synergy, and it can be used to assign
IP addresses to iLOs and ICMs.
Full network management using HPE OneView is available only when VC modules are used.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 40

Creating Ethernet networks

Creating an Ethernet network using HPE OneView

When creating an Ethernet network, the following parameters must be defined:

• Name—A unique name for the network
• Type—Select Ethernet as the network type
• VLAN—Three types are available:
– Tagged—A tagged Ethernet network contains multiple networks on a single uplink set that allows your
customer to share uplinks with those networks. A tagged network uses VLANs, allowing multiple networks to
use the same physical connections. By sharing physical uplinks, your customer can separate traffic streams
from different servers, using the same set of uplinks. Tagged Ethernet and FCoE networks that are connected
to enclosure interconnects require a VLAN ID. A VLAN ID is an integer ranging from 2 to 4094. When editing
a tagged Ethernet or an FCoE network, the VLAN ID is displayed. If your customer does not know which
VLAN IDs have been assigned, they should contact their network administrator. Each network name in the
appliance must be unique. For tagged Ethernet networks, your customer can enter a combination of values or
ranges to add networks in bulk, for example: 113, 114, 200 to 300
– Untagged—An untagged Ethernet network is a single network with a dedicated set of uplink ports used to
pass traffic without VLAN tags. Any tagged packets are dropped. Forwarding is done by MAC address. Your
customer might want to configure an untagged network for iSCSI storage traffic or to set up networks
without configuring VLANs

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 41

– Tunnel—A tunnel network is a single dedicated network with a dedicated set of uplink ports used to pass a
group of VLANs without changing the VLAN tags. Your customer can have a tunnel network with a maximum
of 4094 VLANs
• VLAN ID—The VLAN ID number assigned to a network, entered as a single value. For tagged Ethernet
networks, your customer can enter a combination of values or ranges to add networks in bulk
• Associate with subnet ID—For both tagged and untagged Ethernet networks, lists all subnets not currently
associated with any VLAN. If the selected VLAN ID is already used by another network, and there is an
associated subnet, it lists only the configured subnet. Subnet IDs cannot be assigned when a valid VLAN ID is
not specified or when creating networks in bulk. When editing a network with an associated subnet, if the
associated subnet is changed, validation will fail if any IP addresses are in use in the current subnet
• Purpose—A description to attach to a network to help categorize the purpose of the network: General,
Management, VM Migration, iSCSI, and Fault Tolerance. Changing this parameter does not affect the behavior
of the network
• Preferred bandwidth—The preferred bandwidth, in Gb/s, for the network when the preferred bandwidth is
configured on a port in a server profile. Your customer can override this setting in a server profile. This value
cannot be greater than the maximum bandwidth
• Maximum bandwidth—The maximum bandwidth for a connection to the selected network, in Gb/s, when the
selected network is configured on a port in a server profile. The maximum bandwidth defines the upper limit for
the requested bandwidth allocation setting when the network is associated with a server profile. This value
cannot be less than the preferred bandwidth. The maximum bandwidth for a single physical port cannot exceed
the maximum adapter speed
• Smart Link—Smart Link enables the server software to detect and respond to a loss of network connectivity
on the interconnect uplink ports. Smart Link causes the operating system to detect a failure, and to direct
traffic to an alternative path. With Smart Link enabled, the VC interconnects will drop the Ethernet link on all
server connections associated with the network if all uplink ports within an uplink set lose their connection to
the data center switches. Smart Link can be helpful when using certain server network teaming (bonding)
policies. Smart Link is only required and effective in the non-redundant A/B side configurations. It has no effect
on high availability or redundant configuration where both ICMs are in the same LI, and M-LAG is in use. If a
server profile connection contains network sets with both Smart Link and non-Smart Link-enabled networks, no
Smart Link processing occurs. This means that the profile connection always remains linked, even if uplink
connectivity is lost for the Smart Link enabled networks. If a server profile connection contains network sets
with only Smart Link enabled networks, and if all the uplink connectivity is lost for the networks in the network
set, the server profile connection becomes unlinked due to Smart Link. The warning message indicates the
reason for loss of connectivity. When using Smart Link-enabled networks within a network set, HPE
recommends that all the networks in the network set must be a subset of the configured networks in an uplink
set in the LI
• Private network—A private network is available for Ethernet and RoCE networks only. The private network
feature provides additional network security by limiting traffic flow for the given network. Since the server
ports in a private network cannot communicate with each other within the LI, all server packets are sent
through the LI and out the uplink ports
Optionally, a network can be added to a network set. It can be done when creating the network or later on.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 42

Various types of Ethernet networks

An example of HPE Virtual Connect network types

The graphic above presents various types of networks and the correlation between different networking
components. An internal network is a network that does not have any uplinks and can be used for traffic, such as
vSAN or fault tolerance, assuming that traffic does not leave the frame or enclosure.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 43

Creating Fibre Channel networks

Creating an FC network using HPE OneView

When creating an FC network, the following parameters must be defined:

• Name—A unique name for the network. Follow best practices for network naming conventions
• Type—Select Fibre Channel as the network type
• Fabric type—The VC interconnects in enclosures support the following types of FC networks when connecting
to storage systems:
– Fabric-attach networks—The enclosure interconnects connect to data center SAN fabric switches. SAN
infrastructures typically use an FC switching solution, involving several SAN switches that implement N-Port
ID Virtualization (NPIV) technology. NPIV uses N-ports and F-ports to build an FC SAN fabric. NPIV enables
multiple N_Ports to connect to a switch through a single F_Port, so that a server can share a single physical
port with other servers, but access only its associated storage on the SAN. When your customer configures a
fabric-attach FC network, the port they choose for the uplink from the enclosure interconnect to the storage
SAN must support NPIV

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 44

– Direct-attach networks—Also called Flat SAN, in which the enclosure interconnects connect directly to a
supported storage system. The direct-attach FC solution eliminates the need for a connection from the
enclosure interconnects to an FC SAN switch. This means your customer can connect the enclosure
interconnects directly to the FC SAN storage system. Servers connecting to a direct-attach FC network have
access to all devices connected on the uplink ports defined for that network. If there is more than one
connection from an interconnect to the storage system, each server can access as many paths to the storage
LUN as there are connections to the FC SAN storage system. For direct-attach FC networks, the enclosure
interconnect does not distribute server logins across uplink ports. Server login distribution does not apply to
direct-attach FC networks
Your customer cannot change the type of FC network, but they can delete the network in HPE OneView, and
then add the network as a different type.
• Associated SAN—The managed SAN to associate with this network. If selected, automatic zoning occurs as
well as end-to-end connectivity verification. Automatic zoning connects a server profile on this network to its
storage. If your customer edits the network and changes the association to a different SAN, they must confirm
the change
• Preferred bandwidth—For FC networks, this value is not applicable. The connection speed defaults to Auto
• Maximum bandwidth—For FC networks, the maximum bandwidth is not applicable
• Login redistribution—Used for login balancing when logins are not distributed evenly over the FC links (for
example, when an uplink that was down becomes available). Two modes are available:
– Auto—Login redistribution is initiated automatically when the link stability time expires
– Manual—Login redistribution must be initiated manually
The HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy and the HPE Virtual Connect SE 100 Gb F32
Module for HPE Synergy uplinks only support auto-login redistribution. For these modules, FC networks are
allowed to be configured as Manual, but are treated as Auto. HPE Virtual Connect FC Modules support both
Auto and Manual login redistribution.
• Link stability interval—The link stability interval is enabled when Login redistribution is set to Auto. The link
stability interval is the time interval, in seconds, before login redistribution occurs (when it is set to Auto). HPE
VC FC Modules have a default value of 30 seconds and a supported range of 5 to 1800 seconds. The time
reflects how long, in seconds, that the module waits before reconnecting to a link that was previously offline
(login redistribution). This interval prevents connection loss due to reconnecting to a link that is unstable
(going online and offline repeatedly).

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 45

Creating FCoE networks

Creating an FCoE network using HPE OneView

When creating an FCoE network, the following parameters must be defined:

• Name—A unique name for the network
• Type—Select FCoE as the network type
• Associated SAN—The managed SAN to associate with this network. If selected, automatic zoning occurs, as
well as end-to-end connectivity verification. Automatic zoning connects a server profile on this network to its
storage. If your customer edits the network and changes the association to a different SAN, they must confirm
the change
• VLAN ID—The VLAN ID number assigned to a network, entered as a single value
• Preferred bandwidth—For FCoE networks, this value is not applicable. The connection speed defaults to Auto
• Maximum bandwidth—For FCoE Channel networks, the maximum bandwidth is not applicable

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 46

Creating RoCE networks

Creating an RoCE network using HPE OneView

RDMA over Converged Ethernet (RoCE) is a network protocol that enables remote direct memory access (RDMA)
over an Ethernet network. RoCE networks are, by default, tagged networks. RoCE networks are data networks
and used in all RDMA use cases. The Smart Link and private network features are available on RoCE networks.
RoCE networks are, by default, Smart Link enabled. RoCE networks in HPE OneView are used in connections,
network sets, internal networks, and uplink sets. RoCE networks are automatically configured for lossless transit
from the server adapters to the uplink sets containing the RoCE network.
An RoCE network is supported on the following interconnects:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
RoCE networks enable lossless networking on the supported interconnects for HPE J2000 Flash Enclosure
support. RoCE networks help your customer to configure low latency data access to NVMe over Fabrics
(NVMeoF) storage for shared data access. RoCE networks also help your customer to configure cluster computing
use cases, such as SharePoint deployment or VM migrations across hypervisors.
RoCE networks cannot be used for sFlow, Private VLAN (PVLAN), MVLAN, and remote port monitoring purposes.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 47

When creating an RoCE network, the following parameters must be defined:

• Name—A unique name for the network
• Type—Select RoCE as the network type
• VLAN ID—RoCE networks are, by default, tagged networks
• Preferred bandwidth—The preferred bandwidth, in Gb/s, for the network when the preferred bandwidth is
configured on a port in a server profile. Your customer can override this setting in a server profile. This value
cannot be greater than the maximum bandwidth
• Maximum bandwidth—The maximum bandwidth for a connection to the selected network, in Gb/s, when the
selected network is configured on a port in a server profile. The maximum bandwidth defines the upper limit for
the requested bandwidth allocation setting when the network is associated with a server profile. This value
cannot be less than the preferred bandwidth. The maximum bandwidth for a single physical port cannot exceed
the maximum adapter speed
• Private network— A private network is available for Ethernet and RoCE networks only. The private network
feature provides additional network security by limiting traffic flow for the given network. Since the server
ports in a private network cannot communicate with each other within the LI, all server packets are sent
through the LI and out the uplink ports
Optionally, an RoCE network can be added to a network set.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 48

Creating network sets

Creating a network set in HPE OneView

A network set is a collection of tagged Ethernet networks that form a named group to simplify server profile
creation. Network sets are useful in virtual environments where each server profile connection needs to access
multiple networks. The Network Sets screen displays the network sets currently defined in HPE OneView.
Network sets are aggregated networking objects that contain networks. A network set is an object your customer
can assign to network connections within server profiles to greatly simplify multiple network configuration
management tasks. Use network sets in server profile connections to make all networks on a connection's
downlink port available. Network sets define how packets are delivered to the server when a server Ethernet
connection is associated with the network set. Network sets also enable your customer to define a VLAN trunk,
and associate it with a server connection.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 49

From the Network Sets screen, your customer can view the details of network sets, and create, edit, and delete
network sets. The preferred bandwidth setting of a network set can be overridden by a server profile. Changing
this value for a network set does not affect the server profiles that are overriding it. Instead of assigning a single
network to a connection in a server profile, your customer can assign a network set to that connection.
Using network sets, your customer can quickly deploy changes to the network environment to multiple servers.
For example, your customer has 16 servers connected to a network set. To add a new network to all 16 servers,
they only need to add it to the network set, instead of adding it to each server individually.
Your customer can create a network set for their production networks, and one for their development network.
Network set requirements
A network set has the following requirements:
• All networks in a network set must be Ethernet and/or RoCE networks and must have unique external VLAN
IDs. Untagged and tunnel networks are single networks and do not use network sets. An untagged network is
designated for untagged packets. One network in a network set can be untagged
• All networks in a network set must be configured in the same appliance
• A network can be a member of multiple network sets
• All networks in a network set must be added to uplink sets or internal networks in the LIG (and its LIs) to be
used in server profiles with connections to the LI
• A network set can be empty (contain no networks) or can contain one or more of the networks configured in
the LIG and LI. Empty network sets allow your customer to create network sets in the configuration before they
create the member networks, or to remove all the member networks before they add their replacements.
However, if a server profile adds a connection to an empty network set, the server cannot use the connection to
connect to any data center network. A network can be added to the network set manually or when the network
is created
Network set types
There are two types of network sets: Regular and Large. Your customer can select either a Regular or Large
network set type. Your customer can deploy a Large network set when using the HPE Virtual Connect SE 100 Gb
F32 Module for HPE Synergy.
Regular network sets can contain up to 1000 networks. Large network sets can contain up to 4094 networks
minus the number of networks that are in the reserved VLAN range, which can range from 60 to 128 networks.
The default is 128 networks. Generally, the maximum number of networks is 3966 networks. A maximum of 60
distinct large network sets can be simultaneously deployed per LI.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 50

Learning check
6. Which statement about login redistribution is true?
A. Login redistribution is used for login balancing when logins are not distributed evenly over the Fibre
Channel links.
B. Login redistribution on the HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy can only be
configured to manual mode.
C. Login redistribution is supported only on the HPE Virtual Connect SE 100 Gb F32 Module for HPE
Synergy.
D. Login redistribution is only supported for one logical enclosure per HPE OneView instance.

7. Which statement about Smart Link is true?

A. Smart Link can be configured for Ethernet and FC networks, but not for FCoE.
B. Smart Link requires an additional license and can be enabled per logical enclosure.
C. Smart Link is only required and effective in nonredundant A/B-side configurations.
D. Smart Link is only supported for the HPE Synergy platform with non-Virtual Connect modules.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 51

Creating logical resources: Logical interconnect groups

HPE OneView supports many logical resources, such as LIGs, LIs, enclosure groups, and logical enclosures.
Creating logical interconnect groups

A LIG for HPE Virtual Connect 100 Gb/F32 modules

A LIG acts as a recipe for creating a group that represents the available networks, uplink sets, and interconnect
settings for a set of physical interconnects in a set of enclosures.
There are several kinds of LIGs:
• A multiple-enclosure LIG must match the interconnect link topology within the set of linked enclosures. All bays
must be properly populated in all enclosures in the interconnect link topology. A multiple-enclosure LIG must
include an HPE Virtual Connect SE 40 Gb F8 Module for Synergy and/or an HPE Virtual Connect SE 100 Gb
F32 Module for HPE Synergy and the Interconnect Link Module configuration
• Single-enclosure LIGs, such as a SAS LIG, pertain only to the enclosure in which they are applied. A single-
enclosure LIG can be applied to individual bays in individual enclosures in the interconnect link topology.
Virtual Connect SE FC modules support single-enclosure LIGs
Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 52

LIG for a Virtual Connect SE 40 Gb F8/100 Gb F32 Module

Logical interconnect group definition for VC SE modules

A LIG for Synergy Virtual Connect SE 40 Gb F8/100 Gb F32 Modules defines:

• Enclosure count—This parameter defines the number of frames stacked in the master/satellite configuration.
An administrator can select between one to five frames. If 10 Gb/25 Gb connectivity is planned, your customer
can stack up to five frames together. When 20 Gb/50 Gb connectivity is selected, your customer can stack up
to three frames together. Also, configurations with mixed speed of satellite modules are allowed
• Interconnect bay set—This parameter defines the fabric used for VC modules. According to best practices,
they should be placed in the third fabric, but other fabrics support VC modules as well

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 53

• Redundancy—If there is failure, redundancy is used to prevent loss of connectivity. An interconnect is

duplicated, so if it fails, a backup interconnect is available. HPE OneView automatically sets the redundancy,
based on the redundancy of the original LIG and the enclosure count. HPE OneView uses the following modes
of redundancy:
– Highly available—Two interconnects on opposite sides of two enclosures that are both available to all
enclosures, connected with Interconnect Link Modules. This configuration allows for the loss of any single
interconnect or enclosure without affecting connectivity of the remaining enclosures
– Redundant—The same interconnect type on both sides of a single enclosure. This configuration allows for
the loss of the interconnect on one side without affecting connectivity of the enclosure. The loss of the
interconnects on both sides causes the enclosure to lose connectivity
– Non redundant side A—One interconnect in a single-side A bay (1, 2, or 3) in an enclosure that can be
connected to other enclosures that have an Interconnect Link Module in the same bay. Loss of any
interconnect results in loss of connectivity
– Non redundant side B—One interconnect in a single-side B bay (4, 5, or 6) in an enclosure that can be
connected to other enclosures that have an Interconnect Link Module in the same bay. Loss of any
interconnect results in loss of connectivity
• Uplink set configuration—An uplink set is an association between network and interconnect uplink ports. The
following types of uplink sets are supported:
– Ethernet—An Ethernet uplink set contains multiple networks on a single uplink set, which allows your
customer to share uplinks with those networks. Ethernet is also used for FCoE networks and for a single-
frame Image Streamer configuration
– Fibre Channel—An FC uplink set contains a single network used for storage
– Tunnel—A tunnel uplink set contains a single Ethernet tunnel network with a dedicated set of uplink ports
used to pass a group of VLANs without changing the VLAN tags
– Untagged—An untagged uplink set contains a single untagged Ethernet network with a dedicated set of
uplink ports used to pass untagged traffic (without VLAN tags)
– Image Streamer—An uplink set with only one network and four uplink ports to support a multiframe, Image
Streamer appliance when used for an internally connected deployment network. A single-frame Image
Streamer configuration that is not supported in a production environment requires an Ethernet connection
• Advanced VC settings—Advanced VC settings include storm control, loop protection, QoS, IGMP, and so on

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 54

Creating uplink sets within logical interconnect groups

Different type of the uplinks for HPE Synergy

An uplink set defines a single, dedicated network or a group of networks and physical ports on a set of
interconnects in an enclosure. An uplink set enables your customer to attach the interconnects to their data
center networks. An uplink set enables multiple ports to support port aggregation (multiple ports connected to a
single external interconnect) and link failover with a consistent set of VLAN networks. For the HPE Synergy
platform with three frames minimum and HPE Image Streamer installed, a special type of uplink can be defined.
An uplink set is part of an LI. The initial configuration of the uplink sets for an LI is determined by the
configuration of the uplink sets for the LIG, but your customer can change (override) the uplink sets for a specific
LI.
Changes your customer makes to the uplink sets for a LIG are not automatically propagated to existing LIs. For
example, to propagate a newly added VLAN to a LIG uplink set to its existing LIs, your customer must individually
update each LI configuration from the LIG.
When defining uplink sets, the following rules apply:
• For tagged Ethernet networks and RoCE networks, an uplink set enables your customer to identify interconnect
uplinks that carry multiple networks over the same cable
• For untagged or tunnel Ethernet networks, an uplink set identifies interconnect uplinks that are dedicated to a
single network

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 55

• For FC networks, your customer can add one network to an uplink set. FC does not support virtual networks or
VLANs
• For FCoE networks, an uplink set enables your customer to carry multiple FC and tagged Ethernet networks
over the same set of Ethernet cables
• RoCE networks cannot be marked as native in the uplink sets
• The total number of ports that your customer can assign to uplink sets or use as a network analyzer port
cannot exceed 12 ports per interconnect for the following modules:
– HPE Virtual Connect SE 16 Gb FC Module for Synergy
– HPE Virtual Connect SE 32 Gb FC Module for Synergy

Creating an Ethernet uplink set

For Ethernet interconnects with an automatic connection mode, LACP aggregates as many ports in the uplink
port group as possible into a LAG. As part of the LACP negotiation to form a LAG, the interconnect sends a
request for the frequency of control messages. Your customer can set this frequency through the LACP timer.
The frequency can be:
• Short—Every one second with a three-second timeout
• Long—Every 30 seconds with a 90-second timeout
Your customer should use the Long setting to prevent a timeout and loss of communication during an external
switch firmware upgrade. Your customer should set the LACP timer when they create a LIG, or change the timer
when they add or edit an uplink set.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 56

The HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy and HPE Virtual Connect SE 100 Gb F32 Module
for HPE Synergy provide many LACP load-balancing options for an uplink set. The LACP load-balancing
configuration is available only for uplink sets created using one of the following network types:
• Ethernet
• Tunnel
• Untagged
The configuration enables distribution of the Ethernet traffic among all the uplink ports in an uplink set,
depending on the hash value created out of the hash key fields. During traffic transmission, apart from the
selected value, other fields, such as VLAN, EtherType, and so on are also considered. The table below lists the
various LACP load-balancing options available, and the related hash keys for each value.

LACP load-balancing value Hash key fields

Source and destination MAC Source/Destination MAC + VLAN + EtherType + source module ID/port
address
Destination MAC address Destination MAC + VLAN + EtherType + source module ID/port
Source MAC address Source MAC + VLAN + EtherType + source module ID/port
Destination IP address Destination IP + destination UDP/TCP port
Source IP address Source IP + source UDP/TCP port
Source and destination IP address Source IP/destination IP + source/destination TCP/UDP port

HPE OneView selects the source and destination MAC address values by default. Your customer can configure
the LACP load-balancing option, either while creating a logical enclosure in the LIG or while editing an LI.
LACP failover trigger
Your customer can configure the LACP failover trigger to set the threshold for triggering LACP load balancing:
• All active uplinks transition to offline—This is the default setting. A failover is triggered when all active
uplink ports are offline
• Active uplink bandwidth below threshold—A failover is triggered when the active uplink bandwidth reduces
below the threshold and/or the standby uplink bandwidth increases above the threshold. Enter the bandwidth
threshold percentage to trigger the failover. The default is 50%
• Active uplink count below threshold—A failover is triggered when the number of uplinks in the active LAG is
reduced below the threshold. When both active and standby LAGs do not satisfy the minimum uplink criteria, a
failover is triggered the same as when all active uplinks transition to offline

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 57

LIG for Synergy Virtual Connect FC modules

LIG definition for VC-FC modules for HPE Synergy

A LIG for HPE Synergy Virtual FC modules defines:

• Enclosure count—When defining a LIG for HPE VC-FC modules, it is always 1, as FC modules do not support
stacking like Ethernet modules
• Interconnect bay set used—According to best practices, modules are placed in the second fabric—
interconnects 2 and 5, but if SAS connectivity is not used, FC connectivity works in the first fabric. Note that a
second CPU is required to be used in mezzanine 2
• Redundancy—Because VC-FCs do not span multiple frames, redundancy modes are the same as for HPE VC
SE modules, except they provide a highly available option
• Uplink set configuration for FC networks—Uplink sets associate FC networks with uplink ports, but for a
single uplink set, your customer can use only uplink ports from a single module
Uplinks on a single ICM may be added to an uplink set and trunked together at the SAN switch.
The HPE Virtual Connect SE FC Module for HPE Synergy trunk capability allows for the formation of a single
trunk for multiple ports connected from such a module to a Brocade ToR switch. Trunks allow for improved traffic
flow to and from the servers in the enclosure and the data center SAN fabric, as well as nondisruptive failover for
port faults.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 58

The following HPE Virtual Connect FC Modules support trunking:

• HPE Virtual Connect SE 16 Gb FC Module for HPE Synergy
• HPE Virtual Connect SE 32 Gb FC Module for HPE Synergy
Creating a LIG for Synergy SAS modules

Creating a LIG for SAS modules in HPE OneView

A LIG for HPE Synergy SAS modules defines:

• Enclosure count (always is 1, as SAS modules do not support stacking like Ethernet modules)
• Interconnect bay set used (only first fabric can be used—interconnects 1 and 4; single module is also
supported)
• There are no uplinks to configure

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 59

Learning check
8. Which parameters can be configured when defining a logical interconnect group for 12 Gb SAS switches?
A. Number of SAS switches
B. Interconnect bay location
C. Number of the frames
D. Up to four uplink sets

9. What is the difference between high-availability and redundant configurations within a LIG for a Virtual
Connect SE 40 Gb F8/100 Gb F32 Module?
A. A redundant setup requires at least four VC modules, while a high-availability setup requires two VC
modules in the same frame.
B. In a high-availability setup, both VC modules are installed in different frames, but in a redundant setup,
both are in the same frame.
C. A redundant setup is supported if sFlow is enabled for Virtual Connect SE 100 Gb F32, and both modules
are in different fabrics.
D. A redundant setup is supported only with Virtual Connect SE 100 Gb F32 modules and requires an
additional license.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 60

Creating logical resources: Enclosure groups

To properly set up HPE Synergy frames, an enclosure group must be defined.
Creating an enclosure group

Creating an enclosure group for HPE Synergy

An enclosure group specifies a standard configuration for all its member logical enclosures. Enclosure groups
enable administrators to provision multiple logical enclosures in a consistent, predictable manner. 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. The network connectivity for an enclosure group is defined by the LIGs associated with the
enclosure group. An enclosure group can contain up to five enclosures.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 61

An enclosure group for HPE Synergy frames defines:

• Enclosure count: This number must match the LIG and physical configuration
• iLO and interconnect configuration method:
– Use address pool—Each interconnect and management processor that requires an IP address is allocated
from the configured IP address pools
– Use DHCP—Each interconnect and management processor that requires an IP address is configured to
obtain that address through a DHCP
– Manage externally—Configuration of IP addresses is managed outside of HPE OneView
• Image Streamer network type:
– None—The enclosure group does not have OS deployment configured
– Internal—A multiframe Synergy Image Streamer configuration is in use. The Synergy Image Streamer
appliance is directly connected to a VC interconnect. The OS deployment network is assigned to the Image
Streamer uplink set in one of the LIGs for this enclosure group
– External—A single-frame Synergy Image Streamer configuration is in use. In this configuration, there is one
HPE Composer and one HPE Image Streamer installed. This kind of configuration can be used only for
demonstration/testing/proof of concept purposes and should not be used in a production environment
because of missing redundancy for management appliances
• Interconnect bay configuration—Assignment of the LIGs to the interconnect bays:
– SAS and FC are defined per frame
– Ethernet is defined for all frames stacked together

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 62

Creating logical resources: Logical enclosures

A logical enclosure for HPE Synergy must be created before server profiles can be defined.
Creating a logical enclosure

Creating a logical enclosure in HPE OneView

A logical enclosure contains the configuration intended for a set of physical enclosures. Its default values are
taken from the enclosure group and applied to the physical enclosures. If the intended configuration in the logical
enclosure does not match the actual configuration on the enclosures, the logical enclosure becomes inconsistent.
A logical enclosure defines:
• Association of stacked frames with an enclosure group. Frames with HPE Synergy VC master and satellite
modules are automatically associated through their master/satellite cabling and become candidates for
enclosure groups that contain master/satellite modules
• Firmware baseline, if a Support Pack for ProLiant (SPP) is uploaded to HPE OneView repository
• Static IP address assignments that override the enclosure group address assignment choice

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 63

Growing a logical enclosure

The HPE Synergy grow functionality enables administrators to increase the compute capacity by adding
enclosures to a HPE Synergy logical enclosure, without interrupting the network traffic. The grow functionality is
applicable only for growing the VC Network LI portion of a logical enclosure. An administrator can physically grow
their HPE Synergy configuration from a single frame to a maximum of five HPE Synergy frames, using
Interconnect Link Modules. With HPE OneView, the logical growth occurs by growing the logical enclosure. The
HPE Synergy frames are added to the logical enclosure by associating a new enclosure group with the logical
enclosure and performing an update from the group. HPE OneView completes the change without disassociating
frames from existing logical enclosures or causing an outage to the existing environment.
When physically growing to two or more frames, your customer must use the same model of Interconnect Link
Modules in a bay set. The maximum speed of all downlinks in that bay set is based on the speed of the
Interconnect Link Modules being used, as well as the speeds of the mezzanine cards in the attached servers. For
example, if the HPE Synergy 10 Gb Interconnect Link Module is used, then the maximum speed of all downlinks in
that LI is 10 Gb.
HPE Synergy frames configured to support HPE Synergy Image Streamer can grow from a three to a four- or
five-frame configuration. Your customer can grow a single-frame redundant configuration up to five frames
redundant, or a highly available configuration, depending on the interconnect models inserted in each bay set.
When your customer attempts to grow into an unsupported configuration, HPE OneView returns an error with
hints to help rectify the errors.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 64

Logical interconnects

LI not consistent with LIG

An LI 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 group of Synergy frames cabled together with one instance of HPE
OneView to manage all the resources in the group).
A LIG serves as a template to ensure that the LIs being created are configured consistently. An LI is a single
administrative entity that consists of the configuration for a set of interconnects in a single enclosure or a frame
link topology, and includes:
• The uplink sets, which connect to data center networks
• The mapping of networks to physical uplink ports, which is defined by the uplink sets for an LI
• The internal networks, which are used for server-to-server communications without traffic egressing any
uplinks
• The downlink ports, which connect through the enclosure midplane to the servers in the enclosure
• The connections between interconnects, which are called stacking links (stacking links are external cables
between the external ports of interconnects)

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 65

For a server administrator, an LI represents the available networks through the interconnect uplinks and
the interconnect downlink capabilities through a physical server interface. For a network administrator,
an LI represents an Ethernet stacking configuration, aggregation layer connectivity, stacking topology, network
reachability, statistics, and troubleshooting tools.
LIs are created automatically during logical enclosure setup. Changing the LIG setup makes the LIs configured,
using this LIG, inconsistent. Configuration changes made to a LIG are not automatically propagated to the
member LIs. However, by changing the LIG, your customer can update each LI with a single action.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 66

Activity: Logical interconnects

Sample logical interconnect group for SAS switches

Participants will work by themselves on this activity. Review the list of HPE Synergy components that your
customer has purchased, and then, and answer the questions below:
Your customer’s HPE Synergy components:
• 3 x HPE Synergy 12000 Frame
• 2 x HPE Virtual Connect SE 100 Gb F32 Module for Synergy
• 4 x HPE Synergy 50 Gb Interconnect Link Module
• 4 x HPE Synergy Virtual Connect SE 32 Gb FC Module
• 2 x Brocade 32 Gb Fibre Channel SAN Switch Module for HPE Synergy
• 4 x HPE Synergy 12 Gb SAS Connection Module
• 2 x HPE D3940 Storage Module
• 32 x HPE Synergy 480 Gen10 Plus compute modules with SAS controller

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 67

Answer the following questions:

1. How many logical enclosures can be configured for the given set of components?
__________________________________________________________________________________________________________

2. How many logical interconnects will be created for a given logical enclosure?
__________________________________________________________________________________________________________

3. How many logical interconnect groups are needed, assuming all VC-FC modules, SAS switches, and Brocade
switches have the same configuration?
__________________________________________________________________________________________________________

4. Are there any configuration changes that you would recommend to the customer? Justify your
recommendation.
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 68

Learning check
10. You are in a meeting with a customer, and they challenge you with a statement: “We plan to deploy multiple
HPE Synergy frames with the same configuration, but we are afraid that changing the uplink set for all of
them will be time consuming.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 69

Automation with REST API and PowerShell scripting

HPE OneView provides automation through a REST API and PowerShell Library for HPE OneView.

HPE OneView resource model

Resources in HPE OneView

HPE OneView manages resources using resource managers. A resource is an object that your customer can
interact with through a GUI or other tools, like the REST API or PowerShell scripts.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 70

HPE OneView REST operations

REST API operations

HPE OneView has a resource-oriented architecture that provides a uniform REST interface. Every resource has
one Uniform Resource Identifier (URI) that represents a physical device or logical construct. Your customer can
use REST APIs to list, create, modify, and delete HPE OneView resources.
Creating resources (POST)
The POST method invites the client to specify the unique ID of a new item to be created in a collection managed
by the server. History has shown it to be less problematic if the client's new item request specifies only the
content data, and the server returns a unique "handle" for the new item.
Reading resources (GET)
GET is usually the default method, when not explicitly specified in the request call. It retrieves information from
the server about a resource specified by the URI address in the call. The call might address a category (collection)
of multiple resources. In this case, a list of elements (members) will be returned, with some basic information
about them. Also, the call might address a single resource (element, member of a collection) and the response will
contain more detailed information (attributes) for that element.
Updating resources (PUT)
The PUT method is used to update the description of a resource. If the URI addressed resource exists, it is
updated by the new representation that is sent. If it does not exist, it is created. The server is responsible for
performing the actions needed and aligning that resource to its requested representation sent by the client. Also,
in a request body, an array of resources might be referenced in one call.
Updating resources (PATCH)
The PATCH method does almost the same thing as the PUT method. The main difference is that the PATCH
method requests that a set of changes described in the request entity be applied to the resource.
Deleting resources (DELETE)
Unlike the GET method, which is safe, meaning that calling it produces no side-effects, the PUT and DELETE
methods may produce side effects. They are idempotent methods, meaning that multiple identical requests
should have the same effect as a single request.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 71

HPE OneView REST API

REST API benefits

REST APIs provide many benefits:

• They provide an industry-standard interface for open integration with other management platforms
• They are designed to be ubiquitous—every resource has one URI and represents a physical device or logical
construct
• They enable your customer to automate anything they can do from the UI, using their favorite scripting or
programming language
• They are designed to be highly scalable

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 72

REST API versioning

Each HPE OneView release introduces a new REST API version. When preparing a script, verify the API version.
Using calls from a newer API version against an older version of HPE OneView can generate errors.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 73

cURL CLI utility

For those who prefer a command line interface (CLI) tool, the cURL utility can be used to interact with HPE
OneView. cURL is a free and open command line tool for transferring data with URL syntax under a wide variety
of operating systems, supporting: DICT, FILE, FTP, FTPS, Gopher, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS,
POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, Telnet, and TFTP.
cURL supports SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form-based upload, proxies,
cookies, user and password authentication (Basic, Digest, NTLM, Negotiate, Kerberos), file transfer resume, proxy
tunneling, and many other useful features.
Three examples follow:
• Login:
curl -k -H "Content-Type:application/json" -H "X-API-Version:3" -X
POST -d "{\"userName\":\"Administrator\",\"password\":\"password\"} "
https://appliance.example.com/rest/login-sessions
• Get all enclosures:
curl -k -H "X-API-Version:3" –H "auth:
DmYzKOo3utaMkSpXKos9B6PD0z2s0Vmd”
https://appliance.example.com/rest/enclosures
• Create network (with POST payload in a .json file named CreateNetworkBody):
curl -k -H "Content-Type:application/json" -H "X-API-Version:3" –H
"auth: DmYzKOo3utaMkSpXKos9B6PD0z2s0Vmd" -X POST -d
@CreateNetworkBody.json https://appliance.example.com/rest/ethernet-
networks
NOTE
Download cURL from https://curl.haxx.se.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 74

Postman

Postman interface

Postman helps your customer become more efficient while working with APIs. Postman can be used to interact
with HPE OneView and is very useful when testing scripts.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 75

HPE OneView PowerShell Library

Sample PowerShell cmdlet

The PowerShell Library is a wrapper for REST API calls used in HPE OneView. It is built by following style,
naming, and other standards by Microsoft PowerShell guidelines, like standard verb-noun command naming, and
it provides full integration with help and auto complete.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 76

The PowerShell Library add-on creates additional functions and extends basic use to REST API functionalities in
HPE OneView, making it much easier to perform basic tasks in simple syntax, using embedded objects and other
possibilities of PowerShell scripting. The PowerShell Library maps JSON to/from PowerShell objects.
The PowerShell Library provides full REST interaction allowing users to use:
• New to create a new resource
• Get/Modify/Set to change a resource
• Remove to delete a resource
NOTE
Starting with the HPE OneView 3.10 library release, it is now published on the PowerShell Gallery.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 77

Activity: Meeting with the customer

Participants will work as a group on this activity. After demonstrating HPE Synergy setup, HSP asked you to
verify that they understand everything correctly.
Answer the following questions, and decide if the statements are true or false:
1. True or false: HPE Synergy can be added to an HPE OneView appliance, used to manage a legacy HPE
BladeSystem. ________________________

2. True or false: A logical interconnect group for VC-FC is always created for a single frame.
________________________

3. True or false: The maximum number of frames that can be added to a logical enclosure depends on the
speed of the network adapters in the compute modules. ________________________

4. What is the purpose of a logical interconnect group?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

5. True or false: All logical interconnects are created automatically when a logical enclosure is created.
________________________

6. Which fabric is used by 12 Gb SAS switches? ________________________

7. Which HPE OneView object associates a network with a physical port on HPE Virtual Connect?
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 78

8. How can a new frame be added to an existing logical enclosure?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

9. True or false: FC networks must always be associated with a fabric from a SAN manager.
________________________

10. Describe M-LAG and what it does.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 79

Learning check
11. You are in a meeting with a customer, and they challenge you with a statement: “We have multiple branch
offices running the HPE Synergy platform. All the configuration changes are developed in the HQ. We are
afraid that propagating them to the branch offices will be time consuming and can result in significantly
different configurations.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

12. How can your customer get access to the HPE OneView PowerShell Library?
A. It is available when HPE Synergy is on warranty or a service contract that is purchased.
B. It is bundled with the HPE OneView for VMware vCenter Server® package.
C. It can be downloaded from the HPE OneView appliance or from HPE Synergy Composer.
D. It can be downloaded from the PowerShell Gallery without additional cost.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 80

13. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 81

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 82

Summary
• HPE Virtual Connect provides a disaggregated, rack-scale design that uses a master/satellite architecture to
consolidate data center network connections and reduce hardware and scale network bandwidth across
multiple HPE Synergy frames
• HPE hardware setup is the process of the initial HPE Synergy configuration. If HPE Composer2 is used together
with a DHCP server, it can be completed remotely
• The HPE Synergy configuration process involves several steps to create logical resources, including logical
interconnect groups, enclosure groups, logical enclosures, and logical interconnects
• API tools such as the PowerShell Library allow for scripting and automation. There are other tools like Postman
and the cURL utility that can be used to interact with the REST API

Lab exercise
Open your lab guide, and complete Lab 3: Configuring HPE Synergy.

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 83

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We considered using HPE
Primera for mission-critical workloads, but we are afraid that a single drive failure can cause the whole virtual
volume to fail.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a statement: “We want to use HPE Primera
as a primary storage virtualization platform, but we have heard that for virtualization, HPE Primera does not
support load balancing policies.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 84

3. You are in a meeting with a customer, and they challenge you with a question: “Our HPE Primera systems are
connected through Fibre Channel switches to HPE Synergy. When presenting a volume to a compute node,
we must configure zoning. This is a very time-consuming process. How can HPE OneView help us with this?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. You are in a meeting with a customer, and they challenge you with a statement: “Recently, we purchased HPE
Nimble to provide storage capacity for workloads in remote offices. We heard that HPE Nimble is not
supported in HPE OneView.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 85

5. You are in a meeting with a customer, and they challenge you with a question: “Our development team wants
to create a volume snapshot before installing a new version of the software. Unfortunately, the development
team has no access to SSMC because of the security settings. How can HPE OneView help the development
team with this task?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Configuring HPE Synergy solutions Page 86

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE
compute solutions
Module 3

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 2

Learning objectives
After completing this module, you should be able to:
• Explain HPE Storage concepts and products
• Differentiate and explain multipathing concepts
• Summarize the available storage management options in HPE OneView
• Recommend and describe the process of managing storage components using HPE OneView, including:
– Adding supported storage components
– Adding SAN managers
– Managing volumes
– Managing logical JBODs (just a bunch of disks)

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 3

Customer scenario

HSP successfully deployed the HPE Synergy platform, and they want to prepare for workload deployment. They
plan to boot compute nodes from SAN using virtual volumes (VVs) from HPE Primera, and they want to do as
much as possible using HPE OneView.
The HSP technical team wants to learn the basics of HPE Primera using SSMC, as they are aware that some
features are not accessible from HPE OneView. HSP plans to use VMware vSAN™ for virtualization workloads.
They plan to provide cache and capacity tiers, using drives from the HPE Synergy D3940 Storage Module, and
they want to learn how to manage logical JBODs.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 4

HPE Storage concepts

HPE provides a broad and deep flash portfolio.

HPE Storage array positioning

HPE Storage portfolio

The graphic above presents the HPE Storage portfolio, including the HPE Alletra 6000 and HPE Alletra 9000.
The breadth of HPE’s complete portfolio is aligned to the evolving requirements of customers. Each offering
addresses specific use cases and requirements. Customers can deploy these solutions across cloud, virtual, and
physical environments to ensure investment protection, and eliminate lock-in with broad and deep integration
across a rich ecosystem of independent software vendor (ISV) partners.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 5

OS virtualization—Logical view

HPE Primera virtualization layers

The first layer of abstraction employed by the HPE Primera and HPE Alletra 9000 OS divides media devices into
1 GiB chunklets to improve utilization and avoid stranded capacity. This fine-grained virtualization unit also
enables new media technologies such as storage class memory.
The second layer of abstraction takes the 1 GiB chunklets created from abstracting physical disk (PD) capacity
and creates logical disks (LDs) striped across the system’s PDs and implements the RAID level. Multiple RAID sets
made from chunklets of different PDs are striped together to form an LD. All chunklets belonging to a given LD
will be from the same drive type. Also, the first and second-level mappings taken together serve to massively
parallelize workloads across all the PDs behind a node.
Virtual Volumes (VVs) are the virtual capacity representations that are ultimately exported to hosts and
applications as VLUNs over FC or Internet Small Computer System Interface (iSCSI) target ports. A single VV can
be coherently exported through as few as two ports or as many ports as desired (not fewer than two—one from
each of two different nodes as a minimum).
The third layer of abstraction maps LDs to VVs with a granularity of 32 MiB or 128 MiB. With this approach, a
very small portion of a VV associated with a particular LD can be quickly and non-disruptively migrated to a
different LD for performance or other policy-based reasons, whereas other architectures require migration of the
entire VV. This layer of abstraction also implements many high-level features such as snapshots, caching, and
remote replication.
The three-layer abstraction implemented by the HPE Primera and HPE Alletra 9000 OS can effectively utilize any
underlying media type. This means that HPE Primera storage is able to make the most efficient use of SSDs
through load balancing across all drives to enable ultra-high performance and prolong the life span of flash-based
media.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 6

Chunklet concept

Chunklets and spare chunklets on the physical drive

Every physical disk that is admitted into the system is broken down into allocation units called chunklets.
Chunklet size is fixed at 1 GB for all drive sizes. A chunklet is the most basic element of data storage of the HPE
Primera system and forms the basis of the RAID sets. Depending on the sparing algorithm and system
configuration, some chunklets are allocated as spares.
Unlike many competitive arrays that reserve dedicated spare drives that then sit idle, system-wide sparing with
HPE Primera storage means that spare chunklets are distributed across all drives. This provides additional
protection and enables a balanced load that extends the SSD life span by providing even wearing. It also protects
against performance degradation by enabling a many-to-many rebuild in the event of a failure. Users do not
create chunklets, nor can the chunklet size be changed. In general, chunklets are the smallest unit of measure and
makeup of a VV at the physical level.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 7

Logical disks
There are two types of LDs:
• Shared data (SD) LDs provide the storage space for thin-provisioned VVs (TPVV), reduction VVs, and
snapshots (virtual copies)
• Shared administration (SA) LDs provide the storage space for the metadata used for VVs and snapshots
RAID functionality is implemented at the LD level, with each LD mapped to chunklets to implement RAID 6
(multiple distributed parity, with striping). The HPE Primera OS automatically creates LDs with the desired
availability and size characteristics.
Every LD has an owner and a backup owner. Using the default layout, chunklets from any given PD are owned by
a single node with the partner node as the backup owner; thus, every node creates LDs from the PDs it owns.
System-wide sparing

HPE Primera system-wide sparing

The system-wide striping of data provides high and predictable levels of service for all workload types through
the massively parallel and fine-grained striping of data across all internal resources (drives, ports, cache,
processors, and others). As a result, as the use of the system grows—or in the event of a component failure—
service levels§ remain high and predictable.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 8

For flash-based media, fine-grained virtualization combined with system-wide striping creates uniform IO
patterns, thereby spreading wear evenly across the entire system. Should there be a media failure, system-wide
sparing also helps guard against performance degradation by enabling a many-to-many rebuild, resulting in
faster rebuilds. Because HPE Primera storage automatically manages this system-wide load balancing, no extra
time or complexity is required to maintain an efficient system.
In a traditional storage array, small volumes either suffer from poor performance by using few drives, or waste
expensive resources by using more drives than required for capacity to obtain sufficient performance. On HPE
Primera storage systems, even modest-sized volumes are widely striped, using chunklets spread over multiple
drives of the same type. Wide striping provides the full performance capabilities of the array (nodes, CPUs, buses,
cache, and disk drives) to small volumes without provisioning excess capacity and without creating hotspots on a
subset of PDs.
RAID concepts

RAID 6 with set size 4+2

Exponential growth in SSD capacity without commensurate improvements in reliability or performance results in
greater risk of data loss. For example, consider the 15.36 TB SSDs available on HPE Primera storage systems.
The capacity difference alone implies that reconstruction of a failed disk upon replacement can be expected to
take more than 4x longer than a 3.84 TB drive. This creates a larger window of vulnerability during which a
second disk failure could cause data loss when using RAID 1 or RAID 5.
RAID 6 can rebuild data into a sparing area (spare chunklets) in the event of double disk failure. A RAID 6 volume
can survive the loss of up to two physical disks (data could be lost if three or more disks fail). The HPE Primera
RAID 6 implementation uses a forward error correction method based on erasure coding and offers multiple
distributed parities with striping.
RAID 6 organizes data based on its set size. The set size (SSZ) determines the data-to-parity ratio. This
parameter has performance, cost, and availability implications:
• RAID 6 supports set sizes as follows: 6 (4D+2P), 8 (6D+2P), 10 (8D+2P), 12 (10D+2P), and 16 (14D+2P)
• Primera systems automatically select the correct set size for the system
In an appropriately configured HPE Primera array, all available RAID options allow HPE Primera storage to create
parity sets on different drives in different drive cages with separate power domains for greater protection.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 9

High availability enclosure (cage) vs. high availability drive (magazine)

Cage availability minimums

HPE Primera arrays support two levels of availability:

• Cage (default)—No two members of the same RAID set can be in the same drive enclosure. For example, to
support RAID 6, SSZ=8 (6+2), four drive chassis connected to the same node pair are required. This helps
ensure that data is still available in the event that access to an entire drive cage is lost. This applies to drive
chassis that are point-to-point connected to the nodes (no daisy chain)
• Magazine (lower)—No two members of the same RAID set can be in the same drive magazine. This allows a
wider stripe with fewer drive chassis; for example, a RAID 6, SSZ=8 (6+2) would be possible with only four drive
chassis, provided each chassis had at least two drives

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 10

CPG creation

Creating CPG with a specific high availability (HA) level

A common provisioning group (CPG) represents a virtual pool of LDs that allows VVs to share the CPG’s
resources and allocate space on demand. Your customer can create TPVVs and data reduction VVs that draw
space from the same CPG LD pool.
CPGs enable fine-grained, shared access to pooled logical capacity. Instead of dedicating LDs to volumes, a CPG
allows multiple volumes to share the buffer pool of LDs. For example, when a TPVV is running low on user space,
the system automatically assigns more capacity to the TPVV by mapping new regions from LDs in the CPG to the
TPVV. As a result, large pockets of unused, but allocated, space are eliminated.
The CPGs dynamically allocate storage in increments, which are determined by the number of nodes in the
system and the RAID set size that has automatically been selected. This on-demand allocation unit determines
the automated response to the growth demands of volumes. To grow the volume, the HPE Primera OS may
expand existing LDs according to the CPG’s growth increment, or it may create additional ones. Growth is
triggered when the CPG’s available space falls below 85% of the growth increment value. A mechanism with
warnings and limits can be configured on the array to control the growth of a CPG.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 11

In general, CPGs are the policies and act as the template that VVs use, determining VV and snapshot
characteristics. They can have a separate snapshot copy CPG.
The system has a default CPG and the system first tries to create a CPG in an HA cage with the largest possible
set size. If the number of enclosures and drives does not allow for an HA cage, the system will use the HA
magazine (HA mag). More CPGs can be created manually, when needed, and all new CPGs are created with
RAID 6.
CPGs can be used for:
• Business purposes
• Controlling space allocation (set a growth warning/limit)
• Virtual domains
• Deduplication

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 12

Virtual volume creation

Virtual Volume building blocks

A virtual volume is the HPE terminology for the capacity unit that is presented or exported to a host as a VLUN.
The host sees the exported VV (VLUN) as a disk and can use it for OS deployment or for data. VVs are created
using a CPG, and the VV “inherits” the characteristics of the CPG. HPE Storage arrays allow your customers to
create TPVVs (optionally, they can be deduped and compressed).
NOTE
The matching colors in the graphic above indicate that chunklets are drawn from any available physical
disks, and logical disks are created from any available chunklets.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 13

There are two kinds of VVs: base volumes and snapshot volumes. A base volume directly maps all the user-visible
data, which can be considered to be the original VV and is either (a) a TPVV or reduction VV or (b) a snapshot
volume. When a snapshot is first created, all of its data is mapped indirectly to the parent volume’s data. When a
block is written to the parent, the original block is copied from the parent to the SD space, and the snapshot
points to this data space instead. This methodology is known as copy-on-write (CoW). Similarly, when a block is
written in the snapshot, the data is written in the SD space, and the snapshot points to this data space.
VVs have three types of space:
• The user space represents the user-visible size of the VV (that is, the size of the SCSI LUN seen by a host)
• The shared data (SD) space is used to store the data of the VV and any modified data associated with
snapshots. The granularity of data mapping is 16 KiB pages
• The shared admin (SA) space is used to store the metadata (including the page tables) for VVs and snapshots
Each of the three space types is mapped to LDs, with all of these LDs striped across all controller nodes; thus,
VVs can be striped across multiple nodes for maximum load balancing and performance.
All user-created VVs are TPVVs. A TPVV has space for the base volume allocated from the associated CPG and
snapshot space allocated from the associated snapshot CPG (if any). If data reduction is selected when creating a
TPVV, then common pages of data are shared with other data reduction volumes in the CPG, and the remaining
data is compressed. Data reduction is supported only on CPGs that use SSDs as a tier of storage. The size limit for
an individual TPVV without data reduction is 64 TiB and with data reduction, it is 16 TiB.
On creation, 256 MiB per node is allocated to a VV. Storage is allocated on demand in the SD area. The SA area
contains the metadata indexes that point to the user data in the SD area. Because the SA metadata needs to be
accessed to locate the user data, the indexes are cached in policy memory to reduce the performance impact of
the lookups. User-created VVs associated with a common CPG share the same LDs, and draw space from that
pool as needed, allocating space on demand in small increments for each controller node. As the volumes that
draw space from the CPG require additional storage, the HPE Primera OS automatically allocates additional 256
MiB increments to the volumes.
VLUNs and LUN masking
VVs are only visible to a host after the VVs are exported as VLUNs. VVs can be exported as follows:
• To specific hosts (set of WWNs). The VV is visible to the specified WWNs, regardless of the ports on which
those WWNs appear. This is a convenient way to export VVs to known hosts
• To specific hosts on a specific port

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 14

Thin provisioning overview

Thin provisioned volume provisioning

A TPVV uses logical disks that belong to a logical disk pool known as a CPG. TPVVs associated with the same
CPG draw user space from that pool as needed, allocating space on demand in 1 GB chunklet increments
beginning with 1 GB per controller node. As the volumes that draw space from the CPG require additional
storage, the system automatically creates additional logical disks and adds them to the pool until the CPG
reaches the user-defined growth limit that restricts the CPG’s maximum size.
The anatomy of a thin volume
The sparse nature of thin volumes requires a mechanism to map the VV address space to physical storage pages,
which are 16 KiB in size. The HPE Primera OS does this by using page tables, which are similar in concept to the
virtual memory mapping page tables of operating systems. The logical block address (LBA) of a SCSI read or
write command is then used as an index into three different page tables to find a particular 16 KiB block
belonging to a thin volume. New writes result in a free 16 KiB page being allocated (or multiple 16 KiB pages for
larger writes); rewrites of data simply reuse any previously allocated space, and writes of 16 KiB (or larger) of
zeroes result in space reclaim.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 15

The address space of a thin volume is also assigned across all the nodes in the system in 32 MiB increments in a
round-robin manner. The LBA for a new write IO, therefore, determines which node the IO is directed to, and this
aids the load balancing of IOs across all nodes in the system.
The system also needs a mechanism to track thin volume shared data page usage since space reclaim creates
unused “holes” in the 128 MiB regions allocated to particular thin volumes. To do this, there are two levels of
bitmaps used to track the thin volume used space. The shared data logical disks are made up of 128 MiB regions
that contain 8192 16 KiB pages. The first level (L1) bitmap indicates whether a given 128 MiB region in shared
data space is in use or not. If a region is in use, a second level (L2) bitmap indicates whether a particular 16 KiB
page in that region is in use or not.
As individual 16 KiB pages are freed, the space in the shared data logical disk can become fragmented. A
defragment thread periodically examines the bitmaps to determine whether defragmentation should be initiated.
The data from partially allocated regions is then reorganized to create larger contiguous blocks of free space that
can be reclaimed.
Thin provisioning and VMware vSphere
Since VMware vSphere has its own thin provisioning capabilities, a decision must be made regarding which level
to implement thin provisioning. When implementing HPE Primera TPVVs, administrators often ask whether
implementing for Virtual Machine Disk (VMDK) files makes any sense.
In general, thin provisioning with HPE Primera and vSphere accomplish the same end result, but at different
logical layers. With VMware vSphere thin provisioning, administrators realize greater VM density at the Virtual
Machine File System (VMFS) layer, at the cost of some CPU and disk IO overhead as the volume is incrementally
grown on the ESXi hosts. By implementing HPE Primera TPVVs, the same VM density levels are achieved;
however, the thin provisioning CPU work is offloaded to the HPE Primera ASIC. If the goal is to reduce storage
costs, help maximize storage utilization, and maintain performance, then use HPE Primera thin provisioning
software to provision VMFS volumes. If performance is not a concern, but over-provisioning VMs at the VMFS
layer is important, then administrators can consider implementing both thin provisioning solutions. However,
administrators should realize that there is no additional storage saving realized by using vSphere thin
provisioning on top of HPE Primera TPVVs; and in fact, implementing both solutions adds more management
complexity to the environment.
When creating VMs, there are several options for the file system layout of the VMDK files. By default, VMDK files
are created with the Thick Provision Lazy Zeroed (LZT) option, which means the VMDK is sparsely populated so
not all the blocks are immediately allocated. When a guest VM reads from the unallocated areas of the VMDK, the
ESXi server detects this and returns zeros rather than reading from disk. This VMware thin provisioning
capability enables the oversubscription of the sizes of the VMDK files within the datastore.
For performance-intensive environments, VMware recommends using Thick Provision Eager Zeroed (EZT) virtual
disks. These EZT disks have lower runtime overhead, but require zeros to be written across all of the capacity of
the VMDK at the time of creation. On traditional arrays, this VMDK format would negate all the benefits of thinly
provisioned LUNs as all of the physical storage is allocated when the volume is zero-filled during creation.
However, HPE Primera Thin Persistence software allows clients to retain thin provisioning benefits when using
EZT VMDKs without sacrificing any of the performance benefits offered by this VMDK option. In this case, Thin
Persistence helps ensure that, when a new EZT volume is created, the entire volume is not allocated from physical
storage since all zeros that have been written to the VMDK were intercepted and discarded by the HPE Primera
ASIC.
Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 16

Thin provisioning provides the following benefits:

• No upfront allocation of storage for TPVVs (cost savings)
• No restrictions on where TPVVs should be used (can have snapshots, remotely replicated, Dynamic
Optimization [DO], and so on)
• Allocation size of 16 K page, which is much smaller than most competitors’ thin implementations
• TPVVs can be created in under 30 seconds without any disk layout or configuration planning required
• TPVVs are wide striped over all drives within a certain tier of storage
• The ability to overprovision
• Space can be additionally reduced, using data reduction for even more cost savings

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 17

Triple+ Parity and integrated spare

Triple+ parity with integrated spare

The design goal of HPE Nimble Storage Triple+ Parity RAID was to far exceed the level of resiliency, compared to
all other methods of RAID protection, even for extreme cases of temporally correlated unrecoverable read errors
(UREs)—while maintaining an impressive usable:raw ratio and high performance.
Triple+ Parity RAID can withstand N UREs in parallel, where N is the number of drives in the RAID group, even if
all parity has been lost. This means that a system can completely lose three drives in a Triple+ Parity RAID group
and have simultaneous UREs on all remaining drives, and that system will not suffer data corruption. By
comparison, in a RAID 5 system, if a single drive has been lost (no parity left), zero UREs can happen without the
system losing data.
Triple+ Parity features include:
• Three drive’s worth of parity information is written
• Every chunk in a stripe consists of data, metadata (checksums, sequence number, and so forth), and parity
(XOR of data)
• Tolerates simultaneous failure of any three SSDs
• Built-in virtual spare allows fourth failure
• Intra-drive parity fixes sector loss in single read
• Supported by Nimble AF series and Alletra 6000

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 18

HPE Nimble HF-Series Triple+ Parity

HF-Series Tripe+ Parity

The Adaptive Flash Platform utilizes triple parity RAID to concatenate all hard disk drives in each shelf. HPE
Nimble storage uses left synchronous rotation. When writing parity, the first two parity blocks (P and Q) are
rotational, as seen in the image. The third parity block is not rotational and is written to the disk in slot one,
though it should be noted that if that disk fails, the R block may be written to another disk. To see which disks are
holding the R block, obtain and run the iostat.sh script during a heavy read workload. The disks containing
the R block should stick out with significantly less read activity.
HPE Nimble Storage’s triple parity design supports the loss of three hard disk drives in a single shelf before it
reaches zero disk redundancy. This means that three disk drives within a single shelf can fail without the system
losing data. Failed drives are only counted if they are actively marked as failed by the controllers. Should a single
shelf reach a point where there is zero redundancy within the RAID group, the system stops data services. The
HF-Series utilizes the same intra-drive parity as the AF-Series.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 19

HPE data reduction technologies

Data reduction technologies in HPE Primera

HPE Primera Data Reduction combines deduplication and compression to help maximize space savings. With data
reduction volumes, the incoming data is checked for duplicates before being compressed.
Deduplication with Express Indexing
Deduplication is a technology designed to eliminate duplicate information from being committed to disk. The
HPE Primera ASIC features a dedicated, high-performance, low-latency hashing engine used for deduplication
that can lead to not only massive savings over standard deployment methodologies, but also a much smaller
performance overhead when deduplication is enabled. Deduplication employs Express Indexing, a mechanism
that provides extremely high-performance lookup tables for fast detection of duplicate write requests.
When a new write request enters cache, a hash (or fingerprint) of the data is generated to draw a match against
other data stored on the array. Generating a hash of every data write is an extremely CPU-intensive task, and
many software-implemented hashing algorithms commonly found in all-flash platforms add a significant
performance overhead to write performance. With HPE Primera deduplication software, the CPU-intensive jobs of
calculating hash signatures for incoming data and verifying reads are offloaded to the ASICs, freeing up processor
cycles to perform other critical data services.
After the hash has been calculated, Express Indexing performs instant metadata lookups to compare the
signatures of the incoming request to signatures of data already stored in the array. If a match is found, the
system flags the duplicate request and prevents it from being written to the back end. Instead, a pointer is added
to the metadata table to reference the existing data blocks. To prevent hash collision (when two write pages have
the same signature, but different underlying data), HPE Primera Deduplication software leverages the controller
node ASICs once again to perform a high-performance, bit-to-bit comparison before any new write update is
marked as a duplicate, preventing incorrect data matches. This is an important step to prevent data corruption
and should be at the core of any deduplication implementation.
This hardware-assisted approach enables an inline deduplication implementation that carries multiple benefits,
including increased capacity efficiency, flash performance protection, and flash media life span extension. The
combination of hardware-assisted hashing and Express Indexing is powerful and efficient.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 20

Compression
While deduplication looks for opportunities to remove entire blocks of data by comparing them against each
other, compression works by looking for opportunities to reduce the size of pages before they are written to flash.
When compression and deduplication are enabled together, duplicate blocks are removed first, and then the
remaining data is compressed.
HPE Primera implements an extremely efficient, modern compression algorithm that can deliver supreme
performance for both compression and decompression tasks while yielding excellent compression savings. HPE
Primera implements Express Scan, a technology that further reduces the CPU overhead associated with
compression. This is achieved by inspecting blocks to ensure data is compressible, rather than wasting CPU
cycles attempting to compress data identified as incompressible.
Read and write performance profiles are very important with compression; write performance needs to be high to
support incoming write streams of data, but since writes are cached in system memory before they are committed
to flash, compression is essentially an asynchronous task, so it does not impact write latency as heavily. However,
reads are far more sensitive because not all reads are delivered from cache; whenever a read miss occurs (when a
read is requested and it is not in cache), the array must read the back-end data, decompress it, and return it to
the host. Performance here is the key, as latency increases as decompression performance reduces.
Data packing
After data has been compressed, the result is a number of data blocks that are smaller, but are also odd sizes (for
example, 1.3 KiB, 4.2 KiB, 5.6 KiB). These blocks are not only odd sizes, but they are very hard to write to flash
since flash pages are fixed in size—writing these pages directly to flash would result in lost performance and
reduced efficiency, neither of which are desirable. Data packing addresses this issue by packing these odd-sized
pages together into a single page before they are written to flash.
HPE Primera systems use 16 KiB physical pages to store data. When data reduction is used, HPE Primera data
packing allows multiple compressed pages to be stored in a single 16 KiB physical page. This data packing
technique is part of the inline process that not only optimizes physical space, but also creates larger, more media
efficient write sizes than other approaches, which improves both performance and media endurance. If an
overwrite occurs, the system refits the new compressed page in place, if there is available space. However, if the
new data does not fit into the existing page, it is queued for packing with other new writes. HPE Primera Express
Indexing technology, common to all HPE Primera thin volume types, is used to track the data within the
compressed pages.
Compaction
In addition to Data Reduction, HPE Primera systems offer additional capacity-efficiency technologies that include
market-leading, hardware-accelerated thin provisioning, thin clones, thin reclaim, Virtual Copy, and other
technologies. Savings from these technologies are not included in Data Reduction (or data reduction ratios) and
are instead reported in the compaction ratio—a ratio that exposes the full suite of efficiency technologies.
Therefore, compaction is the combination of thin technologies and data reduction.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 21

Activity: HPE Alletra architecture and features

HPE Alletra 9000 architecture technical document

Open the HPE Alletra 9000 Architecture.pdf document located in your class package, and decide whether the
statements below about Alletra 9000 architecture and functionality are true or false.

Feature True or False

Shared data (SD) LDs provide the storage space for TPVV, reduction VVs, and snapshots
(virtual copies).
Adaptive Sparing is a flash optimization technique that eliminates cache bottlenecks by
changing the frequency at which data is offloaded from cache to flash media, based on system
utilization.
The HPE Alletra 9000 supports system-wide striping.
The HPE Alletra 9000 full-mesh backplane is an active circuit board that contains slots for up to
four controller nodes.
A chunklet is the most basic element of data storage of the HPE Alletra 9000 system and forms
the basis of the RAID sets.
The Persistent Port functionality works for Fibre Channel and iSCSI transport layers.
Cache offload is a unique feature of the HPE Alletra 9000 three-layer virtualization technology
that allows HPE Alletra 9000 controller nodes to share access to SSDs to further drive
efficiency.
Virtual Volumes have two types of space: user space and shared admin space.
Asynchronous periodic replication is based on snapshots and delta resyncs.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 22

Learning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We considered using HPE
Primera for mission-critical workloads, but we are afraid that a single drive failure can cause the whole virtual
volume to fail.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 23

Multipathing concepts

Typical multipath architecture

Multipathing is supported by many different operating systems and provides high-availability and load-balancing.
Multipath drivers provide path virtualization to mask fabric and disk array complexity. Multipath solutions
provide automatic path failover between a server and disk arrays. Some multipath solutions provide load
balancing over multiple HBA paths. Various algorithms can be used, and it is administrator controlled.
CLI and GUI are available for management of the multipathing. In some cases, multipathing algorithms are
embedded into an operating system, and sometimes they must be installed by an administrator.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 24

Automatic path failover

Automatic path failover

If a data path fails, multipathing automatically tries to switch to an alternate path. The failover is not visible to
applications. All path changes are logged, allowing service personnel to investigate and repair failed paths. Your
customer can configure some multipathing solutions to automatically send notification of failures.
Automatic path failover is:
• Supported by services, agents, and drivers
• Transparent to applications
• Possible to configure preferred and alternate paths
• Supported with FC and FC SANs
Some HPE arrays such as Primera, for example, also offer transparent failover of port identity (Persistent Ports
feature).

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 25

Load balancing

Multipathing polices for VMware

Load balancing allows improved throughput from host to target and should be configured from the multipath
application interface (this might be the command line). Multipath load balancing prevents any path from
becoming overloaded, and it helps to prevent the congestion that occurs when many IO operations are directed
to common devices along the same path. Load balancing is performed using a policy selected by the
administrator. The policies find the least busy path as determined by requests, bytes, or service time.
There are various load balancing policies (depending upon the multipath software):
• Round Robin
• Least IO
• Least bandwidth
• Shortest queue (requests, bytes, service time)
• No load balancing (off)

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 26

Microsoft MPIO

Setting MPIO properties in Windows

Multipath IO (MPIO) uses redundant physical path components to eliminate single points of failure between
servers and storage. MPIO increases data reliability and availability, reduces bottlenecks, and provides fault
tolerance and automatic load balancing of IO traffic.
The MPIO driver development kit currently supports Fibre Channel and parallel SCSI interfaces. Support for tape
drives and iSCSI-connected devices is planned for future releases.
Although multipathing and clustering both provide high availability, multipathing by itself does not protect
against hardware or software failure because it only ensures redundancy of cabling, adapters, and switches.
MPIO standardizes the connection between storage and Microsoft Windows Server, creating an interoperable
solution that provides multipathing in heterogeneous storage environments. It is supported by a variety of
storage vendors, including HPE, EMC, Hitachi, QLogic, and VERITAS. This software must not be used on systems
running any other multipathing software.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 27

MPIO solutions consist of two components:

• Drivers developed by Microsoft
• Device-specific modules (DSMs) developed by HPE or other vendors for their storage arrays. Most arrays of
most storage vendors now support generic DSMs, shipped with Windows 2008+, which only need to be enabled
and configured along with Microsoft MPIO

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 28

Learning check
2. You are in a meeting with a customer, and they challenge you with a statement: “We want to use HPE Primera
as a primary storage virtualization platform, but we have heard that for virtualization, HPE Primera does not
support load balancing policies.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 29

Storage management options in HPE OneView

HPE OneView can be used to manage various HPE Storage components.

Storage management using HPE OneView

Storage management options in HPE OneView

The STORAGE section in HPE OneView allows administrators to:

• Manage volumes and volume templates
• Monitor volume sets
• Manage storage pools and storage systems
• Add SAN managers
• Manage SANs imported through a SAN manager
• Manage D3940 drive enclosures
• Manage logical JBODs
HPE OneView provides basic storage management.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 30

Learning check
3. You are in a meeting with a customer, and they challenge you with a question: “Our HPE Primera systems are
connected through Fibre Channel switches to HPE Synergy. When presenting a volume to a compute node,
we must configure zoning. This is a very time-consuming process. How can HPE OneView help us with this
problem?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 31

Storage components supported in HPE OneView

HPE OneView supports only selected HPE Storage arrays. Storage connectivity is managed through SAN
managers.

Supported HPE Storage components in HPE OneView

D3940 Storage module and HPE Primera

HPE OneView supports the following storage components:

• HPE Synergy D3940 Storage Module
• HPE 3PAR (7000, 8000, 9000, 10000, 20000, and 20000 R2)
• HPE StoreVirtual (StoreVirtual 3200 LHOS 13.x, StoreVirtual VSA LHOS 12.x, and StoreVirtual LHOS 13.6)
• HPE Nimble (Nimble OS 4.5, Nimble OS 5.0, and Nimble OS 5.1)
• HPE Primera storage (Primera OS 4.0, Primera OS 4.1, and Primera OS 4.2, 4.2.1, 4.2.2)
• HPE Alletra 9000 and HPE Alletra 6000
NOTE
For the latest information, refer to the HPE OneView Support Matrix.

HPE OneView does not replace management tools for a given type of array. Managing an array is focused on
volume/capacity management, not the array management itself. Advanced array configuration should be
performed using a dedicated tool.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 32

Supported SAN switches

HPE FlexFabric 5700 48 G 4XG 2QSFP+ Switch

HPE OneView supports the following SAN switches:

• HPE FlexFabric switches (specific models):
– HPE FlexFabric 5700, 5900, 5930, 5940, 5710, 5950, 5980
– HPE FlexFabric 79xx and 129xxx Switch Chassis
• Brocade switches:
– 8 Gb, 16 Gb, and 32 Gb FC SAN switches
• Cisco switches:
– Cisco Nexus switches
– Cisco Nexus 5500/5600/6000 models
– Cisco MDS 9xxx model 8, 16, 32 Gb FC SAN switches
You cannot add switches to HPE OneView, but HPE OneView can interact with them through the API or SAN
manager.
NOTE
For the latest information, refer to the HPE OneView Support Matrix.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 33

Connection methods

Storage connected through FC switches and directly

HPE OneView for supported arrays (HPE Primera, 3PAR, and Nimble) supports two connection methods for HPE
Synergy and HPE BladeSystem when Virtual Connect modules are used:
• Fabric attached—The enclosure interconnects connect to data center SAN fabric switches
• Flat SAN—The enclosure interconnects connect directly to a supported storage system
Using a Flat SAN can help your customer to reduce infrastructure cost and simplify the deployment.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 34

Learning check
4. You are in a meeting with a customer, and they challenge you with a statement: “Recently, we purchased HPE
Nimble to provide storage capacity for workloads in remote offices. We heard that HPE Nimble is not
supported in HPE OneView.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 35

Managing storage components using HPE OneView

HPE OneView supports basic storage management for selected arrays.

Storage management functionalities

HPE Primera and 3PAR SSMC

HPE OneView provides storage capacity management features, and it does not replace array management tools.
Advanced array features (like replication, storage containers, virtual domains, and CPGs) are still configured using
an appropriate array management tool. Storage management capabilities are limited to selected HPE arrays;
therefore, third-party storage systems are not supported in HPE OneView.
Adding supported storage components
Before HPE OneView can be used to interact with storage arrays, the array must be added to HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 36

Adding managed storage systems

Adding a storage system to HPE OneView

A storage system is a storage device from which logical disks (volumes) can be provisioned and presented to
servers through FC ports or iSCSI IP addresses. Bringing SAN storage systems under management of HPE
OneView enables your customer to add and create volumes. Your customer can then attach volumes to server
profiles through volume attachments. This enables the server hardware assigned to the server profiles to access
the SAN storage system. StoreServ, StoreVirtual, Primera, and Nimble are the supported storage system types.
HPE OneView monitors the health status of storage systems and issues alerts when there is a change in status of
a storage system. HPE OneView also monitors the connectivity status of storage systems. If HPE OneView loses
connectivity with a storage system, an alert is displayed until connectivity is restored. HPE OneView attempts to
resolve connectivity issues and clear the alert. If it cannot, your customer must resolve the issues, and use the
Storage Systems screen to manually refresh the storage system to synchronize it with HPE OneView.
HPE OneView also monitors storage systems to ensure that they are synchronized with changes to hardware and
configuration settings. However, changes to storage systems made outside HPE OneView (such as changing
credentials) might cause the storage system to lose synchronization with HPE OneView, in which case your
customer can manually refresh the storage system.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 37

To add a supported storage system to HPE OneView:

1. From the HPE OneView main menu, select STORAGE à Storage Systems.
2. In the master pane, click + Add storage system.
3. Enter the data requested on the screen.
4. Click Add to complete the action, or click Add + to add another storage system.
NOTES
• Users must have infrastructure administrator or storage administrator privileges
• The storage system must be powered on and configured, and the Web Services Application Programming
Interface (WSAPI) service must be enabled

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 38

Managing storage pools for HPE Primera and HPE 3PAR

Storage pools management in HPE OneView

A storage pool is an aggregation of physical storage resources (disks) in a storage system. Storage systems
contain information about the storage ports through which they can be accessed. Your customer can provision
logical storage spaces, known as volumes, from storage pools.
The Storage Pools screen displays the storage pools discovered by HPE OneView. Use this screen to manage the
state of the storage pools (discovered/managed), or refresh storage pools properties.
On the Storage Pools screen, select a storage pool to display its configuration properties in the details panel, such
as its state, drive type, RAID level, storage system, domain, volumes, folders, and scopes used by volume
templates and used by volumes. Your customer can also see the total and allocated capacity.
Your customer cannot create or delete storage pools from HPE OneView. Storage pools are automatically
discovered during the storage system add or refresh. After your customer elects to manage storage pools, they
can provision volumes on them.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 39

All storage pools (CPGs) from HPE 3PAR and HPE Primera are imported to HPE OneView when adding a storage
system, and they can be configured to:
• Discovered state
• Managed state
Volume provisioning is only possible for managed pools. The pool state is defined during the import procedure,
but the pool state can be changed after a pool is imported:
• From discovered to managed
• From managed to discovered

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 40

Managing storage pools for HPE Nimble

Adding an HPE Nimble array to HPE OneView

A collection of volumes is referred to as a volume set in HPE OneView. Volume sets are used to govern data-
protection policies, such as snapshot and replication schedules. Volumes that hold multiple components of an
application, such as databases and transaction logs, can be grouped into a volume set.
A volume set includes a set of schedules to create snapshots of each associated volume at a specified interval.
Snapshots are captured synchronously to assure a consistent backup of the entire application environment. In
general, each application uses a different volume set. Volume sets can contain multiple schedules, which affect
all volumes assigned to the set. These schedules are additive, so when schedules overlap, snapshots and replicas
are created for every schedule.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 41

Volume sets are defined and configured by the storage administrator on an HPE Nimble Storage system. For HPE
Nimble Storage, the corresponding terminology for "volume sets" is "data protection volume collections."
If required, your customer can choose to restrict the use of a volume set to specific authorization scopes on
an HPE Nimble Storage system.
Currently, all volume sets for HPE Nimble Storage must be defined in HPE Nimble Storage using the HPE Nimble
Storage administrative console. Newly created "data protection volume collections" are detected and imported
into HPE OneView as volume sets whenever a system refresh occurs. A snapshot schedule (frequency) is defined
in association with the volume set.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 42

Configuring system ports on HPE 3PAR/Primera

Configuring system ports on an HPE Storage system

Port groups represent a set of FC SAN storage access ports that will be assigned, usually in pairs, to a server
profile SAN attachment path. When an FC storage system is imported into HPE OneView, the storage
controller ports can be manually placed into logical, user-defined groups. These port groups are used when
volumes are attached to a server profile. This grouping determines which subset of ports are automatically
assigned to a path to provide access to the volume. Prior to HPE OneView version 5.2, the port group with the
least number of profiles assigned was used for each new path created for a volume attachment. Starting
from HPE OneView version 5.2, the port group identified for the first volume path is preferred for all additional
paths for the same volume on that profile.
An automatic port group assignment improves the predictability and consistency for port group usage by:
• Knowing the volume path used across all fabric connections
• Enabling the administrator to define the ports manually to include all the storage controllers in an array
• Placing alternative paths to the volume from any redundant SAN into the same port group
• Requiring manual port group creation for new storage system additions
When editing HPE 3PAR StoreServ, HPE Primera, and HPE Nimble Storage systems, your customer can only
change the Expected SAN/Network and Port Group values.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 43

Port group characteristics include:

• Port groups are the mechanism in OneView to control which array target ports on a SAN are configured per
server when attaching SAN storage volumes to servers
• Port groups aid automated zoning to select subsets of target ports to zone with initiators when performing
volume attachments
• While adding a storage system, all the storage ports are displayed. If a SAN manager is imported and associated
with available SANs (in case of a fabric attach), the existing connectivity is displayed
• Port groups are used to partition the array target ports on a SAN, configuring only a single group of ports on a
SAN for each volume attachment
• The default is to put all ports on an array connected to a SAN in a single port group, so your customer sees all
ports being configured for each attachment over a SAN by default
• When HPE OneView attaches a volume to a server, for each storage path, OneView configures all storage
system ports connected to the SAN (connecting the storage system to the server) as storage targets. If the
storage administrator wishes to partition the storage system ports into smaller groups to be configured to each
server, then they should assign a group name to the ports to be configured together
• When port groups are defined, OneView (by default) chooses the least configured port group to attach volumes
to a server, achieving load balancing across the storage system’s ports

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 44

Automatic port group assignment

Path assignment by profile connections

The graphic above illustrates how the paths are assigned by profile connection, using the least-used group for
each volume. In this case, a different port group, highlighted in orange, is used to connect to the same storage
array from the second fabric.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 45

Per volume port group assignment

The graphic above illustrates how the port group assignments change from a per-fabric SAN assignment to a
per-volume attachment assignment. The port group used for the SAN A fabric is the same for the SAN B fabric.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 46

Learning check
5. Which action is allowed on storage pools managed by HPE OneView?
A. Changing CPG RAID level
B. Provisioning volumes
C. Extending CPG set size
D. Setting volume replication

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 47

Adding SAN managers

Adding a SAN manager in HPE OneView

SAN managers are a resource in HPE OneView that represent a connection to an external entity through
which SANs are discovered and managed. The external entity can be vendor-specific management software or a
physical switch.
SANs are created outside of HPE OneView in the SAN manager vendor’s management interface. After they are
created, SANs can be discovered and managed in HPE OneView, using the SAN manager resource. When
managing SAN managers, HPE OneView does not permit a SAN to be managed through more than one SAN
manager. When associating an HPE OneView network to the SAN, the choice of which SAN to associate
determines which SAN manager will be used to manage the SAN. Any subsequent change to a new SAN manager
application requires going through a phased migration process.
To add a SAN manager, complete the following steps:
1. From the HPE OneView Main menu, select STORAGE à SAN Managers.
2. Click + Add SAN Manager.
3. From the drop-down menu, select the SAN manager type, and complete all of the required information.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 48

Configuring HPE SAN managers

To configure an HPE SAN manager:
• Your customer must have a valid SNMP v3 user with default read permissions
• HPE SANs must only be managed by a single HPE OneView appliance
• The default port on which the switch listens for SNMP requests is 161
• The SNMP security level setting can be Authentication, Authentication and privacy,
or None
• The authentication protocol setting can be SHA or MD5
• The privacy protocol setting can be DES-56, AES-128, or 3DES
Configuring Cisco SAN manager
To configure a Cisco SAN manager:
• Your customer must have a valid SNMP v3 user with write permissions
• Cisco SANs must only be managed by a single HPE OneView appliance
• Cisco SAN managers managed by HPE OneView discover virtual SANs (VSANs) in the range of VSAN 2 to
4093, but not VSAN 1 (default VSAN) and VSAN 4094 (isolated VSAN). Cisco recommends that you do not use
VSAN 1 in a production environment. All discovered VSANs are reflected in the HPE OneView SANs resources
for association with HPE OneView FC networks for auto-zoning
• The default port on which the switch listens for SNMP requests is 161
• The SNMP security level setting can be Authentication or Authentication and privacy
• The authentication protocol setting can be SHA or MD5
• The privacy protocol setting can be DES-56 or AES-128
Configuring Brocade Network Advisor (BNA) SAN manager
To configure a BNA SAN manager:
• Your customer must have a valid user account with Storage Management Initiative Specification (SMI-S)
running. Your customer should refer to the documentation for their SAN manager for more information
• To allow HPE OneView to see SAN fabric topology changes automatically, your customer must disable Track
Fabric Changes on the BNA. Otherwise, they must perform an Accept Changes operation on the
BNA whenever they make changes to the SAN fabric topology for HPE OneView to see them. See the BNA
documentation for more information on disabling Track Fabric Changes
• BNA-based SANs can be managed by one or more HPE OneView appliances
• BNA's SMI Agent listens on the following default ports: SSL: 5989 and non-SSL: 598

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 49

Configuring Brocade Fabric OS (FOS) switch SAN manager

To configure a Brocade FOS switch SAN manager:
• The HPE OneView Brocade FOS switch SAN Manager uses a REST session on the switch. Each fabric (virtual or
non-virtual) configured on the Brocade switch is discovered by the HPE OneView Brocade FOS switch SAN
Manager, creating an HPE OneView SAN
• Your customer can connect to the Brocade switch REST interface through HTTP (port 80) or HTTPS (port
443). To use HTTPS, configure the switch with an HTTPS certificate
NOTE
Brocade Network Advisor software is EOL. End of support is planned for Feb 2022.

Brocade Fabric OS (FOS) switch SAN manager

Your customer can use HPE OneView to perform SAN auto-zoning with Broadcom Brocade Fibre Channel switch
fabrics. With the addition of a Brocade FOS switch SAN manager, an alternative management path along with
BNA is available to configure SAN zoning, using the FOS REST API of the Brocade switch.
A Brocade FOS switch SAN manager exchanges data with a single physical switch. The FOS SAN manager
discovers all SAN fabrics that are configured in the logically defined fabric for the switch.
To discover multiple SANs, manage zoning configuration from the HPE OneView UI. With HPE OneView, your
customer can choose which physical switch to associate with a particular SAN manager. However, each fabric can
only be managed by one of the SAN managers discovering the fabric.
When choosing the physical switch to associate with a SAN manager, consider the following:
• Which switch is most robust?
• Which switch will undergo fewer changes?
• Which is a member of most of the SAN fabrics that your customer wants to be discovered by HPE OneView,
therefore, minimizing the number of SAN managers they create?

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 50

SAN states

SANs added to HPE OneView

The possible states for SANs are:

• Discovered—A SAN that is not associated with a network. SANs are automatically discovered when a SAN
manager is added to HPE OneView
• Managed—A SAN that is associated with one or more networks in HPE OneView. Only managed SANs can be
configured to be automatically zoned by HPE OneView
• Direct attach SANs—HPE OneView creates a direct attach SAN (flat SAN) automatically when your customer
configures an enclosure with a logical interconnect that contains a direct attach uplink set. HPE OneView
names the direct attach SAN using the format <interconnect><uplink set>. The created SAN is a FC direct
attach SAN that is not zoned and cannot be edited

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 51

Associating a SAN with a network

Associating an FC network with a SAN

To enable auto zoning on a specific network, it must be associated with a SAN:

• If a SAN manager was added before the network is created, association can be done when creating the network
• If a SAN manager was added after the network was created, association can be done by editing the network
Your customer can associate a discovered SAN with one or more networks in HPE OneView from the Networks
screen. The automated zoning feature is activated when presenting a volume to the server through the server
profile.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 52

Changing SAN settings

Editing a SAN

A SAN zone enables communication between devices connected to the SAN. SAN zoning policies determine how
zoning should be configured on a SAN. SAN zoning policies define whether or not zoning is automated as well as
the naming format of zones and aliases. In HPE OneView, your customer can specify the name format of the
zones and aliases that will be created when they associate a storage volume to a server profile via a volume
attachment. By specifying zone names and alias formats, using text strings and server profile objects, your
customer can create names that are meaningful and conform with their naming conventions.
HPE OneView performs zoning only when your customer adds a connection to a server profile and attaches a
SAN storage volume to it. When they do this, HPE OneView determines if the current zoning allows connectivity.
If current zoning does not allow connectivity, HPE OneView creates the necessary zoning, based on the specified
zoning policy.
Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 53

Automated zoning enables HPE OneView to automatically create, edit, and delete zones on a zoned SAN when
your customer attaches storage volumes to servers through a volume attachment in a server profile. Your
customer can specify the name format for a zone by selecting variables in the order of their choice. They can also
add text strings to the zone name. Zone and alias names must follow certain guidelines, and HPE OneView will
modify zone and alias names defined in the zoning policy to ensure they adhere to those guidelines.

Guideline Action taken by HPE OneView

Name cannot contain illegal characters

Removes illegal characters from the name.
(determined by the SAN manager)
Modifies the name to make it unique if it is not unique. The
Name must be unique
name is appended with _# where # is a number starting at 1.
Name begins with an illegal initial character Prepends A_ on invalid alias names, and Z_ on invalid zone
(determined by the SAN manager) names.
Creates a unique name using a unique variable for the SAN.
Name cannot be blank For example, a blank server profile connection variable could
be replaced with the connection ID variable.
Truncates the name starting with tokens in the name, and
Name cannot exceed a certain character length
then the whole name if it is still too long.
Zone and alias naming guidelines

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 54

Activity: HPE OneView storage management features

Storage pools in HPE OneView

HSP wants to know which storage management tasks can be completed using HPE OneView, and which require
array management tools.

Feature Tool

Creating new CPG for HPE Primera and HPE StoreServ

Creating a volume array-based snapshot
Growing a virtual volume size
Quality of Service (QoS) configuration
Replication setup
Configuring zoning on Fibre Channel switches
Boot from SAN configuration for compute nodes
Creating a storage container for vVols
Virtual volume dynamic optimization

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 55

Learning check
6. What is the state of a SAN that is associated with one or more networks in HPE OneView?
A. Discovered
B. Available
C. Connected
D. Managed

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 56

Managing volumes
HPE OneView allows volume management on supported storage arrays.
Volume operations

Configuring global storage settings

Using HPE OneView, an administrator can:

• Create a volume (directly or through a template)
• Import an existing volume
• Manage snapshots and clones
• Delete a volume
• Remove a volume from HPE OneView only (un-import)
• Present a volume to a server through a server profile
• Create private volumes on-demand, when creating a server profile
• Manage multipathing
An administrator can configure HPE OneView to require that a volume template be used when creating a volume.
This is a global setting that prevents the creation of volumes without using a volume template.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 57

Volume template for HPE Primera/HPE 3PAR

Creating a volume template for HPE Primera

When defining a volume template for HPE Primera, the following parameters must be defined:
• Name of the volume (description is optional)—Enter a name for the volume template. Description of the
volume template is optional
• Storage pool—The storage pool in which volumes created from the template are provisioned
• Capacity—The capacity for volumes created from the template. The minimum and maximum volume size is
dependent on the storage system. See the storage system documentation for information on volume size. If
your customer wants to use data reduction technologies on HPE Primera, the minimum volume size is 16 GiB
• Sharing type—Two options are available:
– Shared—The volume can be used by more than one server profile
– Private—The volume can be used by only one server profile and can be used to boot from a SAN

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 58

• Data reduction—HPE Primera Data Reduction combines deduplication and compression to help maximize
space savings. With data reduction volumes, the incoming data is checked for duplicates before being
compressed. The minimum size of the volume with data reduction technologies enabled is 16 GiB
• Snapshot storage pool—A snapshot storage pool is a CPG that is used for snapshot data. It can be the same
CPG as the volume CPG or a different one
Some of the template parameters can be locked and cannot be changed when creating a volume. Parameters for
3PAR arrays are almost the same, though there are minor differences in the Advanced section.
Volume template for StoreVirtual

Creating a volume template for HPE StoreVirtual

When defining template properties for StoreVirtual storage, parameters are very similar to the properties of the
template for the 3PAR arrays:
• Name of the volume (description is optional)
• Storage pool
• Capacity
• Sharing type
• Provisioning type

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 59

In addition, your customer must define:

• Data protection level—Network RAID stripes and protects multiple copies of data across a storage cluster,
eliminating single points of failure. Applications have continuous data availability in the event of a disk, server,
storage subsystem, power, network, or site failure. Match the appropriate network RAID level for each volume in
the cluster, based on capacity and performance needs
• Adaptive Optimization (AO)—AO provides two storage tiers and balances blocks of data transparently
between them, accelerating unpredictable and changing workloads in virtualized environments. AO allows cost-
effective combinations of rotational media and flash storage
Volume template for HPE Nimble

Creating a volume template for HPE Nimble

When defining a volume template for HPE Nimble, the following parameters must be defined:
• Volume name (description is optional)
• Volume capacity
• Sharing type
• Provisioning method
• Volume deduplication

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 60

• Volume encryption, if applicable

• Performance policies
• Cache pinning, if applicable
• Volume set membership
• IOPS limit setting
• Data transfer limit setting
• Folder membership
Some of the parameters are unique to HPE Nimble arrays and include:
• Cache pinning—This parameter is applicable for hybrid (a mix of flash and mechanical storage) arrays, and
provides a 100 percent cache hit rate for specific volumes (for example, volumes dedicated to critical
applications) and delivers the response times of an all-flash storage system. A volume is pinned when the entire
active volume is placed in cache; associated snapshot (inactive) blocks are not pinned. All incoming data after
that point is pinned. The number of volumes that can be pinned is limited by the size of the volumes and
amount of available cache
• Performance policy—Defined on the storage system array, a performance policy helps optimize the
performance of the volume, based on the characteristics of the application using the volume. The policy defines
the block size; whether deduplication, compression, and caching options are enabled; and defines behaviors
when certain limits are exceeded. Based on the selected performance policy, the application category and block
size displays. After a volume is created with a performance policy selected, your customer can change only the
performance policy in the future from among a list of predefined policies having the same block size or
deduplication settings
• Volume set—A collection of volumes is referred to as a volume set in HPE OneView. Volume sets are used to
govern data-protection policies, such as snapshot and replication schedules
• Folders—Folders are containers for holding volumes. They are used most often for organization, management,
and further delegation. Folders provide simple volume grouping for ease of management
• IOPS limit and data transfer limit—Limits on IOPS and data transfer in mega binary bytes per second (MiB/s)
are used in conjunction with the volume block size to govern QoS for volumes. The input and output requests
are throttled when either the IOPS or the data transfer limit is met. On the array, the IOPS and data transfer
limits might also be applied to a folder to equally throttle requests to all volumes in the folder when the
cumulative IOPS of all the volumes under that folder exceed the folder IOPS limit or when the cumulative
throughput of all the volumes under that folder exceeds the folder MiB/s limit

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 61

Creating a volume

Creating a volume using HPE OneView

Volumes can be created manually or by using a template. When creating a volume manually, all parameters must
be entered. When creating a volume by using a template, all parameters are populated from the template. An
administrator can configure the appliance to require that a volume template be used when creating a volume.
This is a global setting that prevents the creation of volumes without using a volume template.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 62

Importing a storage volume

Importing an existing volume to HPE OneView

An administrator can add a volume that exists on a storage system under the management of HPE OneView. The
administrator must select the storage system and provide the volume name, a description for that volume, and a
sharing type. A volume imported to HPE OneView is managed like a volume created using HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 63

Growing volume capacity

Editing volume properties using HPE OneView

An administrator can increase (grow) the capacity of a volume. The minimum and maximum size is dependent on
the storage system. An administrator cannot increase the capacity of a full-provisioned volume beyond the
remaining capacity in the storage pool. To increase volume size, just edit the volume and enter the new capacity.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 64

Creating snapshots and clones

Creating a volume snapshot using HPE OneView

A snapshot is a Virtual Copy of an existing volume at a point in time. Your customer can use a snapshot as a
backup of a volume, and then use the snapshot to revert a volume to the backup or to create volumes from the
snapshot. A snapshot is a static copy of a volume at the point the snapshot is created. Snapshots are not updated
to reflect changes in the volume since the snapshot was taken. A new volume created from a snapshot is the
same size as the snapshot and contains all the data in the snapshot. The two volumes are logically unrelated, but
physically, unchanged data is only stored once between the two volumes. Reverting a volume to a snapshot
reverts to the data the volume contained when the snapshot was taken. The size of the volume remains the same
as when it was reverted. For example, if your customer takes a snapshot of a 50 GiB volume, grows the volume to
100 GiB, and then reverts to the snapshot, the volume is 100 GiB with the data from the 50 GiB snapshot.
Reverting to a snapshot of a volume causes all data created or changed since the snapshot was taken to be lost.
Your customer should back up their data to prevent data loss. Deleting a snapshot results in loss of all data in the
snapshot.
Within HPE OneView, snapshots can only be created for HPE 3PAR StoreServ and HPE Primera for use in
managing the storage system resources. Snapshots for HPE Nimble Storage are created and managed within the
HPE Nimble Storage system.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 65

Scheduling snapshots for volume sets

A volume set includes a set of schedules to create snapshots of each associated volume at a specified interval.
Snapshots are captured synchronously to assure a consistent backup of the entire application environment. In
general, each application uses a different volume set. Volume sets can contain multiple schedules, which affect all
volumes assigned to the set. These schedules are additive, so when schedules overlap, snapshots and replicas are
created for every schedule.
A collection of volumes is referred to as volume set in HPE OneView. Volume sets are used to govern data
protection policies, such as snapshot and replication schedules.
Volumes that hold multiple components of an application, such as databases and transaction logs, can be
grouped into a volume set.
Volume sets and HPE Nimble Storage
Volume sets are defined and configured by the storage administrator on an HPE Nimble Storage system. For HPE
Nimble Storage, the corresponding terminology for "volume sets" is "data protection volume collections."
If required, your customer can choose to restrict the use of a volume set to specific authorization scopes on
an HPE Nimble Storage system.
Currently, all volume sets for HPE Nimble Storage must be defined in HPE Nimble Storage, using the HPE Nimble
Storage administrative console. Newly created "data protection volume collections" are detected and imported
into HPE OneView as volume sets whenever a system refresh occurs. A snapshot schedule (frequency) is defined
in association with the volume set.

A storage volume with a snapshot created

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 66

An administrator can create a full copy of a volume, based on the data in the snapshot. For large volumes, this can
take a long time, depending on storage system resources available for the copy action.
Deleting volume attachments and volumes

Deleting a storage volume using HPE OneView

Using HPE OneView, an administrator can delete storage volumes—the ones created using HPE OneView and
volumes created using array management tools and imported to the HPE OneView.
Volume deletion options:
• Remove a volume from only the HPE OneView inventory
• Remove a volume from the HPE OneView inventory and on the storage system
If the volume is associated with a server profile, HPE OneView does not allow its removal. If your customer wants
to delete such a volume, they must first unexport this volume through the server profile.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 67

HPE OneView shared storage

A storage volume using two HPE OneView instances

HPE OneView supports managing a storage volume from multiple HPE OneView instances. The storage volumes
can be configured using the active/active Peer Persistence architecture to replicate the data between the
different storage arrays. The HPE Primera system manages the consistency of the storage volume. None of
the HPE OneView instances manage this architecture.
Your customer should use the same type of storage volume in all HPE OneView instances. In each appliance, your
customer should configure a server and attach it to the storage volumes of all the appliances. Therefore, your
customer can configure volume attachment of a storage volume in one HPE OneView instance without disrupting
the volume attachment configurations of storage volumes in other instances.
When your customer edits a storage volume in one HPE OneView instance, the changes are applied to the same
storage volume shared in all other HPE OneView instances.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 68

However, the following modifications performed on a storage volume attachment are applicable only to the HPE
OneView instance that manages the server using those storage volume attachments:
• Create or delete storage volume attachments to the storage volume
• Delete a storage volume from one HPE OneView instance (without deleting it from the storage system)
• Deleting a storage volume from one HPE OneView instance does not affect the storage volume present in
another instance. To delete the shared storage volume from different instances, either delete it from the
storage system or from each HPE OneView instance
HPE OneView instances need to be enabled to configure the IO paths to the same two volumes from two
different servers.

Disabling the Extra volume presentations check alert

When multiple HPE OneView appliances are managing the same storage volume, disable the Extra volume
presentations check alert in each appliance.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 69

Learning check
7. Which volume management operation can be completed using HPE OneView?
A. Creating volume snapshots
B. Changing the volume CPG
C. Shrinking an imported volume
D. Changing the volume RAID level

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 70

Managing logical JBODs

HPE OneView can manage logical JBODs for HPE Synergy frames configured with D3940 Storage Modules.
HPE OneView LJBOD—Synergy D3940

Creating a logical JBOD using HPE OneView

Composable storage is a group of PDs that your customer can dynamically define as virtual drives. These virtual
drives are called logical JBODs. A JBOD is a group of physical disk drives that can be assigned to server hardware.
Unlike a RAID configuration, a JBOD is a not a redundant configuration. Your customer can specify a RAID
configuration when they create a logical JBOD. The Logical JBODs screen enables an administrator to create and
manage logical JBODs. An administrator can expand the local storage of the server hardware with logical JBODs.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 71

A logical JBOD provides the following features:

• Drives for a logical JBOD can either be selected automatically or manually
• Drives participating in a logical JBOD can be securely erased
• A logical JBOD lifecycle can be associated with a server profile lifecycle
• A logical JBOD can be created during server profile creation or before
Logical JBODs are created, assigned, and unassigned to server hardware from server profiles or server profile
templates. A logical JBOD uses the drives from the D3940 drive enclosures that are installed in the device bays of
the enclosure and are associated with a SAS logical interconnect. If the logical drive settings in the server profile
indicate that the data in the logical JBOD is to be retained when your customer deletes the server profile, then
the data is retained, and they can assign this logical JBOD to a different server profile. Your customer can delete a
logical JBOD only after they unassign it from the server profile. If they have chosen to erase the drive data when
they delete a logical JBOD, all the drive data will be erased.
Considerations for your customer, when configuring logical JBODs include:
• They can configure the available scopes to allow or restrict access to the drive enclosures
• They can assign a logical JBOD to only one server profile
• They can choose the drive enclosures that belong to the same SAS logical interconnect to create the logical
JBOD
• They can create a logical JBOD using homogenous drives like SAS SSD, SAS HDD, SATA SSD, or SATA HDD.
They cannot mix different types of drives in a logical JBOD
• They cannot add or remove drives to a logical JBOD after it is created

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 72

Activity: Meeting with the customer

Participants will work as a group on this activity. After discussing and demonstrating management of the HPE
Storage components using HPE OneView, HSP has asked you to verify if they understand everything correctly.
Answer the following questions, and decide if the statements are true or false:
1. True or false: The same logical JBOD can be presented to multiple compute nodes. ________________________

2. True or false: HPE Synergy supports in-frame storage (D3940) and external storage components.
________________________

3. Does adding an HPE Storage array to HPE OneView require a supported SAN manager?
________________________

4. True or false: One HPE Primera volume can be managed by two HPE OneView instances.
________________________

5. What is the purpose of a SAN manager?

__________________________________________________________________________________________________________

6. Which storage interconnect modules for HPE Synergy are fully managed with HPE OneView?
__________________________________________________________________________________________________________

7. What is the maximum number of HPE D3940 Storage Modules that can be installed in a single frame?
________________________

8. True or false: The D3940 Storage Module is supported for VMware vSAN deployment.
________________________

9. True or false: A logical drive created on an HPE D3940 Storage Module can be shared between multiple
systems. ________________________

10. Which data protection method is supported in Nimble AF series and Alletra 6000?
__________________________________________________________________________________________________________
Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 73

Learning check
8. Which statement about logical JBODs is true?
A. A logical JBOD requires HPE Synergy Virtual Connect SE 32 Gb FC modules.
B. Different types of drives can be used within a logical JBOD.
C. Only the same type of the drives can be used within a logical JBOD.
D. Logical JBODs cannot be created if a D3940 module is installed in the frame.

9. You are in a meeting with a customer, and they challenge you with a question: “Our development team wants
to create a volume snapshot before installing a new version of the software. Unfortunately, the development
team has no access to SSMC because of the security. How can HPE OneView help the development team with
this task?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

10. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 74

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 75

Summary
• HPE Primera is a Tier 0 enterprise storage solution that delivers the extreme resiliency and performance of
high-end storage with the agility of the cloud
• Multipath solutions provide automatic path failover between a server and disk arrays. Some multipath solutions
provide load balancing over multiple HBA paths
• HPE OneView can be used to manage supported storage components, but it does not replace array
management tools. HPE OneView provides access to the most common storage management features
• Using HPE OneView, customers can manage HPE arrays, SAN managers, volumes, and logical JBODs. HPE
OneView supports only selected HPE Storage components

Lab exercise
Open your lab guide, and complete Lab 4: Managing storage for HPE compute solutions.

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 76

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a question: “We plan to deploy a new set
of HPE Synergy frames that will support a virtualization workload. To simplify the management and
troubleshooting process, we want to standardize all server profiles. We want to be able to quickly propagate
changes to these profiles, if required. How can we do this?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a question: “We plan to present a virtual
volume from HPE Primera to HPE Synergy compute nodes. We heard that to present such a volume, we need
to power off the server. Is there a way to present a volume to the server without powering off the server?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 77

3. You are in a meeting with a customer, and they challenge you with a question: “We need to modify some
server profiles that we created using a server profile template. We tried to modify one of them, and it became
inconsistent with its server profile template. How can we modify server profiles and avoid inconsistency
problems?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. You are in a meeting with a customer, and they challenge you with a question: “In the past, we deleted a
hypervisor cluster profile from HPE OneView, and our VMware cluster was also deleted from the vCenter
Server®. Is there a way to delete such a profile from HPE OneView, and preserve the VMware cluster?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing storage for HPE compute solutions Page 78

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server
profiles
Module 4

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 2

Learning objectives
After completing this module, you should be able to:
• Explain the server profile template (SPT) and the server profile concepts
• Create an SPT

• Manage server profiles

• Manage hypervisor cluster profiles

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 3

Customer scenario

HSP successfully deployed HPE Synergy together with HPE Primera as primary storage. They want to learn how
to build a server profile for HPE Synergy compute nodes. They plan to boot compute nodes from SAN using
virtual volumes from HPE Primera. They know how to manage HPE Primera, but they need more details on how
to configure servers to boot from such volumes. HSP has asked you to explain and demonstrate downlink
aggregation through server profiles.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 4

Server profile template and server profile concepts

A server profile captures key aspects of a server configuration in one place. An SPT serves as a structural
reference when creating a server profile. In other words, server profiles can be created, using the settings
contained within an SPT.

Server profile

List of the server profiles in HPE OneView

Server profiles provide a consistent method to deploy servers and easily manage large numbers of servers in your
customer’s data center. An HPE Synergy compute node must have a server profile defined, otherwise it is
disconnected from the network and storage. Other supported servers can be either monitored or managed using
HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 5

A server profile captures key aspects of a server configuration in one place, including:

• Unique IDs (WWNs, MACs, serial numbers)

• Network and storage connectivity

• Firmware update selection and scheduling

• OS deployment settings (for Synergy only)

• BIOS and boot configuration settings

• Local storage (including D3940 for Synergy) and SAN storage

• Integrated Lights Out (iLO) settings

• Advanced settings

Your customer can assign a server profile to an empty bay. The server profile is applied automatically to the
server hardware when the server is inserted into the bay and meets the following criteria:

• The enclosure bay is not assigned by another server profile (for example, your customer cannot assign a profile
to bay 6 if a profile for a full-height server hardware type (SHT) is assigned to bay 1). This is checked when the
profile is assigned
• The SHT of the hardware matches the SHT specified in the server profile

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 6

Server profile template

List of the server profile templates in HPE OneView

An SPT serves as a structural reference when creating a server profile. All of the configuration constructs of a
server profile are present in the SPT.
SPTs help to monitor, flag, and update server profiles in HPE OneView. This template type defines the centralized
source for the configuration of OS deployment, firmware, connections, local storage, SAN storage, boot, BIOS, and
profile affinity.
SPTs provide a mechanism to store configurations for a server profile. Typically, your customer captures best-
practice configurations in an SPT, and then creates and deploys server profiles. Your customer can create one or
more templates to store the configurations for all the settings of a server profile.
A server profile continues to maintain an association to its SPT after being created from an SPT. Any drift in
configuration consistency between the SPT and server profiles is monitored and made visible on both the SPT
and the associated server profiles. In general, an SPT can be used to create multiple server profiles and propagate
changes to multiple server profiles.
Consistency checking validates a server profile to ensure that the server profile matches the configurations of the
associated SPT. HPE OneView monitors both the server profile and the SPT, and compares the two, based on the
selected consistency check. Your customer can select the consistency check when creating or editing an SPT.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 7

HPE OneView supports three types of consistency checks in the SPT:

• Exact match—The SPT defines the configuration, and the server profile must exactly match the template to
stay consistent
• Minimum match—The server profile must match the minimum configuration defined in the SPT. The server
profile can define additional configurations and still stay consistent with the template. For example, if an SPT
configures a set of volume attachments with the consistency check as a Minimum match, the server profile
based on this template remains consistent, even if it has additional volumes, along with the volumes specified in
the template. If the SPT specifies Exact match as the consistency check, the server profile is consistent only if it
has the same number of volumes as specified in the template
• Not checked—The configurations of the SPT are used as the default while creating the server profile. These
configurations are not checked for consistency and are not subject to remediation
Consistency checking in server profile templates
Consistency checking validates a server profile to ensure that it matches the configuration of its associated SPT.
If both configurations match, the server profile Consistency state field is set to Consistent and is considered to be
compliant. The HPE OneView appliance monitors both the server profile and the SPT, compares the two, and
checks the resources listed below for consistency.
The table below presents consistency checking in SPTs:

Resource Consistency checking parameters

OS Deployment • Exact match—The OS deployment plan in the server profile must

exactly match with that defined in the template. During remediation,
the server profile is changed to an exact match. The settings other than
the OS deployment plan are not checked for consistency
• Not checked—The OS deployment settings in the template are used as
default values when creating the server profile, but are not checked for
consistency and are not subject to remediation
Firmware • Exact match—The server profile must exactly match the firmware
settings in the template. During remediation, the server profile is
changed to an exact match
• Not checked—The firmware settings in the template are used as
default values when creating the server profile, but are not checked for
consistency and are not subject to remediation
Connections • Exact match—The server profile must exactly match the connection
configuration in the template
• Minimum match—The server profile must match the connections in
the template, but additional connections are allowed
• Not checked—The connection configuration settings in the template
are used as default values when creating the server profile, but are not
checked for consistency and are not subject to remediation

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 8

Local Storage • Exact match—The server profile must exactly match the local storage
configuration in the template
• Minimum match—The server profile must match the local storage
configuration in the template, but additional logical drives or logical
JBODs (just a bunch of disks) are allowed
• Not checked—The local storage settings in the template are used as
default values when creating the server profile, but are not checked for
consistency and are not subject to remediation
SAN Storage • Exact match—The server profile must exactly match the template
(attachments, paths, ports, and nothing additional)
• Minimum match—The server profile must contain the attachment
configuration defined in the template, but additional attachments and
paths are allowed in the profile. Storage target ports are not checked
for consistency
• Not checked—The template configuration is used when creating a
server profile, but no consistency checks are performed later
Boot Settings • Exact match—The server profile must exactly match the boot settings
in the template
• Not checked—The boot settings in the template are used as default
values when creating the server profile, but are not checked for
consistency and are not subject to remediation
BIOS Settings • Exact match—The server profile must exactly match the BIOS settings
in the template
• Not checked—The BIOS settings in the template are used as default
values when creating the server profile, but are not checked for
consistency and are not subject to remediation
iLO Settings • Exact match—The server profile must exactly match for each of the
iLO settings under management in the template
• Not checked—The iLO settings in the template are used as default
values when creating the server profile, but are not checked for
consistency and are not subject to remediation

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 9

Learning check
1. You are in a meeting with a customer, and they challenge you with a question: “We plan to deploy a new set
of HPE Synergy frames that will support a virtualization workload. To simplify the management and
troubleshooting process, we want to standardize all server profiles. We want to be able to quickly propagate
changes to these profiles, if required. How can we do this?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 10

Creating a server profile template

The SPT has multiple sections that define specific server configuration options.

General and server profile section

General and server profile sections in the SPT

An HPE OneView server profile has multiple sections that define server identity. Options available can be
different for different servers. In the General section of the SPT, your customer needs to configure the name of
the SPT. Adding a description of the SPT is optional, but it enables your customer to easily identify it. If their
organization is using multiple templates for different workloads, it makes sense to enter a meaningful description
for each of them.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 11

Options available can be different for different servers:

• The General section defines:

– Server profile name

– Optional description

• The Server Profile section defines:

– Server profile description—Description of the server profiles created from the specific SPT
– Server hardware type—Identifies the SHT for which the SPT is created. The SHT determines the
provisioning settings available, such as the BIOS settings
– Enclosure group—Defines the enclosure group for which the SPT is created. By default, profile mobility is
limited to the servers within the same enclosure group and sharing the same hardware type. After the server
profile is created, an administrator can change both the SHT and enclosure group for a given server profile
– Affinity—Controls remove-and-replace behavior for servers. If your customer applies a server profile to a
server, and the server is subsequently removed from the device bay, the Affinity setting controls whether the
server profile is reapplied when your customer inserts a server into the empty bay. Rack servers do not have
affinity
– Device bay—The server profile assigned to the device bay is applied to any server your customer inserts
into the bay, provided the SHT of the inserted server matches the SHT specified
– Device bay + server hardware—The server profile assigned to the device bay is not applied if your
customer inserts a server into the bay, and it does not match the serial number and SHT listed in the
server profile

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 12

OS deployment and firmware section

OS Deployment and Firmware sections in the SPT

OS deployments using HPE Image Streamer and OS deployment plans can be defined and configured within the
SPT. Your customer can create multiple server profiles from a single SPT having the same OS deployment plan.
The OS Deployment section defines the OS Build plan and customization parameters (available only for HPE
Synergy with an Image Streamer).
The Firmware section defines the Service Pack for ProLiant (SPP) to be used as a firmware baseline, consistency
checking, installation method, and activation method, if applicable. A forced installation option defines which
components are installed:

• Unchecked—Only updates are installed

• Checked—Downgrades and rewrites are allowed

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 13

Firmware bundles like an HPE SPP enable your customer to update firmware, drivers, utilities, and the hardware
configuration for enclosures, enclosure groups, and interconnects. An SPP update contains firmware, drivers, and
utilities, delivered as a single Preboot Execution Environment (PXE)-bootable image. Your customer can upload
and install these firmware bundle updates in a repository to simplify maintaining baseline configurations across
devices. The SPP they select as the starting point from which to compare the application of all subsequent SPPs
is their firmware baseline. Your customer can use the server profile to assign firmware levels to managed devices,
or they can choose the managed manually option. The choices for installing an SPP are:

• Firmware and Operating System (OS) Drivers using Smart Update Tools—Updates the firmware and OS
drivers without powering off the server hardware
• Firmware only using Smart Update Tools—Updates the firmware without powering off the server hardware

• Firmware only—Manages the firmware through HPE OneView. Selecting this option requires powering off the
server hardware
Firmware can be changed while the server hardware is powered on as long as the "Firmware only" setting is not
used.
Smart Update Tools
Smart Update Tools (SUT) is an operating system utility used with iLO 4 (Gen9 servers) and iLO 5 (Gen10 and
Gen10 Plus servers) for HPE OneView. SUT provides an online, nondisruptive mechanism to update firmware and
operating system drivers on server hardware.
Smart Update Tools is a generic term used for all variants of SUT. Integrated Smart Update Tools (iSUT) is
available for Windows and Linux with Gen9 and Gen10 servers. For VMware ESXi™ systems, iSUT is available for
Gen10 servers. It needs to be installed within the managed host OS. SUT is available for ESXi with Gen9 servers.
It is a standalone installation for every instance of HPE OneView.
SUT polls HPE OneView every five minutes for new requests, processes those requests, and provides HPE
OneView with a status. HPE OneView posts the progress in the Firmware section of the Server Profile page. SUT
installs updates in the correct order and ensures that all dependencies are met before starting an update. If there
are unmet dependencies, SUT prevents the installation and notifies the HPE OneView administrator that the
installation cannot continue due to a dependency.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 14

Key features:

• Combined driver, software, and firmware updates

• Compliance reporting in the HPE OneView Global Dashboard, based on the status received from SUT

• An increase in uptime by minimizing the number of reboots required for activation

• The ability to perform firmware staging and development tasks outside of the actual maintenance window so
that one reboot during the maintenance window activates both firmware and driver updates
• Multiple user roles:

– The HPE OneView Software administrator defines the required state, using the firmware options in the server
profile.
– The SUT administrator uses SUT to update the firmware and the software on the server

• Manual control and varying levels of automation:

– On-demand or manual updates

– Semiautomatic when staging is automatic or when staging and installation are automatic
– Scheduled updates
– Fully automatic update
Your customer can downgrade device firmware to an earlier version if the later firmware is known to cause a
problem in their environment. The most common reason for downgrading is when a device is repaired, and the
replacement part has firmware that is later than the baseline assigned to your customer’s devices. Other than this
case, downgrading firmware is not recommended.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 15

Connections section

The Connections section in the SPT

Your customer can configure connections in an SPT. Full connection management is available for HPE Synergy.
Your customer can add a connection to a server profile without assigning a network or network set by choosing
the Unassigned selection. By selecting Unassigned from the network drop-down menu, they reserve the
associated server port to assign networks later. Your customer can use this selection to temporarily stop traffic
forwarding on the interconnect port associated with the profile connection. Valid networks or network sets can be
selected for an active connection while the server power is on and without the need to reboot the server.
Connection types, including Ethernet and FC, can be created without assigning a network, using the Unassigned
selection from the network drop-down menu. The Unassigned selection also reserves virtual MAC and WWN
addresses for a virtual port.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 16

Manage connections
By default, the Manage connections checkbox is selected, which enables your customer to add connections to the
SPT. They can deselect Manage connections to create an SPT without connections.
Deselecting Manage connections enables your customer to add connections to the server profile without causing
compliance issues with the SPT. If an Image Streamer is used, the first physical function from two NICs are used
to provide connectivity to the boot volumes.
Network
The network is about the Ethernet network, RDMA over Converged Ethernet (RoCE) network, network set, FC,
Fibre Channel over Ethernet (FCoE), or Internet Small Computer Systems Interface (iSCSI) network for this
connection. An Ethernet or RoCE network or network set can be accessed by an Ethernet device. A FC or FCoE
network can be accessed by a FC device. To boot from an iSCSI device with an Ethernet connection, your
customer must select UEFI (Unified Extensible Firmware Interface) as the boot mode in the Boot Settings pane.
Networks are filtered to both FC and FCoE when the Type is set to Fibre Channel. Typically, your customer should
assign each connection in an SPT to a single network. Network sets enable them to select multiple networks for a
single connection defined in an SPT. Network sets are useful with hypervisors, where SPTs need the ability to
define multiple networks.
Your customer can deploy large network sets when using the HPE Virtual Connect SE 100 Gb F32 Module for
HPE Synergy. Large network sets can contain up to 4094 networks, minus the number of networks that are in the
reserved virtual LAN (VLAN) range, which can range from 60 to 128 networks. The default is 128 networks.
Generally, the maximum number of networks is 3966 networks. A maximum of 60 distinct large network sets can
be simultaneously deployed per logical interconnect.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 17

Adding a connection

Adding a connection in the SPT

When adding a connection, select the type of connection:

• Ethernet

• Fibre Channel

• iSCSI

To define an FCoE connection, select Fibre Channel. After the connection type and specific network are selected,
additional parameters are displayed. Complete the other parameters required for the specific connection type.
The maximum number of connections supported by a profile is equal to the total number of virtual ports available
across all the HPE FlexFabric adapters in the server, plus two unassigned connections, or 50, whichever is smaller.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 18

Adding an Ethernet connection

Adding an Ethernet connection in the SPT

The following parameters are defined for an Ethernet connection:

• Name of the connection (optional)

• Function type (Ethernet)

• Network or network set used by this connection

• Port (auto or manually select physical function)

• Link aggregation group, if required

• Requested bandwidth

• Requested virtual function

• Boot parameters, if required

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 19

Network
The connection contains either an unassigned network that reserves the associated port or a valid Ethernet
network, RoCE network, network set, FC, or FCoE network.
An Ethernet or RoCE network or network set can be accessed by an Ethernet device; a FC or FCoE network can
be accessed by a FC device. To configure an iSCSI boot device with an Ethernet connection, your customer must
select UEFI or UEFI optimized as the boot mode in the Boot Settings pane. Networks are filtered to both FC and
FCoE when the Type is set to Fibre Channel.
Your customer can assign each connection in an SPT to a single network. Network sets enable your customer to
select multiple networks for a single connection defined in a server profile or SPT. Network sets are useful with
hypervisors, where SPTs need the ability to define multiple networks.
Port
Your customer can place a connection on:

• A specific FlexNIC

• Any FlexNIC of a specific adapter port

• An automatically selected FlexNIC

Your customer specifies FlexNICs by adapter, physical port number, and FlexNIC identifier. Adapter identifiers
include LOM, FlexibleLOM 1, FlexibleLOM 2, Mezzanine 1, Mezzanine 2, and Mezzanine 3. FlexNIC identifiers are
a, b, c, and d. For example, selecting Mezzanine 1:2-c configures the connection on the third FlexNIC (c) on the
second physical port of the adapter in Mezzanine slot 1.
Some physical ports are identified by adapter, physical port number, and the suffix (Auto). For example, selecting
FlexibleLOM 1:1 (Auto) places the connection on the first available FlexNIC on the first physical port of the first
FlexibleLOM. These connections are assigned in the order of connection ID. If both connection 5 and connection
8 specify FlexibleLOM 2:1 (Auto), and no other connections are assigned to FlexibleLOM 2, connection 5 is
assigned to the first FlexNIC, and connection 8 is assigned to the second FlexNIC.
Selecting Auto assigns the connection to a FlexNIC in a predetermined order. Connections with Auto specified are
assigned (in connection ID order) to FlexNICs after connections with specific FlexNICs or ports are assigned. All
FC connections are assigned to FlexNICs before Ethernet connections are assigned. Auto connections are
assigned according to function type in the following order:
1. Fibre Channel
2. iSCSI
3. Ethernet (with PXE)
4. Ethernet (without PXE)
In general, your customer must assign a connection to the first FlexNIC on every physical port before a
connection is assigned automatically to the second, third, or fourth FlexNIC of any port.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 20

Before your customer assigns a connection to a FlexNIC, the following conditions must be met:

• They cannot configure the same network on multiple FlexNICs of a single physical port. This includes networks
in a network set
• The sum of the requested bandwidth values cannot exceed the capacity of the port, which is determined by the
adapter
In general, connections with an Auto FlexNIC setting are assigned to FlexNICs in a predetermined order. However,
this can result in the required conditions not being met. In these cases, selecting specific FlexNICs or specific
adapter ports enables your customer to specify a valid configuration. When they select specific ports, ensure that
they do not have unused ports before the last selected FlexNIC. For example, when your customer selects
FlexNICs 1a, 1b, and 1d, port 1c is left unused, and the operating system on the server instantiates the port, but
makes it unavailable for use. This may result in an invalid configuration.
Requested bandwidth (Gb/s)
Each connection on a FlexNIC has the following three types of bandwidth:

• Requested bandwidth—It is the requested minimum bandwidth at which the connection can operate

• Allocated bandwidth—It is automatically derived from the requested bandwidth and is the guaranteed
minimum at which the connection operates
• Maximum bandwidth—It is the maximum speed the connection can operate at and is derived from the lower
of the physical port speed and the speed of the network or network set
When additional bandwidth is available, the connection can operate at a higher than allocated bandwidth. When
additional bandwidth is not available, the network connection speed does not fall below the allocated bandwidth.
For Ethernet, the requested bandwidth applies only to outbound (transmitted) traffic. Inbound traffic is
processed on a first come, first served basis by the interconnect. For FCoE, the requested bandwidth controls
both inbound and outbound traffic.
When your customer selects a network, the appliance automatically populates the preferred bandwidth with the
value from the network definition, but that value can be overridden while defining the connection.
The bandwidth is programmed onto the adapter as an integer percentage of the total possible bandwidth. When
specifying preferred bandwidth for a connection in a profile, the possible choices are in increments of 1% of the
total possible bandwidth. For example, when the total possible bandwidth is 10 Gb, then the preferred bandwidth
setting is in increments of 100 Mb (1% of 10 Gb), but if the total possible bandwidth is 25 Gb, then the preferred
bandwidth specified is in increments of 250 Mb. Any value specified that is not an integer percentage of the total
bandwidth is rounded down to the nearest integer percentage. For example, when the maximum bandwidth is
10 Gb, the requested bandwidth is 1.1 Gb, which is 11% of the total bandwidth. However, when the maximum
bandwidth is 25 Gb, the requested bandwidth of 1.1 Gb, which is 4.4%, is rounded to 4% and the preferred
bandwidth is set to 1 Gb. If rounding causes the value to be 0%, then the value is rounded up to 1%.
The total possible bandwidth is the highest available speed at which the adapter and the interconnect can both
communicate. Both of the ports on an adapter must have the same highest available speed. If one port has a
slower negotiated speed than the other, both ports would take the lower number as their total possible
bandwidth.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 21

If the logical interconnect is formed from a pair of HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy,
then the speed can be changed from 25 Gb to 50 Gb and from 50 Gb to 25 Gb.
When the downlink speed is reduced on the logical interconnect from 50 Gb to 25 Gb, each profile with a server
associated with the logical interconnect is examined. If the sum of the requested bandwidth for any profile
exceeds 25 Gb, the request to change the speed on the logical interconnect is rejected with an error message.
When the speed is changed to 25 Gb, the maximum bandwidth of the profile connections is adjusted if the
original speed is greater than 25 Gb.
For Virtual Connect FC connections, the available discrete values are based on the adapter and the FC
interconnect module. With FC connections on HPE FlexFabric adapters, your customer can select from a full range
of speeds. However, if they change the host bus adapter (HBA) speed through the BIOS setting, and then set the
requested bandwidth setting for a server profile connection to a non-compatible value, the link will not be
established.
Requested virtual functions
The following are the virtual functions that your customer can select:

• None—This is the default setting

• Custom—Select the number of requested virtual functions, up to the maximum number available on the port

• Auto—Virtual functions are distributed automatically across the physical ports. With this setting, virtual
functions are first allocated to the FlexNICs requesting an explicit number of virtual functions. The remaining
virtual functions are then evenly distributed across all FlexNICs that have auto specified the virtual function
allocation. It is therefore possible that a FlexNIC requesting an auto virtual function allocation might receive no
virtual functions
Boot
Your customer can select a connection as a primary or secondary boot device. A template can contain bootable
Ethernet, FC, and iSCSI connections. For an Ethernet connection, the following options are available:

• Not bootable

• PXE primary

• PXE secondary

• iSCSI primary

• SCSI secondary

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 22

Link Aggregation Group

End-to-end link aggregation

The following interconnects support associating connections to form a Link Aggregation Group (LAG):

• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy

• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy

The LAGs on server ports allow for outage-free interconnect firmware update, seamless failover, improved traffic
load-balancing, and switch-assisted NIC teaming policies.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 23

Downlink aggregation

A LAG defined in the SPT

To create a LAG between connections in a server profile, select the same valid Link Aggregation Group (LAG 1
to LAG 60) for each of the connections. A LAG contains two Ethernet connections, and both connections must:

• Have the same requested bandwidth

• Access the same network or network set

• Be configured on the same FlexNIC on both physical ports of one adapter, and adapter ports must be
connected to the interconnects in the same logical interconnect
The teaming or bonding driver in the server OS must be configured to enable the Link Aggregation Control
Protocol (LACP) and to form the LAG correctly.
Examples of supported NIC teaming options include:

• Windows—IEEE 802.3ad dynamic link aggregation (802.3ad) (LACP)

• Linux—IEEE 802.3ad dynamic link aggregation (802.3ad) (LACP)

• ESXi—Route based on IP Hash and Distributed Switch for LACP

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 24

Adding a Fibre Channel connection

Adding a Fibre Channel connection in the SPT

The following parameters must be defined for a FC connection:

• Name of the connection (optional)

• Function type (Fibre Channel)

• FC or FCoE network used by this connection

• Port (auto or manually select physical function)

• Requested bandwidth

• Boot parameters, if required:

– Not bootable
– FC primary
– FC secondary

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 25

If auto zoning functionality is required, an FC or FCoE network should be associated with a fabric provided
through a SAN manager.
Your customer can select a connection as a primary or secondary boot device. A template can contain bootable
Ethernet, FC, and iSCSI connections. When booting from an FC, the following options for a boot target are
available:

• Managed volume—Specify the boot volume by setting the boot attribute on a volume in the SAN Storage
section of the server profile. For iSCSI, the iSCSI initiator used in the boot is defined in the Advanced panel of
the server profile
• Specify boot target—Specify the FC or iSCSI boot target

• Use Adapter BIOS—Select this to enable the BIOS on the server hardware to specify the boot target

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 26

Adding an iSCSI connection

Adding an iSCSI connection in the SPT

The following parameters must be defined for an iSCSI connection:

• Name of the connection (optional)

• Function type (iSCSI)

• iSCSI network used by this connection

• Port (auto or manually select physical function)

• Requested bandwidth

• Boot parameters, if required

• Complete iSCSI Initiator information

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 27

Learning check
2. Which statement about downlink aggregation is true?
A. Both connections must use the same FlexNICs.
B. Both connections must be configured with different speeds.
C. Appropriate licenses must be applied to the profile.
D. The server admin must disable the OS LACP teaming on compute modules.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 28

Configuring local storage

Local storage configuration in the SPT

The Local Storage section defines the integrated storage controller setup. When configuring local storage, the
following parameters can be configured:

• Consistency check level

• Available controller:

– Integrated controller
– SAS controller (for HPE Synergy only)
With a SmartRAID controller, your customer can manage storage that is direct attached to their server hardware,
using server profiles. They can create logical drives in the server profile as part of the integrated storage
controller and mezzanine storage controller configuration. Logical drives configured on a mezzanine storage
controller are backed by Serial Attached SCSI (SAS) logical JBODs that use physical drives zoned to the server
from attached storage. Your customer can view the details of the associated SAS interconnect on the Logical
Interconnects screen. When creating a logical drive, they can also select to have a dedicated spare drive
configured. When a spare drive is configured, the controller switches to use the allocated online spare drive in the
event of a drive failure.
For an HPE Synergy platform, an administrator, through a server profile, can configure the SAS controller
installed in mezzanine 1.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 29

Configuring an integrated storage controller

Configuring an integrated storage controller through SPT

When configuring an integrated storage controller, the number of the options depends on the hardware
generation. When Gen10 server hardware is selected in the server profile, the following options are available:

• Manage integrated storage controller—Selecting this checkbox reveals management options and allows
further configuration
• Reinitialize controller on next profile application—If this checkbox is selected, it erases all existing logical
drives the next time your customer applies the server profile
• Import existing logical drives—Existing logical drives are discovered and added to the server profile. This
operation supports multiple logical drives as long as there is only one logical drive for each drive array
• Write cache—This option allows your customer to configure write cache. When Managed manually is selected,
it indicates the write cache of the physical drives is managed by the user outside of HPE OneView. Write cache
can be also disabled or enabled. If your customer wants to enable or disable write cache, they must define the
logical drive to enable or disable write cache
• Configure the logical drive—This option allows your customer to create a new logical drive, using a hard disk
within a server

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 30

Adding a logical drive for an integrated controller

Adding a logical drive for an integrated storage controller

When adding a logical drive for an integrated storage controller, the following parameters are required:

• Logical drive name

• RAID level

• Number of the drives and drive technology

• Boot ability

• Acceleration settings

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 31

Configuring a mezzanine SAS controller

Configuring a SAS controller for HPE Synergy

When configuring a SAS Mezz 1 storage controller, after the controller management is enabled, the following
options must be configured:

• Controller re-initialization

• Write cache settings

• A logical drive or logical JBOD

This option shows up in a server profile or SPT only for HPE Synergy platform.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 32

Adding a logical JBOD

Adding a logical JBOD for a SAS controller

A logical JBOD uses the drives from the drive enclosures that are installed in the device bays of the enclosure and
are associated with a SAS logical interconnect. When adding a logical JBOD through a server profile, the following
parameters are required:

• JBOD name and description

• Number of the physical drives

• Drives selection method (by type or size and technology)

• Drive erase option

• Permanent/non-permanent option

When adding a new logical JBOD through a server profile, the manual drive selection is not available.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 33

Drive erase option

When your customer deletes a JBOD, this option determines if the data on the physical drives that are allocated
to the JBOD is retained or erased. When configured to Yes, it will erase the data from the physical drives in the
following way: The JBOD is deleted from the server profile, the physical drives are released from the SAS logical
JBOD, and then data is erased. When configured to No, it does not erase the data from the physical drives when
the SAS logical JBOD is deleted from the server profile.
Permanent/non-permanent option
Your customer can choose to either delete or retain the logical JBODs that are created as part of the server
profile or associated with the server profile. If they set the logical JBODs as Permanent, the logical JBODs are
retained as detached resources when they delete the enclosing server profile. If your customer does not set the
logical JBODs as Permanent, the logical JBODs are deleted when they delete the enclosing server profile, and the
data is not recoverable.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 34

Adding a logical drive

Adding a logical drive for a SAS controller

When adding a logical drive through server profile, the following parameters are required:

• Name and description of the logical drive

• RAID level of the logical drive

• Storage location

• Spare drive option, if required

• Drives selection method (by type or size and technology)

• Boot option

• Acceleration option

• Drive erase option

• Permanent/non-permanent option

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 35

RAID level
Supported RAID levels depend on the SHT and on the physical server configuration. Your customer must ensure
they have enough physical drives present for the selected RAID level. If they do not have enough drives to
support the selected RAID level, the server profile create or edit operation fails.
Storage location
An Internal location is appropriate if your customer’s server hardware has a Non-Volatile Memory Express
(NVMe)-enabled backplane connected to the server hardware SAS mezzanine controller. Logical JBODs can be
set to External only. Ensure your customer knows which controller is managing their front drives and that here
are enough drives available. The create action will fail if there are not enough internal drives.
Acceleration options
Acceleration options are available for Gen10 servers only. This setting indicates if the SmartRAID controller
should use an acceleration method to improve the performance of physical disk operations. When set to Enabled,
the SmartRAID controller uses the write cache as the acceleration method. The default is: Managed manually.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 36

SAN storage section

Enabling SAN storage management in the SPT

Associating a server profile or an SPT with a volume gives the server hardware to which the server profile is
assigned access to storage space on a SAN storage system.
The SAN Storage section defines access to SAN volumes, either private or shared. When configuring local
storage, the following parameters can be configured:

• Consistency check level

• Host OS type that will be installed in the server

Adding a volume to the SPT

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 37

There are two types of SAN-based volume to add:

• Existing volume—If this option is selected, the volume that is presented to the server must exist (it can be
either created using HPE OneView or imported from the storage system). The existing volume is attached to
the server, and if applicable, zoning is configured
• New volume—The procedure to attach a new volume created on demand is very similar to adding an existing
volume. The only difference is the volume is created on demand

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 38

Creating a new volume on demand

Adding a SAN volume through the SPT

When adding a SAN volume through a server profile:

• A volume template can be used. If a volume template is not available, all parameters must be entered manually

• A permanent option defines what will happen when a server profile is deleted

• Only private volumes can be created through a server profile

• A volume can be bootable if FC connections in a server profile are configured for boot

The permanent option works in the same way for logical JBODs and logical drives.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 39

Learning check
3. When can a logical JBOD be automatically deleted?
A. When the server profile is moved.
B. When the server profile is copied.
C. When the server profile is deleted.
D. When the server profile is edited.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 40

Boot settings section

Configuring boot settings in the SPT

The Boot Settings section allows configuration of the following parameters:

• Consistency check level

• Boot mode:

– UEFI
– UEFI optimized
– Legacy BIOS

• Secure boot:

– Managed manually
– Enabled
– Disabled

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 41

• PXE boot policy:

– Auto
– IPv4
– IPv6

• Boot order:

– Consistency check level

– Primary boot device (hard disk, PXE, SD card)
By default, server boot behavior is controlled by the server profile or SPT. The SHT determines the available
options in the server profile or SPT. HPE ProLiant Gen9 and newer servers support both Legacy BIOS and UEFI
for configuring the boot process.
Boot mode
Sets the boot mode to one of the following:

• UEFI

• UEFI optimized

• Legacy BIOS

The HPE Superdome Flex Server and HPE Superdome Flex 280 Server support only the UEFI boot mode.
If UEFI or UEFI optimized is selected, the PXE boot policy can also be specified. Additionally, the option to
manage the boot order is also available if the selected server hardware is an HPE ProLiant Gen9 and newer BL
servers. Boot order management is not available for HPE ProLiant Gen9 or newer DL rack servers.
For the UEFI or UEFI-optimized boot mode options, the boot mode choice is based on the expected OS and
required boot features for the server hardware. The UEFI-optimized boot mode reduces the time the system
spends in POST. To select the appropriate boot mode, consider the following:

• If a secure boot is required, the boot mode must be set to UEFI or UEFI optimized

• For operating systems that do not support UEFI (such as DOS or older versions of Windows and Linux), the
boot mode must be set to Legacy BIOS
• When booting Windows 7, Server 2008, or 2008 R2 using UEFI, do not select UEFI optimized

Secure boot
Secure boot is a feature of the UEFI that detects tampering with the boot loaders, firmware, and drivers by
validating their digital signatures. Secure boot ensures that the firmware, drivers, and the OS are signed
using HPE-approved keys. This check helps prevent malware and malicious software usage in customer
environments. HPE OneView manages these keys, and there is no additional action required from users.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 42

BIOS settings section

Enabling BIOS management in the SPT

The BIOS Settings section allows configuration of the server BIOS parameters through the server profile. When
your customer enables the Manage BIOS option, all default settings are applied and whatever explicit overrides
they have specified.
When editing BIOS settings through a server profile, the following parameters are required:

• Consistency check level

• Desired state of the BIOS settings

By default, BIOS settings are not managed through a server profile; however, selecting Manage BIOS enables your
customer to do so on server hardware that supports these options. If they keep the default setting and do not
select the Manage BIOS checkbox, the server profile does not contain any BIOS settings, and managing these
settings is done through the server console interface.
If your customer selects the Manage BIOS checkbox, all BIOS settings are set to their default settings. Your
customer can then edit or override these default settings through the server profile, based on the SHT associated
with the profile.
The following rules apply when managing BIOS settings through the server profile:

• The settings in the server profile are applied on the server hardware when the profile is created and applied

• The settings applied to the server hardware by the server profile are not cleared when Manage BIOS is
deselected, the server profile is deleted, or the server profile is removed from the server hardware

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 43

Editing BIOS settings in the SPT

HPE OneView has a set of default BIOS settings for the SHT. To view the complete set of BIOS settings organized
into categories, click Edit settings. Your customer can click any setting to view help text, and select the required
value for the setting. Any changes to the default settings are displayed in the BIOS Settings panel.
If your customer changes a setting through another means, such as at the server console, those settings are
overwritten by the settings specified in the server profile as soon as the server profile is reapplied to solve the
inconsistency. BIOS settings supported by the server hardware, but do not display in the Edit settings screen, are
not overwritten.
For HPE ProLiant Gen9 and newer servers, both actual and expected configuration values display. Actual settings
are the current values the server is using. The expected settings are the current values defined in the server
profile.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 44

iLO settings section

Editing iLO settings through the SPT

The Edit iLO Settings section allows configuration of the management processor. When editing iLO settings
through a server profile, the following parameters are required:

• Consistency check level

• Desired iLO state for the following sections:

– Manage administrator account—Configure the password of the predefined iLO administrator account or
delete the account
– Manage local accounts—Configure and manage the local accounts. When managed from HPE OneView, all
the local accounts on the iLO are replaced when configuring the accounts specified in the server profile
– Manage directory configuration—Configure the iLO directory (Active Directory, Lightweight Directory
Access Protocol [LDAP], or Kerberos) to enable Single-Sign On (SSO)

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 45

– Manage directory groups—Grant access to specific directory groups for the iLO on the server hardware that
is associated with the profile. When managed from HPE OneView, all the directory groups on the iLO are
replaced when configuring the directory groups specified in the server profile
– Manage iLO hostname—Configure the iLO subsystem name (hostname). When the iLO networking is
configured to use DHCP, the iLO subsystem name (hostname) is used as the Domain Name System (DNS)
name for the iLO. When Manage iLO Hostname is enabled on an SPT, your customer must include the
serverProfileName token in the hostname to ensure that each iLO has a unique hostname. The actual name of
the server profile replaces the serverProfileName token when the server profile referencing this SPT is
assigned to server hardware. The resulting hostname must match the limitations of a hostname (A to Z, a to
z, 0 to 9, and dash)
– Manage key manager—Configure the iLO key manager for secure encryption
iLO settings enable your customer to configure and manage the settings in HPE OneView instead of logging into
the iLO to apply the needed settings. These settings are included when your customer moves the profile to
another server hardware instance. They should use an SPT if they want to maintain consistent management for a
specific iLO setting across multiple iLOs.
Planning for iLO directory configuration and key management
HPE recommends that your customer plan their iLO directory configuration and key management in advance,
and test it on an iLO in the iLO interface. They should confirm that the configuration is correct before configuring
the iLO directory and key manager in HPE OneView, using the tested settings.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 46

Advanced settings section

Advanced settings in the SPT

In this section, administrator can define the following parameters:

• iSCSI initiator name—Virtual or user-defined name of the iSCSI initiator

• MAC addresses—Determines whether the server profiles created from the SPT use virtual or physical MAC
addresses:
– Virtual MAC addresses are generated by the appliance and are used by the servers. The benefit of specifying
virtual MAC addresses in an SPT is that when your customer assigns the template to a server, any server that
is inserted in that server bay uses the same MAC addresses. Thus, a server’s replacement does not affect the
data center interconnects because they do not detect any change in the MAC address
– Physical MAC addresses are reported by the server BIOS and associate a MAC address to the server. Physical
MAC addresses are burned in on the server NICs. If your customer replaces a server, the physical MAC
changes, and they must update the data center interconnects

• WWN addresses—Determines whether the server profiles created from the SPT use virtual or physical WWN
addresses (for FC networks):
– WWN addresses are generated by the appliance and are used by the servers. The benefit of specifying virtual
WWN addresses in a server profile is that when your customer assigns the template to a server, any server
that is inserted in that server bay uses the same WWN addresses. Thus, a server’s replacement does not
affect the data center interconnects because they do not detect any change in the WWN address
– Physical WWN addresses are reported by the server BIOS and associate a WWN address to the server.
Physical WWN addresses are burned in on the server NICs. If your customer replaces a server, the physical
WWN changes, and they must update the data center interconnects

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 47

• Serial number/UUID—Determines whether the server profiles created from the SPT use virtual or physical
serial numbers and universally unique identifiers (UUIDs):
– Virtual serial numbers and UUIDs are generated by the appliance and enable flexibility. The benefit of virtual
serial numbers is that when your customer uses a virtual serial number in an SPT and assigns the template to
a server bay, any server that is inserted in that server bay uses the same serial number
– Physical serial numbers are reported by the server BIOS and associate a serial number to the server

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 48

Activity: HPE OneView server profiles

Adding a connection in a server profile

HSP wants to validate their knowledge about HPE OneView server profiles. Read the statements below and
decide if they are true or false.

Feature True or False

Server profiles cannot have more than four Ethernet connections.

Only connections configured with the same speed can be configured in the same LAG.
Mapping connections to FlexNICs can be done manually.
Server profiles can be assigned to powered-on HPE Synergy compute nodes.
Servers can boot from a logical drive created, using drives from a D3940 storage module.
Firmware and drivers can be updated through the server profile only for HPE Superdome Flex.
Connection speed can be changed only when a server is powered off.
Secure boot is available when a server is booting in legacy BIOS mode.
It is possible to change the server hardware type for an existing server profile.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 49

Learning check
4. Which boot mode enables a secure boot?
A. UEFI
B. UEFI Optimized
C. Legacy BIOS
D. EFI

5. You are in a meeting with a customer, and they challenge you with a question: “We plan to present a virtual
volume from HPE Primera to HPE Synergy compute nodes. We heard that to present such a volume, we need
to power off the server. Is there a way to present a volume to the server without powering off the server?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 50

Managing server profiles

Managing a server profile using HPE OneView

Available operations on server profiles using HPE OneView include:

• Creating a server profile from a template

• Modifying a server profile/SPT

• Creating an SPT from a server profile

• Copying a server profile

• Changing the SHT and enclosure group

• Reapplying the server profile online

• Deleting a server profile

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 51

Creating a server profile from a template

Creating a server profile using SPT

To create a server profile using a template, select the template, and use the Actions menu. The administrator
must select the server hardware that will use that profile. The profile can only be assigned to a server that is
powered off. A server profile can be applied to an empty bay as well. When a server is inserted into that bay, the
server profile will be applied to this server, unless affinity is configured to the device bay and server hardware.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 52

Modifying a server profile template

Editing a server profile template

Your customer can also edit an SPT to change the settings associated with that template. To modify an SPT, your
customer should select a template, and use the Actions menu. They can edit an SPT any time after it has been
created. They can also edit an SPT that has an Error condition to make corrections. When your customer edits an
SPT, the appliance analyzes the changes and updates the template configuration. Then, all the server profiles
associated with the template are evaluated for compliance, and a notification is given indicating the number of
profiles that will be affected by the change. All profiles created from this template will become inconsistent. Your
customer can either select Update from template on the server profile screen to accept the changes from the
template, or select Edit Server Profile to perform manual edits. Some changes can be applied online, but some of
them require the server to be rebooted.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 53

Server profile inconsistent with server profile template

An inconsistent server profile with SPT

Consistency checking is the process of validating a server profile to ensure that it matches the configuration of its
parent SPT. The appliance monitors both the server profile and SPT, compares the two, and checks them for
consistency. If the server profile configuration does not match the SPT, it will be inconsistent. This server profile
state can be:

• Caused by a template change

• Caused by direct profile modification

For different sections of the profile, different levels of consistency can be configured.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 54

Fixing profile inconsistencies

Updating a server profile from the SPT

The following rules apply when resolving an inconsistency for a server profile:

• If the server profile is inconsistent, it can be updated to match the template

• Changes that require a server to be power cycled can be staged

• A profile can be updated from its template, using the appropriate option from the Actions menu

• Before updating a server profile, review the impact of the update

Your customer can use Update from template to update the configuration of the server profile to make it
consistent with its parent SPT. To bring an inconsistent (inconsistent with its template) server profile
configuration back into consistency (consistent) with the SPT, your customer must reapply the settings from the
SPT either manually or automatically. Some server profile updates can be performed automatically when the
server hardware is powered on, and some updates can only be performed when the server hardware is powered
off. Your customer can defer the automatic updates until the next hardware maintenance window, or cancel them
if they do not want to proceed with the updates.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 55

Staging server profile changes when updating from a server profile template
The staging option enables your customer to stage the changes they make when updating a server profile from
its SPT. The changes are staged until the next time the associated server hardware is powered off using HPE
OneView. To enable this option, mark the checkbox on the Update From Template dialog box of the Server
Profile Template screen.
The staging option is available only when all the following are true:

• The server profile is associated with an SPT

• The server profile is not in compliance with its SPT

• There is at least one automatic remediation

• The server profile is assigned to server hardware

• The server hardware is powered on

If an infrastructure administrator updates and stages the server profile changes, the server administrator can
apply the updates during the maintenance window automatically. The staged updates are applied automatically
when the server hardware is powered off via HPE OneView.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 56

Creating a server profile template from a server profile

Creating an SPT from an existing server profile

SPTs can be created from an existing server profile. To do so, use the following procedure:
1. From the HPE OneView main menu, select Server Profiles.
2. In the master pane, select the server profile from which you want to create an SPT.
3. Select Actions à Create template from profile.
4. Enter the data requested on the screen.
5. Click Create to complete the action, or click Create + to create another SPT.
6. In the Server Profile Templates screen, verify that the SPT(s) were created.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 57

Copying and editing a server profile

Copying and editing a server profile

A server profile can be copied to server hardware with the same SHT and in the same enclosure group. Copying a
server profile to new hardware keeps the structure of the profile, but it changes virtual IDs, such as WWNs and
MAC addresses. After editing the server profile directly, it becomes inconsistent with its SPT (if an SPT was
used).

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 58

Changing the server hardware type and enclosure group

Changing the server hardware type and enclosure group for a server profile

Server profiles can be assigned to a server with a different SHT or in a different enclosure group. Some server
profile settings may need to be adjusted when the profile is moved to a different enclosure group or SHT. In
earlier releases, OneView did not provide information about the adjustments, leaving the user to wonder what
changes were made.
When changing the SHT or an enclosure group:

• A preview option lists every setting that will be adjusted

• The list of changes can be copied to the clipboard

• After learning about the changes, the user can either accept the changes, or cancel the edit

• After the changes are accepted, the edit profile session continues

• No server profile changes are committed until the edit session ends

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 59

Reapplying the server profile online

Reapplying a server profile using HPE OneView

Your customer can reapply a server profile to resolve errors or to ensure that the server hardware configuration
matches the server profile. To reduce the time required to reapply a profile, individual components can be
omitted from the reapply operation by clearing those components from the selection list. A server profile can be
reapplied online, although some of the sections cannot be reapplied online. The Reapply option is useful for fixing
server profile connections without a multistep process.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 60

Deleting a server profile

Deleting a server profile using HPE OneView

A server profile that is no longer required can be deleted. After your customer deletes the server profile, the
server hardware is available for another server profile. Network connectivity is lost on the server if the profile had
a network configuration in it. If your customer is having connectivity issues with a server profile, or if a remove
action fails for a server profile, they can forcibly delete it from HPE OneView. Logical JBODs or SAN volumes that
are not marked as permanent are deleted together with the server profile. Deleting a server profile with SAN
volumes attached can fail if there are communication issues with the storage system.
Before deleting a profile with local storage settings, your customer should back up any important data. Logical
JBODs and logical drives on mezzanine controllers are deleted when the profile is deleted, and their data will not
be recoverable. It is also recommended that your customer create a backup of the HPE OneView appliance before
deleting such profiles as a way to recover access to the physical drives, in case the profile is deleted accidentally.
Forcibly deleting a server profile ignores any errors that might occur. This can result in the server hardware and
interconnects to be in a state that prohibits future use of the enclosure bay, or cause networking problems if
other profiles use the same MAC addresses or WWNs as this profile. After forcibly deleting a server profile, any
server hardware assigned to it appears as unassigned.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 61

Activity: Managing server profiles

Inconsistent server profile

HSP has experienced some problems with their server profiles for HPE Synergy compute nodes. What should you
recommend for each of the following problems?
1. Some server profiles are in a critical state after a LAG is configured for two connections. How can this be
fixed?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. After adding a connection in the server profile, it becomes inconsistent with the server profile template. How
can this problem be fixed without updating the server profile template?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 62

3. Some server profiles were deleted, but the volumes associated with them are still available on the storage
array. How can HSP make sure that boot volumes are deleted together with the server profiles?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 63

Learning check
6. Which statement about server profile management is true?
A. When a server profile is deleted, it can be restored within 12 hours.
B. Copying a server profile preserves the MAC addresses, but not the WWNs.
C. Reapplying a server profile can only be done if the server is powered on.
D. It is possible to create a server profile template from an existing profile.

7. You are in a meeting with a customer, and they challenge you with a question: “We need to modify some
server profiles that we created using a server profile template. We tried to modify one of them, and it became
inconsistent with its server profile template. How can we modify server profiles and avoid inconsistency
problems?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 64

Managing hypervisor cluster profiles

A hypervisor cluster profile configures hypervisor clusters and hypervisors with the help of the hypervisor
manager managing them.

Hypervisor cluster profile management using HPE OneView

Hypervisor cluster management options

The HYPERVISORS section in HPE OneView allows administrators to:

• Manage hypervisor cluster profiles

• Manage hypervisor profiles

• Add VMware vCenter® servers

A hypervisor is software deployed on a server node that creates and runs virtual machines (VMs). Hypervisors
are clustered to ensure high availability, to optimize resource utilization, and to be fault tolerant. A hypervisor
cluster profile enables your customer to deploy and manage a cluster of hypervisors running on servers managed
by HPE OneView and orchestrates a consistent configuration on a cluster of server nodes to share the same
workload.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 65

A hypervisor cluster profile and the associated SPT is used to define a consistent configuration from server nodes
to hypervisors in the cluster. The server profiles define the physical server configurations for the server nodes in
the cluster, which are derived from the hypervisor cluster profile and the associated SPT. The hypervisor profiles
define network and storage configurations for hypervisors in the cluster, which are derived from the hypervisor
cluster profile. Hypervisor network and storage configurations in the hypervisor cluster profile are defined based
on the physical server configuration to ensure a consistent configuration from the server node to the hypervisor.
Your customer can create or import a hypervisor cluster profile. A hypervisor cluster profile configures
hypervisors and the hypervisor cluster with the help of the hypervisor manager that is managing them.
The hypervisor cluster profile helps manage lifecycle operations such as growing or shrinking the cluster,
modifying configurations based on needs, consistency checks, and nondisruptive firmware updates on the server
nodes. For example, your customer can grow or shrink a hypervisor cluster by adding or removing hypervisors
from the hypervisor cluster profile. Any change in the configuration of the hypervisor cluster profile is reported as
an inconsistency. When inconsistencies are remediated, the changed configurations can be applied on the
hypervisor cluster and member hypervisors.
A hypervisor cluster profile can manage VMware ESXi-based hypervisor clusters by leveraging the VMware
vCenter server®.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 66

Hypervisor cluster profiles

Creating a hypervisor cluster profile

A hypervisor cluster profile defines consistent compute, network, and storage configuration for a cluster of
hypervisors that will share the same workload. It integrates with the external hypervisor manager software to
deploy a new hypervisor cluster or make changes to the hypervisor cluster or the hypervisor configurations. It
helps manage the configurations on the hypervisors to be consistent with the configurations in the managed
server nodes.
A hypervisor cluster profile can be created within HPE OneView, or an existing hypervisor cluster profile can be
imported to HPE OneView. A hypervisor cluster profile can be deleted from HPE OneView only, or from HPE
OneView and from the hypervisor manager. It means that your customer can delete a VMware cluster only from
HPE OneView, or from both HPE OneView and a VMware vCenter Server®.
Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 67

A hypervisor cluster profile and the associated SPT are used to define a consistent configuration from server
nodes to hypervisors in the cluster. The server profiles define physical server configurations for server nodes in
the cluster, which are derived from template configurations in the hypervisor cluster profile and the associated
SPT. The hypervisor profiles define network and storage configurations for hypervisors in the cluster, which are
derived from template configurations in the hypervisor cluster profile. The template configurations for hypervisor
networking and storage in the hypervisor cluster profile are defined based on physical server template
configurations to ensure consistent configuration from server node to hypervisor. A hypervisor cluster must be
managed by one instance of HPE OneView to avoid inconsistencies.
NOTE
The SPT must have a configured connection to the hypervisor management network for the template to be
valid for use by a hypervisor cluster profile.
Deleting a hypervisor cluster profile
The delete action in hypervisor cluster profile removes a hypervisor cluster profile. Your customer can either
delete the hypervisor cluster profile from HPE OneView and the associated cluster in hypervisor manager, or just
delete the hypervisor cluster profile in HPE OneView only, depending on the option selected during the delete
action:

• HPE OneView and the hypervisor manager—Removes the hypervisor cluster profile, the associated
hypervisor profiles, and the server profiles from HPE OneView. This option also deletes the managed
hypervisor cluster, as it removes the associated hypervisor cluster and its cluster members from the hypervisor
manager. The server hardware returns to the No Profile Applied state and is available for server profile creation
• HPE OneView only—Removes the hypervisor cluster profile and the associated hypervisor profiles from HPE
OneView. The associated server profiles are left unaltered in HPE OneView. This operation does not disrupt the
workloads running on the cluster and leaves the hypervisor cluster intact in the hypervisor manager. As the
associated hypervisor cluster profile is no longer managed from HPE OneView, the configurations on the
physical server and the associated hypervisor must be managed manually. The cluster remediation and rolling
update features are no longer applicable in HPE OneView with this option
vSAN-enabled hypervisor clusters
Starting with HPE OneView 5.0, hypervisor cluster profiles support VMware vSAN-enabled ESXi hypervisor
clusters. vSAN is configured on the ESXi hypervisor cluster. vSAN creates a single storage pool shared across all
hosts in the vSAN cluster and eliminates the need for external shared storage, thus simplifying storage
configuration and VM provisioning activities.
Your customer can import a vSAN-enabled ESXi hypervisor cluster from vCenter into HPE OneView. They can
also create the hypervisor cluster profile using an OS deployment plan and enable vSAN on the corresponding
cluster in vCenter.
The following are the vSAN configurations that must be done on the ESXi hypervisor cluster, using vCenter:

• vSAN kernel port creation on the ESXi host

• IP address assignment to the vSAN kernel port

• vSAN enablement and configuration

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 68

Hypervisor manager and hypervisor profiles

Hypervisor managers in HPE OneView

A hypervisor manager is the software for managing virtualized environments. Through the HPE OneView
Hypervisor Manager resource, your customer can create, import, configure, and manage hypervisors and
hypervisor clusters. A hypervisor manager provides the hostname and credentials to register with HPE OneView.
HPE OneView uses these details to communicate with a hypervisor manager to perform tasks such as add, edit,
and remove hypervisors or hypervisor clusters.
Your customer can register a hypervisor manager with HPE OneView by providing the hostname and credentials
in the Hypervisor Managers user interface. An administrator should ensure that the vCenter server user has the
necessary privileges.
A hypervisor profile contains the configurations intended for a hypervisor running on server hardware managed
by HPE OneView. The hypervisor is a member of a cluster managed by HPE OneView, and it provides the
virtualized compute, network, and storage resources to the cluster. Using the hypervisor profile, your customer
can power on the hypervisor, reset the hypervisor, place the hypervisors into maintenance mode, and update
from a hypervisor cluster profile to rectify inconsistencies.
Consistency checking is the process of validating the intended configurations of the hypervisor profile with the
actual configurations of the hypervisor. If the configurations match, the hypervisor profile consistency field is set
to Consistent and is considered to be compliant. The validation also considers inconsistencies on the server
profile associated with the hypervisor profile.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 69

Activity: Meeting with the customer

Participants will work as a group on this activity. After booting a server from a SAN volume and testing the LACP
on downlinks, HSP has asked you to verify if they understand everything correctly.
Answer the following questions, and decide if the statements are true or false:
1. True or false: A server profile can only be created through a server profile template. ________________________

2. True or false: The LACP on downlinks requires an OS configuration as well. ________________________

3. How can your customer be notified that all server profiles only have connections that were defined in the
server profile template?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. True or false: After it is defined, a server profile cannot be moved to a server with a different server
hardware type. ________________________

5. How many physical functions are supported for 50 Gb network adapters? ________________________

6. Which physical function is dedicated for FCoE connectivity? ________________________

7. How many boot volumes can be configured through a server profile? ________________________

8. True or false: HPE Synergy compute nodes can have only one logical JBOD presented.
________________________

9. True or false: Both private and shared volumes can be created through a server profile.
________________________

10. What will happen when your customer modifies a server profile template?
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 70

Learning check
8. You are in a meeting with a customer, and they challenge you with a question: “In the past, we deleted a
hypervisor cluster profile from HPE OneView, and our VMware cluster was also deleted from the vCenter
Server®. Is there a way to delete such a profile from HPE OneView and preserve the VMware cluster?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

9. Which statement about a hypervisor cluster profile is true?

A. Deleting such a profile deletes the managed cluster.
B. It can be imported or created manually.
C. It can be created without a server profile template.
D. It supports only KVM hypervisors.

10. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 71

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 72

Summary
• HPE Synergy compute nodes must have a server profile defined, otherwise they will be disconnected from the
network and storage
• Creating an SPT simplifies creating server profiles and propagating changes to the server profiles

• HPE OneView can be used for multiple server profile operations. An administrator can edit and copy a server
profile, and they can also create an SPT from an existing server profile or re-parent a server profile to the new
template
• A hypervisor cluster profile enables your customer to deploy and manage a cluster of hypervisors running on
servers managed by HPE OneView

Lab exercise
Open your lab guide, and complete Lab 5: Working with HPE OneView server profiles.

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 73

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We use many HPE
management tools, and we want to know what kind of benefits HPE InfoSight for Servers can bring to our
environment.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a question: “How can the HPE iLO
management processor help us manage our environment, which has more than 1000 servers?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with HPE OneView server profiles Page 74

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products
Module 5

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 2

Learning objectives
After completing this module, you should be able to:
• Explain the HPE approach to compute management
• Describe HPE management products, including:
– iLO 5 management processor
– HPE OneView integration with VMware® and Microsoft products
– HPE OneView Global Dashboard
– HPE iLO Amplifier Pack and HPE InfoSight

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 3

Customer scenario

HSP is managing HPE Synergy using HPE OneView. HPE Synergy compute nodes are booting from a SAN, as
planned. HSP would like to learn more about HPE management tools capabilities and how these tools can help
them with daily management tasks.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 4

HPE management approach and tools

The HPE approach to compute management is continuously evolving.

Pivot from product-centric to customer-centric

Product/feature-centric features

Customer-centric needs

HPE has a wide portfolio of management tools, providing customers with many advanced management features.
When discussing management features of HPE products, focus on the customer needs, not on the set of features
of a given management product. An architect should match a specific management product with the specific
customer problem or need.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 5

HPE management products

HPE management products include:
• iLO 5 management processor
• HPE OneView integration with VMware® and Microsoft products
• HPE OneView Global Dashboard
• HPE iLO Amplifier Pack and HPE InfoSight
iLO 5 management processor

iLO 5 interface

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 6

iLO 5 provides advanced management features and functionalities, including:

• Information – iLO Overview
• System information
• Firmware management
• iLO Federation
• Power and thermal management
• Performance management
• Security management
• HPE OneView and Synergy frame information
• Lifecycle management with Intelligent Provisioning

Information

iLO Overview page

The iLO Overview page

The iLO Overview page displays high-level details about the server and the iLO subsystem, as well as links to
commonly used features.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 7

The Security Dashboard page

The Security Dashboard page displays the status of important security features, the overall security status for the
system, and the current configuration for the security state and server configuration lock features. Your customer
can use the dashboard to evaluate their configuration for potential risks. When a risk is detected, they can view
details and advice on how to improve system security.
The Session List page
The Session List page enables session management, including disconnecting a selected session.
The iLO Event Log page
The iLO Event Log page presents all events for a given management processor and provides the ability to delete
events or export them to the file or filter.
Integrated Management Log page
The Integrated Management Log (IML) provides a record of historical events that have occurred on the server.
Events are generated by the system ROM and by services such as the iLO drivers. Logged events include server-
specific information such as health and status information, firmware updates, operating system information, and
ROM-based POST codes. Entries in the IML can help your customer diagnose issues and identify potential issues.
Preventative action might help to avoid the disruption of service. iLO manages the IML, which your customer can
access through a supported browser, even when the server is powered off. This ability to view the log when the
server is off can be helpful when your customer troubleshoots remote host server issues. When the IML is full,
each new event overwrites the oldest event in the log.
Security Log page
The Security Log provides a record of the security events recorded by the iLO firmware. Examples of the logged
events include changes to the security configuration and security compliance issues. Other logged events include
hardware intrusion, maintenance, and denial of service. The Security Log provides a focused view of all recorded
security events. Some of the same events are also included in the iLO event log or IML. When the Security Log is
full, each new event overwrites the oldest event in the log.
Active Health System Log page
The Active Health System (AHS) monitors and records changes in the server hardware and system configuration.
The AHS provides:
• Continuous health monitoring of over 1600 system parameters
• Logging of all configuration changes
• Consolidated health and service alerts with precise time stamps
• Agentless monitoring that does not affect application performance
The data collected by the AHS is stored in the AHS Log. The data is logged securely, isolated from the operating
system, and separate from customer data. Host resources are not consumed in the collection and logging of AHS
data. When the AHS Log is full, new data overwrites the oldest data in the log. It takes less than five minutes to
download the AHS Log, which can then be sent to a support professional to help your customer resolve an issue.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 8

AHS collects information from seven key providers:

• Integrated Lights-Out (iLO)
• Onboard Administrator (OA)
• Agentless Management Service (AMS)
• Network Interface Controller (NIC)
• Complex Programmable Logic Drive (CPLD)
• System ROM
• Smart Array
Active Health System Viewer
The Active Health System Viewer (AHSV) is an online tool used to read, diagnose, and resolve server issues
quickly, using AHS uploaded data.
NOTE
The AHSV can be accessed using this URL: http://www.hpe.com/servers/ahsv. An HPE Passport account
is required to access this tool.

Diagnostic page
The iLO Self-Test Results section displays the results of internal iLO diagnostic tests, including the test name,
status, and notes. The tests that are run are system dependent. Not all tests are run on all systems. For your
customer to see the tests that are performed on their system, they can view the list on the Diagnostics page. If a
status is not reported for a test, the test is not listed.
In some cases, it might be necessary to reboot iLO; for example, if iLO is not responding to the browser. Using the
Reset option does not make any configuration changes, but ends all active connections to the iLO firmware. If a
firmware file upload is in progress, it is terminated. If a firmware flash is in progress, your customer cannot reset
iLO until the process finishes.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 9

System Information

System information view in iLO 5

Summary tab
The Health Summary page displays the status of monitored subsystems and devices. Depending on the server
configuration, the information on this page varies. If the server is powered off, the system health information on
this page is current as of the last power off. The health information is updated only when the server is powered
on, and POST is complete.
Processors tab
The Processors page displays the available processor slots, the type of processor installed in each slot, and a
summary of the processor subsystem.
If the server is powered off, the system health information on this page is current as of the last power off. The
health information is updated only when the server is powered on, and POST is complete.
Memory tab
The Memory Information page displays a summary of the system memory. When the server power is off,
Advanced Memory Protection (AMP) data is unavailable, and only memory modules present at POST display.
If the server is powered off, the system health information on this page is current as of the last power off. The
health information is updated only when the server is powered on, and POST is complete.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 10

Network tab
If the server is powered off, the health status information on the NIC Information page is current as of the last
power off. The health information is updated only when the server is powered on, and POST is complete.
To view a full set of data on this page, your customer should ensure that the AMS is installed and running. The
server IP address, add-in network adapters, and the server NIC status display only if the AMS is installed and
running on the server.
The information on this page is updated when your customer logs in to iLO. To refresh the data, your customer
can log out of iLO, and then log back in.
Device inventory tab
The Device Inventory page displays information about devices installed in the server. Some examples of the
devices listed on this page include installed adapters, PCI devices, SATA controllers, and Smart Storage batteries.
If the server is powered off, the health status information on this page is current as of the last power off. The
health information is updated only when the server is powered on, and POST is complete.
For older adapters that do not comply with industry-standard management specifications, the AMS is required for
obtaining the adapter firmware version, part number, serial number, and status.
For adapters that support the Field Replaceable Unit (FRU) electrically erasable programmable read-only memory
(EEPROM), iLO obtains static adapter details such as the product name and part number.
Storage tab
If the server is powered off, the system health information on the Storage Information page is current as of the
last power off. The health information is updated only when the server is powered on, and POST is complete.
To view a full set of data on the Storage Information page, ensure that the AMS is installed and running. Serial
Attached SCSI (SAS)/SATA controller information display only if the AMS is installed and running on the server.
The information displayed on this page depends on your customer’s storage configuration. Some storage
configurations do not display information for every category.
Fibre Channel adapters are not listed on this page. To view information about FC adapters, click System
Information in the navigation tree, and then click the Network tab.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 11

Firmware and OS software repository

Firmware and status in iLO 5

Firmware tab
The Firmware page displays firmware information for various server components. If the server is powered off, the
information on this page is current as of the last power off. Firmware information is updated only when the server
is powered on, and POST is complete.
Software tab
This section lists all of the software on the managed server. The list includes HPE and HPE-recommended third-
party software that was added manually or by using the Service Pack for ProLiant (SPP).
Maintenance Windows tab
A maintenance window is a configured time period that applies to an installation task. Your customer can create a
maintenance window on the Maintenance Windows tab or when they add a task to the installation queue.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 12

iLO Repository tab

The iLO Repository is a secure storage area in the nonvolatile flash memory embedded on the system board. The
nonvolatile flash memory is 4 GB in size and is called the iLO NAND. Your customer can use HPE Smart Update
Manager (SUM) or iLO to manage signed software and firmware components in the iLO Repository.
iLO, the Unified Extensible Firmware Interface (UEFI), SUM, and other client software can retrieve these
components and apply them to supported servers. Your customer can use SUM to organize the stored
components into install sets and SUM or iLO to manage the installation queue. Your customer can also add a
component to the installation queue from the iLO Repository page.
When your customer adds a component to the installation queue, a task is added to the end of the queue. After
other queued tasks are complete, the added component is installed when the installation request is detected. The
request is serviced by software that initiates updates for the component. To determine the software that can
initiate an update, your customer can check the component details on the iLO Repository and Installation
Queue pages.
If a previously queued task is waiting to start or finish, a new task might be delayed indefinitely. For example, if a
queued component is installable by the UEFI, a server restart is required before installation can start. If the server
is not restarted, the tasks that follow in the queue are delayed indefinitely.
Install sets tab
An install set is a group of components that can be applied to supported servers with a single command. SUM
determines what to install on a server and creates an install set that is copied to iLO. Your customer can view
existing install sets on the Install Sets page in the iLO web interface.
Saving an install set when your customer deploys from SUM keeps all the components on the iLO system for later
use. For example, your customer could use the saved components to restore or roll back a component version
without needing to find the original SPP.
Installation Queue tab
The Installation Queue page displays summary information for each queued task, and your customer can click an
individual task for more information.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 13

iLO Federation

iLO Federation in iLO 5

iLO uses multicast discovery, peer-to-peer communication, and iLO Federation groups to communicate with iLO
management processors on other HPE compute systems. When your customer navigates to one of the iLO
Federation pages, a data request is sent from the iLO system running the web interface to its peers, and from
those peers to other peers, until all data for the selected group is retrieved.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 14

iLO Federation enables your customer to manage multiple servers from one system using the iLO web interface.
It supports the following features:
• Group health status
• Group virtual media
• Group power control
• Group power capping
• Group firmware update
• Group license installation
• Group configuration
iLO Federation network requirements
• (Optional) iLO Federation supports both IPv4 and IPv6. If both options have valid configurations, your
customer can configure iLO to use IPv4 instead of IPv6
• Your customer should configure the network to forward multicast traffic if they want to manage iLO systems in
multiple locations
• If the switches in your customer’s network include the option to enable or disable multicast traffic, they should
ensure that it is enabled. This configuration is required for iLO Federation and other HPE products to discover
the iLO systems on the network
• For iLO systems that are separated by Layer 3 switches, your customer should configure the switches to
forward Simple Service Discovery Protocol (SSDP) multicast traffic between networks
• Your customer should configure the network to allow multicast traffic (User Datagram Protocol [UDP] port
1900) and direct HTTP (TCP default port 80) communication between iLO systems
• For networks with multiple virtual LANs (VLANs), your customer can configure the switches to allow multicast
traffic between the VLANs
• For networks with Layer 3 switches:
– For IPv4 networks—Your customer should enable Protocol-Independent Multicast (PIM) on the switch and
configure it for PIM Dense Mode
– For IPv6 networks—Your customer should configure the switch for Multicast Listener Discovery (MLD)
snooping
Multicast discovery
This enables or disables multicast discovery. The default setting is Enabled. Selecting Disabled disables the iLO
Federation features for the local iLO system. Disabling multicast discovery is not supported on Synergy compute
modules. To limit the impact of multicast traffic on a network with Synergy compute modules, adjust the IPv6
Multicast Scope and Multicast Time To Live (TTL) settings.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 15

Multicast Announcement Interval (seconds/minutes)

This sets the frequency at which the iLO system announces itself on the network. Each multicast announcement
is approximately 300 bytes. Your customer should select a value of 30 seconds to 30 minutes. The default value
is 10 minutes. Selecting Disabled disables the iLO Federation features for the local iLO system. The possible
values are:
• 30, 60, or 120 seconds
• 5, 10, 15, or 30 minutes
• Disabled
iLO Federation group characteristics
The following are the characteristics of an iLO Federation group:
• All iLO systems are automatically added to the DEFAULT group, which is granted the login privilege for each
group member. Your customer can edit or delete the DEFAULT group membership
• iLO Federation groups can overlap, span racks and data centers, and can be used to create management
domains
• Each iLO system can be a member of up to 10 iLO Federation groups
• There is no limit on the number of iLO systems that can be in a group
• Your customer must have the Configure iLO Settings privilege to configure group memberships
• Your customer can use the iLO web interface to configure group memberships for a local iLO system or a group
of iLO systems

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 16

Power and thermal management

Power Meter view in iLO 5

Server Power tab
The Virtual Power Button section on the Server Power page displays the current power state of the server, as well
as options for remotely controlling server power. System Power indicates the state of the server power when the
page is first opened. The server power state can be ON, OFF, or Reset. Use the browser refresh feature to view
the current server power state. It is rare for a server to be in the Reset state.
Power Meter tab
Power meter graphs display recent server power usage. Power history information is not collected when the
server is powered off. Graphs that include periods in which the server was powered off display a gap to indicate
that data was not collected.
The graph data is cleared when iLO is reset or the server is power cycled. For example, the data is cleared when
the Virtual Power Button Reset or Cold Boot actions are used. The data is not cleared when the Momentary Press
or Press and Hold actions are used.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 17

Power Settings tab

The Power Settings page enables your customer to view and control the power management features of the
server. The power management features on this page vary, based on the server configuration.
The Power Regulator feature enables iLO to modify processor frequency and voltage levels, based on operating
conditions to provide power savings with minimal effect on performance.
Power Regulator modes include:
• Dynamic Power Savings Mode—Automatically varies processor speed and power usage, based on processor
utilization. This option enables the reduction of overall power consumption with little or no impact to
performance. It does not require OS support. This option is supported by Intel® CPUs
• Static Low Power Mode—Reduces processor speed and power usage. This option guarantees a lower
maximum power usage value for the system. Performance impacts are greater for environments with higher
processor utilization. This option is supported by Intel® CPUs
• Static High Performance Mode—Processors run at maximum power and performance at all times, regardless
of the OS power management policy. This option is supported by Intel® and AMD CPUs
• OS Control Mode—Processors run at maximum power and performance at all times, unless the OS enables a
power management policy. This option is supported by Intel® and AMD CPUs
Power tab
The information displayed on the Power Information page varies, depending on the server type. The following
sections are possible:
• Power Supply Summary
• Power Supplies
• HPE Power Discovery Services
• Battery Backup Units
• Smart Storage Energy Pack
• Power Readings
• Power Microcontroller
If the server is powered off, the system health information on this page is current as of the last power off. The
health information is updated only when the server is powered on, and POST is complete.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 18

Fans tab
iLO supports a minimum fan speed (percentage) that prevents the installed fans from running at a speed lower
than the configured setting. When the server is running, the fans run at the configured speed or higher.
The minimum fan speed setting overrides the thermal configuration setting if the minimum fan speed is greater
than the thermal configuration value.
• Optimal Cooling—Provides the most efficient solution by configuring fan speeds to the minimum required to
provide adequate cooling
• Enhanced CPU Cooling—Provides additional cooling to the processors, which can improve performance
• Increased Cooling—Operates fans at a higher speed
• Maximum Cooling—Provides the maximum cooling available for the system
• Acoustic Noise—Sets a maximum fan speed for the purpose of lowering fan noise. Using this configuration
might result in processor throttling in some workloads. This setting is not suitable for systems with GPUs. This
setting is supported on HPE Edgeline EL1000 and HPE Edgeline EL4000 systems with HPE ProLiant m750
Server Blades
The thermal configuration setting overrides the minimum fan speed setting if the thermal configuration value is
greater than the minimum fan speed value.
Temperatures tab
The Temperature page displays the location, status, temperature, and threshold settings of temperature sensors
in the server chassis.
The circles on the temperature graph correspond to the sensors listed in the Sensor Data table. The color on the
graph is a gradient that ranges from green to red. Green represents a temperature of 0°C and red represents the
critical threshold. As the temperature measured by a sensor increases, the graph changes from green to amber,
and then to red if the temperature approaches the critical threshold.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 19

Performance management

Workload Performance Advisor in iLO 5

Settings tab
Selected HPE Gen10 and later servers support the following server performance management and tuning
features:
• Workload matching—Your customer can use preconfigured server profiles to maximize application
performance
• Jitter smoothing—Your customer can use the Processor Jitter Control Mode setting to level and balance
frequency fluctuation (jitter) resulting in lower latency
• Core boosting—Your customer can enable this feature to produce higher performance across more active
processor cores. This feature is supported on Gen10 servers only; it is not supported on Gen10 Plus servers
If your customer resets iLO to the factory default settings, all performance management settings and data are
deleted. When they use the iLO backup and restore feature, the performance management settings are
retained. The collected performance data is not backed up or restored.
• Performance monitoring—Your customer can view performance data collected from supported sensors on
servers with Innovation Engine support. They can configure alerts, based on the collected data
• Workload advisor—Your customer can view selected server workload characteristics. They can view and
configure recommended performance tuning settings, based on the monitored data
Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 20

Monitoring tab
The Performance - Monitoring page displays performance data collected from the following sensors on servers
with Innovation Engine support:
• CPU Utilization—This sensor reports the utilization of all processors installed in the system. The measurement
is based on a percentage of the maximum compute capacity of the processor. It considers how slow or fast the
processor runs when doing work. This measurement might differ from the values that some operating systems
report for utilization, which is often calculated by how often the processor is idle
• Memory Bus Utilization—This sensor reports the utilization of the total bandwidth of the memory bus. The
measurement is based on a percentage of the maximum memory bandwidth of the configuration. This
measurement might differ from the values that some operating systems report for memory utilization, which is
often calculated by how much of the available system memory is being used or allocated
• IO Bus Utilization—This sensor reports the utilization of all processors connected to IO buses (total PCI
Express [PCI-e] bus bandwidth). The measurement is based on a percentage of the maximum total bandwidth
of these buses. This measurement is not an indication of how busy an IO device might be, but rather how much
PCI-e bandwidth the device is using
• CPU Interconnect Utilization—This sensor reports the calculated bandwidth usage of the link connecting
multiple processor sockets in the system. It is an aggregate of all the links within the system
• Jitter Count—This sensor reports the rate of processor frequency changes or "jitter" that occurs on a per-
second basis
• Average CPU Frequency—This sensor reports the average overall processor frequency. A value of zero means
that the processor is idle. This value is different from the "running frequency" often seen under some operating
systems that measure frequency only when the processor is not idle
• CPU Power—This sensor reports the power consumed by the processor. It is based on an energy accumulator
within the processor and is the value that the processor uses to regulate power limits internally
The information on this page might differ from the Total CPU power data on the Power Meter page, which is
obtained without using the Innovation Engine.
Workload Advisor tab
iLO monitors selected server workload characteristics and provides recommended performance tuning settings,
based on the monitored data. Workload characteristics are qualitative assessments of how the workload is using
system resources. They are based on the quantitative measurements from the performance monitoring events
and are useful as a reference when making tuning decisions. These observed characteristics are typically needed
for making intelligent tuning decisions. For instance, a specific BIOS option might provide benefits only if the
workload has a high degree of non-uniform memory access (NUMA) awareness.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 21

Security management

Security settings in iLO 5

Access Settings tab

The default access settings values are suitable for most environments. The values your customer can modify on
the Access Settings page allow customization of the iLO external access methods for specialized environments.
The values your customer enters on the Access Settings page apply to all iLO users.
iLO Service Port tab
The Service Port is a USB port with the label iLO on supported servers and compute modules. When your
customer has physical access to a server, they can use the Service Port to do the following:
• Download the AHS Log to a supported USB flash drive
• Connect a client (such as a laptop) with a supported USB to Ethernet adapter to access the following:
– iLO web interface
– Remote console
– iLO RESTful API
– CLI
– Remote Insight Board Command Language (RIBCL) scripts
Secure Shell Key tab
This section allows authorizing a new Secure Shell (SSH) key by using the web interface and other operations,
such as viewing and deleting SSH keys.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 22

Certificate Mappings tab

The Certificate Mappings page displays the local users of the system and their associated SHA-256 certificate
thumbprints. Your customer should use the controls on this page to add or delete a certificate.
In a smartcard or Common Access Card (CAC) environment, local users must have a smartcard certificate saved
and mapped to their user account to enable smartcard access.
CAC/Smartcard tab
A CAC is a United States Department of Defense (DoD) smartcard for multifactor authentication. CACs are issued
as standard identification for active-duty military personnel, reserve personnel, civilian employees, non-DoD
government employees, state employees of the National Guard, and eligible contractor personnel. In addition to
its use as an ID card, a CAC is required for access to government buildings and computer networks.
Each CAC carries a smartcard certificate that must be associated with your customer’s local user account in the
iLO web interface. They should upload and associate their smartcard certificate with their account by using the
controls on the Certificate Mappings page.
CAC authentication with Lightweight Directory Access Protocol (LDAP) directory support uses a service account
to authenticate to the directory service, and the user account must be present in the same domain as the
configured directory server. Additionally, the user account must be a direct member of the configured groups or
extended schema roles. Cross-domain authentication and nested groups are not supported.
SSL Certificate tab
The Secure Sockets Layer (SSL) protocol is a standard for encrypting data so that it cannot be viewed or
modified while in transit on a network. An SSL certificate is a small computer file that digitally combines a
cryptographic key (the server public key) with the server’s name. Only the server itself has the corresponding
private key, allowing for authenticated two-way communication between a user and the server.
A certificate must be signed to be valid. If it is signed by a Certificate Authority (CA), and that CA is trusted, all
certificates signed by the CA are also trusted. A self-signed certificate is one in which the owner of the certificate
acts as its own CA.
By default, iLO creates a self-signed certificate for use in SSL connections. This certificate enables iLO to work
without additional configuration steps.
Directory tab
The iLO firmware supports Kerberos authentication with Microsoft Active Directory. It also supports directory
integration with an Active Directory or OpenLDAP directory server.
When your customer configures directory integration, they choose between schema-free and HPE Extended
Schema configurations. HPE Extended Schema is supported only with Active Directory. The iLO firmware
connects to directory services by using SSL connections to the directory server LDAP port.
Your customer can enable the directory server certificate validation feature by importing a CA certificate. This
feature ensures that iLO connects to the correct directory server during LDAP authentication.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 23

Configuring the authentication and directory server settings in iLO is one step in the process of configuring iLO
to use a directory or Kerberos authentication. Additional steps are required to set up your customer’s
environment to use these features.
Encryption tab
HPE iLO Standard, that comes with every Gen10 or later server, gives customers the ability to configure servers
in one of three security states. With an iLO Advanced license, customers that need the highest-level encryption
capabilities of Commercial National Security Algorithm (CNSA) have a fourth security state available to them.
As you move up the scale in security, the server enforces stronger encryption rules for web pages, SSH, and
network communications. Note that both ends of each network connection must support the encryption rules, or
they cannot communicate, and some interfaces are shut down to limit potential security threats. The following
security states are available:
• Production
• High Security
• Federal Information Processing Standards (FIPS)
• CNSA
HPE SSO tab
HPE SSO enables your customer to browse directly from HPE SSO-compliant applications to iLO, bypassing an
intermediate login step. To use this feature, your customer must:
• Have a supported version of an application that is HPE SSO-compliant
• Configure iLO to trust the SSO-compliant application
• Install a trusted certificate if the CAC Strict Mode is enabled
iLO contains support for HPE SSO applications to determine the minimum HPE SSO certificate requirements.
Some HPE SSO-compliant applications automatically import trusted certificates when they connect to iLO. For
applications that do not perform this function automatically, your customer should use the HPE SSO page to
configure the SSO settings.
Login Security Banner tab
The Login Security Banner feature allows your customer to configure the security banner displayed on the iLO
web interface and HTML5 standalone remote console login pages. The security banner is also displayed when
your customer connects to iLO through an SSH connection. For example, your customer could enter a message
with contact information for the owner of the server.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 24

HPE OneView and Synergy frame Information

Frame view in iLO 5

The Frame Information page provides information about the frame that contains the Synergy compute module,
which includes the iLO processor. The following frame details are available:
• FRAME HEALTH—The frame health status
• FRAME UID LIGHT—The state of the frame UID LED. The UID LED helps identify and locate a frame
• SERVER LOCATION—The bay number of the compute module in the frame
• ALLOCATED POWER—The maximum allocated power for the compute module when it is powered on
• FRAME SERIAL NUMBER—The frame serial number
• FRAME UNIQUE ID (UUID)—The frame UUID

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 25

Lifecycle management with Intelligent Provisioning

Lifecycle management with Intelligent Provisioning through iLO 5

Intelligent Provisioning tab

Always On Intelligent Provisioning is a web interface your customer can use to perform OS deployments and
review hardware configuration details.
Decommission tab
If your customer wants to decommission a server or prepare it for a different use, they can use the One-button
secure erase feature.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 26

Backup & Restore tab

Backup and restore can be performed automatically or manually:
• Automatic backup and restore—When iLO goes through the initialization process, it backs up the
configuration information stored in the battery-powered SRAM memory device to the nonvolatile flash memory
(NAND). If the SRAM is erased or data corruption is detected, iLO tries to restore the configuration information
from the backup file. Automatic restore operations are recorded in the IML. When iLO security is disabled with
the system maintenance switch, the SRAM data is not restored automatically. The backup file created by the
automatic backup and restore process is not user accessible. It cannot be used to perform a manual restore
operation
• Manual backup and restore—iLO supports manually restoring the configuration information stored in the
battery-powered SRAM memory device. This feature is intended for use on a system with the same hardware
configuration as the system that was backed up. It is not meant to duplicate a configuration and apply it to a
different iLO system

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 27

Demo: Active Health System Viewer

Active Health System Viewer

Your Instructor will demonstrate how to use the AHSV, which can be used to analyze information collected in
HPE Active Health System Log.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 28

Learning check
1. You are in a meeting with a customer, and they challenge you with a question: “How can the HPE iLO
management processor help us manage our environment, which has more than 1000 servers?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 29

HPE OneView integration with VMware and Microsoft products

HPE OneView provides the ability to integrate it with vCenter Server® and Microsoft System Center.
HPE OneView for VMware vCenter Server

HPE OneView for VMware vCenter Server plug-in installed

HPE OneView for VMware vCenter (OV4VC) seamlessly integrates the manageability features of HPE ProLiant,
Synergy, BladeSystem, and Virtual Connect with VMware solutions. Your customer can gain deep control of their
virtualized HPE infrastructure environment, reducing the time it takes to make important changes, increase
capacity, or manage planned and unplanned downtime. When used with the automation power of HPE OneView,
best practices for a converged infrastructure can be defined once and reused many times to provision an entire
cluster with compute and storage fully configured in five easy steps.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 30

Integrations for VMware vRealize Operations™, vRealize Log Insight™, and vRealize Orchestrator™ are also
available, and they deliver powerful analytics and deeper troubleshooting tools to your customer’s VMware
administrators. Seamlessly integrate HPE converged management with VMware management solutions:
• Perform integrated OS, driver, and firmware updates with VMware vSphere® Lifecycle Manager™
• Simplify administration with VMware console access to HPE infrastructure management
• Reduce downtime by automating responses to hardware events with the support of VMware Proactive HA
• Proactively manage changes with detailed relationship dashboards
• Maintain stability and reliability with online firmware inventory and deployment
• Leverage deep analytics and troubleshooting, using integrations with VMware vRealize Operations and Log
Insight
Integrations for VMware vRealize Orchestrator (VRO) provide an easy-to-use, drag and drop access to
automation of HPE OneView-managed hardware deployment, firmware updates, and other lifecycle tasks, using
VRO.
HPE OV4VC Server offers the following benefits:
• Ability to use different types of view:
– Hardware overview
– Firmware inventory
– Network ports
– Fabric diagram
– Enclosures
– Alerts
– Proactive high availability (HA)
– Launch iLO, OA, HPE OneView
• Ability to perform some configuration tasks:
– Grow/edit/shrink/import/remove clusters
– Cluster-aware firmware updates
– Host and cluster consistency check and remediation
– OS deployment

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 31

Separation of server and storage modules

Storage Integration Pack for VMware vCenter view in the vCenter Server

Up to version 9.6, HPE OV4VC was a combined plugin between HPE Servers (OneView) and HPE Storage.
Starting with HPE OV4VC 10.0, the storage components have been removed from OV4VC and are packaged
separately as Storage Integration Pack for VMware vCenter. Currently, to enable server and storage management,
your customer has to deploy two virtual appliances: one for server management and a second one for storage
management.
When upgrading from an older HPE OV4VC 9.x version, the HPE OV4VC 10.x STAR file can be used to
seamlessly update from existing 9.5.1 or 9.6 versions. After the upgrade, any HPE Storage components
configured in the old versions are removed, but all of the previous server configurations are retained.
The OV4VC 10.x backup and restore is only supported only with 10.x releases. A backup from 9.x cannot be
restored with 10.x.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 32

HPE OneView requirements for managing devices

HPE OneView credentials in the vCenter Server

In HPE OV4VC 9.3 and older, it was possible to connect to a server’s HPE iLO directly, without having to have
OneView present. Starting with HPE OV4VC 9.4, all servers, enclosures, and Virtual Connect devices must be
managed by HPE OneView.
Under Administration, the HPE Server Integration tab changed to HPE OneView Credentials. Users are no longer
able to provide separate HPE iLO, OA, and Virtual Connect credentials—only HPE OneView credentials. OV4VC
reports an error when trying to manage non-OneView managed devices. HPE OV4VC supports HPE OneView
Standard licenses for basic inventory and health but requires HPE OneView Advanced licenses for most other
functionality (server profiles, diagram view, and so on). Customers requiring non-OneView managed device
support can stay on OV4VC 9.3.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 33

HPE Server Hardware—Network Diagram

Network Diagram view in the vCenter Server

The Network Diagram page under the Monitor tab for HPE Server Hardware displays a graphical representation
of the network topology of the server and provides the following information:
• Port status—The network diagram provides a visual indication of HPE OneView Interconnect port connectivity
status. A cross mark against any port implies that the port is disconnected
• VMkernel ports—This provides information about the physical IP addresses configured on the port
• Port Telemetry—This provides the telemetry information about the HPE OneView interconnect ports. To view
telemetry for the interconnect port, hover the mouse over the interconnect port to display a graph which
contains the following information:
– The data transfer rate is in Kilobits/sec, Megabits/sec, or Gigabits/sec
– The blue line displays transmitted (out) data through the port over time
– The green line displays the received (in) data through the port over time
• Link Aggregation Groups support—If your customer has configured Link Aggregation Groups (LAGs) on the
client system, the network diagram supports display of LAGs
Your customer can also export the network diagram, save it in .png format, and view the network diagram as and
when required.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 34

Import Cluster

Importing a cluster using the vCenter interface

A cluster-level action can be performed to import any unmanaged vCenter cluster (for example, existing clusters)
into HPE OneView. After the cluster is imported and managed by HPE OneView, an administrator can perform
Grow Cluster, Edit OS Deployment plan, and Shrink Cluster operations on the cluster, using HPE OneView.
Importing a cluster is a nondisruptive action. Any inputs selected are not applicable to existing hosts and are only
used for future deployments. After successfully importing a cluster, the cluster consistency is calculated against
the selected SPT and the current host configuration settings. If there are any inconsistencies, click Apply
recommended action to make it consistent.
The following rules apply when importing a cluster:
• The cluster must have one or more hosts. Empty clusters are not supported
• The cluster is not managed by HPE OV4VC
• The vCenter Server is registered as the hypervisor manager to HPE OneView
• DHCP settings are not supported. Set all the host management network kernel ports to static IP settings. If the
management port is set to DHCP, importing a cluster will fail, and the clusters will be in an inconsistent state
Import cluster is a task that can be run to import an existing cluster into HPE OneView, and apply a HPE OneView
Server Profile Template. It brings the cluster under HPE OneView cluster management.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 35

This enables existing clusters to use the grow/shrink cluster tasks, and enable cluster consistency check and
remediation (including cluster aware firmware updates).
This feature requires HPE Synergy and Virtual Connect (since that is the HPE OneView requirement). It will not
work with DL-based clusters.
Un-Import Cluster

Un-importing a cluster from the vCenter interface

Running this task removes the cluster from HPE OneView cluster management and deletes the HPE OneView
Hypervisor Cluster Profile. This leaves the cluster and hosts intact, and the cluster and host information is still
available in OV4VC. This is useful if your customer wants to try out the HPE OneView Cluster Profile Template
management, but decides to remove or reconfigure it later.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 36

Grow Cluster

Growing cluster with HPE Synergy compute node

Using the Grow Cluster feature, your customer can create or expand the capacity of an existing cluster. The Grow
Cluster option uses HPE OV4VC OS build plans or Image Streamer OS build plans for deployment of VMware
ESXi™ on the HPE Server.
Your customer can grow a cluster using an SPT. It ensures that appropriate network interfaces, active IP pools,
and other configuration parameters remain in sync at the time of cluster expansion. HPE OneView supports
common host network configuration. It supports HPE OneView SPTs to obtain the OS build plans to execute
deployment to the target hardware. This ensures a successful addition of the host to the vCenter cluster with ESX
deployment.
The following rules apply when growing a cluster:
• The deployment option with HPE OneView for VMware works only when NIC0 of the server profile is
configured with a network that has connectivity to the HPE OneView server provisioning component
• The preceding network can act as a vCenter management network or your customer can configure a unique
vCenter management network on any of the NICs
• Your customer must enter a valid static IP from the vCenter management network for the host to be discovered
in the vCenter Server
• The Grow Cluster option is supported only with HPE OneView-managed servers
HPE OV4VC can also be used to shrink clusters. The Shrink Cluster wizard removes individual hosts from HPE
OneView cluster management and returns them to bare metal. The hypervisor cluster profile for this host is
deleted and all of the non-permanent resources like SAN volumes or logical JBODs are also deleted.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 37

Update cluster firmware baseline

Updating logical enclosure firmware, using the vCenter Server interface

VMware vSphere Lifecycle Manager (vLCM) is the current version of Update Manager that enables centralized,
automated patch and version management for VMware vSphere. It offers support for VMware ESXi hosts, virtual
machines (VMs), and virtual appliances. With VMware vSphere Lifecycle Manager, an administrator can upgrade
and patch ESXi, and update third-party software on hosts. vLCM can also perform firmware updates on hosts, the
OS, drivers, and software updates.
The HPE OneView Hardware Support Manager (HSM) plug-in for VLCM integrates with HPE OV4VC and allows
administrators to update server firmware and drivers in the same maintenance window as the ESXi server OS
updates, with a single reboot, if possible.
To deploy on multiple servers at the same time from the vCenter Server, three important image parameters must
be defined:
• The ESXi version that will be used to patch/update the OS on the host
• The vendor add-on, which is an HPE bundle of software
• The firmware and drivers add-on, which is the SPP firmware baseline that is created in HPE OV4VC Pack
The host OS can be installed with either a VMware Image or an HPE VMware custom image. The Image selection
options for a cluster or a host on the VLCM include a Base Image, Vendor add-on (optional), and the Firmware
and Driver add-on. The host can be set up with an HPE custom image or a VMware base image, but only a
VMware base image must be used when adding an image to the image depot in vLCM.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 38

If the host OS is installed with the VMware image, two remediations are required:
• To install the software and HPE drivers from the vendor add-on
• To install the firmware and driver add-on
Your customer can access HPE logical enclosures directly from the HPE Infrastructure Lifecycle Manager. In using
these HPE logical enclosures, your customer can understand the history of the firmware, set the firmware
baseline, and update the firmware to higher versions for a required SPP.
HPE OV4VC uses HPE OneView as a firmware repository. Adding firmware bundles to the firmware repository
enables your customer to deploy them across their environment.
The following prerequisites must be met when configuring the HPE OneView HSM plug-in for VLCM:
• SPP with the supported ESXi version 7.0 or from Gen10 Plus (2020.10.0) or later. The HPE OneView HSM
plug-in can be used to upgrade servers where the installed version is SPP 2019.03 and higher
• All the Gen10 or later servers managed by HPE OneView are supported
• Before remediation operations can be performed from VLCM, your customer should ensure that AMS is running
and Integrated SUT (iSUT) mode is set to AutoDeploy on ESXi

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 39

Proactive HA

Enabling Proactive HA on the cluster level

The Proactive HA feature is available with HPE OV4VC and can be used to deliver the OneView hardware status
of clustered hosts. The list of hosts can be checked with the vCenter Managed Object Browser to determine if
they are being monitored by the OneView provider. Administrators can choose from a broad range of failure
conditions for OV4VC to monitor, including issues with memory, storage, networking adapters, fans, and power.
When OV4VC informs vCenter of an issue, the cluster can then move VMs to other hosts or take another
remediation action, as specified in the cluster HA settings.
The Proactive HA feature migrates VM workloads, based on hardware health and prevents downtime by
automatically moving affected workloads before hardware causes a failure. The HPE Provider has predefined
rules and conditions that trigger live migration or other remediation options.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 40

The automation level can be configured to one of these states:

• Manual—vCenter Server presents migration recommendations for VMs
• Automated—VMs are automatically migrated to healthy hosts and degraded hosts enter into a quarantine or
maintenance mode
Remediation can be configured to one of these states:
• Quarantine mode for all failures—Balances performance and availability by avoiding the usage of partially
degraded hosts, provided that VM performance is unaffected
• Quarantine mode for moderate and Maintenance mode for severe failure (Mixed)—Balances performance
and availability by avoiding the usage of moderately degraded hosts, provided that VM performance is
unaffected. Ensures that VMs do not run on severely failed hosts
• Maintenance mode for all failures—Ensures that VMs do not run on partially failed hosts

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 41

HPE Storage Integration Pack for VMware vCenter

HPE Storage Integration Pack for VMware vCenter plug-in installed

The HPE Storage Integration Pack for VMware vCenter is the redesigned version of the HPE OV4VC plug-in.
Along with the new name, it features a brand-new user interface that more seamlessly integrates with vCenter
and centralizes all HPE Storage functionality on one page. It enables vSphere administrators to quickly obtain
context-aware information, and manage supported HPE Storage devices in their VMware vSphere environment
directly from within vCenter. This plug-in operates independently of HPE OneView and does not require a license
to use.
HPE Storage Integration Pack for VMware vCenter offers the following benefits:
• Simplified administration through integration of the physical and virtual infrastructure
• Accurate problem indicators through the hardware events generated in the VMware vSphere management
console
• Single-click launch of trusted HPE management tools from the vSphere dashboard
• Ability to proactively manage or view changes with detailed relationship dashboards for storage
• Simplified on-demand storage provisioning
• Visualization of complex configuration

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 42

Storage Integration Pack for VMware vCenter features

All HPE Storage Actions

Using the Storage Integration Pack for VMware vCenter, an administrator can:
• Create a VMFS datastore
• Configure vVols
• Create a VM from a template
• Schedule a VMFS datastore snapshot
• Schedule a VM snapshot

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 43

HPE OneView integrations for Microsoft System Center

HPE OneView integration with Microsoft System Center

HPE OneView for Microsoft System Center is a fully integrated product that unifies the management of physical
and virtual IT environments, including servers, storage, network devices, and software. It combines an integrated
set of HPE extensions with Microsoft System Center to bring the native manageability of HPE Servers and
Storage systems to Microsoft System Center environments. HPE OneView for Microsoft System Center provides
comprehensive lifecycle management of HPE converged infrastructure directly from the System Center consoles.
HPE OneView for Microsoft System Center:
• Is ideal for customers who have standardized on Microsoft System Center as their management platform
• Integrates directly into System Center consoles
• Leverages the HPE OneView and HPE Synergy infrastructure automation engine
• Reduces complexity by using the same System Center tools for HPE management tasks
• Simplifies the admin learning curve by using the System Center tools with which they are already familiar

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 44

HPE OneView integrations for Microsoft

HPE OneView integrates with Microsoft System Center Server to deliver powerful HPE hardware management
capabilities directly from System Center consoles for comprehensive system health and alerting, driver and
firmware updates, OS deployment, detailed inventory, and HPE fabric visualization. Integration with additional
components provides additional benefits:
• Simplify administration with single-console access to health, inventory, and configuration monitoring
• Reduce planned and unplanned downtime with detailed resolution information for health alerts
• Take control by launching trusted HPE management tools in context
• Proactively manage changes with detailed insight into the relationship between the physical and virtual
infrastructure—from the VM to the network edge
• Consistent and repeatable bare-metal server deployment
• Maintain stability and reliability of the environment with simplified driver and firmware updates
• Long-term event correlation and trend analysis

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 45

Learning check
2. Which statement about HPE OneView for VMware vCenter® Server is true?
A. It requires one license per managed server and vCenter Server instance.
B. It can be used to grow or shrink a VMware cluster after proper integration.
C. It requires a dedicated VMware cluster with HA and DRS configured.
D. It can be used to manage a VMware cluster after proper licensing.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 46

HPE OneView Global Dashboard

HPE OneView Global Dashboard is delivered free of charge in the form of a virtual appliance.
HPE OneView for large, mixed, and distributed environments

HPE OneView Global Dashboard vs. HPE OneView

The HPE OneView Global Dashboard extends a unified view across multiple data centers anywhere in the world,
providing a simple, efficient, and unified view of the shared storage pools and the health status of servers,
profiles, and enclosures. This means better infrastructure visibility and more informed, faster decision making.
The HPE OneView Global Dashboard provides a unified view of health, alerting, and key resources managed by
HPE OneView. Administrators can access systems across multiple appliances and data center sites. The software
supports the following hardware:
• HPE BladeSystem c7000 enclosure
• HPE ProLiant DL series rack-mount servers
• HPE Synergy
• HPE Apollo 2000, 4000, and 6000
• HPE SimpliVity
Resource changes are updated in real time in Global Dashboard. A full refresh of all resources occurs
approximately every 12 hours. (HPE SimpliVity does not provide real-time updates. Data is collected
automatically every 15 minutes.) Global Dashboard provides quick access to resources by providing links to the
relevant page on the appliance. User roles ensure that only approved users can access monitored appliances.
After approved users log in to Global Dashboard, single sign-on (SSO) is enabled for links between Global
Dashboard and the HPE OneView appliance. SSO is not supported for HPE SimpliVity.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 47

Activity: Licensing management products

iLO licensing information

HSP plans to purchase additional hardware, and they want to make sure that all management products for the
new infrastructure are licensed appropriately. HSP plans to buy the following components:
• 3 HPE Synergy frames
• 30 HPE Synergy 480 Gen10 Plus compute modules
• 2 HPE Virtual Connect SE 100 Gb F32 modules for HPE Synergy (for Ethernet and FC connectivity)
• 2 HPE Primera arrays
• 2 HPE Composer2 modules
• 45 HPE ProLiant DL345 Gen10 Plus servers
• Two HPE Superdome Flex systems, each based on 4 chassis

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 48

One of the priorities for HSP is to manage all components using HPE OneView, but they want to use other
management products as well. For each of the HPE management products, enter the total number of licenses
required to manage all the components.

Feature Total number of licenses

HPE OneView Advanced

HPE OneView for VMware vCenter Server
FC Upgrade
HPE OneView Global Dashboard
HPE iLO Advanced

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 49

Learning check
3. Which statement about HPE OneView Global Dashboard is true?
A. It requires one license per managed server.
B. It is deployed as a virtual appliance.
C. It does not support HPE SimpliVity.
D. It cannot be deployed to VMware ESXi™ systems.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 50

iLO Amplifier Pack and HPE InfoSight

HPE offers advanced management tools like HPE InfoSight together with iLO Amplifier Pack.
iLO Amplifier Pack description

iLO Amplifier Pack benefits

iLO Amplifier Pack is an inventory, firmware, and software update management tool from HPE. It can discover
and inventory up to 10,000 servers providing your customer with a detailed server inventory and downloadable
reports. The massive scale enables your customer to view their complete inventory and keep their servers up to
date from a single dashboard.
Typically, in an enterprise data center environment, it is not desirable to have every server communicate through
the firewall to a cloud-based solution or service that resides outside of it. An on-premises aggregator ensures that
there is a single point of egress from the customer’s environment. The iLO Amplifier Pack is used as an on-
premises aggregator for HPE InfoSight for Servers. The iLO Amplifier Pack is a virtual appliance available as a
free download. The iLO Advanced license on managed servers may be required to complete certain tasks.
iLO Amplifier Pack is the HPE deployment engine for updating firmware, drivers, agents, and configuration tools
for Gen8, Gen9, and Gen10 and later HPE ProLiant servers (rack, tower), HPE Blade servers, and HPE Synergy
servers. iLO Amplifier Pack provides a browser-based GUI as well as a CLI.
iLO Amplifier Pack discovers supported servers and retrieves a detailed inventory from the iLO management
processor. The inventory includes firmware, software, and hardware details that can be viewed and downloaded
from the GUI.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 51

In addition to the integrated hardware and software discovery engine that finds the installed hardware and
current versions of firmware and software in use on target servers, iLO Amplifier Pack installs updates in the
correct order and ensures that all dependencies are met before deploying an update. It also minimizes downtime
by deploying all updates while the target servers are online, limiting the downtime to a single reboot in most
cases.
iLO Amplifier Pack supports both online and offline modes for updates. It leverages SUT for online firmware and
driver updates while allowing the servers to be rebooted independently. It can also be used for offline firmware
updates that involve powering off the servers before updates.
iLO Amplifier Pack supports a feature called Server System Restore that provides users the ability to recover a
system that has corrupt or compromised firmware. The product allows your customer to associate a recovery
policy with each server under its management. This policy enables a user to specify the firmware configuration
settings and a bootable .ISO file that can be used to initiate the user-defined recovery of the OS, layered products
on the OS, as well as data recovery.
OS baseline
OS baselines are user-created, bootable .ISO images that are used in the server system restore process to recover
the OS, layered applications, and data restore from backups. Your customer should use the Import Baseline
feature to import operating system .ISO images for server system restore. iLO Amplifier Pack supports baseline
storage up to 80 GB (which includes both firmware and OS baseline files). The percentage of space used is
displayed at the top of the OS Baseline page.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 52

iLO Amplifier Pack Dashboard

iLO Amplifier Dashboard

The search bar on almost every iLO Amplifier Pack Dashboard screen instantly gets your customer the
information they need for increased productivity, with search support for all the elements in their inventory (for
example, to search for alerts).
The iLO Amplifier Pack management appliance is delivered as a virtual appliance, running in a VMware ESXi VM.
The appliance is OS agnostic with the capability to manage servers, running both Windows and Linux operating
systems, from the iLO management processor. iLO Amplifier Pack management appliance upgrade support is also
provided to help existing users easily update to the latest version of the appliance.
The iLO Amplifier Pack management appliance is security hardened with limited open ports and limited access to
the command prompt. Sensitive data on the appliance is encrypted, and data downloaded from the appliance is
encrypted by default (for example, backup files).
iLO Amplifier Pack appliance backups can be taken from within the tool, and a new appliance can be restored
using these backups. The appliance backup stores configuration, settings, and server credentials, which are
encrypted. The inventory data is not stored in persistent storage and is rediscovered when iLO Amplifier Pack is
restored.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 53

There are no additional licenses required to use iLO Amplifier Pack. It can be deployed in a VMware, Windows, or
Linux hypervisor. After deploying iLO Amplifier Pack, a first-time setup needs be performed to get it up and
running. iLO Amplifier Pack can be used to rapidly discover and inventory supported HPE Servers using either
IPv4 addresses or existing iLO Federation groups. Detailed hardware and firmware inventory is available for all
discovered servers.
The iLO Amplifier Pack Dashboard provides a visual snapshot of the health status of discovered servers with the
ability to click down into additional details. All server events, iLO Amplifier Pack logs, and task statuses can be
viewed from the GUI.
iLO Amplifier Pack leverages and extends the HPE Smart Update portfolio of SPP and SUM for breakthrough
system maintenance at the scale of your customer’s data center. iLO Amplifier Pack and SPP provide capabilities
to systematically update HPE ProLiant servers with one-click simplicity. Multiple servers or iLO Federation
groups can be updated in one task, and iLO Amplifier Pack automatically batches update tasks when large
number of servers are selected for updates.
The Trusted Platform Module (TPM), when used with BitLocker, measures a system state and, upon detection of
a changed ROM image, restricts access to the Windows file system if the user cannot provide the recovery key.
iLO Amplifier Pack detects if the TPM is enabled and provides the user and option to override.
iLO Amplifier Pack supports firmware updates of iLO and other firmware components (system ROM,
Programmable Logic Device [PLD]) directly from the Actions menu. It also supports online deployments of
firmware for Windows and Linux operating systems. iLO Amplifier Pack uses Smart Update Tool (SUT) and
Agentless Management Service (AMS) for online updates, and the latest versions of these components need to
be installed on the managed server. Some components updates may require server reboots to activate SUT and
AMS, which can be done at convenient times from the iLO Amplifier Pack GUI.
Conversely, iLO Amplifier Pack supports offline deployments of all firmware without requiring installation of AMS
or SUT on the managed server. Offline updates are OS agnostic and can be used to update firmware on servers
with or without an OS.
Standardized reports are available to users of iLO Amplifier Pack. A predefined list of reports is available from the
GUI, and these reports can be viewed in the GUI or exported to a CSV file. Predefined reports include:
• Firmware Report
• iLO License Report
• Basic Device Report
• Hardware Inventory Report
Users can customize reports and download them as well. In addition, device driver details can be included in the
custom reports.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 54

HPE InfoSight

HPE InfoSight architecture and flow

HPE InfoSight is a cloud-based, machine learning solution. Every second, it collects and analyzes millions of
sensors from systems across the globe, allowing customers to take advantage of the global learnings from this
data. HPE has been at the forefront of this new data paradigm, and a decade ago, started designing systems with
sensors across the infrastructure stack.
The iLO Amplifier Pack provides a mechanism by which ProLiant servers’ information is passed from a customer
site to the HPE InfoSight backend.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 55

Wealth of server health and performance data

HPE InfoSight building blocks

HPE InfoSight for Servers combines the cloud-based machine learning of HPE InfoSight with the health and
performance monitoring of AHS and HPE iLO. While the capture of health and telemetry data at the individual
server level has been around since AHS was introduced in Gen8 with iLO 4; the difference with HPE InfoSight for
Servers is that this data is now collected automatically and used in a proactive manner.
AHS files contain system health, hardware configuration, firmware and driver details, diagnostic telemetry, and
performance information. AHS also records and timestamps hardware changes as well as firmware, driver, and
software updates. It does not record or collect any personally identifiable information or network security
information. The collection of AHS data is performed by iLO, the management processor, and does not consume
any host resources.
AHS data is collected once per day for every server being monitored by HPE InfoSight for Servers, which is
available at no cost. Basic monitoring and health information is offered for free while more advanced
functionalities require an active server warranty or support contract.
HPE InfoSight for Servers sees beyond the limits of humans and other tools because of its unique approach to
data collection and analysis. It continuously learns from the telemetry to develop an understanding of the ideal
operating environment and combines this with the real-world operational expertise developed by support and
product R&D teams. HPE InfoSight for Servers eliminates time wasted on the maintenance of infrastructure and
delivers insights to predict and prevent problems.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 56

Predictive analytics and global learning

HPE InfoSight for Servers is being constantly enriched with learnings from the installed base as predictive
signatures that detect, predict, and prevent problems before they can affect your customer’s business.
Simplified operations
As a cloud-based application, HPE InfoSight streamlines operations and provides administrators with a one-stop,
one-site portal for easy access to a consolidated view of the infrastructure—wherever it is in the world.
Improved support
While prediction and prevention of issues is critical, HPE InfoSight for Servers is also focused on streamlining and
enhancing the overall support experience.
HPE InfoSight features
HPE InfoSight features include:
• Automatic collection of sensor and telemetry data—AHS files no longer have to be reactively downloaded
and made available to support teams for troubleshooting. For servers connected to HPE InfoSight for Servers,
the AHS files are collected automatically and made available to HPE Support along with insights from InfoSight
• Analyze AHS logs—An individual AHS file can also be uploaded to preview HPE InfoSight for Servers
capabilities and view hardware configuration details, firmware and driver information, and Wellness Alerts. After
analysis, if applicable, it creates support cases for servers under a valid warranty or support contract. To enable
automatic collection of AHS files and to take advantage of the complete feature set, servers must be registered
on HPE InfoSight for Servers
• Wellness Dashboard—When predictive signatures are detected in the AHS data sent across from servers, they
are captured as Wellness Alerts on the Wellness Dashboard. The Wellness Dashboard has a tabular summary by
category and severity, along with a detailed report that timestamps the alert along with symptoms, device
details, causes, and recommended actions. Wellness Alerts pertaining to a server are also listed in the Wellness
Alerts tab in the drilldown view of that particular server. Examples of Wellness Alerts include:
– Detection of hardware failures
– Notifications for certain critical firmware upgrades
– Firmware version recommendations, based on known problematic configurations
– Detection of power faults
– Security setting notifications, and so forth
• Automatic case creation—For a particular set of Wellness Alerts, HPE InfoSight for Servers has the ability to
create a support case automatically and return the support case ID for further tracking. This requires a one-
time configuration from the Wellness Dashboard. This feature is only supported on servers with an active
warranty/support contract and is currently available on supported Gen10 and Gen10 Plus servers, excluding
HPE Edgeline Systems and HPE Synergy compute nodes

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 57

Example 1: Support for part failures

HPE InfoSight operation example: Support for part failures

HPE InfoSight has the ability to detect several parts/hardware failures. When a hard drive failure occurs, HPE
InfoSight analyzes the corresponding IML event in the AHS data and generates a Wellness Alert with details
about the impacted server and recommended action. The remediation for that problem is that the customer is
notified, and an automatic support case is generated.
Example 2: Prevention of drive failure and data loss

HPE InfoSight operation example: Prevention of drive failure and data loss

A critical HPE SAS SSD firmware upgrade was released to prevent drive failure at 32,768 hours of operation. HPE
InfoSight proactively analyzes AHS data and identifies servers that have SSD drive models impacted by the issue
and requiring an immediate upgrade. The remediation is that directions and download links are provided for a
firmware upgrade.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 58

Example 3: Detection of dictionary attacks

HPE InfoSight operation example: Detection of dictionary attacks

For one of the servers, multiple failed iLO login attempts occurred in a very short time, and these multiple failed
login attempts detected during the sampling interval exceeds the defined threshold. The remediation is to review
the iLO Event Log to identify the source of the failed login attempts.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 59

Activity: Meeting with the customer

Participants will work as a group on this activity. After explaining how HPE management tools can help HSP to
perform daily operations, HSP has asked you to verify if they understand everything correctly.
Answer the following questions, and decide, if the statements are true or false:
1. True or false: HPE OneView for VMware vCenter Server requires a license for each server.
________________________

2. True or false: HPE InfoSight supports HPE Servers and Storage systems. ________________________

3. Which component is required to use HPE InfoSight for Servers?

__________________________________________________________________________________________________________

4. True or false: HPE OneView Global Dashboard supports HPE SimpliVity nodes. ________________________

5. What must be registered within vCenter Server to use the HPE Storage Integration Pack for VMware vCenter
to create a vVols datastore?
__________________________________________________________________________________________________________

6. Which action must be taken prior to growing a cluster, using HPE OneView for VMware vCenter Server?
__________________________________________________________________________________________________________

7. What is the maximum size of an Active Health System Log supported by the viewer?
__________________________________________________________________________________________________________

8. True or false: All servers using HPE OneView for VMware vCenter Server must be managed using HPE
OneView. ________________________

9. True or false: A single iLO management process can be a member of 25 iLO Federation groups.
________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 60

10. What is the main functionality of the Proactive HA feature?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Learning check
4. You are in a meeting with a customer, and they challenge you with a statement: “We use many HPE
management tools, and we want to know what kind of benefits HPE InfoSight for Servers can bring to our
environment.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

5. Which component is required to use HPE InfoSight for Servers?

A. HPE OneView Global Dashboard
B. iLO Amplifier Pack
C. HPE OneView for VMware vCenter Server
D. iLO Advanced license

6. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 61

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 62

Summary
• HPE provides many management tools that are designed to solve specific customer problems
• HPE iLO and other management tools provide comprehensive management functionalities for HPE compute
systems

Lab exercise
Open your lab guide, and complete Lab 6: Configuring iLO Federation.

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 63

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We want to protect virtual
machines by configuring a high-availability cluster, but we have VMware Standard licenses that do not
support this feature.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a statement: “We want to deploy a vSAN
for remote offices, but we cannot deploy three ESXi systems per office.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing HPE compute products Page 64

3. You are in a meeting with a customer, and they challenge you with a statement: “We want to simplify the
update process for ESXi systems, including updates of vendor-specific components and the VMware Tools
update.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. You are in a meeting with a customer, and they challenge you with a question: “We standardized on HPE
equipment, and we want to simplify our vSAN expansion. How can HPE help us achieve this goal?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization
workloads
Module 6

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 2

Learning objectives
After completing this module, you should be able to:
• Recommend and explain foundation VMware® virtualization components and technologies
• Configure a two-node virtual SAN (vSAN) setup and vVols
• Introduce VMware solutions certified on HPE compute resources

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 3

Customer scenario

HSP plans to use HPE OneView for VMware vCenter Server® to deploy a VMware ESXi™ system and manage
VMware clusters. They plan to leverage vSAN capabilities in remote offices, but they need to first understand the
underlying VMware technologies and features. HSP wants to leverage available VMware solutions certified on an
HPE compute solution and has asked you for more information.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 4

Foundation VMware virtualization components and technologies

VMware virtualization products are fully supported on the HPE Synergy platform and other HPE compute
products like HPE Superdome Flex and HPE ProLiant servers.

VMware ESXi Hypervisor

Host summary view in the vCenter Server

A hypervisor is responsible for abstracting a server’s physical hardware and creating a virtual machine (VM)
process that provides an environment into which regular unmodified operating systems can be installed. This is a
key point: the OS being installed into a VM has no knowledge that it is running in a VM rather than in real
physical hardware, and this means that VMs can run the majority of x86/x64 compatible operating systems.
A hypervisor allows multiple VMs to share physical hardware. ESXi provides physical resources to the VMs:
• CPU
• Memory
• Network
• Storage
These resources are shared between all VMs running on the ESXi system. The VMs do not have direct access to
the physical resources.
Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 5

VMware vCenter Server

vCenter Server Management interface

Management of the VMware platform can be done using vCenter Server or through direct connection to the ESXi
server. Direct management of the ESXi servers is not very effective as a new session must be opened for each
ESXi server. Typically, direct connection to the ESXi server is used when vCenter Server is not available for some
reason. vCenter Server is a central management system for VMware infrastructure.
vCenter Server is licensed per instance. It serves not only as a management interface for many ESXi servers, but it
also enables a significant number of advanced technologies like:
• High-availability (HA) cluster
• Distributed Resource Scheduler (DRS) cluster
• VMware vSphere® vMotion®
• VMware vSphere Distributed Switches™
Typically, one vCenter Server is enough (it can manage up to 2500 ESXi servers and 40,000 powered-on VMs).
Multiple vCenter Servers can be deployed to maintain different sets of ESXi hosts or to provide disaster recovery
(DR) features: one vCenter Server installed in a primary location and another vCenter Server installed in a DR site.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 6

Starting from version 7.0, vCenter Server is available only as a virtual appliance, running on top of a Linux system.
vCenter Server runs a set of services providing different functionalities. vCenter Server services include:
• VMware vCenter Server
• VMware vSphere Client
• VMware vCenter Single Sign-On
• License service
• Content library

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 7

VMware licensing

Features enabled on the ESXi system

ESXi is licensed per socket. One license is required for each CPU up to 32 cores. Each processor license covers a
CPU with up to 32 cores. If the CPU has more than 32 cores, additional licenses are required. ESXi offers flexible
licensing with different sets of features included. Your customer may choose between the following VMware
editions:
• vSphere Standard—Provides an entry-level solution for basic server consolidation to reduce hardware costs
while accelerating application deployment
• vSphere Enterprise Plus—Offers the full range of vSphere features for transforming data centers into
dramatically simplified cloud infrastructures, and for running modern applications with the next generation of
flexible, reliable IT services
• vSphere Essentials—Delivers the industry-leading virtualization platform for small businesses at an affordable
price. It includes six CPU licenses of vSphere Essentials (for three servers with up to two processors each) and
one license for vCenter Server Essentials
• vSphere Essentials Plus—Provides business continuity with a smaller IT footprint, which reduces overall
hardware costs. This license includes support for HA clusters, VMotion, vSphere Replication, and VMware
vShield Endpoint
ESXi and vCenter Server is available for evaluation for 60 days. After the evaluation period, all ESXi systems are
disconnected from the vCenter Server, and it is not possible to power on VMs, although all running VMs continue
to run.
Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 8

Accessing an individual ESXi server

Host client used to manage ESXi system

Small virtualization environments may have just a few ESXi systems. To manage a single ESXi server, your
customer should use the host client, which is a process running on ESXi itself. It is accessed using a web browser,
and it provides basic management of the virtualization features and one-to-one connectivity. This means that for
each ESXi host, a new web browser session must be opened. A host client is also used when vCenter Server is not
available.
It is also possible to manage ESXi using a CLI, such as ESXCLI or PowerCLI.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 9

Accessing the VMware vCenter Server

vSphere Client view

A vCenter Server can be accessed using:
• vSphere Client™—A vCenter Server can be accessed using vSphere Client, which is based on HTML5. This
client provides full functionality to manage a virtual environment
• PowerCLI—VMware PowerCLI is a collection of PowerShell modules, providing many cmdlets to manage a wide
range of VMware products, including vCenter Server. PowerCLI is widely used to automate environments

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 10

Navigating in vCenter

Four inventory views in the vCenter Server

vCenter Server, through vSphere Client offers four major views:

• Hosts and Clusters—This view presents all ESXi system clusters, including the relationship between them and
VMs
• VMs and Templates—This view presents all VMs and templates, but without presenting the relationship
between VMs/templates and ESXi system/VMware cluster
• Storage—This view presents all the datastores available to any ESXi system managed through the vCenter
Server
• Networking—This view presents all networking components:
– Port groups from standard switches
– Distributed switch components

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 11

VMware datastore

Creating VMFS datastore

A datastore is a logical container used to store VMs, templates, and ISO images. The most popular type of
datastore is the Virtual Machine File System (VMFS) datastore. To create a VMFS datastore, your customer needs
a FC, Fibre Channel over Ethernet (FCoE), direct-attached storage (DAS), or an Internet Small Computer Systems
Interface (iSCSI) logical unit number (LUN). Any of the supported LUNs can be used to create a VMFS partition
used by ESXi hosts.
A datastore can be local or shared. A local datastore is accessible by a single system only, while a shared
datastore can be accessed simultaneously by multiple hosts. It is not recommended to store a VM on the local
datastore, as it cannot be migrated using vMotion, it is not protected by an HA cluster, and it will not be included
in the load balancing procedures of the DRS cluster.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 12

Other types of datastores:

• vSAN—This is a shared datastore type built on local storage. Storage capacity attached directly to the servers
is converted to a shared datastore
• vVols—This technology allows vSphere hosts native access to the storage. There is no need to configure LUNs.
Instead, your customer creates a disk group on the storage array and accesses it natively. Every object stored
on a vVol will be stored in a dedicated volume, where each of them can have a different storage policy
• NFS—This type of datastore just points to an exported NAS folder. In other words, this is a folder located on a
NAS device that is mounted to multiple ESXi servers
For a vSphere environment, it is recommended to use VMFS datastores whenever possible as a VMFS datastore is
optimized for storing and accessing large files. The maximum size of the datastore is 64 TB, and it can be
achieved with a single logical drive, or up to 32 logical drives (extents).
If your customer decides to use NFS datastores, which are ideal for storing VM files, keep in mind that not all
versions of NFS support all functions.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 13

VMware networking

Virtual switches view in vCenter Server

VMware supports two types of virtual switches: the standard vSwitch and the vSphere distributed switch (VDS).
Standard vSwitch
A vSwitch is responsible for connecting VMs to each other and to the data center LAN. When your customer
defines a vSwitch on an ESXi host, they can associate one or more physical NICs with that switch. The vSwitch
owns those NICs—no other vSwitch is allowed to send or receive traffic on them. Your customer should define a
new vSwitch for every set of NICs that they want to devote to a specific purpose. For example, if your customer
wants to use a pair of NICs for traffic associated with one tenant's VMs and a different pair of NICs for another
tenant's VMs, they should define two vSwitches. However, if your customer wants the tenants to share physical
NICs, they should connect them to the same vSwitch, using port groups to separate them.
In the vSphere client, adding a port group is referred to as adding a network of the VM type. The port group
defines settings such as the NIC teaming policy, which determines how traffic is distributed over multiple physical
NICs associated with the vSwitch and the VLAN assignment. The port group controls traffic shaping settings and
other features such as promiscuous mode.
When your customer deploys a VM, they can add one or more vNICs to the VM, and connect each vNIC to a port
group. Each vNIC connects to a virtual port on exactly one port group on one vSwitch. A standard vSwitch is
always defined at the host level.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 14

vSphere distributed switch

A VDS provides a centralized way to manage network connections, simplifying the administrators’ duties and
reducing these risks. The management plane for the VDS resides centrally on the vCenter Server. There, your
customer can create distributed port groups, which include the familiar VLAN and NIC teaming policies. Your
customer should also define a number of uplinks, based on the maximum number of physical NICs that a host
should dedicate to this VDS.
Your customer deploys the VDS to hosts, each of which replicates the VDS in its hypervisor. The individual
instances of the VDS hold the data and control plane, and perform the actual switching. When your customer
associates a host to the VDS, they must associate a physical NIC with at least one uplink. Each uplink can be
associated with only one NIC, but if the VDS has additional uplinks defined, your customer can associate other
physical NICs with them. The multiple NICs act as a team much as they do on an individual virtual switch, using
the settings selected on the VDS centrally.
The VDS’ distributed port groups are available on the hosts for attaching VMs or VMkernel adapters. Note that
for vSphere Distributed Switches, the VMkernel adapter attaches to a distributed port group, rather than directly
to the switch.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 15

Activity: VMware licensing

VMware licensing guide

Participants will work by themselves on this activity. During this activity, you will work with the VMware licensing
guide.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 16

1. Open the VMware-Edition-Comparison.pdf file, located in your class package.

2. What is the minimum license version that supports each of the following?
a. HA cluster ________________________________________________________________________

b. DRS cluster ________________________________________________________________________

c. Distributed switches ________________________________________________________________________

d. FT for VMs with eight vCPUs ________________________________________________________________________

e. vMotion ________________________________________________________________________

f. vVols ________________________________________________________________________

g. Host profiles ________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 17

Learning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We want to protect virtual
machines by configuring a high-availability cluster, but we have VMware Standard licenses that do not
support this feature.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 18

VMware vSAN and vVols

VMware provides advanced storage technologies like vSAN and vVols.
VMware vSAN introduction

vSAN architecture

VMware vSAN provides a software-defined storage (SDS) solution that supports the storage needs of VMs in a
vSphere cluster and provides support for key vSphere capabilities such as VMware vSphere vMotion, VMware
vSphere HA, and VMware vSphere Distributed Resource Scheduler™ (DRS). vSAN aggregates the local server
storage of multiple HPE servers within a vSphere cluster into a shared storage pool that is available to all hosts
within that vSphere cluster. HDDs and flash-based storage, such as SSDs, PCIe accelerators, and NVMe storage
from servers in a vSAN-enabled vSphere cluster contribute to the performance and capacity of the vSAN solution.
VMware vSAN, as its name implies, provides an alternative to traditional shared storage solutions, such as iSCSI,
FC, and FCoE, by utilizing the local storage available to each HPE server in the vSphere cluster. vSAN enables
customers to seamlessly extend virtualization to storage, creating a hyperconverged solution that simply works
with their existing tools, skillsets, software solutions, and hardware platforms. Operations become easier with
fewer tasks and intelligent automation that can be managed through one tool and a unified team, allowing
customers to respond to business demands faster and more intelligently. vSAN also helps enterprises prepare for
tomorrow’s IT demands—whether expanding to the public cloud or rapidly deploying the latest flash and server
technologies.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 19

Data access
When configuring a vSAN, vSphere administrators define disk groups in the VMware vSphere Client. Up to five
disk groups can be configured on a VMware ESXi host in a vSAN cluster, with each disk group comprising one
caching tier SSD and up to a seven-capacity tier HDDs/SSDs. Each disk group is presented as a vSAN shared
datastore that is used to store VM objects such as virtual disks, configuration files, and snapshots.
The data on a vSAN datastore is accessed using one of two methods. If the requested data is local to the host,
then the IO is serviced directly from the local disks. However, if the data is remote, then the data is read from, or
written to, the remote host over the Ethernet network. In a hybrid configuration, the SSDs in the caching tier form
a caching layer with 70 percent dedicated for read cache and 30 percent for write buffer. In an all-flash
configuration, the caching tier only serves as a write buffer, while the capacity tier is used for read cache and
storing data. The read cache keeps a list of commonly accessed disk blocks to reduce IO read latency. If the
requested block is not in cache, it is retrieved directly from the capacity layer.
It is important to note that a host can access the read cache of all hosts in the same cluster. vSAN maintains a
directory of cached blocks that can be referenced to find the requested block and then retrieved over the vSAN
network. Write operations go into the write buffer first and are later destaged to the disks in the capacity layer.
When a write is initiated, it is sent to the local cache on the host and to the write cache on a remote host. In the
event of a failure, this ensures a copy of the data is available. After those writes land on both hosts, the write
operation is acknowledged back to the application. The data is then destaged to the capacity layer at regular
intervals.
High availability
vSAN HA is implemented by replicating the data to one or more additional hosts within the vSAN-enabled
cluster. In addition to acting as read/write cache, the SSDs in the caching layer also support the vSAN replication
activities by acting as the initial write copy target for the replicated data. vSAN provides the ability for an
administrator to define the number of complete mirror copies of data, referred to as replicas, within the vSAN
cluster. The administrator defines the desired number of replicas on a per-VM basis, which provides the flexibility
to adjust the desired level of protection, based on the criticality of the VM data.
Scale-out storage
As new HPE servers are added into a vSAN cluster, the potential capacity of existing shared datastores is
increased. vSAN 6.x and newer supports up to 64 nodes. In addition to extending existing shared datastores,
scale out is possible by creating new datastores through the addition of new hosts into the cluster, by adding
additional disks into existing members of the cluster, or by a combination of these two options. Depending on the
vSphere administrator’s preference, the configuration and addition of the new storage can be performed
automatically by VMware vCenter Server or manually by the administrator.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 20

vSAN cluster requirements

vSAN architecture with disk groups exposed

vSAN supports shared datastores and key vSphere capabilities such as VMware vSphere vMotion, vSphere HA,
and vSphere DRS. However, there are some limitations that should be considered when determining the
appropriate storage solution for a customer environment.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 21

Key limitations and requirements include:

• vSAN does not support Distributed Power Management (DPM)
• Based on the cluster size, disk group, and disk count restrictions, there is a physical limit to the capacity
support of a vSAN configuration
• vSAN and VMware NSX® can coexist on the same vSphere infrastructure, but NSX does not support vSAN
network traffic
• vSAN supports a two-host architecture with a witness node
• A dedicated network for vSAN traffic is required
• An appropriate number of vSAN licenses are required
• vSAN requires a minimum of three vSphere hosts in each cluster, with a maximum of 64 hosts. For remote
office/branch office [ROBO] deployments based on two nodes, two nodes plus a witness is supported
• vSAN storage is only available to the hosts within the vSAN cluster
• There can be up to 200 VMs per host in vSAN 6.x and newer
• HPE Synergy systems with direct-attached storage (DAS) systems are supported in vSAN 6.x and newer
vSAN also has specific hardware requirements:
• Each vSAN node providing capacity to the vSAN cluster must provide SSD capacity for caching and SSD/HDD
capacity for data
• Each vSAN node should have a RAID controller configured in pass-through mode
• A host can support up to five disk groups (each disk group supports one flash device for caching and up to
seven capacity drives). The minimum setup needs one caching device and one capacity drive
• In a hybrid deployment, cache capacity should be at least 10% of the capacity provided by the disk group

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 22

Two-node vSAN cluster with witness node

Enabling vSAN services on VMWare cluster

A minimum of three hosts are required for a standard vSAN cluster, although in a two-node cluster your customer
can have two hosts with an external witness. A vSAN Witness Host is a dedicated ESXi host (may be a physical
ESXi host or a vSAN Witness Appliance), whose purpose is to host the witness component of vSAN objects. This
minimum configuration only allows for a single host failure.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 23

vSphere vVols

vVols architecture

VMware vVols are a vSphere storage architecture that was created to replace the existing VMFS and NFS
implementations that have been used since ESX was first launched. vVols creates a unified standard and
architecture for all storage vendors and storage protocols to adhere to, and it leverages the vSphere APIs for
Storage Awareness (also known as VASA) to accomplish this.
vVols enable vSphere to write VMs natively to storage arrays without using any kind of file system. With vVols,
common storage management tasks are automated, eliminating dependencies to provide more simplified
management. vVols are designed to be dynamic and efficient where no storage is preprovisioned, and data is
thinly written when VMs are created. It provides finer control of storage resources and data services at the VM
level. This eliminates the need for any LUN provisioning and enables storage arrays to automatically reclaim
space when VMs are deleted or moved to another storage device.
vVols allow storage arrays to be VM-aware, and array features can be applied directly to individual VMs instead
of entire LUNs, which provides more flexible consumption of storage resources with greater granularity for
increased efficiency. To accomplish all of this, vSphere Storage Policy-Based Management is used to allow policies
built based on array capabilities to be assigned to VMs.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 24

vVols terminology includes:

• Virtual volume—This is a container encapsulating VM files, virtual disks, and their derivatives. A single VM can
use multiple virtual volumes for different objects
• VASA Provider—A VASA Provider is the software component that mediates out-of-band communication
(control path) for vVols traffic between VMware vCenter Server, VMware ESXi hosts, and a storage array. The
VASA Provider passes information about storage topology, capabilities, and status to vCenter Server and ESXi
hosts. A VASA Provider can reside either within a storage array or be external on a physical server or VM
• Protocol endpoint—ESXi hosts do not have direct access to vVols on a storage array and instead must use a
logical IO proxy that is referred to as a protocol endpoint to communicate with vVols. The protocol endpoint
serves as the data path between ESXi hosts to VMs and their respective vVols. Storage arrays that support
multiple storage IO paths and storage protocols (that is, FC, iSCSI, and NFS) can have multiple protocol
endpoints that point to the same storage container
• Storage container—Instead of using LUNs that are configured on the storage array, vVols use storage
containers, which are pools of raw storage capacity that become a logical grouping of vVols. All vVols are
created inside the storage container. Storage containers are not visible via the in-band data path. The VASA
Provider manages storage containers and reports their existence to the vCenter Server and ESXi hosts via the
out-of-band control path
• Storage policy—The storage profile is a set of rules that define quality of service (QoS) requirements for VMs,
based on the different capabilities provided by the physical storage array. These can be used to perform
placement decisions, admission control, QoS compliance monitoring, and dynamic resource allocation
management of storage resources
• Storage capabilities—These are a specific set of array attributes the VASA Provider feeds to vSphere. They
are used to define policies/levels of service such as RAID level, thin provisioning, drive types, Zero Detect,
snapshots, and more
Before configuring vVols at a customer site, verify interoperability of this technology with other components that
your customer plans to use. Not all applications fully support vVols in the same way that they support normal
datastores. For example, Veeam does not support backup from storage snapshots for vVols, and this is a
consideration that should be made when planning this type of deployment.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 25

How vVols transforms storage in vSphere

Storage transformation with vVols

VMFS is LUN-centric. Storage pools are siloed away from VMware management, and because the storage array
cannot see inside the VMFS datastore, it can only apply features to the entire LUN. For example, array-based
snapshots are a great value add to a VMware environment, but with VMFS, the array must take a snapshot of the
entire LUN. Customers cannot set up different snapshot policies for different VMs. vVols, on the other hand,
break down the siloes, and array services are aligned to VMs. Because vVols let arrays see VMs as objects, arrays
can apply features on a granular basis, based on the customer's needs and priorities.
With VMFS, storage volumes are preallocated, which typically means that customers must over-provision
resources, which leads to inefficiency. However, with vVols vSphere, administrators can dynamically allocate
storage when they need it.
With VMFS, it is complicated to provision storage, as it requires vendor-specific tools for the storage array. vVols
provides simple provisioning and management through vSphere interfaces. vSphere administrators can easily add
a vVol datastore, based on a vVol created on an HPE Storage array, and attach the datastore to ESXi hosts. The
LUNs are managed in the background, making the process much simpler and more intuitive for non-storage
experts.
In addition to reducing the lengthy VMFS provisioning processes, vVols enable vSphere to automate actions on
selected HPE Nimble arrays. For example, when a vSphere administrator deletes a VM, the array automatically
reclaims space.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 26

Simplified vVols setup with HPE Storage integration Pack

Creating a storage container using HPE Storage Integration Pack

The HPE Storage Integration Pack for VMware vCenter (SIPVC) 10.0 is the redesigned version of the HPE
OneView for VMware vCenter plug-in. Along with the new name, it features a new UI that more seamlessly
integrates with vCenter and centralizes all HPE Storage functionality on one page. It enables vSphere
administrators to obtain context-aware information quickly, and manage supported HPE Storage devices in their
vSphere environment directly from within vCenter. This plug-in operates independently of the HPE OneView
product and does not require a license to use.
The SIPVC further simplifies the setup steps of vVols from directly within the vCenter interface.
When creating a vVols datastore using SIPVC, the following steps must be completed:
1. Create a VASA certificate.
2. Enable the VASA Provider service, and register with vCenter.
3. Create the storage container and vVols datastore.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 27

Learning check
2. You are in a meeting with a customer, and they challenge you with a statement: “We want to deploy a vSAN
for remote offices, but we cannot deploy three ESXi systems per office.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

3. Which statement about a vSAN witness node is true?

A. It requires a full license like a standard member of the vSAN cluster.
B. It is a virtual machine running a nested ESXi hypervisor.
C. It is a service started using a vCenter Server management interface.
D. It must be added to the vSAN cluster like a regular node.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 28

VMware solutions certified on HPE compute resources

VMware solutions such as VMware Cloud Foundation™ are certified on HPE compute solutions.

VMware and HPE

VMware and HPE collaboration benefits

HPE and VMware have been collaborating on delivering solutions for their customers for more than 20 years.
With the delivery of HPE Synergy, the world’s first composable infrastructure solution, HPE made it even easier
for HPE VMware customers to move to a software-defined infrastructure (SDI).
The two companies have also collaborated to help their customers simplify their hybrid cloud environments. By
integrating VMware Cloud Foundation (VCF) and HPE solutions, the two companies have made it easier to
design, install, validate, deploy, and manage a hybrid cloud solution.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 29

VMware Cloud Foundation 4 with Tanzu

VMware Cloud Foundation architecture

VMware Cloud Foundation (VCF) is a hybrid cloud platform that can be deployed on premises as a private cloud
or can run as a service within a public cloud. This integrated software stack combines compute virtualization
(VMware vSphere), storage virtualization (VMware vSAN), network virtualization (VMware NSX), and cloud
management and monitoring (VMware vRealize® Suite) into a single platform.
In the version 4 release of VCF, VMware added Tanzu, which embeds the Kubernetes runtime within vSphere.
VMware has also optimized its infrastructure and management tools for Kubernetes, providing a single hybrid
cloud platform for managing containers and VMs.

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 30

vSAN ReadyNode

vSAN ReadyNode benefits

HPE vSAN ReadyNode provides customers with the fastest path to optimized workloads, delivered on platforms
that provide broad scalability and flexibility for each unique environment. The end-to-end solutions are covered
by HPE Proactive Care support provided by HPE, taking into account VMware software licenses. All support for
HPE-branded VMware licenses is provided by HPE. HPE vSAN ReadyNode can be based on ProLiant DL or HPE
Synergy systems.
Key features and benefits include:
• Optimized solutions—Each vSAN ReadyNode offering is optimized to provide ideal performance on the
following workloads:
– Virtualization—This offering is optimized for heavily virtualized and/or web infrastructure environments,
making this solution ideal as a computing power add-on to increase output in media streaming, web serving
services or to manage IT infrastructure
– Data management and processing—This offering provides a solution to data storage aimed at optimizing
data management and analytics. With high disk throughput and low latency, this solution is a useful addition
for a variety of storage structures
– Accelerated Infrastructure—This offering comes graphics ready to optimize next-generation compute
performance via dedicated coprocessors. This is a useful addition for high-end 2D/3D visualization or virtual
desktop infrastructure (VDI)
• Data warehousing—This offering provides the storage needed to assist with heavy collaboration and data-
intensive or large analytics processing environments. Optimized for capacity with additional expansions slots
available, vSAN ReadyNode is geared to handle a wide range of storage requirements
• Custom and scalable build—All nodes default to a configuration optimized for both cost and performance;
however, each has a full suite of options to upgrade. The customer can tailor each server to fit their specific
environment
• Factory built—The hardware is assembled and configured in the HPE Factory, using extensively tested
configuration guidelines

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 31

Activity: Meeting with the customer

Participants will work as a group on this activity. After explaining how VMware technologies work, HSP has asked
you to verify if they understand everything correctly.
Answer the following questions, and decide if the statements are true or false:
1. True or false: vSAN ReadyNode from HPE is based on HPE Synergy and HPE ProLiant servers.
________________________

2. True or false: There is only one type of datastore available for ESXi systems. ________________________

3. What is the maximum number of nodes supported in a VMware vSAN cluster? ________________________

4. True or false: vSphere Distributed switches are created using vCenter Server. ________________________

5. Which VMware license is required to enable a DRS cluster? _________________________________________________

6. Which additional component is required to deploy a two-node vSAN cluster? ______________________________

7. What is the maximum size of a VMFS datastore? ________________________

8. True or false: To setup vVols, Enterprise Plus is required. ________________________

9. True or false: vCenter Server is licensed per instance. ________________________

10. Which component is required to configure a VMware cluster? _________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 32

Learning check
4. You are in a meeting with a customer, and they challenge you with a question: “We standardized on HPE
equipment, and we want to simplify our vSAN expansion. How can HPE help us achieve this goal?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

5. Which statement about HPE OneView for VMware vCenter Server is true?
A. It requires one license per managed server and vCenter Server instance.
B. It can be used to grow or shrink a VMware cluster after proper integration.
C. It can be installed on a Linux or Windows operating system.
D. It can be used to manage a VMware cluster after proper licensing.

6. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 33

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 34

Summary
• VMware provides a comprehensive virtualization solution for any workload and customer size
• A vSAN can be configured using only two nodes and a witness node. This deployment model is dedicated for
ROBO environments. The HPE Storage Integration Pack for VMware vCenter simplifies the vVols configuration
process and other storage-related operations
• Multiple VMware solutions are supported on an HPE compute solution, including standard virtualization
components, VMware Cloud Foundation, or dedicated VDI solutions. HPE also offers vSAN ReadyNode to
simplify the purchase process

Lab exercises
Open your lab guide, and complete:
• Lab 7: Working with HPE OneView for VMware vCenter Server
• Lab 8: Working with a virtualization workload
• Lab 9: Working with HPE Storage Integration Pack for VMware vCenter

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 35

Prelearning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We want to update HPE
OneView to the latest version, but we want to make sure that the appliance is in a healthy state and that the
update procedure will go smoothly.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

2. You are in a meeting with a customer, and they challenge you with a question: “Accidentally, one of our
administrators deleted an SSO certificate from the iLO management processor. We had to call HPE Support to
fix the problem. Is there a way to recover from such issues without calling HPE Support?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 36

3. You are in a meeting with a customer, and they challenge you with a question: “We add at least 5 HPE
Synergy frames per month to our data center. We need to update firmware for interconnect modules to the
latest version during the deployment, but the orchestrated method is time consuming. Are there any other
options that will allow us to update all frames simultaneously?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

4. You are in a meeting with a customer, and they challenge you with a statement: “We want to simplify the
update process for ESXi systems, including updates of vendor-specific components and the VMware Tools
update.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 37

5. You are in a meeting with a customer, and they challenge you with a statement: “We plan to update the HPE
Superdome Flex firmware, but we heard that using the CLI is the only way to complete this task.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

6. You are in a meeting with a customer, and they challenge you with a statement: “We need a better support
level than the standard warranty, but the HPE Pointnext Services offering is very complicated, and we cannot
decide which services we should purchase.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Working with virtualization workloads Page 38

This page intentionally left blank.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle
Module 7

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 2

Learning objectives
After completing this module, you should be able to:
• Manage the HPE Synergy lifecycle, including:
– Updating HPE OneView
– Using support and troubleshooting tools
– Updating firmware
– Migrating to HPE Composer2
• Implement the update process, using VMware vSphere Lifecycle Manager™ (vLCM)
• Manage the firmware for the HPE Superdome Flex family
• Explain the HPE Pointnext Tech Care proposition

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 3

Customer scenario

The HSP technical team needs to update HPE OneView, and they want to know how to do it. The support team
wants to learn about support and troubleshooting tools that can be used to troubleshoot a specific problem with
HPE OneView or components managed using HPE OneView. HSP plans to update firmware for all components
managed using HPE OneView, and they have asked you for more information.
HSP plans to use vSphere Lifecycle Manager to update the environment and virtual machines (VMs) in the future.
HSP wants to learn how to update HPE Superdome Flex and HPE Superdome Flex 280. They want you to explain
the HPE Pointnext Tech Care proposition.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 4

Managing the HPE Synergy lifecycle

Fully populated HPE Synergy frame

Managing the HPE Synergy lifecycle includes updating HPE OneView, using support and troubleshooting tools,
updating firmware, and migrating from HPE Composer to HPE Composer2.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 5

Updating HPE OneView

HPE OneView should be updated to the latest version to get the latest fixes and improvements.
HPE OneView update

Updating HPE OneView

The HPE OneView update procedure can be started from the GUI:
• Create an HPE OneView backup before and after the update
• When your customer installs an appliance update, the appliance restarts and goes offline. When the appliance is
offline, it does not affect the managed resources
• For a clustered Synergy Composer running HPE OneView 5.3 or later, while the standby appliance is updating,
the active appliance can still be used for general monitoring and hardware management

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 6

The HPE OneView appliance runs a combination of software and firmware. Maintaining up-to-date appliance
software and firmware fixes problems, improves performance, and adds new features to the appliance. The
appliance does not automatically notify your customer when an update is available. They must determine if an
appliance update file has been released. The HPE OneView update procedure can be started from the GUI. When
your customer installs an appliance update, the appliance restarts and goes offline. When the appliance is offline,
it does not affect the managed resources. The managed resources continue to operate while the appliance is
offline.
For a clustered Synergy Composer running HPE OneView 5.3 or later, while the standby appliance is updating,
the active appliance can still be used for general monitoring and hardware management. The management
functions are not available when the active appliance performs a failover to the standby appliance. The failover
process takes approximately 30 minutes to complete. Your customer should create an HPE OneView backup
before and after the update as a part of HPE OneView update procedure.
HPE OneView Update Readiness Checker

HPE OneView Update Readiness Checker sample report

The HPE OneView Update Readiness Checker is provided for HPE OneView users to evaluate the health of their
HPE OneView appliances for a set of known conditions before proceeding with an appliance update. At this point,
the checker evaluates conditions only on the appliance and not the managed environment.
The checker runs on a client system outside the HPE OneView appliance and is supported on Windows and Linux
platforms. The checker is supported with HPE OneView 4.2 and later versions of HPE Synergy Composer and VM
appliances. The checker is not supported with HPE Image Streamer appliances.
For secure communications between the client system and the OneView appliance, certificates for the target
OneView appliance must be trusted certificates. Only issues that require attention or remediation are noted in the
output. HPE recommends using the latest version of the utility as new tests are added regularly.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 7

Image-based updates

HPE OneView image-based updates

All updates to HPE OneView 6.0 and newer use an image-based update process, which delivers faster and more
reliable updates. With the image-based update process, a new image is installed to replace the prior image. This
process removes the risk of failures previously associated with updating all the individual packages within the
HPE OneView appliance.
HPE OneView milestone releases

HPE OneView milestone releases

To enhance the HPE OneView update experience, selected HPE OneView releases are designated as milestone
releases. In a milestone release, HPE OneView contains significant architecture enhancements. Your customer
must update to an HPE OneView milestone release before updating to subsequent versions of HPE OneView.
They can expect an HPE OneView milestone release once in every two to three releases.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 8

HPE OneView recommended update paths

Recommended update path for HPE OneView

For the latest fixes, security enhancements, and features, HPE recommends updating HPE OneView to the latest
HPE OneView version available. If your customer is unable to update to the latest HPE OneView version, HPE
recommends updating to the latest milestone release, which provides some of the latest fixes and features, but
also provides an easy update path to future HPE OneView versions. The graphic above presents the
recommended update path.
NOTE
1
Updates from HPE OneView 5.3 for HPE Synergy have the standby appliance update first.
2
HPE OneView 5.4 and 6.0 are milestone releases.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 9

Learning check
1. You are in a meeting with a customer, and they challenge you with a statement: “We want to update HPE
OneView to the latest version, but we want to make sure that the appliance is in a healthy state and that the
update procedure will go smoothly.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 10

Activity: Using the HPE OneView Update Readiness Checker

Sample output from the HPE OneView Update Readiness Checker

Participants will work by themselves on this activity. During this activity, you will use the HPE OneView Readiness
Checker. Follow the instructions:
1. From your management server open Internet Explorer (not Microsoft Edge, Firefox or Chrome) and browse to
synergy.hpe.local.
2. Click More information.
3. Click Go on to the webpage....
4. Click the Certificate error in the address bar.
5. Click View certificates
6. Click Install Certificate.
7. For store location, select Local machine.
8. For certificate store, select Trusted Root Certification Authorities.
9. Click Next followed by Finish. A dialog box is displayed to indicate success.
10. Start a command prompt and navigate to the OURC folder located in the ClassFiles folder on the desktop of
your management server.
11. Type ov-urc.exe –ovHostname synergy.hpe.local and press Enter.
12. Enter studentXX as the username, where XX should be replaced with your group number.
13. Enter P@ssw0rd as the password.
14. Wait until check is completed and review the results.
Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 11

Using support and troubleshooting tools

HPE OneView provides tools supporting troubleshooting process.
Activity log

Activity log in HPE OneView

An activity is a record of a user or system-initiated action or task or an alert message to inform the administrator
that an event has occurred that requires their attention. An alert message is an important troubleshooting tool. It
indicates when an event has occurred, and which resource reported it. Alert messages provide details about
events and suggest a solution.
If a user- or system-initiated action is complete, there is a record for it. If an action is not complete, your customer
can see which subtasks were completed or are still running and which subtasks are interrupted or stopped. The
appliance interleaves the tasks, alerts, and administrator notes into a single view. This process simplifies the
correlation of a user activity with the system health. Your customer can view all activities, filter the activities by
several criteria to view only those they want to see, or search for a specific activity. However, your customer
cannot customize filters to otherwise manage the display of the activities. They can, however, assign alerts to the
appropriate administrator for their timely resolution. When issues are investigated and resolved, your customer

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 12

can clear them, so they no longer require their attention. Your customer can annotate alert messages to keep a
historical record of issues and their resolutions, or they can note a decision that affected the alert resolution.
Activity statuses
For most HPE OneView resources, the status shown represents a single resource and not a roll-up value for
subcomponents, except for the HPE Synergy 12000 Frame. The overall health status of an HPE Synergy frame is
shown in the Master pane and reflects the most serious health status of all infrastructure components. A health
status icon for each component, such as a fan or server in an HPE Synergy frame, can be seen on the Front View
or Rear View panels on the Enclosures screen.
If a problem occurs with a particular infrastructure component, an alert is generated and displays in the
Notification panel on the Enclosures screen. For example, if the HPE Synergy Composer detects a warning
condition for a fan, the HPE Synergy Composer displays a Warning status for the fan and generates an alert.
Similarly, the HPE Synergy Composer generates a Critical status for a power supply and generates an alert. The
overall status of the HPE Synergy frame is Critical in this situation.
The table below presents available statuses for tasks and events.

Critical • A critical alert message was received, or a task failed or was interrupted
• Investigate Critical status activities immediately

Warning • An event occurred that might require your customer’s attention. A warning can
mean that something is not correct within the appliance, and it needs their
attention
• Investigate Warning status activities immediately
OK • For an alert, OK indicates normal behavior or information from a resource
• For a task, OK indicates that it has completed successfully
Unknown • The status of the alert or task is Unknown
• The status of a task that is set to run later is Unknown
Disabled A task was prevented from continuing or completing

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 13

Creating a support dump

Creating a support dump for a logical enclosure

HPE OneView can be used to create two types of support dumps:

• CI support dump—Contains HPE OneView logs with content customization
• LE support dump—Contains HPE OneView, Frame Link Module (FLM), interconnect module (ICM) logs, and
optionally, an appliance dump

CAUTION
Creating a support dump overwrites any existing backup files on the appliance. If possible, your customer
should refrain from creating a support dump, if the backup file has not been copied to an external location
for safekeeping.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 14

Support dumps

Creating a support dump in HPE OneView

HPE OneView allows your customer to:

• Create a full support dump
• Create a preview support dump (for an appliance)
• Enable or disable encryption for support dumps
• Customize support dump content
A support dump contains data that might be considered customer sensitive such as hostnames, IP addresses, and
the appliance audit log. Unless your customer specifies otherwise, all data in the support dump file is encrypted
so that only an authorized technical support person can access it. Your customer can choose not to encrypt the
support dump file if they are an Infrastructure administrator. This option can be useful if they have an onsite,
authorized technical support person or if their environment prohibits outside connections. They can also validate
the contents of the support dump file and verify that it does not contain data considered sensitive in their
environment.
Your customer should use the Advanced option to customize the selection of support dump logs while creating
the support dump. Customizing the selection of support dump logs reduces the size of the collection and, as a
result, enables faster creation and download of the collection.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 15

Some error messages recommend creating a support dump of the HPE Synergy Composer and sending it to an
authorized technical support for analysis. The support dump process performs the following functions:
• Deletes any previous support dump file
• Gathers logs and other information required for debugging
• Creates a compressed file with a name in the following format:
hostname-identifier—timestamp.sdmp Where, for support dump files created from the UI, the identifier is
either CI (indicating an appliance support dump) or LE (indicating a logical enclosure support dump)
If the If the appliance is in an error state, a special Appliance error screen displays. Anyone can create an
encrypted support dump file from that screen without the need for logging in or another form of authentication.
Creating the support dump file removes the backup file that exists on the HPE Synergy Composer. Your customer
should move the backup file to an external location before proceeding.
The support dump file contains the following:
• Operating system logs
• Product logs
• The results of certain operating system and product-related commands
Items logged in the support dump file are recorded according to Coordinated Universal Time (UTC) time.
A preview dump is a subset of a support dump, less than 25 MB, and contains the latest log data. The preview
dump downloads before the full support dump. Your customer can share the preview dump over email, reducing
the time for an initial response from an authorized technical support person. Your customer can request a
preview dump file when creating a support dump. The preview dump has the same properties as a support
dump—if the support dump is encrypted, the preview dump is also encrypted. A preview dump is not a
replacement for a support dump.
Your customer can create a logical enclosure support dump, which, by default, includes the appliance support
dump. The logical enclosure support dump file includes content from each member within each associated logical
interconnect. After the logical enclosure support dump is created, it is incorporated into the appliance support
dump, and the entire bundle of files is compressed into a zip file and encrypted for downloading.
A logical enclosure support dump file includes content from each member logical interconnect and unmanaged
interconnects, and the content of the appliance support dump. The entire bundle of files is compressed for
downloading. If instructed to create a support dump from more than one logical enclosure, your customer should
navigate to each logical enclosure screen individually and create a support dump. They must wait for each
support dump to complete before creating a subsequent support dump. By default, the logical enclosure support
dump includes the appliance support dump. Some of the interconnects may transition into maintenance mode
during the support dump operation. If an interconnect is in an error state, then a recovery is attempted.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 16

HPE OneView backup

Backup section in HPE OneView

HPE OneView provides the ability to save the configuration settings and management data to a backup file and
enables the use of that backup to restore a corrupted appliance in the event of a catastrophic failure.
An appliance backup should be performed:
• After adding hardware
• After changing the appliance configuration
• Before and after updating the appliance firmware
• After performing a factory reset of the frame
An appliance backup can be:
• Performed manually on demand
• Scheduled to be uploaded to the remote location

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 17

The backup process involves creating a backup file and then downloading that file so that your customer can
store it to a safe and secure (off-appliance) location for future use. They can schedule automatic backup
operations and designate a remote location for the backup file.
Backup files are encrypted with a simple symmetric key cryptography, and the key is unique per appliance. This
form of encryption helps prevent casual attempts at reading or tampering with the backup files. HPE strongly
recommends that your customer encrypt backup files on the backup server with an encryption key that they
generate to ensure confidentiality and the integrity of the backup file. The information about the Remote Backup
Location appears on the screen only if a remote backup is set. Similarly, the Schedule information appears on the
screen only if a schedule is set.
To prevent a backup file from being overwritten or deleted, your customer should download it, and save it to an
off-appliance location before running the next backup process. The appliance stores one backup file or one
support dump file on the appliance at a time. Creating a backup file replaces the current backup file or support
dump file. Likewise, creating a support dump file replaces the previous support dump or the backup file.
If your customer starts a backup while a support dump is in progress, the backup operation does not proceed
until the support dump operation completes. If they (as the Infrastructure administrator) start a support dump
while a backup operation is in progress, they have the option of canceling the backup and proceeding with the
support dump.
HPE OneView provides a Backup administrator user role specifically for backing up the appliance by permitting
access to other resource views without permitting actions on those resources or other tasks. Only the
Infrastructure administrator or the Backup administrator can create a backup file, either through the UI or REST
APIs.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 18

Scheduled remote appliance backup

Editing remote backup settings in HPE OneView

A remote backup from an HPE OneView appliance automatically downloads a backup to either a Secure Copy
Protocol (SCP) or Secure File Transfer Protocol (SFTP) server.
Keeping an up-to-date backup is the only way to recover the appliance in case of a catastrophic failure, such as,
disk drive failure on the appliance, whether it is the storage on a VM appliance or a physical drive on an HPE
Synergy Composer.
The administrator must specify a location where to back up the data. After they specify a location, they can
manually perform the backups. They have the option to backup data either to a remote server or to a local
computer through a browser. A remote backup uses an SCP or SFTP protocol over a Secure Shell (SSH)
connection to the remote server. Remote backup supports only credential-based authentication.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 19

The security feature of SCP and SFTP must validate that the configured remote backup server is connected to
the appliance with a host key. HPE OneView releases prior to 4.2 require your customer to retrieve the server
SSH host key and use it while configuring the remote backup. HPE OneView 4.2 and later automatically obtains
the configured remote backup server SSH host key and prompts them to confirm whether the SSH host key
fingerprint matches with the configured remote backup server.
The optional folder field allows your customer to specify a folder in the remote server home directory. If no folder
is specified, the backups are placed in the SCP or SFTP user home directory. Restrictions in using the folder are:
• Only supports a single subdirectory or folder within the home directory. There is no support for a sub folder
• Cannot specify a specific path to place backups. Your customer can only specify the configured user home
directory or a single folder within the home directory
• Cannot use any path characters when specifying the folder. For example, your customer cannot use \ or / to
precede or terminate the folder name

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 20

HPE Remote Support

Editing HPE Remote Support in HPE OneView

HPE Remote Support is available with supported devices as part of the warranty or contractual support
agreement. It provides intelligent event diagnosis and automatic, secure submission of hardware event
notifications to HPE. HPE Remote Support can be enabled from the Settings menu.
Remote Support is integrated into HPE OneView. By enabling Remote Support on the settings screen, your
customer can securely monitor the devices for hardware failures, support cases, service events, warranty and
contract information, and expiration alerts. New equipment added to HPE OneView is automatically connected
and monitored.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 21

HPE OneView Remote Support collects hardware diagnostic and system configuration information. It also stores
administrator contact information. This information is used by HPE or its affiliates to provide recommendations in
the following areas or activities:
• Troubleshooting and resolving system issues
• Optimizing the environment
• Minimizing downtime
Basic collection sends configuration information to HPE for analysis and proactive services in accordance with
your customer’s warranty and service agreements. This data is transmitted every 30 days.
Active health sends information about the server health, detailed configuration, and run-time telemetry to HPE.
This information is used to troubleshoot issues and for internal closed-loop quality analysis. This data is
transmitted every seven days.
To perform basic device monitoring, configuration, and diagnostic collections, and to maintain the health of the
Remote Support solution, on a periodic, event-driven basis, Remote Support sends certain information to HPE.
This information is used in accordance with the Software License Documents and the HPE Online Privacy
Statement.
To ensure that HPE can respond effectively to a required repair and to provide services and recommendations to
reduce downtime, Remote Support collects service delivery information, which includes device administrator
contact details such as name, phone number, and email address, and site location information such as postal
address.
To properly identify monitored devices and to synchronize the local Remote Support software with the HPE
support automation services, Remote Support sends periodic data to HPE, which includes service delivery
information as well as basic device identification information such as IP addresses, MAC addresses, hostnames,
and fully qualified domain names (FQDNs).
To automate service delivery when a failure is detected on a monitored device, Remote Support sends
information about the failure event, which includes diagnostic sense data, firmware information, model number,
serial number, failure details, as well as service delivery information and basic device identifiers as mentioned
earlier.
Configuration collections are required to deliver additional services. Information sent to HPE varies by device
type and can also include component configuration, firmware versions, OS type and version, Domain Name
System (DNS) configuration, Windows domain, and diagnostic information. Your customer should provide
permission to use this information by choosing Opt-In in the Remote Support section and to be contacted
by HPE or their HPE-authorized reseller to optimize their IT environment. HPE or its authorized resellers may use
the collected configuration data to provide your customer with recommendations to optimize their IT
environment. These providers may be located in country/regions other than their HPE IT hardware locations.
Your customer can specify their HPE-authorized resellers or support providers during setup of the Remote
Support software. Only the HPE-authorized resellers and support providers your customer associates with their
devices can receive their configuration data to individually contact them for making IT environment
recommendations or sales/delivery solutions.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 22

Some of the information collected is also used for optional display in Insight Online. This information can be
associated with your customer’s HPE Passport credentials and viewable by them in Insight Online.
Your customer should register with HPE to allow automatic case creation for hardware failures on servers and
enclosures and to enable HPE Pointnext Tech Care. After it is enabled, all eligible devices added in the future are
automatically enabled for Remote Support.
By default, Remote Support is disabled. If Remote Support is not already enabled for a selected device at the
appliance level, enable Remote Support. HPE OneView displays values based on the device serial number and
product number. Your customer can modify or refresh Remote Support device details.
Remote Support enables HPE Pointnext Tech Care services, including proactive scan reports and firmware or
software analysis reports, with recommendations that are based on previously collected configuration data.
Remote Support is secure. No business data is collected, only device-specific configuration and fault data. All
communications are outbound only and use industry standard TLS encryption ensuring confidentiality and
integrity of the information. The data is handled and managed to respect your customer’s privacy.
HPE recommends enabling all features and benefits provided by HPE OneView Remote Support so your
customer can receive fast, accurate phone home support and service per their contractual terms with HPE. HPE
OneView Remote Support registers eligible devices with authorized support services and securely collects
your customer’s HPE IT hardware service, diagnostics, configuration, and telemetry information, together with
their support contact information to provide them with Remote Support and services.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 23

Refresh procedure

Refreshing a server in HPE OneView

The Refresh action queries the resource to obtain the latest information and rediscovers all of the devices
(servers, interconnects, fans, and power supplies) in the enclosure. Refresh is typically performed automatically,
when required. Your customer can perform a manual refresh when instructed to do so when an alert appears on
the enclosure.
This operation is available for various components managed using HPE OneView. When your customer needs
updated information about the specific component-like storage system, the Refresh option should be used. The
Refresh gets the latest information from the component. This operation checks if a specific component is still
properly accessible by HPE OneView.
If your customer removes the Single Sign-On (SSO) certificate from an Integrated Lights Out (iLO) management
processor, your customer does not have to re-add the server or enclosure. They can just refresh the server, and
the certificate is applied again. Another example is a new Common Provisioning Group (CPG) configured on HPE
3PAR or Primera arrays. To import a new CPG into HPE OneView, your customer can refresh the storage system,
and the new CPG appears in HPE OneView. Later, they can decide if they want to make this CPG managed and
available for volume provisioning.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 24

Downloading the MAC table

Downloading a MAC table from a logical interconnect

To troubleshoot a network issue, your customer can view or download the MAC address table of a logical
interconnect. MAC addresses are available for the following Ethernet interconnect modules:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
MAC address information is available for the Ethernet interconnects that are powered on, operational, and
managed by the appliance. Your customer can view up to 100 MAC address entries for the logical interconnect,
or download the entire table as a compressed Comma-Separated Values (CSV) file for further analysis.
The downloaded file contains the entire database with associated uplink sets, server profiles, and networks.
Your customer can initiate one download request at a time. Any previous download is deleted before generating a
new one. The downloaded file is in a compressed CSV file format so that your customer can manipulate the data,
using software of their choice, such as Microsoft Excel.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 25

HPE OneView maintenance console

Maintenance console for HPE Composer

The appliance maintenance console is an important tool for troubleshooting appliance issues when the HPE
OneView UI is not available. Accessing the appliance maintenance console is possible:
• Through an SSH connection
• From the virtual console (appliance only)
• From an HPE Synergy FLM (Synergy only)
• Using a notebook or laptop (Synergy only)
In the upper left-hand corner of most appliance maintenance console screens, the local appliance is identified by
its location (enclosure identifier and appliance bay number) or its host name.
The appliance maintenance console displays an icon and a message about the state of the appliance, indicating
actions such as:
• Normal operation
• Appliance is offline
• Appliance is being updated
• Appliance is being rebooted to update a complex programmable logic device (CPLD) firmware
• Appliance is synchronizing with the other appliance in the cluster
• Appliance is starting up, shutting down, restarting, or temporarily unavailable
• Appliance is being restored from a backup file
• Appliance is being reset to factory default settings

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 26

Commands
The body of the main menu contains commands that can be used to:
• View the appliance details
• Restart the local appliance
• Shut down the appliance
• Update CPLD firmware
• Activate an offline appliance
• Reset the administrator password
• Perform a factory reset of the appliance
• Launch a service console, which an authorized technical support representative can use to diagnose or repair a
problem
• Create a support dump or to download an existing support dump to a USB storage device (connected to the
appliance USB port)
• Configure appliance networking
• Restore an HPE Synergy Composer from a backup file
• Log out of the Maintenance console
Your customer should be sure to log out before removing a console (monitor, keyboard, and mouse). Otherwise,
they might be leaving the appliance maintenance console ready to perform a command like Shutdown the next
time a console is attached, and the Enter key is pressed.
Update CPLD firmware from the appliance Maintenance Console
In an unusual scenario, a critical issue might require a CPLD firmware update. If an issue impacts a CPLD on the
HPE Synergy Composer2 appliance, your customer can resolve it by updating the firmware from the appliance
Maintenance Console. The update process is independent of the standard HPE OneView appliance update.
Generally, the firmware update is activated from HPE OneView. Alternatively, your customer can update only the
CPLD firmware from the appliance Maintenance Console. The CPLD firmware update process does not cause any
downtime of either the appliance or a resource operating on the appliance. Your customer must contact a support
specialist to perform this operation. The CPLD firmware update process takes approximately 10 to 15 minutes to
complete. Your customer can update only one appliance at one time, in any order. This procedure is only
applicable to HPE Synergy Composer2.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 27

Learning check
2. You are in a meeting with a customer, and they challenge you with a question: “Accidentally, one of our
administrators deleted an SSO certificate from the iLO management processor. We had to call HPE Support to
fix the problem. Is there a way to recover from such issues without calling HPE Support?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

3. Which statement about HPE OneView backup is true?

A. It is created automatically once a week.
B. It can be scheduled or created manually.
C. It can be created only using a REST API.
D. It is available only for HPE Composer.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 28

Updating HPE Synergy firmware

HPE OneView can be used to update firmware for managed components.
Firmware repository

Service Pack for Synergy uploaded to HPE OneView

A firmware bundle is a comprehensive collection of firmware and system software components that are tested
together as a single solution stack. The firmware bundle includes drivers, agents, utilities, and firmware packages.
Adding firmware bundles to the firmware repository enables your customer to deploy them across their
environment. Selecting a firmware bundle from the repository displays its release date, supported languages,
operating systems, and the file components. The Settings à Repository panel displays the amount of storage
space available for additional firmware bundles on the appliance. To add a firmware bundle to a repository, your
customer should ensure that they have enough space.
Two types of repositories are supported:
• Internal repository—The internal embedded firmware repository in an HPE Synergy Composer (1st gen) has a
maximum size limit of 12 GB to store and upload firmware files for use by components managed by HPE
OneView. An HPE Synergy Composer2 firmware repository has a maximum size limit of 62 GB to store and
upload firmware files
• External repository—One additional externally managed and user-maintained web server can be added to the
appliance as a repository. Your customer can upload the firmware bundle in a specific directory, and register
the server with HPE OneView. After they have added the web server to HPE OneView as an
external repository, they can upload the firmware bundle to the web server, and the file will be discovered
automatically

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 29

When setting up an external repository, consider the following:

– Your customer cannot edit the web server address after the external repository is added to HPE OneView
– Your customer will be prompted to acknowledge the certificate while setting up the external repository. After
they accept the certificate, it will be added to the certificate repository
– The external repository does not support passwords with characters such as { } @ # ~ /
– HPE OneView supports only anonymous and basic authentication
Firmware bundle types and file formats
“Firmware bundle” is a generic term that HPE OneView uses to refer to firmware items that can be added to an
HPE OneView firmware repository. Your customer can add multiple firmware bundles to an HPE OneView
appliance. The term “firmware baseline” is used interchangeably with firmware bundle. The types of firmware
bundles are: Service Pack, Hotfix, and Custom. Service Pack and Custom are based on ISO files.
Service Pack
A service pack is a comprehensive systems software and firmware update solution, which is delivered as a single
ISO image. The service pack for HPE Synergy is the HPE Synergy Custom Service Pack, and contains firmware
updates for components relevant to HPE Synergy. The HPE Synergy Custom Service Pack is designed to work
with specific HPE Synergy Management combinations. An HPE Synergy Custom Service Pack contains the shared
infrastructure firmware, Smart Update Manager (SUM), and firmware and OS driver smart components. An HPE
Synergy Custom Service Pack cannot be customized outside of HPE OneView. If an HPE Synergy Service Pack is
uploaded to an HPE OneView appliance, it can be used to update firmware for HPE Synergy compute nodes,
FLMs, and HPE OneView managed interconnects.
Hotfix
HPE sometimes releases hotfixes for individual components between main HPE Synergy Custom Service Pack
releases after they have been tested as part of a software release. Hotfixes must be added to specific HPE
Synergy Custom Service Pack releases. Hotfixes typically come in multiple formats for different operating
systems. When downloading a hotfix, download all the variants available, and upload them to the appliance. The
available formats are:
• .exe for Windows and the Unified Extensible Firmware Interface (UEFI) Shell
• .rpm for Linux
• .fwpkg or .zip for VMware® ESXi™
Custom
Your customer can create a custom firmware bundle in HPE OneView by adding one or more hotfixes to an
existing firmware bundle. When your customer adds hotfixes to an HPE Synergy Custom Service Pack, a new
firmware bundle of type Custom is created. If they want, they can delete the hotfixes after the custom firmware
bundle is created as hotfixes cannot be installed individually. The difference between a firmware bundle and a
firmware baseline is that a hotfix cannot be a firmware baseline because a hotfix cannot be directly assigned to a
device.
Firmware update improvements include visual progress of the server firmware update process and canceling the
firmware update task.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 30

When updating firmware, HPE OneView shows visual progress of the server firmware update process. Your
customer can use the Cancel task option in the Activity screen to stop a firmware update that is in an
unresponsive state. The Cancel task option is available for a task only in the following scenarios:
• When updating firmware with a server profile with the Firmware only option
• When a firmware update operation has already begun
• When a firmware update of server hardware initiated from the logical enclosure takes an unusually long time. A
logical enclosure firmware update has multiple child server firmware update tasks running. The Cancel
task option is available for each server firmware update task
Your customer should use the Cancel task option only as an exception when the task appears to be hung, and the
progress bar is not showing progress. The task enters the Canceled state. When your customer cancels a server
profile firmware update task, the profile task enters the Error state. Canceling a task is disruptive to system
operation, and they should only cancel a task after trying other methods to resolve the situation.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 31

Logical enclosure firmware update

Update firmware from the logical enclosure level

Your customer can update firmware from a logical enclosure for the following:
• Shared infrastructure—Shared infrastructure is that which is common to all servers in the enclosure. This
option updates selected enclosures, logical interconnects, serial attached SCSI (SAS) interconnects, drive
enclosure IO adapters, and unmanaged interconnects, if selected
• Shared infrastructure and profiles—This is the default value. This option updates selected enclosures, logical
interconnects, SAS interconnects, server hardware without profiles, server profiles, drive enclosure IO adapters,
and unmanaged interconnects
• Frame link modules only—This option updates only the FLMs

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 32

If your customer updates the logical enclosure firmware with the option Shared infrastructure and profiles or
Shared infrastructure, servers in the following states need to be powered off:
• Server hardware that does not have a server profile assigned
• Server hardware that has a profile assigned, but whose firmware baseline is set in the server profile as managed
manually or has been set to Firmware only
Interconnect firmware update activation for logical enclosures
When updating firmware for a logical enclosure, the following activation options are available:
• Orchestrated
• Impact on server updates
• Parallel
Orchestrated
The orchestrated activation option allows nondisruptive updates to interconnects in a production ready, properly
configured, and redundant environment. One HPE Virtual Connect module is always forwarding network traffic
with no or minimal impact to an application network connection. While the update process is in progress,
orchestrated firmware updates do not affect the network traffic and do not cause outages.
A validation occurs to determine if redundant paths from a server to the top-of-rack (ToR) switches are present.
If the validation is successful, an orchestrated update is performed. If not, a warning is displayed, explaining the
cause and its resolution.
Impact on server updates
Hypervisor clusters are updated non-disruptively when the orchestrated activation option is chosen. If the logical
enclosure contains one or more hypervisor profiles, each hypervisor is serially placed into maintenance mode
before updating. It can take up to 90 minutes to place a hypervisor into maintenance mode, perform the firmware
update, and take it back out of maintenance mode.
Parallel
The parallel activation option updates all the interconnect modules at the same time, resulting in disruption of the
network and storage connectivity. HPE recommends performing parallel activation during a maintenance window
when your customer can better coordinate the downtime.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 33

Logical Interconnect firmware update

Updating firmware for a logical interconnect

Firmware activation options allow your customer to maintain network availability by always keeping one path
active for production traffic, thereby reducing outages due to human errors. Your customer also has the option of
staging the firmware for later activation. Your customer can activate the staged firmware on an individual
interconnect or on all interconnects.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 34

Your customer has the following options when updating firmware based on the logical interconnect:

Firmware update options Description

Update firmware (stage + activate) Stages (uploads) the selected firmware to the secondary flash memory
on the interconnect and then activates the firmware as the baseline. At
the end of this operation, all member interconnects are running the
same firmware baseline and are compliant with one another.
Stage firmware for later activation Stages (uploads) the selected firmware to the secondary flash memory
on the interconnect, but does not activate the firmware. Your customer
can activate the firmware at a later time.
Activate firmware This activates the selected staged firmware.

During this process, all physical interconnect modules in the logical interconnect are updated. When updating
firmware based on the logical interconnect, if one or more interconnects are already running the targeted
firmware version, HPE OneView excludes those interconnects from the firmware update.
Before applying the update, your customer can check if a firmware update is disruptive, using the Preview option.
If the update is disruptive, they should follow the resolutions on the screen to enable the system to perform an
orchestrated update. The Preview option is not available for HPE Synergy pass-thru modules. This option is also
not available when your customer chooses Manual orchestration as the interconnect activation.
There are three available activation methods:
• Orchestrated
• Parallel
• Manual orchestration
In an Orchestrated update, a nondisruptive firmware update is attempted for the logical interconnect. The
following scenarios might occur:
• The firmware update is executed automatically on both interconnects without any disruption to application
network traffic
• The firmware update is executed with minimal impact to application network traffic. A context-specific warning
message is displayed along with an option to proceed or cancel the firmware update
• For example, a warning message is displayed to ensure that OS-level NIC teaming or bonding is enabled for
Ethernet networks and MultiPath Input Output (MPIO) is enabled when Fibre Channel connections are involved
• The firmware update results in a system outage. A warning message appears when network and storage
connections might be disrupted

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 35

In a Parallel update, all the interconnect modules are updated at the same time. This method is the most
disruptive and can cause network and storage connectivity outages. If one or more interconnects are already
running the targeted firmware version, HPE OneView excludes the interconnects from the firmware update.
Performing a parallel downgrade without selecting the Force installation option enables HPE OneView to perform
the operation only on the noncompliant interconnects. A maintenance window might not be required to
downgrade only the noncompliant interconnects.
In a Manual orchestration update, your customer can orchestrate the update in a stepwise approach, using the
following operations:
• Select and update one side of the interconnect topology at a time. Your customer can choose either
interconnect side to update first
• After the update for the chosen side is complete, your customer should proceed to update the other side. If the
firmware update on the interconnect module side that is updated first is not satisfactory, they should roll back
to the original firmware version
NOTE
These operations are not possible with the Parallel and Orchestrated firmware activation options.
Manual orchestration is available on the following modules:
• HPE Virtual Connect SE 40 Gb F8 Module for HPE Synergy
• HPE Virtual Connect SE 100 Gb F32 Module for HPE Synergy
• HPE Synergy 10 Gb/20 Gb/50 Gb Interconnect Link Module
The firmware update is performed on the chosen side while the other side is available to carry production traffic.
This side-by-side firmware update is allowed only at the logical interconnect level. Manual orchestration is
applicable to most updates and downgrades. There are a few exceptions where your customer cannot use the
manual orchestration option. When they try the option for any such exceptions, an error displays, and the
operation does not proceed. For example, they cannot downgrade to a firmware version that is less than the
minimum version that is supported on the interconnect module.
Manual orchestration steps include:
• Choosing which side of interconnects your customer wants to update first and beginning the update for that
side of the logical interconnect
• Verifying that the update of the first side of interconnects is successful before proceeding to update the second
side of interconnects
• If there is an issue with activation of the first side of interconnects, your customer can try again or consider
downgrading the firmware to the previous version
• Upon successfully updating the first side of interconnects, your customer should update the other side of the
logical interconnect to ensure all versions are the same within the logical interconnect
After the interconnects in the first side of the logical interconnect are updated successfully, your customer should
update the interconnects in the second side soon after. If the firmware versions of the interconnects in a logical
interconnect are different, the interconnects remain in maintenance mode, and they are not allowed to make any
configuration changes until the interconnects are at the same version.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 36

Server firmware update

Updating compute node firmware through the server profile

A server firmware update is performed using the server profile. There are three options available:
• Firmware and OS drivers, using SUT
• Firmware only, using SUT
• Firmware only

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 37

Learning check
4. You are in a meeting with a customer, and they challenge you with a question: “We add at least five HPE
Synergy frames per month to our data center. We need to update firmware for interconnect modules to the
latest version during the deployment, but the orchestrated method is time consuming. Are there any other
options that will allow us to update all frames simultaneously?”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

5. Which HPE Synergy component can be updated using the manual orchestration method?
A. Logical enclosure
B. Enclosure group
C. Logical interconnect
D. Server profile

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 38

Migrating to HPE Composer2

Transferring configuration settings and data from an HPE Synergy Composer (1st gen) to a new HPE Synergy
Composer2 is referred to as migration.
Composer compatibility and support

4-port Frame Link Module

A redundant HPE Synergy management ring requires a pair of Composers. The Composers must be the same
generation for each management ring. The HPE Synergy Composer2 is compatible with both the 2-port FLM and
the 4-port FLM. The HPE Synergy Composer (1st gen) is not compatible with the 4-port FLM within a frame. HPE
Synergy frames that contain the Composer (1st gen) require the 2-port FLM.
Options for the FLMs include the 2-port FLM and the 4-port FLM. Each HPE Synergy frame with a management
ring requires two FLMs. Frame link modules within the same frame must be the same generation. A management
ring can contain mixed FLM configurations (frames with two 2-port FLMs and frames with two 4-port FLMs).

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 39

The Composer2 is compatible with both the 2-port FLM and 4-port FLM.
The table below presents HPE Composer2 compatibility.

Frame link module HPE Synergy frame with Composer2 HPE Synergy without Composer2

2-port FLM Supported Supported

4-port FLM Supported Supported

HPE Synergy frames that include the Composer (1st gen) require 2-port FLMs.

The table below presents HPE Composer (1st gen) compatibility.

Frame link module HPE Synergy frame with Composer HPE Synergy without Composer
(1st gen) (1st gen)

2-port FLM Supported Supported

4-port FLM Not supported Supported (transceiver required)

For configurations using Composer (1st gen), the 4-port FLM is supported only in frames that do not contain a
Composer (1st gen). To connect frames with 4-port FLMs to frames with a 2-port FLM, a 10 GBase-T SFP+
transceiver is required to connect to the SFP+ ports on the 4-port FLM.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 40

HPE Synergy migration overview

HPE Composer (1st gen) and HPE Composer2

Transferring configuration settings and data from an HPE Synergy Composer (1st gen) to a new HPE Synergy
Composer2 is referred to as migration.
The migration process uses the backup and restore facility of HPE OneView along with some additional steps.
Migrating a system from HPE Synergy FLM (2-port) to HPE Synergy 4-port FLM requires replacing the FLMs as
well as changes to the LINK and MGMT port cabling. The 4-port FLM supports direct-attach copper (DAC) cables,
or your customer must use HPE 10 GBase-T SFP+ transceivers. When connecting from the MGMT port to a
switch, the transceiver or cable used must match the port speed of the switch used for management network
connectivity.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 41

The procedure consists of the following steps:

1. Plan the migration.
2. Update each HPE Synergy Composer (1st gen) to HPE OneView 5.0 or later.
3. Update the system to the HPE Synergy Custom Service Pack for ProLiant (SPP) 2019.03.20190826 or later,
or to a supported version of the HPE Synergy Service Pack.
4. If the Composer2 was not reimaged during the planning phase, verify that both the HPE Synergy Composer
(1st gen) and the Composer2 are updated to the identical version of HPE OneView.
5. Reimage each HPE Synergy Composer2 to the same version of HPE OneView that is installed on the HPE
Synergy Composer (1st gen).
Operational expectations during the migration processes are as follows:
• When migrating HPE Synergy Composers, the Composers are offline, so no performance data, activities, or
event alerts are available
• When the FLMs are removed from the frame, management network access is lost for that frame, but production
traffic should not be affected
• Compute modules and applications can continue to run during the migration processes
• Preparing the Composer2 for the migration process can add time to the migration process. Self-initialization
can take up to an hour and reimaging, if necessary, can take an additional hour. Performing these steps before
beginning the migration is recommended
NOTE
For detailed information refer to the HPE Synergy Migration Guide for Migrating HPE Synergy Composers
and HPE Synergy Frame Link Modules available at the HPE Support website.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 42

Learning check
6. Populate the support matrix for the given combinations of HPE Composers and FLMs.

Frame link module HPE Synergy frame with Composer2 HPE Synergy without Composer2

2-port FLM
4-port FLM

Frame link module HPE Synergy frame with Composer HPE Synergy without Composer
(1st gen) (1st gen)

2-port FLM
4-port FLM

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 43

Implementing the update process using vSphere Lifecycle Manager

VMware implemented a new update process, using vSphere Lifecycle Manager (vLCM) that replaces Update
Manager.

vSphere Lifecycle Manager

Image Depot in Lifecycle Manager

vLCM provides centralized and automated patch management for virtual components, including clusters, ESXi
servers, drivers and firmware, VM hardware, and VMware Tools.
vLCM introduces the concept of a desired Image, which is a precise description of the OS release, software,
drivers, and firmware. The desired Image is defined using a VMware base image, vendor add-ons, vendor
Hardware Support Pack (HSP), and additional software/driver components. vLCM support of a vendor HSP
requires installation of a vendor vLCM Hardware Support Manager (HSM) plug-in.
vLCM offers the following features:
• Upgrading and patching ESXi hosts
• Installing and updating third-party software on ESXi servers
• Standardizing ESXi images across hosts in a cluster
• Installing and updating ESXi drivers and firmware components
• Managing VMware Tools and VM hardware upgrades

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 44

HPE Infrastructure Lifecycle Manager

Updating logical enclosure firmware

The HPE Infrastructure Lifecycle Manager provides access to logical enclosures and allows firmware updates to
be performed from the vCenter Server interface. The HPE logical enclosures view contains a list of logical
enclosures that the HPE OneView appliances created, using HPE OneView for VMware vCenter. It provides
information about the HPE infrastructure components, such as HPE FLMs, logical interconnects, and other shared
infrastructure hardware components for each HPE Synergy Service Pack.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 45

Learning check
7. You are in a meeting with a customer, and they challenge you with a statement: “We want to simplify the
update process for ESXi systems, including updates of vendor-specific components and the VMware Tools
update.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 46

Managing the firmware for HPE Superdome Flex family

As HPE Superdome Flex is a mission-critical system, firmware updates are carefully managed and tested. UEFI,
Baseboard Management Controller (BMC), Recovery Manager Central (RMC), and field-programmable gate arrays
(FPGAs) are not released and managed as separate, independent firmware images, as they are on most x86
systems. Instead, there is one firmware package, with one revision for HPE Superdome Flex, called the complex
firmware. The embedded firmware management subsystem checks the firmware package against the hardware
and then applies the UEFI, BMC, and RMC updates to the entire system. The RMC checks all system components
to ensure they comply with the installed firmware package and reports any out-of-sync hardware (most likely due
to a board replacement). The firmware update procedure updates the entire set on the system to ensure
everything works together and is supported by HPE.
Online-initiated firmware updates are supported, starting with the 3.0.x version (mid-2019). UEFI firmware for
the nPartition (nPar) is updated, but it does not become active until the nPar is rebooted.
Firmware update for Superdome Flex systems
Firmware can be updated using the following methods:
• Installing the latest complex firmware, using SUM
• Installing the latest complex firmware, using HPE OneView
• Updating the firmware, using RMC CLI
HPE SUM
As HPE’s firmware management and update tool for enterprise environments, HPE SUM can remotely update all
HPE Superdome Flex Server’s firmware, as well as firmware for other HPE products. SUM offers recommendations
for firmware that needs updating, and it has an easy-to-use web UI that provides reporting capabilities and
dependency checking. SUM also installs updates in the correct order through the CLI and/or GUI.
With SUM, updating a system’s complex firmware is made easy by simply running SUM on the data center’s
management network. Your customer should provide the RMC IP address to SUM, SUM will query the system, and
then your customer can run an update using the SUM UI. HPE SUM performs IO updates, which can be completed
offline by running SUM on an nPar or initiated online by running SUM on a supported OS.
NOTE
SUM is included in all new HPE Superdome Flex firmware bundles.

HPE OneView and RMC CLI

HPE OneView can be used to update firmware for HPE Superdome Flex and HPE Superdome Flex 280. This
option includes the ability to update the system complex firmware and maintain a firmware baseline.
The RMC SSH CLI can also initiate a firmware update, and the RMC can upload the firmware using the https, sftp,
or scp protocol from a server on the management network.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 47

The table below presents tools with their recommended use cases.

HPE SUM HPE OneView firmware RMC CLI firmware updated

update

Recommended • Updating complex firmware • Updating complex firmware Updating complex firmware
use cases of one or more HPE of one or more HPE
Superdome Flex systems Superdome Flex systems on one HPE Superdome Flex
simultaneously, using the simultaneously, using the system
same firmware bundle same firmware bundle
• IO updates • Cannot be used for IO
• HPE Persistent Memory
updates
firmware updates

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 48

Learning check
8. You are in a meeting with a customer, and they challenge you with a statement: “We plan to update the HPE
Superdome Flex firmware, but we heard that using the CLI is the only way to complete this task.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 49

HPE Pointnext Tech Care proposition

HPE Pointnext Tech Care is the operational support experience for HPE hardware and HPE software products.

HPE Pointnext Services

HPE Pointnext Services

HPE Pointnext Services have begun their transformation journey, bringing together technology and expertise to
help your customer drive their business forward. In a series of evolutionary changes to how HPE support is sold
and delivered, HPE Pointnext Services delivers a truly customer-centric experience that puts each customer front
and center in a personalized, digital, and intelligent approach to driving innovation.
HPE Pointnext Services has introduced a series of new digital and data-driven capabilities that deliver faster
results in all service delivery operations. New digital collaboration tools, deep data collection and utilization, and
product-specific expertise is revolutionizing the customer experience.
In addition to the digital tools, HPE has endeavored to personalize the service experience for every customer,
allowing them to anticipate customer needs and adapt service delivery to customer individual goals and
preferences.
The most important evolution to this service mandate is to actively drive innovation by leveraging intelligence
and introducing improvements to service products during their terms. Services will no longer remain a static and
reactionary element of the customer environment. HPE Pointnext Services adds features, simplifies the portfolio,
and provides additional capabilities on a regular basis.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 50

Changed customer focus

Changed customer focus

The services industry changes fast. It has evolved from isolated elements to something more holistic. We see this
all the time in our own lives where Netflix and Uber have changed the experience dynamic for the customer. We
also see this every day in our professional lives in IT with, for example, AWS. Service interactions have an identity,
which has become known as the experience economy.
The experience is how we rate the success of our engagement with a service, be it professionally or personally. As
consumers, we know the standalone elements of a service are not a differentiator, and we also know that it is the
overall service experience that attracts and retains people as customers. The exact same thing is now driving the
mindset of our customers—they expect more from HPE. They want an experience, and that is how the HPE
services are changing—they are becoming experience based.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 51

Why make changes to the Operational Services Portfolio?

Changes to Operational Services Portfolio

The HPE portfolio was complicated and needed to move away from the traditional commoditized break/fix
approach which does not differentiate service in any way. In addition, for the last 10 years, companies have had a
slow transformation to providing a digital business, and customers are requesting this change.
HPE Proactive Care Advanced is already retired, and customers have begun to migrate to HPE Datacenter Care
at renewal—and now HPE is launching HPE Pointnext Tech Care. HPE Pointnext Tech Care is the new service
that has been optimized to be attached to new HPE technology and replaces HPE Foundation Care and HPE
Proactive Care. It differentiates by being an experience-based service. HPE Pointnext Tech Care is easier to
explain to your customers and can be differentiated against the warranty in multiple ways, thereby facilitating a
smoother sales cycle.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 52

What is HPE Pointnext Tech Care?

HPE Pointnext Tech Care definition

HPE Pointnext Tech Care is the operational support experience for HPE hardware and software products. HPE
Pointnext Tech Care helps IT teams focus on moving their business forward by proactively searching for better
ways to do things, as opposed to just focusing on reactive issues.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 53

A simpler portfolio

HPE Pointnext Tech Care portfolio

Simplification of the HPE portfolio starts with HPE Pointnext Tech Care:
• One offer—HPE Pointnext Tech Care replaces HPE Foundation Care and HPE Proactive Care. Customers do
not need to make different service comparisons, so this avoids confusion and saves time in the sales and
decision-making process
• Scalable—HPE Pointnext Tech Care features apply universally to the products they cover, and the deliverables
scale, as needed, to address the complexity of each individual product. For example, an HPE 3PAR array is run
by software, but an HPE ProLiant DL is managed with a bias towards the hardware

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 54

Three service options

The actual service levels in HPE Pointnext Tech Care have formal names which are Basic/Essential/Critical.
The table below provides specific details about each of these service levels.

Service level Coverage

Critical • 15-minute response 24x7 for severity 1 incidents (direct connect to

product specialist where available)
• Outage management for severity 1 incidents
• 24x7 6-hour hardware repair commitment (where applicable)
Essential • 15-minute response 24x7 for severity 1 incidents (direct connect to
product specialist where available)
• 24x7 4-hour on-site attendance
Basic • 2-hour response 9x5 (standard business hours)
• Next business day on-site attendance

Incident severity levels are defined as follows:

• Severity 1—Critical business impact. For example, the production environment is down; the production system
or production application is down/critically impacted; there is data corruption/loss or risk; the business is
severely affected; there are safety and security issues
• Severity 2—Limited business impact or business risk. For example, the production environment is available,
but some functions are limited or degraded; there is severely restricted use; there is a critical nonproduction
environment or system issue
• Severity 3—No business impact. For example, there is an issue with a nonproduction system (such as test
system) or there is a noncritical issue; there is a workaround in place; the customer needs assistance with
installations; the customer has questions or requests for information or guidance

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 55

Digital experience with HPE InfoSight and DCE

Digital experience with HPE InfoSight and DCE

Human nature means that we want to be in control of any experience we are involved in. Being connected with
HPE InfoSight as part of HPE Pointnext Tech Care enables this through a faster digital service that also allows
customers to use the knowledge element of the service how they want, when they want.
However, there is more than just the static information like knowledge articles, videos, and user guides. HPE
Pointnext Tech Care also provides real-time, actionable insights to the customer as part of the Digital Customer
Experience (DCE).
The DCE platform is the display element for this information, and InfoSight is the discovery engine. HPE InfoSight
finds the data to initiate auto-case creation, and make timely recommendations to customers, like notifications of
potential workload issues and disc failures, It also provides firmware and patch vulnerability viewpoints. All these
things, if leveraged, can mean higher product performance with faster issue resolution and less downtime.
To truly drive a differentiated product experience, the customer needs to be connected to HPE via HPE InfoSight.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 56

Easy access to experts

Simplified access to the experts

With the introduction of general technical guidance, HPE Pointnext Tech Care goes beyond traditional support by
offering expert technical advice regarding the operation and management of your customer’s entitled product to
get the most out of IT. Product-specific experts means talking to someone who specializes in your customer’s
product, eliminating the need for complex escalations, and an all-new artificial intelligence (AI)-powered digital
experience means faster outcomes at every stage.
General technical guidance
To drive innovation with fewer resources and augment areas where your customer has skill gaps, HPE Pointnext
Tech Care goes beyond traditional support by offering general technical guidance regarding the operation and
management of the entitled product. General technical guidance provides your customer with the freedom to
engage HPE Pointnext Services experts on customer terms leveraging best practices, known issues, and proven
strategies to find ways to do things better and drive business forward. Your customer can engage HPE Pointnext
Services for usage and process support, configuration support, and capacity management, with more topics and
workloads being added throughout the life of your customer’s service contract.
Product-specific experts
Your customer can simplify complex operations and reduce unplanned downtime risk by engaging a technical
resource who specializes in the hardware on which they need support. A customer-centric service experience
means your customer can choose how they want to access expertise, whether it be by phone, by chat, or (for
those who prefer a self-solve approach) by watching videos, reading moderated forums, and more. By scaling the
service experience to a particular product, HPE Pointnext Tech Care eliminates the need for multiple service
options or complex escalations. By automating and streamlining break/fix activities, HPE Pointnext Services can
spend more time focusing on driving business forward.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 57

An AI-powered Digital Experience

Your customer can improve performance, optimize their resources, and plan for the future by leveraging an
AI-driven operations framework that goes above and beyond break/fix. The HPE Pointnext Services experience
has been digitally transformed by introducing an all new HPE Support Center which provides customers with a
personalized experience, multiple communication options, on-demand knowledge intelligence, digital
engagement, enhanced self-solve solutions, and actionable AI insights. Your customer can simplify tasks like
contract and warranty management, case management, or finding the right downloads with personalized data at
their fingertips.
HPE InfoSight enables cloud-based machine learning, pattern recognition, log analysis, and capacity management
warnings to provide predictive support that actively detects problems and either provides the solution
automatically or opens a case to fix the problem. In addition to predicting problems, based on gathered data from
the customer environment, problems that have impacted other customers will be prevented by proactively
providing configuration or firmware solutions before they impact your customer’s business.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 58

Your customers getting the most from their HPE product

HPE Pointnext Tech Care Core features

The HPE Pointnext Tech Care features cover different stages of the product lifecycle, starting with configuration
guidance and best practices described in technical papers, through proactive and reactive support and expansion
recommendations. Note that some features require connectivity with HPE InfoSight.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 59

HPE Pointnext Tech Care—Key points

HPE Pointnext Tech Care key points

HPE Pointnext Tech Care goes beyond traditional support by enabling direct access to product-specific
specialists and providing general technical guidance to help customers not only reduce risk, but also continually
search for ways to do things more efficiently. HPE Pointnext Tech Care customers can get help through multiple
channels that include telephone, HPE moderated forums with defined response times, automated incident
logging, and a real-time chat facility. The service provides access to expert technical resources with specialized
knowledge in the hardware and or software within the context of the specific workload and avoids the customer
spending time answering sometimes unnecessary triage or entitlement questions. HPE Pointnext Tech Care goes
beyond traditional support by offering general technical guidance for the operation, management, and security of
the supported product.
HPE Support Center provides an enhanced and personalized digital experience that helps customers manage
their assets by recognizing the various products installed in the customer’s environment and how these products
interact with each other. New self-service tools allow customers to perform certain activities without having to
open a support incident, as well as providing a portal of curated knowledge resources. HPE Pointnext Tech Care
provides access to HPE resources who will help drive operational excellence and performance optimization from
edge to cloud.
The HPE Pointnext Tech Care service provides a general set of features along with hardware- and/or software-
specific features, based on the technology under support and if the product is hardware, software, or both. Some
service features are enhanced when HPE InfoSight is used to enable HPE to provide greater levels of technical
guidance, using the telemetry provided. Customers who register online through the HPE Support Center gain
access to enhanced digital capabilities, enabling increased ease of management and direct HPE engagement.
Remote and on-site response times vary, based on the service level selected, with the highest service level
providing additional assistance to customers should outages occur.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 60

Services from HPE—Portfolio positioning

HPE GreenLake includes HPE Pointnext Datacenter Care

HPE Pointnext Tech Care is the first operational service above warranty, it is a product-based service which has
fixed deliverables and scope and cannot be customized. It has been optimized to be attached to HPE technology
at the point of sale and is available through upfront and contractual services. HPE Datacenter Care and HPE
GreenLake are built on top of HPE Pointnext Tech Care, and customers buying those services will benefit from
the enhanced customer experience.
HPE Pointnext Tech Care features include:
• General features
• Hardware service features
• Software service features
• Optional features

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 61

General features
The table below presents general service features.

Feature Delivery specifications

Phone access to experts Customers may contact HPE support by telephone 24 hours a day, 7
days per week to log support incidents. Response times depend on the
service level of the covered product.
15-minute 24x7 enhanced response (Critical and Essential service
levels) For severity 1 incidents, HPE aims to either connect the customer
to a product specialist or call the customer back within 15 minutes. For all
other incidents, HPE may connect the customer to a product specialist or
call the customer back within one hour.
2-hour standard response (Basic service level)
For calls on products covered by a basic service agreement, HPE shall
provide a two-hour phone response from a product specialist during the
coverage window.

Expert online chat Customers can initiate an online chat with a specialist technical resource
to ask questions, get help, or general technical guidance. Expert online
chat is provided so customers can obtain quick answers to technical
questions about their HPE product. Complex questions that require
detailed responses may be elevated to support incidents on an as-needed
basis. Expert online chat is limited to English language only and available
during the service coverage window. Availability may vary for certain
products.

Expert forum response Customers can post questions, issues, or discuss usage of products within
the HPE community forums. HPE product specialists respond within two
business days to any unsolved questions raised within the official HPE
community forum for products covered by HPE Support services. Where
posts raise topics that should be addressed through standard support
processes, HPE requests that a formal support incident is created and
follows the standard HPE incident management processes. The specialist
technical resource response is limited to English language only and
requires that the user be registered with HPE Support Center and has
linked service agreements.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 62

General technical guidance HPE endeavors to provide general technical guidance for customer
questions and enquiries specific to the topic areas, regarding the
operation and management of the customer’s products covered by HPE
Pointnext Tech Care. General technical guidance is available through the
telephone, web, and chat communication channels and is subject to the
service coverage window of the service agreement and will be treated as
a severity 3 incident. When related to the topics detailed/described in the
following, HPE identifies knowledge documents, videos, and knowledge
base articles to assist with topics raised. In addition to any limitations or
exclusions set forth in this data sheet, any HPE general technical
guidance shall be provided specifically for the topics detailed in the
following and only for the products covered under the service:
• Correct usage or procedures to use the products’ features
• Assistance with identifying relevant documentation or knowledge base
articles
• HPE best practice advice to help your customer manage and maintain
their products
• Basic navigation to use the product management interface
• Advice on capacity management options, based on product usage
trends (where available)
• Guidance with the general configuration of the product that may
include recommendations for best practice, based on HPE operational
experience
• Guidance on the potential steps to help bring the product into a
supported configuration
General technical guidance topics mentioned previously may not be
applicable to all hardware and/or software products covered by this
service.

HPE InfoSight assistance For HPE products that are supported by HPE InfoSight, HPE provides
support and advice for the setup, configuration, and usage of HPE
InfoSight. In addition to products connected to HPE InfoSight, HPE
extends general technical guidance to include HPE InfoSight analytics
and the alerts and recommendations provided. For configured HPE
products, on request, HPE assists customers to understand the issues,
alerts, and information provided by HPE InfoSight. Where analytics
provide recommendations included in HPE InfoSight workload insights,
HPE can provide qualification of the analysis, the recommendation, and
the general next best actions in line with general technical guidance.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 63

HPE InfoSight predictive alerts For HPE products covered by a service agreement, connected to and as
supported by HPE InfoSight, customers gain access to enhanced
automated monitoring routines that can identify potential issues using
HPE unique signatures, rules, and determinations. For issues identified by
HPE InfoSight, the HPE InfoSight alerts customers to the problem and
identifies opportunities for corrective action, and subject to criticality may
automatically submit incidents to HPE containing diagnostic information
to speed diagnosis and repair. Capabilities may vary by product, devices
need to be supported by HPE InfoSight, and connectivity to HPE
InfoSight is required. Where customers configure HPE InfoSight for
supported HPE products that are covered by HPE Pointnext Tech Care,
customers gain access to enhanced HPE InfoSight analytical capabilities
that provide detailed product insights, issue alerts, and usage and
configuration opportunities.

Automated incident logging For supported HPE products using HPE proprietary service tools
(including HPE InfoSight), and where connected, devices may
automatically submit incidents to HPE containing diagnostic information
to speed diagnosis and repair. Where automated monitoring and incident
submission identifies critical issues requiring HPE engagement, HPE
attempts to engage the previously identified customer contact within the
service coverage window as defined by the service level purchased.
Should the customer contact not be available, or at the customer’s
request, HPE schedules follow up for the next business day. All
noncritical issues will be followed up the next business day. Customers
may at any stage, subject to their service level, engage with HPE to
request continuity of problem diagnosis and resolution.

Tech tips videos HPE provides access to an enhanced tech tips videos by experts offering
technical best practices and functional know-how. The tech tips videos
help customers understand how to best manage and operate their HPE
product and provide information regarding emerging support trends and
capabilities. Tech tips videos are available via HPE Support Center.
Subject of content vary, based on HPE operational experience with
products and best practices in supporting and maintaining these
products.

Outage management (Critical During a severity 1 HPE service incident, should a business impacting
service level) outage be identified by the customer, HPE invokes an enhanced outage
management process, dependent on the issue severity and complexity, to
minimize the business impact and accelerate resolution. After a business
outage or critical workflow interruption has been confirmed by HPE,
technology-specific specialist resources shall be engaged to drive
incident resolution. Throughout the duration of the outage incident, the
specialist resources drive technical resolution and proactively keep
nominated customer stakeholders informed of the status. Where

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 64

identified by HPE, technical insights and opportunities shall be shared to

help reduce future incident likelihood. Outage management is included
for HPE products covered by the critical service level option and is in
addition to standard HPE escalation processes.
Hardware service features
The table below presents hardware service features.

Feature Delivery specifications

Remote problem diagnosis and After the customer has placed a call, and it has been acknowledged by
support HPE (as per general provisions), HPE works during the coverage window
to isolate the hardware incident and to remotely troubleshoot, remedy,
and resolve the incident with the customer. Prior to any on-site
assistance, HPE may initiate and perform remote diagnostics using
electronic remote support solutions to access covered products, or HPE
may use other means available to facilitate the remote incident
resolution. When customers choose to swap defective parts with HPE-
provided replacements customer self-repair (CSR), HPE provides remote
assistance during the service coverage window for installation of
customer-installable parts or firmware classified by HPE as CSR parts.

On-site hardware support For hardware incidents that cannot, in HPE’s judgment, be resolved
remotely, an HPE authorized representative provides on-site technical
support on covered hardware products to return them to operating
condition. After an HPE authorized representative arrives at the site, the
representative continues to deliver the service, either on-site or remotely,
at the discretion of HPE, until the products are repaired. Work may be
temporarily suspended if parts or additional resources are required, but
work will resume when they become available. Repair is considered
complete upon HPE verification that the hardware malfunction has been
corrected or that the hardware has been replaced. In addition, at the time
of on-site technical support delivery, HPE may:
• Install available engineering improvements for covered hardware
products to help ensure proper operation of the hardware products and
maintain compatibility with HPE-supplied hardware replacement parts
• Install available firmware updates defined by HPE as noncustomer
installable for covered hardware products that, in the opinion of HPE,
are required to return the covered product to operating condition or to
maintain supportability by HPE. On request, HPE can install (during
coverage hours) critical HPE firmware updates defined by HPE as
noncustomer installable for covered hardware products. Critical
firmware updates are firmware updates recommended by the HPE
product division for immediate installation
Replacement parts and materials HPE provides HPE supported replacement parts and materials necessary
to maintain the covered hardware product in operating condition,

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 65

including parts and materials for available engineering improvements

required by HPE to assure supportability of the product.

HPE Visual Remote Guidance Customers may choose to connect with specialist technical resources
(VRG) using HPE VRG during the service coverage window. HPE VRG is a
secure, enterprise collaboration application that enables live stream
video, voice, and content sharing through any Android or iOS smart
device. The problem diagnosis and resolution may be performed in real
time, with in-the-moment guidance and collaboration between the
customer and HPE subject matter experts. HPE VRG may also be used to
assist in the installation of HPE-designated CSR parts.

HPE InfoSight dashboards For HPE products covered by a service agreement and connected to HPE
InfoSight, as supported by HPE InfoSight, customers gain access to
additional analytic dashboards that identify device health and/or identify
recommended or required firmware updates and may include
recommended or required driver or software updates (platform
dependent).

HPE InfoSight workload insights Where supported by HPE InfoSight, and where HPE products are covered
by a service agreement and connected to HPE InfoSight, additional
analytics may be provided that help customers understand usage, and
identify opportunities to improve product usage and/or configuration for
select third-party independent software vendor (ISV) software.

Firmware updates for selected Customers are provided access to download, install, and use firmware
products updates for hardware products covered by this service, subject to all
applicable license restrictions in HPE current standard sales terms. For
customers with licenses to firmware-based software products (features
implemented in firmware, activated by the purchase of a separate
software license product), they must also have, if available, an active HPE
service agreement on the firmware-based software products to receive,
download, install, and use related firmware updates.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 66

Collaborative Support and Collaborative Support and Collaborative Assistance provide electronic or
Collaborative Assistance telephone support (during the service coverage window) for select ISV
software that works with hardware covered by HPE Pointnext Tech Care.
Collaborative Support and Collaborative Assistance apply to selected ISV
software when that software is not under HPE support. When ISV
software is covered by HPE Pointnext Tech Care, support is provided as
described in the “Software services features” section of this document.
Collaborative Support and Collaborative Assistance are separate features;
however, Collaborative Assistance applies to all ISV products that are
eligible for Collaborative Support.
Collaborative Support
Collaborative Support is provided for selected ISV software products,
where HPE investigates and attempts to resolve problems by asking the
customer to apply fixes that have been made available or known to HPE.
In some cases, support may be limited to communication of a known fix
available through the installation of a software update or patch, and the
customer will be directed to available sources for the applicable updates
or patches. This is because access to the known fix requires additional
service contracts with the respective software vendor.
Collaborative Assistance
If HPE determines that the HPE product is not the source of the problem,
but HPE deems the problem may be related to the selected ISV software,
HPE shall, at the customer request, initiate Collaborative Assistance.
Collaborative Assistance can be provided only in cases where the
Customer has appropriate active support agreements in place with
selected ISVs, and the customer has taken the steps necessary to ensure
that HPE can engage with the ISV on behalf of the customer. HPE
engages the ISV and provides information about the customer’s issue.
After the incident has transitioned to the ISV, it is then the responsibility
of the ISV to resolve the customer’s issue, which will be subject to the
support levels of the agreement between the customer and that ISV.
After the ISV is engaged, HPE closes the HPE incident, but the customer
or ISV can resume the support issue with HPE, if needed, by referencing
the original incident identification number.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 67

Periodic maintenance For more information on eligible products that receive periodic
maintenance services as part of this service, your customer should
contact their HPE sales representative. If periodic maintenance is
included, an HPE authorized representative will contact your customer to
arrange for the periodic maintenance to be performed at a mutually
agreed-upon time, during local HPE standard business hours, excluding
HPE holidays, and within the required scheduled interval as defined in
the product maintenance schedule, unless otherwise agreed upon by HPE
in writing. HPE plans the necessary periodic maintenance activities and
communicates any identified prerequisites to your customer when
contacting them to schedule the service. Your customer must provide
access to the product, ensure that the prerequisites have been met, and
supply any consumables such as filters and chemicals required at the
time of product maintenance.

6-hour hardware call-to-repair 6-hour hardware call-to-repair is included for HPE products covered by
(Critical service level) the critical service level option and is available on select HPE hardware
products.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 68

Software service features

The table below presents software service features.

Feature Delivery specifications

License-to-use software updates Customers receive the license-to-use software updates to HPE or HPE-
supported third-party software for each system, socket, processor,
processor core, and end-user software license covered by this service, as
allowed by the original HPE or original manufacturer software license
terms, provided they have rightfully acquired the original software
license. Distribution of certain third-party software updates, license
agreements, and license keys may be made directly from the third-party
vendor to customers, as applicable.

Installation advisory support Limited advisory support is provided and is restricted to basic advisory
assistance if your customer encounters difficulties while performing a
software product installation or following advice on proper installation
methods and updating of stand-alone applications. The scope of such
advisory support is at HPE’s discretion. Exclusions to this advisory
support include, but are not limited to any downloading of complete
software packages or walking through an installation from start to finish.
These services are available for an additional charge and can be
purchased separately from HPE.

Software support For software products covered by the service agreement, HPE provides
corrective support to resolve identifiable and customer-reproducible
software product problems, and supports to help them identify problems
that are difficult to reproduce. This support also assists in
troubleshooting problems and determining configuration parameters for
supported configurations.

Software features and operational HPE provides information, as commercially available, on current HPE
support product features, known problems and available solutions, and
operational advice and assistance.

Software product and As HPE releases updates to HPE software, the latest revisions of the
documentation updates software and reference manuals are made available to your customer. For
selected third-party software, HPE provides software updates, as such
updates are made available from the third-party, or HPE may provide
instructions on how your customer can obtain any software updates
directly from the third-party. A license key or access code, or instructions
for obtaining a license key or access code, will also be provided to your
customer when required to download, install, or run the latest software
revision.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 69

Optional features
The table below presents optional features.

Feature Delivery specifications

Hardware data security options Defective media retention (DMR)

(on-site support) In the event of a hardware failure, for eligible products, the DMR service
feature option allows your customer to retain replaced defective hard
disk or eligible SSD/flash drive components that they do not want to
relinquish due to sensitive data contained within the disk (disk or
SSD/flash drive) covered under this service. All disk or eligible SSD/flash
drives on a covered system must participate in the DMR.
Comprehensive defective material retention (CDMR)
In addition to DMR, in the event of a hardware failure, the CDMR service
feature option allows your customer to retain additional replaced
components that have been designated by HPE as having data retentive
capabilities, such as memory modules. All eligible data retentive
components on a covered system must participate in the CDMR.

Preventive maintenance An HPE-authorized representative visits the site at regularly scheduled

intervals. Customers shall call HPE to request and schedule a preventive
maintenance visit at the agreed-upon intervals. Availability and
deliverables may vary by region. Preventive maintenance services are
delivered between 8:00 a.m. and 5:00 p.m. local time, standard business
days, excluding HPE holidays, regardless of the selected coverage
window.

Hardware Exchange Service For products supporting customer self-repair and/or self-replace for all
componentry, at HPE’s discretion, an alternative to hardware on-site
support may be made available. The Hardware Exchange Service is
available for HPE Pointnext Tech Care on Basic Exchange and Essential
Exchange service levels only. It covers products that can easily be
shipped and on which customers can restore data from backup files. The
service is not available on all products or locations.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 70

HPE Datacenter Care Service

HPE Datacenter Care Service is HPE’s most comprehensive support solution tailored to meet your customer’s
specific data center support requirements. It offers a wide choice of proactive and reactive service levels to cover
requirements, ranging from the most basic to the most business-critical environments. HPE Datacenter Care
Service is designed to scale to any size and type of data center environment while providing a single point of
contact for all your customer’s support needs for HPE as well as selected multivendor products. The service is
delivered under the governance of an assigned HPE support team that is familiar with your customer’s IT
environment and understands how it enables your customer’s business. A mutually agreed upon and executed
statement of work (SOW) details the precise combination of reactive and proactive support features that are
provided under HPE Datacenter Care Service, based upon your customer’s requirements.
Your customer can use HPE Datacenter Care Service to complement their organization’s own skills and
capabilities by mixing and matching any of HPE’s support offerings with different elements of their IT solution or
data center, based on the role and importance of the particular products. IT environments are becoming
increasingly diverse, combining low-cost, virtualized, and bladed technology deployed alongside more traditional
high-end products—each of which can have very different reactive support needs. HPE Datacenter Care Service
is designed to meet a wide range of support requirements.
NOTE
An IT environment, as defined by HPE, is the IT infrastructure supported by HPE Datacenter Care Service,
under the direct day-to-day management of one IT organization, in one country, and as detailed in the
SOW.
When the unexpected happens, your customer may still need rapid escalation and incident resolution. In the
event of a service incident, HPE Datacenter Care Service provides access to HPE technical solution specialists
who can help your customer resolve critical issues as quickly as possible. HPE employs accelerated escalation
procedures to resolve complex incidents. In addition, your customer’s support team of HPE specialists is equipped
with remote technologies and tools designed to reduce downtime and increase productivity.
A set of optional proactive services, ranging from technology-specific activities such as firmware and OS patch
analysis/recommendations and change management support, to a systematic approach to continual
improvement, based on IT service management (ITSM) and HPE best practices, including the IT Infrastructure
Library (ITIL) and ISO/IEC 20000, have been designed to augment the skills of your customer’s IT staff and
complement reactive support options. These proactive services are designed to provide flexible choices and are
customized to support different components of a solution or different areas within your customer’s data center.
HPE Datacenter Care Service is designed to augment your customer’s capabilities; help them reduce risks across
people, processes, and technology; increase IT service quality and productivity; and reduce costs.
The core service includes an assigned account team led by a trained HPE Account Support Manager (ASM). The
team’s goal is to form a close working relationship with designated members of your customer’s IT staff and gain
a clear understanding of their business objectives, key service-level agreements (SLAs), and the key performance
indicators (KPIs) your customer needs to meet. Delivery of the various support options your customer has chosen
is overseen by the ASM and directed at meeting your customer’s goals.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 71

The flexibility and customization available with HPE Datacenter Care Service helps provide your customer with a
cost-effective support solution tailored to their unique needs.
In addition to these core services, HPE Datacenter Care offers a number of advantage options or solution blocks
that are designed to help your customer address various IT challenges to help them achieve their desired
business outcome.
The available advantage options currently available are:
• HPE Datacenter Care for SAP HANA®
• HPE Datacenter Care for HPE Nimble Storage
• HPE Datacenter Care for NonStop
• HPE Datacenter Care for Microsoft Azure
• HPE Datacenter Care for Hyperscale
• HPE Datacenter Care for Networking/Edge (aka Campus Care)
• HPE Datacenter Care for NFV
• HPE Datacenter Care for Multivendor
• HPE Datacenter Care Global Call Management
• HPE Adaptive Management Services
HPE GreenLake
HPE GreenLake is an infrastructure utility consumption service, based on the converged infrastructure of HPE
server, storage, and networking equipment installed at your customer’s site. The service is billed based on
monthly usage and allows your customer to procure and pay for their capacity needs on a variable basis, subject
to minimum usage requirements.
HPE GreenLake Solutions
HPE GreenLake Solutions provide complete end-to-end, workload-specific solutions that include, hardware,
software, and expert services delivered on-premises in a pay-per-use model, subject to minimum usage
requirements. The goal of this complete solution approach is faster time to value for HPE customers and reduced
complexity. Each solution includes certain advisory and professional services to further assist your customer with
solution design and integration into their environment.
The current portfolio of HPE GreenLake Solutions includes:
• Big Data
• Backup
• Database with EDB Postgres
• SAP HANA
• Hybrid cloud

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 72

What it means for your customers

HPE Pointnext Tech Care customer benefits

The HPE streamlined portfolio makes the conversation simpler and faster. This benefits everyone including HPE,
partners, and customers. HPE Pointnext Tech Care is experience based, and it provides easier access to experts
via chat or phone and empowers customers with value-based service elements like the non-break/fix general
technical guidance and tech tips videos as part of the DCE. The DCE gives customers real-time actionable insights
as to things they can do themselves, and they can also ask for help in general technical guidance.
By being connected to HPE via HPE InfoSight HPE can make things happen faster, from auto-case creation to
dashboard prompts, where a customer needs to take action with which they can check via an expert chat. Over
the lifecycle of the product and by leveraging DCE-displayed information, HPE Pointnext Tech Care identifies
opportunities for HPE and its partners to talk to customers.

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 73

Activity: Meeting with the customer

Participants will work as a group on this activity. After discussing support and update procedures, HSP asked you
to verify if they understand everything correctly.
Answer the following questions:
1. True or false: HPE OneView supports image-based updates. ________________________

2. True or false: Your customer can update HPE OneView directly from version 5.4 to version 6.1.
________________________

3. Which tool can be used to evaluate the health of the HPE OneView appliance?
__________________________________________________________________________________________________________

4. True or false: HPE Synergy Composer (1st gen) cannot be migrated to HPE Synergy Composer2.
________________________

5. When should an HPE OneView backup be created?

__________________________________________________________________________________________________________

6. For which HPE OneView objects can an administrator create a support dump?
__________________________________________________________________________________________________________

7. Which FLM must be installed in the HPE Synergy frame that is housing an HPE Composer (1st gen)?
__________________________________________________________________________________________________________

8. True or false: vSphere Lifecycle Manager can be used to install and update third-party software on ESXi
servers. ________________________

9. True or false: vSphere Lifecycle Manager requires an additional license. ________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 74

10. Which firmware update method should be used to update the HPE Persistent Memory firmware for HPE
Superdome Flex?
__________________________________________________________________________________________________________

Learning check
9. You are in a meeting with a customer, and they challenge you with a statement: “We need a better support
level than the standard warranty, but the HPE Pointnext Services offering is very complicated, and we cannot
decide which services we should purchase.”

How should you respond?

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

10. Write a summary of the key concepts presented in this module.

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 75

__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________

Rev. 21.41
Confidential - For Training Purposes Only
Managing the solution lifecycle Page 76

Summary
• Managing the HPE Synergy lifecycle includes:
– Updating HPE OneView
– Using support and troubleshooting tools
– Updating firmware and migrating to HPE Composer2
• VMware vSphere Lifecycle Manager is a replacement for Update Manager and offers comprehensive update
options for a virtual environment
• HPE Superdome Flex and HPE Superdome Flex 280 support three different methods for firmware updates:
– RMC CLI
– HPE OneView
– HPE Smart Update Manager
• HPE Pointnext Tech Care is the first operational service above warranty. It is a product-based service that has
fixed deliverables and scope, and it cannot be customized. It has been optimized to be attached to HPE
technology at the point of sale and is available through upfront and contractual services

Lab exercises
Open your lab guide, and complete:
• Lab 10: Working with VMware vSphere Lifecycle Manager
• Lab 11: Working with the PowerShell Library for HPE OneView

Rev. 21.41
Confidential - For Training Purposes Only