Dell PowerFlex Rack with PowerFlex 3.x Administration Guide

Power on the PowerFlex management controller 1.0

Power on the PowerFlex management controller 1.0.

1. Power on the PowerFlex management controller, verify VMware ESXi boots, and that you can ping the management IP address. Allow up to 20 minutes for the PowerFlex management controller to boot after VMware ESXi loads.
2. After the PowerFlex management controller is online, perform the following:
   1. Access each PowerFlex management controller through the host UI client or esxcli
   2. Type esxcli system maintenanceMode set -–enable false
   3. Type esxcli system maintenanceMode get
   4. Exit maintenance mode and verify that the PowerFlex management controller is placed out of maintenance mode.
3. Log in to PowerFlex management controller A through the VMware host client and verify that the DNS/NTP, VMware vCenter, and jump server exist. If the components are not on PowerFlex management controller A, verify that the components exist on PowerFlex management controller B or C and power them on.
   NOTE:External PSCs are not available for a single VMware vCenter environment. Only embedded PSCs are available for a single VMware vCenter. Log in to the PowerFlex management controller through VMware host client, and verify the VMs on the host are in power on state.
4. Verify that no vSAN components are resyncing, all objects are healthy, and there are no alerts or error messages:
   1. From esxcli on each host, run the following command to verify the vSAN cluster is not in maintenance mode:
      esxcli vsan cluster get
   2. From esxcli on each host, run the following command to verify that there are no inaccessible objects and all objects are in a healthy state:
      esxcli vsan health cluster list
5. Power on the DNS, NTP, and jump servers (if applicable).
6. Log in to the VMware vSphere Client and perform a vSAN health check. Verify that no components are resyncing. Complete the following steps:
   1. Go to the vSAN cluster in the VMware vSphere Client.
   2. Click the Monitor tab and click vSAN.
   3. Select Health to review the vSAN health check categories.
      NOTE:If the Test Result column displays Warning or Failed, expand the category to review the results of individual health checks.
   4. From the vSAN menu, select Resyncing Objects and verify that the list is empty.
7. If you are using VMware vCenter high availability, power on the controller and customer (if applicable) VMware vCSA VMs in the following order using the inventory captured prior to power down:
   • Witness
   • Acting Active
   • Acting Passive
8. From the VMware vCenter of the PowerFlex management controller, click Controller Cluster > Monitor > vSAN > Skyline Health > Re-test. Verify that no vSAN components are resyncing and that vSAN is healthy with no alerts or error messages.
   If the Test Result column displays Warning or Failed, expand the category to review the results of individual health checks. Correct any issues before proceeding.
9. If vCenter High Availability is in use, do the following:
   1. Power on the peer and witness VMs and enable them to fully boot.
   2. Select Single vCenter > Configure > vCenter HA and verify that the Active, Passive, and Witness nodes display as up and green.
   3. Click Edit, select Enable vCenter HA and click OK.
10. Power on the remaining management VMs in the following order:
    • PowerFlex Gateway
    • PowerFlex Manager
    • CloudLink Center VMs
    • PowerFlex GUI presentation server
    • Customer vCSA.
    • All the remaining VMs
11. If customer is running vCenter High Availability, perform the following:
    1. Select Customer vCenter > Configure > vCenter HA and verify that the Active, Passive, and Witness nodes display as up and green.
    2. Click Edit > Enable vCenter HA > OK.
12. Verify the following for HA, DRS, and affinity rules:
    1. Log in to the VMware vSphere Client and browse to the cluster.
    2. Click the Configure tab.
    3. Under Services, verify that the vSphere DRS and vSphere Availability are on.
    4. Under Configuration, verify that the VM/Host Rules are added.