BRKNMS 3043 PDF

Advanced Performance
Measurement for IP
and SDN Traffic with
Cisco IOS IP Service
Level Agreements
Michael Geller – Principal Engineer
BRKNMS-3043
Cisco Spark
Questions?
Use Cisco Spark to chat with the
speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
Cisco Spark spaces will be cs.co/ciscolivebot#BRKNMS-3043

available until July 3, 2017.
BRKNMS-3043 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
• Introduction
• Killer Apps For IPSLA
• IPSLA Accuracy
• Performance & Scalability
• Cool IPSLA Features & Probes
• Conclusion
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Rules of the Game!
• Silence your phone, pda, pager, mp3 player… Ok, who has the best ring?
• At CiscoLive! your evaluation is extremely important
• Please remember to wear your badge at all times
• Please visit the World of Solutions
• PLEASE! Ask questions any time
Meet the Engineer
• To make the most of your time at Networkers at Cisco Live 2016, schedule a
Face-to-Face Meeting with top Cisco Engineers.
• Designed to provide a "big picture" perspective as well as "in-depth" technology

discussions, these face-to-face meetings will provide fascinating dialogue and a
wealth of valuable insights and ideas.
• Visit the Meeting Center reception desk located in the Meeting Centre in World
of Solutions.
Prerequisites
• Before attending this session, familiarities with
Cisco IOS® IP Service Level Agreements (IP SLAs)
is essential
• Configuration and generic features will not be covered
• Only new or advanced topics, as well as design recommendations will be
covered
• Some familiarity with Virtualization, SDN and NfV
Objectives
• This session targets network performance measurement only
• Understand the internals
• Cool IPSLA Features and New Probes (Cloud & SDN)
• Performance and scalability considerations
• How to get the most of IP SLAs
• Future and IP SLAs strategic vision
This Is Not
• An introduction to IP SLAs
• Recommendations on QoS configuration
• A talk on backend network management applications
• A speculation on upcoming features
• A marketing document
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
A Quick Review
• IP SLAs in an active probing and monitoring
feature in Cisco IOS
• Wide protocol and applications coverage:
UDP, TCP, ICMP, HTTP, DNS, DHCP, FTP
• Microsecond granularity
• Use it through SNMP or CLI
• Already in Cisco IOS® (available on
most platforms and interfaces type)
IP SLA Overview
IP SLA Capability Overview
Domain
TCP/IP VoIP Network MPLS Video Cloud & Metro-Ethernet

Service DC
UDP Jitter UDP Jitter (+VoIP g711, HTTP LSP Ping Video Cloud Ethernet Echo (802.1ag)
g729) Operation on Service Level
UDP Echo DNS LSP Trace Ethernet Jitter
3K Monitor
VoIP RTP (DSP
UDP Path Echo DHCP LSP Auto- Ethernet MEP VLAN
required) IPSLA
Discovery and Auto-Discovery and Auto-
TCP Connect FTP queries VSM
VoIP H.323 and SIP Call Auto-Schedule Scheduling
for VEMs it
ICMP Echo Setup Delay
(ECMP Tree manages Y.1731 on 7600
ICMP Path Echo VoIP H.323 and SIP Trace)
Gatekeeper Delay
ICMP Jitter VCCV PWE3 Echo
Core Value Features

Flexible Operation Schedule SNMP and CLI Set and Get Support
RT Threshold Alerts + Automatic Reaction Probes Hourly Aggregate Statistics History (Up to 24hrs)
QoS Integration (with Engine 3) Cisco IOS, IOS-XR, and Linux Operating System Support
Auto IP SLA with Endpoint Auto Discovery and Registration
Typical SLA Requirements
Maximum Packet Maximum
Traffic Type Max. Jitter
Loss One-Way Latency
VoIP 1% 120 ms 30 ms
(land line quality)
Video-conferencing 1% 200 ms 50 ms
Streaming video N/A

2% 5s (assuming the receive buffer is
(one way video) large enough)
IP SLA Operations with IPv6 & VRF Support
• dns
• ftp
• http
• icmp-echo
• path-echo
• path-jitter
• tcp-connect
• udp-echo
• udp-jitter
Now On To The Good Stuff!!
Killer Apps For IPSLA

