| |
|
|
boot
Specifies the image or configuration file used when the system starts.
Syntax: boot [1 | 2]
boot {filename | package-file}
boot {filename | package-file} [1 | 2]
boot flags value
boot config filename
boot {filename | package-file}[1 | 2] [config filename]
filename
Name of a file on the local file system to be burned into flash memory.
package-file
Name of a package file containing the operational image for routing modules.
1 | 2
Specifies the space in flash memory to read or write.
value
32-bit hex value that specifies the boot flags to be used when the system is restarted. Each bit of the hexadecimal number controls different aspects of the boot process. Boot flag values are additive. The upper (left-most) four digits of the boot flag are specific to each of the three platforms (server, modules, and bay controller). The lower four digits of the flags are used by all platforms. The following boot flags are supported:
Same on all platforms:
0x00000008 - Fast boot (2 second countdown instead of 10 second countdown).
Server-specific:
Use these flags together to circumvent a forgotten password:0x00010000 - Disable the IPriori CLI password.
0x00020000 - IPriori boots without parsing the configuration file.
Module specific:
0x00080000 - Display all log messages generated by the modules on the console.
Bay specific:
0x20000000 - Display all log messages generated by the bay on the console.config filename
The config keyword specifies that the file specified by filename replaces the current startup script (default is startup.cfg) with the contents of filename at boot time. On reboot the startup-config is the last file set using the boot config command. The filename argument specifies the file used.
Description: Flash memory contains two operational images, identified by 1 or 2. The boot command specifies an image to burn into one of the spaces in flash memory. Optionally, boot enables you to overwrite the existing configuration file. The image and configuration file are loaded when the reload command is used to start the system.
Use the boot [1 | 2] syntax to change the default operational image in flash memory.
Use the boot filename syntax to replace the contents of flash memory with the specified file. The file is written to either an empty space in flash memory, or, if both spaces are filled, overwrites of the oldest of the two images in flash memory.
Use the boot filename [1 | 2] syntax to burn the specified file into the specified space in flash memory.
Package files are a convenient method of packaging compatible operational, FPGA, POST, and boot ROM images for routing modules.
Use the boot package-file [1 | 2] syntax to replace the contents of flash memory with the specified file. The file is written to either an empty space in flash memory, or, if both spaces are filled, overwrites of the oldest of the two images in flash memory.
NOTE Package files contain the operational, POST, FPGA, and boot ROM images for routing modules. The boot command downloads only the operational image from the specified package file to the module.
Use the boot filename [1 | 2] syntax to burn the specified file into the specified space in flash memory.
Use the boot flags value syntax to set the boot flags to be used when the system is restarted. To add new boot flags to the existing boot flag, perform a logical "OR" on the existing boot flag and the new setting.
Use the boot config filename syntax to configure startup-config to use the file specified by filename to be used at boot up instead of the startup.cfg file.
NOTE The show running-config command will not display this change. Use the show boot command to display the file that will be used at bootup.
Use the boot filename [1 | 2] [config filename] syntax to burn the specified operational image into the specified space in flash memory and replace startup.cfg with the specified configuration file.
Use the boot package-file [1 | 2] [config filename] syntax to burn the specified operational image contained in the specified package file into the specified space in flash memory and replace startup.cfg with the specified configuration file.
Use the reload command to start the system using the new image and configuration files.
Factory Default: None.
Command Mode: Configuration.
Example 1: In the following example, the boot filename 1 command burns the image file newimage.cmp into the first space in flash memory. The contents of the configuration file startup.cfg are unchanged:
router(config)#boot newimage.cmp 1
Example 2: In the following example, the boot package-file 1 command burns the operational image contained in the specified package file into the first space in flash memory. The contents of the configuration file startup.cfg are unchanged:
router(config)#boot R0401450.PKG 1
Example 3: In the following example, the boot config command:
- Replaces startup.cfg with the test.cfg as the boot file.
router(config)#boot config test.cfg
Example 4: In the following example, the boot command:
- Overwrites the first space in flash memory with the contents of a file named newimage.raw
- Replaces the configuration file startup.cfg with the testbed.cfg file
router(config)#boot newimage.raw 1 config testbed.cfg
Related Commands: dir
package-file
reload
show boot
show flash
upgrade all
| |
|
|
Copyright © 2005
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: ConfigFileMgrCmd.fm
HTML File Name: ConfigFileMgrCmd2.html
Last Updated: 02/25/05 at 14:26:17