In this communication, we detail the top trending issues with VMware NSX for vSphere and provide you with helpful information on how to address the issues while we build a permanent fix. Please review the left column of the chart below to search for issues specific to your environment, and click on the hyperlinks to access more detailed information on each.
For up-to-date Top Trending NSX issues, previous and current, please see KB Article Trending support issues in VMware NSX for vSphere 6.x (2131154).
Spotlight Issues
Affected version | Component | Issue Summary | Resolution/Work-Around | KB Number | |
1 | 6.2.x, 6.3.x | Guest Introspection | Guest Introspection Status is Warning: Service is not ready.
Rebooting Guest Introspection does not resolve the issue. Removing the VM from the inventory and clicking on the Resolve button to recreate does not resolve the issue. |
This issue occurs when there are orphaned virtual machines on the ESXi hosts. You can see the orphaned virtual machines in the vSphere Web Client and they appear as Powered Off with Status of Unknown.
To resolve this issue, remove the orphaned virtual machines from the vCenter Server inventory. For more information, please refer to the KB. |
KB: 2151671 |
2 | 6.3.2 | ESG/ DLR | Adding or modifying interfaces to edge fails with a blank error message.
Adding a new interface to existing ESG or DLR in NSX for vSphere 6.3.2, clicking on submit throws NULL pointer exception in UI. |
This is a known issue in NSX for vSphere 6.3.2 and vSphere VCSA 6.5 U1.
This issue is resolved in NSX for vSphere 6.3.3, available at VMware Downloads. To avoid this issue, create all interfaces when DLR or ESG is being created using UI. To work around this issue, if you do not want to upgrade, use API call to change the interface settings. For more details, please refer to the KB. |
KB: 2151309
|
3 | 6.2.x, 6.3.x | DSVA | Trend Deep Security Service Deployment “Missing Dependencies” for VMware Network Fabric.
When deploying DSVA from NSX Manager, the “VMware Network Fabric” missing dependency alert may pop up. |
You can safely ignore the alert and force the DSVA deployment by clicking the ok.
1. If the deployment status shows as Failed deployment. 2. Click Resolve. 3. The DSVA deployment will be successful, but the status of Trend Micro Deep Security still shows “Failed”. |
|
4 | 6.2.4, 6.2.5 | DFW | DFW fails to publish updated FW rules to ESXi hosts with error: “Failed to publish message with topic ‘null’.
During publishing process, you may notice high CPU utilization. DFW fails to publish updated FW rules to ESXi hosts. |
This is a known issue affecting NSX Manager 6.2.4 and NSX Manager 6.2.5.
This issue is resolved in NSX for vSphere 6.2.8, available at VMware Downloads. |
KB: 2151137 |
5 | 6.2.x, 6.3.x | L2-VPN | L2VPN communication between sites fails.
The MAC address of VMs at each site are seen on both edges when running show service I2vpn. VMs at different sites cannot reach each other. |
When creating the sub-interfaces on the trunk interface of the Edge to stretch networks across sites, the tunnel ID must match on both sides for the traffic to be bridged correctly. If there is a mismatch in the tunnel ID, the communication between sites may fail.
To Resolve the issue, check the sub interface details on the server (managed) edge. For more details, please refer to the Solution. |
|
6 | 6.3.3 | NSX Controller | At times certain controller APIs could fail due to cleanup of API server reference files. | This issue is resolved in VMware NSX for vSphere 6.3.4.
To work around this issue on NSX for vSphere 6.3.3, and to avoid encountering this issue while upgrading from NSX for vSphere 6.3.3 to a later version, VMware developed a signed script that recreates the status file required by the API server. For more details, please refer to the KB. |
KB: 2151719 |
GA Announcement
VMware vSphere 6.3.4 was released on October 12, 2017 and is now available for download. It addresses a number of specific customer bugs from 6.3.3.
For more information, see the VMware NSX for vSphere 6.3.4 Release Notes and NSX Documentation page.
Below is the list of top issues resolved in 6.3.4:
KB Articles | Details |
2151719 | At times certain controller APIs could fail due to cleanup of API server reference files |
2151845 | TOR VTEPs marked down due to buffer overflow under certain scale configuration |
2151846 | One or more NSX Controllers may use only one CPU after a reboot |
Don’t Forget