User Guide for IP Telephony Monitor
Introduction

Table Of Contents

Introduction

What Is ITM?

How Are ITM and ITM Multi-View Different?

Example: Importing a Voice Gateway into ITM

Example: Importing a Voice Gateway into ITM Multi-View

What Is a Partition?

Is ITM Ready to Use?

How Will I Use ITM for Day-to-Day Operations?

What Is Alerts and Activities?

What Is Device Management?

What Is Notification Services?

What Is Fault History?

What Is IP Phone Information Facility?

What Is Phone Monitoring Admin?

How Does ITM Work?

Users Perform Device Management and Configuration

ITM Performs Ongoing Monitoring, Analysis, and Notification

Users Respond to Notifications and Alerts


Introduction


These topics provide an overview of IP Telephony Monitor (ITM) and IP Telephony Monitor Multi-View:

What Is ITM?

Is ITM Ready to Use?

How Will I Use ITM for Day-to-Day Operations?

How Does ITM Work?

What Is ITM?

ITM offers the following real-time assistance to network and telephony operations personnel:

Monitoring and displaying the operational health of:

IP telephony environments or voice environments using IP as transport

IP infrastructure, or IP fabric, that underlies and supports the IP telephony or voice environment

Analyzing events that occur in these environments and determining when a probable fault has occurred

Notifying users of alert conditions through an online display and through other notification services

When you first start to use ITM, you may be interested in the answers to the following questions:

How Are ITM and ITM Multi-View Different?

What Is a Partition?

Is ITM Ready to Use?

How Are ITM and ITM Multi-View Different?

ITM and ITM Multi-View both provide the features described in the "What Is ITM?" section. The differences between them are described in Table 1-1.

Table 1-1 Comparison of ITM and ITM Multi-View 

Feature
ITM
ITM Multi-View

Number of enterprises that you can manage from a single platform

One.

Up to ten.

Each enterprise is managed from a separate partition. A Partition Administrator assigns devices and users to partitions. Network Administrators and Network Operators log in to ITM and monitor devices in one partition. For more information on partitions, see the "What Is a Partition?" section.

User roles and security

Uses standard CiscoWorks user roles to control access to tasks. For more information on CiscoWorks user roles, see the "Understanding Your User Role" section.

Uses standard CiscoWorks user roles in addition to a unique CiscoWorks user role: the Partition Administrator. Only a Partition Administrator can manage partitions, assigning devices and users to them.

Although the Network Administrator and Network Operator user roles are granted permission to perform ITM tasks, they can do nothing if they have not also been assigned to a partition by a Partition Administrator.

Configuration tasks

You need only perform configuration tasks once with respect to the needs and situation of your enterprise.

A Network Administrator can perform any configuration task.

Each Network Administrator should perform configuration, as needed, taking into account the needs and situation of the enterprise in the active partition. Each Network Administrator might, for example, do the following:

Configure confidence tests

Configure polling parameters and threshold values

There are certain configuration tasks that only a Partition Administrator can perform. See the "Tasks for Partition Administrators" section.

System administration

An admin user can back up, and restore, all ITM data.

An admin user can back up, and restore, all ITM Multi-View data. In addition, a Partition Administrator can save and restore the data for a partition.

Device monitoring

Users have access to information about any device ITM manages.

Users have access to information about the devices ITM Multi-View manages in one partition: the active partition.

Device management

After you add or import devices, ITM initiates discovery, begins polling, and starts to manage the devices.

The process is illustrated in the "Example: Importing a Voice Gateway into ITM" section.

After you add or import devices, ITM Multi-View moves the devices to the default partition and initiates device discovery. However, ITM Multi-View does not begin polling until a Partition Administrator assigns the device to an active partition.

The process is illustrated in the "Example: Importing a Voice Gateway into ITM Multi-View" section.

IP phone information1

Users have access to information about phones that ITM discovers.

Users have access to information about phones that:

Are registered to Cisco CallManager on a media server that is assigned to the active partition.

Are physically connected to a phone access switch that is assigned to the active partition.

1 IP phone information is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


