This technical demonstration we'll show you how'd you configure
PowerChute Network Shutdown to support a Cisco HyperFlex edge cluster.
We'll then showcase PowerChute in action.
Protecting your HyperFlex equipment during a power outage.
Login to vCenter server and right click on the HyperFlex cluster;
select Deploy OVF Templates.
Select local file, click choose files and browse to the folder where you
download the PowerChute OVA file.
Enter a name for the PowerChute VM, then click next.
Select the HyperFlex cluster and click next.
Click next.
Accept the license agreement and click next.
Select a local data store on one of the target nodes and click next.
The drop-down list, select Storage Controller Management Network.
Customize Template allows you to configure a static IP address and
network settings for the PowerChute VM.
Enter a root password for logging into the PowerChute VM
Enable SSH access if required.
Enter your preferred time zone and click next.
Finished to start applying the PowerChute appliance.
When the deployment completes, select the PowerChute VM and power it on
Next click launch web console.
The council shows the PowerChute URL.
Enter this in a browser to launch the step-by-step set up wizard.
Click next.
Choose IPv4 or IPv6, depending on how your network management card is configured.
Select host management vCentral server and click next.
Enter the vCenter server details.
If your vCentral server uses a self signed SSL certificate, enable the
option except untrusted SSL certificates.
Choose HyperFlex from the dropdown list.
If vCenter is deployed as a VM on the cluster, select this option.
Select your UPS configuration type and click next.
Enter your security details.
The username and password I use to access the PowerChute DUI.
The authentification phrase is used to authenticate with
the network management card.
Enter the management card IP address, and click next.
Confirm your settings are correct.
And click apply to register PowerChute with the network management card.
Click next after registration is complete.
The host protection page displays all hosts in the VMware inventory.
PowerChute automatically detects the host running the vCenter
server VM, and the PowerChute VM.
Enter the HyperFlex cluster IP address and credentials for
the local HyperFlex admin use.
If using a self-signed SSL certificate, enable have the option except untrusted
SSL certificates, and click next.
If the UPS supports outlet groups, select the one that's powering
your equipment and click apply.
Click next.
Virtualization settings page allows you to define the times needed for
each step in the shutdown sequence, according to your HyperFlex cell.
Confirm your settings and then click next to apply the changes.
We recommend enabling the option to turn off the UPS.
After the cluster is gracefully shut down.
This helps for longer UPS battery life.
Instead of letting the battery drain each time there's a power outage.
Click finish to complete the setup.
Configure events allows you to define which events will trigger
the shutdown sequence; for example, UPS on battery for five minutes.
Shutdown settings allows you to configure the option to execute a command file
or script during the shutdown sequence.
Enabled VM prioritization to configure the order that your user
VMs would shut down or power back on.
Select VMs on the left and drag them to a priority group on the right.
VMs and high priority groups are shut down last and powered on first.
Set an appropriate duration for each priority group.
To skip powering on VMs in a particular group, you can set a
zero second duration for that group.
We will now showcase PowerChute in action, protecting your HyperFlex
cluster when a power outage occurs.
The UPS has been running on battery power for the configures duration.
This triggers, the shutdown sequence.
User VMs are shut down first.
The vCentral server VM is shut down after the user VMs.
PowerChute then shuts down the HyperFlex cluster service.
After the cluster service has been stopped, the HyperFlex
controller VMs are then shut down.
The whole spot running PowerChute is placed into maintenance mode,
and then gracefully shut down.
The PowerChute host is then gracefully shut down.
The nodes are powered on when AC power returns.
The HyperFlex controller VMs powered on followed by the PowerChute theme.
When PowerChute comes back online, it takes the other
host out of maintenance mode.
The controller VM is then powered on for that host.
When the controller VMs come back online.
The HyperFlex cluster service has started.
Now that the cluster service is back up and running, PowerChute
turns on the vCenter server VM.
The user VMs are then powered on.
The HyperFlex cluster is back online, following the power outage
without any data loss or corruption.
The V-Center server VM and user VMs have been automatically powered
back on; minimizing the downtime.
This concludes our technical demonstration.
We hope you found this useful and informative for more information,
please visit apc.com/pcns.