Handshake mechanisms, Handshake when no root port is elected – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 442

Advertising
background image

412

Multi-Service IronWare Switching Configuration Guide

53-1003036-02

State machines

13

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 75

, 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 RSTP mode may enter a learning state to allow MAC address 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 RSTP mode and if the port meets the conditions for rapid transition.

Handshake mechanisms

To rapidly transition a Designated or Root port into a forwarding state, the Port Role Transition state
machine uses handshake mechanisms to ensure loop free operations. It uses one type of
handshake if no Root port has been assigned on a bridge, and another type if a Root port has
already been assigned.

Handshake when no root port is elected

If a Root port has not been assigned on a bridge, RSTP uses the Proposing -> Proposed -> Sync ->
Synced -> Agreed handshake:

Proposing – The Designated port on the root bridge sends an RST BPDU packet to its peer port
that contains a proposal flag. The proposal flag is a signal that indicates that the Designated
port is ready to put itself in a forwarding state (

Figure 75

). The Designated port continues to

send this flag in its RST BPDU until it is placed in a forwarding state (

Figure 78

) or is forced to

operate in 802.1D mode. (Refer to

“Compatibility of RSTP with 802.1D”

.)

Proposed – When a port receives an RST BPDU with a proposal flag from the Designated port
on its point-to-point link, it asserts the Proposed signal and one of the following occurs
(

Figure 75

):

If the RST BPDU that the port receives is superior to what it can transmit, the port
assumes the role of a Root port. (Refer to the section on

“Bridges and bridge port roles”

.)

If the RST BPDU that the port receives is inferior to what it can transmit, then the port is
given the role of Designated port.

NOTE

Proposed will never be asserted if the port is connected on a shared media link.

In

Figure 75

, Port3/Switch 200 is elected as the Root port

Advertising