Post Installation Tasks

(1GE Only) Run Post Installation Script

Procedure

Step 1

In your web browser, navigate to http://<installer VM IP address>/mssh, and log in using username admin and your password, and run hx_post_install.

Step 2

Press Enter to start post installation tasks in the web-based SSH window.

On execution of the post installation script, choose one of the following options as per the requirement:

  • 1—To run the post installation script on a newly created cluster or on an existing cluster. On selection of this option, the script runs the post installation operations on all the nodes in the cluster.

  • 2—To run the post installation script on expanded nodes or on newly added nodes after executing the expansion workflow. On selection of this option, the script fetches the list of the expanded nodes and runs the post installation operations on the expanded nodes.

  • 3—To have unique SSL certificate in the cluster. On selection of this option, the current certificate is replaced with the newly created SSL certificate. This option is not required for the cluster expansion.

Step 3

Follow the on-screen prompts to complete the installation.

The hx_post_install script completes the following:

  • License the vCenter host.

  • Enable HA/DRS on the cluster per best practices.

  • Suppress SSH/Shell warnings in vCenter.

  • Configure vMotion per best practices.

  • Add additional guest VLANs/portgroups.

  • Perform HyperFlex Edge configuration check.

On successful completion of the post_install workflow, the summary of the configuration executed based on the chosen option is displayed under Cluster Summary.

Sample Post-Install Script is as follows:
admin@SpringpathController:~$ hx_post_install

Select post_install workflow-

1. New/Existing Cluster
2. Expanded Cluster (for non-edge clusters)
3. Generate Certificate

Note: Workflow No.3 is mandatory to have unique SSL certificate in the cluster. By Generating this certificate, it will replace your current certificate. If you're performing cluster expansion, then this option is not required.

Selection: 1
Logging in to controller HX-01-cmip.example.com
HX CVM admin password:
Getting ESX hosts from HX cluster...
vCenter URL: 192.168.202.35
Enter vCenter username (user@domain): administrator@vsphere.local
vCenter Password:
Found datacenter HX-Clusters
Found cluster HX-01

post_install to be run for the following hosts:
HX-01-esxi-01.example.com
HX-01-esxi-02.example.com
HX-01-esxi-03.example.com

Enter ESX root password:

Enter vSphere license key? (y/n) n

Enable HA/DRS on cluster? (y/n) y
Successfully completed configuring cluster HA.

Disable SSH warning? (y/n) y

Add vmotion interfaces? (y/n) y
Netmask for vMotion: 255.255.254.0
VLAN ID: (0-4096) 208
vMotion MTU is set to use jumbo frames (9000 bytes). Do you want to change to 1500 bytes? (y/n) y
vMotion IP for HX-01-esxi-01.example.com: 192.168.208.17
Adding vmotion-208 to HX-01-esxi-01.example.com
Adding vmkernel to HX-01-esxi-01.example.com
vMotion IP for HX-01-esxi-02.example.com: 192.168.208.18
Adding vmotion-208 to HX-01-esxi-02.example.com
Adding vmkernel to HX-01-esxi-02.example.com
vMotion IP for HX-01-esxi-03.example.com: 192.168.208.19
Adding vmotion-208 to HX-01-esxi-03.example.com
Adding vmkernel to HX-01-esxi-03.example.com

Add VM network VLANs? (y/n) y
 Attempting to find UCSM IP
 Found UCSM 10.75.61.254, logging with username admin.  Org is HX-Cluster
 UCSM Password:
 Port Group Name to add (VLAN ID will be appended to the name): USERS
 VLAN ID: (0-4096) 1219
 Adding VLAN 1219 to FI
 Adding VLAN 1219 to vm-network-a VNIC template
 Adding USERS-1219 to HX-01-esxi-01.example.com
 Adding USERS-1219 to HX-01-esxi-02.example.com
 Adding USERS-1219 to HX-01-esxi-03.example.com
Add additional VM network VLANs? (y/n) n

Run health check? (y/n) y

Validating cluster health and configuration...

Cluster Summary:
Version - 3.5(2i)
Model - HXAF220C-M5SX
Health - HEALTHY
ASUP enabled - False
admin@SpringpathController:~$

(10/25GE Only) Run Post Installation Script

Procedure

Step 1

In your web browser, navigate to http://<installer VM IP address>/mssh, and log in using username admin and your password, and run hx_post_install.

Step 2

Press Enter to start post installation tasks in the web-based SSH window.

On execution of the post installation script, choose one of the following options as per the requirement:

  • 1—To run the post installation script on a newly created cluster or on an existing cluster. On selection of this option, the script runs the post installation operations on all the nodes in the cluster.

  • 2—To run the post installation script on expanded nodes or on newly added nodes after executing the expansion workflow. On selection of this option, the script fetches the list of the expanded nodes and runs the post installation operations on the expanded nodes.

  • 3—To have unique SSL certificate in the cluster. On selection of this option, the current certificate is replaced with the newly created SSL certificate. This option is not required for the cluster expansion.

Step 3

Follow the on-screen prompts to complete the installation.

The hx_post_install script completes the following:

  • License the vCenter host.

  • Enable HA/DRS on the cluster per best practices.

  • Remove SSH/Shell warnings in vCenter.

  • Configure vMotion per best practices.

  • Add new VM portgroups

  • Perform HyperFlex Edge health check.

On successful completion of the post_install workflow, the summary of the configuration executed based on the chosen option is displayed under Cluster Summary.

Sample Post-Install Script is as follows:
admin@SpringpathController:~$ hx_post_install

Select post_install workflow-

1. New/Existing Cluster
2. Expanded Cluster (for non-edge clusters)
3. Generate Certificate

Note: Workflow No.3 is mandatory to have unique SSL certificate in the cluster. By Generating this certificate, it will replace your current certificate. If you're performing cluster expansion, then this option is not required.

Selection: 1
Logging in to controller HX-01-cmip.example.com
HX CVM admin password:
Getting ESX hosts from HX cluster...
vCenter URL: 192.168.202.35
Enter vCenter username (user@domain): administrator@vsphere.local
vCenter Password:
Found datacenter HX-Clusters
Found cluster HX-01

post_install to be run for the following hosts:
HX-01-esxi-01.example.com
HX-01-esxi-02.example.com
HX-01-esxi-03.example.com

Enter ESX root password:

Enter vSphere license key? (y/n) n

Enable HA/DRS on cluster? (y/n) y
Successfully completed configuring cluster HA.

Disable SSH warning? (y/n) y

Add vmotion interfaces? (y/n) y
Netmask for vMotion: 255.255.254.0
VLAN ID: (0-4096) 208
vMotion MTU is set to use jumbo frames (9000 bytes). Do you want to change to 1500 bytes? (y/n) y
vMotion IP for HX-01-esxi-01.example.com: 192.168.208.17
Adding vmotion-208 to HX-01-esxi-01.example.com
Adding vmkernel to HX-01-esxi-01.example.com
vMotion IP for HX-01-esxi-02.example.com: 192.168.208.18
Adding vmotion-208 to HX-01-esxi-02.example.com
Adding vmkernel to HX-01-esxi-02.example.com
vMotion IP for HX-01-esxi-03.example.com: 192.168.208.19
Adding vmotion-208 to HX-01-esxi-03.example.com
Adding vmkernel to HX-01-esxi-03.example.com

Add VM network VLANs? (y/n) y
 Attempting to find UCSM IP
 Found UCSM 10.75.61.254, logging with username admin.  Org is HX-Cluster
 UCSM Password:
 Port Group Name to add (VLAN ID will be appended to the name): USERS
 VLAN ID: (0-4096) 1219
 Adding VLAN 1219 to FI
 Adding VLAN 1219 to vm-network-a VNIC template
 Adding USERS-1219 to HX-01-esxi-01.example.com
 Adding USERS-1219 to HX-01-esxi-02.example.com
 Adding USERS-1219 to HX-01-esxi-03.example.com
