Cisco Unified Real-Time Monitoring Tool Administration Guide, Release 9.0(1)
Performance Monitoring
Downloads: This chapterpdf (PDF - 970.0KB) The complete bookPDF (PDF - 6.71MB) | Feedback

Performance Monitoring

Contents

Performance Monitoring

RTMT performance monitoring

Tthe Cisco Unified Communications Manager and Cisco Unity Connection directly update Performance counters (called PerfMon counters). The counters contain simple, useful information on the system and devices on the system, such as number of registered phones, number of active calls, number of available conference bridge resources, and voice messaging port usage.

For Cisco Unified Communications Manager, the Cisco CallManager object contains most of the Cisco Unified Communications Manager performance counters, and these counters have only one instance. The instance-based counters that belong to the other objects can have zero or more instances. For example, if two phones are registered to Cisco Unified Communications Manager, two instances of each counter that belong to the Cisco phones object exist.

You can monitor the performance of the components of the system and the components for the application on the system by choosing the counters for any object by using RTMT. The counters for each object display when the folder expands.

You can log perfmon counters locally on the computer and use the performance log viewer in RTMT to display the perfmon CSV log files that you collected or the Realtime Information Server Data Collection (RISDC) perfmon logs.

RTMT integrates with existing software for performance monitoring:

  • RTMT integrates with the administration and serviceability software for both Cisco Unified Communications Manager and Cisco Unity Connection.
  • RTMT displays performance information for all Cisco Unified Communications Manager and Connection components.

RTMT provides alert notifications for troubleshooting performance. It also periodically polls performance counter to display data for that counter. You can choose to display perfmon counters in a chart or table format.

Performance monitoring allows you to perform the following tasks:

  • Unified CM and Unified CM BE only: Monitor performance counters including all the Cisco Unified Communications Manager servers in a cluster (if applicable), TFTP servers, and database servers.
  • Continuously monitor a set of preconfigured objects AND receive notification in the form of an e-mail message.
  • Associate counter threshold settings to alert notification. An e-mail or popup message provides notification to the administrator.
  • Save and restore settings, such as counters being monitored, threshold settings, and alert notifications, for customized troubleshooting tasks.
  • Display up to six perfmon counters in one chart for performance comparisons.
  • Use performance queries to add a counter to monitor.

Performance counter interface

RTMT contains ready-to-view, predefined performance counters. You can also select and add counters to monitor in RTMT using performance queries.

RTMT displays performance counters in chart or table format. Chart format looks like a miniature window of information. You can display a particular counter by double clicking the counter in the perfmon monitoring pane.

Attributes for predefined performance counters, such as format and category, remain fixed. You can define attributes for counters that you configure in RTMT. Because chart view represents the default, you configure the performance counters to display in table format when you create a category.

Category tabs

A category comprises a group of monitored performance counters. A tab in the RTMT monitoring pane contains the category name. All performance counters that are monitored in this tab belong to a category. RTMT displays any categories that you access during a RTMT session in the bottom toolbar.

The system polls the performance counters in the tab at the same rate, with each category configured to have its own polling rate.

You can create custom categories in the RTMT monitoring pane to view information that helps you troubleshoot specific performance, system, or device problems. If your system is experiencing performance problems with specific objects, create custom categories to monitor the performance of the counters within the object. If the system is experiencing problems with specific devices, create custom categories to monitor the devices in your system. In addition, you can create alert notifications for counters and gateways in these custom categories. To create custom categories, you add a new category tab. When the tab is created, you specify the specific performance counters, devices, and alerts within that tab and then save your custom category by using Profile.

Sample rate

The application polls the counters, devices, and gateway ports to gather status information.

The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds. If the collecting rate for the AMC (Alert Manager and Collector) service parameter changes, the polling rate in the precanned window also updates. In addition, the local time of the RTMT client application and not the backend server time, provides the basis for the time stamp in each chart. For more information on Service Parameters, refer to Cisco Unified Communications Manager Administration Guide or Cisco Unity Connection System Administration Guide.

In the RTMT monitoring pane, you configure the polling intervals for the applicable performance counters, devices, and gateway ports for each category tab that you create.


Note


High-frequency polling rate affects the performance on the server. The minimum polling rate for monitoring a performance counter in chart view equals 5 seconds; the minimum rate for monitoring a performance counter in table view equals 1 second. The default for both specifies 10 seconds.


Zoom perfmon counter

To get a closer look at perfmon counters, you can zoom a perfmon monitor counter in the RTMT.