Killer Apps For IPSLA
• PFR – Performance Routing and Applications
• “Best” Path Selection from a Firewall to ISP
• Using IPSLA Delay Feature To Safely Monitor Lossy Links
• Using IPSLA For DDoS Visibility & Mitigation
• IPSLA “On Steroids” With SDN
• Shadow Routers for IPSLA
PerFormance Routing – Application
Based Decision Making
PerFormance Routing
• http://docwiki.cisco.com/wiki/PfR:Technology_Overview
• It’s all about path selection based on application forensics
• Classify Traffic at the “edge”
• MQC  Set classes, policy and policers
• Set up IPSLA to baseline then monitor application traffic over diverse paths
• Based on SLA’s, make a routing decision – may be different than traditional
• Better use of WAN links
• ISP Selection
PerFormance Routing – Lifecycle
IPSLA Application to App Visibility & Control
Monitoring App Visibility &
ISR G2 Performance ISR G2
User Experience Report
App BW Transaction …
ASR1K Time ASR1K
ISR G2 ASR1K WebEx 3 Mb 150 ms …
High
Citrix 10 Mb 500 ms …
NFv9 Med
Low
IPFIX
Reporting Tools
Reporting Tool
NBAR2 identifies Advanced Use QoS or PfR to
ISR G2 & ASR control application
applications using reporting tool
collect application network usage to
L3 to L7 aggregates and
bandwidth and improve
information reports application
response time application
performance
metrics, and export performance
to management tool
Application Perf. Collection &
Reporting Tool Control & OPT
Recognition Exporting
PerFormance Routing
PerFormance Routing
PerFormance Routing – Target Discovery With
IPSLA
PerFormance Routing – Target Discovery With
IPSLA
PerFormance Routing – Measuring Performance
Best Path Selection – Enterprise
Firewall to ISP
Dual ISP Path Selection With IPSLA
• http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-
generation-firewalls/118962-configure-asa-00.html
Dual ISP Path Selection With IPSLA – Method-1
Dual ISP Path Selection With IPSLA – Validate-1
Using IPSLA Delay Feature To
Safely Monitor “Lossy” Links
Using IPSLA Delay Feature To Safely Monitor
“Lossy” Links
• http://packetpushers.net/using-ip-sla-delay-feature-to-safely-monitor-lossy-links/
Using IPSLA Delay Feature To Safely Monitor
“Lossy” Links
track 1 ip sla 1 reachability
..delay down 90 up 90
track 2 ip sla 2 reachability
..delay down 90 up 90
track 3 list boolean or
..object 1
..object 2
!
ip sla 1
..icmp-echo 155.1.23.2 source-interface Serial0/3/0
..timeout 1000
..threshold 1000
..frequency 30
ip sla schedule 1 life forever start-time now
!
ip sla 2
..icmp-echo 155.1.13.1 source-interface Serial0/2/0:0
..timeout 1000
..threshold 1000
..frequency 30
! You can use tracked object 3 with a static route or EEM script to affect the actual failover event.
IPSLA For DDoS Visibility &
Mitigation
Piecing The Puzzle Together for DDoS
Control Applications
DefenseFlow Automation
Cyber Defense Controller WAE
Control App
Netflow, OSC
Telemetry, NAPI ACI APIs
Analytics
NSO Cisco Open Network OSC BGP-LS Radware

Device
Control Layer Packages
vMS Segment OpenFlow /NetConf

OPFLEX
DDoS Routing Nexus APIs
Perimeter
ASR9K
/Nexus/Mobile
ACI
Leaf
DefensePro ++
Cloud burst ISR SP/Enterprise FirePower

