Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to upgrade a NSX-T 2.3.1 based Workload Domain to NSX-T 2.4 in VMware Cloud Foundation 3.x (70518)

Last Updated: 7/16/2020Categories: How toTotal Views: 2196Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

For any Workload Domains deployed with NSX-T 2.3.1, the following guide provides manual guidance on how to upgrade the deployment successfully to NSX-T 2.4.

Impact / Risks

Please make sure that both the vCenter and ESXi versions of the existing workload are compatible with NSX-T 2.4.

The compatibility guide can be checked here. For a detailed guide, you can refer to NSX-T upgrade guide

Resolution

Upgrade NSX-T Components

In the VMware download portal, locate the NSX-T Data Center version available to upgrade and navigate to Product Downloads > NSX Cloud Upgrade Bundle for NSX-T 2.4.

Verify that the primary upgrade bundle (.mub) filename has a format similar to VMware-CC-upgrade-bundle-ReleaseNumberNSXBuildNumber.mub.

Navigate to the NSX-T Manager UI. In Utilities > Upgrade, upload the upgrade bundle.

Click RUN PRE CHECKS and validate the health. Fix all errors/warnings shown, before proceeding further.

Click on Begin Upgrade at the bottom of the page.

Upgrade Hosts through NSXT UI

Upgrade Edge nodes.

Upgrade Controllers Nodes.

Upgrade NSX-T Management Node(s).

Verify the upgrade completed successfully be signing into the NSX-T Manager UI. In the Overview page, NSX version should show 2.4.0.0.<build-number>.

Delete the NSXT 2.3 Controller VMs through the vCenter.

Add Additional NSX-T Managers

Note: Ensure that DNS records have been created for the 3 additional NSX-T manager VMs.

Navigate to the NSX-T Manager UI page and log in.

Navigate to System Fabric > Compute Managers and select Add. Enter the Management vCenter FQDN.

Deploy an additional NSX-T Manager by navigating to System Overview and then selecting Add.

Repeat Step 3 so there will now be 3 NSX-T Manager VMs.

Note: Ensure there is available resources in the cluster to support the additional virtual machines.

Set VIP address by selecting Virtual IP Edit.

Select System Fabric > Compute Managers and the press Delete to delete the Compute Manager which maps to Management vCenter.

Add Anti-affinity rules for the 3 NSXT manager VMs

Login to the Management Workload Domain's vCenter Web Client.

Right click on the Management Workload Domain cluster select Settings.

Under the Configure tab select VM/Host Rules and click Add.

Enter the following information in the wizard:

Name: NSXT Managers Anti Affinity Rule
Type : Separate Virtual Machines

Add the three NSX-T Managers VM created and then click OK.

Issue certificates to NSXT Managers & VIP

Navigate to https://kb.vmware.com/s/article/67030 and download the attached file 67030_cert-gen.zip.

Using WinSCP, or another FTP client, upload the 67030_cert-gen.zip file to the SDDC Manager VM to /tmp/.

Extract the zip and navigate into the extracted folder.

Open an SSH to the SDDC Manager VM and change to root.

su -

Issue the following command to access the Postgres database:

sudo -u postgres psql postgres -h /home/postgresql

Access the platform database:

\c platform

Open a second SSH to the SDDC Manager VM and change to root.

su -

Execute following sql query on 1st SSH session to update 1st NSX-T Manager reference:

update nsxt_manager set version = '2.4.0.0.0.12456646', vm_hostname = '{nsx-t-manager-1.domain.local}', vm_name = 'nsx-t-manager-1-VM-Name', vm_management_ip_address = '{nsx-t-manager-1-IP-Address}';

Using the 2nd SSH session, execute the ec-ec.1-upgrade.py python script to issue certificate.

Execute following SQL query on 1st SSH session to update the 2nd NSX-T Manager reference:

update nsxt_manager set version = '2.4.0.0.0.12456646', vm_hostname = '{nsx-t-manager-2.domain.local}', vm_name = 'nsx-t-manager-2-VM-Name’, vm_management_ip_address = '{nsx-t-manager-2-IP-Address}’;

Using the 2nd SSH session, execute the ec-ec.1-upgrade.py python script to issue certificate.

Execute following sql query on 1st SSH session to update 3rd NSX-T Manager reference:

update nsxt_manager set version = '2.4.0.0.0.12456646', vm_hostname = '{nsx-t-manager-3.domain.local}', vm_name = 'nsx-t-manager-3-VM-Name’, vm_management_ip_address = '{nsx-t-manager-3-IP-Address}’;

Using the 2nd SSH session, execute the ec-ec.1-upgrade.py python script to issue certificate.

Execute following SQL query on 1st SSH session to update NSX-T VIP reference:

