Question 160
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. The most directly supported response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior. Technical basis: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of success: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT. Ongoing protection: Use packet-level hello tests when control-plane filters change.
Incorrect Answers
The alternative guards against: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The root condition for this case is: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The focused prevention check is: Use packet-level hello tests when control-plane filters change.
The alternative guards against: Unbounded redistribution expands IGP state and can affect convergence and resource use. The root condition for this case is: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The focused prevention check is: Use packet-level hello tests when control-plane filters change.
That recurring practice manages a separate exposure: Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. The present case instead depends on: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The suitable ongoing safeguard is: Use packet-level hello tests when control-plane filters change.