IPSLA

Introduction to Network Performance Measurement with Cisco IOS IP SLA

BRKNMS-1204

BRKNMS-1204 14528_04_2008_c1

2008 Cisco Systems, Inc. All rights reserved.

Cisco Public

2

2006, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

1

AbstractThis presentation introduces you to the principles of network performance measurements with the Cisco IOS IP SLA feature, formerly known as SAA. This session is specially designed for attendees with little or no experience on this topic. We will first explain the concept and background of IP SLA and discover various operations, such as Jitter, DNS, DHCP, and HTTP. Real-life examples of configuration will be provided for a better understanding. This session is a good preparation if you are planning on attending the Advanced Session on Network Performance Measurement. It is designed for network planners and administrators of both Enterprises and Service Providers that deal with network performance management regularly. Attendees should be familiar with IP and SNMP fundamentals.BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

3

Objective of This PresentationIntroduce active measurement Provide a clear understanding of Cisco IP SLA functions Understand how IP SLA is working Be able to configure various operations Limitations and scalability issuesDesigning Your Network to Deploy Tight SLA Services or Qos Configuration Cisco Applications, Graphical Interfaces, and Other Third Party Applications That Leverage IP SLA For Advanced IP SLA Concepts See NMS-3043 Acknowledgement Emmanuel TychonBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

4


2

AgendaSLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios

BRKNMS-1204 14528_04_2008_c1


Cisco Public

5

Service Level Agreements (SLA) and Service DeliverySLAs Are Becoming an Integral Part of Service Delivery

Businesses are relying on them for mission critical applications (voice, video, SAP)

SLA is the cornerstone of carriers differentiated service offerings

Service Provider NetworkEnterprise Network Enterprise Network

BRKNMS-1204 14528_04_2008_c1


Cisco Public

6


3

Whats an SLA?

A Service Level Agreement is the formalization of the Quality of the Service in a contract between the Customer and the Service Provider.

Fred Baker, Fellow of Cisco Systems

If You Cant Measure ItDont Negotiate It...BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

7

SLA ComponentsMetrics:Particular type of test, between a single source/target pair General: Availability Mean Time To Restore (MTTR) Per class of service: Packet loss Network delay Network delay variation (jitter)

Processes Remedies/reparationsBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

8


4

SLA CriteriaEasy to understand Simple and light to measure Attainable Meaningful Controllable Application/service driven

BRKNMS-1204 14528_04_2008_c1


Cisco Public

9

Multimedia QoS Requirements (Examples)

Traffic Type VoIP Video-Conferencing Streaming Video

Maximum Packet Loss 1% 1% 2%

Maximum One-Way Latency 200 ms 200 ms 5s

Max. Jitter 30 ms 30 ms N/A

BRKNMS-1204 14528_04_2008_c1


Cisco Public

10


5

The SLA LifecycleBaseline Network Performance Verify Network Readiness for (New) Services, QoS, etc. Understand and Apply Network Performance Baseline I) Adjust Network to get Confidence to Deploy New Services and Applications II) Deployment

2

Quantify Results

1

Reduced deployment time? Prove service and application differentiation Verify SLA Reduced network downtime?

Assure Application and Service Deployment

3

Fine-Tune and Optimize I) Ongoing Measurements to Understand Behavior. II) Define Proactive Notifications11

4

BRKNMS-1204 14528_04_2008_c1


Cisco Public


BRKNMS-1204 14528_04_2008_c1


Cisco Public

12


6

Murphys LawIf anything can go wrong, it will If anything just cannot go wrong, it will anyway Left to themselves, things tend to go from bad to worse If everything seems to be going well, you have obviously overlooked something

BRKNMS-1204 14528_04_2008_c1


Cisco Public

13

SLA Parameter: Latency (Delay)Propagation delay: the time it takes to the physical signal to traverse the path Serialization delay is the time it takes to actually transmit the packet; depends on the bit-rate Queuing delay is the time a packet spends in router queues; depends on queue length and type A maximum end-to-end one-way delay of 120 milliseconds is recommended for comfortable human-to-human audio

BRKNMS-1204 14528_04_2008_c1


Cisco Public

14


7

SLA Parameter: JitterJitter is delay variation It is caused by queue depth variation Jitter is bad for interactive voice like VoIP, generating pops and clicks

tBRKNMS-1204 14528_04_2008_c1


Cisco Public

15

SLA Parameter: Packet LossLoss of an isolated packet Possible causes:Because of a single CRC error Because of short duration full queue (tail-drop)

Little or no impact for VoIP calls, based on UDP With TCP, forces retransmit possibly at a lower speed reducing the effective bandwidth

BRKNMS-1204 14528_04_2008_c1


Cisco Public

16


8

SLA Parameter: Burst LossMultiple consecutive packets are lost Possible causes:A noise on the transmission media that kills all the packets A sudden route change in a transit device creates a temporary black hole Full transit interface queue

BRKNMS-1204 14528_04_2008_c1


Cisco Public

17

SLA Parameter: Packet ReorderingThis is not a rare situation According to a study, roughly 25% of the hosts monitored exhibit reordering, where on average eight of the 50 packets were identified as being out of order Packet reordering within a TCP session causes unnecessary retransmissions and prevents the congestion window from growing properly Potential impact on the UDP application performance (e.g. DNS vs. Voice-Codec)(Results Are Based on Packet Reordering Is Not Pathological Network Behavior, Jon C. R. Bennett, Craig Partridge, and Nicholas Shectman. IEEE/ACM Transactions on Networking , Vol. 7, No. 6, December 1999, p789 and Reordering of IP Packets in Internet, Xiaoming Zhou and Piet Van Mieghem, PAM2004 Contribution)BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

18


9

Packet Reordering CausesLoad balancing through multiple paths having different latencies Inadequate QoS/queuing policy Typically happening on some parallel architectures

BRKNMS-1204 14528_04_2008_c1


Cisco Public

19


BRKNMS-1204 14528_04_2008_c1


Cisco Public

20


10

Current Solutions to Measure SLAWait for problem to happen, and customer to complainReactive approach

ManuallyTime consuming approach

Custom, home-made applicationThe geeky approach

Special hardware probesThe expensive approach

BRKNMS-1204 14528_04_2008_c1


Cisco Public

21