Scrubbing Scrubbing 9300
45
IPSLA on “Steroids” With SDN
IPSLA On “Steroids” With SDN – ThousandEyes-1
• http://blog.ipspace.net/2013/11/use-thousandeyes-to-implement-ip-sla-on.html
IPSLA On “Steroids” With SDN – ThousandEyes-2
• http://blog.ipspace.net/2013/11/use-thousandeyes-to-implement-ip-sla-on.html
Shadow Routers For IPSLA
Why Use a Shadow Router?
• A shadow router is a dedicated box for IP SLAs.
But why?
• If your Provider Edge (PE) router is already overloaded (> 60%
CPU at interrupt level)
• If your PE lacks memory
• If your PE is a distributed platform
• If you want to separate measurement from forwarding
• Upgrade freely for the latest and greatest IP SLA features without
disturbing the traffic, then…
• Use a shadow router (router dedicated to IPSLA)
Shadow Router Configuration
Point-of-Presence
• A shadow router is typically a
dedicated router located near a Shadow
ideal measurement point. PE
• A point-of-presence (POP) is an
ideal location.
• It can be connected to the PE via
various methods: direct IP
connection, tunnels, dot1q
CE
How to Probe?
• Full mesh
• Full mesh between same-customer CPEs
• Partial mesh
• Composite SLAs
Full Mesh
Nodes Operation
2 1
3 3
4 6
5 10
6 15
n2 7
8
21
28
… …
100 4950
 Number of operations is
proportional to the square
of the number of nodes
 Does not scale
Full Mesh CE-to-CE [Example]
CE CE
PE Core PE
PE
Accurate: direct measurement from end-to-end, best

CE user-perspective view
Expensive: for n nodes, requires n(n-1)/2 operations
In certain cases, it might be difficult to poll the results
with SNMP on the CE
Partial Mesh
• Full mesh is not always
London desirable, while partial mesh
dramatically reduces the
Amsterdam San Jose number of operations.
• Measurement points can be
based on traffic matrix,
traffic importance
Raleigh Paris
• For instance, try a coverage
objective for 80% of the
traffic
• To build a traffic matrix, use
NetFlow.
Brussels
Composite SLA for Delay [Example]
CE CE
PE Core
PE
PE
Easy: Total delay can be easily calculated by adding the measured
delay along the path
Flexible: You can split the measurement for Core
CE Edge, and total
Measurements are less accurate, as each measurement carry
its own error tolerance (typically ± 1 ms per measurement)
NSO and Orchestration of IPSLA
IPSLA Triggers vMS Events
Management Network Multi-vendor service orchestrator
Applications Engineer for existing and future networks
REST, Java, NETCONF Network-wide CLI, Web UI

Single pane of glass for:
 L2-L7 networking
Tail-f Network Control System Service  Hardware Devices
Models  Virtual Appliances
Service Manager
 OpenFlow Switches
Device Manager
Tail-F Network Control System
Device
Network Element Drivers Models
provides abstractions
based on
 Data models
NETCONF, CLI, SNMP, REST, etc.  Transactions
End-to-End
Transactions Sold to service providers
• Applications Perpetual license
• Controllers
Voice & Jitter With IPSLA
UDP Jitter Operation
• Measures the delay, delay variation (jitter), corruption, misordering
and packet loss by generating periodic UDP traffic
• One-way results for jitter and packet-loss. If clocks are synchronized
and IOS is at least 12.2(T), one-way delay is also measured.
• Detect and report out-of-sequence and
corrupted packets
• Since 12.3(4)T—also with MOS and ICPIF score for voice clarity
estimation.
• This operation always requires IPSLA responder
UDP Jitter—Measurement Example
Send Packets STx = sent tstamp Receive packets
i1 for packet x. i2
P2 P1 P2 P1
ST2 ST1 RT2 RT1
IPSLA
IP Core Responder
RTx = receive
tstamp for packet x.
Reflected packets Reply to packets
dx = processing time
i4 i3 spent between
P1 P2 P1 P2 packet arrival and
AT1 AT2 RT1+d1 RT2+d2 treatment.
ATx = receive
Each packet contains STx, RTx, ATx, dx and the source can now calculate:
tstamp for packet x.
JitterSD = (RT2-RT1)-(ST2-ST1) = i2-i1
JitterDS = (AT2-AT1)-((RT2+d2)-(RT1+d1)) = i4-i3
Jitter Calculation—Beware!
t=0 t=20 t=40
i1=20 ms i1=20 ms
p1 p2 p3
lat = 50 ms
send
lat = 55 ms
lat = 50 ms
t=25
i2=25 ms i2=15 ms
receive p1 p2 p3
IPSLA Jitter i2-i1 = +5 ms i2-i1 = -5 ms

