Management Benchmarking Framework IETF 87 Berlin draftconstantinebmwgtrafficmanagement01 Barry Constantine barryconstantinejdsucom Tim Copley timothycopleylevel3com Ram Krishnan ID: 400195
Download Presentation The PPT/PDF document "Traffic" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Traffic
Management
Benchmarking Framework
IETF
87 Berlin
draft-constantine-bmwg-traffic-management-01
Barry
Constantine
barry.constantine@jdsu.com
Tim Copley
timothy.copley@level3.com
Ram
Krishnan
ramk@brocade.comSlide2
Traffic Management Benchmarking Overview
Extends RFC 2544 benchmarking into traffic management functionality of network elements:
Classification / Prioritization
Policing
Queuing / Scheduling
Shaping
AQMSlide3
Revisions Incorporated into Draft-01
This
revision
primarily augmented
the
verification focus of
the first draft
by adding
capacity benchmarking for each traffic management
area
An example would include the area of traffic shapers; the capacity benchmarking section specifies various combinations of stress test including:
Single shaper per port, all ports active
Multiple shapers per port, single port active
Combination of the first two; multiple shapers per port and all ports activeSlide4
Other Status on this Draft
In addition to stateless traffic tests, the draft proposes TCP
stateful
traffic (“TCP Test Patterns”) to emulate application traffic behavior
In addition to bulk file transfers,
e
xamples include HTTP web browsing, data base transactions, etc. which are chatty by nature
We researched and experimented with Flowgrind and Harpoon open source tools to study emulation techniques
Conducted some basic traffic shaper and policer lab tests to study vendor behavior and developed test scripts to analyze packet capture files (next slides) Slide5
Traffic Shaper Lab Experiments (1)
This is the output of a vendor’s traffic shaper, configured for a CIR of
40 Mbps,
20KB
CBS
and
shaper
default queue size of 64,000 bytes. Ingress Layer 2 traffic was configured for 128 KB bursts / 128 byte packets.Slide6
Traffic Shaper Lab Experiments (2)
Same test configuration as first slide, but increased shaper queue
to 131,072 bytesSlide7
Next Steps for the Traffic Management Draft
We seek the BMWG to formally adopt this personal submission as a chartered draft work
Work on the next revision(s) to:
I
ncorporate the excellent comments that we received (thanks Al and Reinhard!)
Conduct laboratory testing to verify the core procedure(s)