The first thing to confirm is whether the DLR instance has been created and whether its control plane is active.

  1. From the NSX Manager shell, run show cluster all to get the cluster ID.
  2. Run show cluster cluster-id to get the host ID.
  3. Run show logical-router host hostID dlr all verbose to get the status information.
nsxmgr# show logical-router host host-id dlr all verbose

VDR Instance Information :

Vdr Name:                   default+edge-1
Vdr Id:                     1460487509
Number of Lifs:             4
Number of Routes:           5
State:                      Enabled
Controller IP:    
Control Plane Active:       Yes
Control Plane IP: 
Edge Active:                No
The points to note:
  • This command displays all DLR instances that exist on the given ESXi host.
  • “Vdr Name” consists of “Tenant” “+ “Edge Id." In the example, “Tenant” was not specified, so the word “default” is used. The “Edge Id” is “edge-1," which can be seen in the NSX UI.
    • In cases where there are many DLR instances on a host, a method for finding the right instance is to look for the “Edge ID” displayed in the UI “NSX Edges."
  • “Vdr Id” is useful for further lookups, including logs.
  • “Number of Lifs” refers to the LIFs that exist on this individual DLR instance.
  • “Number of Routes” is in this case 5, which consists of 4 x directly connected routes (one for each LIF), and a default route.
  • “State,” “Controller IP,” and “Control Plane Active” refer to the state of the DLR’s control plane and must list the correct Controller IP, with Control Plane Active: Yes. Remember, the DLR function requires working Controllers; the output above shows what is expected for a healthy DLR instance.
  • “Control Plane IP” refers to the IP address that the ESXi host uses to talk to the Controller. This IP is always the one associated with the ESXi host’s Management vmknic, which in most cases is vmk0.
  • “Edge Active” shows whether or not this host is the one where the Control VM for this DLR instance is running and in Active state.
    • The placement of the Active DLR Control VM determines which ESXi host is used to perform NSX L2 bridging, if it is enabled.
  • There is also a “brief” version of the above command that produces a compressed output useful for a quick overview. Note that “Vdr Id” is displayed in hexadecimal format here:
nsxmgr# show logical-router host host-id dlr all brief

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
--------             -------    -----   ------- -----      -------------    ------
default+edge-1       0x570d4555 4       5       A

The “Soft Flush” states refer to short-lived transient states of the LIF lifecycle and is not normally seen in a healthy DLR.