The Concept of Cisco IP SLAIf you have a running Cisco IOS router, turn it into an active probing device:Synthetic Probe Core technology in IOS Available on most Cisco platforms from 12.0(5)T or later

Reuse your current equipment and enhance existing network management applications

IP SLA

BRKNMS-1204 14528_04_2008_c1


Cisco Public

22


11

IP SLA HistoryUsed to be called RTR, renamed SAA in 12.0(5)T; we call it Engine 1. New Engine 2 is a major code rewrite introduced initially in 12.2(11)T, and now present in all 12.3 and later trains. Engine 2 is faster and consumes less memory. New CLI (Phase I) and enhanced accuracy for 12.3(14)T release: IP SLA, but using Engine 2.timeEngine:

Engine 1 RTR rtr SAA

Engine 2 IP SLA ip sla mon ip sla

Feature Name:

CLI:

BRKNMS-1204 14528_04_2008_c1


Cisco Public

23

Cisco IOS IP SLA PartnersCisco Network Management SolutionIP Communications Service Monitor Internetworking Performance Monitor Telephony Monitoring Enterprise performance measurements

Third Party Products

New Partners 2006

BRKNMS-1204 14528_04_2008_c1


Cisco Public

24


12

IP SLA and the Measurement FrameworkSampling Method

Observed/PassiveCollection Method

Synthetic/Active

Embedded Agents

External Probes

Scope of Measurement

Device/LinkPerspective of Measurement

End-to-End/Path

User

Network

BRKNMS-1204 14528_04_2008_c1


Cisco Public

25

IP SLA: Sampling MethodObservedDefinitionActual end-user network traffic where performance is measured by timing specific application traffic flows

SyntheticDefinitionNetwork traffic generated strictly for the purpose of measuring a network performance characteristic

AdvantagesMost accurate for live application traffic on a specified link

AdvantagesMeasures performance: Between any two points in the network Controllable, on a continuous basis By traffic class based on IP Precedence marking

DisadvantagesLimited to measuring: Existing traffic types, which may not be present on the network at all times Existing traffic patterns, which may not reflect patterns for new or future applications

DisadvantagesOnly an approximation for performance of live traffic Inject some traffic in the network

BRKNMS-1204 14528_04_2008_c1


Cisco Public

26


13

IP SLA: Collection MethodEmbeddedDefinitionMechanisms for collection of network statistics are integrated into the network communication device (e.g., router or switch), itself

ExternalDefinitionMechanisms for collection of network statistics are provided by a stand-alone device specifically designed to collect network performance statistics

AdvantagesFollows network infrastructure Gathers metrics that cannot be observed externally End-to-end monitoring

AdvantagesValidation of performance performed independent of the devices that transmit network traffic

DisadvantagesMore hardware to administer Observed statistics limited to points of deployment Scale and distribution issues

DisadvantagesPerformance monitoring has devicelevel performance implications

BRKNMS-1204 14528_04_2008_c1


Cisco Public

27

IP SLA: Scope of MeasurementDevice or Link OrientedDefinitionPerformance measurement based on analysis of specific device or device interface, and typically based on utilization rates

End to EndDefinitionPerformance measurement based on analysis of response time across two or more network devices, and typically based on latency

AdvantagesDetailed application performance monitoring of critical network links

AdvantagesStarting point performance troubleshooting Reflects end-user experience

DisadvantagesWhen network-wide performance problems exist, how does one select which device or link to evaluate?

DisadvantagesPrior knowledge of relevant end-to-end paths is needed

BRKNMS-1204 14528_04_2008_c1


Cisco Public

28


14

IP SLA: Perspective of MeasurementUserDefinitionMeasurement based on performance statistics measured at the end-user workstation

NetworkDefinitionMeasurement based on performance statistics measured in network devices

AdvantagesAccurate measurement of end-user experience

AdvantagesEasy to deploy, and non-intrusive to the desktop Identifies network performance issue

DisadvantagesScale and distribution issues Intrusive on the desktop

DisadvantagesImperfect understanding of end-user experience

BRKNMS-1204 14528_04_2008_c1


Cisco Public

29

Benefits of Using IP SLAFlat learning curve (Cisco IOS technology) No additional equipment, nor vendor Can be deployed on customer site (CPE) and measure end-to-end SLAs Activate at the production router (CPE, CE, PE) or as a dedicated shadow-router Can be managed with existing router management tools (e.g. CiscoWorks)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

30


15

IP SLA Technical OverviewWide measurement capabilities (UDP, TCP, ICMP) Near millisecond precision Accessible using CLI and SNMP Proactive notification Historical data storage Flexible scheduling options Already in Cisco IOS (available on most platforms) Almost all interfaces supported, physical, and logical

BRKNMS-1204 14528_04_2008_c1


Cisco Public

31

Proactive NotificationCan send SNMP traps when certain triggering events occur (e.g., when rising and falling thresholds are passed) Can trigger another IP SLA operation for further analysis (e.g., when ping fails, a path echo operation starts)

IP SLA

WANSN p tra MP

NMSBRKNMS-1204 14528_04_2008_c1

www.cisco.com32


Cisco Public


16

Historical Data StorageStores previous results Not supported on all operations New enhanced history enables configuration of IP SLA to store aggregated measurements in bucketsE.g., store 48 buckets, and each bucket maintains 15 minutes of the aggregated measurements; with this configuration, it can store 12 hours of performance information

BRKNMS-1204 14528_04_2008_c1


Cisco Public

33

Comprehensive Hardware SupportEnterprise and Aggregation/Edge Core

Cisco IOS Software Release 12.2SCisco CRS-1 (Future) Cisco Catalyst 6500; Cisco 7600 Series Cisco 12000 Series

Cisco 7200 Series

Cisco 7300 Series

Cisco 10000 Series

AccessCisco IOS Software Releases 12.3T and 12.4

Cisco 800 Series (Responder Only)BRKNMS-1204 14528_04_2008_c1

Cisco 1700/ 1800 Series

Cisco 2600/ 2800 Series

Cisco 3700 Series

Cisco 3800 Series

Cisco 7200 and 7300 Series

Cisco 2900, 3550, and 3750 Series


Cisco Public

34


17

