Troubleshooting VRC

This appendix provides information to help you when using the Cisco Voice Routing Center (VRC).

General FAQs

Table B-1 General Frequently Asked Questions

Question	Answer
What VRC documentation is available?	Cisco Voice Routing Center Software Version 1.2.1 reference documentation is located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/vrc/vrc1_2_1/index.htm Online Help Release Notes User Guide System Administration Help Files
What PTC documentation is available?	PTC 3.0 reference documentation is located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ptc/3 _0/index.htm
How do I import a file?	You can import a file from the console or the VRC client. From the console, click the Operations tab and choose Batch Import Network Element. From the client, choose Import Topology from the Topology menu. When you import files from the client, the batch import file must be located in the /tftpboot/gdpm/batch/ directory.
Why do I receive the following error on my browser when I try to launch the VRC client? No Java 2 SDK, Standard Edition v x.x.x support for APPLET!!	You are probably using an unsupported browser. VRC supports Internet Explorer 5.0 or 5.5 and Netscaper 7.
How do I execute a Discovery?	From the Baseline View, right click the Administrative Domain (AD) or region and choose Discover from the menu. We recommend that your initial Discovery be done at the AD level.
What is the difference between Normal and Forced Discovery?	Normal Discovery stops if an element is unreachable or if a network element is defined incorrectly in the topology (for example, a gateway is really a gatekeeper). See Discovering a Dial Plan for more details on why normal Discovery causes the Discovery operation to stop. Forced Discovery logs these errors and moves on to Discover the next network element.
When I open a saved design file, is it true that I may be out of sync with the Baseline?	Yes. Another user might have changed the baseline dial plan since you last started and saved your dial plan design.

Cisco VRC Error Messages

Where 539 is the internal error message number, Warning is the severity of error message, followed by a brief description. Error messages are reported numerically by the particular VRC operation or component they relate to.

Error—The VRC operation cannot continue until this error is fixed. For example, this means that the state of the component is not valid, and the Design View cannot be committed until the problem is corrected.
Warning—A problem was detected during the VRC operation. We recommend that you make the necessary changes to correct the problem. However, the operation can continue if you choose not to fix it.
Audit—VRC records user actions in audit files. The following are examples of user actions that VRC audits:

Changes to the topology (adding or removing elements)
Changes to the dial plan (design changes)
Changes to user administration (adding new user, changing privileges)
Logging in
Logging out

Information—An action has been completed.

Note If you are required to stop the VRC server and restart it to recover from an error, report the circumstances to Cisco Technical Support.

Note To help you troubleshoot a specific VRC component or subsystem, use the debugging tool on the console.

Table B-2 Error Message Types

VRC Component	Error Message Number Block
General	100-199
Database	200-299
Topology	300-399
Security	400-499
Dial Plan	500-599
GUI Infrastructure	600-699
Network Element Distribution	700-799
Network Element Discovery	800-899
File Manager	900-999
Request Handler	1000-1099
Network Element Access and Discovery	1100-1199
Design Manager	1200-1299
VRC Server	1300-1399
Administrative Service	1400-1499
Model Persistor	1500-1599
Common Modules	1600-1699
CLI Generator	1700-1799
Dial Plan Generator	1800-1899
Console Backup Restore	1900-1999
Report Service	2000-2999

This section provides general descriptions about error messages for specific VRC components. See the online help for a complete list of VRC error messages for each VRC component.

Database Error Messages

Database error messages are generated when there is an error during database operations. For example, most database errors are internal errors.

This is typically an internal error while inserting or updating a specific table in the MySQL database. Check the server environment and make sure that the MySQL server is running.

When you encounter database error messages, use the console to set the debug of the Database subsystem to On.

If you encounter errors with the database schema, you must reinstall the VRC software and reconfigure the database.

Topology Error Messages

Topology-related error messages occur most frequently during the following operations:

A region is created in the CNS security service when one is created in the dial plan. If the security service is unable to create the region, you receive errors.

When you encounter Topology error messages, use the console to set the debug of the Topology subsystem to On.

Security Error Messages

Security error messages are generated from the security service of the VRC server.

When you encounter Security error messages, use the console to set the debug of the security subsystem to on.

Discovery Error Messages

When you encounter Discovery error messages, use the console to set the debug of the Discovery subsystem to on.

Design Manager Error Messages

The VRC design manager presides over operations that take place while the user is in a design session. There can be 50 design sessions open at one time.

Most design manager error messages can be avoided if you check for the following issues:

Make sure that you are in the correct VRC View for the specific operation you are trying to execute. Most operations that involve the design manager take place in the Design View.
Your scope is the piece of the network over which you have administrative privileges. Only one user can administer a particular scope at a given time.
Some operations can occur concurrently, but others can only be handled by the VRC server one at a time. If an operation cannot be executed because it cannot be initialized, wait a few moments and try again. VRC might be waiting for an operation to complete, or an operation must be in the initialized state before you can execute it.

When you encounter design manager error messages, use the console to set the debug of the subsystems for the dial plan generation (DPGeneration) and dial plan controller (DialplanCtr) to on.

Troubleshooting the Cisco VRC

VRC Client

This section lists additional troubleshooting information for VRC client operation.

VRC Server

This section lists additional troubleshooting information for VRC server operation.

Table B-3 Log File Names that Capture Logging Information

Log File	User Activity	Dial Plan Problems	System Activity	System Errors	Debug Trace
Internal (server)	X	X	X	X	X
System (server)	X	X	X
Audit (server)	X
User (client)	per user	per user	per user

VRC MySQL

This section lists additional troubleshooting information for the MySQL operations in VRC.

Table of Contents

Troubleshooting Cisco VRC