User Guide for IP Telephony Monitor
Configuring and Administering ITM
Downloads: This chapterpdf (PDF - 253.0KB) The complete bookPDF (PDF - 5.58MB) | Feedback

Configuring and Administering ITM

Table Of Contents

Configuring and Administering ITM

Using ITM Configuration

Performing System Administration

Applying Changes

Performing Scheduling Tasks

Configuring the Daily Purging Schedule

Configuring Rediscovery Schedules

Suspending a Rediscovery Schedule

Resuming a Rediscovery Schedule

Adding a Rediscovery Schedule

Editing a Rediscovery Schedule

Deleting a Rediscovery Schedule

Configuring SNMP Trap Receiving and Forwarding

Enabling Devices to Send Traps to ITM

Enabling Cisco IOS-Based Devices to Send Traps to ITM

Enabling Catalyst Devices to Send SNMP Traps to ITM

Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs

Updating the SNMP Trap Receiving Port

Configuring SNMP Trap Forwarding

Configuring a Default SMTP Server


Configuring and Administering ITM



Note If you have ITM Multi-View, also see the "Configuring and Administering ITM Multi-View" section.


These topics provide an introduction and overview of configuration and administration tasks:

Using ITM Configuration

Performing System Administration

Applying Changes

Performing Scheduling Tasks

Configuring SNMP Trap Receiving and Forwarding

Configuring a Default SMTP Server

Using ITM Configuration

When you select IP Telephony Monitor > Configuration, IP Telephony Monitor (ITM) displays several applications and folders.


Note Your login determines which applications and folders are displayed to you. See the "Understanding Your User Role" section.


Table 14-1 lists the folders and applications, shows where you can find the instructions and procedures for using each, and provides a brief description of what you can accomplish using the application.

Table 14-1 Configuration Folder Options 

Folders and Options in the Configuration Folder
Description

Polling and Thresholds:

Polling Parameters

Managing Thresholds

Setting Priorities

See the "Configuring Polling and Thresholds" section.

From the Polling and Thresholds folder, you can:

Change polling intervals, timeouts, and retries by device group

Change thresholds, resetting the limits against which polled data will be compared

Reprioritize customizable groups for polling and thresholds

Apply Changes

See the "Performing System Administration" section.

After you apply changes, ITM configures data collectors to:

Start using updated polling parameters and threshold values

Resume polling for devices or device elements that were previously suspended

Confidence Testing

See the "Configuring Confidence Tests" section.

Establish tests for Cisco CallManager functions.

Confidence Test Schedule

See the "Scheduling Confidence Tests" section.

Change the range of hours during which confidence tests should run.

Rediscovery Schedule

See the "Configuring Rediscovery Schedules" section.

Change the rediscovery schedule. Suspend and resume rediscovery.

Group Management

See the "Managing Groups" section.

View the rules that govern system-defined device groups. Maintain customizable polling and threshold groups. Create and maintain user-defined device groups.

Daily Purging Schedule

See the "Configuring the Daily Purging Schedule" section.

Change the time at which to start purging the Fault History database.

Alerts and Activities Views

See the "Configuring Views for the Alerts and Activities Display" section.

Create views.

RME Synchronization1

See the "Using RME Synchronization" section.

Suspend or resume adding devices to ITM from RME. View devices that are in ITM but not in RME.

Logging

See the "Configuring Logging" section.

Change the level of messages written to log files.

SNMP Trap Receiving

See the "Updating the SNMP Trap Receiving Port" section.

Change the port on which ITM listens for SNMP traps.

SNMP Trap Forwarding

See the "Configuring SNMP Trap Forwarding" section.

Set a host and port number as a recipient for pass-through traps.

Default SMTP Server

See the "Configuring a Default SMTP Server" section.

Change or enter a default server to use for e-mail notifications.

1 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/cgi-bin/tablebuild.pl/item-3des.


Performing System Administration

Network Administrators, Network Operators, and System Administrators share some common interests and common tasks. The "Administering ITM" section focuses on tasks and information for the admin user or System Administrator. However, Network Administrator and Network Operators may be interested in selected topics:

Ports and Protocols that ITM Uses

Device Support

Configuring Logging

In addition, the "Performing Scheduling Tasks" section highlights the need for cooperation when scheduling database backups (a System Administrator task) and scheduling CPU-intensive activities (a Network Administrator or Network Operator task.)

Applying Changes

Changes to polling parameters and threshold values do not take effect until you apply changes, thereby reconfiguring ITM to use the new values. Similarly, after you resume devices or device components that were suspended from polling, you must apply changes for the device elements to be polled.

Before You Begin

Applying changes is a CPU-intensive event that may take between one and five minutes to complete. Therefore, to minimize system impact, consider doing the following when possible:

Consolidating changes to polling parameters and threshold values, thereby limiting the number of times you will need to apply them.

Applying changes during a low-usage time.


Note Confidence tests do not run while ITM applies changes.



Step 1 Select IP Telephony Monitor > Configuration > Apply Changes. The Apply Changes page appears.

Step 2 Click Yes to apply the changes:

If another user has already initiated applying changes, a message is displayed and changes are not applied again.

If, since the last time changes were applied, polling parameter settings or threshold values have not changed and devices have not been suspended and then resumed, changes will not be applied.


Tip

You cannot directly verify that changes have been applied. However, you can do so indirectly. For example, in response to an event, you change a threshold value and apply changes. After ITM finishes applying changes, you can see whether ITM clears the event.

For more information, see the following topics:

Viewing Events Associated with an Alert

Suspending/Resuming Devices

Configuring Polling and Thresholds

Performing Scheduling Tasks

When ITM is first installed, most tasks listed in Table 14-2 are scheduled by default to ensure that they do not run concurrently. You can configure the schedules for these tasks to meet the requirements of your site. However, you should still avoid running them concurrently.

Table 14-2 Scheduling Considerations 

Configuration Task
Default Schedule
Comments and Notes
Database purging

Run daily at midnight.

The amount of time it takes to purge the database depends on the size of the database.

Major phone discovery 1

Run daily at midnight, 04:00, 08:00, 12:00, 16:00, and 20:00.

You can determine how long the last phone discovery took to complete by comparing at the start and end times on the Collection Status page. (See the "Viewing IP Phone Discovery Status" section.) Knowing how long phone discovery normally takes to complete will help you to schedule.

Rediscovery

Run weekly on Monday at 2:00 a.m.

By default, rediscovery starts 2 hours after database purging.

Confidence testing

Run Monday through Friday from 6:00 a.m. to 6:00 p.m.

Confidence tests can be scheduled to run for up to 16 hours a day. Confidence tests should not be scheduled to run during maintenance periods on Cisco CallManagers.

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


In addition to configuring schedules with ITM, a system administrator can schedule database backups. You should be careful to coordinate the database backup schedule to avoid running concurrently with the tasks listed in Table 14-2.

For more information about schedules, see the following topics:

Configuring the Daily Purging Schedule

Configuring Rediscovery Schedules

Scheduling Confidence Tests

Backing Up and Restoring ITM Data

Scheduling Major Phone Discovery

Configuring the Daily Purging Schedule


Note Your login determines whether or not you can perform this task. See the "Understanding Your User Role" section.


Data for Fault History remains in the ITM database for 31 days. Purging occurs every day to maintain only 31 days of data. You can select the time of day that purging begins. By default, purging begins at 00:00.

Before You Begin

Review the information in the "Performing Scheduling Tasks" section to ensure that daily purging does not conflict with the other scheduled jobs listed there.


Step 1 Select IP Telephony Monitor > Configuration > Daily Purging Schedule.

Step 2 Select the Purge Time:

Hour—From 0 to 23

Minute—From 0 to 50 in ten-minute intervals

The default purge time is 00:00.

Step 3 Click the Apply button.


Tip

You can check the status of the ITM data purge job from the Job Manager page each day after the job runs. To do so, select Server Configuration > Administration > Job Management and find ITM:DataPurge under Job Type.


