Realtyloading774

When you enable MSTP on the switch, a spanning tree instance is enabled automatically. The switch supports up to 16 configurable MST instances for each VLAN group that you want to operate as an active topology within the region to which the switch belongs. When creating an instance, you must include a minimum of one VID. You can add more VIDs later if desired.

• Hp Procurve Configure Spanning Tree Priority
• Procurve Spanning Tree Priority Tool
• Procurve Spanning Tree Port Priority

Syntax:

[no] spanning-tree instance <1..4> vlan <vid> [<vid..vid>]

Priority The preference that STP gives this port relative to other ports for forwarding traffic out of the spanning tree. A higher numerical value means a lower priority; thus, the highest priority is 8. 128 Possible values: 8 – 252 (configurable in increments of 4) Path Cost The cost of using the por t to reach the root br idge. Spanning-tree mst configuration name mstp revision 1 instance 0 vlan 1, 40, 70, 100, 250 spanning-tree mst 0 root primary Its strange that your root is flapping but you have only set the priority for instance 1 not 0. Move it all to instance 0 and also set the priority of MST instance 0 on the HP switches to higher than the default.

Configuring MSTP on the switch automatically configures the IST instance and places all statically and dynamically configured VLANs on the switch into the IST instance. This command creates a new MST instance (MSTI) and moves the VLANs you specify from the IST to the MSTI.

You must map at least one VLAN to an MSTI when you create it. You cannot map a VLAN ID to more than one instance. You can create up to 16 MSTIs in a region.

The no form of the command removes one or more VLANs from the specified MSTI. If no VLANs are specified, the no form of the command deletes the specified MSTI.

When you remove a VLAN from an MSTI, the VLAN returns to the IST instance, where it can remain or be re-assigned to another MSTI configured in the region.

This new default behavior differs from automatically including configured (static and dynamic) VLANs in the IST instance and requiring the manual assigning of individual static VLANs to an MSTI.

Syntax:

spanning-tree instance <1..4> priority <priority-multiplier>

Sets the switch (bridge) priority for the designated instance. This priority is compared with the priorities of other switches in the same instance to determine the root switch. The lower the priority value, the higher the priority. If there is only one switch in the instance, then that switch is the root switch for the instance. The IST regional root bridge provides the path to instances in other regions that share one or more of the same VLANs.

The priority range for an MSTP switch is 0 - 61440. However, this command specifies the priority as a multiplier (0 - 15) of 4096. When a priority multiplier value is set from 0 - 15, the actual priority assigned to the switch for the specified MST instance is: (priority-multiplier) x 4096

For example, if you configure 5 as the priority-multiplier for MST Instance 1 on a given MSTP switch, the Switch Priority setting is 20,480 for that instance in that switch.

Syntax:

spanning-tree instance <ist | 1..4> <port-list> path-cost [auto | <1..200000000>]

Assigns an individual port cost for the IST or for the specified MST instance.

For a given port, the path cost setting can be different for different MST instances to which the port may belong. The switch uses the path cost to determine which ports are the forwarding ports in the instance; that is, which links to use for the active topology of the instance and which ports to block.

The settings are either auto or in a range from 1 to 200,000,000. With the auto setting, the switch calculates the path cost from the link speed:

Syntax:

spanning-tree instance <1..4 port-list> priority <priority-multiplier>

Sets the priority for the specified ports in the specified MST instance.

For a given port, the priority setting can be different for different MST instances to which the port may belong. The priority range for a port in a given MST instance is 0 - 255. However, this command specifies the priority as a multiplier (0 - 15) of 16. When you specify a priority multiplier of 0 - 15, the actual priority assigned to the switch is: (priority-multiplier) x 16

Setting priority for a port in a specified MST instance

If you configure 2 as the priority multiplier on a given port in an MST instance, then the actual Priority setting is 32x. After you specify the port priority multiplier in an instance, the switch displays the actual port priority and not the multiplier in the show spanning-tree instance <1..4> or show spanning-tree <port-list> instance <1..4> displays.

You can view the actual multiplier setting for ports in the specified instance by executing show running and looking for an entry in the following format:

spanning-tree instance < 1..4 port-list> priority <priority-multiplier>

For example, configuring port A2 with a priority multiplier of 3 in instance 1, results in this line in the show running output:

Syntax:

spanning-tree <port-list> priority <priority-multiplier>

Sets the priority for the specified ports for the IST (Instance 0) of the region in which the switch resides.

The priority component of the port's Port Identifier is set. The Port Identifier is a unique identifier that helps distinguish this switch's ports from all others. It consists of the priority value with the port number extension—PRIORITY:PORT_NUMBER. A port with a lower value of Port Identifier is more likely to be included in the active topology.

This priority is compared with the priorities of other ports in the IST to determine which port is the root port for the IST instance. The lower the priority value, the higher the priority. The IST root port (or trunk) in a region provides the path to connected regions for the traffic in VLANs assigned to the region's IST instance.

The priority range for a port in a given MST instance is 0 - 240. However, this command specifies the priority as a multiplier (0 - 15) of 16. When you specify a priority multiplier of 0 - 15, the actual priority assigned to the switch is: (priority-multiplier) x 16

