User Guide for Internetwork Performance Monitor 4.0.1 (With LMS 3.0 December 2007 Update) - Chapter 4 : IPM Operation Management [CiscoWorks Internetwork Performance Monitor]

Table Of Contents

Managing IPM Operations

Overview of IP SLA Operations

Understanding the List of Operations in IPM

Overview of List of Operations Page

Viewing the List of Defined Operations

Creating User-Defined Operations

General Settings for a User-Defined Operation

Specific Settings for a User-Defined Operation

Viewing the Summary of a User-Defined Operation

Editing User-Defined Operations

Deleting User-Defined Operations

Viewing Operation Properties

Using IP SLA Operations to Measure Network Performance

Measuring Network Performance for IP

Measuring End-to-End Performance for Echo

Defining an Echo Operation

Measuring Hop-by-Hop Performance for Path Echo

Defining a Path Echo Operation

Measuring Network Performance for UDP Echo

Defining a UDP Echo Operation

Measuring Network Performance for ICMP Jitter

Defining an ICMP Jitter Operation

Measuring Network Performance for UDP Jitter

Defining a UDP Jitter Operation

Measuring Network Performance for RTP

Defining an RTP Operation

Measuring Network Performance for Call Setup Post Dial Delay

Defining a Call Setup Post Dial Delay Operation

Measuring Network Performance for Gatekeeper Registration Delay

Defining a Gatekeeper Registration Delay Operation

Measuring Network Performance for DNS

Defining a DNS Operation

Measuring Network Performance for DHCP

Defining a DHCP Operation

Measuring Network Performance for HTTP

Defining an HTTP Operation

Measuring Network Performance for FTP

Defining an FTP Operation

Measuring Network Performance for DLSw

Defining a DLSw Operation

Measuring Network Performance for TCP Connect

Defining a TCP Connect Operation

Managing IPM Operations

This chapter provides details on using IPM to measure latency, jitter, availability, and errors. It contains the following topics:

•Overview of IP SLA Operations

•Understanding the List of Operations in IPM

•Using IP SLA Operations to Measure Network Performance

Overview of IP SLA Operations

IP SLA is a portfolio of technology embedded in most devices that run Cisco IOS software. This 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—for measuring network performance.

IPM supports the following IP SLA operations:

•Echo Operations

–Echo

–Path Echo

–UDP Echo (User Data Protocol)

•Jitter Operations

–ICMP Jitter (Internet Control Message Protocol)

–UDP Jitter (User Data Protocol)

•VoIP Operations

–Call Setup Post Dial Delay

–Gatekeeper Registration Delay

–RTP (Real-time Transfer Protocol)

•Operation based on Services

–DNS (Domain Name System)

–DHCP (Dynamic Host Configuration Protocol)

–HTTP (HyperText Transfer Protocol)

–FTP (File Transfer Protocol)

–DLSw (Data-link Switching)

–TCP Connect

For IPM operations, the IPM Request size does not include the size of the headers added by the respective layers. The header size varies according to the type of the IP SLA operation. The overhead added by different layers are as follows:

•TCP Layer - 20 bytes

•UDP Layer - 8 bytes

•IP Layer - 20 to 60 bytes

•ICMP Layer - 8 bytes

•IP SLA - 8 bytes

Predefined IP SLA Operations

When you install IPM, a group of predefined operations are provided. Table 4-1 describes the predefined operations.

You can define one or more new operations to fit your needs. Although, you cannot modify the default operations, you can use them as templates for creating your own operations.

Note IPM does not provide a predefined HTTP, FTP, or RTP operation. Therefore, before you create a HTTP, FTP, or RTP collector, you must first create the respective HTTP, FTP, or RTP operation.

Table 4-1 Predefined Operations

Operations

Description

Echo Operations

Default Echo

Measures end-to-end latency in an IP network. Protocol is set to IP, Packet Priority is set to 0 (no priority), and Request Payload is set to 64 bytes.

IPM supports the following default echo operations:

•DefaultIpEcho

•DefaultIpEchoPri3

•DefaultIpEchoPri7

Default Path Echo

Measures hop-by-hop latency in an IP network.

•Packet Priority is set to 0 (no priority)

•Request Payload is set to 64 bytes

•Maximum Paths is set to 5

•Maximum Hops is set to 15

•Sample interval is set to 180 seconds

This operation is denoted as `DefaultIpPathEcho'.

Default UDP Echo

Measures end-to-end latency for a UDP datagram. Packet Priority is set to 0 (no priority), Request Payload is set to 64 bytes, and Target Port is set to 7.

This operation is denoted as `DefaultUDPEcho'.

Jitter Operations

Default ICMP Jitter

Measures network performance by generating a stream of ICMP packets between a Cisco IOS device (source) and IP device (destination).

You need not use Responder Enabled target device for this jitter operation since this is mainly used for non-Cisco devices.

This operation is denoted as `DefaultICMPJitter'.

Default UDP Jitter

Measures round-trip latency, packet loss, and jitter in IP networks by generating synthetic UDP traffic.

You must use Responder Enabled target devices for this operation.

IPM supports the following default UDP jitter operations:

•Default60ByteVoice

•Default160ByteVoice

•DefaultVPN

•DefaultVideo

Default VOIP Post Dial Delay

Measure your network's response time for setting up a Voice over IP (VoIP) call.

This operation is denoted as `CallSetupPostDialDelay'.

Default VOIP Gatekeeper Registration Delay

Measures the average, median, or aggregated response time (delay) of registration attempts from a VoIP source router to a VoIP gatekeeper device.

This operation is denoted as `GatekeeperRegistrationDelay'.

Operations based on services

Default DNS

Measures end-to-end latency for DNS lookups. DNS Name Server is set to the IP address of the DNS server configured on the system on which the IPM server is running. The DNS Lookup Name is set to the name of the host to look up for the DNS request.

When you create a non-default operation, it is mandatory to specify a DNS Name Server.

This operation is denoted as `DefaultDNS'.

Default DHCP

Measures end-to-end latency for acquiring a new DHCP lease.

This operation is denoted as `DefaultDNS'.

Default DLSw

Measures end-to-end latency in a network which uses DLSw to route SNA traffic over an IP network. Request size is set to 64 and Response Payload is set to 64.

This operation is denoted as `DefaultDLSw'.

