cancel
Showing results for 
Search instead for 
Did you mean: 

Configure IP SLA + PBR

Configure IP SLA + PBR

SOUILAH_Mohamed
New Contributor
Hello,

I have to migrate from CISCO routers 1941 to Extreme X670, the routing configuration is as follows:
We have two outputs, one is for the business flow and the other is for the internet, if one link falls the other will replace it, for this we have to configure a PBR + SLA.
Here is the CISCO configuration:

************* Config Tracking *******************

track 100 ip sla 100
track 101 ip sla 101
track 150 list boolean or
object 100
object 101
track 300 ip sla 300
track 301 ip sla 301
track 350 list boolean or
object 300
object 301

************** Config SLA *********************

ip sla 100
icmp-echo 10.x.x.x source-interface Loopback2
threshold 1500
timeout 1500
frequency 2
ip sla schedule 100 life forever start-time now
ip sla 101
icmp-echo 10.x.x.x source-interface Loopback2
threshold 1500
timeout 1500
frequency 2
ip sla schedule 101 life forever start-time now
ip sla 300
icmp-echo 10.x.x.x source-interface Loopback1
threshold 1500
timeout 1500
frequency 2
ip sla schedule 300 life forever start-time now
ip sla 301
icmp-echo 10.x.x.x source-interface Loopback1
threshold 1500
timeout 1500
frequency 2
ip sla schedule 301 life forever start-time now

******************* Config Route-Map ********************

route-map FluxMetier deny 5
match ip address flux-intra-UP
!
route-map FluxMetier permit 10
match ip address DSCP-IN-D1INP
set ip next-hop verify-availability 172.x.x.x 1 track 350
!
route-map FluxMetier permit 20
match ip address DSCP-IN-D2INP
set ip next-hop verify-availability 172.x.x.x 1 track 350
!
route-map FluxMetier permit 40
match ip address inter-UP
set ip next-hop verify-availability 172.x.x.x 1 track 350
!
route-map FluxMetier permit 50
match ip address meca-up-LUG
set ip next-hop verify-availability 172.x.x.x 1 track 350
!
route-map STATIC-TO-OSPF permit 40
match tag 201
!

****************** Config Routage statique ****************

ip route 0.0.0.0 0.0.0.0 172.x.x.x 10 name Cxxx track 150
ip route 0.0.0.0 0.0.0.0 172.x.x.x 20 name Oxx track 350
ip route 10.x.x.x 255.255.255.255 172.x.x.x name UP-PBR-Mxxxxxx
ip route 10.x.x.x 255.255.255.255 172.x.x.x name UP-PBR-Mxxxxxx
ip route 10.x.x.x 255.255.255.255 172.x.x.x name UP-PBR-Cxxxxxxxx
ip route 10.x.x.x 255.255.255.255 172.x.x.x name UP-PBR-Cxxxxxxxx
ip route 172.x.x.x 255.255.255.0 172.x.x.x tag 201 name Ixxxxxx-Pxxxxxxxxxxx
!

My questions :

I am a beginner on ExtremeNetworks, and on the internet, I learned that to do this I have to write scripts, can you help me to write this script knowing that I never Written Scripts before (except ACL)

Thank you sincerely for your help, my situation is really critical and urgent.

Best regards.
10 REPLIES 10

Matthew_Helm1
Extreme Employee
Were it sufficient to simply use ICMP to the next-hop to verify the static route, one could avoid using scripting and instead use the ping-protection feature found in 16.2. Here is a link to the release notes.

It appears, however, that the SLA for each route is more complex, and that latency is used in addition to ICMP packet loss to determine that a static route is invalid. Is this true?

I can help with a script, but I need you to verify the exact conditions under which you need to determine that a static route is invalid.
GTM-P2G8KFN