Question 440
During an independent network handover at the Hollow Creek branch of North Basin Transit, the monitored service is fleet booking for clients in 10.115.6.0/24; incident reference is DC-8841. The on-duty analyst documents this symptom before proposing any configuration: A downstream OSPF route remains in forwarding briefly after a link failure because failure detection and reconvergence lag behind link state. 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 ND failures, duplicate address detection and blocked critical ICMPv6 types. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A downstream OSPF route remains in forwarding briefly after a link failure because failure detection and reconvergence lag behind link state. This alternative addresses a different issue (ipv6 neighbor discovery). The decisive distinction is: Measure convergence intervals and route flap frequency during fault drills.
This alternative addresses a different issue (longest prefix route selection). The option would address: Monitor route insertion/deletion and path selection for important destination prefixes. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A downstream OSPF route remains in forwarding briefly after a link failure because failure detection and reconvergence lag behind link state.
Monitor asymmetric route changes and stateful firewall drops for the service. This alternative addresses a different issue (return path symmetry). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A downstream OSPF route remains in forwarding briefly after a link failure because failure detection and reconvergence lag behind link state. The decisive distinction is: Measure convergence intervals and route flap frequency during fault drills.
The on-duty analyst documents this symptom before proposing any configuration: A downstream OSPF route remains in forwarding briefly after a link failure because failure detection and reconvergence lag behind link state. That points to this explanation: Measure convergence intervals and route flap frequency during fault drills.