[141098] in North American Network Operators' Group
sFlow and NetFlow data collection and monitoring
daemon@ATHENA.MIT.EDU (Sargun Dhillon)
Fri Jun 3 04:08:55 2011
Date: Fri, 3 Jun 2011 03:08:01 -0500 (CDT)
From: Sargun Dhillon <sdhillon@decarta.com>
To: nanog@nanog.org
In-Reply-To: <162006952.204671.1307087916175.JavaMail.root@mail-1.01.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I'm looking into network monitoring utilities for both gathering basic statistics conducive to my enterprise as well as looking for anomalies in traffic traffic. I'm curious as to how NANOG approaches this problem.
Are most of your statistics gathered via netflow, or sFlow? How do you gather them, and process them? What do most of you use the data for? Deciding (de)peering agreements? Reducing latency to your biggest customers?
How 'standard' are the industry standards (Fluke, Arbour). I've experimented with pm-acct, and flow-tools. How do you leverage flow-tools and pmacct?
--
Sargun Dhillon
deCarta
VoIP (US): +1-925-235-1105
