[j-nsp] sampled problem

[Paul Goyette]

When first starting sampling, it is necessary for rpd and sampled
to get "in sync".  Depending on how many routes you have, it can
take a couple minutes or so for sampled to learn which routes go
with which AS.

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Richard A
Steenbergen
Sent: Wednesday, February 25, 2004 6:18 PM
To: Jonas Frey (Probe Networks)
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] sampled problem


On Thu, Feb 26, 2004 at 02:15:08AM +0100, Jonas Frey (Probe Networks) wrote:
> Hi Yulianto,
>
> the high usage went away after 2-3 minutes. Thanks for everyone who
> pointed this out. Strange anyway.

Yeah I see that one all the time, but usually after first turning on
sampling. Anyone from jnpr want to tell us why? :)

--
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp