Internet2 Network Observatory Update

Matt Zekauskas, matt@internet2.eduMeasurement SIG

2006 Fall Member Meeting4-Dec-2006

2 Matt Zekauskas

Note…

• There is a main track session on the Observatory Wednesday morning

• This will be my take, and an opportunity for you to ask questions and give comments

3 Matt Zekauskas

Recall: Abilene Observatory

• Motivation• Monitor network operations• Support network research

• Two components• Data collected by NOC, OHIO ITEC, and Internet2

for operations and research, stored in distributed databases• Equipment colocation where uniquely useful for

research projects [allocate power and space ahead of time]

4 Matt Zekauskas

Abilene Observatory: Capabilities

• One way latency, jitter, loss• IPv4 and IPv6 (“owamp”)

• Regular TCP/UDP throughput tests – ~1 Gbps• IPv4 and IPv6; On-demand available (“bwctl”)

• SNMP• Octets, packets, errors; collected 1/min

• Flow data• Addresses anonymized by 0-ing the low order 11 bits

• Routing updates• Both IGP and BGP - Measurement device participates in both

• Router configuration• Visible Backbone – Collect 1/hr from all routers

• Dynamic updates• Syslog; also alarm generation (~nagios); polling via router proxy

5 Matt Zekauskas

Abilene Observatory: Datasets

• Usage Data

• Netflow Data

• Routing Data

• Latency Data

• Throughput Data

• Router Data

• Syslog Data

6 Matt Zekauskas

Abilene Observatory: Rack Hardware

• Local rack LAN switch• 2 PC’s with direct gigE attach to routers

for throughput testing• 1 PC for latency testing• 1 PC for dynamic • 1 PC for statistics collection (netflow

redistribution, routing, …) – collect locally in case of network partition

7 Matt Zekauskas

Abilene Observatory: Collocation

• PlanetLab

• NLANR MNA OCxMON

• NLANR MNA AMP

• High-speed TCP testing and protocol development

8 Matt Zekauskas

Rough Timeline

• Started thinking about what a new Observatory might mean a while ago, focusing on measuring “lightpaths”; HOPI

• Small group (Magorian, Metzger, Boote, Boyd Zekauskas) came up with initial thoughts (~June 2006)• Languished due to other commitments and NTAC

development

• Proceed with something reasonable for initial Internet2 Network node deployment

9 Matt Zekauskas

Internet2 Network Observatory Goals

• Maintain Abilene Observatory features• Keep current data collection going (and in fact we want latency and

throughput testing maintained throughout transition to monitor)• Keep current testing to middle available

• Take advantage of newer processors and buses now available• AC power helps!

• 10 G capabilities• Incorporate what we learned from HOPI

• Control/test/measurement• Flexibility to update configuration, software based on experience,

community input, research input• Not so complex as to be unmanageable

10 Matt Zekauskas

Internet2 Network Observatory

• Initial realization• Router nodes• Same number of machines as Abilene• Different interconnection, more powerful

LAN switch, 10GE router attachment

• Optical nodes• Same number of machines as HOPI• But connect to the Ciena CD CI

11 Matt Zekauskas

Router Nodes

12 Matt Zekauskas

Optical Nodes

13 Matt Zekauskas

Internet2 Observatory: Collocation

• PlanetLab – new machines to be deployed (were to be upgraded anyway)

• Passive: in discussion with CAIDA (Matt Z to go back, given that there is now a timeline)

• AMP project has apparently ended, so it will not continue

• Adding a Phoebus PC at router sites• Adding NetFPGA capability at optical sites

14 Matt Zekauskas

Next Steps

• As always, respond to suggestions• If there is a particular aspect you are interested in,

let us know!

• Revisit requirements document from June (see http://measurement.internet2.edu/ , next talk)

• Review/direction from NTAC, possible WG• NOC adding basic performance monitoring for

optical nodes• Internet2+NOC adding perfSONAR interfaces

15 Matt Zekauskas