Question 640
A new OSPF uplink remains down at the adjacency stage after a router replacement. What should the operations engineer do first to address the stated fault?
Explanation
Correct Answer
Correct diagnosis: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. The appropriate action is: Compare area, interface mode, timers, authentication and physical status on both endpoints. The follow-up evidence required is: The corrected link reaches stable Full adjacency and exchanges the intended routes.
Incorrect Answers
This answer would be more suitable when oSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path, where the corrective action is to review each interface's OSPF metric and compare end-to-end computed costs. The failure here is different: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Required validation: The corrected link reaches stable Full adjacency and exchanges the intended routes.
Route preference determines the selected route before any multipath decision describes a neighboring protocol concern. In this case the controlling fact is layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. A correct remediation would compare area, interface mode, timers, authentication and physical status on both endpoints and demonstrate: The corrected link reaches stable Full adjacency and exchanges the intended routes.
The proposed principle concerns another network fault: OSPF network-type and Hello compatibility can prevent adjacency formation. Here, layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. The most direct correction is to compare area, interface mode, timers, authentication and physical status on both endpoints, confirmed by the corrected link reaches stable Full adjacency and exchanges the intended routes.