RTP Stream Jitter Packet too late: 5 ms Packet on-time: 0 ms
If you count positive and negative jitter, you are penalized twice.
Counting only positive jitter is enough.
UDP 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)
• Packets are sent every 20 milliseconds
• Marked with DSCP value of 8 (TOS equivalent 0x20)
ip sla 1
udp-jitter 10.52.130.68 16384 \
num-packets 1000 interval 20
tos 0x20
frequency 60
request-data-size 172
B C
A A = 20 ms
B = 20 s (1000 x 20 ms)
C = 40 s (60 s – 20 s)
UDP Jitter Example (New CLI)
Differences Between CLIs:
rtr 1
type jitter dest-ipaddr 10.52.130.68 dest-port 16384 \
tos 20
frequency 60
rtr schedule 1 life forever start-time now
ip sla monitor 1
type jitter dest-ipaddr 10.52.130.68 dest-port 16384 \
tos 20
frequency 60
ip sla monitor schedule 1 start-time now
ip sla 1
udp-jitter 10.52.130.68 16384 \
tos 20
frequency 60
UDP Jitter with VoIP MOS Score
• Introduced in Cisco IOS 12.3(4)T—“Advanced” feature set
• Modified jitter operation reports both Mean Opinion Score (MOS) and
Calculated Planning Impairment Factor (ICPIF)
• Those results are estimates and should be used for comparison only and
should not be interpreted as reflecting actual customer opinions
• Supported Codecs:
• G.711 A Law (g711alaw: 64 kbps PCM compression method)
• G.711 mu Law (g711ulaw: 64 kbps PCM compression method)
• G.729A (g729a: 8 kbps CS-ACELP compression method)
• Note: this is not a real RTP voice stream, but it has the same
characteristics. For real RTP stream generation, check IP SLAs’ “VoIP
RTP” operation.
VoIP Operation: Sample Configuration
• Operation parameters autoconfigured to simulate a G729a codec
• 1000 packets, interval 20 ms (default values)
• Operation frequency will be randomized between
40 and 60 seconds
ip sla 30
udp-jitter 192.1.3.2 16001 codec g729a
ip sla group schedule 30 30-31 schedule-period 1
frequency range 40-60 start-time now life forever
Summary
• IP SLAs is a Cisco IOS Feature
• Active monitoring with synthetic operations—
sending additional traffic in the network.
• Detailed results like availability, delay, loss,
and jitter per direction and MOS score.
• Easy to use, available on many platforms.
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
IPSLA Accuracy—ICMP Echo Probe
ICMP Echo Probe
Sender Responder
(90% Process Load)

 With unloaded receiver, IPSLA measures 15.0 ms
 With high CPU load on the receiver: 58.5 ms!!
Any System Will Report Wrong Results when Excessive CPU Time Is Spent on the Receiver
Between the ICMP Echo Request and Echo Reply
Fortunately, We Have a Solution…
Processing Time Measurement
• When running the responder, we have a clear advantage, because
• A mechanism to measure the processing time spent on the receiving
router is in place, inserting a timestamp when the responder receives and
send the packet
• Receive timestamp done at interrupt level, as soon as the packet is
dequeued from the interface driver; with absolute priority over everything
else
• With IPSLA, this mechanism is implemented for both UDP Echo
and UDP Jitter operations
UDP Echo Operation (with IPSLA Responder)
T1 T2
T5 T3
Sender
T4 Responder
Processing Delay on the Source: Tps = T5-T4

Processing Delay on the Destination: Tpd = T3-T2
Round Trip Time Delay: T = […] = T2 - T1 + T4 - T3
• We have no control of queuing delay on the source

and destination, but this is experienced by real traffic too, and must be
accounted as such
IPSLA Accuracy: UDP Echo Probe
UDP Echo Probe
Sender Responder
(90% Process Load)

 With unloaded receiver: 15.0 ms
 With 90% CPU receiver: 15.3 ms
