VMware Validated Design for SDDC v5.01 on Dell EMC VxRail · 2020-03-05 · VVD on VxRail 5.0.1 Upgrade Guide 1 Dell Customer Communication - Confidential VMware Validated Design

VVD on VxRail 5.0.1 Upgrade Guide 1 Dell Customer Communication - Confidential Dell Customer Communication - Confidential

VMware Validated Design for SDDC v5.01 on Dell EMC VxRail

Upgrade Guide

Abstract This guide provides information for upgrading VVD on VxRail from VVD 4.3 to VVD 5.01. The document is based on VMware’s VVD 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 4.3 VVD on VxRail Guide.

H17942

September 2019

2 VVD on VxRail 5.0.1 Upgrade Guide Dell Customer Communication - Confidential 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 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. [9/10/2019] [Deployment Guide] [Document ID]


Table of contents 1 About VMware Validated Design Upgrade .......................................................................................... 8

Intended audience ..................................................................................................................... 8

Required VMware software ....................................................................................................... 8

Required VxRail software .......................................................................................................... 8

Before you apply this guidance ................................................................................................. 8

2 SDDC Upgrade Overview ................................................................................................................... 9

Upgrade policy ........................................................................................................................... 9

Upgrade paths and application upgrade sequence ................................................................... 9

VMware software versions in the upgrade .............................................................................. 11

General prerequisites for the SDDC upgrade ......................................................................... 12

Best Practices in SDDC upgrades .......................................................................................... 12

Planning for the SDDC upgrade .............................................................................................. 12

Considerations for an upgrade failure ..................................................................................... 13

Post-upgrade operations ......................................................................................................... 13

3 Upgrade the Operations Management layer ..................................................................................... 14

Upgrade Overview ................................................................................................................... 14

Upgrade vRealize Suite Lifecycle Manager ............................................................................ 14

Prerequisites ............................................................................................................................ 14

Take a snapshot of the vRealize Suite Lifecycle Manager Virtual Appliance ......................... 15

Pause the replication of the vRealize Suite Lifecycle Manager virtual appliance ................... 16

Upgrade the vRealize Suite Lifecycle Manager Virtual Appliance .......................................... 16

Install the patch for vRealize Suite Lifecycle Manager ............................................................ 18

Delete the snapshots of the vRealize Suite Lifecycle Manager virtual appliance ................... 18

Resume the replication of the vRealize Suite Lifecycle Manager virtual appliance ................ 19

Upgrade vRealize Log Insight Using vRealize Suite Lifecycle Manager................................. 19

Download vRealize Log Insight in vRealize Suite Lifecycle Manager ..................................... 21

Upgrade vRealize Log Insight in Region A .............................................................................. 21

Upgrade the vRealize Log Insight cluster in Region A using vRealize Suite Lifecycle Manager 22

Upgrade the content packs on vRealize Log Insight in Region A ........................................... 23

Upgrade the vRealize Log Insight Agents on the Windows Server virtual machines in Region A 23

Delete the snapshots of the vRealize Log Insight virtual appliances in Region A .................. 25

Upgrade vRealize Log Insight in Region B .............................................................................. 26


Verify the Event Forwarding Filter configuration in Region A and Region B ........................... 27

Upgrade vRealize Operations Manager using vRealize Suite Lifecycle Manager .................. 28

Take the vRealize Operations Manager Analytics cluster offline and take snapshots............ 29

Download vRealize Operations Manager in vRealize Suite Lifecycle Manager ..................... 31

Pause the Replication of vRealize Operations Manager ......................................................... 31

Upgrade vRealize Operations Manager Using vRealize Suite Lifecycle Manager ................. 32

Update vRealize Operations Manager License Key ............................................................... 33

Upgrade the Management Packs for NSX for vSphere and for Site Recovery Manager in vRealize Operations Manager ........................................................................................................... 33

Reinstall the Management Pack for Storage Devices in vRealize Operations Manager ........ 34

Add Storage Devices Adapters in vRealize Operations Manager........................................... 35

Resume the replication of vRealize Operations Manager ....................................................... 37

Delete the Snapshots of the vRealize Operations Manager Virtual Appliances ..................... 37

4 Upgrade the Cloud Management Layer ............................................................................................ 39

Upgrade vRealize Business using vRealize Suite Lifecycle Manager .................................... 39

Take the vRealize Business Virtual Machines Offline and Take Snapshots ........................... 39

Download vRealize Business in vRealize Suite Lifecycle Manager ........................................ 41

Pause the Replication of vRealize Business ........................................................................... 41

Upgrade vRealize Business Using vRealize Suite Lifecycle Manager.................................... 42

Delete the snapshots of the vRealize Business Virtual Machines .......................................... 43

Resume the Replication of vRealize Business ........................................................................ 44

Upgrade vRealize Automation using vRealize Suite Lifecycle Manager................................. 44

Set the vRealize Automation Database Replication Mode to Asynchronous .......................... 47

Direct Traffic to the Primary Nodes and Disable Health Monitoring for vRealize Automation on the Load Balancer in Region A.......................................................................................................... 47

Take the vRealize Automation Virtual Machines Offline and Take Snapshots ....................... 49

Download vRealize Automation in vRealize Suite Lifecycle Manager .................................... 50

Pause the replication of vRealize Automation ......................................................................... 51

Upgrade vRealize Automation using vRealize Suite Lifecycle Manager................................. 51

Configure the embedded vRealize Orchestrator service in the vRealize Automation appliances in Region A ...................................................................................................................... 52

Re-Enable traffic to the secondary nodes and Health Monitoring for vRealize Automation on the Load Balancer ............................................................................................................................. 53

Post-upgrade configuration of the Cloud Management Layer ................................................. 54

Set the vRealize Automation database replication mode to synchronous .............................. 54

Run test connection and verify the upgraded endpoints ......................................................... 55

Run NSX Network and Security Inventory Data Collection ..................................................... 55


Enable Automatic Manager Service Failover .......................................................................... 57

Enable vRealize Orchestrator Multi-Tenancy .......................................................................... 58

Delete the snapshots of the vRealize Automation virtual machines ....................................... 58

Resume the replication of vRealize Automation...................................................................... 59

Save a baseline for environment configuration drift of vRealize products in vRealize Suite Lifecycle Manager ............................................................................................................................. 60

Re-configure the vRealize Log Insight agent on vRealize Business ....................................... 61

Configure the vRealize Log Insight Linux agent on vRealize business in Region B ............... 62

Delete and re-create the agent groups for vRealize bBusiness in Region A and Region B ... 63

5 Upgrade the Business Continuity layer ............................................................................................. 65

Review and update vSphere Storage APIs – Data Protection based backup solution ........... 65

Prerequisites ............................................................................................................................ 65

What to do next ....................................................................................................................... 65

Upgrade disaster recovery components .................................................................................. 65

Prerequisites ............................................................................................................................ 66

Upgrade the vSphere replication virtual appliance in Region A .............................................. 66

Deploy the new vSphere Replication virtual appliance in Region A ........................................ 67

Delete the virtual machine of the old vSphere Replication instance in Region A ................... 71

Upgrade Site Recovery Manager in Region A ........................................................................ 72

Upgrade the vSphere replication in Region B ......................................................................... 74

Deploy the new vSphere Replication virtual appliance in Region B ........................................ 76

Upgrade the vSphere Replication virtual appliance in Region B ............................................. 78

Delete the virtual machine of the old vSphere replication instance in Region B ..................... 79

Upgrade Site Recovery Manager in Region B ........................................................................ 80

Reconnect the vSphere replication and Site Recovery Manager instances between the protected and the recovery sites ....................................................................................................... 82

6 Upgrade the virtual infrastructure layer ............................................................................................. 85

Upgrade the NSX components for the Management, Shared Edge and Compute Clusters .. 85

Upgrade the NSX Manager instances ..................................................................................... 87

Upgrade the NSX controller clusters ....................................................................................... 89

Upgrade the NSX components on the ESXi hosts .................................................................. 91

Upgrade the NSX Edge instances ........................................................................................... 93

Upgrade the Management Cluster .......................................................................................... 96

Take snapshots of the vCenter Server and Platform Services Controller instances in Region A and Region B ................................................................................................................................. 97

Upgrade the Platform Services Controller for the Management Cluster in Region A ............. 98


Upgrade vCenter Server for the Management Cluster in Region A ...................................... 102

Upgrade Platform Services Controller instances in Region B ............................................... 105

Upgrade vCenter Server for the Management Cluster in Region B ...................................... 109

Delete the Obsolete vCenter Server and Platform Services Controllers Appliances in Region A and Region B ............................................................................................................................... 111

Upgrade the VxRail Management Cluster ............................................................................. 112

Upgrade the VxRail Clusters and VMware Tools for the Management Cluster in Region B 117

Upgrade the components for the Shared Edge and Compute Clusters ................................ 118

Upgrade vCenter Server for the Shared Edge and Compute Cluster in Region A and Region B 118

Upgrade vCenter Server for the Shared Edge and Compute Cluster in Region B ............... 122

Perform the VxRail Cluster Upgrade of the Shared Edge and Compute Clusters ................ 125

Global Post-Upgrade Configuration of the Virtual Infrastructure Layer ................................. 127

Add vCenter Server and Platform Services Controller instances to Virtual Machine DRS Groups in Region A and Region B .................................................................................................. 127

Post-upgrade configuration of the virtual infrastructure components in Region A ................ 128

Set SDDC Deployment Details on the Management vCenter Server in Region A ............... 128

Set SDDC deployment details on the Shared Edge and Compute vCenter server in Region A 129

Procedure .............................................................................................................................. 129

Post-upgrade configuration of the Virtual Infrastructure components in Region B ............... 130

7 SDDC Startup and Shutdown.......................................................................................................... 133

Shutdown Order of the Management Virtual Machines ........................................................ 133

Startup order of the Management Virtual Machines .............................................................. 135

Before you begin ................................................................................................................... 135

Starting up the ESXi hosts in the vSAN clusters ................................................................... 135

Starting up the management virtual machines: ..................................................................... 135



1 About VMware Validated Design Upgrade This guide is written for VVD on VxRail upgrades from VVD 4.3 to VVD 5.01. The document is based on VMware’s VVD 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 4.3 VVD on VxRail Guide.

Before you start an upgrade of your SDDC, make sure that you are familiar with the update or upgrade planning guidance that is part of this guide.

Intended audience 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 for more information about supported product versions.

Required VxRail software The VxRail Cluster upgrade from VVD 4.3 to VVD 5.0.1 requires two VxRail releases:

• 4.7.001 – This is a temporary release, so the latest supported version is recommended.

• 4.7.111 or later – This was the version qualified for VVD 5.0.1. It also aligned to the VVD BOM. Subsequent releases can be used as long as they fall within the 4.7.100 family.

Before you apply this guidance The sequence of the documentation of VMware Validated Design 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 acquainted with the following:

VxRail Installation and Administration

• VMware Validated Design Architecture and Design

• VMware Validated Design Planning and Preparation

https://docs.vmware.com/en/VMware-Validated-Design/services/documentation-map/GUID-EE7CF703-7DE5-4478-9AEF-98F51812465D.html

https://docs.vmware.com/en/VMware-Validated-Design/services/documentation-map/GUID-EE7CF703-7DE5-4478-9AEF-98F51812465D.html


2 SDDC Upgrade Overview VMware Validated Designs on VxRail reduce risk and time in performing updates and upgrades by validating the procedures and software versions associated with each VMware Validated Design release. Consider the policy, upgrade paths, system requirements and upgrade sequence for a successful SDDC upgrade.

Upgrade policy VMware Validated Design provides guidance to update and upgrade the SDDC management products according to an upgrade validation policy. Dell EMC has further validated these procedures and adjusted sections for the VVD on VxRail designs.

Updates that are validated by VMware Validated Design VMware Validated Design 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 the interoperability, and introduces new features, functionality, and bug fixes.

Update Does not impact the SDDC design and implementation, includes bug fixes, VxRail patches, and ensures interoperability.

The upgrade of a VMware Validated Design 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 VMware Validated Design Scalability and functional tests for individual patches, express patches, or hot fixes are not typically performed against a VMware Validated Design.

Upgrade paths and application upgrade sequence You must follow the SDDC upgrade path and sequences for this VMware Validated Design.

Upgrade paths You must run version 4.3 of this VMware Validated Design before you upgrade to version 5.0.1.

Table 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


Upgrade Sequence Тhe progressive and granular upgrade process of this VMware Validated Design 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, minimizing the number of product champions required during maintenance windows

• Reduces the overall upgrade window 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.

Table 2. Upgrade Sequence of This VMware Validated Design

Order Upgraded or Updated

Component Sub-Component (in Order)

SDDC Layer

1 Yes vRealize Suite Lifecycle Manager - Operations Management 2 Yes vRealize Log Insight vRealize Log Insight

Appliances vRealize Log Insight Agents

3 Yes vRealize Operations Manager - 4 Yes vRealize Business for Cloud vRealize Business

Appliance Cloud Management

vRealize Business Data Collectors

5 Yes vRealize Automation vRealize Automation Appliances vRealize Orchestrator (Embedded) vRealize Automation IaaS Components

6† Determined by Organization

vSphere Storage APIs for Data Protection-based Backup Solution

- Business Continuity

7 Yes vSphere Replication - Site Recovery Manager -

8 Yes NSX Data Center for vSphere

NSX Manager Instances

Virtual Infrastructure – Networking

NSX Controller Instances NSX Networking Fabric NSX Edges

9 Yes Platform Services Controller - Virtual Infrastructure - Management vCenter Server -


Order Upgraded or Updated

Component Sub-Component (in Order)

SDDC Layer

vSphere Update Manager Download Service

-

VMware Tools -

10 Yes ESXi, Firmware, BIOS - VxRail Manager Lifecycle Upgrade management Cluster

vSAN -

11 Yes Platform Services Controller - Virtual Infrastructure – Shared Edge Compute vCenter Server -

12 Yes ESXi, Firmware, BIOS - VxRail Lifecycle Upgrade Shared Edge Compute Cluster vSAN -

Note: VMware Validated Design requires a compatible and supported backup solution. Refer to your backup solution documentation for the interoperability with the vSphere version 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 VMware Validated Design.

VMware software versions in the upgrade Upgrade each SDDC management product to the specific version according to the software bill of materials in this VMware Validated Design.

Table 3. Upgrade from VMware Validated Design for Software-Defined Data Center 4.3 to VMware Validated Design for Software-Defined Data Center 5.0.1.

SDDC Layer Product Name Product Version in VVD 4.3

Product Version in VVD5.0

Operation Type

Operations Management

vRealize Suite Lifecycle Manager 1.2 2.1.0 Patch 1 Upgrade

vRealize Log Insight 4.6 4.7 Upgrade

vRealize Log Insight Agent 4.6 4.7 Upgrade

vRealize Operations Manager 6.7 7.0 Upgrade

Cloud Management

vRealize Business for Cloud 7.4 7.5 Upgrade

vRealize Automation with Embedded vRealize Orchestrator

7.4 7.5 Upgrade

Business Continuity

Site Recovery Manager 6.5.1.1 8.1.1 Upgrade

vSphere Replication 6.5.1.3 8.1.1 Upgrade

Backup solution based on VMware vSphere Storage APIs for Data Protection

Compatible Version

Compatible Version

Vendor Specific

Virtual Infrastructure

NSX Data Center for vSphere 6.4.1 6.4.4 Update

Platform Services Controller 6.5 Update 2 6.7 Update 1 Upgrade

vCenter Server 6.5 Update 2 6.7 Update 1 Upgrade


SDDC Layer Product Name Product Version in VVD 4.3

Product Version in VVD5.0

Operation Type

VxRail Virtual Infrastructure 4.7.111

ESXi 6.5 Update 2 6.7 Update 1 Upgrade

vSAN 6.6.1 Update 2 6.7 Update 1 Upgrade

For information about all components included in the VMware Validated Design 4.3 and VMware Validated Design 5.0.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, verify that your existing VMware Validated Design environment meets the following prerequisites:

• The environment implementation exactly follows the software bill of materials for the previous release.

• Your VMware vSphere Storage APIs for Data Protection-based backup solution has been certified with vSphere 6.7 Update 1. For more information, contact your backup solution vendor.

Review the following:

• The release notes for each product version included in the updated software bill of materials.

• 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.

• All custom integrations developed and deployed externally from the VMware Validated Design framework to ensure compatibility with product versions in the updated software bill of materials, such as vRealize Orchestrator workflows.

• All third-party product integrations in your environment to ensure compatibility with the product versions in the updated software bill of materials.

• The System Health of all VxRail clusters within VxRail Manager and address any alarms or error conditions before proceeding.

Best Practices in SDDC upgrades Prepare for an upgrade and perform post-upgrade activities to verify the operational state of the SDDC.

Planning for the SDDC upgrade • Schedule a maintenance window that is suitable for your organization and tenants.

• Allocate time in your maintenance window to run operational verification tests. For example, critical business functions, integration validations, and system performance. Add time to respond to incidents or errors without exceeding your maintenance window.


• Plan for any potential impact to tenant workloads during an upgrade. If capacity allows, use vSphere vMotion to temporarily migrate tenant workloads to other compute clusters during an upgrade.

• Communicate the upgrade to your organization and tenants.

• Communicate the upgrade to your Technical Account Manager and Global Support Service representative, as applicable.

• Perform and verify the backups and snapshots for the SDDC management components.

• Perform snapshot maintenance on the management virtual machines and appliances to minimize snapshot overhead during the upgrade of each SDDC functional layer. Guidance for each layer discusses the preparational use of snapshots.

Considerations for an upgrade failure Collect the product support bundles for the failed product upgrade and contact VMware Technical Support.

Roll back the component upgrade If a component upgrade fails, the order of operations ensures backward compatibility and interoperability are maintained between layers. As long as snapshots are being created per the document guidance, you can roll back to a previous version of the components within a layer.

Important

• The rollback of ESXi and vSAN is not supported.

• The rollback of an SDDC after more than one layer has been successfully upgraded is not supported.

Post-upgrade operations After completing an upgrade, consider the following practices:

• Verify the business functionality, integration, and system performance. For more information, see the VMware Validated Design Operational Verification documentation.

• Conduct an upgrade retrospective discussion. Document the areas for a process improvement and incorporate them in the next upgrade.


3 Upgrade the Operations Management layer Start by upgrading vRealize Life Cycle Manager (vRLCM) then use vRLCM to upgrade the operations management layer. The vRealize Operations Manager and vRealize Log Insight components continue to monitor existing and upgraded components using the latest capabilities of the new release. In addition, perform post-upgrade configurations procedures for each upgraded component.

Table 4. Upgrade Sequence for the Operations Management Layer

Order Component Sub-Component 1 vRealize Suite Lifecycle Manager -

2 vRealize Log Insight vRealize Log Insight Appliances

vRealize Log Insight Agents

Post-upgrade Configuration of vRealize Log Insight -

3 vRealize Operations Manager -

Post-upgrade Configuration of vRealize Operations Manager -

Upgrade Overview Upgrade vRealize Suite Lifecycle Manager

Upgrade vRealize Log Insight Using vRealize Suite Lifecycle Manager

Upgrade vRealize Operations Manager using vRealize Suite Lifecycle Manager

Upgrade vRealize Suite Lifecycle Manager In this release of the VMware Validated Design, the upgrade of vRealize Suite Lifecycle Manager is a two-step process. The first task is to upgrade vRealize Suite Lifecycle Manager, then patch it by uploading and installing a required patch.

Table 5. vRealize Suite Lifecycle Manager Node in the SDDC

Region Role IP Address Fully Qualified Domain Name

Region A vRealize Suite Lifecycle Manager Virtual Appliance

192.168.11.20 vrslcm01svr01a.rainpole.local

Prerequisites • Verify that there are sufficient privileges in the vSphere Web Client to pause the

replication task of vRealize Suite Lifecycle Manager.

• Verify that there is a minimum of 3 GB of disk space available on the root/file system of the vRealize Suite Lifecycle Manager virtual appliance.


• Download the vrlcm-2.1-PATCH1.patch file of vRealize Suite Lifecycle Manager from My VMware Product Patches to a Windows host that has access to your SDDC. See VMware Knowledge Base article KB 65098.

• Review the release notes of the vRealize Suite Lifecycle Manager version in this validated design.

Procedure Upgrade the vRealize Suite Lifecycle Manager appliance by using an upgrade ISO file.

Install the patch for vRealize Suite Lifecycle Manager.

After you upgrade vRealize Suite Lifecycle Manager, install the required patch on the virtual appliance.

Delete the snapshots of the vRealize Suite Lifecycle Manager virtual appliance. After you upgrade vRealize Suite Lifecycle Manager, delete the virtual appliance snapshot.

Resume the replication of the vRealize Suite Lifecycle Manager virtual appliance After the upgrade of vRealize Suite Lifecycle Manager, resume the paused replication task for the vRealize Suite Lifecycle Manager virtual appliance, to support a failover to Region B.

What to do next Verify that vRealize Suite Lifecycle Manager is operational after the upgrade. See Verification of vRealize Suite Lifecycle Manager in the VMware Validated Design Operational Verification documentation.

Take a snapshot of the vRealize Suite Lifecycle Manager Virtual Appliance

The snapshot is used in the event you need to roll vRealize Suite Lifecycle Manager back to a previous state.

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

a Open a Web browser and go

to h t tps : / /s fo01m01vc01.s fo01.ra inpole. loca l /vsphere-c l ient / .

b Log in with: username: [email protected] and password: vsphere_admin_password.

From the Home menu, select VMs and Templates.

In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01-mgmt01.

Right-click vrslcm01svr01a and select Snapshots > Take Snapshot.

In the Take VM Snapshot dialog box, enter the following settings and click OK.

https://my.vmware.com/group/vmware/patch

https://kb.vmware.com/s/article/65098

https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client/


Setting Value Name VMware Validated Design 5.0.1 Operations Managemen

Upgrade Description -

Snapshot the virtual machine's memory Deselected

Quiesce guest file system (Needs VMware Tools installed)

Deselected

Verify that the snapshot of the vRealize Suite Lifecycle Manager virtual appliance is successfully created.

Pause the replication of the vRealize Suite Lifecycle Manager virtual appliance

Before the upgrade, pause the replication task that controls the network traffic of vRealize Suite Lifecycle Manager between the source and the target site.



to ht tps :/ /s fo01m01vc01.sfo01.ra inpole. local/vsphere-c l ient / .

b Log in with username: [email protected] and password: vsphere_admin_password.

From the Home menu, select vSphere Replication.

Select the sfo01m01vc01.sfo01.rainpole.local vCenter Server instance.

