|
|
This appendix describes the Cisco uBR924 cable access router ROM monitor---the first software to run when the router is powered-on or reset. The ROM monitor helps you isolate or rule out hardware problems when installing the router.
This appendix describes:
The ROM monitor diagnostics help initialize the processor hardware and boot the main operating system software. The ROM monitor version introduced with the Cisco uBR924 in the
Cisco IOS Release 12.0(4)XI timeframe displays as follows:
rommon 2 > i System Bootstrap, Version 12.0(19990506:181223)[sjacobso-jac-xi26 2504] DEVELOPMENT SOFTWARE Copyright (c) 1994-1999 Cisco Systems, Inc. UBR924 platform with 16384 Kbytes of main memory
The ROM monitor main memory information is shown below:
rommon 3 > meminfo Main memory size: 16 MB Available main memory starts at 0x14000, size 16304 KB I/O (packet) memory size: 512 KB NVRAM size: 16 KB
To default to booting at the ROM monitor while running the system software, reset the configuration register to 0x0 by entering configuration mode, and enter the configuration command following:
config-reg 0x0The new configuration register value, 0x0, takes effect after the router is rebooted with 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.
Following are ROM monitor command conventions:
The ROM monitor supports command aliasing modeled on the aliasing function built into the Korn shell. The alias command is used to set and view aliased names. This allows the user to alias command names to a letter or word. Aliasing is often used to shorten command names or automatically invoke command options.
Aliases are stored in NVRAM and remain intact across periods of no power. These are some of the set aliases.
b=boot h=history i=reset r=repeat k=stack ?=help
Enter ? or help at the rommon > prompt to display a list of available commands and options:
rommon 12 > help alias set and display aliases command boot boot up an external process confreg configuration register utility cont continue executing a downloaded image context display the context of a loaded image cookie display contents of cookie PROM in hex dev list the device table dir list files in file system dnld serial download a program module frame print out a selected stack frame help monitor builtin command help history monitor command history meminfo main memory information repeat repeat a monitor command reset system reset set display the monitor variables stack produce a stack trace sync write monitor environment to NVRAM sysret print out info from last system return unalias unset an alias unset unset a monitor variable xmodem x/ymodem image download
The commands are listed and described in alphabetical order. Note that the ROM monitor commands are case-sensitive.
rommon 1 > alias
r=repeat
h=history
?=help
b=boot
ls=dir
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 "use all zero broadcast"? 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.
reboot >
monitor: command "launch" aborted due to user interrupt
diagmon 7 > cont
reboot>
rommon 6 > context
CPU Context:
d0 - 0x00000028 a0 - 0x0ff00420
d1 - 0x00000007 a1 - 0x0ff00000
d2 - 0x00000007 a2 - 0x02004088
d3 - 0x00000000 a3 - 0x020039e6
d4 - 0x00000000 a4 - 0x02002a70
d5 - 0x02003e8a a5 - 0x02003f17
d6 - 0x00000000 a6 - 0x02003938
d7 - 0x00000001 a7 - 0x0200392c
pc - 0x02004adc vbr - 0x02000000
rommon 1 > cookie
cookie:
01 01 00 00 0c 07 af 80 07 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
rommon 10 > dev
Devices in device table:
id name
eprom: eprom
flash: PCMCIA slot 1
rommon 11 > dir flash:
File size Checksum File name
65 bytes (0x41) 0xb49d clev/oddfiles65
2229799 bytes (0x220627) 0x469e C5200-k.z
rommon 6 > frame 2
Frame 02: FP = 0x02003960 RA = 0x020050ee
at 0x02003968 (fp + 0x08) = 0x02004f8d
at 0x0200396c (fp + 0x0c) = 0x0200f390
at 0x02003970 (fp + 0x10) = 0x02006afc
at 0x02003974 (fp + 0x14) = 0xc0a82983
at 0x02003978 (fp + 0x18) = 0x02003a7e
at 0x0200397c (fp + 0x1c) = 0x02002630
at 0x02003980 (fp + 0x20) = 0x00000000
at 0x02003984 (fp + 0x24) = 0x02000000
at 0x02003988 (fp + 0x28) = 0x0200c4a4
at 0x0200398c (fp + 0x2c) = 0x0200f448
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
rommon 5 > stack 8
Stack trace:
PC = 0x02004adc
Frame 00: FP = 0x02003938 RA = 0x02005f2a
Frame 01: FP = 0x02003948 RA = 0x02005df0
Frame 02: FP = 0x02003960 RA = 0x020050ee
Frame 03: FP = 0x02003994 RA = 0x02004034
Frame 04: FP = 0x02003b00 RA = 0x00012ca6
rommon 8 > sysret
System Return Info:
count: 19, reason: reset
pc:0x60043754, error address: 0x0
Stack Trace:
FP: 0x80007e78, PC: 0x60043754
FP: 0x80007ed8, PC: 0x6001540c
FP: 0x80007ef8, PC: 0x600087f0
FP: 0x80007f18, PC: 0x80008734
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Wed Aug 25 18:12:46 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.