End of General Support for VMware NSX for vSphere 6.1.x has been extended by 3 months to January 15th, 2017. This is to allow customers to have time to upgrade from NSX for vSphere 6.1.7, which contains an important security patch improving input validation of the system, to the latest 6.2.x release. For recommended upgrade paths, refer to the latest NSX for vSphere 6.2 Release Notes and the VMware Interoperability Matrix.
Migration of Service VM (SVM) may cause ESXi host issues in VMware NSX for vSphere 6.x (2141410). See also the CAUTION statement in the 6.2.3 Administration Guide.
Do not migrate the Service VM (SVM) manually (vMotion/SvMotion) to another ESXi host in the cluster.
The latest versions of vSphere 5.5 and 6.0 inhibit vMotion migration. However, storage vMotion is not blocked, and such movement may lead to unpredictable results on the destination host.
vCenter Server 6.0 restart/reboot results in duplicate VTEPs on VXLAN prepared ESXi hosts (2144605). The NSX-side update to protect against this issue is available in 6.2.3. This issue will be resolved fully in a future version of vCenter.
Important new and changed documentation with NSX for vSphere 6.2.3 – see the NSX Documentation Center
How to track the top field issues
VMware is actively working to address a recently discovered issue wherein an incremental backup becomes a full backup when backing up Windows 2008 (or higher) virtual machines with VSS-based application quiesced snapshot.
This recent CBT (Changed Block Tracking) issue does not cause any data loss or data corruption.
This issue is well understood and VMware engineering is actively working on a fix.
For more details on this issue and latest status on resolution, please refer to KB article: After upgrading to ESXi 6.0 Build 3825889, incremental virtual machine backups effectively run as full backups when application consistent quiescing is enabled (2145895)
Subscribe to the rss feed for the KB article to ensure you do not miss any update by using this link.
Our NSX support team would like all of our customers to know about important KB updates for NSX for vSphere issues.
Here’s what’s new and trending-
Important: Upgrades from NSX for vSphere 6.1.6 to 6.2.2 are not supported.
See KB 2145543 NSX Controller upgrade fails with the error: 409 (Conflict); invoking error handler.
vCloud Networking and Security will reach End of Availability and End of General Support on September 19, 2016.
NEW! See our first NSX KBTV YouTube video: https://youtu.be/5pSNfnk1_MA
vShield Endpoint and vCNS End Of Availability (EOA) – See:
KB 2105558 Support for partner integrations with VMware vShield Endpoint and VMware vCloud Networking and Security.
KB 2110078 Implementation of VMware vShield Endpoint beyond vCloud Networking and Security End of Availability (EOA).
Future releases of NSX for vSphere 6.2.x will enable customers to manage vShield Endpoint from NSX Manager. Customers who purchased vSphere with vShield Endpoint will be able to download NSX.
NSX for vSphere 6.1.x will reach End of General Support on October 15, 2016.
NEW! VMware has extended the End of General Support date to three years after GA for NSX for vSphere 6.2.x only. The VMware Lifecycle Product Matrix now reflects this change.
New and Important issues:
KB 2144551 Configuring a default gateway on the DLR in NSX fails
KB 2144605 vCenter 6.0 restart/reboot may result in duplicate VTEPs on VXLAN prepared ESX hosts.
KB 2143998 NSX Edge virtual machines do not failover during a vSphere HA event
KB 2145571 NSX Edge fails to power on when logging all ACCEPT firewall rules
KB 2145468 NSX Edge uplink interface does not process any traffic after it is disabled and re-enabled in ECMP environment
KB 2139067 Shutdown/Startup order of the NSX for vSphere 6.x environment after a maintenance window or a power outage. Please refer to the updated sequence for a cross VC environment.
KB 2145447 NetX/Service Instance filter created in vCNS disappears after upgrading to NSX
KB 2145322 NSX Edge logs show Memory Overloaded warnings
KB 2144901 Unexpected TCP interruption on TCP sessions during Edge High Availability (HA) failover in VMware NSX for vSphere 6.2.x
KB 2145273 Troubleshooting DLR using NSX Central CLI
KB 2145359 Pings fail between two VMs on different hosts across a logical switch
How to track the top field issues:
vCloud Networking and Security will reach end of availability and end of support on September 19, 2016.
- KB 2144733 – End of Availability and End of Support Life for VMware vCloud Networking and Security 5.5.x
- See the fully updated vCNS to NSX Upgrade Guide
- See also KB 2144620 – VMware vCloud Networking and Security 5.5.x upgrade to NSX for vSphere 6.2.x Best Practices
- Upgrade path from vCNS 5.x: Using the NSX upgrade bundle posted on or after 31 March, 2016, you may upgrade directly from vCNS 5.1.x or vCNS 5.5.x to NSX 6.2.2 Please see the NSX 6.2.2 release notes
- Upgrades from NSX 6.1.5 to NSX 6.2.0 are not supported. Instead, you must upgrade from NSX 6.1.5 to NSX 6.2.1 or later to avoid a regression in functionality. Refer to KB 2129200
NSX for vSphere 6.1.x will reach end of availability and end of support on October 15, 2016
- KB 2144769 – End of Availability and End of Support Life for VMware NSX for vSphere 6.1.x
- The recommended release for NSX-V is 6.2.2. Refer to KB 2144295 – Recommended minimum version for VMware NSX for vSphere with Guest Introspection Driver, ESXi and vCenter server.
- KB 2144726 – Service Composer fails to translate virtual machines into security-groups in VMware NSX for vSphere 6.x
- KB 2140891 – Storage vMotion of Edge appliance disrupts VIX communication in VMware vCloud Networking and Security 5.5.x and NSX for vSphere 6.x
- KB 2144476 – After reinstalling vCenter Server 6.0 EAM fails to push VIB’s to ESXi host with the error: Host not covered by scope anymore
- KB 2144456 – Importing draft firewall rules fails after existing firewall configuration is removed by a REST API request
- KB 2144387 – After upgrading to VMware NSX for vSphere 6.2.2 there is no upgrade option available for NSX Guest Introspection and NSX Data Security and the services remain at version 6.2.1
- KB 2144420 – Any changes to the Primary UDLR result in the vNic_0 being shutdown on the Seconday UDLR in VMware Cross-vCenter NSX for vSphere 6.2.x
- KB 2144236 – VMtools issue – Virtual machine performance issues after upgrading VMware tools version to 10.0.x in NSX/ VMware vCloud Networking and Security 5.5.x
- KB 2144649 – IPv4 IP address do not get auto approved when SpoofGuard policy is set to Trust On First Use (TOFU) in VMware NSX for vSphere 6.2.x
- KB 2144732 – In VMware NSX for vSphere 6.x, unpreparing Stateless ESXi host fails with the error: Agent VIB module is not installed. Cause : 15 The installation transaction failed. The transaction is not supported
- KB 2135956 – VMware ESXi 6.0 Update 1 host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4923 – Usage error in dlmalloc – now resolved in vSphere 6.0U2. See also the vSphere 6.0U2 Release Notes
- KB 2126275 – Publishing Distributed Firewall (DFW) rules fails after referenced object is deleted in VMware NSX for vSphere 6.1.x and 6.2.x
Tracking the top issues:
There are many, many, blogs, forums, videos channels out there that cover various VMware topics, and we commonly see our KB articles being linked from those sites.
We wanted to help those doing this with a couple of quick tips that will make your links easier to read and more resilient to potential changes in our CMS in the future.
When you open one of our KB articles and look at your URL bar, you’ll see a long, and parameterized URL. For example:
As you can see, this URL includes unnecessary parameters for sharing and just looks long and ugly. Here’s a much cleaner format to use:
The beginning part is always the same, just substitute the actual KB number you wish to reference at the end. Also note that we are now using https rather than the older and less secure http protocol.
Hope this helps those of you sharing our content; you have our thanks!
Over the weekend, the VMware Knowledgebase website was upgraded to improve the customer experience in several ways.
Main objectives of the upgrade were to:
- Upgrade the Knowledgebase application software/hardware
- Improve stability and security of the website
- Implement Secure Sockets Layer (SSL)
- Implement a Captcha system into the comments area
We will continue our efforts to make the Knowledgebase system as secure and robust as our customers expect.
Here is a list of currently trending KBs for NSX for vSphere
Netcpa issues in VMware NSX for vSphere 6.x (2137005)
- Virtual machines running on the same ESXi host fails to communicate with each other
- Virtual machine fails to communicate with the NSX Edge Gateway (ESG)
- Routing does not appear to be functioning despite having a defined route for the NSX Edge Gateway
- Rebooting the NSX Edge does not resolve the issue
- Running the esxcli network vswitch dvs vmware vxlan network list –vds-name=Name_VDS command on the ESXi host displays the VNIs as down
Network connectivity issues after upgrading or repreparing ESXi hosts in a VMware NSX/VCNS environment (2107951)
- Connecting virtual machines to a logical switch fails
- Re-connecting the virtual machine to a logical switch fails
Oracle connections times out when forwarded through the VMware NSX for vSphere 6.1.x Edge (2126674)
- Oracle connections times out when forwarded through the VMware NSX for vSphere 6.1.x Edge
- The NSX Edge is dropping packets and client/server keeps re-transmitting the same particular packets
MSRPC connections time out when forwarded through the VMware NSX for vSphere 6.1.x Edge (2137751)
- MSRPC connections time out when forwarded through the VMware NSX for vSphere 6.1.x Edge
Linux virtual machines with NFSv3 mounts experience an operating system hang after more than 15 minutes outage on the upstream datapath (2133815)
- Applications interacting with an NFSv3 mount experience a hang on hard mounted NFSv3 mounts or an error on soft mounted NFSv3 mounts after more than 15 minute upstream data path failure
- The virtual machine performance increasingly degrades with the time it resides in an NFS hung state
VMware ESXi 6.0 Update 1 host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4923 – Usage error in dlmalloc (2135956)
- VMware ESXi 6.x host fails with a purple diagnostic screen
- Netflow function is enabled on the ESXi host
Recommended minimum VMware Tools versions for Guest Instrospection in VMware NSX for vSphere 6.x (2139740)
- Windows virtual machines using the vShield Endpoint TDI Manager or NSX Network Introspection Driver (vnetflt.sys) driver fails with a blue diagnostic screen
Understanding and troubleshooting Message Bus in VMware NSX for vSphere 6.x (2133897)
- This article can be referred to when it is suspected that a communication issue between the NSX Manager and the ESXi hosts is responsible for symptoms observed such as failure to publish configuration. Examples of such symptoms are:
- Publishing firewall rules fails
- Some of the ESXi hosts does not have the VDR/LIF information configured through the NSX Manager
Today we’d like to highlight one specific KB article related to View Composer. You might consider it a first step in addressing composer problems. The KB we’re talking about is:
This guide includes basic troubleshooting steps, issues observed in the process of composer installation or composer uninstall process, and finally operational issues. At the bottom of the KB there is a long list of related KBs that are also of interest if View composer problems are encountered.
- Basic Troubleshooting Questions
- Install and Uninstall VMware View Composer
- VMware View Composer Error Messages
- VMware View Composer Customization Failures
- Unknown VMware View Composer Failures