Re: Problem with sla tracking from Dialer Interface

mani98765 · ‎12-23-2015

Hello,

I would like to build a backup route, if my dsl line fails.

So I made a sla tracking on my dns server with source interface Dialer 1 and made a route with the tracking activated.

My problem is, that if I have this activated, I can't ping from Dialer 1 interface to my DNS Server, it seams, that it uses my backup route, instead of the source interface Dialer 1.

Have you got any idea, how to solve this problem?

Thank you

Manuel

EDIT:

If I make a static route to my DNS over Dialer 1, everything works fine. But so it seems, that even if I ping with source Dialer 1, it first looks into the routing table, and it don't choose the way over Dialer 1, it takes the way over my Backup route. How can I make this right, so it sends the ping out of Dialer 1, without have a look into the routing table?

Richard Bradfield · ‎12-23-2015

please post relevant configuration

mani98765 · ‎12-23-2015

Hello, this is the relevant configuration:

If the track is down, it pings via the backup route to the dns server, so if my backup is down and my main route is up, it will never switch back to the main route to my ISP.

track 1 ip sla 1 reachability
!
interface Dialer1
ip address negotiated
ip access-group WANin in
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication chap callin
ppp chap hostname *******
ppp chap password *******
!
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 192.168.0.253 10
!
ip nat inside source list NATLIST interface Dialer1 overload
!
ip access-list standard NATLIST
permit 192.168.0.0 0.0.0.255
deny any log
ip access-list standard TELNET
permit 192.168.0.0 0.0.0.255
deny any log
!
ip access-list extended LANin
permit ip 192.168.0.0 0.0.0.255 any
permit udp any eq bootpc any eq bootps
!
ip sla 1
icmp-echo 213.33.99.70 source-interface Dialer1
timeout 1000
threshold 2
frequency 3
ip sla schedule 1 life forever start-time now
dialer-list 1 protocol ip permit

Richard Bradfield · ‎11-02-2016

Hi,

I don't know how you fixed this problem. but see link below for new command on the dialer interface to overcome this

http://www.cisco.com/c/en/us/support/docs/wan/point-to-point-protocol-ppp/200466-Track-PPP-session-over-Dialer-interface.html

GIANRICO FICHERA · ‎10-10-2022

A solution could be to use the command:

dialer down-with-vInterface

if available.
A different solution is to track the protocol status of the Dialer1 interface, given that the Dialer1 interface is always up:

track 10 interface Dialer1 ip routing
   delay down 5 up 30
!
ip route 0.0.0.0 0.0.0.0 Dialer1 track 10
ip route 0.0.0.0 0.0.0.0 192.168.0.253 200

Gianrico Fichera
ITESYS SRL

Chosebin · ‎03-17-2023

So many days of reading and finally found this short thread with the right answer! Richard get's right but it MUST be used with the Gianrico's track 10 interface Dialer1 ip routing to works correctly. Tested with Bell Canada's Fibe pppoe. Thank you guys.