Catalyst 4500 Series Switch Software Configuration Guide, 12.2(50)SG

Configuring Cisco IOS IP SLAs Operations

This chapter describes how to use Cisco IOS IP Service Level Agreements (SLAs) on the switch. Cisco IP SLAs is a part of Cisco IOS software that allows Cisco customers to analyze IP service levels for IP applications and services by using active traffic monitoring—the generation of traffic in a continuous, reliable, and predictable manner—for measuring network performance. With Cisco IOS IP SLAs, service provider customers can measure and provide service level agreements, and enterprise customers can verify service levels, verify outsourced service level agreements, and understand network performance. Cisco IOS IP SLAs can perform network assessments, verify quality of service (QoS), ease the deployment of new services, and assist with network troubleshooting.

Note Switches running the IP base image support only IP SLAs responder functionality and must be configured with another device that supports full IP SLAs functionality, for example, a switch.

For more information about IP SLAs, see the Cisco IOS IP SLAs Configuration Guide, Release 12.4T at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

This chapter consists of these sections:

•Command Table

•Understanding Cisco IOS IP SLAs  

•Configuring IP SLAs Operations

•Monitoring IP SLAs Operations

Command Table

This table lists the commands most commonly used with Cisco IP SLAs.

Understanding Cisco IOS IP SLAs

Cisco IOS IP SLAs sends data across the network to measure performance between multiple network locations or across multiple network paths. It simulates network data and IP services and collects network performance information in real time. Cisco IOS IP SLAs generates and analyzes traffic either between Cisco IOS devices or from a Cisco IOS device to a remote IP device such as a network application server. Measurements provided by the various Cisco IOS IP SLAs operations can be used for troubleshooting, for problem analysis, and for designing network topologies.

Depending on the specific Cisco IOS IP SLAs operation, various network performance statistics are monitored within the Cisco device and stored in both command-line interface (CLI) and Simple Network Management Protocol (SNMP) MIBs. IP SLAs packets have configurable IP and application layer options such as source and destination IP address, User Datagram Protocol (UDP)/TCP port numbers, a type of service (ToS) byte (including Differentiated Services Code Point [DSCP] and IP Prefix bits), Virtual Private Network (VPN) routing/forwarding instance (VRF), and URL web address.

Because Cisco IP SLAs is Layer 2 transport independent, you can configure end-to-end operations over disparate networks to best reflect the metrics that an end user is likely to experience. IP SLAs collects a unique subset of these performance metrics:

•Delay (both round-trip and one-way)

•Jitter (directional)

•Packet loss (directional)

•Packet sequencing (packet ordering)

•Path (per hop)

•Connectivity (directional)

•Server or website download time

Because Cisco IOS IP SLAs is SNMP-accessible, it can also be used by performance-monitoring applications like CiscoWorks Internetwork Performance Monitor (IPM) and other third-party Cisco partner performance management products. You can find more details about network management products that use Cisco IOS IP SLAs at this URL: http://www.cisco.com/go/ipsla

Using IP SLAs can provide these benefits:

•Service-level agreement monitoring, measurement, and verification.

•Network performance monitoring

–Measures the jitter, latency, or packet loss in the network.

–Provides continuous, reliable, and predictable measurements.

•IP service network health assessment to verify that the existing QoS is sufficient for new IP services.

•Edge-to-edge network availability monitoring for proactive verification and connectivity testing of network resources (for example, shows the network availability of an NFS server used to store business critical data from a remote site).

•Troubleshooting of network operation by providing consistent, reliable measurement that immediately identifies problems and saves troubleshooting time.

This section includes this information about IP SLAs functionality:

•Using Cisco IOS IP SLAs to Measure Network Performance

•IP SLAs Responder and IP SLAs Control Protocol

•Response Time Computation for IP SLAs

•IP SLAs Operation Scheduling

•IP SLAs Operation Threshold Monitoring

Using Cisco IOS IP SLAs to Measure Network Performance

