H18075 - VVD 5.1.1 Upgrade Guide

VMware Validated Design for SDDC v5.1.
1 on
Dell EMC VxRail
Upgrade Guide
Abstract
This guide provides information for upgrading VMware Validated Design
(VVD) on VxRail from version 5.1. to 5.1.1. The document is based on
VMware’s validated design upgrade documentation. It provides step-by-
step instructions for upgrading the VxRail and Software-Defined Data
Center (SDDC) components that are deployed according to the SDDC
5.1 VVD on VxRail Guide.
January 2020
Dell Customer Communication - Confidential

The information in this publication is provided “as is.” Dell Inc. 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.
Use, copying, and distribution of any software described in this publication requires an applicable software license.
Copyright © 2019-2020 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners. [1/13/2020] [Upgrade Guide] [H18075]

Contents
1 About VMware Validated Design Upgrade ................................................................................................................... 5
Required VMware software ................................................................................................................................ 5
Required VxRail software ................................................................................................................................... 5
Before you apply this guidance .......................................................................................................................... 5
2 SDDC Upgrade Overview ............................................................................................................................................ 6
Upgrade policy .................................................................................................................................................... 6
Upgrade paths and application upgrade sequence ............................................................................................ 6
VMware software versions in the upgrade package........................................................................................... 8
General prerequisites for the SDDC upgrade .................................................................................................... 8
Upgrade the content packs on vRealize Log Insight in Region A ...................................................................... 9
Upgrade the management packs for Site Recovery Manager in vRealize Operations Manager ....................10
3 Upgrade the Business Continuity Layer .....................................................................................................................11
Review and update vSphere storage APIs – Data Protection based backup solution.....................................11
4 Upgrade the virtual infrastructure layer ......................................................................................................................12
Upgrade the NSX components for the Management, Shared Edge and Compute clusters ............................12
Upgrade the NSX Manager instances ..............................................................................................................14
Upgrade the NSX Controller clusters ...............................................................................................................16
Upgrade the NSX components on the ESXi hosts ...........................................................................................17
Upgrade the NSX Edge instances ....................................................................................................................19
5 Upgrade the Management Cluster .............................................................................................................................23
Upgrade the Management vCenter Server and all Platform Services controller instances .............................23
Take snapshots of the vCenter Server and Platform Services controller instances ........................................24
Update the Platform Services controller for the Management cluster in Region A ..........................................25
Update the Platform Services controller instances in Region B .......................................................................27
Upgrade the VxRail Management cluster .........................................................................................................28
Upgrade the VxRail clusters and VMware tools for the Management cluster in Region B ..............................32
Upgrade the components for the Shared Edge and Compute clusters............................................................33
Global post-upgrade configuration of the virtual infrastructure layer ................................................................33
Set SDDC deployment details on the Management vCenter Server in Region A ............................................34
Set SDDC deployment details on the Shared Edge and Compute vCenter server in Region A......................34
Post-upgrade configuration of the virtual infrastructure components in Region B ...........................................35

6 SDDC Startup and Shutdown.....................................................................................................................................38
Shutdown order of the Management virtual machines .....................................................................................38
Start-up order of the Management Virtual Machines........................................................................................40
Before you begin...............................................................................................................................................40
Start up the ESXi hosts in the vSAN clusters ...................................................................................................40
Start up the management virtual machines: .....................................................................................................40

1 About VMware Validated Design Upgrade
This guide provides information for upgrading VMware Validated Design (VVD) on VxRail from version 5.1 to
5.1.1. The document is based on VMware’s validated design upgrade documentation. It provides a workflow and
step-by-step instructions for upgrading the VxRail and Software-Defined Data Center (SDDC) components that
are deployed according to the SDDC 5.1 VVD on VxRail Guide.
Before you start an upgrade of your SDDC, make sure that you are familiar with the upgrade planning guidance
that is part of this document.
The VMware Validated Design Upgrade documentation is intended for cloud architects, infrastructure
administrators, and cloud administrators who are familiar with and want to keep their VMware software up-to-
date.
Required VMware software

The VMware Validated Design Upgrade documentation is compliant and validated with certain product versions.
See the VMware Validated Design Release Notes and VMware software versions in the upgrade package for
more information about supported product versions.
Required VxRail software

The VVD on VxRail version 5.1 to 5.1.1 upgrade requires a VxRail cluster running release 4.7.410 or later. This
VxRail release contains software which is aligned to the VVD 5.1.1 software BOM. Subsequent releases can be
used as long as they fall within the 4.7.4xx family.
Before you apply this guidance

The sequence of the VMware Validated Design documentation follows the stages for implementing and
maintaining an SDDC. See Documentation Map for VMware Validated Design.
To use this VMware Validated Design Upgrade Guide, you must be familiar with the following:
• VxRail installation and administration
• VVD architecture and design
• VVD planning and preparation

2 SDDC Upgrade Overview
VVD on VxRail reduces risk and time in performing upgrades by validating the procedures and software versions
associated with each VVD release. Consider the policy, upgrade paths, system requirements and upgrade
sequence for a successful SDDC upgrade.
Upgrade policy
VVD provides guidance to upgrade the SDDC management products according to an upgrade validation policy.
Dell EMC has further validated and adjusted these procedures for the VVD on VxRail implementations.
Upgrades and updates that are validated by VVD

VVD follows a set of lifecycle management principles for the VMware SDDC components and the VxRail
clusters.
Upgrade Might impact the SDDC design and implementation, ensures
interoperability, and introduces new features, functionality, and bug fixes.
Update Does not impact the SDDC design and implementation, ensures
interoperability, includes bug fixes and VxRail patches.
The upgrade of a VVD provides a specific procedure to move between each release. Unless specific express
patches or hot fixes are required for an environment, a deviation is not supported.
Updates that are not validated by VVD

Scalability and functional tests for individual patches, express patches, or hot fixes are not typically performed
against a VVD.
Upgrade paths and application upgrade sequence

You must follow the SDDC upgrade path and sequences for this VVD.
Upgrade paths
You must run VVD version 5.1 before you upgrade to version 5.1.1.
Upgrade paths of this validated design
Currently Installed Version Upgrade Path
4.1 4.2
4.2 4.3
4.3 5.0.1
5.01 5.1
5.1 5.1.1
Upgrade sequence
The upgrade process of this VVD release provides the following benefits:
• Isolates the VMware and VxRail components at functional layers.

• Supports incremental upgrade from one version to another with minimal context switching between
products and user interfaces.
• Reduces the overall time to upgrade and the impact of a failed component upgrade.
• Upgrading the operations management layer first provides continuous monitoring and alerting during the
subsequent upgrade processes.
• By decoupling the upgrade of Site Recovery Manager and vSphere Replication from the upgrade of
Platform Services Controller and vCenter Server in both Region A and Region B, you can accurately size
and schedule the maintenance windows for the end-to-end upgrade across both regions.
Upgrade sequence of this VVD
Order Upgraded Component Sub-Component (in SDDC Layer
or Updated Order)
1 No vRealize Suite Lifecycle Operations Management
Manager
2 Yes vRealize Log Insight Content Packs Only
3 Yes vRealize Operations Management Packs Only
Manager
4 No vRealize Business for Cloud Management
Cloud
5 No vRealize Automation
6† Determined vSphere Storage APIs for Business Continuity

by Data Protection-based
Organization Backup Solution
7 No vSphere Replication
Site Recovery Manager
8 Yes NSX Data Center for NSX Manager Instances Virtual Infrastructure –
vSphere Networking
NSX Controller Instances
NSX Networking Fabric
NSX Edges
9 Yes Platform Services Controller Virtual Infrastructure –
Management
vCenter Server
vSphere Update Manager
Download Service
VMware Tools
10 Yes ESXi, Firmware, BIOS VxRail Composite Bundle VxRail Lifecycle Manage-
vSAN ment (LCM) Cluster
11 Yes Platform Services Controller Virtual Infrastructure –
vCenter Server Shared Edge Compute
12 Yes ESXi, Firmware, BIOS, vSAN VxRail Composite Bundle VxRail LCM Edge
Compute Cluster
Note: VVD requires a compatible and supported backup solution. Refer to your backup solution documentation
for the interoperability with the vSphere versions listed in the Release Notes. If the backup solution is not
compatible, upgrade the backup solution before you upgrade the rest of the components of this VVD
environment.

VMware software versions in the upgrade package
Upgrade each SDDC management product to the specific version according to the software bill of materials in
this VVD.
Upgrade from VVD for SDDC 5.1 to VVD for SDDC 5.1.
SDDC Layer Product Name Product Product Operation
Version in Version in Type
VVD5.1 VVD5.1.1
Operations vRealize Suite Lifecycle Manager 2.1.0 Patch 2 2.1 Patch 2 N/A
Management
vRealize Log Insight 4.8 4.8 N/A
vRealize Log Insight Agent 4.8 4.8 N/A
vRealize Operations Manager 7.5 7.5 N/A
Cloud vRealize Business for Cloud 7.6 7.6 N/A

Management
vRealize Automation with 7.6 7.6 N/A
Embedded vRealize Orchestrator
Business Site Recovery Manager 8.2 8.2 N/A
Continuity
vSphere Replication 8.2 8.2 N/A
Backup solution based on VMware Compatible Compatible Vendor

vSphere Storage APIs for Data Version Version Specific
Protection
Virtual NSX Data Center for vSphere 6.4.5 6.4.6 Update
Infrastructure
Platform Services Controller 6.7 Update 2 6.7 P01 Upgrade
vCenter Server 6.7 Update 2 6.7 P01 Upgrade
VxRail Virtual ESXi 6.7 Update 2 6.7 P01 Upgrade

Infrastructure
4.7.212 vSAN 6.7 Update 2 6.7 P01 Upgrade
For information about all components included in the VVD 5.1 software bill of materials, see VMware Validated
Design Release Notes.
General prerequisites for the SDDC upgrade

Before you upgrade the functional layers of the SDDC, ensure that your existing VVD environment meets the
following general prerequisites:
• Review the VMware Validated Design Planning and Preparation documentation and the individual
prerequisites for each product. Address any hardware or software requirements that might impact the
upgrade.
• Verify that your VMware vSphere Storage APIs for Data Protection-based backup solution has been
certified with vSphere 6.7 P01. For more information, contact your backup solution vendor.
• Review all custom integrations developed and deployed externally from the VVD framework to ensure
compatibility with product versions in the updated software bill of materials, such as vRealize Orchestrator
workflows.
• Review all third-party product integrations in your environment to ensure compatibility with the product
versions in the updated software bill of materials.

• Confirm the system health of all VxRail clusters within VxRail Manager and address any alarms or error
conditions before proceeding.
Upgrade the content packs on vRealize Log Insight in Region A

After you upgrade the vRealize Log Insight cluster, upgrade the content packs using the Content Pack
Marketplace in vRealize Log Insight.
vRealize Log Insight Content Pack
Content Pack Version

vRealize Log Insight Content Pack for NSX for vSphere 3.9
vRealize Log Insight Content Pack for vRealize Automation 7.5 1.0
vRealize Log Insight Content Pack for vRealize Orchestrator 2.10
vRealize Log Insight Content Pack for vRealize Business 1.53
vRealize Log Insight Content Pack for Linux 2.0.1
vRealize Log Insight Content Pack for vSAN 2.2
Procedure
1. Log in to the vRealize Log Insight user interface.
a Open a Web browser and go to ht t p s: / /sf o0 1v r li 0 1. sf o 0 1. ra inp ol e. lo ca l.
b Log in with username: admin and password: vrli_admin_password.
2. Click the configuration drop-down menu icon and select Content Packs.
3. Uninstall the outdated content packs for vRealize Automation and Microsoft SQL Server.
a In the navigation pane, under Installed Content Packs, click VMware-vRA 7.3+
b Click the settings drop-down menu icon , select Uninstall, and click OK.
c To confirm, click OK.
d Repeat Steps 3.a to 3.c for content pack Microsoft – SQL Server.
4. Install the new content pack for vRealize Automation.
a In the navigation pane, under Content Pack Marketplace, click Marketplace.
b Click the VMware – vRA 7.5+ content pack.
c In the Install Content Pack dialog box, select the checkbox to accept the terms of the license
agreement.
d Click Install, and then click OK.
5. Update content packs.
6. In the Navigator, under Content Pack Marketplace, click Updates.
7. On the Log Insight Content Pack Marketplace page, click the Linux 2.0.1 content pack update.
8. In the Update Content Packs dialog box of Linux 2.0.1, click Update.
9. Click OK to complete the update of the Linux 2.0.1 content packs.
10. Under Installed Content Packs, verify that the version number of each content pack matches with
the version for this validated design.

Upgrade the management packs for Site Recovery Manager in
vRealize Operations Manager
After you finish the upgrade of vRealize Operations Manager, upgrade the management packs for NSX for
vSphere and for Site Recovery Manager to ensure continuous interoperability.
vRealize Operations Manager management packs
PAK Type PAK File
vRealize Operations Management Pack for NSX for vmware-MPforNSX-vSphere-build_number.pak
vSphere
vRealize Operations Management Pack for VMware VMware-srm-vrops-mp-build_number.pak
Site Recovery Manager
Procedure
1. Log in to vRealize Operations Manager by using the operations interface.
a Open a Web browser and go to ht t p s: / /v ro ps 0 1sv r0 1 .r a inpo le .l oc a l.
b Log in with username: admin and password: vrops_admin_password.
2. Upgrade the Management Pack for NSX for vSphere.
a On the main navigation bar, click Administration.

b In the left pane, click Solutions.
c On the Solutions page, click the Add icon.
d On the Select a Solution page, browse your file system and locate the .pak file of Management
Pack for Storage Devices and click Open.
e Select Install the PAK file even if it is already installed, click Upload, and click Next.
f On the End User Agreement page, select the I accept the terms of this agreement check box
and click Next.
g After the upgrade is complete, click Finish.
3. Verify that the adapters are collecting metrics.
a On the Solutions page, select Management Pack for Storage Devices from the solution table.
b Under Configured Adapter Instances, verify that the Collection State is Collecting and the
Collection Status is Data receiving.
4. Repeat this procedure and upgrade the Management Pack for Site Recovery Manager.
10

3 Upgrade the Business Continuity Layer
After the operations management and cloud management layers have been upgraded, proceed to the
components of the business continuity layer.
Upgrade sequence for the Business Continuity layer in VVD
Order Component Sub-Component

1 vSphere Storage APIs – Data Protection Based Backup Solution -
2 vSphere Replication Virtual Appliance in Region A -
3 Site Recovery Manager Instance in Region A -
4 vSphere Replication Virtual Appliance in Region B -
5 Site Recovery Manager Instance in Region B -
6 Migration of Site Recovery Manager to an appliance in Region A -
7 Migration of Site Recovery Manager to an appliance in Region B -
Review and update vSphere storage APIs – Data Protection based

backup solution
Before you upgrade the virtual infrastructure layer, verify that your vSphere Storage APIs – Data Protection
(VADP) based backup solution is compatible with the version of vSphere in this release of VVD.
Perform the upgrade outside of the usual backup windows.
Prerequisites
• Verify that your backup solution is compatible with vSphere 6.7 P01. Contact your backup solution
vendor for product compatibility matrices.
• Verify that all customizations or integrations are compatible with the backup solution. Contact your
backup solution vendor.
• Verify that the backup solution is fully operational and compatible with any other clients, such as,
reporting tools, web browsers, and so forth. Contact your backup solution vendor for their product
compatibility matrices.
• Allocate adequate time for the duration of the maintenance window. Contact your backup solution
vendor to estimate the time required to upgrade and verify solution operations.
• Verify that no alarms exist for the backup solution in both the vSphere Web Client and backup solution
management interfaces.
What to do next
Verify that backup solution is operational after the upgrade.
11

4 Upgrade the virtual infrastructure layer
After upgrading the operations management, cloud management, and business continuity layers, upgrade the
components of the virtual infrastructure layer of the SDDC. Upgrade the virtual infrastructure layer last to
reduce the time to upgrade the whole stack and prevent errors caused by incompatibility between product
versions.
Upgrade sequence for the Virtual Infrastructure layer in VVD
Order Component Sub-Component

1 NSX for vSphere NSX Manager instances
NSX Controller instances
NSX Networking fabric
NSX Edges
Post-upgrade configuration of NSX
2 Platform Services Controller instances -
vCenter Server instances for the management
clusters
-
3 VxRail Management cluster Upgrade -
5 vCenter Server instances for the shared edge -
and compute clusters
6 VxRail Compute cluster Upgrade -
7 Post-upgrade reconfiguration for the virtual -
infrastructure layer
Upgrade the NSX components for the Management, Shared Edge

and Compute clusters
Begin the virtual infrastructure upgrade by upgrading the NSX environment. Upgrade each functional group of
devices in the NSX Region A and Region B deployment.
Upgrading NSX is a multi-step process. Upgrade the paired NSX Manager instances for cross-vCenter
networking and security, then the NSX Controller nodes, the ESXi VIBs, and the NSX Edge devices, starting
with the universal distributed logical routers. This upgrade operation is split between the management cluster
pairs and the shared edge and compute cluster pairs.
NSX for vSphere components in the SDDC
Region Role IP Address FQDN
Region A NSX Manager for the management 172.16.11.65 sfo01m01nsx01.sfo01.rainpole.local
cluster that is running as primary
NSX Controller 1 for the management 172.16.11.118 -
cluster
cluster
cluster
12

