Hi Bryan,

 

done a debug on the situation, and EIGRP packets are sent and receive
normally, but still issues a goodbye after a while. is this a bug or what?

 

the thing is when I remove the fallback bridge configuration on Cat1 that
bridges vlan 5 (192.168.5.0/24) and fa1/10 (192.168.10.0/24). the EIGRP
stabilizes. So EIGRP somehow gets screwed up with the injection of the
fallback bridging configuration. I know the fallback bridging has a separate
bridge STP that it runs with compared to the normal STP. 

 

I'm thinking , since the Dynamips/GNS3 simulation is limited to CST type of
spanning-tree, is this why it's happening???? doesn't make sense to me.

 

here is the debug output:

 

*Mar  1 00:23:26.979: EIGRP: Received HELLO on Vlan5 nbr 192.168.5.5

*Mar  1 00:23:26.979:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
peerQ un/rely 0/2

*Mar  1 00:23:27.143: EIGRP: Sending HELLO on Vlan5

*Mar  1 00:23:27.143:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Cat1(config)#

*Mar  1 00:23:28.455: EIGRP: Sending UPDATE on Vlan5 nbr 192.168.5.5, retry
16, RTO 5000

*Mar  1 00:23:28.459:   AS 1, Flags 0x1, Seq 28/0 idbQ 0/0 iidbQ un/rely 0/0
peerQ un/rely 0/2

*Mar  1 00:23:29.379: EIGRP: Sending HELLO on FastEthernet1/10

*Mar  1 00:23:29.379:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Cat1(config)#

*Mar  1 00:23:31.455: EIGRP: Received HELLO on Vlan5 nbr 192.168.5.5

*Mar  1 00:23:31.459:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
peerQ un/rely 0/2

*Mar  1 00:23:32.055: EIGRP: Sending HELLO on Vlan5

*Mar  1 00:23:32.055:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Cat1(config)#

*Mar  1 00:23:33.363: EIGRP: Received HELLO on Vlan5 nbr 192.168.5.5

*Mar  1 00:23:33.367:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
peerQ un/rely 0/2

*Mar  1 00:23:33.367:        Inteface goodbye received

*Mar  1 00:23:33.367: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is down: Interface Goodbye received

Cat1(config)#

*Mar  1 00:23:33.383: EIGRP: Vlan5 multicast flow blocking cleared

*Mar  1 00:23:33.951: EIGRP: Sending HELLO on FastEthernet1/10

*Mar  1 00:23:33.951:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Cat1(config)#

 

Cheers!

Antonio

 

From: Bryan Bartik [mailto:[email protected]] 
Sent: Monday, 15 June 2009 11:20 AM
To: Antonio Dee Hotmail
Cc: Wouter Prins; CCIE_RS OnlineStudyList
Subject: Re: [OSL | CCIE_RS] Fallback Bridging creating problem with routing
protocol

 

Hi,

Have you done any debugging to see if EIGRP packets are being seen before
the hold time expires?

On Sun, Jun 14, 2009 at 7:40 PM, Antonio Dee Hotmail
<[email protected]> wrote:

I don't think it's an MTU issue, as i'm running the NM-16 module for the
switching function on the GNS3 simulator

 

 

From: Wouter Prins [mailto:[email protected]] 
Sent: Monday, 15 June 2009 12:54 AM
To: Antonio Dee Hotmail
Subject: Re: [OSL | CCIE_RS] Fallback Bridging creating problem with routing
protocol

 

MTU issue?

2009/6/13 Antonio Dee Hotmail <[email protected]>

Hi All,

 

I'm not sure if this is just because of GNS3 or this is really a problem
with Fallback bridging to look out for.

 

My fallback bridging configuration on Cat1 is:

 

Cat1(config)# bridge 10 protocol vlan-bridge

Cat1(config)# no bridge 10 acquire

Cat1(config)# bridge 10 address 1111.1111.1111 forward

Cat1(config)# bridge 10 address aaaa.aaaa.aaaa forward

!

Cat1(config)# int vlan 5

Cat1(config-if)# bridge 10

!

Cat1(config)# int fa1/10

Cat1(config-if)# bridge 10 

 

Nothing fancy, I'm just trying out scenarios integrating different things to
see if they break or not. And i stumbled something that breaks :-) or :-(

 

My setup is so simple:    R10 <-------> Cat1 <------> R5

 

R10 (192.168.10.10) to Cat1 subnet is 192.168.10.0/24        - Cat1
connected to R10 with Fa1/10 port L3 configuration

R5 (192.168.5.5) to Cat1 subnet is 192.168.5.0/24             - Cat1
connected to R5 with Fa1/5 port L2 configuration (vlan 5) ; SVI on Cat1 is
192.168.5.1

 

Everytime i stop my GNS3 and then start back from scratch, i get this error
after injecting the fallback bridging on Cat1 to bridge both subnets.

 

I get this error on R5 to Cat1 leg, i don't see this on R10 to Cat1 leg.

 

It goes up and then goes down, it's flapping.

 

Cat1(config)#

*Mar  1 00:20:53.703: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is up: new adjacency

Cat1(config)#

*Mar  1 00:22:13.187: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is down: Interface Goodbye received

Cat1(config)#

*Mar  1 00:22:15.999: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is up: new adjacency

Cat1(config)#

*Mar  1 00:23:35.511: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is down: retry limit exceeded

Cat1(config)#

*Mar  1 00:23:38.131: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is down: Interface Goodbye received

Cat1(config)#

*Mar  1 00:23:41.563: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.5.5
(Vlan5) is up: new adjacency

 

 

Cheers!

Antonio




-- 
Wouter Prins
[email protected]
0x301FA912




-- 
Bryan Bartik
CCIE #23707 (R&S), CCNP
Sr. Support Engineer - IPexpert, Inc.
URL: http://www.IPexpert.com

Reply via email to