Default TCP Connect

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.

IPM supports the following default TCP Connect operations:

•DefaultSMTP

•DefaultPOP3

•DefaultTelnet

•DefaultNNTP

Understanding the List of Operations in IPM

This section explains how to manage the IP SLA operations.

It contains the following topics:

•Overview of List of Operations Page

•Viewing the List of Defined Operations

•Creating User-Defined Operations

•Editing User-Defined Operations

•Deleting User-Defined Operations

•Viewing Operation Properties

Overview of List of Operations Page

The List of Operations page (Table 4-2) lists all the operations in IPM (Internetwork Performance Monitor > Collector Management > Operations). This page contains the following pane, icon, and buttons:

Table 4-2 List of Operations Page

Pane/Buttons

Description

List of Operations

Lists all operations in IPM.

The operations are identified by the Operation Name that you have entered while creating them.

Filter

Filters the list of operations based on the following:

•All

•Operation Name

•Operation Type

•Create Type

For more information, see Filtering List of Operations

Create

Allows you to create a user-defined operation.

For more information, see Creating User-Defined Operations.

Edit

Allows you to edit a user-defined operation.

For more information, see Editing User-Defined Operations.

Delete

Allows you to delete user-defined operations.

For more information, see Deleting User-Defined Operations.

View

Allows you to view the details of a system-defined or user-defined operation.

For more information, see Viewing Operation Properties.

Allows you to refresh the list of operations.

Viewing the List of Defined Operations

The List of Operations page allows you to view the list of system-defined and user-defined operations and filter the list of operations.

To view the list of defined operations, select Internetwork Performance Monitor > Collector Management > Operations from CiscoWorks LMS Portal.

The List of Operations page appears with the list of system-defined and user-defined operations.

Filtering List of Operations

Using the Filter field in the List of Operations page, you can filter the operations. You can filter the operations using one of the following fields and clicking Filter. For more information, see Table 4-3.

Table 4-3 Filtering List of Operations Page

Fields for Filtering

Description

All

Displays all operations.

Operation Name

Enter the complete or part of the Operation name that you want to display.

Operation Type

Enter the complete or part of the Operation type that you want to display.

The operation types available are:

•Echo

•PathEcho

•UDPEcho

•ICMPJitter

•UDP Jitter

•CallSetupPostDialDelay

•GatekeeperRegistrationDelay

•RTP

•DNS

•DHCP

•HTTP

•FTP

•DLSw

•TCPConnect

Create Type

Enter the complete or part of the Create type that you want to display.

The Create types available are:

•System Defined

•User Defined

Example 1:

If you want to filter the Operations based on Operation Type and with value UDP:

1. From the Filter Drop down, select Operation Type.

2. In the Fiter text area enter UDP

3. Click Filter

By default the filter operation uses "contains" to filter the Operations. All those Operation Types that contain the value UDP are filtered and provided in the results:

UDPJitter

UDPEcho

Example 2:

If you want to filter the Operations based on Operation Name and with value Default:

1. From the Filter Drop down, select Operation Name.

2. In the Fiter text area enter Default

3. Click Filter

By default the filter operation uses "contains" to filter the Operations.

All those Operation Names that contain the value Default are filtered and provided in the results:

DefaultVideo

DefaultVPN

EchoDefault

Example 3:

Let us say, you want to filter the Operations based on Create Type and with value SYSTEM:

1. From the Filter Drop down, select Create Type.

2. In the Fiter text area enter SYSTEM

3. Click Filter

By default the filter uses "contains" to filter the Operations.

All the System Defined operations are filtered and provided in the results.

Creating User-Defined Operations

IPM provides a single wizard-based approach that leads you through the procedure to create multiple user-defined operations. While creating these operations, you can use the system-defined operation template and modify only the required parameters for that operation.

This wizard process involves the following four steps:

•General Settings for a User-Defined Operation

•Specific Settings for a User-Defined Operation

•Viewing the Summary of a User-Defined Operation

You must complete all the four tasks in this sequence to create user-defined operations. If you exit the wizard at any stage using Cancel, the details you have specified will be lost and the user-defined operation will not be created.

General Settings for a User-Defined Operation

The General Settings page allows you to define operation details, and threshold, timeout, and miscellaneous settings.

To specify the general settings for a user-defined operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Specify the following in the Details section:

•Name—Enter an operation name.

•Description—Enter a brief description of the operation, including its purpose.

•Type—Select the operation type from the drop-down list.

For more information, see Using IP SLA Operations to Measure Network Performance.

Step 4 Specify the following in the Threshold Settings section:

•Generate Action Event—Select one of the algorithms to be used by IPM to calculate threshold violations:

–Never—Do not calculate threshold violations. This is the default setting.

–Immediate—When the latency exceeds the rising threshold or drops below the falling threshold, immediately perform the action defined by Action Event Type.

–Consecutive—When the latency exceeds the rising threshold or drops below the falling threshold X times consecutively, perform the action defined by Action Event Type.

Optionally, specify the number of consecutive occurrences. The default is 5.

–X of Y—When the latency exceeds the rising threshold or drops below the falling threshold X out of the last Y times, perform the action defined by Action Event Type.

Optionally, specify the number of violations that must occur within a specified number. Valid values for both the x-value (X) and y-value (Y) are 1 through 16. The default is 5 for both values.

–Average—When the average of the last X completion latency values exceeds the rising threshold or drops below the falling threshold, perform the action defined by Action Event Type.

Optionally, specify the number of operations to average. The default is the average of the last 5 latency operations.

•Action Event Type—Select the action event type as None or SNMP Trap from the drop-down list.

•Rising Threshold (msecs)—Enter a value for rising threshold in milliseconds. The value entered should be greater than the Falling Threshold value.

Valid values are between 1 and 99999 milliseconds. The default is 5000 milliseconds.

When the average round-trip time exceeds the rising threshold, the collector uses the algorithm specified in Generate Action Event to determine if a threshold violation has occurred. If a violation occurs, the action defined in Action Event Type is taken.

However, for UDP Jitter and ICMP Jitter, the rising threshold values apply to the average jitter data.

