This document describes how to install and configure the HPE Hyper Converged 380 appliance and expansion nodes. This document is for
products with
Part Number: 860192-003
September 2016
Edition: 3
Installation Guide
the person who installs, administers, and troubleshoots servers and is skilled in network configuration and virtual environments. Hewlett
Packard Enterprise assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in
hazardous energy levels.
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not
responsible for information outside the Hewlett Packard Enterprise website.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are
licensed to the U.S. Government under vendor’s standard commercial license.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
VMware®, vCenter™, and vSphere™ are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
NVIDIA, the NVIDIA logo, and NVIDIA Tesla are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.
Purpose of this guide ..................................................................................................................................... 7
Before you begin ....................................................................................................................................... 8
Before installing ........................................................................................................................................................ 8
Default user names and passwords ....................................................................................................................... 17
Front panel ............................................................................................................................................................. 20
Space and airflow requirements .................................................................................................................. 23
Temperature requirements .......................................................................................................................... 24
Power requirements .................................................................................................................................... 24
Connecting a DC power cable to a DC power source ................................................................................. 24
Installing the node into the rack .............................................................................................................................. 26
Cabling the system ................................................................................................................................................. 27
General virtualization configuration (all 1 GbE appliance)........................................................................... 28
General virtualization (10GbE appliance) and VDI configurations .............................................................. 29
Configuring the system ........................................................................................................................... 32
Configuring the HC380 system .............................................................................................................................. 32
Configuring the network switches ........................................................................................................................... 32
Powering on all nodes ............................................................................................................................................ 33
Configuring a laptop or workstation to access the system ..................................................................................... 33
Completing the initial HC380 Management UI configuration .................................................................. 46
Configuring the settings .......................................................................................................................................... 46
Performing the initial HC380 Management UI setup .............................................................................................. 46
Configuring LDAP or Active Directory .................................................................................................................... 47
User roles .................................................................................................................................................... 47
Certificate error when launching vCenter web client ................................................................................... 73
HC380 nodes are not discovered ................................................................................................................ 73
OneView InstantOn hangs during deployment ............................................................................................ 73
vCenter license status on Health screen is red ........................................................................................... 74
OneView InstantOn progress indicator appears to hang ............................................................................. 74
"Invalid username and password" error appears when you specify a local vCenter ................................... 74
Application performance on management VM might decrease ................................................................... 74
"The page cannot be displayed" error message appears ............................................................................ 75
OneView InstantOn hangs with error message "0:02 Adding SAN to vCenter" .......................................... 75
vSphere HA errors .................................................................................................................................................. 75
Connection error to vCenter server ............................................................................................................. 76
Installation utility cannot assign the DCM network VLAN to the ESXmgmt portgroup ................................ 76
Unable to migrate host to management cluster ........................................................................................... 77
Trouble setting up storage ........................................................................................................................... 77
Distributed switches were not created as expected .................................................................................... 78
Foundation or Enterprise zip files on the datastore supplied by the factory image are not found ............... 78
Foundation or Enterprise zip files can not be unzipped .............................................................................. 79
Storage is not available for OVA images ..................................................................................................... 79
Contents 4
Issues creating first management appliance ............................................................................................... 79
CloudSystem was not deployed successfully .............................................................................................. 80
Could not update the hpcs-data* distributed switch .................................................................................... 80
Could not register vCenter with CloudSystem ............................................................................................. 80
Could not activate compute nodes .............................................................................................................. 81
Could not create Tenant VLAN Segment Ranges ....................................................................................... 81
Could not create Tenant and Provider VLAN Networks .............................................................................. 82
Could not add Subnets to Networks ............................................................................................................ 82
Could not create router ................................................................................................................................ 82
Could not update to 9.02 ............................................................................................................................. 82
Could not update passwords ....................................................................................................................... 83
VSA volumes did not stabilize in 10 minutes…cannot continue .................................................................. 83
VM <name> did not power off - <error msg>............................................................................................... 83
Problem finding original vCenter cluster ...................................................................................................... 83
Could not find the VSA VM on host <name> ............................................................................................... 84
Configuring the switches ............................................................................................................................. 86
Connecting to the serial console port .......................................................................................................... 86
Configuring the switches ............................................................................................................................. 92
Validating the switch configuration .............................................................................................................. 96
Uplink into existing network infrastructure ................................................................................................. 100
Appendix G: Management group quorum consideration ...................................................................... 109
Appendix H: IP addresses for sample cluster ....................................................................................... 110
ESXi management network IP addresses worksheet .......................................................................................... 110
vSphere vMotion network IP addresses worksheet ............................................................................................. 112
Storage network IP addresses worksheet ............................................................................................................ 113
CloudSystem network IP addresses worksheet ................................................................................................... 114
Warranty and regulatory information ..................................................................................................... 116
Warranty information ............................................................................................................................................ 116
Regulatory information ......................................................................................................................................... 116
Safety and regulatory compliance ............................................................................................................. 116
Belarus Kazakhstan Russia marking ......................................................................................................... 116
Turkey RoHS material content declaration ................................................................................................ 117
Ukraine RoHS material content declaration .............................................................................................. 117
Support and other resources ................................................................................................................ 119
Accessing Hewlett Packard Enterprise Support ................................................................................................... 119
Information to collect ................................................................................................................................. 119
Remote support .................................................................................................................................................... 120
Insight Remote Support installation ........................................................................................................... 120
Acronyms and abbreviations................................................................................................................. 121
Index ..................................................................................................................................................... 124
Contents 6
Introduction
Product introduction
The Hyper Converged 380 system is a virtualization appliance that combines compute and storage
resources in the same chassis. It is designed to be deployed easily and yet manage a variety of virtualized
workloads in medium-sized businesses and enterprises.
The system is available in three workload configurations:
• General virtualization — supports general-purpose virtualization workloads
• HPE Helion CloudSystem — open and fully integrated cloud solution delivering automation,
orchestration, and control across multiple clouds
•Virtual Desktop Infrastructure (VDI) — supports specific VDI workloads
Purpose of this guide
All hardware comes preintegrated and ready to connect to a network switch. All software, with the
exception of the VDI-specific application, comes preloaded enabling a simple installation. This guide
contains information for installing and configuring the appliance and adding expansion nodes.
Use the instructions and guidelines in this guide to perform the following tasks.
•Initial installation and deployment tasks
o Plan for the installation by using the preinstallation worksheets to collect the information required
o Install the hardware into your datacenter environment
o Connect the appliance to your network and connect to the system
o Deploy the system using the HPE OneView InstantOn configuration utility
o Install HC380 Management UI
o Complete the initial configuration of HC380 Management UI
o Install Cloud System (optional)
• Adding HC380 expansion nodes
o Expand the system
NOTE: For information about installing the VDI configuation, see HPE Reference
Architecture for VMware Horizon (with View) 6.2.2 on HPE Hyper Converged 380 on the
The HC380 ships with a supported set of software versions that comply with the HC380 firmware and
software compatibility matrix. Over time, the HC380 matrix may be updated to support newer versions.
Customers maintain the HC380 to be in compliance with the HC380 compatibility matrix. For more
information, see the HPE Hyper Converged 380 Firmware and Software Compatibility Matrix on the
Hewlett Packard Enterprise website (http://www.hpe.com/support/hc380CMen).
Introduction 7
Before you begin
Before installing
The HC380 installation process is designed for an IT specialist who is familiar with computer hardware
and software concepts and virtual machine networking. You are encouraged to read through this
document before you begin installation and familiarize yourself with each of the steps.
You need the following items to successfully complete the installation:
•Network switches and cables that meet the following requirements:
o 1Gb connections for each the iLO and 1Gb LOM ports on each node
o 1Gb or 10Gb connections the FlexLOM ports on each node
o 1Gb and 10Gb connections IPv6 capable and enabled
•Appropriate power and rack space for the HC380 nodes and any other hardware that may be part of
the environment
•Laptop or other computer that can be network cabled directly to a node to begin configuration. The
instructions assume that you are using a Windows-based computer with Remote Desktop Services
installed.
•VMware vSphere Enterprise or Enterprise Plus license
Networking requirements
Planning and executing the network installation is the single most important item to a successful
installation. Whether you are integrating into an existing data center infrastructure or isolating the
appliance from other resources, you must consider not only the initial appliance installation, but also plan
for any future expansion.
IMPORTANT: The networking choices made during the initial installation may not be
reversible at a later time without a complete reinstallation.
Flat or VLAN-tagged networks
The HC380 appliance creates and utilizes different internal networks to segregate traffic, including ESXi
management, vMotion, and storage. These networks may be configured in either a "flat" or VLAN-tagged
network topology, depending on the workload configuration and your specific network requirements. Here
are the options based on workload type:
• General virtualization: Flat or VLAN-tagged network
• CloudSystem: VLAN-tagged network only
• VDI: Flat or VLAN-tagged network
If you have a choice and are unsure about which network type to use, consult your network administrator.
IPv6 enablement at switch level
The HC380 requires that the 1Gb and 10Gb switches be IPv6 enabled.
Most switches have IPv6 enabled by default, but some companies may explicitly disable IPv6 Link Local
by setting up access control lists (ACLs) or performing other IT functions.
Before you begin 8
If IPv6 is not enabled, the HC380 nodes will not be discovered during the installation progress and the
Addresses
HC380
172.28.0.1
1
This value is provided during the
HC380 OneView
172.28.0.2
1
This value is provided during the
installation and deployment will not complete.
IP address assignments
Note the following points about the IP address assignments:
•The appliance uses a private IPv4 network (192.168.42.0/24) for internal system communications
that can not be used by other devices sharing the same network.
•If you plan to expand the number of nodes in the future, Hewlett Packard Enterprise recommends
that you preallocate and leave enough room in the IP address ranges. Preallocating allows you to
add future nodes with IP addresses matching the initial installation subnet ranges. If you choose not
to preallocate the IP addresses now, the future nodes require IP addresses within the subnet ranges
used during initial system deployment.
•You need between 5 and 119 IPv4 addresses, depending upon whether you are performing an initial
configuration or expanding the HC380 cluster.
oIf you are performing an initial configuration, the system requires between 15 and 119 IPv4
addresses, depending on the number of nodes in your initial configuration and whether you are
installing CloudSystem.
oIf you are expanding an existing HC380 cluster, you need between 5 and 70 IPv4 addresses,
depending on the number of nodes you are adding and whether you are using CloudSystem.
•Since the OneView InstantOn configuration utility accepts a starting IP address and automatically
increments the IP addresses by the number of nodes in the initial configuration or expansion, some
of the IP addresses must be contiguous.
•For examples and worksheets to help you plan your networks, see "Appendix H: IP addresses for
sample cluster (on page 110)."
Planning your appliance networks
Use the topics in this section to plan your appliance networks and determine the IP addresses that are
required for your installation.
ESXi management network IP addresses
The ESXi management network assigned in OneView InstantOn requires contiguous IP addresses. When
assigning IP addresses for the ESXi management network, the Management VM IP address is assigned
first and is the starting IP address. Record the starting IP address on the preinstallation worksheet
("Preinstallation worksheets" on page 14).
You must choose separately the HC380 Management UI and HC380 OneView VM IP addresses on the
ESXi management network so that they do not conflict with the IP addresses assigned by OneView
InstantOn.
When planning the ESXi management network, Hewlett Packard Enterprise recommends that you use
the convention shown in the table.
Network
Purpose Example Count Notes
W.X.Y.n
W.X.Y.n+1
Management UI VM
VM
HC380 Management UI
installation.
initial configuration of the HC380
Management UI
Before you begin 9
Addresses
HC380
172.28.0.3
1
This value is the starting IP
ESXi Nodes (16
172.28.0.4 –
1 - 16
These address values are
CloudSystem
(optional)
172.28.0.20 -
25
For CloudSystem only.
CloudSystem
172.28.0.45 –
3
For CloudSystem only.
172.28.0.1
1
HC380 OneView VM
172.28.0.2
1
HC380 Management VM
172.28.0.3*
1
172.28.0.4* -
172.28.0.19*
16
Total: 19
VMs (optional)
172.28.0.20 -
25
172.28.0.45 –
172.28.0.47
3
Total: 47
Network
W.X.Y.n+2
W.X.Y.n+3 W.X.Y.n+18
W.X.Y.n+19 –
W.X.Y.n+43
W.X.Y.n+44 –
W.X.Y.n+46
Purpose Example Count Notes
Management VM
nodes)
Management &
Compute VMs
Console VIP
(optional)
172.28.0.19
172.28.0.44
172.28.0.47
address on the IP assignments
screen of OneView InstantOn.
automatically and sequentially
assigned to the nodes by
OneView InstantOn, starting
immediately after the HC380
Management VM IP address.
The examples shown above show that all IP addresses are contiguous. However, the only addresses that
the system requires to be contiguous are the addresses used by HC380 management VM and the ESXi
management network nodes. The other addresses are not required to be contiguous, but Hewlett Packard
Enterprise recommends that they be in the same address range, to enable expansion at a later date.
Use one of the following calculations to help you determine the number of IPv4 addresses you need for
your ESXi management network, where N is the number of nodes in your cluster.
• N + 3 (for General virtualization and VDI)
• N + 31 (for CloudSystem)
Use the following guidelines and examples for a 16-node and two-node cluster.
16-node cluster
For a 16-node cluster, you need between 19 and 47 IP addresses.
Purpose Example Count
HC380 Management UI VM
ESXi Nodes (16 nodes)
CloudSystem Management & Compute
CloudSystem Console VIP (optional)
* Must be contiguous
Two-node cluster
172.28.0.44
For a two-node cluster, Hewlett Packard Enterprise recommends that you reserve IP addresses to allow
for future expansion. Therefore, you need between 19 and 47 IP addresses.
Before you begin 10
172.28.0.1
1
HC380 OneView VM
172.28.0.2
1
172.28.0.3*
1
172.28.0.4*
172.28.0.5*
2
172.28.0.6* -
14
Total: 19
VMs (optional)
172.28.0.20-
25
172.28.0.45 –
3
Total: 47
Purpose Example Count
HC380 Management UI VM
HC380 Management VM
ESXi nodes (two nodes)
Reserved for expansion
172.28.0.19*
CloudSystem Management & Compute
CloudSystem Console VIP (optional)
* Must be contiguous
172.28.0.44
172.28.0.47
vSphere vMotion network IP addresses
The vSphere vMotion network requires contiguous IPv4 addresses, one for each HC380 node in the
cluster. In OneView InstantOn, you provide the first IP address as the starting address, and the program
automatically assigns all other IP addresses in sequence. Record the starting IP address on the
preinstallation worksheet ("Preinstallation worksheets" on page 14).
If you are installing CloudSystem, no additional IP addresses are needed.
Use the following examples for the required number of IP addresses:
• For a 16-node cluster, you will need 16 contiguous IPv4 addresses.
• For a two-node cluster, you will need 2 contiguous IPv4 addresses.
• For a three-node cluster, you will need 3 contiguous IPv4 addresses.
Storage network IP addresses
The storage network requires five contiguous IPv4 addresses for the first node and three contiguous IPv4
addresses for every additional node. These IP addresses are used by the HC380 Management VM, iSCSI
initiators, and HPE StoreVirtual.
Use the following examples for the required number of IP addresses:
• For a sixteen-node cluster, you will need 50 contiguous IPv4 addresses
• For a two-node cluster, you will need 8 contiguous IPv4 addresses
• For a three-node cluster, you will need 11 contiguous IPv4 addresses
In OneView InstantOn, you provide the first IP address as the starting address, and the program
automatically assigns all other IP addresses in sequence. Record the starting IP address on the
preinstallation worksheet ("Preinstallation worksheets" on page 14).
Planning for expansion
If you are planning to expand in the future, Hewlett Packard Enterprise recommends that you preallocate
the IP addresses that are needed for the future nodes. For each new expansion node, you need five IPv4
Before you begin 11
addresses for OneView InstantOn. HC380 Management UI also requires the iLO IPv4 address for the
node.
The five IPv4 addresses are used as follows:
• One address is used for the ESXi host.
• One address is used for the vSphere vMotion component on the ESXi host.
• Three addresses are used by the storage network, including two for the iSCSI initiators.
The following IP addresses from the initial system deployment are reused for the expansion process:
• HC380 Management UI VM
• HC380 OneView VM
• HC380 Management VM
• StoreVirtual cluster
If you are planning to expand to a 16-node system in the future, Hewlett Packard Enterprise recommends,
but does not require, that you preallocate the IP addresses that will be needed for the remaining nodes
now. Preallocating IP addresses for all 16 nodes allows you to assign contiguous blocks of IP addresses
to the various networks.
For each network type (ESXi, vSphere vMotion, Storage), you choose the first IP address in that group’s
range. After that IP address is chosen, OneView InstantOn will automatically increment and assign the
remaining IP addresses for that group.
VMware vCenter
The HC380 can be deployed with either a local vCenter Server instance, or with a remote vCenter Server
(or vCenter Server appliance) instance. Regardless of the vCenter Server location, it must have HPE
OneView for vCenter integrated. During OneView InstantOn configuration, OneView InstantOn checks
that the specified vCenter Server has OneView for vCenter configured, and will not continue until this
check is complete. For additional information, see "Appendix F: Remote vCenter setup (on page 107)."
NOTE: A remote vCenter setup is not supported with CloudSystem.
Before deploying the HC380 with the remote vCenter option, ensure that the following requirements are
met on the remote server on which VMware vCenter Server and OneView for VMware vCenter are
installed:
•Verify that the remote server is configured on a network that is accessible to the 10 GbE switches
that are connected to the HC380 system. You need the IP address for the remote vCenter server and
the default port used for SSO.
• Verify that the remote vCenter is not running on a host intended to be an HC380 appliance instance.
• Disable the firewalls for the HC380 appliance, or enable the following ports for inbound access:
o HPE HTTPS Port 3501 TCP
o HPE UIM Port 3504 TCP (must be accessible from the Management VM of the system running
OneView InstantOn)
NOTE:
• For more information about these ports, see “Default port values” in HP OneView for
• These firewall or port settings are only required during deployment of a new system
VMware vCenter Installation Guide found on the Hewlett Packard Enterprise website
(http://www.hpe.com/info/ovvcenter/docs).
installation or a system expansion. Once that deployment is complete, you can either
re-enable the firewalls or disable port access.
Before you begin 12
• Install VMware vCenter Server. Hewlett Packard Enterprise recommends that you always install the
• Install OneView for VMware vCenter and ensure that it has access to the networks that will be used
• Ensure that you have access to the OneView for VMware vCenter administrator credentials on the
• Verify that the remote server can support the additional system hosts, datacenter, and Virtual
HPE iLO 4
Although iLO 4 is not required for daily use, Hewlett Packard Enterprise recommends that you configure
the iLO of each HC380 server as part of the initial setup. iLO is required when performing a node
recovery, for perform a firmware update, and for CloudSystem. The default iLO credentials can be found
on the toe tag on each HC380 node.
For more information about configuring iLO, see HPE iLO 4 User Guide, which is available on the Hewlett
Packard Enterprise website (http://www.hpe.com/info/ilo/docs).
latest updates of the software.
for HC380 ESXi management and for HC380 storage.
remote server. These credentials are used by OneView InstantOn during deployment.
Machines that will be installed or added (expanded).
NOTE: To determine the supported limits for each version, see the VMware vCenter Server
documentation.
Before you begin 13
Preinstallation worksheets
added during an expansion)
Subnet Mask
Gateway
Subnet Mask
VLAN ID (optional, for CloudSystem)
Subnet Mask
Gateway
VLAN ID (optional, for CloudSystem)
This section contains information lists for data needed during the appliance installation and configuration.
If you are expanding an existing configuration, you will need to obtain data from the existing appliance and
Appliance networks
add any data for an expansion node.
For each network type (ESXi, vSphere vMotion, Storage), you choose the first IP address in the range for
that group. Once that IP address is chosen, OneView InstantOn automatically increments and assigns the
remaining IP addresses for that group. Each network type assigned in OneView InstantOn requires
contiguous IP addresses.
Use the worksheets for an initial installation and for an expansion.
ESXi Network Components
To help you plan the ESXi management network, see "ESXi management network IP addresses (on page
9)."
ESXi network components Value
Starting IP address
(used by the HC380 Management VM during
initial installation or by the first ESXi node being
vSphere vMotion IPs
To help you plan the vSphere vMotion network, see "vSphere vMotion network IP addresses (on page
11)."
vSphere vMotion IPs Value
Starting IP address
Storage network IPs
To help you plan the storage network, see "Storage network IP addresses (on page 11)."
Storage network IPs Value
Starting IP address
HC380 Management UI VM
Preinstallation worksheets 14
For the HC380 Management UI initial configuration, you assign two additional IPv4 addresses for the
Item
Value
password
HC380 Management UI VM IP address
Subnet Mask
Gateway
HPE OneView VM IP address
Subnet Mask
Port on remote vCenter system
User name for vCenter on remote system
Password for vCenter on remote system
on IP assignment screen)
on IP assignment screen)
IP assignment screen)
HC380 Management UI and HPE OneView components, listed in the worksheet.
To help you determine the IP addresses to use in this worksheet, see "ESXi management network IP
addresses (on page 9)."
HC380 Management UI VM administrator
Gateway
Remote vCenter
Use this section only:
• if you plan to use a remote vCenter in your initial HC380 installation
• if you are expanding and you selected the remote vCenter option during the initial installation
Initial installation
If you choose the remote vCenter option on the OneView InstantOn vCenter screen, you are required to
enter an HC380 Management VM IP address, subnet mask, gateway and DNS addresses into the
Management VM ESX Connectivity area on that screen. These values are used to configure the
Management VM so that HP OneView InstantOn can verify that the remote server can be accessed and
that the remote instance of HPE OneView for VMware vCenter is installed at the correct, minimum
version.
The HC380 Management VM IP address, subnet mask and gateway are automatically populated on the
OneView InstantOn IP assignment screen as the starting address for the ESXi Network Component. The
DNS value is used on the OneView InstantOn Settings screen.
For more information on a remote vCenter setup, see "Appendix F: Remote vCenter setup (on page
107)."
Item Value
IP address of remote vCenter system
IP address for HC380 Management VM on the ESXi
management network
(same as starting address of the ESXi components
Subnet Mask for the HC380 ESXi management
network
(same as subnet mask value of the ESXi components
Gateway on the HC380 ESXi management network
(same as gateway value of the ESXi components on
Preinstallation worksheets 15
Item Value
(same as DNS value from Settings screen)
Automatically populated from initial installation
Port
Automatically populated from initial installation
User name
Automatically populated from initial installation
Password
and can include numbers, or the _* characters
\ / , . ; ' " : characters
Only needed if connecting to a local vCenter
Storage network DNS
Storage network NTP (optional)
Storage network mail server
Storage network mail server port
Sender email
NFS file share path (for 2-node system)*
Use same value provided during initial installation
Use same value provided during initial installation
DNS Server on the HC380 ESXi management
network
Expansion
During an expansion, you are required to provide the password for the remote vCenter user name.
Remote vCenter server item Value
IP address
Settings
Use the following checklist to set up your storage network for a new installation.
Item Value
StoreVirtual user name
Must contain 3–30 characters, begin with a letter,
StoreVirtual password
Must contain 5–40 characters and not include the
vSphere license (optional)
Recipient email
* For more information, see "Appendix G: Management group quorum consideration (on page 109)."
Use the following checklist for an expansion.
Item Value
StoreVirtual user name
StoreVirtual password
Preinstallation worksheets 16
iLO addresses
iLO IPv4 address requirements
Each HC380 server has an iLO which is manually configured with an IPv4 address on the ESX
management network. HC380 Management UI imports the iLO for each of the servers by IP address
during its configuration process, so that it can then manage the iLOs.
HC380 Management UI does not require that you enter the serial number, but it does associate each IP
address to a serial number. All of the iLO IP addresses must be accessible from the ESXi management
network.
For more information about iLO, see "HPE iLO 4 (on page 13)."
iLO address worksheet
Use the worksheet to record the node serial number and the iLO IP address associated to that serial
number.
During an expansion, you can use this same worksheet and then manually enter the IPv4 addresses into
HC380 Management UI (Settings area) for each new node that you are adding.
Node Serial number iLO IP address
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Default user names and passwords
The following default usernames and passwords are shipped with the appliance or are needed to
complete the setup.
Preinstallation worksheets 17
administrator@vsphere.local
HyperConv!234
HC380 Management VM
administrator
HyperConv!234
root
HyperConv!234
Console
admin
unset
OpenStack Horizon Console
admin
unset
Appliances
cloudadmin
cloudadmin
CSA MarketPlace Portal
consumer
cloud
Operations Orchestration
administrator
unset
DCM IP Range: (25 contiguous IPs)
DCM VLAN ID:
DCM CIDR:
DCM Gateway:
DCM Management Appliance VIP:
DCM Management Appliance FQDN:
DCM Cloud Controller VIP:
DCM Cloud Controller FQDN:
DCM Enterprise Appliance VIP:
DCM Enterprise Appliance FQDN:
Cloud Management Network
CLM VLAN ID:
Consumer Access Network
CAN IP Range: (+3 contiguous IPs)
CAN VLAN ID:
CAN CIDR:
CAN Gateway:
CAN Cloud Controller VIP:
CAN Cloud Controller FQDN:
CAN Enterprise Appliance VIP:
CAN Enterprise Appliance FQDN:
Item Username Password
vCenter Server (local)
ESXi shell
iLO administrator
CloudSystem Operations
CloudSystem Management
For more information about iLO, see "HPE iLO 4 (on page 13)."
CloudSystem
Use the following worksheet to assist in the pre-planning for the CloudSystem workload configuration. If
you are installing the general virtualization or VDI workload configurations, you can skip this spreadsheet.
While the Block and Object networks are not used, the installation process requires a VLAN for each
network. Assign two unused VLAN IDs for these networks that do not interfere with any of your other
networks.
For more information, see "Appendix E: CloudSystem Network Diagram (on page 106)."
Item Value
Data Center Management Network
Preinstallation worksheets 18
Item Value
External Network
External VLAN ID:
Provider Networks
Provider 1 VLAN ID:
Provider 1 CIDR:
Provider 2 VLAN ID:
Provider 2 CIDR:
Provider 3 VLAN ID:
Provider 3 CIDR:
Provider 4 VLAN ID:
Provider 4 CIDR:
Tenant Networks
Tenant 1 VLAN ID:
Tenant 1 CIDR:
Tenant 2 VLAN ID:
Tenant 2 CIDR:
Tenant 3 VLAN ID:
Tenant 3 CIDR:
Tenant 4 VLAN ID:
Tenant 4 CIDR:
Block Storage Networks
Block Storage VLAN ID:
Object Proxy Network
Object Proxy VLAN ID:
Preinstallation worksheets 19
Appliance components
1
Bay 3, with 8 HDDs or SSDs (optional)
2
Bay 2, with 8 HDDs or SSDs (optional)
3
Bay 1, with 8 HDDs or SSDs
Item
Description
1
Bay 3, with 6 HDDs and 2 SSDs (optional)
Bay 2, with 6 HDDs and 2 SSDs (optional)
3
Bay 1, with 6 HDDs and 2 SSDs
The following diagrams are examples to help you understand important component locations. Because
the HC380 is available with an array of options, storage, networking and power components will vary
Front panel
depending on your specific configuration.
•Front panel with HDDs or SSDs in all three storage bays
Item Description
•Front panel hybrid configuration with 6 HDDs and 2 SSDs in each storage bay
2
Appliance components 20
Rear panel components
Item
Description
1
10 GbE NIC Port 2
2
10 GbE NIC Port 1 (FlexLOM)
nVIDIA graphics card (VDI only, optional)
4
iLO connector
5
1 GbE RJ-45 port 1 (do not use during initial configuration)
1 GbE RJ-45 port 2 (for connection to a laptop or workstation for setup, on
1 GbE RJ-45 port 3 (not used during initial configuration; available for
1 GbE RJ-45 port 4 (not used during initial configuration; available for
9
nVIDIA graphics card (VDI only, optional)
10
Power supply 1 (PS1)
11
Power supply 2 (PS2)
12
Rear panel HDDs (VDI only, optional)
1
1 GbE RJ-45 port 8
1 GbE RJ-45 port 7
3
1 GbE RJ-45 port 6
4
1 GbE RJ-45 port 5
General virtualization and VDI rear panel components
1 GbE RJ-45 port 1 (Do not use during initial configuration)
7
1 GbE RJ-45 port 2 (For connection to a laptop or workstation for setup, on
1 GbE RJ-45 port 3 (not used during initial configuration; available for
1 GbE RJ-45 port 4 (not used during initial configuration; available for
10
Power supply 1 (PS1)
11
Power supply 2 (PS2)
Item
Description
1
10 GbE NIC Port 2
2
10 GbE NIC Port 1
3
10 GbE NIC (Ports 4 and 3)
4
10 GbE NIC (Ports 6 and 5)
5
iLO connector
6
1 GbE RJ-45 port 1 (do not use during initial configuration)
1 GbE RJ-45 port 2 (for connection to a laptop or workstation for setup, on
1 GbE RJ-45 port 3 (not used during initial configuration; available for
1 GbE RJ-45 port 4 (not used during initial configuration; available for
Power supply 2 (PS1)
Power supply 2 (PS2)
management VM)
8
customer network)
9
customer network)
CloudSystem rear panel components
7
8
9
10
management VM)
customer network)
customer network)
11
Appliance components 22
Installing the HC380 appliance nodes
arrangement ensures proper airflow. Using a rack without blanking panels results in improper
If the 42U rack includes closing front and rear doors, you must allow
The clearance between the installed rack component and the side panels of the rack
This section provides instructions for installing the appliance nodes into a rack and cabling the network.
Optimum environment
When installing the server in a rack, select a location that meets the environmental standards described in
Space and airflow requirements
this section.
To allow for servicing and adequate airflow, observe the following space and airflow requirements when
deciding where to install a rack:
• Leave a minimum clearance of 63.5 cm (25 in) in front of the rack.
• Leave a minimum clearance of 76.2 cm (30 in) behind the rack.
• Leave a minimum clearance of 121.9 cm (48 in) from the back of the rack to the back of another rack
or row of racks.
Hewlett Packard Enterprise nodes draw in cool air through the front door and expel warm air through the
rear door. Therefore, the front and rear rack doors must be adequately ventilated to allow ambient room
air to enter the cabinet, and the rear door must be adequately ventilated to allow the warm air to escape
from the cabinet.
CAUTION: To prevent improper cooling and damage to the equipment, do not block the
ventilation openings.
When vertical space in the rack is not filled by a server or rack component, the gaps between the
components cause changes in airflow through the rack and across the servers. Cover all gaps with
blanking panels to maintain proper airflow.
CAUTION: Always use blanking panels to fill empty vertical spaces in the rack. This
cooling that can lead to thermal damage.
The 9000 and 10000 Series Racks provide proper server cooling from flow-through perforations in the
front and rear doors that provide 64 percent open area for ventilation.
CAUTION: When using a Compaq branded 7000 series rack, install the high airflow rack
door insert (PN 327281-B21 for 42U rack, PN 157847-B21 for 22U rack) to provide proper
front-to-back airflow and cooling.
CAUTION: If a third-party rack is used, observe the following additional requirements to
ensure adequate airflow and to prevent damage to the equipment:
• Front and rear doors—
5,350 sq cm (830 sq in) of holes evenly distributed from top to bottom to permit adequate
airflow (equivalent to the required 64 percent open area for ventilation).
• Side—
must be a minimum of 7 cm (2.75 in).
Installing the HC380 appliance nodes 23
Temperature requirements
es and voltage spikes and keeps the system in operation during a power
NEC and
To ensure continued safe and reliable equipment operation, install or position the system in a
well-ventilated, climate-controlled environment.
The maximum recommended ambient operating temperature (TMRA) for most server products is 35°C
(95°F). The temperature in the room where the rack is located must not exceed 35°C (95°F).
CAUTION: To reduce the risk of damage to the equipment when installing third-party options:
• Do not permit optional equipment to impede airflow around the server or to increase the
internal rack temperature beyond the maximum allowable limits.
• Do not exceed the manufacturer’s TMRA.
Power requirements
Installation of this equipment must comply with local and regional electrical regulations governing the
installation of information technology equipment by licensed electricians. This equipment is designed to
operate in installations covered by NFPA 70, 1999 Edition (National Electric Code) and NFPA-75, 1992
(code for Protection of Electronic Computer/Data Processing Equipment). For electrical power ratings on
options, refer to the product rating label or the user documentation supplied with that option.
WARNING: To reduce the risk of personal injury, fire, or damage to the equipment, do not
overload the AC supply branch circuit that provides power to the rack. Consult the electrical
When installing more than one server, you may need to use additional power distribution devices to safely
provide power to all devices. Observe the following guidelines:
authority having jurisdiction over wiring and installation requirements of your facility.
CAUTION: Protect the server from power fluctuations and temporary interruptions with a
regulating uninterruptible power supply. This device protects the hardware from damage
caused by power surg
failure.
• Balance the server power load between available AC supply branch circuits.
• Do not allow the overall system AC current load to exceed 80% of the branch circuit AC current
rating.
•Do not use common power outlet strips for this equipment.
Connecting a DC power cable to a DC power source
•Provide a separate electrical circuit for the server.
WARNING: To reduce the risk of electric shock or energy hazards:
• This equipment must be installed by trained service personnel, as defined by the
IEC 60950-1, Second Edition, the standard for Safety of Information Technology
Equipment.
• Connect the equipment to a reliably grounded Secondary circuit source. A Secondary
circuit has no direct connection to a Primary circuit and derives its power from a
transformer, converter, or equivalent isolation device.
• The branch circuit overcurrent protection must be rated 27 A.
WARNING: When installing a DC power supply, the ground wire must be connected before
the positive or negative leads.
Installing the HC380 appliance nodes 24
WARNING:
Remove power from the power supply before performing any installation steps or
If the DC connection exists between the earthed conductor of the DC supply circuit
This equipment should be located in the same immediate area (such as adjacent cabinets)
uipment that has a connection between the earthed conductor of the same
Switching or disconnecting devices should not be in the earthed circuit conductor between
The minimum nominal thread diameter of a pillar or stud type terminal must be
At least two people are needed to safely unload the rack from the pallet. An empty 42U rack
maintenance on the power supply.
CAUTION: The server equipment connects the earthed conductor of the DC supply circuit to
the earthing conductor at the equipment. For more information, see the documentation that
ships with the power supply.
CAUTION:
and the earthing conductor at the server equipment, the following conditions must be met:
• This equipment must be connected directly to the DC supply system earthing electrode
conductor or to a bonding jumper from an earthing terminal bar or bus to which the DC
supply system earthing electrode conductor is connected.
•
as any other eq
DC supply circuit and the earthing conductor, and also the point of earthing of the DC
system. The DC system should be earthed elsewhere.
• The DC supply source is to be located within the same premises as the equipment.
•
the DC source and the point of connection of the earthing electrode conductor.
To connect a DC power cable to a DC power source:
1. Cut the DC power cord ends no shorter than 150 cm (59.06 in).
2. If the power source requires ring tongues, use a crimping tool to install the ring tongues on the power
cord wires.
IMPORTANT: The ring terminals must be UL approved and accommodate 12 gauge wires.
IMPORTANT:
3.5 mm (0.138 in); the diameter of a screw type terminal must be 4.0 mm (0.157 in).
3. Stack each same-colored pair of wires and then attach them to the same power source. The power
cord consists of three wires (black, red, and green).
For more information, see the documentation that ships with the power supply.
Rack warnings
WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that:
• The leveling jacks are extended to the floor.
• The full weight of the rack rests on the leveling jacks.
• The stabilizing feet are attached to the rack if it is a single-rack installation.
• The racks are coupled together in multiple-rack installations.
• Only one component is extended at a time. A rack may become unstable if more than one
component is extended for any reason.
WARNING: To reduce the risk of personal injury or equipment damage when unloading a
rack:
•
can weigh as much as 115 kg (253 lb), can stand more than 2.1 m (7 ft) tall, and might
become unstable when being moved on its casters.
• Never stand in front of the rack when it is rolling down the ramp from the pallet. Always
handle the rack from both sides.
Installing the HC380 appliance nodes 25
Always plan the rack installation so that the heaviest item is on the bottom of the
To reduce the risk of electric shock, fire, or damage to the equipment, do not plug
slack in each of the cables to prevent damage to the cables when the server is extended from
Installing the node into the rack
CAUTION:
rack. Install the heaviest item first, and continue to populate the rack from the bottom to the top.
1. Install the server and cable management arm into the rack. For more information, see the installation
instructions that ship with the 2U Quick Deploy Rail System.
2. Connect peripheral devices to the server. For information on identifying connectors, see one of the
following:
o "General virtualization and VDI rear panel components (on page 21)"
o "CloudSystem rear panel components (on page 22)"
WARNING:
telephone or telecommunications connectors into RJ-45 connectors.
3. Connect the power cord to the rear of the server.
4. Install the power cord anchors.
5. Secure the cables to the cable management arm.
IMPORTANT: When using cable management arm components, be sure to leave enough
the rack.
Installing the HC380 appliance nodes 26
ems placed against
it. Pay particular attention to the plug, electrical outlet, and the point where the cord extends
6. Connect the power cord to the AC power source.
WARNING: To reduce the risk of electric shock or damage to the equipment:
• Do not disable the power cord grounding plug. The grounding plug is an important safety
feature.
• Plug the power cord into a grounded (earthed) electrical outlet that is easily accessible at all
times.
• Unplug the power cord from the power supply to disconnect power to the equipment.
• Do not route the power cord where it can be walked on or pinched by it
from the node.
Cabling the system
This section provides some cabling examples to help you properly cable your appliance. Your
configuration may differ from the examples, but the details should provide guidance for you to properly
cable the appliance in your environment.
After completing the network connections, be sure to connect the power cables to the system.
Hewlett Packard Enterprise recommends two 10GbE or 1GbE (if 1GbE solution is used) switches
configured in a highly available configuration to ensure a network switch failure does not prevent access
to the HC380 configuration. Examples on how to configure both HPE 5900 series switches and Cisco
Nexus 5600 switches are provided in "Appendix A: Network switch configuration (on page 85)."
Installing the HC380 appliance nodes 27
General virtualization configuration (all 1 GbE appliance)
1 GbE Switch A (IPv6 enabled)
13
Connect Node 2, Port 4 to Switch A (IPv6
Interconnect switch links
14
Connect Node 2, Port 2 to Switch A (IPv6
Interconnect switch links
15
Connect Node 2, Port 3 to Switch B (IPv6
1 GbE Switch B (IPv6 enabled)
16
Connect Node 2, Port 1 to Switch B (IPv6
Connect Node 1, Port 4 to Switch A (IPv6
enabled)
17
1GbE RJ-45 port 2 (not used)
Connect Node 1, Port 2 to Switch A (IPv6
18
1GbE RJ-45 port 3 (not used during initial
Connect Node 1, Port 3 to Switch B (IPv6
19
1GbE RJ-45 port 4 (not used during initial
Connect Node 1, Port 1 to Switch B (IPv6
enabled)
20
Node 2
1GbE RJ-45 port 2 (for connection to a
laptop or workstation for setup)
21
1 GbE Switch
1GbE RJ-45 port 3 (not used during initial
network)
22
Connect Node 2, iLO port to 1 GbE Switch
1GbE RJ-45 port 4 (not used during initial
network)
23
Connect Node 1, iLO port to 1 GbE Switch
Node 1
The following cabling example shows the use of three 1 GbE switches with the all 1 GbE appliance. This
example applies to the General Virtualization workload configuration only.
Item Description Item Description
1
2
3
4
5
6
enabled)
7
enabled)
8
9
10
configuration; available for customer
11
configuration; available for customer
enabled)
enabled)
enabled)
enabled)
configuration; available for customer network)
configuration; available for customer network)
12
Installing the HC380 appliance nodes 28
10 GbE Switch A (IPv6 enabled)
11
Connect Node 2, Port 2 to Switch A (IPv6
Interconnect switch links
12
Connect Node 2, Port 1 to Switch B (IPv6
3
Interconnect switch links
13
1GbE RJ-45 port 2 (not used)
10 GbE Switch B (IPv6 enabled)
14
1GbE RJ-45 port 3 (not used during initial
Connect Node 1, Port 2 to Switch A (IPv6
15
1GbE RJ-45 port 4 (not used during initial
Connect Node 1, Port 1 to Switch B (IPv6
enabled)
16
Node 2
1GbE RJ-45 port 2 (for connection to a
laptop or workstation for setup)
17
1 GbE Switch
1GbE RJ-45 port 3 (not used during initial
network)
18
Connect Node 2, iLO port to 1 GbE Switch
1GbE RJ-45 port 4 (not used during initial
network)
19
Connect Node 1, iLO port to 1 GbE Switch
Node 1
General virtualization (10GbE appliance) and VDI
configurations
The following cabling example shows the use of two 10 GbE switches and one 1 GbE switch. This
example applies to both the General Virtualization and VDI workload configurations. Though the rear
components might vary for each configuration, the cabling for the two configurations is similar.
Item Description Item Description
1
2
4
5
enabled)
6
7
8
configuration; available for customer
9
configuration; available for customer
10
enabled)
enabled)
configuration; available for customer network)
configuration; available for customer network)
Installing the HC380 appliance nodes 29
CloudSystem configuration
10 GbE Switch A (IPv6 enabled)
15
Connect Node 1, Port 4 to Switch A (IPv6
Interconnect switch links
16
Connect Node 1, Port 6 to Switch A (IPv6
Interconnect switch links
17
Connect Node 1, Port 5 to Switch B (IPv6
10 GbE Switch B (IPv6 enabled)
18
Connect Node 1, Port 3 to Switch B (IPv6
Connect Node 1, Port 4 to Switch A (IPv6
19
Node 2
Connect Node 1, Port 6 to Switch A (IPv6
20
Connect Node 2, Port 2 to Switch A (IPv6
Connect Node 1, Port 5 to Switch B (IPv6
21
Connect Node 2, Port 1 to Switch B (IPv6
Connect Node 1, Port 3 to Switch B (IPv6
22
1 GbE RJ-45 port 2
Node 1
23
1 GbE RJ-45 port 3 (not used during initial
Connect Node 1, Port 2 to Switch A (IPv6
24
1 GbE RJ-45 port 4 (not used during initial
Connect Node 1, Port 1 to Switch B (IPv6
enabled)
25
1 GbE Switch
Item Description Item Description
1
2
3
4
5
enabled)
6
enabled)
7
enabled)
8
enabled)
9
10
enabled)
11
enabled)
enabled)
enabled)
enabled)
enabled)
enabled)
(not used during initial configuration; available for
customer network)
configuration; available for customer network)
configuration; available for customer network)
Installing the HC380 appliance nodes 30
Loading...
+ 95 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.