A BGP session across an unplugged cable stays Established and keeps its routes #1269
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1269
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Two routers, eBGP over one cable. Session up, prefix learned. Now pull the cable:
The cable is out. The session says Established, the prefix stays installed, and
show ip routeoffers aBroute whose next hop cannot be reached — so the routing table claims a path that does not exist. Shutting the
far port produces the same thing.
_bgpReachable()askediface.enabled— "did somebody shut this port" — and nothing else. Not whether thecable is in, not whether the link is up, not whether the far port is up. That is the same question
show ip interface briefwas answering wrongly before #1237, and the same rule (Device.ifaceStatus(iface, topo)) now exists for it.Separately,
show ip bgpprinted a count of installed prefixes and no way to see which prefixes, offwhich peer, with what path — the next question, and the one
show ip routesends you here with.Expected
admin-down port each end the session, with the reason naming the actual fault (
cannot carry a frame (link down),(peer shut down),administratively down) rather than "down on the router";Brow survives asession that is down;
show ip bgplists the installed prefixes with next hop, MED, local preference, weight, AS path and origin,and marks the session type — and the prefix length printed there matches
show ip route's, one mask rule;Scope
The existing BGP reachability check and the existing
show ip bgpoutput. No new commands, no new configsurface.
show ip routecannot say a next hop is unreachable #1271