| VMware NSX 3.2.2.1 | 30 MAR 2023 | Build 21487560 Check for additions and updates to these release notes. |
What's New
NSX-T Data Center 3.2.2.1 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.2 Release Notes for the current known issues.
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, Italian, and Spanish. Because NSX-T Data Center localization utilizes the browser language settings, ensure that your settings match the desired language.
Document Revision History
March 30, 2023. First edition.
Resolved Issues
-
Fixed Issue 3152195: DFW rules with Context Profiles with FQDN of type .*XYZ.com fail to be enforced.
DFW rule enforcement does not work as expected in this specific scenario.
-
Fixed Issue 3106569: Performance not reaching expected levels with EVPN route server mode.
vNIC filters programmed on pNIC may be stale, incorrect, or missing when overlay filters are programmed to the pNIC in a teaming situation, resulting in a possible performance regression.
-
Fixed Issue 3118868: Incorrect or stale vNIC filters programmed on pNIC when overlay filters are programmed around the same time as a pNIC is enabled.
vNIC filters programmed on pNIC may be stale, incorrect, or missing when overlay filters are programmed around the same time as a pNIC is enabled, resulting in a possible performance regression.
-
Fixed Issue 3094405: Incorrect or stale vNIC filters programmed to pNIC when overlay networks are configured.
vNIC overlay filters are updated in a specific order. When updates occur in quick succession, only the first update is retained, and subsequent updates are discarded, resulting in incorrect filter programming and a possible performance regression.
-
Fixed Issue 3152174: Host preparation with VDS fails with error: Host {UUID} is not added to VDS value.
On vCenter, if networks are nested within folders, migrations from NVDS to CVDS or NSX-V to NSX-T may fail if migration is to CVDS in NSX-T.
-
Fixed Issue 3113100: IP address is not realized for some VMs in the Dynamic security groups due to stale VIF entry.
If a cluster has been initially set up for Networking and Security using Quick Start, uninstalled, and then reinstalled solely for Security purposes, DFW rules may not function as intended. This is because the auto-TZ that was generated for Networking and Security is still present and needs to be removed in order for the DFW rules to work properly.
-
Fixed Issue 3113093: Newly added hosts are not configured for security.
After the installation of security, when a new host is added to a cluster and connected to the Distributed Virtual Switch, it does not automatically trigger the installation of NSX on that host.
-
Fixed Issue 3113085: DFW rules are not applied to VM upon vMotion.
When a VM protected by DFW is vMotioned from one host to another in a Security-Only Install deployment, the DFW rules may not be enforced on the ESX host, resulting in incorrect rule classification.
-
Fixed Issue 3113073: DFW rules are not getting enforced for some time after enabling lockdown mode.
Enabling lockdown mode on a transport node can cause a delay in the enforcement of DFW rules. This is because when lockdown mode is enabled on a transport node, the associated VM may be removed from the NSX inventory and then recreated. During this time gap, DFW rules may not be enforced on the VMs associated with that ESXi host.
-
Fixed Issue 3113076: Core dumps not generated for FRR daemon crashes.
In the event of FRR daemon crashes, core dumps are not generated by the system in the /var/dump directory. This can cause BGP to flap.
-
Fixed Issue 3113067: Unable to connect to NSX-T Manager after vMotion.
When upgrading NSX from a version lower than NSX 3.2.1, NSX manager VMs are not automatically added to the firewall exclusion list. As a result, all DFW rules are applied to manager VMs, which can cause network connectivity problems.
This issue does not occur in fresh deployments from NSX 3.2.2 or later versions. However, if you are upgrading from NSX 3.2.1 or earlier versions to any target version up to and including NSX 4.1.0 this issue may be encountered.
