[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OOB core router connectivity wish list
- Subject: OOB core router connectivity wish list
- From: rdobbins at arbor.net (Dobbins, Roland)
- Date: Sat, 12 Jan 2013 16:39:08 +0000
- In-reply-to: <CAL9jLabcyTQns31FO1Pys0Mc3-E_=Ng46Saj5njL1JwYmUWRQg@mail.gmail.com>
- References: <[email protected]> <CAP-guGWxsGryfE0=fuezeqfu6yO7u76DL5YjG4UgT=3a63kDTQ@mail.gmail.com> <[email protected]> <[email protected]> <CAL9jLabcyTQns31FO1Pys0Mc3-E_=Ng46Saj5njL1JwYmUWRQg@mail.gmail.com>
On Jan 10, 2013, at 9:35 AM, Christopher Morrow wrote:
> I don't think roland was really saying that normal netflow from a device in production pushing a few hundred gbps of traffic would be
> appropriate to ship out the OOB network... or I hope that wasn't his point. I don't think oob networks need to be sized for that.
Actually, that is what I'm saying - and with sampled flow telemetry, this isn't a huge bps issue. With flow telemetry, we're typically looking at 0.5% - 1.5% of the aggregate utilized bandwidth of the exporting device, multiplied by the sampling ratio (e.g., .01, .0001, whatever) - so, they isn't a huge amount of traffic, even for very high-speed network.
Modern networks should be designed with OOB/DCN which are sufficiently sized to handle flow telemetry. Exporting it in-band means that one is blind during network partition events, when visibility is key.
-----------------------------------------------------------------------
Roland Dobbins <rdobbins at arbor.net> // <http://www.arbornetworks.com>
Luck is the residue of opportunity and design.
-- John Milton