-
User Guide for Internetwork Performance Monitor 4.0
-
Preface
-
Chapter 1 Overview of IPM
-
Chapter 2 What's New in This Release
-
Chapter 3 Adding Devices Using Device Management
-
Chapter 4 Managing IPM Operations
-
Chapter 5 Managing Collectors in IPM
-
Chapter 6 Managing Collector Groups
-
Chapter 7 Managing Admin Settings in IPM
-
Chapter 8 IPM Reports and Graphs
-
Chapter 9 IP SLA Feature Mapping
-
Chapter 10 IPM CLI Command Reference
-
Appendix A IPM 4.0 FAQs and Troubleshooting Tips
-
Appendix B : IPM 4.0 Database Schema
-
Index
-
Table Of Contents
Overview of IPM
Internetwork Performance Monitor (IPM) is a network management application that allows you to monitor the performance of multi-protocol networks. IPM monitors the network performance by configuring collectors on IP SLA (IP Service Level Agreement) capable source devices (routers) and collects the performance-related statistics from these devices.
You can use IPM to:
•
Troubleshoot problems manually by checking the network performance between devices.
•
•
•
•
•
•
•
•
•
•
This chapter contains the following topics:
Overview of Cisco IOS IP SLA
IP SLA (formerly known as SAA) is a feature built into the Cisco Internetwork Operating System (IOS) used by most Cisco routers and IOS switches. IP SLA has been available since IOS version 11.2.
In a typical IP SLA implementation, a low-end Cisco router is usually dedicated to running the operations to the various destinations. Destinations can be as simple as any IP-enabled network device or as robust as a Cisco networking device such as a router or switch, which actively participates in the IP SLA operations.
The numerical results of each IP SLA operation can be kept internally in the Cisco device (with configurable history) and accessed using the device's command line interface. The IP SLA results are also exposed to network management applications using the SNMP Protocol.
When using SNMP to collect IP SLA information, the Cisco-RTTMON-MIB can be used to translate the available SNMP Object Identifiers (OIDs).
Key Terms and Concepts
The key terms and concepts used in IPM are:
•
•
•
•
Network Performance Statistics
IPM measures the following five key network statistics:
•
•
•
•
•
Source
Originating router or switch running IOS from which IPM measures network performance. The source router or switch must be running a version of Cisco IOS software version that supports IP SLA.
For detailed information about the supported versions of the Cisco IOS software (12.1 or later), refer the IP SLA Feature Mapping.
Target
A device to which the packets are sent by the IP SLA source devices. Target devices are the destination devices for which you want to gather network performance statistics. The target devices can be any IP-addressable device or a Cisco device running the IP SLA Responder on which the source router performs IP SLA operations.
For UDP Jitter measurements, the target must be an IP SLA-capable Cisco router with RTR responder enabled. Target devices with Responder capability provides accurate measurements.
Operation
It is an IP SLA operation that is configured on the source router to measure network performance statistics such as IPEcho and IPPathEcho.
Operation Sample Interval
The frequency with which the IPM source device polls the target device to retrieve the statistics based on the IP SLA operations, configured by the user.
Collector
A collector is defined as an entity that encompasses a source router, a target device, an operation, and collector schedule details.
Collector Schedule Duration
Indicates for how long (in days, hours, and minutes) the collector runs and gathers information from the source router. The default Start Time for a Collector is Immediate; the default End Time for a Collector is Forever. The polling period is set from 00:00 hours to 00.00 hours on a daily basis.
Polling Interval
The frequency at which the IPM server polls the source router to retrieve the statistics and update the IPM database. IPM retrieves the data from the source router every hour by default. The polling interval (such as 1, 5, 15, 30, or 60 minutes) is specified while creating collectors. The default polling interval is 60 minutes.
IP SLA Responder
The component embedded in a target Cisco device running version 12.1 or later of the Cisco IOS software. It responds to IP SLA request packets from a source device and provides accurate results.
Latency
Time taken for a packet to travel from the source to target and back. It is also referred to as RTT (Round-Trip Time).
Availability
Checks the reachability of the target device based on the successful completion of the RTT operation from source to target. The availability is reported in percentages.
Jitter
Inter-packet delay between any two consecutive data packets sent from the source to target router and back.
Packet Loss
Measures the total number of packets lost while moving from source to target and back.
Report Jobs
They are jobs for which reports are scheduled to run at the specified date and time.
Report Archives
A report is archived when a scheduled report job is completed successfully and stored in archives for future reference.
Minute Reports and Graphs
These reports and graphs are generated on a minute basis. They contain statistical data for a single or a group of collectors.
Historical Reports and Graphs
These reports and graphs are generated based on the granularity, such as hourly, daily, monthly, or weekly. They contain statistical data for a single or group of collectors.
Historical/Statistical Collector Type
Collector type specified while creating a collector to archive the collector statistics in the IPM database for generating custom reports.
Monitored/Real-time Collector Type
Collector type specified while creating a collector to view the collector statistics in real time. The real-time statistics are not stored in the IPM database.
Report Granularity
Level of report detail that you want to view from the archived statistics. The various levels are Minute, Hourly, Daily, Weekly, and Monthly.
Realtime Graph
Allows you to monitor the statistics of a collector on a real-time basis.
Overlay Graph
Comparitive view of the latency of one or more collectors.
How Does IPM Work?
IPM measures and displays network performance statistics (such as latency, availability, jitter, packet loss, and error information) between a source and a target device by polling the source router. For more information, see Figure 1-1 and Figure 1-2.
Figure 1-1 IPM Process Flow
Figure 1-2 IPM WorkFlow
Access to the IPM application is through:
•
•
Overview of IPM Homepage
This section lists all the tasks that can be accomplished with Internetwork Performance Monitor (IPM) application (CiscoWorks LMS Portal > Internetwork Performance Monitor).
IPM consists of the following modules:
Collector Management
Collector Management consists of the following components:
•
•
•
•
Devices
Devices is the starting point for all IPM tasks. For IPM to work with devices, you must first add devices to Common Services' Device and Credential Repository.
IPM allows you to either select devices from Device and Credential Repository (DCR) and add the selected devices into IPM.
You can also automatically add devices to IPM by selecting the Automatically Manage Devices from Credential Repository option in the Internetwork Performance Monitor > Admin > Application Settings page.
You can add adhoc devices into IPM space directly as targets. However, the adhoc devices are not listed in DCR.
IPM devices can be either source or target.
•
The source devices are listed under Source Device Selector on the Create Collector page. This list contains only IP SLA capable devices under the respective MDF categories.
•
Note
You can perform the following tasks in the Devices, refer Table 1-1.
Operations
IP SLA is a portfolio of technology embedded in most devices that run Cisco IOS software, which allows you to analyze IP service levels for IP applications and services, to increase productivity, to lower operational costs, and to reduce the frequency of network outages.
IP SLA uses active traffic monitoring (the generation of traffic in a continuous, reliable, and predictable manner) to measure network performance.
IPM supports the following IP SLA operations:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
–
–
–
–
You can perform the following tasks in the Operations, refer Table 1-2.
Collectors
A collector is defined as an entity that encompasses a source router, a target device, an operation, and a collector schedule. For more information, see Key Terms and Concepts.
You can perform the following tasks in Collectors, refer Table 1-3.
Group Administration
Grouping collectors and working with groups provides convenience to you in selecting required collectors. You can define several groups of collectors based on a set of criteria and manage the same.
You can perform the following tasks in Group Administration, refer Table 1-4.
Reports
The Reports module allows you to manage report archives, report jobs, audit reports, and system reports (Internetwork Performance Monitor > Reports).
The Reports module contains:
Report Archives
Report Archives allows you to manage the archived reports and create report jobs. The report jobs are created based on the report types (Availability, Latency, Jitter, HTTP, ICMP, PathEcho, and RTP) and granularity (Daily, Hourly, Weekly, or Monthly).
You can view the following reports and graphs for the report types:
•
•
You can perform the following tasks in Report Archives, refer Table 1-5.
Report Jobs
The Report Job Browser page allows you to manage the report jobs.
You can perform the following tasks in Report Jobs, refer Table 1-6.
Audit Reports
Audit reports track all configuration changes on the IPM server by the LMS users. You can generate audit reports (Internetwork Performance Monitor > Reports > Audit Reports).
System Reports
The system generates statistical reports for collectors based on the parameters, namely, Availability, Latency, Jitter, HTTP, ICMP, PathEcho, and RTP. The reports are generated on a daily, weekly, and monthly basis. The reports generated are in tabular format.
You can perform the following tasks in System Reports, refer Table 1-7.
Administration
The Admin module allows you to set system-wide parameters for IPM such as log level settings, auto update from DCR, purge historical and audit reports, copy IP SLA configuration to running-config, and managed source interface settings.
You can perform the following tasks in Administration, refer Table 1-8.
