|
|
This appendix describes the Cisco 800 series router ROM monitor. The ROM monitor runs when the router is powered up or reset and helps to initialize the processor hardware and boot the operating system software.
You might need to access the ROM monitor for the following reasons:
To use the ROM monitor, you must connect a terminal or PC to the light-blue Console port on the router. (For information on making this connection, see the Cisco 800 Series Routers Hardware Installation Guide.)
To use the ROM monitor, perform the following steps:
The Flash memory contains a software image unless you deleted it by using the ROM monitor erase command.
Step 2 Reload the software by doing one of the following:
router# reloadStep 3 Perform this step only if Flash memory contains a software image. Before the terminal or PC displays Boot ... (approximately 10 seconds), press Escape, Control-C, or Break.
The router enters the ROM monitor as indicated by the following prompt:
boot#
While in the ROM monitor, you can access basic configuration parameters and commands. The parameters and commands that you can access depends on the mode you are in. For more information on modes, see the next section. For information on parameters, see the "Configuring Basic Configuration Parameters" section later in this appendix. For information on commands, see the "Commands" section later in this appendix.
The ROM monitor consists of the following modes:
 |
Note Cisco does not recommend setting a ROM monitor password. The only situation in which you should set a password is if you allow remote access to the ROM monitor through a modem. If you set this password, you will be in disable mode when you enter the ROM monitor and must enter the password if you want to enter enable mode. If you forget this password, you must contact the Cisco Technical Assistance Center to recover it. |
You can access these modes by entering the following commands at the ROM monitor prompt:
The parameters and commands that you can access depend on the mode you are in. For more information on parameters, commands, and modes, see
"Configuring Basic Configuration Parameters" and "Commands" later in this appendix.
To access a listing of the basic configuration parameters and their possible settings, enter the following command:
boot# set ?
A display similar to the following example appears:
set baud ={300|1200|2400|4800|9600|19200|38400|57600|115200}
set data-bits ={7|8}
set parity ={none|even|odd}
set stop-bits ={1|2}
set console-flags ={rts|dsr}
set mac-address =X.X.X
set unit-ip =N.N.N.N
set serv-ip =N.N.N.N
set netmask =N.N.N.N
set gate-ip =N.N.N.N
set pkt-timeout =N (seconds)
set tftp-timeout =N (seconds)
set boot-action ={flash|tftp|none}
set debug-flags =N
set file-name ="file-name"
set watchdog ={off|on}
set prompt ="prompt-string"
set ios-conf =N
|
Note This display shows all available parameters. The parameters that actually display depend on which mode you are in. For information on modes, see the "ROM Monitor Modes" section earlier in this appendix. |
To configure a parameter, use the following command at the ROM monitor prompt:
set parameter = value
For example, to set the baud rate parameter to 19200, enter the following:
boot# set baud = 19200
Table D-1 describes the parameters, their defaults, and the modes in which they can be configured.
.
| Parameter | Description | Default | Modes Configured In |
|---|---|---|---|
baud1 | Baud rate of console port. | 9600 | enable |
data-bits1 | Data bits of console port. | 8 | enable |
parity1 | Parity of console port. | N/A | enable |
stop-bits1 | Stop bits of console port. | 1 | enable |
console-flags1 | Flags for Console port.
Enter 1 for rts, 2 for dsr, or 3 for both. | 0 | enable |
mac-address | Ethernet MAC address for your router, for example, 0BAD.1BAD.2BAD. | xxxx.xxxx.xxxx (Factory sets this value.) | enable |
unit-ip | IP address of your router. | 0.0.0.0 | enable |
serv-ip | IP address of your TFTP server. Used only if router is set up to boot from a TFTP server on your network. | 0.0.0.0 | enable |
netmask | Subnet mask for IP address. | 0.0.0.0 | enable |
gate-ip | Default gateway IP address. Used only if router is set up to boot from a TFTP server and if the server is on a different subnet. | 0.0.0.0 | enable |
pkt-timeout | Number of seconds before router retries a TFTP ACK or RRQ. | 4 | enable |
tftp-timeout | Number of seconds before TFTP ACK or RRQ fails. | 16 | enable |
boot-action | Action that router takes on power up:
| flash | enable |
file-name | Default filename for boot and upload commands, for example: c800-g3-mw. | c800-g3-mw | enable |
Automatic reboot if router becomes nonfunctional. | on | enable | |
prompt | CLI prompt string. | boot # | disable, enable |
ios-conf | Reset the configuration register. Equivalent to config-register software command. | 0 | enable |
To access a listing of the ROM monitor commands and a brief description of each command, enter the following command:
boot# help
A display similar to the following appears:
boot Execute image or CLI command script. delete Deletes file-name from flash (8th delete is permanent). disable Disable privileged commands. echo Display arguments (to test CLI behavior). enable Enable privileged or debug commands. flash Single cycle id/erase/write test for each flash chip. help Display help for command (* for all). list List files currently in ram and saved in flash. load Load saved boot environment from flash. passwd Set or change the ROM password. reset Reset console port to current parameters. set Set boot environment values. save Save boot environment or loaded file to flash. show Show current or saved boot environment. test Initiate endless H/W bringup testing. upload Load image or configuration data into RAM. undelete Undelete file-name (maximum of 8 deletes & undeletes).
|
Note This display shows all available commands. The commands that actually display depend on which mode you are in. For information on modes, see the "ROM Monitor Modes" section earlier in this appendix. |
Table D-2 describes the commands and the modes in which you can use them.
| Commands | Description | Mode |
|---|---|---|
boot [flash | tftp] |
| enable |
delete filename | Marks specified filename as deleted from Flash memory. (You need to specify pathname as well as filename.) The eighth time you delete a specified filename, the file is permanently deleted. | enable |
disable | Enter disable mode, which has access to fewer parameters and commands than enable mode. | disable, enable |
echo [arguments] | Display arguments to test CLI behavior. | enable |
enable | Enter enable mode. | disable, enable |
erase | Erases files marked for deletion from Flash memory. | enable |
help [command | *] |
| disable, enable |
list | List files currently in RAM and saved in Flash memory. | disable, enable |
load | Load current software configuration stored in Flash memory. | disable, enable |
passwd | Set or change the ROM monitor password, which protects the enable-mode commands. Cisco recommends setting up this password only if you allow remote access to the ROM monitor. If you set up a password, you will enter the disable mode in the ROM monitor and must enter the password if you want to enter the enable mode. If you forget the password, you must contact the Cisco Technical Assistance Center to recover it. | enable |
reboot | Resets the hardware, and boots the software. | enable |
reset | Reset console port to recognize reconfigured parameters. | enable |
save [file [= file-name]] |
| enable |
set [variable={value | ?}] |
| disable, enable |
show [saved] | Show current or saved configuration. | disable, enable |
upload [serial | tftp | xmodem] [= filename] | Load software image or configuration data from the specified source into RAM. | enable |
undelete [filename] | Undo the deletion of specified filename up to eight times. |
Before setting up your router to boot from a TFTP server, you must do the following:
To set up your router to boot from a TFTP server that is on an Ethernet network, follow these steps.
set unit-ip = ip-address
set serv-ip = ip-address
Step 2 Set up the subnet mask:
set netmask = subnet-mask
Step 3 If the TFTP server is on a different subnet than the router, set up an IP address for a gateway server:
set gate-ip = ip-address
Step 4 Set up the filename for the software image or script that will reside on the TFTP server by using the following command:
set file-name = filename
Your TFTP server configuration determines the filename.
Step 5 Boot the software by using one of the following methods:
a. If you want to set up the router to boot from the TFTP server each time you power-on the router, enter the following command:
b. If you want to boot from the TFTP server now but not each time you power-on the router, enter the following command:
When upgrading the ROM on the Cisco 800 series, you must do so from TinyROM (also called boot) mode while connected to the console port. This action requires you to reload the router and interrupt data transfer.
 |