On the Monitor tab, click vSphere Replication > Outgoing Replications.

In the Search text box, enter vrslcm .

Select the vrslcm01svr01a virtual machine and click the Pause ongoing replication icon.

In the Pause dialog box, click Yes.

Click vSphere Replication and under Monitoring, verify that the replication status is Paused for vrslcm01svr01a.

Upgrade the vRealize Suite Lifecycle Manager Virtual Appliance Upgrade the vRealize Suite Lifecycle Manager appliance by using an upgrade ISO file.

Procedure Log in to vRealize Suite Lifecycle Manager appliance by using Secure Shell (SSH)

client.

a Open an SSH connection to vrslcm01svr01a.rainpole.local.

b Log in with username: root and password: vrslcm_root_password.



Before initiating the upgrade, grant execute permission to the upgrade script and verify that the sfcb service is running.

a Grant execute permission to the upgrade script.chmod

chmod -R 775 /etc/vlcm/upgrade-va

b Verify that the sfcb service is running.

/etc/init.d/vami-sfcb status

c If the sfcb service is not running, start it.

/etc/init.d/vami-sfcb start

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

a Open a Web browser and go to ht tps :/ /s fo01m01vc01.sfo01.ra inpole. local/vsphere-c l ient/ .

b Log in with username: [email protected] and password: vsphere_admin_password

Mount the VMware-vLCM-Appliance-2.1.0.11-build_number-updaterepo.iso upgrade file to the CD-ROM drive of the vRealize Suite Lifecycle Manager virtual appliance.

Log in to vRealize Suite Lifecycle Manager user interface.

a Open a Web browser and go to https: / /vrslcm01svr01a.rainpole. local/vrlcm .

b Log in as username: admin@localhost and password: vrslcm_admin_password.

In the Navigator, click the Settings icon and click the Update tab.

The Appliance Version of the current vRealize Suite Lifecycle Manager appliance appears.

Under Update vRealize Suite Lifecycle Manager, select CD-ROM as the repository type, and click Check updates.

The following message appears: Checking for available updates, this process can take a few minutes...Available Updates - 2.1.0.10 Build 13273278. Important: Check this KB article before triggering Upgrade - https://kb.vmware.com/s/article/56511.

Click Install upgrades.

The following message appears: Successfully triggered an upgrade. The server will not be available until upgrade completion. Refresh the browser window after some time.

After several minutes, refresh the vRealize Suite Lifecycle Manager user interface, and in the Upgrade Successful dialog box, click Continue.

Click the Settings icon and click the Update tab.


mailto:[email protected]


After the upgrade finishes, the following message appears: Upgrade completed successfully from 1.2.0.10 to 2.1.0.10.

If after the upgrade you do not see the appliance version updated, restart the vRealize Suite Lifecycle Manager virtual appliance.

Unmount the upgrade ISO file from the CD-ROM drive of the vRealize Suite Lifecycle Manager virtual appliance.

Install the patch for vRealize Suite Lifecycle Manager After you upgrade vRealize Suite Lifecycle Manager, install the required patch on the virtual appliance.

Procedure Log in to vRealize Suite Lifecycle Manager user interface.

a Open a Web browser and go to

https: / /vrslcm01svr01a.rainpole. local/vrlcm .

b Log in with username: admin@localhost and password: vrslcm_admin_password.

In the Navigator, click the Settings icon and click the Update tab.

Under System Information, click Install patch.

The Install Patch wizard appears.

Click Upload and upload the vrlcm-2.1.0-PATCH1.patch file.

After the upload finishes, the following message appears: Patch File vrlcm-2.1.0-PATCH1.patch is uploaded to the server.

On the Select Patch page, select PATCH2 and click Next.

On the Review and Install page, click Install.

The following message appears: Patch installation request was submitted successfully. On closing this wizard you will be taken to maintenance page. You will be directed to home page after installation.

Close the Install Patch wizard.

On the Under Maintenance page, click Back home.

Click the Settings icon, and click the Update tab.

Appliance Version shows 2.1.0 Patch 1.

Delete the snapshots of the vRealize Suite Lifecycle Manager virtual appliance

After you upgrade vRealize Suite Lifecycle Manager, delete the virtual appliance snapshot.




to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / . b Log in with username: [email protected] and password:

vsphere_admin_password.


In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01-mgmt01.

Right-click vrslcm01svr01a and select Snapshots > Manage Snapshots.

Select the VMware Validated Design 5.0.1 Operations Management Layer Upgrade snapshot and click the Delete a VM Snapshot icon.

In the Confirm Delete dialog box, click Yes.

Resume the replication of the vRealize Suite Lifecycle Manager virtual appliance

After the upgrade of vRealize Suite Lifecycle Manager, resume the paused replication task for the vRealize Suite Lifecycle Manager virtual appliance, to support a failover to Region B.






Select the sfo01m01vc01.sfo01.rainpole.local vCenter Server instance.


In the Search text box, enter vrslcm .

Select the vrslcm01svr01a virtual machine and click the Resume paused replication icon.

In the Resume dialog box, click Yes.

Click vSphere Replication and under Monitoring, verify that the replication status is OK for vrslcm01svr01a.

Upgrade vRealize Log Insight Using vRealize Suite Lifecycle Manager

After upgrading vRealize Suite Lifecycle Manager, begin the operations management layer upgrade with the vRealize Log Insight cluster in Region A. Upon completion of Region A, upgrade the vRealize Log Insight cluster in Region B, and manually upgrade content packs and agents.

• Upgrade the vRealize Log Insight clusters in each region using vRealize Suite Lifecycle



Manager.

• Manually upgrade the vRealize Log Insight agents on the management components that send log data to the vRealize Log Insight cluster over the Ingestion API.

• After you upgrade the vRealize Log Insight virtual appliances and content packs, upgrade the agents on all the Microsoft Windows Server virtual machines.

Table 6. vRealize Log Insight Nodes in the SDDC

Region Role IP Address FQDN Region A Integrated Load Balancer VIP 192.168.31.10 sfo01vrli01.sfo01.rainpole.local

Master Node 192.168.31.11 sfo01vrli01a.sfo01.rainpole.local Worker Node 1 192.168.31.12 sfo01vrli01b.sfo01.rainpole.local Worker Node 2 192.168.31.13 sfo01vrli01c.sfo01.rainpole.local Worker Node x 192.168.31.x sfo01vrli01x.sfo01.rainpole.local

Region B Integrated Load Balancer VIP 192.168.32.10 lax01vrli01.lax01.rainpole.local Master Node 192.168.32.11 lax01vrli01a.lax01.rainpole.local Worker Node 1 192.168.32.12 lax01vrli01b.lax01.rainpole.local Worker Node 2 192.168.32.13 lax01vrli01c.lax01.rainpole.local Worker Node x 192.168.32.x lax01vrli01x.lax01.rainpole.local

Prerequisites • Verify that the vRealize Log Insight cluster is part of a vRealize Suite Lifecycle Manager

private cloud environment.

• Verify that you have a current backup of each vRealize Log Insight virtual appliance.

• Verify that the vRealize Suite Lifecycle Manager virtual appliance is: connected to the Internet, is registered with the My VMware portal, and that your account for My VMware has sufficient permissions to download vRealize Log Insight from your entitlement account.

• Review the release notes of the vRealize Log Insight version in this validated design.

Procedure Download vRealize Log Insight in vRealize Suite Lifecycle Manager.

Upgrade vRealize Log Insight in Region A using vRealize Suite Lifecycle Manager, followed by a manual upgrade of the content packs and the agents.

After completing the upgrade of the vRealize Log Insight cluster in Region A, return to the previous procedures and continue with the upgrade of the vRealize Log Insight cluster in Region B.

After completing the upgrade of vRealize Log Insight in both regions, to prevent forwarding loops, verify the event forwarding filter configuration in Region A and Region B.


What to do next Verify that vRealize Log Insight is operational after the upgrade. See Verification of vRealize Log Insight in the VMware Validated Design Operational Verification documentation.

Download vRealize Log Insight in vRealize Suite Lifecycle Manager In vRealize Suite Lifecycle Manager, you download the vRealize Log Insight product binaries for the upgrade from My VMware.





In the Navigator, click the Settings icon and click the My VMware tab.

In the My VMware Products list, locate the vRealize Log Insight product with version 4.7.0 and click the Download icon.

Download status progresses from SUBMITTED to INPROGRESS.

In the Download Status column, click the INPROGRESS status.

On the Requests page, monitor myvmwaredownload until the request is marked as COMPLETED.

Upgrade vRealize Log Insight in Region A Upgrade the operations management layer by starting with the vRealize Log Insight cluster in Region A. You upgrade vRealize Log Insight using vRealize Suite Lifecycle Manager, followed by a manual upgrade of the content packs and the agents.

Take Snapshots of the vRealize Log Insight Appliances in Region A Before you begin, take a snapshot of each vRealize Log Insight virtual machine in the environment. Use these snapshots to perform a rollback operation, if necessary.

Table 7. vRealize Log Insight Virtual Machines

Region Virtual Machine Name Region A sfo01vrli01a

sfo01vrli01b sfo01vrli01c



to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / .



Take a snapshot for each vRealize Log Insight node.

a From the Home menu, select VMs and Templates.

b In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01fd-vrli

c Right-click sfo01vrli01a and select Snapshots > Take Snapshot. d In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Operations

Management Layer Upgrade Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools installed)

Deselected

e Repeat this step for the remaining vRealize Log Insight virtual machines in Region A.

Verify that the snapshots for each vRealize Log Insight virtual machine are successfully created.

Upgrade the vRealize Log Insight cluster in Region A using vRealize Suite Lifecycle Manager

Use vRealize Suite Lifecycle Manager and upgrade the vRealize Log Insight cluster in Region A.





In the Navigator, click the Environments icon.

Locate the SFO-Region-Env environment and click View Details.

In the vRealize Log Insight product card, click the ellipsis on the top right corner and select Upgrade.

On the vRealize Log Insight page, under the Product Details section, enter the following settings and click Check Compatibility Matrix.

Setting Value Select Repository Type vRealize Suite Lifecycle Manager Repository Product Version 4.7.0



Click Next and in the PreCheck Details section, click Run Precheck.

vRealize Suite Lifecycle Manager displays a Validation request submitted successfully message. The validation takes a few minutes to finish and shows Successful for Data validation and vRealize Log Insight Validations.

After the pre-check validation finishes successfully, click Next.

In the Summary Details section, review the Product Upgrade information and click Submit.

In the Navigator, click the Requests icon.

In the Request Info column, the Validate and Submit Upgrade Product request for Environment Name: Cross-Region-Env shows an INPROGRESS status.

After the upgrade is complete, verify that vRealize Log Insight is upgraded to version 4.7.

a In the Navigator, click Environments, locate the environment that was upgraded,

and click View Details.

b On the vRealize Log Insight product card, verify that the version is 4.7.0.

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.

Procedure Log in to the vRealize Log Insight user interface.

a Open a Web browser and go to https:/ /sfo01vrli01.sfo01.rainpole. local . b Log in with username: admin and password: vrli_admin_password.

Click the configuration drop-down menu icon and select Content Packs.

In the Navigator, under Content Pack Marketplace, click Updates.

On the Log Insight Content Pack Marketplace page, click Update All to upgrade all content packs to the latest version.

After upgrading the content packs, click each of the items under Installed Content Packs and verify that the Version number of each content pack matches with the version for this Validated Design.

Upgrade the vRealize Log Insight Agents on the Windows Server virtual machines in Region A

After upgrading the vRealize Log Insight cluster in Region A, upgrade the vRealize Log Insight agents on the Windows Server virtual machines in the environment. Download the latest agents from the vRealize Log Insight cluster and upgrade the agent that runs on the vRealize Automation IaaS servers, Microsoft SQL Server, and Site Recovery Manager Server in Region A.




Click the configuration drop-down menu icon and select Administration.

Under Management, click Agents.

Click the Download Log Insight Agent Version 4.7.0 link from the bottom of the page.

In the Download Log Insight Agent Version 4.7.0 dialog box, download the following vRealize Log Insight Agent files on the Windows host that you use to access the environment.

Setting Value Download location https:/ /sfo01vrl i01.s fo01.rainpole. local

Agent version Windows MSI (32-bit/64-bit)

Save As VMware-Log-Insight-Agent-4.7.0-build_number_Region_A_vRealize_Log_Insight_VIP_address.msi

Upgrade the vRealize Log Insight Agents for Windows virtual machines.

a Open a Remote Desktop Protocol (RDP) connection to each of the following Windows virtual machines.

SDDC Layer Role Fully Qualified Domain Name Cloud Management vRealize Automation IaaS Web

Server vra01iws01a.rainpole.local vra01iws01b.rainpole.local

vRealize Automation IaaS Manager Service and DEM Orchestrator

vra01ims01a.rainpole.local vra01ims01b.rainpole.local

vRealize Automation IaaS DEM Worker

vra01dem01a.rainpole.local vra01dem01b.rainpole.local

vRealize Automation IaaS Proxy Agent

sfo01ias01a.sfo01.rainpole.local sfo01ias01b.sfo01.rainpole.local

Microsoft SQL Server vra01mssql01.rainpole.local Business Continuity Site Recovery Manager sfo01m01srm01.sfo01.rainpole.local

b Log in to the vRealize Automation windows virtual machine with username: rainpole\svc-vra and password: svc-vra_user_password

c Copy the VMware-Log-Insight-Agent-4.7.0-build_number_Region_A_vRealize_Log_Insight_VIP_address.msi file from the Windows host to the vRealize Automation Windows Server virtual machine.

d Open an administrative command prompt window, and navigate to the directory where the.msi file is saved.

e Run the following command to install the vRealize Log Insight agent with custom values.


VMware-Log-Insight-Agent-4.7.0-build_number_192.168.31.10.msi SERVERPORT=9000 AUTOUPDATE=yes LIAGENT_SSL=no

f In the VMware vRealize Log Insight Agent Setup wizard, accept the license agreement and click Next.

g With the Log Insight host name sfo01vrli01.sfo01.rainpole.local shown in the Host text box, click Install.

h When the installation is complete, click Finish.

i Repeat this step on the remaining vRealize Automation IaaS virtual machines including Microsoft SQL Server.

j After the vRealize Log Insight agent has been upgraded on the vRealize Automation IaaS virtual machines, repeat this step on the Site Recovery Manager virtual machine using the following credentials to log in.

Settings Value User name Windows administrator user Password windows_administrator_password

After you upgrade the vRealize Log Insight agents for Region A, verify the agent version in the vRealize Log Insight cluster.


c Click the configuration drop-down menu icon and select Administration.

d Under Management, click Agents.

e On the Agents page, verify that the Version column shows 4.7.0.xxxxxxx for all the windows server virtual machines.

Delete the snapshots of the vRealize Log Insight virtual appliances in Region A

After completing the upgrade of vRealize Log Insight and verifying operations and functionality in Region A, delete the virtual machines snapshots.

Table 8. vRealize Log Insight Virtual Machines

Region Virtual Machine Name Region A sfo01vrli01a

sfo01vrli01b sfo01vrli01c







In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01fd-vrli.

Right-click sfo01vrli01a and select Snapshots > Manage Snapshots.

Click the snapshot that you created before the vRealize Log Insight upgrade, click the Delete a VM Snapshot icon and click Yes.

Repeat this procedure for the remaining virtual machines in the vRealize Log Insight cluster in Region A.

Upgrade vRealize Log Insight in Region B After completing the vRealize Log Insight cluster upgrade in Region A, return to the previous procedures and continue with the upgrade of the vRealize Log Insight cluster in Region B.

Procedure Take snapshots of the vRealize Log Insight virtual machines in Region B.

Repeat Take Snapshots of the vRealize Log Insight Appliances in Region A using the following details for Region B.

vCenter Server Data Center Folder Virtual Machine Name lax01m01vc01.lax01.rainpole.local lax01-m01dc lax01-m01fd-vrli lax01vrli01a

lax01vrli01b lax01vrli01c

Upgrade the vRealize Log Insight cluster in Region B.

Repeat Upgrade the vRealize Log Insight Cluster in Region A Using vRealize Suite Lifecycle Manager using the following details for Region B.

Setting Value Environment Name LAX-Region-Env

Upgrade the content packs on the vRealize Log Insight cluster in Region B.

Repeat Upgrade the Content Packs on vRealize Log Insight in Region A using the following details for Region B.

Setting Value vRealize Log Insight Login URL https:/ / lax01vrl i01a. lax01.rainpole. local

Upgrade the vRealize Log Insight agents on the Windows Servers in Region B.

Repeat Upgrade the vRealize Log Insight Agents on the Windows Server Virtual Machines in Region A using the following details for Region B.



Table 9. MSI File of the vRealize Log Insight Agent for the Windows Nodes in Region B

Setting Value Download location https:/ / lax01vrl i01. lax01.rainpole. local Agent version Windows MSI (32-bit/64-bit) Save As VMware-Log-Insight-Agent-4.7.0-

build_number_Region_B_vRealize_Log_ Insight_VIP_address.msi

Table 10. Windows Nodes to Update the Log Insight Agent on in Region B

SDDC Layer Role Fully Qualified Domain Name Cloud Management vRealize Automation IaaS Proxy

Agent lax01ias01a.lax01.rainpole.local lax01ias01b.lax01.rainpole.local

Business Continuity Site Recovery Manager lax01m01srm01.lax01.rainpole.local

Update the agent on the IaaS or Site Recovery Manager virtual machine using the following command: VMware-Log-Insight-Agent-4.7.0-build_number_192.168.32.10.msi SERVERPORT=9000 AUTOUPDATE=yes LIAGENT_SSL=no.

Delete the Snapshots of the vRealize Log Insight Virtual Appliances in Region B.

Repeat Delete the Snapshots of the vRealize Log Insight Virtual Appliances in Region A using the following details for Region B.

vCenter Server Data Center Folder Virtual Machine Name lax01m01vc01.lax01.rainpole.local lax01-m01dc lax01-m01fd-vrli lax01vrli01a

lax01vrli01b lax01vrli01c

Verify the Event Forwarding Filter configuration in Region A and Region B

After completing the upgrade of vRealize Log Insight in both regions, to prevent forwarding loops, verify the event forwarding filter configuration.

Setting Region A Region B vRealize Log Insight UI https://sfo01vrli01.sfo01.rainpole.local https://lax01vrli01.lax01.rainpole.local Event Forwarding Name SFO01 to LAX01 LAX01 to SFO01 Filter Site does not match LAX01 Site does not match SFO01




Verify the event forwarding filter to prevent forwarding loops.

a Click the configuration drop-down menu icon and select Administration.

b Under Management, click Event Forwarding.

c On the Event Forwarding page of the vRealize Log Insight user interface, click the Edit icon of the SFO01 to LAX01 destination.

d In the Edit Destination dialog box, under the Filter section, verify the following filter attributes.

Filter Type Operator Value Site does not match LAX01

e Click Save.

Repeat this procedure for the vRealize Log Insight cluster in Region B.

Upgrade vRealize Operations Manager using vRealize Suite Lifecycle Manager

After you finish the upgrade of vRealize Log Insight, continue the operations management layer upgrade with a vRealize Operations Manager upgrade using vRealize Suite Lifecycle Manager. Both the virtual appliance operating system and the vRealize Operations Manager product are upgraded. After the upgrade, perform additional configurations on the management pack adapters and dashboards for alignment with the design.

Table 11. vRealize Operations Manager Nodes in the SDDC

Region Role IP Address Fully Qualified Domain Name Region A Master Node 192.168.11.31 vrops01svr01a.rainpole.local

Master Replica Node 192.168.11.32 vrops01svr01b.rainpole.local Data Node 1 192.168.11.33 vrops01svr01c.rainpole.local Remote Collector Node 1 192.168.31.31 sfo01vropsc01a.sfo01.rainpole.local Remote Collector Node 2 192.168.31.32 sfo01vropsc01b.sfo01.rainpole.local

Region B Remote Collector Node 1 192.168.32.31 lax01vropsc01a.lax01.rainpole.local Remote Collector Node 2 192.168.32.32 lax01vropsc01b.lax01.rainpole.local

Prerequisites

• Download the.pak files for the Management Packs for vRealize Operations Manager to a Windows host that has access to the environment.

Table 12. PAK Files Required for vRealize Operations Manager Management Packs Upgrade

PAK Type PAK File vRealize Operations Management Pack for NSX for vSphere

vmware-MPforNSX-vSphere-build_number.pak


PAK Type PAK File vRealize Operations Management Pack for VMware Site Recovery Manager

VMware-srm-vrops-mp-build_number.pak

vRealize Operations Management Pack for Storage Devices

vmware-MPforPhysicalSAN-build_number.pak

• Remediate any issues before you begin the upgrade. Examine the health of the vRealize Operations Manager cluster by running an Upgrade Assessment Tool, which provides a pre-upgrade report detailing the metric reduction impact on the user content and offers suggestions for replacement metrics. Install and run the Upgrade Assessment Tool by following the procedure in VMware Knowledge Base article 57283.

• Preserve any customized content such as alert definitions, symptom definitions, recommendations, and views, by cloning the content.

• vRealize Operations Manager 7.0 is a major version that requires a new license key. The product works in evaluation mode until you install a new valid license key. See the Release Notes and obtain the license key for vRealize Operations Manager 7.0 from the My VMware portal.

• Verify that you have a current backup of each vRealize Operations Manager virtual appliance.

• Verify you have privileges in the vSphere Web Client to pause the replication task of vRealize Operations Manager.

• Verify that the vRealize Suite Lifecycle Manager virtual appliance is: connected to the Internet, is registered with the My VMware portal, and that your account for My VMware has sufficient permissions to download vRealize Operations Manager.

• Verify that vRealize Operations Manager appliances are in a consistent state.

• Verify that the root passwords are the same for all vRealize Operations Manager nodes.

• Verify that the vRealize Log Insight agent configuration/var/lib/loginsight-agent/liagent.ini file, contains ssl=no on all vRealize Operations Manager virtual appliances.

• Review the release notes of the vRealize Operations Manager version in this validated design

Take the vRealize Operations Manager Analytics cluster offline and take snapshots

Before the upgrade of vRealize Operations Manager, take the Analytics Cluster offline and take a snapshot of each vRealize Operations Manager node. If you must rollback vRealize Operations Manager to the previous state, use these snapshots to perform the rollback operation.

Table 13. vRealize Operations Manager Virtual Machines

Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vrops Master Node vrops01svr01a

sfo01-m01fd-vrops Master Replica Node vrops01svr01b sfo01-m01fd-vrops Data Node 1 vrops01svr01c