Region Role IP Address FQDN
NSX Manager for the shared edge and 172.16.11.66 sfo01w01nsx01.sfo01.rainpole.local
compute cluster that is running as
primary
NSX Controller 1 for the shared edge 172.16.31.118 -
and compute cluster
and compute cluster
and compute cluster
Region B NSX Manager for the management 172.17.11.65 lax01m01nsx01.lax01.rainpole.local
cluster that is running as secondary
NSX Manager for the shared edge and 172.17.11.66 lax01w01nsx01.lax01.rainpole.local
compute cluster that is running as
secondary
Note: vRealize Operations Manager and vRealize Log Insight might generate several false alerts during the NSX
upgrade procedure.
Prerequisites
• Download the NSX upgrade bundle, VMware-NSX-Manager-upgrade-bundle-6.4.6-
build_number.tar.gz, from My VMware to a Windows host that has access to your data center.
• Review the release notes for this NSX build.
• Review Operational Impacts of NSX Upgrade in the NSX Upgrade Guide to understand the impact that
each component might have on your environment.
• Review Upgrade NSX in a Cross-vCenter NSX Environment and Upgrade NSX Using Upgrade
Coordinator in NSX Upgrade Guide to understand the prerequisites for your environment and the
provided detailed upgrade guidance.
• Verify that all virtual networking integration in the environment has been quiesced of all activities,
including but not limited to the following operations:
Users ordering new virtual machines backed by virtual wires over the cloud management platform
Тhird-party integration that automates the ordering or deployment of new virtual machines that are
backed by virtual wires
Administrators manually creating new NSX-based components
Without quiescing the environment, rollback operations might be disrupted by orphaned objects
generated after you have taken snapshots. That could result in an extended maintenance window.
• Validate the NSX Manager file system usage and perform space reclamation if necessary.
13

Procedure
1. Open an SSH connection to the NSX Manager instance you are upgrading using the admin account
credentials and run the following command to show the filesystem usage.
show filesystems
2. If the filesystem usage is at 100 percent, enter Privileged mode and clear the logs by running the
following commands.
enable
purge log manager
purge log system
3. Reboot the NSX Manager appliance to apply the log clean-up.

4. Back up the NSX configuration and download the technical support logs.
5. Back up the NSX Manager pair, both primary and secondary instances. For more information, see
Back Up and Restore NSX Manager in the NSX Upgrade Guide.
6. Verify that each NSX controller is in normal, connected state.
7. Verify that Host Preparation > Installation Status of all clusters has the green checkmark and the
proper NSX for vSphere version.
8. Get the current version of the NSX VIBs on the hosts in the management cluster and in the shared
edge and compute cluster.
a Log in to one of the hosts in the cluster by using the ESXi Host Client.
b Select Host > Manage.
c On the Packages tab, search for es x- n .
d Note the current version of the esx-nsxv VIB.
Upgrade the NSX Manager instances

When you upgrade the NSX components in Region A and Region B, upgrade the NSX Manager instances first.
Start with the NSX Manager nodes for the management cluster. Continue with the NSX Manager nodes for the
shared edge and compute cluster. You must upgrade the primary and all secondary NSX Manager instances to
the same version in the same maintenance window. The upgrade of the management clusters and the shared
edge and compute clusters should also be performed in the same maintenance window, but could be separate
if required.
NSX Manager nodes in the SDDC
Order Region NSX Manager NSX Appliance URL vCenter Server

Instance URL
1 Region A Primary NSX Manager https://sfo01m01nsx01.sfo01. sfo01m01vc01.sfo01.
for the management rainpole.local rainpole.local
cluster
2 Region B Secondary NSX https://lax01m01nsx01.lax01. lax01m01vc01.lax01.
Manager for the rainpole.local rainpole.local
management cluster
3 Region A Primary NSX Manager https://sfo01w01nsx01.sfo01. sfo01m01vc01.sfo01.
for the shared edge rainpole.local rainpole.local
and compute cluster
14

Order Region NSX Manager NSX Appliance URL vCenter Server
Instance URL
4 Region B Secondary NSX https://lax01w01nsx01.lax01. lax01m01vc01.lax01.
Manager for the shared rainpole.local rainpole.local
edge and compute
cluster
Procedure
1. Log in to the Management NSX Manager appliance user interface.
a Open a Web browser and go to ht t p s: / /sf o0 1m 0 1n sx 0 1. sf o 0 1. r ain pol e. l oc al.

b Log in with username: admin and password: nsx_manager_admin_password.
2. Click Upgrade, and on the Upgrade page, click Upload Bundle.
3. In the Upgrade dialog box, click Choose File and navigate to the VMware-NSX-Manager-upgrade-
bundle-6.4.6-build_number.tar.gz upgrade bundle on your file system.
4. Click Open > Continue.
The NSX Manager starts uploading the upgrade bundle.
5. After the upload is complete, in the Upgrade dialog box, configure the following settings and click
Upgrade.
Upgrade dialog box settings
Setting Value
Do you want to enable SSH? Yes
Do you want to join the VMware Customer Yes
Experience Program
Note: You are logged out of the NSX Manager while it reboots.
6. Log in to the Management NSX Manager appliance user interface.
a Open a Web browser and go to ht t p s: / /sf o0 1m 0 1n sx 0 1. sf o 0 1. r ain pol e. l oc al.

b Log in with username admin and password nsx_manager_admin_password.
7. Click Upgrade and verify that the Upgrade tab shows the following configuration.
Upgrade tab settings
Setting Expected Value

Current Software Version 6.4.6-build_number
Upgrade State Complete
8. Log in to vCenter Server by using the vSphere Web Client.
a Open a Web browser and go

to ht t p s: // sf o 0 1m 01v c 01 . sf o 01 .r a inpo l e. loc al /v sp he r e-c li ent /.
b Log in with username [email protected] and password vsphere_admin_password.
9. In the vSphere Web client, check for the latest NSX plug-in.
a Click Menu > Administration.
15

b In the navigation pane, under Solutions, click Client Plug-Ins.
c Verify that the NSX plugins are upgraded to version 6.4.6.
10. Perform a fresh backup of the primary NSX Manager, sfo01m01nsx01.sfo01.rainpole.local.
Note: You cannot restore the new NSX Manager from previous backups.
11. To complete the NSX Manager upgrade in the management cluster, repeat the steps for the NSX
Manager on Region B, lax01m01nsx01.lax01.rainpole.local.
12. Repeat the procedure for the shared edge and compute cluster.
13. Start with the primary NSX Manager Region A, sfo01w01nsx01.sfo01.rainpole.local, and complete
the upgrade of the Region B NSX Manager, lax01w01nsx01.lax01.rainpole.local (if applicable).
Upgrade the NSX Controller clusters

After you upgrade the NSX Manager instances in Region A and Region B, upgrade the NSX Controller
instances for the management cluster and the shared edge and compute cluster. Upgrade the NSX Controllers
clusters immediately after the upgrade the of the NSX Manager instances to keep their versions aligned.
You can use the Upgrade Coordinator to orchestrate the upgrade of the NSX components in the environment. If
using Upgrade Coordinator for this validated design, do not use the one-click option; upgrade each component
one-by-one to maintain control.
Upgrade the NSX Controller instances for the management cluster first, then upgrade the NSX Controller
instances for the shared edge and compute cluster. You can perform these operations in the same or separate
maintenance windows.
NSX Controller nodes in Region A
Order Region NSX Manager NSX Manager IP NSX Controller IP

Address Address
1 Region A Primary NSX Manager for 172.16.11.65 172.16.11.118
the management cluster 172.16.11.119
172.16.11.120
2 Region A Primary NSX Manager for 172.16.11.66 172.16.31.118
the shared edge and
172.16.31.119
compute cluster
172.16.31.120
Procedure

b Log in using username [email protected] and password vsphere_admin_password.
2. In the Networking and Security inventory, click Installation and Upgrade.
3. On the Upgrade tab, from the NSX Manager drop-down menu, select the 172.16.11.65 |
Primary NSX Manager instance, and click Plan Upgrade.
4. On the Select Upgrade Plan page of the Upgrade Components wizard, select Plan Your Upgrade
and click Next.
5. On the Plan Content page, configure the following settings and click Next.
16

Plan content settings
Setting Value
Select Components Clusters Deselected
Universal Logical Routers Deselected
NSX Edges Deselected
Service VMs Deselected
Define Pause Upgrade Pause between components Enabled
Options Pause on error Enabled
6. On the Review Plan page, verify that Pause between components and Pause on error are set to Yes,
and click Start Upgrade.
7. Monitor the progress of the upgrade of the NSX Controller nodes.
a From the Upgrade tab, click View Details.
b The Planned Controllers Upgrade Details dialog box shows the overall progress of the controller
upgrade.
c On the Management tab Click NSX Controller Nodes.
The Upgrade Status column shows the following stages for each NSX Controller:
NSX controller stages
Status Controller Upgrade Stage

Connected Not Started
Downloading Upgrade
Downloading Upgrade Completed
Upgrading
Service Unavailable Rebooting
Connected Upgraded
8. After the upgrade is completed, select the Management tab, and in the NSX Controller nodes
section, verify that the upgraded NSX Controller has the following configuration.
NSX controller configurations

Status Connected
Software Version 6.4.6.build_number
9. After all of the NSX Controllers have been upgraded, click Resume on the Upgrade tab.
10. After the upgrade of the NSX Management Controller cluster is completed, repeat the procedure on
the Shared Edge and Compute cluster in Region A.
Upgrade the NSX components on the ESXi hosts

After the NSX Manager and NSX Controller cluster instances in Region A and Region B, update the
NSX Virtual Infrastructure Bundle (VIB) on each ESXi host in the management and in the shared edge
and compute clusters.
17