Example: Importing a Voice Gateway into ITM

Figure 1-1 shows the series of activities that ITM performs when a user imports a voice gateway, including showing how a user can confirm that these activities have occurred. To see the same example illustrated for ITM Multi-View, see the "Example: Importing a Voice Gateway into ITM Multi-View" section.

Figure 1-1 Importing Devices to ITM

ITM performs the following tasks after a user imports a device:

ITM discovers the device—You can see the results of this discovery using Device Management; the Device Details page will display the state and functions of the device.

ITM assigns the device to system-defined groups—You can see which devices are members of each system-defined group using Group Management; the Membership Details page for any group will display them.

ITM starts to poll the device—You can see alerts for a device on the Alerts and Activities display when events occur on the device. You can see the overriding group that ITM uses for polling parameters and threshold values for the voice gateway on the Polling Parameters Summary and the Thresholds Summary pages.


Note ITM also performs these tasks after devices are added to ITM by RME synchronization. See the "Synchronizing ITM Inventory with RME Inventory" section.

RME Synchronization is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


Example: Importing a Voice Gateway into ITM Multi-View

Figure 1-2 shows that when a user imports a voice gateway, ITM Multi-View moves it to the default partition, P0. Only after a Partition Administrator assigns the voice gateway to an active partition, P1, does ITM Multi-View discover the gateway, assign it to system-defined groups, and prepare to poll the voice gateway.

Figure 1-2 Importing Devices to ITM Multi-View

What Is a Partition?

As you work with ITM, use the online help, or read the documentation, you will encounter the term partition. A partition is a logical grouping of a set of managed devices. These devices can belong to only one partition at any time. A partition also has a set of users who can perform operations on the devices in the partition.

If you are using ITM Multi-View, each device that ITM manages must be assigned to one of ten partitions. Users must also be assigned to one or more defined partitions, and can only view and act upon devices in one partition at a time.

If you are using ITM, all of your devices are in one partition and all users are assigned to that single partition.

Is ITM Ready to Use?

The person or team that installed ITM should have completed the initial configuration before you start working with ITM. The instructions for configuring ITM are included in Installation and Configuration Guide for IP Telephony Monitor. The following table lists the tasks that should already be complete before you start to work with ITM.

 
Initial Configuration Task
For ITM
For ITM Multi-View
Reference

Step 1 

Create at least one user in the Partition Administrator role

N/A

Yes

Creating a Partition Administrator

Step 2 

Create one or more partitions

N/A

Yes1

Creating a Partition

Step 3 

Import devices

Yes

Yes

Importing Devices

Step 4 

Move devices to an active partition

N/A

Yes

Editing a Partition

         
         

Step 5 

Configure SNMP Trap Forwarding 2

Optional

Optional

Configuring SNMP Trap Forwarding

Step 6 

Configure SNMP Trap2 Receiving

Optional

Optional

Updating the SNMP Trap Receiving Port

1 Alternatively, a Partition Administrator can import devices before creating a partition. See the "Tasks that a Partition Administrator Can Perform in Partition 0" section.

2 Only users who want to integrate ITM with a network management system (NMS) or trap daemon on another server must perform this task.

After the tasks in the previous table are complete, ITM is ready to monitor and analyze events, and provide notification of alerts on the Alerts and Activities display. ITM uses the default polling parameters and threshold values, default rediscovery and purging schedules, and default views. You should determine whether the default values are adequate for your use.

Table 1-2 lists tasks that you may attend to, at your discretion, after the initial configuration. The table lists optional configuration tasks and some day-to-day tasks that you may want to address when you first start to use ITM.

Table 1-2 Tasks to Consider when Initially Setting Up ITM 

Initial Setup Tasks
Explanation
Reference

Subscribe users to receive e-mail notification of alerts and subscribe hosts to receive ITM-generated SNMP traps.

ITM displays the operational health of the IP telephony environment and IP fabric on the Alerts and Activities display. In addition, you can subscribe users and hosts to receive e-mail or ITM-generated SNMP traps, respectively, in response to alerts.

Using Notification Services

