Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
BRKNMS-1204
BRKNMS-1204 14528_04_2008_c1
Cisco Public
Abstract
This 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
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
Businesses are relying on them for mission critical applications (voice, video, SAP)
BRKNMS-1204 14528_04_2008_c1
Cisco Public
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.
SLA Components
Metrics:
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/reparations
BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public
SLA Criteria
Easy to understand Simple and light to measure Attainable Meaningful Controllable Application/service driven
BRKNMS-1204 14528_04_2008_c1
Cisco Public
BRKNMS-1204 14528_04_2008_c1
Cisco Public
10
Quantify Results
Reduced deployment time? Prove service and application differentiation Verify SLA Reduced network downtime?
Fine-Tune and Optimize I) Ongoing Measurements to Understand Behavior. II) Define Proactive Notifications
11
BRKNMS-1204 14528_04_2008_c1
Cisco Public
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
12
Murphys Law
If 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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
14
t
BRKNMS-1204 14528_04_2008_c1
Cisco Public
15
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
17
18
BRKNMS-1204 14528_04_2008_c1
Cisco Public
19
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
20
10
Manually
Time consuming approach
BRKNMS-1204 14528_04_2008_c1
Cisco Public
21
Reuse your current equipment and enhance existing network management applications
IP SLA
BRKNMS-1204 14528_04_2008_c1
Cisco Public
22
11
IP SLA History
Used 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.
time
Engine:
Feature Name:
CLI:
BRKNMS-1204 14528_04_2008_c1
Cisco Public
23
BRKNMS-1204 14528_04_2008_c1
Cisco Public
24
12
Observed/Passive
Collection Method
Synthetic/Active
Embedded Agents
External Probes
Scope of Measurement
Device/Link
Perspective of Measurement
End-to-End/Path
User
Network
BRKNMS-1204 14528_04_2008_c1
Cisco Public
25
Synthetic
Definition
Network traffic generated strictly for the purpose of measuring a network performance characteristic
Advantages
Most accurate for live application traffic on a specified link
Advantages
Measures performance: Between any two points in the network Controllable, on a continuous basis By traffic class based on IP Precedence marking
Disadvantages
Limited 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
Disadvantages
Only an approximation for performance of live traffic Inject some traffic in the network
BRKNMS-1204 14528_04_2008_c1
Cisco Public
26
13
External
Definition
Mechanisms for collection of network statistics are provided by a stand-alone device specifically designed to collect network performance statistics
Advantages
Follows network infrastructure Gathers metrics that cannot be observed externally End-to-end monitoring
Advantages
Validation of performance performed independent of the devices that transmit network traffic
Disadvantages
More hardware to administer Observed statistics limited to points of deployment Scale and distribution issues
Disadvantages
Performance monitoring has devicelevel performance implications
BRKNMS-1204 14528_04_2008_c1
Cisco Public
27
End to End
Definition
Performance measurement based on analysis of response time across two or more network devices, and typically based on latency
Advantages
Detailed application performance monitoring of critical network links
Advantages
Starting point performance troubleshooting Reflects end-user experience
Disadvantages
When network-wide performance problems exist, how does one select which device or link to evaluate?
Disadvantages
Prior knowledge of relevant end-to-end paths is needed
BRKNMS-1204 14528_04_2008_c1
Cisco Public
28
14
Network
Definition
Measurement based on performance statistics measured in network devices
Advantages
Accurate measurement of end-user experience
Advantages
Easy to deploy, and non-intrusive to the desktop Identifies network performance issue
Disadvantages
Scale and distribution issues Intrusive on the desktop
Disadvantages
Imperfect understanding of end-user experience
BRKNMS-1204 14528_04_2008_c1
Cisco Public
29
BRKNMS-1204 14528_04_2008_c1
Cisco Public
30
15
BRKNMS-1204 14528_04_2008_c1
Cisco Public
31
Proactive Notification
Can 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
WAN
SN p tra MP
NMS
BRKNMS-1204 14528_04_2008_c1
www.cisco.com
32
Cisco Public
16
BRKNMS-1204 14528_04_2008_c1
Cisco Public
33
Access
Cisco IOS Software Releases 12.3T and 12.4
Cisco Public
34
17
BRKNMS-1204 14528_04_2008_c1
Cisco Public
35
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 X
36
18
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
37
Management Application
M ea su re
Measure
IP SLA
38
19
IP SLA Sender
Cisco 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 Responder
Runs 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 Sender
IP SLA Responder
UDP, 1967 Responder Says OK Control Phase Start Listening on UDP Port 2020 Sending Test Packets
IP SLA-Test
UDP, 2020
BRKNMS-1204 14528_04_2008_c1
Cisco Public
41
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
42
21
CLI Modifications
Recently, 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 rtr
BRKNMS-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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
45
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
47
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
49
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
51
BRKNMS-1204 14528_04_2008_c1
Cisco Public
52
26
SYN SYN/ACK
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
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
55
BRKNMS-1204 14528_04_2008_c1
56
28
IP Core
IP SLA Responder
Per-Direction Inter-Packet Delay (Jitter) Per-Direction Packet Loss Average Round Trip Delay
BRKNMS-1204 14528_04_2008_c1
Cisco Public
57
Receive Packets i2
P2
ST2
i1
P1
ST1
P2 IP Core
RT2 Responder
P1
RT1
IP SLA
Reflected Packets
Reply to Packets
P1
AT1
ATx = Receive tstamp for Packet x
i4
P2
AT2
P1
RT1+d1
i3
P2
RT2+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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
59
BRKNMS-1204 14528_04_2008_c1
Cisco Public
60
30
Responder
Rx Counter: 1 Ack: (1,1) Rx Counter: 2
Current RxCount Index of the ACKd packet
Rx: (1,1)
Send Counter: 2
Send Counter: 3
Rx: (3,3)
Send Counter: 4
Time
BRKNMS-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: (5,4)
Cisco Public
61
UDP Jitter Operation to 10.52.130.68, Port 3456 Send 20 packets each time
62
31
B A
BRKNMS-1204 14528_04_2008_c1
Cisco Public
63
BRKNMS-1204 14528_04_2008_c1
Cisco Public
64
32
65
BRKNMS-1204 14528_04_2008_c1
Cisco Public
66
33
DHCP Operation
Useful 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 operation
ip 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 server
BRKNMS-1204 14528_04_2008_c1
Cisco Public
67
DNS Operation
Difference 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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
69
HTTP Operation
Measures 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
DNS Server
SYN TCP RTT SYN/ACK ACK Time to First Byte GET / <HTML> </HTML> HTTP RTT FIN FIN/ACK ACK
IP SLA
HTTP Server
BRKNMS-1204 14528_04_2008_c1
Cisco Public
71
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
73
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
74
37
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 Operation
Measures 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
77
BRKNMS-1204 14528_04_2008_c1
Cisco Public
78
39
PathJitter Operation
Runs 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
79
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
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
PacketLoss:0 MaxRTT:2 MaxPosJitter:1 MaxNegJitter:0 DiscardedSamples:0 PacketLoss:0 MaxRTT:3 MaxPosJitter:2 MaxNegJitter:1 DiscardedSamples:0
BRKNMS-1204 14528_04_2008_c1
Cisco Public
82
41
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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
84
42
BRKNMS-1204 14528_04_2008_c1
BRKNMS-1204 14528_04_2008_c1
Connectivity tests to IP devices Connectivity tests to network services (DHCP, DNS, http)
*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
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
Cisco Public
86
43
BRKNMS-1204 14528_04_2008_c1
Cisco Public
87
Scheduling Caveat
If 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 <n> start-time after 00:01:00 ip sla monitor schedule <n+1> start-time after 00:01:01 ip sla monitor schedule <n+2> start-time after 00:01:02
BRKNMS-1204 14528_04_2008_c1
Cisco Public
88
44
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
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
Router(config)#ip sla monitor reaction-configuration <n> ? 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 <entry-number> <target-number>
BRKNMS-1204 14528_04_2008_c1
Cisco Public
91
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
Cisco Public
92
46
BRKNMS-1204 14528_04_2008_c1
Cisco Public
93
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 Marking
Probes 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
TOS (RFC795)
P2
P1
P0
T3
T2
ToS
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
DSCP 40 44 14
Precedence 5 5 1
96
48
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
97
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
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
Memory Limit
BRKNMS-1204 14528_04_2008_c1 2008 Cisco Systems, Inc. All rights reserved. Cisco Public
98
49
Operational State
Show the Actual State of an Operation: Old command
show rtr operational-state operation-number
New command
show ip sla monitor statistics operation-number [details]
BRKNMS-1204 14528_04_2008_c1
Cisco Public
99
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 Operations
To delete one operation <n>:
router(config)# no ip sla monitor <n>
BRKNMS-1204 14528_04_2008_c1
Cisco Public
101
BRKNMS-1204 14528_04_2008_c1
Cisco Public
102
51
BRKNMS-1204 14528_04_2008_c1
Cisco Public
103
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
Agenda
SLA Concept Network Disturbance Active Measurement Overview Architecture Configuration Options Monitoring and Debugging Use Cases and Scenarios
BRKNMS-1204 14528_04_2008_c1
Cisco Public
105
PoP1
PoP3
PoP4
PE
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
PoP2
PoP1
PoP3
PoP4
BRKNMS-1204 14528_04_2008_c1
Cisco Public
107
PoP2
PoP1
PoP3
PoP4
Cisco Public
108
54
PoP2
NOC
PoP3 PoP1
CE
PoP4
Best practice suggests using 1 site to poll the others to increase manageability when network design changes are required
BRKNMS-1204 14528_04_2008_c1
Cisco Public
109
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
CE
PE
PE
CE
ISP
CPE
CPE
BRKNMS-1204 14528_04_2008_c1
Cisco Public
111
HomeOffi ce
Retail Branch
Small Office
BRKNMS-1204 14528_04_2008_c1
Cisco Public
112
56
DNS
DHCP
Web
BRKNMS-1204 14528_04_2008_c1
Cisco Public
113
References
Cisco 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
BRKNMS-1204 14528_04_2008_c1
Cisco Public
115
A Complementary Solution
NetFlow
From where? To Who? When? How Much? Which Apps? What ToS?
IP SLA
Latency Loss Jitter Server Delay (HTTP, DNS, TCP Connect)
BRKNMS-1204 14528_04_2008_c1
Cisco Public
116
58
Summary
SLA 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
Conclusion
IP 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 Reading
Continue 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:
120
60
BRKNMS-1204 14528_04_2008_c1
Cisco Public
121
BRKNMS-1204 14528_04_2008_c1
Cisco Public
122
61