An interface can be configured for either loop protection or root protection, but not for
both.
Related
Documentation
Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from
Blocking to Forwarding in a Spanning Tree on EX Series Switches on page 1569
•
•
Understanding Root Protection for STP, RSTP, VSTP, and MSTP on EX Series Switches
on page 1524
•
Understanding BPDU Protection for STP, RSTP, and MSTP on EX Series Switches on
page 1522
•
Understanding MSTP for EX Series Switches on page 1521
•
Understanding RSTP for EX Series Switches on page 1520
•
Understanding STP for EX Series Switches on page 1519
•
Understanding VSTP for EX Series Switches on page 1525
Understanding Root Protection for STP, RSTP, VSTP, and MSTP on EX Series Switches
Juniper Networks EX Series Ethernet Switches provide Layer 2 loop prevention through
Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning
Tree Protocol (VSTP), and Multiple Spanning Tree Protocol (MSTP). A loop-free network
is supported through the exchange of a special type of frame called bridge protocol data
unit (BPDU). Peer STP applications running on the switch interfaces use BPDUs to
communicate. Ultimately, the exchange of BPDUs determines which interfaces block
traffic and which interfaces become root ports and forward traffic.
However, a root port elected through this process has the possibility of being wrongly
elected. A user bridge application running on a PC can generate BPDUs, too, and interfere
with root port election. Root protection allows network administrators to manually
enforce the root bridge placement in the network.
Enable root protection on interfaces that should not receive superior BPDUs from the
root bridge and should not be elected as the root port. These interfaces become
designated ports and are typically located on an administrative boundary. If the bridge
receives superior STP BPDUs on a port that has root protection enabled, that port
transitions to a root-prevented STP state (inconsistency state) and the interface is
blocked. This blocking prevents a bridge that should not be the root bridge from being
elected the root bridge. After the bridge stops receiving superior STP BPDUs on the
interface with root protection, the interface returns to a listening state, followed by a
learning state, and ultimately back to a forwarding state. Recovery back to the forwarding
state is automatic.
When root protection is enabled on an interface, it is enabled for all the STP instances
on that interface. The interface is blocked only for instances for which it receives superior
BPDUs. Otherwise, it participates in the spanning-tree topology.
An interface can be configured for either root protection or loop protection, but not for
both.
Copyright © 2010, Juniper Networks, Inc.
1524
Complete Software Guide for Junos
®
OS for EX Series Ethernet Switches, Release 10.3
Summary of Contents for JUNOS OS 10.3 - SOFTWARE
Page 325: ...CHAPTER 17 Operational Mode Commands for System Setup 229 Copyright 2010 Juniper Networks Inc ...
Page 1323: ...CHAPTER 56 Operational Mode Commands for Interfaces 1227 Copyright 2010 Juniper Networks Inc ...
Page 2841: ...CHAPTER 86 Operational Commands for 802 1X 2745 Copyright 2010 Juniper Networks Inc ...
Page 3367: ...CHAPTER 113 Operational Mode Commands for CoS 3271 Copyright 2010 Juniper Networks Inc ...
Page 3435: ...CHAPTER 120 Operational Mode Commands for PoE 3339 Copyright 2010 Juniper Networks Inc ...
Page 3529: ...CHAPTER 126 Operational Mode Commands for MPLS 3433 Copyright 2010 Juniper Networks Inc ...