You can use IP SLAs to monitor the performance between any area in the network—core, distribution, and edge—without deploying a physical probe. It uses generated traffic to measure network performance between two networking devices. Figure 55-1 shows how IP SLAs begins when the source device sends a generated packet to the destination device. After the destination device receives the packet, depending on the type of IP SLAs operation, it responds with time-stamp information for the source to make the calculation on performance metrics. An IP SLAs operation performs a network measurement from the source device to a destination in the network using a specific protocol such as UDP.

Figure 55-1 Cisco IOS IP SLAs Operation

To implement IP SLAs network performance measurement, you need to perform these tasks:

1. Enable the IP SLAs responder, if required.

2. Configure the required IP SLAs operation type.

3. Configure any options available for the specified operation type.

4. Configure threshold conditions, if required.

5. Schedule the operation to run, then let the operation run for a period of time to gather statistics.

6. Display and interpret the results of the operation using the Cisco IOS CLI or a network management system (NMS) system with SNMP.

For more information about IP SLAs operations, see the operation-specific chapters in the Cisco IOS IP SLAs Configuration Guide, Release 12.4T at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

Note The switch does not support Voice over IP (VoIP) service levels using the gatekeeper registration delay operations measurements. Before configuring any IP SLAs application, you can use the show ip sla application privileged EXEC command to verify that the operation type is supported on your software image.

IP SLAs Responder and IP SLAs Control Protocol

The IP SLAs responder is a component embedded in the destination Cisco device that allows the system to anticipate and respond to IP SLAs request packets. The responder provides accurate measurements without the need for dedicated probes. The responder uses the Cisco IOS IP SLAs Control Protocol to provide a mechanism through which it can be notified on which port it should listen and respond. Only a Cisco IOS device can be a source for a destination IP SLAs Responder.

Note The IP SLAs responder can be a Cisco IOS Layer 2, responder-configurable switch, such as a Catalyst 4500 running the IP base image. The responder does not need to support full IP SLAs functionality.

Figure 55-1 shows where the Cisco IOS IP SLAs responder fits in the IP network. The responder listens on a specific port for control protocol messages sent by an IP SLAs operation. Upon receipt of the control message, it enables the specified UDP or TCP port for the specified duration. During this time, the responder accepts the requests and responds to them. It disables the port after it responds to the IP SLAs packet, or when the specified time expires. MD5 authentication for control messages is available for added security.

You do not need to enable the responder on the destination device for all IP SLAs operations. For example, a responder is not required for services that are already provided by the destination router (such as Telnet or HTTP). You cannot configure the IP SLAs responder on non-Cisco devices and Cisco IOS IP SLAs can send operational packets only to services native to those devices.

Response Time Computation for IP SLAs

Switches and routers can take tens of milliseconds to process incoming packets due to other high priority processes. This delay affects the response times because the test-packet reply might be in a queue while waiting to be processed. In this situation, the response times would not accurately represent true network delays. IP SLAs minimizes these processing delays on the source device as well as on the target device (if the responder is being used) to determine true round-trip times. IP SLAs test packets use time stamping to minimize the processing delays.

When the IP SLAs responder is enabled, it allows the target device to take time stamps when the packet arrives on the interface at interrupt level and again just as it is leaving, eliminating the processing time. This time stamping is made with a granularity of sub-milliseconds (ms).

Figure 55-2 demonstrates how the responder works. Four time stamps are taken to make the calculation for round-trip time. At the target router, with the responder functionality enabled, time stamp 2 (TS2) is subtracted from time stamp 3 (TS3) to produce the time spent processing the test packet as represented by delta. This delta value is then subtracted from the overall round-trip time. Notice that the same principle is applied by IP SLAs on the source router where the incoming time stamp 4 (TS4) is also taken at the interrupt level to allow for greater accuracy.

Figure 55-2 Cisco IOS IP SLAs Responder Time Stamping

An additional benefit of the two time stamps at the target device is the ability to track one-way delay, jitter, and directional packet loss. Because much network behavior is asynchronous, it is critical to have these statistics. However, to capture one-way delay measurements, you must configure both the source router and target router with Network Time Protocol (NTP) so that the source and target are synchronized to the same clock source. One-way jitter measurements do not require clock synchronization.

IP SLAs Operation Scheduling

For more details about the IP SLAs multioperations scheduling functionality, see the "IP SLAs—Multiple Operation Scheduling" chapter of the Cisco IOS IP SLAs Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

When you configure an IP SLAs operation, you must schedule the operation to begin capturing statistics and collecting error information. You can schedule an operation to start immediately or to start at a certain month, day, and hour. You can use the pending option to set the operation to start at a later time. The pending option is an internal state of the operation that is visible through SNMP. The pending state is also used when an operation is a reaction (threshold) operation waiting to be triggered. You can schedule a single IP SLAs operation or a group of operations at one time.

You can schedule several IP SLAs operations by using a single command through the Cisco IOS CLI or the CISCO RTTMON-MIB. Scheduling the operations to run at evenly distributed times allows you to control the amount of IP SLAs monitoring traffic. This distribution of IP SLAs operations helps minimize the CPU utilization and thus improves network scalability.

IP SLAs Operation Threshold Monitoring

For details on using thresholds with Cisco IOS IP SLAs operations, see the "IP SLAs—Proactive Threshold Monitoring" chapter of the Cisco IOS IP SLAs Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

To support successful service level agreement monitoring, you must have mechanisms that notify you immediately of any possible violation. IP SLAs can send SNMP traps that are triggered by events such as these:

•Connection loss

•Timeout

•Round-trip time threshold

•Average jitter threshold

•One-way packet loss

•One-way jitter

•One-way mean opinion score (MOS)

•One-way latency

An IP SLAs threshold violation can also trigger another IP SLAs operation for further analysis. For example, the frequency could be increased or an ICMP path echo or ICMP path jitter operation could be initiated for troubleshooting.

Determining the type of threshold and the level to set can be complex, and depends on the type of IP service being used in the network. For more details on using thresholds with Cisco IOS IP SLAs operations, see the "IP SLAs—Proactive Threshold Monitoring" chapter of the Cisco IOS IP SLAs Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

Configuring IP SLAs Operations

Note This section does not include configuration information for all available operations as the configuration information details are included in the Cisco IOS IP SLAs Configuration Guide. It does include several operations as examples, including configuring the responder, configuring UDP jitter operation, which requires a responder, and configuring ICMP echo operation, which does not require a responder. A switch running the IP base image supports only IP SLAs responder functionality. The switch must be running the IP services image for full IP SLAs functionality.

For details about configuring other operations, see he Cisco IOS IP SLAs Configuration Guide at this URL
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

This section includes this information:

•Default Configuration

•Configuration Guidelines

•Configuring the IP SLAs Responder

•Analyzing IP Service Levels by Using the UDP Jitter Operation

•Analyzing IP Service Levels by Using the ICMP Echo Operation

Default Configuration

No IP SLAs operations are configured.

Configuration Guidelines

For detailed descriptions and configuration procedures, see the Cisco IOS IP SLAs Configuration Guide, Release 12.4T at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html

Note that not all of the IP SLAs commands or operations described in this guide are supported on the switch. The switch supports IP service level analysis by using UDP jitter, UDP echo, HTTP, TCP connect, ICMP echo, ICMP path echo, ICMP path jitter, FTP, DNS, and DHCP, as well as multiple operation scheduling and proactive threshold monitoring. It does not support VoIP service levels using the gatekeeper registration delay operations measurements.

Before configuring any IP SLAs application, you can use the show ip sla application privileged EXEC command to verify that the operation type is supported on your software image. This is an example of the output from the command:

Switch# show ip sla application

        IP SLAs

Version: 2.2.0 Round Trip Time MIB, Infrastructure Engine-II

Time of last change in whole IP SLAs: 22:17:39.117 UTC Fri Jun

Estimated system max number of entries: 15801

Estimated number of configurable operations: 15801

Number of Entries configured  : 0

Number of active Entries      : 0

Number of pending Entries     : 0

Number of inactive Entries    : 0

        Supported Operation Types

Type of Operation to Perform: 802.1agEcho

Type of Operation to Perform: 802.1agJitter

Type of Operation to Perform: dhcp

Type of Operation to Perform: dns

