Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Figure 6-15. Using Reload with Pending Configuration Changes
Scheduled Reload. If no parameters are entered after the reload command,
an immediate reboot is executed. The reload at and reload after command
information is not saved across reboots. If the switch is rebooted before a
scheduled reload command is executed, the command is effectively cancelled.
When entering a reload at or reload after command, a prompt will appear to
confirm the command before it can be processed by the switch. For the reload
at command, if mm/dd/yy are left blank, the current day is assumed.
The scheduled reload feature removes the requirement to physically reboot
the switch at inconvenient times (for example, at 1:00 in the morning). Instead,
a reload at 1:00 mm/dd command can be executed (where mm/dd is the date
the switch is scheduled to reboot).
Note Configuration changes are not saved with reload at or reload after commands.
No prompt to save configuration file changes is displayed. See Table 6-2 on
page 6-19.
Examples of scheduled reload commands:
â– To schedule a reload in 15 minutes:
ProCurve# reload after 15
â– To schedule a reload in 3 hours:
ProCurve# reload after 03:00
â– To schedule a reload for the same time the following day:
ProCurve# reload after 01:00:00
â– To schedule a reload for the same day at 12:05:
ProCurve# reload at 12:05
â– To schedule a reload on some future date:
ProCurve# reload at 12:05 01/01/2008
ProCurve(config)# reload after 04:14:00
Reload scheduled in 4 days, 14 hours, 0 minutes
Figure 6-16. An Example of the reload Command
6-21
To Next Page
Loading...
Need help?
General