Caution The Cisco 801, 802, 803, and 804 routers use a different TinyROM than the Cisco 805 router. When upgrading the TinyROM version, be sure you have the proper version for your router model. Downloading the Cisco 805 TinyROM to a Cisco 801-804 router or a Cisco 801-804 TinyROM to a Cisco 805 router will cause the router to become permanently inoperative. |
Before you upgrade the TinyROM on your router, make sure you understand the following notes:
Follow these steps to upgrade TinyROM using Xmodem:
Step 2 Click Login to log into CCO. When prompted, enter your username and password.
Step 3 Follow this path:
Software Center: Access Products: 800 Series
Step 4 Transfer the TinyROM image to the host that is connected to the router's console port.
|
Note The following upgrade procedure is initiated from TinyROM (also known as boot) mode. The ISDN connection is unavailable during the upgrade process. |
Step 5 Reload the TinyROM software by doing one of the following:
a. Enter the following command from privileged EXEC mode:
router# reload
b. Turn the router to standby, wait 5 seconds, then turn it on again.
Step 6 Immediately press Escape, Control-C, or Break.
This forces the router to access the TinyROM as indicated by the following prompt:
boot#
Step 7 Upload your new TinyROM image to the router from the host connected to the router's console port.
boot# upload xmodem =c800u-tinyrom-mw
The following is an example of output displayed while the software is uploading:
Ready for X/Modem upload ... [note: no status bar for xmodem transfers, abort with Control-X or break]
Step 8 From your host, enter the Xmodem send command for your terminal emulation software.
For example, if you are using HyperTerm, select Transfer > Send File. The Send File dialog box appears. Click Browse to locate the software image. Select Xmodem as the protocol, and click Send.
Step 9 When the transfer is complete, save the new TinyROM image to Flash memory:
boot# save file
The router then saves the new TinyROM to Flash memory and automatically reboots into normal running mode.
Below is an example of the TinyROM upgrade procedure using Xmodem:
router# reload Proceed with reload? [confirm] 3d00h: %SYS-5-RELOAD: Reload requested 3d00h: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed to up TinyROM version 1.0(2) Mon Nov 02 17:14:53 1998 Copyright (c) 1998 by cisco Systems, Inc. All rights reserved. POST ......... OK. 12MB DRAM, 4MB Flash. boot# upload xmodem =c800u-tinyrom-mw Ready for X/Modem upload ... CCCC
|
Note Enter the Xmodem transfer command from your terminal emulation program and send the file to the router through Xmodem. |
upload: succeeded (110 seconds).
|
Note Use the list command to see that the file was transferred successfully. |
boot# list Status Size Dev Name ------ 48K ram TinyROM-1.0(3) ------ 48K flash TinyROM-1.0(1) ------ 48K flash TinyROM-1.0(2) ---r-x 3322K flash c800-nsy6-mw.120-5.0.2.T1 8832K free 12288K total boot# save file Save will destroy "TinyROM-1.0(2)", continue? [y|N] y ROM update: erase, burn, and reboot (max. 5 seconds) ...
|
Caution In a few cases, the router might display a message saying that it is going to destroy the Cisco IOS. If this happens, answer y to the question to continue and then follow the procedure entitled "Upgrading Software from TinyROM" in "Upgrading Cisco IOS Software." |
The router saves the TinyROM image and reboots into normal running mode.
Follow these steps to upgrade the TinyROM using Trivial File Transfer Protocol (TFTP). This procedure is based on the following network example:
Step 2 Click Login to log into CCO. When prompted, enter your username and password.
Step 3 Follow this path:
Software Center: Access Products: 800 Series
Step 4 Transfer the TinyROM image to your TFTP server. (Be sure to use binary transfer mode when any TCP/IP transfer method such as TFTP or FTP is used.)
|
Note The following upgrade procedure is initiated from TinyROM (also known as boot) mode. The ISDN connection is unavailable during the upgrade process. |
Step 5 Enter the TinyROM by performing the following steps:
a. Reload the software by doing one of the following:
router# reload
b. Immediately press Escape, Control-C, or Break.
boot#
Step 6 Set IP address for the TFTP server:
boot# set serv-ip = 10.2.0.2
Step 7 Set IP address and subnet mask for the router:
boot# set unit-ip = 10.1.0.1 boot# set netmask = 255.255.255.0
Step 8 If the TFTP server is on a different subnet than the router, set up an IP address for a gateway server:
boot# set gate-ip = 10.1.0.2
Step 9 Download the software image from the TFTP server:
boot# upload tftp =c800u-tinyrom-mw TFTP initiated. upload: succeeded (4 seconds).
Step 10 When the transfer is complete, save the new TinyROM image to Flash memory:
boot# save file
The router then saves the new TinyROM to Flash memory and automatically reboots into normal running mode.
Below is an example of screen display showing keyboard entries and system responses for upgrade procedure using TFTP:
router# reload Proceed with reload? [confirm] 3d00h: %SYS-5-RELOAD: Reload requested 3d00h: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed to up TinyROM version 1.0(2) Mon Nov 02 17:14:53 1998 Copyright (c) 1998 by cisco Systems, Inc. All rights reserved. POST ......... OK. 12MB DRAM, 4MB Flash. boot# set serv-ip =10.2.0.2 boot# set unit-ip =10.1.0.1 boot# set netmask =255.255.255.0 boot# set gate-ip =10.1.0.2 boot# save boot# list Status Size Dev Name ------ 48K flash TinyROM-1.0(1) ------ 48K flash TinyROM-1.0(2) ---r-x 3160K flash c800-nsy6-mw 768K free 4096K total boot# upload tftp =c800u-tinyrom-mw TFTP initiated. upload: succeeded (4 seconds).
|
Note You can use the list command to see that the file was transferred successfully, as in this example: |
boot# list Status Size Dev Name ------ 48K ram TinyROM-1.0(3) ------ 48K flash TinyROM-1.0(1) ------ 48K flash TinyROM-1.0(2) ---r-x 3160K flash c800-nsy6-mw 768K free 4096K total boot# save file Save will destroy "TinyROM-1.0(2)", continue? [y|N] y ROM update: erase, burn, and reboot (max. 5 seconds) ...
|
Caution In a few cases, the router might display a message to say that it is going to destroy the Cisco IOS. If this happens, answer y to the question to continue, then follow the procedure entitled "Upgrading Software from TinyROM" in "Upgrading Cisco IOS Software." |
The router saves the TinyROM image and reboots into normal running mode.
TinyROM Version 1.2(2) checks your Cisco router designation at installation time and prevents the loading of the wrong image on your router. For example, you will not be able to load a Cisco 805 TinyROM image on a Cisco 801, 802, 803, or 804 router.
To find out which version of the TinyROM image is installed on your router, do one of the following:
For information about how to upgrade your TinyROM image, refer to the "Upgrading TinyROM" section in this appendix.
Posted: Wed May 24 16:38:36 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.