Question 680
For a wholesale transit provider, the change record describes: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. What preventive validation should be standard?
Explanation
Correct Answer
Verify lower-layer IGP readiness before diagnosing dependent BGP sessions. This helps prevent recurrence of the issue: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. Acceptance evidence should be: OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
Incorrect Answers
Include reference bandwidth standards in routing config review. That is a sensible control for ANOTHER scenario: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. It is less targeted to this issue than: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
Test protocol instance, VRF and AF together in route acceptance. That is a sensible control for ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It is less targeted to this issue than: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles. That is a sensible control for ANOTHER scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. It is less targeted to this issue than: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.