Procedure
    Step 1   To zoom in a counter, perform one of the following tasks:
    1. To zoom predefined objects, such as System Summary, perform one of the following tasks:
      • Drag the mouse over the plot area in the counter to frame the data and release the mouse button. The counter zooms in the chart.
      • Click the counter. The counter zooms in.
    2. To zoom counters in the Performance pane, perform one of the following tasks (and resize the window, if necessary):
      • Double-click the counter that you want to zoom. The box with the counter appears highlighted and the Zoom window launches. The minimum, maximum, average, and last fields show the values for the counter since the monitoring began for the counter.
      • Click the counter to select the counter to zoom. The box with the counter appears highlighted. Right-click the counter and select Zoom Chart or choose System > Performance > Zoom Chart. The Zoom window launches. The minimum, maximum, average, and last fields show the values for the counter since the monitoring began for the counter.
    Step 2   To zoom out a counter, perform one of the following tasks:
    1. To zoom out predefined objects, such as System Summary, click the counter and press Z in the active counter to return the counter to original size.
    2. To zoom out counters in the Performance pane, click OK to close the Zoom window.

    Highlight charts and graphs

    The highlight feature helps to distinguish hosts and counters when multiple nodes or counters display on color-coded graphs. This feature is active in the System Summary, CPU and Memory, Disk Usage, and Performance Log Viewer windows.

    Procedure
      Step 1   To highlight charts and graphs, perform one of the following tasks:
      1. To highlight charts and graphs for predefined objects, such as System Summary, right-click in a plot area to highlight the nearest data series or point.
      2. To highlight charts and graphs in the performance log viewer, perform one of the following tasks
        • Right-click on any color code in the table below the chart in the Performance Log Viewer and choose Highlight to highlight the data series for that counter.
        • Right-click on any color code in the table below the chart in the Performance Log Viewer and choose Change Color to select a different color for the counter.
      Step 2   To return a highlighted item to its original appearance in the Performance Log Viewer, select another item to highlight.

      Counter properties

      Counter properties allow you to display a description of the counter and configure data-sampling parameters.

      The Counter Property window contains the option to configure data samples for a counter. The performance counters that display in the RTMT performance monitoring pane contain green dots that represent samples of data over time. You can configure the number of data samples to collect and the number of data points to show in the chart. After the data sample is configured, view the information by using the View All Data/View Current Data menu option to view all the data that a perfmon counter collected.

      Alert notification for counters

      Using the alert notification feature, the application notifies you of system problems. Perform the following configuration setup to activate alert notifications for a system counter:

      • From the RTMT Perfmon Monitoring pane, choose the system perfmon counter.
      • Set up an e-mail or a message popup window for alert notification.
      • Determine the threshold for the alert (for example, an alert activates when calls in progress exceed the threshold of over 100 calls or under 50 calls).
      • Determine the frequency of the alert notification (for example, the alert occurs once or every hour).
      • Determine the schedule for when the alert activates (for example, on a daily basis or at certain times of the day).

      Perfmon logs

      You can log perfmon counters locally on the computer and use the performance log viewer in RTMT to display the perfmon CSV log files that you collected or the Realtime Information Server Data Collection (RISDC) perfmon logs.

      RTMT allows you to choose different perfmon counters to log locally. You can then view the data from the perfmon CSV log by using the performance log viewer.

      Perfmon data log troubleshooting

      The troubleshooting perfmon data logging feature assists Cisco TAC in identifying system problems. When you enable troubleshooting perfmon data logging, you initiate the collection of a set of the applicable Cisco Unified Communications Manager, Cisco Unity Connection, and operating system performance statistics on the selected server. The statistics that are collected include comprehensive information that can be used for system diagnosis.

      The system automatically enables troubleshooting perfmon data logging to collect statistics from a set of perfmon counters that provides comprehensive information on the system state. When Troubleshooting Perfmon Data Logging is enabled, Cisco estimates that the system experiences a less than 5-percent increase in CPU utilization and an insignificant increase in the amount of memory that is being used, and it writes approximately 50 MB of information to the log files daily.

      You can perform the following administrative tasks with the troubleshooting perfmon data logging feature:

      • Enable and disable the trace filter for Troubleshooting perfmon data logging.
      • Monitor the applicable set of predefined System, Cisco Unified Communications Manager, and Cisco Unity Connection performance objects and counters on each server.
      • Log the monitored performance data in CSV file format on the server in the active log partition in the var/log/active/cm/log/ris/csv directory. The log file uses the following naming convention: PerfMon_<server>_<month>_<day>_<year>_<hour>_<minute>.csv; for example, PerfMon_172.19.240.80_06_15_2005_11_25.csv. Specify the polling rate. This rate specifies the rate at which performance data gets gathered and logged. You can configure the polling rate down to 5 seconds. Default polling rate equals 15 seconds.
      • View the log file in graphical format by using the Microsoft Windows performance tool or by using the Performance Log viewer in the RTMT.
      • Specify the maximum number of log files that will be stored on disk. Log files exceeding this limit get purged automatically by removal of the oldest log file. The default specifies 50 files.
      • Specify the rollover criteria of the log file based on the maximum size of the file in megabytes. The default value specifies 5 MB.
      • Collect the Cisco RIS Data Collector PerfMonLog log file by using the Trace & Log Central feature of the RTMT or Command Line Interface.

      The troubleshooting perfmon data-logging feature collects information from the following counters within the following perfmon objects.


      Note


      No Cisco Unity Connection counters get logged to the troubleshooting perfmon data log.


      • Database Change Notification Server Object
        • Clients
        • CNProcessed
        • QueueDelay
        • QueuedRequestsInDB
        • QueuedRequestsInMemory
      • Database Local DSN Object
        • CcmDbSpace_Used
        • CcmtempDbSpace_Used
        • CNDbSpace_Used
        • LocalDSN
        • RootDbSpace_Used
        • SharedMemory_Free
        • SharedMemory_Used
      • Enterprise Replication DBSpace Monitors Object
        • ERDbSpace_Used
        • ERSBDbSpace_Used
      • IP Object
        • In Receives
        • In HdrErrors
        • In UnknownProtos
        • In Discards
        • In Delivers
        • Out Requests
        • Out Discards
        • Reasm Reqds
        • Reasm Oks
        • Reasm Fails
        • Frag OKs
        • Frag Fails
        • Frag Creates
        • InOut Requests
      • Memory Object
        • % Page Usage
        • % VM Used
        • % Mem Used
        • Buffers Kbytes
        • Cached Kbytes
        • Free Kbytes
        • Free Swap Kbytes
        • HighFree
        • HighTotal
        • Low Total
        • Low Free
        • Page Faults Per Sec
        • Page Major Faults Per Sec
        • Pages
        • Pages Input
        • Pages Input Per Sec
        • Pages Output
        • Pages Output Per Sec
        • SlabCache
        • SwapCached
        • Shared Kbytes
        • Total Kbytes
        • Total Swap Kbytes
        • Total VM Kbytes
        • Used Kbytes
        • Used Swap Kbytes
        • Used VM Kbytes
      • Network Interface Object
        • Rx Bytes
        • Rx Packets
        • Rx Errors
        • Rx Dropped
        • Rx Multicast
        • Tx Bytes
        • Tx Packets
        • Tx Errors
        • Tx Dropped
        • Total Bytes
        • Total Packets
        • Tx QueueLen
      • Number of Replicates Created and State of Replication Object
        • Replicate_State
      • Partition Object
        • % CPU Time
        • %Used
        • Await Read Time
        • Await Time
        • Await Write Time
        • Queue Length
        • Read Bytes Per Sec
        • Total Mbytes
        • Used Mbytes
        • Write Bytes Per Sec
      • Process Object
        • % Memory Usage
        • Data Stack Size
        • Nice
        • PID
        • STime
        • % CPU Time
        • Page Fault Count
        • Process Status
        • Shared Memory Size
        • VmData
        • VmRSS
        • VmSize
        • Thread Count
        • Total CPU Time Used
      • Processor Object
        • Irq Percentage
        • Softirq Percentage
        • IOwait Percentage
        • User Percentage
        • Nice Percentage
        • System Percentage
        • Idle Percentage
        • %CPU Time
      • System Object
        • Allocated FDs
        • Freed FDs
        • Being Used FDs
        • Max FDs
        • Total Processes
        • Total Threads
        • Total CPU Time
      • TCP Object
        • Active Opens
        • Passive Opens
        • Attempt Fails
        • Estab Resets
        • Curr Estab
        • In Segs
        • Out Segs
        • Retrans Segs
        • InOut Segs
      • Thread Object—Troubleshooting Perfmon Data Logger only logs Cisco Unified Communications Manager threads.
        • %CPU Time
      • Cisco CallManager Object
        • CallManagerHeartBeat
        • CallsActive
        • CallsAttempted
        • CallsCompleted
        • InitializationState
        • RegisteredHardwarePhones
        • RegisteredMGCPGateway
      • Cisco SIP Stack Object
        • CCBsAllocated
        • SCBsAllocated
        • SIPHandlerSDLQueueSignalsPresent
      • Cisco CallManager System Performance Object
        • AverageExpectedDelay
        • CallsRejectedDueToThrottling
        • CodeRedEntryExit
        • CodeYellowEntryExit
        • QueueSignalsPresent 1-High
        • QueueSignalsPresent 2-Normal
        • QueueSignalsPresent 3-Low
        • QueueSignalsPresent 4-Lowest
        • QueueSignalsProcessed 1-High
        • QueueSignalsProcessed 2-Normal
        • QueueSignalsProcessed 3-Low
        • QueueSignalsProcessed 4-Lowest
        • QueueSignalsProcessed Total
        • SkinnyDevicesThrottled
        • ThrottlingSampleActivity
        • TotalCodeYellowEntry
      • Cisco TFTP Server Object
        • BuildAbortCount
        • BuildCount
        • BuildDeviceCount
        • BuildDialruleCount
        • BuildDuration
        • BuildSignCount
        • BuildSoftkeyCount
        • BuildUnitCount
        • ChangeNotifications
        • DeviceChangeNotifications
        • DialruleChangeNotifications
        • EncryptCount
        • GKFoundCount
        • GKNotFoundCount
        • HeartBeat
        • HttpConnectRequests
        • HttpRequests
        • HttpRequestsAborted
        • HttpRequestsNotFound
        • HttpRequestsOverflow
        • HttpRequestsProcessed
        • HttpServedFromDisk
        • LDFoundCount
        • LDNotFoundCount
        • MaxServingCount
        • Requests
        • RequestsAborted
        • RequestsInProgress
        • RequestsNotFound
        • RequestsOverflow
        • RequestsProcessed
        • SegmentsAcknowledged
        • SegmentsFromDisk
        • SegmentsSent
        • SEPFoundCount
        • SEPNotFoundCount
        • SIPFoundCount
        • SIPNotFoundCount
        • SoftkeyChangeNotifications
        • UnitChangeNotifications

      Predefined system objects

      RTMT displays information on predefined system objects in the monitoring pane.


      Tip


      The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds. If the collecting rate for the AMC (Alert Manager and Collector) service parameter changes, the polling rate in the precanned window also updates. In addition, the local time of the RTMT client application and not the backend server time, provides the basis for the time stamp in each chart.

      For more information on service parameters, refer to Cisco Unified Communications Manager Administration Guide or Cisco Unity Connection System Administration Guide.


      The following table provides information on the predefined objects that RTMT monitors.


      Tip


      To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart in which you are interested. Release the left mouse button when you have the selected area. RTMT updates the monitored view. To zoom out and reset the monitor to the initial default view, press the R key.


      Table 1 System Categories

      Category

      Description

      System Summary

      Displays information on Virtual Memory usage, CPU usage, Common Partition Usage, and the alert history log.

      To display information on predefined system objects, choose System > System Summary.

      Server

      • CPU and Memory—Displays information on CPU usage and Virtual memory usage for the server.To display information on CPU and Virtual memory usage, choose System > Server > CPU and Memory.To monitor CPU and memory usage for specific server, choose the server from the host drop-down list box.
      • Process—Displays information on the processes that are running on the server.To display information on processes running on the system, choose System > Server > Process. To monitor process usage for specific server, choose the server from the Host drop-down list box.
      • Disk Usage—Displays information on disk usage on the server.To display information on disk usage on the system, choose System > Server > Disk Usage. To monitor disk usage for specific server, choose the server from the host drop-down list box.
      • Critical Services—Displays the name of the critical service, the status (whether the service is up, down, activated, stopped by the administrator, starting, stopping, or in an unknown state), and the elapsed time during which the services have existed in a particular state for the server or for a particular server in a cluster (if applicable).To display information on critical services, choose System > Server > Critical Services, then click the applicable tab:
        • To display system critical services, click the System tab.
        • To display Cisco Unified Communications Manager critical services, click the CallManager tab.
        • To display Cisco Unity Connection critical services, click the Cisco Unity Connection tab.
        • To monitor critical services for specific server on the tab, choose the server from the host drop-down list box and click the critical services tab in which you are interested. If the critical service status indicates that the administrator stopped the service, the administrator performed a task that intentionally stopped the service; for example, the service stopped because the administrator backed up or restored Cisco Unified Communications Manager, performed an upgrade, stopped the service in Cisco Unified Serviceability or the Command Line Interface (CLI), and so on. If the critical service status displays as unknown state, the system cannot determine the state of the service.

      System summary monitoring

      The system summary in RTMT allows you to monitor important common information in a single monitoring pane. In system summary, you can view information on the following predefined object:

      • Virtual Memory usage
      • CPU usage
      • Common Partition Usage
      • Alert History Log

      Server status monitoring

      The Servers category monitors CPU and memory usage, processes, disk space usage, and critical services for the different applications on the server.

      The CPU and Memory monitor provide information about the CPU usage and Virtual memory usage on each server. For each CPU on a server, the information includes the percentage of time that each processor spends executing processes in different modes and operations (User, Nice, System, Idle, IRQ, SoftIRQ, and IOWait). The percentage of CPU equals the total time that is spent executing in all the different modes and operations excluding the Idle time. For memory, the information includes the Total, Used, Free, Shared, Buffers, Cached, Total Swap, Used Swap, and Free Swap memory in Kbytes, and the percentage of Virtual Memory in Use.

      The Processes monitor provides information about the processes that are running on the system. RTMT displays the following information for each process—process ID (PID), CPU percentage, Status, Shared Memory (KB), Nice (level), VmRSS (KB), VmSize (KB), VmData (KB), Thread Count, Page Fault Count, and Data Stack Size (KB).

      The disk usage monitoring category charts the percentage of disk usage for the common and swap partitions. It also displays the percentage of disk usage for each partition (Active, Boot, Common, Inactive, Swap, SharedMemory, Spare) in each host.


      Note


      If more than one logical disk drive is available in your system, the system stores CTI Manager traces in the 'spare' partition on the first logical disk and CiscoCallManager traces on the second logical disk. RTMT monitors the disk usage for the 'spare' partition in the Disk Usage window.


      The Critical Services monitoring category provides the name of the critical service, the status (whether the service is up, down, activated, stopped by the administrator, starting, stopping, or in an unknown state), and the elapsed time during which the services are up and running on the system.

      For a specific description of each state, see the following table.

      Table 2 Status of Critical Services

      Status of Critical Service

      Description

      starting

      The service currently exists in start mode, as indicated in the Critical Services pane and in Control Center in Cisco Unified Serviceability

      up

      The service currently runs, as indicated in the Critical Services pane and in Control Center in Cisco Unified Serviceability.

      stopping

      The service currently remains stopped, as indicated in the Critical Services pane and in Control Center in Cisco Unified Serviceability.

      down

      The service stopped running unexpectedly; that is, you did not perform a task that stopped the service. The Critical Services pane indicates that the service is down.

      The CriticalServiceDown alert gets generated when the service status equals down.

      stopped by Admin

      You performed a task that intentionally stopped the service; for example, the service stopped because you backed up or restored Cisco Unified Communications Manager, performed an upgrade, stopped the service in Cisco Unified Serviceability or the Command Line Interface (CLI), and so on.

      The Critical Services pane indicates the status.

      not activated

      The service does not exist in a currently activated status, as indicated in the Critical Services pane and in Service Activation in Cisco Unified Serviceability.

      unknown state

      The system cannot determine the state of the service, as indicated in the Critical Services pane.

      Server logs

      Every 5 minutes, the server data gets logged into the file as a single record. The system logs the data every 5 minutes for the following counters, based on the following calculation:

      • cpuUsage—Average of all the values that were collected in the last 5 minutes
      • MemoryInUse—Average of all the values that were collected in the last 5 minutes
      • DiskSpaceInUse—Average of all the values that were collected in the last 5 minutes for the active partition

      The Cisco AMC service logs the server data in csv format. The header of the log comprises the time zone information and a set of columns with the previous counters for a server. These sets of columns repeat for every server in a cluster, if applicable.

      The following file name format of the server log applies: ServerLog_MM_DD_YYYY_hh_mm.csv. The first line of each log file comprises the header.

      Predefined Cisco Unified Communications Manager objects

      RTMT displays information on predefined Cisco Unified Communications Manager objects in the monitoring pane when you select Communications Manager in the quick launch channel. The tool monitors the predefined objects on all servers in an cluster, if applicable.


      Tip


      The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds. If the collecting rate for the AMC (Alert Manager and Collector) service parameter changes, the polling rate in the precanned window also updates. In addition, the local time of the RTMT client application and not the backend server time, provides the basis for the time stamp in each chart.

      For more information on Service Parameters, refer to Cisco Unified Communications Manager Administration Guide or Cisco Unity Connection System Administration Guide.


      The following table provides information on the predefined object that RTMT monitors.


      Tip


      To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart in which you are interested. Release the left mouse button when you have the selected area. RTMT updates the monitored view. To zoom out and reset the monitor to the initial default view, press the R key.


      Table 3  Cisco Unified Communications Manager Categories

      Category

      Description

      CallManager Summary

      Displays registered phones, calls in progress, and active gateway ports and channels.

      To display information on predefined Cisco Unified Communications Manager objects, choose CallManager > CallManager Summary.

      Call Process

      • Call Activity—Displays the call activity on Cisco Unified Communications Manager, including calls completed, calls attempted, calls in progress, and logical partition total failures. This includes all servers in the cluster, if applicable.To display information on call activities, choose CallManager > Call Process > Call Activity.
      • Gateway Activity—Displays gateway activity on Cisco Unified Communications Manager, including active ports, ports in service, and calls completed. This includes all servers in the cluster, if applicable.To display information on gateway activities, choose CallManager > Call Process > Gateway Activity. Select the type of gateway interface from the Gateway Type drop-down box.
      • Trunk Activity—Displays the trunk activity on Cisco Unified Communications Manager, including calls in progress and calls completed. This includes all servers in the cluster, if applicable.To display information on trunk activities, choose CallManager > Call Process > Trunk Activity. Select the trunk type in the Trunk Type drop-down box.
      • SDL Queue—Displays SDL queue information, including number of signals in queue and number of processed signals.To display information on the SDL Queue, choose CallManager > Call Process > SDL Queue. Select the type from the SDL Queue Type drop-down list box.
      • SIP Activity—Displays SIP activity on Cisco Unified Communications Manager, including summary requests, summary responses, summary of failure responses in, summary of failure responses out, retry requests out, and retry responses out. This includes all servers in the cluster, if applicable.To display information on SIP activities, choose CallManager > Call Process > SIP Activity.
      • Session Trace—Displays all SIP message activity: specifically, the incoming and outgoing calls and sessions that pass through the Cisco Unified Communications Manager. Provides associated call flow diagram for each SIP transaction.To display information on Session Trace, choose CallManager > Call Process > Session Trace.

      Device

      Device Summary displays information on the Cisco Unified Communications Manager server, including the number of registered phone devices, registered gateway devices, and registered media resource devices. This includes all servers in the cluster, if applicable.

      Device Search displays cluster name and device types in a tree hierarchy and allows you to query for information on phones and devices.

      Phone Summary displays information on the Cisco Unified Communications Manager server, including the number of registered phones, registered SIP phones, registered SCCP phones, partially registered phones, and the number of failed registration attempts. This includes all servers in the cluster, if applicable.

      To display information on the number of registered phones, gateways, and media resource devices on Cisco Unified Communications Manager, choose CallManager > Device > Device Summary.

      Tip    To monitor other devices, you must perform additional configuration steps.

      Service

      • Cisco TFTP—Displays Cisco TFTP status on the Cisco Unified Communications Manager server, including total TFTP requests, total TFTP requests found, and total TFTP requests aborted. This includes all servers in the cluster, if applicable.To display information on the Cisco TFTP service, choose CallManager > Service > Cisco TFTP.
      • Heartbeat—Displays heartbeat information for the Cisco Unified Communications Manager, Cisco TFTP service.To display the heartbeat status of Cisco Unified Communications Manager servers, Cisco TFTP servers, choose CallManager > Service > Heartbeat.
      • Database Summary—Provides connection information for the server, such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, the number of devices that are queued for a device reset, the number of replicates that have been created, and the status of the replication.To display information on the database, choose CallManager > Service > Database Summary.

      CTI Manager

      Displays information on the devices and applications that interfaces with the CTI Manager.

      To display information on CTI Applications, choose CallManager > CTI > CTI Manager.

      To monitor specific CTI types, you must perform additional configuration steps. See topics related to monitoring CTI applications, devices, and lines.

      You cannot choose CTI Manager by using the menu bar. To monitor the number of open devices, lines, and CTI connections in a single window on Cisco Unified Communications Manager, see topics related to device monitoring.

      Intercompany Media Services

      • Routing—Displays the total number of Cisco Intercompany Media Engine routes maintained by Cisco Unified Communications Manager.To display information on call activities, choose CallManager > Intercompany Media Services > Routing.
      • Call Activities—Displays the Cisco Intercompany Media Engine call activity, including the number of calls that were accepted, busy, no answer, and failed.To display information on call activities, choose CallManager > Intercompany Media Services > Call Activities.

      Cisco Unified Communications Manager summary view

      In a single monitoring pane, RTMT allows you to monitor information about a Cisco Unified Communications Manager server or about all servers in a cluster (if applicable). In the CallManager Summary window, you can view information on the following predefined object:

      • Registered Phones
      • Calls in Progress
      • Active Gateway, Ports & Channels

      Call-processing activity monitoring

      The Call Process monitoring category monitors the following items:

      • Call Activity—You can monitor the number of calls that were attempted, calls that were completed, calls in progress, and logical partition total failures for a particular server or for an entire cluster (if applicable).
      • Gateway Activity—You can monitor gateway activity for each gateway type. Gateway activity monitoring includes the number of active ports, the number of ports in service, and the number of calls that were completed for each gateway type for a particular server or for an entire cluster (if applicable).
      • Trunk Activity—The system monitors trunk activity by trunk type for a particular server or for an entire cluster (if applicable). Trunk activity monitoring includes the number of calls in progress and the number of calls that were completed for a particular trunk type.
      • SDL Queue—SDL queue monitoring monitors the number of signals in the SDL queue and the number of signals that were processed for a particular signal distribution layer (SDL) queue type. The SDL queue types comprise high, normal, low, and lowest queue. You can monitor the SDL queue for a particular server or for an entire cluster (if applicable).
      • SIP Activity—The system displays a summary of SIP requests, SIP responses, total number of failed incoming responses (4xx, 5xx, and 6xx), total number of failed outgoing responses (4xx, 5xx, and 6xx), number of retry requests, and number of retry responses.
      • Session Trace—You can search or trace the calls based on the following criteria: Calling Number/URI, Called Number/URI, Start Time, and Duration. RTMT downloads the Call Log file(s) that include the Start Time and Duration, search for the matching calls, list the matching call records, and provide the Call Flow Diagram.

      The following table provides information about the call processing objects that RTMT monitors, the alert, thresholds, and defaults. For information on Cisco Unified Communications Manager call activity daily reports, refer to Cisco Unified Serviceability Administration Guide.

      Table 4 Call Processing Category

      Monitored Objects (displayed)

      Alert/Threshold/Default

      CallsAttempted, CallsCompleted, CallsInProgress, and Logical Partition Failures Total for each server and cluster (if applicable).

      N/A

      CallsAttempted, CallsCompleted, and CallsInProgress of each type of MGCP FXS/FXO/PRI/T1CAS/H.323 gateway, as well as SIP and H.323 Trunks for each server and cluster (if applicable).

      N/A

      Channel/Port Status of each MGCP FXS/FXO/PRI/T1CAS gateway.

      N/A

      SDL Queue activity on each server.

      N/A

      MGCP FXS Gateway—Number of In-Service and Active ports for each server and cluster (if applicable).

      Route-List exhausted

      MGCP FXO Gateway—Number of In-Service and Active ports for each server and cluster (if applicable).

      Route-List exhausted

      MGCP PRI Gateway—Number of In-Service and Active channels for each server and cluster (if applicable).

      • D-Channel out of service
      • Route List exhausted

      MGCP T1CAS Gateway—Number of In-Service and Active ports for each server and cluster (if applicable).

      Route List exhausted

      Call-processing logs

      The system accumulates call-processing data in the memory whenever RTMT calls the LogCall API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

      The system logs data every 5 minutes for the following counters on the basis of the following calculation:

      • cmCallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • cmCallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • cmCallsInProgress—Average of all the values that were collected in last 5 minutes
      • gwMGCP_FXS_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwMGCP_FXO_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwMGCP_PRI_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwMGCP_T1_CAS_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwH323_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwH323_CallsInProgress—Average of all the values that were collected in last 5 minutes
      • gwH323_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • trunkH323_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • trunkH323_CallsInProgress—Average of all the values collected in last 5 minutes
      • trunkH323_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • trunkSIP_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • trunkSIP_CallsInProgress—Average of all the values that were collected in last 5 minutes
      • trunkSIP_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
      • gwMGCP_FXS_PortsInService—Average of all the values that were collected in last 5 minutes
      • gwMGCP_FXO_PortsInService—Average of all the values that were collected in lasts 5 minutes
      • gwMGCP_PRI_SpansInService—Average of all the values that were collected in last 5 minutes
      • gwMGCP_T1_CAS_SpansInService—Average of all the values that were collected in last 5 minutes
      • gwMGCP_FXS_ActivePorts—Average of all the values that were collected in last 5 minutes
      • gwMGCP_FXO_ActivePorts—Average of all the values that were collected in last 5 minutes
      • gwMGCP_PRI_ActiveChannels—Average of all the values that were collected in last 5 minutes
      • gwMGCP_T1_CAS_ActiveChannels—Average of all the values that were collected in last 5 minutes

      The AMC service logs the call data in windows Performance tool-compatible csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for the server. These sets of columns repeat for every server in a cluster, if applicable.

      The following file name format of the Call Log applies: CallLog_MM_DD_YYYY_hh_mm.csv.

      The first line of each log file comprises the header.

      Perform session trace

      Cisco Unified Communications Manager captures and logs all SIP message activities, which comprise the incoming and outgoing calls or sessions that pass through it. Cisco Unified Communications Manager stores the messages on a per-transaction basis in a new Call Log file, which can be downloaded through RTMT for post-processing activity.

      RTMT users can search or trace the calls based on the following criteria:

      • Calling Number/URI
      • Called Number/URI
      • Start Time
      • Duration

      RTMT downloads the Call Log file that includes the Start Time and Duration. The tool searches for the matching calls, lists the matching call records, and provides the SIP message Call Flow Diagram.

      You can also save the call logs on your local system. Based on the saved call logs, RTMT can search for the matching calls, list the matching records, and provide SIP Message Call Flow Diagrams. For more information about tracing the calls based on uploaded call logs, see

      Open from local disk.
      Before You Begin

      Perform the following task:

      • Use the enterprise parameter, Enable Call Trace Log, to enable or disable Call Tracing. For more information on configuring enterprise parameters, refer to the Cisco Unified Communications Manager Administration Guide.
      • The default value for maximum number of Call Trace log files specifies 2000 and the default value for maximum Call Trace log file size specifies 2 MB.

      Scenarios while uninstalling RTMT

      Consider the following scenarios, while uninstalling RTMT:

      1. User saves the call flow diagram files in a folder (created by the user under user.home directory)—All the files in user.home are deleted except the newly created folder and the user.home directory.
      2. User saves the call flow diagram files in a folder (created during RTMT installation) under user.home directory—All the files in user.home are deleted including the user.home directory.
      3. User directly saves the call flow diagram files under user.home directory—All the files in user.home are deleted except the newly created files and the user.home directory.
      4. User saves the call flow diagram files in a folder which is outside user.home directory—user.home and its contents are removed. The folder created by the user is not deleted.

      Monitor real-time data

      The following procedure describes how you can monitor real-time data using RTMT.

      Procedure
        Step 1   To display information on Session Trace, from the RTMT menus, choose CallManager > Call Process > Session Trace Log View > Real Time Data.

        The Real Time Data screen displays.

        Step 2   Enter the search criteria and Click Run.
        Note   

        You can search calls based on the following criteria: Calling Number/URI, Called Number/URI, Start Time, and Duration. The search applies to the entire Unified CM cluster, not just the local node. If any node fails to collect the trace files, the system displays an error message in the bottom panel and pops up the message prompt to the user.

        Click Yes to ignore the error and generate the table, based on the input.

        Note   

        In Calling Number/URI, Called Number/URI, you can use wild character "*" to match any number of characters. For example, a search for 123* fetches numbers like "123", "123456", "123*", "1234", etc.

        If you want to search for numbers with a "*" in them, use "\*". For example, to search for a Called Number like 12*45, enter 12\*45 in the search box.

        If matching calls are found, the Matching Call pane displays Start Time, Calling DN, Original Called DN, Final Called DN, Calling Device Name, Called Device Name and Termination Cause Code.

        Note   

        The Called Party Trace Feature adds the Calling Device Name and Called Device Name fields.

        • Calling and Called device names will not be available for failed calls such as calls made to unreachable destinations.
        • The Termination Cause Code helps to identify the failed calls, and provides the reason for the failure of the calls. The Termination Cause Code is displayed in parenthesis followed by description.
        • If the call is in progress or if the call trace logging is turned off after the call, the Termination Cause Code column remains blank.
        Note   

        If cause code description is missing or if you want more information on the Termination Cause Codes, refer the CDR cause codes in Cisco Unified Call Details Records Administration Guide.

        After the call records are displayed in the Matching Calls pane, you can trace calls by following the steps described in


        Open from local disk

        The following procedure describes the steps to monitor session trace data from the logs saved on your local disk:

        Procedure
            Command or Action Purpose
          Step 1 From the RTMT menus, choose CallManager > Call Process > Session Trace Log View > Open from Local Disk.  

          The Open from Local Disk screen appears.

           
          Step 2 In the File Location field, specify the directory where the call log files are saved on your local disk. You can click Browse to specify the directory path.   
          Step 3 Check the Enable Time Based Search check box to view call records for a specific duration. If you check this check box, you can specify the duration in Duration field. If you do not check this check box, you will not be able to specify the duration. In such cases, all the calls from the specified Start Time that are present in the saved log files will be displayed.   
          Step 4 Enter the search criteria and click Run. 
          Note   

          In Calling Number/URI, Called Number/URI, you can use the wildcard character ‘*’ to match any number of characters. For example, a search for 123* fetches numbers like 123, 1234, 123456, 123*, and so on.

          If you want to search for numbers with a ‘*’ in them, use ‘\*’. For example, to search for a Called Number like 12*45, enter 12\*45 in the search box.

          If matching calls are found, the Matching Call pane displays Start Time, Calling DN, Original Called DN, Final Called DN, Calling Device Name, Called Device Name, and Termination Cause Code.

          Note   

          The Called Party Trace Feature adds the Calling Device Name and Called Device Name fields.

          Note   

          If cause code description is missing or if you want more information about the Termination Cause Codes, refer the CDR cause codes in Cisco Unified Call Details Records Administration Guide.

           

          Trace calls

          This section describes the procedure to trace call records displayed as per the specified search criteria.


          Note


          Use this procedure in conjunction with Monitor real-time data and Open from local disk.


          Procedure
            Step 1   Select a call (a row) to trace.

            By default, Include SIP Message check box is selected to view the associated SIP protocol messages or call transactions.

            Step 2   To generate the SIP Message Call Flow Diagram, click Trace Call. If you want to stop the generation of the session information, click Cancel on the progress window.

            The Analyze Call Diagram window displays the corresponding SIP messages in the Call Flow Diagram.

            Step 3   Click the tabs that you want to view. The following tabs are available:
            1. Call Flow Diagram—Displays the corresponding SIP messages in the Call Flow Diagram.
            2. Log File—Displays the entire log file.
            3. SIP Message—Appears only when the Include SIP Message check box is checked. Displays the actual SIP message that gets logged into the SDI log file.
            Step 4   The following table lists the details that are displayed, when you move your mouse over the SIP messages in the Call Flow Diagram.

            Field

            Description

            Sender

            Displays the IP address of the originating call.

            GUID

            Displays the SIP call ID.

            Message Label

            Displays the message type for the corresponding SIP message onto which you move your mouse; for example, 200 OK, or180 Ringing.

            Receiver

            Displays the IP address of the destination call.

            MAC_ADDRESS

            Displays the name of the device.

            Message Tag

            Displays the sequence number to match the actual messages in the SDI Trace file.

            MSG_TYPE

            Displays the type of message.

            Correlation ID

            Displays the Correlation ID.

            Timestamp

            Displays the server time at which the call operation (call setup/split/join/release) happens.

            Detailed SIP Message—Appears only when the Include SIP Message check box is checked. Displays the actual SIP message that gets logged into the SDL log file.

            Message in Log File—Displays the log file which contains the message.

            To view the SIP messages that get logged into the SDL log file, do the following:

            • check the Enable SIP Call Processing Trace check box in the Trace Configuration window of Cisco Unified Serviceability (Trace > Configuration). See Cisco Unified Serviceability Administration Guide for more information.
            • set the trace level to any one of the following—State Transition, Significant, Arbitrary or Detailed.
            Note   

            If you are monitoring the session trace data from the logs stored on your local disk, the detailed SIP message will be available only if the SDL/SDI logs are present in the parent directory of the call logs.

            Step 5   Click Save.

            If you are monitoring real-time data, the Call Flow Diagram gets saved as index.html in the specified folder along with the SDL files which contain the SIP messages. You can email the files to the Technical Assistance Center (TAC). For more information on monitoring real-time data, see Monitor real-time data. The SIP messages in the saved Call Flow Diagram appear as hyperlinks. When you click on a SIP message, the detailed SIP message along with the following details is displayed in a new window.

            Field

            Description

            Sender

            Displays the IP address of the originating call.

            GUID

            Displays the SIP call ID.

            Message Label

            Displays the message type for the corresponding SIP message onto which you move your mouse; for example, 200 OK, or180 Ringing.

            Receiver

            Displays the IP address of the destination call.

            MAC_ADDRESS

            Displays the name of the device.

            Message Tag

            Displays the sequence number to match the actual messages in the SDI Trace file.

            MSG_TYPE

            Displays the type of message.

            Correlation ID

            Displays the Correlation ID.

            Timestamp

            Displays the server time at which the call operation (call setup/split/join/release) happens.

            If you open logs for Cisco Unified Communications Manager 8.5 or 8.6 using Open from Local Disk option and save the ladder diagram , the SIP messages, the SDI log files that contain the SIP messages and SDL Log files for a duration of from 5 minutes before the start of the call to 5 minutes after the start of the call will be saved. If you save logs from Cisco Unified Communications Manager 9.0 or later, the SDL log files that contain the call details are saved along with index.html and the SIP messages. For more information about monitoring the session trace data from the logs saved to your local disk, see Open from local disk.

            Note   

            If the files are zipped, extract the zipped files to a local folder and open them to view the images.

            You can do the following:

            1. To view the online help, click Help.
            2. To exit the Analyze Call Diagram screen, click Close.
            3. To navigate to the previous page, click Previous Messages.
            4. To navigate to the next page, click Next Messages.
              Note   

              Previous Messages or Next Messages is enabled only when the message size exceeds a threshold.

            The Session Manager logs the call data in new log files. These new log files are located in the following folder: /var/log/active/cm/trace/ccm/calllogs/.

            The Call Log name has the following file name pattern: calllogs_dddddddd.txt.gz.

            Detailed SIP messages are logged into SDI traces.

            The Call Logs include the following message types:

            • Call Control—Writes call information at call setup, split, join and release.
              Timestamp|MessageType (CC)|Operation (SETUP/SPLI/JOIN/RELEASE)|CI for one leg (aCI)|CI for other leg (bCI)|calling DN|Orig Called DN|Final Called DN
            • Device Layer—Writes metadata information that relates to message from or to the device.
              Timestamp|MessageType (SIPL/SIPT)|My leg CI|Protocol(tcp/ucp)|Direction (IN/OUT)|local ip|local port|device name|device ip|device port|Correlation id|Message Tag|SIP Call ID|SIP method

            The following limitations apply when the Call Flow Diagram gets generated:

            • Search does not show incomplete calls. Example: When the user picks up the handset and hangs up without dialing the complete DN, it will not be listed in the search results.
            • The Call Flow Diagram does not show some SIP messages in the following scenarios:
              • Conference calls involving more than three parties.
              • A call leg is used to invoke a feature alone.
              Example: Phone B and Phone C are in the same pickup group.
              1. User A calls Phone B.
              2. User C lifts up the Phone C handset.
              3. User C presses the PickUp softkey to pickup the call.

            SIP messages exchanged in Step b are not displayed in the Call Flow Diagram

            In these cases, a RELEASE message is logged in the call logs without a corresponding SETUP message.


            Services monitoring

            The Service monitoring category monitors the activities of Cisco TFTP requests, database activities, and heartbeat of the server or of different servers in a cluster (if applicable).

            The Cisco TFTP service builds and serves files that are consistent with the trivial file transfer protocol, which is a simplified version of the File Transfer Protocol (FTP). Cisco TFTP builds configuration files and serves embedded component executables, ringer files, and device configuration files. You can view the total Cisco TFTP requests, requests not found, and requests that were aborted.

            The tool (RTMT) monitors the heartbeat of Cisco Unified Communications Manager and Cisco TFTP services for the server or for different servers in a cluster (if applicable). The heartbeat acts as an indicator of the life of whatever it is monitoring. When the heartbeat is lost, a blinking icon appears in the lower, right corner of the RTMT window. To find when the heartbeat loss was detected, click the blinking icon. An email can notify you of the heartbeat loss, if you configure the system to do so.

            The database summary provides connection information for the server or for each server in a cluster (if applicable), such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, the number of devices that are queued for a device reset, replicates created, and replication status.

            The following table provides information about the service objects that RTMT monitors, the alert, thresholds, and defaults. For information on daily reports for CTI and Cisco TFTP usage statistics, refer to Cisco Unified Serviceability Administration Guide.

            Table 5 Services Category

            Monitored Objects (displayed)

            Alert/Threshold/Default

            Number of open devices, lines, CTI connections, and active Cisco Unified Communications Manager links for each CTI Manager.

            N/A

            TotalTftpRequests and TotalTftpRequestsAborted for each Cisco TFTP server.

            N/A

            Connection and replication status for each Directory server.

            • Connection failed.
            • Replication failed.

            Heartbeat rate for each Cisco CallManager, Cisco TFTP services.

            • Cisco Unified Communications Manager heartbeat rate specifies <0.x. Default specifies 0.5.
            • Cisco TFTP heartbeat rate specifies <0.x. Default specifies 0.5.

            Service logs

            The service data accumulates in the memory whenever RTMT calls the LogService API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

            The system logs data every 5 minutes for the following counters, based on the following calculation:

            • ctiOpenDevices—Average of all the values that were collected in last 5 minutes
            • ctiLines—Average of all the values that were collected in last 5 minutes
            • ctiConnections—Average of all the values that were collected in last 5 minutes
            • ctiActiveCMLinks—Average of all the values that were collected in last 5 minutes
            • tftpRequests—Cumulative (difference between last collected value and the first collected value in last 5 minutes)
            • tftpAbortedRequests—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

            The AMC service logs the service data in csv format. The header of the log comprises the time zone information and a set of columns with the counters that were previously listed for a server. These sets of columns repeat for every server in a cluster, if applicable.

            The following file name format of the Service Log applies: ServiceLog_MM_DD_YYYY_hh_mm.csv.

            The first line of each log comprises the header.

            Device monitoring

            The Device monitoring category provides a summary of devices, device search capability, and a summary of phones.

            The following table provides information about the device objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those devices. For information on daily reports on number of registered devices, refer to Cisco Unified Serviceability Administration Guide.

            Table 6 Devices Category

            Monitored Objects (displayed)

            Alert/Threshold/Default

            Number of registered phones for each server or for all servers in a cluster (if applicable).

            Total number of registered phones drops by X% in consecutive polls. Default specifies 10%.

            Number of registered gateways on each server or for all servers in a cluster (if applicable).

            For Cisco Unified Communications Manager:

            • (Warning) Clusterwide total number of registered gateways decreased in consecutive polls.
            • (Informational) Clusterwide total number of registered gateways increased in consecutive polls.

            For Cisco Business Edition 5000:

            • (Warning) Total number of registered gateways decreased in consecutive polls.
            • (Informational) Total number of registered gateways increased in consecutive polls.

            Number of registered media devices on each server or for all servers in a cluster (if applicable).

            For Cisco Unified Communications Manager:

            • (Warning) Clusterwide total number of registered media devices decreased in consecutive polls.
            • (Informational) Clusterwide total number of registered media devices increased in consecutive polls.
            • Media List exhausted.

            For Cisco Business Edition 5000:

            • (Warning) Total number of registered media devices decreased in consecutive polls.
            • (Informational) Total number of registered media devices increased in consecutive polls.
            • Media List exhausted.

            The Device Search menu comprises the following items on which you can search: phones, gateway devices, H.323 devices, CTI devices, voice-messaging devices, media resources, hunt lists, and SIP trunks.

            You can search on any device in the Cisco Unified Communications Manager system and choose the status of the devices, including registered, unregistered, rejected, any status, and devices that are only configured in the database. You can also search by any model, or a specific device model, and set up criteria that include several different attributes. Within the phone search, you can also search on the basis of phone protocol.

            RTMT queries RIS to find the matching device. Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

            If you have Cisco Unified Communications Manager clusters and you search for a device by choosing the any status option, RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the RIS database for all specified Cisco Unified Communications Manager servers for a period of time. As a result, you may see multiple entries of a device with multiple statuses (Registered, Unregistered, and so on) in RTMT.

            When you see multiple entries of a device, the current status of the device reflects the entry that has the latest time stamp. By configuring the RIS Unused Cisco CallManager Device Store Period service parameter for the Cisco RIS Data Collector service in Cisco Unified Communications Manager Administration, you can configure the period of time that the RIS database keeps information on unregistered or rejected device. Refer to Cisco Unified Communications Manager Administration Guide for more information on configuring service parameter.


            Tip


            To find the matching item, RTMT requires that you activate the Cisco RIS Data Collector service in the Service Activation window.


            Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

            The phone summary provides information on the number of registered phones, phones that are running SIP, phones that are running SCCP, partially registered phones, and the number of failed registration attempts.

            Device logs

            The device data accumulates in the memory whenever RTMT calls the LogDevice API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

            The data gets logged every 5 minutes for the following counters based on the following calculation:

            • gatewayDevicesFXS—Average of all the values that were collected in last 5 minutes
            • gatewayDevicesFXO—Average of all the values that were collected in last 5 minutes
            • gatewayDevicesPRI—Average of all the values that were collected in last 5 minutes
            • gatewayDevicesT1—Average of all the values that were collected in last 5 minutes
            • gatewayDevicesH323—Average of all the values that were collected in last 5 minutes

            The AMC service logs the device data in csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for a server. These sets of columns repeat for every server in a cluster, if applicable.

            The following file name format of the Device Log applies: DeviceLog_MM_DD_YYYY_hh_mm.csv.

            The first line of each log file comprises the header.

            Device monitoring

            This section contains information about device monitoring.

            Find specific devices to monitor

            By performing the following procedure, you can monitor data for the following device types:

            • Phones
            • Gateway Devices
            • H.323 Devices
            • CTI Devices
            • Voice Mail Devices
            • Media Resources
            • Hunt List
            • SIP Trunk
            Procedure
              Step 1   Perform one of the following tasks:
              1. On the Quick Launch Channel, do the following:
                1. Click CallManager.
                2. In the tree hierarchy, double-click Device.
                3. Click the Device Search icon.
              2. Choose CallManager > Device > Device Search > Open Device Search and select the device type; for example, Phone, Gateway, Hunt List, and so on. A device selection window displays where you enter the search criteria. Go to Step 4.

                The Device Search window displays the cluster names (if applicable) and tree hierarchy that lists all device types that you can monitor.

                Tip   

                After you display the Device Search or CTI Search panes, you can right-click a device type and choose CCMAdmin to go to Cisco Unified Communications Manager Administration.

              Step 2   To find all devices or to view a complete list of device models from which you can choose, right-click the cluster name and choose Monitor.
              Step 3   To monitor a specific device type, right-click or double-click the device type from the tree hierarchy.
              Tip   

              If you right-click the device type, you must choose Monitor for the device selection window to display.

              Step 4   In the Select device with status window, click the radio button that applies.
              Step 5   In the drop-down list box next to the radio button that you clicked, choose Any CallManager or a specific Cisco Unified Communications Manager server for which you want the device information to display.
              Tip   

              In the remaining steps, you can choose the < Back, Next >, Finish, or Cancel buttons.

              Step 6   Click the Next > button.
              Step 7   In the Select Device with Download Status pane, click the radio button that applies, and click Next.
              Step 8   In the Search by device model pane, click the radio button that applies.
              Tip   

              If you chose Device Model, choose the device type for which you want the device information to display.

              Step 9   Click Next.
              Step 10   In the Search with name pane, click the radio button that applies and enter the appropriate information in the corresponding fields, if required.
              Tip   

              If you enter the IPv6 address, the IP Subnet does not apply. Cisco Business Edition 5000 does not support IPv6.

              Step 11   Click Next.
              Step 12   In the Monitor following attributes pane, check one or all of the search attributes.
              Tip   

              If you check the Ipv6Address check box, be aware that Cisco Business Edition 5000 does not support IPv6.

              Step 13   Click Finish.
              Tip   

              Some devices may not provide information for all search criteria. For example, if you select to monitor a phone for active load, inactive load, download status, or download reason, the download status results display Unknown for phone models that cannot provide this information.


              View phone information

              You can view information about phones that display in the RTMT device monitoring pane. This section describes how to view phone information.

              Procedure
                Step 1   Find and display the phone in the RTMT device monitoring pane.
                Step 2   Perform one of the following tasks:
                1. Right-click the phone for which you want information to display and choose Open.
                2. Click the phone and choose Device > Open.

                  The Device Information window displays.

                Step 3   In the Select Device with Status pane, click the radio button that applies.
                Step 4   In the drop-down list box next to the radio button that you clicked, choose Any CallManager or a specific Cisco Unified Communications Manager server for which you want the device information to display.
                Step 5   In the Search By Device Model pane, choose the phone protocol that you want to display.
                Step 6   Click the Any Model or Device Model radio button.

                If you click the Device Model radio button, choose a particular phone model that you want to display.

                Step 7   Click Next.
                Step 8   In the Search With Name pane, click the radio button that applies and enter the appropriate information in the corresponding fields.
                Step 9   In the Monitor following attributes pane, check one or all of the search attributes.
                Step 10   Click Finish.

                The Device Information window displays. For more information on the device, choose any field that displays in the left pane of the window.


                View device properties

                You can view the properties of devices that display in the RTMT device monitoring pane. This section describes how to view device properties.

                Procedure
                  Step 1   Find and display the device in the RTMT device monitoring pane.
                  Step 2   Perform one of the following tasks:
                  1. Right-click the device for which you want property information and choose Properties.
                  2. Click the device for which you want property information and choose Device > Properties.
                  Step 3   To display the device description information, click the Description tab.
                  Step 4   To display other device information, click the Other Info tab.

                  Set up polling rate for devices and performance monitoring counters

                  Cisco Unified Communications Manager polls counters, devices, and gateway ports to gather status information. In the RTMT monitoring pane, you configure the polling intervals for the performance monitoring counters and devices.


                  Note


                  High-frequency polling rate may adversely affect Cisco Unified Communications Manager performance. The minimum polling rate for monitoring a performance counter in chart view specifies 5 seconds; the minimum rate for monitoring a performance counter in table view specifies 1 second. The default value for both specifies 10 seconds.



                  Note


                  The default value for devices specifies 10 minutes.


                  Perform the following procedure to update the polling rate:

                  Procedure
                    Step 1   Display the device or performance monitoring counter in the RTMT monitoring pane.
                    Step 2   Click the device and choose Edit > Polling Rate.
                    Step 3   In the Polling Interval pane, specify the time that you want to use.
                    Step 4   Click OK.

                    CTI application, device, and line monitoring

                    The CTI category monitors CTI Manager activities and provides CTI search capability. With CTI Manager, you can monitor the number of open devices, lines, and CTI connections.

                    You can specify criteria for the CTI applications, devices, and lines that include CTI status, device name, application pattern, and attributes.


                    Tip


                    To find the matching item, RTMT requires that you activate the Cisco RIS Data Collector service in the Service Activation window in Cisco Unified Serviceability.


                    Results display in a table with a row for each matched device, a column for each of the specified attributes, and a timestamp of the device that has been opened/closed and the application that controls the device media.

                    View CTI Manager information

                    To display a chart of open devices, lines, and CTI connections for each server or for each server in a cluster (if applicable), click CallManager in the quick launch channel; double-click CTI, and then click the CTI Manager icon.

                    Find CTI applications to monitor

                    Perform the following procedure to find specific CTI applications to monitor:

                    Procedure
                      Step 1   Perform one of the following tasks:
                      1. On the Quick Launch Channel
                        1. Click CallManager.
                        2. In the tree hierarchy, double-click CTI.
                        3. Click the CTI Search icon.
                      2. Choose CallManager > CTI > CTI Search > CTI Applications. The selection window displays where you can enter the search criteria.
                      Step 2   From the CTI Manager drop-down list box, choose the CTI Manager that you want to monitor.
                      Step 3   From the Applications Status drop-down list box, choose the application status.
                      Step 4   Click Next.
                      Step 5   In the Application Pattern pane, click the radio button that applies.
                      Step 6   Enter the information in the field for the radio button that you clicked; for example, if you clicked the IP Subnet radio button, enter the IP address and the subnet mask in the field.
                      Tip   

                      If you enter the IPv6 address, the IP Subnet does not apply. IPv6 support does not apply to Cisco Business Edition 5000.

                      Step 7   Click Next.
                      Step 8   In the Monitor following attributes window, check one or all of the check boxes for the attributes that you want to monitor.
                      Step 9   Click Finish.

                      The applications monitoring pane displays the information that you chose.


                      Find CTI devices to monitor

                      Perform the following procedure to find specific CTI devices to monitor.

                      Procedure
                        Step 1   Perform one of the following tasks:
                        1. On the Quick Launch Channel
                          1. Click CallManager.
                          2. In the tree hierarchy, double-click CTI.
                          3. Click the CTI Search icon.
                        2. Choose CallManager > CTI > CTI Search > CTI Devices. The selection window displays where you can enter the search criteria. Go to Step 2.
                          Tip   

                          If you right-click the option, choose Monitor.

                        Step 2   From the CTI Manager drop-down list box, choose the CTI Manager that you want to monitor.
                        Step 3   From the Devices Status drop-down list box, choose the device status.
                        Step 4   In the Devices pane, click the radio button that applies.
                        Tip   

                        If you chose Device Name, enter the device name in the field.

                        Step 5   Click Next.
                        Step 6   In the Application Pattern window, click the radio button that applies.
                        Step 7   Enter the information in the field for the radio button that you clicked; for example, if you clicked IP Subnet, enter the IP address and subnet mask in the field.
                        Tip   

                        If you enter the IPv6 address, the IP Subnet does not apply. IPv6 support does not apply to Cisco Business Edition 5000

                        Step 8   Click Next.
                        Step 9   In the Monitor following attributes window, check one or all check boxes for the attributes that you want to monitor.
                        Step 10   Click Finish.

                        The devices monitoring pane displays the information that you chose.


                        Find CTI lines to monitor

                        Perform the following procedure to find specific CTI lines to monitor.

                        Procedure
                          Step 1   Perform one of the following tasks:
                          1. On the Quick Launch Channel
                            1. Click CallManager.
                            2. In the tree hierarchy, double-click CTI.
                            3. Click the CTI Search icon.
                          2. Choose CallManager > CTI > CTI Search > CTI Lines. The selection window displays where you can enter the search criteria. Go to Step 2.
                            Tip   

                            If you right-click the option, choose Monitor.

                          Step 2   From the CTI Manager & Status drop-down list box, choose the CTI manager that you want to monitor.
                          Step 3   From the Lines Status drop-down list box, choose the status.
                          Step 4   In the Devices pane, click the radio button that applies.
                          Tip   

                          If you chose Device Name, enter the device name in the field.

                          Step 5   In the Lines pane, click the radio button that applies:
                          Note   

                          If you chose Directory Number, enter the directory number in the field.

                          Step 6   Click Next.
                          Step 7   In the Application Pattern pane, click the radio buttons apply:
                          Step 8   Enter the information in the field for the radio button that you clicked; for example, if you clicked IP Subnet, enter the IP address and subnet mask in the field.
                          Tip   

                          If you enter the IPv6 address, the IP Subnet does not apply. IPv6 support does not apply to Cisco Business Edition 5000.

                          Step 9   Click Next.
                          Step 10   In the Monitor following attributes window, check one or all check boxes for the attributes that you want to monitor.
                          Step 11   Click Finish.

                          The lines monitoring pane displays the information that you chose.


                          View application information

                          You can view the application information for selected devices such as the Cisco Unified IP Phone, CTI port, and CTI route point. This section describes how to view application information.

                          Procedure
                            Step 1   Find and display the devices in the RTMT monitoring pane.
                            Step 2   Perform one of the following tasks:
                            1. Right-click the device for which you want application information; for example, CTI; then, choose App Info.
                            2. Click the device for which you want application information and choose Device > App Info.

                              The Application Information window displays the CTI manager server name, application ID, user ID, application IP address, application status, app time stamp, device time stamp, device name, and CTI device open status.

                            Step 3   To view updated information, click Refresh. To close the window, click OK.

                            Access learned pattern and SAF forwarder reports for Call Control Discovery

                            Learned pattern reports and SAF forwarder reports support the call control discovery feature. When you configure the call control discovery feature, Cisco Unified Communications Manager advertises itself and its hosted DN patterns to other remote call-control entities that use the SAF network. Likewise, these remote call-control entities advertise their hosted DN patterns, which Cisco Unified Communications Manager can learn and insert in digit analysis. For more information on the call control discovery feature, refer to the "Call Control Discovery" chapter in the Cisco Unified Communications Manager Features and Services Guide.

                            Learned Pattern reports include such information as learned pattern name, time stamp, and reachability status for the pattern. See the following table.


                            Note


                            The learned pattern may be repeated in the report because the learned pattern may be coming from a different source; for example, it may be coming from a different IP address.


                            Table 7 Data from Learned Pattern Report

                            Column

                            Description

                            Pattern

                            Displays the name of the learned pattern from the remote call-control entity.

                            TimeStamp

                            Displays the date and time that the local Cisco Unified Communications Manager marked the pattern as a learned pattern.

                            Status

                            Indicates whether the learned pattern was reachable or unreachable

                            Protocol

                            Displays the protocol for the SAF-enabled trunk that was used for the outgoing call to the learned pattern; if the remote call-control entity has QSIG tunneling configured for the SAF-enabled trunk, the data indicates that QSIG tunneling was used; for example, EMCA is listed along with H.323 in this column.

                            AgentID

                            Displays the name of the remote call-control entity that advertised the learned pattern

                            IP Address

                            Displays the IP address for the call control entity that advertised the learned pattern; Displays the port number that the call-control entity uses to listen for the call.

                            ToDID

                            Displays the PSTN failover configuration for the learned pattern.

                            CUCMNodeId

                            Displays the ID from the local Cisco Unified Communications Manager node.

                            SAF Forwarder reports display information such as authentication status and registration status of SAF forwarders. See the following table.

                            Table 8 Data from SAF Forwarder Report

                            Column

                            Description

                            Name

                            Displays the name of the SAF forwarder that you configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration.

                            Description

                            Displays the description for the SAF forwarder that you configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration. If None displays, you did not enter a description for the SAF forwarder.

                            IP Address

                            Displays the IP address for the SAF forwarder, as configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration.

                            Port

                            Indicates the port number that Cisco Unified Communications Manager uses to connect to the SAF forwarder; by default, Cisco Unified Communications Manager uses 5050.

                            Type

                            Indicates whether the SAF forwarder is classified as the primary or backup SAF forwarder.

                            Connection Status

                            Indicates whether Cisco Unified Communications Manager can connect to the SAF forwarder.

                            Authentication Type

                            Indicates that Cisco Unified Communications Manager used digest authentication to connect to the SAF forwarder.

                            Registration Status

                            Indicates whether the Cisco Unified Communications Manager is registered to the SAF forwarder.

                            Time Last Registered

                            Displays the date and time when the Cisco Unified Communications Manager last registered with the SAF forwarder.

                            No of Registered Applications

                            Displays the total number of CCD advertising and requesting services that are registered to the SAF forwarder.

                            No of Connection Re-Attempts

                            Displays the number of times that the call-control entity, in this case, the Cisco Unified Communications Manager, has attempted to connect to the SAF forwarder.

                            RTMT allows you to search based on different criteria; for example, if you specify a search for the remote call-control entity, all the learned patterns display for the remote call-control entity.

                            To access the Learned Patterns or SAF Forwarders reports in RTMT, perform the following procedure:

                            Procedure
                              Step 1   To access the report, perform one of the following tasks:
                              1. For Learned Patterns—From the RTMT menus, choose CallManager > Report > Learned Pattern. Or, Click the CallManager tab; then, click Learned Pattern.
                              2. For SAF Forwarders—From the RTMT menus, choose CallManager > Report > SAF Forwarders. Or, click the CallManager tab; then, click SAF Forwarders.
                              Step 2   Choose the node from the Select a Node drop-down list box.

                              For learned pattern reports, if the Cisco CallManager service is running but the CCD requesting service is not running on that node, a message displays that the CCD Report Service is not working after you choose the node. If the CCD requesting service is not active on the node that you choose, the report displays as empty.

                              Step 3   Review the data in the report.

                              See the Data from Learned Pattern Report table and the Data from SAF Forwarder Report table for descriptions of the items reported.

                              Step 4   After the data displays, if you want to filter the results based on specific criteria, click the Filter button; specific the criteria that you want to search, click Apply and then OK.
                              Step 5   To display the most current results, click Refresh.
                              Step 6   If you want to search on a specific string in the data, click the Find button, enter the string, then, click Find Next.
                              Step 7   If you want to save the results, click Save, and choose either XML or Text, depending on how you want to save the results. Browse to the location where you want to save the data, name the file that you want to save; then, click Save.

                              Access Called Party Trace report

                              Called Party Trace allows you to configure a directory number or list of directory numbers that you want to trace. You can request on-demand tracing of calls using the Session Trace Tool.

                              The Called Party Trace feature provides information on the calling party number in addition to the called party number within a node. You can use the information from each node to trace a call back to the originator.


                              Note


                              You must be an authorized administrator to access the directory number logs. To grant authorization to a specific role using MLA, the "Called Party Tracing" resource must have read permission enabled for the role.


                              To access the Called Party Trace report in the Real-Time Monitoring Tool (RTMT), follow these steps:

                              Procedure
                                Step 1   From the RTMT menu, choose CallManager > Callprocess > Called Party Trace. Or, Click the CallManager tab; then, click Called Party Trace.
                                Step 2   Select the start time of the report using the drop-down box.
                                Note   

                                The start time cannot be older than five years from the current date.

                                Step 3   The report will show the following information:
                                • Start time
                                • Calling directory number
                                • Original called directory number
                                • Called directory number
                                • Calling device name
                                • Called device name
                                Note   

                                When 5 megabytes of trace file entries have been written to the log files being accessed by RTMT, the oldest log information is overwritten by new trace entries as they are recorded. The RTMT will only list a maximum of 500 entries for any given search.


                                Monitor Intercompany Media Services


                                Tip


                                The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds. If the collecting rate for the AMC (Alert Manager and Collector) service parameter changes, the polling rate in the precanned window also updates. In addition, the local time of the RTMT client application, not the backend server time, provides the basis for the time stamp in each chart.



                                Tip


                                To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart that interests you. Release the left mouse button when you have the selected area. RTMT updates the monitored view. To zoom out and reset the monitor to the initial default view, press the R key.


                                The Intercompany Media Services monitoring category monitors the following items:

                                • Routing—Displays the total number of Cisco Intercompany Media Engine routes that Cisco Unified Communications Manager maintains. This total includes the following routes:
                                  • Learned routes that represent the phone numbers that the Cisco Intercompany Media Engine client learned and that exist in the Cisco Unified Communications Manager routing tables
                                  • Unique domains of peer enterprises for which Cisco Intercompany Media Engine routes exist
                                  • Published routes that represent the number of direct inward dialing numbers (DIDs) that were published successfully to the IME distributed hash table across all Cisco Intercompany Media Engine services
                                  • Rejected routes that represent the number of learned routes that got rejected because the administrator blocked them. These charts represent the following performance counters for the Cisco IME Client performance object: RoutesLearned, DomainsUnique, RoutesPublished, and RoutesRejected. To display information on routing, choose CallManager > Cisco IME Client > Routing.
                                • Call Activities—Allows you to monitor the total number of Cisco Intercompany Media Engine calls. This total includes the following types of calls:
                                  • Calls that were attempted (including calls that were accepted, busy, no answer, and failed)
                                  • Calls that were received
                                  • Calls that were set up (that is, made by Cisco Unified Communications Manager and accepted by the remote party)
                                  • Calls that were accepted (that is, received by Cisco Unified Communications Manager and answered by the called party)
                                  • Calls that completed fallback to the PSTN
                                  • Calls that did not successfully fallback to the PSTN.

                                These charts represent the following performance counters for the Cisco IME Client performance object: CallsAttempted, CallAccepted, CallsReceived, CallsSetup, IMESetupsFailed, and FallbackCallsFailed.

                                To display information on call activities, choose CallManager > Cisco IME Client > Call Activities.

                                Categories

                                Categories allow you to organize objects in RTMT, such as performance monitoring counters and devices. For example, the default category under performance monitoring, RTMT allows you to monitor six performance monitoring counters in graph format. If you want to monitor more counters, you can configure a new category and display the data in table format.

                                If you perform various searches for devices, for example, for phones, gateways, and so on, you can create a category for each search and save the results in the category.

                                Add category

                                To add a category, perform the following procedure:

                                Procedure
                                  Step 1   Go to applicable window for your configuration:

                                  Cisco Unified Communications Manager

                                  Display Performance Monitoring under the system tab or Devices/CTIs in the Search window under the Communications Manager tab.

                                  Cisco Business Edition 5000

                                  Display Performance Monitoring under the system tab or Devices/CTIs in the Search window under the Communications Manager tab.

                                  Connection

                                  Choose System > Performance > Open Performance Monitoring.

                                  Step 2   Choose Edit > Add New Category.
                                  Step 3   Enter the name of the category; click OK.

                                  The category tab displays at the bottom of the window.


                                  Rename category

                                  To rename a category, perform the following procedure:

                                  Procedure
                                    Step 1   Perform one of the following tasks:
                                    1. Right-click the category tab that you want to rename and choose Rename Category.
                                    2. Click the category tab that you want to rename and choose Edit > Rename Category.
                                    Step 2   Enter the new name and click OK.

                                    The renamed category displays at the bottom of the window.


                                    Delete category

                                    To delete a category, perform one of the following tasks:

                                    • Right-click the category tab that you want to delete and choose Remove Category.
                                    • Click the category tab that you want to delete and choose Edit > Remove Category.

                                    Add counter using performance queries

                                    You can use queries to select and display perfmon counters. You can organize the perfmon counters to display a set of feature-based counters and save it in a category. After you save your RTMT profile, you can quickly access the counters in which you are interested.

                                    RTMT displays perfmon counters in chart or table format. The chart format displays the perfmon counter information by using line charts. For each category tab that you create, you can display up to six charts in the RTMT Perfmon Monitoring pane with up to three counters in one chart. After you create a category, you cannot change the display from a chart format to a table format, or vice versa.


                                    Tip


                                    You can display up to three counters in one chart in the RTMT Perfmon Monitoring pane. To add another counter in a chart, click the counter and drag it to the RTMT Perfmon Monitoring pane. Repeat again to add up to three counters.


                                    By default, RTMT displays perfmon counters in a chart format. You can also choose to display the perfmon counters in a table format. To display the perfmon counters in table format, you need to check the Present Data in Table View check box when you create a new category.

                                    Before You Begin

                                    Before you add counters, see the topics related to category tabs and zooming a perfmon counter.

                                    Procedure
                                      Step 1   Perform one of the following tasks:
                                      1. On the Quick Launch Channel, do the following:
                                        1. Click System.
                                        2. In the tree hierarchy, double-click Performance.
                                        3. Click the Performance icon.
                                      2. Choose System > Performance > Open Performance Monitoring.
                                      Step 2   Click the name of the server where you want to add a counter to monitor.

                                      The tree hierarchy expands and displays all the perfmon objects.

                                      Step 3   To monitor a counter in table format, continue to Step 4. To monitor a counter in chart format, skip to Step 9.
                                      Step 4   Choose Edit > New Category.
                                      Step 5   In the Enter Name field, enter a name for the tab.
                                      Step 6   To display the perfmon counters in table format, check the Present Data in Table View check box.
                                      Step 7   Click OK.

                                      A new tab with the name that you entered displays at the bottom of the pane.

                                      Step 8   Perform one of the following tasks to select one or more counters with one or more instances for monitoring in table format (skip the remaining step in this procedure):
                                      1. Double click a single counter and select a single instance from the pop-up window; then, click Add.
                                      2. Double click a single counter and select multiple instances from the pop-up window; then, click Add.
                                      3. Drag a single counter to the monitoring window and select a single instance from the pop-up window; then click Add.
                                      4. Drag a single counter to the monitoring window and select multiple instances from the pop-up window; then, click Add.
                                      5. Select multiple counters and drag them onto the monitoring window. Select a single instance from the pop-up window; then, click Add.
                                      6. Select multiple counters and drag them onto the monitoring window. Select multiple instances from the pop-up window; then, click Add.
                                        Tip   

                                        To display the counter in chart format after you display it in table format, right-click the category tab and choose Remove Category. The counter displays in chart format.

                                      Step 9   To monitor a counter in chart format, perform the following tasks:
                                      1. Click the file icon next to the object name that lists the counters that you want to monitor.

                                        A list of counters displays.

                                      2. To display the counter information, either right-click the counter and click Counter Monitoring, double-click the counter, or drag and drop the counter into the RTMT Perfmon Monitoring pane.

                                        The counter chart displays in the RTMT Perfmon Monitoring pane.


                                      Remove counter from Performance Monitoring pane

                                      You can remove a counter chart (table entry) with the Remove Chart/Table Entry menu item in the Perfmon menu in the menu bar.

                                      You can remove counters from the RTMT Perfmon Monitoring pane when you no longer need them. To remove a counter from the pane, perform the following procedure:

                                      The counter no longer displays in the RTMT Perfmon Monitoring pane.

                                      Procedure
                                      Perform one of the following tasks:
                                      1. Right-click the counter that you want to remove and choose Remove.
                                      2. Click the counter that you want to remove and choose Perfmon > Remove Chart/Table Entry.

                                      Add counter instance

                                      To add a counter instance, perform the following procedure:

                                      Procedure
                                        Step 1   Find and display the performance monitoring counter.
                                        Step 2   Perform one of the following tasks:
                                        1. Double-click the performance monitoring counter in the performance monitoring tree hierarchy.
                                        2. Click the performance monitoring counter in the performance monitoring tree hierarchy and choose System > Performance > Counter Instances.
                                        3. Right-click the performance monitoring counter in the performance monitoring tree hierarchy and choose Counter Instances.
                                        Step 3   In the Select Instance window, click the instance; then, click Add.

                                        The counter displays.


                                        Set up counter alert notification

                                        The following procedure describes how to configure alert notification for a counter.


                                        Tip


                                        To remove the alert for the counter, right-click the counter and choose Remove Alert. The option appears gray after you remove the alert.


                                        The following table describes the counter alert configuration parameters in the Threshold, Value Calculated As, Duration, Frequency, and Schedule panes.

                                        Table 9 Counter Alert Configuration Parameters

                                        Setting

                                        Description

                                        Threshold Pane

                                        Trigger alert when following conditions met (Over, Under)

                                        Check the check box and enter the value that applies.

                                        • Over—Check this check box to configure a maximum threshold that must be met before an alert notification is activated. In the Over value field, enter a value. For example, enter a value that equals the number of calls in progress.
                                        • Under—Check this check box to configure a minimum threshold that must be met before an alert notification is activated. In the Under value field, enter a value. For example, enter a value that equals the number of calls in progress.
                                          Tip    Use these check boxes in conjunction with the Frequency and Schedule configuration parameters.

                                        Value Calculated As Pane

                                        Absolute, Delta, Delta Percentage

                                        Click the radio button that applies.

                                        • Absolute—Choose Absolute to display the data at its current status. These counter values are cumulative.
                                        • Delta—Choose Delta to display the difference between the current counter value and the previous counter value.
                                        • Delta Percentage—Choose Delta Percentage to display the counter performance changes in percentage.

                                        Duration Pane

                                        Trigger alert only when value constantly...; Trigger alert immediately

                                        • Trigger alert only when value constantly...If you want the alert notification only when the value is constantly below or over threshold for a desired number of seconds, click this radio button and enter seconds after which you want the alert to be sent.
                                        • Trigger alert immediately—If you want the alert notification to be sent immediately, click this radio button.

                                        Frequency Pane

                                        Trigger alert on every poll; trigger up to...

                                        Click the radio button that applies.

                                        • Trigger alert on every poll—If you want the alert notification to activate on every poll when the threshold is met, click this radio button.For example, if the calls in progress continue to go over or under the threshold, the system does not send another alert notification. When the threshold is normal (between 50 and 100 calls in progress), the system deactivates the alert notification; however, if the threshold goes over or under the threshold value again, the system reactivates alert notification.
                                        • Trigger up to...—If you want the alert notification to activate at certain intervals, click this radio button and enter the number of alerts that you want sent and the number of minutes within which you want them sent.

                                        Schedule Pane

                                        24-hours daily; start/stop

                                        Click the radio button that applies:

                                        • 24-hours daily—If you want the alert to be triggered 24 hours a day, click this radio button.
                                        • Start/Stop—If you want the alert notification activated within a specific time frame, click the radio button and enter a start time and a stop time. If the check box is checked, enter the start and stop times of the daily task. For example, you can configure the counter to be checked every day from 9:00 am to 5:00 pm or from 9:00 pm to 9:00 am.
                                        Procedure
                                          Step 1   Find and display the performance counter.
                                          Step 2   From the counter chart or table, right-click the counter for which you want to configure the alert notification, and choose Set Alert/Properties.
                                          Step 3   Check the Enable Alert check box.
                                          Step 4   In the Severity drop-down list box, choose the severity level at which you want to be notified.
                                          Step 5   In the Description pane, enter a description of the alert.
                                          Step 6   Click Next.
                                          Step 7   Configure the settings in the Threshold, Value Calculated As, Duration, Frequency, and Schedule panes. After you enter the settings in the window, click Next to proceed to the next panes.
                                          Step 8   If you want the system to send an e-mail message for the alert, check the Enable Email check box.
                                          Step 9   If you want to trigger an alert action that is already configured, choose the alert action that you want from the Trigger Alert Action drop-down list box.
                                          Step 10   If you want to configure a new alert action for the alert, click Configure.
                                          Note   

                                          Whenever the specified alert is triggered, the system sends the alert action.

                                          The Alert Action dialog box displays.

                                          Step 11   To add a new alert action, click Add.

                                          The Action Configuration dialog box displays.

                                          Step 12   In the Name field, enter a name for the alert action.
                                          Step 13   In the Description field, enter a description for the alert action.
                                          Step 14   To add a new e-mail recipient for the alert action, click Add.

                                          The Input dialog box displays.

                                          Step 15   Enter either the e-mail or e-page address of the recipient that you want to receive the alert action notification.
                                          Step 16   Click OK.

                                          The recipient address displays in the Recipient list. The Enable check box gets checked.

                                          Tip   

                                          To disable the recipient address, uncheck the Enable check box. To delete a recipient address from the Recipient list, highlight the address and click Delete.

                                          Step 17   Click OK.
                                          Step 18   The alert action that you added displays in Action List.
                                          Tip   

                                          To delete an alert action from the action list, highlight the alert action and click Delete. You can also edit an existing alert action by clicking Edit.

                                          Step 19   Click Close.
                                          Step 20   In the User-defined email text box, enter the text that you want to display in the e-mail message.
                                          Step 21   Click Activate.

                                          Display counter description

                                          Use one of two methods to obtain a description of the counter:

                                          Procedure
                                            Step 1   Perform one of the following tasks:
                                            1. In the Perfmon tree hierarchy, right-click the counter for which you want property information and choose Counter Description.
                                            2. In the RTMT Performance Monitoring pane, click the counter and choose System > Performance > Counter Description from the menu bar.
                                              Tip   

                                              You can display the counter description and configure data-sampling parameters.

                                              The Counter Property window displays the description of the counter. The description includes the host address, the object to which the counter belongs, the counter name, and a brief overview of what the counter does.

                                            Step 2   To close the Counter Property window, click OK.

                                            Configure data sample

                                            The Counter Property window contains the option to configure data samples for a counter. The perfmon counters that display in the RTMT Perfmon Monitoring pane contain green dots that represent samples of data over time. You can configure the number of data samples to collect and the number of data points to show in the chart. After the data sample is configured, view the information by using the View All Data/View Current Data menu option.

                                            This section describes how to configure the number of data samples to collect for a counter.

                                            Procedure
                                              Step 1   Find and display the counter.
                                              Step 2   Perform one of the following tasks:
                                              1. Right-click the counter for which you want data sample information and choose Monitoring Properties if you are using chart format and Properties if you are using table format.
                                              2. Click the counter for which you want data sample information and choose System > Performance > Monitoring Properties.

                                                The Counter Property window displays the description of the counter, as well as the tab for configuring data samples. The description includes the host address, the object to which the counter belongs, the counter name, and a brief overview of what the counter does.

                                              Step 3   To configure the number of data samples for the counter, click the Data Sample tab.
                                              Step 4   From the No. of data samples drop-down list box, choose the number of samples (between 100 and 1000).

                                              The default specifies 100.

                                              Step 5   From the No. of data points shown on chart drop-down list box, choose the number of data points to display on the chart (between 10 and 50).

                                              The default specifies 20.

                                              Step 6   Click one of the following parameters:
                                              • Absolute - Because some counter values are accumulative, choose Absolute to display the data at its current status.
                                              • Delta - Choose Delta to display the difference between the current counter value and the previous counter value.
                                              • Delta Percentage - Choose Delta Percentage to display the counter performance changes in percentage.
                                              Step 7   To close the Counter Property window and return to the RTMT Perfmon Monitoring pane, click the OK button.

                                              View counter data

                                              Perform the following procedure to view the data that is collected for a performance counter.

                                              Procedure
                                                Step 1   In the RTMT Perfmon Monitoring pane, right-click the counter chart for the counter for which you want to view data samples and choose View All Data.

                                                The counter chart displays all data that has been sampled. The green dots display close together, almost forming a solid line.

                                                Step 2   Right-click the counter that currently displays and choose View Current.

                                                The counter chart displays the last configured data samples that were collected.


                                                Local perfmon counter data logging

                                                RTMT allows you to choose different perfmon counters to log locally. You can then view the data from the perfmon CSV log by using the performance log viewer.

                                                Start perfmon counter logging

                                                To start logging perfmon counter data into a CSV log file, perform the following procedure:

                                                Procedure
                                                  Step 1   Find and display the performance monitoring counters.
                                                  Step 2   If you are displaying perfmon counters in the chart format, right-click the graph for which you want data sample information and choose Start Counter(s) Logging. If you want to log all counters in a screen (both chart and table view format), you can right-click the category name tab at the bottom of the window and choose Start Counter(s) Logging.

                                                  The Counter Logging Configuration dialog box displays.

                                                  Step 3   In the Logger File Name field, enter a file name and click OK.

                                                  RTMT saves the CSV log files in the log folder in the .jrtmt directory under the user home directory. For example, in Windows, the path specifies D:\Documents and Settings\userA\.jrtmt\log, or in Linux, the path specifies /users/home/.jrtmt/log.

                                                  To limit the number and size of the files, configure the maximum file size and maximum number of files parameter in the trace output setting for the specific service in the Trace Configuration window of Cisco Unified Serviceability. See Cisco Unified Serviceability Administration Guide.


                                                  Stop perfmon counter logging

                                                  To stop logging perfmon counter data, perform the following procedure:

                                                  Procedure
                                                    Step 1   Find and display the performance monitoring counters.
                                                    Step 2   If you are displaying perfmon counters in the chart format, right-click the graph for which counter logging is started and choose Stop Counter(s) Logging. If you want to stop logging of all counters in a screen (both chart and table view format), you can right-click the category name tab at the bottom of the window and choose Stop Counter(s) Logging.

                                                    Perfmon log files

                                                    You can view data from the perfmon CSV log by using the Performance Log Viewer in RTMT or by using the Microsoft Performance tool.

                                                    View log files on Performance Log Viewer

                                                    The Performance Log Viewer displays data for counters from perfmon CSV log files in a graphical format. You can use the performance log viewer to display data from the local perfmon logs that you collected, or you can display the data from the Realtime Information Server Data Collection (RISDC) perfmon logs.

                                                    The local perfmon logs comprise data from counters that you choose and store locally on your computer. You can manually start and stop local counter data logging.

                                                    The following table describes the functions of different buttons that are available on the performance log viewer.

                                                    Table 10 Performance Log Viewer

                                                    Button

                                                    Function

                                                    Select Counters

                                                    Allows you to add counters that you want to display in the performance log viewer. To not display a counter, uncheck the Display column next to the counter.

                                                    Reset View

                                                    Resets the performance log viewer to the initial default view.

                                                    Save Downloaded File

                                                    Allows you to save the log file to your local computer.


                                                    Tip


                                                    You can order each column by clicking on a column heading. The first time that you click on a column heading, the records display in ascending order. A small triangle pointing up indicates ascending order. If you click the column heading again, the records display in descending order. A small triangle pointing down indicates descending order. If you click the column heading one more time, the records displays in the unsorted state.


                                                    Procedure
                                                      Step 1   Perform one of the following tasks:
                                                      1. On the Quick Launch Channel, do the following:
                                                        1. Click System.
                                                        2. In the tree hierarchy, double-click Performance.
                                                        3. Click the Performance Log Viewer icon.
                                                      2. Choose System > Performance > Open Performance Log Viewer.
                                                      Step 2   Choose the type of perfmon logs that you want to view:
                                                      1. For RISDC Perfmon Logs, perform the following steps:
                                                        1. Click on RISDC Perfmon Logs and choose a server from the Select a node drop-down box.
                                                        2. Click Open. The File Selection Dialog Box displays.
                                                        3. Choose the file and click Open File. The Select Counters Dialog Box displays.
                                                        4. Choose the counters that you want to display by checking the check box next to the counter.
                                                        5. Click OK.
                                                      2. For locally stored data, perform the following steps:
                                                        1. Click Local Perfmon Logs.
                                                        2. Click Open. The File Selection Dialog Box displays. RTMT saves the perfmon CSV log files in the log folder in the .jrtmt directory under the user home directory. In Windows, the path specifies D:\Documents and Settings\userA\.jrtmt\log, or in Linux, the path specifies /users/home/.jrtmt/log.
                                                        3. Browse to the file directory.
                                                        4. Choose the file that you are interested in viewing or enter the file name in the filename field.
                                                        5. Click Open. The Select Counters Dialog Box displays.
                                                        6. Choose the counters that you want to display by checking the check box next to the counter.
                                                        7. Click OK.

                                                        The performance log viewer displays a chart with the data from the selected counters. The bottom pane displays the selected counters, a color legend for those counters, display option, mean value, minimum value, and the maximum value.


                                                      Zoom in and out of charts

                                                      The performance Log viewer includes a zoom feature that allows you to zoom in on an area in the chart. To zoom in, click and drag the left button of the mouse until you have the selected desired area.

                                                      To reset the chart to the initial default view, click Reset View or right-mouse click the chart and choose Reset.

                                                      View perfmon log files using Microsoft Performance tool

                                                      To view the log files by using the Microsoft Performance tool, follow these steps:

                                                      Procedure
                                                        Step 1   Choose Start > Settings > Control Panel > Administrative Tools > Performance.
                                                        Step 2   In the application window, click the right mouse button and choose Properties.
                                                        Step 3   Click the Source tab in the System Monitor Properties dialog box.
                                                        Step 4   Browse to the directory where you downloaded the perfmon log file and choose the perfmon csv file. The log file includes the following naming convention: PerfMon_<server>_<month>_<day>_<year>_<hour>_<minute>.csv; for example, PerfMon_172.19.240.80_06_15_2005_11_25.csv.
                                                        Step 5   Click Apply.
                                                        Step 6   Click the Time Range button. To specify the time range in the perfmon log file that you want to view, drag the bar to the appropriate starting and ending times.
                                                        Step 7   To open the Add Counters dialog box, click the Data tab and click Add.
                                                        Step 8   From the Performance Object drop-down box, choose the perfmon object. If an object has multiple instances, you may choose All instances or select only the instances that you are interested in viewing.
                                                        Step 9   You can choose All Counters or select only the counters that you are interested in viewing.
                                                        Step 10   To add the selected counters, click Add.
                                                        Step 11   When you finish selecting counters, click Close.

                                                        Troubleshooting perfmon data logging

                                                        When you enable RISDC perfmon logs, information gets collected for the system in logs that are written on the server. You can enable or disable RISDC perfmon logs by going to the Service Parameter window of the administration interface for your configuration:

                                                        Cisco Unified Communications Manager

                                                        On Cisco Unified Communications Manager Administration, choose System > Service Parameters and select the Cisco RIS Data Collector Service from the Service drop-down menu.

                                                        Cisco Business Edition 5000

                                                        On Cisco Unified Communications Manager Administration, choose System > Service Parameters and select the Cisco RIS Data Collector Service from the Service drop-down menu.

                                                        Connection

                                                        On Cisco Unity Connection Administration, choose System Settings > Service Parameters and select the Cisco RIS Data Collector from the Service drop-down menu.

                                                        By default, RISDC perfmon logging remains enabled. Be aware that RISDC perfmon logging is also known as Troubleshooting Perfmon Data logging. When you enable RISDC perfmon logging, the server collects performance data that are used to troubleshoot problems.

                                                        You can collect the log files for Cisco RIS Data Collector service on the server by using RTMT to download the log files. If you want to download the log files by using the CLI, refer to Command Line Interface Reference Guide for Cisco Unified Solutions. After you collect the log files, you can view the log file by using the Performance Log Viewer in RTMT or by using the Microsoft Windows performance tool.

                                                        Set up troubleshooting perfmon data logging

                                                        The following procedure describes how to configure the troubleshooting perfmon data logging feature.

                                                        Procedure
                                                          Step 1   Go to the Service Parameters window of the administration interface for your configuration:

                                                          Cisco Unified Communications Manager

                                                          On Cisco Unified Communications Manager Administration, choose System > Service Parameters. The Service Parameter Configuration window displays.

                                                          Cisco Business Edition 5000

                                                          On Cisco Unified Communications Manager Administration, choose System > Service Parameters. The Service Parameter Configuration window displays.

                                                          Connection

                                                          On Cisco Unity Connection Administration, expand System Settings, then click Service Parameters. The Service Parameter Configuration window displays.

                                                          Step 2   From the Server drop-down list box, choose the server.
                                                          Step 3   From the Service drop-down list box, choose Cisco RIS Data Collector.
                                                          Step 4   Enter the appropriate data-logging parameter settings as described in Table 1.
                                                          Step 5   Click Save.

                                                          Troubleshoot perfmon data logging settings

                                                          The following table describes the available settings to enable and disable troubleshooting perfmon data logging.

                                                          Table 11 Troubleshooting Perfmon Data-Logging Parameters

                                                          Field

                                                          Description

                                                          Enable Logging

                                                          From the drop-down box, choose True to enable or False to disable troubleshooting perfmon data logging. The default value specifies True.

                                                          Polling Rate

                                                          Enter the polling rate interval (in seconds). You can enter a value from 5 (minimum) to 300 (maximum). The default value specifies 15.

                                                          Maximum No. of Files

                                                          Enter the maximum number of Troubleshooting Perfmon Data Logging files that you want to store on disk. You can enter a value from 1 (minimum) up to 100 (maximum). The default value specifies 50.

                                                          Consider your storage capacity in configuring the Maximum No. of Files and Maximum File Size Parameters. Cisco recommends that you do not exceed a value of 100 MB when you multiply the Maximum Number of Files value by the Maximum File Size value.

                                                          When the number of files exceeds the maximum number of files that you specified in this field, the system will delete log files with the oldest timestamp.

                                                          Caution   

                                                          If you do not save the log files on another machine before you change this parameter, you risk losing the log files.

                                                          Maximum File Size

                                                          Enter the maximum file size (in megabytes) that you want to store in a perfmon log file before a new file is started. You can enter a value from 1 (minimum) to 500 (maximum). The default value specifies 5 MB.

                                                          Consider your storage capacity in configuring the Maximum No. of Files and Maximum File Size Parameters. Cisco recommends that you do not exceed a value of 100 MB when you multiply the Maximum Number of Files value by the Maximum File Size value.

                                                          Port Monitor

                                                          The Port Monitor lets you monitor the activity of each Cisco Unity Connection voice messaging port in real time. This information can help you determine whether they system has too many or too few ports.

                                                          The Port Monitor provides information about each Cisco Unity Connection voice messaging port in real time. This information can help you determine the activity of each port and whether the system has too many or too few ports. The Port Monitor displays the information for each port as described in the following table.

                                                          Table 12 Fields and Descriptions in the Port Monitor

                                                          Field

                                                          Description

                                                          Port Name

                                                          The display name of the port in Cisco Unity Connection Administration.

                                                          Caller

                                                          For incoming calls, the phone number of the caller.

                                                          Called

                                                          For incoming calls, the phone number that was dialed.

                                                          Reason

                                                          If applicable, the reason why the call was redirected.

                                                          Redir

                                                          The extension that redirected the call. If the call was redirected by more than one extension, this field shows the extension prior to the last extension.

                                                          Last Redir

                                                          The last extension that redirected the call.

                                                          Application Status

                                                          The name of the conversation that Cisco Unity Connection is playing for the caller. When the port is not handling a call, the status displays Idle.

                                                          Display Status

                                                          The action that the conversation is currently performing. When the port is not handling a call, the status displays Idle.

                                                          Conversation Status

                                                          Specific details about the action that the conversation is performing. When the port is not handling a call, the status displays Idle.

                                                          Port Ext

                                                          The extension of the port.

                                                          Connected To

                                                          For Cisco Unified Communications Manager SCCP integrations, the IP address and port of the Cisco Unified Communications Manager server to which the ports are registered.


                                                          Note


                                                          Depending on the information that the phone system integration provided and the status of the call, some fields may remain blank.


                                                          Start Cisco Unity Connection Port Monitor polling

                                                          Perform the following steps to use the Port Monitor.


                                                          Note


                                                          Setting a low polling rate may impact system performance.


                                                          Procedure
                                                            Step 1   In Unified CM Real Time Monitoring Tool, access Unity Connection and click Port Monitor. The Port Monitor window displays.
                                                            Step 2   In the Node drop-down box, choose a Cisco Unity Connection server.
                                                            Step 3   In the Polling Rate field, accept the default or enter the number of seconds between updates in the data on the Port Monitor tab; then, click Set Polling Rate.
                                                            Step 4   Click Start Polling. The Port Monitor window displays the status of all voice messaging ports on Cisco Unity Connection.