Default BGP route is missing from routing table.
search cancel

Default BGP route is missing from routing table.

book

Article ID: 441202

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Running the following command on an NSX edge shows the default BGP route is learned from the upstream switch.

    edge(tier0-vrf_sr[0])> get bgp neighbor <IP> routes
    BGP table version is 12, local router ID is <IP>
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
    Origin codes: i - IGP, e - EGP, ? - incomplete

       Network          Next Hop            Metric LocPrf Weight Path
    *> 0.0.0.0/0        <IP>              0             0 <AS> i

  • Although the route is learned from BGP, it is not installed into the routing table. The following command does not show the BGP-advertised default route.

    edge-1(tier0-vrf_sr[0])> get routes

  • The routing table (get routes) also doesn't contain a route to the next hop of the default route.

Environment

VMware NSX

Resolution

This is a configuration issue. The solution depends on where the misconfiguration resides.

Option A:
If the next hop IP/subnet of the advertised default route is incorrect, adjust the default route that is being advertised from the upstream switch.

Option B:
If the advertised next-hop IP/subnet is correct, verify and adjust the Tier-0 uplink interface configuration to ensure a directly connected route is generated for that subnet.