Search the VMware Knowledge Base (KB)
View by Article ID

Fenced vApps fails in vCloud Director 8.20 after upgrading to NSX for vSphere 6.3.x (2150010)

  • 0 Ratings
Language Editions


After upgrading from NSX to 6.3.x and NSX Edge Gateways to 6.3.x in vCloud Director 8.20, you experience these symptoms:
  • Fence vApps fails
  • Virtual machines in a fenced network fails to communicate to its gateway


In NSX 6.3.x Edge Gateways, a new route table is introduced (table 251) which is always looked up first for routes. The main table (table 254) is looked up only when the table 251 does not have a route. The issue occurs because the device routes (a /32 route for vApp VM) are auto-plumbed to the main table, whereas table 251 already has a default route in it. Therefore, since the table 251 already has a default route, the lookup never happens on the main table and hence the fenced vApp virtual machines lose connectivity.


This issue is resolved in VMware NSX for vSphere 6.3.2, available at VMware Downloads.

To work around this issue if you have already upgraded to NSX for vSphere 6.3.0 or 6.3.1 using Fenced vApps in vCloud Director 8.20, contact VMware Support. To contact VMware support, see Filing a Support Request in My VMware (2006985) or How to Submit a Support Request.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings