My router has lost its eigrp neighbor relationship so has lost all its routing information even though I can ping the neighbor address from the router. All interfaces are up.
I have tried restarting the router.
Its neighbor has the following logs
Aug 20 12:22:31.855: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 10.128.34.9 (Vlan
8) is down: retry limit exceeded
Aug 20 12:22:32.947: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 10.128.34.9 (Vlan
8) is up: new adjacency
I have tried the clear ip eigrp neighbor 10.128.34.9 from the routers neighbor.
Any help much appreciated.
Is this happening often or is it a one off ?
There are a number of reasons why this could be happening, start with this doc and see if it helps -
I'm assuming you haven't made any changes recently eg. new acls etc..
Yes its happening alot. No changes have been made although when I logged on to the router debugging was enabled which i have now turned off.
Any debugging can put an overhead on the router and the more general the more overhead. The router may have been so busy handling the debugging it could not process the EIGRP hellos in time and so the EIGRP adjacency went down.
Have you lost the adjacency since you turned off debugging ?
No its still happening. The logs stamps 1 hour behind so I thought it had stopped initially. The router is connected to a switch stack. The switch stack has a connection to each core switch. the core switch have a vlan which is the routers eigrp neighbor
Can you check all your devices to make sure none of them have debugging turned on. Then go through that document to see if any of it applies to your scenario.
EIGRP neighbors lose adjacency when they miss a certain number of hello's. So you need to check both your core devices, the router itself and the switch stack to make sure you have no bottlenecks anywhere.
Our core switches show the router in its list of eigrp neighbors.
The router doesn't have any eigrp neighbors.
What about the path it takes, have you tested it?
Send 5000 pings with a datagram of 1500 and what are the results?
Please do the ping test as Kevin suggested. Also, allow me a couple of questions:
1.) Did this problem come just out-of-blue, or were there any changes implemented in the network, no matter how insignificant?
2.) How many EIGRP neighbors should the router 10.128.34.9 have? Do all these neighbors report flapping adjacencies or only some of them?
3.) Is there any EIGRP authentication in place?
4.) Can you please post the configuration of the EIGRP process and the Vlan8 interfaces of both the router 10.128.34.9 and its neighbor?
Does it try resetting the EIGRP neighbor every 120 seconds or so? If so, then the problem you may be experiencing is related to a multicast issue between the router and its' neighbor. EIGRP uses multicast packets to communicate with neighbors.
To confirm whether it is a multicast issue that is affecting your peering, try defining your EIGRP neighbors explicitly on the two peers (using the 'neighbor' command within router eigrp config). By explicitly defining your neighbors, they will communicate using unicast packets, thus eliminating multicast problems as a potential cause.
I had this problem with EIGRP peering over a Metro Ethernet connection. The provider later confirmed that a bug in their ME equipment was affecting multicast communication.
Hope this helps.
>>I logged on to the router debugging was enabled which i have now turned off.
On top of what everyone else has said, when you noticed someone else had debugging on...what it for eigrp? Possibly someone else was ts'g the problem already and you could save time depending on the size of your org by asking around. If not, then if they had debugging on then maybe they were troubleshooting a differenet problem and during the rucus, did something to cause your EIGRP to have fits. You probably already thought about this, but figure I would throw it in.
Cheers and good luck,