The IPSLA Responder Processing Delay Will Be
Subtracted from the Final Results
Summary
• IP SLAs uses a special time stamping mechanism at interrupt
level and its accuracy preserved even under high CPU load
• The absolute tested accuracy is  1 ms. In other words, when it
says 35 ms, it could be somewhere between
34 ms and 36 ms.
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
Cisco IOS IP SLAs Performance:
CPU Load by Platform
(Jitter Probe Running Eng 2+—2000 Active Jitter Oper —Cisco IOS 12.4(PI3)T)
Oper/ Pkts/ Oper/
2800 2811 2851 2691 3745 3845 3825 1841
Second second Minute
4 200 240 3 3 1 2 1 0 2 3
8 400 480 6 5 2 3 1 1 3 4
12 600 720 8 7 3 4 2 2 5 6
16 800 960 10 9 4 5 2 2 7 8
20 1000 1200 13 11 4 6 3 3 8 10
24 1200 1440 15 13 5 8 4 4 10 11
28 1400 1680 18 14 6 9 4 4 12 13
32 1600 1920 20 16 7 10 5 5 14 15
36 1800 2160 23 18 8 11 5 6 16 17
40 2000 2400 24 20 9 12 6 6 17 18
44 2200 2640 27 21 10 14 7 7 19 20
48 2400 2880 29 21 11 15 7 8 21 22
52 2600 3120 32 22 12 16 8 8 23 23
56 2800 3360 34 22 13 17 9 9 26 24
60 3000 3600 36 23 14 18 9 9 27 26
Cisco IP SLAs Performance: UDP-Jitter
UDP-Jitter Probe Running Engine 3—Cisco IOS 15.1(4)M
Default Parameters: Frequency (60secs), Request Size (32bytes), Packet Interval (20ms), Number of Packets (10)
1921 2921 3925 3945 3945E
Operations (Total) 1000 2000 3000 4000 5000
Operations/Second 16.7 33.3 50 66.7 83.3
Packets Per Second 166.7 333.3 500.0 667.0 833.3
Operations/Min 1000 2000 3000 4000 5000
CPU Usage ~6% ~8% ~8% ~8% ~1%
Each configuration being different, use those numbers with care: they are only an indication.
No SNMP polling were performed to gather the operation results
IP SLA Performance: UDP-Jitter for VoIP
UDP-Jitter Probe for VoIP (G.729a) running Engine 3: Cisco IOS 15.1(4)M
Default Parameters: Frequency (60secs), Codec Packet Size (32bytes), Codec Interval (20ms), Codec Number
of Packets (1000)
1921 2921 3925 3945 3945E
Operations (Total) 150 225 275 400 900
Operations/Second 2.5 3.75 4.58 6.7 15.0
Packets Per Second 2500.0 3750.0 4583.3 6733.3 15000.0
Operations/Min 150 225 275 400 900
CPU Usage ~59% ~61% ~43% ~54% ~43%
Each configuration being different, use those numbers with care: they are only an indication.
No SNMP polling were performed to gather the operation results
Summary
• Under normal conditions and with reasonable targets,
a performance issue with IP SLAs is unlikely
• Memory usage is reasonable, and should never be a problem
on any platform.
• Compared to Engine 1, both performance and memory usage
have been improved on IPSLA Engine 2 and 2+
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
Template-Based Configuration
• ip sla auto-measure group wacho
destination ip-address alist-1 port 16000
type jitter
schedule id wa-sched
• ip sla list ip-address alist-1
ip-addresses 1.1.1.1, 2.2.2.2, 3.3.3.3
ip-addresses 10.1.1.1-100
ip-addresses exclude 10.1.1.5, 10.1.1.8
• ip sla auto-measure schedule wa-sched
start-time now
QoS Integration (example)
Observation: Need to send the same operation in each class.
Problem: Provision the same operation multiple times is lengthy, error prone, and counter productive.
Solution: Discover the QoS classes on the outgoing interface and automatically instantiate probes.
class-map voice-traffic
match dscp EF QoS Class definition
class-map data-traffic
match dscp AFnn
policy auto-measure
class voice-traffic How to
measure type ip-sla group voice-traffic-probes-grp
class data-traffic measure
measure type ip-sla group udp-jitter-probes-grp in each class?
End-Point Auto Registration
ip sla auto group test Hub to Spoke-1

measure type udp-jitter ip sla 34567
udp-jitter 10.10.10.2 5000
destination auto-discover dest-port 5000 Hub to Spoke-2
schedule now ip sla 87422
Hub udp-jitter 20.20.20.2 5000
Hub to Spoke-3
ip sla 363435
172.17.0.5 udp-jitter 30.30.30.2 5000
spoke-3
30.30.30.2 ip sla responder auto-register 172.17.0.5

