Configuring Spanning Tree Protocol (STP) and IronSpan Features
December 2005
© Foundry Networks, Inc.
7 - 23
State Machines
The bridge uses the Port Role Selection state machine to determine if port role changes are required on the
bridge. This state machine performs a computation when one of the following events occur:
•
New information is received on any port on the bridge
•
The timer expires for the current information on a port on the bridge
Each port uses the following state machines:
•
Port Information – This state machine keeps track of spanning-tree information currently used by the port. It
records the origin of the information and ages out any information that was derived from an incoming BPDU.
•
Port Role Transition – This state machine keeps track of the current port role and transitions the port to the
appropriate role when required. It moves the Root port and the Designated port into forwarding states and
moves the Alternate and Backup ports into discarding states.
•
Port Transmit – This state machine is responsible for BPDU transmission. It checks to ensure only the
maximum number of BPDUs per hello interval are sent every second. Based on what mode it is operating in,
it sends out either legacy BPDUs or RST BPDUs. In this document legacy BPDUs are also referred to as STP
BPDUs.
•
Port Protocol Migration – This state machine deals with compatibility with 802.1D bridges. When a legacy
BPDU is detected on a port, this state machine configures the port to transmit and receive legacy BPDUs and
operate in the legacy mode.
•
Topology Change – This state machine detects, generates, and propagates topology change notifications. It
acknowledges Topology Change Notice (TCN) messages when operating in 802.1D mode. It also flushes the
MAC table when a topology change event takes place.
•
Port State Transition – This state machine transitions the port to a discarding, learning, or forwarding state
and performs any necessary processing associated with the state changes.
•
Port Timers – This state machine is responsible for triggering any of the state machines described above,
based on expiration of specific port timers.
In contrast to the 802.1D standard, the 802.1W standard does not have any bridge specific timers. All timers in the
CLI are applied on a per-port basis, even though they are configured under bridge parameters.
802.1W state machines attempt to quickly place the ports into either a forwarding or discarding state. Root ports
are quickly placed in forwarding state when both of the following events occur:
•
It is assigned to be the Root port.
•
It receives an RST BPDU with a proposal flag from a Designated port. The proposal flag is sent by ports with
a Designated role when they are ready to move into a forwarding state.
When a the role of Root port is given to another port, the old Root port is instructed to reroot. The old Root port
goes into a discarding state and negotiates with its peer port for a new role and a new state. A peer port is the port
on the other bridge to which the port is connected. For example, in Figure 7.4, Port1 of Switch 200 is the peer port
of Port2 of Switch 100.
A port with a Designated role is quickly placed into a forwarding state if one of the following occurs:
•
The Designated port receives an RST BPDU that contains an agreement flag from a Root port
•
The Designated port is an Edge port
However, a Designated port that is attached to an Alternate port or a Backup port must wait until the forward delay
timer expires twice on that port while it is still in a Designated role, before it can proceed to the forwarding state.
Backup ports are quickly placed into discarding states.
Alternate ports are quickly placed into discarding states.
A port operating in 802.1W mode may enter a learning state to allow MAC entries to be added to the filtering
database; however, this state is transient and lasts only a few milliseconds, if the port is operating in 802.1W mode
and if the port meets the conditions for rapid transition.
Содержание FastIron Edge Switch X424
Страница 36: ...Foundry Configuration Guide for the FESX FSX and FWSX 2 12 Foundry Networks Inc December 2005...
Страница 56: ...Foundry Configuration Guide for the FESX FSX and FWSX 3 20 Foundry Networks Inc December 2005...
Страница 70: ...Foundry Configuration Guide for the FESX FSX and FWSX 4 14 Foundry Networks Inc December 2005...
Страница 198: ...Foundry Configuration Guide for the FESX FSX and FWSX 8 38 Foundry Networks Inc December 2005...
Страница 316: ...Foundry Configuration Guide for the FESX FSX and FWSX 12 26 Foundry Networks Inc December 2005...
Страница 334: ...Foundry Configuration Guide for the FESX FSX and FWSX 13 18 Foundry Networks Inc December 22 2005...
Страница 350: ...Foundry Configuration Guide for the FESX FSX and FWSX 15 12 Foundry Networks Inc December 2005...
Страница 458: ...Foundry Configuration Guide for the FESX FSX and FWSX 18 18 Foundry Networks Inc December 2005...
Страница 712: ...Foundry Configuration Guide for the FESX FSX and FWSX 22 32 Foundry Networks Inc December 2005...
Страница 760: ...Foundry Configuration Guide for the FESX FSX and FWSX A 34 Foundry Networks Inc December 2005...
Страница 796: ...Foundry Configuration Guide for the FESX FSX and FWSX C 18 Foundry Networks Inc December 2005...
Страница 820: ...Foundry Configuration Guide for the FESX FSX and FWSX E 10 Foundry Networks Inc December 2005...