Which steps are essential after a routing change to ensure convergence and no forwarding gaps?

Which steps are essential after a routing change to ensure convergence and no forwarding gaps?

• A. Verify routing table entries, neighbor adjacencies, and logs; confirm ACLs and NAT as needed.
• B. Disconnect all devices to force reset.
• C. Ignore interface states and adjacencies.
• D. Reboot all routers.

Answer: (A)

After a routing change, you want the network to reach a stable state where every router’s forwarding table reflects the new topology and traffic can flow without gaps. The best way to confirm that is to verify three things together: the routing table entries, the neighbor adjacencies, and the system logs. Checking the routing table on key routers shows which routes are installed, their next-hops, and metrics, confirming that the intended paths are actually being used. Verifying neighbor adjacencies ensures that the routing protocol has formed proper sessions with its peers and that routes are being learned and propagated across the network, not just locally configured. Reviewing logs helps you spot any convergence issues, such as route flaps, stale adjacencies, or redistribution problems that can slow or disrupt convergence. It’s also important to confirm ACLs and NAT as needed because a routing change can alter traffic paths in ways that cause filters to block or translations to fail, creating forwarding gaps even when routes exist. In practice, a quick check across the network focuses on: are routes present and reachable in the routers’ tables, are protocol adjacencies stable, and are there any warning signs in logs? If all of these align, traffic should converge smoothly. Disruptive actions like disconnecting devices or rebooting do not address the need to validate the actual forwarding state and can hide or create problems rather than solve them.

After a routing change, you want the network to reach a stable state where every router’s forwarding table reflects the new topology and traffic can flow without gaps. The best way to confirm that is to verify three things together: the routing table entries, the neighbor adjacencies, and the system logs. Checking the routing table on key routers shows which routes are installed, their next-hops, and metrics, confirming that the intended paths are actually being used. Verifying neighbor adjacencies ensures that the routing protocol has formed proper sessions with its peers and that routes are being learned and propagated across the network, not just locally configured. Reviewing logs helps you spot any convergence issues, such as route flaps, stale adjacencies, or redistribution problems that can slow or disrupt convergence. It’s also important to confirm ACLs and NAT as needed because a routing change can alter traffic paths in ways that cause filters to block or translations to fail, creating forwarding gaps even when routes exist.

In practice, a quick check across the network focuses on: are routes present and reachable in the routers’ tables, are protocol adjacencies stable, and are there any warning signs in logs? If all of these align, traffic should converge smoothly. Disruptive actions like disconnecting devices or rebooting do not address the need to validate the actual forwarding state and can hide or create problems rather than solve them.