Yes – I should add, this is being done because unfortunately SNMP won’t work in this instance. On this platform (ASR1001-X), port-channel subinterface counters don’t work. There is a hardware limitation, according to TAC.
From: Deny IP Any Any [mailto:denyipany...@gmail.com] Sent: Wednesday, 30 November 2016 7:47 AM To: Chris Balmain <chris.balm...@connectivityit.com.au> Subject: Re: [c-nsp] Netflow on non-IP interfaces? if all you want is bytes in/out, maybe SNMP would be easier for this On Mon, Nov 28, 2016 at 5:59 PM, Chris Balmain <chris.balm...@connectivityit.com.au<mailto:chris.balm...@connectivityit.com.au>> wrote: Hi list, I'm trying, perhaps in vain, to get some Netflow data on a non-IP interface on an ASR1K - in this case, a PPPoE server interface like: interface Port-channel1.20 encapsulation dot1Q 20 pppoe enable group XXXX ! I tried defining a custom record that only matches & collects very basic fields: flow record TEST match interface input match interface output collect counter bytes collect counter packets ! ...with an associated monitor/exporter and applied to the PPPoE server interface with "ip flow monitor XXX in" and ditto for out - but I don't get any flows appearing in the cache or exported to my collector. I also tried "mpls flow monitor XXX in" with the same result. Is there any way to get Netflow to work with L2 traffic? I'm only interested in the fields I mentioned above - in/out interface, and bytes/packets counts. Regards, Chris _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- deny ip any any (4393649193 matches) _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
