01-27-2018 03:28 AM - edited 03-01-2019 02:03 PM
Dear All,
I have an issue with An EIGRP neighborship between two sites over a Metro Ethernet circuit. The EGRP keeps building up and get torn down on Site1 end of the WAN-link with the following logs. Site2 does not even try to build up EIGRP.
%DUAL-5-NBRCHANGE: EIGRP-IPv4 653: Neighbor 10.X.X.170 (GigabitEthernet0/1/0) is down: retry limit exceeded
%DUAL-5-NBRCHANGE: EIGRP-IPv4 653: Neighbor 10.X.X.170 (GigabitEthernet0/1/0) is up: new adjacency
%DUAL-5-NBRCHANGE: EIGRP-IPv4 653: Neighbor 10.X.X.170 (GigabitEthernet0/1/0) is down: retry limit exceeded
%DUAL-5-NBRCHANGE: EIGRP-IPv4 653: Neighbor 10.X.X.170 (GigabitEthernet0/1/0) is up: new adjacency
After some troubleshooting I found some weirdness. In Site1 I can resolve the MAC address of the opposite end via ARP, but on Site2 I get "Incomplete ARP. Also, when debuging EIGRP hellos, it turned out that on Site2 Hellos from Site1 are received, but the other way around the Hellos from Site2 are not arriving at Site1.
SITE1:
Site1#sh arp 10.X.X.170
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.X.X.170 0 XXXX.XXXX.XXXX ARPA GigabitEthernet0/1/0
Site1# sh log | i HELLO on Gi0/1/0
Jan 26 13:42:36.048 MET: EIGRP: Sending HELLO on Gi0/1/0 - paklen 20
Jan 26 13:42:37.652 MET: EIGRP: Received HELLO on Gi0/1/0 - paklen 20 nbr 10.X.X.170
SITE2:
Site2#sh arp | i 10.X.X.169
Internet 10.X.X.169 0 Incomplete ARPA
Site2# sh log | i HELLO on Gi0/1/0
Jan 26 13:41:17.633 MET: EIGRP: Sending HELLO on Gi0/1/0 - paklen 20
Jan 26 13:41:22.017 MET: EIGRP: Sending HELLO on Gi0/1/0 - paklen 20
Jan 26 13:41:26.881 MET: EIGRP: Sending HELLO on Gi0/1/0 - paklen 20
Jan 26 13:41:31.753 MET: EIGRP: Sending HELLO on Gi0/1/0 - paklen 20
Do you have idea what might be causing this strange one-way outage?
Thanks for your help in advance!
Bence Basa
Solved! Go to Solution.
02-04-2018 11:59 PM
Hi guys,
the provider has not found any issue on their circuit, but as a result of onsite tests on both ends they suspected an issue with the port or cabling on Site1. Cabling health was verified, so wedecided to replace the interface card which is a EHWIC-1GE-SFP-CU, the Metro link was connected to the bult-in copper port.
After replacement we could build up the connection between the two sites.
01-27-2018 10:52 AM
It sounds like you need to contact the service provider of your Metro-E circuit.
02-03-2018 09:41 AM
Hi,
Did you find the cause contacting your provider? Can you share it with the forum?
02-04-2018 11:59 PM
Hi guys,
the provider has not found any issue on their circuit, but as a result of onsite tests on both ends they suspected an issue with the port or cabling on Site1. Cabling health was verified, so wedecided to replace the interface card which is a EHWIC-1GE-SFP-CU, the Metro link was connected to the bult-in copper port.
After replacement we could build up the connection between the two sites.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: