[f-nsp] Spanning tree on brocade

Nick Cutting ncutting at edgetg.com
Tue May 17 09:01:39 EDT 2016


So is this the root port (cisco terminology) – when the designated bridge is set to the root bridge’s priority+mac?

[cid:image002.png at 01D1B01A.92E9D010]

From: ekoyle at gmail.com [mailto:ekoyle at gmail.com] On Behalf Of Eldon Koyle
Sent: Monday, May 16, 2016 6:56 PM
To: Nick Cutting
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Spanning tree on brocade

The bridge ID is the bridge priority in hex (default 0xFFFF) followed by the chassis MAC.  This is part of the STP specification.  The lowest bridge ID is chosen as the root bridge (so the lower the priority value the more likely a device is to become the spanning tree root, and when the priority is equal the lower chassis MAC wins).
"VLAN ID" is the VLAN ID for this STP instance (or, often 4094 for the common STP instance in single spanning tree; look for "L2 VLAN ... are members of single spanning tree" in the output).
"Root ID" is the bridge ID of the global STP root device

"Bridge Address" is the chassis MAC of the device you are connected to (not the Bridge ID)
"Designated Bridge" is the bridge ID of the local root
"Designated Root" is the bridge ID of the global root for this instance


Note that to see rstp info, you need to do 'show 802-1w' which has similar output to 'show span', but drops the redundant "Designated Root" column and adds a "Role" column (which I find a lot easier to understand).  STP and RSTP are completely separate on these devices.

You might try looking at the output of 'show span detail' and 'show span 802-1w detail' to see if that clears anything up for you.
Also, the priority is entered in decimal in the config (so you will probably see a line like: 'spanning tree ... priority 25077' for your device with 61f5 in its bridge id).
--
Eldon Koyle

On Mon, May 16, 2016 at 2:58 PM, Nick Cutting <ncutting at edgetg.com<mailto:ncutting at edgetg.com>> wrote:
Hi I am trying to document the spanning tree domain on a brocade environment that has both TurboIron-X24’s and FCX-48G’s

I’m traditionally a cisco guy so need some help in figuring out the show output of show span.

Right now we have a mix of rapid spanning tree and classic, I need help in understand which is the mac address of the root bridge, the root ports and the terminology used in the output.

For example – is the root ID a mac address and the vlan ID added in Hex? What is the designated bridge ? is this is the downstream switches bridge ID?

I can’t seem to match the bridge ID and the Root ID to mac address tables on the switch – is anyone able to shed light on these relationships and describe what each of the terms means below?

I’m guessing the first 4 digits of the DES root and DES Bridge are the priorities in HEX


STP instance owned by VLAN 501

Global STP (IEEE 802.1D) Parameters:

VLAN Root             Root Root Prio Max He- Ho- Fwd Last     Chg  Bridge
 ID   ID              Cost Port rity Age llo ld  dly Chang    cnt  Address
                                Hex  sec sec sec sec sec
 501 61f5000d662f3f40 6    1    ffff 20  2   1   15  133406   770  748ef86b37cd

Port STP Parameters:

Port  Prio Path  State       Fwd    Design   Designated       Designated
Num   rity Cost              Trans  Cost     Root             Bridge
      Hex
1     80   2     FORWARDING  3      4        61f5000d662f3f40 ffff0024387826c0
2     80   2     BLOCKING    5      6        61f5000d662f3f40 ffff002438780e80
5     80   2     FORWARDING  1      6        61f5000d662f3f40 ffff748ef86b37cd
6     80   2     FORWARDING  4      6        61f5000d662f3f40 ffff748ef86b37cd
11    80   2     BLOCKING    7      6        61f5000d662f3f40 8000748ef8f81bc0
12    80   2     BLOCKING    5      6        61f5000d662f3f40 8000748ef8f80e40
13    80   2     FORWARDING  2      6        61f5000d662f3f40 ffff748ef86b37cd
14    80   2     FORWARDING  2      6        61f5000d662f3f40 ffff748ef86b37cd
15    80   2     FORWARDING  2      6        61f5000d662f3f40 ffff748ef86b37cd
16    80   2     FORWARDING  2      6        61f5000d662f3f40 ffff748ef86b37cd
17    80   2     FORWARDING  3      6        61f5000d662f3f40 ffff748ef86b37cd
18    80   0     DISABLED    0      0        0000000000000000 0000000000000000
19    80   2     FORWARDING  7      6        61f5000d662f3f40 ffff748ef86b37cd
20    80   2     FORWARDING  9      6        61f5000d662f3f40 ffff748ef86b37cd
21    80   2     FORWARDING  3      6        61f5000d662f3f40 ffff748ef86b37cd
22    80   2     FORWARDING  3      6        61f5000d662f3f40 ffff748ef86b37cd
23    80   2     BLOCKING    10     4        61f5000d662f3f40 ffff0024387826c0
24    80   2     BLOCKING    10     4        61f5000d662f3f40 ffff0024387826c0




Nick Cutting | Network Engineer | Architecture & Standards Team| Office: 203-742-7856<tel:203-742-7856> | Fax: 203-742-7890<tel:203-742-7890>

[cid:image001.png at 01D045E3.7FDE6B40]


_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net<mailto: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/20160517/3c6cc7aa/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 44707 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20160517/3c6cc7aa/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8309 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20160517/3c6cc7aa/attachment-0003.png>


More information about the foundry-nsp mailing list