Type of Operation to Perform: echo

Type of Operation to Perform: ftp

Type of Operation to Perform: http

Type of Operation to Perform: jitter

Type of Operation to Perform: pathEcho

Type of Operation to Perform: pathJitter

Type of Operation to Perform: tcpConnect

Type of Operation to Perform: udpEcho

IP SLAs low memory water mark: 21741224

Configuring the IP SLAs Responder

The IP SLAs responder is available only on Cisco IOS software-based devices, including some Layer 2 switches that do not support full IP SLAs functionality, such as the Cisco ME 2400 switch.

To configure the IP SLAs responder on the target device (the operational target), follow these steps:

To disable the IP SLAs responder, enter the no ip sla responder global configuration command. This example shows how to configure the device as a responder for the UDP jitter IP SLAs operation in the next procedure:

Switch(config)# ip sla responder udp-echo 172.29.139.134 5000

Analyzing IP Service Levels by Using the UDP Jitter Operation

Jitter means interpacket delay variance. When multiple packets are sent consecutively 10 ms apart from source to destination, if the network is behaving correctly, the destination should receive them 10 ms apart. But if there are delays in the network (like queuing, arriving through alternate routes, and so on) the arrival delay between packets might be more than or less than 10 ms with a positive jitter value meaning that the packets arrived more than 10 ms apart. If the packets arrive 12 ms apart, positive jitter is 2 ms; if the packets arrive 8 ms apart, negative jitter is 2 ms. For delay-sensitive networks, positive jitter values are undesirable, and a jitter value of 0 is ideal.

In addition to monitoring jitter, the IP SLAs UDP jitter operation can be used as a multipurpose data gathering operation. The packets IP SLAs generates carry packet sending and receiving sequence information and sending and receiving time stamps from the source and the operational target. Based on these, UDP jitter operations measure this data:

•Per-direction jitter (source to destination and destination to source)

•Per-direction packet-loss

•Per-direction delay (one-way delay)

•Round-trip delay (average round-trip time)

Because the paths for the sending and receiving of data can be different (asymmetric), you can use the per-direction data to more readily identify where congestion or other problems are occurring in the network.

The UDP jitter operation generates synthetic (simulated) UDP traffic and sends a number of UDP packets, each of a specified size, sent a specified number of milliseconds apart, from a source router to a target router, at a given frequency. By default, ten packet-frames, each with a payload size of 10 bytes are generated every 10 ms, and the operation is repeated every 60 seconds. You can configure each of these parameters to best simulate the IP service you want to provide.

Note The IP SLA precision microsecond feature does not provide microsecond accuracy; it provides only microsecond granularity of the timestamps.

To provide accurate one-way delay (latency) measurements, time synchronization, such as that provided by NTP, is required between the source and the target device. Time synchronization is not required for the one-way jitter and packet loss measurements. If the time is not synchronized between the source and target devices, one-way jitter and packet loss data is returned, but values of 0 are returned for the one-way delay measurements provided by the UDP jitter operation.

Note Before you configure a UDP jitter operation on the source device, you must enable the IP SLAs responder on the target device (the operational target).

To configure UDP jitter operation on the source device, follow these steps:

To disable the IP SLAs operation, enter the no ip sla operation-number global configuration command. This example shows how to configure a UDP jitter IP SLAs operation:

Switch(config)# ip sla 10 

Switch(config-ip-sla)# udp-jitter 172.29.139.134 5000 

Switch(config-ip-sla-jitter)# frequency 30 

Switch(config-ip-sla-jitter)# exit 

Switch(config)# ip sla schedule 5 start-time now life forever 

Switch(config)# end

Switch# show ip sla configuration 10

IP SLAs, Infrastructure Engine-II.

Entry number: 10

Owner:

Tag:

Type of operation to perform: udp-jitter

Target address/Source address: 1.1.1.1/0.0.0.0

Target port/Source port: 2/0

Request size (ARR data portion): 32

Operation timeout (milliseconds): 5000

Packet Interval (milliseconds)/Number of packets: 20/10

Type Of Service parameters: 0x0

Verify data: No

