Foundry Networks Switch and Router, Руководство по установке и настройке

Страница: 206 / 1070

Foundry Switch and Router Installation and Configuration Guide
7 - 10 December 2000
Saving or Erasing Image and Configuration Files
You can save modified configuration files to the permanent startup configuration file or erase software images or
configuration files.
USING THE CLI
• erase flash primary erases the image stored in primary flash of the system.
• erase flash secondary erases the image stored in secondary flash of the system.
• erase startup-config erases the configuration stored in the startup configuration file; however, the running
configuration remains intact until system reboot.
• write memory saves the running configuration file into the startup configuration file.
NOTE: All of these commands are at the privileged level of the CLI. See the Foundry Switch and Router
Command Line Interface Reference .
USING THE WEB MANAGEMENT INTERFACE
You cannot delete image or configuration files using the Web management interface.
Scheduling a System Reload
In addition to reloading the system manually, you can configure the Foundry device to reload itself at a specific
time or after a specific amount of time has passed.
NOTE: The scheduled reload feature requires the system clock. You can use a Simple Network Time Protocol
(SNTP) server to set the clock or you can set the device clock manually. See “Specifying a Simple Network Time
Protocol (SNTP) Server” on page 10-10 or “Setting the System Clock” on page 10-12.
Reloading at a Specific Time
To schedule a system reload for a specific time, use one of the following methods.
USING THE CLI
To schedule a system reload from the primary flash module for 6:00:00 AM, January 19, 1999, enter the following
command at the global CONFIG level of the CLI:
BigIron# reload at 06:00:00 01-19-99
Syntax: reload at <hh:mm:ss> <mm-dd-yy> [primary | secondary]
<hh:mm:ss> is the hours, minutes, and seconds.
<mm-dd-yy> is the month, day, and year.
primary | secondary specifies whether the reload is to occur from the primary code flash module or the
secondary code flash module. The default is primary .
USING THE WEB MANAGEMENT INTERFACE
You cannot schedule a system reload using the Web management interface.
Reloading after a Specific Amount of Time
To schedule a system reload to occur after a specific amount of time has passed on the system clock, use one of
the following methods.
USING THE CLI
To schedule a system reload from the secondary flash one day and 12 hours later, enter the following command at
the global CONFIG level of the CLI: