10-28-2013 02:58 PM - edited 03-04-2019 09:26 PM
Hi community, I'm having this situation where we are migrating from a 7500 router to an ASR1004. The 7500 is working perfectly and establishing all of it's adjacencies with no problem whatsoever, but when we change the router to an ASR1004 we are experiencing problems in the way that one of the peers is not sending the routing update to it, refreshing the routes in the routing table every one minute. The configs are shown below:
7500 Router | ASR1004 | Failing peer IOS 15 |
---|---|---|
interface ATM4/1/0.77 point-to-point bandwidth 1984 ip address 192.168.1xx.xx 255.255.255.252 service-policy output QoS_CDS_Classify pvc XXXXXXXX 3/77 ubr 2234 no ilmi manage encapsulation aal5snap | interface ATM0/0/0.77 point-to-point bandwidth 1984 ip vrf forwarding XXXX_XX_XXX ip address 192.168.1xx.xx 255.255.255.252 no ip redirects no ip unreachables shutdown no atm enable-ilmi-trap pvc XXXXXX 3/77 ubr 2234 no ilmi manage encapsulation aal5snap | interface Serial0/0/0:0.16 point-to-point ip address 192.168.1xx.xx 255.255.255.252 ip redirects ip proxy-arp ip load-sharing per-destination ip cef accounting non-recursive internal ip flow ingress no snmp trap link-status frame-relay interface-dlci 16 |
router eigrp 1 variance 2 network 10.0.0.0 network 192.168.1xx.0 network 192.168.1xx.0 network 192.168.2xx.0 distribute-list CDS_Route-Dist out ATM4/1/0.1x distribute-list CDS_Route-Dist out ATM4/1/0.1x | router eigrp 1 ! address-family ipv4 vrf XXXX autonomous-system 1 variance 2 network 10.0.0.0 network 192.168.1xx.0 network 192.168.1xx.0 network 192.168.2xx.0 distribute-list XXXXXX out ATM0/0/0.1x distribute-list XXXXXX out ATM0/0/0.1x | router eigrp 1 network 10.0.0.0 network 192.168.1xx.0 network 192.168.1xx.0 |
-------- Retry Exceeded Log from ASR ---------
025310: Oct 26 00:08:01: EIGRP: Retransmission retry limit exceeded
025311: Oct 26 00:08:01: EIGRP: Holdtime expired
025312: Oct 26 00:08:01: Going down: Peer 192.168.1xx.xx total=38 stub 1, iidb-stub=0 iid-all=0
025313: Oct 26 00:08:01: EIGRP(4:1):[bfd_reg] state:2 iidb:AT0/0/0.7x peer:192.168.1xx.xx
025314: Oct 26 00:08:01: EIGRP: Handle deallocation failure [15]
025315: Oct 26 00:08:01: EIGRP: Neighbor 192.168.1xx.xx went down on ATM0/0/0.7x
025316: Oct 26 00:08:01: EIGRP: Packet from ourselves ignoredloggi
-------- Pending Routes in Remote Peer ---------
XXXXXX#show ip eigrp vrf XXXXXX interfaces
EIGRP-IPv4 Interfaces for AS(1) VRF(XXXX_XX_XXX)
Xmit Queue PeerQ Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable Un/Reliable SRTT Un/Reliable Flow Timer Routes
.
.
AT0/0/0.7x 1 0/0 0/0 5 0/36 56 0
AT0/0/0.7x 1 0/0 0/0 10 0/36 76 0
AT0/0/0.7x 1 0/0 0/1 14 0/36 92 594
.
.
-------- EIGRP Neighbors in ASR -------
EIGRP-IPv4 Neighbors for AS(1) VRF(XXXXXX)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
15 192.168.1xx.xx AT0/0/0.7x 208 00:00:31 14 5000 1 240996
I'm really shooting arrows here to see if I can get to the root of this problem. Am I hitting a bug? is this normal behaviour? is the problem in the remote peer? if so then why does it work with the first router?
Summarizing:
1. Adjacency for this neighbor lasts for one minute (hello timer or hold down didn't solve the issue)
2. Routes in routing table refresh every one minute.
3. Remote router has too many routes pending
Hope you guys can help me here.
Thank you
10-29-2013 12:22 PM
Anybody?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide