As soon as the RPM object no longer reaches the destination, the preferred route is set with "[Static/1] 00:03:03, metric2 0". The AD of 1 is therefore better than the normal static route with the value of 5. Accordingly, the backup path should be specified under preferred route. Otherwise, the appropriate default route is normally used in the routing instance. ISP2.inet.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 *[Static/1] 00:07:20, metric2 0 ##RPM/ip-monitoring > to 192.168.10.1 via ge-0/0/5.0 [Static/5] 00:00:01 ##static Default route > to 192.168.1.1 via ge-0/0/4.0
I have tried this,when the first ISP link is down it's working fine with the failover but when there is any issues from the ISP1 like routing it is not failing over the ISP 2 and internet is down and SRX is unreachable from our side
As soon as the RPM object no longer reaches the destination, the preferred route is set with "[Static/1] 00:03:03, metric2 0". The AD of 1 is therefore better than the normal static route with the value of 5. Accordingly, the backup path should be specified under preferred route. Otherwise, the appropriate default route is normally used in the routing instance.
ISP2.inet.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0 *[Static/1] 00:07:20, metric2 0 ##RPM/ip-monitoring
> to 192.168.10.1 via ge-0/0/5.0
[Static/5] 00:00:01 ##static Default route
> to 192.168.1.1 via ge-0/0/4.0
Bonjour et pour le retour à l’ISP23 une fois l’interface remontée vous faites comment ?
I have tried this,when the first ISP link is down it's working fine with the failover but when there is any issues from the ISP1 like routing it is not failing over the ISP 2 and internet is down and SRX is unreachable from our side
At least say something