Missing IP Addresses on Tier0 NSX Edge Node Interfaces in CLI

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

The output from the CLI command "get interfaces" on the Tier0 Gateway in the NSX Edge node indicates that the Uplink interfaces are missing IP addresses.

Logical Router
UUID VRF LR-ID Name Type 
########-####-####-###############0a 1 13488 SR-T0 SERVICE_ROUTER_TIER0 
Interfaces (IPv6 DAD Status A-DAD_Success, F-DAD_Duplicate, T-DAD_Tentative, U-DAD_Unavailable)

    Interface : ########-####-####-###############6e
    Ifuid : 123
    Name : T0-uplink
    Fwd-mode : IPV4_ONLY
    Internal name : uplink-123
    Mode : lif
    Port-type : uplink
    IP/Mask : <------------------------------------------------------------------No IP address
    MAC : ##:##:##:##:##:b3
    VLAN : <vlan id>
    Access-VLAN : untagged
    LS port : ########-####-####-###############36
    Urpf-mode : NONE
    DAD-mode : LOOSE
    RA-mode : SLAAC_DNS_THROUGH_RA(M=0, O=0)
    Admin : up
    Op_state : up
    Enable-mcast : False
    MTU : <mtu number>
    arp_proxy :  

In the Edge node log at /var/log/frr/frr.log, entries similar to the following are observed:

BGP: [EC 33554465] <IPv4-address-1> [FSM] Failure handling event BGP_Start in state Idle, prior events BGP_Start, BGP_Start, fd -1
BGP: [Event] Incoming BGP connection rejected from <IPv4-address-1> since it is not directly connected and TTL is 1

In the Edge node log /var/log/syslog, the following events are observed:

nsx-edge-1 bgpd 22005 - - [EC 33554465] <IPv6-address-1> [FSM] Failure handling event BGP_Start in state Idle, prior events BGP_Start, BGP_Start, fd -1
nsx-edge-1 bgpd 22005 - - [EC 33554465] <IPv6-address-2> [FSM] Failure handling event BGP_Start in state Idle, prior events BGP_Start, BGP_Start, fd -1

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

Please note that while this issue may appear similar to the one discussed in this KB article 322523, the workaround provided there is applicable only when FRR does not have the IP addresses. This KB refers to an instance where the uplink itself is missing the IP address, indicating that this is a different issue.

Environment

VMware NSX

VMware NSX-T Data Center

Cause

This issue can be caused by a stale LIF, leading to a duplicate IP issue at LCP when a new port with the same IP address is created.

Resolution

Restart the local controller service via edge CLI using the command:

restart server local-controller