Best practice - prevent connectivity loss of remote device

When configuring a remote device with various parameters, it is always best practice to take precautions to prevent loss of connectivity, or if connectivity is lost, to ensure that it can automatically be reestablished.

This can be done using the reload in or reload at commands.

When configuring a device using the command line via Telnet or SSH, it is best practice to issue the reload in or the reload at command and cause the device to reload within a brief period of time, such as five or ten minutes. This can be done like so:

Router# reload in 10
Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)
Proceed with reload? [confirm]
Router#

Or:

Router# reload at 13:00
Router# Reload scheduled for 13:00:00 PDT Fri Apr 21 1996 (in 1 hour and 2 minutes)
Proceed with reload? [confirm]
Router#

The reload at command requires that the device's clock is correctly set on the device.

Using these commands, if you accidently lose connectivity to the device because of commands that you are entering (such as Access-List (ACL)s or Routing modifications for example), then the device will automatically reboot in a few moments with its startup configuration, allowing you to reestablish connectivity.

This best practice is especially useful for those devices found in remote areas, because it will save you or a colleague a trip to the device to reboot it manually.

Once you successfully configure the device, you can then cancel the reload command.