Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products

Dell PowerFlex Rack with PowerFlex 3.x Administration Guide

PDF

Power off the PowerFlex management controller 1.0

Use this procedure to power off the PowerFlex management controller.

Steps

  1. Log in to VMware vSphere Client, take an inventory of the VMware vCenter HA roles (active, passive, and witness) within the VMware vCenter for both management and customer vCenters.
    NOTE:The appended names of the VMs may not properly reflect the current role that each vCSA VM is performing.
  2. Using the VMware vSphere Client, shut down all VMs running on the vSAN cluster, except the customer and PowerFlex management controller VMware vCenter, DNS server or NTP server (if applicable), vCLS, and jump server.
  3. If VMware vCenter HA is enabled on customer or controller vCenters, perform the following:
    1. Select vCenter > Configure > vCenter HA.
    2. Click Edit.
    3. Select Maintenance Mode and click OK.
  4. Shut down the customer vCenter HA VMs in the following order:
    1. Acting passive
    2. Acting active
    3. Witness
  5. Select the PowerFlex management controller, disable HA, and set DRS to manual.
  6. Disable anti-affinity rules and manually migrate all controller vCenters, DNS/NTP servers (if applicable), vCLS, and jump server VMs to PowerFlex management controller A.
    NOTE:Document all the rule enablement settings in VMware vCenter to re-enable the settings after powering on PowerFlex management controller 1.0.
    NOTE:If vCLS VMs are on local storage, they are not migrated.
  7. From the PowerFlex management controller vCenter VMware vSphere Client, perform the following:
    1. Select Cluster > Monitor > vSAN > Skyline Health.
    2. Select Re-test.
    3. Verify that no vSAN components are resyncing and that vSAN is healthy with no alerts or error messages.
      NOTE:If the Test Result column displays Warning or Failed, expand the category to review the results of individual health checks. Address any issues before proceeding.
  8. From PowerFlex management controller A VMware vSphere Client, shut down the remaining VMs in the following order:
    1. Acting passive controller vCSA VM
    2. Acting active controller vCSA VM
    3. Witness controller vCSA VM
    4. NTP/DNS server (if applicable)
    5. Jump server
  9. To place each PowerFlex management controller into maintenance mode, perform the following from esxcli on each host:
    1. Type:

      esxcli system maintenanceMode set --enable true --vsanmode noAction

    2. To see the list of VMs and document the vCLS VM ID, type:

      #vim-cmd vmsvc/getallvms

    3. The vCLS VMs are powered on automatically. To avoid a race condition, manually shut down the vCLS VMs for the host to go into maintenance mode either using host UI client or esxcli, type:

      #vim-cmd vmsvc/power.off  <vCLS VM-ID>

    4. To verify that the host is placed in maintenance mode, type:

      esxcli system maintenanceMode get

  10. Once placed into maintenance mode, shut down the PowerFlex management controller hosts:

    esxcli system shutdown poweroff --reason powerflexrack-shutdown


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\