https://docs.vmware.com/en/vRealize-Operations-Manager/7.0/rn/vRealize-Operations-Manager-70.html#sys_req

https://my.vmware.com/


Region Folder Role Virtual Machine Name sfo01-m01fd-vrops Data Node X vrops01svr01 x.rainpole.local

Additional node that you have joined to your vRealize Operations Manager analytics cluster.

sfo01-m01fd-vropsrc Remote Collector 1 sfo01vropsc01a sfo01-m01fd-vropsrc Remote Collector 2 sfo01vropsc01b

Region B lax01-m01fd-vropsrc Remote Collector 1 lax01vropsc01a lax01-m01fd-vropsrc Remote Collector 2 lax01vropsc01b

Procedure Log in to the vRealize Operations Manager administrator interface on the master node

of your analytics cluster.

a Open a Web browser and go to https: / /vrops01svr01а.rainpole. local /admin .

b Log in with username: admin and password vrops_admin_password.

Take all vRealize Operations Manager nodes in the cluster offline.

In the Navigator, click System Status.

On the System Status page, under Cluster Status click Take Offline.

a In the Take Cluster Offline dialog box, enter VMware Val idated Design 5.0.1 Operations Management Layer Upgrade in the Reason text box and click OK.

Wait until all vRealize Operations Manager nodes in the cluster are offline and the Cluster Status becomes Offline.


Open a Web browser and go to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / .

a Log in with username: [email protected] and password: vsphere_admin_password.

Take a snapshot of the vRealize Operations Manager virtual machines in the environment.

a From the Home menu, select VMs and Templates.

b In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01-mgmt01.

c In the Navigator, right-click vrops01svr01a and select Snapshots > Take Snapshot.

d In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Operations

Management Layer Upgrade



Setting Value Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools installed) Deselected

e Repeat this step for the remaining vRealize Operations Manager virtual machines in Region A and Region B.

Verify that the snapshots for each vRealize Operations Manager virtual machine are successfully created.

Download vRealize Operations Manager in vRealize Suite Lifecycle Manager

In vRealize Suite Lifecycle Manager, download the vRealize Operations Manager product binaries from My VMware.






In the My VMware Products list, locate the vRealize Operations product with version 7.0.0 and click the Download icon.



Pause the Replication of vRealize Operations Manager Before the upgrade, pause the replication task that controls the network traffic of vRealize Operations Manager VMs to prevent updates to the replica virtual machines.






Select the sfo01m01vc01.sfo01.rainpole.local vCenter Server.




Enter vrops in the Search text box.

Select all the vRealize Operations Manager virtual machines and click the Pause ongoing replication icon.


Click vSphere Replication and under Monitoring, verify that the replication status is Paused for the vRealize Operations Manager virtual machines.

Upgrade vRealize Operations Manager Using vRealize Suite Lifecycle Manager

Use vRealize Suite Lifecycle Manager and upgrade vRealize Operations Manager.






In the Cross-Region-Env environment card, click View Details.

In the vRealize Operations product card, click the ellipsis on the top right corner and select Upgrade.

On the vRealize Operations page, under the Product Details section, enter the following settings and click Next.


In the PreCheck Details section, click Run PreCheck.

vRealize Suite Lifecycle Manager displays a Validation request submitted successfully message. The validation takes a few minutes to finish and displays the results after the validation tasks have completed.





On the Requests page, monitor the Upgrade vROPS steps until the request is marked as COMPLETED.


After the upgrade finishes, verify that vRealize Operations is upgraded to version 7.0.

a In the Navigator, click the Environments icon.

b In the Cross-Region-Env environment card, click View Details.

c In the vRealize Operations product card, verify that the version is 7.0.0.

Update vRealize Operations Manager License Key vRealize Operations Manager 7.0 is a major version that requires a new license key. After the upgrade, all license keys are invalidated, except vSOM Enterprise Plus and its add-ons. vRealize Operations Manager works in evaluation mode for 60 days.

Procedure Log in to vRealize Operations Manager by using the operations interface.

a Open a Web browser and go to https:/ /vrops01svr01.rainpole.local . b Log in with username: admin and password: vrops_admin_password.

On the main navigation bar, click Administration.

In the left pane, click Management > Licensing.

On the License Keys tab, click the Add icon.

In the Add License dialog box, select vRealize Operations Manager from the Select product or solution drop-down menu.

Enter the license key and click Validate.

The following message appears: License key validated successfully.

Review the license key details, and click Save.

Upgrade the Management Packs for NSX for vSphere and 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. The remaining management packs included in the VMware Validated Design are pre-installed with vRealize Operations Manager.

Table 14. Management Packs for vRealize Operations Manager

PAK Type PAK File vRealize Operations Management Pack for NSX for vSphere vmware-MPforNSX-vSphere-build_number.pak vRealize Operations Management Pack for VMware Site Recovery Manager

VMware-srm-vrops-mp-build_number.pak




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 NSX for vSphere 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.

Verify that the adapters are collecting metrics.

a On the Solutions page, select Management Pack for NSX-vSphere from the solution table.

b Under Configured Adapter Instances, verify that the Collection State is Collecting and the Collection Status is Data receiving.

Repeat this procedure and upgrade the Management Pack for Site Recovery Manager.

Reinstall the Management Pack for Storage Devices in vRealize Operations Manager

vRealize Operations Management Pack for Storage Devices 7.0 is not a continuation of the previous versions. Uninstall the previous version and install the later version of the management pack.

Table 15. Management Pack for Storage Devices for vRealize Operations Manager

PAK Type PAK File vRealize Operations Management Pack for Storage Devices

vmware-MPforPhysicalSAN-build_number.pak



Uninstall the Management Pack for Storage Devices.



b In the left pane, click Solutions.

c On the Solutions page, locate Management Pack for Storage Devices, and click Uninstall Solution.

d In the Warning dialog box, select I understand the risk and agree, and click OK.

Install the Management Pack for Storage Devices.


b In the left pane of vRealize Operations Manager, click Solutions.

c On the Solutions page, click Add.

d On the Select a Solution page, browse your file system and locate the.pak file for the 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 installation finishes, click Finish.

Add Storage Devices Adapters in vRealize Operations Manager After installing the management pack, configure storage devices adapters to collect monitoring data about the storage devices in the SDDC. Each adapter communicates with a vCenter Server instance to retrieve data about the storage devices from the vCenter Server inventory.



On the main navigation bar, click Administration.

In the left pane of vRealize Operations Manager, click Solutions.

Select Management Pack for Storage Devices from the solution table and click Configure.

The Manage Solution - Management Pack for Storage Devices dialog box appears.

Under Instance Settings, enter the settings for the connection to the vCenter Server instance.

a If you already have added another storage devices adapter, click the Add icon on

the left side to add adapter settings.

b Enter the display name, description, and name of the vCenter Server instance.


Table 16. Storage Devices Adapters in Region A

Setting Value for the Management vCenter Server in Region A

Value for the Compute vCenter Server in Region A

Display Name Storage Devices Adapter - sfo01m01vc01 Storage Devices Adapter - sfo01w01vc01 Description Storage Devices in Management vCenter for sfo01 Storage Devices in Compute vCenter for sfo01 vCenter Server sfo01m01vc01.sfo01.rainpole.local sfo01w01vc01.sfo01.rainpole.local SNMP Community Strings

- -

Table 17. Storage Devices Adapters in Region B

Setting Value for the Management vCenter Server in Region B

Value for the Compute vCenter Server in Region B

Display Name Storage Devices Adapter - lax01m01vc01 Storage Devices Adapter - lax01w01vc01 Description Storage Devices in Management vCenter for lax01 Storage Devices in Compute vCenter for lax01 vCenter Server lax01m01vc01.lax01.rainpole.local lax01w01vc01.lax01.rainpole.local SNMP Community Strings

- -

c Click the Add icon next to the Credential text box, and configure the collection credentials for the connection to the vCenter Server instance, and click OK.

vCenter Server Credentials Attribute for Region A Credential name Storage Devices Adapter Credentials - sfo01m01vc01

Storage Devices Adapter Credentials - sfo01w01vc01 User name [email protected] Password svc-vrops-mpsd-password

vCenter Server Credentials Attribute for Region B

Credential name Storage Devices Adapter Credentials - lax01m01vc01 Storage Devices Adapter Credentials - lax01w01vc01

User name [email protected] Password svc-vrops-mpsd-password

d Click Test Connection and validate the connection to the vCenter Server.

The vCenter Server certificate appears.

e In the Review and Accept Certificate dialog box, verify the vCenter Server certificate information, and click Accept.

f In the Info dialog box, click OK .

g Expand Advanced Settings, from the Collectors/Groups drop-down menu, select sfo01-remote-collectors and click Save Settings.

h In the Info dialog box, click OK.

i Repeat this step for the other vCenter Server instance.

In the Manage Solution - Management Pack for Storage Devices dialog box, click Close.


The storage devices adapters appear on the Solutions page of the vRealize Operations Manager user interface. The Collection State column for the Physical Storage Devices Adapter displays Collecting, and the Collection Status column displays Data receiving.

Resume the replication of vRealize Operations Manager After completing the upgrade of vRealize Operations Manager, you resume the replication task and allow the vRealize Operations Manager virtual machines replication between Region A and Region B.







Click the Monitor tab and click vSphere Replication > Outgoing Replications.

In the Search text box, enter vrops .

Select all vRealize Operations Manager virtual machines, and click the Resume paused replication icon.


Click vSphere Replication and under Monitoring, verify that the replication status is OK for all vRealize Operations Manager virtual machines.

Delete the Snapshots of the vRealize Operations Manager Virtual Appliances

After you complete the upgrade of vRealize Operations and verify operations and functionality, delete the virtual machines snapshots taken before the upgrade.

Table 18. vRealize Operations Manager Virtual Machines

Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vrops Master Node vrops01svr01a

sfo01-m01fd-vrops Master Replica Node vrops01svr01b sfo01-m01fd-vrops Data Node 1 vrops01svr01c sfo01-m01fd-vrops Data Node X vrops01svr01 x

Additional node joined to your vRealize Operations Manager analytics cluster.

sfo01-m01fd-vropsrc Remote Collector 1 sfo01vropsc01a sfo01-m01fd-vropsrc Remote Collector 2 sfo01vropsc01b



Region Folder Role Virtual Machine Name Region B lax01-m01fd-vropsrc Remote Collector 1 lax01vropsc01a

lax01-m01fd-vropsrc Remote Collector 2 lax01vropsc01b



to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / . b Log in with username [email protected] and password:



In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01fd-vrops.

Right-click vrops01svr01a and select Snapshots > Manage Snapshots.

Click the snapshot that you created before vRealize Operations Manager upgrade and click the Delete a VM Snapshot icon.


Repeat this procedure for the remaining vRealize Operations Manager virtual machines.

What to do next Verify that vRealize Operations Manager is operational after the upgrade. See Verification of vRealize Operations Manager in the VMware Validated Design Operational Verification documentation.



4 Upgrade the Cloud Management Layer Continue the VMware Validated Design upgrade with the cloud management products.

Table 19. Upgrade Sequence for the Cloud Management Layer

Order Components Sub-Component 1 vRealize Business for Cloud vRealize Business Server

vRealize Business Data Collector 2 vRealize Automation vRealize Automation Appliances with Embedded

vRealize Orchestrator vRealize Automation IaaS Components

3 Post-Upgrade Configuration Changes -

Upgrade vRealize Business using vRealize Suite Lifecycle Manager Continue upgrading the VMware Validated Design from the previous version by upgrading the cloud management layer. In the cloud management layer, begin the upgrade with vRealize Business.

Table 20. vRealize Business Nodes in the SDDC

Region Role IP Address Fully Qualified Domain Name

Region A vRealize Business Server 192.168.11.66 vrb01svr01.rainpole.local vRealize Business Data Co 192.168.31.54 sfo01vrbc01.sfo01.rainpole.local

Region B vRealize Business Data Co 192.168.32.54 lax01vrbc01.lax01.rainpole.local

Prerequisites • Verify that the vRealize Suite Lifecycle Manager virtual appliance is: connected to the

Internet, is registered with the My VMware portal, and that your account for My VMware has sufficient permissions to download vRealize Business.

• Verify that you have privileges in the vSphere Web Client to pause the replication task of vRealize Business.

• Review the release notes of the vRealize Business version in this validated design.

Take the vRealize Business Virtual Machines Offline and Take Snapshots

Before you upgrade the vRealize Business, shut down the virtual machines in order and take a snapshot of each virtual machine in the environment. Use these snapshots to perform the rollback operation if necessary.


Table 21. vRealize Business Virtual Machines

Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vra vRealize Business for Cloud Server vrb01svr01

sfo01-m01fd-vraias vRealize Business for Cloud Data Collector sfo01vrbc01 Region B lax01-m01fd-vraias vRealize Business for Cloud Data Collector lax01vrbc01






Shut down the vRealize Business nodes in the environment according to the Shutdown Order of the Management Virtual Machines.

a In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-

m01dc>sfo01-m01fd-vra. b Right-click sfo01vrbc01 and select Power > Shut Down Guest OS. c In the Confirm Guest Shut Down dialog box, click Yes. d Repeat this step for the remaining vRealize Business virtual machines in the

environment.

Take a snapshot of the vRealize Business virtual machines in the environment.

a In the Navigator, right-click vrb01svr01 and select Snapshots > Take Snapshot.

b In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Cloud Management

Layer Upgrade Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools installed)

Deselected

c Repeat this step for the remaining vRealize Business virtual machines in the environment.

Verify that the snapshots for each vRealize Business virtual machine are successfully created.

Power on the vRealize Business virtual machines in the environment according to the Startup Order of the Management Virtual Machines.

a Right-click vrb01svr01 and select Power > Power On.



b Repeat this step for the remaining vRealize Business virtual machines in the environment.

Download vRealize Business in vRealize Suite Lifecycle Manager In vRealize Suite Lifecycle Manager, download the vRealize Business for Cloud binaries from My VMware.



https: / /vrslcm01svr01a.rainpole. local/vrlcm . b Log in with username: admin@localhost and password: vrslcm_admin_password.


In the My VMware Products list, locate the vRealize Business for Cloud product with version 7.5 and click the Download icon.




Pause the Replication of vRealize Business Before the upgrade, pause the replication task that controls the network traffic of vRealize Business virtual machines between Region A and Region B.








Select all the vRealize Business for Cloud virtual machines, and click the Pause ongoing replication icon.


Verify that the replication status is Paused for the vRealize Business for Cloud virtual machines.

Click vSphere Replication and under Monitoring, verify that the replication status is Paused for the vRealize Business for Cloud virtual machines.



Upgrade vRealize Business Using vRealize Suite Lifecycle Manager Use vRealize Suite Lifecycle Manager and upgrade vRealize Business.



https://vrslcm01svr01a.rainpole.local/vrlcm.




In the vRealize Business for Cloud product card, click the ellipsis on the top right corner and select Upgrade.

On the vRealize Business for Cloud page, under the Product Details section, enter the following settings and click Check Compatibility Matrix.


In the Product Details section, click Next.


vRealize Suite Lifecycle Manager displays a Validation request submitted successfully message. The validation takes a few minutes to finish and shows Successful for Data validation and vRealize Business for Cloud Validations.





After the upgrade finishes, verify that vRealize Business is upgraded to version 7.5.

a In the Navigator, click the Environments icon. b In the Cross-Region-Env environment card, click View Details. c In the vRealize Business for Cloud product card, verify that version is 7.5.0.

Unregistering vRealize Business from vRealize Automation and re-registering is automatically done by vRealize Suite Lifecycle Manager.

Log in to the vRealize Business Server appliance management console.

a Open a Web browser and go to https:/ /vrb01svr01.rainpole. local:5480 . b Log in with username: root and password: vrb_server_root_password.


If the upgrade fails, re-register vRealize Business with the vsphere.local default tenant after a rollback.

a Click Registration > vRA and enter the following credentials.

Setting Value Hostname vra01svr01.rainpole.local SSO Default Tenant vsphere.local SSO Admin User administrator SSO Admin Password vra_administrator_password Accept "vRealize Automation" certificate Selected

b Click Register. At the top of the page, a Registered with vRealize Automation message appears.

Delete the snapshots of the vRealize Business Virtual Machines After completing the upgrade of vRealize Business and verifying functionality, delete the virtual machines snapshots.

Table 22. vRealize Business Virtual Machines

Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vra vRealize Business for Cloud Server vrb01svr01

sfo01-m01fd-vraias vRealize Business for Cloud Data Collector sfo01vrbc01 Region B lax01-m01fd-vraias vRealize Business for Cloud Data Collector lax01vrbc01






In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01fd-vra.

Right-click vrb01svr01 and select Snapshots > Manage Snapshots.

Click the snapshot that you created before the vRealize Business upgrade, click the Delete a VM Snapshot icon and click Yes.


Repeat this procedure for the remaining vRealize Business data collector virtual machines.



Resume the Replication of vRealize Business Resume the paused replication task to allow vRealize Business for Cloud virtual machine replication between Region A and Region B.








Select all the vRealize Business virtual machines, and click the Resume paused replication icon.


Click vSphere Replication and under Monitoring, verify that the replication status is OK for the vRealize Business for Cloud virtual machines.

Upgrade vRealize Automation using vRealize Suite Lifecycle Manager

Proceed to upgrade vRealize Automation components using vRealize Suite Lifecycle Manager.

Table 23. vRealize Automation Nodes in the SDDC

Region Role IP Address Full Qualified Domain Name Region A vRealize Automation Server VIP 192.168.11.53 vra01svr01.rainpole.local

vRealize Automation Server Appliance 192.168.11.51 vra01svr01a.rainpole.local 192.168.11.52 vra01svr01b.rainpole.local

192.168.11.50 vra01svr01c.rainpole.local

vRealize Automation for IaaS Web VIP 192.168.11.56 vra01iws01.rainpole.local vRealize Automation for IaaS Web Server 192.168.11.54 vra01iws01a.rainpole.local

192.168.11.55 vra01iws01b.rainpole.local vRealize Automation IaaS Model Manager VIP 192.168.11.59 vra01ims01.rainpole.local vRealize Automation IaaS Model Manager Server

192.168.11.57 vra01ims01a.rainpole.local 192.168.11.58 vra01ims01b.rainpole.local

vRealize Automation IaaS DEM Worker 192.168.11.60 vra01dem01a.rainpole.local 192.168.11.61 vra01dem01b.rainpole.local

vRealize Automation IaaS Proxy Agent 192.168.31.52 sfo01ias01a.sfo01.rainpole.local 192.168.31.53 sfo01ias01b.sfo01.rainpole.local

Microsoft SQL Server for vRealize Automation 192.168.11.62 vra01mssql01.rainpole.local



Region Role IP Address Full Qualified Domain Name Region B vRealize Automation IaaS Proxy Agent 192.168.32.52 lax01ias01a.lax01.rainpole.local

192.168.32.53 lax01ias01b.lax01.rainpole.local

Prerequisites Verify that all vRealize Automation components have the required compute and storage resources to perform the upgrade, including space for temporary objects created during the process.

Table 24. Hardware Requirements for Upgrading vRealize Automation

Node Hardware Requirement for Each Node

Description

vRealize Automation Appliances Available disk space Disk1 with 50 GB

Disk3 with 25 GB

Disk4 with 50 GB

At least 4.5 GB of free disk space on the root partition to download and run the upgrade.

At least 4.5 GB of free space on the/storage/db

/storage/log subfolder cleaned of older archived ZIP files to free up disk space.

Memory 18 GB vCPU 4

vRealize Automation IaaS Windows virtual machines and Microsoft SQL Server database

Available disk space 5 GB

Verify that third-party software components required for the upgrade are available on the vRealize Automation nodes.

Table 25. Software Requirements for Upgrading vRealize Automation

Node Software Requirement

Description

Primary vRealize Automation IaaS Model Manager Server vra01iws01a.rainpole.local

Java Java SE Runtime Environment 8 64-bit Update 181* *installed. Remove any other versions from the system.

After you install Java, set the JAVA_HOME environment variable to the directory path of the new version.

*Caution: Validation testing has identified that the JRE version installed in the vra01iws01a.sfo01.rainpole.local Windows VM must be build 181. Newer versions may result in failure to upgrade the vCenter and WAPI services.


Table 26. Prerequisites for Upgrading vRealize Automation

Prerequisite Category

Description

Compatibility Verify all third-party integrations that might have been configured for use with vRealize Automation are compatible with vRealize Automation version 7.5. Contact the third-party integration vendor or developer and ensure compatibility.

Backup Verify that current backups of the vRealize Automation virtual appliances and the Infrastructure-as-a-Service (IaaS) virtual machines exist.

See the VMware Validated Design Backup and Restore documentation. Verify that a current backup of the external vRealize Automation database exists. The default name of the Microsoft SQL Server database is VRADB-01.

Privileges Verify that you have sufficient privileges to manage replications in the vSphere Web Client to pause the replication task of vRealize Automation before the upgrade.

Downloads Verify that the vRealize Suite Lifecycle Manager virtual appliance is: connected to the Internet and registered with My VMware portal using an account entitled to download the upgrade binaries.

Review the release notes of the vRealize Automation version in this validated design.

Cluster Integrity and Health

Open a Web browser and log in to the VAMI management interfaces by navigating to https:/ /vra01svr01a. rainpole. local :5480 . Select vRA Settings > Cluster and verify that all vRealize Automation IaaS Windows Server nodes meet the following requirements.

Have a Last Connected status of less than 30 seconds. Have a Time Offset status of less than 1 second. Open a web browser and log in to the three VAMI management interfaces by navigating to https:/ /vra01svr01a. rainpole. local :5480 , https:/ /vra01svr01b.rainpole. local :5480 and https:/ /vra01svr01c. rainpole. local :5480 . Select vRA Settings > Cluster and verify that both vRealize Automation virtual appliances meet the following requirements.

Have a Last Connected status of less than 10 minutes. The PostgreSQL database is connected and reporting a Status state of Up, indicating that the master and replica nodes are running. The PostgreSQL database is connected and reporting a Valid state of Yes, indicating synchronization between the master and replica nodes. Open a Web browser and log in to the three VAMI management interfaces by navigating to https:/ /vra01svr01a. rainpole. local :5480 , https:/ /vra01svr01b.rainpole. local :5480 , and https:/ /vra01svr01c. rainpole. local :5480 .

Select Services and verify that all services are reporting a REGISTERED status.


Prerequisite Category

Description

Preparing the vRealize Automation Environment

Make the vRealize Automation environment unavailable to end users and any automated integrations during the upgrade maintenance window.

