From: Yagnesh Patel (Yagnesh.Patel@xxxxxxxxxxx)
Date: Sat Jun 01 2002 - 19:44:09 GMT-3
David,
Here it is with output of show spanning-tree command.
R01
interface Serial0.1 multipoint
ip address 133.10.1.1 255.255.255.0
frame-relay map bridge 114 broadcast >>>> to R02
frame-relay map bridge 113 broadcast >>>> to R03
frame-relay map ip 133.10.1.2 113 broadcast
frame-relay map ip 133.10.1.3 114 broadcast
no frame-relay inverse-arp
!
bridge 1 protocol ieee
R01#show spann
Bridge group 1 is executing the IEEE compatible Spanning Tree protocol
Bridge Identifier has priority 32768, address 0000.0cfe.6484
Configured hello time 2, max age 20, forward delay 15
<<<< Current root has priority 1, address 0000.0c47.0b86>>>>> pointing
to R03 (good)
Root port is 9 (Serial0.1), cost of root path is 647
Port Number size is 9
Topology change flag not set, detected flag not set
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0
bridge aging time 300
Port 9 (Serial0.1 Frame Relay) of Bridge group 1 is forwarding
Port path cost 647, Port priority 128
Designated root has priority 1, address 0000.0c47.0b86
Designated bridge has priority 1, address 0000.0c47.0b86
Designated port is 3, path cost 0
Timers: message age 1, forward delay 0, hold 0
BPDU: sent 1, received 592
R2
interface Serial0
ip address 133.10.1.2 255.255.255.0
encapsulation frame-relay
ip ospf priority 0
no fair-queue
frame-relay map bridge 311 broadcast >>>> to R01
frame-relay map ip 133.10.1.1 311 broadcast
frame-relay map ip 133.10.1.3 311 broadcast
no frame-relay inverse-arp
bridge-group 1
!
bridge 1 protocol ieee
R02#show spann
Bridge group 1 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, address 00e0.f759.baae
Configured hello time 2, max age 20, forward delay 15
<<<<We are the root of the spanning tree >>>> !!!!!!!!!Problem
!!!!!!!!!!!!
Topology change flag set, detected flag set
Number of topology changes 7 last change occurred 00:00:32 ago
from Ethernet0
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 1, topology change 2, notification 0, aging 15
Port 2 (Ethernet0) of Bridge group 1 is forwarding
Port path cost 100, Port priority 128, Port Identifier 128.2.
Designated root has priority 32768, address 00e0.f759.baae
Designated bridge has priority 32768, address 00e0.f759.baae
Designated port id is 128.2, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
BPDU: sent 31, received 0
Port 6 (Serial0) of Bridge group 1 is forwarding
Port path cost 647, Port priority 128, Port Identifier 128.6.
Designated root has priority 32768, address 00e0.f759.baae
Designated bridge has priority 32768, address 00e0.f759.baae
Designated port id is 128.6, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 2
BPDU: sent 223, received 19
R03
interface Serial0
ip address 133.10.1.3 255.255.255.0
encapsulation frame-relay
ip ospf priority 0
frame-relay map bridge 411 broadcast >>> to R01
frame-relay map ip 133.10.1.1 411 broadcast
frame-relay map ip 133.10.1.2 411 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
bridge-group 1
!
bridge 1 protocol ieee
bridge 1 priority 1
R03#show spann
Bridge group 1 is executing the IEEE compatible Spanning Tree protocol
Bridge Identifier has priority 1, address 0000.0c47.0b86
Configured hello time 2, max age 20, forward delay 15
<< We are the root of the spanning tree>>> R03 is set for low priority
so this is fine
Port Number size is 9
Topology change flag not set, detected flag not set
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0
bridge aging time 300
Port 2 (TokenRing0) of Bridge group 1 is forwarding
Port path cost 62, Port priority 128
Designated root has priority 1, address 0000.0c47.0b86
Designated bridge has priority 1, address 0000.0c47.0b86
Designated port is 2, path cost 0
Timers: message age 0, forward delay 0, hold 0
BPDU: sent 0, received 0
Port 3 (Serial0 Frame Relay) of Bridge group 1 is forwarding
Port path cost 647, Port priority 128
Designated root has priority 1, address 0000.0c47.0b86
Designated bridge has priority 1, address 0000.0c47.0b86
Designated port is 3, path cost 0
Timers: message age 0, forward delay 0, hold 0
BPDU: sent 0, received 5
hope this helps
-Yagnesh
David Luu wrote:
> post your whole config
>
> At 05:39 PM 6/1/2002 -0400, Yagnesh Patel wrote:
>
>> David,
>> I am sorry but you got this wrong. I don't see R3 as a root Bridge
>> in R2 even thought i have appropriate frame-relay DLCI statements in
>> all my routers. Now think again it means that R1 is not forwarding
>> the BPDUs to R2.
>>
>> Just to clarify few things ....
>>
>> R1- sees R3 as a root bridge (this is fine}
>> R3- sees It self as a Root bridge (this is fine because it is set to
>> lower priority)
>> R2- sees it self as a Root bridge """""This means R1 is not
>> forwarding BPDUs from one spoke(R3) to another Spoke(R2)"""""""
>>
>> Thanks
>> Yagnesh
>>
>>
>> David Luu wrote:
>>
>>> i would like to clear this whole split-horizon thing...
>>>
>>> this is the scenario that Yagnesh has...
>>>
>>> ____R2
>>> /
>>> R1----<
>>> \____R3
>>>
>>> R1 being a multipoint interface acting as a hub for R2 and R3...
>>>
>>> on R2, Yagnesh sees R3 as root bridge...the way STP works, a blocked
>>> port will not send data and BPDUs...but he can see R3 as root bridge
>>> on R2, the only way for R2 to know is through BPDUs
>>>
>>> the reason for him being able to see BPDUs is because of the mapping
>>> the bridge to dlci's...if you ask yourself what does the map bridge
>>> statements have to do with it, think about how frame relay in a
>>> multipoint environment when you have to map ip's to dlci's, it works
>>> the same way...you could have split-horizon turned on and it will
>>> still work
>>>
>>> in this scenario you need to manipulate R1 as the root bridge for it
>>> to work properly
>>>
>>>
>>> At 09:42 AM 6/1/2002 -0400, ying chang wrote:
>>>
>>>> Sorry, but I would agree with Serguei. We may not be able to call
>>>> it split-horizon, but that's basically why we cannot bridge between
>>>> 2 spokes in multipoint FR environment. Bridge will not send data
>>>> back out to the same port it receives from. I would try
>>>> point-to-point if I must bridge spokes.
>>>>
>>>> Chang
>>>>
>>>>> From: David Luu <wicked01@ix.netcom.com>
>>>>> Reply-To: David Luu <wicked01@ix.netcom.com>
>>>>> To: "Bezverkhi, Serguei" <Serguei.Bezverkhi@hp.com>,
>>>>> "Yagnesh Patel" <Yagnesh.Patel@verizon.net>
>>>>> CC: <ccielab@groupstudy.com>
>>>>> Subject: RE: FrameRelay multipoint interface and bridging
>>>>> Date: Fri, 31 May 2002 21:49:38 -0700
>>>>>
>>>>> split horizon deals with routing updates being received and not
>>>>> sent out
>>>>> the same interface...split horizon deals with layer 3, bridging is
>>>>> layer
>>>>> 1...it has no relevance in this scenario
>>>>>
>>>>> yagnesh...
>>>>>
>>>>> first of all, does your frame relay work? without any routing
>>>>> protocols
>>>>> running...ping throughout the frame relay cloud, if you cant ping,
>>>>> then the
>>>>> problem lies in your frame relay configs
>>>>>
>>>>> frame relay map bridge statements needs to be in all routers
>>>>> participating
>>>>> in a bridged multipoint frame relay environment...R1s multipoint
>>>>> serial
>>>>> interface, R2 and R3s serial interface (R1 will have 2 map bridge
>>>>> statements)
>>>>>
>>>>> and the bridge group command on all interfaces participating...R1s
>>>>> multipoint serial interface, R2s serial and ethernet, R3s serial
>>>>> and ethernet
>>>>>
>>>>>
>>>>> At 12:03 AM 6/1/2002 -0400, Bezverkhi, Serguei wrote:
>>>>>
>>>>>> It won't work because of the split horizon, and as far as I remember
>>>>>> there is no way to disable it. You have to use point-to-point
>>>>>> interfaces
>>>>>> to resolve this.
>>>>>>
>>>>>> Hope it helps
>>>>>>
>>>>>> Serguei
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Yagnesh Patel [mailto:Yagnesh.Patel@verizon.net]
>>>>>> Sent: May 31, 2002 10:41 PM
>>>>>> To: ccielab@groupstudy.com
>>>>>> Subject: FrameRelay multipoint interface and bridging
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>> Can anyone please provide me a good solution for the following
>>>>>> problem.
>>>>>>
>>>>>> R1= Hub router with a multipoint interface
>>>>>> R2 = Spoke_1 with Connected to R1's multipoint interface thru
>>>>>> Frame-relay R3 = Spoke_2 Connected to R1's multipoint interface thru
>>>>>> Frame-relay VLAN_2 = Connected to R2 router VLAN_3 = Connected to R3
>>>>>> router
>>>>>>
>>>>>> I want to bridge VLAN2 and VLAN3. I have all appropriate
>>>>>> commands under
>>>>>>
>>>>>> the interfaces / global including "frame-relay map bridge"
>>>>>> statement but
>>>>>>
>>>>>> it is not working. I think it is not working because both spokes are
>>>>>> connected to the same multipoint interface on R1.
>>>>>>
>>>>>>
>>>>>> Thanks
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:20 GMT-3