update nsxt_manager set version = '2.4.0.0.0.12456646', vm_hostname = '{vip-nsx-t-manager.domain.local}', vm_name = 'vip-nsx-t-manager', vm_management_ip_address = '{nsx-t-VIP-Address}’;

Open the ec-ec.1-upgrade.py file:

vi ec-ec.1-upgrade.py

Replace line number 36 from:

(APPLY_CERT = 'api/v1/node/services/http?action=apply_certificate&certificate_id=%s')

and change it to:

(APPLY_CERT_ON_CLUSTER = 'api/v1/cluster/api-certificate?action=set_cluster_certificate&certificate_id=%s')

Replace line number 198 from:

(uri = APPLY_CERT % cert_id)

and change it to:

(uri = APPLY_CERT_ON_CLUSTER % cert_id)

Save and exit the file by pressing ESC and type :wq.

Execute ec-ec.1-upgrade.py python script to issue certificate at cluster level:

python ec-ec.1-upgrade.py

Register vCenter as Compute Managers

Add the existing Workload Domain’s vCenter Server as Compute Manager, using the vCenter's FQDN.

Verify the ESXi hosts managed by the vCenter are shown under Fabric Nodes.

Replace VMware Cloud Foundation created Logical Switches (LS) with Segments.

Log into the NSX-T Manager UI and navigate to System > Fabric > Profiles > NIOC Profiles.

Click on Add to create a new NIOC Profile.

Note: Ensure that a spare Uplink Profile exists with active uplinks as uplink1 & uplink2.

For each cluster, make note of all three Logical Switches that are attached to hosts in the cluster.

Navigate to System > Fabric > Nodes > Host Transport Nodes. Select the first host in the list and click on Actions > Migrate ESX VMkernel and Physical Adapters to migrate the ESX VMkernels from N-VDS to VDS portgroups through one of the physical adapters.

Note: In case there multiple vmnics, select the one where the name has largest number as suffix. All the vmks should be migrated to a portgroup with Ephemeral binding. If the portgroups for vMotion and/or vSAN are Static binding, these will need to be changed to Ephemeral.

Repeat Step 4 for all hosts in the cluster. Repeat for all clusters.

Verify all VMkernels have migrated and now report the correct VDS in vCenter.

In the NSX Manager UI, navigate to Advanced Networking & Security > Switching > Switches, verify the logical switches report Logical Ports as 0.

Navigate to Networking > Segments and click on Add Segment. Add three segments using the same names, Transport Zone and VLAN as the three logical switches, noted in Step 3, that are used in the cluster for Management, vSAN, and vMotion.

Delete the three logical switches.

Note: Networking to Virtual Machines may be affected, restore the connectivity of the if affected by Step 5.

Click on Add Segment to create another Segment for each overlay Logical Switch. The Segment Name and Transport Zone need to be match the overlay Logical Switch.

Migrate all VMs to the newly created Segment(s).

Delete the overlay Logical Switch.

Create a Transport Node profile

Create a Transport Node profile by navigating to System > Fabric Profiles > Transport Node Profiles.

The name of the Transport Node Profile should be ClusterName-UUID

The description of the Transport Node Profile should be the corresponding Compute Manager’s FQDN.

Move the two transport zones (TZ) to right side box.

Select the NIOC Profile.

Select the Uplink profile.

Select the Physical NICs required for the uplinks.

Click on Mapping to open the Networking Mappings for Install wizard.

Click  the +ADD button and add 3 vmkernels, then bind the vmkernels to Segments created in Step 8 of "Replace VMware Cloud Foundation created Logical Switches (LS) with Segments."

For example:

Map vmk0 to segment for management

Map vmk1 to segment for vmotion

map vmk2 to segment for vsan

Note: In an environment with multiple clusters, there'll be multiple segments/LS, care in identifying the correct Segments is mandatory. Mapping vmks to segment of different clusters may cause connectivity issues with the hosts. Recovery option may be limited.

Evacuate VMs in 1st half of the hosts in the cluster to the 2nd half of hosts of the cluster.

Navigate to Fabric > Nodes and select the cluster which was used for creating the Transport Node Profile.

Select CONFIGURE NSX.

For any hosts with running VMs, the Transport Node Profile may not be applied, therefore, migrate the VMs back to the 1st half of hosts in the cluster and then select CONFIGURE NSX again to apply to the remaining Hosts.

If the transport nodes are displayed as IPs then change them to the FQDNs by selecting the node followed by clicking EDIT.

Revert the bindings of the vSAN and vMotion portgroups to static in vCenter. It may also be required to change the number of ports to the value that it was earlier.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
サービス プロバイダの VMware Cloud Foundation でターゲット データストアにスペースが含まれていると、コンテンツ ライブラリの作成に失敗する (70521)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.7.x

VMware Cloud Foundation 3.5.x

Take Our Survey

Support Assistant