•Falling Threshold (msecs)—Enter a value for falling threshold in milliseconds. The value entered should be greater than the Timeout value.

Valid values are between 0 and 99999 milliseconds. The default value is 3000 milliseconds.

When the average round-trip time falls below the falling threshold, the threshold is reset. Only one event is generated for the time the average round-trip time is above the rising threshold.

However, for UDP Jitter and ICMP Jitter, the falling threshold values apply to the average jitter data.

•X Occurrences of Y Samples—When the latency exceeds the rising threshold or drops below the falling threshold X out of the last Y times, perform the action defined by Action Event Type.

Optionally, you can specify the number of violations that must occur as given below:

–X—Specify the number of violations that must occur within a specified number. The default value is 5. Valid values ranges between 1 and 16.

–Y—Specify the number of violations that must occur within a specified number. The default value is 5. Valid values ranges between 1 and 16.

Step 5 Specify the following in the Timeout Settings section:

•Timeout Value (msecs)—Enter the amount of time in milliseconds for the collector to wait for a response to its echo operation. The default value is 5000 for all operations.

•Enable Timeout Action—Enable the Timeout Value option to check for latency reporting operation time-outs based on the timeout value configured.

You can configure IPM to notify source router to raise a trap when a threshold violation/timeout occurs. However, you should configure a separate NMS to receive and process these traps.

Step 6 Specify the Sample Interval (seconds) in the Miscellaneous Settings section. The source router uses the specified value to collect data. For more information on the Sample Interval, see Operation Sample Interval.

The valid values are 10 to 3600 (1 hour). The default is 60 seconds.

Step 7 Click Next.

The Specific Settings page appears.

Specific Settings for a User-Defined Operation

The Specific Settings page allows you to define the specific settings for an operation. The specific setting differs for each operation type.

To know the specific settings for a particular operation, click the required link. The list of links is given below:

•Measuring Network Performance for DHCP

•Measuring Network Performance for DNS

•Measuring Network Performance for FTP

•Measuring End-to-End Performance for Echo

•Measuring Hop-by-Hop Performance for Path Echo

•Measuring Network Performance for HTTP

•Measuring Network Performance for DLSw

•Measuring Network Performance for UDP Echo

•Measuring Network Performance for UDP Jitter

•Measuring Network Performance for ICMP Jitter

•Measuring Network Performance for Gatekeeper Registration Delay

•Measuring Network Performance for Call Setup Post Dial Delay

•Measuring Network Performance for RTP

•Measuring Network Performance for TCP Connect

To assign specific settings for a user-defined operation:

Step 1 Specify the following in the Packet Settings section:

•IP QoS Type—Select IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Request Payload (bytes)—Enter the number of bytes to specify the payload size of the request packet. The default setting is 64 bytes.

Step 2 Select the Loose Source Routing (LSR) check box to enter LSR Hop Addresses.

Step 3 Click Next.

The Summary page appears with the details of the user-defined operation.

Viewing the Summary of a User-Defined Operation

The Summary page allows you to view the details of the user-defined operation you have created.

To view the summary of a user-defined operation:

Step 1 Click Finish.

A message appears that the operation is created successfully.

Step 2 Click OK.

The List of Operations page appears.

Or

Click Back.

Allows you to modify the general and specific settings of the operation defined on the General Settings and Specific Settings pages.

Editing User-Defined Operations

You can edit all parameters of a user-defined operation except the name and type of operation. You cannot edit the system-defined operations.

Note An error message appears if you try to delete the operation of a running collector.

To edit a user-defined operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Select an operation that you want to edit.

Step 3 Click Edit.

The General Settings page appears.

Step 4 Modify the required fields in the General Settings page.

Note You can modify only the fields in the Threshold Settings, Timeout Settings, and Miscellaneous Settings sections. You cannot modify the Details section.

For more information, see General Settings for a User-Defined Operation.

Step 5 Click Next.

The Specific Settings page appears.

Step 6 Modify the required fields in the Specific Settings page.

For more information, see Specific Settings for a User-Defined Operation.

Step 7 Click Next.

The Summary page appears with the details of the operation that you have updated.

Step 8 Click Finish to update the changes made.

Deleting User-Defined Operations

You can delete user-defined operations that you no longer need. However, you cannot delete an operation if that operation is currently used by a collector. In that case, you must delete the collector first and then delete the operation. You can delete more than one operation at a time.

Note You cannot delete the default operations provided with IPM.

To delete IPM user-defined operations:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Select the operations that you want to delete.

Step 3 Click Delete.

The Delete Confirmation dialog box appears.

An error message appears if you try to delete operations that are currently used by a collector.

Step 4 Click OK.

The selected operations are deleted from the IPM database.

Viewing Operation Properties

The Operation Properties window allows you to view the properties of a defined operation.

To view operation properties:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Select an operation for which you want to view the properties.

Step 3 Click View.

The Operation Properties window appears with the information on general setting, threshold settings, timeout settings and specific settings for the selected operation.

For more information on the general settings for each Operation, see:

General Settings for a User-Defined Operation

For more information on the specific settings for each Operation, see:

•Defining an Echo Operation for Echo Operation

•Defining a Path Echo Operation for Path Echo Operation

•Defining a UDP Echo Operation for UDP Echo Operation

•Defining an ICMP Jitter Operation for ICMP Jitter Operation

•Defining a UDP Jitter Operation for UDP Jitter Operation

•Defining an RTP Operation for RTP Operation

•Defining a Call Setup Post Dial Delay Operation for Call Setup Post Dial Delay Operation

•Defining a Gatekeeper Registration Delay Operation for Gatekeeper Registration Delay Operation

•Defining a DNS Operation for DNS Operation

•Defining a DHCP Operation for DHCP Operation

•Defining an HTTP Operation for HTTP Operation

•Defining an FTP Operation for FTP Operation

•Defining a DLSw Operation for DLSw Operation

•Defining a TCP Connect Operation for TCP Connect Operation

Using IP SLA Operations to Measure Network Performance

IPM allows you to measure the network performance using the following IP SLA operations:

•Measuring Network Performance for IP

•Measuring Network Performance for UDP Echo

•Measuring Network Performance for ICMP Jitter

