Académique Documents
Professionnel Documents
Culture Documents
Huawei switch
The Multiple Spanning Tree Protocol (MSTP) was originally defined as the IEEE 802.1s
standard protocol. Now the standard IEEE 802.1Q-2005 includes MSTP. The basic role of
this protocol is to prevent L2 loops. I do not want to explain MSTP in details, as this can be
easily found on the Internet. I just want to show you:
By default MSTP runs only one spanning-tree topology over a LAN network for every
VLAN. Even if we configure 1000 different VLANs throughout this topology, only three
links will be utilized. This is because STP blocks two links, preventing our topology from L2
loops. In our case SW1 was elected as the Root Bridge. As a result we have the following
logical topology which will be used by every VLAN to forward traffic (assuming default
MSTP configuration):
Links SW2SW3 and SW2SW4 will be blocked by the SW3 and SW4 switches
respectively. Traffic from every device connected to any VLAN configured, will be travelling
only these three links. This is a default MSTP behaviour.
To overcome this negative issue, MSTP protocol should be properly planned and configured.
By default this protocol runs only one STP instance and maps all VLANs to this instance. To
utilize all physical links equally, additional instances should be added.
Lets assume that we have two VLANs: 100 and 200. By default both VLANs will use the
same logical STP topology as in the picture above. This is because both VLANs belong to the
same MSTP Instance, which was determined by the one Root Bridge placement (SW1 in our
case).
To force VLAN 100 to use one logical topology and VLAN 200 to use a different logical
topology, we need to:
<labnarioSW1>system-view
[labnarioSW1]vlan batch 100 200
[labnarioSW1]stp region-configuration
[labnarioSW1-mst-region] region-name labnario
[labnarioSW1-mst-region] instance 1 vlan 100
[labnarioSW1-mst-region] instance 2 vlan 200
[labnarioSW1-mst-region] active region-configuration
Info: This operation may take a few seconds. Please wait for a
moment....done.
[labnarioSW1-mst-region]
[labnarioSW1-mst-region]check region-configuration
Admin configuration
Format selector :0
Region name :labnario
Revision level :0
As you see above, by default all VLANs are mapped to the MSTP Instance 0. This is the
reason that all VLANs use the same logical topology to forward traffic between devices.
Now SW1 should be configured as the Root Bridge for MSTP Instance 1 and SW2 as the
Root Bridge for MSTP Instance 2. In case of Root Bridge failure, backup devices should be
also defined as follows:
0.4c1f-cc10-af35
Zero followed by the MAC address means, that this switch is the Root Bridge Primary for the
MSTP Instance 1. By default bridge priority equals to 32768. Lets check MSTP Instance 2:
Bridge ID is:
4096.4c1f-cc10-af35
Bridge priority equals to 4096, this is because this switch is configured as the Root Bridge
Secondary for the MSTP Instance 2.
As you see, RegRoot ID is different than Bridge ID. This is because SW2 was configured as
the STP Root Bridge Primary for the MSTP Instance 2.
All ports in MSTP Instance 1 have a Designated role. This means that SW1 is the Root Bridge
for this Instance.
RegRoot field points to SW1s MAC address. This means that SW1 is the Root Bridge for
MSTP Instance 1. Bridge ID followed by the 4096 means that SW2 is the Root Bridge
Secondary for MSTP Instance 1.
All ports in MSTP Instance 2 have Designated role and Forwarding state. This switch is the
Root Bridge for MSTP Instance 2.
Which links are blocked by the MSTP? Lets check STP topologies on SW3:
Interface Eth0/0/3 is blocked by the STP Instance 1 and Eth0/0/1 blocked by the STP Instance
2.
<labnarioSW4>debugging stp ?
all Specify all debug switch
event Specify event debug switch
global-error Specify global error debug switch
global-event Specify global event debug switch
ha-info Backup information
instance Spanning tree instance
interface Specify interface
msti Specify debugging packet's MSTIs
packet Specify packet debug switch
process The MSTP process