Add additional VM network VLANs? (y/n) n

Run health check? (y/n) y

Validating cluster health and configuration...

Cluster Summary:
Version - 3.5(2i)
Model - HXAF220C-M5SX
Health - HEALTHY
ASUP enabled - False
admin@SpringpathController:~$

Configuring vMotion

Configuring vMotion Automatically

The hx_post_install script automatically configures vMotion based on network topology.

1GE Single Switch Considerations

  • Automated configuration supports only trunk ports and only configurations using a dedicated vMotion VLAN.

  • If using access ports or using a shared vMotion VLAN, you have to manually configure vMotion on the existing management VMkernel port (vmk0).

  • vMotion is shared on the 1GE management and VM network uplink.

  • A new VMKernel port (vmk2) is created with a default 500Mbps traffic shaper to ensure vMotion doesn’t fully saturate the link. This default value may be changed after running hx_post_install. See Configuring Traffic Shaping Manually.

1GE Dual Switch Considerations

  • vMotion is configured on a dedicated 1GE uplink.

  • A new VMKernel port (vmk2) is created. Failover order is auto-configured such that storage data and vMotion are separated under normal network conditions.

  • No traffic shaper is required in this configuration.

10/25GE Switch Considerations

  • vMotion vMotion is configured on dedicated vMotion vSwitch with dedicate active/standby vNICs.

  • A new VMKernel port (vmk2) is created. Failover order is auto-configured such that storage data and vMotion are separated under normal network conditions.

  • No traffic shaper is required in this configuration, although bandwidth is shared among management, vMotion, and guest VM port groups. You may apply an optional traffic shaper depending on your networking requirements.

Configuring vMotion Manually

vMotion can be configured in a number of different ways depending on environmental needs. This task covers one possible configuration and variations to this procedure are expected and permitted.

This configuration leverages a unique VLAN for vMotion that is trunked across port 1.

Procedure

Step 1

Launch vShpere, and log in to the vCenter Server as an administrator.

Step 2

From the vCenter Inventory Lists, click the HyperFlex host, and navigate to Manage > Networking > Virtual Switches.

Step 3

Click Add Host Networking.

Step 4

On the Add Network Wizard: Connection Type page, click VMkernel, and click Next.

Step 5

Click Use vswitch-hx-inband-mgmt, and click Next.

Step 6

Enter a distinctive Network Label, such as vMotion, enter the correct VLAN ID, check Use this port group for vMotion, and click Next.

Step 7

Click Use the following IP settings, enter a static IPv4 address and Subnet Mask, and click Next.

Step 8

Review the settings, and click Finish.

Step 9

Repeat this procedure for all HyperFlex hosts and compute-only hosts in the HyperFlex storage cluster.

Configuring Traffic Shaping Manually

For 1GE single switch deployments, it is a best practice to enable traffic shaping on the vMotion interface to prevent network congestion on shared uplinks. Failure to configure a traffic shaper could result in vMotion traffic starving management and VM guest traffic sharing the same physical 1GE port. vMotion standard switches only allow for egress traffic shaping.

Procedure

Step 1

Launch vSphere, and log in to the vCenter Server as an administrator.
Step 2

From the vCenter Inventory Lists, click the HyperFlex host, and navigate to Manage > Networking > Virtual Switches.

Step 3

Select the vSwitch that contains the vMotion portgroup.
Step 4

Click the vMotion portgroup name, and click Edit Settings (pencil icon).

Step 5

On the left menu, select Traffic shaping.

Step 6

Check the override box to enable the traffic shaper.
Step 7

Set the average and peak bandwidth to meet environmental needs. One possible value to use is 500,000 Kbits/sec for both, representing 50% of total bandwidth available on a 1GE uplink.

Step 8

Select OK to save settings.

Note 
Be careful to set average bandwidth to the desired setting. Peak bandwidth works only for bursting traffic and is quickly exhausted for vMotion operations.