In this case, couldn't source/destination class accounting work for you instead?
http://www.juniper.net/techpubs/software/junos/junos83/swconfig83-networ k-interfaces/html/interfaces-family-config40.html -evt > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > TCIS List Acct > Sent: Thursday, May 24, 2007 11:42 AM > To: NSP Juniper > Subject: Re: [j-nsp] NetFlow on M7i > > > > Erdem Sener wrote: > > In case you're monitoring on a interface basis, and just the in/out > > octets, I would aggree that SNMP is the way to go and using sampling > > would just be complexing things unnecessarily. > > > > However, if you not only need the interface counters but > want to have > > information on flows (e.g traffic from/to a single host > host on a /24 > > ethernet interface), sampling would do the trick. > > > > Cheers, > > Erdem > > > > Unfortunately SNMP monitoring won't work for us. We need to > be able to exclude > certain traffic from the measurements (such as > locally-originated backup > traffic, etc). This is why NetFlow or something similar is > what we need to use. > > --Mike > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
