|
|
This chapter provides detailed descriptions of the commands used to modify the rebooting procedures of the router.
For configuration information and examples, refer to the "Rebooting a Router" chapter in the Configuration Fundamentals Configuration Guide.
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. |
For most platforms, if you enter the boot command and press Return, the router boots from ROM by default. However, for some platforms, such as the Cisco 3600 series, if you enter the boot command and press Enter, the router boots the first image in Flash memory. Refer to the documentation for your platform for information about the default image.
If you enter the boot flash command without a filename, the first valid file in Flash memory is loaded.
For other defaults, see the Syntax Description section.
This command first appeared in Cisco IOS Release 10.3.
Use this command only when your router cannot find the boot configuration information needed in nonvolatile random-access memory (NVRAM). To get to the ROM monitor prompt (>), use one of the following methods:
Refer to the your hardware documentation for information on correct jumper settings for your platform.
In the following example, a router is manually booted from ROM (except the Cisco 3600 series):
> boot F3: (ROM Monitor copyrights)
In the following example, a router boots the file routertest from a network server with the IP address 172.16.15.112:
> boot routertest 172.16.15.112 F3: (ROM Monitor copyrights)
The following example shows the boot flash command without the filename argument.The first valid file in Flash memory is loaded.
> boot flash
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
In the following example, the boot flash command is used with the filename gs7-k. That is the file that will be loaded.
> boot flash gs7-k
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
In the following example, the boot flash flash: command boots the relocatable image file igs-bpx-l from partition 2 in Flash memory:
>boot flash flash:2:igs-bpx-lF3: 3562264+98228+303632 at 0x30000B4(ROM Monitor copyrights)
Use the following example if the boot image has been inadvertently erased. (The IOS is directly launched from the ROM monitor without the intermediate boot stage. This startup requires less system memory.)
> boot flash:c4500-j-mz.103-7
In the following example, the Cisco 7000 family accepts the flash keyword for compatibility but ignores it, and boots from slot0:
> boot flash slot0:gs7-k-mz.103-9
F3: 8468+3980384+165008 at 0x1000
In the following example, the new rommon requires new syntax.
rommon 8 > b flash flash:c4500-j-mz.103-12
boot of "flash flash:c4500-j-mz.103-12" using boot helper "bootflash:c4500-xboot.101-1" failed
In the following example, the command did not function because it must be entered in lowercase.
rommon 10 > BOOT
command "BOOT" not found
The following example shows the ROM monitor booting the first file in the first partition of internal Flash memory of a Cisco 3600 series:
> boot flash:
This example boots the first image file in the first partition of the Flash memory card in slot 0 of a Cisco 3600 series:
> boot slot0:
The following example shows the ROM monitor booting the first file in the first Flash memory partition on a Cisco 1600 series:
> boot flash:
You can use the master indexes or search online to find documentation of related commands.
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. |
There is no default Flash device or filename.
Global configuration
This command first appeared in Cisco IOS Release 11.0.
The boot bootldr command sets the BOOTLDR environment variable in the current running configuration. You must specify both the device and the filename.
The no form of the command sets the BOOTLDR environment variable to a null string. On the Cisco 7000 family, a null string causes the first image file in bootflash to be used as the boot image that ROM uses for booting.
In the following example, the internal Flash memory contains the boot image:
boot bootldr bootflash:boot-image
The following example specifies that the Flash memory card inserted in slot 0 contains the boot image:
boot bootldr slot0:boot-image
You can use the master indexes or search online to find documentation of related commands.
copy running-config startup-config
show boot
show flash
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. |
No secondary bootstrap
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The boot bootstrap command causes the router to load a secondary bootstrap image over the network. The secondary bootstrap image then loads the specified system image file. See the appropriate hardware installation guide for details on the configuration register and secondary bootstrap filename.
Use this command when you have attempted to load a system image but have run out of memory even after compressing the system image. Secondary bootstrap allows you to load a larger system image through a smaller secondary image.
In the following example, the system image file sysimage-2 will be loaded by using a secondary bootstrap image:
boot bootstrap sysimage-2
| 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. |
If you configure the router to boot from a network server but do not specify a system image file with the boot system command, the router uses the configuration register settings to determine the default system image filename. The router forms the default boot filename by starting with the word cisco and then appending the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the processor type name (cisconn-cpu). See the appropriate hardware installation guide for details on the configuration register and default filename. See also the config-register or confreg command. See also the "Syntax Description" section preceding this section.
If you omit a keyword (flash, mop, rom, rcp, or tftp) from the boot system command, the system defaults to booting from a system image stored on a TFTP server.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
For this command to work, the config-register command must be set properly.
Enter several boot system commands to provide a fail-safe method for booting your router. The router stores and executes the boot system commands in the order in which you enter them in the configuration file. If you enter multiple boot commands of the same type--for example, if you enter two commands that instruct the router to boot from different network servers--then the router tries them in the order in which they appear in the configuration file. If a boot system command entry in the list specifies an invalid device, the router skips that entry. Use the boot system rom command to specify use of the ROM system image as a backup to other boot commands in the configuration.
For some platforms, the boot image must be loaded before the system image is loaded. However, on many platforms, the boot image is only loaded if the router is booting from a network server or the flash device is not specified. If the device is specified, the router will boot faster because it does not have to load the boot image first.
This section contains the following usage guideline sections:
To remove a single entry from the bootable image list, use the no form of the command with an argument. For example, to remove the entry that specifies a bootable image on a Flash memory card inserted in the second slot, use the no boot system flash slot1:[filename] command. All other entries in the list remain.
To eliminate all entries in the bootable image list, use the no boot system command. At this point, you can redefine the list of bootable images using the previous boot system commands. Remember to save your changes to your startup configuration by issuing the copy running-config startup-config command.
Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file with the no boot system flash filename command. Then add a new line in the configuration file with the boot system flash filename command.
You can boot the router from a compressed image on a network server. When a network server boots software, both the image being booted and the running image must fit into memory. Use compressed images to ensure that enough memory is available to boot the router. You can compress a software image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command. (You can also uncompress data with the UNIX uncompress command.)
The rcp protocol requires that a client send the remote username in an rcp request to a server. When the router executes the boot system rcp command, the Cisco IOS software sends the host name as the both the remote and local usernames by default. For the rcp protocol to execute properly, an account must be defined on the network server for the remote username configured on the router.
If the server has a directory structure, the rcp software searches for the system image to boot from the remote server relative to the directory of the remote username.
By default, the router software sends host name as the remote username. You can override the default remote username by using the ip rcmd remote-username command. For example, if the system image resides in the home directory of a user on the server, you can specify that user's name as the remote username.
During the first 60 seconds of startup, you can force the router to stop booting by pressing the Break key. The router will enter ROM Monitor mode, where you can change the configuration register value or boot the router manually.
For the Cisco 3600 series and Cisco 7000 family, the boot system command modifies the BOOT environment variable in the running configuration. The BOOT environment variable specifies a list of bootable images on various devices.
To view the contents of the BOOT environment variable, use the show boot command.
The following example illustrates a list specifying two possible internetwork locations for a system image, with the ROM software being used as a backup:
boot system cs3-rx.90-1 192.168.7.24 boot system cs3-rx.83-2 192.168.7.19 boot system rom
The following example boots the system boot relocatable image file igs-bpx-l from partition 2 of the Flash device:
boot system flash flash:2:igs-bpx-l
The following example instructs the router to boot from an image located on the Flash memory card inserted in slot 0 of the Cisco 7000 RSP7000 card, Cisco 7200 NPE card, or Cisco 7500 series RSP card:
boot system flash slot0:new-config
This example specifies the file new-ios-image as the system image for a Cisco 3600 series router to load at startup. This file is located in the fourth partition of the Flash memory card in slot 0:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flash slot0:4:dirt/images/new-ios-image
This example boots from the image file c1600-y-l in partition 2 of Flash memory of a Cisco 1600 series:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flash flash:2:c1600-y-l
You can use the master indexes or search online to find documentation of related commands.
config-register
copy
copy flash rcp
copy flash tftp
copy verify flash
copy running-config startup-config
copy tftp flash
ip rcmd remote-username
show boot
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). |
Refer to your platform documentation for the default configuration register value.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
This command applies only platforms which use a software configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines if the router boots manually, from ROM, or from Flash or the network. To change the boot field value and leave all other bits set to their default values, follow these guidelines:
For more information about the configuration register bit settings and default filenames, see the appropriate router hardware installation guide.
In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x210F
You can use the master indexes or search online to find documentation of related commands.
boot system
confreg
o
show version
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. |
Refer to your platform documentation for the default configuration register value.
ROM Monitor
This command first appeared in Cisco IOS Release 10.0.
Not all versions in the ROM Monitor support this command. Refer to your platform documentation for more information on ROM Monitor mode.
If you use this command without specifying the configuration register value, the router prompts for each bit of the configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines if the router boots manually, from ROM, or from Flash or the network. To change the boot field value and leave all other bits set to their default values, follow these guidelines:
For more information about the configuration register bit settings and default filenames, see the appropriate router hardware installation guide.
In the following example, the configuration register is set to boot the system image from Flash memory:
confreg 0x210F
In the following example, no configuration value is entered, so the system prompt for each bit in the register:
rommon 7 > confreg
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400 [0]: 0
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = the boot helper image
2-15 = boot system
[0]: 0
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
You must reset or power cycle for new config to take effect.
rommon 8>
To return to the EXEC mode from ROM monitor mode, use the continue ROM monitor command.
continueThis command has no arguments or keywords.
ROM monitor
This command first appeared in Cisco IOS Release 11.0.
Use this command when you are in ROM monitor mode, and you want to return to EXEC mode to use the system image instead of reloading. On older platforms, the angle bracket (>) indicates that you are in ROM monitor mode. On newer platforms, "rommon number>" is the default ROM monitor prompt. Typically, you are in ROM monitor mode when you manually load a system image or perform diagnostic tests. Otherwise, you will most likely never be in this mode.
 | Caution While in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a reset or the continue command. |
