[159387] in North American Network Operators' Group

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

Re: OOB core router connectivity wish list

daemon@ATHENA.MIT.EDU (Saku Ytti)
Thu Jan 10 02:16:10 2013

Date: Thu, 10 Jan 2013 09:15:52 +0200
From: Saku Ytti <saku@ytti.fi>
To: nanog@nanog.org
In-Reply-To: <B10599B9-6AE5-4DAA-8865-CF036E7591D2@arbor.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On (2013-01-09 23:17 +0000), Dobbins, Roland wrote:

> Flow telemetry export - many of these so-called 'management' ports can't be used to export flow, oddly enough.

That is task for on-band interfaces, which attach to your forwarding-logic.
OOB is separate component, really only relying on same powersupply, it's
key value that it is not fate-sharing any more than absolutely must with
host.
To export flow, you need port to be connected to your forwarding hardware,
not control-plane and certainly not OOB management-plane. 

The port sole purpose is disaster recovery, it's like NG RS232 port, it
would not be used as your day to day port to configure the box. 

Cheack Cisco's "CMP" this is what we need.

-- 
  ++ytti


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