VxRail ™ SolVe Generator

Solution for Validating your engagement

Topic
VxRail Software Upgrade Procedures
Selections
Select the VxRail Appliance Model: VxRail E460/E460F
Select the Installed VxRail Software Version: v4.7.000
Select the Target VxRail Software Version: v7.0.200
Select your current VxRail Configuration: VxRail Cluster - non-vSAN Stretched Cluster
Is VMware Horizon VDI Installed?: No

Generated: May 16, 2021 1:56 PM GMT

REPORT PROBLEMS

If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@emc.com
Copyright © 2020 Dell Inc. or its subsidiaries. All Rights Reserved.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION (“EMC”)
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT AND ANY WARRANTY ARISING BY STATUTE, OPERATION OF LAW, COURSE OF
DEALING OR PERFORMANCE OR USAGE OF TRADE. IN NO EVENT SHALL EMC BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF EMC HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice. Use, copying, and distribution of any EMC software described in this
publication requires an applicable software license.

Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.

Publication Date: May, 2021

Dell Technologies Confidential Information version: 4.2.3.3

Page 1 of 28
 Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3

Data-in-Place upgrade solution from v4.5.4xx and v4.7.000/001 to v7.0.200.........................4

Summary:......................................................................................................................................................4
Materials Required:.......................................................................................................................................4
Preparation: ..................................................................................................................................................5
VxRail Cluster Upgrade ................................................................................................................................6
Task 1: Use Converged PSC for VxRail 7.0 (Applicable for External PSC on release v4.5.400
only) 6
Task 2: Disk Space Expansion (Applicable for release v4.5.400 and 4.7.00x only) .....................7
Task 3: [Optional] Configure alarm definition for Email notification.............................................10
Task 4: Take a snapshot of all the service Virtual Machines ......................................................10
Task 5: Upgrade from v4.5.4xx and v4.7.000/001 to v7.0.200 ...................................................12
Task 6: Remove snapshots of the service Virtual Machines.......................................................22
Task 7: Mystic Service account password change (Optional).....................................................24
Appendix A: Get the Correct Controller Key Value...........................................................26
Troubleshooting ....................................................................................................................28

Dell Technologies Confidential Information version: 4.2.3.3

Page 2 of 28
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.

Read, understand, and perform these tasks

1. Table 1 lists tasks, cautions, warnings, notes, and/or knowledgebase (KB) solutions that you need to
be aware of before performing this activity. Read, understand, and when necessary perform any
tasks contained in this table and any tasks contained in any associated knowledgebase solution.

Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity

491674: VxRail: Avoid any management operations during upgrade"

528322: VxRail: How to upgrade Log Insight

539930: VxRail: LCM failed to expand /data/store2 partition on VxRail manager

536801: VxRail: How to run VxVerify

543609: VxRail: VxRail 4.7.470 plugin shown after installing or upgrading to VxRail 7.0.000

543028: VxRail: Need to update VxRail Manager configuration after converging external vCenter and
PSC using script

2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.

Note: There may not be any top trending service topics for this product at any given time.

VxRail Appliance Top Service Topics

Dell Technologies Confidential Information version: 4.2.3.3

Page 3 of 28
IMPORTANT: Please confirm whether a customer is using RecoverPoint for Virtual Machines (RP4VM)
in the VxRail cluster, prior to upgrading VxRail. RP4VM must be upgraded prior to upgrading VxRail to
prevent a DRU/DU issue on the VxRail cluster!

Note: It is highly advisable to monitor node reboots through IDRAC/BMC interfaces to detect boot related
issues.

Data-in-Place upgrade solution from v4.5.4xx and v4.7.000/001 to

v7.0.200
Note: This upgrade procedure can be applied for customers in Greater China.

Summary:
This procedure describes the steps required to perform a data-in-place upgrade to v7.0.200 on a VxRail
Appliance running v4.5.400, v4.5.401, v4.5.402, v4.5.420, v4.5.422, v4.5.450, v4.5.451, v4.5.452,
v4.5.460, v4.7.000 or v4.7.001.

