reload
Restart a device to apply configuration changes that require a reboot, or to recover from a hung process.
Definition: reload is a Cisco IOS privileged exec command. Restarts the Cisco device, loading the IOS image specified by show boot and the startup configuration from NVRAM. Can be scheduled for a future time using 'reload in' or 'reload at'.
Overview
The reload command is a fundamental IOS command used to reboot a Cisco router or switch. It is typically executed from privileged EXEC mode (enable mode) and causes the device to perform a cold restart, reloading the IOS image and reinitializing all hardware and software components. The primary purpose of reload is to apply configuration changes that require a reboot (such as changes to the boot system variable, IOS upgrade, or certain hardware reinitializations) or to recover from a system hang or memory leak.
When a reload is initiated, the device will prompt the user to confirm, and if not confirmed within 60 seconds (default), the reload is cancelled. The command can be scheduled with a delay (e.g., reload in 10) to allow for a graceful shutdown or to give administrators time to save configurations. It is important to note that reload does not save the running configuration to startup-config; therefore, any unsaved changes will be lost upon reboot.
The command requires privilege level 15 (or equivalent) and is often used in conjunction with 'write memory' to ensure the startup configuration is updated. In a network troubleshooting workflow, reload is a last-resort action after verifying that other methods (such as clearing processes or interfaces) have failed. It is also used during maintenance windows to apply IOS upgrades or to reset a device that has become unresponsive.
The reload command can be aborted using the 'reload cancel' command if issued before the reload timer expires. Understanding the reload command is critical for network engineers because improper use can cause network outages; therefore, it should be used with caution and only when necessary.
reload [in <hh:mm> | at <hh:mm> [month day] | cancel] [text <reason>]When to Use This Command
- Apply a new IOS image after uploading to flash
- Force a scheduled maintenance reload with reload in 60 (60 minutes from now)
- Recover from a software fault without travelling to the site (scheduled reload is a safety net)
- Test that the startup config is correct by reloading to verify the device comes back correctly
Parameters
| Parameter | Syntax | Description |
|---|---|---|
| in | in <hh:mm:ss> | <mm> | Schedules the reload to occur after a specified delay. Time can be specified in hours:minutes:seconds or just minutes. If omitted, the reload occurs immediately after confirmation. Common mistake: forgetting to convert minutes to seconds or using an invalid format. |
| at | at <hh:mm> [month day | day month] | Schedules the reload to occur at a specific time and date. The time is in 24-hour format. If no date is specified, the reload occurs the next time that time occurs. This parameter is useful for maintenance windows. Common mistake: misinterpreting the time zone (the device uses its configured time zone). |
| cancel | cancel | Cancels a previously scheduled reload. This parameter is used alone (e.g., 'reload cancel') and does not require additional arguments. It is useful when a scheduled reload is no longer needed. |
| reason | reason <text> | Provides a text description for the reload, which is logged and can be viewed in system logs. This helps in documenting why the reload was performed. Common mistake: forgetting to enclose multi-word reasons in quotes. |
| force | force | Suppresses the confirmation prompt and forces the reload to proceed immediately (or at the scheduled time). Use with caution as it bypasses the safety check. Common mistake: using force without saving the configuration. |
| fast | fast | Performs a fast reload that skips certain hardware initialization steps, reducing reboot time. Not supported on all platforms. Common mistake: assuming fast reload is available on all IOS versions. |
Command Examples
Schedule a reload in 30 minutes with a safety net
Router# reload in 30 Reload scheduled in 30 minutes by admin on vty0 (192.168.1.100) [confirm] Router# show reload Reload scheduled for 14:53:00 UTC Sat Jun 27 2026 (29 minutes and 45 seconds away) Reloading in 30 minutes. Stop with 'reload cancel'.
Immediate reload
Router# reload Proceed with reload? [confirm] %SYS-5-RELOAD: Reload requested by admin on vty0. Reload Reason: Reload command.
Understanding the Output
Scheduled reload is a critical safety tool: if a config change breaks access, the device reloads back to the last saved config. Always have an unsaved config when using scheduled reload as a safety net — or ensure write memory is done beforehand for intentional changes. reload cancel stops a pending scheduled reload.
Configuration Scenarios
Scheduled reload for IOS upgrade maintenance window
A network engineer needs to upgrade the IOS image on a core router. The upgrade requires a reload to boot the new image. The reload is scheduled during a maintenance window to minimize impact.
Topology
R1 (core router) connected to distribution switchesSteps
- 1.Step 1: Save the running configuration: R1# copy running-config startup-config
- 2.Step 2: Verify the new IOS image is in flash: R1# dir flash:
- 3.Step 3: Set the boot system variable to the new image: R1(config)# boot system flash:c2900-universalk9-mz.SPA.157-3.M3.bin
- 4.Step 4: Exit configuration mode: R1(config)# exit
- 5.Step 5: Schedule the reload for 2:00 AM: R1# reload at 02:00 reason "IOS upgrade maintenance"
- 6.Step 6: Confirm the scheduled reload: R1# show reload
! Save config and set boot variable copy running-config startup-config configure terminal boot system flash:c2900-universalk9-mz.SPA.157-3.M3.bin end reload at 02:00 reason "IOS upgrade maintenance"
Verify: Use 'show reload' to display the scheduled reload time and reason. Expected output: 'Reload scheduled for 02:00:00 UTC Mon Mar 10 2025 (in 4 hours 30 minutes) by console'
Watch out: Forgetting to save the running configuration before reload; the new boot variable will not be saved and the device will boot with the old image.
Immediate reload to recover from a hung device
A switch becomes unresponsive to Telnet/SSH and console commands due to a software hang. The engineer must perform an immediate reload to restore operation.
Topology
SW1 (access switch) connected to end devicesSteps
- 1.Step 1: Attempt to access the device via console (if possible). If console is responsive, proceed.
- 2.Step 2: Save the running configuration (if possible): SW1# copy running-config startup-config
- 3.Step 3: Issue the reload command: SW1# reload
- 4.Step 4: Confirm the reload when prompted: 'Proceed with reload? [confirm]'
- 5.Step 5: Wait for the device to reboot and verify it comes back online.
! Immediate reload (if console accessible) copy running-config startup-config reload Proceed with reload? [confirm]
Verify: After reboot, check the uptime: 'show version' and verify interfaces are up: 'show ip interface brief'. Expected output: uptime less than a few minutes.
Watch out: If the device is completely unresponsive, a power cycle may be necessary. Also, if the running config was not saved, the device will boot with the startup config, potentially losing recent changes.
Troubleshooting with This Command
The reload command is primarily used as a troubleshooting tool when a device is experiencing abnormal behavior such as high CPU, memory leaks, or unresponsive processes. Before resorting to reload, a network engineer should collect diagnostic data (e.g., show processes cpu, show memory statistics, show logging) to identify the root cause. If the device is still responsive, the reload can be scheduled to minimize impact.
When troubleshooting, the 'reload in' parameter is useful to allow time for data collection before the reboot. For example, 'reload in 10' gives 10 minutes to capture output from 'show tech-support' or 'debug' commands. After the reload, the engineer should check the 'show version' output for crash information (e.g., 'System restarted by reload' vs 'System restarted by power-on') and review the 'show logging' output for any error messages preceding the hang.
If the problem recurs, the reload may only provide temporary relief, and further investigation into hardware or software issues is needed. The 'reload cancel' command is essential if the scheduled reload is no longer needed after the issue is resolved. In high-availability environments, reload should be coordinated with redundant peers to avoid traffic loss.
For devices running stateful switchover (SSO), a reload of the active supervisor may trigger a switchover to the standby, which can be less disruptive. Always correlate reload events with network monitoring systems to understand the impact.
CCNA Exam Tips
CCNA exam: reload without write memory reboots from the last saved startup-config — current unsaved changes are discarded
Write memory (or copy running-config startup-config) first to preserve changes
Scheduled reload in 30 is a safety net technique: make config changes, if they work cancel the reload, if they break connection the device reloads to the last good config
Common Mistakes
Running reload without considering unsaved config — changes made this session are lost
Not using reload in during remote maintenance — if you break connectivity you cannot reload manually
Forgetting reload cancel after a scheduled reload is no longer needed
reload vs dir
Although 'reload' and 'dir' are both system-level commands in Privileged EXEC mode, they serve entirely different purposes: reload initiates a device restart, while dir displays filesystem contents. They are rarely confused but are often mentioned together in contexts of system maintenance and troubleshooting.
| Aspect | reload | dir |
|---|---|---|
| Scope | Device restart and configuration reload | Filesystem listing and space inspection |
| Effect on device | Reboots the device, clears RAM, reloads IOS and startup config | Reads filesystem metadata; no state change |
| Persistence | Reloads startup configuration from NVRAM; unsaved changes lost | Does not affect configuration or running state |
| Scheduling | Supports 'reload in' or 'reload at' for delayed reboot | No scheduling capability; immediate output |
| Typical use case | Apply configuration changes, recover from hangs, upgrade IOS | Verify file availability, check free space, list bootable images |
Use reload when you need to restart the device to apply configuration changes, perform an IOS upgrade, or recover from a temporary issue.
Use dir when you need to inspect filesystem contents, verify the presence of a file, or check available storage space.
Platform Notes
On Cisco IOS-XE (e.g., Catalyst 9000 switches), the reload command behaves similarly but may have additional options such as 'reload fast' for faster reboot on supported hardware. The output of 'show reload' may include more detailed information about the reason and scheduled time. On NX-OS (e.g., Nexus switches), the equivalent command is 'reload' as well, but it is executed from the 'configure terminal' mode or from EXEC mode.
NX-OS also supports 'reload ascii' for ASCII configuration reload. On ASA firewalls, the reload command is used to reboot the appliance; it supports 'reload at' and 'reload in' similar to IOS. On IOS-XR (e.g., ASR 9000), the reload command is used but with different syntax: 'reload location all' or 'reload node' for specific line cards.
IOS-XR also requires a 'commit' before reload if configuration changes were made. In general, the reload command is universal across Cisco platforms, but the exact syntax and options vary. Always consult the platform-specific documentation before performing a reload in a production environment.
Related Commands
dir
Lists files in the specified filesystem (flash, NVRAM, USB, bootflash). Shows file names, sizes in bytes, dates, and total/free space available.
show boot
Displays the current boot system configuration including the IOS image file the router will load on next reload, the configuration register setting, and BOOT environment variable.
Practice for the CCNA 200-301
Test your knowledge with practice questions covering all CCNA 200-301 exam domains.
Practice CCNA 200-301 Questions