In the following example, the continue command takes you from ROM monitor to EXEC mode:
> continue
Router#
You can use the master indexes or search online to find documentation of related commands.
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.
oThis command has no arguments or keywords.
Refer to the appropriate hardware installation guide for default values.
ROM monitor
This command first appeared in Cisco IOS Release 10.0.
Not all platforms support the o command.
To get to the ROM monitor prompt, use the reload EXEC command if the configuration register has a boot value of 0. (For systems with a software configuration register, a value can be included on the o/r command line.) Use the i command in conjunction with the o/r command to initialize the router. (The i command is documented in the hardware installation and maintenance publication for your product.) The o/r command resets the configuration register to 0x141, which disables the Break key, ignores the NVRAM configuration, and boots the default system image from ROM.
The following is a sample display from the o command:
> o Bit# Configuration register option settings: 15 Diagnostic mode disabled 14 IP broadcasts do not have network numbers 13 Do not boot default ROM software if network boot fails 12-11 Console speed is 9600 baud 10 IP broadcasts with ones 09 Do not use secondary bootstrap 08 Break enabled 07 OEM disabled 06 Ignore configuration disabled 03-00 Boot to ROM monitor >
The following is an example of the o/r and i commands used to reset and boot the default system image from ROM:
>o/r>i
You can use the master indexes or search online to find documentation of related commands.
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. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The reload command halts the system. If the system is set to restart on error, it reboots itself. Use the reload command after configuration information is entered into a file and saved to the startup configuration.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This prevents the system from dropping to the ROM monitor and thereby taking the system out of the remote user's control.
If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you say "yes" in this situation, the system goes to setup mode upon reload.
When you schedule a reload to occur at a later time, it must take place within approximately 24 days.
The at keyword can only be used if the system clock has be set on the router (either through NTP, the hardware calendar, or manually). The time is relative to the configured time zone on the router. To schedule reloads across several routers to occur simultaneously, the time on each router must be synchronized with NTP.
To display information about a scheduled reload, use the show reload command.
The following example illustrates how to use the reload command to immediately reload the software on the router:
Router# reload
The following example illustrates how to use the reload command to reload the software on the router in 10 minutes:
Router# reload in 10
Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)
Proceed with reload? [confirm]
Router#
The following example illustrates how to use the reload command to reload the software on the router at 1:00 p.m. today:
Router# reload at 13:00
Router# Reload scheduled for 13:00:00 PDT Fri Apr 21 1996 (in 1 hour and 2 minutes)
Proceed with reload? [confirm]
Router#
The following example illustrates how to use the reload command to reload the software on the router on April 20 at 2:00 a.m.:
Router# reload at 02:00 apr 20
Router# Reload scheduled for 02:00:00 PDT Sat Apr 20 1996 (in 38 hours and 9 minutes)
Proceed with reload? [confirm]
Router#
The following example illustrates how to use the reload command to cancel a pending reload:
Router# reload cancel
%Reload cancelled.
You can use the master indexes or search online to find documentation of related commands.
copy running-config startup-config
show 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 bootThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
Use this command with the Cisco 7000 family. The show boot command allows you to view the current settings for the following environment variables:
The BOOT environment variable specifies a list of bootable images on various devices. The CONFIG_FILE environment variable specifies the configuration file used during system initialization. The BOOTLDR environment variable specifies the Flash device and filename containing the rxboot image that ROM uses for booting. You set these environment variables with the boot system, boot config, and boot bootldr commands, respectively.
When you use this command on a Cisco 7507 or Cisco 7513 configured for High System Availability (HSA), this command also shows you the environment variable settings for both the master and slave RSP card.
HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
The following is sample output from the show boot command:
Cyclone# show boot
BOOT variable =
CONFIG_FILE variable = nvram:
Current CONFIG_FILE variable = slot0:router-config
BOOTLDR variable not exist
Configuration register is 0x0
Cyclone#
In the sample output, the BOOT environment variable contains a null string. That is, a list of bootable images is not specified.
The CONFIG_FILE environment variable points to the configuration file in NVRAM as the startup (initialization) configuration. The run-time value for the CONFIG_FILE environment variable points to the router-config file on the Flash memory card inserted in the first slot of the RSP card. That is, during the run-time configuration, you have modified the CONFIG_FILE environment variable using the boot config command, but you have not saved the run-time configuration to the startup configuration. To save your run-time configuration to the startup configuration, use the copy running-config startup-config command. If you do not save the run-time configuration to the startup configuration, then the system reverts back to the saved CONFIG_FILE environment variable setting for initialization information upon reload. In this sample, the system reverts back to NVRAM for the startup configuration file.
The BOOTLDR environment variable does not yet exist. That is, you have not created the BOOTLDR environment variable using the boot bootldr command.
The following example is output from the show boot command for a Cisco 7513 configured for HSA:
Router# show boot
BOOT variable =
CONFIG_FILE variable =
Current CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
current slave is in slot 7
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
Router#
You can use the master indexes or search online to find documentation of related commands.
boot bootstrap
boot config
boot system
show version
To display the reload status on the router, use the show reload EXEC command.
show reloadThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
You can use the show reload command to display a pending software reload. To cancel the reload, use the reload cancel privileged EXEC command.
The following sample output from the show reload command shows that a reload is schedule for 12:00 a.m. (midnight) on Saturday, April 20:
Router#show reloadReload scheduled for 00:00:00 PDT Sat April 20 1996 (in 12 hours and 12 minutes)Router#
You can use the master indexes or search online to find documentation of related commands.
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 versionThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
You can also use this command with a Cisco 7507 or Cisco 7513 configured with High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
When used with HSA, this command also displays the currently running slave RSP card and the Cisco IOS release that it is running.
The following is sample output from the show version command:
Router> show version
GS Software (GS7), Version 10.0
Copyright (c) 1986-1993 by cisco Systems, Inc.
Compiled Mon 11-Jan-93 14:44
System Bootstrap, Version 4.6(1)
Current date and time is Fri 2-26-1993 2:18:52
Boot date and time is Fri 1-29-1993 11:42:38
Router uptime is 3 weeks, 6 days, 14 hours, 36 minutes
System restarted by power-on
Running default software
Network configuration file is "Router", booted via tftp from 172.16.2.333
RP1 (68040) processor with 16384K bytes of memory.
X.25 software.
Bridging software.
1 CIP controller (3 IBM Channels).
1 CIP2 controller (3 IBM Channels).
1 Switch Processor.
1 TRIP controller (4 Token Ring).
4 Token Ring/IEEE 802.5 interface.
1 AIP controller (1(ATM)
1 ATM network interface
4096K bytes of flash memory on embedded flash (in RP1).
Configuration register is 0x0
Table 19 describes significant fields shown in these displays.
| Field | Description |
|---|---|
| GS Software (GS7), Version 10.0 | Always specify the complete version number when reporting a possible software problem. In the example output, the version number is 10.0. |
| System Bootstrap, Version | Bootstrap version string. |
| Current date and time
Boot date and time Router uptime is | Current date and time, the date and time the system was last booted, and uptime, or the amount of time the system has been up and running. |
| System restarted by power-on | Also displayed is a log of how the system was last booted, both as a result of normal system startup and of system error. For example, information can be displayed to indicate a bus error that is generally the result of an attempt to access a nonexistent address, as follows:
System restarted by bus error at PC 0xC4CA, address 0x210C0C0 |
| Running default software | If the software was booted over the network, the Internet address of the boot host is shown. If the software was loaded from onboard ROM, this line reads "running default software." In addition, the names and sources of the host and network configuration files are shown. |
| RP1.... | The remaining output in each display shows the hardware configuration and any nonstandard software options. The configuration register contents are displayed in hexadecimal notation. |
The output of the show version EXEC command can also provide certain messages, such as bus error messages. If such error messages appear, report the complete text of this message to your technical support specialist.
The following is sample output from the show version command on a Cisco 7500 series router with an RSP2 and three VIP2s with a variety of interfaces.
Router# show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-JV-M), Experimental Version 11.1(12816)
[getchell 108]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 03-Jun-96 11:39 by getchell
Image text-base: 0x600108A0, data-base: 0x60910000
ROM: System Bootstrap, Version 5.3(16645) [szhang 571], INTERIM SOFTWARE
Router uptime is 4 minutes
System restarted by reload
System image file is "slot0:dirt/vip2/master/rsp-jv-mz.960603", booted via tftp from 172.18.2.3
cisco RSP2 (R4600) processor with 24576K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0
Last reset from power-on
G.703/E1 software, Version 1.0.
SuperLAT software copyright 1990 by Meridian Technology Corp).
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc).
Primary Rate ISDN software, Version 1.0.
Chassis Interface.
1 CIP controller (3 IBM Channels).
1 CIP2 controller (3 IBM Channels).
1 EIP controller (6 Ethernet).
1 HIP controller (1 HSSI).
1 FSIP controller (8 Serial).
1 AIP controller (1 ATM).
1 TRIP controller (4 Token Ring).
1 FIP controller (1 FDDI).
1 MIP controller (2 T1).
3 VIP2 controllers (1 FastEthernet)(13 Ethernet)(4 Serial)(4 Token Ring)(1
Fddi).
1 FEIP controller (1 FastEthernet).
19 Ethernet/IEEE 802.3 interfaces.
2 FastEthernet/IEEE 802.3 interfaces.
8 Token Ring/IEEE 802.5 interfaces.
12 Serial network interfaces.
1 HSSI network interface.
2 FDDI network interfaces.
1 ATM network interface.
2 Channelized T1/PRI ports.
125K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
No slave installed in slot 7.
Configuration register is 0x0
Table 20 describes the fields in this display for Cisco 7500 series routers with an RSP2 route switch processor.
| Field | Description |
|---|---|
| IOS (tm) GS Software, Version 11.1 | Always specify the complete version number when reporting a possible software problem. In the example output, the version number is 11.1. |
| ROM: System Bootstrap, Version 5.3(16645) [szhang 571], INTERIM SOFTWARE | Bootstrap version string. |
| Router uptime is...
System restarted by... System image file is... | The amount of time the system has been up and running, how the system was restarted, and the name of the system image file. |
| System last reset by | Also displayed is a log of how the system was last booted, both as a result of normal system startup and of system error. For example, information can be displayed to indicate a bus error that is generally the result of an attempt to access a nonexistent address, as follows:
System restarted by bus error at PC 0xC4CA, address 0x210C0C0 |
| cisco RSP2 (R4600) processor... | The remaining output in each display shows the software currently running, hardware configuration, and any nonstandard software options. The configuration register contents are displayed in hexadecimal notation. |
The following is sample output of the show version command from a Cisco 7513. In this example, the current slave is processor slot 7.
Router# show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-P-M), Experimental Version 11.1(5479) [dbath 119]
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Wed 08-Nov-95 17:51 by dbath
Image text-base: 0x600088A0, data-base: 0x603B6000
ROM: System Bootstrap, Version 5.3(18168) [mansonw 63], INTERIM SOFTWARE
Router uptime is 4 days, 31 minutes
System restarted by reload
System image file is "slot0:dirt/dbath/rsp-p-mz-ark-1", booted via tftp from 172.31.7.19
cisco RSP2 (R4600) processor with 16384K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0
Last reset from power-on
G.703/E1 software, Version 1.0.
Primary Rate ISDN software, Version 1.0.
Chassis Interface.
1 CIP controller (3 IBM Channels).
1 CIP2 controller (3 IBM Channels).
1 EIP controller (6 Ethernet).
1 FSIP controller (8 Serial).
1 AIP controller (1 ATM).
1 TRIP controller (4 Token Ring).
1 FIP controller (1 FDDI).
1 MIP controller (2 T1).
6 Ethernet/IEEE 802.3 interfaces.
4 Token Ring/IEEE 802.5 interfaces.
8 Serial network interfaces.
1 FDDI network interface.
1 ATM network interface.
2 Channelized T1/PRI ports.
125K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Slave in slot 7 is running Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-DW-M), Experimental Version 11.1(5479) [dbath 118]
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Wed 08-Nov-95 16:57 by dbath
Configuration register is 0x0
You can use the master indexes or search online to find documentation of related commands.
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 configThis command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use this command for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
In automatic synchronization mode, when you issue a copy EXEC command that specifies the master's startup configuration (startup-config) as the target, the master also copies the same file to the slave's startup configuration (slave-startup-config). Use this command when implementing HSA for simple hardware backup or for software error protection to ensure that the master and slave RSP contain the same configuration files.
The following example turns on automatic configuration file synchronization. When the copy running-config startup-config command is issued, the running configuration is saved to the startup configurations of both the master RSP and the slave RSP.
Router(config)# slave auto-sync config Router(config)# end Router# copy running-config startup-config
You can use the master indexes or search online to find documentation of related commands.
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. |
The default slave is the RSP card located in the higher number processor slot. On the Cisco 7507, processor slot 3 contains the default slave RSP. On the Cisco 7513, processor slot 7 contains the default slave RSP.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use this command for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
The router uses the default slave information when booting:
The following example sets the default slave RSP to processor slot 2 on a Cisco 7507:
slave default-slot 2
You can use the master indexes or search online to find documentation of related commands.
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. |
The default is to load the image from the system bundle.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use this command for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
Use the slave image command to override the slave image that is bundled with the master image.
When using HSA for simple hardware backup, ensure that the slave image is in the same location on the master and the slave RSP card. Thus, if the slave RSP card becomes the master, it will be able to find the slave image and download it to the new slave.
The following example specifies that the slave RSP run the rsp-dw-mz.ucode.111-3.2 image from slot 0.
slave image flash slot0:rsp-dw-mz.ucode.111-3.2
You can use the master indexes or search online to find documentation of related commands.
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 reloadThis command has no arguments or keywords.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use this command for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
After using the slave image global configuration command to specify the image that the slave RSP runs on a Cisco 7507 or Cisco 7513, use the slave reload command to reload the slave with the new image. The slave reload command can also be used to force the slave to reboot its existing image.
The following example reloads an inactive slave RSP card. If the slave successfully reloads, it will return to an active slave state. If the master RSP fails, the slave RSP will become the master.
slave reload
You can use the master indexes or search online to find documentation of related commands.
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 configThis command has no arguments or keywords.
Automatic synchronization is turned on.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.1.
Use this command for a Cisco 7507 or Cisco 7513 that is configured for High System Availability (HSA). HSA refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
This command allows you to synchronize the configuration files of the master and slave RSP cards on a case-by-case basis when you do not have automatic synchronization turned on. This command copies the master's configuration file to the slave RSP card.
The following example synchronizes the configuration files on the master and slave RSP card:
slave sync config
You can use the master indexes or search online to find documentation of related commands.
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 terminalThis command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
The slave console does not have enable password protection. Thus, an individual connected to the slave console port can enter privileged EXEC mode and view or erase the configuration of the router. Use the no slave terminal command to disable slave console access and prevent security problems. When the slave console is disabled, users cannot enter commands.
If slave console access is disabled, the following message appears periodically on the slave console:
%%Slave terminal access is disabled. Use "slave terminal" command in master RSP configuration mode to enable it.
The following example disables console access to the slave RSP:
no slave terminal
|
|