Note: vSphere 7.0 license keys are required for a cluster to run on vSphere 7.0. The LCM precheck will
not stop a user from upgrading without 7.0 license keys. Without them, the nodes will be running on 60-
day evaluation license keys. User needs to go my.vmware.com to determine whether their clusters need
7.0 license keys and acquire them there if applicable.
Note: VxRail appliances based on the Quanta hardware platform are not supported at VxRail v7.0.200.

Note: Users upgrading from VxRail v4.5.400 may need to perform manual steps after completing the
v7.0.200 upgrade to implement some of the security mitigations. For a description of these issues and a
link to the mitigation procedure, review the MCEPSC vulnerability described in the “Security fixes” section
of the release notes.
Note: If the VxRail Manager SSL certificate has been changed, please refer to the following EMC
Knowledgebase solution 530378 (How to prevent vCenter plugin issue caused by VxRail Manager SSL
certificate mismatch) before proceeding with the upgrade.

Materials Required:
Ensure the following passwords are available:
 VxRail Manager Root
 vCenter Administrator
 vCenter Root
 PSC Root
 ESXi Node Root
 iDRAC/BMC (aka Baseboard Management Controller (if configured)
Download the VxVerify tool from https://support.emc.com/kb/536801. VxVerify is designed specifically to
detect issues which could cause complications or failures during VxRail LCM upgrades.
A temporary IP address on the same subnet needed to upgrade vCenter Server (not required if using
external vCenter).

Dell Technologies Confidential Information version: 4.2.3.3

Page 4 of 28
  There is no need to load the file locally when performing an Internet connected upgrade. The upgrade
file will be auto downloaded from support.emc.com.
 If not internet connected, the upgrade file will file need to be downloaded from
https://support.emc.com/products/39970 and made locally available.
 File names (choose one):
o VXRAIL_COMPOSITE-7.0.200-xxx_for_4.5.x.zip (for 4.5.x only)
o VXRAIL_COMPOSITE-7.0.200-xxx_for_4.7.x.zip (for 4.7.x only)
For clusters with external vCenter only):
o VXRAIL_COMPOSITE-SLIM-7.0.200-xxx_for_4.5.x.zip (for 4.5.x only)
o VXRAIL_COMPOSITE-SLIM-7.0.200-xxx_for_4.7.x.zip (for 4.7.x only)

Preparation:
1. [ ] Execute the VxVerify tool. Follow the instructions available in KB536801.
2. [ ] Log into VxRail Manager.
3. [ ] Make sure the VxRail appliance is in a healthy state.

a. On the CONFIG page under the General tab, select the Diagnostic button under System
Diagnostics to verify the VxRail cluster health status. Address any issues found prior to starting
the upgrade process.
4. [ ] Confirm VxRail appliance is currently running v4.5.400, v4.5.401, v4.5.402, v4.5.420, v4.5.422,
v4.5.450, v4.5.451, v4.5.452, v4.5.460, v4.7.000 or v4.7.001.

a. On the CONFIG page, select the System tab.

Note: Screen shots may differ depending on the running VxRail version.

Figure 1

Note: If this VxRail Cluster is joining an External vCenter, please check the VxRail and External vCenter
Interoperability Matrix: https://www.dell.com/support/kbdoc/000520355. Work with the customer to ensure
that the External vCenter is running a supported version.

Dell Technologies Confidential Information version: 4.2.3.3

Page 5 of 28
Note: All customer-supplied vCenter configurations are required to upgrade to vCenter 7.0 U1 prior to
upgrading to VxRail 7.0.200. Prior to the vCenter upgrade, users are required to follow manual steps to
update a vCenter setting prior to upgrading the customer-supplied vCenter to 7.0 U1. Please reference
https://www.dell.com/support/kbdoc/000181307 for the detailed procedure. Set Cluster Health Monitoring
to Muted mode in the VxRail Manager GUI prior to upgrading external vCenter to avoid false alerts.
Note: If this VxRail Cluster is joining an External vCenter with an External PSC, after the External
vCenter is upgraded to v7.0, follow the “Use Converged PSC for VxRail 7.0” procedure below. Otherwise
VxRail Manager will prevent you from logging in.