For each NSX Manager instance in Region A and Region B, run an upgrade for each cluster. Run the upgrade
on the hosts of the management cluster first.
NSX Manager instances and associated clusters
Region NSX Manager NSX Cluster
Manager IP
Address
Region A Primary NSX Manager for 172.16.11.65 sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc > sfo01-m01-mgmt01
the management cluster
Primary NSX Manager for 172.16.11.66 sfo01w01vc01.sfo01.rainpole.local > sfo01-w01dc > sfo01-w01-comp01
the shared edge and
compute cluster
Region B Secondary NSX Manager 172.17.11.65 lax01m01vc01.lax01.rainpole.local > lax01-m01dc > lax01-m01-mgmt01
for the management cluster
Secondary NSX Manager 172.17.11.66 lax01w01vc01.lax01.rainpole.local > lax01-w01dc > lax01-w01-comp01
for the shared edge and
compute cluster
Prerequisites
Before you upgrade the NSX components on the ESXi hosts, verify the following:
• vSphere DRS is enabled and set to Fully Automated on the clusters.
• vSphere vMotion functions correctly between the ESXi hosts in each cluster.
• All ESXi hosts are connected to vCenter Server.
• No ESXi hosts are in maintenance mode in vCenter Server.
Procedure

b Log in with username [email protected] and password vsphere_admin_password.
2. In Networking and Security inventory, click Installation and Upgrade.
3. Click the Upgrade tab. From the NSX Manager drop-down menu, select the 172.16.11.65 |
4. On the Select Upgrade Plan page of the Upgrade Components wizard, select Plan Your Upgrade
and click Next.
Setting Value
Select Components Clusters Selected
Universal Logical Routers Deselected
NSX Edges Deselected
Define Pause Upgrade Options Pause between components Enabled
18

Setting Value
Pause on error Enabled
6. On the Plan Host Clusters page, select Group for newly added Clusters, and click Edit.
7. In the Edit Upgrade Group dialog box, verify that the following settings are configured, click OK, and
click Next.
Upgrade group settings

Selected Objects sfo01-m01-mgmt01
Upgrade Order Serial
9. Validate that the NSX Controllers are running version 6.4.6.build_number, and click Resume to
proceed to the upgrade of the next cluster.
10. Monitor the progress.
11. From the Upgrade tab, click View Details.
The Upgrade Plan Progress dialog box shows the overall progress of the cluster upgrade. Click the
Details button for additional information about each step.
12. Click the Host Preparation tab.
The NSX Installation changes to In Progress while the NSX upgrade is applied to each ESXi host.
Each host is placed in to maintenance mode during the upgrade.
13. Wait for the NSX VIB upgrade of each ESXi host in the management cluster in Region A.
After the upgrade of all ESXi hosts is completed, they are in a ready state, indicated by a green
checkmark, with a VIB version of 6.4.6.build_number.
14. Repeat the steps to upgrade the NSX components on the remaining clusters in Region A and Region
B.
15. When you perform the upgrade on a secondary node in Region B, provide the following user name
and password in the Enter Secondary Manager Credentials dialog box, and click OK.
Secondary Manager credentials
Setting Value
User name [email protected]
Password svc-nsxmanager_password
Upgrade the NSX Edge instances

After you upgrade the control and data plane components of NSX for vSphere, upgrade the universal
distributed logical router, NSX Edge services gateways, and load balancer instances.
For each NSX Manager instance in Region A and Region B, run an upgrade for each universal distributed
logical router (UDLR), distributed logical router (DLR), and the edge services gateways (ESG) in each region.
Using Upgrade Coordinator, create an upgrade plan for the management cluster edge devices in Region A first,
then, proceed with the remaining clusters in each region.
19

NSX Manager instances and associated host clusters
Region NSX Manager NSX Host Cluster

Manager IP
Address
Region A Primary NSX Manager for the management 172.16.11.65 sfo01-m01-mgmt01
cluster
Primary NSX Manager for the 172.16.11.66 sfo01-w01-comp01
shared edge and compute cluster
Region B Secondary NSX Manager for the management 172.17.11.65 lax01-m01-mgmt01
cluster
Secondary NSX Manager for the shared edge 172.17.11.66 lax01-w01-comp01
and compute cluster
NSX Edge instances upgrade ordering for the Management clusters

Order Management UDLR in Management Edge in Management Edge
Region A Region A with in Region B
Availability Zones
1 sfo01m01udlr01 - -
2 - -
 sfo01m01esg01
 sfo01m01esg02
If using multiple availability
zones:
 sfo02m01esg01
 sfo02m01esg02
 sfo01m01lb01
 sfo01psc01
3 - -
• lax01m01esg01
• lax01m01esg02
• lax01m01lb01
• lax01m01psc01
4 sfo01w01udlr01 - -
5 - -
 sfo01w01dlr01
 sfo01w01esg01
 sfo01w01esg02
6 - -
 lax01w01dlr01
 lax01w01esg01
 lax01w01esg02
Procedure
20

b Log in using username [email protected] and password vsphere_admin_password.
2. In the Networking and Security inventory, click Installation and Upgrade.
3. Click the Upgrade tab, from the NSX Manager drop-down menu, select the 172.16.11.65 |
4. On the Select Upgrade Plan page of the Upgrade Components wizard, click Plan Your Upgrade and
click Next.
Setting Value
Select Components Clusters Deselected
Universal Logical Routers Selected
NSX Edges Selected
Define Pause Upgrade Options Pause between components Enabled
Pause on error Enabled
6. On the Universal Logical Routers page, select universal_routers_host_cluster, and click Edit.
7. In the Edit Upgrade Group dialog box, verify the following settings and click OK.
UDLR settings

Selected Objects Management UDLR in Region A per NSX Edge Instances
Upgrade order Serial
8. On the Plan NSX Edges page, select edge_host cluster, and click Edit.
9. In the Edit Upgrade Group dialog box, verify that the following settings are configured, click OK, and
click Next.
Management Edge settings

Selected Objects Management Edge in Region A per NSX Edge Instances
Upgrade order Serial
Note: Performing the upgrade in a serialized order minimizes disruption on both the management and shared
and edge compute clusters.
11. Verify that the NSX Controllers are of version 6.4.6.build_number , and click Resume to proceed
to the universal logical router upgrade.
12. Monitor the progress. From the Upgrade tab Click View Details.
The Upgrade Plan Progress dialog box shows the overall progress of the Universal Logical
Router upgrade.
13. From the navigation pane, under Networking and Security click NSX Edges.
21

During the UDLR upgrade, the Deployment Status column for UDLR shows Busy. After a successful
upgrade of the UDLR, the Deployment Status shows Deployed.
14. To Proceed with the NSX Edge upgrade, from the navigation pan, under Networking and Security,
click Installation and Upgrade. Select the Upgrade tab, and click Resume.
15. Wait for upgrade of each NSX Edge instance by monitoring the progress.
16. After all the NSX Edge instances are upgraded, on the NSX Edges page under Networking and
Security, verify that the Deployment Status for each edge device shows Deployed, and the Version
column contains the upgraded version of 6.4.6.
17. On the Upgrade tab, under Installation and Upgrade, click Resume to close the wizard.
18. Repeat the steps to upgrade the NSX Edge instances in the management cluster of Region B.
When performing the upgrade to the secondary nodes in Region B, enter the following Secondary
Manager Credentials when prompted and click OK.
Secondary Manager credentials
Setting Value
User name [email protected]
Password svc-nsxmanager_user_ password
Confirm password svc-nsxmanager_user_ password
19. Repeat the steps to upgrade the NSX Edge instances in the shared edge and compute cluster,
starting with Region A, and following with Region B.
22

5 Upgrade the Management Cluster
Before you upgrade the virtual infrastructure layer of the SDDC, upgrade the components that support the
management cluster.
Upgrade the Management vCenter Server and all Platform Services

controller instances
When you upgrade the vSphere layer for the management components in the SDDC, upgrade both Platform
Services Controllers and the Management vCenter Server instances in Region A. Repeat this operation in
Region B.
Upgrade sequence for the Management vCenter and Platform Services controller
instances in the SDDC
Region Upgrade Role IP Fully Qualified Domain Name
Order Address
Region A 1 Management Platform 172.16.11.61 sfo01m01psc01.sfo01.rainpole.local
Services Controller
configured in a highly
available pair
2 Compute PSC configured 172.16.11.63 sfo01w01psc01.sfo01.rainpole.local
in an HA pair
3 Management vCenter 172.16.11.62 sfo01m01vc01.sfo01.rainpole.local
Server
Region B 4 Management Platform 172.17.11.61 lax01m01psc01.lax01.rainpole.local
Services Controllers
configured in highly
available pair
5 Compute Platform Services 172.17.11.63 lax01w01psc01.lax01.rainpole.local
Controllers configured in a
highly available pair
6 Management vCenter 172.17.11.62 lax01m01vc01.lax01.rainpole.local
Server
The Platform Services Controller instances for the management and for the shared edge and compute clusters
are configured as highly available pairs, you must upgrade each component in the following order. Start the
upgrade process by disabling traffic to the management Platform Services Controller in the load balancer,
upgrading the virtual appliance, then reenabling traffic in the load balancing for that Platform Services Controller
instance.
Repeat this process for the Platform Services Controller instance for the shared edge and compute cluster.
Prerequisites
• Download the vCenter Server Appliance Installer VMware-vCenter-Server-Appliance-6.7.0.042000-
14367737-patch-FP to a shared storage location where it can be mounted to the vCenter and Platform
Services Controller VMs.
• Review the release note of the vCenter Server version in this validated design.
• Verify that all management ESXi hosts have lockdown mode disabled during the upgrade.
• Verify that the management clusters do not have vSphere DRS set to Fully Automated.
23

