VMware NSX-T Data Center 3.2.1.1 Release Notes

VMware NSX 3.2.1.1 | 26 JUL 2022 | Build 20115686 Check for additions and updates to these release notes.

What's New

NSX-T Data Center 3.2.1.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.1 Release Notes for the current known issues.

Introduction of the NSX Upgrade Evaluation Tool - Customers upgrading to NSX-T 3.2.1.1 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

July 26, 2022. First edition.
July 29, 2022. Second edition.	Added resolved issues 2994424 and 3003239.
September 26, 2022. Third edition.	Added Italian to Available Languages.

Resolved Issues

• Fixed Issue 2981757: Page leak in shared memory setup by dvfilter library for vDPI.

  Traffic loss observed when VDPI is enabled.

• Fixed Issue 2982402: Upgrade from 3.2.0.1 to 3.2.1 failed with, "Management service is not available" error.

  Cannot upgrade NSX environment.

• Fixed Issue 2985196: Rule tag length of 31 characters too short for some customers' use.

  The rule tag is not limited in the NSX Manager, but the config plane and dataplane would truncate the string to 31 characters.

• Fixed Issue 2986484: Global address sets within the firewall can be implicitly deleted, and then the kernel becomes inconsistent with LCP's belief of the running config.

  If a global address set is required by a rule, but the address set has been deleted, the ruleset programming will fail. When ruleset programming fails, the admin needs to modify a rule and republish.

• Fixed Issue 2959934: L7 Load Balancer Nginx processes crash if the server keepalive is enabled.

  The L7 LB service is unavailable.

• Fixed Issue 2990020: TransportNodeProfile gets stuck at 92% while configuring the Transport Node.

  You can't create any workloads with proper connectivity due to the failure in the configuring TransportNode. Traffic is also impacted for existing workloads.

• Fixed Issue 2992341: A port with a wrong name is created in an NVDS scenario with a host attached to a segment during TN preparation.

  No functionality impact.

• Fixed Issue 2992587: URT generated VDS names in VCF cases might be longer than 80 characters, which leads to creating VDS failure.

  No impact, as VDS names in generated topology can be customized by the user.

• Fixed Issue 2985258: Auto-deployed Edge VM created by PI cannot register.

  PI workflow to register edge VM is broken.

• Fixed Issue 2993849: Performance impact seen on the host containing Edge VM / HCX VM / workload VM with MAC learning enabled.

  Users having high traffic scale can see their throughput drop / CPU utilization for Networlds increase.

• Fixed Issue 2990145: SSH service is restarting due to "PUT: /api/v1/transport-nodes/<node-uuid>/node/services/ssh" API call, where request is to update ssh services properties i.e., start_on_boot/root_login.

  SSH service will be in running state even though user requested for the ssh service stop.

• Fixed Issue 2994087: Feature enforcement missing for newly introduced DFW/GFW add-on SKUs, preventing NAPP installation.

  User applied DFW ATP on top of NSX Advanced license and found they are not entitled to install NAPP.

• Fixed Issue 2995902: NvdsUpgradeHostState DB update happens in parallel during task and activity, which leads to losing saved TN config.

  NVDS to CVDS migration fails at TN_UPDATE stage.

• Fixed Issue 2997330: Cross-site route sync for stretched Tier0 gateway didn't resume when interfaces were recreated after deleting all the interfaces on the edge nodes of one site.

  Cross-site connectivity between connected Tier1 and site local networks may break.

• Fixed Issue 3000867: The edge dp coredump is seen when both control prior and service core are enabled.

  The edge dp will not be up and running.

• Fixed Issue 3003753: CCP memory leak because of caching default IP Discovery profile for all logical switch ports.

  Central Control Plane restarts due to out of memory. Control plane operations will resume after restart.

• Fixed Issue 2989885: Edge VM to be deleted is not reachable from NSX manager, and deletion is stuck.

  Unable to delete the edge VM.

• Fixed Issue 3005052: There are VMs that have mismatched logical port IDs.

  DFW rules are not applied on the VMs that have mismatched logical port IDs.

• Fixed Issue 2998097: Central CLI stops working if 7.0.2+ ESXi host reboots.

  Central CLI stops working on the rebooted host.

• Fixed Issue 2938327: Traffic drops with L7 rules.

  Traffic drops for flows with IDS and L7 context rules.

• Fixed Issue 2999867: FTP data connection may fail depending on what other FW rules are configured.

  FTP service behind edge FW may fail to transfer files.

• Fixed Issue 2994424: URT generated multiple VDS for one cluster if named teaming of transport nodes in the cluster are different.

  Transport nodes with different named teaming were migrated to different VDSes, even if they are in the same clusters.

• Fixed Issue 3003239: Firewall rules may not be applied successfully to VMs due to Group handling issue.

  Firewall rules may not be applied successfully to VMs due to an issue with Group processing. Rule does not reach the impacted VMs.