Gert, As far as I know it's not on the roadmap for Sup720 but will be available for Sup2T with Flexible Netflow. In Sup2T FNF you can also have per-interface flowmask for Netflow.
Best regards, Andras On Mon, Dec 10, 2012 at 2:03 PM, Gert Doering <[email protected]> wrote: > Hi, > > On Mon, Dec 10, 2012 at 01:50:04PM +0100, Tóth András wrote: > > The reason you start seeing a conflict as soon as you enable mls flow > ipv6 > > is that IPv6 Netflow can only be enabled globally, not per-interface. > > Which is actually an interesting topic on its own. It used to be that > way for IPv4 Netflow, too, but later the code was changed to make that > per-interface (and it seems to really do that at flow collection time, > not only at flow-export time - so it helps TCAM contention if netflow > collection doesn't have to be on on all interfaces). > > Now the $5M question - is the hardware capable of doing IPv6 per-interface > netflow, and if yes, is this on Cisco's roadmap? For the Sup720, or > only for the Sup2T? > > (I'm more curious about the details, and not going to rant either way...) > > gert > -- > USENET is *not* the non-clickable part of WWW! > // > www.muc.de/~gert/ > Gert Doering - Munich, Germany > [email protected] > fax: +49-89-35655025 > [email protected] > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
