Question 530
At fictional Keystone Hospitality, a network engineer supporting guest services is reviewing BGP routing, path attributes and EVPN exchange during an initial deployment test (HCIP-H12-821-BGP-133). The observed network issue is: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. Which routing, switching, or network principle best explains the appropriate solution?
Explanation
Correct Answer
The governing principle is: BGP TCP endpoints must match peer configuration and be routable in both directions. In this scenario, the appropriate action is: Configure a consistent loopback update source and verify bidirectional route to peer addresses. Valid evidence would show: Both routers reach Established using the planned loopback source and destination.
Incorrect Answers
“EVPN multihoming uses Ethernet Segment identification and designated-forwarder coordination” responds to another technical or business failure: A multihomed EVPN Ethernet segment advertises conflicting identifiers and an engineer assumes all attached devices will suppress duplicates automatically. That source case depends on: EVPN multihoming uses Ethernet Segment identification and designated-forwarder coordination. The present issue is: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. The more direct action is “BGP TCP endpoints must match peer configuration and be routable in both directions” because BGP TCP endpoints must match peer configuration and be routable in both directions.
“BGP FSM states distinguish session formation failures from routing-update processing” responds to another technical or business failure: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. That source case depends on: BGP FSM states distinguish session formation failures from routing-update processing. The present issue is: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. The more direct action is “BGP TCP endpoints must match peer configuration and be routable in both directions” because BGP TCP endpoints must match peer configuration and be routable in both directions.
“EVPN Type 2 routes distribute endpoint MAC reachability and related IP bindings” responds to another technical or business failure: A VXLAN VTEP fails to learn a remote host's MAC and IP even though underlay IP reachability is working. That source case depends on: EVPN Type 2 routes distribute endpoint MAC reachability and related IP bindings. The present issue is: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. The more direct action is “BGP TCP endpoints must match peer configuration and be routable in both directions” because BGP TCP endpoints must match peer configuration and be routable in both directions.