• Verify that any integration with the Management vCenter Server instances in the environment has
been quiesced of all activities. Such activities include users performing active backups of components
and provisioning virtual machines by using vRealize Automation. Without quiescing the environment,
rollback operations can be disrupted by orphaned objects that created after snapshots have been
taken.
• Verify that current backups of all Platform Services Controller and Management vCenter Server virtual
appliances exist.
Take snapshots of the vCenter Server and Platform Services

controller instances
Before the update, take snapshots of the Management vCenter Server virtual appliance and the Platform
Services Controller virtual appliances in Region A and Region B.
vCenter Server and Platform Services controller
Region Folder Role Virtual Machine Name
Region A sfo01-m01fd-mgmt vCenter Server sfo01m01vc01
sfo01-m01fd-mgmt Platform Services Controller for the sfo01m01psc01
Management Cluster
sfo01-m01fd-mgmt Platform Services Controller for the sfo01w01psc01
Shared Edge and Compute Cluster
Region B lax01-m01fd-mgmt vCenter Server lax01m01vc01
lax01-m01fd-mgmt Platform Services Controller for the lax01m01psc01
Management Cluster
lax01-m01fd-mgmt Platform Services Controller for the lax01w01psc01
Shared Edge and Compute Cluster
Procedure
a Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v c0 1. sf o 0 1. r ain pol e. l oc al /ui /.

b Log in with user name [email protected] and password vsphere_admin_password.
2. From the Home menu of the vSphere Web Client, click VMs and Templates.
3. Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-m01fd-mgmt data
center, and expand the sfo01-m01fd-mgmt folder.
4. Right-click sfo01m01vc01 and select Snapshots > Take Snapshot.
5. In the Take VM Snapshot dialog box, enter the following settings and click OK.
VM snapshot settings
Setting Value
Name VMware Validated Design 5.0.1 Virtual Infrastructure

Layer Upgrade
Description -
Snapshot the virtual machine's memory Deselected

Quiesce guest file system Deselected
(Needs VMware Tools installed)
24

6. Repeat the procedure for the Platform Service Controller instances in Region A, and for the
Management vCenter Server and all Platform Services Controller appliances in Region B.
Update the Platform Services controller for the Management cluster

in Region A
Begin the update of the Platform Services Controller appliances in Region A. To keep the services provided by
the Platform Services Controller instances running, direct all network traffic to one instance while the other
instance of the high availability pair is being updated.
Platform Services Controller Instances in Region A
Role Virtual Machine Name Fully Qualified Domain Name
Platform Services Controller for sfo01m01psc01 sfo01m01psc01.sfo01.rainpole.local
the management cluster
Platform Services Controller for sfo01w01psc01 sfo01w01psc01.sfo01.rainpole.local
the shared edge and compute
cluster
Procedure
a Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v c0 1. sf o 0 1. r ain pol e. l oc al /ui /.

b Log in with user name [email protected] and password vsphere_admin_password.
2. Direct all traffic to the Platform Services Controller for the Shared Edge and Compute cluster, disable
the membership of the Platform Services Controller for the Management cluster in the load balancer
pools.
a From the Home menu of the vSphere Web Client, select Networking & Security.
b In the Navigator, select NSX Edges.
c From the NSX Manager drop-down menu, select the 172.16.11.65 NSX Manager, and double-
click the sfo01psc01 NSX Edge device.
d On the Manage tab, click Load Balancer > Pools.
e Select the psc-https-443 load balancer pool and click Edit.
f In the Edit Pool dialog box, from the Members pane, select sfo01m01psc01, and click Edit.
g In the Edit Member dialog box, from the State drop-down menu, select Disable, and click OK.
h In the Edit Pool dialog box, click OK.
i Repeat Step 2.e to Step 2.h for the psc-tcp-389 load balancer pool.
j On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-
389 report status DOWN for sfo01m01psc01.
3. Mount the VMware vCenter Server Appliance Patch ISO file to the Platform Services Controller virtual
machine Update the Platform Services Controller.
a In the VMs and templates inventory, expand the sfo01m01vc01.sfo01.rainpole.local tree and
expand the sfo01-m01dc data center.
b Expand the sfo01-m01fd-mgmt folder.
25

c Click the sfo01m01psc01 virtual machine and click Launch Remote Console.
d In the Launch Remote Console dialog box, select Yes.
e In the VMware Remote Console, click VMRC and select Removable Devices > CD/DVD drive 1
> Connect to Disk Image File (iso)....
f In the Choose Image dialog box, navigate to the location of your downloaded VMware-vCenter-
Server-Appliance-6.7.0.x-build_number-patch-FP.isofile and click Open
4. Using a Web Browser, log in to the Platform Services Control VAMI interface.
a Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 ps c0 1. sf o 0 1. r ai npol e . loc a l: 5 4 80

b Log in with user name root and password psc_root_password.
5. Update the appliance.

a In the navigation pane, click Update.
b Click Check Updates and select Check CDROM.
c Click Stage and install.
d On the End user license agreement page, select I accept the terms of the license agreement
and click Next.
e On the Backup Platform Services Controller page, select I have backed up Platform Services
Controller and its associated databases and click Finish.
f When the update completes, in the Installation succeeded dialog box, click Close.
The Platform Services Controller appliance reboots.
g Re-authenticate to the VAMI interface and verify that the version has been updated, click
Update and verify the updated version number.
6. Restore the traffic to the Platform Services Controller for the Management cluster and enable
membership of the Platform Services Controller instance in the load balancer pools.
a From the vSphere Client, in Networking & Security inventory, select NSX Edges.
b From the NSX Manager drop-down menu, select the 172.16.11.65 NSX Manager, and double-
click the sfo01psc01 NSX Edge device.
c On the Manage tab, click Load Balancer > Pools.
d Select the psc-https-443 load balancer pool and click Edit.
e In the Edit Pool dialog box, from the Members pane, select sfo01m01psc01, and click Edit.
f In the Edit Member dialog box, from the State drop-down menu, select Enable, and click OK.
g In the Edit Pool dialog box, click OK.
h Repeat Step 6.e to Step 6.h for the psc-tcp-389 load balancer pool.
i On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-
389 report status UP for sfo01m01psc01.
7. Disconnect the attached update .iso file from the Platform Services Controller appliance.
8. Repeat this procedure for the sfo01w01psc01.sfo01.rainpole.local Platform Services Controller
instance in Region A.
26

Update the vCenter Server for the Management cluster in Region A
After completing the upgrade of the Platform Services Controller appliances in Region A, upgrade the vCenter
Server instance for the management cluster in Region A.
Procedure
1. Mount the VMware vCenter Server Appliance Patch ISO to the Management vCenter Server virtual
machine.
a Open a Web browser and log in to ht t p s: // sf o 01 m 01v c0 1 .sf o0 1. r ai npo l e. lo ca l/u i/

with user [email protected] and password vsphere_admin_password.
b In the VMs and templates inventory, expand the sfo01m01vc01.sfo01.rainpole.local tree and
expand the sfo01-m01dc data center.
c Expand the sfo01-m01fd-mgmt folder.
d Click the sfo01m01vc01 virtual machine and click Launch Remote Console.
e In the Launch Remote Console dialog box, click Yes.
f In the VMware Remote Console, click VMRC and select Removable Devices > CD/DVD drive 1
> Connect to Disk Image File (iso)....
g In the Choose Image dialog box, navigate to the location of your downloaded VMware-vCenter-
Server-Appliance-6.7.0.x-build_number-patch-FP.isofile and click Open
2. From a Web Browser log in to the Region A management vCenter server VAMI interface.
a Open a Web browser and go to the management port
@ ht tps :/ /s f o 01m 01 vc 01 .s f o 01 .r a in p ol e .l oc a l/ vs p her e-c l i en t: 5 48 0 .
b Log in with user name root and password root_password.
3. Update the appliance.
a In the navigation pane, click Update.
b Click Check Updates and select Check CDROM.
c Click Stage and install.
d On the End user license agreement page, select I accept the terms of the license agreement
and click Next.
e On the Backup vCenter Server page, select I have backed up vCenter Server and its
associated databases, and click Finish.
f When the update completes, in the Installation succeeded dialog box, click Close.
The vCenter Server appliance reboots.

g Re-authenticate to the vCenter VAMI interface and verify that the version has been updated,
click Update and verify the updated version number.
4. Disconnect the attached update .isofrom the Management vCenter Server appliance.
Update the Platform Services controller instances in Region B

After you complete the update of the management virtual infrastructure in Region A, update the Platform
Services Controller instances in Region B. To keep the services provided by the Platform Services Controller
instances running, direct all network traffic to one instance while the other instance of the highly available pair is
being upgraded.
27

1. Update the Platform Services Controller instances in Region B.
2. First update the Platform Services Controller instance for the management cluster, then update the
Platform Services Controller for the shared edge and compute cluster
3. Repeat Update the Platform Services Controller Instances in Region A by using the following details.
Platform Services controller settings
Setting Value Fully Qualified Domain Name

