RE: Troubleshooting EIGRP Neighbor Flapping

From: Reza Toghraee (reza@toghraee.com)
Date: Tue Oct 14 2008 - 16:44:32 ART


Put "no keepalive" on R6 Serial 0/0/0
It will fix. Since the R6 to BB1 connection is direct by default.

Reza

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Sachin D
Sent: Tuesday, October 14, 2008 11:23 PM
To: Cisco certification
Subject: Troubleshooting EIGRP Neighbor Flapping

Hi Guys,

I am facing EIGRP neighbor flapping for one of my lab, There is no
reachability issue between the 2 neighbors hence physical cabling issues are
ruled out. Scanned google all steps mention there in troubleshooting are
verified for me

Below is the topology and problem, hope some one can help me on some
troubleshooting steps or problem I am facing

--------- --------------------
----------------
| R6 |______________| FR Cloud |_________| BB1 |
---------P2MP Phy int ------- 2P Sub int
--------------

Checked all K values at both the ends and they are matching

R6 Configs

R6#sh run int s0/0/0
Building configuration...

Current configuration : 154 bytes
!
interface Serial0/0/0
 ip address 54.1.2.6 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 54.1.2.254 100
 no frame-relay inverse-arp
end

R6#

R6#sh run | s eigrp
router eigrp 10
 network 54.1.2.6 0.0.0.0
 network 150.1.6.6 0.0.0.0
 no auto-summary
R6#

BB Configurations

interface Serial0/0/0.100 point-to-point
 description PVC 100 to Rack1
 ip address 54.1.2.254 255.255.255.0
 ipv6 address 2001:54:1:2::254/64
 ipv6 address FE80::254 link-local
 frame-relay interface-dlci 100
!

router eigrp 10
 network 54.0.0.0
 network 200.0.0.0 0.0.3.255
 distribute-list EIGRP out
 distribute-list prefix DENY_DEFAULT in
 no auto-summary
 no eigrp log-neighbor-changes
 no eigrp log-neighbor-warnings

BB1#sh ip prefix-list DENY_DEFAULT
ip prefix-list DENY_DEFAULT: 2 entries
   seq 5 deny 0.0.0.0/0
   seq 10 permit 0.0.0.0/0 le 32
BB1#

BB1#sh ip access-lists EIGRP
Standard IP access list EIGRP
    10 permit 200.0.0.0, wildcard bits 0.0.3.255

BB1#sh ip protocols
Routing Protocol is "eigrp 10"
  Outgoing update filter list for all interfaces is EIGRP
  Incoming update filter list for all interfaces is (prefix-list)
DENY_DEFAULT
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  EIGRP maximum hopcount 100
  EIGRP maximum metric variance 1
  Redistributing: eigrp 10
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    54.0.0.0
    200.0.0.0/22
  Routing Information Sources:
    Gateway Distance Last Update
  Distance: internal 90 external 170

R6#sh ip protocols
Routing Protocol is "eigrp 10"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  EIGRP maximum hopcount 100
  EIGRP maximum metric variance 1
  Redistributing: eigrp 10
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    54.1.2.6/32
    150.1.6.6/32
  Routing Information Sources:
    Gateway Distance Last Update
    (this router) 90 00:04:57
  Distance: internal 90 external 170

R6#

Error Messages

*Oct 14 19:28:19.195: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is down: retry limit exceeded
R6#
*Oct 14 19:28:23.403: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is up: new adjacency
R6#
*Oct 14 19:29:42.915: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is down: retry limit exceeded
*Oct 14 19:29:43.107: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is up: new adjacency
R6#
*Oct 14 19:31:02.619: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is down: retry limit exceeded
R6#
*Oct 14 19:31:06.867: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is up: new adjacenc

*REACHABILITY TEST (Can ping the neighbo while adjacancy goes down)

*R6#ping 54.1.2.254 repeat 10000

Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 54.1.2.254, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

*Oct 14 19:00:05.023: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is down: retry limit
exceeded!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*Oct 14 19:00:08.311: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
54.1.2.254(Serial0/0/0) is up: new adjacency!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
Success rate is 99 percent (1389/1390), round-trip min/avg/max = 56/57/304
ms

Checked MTU size on both interfaces same

R6#sh int s0/0/0
Serial0/0/0 is up, line protocol is up
  Hardware is GT96K Serial
  Internet address is 54.1.2.6/24
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

BB1#sh int s0/0/0
Serial0/0/0 is up, line protocol is up
  Hardware is GT96K Serial
  Description: Serial to FRS
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

Regards
*
*

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:21 ARST