Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
RSM IOS
- Thread starter ciscokano
- Start date
- If rxboot is a scaled down version of IOS then maybe you
need to go to the priviledge exec mode(enable) Router(boot)#
and this may have a copy command you are looking for.
BOOT PROCESS
1. ROM monitor process—The ROM monitor looks for the rxboot image in the BOOTLDR variable in NVRAM (set using the boot bootldr device:filename command). If the ROM monitor finds the rxboot image, the ROM monitor loads that image and then proceeds to the Rxboot images process.
2. If the ROM monitor does not find the rxboot image, it looks for the BOOT variable (set using the boot system flash device:filename commands), which is a list of image names. If the ROM monitor finds and successfully loads one of these images, the boot process is complete.
3. If the ROM monitor does not find any of the images specified by the BOOT variable, it loads the first image on the Flash PC card in slot 0. If it does not find an image on the Flash PC card in slot 0, it loads the first image in boot Flash. If it does not find an image in boot Flash, it goes to the ROM monitor prompt.
4. Rxboot image process—The rxboot image runs and parses the configuration file looking for boot system commands. The boot system [rcp | tftp] filename [ip-address] commands specify which image to boot when netbooting. The boot system flash device:filename commands specify what to boot when booting from Flash. The commands are attempted in the order that they appear in the configuration file. If any command succeeds, the boot process is complete. If none of the commands succeed, the system remains at the rxboot image.
IMAGE DESCRIPTIONS
ROM Monitor—This image gains control at reset, power up, or after a nonrecoverable event (such as a bus error). It contains the user interface of the current Cisco ROM monitor, disassembler, memory display, and so on. It has console drivers and trap handlers for parity and bus errors. It does not have any network interface code. The ROM monitor is able to read the flash devices. This image is run from ROM.
Rxboot Image (Boot Image)—This limited function system image has network interface code and end-host protocol code. This image is used as a backup in case the RSM goes down while programming Flash for the main Cisco IOS image. This image is run from RAM.
System image—This is the main Cisco IOS image.
RECOVER FROM RXBOOT LOAD ONLY
Step 1 Verify that the new Cisco IOS software image has been stored properly. Use the show flash command to make sure that the file has been saved, that the size is correct, and that you do not have an invalid checksum message.
Command: show flash
alt-commands: pwd (primary working directory)
(bootflash:,slot0:,slot1
alt-commands: dir (shows you the files on a
particular device.)
If the file does not appear, or if it appears followed by "[invalid checksum]", or if the size does not correspond to the file size on the TFTP server, you must start the installation again. Be aware that the size is listed in bytes in the router and is sometimes listed in kilobytes in TFTP servers.
Step 2 Verify that the boot system commands are in the right order in the configuration. The router stores and executes the boot system commands in the order in which you enter them in the configuration file. If a boot system command entry in the list specifies an invalid device or filename, the router skips that entry.
command: boot system
Step 3 Verify that the config register value is correct. The last digit should be a 2. You can check this with the show version command. If the value is not correct, you must restore a valid value and reload the image.
command: show version
SOURCES(Information taken from the follwing URLs)
need to go to the priviledge exec mode(enable) Router(boot)#
and this may have a copy command you are looking for.
BOOT PROCESS
1. ROM monitor process—The ROM monitor looks for the rxboot image in the BOOTLDR variable in NVRAM (set using the boot bootldr device:filename command). If the ROM monitor finds the rxboot image, the ROM monitor loads that image and then proceeds to the Rxboot images process.
2. If the ROM monitor does not find the rxboot image, it looks for the BOOT variable (set using the boot system flash device:filename commands), which is a list of image names. If the ROM monitor finds and successfully loads one of these images, the boot process is complete.
3. If the ROM monitor does not find any of the images specified by the BOOT variable, it loads the first image on the Flash PC card in slot 0. If it does not find an image on the Flash PC card in slot 0, it loads the first image in boot Flash. If it does not find an image in boot Flash, it goes to the ROM monitor prompt.
4. Rxboot image process—The rxboot image runs and parses the configuration file looking for boot system commands. The boot system [rcp | tftp] filename [ip-address] commands specify which image to boot when netbooting. The boot system flash device:filename commands specify what to boot when booting from Flash. The commands are attempted in the order that they appear in the configuration file. If any command succeeds, the boot process is complete. If none of the commands succeed, the system remains at the rxboot image.
IMAGE DESCRIPTIONS
ROM Monitor—This image gains control at reset, power up, or after a nonrecoverable event (such as a bus error). It contains the user interface of the current Cisco ROM monitor, disassembler, memory display, and so on. It has console drivers and trap handlers for parity and bus errors. It does not have any network interface code. The ROM monitor is able to read the flash devices. This image is run from ROM.
Rxboot Image (Boot Image)—This limited function system image has network interface code and end-host protocol code. This image is used as a backup in case the RSM goes down while programming Flash for the main Cisco IOS image. This image is run from RAM.
System image—This is the main Cisco IOS image.
RECOVER FROM RXBOOT LOAD ONLY
Step 1 Verify that the new Cisco IOS software image has been stored properly. Use the show flash command to make sure that the file has been saved, that the size is correct, and that you do not have an invalid checksum message.
Command: show flash
alt-commands: pwd (primary working directory)
(bootflash:,slot0:,slot1
alt-commands: dir (shows you the files on a
particular device.)
If the file does not appear, or if it appears followed by "[invalid checksum]", or if the size does not correspond to the file size on the TFTP server, you must start the installation again. Be aware that the size is listed in bytes in the router and is sometimes listed in kilobytes in TFTP servers.
Step 2 Verify that the boot system commands are in the right order in the configuration. The router stores and executes the boot system commands in the order in which you enter them in the configuration file. If a boot system command entry in the list specifies an invalid device or filename, the router skips that entry.
command: boot system
Step 3 Verify that the config register value is correct. The last digit should be a 2. You can check this with the show version command. If the value is not correct, you must restore a valid value and reload the image.
command: show version
SOURCES(Information taken from the follwing URLs)
- Status
Similar threads