•Measuring Network Performance for UDP Jitter

•Measuring Network Performance for RTP

•Measuring Network Performance for Call Setup Post Dial Delay

•Measuring Network Performance for Gatekeeper Registration Delay

•Measuring Network Performance for DNS

•Measuring Network Performance for DHCP

•Measuring Network Performance for HTTP

•Measuring Network Performance for FTP

•Measuring Network Performance for DLSw

•Measuring Network Performance for TCP Connect

Measuring Network Performance for IP

In an IP network there are two types of measurements that you can take:

•Echo or Ping Echo—Measures the total round-trip latency from the source to the target device. The IP SLA feature in the source router issues an Internet Control Message Protocol (ICMP) ping to the target device and extracts the latency data from the reply.

For more information, see Measuring End-to-End Performance for Echo.

•Path Echo or Ping Path Echo—Measures the total round-trip latency as well as the incremental latency for each hop in all paths between the source router and the target device. Path Echo is available only for the IP protocol.

The IP SLA feature first issues a traceroute command to determine the path through the network from the specified source to the specified target device.

The data returned from the traceroute command contains the host name or IP address of each of the routers in the path. IP SLA then issues ICMP pings to each of the routers listed in the traceroute data.

The ICMP ping returns statistics regarding the latency, availability, and errors between the specified source and each of the routers.

For more information, see Measuring Hop-by-Hop Performance for Path Echo.

Measuring End-to-End Performance for Echo

Echo or Ping Echo operation measures end-to-end performance between a source and any IP-enabled device.

Latency is computed by measuring the time taken between sending an ICMP echo request message to the destination and receiving an ICMP echo reply. The Echo operation also measures availability and errors for IP services.

With an Echo operation, you can determine performance on a specific path by using Loose Source Routing.

Additionally, IPM provides an option for measuring quality of service (QoS) between endpoints by setting the DSCP and the type of service (ToS) bits on the IP packet.

To measure end-to-end performance for Echo:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a Ping Echo server as a target device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Define a Ping Echo operation. Use DefaultIPEcho operation or customize a Echo operation.

For details on defining a Ping Echo operation, see Defining an Echo Operation.

Step 4 Define a collector to measure performance between the source and target.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the Echo statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining an Echo Operation

IPM provides three default Echo operations namely DefaultIpEcho, DefaultIpEchoPri3, DefaultIpEchoPri7 for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own Echo operations from the List of Operations page.

To define an Echo operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select Echo operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type—Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the QoS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Request Payload (bytes)—Enter the number of bytes in the Request Payload field to use for the size of the payload of the ICMP echo request packet. The default setting is 64 bytes.

Step 6 Enable the Loose Source Routing option to measure performance for a specific path and add the hops for the operation to use. You can enter a maximum of eight hops.

Step 7 Click Finish.

The newly defined Echo operation is successfully created.

An error message appears if the Create operation fails.

Measuring Hop-by-Hop Performance for Path Echo

IPM's Path Echo or Ping Path Echo operation determines hop-by-hop performance between a source and target device on the network by discovering the path. Path Echo uses traceroute and then measures performance between the source and each intermittent hop in the path.

If there are multiple equal cost routes between the source and the target, the Path Echo operation can identify the correct path by using Loose Source Routing (if the option is enabled on the intermediate hop devices).

This feature enables IP SLA to discover paths more accurately compared to a regular traceroute. The Path Echo operation also measures availability and errors for IP services.

To measure hop-by-hop performance for Path Echo:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of Path Echo requests from the source device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Define a Path Echo operation. Use the DefaultIPPathEcho operation or customize a Path Echo operation.

For details on defining a Ping Path Echo operation, see Defining a Path Echo Operation.

Step 4 Define a collector to measure performance between the source and target.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the Path Echo statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a Path Echo Operation

IPM provides a default Path Echo operation for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own Path Echo operations from the List of Operations page.

To define a Path Echo operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select PathEcho operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type—Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the QoS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Request Payload (bytes)—Enter the number of bytes in the Request Payload field to use for the size of the payload of the ICMP echo request packet. The default setting is 64 bytes.

Step 6 Specify the following in the Path Settings section:

•Maximum Path—Enter a value to specify the maximum number of paths to discover. The valid range is 1 to 128 paths. The default setting is 5.

To ensure that you do not miss collecting statistics for relevant paths, set this value to a number slightly higher than the expected number of paths.

•Maximum Hops—Enter a value to specify the maximum number of hops to discover. The valid range is 1 to 25 hops. The default setting is 10 hops.

To ensure that you do not miss collecting statistics for relevant hops, set this value to a number slightly higher than the expected number of hops.

Step 7 Click Next.

The Summary page appears with the details of the operation created.

Step 8 Click Finish.

The newly defined Path Echo operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for UDP Echo

IPM's UDP Echo operation measures round-trip latency between a source and any IP-enabled device running UDP services. Latency is computed by measuring the time taken to send a datagram and receive a response from the target device. The UDP operation also measures availability and errors for UDP services.

To measure end-to-end performance for UDP Echo:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of connection requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Define a UDP operation. Use the DefaultUDPEcho operation or customize a UDP Echo operation.

For details on defining an UDP Echo operation, see Defining a UDP Echo Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the UDP Echo statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a UDP Echo Operation

IPM provides a default UDP Echo operation for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own UDP Echo operations from the List of Operations page.

To define a UDP Echo operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select UDPEcho operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Specific Settings section:

•IP QoS Type— Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Request Payload (bytes)—Enter the number of bytes to use for the size of the payload of the request packet. The default setting is 64 bytes.

Step 6 Specify the UDP Echo port number in the Port Settings section.

The target device uses this port number when sending response packets. Valid values are 7, and 1025 to 65535. The default setting is 7.

•If the target device is a Cisco router running version 12.1 or later of the Cisco IOS software, you can specify any port that is not well known.

That is, you can specify any port number greater than 1024 to communicate with the IP SLA Responder, as long as someone is listening on that target port. The only allowed well known port is UDP port 7.

•If the target is not running version 12.1 or later of the Cisco IOS software, whether a Cisco or a non-Cisco IP host, you must specify UDP port 7 as the target port.

