|
|
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.
To boot the router manually from the prompt, use the boot ROM monitor command.
This manual reload is only used for troubleshooting purposes, and the options directly depend upon hardware possibilities.
The rom monitor prompt is either ">" or for newer platforms "rommon x>". Enter only lowercase commands.
These commands work only if there is a valid image to boot. Also, from the ROM monitor prompt, issuing a prior reset command is necessary for the boot to be always successful.
boot| 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 device: argument specifies the Flash memory device from which to obtain the system image. See the device: 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. |
| device: | Only newer ROM monitors support the device:filename format. Specifying the device is optional for all platforms except the Cisco 7000 family. Possible devices are:
· flash:--Internal Flash memory on the Cisco 1600 series and Cisco 3600 series. This is the only valid device 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 2500 where the flash may be partitioned. |
To specify a Flash device and filename containing the boot image that ROM uses for booting, use the boot bootldr global configuration command. Use the no form of the command to remove this boot image specification.
boot bootldr device: filename| device: | Device containing the boot image that ROM uses. The colon (:) is required. Valid values are as follows:
· bootflash--Internal Flash memory. · slot0--First PCMCIA slot. · slot1--Second PCMCIA slot. |
| filename | Name of the boot image file. The maximum filename length is 63 characters. |
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 flash [filename]| 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. |
| mop | Boots the router from a system image stored on a DEC MOP server. |
| mac-address | (Optional) MAC address of the MOP server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first MOP server to indicate that it has the file is the server from which the router gets the boot image. |
| interface | (Optional) Interface out which the router should send MOP requests to reach the MOP server. The interface options are async, dialer, Ethernet, loopback, null, serial, and tunnel. If the interface argument is not specified, a request is sent on all interfaces that have MOP enabled. The interface from which the first response is received is the interface used to load the software. |
| 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. |
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 flash [device:][partition-number:][filename] (Cisco 1600 series and Cisco 3600 series)| 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. |
| device: | (Optional) Device containing the system image to load at startup. The colon (:) is required. Valid devices 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 device is the default if you do not specify a device. This is the only valid device 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 device is the default if you do not specify a device. · 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 device, the specified partition of Flash memory, or the default Flash device if you also omit the device: argument. |
| mop | Boots the router from a system image stored on a Digital MOP server. Do not use this keyword with the Cisco 3600 series or Cisco 7000 family. |
| mac-address | (Optional) Media Access Control (MAC) address of the MOP server containing the specified system image file. If you do not include the MAC address argument, the router sends a broadcast message to all MOP boot servers. The first MOP server to indicate that it has the specified file is the server from which the router gets the boot image. |
| interface | (Optional) Interface the router uses to send out MOP requests to the MOP server. The interface options are async, dialer, ethernet, serial, and tunnel. If you do not specify the interface argument, the router sends a request out on all interfaces that have MOP enabled. The interface that receives the first response is the interface the router uses to load the software. |
| rom | Boots the router from ROM. Do not use this keyword with the Cisco 3600 series or Cisco 7000 family. |
| rcp | (Optional) Boots the router from a system image stored on a network server using rcp. If you omit this keyword, the transport mechanism defaults to tftp. |
| tftp | (Optional) Boots the router from a system image stored on a TFTP server. This is the default when you do not specify any keyword (flash, mop, rom, tftp, or rcp). |
| ip-address | (Optional) IP address of the TFTP server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
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). |
To change the configuration register settings while in ROM Monitor mode, use the config-register 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. |
To return to the EXEC mode from ROM monitor mode, use the continue ROM monitor command.
continueTo 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.
oTo 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. |
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 boot EXEC command.
show bootTo display the reload status on the router, use the show reload EXEC command.
show reloadTo 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 versionTo 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 configTo 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. |
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 | flash file-id}| system | (Optional) Loads the slave image that is bundled with the master system image. This is the default. |
| flash | (Optional) Loads the slave image from the Flash device specified by the file-id argument. |
| file-id | Specifies a device:filename of the slave image file to download. The colon (:) is required. Valid devices are as follows:
· bootflash--Internal Flash memory in the Cisco 7500 series. · slot0--PCMCIA slot on the Cisco 7000 series RP card or the first PCMCIA slot on the Cisco 7500 series RSP card. · slot1--Second PCMCIA slot on the Cisco 7500 series RSP card. The filename argument is the name of a file on the specified Flash device. The file can be of any type. The maximum filename length is 63 characters. The first file on the specified device is the default file. |
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 reloadTo 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
|
|