Platform Services Controller for the lax01m01psc01 lax01m01psc01.lax01.rainpole.local
management cluster
Platform Services Controller for the shared lax01w01psc01 lax01w01psc01.lax01.rainpole.local
edge and compute cluster
vCenter Server lax01m01vc01.lax01.rainpole.local
NSX Manager 172.17.11.65
Data Center lax01-m01dc
Folder lax01-m01fd-mgmt
4. Update the Management vCenter Server in Region B

Repeat Update the Management vCenter Server in Region A.
Management vCenter server settings
Setting Value Fully Qualified Domain Name

Virtual machine name of the vCenter Server lax01m01vc01 lax01m01vc01.lax01.rainpole.local
Instance for the management cluster
Data Center lax01-m01dc
Folder lax01-m01fd-mgmt
Upgrade the VxRail Management cluster

After you upgrade the SDDC infrastructure management components, perform the VxRail Lifecycle Manager
(LCM) upgrade to upgrade the VxRail Management cluster in Region A and Region B.
VxRail provides integrated lifecycle management to automate the process of upgrading the following
components in the each VxRail Cluster: Host BIOS, device firmware, ESXi Version, VxRail agents, vSAN
software, and the vDS version.
After completing the LCM process in the Region A Management Cluster, repeat the operations in Region B.
This sequence poses the least impact on your ability to perform disaster recovery operations in the SDDC and
minimal operational impact to your tenant workloads and provisioning operations.
VxRail Manager Systems in Region A
Regio VxRail IP Address vCenter Server Composite

n Manager Package
A sfo01m01vxm01 172.16.11.65 sfo01m01vc01.sfo01.rainpole.local 4.7.410
Prerequisites
• Confirm that the VxRail clusters are all in good health and have no alerts or warnings.
28

• Download the VxRail 4.7.410 composite software bundle for this upgrade.
- Download the following software package from the dellemc.com support site
https://download.emc.com/downloads/DL96732_VxRail-4.7.410-Composite-Upgrade-Package-
for-4.7.x.zip.
Verify that vSphere DRS on the management cluster is set to Fully Automated during the upgrade
operations.
• For VMware tools

- Verify that all ESXi hosts in the management cluster have been upgraded.
- Verify that the vRealize Automation environment has been quiesced of all activities, including but
not limited to, users ordering new virtual machines and third-party integration that might automate
the ordering of new virtual machines.
- Verify that the maintenance window is in a time period in which no backup jobs are running or
scheduled to run.
Upgrade the VxRail Management cluster in Region A

1. Log in to the VxRail Manager instance supporting Management cluster.
2. Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v xm0 1 .sf o0 1 .r ai npo le .lo c al.
3. Log in with user name [email protected] and password vsphere_admin_password.
4. Confirm that the cluster is in a healthy state prior to proceeding.
5. Select the dashboard icon from the list of management options and confirm the status is healthy with
a green checkmark.
6. Select the health tab and confirm there are not outstanding health issues with any of the hardware
components.
7. Remediate any issues before proceeding.
8. Take a Snapshot of the VxRail Manager VMs in Region A.
a Log in to the Management vCenter Server at
ht t ps: // sf o 0 1m 0 1v c 01 .sf o0 1. r ai npo le .lo c al using the vSphere Web Client.
b Navigate to Hosts and Clusters.
c Locate the VxRail Manager VM.
d Right-click and select Create a snapshot.
9. Open a Web browser and go to https://sfo01m01vxm01.sfo01.rainpole.local
10. Log in to the vSphere Web Client.
11. Select the Config Icon.
12. Click Local Upgrade.
13. In open file dialog, navigate to the upgrade composite package file, VXRAIL_COMPOSITE4.7.410-
xxxxx_for_4.7.x.zip, previously downloaded and saved locally, and then click Open to select.
14. Monitor the progress until the upload has completed.
15. Click Continue to proceed with the upgrade.
Individual upgrade tasks can be monitored by expanding the details control located below the
progress bar.
29

16. Monitor the progress until the upgrade has completed.
17. Amongst the other tasks performed during this upgrade is the update of the ESXi host NSX VIB
version. Confirm that the esx-nsxv software package has been updated from the previous release.
a Go to the VCenter UI > Host > Configure  Packages. Locate the esx-nsxv package. Verify
the version and the installed-on date have been updated.
18. If the VIB has not been upgraded, resolve that by synchronizing the host in NSX Manager. In some
cases, this may require placing the node in maintenance mode.
19. When the VxRail cluster has been upgraded and validated with the 4.7.410 release,
a Confirm that there are no outstanding errors or event messages.
b Re-enable the VxRail ESRS and support services.
c Remove any VxRail Manager VM snapshots created prior to the upgrade.
Remediate VMware tools in the Management cluster in Region A

After you upgrade the ESXi hosts in the management cluster, update VMware Tools on the virtual machines of
the management components in Region A. To remediate the management virtual machines that are running
earlier version of VMware Tools, create a baseline group so that vSphere Update Manager Download Service
on the Management vCenter Server in Region A can automatically identify them.
Remediate VMware Tools on the folders of the following management virtual machines:
Management Virtual Machines for VMware tools remediation in Region A
Cluster Name Folder Role Virtual Machine
Name
sfo01-m01-mgmt01 sfo01-m01fd-mgmt Update Manager Download sfo01umds01
Service
sfo01-m01fd-vra vRealize Automation IaaS Web vra01iws01a
Server
vra01iws01b
vRealize Automation IaaS vra01ims01a
Manager Service
vra01ims01b
vRealize Automation IaaS DEM vra01dem01a
Workers
vra01dem01b
Microsoft SQL Server vra01mssql01
sfo01-m01fd-vraias vRealize Automation IaaS Proxy sfo01ias01a
Agent
sfo01ias01b
sfo01-m01fd-bcdr Site Recovery Manager sfo01m01srm01
Procedure
2. Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v c0 1. sf o 0 1. r ain pol e. l oc al /ui /.
3. Log in using the following credentials. Log in with user name [email protected] and
password vsphere_admin_password.
4. Create a fixed baseline for VMware Tools that is packaged with ESXi 6.7 release in vSphere Update
Manager Download Service.
a From the Home menu of the vSphere Web Client, select Update Manager.
30

b In the Servers pane, select sfo01m01vc01.sfo01.rainpole.local.
c On the Manage tab, click the VMs Baselines tab.
d On the VMs Baselines page, click New Baseline Group.
e In the New Baseline Group wizard, follow the prompts and configure the following settings.
Baseline group settings
New Baseline Group Setting Value
Wizard Page
Name Name VMware Tools for VMware Validated Design 5.1
Description -
Upgrades VM Hardware Upgrades None
VMware Tools Upgrades VMware Tools Upgrade to Match Host
(Predefined)
Ready to complete - -
5. Attach the new baseline and scan the VM folder for updates against the new baseline.
a On the VMs Baselines tab, click Go to compliance view, and select the sfo01-m01-mgmt01
cluster in the inventory.
b In the Navigator, click VMs and Templates, expand the and expand the sfo01-m01dc data
center, and select sfo01-m01fd-bcdr.
c On the Update Manager tab, click Attach Baseline.
6. In the Attach Baseline or Baseline Group dialog box, under the Baseline Groups pane, select the
VMware Tools for VMware Validated Design 5.1 baseline group, and click OK.
7. After you attach the baseline, click Scan for Updates.
8. In the Scan for Updates dialog box, under Scan for Updates, select only VMware Tools upgrades,
and click OK.
9. After the scan is complete, the folder status is Non-Compliant.
10. Remediate the virtual machines and upgrade VMware Tools to ESXi 6.7 P91 release.
a On the Update Manager tab, click Remediate.

b In the Remediate wizard, follow the prompts and configure the following settings.
Remediate Wizard settings
Remediate Wizard Setting Value
Page
Select baselines Baseline groups VMware Tools for VMware Validated
Design 5.1.1
Baselines VMware Tools Upgrade to Match Host
(Predefined)
Select target objects Select target objects sfo01m01srm01
Task name sfo01-m01fd-bcdr - VMware Tools for
VMware Validated Design 5.1.1
Task description -
Apply upgrade at specific time Selected
For powered on VMs Run this action now
For powered off VMs Run this action now
For suspended VMs Run this action now
31

Remediate Wizard Setting Value
Page
Rollback Options Take a snapshot of the VMs Selected
before remediation to enable
rollback.
Snapshot Retention Do not delete snapshots
Snapshot name VMware Tools for VMware Validated
Design 5.1
Snapshot description -
Ready to complete Click Finish to begin the upgrade.
The Update Manager remediation process starts running and restarts the virtual machines.
11. After the VMware Tools upgrade is complete on each virtual machine in the folder, review the
Summary tab for each virtual machine, and verify that the VMware Tools status is Running and
version is <current>.
12. Navigate back to the sfo01-m01fd-bcdr folder and run the Scan for Updates operation again to verify
that the management virtual machines are Compliant.
Note: Because of the use of Guest Managed VMware Tools in the virtual machines, the Compliance Status
might report Incompatible for the overall folder.
13. Delete the snapshot from each virtual machine in the folder.
a From the Home menu of the vSphere Web Client, select VMs and Templates.
b In the Navigator pane, expand the sfo01m01vc01.sfo01.rainpole.local tree and select the
sfo01-m01fd-bcdr folder.
c Right-click each virtual machine and select Snapshots > Delete All Snapshots.
d In the Confirm Delete dialog box, click Yes.
14. Repeat the procedure for the other management virtual machines using their respective folders in
Region A.
Upgrade the VxRail clusters and VMware tools for the Management
cluster in Region B
In a dual-region SDDC, after you complete the upgrade of the virtual infrastructure components for the
management cluster in Region A, start the upgrade of the VxRail clusters, ESXi hosts, VMware Tools, in
Region B. Upgrading both regions enables failover and failback between Region A and Region B.
General Parameters for Update of UMDS and Management ESXi in Region B
Component Value
vSphere Web Client URL https://lax01m01vc01.lax01.rainpole.local/vsphere-client
vCenter Server lax01m01vc01.lax01.rainpole.local
Cluster lax01-m01-mgmt01
Region VxRail vCenter Server Composite

