Table Of Contents
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
Understanding How PortFast Works
Understanding How PortFast BPDU Guard Works
Understanding How PortFast BPDU Filtering Works
Understanding How UplinkFast Works
Understanding How BackboneFast Works
Understanding How Loop Guard Works
Configuring PortFast
Enabling PortFast on an Access Port
Enabling Spanning Tree PortFast on a Trunk Port
Disabling PortFast
Resetting PortFast
Configuring PortFast BPDU Guard
Enabling PortFast BPDU Guard
Disabling PortFast BPDU Guard
Configuring PortFast BPDU Filtering
Enabling PortFast BPDU Filtering
Disabling PortFast BPDU Filtering
Configuring UplinkFast
Enabling UplinkFast
Disabling UplinkFast
Configuring BackboneFast
Enabling BackboneFast
Displaying BackboneFast Statistics
Disabling BackboneFast
Configuring Loop Guard
Enabling Loop Guard
Disabling Loop Guard
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
This chapter describes how to configure the spanning tree PortFast, UplinkFast, BackboneFast, and loop guard features on the Catalyst 6500 series switches.
Note
For information on configuring the Spanning Tree Protocol (STP), see "Configuring Spanning Tree."
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Catalyst 6500 Series Switch Command Reference publication.
This chapter consists of these sections:
•
Understanding How PortFast Works
•
Understanding How PortFast BPDU Guard Works
•
Understanding How PortFast BPDU Filtering Works
•
Understanding How UplinkFast Works
•
Understanding How BackboneFast Works
•
Understanding How Loop Guard Works
•
Configuring PortFast
•
Configuring PortFast BPDU Guard
•
Configuring PortFast BPDU Filtering
•
Configuring UplinkFast
•
Configuring BackboneFast
•
Configuring Loop Guard
Understanding How PortFast Works
Spanning tree PortFast causes a switch or trunk port to enter the spanning tree forwarding state immediately, bypassing the listening and learning states.
You can use PortFast on switch or trunk ports that are connected to a single workstation, switch, or server to allow those devices to connect to the network immediately, instead of waiting for the port to transition from the listening and learning states to the forwarding state.
Caution 
You can use PortFast to connect a single end station or a switch port to a switch port. If you enable PortFast on a port that is connected to another Layer 2 device, such as a switch, you might create network loops.
When the switch powers up, or when a device is connected to a port, the port normally enters the spanning tree listening state. When the Forward Delay timer expires, the port enters the learning state. When the Forward Delay timer expires a second time, the port transitions to the forwarding or blocking state.
When you enable PortFast on a switch or trunk port, the port transitions immediately to the spanning tree forwarding state.
Understanding How PortFast BPDU Guard Works
BPDU guard prevents spanning tree loops by moving a port into the errdisable state when a BPDU is received on that port. When you enable BPDU guard on the switch, spanning tree shuts down the interfaces that receive BPDUs instead of putting the interfaces into the spanning tree blocking state. When you enable BPDU guard globally and set the port configuration as the default for BPDU guard (see "Configuring PortFast BPDU Guard" section), then the PortFast configuration enables or disables BPDU guard.
If the port configuration is not set to default, then PortFast will not affect BPDU guard. Table 9-1 lists all the possible BPDU guard port configurations. BPDU guard can prevent invalid configurations, because you must manually put the interface back in service.
Table 9-1 BPDU Guard Port Configurations
Per-Port Configuration
|
Global Configuration
|
PortFast Operational Value
|
Operational BPDU Guard
|
Default
|
Enable
|
Enable
|
Enable
|
Default
|
Enable
|
Disable
|
Disable
|
Default
|
Disable
|
X
|
Disable
|
Disable
|
X
|
X
|
Disable
|
Enable
|
X
|
X
|
Enable
|
Understanding How PortFast BPDU Filtering Works
BPDU filtering allows you to avoid transmitting BPDUs on a port that is connected to an end system. When you enable BPDU filtering on the switch, spanning tree places that port in the forwarding state immediately, instead of going through the listening, learning, and forwarding states. When you enable BPDU filtering globally and set the port configuration as the default for BPDU filtering (see the "Configuring PortFast BPDU Filtering" section), then PortFast enables or disables BPDU filtering.
If the port configuration is not set to default, then the PortFast configuration will not affect BPDU filtering. Table 9-2 lists all possible BPDU filtering combinations. BPDU filtering allows access ports to move directly to the forwarding state as soon as the end hosts are connected.
Table 9-2 BPDU Filtering Port Configurations
Per-Port Configuration
|
Global Configuration
|
PortFast Operational Value
|
Operational BPDU Filter
|
Default
|
Enable
|
Enable
|
Enable1
|
Default
|
Enable
|
Disable
|
Disable
|
Default
|
Disable
|
X
|
Disable
|
Disable
|
X
|
X
|
Disable
|
Enable
|
X
|
X
|
Enable
|
Understanding How UplinkFast Works
UplinkFast provides fast convergence after a spanning tree topology change and achieves load balancing between redundant links using uplink groups. An uplink group is a set of ports (per VLAN), only one of which is forwarding at any given time. Specifically, an uplink group consists of the root port (which is forwarding) and a set of blocked ports. The blocked ports do not include self-looping ports. The uplink group provides an alternate path in case the currently forwarding link fails.
Note
UplinkFast is most useful in wiring-closet switches. This feature may not be useful for other types of applications.
Figure 9-1 shows an example topology with no link failures. Switch A, the root switch, is connected directly to Switch B over link L1 and to Switch C over link L2. The port on Switch C that is connected directly to Switch B is in the blocking state.
Figure 9-1 UplinkFast Example Before Direct Link Failure
If Switch C detects a link failure on the currently active link L2 (a direct link failure), UplinkFast unblocks the blocked port on Switch C and transitions it to the forwarding state without going through the listening and learning states, as shown in Figure 9-2. This switchover takes approximately 1 to 5 seconds.
Figure 9-2 UplinkFast Example After Direct Link Failure
Understanding How BackboneFast Works
BackboneFast is initiated when a root port or blocked port on a switch receives inferior BPDUs from its designated bridge. An inferior BPDU identifies one switch as both the root bridge and the designated bridge. When a switch receives an inferior BPDU, it indicates that a link to which the switch is not directly connected (an indirect link) has failed (that is, the designated bridge has lost its connection to the root bridge). Under normal spanning tree rules, the switch ignores inferior BPDUs for the configured maximum aging time, as specified by the agingtime variable of the set spantree maxage command.
The switch tries to determine if it has an alternate path to the root bridge. If the inferior BPDU arrives on a blocked port, the root port and other blocked ports on the switch become alternate paths to the root bridge. (Self-looped ports are not considered alternate paths to the root bridge.) If the inferior BPDU arrives on the root port, all blocked ports become alternate paths to the root bridge. If the inferior BPDU arrives on the root port and there are no blocked ports, the switch assumes that it has lost connectivity to the root bridge, causes the maximum aging time on the root to expire, and becomes the root switch according to normal spanning tree rules.
If the switch has alternate paths to the root bridge, it uses these alternate paths to transmit a new kind of PDU called the Root Link Query PDU out all alternate paths to the root bridge. If the switch determines that it still has an alternate path to the root, it causes the maximum aging time on the ports on which it received the inferior BPDU to expire. If all the alternate paths to the root bridge indicate that the switch has lost connectivity to the root bridge, the switch causes the maximum aging times on the ports on which it received an inferior BPDU to expire. If one or more alternate paths can still connect to the root bridge, the switch makes all ports on which it received an inferior BPDU its designated ports and moves them out of the blocking state (if they were in the blocking state) through the listening and learning states and into the forwarding state.
Figure 9-3 shows an example topology with no link failures. Switch A, the root switch, connects directly to Switch B over link L1 and to Switch C over link L2. The port on Switch C that connects directly to Switch B is in the blocking state.
Figure 9-3 BackboneFast Example Before Indirect Link Failure
If link L1 fails, Switch C detects this failure as an indirect failure, because it is not connected directly to link L1. Switch B no longer has a path to the root switch. BackboneFast allows the blocked port on Switch C to move immediately to the listening state without waiting for the maximum aging time for the port to expire. BackboneFast then transitions the port on Switch C to the forwarding state, providing a path from Switch B to Switch A. This switchover takes approximately 30 seconds. Figure 9-4 shows how BackboneFast reconfigures the topology to account for the failure of link L1.
Figure 9-4 BackboneFast Example After Indirect Link Failure
If a new switch is introduced into a shared-medium topology, BackboneFast is not activated. Figure 9-5 shows a shared-medium topology in which a new switch is added. The new switch begins sending inferior BPDUs that say it is the root switch. However, the other switches ignore these inferior BPDUs and the new switch learns that Switch B is the designated bridge to Switch A, the root switch.
Figure 9-5 Adding a Switch in a Shared-Medium Topology
Understanding How Loop Guard Works
Unidirectional link failures may cause a root port or alternate port to become designated as root if BPDUs are absent. Some software failures may introduce temporary loops in the network. The loop guard feature checks if a root port or an alternate root port receives BPDUs. If the port is not receiving BPDUs, loop guard puts the port into an inconsistent state until it starts receiving BPDUs again. Loop guard isolates the failure and lets spanning tree converge to a stable topology without the failed link or bridge.
You can enable loop guard on a per-port basis. When you enable loop guard, it is automatically applied to all of the active instances or VLANs to which that port belongs. When you disable loop guard, it is disabled for the specified ports. Disabling loop guard moves all loop-inconsistent ports to the listening state.
If you enable loop guard on a channel and the first link becomes unidirectional, loop guard blocks the entire channel until the affected port is removed from the channel. Figure 9-6 shows loop guard in a triangle switch configuration.
Figure 9-6 Triangle Switch Configuration with Loop Guard
Figure 9-6 illustrates the following configuration:
•
Switches A and B are distribution switches.
•
Switch C is an access switch.
•
Loop guard is enabled on ports 3/1 and 3/2 on Switches A, B, and C.
Use loop guard only in topologies where there are blocked ports. Topologies that have no blocked ports, which are loop free, do not need to enable this feature. Enabling loop guard on a root switch has no effect but provides protection when a root switch becomes a nonroot switch.
Follow these guidelines when using loop guard:
•
You cannot enable loop guard on PortFast-enabled or dynamic VLAN ports.
•
You cannot enable PortFast on loop guard-enabled ports.
•
You cannot enable loop guard if root guard is enabled.
Loop guard interacts with other features as follows:
•
Loop guard does not affect the functionality of UplinkFast or BackboneFast.
•
Do not enable loop guard on ports that are connected to a shared link.
Note
We recommend that you enable loop guard on root ports and alternate root ports on access switches.
•
Root guard forces a port to be always designated as the root port. Loop guard is effective only if the port is a root port or an alternate port. You cannot enable loop guard and root guard on a port at the same time.
•
PortFast transitions a port into a forwarding state immediately when a link is established. Because a PortFast-enabled port will not be a root port or alternate port, loop guard and PortFast cannot be configured on the same port. Assigning dynamic VLAN membership for the port requires that the port is PortFast enabled. You cannot configure a loop guard-enabled port with dynamic VLAN membership.
•
If your network has a type-inconsistent port or a PVID-inconsistent port, all BPDUs are dropped until the misconfiguration is corrected. The port transitions out of the inconsistent state after the message age expires. Loop guard ignores the message age expiration on type-inconsistent ports and PVID-inconsistent ports. If the port is already blocked by loop guard, misconfigured BPDUs that are received on the port make loop guard recover, but the port is moved into the type-inconsistent state or PVID-inconsistent state.
•
In high-availability switch configurations, if a port is put into the blocked state by loop guard, it remains blocked even after switchover to the redundant supervisor engine. The newly activated supervisor engine recovers the port only after receiving a BPDU on that port.
•
Loop guard uses the ports known to spanning tree. Loop guard can take advantage of logical ports that are provided by the Port Aggregation Protocol (PAgP). However, to form a channel, all the physical ports that are grouped in the channel must have compatible configurations. PAgP enforces uniform configurations of root guard or loop guard on all the physical ports to form a channel.
These caveats apply to loop guard:
–
Spanning tree always chooses the first operational port in the channel to send the BPDUs. If that link becomes unidirectional, loop guard blocks the channel, even if other links in the channel are functioning properly.
–
If a set of ports that are already blocked by loop guard are grouped together to form a channel, spanning tree loses all the state information for those ports and the new channel port may obtain the forwarding state with a designated role.
–
If a channel is blocked by loop guard and the channel breaks, spanning tree loses all the state information. The individual physical ports may obtain the forwarding state with the designated role, even if one or more of the links that formed the channel are unidirectional.
Note
You can enable UniDirectional Link Detection (UDLD) to help isolate the link failure. A loop may occur until UDLD detects the failure, but loop guard will not be able to detect it.
•
Loop guard has no effect on a disabled spanning tree instance or a VLAN.
Configuring PortFast
These sections describe how to configure spanning tree PortFast on the switch:
•
Enabling PortFast on an Access Port
•
Enabling Spanning Tree PortFast on a Trunk Port
•
Disabling PortFast
•
Resetting PortFast
Enabling PortFast on an Access Port
Caution 
You can use PortFast to connect a single end station or a switch port to a switch port. If you enable PortFast on a port that is connected to another Layer 2 device, such as a switch, you might create network loops.
To enable PortFast on a switch port, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable PortFast on a switch port that is connected to a single workstation, switch, or server.
|
set spantree portfast mod_num/port_num enable | disable
|
Step 2
|
Verify the PortFast setting on a switch port.
|
show spantree [mod_num/port_num] [vlan]
|
This example shows how to enable PortFast on port 1 of module 4 and verify the configuration; the PortFast status is shown in the "Fast-Start" column:
Console> (enable) set spantree portfast 4/1 enable
Warning:Connecting Layer 2 devices to a fast start port can cause
temporary spanning tree loops. Use with caution.
Spantree port 4/1 fast start enabled.
Console> (enable) show spantree 4/1
Port Vlan Port-State Cost Priority Fast-Start Group-method
--------- ---- ------------- ----- -------- ---------- ------------
4/1 1 blocking 19 20 enabled
4/1 100 forwarding 10 20 enabled
4/1 521 blocking 19 20 enabled
4/1 522 blocking 19 20 enabled
4/1 523 blocking 19 20 enabled
4/1 524 blocking 19 20 enabled
4/1 1003 not-connected 19 20 enabled
4/1 1005 not-connected 19 4 enabled
Note
If the designation for a port is displayed as edge, that port is also a PortFast port. See the "Edge Ports" section.
Enabling Spanning Tree PortFast on a Trunk Port
Caution 
You can use PortFast to connect a single end station or a switch port to a switch port. If you enable PortFast on a port that is connected to another Layer 2 device, such as a switch, you might create network loops.
To enable PortFast on a trunk port, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable PortFast on a trunk port that is connected to a single workstation, switch, or server.
|
set spantree portfast mod_num/port_num enable trunk
Note If you issue the set spantree portfast command on a trunk port without using the trunk keyword, the trunk port will stay in disable mode.
|
Step 2
|
Verify the PortFast setting on a trunk port.
|
show spantree portfast [mod_num/port_num]
|
This example shows how to enable PortFast on port 1 of module 4 of a trunk port, bring the trunk port to a forwarding state, and verify the configuration (the PortFast status is shown in the "Fast-Start" column):
Console> (enable) set spantree portfast 4/1 enable trunk
Warning:Connecting Layer 2 devices to a fast start port can cause
temporary spanning tree loops. Use with caution.
Spantree port 4/1 fast start enabled.
Console> (enable) show spantree 4/1
Port Vlan Port-State Cost Prio Portfast
------------------------ ---- ------------- --------- ---- ------------------
4/1 1 blocking 4 32 enabled 0
4/1 100 forwarding 4 32 enabled 0
4/1 521 blocking 4 32 enabled 0
4/1 524 blocking 4 32 enabled 0
4/1 1003 not-connected 4 32 enabled 0
4/1 1005 not-connected 4 32 enabled 0
Console> (enable) show spantree portfast 4/1
Portfast BPDU guard is disabled.
Portfast BPDU filter is disabled.
Note
When PortFast is enabled between two switches, the system will verify that there are no loops in the network before bringing the blocking trunk to a forwarding state.
Disabling PortFast
To disable PortFast on a switch or trunk port, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable PortFast on a switch port.
|
set spantree portfast mod_num/port_num disable
|
Step 2
|
Verify the PortFast setting.
|
show spantree mod_num/port_num
|
This example shows how to disable PortFast on port 1 of module 4:
Console> (enable) set spantree portfast 4/1 disable
Spantree port 4/1 fast start disabled.
Resetting PortFast
To reset PortFast on a switch or trunk port to its default settings, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Reset PortFast to its default settings on a switch port.
|
set spantree portfast mod_num/port_num default
|
Step 2
|
Verify the PortFast setting.
|
show spantree mod_num/port_num
|
This example shows how to reset PortFast to its default settings on port 1 of module 4:
Console> (enable) set spantree portfast 4/1 default
Spantree port 4/1 fast start set to default.
Console> (enable) show spantree portfast 4/1
Portfast BPDU guard is disabled.
Portfast BPDU filter is disabled.
Configuring PortFast BPDU Guard
These sections describe how to configure PortFast BPDU guard on the switch:
•
Enabling PortFast BPDU Guard
•
Disabling PortFast BPDU Guard
Enabling PortFast BPDU Guard
The PortFast feature is configured on an individual port and the PortFast BPDU guard option is configured either globally or on a per-port basis.
When you disable PortFast on a port, PortFast BPDU guard becomes inactive. Port configuration overrides global configuration unless port configuration is set to default. If port configuration is set to default, global configuration is checked. If the port configuration is enabled, the port configuration is used and the global configuration is not used.
To enable PortFast BPDU guard on a nontrunking switch port, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable BPDU guard on an individual port.
|
set spantree portfast bpdu-guard mod/port [disable | enable | default]
|
Step 2
|
Verify the PortFast BPDU guard setting.
|
show spantree summary
|
This example shows how to enable PortFast BPDU guard on the switch and verify the configuration in the Per VLAN Spanning Tree + (PVST+) mode:
Note
For additional PVST+ information, see "Configuring Spanning Tree."
Console> (enable) set spantree portfast bpdu-guard 6/1 enable
Spantree port 6/1 bpdu guard enabled.
Console> (enable) show spantree summary
Root switch for vlans: none.
Portfast bpdu-guard enabled for bridge.
Uplinkfast disabled for bridge.
Backbonefast disabled for bridge.
Vlan Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Disabling PortFast BPDU Guard
To disable PortFast BPDU guard on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable PortFast BPDU guard on the switch.
|
set spantree portfast bpdu-guard mod/port [disable | enable | default]
|
Step 2
|
Verify the PortFast BPDU guard setting.
|
show spantree summary
|
This example shows how to disable PortFast BPDU guard on the switch and verify the configuration:
Console> (enable) set spantree portfast bpdu-guard disable
Spantree portfast bpdu-guard disabled on this switch.
Console> (enable) show spantree summary
Summary of connected spanning tree ports by vlan
Portfast bpdu-guard disabled for bridge.
Uplinkfast disabled for bridge.
Backbonefast disabled for bridge.
Vlan Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Configuring PortFast BPDU Filtering
These sections describe how to configure PortFast BPDU filtering on the switch:
•
Enabling PortFast BPDU Filtering
•
Disabling PortFast BPDU Filtering
Enabling PortFast BPDU Filtering
To enable PortFast BPDU filtering on a nontrunking port, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable the BPDU filter state on the port.
|
set spantree portfast bpdu-filter mod/port [disable | enable | default]
|
Step 2
|
Verify the PortFast BPDU filter setting.
|
show spantree summary
|
BPDU filtering is set to default on each port. This example shows how to enable PortFast BPDU filtering on the port and verify the configuration in PVST+ mode:
Note
For PVST+ information, see "Configuring Spanning Tree."
Console> (enable) set spantree portfast bpdu-filter 6/1 enable
Warning:Ports enabled with bpdu filter will not send BPDUs and drop all
received BPDUs. You may cause loops in the bridged network if you misuse
Console> (enable) show spantree summary
Root switch for vlans: none.
Portfast bpdu-filter enabled for bridge.
Uplinkfast disabled for bridge.
Backbonefast disabled for bridge.
Vlan Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Disabling PortFast BPDU Filtering
To disable PortFast BPDU filtering on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable PortFast BPDU filtering on the switch.
|
set spantree portfast bpdu-filter disable
|
Step 2
|
Verify the PortFast BPDU filtering setting.
|
show spantree summary show portfast
|
This example shows how to disable PortFast BPDU filtering on the switch and verify the configuration:
Console> (enable) set spantree portfast bpdu-filter disable
Spantree portfast bpdu-filter disabled on this switch.
Console> (enable) show spantree summary
Summary of connected spanning tree ports by vlan
Portfast bpdu-filter disabled for bridge.
Uplinkfast disabled for bridge.
Backbonefast disabled for bridge.
Vlan Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Configuring UplinkFast
You can configure UplinkFast for PVST+ or for Multi-Instance Spanning Tree Protocol (MISTP). The command is the same but the output may be slightly different.
Note
For additional MISTP information, see "Configuring Spanning Tree."
These sections describe how to configure UplinkFast on the switch:
•
Enabling UplinkFast
•
Disabling UplinkFast
Enabling UplinkFast
The set spantree uplinkfast enable command increases the path cost of all ports on the switch, making it unlikely that the switch will become the root switch. The station_update_rate value represents the number of multicast packets that are transmitted per 100 milliseconds (the default is 15 packets per millisecond).
Note
When you enable the set spantree uplinkfast command, it affects all VLANs on the switch. You cannot configure UplinkFast on an individual VLAN.
To enable UplinkFast on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable UplinkFast on the switch.
|
set spantree uplinkfast enable [rate station_update_rate] [all-protocols off | on]
|
Step 2
|
Verify that UplinkFast is enabled.
|
show spantree uplinkfast [{mistp-instance [instances]}| vlans]
|
With PVST+ mode enabled, this example shows how to enable UplinkFast with a station-update rate of 40 packets per 100 milliseconds and how to verify that UplinkFast is enabled:
Console> (enable) set spantree uplinkfast enable
VLANs 1-4094 bridge priority set to 49152.
The port cost and portvlancost of all ports set to above 3000.
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
uplinkfast enabled for bridge.
Console> (enable) show spantree uplinkfast 1 100 521-524
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
-----------------------------------------------
This example shows how to display the UplinkFast feature settings for all VLANs:
Console> show spantree uplinkfast
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
------------------------------------------------
21-50 1/9(fwd), 1/6-1/8, 1/10-1/12
With MISTP mode enabled, this example shows the output when you enable UplinkFast:
Console> (enable) set spantree uplinkfast enable
Instances 1-16 bridge priority set to 49152.
The port cost and portinstancecost of all ports set to above 10000000.
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
uplinkfast enabled for bridge.
This example shows how to display the UplinkFast feature settings for a specific instance:
Console> show spantree uplinkfast mistp-instance 1
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
------------------------------------------------
Disabling UplinkFast
The set spantree uplinkfast disable command disables UplinkFast on the switch, but the switch priority and port cost values are not reset to the factory defaults.
Note
When you enter the set spantree uplinkfast disable command, it affects all VLANs on the switch. You cannot disable UplinkFast on an individual VLAN.
To disable UplinkFast on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable UplinkFast on the switch.
|
set spantree uplinkfast disable
|
Step 2
|
Verify that UplinkFast is disabled.
|
show spantree uplinkfast
|
With PVST+ mode enabled, this example shows how to disable UplinkFast on the switch and verify the configuration:
Console> (enable) set spantree uplinkfast disable
Uplinkfast disabled for switch.
Use clear spantree uplinkfast to return stp parameters to default.
Console> (enable) show spantree uplinkfast
Station update rate set to 15 packets/100ms.
uplinkfast all-protocols field set to off.
-----------------------------------------------
Configuring BackboneFast
These sections describe how to configure BackboneFast:
•
Enabling BackboneFast
•
Displaying BackboneFast Statistics
•
Disabling BackboneFast
Enabling BackboneFast
Note
For BackboneFast to work, you must enable it on all switches in the network. BackboneFast is not supported on Token Ring VLANs. This feature is supported for use with third-party switches.
To enable BackboneFast on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable BackboneFast on the switch.
|
set spantree backbonefast enable
|
Step 2
|
Verify that BackboneFast is enabled.
|
show spantree backbonefast
|
This example shows how to enable BackboneFast on the switch and how to verify the configuration:
Console> (enable) set spantree backbonefast enable
Backbonefast enabled for all VLANs
Console> (enable) show spantree backbonefast
Displaying BackboneFast Statistics
To display BackboneFast statistics, perform this task in privileged mode:
Task
|
Command
|
Display BackboneFast statistics.
|
show spantree summary
|
This example shows how to display BackboneFast statistics:
Console> (enable) show spantree summary
Summary of connected spanning tree ports by vlan
Uplinkfast disabled for bridge.
Backbonefast enabled for bridge.
Vlan Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Blocking Listening Learning Forwarding STP Active
----- -------- --------- -------- ---------- ----------
Number of inferior BPDUs received (all VLANs) : 0
Number of RLQ req PDUs received (all VLANs) : 0
Number of RLQ res PDUs received (all VLANs) : 0
Number of RLQ req PDUs transmitted (all VLANs) : 0
Number of RLQ res PDUs transmitted (all VLANs) : 0
Disabling BackboneFast
To disable BackboneFast on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable BackboneFast.
|
set spantree backbonefast disable
|
Step 2
|
Verify that BackboneFast is disabled.
|
show spantree backbonefast
|
This example shows how to disable BackboneFast and how to verify the configuration:
Console> (enable) set spantree backbonefast disable
Backbonefast enabled for all VLANs
Console> (enable) show spantree backbonefast
Configuring Loop Guard
These sections describe how to configure loop guard:
•
Enabling Loop Guard
•
Disabling Loop Guard
Enabling Loop Guard
Use the set spantree guard command to enable or disable the spanning tree loop guard feature on a per-port basis.
To enable loop guard on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Enable loop guard on a port.
|
set spantree guard loop mod/port
|
Step 2
|
Verify that loop guard is enabled.
|
show spantree guard {mod/port | vlan} mistp-instance instance
|
This example shows how to enable loop guard:
Console> (enable) set spantree guard loop 5/1
Rootguard is enabled on port 5/1, enabling loopguard will disable rootguard on this port.
Do you want to continue (y/n) [n]? y
Loopguard on port 5/1 is enabled.
Disabling Loop Guard
To disable loop guard on the switch, perform this task in privileged mode:
| |
Task
|
Command
|
Step 1
|
Disable loop guard on a port.
|
set spantree guard none mod/port
|
Step 2
|
Verify that loop guard is disabled.
|
show spantree guard {mod/port | vlan} mistp-instance instance
|
This example shows how to disable loop guard:
Console> (enable) set spantree guard none 5/1
Rootguard is disabled on port 5/1, disabling loopguard will disable rootguard on this
port.
Do you want to continue (y/n) [n]? y
Loopguard on port 5/1 is disabled.