Table of Contents
Advertisement
Troubleshooting and System Errors
Appendix A describes files you can use to troubleshoot errors and problems on the VPN 3002 and LED
indicators for the system. It also describes common errors that might occur while configuring and using
the system, and how to correct them. It includes the following topics:
Files for Troubleshooting
LED Indicators
System Errors
Settings on the VPN Concentrator
VPN 3002 Hardware Client Manager Errors
Command-Line Interface Errors
Files for Troubleshooting
The VPN 3002 Hardware Client creates several files that you can examine and that can assist Cisco
support engineers when troubleshooting errors and problems:
•
•
•
•
•
Event Logs
The VPN 3002 records system events in the event log, which is stored in nonvolatile memory (NVRAM).
To troubleshoot operational problems, we recommend that you start by examining the event log. To view
the event log, see Administration | File Management | View, and click View Saved Log File. To configure
events, and to choose the events you want to view, see Configuration | System | Events and Monitoring
| Filterable Event Log.
The VPN 3002 automatically saves the event log to a file in flash memory if it crashes, and when it is
rebooted. This log file is named SAVELOG.TXT, and it overwrites any existing file with that name. The
SAVELOG.TXT file is useful for debugging. To view SAVELOG.TXT, see Administration | File
Management | View, and click View Saved Log File .
OL-2854-01
Event log—Record of system events.
SAVELOG.TXT—Event log that is automatically saved when the system crashes and when it is
rebooted.
CRSHDUMP.TXT—Internal system data file that is written when the system crashes.
CONFIG—Normal configuration file used to boot the system.
CONFIG.BAK—Backup configuration file.
A P P E N D I X
VPN 3002 Hardware Client Getting Started
A
A-1
Advertisement
Table of Contents
