Dell PowerStore 500T EMC PowerStore Software Upgrade Guide - Page 14

Select Patches Automatically

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

Page 14 highlights

Steps 1. Identify the primary and peer nodes on the primary appliance of the cluster. See Minimizing internal ESXi host failover occurrences on page 11 for more information. 2. Select Compute > vCenter Server Connection and select Launch vSphere to start the vSphere Client. 3. In the vSphere Client, log in to the vCenter Server and open vSphere Update Manager or vSphere Lifecycle Manager. 4. Create a baseline for the update using the Patch content type. a. On the Select Patches Automatically page, clear the Automatically update this baseline with patches that match the following criteria checkbox to prevent unqualified VIBs from being installed on the ESXi hosts. b. On the Select Patches Manually page, select the filter icon in the ID column to display the filter field. c. In the filter field, type the ESXi upgrade package name (without the .zip extension) listed in the PowerStore Release Notes, and select the ESXi package to add it to the baseline. 5. Stage the baseline to all the internal ESXi hosts in the PowerStore cluster. 6. Before placing the ESXi host on one node of an appliance into maintenance mode, ensure that system resources are available on the other ESXI host to run the migrated user VMs. If the CPU and memory utilization on each ESXi host is greater than 75%, migrate the VMs to another ESXi host in vCenter Server using vMotion or power off the user VMs. 7. Place the ESXi host on the peer node of the primary appliance into maintenance mode. 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 on page 10 for more information. CAUTION: Do not manually power off the controller VMs, which are named PSTX-. 8. On the Updates tab, select the baseline that is attached to the ESXi host on the peer node of the primary appliance and select Remediate to update the ESXi host. The ESXi update takes approximately 30 minutes to one hour to complete per node. The amount of time that an ESXi update takes depends on whether preupgrade and node firmware packages are applied when the ESXi host reboots. 9. Ensure that the remediation process has completed for the ESXi host on the peer node, then exit maintenance mode. The controller VM automatically starts when the ESXi host exits maintenance mode. 10. 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. 11. Repeat steps 7 through 10 for the ESXi host on the primary node of the appliance. NOTE: PowerStore Manager temporally stops displaying performance metrics when the primary node of the primary appliance reboots during the ESXi update. 12. Migrate VMs back to the preferred node using vMotion. 13. Repeat steps 6 to 12 to perform ESXI updates on the nodes of the other appliances in the 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 page 15. 14 PowerStore X model clusters

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
Steps
1.
Identify the primary and peer nodes on the primary appliance of the cluster. See
Minimizing internal ESXi host failover
occurrences
on page 11 for more information.
2.
Select
Compute
>
vCenter Server Connection
and select
Launch vSphere
to start the vSphere Client.
3.
In the vSphere Client, log in to the vCenter Server and open vSphere Update Manager or vSphere Lifecycle Manager.
4.
Create a baseline for the update using the Patch content type.
a.
On the
Select Patches Automatically
page, clear the
Automatically update this baseline with patches that match
the following criteria
checkbox to prevent unqualified VIBs from being installed on the ESXi hosts.
b.
On the
Select Patches Manually
page, select the filter icon in the ID column to display the filter field.
c.
In the filter field, type the ESXi upgrade package name (without the .zip extension) listed in the
PowerStore Release
Notes
, and select the ESXi package to add it to the baseline.
5.
Stage the baseline to all the internal ESXi hosts in the PowerStore cluster.
6.
Before placing the ESXi host on one node of an appliance into maintenance mode, ensure that system resources are available
on the other ESXI host to run the migrated user VMs. If the CPU and memory utilization on each ESXi host is greater than
75%, migrate the VMs to another ESXi host in vCenter Server using vMotion or power off the user VMs.
7.
Place the ESXi host on the peer node of the primary appliance into maintenance mode.
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
on page 10 for more information.
CAUTION:
Do not manually power off the controller VMs, which are named
PSTX-
<service_tag>
-
<node_letter>
.
8.
On the
Updates
tab, select the baseline that is attached to the ESXi host on the peer node of the primary appliance and
select
Remediate
to update the ESXi host.
The ESXi update takes approximately 30 minutes to one hour to complete per node. The amount of time that an ESXi update
takes depends on whether preupgrade and node firmware packages are applied when the ESXi host reboots.
9.
Ensure that the remediation process has completed for the ESXi host on the peer node, then exit maintenance mode.
The controller VM automatically starts when the ESXi host exits maintenance mode.
10.
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.
11.
Repeat steps 7 through 10 for the ESXi host on the primary node of the appliance.
NOTE:
PowerStore Manager temporally stops displaying performance metrics when the primary node of the primary
appliance reboots during the ESXi update.
12.
Migrate VMs back to the preferred node using vMotion.
13.
Repeat steps 6 to 12 to perform ESXI updates on the nodes of the other appliances in the 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 page 15.
14
PowerStore X model clusters