Cisco Device DetailsCisco IOS Routers: Available on all platforms from the small 800 up to the 12000 Catalyst Switches: 2900, 3500, 3700, 4000 (SUP4), 6000 (MSFC or MWAM) Included in IP feature set since 11.3 and up to 12.2, and 12.3M (included) Starting release 12.3T and all 12.4, the IP voice or upper feature set will be required The responder will still remain in IP base

BRKNMS-1204 14528_04_2008_c1


Cisco Public

35

Features and Supported Cisco IOS VersionFeature/ReleaseICMP Echo ICMP Echo Path UDP Echo TCP Connect UDP Jitter HTTP DNS DHCP DLSw+ SNMP Support UDP Jitter With One Way Latency FTP Get MPLS/VPN Aware Frame-Relay (CLI) ICMP Path Jitter APM Voice with MOS/ICPIF Score Post Dial Delay H323/SIPBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

11.2

12.0(3)T

12.0(5)T 12.0(8)S

12.1(1)T 12.2

12.2(2) T

12.2(11)T (Eng2)

12.3(4)T

12.3(12) T

X X

X X X X

X X X X X X X X X X

X X X X X X X X X X X X

X X X X X X X X X X X X X X X X

X X X X X X X X X X X X X X X X

X X X X X X X X X X X X X X X X X

X X X X X X X X X X X X X X X X X X36


18


BRKNMS-1204 14528_04_2008_c1


Cisco Public

37

How Does It Work?Hop-by-hop analysis Edge-to-edge measurement Proactive notificationRising and falling thresholds Robust threshold definition for SLAs SNMP traps generated when SLA violatedIP Host SNMP Trap

Management Application

Configure Collect Present

Thresholds can trigger SA operation activation for further analysis

M ea su re

Cisco IOS DeviceIP SLA

Measure

IP SLA

Measure (IP SLA Responder)BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

38


19

IP SLA SenderCisco IOS device that sends probe packets Operation configuration takes place on the sender only Once the operation is finished, all the results are to be polled off the sender Target is another host (IP Host, or IP SLA Responder) Some operations require the target to run the IP SLA responder (Jitter for instance), some other are working with a simple IP Host (ICMP Ping)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

39

IP SLA ResponderRuns on Cisco IOS Configure ip sla monitor responder, or set rttMonApplResponder.0=1 with SNMP Sender uses the IP SLA Control Protocol to communicate with responder before sending the test packets Responder knows the type of operation, the port used, the duration Communication can be authenticated with MD5, not encrypted (offers integrity) Responder inserts in/out timestamps in packet payload (measures CPU time spent) 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

BRKNMS-1204 14528_04_2008_c1

40


20

IP SLA Operation with ResponderControl Message Ask Receiver to Open Port 2020 on UDPIP SLA-Control

IP SLA Sender

IP SLA Responder

UDP, 1967 Responder Says OK Control Phase Start Listening on UDP Port 2020 Sending Test PacketsIP SLA-Test

UDP, 2020

Probing Phase Done: Stop Listening

BRKNMS-1204 14528_04_2008_c1


Cisco Public

41


BRKNMS-1204 14528_04_2008_c1


Cisco Public

42


21

CLI ModificationsRecently, the CLI command rtr was changed to ip sla monitor ALL CLI examples in this presentation are based on CLI phase 2 that started shipping in 12.3(14)T up to 12.4(4)T Starting in 12.4(6)T, the keywords monitor, type, dest-ip, dest-port are removed (CLI phase 3). Optional parameters keep the keywords. After an IOS upgrade to 12.4(6)T, the configuration will automatically be converted (both rtr as well as monitor etc.). rtr commands are transparent! All previous releases still use rtrBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

43

Configuring an Operation

R3(config)#ip sla monitor 1 R3(config-ip-sla-monitor)#type ? IP SLAs entry configuration commands: dhcp DHCP Operation dns DNS Query Operation echo Echo Operation frame-relay Frame-Relay Operation ftp FTP Operation http HTTP Operation path-echo Path Discovered Echo Operation path-jitter Path Discovered Jitter Operation slm SLM Operation tcp-connect TCP Connect Operation udp-echo UDP Echo Operation voip Voice Over IP Operation

BRKNMS-1204 14528_04_2008_c1


Cisco Public

44


22

ICMP Echo OperationPing test Target can be any IP host 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 Processing delays on the source router is subtracted

BRKNMS-1204 14528_04_2008_c1


Cisco Public

45

ICMP Echo Operation (Measurement)T1

IP SLA T3 T2(at Interface Level)

Target Host

Processing Time on the Sender: Tproc = T3-T2 Round Trip Time: T = T3-T1-Tproc T=T3-T1-(T3-T2) T=T3-T1-T3+T2 T=T2-T1

Locally an IP SLA packet will perceive the same scheduling latency as any packet from its class Remember that this type of operation will include the processing time on the target host (see later to avoid this)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

46


23

ICMP Echo Operation (Example)ip sla monitor 2 type echo protocol ipIcmpEcho 10.32.130.2 tos 32 frequency 120 ip sla monitor schedule 2 life forever start-time now

BRKNMS-1204 14528_04_2008_c1


Cisco Public

47

ICMP Echo Operation (Output)R3#show ip sla stat 2

Round Trip Time (RTT) for Latest RTT: 100 ms

Index 2

Latest operation start time: *17:32:53.315 CET Tue Feb 21 2006 Latest operation return code: Timeout Number of successes: 0 Number of failures: 1 Operation time to live: Forever

BRKNMS-1204 14528_04_2008_c1


Cisco Public

48


24

UDP Echo OperationUses either well-known UDP port 7 (echo service) or any other custom port Requires responder for more accurate results: processing delays subtracted on both source and destinationip sla monitor 3 type udp-echo 172.16.6.1 7 ip sla monitor schedule 3 start-time now

BRKNMS-1204 14528_04_2008_c1


Cisco Public

49

UDP Echo Operation (With IP SLA Responder)T1 T2

T3 Source T5 T4 Responder

Processing Delay on the Source: Tps = T5-T4 Processing Delay on the Destination: Tpd = T3-T2 Total Delay: T = T5-T1-Tps-Tpd T = T5-T1-(T5-T4)-(T3-T2) T = T5-T1-T5+T4-T3+T2 T = T2+T4-T1-T3

We have no control on the queuing delay (neither source nor destination) Queuing delay is usually negligible, but might become a problem on highly utilized interfaces

BRKNMS-1204 14528_04_2008_c1


