Dell PowerFlex Appliance with PowerFlex 4.x Administration Guide

Power off the PowerFlex management controller 2.0

Power off the PowerFlex management controller 2.0 on each of the PowerFlex management controller VMware ESXi hosts.

1. Determine the primary MDM IP address:
   1. Log in to PowerFlex Manager to determine the primary MDM.
   2. To view the details of a resource group, click Lifecycle > Resource Groups > PowerFlex management controller 2.0 resource group. Scroll to the Service Details page and make a note of the primary MDM IP address.
2. Log in to the primary MDM using SSH.
3. Log in to the MDM cluster:
   #scli --login --management_system_ip <PFxM_IP_Address> --username admin --password <PFxM_Password>
4. Identify the storage pools for each protection domain and record the protection domain or storage pool mappings:
   #scli --query_all_volumes --protection_domain_name pfmc | grep "Storage Pool"
5. Log in to the PowerFlex management platform primary node using SSH and run the following commands to stop the CMO database:
   # echo alias k="kubectl -n $(kubectl get pods -A | grep -m 1 -E 'platform|pgo|helmrepo' | cut -d' ' -f1)"
   # kubectl config set-context default --namespace=$(kubectl get pods -A | grep -m 1 -E 'platform|pgo|helmrepo|docker' | cut -d' ' -f1)
   # echo $(kubectl get pods -l="postgres-operator.crunchydata.com/control-plane=pgo" --no-headers -o name && kubectl get pods -l="postgres-operator.crunchydata.com/instance" --no-headers -o name) | xargs kubectl get -o wide
   # kubectl -n powerflex patch $(kubectl -n powerflex get postgrescluster -o name) --type merge --patch '{"spec":{"shutdown":true}}'
6. Verify the database shutdown. Only the PostgreSQL operator pod pgo must remain the same when running the command:
   #echo $(kubectl get pods -l="postgres-operator.crunchydata.com/control-plane=pgo" --no-headers -o name && kubectl get pods -l="postgres-operator.crunchydata.com/instance" --no-headers -o name) | xargs kubectl get -o wide
7. Disable vSphere high availability and change startup order of SVMs. If the host is part of a vSphere high availability cluster, the automatic startup and shutdown of VMs is disabled.
   1. Log in to VMware vSphere Client.
   2. From vSphere Client > Shortcuts > Hosts and Clusters.
   3. Browse to the cluster.
   4. Click the Configure tab.
   5. Select vSphere Availability and click Edit.
   6. Click the toggle button to disable vSphere HA.
   7. Click OK.
8. Modify the startup order of SVMs to manual to enable the vSphere high availability. This is applicable for all SVMs in the management controller PowerFlex cluster:
   1. In the VMware vSphere Client, select the host where the VM is located.
   2. Click the Configure tab.
   3. Under Virtual Machines, select VM Startup/Shutdown, and click Edit.
      The Edit VM Startup and Shutdown window opens.
   4. Select the Automatically start and stop the virtual machines with the system check box.
   5. Set shutdown action to Guest shutdown.
   6. To change the startup order of VMs, select a virtual machine from the Manual Startup category and use the up arrow to move the VM to the Automatic category.
   7. Select the SVM and move it to Automatic category. This ensures that the SVM automatically stops and starts with the VMware ESXi system.
   8. Repeat the steps for all the SVMs.
   9. Verify the settings and click OK.
9. Gracefully shut down all the VMs except SVMs and vCenter VM:
   1. Log in to VMware vSphere Client.
   2. From vSphere Client > Shortcuts > Hosts and Clusters.
   3. Browse and right-click the VM and select Power > Shut Down Guest OS.
   Since SVMs are set to automatically stop and start, there is no need to manually power off.
10. Identify the host where the vCenter server is running and make a note of the IP address or hostname. If vCenter high availability is enabled, make a note of the IP addresses of the hosts where active, passive, and witness nodes are running:
    1. Log in to VMware vSphere Client.
    2. From vSphere Client > Shortcuts > Hosts and Clusters.
    3. Browse the vCenter VM.
    4. Make a note of the host IP address from the Summary page.
11. Shut down the vCenter server VM gracefully. If you have vCenter high availability that is configured, shut down the active, passive, and witness nodes:
    1. Log in to the VMware ESXi using the host client.
    2. Click Virtual Machines > Select the vCenter VM and click to open a browser console.
    3. Press F12 to shut down the VM.
    4. Enter the root password and press OK.
12. Shut down the VMware ESXi servers gracefully:
    1. Log in to VMware ESXi Host Client.
    2. Right-click Host and select Shut down.
    3. To confirm the shutdown of the selected host, click SHUT DOWN.
    4. Repeat the steps for all the remaining nodes.