JDSU TrueSpeed Automated RFC-6349 TCP Testing

TrueSpeedTM
Automated RFC 6349 TCP Testing
Guylain Barlow,
Senior Product Line Manager
Agenda
Who should test TCP?
Why Test TCP?
What is RFC 6349?
TCP Performance Issues and the TrueSpeed Solution
2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 2

TCP Testing Applications
Customer Site Ethernet Provider Customer Aggregation
T-BERD/MTS 5800 T-BERD/MTS 8000
T-BERD
Backhaul
Network
T-BERD/MTS 8000
T-BERD/MTS 6000 T-BERD/MTS 6000
1. Service providers offering Ethernet Business services
2. Service providers offering Ethernet Backhaul services
3. Mobility service providers deploying 3G or 4G/LTE

Why is TCP Testing Important?
Running RFC2544, Y.1564 or other Layer 2/3 installation tests

is always the first step
But even when these Layer 2/3 tests pass, end-customers

can still complain that the network is slow and the cause of
poor application performance (i.e. FTP, web browsing, etc.)
Lack of TCP testing is a turn-up gap because end-customer

applications are transported using TCP in Layer 4
Save up to 30% OPEX costs by eliminating or quickly

resolving painful end-customer finger pointing scenarios

Which Applications use TCP?
HTTP, FTP, E-mail, Sharepoint,

7 on Communicator, Facebook, YouTube, etc
Applicati
6 tion
Presenta
5
Session
TCP RFC 6349 TrueSpeedTM

4 t
Transpor
3 IP Y.1564 SAMComplete
Network
2 &
Datalink RFC 2544
Ethernet
1
Physical

Case Study: Customer Issue
100 Mbps Service

~20 msec RTT
Layer 2 traffic testing was done twice, Test results = Pass

End-customer performance dipped to 50-60 Mbps at various times of the day (end-customer
running iperf based speed tests)
TrueSpeedTM test was run from network provider demarc in Tampa to Atlanta
TCP throughput was rock solid at nearly 100 Mbps (95 Mbps layer 4) NO DROPs
Finger was clearly pointed at customer data center network; investigation proceeded in the customer
arena (provider was cleared of guilt) larger TCP window was required

Case Study: Network Provider Issue
300 Mbps Service

~75 msec RTT
Layer 2 traffic testing was done twice, Test results = Pass

End-customer file transfer performance was low (150 Mbits/sec)
TrueSpeedTM (30-40 TCP sessions with 64 KB window) stressed network buffers
Problem was reproduced with bursty traffic (traffic drop)
Network provider isolated to mis-configured device at California site needed larger egress buffers

Brief Overview of RFC 6349
8
RFC 6349: TCP Throughput Test Methodology
IETF RFC 6349 specifies the methodology for measuring end-to-end

TCP Throughput in a managed IP network.
JDSU and two (2) Network Providers co-authored this RFC
0. Run traditional RFC2544 to verify the integrity of the network at Layers

2 and 3 before conducting TCP testing.
1. Path MTU Detection (per RFC4821)

Verify network MTU with active TCP segment size testing to ensure
TCP payload does not get fragmented
2. Baseline Round-Trip Time and Bandwidth

Predict optimum TCP window size to automatically calculate the
TCP Bandwidth Delay Product (BDP)
3. Single and Multiple TCP Connection Throughput Tests

Verify TCP window size predictions to enable automated full pipe
TCP testing

RFC 6349 Metrics: TCP Efficiency
TCP retransmissions are a normal behavior in network communications.
But what is the efficiency of a network transfer?
Time spent transmitting good payload versus retransmitting it.
The TCP Efficiency metric is the percentage of Bytes that did not have
to be retransmitted and is defined as:
TCP efficiency= Transmitted Bytes - Retransmitted Bytes x 100

Transmitted Bytes
As an example, if 100,000 Bytes were sent and 1,000 had to be

retransmitted, the TCP Efficiency would be calculated as:
101,000 - 1,000 x 100 = 99%

101,000

RFC 6349 Metrics: Buffer Delay
TCP throughput is also affected by increase in RTT, which can be
caused by network congestion or buffer delay.
The Buffer Delay Percentage is defined as:
Buffer Delay % = Average RTT during Transfer - Baseline RTT x 100

Baseline RTT
Example: If the baseline RTT for a network path is 2 ms and the

average RTT increases to 3 ms during the test. The Buffer Delay
Percentage would be calculated as:
3 2 x 100 = 50%
2

JDSU TrueSpeed = RFC 6349 Automated
Reduce operating expenses up to 30% by minimizing

truck rolls
Complete fast, repeatable, automated TCP tests in less

than 5 minutes
Verify results with an intuitive graphical user interface

that is easy to use by technicians at all skill levels
Closes the testing gap! Solve the tough, costly problems

that you miss with RFC 2544 and Y.1564

TCP Performance Issues
and the TrueSpeed Solution
13
TCP Window Problem: Misconfigured CPE Host
Provider Network
Customer Premise
100 M Ethernet
Service
20 msec round trip
Long Fat Network

Customer Laptop Firewall, Proxy, etc.
Problem Description Location / How does How can the

