Download ppt slides

STARTAP
QBONE
Activities
Linda Winkler
IWS2000/APAN Technology Session
Feb 17, 2000
[email protected]
Internet2 QBone Initiative
Build interdomain testbed infrastructure
Experiment and improve understanding of DiffServ
Incrementally improve testbed
Support intradomain & interdomain deployment
Lead and follow IETF standards work
Some parts of DiffServ architecture ready; others far
from it
Our experience will inform standards process
Openness of R&E community gives us an edge
Users will tolerate the flakiness of an experimental
infrastructure
Engineers will share experience and measurement data
QBone as “infrastructure that only a graduate student
could love”
QBone Architecture (10km view)
IETF “Diff” (EF PHB) + QBone “Serv” (QPS)
QBone Premium Service
Idea: converge on Jacobson’s VLL “Premium” service
Well-defined SLS:
Peak rate (R) & “Service MTU” (M) implying a token bucket
meter
Near-zero loss
Low jitter
Delay variation due to queuing effects should be no greater
than the packet transmission time of a M sized packet
All bets are off if the reserved interdomain route flaps
Plus important value-adds:
Integrated measurement/dissemination infrastructure
Experimentation with pre-standards inter-domain bandwidth
brokering and signaling
STARTAP Architecture Diagram
U.S. and International o
Network Connections o
o
TransPAC
Ethernet
Ameritech NAP
Ascend 5XX ATM switches
DS
Cisco 7507
STAR TAP Cisco LS1010 ATM switch
STAR TAP 6TAP Router
(IPv6)
Router (IPv4)
Cisco 7200
Cisco 7505
Star Tap
General Purpose
UNIX Host
NLANR
AMP
NLANR
Web Cache
OC3c
NLANR
OC3MON
Various Speeds
STARTAP Simplified
SingAREN
IPV4
DS
APAN
KR
IPV4
DS
JP
IPV4
DS
Abilene
ESnet
AADS
Argonne
Mar ‘00
STARTAP
1 Mbps
IPV4
IPV6
IPV4
DS
STARTAP- IP DiffSrv Router
One stop shopping for STARTAP DS routes
STARTAP DS Router is AUP free
STARTAP DS Router will run experimental Cisco
IOS
Setting up Bandwidth Broker/Resource Manager
DS Components
Expedited Forwarding Cisco model
Ingress (classify, mark, police) CAR
Egress (bandwidth allocation) WFQ
Committed Access Rate Traffic Conditioner
Meter, mark and police (drop)
Queueing
WFQ
PQ
GARA Bandwidth Broker
Admission control
Resource management
Router configuration
Traffic Shaping (GTS, DTS)
DOE EMERGE Testbed
Abilene
Abilene
DS Boundary
DS
Boundary
Node
Node
GARA
Client
API
GARA
Resource
Manager
iCAIR
iCAIR
DS Boundary
DS
Boundary
Node
Node
Argonne
DSArgonne
Interior
DS
Interior
Node
Node
admission control,
manage resources,
configure devices
GARA
Client
API
Argonne
Argonne
DS Boundary
DS
Boundary
Node
Node
Argonne
DSArgonne
Interior
DS
Interior
Node
Node
UIC/EVL
UIC/EVL
DS Boundary
DS
Boundary
Node
Node
EMERGE/MREN
DS Region
Wisconsin
DS Wisconsin
Boundary
DS
Boundary
Node
Node
UChicago
UChicago
DS Boundary
DS
Boundary
Node
Node
NCSA/UIUC
DSNCSA/UIUC
Boundary
DS
Boundary
Node*
Node*
ESnet
ESnet
DS Boundary
DS
Boundary
Node
Node
mark
Layer 2 ATM
mostly UBR PVCs
police
www.evl.uic.edu/cavern/EMERGE
StarTAP
StarTAP
DS Boundary
DS
Boundary
Node
Node
Globus Grid Services Package
Deploy standard infrastructure across participating sites
Provide maximum capabilities to applications
Increase what can be “taken for granted” when developing
applications
Reduce deployment burden at sites
Services include
Authentication
Resource discovery
Resource management (Globus Architecture for Reservation and
Allocation – GARA)
Instrumentation (netlogger)
Globus Architecture for
Reservation and Allocation (GARA)
Three important contributions:
Support for Advance Reservations
Uniform treatment of underlying resources
Network, disk, CPU etc…
Currently supported:
Differentiated Services, DPSS, and DSRT
Layered architecture enables generic coreservation agents
User is able to select API best suitable for his need
GARA Basics—Reservations
There is a generic “reservation”, which has several
properties:
Start Time (“now” or future) and Duration
Resource type/Underlying resource identifier
Resource-specific (bandwidth, % CPU…)
All reservations are treated uniformly:
Create/Modify (Given properties)
=> Returns Reservation Handle
Destroy
Monitor (Callbacks or Polling)
End-to-End Network Reservations
Algorithm for a single network reservation
Discover which gatekeepers/resource
managers need to be contacted (MDS)
Make reservation at each one.
End-to-End Co-Reservation Agent
Resource Manager
User process
MDS
Resource Manager
Workstation
GARA features
Reservation-Subtypes
low-latency
Used to support jitter sensitive applications using the same
EF aggregate behavior as high-throughput TCP applications
Based on traffic shaping and Priority-Queuing
Currently being evaluated
background
Used to support bulk transfers, including deadline support.
Takes at least the amount of premium traffic required to
fulfill the deadline; more if not used actively
Monitoring of the network edges
Provides feedback to applications when they send too
fast
Basic Experiment I
Goal: Proof of Premium Quality for TCP flows
Run modified ttcp with different traffic and
reservation profiles; gather receiver bound statistics
Create congestion using gen_send/recv
Stable Long Term TCP Traffic
(Attempted Rate: 6000KB/s, Buffer size: 2000000 bytes)
9000
8000
Actual Rate (Kbs)
7000
6000
Rate
Limit
5000
4000
3000
2000
1
7
13
19
25
31
37
43
49
55
Time
61
67
73
79
85
91
97
Basic Experiment II
Use tcpdump and tcptrace understand the
behavior
Use netlogger_enabled ttcp_gara and
gen_recv to publish data into MDS. “Real
Time Visualization of rtt”
Basic Experiment III
Goal: Demonstrate Premium Quality for UDP flows
Run mgen/drec with different traffic and reservation
profiles; gather receiver bound statistics
Create congestion using gen_send/recv
Basic Experiment IV
Goal: Proof Premium Quality for UDP
flows sharing one EF aggregate
Run mgen/drec with different traffic and
reservation profiles; gather receiver
bound statistics
Run high-throughput ttcp using a correct
reservation
Create congestion using gen_send/recv
Testing
 Perform local ANL/GARNET tests
 Each EMERGE site provides a test machine (Linux
RH6.1)
 Phase 1- measure baseline end-to-end BE performance
(desire 100 Mbps ~ achieving 70-80 Mbps)
Phase 2- measure single stream end-to-end Premium
service
Need better measurement tools and techniques
Phase 3- measure application end-to-end performance
Phase 4- measure multiple stream end-to-end Premium
service
Phase 5- evaluate a MPLS label-switched router as a
Diffserv router
References
www.globus.org
www.globus.org/qos
www.internet2.edu/qos