Manager Package
B lax01m01vxm01 172.17.11.65 sfo01m01vc01.sfo01.rainpole.local 4.7.410
32

Procedure
1. Log in to the VxRail Manager instance supporting Management cluster.
2. Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v xm0 1 .sf o0 1 .r ai npo le .lo c al.
4. Confirm that the cluster is in a healthy state prior to proceeding.
a Select the dashboard icon from the list of management options and confirm the status is healthy
with a green checkmark.
b Select the health tab and confirm there are not outstanding health issues with any of the
hardware components.
c Remediate any issues before proceeding.
5. Take a Snapshot of the VxRail Manager VMs in Region A
a Log in to the Management vCenter Server at
ht t ps: // sf o 0 1m 0 1v c 01 .sf o0 1. r ai npo le .lo c al using the vSphere Web Client.
b Navigate to Hosts and Clusters.
c Locate the VxRail Manager VM.
d Right-click and select Create a snapshot.
6. Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v xm0 1 .sf o0 1 .r ai npo le .lo c al
7. Log in to the vSphere Web Client.
8. Select the Config Icon.
9. Click Local Upgrade.
10. In open file dialog, navigate to the upgrade composite package file, VXRAIL_COMPOSITE4.7.410-
xxxxx_for_4.7.x.zip, previously downloaded and saved locally, and then click Open to select.
11. Monitor the progress until the upload has completed.
12. Click Continue to proceed with the upgrade.
Individual upgrade tasks can be monitored by expanding the details control located below the progress
bar.
13. Monitor the progress until the upgrade has completed.
14. When the VxRail cluster has been upgraded and validated with the 4.7.410 release,
a Confirm there are no outstanding errors or event messages
b Re-enable the VxRail ESRS and support services.
c Remove any VxRail Manager VM snapshots created prior to the upgrade.
Upgrade the components for the Shared Edge and Compute clusters
After you upgrade the components that support the management cluster, upgrade the components for the
shared edge and compute clusters to complete the upgrade of the SDDC virtual infrastructure layer.
Global post-upgrade configuration of the virtual infrastructure layer

After you upgrade the virtual infrastructure layer, perform global post-upgrade configuration according to the
dependencies between these components and to align your environment to the guidance in this VVD.
33

Set SDDC deployment details on the Management vCenter Server in
Region A
Update the identity of your SDDC deployment on vCenter Server. Use this identity as a label in tools for
automated SDDC deployment.
Procedure
2. Open a Web browser and go to ht t p s: / /sf o0 1 m0 1 v c0 1. sf o 0 1. r ain pol e. l oc al /v sph e r e-
cl ie nt /.
4. From the vSphere Client menu, select Global Inventory Lists.
5. Click vCenter Servers.
6. Click the sfo01m01vc01.sfo01.rainpole.local vCenter Server object and click the Configure tab in
the center pane.
7. Under the Settings pane, click Advanced Settings and click Edit.
8. In the Edit Advanced vCenter Server Settings dialog box, configure the following properties and click
OK.
a Search for the c o n f i g . S D DC .D ep l o ye d . Ver s i o n property and change its value from 5. 1 to
5. 1. 1.
b Add the config.SDDC.Deployed.WorkloadDomain and
config.SDDC.Deployed.InstanceId properties.
SDDC properties
Name Value 1
config.SDDC.Deployed.Type VVD-VxRail
config.SDDC.Deployed.Flavor Standard
config.SDDC.Deployed.Version 5.1.1
config.SDDC.Deployed.WorkloadDomain Management
config.SDDC.Deployed.Method Automation
config.SDDC.Deployed.InstanceId unique_identifier*
Note: To generate a unique identifier, use the Online UUID Generator website https://www.uuidgenerator.net/
and copy/paste the UUID in to the config.SDDC.Deployed.InstanceId value. The Online UUID Generator is a
universally unique identifier that generates random numbers using a secure random number generator.
c Click OK to close the window.
Set SDDC deployment details on the Shared Edge and Compute

vCenter server in Region A
Update the identity of your SDDC deployment on the Compute vCenter Server in Region A. You can use this
identity as a label in tools for automated SDDC deployment.
34

Procedure
1. Log in to the Compute vCenter Server by using the vSphere Client.
2. Open a Web browser and go to ht t p s: / /sf o0 1w 01v c0 1 .sf o0 1. r ai npo le .lo ca l/ ui /.
6. Click the sfo01w01vc01.sfo01.rainpole.local vCenter Server object and click the Configure tab in
the central pane.
7. Under the Settings pane, click Advanced Settings and click the Edit button.
OK.
a Search for the c o nf i g .S D DC .D ep l o ye d . Ver s i o n property and change its value from 5. 1 to
5. 1. 1.
SDDC Deployed properties
Name Value
config.SDDC.Deployed.WorkloadDomain SharedEdgeAndCompute
Note * Use the unique_identifier you generated for the Management vCenter Server. See Set SDDC
Deployment Details on the Management vCenter Server in in Region A.
9. Click OK to close the window.
Post-upgrade configuration of the virtual infrastructure components

in Region B
After you upgrade all virtual infrastructure components in your environment, perform global post-upgrade
configuration according to the dependencies between the components in Region B and to the guidance in this
validated design.
Update the SDDC deployment details on the Region B Management vCenter

Server
Update the identity of your SDDC deployment on the Management vCenter Server in Region B. Use this
identity as a label in tools for automated SDDC deployment.
35

Procedure
1. Log in to the Management vCenter Server by using the vSphere Client.
2. Open a Web browser and go to ht t p s: / /l a x0 1m 0 1 v c0 1. la x 01 . ra inp ol e. l oc al /ui.
6. Click the lax01m01vc01.lax01.rainpole.local vCenter Server object and click the Configure tab in
the central pane.
OK.
9. Search for the c o nf i g .S D DC .D ep l o ye d . Ver s i o n property and change its value from 5. 1 to
5. 1. 1.
10. Add the config.SDDC.Deployed.WorkloadDomain and
SDDC Deployed settings
Name Value 1
config.SDDC.Deployed.Version 5.1
config.SDDC.Deployed.WorkloadDomain Management
Set SDDC deployment details on the Compute vCenter Server in Region B

Update the identity of your SDDC deployment on the Compute vCenter Server in Region B. Use this identity as
a label in tools for automated SDDC deployment.
Procedure
1. Log in to the Compute vCenter Server by using the vSphere Client.
2. Open a Web browser and go to ht t p s: / /l a x0 1w 01v c0 1 .l ax 0 1. r ain pol e .lo ca l/ ui /.
6. Click the lax01w01vc01.lax01.rainpole.local vCenter Server object and click the Configure tab in
the central pane.
OK.
36

a Search for the c o n f i g . S D DC .D ep l o ye d . Ver s i o n property and change its value from 5.1 to
5. 1. 1.
SDDC Deployed settings
Name Value
config.SDDC.Deployed.WorkloadDomain SharedEdgeAndCompute
Note: * Use the unique_identifier you generated for the Management vCenter Server. See Set SDDC
Deployment Details on the Management vCenter Server in Region B.
9. Click OK to close the window.
37

6 SDDC Startup and Shutdown
When you perform patch, upgrade, recovery, or failover of the SDDC management applications, make sure that
you start up and shut down the management virtual machines according to a predefined order.
Shutdown order of the Management virtual machines

Shut down the virtual machines of the SDDC management stack by following a strict order to avoid data loss
and faults in the components.
Before you begin:

• Verify that virtual machines are not running on snapshots.
• Ensure that verified backups of all management and tenant virtual machines are available.
• If a data protection (VADP) based backup solution is running on the management clusters, verify that the
solution is properly shutdown following the vendor guidance.
• If the hosts in a vSAN cluster are to be shut down, appropriately shut down the tenant workloads in the
shared edge and compute cluster.
Shutting down the ESXi hosts in the vSAN clusters:

Refer to VMware Knowledge Base article 2142676 for information on preparing and shutting down ESXi hosts
in vSAN clusters.
Shutting down the management virtual machines:

• Shut down the virtual machines of the SDDC management stack in the shutdown order provided in the
following table.
• Verify that the console of the virtual machine and its services are completely shut down before moving to
the next virtual machine.
Note: The vCenter Server instances, NSX load balancers for the Platform Services Controllers, the Platform
Services Controllers, and the management clusters are the last virtual machines to be shut down.
Virtual machine shut-down order
Virtual Machine shut-down order Virtual Machine Name in Region B Shutdown