Update polling parameters and threshold values.

ITM provides default values. However, you can update the values based on your experience with and knowledge of the IP telephony environment and IP fabric. You should plan to apply the changes during a time of low activity on the network.

Configuring Polling and Thresholds

Set up confidence tests to monitor IP telephony application health.

You can configure various tests to run at intervals against IP telephony elements, such as Cisco CallManagers.

Configuring Confidence Tests

Import phones and configure phone monitoring.1

ITM monitors key phones.

Getting Started with Phone Monitoring

Set up phone reachability tests to check the availability of key phones.2

You can configure ITM to test the availability of key phones in your network.

Using the Phone Reachability Testing Manager

Set up Survivable Remote Site Telephony (SRST) tests.2

After you import devices to ITM, import a list identifying the source routers and target SRST routers in ITM inventory. This enables ITM to perform regular tests and to notify you when a branch office fails over to SRST.

Getting Started with SRST Monitoring Management

Update device rediscovery schedules.

ITM provides a single default schedule for device rediscovery. You can use that schedule or suspend it and create additional rediscovery schedules.

Configuring Rediscovery Schedules

Update phone discovery schedules.2

ITM provides six default schedules for phone discovery. You can update or delete them; you can also add phone discovery schedules (up to a maximum of ten.)

Scheduling Major Phone Discovery

Set up RME Synchronization.2

You can automatically synchronize ITM inventory with RME inventory.

Synchronizing ITM Inventory with RME Inventory.

     

Add Alerts and Activities views.

Alerts and Activities views control which groups of devices are the focus of the Alerts and Activities display. ITM provides two default views. You can add more views.

Configuring Views for the Alerts and Activities Display

Update the daily purging schedule.

By default, ITM purges the database at midnight. You can modify the schedule.

Configuring the Daily Purging Schedule

1 Phone Monitoring is available only if you have not downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.

2 Phone reachability tests, SRST tests, RME synchronization, and phone discovery schedules are supported only if you have downloaded and installed IDU 2 or later.


How Will I Use ITM for Day-to-Day Operations?

These topics briefly describe ITM functions that will be used frequently. On a day-to-day basis, operations personnel are likely to use the Alerts and Activities display and Fault History to monitor the IP telephony environment. Operations personnel are also likely to use IP Phone Information Facility to find phones.


Note IP Phone Information Facility is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


Network administrators and operators might similarly use the Alerts and Activities display and Fault History to assess network health. They might also use one of the following:

IP Phone Information Facility—To find phones.

Phone Monitoring—To monitor key phones.


Note Phone Monitoring is available only if you have not downloaded and installed IDU 2 or later.


In addition, network administrators and operators will use:

Device Management—To keep the inventory of devices that ITM monitors current.

Notification Services—To ensure that the right users and systems receive e-mail or SNMP traps in response to alerts on selected devices.

To make the most effective use of ITM on a day-to-day basis, network administrators and operators also need to understand the impact of operations on configuration and administration tasks. An overview is provided in the "Performing Scheduling Tasks" section.

The ITM functions that support day-to-day operations are further described in the following topics:

What Is Alerts and Activities?

What Is Device Management?

What Is Notification Services?

What Is Fault History?

What Is IP Phone Information Facility?

What Is Phone Monitoring Admin?

What Is Alerts and Activities?

The Alerts and Activities display provides a consolidated real-time view of the operational status of your IP telephony environment and IP fabric. When a fault occurs in your network, the IP Telephony Monitor generates an event (or events). Events are rolled up into alerts, one alert for each device with a fault.

When an alert occurs on an element in your active view (a logical group of devices), it is displayed on your Alerts and Activities display. You, or a user with administrative privileges, can customize your view to include only those device groups that are important to you.

From the Alerts and Activities display you can also:

Drill down into an alert to see what events caused the alert, and add alert annotations for other users to read.

Drill down into specific events for MIB attribute values.

Open a Detailed Device View to examine device components and suspend or resume monitoring of them.

Use the ITM Tools button and click the Fault History link to view historical details on alerts and events from the past 24 hours.

