EIGRP is trying to send updates with multicast and as it is not working it tries with unicast a certain amaount of time( retry limit) and as it is still not working it tears down the adjacency.It brings the adjacency up again and the same stuff happens again and again.
Can you provide a topology as well as the running config from the 2 neighbours.
I only have access to ISP router, so I cant see any logs in ISP router that is a neighbor of problematic router, And configuration of ISP router under the EIGRP and interface are fine...I didn't find any problem in the configuration, above logs are provided by the Customer that is apearing on there own devices...
And I dont have the access of customer devices...
But I tried to contact to customer and whenever I will get any update from the customer will post my updates..
Along with what Alain stated, check your duplex settings on the interface. I had this problem the other day and found that it was negotiated at half duplex. Once I changed that the neighbors came up without a problem.
If these logs are from the customer router then it suggests that they are receiving EIGRP hello messages from you that initiate the EIGRP neighbor process. Then they are trying to send updates to you but that they are not receiving EIGRP responses from you. I would suggest testing to see if there is any problem in connectivity. I would try ping to both the unicast and the 220.127.116.11 addresses of the customer specifying your connected interface as the source address. And I would suggest that they do the same test of pinging both your unicast and the multicast address.
Are you seeing any log messages on your router about this neighbor?
Thats the problem...Actually on ISP router I am not getting any logs related to the EIGRP...and We cant go beyond that..I mean cant ask customer about more information as I am unable to found any EIGRP logs on ISP device....
And the neighborship with the Customer router is OK.
Let me show.....the output from ISP routers---
Got the reply from all EIGRP neigbors---
Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 18.104.22.168, timeout is 2 seconds:
Reply to request 0 from 172.22.74.1, 1 ms Reply to request 0 from 172.31.192.202, 1 ms Reply to request 0 from 172.22.74.5, 1 ms
rtr-mpls-az-arbnr01#sh ip int br Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 172.22.74.2 YES NVRAM up up GigabitEthernet0/1 unassigned YES NVRAM up up GigabitEthernet0/1.2993 172.31.232.46 YES NVRAM up up FastEthernet0/2/0 unassigned YES unset up up FastEthernet0/2/1 unassigned YES unset administratively down down FastEthernet0/2/2 unassigned YES unset administratively down down FastEthernet0/2/3 unassigned YES unset administratively down down Serial0/0/0:0 unassigned YES NVRAM administratively down down Serial0/1/0:0 unassigned YES NVRAM administratively down down Vlan1 172.22.74.6 YES NVRAM up up Loopback10 22.214.171.124 YES NVRAM up up Loopback11 172.31.192.202 YES NVRAM up up
U can see Eigrp neigbor is up for more than 6weeks on ISP device--
rtr-mpls-az-arbnr01#ping 172.22.74.1 si 1000 re 100
Type escape sequence to abort. Sending 100, 1000-byte ICMP Echos to 172.22.74.1, timeout is 2 seconds: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/8 ms
No EIGRP logs on device--
May 17 14:57:44.114 BST: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 4% and 1: 4%
May 17 14:58:14.651 BST: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 4% and 1: 3%
May 17 15:23:34.780 BST: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 3% and 1: 3%
May 17 15:28:39.886 BST: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 4% and 1: 3%
May 17 15:29:10.455 BST: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 4% and 1: 3%
EIGRP Config on ISP Router
router eigrp 100
redistribute static route-map static-to-eigrp
network 10.130.98.0 0.0.0.255
network 172.22.1.0 0.0.0.255
network 172.22.74.0 0.0.0.3
network 172.22.74.4 0.0.0.3
network 172.31.192.202 0.0.0.0
Now pls suggest everything working fine over here...now Wat I need to do??
Thank you for the additional information. I am confused about what is going on. The error message in your original post specifies that the neighbor address is 172.22.74.6. And from the new information that you provide that would be the address on vlan 1. But the EIGRP output that you sent says that the neighbor is on Gig0/0. If the neighbor is on Gig0/0 how are they seeing hello messages from 172.22.74.6 on vlan 1? Perhaps more detail of how your router is configured might be helpful.
Are you saying that you see no log messages from EIGRP at all or just that there are no log messages about this neighbor? If there are no log messages for EIGRP at all then the logging may be disabled. You might try this command under router eigrp and see if it produces log messages
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...