Cisco Emergency Responder 8.6 Troubleshooting Guide
Collecting Trace and Debug Information
Downloads: This chapterpdf (PDF - 342.0KB) The complete bookPDF (PDF - 1.24MB) | Feedback

Collecting Trace And Debug Information

Table Of Contents

Collecting Trace And Debug Information

Enabling Detailed Trace And Debug Information For Cisco Emergency Responder

Enabling Syslog


Collecting Trace And Debug Information


When you contact Cisco Technical Support for help with a problem that you are having with Cisco Emergency Responder (Emergency Responder), Cisco might request that you collect trace and debug information.

Because collecting trace and debug information affects Emergency Responder performance, you should only turn on tracing and debugging at Cisco's request. The generated information is for Cisco's use in resolving product problems.

Use the following sections to learn about:

Enabling Detailed Trace And Debug Information For Cisco Emergency Responder

Enabling Syslog

Enabling Detailed Trace And Debug Information For Cisco Emergency Responder

To enable detailed trace and debug information for Emergency Responder, follow these steps:

Procedure


Step 1 From the Emergency Responder web interface, select Cisco ER Group > Server Settings.

Emergency Responder opens the Server Settings page.

Step 2 From the left column, select the server from which you must collect debug or trace information.

Emergency Responder displays the settings for the server.

Step 3 Scroll down to the debug package and trace package sections and select the packages that Cisco Technical Support has requested.

The lists in each section are identical; make sure that you select the package in the list that Cisco requested. Packages selected in the Debug list generate trace information plus extra debug data. If Cisco requests that you select all packages, click Select All for the appropriate list.

The available packages include:

CER_DATABASE—The database subsystem, covers the log information generated by the database access code.

CER_REMOTEUPDATE—The remote update subsystem, which manages updates between servers.

CER_PHONETRACKINGENGINE—The phone tracking subsystem, which runs the phone tracking and switch-port and phone update processes.

CER_ONSITEALERT—The onsite alert subsystem for notifying onsite alert personnel.

CER_CALLENGINE—The call engine subsystem, which routes and processes calls.

CER_SYSADMIN—The system administration web interface subsystem.

CER_TELEPHONY—The telephony subsystem, used for interactions with Cisco Unified CM.

CER_AGGREGATOR—The aggregator module covers all Emergency Responder server communication and data handling with the phone tracking engine. The module includes the search and lookup of tracked data for the subsystems like cluster, Administration, Cisco IP SoftPhone and call routing.

CER_GROUP—The Emergency Responder server group subsystem, used for communicating between servers within a group.

CER_CLUSTER—The server cluster subsystem, used for communicating between Emergency Responder groups in a cluster.

Step 4 Click Update to save and activate your changes.

Emergency Responder begins generating the requested trace and debug information.


Note The traces for Emergency Responder can be collected from either Emergency Responder Serviceability web interface or by using the CLI.


Step 5 When you have finished generating debug and trace information, click Clear All for each section in which you have made a selection to turn off debug and trace. Then, click Update to complete the change.


Related Topics

Server Settings for CERServerGroup, Cisco Emergency Responder 8.6 Administration Guide

Serviceability Web Interface For Cisco Emergency Responder, Cisco Emergency Responder 8.6 Administration Guide

CLI, Cisco Emergency Responder 8.6 Administration Guide

Enabling Syslog

To collect trace and debug information, you must enable syslog for Emergency Responder.

To enable syslog for Emergency Responder, see the "Collecting Information From Syslog" section on page 16-2.