Professional Documents
Culture Documents
April 2022
Rev. A08
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2020- 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.
Contents
Additional Resources.....................................................................................................................4
Contents 3
Preface
As part of an improvement effort, revisions of the software and hardware are periodically released. Some functions that are
described in this document are not supported by all versions of the software or hardware currently in use. The product release
notes provide the most up-to-date information about product features. Contact your service provider if a product does not
function properly or does not function as described in this document.
4 Additional Resources
1
PowerStore non-disruptive software
upgrades
This document describes how to upgrade the software on your PowerStore cluster.
Performing a non-disruptive upgrade (NDU) on a PowerStore cluster does not stop I/O. The I/O requirements of the
PowerStore cluster can be met by a single node on each appliance in the cluster. The NDU process ensures that only one
node of the cluster is taken offline at any given time. Taking a node offline does not cause host I/O disruptions when the hosts
have redundant data access paths present and the best practices are configured for the host operating system.
NOTE: For host connectivity best practices, see the PowerStore Host Configuration Guide and Host Connectivity Guides in
section 7. Host Connectivity/Configuration Documentation on https://www.dell.com/powerstoredocs.
PowerStore NDU is supported with Solaris native MPxIO starting at Solaris 11.4 SRU 35. Contact your service provider for
PowerStore NDU support on earlier Solaris versions or Solaris updates.
NOTE: During the NDU, you cannot perform configuration changes or management operations on the PowerStore cluster.
Similarly, when the PowerStore OS is upgraded and the PowerStore VASA provider is offline, the I/O and availability of the
vVol-based VMs served from the PowerStore cluster are not impacted. However, management operations such as creating
VMs, rebooting VMs, migrating VMs to other ESXi hosts, and taking VM snapshots cannot be performed on vVol-based VMs
while the VASA provider is offline.
When the PowerStore OS upgrade is complete, wait five to ten minutes for the status of the PowerStore VASA provider to
change to Online in vCenter Server before creating storage containers or performing management operations on vVol-based
VMs.
NOTE: Within this document, PowerStore software is the software upgrade package for a PowerStore system and
PowerStore OS is the operating system that runs on the nodes of a PowerStore cluster.
Topics:
• Download the PowerStore upgrade packages
Prerequisites
Download the latest PowerStore Release Notes from the Dell Support Site to identify the upgrade packages to download for the
PowerStore cluster.
Steps
1. To access the Dell Support Site, open a browser and go to https://www.dell.com/support.
2. If you are not logged into the Dell Support Site, click Sign In and log in using an account that is associated with the
PowerStore cluster.
3. Type PowerStore in the Search support text box and select the model number of the PowerStore cluster from the list
that is displayed.
4. Click Drivers & Downloads on the PowerStore support page.
5. To sort the downloads from newest to oldest, select Released: Newest from the Sort by drop-down menu.
6. Identify the PowerStore upgrade package to download and click Download.
Steps
1. Download the latest PowerStore T model upgrade package as described in the Installation and Upgrade Considerations
section of the PowerStore Release Notes.
For instructions on downloading upgrade packages from the Dell Support Site, see Download the PowerStore upgrade
packages on page 5.
2. Review the upgrade considerations in Upgrade readiness for PowerStore T model clusters on page 7.
3. Upload the software upgrade package to PowerStore Manager.
a. In PowerStore Manager, select the Settings icon, and then select Upgrades in the Cluster section.
b. Select Upload Package.
c. Select the PowerStore T model upgrade package to upload and select Open.
NOTE: Do not close or refresh the browser while the software upgrade package is uploaded to PowerStore
Manager.
When the PowerStore T model software upgrade package finishes uploading, it is displayed in the Software packages
table.
4. Perform a Pre-Upgrade Health Check on the PowerStore T model cluster at least seven days before performing the upgrade.
For instructions, see Perform a Pre-Upgrade Health Check on the PowerStore T model cluster on page 7.
NOTE: If you are upgrading from PowerStore OS 2.1.x to a later version of the PowerStore OS, ensure the Upgrade
Extensions Health Check has been run within one hour of performing the upgrade. For instructions, see Perform an
Upgrade Extensions System Check on a PowerStore T model cluster (Upgrades from PowerStore OS 2.1.x only) on page
8.
5. Perform the steps in Upgrade the software on the PowerStore T model cluster on page 9.
The PowerStore T model software upgrade takes approximately one hour to one and a half hours to complete per appliance.
Results
If the software upgrade process fails, check for and resolve all critical alerts on the cluster and retry the upgrade.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. If the PowerStore T model software upgrade package has not been uploaded to PowerStore Manager:
a. Select Upload Package.
The Choose File to Upload dialog box is displayed.
b. Select the PowerStore T model software upgrade package, and select Open.
The PowerStore T model software upgrade package is uploaded and displayed in the Software packages table.
Results
CAUTION: A green check mark does not indicate that the Pre-Upgrade Health Check completed without any
error or warning messages. A green check mark only indicates that a health check step completed successfully.
For more information, see KB article 000130130 (Health Check shows all green when there are warnings).
Prerequisites
CAUTION: Follow these instructions only when upgrading from PowerStore OS 2.1.x to a later version of the
PowerStore OS.
The Upgrade button on the Settings > Cluster > Upgrades page is disabled unless an Upgrade Extensions System Check has
been run within the past 60 minutes.
Steps
1. Perform the following steps if a new Health Check package is available on the Dell Support Site:
a. Log in to the Dell Support Site and download the new Health Check package.
For instructions on downloading packages, see Download the PowerStore upgrade packages on page 5.
b. In PowerStore Manager, select Settings and then select Upgrades in the Cluster section.
c. Select Upload Package.
d. Select the new Health Check package and click Open.
NOTE: Do not close or refresh the browser while the Health Check package is uploaded to PowerStore Manager.
e. Select the uploaded Health Check package on the Upgrades page and select Upgrade to install the Health Check
updates.
2. Run the Upgrade Extensions System Check on the PowerStore cluster.
a. Under Monitoring, select System Checks.
b. Select Run Upgrade Extensions.
Next steps
Ensure that a successful Upgrade Extensions System Check is the last health check that is run on the PowerStore cluster
before starting the software upgrade.
Prerequisites
Ensure that a Pre-Upgrade Health Check has been performed at least seven days before upgrading the PowerStore OS on the
PowerStore T model cluster. For instructions, see Perform a Pre-Upgrade Health Check on the PowerStore T model cluster on
page 7.
NOTE: If you are upgrading from PowerStore OS 2.1.x to a later version of the PowerStore OS, ensure the Upgrade
Extensions Health Check has been run within one hour of performing the upgrade. For instructions, see Perform an Upgrade
Extensions System Check on a PowerStore T model cluster (Upgrades from PowerStore OS 2.1.x only) on page 8.
Steps
1. Open PowerStore Manager.
2. Select the Settings icon, and then select Upgrades in the Cluster section.
3. If the PowerStore T model software upgrade package has not been uploaded to PowerStore Manager:
a. Select Upload Package.
The Choose File to Upload dialog box is displayed.
b. Select the PowerStore T model software upgrade package, and select Open.
The PowerStore T model software upgrade package is uploaded to PowerStore Manager and displayed in the Software
packages table.
NOTE: Do not close or refresh the browser while the software upgrade package is uploaded to PowerStore
Manager.
4. Select the PowerStore T model software upgrade package in the Software packages table, and select Upgrade.
The PowerStore T model software upgrade takes approximately one hour to one and a half hours to complete per appliance.
The amount of time that the software upgrade depends on whether node firmware upgrades are applied during the upgrade.
NOTE: The PowerStore T model cluster temporarily stops recording performance metrics when the primary node of the
primary appliance reboots during the software upgrade.
Results
During the software upgrade process, the primary node of the primary appliance fails over to the secondary node of the
appliance and you are disconnected from PowerStore Manager. You can log back in to PowerStore Manager after the failover
process is complete.
When a new version of the PowerStore OS is installed, the column layout settings in PowerStore Manager tables reset to
their default layout. Changes to the column layout settings in PowerStore Manager do not persist when the PowerStore OS is
upgraded.
Prerequisites
CAUTION: Use these instructions only when upgrading from PowerStore OS 1.0.x to 2.0.x. For instructions on
upgrading from PowerStore OS 2.0.x to 2.1.x, see Upgrading PowerStore X model clusters (PowerStore OS
2.0.x to 2.1.x) on page 18.
Steps
1. Download the latest PowerStore X model upgrade package .zip file as described in the Installation and Upgrade
Considerations section of the PowerStore Release Notes.
For instructions on downloading upgrade packages from the Dell Support Site, see Download the PowerStore upgrade
packages on page 5.
2. Extract the individual upgrade packages from the PowerStore X model upgrade package .zip file.
3. Review the upgrade considerations in Upgrade readiness for PowerStore X model clusters (PowerStore OS 1.0.x to 2.0.x) on
page 11.
4. Upload the software update packages to PowerStore Manager.
NOTE: Do not upload ESXi update package to PowerStore Manager.
a. In PowerStore Manager, select the Settings icon, and then select Upgrades in the Cluster section.
b. Select Upload Package.
c. Select the PowerStore X model software update package to upload and select Open.
NOTE: Do not close or refresh the browser while the software update package is uploaded to PowerStore Manager.
When the PowerStore X model software update package finishes uploading, it is displayed in the Software packages
table.
Results
If the PowerStore OS upgrade process fails, check for and resolve all critical alerts on the cluster and retry the upgrade.
Steps
1. In PowerStore Manager, select the Settings icon, and then select Properties in the Cluster section.
2. Record the name of the appliance in the Primary Appliance field.
This appliance is the primary appliance of the cluster.
3. Record the name of the primary node in the Primary Node on Appliance field.
The secondary node of the appliance is the opposite of the primary node.
NOTE: For example, if Node A is displayed in the Primary Node on Appliance field, the secondary node is Node B.
4. Identify the IP addresses of the internal ESXi hosts on the nodes of the primary appliance.
a. Select Settings > Network IPs in PowerStore Manager.
b. Record the Host Node IP address, Appliance name, and Node letter of the nodes on the primary appliance.
The Host Node IP addresses are the IP addresses of the internal ESXi hosts on the primary and secondary nodes of the
primary appliance.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. If the PowerStore OS software upgrade package has not been uploaded to PowerStore Manager:
a. Select Upload Package.
The Choose File to Upload dialog box is displayed.
b. Select the PowerStore OS software upgrade package, and select Open.
NOTE: Do not close or refresh the browser while the software upgrade package is uploaded to PowerStore
Manager.
The uploaded PowerStore OS upgrade package is displayed as a Software Release package in the Software packages
table.
3. When you are ready to perform the Pre-Upgrade Health Check, select the PowerStore OS software upgrade package in the
Software packages table, and select Health Check.
Monitor the health check process until it completes.
4. If the Pre-Upgrade Health Check fails:
a. Select the failed Pre-Upgrade Health Check entry under Recent activities to open the Job Details slide-out panel.
b. Select each row in the Job Details slide-out panel to review the failure or warning messages that were generated during
the Pre-Upgrade Health Check.
If you need help with understanding a message, contact your service provider for assistance.
c. Identify the cause of each failure or warning message and fix the issue that caused the problem.
NOTE: The Pre-Upgrade Health Check displays the following failures when it is run before the preupgrade and node
firmware update packages are installed and the internal ESXi hosts are updated:
These Pre-Upgrade Health Check failures are resolved when the steps in Install the preupgrade package on the cluster
(PowerStore OS 1.0.x to 2.0.x) on page 14, Install the node firmware update package on the cluster (PowerStore OS
1.0.x to 2.0.x) on page 14, and Update the internal ESXi hosts on the cluster (PowerStore OS 1.0.x to 2.0.x) on page
15 are performed.
Results
CAUTION: A green check mark does not indicate that a Pre-Upgrade Health Check completed without any error
or warning messages. A green check mark only indicates that a Pre-Upgrade Health Check step completed
successfully. For more information, see KB article 000130130 (Health Check shows all green when there are
warnings).
Prerequisites
● Ensure that the preupgrade package has been uploaded to PowerStore Manager.
● Ensure that a Pre-Upgrade Health Check has been performed at least seven days before installing the preupgrade
package on the PowerStore X model appliance. For instructions, see Perform a Pre-Upgrade Health Check on the cluster
(PowerStore OS 1.0.x to 2.0.x) on page 12.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. Select the preupgrade package in the Software packages table, and select Upgrade.
NOTE: The preupgrade package is displayed as a Hotfix package in the Software packages table.
Results
The preupgrade package is not applied to the PowerStore X model cluster until the nodes of the cluster are rebooted. However,
the nodes do not automatically reboot after a preupgrade package is installed. The nodes of the cluster are rebooted when ESXi
updates are installed on the internal ESXi hosts, as described in Update the internal ESXi hosts on the cluster (PowerStore OS
1.0.x to 2.0.x) on page 15. If ESXi updates are not installed, you must reboot the nodes of the cluster during the PowerStore
OS upgrade, as described in Upgrade the PowerStore OS on the cluster (PowerStore OS 1.0.x to 2.0.x) on page 17.
Next steps
If a PowerStore X model node firmware upgrade is available or required, go to Install the node firmware update package on the
cluster (PowerStore OS 1.0.x to 2.0.x) on page 14.
If a PowerStore X model node firmware upgrade is not available, go to Update the internal ESXi hosts on the cluster
(PowerStore OS 1.0.x to 2.0.x) on page 15.
Prerequisites
● Ensure that the node firmware update package has been uploaded to PowerStore Manager.
● Ensure that a Pre-Upgrade Health Check has been performed at least seven days before installing the node firmware
package on the PowerStore X model cluster. For instructions, see Perform a Pre-Upgrade Health Check on the cluster
(PowerStore OS 1.0.x to 2.0.x) on page 12.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. Select the node firmware update package in the Software packages table, and select Upgrade.
The installation of the node firmware update package takes approximately 10 to 15 minutes to complete.
Results
The node firmware updates are not applied to the PowerStore X model cluster until the nodes of the cluster are rebooted.
However, the nodes do not automatically reboot after a firmware update package is installed. The nodes of the cluster are
rebooted when ESXi updates are installed on the internal ESXi hosts, as described in Update the internal ESXi hosts on the
cluster (PowerStore OS 1.0.x to 2.0.x) on page 15. If ESXi updates are not installed, you must reboot the ESXi hosts on
the nodes of the cluster during the PowerStore OS upgrade, as described in Upgrade the PowerStore OS on the cluster
(PowerStore OS 1.0.x to 2.0.x) on page 17.
Next steps
If ESXi updates are available or required, go to Update the internal ESXi hosts on the cluster (PowerStore OS 1.0.x to 2.0.x) on
page 15.
If ESXi updates are not available, go to Upgrade the PowerStore OS on the cluster (PowerStore OS 1.0.x to 2.0.x) on page 17.
Prerequisites
Ensure that the ESXi update package has been imported into vSphere Update Manager or vSphere Lifecycle Manager. For
instructions, see Upgrading PowerStore X model clusters (PowerStore OS 1.0.x to 2.0.x) on page 10.
CAUTION: The internal nodes of a PowerStore X model cluster can only use ESXi updates that are qualified by
Dell EMC. Do not use ESXi updates that are obtained from VMware or any other source.
Steps
1. Identify the primary appliance and identify the IP addresses of the internal ESXi hosts on the primary and secondary nodes
of the appliance. For instructions, see Minimizing internal ESXi host failover occurrences (PowerStore OS 1.0.x to 2.0.x) on
page 12.
NOTE: The terms peer node and secondary node are used interchangeably in PowerStore documentation.
2. If there are multiple appliances in the cluster, perform the following steps to collect information about the other appliances:
a. Select Settings > Network IPs in PowerStore Manager.
b. Record the Host Node IP address, Appliance name, and Node letter of each node in the cluster.
c. For the other appliances in the cluster, select the Hardware > Appliances > appliance > Components card in
PowerStore Manager.
d. Select the Internal View tab.
The text (primary) is displayed next to the primary node of the selected appliance, and the secondary node is opposite
of the primary node. For example, if the text (primary) is displayed for Node A, the secondary node is Node B.
e. Use the collected information to identify the IP addresses of the internal ESXi hosts on the primary and secondary nodes
of the other appliances in the cluster.
3. In PowerStore Manager, select Compute > vCenter Server Connection and select Launch vSphere to start the vSphere
Client.
4. In the vSphere Client, log in to the vCenter Server and open vSphere Update Manager or vSphere Lifecycle Manager.
5. Create a baseline for the update using the Patch content type.
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.
9. On the Updates tab, select the baseline that is attached to the ESXi host on the secondary 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.
10. Ensure that the remediation process has completed for the ESXi host on the secondary node, and then exit maintenance
mode.
The controller VM automatically starts when the ESXi host exits maintenance mode.
11. 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.
12. 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.
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 1.0.x to 2.0.x) on page 17.
Prerequisites
Perform a final Pre-Upgrade Health Check before upgrading the PowerStore OS on the PowerStore X model cluster. For
instructions, see Perform a Pre-Upgrade Health Check on the cluster (PowerStore OS 1.0.x to 2.0.x) on page 12.
Steps
1. If you installed a preupgrade package or upgraded the node firmware, but you were not required to perform ESXi host
updates, you must reboot the internal nodes on the cluster to apply the preupgrade package and firmware upgrades.
Rebooting the nodes to apply the preupgrade package and firmware upgrade package takes approximately 35 to 60 minutes
per node. To reboot the nodes of the cluster:
a. Identify the primary and secondary nodes on the primary appliance of the cluster. See Minimizing internal ESXi host
failover occurrences (PowerStore OS 1.0.x to 2.0.x) on page 12 for more information.
b. In the vSphere Client, reboot the ESXi host on the secondary node. For instructions, see the PowerStore Power Down
and Reboot Procedures Guide.
c. If the ESXi host on the secondary node does not automatically exit maintenance mode after rebooting, manually exit
maintenance mode on the secondary node.
d. Repeat the previous steps for the ESXi host on the primary node.
e. Repeat the previous steps on the other appliances in the cluster.
2. Select the Settings icon, and then select Upgrades in the Cluster section.
3. Select the PowerStore OS upgrade package in the Software packages table, and select Upgrade.
NOTE: The PowerStore OS upgrade package is displayed as a Software Release package in the Software packages
table.
The PowerStore OS upgrade takes approximately one hour to complete.
Results
The PowerStore X model cluster temporarily stops recording performance metrics when the primary node on the primary
appliance reboots during the ESXi update. When the primary node on the primary appliance reboots, the primary node fails over
to the secondary node and you are disconnected from PowerStore Manager. You can log back in to PowerStore Manager after
the failover process is complete.
Next steps
Use the vSphere Client to manually rebalance the VMs in vCenter or allow VMware Distributed Resource Scheduler (DRS) to
automatically rebalance the VMs .
When a new version of the PowerStore OS is installed, the column layout settings in PowerStore Manager tables reset to
their default layout. Changes to the column layout settings in PowerStore Manager do not persist when the PowerStore OS is
upgraded.
Prerequisites
CAUTION: Use these instructions only when upgrading from PowerStore OS 2.0.x to 2.1.x. For instructions on
upgrading from PowerStore OS 1.0.x to 2.0.x, see Upgrading PowerStore X model clusters (PowerStore OS 1.0.x
to 2.0.x) on page 10
Steps
1. Download the latest PowerStore X model upgrade package .zip file as described in the Installation and Upgrade
Considerations section of the PowerStore Release Notes.
For instructions on downloading upgrade packages from the Dell Support Site, see Download the PowerStore upgrade
packages on page 5.
2. Extract the PowerStore X model preupgrade package and PowerStore OS upgrade package from the PowerStore X model
upgrade package .zip file.
3. Review the upgrade considerations in Upgrade readiness for PowerStore X model clusters (PowerStore OS 2.0.x to 2.1.x) on
page 19.
4. Upload the PowerStore X model preupgrade package and PowerStore OS upgrade package to the cluster.
a. In PowerStore Manager, select the Settings icon, and then select Upgrades in the Cluster section.
b. Select Upload Package.
c. Select the preupgrade package and select Open.
NOTE: Do not close or refresh the browser while the preupgrade package is uploaded to PowerStore Manager.
The uploaded preupgrade package is displayed as a Hotfix package in the Software packages table.
d. Repeat the previous two steps to upload the PowerStore OS upgrade package to the cluster.
The uploaded PowerStore OS upgrade package is displayed as a Software Release package in the Software packages
table.
5. Perform a Health Check on the PowerStore X model cluster at least seven days before performing the upgrade.
For instructions, see Perform a Pre-Upgrade Health Check on the cluster (PowerStore OS 2.0.x to 2.1.x) on page 20.
NOTE: If you are upgrading from PowerStore OS 2.1.x to a later version of the PowerStore OS, ensure that the Upgrade
Extensions Health Check has been run within one hour of performing the upgrade. For instructions, see Perform an
Upgrade Extensions System Check on the cluster (Upgrades from PowerStore OS 2.1.x only) on page 21.
6. Perform the PowerStore X model appliance upgrade steps in the following order:
If you have already performed one of upgrade steps that are listed below, you can skip that step.
a. Install preupgrade package - Installing the preupgrade package takes approximately twenty minutes to complete.
b. Update internal ESXi hosts - Resizing the private VMFS datastores can take over one hour to complete. Updating the
node firmware and internal ESXi hosts takes approximately 30 minutes to complete per node.
c. Upgrade the PowerStore OS - Upgrading the PowerStore OS takes approximately one hour to complete.
Steps
1. In PowerStore Manager, select the Settings icon, and then select Properties in the Cluster section.
2. Record the name of the appliance in the Primary Appliance field.
This appliance is the primary appliance of the cluster.
3. Record the name of the primary node in the Primary Node on Appliance field.
The secondary node of the appliance is the opposite of the primary node.
NOTE: For example, if Node A is displayed in the Primary Node on Appliance field, the secondary node is Node B.
4. Identify the IP addresses of the management appliance and the IP addresses of the internal ESXi hosts on the nodes of the
primary appliance.
a. Select Settings > Network IPs in PowerStore Manager.
b. Record the Management Appliance IP address of the primary appliance in the cluster.
c. Record the Host Node IP address, Appliance name, and Node letter of the nodes on the primary appliance.
The Host Node IP addresses are the IP addresses of the internal ESXi hosts on the primary and secondary nodes of the
primary appliance.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. If the PowerStore OS upgrade package has not been uploaded to PowerStore Manager:
a. Select Upload Package.
The Choose File to Upload dialog box is displayed.
b. Select the PowerStore OS upgrade package, and select Open.
NOTE: Do not close or refresh the browser while the upgrade package is uploaded to PowerStore Manager.
The uploaded PowerStore OS upgrade package is displayed as a Software Release package in the Software packages
table.
3. When you are ready to perform the Pre-Upgrade Health Check, select the PowerStore OS upgrade package in the Software
packages table, and select Health Check.
Monitor the health check process until it completes.
4. If the Pre-Upgrade Health Check fails:
a. Select the failed Pre-Upgrade Health Check entry under Recent activities to open the Job Details slide-out panel.
b. Select each row in the Job Details slide-out panel to review the failure or warning messages that were generated during
the Pre-Upgrade Health Check.
These Pre-Upgrade Health Check failures are resolved when the steps in Install the preupgrade package on the cluster
(PowerStore OS 2.0.x to 2.1.x) on page 22 and Update the internal ESXi hosts and node firmware (PowerStore OS
2.0.x to 2.1.x) on page 23 are performed.
Results
CAUTION: A green check mark does not indicate that a Pre-Upgrade Health Check completed without any error
or warning messages. A green check mark only indicates that a Pre-Upgrade Health Check step completed
successfully. For more information, see KB article 000130130 (Health Check shows all green when there are
warnings).
Prerequisites
CAUTION: Follow these instructions only when upgrading from PowerStore OS 2.1.x to a later version of the
PowerStore OS.
The Upgrade button on the Settings > Cluster > Upgrades page is disabled unless an Upgrade Extensions System Check has
been run within the past 60 minutes.
Steps
1. Perform the following steps if a new Health Check package is available on the Dell Support Site:
a. Log in to the Dell Support Site and download the new Health Check package.
For instructions on downloading packages, see Download the PowerStore upgrade packages on page 5.
b. In PowerStore Manager, select Settings and then select Upgrades in the Cluster section.
c. Select Upload Package.
e. Select the uploaded Health Check package on the Upgrades page and select Upgrade to install the Health Check
updates.
2. Run the Upgrade Extensions System Check on the PowerStore cluster.
a. Under Monitoring, select System Checks.
b. Select Run Upgrade Extensions.
The System Check detects if there are issues on the PowerStore cluster that might prevent the upgrade from
completing successfully. If the System Check finds issues on the cluster, resolve those issues before performing the
PowerStore software upgrade.
c. Run the Upgrade Extensions System Check again to ensure that all issues have been resolved.
Next steps
Ensure that a successful Upgrade Extensions System Check is the last health check that is run on the PowerStore cluster
before starting the software upgrade.
Prerequisites
Ensure that a Pre-Upgrade Health Check has been performed at least seven days before installing the preupgrade package on
the PowerStore cluster. For instructions, see Perform a Pre-Upgrade Health Check on the cluster (PowerStore OS 2.0.x to
2.1.x) on page 20.
NOTE: If you are upgrading from PowerStore OS 2.1.x to a later version of the PowerStore OS, ensure that the Upgrade
Extensions Health Check has been run within one hour of performing the upgrade. For instructions, see Perform an Upgrade
Extensions System Check on the cluster (Upgrades from PowerStore OS 2.1.x only) on page 21.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. Select the preupgrade package in the Software packages table, and select Upgrade.
NOTE: The preupgrade package is displayed as a Hotfix package in the Software packages table.
Results
Installing the preupgrade package stages the following files on the PowerStore X model cluster:
● Node firmware update
● Dell EMC custom VMware .VIB files
● Dell EMC ESXi 7.0 update
● Service script for resizing the ESXi VMFS datastore (svc_esxi_helper)
Installing the preupgrade package also causes the Pre-Upgrade Health Check to run, which checks for the following issues:
● If the local VMFS datastores on the ESXi hosts contain VMs other than the PowerStore controller VM, the following failure
is displayed:
This upgrade requires that no VMs are present in the ESXi host local datastore other than
the PowerStore VM. Please migrate the VMs located in the ESXi host's local datastore to
another Storage Container prior to upgrade. (esx_check_local_vms_static)
Next steps
Go to Update the internal ESXi hosts and node firmware (PowerStore OS 2.0.x to 2.1.x) on page 23.
Steps
1. Identify the primary appliance and identify the IP addresses of the internal ESXi hosts on the primary and secondary nodes
of the appliance. For instructions, see Minimizing internal ESXi host failover occurrences (PowerStore OS 2.0.x to 2.1.x) on
page 19.
NOTE: The terms peer node and secondary node are used interchangeably in PowerStore documentation.
2. If there are multiple appliances in the cluster, perform the following steps to collect information about the other appliances:
a. Select Settings > Network IPs in PowerStore Manager.
b. Record the Management Appliance IP address for each appliance in the cluster.
c. Record the Host Node IP address, Appliance name, and Node letter of each node in the cluster.
d. For the other appliances in the cluster, select the Hardware > Appliances > appliance > Components card in
PowerStore Manager.
e. Select the Internal View tab.
The text (primary) is displayed next to the primary node of the selected appliance, and the secondary node is opposite
of the primary node. For example, if the text (primary) is displayed for Node A, the secondary node is Node B.
f. Use the collected information to identify the IP addresses of the ESXi hosts on the primary and secondary nodes of the
other appliances in the cluster.
3. To upgrade a single-appliance cluster, perform the following steps starting with the ESXi host on the secondary node of
primary appliance.
To upgrade a multi-appliance cluster, perform the following steps starting with the ESXi hosts on the secondary appliances
first and the primary appliance last.
4. Resize the VMFS datastore of the internal ESXi host on the secondary node of an appliance in the cluster.
a. Log in to the vCenter Server using the vSphere Client.
To start the vSphere Client from PowerStore Manager, select Compute > vCenter Server Connection and select
Launch vSphere.
b. Ensure that the ESXi host on the other node of the appliance has enough system resources to run the user VMs that are
migrated to it when the ESXi host on the secondary node is placed into maintenance mode.
NOTE: If the CPU and memory utilization on the ESXi host is greater than 75%, migrate the VMs to another ESXi
host in the vCenter Server using vMotion or power off the user VMs before continuing.
c. Place the ESXi host on the secondary node of the appliance into maintenance mode.
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.
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 PowerStore 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.
5. Reboot the ESXi host on the secondary node of an appliance to update the ESXi host and node firmware.
a. In the vSphere Client, reboot the ESXi host that is in maintenance mode.
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:
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.
6. Repeat steps 4 and 5 to resize the VMFS datastore and update the ESXi host and node firmware 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 an ESXi update.
7. Migrate the VMs back to the preferred node in the cluster using vMotion.
8. For a multi-appliance cluster, repeat steps 4 through 7 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.
● 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 to 2.1.x) on page 25.
Prerequisites
Perform a final Pre-Upgrade Health Check before upgrading the PowerStore OS on the PowerStore X model cluster. For
instructions, see Perform a Pre-Upgrade Health Check on the cluster (PowerStore OS 2.0.x to 2.1.x) on page 20.
NOTE: If you are upgrading from PowerStore OS 2.1.x to a later version of the PowerStore OS, ensure that the Upgrade
Extensions Health Check has been run within one hour of performing the upgrade. For instructions, see Perform an Upgrade
Extensions System Check on the cluster (Upgrades from PowerStore OS 2.1.x only) on page 21.
Steps
1. Select the Settings icon, and then select Upgrades in the Cluster section.
2. Select the PowerStore OS upgrade package in the Software packages table, and select Upgrade.
NOTE: The PowerStore OS upgrade package is displayed as a Software Release package in the Software packages
table.
The PowerStore OS upgrade takes approximately one hour to complete.
Results
The PowerStore X model cluster temporarily stops recording performance metrics when the primary node on the primary
appliance reboots during the ESXi update. When the primary node on the primary appliance reboots, the primary node fails over
to the secondary node and you are disconnected from PowerStore Manager. You can log back in to PowerStore Manager after
the failover process is complete.
Next steps
Use the vSphere Client to manually rebalance the VMs in vCenter or allow VMware Distributed Resource Scheduler (DRS) to
automatically rebalance the VMs .
When a new version of the PowerStore OS is installed, the column layout settings in PowerStore Manager tables reset to
their default layout. Changes to the column layout settings in PowerStore Manager do not persist when the PowerStore OS is
upgraded.
Steps
1. Download the latest drive firmware update package from the Dell Support Site.
The drive firmware update package contains firmware updates for the drives in the PowerStore cluster. For instructions on
downloading PowerStore upgrade packages, see Download the PowerStore upgrade packages on page 5.
2. Select the Settings icon, and then select Upgrades in the Cluster section.
3. Select Upload Package.
The Choose File to Upload dialog box is displayed.
4. Select the drive firmware update package, and select Open.
The drive firmware update package is uploaded and displayed in the Software packages table.
NOTE: Do not close or refresh the browser while the drive firmware update package is uploaded to PowerStore
Manager.
5. Select the drive firmware update package in the Software packages table, and select Upgrade.
Results
● To verify the drive firmware version for individual drives in a PowerStore cluster, go to the Hardware > Appliances >
appliance > Components > Drives page in PowerStore Manager.
● To verify the drive firmware version for all the drives in a PowerStore cluster, run the service command svc_diag list
--show_drives. For more information, see the PowerStore Service Scripts Guide.