Step 7 Click Next.

The Summary page appears with the details of the operation created.

Step 8 Click Finish.

The newly defined UDP operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for ICMP Jitter

The ICMP Jitter generates a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics namely latency, round-trip time, jitter (interpacket delay variance), and packet loss.

The destination device can be any network device that supports ICMP such as a server or workstation. ICMP does not require IP SLA responders to be configured on the destination devices.

ICMP provides:

•End-to-end performance measurements between a Cisco device (source) and any IP device (destination) using ICMP.

•Proactive threshold violation monitoring through Simple Network Management Protocol (SNMP) trap notifications and syslog messages.

To measure end-to-end performance for ICMP Jitter:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of discovery requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Define a ICMP Jitter operation. Use the DefaultICMPJitter operation or customize a ICMP Jitter operation.

For details on defining an ICMP operation, see Defining an ICMP Jitter Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the ICMP Jitter statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining an ICMP Jitter Operation

IPM provides a default ICMP Jitter operation for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own ICMP Jitter operations from the List of Operations page.

To define an ICMP Jitter operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select ICMPJitter operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type—Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Packet Interval (msecs)—Enter the number of milliseconds to use for the interpacket delay between packets sent from the source router to the target router. The default setting is 20 milliseconds.

•Number of Packets—Enter the number of packets to send to the target to measure latency. The default setting is 10 packets.

Step 6 Click Next.

The Summary page displays the operation details that you have created.

Step 7 Click Finish.

The newly defined ICMP Jitter operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for UDP Jitter

The UDP Jitter operation for Voice over IP measures round-trip latency, packet loss, and jitter in IP networks by generating synthetic UDP traffic. The UDP Jitter operation sends a defined number of packets of a defined size from the source to a target with a defined interpacket delay.

Both the source and the target must be running version 12.1 or later of the Cisco IOS software, and the SA Agent responder must be enabled on the target.

To enable the SA Agent Responder on the target, use the rtr responder IOS configuration command. The packets sent out to measure jitter contain packet sequence information, as well as sending and receiving timestamps from the source and the Responder.

Note The UDP Jitter operation sends only UDP data traffic, and does not send any voice packets.

The UDP Jitter operation measures the following network performance statistics:

•Round-trip network latency

•Per-direction packet loss

•Per-direction interpacket delay variance (jitter)

•Network availability and errors

The MOS and ICPIF are values that are obtained when collectors are configured with UDP Jitter operations that have codec types other than None. The UDP Jitter with VoIP operation is present only in versions 12.3(14)T and above. The definitions of MOS and ICPIF are given below:

•MOS

Mean Opinion Score provides a numerical measure of the voice quality in the network. It is expressed as a single number in the range 1 to 5, where 1 is lowest perceived quality, and 5 is the highest perceived quality.

•ICPIF

Calculated Planning Impairment Factor loss/delay busyout threshold. The ICPIF numbers represent predefined combinations of loss and delay. Packet loss and delay determine the threshold for initiating the busyout state. Table 4-4 shows the resulting MOS values that will be generated for corresponding ICPIF values.

Table 4-4 Correspondence of ICPIF Values to MOS Values

ICPIF Range

MOS

Quality Category

0 - 3

5

Best

4 - 13

4

High

14 - 23

3

Medium

24 - 33

2

Low

34 - 43

1

Poor

To measure end-to-end performance for UDP Jitter:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of discovery requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Define an UDP Jitter operation. Use one of the default UDP Jitter operations or customize a UDP Jitter operation.

For details on defining an UDP Jitter operation, see Defining a UDP Jitter Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the UDP Jitter statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a UDP Jitter Operation

IPM provides several default UDP Jitter operations for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own UDP Jitter operations from the List of Operations page.

To define an UDP operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select an UDP Jitter operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Codec/ICPIF Settings section:

•Target Port—Enter the UDP Jitter port number. The target device uses this port number when sending a response packet.

Valid values range from 1 to 65536. The default setting is 16400 for Voice, 2000 for VPN, and 50505 for Video.

The Target Port should be a even number if you have selected the Codec Types g711alaw, g711ulaw, or g729a.

•Codec Type—Select the codec type keywords from the drop-down list.

It enables the generation of estimated voice quality scores in the form of Calculated Planning Impairment Factor (ICPIF) and Mean Opinion Score (MOS) values. The codec type should match the encoding algorithm that you are using for VoIP transmissions.

–Codec type g711alaw—The G.711 A-Law codec (64 kbps transmission).

–Codec type g711ulaw—The G.711 muHmm-Law codec (64 kbps transmission).

–Codec type g729a—The G.729A codec (8 kbps transmission).

The default codec type is None.

•Advantage Factor—Select the advantage factor from the drop-down list. It specifies the expectation factor to be used for ICPIF calculations.

This value is subtracted from the measured impairments to yield the final ICPIF value (and corresponding MOS value). The valid values range from 0 to 20. The default value is 0.

Table 4-5 depicts the Advantage Factor Recommended Maximum values:

Table 4-5 Advantage Factor Recommended Maximum Values

Communication Service

Advantage/Expectation Factor:

Maximum value of A

Conventional wire-line (land-line)

0

Mobility (cellular connections) within a building

5

Mobility within a Geographical area or moving in a vehicle

10

Access to hard-to-reach location;

(for example, via multi-hop satellite connections)

20

Step 6 Specify the following in the Packet Settings section:

•IP QoS Type—Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

•Request Payload (bytes)—Enter the number of bytes to use for the size of the payload of the UDP request packet. The default setting is one of the following values:

–60 bytes for Default60ByteVoice operations

–160 bytes for Default160ByteVoice operations

–1024 bytes for DefaultVPN and DefaultVideo operations

•Packet Interval (msecs)—Enter the number of milliseconds to use for the interpacket delay between packets sent from the source router to the target router. The default setting is 20 milliseconds.

•Number of Packets—Enter the number of packets to send to the target to measure latency. The default setting is 10 packets.

Step 7 Click Next.

The Summary page displays the operation details that you have created.

Step 8 Click Finish.

The newly defined UDP Jitter operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for RTP

