VMware NSX 4.1.2.4 Release Notes

VMware NSX 4.1.2.4| 14 MAY 2024 | Build 23786733 Check for additions and updates to these release notes.

What's New

NSX 4.1.2.4 is an update release that comprises bug fixes only. See "Resolved Issues" below for the list of issues resolved in this release.

Compatibility and System Requirements

For compatibility and system requirements information, see the VMware Product Interoperability Matrices and the NSX Installation Guide.

Upgrade Notes for This Release

For instructions about upgrading NSX components, see the NSX Upgrade Guide.

Customers upgrading to this release are recommended 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. The tool is integrated into the Upgrade workflow, before you begin upgrading the NSX Managers.

Available Languages

NSX has been localized into multiple languages: English, German, French, Japanese, Simplified Chinese, Korean, Traditional Chinese, Italian, and Spanish. Because NSX localization utilizes the browser language settings, ensure that your settings match the desired language.

Document Revision History

Revision Date	Edition	Changes
May 14, 2024	1	Initial edition
May 21, 2024	2	Added Resolved Issue 3373060

Resolved Issues

• Fixed Issue 3373060: ESXi hosts lose connectivity on vmk0 during NSX upgrade from 4.1.0.2 to 4.1.2.3

  ESXi host loses management connectivity during maintenance mode VMware NSX upgrade.

• Fixed Issue 3365679: Segment Port deletion issue on Security install.

  Segment Ports are deleted or DFW rules are not applied correctly.

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

  False packet drops are reported, and customers could see false alarms.

• Fixed Issue 3373622: The following Group query API calls fail through vRNI when page size is used: /policy/api/v1/infra/domains/default/groups and /policy/api/v1/infra/domains/default/groups/SG-Linux/members/logical-ports.

  NSX Group query API calls with page size may fail through vRNI with error code 500.

• Fixed Issue 3373710: Host can crash to a purple screen of death (PSOD) when memory allocation for fastpath stats fails in fastpath creation with EDP standard.

  Host can crash to a PSOD.

• Fixed Issue 3374060: When a multicast ENS flow is enabled, the reference count of multicast packets could be calculated incorrectly and lead to packet double free or use-after-free issue, which might cause the host to crash.

  ESXi host crashes.

• Fixed Issue 3373693: The system might crash to a purple screen of death (PSOD) in certain situations where programming MAC addresses to a pNIC might fail.

  ESXi crashes.

• Fixed Issue 3373692: The system might crash to a purple screen of death (PSOD) in certain situations involving shared or dedicated rss where network threads are added or removed.

  Network threads are added or removed automatically in interrupt mode. ESX crashes.

• Fixed Issue 3373691: The system might crash to purple screen of death (PSOD) in certain situations where network threads are added or removed.

  Network threads are added or removed automatically in interrupt mode. ESX crashes.

• Fixed Issue 3373690: The system might crash to purple screen of death (PSOD) in certain situations where network threads are added or removed.

  Network threads are added or removed automatically in interrupt mode, ESX crashes.

• Fixed Issue 3374013: High upgrade time is observed in ENS enabled DVS.

  The upgrade time becomes longer.

• Fixed Issue 3373682: When EDP interrupt is used, pNIC interrupt processing can be delayed.

  Packets can be dropped and throughput can fluctuate severely.

• Fixed Issue 3373818: When ENS is enabled, run net-stats with "-t h" option to enable collecting histogram.

  When net-stats exits, ENS cleans up memory used for net-stats and triggers a purple screen of death (PSOD) on ESX. ESX crashes.

• Fixed Issue 3373997: If there are too many concurrent queries and indexing requests at the same time, search APIs fail intermittently if the OpenSearch/ElasticSearch query cache occupies a large portion of allocated heap.

  UI does not work intermittently.

• Fixed Issue 3373994: NSX inventory VMs/VIFs are not in sync with VC inventory.

  Discovery agent will not be able to send VM/VIFs details to MP due to out-of-order ACKs from MP. ACK out-of-order is observed due to messaging channel stuck between Discovery Agent and MP. MP-Inventory might not be able to learn about VM/VIF events like creation, deletion, and vMotion.

• Fixed Issue 3373990: VMs falling out of NSX inventory when new VMs are deployed or vMotion.

  Inventory will not learn about VM events like creation, deletion, and vMotion. This will have impact on features like DFW (for example, DFW rules getting dropped).

