Thank you -
Now – should I see a lower cost on a trunk link?
I still see a cost of 4 on a 2x10 trunk port (etherchannel/LAG) – is there
somewhere I need to change a reference cost to accommodate for links larger
than 10G?
Now I know that Port1 connected to a switch, that connects to the root bridge –
How using the detail output can I know that this is true (if I had not traced
the cables?)
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 214685 770 748ef86b37cd
Does this also mean I’m running MST? – this only showed up under the detail
section, and I see no config for MST.
#sh span detail vlan 501
======================================================================
VLAN 501 - MULTIPLE SPANNING TREE (MSTP) ACTIVE
======================================================================
Bridge identifier - 0xffff748ef86b37cd
Active global timers - None
Port 1 is FORWARDING
Port - Path cost: 2, Priority: 128, Root: 0x61f5000d662f3f40
Designated - Bridge: 0xffff0024387826c0, Interface: 64, Path cost: 4
Active Timers - Message age: 1
BPDUs - Sent: 579, Received: 215789
Port 2 is BLOCKING
Port - Path cost: 2, Priority: 128, Root: 0x61f5000d662f3f40
Designated - Bridge: 0xffff002438780e80, Interface: 64, Path cost: 6
Active Timers - Message age: 2
BPDUs - Sent: 541, Received: 216134
……
Port 23 is BLOCKING
Port - Path cost: 2, Priority: 128, Root: 0x61f5000d662f3f40
Designated - Bridge: 0xffff0024387826c0, Interface: 66, Path cost: 4
Active Timers - Message age: 1
BPDUs - Sent: 859, Received: 432688
Port 24 is BLOCKING
Port - Path cost: 2, Priority: 128, Root: 0x61f5000d662f3f40
Designated - Bridge: 0xffff0024387826c0, Interface: 66, Path cost: 4
Active Timers - Message age: 1
BPDUs - Sent: 859, Received: 432688
From: [email protected] [mailto:[email protected]] On Behalf Of Eldon Koyle
Sent: Monday, May 16, 2016 6:56 PM
To: Nick Cutting
Cc: [email protected]
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
<[email protected]<mailto:[email protected]>> 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:[email protected]]
_______________________________________________
foundry-nsp mailing list
[email protected]<mailto:[email protected]>
http://puck.nether.net/mailman/listinfo/foundry-nsp
________________________________
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp