cc/td/doc/product/software/ios120/12supdoc/12cmdsum
hometocprevnextglossaryfeedbacksearchhelp

Table of Contents

Booting Commands

Booting Commands

This chapter describes the function and displays the syntax for booting commands. For more information about defaults and usage guidelines, see the corresponding chapter of the Configuration Fundamentals Command Reference.

boot

To boot the router manually, use the boot ROM monitor command. The syntax of this command varies according to the platform and ROM Monitor version. Refer to the documentation for your platform to determine which command to use.

boot
boot
file-url
boot
filename [ip-address]
boot flash [filename]
boot flash [partition-number:][filename]

boot
flash-fs:[filename] (Cisco 7000  family)
boot [flash-fs:][partition-number:][filename] (Cisco  1600 and Cisco 3600  series)

file-url

URL of the image to boot. This option is only available with later ROM Monitor releases.

filename

When used in conjunction with the ip-address argument, the filename argument is the name of the system image file to boot from a network server. The filename is case sensitive.

When used in conjunction with the flash keyword, the filename argument is the name of the system image file to boot from Flash memory.

On all platforms except the Cisco  1600 series, Cisco  3600 series, and Cisco  7000 family, the system obtains the image file from internal Flash memory.

On the Cisco  1600 series, Cisco  3600 series and Cisco  7000 family, the flash-fs: argument specifies the Flash memory device from which to obtain the system image. See the flash-fs: argument later in this table for valid device values. The filename is case sensitive. Without filename, the first valid file in Flash memory is loaded.

ip-address

(Optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.

flash

(Optional) Boots the router from Flash memory.

flash-fs:

Only newer ROM monitors support the flash-fs:filename format. Specifying the Flash file system is optional for all platforms except the Cisco 7500 series. Possible file systems are:

· flash:---Internal Flash memory on the Cisco  1600 series and Cisco  3600 series. This is the only valid Flash file system for the Cisco  1600 series.

· bootflash:---Internal Flash memory on the Cisco  7000 family.

· slot0:---Flash memory card in first PCMCIA slot on the Cisco  7000 family and Cisco  3600 series.

· slot1:---Flash memory card in second PCMCIA slot on the Cisco 7000 family and Cisco  3600 series.

partition-number:

(Optional) Boots the router from Flash memory with the optional filename of the image you want loaded from the specified Flash partition. If you do not specify a filename, the first valid file in the specified partition of Flash memory is loaded. This option is relevant to platforms such as the Cisco  2500 where Flash memory may be partitioned.


boot bootldr

To specify the location of the boot image that ROM uses for booting, use the boot  bootldr global configuration command. Use the no form of this command to remove this boot image specification.

boot bootldr file-url
no boot bootldr

file-url

URL of the boot image on a Flash file system.


boot bootstrap

To configure the filename that is used to boot a secondary bootstrap image, use the boot bootstrap global configuration command. Use the no form of this command to disable booting from a secondary bootstrap image.

boot bootstrap file-url
no boot bootstrap file-url

boot bootstrap flash
[filename]
no boot bootstrap flash [filename]

boot bootstrap [tftp] filename [ip-address]
no boot bootstrap [tftp] filename [ip-address]

file-url

URL of the bootstrap image.

flash

Boots the router from Flash memory.

filename

(Optional with flash) Name of the system image to boot from a network server or from Flash memory. If you omit the filename when booting from Flash memory, the router uses the first system image stored in Flash memory.

tftp

(Optional) Boots the router from a system image stored on a TFTP server.

ip-address

(Optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.


boot system

To specify the system image that the router loads at startup, use one of the following boot  system global configuration commands. Use a no form of this command to remove the startup system image specification.

boot system file-url
no boot system file-url

boot system flash
[flash-fs:][partition-number:][filename]
no boot system flash [flash-fs:][partition-number:][filename]

boot system rom
no boot system rom

boot system
{rcp | tftp | ftp} filename [ip-address]
no boot system {rcp | tftp | ftp} filename [ip-address]

no boot system

file-url

URL of the system image to load at system startup.

flash

On all platforms except the Cisco  1600 series, Cisco  3600 series, and Cisco  7000 family, this keyword boots the router from internal Flash memory. If you omit all arguments that follow this keyword, the system searches internal Flash for the first bootable image.

On the Cisco  1600 series, Cisco  3600 series, and Cisco 7000 family, this keyword boots the router from a Flash device, as specified by the device: argument. On the Cisco  1600 series and Cisco  3600 series, if you omit all optional arguments, the router searches internal Flash memory for the first bootable image. On the Cisco  7000 family, when you omit all arguments that follow this keyword, the system searches the PCMCIA slot 0 for the first bootable image.

flash-fs:

(Optional) Flash file system containing the system image to load at startup. The colon (:) is required. Valid file systems are as follows:

· flash:---Internal Flash memory on the Cisco  1600 series and Cisco  3600 series. For the Cisco  1600 series and Cisco  3600 series, this file system is the default if you do not specify a file system. This is the only valid file system for the Cisco  1600 series,

· bootflash---Internal Flash memory in the Cisco 7000 family.

· slot0---First PCMCIA slot on the Cisco  3600 series and Cisco 7000 family. For the Cisco 7000 family, this file system is the default if you do not specify a file system.

· slot1---Flash memory card in the second PCMCIA slot on the Cisco  3600 series and Cisco 7000 family.

partition-number:

(Optional) Number of the Flash memory partition that contains the system image to boot, specified by the optional filename argument. If you do not specify a filename, the router loads the first valid file in the specified partition of Flash memory. This argument is only valid on routers which can be partitioned.

filename

(Optional when used with boot system flash) Name of the system image to load at startup. It is case sensitive. If you do not specify a filename, the router loads the first valid file in the specified Flash file system, the specified partition of Flash memory, or the default Flash file system if you also omit the flash-fs: argument.

rom

Boots the router from ROM. Do not use this keyword with the Cisco  3600 series or the Cisco 7000 family.

rcp

Boots the router from a system image stored on a network server using rcp.

tftp

Boots the router from a system image stored on a TFTP server.

ftp

Boots the router from a system image stored on an FTP server.

ip-address

(Optional) IP address of the server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.


config-register

To change the configuration register settings, use the config-register global configuration command.

config-register value

value

Hexadecimal or decimal value that represents the 16-bit configuration register value that you want to use the next time the router is restarted. The value range is from 0x0 to 0xFFFF (0 to 65535 in decimal).


confreg

To change the configuration register settings while in ROM Monitor mode, use the confreg ROM Monitor command.

confreg [value]

value

(Optional) Hexadecimal value that represents the 16-bit configuration register value that you want to use the next time the router is restarted. The value range is from 0x0 to 0xFFFF.


continue

To return to the EXEC mode from ROM monitor mode, use the continue ROM monitor command.

continue

o

To list the value of the boot field (bits 0-3) in the configuration register, use the ROM monitor o command. To reset the value of the boot field so that the router boots from ROM, use the ROM monitor o/r command.

o
o/r

reload

To reload the operating system, use the reload EXEC command.

reload [text | in [hh:]mm [text] | at hh:mm [month day | day month] [text] | cancel]

text

(Optional) Reason for the reload, 1 to 255 characters long.

in [hh:]mm

(Optional) Schedule a reload of the software to take effect in the specified minutes or hours and minutes. The reload must take place within approximately 24 days.

at hh:mm

(Optional) Schedule a reload of the software to take place at the specified time (using a 24-hour clock). If you specify the month and day, the reload is scheduled to take place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time), or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The reload must take place within approximately 24 days.

month

(Optional) Name of the month, any number of characters in a unique string.

day

(Optional) Number of the day in the range 1 to 31.

cancel

(Optional) Cancel a scheduled reload.


show boot

The show bootvar command replaces the show boot command. See the show bootvar command in this chapter for more information.

show bootvar

To display the contents of the BOOT environment variable, the name of the configuration file pointed to by the CONFIG_FILE environment variable, the contents of the BOOTLDR environment variable, and the configuration register setting, use the show bootvar EXEC command.

show bootvar

show reload

To display the reload status on the router, use the show reload EXEC command.

show reload

show version

To display the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images, use the show version EXEC command.

show version

slave auto-sync config

To turn on automatic synchronization of configuration files for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA), use the slave auto-sync config global configuration command. To turn off automatic synchronization, use the no form of the command.

slave auto-sync config
no slave auto-sync config

slave default-slot

To specify the default slave RSP card on a Cisco 7507 or Cisco 7513, use the slave default-slot global configuration command.

slave default-slot processor-slot-number

processor-slot-number

Number of processor slot that contains the default slave RSP. On the Cisco 7507, valid values are 2 or 3. On the Cisco 7513, valid values are 6 or 7. The default is the higher number processor slot.


slave image

To specify the image that the slave RSP runs on a Cisco 7507 or Cisco 7513, use the slave image global configuration command.

slave image {system | file-url}

system

Loads the slave image that is bundled with the master system image. This is the default.

file-url

Loads the slave image from the specified file in a Flash file system. If you do not specify a filename, the first file on the specified Flash file system is the default file.


slave reload

To force a reload of the image that the slave RSP card is running on a Cisco 7507 or Cisco 7513, use the slave reload global configuration command.

slave reload

slave sync config

To manually synchronize configuration files on the master and slave RSP cards of a Cisco 7507 or Cisco 7513, use the slave sync config privileged EXEC command.

slave sync config

slave terminal

To enable access to the slave RSP console, use the slave terminal global configuration command. The no form of this command disables access to the slave RSP console.

slave terminal
no slave terminal


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Feb 8 14:09:44 PST 1999
Copyright 1989-1999©Cisco Systems Inc.