Verify that the vRealize Automation environment has been quiesced for all activities, including but not limited to, users ordering new virtual machines and third-party integrations that can automate the ordering of new virtual machines. Without quiescing the environment, rollback operations can be disruptive, generating orphaned objects after snapshots have been created. To remediate such situation, you extend the maintenance window.

Verify that you have access to all databases and load balancers that vRealize Automation upgrade participates in, or impacts.

Verify that vRealize Automation appliances are in a consistent state before proceeding with the upgrade.

Set the vRealize Automation Database Replication Mode to Asynchronous

Before upgrading the distributed vRealize Automation environment, you set the embedded PostgreSQL database synchronous replication mode to asynchronous.

Procedure Log in to the first vRealize Automation appliance.

a Open a Web browser and go to https:/ /vra01svr01a.rainpole. local:5480 b Log in with username: root and password: vra_appA_root_password

On the vRA Settings tab, click the Database tab, and under Actions, click the Async Mode button.

In the Sync State column, verify that all nodes show as Async.

Replication mode shows Database is in Asynchronous Mode.

Direct Traffic to the Primary Nodes and Disable Health Monitoring for vRealize Automation on the Load Balancer in Region A

Before you upgrade the vRealize Automation virtual appliances and the vRealize Automation IaaS nodes, direct all traffic to the primary node and disable the health check on the NSX load balancer for the management applications.

The configuration change disables the second pool member for the five vRealize Automation VIPs. During an upgrade, If the second pool member remains enabled, you might experience failures during vRealize Automation upgrade, and service initialization or registration failures during a vRealize Automation appliance power cycle operations.

On the NSX load balancer, you disable the secondary vRealize Automation nodes and deselect the monitor for the associated traffic in the pools.


Load Balancer Pools on sfo01m01lb01 Secondary Member to Disable vra-svr-443 According to which nodes are labelled as REPLICA:

vra01svr01a

vra01svr01b

vra01svr01c

vra-svr-8444 According to which node is labelled as REPLICA

vra01svr01a

vra01svr01b

vra01svr01c

vra-iws-443 vra01iws01b vra-ims-443 vra01ims01b vra-vro-8283 According to which node is labelled as REPLICA:

vra01svr01a

vra01svr01b

vra01svr01c


a Open a Web browser and go to https:/ /vra01svr01a.rainpole. local:5480 b Log in with username: root and password: vra_appA_root_password.

On the vRA Settings tab, click the Database tab and verify which vRealize Appliances are secondary and show as REPLICA.


a Open a Web browser and go to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / .


From the Home menu of the vSphere Web Client, select Networking & Security.

In the Navigator, click NSX Edges.

From the NSX Manager drop-down menu, select 172.16.11.65 and double-click the sfo01m01lb01 NSX Edge to open its network settings.

On the Manage tab, click the Load Balancer tab and click Pools.

Select the vra-svr-443 pool that contains the vRealize Automation appliances and click Edit.

In the Edit Pool dialog box, for each secondary node, click Edit, from the State drop-down menu select Disable, and click OK.

In the Edit Pool dialog box, from the Monitors drop-down menu select None, and click OK.



Repeat the procedure on the remaining load balancer pools.

To verify that the load balancer redirects the traffic to the primary node of vRealize Automation, open a Web browser, go to https: / /vra01svr01.rainpole. local/vcac , and verify that the login page of the vRealize Automation administration portal appears.

Take the vRealize Automation Virtual Machines Offline and Take Snapshots

Before the upgrade of vRealize Automation, shut down the virtual machines in an order and take a snapshot of each virtual machine in the environment.

Table 27. vRealize Automation Virtual Machines

Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vra vRealize Automation Appliances vra01svr01a

sfo01-m01fd-vra sfo01-m01fd-vra

vra01svr01b vra01svr01c

sfo01-m01fd-vra vRealize Automation IaaS Web Servers vra01iws01a sfo01-m01fd-vra vra01iws01b sfo01-m01fd-vra vRealize Automation IaaS Manager Service

and DEM Orchestrators vra01ims01a

sfo01-m01fd-vra vra01ims01b sfo01-m01fd-vra vRealize Automation IaaS DEM Workers vra01dem01a sfo01-m01fd-vra vra01dem01b sfo01-m01fd-vraias vRealize Automation IaaS Proxy Agents sfo01ias01a sfo01-m01fd-vraias sfo01ias01b

Region B lax01-m01fd-vraias vRealize Automation IaaS Proxy Agents lax01ias01a lax01-m01fd-vraias lax01ias01b

Important: If you are using the designated Microsoft SQL Server vra01mssql01.rainpole.local covered within the VMware Validated Design, include this virtual machine in the snapshot procedure. If you are using a shared instance of Microsoft SQL Server to host the vRealize Automation IaaS database with other databases, ensure that you have a recent backup per the vRealize Automation Upgrade Prerequisites.






Shut down the vRealize Automation virtual machines in the environment according to the Shutdown Order of the Management Virtual Machines.

a In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-

m01dc>sfo01-m01fd-vra. b Right-click vra01dem01a, select Power > Shut Down Guest OS.



c In the Confirm Guest Shut Down dialog box, click Yes.

d Repeat this step for the remaining vRealize Automation virtual machines in the environment.

Take a snapshot of the vRealize Automation virtual machines in the environment.

a In the Navigator, right-click vra01svr01a and select Snapshots > Take Snapshot.

b In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Cloud Management


Deselected

c Repeat this step for the remaining vRealize Automation virtual machines in the environment.

Verify that the snapshots for each vRealize Automation virtual machine are successfully created.

Power on the vRealize Automation virtual machines in the environment according to the Startup Order of the Management Virtual Machines.

a In the Navigator, expand the sfo01m01vc01.sfo01.rainpole.local > sfo01-

m01dc > sfo01-m01fd-vra tree. b Right-click the vra01mssql01 virtual machine, select Power > Power On. c Repeat this step for the remaining vRealize Automation virtual machines in the

environment.

Download vRealize Automation in vRealize Suite Lifecycle Manager In vRealize Suite Lifecycle Manager, download the vRealize Automation product binaries for the upgrade from My VMware.




b Log in with username: admin@localhost and password: vrslcm_admin_password


In the My VMware Products list, locate the vRealize Automation product with version 7.5 and click Download.





Pause the replication of vRealize Automation Before the upgrade, you pause the replication task that controls the network traffic of vRealize Automation virtual machines between Region A and Region B.








Select all the vRealize Automation virtual machines, and click the Pause ongoing replication icon.


Click vSphere Replication and under Monitoring, verify that the replication status is Paused for the vRealize Business for Cloud virtual machines.

Upgrade vRealize Automation using vRealize Suite Lifecycle Manager

Use vRealize Suite Lifecycle Manager and upgrade vRealize Automation.




b Log in with username: admin@localhost and password: vrslcm_admin_password



In the vRealize Automation product card, click the ellipsis on the top right corner and select Upgrade.

On the vRealize Automation page, under the Product Details section, enter the following settings and click Next.



Setting Value Select Repository Type vRealize Suite Lifecycle Manager Repository

Product Version 7.5.0


vRealize Suite Lifecycle Manager displays a Validation request submitted successfully message. The validation takes a few minutes to finish and shows Successful for Data validation and vRealize Automation Validations.





After the upgrade finishes, verify that vRealize Automation is upgraded to version 7.5.

a In the Navigator, click the Environments icon.

b In the Cross-Region-Env environment card, click View Details.

c In the vRealize Automation product card, verify that the version is 7.5.0.

vRealize Suite Lifecycle Manager unregisters vRealize Business from vRealize Automation and re-registers it automatically.

Configure the embedded vRealize Orchestrator service in the vRealize Automation appliances in Region A

After the upgrade, enable the embedded vRealize Orchestrator service and configure the vRealize Orchestrator service in the vRealize Automation appliances. Configure each vRealize Automation appliance to create a highly available embedded vRealize Orchestrator cluster.

vRealize Orchestrator Instance IP Address FQDN Host A 192.168.11.51 vra01svr01a.rainpole.local Host B 192.168.11.52 vra01svr01b.rainpole.local Host C 192.168.11.50 vra01svr01c.rainpole.local

Procedure Log in to the vRealize Automation appliance by using Secure Shell (SSH) client.

a Open an SSH connection to vra01svr01a.rainpole. local . b Log in with username: root and password: vra_appA_root_password.

Verify that the automatic start of the service is enabled using the following command: chkconfig vco-configurator.


If the service reports Off, enable an automatic restart of the vRealize Orchestrator user interface service upon subsequent reboots of the vRealize Automation appliance using the following command: chkconfig vco-configurator on.

Verify the status of vRealize Orchestrator user interface using the following command: chkconfig vco-configurator status.

Repeat this procedure and configure vRealize Orchestrator for vra01svr01b.rainpole.local and vra01svr01b.rainpole.local.

Re-Enable traffic to the secondary nodes and Health Monitoring for vRealize Automation on the Load Balancer

After you complete the upgrade of vRealize Automation, restore traffic distribution and health checks on the NSX load balancer, across the primary and secondary components of the vRealize Automation platform.

On the NSX load balancer, re-enable the secondary vRealize Automation nodes and select the monitor for the associated traffic in the pools.

Table 28. vRealize Automation Pool Members to Re-Enable on the NSX Load Balancer

Server Pool on the sfo01m01lb01 Load Balancer

Secondary Member to Re-Enable

Service Monitor to Re-Associate

vra-svr-443 According to which one is the pr node: vra01svr01a

vra01svr01b

vra01svr01c

vra-svr-443-monitor

vra-svr-8444 According to which one is the pr node: vra01svr01a

vra01svr01b

vra01svr01c

vra-svr-443-monitor

vra-iws-443 vra01iws01b vra-iws-443-monitor vra-ims-443 vra01ims01b vra-ims-443-monitor vra-vro-8283 vra01svr01a vra01svr01b vra01s vra-vro-8283-monitor




vsphere_admin_password




In the Navigator, click NSX Edges.

From the NSX Manager drop-down menu, select 172.16.11.65 and double-click sfo01m01lb01.

On the Load Balancer tab, click Pools.

Select the vra-svr-443 pool that is associated with the traffic to the vRealize Automation portal and click Edit.

In the Edit Pool dialog box, select the secondary node that you disabled before the upgrade, click Edit, select Enable from the State drop-down menu, and click OK.

In the Edit Pool dialog box, select vra-svr-443-monitor from the Monitors drop-down menu and click OK.

Repeat this procedure for the remaining load balancer pools.

Note: vRealize Automation appliances are upgraded in a distributed environment with three nodes vra01svr01a, vra01svr01b, and vra01svr01c. Ensure that both replicas health monitors are enabled.

What to do next Verify that vRealize Automation is operational after the upgrade. See Verification of vRealize Automation in the VMware Validated Design Operational Verification documentation.

Post-upgrade configuration of the Cloud Management Layer After you complete the upgrade of the Cloud Management Layer, perform the post-upgrade configuration changes to the environment according to the design objectives and deployment guidance to ensure your environment remains aligned to this VMware Validated Design.

Set the vRealize Automation database replication mode to synchronous

The embedded PostgreSQL database replication mode is set to asynchronous before the vRealize Automation upgrade. Set the database replication mode back to synchronous after upgrading the distributed vRealize Automation environment.


a Open a Web browser and go to https:/ /vra01svr01a.rainpole. local:5480

b Log in with username: root and password vra_appA_root_password.

Click the Cluster tab, and under Actions, click the Sync Mode button.

In the Sync State column, verify that all nodes show as Sync.

Replication mode shows Database is in Synchronous Mode. Automatic failover is now turned on!


Run test connection and verify the upgraded endpoints Upgrading vRealize Automation introduces changes to certain endpoints in the target environment. Perform a certificate validation by running a test connection for all applicable endpoints.

Table 29. Endpoints in vRealize Automation

Name Platform Type Address User Name sfo01w01vc01.sfo01.rainpole .local

vSphere(vCenter) https://sfo01w01vc01.sfo01. rainpole.local/sdk

rainpole\svc-vra

lax01w01vc01.lax01.rainpole .local

vSphere(vCenter) https://lax01w01vc01.lax01. rainpole.local/sdk

rainpole\svc-vra

SFO-NSX Endpoint NSX https://sfo01w01vc01.sfo01. rainpole.local

rainpole\svc-vra

LAX-NSX Endpoint NSX https://lax01w01vc01.lax01. rainpole.local

rainpole\svc-vra

vra01svr01.rainpole.local vRealize Orchestrator

https://vra01svr01.rainpole. local/vco

[email protected]

Procedure Log in to the vRealize Automation Rainpole portal.


https: / /vra01svr01.rainpole. local/vcac/org/rainpole .

b Log in to the rainpole.local domain with username: vra-admin-rainpole and password: vra-admin-rainpole_password.

Click the Infrastructure tab and in the navigator click Endpoints > Endpoints.

Perform a certificate validation for all endpoints.

a Select the sfo01w01vc01.sfo01.rainpole.local endpoint and click the Edit icon.

b Click Test connection.

c If a certificate prompt appears, click OK to accept the certificate.

Note: If a certificate prompt does not appear, the certificate might currently be stored in the trusted root authority of the Windows machine hosting the endpoint service, for example the proxy agent machine or DEM machine.

d Click OK to apply the certificate acceptance and save the endpoint.

e Repeat this step for the remaining endpoints.

Run NSX Network and Security Inventory Data Collection Run an NSX Network and Security Inventory data collection in the upgraded vRealize Automation environment. This data collection task is necessary to support the load balancer reconfiguration option in deployments.

https://sfo01w01vc01.sfo01.rainpole.local/sdk


https://lax01w01vc01.lax01/rainpole.local/sdk

https://lax01w01vc01.lax01/rainpole.local/sdk

https://sfo01w01vc01.sfo01/rainpole.local

https://sfo01w01vc01.sfo01/rainpole.local

https://lax01w01vc01.lax01/rainpole.local

https://lax01w01vc01.lax01/rainpole.local

https://vra01svr01.rainpole/local/vco

https://vra01svr01.rainpole/local/vco


Table 30. Endpoints in vRealize Automation

Name Platform Type Address User Name sfo01w01vc01.sfo01. rainpole.local

vSphere(vCenter) https://sfo01w01vc01.sfo01. rainpole.local/sdk

rainpole\svc-vra

lax01w01vc01.lax01. rainpole.local

vSphere(vCenter) https://lax01w01vc01.lax01. rainpole.local/sdk

rainpole\svc-vra

vra01svr01.rainpole.local vRealize Orchestrator https://vra01svr01.rainpole.local/vco [email protected]

Procedure Log in to the vRealize Automation Rainpole portal.


https: / /vra01svr01.rainpole. local/vcac/org/rainpole .

b Log in to the rainpole.local domain with username: vra-admin-rainpole and password: rainpole.local.

Click the Infrastructure tab and in the navigator click Endpoints > Endpoints.

Select the vra01svr01.rainpole.local vRealize Orchestrator endpoint to perform a data collection.

The Actions icon becomes available for the highlighted endpoint.

a Click Actions > Data Collection .

The endpoint name and status information appear.

b Click Start. Wait until the data collection completes. The process might take several minutes.

c Click Refresh and verify that the data collection completed successfully.

A data collection succeeded status message appears to indicate that the configuration process completed.

Select the sfo01w01vc01.sfo01.rainpole.local vSphere(vCenter) endpoint.

a Click Actions > View Compute Resources.

The Compute Resources page appears.

b Point over sfo01-w01-comp01, and from the menu select Data Collection.

c Configure the Compute Resource data collection specifications.

d Select On to enable data collection.

e Under the Inventory data collection, click Request Now.

f Under the State data collection, click Request Now.

g Under the Performance data collection, click Request Now.

h Under the Network and Security Inventory data collection, click Request Now to manually start data collection.

i Click Refresh and verify that the data collection completed successfully.



https://lax01w01vc01.lax01.rainpole.local/sd,

https://lax01w01vc01.lax01.rainpole.local/sd,

https://vra01svr01.rainpole.local/vco


A data collection succeeded status message appears to indicate that the configuration process completed.

j After the data collection process completes, click Cancel. k Repeat this step for the lax01w01vc01.lax01.rainpole.local vSphere(vCenter)

endpoint.

Enable Automatic Manager Service Failover After upgrading vRealize Automation, the Automatic Manager Service failover is disabled by default. You enable automatic Manager Service on the three vRealize Automation nodes.

Procedure Log in to the first vRealize Automation virtual appliance by using Secure Shell (SSH)

client.

a Open an SSH connection to vra01svr01a.rainpole. local . b Log in with username: root and password: root_password

Use Python to validate that failover is enabled on each Manager Service node.

a Navigate to the/usr/lib/vcac/tools/vami/commands directory.

b Run the following command: python ./manager-service-automatic-failover ENABLE.

c Verify that the system returns the following message: Enabling Manager Service automatic failover mode on node: IAAS_MANAGER_SERVICE_NODEID done

Log in to the virtual machine of the vRealize Automation IaaS Manager Service by using a Remote Desktop Protocol (RDP) client.

a Open an RDP connection to the vra01ims01a.rainpole. local virtual machine.

b Log in with username: rainpole\svc-vra and password: svc-vra_password.

Verify that failover mode is enabled on each Manager Service node by validating the Manager Service configuration file.

a Navigate to the vRealize Automation installation folder C:\Program Files

(x86)\VMware\vCAC\Server\.

b Open the ManagerService.exe.config file with a text editor.

c In the <appSettings> section, verify that the following elements are present.

<add key="FailoverModeEnabled" value="True" />

<add key="FailoverPingIntervalMilliseconds" value="30000" />

<add key="FailoverNodeState" value="active" />

<add key="FailoverMaxFailedDatabasePingAttepts" value="5" />


<add key="FailoverMaxFailedRepositoryPingAttepts" value="5" />

d Repeat this step for vra01ims01b.rainpole.local.

Enable vRealize Orchestrator Multi-Tenancy The upgraded vRealize Orchestrator instances are configured to run in a single-tenant mode. When you enable multi-tenancy, multiple vRealize Automation tenants can share the embedded vRealize Orchestrator cluster.

Important: To preserve a backwards compatibility, the multi-tenancy feature is disabled by default, as enabling it is irreversible. You cannot safely disable multi-tenancy in vRealize Orchestrator after it is enabled.

vRealize Orchestrator Instance IP Address FQDN Host A 192.168.11.51 vra01svr01a.rainpole.local Host B 192.168.11.52 vra01svr01b.rainpole.local Host C 192.168.11.50 vra01svr01c.rainpole.local

Procedure Log in to the vRealize Automation appliance by using Secure Shell (SSH) client.

a Open an SSH connection to vra01svr01a.rainpole. local . b Log in with username: root and password: vra_appA_root_password.

Stop the vRealize Orchestrator services, enable the multitenancy feature, and start the services.

a Run the following command to stop the vRealize Orchestrator server and Control

Center services: service vco-server stop && service vco-configurator stop.

b Navigate to the/var/lib/vco/tools/configuration-cli/bin directory using the following command: cd /var/lib/vco/tools/configuration-cli/bin

c Run the vro-configure.sh script to enable the multitenancy feature using the following command: ./vro-configure.sh enable-multi-tenancy.

d Run the following command to start the vRealize Orchestrator server and the Control Center services: service vco-server start && service vco-configurator start.

Repeat this procedure and configure vRealize Orchestrator multitenancy for vra01svr01b.rainpole.local and vra01svr01b.rainpole.local.

Delete the snapshots of the vRealize Automation virtual machines After completing the upgrade of vRealize Automation and verifying operations and functionality, delete the virtual machines snapshots.



Region Folder Role Virtual Machine Name Region A sfo01-m01fd-vra vRealize Automation Appliances vra01svr01a


vRealize Automation IaaS Web Servers vra01iws01a vra01iws01b

vRealize Automation IaaS Manager Service and DEM Orchestrators

vra01ims01a vra01ims01b

vRealize Automation IaaS DEM Workers vra01dem01a vra01dem01b

sfo01-m01fd-vraias vRealize Automation IaaS Proxy Agents sfo01ias01a sfo01-m01fd-vraias sfo01ias01b

Region B lax01-m01fd-vraias vRealize Automation IaaS Proxy Agents lax01ias01a lax01-m01fd-vraias lax01ias01b

Note: If you are using the designated Microsoft SQL Server vra01mssql01.rainpole.local covered within the VMware Validated Design, delete the snapshot taken for the vRealize Automation upgrade task.






In the Navigator, expand sfo01m01vc01.sfo01.rainpole.local>sfo01-m01dc>sfo01-m01fd-vra.

Right-click vra01svr01a and select Snapshots > Manage Snapshots.

Click the snapshot that you created before the vRealize Automation upgrade and click the Delete a VM Snapshot icon.


Repeat this procedure for the remaining vRealize Automation virtual machines.

Resume the replication of vRealize Automation After completing the upgrade of vRealize Automation, resume the replication task and allow the vRealize Automation virtual machines replication between Region A and Region B.




vRealize Automation Appliances vra01svr01a


vRealize Automation IaaS Web Servers vra01iws01a vra01iws01b

vRealize Automation IaaS Manager Service and DEM Orchestrators


vRealize Automation IaaS DEM Workers vra01dem01a vra01dem01b

Microsoft SQL Server vra01mssql01








Select all the vRealize Automation virtual machines, and click the Resume paused replication icon.


Click vSphere Replication and under Monitoring, verify that the replication status is OK for the following virtual machines.

Save a baseline for environment configuration drift of vRealize products in vRealize Suite Lifecycle Manager

vRealize Suite Lifecycle Manager uses the product baseline to generate configuration drift reports that show the difference between the current product configuration and the baseline configuration. You save a baseline to monitor each environment for a configuration drift.

Environment Task Cross-Region-Env Save Baseline SFO-Region-Env Save Baseline LAX-Region-Env Save Baseline







On the Home page, click Manage Environments.

In the Cross-Region-Env environment card, click the ellipsis on the top right corner and under Configuration Drift select Save Baseline.

In the Cross-Region-Env environment card, verify that a Baseline Save Initiated message appears.

Repeat this procedure for the remaining environments.

Re-configure the vRealize Log Insight agent on vRealize Business Reconfigure the vRealize Log Insight agent on each node to set log forwarding and maintain alignment with the VMware Validated Design.

Configure the vRealize Log Insight Linux agents on vRealize Business in Region A The vRealize Log Insight agent comes pre-installed on the vRealize Business virtual appliances. You edit the liagent.ini file to configure the agent to send events to the vRealize Log Insight server in Region A, set the communication protocol and port, and configure the flat file log collection.

