OmniStack Virtual Controller Shutdown/Startup

An OmniStack Virtual Controller (OVC) is deployed on each HPE SimpliVity node and is responsible for managing the HPE SimpliVity Cluster.

OVC Shutdown is enabled by default. In the PowerChute shutdown sequence, the OVC is shut down after all other VMs in the Cluster. The first OVC VM is shut down using the "Shut Down Safe" option in vSphere, which triggers a Wait for Storage HA Compliance task. When this task is complete, the OVC VM is shut down. Subsequent OVC VMs are shut down using the "Force Virtual Controller Shutdown" command.

All OmniStack Virtual Controllers in the HPE SimpliVity Cluster must be powered on and accessible during PowerChute setup to ensure they are shut down and started by PowerChute as expected.

The Duration field is the time allowed for all the OVCs to gracefully shut down. If the OVCs are shut down before the Duration time, PowerChute waits until this time has elapsed before proceeding to the next step in the sequence.

Using the Shutdown Duration field, you must allow sufficient time for all your OVCs to gracefully shut down before the hosts are commanded to shut down.

OVC Shutdown/Startup

Re-starting after a shutdown

If the Skip Maintenance Mode checkbox is selected in PowerChute, the OmniStack Virtual Controller VMs will get started automatically using the VMware VM Shutdown/Startup configuration for each host. PowerChute will not start the OmniStack Virtual Controller VMs, but PowerChute will still wait the configured OVC Startup Duration before proceeding with User VM startup

If PowerChute is deployed as a VM and VMware HA is disabled for the cluster, the PowerChute VM should be configured to start after the OmniStack Virtual Controller VMs using the VM Shutdown/Startup option in vSphere.

It is recommended to wait at least 5 minutes after OVC startup to ensure all services are running. You should account for this using the OVC Startup Duration field.