There is extensive debug capability for troubleshooting issues with the VPN Router MC. This section explains how to use this capability efficiently.
Setting the Logging Level
There are two levels of logging available for Router MC: debug and info. The default logging level is information. With this level, only information and error messages are written to the log file. While troubleshooting issues on VPN Router MC, you might want to set the logging to the debug level. However, note that working in debug mode uses more system resources, which slows down the system. Hence, you must use the debug level only when it is required. Once you are finished with troubleshooting or collecting data for analysis, reset the level back to info. Work through the following steps to perform this task:
Collecting the Debug Information (Diagnostics)
After setting up the logging level to debug, you can collect or view the debug information in two ways: by using a Graphic User Interface (GUI) or the Command line Interface (CLI).
Using a Graphic User Interface
You can view the debug log messages in the Common Services user interface, by selecting VPN Security Management Solution > Admin > Logging > Operation. This is useful for viewing the information in real time without having the console access to the Router MC server. However, if you want to analyze the log offline or want to send this information to the Cisco support center for additional analysis, you might want to follow the procedure described in the section that follows.
Using a Command Line Interface
Using the CLI is more efficient than using a GUI to collect debug information from the Router MC Server. Work through the following steps to practice using the CLI:
The MDCSupportInformation.zip file does not include the Router MC database. However, this may be required by the Cisco Support team to replicate your setup. To collect the Router MC database, follow the procedure in the next section.
Collecting the Router MC Database
Work through the following steps to collect the Router MC database of the Router MC server:
Using the Log Files
The MDCSupportInformation.zip file is made up of a number of files. Hence to analyze the problem efficiently, you need to know which files are pertinent to the Router MC and therefore need to be analyzed Each message in the log files contains the timestamp, the module that has written the message, its type (information, debug or error), and its data. The following list outlines some of the most important logs that you need to analyze first, based on the types of problem you are experiencing:
The Router MC can generate the following reports, which can be used for troubleshooting Router MC: