Released December 19th 2022 | Build 20959512 | NSX-T 3.2.2.0.1 HP release notes
This patch is built on top of NSX-T 3.2.2. For more information on 3.2.2 please refer to 3.2.2 Release Notes
To obtain the hot patch, open a Service Request under the NSX product line for review and approval to download. This hot patch is not available through the Customer Connect download pages.
For VCF environments, review the VCF async patch information in KB 88287.
The next upgrade path from NSX 3.2.2.0.1 is NSX 4.1.0.
This hot patch contains the fixes mentioned below:
Note: VMware does NOT recommend 3.2.2.0.1 release for Bare metal windows or NSX cloud. The release was built with an insufficient signature and integrity checks turned on, therefore installation on Windows and Azure will fail.
Fixed Issues
Issue
|
Description
|
3064131
|
VRA BYOT - check realization failure
|
3064141
|
Ping from a VM in NSX-V to a VM being migrated from NSX-V to NSX-T by V2T migrator dropped packets
|
3064144
|
Post edge cutover NSX-V workloads still resolving ARP to NSX-V ESG's MAC
|
3064683
|
Outage caused by VDS out-of-sync error
|
3075231
|
[NSX-T / Federation] Added second NSX Tag2 not copied over to ESXi (net-dvs -l | grep extraConfig)
|
3069030
|
Config translation failed [Reason: [topology_plugin] Can not proceed with migration: Invalid NSX-V Manager IP address
|
3058728
|
High latency on network after upgrading VCF to 4.4.1
|
3072167
|
3.2.2 installation fails on hosts when they are configured with cert chain
|
3073628
|
Security Only upgrade from 3.2.1.1 to 3.2.2 host fails with "NSX enabled switches already exist on host"
|
3076582
|
After upgrading NSX-T to 3.2.1.2 there is a problem with PUT based API calls
|
3080210
|
TCP ACK is getting dropped between source and destination VM when destination is using old Operation system
|
3061761
|
Edge goes unresponsive due to high kswapd0 cpu usage
|
Please refer to NSX 3.2.x Upgrade Guide for upgrade instructions.