Question 320
During an independent network handover at the Coastal Haven branch of Riverton Health Center, the monitored service is video collaboration for clients in 172.18.14.0/24; incident reference is DC-8637. The on-duty analyst documents this symptom before proposing any configuration: OSPF neighbors repeatedly reset even though interface IP connectivity is stable and capture evidence shows incompatible hello/dead timers. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Monitor next-hop tracking, neighbor resolution and static route usability. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: OSPF neighbors repeatedly reset even though interface IP connectivity is stable and capture evidence shows incompatible hello/dead timers. This alternative addresses a different issue (static route next-hop validation). The decisive distinction is: Monitor neighbor transitions and timer-related syslog events.
This alternative addresses a different issue (ospf advertisement missing). The option would address: Monitor authorized prefix inventory against OSPF route distribution. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: OSPF neighbors repeatedly reset even though interface IP connectivity is stable and capture evidence shows incompatible hello/dead timers.
Audit IPAM allocations, address overlaps and host route table changes. This alternative addresses a different issue (cidr subnet boundary). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: OSPF neighbors repeatedly reset even though interface IP connectivity is stable and capture evidence shows incompatible hello/dead timers. The decisive distinction is: Monitor neighbor transitions and timer-related syslog events.
The on-duty analyst documents this symptom before proposing any configuration: OSPF neighbors repeatedly reset even though interface IP connectivity is stable and capture evidence shows incompatible hello/dead timers. That points to this explanation: Monitor neighbor transitions and timer-related syslog events.