10.10.10.2
20.20.20.2
spoke -1
spoke-2 ip sla responder auto-register 172.17.0.5
ip sla responder auto-register 172.17.0.5
Video Monitoring Features
Feature Purpose Mechanism Monitor User Interface Note
Passive Monitor a node • Clone & truncate pkt Loss, delay, • Config via CLI, • Real and synthetic traffic
Mon. • Punt to cpu to jitter SNMP • Statically applied policy
process
• Report via CLI,
SNMP, Netflow
Media • Monitor end-to-end RSVP. PM collects Loss, delay, CLI • Real and synthetic traffic
Trace condition stat on each node jitter •dynamically applied policy
on demand
• Control resources
IPSLA Generate synthetic video • Leverage existing Loss, one way CLI
traffic for pre- deployment IPSLA for media traffic delay, jitter
assessment • Need platform
assistance
destination destination
source source
Passive Monitoring Media Trace IPSLA

Video Per-Application Targets
General Guidelines
Application Latency Jitter Loss (VoD) Loss (Live)
Streaming Video < 1000ms < 100 ms < 0.1% < 0.05%
Video Conferencing < 150 ms <30 ms NA < 0.10%
TelePresence < 150 ms < 10 ms NA < 0.05%
Digital Signage < 1000 ms < 100 ms < 0.1% 0%
IPTV < 1000 ms < 100 ms < 0.1% 0%
Video Surveillance < 1000 ms < 100 ms < 0.1% < 0.05%
Cisco TelePresence Traffic Characteristics
IPSLA Video Operation
• Convenient for pre-deployment assessment, pre-event testing
and post-event troubleshooting.
Is my network ready for • More bandwidth needed? Deploy PfR?
100 HD Desktop
Cameras, 30 IPVSC • QoS needed?
and a new
Telepresence room? • Fully integrated with IPSLA control and scheduling framework
• Extension to current IPSLA CLI and MIB interface to allow easy
integration with NMS products
Switch D
Router C Router B
Switch A
IPSLA Video Operation
Embedded Traffic Simulator
 IPSLA known in industry for jitter, ICMP, etc. probes
 Most probes measure experience without affecting user
traffic (hopefully)
 Need traffic to stress test network
 IPSLA VO provides
 Realistic representation of arbitrary video (RTP)
traffic
 Packet sizes, burstiness, traffic rate, etc.
 pre-packaged profiles:
 IPTV, Video Surv, CTS
X
 Extensible via data file
 Custom profile generation from packet capture
X BRKNMS-3043 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 87
Pre-Deployment Planning
 Objective
Enable clientless deployment and capacity planning
- How many streams at bandwidth x at this time of day can we expect to support
- What delay/loss impact does the addition of an extra stream at bandwidth X
 Solution Value
Clientless pre-deployment and provisioning for network readiness assessment and traffic
modeling
Remote Site
Operations System
(OSS) or
Application
Video Configuration: Video Op. cont.
router(config)#
ipsladev3750e-3(config-ip-sla)#video ?
Hostname or A.B.C.D Destination IP address or hostname
ipsladev3750e-3(config-ip-sla)#video 192.168.1.4 ?
<1-65535> Port Number
ipsladev3750e-3(config-ip-sla)#video 192.168.1.4 4336 ?

source-ip Source address
ipsladev3750e-3(config-ip-sla)#video 192.168.1.4 4336 source-ip

192.168.1.3 ?
source-port Source Port
Video Configuration: Video Op. cont.
router(config)#
ipsladev3750e-3(config-ip-sla)#$6 source-ip 192.168.1.3

source-port 3228 ?
profile traffic profile type to be configured
ipsladev3750e-3(config-ip-sla)#$p 192.168.1.3 source-

port 3228 profile ?
IPTV IP Television traffic (2.6 Mbps)
IPVSC IP video surveillance camera traffic (2.2
Mbps)
TELEPRESENCE Cisco Telepresence 1080P traffic
(6.6Mbps)
ipsladev3750e-3(config-ip-sla)#$p 192.168.1.3 source-

