[c-nsp] netflow on bridge domain interface

[CiscoNSP List]

Late reply, apologies, but I found the old case, and Netflow (At the time when opening the case) ended up being not supported, but on the "roadmap" as a supported feature...TAC could not give me any approx dates that it would be supported....Ill have to test out one of our 1001X's to see if its still the case.....it's certainly configurable under the BDI, just didnt "work" in one direction (But as I said, that was over a year ago)....

Kindly find the following document
http://www.cisco.com/c/en/us/td/docs/routers/asr1000/configuration/guide/chassis/asrswcfg/bdi.html
[http://www.cisco.com/web/fw/i/logo-open-graph.gif]<http://www.cisco.com/c/en/us/td/docs/routers/asr1000/configuration/guide/chassis/asrswcfg/bdi.html>

Configuring Bridge Domain Interfaces - Cisco<http://www.cisco.com/c/en/us/td/docs/routers/asr1000/configuration/guide/chassis/asrswcfg/bdi.html>
www.cisco.com
Current Book Title. Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide. Current Chapter Title. Configuring Bridge Domain Interfaces




Restrictions for Bridge Domain Interfaces

The following are the restrictions pertaining to bridge domain interfaces:

Only 4096 bridge domain interfaces are supported per system.

Bridge domain interfaces do not support the following features:

- PPP over Ethernet (PPPoE)

- Bidirectional Forwarding Detection (BFD) protocol

- Netflow

- QOS

- Network-Based Application Recognition (NBAR) or Advanced Video Coding (AVC)





________________________________
From: cisco-nsp <cisco-nsp-bounces at puck.nether.net> on behalf of CiscoNSP List <CiscoNSP_list at hotmail.com>
Sent: Thursday, 19 May 2016 12:17 PM
To: Mike; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] netflow on bridge domain interface


Hmm..replied to this earlier, but didnt show up on the list (My other replies have come through immediately) - re-send....apologies for double post, if the original reply shows up :)

I ran into a similar problem on our older ASR1001's, trying to get FNF to work....one way traffic only being reported(Config was correct)....opened TAC case that was "protracted"....out of frustration, and needing FNF "immediately", I ended up having to just use old-style dot1Q subints, and FNF worked without issue(Same config as was on the BDI Int).....Ill dig up the old case details.....but this was at least a year ago....so was hoping the "bug" was fixed by now....



________________________________________
From: cisco-nsp <cisco-nsp-bounces at puck.nether.net> on behalf of Mike <mike-cisconsplist at tiedyenetworks.com>
Sent: Sunday, 15 May 2016 6:06 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] netflow on bridge domain interface

Hi,

     I am playing to ntopng and nprobe to capture the flow exports from
a bridge domain interface, and I seem to only be seeing statistics for
one side of the conversation however (inbound internet -> hosts). The
BDI is connected to my default gateway and so certainly everything to
and from the internet has to pass by this way. I am running  03.10.05.S
on an asr1000, wondering if this is a bug/limitation/config error on my
part?

Mike-

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
cisco-nsp Info Page - puck.nether.net<https://puck.nether.net/mailman/listinfo/cisco-nsp>
puck.nether.net
To see the collection of prior postings to the list, visit the cisco-nsp Archives. Using cisco-nsp: To post a message to all the list members, send ...



archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/