Cisco – How to Schedule an Automatic Reboot

Posted on by

In some situations, such as persistent memory issues with a switch, scheduling automatic reboots can ensure that the device operates optimally. This is particularly useful if you need the switch to be in a stable state at the start of the day. Cisco devices allow you to configure reboots to occur after a specific period or at a set time.

Below is a detailed guide to scheduling and managing automatic reboots on Cisco switches.

Types of Automatic Reboots

Cisco switches provide flexibility in scheduling reboots. You can:

  1. Schedule a reboot to occur after a specific time interval.
  2. Schedule a reboot to occur at an exact time and date.

Scheduling a Reboot After a Time Interval

To schedule a reboot to happen after a specific period, use the following command:

reload in [HH:MM]

For example, to reboot the switch 2 hours and 30 minutes from now, you would execute:

sos-admins01#reload in 2:30
Reload scheduled for 07:22:15 UTC Thu Jan 14 2016 (in 2 hours and 30 minutes)
Proceed with reload? [confirm]

When you confirm, the switch will automatically reboot at the scheduled time.

Scheduling a Reboot at a Specific Time and Date

If you want the reboot to occur at a particular hour and date, use the command:

reload at [HH:MM] [DD] [Month]

For example, to schedule a reboot at 7:30 AM on January 14th, the command would be:

sos-admins01#reload at 7:30 14 jan
Reload scheduled for 07:30:00 UTC Thu Jan 14 2016 (in 1 hours and 22 minutes)
Proceed with reload? [confirm]

This is useful for planning reboots during maintenance windows or periods of low network activity.

Checking Scheduled Reboots

To verify if any automatic reboots are currently scheduled, use the following command:

show reload

This will display any pending reload schedules, allowing you to confirm if a reboot has been properly set.

Canceling a Scheduled Reboot

If you need to cancel a previously scheduled reboot, use the command:

reload cancel

For example:

sos-admins01#reload cancel

This command ensures that no unexpected reboots occur if plans change.

Best Practices

  1. Plan for Maintenance Windows: Always schedule reboots during low-traffic periods, such as late at night or early morning, to minimize disruption to users.
  2. Inform Stakeholders: Notify your team or users about planned reboots to avoid surprises.
  3. Verify the Configuration: Before scheduling a reboot, double-check that the device’s configuration is saved to avoid losing changes. Use the write command to save configurations.

By leveraging these commands, you can automate the maintenance of your Cisco switches, ensuring they remain reliable and performant without requiring constant manual intervention.