port 3228 profile IPVSC
IP SLA Video Show Configuration
ipsladev3750e-3#show ip sla configuration 111
IP IP SLAs Infrastructure Engine-III
Entry number: 111
Owner:
Tag:
Operation timeout (milliseconds): 5000
Type of operation to perform: video
Video profile name: IPVSC
Video duration (seconds): 20
DSCP: cs5
Target address/Source address: 192.168.1.4/192.168.1.3
Target port/Source port: 4336/3228
Vrf Name:
Control Packets: enabled
Schedule:
Operation frequency (seconds): 900 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
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:
IP SLA Video Show Statistics
ipsladev3750e-1#show ip sla statistics 1
IPSLAs Latest Operation Statistics
IPSLA operation id: 1

Type of operation: video
Latest operation start time: 10:50:53 PST Fri Feb 25 2011
Latest operation return code: OK
Packets:
Sender Transmitted: 2034
Responder Received: 1994
Latency one-way time:
Number of Latency one-way Samples: 1894
Source to Destination Latency one way Min/Avg/Max: 0/29/31 milliseconds
NTP sync state: SYNC
Inter Packet Delay Variation, RFC 5481 (IPDV):
Number of SD IPDV Samples: 1847
Source to Destination IPDV Min/Avg/Max: 0/1/3 milliseconds
Packet Loss Values:
Loss Source to Destination: 60
Out Of Sequence: 33
Number of successes: 1
Number of failures: 0
Operation time to live: 3578 sec
ISR: IPSLA-VO Emulates Endpoint Traffic
ISR-G2#show ip sla config [x]
The ISR-G2 supports this
Input-interface: GigabitEthernet1/0 interface emulation.
Emulate source address: x

Emulate source port: a
Emulated IP SLA VO IP SLA VO
Endpoint Sender Responder
no packets synthetic packets
packet
termination
IP address: x packet IP address: y

UDP port: a generation UDP port: b
Source IP address: x
Destination IP address: y
Source UDP port: a
Destination UDP port: b
Pre-Packaged and Custom Profiles
Support for
Platform Pre-Packaged Profile
Custom Profiles
Telepresence
Cisco Catalyst 3k IPTV Yes
IPVSC
Telepresence
Cisco Catalyst 4k IPTV No
IPVSC
CP-9900-CIF-15-384kbps CTS-1080P-Best
CP-9900-CIF-30-1000kbps CTS-1080P-Better
CP-9900-QCIF-10-79kbps CTS-1080P-Good
Cisco ISR-G2 CP-9900-QCIF-15-99kbps CTS-720P-Best Yes
CP-9900-QCIF-30-249kbps CTS-720P-Better
CP-9900-VGA-15-1000kbps CTS-720P-Good
CP-9900-VGA-30-1000kbps CTS-720P-Lite
Generating IPVSC Traffic Using ISR
(1) Custom IPVSC profile parameters;
ip sla profile video IPVSC
endpoint custom
description Cisco 4000 HD Camera
resolution 1080P
frame rate 30
bitrate maximum 4000
bitrate window-size 167
frame intra size maximum 100
frame intra refresh interval 1
rtp size average 1300
rtp buffer output shaped
content single-person
(2) Traffic characteristics

BW ≈ 3.2Mbps
Debugging Commands & Steps
Available DEBUG commands:
Sender debug
ipsladev3750e-3#debug ip sla trace
ipsladev3750e-3#debug ip sla error
• This will show both IP SLA debug and platform debug.

• Basic familiarity with IP SLA debug is expected
Responder Debug
ipsladev3750e-3#debug ip sla trace 0
ipsladev3750e-3#debug ip slaerror 0
IP SLAs—MPLS Health Monitor
• Automatically create and delete IP SLAs LSP ping or LSP traceroute
operations based on network topology
• Works on the MPLS L3 layer, under the IP layer. Discovers MPLS
issues even when IP routing is working ok.
• Dramatically reduces troubleshooting time, and cost associated to
maintenance of MPLS networks.
• Other PEs are discovered using BGP next-hop, and operations
configured accordingly.
• Requires 12.2(27)SBC and later.
• New capability for Metro Ethernet on 7600: Y.1731
Cisco IP SLAs
Performance Management Extensions (Y.1731 …)
• Cisco IP SLAs Embedded Policy Management

