Question 140
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPFv2 interface remains stuck in EXSTART on an Ethernet service whose two ends have inconsistent MTUs. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: An OSPFv2 interface remains stuck in EXSTART on an Ethernet service whose two ends have inconsistent MTUs. The most directly supported response is: Check and reconcile supported MTU and adjacency parameters before applying disruptive resets. Technical basis: OSPF database description exchange can fail when adjacent interfaces disagree on required parameters. Evidence of success: Neighbors progress to FULL and exchange the expected link-state database. Ongoing protection: Include link MTU compatibility in OSPF turn-up validation.
Incorrect Answers
That recurring practice manages a separate exposure: BGP may retain several path candidates while selecting a subset for best-path and forwarding use. The present case instead depends on: OSPF database description exchange can fail when adjacent interfaces disagree on required parameters. The suitable ongoing safeguard is: Include link MTU compatibility in OSPF turn-up validation.
That recurring practice manages a separate exposure: BGP routing policy controls prefix acceptance, while forwarding uses the most specific installed route. The present case instead depends on: OSPF database description exchange can fail when adjacent interfaces disagree on required parameters. The suitable ongoing safeguard is: Include link MTU compatibility in OSPF turn-up validation.
That recurring practice manages a separate exposure: BGP requires a successful TCP session before exchanging UPDATE messages. The present case instead depends on: OSPF database description exchange can fail when adjacent interfaces disagree on required parameters. The suitable ongoing safeguard is: Include link MTU compatibility in OSPF turn-up validation.