Dell PowerStore 1200T EMC PowerStore Software Upgrade Guide - Page 12

PowerStore X model clusters, automatically migrated when an ESXi host is placed into maintenance mode.

Get Dell PowerStore 1200T PDF manuals and user guides View all Dell PowerStore 1200T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

User VMs automatically migrate to the other node in the appliance. After all user VMs are migrated, the controller VM automatically shuts down and the ESXi host enters maintenance mode. NOTE: Some user VMs may not migrate due to local dependencies or lack of resources. User intervention may be required to manually power off these user VMs to allow the ESXi host to enter maintenance mode. See ESXi and VM considerations (PowerStore OS 1.0.x to 2.0.x) on page 18 for more information. CAUTION: Do not manually power off the controller VMs, which are named PSTX-. The controller VMs are automatically powered off when an ESXi host is placed into maintenance mode. CAUTION: Do not manually migrate or power off the vCLS VMs on the ESXi hosts. The vCLS VMs are automatically migrated when an ESXi host is placed into maintenance mode. d. Open an SSH client and connect to the management IP address of the appliance that contains the ESXi host that is in maintenance mode. NOTE: External SSH management access must be enabled on the appliance. e. Enter the username and password of the service account to log in to the appliance. f. Run the following command to resize the VMFS datastore on the ESXi host: svc_esxi_helper upgrade NOTE: Resizing the VMFS datastore can take over one hour to complete. 7. Reboot the ESXi host on the secondary node of an appliance to update the node firmware and install ESXi updates. a. In the vSphere Client, right-click the ESXi host and select Power > Reboot. After a few minutes, the status ESXi host should change to Not responding, which indicates that the host is rebooting. NOTE: The following alert is displayed in PowerStore Manager while the controller VM is shut down: Node has been physically removed or shut down b. Monitor the ESXi host reboot. NOTE: The ESXi update takes approximately 30 minutes to complete. The status changes back to Maintenance Mode after the reboot is complete. c. Exit maintenance mode on the ESXi host after the reboot is complete. The controller VM should automatically start when the ESXi host exits maintenance mode. d. Ensure that the ESXi host and controller VM are operating normally before continuing. ● Monitor the Protocol Endpoint (PE) paths in vCenter to identify when the paths to the ESXi host are Active before continuing. ● Monitor the alerts in PowerStore Manager to identify when the node is up. Then, wait 15 minutes after the alert is cleared before continuing. 8. Repeat steps 6 and 7 to resize the VMFS datastore and update the ESXi host on the primary node of an appliance. NOTE: PowerStore Manager temporally stops displaying performance metrics when the primary node of the primary appliance reboots during the ESXi update. 9. Migrate the VMs back to the preferred node in the cluster using vMotion. 10. Repeat steps 6 through 9 to update the ESXI hosts on the nodes of the other appliances in the PowerStore X model cluster. Results The ESXi hosts on the nodes of the cluster are now powered on and running the updated version of ESXi. The version of ESXi that the ESXi hosts are running is visible on the Upgrades page in PowerStore Manager. ● If the ESXi versions on the nodes of an appliance do not match, an alert is generated. ● If the ESXi versions on the appliances in the cluster do not match, an alert is generated. Next steps Go to Upgrade the PowerStore OS on the cluster (PowerStore OS 2.0.x or later) on page 13. 12 PowerStore X model clusters

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
User VMs automatically migrate to the other node in the appliance. After all user VMs are migrated, the controller VM
automatically shuts down and the ESXi host enters maintenance mode.
NOTE:
Some user VMs may not migrate due to local dependencies or lack of resources. User intervention may be
required to manually power off these user VMs to allow the ESXi host to enter maintenance mode. See
ESXi and VM
considerations (PowerStore OS 1.0.x to 2.0.x)
on page 18 for more information.
CAUTION:
Do not manually power off the controller VMs, which are named
PSTX-
<service_tag>
-
<node_letter>
. The controller VMs are automatically powered off when an ESXi host is placed into
maintenance mode.
CAUTION:
Do not manually migrate or power off the vCLS VMs on the ESXi hosts. The vCLS VMs are
automatically migrated when an ESXi host is placed into maintenance mode.
d.
Open an SSH client and connect to the management IP address of the appliance that contains the ESXi host that is in
maintenance mode.
NOTE:
External SSH management access must be enabled on the appliance.
e.
Enter the username and password of the service account to log in to the appliance.
f.
Run the following command to resize the VMFS datastore on the ESXi host:
svc_esxi_helper upgrade
NOTE:
Resizing the VMFS datastore can take over one hour to complete.
7.
Reboot the ESXi host on the secondary node of an appliance to update the node firmware and install ESXi updates.
a.
In the vSphere Client, right-click the ESXi host and select
Power
>
Reboot
.
After a few minutes, the status ESXi host should change to
Not responding
, which indicates that the host is
rebooting.
NOTE:
The following alert is displayed in PowerStore Manager while the controller VM is shut down:
Node has been physically removed or shut down
b.
Monitor the ESXi host reboot.
NOTE:
The ESXi update takes approximately 30 minutes to complete.
The status changes back to
Maintenance Mode
after the reboot is complete.
c.
Exit maintenance mode on the ESXi host after the reboot is complete.
The controller VM should automatically start when the ESXi host exits maintenance mode.
d.
Ensure that the ESXi host and controller VM are operating normally before continuing.
●
Monitor the Protocol Endpoint (PE) paths in vCenter to identify when the paths to the ESXi host are Active before
continuing.
●
Monitor the alerts in PowerStore Manager to identify when the node is up. Then, wait 15 minutes after the alert is
cleared before continuing.
8.
Repeat steps 6 and 7 to resize the VMFS datastore and update the ESXi host on the primary node of an appliance.
NOTE:
PowerStore Manager temporally stops displaying performance metrics when the primary node of the primary
appliance reboots during the ESXi update.
9.
Migrate the VMs back to the preferred node in the cluster using vMotion.
10.
Repeat steps 6 through 9 to update the ESXI hosts on the nodes of the other appliances in the PowerStore X model cluster.
Results
The ESXi hosts on the nodes of the cluster are now powered on and running the updated version of ESXi. The version of ESXi
that the ESXi hosts are running is visible on the
Upgrades
page in PowerStore Manager.
●
If the ESXi versions on the nodes of an appliance do not match, an alert is generated.
●
If the ESXi versions on the appliances in the cluster do not match, an alert is generated.
Next steps
Go to
Upgrade the PowerStore OS on the cluster (PowerStore OS 2.0.x or later)
on page 13.
12
PowerStore X model clusters