The IP SLA Real-Time Transport Protocol (RTP)-based Voice over IP (VoIP) Operation feature provides the capability to set up and schedule a test call and use Voice source router digital signal processors (DSPs) to gather network performance-related statistics for the call.

Available statistical measurements for VoIP networks include jitter, frame loss, Mean Opinion Score for Conversational Quality (MOS-CQ), and Mean Opinion Score for Listening Quality (MOS-LQ).

The IP SLAs RTP-Based VoIP Operation provides:

•End-to-end performance measurements using DSPs for determining voice quality in VoIP networks.

•Proactive threshold violation monitoring through SNMP trap notifications.

To measure end-to-end performance for RTP:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of discovery requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Customize an RTP operation.

For details on defining a RTP operation, see Defining an RTP Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the RTP statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining an RTP Operation

IPM provides a default RTP operation to set up and schedule a test call and use Voice source router digital signal processors (DSPs) to gather network performance-related statistics for the call.

In addition, IPM provides the option to create, modify, or delete your own RTP operations from the List of Operations page.

To define a RTP operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select RTP operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Settings section:

•Source Voice Port—Specify the source voice port. The source voice port is represented as slot/[subunit]/port:ds0-group-number, where:

–slot refers to source slot number.

–/subunit refers to source submit. A slash must precede this value.

–/port refers to source port number. A slash must precede this value.

–:ds0-group-number refers to DS0 group number. A colon must precede this value.

•Codec Type—Enables the generation of estimated voice quality scores in the form of Calculated Planning Impairment Factor (ICPIF) and Mean Opinion Score (MOS) values. The codec type should match the encoding algorithm you are using for VoIP transmissions.

–Codec type g711alaw—The G.711 A-Law codec (64 kbps transmission).

–Codec type g711ulaw—The G.711 muHmm-Law codec (64 kbps transmission).

–Codec type g729a—The G.729A codec (8 kbps transmission).

The default codec type is g729a codec.

•Call Duration—Specifies the duration of the test call. The valid values range from 20 to 180 seconds. The default value is 20 seconds.

Collectors move to Config Failed state if the values you specify do not fall between 20 and 180.

•Advantage Factor—Specifies the expectation factor to be used for ICPIF calculations. This value is subtracted from the measured impairments to yield the final ICPIF value (and corresponding MOS value). The valid values range from 0 to 20. The default value is 0.

Step 6 Click Next.

The Summary page appears with the details of the operation created.

Step 7 Click Finish.

The newly defined RTP operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for Call Setup Post Dial Delay

The Cisco IOS IP Service Level Agreements (SLAs) VoIP Call Setup (Post-Dial Delay) Monitoring feature provides the ability to measure your network's response time for setting up a Voice over IP (VoIP) call.

Using H.23 or Session Initiation Protocol (SIP), the IP SLAs or VOIP Call setup operation measures the total time taken to send and receive a call message. This measurement provides information if the dialed number rang or the called party answered the call.

In order to use the IP SLAs VoIP call setup functionality, your Cisco IOS software image must support the IP SLAs VoIP test-call application and IP SLAs VoIP Responder application.

To determine if your Cisco IOS software image is configured with these applications, use the show call application voice command in EXEC mode.

For this operation, you need not define a target device for the collector.

To measure end-to-end performance for Call Setup Post Dial Delay:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Customize a Call Setup Post Dial Delay operation.

For details on defining a Call Setup Post Dial Delay operation, see Defining a Call Setup Post Dial Delay Operation.

Step 3 Define a collector to measure the network performance.

For details on defining a collector, see Defining Collectors.

Step 4 Generate the report to view the Call Setup Post Dial Delay statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a Call Setup Post Dial Delay Operation

Call Setup Post Dial Delay operations measure your network's response time for setting up a Voice over IP (VoIP) call. In addition, IPM provides the option to create, modify, or delete your own Call Setup Post Dial Delay operations from the List of Operations page.

If a gatekeeper (GK) or directory gatekeeper (DGK) is involved in the H.323 call signaling, additional messages are sent and received between the originating and terminating gateways before the call message (containing a call number) is actually sent.

The additional time required for these messages is included in the IP SLAs VoIP call setup response time measurement.

Likewise, if a proxy server or redirection server is involved in the SIP call signaling, any additional time required for messages to be sent and received (before sending the call message) is included in the VoIP call setup response time measurement.

A traditional (plain old) telephone service (POTS) IP phone can be set up at the terminating gateway to respond to an IP SLAs VoIP call setup test call. As a convenient alternative to an actual IP phone, you can enable the IP SLAs VoIP Responder application in the terminating gateway.

The IP SLAs VoIP Responder application will respond to incoming call setup messages from the originating gateway using H.323 or SIP.

The IP SLAs VoIP Responder application is different from the IP SLAs Responder (which is configured using the IP SLA monitor Responder command in global configuration mode).

To define a Call Setup Post Dial Delay operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select CallSetupPostDialDelay operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Settings section:

•Phone Number—Specifies either the full E.164 telephone number or the dial peer number.

•Detect Point—Sets the Voice over IP call setup operation to measure the response time for the called number to ring. The default value is 6.

Step 6 Click Next.

The Summary page displays the details of the operation that you have created.

Step 7 Click Finish.

The newly defined Call Setup Post Dial Delay operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for Gatekeeper Registration Delay

The VoIP (Voice over IP) Gatekeeper Registration Delay operation determines the average, median, or aggregated response time (delay) of registration attempts from a VoIP source router to a VoIP gatekeeper device.

To measure VoIP gatekeeper registration response time, the gatekeeper registration delay operation sends a lightweight Registration Request (RRQ) from an source router to an gatekeeper and records the amount of time taken to receive the Registration Confirmation (RCF) back from the gatekeeper.

For this operation, you need not define a target device for the collector.

To measure end-to-end performance for Gatekeeper Registration Delay:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a Gatekeeper Registration Delay operation. Use the default Gatekeeper Registration Delay operation or customize a Gatekeeper Registration Delay operation.

For details on defining an Gatekeeper Registration Delay operation, see Defining a Gatekeeper Registration Delay 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 Collectors.

Step 4 Generate the report to view Gatekeeper Registration Delay statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a Gatekeeper Registration Delay Operation

