No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - Ethernet Switching

AR650, AR1600, and AR6100 V300R003

This document describes how to configure the components for LAN services, including link aggregation groups, VLANs, voice VLANs, MAC address tables, transparent bridging, as well as GVRP, STP/RSTP, and MSTP protocols.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
RSTP Technology Details

RSTP Technology Details

The Proposal/Agreement mechanism enables a designated port to enter the Forwarding state quickly. As shown in Figure 10-13, root bridge S1 establishes a link with S2. On S2, p2 is an alternate port; p3 is a designated port and is in the Forwarding state; p4 is an edge port.

Figure 10-13  Proposal/Agreement negotiation process

The Proposal/Agreement mechanism works as follows:
  1. p0 and p1 become designated ports and send RST BPDUs to each other.
  2. The RST BPDU sent from p0 is superior to that of p1, so p1 becomes a root port and stops sending RST BPDUs.
  3. p0 enters the Discarding state and sets the Proposal field in its RST BPDU to 1.
  4. After S2 receives an RST BPDU with the Proposal field set to 1, it sets the sync variable to 1 for all its ports.
  5. As p2 has been blocked, its state remains unchanged. p4 is an edge port and does not participate in calculation. Therefore, only the non-edge designated port p3 needs to be blocked.
  6. After the synced variable of each port is set to 1, p2 and p3 enter the Discarding state, and p1 enters the Forwarding state and returns an RST BPDU with the Agreement field being set to 1 to S1. This RST BPDU carries the same information as that in the BPDU sent by the root bridge, except that the Agreement field is set to 1 and the Proposal field is set to 0.
  7. After S1 receives this RST BPDU, it identifies that the RST BPDU is a response to the proposal that it has sent. Then p0 immediately enters the Forwarding state.

The proposal/agreement process can proceed to downstream devices.

STP can select designated ports quickly; however, to prevent loops, all ports must wait at least one Forward Delay interval before starting data forwarding. RSTP blocks non-root ports to prevent loops and uses the proposal/agreement mechanism to shorten the time that an upstream port waits before transitioning to the Forwarding state.

NOTE:

The proposal/agreement mechanism applies only to P2P full-duplex links between two switching devices. When proposal/agreement fails, a designated port is elected after two Forward Delay intervals, same as designated port election in STP mode.

RSTP Topology Changes

RSTP considers that the network topology has changed when a non-edge port transitions to the Forwarding state.

When detecting a topology change, RSTP devices react as follows:
  • The local device starts a TC While timer on each non-edge designated port. The TC While timer value is two times the Hello timer value.

    Within the TC While time, the local device clears MAC address entries learned on ports whose states have changed.

    At the same time, these ports send out RST BPDUs with the TC bit set to 1. When the TC While timer expires, the ports stop sending RST BPDUs.

  • When other switching devices receive RST BPDUs, they clear MAC address entries learned on all their ports except the ports that receive the RST BPDUs. These switching devices also start a TC While timer on each non-edge designated port and repeat the preceding process.

RST BPDUs are then flooded on the entire network.

Interoperability with STP

RSTP can interoperate with STP, but its advantages such as fast convergence are lost when it interoperates with STP.

On a network with both STP-capable and RSTP-capable devices, STP-capable devices drop RST BPDUs. If a port on an RSTP-capable device receives a configuration BPDU from an STP-capable device, the port switches to the STP mode and starts to send configuration BPDUs after two Hello intervals.

After STP-capable devices are removed, Huawei RSTP-capable devices can switch back to the RSTP mode.

Download
Updated: 2019-04-12

Document ID: EDOC1100041791

Views: 62854

Downloads: 40

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next