Important KB updates for current NSX for vSphere users

Our NSX team would like all of our customers to know about important KB updates for current NSX for vSphere issues. Here’s what’s new and trending-

Recommended minimum version for VMware NSX for vSphere with Guest Introspection Driver, ESXi and vCenter server (KB 2144295)

  • NSX for vSphere 6.2.2​
  • NEW! See also the minimum recommended version table in the Systems Requirements section of the NSX for vSphere 6.2.2 Release Notes. 

Key issues resolved in NSX for vSphere in release 6.2.2:

  • KB 2144097After deploying a VMware NSX for vSphere 6.2.x Edge, adding a dhcp pool fails with the error: Invalid host name <name.local>
  • KB 2144457Shutting down the VMware NSX for vSphere 6.x controllers while using replication type Hybrid mode flushes out the VTEP tables on the ESXi host
  • KB 2144096VMware vCloud Networking and Security and NSX for vSphere workaround for CVE-2015-7547: glibc getaddrinfo stack-based buffer overflow
  • KB 2144018 / – In VMware NSX for vSphere 6.2.1, ESXi 5.5.x/6.0.x host experiences a purple diagnostic screen mentioning PFFilterPacket and VSIPDVFProcessSlowPathPackets
  • KB 2143397 / – In VMware NSX for vSphere 6.2.1, adding an ESXi host to the vSphere Distributed Switch fails with the error: Host <IP address> is not licensed for the VDS feature. Cannot add this host to dvSwitch
  • KB 2144314 In VMware NSX for vSphere 6.x, ESXi 5.5.x host experiences a purple diagnostic screen mentioning VdrProcessDhcpClientReq and VdrConsumeDhcp

Top troubleshooting issues:

  • KB 2144605Troubleshooting duplicate VXLAN VTEP vmk interfaces or IP addresses in VMware NSX for vSphere 6.x
  • KB 2137025IP address assignments to VXLAN Tunnel End Point (VTEP) and NSX host preparation fails with the error: Insufficient IP addresses in IP pool
  • KB 2144016In VMware NSX for vSphere 6.x, the NSX agencies on an ESXi host are uninstalled after unregistering the NSX Solution Plug-in
  • KB 2144200In VMware NSX for vSphere 6.x, installing or upgrading NSX VIBs fails with the error: ERROR: The pending transaction requires xxx MB free space, however the maximum supported size is xxx MB
  • KB 2126560 – Understanding and troubleshooting High Availability (HA) on the VMware NSX for vSphere 6.x Edge
    • ​Inline with other HA features, such as vSphere HA or MSCS, Edge HA is not designed to deliver zero downtime as the failover between appliances may require some services to be restarted.
    • ​NSX Edge HA is designed to minimize failover downtime. For example, it synchronizes the connection tracker of the statefull firewall, or the statefull information held by the load balancer. However, the time required to bring all services back up is not null. Examples of known service restart impacts include a non-zero downtime with dynamic routing when an Edge is operating as a router.
    • ​See also the 6.2.2 and 6.1.6 release notes – Fixed Issue [1573818]: [Traffic interrupted for 50 seconds after HA failover on ESG]


How to track the top field issues:


Leave a Reply

Your email address will not be published.