From: Jason Guy \(jguy\) (jguy@cisco.com)
Date: Wed Jul 18 2007 - 12:26:57 ART
Are you doing GRE+IPsec, or DMVPN?
Make sure the tunnel destination or source address is not getting
advertised via eigrp over the tunnel. I have seen this problem in my
own stuff and it causes the tunnel to bounce repeatedly. I agree, the
f0/0 interface should not matter here since it is not involved with the
tunnel (unless you are unnumbered to the f0/0 and it is flapping).
Jason
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Phillip McCollum
> Sent: Wednesday, July 18, 2007 10:35 AM
> To: ccielab@groupstudy.com
> Subject: EIGRP Neighbor Flap
>
> Hi folks,
>
> I've been going back and forth with an issue on my ISP's managed
network
> and
> wanted to seek some expert advice. The setup is as follows:
>
> <switch>---<fa0/0>[spoke router]<s0/0 w/3 tunnel interfaces>======(ISP
> Cloud)EIGRP========<s0/0 w/tunnel interface><hub router>
>
> As you can see, EIGRP is running inside of an IPSec tunnel. 2 tunnels
go
> to
> a primary hub router and 1 tunnel goes to a backup hub router.
> Intermittently, I will get messages in the logs as follows (IP
addresses
> changed for privacy):
>
> Jul 17 11:56:17.790 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is down: holding time expired
> Jul 17 11:56:17.794 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: holding time expired
> Jul 17 11:56:17.798 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: holding time expired
> Jul 17 11:56:17.830 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is up: new adjacency
> Jul 17 11:56:17.838 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 11:56:17.838 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
> Jul 17 11:56:17.838 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: Interface Goodbye received
> Jul 17 11:56:17.838 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is down: Interface Goodbye received
> Jul 17 11:56:17.838 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: Interface Goodbye received
> Jul 17 11:56:17.842 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 11:56:17.842 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is up: new adjacency
> Jul 17 11:56:17.842 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
> Jul 17 11:56:17.897 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: peer restarted
> Jul 17 11:56:17.909 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: peer restarted
> Jul 17 11:56:22.481 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
> Jul 17 11:56:22.773 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 16:42:02.131 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: holding time expired
> Jul 17 16:42:02.135 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is down: holding time expired
> Jul 17 16:42:02.135 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: holding time expired
> Jul 17 16:42:02.183 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 16:42:02.183 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is up: new adjacency
> Jul 17 16:42:02.211 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
> Jul 17 16:42:02.211 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: Interface Goodbye received
> Jul 17 16:42:02.211 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: Interface Goodbye received
> Jul 17 16:42:02.215 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is down: Interface Goodbye received
> Jul 17 16:42:02.215 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 16:42:02.215 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
> Jul 17 16:42:02.215 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is up: new adjacency
> Jul 17 16:42:17.214 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is down: holding time expired
> Jul 17 16:42:17.214 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is down: holding time expired
> Jul 17 16:42:17.214 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is down: holding time expired
> Jul 17 16:42:53.211 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 2.2.2.2(Tunnel1) is up: new adjacency
> Jul 17 16:42:54.859 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 1.1.1.1 (Tunnel0) is up: new adjacency
> Jul 17 16:42:59.503 GMT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> 3.3.3.3 (Tunnel2) is up: new adjacency
>
>
>
>
> Now, the provider keeps pointing the finger back at possible issues on
the
> Fa0/0 interface causing this. I'm thinking it doesn't matter what's
> happening on the Fa0/0 interface. This neighbor relationship is
between
> the
> s0/0 interface of the spoke and There is no flapping on any interface
> (tunnel, serial, or fast Ethernet) and all stats are clean with
regards to
> line errors, etc.
>
> So my question is. Am I crazy for thinking this has nothing to do with
> anything on the Fa0/0 side???
>
> Hope this makes some sense. Thanks in advance folks!
>
> Phillip
>
>
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:41 ART