•Scheduling Automation / Policy Alerts / Data Collection
• In-band Performance Management Tool for Ethernet
•Delay, Delay Variation and Packet Loss measurement
•Built in CFM principles
• Automatic Discovery of Probe Endpoints
•Using entries on CFM CCM database
Agenda
• Introduction
• IPSLA Accuracy
• Conclusion
References
• Cisco IOS IPSLA home page
• http://www.cisco.com/go/ipsla
• For questions related to Cisco IP SLAs that cannot be handled by the Technical
Assistance Center (TAC),
feel free to write an email to:
• [email protected]
Summary and Conclusion
• IPSLA is a Cisco IOS feature available today to actively measure
and report many network metrics.
• It is easy to use, and is supported by many existing network
management applications.
• We also have MPLS OAM, Gatekeeper Registration, H323/SIP Call
Setup operation, and many other new features.
• Stay tuned. We have an ambitious roadmap for new features like
better voice measurements, multicast, Ethernet OAM and we’re
always listening your suggestions!
Complete Your Online
Session Evaluation
• Give us your feedback to be
entered into a Daily Survey
Drawing. A daily winner will
receive a $750 gift card.
• Complete your session surveys
through the Cisco Live mobile
app or on www.CiscoLive.com/us.
Don’t forget: Cisco Live sessions will be

available for viewing on demand after the
event at www.CiscoLive.com/Online.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Lunch & Learn
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you

BRKNMS 3043 PDF

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

BRKNMS 3043 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRKNMS 3043 PDF

Uploaded by

Copyright:

Available Formats

Advanced Performance

Cisco Spark spaces will be cs.co/ciscolivebot#BRKNMS-3043

• PLEASE! Ask questions any time

• Designed to provide a "big picture" perspective as well as "in-depth" technology

TCP/IP VoIP Network MPLS Video Cloud & Metro-Ethernet

Core Value Features

Streaming video N/A

Killer Apps For IPSLA

NSO Cisco Open Network OSC BGP-LS Radware

vMS Segment OpenFlow /NetConf

Cloud burst ISR SP/Enterprise FirePower

Accurate: direct measurement from end-to-end, best

REST, Java, NETCONF Network-wide CLI, Web UI

IPSLA Jitter i2-i1 = +5 ms i2-i1 = -5 ms

(90% Process Load)

 With high CPU load on the receiver: 58.5 ms!!

Processing Delay on the Source: Tps = T5-T4

• We have no control of queuing delay on the source

UDP Echo Probe

(90% Process Load)

1921 2921 3925 3945 3945E

Operations (Total) 1000 2000 3000 4000 5000

Operations/Second 16.7 33.3 50 66.7 83.3

Packets Per Second 166.7 333.3 500.0 667.0 833.3

Operations/Min 1000 2000 3000 4000 5000

CPU Usage ~6% ~8% ~8% ~8% ~1%

1921 2921 3925 3945 3945E

Operations (Total) 150 225 275 400 900

Operations/Second 2.5 3.75 4.58 6.7 15.0

Packets Per Second 2500.0 3750.0 4583.3 6733.3 15000.0

Operations/Min 150 225 275 400 900

CPU Usage ~59% ~61% ~43% ~54% ~43%

ip sla auto group test Hub to Spoke-1

30.30.30.2 ip sla responder auto-register 172.17.0.5

Passive Monitoring Media Trace IPSLA

Application Latency Jitter Loss (VoD) Loss (Live)

Video Conferencing < 150 ms <30 ms NA < 0.10%

TelePresence < 150 ms < 10 ms NA < 0.05%

Digital Signage < 1000 ms < 100 ms < 0.1% 0%

IPTV < 1000 ms < 100 ms < 0.1% 0%

ipsladev3750e-3(config-ip-sla)#video 192.168.1.4 4336 ?

ipsladev3750e-3(config-ip-sla)#video 192.168.1.4 4336 source-ip

ipsladev3750e-3(config-ip-sla)#$6 source-ip 192.168.1.3

ipsladev3750e-3(config-ip-sla)#$p 192.168.1.3 source-

ipsladev3750e-3(config-ip-sla)#$p 192.168.1.3 source-

IPSLA operation id: 1

Emulate source address: x

IP address: x packet IP address: y

(2) Traffic characteristics

• This will show both IP SLA debug and platform debug.

• Cisco IP SLAs Embedded Policy Management

Don’t forget: Cisco Live sessions will be

You might also like