EIGRP retry limit exceeded

Unanswered Question
Sep 17th, 2003

I am keep on getting "%DUAL-5-NBRCHANGE: IP-EIGRP 90: Neighbor 10.65.104.3 (Vlan118) is down: retry limit exceeded" from both VLAN 22 and VLAN 118.

There are total 22 VLANs in this MSFC, why only these 2 VLAN not holding the EIGRP neighbor?

I have tried shut and no shut on the VLAN interface, check the Spantree root, check the trunking... All looks fine???

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
deilert Wed, 09/17/2003 - 08:58

You have an issue with connectivity on these vlans , investigate all the switch ports on the vlans and inspect them for errors.

frank@networkex... Wed, 09/17/2003 - 09:44

The switches are connectd via trunk port, all 22 VLANs are through this trunked port.

The EIGRP neighbor just bouncing up and down for every minute or 2 for VLAN 22 and VLAN 118 only.

ruwhite Wed, 09/17/2003 - 10:53

This is a unicast failure, rather than a multicast or general failure.... Can you ping between these routers? Suppose you have two routers back to back:

A----B

A transmits some packet to B which must be acknowledged, multicast. B will acknowledge this packet using a unicast ack (actually, any packet sent back towards A can carry the ack). Assume that either the original multicast, or the ack, is lost. A sets a timer when it sends the original packet; once this timer expires, A retransmits this packet unicast just to B, and resets the timer.

If A attempts to transmit the packet 16 times, or through an entire dead interval, and never receives an ack, it will destroy the peer, and spit out the message you describe above.

From the frequency of the messages, it sounds like the inital hello, which is multicast, is getting through, but the next set of messages, which are unicast for the initial table exchange, are not. This would account for the two or three minute interval between bounces on each neighbor. I would bet that if you look at those bouncing neighbors, their RTO is always 5000.

The way to check on this is just to unicast ping to each neighbor, and see if it works. If it doesn't, you have a unicast failure in the link to those routers.

Russ.W

frank@networkex... Wed, 09/17/2003 - 13:57

Russ, You are right in the target... I can not ping each other (Funny thing is the HSRP is working between these 2 MSFC)

I have checked the layer 2, the trunk port 1/1 on both switch are forwarding both VLAN 22 and 118, but on the trunk port 2/1, only A switch forwarding VLAN 22 and 118, but B switch is blocking...

Is it possible ths unicast going out from switch A port 1/1 and coming back from switch B port 2/1 and since switch B port 2/1 is blocking so the packet got dropped?

ruwhite Wed, 09/17/2003 - 16:11

HSRP uses a multicast to see the routers in the group.... As weird as it sounds, I would start with a show ip route for each ip address you're trying to get to on each router, and make certain it actually points out the right interface, etc, before doing anything else. Then I'd make a list of the mac addresses of each of the interfaces from the arp cache, and compare them to the cef and arp caches on the other routers.

Next, I'd start considering the switching side of things.

Russ.W

frank@networkex... Thu, 09/18/2003 - 09:57

I did "sh ip arp" from both MSFC, the MAC are all match for.

Do know how to shoe the MAC from cef? I did "sh ip cef vlan 22 detail", not seeing the MAC but the neighbor are show as "valid cached adjacency"...

ruwhite Thu, 09/18/2003 - 10:32

It's in the output of show adj detail, or it should be:

2651A#sho adj detail

....

IP FastEthernet0/0 208.0.6.11(5)

0 packets, 0 bytes

0003E34866000003E34864A00800

ARP 00:08:32

Epoch: 0

Russ.W

frank@networkex... Fri, 09/19/2003 - 04:47

Here is the sh adj detail:

USMPSARLRMSFC#sh adj vlan 22 detail

Protocol Interface Address

IP Vlan22 vlan21hsrp.us.schp.com(5) (10.64.22.1)

0 packets, 0 bytes

00000C07AC16

0004C15496820800

ARP 03:23:52

Epoch: 0

IP Vlan22 USMPS01DRMSFC.us.schp.com(5) (10.64.22.2)

0 packets, 0 bytes

0004C1DEEBC2

0004C15496820800

ARP 03:23:52

Epoch: 0

USMPSARLRMSFC#sh ip arp 10.64.22.2