Note If you delete the ITM:DataPurge job using the Job Manager, purging will not resume until you restart the daemon manager, reboot the server, or reconfigure the daily purging schedule.


Configuring Rediscovery Schedules


Note Your login determines whether or not you can perform this task. See the "Understanding Your User Role" section.


ITM rediscovery probes the devices to discover their configuration and verify their manageable elements in inventory.

ITM contains a default discovery schedule that starts rediscovery on a weekly basis. Although you cannot modify the default discovery schedule, you can suspend it and add, modify, or delete additional schedules.

Suspending a Rediscovery Schedule

ITM includes a default rediscovery schedule, Default_Schedule. You cannot edit or delete Default_Schedule, but you can suspend it. To completely suspend rediscovery for a period of time, you may have to repeat this procedure to suspend more than one schedule.


Step 1 Select IP Telephony Monitor > Rediscovery Schedule.

Step 2 From the Rediscovery Schedule page, select a schedule that does not show Suspended as its status, and click the Suspend button.

Step 3 The status for the schedule changes to Suspended and the schedule does not execute again until you resume the schedule. The schedule remains listed on the Rediscovery Schedule page until you delete it.


Resuming a Rediscovery Schedule


Step 1 Select IP Telephony Monitor > Rediscovery Schedule.

Step 2 From the Rediscovery page, select a schedule with a status of Suspended and click the Resume button.

Step 3 The status for the schedule changes to Scheduled.


Adding a Rediscovery Schedule

Before You Begin

See the "Performing Scheduling Tasks" section to plan the rediscovery schedule for maximum efficiency and minimum system impact.


Step 1 Select IP Telephony Monitor > Rediscovery Schedule and click the Add button.

Step 2 Enter a name for the schedule.

Step 3 By default, Weekly is selected for Execute. Select how often the schedule should execute from the following choices:

Once

Daily

Weekly

Monthly

Step 4 Select the date, hour, and minute on which to start the rediscovery schedule and click Next.

Step 5 Review the information on the Schedule Summary: Add page and click Finish. The Rediscovery Schedule page appears, listing the new schedule.


Editing a Rediscovery Schedule

Before You Begin

See the "Performing Scheduling Tasks" section to plan the rediscovery schedule for maximum efficiency and minimum system impact.


Step 1 Select IP Telephony Monitor > Rediscovery Schedule.

Step 2 Select a rediscovery schedule with a status of Scheduled and click the Edit button.


Note You cannot edit Default_Schedule.


Step 3 You can modify how often the schedule executes and when the schedule starts:

a. If desired, select among the following choices for how often the schedule should execute:

b. If desired, select a different date, hour, and minute on which to start rediscovery.

Step 4 Click Next.

Step 5 Review the information on the Schedule Summary: Edit page and click Finish. The Rediscovery Schedule page appears, listing the modified schedule.


Deleting a Rediscovery Schedule


Step 1 Select IP Telephony Monitor > Rediscovery Schedule.

Step 2 Select a rediscovery schedule and click the Delete button. A confirmation dialog box appears.


Note You cannot delete Default_Schedule.


Step 3 Click Yes.


Configuring SNMP Trap Receiving and Forwarding

ITM can receive traps on any available port and forward them to a list of devices and ports. This capability enables ITM to easily work with other trap processing applications. However, you must enable SNMP on your devices and you must do one of the following:

Configure SNMP to send traps directly to ITM

Integrate SNMP trap receiving with an NMS or a trap daemon

To send traps directly to ITM, perform the tasks in the "Enabling Devices to Send Traps to ITM" section. To integrate SNMP trap receiving with an NMS or a trap daemon, follow the instructions in "Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs" section.

Enabling Devices to Send Traps to ITM


Note If your devices send SNMP traps to a Network Management System (NMS) or a trap daemon, see the "Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs" section.


Because ITM uses SNMP MIB variables and traps to determine device health, you must configure your devices to provide this information. For any Cisco devices that you want ITM to monitor, SNMP must be enabled and the device must be configured to send SNMP traps to the ITM server.

Make sure your devices are enabled to send traps to ITM by using the command line or GUI interface appropriate for your device:

Enabling Cisco IOS-Based Devices to Send Traps to ITM

Enabling Catalyst Devices to Send SNMP Traps to ITM

Enabling Cisco IOS-Based Devices to Send Traps to ITM

For devices running Cisco IOS software, provide the following commands:

(config)# snmp-server [community string] ro
(config)# snmp-server enable traps
(config)# snmp-server host [a.b.c.d] traps [community string]

Where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the ITM server).

For more information, refer to the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Products & Services > Cisco IOS Software.

Step 3 Select the Cisco IOS software release version used by your IOS-based devices.

Step 4 Select Technical Documentation and select the appropriate command reference guide.


Enabling Catalyst Devices to Send SNMP Traps to ITM

For devices running Catalyst software, provide the following commands:

(enable)# set snmp community read-only [community string]
(enable)# set snmp trap enable all
(enable)# set snmp trap [a.b.c.d] [community string]

Where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the ITM server).

For more information, refer to the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Products & Services > Cisco Switches.

Step 3 Select the appropriate Cisco Catalyst series switch.

Step 4 Select Technical Documentation and select the appropriate command reference guide.


Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs

You might need to complete one or more of the following steps to integrate SNMP trap receiving with other trap daemons and other Network Management Systems (NMSs):

If you are integrating ITM with a remote version of HP OpenView or NetView, you must install the appropriate adapter on the system with HP OpenView or NetView.


Note The HPOV-Net View adapters are available on the ITM download site: http://www.cisco.com/cgi-bin/tablebuild.pl/item-3des.


Add the host where ITM is running to the list of trap destinations in your network devices. See the "Enabling Devices to Send Traps to ITM" section. Specify port 162 as the destination trap port.

If another NMS is already listening for traps on the standard UDP trap port (162), you must configure ITM to use another port, such as port 9000. See the "Updating the SNMP Trap Receiving Port" section.

If your network devices are already sending traps to another management application, configure that application to forward traps to ITM.

Table 14-3 describes scenarios for SNMP trap receiving and lists the advantages of each.

Table 14-3 Configuration Scenarios for Trap Receiving 

Scenario
Advantages

Network devices send traps to port 162 of the host where ITM is running. ITM receives the traps and forwards them to the NMS.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

ITM provides a reliable trap reception, storage, and forwarding mechanism.

NMS continues to receive traps on port 162.

Network devices continue to send traps to port 162.

The NMS receives traps on default port 162 and forwards them to port 162 on the host where ITM is running.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

ITM does not receive traps dropped by the NMS.


Updating the SNMP Trap Receiving Port

By default, ITM receives SNMP traps on port 162. If you need to change the port (for example, to port 9000), you can do so.


Note If you are using ITM Multi-View, you must have Partition Administrator privileges to configure SNMP trap forwarding. If you are using ITM, you need to have Network Administrator or Network Operator privileges.



Step 1 Select IP Telephony Monitor > Configuration > SNMP Trap Receiving.

Step 2 Enter the port number in the Receiving Port entry box.

Step 3 Click Apply.


For a list of ports that are already in use, see the "Ports and Protocols that ITM Uses" section.

Configuring SNMP Trap Forwarding


Note Your login determines whether or not you can perform this task. See the "Understanding Your User Role" section.


By default, ITM does not forward unprocessed SNMP traps. However, you can configure it to do so.


Step 1 Select IP Telephony Monitor > Configuration > SNMP Trap Forwarding.

Step 2 For each host, enter:

An IP address or DNS name for the hostname.

A port number on which the host can receive traps.

Step 3 Click the Apply button.


For additional information, please see the following topics:

Ports and Protocols that ITM Uses

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

Configuring a Default SMTP Server


Note Your login determines whether or not you can perform this task. See the "Understanding Your User Role" section.


This SMTP server is used by default when you add or edit subscriptions for e-mail notifications or send e-mail notifications from the Alerts and Activities display.


Step 1 Select IP Telephony Monitor > Configuration > Default SMTP Server.

Step 2 Enter a fully qualified SMTP server name.

Step 3 Click OK.