[183417] in North American Network Operators' Group
Re: NetFlow - path from Routers to Collector
daemon@ATHENA.MIT.EDU (Roland Dobbins)
Tue Sep 1 18:56:06 2015
X-Original-To: nanog@nanog.org
From: "Roland Dobbins" <rdobbins@arbor.net>
To: nanog@nanog.org
Date: Wed, 02 Sep 2015 05:51:41 +0700
In-Reply-To: <0AAF5D1F-688F-450A-8049-43AF1E37BE8E@puck.nether.net>
Errors-To: nanog-bounces@nanog.org
On 2 Sep 2015, at 5:38, Jared Mauch wrote:
> Please stop digging,
Since I'm not digging, I've no reason to stop. I see and deal with the
various quirks of more different platforms exporting flow telemetry than
most folks, all day, every day, so I know just a little bit about this
topic.
> Sounds like you haven’t used Cisco recently.
I use Cisco all the time, thanks. They aren't perfect - no vendor is.
They have various issues with their NetFlow implementations on various
platforms - for example, bursts of wildly inaccurate flow statistics
from CRS boxes when a linecard is rebooted, a problem which has
persisted for years and is just now being addressed. Odd stuff with
EARL8 on Sup2T/DFC4 in certain configurations, and so forth.
But Niels is grossly exaggerating. I get very usable flow telemetry from
them in many, many networks. I deal with flow telemetry from many,
many vendors/platforms, and I can confidently assert that Cisco are
nowhere near the bottom of the heap when it comes to the verisimilitude
and functionality of their flow telemetry export. Quite the opposite
-----------------------------------
Roland Dobbins <rdobbins@arbor.net>