Vrf Name:

Control Packets: enabled

Schedule:

    Operation frequency (seconds): 30

    Next Scheduled Start Time: Pending trigger

    Group Scheduled : FALSE

    Randomly Scheduled : FALSE

    Life (seconds): 3600

    Entry Ageout (seconds): never

    Recurring (Starting Everyday): FALSE

    Status of entry (SNMP RowStatus): notInService

Threshold (milliseconds): 5000

Distribution Statistics:

    Number of statistic hours kept: 2

    Number of statistic distribution buckets kept: 1

    Statistic distribution interval (milliseconds): 20

Enhanced History:

Analyzing IP Service Levels by Using the ICMP Echo Operation

The ICMP echo operation measures end-to-end response time between a Cisco device and any devices using IP. Response time is computed by measuring the time taken between sending an ICMP echo request message to the destination and receiving an ICMP echo reply. Many customers use IP SLAs ICMP-based operations, in-house ping testing, or ping-based dedicated probes for response time measurements between the source IP SLAs device and the destination IP device. The IP SLAs ICMP echo operation conforms to the same specifications as ICMP ping testing, and the two methods result in the same response times.

Note This operation does not require the IP SLAs responder to be enabled.

To configure an ICMP echo operation on the source device, follow these steps:

configure terminal

ip sla operation-number 

icmp-echo 
{destination-ip-address | 
destination-hostname} 
[source-ip {ip-address | 
hostname} | source-interface 
interface-id] 

frequency seconds

exit

ip sla schedule 
operation-number [life 
{forever | seconds}] 
[start-time {hh:mm [:ss] 
[month day | day month] | 
pending | now | after 
hh:mm:ss] [ageout seconds] 
[recurring] 

end

show ip sla configuration 
[operation-number] 

copy running-config 
startup-config

To disable the IP SLAs operation, enter the no ip sla operation-number global configuration command. This example shows how to configure an ICMP echo IP SLAs operation:

Switch(config)# ip sla 12 

Switch(config-ip-sla)# icmp-echo 172.29.139.134 

Switch(config-ip-sla-echo)# frequency 30 

Switch(config-ip-sla-echo)# exit 

Switch(config)# ip sla schedule 5 start-time now life forever 

Switch(config)# end

Switch# show ip sla configuration 22

IP SLAs, Infrastructure Engine-II.

Entry number: 12

Owner:

Tag:

Type of operation to perform: echo

Target address: 2.2.2.2

Source address: 0.0.0.0

Request size (ARR data portion): 28

Operation timeout (milliseconds): 5000

Type Of Service parameters: 0x0

Verify data: No

Vrf Name:

Schedule:

    Operation frequency (seconds): 60

    Next Scheduled Start Time: Pending trigger

    Group Scheduled : FALSE

    Randomly Scheduled : FALSE

    Life (seconds): 3600

    Entry Ageout (seconds): never

    Recurring (Starting Everyday): FALSE

    Status of entry (SNMP RowStatus): notInService

Threshold (milliseconds): 5000

Distribution Statistics:

    Number of statistic hours kept: 2

    Number of statistic distribution buckets kept: 1

    Statistic distribution interval (milliseconds): 20

History Statistics:

    Number of history Lives kept: 0

    Number of history Buckets kept: 15

    History Filter Type: None

Enhanced History:

Monitoring IP SLAs Operations

To display IP SLAs operations configuration and results, use the commands listed in Table 55-1.

show ip sla application 

show ip sla authentication 

show ip sla configuration [entry-number] 

show ip sla enhanced-history {collection-statistics | 
distribution statistics} [entry-number] 

show ip sla ethernet-monitor configuration [entry-number] 

show ip sla group schedule [schedule-entry-number]

show ip sla history [entry-number | full | tabular] 

show ip sla mpls-lsp-monitor {collection-statistics | 
configuration | ldp operational-state | scan-queue | 
summary [entry-number] | neighbors}

show ip sla reaction-configuration [entry-number] 

show ip sla reaction-trigger [entry-number] 

show ip sla responder

show ip sla statistics [entry-number | aggregated | 
details]