VxRail Cluster Upgrade

Task 1: Use Converged PSC for VxRail 7.0 (Applicable for External PSC on release v4.5.400
only)
Note: VCSA v7.0 will not support an External PSC. After converting the External PSC into an Embedded
PSC, the old PSC record remains in VxRail Manager preventing users from logging into VxRail Manager.
The ext_vc_psc_convergence_post_action.py script must be run to resolve this issue.

1. [ ] Download the script ext_vc_psc_convergence_post_action.py from support.emc.com.

2. [ ] Use FileZilla to upload the ext_vc_psc_convergence_post_action.py to the VxRail Manager VM.
Open FileZilla and enter the following information:
Host: <enter_vxrail_manager_ip_address>
Username: mystic
Password: <please_get_password_from_customer>
Port: 22

Figure 2

3. [ ] Click Quickconnect to connect to the VxRail Manager VM. The VxRail Manager default directory
will be /home/mystic.
4. [ ] Upload the ext_vc_psc_convergence_post_action.py file to the /home/mystic directory. Once the
upload has completed, close FileZilla.
5. [ ] Using PuTTy or other SSH client, establish an SSH session to the VxRail Manager VM using the
following permissions:
Host Name (or IP address): <enter_vxrail_manager_ip_address>
Port: 22
Login: mystic
Password: <please_get_password_from_customer>
6. [ ] Switch to root user account.

Dell Technologies Confidential Information version: 4.2.3.3

Page 6 of 28
 su <enter>
Password: <please_get_password_from_customer>
7. [ ] Run the ls -l command to verify the file has been uploaded.

Figure 3

8. [ ] Run the script with the following command. The script will check the vCenter type first to make
sure the script is run under the embedded PSC vCenter.
python ext_vc_psc_convergence_post_action.py -u <vcenter_admin_usr> -p
<vcenter_admin_pwd>
For example:
python ext_vc_psc_convergence_post_action.py -u
administrator@vsphere.local -p Passw0rd!
9. [ ] Once the script has completed, close the SSH session.

Task 2: Disk Space Expansion (Applicable for release v4.5.400 and 4.7.00x only)
Note: For release v4.5.400 and 4.7.00x, there is not enough disk space in the VxRail Manager
/data/store2 to perform an upgrade to v7.0.200. The VXRAIL_COMPOSITE-7.0.200-xxx_for_4.5.x.zip
and VXRAIL_COMPOSITE-7.0.200-xxx_for_4.7.x.zip bundles are larger than the available space,
therefore the disk_space_expansion.py script must be run to add 64GB of additional space to
/data/store2.

1. [ ] Download the script disk_space_expansion.py from support.emc.com.

2. [ ] Use FileZilla to upload the disk_space_expansion.py to the VxRail Manager VM. Open FileZilla
and enter the following information:
Host: <enter_vxrail_manager_ip_address>
Username: mystic
Password: <please_get_password_from_customer>
Port: 22

Figure 4

3. [ ] Click Quickconnect to connect to the VxRail Manager VM. The VxRail Manager default directory
will be /home/mystic.

Dell Technologies Confidential Information version: 4.2.3.3

Page 7 of 28
 4. [ ] Upload the disk_space_expansion.py file to the /home/mystic directory. Once the upload has
completed, close FileZilla.
5. [ ] Using PuTTy or other SSH client, establish an SSH session to the VxRail Manager VM using the
following permissions:
Host Name (or IP address): <enter_vxrail_manager_ip_address>
Port: 22
Login: mystic
Password: <please_get_password_from_customer>
6. [ ] Switch to root user account.
su <enter>
Password: <please_get_password_from_customer>
7. [ ] Run the ls -l command to verify the file has been uploaded.

Figure 5

8. [ ] Run the df -Th command. Note in this example that the /data/store2 size is approximately 14G,
which is not large enough to accommodate the upgrade bundle.

Figure 6

