Table Of Contents
Trace Collection and Log Central in RTMT
Importing Certificates
Displaying Trace & Log Central Options in RTMT
Collecting Traces
Using the Query Wizard
Scheduling Trace Collection
Viewing Trace Collection Status and Deleting Scheduled Collections
Collecting a Crash Dump
Using Local Browse
Using Remote Browse
Using Q931 Translator
Displaying QRT Report Information
Using Real Time Trace
View Real Time Data
Monitor User Event
Updating the Trace Configuration Setting for RTMT
Related Topics
Trace Collection and Log Central in RTMT
The trace and log central feature in the Cisco Unified Presence real-time monitoring tool (RTMT) allows you to configure on-demand trace collection for a specific date range or an absolute time. You can collect trace files that contain search criteria that you specify and save the trace collection criteria for later use, schedule one recurring trace collection and download the trace files to an SFTP server on your network, or collect a crash dump file. After you collect the files, you can view them in the appropriate viewer within the real-time monitoring tool.
Note 
From RTMT, you can also edit the trace setting for the traces on the node that you have specified. Enabling trace settings decreases system performance; therefore, enable Trace only for troubleshooting purposes.
Note To use the trace and log central feature in the RTMT, make sure that RTMT can access all of the nodes in the cluster directly without Network Access Translation (NAT). If you have set up a NAT to access devices, configure the Cisco Unified Presence with a hostname instead of an IP address and make sure that the host names and their routable IP address are in the DNS server or host file.
Note For devices that support encryption, the SRTP keying material does not display in the trace file.
This chapter contains information on the following topics:
•Importing Certificates
•Displaying Trace & Log Central Options in RTMT
•Collecting Traces
•Using the Query Wizard
•Scheduling Trace Collection
•Viewing Trace Collection Status and Deleting Scheduled Collections
•Collecting a Crash Dump
•Using Local Browse
•Using Remote Browse
•Using Q931 Translator
•Displaying QRT Report Information
•Using Real Time Trace
•Updating the Trace Configuration Setting for RTMT
Importing Certificates
You can import the server authentication certificate that the certificate authority provides for each server in the cluster. Cisco recommends that you import the certificates before using the trace and log central option. If you do not import the certificates, the trace and log central option displays a security certificate for each node in the cluster each time that you log into RTMT and access the trace and log central option. You cannot change any data that displays for the certificate.
To import the certificate, choose System > Tools > Trace > Import Certificate.
A messages displays that states that the system completed the importing of server certificates. Click OK.
Displaying Trace & Log Central Options in RTMT
Before you begin, make sure that you have imported the security certificates as described in the "Importing Certificates" section.
To display the Trace & Log Central tree hierarchy, perform one of the following tasks:
•In the Quick Launch Channel, click System; in the tree hierarchy, double-click Tools; then, click the Trace & Log Central icon.
•Choose System > Tools > Trace > Open Trace & Log Central.
Tip From any option that displays in the tree hierarchy, you can specify the services/applications for which you want traces, specify the logs and servers that you want to use, schedule a collection time and date, configure the ability to download the files, configure zip files, and delete collected trace files.
After you display the Trace & Log Central options in the real-time monitoring tool, perform one of the following tasks:
•Collect traces for services, applications, and system logs on one or more servers in the cluster. See "Collecting Traces" section
•Collect and download trace files that contain search criteria that you specify as well as save trace collection criteria for later use. See "Using the Query Wizard" section
•Schedule a recurring trace collection and download the trace files to an SFTP server on your network. See "Scheduling Trace Collection" section
•Collect a crash dump file for one or more servers on your network. See "Collecting a Crash Dump" section.
•View the trace files that you have collected. See the "Using Local Browse" section.
•View all of the trace files on the server. See the "Using Remote Browse" section.
•View the current trace file that is being written on the server for each application. You can perform a specified action when a search string appears in the trace file. See "Using Real Time Trace" section.
Collecting Traces
Use the Collect Traces option of the trace and log central feature to collect traces for services, applications, and system logs on one or more servers in the cluster. You specify date/time range for which you want to collect traces, the directory in which to download the trace files, whether to delete the collected files from the server, and so on. The following procedure describes how to collect traces by using the trace and log central feature.
Note The services that you have not activated also display, so you can collect traces for those services.
If you want to collect trace files that contain search criteria that you specify or you want to use trace collection criteria that you saved for later use, see the "Using the Query Wizard" section.
Before You Begin
Perform one or more of the following tasks:
•Configure the information that you want to include in the trace files for the various services from the Trace Configuration window. For more information, see the "Trace Configuration" section on page 5-1.
•If you want alarms to be sent to a trace file, choose an SDI trace file as the alarm destination in the Alarm Configuration window. For more information, see the "Alarm Configuration" section on page 3-1.
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 In the tree hierarchy, double-click Collect Files.
The Select CUP Services/Applications tab displays.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Step 3 Perform one of the following tasks:
•To collect traces for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box.
•To collect traces for all services and applications on a particular server, check the check box next to the IP address of the server.
•To collect traces for particular services or applications on particular servers, check the check boxes that apply.
•To continue the trace collection wizard without collecting traces for services or applications, go to Step 4.
Note The services that you have not activated also display, so you can collect traces for those services.
Note You can install some of the listed services/applications only on a particular node in the cluster. To collect traces for those services/applications, make sure that you collect traces from the server on which you have activated the service/application.
Step 4 Click Next.
The Select System Services/Applications tab displays.
Step 5 Perform one of the following tasks:
•To collect all system logs for all servers in the cluster, check the Select All Logs on all Servers check box.
•To collect traces for all system logs on a particular server, check the check box next to the IP address of the server.
•To collect traces for particular system logs on particular servers, check the check boxes that apply.
For example, to collect CSA logs, check the Cisco Security Agent check box in the Select System Logs tab. To access user logs that provide information about users that are logging in and out, check the Security Logs check box in the Select System Logs tab.
•To continue the trace collection wizard without collecting traces for system logs, go to Step 6.
Step 6 Click Next.
Step 7 In the Collection Time group box, specify the time range for which you want to collect traces. Choose one of the following options:
•Absolute Range—Specify the server time zone and the time range (start and end date and time) for which you want to collect traces.
The time zone of the client machine provides the default setting for the Select Reference Server Time Zone field. All the standard time zones, along with a separate set of entries for all time zones that have Daylight Saving settings, display in the Select Time Zone drop-down list box.
The trace files that get modified in the date range (between the From date and the To date), get collected if the chosen time zone matches the time zone settings of the server (for example Server 1). If another server exists in the same Cisco Unified Presence cluster (Server 2), but that server resides in a different time zone, then the trace files that get modified in the corresponding date range in Server 2 will get collected from Server 2.
To set the date range for which you want to collect traces, choose the drop-down list box in the From Date/Time and To Date/Time fields.
•Relative Range—Specify the time (in minutes, hours, days, weeks, or months) prior to the current time for which you want to collect traces.
Step 8 From the Select Partition drop-down list box, choose the partition that contains the logs for which you want to collect traces.
Cisco Unified Presence Serviceability stores logs for up to two Linux-based versions of Cisco Unified Presence. Cisco Unified Presence Serviceability stores the logs for the version of Cisco Unified Presence that you are logged in to in the active partition and stores the logs for the other version of Cisco Unified Presence (if installed) in the inactive directory.
So, when you upgrade from one version of Cisco Unified Presence that is running on the Linux platform to another and log in to the new version of Cisco Unified Presence that is running on the Linux platform, Cisco Unified Presence Serviceability moves the logs from the previous version to the inactive partition and stores logs for the newer version in the active partition. If you log in to the older version of Cisco Unified Presence, Cisco Unified Presence Serviceability moves the logs for the newer version of Cisco Unified Presence to the inactive partition and stores the logs for the older version in the active directory.
Note Cisco Unified Presence Serviceability does not retain logs from Cisco Unified Presence versions that ran on the Windows platform.
Step 9 To specify the directory in which you want to download the trace files, click the Browse button next to the Download File Directory field, navigate to the directory, and click Open. The default specifies C:\Program Files\Cisco\Presence Serviceability\jrtmt\<server IP address>\<download time>.
Step 10 To create a zip file of the trace files that you collect, choose the Zip File radio button. To download the trace files without zipping the files, choose the Do Not Zip Files radio button.
Step 11 To delete collected log files from the server, check the Delete Collected Log Files from the server check box.
Step 12 Click Finish.
The window shows the progress of the trace collection. If you want to stop the trace collection, click Cancel.
When the trace collection process is complete, the message "Completed downloading for node <IP address>" displays at the bottom of the window.
Step 13 To view the trace files that you collected, you can use the Local Browse option of the trace collection feature. For more information, see the "Using Local Browse" section.
Additional Information
See the Related Topics.
Using the Query Wizard
The Trace Collection Query Wizard allows you to collect and download trace files that contain search criteria that you specify as well as to save trace collection criteria for later use. To use the Trace Collection Query Wizard, perform the following procedure.
Before You Begin
Perform one or more of the following tasks:
•From the Trace Configuration window, configure the information that you want to include in the trace files for the various services. For more information, see the "Trace Configuration" section on page 5-1.
•If you want alarms to be sent to a trace file, choose an SDI trace file as the alarm destination in the Alarm Configuration window. For more information, see the "Alarm Configuration" section on page 3-1.
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 In the tree hierarchy, double-click Query Wizard.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Step 3 In the window that opens, click one of the following radio buttons:
•Saved Query
Click the Browse button to navigate to the query that you want to use. Choose the query and click Open.
If you chose a single node generic query, the node to which RTMT is connected displays with a checkmark next to the Browse button. You can run the query on additional nodes by placing a checkmark next to those servers.
If you chose an all node generic query, all nodes display with a checkmark next to the Browse button. You can uncheck any server for which you do not want to run the query.
If you chose a regular query, all of the nodes that you selected when you saved the query display with a checkmark. You can check or uncheck any of the servers in the list. If you choose new servers, you must use the wizard to choose the services for that node.
To run the query without any modifications, click Run Query and go to Step 17. To modify the query, go to Step 4.
•Create Query
Step 4 Click Next.
The Select CUP Services/Applications tab displays.
Step 5 If you clicked the Saved Query radio button and chose a query, the criteria that you specified for query display. If necessary, modify the list of services/applications for which you want to collect traces. If you clicked the Create Query radio button, you must choose all services/applications for which you want to collect traces.
Tip To collect traces for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box. To collect traces for all services and applications on a particular server, check the check box next to the IP address of the server.
Note The services that you have not activated also display, so you can collect traces for those services.
Note You can install some listed services/applications only on a particular node in the cluster. To collect traces for those services/applications, make sure that you collect traces from the server on which you have activated the service/application.
Step 6 Click Next.
Step 7 In the Select System Services/Applications tab, check all check boxes that apply.
Tip To collect traces for all system logs for all servers in the cluster, check the Select All Logs on All Servers check box. To collect traces for all services and applications on a particular server, check the check box next to the IP address of the server.
Step 8 Click Next.
Step 9 In the Query Time Options group box, specify the time range for which you want to collect traces. Choose one of the following options:
•All Available Traces—Choose this option to collect all the traces on the server for the service(s) that you chose.
•Absolute Range—Specify the server time zone and the time range (start and end date and time) for which you want to collect traces.
The time zone of the client machine provides the default setting for the Select Reference Server Time Zone field. All the standard time zones, along with a separate set of entries for all time zones that have Daylight Saving settings, display in the Select Time Zone drop-down list box.
The trace files that get modified in the date range (between the From date and the To date), get collected if the chosen time zone matches the time zone settings of the server (for example Server 1). If another server exists in the same Cisco Unified Presence cluster (Server 2), but that server is in a different time zone, then the trace files that get modified in the corresponding date range in Server 2 will get collected from Server 2.
To set the date range for which you want to collect traces, choose the drop-down list box in the From Date/Time and To Date/Time fields.
•Relative Range—Specify the time (in minutes, hours, days, weeks, or months) prior to the current time for which you want to collect traces.
Step 10 To search by phrases or words that exist in the trace file, enter the word or phrase in the Search String field. The tool searches for an exact match to the word or phrase that you enter.
Step 11 From the Call Procession Impact Options drop-down list box, specify the level of impact you want the string search activity to have on call processing. Available options include Low, Medium, and High. Low impact causes the least impact on call processing but yields slower results. High impact causes the most impact on call processing but yields faster results.
Step 12 Choose one of the following options:
•To execute the query, click Run Query.
The Query Results folder displays. When the query completes, a dialog box that indicates that the query execution completed displays. Click OK and continue with Step 17.
•To save the query, click the Save Query button and continue with Step 13.
Step 13 Check the check box next to the type of query that you want to create.
•Generic Query—Choose this option if you want to create a query that you can run on nodes other than the one on which it was created. You can only create a generic query if the services that you chose exist on a single node. If you chose services on more than one node, a message displays. You can either save the query as a regular query or choose services on a single node.
Then, choose either the Single Node Query or All Node Query option. If you choose the Single Node Query, the trace collection tool by default chooses the server on which you created the query when you execute the query. If you choose the All Node Query option, the trace collection tool by default chooses all of the servers in the cluster when you execute the query.
Note You can choose servers other than the default before running the query.
•Regular Query—Choose this option if you only want to run the query on that node or cluster on which you created the query.
Step 14 Click Finish.
Step 15 Browse to the location to store the query, enter a name for the query in the File Name field, and click Save.
Step 16 Do one of the following tasks:
•To run the query that you have just saved, click Run Query and continue with Step 17.
•To exit the query wizard without running the query that you created, click Cancel.
Step 17 After the query execution completes, perform one or more of the following tasks:
•To view a file that you collected, navigate to the file by double-clicking Query Results, double-clicking the <node> folder, where <node> equals the IP address or host name for the server that you specified in the wizard, and double-clicking the folder that contains the file that you want to view. After you have located the file, double-click that file. The file displays in the viewer that is designated for that file type.
•Download the trace files and the result file that contains a list of the trace files that your query collected by choosing the files that you want to download, clicking Download, specifying the criteria for the download, and clicking Finish.
–To specify the directory in which you want to download the trace files and the results file, click the Browse button next to the Download all files field, navigate to the directory, and click Open. The default specifies C:\Program Files\Cisco\Presence Serviceability\jrtmt\<server IP address>\<download time>.
–To create a zip file of the trace files that you collect, check the Zip File check box.
–To delete collected log files from the server, check the Delete Collected Log Files from Server check box.
Tip After you have downloaded the trace files, you can view them by using the Local Browse option of the trace and log central feature. For more information, see the "Using Local Browse" section.
•To save the query, click Save Query and complete Step 13 through Step 15.
Additional Information
See the Related Topics.
Scheduling Trace Collection
You can use the Schedule Collection option of the trace and log central feature to schedule recurring up to 6 concurrent trace collections and to download the trace files to an SFTP server on your network, run another saved query, or generate a syslog file. To change a scheduled collection after you have entered it in the system, you must delete the scheduled collection and add a new collection event. To schedule trace collection, perform the following procedure.
Note You can schedule up 10 trace collection jobs, but only 6 trace collection can be concurrent. That is, only 6 jobs can be in a running state at the same time.
Before You Begin
Perform one or more of the following tasks:
•Configure the information that you want to include in the trace files for the various services from the Trace Configuration window. For more information, see the "Trace Configuration" section on page 5-1.
•If you want alarms to be sent to a trace file, choose an SDI trace file as the alarm destination in the Alarm Configuration window. For more information, see the "Alarm Configuration" section on page 3-1.
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 In the tree hierarchy, double-click Schedule Collection.
The Select CUP Services/Applications tab displays.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Step 3 Perform one of the following tasks:
•To collect traces for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box.
•To collect traces for all services and applications on a particular server, check the check box next to the IP address of the server.
•To collect traces for particular services or applications on particular servers, check the check boxes that apply.
•To continue the trace collection wizard without collecting traces for services or applications, go to Step 4.
Note The services that you have not activated also display, so you can collect traces for those services.
Note You can install some of the listed services/applications only on a particular node in the cluster. To collect traces for those services/applications, make sure that you collect traces from the server on which you have activated the service/application.
Step 4 Click Next.
The System Services/Applications tab displays.
Step 5 To collect traces on system logs, perform one of the following tasks:
•To collect all system logs for all servers in the cluster, check the Select All Logs on all Servers check box.
•To collect traces for all system logs on a particular server, check the check box next to the IP address of the server.
•To collect traces for particular system logs on particular servers, check the check boxes that apply.
•To continue the trace collection wizard without collecting traces for system logs, go to Step 6.
Step 6 Click Next.
Step 7 Specify the server time zone and the time range for which you want to collect traces.
The time zone of the client machine provides the default setting for the Select Reference Server Time Zone field. All the standard time zones, along with a separate set of entries for all time zones that have Daylight Saving settings, display in the Select Time Zone drop-down list box.
Step 8 To specify the date and time that you want to start the trace collection, click the down arrow button next to the Schedule Start Date/Time field. From the Date tab, choose the appropriate date. From the Time tab, choose the appropriate time.
Step 9 To specify the date and time that you want to end the trace collection, click the down arrow button next to the Schedule End Date/Time field. From the Date tab, choose the appropriate date. From the Time tab, choose the appropriate time.
Note The trace collection completes, even if the collection goes beyond the configured end time; however, the trace and log central feature deletes this collection from the schedule.
Step 10 From the Scheduler Frequency drop-down list box, choose how often you want to run the configured trace collection.
Step 11 From the Collect Files generated in the last drop-down list boxes, specify the time (in minutes, hours, days, weeks, or months) prior to the current time for which you want to collect traces.
Step 12 To search by phrases or words that exist in the trace file, enter the word or phrase in the Search String field. The tool searches for an exact match to the word or phrase that you enter and only collects those files that match the search criteria.
Step 13 To create a zip file of the trace files that you collect, check the Zip File check box.
Step 14 To delete collected log files from the server, check the Delete Collected Log Files from the Server check box.
Step 15 Choose one or more of the following actions:
•Download Files
•Run Another Query
•Generate Syslog
Step 16 Do one of the following:
•If you chose Download Files or Run Another Query, continue with Step 17.
•If you chose Generate Syslog, go to Step 19.
Step 17 In the SFTP Server Parameters group box, enter the server credentials for the server where the trace and log central feature downloads the results and click Test Connection. After the trace and log central feature verifies the connection to the SFTP server, click OK.
Note The Download Directory Path field specifies the directory in which the trace and log central feature stores collected files. By default, the trace collection stores the files in the home directory of the user whose user ID you specify in the SFTP parameters fields: /home/<user>/Trace.
Step 18 If you chose the Run Another Query Option, click the Browse button to locate the query that you want to run and click OK.
Note The trace and log central feature only executes the specified query if the first query generates results.
Step 19 Click Finish.
A message indicates that the system added the scheduled trace successfully.
Note If the real-time monitoring tool cannot access the SFTP server, a message displays. Verify that you entered the correct IP address, user name, and password
Step 20 Click OK.
Step 21 To view a list of scheduled collections, click the Job Status icon in the Quick Launch Channel.
Tip To delete a scheduled collection, choose the collection event and click Delete. A confirmation message displays. Click OK.
Additional Information
See the Related Topics.
Viewing Trace Collection Status and Deleting Scheduled Collections
To view trace collection event status and to delete scheduled trace collections, use the following procedure:
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 In the Quick Launch Channel, click the Job Status icon.
Step 3 From the Select a Node drop-down list box, choose the server for which you want to view or delete trace collection events.
This list of scheduled trace collections displays.
Possible job types include Scheduled Job, OnDemand, RealTimeFileMon, and RealTimeFileSearch.
Possible statuses include Pending, Terminated, Running, Cancel, and Terminated.
Step 4 To delete a scheduled collection, choose the event that you want to delete and click Delete.
Note You can only delete jobs with a status of "Pending" or "Running" and a job type of "ScheduleTask."
Additional Information
See the Related Topics.
Collecting a Crash Dump
Perform the following procedure to collect a core dump of trace files:
Procedure
Step 1 Display the Trace & Log Central tree hierarchy, as described in "Displaying Trace & Log Central Options in RTMT" section.
Step 2 Double-click Collect Crash Dump.
Note The services that you have not activated also display, so you can collect traces for those services.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Note You can install some of the listed services/applications only on a particular node in the cluster. To collect traces for those services/applications, make sure that you collect traces from the server on which you have activated the service/application.
Step 3 In the Select CUP Services/Applications tab, perform one of the following tasks:
•To collect traces for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box.
•To collect traces for all services and applications on a particular server, check the check box next to the server.
•To collect traces for particular services or applications on particular servers, check the check boxes that apply.
•To continue the collect crash dump wizard without collecting traces for services or applications, go to Step 4.
Step 4 Click Next.
Step 5 In the Select System Services/Application tab, perform one of the following tasks:
•To collect all system logs for all servers, check the Select All Services on all Servers check box.
•To collect traces for all system logs on a particular server, check the check box next to the IP address of the server.
•To collect traces for particular system logs on particular servers, check the check boxes that apply.
•To continue the collect crash dump wizard without collecting traces for system logs, go to Step 6.
Step 6 In the Collection Time group box, specify the time range for which you want to collect traces. Choose one of the following options:
•Absolute Range—Specify the server time zone and the time range (start and end date and time) for which you want to collect traces.
The time zone of the client machine provides the default setting for the Select Reference Server Time Zone field. All the standard time zones, along with a separate set of entries for all time zones that have Daylight Saving settings, display in the Select Time Zone drop-down list box.
The crash files that get modified in the date range (between the From date and the to date, get collected if the chosen time zone matches the zone settings of the server (for example Server 1). If another server exists in the same Cisco Unified Presence cluster (Server 2), that is in a different time zone, then the crash files that get modified in the corresponding date range in Server 2 will get collected from Server 2.
To set the date range for which you want to collect crash files, choose the drop-down list box in the From Date/Time and To Date/Time fields.
•Relative Range—Specify the amount of time (in minutes, hours, days, weeks, or months) prior to the current time for which you want to collect crash files.
Step 7 From the Select Partition drop-down list box, choose the partition that contains the logs for which you want to collect traces.
Cisco Unified Presence Serviceability stores logs for up to two Linux-based versions of Cisco Unified Presence. Cisco Unified Presence Serviceability stores the logs for the version of Cisco Unified Presence that you are logged in to in the active partition and stores the logs for the other version of Cisco Unified Presence (if installed) in the inactive directory.
So, when you upgrade from one version of Cisco Unified Presence that is running on the Linux platform to another and log in to the new version of Cisco Unified Presence that is running on the Linux platform, Cisco Unified Presence Serviceability moves the logs from the previous version to the inactive partition and stores logs for the newer version in the active partition. If you log in to the older version of Cisco Unified Presence, Cisco Unified Presence Serviceability moves the logs for the newer version of Cisco Unified Presence to the inactive partition and stores the logs for the older version in the active directory.
Note Cisco Unified Presence Serviceability does not retain logs from Cisco Unified Presence versions that ran on the Windows platform.
Step 8 To specify the directory in which you want to download the trace files, click the Browse button next to the Download File Directory field, navigate to the directory, and click Open. The default specifies C:\Program Files\Cisco\Presence Serviceability\jrtmt\<server IP address>\<download time>.
Step 9 To create a zip file of the crash dump files that you collect, choose the Zip File radio button. To download the crash dump files without zipping the files, choose the Do Not Zip Files radio button.
Note You cannot download a zipped crash dump file that exceeds 2 gigabytes.
Step 10 To delete collected crash dump files from the server, check the Delete Collected Log Files from Server check box.
Step 11 Click Finish.
A message displays that states that you want to collect core dumps. To continue, click Yes.
Note If you chose the Zip File radio button and the crash dump files exceed 2 gigabytes, the system displays a message that indicates that you cannot collect the crash dump file of that size with the Zip File radio button selected. Choose the Do Not Zip Files radio button, and try the collection again.
Additional Information
See the Related Topics.
Using Local Browse
After you have collected trace files and downloaded them to your PC, you can view them with a text editor that can handle UNIX variant line terminators such as WordPad on your PC, or you can view them by using the viewers within the real-time monitoring tool.
Note Do not use NotePad to view collected trace files.
Perform the following procedure to display the log files that you have collected with the trace and log central feature. If you zipped the trace files when you downloaded them to your PC, you will need to unzip them to view them by using the viewers within the real-time monitoring tool.
Before You Begin
Collect traces files as described in one of the following sections:
•"Collecting Traces" section
•"Using the Query Wizard" section
•"Scheduling Trace Collection" section
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 Double-click Local Browse.
Step 3 Browse to the directory where you stored the log file and choose the file that you want to view.
Step 4 To display the results, double-click the file.
Step 5 Click on the program (viewer) that you would like to use to view the file. If the program is not on the list, choose another program by clicking on the Other button.If you wish to use this program as your default viewer, click the Always use this program to open these files checkboxThe real-time monitoring tool displays the file in the appropriate viewer for the file type. If no other appropriate viewer applies, the real-time monitoring tool opens files in the Generic Log Viewer.
Additional Information
See the Related Topics.
Using Remote Browse
After the system has generated trace files, you can view them on the server by using the viewers within the real-time monitoring tool. You can also use the remote browse feature to download the traces to your PC.
Perform the following procedure to display and/or download the log files on the server with the trace and log central feature.
Before You Begin
Collect traces files as described in one of the following sections:
•"Collecting Traces" section
•"Using the Query Wizard" section
•"Scheduling Trace Collection" section
Procedure
Step 1 Display the Trace & Log Central options, as described in the "Displaying Trace & Log Central Options in RTMT" section.
Step 2 Double-click Remote Browse.
Step 3 Choose the appropriate radio button, and click Next. If you choose Trace Files, go to Step 4. If you choose Crash Dump, go to Step 9.
Note The services that you have not activated also display, so you can choose traces for those services.
Note You can install some listed services/applications only on a particular node in the cluster. To choose traces for those services/applications, make sure that you choose traces from the server on which you have activated the service/application.
Step 4 In the Select CUP Services/Applications tab, perform one of the following tasks:
•To choose traces for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box.
•To choose traces for all services and applications on a particular server, check the check box next to the IP address of the server.
•To choose traces for particular services or applications on particular servers, check the check boxes that apply.
•To continue the remote browse wizard without choosing traces for services or applications, go to Step 5.
Note The services that you have not activated also display, so you can choose traces for those services.
Note You can install some listed services/applications only on a particular node in the cluster. To choose traces for those services/applications, make sure that you choose traces from the server on which you have activated the service/application.
Step 5 Click Next.
The System Services/Applications tab displays.
Step 6 Perform one of the following tasks:
•To choose all system logs for all servers in the cluster, check the Select All Logs on all Servers check box.
•To choose traces for all system logs on a particular server, check the check box next to the IP address of the server.
•To choose traces for particular system logs on particular servers, check the check boxes that apply.
•To continue the remote browse wizard without collecting traces for system logs, go to Step 13.
Step 7 Click Next.
Step 8 Go to Step 13.
Step 9 In the CUP Applications/Services tab, perform one of the following tasks:
•To choose crash dump files for all services and applications for all servers in the cluster, check the Select All Services on All Servers check box.
•To choose crash dump files for all services and applications on a particular server, check the check box next to the IP address of the server.
•To choose crash dump files for particular services or applications on particular servers, check the check boxes that apply.
Step 10 Click Next.
Step 11 In the Select System Services/Application tab, perform one of the following tasks:
•To choose crash dump files for all servers, check the Select All Services on all Servers check box.
•To choose crash dump files for all system logs on a particular server, check the check box next to the IP address of the server.
•To choose crash dump files for particular system logs on particular servers, check the check boxes that apply.
•To continue the collect crash dump wizard without collecting crash dump files, go to Step 12.
Step 12 Click Next.
Step 13 Click Finish.
Step 14 After the traces become available, a message displays. Click Close.
Step 15 Perform one of the following tasks:
•To display the results, navigate to the file through the tree hierarchy. After the log file name displays in the pane on the right side of the window, you can either right-click the mouse to select the type of program that you would like to use to view the file or double-click the file to display the file in the default viewer.
Tip To sort the files that displays in the pane, click a column header; for example, to sort the files by name, click the Name column header.
The real-time monitoring tool displays the file in the appropriate viewer for the file type. If no other appropriate viewer applies, the real-time monitoring tool opens files in the Generic Log Viewer.
•To download the trace files, choose the files that you want to download, click Download, specify the criteria for the download, and click Finish.
–To specify the directory in which you want to download the trace files, click the Browse button next to the Download all files field, navigate to the directory, and click Open. The default specifies C:\Program Files\Cisco\Presence Serviceability\jrtmt\<server IP address>\<download time>.
–To create a zip file of the trace files that you collect, check the Zip File check box.
–To delete collected log files from the server, check the Delete Files on server check box.
•To delete trace files from the node, click the file that displays in the pane on the right side of the window; then, click the Delete button.
•To refresh a specific service or node, click the server name or service; then, click the Refresh button. After a message states that the remote browse is ready, click Close.
•To refresh all services and nodes that display in the tree hierarchy, click the Refresh All button. After a message states that the remote browse is ready, click Close.
Tip After you have downloaded the trace files, you can view them by using the Local Browse option of the trace and log central feature. For more information, see the "Using Local Browse" section.
Additional Information
See the Related Topics.
Using Q931 Translator
Note Cisco Unified Presence does not support the Q931 Translator.
Displaying QRT Report Information
Note Cisco Unified Presence does not support QRT report information.
Using Real Time Trace
The real-time trace option of the trace and log central feature in the RTMT allows you to view the current trace file that is being written on the server for each application. If the system has begun writing a trace file, the real time trace starts reading the file from the point where you began monitoring rather than at the beginning of the trace file. You cannot read the previous content.
The real-time trace provides the following options:
•View Real Time Data
•Monitor User Event
View Real Time Data
The view real time data option of the trace and log central feature allows you to view a trace file as the system writes data to that file. You can view real-time trace data in the generic log viewer for up to 10 services, 5 of which can exist on a single node. The log viewer refreshes every 5 seconds. As the traces get rolled into a new file, the generic log viewer appends the content in the viewer.
Note Depending on the frequency of the traces that a service writes, the View Real Time Data option may experience a delay before being able to display the data in the generic log viewer.
Procedure
Step 1 Display the Trace & Log Central tree hierarchy, as described in "Displaying Trace & Log Central Options in RTMT" section.
Step 2 Double-click Real Time Trace.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Step 3 Double-click View Real Time Data.
The Real Time Data wizard displays.
Step 4 From the Nodes drop-down list box, choose the node for which you want to view real-time data and click Next.
Step 5 Choose the service and the trace file type for which you want to view real-time data and click Finish.
Note The services that you have not activated also display, so you can collect traces for those services.
The real-time data for the chosen service displays in the generic log viewer.
Step 6 Check the Show New Data check box to keep the cursor at the end of the window to display new traces as they appear. Uncheck the Show New Data check box if you do not want the cursor to move to the bottom of the window as new traces display.
Step 7 Repeat this procedure to view data for additional services. You can view data for up to 10 services, 5 of which can exist on a single node. A message displays if you attempt to view data for too many services or too many services on a single node.
Step 8 When you are done viewing the real time data, click Close on the generic log viewer.
Additional Information
See the Related Topics.
Monitor User Event
The monitor user event option of the trace and log central feature monitors real-time trace files and performs a specified action when a search string appears in the trace file. The system polls the trace file every 5 seconds. If the search string occurs more than once in one polling interval, the system only performs the action once. For each event, you can monitor one service on one node.
Before you Begin
If you want to generate an alarm when the specified search string exists in a monitored trace file, enable the TraceCollectionToolEvent alert. For more information on enabling alerts, see the "Setting Alert Properties" section on page 8-2.
Procedure
Step 1 Display the Trace & Log Central tree hierarchy, as described in "Displaying Trace & Log Central Options in RTMT" section.
Step 2 Double-click Real Time Trace.
Note If any server in the cluster is not available, a dialog box displays with a message that indicates which server is not available. The unavailable server will not display in the Trace & Log Central windows.
Step 3 Double-click Monitor User Event.
The Monitor User Event wizard displays.
Step 4 Perform one of the following tasks:
•To view the monitoring events that you have already set up, choose the View Configured Events radio button, choose a server from the drop-down list box, and click Finish.
The events configured for the server that you choose display.
Note To delete an event, choose the event and click Delete.
•To configure new monitoring events, choose the Create Events radio button, click Next, and continue with Step 5.
Step 5 Choose the node that you want the system to monitor from the Nodes drop-down list box and click Next.
Step 6 Choose the service and the trace file type that you want the system to monitor and click Next.
Note The services that you have not activated also display, so you can collect traces for those services.
Step 7 In the Search String field, specify the phrases or words that you want the system to locate in the trace files. The tool searches for an exact match to the word or phrase that you enter.
Step 8 Specify the server time zone and the time range (start and end date and time) for which you want the system to monitor trace files.
The time zone of the client machine provides the default setting for the Select Reference Server Time Zone field. All the standard time zones, along with a separate set of entries for all time zones that have Daylight Saving settings, display in the Select Time Zone drop-down list box.
The trace files that get modified in the date range (between the From date and the To date), get monitored if the chosen time zone matches the time zone settings of the server (for example Server 1). If another server exists in the same Cisco Unified Presence cluster (Server 2), but that server is in a different time zone, then the trace files that get modified in the corresponding date range in Server 2 will get monitored from Server 2.
To set the date range for which you want to monitor traces, choose the drop-down list box in the From Date/Time and To Date/Time fields.
Step 9 Choose one or more of the following actions that you want the system to perform when it encounters the search string that you specified in the Search String field:
•Alert—Choose this option to generate an alarm when the system encounters the specified search string. For the system to generate the alarm, you must enable the enable the TraceCollectionToolEvent alert. For more information on enabling alerts, see the "Setting Alert Properties" section on page 8-2.
•Local Syslog—Choose this option if you want the system to log the errors in the application logs area in the SysLog Viewer. The system provides a description of the alarm and a recommended action. You can access the SysLog Viewer from RTMT.
•Remote Syslog—Choose this option to enable the system to store the syslog messages on a syslog server. In the Server Name field, specify the syslog server name.
•Download File—Choose this option to download the trace files that contain the specified search string. In the SFTP Server Parameters group box, enter the server credentials for the server where you want to download the trace files and click Test Connection. After the trace and log central feature verifies the connection to the SFTP server, click OK.
Note The Download Directory Path field specifies the directory in which the trace and log central feature stores collected files. By default, the trace collection stores the files in the home directory of the user whose user ID you specify in the SFTP parameters fields: /home/<user>/Trace.
Note The system polls the trace files every 5 seconds and performs the specified actions when it encounters the search string. If more than one occurrence of the search string occurs in a polling interval, the system performs the action only once.
Step 10 Click Finish.
Additional Information
See the Related Topics.
Updating the Trace Configuration Setting for RTMT
To edit trace settings for the Real-Time Monitoring plug-in, choose Edit > Trace Settings; then, click the radio button that applies. The system stores the rtmt.log file in the logs directory where you installed the RTMT plug-in; for example, C:\Program Files\Cisco\Presence Serviceability\jrtmt\log.
Tip The Error radio button equals the default setting.
Additional Information
See the Related Topics.
Related Topics
•Using the Query Wizard
•Using Local Browse
•Collecting Traces
•Scheduling Trace Collection
•Displaying Trace & Log Central Options in RTMT
•Collecting a Crash Dump
•Using Local Browse
•Trace Configuration, page 5-1
•Alert Configuration in RTMT, page 8-1
Feedback