From: Shine Joseph (shinepjoseph@iprimus.com.au)
Date: Thu Mar 20 2008 - 02:17:42 ART
Moe,
That's good.
Can you swap the DTE/DCE side and apply the clock on FR switch rather than
on the router. See it if that makes a difference. I strongly suspect that.
Regards,
Shine
_____
From: cisco-addicted [mailto:cisco.addicted@gmail.com]
Sent: Thursday, 20 March 2008 3:49 PM
To: 'Shine Joseph'; 'But Nicky'; 'Rik Guyler'; surendratk@hotmail.com;
'Jonathan Greenwood II'
Cc: 'Adel Karim'; 'Envuladu Tsaku'; steveaggie@gmail.com; 'Cisco
certification'
Subject: RE: EIGRP adjacency Flapping
Dear,
The clock rate on R2 serial because I connected the DCE cable from R2 side
not the FRSW. Is this a problem?? Should all the FRSW be the DCE and the
other routers be DTE??
And by the way the ping from all the three routers on the FR interfaces
working fine, but when I tried to use the broadcast address; only R2 was
able to ping both spokes.
The good news that after configuring the neighbor command between them, the
adjacency worked fine ;). But what was the cause of the problem????? What if
they asked me not to use this command ???
With all regards
Moe
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Rack1R1#ping 183.1.123.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Rack1R1#
Rack1R1#
Rack1R1#ping 183.1.123.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/112/112 ms
Rack1R1#
Rack1R1#
Rack1R1#
Rack1R1#ping 183.1.123.255
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.255, timeout is 2 seconds:
Reply to request 0 from 183.1.123.2, 84 ms
Reply to request 1 from 183.1.123.2, 84 ms
Reply to request 2 from 183.1.123.2, 84 ms
Reply to request 3 from 183.1.123.2, 84 ms
Reply to request 4 from 183.1.123.2, 84 ms
Rack1R1#
Rack1R1#
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1 R2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Rack1R2#
Rack1R2#ping 183.1.123.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Rack1R2#
Rack1R2#
Rack1R2#ping 183.1.123.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#ping 183.1.123.255
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.255, timeout is 2 seconds:
Reply to request 0 from 183.1.123.3, 128 ms
Reply to request 0 from 183.1.123.1, 140 ms
Reply to request 1 from 183.1.123.3, 128 ms
Reply to request 1 from 183.1.123.1, 140 ms
Reply to request 2 from 183.1.123.3, 128 ms
Reply to request 2 from 183.1.123.1, 140 ms
Reply to request 3 from 183.1.123.3, 128 ms
Reply to request 3 from 183.1.123.1, 140 ms
Reply to request 4 from 183.1.123.3, 128 ms
Reply to request 4 from 183.1.123.1, 140 ms
Rack1R2#
Rack1R2#
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R3
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Rack1R3#
Rack1R3#
Rack1R3#ping 183.1.123.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/113/120 ms
Rack1R3#
Rack1R3#
Rack1R3#
Rack1R3#ping 183.1.123.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Rack1R3#
Rack1R3#
Rack1R3#
Rack1R3#ping 183.1.123.255
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 183.1.123.255, timeout is 2 seconds:
Reply to request 0 from 183.1.123.2, 144 ms
Reply to request 1 from 183.1.123.2, 144 ms
Reply to request 2 from 183.1.123.2, 144 ms
Reply to request 3 from 183.1.123.2, 144 ms
Reply to request 4 from 183.1.123.2, 144 ms
Rack1R3#
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Rack1R1#sh fram ma
Serial0/2/0 (up): ip 183.1.123.3 dlci 102(0x66,0x1860), static,
CISCO, status defined, active
Serial0/2/0 (up): ip 183.1.123.2 dlci 102(0x66,0x1860), static,
broadcast,
CISCO, status defined, active
Rack1R1#
Rack1R1#
Rack1R1#
Rack1R1#
RDC-NOD-TS#2
[Resuming connection 2 to r2 ... ]
f
% Ambiguous command: "f"
Rack1R2#
Rack1R2#
Rack1R2#sh fram ma
Serial0/2/0 (up): ip 183.1.123.1 dlci 201(0xC9,0x3090), static,
broadcast,
CISCO, status defined, active
Serial0/2/0 (up): ip 183.1.123.3 dlci 203(0xCB,0x30B0), static,
broadcast,
CISCO, status defined, active
Rack1R2#
Rack1R2#
Rack1R2#
RDC-NOD-TS#3
[Resuming connection 3 to r3 ... ]
Rack1R3#
Rack1R3#sh fram ma
Serial1/0 (up): ip 183.1.123.1 dlci 302(0x12E,0x48E0), static,
CISCO, status defined, active
Serial1/0 (up): ip 183.1.123.2 dlci 302(0x12E,0x48E0), static,
broadcast,
CISCO, status defined, active
Serial1/1 (up): ip 183.1.0.4 dlci 315(0x13B,0x4CB0), static,
CISCO, status defined, active
Serial1/1 (up): ip 183.1.0.5 dlci 315(0x13B,0x4CB0), static,
broadcast,
CISCO, status defined, active
Rack1R3#
Rack1R3#
From: Shine Joseph [mailto:shinepjoseph@iprimus.com.au]
Sent: Thursday, March 20, 2008 6:54 AM
To: 'cisco-addicted'; 'But Nicky'; 'Rik Guyler'; surendratk@hotmail.com;
'Jonathan Greenwood II'
Cc: 'Adel Karim'; 'Envuladu Tsaku'; steveaggie@gmail.com; 'Cisco
certification'
Subject: RE: EIGRP adjacency Flapping
Hi Cisco-addicted,
I am wondering why/how you have a clock rate set on R2?
Can you get the frame-relay map output from all the three switches? Before
doubting an IOS bug or FR switch, see if you can ping by eigrp multicast
address and see who actually replies. Else try out forming unicast
neighbours.
Regards,
Shine
_____
From: cisco-addicted [mailto:cisco.addicted@gmail.com]
Sent: Thursday, 20 March 2008 11:31 AM
To: 'But Nicky'; 'Rik Guyler'; surendratk@hotmail.com; 'Jonathan Greenwood
II'
Cc: 'Shine Joseph'; 'Adel Karim'; 'Envuladu Tsaku'; steveaggie@gmail.com;
'Cisco certification'
Subject: RE: EIGRP adjacency Flapping
Dears,
Thnaks for your help, I tried & worked on all the comments and notes you
provided but nothing happened.
Dear Jonathan,
I tried the troubleshooting chart and all the ping working fine with me
from everywhere to everywhere with different packet size.
Gangs, do you think it is related to IOS bug??? Or how to isolate any
failure in FR?? I am afraid that the FRSW is responsible for that.
Check the configuration in the R2 (the hub) and R1 & R2 the spokes and I am
waiting for your feedback.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
interface Serial0/2/0
ip address 183.1.123.2 255.255.255.0
encapsulation frame-relay
no ip split-horizon eigrp 100
clockrate 125000
frame-relay map ip 183.1.123.1 201 broadcast
frame-relay map ip 183.1.123.3 203 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
!
interface Serial0/2/1
no ip address
shutdown
!
router eigrp 100
network 150.1.2.2 0.0.0.0
network 183.1.28.2 0.0.0.0
network 183.1.123.2 0.0.0.0
no auto-summary
eigrp router-id 150.1.2.2
!
Rack1R2#sh ip eigrp neighbors
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 183.1.123.1 Se0/2/0 139 22:40:52 47 1140 0 43
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
interface Serial0/2/0
ip address 183.1.123.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 183.1.123.3 102
frame-relay map ip 183.1.123.2 102 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
!
interface Serial0/2/1
no ip address
shutdown
!
router eigrp 100
network 150.1.1.1 0.0.0.0
network 183.1.17.1 0.0.0.0
network 183.1.123.1 0.0.0.0
no auto-summary
eigrp router-id 150.1.1.1
!
!
Rack1R1#sh ip eigrp neighbors
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 183.1.123.2 Se0/2/0 164 22:40:30 105 1140 0 34
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R 3
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
interface Serial1/0
ip address 183.1.123.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 183.1.123.1 302
frame-relay map ip 183.1.123.2 302 broadcast
no frame-relay inverse-arp
!
!
router eigrp 100
redistribute connected metric 10000 10 255 1 1500 route-map
CONNECTED_INTERFACE
network 183.1.123.3 0.0.0.0
no auto-summary
eigrp router-id 150.1.3.3
!
Rack1R3#sh ip ei neighbors
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 183.1.123.2 Se1/0 163 22:46:02 56 1140 0 34
Rack1R3#
From: But Nicky [mailto:lyredhair@gmail.com]
Sent: Tuesday, March 18, 2008 5:49 AM
To: Rik Guyler
Cc: Shine Joseph; Adel Karim; Envuladu Tsaku; steveaggie@gmail.com;
cisco-addicted; Cisco certification
Subject: Re: EIGRP adjacency Flapping
Hi all,
I think maybe there two causes:
1. split-horizon
2. duplicate router-id at EIGRP process.
BR,
But.
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:54 ART