ACM Home Page
Please provide us with feedback. Feedback
Building a better NetFlow
Full text PdfPdf (256 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the 2004 conference on Applications, technologies, architectures, and protocols for computer communications table of contents
Portland, Oregon, USA
SESSION: Router design table of contents
Pages: 245 - 256  
Year of Publication: 2004
ISBN:1-58113-862-8
Also published in ...
Authors
Cristian Estan  University of California, San Diego, La Jolla, CA
Ken Keys  University of California, San Diego, La Jolla, CA
David Moore  University of California, San Diego, La Jolla, CA
George Varghese  University of California, San Diego, La Jolla, CA
Sponsors
ACM: Association for Computing Machinery
SIGCOMM: ACM Special Interest Group on Data Communication
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 13,   Downloads (12 Months): 155,   Citation Count: 26
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1015467.1015495
What is a DOI?

ABSTRACT

Network operators need to determine the composition of the traffic mix on links when looking for dominant applications, users, or estimating traffic matrices. Cisco's NetFlow has evolved into a solution that satisfies this need by reporting flow records that summarize a sample of the traffic traversing the link. But sampled NetFlow has shortcomings that hinder the collection and analysis of traffic data. First, during flooding attacks router memory and network bandwidth consumed by flow records can increase beyond what is available; second, selecting the right static sampling rate is difficult because no single rate gives the right tradeoff of memory use versus accuracy for all traffic mixes; third, the heuristics routers use to decide when a flow is reported are a poor match to most applications that work with time bins; finally, it is impossible to estimate without bias the number of active flows for aggregates with non-TCP traffic.In this paper we propose Adaptive NetFlow, deployable through an update to router software, which addresses many shortcomings of NetFlow by dynamically adapting the sampling rate to achieve robustness without sacrificing accuracy. To enable counting of non-TCP flows, we propose an optional Flow Counting Extension that requires augmenting existing hardware at routers. Both our proposed solutions readily provide descriptions of the traffic of progressively smaller sizes. Transmitting these at progressively higher levels of reliability allows graceful degradation of the accuracy of traffic reports in response to network congestion on the reporting path.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
IPMON - packet trace analysis. http://ipmon.sprintlabs.com/packstat/packetoverview.php.
 
2
Personal conversation with Dave Plonka.
3
 
4
Andy Bierman and Juergen Quittek. Packet sampling (psamp). IETF working group.
 
5
N. Brownlee, C. Mills, and G. Ruth. Traffic flow measurement: Architecture. RFC 2722, October 1999.
 
6
Nevil Brownlee and Dave Plonka. IP flow information export (ipfix). IETF working group.
 
7
J. Lawrence Carter and Mark N. Wegman. Universal classes of hash functions. In Journal of Computer and System Sciences, volume 18, April 1979.
8
9
10
11
12
13
 
14
Cristian Estan, Ken Keys, David Moore, and George Varghese. Building a better NetFlow: Technical report, 2004. http://www.caida.org/outreach/papers/2004/tr-2004-03/.
15
16
 
17
18
 
19
Ken Keys, David Moore, Ryan Koga, Edouard Lagache, Michael Tesch, and k claffy. The architecture of CoralReef: an Internet traffic monitoring software suite. In PAM2001. CAIDA, RIPE NCC, April 2001. http://www.caida.org/outreach/papers/2001/CoralArch/.
20
 
21
Keith McCloghrie and Marshall T. Rose. RFC 1213, March 1991.
 
22
David L. Mills. RFC 1305: Network time protocol (version 3) specification, implementation, March 1992.
 
23
D. Moore, V. Paxson, S. Savage, C. Shannon, S. Staniford, and N. Weaver. The spread of the sapphire/slammer worm. Technical report, 2003.
 
24
Cisco netflow. http://www.cisco.com/warp/public/732/Tech/netflow.
 
25
 
26
Peter Phaal, Sonia Panchen, and Neil McKee. RFC 3176: sFlow, September 2001.
 
27
 
28
 
29
Sampled NetFlow. http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s sanf.htm.

CITED BY  26

Collaborative Colleagues:
Cristian Estan: colleagues
Ken Keys: colleagues
David Moore: colleagues
George Varghese: colleagues