[j-nsp] rpm / ip-monitoring

Mike Gonnason gonnason at gmail.com
Wed Aug 27 20:52:02 EDT 2014


Instead of disabling the interface, can you just alter routing to avoid
that path, but RPM could still test since that interface would still be up?

-Mike Gonnason


On Wed, Aug 27, 2014 at 5:37 PM, Tyler Christiansen <tyler at adap.tv> wrote:

> Good point.  I glossed over that a bit.
>
> In that case, you won't even be able to test if it's working or not as you
> have disabled it (as Andrew points out).  I suppose you could write a
> script that re-enables the interface every hour or twenty four hours or
> whatever interval, then the RPM probe would just shut it back down if it's
> not fixing, but that seems a bit of a hassle.
>
> --tc
>
>
> On Wed, Aug 27, 2014 at 4:35 PM, Andrew Jones <aj at jonesy.com.au> wrote:
>
> > Surely the test will never recover without intervention, as the interface
> > it uses gets disabled?
> >
> >
> > On 28.08.2014 02:28, Tyler Christiansen wrote:
> >
> >> I could be mistaken, but I believe it automatically reverts when the
> test
> >> is successful unless you specify no-preempt.
> >>
> >>
> >> On Wed, Aug 27, 2014 at 12:50 AM, Mattias Gyllenvarg <
> >> mattias at gyllenvarg.se>
> >> wrote:
> >>
> >>  Dear List
> >>>
> >>> I have a rpm /ip-monitor setup that is supposed to test the function
> of a
> >>> local internet line (ping internet destination).
> >>>
> >>> And disable it if it is not responding.
> >>>
> >>> This works fine BUT, how do I get it to re-enable when it is working
> >>> again.
> >>>
> >>> I need this to work with DHCP so I cannot work with a default route.
> >>>
> >>>
> >>> **********************
> >>>
> >>> services {
> >>>     rpm {
> >>>         probe Internet {
> >>>             test PING-GOOGLE-DNS {
> >>>                 target address 8.8.8.8;
> >>>                 probe-count 5;
> >>>                 probe-interval 2;
> >>>                 test-interval 20;
> >>>                 thresholds {
> >>>                     total-loss 4;
> >>>                 }
> >>>                 destination-interface fe-0/0/3.0;
> >>>             }
> >>>         }
> >>>     }
> >>>     ip-monitoring {
> >>>         policy Local-Internet-Test {
> >>>             match {
> >>>                 rpm-probe Internet;
> >>>             }
> >>>             then {
> >>>                 interface fe-0/0/3 {
> >>>                     disable;
> >>>                 }
> >>>             }
> >>>         }
> >>>     }
> >>> }
> >>>
> >>> *************************
> >>>
> >>> --
> >>> *Med Vänliga Hälsningar / Best Regards*
> >>> *Mattias Gyllenvarg*
> >>> _______________________________________________
> >>> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
>
>
> --
>
> *Tyler Christiansen | Technical Operations*
> tyler <http://adap.tv/>@adap.tv <http://adap.tv/> | www.adap.tv
> *m :* 864.346.4095
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list