|
Appendix A describes files for troubleshooting the VPN 3002 and LED indicators on the system. It also describes common errors that might occur while configuring and using the system, and how to correct them.
The VPN 3002 Hardware Client creates several files that you can examine and that can assist Cisco support engineers when troubleshooting errors and problems:
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 on 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 on View Saved Log File.
If the VPN 3002 crashes during operation, it saves internal system data in nonvolatile memory (NVRAM), and then automatically writes this data to a CRSHDUMP.
TXT file in flash memory when it is rebooted. This file contains the crash date and time, software version, tasks, stack, registers, memory, buffers, and timers which help Cisco support engineers diagnose the problem. In case of a crash, we ask that you send this file when you contact TAC for assistance. To view the CRSHDUMP.TXT
file,
see Administration | File Management | View, and click on View Saved Log Crash Dump File.
The VPN 3002 saves the current boot configuration file (CONFIG) and its predecessor (CONFIG.BAK) as files in flash memory. These files may be useful for troubleshooting. See Administration | File Management for information on managing files in flash memory.
LED indicators on the VPN 3002 are normally green or flashing amber. LEDs that are solid amber or off may indicate an error condition.
Contact Cisco TAC if any LED indicates an error condition.
The LEDs on the front of the VPN 3002 are:
LED | Status | Explanation |
---|---|---|
PWR | Green | Unit is on and has power. |
| Off | Unit is powered off. |
SYS | Flashing amber | Unit is performing diagnostics. |
| Solid amber | Unit has failed diagnostics. |
| Flashing green | Unit is negotiating DHCP or PPPoE. |
| Green | Unit is operational. |
VPN | Off | No VPN tunnel exists. |
| Amber | Tunnel has failed. |
| Green | Tunnel is established. |
The LEDs on the rear of the VPN 3002 indicate the status of the private and public interfaces.
LED | Explanation |
Green | Interface is connected to the network. |
OFF | Interface is not connected to the network. |
Flashing amber | Traffic is traveling across the interface. |
If you have configured the VPN 3002, and you are unable to connect to or pass data to the central-site VPN Concentrator, use Table A-1 to analyze the problem. Also, use the following section of this appendix to check the settings on the VPN Concentrator to which this VPN 3002 connects.
If your VPN 3002 experiences connectivity problems, check the configuration of the VPN Concentrator.
Step 1 Configure the connection as a Client, not LAN-to-LAN.
Step 2 Assign this VPN 3002 to a group. Configure group and user names and passwords. These must match the group and user names and passwords that you set on the VPN 3002. Refer to Chapter 14, "User Management," in the VPN 3000 Series Concentrator Reference Volume I.
Step 3 If the VPN 3002 uses PAT mode, enable a method of address assignment for the VPN 3002: DHCP, address pools, per user, or client specified. Refer to Chapter 6, "Address Management," in the VPN 3000 Series Concentrator Reference Volume I.
Step 4 If you are using Network Extension mode, configure a default gateway or a static route to the private network of the VPN 3002. Refer to Chapter 8, "IP Routing," in the VPN 3000 Series Concentrator Reference Volume I.
Step 5 Check the Event log. Refer to Chapter 10, "Events," in the VPN 3000 Series Concentrator Reference Volume I.
The following sections describe errors that might occur while using the HTML-based VPN 3002 Hardware Client Manager with a browser.
The Manager displays the Invalid Login or Session Timeout screen (see Figure A-1).
Problem | Possible Cause | Solution |
---|---|---|
You entered an invalid administrator login-name and password combination |
|
|
The Manager session has been idle longer than the configured timeout interval. (The default timeout interval is 600 seconds, which equals 10 minutes). |
| On the Administration | Access Rights | Access Settings screen, change the Session Timeout interval to a larger value and click on Apply. |
The Manager unexpectedly logs out.
Problem | Possible Cause | Solution |
---|---|---|
You clicked on the Refresh or Reload button on the browser navigation toolbar, and the Manager logged out. The main login screen displays. | To protect access security, clicking on Refresh or Reload on the browser toolbar automatically logs out the Manager session. | Do not use the browser navigation toolbar buttons with the VPN 3002 Hardware Client Manager. Use only the Manager Refresh button where it appears on a screen. We recommend that you hide the browser navigation toolbar to prevent mistakes. |
The Manager displays an incorrect screen or data when you click on the browser back or forward button.
The Manager displays a screen with the message: "Error/An error has occurred while attempting to perform the operation." An additional error message describes the erroneous operation (see Figure A-2).
The Manager displays a screen with the message: "Not Allowed / You do not have sufficient authorization to access the specified page." (see Figure A-3).
Problem | Possible cause | Solution |
---|---|---|
You tried to access an area of the Manager that you do not have authorization to access. |
|
|
The Manager displays a screen with the message: "Not Found/An error has occurred while attempting to access the specified page." The screen includes additional information that identifies system activity and parameters.
Problem | Possible cause | Solution |
---|---|---|
The Manager could not find a screen. |
| Clear the browser's cache: delete its temporary internet files, history files, and location bar references. Then try again. |
|
| Please note the system information on the screen and contact Cisco support personnel for assistance. |
Microsoft Internet Explorer displays a Script Error dialog box that includes the error message: No such interface supported.
These errors may occur while using the menu-based command-line interface from a console or Telnet session.
Error | Problem | Possible Cause | Solution |
---|---|---|---|
The system expected a valid 4-byte dotted decimal entry, and the entry was not in that format. |
| At the prompt, reenter a valid 4-byte dotted decimal number. | |
The system expected a number within a certain range, and the entry was outside that range. |
| At the prompt, reenter a number in the appropriate range. | |
The entry for a password and the entry to verify the password do not match. |
| At the Verify |
Posted: Wed Nov 20 10:53:27 PST 2002
Copyright 1989-2000©Cisco Systems Inc.