Virtual Machine Name in Region A Order
vRealize Suite Lifecycle Manager - 1
Total Number of VMs (1)
vrslcm01svr01a - 1
vRealize Log Insight vRealize Log Insight 2
Total Number of VMs (3) Total Number of VMs (3)
sfo01vrli01c lax01vrli01c 1
sfo01vrli01b lax01vrli01b 1
sfo01vrli01a lax01vrli01a 2
vRealize Operations Manager vRealize Operations Manager 2
sfo01vropsc01b lax01vropsc01b 1
38

sfo01vropsc01a lax01vropsc01a 1
vrops01svr01c - 2
vrops01svr01b - 3
vrops01svr01a - 4
vRealize Business for Cloud Realize Business for Cloud 3
sfo01vrbc01 lax01vrbc01 1
vrb01svr01 - 2
vRealize Automation vRealize Automation 4
vra01dem01b - 1
vra01dem01a - 1
sfo01ias01b lax01ias01b 1
sfo01ias01a lax01ias01a 1
vra01ims01b - 2
vra01ims01a - 2
vra01iws01b - 3
vra01iws01a - 4
vra01svr01c - 5
vra01svr01b - 5
vra01svr01a - 5
vra01mssql01 - 6
Site Recovery Manager and Site Recovery Manager and 5
vSphere Replication vSphere Replication
sfo01m01vrms01 lax01m01vrms01 1
sfo01m01srm01 lax01m01srm01 2
Update Manager Download Update Manager Download 5
Service (UMDS) Service (UMDS)
sfo01umds01 lax01umds01 N/A for VVD on
VxRail design
Core Stack Core Stack 6
sfo01m01lb01 (0,1) lax01m01lb01 (0,1) 1
sfo01m01udlr01 (0,1) - 1
sfo01m01esg01 lax01m01esg01 1
sfo01w01udlr01 (0,1) - 1
sfo01w01dlr01 (0,1) lax01w01dlr01 (0,1) 1
sfo01w01esg01 lax01w01esg01 1
sfo01m01nsx01 lax01m01nsx01 2
sfo01w01nsx01 lax01w01nsx01 2
39

sfo01m01nsxc01 - 3
sfo01m01nsxc02 - 3
sfo01m01nsxc03 - 3
sfo01w01nsxc01 - 3
sfo01w01nsxc02 - 3
sfo01w01nsxc03 - 3
sfo01m01vc01 lax01m01vc01 4
sfo01w01vc01 lax01w01vc01 4
sfo01psc01 (0,1) lax01psc01 (0,1) 5
sfo01w01psc01 lax01w01psc01 6
sfo01m01psc01 lax01m01psc01 6
Start-up order of the Management Virtual Machines

Start up the virtual machines of the SDDC management stack by following a strict order to guarantee the
faultless operation of and the integration between the components.
Before you begin

Verify that external dependencies for the SDDC, such as Active Directory, DNS, NTP, SMTP, and FTP/SFTP
are available.
Start up the ESXi hosts in the vSAN clusters

If the vSAN clusters are shut down, refer to VMware Knowledge Base article 2142676 for information on
starting up hosts and exiting maintenance mode.
Start up the management virtual machines:

1. Start up the virtual machines in the start-up order provided in the following table.
2. Verify that the console of the VM is available and all services of the VM are up, before proceeding
with the next virtual machine.
3. Refer to VMware Knowledge Base article 2142676 for information on verifying the health of the vSAN
clusters before starting up tenant workloads.
4. If a data protection (VADP) based backup solution is deployed on the management cluster, verify that
the solution is properly started and operational, following the vendor guidance.
Virtual Machine start-up order
Virtual Machine in Region A Virtual Machine in Region B Start-up Order

Core Stack Core Stack 1
Number of VMs (26) Number of VMs (16)
sfo01m01psc01 lax01m01psc01 1
sfo01w01psc01 lax01w01psc01 1
sfo01psc01 (0,1) lax01psc01 (0,1) 2
sfo01m01vc01 lax01m01vc01 3
40

sfo01w01vc01 lax01w01vc01 3
sfo01m01nsx01 lax01m01nsx01 4
sfo01w01nsx01 lax01w01nsx01 4
sfo01m01nsxc01 - 5
sfo01m01nsxc02 - 5
sfo01m01nsxc03 - 5
sfo01w01nsxc01 - 5
sfo01w01nsxc02 - 5
sfo01w01nsxc03 - 5
sfo01m01lb01 (0,1) lax01m01lb01 (0,1) 6
sfo01m01udlr01 (0,1) - 6
sfo01w01udlr01 (0,1) - 6
sfo01w01dlr01 (0,1) lax01w01dlr01(0,1) 6
Update Manager Download Service Update Manager Download 2
(UMDS) Service (UMDS)
sfo01umds01 lax01umds01 1
Site Recovery Manager and vSphere Site Recovery Manager and 2
Replication vSphere Replication
sfo01m01vrms01 lax01m01vrms01 1
sfo01m01srm01 lax01m01srm01 1
vRealize Automation vRealize Automation 3
vra01mssql01 - 1
vra01svr01a - 2
vra01svr01b - 2
vra01svr01c - 2
vra01iws01a - 3
vra01iws01b - 4
vra01ims01a - 5
vra01ims01b - 6
sfo01ias01a lax01ias01a 7
sfo01ias01b lax01ias01b 7
vra01dem01a - 7
vra01dem01b - 7
vRealize Business for Cloud vRealize Business for Cloud 4
vrb01svr01 - 1
sfo01vrbc01 lax01vrbc01 2
41

vRealize Operations vRealize Operations Manager 5
Manager Total Number of VMs (5) Total Number of VMs (2)
vrops01svr01a - 1
vrops01svr01b - 2
vrops01svr01c - 3
sfo01vropsc01a lax01vropsc01a 4
sfo01vropsc01b lax01vropsc01b 4
vRealize Log Insight vRealize Log Insight 5
sfo01vrli01a lax01vrli01a 1
sfo01vrli01b lax01vrli01b 2
sfo01vrli01c lax01vrli01c 2
vRealize Suite Lifecycle Manager vRealize Suite Lifecycle 6
Total Number of VMs (1) Manager
Total Number of VMs (0)
vrslcm01svr01a - 1
42

H18075 - VVD 5.1.1 Upgrade Guide

Uploaded by

Copyright:

Available Formats

H18075 - VVD 5.1.1 Upgrade Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

H18075 - VVD 5.1.1 Upgrade Guide

Uploaded by

Copyright:

Available Formats

VMware Validated Design for SDDC v5.1.

Dell Customer Communication - Confidential

Dell Customer Communication - Confidential

Dell Customer Communication - Confidential

Dell Customer Communication - Confidential

Required VMware software

Required VxRail software

Before you apply this guidance

Dell Customer Communication - Confidential

Upgrades and updates that are validated by VVD

Updates that are not validated by VVD

Upgrade paths and application upgrade sequence

• Isolates the VMware and VxRail components at functional layers.

Dell Customer Communication - Confidential

6† Determined vSphere Storage APIs for Business Continuity

Dell Customer Communication - Confidential

vRealize Log Insight Agent 4.8 4.8 N/A

vRealize Operations Manager 7.5 7.5 N/A

Cloud vRealize Business for Cloud 7.6 7.6 N/A

Backup solution based on VMware Compatible Compatible Vendor

vCenter Server 6.7 Update 2 6.7 P01 Upgrade

VxRail Virtual ESXi 6.7 Update 2 6.7 P01 Upgrade

General prerequisites for the SDDC upgrade

Dell Customer Communication - Confidential

Upgrade the content packs on vRealize Log Insight in Region A

Content Pack Version

vRealize Log Insight Content Pack for vRealize Orchestrator 2.10

vRealize Log Insight Content Pack for vRealize Business 1.53

vRealize Log Insight Content Pack for Linux 2.0.1

vRealize Log Insight Content Pack for vSAN 2.2

Dell Customer Communication - Confidential

a On the main navigation bar, click Administration.

Dell Customer Communication - Confidential

Order Component Sub-Component

Review and update vSphere storage APIs – Data Protection based

Dell Customer Communication - Confidential

Order Component Sub-Component

Upgrade the NSX components for the Management, Shared Edge

Dell Customer Communication - Confidential

Dell Customer Communication - Confidential

3. Reboot the NSX Manager appliance to apply the log clean-up.

Upgrade the NSX Manager instances

Order Region NSX Manager NSX Appliance URL vCenter Server

Dell Customer Communication - Confidential

a Open a Web browser and go to ht t p s: / /sf o0 1m 0 1n sx 0 1. sf o 0 1. r ain pol e. l oc al.

a Open a Web browser and go to ht t p s: / /sf o0 1m 0 1n sx 0 1. sf o 0 1. r ain pol e. l oc al.

Setting Expected Value

8. Log in to vCenter Server by using the vSphere Web Client.

a Open a Web browser and go

a Click Menu > Administration.

Dell Customer Communication - Confidential

Upgrade the NSX Controller clusters

Order Region NSX Manager NSX Manager IP NSX Controller IP

a Open a Web browser and go

Dell Customer Communication - Confidential

Status Controller Upgrade Stage

Setting Expected Value

Upgrade the NSX components on the ESXi hosts

Dell Customer Communication - Confidential