IPM supports one default VoIP Gatekeeper Registration Delay operation for measuring performance of registration attempts from a VoIP source router to a VoIP gatekeeper.

In addition, IPM provides the option to create, modify, or delete your own VoIP Gatekeeper Registration Delay operation from the List of Operations page.

To define a Gatekeeper Registration Delay operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select GatekeeperRegistrationDelay operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Note Ensure that you specify gatekeeper registration response time in the Rising Threshold field.

Step 4 Click Next.

The Summary page displays the details of the operation that you have created.

Step 5 Click Finish.

The newly defined VoIP Gatekeeper Registration Delay operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for DNS

DNS operation latency is computed by measuring the time between sending a DNS request and receiving a reply. The operation queries for an IP address if you specify a host name or queries for a host name if you specify an IP address.

The DNS operation also measures availability and errors for DNS services.

To measure end-to-end performance for DNS:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a Lookup String (host name or IP address) as a target device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Define a DNS operation. Use the DefaultDNS operation or customize a DNS operation.

The DNS server is specified as part of the operation.

For details on defining a DNS operation, see Defining a DNS Operation.

Step 4 Define a collector to measure performance between the source router and DNS servers.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the DNS statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a DNS Operation

IPM provides a default DNS operation for measuring performance between a source and a DNS server. In addition, IPM provides the option to create, modify, or delete your own DNS operations from the List of Operations page.

Note The default DNS operation is available only on Solaris platform and not on Windows.

To define a DNS operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select DNS operation from the Type drop-down list.

To complete other general setting parameters for the selected operation, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Enter the host name or IP address for DNS server name in the DNS Server Details section.

IPM automatically creates the DefaultDNS operation at startup based on the DNS server configuration of the IPM server.

Step 6 Click Next.

The Summary page appears with the details of the operation created.

Step 7 Click Finish.

The newly defined DNS operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for DHCP

The DHCP operation measures the round-trip latency time taken to discover a DHCP server and obtain a lease from it. After obtaining an IP address, IP SLA releases the IP address that was leased by the server.

The DHCP operates on two modes:

•By default, the DHCP operation sends discovery packets on every available IP interface on the source router.

•If a specific DHCP server is configured on the router, then discovery packets are sent to only that DHCP server.

The DHCP operation also measures availability and errors for DHCP services.

To measure end-to-end performance for DHCP:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a DHCP server as a target device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Define a DHCP operation. Use the DefaultDHCP operation or customize a DHCP operation.

For details on defining a DHCP operation, see Defining a DHCP Operation.

Step 4 Define a collector to measure performance between the source router and DHCP servers.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the DHCP statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a DHCP Operation

IPM provides a default DHCP operation for measuring performance in leasing an IP address from a DHCP server. In addition, IPM provides the option to create, edit, or delete your own DHCP operations from the List of Operations page.

To define a DHCP operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select DHCP operation from the Type drop-down list.

To complete other general setting parameters for the selected operation, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Summary page appears with the details of the operation created.

Step 5 Click Finish.

The newly defined DHCP operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for HTTP

The HTTP operation measures the round-trip latency time required to connect to and access data from an HTTP server. Three HTTP server response time measurements are made:

•DNS Lookup—Round-trip latency in looking up the domain name.

•TCP Connect—Round-trip latency in performing a TCP connect to the HTTP server.

•HTTP transaction time—Round-trip latency in sending a request to, and receiving a reply from, the HTTP server (the probe retrieves the base HTML page only).

The HTTP operation also measures availability and errors for HTTP services.

To measure end-to-end performance for HTTP:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define an HTTP server as a target device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Customize an HTTP operation.

For details on defining an HTTP operation, see Defining an HTTP Operation.

Step 4 Define a collector to measure performance between the source device and the HTTP servers.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the HTTP statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining an HTTP Operation

The List of Operations page allows you to create, modify, or delete your own HTTP operations for measuring performance in connecting and accessing data from an HTTP server. IPM does not provide a default HTTP operation.

To define an HTTP operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select HTTP operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type— Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The value you select defines the packet priority and is based on the DSCP RFC standards.

Step 6 Specify the following in the Lookup Settings section:

•URL Relative Path—Enter the URL to use for the HTTP request. IPM validates the format of the HTTP string that you enter in the URL Lookup String field.

–The URL that you enter must be in the [/path/filename or filename] format.

If you specify the path in the URL Relative Path field, the next two characters that follow a `%' should be hexadecimal values. The maximum length of characters that you can specify in the URL Relative Path field is 127.

IPM displays appropriate error messages if any of the variables you enter in the URL string is incorrect.

•Port—Port number should be greater than 0 and less than 65536. The default value is 80.

•Download URL From Cache—Select the check box if you want the source to search its cache for the Website and, if it is found, download it instead of querying the Website.

Deselect the check box if you want the router to query the Website for the HTTP request. By default, the check box is not selected.

Step 7 Specify the following in the Proxy Server Settings section:

•Use HTTP Proxy Server—Select the check box to configure IPM to use a proxy server.

•Proxy Server—Enter the name or address of the proxy server to configure IPM to use a proxy server.

IPM will use the proxy server you specify for collectors you have configured for the HTTP operation.

The default port for the HTTP proxy server would be 80, and the type of proxy server would be HTTP. You can set proxy server settings for IOS versions 12.1(9a) and above. To specify a different proxy port, enter the server name as: http proxy server: port number.

Step 8 Click Next.

The Summary page appears with the details of the operation created.

Step 9 Click Finish.

The newly defined HTTP operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for FTP

FTP is an application protocol, part of the Transmission Control Protocol (TCP)/IP protocol stack, used for transferring files between network nodes. The FTP operation measures the round-trip latency time required to connect to and access data from an FTP server.

The FTP transaction time server response shows the round-trip latency in sending a request to, and downloading the file from the FTP server.

The FTP operation also measures availability and errors for FTP services.

To measure end-to-end performance for FTP:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a FTP server as a target device.

For details on defining a target device, see Specifying Target Devices.

Step 3 Customize an FTP operation.

For details on customizing an FTP operation, see Defining an FTP Operation.

Step 4 Define a collector to measure performance between the source device and the FTP servers.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the FTP statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining an FTP Operation

Use the List of Operations page to create, modify, or delete your own FTP operations for measuring performance while connecting and accessing data from an FTP server. IPM does not provide a default FTP operation.

To define an FTP operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select FTP operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type—Select IP QoS as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

Step 6 Specify the following in the Lookup Settings section:

•Enter the user name and password in the User Name and Password fields to access the FTP server. Use the default values to access an anonymous FTP server.

IPM checks the syntax and also checks whether:

–The username contains only alphanumerical characters, safe characters ('$','-','_','.','+'), and extra characters ('!','*',',',0x27,0x28,0x29).

–The password contains only alphanumerical characters, safe characters, extra characters, and `%'.

