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

Connectivity outage after reboot of NSX Manager (2150701)

  • 0 Ratings

Symptoms

  • ESXi host purges all VDR instances except one VDR instance, leaving only one VDR instance on the host.

  • In the ESXi host netcpa.log file, you see entries similar to:

    2016-12-02T07:14:49.364Z [FFF64B70 info 'Default'] Purged stale vdrId 12003, vdrName tenant2+edge-13, universal: false, localEgress: false
    2016-12-02T07:14:49.364Z [FFF64B70 info 'Default'] Purged stale vdrId 12001, vdrName pentest+edge-8, universal: false, localEgress: false
    2016-12-02T07:14:49.364Z [FFF64B70 info 'Default'] Purged stale vdrId 12006, vdrName t-ous+edge-25, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12004, vdrName p-ous+edge-20, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12002, vdrName tenant1+edge-10, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12005, vdrName Tmz0+edge-3, universal: false, localEgress: false


  • Running the command net-vdr --instance --brief -l on the ESXi host, you see only one VDR instance.

    VDR Instance Information :
    ---------------------------

    State Legend: [A: Active], [D: Deleting], [X: Deleted], [I: Init]
    State Legend: [SF-R: Soft Flush Route], [SF-L: Soft Flush LIF]

    Vdr Name   Vdr Id   #Lifs  #Routes  State  Controller Ip   CP Ip
    --------  -------   -----  -------  -----  -----------    ------
    edge-6     0x2ee0    2       6       A     10.129.84.71   10.129.83.137


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when distributed logical router (DLR) instances were purged from ESXi hosts as a result of incorrect partial sync of VDR.

Resolution

This issue is resolved in NSX for vSphere 6.2.5 and NSX for vSphere 6.3.0, available at VMware Downloads.
 
To work around the issue if you do not want to upgrade, perform a Force-sync of the routing service.
  1. In the vSphere Web Client, navigate to Home > Networking & Security > Installation, select the Host Preparation tab.
  2. Select Cluster > Click Force Sync Service from the Action menu.
  3. Select Routing and Click OK.

Note: Force Sync of Routing requests all hosts to initiate Vdr Instance List from VSM again. VSM sends Vdr Instance list for all the VDRs and all Vdr Instance will be created on the host.

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.

Feedback

  • 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
Actions
KB: