Hi Pierre,
You still need to finish setting up trunking on the
2924XL to see if my theory is correct.
The two Catalysts on the segment between Port B on the
C1912 and Fa0/21 on the 2924XL don't seem to be
talking. So Port B shows that it knows who the root
bridge is, but it shows itself as the designated
bridge since it sees itself as the only switch on that
segment and thus the only way to get to the root. One
thing I still can't explain is why Port A on the C1912
shows the root cost as being 0. It should be only 0
only if it sees itself as the root, but it doesn't
because it shows the proper MAC address.
Anyways, give that a shot and let's see where it goes.
Michael
--- Pierre-Alex <[EMAIL PROTECTED]> wrote:
> Hi Leigh Anne and others:
>
> Leigh Anne, I hope you did not loose sleep over this
> problem.... At 8:30 PM
> after a full day on this problem I went to sleep and
> crashed ....
>
> So here we again:
>
> You discovered correctly that PORT A is connected to
> f0/20 and PORT B to f
> 0/21
> ALL those ports are part of VLAN 1 (see output
> bellow)
> And all the ports are in fowarding mode and the
> lights on the switch are
> glowing GREEN! (see below the span tree)
> Someone suggested the presence of an etherchannel
> configured by default. I
> will look into this
> and will let you know ....
>
> Pierre-Alex
>
> Interface Fa0/20 (port 22) in Spanning tree 1 is
> FORWARDING
> Port path cost 19, Port priority 128
> Designated root has priority 32768, address
> 0050.3ef0.3580
> Designated bridge has priority 32768, address
> 0050.3ef0.3580
> Designated port is 22, path cost 0
> Timers: message age 0, forward delay 0, hold 0
> BPDU: sent 73253, received 5
>
> Interface Fa0/21 (port 23) in Spanning tree 1 is
> FORWARDING
> Port path cost 19, Port priority 128
> Designated root has priority 32768, address
> 0050.3ef0.3580
> Designated bridge has priority 32768, address
> 0050.3ef0.3580
> Designated port is 23, path cost 0
> Timers: message age 0, forward delay 0, hold 0
> BPDU: sent 73251, received 3
>
> --More--
>
>
> VLAN Name Status
> Ports
> ---- -------------------------------- ---------
> ----------------------------
> ---
> 1 default active
> Fa0/2, Fa0/3, Fa0/4, Fa0/5,
>
> Fa0/6, Fa0/7, Fa0/10,
> Fa0/11,
>
> Fa0/12, Fa0/13, Fa0/14,
> Fa0/15,
>
> Fa0/17, Fa0/18, Fa0/19,
> Fa0/21,
>
> Fa0/22, Fa0/23
> 2 VLAN_A active
> Fa0/9, Fa0/16, Fa0/24
> 3 VLAN_B active
> Fa0/1, Fa0/8
>
>
> ___________________________________________
>
> Port FastEthernet 0/26 of VLAN1 is Forwarding
> Port path cost 10, Port priority 128
> Designated root has priority 32768, address
> 0050.3EF0.3580
> Designated bridge has priority 32768, address
> 0050.3EF0.3580
> Designated port is 22, path cost 0
> Timers: message age 20, forward delay 15, hold 1
> --More--
> Port FastEthernet 0/27 of VLAN1 is Forwarding
> Port path cost 10, Port priority 128
> Designated root has priority 32768, address
> 0050.3EF0.3580
> Designated bridge has priority 32768, address
> 0050.50E2.42C0
> Designated port is 27, path cost 10
> Timers: message age 20, forward delay 15, hold 1
>
> Pierre-Alex
>
> -----Original Message-----
> From: Leigh Anne Chisholm [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 1:29 AM
> To: Pierre-Alex; Cisco Groupstudy (E-mail)
> Cc: Dale Cunningham
> Subject: RE: DISTURBING: Spanning Tree Protocol Does
> not Work.
>
> Okay, here's the jist of things.
>
> The Catalyst 2924XL is the root bridge:
>
> > C2924XL#sh span
> >
> > Spanning tree 1 is executing the IEEE compatible
> Spanning Tree protocol
> > Bridge Identifier has priority 32768, address
> 0050.3ef0.3580
> > Configured hello time 2, max age 20, forward
> delay 15
> > We are the root of the spanning tree
>
> Port 0/26 on the Catalyst 1912 is identifying "Port
> 22" as the "designated
> port":
>
> > Port FastEthernet 0/26 of VLAN1 is Forwarding
> > Port path cost 10, Port priority 128
> > Designated root has priority 32768, address
> 0050.3EF0.3580
> > Designated bridge has priority 32768, address
> 0050.3EF0.3580
> > Designated port is 22, path cost 0
> > Timers: message age 20, forward delay 15, hold
> 1
>
> Port 22 is, port 0/20 on the Catalyst 2924XL switch:
>
> > Interface Fa0/20 (port 22) in Spanning tree 1 is
> FORWARDING
> > Port path cost 19, Port priority 128
> > Designated root has priority 32768, address
> 0050.3ef0.3580
> > Designated bridge has priority 32768, address
> 0050.3ef0.3580
> > Designated port is 22, path cost 0
> > Timers: message age 0, forward delay 0, hold 0
> > BPDU: sent 46897, received 5
>
> We can deduce that FastEthernet 0/26 on the 1912
> switch is directly
> connected to FastEthernet 0/20 on the 2924XL switch.
>
> Note that FastEthernet 0/26 on the Catalyst 1912 is
> identified as the root
> port as seen below:
>
> > C1912#sh span
> >
> > VLAN1 is executing the IEEE compatible Spanning
> Tree Protocol
> > Bridge Identifier has priority 32768, address
> 0050.50E2.42C0
> > Configured hello time 2, max age 20, forward
> delay 15
> > Current root has priority 32768, address
> 0050.3EF0.3580
> > Root port is FastEthernet 0/26, cost of root
> path is 10
> > Topology change flag not set, detected flag not
> set
> > Topology changes 5, last topology change occured
> 0d02h42m54s ago
> > Times: hold 1, topology change 8960
> > hello 2, max age 20, forward delay 15
> > Timers: hello 2, topology change 35,
> notification 2
>
> So what we have is a LAN segment connection where
> one end of the connection
> is identified as the root port while the other is
> identified as the root
> port for the non-root-bridge Catalyst 1912 switch.
> Everything seems to be
> "kosher".
>
> All ports on the root bridge are designated ports by
> default. During the
> execution of the Spanning Tree Algorithm, a root
> port (the port with the
> lowest cost path to the root bridge) is identified,
> and each LAN segment
> must identify one port as a designated port. If the
> LAN segment contains
> one or more ports not identified as the root port
> for the switch or a
> designated port, the port is identified as
> non-designated and is placed in
> the blocking state.
>
> If spanning tree was working properly in this
> topology, and if a looped
> topology actually existed, another port on the
> Catalyst 1912 should show a
> port on the Catalyst 2924XL as its designated port
> with that port on the
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
