VMware NSX | 04 OCT 2022 | Build 20541212

Check for additions and updates to these release notes.

What's New

NSX-T Data Center is an update release that comprises bug fixes only. See "Resolved Issues" below for the list of issues resolved in this release. See the VMware NSX-T Data Center 3.2 Release Notes for the list of new features introduced in NSX-T 3.2. See the VMware NSX-T Data Center 3.2.1 Release Notes for the current known issues.

Introduction of the NSX Upgrade Evaluation Tool - Customers upgrading to NSX-T are strongly encouraged to run the NSX Upgrade Evaluation Tool before starting the upgrade process. The tool is designed to ensure success by checking the health and readiness of your NSX Managers prior to upgrading.

Compatibility and System Requirements

For compatibility and system requirements information, see the VMware Product Interoperability Matrices and the NSX-T Data Center Installation Guide.

Upgrade Notes for This Release

For instructions about upgrading the NSX-T Data Center components, see the NSX-T Data Center Upgrade Guide.

Available Languages

NSX-T Data Center has been localized into multiple languages: English, German, French, Italian, Japanese, Simplified Chinese, Korean, Traditional Chinese, and Spanish. Because NSX-T Data Center localization utilizes the browser language settings, ensure that your settings match the desired language.

Document Revision History

October 4, 2022. First edition.

Resolved Issues

  • Fixed Issue 3032598: N-S traffic outage during NSX edge migration in BYOT.

    Longer outage seen when multiple UDLRs are migrated from NSX for vSphere to NSX-T.

  • Fixed Issue 3033063: In VUM upgrade workflow, creation of nsxuser on the host may fail and lead to NSX host upgrade failure.

    During a VUM upgrade, after ESXi hosts are upgraded to a newer version, NSX manager detects a new ESXi version and starts NSX VIB upgrade automatically. The ESXi host may sometimes disconnect from vCenter for a few seconds after host upgrade and during this time if NSX tries to create nsxuser to help update the VIBs it will fail and mark the host as failed on UI.

  • Fixed Issue 3033060: Fail to apply Transport Node profile on a cluster.

    Cm-inventory (compute manager) service may run out of memory when there are thousands of segments (dvpg) configured on NSX and realized on vCenter either attached to one DVS or multiple DVS. The configuration can lead to TN profile realization failure.

  • Fixed Issue 3024608: SFTP server password and passphrase used in backup/restore stored in clear text in unified appliance logs.

    Unified appliance logs show the SFTP server password and passphrase in clear text whenever backup configuration is created/updated.

  • Fixed Issue 3033587: Receive Side Scaling (RSS) does not work with Mellanox interfaces in Bare Metal Edge.

    Lack of RSS leads to over utilization of single core and causes severe performance issues.

  • Fixed Issue 3025912: Upgrade from NSX-T 3.2.1 to fails for Global Manager.

    A wrong API used during global manager upgrade leads to GM upgrade failure.

  • Fixed Issue 3027797: Bare Metal Edge management bond interfaces may be lost after a reboot, or there may be incorrectly named interfaces.

    Loss of Edge management connectivity, new configuration realization may fail and impact datapath.

  • Fixed Issue 3039749: ESX PSOD when a malformed IPv6 ND/unsolicited NA packet is received on an overlay segment.

    Downtime due to ESX PSOD.

  • Fixed Issue 3027804: Edit Edge Transport Node Dialog does not show uplinks from Named teaming policies or lags defined in uplink profile.

    Functionality loss as you are not able to use uplinks from lags or named teaming policies in a Edge Transport Node from the UI.

  • Fixed Issue 3027814: Nginx crash after LB persistence is disabled.

    New connection cannot be established as dead lock.

  • Fixed Issue 3027792: VMs intermittent connectivity issues after applying a transport node profile to a cluster without detaching a pre-existing TNP first.

    VMs intermittent connectivity issues after applying a transport node profile to a cluster without detaching a pre-existing TNP first.

  • Fixed Issue 3030768: NAT rules are not working without firewall_rule after upgrade from NSX-T 2.3.x to 3.2.x.

    Traffic is affected by N-S or E-W.

  • Fixed Issue 3030772: The NAT Active counter shows a very large, incorrect value (e.g., "NAT Active/Max": "4293970739/4294967295").

    Incorrect counter of active NAT connections.

  • Fixed Issue 3027913: An invalid flow cache entry causes packets of unrelated flows to bypass FW and SNAT processing.

    Random flow failure. Client application reports connection reset.

  • Fixed Issue 3039568: Upgrading to 3.2.1 from 3.1.x or older for envs with segment GPRR entry with realizedObjectId=null would fail with NPE.

    Unable to upgrade to 3.2.1.x.

  • Fixed Issue 3035364: There are VMs connected to DFW enabled DVPortgroup and they do not have correct firewall rules applied to them.

    DFW rules are not applied correctly on the VMs.

check-circle-line exclamation-circle-line close-line
Scroll to top icon