Question 550
At fictional Lakeshore Finance, a network engineer supporting transaction systems is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-138). The observed network issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. Which routing, switching, or network principle best explains the appropriate solution?
Explanation
Correct Answer
The governing principle is: OSPF interface network type affects neighbor handling and designated router behavior. In this scenario, the appropriate action is: Align compatible OSPF network types and validate hello and DR behavior for the actual media. Valid evidence would show: Neighbors form a stable adjacency without an unintended DR election on the point-to-point link.
Incorrect Answers
“OSPF E1 and E2 external cost calculations treat internal path costs differently” responds to another technical or business failure: An engineer mistakes an OSPF external Type 2 metric for a path whose internal costs are always added to its advertised value. That source case depends on: OSPF E1 and E2 external cost calculations treat internal path costs differently. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.
“OSPF neighbor liveness requires compatible timer parameters on the shared network” responds to another technical or business failure: Routers have the same network prefix but one side uses a different OSPF Hello interval on an Ethernet segment. That source case depends on: OSPF neighbor liveness requires compatible timer parameters on the shared network. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.
“Totally stubby area behavior reduces inter-area summary visibility beyond ordinary stub restrictions” responds to another technical or business failure: An OSPF totally stubby area receives unwanted detailed inter-area routes after only one router's configuration changes. That source case depends on: Totally stubby area behavior reduces inter-area summary visibility beyond ordinary stub restrictions. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.