[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[c-nsp] Peering + Transit Circuits
- Subject: [c-nsp] Peering + Transit Circuits
- From: tdurack at gmail.com (Tim Durack)
- Date: Tue, 18 Aug 2015 09:44:34 -0400
- In-reply-to: <[email protected]>
- References: <CAE_ug143GsMN3+CNz=AgTr+xjGWY2CrmXYW=jf36JQ3AAnukFw@mail.gmail.com> <[email protected]> <CAE_ug14LM_Ev_MkK_OAO_MtY8A==BY7Goa=02+oYSvi2n8d=yw@mail.gmail.com> <[email protected]>
On Tue, Aug 18, 2015 at 9:38 AM, Gert Doering <gert at greenie.muc.de> wrote:
> Hi,
>
> On Tue, Aug 18, 2015 at 09:32:53AM -0400, Tim Durack wrote:
> > > (It would be cool if Cisco would understand that hardware forwarding
> > > platforms need useful netflow with MAC-addresses in there... ASR9k at
> [..]
> > At the risk of introducing religion, I will mention sFlow...
>
> Yes... and this is helping exactly why...? Given the overwhelming
> support for sFlow in (Cisco-) hardware routers used as peering edge? :-)
I ask Cisco for sFlow support on a regular basis. Cisco typically respond
with some variation of NIH syndrome. Anyway, back to my question :-)
--
Tim:>