Connectivity outage after reboot of NSX Manager
search cancel

Connectivity outage after reboot of NSX Manager

book

Article ID: 301269

calendar_today

Updated On:

Products

VMware NSX Networking VMware NSX

Issue/Introduction

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 vdr1+edge-13, universal: false, localEgress: false
    2016-12-02T07:14:49.364Z [FFF64B70 info 'Default'] Purged stale vdrId 12001, vdrName vdr2+edge-8, universal: false, localEgress: false
    2016-12-02T07:14:49.364Z [FFF64B70 info 'Default'] Purged stale vdrId 12006, vdrName vdr3+edge-25, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12004, vdrName vdr4+edge-20, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12002, vdrName vdr5+edge-10, universal: false, localEgress: false
    2016-12-02T07:14:49.365Z [FFF64B70 info 'Default'] Purged stale vdrId 12005, vdrName vdr6+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.xxx.yyy.zzz 10.xxx.yyy.zzz

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

Environment

VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.2.x

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 Downloading Broadcom products and Software.

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.

 

Additional Information

中文简体:重新引导 NSX Manager 后连接中断