Question 590
An NSR configuration fails commit after an operator adds graceful restart on the same device. What diagnosis and engineering response are most appropriate?
Explanation
Correct Answer
Correct diagnosis: Conflicting local GR and NSR configuration must be resolved before activation. The appropriate action is: Remove the incompatible local mode and validate the supported HA configuration. The follow-up evidence required is: The corrected candidate commits and the Routing Engine synchronization check passes.
Incorrect Answers
The alternative addresses an engineer expects a designated router to be elected on a point-to-point OSPF circuit, not the present root cause. Here the selected correction must reflect conflicting local GR and NSR configuration must be resolved before activation. Test for: The corrected candidate commits and the Routing Engine synchronization check passes.
This answer would be more suitable when a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart, where the corrective action is to check whether GRES is paired with the intended GR or NSR support and verify protocol state. The failure here is different: Conflicting local GR and NSR configuration must be resolved before activation. Required validation: The corrected candidate commits and the Routing Engine synchronization check passes.
This option overlooks the decisive condition. Its supporting principle is nonstop bridging protects relevant Layer 2 control-protocol state during switchover, while this scenario depends on conflicting local GR and NSR configuration must be resolved before activation. Verify the correction with: The corrected candidate commits and the Routing Engine synchronization check passes.