Cisco Systems VG204XM, VG202XM manual Using Debug Commands, Error Reporting

Models: VG202 VG204XM VG204 VG202XM

1 52
Download 52 pages 56.9 Kb
Page 49
Image 49

Appendix A Using the ROM Monitor

Using Debug Commands

Ymodem uses CRC-16 error checking to validate each packet. Depending on the device that the software is being downloaded from, this function might not be supported by Xmodem

destination_file_name—Name of the system image file or the system configuration file. In order for the voice gateway to recognize it, the name of the configuration file must be voice gateway_confg.

Follow these steps to run the xmodem console download command.

Procedure

Step 1 Move the image file to the local drive where Xmodem will execute.

Step 2 Enter the xmodem command.

Error Reporting

Because the ROM monitor console download uses the console to perform the data transfer, when an error occurs during a data transfer, the system only displays the error messages on the console after the data transfer terminates.

If you changed the baud rate from the default rate, the error message is followed by a message telling you to restore the terminal to the baud rate specified in the configuration register.

Using Debug Commands

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

"xxx: kernel context state is invalid, can not proceed."

The following are the ROM monitor debugging commands:

stack or k—Produces a stack trace; for example:

rommon 6> stack

 

Stack trace:

 

PC = 0x801111b0

 

Frame 00: FP = 0x80005ea8

PC = 0x801111b0

Frame 01: FP = 0x80005eb4

PC = 0x80113694

Frame 02: FP = 0x80005f74

PC = 0x8010eb44

Frame 03: FP = 0x80005f9c

PC = 0x80008118

Frame 04: FP = 0x80005fac

PC = 0x80008064

Frame 05: FP = 0x80005fc4

PC = 0xfff03d70

context—Displays processor context; for example:

 

rommon 7> context

 

 

 

 

 

 

 

 

 

 

 

CPU

context of the most

recent exception:

 

 

 

 

 

 

PC

= 0x801111b0

MSR =

0x00009032

CR

= 0x53000035

LR

= 0x80113694

 

CTR

= 0x801065e4

XER =

0xa0006d36

DAR = 0xffffffff

DSISR

= 0xffffffff

 

DEC

= 0xffffffff

TBU

=

0xffffffff

TBL

= 0xffffffff

IMMR

= 0xffffffff

 

R0

= 0x00000000

R1

=

0x80005ea8

R2

= 0xffffffff

R3

= 0x00000000

 

R4

= 0x8fab0d76

R5

=

0x80657d00

R6

= 0x80570000

R7

= 0x80570000

 

R8

= 0x00000000

R9

=

0x80570000

R10

= 0x0000954c

R11

= 0x00000000

 

R12

= 0x00000080

R13 =

0xffffffff

R14

= 0xffffffff

R15

= 0xffffffff

 

Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM Voice Gateways Software Configuration Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

OL-16191-01

 

 

 

 

 

 

 

 

 

A-7

 

 

 

 

 

 

 

 

 

 

 

 

Page 49
Image 49
Cisco Systems VG204XM, VG202XM manual Using Debug Commands, Error Reporting, Context-Displays processor context for example