NSX-T Data Center 3.1.3.8 is an update release that comprises critical bug fixes for issues from prior releases. See "Resolved Issues" below for the list of issues resolved in this release. See the VMware NSX-T Data Center 3.1.3 Release Notes for the current known issues.
|
VMware NSX 3.1.3.8 | 06 OCT 2022 | Build 20532384 Check for additions and updates to these release notes. |
What's New
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 06, 2022. First edition.
Resolved Issues
-
Fixed Issue 3024018: Hyper-threading on Edge nodes cannot be disabled automatically on CPUs released after 2020.
Hyper-threading enabled on Baremetal Edge may reduce packet forwarding performance since datapath fastpath threads mistakenly share physical cores with another process/thread.
-
Fixed Issue 3018926: API calls to retrieve Logical Router statistics times out.
The API call may not be successful in environments with more than 1000 Logical Router Ports.
-
Fixed Issue 3023503: NSX for vSphere to NSX-T migration may fail if the size of associated VIFs exceed 500.
A Policy group is not created on the NSX side when the associated VIFs for IPFIX/Netflow at each DVS exceeds 500.
-
Fixed Issue 3025226: End users impacted by intermittent app resets.
An invalid flow cache entry causes packets of unrelated flows to bypass FW and SNAT processing and lead to app resets.
-
Fixed Issue 3025236: NSX user creation API fails due to host disconnection.
During the VUM upgrade workflow, after the ESXi host upgrade, NSX Manager detects the upgraded host version and automatically tries to update NSX VIBs on the host. Sometimes the host is disconnected from vCenter for 5 -10 seconds after upgrade. If during this time, MP tries to create nsxuser on the host by invoking the vCenter api to copy the LCP bundles, it fails.
-
Fixed Issue 3023499: PSOD during HOST upgrade.
If ENS is enabled during the NSX upgrade, the host may PSOD because of a race condition.
-
Fixed Issue 3024025: Applying Transport Node profile on a cluster fails.
When a transport node profile (TNP) is applied to a cluster, an API call is made from proton to cm-inventory JVM to get the network details of each host. Every time a call to fetch network information was made, the cm-inventory JVM loaded all the DvPortGroup details. Cm-inventory runs out of memory when there are more than 10 calls for each host at the same time during TNP apply or update. As a result, TNP apply fails on the clustered hosts.
-
Fixed Issue 3035576: Multiple IDPS events concatenated in 1 alert.
Multiple IDPS events are concatenated into one alert, which results in an incorrect log split at times.
-
Fixed Issue 3039747: PSOD of ESX.
ESX PSOD when a malformed IPv6 ND/unsolicited NA packet is received on an overlay segment.
