, August 16, 2013 3:47 AM
To: Ahmad Hasan
Cc: juniper-nsp@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
AM
To: Ahmad Hasan
Cc: juniper-nsp@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
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
on cisco side
BR,
A.Hasan
-Original Message-
From: Chris Kawchuk [mailto:juniperd...@gmail.com]
Sent: Friday, August 16, 2013 3:47 AM
To: Ahmad Hasan
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] IP Monitoring/Tracking (SLA) on high end SRX
How about a default 0.0.0.0/0
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
] 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
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
7 matches
Mail list logo