[j-nsp] IP Monitoring/Tracking (SLA) on high end SRX

[Morgan McLean]

I guess technically any protocol would help in this case...regardless of
default advertisement. I'm guessing no protocols are possible?


On Sun, Aug 18, 2013 at 2:46 AM, Morgan McLean <wrx230 at gmail.com> wrote:

> Could you ask them to use a routing protocol and implement some logic on
> their side dictating when they advertise a default to you?
>
> Morgan
>
>
> On Sat, Aug 17, 2013 at 2:40 PM, Ahmad Hasan <barakat-ahmad at hotmail.com>wrote:
>
>> BFD is not a valid option because the other end is cisco and the customer
>> is
>> using PBR, so based on their feedback they can't implement BFD along with
>> PBR on cisco side
>>
>> BR,
>> A.Hasan
>>
>> -----Original Message-----
>> From: Chris Kawchuk [mailto:juniperdude at gmail.com]
>> Sent: Friday, August 16, 2013 3:47 AM
>> To: Ahmad Hasan
>> Cc: juniper-nsp at puck.nether.net
>> Subject: Re: [j-nsp] IP Monitoring/Tracking (SLA) on high end SRX
>>
>> How about a default 0.0.0.0/0 with a bfd-liveliness detection.
>>
>> We use this for conditionally routing statics every now and then.
>>
>> Works well assuming the next-hop supports BFD; and no dynamic routing
>> protocol needed.
>>
>> - CK.
>>
>>
>> On 16/08/2013, at 7:15 AM, Darren O'Connor <darrenoc at outlook.com> wrote:
>>
>> > You could run VRRP on R1 and R2 giving R1 the higher priority. Have
>> > the static default on the SRX3600 pointing to the VRRP IP
>> >
>> > Darren
>> > http://www.mellowd.co.uk/ccie
>> >
>> >
>> >> From: barakat-ahmad at hotmail.com
>> >> To: juniper-nsp at puck.nether.net
>> >> Date: Tue, 13 Aug 2013 13:16:49 +0300
>> >> Subject: [j-nsp] IP Monitoring/Tracking (SLA) on high end SRX
>> >>
>> >> Dear All
>> >>
>> >>
>> >>
>> >> We have high end SRX3600 connected to layer2 switch and then to two
>> >> gateway routers, and we have a static default route to R1 with
>> >> default preference
>> >> (5) and to R2 with preference 10, we need to track the IP of R1 so
>> >> that in case we couldn't ping R1 the route to prefer R2 i.e. in case
>> >> the link between R1 and the layer2 switch went down the route to prefer
>> R2.
>> >>
>> >> Noting that we were able to accomplish the above requirements with
>> >> branch SRX using either two options (set services ip-monitoring) or
>> >> (set services
>> >> rpm)
>> >>
>> >> Unfortunately the mentioned commands are not supported on high end
>> >> SRX
>> >>
>> >> Any ideas.
>> >>
>> >>
>> >>
>> >> Regards
>> >>
>> >> A.Hasan
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> 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
>>
>
>
>
> --
> Thanks,
> Morgan
>



-- 
Thanks,
Morgan