Cisco Public

50


25

UDP Echo Operation (Output)R3#show ip sla monitor stat 3 details Round Trip Time (RTT) for Index 3 Latest RTT: 1 milliseconds Latest operation start time: *17:42:45.475 CET Tue Feb 21 2006 Latest operation return code: OK Over thresholds occurred: FALSE Number of successes: 1 Number of failures: 3 Operation time to live: 3397 sec Operational state of entry: Active Last time this entry was reset: Never

BRKNMS-1204 14528_04_2008_c1


Cisco Public

51

TCP Connect OperationTCP Connect Operation measures the time taken by the source to perform a TCP connect operation to the destination device Target can be normal host or IP SLA responder Useful in simulating Telnet, SSH, SQL, connection time

BRKNMS-1204 14528_04_2008_c1


Cisco Public

52


26

TCP Connect Operation (Measurement)T1

SYN SYN/ACK

T2 ACK Source FIN Destination

The measured connecting time is the difference between sending the initial SYN and receiving the ACK, in this case = T2-T1

BRKNMS-1204 14528_04_2008_c1


Cisco Public

53

TCP Connect Operation (Example)ip sla monitor 123 type tcp-connect 10.52.132.68 9 control disable ip sla schedule 123 start-time now

Connects to TCP Connection to 10.52.132.68 on port 9

If the target host is not running IP SLA, disable the Control Protocol (optional). Default: enabled

BRKNMS-1204 14528_04_2008_c1


Cisco Public

54


27

TCP Connect Operation (Output)Router#sh ip sla monitor statistics 123 detailRound trip time (RTT) Index 123 Latest RTT: 1 ms Latest operation start time: 14:20:26.272 CET Mon Mar 13 2006 Latest operation return code: OK Over thresholds occurred: FALSE Number of successes: 24 Number of failures: 0 Operation time to live: Forever Operational state of entry: Active Last time this entry was reset: Never

BRKNMS-1204 14528_04_2008_c1


Cisco Public

55

UDP Jitter OperationMeasures the delay, delay variance (jitter) and packet loss by generating periodic UDP traffic Measures: per-direction jitter, per-direction packet-loss, and round trip time Detect and report out-of-sequence and corrupted packets One-way delay requires Cisco IOS 12.2(2)T or later and clock synchronization between source and destination Always requires IP SLA responder Starting Cisco IOS 12.3(4)T, the operation can measure MOS and ICPIF scores for VoIP 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

BRKNMS-1204 14528_04_2008_c1

56


28

UDP Jitter: Packet StreamSend train of packets cith constant interval Receive train of packets at Interval, impacted by the network

IP CoreIP SLA Responder

Per-Direction Inter-Packet Delay (Jitter) Per-Direction Packet Loss Average Round Trip Delay

The Responder adds a Receive Time Stamp and replies to Packets.

BRKNMS-1204 14528_04_2008_c1


Cisco Public

57

UDP Jitter: Measurement ExampleSend PacketsSTx = Sent tstamp for Packet x

Receive Packets i2

P2ST2

i1

P1ST1

P2 IP CoreRT2 Responder

P1RT1

IP SLA

RTx = Receive tstamp for Packet x

Reflected Packets

Reply to Packets

dx = Processing Time Spent Between Packet Arrival and Treatment

P1AT1ATx = Receive tstamp for Packet x

i4

P2AT2

P1RT1+d1

i3

P2RT2+d2

Each Packet Contains STx, RTx, ATx, dx and the Source Can Now Calculate: JitterSD = (RT2-RT1)-(ST2-ST1) = i2-i1 JitterDS = (AT2-AT1)-((RT2+d2)-(RT1+d1)) = i4-i3

BRKNMS-1204 14528_04_2008_c1


Cisco Public

58


29

UDP Jitter OperationJitter Computation If packets are sent with 10ms interval, positive jitter means they have been received with more than 10ms interval Negative jitter means less than 10ms interval Zero jitter means they are received with the same inter-packet delay (the variance is zero) Jitter should remain as low as possible for real-time traffic such as voice over IP No need to have clocks synchronized

BRKNMS-1204 14528_04_2008_c1


Cisco Public

59

UDP Jitter OperationOne-Way Delay Computation One-way delay measurement requires the clocks on source and target routers synchronized Use Network Time Protocol (NTP) server, eventually with GPS device as reference Use a GPS device on the auxiliary port of a 7200 (ex: Trimble Palisade GPS) If the time is not synchronized, IP SLA ignores the measurement by filling in 0s

BRKNMS-1204 14528_04_2008_c1


Cisco Public

60


30

UDP Jitter OperationPacket LossSenderSend Counter: 1

Result: PacketLossSD = 1 PacketLossDS = 1

ResponderRx Counter: 1 Ack: (1,1) Rx Counter: 2Current RxCount Index of the ACKd packet

Rx: (1,1)Send Counter: 2

Send Counter: 3

Ack: (2,2) Rx Counter: 3 Ack: (3,3)

Rx: (3,3)Send Counter: 4


TimeBRKNMS-1204 14528_04_2008_c1 BRKNMS-1204 14528_04_2008_c1

R received the packet, but did not receive the ACK: PacketLossDS + 1

Send Counter: 5

Rx Counter: 4 Ack: (5,4)

Rx: (5,4)

