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

NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access
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).
ERPS Single Ring Principles

ERPS Single Ring Principles

ERPS is a standard ring protocol used to prevent loops on ERPS rings at the Ethernet link layer. A router can have a maximum of two ports added to the same ERPS ring.

To prevent loops on an ERPS ring, you can enable a loop-breaking mechanism to block the Ring Protection Link (RPL) owner port to eliminate loops. If a link on the ring network fails, the ERPS-enabled router immediately unblocks the blocked port and performs link switching to restore communication between nodes on the ring network.

This section describes how ERPS is implemented on a single ring when links are normal, when a link fails, and when the link recovers (including protection switching operations).

Links Are Normal

On the network shown in Figure 12-8, Device A through Device E constitute a ring network, and they can communicate with each other.
  1. To prevent loops, ERPS blocks the RPL owner port and also the RPL neighbor port (if any is configured). All other ports can transmit service traffic.
  2. The RPL owner port sends R-APS (NR) messages to all other nodes on the ring at an interval of 5s, indicating that ERPS links are normal.
Figure 12-8 ERPS single ring networking (links are normal)

A Link Fails

As shown in Figure 12-9, if the link between Device D and Device E fails, the ERPS protection switching mechanism is triggered. The ports on both ends of the faulty link are blocked, and the RPL owner port and RPL neighbor port are unblocked to send and receive traffic. This mechanism ensures that traffic is not interrupted. The process is as follows:

  1. After Device D and Device E detect the link fault, they block their ports on the faulty link and perform a Filtering Database (FDB) flush.
  2. Device D and Device E send three consecutive R-APS Signal Fail (SF) messages to the other LSWs and then send one R-APS (SF) message at an interval of 5s afterwards.
  3. After receiving an R-APS (SF) message, the other LSWs perform an FDB flush. Device C on which the RPL owner port resides and Device B on which the RPL neighbor port resides unblock the respective RPL owner port and RPL neighbor port, and perform an FDB flush.
Figure 12-9 ERPS single ring networking (unblocking the RPL owner port and RPL neighbor port if a link fails)

The Link Recovers

After the link fault is rectified, either of two situations may occur:

  • If the ERPS ring uses revertive switching, the RPL owner port is blocked again, and the link that has recovered is used to forward traffic.
  • If the ERPS ring uses non-revertive switching, the RPL remains unblocked, and the link that has recovered remains blocked.

The following example uses revertive switching to describe the process after the link recovers.

  1. After the link between Device D and Device E recovers, Device D and Device E start a guard timer to avoid receiving out-of-date R-APS PDUs. The two routers do not receive any R-APS PDUs before the timer expires. At the same time, Device D and Device E send R-APS (NR) messages to the other LSWs.
  2. After receiving an R-APS (NR) message, Device C on which the RPL owner port resides starts the WTR timer. After the WTR timer expires, Device C blocks the RPL owner port and sends R-APS (NR, RB) messages.
  3. After receiving an R-APS (NR, RB) message, Device D and Device E unblock the ports at the two ends of the link that has recovered, stop sending R-APS (NR) messages, and perform an FDB flush. The other LSWs also perform an FDB flush after receiving an R-APS (NR, RB) message.

Protection Switching

  • Forced switch

    On the network shown in Figure 12-10, Device A through Device E on the ERPS ring can communicate with each other. A forced switch (FS) operation is performed on the Device E's port that connects to Device D, and the Device E's port is blocked. The RPL owner port and RPL neighbor port are then unblocked to send and receive traffic. This ensures that traffic is not interrupted. The process is as follows:

    1. After the Device E's port that connects to Device D is forcibly blocked, Device E performs an FDB flush.
    2. Device E sends three consecutive R-APS (SF) messages to the other LSWs and then after 5s, sends another R-APS (SF) message.
    3. After receiving an R-APS (SF) message, the other LSWs perform an FDB flush. Device C on which the RPL owner port resides and Device B on which the RPL neighbor port resides unblock the respective RPL owner port and RPL neighbor port, and perform an FDB flush.
    Figure 12-10 Layer 2 ERPS ring networking (blocking a port by FS)

  • Clear

    After a clear operation is performed on Device E, the port that is forcibly blocked by FS sends R-APS (NR) messages to all other ports on the ERPS ring.

    • If the ERPS ring uses revertive switching, the RPL owner port starts the WTB timer after receiving an R-APS (NR) message. After the WTB timer expires, the FS operation is cleared. The RPL owner port is then blocked, and the blocked port on Device E is unblocked. If you perform a clear operation on Device C on which the RPL owner port resides before the WTB timer expires, the RPL owner port is immediately blocked, and the blocked port on Device E is unblocked.
    • If the ERPS ring uses non-revertive switching and you want to block the RPL owner port, perform a clear operation on Device C on which the RPL owner port resides.
  • Manual switch

    Compared with an FS operation, a manual switch (MS) operation triggers protection switching in a similar way except that an MS operation does not take effect in FS, MS, or link failure conditions.

Download
Updated: 2019-01-02

Document ID: EDOC1100058405

Views: 16331

Downloads: 18

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