Expanding Cloudsystem; Compute Node Expansion; Pre-Expansion Preparation - HP Hyper Converged 380 Installation Manual

Expanding CloudSystem

Compute node expansion

When CloudSystem has been installed on an HC380, the default networking has been adjusted to suit the
CloudSystem requirements. For compute nodes, the management network, or Data Center Management
(DCM) which uses portgroup ESXcomp on the vSwitch1 standard switch in vCenter has been assigned a
VLAN ID and migrated to a vCenter distributed switch CS9_Compute_DVS and portgroup dvESXcomp
(management hosts are migrated to CS9_Mgmt_DVS and portgroup dvESXmgmt). It is the same
situation for management nodes where the DCM network which uses portgroup ESXmgmt on the
vSwitch1 standard switch in vCenter has been assigned a VLAN ID and migrated to a vCenter distributed
switch CS9_Mgmt_DVS and portgroup dvESXmgmt.
The OneView InstantOn expansion process currently does not provide an automated way to add a
compute node. Manual steps are need to configure a new node into the compute host cluster. There are
four key steps to follow, five for compute. On the details, there are specifics to either the management or
compute node that are highlighted.
Pre-expansion preparation of the network configuration for the new node.
1.
Configure the new node in CMC.
2.
Configure the volume(s) in vCenter.
3.
Configure the new node on the virtual distributed switch of vCenter.
4.
(Compute only) Activate the compute host cluster.
5.

Pre-expansion preparation

Prepare the IP address, netmask, gateway, and VLAN's of the new node for ESXmgmt, vMotion,
1.
HostStorage2 and HostStorage3 networks. The values should be on the same range and values as
the existing nodes.
Open up the port for vmnic0 of the new node in the Top of Rack switch to access the DHCP address
2.
via vSphere client on the Jump Station or installation laptop.
Launch vSphere client and connect to the new node's DHCP IP as root user.
3.
Power off the HPE-HC-management VM.
a.
Delete the VM from disk. There should be only the VSA VM left and keep it powered off.
b.
Edit networks of the ESXi host:
c.
Add the Storage VLAN to VSAeth0.
i.
Add the DCM network VLAN and configure the IP, Subnet, and Gateway of ESXmgmt.
ii.
Add the vMotion VLAN and configure the IP, Subnet, and Gateway of vMotion.
iii.
Add the Storage VLAN and configure the IP, Subnet, and Gateway of HostStorage2.
iv.
Add the Storage VLAN and configure the IP, Subnet, and Gateway of HostStorage3.
v.
Remove the dash "-" at the end of the VSA VM name.
d.
Verify that you can ping the ESXmgmt IP.
e.
Exit the vSphere client.
f.
Re-launch the vSphere client and connect to the management VM IP, i.e. 192.168.42.100.
4.
Add the new ESXi node to the CloudSystem compute cluster using the ESXmgmt IP.
a.
Power on the new VSA VM.
b.
Once fully booted, launch the console of the VM.
c.
Type start at the login prompt.
i.
Expanding the system 69