![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Cisco 4500-M and Cisco 4700-M ROM Monitor
This appendix describes the Cisco 4500-M and Cisco 4700-M ROM monitor, the first software to run when the router is powered up or reset. The Cisco 4500-M and Cisco 4700-M ROM monitor supports more features than the familiar Cisco 4000-M ROM monitor. The ROM Monitor can help you isolate or rule out hardware problems encountered when installing your router. A summary of the ROM monitor diagnostic tests and command options is provided.
The ROM monitor diagnostics help initialize the processor hardware and boot the main operating system software. If you set the software configuration register (bits 3, 2, 1, and 0) to zero, you can start the router in the standalone ROM monitor. An example of the Cisco 4500-M and Cisco 4700-M ROM monitor prompt follows:
rommon 1 >
To enable Break and to default to booting at the ROM monitor while running the system software, reset the configuration register to 0x0 by entering configuration mode, then enter the following configuration command:
config-reg 0x0
The new configuration register value, 0x0, takes effect after the router is rebooted when you enter the reload command. If you set the configuration to 0x0, you will have to manually boot the system from the console each time you reload the router.
At the ROM monitor prompt, enter ? or help at the rommon 1 > prompt to display a list of available commands and options, as follows:
Following are ROM monitor command conventions:
The following case-sensitive ROM monitor commands are among the most useful:
Most of the debugging commands are functional only when the Cisco IOS software has crashed or is aborted. If you enter the debug commands and Cisco IOS crash information is not available, the screen will display the following error message:
The configuration register resides in NVRAM. The configuration register is identical in operation to other Cisco routers. Enter the confreg command for the menudriven system, or enter the new value of the register in hexadecimal.
Copyright 1988-1996 © Cisco Systems Inc.
Available ROM Monitor Commands
rommon 1 > ?
help monitor builtin command help
boot boot up an external process
dir list files in file system
dev list the device table
confreg configuration register utility
reset system reset
stack produce a stack trace
context display the context of a loaded image
frame print out a selected stack frame
sysret print out info from last system return
meminfo main memory information
rommon 2 >
ROM Monitor Command Conventions
boot
[
-xv
]
[devid][imagename]
rommon 10 > dev
Devices in device table:
id name
flash: flash
bootflash: boot flash
eprom: eprom
rommon 11 > dir flash:
File size Checksum File name
2229799 bytes (0x220627) 0x469e C4500-k
Debugging Commands
"xxx: kernel context state is invalid, can not proceed."
rommon 8 > sysret
System Return Info:
count: 19, reason: user break
pc:0x60043754, error address: 0x0
Stack Trace:
FP: 0x80007e78, PC: 0x60043754
FP: 0x80007ed8, PC: 0x6001540c
FP: 0x80007ef8, PC: 0x600087f0
FP: 0x80007f18, PC: 0x80008734
rommon 9 > meminfo
Main memory size: 8 MB. Packet memory size: 4 MB
Available main memory starts at 0xa000e001, size 0x7f1fff
Packet memory starts at 0xa8000000
NVRAM size: 0x20000
Configuration 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