Related
Documentation
Understanding Loop Protection for Spanning-Tree Instance Interfaces on page 426•
• Loop Protection for a Spanning-Tree Instance Interface on page 427
• Example: Enabling Loop Protection for Spanning-Tree Protocols on page 429
Example: Enabling Loop Protection for Spanning-Tree Protocols
This example blocks and logs the non-designated RSTP port ge-1/2/0 after the BPDU
timeout interval expires:
[edit]
protocols {
rstp {
interface ge-1/2/0 {
bpdu-timeout-action block;
}
}
}
NOTE: This is not a complete configuration. You must also fully configure
RSTP, including the ge-1/2/0 interface.
Related
Documentation
Loop Protection for a Spanning-Tree Instance Interface on page 427•
• Understanding Loop Protection for Spanning-Tree Instance Interfaces on page 426
Understanding Root Protection for Spanning-Tree Instance Interfaces in a Layer 2
Switched Network
Root protect helps to enforce the root bridge placement in a Layer 2 switched network.
Enable root protect on interfaces that should not receive superior bridge protocol data
units (BPDUs) from the root bridge. Typically, these ports are spanning tree
protocol-designated ports on an administrative boundary. Enabling root protect ensures
the port remains a spanning-tree designated port.
When root protect is enabled on an interface, it is enabled for all spanning-tree protocol
instances on that interface. The interface is blocked only for those instances that receive
superior BPDUs.
By default, root protect is disabled.
If the bridge receives superior BPDUs on a port that has root protect enabled, that port
transitions to a root-prevented STP state and the interface is blocked. This prevents a
bridge that should not be the root bridge from being elected the root bridge.
After the bridge stops receiving superior BPDUs on the port with root protect enabled
and the received BPDUs time out, that port transitions back to the STP-designated port
state.
429Copyright © 2017, Juniper Networks, Inc.
Chapter 12: Configuring Layer 2 Control Protocol