Specifications
Table Of Contents
- Contents
- Preface
- Getting Started
- Basic Router Configuration
- Interface Port Labels
- Viewing the Default Configuration
- Information Needed for Configuration
- Configuring Basic Parameters
- Configuring Static Routes
- Configuring Dynamic Routes
- Configuring Enhanced IGRP
- Basic Router Configuration
- Configuring Your Router for Ethernet and DSL Access
- Sample Network Deployments
- Configuring PPP over Ethernet with NAT
- Configuring PPP over ATM with NAT
- Configuring a LAN with DHCP and VLANs
- Configuring a VPN Using Easy VPN and an IPSec Tunnel
- Configure the IKE Policy
- Configure Group Policy Information
- Apply Mode Configuration to the Crypto Map
- Enable Policy Lookup
- Configure IPSec Transforms and Protocols
- Configure the IPSec Crypto Method and Parameters
- Apply the Crypto Map to the Physical Interface
- Create an Easy VPN Remote Configuration
- Verifying Your Easy VPN Configuration
- Configuration Example
- Configuring VPNs Using an IPSec Tunnel and Generic Routing Encapsulation
- Configuring a Simple Firewall
- Configuring a Wireless LAN Connection
- Sample Configuration
- Configuring Additional Features and Troubleshooting
- Additional Configuration Options
- Configuring Security Features
- Configuring Dial Backup and Remote Management
- Troubleshooting
- Reference Information
- Cisco IOS Software Basic Skills
- Concepts
- ROM Monitor
- Common Port Assignments
C-8
Cisco 1800 Series Integrated Services Routers (Fixed) Software Configuration Guide
OL-6426-02
Appendix C ROM Monitor
Debug Commands
Follow these steps to run Xmodem:
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, error messages are only displayed on the console once the data transfer is
terminated.
If you have 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.
Debug Commands
Most ROM monitor debugging commands are functional only when Cisco IOS software has crashed or
is halted. If you enter a debugging command and Cisco
IOS crash information is not available, you see
the following error message:
"xxx: kernel context state is invalid, can not proceed."
The following are 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:
> context
xt of the most recent exception
000000 R1 = 0x832552c4 R2 = 0xffffffffR3 = 0x00000000
000021 R5 = 0x839960a8 R6 = 0x00029220R7 = 0xffffffff
9c0000 R9 = 0xffffffff R22 = 0xffffffff R23 = 0xffffffff
000e881 R13 = 0xffffffff R14 = 0xffffffff R15 = 0xffffffff
fffffff R25 = 0xffffffff R30 = 0xffffffff IVPR = 0xffffffff
fffffff R25 = 0xffffffff R26 = 0xffffffff R27 = 0xffffffff
fffffff R29 = 0xffffffff R30 = 0xffffffff R31 = 0xffffffff
888002 LR = 0x800e3638 CTR = 0x8003af88 XER = 0xffffffff
fffffff TBL = 0xffffffff DEAR = 0xffffffff DBCR2 = Oxffffffff
fffffff DBCR0 = 0xffffffff DBCR1 = 0xffffffff DBCR2 = 0xffffffff
ffffffff IAC2 = 0xffffffff DAC1 = 0xffffffff MCSRR1 = 0xffffffff
03af88 MSR = 0x00029220
• frame—Displays an individual stack frame.