9. [ ] Run the script with the following command. It will display the message “Config logic volume
succeeded” and “Running script succeeded” if the script executed successfully.
python disk_space_expansion.py -c <vcenter_ip> -u <vcenter_usr> -p
<vcenter_pwd> [-s] [-k <controller_key>]
For example:
python disk_space_expansion.py -c 10.xx.xx.xx -u
administrator@vsphere.local -p Passw0rd!

Dell Technologies Confidential Information version: 4.2.3.3

Page 8 of 28
 Figure 7

Note: The -s (skip taking snapshot) option is optional. If it is not provided, the script will take a snapshot
of the VxRail Manager VM automatically.

For example:
python disk_space_expansion.py -c 10.xx.xx.xx -u
administrator@vsphere.local -p Passw0rd! -s

Note: The -k (specify a controller key value) option is optional. If the disk expansion fails due to a
controller key error, use this option to provide a controller key value when adding disk space to the VM.

For example:
python disk_space_expansion.py -c 10.xx.xx.xx -u
administrator@vsphere.local -p Passw0rd! -k 1000

Note: Please follow Appendix A to obtain the correct controller key value if the script fails due to an
incorrect value.

Dell Technologies Confidential Information version: 4.2.3.3

Page 9 of 28
10. [ ] After the disk space expansion has completed, run the “df -Th” command to verify the
/data/store2 has been extended. It should be approximately 77G. Once the disk space expansion has
completed, close the SSH session.

Figure 8

Task 3: [Optional] Configure alarm definition for Email notification

If email notification is needed during LCM upgrade, please follow KB524924. Click
Email notification will be sent out with below stages
 When the cluster starts to do LCM upgrade, email notification about LCM upgrade starting will be sent
out.
 For each node
 When the node starts upgrade, email notification about node upgrade starting will be sent out.
 When the node completes upgrade, email notification about node upgrade completion will be sent
out.
 Any node upgrade failure, email notification about node upgrade failure will be sent out.
 When the cluster completes LCM upgrade, email notification about LCM upgrade completion will be
sent out.

Task 4: Take a snapshot of all the service Virtual Machines

 VxRail Manager VM
 VMware vCenter Server Appliance VM (if using embedded)
 VMware vCenter Server Platform Services Controller VM (if using embedded)
 VMware vRealize Log Insight VM (if using VxRail deployed syslog)
 ESRS VE VM (if call home is enabled and using VxRail Manager deployed ESRS)

1. [ ] Log into the vSphere Web Client.

2. [ ] Navigate to Hosts and Clusters.

Dell Technologies Confidential Information version: 4.2.3.3

Page 10 of 28
 Figure 9

3. [ ] Take a snapshot of a service VM. For example, right-click VxRail Manager > Snapshots > Take
Snapshot.

Figure 10

4. [ ] Enter a name and click OK.

Dell Technologies Confidential Information version: 4.2.3.3

Page 11 of 28
 Figure 11

5. [ ] Repeat steps 3 and 4 for each of the remaining service VM’s.

Task 5: Upgrade from v4.5.4xx and v4.7.000/001 to v7.0.200

1. [ ] If not already connected, log into VxRail Manager.
2. [ ] Go to CONFIG page > System tab.
3. [ ] If the cluster is not internet enabled, skip to step 7 to perform the Local Upgrade option.
4. [ ] If connected to the internet, the Internet Upgrade button can be selected to automatically get the
required file.

Figure 12

5. [ ] If the support account is not already set, you will be required to enter your Support username and
password then press Login you will then be prompted to select Internet Upgrade again.

Dell Technologies Confidential Information version: 4.2.3.3

Page 12 of 28
 Figure 13

6. [ ] The required file will begin to be downloaded. When completed, skip to step 10.

Figure 14

7. [ ] If the cluster is not internet enabled, Select the Local Upgrade option.

Note: Screen shots may differ depending on the running VxRail version.

Dell Technologies Confidential Information version: 4.2.3.3

Page 13 of 28
 Figure 15

8. [ ] In open file dialog, navigate to the upgrade composite package file previously downloaded and
saved locally and then click Open to select.

Note: Screen shot will differ if the VXRAIL_COMPOSITE-SLIM-7.0.200-xxx_for_4.5.x.zip file is being

