Working on broken networks is always an exciting business to be in—particularly if you work for a large vendor where large broken networks are brought to your door every day. To survive the constant onslaught, you eventually develop a set of simple and quick patches or changes you can always rely on to settle a network down so you can start the process of actually troubleshooting the problem. For example, one set of steps network engineers dealing with failures in a distance-vector control plane might take to stabilize the network could be:
• Look at the routing protocol topology database.
• Determine how many paths, on average, there are to any given destination in the table.
• Configure interfaces as passive ...