• Fixed Issue 3373988: After vMotion, VMs in the new host are not discovered in MP inventory.

  Host side inventory agent DA gets stuck in WAITING_FOR_DATA state and msg_type as DMT_INIT. Security policies configured for the VM before migrating to host will not be applicable post vMotion as the VM is not discovered.

• Fixed Issue 3373985: Edge bare metal upgrade rollback fails with the error "Unexpected error, rollback not possible" if the OS is installed on any disk other than 'sda'.

  Unable to rollback edge bare metal after upgrade in case of any issue.

• Fixed Issue 3354160: Queue transaction size is above the allowed maximum size.

  You are blocked from on-boarding a new site.

• Fixed Issue 3373982: dp-fp core is generated.

  Traffic gets impacted during the core dump creation.

• Fixed Issue 3373976: EVPN Type-5 routes are missing in the Tier-0 VRF.

  Traffic outage occurs in affected Tier-0 VRF.

• Fixed Issue 3373974: If the VM is rebooted after the NSX manager multi hop upgrade from 3.0.x to 3.2.2 or 3.2.3 to 4.1.x, the NSX UI shows the Edge status as down.

  Once the Edge node restarts during upgrade or post upgrade, then data plane service crashes while generating core files /var/log/core/core.statsXX.XXXXXXXXXX.XXXX.X.XX.gz. Traffic passing through NSX Edge VM or a non edge VM gets impacted.

• Fixed Issue 3373962: The VLAN based logical switch ports use a wrong teaming policy.

  The wrong teaming policy might cause connectivity issue.

• Fixed Issue 3373620: At the time of saving a group in NSX, a check is performed to ensure that the group actually exists.

  Instead of performing an "exact match" search, the code performs a "starts with" search. In this case, the search finds multiple entries and the group existence test fails. Adding a group pg-nsx-r, which is a substring of pg-nsx-rw, fails when pg-nsx-rw group already exists and a group with a shorter name, such as pg-nsx-r, is being added.

• Fixed Issue 3373801: Physical NIC in bare metal edge resets under heavy traffic.

  The reset of the device results in the interface being inoperable for a short time. Traffic might be lost and BFD sessions will flap.

• Fixed Issue 3373798: Heap allocation fails when required for ENS fastpath creation.

  ENS fastpath is created to cater for the customer network load. ENS fastpath creation failure leads to insufficient CPU resources for handling the traffic and might cause performance issues.

• Fixed Issue 3379516: NSX-T DFW DNS rule for FQDN filtering is causing a 20ms latency issue.

  Customer have implemented FQDN Filtering using distributed firewall, but are experiencing delays when the DNS Context Profile is applied. When you remove the firewall rule with the DNS context profile, there is no delay.

• Fixed Issue 3378098: nsx-syslog.log from ESXI is flooded with the same error.

  The same log is seen multiple times: DfwConnector: No filters found for VM 50 1c 3e 23 5d df df 89-93 e8 c3 ca d4 e2 73 07, cannot add 5-tuple information. Other logs might get lost because of the one log that is flooding the file.

• Fixed Issue 3375870: Edge HA failover due to DP-FW crash and core.dp-fw-dispatch coredumps are observed on Edges.

  In the NSX-T manager UI, the below alarm is generated with the following details: Application on NSX node <NSX-Edge node> has crashed. The number of core files found is 1. Collect the Support Bundle including core dump files and contact VMware Support team.

• Fixed Issue 3375771: Tier-0 interface level realization shows as uninitialized.

  Customers might see the status of some entities as UNINITIALIZED after the restart of the proton service.

• Fixed Issue 3375085: Service Insertion can drop traffic in some vMotion scenarios when both redirection and copy mode are used.

  During vMotion of a GVM, packet drops are seen.

• Fixed Issue 3374903: core.dp-fw-dispatch coredump are observed on Edge during/after Upgrade.

  In the NSX-T manager UI, the below alarm is generated with the following details: Application on NSX node <NSX-Edge node> has crashed. The number of core files found is 1. Collect the Support Bundle including core dump files and contact VMware Support team.

• Fixed Issue 3373528: Notification watcher may fail to be created in NSX Manager.

  The notification watcher may fail with a 404 error. This impacts VRNI and Service insertion because they utilize the notification watcher.