cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
649
Views
0
Helpful
0
Replies

CA on Router HA - 2901 issue

Daniel Freitas
Level 1
Level 1

Hello experts!


I'm working to implement a DMVPN scenario where the links use dynamic IP addressing.

Now I`m trying to bring up a CA on the routers of the company head quarters, and facing an issue where the devices are not able to establish the redundancy in the way it should.


The related setup is:


CHEF-01-RT-01#sh run | s ipc|redun|.1717

ipc zone default
association 1
no shutdown
protocol sctp
local-port 5000
local-ip 172.17.10.194
assoc-retransmit 20
remote-port 5000
remote-ip 172.17.10.195

!
redundancy inter-device
scheme standby HA
!

interface FastEthernet0/0/0.1717
description to R2-FastEthernet0/0/0.1717 - CA-HA
encapsulation dot1Q 1717
ip address 172.17.10.194 255.255.255.248
standby version 2
standby 12 ip 172.17.10.193
standby 12 priority 110

standby 12 name HA


CHEF-01-RT-02#sh run | s ipc|redun|.1717

ipc master 172.17.10.194
ipc zone default
association 1
no shutdown
protocol sctp
local-port 5000
local-ip 172.17.10.195
remote-port 5000
remote-ip 172.17.10.194

!
redundancy inter-device
scheme standby HA
!
interface FastEthernet0/0/0.1717
description to R1-FastEthernet0/0/0.1717 - CA-HA
encapsulation dot1Q 1717
ip address 172.17.10.195 255.255.255.248
standby version 2
standby 12 ip 172.17.10.193
standby 12 name HA

 

I`m using IOS c2900-universalk9-mz.SPA.157-3.M5.bin.


OK. With that in mind, my issue starts. When I bring the interface with the HSRP up, it starts to boot both routers, one each time. When the first one finish to boot, the second one starts. This seems to be related with the HSRP election process together with the SCTP protocol.

I was able to perform a workaround, by removing the HSRP address of the R2 and bringing the interface up and after configuring again the standby address. But if that routers boot, the boot loop will start on both routers again.

I also tried to disable the interfaces keepalive with the command "no keepalive", but got no success. Seems that this command is no longer able to keep the interface up with the peer down.

Any ideas how to solve this issue?


Thanks in advance!

 

0 Replies 0