cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
562
Views
5
Helpful
2
Replies

DMVPN Tunnel Phase 1 with EIGRP

Hi Friends,

i have problem with this Tunnel, it's a DMVPN Tunnel and the Routers Running EIGRP over the Tunnel.

 

The Problem is that this tunnel goes down once or twice a day !!! BUT not every day and not same time.

Here are a output from the two routers:

R1#show run interface tunnel 0
Building configuration...

Current configuration : 290 bytes
!
interface Tunnel0
 bandwidth 1000
 ip address 10.0.2.1 255.255.255.0
 no ip redirects
 ip mtu 1400
 ip nhrp authentication XXXXXX
 ip nhrp map multicast dynamic
 ip nhrp network-id 1
 ip tcp adjust-mss 1360
 keepalive 9 3
 cdp enable
 tunnel source BVI1
 tunnel mode gre multipoint
end

 

R1#show run | section eigrp
router eigrp 100
 network 10.0.0.0 0.0.0.255
 network 10.0.2.0 0.0.0.255
 network 192.168.1.0
 no auto-summary

 

 

R1#show ip eigrp 100 neighbors
IP-EIGRP neighbors for process 100
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   10.0.2.2                Tu0               11 00:03:45   40   240  0  7004

 

 

R1#show logging | begin Nov 26

Nov 27 04:54:52.702: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.2 (Tunnel0) is down: holding time expired

 

Nov 27 04:55:20.427: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to up
Nov 27 04:55:33.638: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.2 (Tunnel0) is up: new adjacency

 

Nov 27 13:53:10.325: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.2 (Tunnel0) is down: holding time expired
Nov 27 13:53:36.179: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to up

 

Nov 27 13:53:39.074: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to up
Nov 27 13:54:36.393: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.2 (Tunnel0) is up: new adjacency

 

There is also other errors i don't know it's for the same problem or not.Nov 29 12:18:27.024: %CALLRECORD-3-SCM_TERSE_CALL_REC: slot/wic-slot/port=0/1/0,calling=n/a,called=n/a,std=V34,prot=LAPM,comp=V42B,finl-rx/tx b-rate=4800/21600,time=308,disc(local)=0  User Hangup

Nov 29 13:32:45.340: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=A.A.A.126, prot=50, spi=0xC0558AC(201676972), srcaddr=B.B.B.9
Nov 29 15:49:50.320: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=A.A.A.126, prot=50, spi=0x65007446(1694528582), srcaddr=B.B.B.9
Nov 29 15:52:50.790: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=A.A.A.126, prot=50, spi=0x4500E5F3(1157686771), srcaddr=B.B.B.9

 

 

R2#show run interface tunnel 0
Building configuration...

Current configuration : 357 bytes
!
interface Tunnel0
 bandwidth 1000
 ip address 10.0.2.2 255.255.255.0
 ip mtu 1400
 ip nhrp authentication XXXXXX
 ip nhrp map 10.0.2.1 A.A.A.126
 ip nhrp map multicast A.A.A.126
 ip nhrp network-id 1
 ip nhrp nhs 10.0.2.1
 ip tcp adjust-mss 1360
 keepalive 9 3
 cdp enable
 tunnel source FastEthernet0/1
 tunnel destination A.A.A.126
end

 

R2#show run | section eigrp 100
router eigrp 100
 network 10.0.1.2 0.0.0.0
 network 10.0.2.0 0.0.0.255
 network 172.16.1.0 0.0.0.255
 no auto-summary

 

R2#show ip eigrp neighbors
IP-EIGRP neighbors for process 100
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   10.0.2.1                Tu0               12 00:04:41 1035  5000  0  278

 

R2#show logging | begin Nov 26

 

Nov 27 04:54:52.570: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.1 (Tunnel0) is down: holding time expired
Nov 27 04:55:12.960: %TRACKING-5-STATE: 1 interface Tu0 line-protocol Up->Down
Nov 27 04:55:13.664: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down

Nov 27 04:55:30.958: %TRACKING-5-STATE: 1 interface Tu0 line-protocol Down->Up
Nov 27 04:55:31.662: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
Nov 27 04:55:33.662: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.1 (Tunnel0) is up: new adjacency
Nov 27 04:58:47.480: SSH2 3: Unexpected message received

 

 

 

Nov 27 13:53:09.287: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.1 (Tunnel0) is down: holding time expired
Nov 27 13:53:31.857: %TRACKING-5-STATE: 1 interface Tu0 line-protocol Up->Down
Nov 27 13:53:31.941: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down

 

Nov 27 13:54:33.947: %TRACKING-5-STATE: 1 interface Tu0 line-protocol Down->Up
Nov 27 13:54:34.935: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
Nov 27 13:54:36.415: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.0.2.1 (Tunnel0) is up: new adjacency

 

There is also other errors i don't know it's for the same problem or not.

Nov 27 13:58:45.627: %CALLRECORD-3-SCM_TERSE_CALL_REC: slot/wic-slot/port=0/1/0,calling=n/a,called=n/a,std=V34,prot=LAPM,comp=V42B,finl-rx/tx b-rate=28800/19200,time=310,disc(local)=C  Remote Hangup
Nov 27 14:19:52.902: SSH2 3: Unexpected mesg type received
Nov 27 16:53:25.059: SSH2 5: Unexpected mesg type received
Nov 27 19:14:09.302: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=B.B.B.9, prot=50, spi=0x984EAB85(2555292549), srcaddr=A.A.A.126
Nov 27 19:36:52.204: SSH2 0: Unexpected mesg type received

 

 

 

 

2 Replies 2

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

According to this Q&A, this maybe a layer-1 or layer-2 issue. 

Q. What does the %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.254.0.3 (Tunnel0) is down: holding time expired error message mean?

 

A. This message indicates that the router has not heard any EIGRP packets from the neighbor within the hold-time limit. Because this is a packet-loss issue, check for a Layer 2 problem.

link:

http://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/13681-eigrpfaq.html#err-msg

HTH

hi Reza Sharifi ,

 

Thanks for the help i added the following configuration to the Routers:

R1 & R2:

Interface Tunnel0

 ip hello-interval eigrp 100 60

 ip hold-time eigrp 100 300

 

in this case it will have to miss 5 hello to declare the neighbor dead.

i will let you know if this fixed the problem or not.

 

Best Regards

Sensie

Getting Started

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:

Review Cisco Networking products for a $25 gift card