user manual
Table Of Contents
- User Guide for Internetwork Performance Monitor
- Contents
- Preface
- Overview of IPM
- Getting Started With IPM
- Using IPM to Measure Network Performance
- Measuring Network Performance for DHCP
- Measuring Network Performance for DLSw
- Measuring Network Performance for DNS
- Measuring Network Performance for HTTP
- Measuring Network Performance for FTP
- Measuring Network Performance for IP
- Measuring Network Performance for SNA
- Measuring Network Performance for TCP
- Measuring Network Performance for UDP
- Measuring Network Performance for Enhanced UDP
- Modifying IPM Components
- Working With Source Devices
- Working With Target Devices
- Working With Operations
- Working With Collectors
- Adding Components Using Seed Files
- Changing IP Addresses
- Setting the Baseline
- Setting IPM Database Preferences
- Setting SNMP Timeout and Retry Environment Variables
- Setting New IPM Server Process Timeout Values
- Setting the DISPLAY Variable in Solaris
- Backing Up or Restoring the IPM Database
- NVRAM Settings
- Managed Source Interface Settings
- Changing Administrative Password
- Changing IPM Database Password
- Working With Message Log Window
- Working With IPM From the CiscoWorks Homepage
- Accessing IPM Data From the CiscoWorks Homepage
- Viewing IPM Server Information
- Importing Devices From Device and Credential Repository
- Downloading the IPM Client
- Viewing Configuration Information
- Viewing Latency Data
- Viewing Jitter Data
- Viewing HTTP Data
- Accessing Software Updates and Additional Information
- IPM FAQs and Troubleshooting Tips
- IPM Command Reference
- SA Agent Feature Mapping
- Glossary
- Index

3-33
User Guide for Internetwork Performance Monitor
OL-11291-01
Chapter 3 Using IPM to Measure Network Performance
Measuring Network Performance for TCP
Measuring Network Performance for TCP
IPM’s TCP Connect operation measures round-trip latency between a source and any IP-enabled device
running TCP services. Latency is computed by measuring the time taken by the source to perform a TCP
connect operation to the target device. This operation is useful for simulating Telnet or HTTP connection
times. The TCP operation also measures availability and errors for TCP services.
You can specify any port number, well known or otherwise, on any IP host, Cisco or non-Cisco, as long
as someone is listening on that port on the target. A well known port is a port number less than or equal
to 1024 (for example, 21 for FTP, 23 for Telnet, and 80 for HTTP). IPM provides default TCP
Connection operations for several of these common TCP services.
To measure end-to-end latency for TCP:
Step 1 Define a device as the source device from which to measure performance. For details on defining a
source device, see Defining a Source Device.
Step 2 Define a device as the target of connection requests from the source device. For details on defining a
target, see Defining a Target.
To control how statistics are collected, use one of the default operations for TCP or define your own TCP
operation. For details on defining a TCP operation, see Defining a TCP Operation.
Step 3 Define a collector to measure performance between the source router and target you defined. For details
on defining a collector, see Defining a Collector. If you set the collector’s schedule to On Demand, start
the collector when needed.
Step 4 View the statistics in the TCP Historical Statistics window. For details on viewing end-to-end statistics
for TCP, see Viewing Statistics for TCP.
Defining a TCP Operation
IPM provides several default TCP operations for measuring performance between a source and target.
In addition, IPM provides the option to create, modify, or delete your own TCP operations from the TCP
Operation Configuration window.
To define a TCP operation:
Step 1 From the IPM Main Window, select Edit > Configuration.
The Configuration window appears.
Step 2 Click Operation.
The Operation Configuration window appears within the Configuration window.
Step 3 Click TCP Connect
The TCP Operation Configuration window (Figure 3-20) appears.