VMware NSX-T Data Center 3.2.3.2 Release Notes

VMware NSX 3.2.3.2 | 15 FEBRUARY 2024 | Build 23214453 Check for additions and updates to these release notes.

What's New

NSX-T Data Center 3.2.3.2 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.3 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

• February 15, 2024. First edition.

• February 29, 2024. Second edition. Added resolved issue 3308656.

• March 5, 2024. Third edition. Added resolved issues 3230394, 3273134, 3308657, 3307947, 3311565, 3295602, 3292642, 3259109.

Resolved Issues

• Fixed Issue 3259109: Dataplane memory configuration is insufficient to support 4K ring size on large configurations with many cores and NICs.

  In large servers, the ring size is limited. This may increase the risk of dropped packets on high throughput interfaces.

• Fixed Issue 3292642: In NSX-T environments configured with Service Insertion, false reports of packet drops reported on all versions of ESXi.

  False packet drops are reported so no application impact will be seen.

• Fixed Issue 3295602: Intermittent traffic loss between Guest VMs in a service insertion environment after vMotion.

  Traffic loss between GVMs in a service insertion environment.

• Fixed Issue 3311565: REST API to NSX Manager fails while using it with vIDM authentication.

  vRA does not work as expected due to 403 error codes returned from the NSX Manager.

• Fixed Issue 3307947: Unable to delete subnet in IP pool even if the subnet is not used in allocation.

  Subnet deletion does not work.

• Fixed Issue 3308657: When creating firewall sections with very large number of rules, the create/delete rule API response is taking more than 30 minutes.

  This slowness causes 409/500 errors or slowness in API executions for PODS to come up.

• Fixed Issue 3273134: FQDN rule enforcement fails during an upgrade (once hosts are upgraded but not the management plane) from 3.X to 4.0.1 release.

  FQDN rule matching fails. Traffic drop.

• Fixed Issue 3230394: Latency observed during DFW config updates.

  During a DFW configuration change, network packets can be delayed and latency observed at VM endpoints. This can be seen even on seemingly unrelated VMs or ESX interfaces. Latency increases with the size of the overall DFW configuration.

• Fixed Issue 3308656: DFW intermittently drops TCP packets for long lived connections.

  Occasional communication failure between VMs.

• Fixed Issue 3333008: Firewall Section lock/unlock does not work.

  Existing locked sections cannot be unlocked by neither the user that created them nor the default enterprise admin account.

• Fixed Issue 3333006: New rules were not created due to ruleID generation failure.

  Cannot create new rules.

• Fixed Issue 3333005: Distributed firewall search filter tool not working properly and reporting a general error.

  Firewall search filter tool not working. Users may not retrieve the expected group member(s) or related group(s).

• Fixed Issue 3332986: PSOD in hosts with ESX 7.0U3 when using ENS.

  ESX will crash.

• Fixed Issue 3308881: Firewall rules were not being applied as expected due to an empty InternalDfwFirewallConfiguration table, or Firewall Exclude List functionalities are not usable due to an incorrect InternalFirewallExcludeList table.

  Rules are not applied. Firewall exclude list functionalities could also be unusable.

• Fixed Issue 3332977: Container to Container connection timeout after NSX-T upgrade.

  Dynamic group membership is wrong. DFW/Gateway Firewall that leverages the group may be impacted. Traffic may not be correctly allowed or dropped.

• Fixed Issue 3336161: IPv6 ANY/ALL address ("::/0") group is not working.

  IPv6 ANY/ALL address ("::/0") group associated to DFW rule will not work.