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 On 5/23/07, Pierantozzi Craig <[EMAIL PROTECTED]> wrote: > IMHO, I don't think sampling gives you the true data you need for > billing. Usage based billing is usually done using counters gathered > via SNMP to get the most accuracy. Depends on your billing model I > suppose but for true in/out packets/bytes, SNMP counters are the more > proven option. > > my .02 > > On May 23, 2007, at 12:22 PM, TCIS List Acct wrote: > > > > So without a services PIC, am I limited to 7,000pps flows? We > > don't push a lot > > of ppps now (maybe 200,000pps max) so the M7i won't even break a > > sweat with our > > current load. I just need to know that I can get _accurate_ > > NetFlow stats out > > of the M7i for billing purposes (bytes in/out per IP address for > > customer billing). > > > > --Mike > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