Setting priority for specified ports for an IST

Configuring 5 as the priority multiplier on a given port in the IST instance for a region creates an actual priority setting of 80. After specifying the port priority multiplier for the IST instance, the switch displays the actual port priority, not the multiplier, in the show spanning-tree instance ist or show spanning-tree <port-list> instance ist displays. You can view the actual multiplier setting for ports in the IST instance by executing show running and looking for an entry in this format:

spanning-tree <port-list> priority <priority-multiplier>

So configuring port A2 with a priority multiplier of 2 in the IST instance, results in this line in the show running output:

This command enables or disables spanning tree operation for any spanning tree protocol enabled on the switch. Before using to enable spanning tree, ensure that the right version is active on the switch.

Syntax:

Enables or disables spanning tree. Enabling spanning tree with MSTP configured, implements MSTP for all physical ports on the switch according to the VLAN groupings for the IST instance and any other configured instances.

Disabling MSTP removes protection against redundant loops that can significantly slow or halt a network.

This command simply turns spanning tree on or off. It does not change the existing spanning tree configuration.

This operation exchanges the currently active MSTP configuration with the currently pending MSTP configuration, making it possible to implement a new MSTP configuration with minimal network disruption or to exchange MSTP configurations for testing or troubleshooting purposes.

When configuring or reconfiguring MSTP, the switch recalculates the corresponding network paths. This can have a ripple effect throughout your network as adjacent MSTP switches recalculate network paths to support the configuration changes invoked in a single switch. Although MSTP employs rapid spanning tree operation, the convergence time for implementing MSTP changes can be disruptive to your network. However, by using the spanning-tree pending feature, you can set up an MSTP on the switch and then invoke all instances of the new configuration at the same time, instead of one at a time.

Syntax:

[no] spanning-tree pending [ apply | <config-name> | <config-revision> | instance | reset ]

Exchanges the currently active MSTP configuration with the current pending MSTP configuration. Options are as follows:

To create a pending MSTP configuration and exchange it with the active MSTP configuration:

1. Configure the VLANs to include in any instances in the new region. When you execute the pending command, all VLANs configured on the switch will be assigned to a single pending IST instance unless assigned to other, pending MST instances. The pending command creates the region's IST instance automatically.

2. Configure MSTP as the spanning tree protocol, then execute write mem and reboot. The pending option is available only with MSTP enabled.

3. Configure the pending region <config-name> to assign to the switch.

4. Configure the pending <config-revision> number for the region name.

5. If you want an MST instance other than the IST instance, configure the instance number and assign the appropriate VLANs (VIDs) using the pending instance <1..4> vlan [ vid | <vid-range> ]

6. Repeat step 5 for each additional MST instance necessary.

7. To review your pending configuration, use the show spanning-tree pending command.

8. To exchange the currently active MSTP configuration with the pending MSTP configuration, use the spanning-tree pending apply command.

I want to point out that Ruckus/Brocade has 2 commands that contradict each other when configuring Spanning Tree:

Brocade(config-vlan-1)#spanning-tree ?

802-1w Enable Rapid Spanning Tree IEEE 802.1w
rstp Enable Rapid Spanning Tree

Since RSTP is the same as 802.1w further clarification is needed.

Brocade(config-vlan-1)#spanning-tree rstp is a Brocade early implementation of the IEEE 802.1W which provided only a subset of the standard, whereas the

Brocade(config-vlan-1)#spanning-tree 802-1w feature provides the full standard, so basically you should use 802.1w.

How to configure Spanning Tree on Brocade

Ran mainly on a per VLAN basis.

Brocade# conf t
Brocade (config)#vlan 1
Brocade (config-vlan-1)# spanning-tree 802-1w – enabled spanning tree basic mode
Brocade (config-vlan-1)# show 802-1w – shows spanning tree information
Brocade (config-vlan-1)# spanning-tree 802-1w priority 0 – to designate that switch Root bridge

If you know there is a point to point link between 2 rapid spanning tree devices you have to turn that on at the interface level

Hp Procurve Configure Spanning Tree Priority

Point-to-Point/Uplinks
Brocade (config-vlan-1)#int e 1/1/1
Brocade (config-if-e10000-1/1/1)# spanning-tree 802-1w admin-p2pt-mac – don’t allow for a broadcast domain, assume there is a link between 2 rapid spanning tree root bridges/uplinks ( without this it will fail over in 2 seconds or less, but fail back takes the traditional 30 of listening and learning, but this allows it to fail forward and back in 2 seconds or less

Access/Edge-Ports
Brocade (config-if-e10000-1/1/1)# int e 1/1/3 to 1/1/24
Brocade (config-if-e10000-1/1/3-1/1/24)# spanning-tree 802-1w admin-edge-port (not really required, just means topology changes on the edge is not going to cause re-convergence on the core links or vice versa

Procurve Spanning Tree Priority Tool

Brocade (config-if-e10000-1/1/3-1/1/24)# show run – will see spanning tree on the VLAN and the int ports

Procurve Spanning Tree Port Priority

***DO NOT USE VLAN1 IN PRODUCTION, THIS IS PURELY FOR DEMONSTRATION PURPOSES***