Download This Guide
Supported Platforms
Configuring Rapid Spanning-Tree Protocol
You can configure Rapid Spanning-Tree Protocol (RSTP) under the following hierarchy levels:
- [edit logical-systems logical-system-name protocols]
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
- [edit protocols]
- [edit routing-instances routing-instance-name protocols]
The routing instance type can be either virtual-switch or layer2-control.
To configure the Rapid Spanning-Tree Protocol:
- Enable RSTP as the version of spanning-tree
protocol to be configured:
[edit]
user@host@ edit ... protocols (STP Type) rstp (Optional) For compatibility with older bridges that do not support RSTP, you can run force RSTP to run as the original IEEE 802.1D Spanning-Tree Protocol (STP) version:
[edit ... protocols rstp]user@host# set force-version stpNote: If RSTP has been forced to run as the original STP version, you can revert back to RSTP by first removing the force-version statement from the configuration and then entering the clear spanning-tree protocol-migration configuration mode command.
- (Optional) Enable provider bridge participation
in the RSTP instance:
[edit ... protocols rstp]
user@host# set bpdu-destination-mac-address provider-bridge-group - (Optional) Specify the extended system identifier
used in identifiers bridges that participate in RSTP:
[edit ... protocols rstp]
user@host# set extended-system-id identifier Configure the interfaces that participate in the RSTP instance.
- Enable configuration of the interface:
[edit ... protocols rstp]
user@host# edit interface interface-name - Configure the interface priority:
[edit ... protocols rstp interface interface-name]
user@host# set priority interface-priority - (Optional) By default, the interface link cost is determined
by the link speed. You can configure the interface link cost to control
which bridge is the designated bridge and which port is the designated
port:
[edit ... protocols rstp interface interface-name]
user@host# set cost interface-link-cost - Configure the interface link mode to identify point-to-point
links:
[edit ... protocols rstp interface interface-name]
user@host# set mode (p2p | shared)Specify p2p if the link is point to point. Specify shared is the link is a shared media.
- (Optional) Configure the interface as an edge port:
[edit ... protocols rstp interface interface-name]
user@host# set edgeEdge ports do not expect to receive bridge protocol data unit (BPDU) packets. If a BPDU packet is received for an edge port, the port becomes a nonedge port
- Enable configuration of the interface:
- Configure the bridge priority
[edit ... protocols rstp]
user@host# set bridge-priority bridge-priorityFor more information, see Bridge Priority for Election of Root Bridge and Designated Bridge.
Configure hello BPDU timers.
- Configure the maximum expected arrival time of hello BPDUs:
[edit ... protocols rstp]
user@host# set max-age seconds - Configure the time interval at which the root bridge transmits
configuration BPDUs:
[edit ... protocols rstp]
user@host# set hello-time seconds
- Configure the maximum expected arrival time of hello BPDUs:
- (Optional) By default, the bridge port remains
in the listening and learning states for 15 seconds before transitioning
to the forwarding state. You can specify a delay from 4 through 20 seconds instead:
[edit ... protocols rstp]
user@host# set forward-delay seconds Verify the RSTP configuration:
[edit]... { # Optional logical system and/or routing instanceprotocols (STP Type) {rstp {force-version stp; # Optional.bpdu-destination-mac-address provider-bridge-group; # Optionalextended-system-id identifier; # Optional.interface interface-name {priority interface-priority;cost interface-link-cost; # Optional.mode (p2p | shared);edge; # Optional.}bridge-priority bridge-priority;max-age seconds;hello-time seconds;forward-delay seconds; # Optional.}}}