352-001 · Question #549
A network is designed to use OSPF to reach eBGP peers. For eBGP peers to stay stable in case of a link failure, what condition should be avoided?
The correct answer is D. Advertise IP addresses used on eBGP peer statements via eBGP. When OSPF is used to reach eBGP peers, advertising the eBGP peer addresses only via eBGP creates a recursive routing failure when the session drops, because the route to the peer is lost along with the session.
Question
A network is designed to use OSPF to reach eBGP peers. For eBGP peers to stay stable in case of a link failure, what condition should be avoided?
Options
- AAdvertise IP addresses used on eBGP statements via a normal OSPF area
- BUse an ACL to block BGP in one direction
- CDisable BGP synchronization
- DAdvertise IP addresses used on eBGP peer statements via eBGP
How the community answered
(38 responses)- A8% (3)
- B13% (5)
- C24% (9)
- D55% (21)
Why each option
When OSPF is used to reach eBGP peers, advertising the eBGP peer addresses only via eBGP creates a recursive routing failure when the session drops, because the route to the peer is lost along with the session.
Advertising eBGP peer addresses into a normal OSPF area is the recommended practice, as it provides IGP-based stability independent of the BGP session state.
Using an ACL to block BGP in one direction is a policy or security action unrelated to the routing stability problem caused by recursive lookup failures.
Disabling BGP synchronization is a standard modern practice that prevents BGP from waiting for IGP convergence before advertising routes, and does not affect peer reachability stability.
If the IP addresses used in eBGP peer statements are only reachable via eBGP-learned routes, a session failure causes those routes to be withdrawn. This creates a recursive lookup failure where the router cannot re-establish the session because the route to the peer no longer exists, making recovery impossible. Peer addresses should always be reachable via a stable IGP such as OSPF.
Concept tested: eBGP peer reachability via IGP to prevent recursive routing failure
Source: https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html
Topics
Community Discussion
No community discussion yet for this question.