[j-nsp] Juniper RPM Monitoring

[Danny Vernals]

On Wed, Aug 24, 2011 at 7:41 PM, Keegan Holley
<keegan.holley at sungard.com> wrote:
> Does anyone have any experiences with RPM on MX boxes?  I'm a bit leary of
> monitoring daemons and probes running directly on routes.  Then there's the
> recent bug circus with the 9 and 10 code trains.  I also can't remember
> coming across it anywhere in the wild.  Just wondering if anyone has had any
> experience with it positive or negative.

I've played with a test deployment on MX and M series on various
releases 8.1 through 10.4.  Enabling the service didn't have any
detrimental effect on the routers, no bugs were encountered and there
was only a minimal impact on CPU.

Using it to monitor availability worked fine but if you're planning on
monitoring latency and jitter then my findings were to do this you'd
need an MS-DPC.  With an MS-DPC the service can use two-way time
stamping, without one you can only do one-way timestamping and you're
reliant on the RE so results are subject to variance when the router
is busy with RPD etc.  There was a significant difference between
latency / jitter measured on external probes compared to results based
on RPM.

The MS-DPC route was too expensive for us.

>
> http://www.juniper.net/us/en/local/pdf/app-notes/3500145-en.pdf
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>