After upgrading vRealize Business, reconfigure the liagent.ini agent configuration file on the vRealize Business server and on the vRealize Business data collector VM to reconnect to the vRealize Log Insight server in Region A.

Procedure Enable Secure Shell (SSH) on the vRealize Business appliances.

a Open a Web browser and go to the following URL.

vRealize Business Node Virtual Appliance Management Interface URL

vRealize Business Server Appliance https://vrb01svr01.rainpole.local:5480 vRealize Business Data Collector https://sfo01vrbc01.sfo01.rainpole.local:5480

b Log in with username: root and password: vrb_root_password.

c Click the Administration tab and click Administration.

d Under the Actions section, click Toggle SSH setting.

e Verify that SSH service status shows Enabled.


f Repeat this step to configure the sfo01vrbc01.sfo01.rainpole.local vRealize Business Data Collector.

Configure the vRealize Log Insight agent in the vRealize Business appliance.

a Open an SSH connection to the vRealize Business appliance using the following settings.

Setting Value Hostname vrb01svr01.rainpole.local

sfo01vrbc01.sfo01.rainpole.local

User name root Password vrb_root_password

b Back up the current liagent.ini file using the following command: cp /var/lib/loginsight-agent/liagent.ini /var/lib/loginsight-agent/liagent.bak

c Edit the liagent.ini file in a text editor using the following command: vi /var/lib/loginsight-agent/liagent.ini

d Modify the file to contain only the following data.

[server] hostname= sfo01vrli01.sfo01.rainpole.local proto = cfapi port = 9000 ssl = no [common|global] tags = {"product":"vrb", "agent_name":"vrb01svr01.rainpole.local"}

e Press Escape and enter:wq! to save the file.

f Start the Log Insight agent using the following command: systemctl restart liagentd.

g Verify that the Log Insight agent is running using the following command: systemctl status liagentd.

h Turn on autorun by default for the Log Insight agent using the following command: chkconfig liagentd on.

i Repeat this step to configure the sfo01vrbc01.sfo01.rainpole.local vRealize Business Data Collector.

Configure the vRealize Log Insight Linux agent on vRealize business in Region B

The vRealize Log Insight agent comes pre-installed on the vRealize Business virtual appliances. Edit the liagent.ini file to configure the agent to send events to the vRealize Log Insight server in Region B, set the communication protocol and port, and configure the flat file log collection.

After you upgrade vRealize Business, reconfigure the vRealize Log Insight agent configuration file on the vRealize Business data collector virtual machine to reconnect to the vRealize Log Insight server in Region B.


Procedure Enable Secure Shell (SSH) on the vRealize Business Data Collector appliance.

a Open a Web browser and go to the following URL:

https: / / lax01vrbc01.lax01.rainpole.local:5480

b Log in with username: root and password: vrb_root_password

c Click the Administration tab and click Administration.

d Under the Actions section, click Toggle SSH setting.

e Verify that SSH service status shows Enabled.

Configure the vRealize Log Insight agent in the vRealize Business appliance.

a Open an SSH connection to the vRealize Business appliance using the following settings.

Setting Value Hostname lax01vrbc01.lax01.rainpole.local User name root Password vrb_root_password

b Back up the current liagent.ini file using the following command: cp /var/lib/loginsight-agent/liagent.ini /var/lib/loginsight-agent/liagent.bak.

c Edit the liagent.ini file in a text editor using the following command: vi /var/lib/loginsight-agent/liagent.ini

d Modify the file to contain only the following data.

[server] hostname= lax01vrli01.lax01.rainpole.local proto = cfapi port = 9000 ssl = no [common|global] tags = {"product":"vrb", "agent_name":"lax01vrbc01.lax01.rainpole.local"}

e Press Escape and enter:wq! to save the file.

f Start the Log Insight agent using the following command: systemctl restart liagentd.

g Verify that the Log Insight agent is running using the following command: systemctl status liagentd.

h Turn on autorun by default for the Log Insight agent using the following command: chkconfig liagentd on.

Delete and re-create the agent groups for vRealize bBusiness in Region A and Region B

After the upgrade, you remove the old agent groups and re-create them to work with the new version of vRealize Business.


Setting Region A Value Region B Value vRealize Log Insight UI h t tps : / /s fo01vr l i01.s fo01 .ra inpole.

loca l h t tps : / / lax01vr l i01. lax01. ra inpole. loca l

Hostname vrb01svr01.rainpole.local sfo01vrbc01.sfo01.rainpole.local

lax01vrbc01.lax01.rainpole.local



Click the configuration drop-down menu icon and select Administration.

Under Management, click Agents.

From the drop-down menu at the top, point to vRB - Agent Group from the Active Groups section and click the Delete icon.

In the Delete Agent Group dialog box, click Delete.

Create the agent group for vRealize Business appliances on vRealize Log Insight.

a From the drop-down menu on the top, select vRBC Appliance for v7.5 from the Available Templates section.

b Click Copy Template.

c In the Copy Agent Group dialog box, enter vRB v7.5 - Agent Group in the name text box and click Copy.

Filter Operator Values Hostname Matches vrb01svr01.rainpole.local sfo01vrbc01.sfo01.rainpole.local

d Click the Refresh icon and verify that all the hosts in the filter appear in the Agents list.

e Click Save New Group.

f Click the Dashboards tab, and under VMware - vRealize Business for Cloud click General - Overview to verify the configuration.

The dashboard shows log data from the vRealize Business for Cloud components.

Repeat the previous step with the Region B values.

https://sfo01vrli01.sfo01.rainpole/local

https://sfo01vrli01.sfo01.rainpole/local

https://lax01vrli01.lax01.rainpole.local/

https://lax01vrli01.lax01.rainpole.local/


5 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.

Table 33. Upgrade Sequence for the Business Continuity Layer in VMware Validated Design

Order Component Sub-Component 1 vSphere Storage APIs – Data Protection Based Backup Solution - 2 vSphere Replication Virtual Appliance in Region A -

Site Recovery Manager Instance in Region A

3 - 4 vSphere Replication Virtual Appliance in Region B - 5 Site Recovery Manager Instance 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 VMware Validated Design.

Perform the upgrade outside of the usual backup windows.

Prerequisites • Verify that your backup solution is compatible with vSphere 6.7 Update 1. 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 and 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.

Upgrade disaster recovery components Perform the Business Continuity Layer upgrade by upgrading the vSphere Replication appliance and Site Recovery Manager system in Region A. Then, repeat this operation in Region B.


Table 34. Management Disaster Recovery Nodes in the SDDC

Region Role IP Address Fully Qualified Domain Name Region A vSphere Replication 172.16.11.123 sfo01m01vrms01.sfo01.rainpole.local

Site Recovery Manager 172.16.11.124 sfo01m01srm01.sfo01.rainpole.local Region B vSphere Replication 172.17.11.123 lax01m01vrms01.lax01.rainpole.local

Site Recovery Manager 172.17.11.124 lax01m01srm01.lax01.rainpole.local

Prerequisites For vSphere Replication

• Download the vSphere Replication update VMWare-vSphere_Replication-8.1.1-build_number.iso file on the machine that you use to access the vSphere Web Client.

• Create a backup of each vSphere Replication appliance that has been configured as a pair.

• Verify that all services on the Management Platform Services Controller and Management vCenter Server virtual appliances are running.

• Review the release notes of the vSphere Replication version in this validated design.

For Site Recovery Manager

• Download the Site Recovery Manager update VMWare-srm-8.1.1-build_number.exe file.

• Create a backup of each Site Recovery Manager system that has been configured as a pair.

• Verify that all services on the Management Platform Services Controller and Management vCenter Server instances are running.

• For information about the prerequisites to upgrading Site Recovery Manager, see Prerequisites and Best Practices for Site Recovery Manager Upgrade in the Upgrading Site Recovery Manager documentation.

• Verity that the Windows operating system on each Site Recovery Manager virtual machine is updated with Microsoft KB2999226. See Site Recovery Manager Release Notes.

• Review the release notes of the Site Recovery Manager version in this validated design.

Upgrade the vSphere replication virtual appliance in Region A To upgrade vSphere Replication from version 6.5.1 to version 8.1.1, deploy a new vSphere Replication virtual appliance in the protected region, migrate existing settings, and remove the old vSphere Replication virtual appliance.

Prerequisites for upgrading the vSphere Replication virtual appliance in Region A To deploy a new vSphere Replication virtual appliance, your environment must satisfy certain hardware and software requirements.

https://docs.vmware.com/en/Site-Recovery-Manager/8.1/com.vmware.srm.install_config.doc/GUID-C9BD3EEA-73F3-4784-8D7A-EB281C69C4D0.html


Environment Prerequisites • Verify the vSphere Replication virtual appliance is operational in Region A.

• Verify that a current backup of the vSphere Replication appliance exists in Region A.

Software Requirements

• Before you install vSphere Replication, obtain the vSphere Replication software. Component Requirement Installation package Download the vSphere Replication VMWare-vSphere_Replication-8.1.1-build_number.iso

image and mount it on the machine that you use to access the vSphere Web Client.

• IP Addresses, Host Names, and Network Configuration

• Allocate a temporary static IP address and use the existing network configuration for the new vSphere Replication appliance deployment.

Table 35. Network Configuration of vSphere Replication in Region A

Setting Value Host name sfo01m01vrms01 Static IPv4 address 172.16.11.70 Subnet mask 255.255.255.0 Default gateway 172.16.11.253 DNS servers 172.16.11.5 FQDN sfo01m01vrms01.sfo01.rainpole.local Used ports 5480 NTP servers ntp.sfo01.rainpole.local

ntp.lax01.rainpole.local

Deployment prerequisites Verify that your environment satisfies the following prerequisites for the deployment of vSphere Replication.

Prerequisite Value Active Directory Verify that you have a parent active directory with the SDDC user roles configured

for the rainpole.local domain. The users and groups must be available in Region A and Region B.

Software Features Verify that the Platform Services Controller instances for Region A and Region B are connected to the Active Directory domain.

Deploy the new vSphere Replication virtual appliance in Region A Deploy the new vSphere Replication virtual appliance in the protected region.






Rename the existing vSphere Replication appliance and take a snapshot of the virtual machine.

a In the Navigator pane, click VMs and Templates.

b Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-m01dc data center, and expand the sfo01-m01fd-bcdr folder.

c Right-click the sfo01m01vrms01 virtual machine and select Rename.

d Enter sfo01m01vrms01_old as the new name of the virtual machine and click OK.

e Right-click the sfo01m01vrms01_old virtual machine and select Snapshots > Take Snapshot.

f In the Take Snapshot dialog box, click Yes.

g In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Business Continuity

Layer Upgrade Description -

Snapshot the virtual machine's memory Deselected Quiesce guest file system (needs VMware Tools installed)

Deselected

In the Navigator pane, click Hosts and Clusters.

Right-click sfo01m01vc01.sfo01.rainpole.local and select Deploy OVF Template.

Deploy the new vSphere Replication virtual appliance.

a On the Select template page, click the Browse button.

b Navigate to the bin folder of the mounted VMware-vSphere_Replication-8.1.1-build_number.iso file on your computer, select the following files, click Open, and click Next.

vSphere_Replication_OVF10.ovf

vSphere_Replication-support.vmdk

vSphere_Replication-system.vmdk

c On the Select name and location page, configure the following settings and click Next.



Setting Value Name sfo01m01vrms01 vCenter Server sfo01m01vc01.sfo01.rainpole.local Data center sfo01-m01dc Folder sfo01-m01fd-bcdr

d On the Select a resource page, select the sfo01-m01-mgmt01 cluster and click Next.

e On the Review details page, click Next. f On the Accept license agreements page, click Accept and click Next. g On the Select configuration page, leave the default 4 vCPU configuration and click

Next. h On the Select storage page, enter the following settings and click Next.

Setting Value Select virtual disk format Thin provision VM Storage Policy vSAN Default Storage Policy Datastore sfo01-m01-vsan01

i On the Select networks page, select the following settings and click Next.

Setting Value Management Network Destination sfo01-m01-vds01-management IP protocol IPv4 IP allocation Static - Manual

j On the Customize template page, configure the following settings and click Next.

Setting Value Hostname sfo01m01vrms01.sfo01.rainpole.local NTP servers ntp.sfo01.rainpole.local,ntp.lax01.rainpole.local Enter password vr_sfo_root_password Confirm password vr_sfo_root_password Default gateway 172.16.11.253 Domain name sfo01.rainpole.local DNS 172.16.11.5,172.16.11.4 DNS search path sfo01.rainpole.local Management network IP address 172.16.11.70 Management network netmask 255.255.255.0

k On the vService bindings page, click Next. l On the Ready to complete page, click Finish.

Add a dedicated network adapter for replication traffic.

a Right-click the sfo01m01vrms01 virtual machine and select Edit Settings.


b In the Edit Settings dialog box, from the New device drop-down menu, select Network, and click Add.

c From the New Network device drop-down menu, select Show more networks, select sfo01-m01-vds01-replication, and click OK.

d In the Edit Settings dialog box, click OK.

(Optional) If replication traffic for Availability Zone 2 is configured, add a dedicated network adapter to handle replication traffic to Availability Zone 2.

a Right-click the sfo01m01vrms01 virtual machine and select Edit Settings.


c From the New Network device drop-down menu, select Show more networks, select sfo02-m01-vds01-replication, and click OK.


Upgrade the vSphere Replication Virtual Appliance in Region A Deploy ta new vSphere Replication appliance in Region A and migrate the settings from the old vSphere Replication appliance.





Upgrade the vSphere Replication Virtual Appliance.

a In the Navigator, click VMs and Templates and expand the sfo01m01vc01.sfo01.rainpole.local tree.

b Expand the sfo01-m01dc data center, select the sfo01-m01fd-bcdr folder and locate the sfo01m01vrms01 virtual machine.

c Right-click the sfo01m01vrms01 virtual machine and select Power > Power On.

The vSphere Replication virtual appliance powers on.

d Right-click sfo01m01vrms01 and select Open Console.

e Select 3 Upgrade and press Enter. f In the Please enter old VR appliance root password dialog box, enter

vr_sfo_root_password of the old vSphere Replication virtual appliance and press Enter. The upgrade process starts. During this process, the old vSphere Replication appliance is powered off automatically.

g In the Please enter SSO admin username dialog box, enter [email protected] and click OK.



h In the Please enter SSO admin password dialog box, enter svc-vr_password and click OK.

Upon successful upgrade, virtual machine and application configuration from the existing vSphere Replication appliance is applied to the new vSphere Replication virtual appliance.

Verify that the correct configuration settings are applied in the Virtual Appliance Management Interface (VAMI) of the new vSphere Replication appliance.


https: / /sfo01m01vrms01.sfo01.rainpole.local:5480 .

b Log in with username: root and password: vr_sfo_root_password

c On the VR tab, click Configuration and verify the following settings.

Setting Value Configuration Mode Configure using the embedded database. LookupService Address sfo01psc01.sfo01.rainpole.local SSO Administrator [email protected] Password svc-vr_password VRM Host 172.16.11.123 VRM Site Name sfo01m01vc01.sfo01.rainpole.local vCenter Server Address sfo01m01vc01.sfo01.rainpole.local vCenter Server Port 80 vCenter Server Admin Mai vcenter_server_admin_email IP Address for Incoming St Traffic

172.16.16.71

VRM service running Tomcat service running

Verify that the correct configuration settings are applied on the new vSphere Replication virtual machine in vCenter Server.


https: / /sfo01m01vc01.sfo01.rainpole.local /vsphere-cl ient .


c From the Home menu, select Site Recovery and under sfo01m01vc01.sfo01.rainpole.local, verify that vSphere Replication shows OK status .

Delete the virtual machine of the old vSphere Replication instance in Region A

After a successful upgrade, you delete the virtual machine of the old vSphere Replication instance.







In the Navigator, click VMs and Templates and expand the sfo01m01vc01.sfo01.rainpole.local tree.

Expand the sfo01-m01dc data center, select the sfo01-m01fd-bcdr folder, and locate the sfo01m01vrms01_old virtual machine.

Right-click the sfo01m01vrms01_old virtual machine and select Delete from Disk.

In the Confirmation dialog box, click Yes.

Upgrade Site Recovery Manager in Region A After you upgrade vSphere Replication in Region A, proceed with the Site Recovery Manager upgrade in Region A.





Take a snapshot of the Site Recovery Manager Windows virtual machine.

a In the Navigator, click VMs and Templates and expand the sfo01m01vc01.sfo01.rainpole.local tree.

b Expand the sfo01-m01dc data center, select the sfo01-m01fd-bcdr folder, and locate the sfo01m01srm01 virtual machine.

c Right-click sfo01m01srm01 and select Snapshots > Take Snapshot. d In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting Value Name VMware Validated Design 5.0.1 Business Continuity Layer

Upgrade Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools installed)

Deselected

Log in to the Site Recovery Manager virtual machine by using a Remote Desktop Protocol (RDP) client.

a Open an RDP connection to sfo01m01srm01.sfo01.rainpole. local . b Log in with username: Windows administrator user and password:

Windows_administrator_password.




Copy the upgrade VMware-srm-8.1.1-build_number.exe file to the sfo01m01srm01 virtual machine.

To start the VMware Site Recovery Manager installation wizard, right-click the.exe file and select Run as Administrator.

On the Select Language dialog box, click OK.

On the Welcome page, click Next.

On the VMware Patents page, click Next.

On the End User License Agreement page, select I agree to the terms in the license agreement, and click Next.

On the Installation Prerequisites page, click Next.

On the vSphere Platform Services Controller page, verify that the following settings are accurate, reenter the svc-srm_password, and click Next.

Setting Value Address sfo01psc01.sfo01.rainpole.local HTTPS Port 443 User name [email protected] Password svc-srm_password

In the Platform Services Controller Certificate dialog box, review the details of the certificate and click Accept.

On the VMware vCenter Server page, validate that the settings for sfo01m01vc01.sfo01.rainpole.local are correct, and click Next.

In the vCenter Server Certificate dialog box, review the details of the certificate and click Accept.

On the Site Recovery Manager Extension page, verify that the following settings are configured and click Next.

Setting Value Administrator email srm_admin_sfo_email_address Local Host 172.16.11.124 Listener Port 9086 Site Recovery Manager User Interface Port 443

In the Your Site Recovery Manager extension is already registered dialog box, click Yes.

In the Existing Site Recovery Manager registrations dialog box, click Yes.

On the Certificate Type page, select Use existing certificate and click Next.


On the Embedded Database Configuration page, reenter the Site Recovery Manager database password, validate the following settings, and click Next.

Setting Value Data Source Name SRM_SITE_SFO Database User Name srm_db_admin Database Password srm_db_admin_sfo_password Database Port 5678 Connection Count 5 Max. Connections 20

On the Site Recovery Manager Service Account page, ensure the Use Local System account is selected and click Next.

On the Ready to Install the Program page, click Install.

On the Install Shield Wizard Completed page, click Finish.

After you upgrade Site Recovery Manager, close all browser sessions to vSphere Web Client and clear the browser cache.

Verify the version of Site Recovery Manager plug-in.



c From the Home menu, select Administration.

d In the Navigator pane, under Solutions, click Client Plug-Ins.

e In the Client Plug-Ins section, verify that the VMware Site Recovery plug-in versions corresponds to the upgraded version.

f If the VMware Site Recovery Manager client plug-in does not appear, open an SSH connection to sfo01m01vc01.sfo01.rainpole.local and restart the vSphere Web Client service by running the following commands: service-control --stop vsphere-client service-control --start vsphere-client

Upgrade the vSphere replication in Region B Continue your upgrade of the disaster recovery components in the SDDC. After you upgrade the vSphere Replication and Site Recovery Manager in Region A, upgrade the vSphere Replication virtual appliance in Region B.

Prerequisites for upgrading the vSphere replication virtual appliance in Region B To deploy a new vSphere Replication virtual appliance, your environment must satisfy certain hardware and software requirements.



Environment Prerequisites • Verify that the vSphere Replication virtual appliance operational in Region B.

• Verify that a current backup of the vSphere Replication appliance exists in Region B.

Software requirements Before you install vSphere Replication, make sure that you have the following configuration available in your environment.

Component Requirement Installation package Download the vSphere Replication VMWare-

vSphere_Replication-8.1.1-build_number.iso image and mount it on the machine that you use to access the vSphere Web Client.

IP addresses, host names, and network configuration Allocate a temporary static IP address and use the existing network configuration for the new vSphere Replication appliance deployment.

Table 36. Network Configuration of vSphere Replication in Region B

Setting Value Host name lax01m01vrms01 Static IPv4 address 172.17.11.70 Subnet mask 255.255.255.0 Default gateway 172.1.11.253 DNS servers 172.17.11.5 FQDN lax01m01vrms01.lax01.rainpole.local Used ports 5480 NTP servers ntp.lax01.rainpole.local

ntp.sfo01.rainpole.local

Deployment prerequisites Verify that your environment satisfies the following prerequisites for the deployment of vSphere Replication.

Prerequisite Value Active Directory Verify that you have a parent active directory with the SDDC user roles

configured for the rainpole.local domain. The users and groups must be available in Region A and Region B.

Software Features Verify that the Platform Services Controller instances for Region A and Region B are connected to the Active Directory domain.


Deploy the new vSphere Replication virtual appliance in Region B Deploy the new vSphere Replication virtual appliance in the recovery region.

Procedure Log in to the Management vCenter Server by using the vSphere Client.


to https: / / lax01m01vc01.lax01.rainpole.local /vsphere-client .


Rename the existing vSphere Replication appliance and take a snapshot of the virtual machine.

a In the Navigator pane, click VMs and Templates.

b Expand the lax01m01vc01.lax01.rainpole.local tree, double-click the lax01-m01dc data center, and expand the lax01-m01fd-bcdr folder.

c Right-click lax01m01vrms01 and select Rename.

d Enter lax01m01vrms01_old as the new name of the virtual machine and click OK.

e Right-click the lax01m01vrms01_old virtual machine and select Snapshots > Take Snapshot.

f In the Take Snapshot dialog box, click Yes.

g In the Take VM Snapshot dialog box, enter the following settings and click OK.


Upgrade Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools installed)

Deselected

In the Navigator pane, click Hosts and Clusters.

Right-click lax01m01vc01.lax01.rainpole.local and select Deploy OVF Template.

Deploy the new vSphere Replication virtual appliance.

a On the Select template page, click the Browse button.

b Navigate to the bin folder of the mounted VMware-vSphere_Replication-8.1.1-build_number.iso file on your computer, select the following files, click Open, and click Next. vSphere_Replication_OVF10.ovf

vSphere_Replication-support.vmdk

