Table Of Contents
ROM Monitor
Entering the ROM Monitor Program
ROM Monitor Command Conventions
Command Aliasing
ROM Monitor Commands
ROM Monitor
The information in this chapter applies to the Cisco AS5350XM and Cisco AS5400XM universal gateways.
This chapter describes the Cisco AS5350XM and Cisco AS5400XM ROM monitor, the first software to run when the gateway is powered-up or reset. The ROM monitor can help you isolate or rule out hardware problems encountered when installing your gateway. This appendix describes the following:
•
Entering the ROM Monitor Program
•
ROM Monitor Command Conventions
•
Command Aliasing
•
ROM Monitor Commands
Entering the ROM Monitor Program
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 gateway in the standalone ROM monitor. An example of the ROM monitor prompt follows:
To enable the Break key, and 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 following configuration command:
The new configuration register value, 0x0, takes effect after the gateway 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 gateway.
Timesaver
Break (system interrupt) is always enabled for 60 seconds after rebooting the system, regardless of whether break is configured to be off by setting the configuration register. During the 60-second window, you can break to the ROM monitor prompt.
ROM Monitor Command Conventions
Following are ROM monitor command conventions:
•
Brackets [ ] denote an optional field. If a minus option is followed by a colon (for example: [-s:]), you must provide an argument for the option.
•
A word in italics means that you must fill in the appropriate information.
•
All address and size arguments to the memory-related commands are assumed to be hexadecimal (no "0x" prefix or "h" suffix needed).
•
The options [-bwl] for the memory-related commands provide for byte, word, and longword operations. The default is word.
•
You can invoke the memory-related commands by entering the command with no arguments. This causes the utility to prompt you for parameters. This option is available for the commands marked as prompting.
•
All the built-in commands can be aborted (user interrupt signal) by pressing the Break key at the console.
•
You can place more than one command (except the repeat command) on a line by using the semicolon delimiter.
Command Aliasing
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 you 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:
ROM Monitor Commands
At the ROM monitor prompt, enter ? or help at the rommon n > prompt to display a list of available commands and options, as follows:
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
dis disassemble instruction stream
frame print out a selected stack frame
hardware_info display hardware information
help monitor builtin command help
history monitor command history
meminfo memory information (-spd dumps SDRAM cookie)
rommon-pref select ROMMON
set show all monitor variables
showmon display currently selected ROM monitor
stack produce a stack trace
sync write monitor environment to NVRAM
sysret print out info from last system return
tftpdnld tftp image download
unset unset a monitor variable
Note
You can display additional details for a command by entering the command name with a -? option, which prints the command usage message.
The commands are listed and described in alphabetical order. Note that the ROM monitor commands are case sensitive.
•
alias [name = value]—Aliases a name to a value. If the value contains white space or other special (shell) characters, it must be enclosed in quotation marks. If the value has a space as the last character, the next command-line word is also checked for an alias (normally only the first word on the command line is checked). Without an argument, this command prints a list of all aliased names with their values.
For example:
•
boot or b—Boots an image. The boot command with no arguments boots the first image in boot flash memory. You can include an argument, filename, to specify a file to be booted over the network using the Trivial File Transfer Protocol (TFTP). The local device (see the description of b device following) can be specified by entering the device specifier (devid). If the specified device name is not recognized by the ROM monitor, the system attempts to boot the image (imagename) from a network TFTP server. Do not insert a space between devid and imagename. Options to the boot command are -x, load image but do not execute, and -v, verbose. The form of the boot command follows:
The Cisco AS5350XM and Cisco AS5400XM universal gateways support the following three boot commands at the ROM monitor level:
boot [-xv] [devid] [imagename]
b—load/run the first XM image on flash.
b flash:filename—Load or run the image pointed to by flash:filename.
•
confreg [hexnum]—When executed with the argument hexnum, changes the virtual configuration register to match the hex number specified. Without the argument, the confreg command dumps the contents of the virtual configuration register in English and allows you to alter the contents. You are prompted to change or keep the information held in each bit of the virtual configuration register. In either case, the new virtual configuration register value is written into NVRAM and does not take effect until you reset or power cycle the gateway.
The configuration register resides in NVRAM. The configuration register is identical in operation to other Cisco gateways. Enter the confreg command for the menu-driven system, or enter the new value of the register in hexadecimal.
Note
The value is always interpreted as hex. The confreg utility prints a before and after view of the configuration register when used in menu-driven mode.
For example:
(Virtual Configuration Register:0x0)
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]:
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]:
disable "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
4 = 19200, 5 = 38400, 6 = 57600, 7 = 115200 [0]:
change the boot characteristics? y/n [n]:
(Virtual Configuration Register:0x0)
do you wish to change the configuration? y/n [n]:
•
cont [-b]—Continues a loaded image that has stopped. The -b option sets the requested break points before continuing.
For example:
monitor: command "launch" aborted due to user interrupt
•
context—Displays the CPU context at the time of the fault. The context from kernel mode and process mode of a booted image is displayed, if available.
For example:
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
•
cookie—Displays the contents of the cookie PROM in hexadecimal format.
For example:
00 01 01 31 03 15 03 20 00 14 33 01 30 11 4a 41
42 30 33 35 31 30 37 38 32 00 00 00 00 00 13 63
0c 1d 00 00 00 00 11 11 22 22 33 33 44 44 55 55
66 66 77 77 88 88 99 99 00 00 11 11 22 22 33 33
ff 00 30 96 f8 00 7a ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
•
dev—Lists boot device identifications on the gateway.
For example:
•
dir devid—Lists the files on the named device.
For example:
File size Checksum File name
9474676 bytes (0x909274) 0x54322421 c5350-js-mz.Jan6
•
ethertype [fe | ge]—The Cisco AS5350XM and AS5400XM universal gateway Ethernet ports are Gigabit Ethernet ports (labeled GE0 and GE1 on the chassis). The Cisco IOS firmware and software is designed so that configurations for Fast Ethernet will work on the Cisco AS5350XM and AS5400XM universal gateways without requiring any modification by the user.
If the Cisco IOS commands, write or copy running-config startup-config have been used to save the configuration to NVRAM, then all references to Ethernet interfaces will now be GigabitEther, and the IOS commands, write terminal and show running configuration will always show GigabitEther.
If you must have FastEther available as a searchable word for any scripts you are using, you can use the ROMMON command, ethertype fe to change GigabitEther to FastEther. Once you enter ethertype fe, the IOS image will only recognize FastEther. It will not recognize GigabitEther.
For example:
•
frame [number]—Displays an entire individual stack frame. Enter a number to indicate which frame to display. You can also specify a number to indicate which stack frame to display. Note that the default is 0 (zero), which is the youngest frame.
For example:
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
•
help—Prints a summary of the ROM monitor commands to the console screen. This is the same output as entering ?
For example:
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
dis disassemble instruction stream
frame print out a selected stack frame
hardware_info display hardware information
help monitor builtin command help
history monitor command history
meminfo memory information (-spd dumps SDRAM cookie)
rommon-pref Select ROMMON
set show all monitor variables
showmon display currently selected ROM monitor
stack produce a stack trace
sync write monitor environment to NVRAM
sysret print out info from last system return
tftpdnld tftp image download
unset unset a monitor variable
•
history or h—Displays the command history, that is, the last 16 commands executed in the ROM monitor environment.
•
meminfo—Displays the size (in bytes), the starting address, the available range of the main memory, the starting point and size of packet memory, and the size of nonvolatile memory (NVRAM).
For example:
Main memory size:128 MB. Packet memory size:64 MB
Available main memory starts at 0xa000e000, size 0x7ff2000
Packet memory starts at 0xa8000000
Main memory control register:0xbe9022f4
Shared memory control register:0x00000202
•
reset or i—Resets and initializes the system, similar to power up.
•
rommon-pref [readonly | upgrade]—Selects the ROM monitor image to be booted on the next reload.
•
set—Displays all the monitor variables and their values.
•
showmon—Displays both ROM monitor images and verifies which image is running.
For example:
ReadOnly ROMMON version is:
System Bootstrap, Version 12.3(12r)PI6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2004 by cisco Systems, Inc.
Upgrade ROMMON version is:
System Bootstrap, Version 12.3(12r)PI6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2004 by cisco Systems, Inc.
Upgrade ROMMON currently running
Upgrade ROMMON is selected for next boot
•
stack [num]—Produces a stack trace of the number of frames, specified by num. The default is 5. The command dumps from the kernel stack and the process stack (if one is available) of a booted image.
For example:
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
•
sync—Writes the working in-core copy of the environment variables and aliases them to NVRAM so that they are read on the next reset.
•
sysret—Displays the return information from the last booted system image. This includes the reason for terminating the image, a stack dump of up to eight frames, and if an exception is involved, the address where the exception occurred.
For example:
count: 19, reason: user break
pc:0x60043754, error address: 0x0
FP: 0x80007e78, PC: 0x60043754
FP: 0x80007ed8, PC: 0x6001540c
FP: 0x80007ef8, PC: 0x600087f0
FP: 0x80007f18, PC: 0x80008734
•
tftpdnld -r—Loads the image from the TFTP server pointed to by TFTP_FILE as shown below:
TFTP_FILE=hyeh/c5400-js-mz.nemo.Sep20
The user must set up the preceding five environmental variables (variable = new.value)above to boot from the TFTP server as follows:
rommon 2> TFTP_FILE=user/newimage.ios
•
unalias name—Removes name and its associated value from the alias list.
•
unset varname—Removes the variable name from the variable list.
•
xmodem [- yc] destination_file_name—Downloads a system image to flash memory over the console port. The -y option performs the download. The -c option performs the download using 16-bit CRC error checking. The Xmodem transfer protocol supports a 128-byte block size, and the transfer begins with a block number starting at 1, which contains file data. This is the default transfer protocol.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0812R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006, 2009 Cisco Systems, Inc. All rights reserved.