You can see which components of the device are in the ITM manageable inventory as follows: After you locate the device on the Alerts and Activities display, you can click it and open a Detailed Device View. The Detailed Device View displays the manageable components of the device. From the Detailed Device View, a user in a Network Administrator role can suspend monitoring of a device component and, afterwards, resume monitoring of the device component again.

What Is Device Management?

Device Management involves keeping the inventory of devices that ITM monitors up-to-date. The following scenario describes the process for managing devices:

1. A user adds a device or imports a group of devices to ITM.

2. ITM probes the devices to discover their configuration and adds their manageable elements to its inventory. The user can click View Discovery Status to see the status of devices.

3. By default, ITM performs rediscovery on a weekly basis. A user can update the default discovery schedule or add discovery schedules.

4. When a device is added to or deleted from the user's IP telephony environment or IP fabric, the user must correspondingly add or delete the device in ITM.

What Is Notification Services?

In addition to watching network conditions as they change on the Alerts and Activities display, you can use notification services to automatically notify users and other systems when specific changes occur on selected devices. To do so, you create subscriptions for either e-mail notification or ITM-generated SNMP trap notification. Subscriptions comprise:

A list of devices and device groups of interest

The status and severity of alarms for which you want notification

One ore more recipients

You can add, modify, and delete subscriptions at any time as your need to disseminate the status and severity of alarms changes.

What Is Fault History?

Fault History provides the history of ITM events and alerts. The stored history includes alert information and annotations (informational text entered by ITM users), and event information and properties (component name and MIB attributes).

You can start Fault History in the following ways:

From the Alerts and Activities Display page. From here, you can generate a Fault History display with information about alerts and events from the last 24 hours.

From IP Telephony Monitor  >  Fault History. This method provides historical information about all alerts and events in the Fault History database. The Fault History database keeps information for the alerts and events that occurred within the last 31 days.

You can use Fault History to generate customized tabular displays of specific alerts, specific events, event dates, and event severity.

What Is IP Phone Information Facility?


Note IP Phone Information Facility is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


IP Phone Information Facility helps you to find phones and display pertinent details about them. IP Phone Information Facility includes:

Simple and advanced find functions that allow you to view information about your phones, including:

IP address, MAC address, and Cisco CallManager address

Switch and port

Displays with information such as:

Survivable Remote Site Telephony (SRST) configuration details

IPT application details

IPT Security Details which includes displays such as:

Suspect phones—These are phones that are not registered to a Cisco CallManager.

Phones with duplicate MAC addresses or duplicate IP addresses

Phones that have been added or deleted, or have changed status

Phones that have been moved


Note ITM can automatically print security displays to PDF files daily.


What Is Phone Monitoring Admin?


Note Phone Monitoring is available only if you have not downloaded and installed IDU 2 or later.


With phone monitoring, you can monitor the health of important phones in your network. Through the Alerts and Activities display, you can view information about the phones, such as a phone's reachability and its registration with a Cisco CallManager. ITM supports up to 1,000 monitored phones.

How Does ITM Work?

These topics provide a simplified view of ITM user tasks and ITM processing:

Users Perform Device Management and Configuration

ITM Performs Ongoing Monitoring, Analysis, and Notification

Users Respond to Notifications and Alerts

Users Perform Device Management and Configuration

Users supply the information that tells ITM what to monitor. Figure 1-3 shows a user importing devices and phones, and performing optional configuration tasks to optimize ITM.

Figure 1-3 The Role of User Input

Users supply the following information:

Devices—You must import devices and, as your IP telephony environment and IP fabric change, you must add and delete them accordingly. ITM performs periodic rediscovery, refreshing the inventory of phones, known devices, and device components.


Note ITM monitors supported devices only. To see the device support table for ITM, log in to Cisco.com at http://cisco.com and select Products & Services > Network Management CiscoWorks > CiscoWorks IP Telephony Environment Monitor > CiscoWorks IP Telephony Monitor > Technical Documentation > Device Support Tables.


Phones:

Phone Reachability Tests—To perform phone reachability tests, you must select the phones to test by importing tests for phones that are already managed by ITM.


Note Phone reachability testing is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


SRST Management—To determine when phones are running under Survivable Remote Site Telephony (SRST), you must import information for tests.


Note SRST management is available only if you have downloaded and installed IDU 2 or later.


Phone Monitoring—To monitor a set of important phones, you must import and select them. Over time, you may want to delete phones that no longer require monitoring, or add other phones.


Note Phone Monitoring is available only if you have not downloaded and installed IDU 2 or later.


Supported IP telephony applications—ITM polls and rediscovers the devices on which supported IP telephony applications (for example, Cisco CallManager) run, just as ITM does for any other supported device that you import. In addition, you can set up confidence tests to monitor IP telephony applications such as Cisco Emergency Responder.

You can decide how to manage the information about alerts and traps that ITM produces. For example, you can:

Create views, enabling users to monitor specific groups of devices on the Alerts and Activities display.

Create subscriptions to send e-mail and generated SNMP trap notification to users and systems, respectively.

Determine where to forward traps by configuring the port to which ITM forwards them.

You can also control how often ITM gathers data. ITM receives traps in real time, but you can change the frequency with which ITM performs the following tasks:

Polling—You can change the default polling parameters for device groups, altering the polling interval, timeout, and number of retries.

Rediscovery—You can suspend the default rediscovery schedule and add different rediscovery schedules to fit your circumstances.

Confidence testing—You can change the frequency with which tests are run. In addition, you can change the range of time during which tests do not run.

Phone discovery—You can add, delete, or modify the schedules for major phone discovery.


Note Phone discovery scheduling is available only if you have downloaded and installed IDU 2 or later.


Phone reachability testing—You can set the interval for phone reachability tests.


Note Phone reachability testing is available only if you have downloaded and installed IDU 2 or later.


SRST monitoring—When you import SRST information, you set the intervals at which tests run. You can update SRST information by importing it again.


Note SRST monitoring is available only if you have downloaded and installed IDU 2 or later.


For additional information, see the following parts of this book:

Part 1, "Using ITM"

Part 3, "Configuring and Administering ITM"

ITM Performs Ongoing Monitoring, Analysis, and Notification

ITM continuously gathers information from devices and device components, analyzing and prioritizing events, and raising alerts.

Figure 1-4 ITM Continuously Monitors the IP Fabric

ITM generates alerts based on the following activities:

Polling—During polling, ITM identifies conditions that warrant generating an event, such as device unreachable or interface down.

Managing thresholds—After polling, ITM compares the data it collected against threshold values for the devices. If threshold values exceed or do not meet limits, ITM generates the appropriate event.

Receiving SNMP traps—ITM listens for traps on the default port or the port that you have configured for SNMP trap receiving. ITM will process the traps from known, supported devices.

Testing—You can configure ITM to run the following types of tests:

Confidence testing—Confidence testing of selected functions on Cisco CallManager can uncover problems that ITM reports.

IP phone reachability testing—ITM can use Cisco IOS IP SLA (IP SLA) technology to monitor the reachability of key phones in the network.


Note IP phone reachability testing is available only if you have downloaded and installed Incremental Device Update (IDU) 2 or later from the ITM download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/item-3des.


Survivable Remote Site Telephony (SRST) testing—ITM can alert you when a branch office is operating under SRST.


Note SRST testing is available only if you have downloaded and installed IDU 2 or later.


As ITM generates alerts and alert conditions change, ITM determines when to send e-mail notification to subscribers and when to generate SNMP traps to send to other systems.

For additional information, see the following topics:

MIBs Polled

Processed and Pass-through Traps, and Unidentified Traps and Events

Events Processed

Polling—SNMP and ICMP

How ITM Calculates Repeated Restarts and Flapping

Users Respond to Notifications and Alerts

Most users will monitor the condition of the IP telephony system by using the Alerts and Activities display; others will respond to e-mail. External hosts will receive generated SNMP traps. Figure 1-5 shows how you can respond using Alerts and Activities.

Figure 1-5 Users Respond to Alerts