Enterasys Networks X-Pedition XSR CLI - Manual (Page 120)

File System Commands
3-114 Configuring the XSR Platform
which is specified in the flash:boot‐config file. Although you cannot configure the secondary EOS
file, if you wish to rename it, use the
boot system command. Be aware that if the boot‐config file
does not exist in the flash: directory, EOS fallback will seach for the default xsr1200.fls ,
xsr1800.fls or xsr3000.fls file first in flash:, then in cflash:, finally over the network (as
specified in the bootrom using the Bootrom monitor mode commands sn or np ).
When you reboot the router using reload , the newly loaded startup-config file is converted to
the running config file. The command initiates a script requiring confirmation of your intention.
Be aware that the reload command does not appear in startup-config .
For more information on how to use this command, refer to the Chapter 2: Managing the XSR in the
XSR User’s Guide.
Syntax
reload [in | at [mmm | hh:mm] | cancel | cold | warm | fallback] primary-file
{cflash: | flash:} duration [config | snmp [ip-address]]
Defaults
• Warm start
• Primary‐OS test: 10 minutes
Mode
Privileged EXEC: XSR#
in Reloads after a specified interval, expressed in minutes or hours:minutes.
at Reloads at a particular time, expressed in hours and minutes.
cancel Cancels a pending reload.
primary-
file The filename, including the device name (flash:xsr1800.fls, for example), and can
include any other designation of up to 31 ASCII characters. For example:
flash:my_new_xsr1800.fls or cflash:8_12_04_xsr1800.fls.
cflash:
flash: Reloads primary OS file from cflash: or flash: directory and tested for an interval
you specify between 5 and 30 minues.
duration Primary OS test period after reload, ranging from 5 to 30 minutes.
config Fallback to secondary OS file if any syntax error is found in startup‐config.
snmp Fallback to secondary OS file if no SNMP message was received during test.
ip-address SNMP manager IP address to be monitored for received messages. If no SNMP
IP address is specified, any received SNMP message indicates SNMP
communications are successful.
cold XSR hardware is re‐initialized with the SDRAM cleared and software rebooted.
The start is slower since hardware diagnostics are performed.
warm XSR hardware is re‐initialized and software rebooted. The start is faster since
hardware diagnostics are not performed during the reboot.
none Lack of argument performs a warm start.