I'd be interested to learn this as well. Also, how can you monitor the router properly to know whether sampling is affecting performance (counters, ram, cpu, etc.)
/b On Thu, Aug 28, 2008 at 10:25 AM, Justin M. Streiner < [EMAIL PROTECTED]> wrote: > All: > > This is aimed more at people who running Juniper routers in fairly high > traffic environments, but any input is certainly welcome. > > I'm looking for recommendations/bast practices regarding what are good > starting points for setting the Netflow sampling rates to balance accuracy > of flow stats against not blowing the ASPIC-II out of the water... > > I've read a bit about this and the consensus seems to be that there is no > consensus :) I've seen implementations using between 1 packet out of every > 100 to 1 out of 1000 with differing run lengths. > > We do use Netflow based monitoring, so there is a need to sample often > enough to keep the data reasonably accurate. > > jms > _______________________________________________ > 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