Protocol Address Age (min) Hardware Addr Type Interface

Internet 10.64.22.2 36 0004.c1de.ebc2 ARPA Vlan22

USMPSARLRMSFC#sh ip arp 10.64.22.1

Protocol Address Age (min) Hardware Addr Type Interface

Internet 10.64.22.1 36 0000.0c07.ac16 ARPA Vlan22

USMPSARLRMSFC#

USMPSARLRMSFC#sh adj vlan 118 detail

Protocol Interface Address

IP Vlan118 USMPS01DRMSFC.us.schp.com(5) (10.65.104.2)

5 packets, 355 bytes

0004C1DEEBC2

0004C15496820800

ARP 03:21:52

Epoch: 0

IP Vlan118 vlan118hsrp.us.schp.com(5) (10.65.104.1)

173 packets, 16891 bytes

00000C07AC76

0004C15496820800

ARP 03:21:52

Epoch: 0

IP Vlan118 mpsarp01d.us.schp.com(5) (10.65.104.105)

1 packets, 62 bytes

0050565A1A0F

0004C15496820800

ARP 03:51:19

Epoch: 0

USMPSARLRMSFC#sh ip arp 10.64.104.2

USMPSARLRMSFC#sh ip arp 10.64.104.1

USMPSARLRMSFC#sh ip arp 10.64.104.2

USMPSARLRMSFC#sh stand vlan118

Vlan118 - Group 118

Local state is Standby, priority 100, may preempt

Hellotime 3 sec, holdtime 10 sec

Next hello sent in 1.752

Virtual IP address is 10.65.104.1 configured

Active router is 10.65.104.2, priority 110 expires in 8.536

Standby router is local

1 state changes, last state change 1w1d

IP redundancy name is "hsrp-Vl118-118" (default)

USMPSARLRMSFC#sh ip arp 10.64.104.2

USMPSARLRMSFC#

The VLAN 22 matches the MAC, but VLAN 118 is not learning MAC???

HSRP still working???

USMPSARLRMSFC#sh ip eigrp nei

IP-EIGRP neighbors for process 90

H Address Interface Hold Uptime SRTT RTO Q Seq Type

(sec) (ms) Cnt Num

23 10.65.104.2 Vl118 11 00:00:08 1 4500 21 0

24 10.64.22.2 Vl22 14 00:00:59 1 5000 21 0

22 10.64.4.2 Vl1 12 3w6d 4 200 0 1651510

Both VLAN 22 and 118 are not forming the neighbor.

frank@networkex... Fri, 09/19/2003 - 04:56

Sorry, I was showing the wrong IP...

Here is the show for VLAN 118, all MAC are matching.

USMPSARLRMSFC#sh adj vl118 detail

Protocol Interface Address

IP Vlan118 USMPS01DRMSFC.us.schp.com(5) (10.65.104.2)

5 packets, 355 bytes

0004C1DEEBC2

0004C15496820800

ARP 03:12:40

Epoch: 0

IP Vlan118 vlan118hsrp.us.schp.com(5) (10.65.104.1)

173 packets, 16891 bytes

00000C07AC76

0004C15496820800

ARP 03:12:40

Epoch: 0

IP Vlan118 mpsarp01d.us.schp.com(5) (10.65.104.105)

1 packets, 62 bytes

0050565A1A0F

0004C15496820800

ARP 03:52:49

Epoch: 0

USMPSARLRMSFC#sh ip arp 10.65.104.2

Protocol Address Age (min) Hardware Addr Type Interface

Internet 10.65.104.2 47 0004.c1de.ebc2 ARPA Vlan118

USMPSARLRMSFC#sh ip arp 10.65.104.1

Protocol Address Age (min) Hardware Addr Type Interface

Internet 10.65.104.1 47 0000.0c07.ac76 ARPA Vlan118

USMPSARLRMSFC#

ruwhite Fri, 09/19/2003 - 06:10

The mac addresses look right--is vlan 118 the right vlan to reach this address? I assume it is. It sounds like you have some other problem which is blocking unicast. Check the return path on the other routers, as well.

Russ.W

Actions

Login or Register to take actions

This Discussion

Posted September 17, 2003 at 8:02 AM
Stats:
Replies:10 Overall Rating:
Views:732 Votes:0
Shares:0
Tags: No tags.