used.

Figure 16 Screenshot for v4.5.x

Note: Screen shot will differ if the VXRAIL_COMPOSITE-SLIM-7.0.200-xxx_for_4.7.x.zip file is being

used.

Dell Technologies Confidential Information version: 4.2.3.3

Page 14 of 28
 Figure 17 Screenshot for v4.7.x

9. [ ] The download progress can be monitored on the screen.

Note: Screen shots may differ depending on the running VxRail version.

Figure 18

10. [ ] Click the Continue button to start the upgrade

Note: Screen shots may differ depending on the running VxRail version.

Figure 19

Dell Technologies Confidential Information version: 4.2.3.3

Page 15 of 28
11. [ ] Input the usernames, passwords and temporary IP as prompted. Input fields will differ depending
on whether you are using an external vCenter or internal vCenter. Click Submit to continue.

Figure 20

12. [ ] The upgrade progress can be monitored on the screen.

Note: Screen shots may differ depending on the running VxRail version.

Figure 21

Dell Technologies Confidential Information version: 4.2.3.3

Page 16 of 28
Note: VxRail upgrading page will be unreachable about 10 minutes after the warning dialog is shown.

Figure 22

13. [ ] Refresh the browser after VxRail Manager is recovered, LCM progress can be monitored
continuously.

Note: Screen shots may differ depending on the running VxRail version.

Figure 23

Dell Technologies Confidential Information version: 4.2.3.3

Page 17 of 28
14. [ ] After vCenter upgrade completed, you will be logout from vCenter automatically

Note: After re-login vCenter, enable the VxRail plugin by clicking on “Refresh Browser”

Figure 24

15. [ ] Log into vCenter using HTLM5 client with vCenter administrator account, then click VxRail
Cluster > Configure > VxRail > Updates.

Figure 25

16. [ ] The upgrade completes.

Dell Technologies Confidential Information version: 4.2.3.3

Page 18 of 28
 Figure 26

17. [ ] From the Home tab, select Hosts and Clusters and select the VxRail Cluster. Under the
Configure tab, expand the VxRail selection and choose Updates to verify the VxRail component
versions.

Figure 27

18. [ ] Make sure the VxRail appliance is in a healthy state.

a. Navigate to Home > Hosts and Clusters > VxRail-Cluster.

b. Select Monitor > Issues and Alarms > All Issues.

Dell Technologies Confidential Information version: 4.2.3.3

Page 19 of 28
 Figure 28

c. Verify the VxRail cluster is in health status.

19. [ ] If ESRS is enabled in your VxRail appliance, please check the ESRS status.

a. Navigate to Home > Host and Clusters > VxRail-Cluster.

b. Select Configure > VxRail > Support.

Figure 29

c. On the Support section, check last heartbeat is alive like the following figure.

Dell Technologies Confidential Information version: 4.2.3.3

Page 20 of 28
 Figure 30 Check Last heartbeat

d. Open in browser: https://<ESRS VE IP>:9443. Login with admin username and password.
e. Check ESRS VE connectivity status is connected.

Figure 31

f. If not connected, please follow the below steps to correct the status.
a. Navigate to Home > Hosts and Clusters > VxRail-Cluster
b. Select Configure > VxRail > Support.
c. On the ESRS section, click DELETE… button.

Dell Technologies Confidential Information version: 4.2.3.3

Page 21 of 28
 Figure 32 Delete ESRS again

a. After delete is successful, click EDIT… button to add it again.

Figure 33 Enable ESRS again

Note: Users upgrading from VxRail v4.5.400 may need to perform manual steps after completing the
v7.0.200 upgrade to implement some of the security mitigations. For a description of these issues and a
link to the mitigation procedure, review the MCEPSC vulnerability described in the “Security fixes” section
of the release notes.

Task 6: Remove snapshots of the service Virtual Machines.

