| VMware NSX 4.2.0.2 | 17 SEP 2024 | Build 24278654 Check for additions and updates to these release notes. |
What's New
NSX 4.2.0.2 is an update release that comprises bug fixes only. See "Resolved Issues" for the list of issues resolved in this release. See the VMware NSX 4.2.0 Release Notes for the list of new features introduced in NSX 4.2.0 and for the current known issues.
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.
This release is not supported for NSX Cloud customers deployed with AWS/Azure workloads. Do not upgrade your environment in this scenario.
Note: 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 Manager repository prior to upgrading. The tool is already integrated into the Upgrade workflow as part of the upgrade pre-checks; no separate action is needed.
Upgrade Integration Issues Due to Download Site Decommission
The NSX upgrade experience is impacted due to the decommissioning of downloads.vmware.com. See knowledge base article 372634 before upgrading.
Available Languages
Beginning with the next major release, we will be reducing the number of supported localization languages. The three supported languages will be:
-
Japanese
-
Spanish
-
French
The following languages will no longer be supported:
-
Italian, German, Korean, Traditional Chinese, and Simplified Chinese.
Impact:
-
Customers who have been using the deprecated languages will no longer receive updates or support in these languages.
-
All user interfaces, help documentation, and customer support will be available only in English or in the three supported languages mentioned above.
Because NSX localization utilizes the browser language settings, ensure that your settings match the desired language.
Document Revision History
| Revision Date |
Edition |
Changes |
|---|---|---|
| September 16, 2024 |
1 |
Initial edition |
| September 19, 2024 |
2 |
Updated 3431505. |
Resolved Issues
-
Fixed Issue 3432205: Corrupted user role binding entries could be used for subsequent authorization.
Users having group names created with lowercase letters could get higher permission than pre-defined. This will have implications to both LDAP and vIDM.
-
Fixed Issue 3431564: After upgrading NSX to 4.2.0, users who belong to an LDAP group that is a nested member of a group added to NSX get an "Access Denied" error when they log into NSX.
Users who previously were able to log in to NSX can no longer log in after upgrade to 4.2.0.
-
Fixed Issue 3431563: There can be a delay of one hour between the time a new nested group is added to LDAP before a user in that group can log into NSX. Instead, they see an "Access Denied" error.
Users may not be able to log in immediately.
-
Fixed Issue 3430006: After upgrading to NSX 4.2, if an LDAP identity source was configured prior to the upgrade, resolution of nested LDAP groups is incorrectly turned off.
Users cannot log in to NSX Manager using LDAP.
-
Fixed Issue 3431505: PSOD can occur during vMotion import.
PSOD can occur if the vMotion import connection state information contains an extreme number (millions) of L7 attributes.
-
Fixed Issue 3429995: Users who are added to NSX via LDAP groups may acquire elevated permissions that they should not have.
LDAP users may be able to perform operations when they should not be allowed.
