Dialers with HSRP

[tonyk0001]

Hi Team,   I hope this finds you well. I need some help, We have configured HSRP on WAN Routers but they all have dialers on them.   But when we trigger the fail over to the standby Router, The dialers don't come I think its because the tracking line protocol on the interfaces.   Please advise if there is something I can change.  

Regards

Tony Karera     

[Georg Pauwen]

Hello,

post the configs of your WAN routers so we can check and possible lab...

[tonyk0001]

Hi George,

interface GigabitEthernet0/0/0.2

 encapsulation dot1Q 2

 ip address 105.179.2.2 255.255.255.252

!

interface GigabitEthernet0/0/0.4

 encapsulation dot1Q 4

 ip address 10.42.1.20 255.255.255.0

 ip nat outside

!

interface GigabitEthernet0/0/0.8

 encapsulation dot1Q 8

!

interface GigabitEthernet0/0/0.9

 description JJJJ

 encapsulation dot1Q 9

 ip access-group 110 in

 ip access-group 110 out

 pppoe enable group global

 pppoe-client dial-pool-number 3

!

interface GigabitEthernet0/0/0.12

 description PPP

 encapsulation dot1Q 12

 no ip redirects

 no ip proxy-arp

 pppoe enable group global

 pppoe-client dial-pool-number 1

!

interface GigabitEthernet0/0/0.13

 description BBB

 encapsulation dot1Q 13

 ip nat outside

 pppoe enable group global

 pppoe-client dial-pool-number 2

 ip virtual-reassembly

 --More--         !

!

interface GigabitEthernet0/0/0.213

 description VPN

 encapsulation dot1Q 213

 ip address 192.168.213.1 255.255.255.0

!

interface GigabitEthernet0/0/0.247

!

interface GigabitEthernet0/0/0.2039

 encapsulation dot1Q 2039

 ip address 192.168.26.1 255.255.255.0

!

interface GigabitEthernet0/0/0.2087

 encapsulation dot1Q 2087

ip address 192.168.90.2 255.255.255.0

!

interface GigabitEthernet0/0/1

 ip address 192.168.50.2 255.255.255.0

 negotiation auto

!

interface GigabitEthernet0/0/2

 ip address 192.168.20.2 255.255.255.0

 ip nat outside

 negotiation auto

 crypto map dcp

 ip virtual-reassembly

!

interface GigabitEthernet0/0/3

 ip address 172.16.20.3 255.255.255.240

 ip nat inside

 standby 1 ip 172.16.20.4

 standby 1 priority 150

 standby 1 preempt

 standby 1 track 1 decrement 55

 negotiation auto

!

interface GigabitEthernet0

ip address 192.168.10.2 255.255.255.0

 negotiation auto

!

interface Vlan1

 no ip address

 shutdown

!

interface Dialer1

 bandwidth 100000

 bandwidth inherit 100000

 ip address negotiated

 ip mtu 1492

 ip nat inside

 encapsulation ppp

 dialer pool 1

 dialer-group 1

 ppp authentication pap callin

 ppp pap sent-username x.x.x.x password 7 x.x.x.x

!

interface Dialer2

 ip address negotiated

 ip mtu 1492

 --More--          ip nat outside

 encapsulation ppp

 dialer pool 2

 dialer-group 2

 ppp authentication pap callin

 ppp pap sent-username x.x.x. password 7 0x.x.x

 no cdp enable

 ip virtual-reassembly

!

interface Dialer3

 bandwidth 100000

 bandwidth inherit 100000

 ip address negotiated

 ip mtu 1492

 ip nat outside

 ip access-group 110 in

 ip access-group 110 out

 encapsulation ppp

 dialer pool 3

 dialer-group 3

 ppp authentication pap callin

 ppp pap sent-username x.x.x. password 0 x.x.x

 --More--          ip virtual-reassembly

track 1 interface GigabitEthernet0/0/0 line-protocol

[Georg Pauwen]

Hello,

the dialer interface stays up even when the physical interface is down, that might indeed be the problem.

Try a boolean, where both the physical and the dialer interface is being tracked, if either one is down, the tracked object is considered down:

track 1 interface GigabitEthernet0/0/0 line-protocol
!
track 2 interface Dialer1 line-protocol
!
track 3 list boolean and
object 1
object 2