Dear All, I am really thankfull towards you all for your kind help and quick response.
Actually now in Juniper M10i we don't have service PIC, we will be upgrading our Juniper M10i with MS-PIC which is an integrated service PIC. And also we can't activate lo0 interface for now on our network. We will be looking on this topic with details considering your given ideas and will further come on contact with experts like you whenever came on some confusion on any related issue. Thank You. Thank You very much for your kind help again. Regards, Uttam On Mon, Dec 21, 2009 at 1:51 PM, <[email protected]> wrote: > > I think it is common practice, and it is required also by major netflow > > tools, to have sampling enabled as input on all interfaces. This allows > > to directly getting stats for ingress traffic and indirectly getting > > stats for egress traffic by aggregating on the egress if-index of the > > netflow record. This avoid double counting the same flow first on > > ingress on one interface and then again on egress on another interface. > > Or just enable it on the transit/peering interfaces. You obviously > lose the information about which (internal) interface the traffic > is coming from. > > > One thing that you may want to check: I think that the M10i is equipped > > with the integrated service-pic that would allow to perform sampling in > > hardware rather than on the RE. In that case you find a sp-././. > > interface. By enabling family inet on it you enable the service pic; > > then you can source netflow from it. > > No, the M10i doesn't have any integrated service-pic. The M7i has an > integrated *tunnel PIC*, which is not the same. > > Steinar Haug, Nethelp consulting, [email protected] > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
