ISSUE: eigrp neighborship is flapping between DM VPN Spoke (10.13.0.18) and Hub router (10.13.0.1). I need your inputs in troubleshooting this.
Please let me know if you need more details
The tunnel state is up and up .
Crypto isakmp state is QM_IDLE.
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.13.0.1 (Tunnel1) is down: Peer goodbye received %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.13.0.1 (Tunnel1) is up: new adjacency %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.13.0.1 (Tunnel1) is down: Peer goodbye received %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.13.0.1 (Tunnel1) is up: new adjacency %ADJ-5-PARENT: Midchain parent maintenance for IP midchain out of Tunnel1, addr 10.13.0.1 841471C0 - looped chain attempting to stack %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.13.0.1 (Tunnel1) is down: holding time expired
on 10.13.0.18, the tunnel config is
ip address 10.13.0.18 255.255.0.0
no ip redirects
ip mtu 1400
ip nhrp authentication 111
ip nhrp map multicast dynamic
ip nhrp map 10.13.0.1 188.8.131.52
ip nhrp map multicast 184.108.40.206
ip nhrp network-id 101
ip nhrp nhs 10.13.0.1
ip nhrp cache non-authoritative
ip summary-address eigrp 1 220.127.116.11 255.255.254.0 5
Goodbye received indicates the neighbor declared us down. What does the other side of the tunnel see?
Are you seeing Input Queue drops or high CPU? These could be symptoms of overutilization on the device.
Finally you haven't set the bandwidth on the tunnel interface here, meaning that EIGRP thinks it can only use 50% of 4kb for packets. I'm assuming your physical connectivity is greater than 8kbps. I would suggest increasing the "eigrp bandwidth-percent" command to something over 100% so that it is equal to 50% of your physical or increase the tunnel bandwidth to match the physical CIR.
Success rate is 96 percent (812/840), round-trip min/avg/max = 1/1/20 ms
Please note during the packet loss, the eigrp neighborship is up.
Worked with AT&T to find out if this is an ISP issue. Replaced the cable between router and the modem. NO LUCK.
Worked with Cisco and identified there is a routing loop with the help of debug outputs (attached). Implemented an inbound distribute list (attached) on Tiffin backup router to filter out the duplicate routes and tunnel came up.
The ip address for fa 4 interface of TIFFABWBR1 is 18.104.22.168.
We have a static route pointing on GRV hub router towards Tiffin.
GRVVPNCR2#show run | i 22.214.171.124
ip route 126.96.36.199 255.255.255.255 188.8.131.52
This same route is being redistributed on HUB and advertised to spoke router which has caused this issue.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.