Question 420
At fictional Uplands Retail, a network engineer supporting customer edge routers is reviewing OSPF area design and link-state convergence during a supervised route change (HCIP-H12-821-OSPF-105). The observed network issue is: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Apply compatible authentication settings and keys on both interfaces under controlled change. The specific reported fault is: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. Confirmation should show: Authenticated Hellos are accepted and the neighbor reaches the expected stable state. The supporting technical principle is: OSPF routing exchanges depend on matched authentication parameters when authentication is enabled.
Incorrect Answers
“Compare interface MTU and OSPF database-exchange behavior before considering any controlled workaround” responds to another technical or business failure: An OSPF neighbor stays in Exchange and large database description packets fail over a reduced-MTU tunnel. That source case depends on: Incompatible interface MTU can interrupt OSPF database synchronization. The present issue is: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. The more direct action is “Apply compatible authentication settings and keys on both interfaces under controlled change” because OSPF routing exchanges depend on matched authentication parameters when authentication is enabled.
“Restore an appropriate area 0 connection or review a supported planned virtual-link design” responds to another technical or business failure: A branch area has no direct backbone connectivity and operators try to exchange routes between nonbackbone areas directly. That source case depends on: OSPF inter-area routing depends on a contiguous logical backbone architecture. The present issue is: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. The more direct action is “Apply compatible authentication settings and keys on both interfaces under controlled change” because OSPF routing exchanges depend on matched authentication parameters when authentication is enabled.
“Investigate bidirectional Hello reception and permitted multicast or interface filtering on the segment” responds to another technical or business failure: A transit OSPF link remains in Init because one router never sees its own router ID listed in neighbor Hellos. That source case depends on: OSPF two-way communication is established only after reciprocal Hello discovery. The present issue is: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. The more direct action is “Apply compatible authentication settings and keys on both interfaces under controlled change” because OSPF routing exchanges depend on matched authentication parameters when authentication is enabled.