vSphere_Replication-system.vmdk



c On the Select name and location page, configure the following and click Next.

Setting Value Name lax01m01vrms01 vCenter Server lax01m01vc01.lax01.rainpole.local Data center lax01-m01dc Folder lax01-m01fd-bcdr

d On the Select a resource page, select the lax01-m01-mgmt01 cluster and click Next.

e On the Review details page, click Next. f On the Accept license agreements page, click Accept and click Next. g On the Select configuration page, leave the default 4 vCPU selected and click

Next. h On the Select storage page, enter the following settings and click Next.

Setting Value Select virtual disk format Thin provision VM Storage Policy vSAN Default Storage Policy Datastore lax01-m01-vsan01

i On the Select networks page, select the following settings and click Next.

Setting Value Management network destination lax01-m01-vds01-management IP protocol IPv4 IP allocation Static - Manual

j On the Customize template page, enter the following settings and click Next.

Setting Value Hostname lax01m01vrms01.lax01.rainpole.local NTP servers ntp.lax01.rainpole.local,ntp.sfo01.rainpole.local Enter password vr_lax_root_password Confirm password vr_lax_root_password Default gateway 172.17.11.253 Domain name lax01.rainpole.local DNS 172.17.11.5,172.17.11.4 DNS search path lax01.rainpole.local Management network IP address 172.17.11.70 Management network netmask 255.255.255.0

k On the vService bindings page, click Next. l On the Ready to complete page, click Finish.

Add a dedicated network adapter for replication traffic.


a Right-click the lax01m01vrms01 virtual machine and select Edit Settings.


c From the New Network device drop-down menu, select Show more networks, select lax01-m01-vds01-replication, and click OK.


Upgrade the vSphere Replication virtual appliance in Region B Deploy the new vSphere Replication appliance in Region B and migrate the settings from the old vSphere Replication appliance.





Upgrade the vSphere Replication.

a In the Navigator, click VMs and Templates and expand the lax01m01vc01.lax01.rainpole.local tree.

b Expand the lax01-m01dc data center, select the lax01-m01fd-bcdr folder and locate the lax01m01vrms01 virtual machine.

c Right-click the lax01m01vrms01 virtual appliance and select Power > Power On.

The vSphere Replication virtual appliance powers on.

d Right-click lax01m01vrms01 and select Open Console.

e Select 3 Upgrade and press Enter. f In the Please enter old VR appliance root password dialog box, enter

vr_lax_root_password for the old vSphere Replication appliance and hit Enter. The upgrade process starts. During this process, the old vSphere Replication appliance is powered off automatically.

g In You need to manually reconfigure pairings with addresses: sfo01m01psc01.sfo01rainpole.local; dialog box hit Enter to acknowledge the message.

h In the Please enter SSO admin username dialog box, enter [email protected] and select OK.

i In the Please enter SSO admin password dialog box, enter svc-vr_password and select OK.

When the upgrade completes successfully, configurations including the network settings of the old vSphere Replication appliance are migrated to the new vSphere Replication appliance.

Verify that the correct configuration settings are applied in the Virtual Appliance Management Interface (VAMI) of the new vSphere Replication appliance.




https: / / lax01m01vrms01.lax01.rainpole.local:5480 and Log in with username:

b Log in with username: root and password vr_lax_root_password.

c On the VR tab, click Configuration and verify the following settings.

Setting Value Configuration Mode Configure using the embedded database. LookupService Address lax01psc01.lax01.rainpole.local SSO Administrator [email protected] Password svc-vr_password VRM Host 172.17.11.123 VRM Site Name lax01m01vc01.lax01.rainpole.local vCenter Server Address lax01m01vc01.lax01.rainpole.local vCenter Server Port 80 vCenter Server Admin Mail vcenter_server_admin_email IP Address for Incoming Storage Traffic 172.17.11.123 VRM service running Tomcat service running

Verify that the configuration settings are applied properly on the new vSphere Replication virtual machine in vCenter Server.


https: / / lax01m01vc01.lax01.rainpole.local /vsphere-cl ient .


c From the Home menu, select Site Recovery and under lax01m01vc01.lax01.rainpole.local, verify that vSphere Replication shows OK status.

Delete the virtual machine of the old vSphere replication instance in Region B

After a successful upgrade, you delete the virtual machine of the old vSphere replication instance.





In the Navigator, click VMs and Templates and expand the lax01m01vc01.lax01.rainpole.local tree.




Expand the lax01-m01dc data center, select the lax01-m01fd-bcdr folder, and locate the lax01m01vrms01_old virtual machine.

Right-click the lax01m01vrms01_old virtual machine and select Delete from Disk.

In the Confirmation dialog box, click Yes.

Upgrade Site Recovery Manager in Region B After you upgrade vSphere Replication in Region B, upgrade the Site Recovery Manager system in Region B.





Take a snapshot of the Site Recovery Manager virtual machine in Region B.

a In the Navigator, click VMs and Templates and expand the lax01m01vc01.lax01.rainpole.local tree.

b Expand the lax01-m01dc data center, select the lax01-m01fd-bcdr folder, and locate the lax01m01srm01 virtual machine.

c Right-click lax01m01srm01 and select Snapshots > Take Snapshot. d In the Take VM Snapshot dialog box, enter the following settings and click OK.



Deselected

Log in to the Site Recovery Manager virtual machine by using a Remote Desktop Protocol (RDP) client.

a Open an RDP connection to the virtual machine

lax01m01srm01.lax01.rainpole.local . b Log in with username: Windows administrator user and password:

Windows_administrator_password

Copy the upgrade VMware-srm-8.1.1-build_number.exe file to the lax01m01srm01 virtual machine.

To start the VMware Site Recovery Manager installation wizard, right-click the.exe file and select Run as Administrator.



In the Select Language dialog box, click OK.

On the Welcome page, click Next.

On the VMware Patents page, click Next.

On the End User License Agreement page, select I agree to the terms in the license agreement, and click Next.

On the Installation Prerequisites page, click Next.

On the vSphere Platform Services Controller page, verify that the following settings are accurate, reenter the svc-srm_password, and click Next.

Setting Value Address lax01psc01.lax01.rainpole.local HTTPS Port 443 Username [email protected] Password svc-srm_password

If prompted, in the Platform Services Controller Certificate dialog box, review the details of the certificate and click Accept.

On the VMware vCenter Server page, validate that the settings for lax01m01vc01.lax01.rainpole.local are correct, and click Next.

In the vCenter Server Certificate dialog box, review the details of the certificate and click Accept.

On the Site Recovery Manager Extension page, verify that the following settings are configured and click Next.

Setting Value Administrator email srm_admin_sfo_email_address Local Host 172.17.11.124 Listener Port 9086 Site Recovery Manager User Interface Port 443

In the Your Site Recovery Manager extension is already registered dialog box, click Yes.

In the Existing Site Recovery Manager registrations dialog box, click Yes .

On the Certificate Type page, select Use existing certificate and click Next.

On the Embedded Database Configuration page, reenter the Site Recovery Manager database password, validate the following settings, and click Next.

Setting Value Data Source Name SRM_SITE_LAX Database User Name srm_db_admin


Setting Value Database Password srm_db_admin_lax_password Database Port 5678 Connection Count 5 Max. Connections 20

On the Site Recovery Manager Service Account page, ensure the Use Local System account is selected and click Next.

On the Ready to Install the Program page, click Install.

On the InstallShield Wizard Completed page, click Finish to exit the wizard.

After you upgrade the Site Recovery Manager, close all browser sessions to the vSphere Web Client and clear the browser cache.

Check for the latest Site Recovery Manager plug-in in the vSphere Web Client.

a Open a Web browser and go to https: / / lax01m01vc01.lax01.rainpole.local /vsphere-client .

b Log in with username: [email protected] and vsphere_admin_password.

c From the Home menu, select Administration.

d In the Navigator pane, under Solutions, click Client Plug-Ins.

e In the Client Plug-Ins section, verify that the VMware Site Recovery plug-in appears with the upgraded version.

f If the VMware Site Recovery Manager client plug-in does not appear, open an SSH connection to lax01m01vc01.lax01.rainpole.local and restart the vSphere Web Client service by running the following commands: service-control --stop vsphere-client service-control --start vsphere-client

Reconnect the vSphere replication and Site Recovery Manager instances between the protected and the recovery sites

After you have successfully upgraded vSphere Replication and Site Recovery Manager in Region A and Region B, you must reconnect the protected and the recovery site pair to reenable disaster recovery protection for the management components of the SDDC.





From the Home menu, select Site Recovery.

On the Site Recovery page, locate the sfo01m01vc01.sfo01.rainpole.local site and click OPEN Site Recovery.




The Site Recovery home page opens.

On the Site Recovery home page, under the dual region site pair, click the View Details button.

Reconnect the Site Recovery Manager instances between the sfo01m01vc01.sfo01.rainpole.local and lax01m01vc01.lax01.rainpole.local sites.

a On the Site Recovery home page, from the drop-down menu select

sfo01m01vc01.sfo01.rainpole.local. b Under the Site Pair tab, on the Summary page, click the Reconfigure Site Pair

button.

The Reconfigure Site Pair dialog box appears.

c On the Platform Services Controller page, under First site, select sfo01m01vc01.sfo01.rainpole.local.

d On the Platform Services Controller page, under Second site, select Platform Services Controller, enter the following settings, and click Next.

Setting Value PSC host name lax01psc01.lax01.rainpole.local PSC port 443 User name [email protected] Password svc-srm_password

e In the Security Alert dialog box, review the certificate thumbprint for lax01psc01.lax01.rainpole.local and click Connect.

f On the Services to reconfigure page, under Second site, select lax01psc01.lax01.rainpole.local.

g On the Services to reconfigure page, under Select the services you want to recofigure, select Site Recovery Manager and click Next

h On Ready to complete page, validate the settings and click Finish.

Under the Site Pair tab, on the Summary page, Remote SRM connection shows Connected state for the sfo01m01vc01.sfo01.rainpole.local and lax01m01vc01.lax01.rainpole.local sites

Reconnect the vSphere Replication instances between the sfo01m01vc01.sfo01.rainpole.local and lax01m01vc01.lax01.rainpole.local sites.

a On the Site Recovery home page, from the drop-down menu select

sfo01m01vc01.sfo01.rainpole.local. b Under the Site Pair tab, on the Summary page, click the Reconfigure Site Pair

button.

The Reconfigure Site Pair dialog box appears.

c On the Platform Services Controller page, under First site, select sfo01m01vc01.sfo01.rainpole.local.

d On the Platform Services Controller page, under Second site, select Platform Services Controller, enter the following settings, and click Next.


Setting Value PSC host name lax01psc01.lax01.rainpole.local PSC port 443 User name [email protected] Password svc-vr_password

e In the Security Alert dialog box, review the certificate thumbprint for lax01psc01.lax01.rainpole.local and click Connect.

f On the Services to reconfigure page, under Second site, select lax01psc01.lax01.rainpole.local.

g On the Services to reconfigure page, under Select the services you want to recofigure, select vSphere Replication and click Next

h On Ready to complete page, review the settings and click Finish.

Under the Site Pair tab, on the Summary page, Remote VR connection shows Connected state for the sfo01m01vc01.sfo01.rainpole.local and lax01m01vc01.lax01.rainpole.local sites


6 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.

Table 37. Upgrade Sequence for the Virtual Infrastructure Layer in VMware Validated Design

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. You 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.

Table 38. NSX for vSphere Components in the SDDC

Region Role IP Address FQDN Region A NSX Manager for the management

cluster that is running as primary 172.16.11.65 sfo01m01nsx01.sfo01.rainpole.local

NSX Controller 1 for the management cluster

172.16.11.118 -

NSX Controller 2 for the management cluster

172.16.11.119 -


Region Role IP Address FQDN NSX Controller 3 for the management cluster

172.16.11.120 -

NSX Manager for the shared edge and compute cluster that is running as primary

172.16.11.66 sfo01w01nsx01.sfo01.rainpole.local

NSX Controller 1 for the shared edge and compute cluster

172.16.31.118 -


172.16.31.119 -


172.16.31.120 -

Region B NSX Manager for the management cluster th running as secondary

172.17.11.65 lax01m01nsx01.lax01.rainpole.local

NSX Manager for the shared edge and compute cluster that is running as secondary

172.17.11.66 lax01w01nsx01.lax01.rainpole.local

Note: You might receive several false alerts from vRealize Operations Manager and vRealize Log Insight during the NSX upgrade procedure.

Prerequisites • Download the NSX upgrade bundle, VMware-NSX-Manager-upgrade-bundle-6.4.4-

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.

a 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.

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-D824C743-8137-47F8-AF5D-C225CC8A2542.html

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-A539869B-9858-48B3-90ED-2336698EE386.html

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-A539869B-9858-48B3-90ED-2336698EE386.html


b 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

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

• Back up the NSX configuration and download the technical support logs.

• 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.

• Verify that each NSX controller is in normal, connected state.

• Verify that Host Preparation > Installation Status of all clusters has the green check mark and the proper NSX for vSphere version.

• 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 esx-n.

d Note the current version of the following VIB.

esx-nsxv

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.

Table 39. NSX Manager Nodes in the SDDC

Order Region NSX Manager Instance

NSX Appliance URL vCenter Server URL

1 Region A Primary NSX Manager For the management cluster

https://sfo01m01nsx01.sfo01.rainpole.local sfo01m01vc01.sfo01. rainpole.local

2 Region B Secondary NSX Manager for the management cluster

https://lax01m01nsx01.lax01.rainpole.local lax01m01vc01.lax01. rainpole.local

3 Region A Primary NSX Manager For the shared edge and compute cluster

https://sfo01w01nsx01.sfo01.rainpole.local sfo01m01vc01.sfo01. rainpole.local

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-4467950E-1E95-480C-A48B-D649368A42E3.html


Order Region NSX Manager Instance

NSX Appliance URL vCenter Server URL

4 Region B Secondary NSX Manager for the shared edge and compute cluster

https://lax01w01nsx01.lax01.rainpole.local lax01m01vc01.lax01. rainpole.local

Procedure Log in to the Management NSX Manager appliance user interface.


https: / /sfo01m01nsx01.sfo01.rainpole. local . b Log in with username: admin and password: nsx_manager_admin_password

Click Upgrade, and on the Upgrade page, click Upload Bundle.

In the Upgrade dialog box, click the Choose File button and navigate to the VMware-NSX-Manager-upgrade-bundle-6.4.4-build_number.tar.gz upgrade bundle on your file system.

Click Open and click Continue.

The NSX Manager starts uploading the upgrade bundle.

After the upload is complete, in the Upgrade dialog box, configure the following settings and click Upgrade.

Setting Value Do you want to enable SSH? Yes Do you want to join the VMware Customer Experience Yes

You are logged out of the NSX Manager user interface.

Log in to the Management NSX Manager appliance user interface.

a Open a Web browser and go to https: / /sfo01m01nsx01.sfo01.rainpole. local .

b Log in with username: admin and password: nsx_manager_admin_password

Click Upgrade and verify that the Upgrade tab shows the following configuration.

Setting Expected Value Upgrade State Complete Current Software Version 6.4.4-build_number








In the vSphere Web Client, check for the latest NSX plug-in.

a From the Home menu, select Administration.

b In the Navigator pane, under Solutions, click Client Plug-Ins.

c Verify that tha NSX plugins are upgraded to version 6.4.4.

Perform a fresh backup of the primary NSX Manager, sfo01m01nsx01.sfo01.rainpole.local.

Note: You cannot restore the new NSX Manager from previous backups.

To complete the NSX Manager upgrade in the management cluster, repeat the steps for the NSX Manager on Region B, lax01m01nsx01.lax01.rainpole.local.

Repeat the procedure for the shared edge and compute cluster.

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.

Note: If using Upgrade Coordinator for this validated design, do not use the One-Click option. You must 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.

Table 40. NSX Controller Nodes in Region A

Order Region NSX Manager NSX Manager IP Address

NSX Controller IP Address

1 Region A Primary NSX Manager for the management cluster

172.16.11.65 172.16.11.118 172.16.11.119 172.16.11.120

2 Region A Primary NSX Manager for the s edge and compute cluster

172.16.11.66 172.16.31.118 172.16.31.119 172.16.31.120






From the Home menu of the vSphere Web Client, select Networking and Security.

In the Navigator pane, under Networking and Security, click Installation and Upgrade.

Click the Upgrade tab, from the NSX Manager drop-down menu, select the 172.16.11.65 | Primary NSX Manager instance, and click Plan Upgrade.

On the Select Upgrade Plan page of the Upgrade Components wizard, select Plan Your Upgrade and click Next.

On the Plan Content page, configure the following settings and click Next.

Setting Value Select Components Clusters Deselected

Universal Logical Routers Deselected NSX Edges Deselected Service VMs Deselected

Define Pause Upgrade Options Pause between components Enabled Pause on error Enabled

On the Review Plan page, verify that Pause between components and Pause on error are set to Yes, and click Start Upgrade.

Monitor the progress of the upgrade of the NSX Controller nodes.

a From the Upgrade tab, click View Details. The Planned Controllers Upgrade Details dialog box shows the overall progress of the controller upgrade.

b From the Management tab, click NSX Controller Nodes and monitor the progress. The Upgrade Status column shows the following stages for each NSX Controller:

Status Controller Upgrade Stage Connected Not Started

Downloading Upgrade Downloading Upgrade Completed Upgrading

Service Unavailable Rebooting Connected Upgraded

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.



Setting Expected Value Status Connected Software Version 6.4.4.build_number

After all NSX Controllers have been upgraded, click Resume on the Upgrade tab.

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.

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.

Table 41. NSX Manager Instances and Associated Clusters

Region NSX Manager NSX Manager IP Address

Cluster

A Primary NSX Manager for the management cluster

172.16.11.65 sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc > sfo01-m01-mgmt01

Primary NSX Manager for the shared edge and compute cluster

172.16.11.66 sfo01w01vc01.sfo01.rainpole.local > sfo01-w01dc > sfo01-w01-comp01

B Secondary NSX Manager for the management cluster

172.17.11.65 lax01m01vc01.lax01.rainpole.local > lax01-m01dc > lax01-m01-mgmt01

Secondary NSX Manager for the shared edge and compute cluster

172.17.11.66 lax01w01vc01.lax01.rainpole.local > lax01-w01dc > lax01-w01-comp01

Prerequisites • Verify that vSphere DRS is enabled and set to Fully Automated on the clusters.

• Verify that vSphere vMotion functions correctly between the ESXi hosts in each cluster.

• Verify that all ESXi hosts are connected to vCenter Server.

• Verify that no ESXi hosts are in maintenance mode in vCenter Server.










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 Service VMs Deselected


On the Plan Host Clusters page, select the Group for newly added Clusters radio button, and click Edit.

In the Edit Upgrade Group dialog box, verify that the following settings are configured, click OK, and on the Plan Host Clusters page click Next.

Setting Expected Value Selected Objects sfo01-m01-mgmt01 Upgrade order Serial

On the Review Plan page, verify that Pause between components and Pause on error are set to Yes, and click Start Upgrade.

Validate that the NSX Controllers are running version 6.4.4.build_number, and click Resume to proceed to the upgrade of the next cluster.

Monitor the progress.

a 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.

b On 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.

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 check mark, with a VIB version of 6.4.4.build_number.


Repeat the steps to upgrade the NSX components on the remaining clusters in Region A and Region B.

When you perform the upgrade on a secondary node in Region B, enter user name [email protected] and password svc-nsxmanager_password in the Enter Secondary Manager Credentials dialog box, and click OK.

Upgrade the NSX Edge instances After 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.

Table 42. NSX Manager Instances and Associated Host Clusters

Region NSX Manager NSX Manager IP Address

Host Cluster

A Primary NSX Manager for the management cluster

172.16.11.65 sfo01-m01-mgmt01

Primary NSX Manager for the shared edge and compute cluster

172.16.11.66 sfo01-w01-comp01

B Secondary NSX Manager for the management cluster

172.17.11.65 lax01-m01-mgmt01

Secondary NSX Manager for the shared edge and compute cluster

172.17.11.66 lax01-w01-comp01

Table 43. NSX Edge Instances Upgrade Ordering for the Management Clusters

Order Management UDLR in Region A

Management Edge in Region A with Availability Zones

Management Edge in Region B

1 sfo01m01udlr01 - -

2 - sfo01m01esg01

sfo01m01esg02

If using multiple availability zones,

sfo02m01esg01

sfo02m01esg02

sfo01m01lb01

sfo01psc01

-

3 - - lax01m01esg01

lax01m01esg02

lax01m01lb01

lax01m01psc01


Order Management UDLR in Region A

Management Edge in Region A with Availability Zones

Management Edge in Region B

4 sfo01w01udlr01 - -

5 - sfo01w01dlr01

sfo01w01esg01

sfo01w01esg02

-

6 - - lax01w01dlr01

lax01w01esg01

lax01w01esg02



to ht tps :/ /s fo01m01vc01.sfo01.ra inpole. local/vsphere-c l ient / .





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 Service VMs Deselected


On the Universal Logical Routers page, select universal_routers_host_cluster, and click Edit.

In the Edit Upgrade Group dialog box, verify that the following settings are configured, click OK.




Setting Expected Value Selected Objects Management UDLR in Region A per NSX Edge Instances Upgrade order Serial

On the Plan NSX Edges page, select edge_host cluster, and click Edit.

In the Edit Upgrade Group dialog box, verify that the following settings are configured, click OK, and click Next.

Setting Expected Value 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.

On the Review Plan page, verify that Pause between components and Pause on error are set to Yes , and click Start Upgrade.

Verify that the NSX Controllers are of version 6.4.4.build_number , and click Resume to proceed to the universal logical router upgrade.

Monitor the progress.

a From the Upgrade tab, click View Details. In the Upgrade Plan Progress dialog box, you can monitor the overall progress of the Universal Logical Router upgrade.

b In the NSX Edges section under the Networking and Security in the left pane, the Deployment Status for UDLR changes to Busy as the UDLR is upgraded.

After a successful upgrade of the UDLR, select NSX Edges under Networking and Security, verify that the Deployment Status column for the edge device shows Deployed, and the Version column contains the upgraded version of 6.4.4.

Click the Upgrade tab again under Installation and Upgrade section, and click Resume to proceed with the NSX Edges upgrade.

Wait for upgrade of each NSX Edge instance by monitoring the progress.

After all the NSX Edge instances are upgraded, on the NSX Edges page under the Networking and Security, verify that the Deployment Status column for each edge device shows Deployed, and the Version column contains the upgraded version of 6.4.4.

