cc/td/doc/product/voice/c_access/vg_200
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Using the ROM Monitor

Using the ROM Monitor

This appendix describes using the ROM monitor (also called the bootstrap program), which is the firmware that runs when you power on or restart a Cisco Voice Gateway 200 (VG200). During normal operation, the ROM monitor helps to initialize the processor hardware and boot the operating system software. You can also use the ROM monitor to:

This appendix contains the following sections:

Entering the ROM Monitor Mode

To use the ROM monitor, you must have access to the console port (see the chapter "Overview."

Perform the following steps to enter the ROM monitor mode:


Step 1 Restart the gateway by entering the following command:

vg200> reload

Step 2 Force the gateway to stop booting and enter the ROM monitor mode by pressing the Break key in response to the following prompt:

Press the Break key during the first 60 seconds while the system is starting up

Verifying that You Are in ROM Monitor Mode

To verify that you are in the ROM monitor mode, check that the prompt displayed on your screen is the ROM monitor mode prompt, as follows:

rommon # >
 

The # is the line number and increases incrementally at each prompt.

From the Cisco IOS software, you can configure the gateway to automatically enter the ROM monitor mode the next time the gateway boots by setting virtual configuration register bits 3, 2, 1, and 0 to zero. From the console, enter the following configuration command:

rommon # >configuration-register 0x0
 

The new configuration register value, 0x0, is effective after the gateway is rebooted with the reload command. The gateway remains in the ROM monitor and does not boot the operating system.

As long as the configuration register value remains 0x0, you must manually boot the operating system from the console. Refer to the boot command in the "Command Descriptions" section.

ROM Monitor Commands

Enter ? or help at the ROM monitor mode prompt to display a list of available commands. For example:

rommon 1 >  ?
alias       set and display aliases command
boot        boot up an external process
break       set/show/clear the breakpoint
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 the file system
dis         display instruction stream
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
tftpdnld    tftp image download
unalias     unset an alias
unset       unset a monitor variable
xmodem      x/ymodem image download
rommon 2 >

Note You can abort any command by pressing the Break key at the console.

ROM Monitor Syntax Conventions

The ROM monitor syntax in this appendix uses the following conventions:

    command [abc]
    
    command type interface
    

Command Descriptions

This section lists some useful ROM monitor commands. Refer to the Cisco IOS configuration guides and command references for more information on ROM monitor commands.

Options to the boot command are -x, load image but do not execute, and -v, verbose.
Use the Cisco IOS commands show version and show hardware to display the source of the currently running image.
    rommon 8 > dir flash:
             File size               Checksum   File name
           2229799 bytes (0x220627)   0x469e vg200-i6s-mz
    
    rommon 9 > meminfo
     
    Main memory size: 32 MB.
    Available main memory starts at 0xa000e000, size 32704KB
    IO (packet) memory size: 25 percent of main memory.
    NVRAM size: 32KB
     
    
    rommon 10 > meminfo -l
     
    Supported memory configurations:
     
    DIMM 0       DIMM 1
    -------------------
                 4M
                 8M-DUAL
                 16M
                  32M-DUAL
    4M
    4M           4M
    4M           8M-DUAL
    4M           16M
    4M           32M-DUAL
    8M-DUAL
    8M-DUAL      4M
    8M-DUAL      8M-DUAL
    8M-DUAL      16M
    8M-DUAL      32M-DUAL
    16M
    16M          4M
    16M          8M-DUAL
    16M          16M
    16M          32M-DUAL
    32M-DUAL
    32M-DUAL     4M
    32M-DUAL     8M-DUAL
    32M-DUAL     16M
    32M-DUAL     32M-DUAL
     
    

Debugging Commands

Most debugging commands are functional only when Cisco IOS software has crashed or is aborted. If you enter a debugging command and Cisco IOS crash information is not available, the following error message appears:

"xxx: kernel context state is invalid, can not proceed."
 
    rommon 8 > sysret
    System Return Info:
    count: 19,  reason: a SegV exception
    pc:0x802b1040,  error address: 0x802b1040
    Stack Trace:
    FP: 0x80908398, PC: 0x802b102c
    FP: 0x809083b0, PC: 0x802b0b88
    FP: 0x809083d8, PC: 0x8017039c
    FP: 0x809083e8, PC: 0x8016f764
    

Configuration Register Commands

The virtual configuration register resides in NVRAM. You can display or modify the virtual configuration register from either the ROM monitor or the operating system software.

To change the virtual configuration register from the ROM monitor, enter confreg by itself for menu mode, or enter the new value of the register in hexadecimal.

In either case, the new virtual configuration register value is written into NVRAM, but is not effective until you reset or power-cycle the gateway.
The following display shows an example of the confreg command:
    rommon 7 > confreg
     
     
        Configuration Summary
    enabled are:
    break/abort has effect
    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]: 
    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]:  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
    break/abort has effect
    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
    

Procedures for Recovering Boot and System Images

If your Cisco VG200 experiences difficulties and no longer contains a valid Cisco IOS software image in Flash memory, you can recover the Cisco IOS image using one of the following ROM monitor commands:

Using the xmodem Command

The xmodem command establishes a connection between a console and the gateway console port for disaster recovery if both the boot and system images are erased from Flash memory.

xmodem [filename]---Establishes an Xmodem connection between the console and the gateway. The optional parameter filename specifies the source file containing the Cisco IOS image.

Other options include the following:

Using the tftpdnld Command

The tftpdnld command downloads a Cisco IOS software image from a remote server accessible from an Ethernet network interface on a Cisco VG200. The tftpdnld command downloads the Cisco IOS software image into Flash memory using TFTP.

The following software restriction applies when using the tftpdnld command:
(the Ethernet platform only accepts and sends Ethernet V2.0 data packets).

tftpdnld [-h] [-r]---Begins the TFTP copy procedure.

Options include the following:

The tftpdnld command requires that you specify certain variables when you issue the command. The syntax for specifying the variables is:

VARIABLE_NAME=value
 

The variables that you must specify include the following:

The following tftpdnld command variables are optional:

Specify the FE_SPEED_MODE variable for the Fast Ethernet network interface. After you specify the variables, you must re-enter the tftpdnld command. For example:
    rommon 1 > IP_ADDRESS=172.15.19.11
    rommon 2 > IP_SUBNET_MASK=255.255.255.0
    rommon 3 > DEFAULT_GATEWAY=172.16.19.1
    rommon 4 > TFTP_SERVER=172.15.20.10
    rommon 5 > TFTP_FILE=/tftpboot/vg200-i6s-mz
    rommon 6 > tftpdnld
     
         IP_ADDRESS=172.15.19.11
         IP_SUBNET_MASK=255.255.255.0
         DEFAULT_GATEWAY=172.16.19.1
         TFTP_SERVER=172.15.20.10
         TFTP_FILE=/tftpboot/vg200-i6s-mz
         
    Invoke this command for disaster recovery only.
    WARNING: all existing data in all partitions on flash will be lost!
    Do you wish to continue? y/n: [n]:
     
    

Enter y to begin downloading the Cisco IOS software image. When the process is complete, the ROM monitor mode prompt appears on your screen.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jun 12 12:56:46 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.