[f-nsp] Spanning tree on brocade

Eldon Koyle ekoyle+puck.nether.net at gmail.com
Wed May 18 02:02:57 EDT 2016


So neither "show span" nor "show 802-1w" shows spanning tree running?  Is
this turboiron running routing code or switch code?  IIRC, the default is
single spanning tree on switch code and no spanning tree on routing code.

-- 
Eldon Koyle
On May 17, 2016 2:12 PM, "Nick Cutting" <ncutting at edgetg.com> wrote:

> I think I have found my answer – as this switch is not participating in
> spanning tree – I believe that :
>
>
>
> STP configured to ON, priority is level0
>
>
>
> Is forwarding the BPDU’s unmodified.
>
>
>
> Would I be correct in this assumption? I see the correct Bridge ID’s as if
> this switch is not there.
>
>
>
> *From:* Nick Cutting
> *Sent:* Tuesday, May 17, 2016 3:26 PM
> *To:* Nick Cutting; Eldon Koyle
> *Cc:* foundry-nsp at puck.nether.net
> *Subject:* RE: [f-nsp] Spanning tree on brocade
>
>
>
> Now I have another switch – that has no IEEE spanning tree, No 802w, and
> no pvst configured.
>
>
>
> however, it says it is enabled on the port??
>
>
>
> 10GigabitEthernet23 is up, line protocol is up
>
>   Hardware is 10GigabitEthernet, address is 748e.f821.57d3 (bia
> 748e.f821.57e9)
>
>   Configured speed 10Gbit, actual 10Gbit, configured duplex fdx, actual fdx
>
>   Member of L2 VLAN ID 501, port is untagged, port state is FORWARDING
>
>   BPDU guard is Disabled, ROOT protect is Disabled
>
>   Link Error Dampening is Disabled
>
> *  STP configured to ON, priority is level0*
>
>
>
> Now – the loops prevention is on the otherside – and they are receiving
> BPDU’s on this switch – how can this be possible with no stp config?
>
>
>
> Can someone please elaborate on the port level spanning tree?
>
>
>
> Thanks !
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20160518/a1b75e26/attachment-0001.html>


More information about the foundry-nsp mailing list