Measurements in Support of End-to End Performance

1
Measurements in Support of End-to End Performance

• Matt Zekauskas, matt_at_internet2.edu
• Fall 2000 Internet2 Member Meeting
• Atlanta, Georgia

2
Outline

• Whats needed
• Monitoring
• Diagnostics
• General plans
• What can you do today

3
Vision I

• Ongoing monitoring to test major elements, and
  (some, important) end-to-end paths.
• Elements gigaPoP links, peering,
• Utilization
• Delay
• Loss
• Occasional throughput
• Multicast connectivity

4
Vision II

• There are many more paths end to end than can be
  monitored.
• Diagnostic tools available on-demand (with
  authorization)
• Show routes
• Perform flow tests (perhaps app tests)
• Parse/debug flows (a-la tcpdump or OCxMon with
  heuristic tools)

5
Problem Isolation via Divide and Conquer
6
Duke - Frankfurt
Goal 7 Mbps bi-directional UDP
Duke
Frankfurt
Teleglobe ATM
DFN
NCREN
Abilene
25 Broadway
Dante
WASH
NYCM
60 Hudson
7
The Duke-Frankfurt Problem
Abilene to Dante Link Utilization http//monon.uit
s.iupui.edu/abilene/nycm/dante-bits.html
8
In Process

• Abilene will be an exemplar
• All measurements open
• Tests possible to router nodes
• Web-based on-demand measurements
• Throughput tests routinely through backbone
• as well as existing utilization, etc.

9
Eventually

• Tests available in automated fashion
• Also utilize existing meas. infrastructures
• Spread to other backbones
• Spread to gigaPoPs
• Spread to campus edges
• available throughout Internet2 infrastructure
• Portable monitoring toolkit

10
What Is Available Today

• Abilene NOC tools
• www.abilene.iu.edu, operational
• Surveyor (one-way delay, loss, routing)
• www.advanced.org/surveyor
• AMP (round-trip delay, loss, routing)
• moat.nlanr.net/AMP (and /PMA)
• Intermediate throughput tests
• Ad-hoc, contact matt_at_internet2.edu

11
www.internet2.edu