Responsibility TrueSpeedTM problem be
detect this? fixed?
Window size High latency and/or End hosts, WALK THE End-customer
not optimized High BW links Firewalls, WINDOW test must tune the
require end host Proxies reports the actual end host device
TCP WINDOW throughput vs. TCP Window
SETTINGS TO BE End-Customer ideal for various size
OPTIMAL for full Window Sizes
TCP throughput

Latency and TCP Window Size Relationship
The TCP Window size is the amount of data that a sender will place onto
the network before an ACK is required from the receiver
T3 Link with 25 ms RTT, (latency = 12.5 ms)
Internet
Sender with
Window = 17K #12
#1 #2 #3 * sending stops
Receiver
ACK takes 12.5 ms to reach Sender ACK
Window is full after ~ 3ms; no more data can be sent till the ACK is received
Twelve packets in flight = ~17KB
Optimum window is obviously much greater

The Bandwidth Delay Product (BDP)
Calculate Ideal TCP Window based on the Bandwidth

Delay Product (BDP)
BDP = RTD * Link BW / 8
Using the T3 example (45 Mbps link with 25 msec RTD)
BDP = 25 msec * 45 Mb/s / 8 = ~140 KBytes (Ideal TCP Window)
If TCP Window size = 17KBytes

User would only achieve maximum of ~5.5 Mbps TCP throughput
Most applications ride on TCP (i.e. FTP, HTTP)

Rather than UDP
FTP and HTTP performance are directly related to proper TCP
performance
Test TCP first, tune the TCP window, then test FTP and HTTP

DEMO 1: TrueSpeed Window Size Testing
Egress
Port
100 100
Mbps Mbps
20
TrueSpeed:
4 Window Sizes
BDP = BW x RTT / 8 = 100 Mbps x 0.020 / 8 = ~256,000 bytes
TrueSpeed Walk the Window test will be conducted to demonstrate

TCP throughput for 32 KB, 64 KB,128 KB, and 256KB TCP Windows

Traffic Policers,
Traffic Shapers and TCP

Bursty vs. Constant Traffic Applications
Bursty Traffic Constant Traffic
7 HTTP, FTP, E-mail, Voice and

on
Applicati Sharepoint, Broadband Video
6 n Communicator,
Pr esentatio
Facebook, YouTube,
5 Call setup
Session
TCP
t
4 Transpor UDP
Traffic Traffic
3
Network
2
Datalink
1
Physical Time Time

Constant Traffic vs. Burst Traffic on 1GigE Link
100Mb per second Constant Traffic on 1GigE Link

1GigE
Gap Time
Constant
Time Interval
Still 100Mb per second, but transmitted as a

1GigE burst for a fraction of the time interval
Burst Gap Time
Time Interval
Network Policers
Traffic is always sent at 1Gbps line rate

NTE with policer 100M CIR (Committed Information Rate) and 64KB CBS
(Committed Burst Size)
Policers meter on the ingress port, they dont buffer
count bytes and discard frames when the SLA is violated
Common Ethernet Mobile Backhaul scenario
NTE
Policing at
100M CIR
64KB CBS
1Gbps Line Rate Network side 10Gbps port

From Customer CPE Ingress CIR = 100M
Port CBS = 64KB

Constant Traffic 100 Mbps
Tokens
Policer Config:
CIR = 100 Mbps
CBS = 64 KB
Leaky
bucket
algorithm
1Gbps Line Rate 1Gbps Line Rate
CIR = 100 Mbps

Frame
CBS = 64 KB
Ethernet Switch or Router

Burst of Frames Equal to CBS
Tokens
Policer Config:
CIR = 100 Mbps
CBS = 64 KB
CIR = 100 Mbps

Frame
CBS = 64 KB

Burst of Frames Larger than CBS!
Tokens
Policer Config:
CIR = 100 Mbps
CBS = 64 KB
X
CIR = 100 Mbps
Frame
CBS = 64 KB

Demo 2: TrueSpeed Testing into a Policer with 64KB CBS
Policer:
100 Mbps CIR
64 KB CBS
Gig
GigE
E
410.5 ms Delay
TrueSpeed: up to 64 TCP
sessions: users browsing
web, emailing, FTPing, etc.
In the demo, the Near End T-BERD will send TCP traffic to the Far End T-
BERD which is essentially a TCP speed test
2 TCP sessions, each with a 64KB window will be used to generate an
aggregate 128 KB TCP window
128KBytes = Bandwidth Delay Product (BDP)

Traffic Shaping to Improve
TCP Performance

What is Traffic Shaping?
Traffic shaping will buffer and queue the excess packets

that are above a predefined traffic rate (i.e. CIR)
Unshaped LAN Traffic Shaped WAN Traffic
Shaper:
100 Mbps
GigE GigE
CPE
Router

Traffic Shaping in Action
Shaper Config:
CIR = 100 Mbps
CBS = 64 KB
256 KB CIR = 100 Mbps

Shaper Queue CBS = 64 KB
64 KB 64 KB 64 KB 64 KB

Recap: Shaper vs. a Policer
Shaping Policing
Traffic shaping will buffer Traffic policing will drop

