[183436] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NetFlow - path from Routers to Collector

daemon@ATHENA.MIT.EDU (Mark Tinka)
Wed Sep 2 02:19:34 2015

X-Original-To: nanog@nanog.org
To: Roland Dobbins <rdobbins@arbor.net>, nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Wed, 2 Sep 2015 08:08:37 +0200
In-Reply-To: <8A2AD148-2748-4633-AB7B-B6D227C3D0B4@arbor.net>
Errors-To: nanog-bounces@nanog.org



On 1/Sep/15 19:12, Roland Dobbins wrote:

>
>  
>
> Running flow telemetry in-band is penny-wise and pound-foolish, for
> networks of any size, in any circumstances.  All management-plane
> traffic (and that's what flow telemetry is) should be segregated from
> the production network data plane.

Looking at the span of my network, when I am building an OoB platform to
maintain management access to any device that may lose in-band
connectivity, I'll be honest, moving flow data across that is the least
of my worries. Simply because the costs and effort associated with
getting OoB management plane access that is cleanly separated from
in-band topologies does not always encourage the addition of traffic
that could kill the case for the same.

When my device is down, my primary objective is to get it back up, fast.
Flow data being lost is less of a problem.

Mark.

home help back first fref pref prev next nref lref last post