On the Upgrade tab, under Installation and Upgrade, click Resume to close the wizard.

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.


Setting Value User name [email protected] Password svc-nsxmanager_user_ password Confirm password svc-nsxmanager_user_ password

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.

Upgrade the Management Cluster When you upgrade the virtual infrastructure layer of the SDDC, upgrade the components that support the management cluster first.

Upgrade the Management vCenter server and all Platform Services Controller instances in Region A and Region B 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. Then repeat this operation in Region B.

Table 44. Upgrade Sequence for the Management vCenter and Platform Services Controller Instances in the SDDC

Region Upgrade Order

Role IP Address Fully Qualified Domain Name

A 1 Management Platform Services Controller that is configured in a highly available pair

172.16.11.61 sfo01m01psc01.sfo01.rainpole.local

2 Compute Platform Services Controller that is configured in a highly available pair

172.16.11.63 sfo01w01psc01.sfo01.rainpole.local

3 Management vCenter Server 172.16.11.62 sfo01m01vc01.sfo01.rainpole.local

B 4 Management Platform Services Controller that is configured in a highly available pair

172.17.11.61 lax01m01psc01.lax01.rainpole.local

5 Compute Platform Services Controller that is configured in a highly available pair

172.17.11.63 lax01w01psc01.lax01.rainpole.local

6 Management vCenter Server 172.17.11.62 lax01m01vc01.lax01.rainpole.local

Because the Platform Services Controller instances for the management and for the shared edge and compute clusters are configured as highly available pairs, you follow a specific order when upgrading each component. 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.

The Platform Service Controller upgrade does not preserve or transfer the local user and group files from the previous PSC. Upon completion of the upgrade, you need to recreate the


local group and service account for VxRail that were established during the VxRail initialization. The accounts will need to be recreated after the upgrade of all PSCs.

Repeat this process for the Platform Services Controller instance for the shared edge and compute cluster.

Prerequisites

• Download the vCenter Server Appliance Installer VMware-VCSA-all-6.7.x-build_number.iso file locally to a windows host that has access to the management VLAN network.

• Review the release note of the vCenter Server version in this validated design.

• Verify that the management clusters do not have vSphere DRS set to Fully Automated.

• Verify that any integration with the Management vCenter Server instances in the environment has been quiesced of all activities. Such activities include but are not limited to users performing active backups of components or provisioning of new 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 in Region A and Region B

Before you perform the upgrade, take snapshots of the Management vCenter Server virtual appliance and the Platform Services Controller virtual appliances in Region A and Region B.

Region Folder Role Virtual Machine Name

A sfo01-m01fd-mgmt vCenter Server sfo01m01vc01 sfo01-m01fd-mgmt Platform Services Controller for the Management Cluster sfo01m01psc01 sfo01-m01fd-mgmt Platform Services Controller for the Shared Edge and

Compute Cluster sfo01w01psc01

B lax01-m01fd-mgmt vCenter Server lax01m01vc01 lax01-m01fd-mgmt Platform Services Controller for the Management Cluster lax01m01psc01 lax01-m01fd-mgmt Platform Services Controller for the Shared Edge and

Compute Cluster lax01w01psc01


Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/vsphere-

client/.


Log in with user name [email protected] and password vsphere_admin_password.

From the Home menu of the vSphere Web Client, click VMs and Templates.

Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-m01fd-mgmt data center, and expand the sfo01-m01fd-mgmt folder.

Right-click sfo01m01vc01 and select Snapshots > Take Snapshot.


Setting Value Name VMware Validated Design 5.0.1 Virtual Infrastructure


Deselected

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.

Upgrade the Platform Services Controller for the Management Cluster in Region A

Begin by upgrading the Platform Services Controller appliances in Region A. To keep the services provided by the Platform Services Controller instances running, you direct all network traffic to one instance while the other instance of the high availability pair is being upgraded.

Table 45. Platform Services Controller Instances in Region A

Role Virtual Machine Name Fully Qualified Domain Name Platform Services Controller for the management cluster

sfo01m01psc01 sfo01m01psc01.sfo01.rainpole.local

Platform Services Controller for the shared edge and compute cluster

sfo01w01psc01 sfo01w01psc01.sfo01.rainpole.local


Open a Web browser and go






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 the Edit button.

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 steps 4e to 4h 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.

Rename the sfo01m01psc01 virtual machine.

a From the Home menu of the vSphere Web Client, select Hosts and Clusters.

b Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-m01fd-mgmt data center, and expand the sfo01-m01fd-mgmt folder.

c Right-click sfo01m01psc01 and select Rename.

d Enter sfo01m01psc01_old as the new name of the virtual machine, and click OK.

On the Windows host that has access to your data center, mount the vCenter Server Appliance installer VMware-VCSA-all-6.7.x-build_number.iso.

Navigate to the\vcsa-ui-installer\win32 directory and start the installer.exe executable file.

The vCenter Server Appliance Installer starts.

On the Home page, click Upgrade.

Follow the prompts and configure the following settings for the first stage of the vCenter Server Appliance Installer.

Table 46. Upgrade - Stage 1: Deploy Platform Services Controller

Upgrade Wizard Page Setting Value Introduction - - End user license agreement

Read and accept the EULA, and click Next.

Connect to source appliance

Appliance FQDN or IP address sfo01m01psc01.sfo01.rainpole.local Appliance HTTPS port 443

Configure the settings and click Connect to source.


Upgrade Wizard Page Setting Value Appliance OS root password sfo01m01psc01_root_password ESXi host or vCenter Server nam sfo01m01vc01.sfo01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password

1 Configure the settings and click Next. 2 On the Certificate Warning dialog box, click Yes.

Appliance deployment target

ESXi host or vCenter Server nam sfo01m01vc01.sfo01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Select folder Folder sfo01-m01fd-mgmt Select compute resource Compute resource sfo01-m01-mgmt01 Set up target appliance VM

VM name sfo01m01psc01 Set root password sfo01m01psc01_root_password Confirm root password sfo01m01psc01_root_password

Select datastore Datastore sfo01-m01-vsan01 Enable thin disk mode Selected

Configure network settings

Network sfo01-m01-vds01-management IP version IPv4 IP assignment Static Temporary IP address 172.16.11.70 Subnet mask or prefix length 24 Default gateway 172.16.11.1 DNS servers 172.16.11.5,172.16.11.4

Configure the settings and click Connect to source. Ready to complete stage 1 Verify the configuration and click Finish.

Wait until the first stage of the vCenter Server Appliance Installer completes. The deployment process might take several minutes.

On the Upgrade - Stage 1: Deploy Platform Services Controller page, click Continue.

Follow the prompts and configure the following settings for the second stage of the vCenter Server Appliance Installer.


Table 47. Upgrade - Stage 2: Platform Services Controller Appliance

Upgrade Wizard Page Setting Value Introduction - - Connect to source PSC Single Sign-On user name [email protected]

Single Sign-On password vsphere_admin_password Source PSC appliance (OS) root password sfo01m01psc01_root_password ESXi host or vCenter Server user name [email protected] Password vsphere_admin_password

Configure the settings and click Next. Configure CEIP Join the VMware Customer Experience

Improvement Program (CEIP) Selected

Ready to complete I have backed up the source Platform Services Controller and all the required data from the database.

Selected

1 Review the new appliance configuration and click Finish.

2 On the Shutdown Warning dialog box, click Ok.

Wait until the second stage of the vCenter Server Appliance Installer completes. The process might take several minutes.

Create the local credentials for VxRail Administrative entitlements The new PSC did not preserve the local password or group files which include credentials required by VxRail Manager. In order to re-establish the VxRail Manager relationship with the SSO domain, you need to create the accounts on the new Platform Service Controller. The values of the accounts can be obtained from the /etc/password and /etc/groups files on the sfo01m01psc01_old VM.

Login into the management vCenter server and locate the original Platform Services Controller virtual appliance. ht tps :/ /s fo01m01vc01.sfo01.ra inpole. local/vsphere-c l ient / .

Locate sfo01m01psc01_old and edit the VM settings to disable the Network Adapted to avoid IP address conflict with the replacement VM.

Power on the VM

Connect to the VM through the vCenter Console and login to the Shell.

Confirm the entries by using the cat or grep command to locate the group and user details as illustrated in the screen capture below. Note, your user and group account names are likely be different than the example.



Open an SSH session to the replacement PSC sfo01m01psc01.sfo01.rainpole.local

Run the following commands to add the group and user

groupadd -g 59006 vxadmins

useradd vxadmin -u 1003 -g 59006 -d /home/vxadmin -s /bin/bash

Set the password of the vxadmin account to match the password of the original PSC

passwd vxadmin

Confirm that the credential has been re-established by logging into vCenter Administration “Users and Groups” and locating the vxadmin account under the localos identity source. Confirm that the account exists and is a member of the “VMware HCIA Manager” group.

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.


In the Navigator, select NSX Edges.

From the NSX Manager drop-down menu, select the 172.16.11.65 NSX Manager, and double-click the sfo01psc01 NSX Edge device.

On the Manage tab, click Load Balancer > Pools.

Select the psc-https-443 load balancer pool and click the Edit button.

In the Edit Pool dialog box, from the Members pane, select sfo01m01psc01, and click the Edit button.

In the Edit Member dialog box, from the State drop-down menu, select Enable, and click OK.

In the Edit Pool dialog box, click OK.

Repeat Steps 5 to 8 for the psc-tcp-389 load balancer pool.

On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-389 report status UP for sfo01m01psc01.

Repeat this procedure for the sfo01w01psc01.sfo01.rainpole.local Platform Services Controller instance in Region A.

Upgrade 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.






Rename the sfo01m01vc01 virtual machine.

a From the Home menu of the vSphere Web Client, select Hosts and Clusters. b Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-

m01fd-mgmt data center, and expand the sfo01-m01fd-mgmt folder. c Right-click sfo01m01vc01 and select Rename. d Enter sfo01m01vc01_old as the new name of the virtual machine, and click

OK.


a Navigate to the\vcsa-ui-installer\win32 directory and start the installer.exe executable file. The vCenter Server Appliance Installer starts.

b On the Home page, click Upgrade. c Follow the prompts and configure the following settings for the first stage of the

vCenter Server Appliance Installer.

Table 48. Upgrade - Stage 1: Deploy vCenter Server

Upgrade Wizard Page Setting Value

Introduction - - End user license agreement - -

Read and accept the EULA, and click Next. Connect to source appliance Appliance FQDN or IP address sfo01m01vc01.sfo01.rainpole.local

Appliance HTTPS port 443

Configure the settings and click Connect to source. Appliance OS root password sfo01m01vc01_root_password ESXi host or vCenter Server name sfo01m01vc01.sfo01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Appliance deployment target ESXi host or vCenter Server name sfo01m01vc01.sfo01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password





Select folder Folder sfo01-m01fd-mgmt Select compute resource Compute resource sfo01-m01-mgmt01 Set up target appliance VM VM name sfo01m01vc01

Set root password sfo01m01vc01_root_password Confirm root password sfo01m01vc01_root_password

Select Deployment Size Deployment size Small Storage size Default


Configure network settings Network sfo01-m01-vds01-management IP version IPv4 IP assignment Static Temporary IP address 172.16.11.70 Subnet mask or prefix length 24 Default gateway 172.16.11.1 DNS servers 172.16.11.5,172.16.11.4

Configure the settings and click Connect to source. Ready to complete stage 1 - -

Verify the configuration and click Finish.


On the Upgrade - Stage 1: Deploy vCenter Server page, click Continue.


Table 49. Upgrade - Stage 2: vCenter Server Appliance

Upgrade Wizard Page Setting Value Introduction - - Select upgrade data Configuration Selected Configure CEIP Join the VMware Customer Experience


Ready to complete I have backed up the source vCenter Server and all the required data from the database.

Selected





To ensure that the network access between vCenter Server and NSX is not blocked, exclude the newly upgraded vCenter Server Appliance from all distributed firewall rules.


to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / . b Log in with user name [email protected] and password

vsphere_admin_password. c From the Home menu of the vSphere Web Client, select Networking & Security. d In the Navigator pane, click Firewall Settings, and click the Exclusion List tab. e From the NSX Manager drop-down menu, select 172.16.11.65 | Primary. f Click the Add button. g From the Select VM(s) to include dialog box, select sfo01m01vc01, click the Add

icon, and click OK.

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

Role Virtual Machine Name Fully Qualified Domain Name Platform Services Controller for the management cluster

lax01m01psc01 lax01m01psc01.lax01.rainpole.local


lax01w01psc01 lax01w01psc01.lax01.rainpole.local


Open a Web browser and go to https: / / lax01m01vc01.lax01.rainpole.local /vsphere-client .


To direct all traffic to the Platform Services Controller for the Management cluster, disable the membership of the Platform Services Controller for the Shared Edge and Compute 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.17.11.65 NSX Manager,

and double-click the lax01psc01 NSX Edge device. d On the Manage tab, click Load Balancer > Pools. e Select the psc-https-443 load balancer pool and click the Edit button. f In the Edit Pool dialog box, from the Members pane, select lax01m01psc01, and

click the Edit button.




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 Steps 4e to 4h 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 lax01m01psc01.

Rename the lax01m01psc01 virtual machine.

a From the Home menu of the vSphere Web Client, select Hosts and Clusters. b Expand the lax01m01vc01.lax01.rainpole.local tree, double-click the lax01-m01dc

data center, and expand the lax01-m01fd-mgmt folder.

c Right-click lax01m01psc01 and select Rename.

d Enter lax01m01psc01_old as the new virtual machine, and click OK.


a Navigate to the\vcsa-ui-installer\win32 directory and start the installer.exe executable file.


b On the Home page, click Upgrade. c Follow the prompts and configure the following settings for the first stage of the

vCenter Server Appliance Installer.

Table 50. Upgrade - Stage 1: Deploy Platform Services Controller

Upgrade Wizard Page Setting Value Introduction - - End user license agreement Read and accept the EULA, and click Next. Connect to source appliance Appliance FQDN or IP address lax01m01psc01.lax01.rainpole.local


Configure the settings and click Connect to source. Appliance OS root password lax01m01psc01_root_password ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Appliance deployment target

ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password




Select folder Folder lax01-m01fd-mgmt Select compute resource Compute resource lax01-m01fd-mgmt Set up target appliance VM VM name lax01m01psc01

Set root password lax01m01psc01_root_password Confirm root password lax01m01psc01_root_password

Select datastore Datastore lax01-m01-vsan01 Enable thin disk mode Selected

Configure network settings Network lax01-m01-vds01-management IP version IPv4 IP assignment Static Temporary IP address 172.17.11.70 Subnet mask or prefix length 24 Default gateway 172.17.11.1 DNS servers 172.17.11.5,172.17.11.4

Configure the settings and click Connect to source. Ready to complete stage 1 Verify the configuration and click Finish.

d Wait until the first stage of the vCenter Server Appliance Installer completes. The deployment process might take several minutes.

e On the Upgrade - Stage 1: Deploy Platform Services Controller page, click Continue.

f Follow the prompts and configure the following settings for the second stage of the vCenter Server Appliance Installer.

Table 51. Upgrade - Stage 2: Platform Services Controller Appliance

Upgrade Wizard Page Setting Value Introduction - - Connect to source PSC Single Sign-On user name [email protected]

Single Sign-On password vsphere_admin_password Source PSC appliance (OS) root password

lax01m01psc01_root_password

ESXi host or vCenter Server user name [email protected] Password vsphere_admin_password

Configure CEIP Join the VMware's Customer Experience Improvement Program (CEIP)

Selected

Ready to complete I have backed up the source Platform Services Controller and all the required data from the database.

Selected




g Wait until the second stage of the vCenter Server Appliance Installer completes. The process might take several minutes.

Create the local credentials for VxRail Administrative entitlements The new PSC did not preserve the local password or group files which include credentials required by VxRail Manager. In order to re-establish the VxRail Manager relationship with the SSO domain, you need to create the accounts on the new Platform Service Controller. The values of the accounts can be obtained from the /etc/password and /etc/groups files on the lax01m01psc01_old VM.

Login into the management vCenter server and locate the original Platform Services Controller virtual appliance.

Edit the VM settings to disable the Network Adapted to avoid IP address conflict with the replacement VM.

Power on the VM

Connect to the VM through the vCenter Console and login to the Shell.

Confirm the entries by using the cat or grep command to locate the group and user details as illustrated in screen capture below. Note, your user and group account names are likely be different than the example.

Open an SSH session to the replacement PSC sfo01m01psc01.sfo01.rainpole.local

Run the following commands to add the group and user

groupadd -g 59006 vxadmins useradd vxadmin -u 1003 -g 59006 -d /home/vxadmin -s /bin/bash

Set the password of the vxadmin to match the original PSC

passwd vxadmin.

Confirm that the credential has been re-established by logging into vCenter Administration “Users and Groups” and locating the vxadmin account under the localos identity source. Confirm that the account exists and is a member of the “VMware HCIA Manager” group.

Restore traffic to the Platform Services Controller To restore traffic to the Platform Services Controller for the Management cluster, enable membership of the Platform Services Controller instance in the load balancer pools.



In the Navigator, select NSX Edges.

From the NSX Manager drop-down menu, select the 172.17.11.65 NSX Manager, and double-click the lax01psc01 NSX Edge device.

On the Manage tab, click Load Balancer > Pools.

Select the psc-https-443 load balancer pool and click the Edit button.

In the Edit Pool dialog box, from the Members pane, select lax01m01psc01, and click the Edit button.

In the Edit Member dialog box, from the State drop-down menu, select Enable, and click OK.

In the Edit Pool dialog box, click OK.

Repeat Steps 5 to 8 for the psc-tcp-389 load balancer pool.

On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-389 report status UP for lax01m01psc01.

Repeat this procedure for the lax01w01psc01.lax01.rainpole.local Platform Services Controller instance in Region B.

Upgrade vCenter Server for the Management Cluster in Region B After completing the upgrade of the Platform Services Controller instances in Region B, you continue by upgrading the vCenter Server for the management cluster in Region B.





Rename the lax01m01vc01 virtual machine.

a From the Home menu of the vSphere Web Client, select Hosts and Clusters. b Expand the lax01m01vc01.lax01.rainpole.local tree, double-click the lax01-

m01dc data center, and expand the lax01-m01fd-mgmt folder. c Right-click lax01m01vc01 and select Rename. d Enter lax01m01vc01_old as the new virtual machine name, and click OK.









Upgrade Wizard Page Setting Value Introduction - - End user license agreement - -

Read and accept the EULA, and click Next. Connect to source appliance Appliance FQDN or IP address lax01m01vc01.lax01.rainpole.local


Configure the settings and click Connect to source. Appliance OS root password lax01m01vc01_root_password ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Appliance deployment target ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Select folder Folder lax01-m01fd-mgmt Select compute resource Resource pool lax01-m01fd-mgmt Set up target appliance VM VM name lax01m01vc01

Set root password lax01m01vc01_root_password Confirm root password lax01m01vc01_root_password


Select datastore Datastore lax01-m01-vsan01 Enable thin disk mode Selected

Configure network settings Network lax01-m01-vds01-management IP version IPv4 IP assignment Static Temporary IP address 172.17.11.70 Subnet mask or prefix length 24 Default gateway 172.17.11.1 DNS servers 172.17.11.5,172.17.11.4

Configure the settings and click Connect to source.


Upgrade Wizard Page Setting Value Ready to complete stage 1 - -






Upgrade Wizard Page Setting Value Introduction - - Select upgrade data Configuration Selected Configure CEIP Join the VMware Customer Experience



Selected






to https: / / lax01m01vc01.lax01.rainpole.local /vsphere-client . b Log in with user name [email protected] and password

vsphere_admin_password. c From the Home menu of the vSphere Web Client, select Networking & Security. d In the Navigator pane, click Firewall Settings, and click the Exclusion List tab. e From the NSX Manager drop-down menu, select 172.17.11.65 | Primary. f Click the Add button. g From the Select VM(s) to include dialog box, select lax01m01vc01, click the Add

icon, and click Ok.

Delete the Obsolete vCenter Server and Platform Services Controllers Appliances in Region A and Region B

After you complete the upgrade of the management components in Region A and Region B, and validate their stability, remove the obsolete versions of the virtual appliances.



Region Folder Virtual Machine to Delete Region A sfo01-m01fd-mgmt sfo01m01vc01_old

sfo01m01psc01_old sfo01w01psc01_old

Region B lax01-m01fd-mgmt lax01m01vc01_old lax01m01psc01_old lax01w01psc01_old




From the Home menu of the vSphere Web Client, select VMs and Templates.


Right-click the sfo01m01vc01_old virtual machine and select Delete from Disk.

In the Confirmation dialog box, click Yes

Repeat the procedure for the remaining obsolete virtual machines in Region A and Region B.

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.

Table 54. VxRail Manager Systems in Region A

Region VxRail Manager IP Address vCenter Server Composite Package

A sfo01m01vxm01 172.16.11.65 sfo01m01vc01.sfo01.rainpole.local 4.7.001 4.7.111



Prerequisites

• Confirm that the VxRail Clusters are all in good health and have no alerts or warnings.

• Download the VxRail Composite Bundles software that will be used for this upgrade. There are two version of software required VxRail 4.7.001 and 4.7.111 or later.

• Download the following software packages from the dellemc.com support site VxRail 4.7.001 Composite Upgrade Package for 4.5.x and VxRail 4.7.111 Composite Upgrade Package for 4.7.x

• 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 Log in to the VxRail Manager instance supporting Management Cluster.


to https: / /sfo01m01vxm01.sfo01.rainpole. local .


Confirm that the cluster is in a healthy state prior to proceeding.

Select the dashboard icon from the list of management options and confirm the status is healthy with a green checkmark

Select the health tab and confirm there are not outstanding health issues with any of the hardware components.

Remediate any issues before proceeding.

Take a Snapshot of the VxRail Manager VMs in Region A

a Log into the Management vCenter Server at https://sfo01m01vc01.sfo01.rainpole.local 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.

Open a Web browser and go to https://sfo01m01vxm01.sfo01.rainpole.local

Log into the vSphere Web Client.

https://download.emc.com/downloads/DL91766_VxRail-4.7.001-Composite-Upgrade-Package-for-4.5.x.zip?source=OLS






Select the Config Icon

Click Local Upgrade.

In open file dialog, navigate to the upgrade composite package file, VXRAIL_COMPOSITE4.7.001-xxxxx_for_4.5.x.zip, previously downloaded and saved locally, and then click Open to select.

Monitor the progress until the upload has completed.

Click Continue to proceed with the upgrade.

Individual upgrade tasks can be monitored by expanding the details control located below the progress bar.