and queue the excess the excess packets that
packets that are above a are above a predefined
predefined traffic rate traffic rate
29

Best Practice: Shaper at Customer Edge
LAN MPLS
CPE Router CE Router

with Shaping with Policing
MPLS
TBERD with CE Router

Integrated Shaper!! with Policing

Shaper Results Recap

The Future:
TrueSpeed
Network Function Virtualization (NFV)
Service Performance Challenges
1. Consumers complain they are not getting the bandwidth they are paying for
a. They run a speed test from an off-network site and get unreliable results
Test #1
Finger pointing begins!
Test #2
b. Carrier SLAs cannot be correlated to customer results
Test #3
2. Different Workgroups use different methods of testing performance

a. Speed Test servers, FTP servers, iPerf servers
b. Lack of standards based methods
Additional finger pointing!
3. Small Business Retail customers complain they have throughput problems

a. No way of correlating service performance results
Problem escalation & revenue impact!

RFC 6349 the TrueSpeed Advantage
SpeedTest or RFC 6349?
SpeedTest
Well known way of testing speed of a service
Performance varies when server is off-network
Non-standard test
Results do not help troubleshoot problem
RFC 6349
Standardized Test Methodology
- By standard body that created TCP/IP & Internet (IETF)
Apples-to-apples verification with customer
(consumer, business or retail) by all internal
groups
Provides information (actionable) need to repair
- TCP Efficiency (Indicator of retransmissions)
Buffer setup problems
Congestion
- Buffer Delay (Indicator of variable latency)
Congestion
Multiple paths for traffic
- TCP Window size
Is windows scaling turned on?

Test & Measurement Transition to Virtualization
The path to Network Function Virtualization will take a long time
, test and measurement tools will evolve into NFV as well.
CER
Today PER
CPE
Ethernet NID
CER
Tomorrow PER
TrueSpeedTM VNF SW
RFC 6349
CPE
Ethernet NID
x86 Server
Where its all headed

TrueSpeedTM VNF SW
RFC 6349
PER
CER
CPE
Ethernet NID
x86 Server
Questions and Answers
Session
36

JDSU TrueSpeed Automated RFC-6349 TCP Testing

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

JDSU TrueSpeed Automated RFC-6349 TCP Testing

Încărcat de

Drepturi de autor:

Formate disponibile

TrueSpeedTM

Automated RFC 6349 TCP Testing

Who should test TCP?

Why Test TCP?

What is RFC 6349?

TCP Performance Issues and the TrueSpeed Solution

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 2

T-BERD/MTS 5800 T-BERD/MTS 8000

T-BERD/MTS 6000 T-BERD/MTS 6000

1. Service providers offering Ethernet Business services

2. Service providers offering Ethernet Backhaul services

3. Mobility service providers deploying 3G or 4G/LTE

Running RFC2544, Y.1564 or other Layer 2/3 installation tests

But even when these Layer 2/3 tests pass, end-customers

Lack of TCP testing is a turn-up gap because end-customer

Save up to 30% OPEX costs by eliminating or quickly

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 4

HTTP, FTP, E-mail, Sharepoint,

TCP RFC 6349 TrueSpeedTM

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 5

100 Mbps Service

Layer 2 traffic testing was done twice, Test results = Pass

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 6

300 Mbps Service

Layer 2 traffic testing was done twice, Test results = Pass

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 7

IETF RFC 6349 specifies the methodology for measuring end-to-end

0. Run traditional RFC2544 to verify the integrity of the network at Layers

1. Path MTU Detection (per RFC4821)

2. Baseline Round-Trip Time and Bandwidth

3. Single and Multiple TCP Connection Throughput Tests

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 9

TCP efficiency= Transmitted Bytes - Retransmitted Bytes x 100

As an example, if 100,000 Bytes were sent and 1,000 had to be

101,000 - 1,000 x 100 = 99%

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 10

The Buffer Delay Percentage is defined as:

Buffer Delay % = Average RTT during Transfer - Baseline RTT x 100

Example: If the baseline RTT for a network path is 2 ms and the

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 11

Reduce operating expenses up to 30% by minimizing

Complete fast, repeatable, automated TCP tests in less

Verify results with an intuitive graphical user interface

Closes the testing gap! Solve the tough, costly problems

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 12

Long Fat Network

Problem Description Location / How does How can the

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 14

T3 Link with 25 ms RTT, (latency = 12.5 ms)

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 15

Calculate Ideal TCP Window based on the Bandwidth

If TCP Window size = 17KBytes

Most applications ride on TCP (i.e. FTP, HTTP)

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 16

BDP = BW x RTT / 8 = 100 Mbps x 0.020 / 8 = ~256,000 bytes

TrueSpeed Walk the Window test will be conducted to demonstrate

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 17

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 18

Bursty Traffic Constant Traffic

7 HTTP, FTP, E-mail, Voice and

2014 JDS Uniphase Corporation | JDSU CONFIDENTIAL AND PROPRIETARY INFORMATION 19

100Mb per second Constant Traffic on 1GigE Link

Still 100Mb per second, but transmitted as a

Burst Gap Time