Once the upgrade has completed successfully, remove all the snapshots created in the “Take a snapshot
of the service Virtual Machines” section to prevent vSAN capacity utilization long term:
 VxRail Manager VM
 VMware vCenter Server Appliance VM (if using embedded)
 VMware vCenter Server Platform Services Controller VM (if using embedded)
 VMware vRealize Log Insight VM (if using VxRail deployed syslog)
 ESRS VE VM (if call home is enabled and using VxRail Manager deployed ESRS)
1. [ ] Navigate to Home > Hosts and Clusters > VxRail-Cluster.

Dell Technologies Confidential Information version: 4.2.3.3

Page 22 of 28
 Figure 34

2. [ ] Remove the snapshot of a service VM. For example, right-click VxRail Manager > Snapshots >
Manage Snapshots.

Figure 35

3. [ ] Select the appropriate snapshot and click Delete.

Dell Technologies Confidential Information version: 4.2.3.3

Page 23 of 28
 Figure 36

4. [ ] Click OK to remove the snapshot.

Figure 37

5. [ ] Repeat steps 2 through 4 for each of the remaining service VM’s.

Task 7: Mystic Service account password change (Optional)

With the release of v4.7.x, the Mystic Service account can now have the password changed. Work with
your customer to determine the new password. To change the password, perform the following:

1. [ ] Log in to vCenter Server using HTML5 Client with administrative privileges.

2. [ ] Navigate to Home > Host and Clusters > VxRail-Cluster > VxRail Manager.
3. [ ] Under the Summary tab, click Launch Web Console.

Dell Technologies Confidential Information version: 4.2.3.3

Page 24 of 28
 Figure 38

4. [ ] Login with root username and password.

Figure 39

5. [ ] Perform the following command to update the password:

# passwd mystic
6. [ ] Enter the new password as prompted.
7. [ ] Type logout to log out of VxRail Manager console.

Dell Technologies Confidential Information version: 4.2.3.3

Page 25 of 28
Appendix A: Get the Correct Controller Key Value
1. [ ] Connect to https://<vCenterServer IP Address>/mob and log in using administrator@domain
credentials.

Figure 40

2. [ ] Click content to access the MOB properties table. The MOB properties table has three columns
labeled NAME, TYPE, and VALUE.

Figure 41

3. [ ] Locate property with NAME rootFolder and TYPE ManagedObjectReference:Folder and click on
the link for (Datacenters) VALUE.

Figure 42 MOB root folder for data center

Dell Technologies Confidential Information version: 4.2.3.3

Page 26 of 28
 4. [ ] Locate the property with NAME ChildEntity and TYPE ManagedObjectReference:ManagedEntity[].
Click on the link for the VxRail-Datacenter VALUE.

Figure 43

5. [ ] Locate the property with NAME datastore and TYPE ManagedObjectReference:Datastore[] for the
VxRail-Virtual-SAN-datastore-uuid VALUE.

Figure 44 Sample MoRef ID for vSAN Database

6. [ ] Click on datastore-morefid link just to the left of VxRail-Virtual-SAN-datastore-uuid.

7. [ ] Locate the property with NAME vm and TYPE ManagedObject Reference:VirtualMachine[].
Record the MoRef ID value of the VxRail Manager entity labeled VxRail Manager.

Figure 45 Sample MoRef ID for VxRail Manager

8. [ ] Click on VxRail Manager-morefid link just to the left of VxRail Manager.

9. [ ] Locate the property with NAME config and TYPE VirtualMachineConfigInfo. Click on the link
for the config VALUE.

Figure 46 Sample MoRef ID for config

10. [ ] Locate the property with NAME hardware and TYPE VirtualHardware. Click on the link for the
hardware VALUE.

Dell Technologies Confidential Information version: 4.2.3.3

Page 27 of 28
 Figure 47 Sample MoRef ID for hardware

11. [ ] Locate the property with NAME device and TYPE VirtualDevice[]. Record the value of
VirtualLsiLogicController.

Figure 48

Troubleshooting
If vCenter upgrade failed, you can revert vCenter and PSC and then check vCenter service status to
confirm vCenter and PSC reverted to previous upgrade version. Please refer to
https://support.emc.com/kb/542406 for more details.

Dell Technologies Confidential Information version: 4.2.3.3

Page 28 of 28