of disaster is with the reload command. With this command, you can make a router reboot in a set amount of time. Because the configuration that caused the router to become unavailable will not have been saved, having the router reboot automatically will bring the router back to life. To reboot the router in 15 minutes, issue the reload in command, as shown here: TS-1#reload in 15 Reload scheduled in 15 minutes Proceed with reload? [confirm] Alternatively, you can specify a time at which to reload the router with the reload at command: TS-1#reload at 12:05 July 10 Reload scheduled for 12:05:00 UTC Mon Jul 10 2006 (in 566 hours and 33 minutes) Proceed with reload? [confirm] Be warned that if you've already started to make your changes, the router will prompt you to save them before you reload. Remember to cancel the reboot when you've successfully made your change! To cancel an impending scheduled reload, execute the reload cancel command: TS-1#reload cancel TS-1# SHUTDOWN ABORTED Multiple Component Failure Many networks are designed to avoid single points of failure. What usually brings these networks down is multiple component failure. Multiple component failure can be trig- gered by a root cause such as dirty or unreliable power, or it can just be a fluke. One device can also sometimes cause failures in other devices. Many enterprise networks employ Cisco PIX or ASA firewalls in redundant pairs. This is a reliable and proven way to ensure that your firewall isn't a single point of failure. If the standby firewall fails and nobody knows about it, the remaining firewall is a single point of failure. The problem is that many people install these failover pairs and then don't monitor them in any way. I once had a client whose secondary firewall had been offline for months. When the primary failed, the entire network went offline and the executives started screaming. Since no one had been checking the firewalls, everyone assumed that all was well. Nothing sells network management tools like a previously unknown failu