R missed a packet (only 4 received while 5 sent: PacketLossSD += 1


Cisco Public

61

UDP Jitter Operation (Example)Typical IP SLAs configuration (12.4(4)T):ip sla monitor 10 type Jitter dest-ipaddr 10.52.130.68 dest-port 3456 interval 10 num-packets 20 source-ipaddr 1.1.1.2 source-port 80[control] ip sla monitor schedule 10 start-time now

UDP Jitter Operation to 10.52.130.68, Port 3456 Send 20 packets each time

IP SLAs CLI Conversion Document in 12.3(14)T and Above: www.cisco.com/en/US/products/ps6602/products_white_paper 0900aecd8022c2cc.shtml 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

62

31

UDP Voice Jitter Operation (Example)Simulating G.711 VoIP call Use RTP/UDP ports 16384 and above, the packet size is 172 bytes (160 bytes of payload, 12 bytes for RTP header) Packets are sent every 20 milliseconds (interval) Marked with DSCP value of 8 (TOS equivalent 0x20) Runs every minute (frequency)ip sla monitor 1 type jitter dest-ipaddr 10.0.0.2 dest-port 5556 num-packets 1000 request-data-size 172 tos 32 ip sla monitor schedule 1 life forever start-time now

B A

C A = 20 ms B = 20 s (1000 x 20 ms) C = 40 s (60 s 20 s)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

63

UDP Voice Jitter Operation (Output) [1/3]Router#sh ip sla mon sta 1 detail Round trip time (RTT) Index 1 Latest RTT: 1 ms Latest operation start time: *18:32:08.279 PST Tue Mar 14 2006 Latest operation return code: OK Over thresholds occurred: FALSE RTT Values Number Of RTT: 1000 RTT Min/Avg/Max: 1/1/4 ms Latency one-way time milliseconds Number of Latency one-way Samples: 0 Source to Destination Latency one way Min/Avg/Max: 0/0/0 ms Destination to Source Latency one way Min/Avg/Max: 0/0/0 ms Source to Destination Latency one way Sum/Sum2: 0/0 Destination to Source Latency one way Sum/Sum2: 0/0 (cont)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

64


32

UDP Voice Jitter Operation (Output) [2/3](cont) Jitter time milliseconds Number of Jitter Samples: 999 Source to Destination Jitter Min/Avg/Max: 1/3/8 ms Destination to Source Jitter Min/Avg/Max: 1/2/4 ms Source to destination positive jitter Min/Avg/Max: 1/3/8 ms Source to destination positive jitter Number/Sum/Sum2: 413/1578/6188 Source to destination negative jitter Min/Avg/Max: 3/3/8 ms Source to destination negative jitter Number/Sum/Sum2: 409/1574/6190 Destination to Source positive jitter Min/Avg/Max: 1/2/4 ms Destination to Source positive jitter Number/Sum/Sum2: 398/1086/3252 Destination to Source negative jitter Min/Avg/Max: 1/2/4 ms Destination to Source negative jitter Number/Sum/Sum2: 395/1089/3285 Interarrival jitterout: 0 Interarrival jitterin: 0 Packet Loss Values Loss Source to Destination: 0 Loss Destination to Source: 0 Out Of Sequence: 0 Tail Drop: 0 Packet Late Arrival: 0 Voice Score Values Calculated Planning Impairment Factor (ICPIF): 0 Mean Opinion Score (MOS): 0 Number of successes: 1 Number of failures: 0 Operation time to live: Forever Operational state of entry: Active Last time this entry was reset: NeverBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

65

UDP Voice Jitter Operation (Output) [3/3]Average positive jitter.

Smallest positive jitter. Biggest positive jitter.

Source to destination positive jitter Min/Avg/Max: 1/3/8 ms

Sum of all positive jitter.

Source to destination positive jitter Number/Sum/Sum2: 413/1578/6188Total number of packets with a positive jitter. Sum the squares of all positive jitter.

BRKNMS-1204 14528_04_2008_c1


Cisco Public

66


33

DHCP OperationUseful for Cable/DSL providers that uses DHCP for dynamic address allocation Measures the time taken to discover a DHCP Server and obtain a lease from it IP SLA releases the leased IP address after the operationip sla monitor 30 type dhcp dest 10.1.1.1 [opt 82] ip sla monitor schedule 30 start-time now

This feature enables the router to include information about itself and the attached client when forwarding DHCP requests to a DHCP serverBRKNMS-1204 14528_04_2008_c1


Cisco Public

67

DNS OperationDifference between the time taken to send a DNS request and the time a reply is received Check your DNS performance, a critical element for surfers speed feeling The IP SLA DNS operation queries for an IP address if the user specifies hostname (forward), or queries for a hostname if the user specifies an IP address (reverse) Do not revert back to TCP if the DNS UDP query fails

BRKNMS-1204 14528_04_2008_c1


Cisco Public

68


34

DNS Operation (Example)ip sla monitor 40 type dns target-addr www.cisco.com name-server 10.1.1.1 ip sla monitor schedule 40 start-time now

Resolve www.cisco.com to an IP Address

Against the DNS Server 10.1.1.1

BRKNMS-1204 14528_04_2008_c1


Cisco Public

69

HTTP OperationMeasures HTTP server responsiveness: DNS request, TCP connection, time to first byte, HTTP transaction time HTTP Proxy servers supported IP SLA Responder cannot be used Supports GET requests and custom RAW requests:GET requestIP SLA will format the request based on the URL specified RAWOne must specify the entire content of the HTTP request; this gives ultimate flexibility for user to control fields such as authentication

BRKNMS-1204 14528_04_2008_c1


Cisco Public

70


35

HTTP Operation (Measurement)DNS REQ DNS RTT DNS ANS

DNS ServerSYN TCP RTT SYN/ACK ACK Time to First Byte GET / HTTP RTT FIN FIN/ACK ACK

IP SLA

HTTP Server

BRKNMS-1204 14528_04_2008_c1


Cisco Public

71

HTTP Operation (GET Example)Simple GET Request to Serverwww.cisco.com

ip sla monitor 50 type http operation get url http://www.cisco.com/go/ipsla ip sla monitor schedule 50 start-time now

Options:cache name-server proxy source-ipaddr source-port version Enable or Disable download of cached HTTP page Name Server Proxy information Source Address Source Port Version Number

BRKNMS-1204 14528_04_2008_c1


Cisco Public

72


36

HTTP Operation (Output)Router#sh ip sla monitor stat 50 Round Trip Time (RTT) for Index 50 Latest RTT: 193 ms Latest operation return code: OK Latest operation start time: *18:32:08.279 PST Tue Mar 14 2006 Latest DNS RTT: 4 ms Latest TCP Connection RTT: 8 ms Latest HTTP Transaction RTT: 181 ms Number of successes: 1 Number of failures: 0 Operation time to live: 3593 sec

Total = DNS RTT + TCP RTT + HTTP RTT

BRKNMS-1204 14528_04_2008_c1


Cisco Public

73

HTTP Operation (RAW Authentication)Use RAW for a HTTP GET Operation on Server www.cisco.com; the Requested Page Is Password Protected

ip sla monitor 60 type http operation raw url http://www.cisco.com http-raw-request GET /lab/index.html HTTP/1.0\r\n Authorization: Basic btNpdGT4biNvoZe=\r\n \r\n exit ip sla monitor schedule 60 start-time now

user:password Encoded in Base64BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

74


37

HTTP Operation (Example: Proxy)Use Proxy example-proxy to Get to a Page on the Server www.cisco.com

ip sla monitor 70 type http operation get url http://www.cisco.com proxy.cisco.com:80 ip sla monitor schedule 70 start-time now

proxy http://example-

BRKNMS-1204 14528_04_2008_c1


Cisco Public

75

FTP OperationMeasures the time to download a file Do not abuse: big files gives more realistic results while consumes more bandwidth Active or passive mode Does not work with IP SLA responder

BRKNMS-1204 14528_04_2008_c1


Cisco Public

76


38

FTP Operation (Example)Get the file /home/user/test.capip sla monitor 80 type ftp operation get url ftp://user:[email protected]/test.cap [mode] ip sla monitor schedule 80 start-time now

Get the file in /test.capip sla monitor 81 type ftp operation get url ftp://user:[email protected]//test.cap [mode] ip sla monitor schedule 81 start-time now

Absolute vs. Relative Path

[mode]: active or passive ftpBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

77

FTP Operation (Output)Router#sh ip sla monitor stat 80 Entry number: 80 Modification time: *19:15:28.968 UTC Tue Mar 14 2006 Number of Octets Used by this Entry: 3264 Number of operations attempted: 1 Number of operations skipped: 0 Current seconds left in Life: 3591 Operational state of entry: Active Download Bandwidth was: Last time this entry was reset: Never 294792 bytes/587 s = 502 KB/s Connection loss occurred: FALSE Timeout occurred: FALSE Over thresholds occurred: FALSE Latest RTT (milliseconds): 587 Latest operation start time: *19:15:28.972 UTC Tue Mar 14 2006 Latest operation return code: OK Bytes read: 294792

BRKNMS-1204 14528_04_2008_c1


Cisco Public

78


39

PathJitter OperationRuns in two phases: route discovery, and hops evaluation (see next slide) Per hop round trip time Per hop packet loss Per hop cumulated Jitter with noise reduction (RFC1889) No IP SLA responder required on the destination, nor on the hops

Note: Requires Cisco IOS Version 12.2(2)T or LaterBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

79

PathJitter Operation (Two Phases)Hop 1

Destination

Source Hop 2

1. 2.

Discover the path with traceroute Evaluate each hop one by one for RTT, packet lost, and round-trip total Jitter

BRKNMS-1204 14528_04_2008_c1


Cisco Public

80


40

PathJitter Operation (Example)Trace the Hops to 10.52.128.1:

ip sla monitor 11 type path-jitter dest-ipaddr 10.52.128.1 [options] ip sla monitor schedule 11 start-time now

options: interval num-packets source-ipaddr targetOnly Inter packet interval Number of packets to be transmitted Source IP Address Perform Path Jitter on destination only

BRKNMS-1204 14528_04_2008_c1


Cisco Public

81

PathJitter Operation (Output)sh ip sla mon stat 11 details ---- Path Jitter Statistics ---Source IP Destination IP Number of Echos Interval between Echos Target Only Hop IP 10.52.132.2: RTT:1 MinRTT:1 MinPosJitter:1 MinNegJitter:0 OutOfSequence:0 Hop IP 10.52.128.1: RTT:1 MinRTT:1 MinPosJitter:2 MinNegJitter:1 OutOfSequence:0 10.52.132.5 10.52.128.1 10 20 ms Disabled (default)

PacketLoss:0 MaxRTT:2 MaxPosJitter:1 MaxNegJitter:0 DiscardedSamples:0 PacketLoss:0 MaxRTT:3 MaxPosJitter:2 MaxNegJitter:1 DiscardedSamples:0

Jitter:0 SumRTT:19 SumPos:1 SumNeg:0

Sum2RTT:37 Sum2Pos:1 Sum2Neg:0

Jitter:0 SumRTT:14 SumPos:2 SumNeg:2

Sum2RTT:24 Sum2Pos:4 Sum2Neg:2

BRKNMS-1204 14528_04_2008_c1


Cisco Public

82


41

Post Dial and Gatekeeper DelaysSIP and H.323 This feature adds the capability to monitor call setup delay for VoIP calls Requires Cisco IOS 12.3(12)T or later

ip sla monitor 21 type voip delay gatekeeper registration ip sla monitor schedule 21 life forever start-time now

ip sla monitor 22 type voip delay post-dial [destination | detect point] ip sla monitor schedule 22 life forever start-time now

BRKNMS-1204 14528_04_2008_c1


Cisco Public

83

Enhanced Object Tracking with IP SLAUses IP SLA operation as a metric for HSRP Introduced in Cisco IOS 12.3(4)T and 12.2(25)Sip sla monitor 31 type echo protocol ipIcmpEcho 10.51.12.4 timeout 1000 frequency 3 threshold 2 ip sla monitor schedule 1 start-time now life forever ! track 2 rtr 1 state track 3 rtr 1 reachability ! interface e0/1 ip address 10.21.0.4 255.255.0.0 standby 3 ip 10.21.0.10 standby 3 priority 120 standby 3 preempt standby 3 track 2 standby 3 track 3

BRKNMS-1204 14528_04_2008_c1


Cisco Public

84


42

Cisco IOS IP SLA Uses and MetricsData Traffic Minimize delay, packet loss Verify Quality of Service (QoS) VoIP Minimize delay, packet loss, jitter Service Level Agreement Measure delay, packet loss, jitter One-way Reachability Connectivity testing Application testing Streaming Video* Minimize delay, packet loss

BRKNMS-1204 14528_04_2008_c1

BRKNMS-1204 14528_04_2008_c1


Requirement IP SLA Measurement

Jitter Packet loss Latency per QoS

Jitter Packet loss Latency MOS Voice Quality Score

Jitter Packet loss Latency One-way Enhanced accuracy NTP

Connectivity tests to IP devices Connectivity tests to network services (DHCP, DNS, http)

Jitter Packet loss Latency

*IP SLA Has No Specific Monitoring Option for Streaming Video and Does Not Generate IP SLA Video Streams 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

85



Cisco Public

86

43

Schedule and StopTo schedule operation to start:ip sla monitor schedule [life seconds] [start-time {pending | now | hh:mm [month day |day month]}][ageout seconds]

To stop a running operation :no ip sla monitor schedule

BRKNMS-1204 14528_04_2008_c1


Cisco Public

87

Scheduling CaveatIf you configure multiple operations to start now, all will start at the same time after a router reload Consider using the option after instead of now Example, new operations are started every second:

ip sla monitor schedule start-time after 00:01:00 ip sla monitor schedule start-time after 00:01:01 ip sla monitor schedule start-time after 00:01:02

BRKNMS-1204 14528_04_2008_c1


Cisco Public

88


44

Multi-Operation Scheduler (Configuration)Start many operations at once, with automatic smooth start-time Example, start operations 1 to 10 within 10 seconds:

ip sla monitor group schedule 1 1-10 schedule-period 10 start-time now sh ip sla monitor operation | include start Latest operation start time: *12:50:51.599 PST Mon Apr 18 Latest operation start time: *12:50:52.599 PST Mon Apr 18 Latest operation start time: *12:50:53.599 PST Mon Apr 18 Latest operation start time: *12:50:34.579 PST Mon Apr 18 Latest operation start time: *12:50:35.579 PST Mon Apr 18 Latest operation start time: *12:50:36.579 PST Mon Apr 18 Latest operation start time: *12:50:37.579 PST Mon Apr 18 Latest operation start time: *12:50:38.579 PST Mon Apr 18 Latest operation start time: *12:50:39.579 PST Mon Apr 18 Latest operation start time: *12:50:40.591 PST Mon Apr 18

2005 2005 2005 2005 2005 2005 2005 2005 2005 2005

BRKNMS-1204 14528_04_2008_c1


Cisco Public

89

Multi-Operation Scheduler (Status)Show Command:

r1#show ip sla monitor group schedule Group Entry Number: 1 Probes to be scheduled: 1-10 Total number of probes: 10 Schedule period: 10 Mode: even Group operation frequency: Equals schedule period Status of entry (SNMP RowStatus): Active Next Scheduled Start Time: Start Time already passed Life (seconds): 3600 Entry Ageout (seconds): never

BRKNMS-1204 14528_04_2008_c1


Cisco Public

90


45

Reaction Actions and Operation Trigger

Router(config)#ip sla monitor reaction-configuration ? action-type ip sla Reaction Action Type connection-loss-enable ip sla Enable Connection Loss Reaction threshold-falling ip sla Falling Threshold Value threshold-type ip sla Reaction Threshold Type timeout-enable ip sla Enable Timeout Reaction Router(config)#ip sla monitor reaction-trigger

BRKNMS-1204 14528_04_2008_c1


Cisco Public

91

VRF-Awareness Issue (for MPLS/VPN)How to send probe packets from IP SLA to a specific VPN? By default, local processes are not executed in a VRF contextIP SLA (PE)

10.10.10.1

10.11.10.1

10.12.10.1

Route lookup is done in the global routing table, and the wrong route is selected

CEs with VRFs Red, Blue and Yellow

We Need a Way to Execute an Operation in a VRF Contexte.g., Red, Blue or YellowBRKNMS-1204 14528_04_2008_c1


Cisco Public

92


46

Solution: IP SLA for MPLS/VPNIP SLA operations are VRF-aware since 12.2(2)T, 12.2(6)S, 12.0(26)S Supported on ICMP Echo, ICMP Path Echo, UDP Echo, and UDP Jitter operations Allows measurement from PE to anything Use vrf vrf-name option

BRKNMS-1204 14528_04_2008_c1


Cisco Public

93

IP SLA for MPLS/VPN (Example)Sends Probes to a Remote IP SLA in the Context of the Blue VPN:

ip sla monitor 41 type jitter dest-ipaddr 1.1.1.1 dest-port 80 vrf blue ip sla monitor schedule 41 start-time now

BRKNMS-1204 14528_04_2008_c1


Cisco Public

94


47

TOS MarkingProbes can be TOS marked to match the target class Only TOS setting is supported, no diffserv (see next slide to perform translation)

ip sla monitor 11 type jitter dest-ipaddr 10.52.130.68 dest-port 16384 \ interval 20 num-packets 1000 tos 0x20 frequency 60 request-data-size 172 ip sla monitor schedule 11 start-time now

BRKNMS-1204 14528_04_2008_c1


Cisco Public

95

Converting Between TOS and DiffServ128 4 64 2 32 1 16 8 4 2 1

TOS (RFC795)

P2

P1

P0

T3

T2ToS

T1

T0

CU

In Cisco IOS the 8 TOS bits are set from right to left

precedence

Always zero 32 16 8 4 2 1

DiffServ (RFC2474)

D5

D4

D3

D2

D1

D0

CU

CU

DSCP (6 bits)

Multiply by 4

Divide by 8

Binary 101 000 101 100 001 110BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved.

ToS 160 (0xA0) 176 (0xB0) 56 (0x38)Cisco Public

DSCP 40 44 14

Precedence 5 5 196


48


BRKNMS-1204 14528_04_2008_c1


Cisco Public

97

IP SLA Application Version

R3#show ip sla monitor application IP Service Level Agreements Version: Round Trip Time MIB 2.2.0, Infrastructure Engine-II Time of last change in whole IP SLAs: *17:46:22.215 CET Tue Feb 21 2006 Estimated system max number of entries: 10852 Estimated Number of Number of Number of Number of number of configurable operations: 10847 Entries configured : 5 active Entries : 2 pending Entries : 0 inactive Entries : 3

Maximum Number of Configurable Operations

Supported Operation Types Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform: Type of Operation to Perform:

dhcp dns echo frameRelay ftp http jitter pathEcho pathJitter tcpConnect udpEcho voip

Supported Operations

IP SLAs low memory water mark: 14976312

Memory LimitBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

98


49

Operational StateShow the Actual State of an Operation: Old commandshow rtr operational-state operation-number

New commandshow ip sla monitor statistics operation-number [details]

BRKNMS-1204 14528_04_2008_c1


Cisco Public

99

Display the Configuration State (Incl. Defaults)

R3#show ip sla monitor configuration 1 IP SLAs, Infrastructure Engine-II. Entry number: 1 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: 1000/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): 60 (not considered if randomly scheduled) 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:

BRKNMS-1204 14528_04_2008_c1


Cisco Public

100


50

Deleting OperationsTo delete one operation :router(config)# no ip sla monitor

To delete all operations:router(config)# ip sla monitor reset

BRKNMS-1204 14528_04_2008_c1


Cisco Public

101

Debugging an Operations ActivitiesTo debug operation activity:debug ip sla monitor trace

To debug activity of the responder:debug ip sla monitor trace 0

The Responder Is the Equivalent of Operation Zero

BRKNMS-1204 14528_04_2008_c1


Cisco Public

102


51

Debugging an Operations ErrorsTo debug errors for operation :router# debug ip sla monitor error

To debug errors the responder:router# debug ip sla monitor error 0

The Responder Is the Equivalent of Operation Zero

BRKNMS-1204 14528_04_2008_c1


Cisco Public

103

Debug Sample Output

16:27:45.402: ip sla 1: Starting An Echo Operation - IP sla Probe 1 16:27:45.406: source=10.52.132.69(49175) dest-ip=10.52.132.68(9999) 16:27:45.406: sending control msg: 16:27:45.406: Ver: 1 ID: 144 Len: 52 16:27:45.406: cmd: command: RTT_CMD_JITTER_PORT_ENABLE, ip: 10.52.132.68, port: 9999, duration: 5200 16:27:45.414: receiving reply 16:27:45.414: Ver: 1 ID: 144 Len: 8 16:27:45.422: sdTime: 2104279296 dsTime: -2017879294 16:27:45.422: responseTime (1): 2 16:27:45.442: sdTime: 2104279296 dsTime: -2017879295 16:27:45.442: jitterOut: 0 16:27:45.442: jitterIn: -1 16:27:45.442: responseTime (2): 1

BRKNMS-1204 14528_04_2008_c1


Cisco Public

104


52


BRKNMS-1204 14528_04_2008_c1


Cisco Public

105

Scenario 1: Service Provide Core NetworkShadow Router at Each PoPPoP2

PoP1

PoP3

PoP4

PE

P

PE PE

Shadow Router (2600, 3600) Dedicated for IP SLA Possible GPS feed for clock synchronisation (one-way delay) 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

BRKNMS-1204 14528_04_2008_c1

106


53

Scenario 1: Service Provide Core NetworkExtending Monitoring to the Customer SitesHierarchical Polling PoP to CPE

PoP2

PoP1

PoP3

PoP4

BRKNMS-1204 14528_04_2008_c1


Cisco Public

107

Scenario 1: Service Provide Core NetworkScalability Versus Accuracy

PoP2

PoP1

PoP3

PoP4

# of operations = PoP(PoP-1) + 1 for each CPE versus # of operations =CPE(CPE-1)BRKNMS-1204 14528_04_2008_c1


Cisco Public

108


54

Scenario 1: Service Provide Core NetworkBest Practice: NOC to POP/CE SLACE CE

PoP2

NOC

PoP3 PoP1

CE

PoP4

Best practice suggests using 1 site to poll the others to increase manageability when network design changes are requiredBRKNMS-1204 14528_04_2008_c1


Cisco Public

109

Scenario 1: Service Provide Core NetworkBest Practice: CE to CE SLACE CE

PoP2 NOC PoP3 PoP1

CE

CE

PoP4

For increased accuracy, define CE to CE polling. Drawback: less flexible, more overhead.BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

110


55

Scenario 2: Enterprise WANISP SLA Monitoring

CE

PE

PE

CE

ISP

CPE

CPE

Enterprise (CPE to CE)

ISP Network (CE to CE)

Enterprise (CPE to CE)

End-to-End (CPE to CPE)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

111

Scenario 2: Enterprise WANHierarchical MonitoringCorp. HQ Data Center Regional Aggregation Remote Campus

HomeOffi ce

Retail Branch

Network Connectivity Server Connectivity

Small Office

BRKNMS-1204 14528_04_2008_c1


Cisco Public

112


56

Scenario 3: Network ServicesMonitoring DNS, DHCP, Email, Web Servers

DNS

DHCP

Email

Web

BRKNMS-1204 14528_04_2008_c1


Cisco Public

113

ReferencesCisco IOS IP SLA Web site on CCO:http://www.cisco.com/go/ipsla This page contains links to executive and technical documents, documentation, and white papers

Suggested reading:Cisco IOS IP Service Level Agreements User Guide Accurate Network Performance Monitoring using Cisco IOS IP SLA

BRKNMS-1204 14528_04_2008_c1


Cisco Public

114


57

IP SLA Email AliasesCisco IOS IP SLAs External Self-Help User Community:[email protected] [email protected]

Cisco IOS IP SLAs External Announcements:[email protected] [email protected]

BRKNMS-1204 14528_04_2008_c1


Cisco Public

115

A Complementary Solution

NetFlowFrom where? To Who? When? How Much? Which Apps? What ToS?

IP SLALatency Loss Jitter Server Delay (HTTP, DNS, TCP Connect)

BRKNMS-1204 14528_04_2008_c1


Cisco Public

116


58

SummarySLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios

BRKNMS-1204 14528_04_2008_c1


Cisco Public

117

ConclusionIP SLA is the integrated Cisco IOS feature to actively measure and report applications and network performance It offers a broad set of measurement functions Several network management applications support it Stay tunedwe have an ambitious roadmap for new features What other features would you like to see added?

BRKNMS-1204 14528_04_2008_c1


Cisco Public

118


59

Q and A

BRKNMS-1204 14528_04_2008_c1


Cisco Public

119

Recommended ReadingContinue your Cisco Live learning experience with further reading from Cisco Press Check the Recommended Reading flyer for suggested books Please refer to the work titled Accounting and Performance Management at the URL below:

http://www.ciscopress.com/b ookstore/product.asp?isbn= 1587051982&rl=1

Available Onsite at the Cisco Company StoreBRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public

120


60

Complete Your Online Session EvaluationGive us your feedback and you could win fabulous prizes. Winners announced daily. Receive 20 Passport points for each session evaluation you complete. Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.Dont forget to activate your Cisco Live virtual account for access to all session material on-demand and return for our live virtual event in October 2008. Go to the Collaboration Zone in World of Solutions or visit www.cisco-live.com.

BRKNMS-1204 14528_04_2008_c1


Cisco Public

121

BRKNMS-1204 14528_04_2008_c1


Cisco Public

122


61

IPSLA

Documents

Transcript of IPSLA