|
VMware NSX-T Data Center 3.0.3.1 | 23 December 2021 | Build 19067109 Check regularly for additions and updates to these release notes. |
What's in the Release Notes
The release notes cover the following topics:
What's New
The VMware NSX-T 3.0.3.1 patch is a Mandatory Security Update for all deployments running NSX-T 3.0.x versions to address the security vulnerability documented in VMSA-2021-0028. The version of Log4j is updated to 2.16.
See the VMware NSX-T Data Center 3.0.3 Release Notes for the current known issues.
Document Revision History
December 23, 2021. First edition.
Resolved Issues
- Fixed Issue: Updated Apache Log4j to version 2.16 to resolve CVE-2021-44228 and CVE-2021-45046.
The VMware NSX-T 3.0.3.1 patch is a Mandatory Security Update for all deployments running NSX-T 3.0.x versions to address the security vulnerability documented in VMSA-2021-0028. The version of Log4j is updated to 2.16.
- Fixed Issue 2823502: DHCP relay feature cannot broadcast DHCP packet.
Some DHCP clients that depend on broadcast may fail to get IP address.
- Fixed Issue 2838860: [NSXCloud] The AMI and other options are disabled when redeploying secondary PCG.
[NSXCloud] The AMI and other options are disabled when redeploying secondary PCG.
- Fixed Issue 2814681: Baremetal Edge datapath performance is lower than expected due to KNI thread competing for CPU with datapath.
Significantly reduced Edge datapath forwarding performance for some flows.
- Fixed Issue 2809875: EVPN tunnel port MTU does not reflect the uplink frame size.
EVPN tunnel port MTU does not reflect the uplink frame size.
- Fixed Issue 2799728: Packets to DC-GW are dropped by Edge when DC-GW use different R-MAC in different VRF.
Packets to DC-GW will be blackholes at Edge for some VRFs.
- Fixed Issue 2814472: Excessive files /config/vmware/edge/frr/reload*.txt are being generated.
This can impact connectivity if the edge is overloaded or VTEP goes down.
- Fixed Issue 2750654: Database compactor went Out of Memory causing management cluster failure.
Production functionality of PKS is impacted due to failed cluster. NSX-T Manager UI is down.
- Fixed Issue 2811545: During full sync between MP and CCP, statesync may provide data from stale cache.
MP and CCP data going out of sync.
- Fixed Issue 2773857: T0 external Interface not available in the routing table of active edge node.
T0 external interface not available in the routing table of active edge node.
- Fixed Issue 2715612: Network latencies are observed during a vMotion import.
Network traffic to seemingly unrelated VMs can be impacted during a VM import.
- Fixed Issue 2775494: The transport-nodes/{uuid}/status API for an Edge node returns incorrect values for the mem_used property.
If tracking the memory usage of Edge VMs using the transport-nodes/{edge-uuid}/status API, the mem_used value may lead you to believe the Edge is almost out of memory when this is not really the case.
- Fixed Issue 2777547: The transport-nodes/{uuid}/status API for an Edge node returns incorrect values for the mem_used property.
The transport-nodes/{uuid}/status API for an Edge node returns incorrect values for the mem_used property.
- Fixed Issue 2777548: The transport-nodes/{uuid}/status API for an Edge node returns incorrect values for the mem_used property.
The transport-nodes/{uuid}/status API for an Edge node returns incorrect values for the mem_used property.
- Fixed Issue 2679720: Vmotion import of firewall config with poorly constructed group memberships can cause host NMI.
The destination ESX can experience an NMI PSOD during the import of vMotion data.
- Fixed Issue 2715469: Upgrade of an edge deployed on a bare metal server with more than one disk might fail.
The edge upgrade will fail.
