Transcript
Page 1: Interpreting Network Traffic Flows

Interpreting Network Traffic Flows

Bill Jensen, Paul Nazario and Perry Brunelli

Page 2: Interpreting Network Traffic Flows

Agenda

1. How did we get here

2. Network monitoring tools

3. Sample graphs

Page 3: Interpreting Network Traffic Flows

Shawn Fanning http://www.time.com/time/magazine/

articles/0,3266,55730,00.html

Napster

Page 4: Interpreting Network Traffic Flows

Taming Bandwidth Hogs . . . How can your campus do it?

Ana Preston, University of Tennessee

Linda Roos, University of Nebraska, Lincoln

Tuesday, 11:45, Marquis 4

Page 5: Interpreting Network Traffic Flows

www.funnytimes.com

Page 6: Interpreting Network Traffic Flows

A simple question

CIO requested that we estimate Internet transit requirements for the next 18 months

Page 7: Interpreting Network Traffic Flows

Sources

www.research.att.com/~amo/doc/networks.html

http://www.research.microsoft.com/~Gray/Moore_Law.html

Page 8: Interpreting Network Traffic Flows
Page 9: Interpreting Network Traffic Flows

What are current bandwidth requirements?

What do we receive from our provider?

Page 10: Interpreting Network Traffic Flows

A few words about UW Internet access

WiscNet is a state education-based ISP - founded with help from UW-Madison

Charter membership included 14 UW-System universities and 8 privates colleges

WiscNet now serves over 500 educational institutions - predominantly K-12

Page 11: Interpreting Network Traffic Flows

The WiscNet backbone

Comprised of OC-3 links connecting UW- Madison, UW-Milwaukee, the Chicago NAP and the Ameritech Advanced Data Service Center (AADS), also in Chicago.

Page 12: Interpreting Network Traffic Flows
Page 13: Interpreting Network Traffic Flows
Page 14: Interpreting Network Traffic Flows

WiscNet Services

Internet transport and transit Internet 2 transport Peering transport at AADS

Page 15: Interpreting Network Traffic Flows

Current bandwidth requirements continued... Inbound vs. outbound traffic Usage caps Prime time usage Peering and I2 traffic Effect of peer-to-peer networking and

future policy on usage/fair utilization

Page 16: Interpreting Network Traffic Flows

www.wiscnet.net

Page 17: Interpreting Network Traffic Flows

What is a flow?

Host-to-host conversation between that includes the IP address and port # for each host.

Representation of a series of packets traveling between two end-points.

A unidirectional series of IP packets of a given protocol, traveling between a source and destination within a certain period of time.

Page 18: Interpreting Network Traffic Flows

Flow as represented by log

Easy to think of it as we would a sniffer trace - bits and bytes seen traversing the wire

In actuality, the flows are the accounting record or log of activity as reported by the router

Page 19: Interpreting Network Traffic Flows

Measurement Tools - Flowscan

Flowscan - freely available perl scripts and modules that aggregate other freely available tools for representing flows

Analyzes and reports on NetFlow data collected by CAIDA’s clfowd

Stored using RRDtool - time series data Flowscan provides reporting capabilities

and visualization of flow data

Page 20: Interpreting Network Traffic Flows

Example

cflowd receives flow data from the router and writes it to disk.

Flowscan parses/messages data from cflowd and stores the results in RRD format.

RRDtool graph produces graphs from RRD files.

Page 21: Interpreting Network Traffic Flows

More on FlowScan

See http://net.doit.wisc.edu/~plonka/lisa/FlowScan/

[email protected]

http://mil.doit.wisc.edu/~plonka/

Dave ->

Page 22: Interpreting Network Traffic Flows

General Flowscan Graphs

Page 23: Interpreting Network Traffic Flows
Page 24: Interpreting Network Traffic Flows
Page 25: Interpreting Network Traffic Flows
Page 26: Interpreting Network Traffic Flows
Page 27: Interpreting Network Traffic Flows
Page 28: Interpreting Network Traffic Flows
Page 29: Interpreting Network Traffic Flows
Page 30: Interpreting Network Traffic Flows
Page 31: Interpreting Network Traffic Flows
Page 32: Interpreting Network Traffic Flows

Network Events Captured by FlowScan

Page 33: Interpreting Network Traffic Flows
Page 34: Interpreting Network Traffic Flows
Page 35: Interpreting Network Traffic Flows
Page 36: Interpreting Network Traffic Flows
Page 37: Interpreting Network Traffic Flows
Page 38: Interpreting Network Traffic Flows
Page 39: Interpreting Network Traffic Flows

New Development

wwwstats.net.wisc.edu/CampusIO/top/originAS.html

wwwstats.net.wisc.edu/CampusIO/top/128.104.16.0_22_top.html

Page 40: Interpreting Network Traffic Flows

“It’s easier to ride a horse in the direction it’s going”

Daniel Burrus

www.burrus.com


Top Related