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

[Darren O'Connor]

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