In a backbone router flood scenario, what will the other routers communicate to each other to maintain services?

In a backbone router flood scenario, what will the other routers communicate to each other to maintain services?

• A. The change in the routing fabric to bypass the affected router
• B. More RESET packets to the affected router to get it to power back up
• C. STOP packets to all other routers warning of where the attack originated
• D. RESTART packets to the affected router to get it to power back up

Answer: (A)

Routing convergence and path reconfiguration in response to a topology change. When a backbone router is flooded or otherwise fails, the other routers share topology information through the network’s routing protocols and quickly recompute new forwarding paths. This update makes them bypass the affected router, so traffic can still reach its destinations via alternate, healthy routes. In link-state protocols like OSPF or IS-IS, topology changes are flooded (LSAs) and each router recalculates its shortest-path tree to reflect the new network map. In distance-vector protocols, routers advertise updated costs to destinations, leading to a new converged routing table. The aim is to maintain services by altering the routing fabric, not by sending reset or restart signals to the failed device, which is not how routing continuity is achieved.

Routing convergence and path reconfiguration in response to a topology change. When a backbone router is flooded or otherwise fails, the other routers share topology information through the network’s routing protocols and quickly recompute new forwarding paths. This update makes them bypass the affected router, so traffic can still reach its destinations via alternate, healthy routes. In link-state protocols like OSPF or IS-IS, topology changes are flooded (LSAs) and each router recalculates its shortest-path tree to reflect the new network map. In distance-vector protocols, routers advertise updated costs to destinations, leading to a new converged routing table. The aim is to maintain services by altering the routing fabric, not by sending reset or restart signals to the failed device, which is not how routing continuity is achieved.