IP SLA AND STATIC ROUTE CONFLICT ICMPECHO RESPONSE
Hello, can somebody help use to resolve this problem between IPSLA and static router ICMPECHO?.
We have a central site with a main router 7206VXR.
This router is connected to an IPVPN Cloud using MPLS routing so many remote sites can communicate with it.
There is a remote site (10.60.1.0 / 24) that reach the central site through another carrier.
If we want to reach the remote site from the main router, we use the static route:
ip route 10.60.1.0 255.255.255.0 10.1.200.132, where 10.1.200.132 is the switch where the remote site reach the central site.
This static route is announced to IPVPN Cloud using prefix-list, route-map and redistribute static at BGP routing protocol.
What we want is to denegate the announcement of this static route if the remote site (10.60.1.10 / 24) is unreachable.
We are using the IP SLA to reach this result but the problem is that the address: 10.1.200.132 does never goes DOWN.
If we keep this static route and use another like that: ip route 10.60.1.0 255.255.255.0 10.60.1.155 always the first take precedence.
If we delete the static route: ip route 10.60.1.0 255.255.255.0 10.1.200.132 the remote site is unreachable and we lost connection.
The commands we use are:
track 123 ip sla 1 reachability
ip route 10.60.1.0 255.255.255.0 10.1.200.132 240 track 123
ip sla 1 icmp-echo 10.1.200.132 source-interface GigabitEthernet0/1 timeout 1000 threshold 2 frequency 3 ip sla schedule 1 life forever start-time now
! ip prefix-list ARRIOLA seq 5 permit 10.110.0.0/16 ! ip prefix-list DEFAULT seq 5 permit 0.0.0.0/0 ! ip prefix-list DMZ seq 5 permit 192.168.104.200/32 ip prefix-list DMZ seq 10 permit 192.168.104.101/32 ip prefix-list DMZ seq 15 permit 192.168.104.110/32 ip prefix-list DMZ seq 20 permit 192.168.104.0/24 ! ip prefix-list TELMEX seq 5 permit 10.60.1.0/24
! route-map ESTATICAS permit 10 match ip address prefix-list ARRIOLA ! route-map ESTATICAS permit 15 match ip address prefix-list DMZ ! route-map ESTATICAS permit 20 match ip address prefix-list DEFAULT set community 6147:70 6147:100 ! route-map ESTATICAS permit 30 match ip address prefix-list TELMEX set community 6147:90 ! route-map ESTATICAS permit 40 set community 6147:70 !
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.