Monitor the progress until the upgrade has completed.

Amongst the other tasks performed during this upgrade was the update to the NSX VIB version on the ESXi host. Confirm that the esx-nsxv VIB installed has been updated from 6.5 to 6.7.

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.

Upon successful completion of the VVD 4.7.001 upgrade, repeat steps 2 – 7 using the VXRAIL_COMPOSITE-4.7.111-13048812_for_4.7.x composite software bundle.

When the VxRail cluster has been upgraded and validated with the 4.7.100 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.

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:

Table 55. 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

Service sfo01umds01

sfo01-m01fd-vra vRealize Automation IaaS Web Server vra01iws01a vra01iws01b

vRealize Automation IaaS Manager Service


vRealize Automation IaaS DEM Workers

vra01dem01a vra01dem01b

Microsoft SQL Server vra01mssql01


Cluster Name Folder Role Virtual Machine Name sfo01-m01fd-vraias vRealize Automation IaaS Proxy Agent sfo01ias01a

sfo01ias01b sfo01-m01fd-bcdr Site Recovery Manager sfo01m01srm01



Log in using the following credentials. Log in with user name [email protected] and password vsphere_admin_password.

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. 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.

New Baseline Group Wizard Page

Setting Value

Name Name VMware Tools for VMware Validated Design 5.0 Description -

Upgrades VM Hardware Upgrades None VMware Tools Upgrades VMware Tools Upgrade to Match Host

(Predefined) Ready to complete - -

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.

In the Attach Baseline or Baseline Group dialog box, under the Baseline Groups pane, select the VMware Tools for VMware Validated Design 5.0.1 baseline group, and click OK.

After you attach the baseline, click Scan for Updates.

In the Scan for Updates dialog box, under Scan for Updates, select only VMware Tools upgrades, and click OK.

After the scan is complete, the folder status is Non-Compliant.



Remediate the virtual machines and upgrade VMware Tools to ESXi 6.7 Update 1 Release.

a On the Update Manager tab, click Remediate.

b In the Remediate wizard, follow the prompts and configure the following settings.

Remediate Wizard Page

Setting Value

Select baselines Baseline groups VMware Tools for VMware Validated Design 5.0.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.0.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

Rollback Options Take a snapshot of the VMs before remediation to enable rollback.

Selected

Snapshot Retention Do not delete snapshots Snapshot name VMware Tools for VMware Validated

Design 5.0 Snapshot description -

Ready to complete Click Finish to begin the upgrade.

The Update Manager remediation process starts running and restarts the virtual machines.

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).

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.

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.

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.

Table 56. 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 Manager vCenter Server Composite Package

Region B lax01m01vxm01 172.17.11.65 sfo01m01vc01.sfo01.rainpole.local 4.7.001 4.7.111

Procedure Log in to the VxRail Manager instance supporting Management Cluster.

Open a Web browser and go to https: / /sfo01m01vxm01.sfo01.rainpole. local .



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.


a Log into the Management vCenter Server at https: / /sfo01m01vc01.sfo01.rainpole.local 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.

Open a Web browser and go to ht tps: / /s fo01m01vxm01.sfo01.ra inpole. local



https://sfo01m01vxm01.sfo01.rainpole.local/


Select the Config Icon.




Click Continue to proceed with the upgrade




If the VIB has not been upgraded, resolve that by synchronizing the host in NSX Manager.



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.

Upgrade vCenter Server for the Shared Edge and Compute Cluster in Region A and Region B

After you upgrade the components that support the management cluster in the SDDC, upgrade the Compute vCenter Server in Region A and repeat this operation in Region B.

Upgrading vCenter Server for the Shared Edge and Compute cluster is a single-step operation. Update the Compute vCenter Server in Region A and then repeat this operation in Region B.

Table 57. Compute vCenter Server Instances in the SDDC

Region Role IP Address Fully Qualified Domain Name Region A Compute vCenter Server 172.16.11.64 sfo01w01vc01.sfo01.rainpole.local Region B Compute vCenter Server 172.17.11.64 lax01w01vc01.lax01.rainpole.local


Prerequisites

• Download the vCenter Server Appliance upgrade VMware-VCSA-all-6.7.0-build_number.iso file locally to a windows host that has access to the management VLAN network.

• Verify that all compute ESXi hosts have the lockdown mode disabled during the upgrade.

• To automatically migrate edge and tenant workloads between hosts while they are upgraded, verify that vSphere DRS on the Shared Edge and Compute cluster is set to Fully Automated for the duration of the upgrade operations.

• Ensure that any integration with the Compute vCenter Server instances in the environment is quiesced of all activities. Such activities include but are not limited to users performing active backups of components or provisioning of new virtual machines by using vRealize Automation. Without quiescing the environment, rollback operations can be disrupted by orphaned objects that might be generated after you have taken snapshots. This may also result in extending the time of the maintenance windows.

• Verify that current backups of the Compute vCenter Server instances exist in both regions.

Take Snapshots of the vCenter Server Instances for the Shared Edge and Compute Clusters in Region A and Region B Before you start the upgrade of the vSphere components, take snapshots of the vCenter Server instances for the shared edge and compute clusters in Region A and Region B. If you must perform a rollback to the previous state, these snapshots accelerate a rollback operation.


Region Folder Virtual Machine Name Region A sfo01-m01fd-mgmt sfo01w01vc01 Region B lax01-m01fd-mgmt lax01w01vc01




From the Home menu of the vSphere Web Client, click VMs and Templates.


Right-click sfo01w01vc01 and select Snapshots > Take Snapshot.




Setting Value Name VMware Validated Design 5.0.1 Virtual Infrastructure L

Upgrade Description - Snapshot the virtual machine's memory Deselected Quiesce guest file system (Needs VMware Tools instal Deselected

Repeat the procedure for the vCenter Server appliance for the shared edge and compute cluster in Region B.

Upgrade vCenter Server for the Shared Edge and Compute Cluster in Region A After you upgrade the components for the management clusters, upgrade the Compute vCenter Server in Region A.




Rename the sfo01w01vc01 virtual machine.

a From Home menu of the vSphere Web Client, select Hosts and Clusters. b Expand the sfo01m01vc01.sfo01.rainpole.local tree, double-click the sfo01-

m01fd-mgmt data center, and expand the sfo01-m01fd-mgmt folder. c Right-click sfo01w01vc01 and select Rename. d Enter sfo01w01vc01_old as the new virtual machine name, and click OK.








Read and accept the EULA, and click Next.



Upgrade Wizard Page Setting Value Connect to source appliance Appliance FQDN or IP address sfo01w01vc01.sfo01.rainpole.local


Configure the settings and click Connect to source. Appliance OS root password sfo01w01vc01_root_password ESXi host or vCenter Server name

sfo01m01vc01.sfo01.rainpole.local

HTTPS port 443 User name [email protected] Password vsphere_admin_password


Appliance deployment target ESXi host or vCenter Server name

sfo01m01vc01.sfo01.rainpole.local

HTTPS port 443 User name [email protected] Password vsphere_admin_password


Select folder Folder sfo01-m01fd-mgmt Select compute resource Compute resource sfo01-m01-mgmt01 Set up target appliance VM VM name sfo01w01vc01

Set root password sfo01w01vc01_root_password Confirm root password sfo01w01vc01_root_password



Configure network settings Network sfo01-m01-vds01-management IP version IPv4 IP assignment Static Temporary IP address 172.16.11.70 Subnet mask or prefix length 24 Default gateway 172.16.11.1 DNS servers 172.16.11.5,172.16.11.4








Upgrade Wizard Page Setting Value Introduction - - Select upgrade data Configuration Selected Configure CEIP Join the VMware Customer Experience Improvement

Program (CEIP) Selected


Selected






to https: / /sfo01m01vc01.sfo01.rainpole. local /vsphere-client / . b Log in with user name [email protected] and password

vsphere_admin_password. c From the Home menu of the vSphere Web Client, select Networking & Security. d In the Navigator pane, Click Firewall Settings, and click the Exclusion List tab. e From the NSX Manager drop-down menu, select 172.16.11.66 | Primary. f Click the Add button. g From the Select VM(s) to include dialog box, select sfo01w01vc01, click the Add

icon, and click Ok.

Upgrade vCenter Server for the Shared Edge and Compute Cluster in Region B

After you update the Compute vCenter Server in Region A, update the Compute vCenter Server in Region B to complete the upgrade of vCenter Server.




Rename the lax01m01vc01 virtual machine.




a From the Home menu of the vSphere Web Client, select Hosts and Clusters. b Expand the lax01m01vc01.lax01.rainpole.local tree, double-click the lax01-

m01dc data center, and expand the lax01-m01fd-mgmt folder. c Right-click lax01w01vc01 and select Rename. d Enter lax01w01vc01_old as the new virtual machine name, and click OK.





Follow the prompts and configure the following settings in each section of the Upgrade - Stage 1: Deploy vCenter Server wizard.



Read and accept the EULA, and click Next. Connect to source appliance Appliance FQDN or IP address lax01w01vc01.lax01.rainpole.local


Configure the settings and click Connect to source. Appliance OS root password lax01m01vc01_root_password ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Appliance deployment target ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local HTTPS port 443 User name [email protected] Password vsphere_admin_password


Select folder Folder lax01-m01fd-mgmt Select compute resource Resource pool lax01-m01fd-mgmt Set up target appliance VM VM name lax01w01vc01

Set root password lax01w01vc01_root_password Confirm root password lax01w01vc01_root_password


Upgrade Wizard Page Setting Value Select Deployment Size Deployment size Small

Storage size Default Select datastore Datastore lax01-m01-vsan01

Enable thin disk mode Selected Configure network settings Network lax01-m01-vds01-management

IP version IPv4 IP assignment Static Temporary IP address 172.17.11.70 Subnet mask or prefix length 24 Default gateway 172.17.11.1 DNS servers 172.17.11.5,172.17.11.4







Upgrade Wizard Page Setting Value Introduction - - Select upgrade data Configuration Selected Configure CEIP Join the VMware Customer Experience Improvement

Program (CEIP) Selected


Selected






to https: / / lax01m01vc01.lax01.rainpole.local /vsphere-client . b Log in with user name [email protected] and password




c From the Home menu of vSphere Web Client, select Networking & Security. d In the Navigator pane, Click Firewall Settings and click the Exclusion List tab. e From the NSX Manager drop-down menu, select 172.17.11.66 | Primary. f Click the Add button. g From the Select VM(s) to include dialog box, select lax01w01vc01, click the

Add icon, and click Ok.

Delete the Obsolete vCenter Server Appliances in Region A and Region B After completing the upgrade of the Shared Edge and Compute cluster components in Region A and Region B, delete the obsolete vCenter Server virtual appliances.


Region Folder Virtual Machine to Delete Region A sfo01-m01fd-mgmt sfo01w01vc01_old Region B lax01-m01fd-mgmt lax01w01vc01_old




From the Home menu of vSphere Web Client, select VMs and Templates.


Right-click the sfo01w01vc01_old virtual machine, select Delete from Disk.

in the Confirmation dialog box, click Yes.

Repeat this procedure for the lax01w01vc01_old virtual machine in Region B.

Perform the VxRail Cluster Upgrade of the Shared Edge and Compute Clusters

After you upgrade the SDDC components that provide infrastructure management, upgrade the VxRail Cluster supporting the Shared Edge and Compute cluster. Begin the process in Region A and repeat the steps in Region B.

Table 64. Shared Edge and Compute ESXi Hosts in the SDDC

Region Fully Qualified Domain Name IP Address Region A sfo01w01vxm01.sfo01.rainpole.local 172.16.31.65 Region B lax01w01esx01.lax01.rainpole.local 172.17.31.65



Procedure Log in to the VxRail Manager instance supporting Management Cluster.

Open a Web browser and go to https: / /sfo01m01vxm01.sfo01.rainpole. local .



Selecting the dashboard icon from the list of management options and confirm the status is healthy with a green checkmark

Select the health tab and confirm there are not outstanding health issues with any of the hardware components.

Remediate any issues before proceeding.


a Log into the Management vCenter Server at https: / /sfo01m01vc01.sfo01.rainpole.local 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.

Open a Web browser and go to https://sfo01w01vxm01.sfo01.rainpole.local


Select the Config Icon




Click Continue to proceed with the upgrade




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.





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.

Repeats steps 1 – 15 in Region B to upgrade the VxRail Workload Domain Cluster supporting the Shared Edge and Compute Cluster in that Region.

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 VMware validated design.

Add vCenter Server and Platform Services Controller instances to Virtual Machine DRS Groups in Region A and Region B

After you upgrade the vCenter Server and Platform Services Controller components, you add the new appliances to virtual machine DRS groups. This enables the previously created anti-affinity rules and specifies that critical virtual machines, such as the vCenter Server instances, run on different hosts.

Table 65. Virtual Machine DRS Groups for Region A and Region B

Region Cluster Role Virtual Machine VM/Host Group Region A sfo01-m01-mgmt01 Platform Services Controller for

the management cluster sfo01m01psc01 Platform Services

Controllers Platform Services Controller for the shared edge and compute cluster

sfo01w01psc01

vCenter Server for the management cluster

sfo01m01vc01 vCenter Servers

vCenter Server for the shared edge and compute cluster

sfo01w01vc01

Region B lax01-m01-mgmt01 Platform Services Controller for the management cluster

lax01m01psc01 Platform Services Controllers


lax01w01psc01

vCenter Server for the management cluster

lax01m01vc01 vCenter Servers

vCenter Server for the shared edge and compute cluster

lax01w01vc01






In the Navigator pane, select Host and Clusters, and expand the sfo01m01vc01.sfo01.rainpole.local tree.

Add the Platform Services Controller instances to the Platform Services Controllers VM/Host Group.

a Select the sfo01-m01-mgmt01 cluster and click the Configure tab. b On the Configure page, click VM/Host Groups. c On the VM/Host Groups page, select the Platform Services Controllers group,

and click Edit. d In the Edit VM/Host Group dialog box, click Add, select sfo01m01psc01 and

sfo01m01psc01, and click OK.

Add the vCenter Server instances to the vCenter Servers VM/Host Group.

a Select the sfo01-m01-mgmt01 cluster and click the Configure tab. b On the Configure page, click VM/Host Groups. c On the VM/Host Groups page, select the vCenter Servers group, and click Edit. d In the Edit VM/Host Group dialog box, click Add, select sfo01m01vc01 and

sfo01w01vc01, and click OK.

Repeat the procedure for the Platform Services Controller and vCenter Server instances in Region B.

Post-upgrade configuration of the virtual infrastructure components in Region A

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 VMware validated design.

Set SDDC Deployment Details on the Management vCenter Server in Region A

Update the identity of your SDDC deployment on vCenter Server. You use this identity as a label in tools for automated SDDC deployment.




From the Menu of the vSphere Client, select Global Inventory Lists.

Click vCenter Servers.

Click the sfo01m01vc01.sfo01.rainpole.local vCenter Server object and click the Configure tab in the central pane.

Under the Settings pane, click Advanced Settings and click the Edit button.



In the Edit Advanced vCenter Server Settings dialog box, configure the following properties and click OK.

a Search for the config.SDDC.Deployed.Version property and change its

value from 4.3.0 to 5.0.0 . b Add the config.SDDC.Deployed.WorkloadDomain and

config.SDDC.Deployed.InstanceId properties.

Name Value 1 config.SDDC.Deployed.Type VVD config.SDDC.Deployed.Flavor Standard config.SDDC.Deployed.Version 5.0 config.SDDC.Deployed.WorkloadDomain Management config.SDDC.Deployed.Method DIY 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 into 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.

Procedure Log in to the Compute vCenter Server by using the vSphere Client.

Open a Web browser and go to https: / /sfo01w01vc01.sfo01.rainpole.local /vsphere-cl ient/ .




Click the sfo01w01vc01.sfo01.rainpole.local vCenter Server object and click the Configure tab in the central pane.




value from 4.3.0 to 5.0 . b Add the config.SDDC.Deployed.WorkloadDomain and


https://www.uuidgenerator.net/



Name Value config.SDDC.Deployed.Type VVD config.SDDC.Deployed.Flavor Standard config.SDDC.Deployed.Version 5.0.1 config.SDDC.Deployed.WorkloadDomain SharedEdgeAndCompute config.SDDC.Deployed.Method DIY config.SDDC.Deployed.InstanceId unique_identifier*

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.

c 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.

Set SDDC deployment details on the Management vCenter Server in Region B Update the identity of your SDDC deployment on the Management vCenter Server in Region B. You use this identity as a label in tools for automated SDDC deployment.






Click the lax01m01vc01.lax01.rainpole.local vCenter Server object and click the Configure tab in the central pane.



Search for the config.SDDC.Deployed.Version property and change its value from 4.3.0 to 5.0 .

Add the config.SDDC.Deployed.WorkloadDomain and config.SDDC.Deployed.InstanceId properties.



Name Value 1 config.SDDC.Deployed.Type VVD config.SDDC.Deployed.Flavor Standard config.SDDC.Deployed.Version 5.0.1 config.SDDC.Deployed.WorkloadDomain Management config.SDDC.Deployed.Method DIY 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 into 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.

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. You use this identity as a label in tools for automated SDDC deployment.

Procedure Log in to the Compute vCenter Server by using the vSphere Client.

Open a Web browser and go to https: / / lax01w01vc01.lax01.rainpole.local /vsphere-client .




Click the lax01w01vc01.lax01.rainpole.local vCenter Server object and click the Configure tab in the central pane.




value from 4.3.0 to 5.0 . b Add the config.SDDC.Deployed.WorkloadDomain and


Name Value config.SDDC.Deployed.Type VVD config.SDDC.Deployed.Flavor Standard config.SDDC.Deployed.Version 5.0.1 config.SDDC.Deployed.WorkloadDomain SharedEdgeAndCompute config.SDDC.Deployed.Method DIY config.SDDC.Deployed.InstanceId unique_identifier*

https://www.uuidgenerator.net/



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.

Click OK to close the window.


7 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 Name in Region A

Virtual Machine Name in Region B

Shutdown Order

vRealize Suite Lifecycle Manage Total Number of VMs (1)

- 1

vrslcm01svr01a - 1

vRealize Log Insight Total Number of VMs (3)


2

sfo01vrli01c lax01vrli01c 1 sfo01vrli01b lax01vrli01b 1 sfo01vrli01a lax01vrli01a 2

vRealize Operations Manager Total Number of VMs (5)


2

sfo01vropsc01b lax01vropsc01b 1 sfo01vropsc01a lax01vropsc01a 1 vrops01svr01c - 2 vrops01svr01b - 3 vrops01svr01a - 4

vRealize Business for Cloud Total Number of VMs (2)

Realize Business for Cloud Total Number of VMs (1)

3

sfo01vrbc01 lax01vrbc01 1 vrb01svr01 - 2

vRealize Automation Total Number of VMs (12)


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 vSphere Replication Total Number of VMs (2)

Site Recovery Manager and vSphere Replication Total Number of VMs (2)

5

sfo01m01vrms01 lax01m01vrms01 1 sfo01m01srm01 lax01m01srm01 2

Update Manager Download Service (UMDS) Total Number of VMs (1)

Update Manager Download Service (UMDS) Total Number of VMs (1)

5

sfo01umds01 lax01umds01 N/A for VVD on VxRail design

Core Stack Total Number of VMs (26)

Core Stack Total Number of VMs (16)

6


Startup 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.

Starting 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.

Starting up the management virtual machines: Start up the virtual machines in the startup order provided in the following table.

Verify that the console of the VM is available and all services of the VM are up, before proceeding with the next virtual machine.

Refer to VMware Knowledge Base article 2142676 for information on verifying the health of the vSAN clusters before starting up tenant workloads.

sfo01m01lb01 (0,1) lax01m01lb01 (0,1) 1 sfo01m01udlr01 (0,1) - 1 sfo01m01esg01 lax01m01esg01 1 sfo01m01esg02 lax01m01esg02 1 sfo01w01udlr01 (0,1) - 1 sfo01w01dlr01 (0,1) lax01w01dlr01 (0,1) 1 sfo01w01esg01 lax01w01esg01 1 sfo01w01esg02 lax01w01esg02 1 sfo01m01nsx01 lax01m01nsx01 2 sfo01w01nsx01 lax01w01nsx01 2 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




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 in Region A Virtual Machine in Region B Startup Order

Core Stack Number of VMs (26)

Core Stack Number of VMs (16)

1

sfo01m01psc01 lax01m01psc01 1 sfo01w01psc01 lax01w01psc01 1 sfo01psc01 (0,1) lax01psc01 (0,1) 2 sfo01m01vc01 lax01m01vc01 3 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 sfo01m01esg01 lax01m01esg01 6 sfo01m01esg02 lax01m01esg02 6 sfo01w01udlr01 (0,1) - 6 sfo01w01dlr01 (0,1) lax01w01dlr01(0,1) 6 sfo01w01esg01 lax01w01esg01 6 sfo01w01esg02 lax01w01esg02 6

Update Manager Download Service Total Number of VMs (1)

Update Manager Download Service Total Number of VMs (1)

2

sfo01umds01 lax01umds01 1

Site Recovery Manager and vSpher Replication Total Number of VMs (2)

Site Recovery Manager and vSpher Replication Total Number of VMs (2)

2

sfo01m01vrms01 lax01m01vrms01 1 sfo01m01srm01 lax01m01srm01 1



3

vra01mssql01 - 1 vra01svr01a - 2 vra01svr01b - 2 vra01svr01c - 2 vra01iws01a - 3 vra01iws01b - 4 vra01ims01a - 5


Virtual Machine in Region A Virtual Machine in Region B Startup Order vra01ims01b - 6 sfo01ias01a lax01ias01a 7 sfo01ias01b lax01ias01b 7 vra01dem01a - 7 vra01dem01b - 7



4

vrb01svr01 - 1 sfo01vrbc01 lax01vrbc01 2



5

vrops01svr01a - 1 vrops01svr01b - 2 vrops01svr01c - 3 sfo01vropsc01a lax01vropsc01a 4 sfo01vropsc01b lax01vropsc01b 4



5

sfo01vrli01a lax01vrli01a 1 sfo01vrli01b lax01vrli01b 2 sfo01vrli01c lax01vrli01c 2

vRealize Suite Lifecycle Manager Total Number of VMs (1)

vRealize Suite Lifecycle Manager Total Number of VMs (0)

6

vrslcm01svr01a - 1

Documents

VMware Validated Design for SDDC v5.01 on Dell EMC VxRail · 2020-03-05 · VVD on VxRail 5.0.1 Upgrade Guide 1 Dell Customer Communication - Confidential VMware Validated Design