•Enter the file location in the File Location field. Use the following guidelines to enter a file location:

–To select a relative path use /, this will look for the file in the User's Home Directory

Example

/Documents and Settings/<username>/myfile.sh

Where myfile.sh is the name of the file and /Documents and Settings/<username> is the User's Home Directory.

Specifying single slash will assume that the relative path is considered.

–To select an absolute path use //, this will look for the file in the absolute path not relative to the User's Home directory.

Example

//opt/CSCOpx/bin/myfile.sh

Where myfile.sh is the name of the file

–IPM checks the syntax and also checks whether:

The path, dir/file, contains only alphanumerical characters, safe characters, extra characters, reserved characters ('?','@','&','='.'/'), ` ', and `%'

•Select the mode of FTP session from the drop-down list.

–In Active FTP, the client opens a control connection on port 21 to the server, and whenever the client requests data from the server, the server opens a TCP session on port 20.

–In Passive FTP, the client opens the data sessions, using a port number supplied by the server. This is the default FTP mode.

Step 7 Click Next.

The Summary page appears with the details of the operation created.

Step 8 Click Finish.

The newly defined FTP operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for DLSw

DLSw+ is the enhanced Cisco version of DSCP RFC 1795. DLSw+ tunnels SNA traffic over IP backbones using TCP. The routers performing the tunneling of SNA traffic onto TCP/IP are referred to as DLSw peers.

The DLSw operation measures the DLSw+ protocol stack and round-trip latency between DLSw peers. Normally DLSw peers communicate through TCP port 2065.

To successfully run the DLSw operation you must have a connected DLSw+ peer between the source and destination Cisco devices. On the source DLSw+ device, an operation can be defined for a DLSw+ partner peer. The DLSw operation also measures availability and errors for DLSw services.

To measure the round-trip latency between two DLSw peers, the IP address that you define as the source router must be one of the DLSw peers. Also, the IP address that you define as the target router must be configured as the DLSw peer to the source router.

To measure end-to-end performance for DLSW:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of discovery requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Define a DLSw operation. Use the DefaultDLSw operation or customize a DLSw operation.

For details on defining an DLSW operation, see Defining a DLSw Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the DLSW statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a DLSw Operation

IPM provides a default DLSw operation for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own DLSw operations from the List of Operations page.

To define a DLSw operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select DLSW operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Enter the number of bytes to use for the size of the payload of the request packet in the Request Payload. The values can be less than or equal to 16384. The default value is 64 bytes.

Step 6 Click Next.

The Summary page displays the operation details that you have created.

Step 7 Click Finish.

The newly defined DLSw operation is successfully created.

An error message appears if the Create operation fails.

Measuring Network Performance for TCP Connect

The TCP Connect operation in IPM 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 Connect:

Step 1 Define a device as the source device from which to measure performance.

For details on defining a source device, see Specifying Source Devices.

Step 2 Define a device as the target of connection requests from the source device.

For details on defining a target, see Specifying Target Devices.

Step 3 Define a TCP operation. Use one of the default operations for TCP or customize a TCP operation.

For details on defining a TCP operation, see Defining a TCP Connect Operation.

Step 4 Define a collector to measure performance between the source router and target you defined.

For details on defining a collector, see Defining Collectors.

Step 5 Generate the report to view the TCP Connect statistics.

For more information on generating the report, see Generating Statistical Reports and Graphs.

Defining a TCP Connect 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 List of Operations page.

To define a TCP Connect operation:

Step 1 Go to LMS Portal and select Internetwork Performance Monitor > Collector Management > Operations.

The List of Operations page appears.

Step 2 Click Create.

The General Settings page appears.

Step 3 Select TCPConnect operation from the Type drop-down list.

To complete other general setting parameters, see General Settings for a User-Defined Operation.

Step 4 Click Next.

The Specific Settings page appears.

Step 5 Specify the following in the Packet Settings section:

•IP QoS Type—Select the IP QoS Type as IP Precedence or DSCP.

•IP QoS Settings—Select a value from the drop-down list. The values change based on your IP QoS Type selection.

–If you have selected IP QoS Type as IP Precedence, select the IP QoS Settings value from the drop-down list. The values range from 0 to 7.

The value you select sets the priority for the request packet. The default setting is 0 (no priority). This option sets the ToS bits in the IP packet.

–If you have selected IP QoS Type as DSCP, select the desired IP QoS Settings value from the drop-down list. The values range from 0 to 63.

The value you select defines the packet priority and is based on the DSCP RFC standards.

Step 6 Specify the following in the Other Settings section:

•Target Port—Enter the TCP port number. The target device uses the specified port number when sending a response to a connection request. Valid values range from 1 to 65535. The default setting is 3000.

You can specify any port number, known or unknown, on any IP host, Cisco or non-Cisco, as long as someone is listening on that target port.

–If the port number specified is less than 1024, then your target device can be a Cisco Responder or any IP reachable device.

–If the port number specified is greater than 1024, then your target device must be a Cisco IP SLA Responder enabled device.

•Control Enable—Select True or False from the drop-down list. The value you select depends on the value specified for the target port.

–If you have specified a known port (such as less than 1024), then you have to select False from the drop-down list.

–If you have specified a unknown port (such as greater than 1024), then you have to select True from the drop-down list.

Step 7 Click Next.

The Summary page appears with the details of the operation created.

Step 8 Click Finish.

The newly defined TCP Connect operation is successfully created.

An error message appears if the Create operation fails.