Hi Osama, On Thu, May 09, 2013 at 11:13:56AM +0200, Osama Abuelsorour wrote:
> What we are trying to do is to gain insights about traffic from the PE router > towards our core network by applying NetFlow on the aggregate interface > towards the core. Ideally, we want to use the MPLS tags to be able to > identify and aggregate flow statistics coming from the access side. Then > using some external helpers, the MPLS tags can be given meanings rather than > just numbers. > > The other alternative would be to apply NetFlow on all the interfaces from > the access side, which is really a nightmare on all levels. Makes sense. Was wondering what is the meaning of 'identify' flows coming from the access side: is it understanding which L2/L3 MPLS VPN a particular flow belongs to? If yes, still doing egress NetFlow towards the core, would looking at the input interface be an option? The helper you would have to build for resolving ifindexes should be much easier than resolving MPLS labels since also it's all standard SNMP MIBs. Or you have multiple levels of aggregation and the input interface doesn't say much? Or there is more or different that i'm missing? Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
