01-12 ERPS (G 8032) Configuration

CloudEngine 8800, 7800, 6800, and 5800 Series
Switches
Configuration Guide - Ethernet Switching 12 ERPS (G.8032) Configuration
12 ERPS (G.8032) Configuration
This chapter describes how to configure Ethernet Ring Protection Switching

(ERPS). ERPS is a protocol defined by the International Telecommunication Union
- Telecommunication Standardization Sector (ITU-T) to eliminate loops at Layer 2.
It implements convergence of carrier-class reliability standards, and allows all
ERPS-capable devices on a ring network to communicate.
12.1 Overview of ERPS

12.2 Understanding ERPS
12.3 Application Scenarios for ERPS
12.4 Summary of ERPS Configuration Tasks
12.5 Licensing Requirements and Limitations for ERPS
12.6 Default Settings for ERPS
12.7 Configuring ERPS
12.8 Maintaining ERPS
12.9 Configuration Examples for ERPS
12.10 Troubleshooting ERPS
12.1 Overview of ERPS
Definition
ERPS is a protocol defined by the International Telecommunication Union -
Telecommunication Standardization Sector (ITU-T) to eliminate loops at Layer 2.
Because the standard number is ITU-T G.8032/Y1344, ERPS is also called G.8032.
ERPS defines Ring Auto Protection Switching (RAPS) Protocol Data Units (PDUs)
and protection switching mechanisms.
ERPS has two versions: ERPSv1 released by ITU-T in June 2008 and ERPSv2
released in August 2010. EPRSv2, fully compatible with ERPSv1, provides the
following enhanced functions:
Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 638

Switches
● Multi-ring topologies, such as intersecting rings

● RAPS PDU transmission on non-virtual-channels (NVCs) in sub-rings
● Forced Switch (FS) and Manual Switch (MS)
● Revertive and non-revertive switching
Purpose
Generally, redundant links are used on an Ethernet switching network such as a
ring network to provide link backup and enhance network reliability. The use of
redundant links, however, may produce loops, causing broadcast storms and
rendering the MAC address table unstable. As a result, communication quality
deteriorates, and communication services may even be interrupted. Table 12-1
describes ring network protocols supported by devices.
Table 12-1 Ring network protocols supported by devices
Ring Network Advantage Disadvantage

Protocol
STP/RSTP/MSTP ● Applies to all Layer 2 Provides low convergence

networks. on a large network, which
● Is a standard IEEE cannot meet the carrier-
protocol that allows class reliability requirement.
Huawei devices to
communicate with non-
Huawei devices.
ERPS ● Provides fast Requires the network

convergence and carrier- topology to be planned in
class reliability. advance. The configuration
● Is a standard ITU-T is complex.
protocol that allows
Huawei devices to
communicate with non-
Huawei devices.
● Supports single-ring and
multi-ring topologies in
ERPSv2.
Ethernet networks demand faster protection switching. STP does not meet the
requirement for fast convergence.
ERPS, a standard ITU-T protocol, prevent loops on ring networks. It optimizes

detection and performs fast convergence. ERPS allows all ERPS-capable devices on
a ring network to communicate.
Benefits
● Prevents broadcast storms and implements fast traffic switchover on a
network where there are loops.

Switches
● Provides fast convergence and carrier-class reliability.

● Allows all ERPS-capable devices on a ring network to communicate.
12.2 Understanding ERPS
12.2.1 Basic ERPS Concepts

ERPS eliminates loops at the link layer of an Ethernet network. ERPS works for
ERPS rings. There are several nodes in an ERPS ring. ERPS blocks the RPL owner
port and controls common ports to switch the port status between Forwarding
and Discarding and eliminate loops. ERPS uses the control VLAN, data VLAN, and
Ethernet Ring Protection (ERP) instance.
On the network shown in Figure 12-1, SwitchA through SwitchD constitute a ring
and are dual-homed to the upstream network. This access mode will cause a loop
on the entire network. To eliminate redundant links and ensure link connectivity,
ERPS is used to prevent loops.
Figure 12-1 ERPS single-ring networking
Network
Router1 Router2
SwitchA SwitchD
ERPS
RPL
SwitchB SwitchC
User
network
RPL owner
RPL neighbour
ERPS can be deployed on the network shown in Figure 12-1.

Switches
ERPS Ring
An ERPS ring consists of interconnected Layer 2 switching devices configured with
the same control VLAN.
An ERPS ring can be a major ring or a sub-ring. By default, an ERPS ring is a major
ring. The major ring is a closed ring, whereas a sub-ring is a non-closed ring. The
major ring and sub-ring are configured using commands. On the network shown
in Figure 12-2, SwitchA through SwitchD constitute a major ring, and SwitchC
through SwitchF constitute a sub-ring.
Only ERPSv2 supports sub-rings.
Figure 12-2 ERPS major ring and sub-ring networking

SwitchC
SwitchA SwitchE
Major Ring Sub-Ring
SwitchB SwitchF
SwitchD
Node
A node refers to a Layer 2 switching device added to an ERPS ring. A maximum of
two ports on each node can be added to the same ERPS ring. SwitchA through
SwitchD in Figure 12-2 are nodes in an ERPS major ring.
Port Role
ERPS defines three port roles: RPL owner port, RPL neighbor port (only in ERPSv2),
and common port.
● RPL owner port
An RPL owner port is responsible for blocking traffic over the Ring Protection
Link (RPL) to prevent loops. An ERPS ring has only one RPL owner port.
When the node on which the RPL owner port resides receives an RAPS PDU
indicating a link or node fault in an ERPS ring, the node unblocks the RPL
owner port. Then the RPL owner port can send and receive traffic to ensure
nonstop traffic forwarding.
The link where the RPL owner port resides is the RPL.
● RPL neighbor port
An RPL neighbor port is directly connected to an RPL owner port.
Both the RPL owner port and RPL neighbor ports are blocked in normal
situations to prevent loops.
If an ERPS ring fails, both the RPL owner and neighbor ports are unblocked.
The RPL neighbor port helps reduce the number of FDB entry updates on the
device where the RPL neighbor port resides.

Switches
● Common port
Common ports are ring ports other than the RPL owner and neighbor ports.
A common port monitors the status of the directly connected ERPS link and
sends RAPS PDUs to notify the other ports of its link status changes.
Port Status
On an ERPS ring, an ERPS-enabled port has two statuses:
● Forwarding: forwards user traffic and sends and receives RAPS PDUs.
● Discarding: only sends and receives RAPS PDUs.
Control VLAN
A control VLAN is configured in an ERPS ring to transmit RAPS PDUs.
Each ERPS ring must be configured with a control VLAN. After a port is added to
an ERPS ring configured with a control VLAN, the port is added to the control
VLAN automatically.
Different ERPS rings must use different control VLANs.
Data VLAN
Unlike control VLANs, data VLANs are used to transmit data packets.
ERP Instance
On a Layer 2 device running ERPS, the VLAN in which RAPS PDUs and data
packets are transmitted must be mapped to an Ethernet Ring Protection (ERP)
instance so that ERPS forwards or blocks the packets based on configured rules. If
the mapping is not configured, the preceding packets may cause broadcast storms
on the ring network. As a result, the network becomes unavailable.
Timer
ERPS defines four timers: Guard timer, WTR timer, Holdoff timer, and WTB timer
(only in ERPSv2).
● Guard timer
After a faulty link or node recovers or a clear operation is executed, the device
sends RAPS No Request (NR) messages to inform the other nodes of the link
or node recovery and starts the Guard timer. Before the Guard timer expires,
the device does not process any RAPS (NR) messages to avoid receiving out-
of-date RAPS (NR) messages. After the Guard timer expires, if the device still
receives an RAPS (NR) message, the local port enters the Forwarding state.
● WTR timer
If an RPL owner port is unblocked due to a link or node fault, the involved
port may not go Up immediately after the link or node recovers. Blocking the
RPL owner port may cause network flapping. To prevent this problem, the
node where the RPL owner port resides starts the wait to restore (WTR) timer
after receiving an RAPS (NR) message. If the node receives an RAPS Signal
Fail (SF) message before the timer expires, it terminates the WTR timer. If the

Switches
node does not receive any RAPS (SF) message before the timer expires, it
blocks the RPL owner port when the timer expires and sends an RAPS (no
request, root blocked) message. After receiving this RAPS (NR, RB) message,
the nodes set their recovered ports on the ring to the Forwarding state.
● Holdoff timer
On Layer 2 networks running EPRS, there may be different requirements for
protection switching. For example, on a network where multi-layer services
are provided, after a server fails, users may require a period of time to rectify
the server fault so that clients do not detect the fault. You can set the Holdoff
timer. If the fault occurs, the fault is not immediately sent to ERPS until the
Holdoff timer expires.
● WTB timer
The wait to block (WTB) timer starts when Forced Switch (FS) or Manual
Switch (MS) is performed. Because multiple nodes on an ERPS ring may be in
FS or MS state, the clear operation takes effect only after the WTB timer
expires. This prevents the RPL owner port from being blocked immediately.
The WTB timer value cannot be configured. Its value is the Guard timer value
plus 5. The default WTB timer value is 7s.
Revertive and Non-revertive Switching

After link faults in an ERPS ring are rectified, re-blocking the RPL owner port
depends on the switching mode:
● In revertive switching, the RPL owner port is re-blocked after the WTR timer
expires, and the RPL is blocked.
● In non-revertive switching, the WTR timer is not started, and the original
faulty link is still blocked.
ERPS rings use revertive switching by default.
ERPSv1 supports only revertive switching. ERPSv2 supports both revertive and non-
revertive switching.
Port Blocking Modes

Because the Ring Protection Link (RPL) may have high bandwidth, you can block
the low-bandwidth link so that user traffic can be transmitted on the RPL. ERPSv2
supports both Forced Switch (FS) and Manual Switch (MS) modes for blocking an
ERPS port:
● FS: forcibly blocks a port immediately after FS is configured, irrespective of
whether link failures have occurred.
● MS: blocks a port on which MS is configured when the ERPS ring is in Idle or
Pending state.
In addition to FS and MS operations, ERPS also supports the clear operation. The
clear operation has the following functions:
● Clears an existing FS or MS operation.
● Triggers revertive switching before the WTR or WTB timer expires in the case
of revertive switching operations.
● Triggers revertive switching in the case of non-revertive switching operations.

Switches
Only ERPSv2 supports port blocking modes.
RAPS PDU Transmission Mode in a Sub-ring

ERPSv2 supports single-ring and multi-ring topologies. In multi-ring topologies,
both the virtual channel (VC) and non-virtual-channel (NVC) can be used to
transmit RAPS PDUs in sub-rings.
● VC: RAPS PDUs in sub-rings are transmitted to the major ring through
interconnected nodes. The RPL owner port of the sub-ring blocks both RAPS
PDUs and data traffic.
● NVC: RAPS PDUs in sub-rings are terminated on the interconnected nodes.
The RPL owner port blocks data traffic but not RAPS PDUs in each sub-ring.
On the network shown in Figure 12-3, a major ring is interconnected with two
sub-rings. The sub-ring on the left has a VC, whereas the sub-ring on the right has
an NVC.
Figure 12-3 Interconnected rings with a VC or NVC
Major Ring
Sub-Ring Sub-Ring
with virtual without virtual
channel channel
Ethernet Ring Node
Interconnection Node
RPL owner Interface
RAPS Virtual Channel
By default, sub-rings use NVCs to transmit RAPS PDUs, except for the scenario
shown in Figure 12-4.
NOTE
When sub-ring links are incontiguous, VCs must be used.
On the network shown in Figure 12-4, links b and d belong to major rings 1 and 2
respectively; links a and c belong to the sub-ring. As links a and c are

Switches
incontiguous, they cannot detect the status change between each other, so VCs
must be used for RAPS PDU transmission.
Figure 12-4 VC networking

a
Sub-Ring
with virtual
channel
b d
Major Major
Ring1 Ring2
c
Ethernet Ring Node
Interconnection Node
RPL owner Interface
RAPS Virtual Channel
Table 12-2 lists the advantages and disadvantages of RAPS PDU transmission
modes in sub-rings with VCs or NVCs.
Table 12-2 Comparison between RAPS PDU transmission modes in a sub-ring with
VCs or NVCs
RAPS Advantage Disadvantage
PDU
Transmis
sion
Mode in
a Sub-
ring
VC Applies to scenarios in Requires VC resource reservation and

which sub-ring links are controls VLAN assignment from
incontiguous. adjacent rings.

Switches
RAPS Advantage Disadvantage

PDU
Transmis
sion
Mode in
a Sub-
ring
NVC Does not need to reserve Is not applicable to scenarios in

resources or control VLAN which sub-ring links are incontiguous.
assignment from adjacent
rings.
12.2.2 RAPS PDUs
ERPS protocol packets are called Ring Auto Protection Switching (RAPS) Protocol
Data Units (PDUs), which are transmitted in ERPS rings to convey ERPS ring
information. Figure 12-5 shows the RAPS PDU format.
Figure 12-5 RAPS PDU format

1 2 3 4
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
1
MEL Version(0) OpCode(R-APS=40) Flags(0) TLV Offset(32)
5
... R-APS Specific Information(32 octets)
...
37
[optional TLV starts here;otherwise End TLV]
last End TLV(0)
Table 12-3 describes the fields in an RAPS PDU.
Table 12-3 Fields in an RAPS PDU
Field Leng Description

th
MEL 3 bits Identifies the maintenance entity group (MEG) level

of the RAPS PDU.
Version 5 bits ● 0x00: ERPSv1

● 0x01: EPRSv2
OpCode 8 bits Indicates an RAPS PDU. The value of this field is 0x28.

Switches
Field Leng Description

th
Flags 8 bits Is ignored upon RAPS PDU receiving. The value of this
field is 0x00.
TLV Offset 8 bits Indicates that the TLV starts after an offset of 32
bytes. The value of this field is 0x20.
R-APS Specific 32x8 Is the core field in an RAPS PDU and carries ERPS ring
Information bits information. There are differences between sub-fields
in ERPSv1 and ERPSv2. Figure 12-6 shows the R-APS
Specific Information field format in ERPSv1. Figure
12-7 shows the R-APS Specific Information field
format in ERPSv2.
TLV Not Describes information to be loaded. The end TLV

limite value is 0x00.
d
Figure 12-6 Format of the R-APS Specific Information field in ERPSv1

1 2 3 4
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Request Reserved Status Node ID(6 octets)

/State 1 R D
Status
B N
Reserved
F
(Node ID)
Reserved 2(24 octets)
Figure 12-7 Format of the R-APS Specific Information field in ERPSv2

1 2 3 4
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Request Status Node ID(6 octets)

Sub-code
/State R D B
Status
B N P
Reserved
F R
(Node ID)
Reserved 2(24 octets)
Table 12-4 describes sub-fields in the R-APS Specific Information field.

Switches
Table 12-4 Sub-fields in the R-APS Specific Information field
Sub-Field Length Description
Request/ 4 bits Indicates that this RAPS PDU is a request or state PDU.
State The value can be:
● 1101: forced switch (FS)
● 1110: Event
● 1011: signal failed (SF)
● 0111: manual switch (MS)
● 0000: no request (NR)
● Others: reserved
Reserved 4 bits Reserved 1 is used in ERPSv1 for message reply or

1 protection identifier.
Sub-code Sub-code is used in ERPSv2. The value depends on the

Request/State field value:
● If the Request/State field value is 1110, the Sub-
code value is 0000, indicating FDB entry update.
● If the Request/State field value is any other value
than 1110, the Sub-code value is 0000 and ignored
upon RAPS PDU receiving.
Status 8 bits Includes the following status information:

● RPL Blocked (RB) (1 bit): The value 1 indicates that
the RPL owner port is blocked; the value 0 indicates
that the RPL owner port is unblocked. The nodes
where the RPL owner port is not configured set this
sub-field to 0 in outgoing RAPS PDUs.
● Do Not Flush (DNF) (1 bit): The value 1 indicates
that FDB entries are not updated when RAPS PDUs
are received; the value 0 indicates that FDB entries
may be updated when RAPS PDUs are received.
● Blocked port reference (BPR) (1 bit): The value 0
indicates that ring link 0 is blocked. The value 1
indicates that ring link 1 is blocked.
BPR is valid only in ERPSv2.
● Status Reserved: This sub-field is reserved. This sub-
field is all 0s during RAPS PDU transmission, and is
ignored upon RAPS PDU receiving. In ERPSv1, this
sub-field has 6 bits. In ERPSv2, this sub-field has 5
bits.
Node ID 6 x 8 bits Identifies the MAC address of a node in an ERPS ring.

It is informational and does not affect protection
switching in the ERPS ring.
Reserved 24 x 8 bits Is reserved and ignored upon RAPS PDU receiving. The
2 value is all 0 during RAPS PDU transmission.

Switches
12.2.3 ERPS Single-ring Principles

ERPS is a standard ring protocol used to prevent loops in ERPS rings at the
Ethernet link layer. A maximum of two ports on each Layer 2 switching device can
be added to the same ERPS ring.
To prevent loops in 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 device 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 network 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, SwitchA through SwitchE 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 RAPS (NRRB) messages to all other nodes in the
ring at an interval of 5s, indicating that ERPS links are normal.

Switches
Figure 12-8 ERPS single-ring networking (links are normal)
Network
Router1 Router2
SwitchA SwitchE
ERPS
SwitchB RPL SwitchD
RPL owner SwitchC
User
network
Blocked Interface
Data Flow
A Link Fails
As shown in Figure 12-9, if the link between SwitchD and SwitchE 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 nonstop traffic transmission. The
process is as follows:
1. After SwitchD and SwitchE detect the link fault, they block their ports on the
faulty link and update Filtering Database (FDB) entries.
2. SwitchD and SwitchE send three consecutive RAPS Signal Fail (SF) messages
to the other LSWs and send one RAPS (SF) message at an interval of 5s
afterwards.
3. After receiving an RAPS (SF) message, the other LSWs update their FDB
entries. SwitchC on which the RPL owner port resides and SwitchB on which
the RPL neighbor port resides unblock the respective RPL owner port and RPL
neighbor port, and update FDB entries.

Switches
Figure 12-9 ERPS single-ring networking (unblocking the RPL owner port and RPL
neighbor port if a link fails)
Network
Router1 Router2
SwitchA SwitchE
ERPS
SwitchB RPL SwitchD
RPL owner SwitchC
User
network
Failed Link
Blocked Interface
Data Flow
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 is still blocked.
The following example uses revertive switching to illustrate the process after the
link recovers.
1. After the link between SwitchD and SwitchE recovers, SwitchD and SwitchE
start the Guard timer to avoid receiving out-of-date RAPS PDUs. The two
switches do not receive any RAPS PDUs before the timer expires. At the same
time, SwitchD and SwitchE send RAPS (NR) messages to the other LSWs.
2. After receiving an RAPS (NR) message, SwitchC on which the RPL owner port
resides starts the WTR timer. After the WTR timer expires, SwitchC blocks the
RPL owner port and sends RAPS (NR, RB) messages.

Switches
3. After receiving an RAPS (NR, RB) message, SwitchD and SwitchE unblock the
ports at the two ends of the link that has recovered, stop sending RAPS (NR)
messages, and update FDB entries. The other LSWs also update FDB entries
after receiving an RAPS (NR, RB) message.
Protection Switching
● Forced switch
On the network shown in Figure 12-10, SwitchA through SwitchE in the ERPS
ring can communicate with each other. A forced switch (FS) operation is
performed on the SwitchE's port that connects to SwitchD, and the SwitchE's
port is blocked. Then the RPL owner port and RPL neighbor port are
unblocked to send and receive traffic. This mechanism ensures nonstop traffic
transmission. The process is as follows:
a. After the SwitchD's port that connects to SwitchE is forcibly blocked,
SwitchE update FDB entries.
b. SwitchE sends three consecutive RAPS (SF) messages to the other LSWs
and sends one RAPS (SF) message at an interval of 5s afterwards.
c. After receiving an RAPS (SF) message, the other LSWs update their FDB
entries. SwitchC on which the RPL owner port resides and SwitchB on
which the RPL neighbor port resides unblock the respective RPL owner
port and RPL neighbor port, and update FDB entries.

Switches
Figure 12-10 Layer 2 ERPS ring networking (blocking a port in FS mode)
Network
Router1 Router2
SwitchA SwitchE
ERPS
SwitchB RPL SwitchD
RPL owner SwitchC
User
network
Blocked Interface
Data Flow
● Clear
After a clear operation is performed on SwitchE, the port that is forcibly
blocked by FS sends RAPS (NR) messages to all other ports in the ERPS ring.
– If the ERPS ring uses revertive switching, the RPL owner port starts the
WTB timer after receiving an RAPS (NR) message. After the WTB timer
expires, the FS operation is cleared. Then the RPL owner port is blocked,
and the blocked port on SwitchE is unblocked. If you perform a clear
operation on SwitchC on which the RPL owner port resides before the
WTB timer expires, the RPL owner port is immediately blocked, and the
blocked port on SwitchE is unblocked.
– If the ERPS ring uses non-revertive switching and you want to block the
RPL owner port, perform a clear operation on SwitchC on which the RPL
owner port resides.
● Manual switch
The MS process in an ERPS ring is similar to the FS process. The difference is
that the MS operation does not take effect when the ERPS ring is not idle or
pending.

Switches
12.2.4 ERPS Multi-ring Principles

Ethernet Ring Protection Switching Version 1 (ERPSv1) supports only single-ring
topology, whereas ERPSv2 supports single-ring and multi-ring topologies.
In a multi-ring topology, there are major rings and sub-rings. Depending on
whether Ring Auto Protection Switching Protocol Data Units (R-APS PDUs) on a
sub-ring are transmitted to a major ring, a sub-ring can either have or not have a
virtual channel (VC). If R-APS PDUs on a sub-ring are transmitted to a major ring,
the sub-ring has a virtual channel; otherwise, the sub-ring does not have a virtual
channel.
This section describes how ERPS is implemented on a multi-ring network when
links are normal, when a link fails, and when the link recovers.
Sub-rings Do Not Have VCs

Links Are Normal
On the multi-ring network shown in Figure 12-11, SwitchA through SwitchE
constitute a major ring; SwitchB, SwitchC, and SwitchF constitute sub-ring 1, and
SwitchC, SwitchD, and SwitchG constitute sub-ring 2. The LSWs in each ring can
communicate with each other.
1. To prevent loops, each ring blocks its RPL owner port. All other ports can
transmit service traffic.
2. The RPL owner port on each ring sends RAPS (NRRB) messages to all other
nodes in the same ring at an interval of 5s. The RAPS (NRRB) messages in the
major ring are transmitted only in this ring. The RAPS (NRRB) messages in
each sub-ring are terminated on the interconnected nodes and therefore are
not transmitted to the major ring.
Traffic between PC1 and the upper-layer network travels along the path PC1 ->
SwitchF -> SwitchB -> SwitchA -> Router1; traffic between PC2 and the upper-
layer network travels along the path PC2 -> SwitchG -> SwitchD -> SwitchE ->
Router2.

Switches
Figure 12-11 ERPS multi-ring networking with sub-rings that do not have VCs
(links are normal)
Network
Router1 Router2
SwitchA SwitchE
Major Ring
SwitchB SwitchD
L
RP
Sub-Ring1 Sub-Ring2
RP
L SwitchC L
RP
SwitchF SwitchG
PC1
PC2
RPL owner
Data Flow
A Link Fails
As shown in Figure 12-12, if the link between SwitchD and SwitchG fails, the ERPS
protection switching mechanism is triggered. The ports on both ends of the faulty
link are blocked, and the RPL owner port in sub-ring 2 is unblocked to send and
receive traffic. In this situation, traffic from PC1 still travels along the original
path. SwitchC and SwitchD inform the other nodes in the major ring of the
topology change so that traffic from PC2 is also not interrupted. Traffic between
PC2 and the upper-layer network travels along the path PC2 -> SwitchG ->
SwitchC -> SwitchB -> SwitchA -> SwitchE -> Router2. The process is as follows:
1. After SwitchD and SwitchG detect the link fault, they block their ports on the
faulty link and update Filtering Database (FDB) entries.
2. SwitchG sends three consecutive RAPS (SF) messages to the other LSWs and
sends one RAPS (SF) message at an interval of 5s afterwards.

Switches
3. SwitchG then unblocks the RPL owner port and updates FDB entries.
4. After the interconnected node SwitchC receives an RAPS (SF) message, it
updates FDB entries. SwitchC and SwitchD then send RAPS Event messages
within the major ring to notify the topology change in sub-ring 2.
5. After receiving an RAPS Event message, the other LSWs in the major ring
update FDB entries.
Then traffic from PC2 is switched to a normal link.
Figure 12-12 ERPS multi-ring networking (unblocking the RPL owner port if a link
fails)
Network
Router1 Router2
SwitchA SwitchE
Major Ring
SwitchB SwitchD
RPL
Sub-Ring2
Sub-Ring1 RP
L L
RP SwitchC
SwitchF SwitchG
PC1
PC2
Blocked Interface
Data Flow
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.

Switches
● If the ERPS ring uses non-revertive switching, the RPL remains unblocked, and
the link that has recovered is still blocked.
The following example uses revertive switching to illustrate the process after the
link recovers.
1. After the link between SwitchD and SwitchG recovers, SwitchD and SwitchG
start the Guard timer to avoid receiving out-of-date RAPS PDUs. The two
devices do not receive any RAPS PDUs before the timer expires. Then SwitchD
and SwitchG send RAPS (NR) messages within sub-ring 2.
2. SwitchG on which the RPL owner port resides starts the WTR timer. After the
WTR timer expires, SwitchG blocks the RPL owner port and unblocks its port
on the link that has recovered and then sends RAPS (NR, RB) messages within
sub-ring 2.
3. After receiving an RAPS (NR, RB) message from SwitchG, SwitchD unblocks its
port on the recovered link, stops sending RAPS (NR) messages, and updates
FDB entries. SwitchC also updates FDB entries.
4. SwitchC and SwitchD (interconnected nodes) send RAPS Event messages
within the major ring to notify the link recovery of sub-ring 2.
5. After receiving an RAPS Event message, the other LSWs in the major ring
update FDB entries.
Then traffic changes to the normal state, as shown in Figure 12-11.
Sub-rings Have VCs

When sub-rings have VCs, the R-APS PDUs of the sub-rings are transmitted to the
major ring through the interconnection nodes. In other words, the interconnection
nodes do not terminate the R-APS PDUs of the sub-rings. The blocked ports of
sub-rings block both R-APS PDUs and data traffic.
Links Are Normal
On the multi-ring network shown in Figure 12-13, Switch A, Switch B, and Switch
E constitute major ring 1; Switch C, Switch D, and Switch F constitute major ring 2;
Switch A through Switch D constitute a sub-ring. The two major rings are
interconnected with the sub-ring. The devices on each ring can communicate with
each other.
1. To prevent loops, each ring blocks its RPL owner port. All other ports can
transmit data traffic.
2. The RPL owner port on each ring sends R-APS (NR) messages to all other
nodes on the same ring at an interval of 5s. The R-APS (NR) messages of
each major ring are transmitted only within the same major ring, whereas the
R-APS (NR) messages of the sub-ring are transmitted to the major rings over
the interconnection nodes.
Traffic between PC1 and PC2 travels along the path PC1 <-> Switch E <-> Switch B
<-> Switch C <-> Switch F <-> PC2.

Switches
Figure 12-13 ERPS multi-ring networking with a sub-ring that has VCs (links are
normal)
SwitchE SwitchF
RPL SwitchA RPL SwitchD RPL
PC1 PC2
Ma
jor g2
Rin Rin
g1 jor
Ma
Sub- Ring
SwitchB SwitchC
RPL owner
Data Flow
A Link Fails
As shown in Figure 12-14, if the link between Switch B and Switch C fails, ERPS is
triggered. Specifically, the ports on both ends of the faulty link are blocked, and
the RPL owner port on the sub-ring is unblocked to send and receive user traffic.
Switch B and Switch C inform the other nodes on the major rings of the topology
change so that traffic between PCs is not interrupted. Traffic between PC1 and
PC2 then travels along the path PC1 <-> Switch E <-> Switch B <-> Switch A <->
Switch D <-> Switch C <-> Switch F <-> PC2. The detailed process is as follows:
1. After Switch B and Switch C detect the link fault, they both block their ports
on the faulty link and perform an FDB flush.
2. Switch B sends three consecutive R-APS (SF) messages to the other devices on
the sub-ring and then sends one R-APS (SF) message at an interval of 5s
afterwards. The R-APS (SF) messages then arrive at major ring 1.
3. After receiving an R-APS (SF) message, Switch A on major ring 1 unblocks its
RPL owner port and performs an FDB flush.
4. The other major ring nodes also perform an FDB flush. Traffic between PCs is
then rapidly switched to a normal link.
Figure 12-14 ERPS multi-ring networking with a sub-ring that has VCs (a link
fails)
SwitchE SwitchF
RPL SwitchA RPL SwitchD RPL
PC1 PC2
Ma
jor g2
Rin Rin
g1 jor
Ma
Sub- Ring
SwitchB SwitchC
Blocked Interface
Data Flow

Switches
The Link Recovers

After the link fault is rectified, either of the following situations may occur:
● If the revertive switching mode is configured for the ERPS major rings and
sub-ring, the RPL owner port is blocked again, and the link that has recovered
is used to forward traffic.
● If the non-revertive switching is configured for the ERPS major rings and sub-
ring, the RPL owner port remains unblocked, but 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 Switch B and Switch C recovers, Switch B and Switch C
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. Then Switch
B and Switch C send R-APS (NR) messages, which are transmitted within the
major rings and sub-ring.
2. Switch A starts the WTR timer. After the WTR timer expires, Switch A blocks
the RPL owner port and then sends R-APS (NR, RB) messages to other
connected devices.
3. After receiving an R-APS (NR, RB) message from Switch A, Switch B and
Switch C unblock its port on the recovered link, stop sending R-APS (NR)
messages, and perform an FDB flush.
4. After receiving an R-APS (NR, RB) message from Switch A, other devices also
perform an FDB flush.
Traffic then travels in the same way as that shown in Figure 12-13.
12.2.5 ERPS Multi-instance

On a common ERPS network, a physical ring can be configured with a single ERPS
ring, and only one blocked port can be specified in the ring. When the ERPS ring is
in normal state, the blocked port prohibits all service packets from passing
through. As a result, all service data is transmitted through one path over the
ERPS ring, and the other link on the blocked port becomes idle, wasting
bandwidth. As shown in Figure 12-15, when only ERPS Ring1 is configured,
Interface1 is blocked and data is forwarded through the path where Data Flow1
travels. The link SwitchC -> SwitchD -> SwitchE is idle.

Switches
Figure 12-15 Networking diagram of ERPS multi-instance
Network
Router1 Router2
SwitchE
SwitchA
ERPS Ring2
ERPS Ring1
SwitchB SwitchD
Interface2 Interface1
SwitchC
CE1 Ring1 Blocked Port

Ring2 Blocked Port
Data Flow1
VLAN100-200
and VLAN300- Data Flow2
400
To improve link use efficiency, only two logical rings can be configured in the
same physical ring in the ERPS multi-instance. A port may have different roles in
different ERPS rings and different ERPS rings use different control VLANs. A
physical ring can have two blocked ports accordingly. Each blocked port
independently monitors the physical ring status and is blocked or unblocked. An
ERPS ring must be configured with an ERP instance, and each ERP instance
specifies a range of VLANs. The topology calculated for a specific ERPS ring only
takes effect in the ERPS ring. Different VLANs can use separate paths,
implementing traffic load balancing and link backup.
As shown in Figure 12-15, you can configure ERPS Ring1 and ERPS Ring2 in the
physical ring consisting of SwitchA through SwitchE. Interface1 is the blocked port
in ERPS Ring1. The VLANs mapping to the ERP instance is VLANs 100 to 200.
Interface2 is the blocked port in ERPS Ring2. The VLANs mapping to the ERP
instance is VLANs 300 to 400. After the configuration is completed, data from
VLANs 100 to 200 is forwarded through Data Flow1, and data from VLANs 300 to
400 is forwarded through Data Flow2. In this manner, load balancing is
implemented and link use efficiency is improved.

Switches
12.3 Application Scenarios for ERPS

Generally, redundant links are used on an Ethernet switching network to provide
link backup and enhance network reliability. The use of redundant links, however,
may produce loops, causing broadcast storms and rendering the MAC address
table unstable. As a result, communication quality deteriorates, and
communication services may even be interrupted.
To prevent loops caused by redundant links, enable ERPS on the nodes of the ring
network. ERPS is a Layer 2 loop-breaking protocol defined by the ITU-T, and
provides fast convergence of carrier-class reliability standards.
Figure 12-16 Layer 2 application of ERPS
Network
Router1 Router2
SwitchA SwitchE
ERPS
SwitchB SwitchD
RPL
RPL Owner
SwitchC
User User
network1 network3
User
network2
Blocked Port
Data Flow1
Data Flow2
Data Flow3

Switches
As shown in Figure 12-16, SwitchA through SwitchE constitute a ring. The ring
runs ERPS to provide protection switching for Layer 2 redundant links and prevent
loops that cause broadcast storms and render the MAC address table unstable.
Generally, the RPL owner port is blocked and does not forward service packets,
preventing loops. If a fault occurs on the link between SwitchA and SwitchB, ERPS
will unblock the blocked RPL owner port and traffic from User network1 and User
network2 is forwarded through the path SwitchC ->SwitchD ->SwitchE.
12.4 Summary of ERPS Configuration Tasks

After a single ERPS ring or intersecting ERPS ring is configured, a specified port
can be blocked to remove loops. Table 12-5 describes the ERPS configuration
tasks.
Table 12-5 ERPS configuration tasks

Scenario Description Task
Configure ERPS single- You can configure ERPS 12.7.1 Configuring

ring networking single-ring networking ERPSv1
when there is only one
ring in the network
topology.
Configure ERPS You can configure ERPS 12.7.2 Configuring

intersecting-ring intersecting-ring ERPSv2
networking networking when there
are two or more rings in
the network topology
and many common
nodes between two
rings.
12.5 Licensing Requirements and Limitations for ERPS
Involved Network Elements

Other network elements are required to support ERPS functions.
Licensing Requirements
ERPS is a basic function of the switch, and as such is controlled by the license for
basic software functions. The license for basic software functions has been loaded
and activated before delivery. You do not need to manually activate it.

Switches
Version Requirements
Table 12-6 Products and minimum version supporting ERPS

Product Minimum Version Required
CE5850EI V100R003C10
CE5810EI V100R003C10
CE5850HI V100R003C10
CE5855EI V100R005C10
CE6850EI V100R003C10
CE6850HI V100R005C00
CE6850U-HI V100R005C10
CE6851HI V100R005C10
CE6810EI V100R003C10
CE6810LI V100R003C10
CE6855HI V200R001C00
CE6856HI V200R002C50
CE6857EI V200R005C10
CE6870-24S6CQ-EI V200R001C00
CE6870-48S6CQ-EI V200R001C00
CE6870-48T6CQ-EI V200R002C50
CE6860-48S8CQ-EI V200R002C50
CE6865EI V200R005C00
CE6875-48S4CQ-EI V200R003C00
CE7850EI V100R003C10
CE7855EI V200R001C00
CE8860EI V100R006C00
CE8861EI/CE8868EI V200R005C10
CE8850-32CQ-EI V200R002C50
CE8850-64CQ-EI V200R005C00
CE9860EI V200R020C00

Switches
NOTE
For details about the mapping between software versions and switch models, see the
Hardware Query Tool.
Feature Limitations
● In ERPSv2, sub-rings can interlock in multi-ring topologies. The sub-rings
attached to other sub-rings must use non-virtual channels.
● A VLAN cannot be mapped to multiple MSTIs. If you map a VLAN that has
already been mapped to an MSTI to another MSTI, the original mapping will
be deleted.
● To configure the mapping between an ERP instance and a MUX VLAN, please
configure the principal VLAN, subordinate group VLANs, and subordinate
separate VLANs of the MUX VLAN in the same ERP instance. Otherwise, loops
may occur.
● A port can be added to a maximum of two ERPS rings.
● An ERPS-enabled port needs to allow packets of control VLANs and data
VLANs to pass through, so the link type of the port must be configured as
trunk or hybrid.
● Flush-FDB packets for updating MAC addresses cannot be separately sent, so
do not configure a direct link between two upstream nodes as the RPL.
● If the virtual-channel enable command is used to set the VC mode for RAPS
PDU transmission in a sub-ring, ensure that the control VLAN of the major
ring is used to transmit only the RAPS PDUs of the sub-ring. Otherwise,
attacks may use bogus RAPS PDUs of the sub-ring to form loops or even fault
in the major ring.
● ERPS cannot be applied simultaneously with Selective QinQ, VLAN mapping,
or Port Security on a port.
● Before adding a port to an ERPS ring, ensure that the STP/RSTP/MSTP/VBST
or Smart Link is not enabled on the port.
● ERPS packets may be discarded by the interface with multicast traffic
suppression enabled using the storm suppression multicast command.
12.6 Default Settings for ERPS

Table 12-7 describes default ERPS settings.
Table 12-7 ERPS default setting
Parameter Default Setting
ERPS ring Not created
Guard timer 200 centiseconds
Wait to restore (WTR) timer 5 minutes
Holdoff timer 0 deciseconds

Switches
Parameter Default Setting
ERPS version ERPSv1
12.7 Configuring ERPS
12.7.1 Configuring ERPSv1

If there is no link fault on a ring network, ERPS can eliminate loops on the
Ethernet network. If a link fault occurs on the ring network, ERPS can quickly
restore communication between nodes on the ring network.
12.7.1.1 Creating an ERPS Ring
Context
ERPS works for ERPS rings. An ERPS ring consists of interconnected Layer 2
switching devices configured with the same control VLAN and data VLAN. Before
configuring other ERPS functions, you must configure an ERPS ring.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run erps ring ring-id
An ERPS ring is created and the ERPS ring view is displayed.
Step 3 (Optional) Run description
The description of the device is configured. The description can contain the ERPS
ring ID, which facilitates device maintenance in an ERPS ring.
By default, the description of an ERPS ring is the ERPS ring name, for example,
Ring 1.
Step 4 Run commit
The configuration is committed.
----End
12.7.1.2 Configuring the Control VLAN
Context
In an ERPS ring, the control VLAN is used only to forward RAPS PDUs but not
service packets, so the security of ERPS is improved. All the devices in an ERPS ring

Switches
must be configured with the same control VLAN, and different ERPS rings must
use different control VLANs.
Procedure
The ERPS ring view is displayed.
Step 3 Run control-vlan vlan-id
The control VLAN of the ERPS ring is configured.
● The control VLAN specified by vlan-id must be a VLAN that has not been
created or used.
● If you run the control-vlan command multiple times, only the latest
configuration takes effect.
● If the ERPS ring contains ports, the control VLAN cannot be changed. To
delete the configured control VLAN, run the undo erps ring command in the
interface view or the undo port command in the ERPS ring view to delete
ports from the ERPS ring, and run the undo control-vlan command to delete
the control VLAN.
● After a control VLAN is created, the vlan batch vlan-id1 [ to vlan-id2 ]
&<1-10> command used to create common VLANs is displayed in the
configuration file.
● After a port is added to an ERPS ring configured with a control VLAN, the port
is added to the control VLAN.
– If the port is a trunk port, the port trunk allow-pass vlan vlan-id
command is displayed in the record of the port that has been added to
the ERPS ring in the configuration file.
– If the port is a hybrid port, the port hybrid tagged vlan vlan-id
Step 4 Run commit
----End
12.7.1.3 Configuring an ERP Instance and Activating the Mapping Between

the ERP Instance and VLAN
Context
packets are transmitted must be mapped to an ERP instance so that ERPS
forwards or blocks the packets based on configured rules. If the mapping is not
configured, the preceding packets may cause broadcast storms on the ring
network. As a result, the network becomes unavailable.

Switches
Procedure
Step 3 Run protected-instance { all | { instance-id1 [ to instance-id2 ] &<1-10> } }
An ERP instance is created for the ERPS ring.
By default, no ERP instance is configured in an ERPS ring.
NOTE
● If you run the protected-instance command multiple times in the same ERPS ring,
multiple ERP instances are configured.
● If the ERPS ring contains ports, the ERP instance cannot be changed. To delete the
configured ERP instance, run the undo erps ring command in the interface view or the
undo port command in the ERPS ring view to delete ports from the ERPS ring, and run
the undo protected instance command to delete the ERP instance.
Step 4 Run commit

Step 5 Run quit
Step 6 Configure the mapping between an ERP instance and VLAN.
1. Run stp region-configuration
The Multiple Spanning Tree (MST) region view is displayed.
2. Run instance instance-id vlan { vlan-id [ to vlan-id ] } &<1-10>
The mapping between the ERP instance and VLAN is configured.
By default, all VLANs in an MST region are mapped to instance 0.
instance-id in this command must be the same as instance-id used by the
protected-instance command.
NOTE
– A VLAN cannot be mapped to multiple MSTIs. If you map a VLAN that has already
been mapped to an MSTI to another MSTI, the original mapping will be deleted.
– The vlan-mapping modulo modulo command configures the mapping between
MSTIs and VLANs based on the default algorithm. However, the mapping
configured using this command cannot always meet the actual demand. Therefore,
running this command is not recommended.
– To configure the mapping between an ERP instance and a MUX VLAN, you are
advised to configure the principal VLAN, subordinate group VLANs, and
subordinate separate VLANs of the MUX VLAN in the same ERP instance.
Otherwise, loops may occur.
3. Run commit
----End

Switches
12.7.1.4 Adding a Layer 2 Port to an ERPS Ring and Configuring the Port
Role
Context
After ERPS is configured, add Layer 2 ports to an ERPS ring and configure port
roles so that ERPS can work properly.
You can add a Layer 2 port to an ERPS ring in either of the following ways:
● In the ERPS ring view, add a specified port to the ERPS ring and configure the
port role.
● In the interface view, add the current port to the ERPS ring and configure the
port role.
NOTE

● An ERPS-enabled port needs to allow packets of control VLANs and data VLANs to pass
through, so the link type of the port must be configured as trunk or hybrid.
● Flush-FDB packets for updating MAC addresses cannot be separately sent, so do not
configure a direct link between two upstream nodes as the RPL.
● Before changing the port role, use the shutdown command to disable the port. When
the port role is changed, use the undo shutdown command to enable the port. This
prevents traffic interruptions.
Prerequisites
● The port is not a Layer 3 port. If the port is a Layer 3 port, run the portswitch
command to switch the port to the Layer 2 mode.
● Spanning Tree Protocol (STP) or Smart Link is not enabled on the port.
– If the port has STP enabled, run the stp disable command in the
interface view to disable STP.
– If the port has Smart Link enabled, run the undo port command in the
Smart Link group view to disable Smart Link.
● The control-vlan command has been executed to configure a control VLAN
and the protected-instance command has been executed to configure an
ERP instance.
Procedure
Step 2 Add a Layer 2 port to an ERPS ring and configure the port role in either of the
following ways.
port role.
a. Run interface interface-type interface-number
The interface view is displayed.

Switches
b. Run stp disable

STP is disabled on the ERPS-enabled port.
c. Run port link-type trunk
The link type of the ERPS-enabled port is configured as trunk.
d. Run port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> |
all }
The VLANs allowed by the ERPS-enabled port are specified.
After the control-vlan command is used in the ERPS ring view to
configure a control VLAN and the port interface-type interface-number
[ rpl owner ] command is configured, the ports in the ERPS ring allow
packets of the control VLAN to pass through. Therefore, you need to
specify only the IDs of data VLANs in this step.
e. Run quit
Return to the system view.
f. Run erps ring ring-id
g. Run port interface-type interface-number [ rpl owner ]
The port is added to the ERPS ring and its role is configured. If rpl owner
is specified, the port is configured as an RPL owner port. If rpl owner is
not specified, the port is a common port.
port role.
The specified interface view is displayed.
b. Run stp disable
all }
[ rpl owner ] command is configured, the ports in the ERPS ring allow
packets of the control VLAN to pass through. Therefore, you need to
specify only the IDs of data VLANs in this step.
e. Run erps ring ring-id [ rpl owner ]
The current port is added to the ERPS ring and its role is configured. If rpl
owner is specified, the port is configured as an RPL owner port. If rpl
owner is not specified, the port is a common port.
Step 3 Run commit
----End

Switches
12.7.1.5 (Optional) Configuring Timers in an ERPS Ring
Context
After a link or node failure in an ERPS ring recovers, the device starts timers in the
ERPS ring to reduce traffic interruptions. This prevents network flapping.
Procedure
Step 3 Configure the WTR timer, Guard timer, and Holdoff timer in the ERPS ring
according to actual networking.
● Run wtr-timer time-value
The WTR timer is set.
By default, the WTR timer is 5 minutes in an ERPS ring.
● Run guard-timer time-value
The Guard timer is set.
By default, the Guard timer is 200 centiseconds in an ERPS ring.
● Run holdoff-timer time-value
The Holdoff timer is set.
By default, the Holdoff timer is 0 deciseconds in an ERPS ring.
Step 4 Run commit
----End
12.7.1.6 (Optional) Configuring the MEL Value
Context
On a Layer 2 network running ERPS, if another fault detection protocol (for
example, CFM) is enabled, the MEL field in RAPS PDUs determines whether the
RAPS PDUs can be forwarded. If the MEL value in an ERPS ring is smaller than the
MEL value of the fault detection protocol, the RAPS PDUs have a lower priority
and are discarded. If the MEL value in an ERPS ring is larger than the MEL value of
the fault detection protocol, the RAPS PDUs can be forwarded. In addition, the
MEL value can also be used for interworking with other vendors' devices in an
ERPS ring. The same MEL value ensures smooth communication between devices.

Switches
Procedure
Step 3 Run raps-mel level-id
The MEL value in the ERPS ring is set.
By default, the MEL value in RAPS PDUs is 7.
Step 4 Run commit
----End
12.7.1.7 Verifying the ERPS Configuration
Procedure
● Run the display erps [ ring ring-id ] [ verbose ] command to check the
device ports added to an ERPS ring and ERPS ring configurations.
● Run the display erps interface interface-type interface-number [ ring ring-
id ] command to check physical configurations of the port added to an ERPS
ring.
----End
12.7.2 Configuring ERPSv2

When there is no faulty link on a ring network, Ethernet Ring Protection Switching
(ERPS) can eliminate loops on the network. When a link fails on the ring network,
ERPS can immediately restore communication between nodes on the network.
ERPSv2, compatible with ERPSv1, supports multi-ring topologies, in addition to
ERPSv1 functions such as single ring topologies and multi-instance.
12.7.2.1 Creating an ERPS Ring
Context
ERPS works for ERPS rings. An ERPS ring consists of interconnected Layer 2
switching devices configured with the same control VLAN and data VLAN. Before
configuring other ERPS functions, configure an ERPS ring.
Procedure

Switches
An ERPS ring is created and the ERPS ring view is displayed.
By default, an ERPS ring configured using the erps ring ring-id command is a
major ring.
Step 3 Run version v2
ERPSv2 is specified.
By default, ERPSv1 is used.
Before specifying ERPSv1 for an ERPSv2-enabled device, delete all ERPS

configurations that ERPSv1 does not support.
Step 4 (Optional) Run sub-ring
The ERPS ring is configured as a sub-ring.
By default, an ERPS ring is a major ring. Major rings are closed, and sub-rings are
open. This step is performed only when an existing ERPS ring needs to be used as
a sub-ring.
An ERPS ring that has a port cannot be configured as a sub-ring. Before

configuring an ERPS ring that has a port as a sub-ring, run the undo erps ring
command in the interface view or the undo port command in the ERPS ring view
to delete the port from the ERPS ring. Then run the sub-ring command to
configure the ERPS ring as a sub-ring.
Step 5 (Optional) Run virtual-channel { enable | disable }
The RAPS PDU transmission mode is specified in the sub-ring.
By default, sub-rings use non-virtual-channels (NVCs) to transmit RAPS PDUs. The

default transmission mode is recommended. This step takes effect only in a sub-
ring.
NOTE
If the virtual-channel enable command is used to set the VC mode for RAPS PDU
transmission in a sub-ring, it is recommended that the control VLAN of the major ring be
used to transmit only the RAPS PDUs of the sub-ring. Otherwise, attacks may use bogus
RAPS PDUs of the sub-ring to form loops or even fault in the major ring.
Step 6 (Optional) Run description text
The description is configured for the ERPS ring.
By default, the description of an ERPS ring is the ERPS ring name, for example,
Ring 1.
Step 7 Run commit
----End

Switches
12.7.2.2 Configuring the Control VLAN
Context
In an ERPS ring, the control VLAN is used only to forward RAPS PDUs but not
service packets, so the security of ERPS is improved. All the devices in an ERPS ring
must be configured with the same control VLAN, and different ERPS rings must
use different control VLANs.
Procedure
Step 3 Run control-vlan vlan-id
The control VLAN of the ERPS ring is configured.
● The control VLAN specified by vlan-id must be a VLAN that has not been
created or used.
● If you run the control-vlan command multiple times, only the latest
configuration takes effect.
● If the ERPS ring contains ports, the control VLAN cannot be changed. To
delete the configured control VLAN, run the undo erps ring command in the
interface view or the undo port command in the ERPS ring view to delete
ports from the ERPS ring, and run the undo control-vlan command to delete
the control VLAN.
● After a control VLAN is created, the vlan batch vlan-id1 [ to vlan-id2 ]
&<1-10> command used to create common VLANs is displayed in the
configuration file.
● After a port is added to an ERPS ring configured with a control VLAN, the port
is added to the control VLAN.
– If the port is a trunk port, the port trunk allow-pass vlan vlan-id
– If the port is a hybrid port, the port hybrid tagged vlan vlan-id
Step 4 Run commit
----End
12.7.2.3 Configuring an ERP Instance and Activating the Mapping Between

the ERP Instance and VLAN

Switches
Context
packets are transmitted must be mapped to an ERP instance so that ERPS
forwards or blocks the packets based on configured rules. If the mapping is not
configured, the preceding packets may cause broadcast storms on the ring
network. As a result, the network becomes unavailable.
Procedure
Step 3 Run protected-instance { all | { instance-id1 [ to instance-id2 ] &<1-10> } }
An ERP instance is created for the ERPS ring.
By default, no ERP instance is configured in an ERPS ring.
NOTE
● If you run the protected-instance command multiple times in the same ERPS ring,
multiple ERP instances are configured.
● If the ERPS ring contains ports, the ERP instance cannot be changed. To delete the
configured ERP instance, run the undo erps ring command in the interface view or the
undo port command in the ERPS ring view to delete ports from the ERPS ring, and run
the undo protected instance command to delete the ERP instance.
Step 4 Run commit

Step 5 Run quit
Step 6 Configure the mapping between an ERP instance and VLAN.
1. Run stp region-configuration
The Multiple Spanning Tree (MST) region view is displayed.
2. Run instance instance-id vlan { vlan-id [ to vlan-id ] } &<1-10>
The mapping between the ERP instance and VLAN is configured.
By default, all VLANs in an MST region are mapped to instance 0.
instance-id in this command must be the same as instance-id used by the
protected-instance command.

Switches
NOTE
– A VLAN cannot be mapped to multiple MSTIs. If you map a VLAN that has already
been mapped to an MSTI to another MSTI, the original mapping will be deleted.
– The vlan-mapping modulo modulo command configures the mapping between
MSTIs and VLANs based on the default algorithm. However, the mapping
configured using this command cannot always meet the actual demand. Therefore,
running this command is not recommended.
– To configure the mapping between an ERP instance and a MUX VLAN, you are
advised to configure the principal VLAN, subordinate group VLANs, and
subordinate separate VLANs of the MUX VLAN in the same ERP instance.
Otherwise, loops may occur.
3. Run commit
----End
12.7.2.4 Adding a Layer 2 Port to an ERPS Ring and Configuring the Port
Role
Context
After ERPS is configured, add Layer 2 ports to an ERPS ring and configure port
roles so that ERPS can work properly.
You can add a Layer 2 port to an ERPS ring in either of the following ways:
port role.
port role.
NOTE

● An ERPS-enabled port needs to allow packets of control VLANs and data VLANs to pass
through, so the link type of the port must be configured as trunk or hybrid.
● Flush-FDB packets for updating MAC addresses cannot be separately sent, so do not
configure a direct link between two upstream nodes as the RPL.
● Before changing the port role, use the shutdown command to disable the port. When
the port role is changed, use the undo shutdown command to enable the port. This
prevents traffic interruptions.
Prerequisites
● The port is not a Layer 3 port. If the port is a Layer 3 port, run the portswitch
command to switch the port to the Layer 2 mode.
● Spanning Tree Protocol (STP) or Smart Link is not enabled on the port.
– If the port has STP enabled, run the stp disable command in the
interface view to disable STP.
– If the port has Smart Link enabled, run the undo port command in the
Smart Link group view to disable Smart Link.

Switches
● The control-vlan command has been executed to configure a control VLAN

and the protected-instance command has been executed to configure an
ERP instance.
Procedure
Step 2 Add a Layer 2 port to an ERPS ring and configure the port role in either of the
following ways.
port role.
The interface view is displayed.
b. Run stp disable
all }
[ rpl { owner | neighbour } ] command is configured, the ports in the
ERPS ring allow packets of the control VLAN to pass through. Therefore,
you need to specify only the IDs of data VLANs in this step.
e. Run quit
f. Run erps ring ring-id
g. Run port interface-type interface-number [ rpl { owner | neighbour } ]
The port is added to the ERPS ring and its role is configured.
port role.
The specified interface view is displayed.
b. Run stp disable
all }

Switches

[ rpl { owner | neighbour } ] command is configured, the ports in the
ERPS ring allow packets of the control VLAN to pass through. Therefore,
you need to specify only the IDs of data VLANs in this step.
e. Run erps ring ring-id [ rpl { owner | neighbour } ]
The current port is added to the ERPS ring and its role is configured.
Step 3 Run commit
----End
12.7.2.5 Configuring the Topology Change Notification Function
Context
If an upper-layer Layer 2 network is not notified of the topology change in an
ERPS ring, the MAC address entries remain unchanged on the upper-layer network
and therefore user traffic is interrupted. To ensure nonstop traffic transmission,
configure the topology change notification function and specify the ERPS rings
that will be notified of the topology change.
In addition, if an ERPS ring frequently receives topology change notifications, its

nodes will have lower CPU processing capability and repeatedly update Flush-FDB
packets, consuming much bandwidth. To resolve this problem, set the topology
change protection interval at which topology change notifications are sent to
suppress topology change notification transmission, and set the maximum number
of topology change notifications that can be processed during the topology
change protection interval to prevent frequent MAC address and ARP entry
updates.
Procedure
Step 3 Run tc-notify erps ring { ring-id1 [ to ring-id2 ] } &<1-10>
The ERPS ring is configured to notify other ERPS rings of its topology change.
ring-id1 [ to ring-id2 ] specifies the start and end ring IDs of the ERPS rings that
will be notified of the topology change. Ensure that the ERPS rings specified by
ring-id1 and ring-id2 exist. If the specified rings do not exist, the topology change
notification function does not take effect.
After the ERPS rings receive the topology change notification from an ERPS ring,
they send Flush-FDB messages on their separate rings to instruct their nodes to
update MAC addresses so that user traffic is not interrupted.

Switches
Step 4 (Optional) Run tc-protection interval interval-value

The topology change protection interval at which topology change notification
messages are sent is set.
Step 5 (Optional) Run tc-protection threshold threshold-value
The number of times ERPS parses topology change notifications and updates
forwarding entries in the topology change protection interval is set.
The topology change protection interval is the one specified by the tc-protection
interval command.
Step 6 Run commit
----End
12.7.2.6 (Optional) Configuring ERPS Protection Switching
Context
To ensure that ERPS rings function normally when a node or link fails, configure
revertive/non-revertive switching, port blocking mode, and timers.
Procedure
Step 3 Run revertive { enable | disable }
The protection switching mode is specified.
By default, ERPS rings use revertive switching.
Step 4 Run quit
Step 5 Perform either of the following operations to configure a port blocking mode.
● To configure a port blocking mode for a port in the ERPS ring view, perform
the following steps:
a. Run the erps ring ring-id command to enter the ERPS ring view.
b. Run the port interface-type interface-number protect-switch { force |
manual } command to configure a port blocking mode for an ERPS port.
● To configure a port blocking mode in the interface view, perform the
following steps:
a. Run the interface interface-type interface-number command to enter the
interface view.

Switches
b. Run the erps ring ring-id protect-switch { force | manual } command to

configure a port blocking mode for the port.
The ERPS ring specified by ring ring-id must be the one to which the port
belongs.
To delete the specified port blocking mode, run the clear command in the ERPS
ring view.
Step 6 Run quit
Step 7 Run commit
----End
12.7.2.7 (Optional) Configuring Timers in an ERPS Ring
Context
After a link or node failure in an ERPS ring recovers, the device starts timers in the
ERPS ring to reduce traffic interruptions. This prevents network flapping.
Procedure
Step 3 Configure the WTR timer, Guard timer, and Holdoff timer in the ERPS ring
according to actual networking.
● Run wtr-timer time-value
The WTR timer is set.
By default, the WTR timer is 5 minutes in an ERPS ring.
● Run guard-timer time-value
The Guard timer is set.
By default, the Guard timer is 200 centiseconds in an ERPS ring.
● Run holdoff-timer time-value
The Holdoff timer is set.
By default, the Holdoff timer is 0 deciseconds in an ERPS ring.
Step 4 Run commit
----End

Switches
12.7.2.8 Verifying the ERPS Configuration
Procedure
● Run the display erps [ ring ring-id ] [ verbose ] command to check the
device ports added to an ERPS ring and ERPS ring configurations.
● Run the display erps interface interface-type interface-number [ ring ring-
id ] command to check physical configurations of the port added to an ERPS
ring.
----End
12.8 Maintaining ERPS
12.8.1 Clearing ERPS Statistics
Context
Before recollecting ERPS statistics, run the reset erps command to clear existing
ERPS statistics.
NOTICE
The cleared ERPS statistics cannot be restored. Exercise caution when you run this
command.
Procedure
Step 1 Run the reset erps [ ring ring-id ] statistics command to clear packet statistics in
an ERPS ring.
----End
12.9 Configuration Examples for ERPS
12.9.1 Example for Configuring ERPS Multi-instance
Networking Requirements

Switches
Figure 12-17 shows a network on which a multi-instance ERPS ring is used.
SwitchA through SwitchD constitute a ring network at the aggregation layer to
implement service aggregation at Layer 2 and process Layer 3 services. ERPS is
used on the ring network to provide protection switching for Layer 2 redundant
links. ERPS ring 1 and ERPS ring 2 are configured on SwitchA through SwitchD. P1
on SwitchB is a blocked port in ERPS ring 1, and P2 on SwitchA is a blocked port in
ERPS ring 2, implementing load balancing and link backup.
Figure 12-17 ERPS multi-instance networking
Network
Router1 Router2
SwitchC 10GE1/0/1 SwitchD
10GE1/0/2
10GE1/0/1 10GE1/0/2
ERPS
10GE1/0/2 10GE1/0/1
P2
SwitchA 10GE1/0/2
P1 SwitchB
10GE1/0/1
VLAN: VLAN:
100~200 300~400
ERPS ring1
ERPS ring2
Blocked Port1
Blocked Port2
Data Flow1
Data Flow2

Switches
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the link type of all ports to be added to ERPS rings as trunk.
2. Create ERPS rings and configure control VLANs and Ethernet Ring Protection
(ERP) instances in the ERPS rings.
3. Add Layer 2 ports to ERPS rings and specify port roles.
4. Configure the Guard timers and WTR timers in the ERPS rings.
5. Configure Layer 2 forwarding on SwitchA through SwitchD.
Procedure
Step 1 Configure the link type of all ports to be added to an ERPS ring as trunk.
# Configure SwitchA.
<HUAWEI> system-view
[~HUAWEI] sysname SwitchA
[*HUAWEI] commit
[~SwitchA] interface 10ge 1/0/1
[~SwitchA-10GE1/0/1] port link-type trunk
[*SwitchA-10GE1/0/1] commit
[~SwitchA-10GE1/0/1] quit
# Configure SwitchB.
[~HUAWEI] sysname SwitchB
[*HUAWEI] commit
[~SwitchB] interface 10ge 1/0/1
[~SwitchB-10GE1/0/1] port link-type trunk
[*SwitchB-10GE1/0/1] commit
[~SwitchB-10GE1/0/1] quit
# Configure SwitchC.
[~HUAWEI] sysname SwitchC
[*HUAWEI] commit
[~SwitchC] interface 10ge 1/0/1
[~SwitchC-10GE1/0/1] port link-type trunk
[*SwitchC-10GE1/0/1] commit
[~SwitchC-10GE1/0/1] quit
# Configure SwitchD.
[~HUAWEI] sysname SwitchD
[*HUAWEI] commit
[~SwitchD] interface 10ge 1/0/1
[~SwitchD-10GE1/0/1] port link-type trunk

Switches
[*SwitchD-10GE1/0/1] commit
[~SwitchD-10GE1/0/1] quit
Step 2 Create ERPS ring 1 and ERPS ring 2 and configure ERP instances in the two rings.
Set the control VLAN ID of ERPS ring 1 to 10 and the control VLAN ID of ERPS ring
2 to 20. Enable ERPS ring 1 to transmit data packets from VLANs 100 to 200 and
enable ERPS ring 2 to transmit data packets from VLANs 300 to 400.
[~SwitchA] erps ring 1
[*SwitchA-erps-ring1] control-vlan 10
[*SwitchA-erps-ring1] protected-instance 1
[*SwitchA-erps-ring1] commit
[~SwitchA-erps-ring1] quit
[~SwitchA] stp region-configuration
[~SwitchA-mst-region] instance 1 vlan 10 100 to 200
[*SwitchA-mst-region] commit
[~SwitchA-mst-region] quit
[~SwitchB] erps ring 1
[*SwitchB-erps-ring1] control-vlan 10
[*SwitchB-erps-ring1] protected-instance 1
[*SwitchB-erps-ring1] commit
[~SwitchB-erps-ring1] quit
[~SwitchB] stp region-configuration
[~SwitchB-mst-region] instance 1 vlan 10 100 to 200
[*SwitchB-mst-region] commit
[~SwitchB-mst-region] quit
[~SwitchC] erps ring 1
[*SwitchC-erps-ring1] control-vlan 10
[*SwitchC-erps-ring1] protected-instance 1
[*SwitchC-erps-ring1] commit
[~SwitchC-erps-ring1] quit
[~SwitchC] stp region-configuration
[~SwitchC-mst-region] instance 1 vlan 10 100 to 200
[*SwitchC-mst-region] commit
[~SwitchC-mst-region] quit

Switches
[~SwitchD] erps ring 1
[*SwitchD-erps-ring1] control-vlan 10
[*SwitchD-erps-ring1] protected-instance 1
[*SwitchD-erps-ring1] commit
[~SwitchD-erps-ring1] quit
[~SwitchD] stp region-configuration
[~SwitchD-mst-region] instance 1 vlan 10 100 to 200
[*SwitchD-mst-region] commit
[~SwitchD-mst-region] quit
Step 3 Add Layer 2 ports to ERPS rings and specify port roles. Configure 10GE 1/0/1 on
SwitchA and 10GE 1/0/2 on SwitchB as their respective RPL owner ports.
[~SwitchA-10GE1/0/1] stp disable
[*SwitchA-10GE1/0/1] erps ring 1
[*SwitchA-10GE1/0/1] erps ring 2 rpl owner
[~SwitchB-10GE1/0/1] stp disable
[*SwitchB-10GE1/0/1] erps ring 1
[*SwitchB-10GE1/0/2] erps ring 1 rpl owner
[~SwitchC-10GE1/0/1] stp disable
[*SwitchC-10GE1/0/1] erps ring 1

Switches

[~SwitchD-10GE1/0/1] stp disable
[*SwitchD-10GE1/0/1] erps ring 1
Step 4 Configure the Guard timers and WTR timers in the ERPS rings.
[~SwitchA-erps-ring1] wtr-timer 6
[*SwitchA-erps-ring1] guard-timer 100
[~SwitchB-erps-ring1] wtr-timer 6
[*SwitchB-erps-ring1] guard-timer 100
[~SwitchC-erps-ring1] wtr-timer 6
[*SwitchC-erps-ring1] guard-timer 100
[~SwitchD-erps-ring1] wtr-timer 6
[*SwitchD-erps-ring1] guard-timer 100

Switches

Step 5 Configure Layer 2 forwarding on SwitchA through SwitchD.

[~SwitchA] vlan batch 100 to 200 300 to 400
[*SwitchA] commit
[~SwitchA-10GE1/0/1] port trunk allow-pass vlan 100 to 200 300 to 400
[~SwitchB] vlan batch 100 to 200 300 to 400
[*SwitchB] commit
[~SwitchB-10GE1/0/1] port trunk allow-pass vlan 100 to 200 300 to 400
[~SwitchB-10GE1/0/2] port trunk allow-pass vlan 100 to 200 300 to 400
[~SwitchC] vlan batch 100 to 200 300 to 400
[*SwitchC] commit
[~SwitchC-10GE1/0/1] port trunk allow-pass vlan 100 to 200 300 to 400
[~SwitchC-10GE1/0/2] port trunk allow-pass vlan 100 to 200 300 to 400
[~SwitchD] vlan batch 100 to 200 300 to 400
[*SwitchD] commit
[~SwitchD-10GE1/0/1] port trunk allow-pass vlan 100 to 200 300 to 400
Step 6 Verify the configuration.

# After the network becomes stable, run the display erps command to check brief
information about the ERPS ring and ports added to the ERPS ring. SwitchB is used
as an example.
[~SwitchB] display erps
D : Discarding
F : Forwarding
R : RPL Owner
N : RPL Neighbour

Switches
FS : Forced Switch
MS : Manual Switch
Total number of rings configured = 2
Ring Control WTR Timer Guard Timer Port 1 Port 2
ID VLAN (min) (csec)
--------------------------------------------------------------------------------
1 10 6 100 (F)10GE1/0/1 (D,R)10GE1/0/2
2 20 6 100 (F)10GE1/0/1 (F)10GE1/0/2
--------------------------------------------------------------------------------
# Run the display erps verbose command to check detailed information about
the ERPS ring and ports added to the ERPS ring. SwitchB is used as an example.
[~SwitchB] display erps verbose
Ring ID :1
Description : Ring 1
Control Vlan : 10
Protected Instance :1
Service Vlan : 100 to 200
WTR Timer Setting (min) :6 Running (s) :0
Guard Timer Setting (csec) : 100 Running (csec) :0
Holdoff Timer Setting (deciseconds) : 0 Running (deciseconds) : 0
WTB Timer Running (csec) :0
Ring State : Idle
RAPS_MEL :7
Revertive Mode : Revertive
R-APS Channel Mode :-
Version :1
Sub-ring : No
Forced Switch Port :-
Manual Switch Port :-
TC-Notify :-
Time since last topology change : 0 days 0h:35m:5s
--------------------------------------------------------------------------------
Port Port Role Port Status Signal Status
--------------------------------------------------------------------------------
10GE1/0/1 Common Forwarding Non-failed
10GE1/0/2 RPL Owner Discarding Non-failed
Ring ID :2
Control Vlan : 20
Ring State : Idle
RAPS_MEL :7
Version :1
Sub-ring : No
TC-Notify :-
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----End

Switches
Configuration Files
● SwitchA configuration file
#
sysname SwitchA
#
vlan batch 10 20 100 to 200 300 to 400
#
stp region-configuration
instance 1 vlan 10 100 to 200
#
erps ring 1
control-vlan 10
protected-instance 1
wtr-timer 6
guard-timer 100
#
erps ring 2
control-vlan 20
wtr-timer 6
guard-timer 100
#
interface 10GE1/0/1
port link-type trunk
port trunk allow-pass vlan 10 20 100 to 200 300 to 400
stp disable
erps ring 1
erps ring 2 rpl owner
#
interface 10GE1/0/2
stp disable
erps ring 1
erps ring 2
#
return
● SwitchB configuration file

#
sysname SwitchB
#
vlan batch 10 20 100 to 200 300 to 400
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
#
erps ring 2
control-vlan 20
wtr-timer 6
guard-timer 100
#
interface 10GE1/0/1
stp disable
erps ring 1
erps ring 2
#

Switches
interface 10GE1/0/2
stp disable
erps ring 2
#
return
● SwitchC configuration file
#
sysname SwitchC
#
vlan batch 10 20 100 to 200 300 to 400
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
#
erps ring 2
control-vlan 20
wtr-timer 6
guard-timer 100
#
interface 10GE1/0/1
stp disable
erps ring 1
erps ring 2
#
interface 10GE1/0/2
stp disable
erps ring 1
erps ring 2
#
return
● SwitchD configuration file
#
sysname SwitchD
#
vlan batch 10 20 100 to 200 300 to 400
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
#
erps ring 2
control-vlan 20
wtr-timer 6
guard-timer 100
#
interface 10GE1/0/1

Switches

stp disable
erps ring 1
erps ring 2
#
interface 10GE1/0/2
stp disable
erps ring 1
erps ring 2
#
return
12.9.2 Example for Configuring an ERPS Multi-ring Network
Networking Requirements
On the ERPS multi-ring network shown in Figure 12-18, SwitchA, SwitchB, and
SwitchD constitute a major ring, and SwitchA, SwitchC, and SwitchD constitute a
sub-ring.
Figure 12-18 ERPS multi-ring networking
Network
Router1 Router2
10GE1/0/2
SwitchA SwitchD
10GE1/0/3 10GE1/0/1
10GE1/0/1 10GE1/0/3
sub-ring major ring
10GE1/0/2
10GE1/0/2
10GE1/0/1 10GE1/0/1
SwitchC SwitchB
RPL owner

Switches
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the link type of all ports to be added to ERPS rings as trunk.
2. Create ERPS rings and configure control VLANs and Ethernet Ring Protection
(ERP) instances in the ERPS rings.
3. Specify the ERPS version and configure a sub-ring.
4. Add Layer 2 ports to ERPS rings and specify port roles.
5. Configure the topology change notification and TC protection.
6. Configure the Guard timers and WTR timers in the ERPS rings.
7. Configure Layer 2 forwarding on SwitchA through SwitchD.
Procedure
Step 1 Configure the link type of all ports to be added to ERPS rings as trunk.
[~HUAWEI] sysname SwitchA
[*HUAWEI] commit
[~HUAWEI] sysname SwitchB
[*HUAWEI] commit
[~HUAWEI] sysname SwitchC
[*HUAWEI] commit

Switches
[~HUAWEI] sysname SwitchD
[*HUAWEI] commit
Step 2 Create ERPS ring 1 and ERPS ring 2 and configure ERP instances in the two rings.
Set the control VLAN ID of ERPS ring 1 to 10 and the control VLAN ID of ERPS ring
2 to 20. Enable ERPS ring 1 to transmit data packets from VLANs 100 to 200 and
enable ERPS ring 2 to transmit data packets from VLANs 300 to 400.
NOTE
A VLAN cannot be mapped to multiple MSTIs. If you map a VLAN that has already been
mapped to an MSTI to another MSTI, the original mapping will be deleted.

Switches
Step 3 Specify ERPSv2 and configure ERPS ring 2 as a sub-ring.
[~SwitchA-erps-ring1] version v2
[~SwitchA-erps-ring2] version v2
[*SwitchA-erps-ring2] sub-ring
[~SwitchB-erps-ring1] version v2
[~SwitchC-erps-ring2] version v2
[*SwitchC-erps-ring2] sub-ring
[~SwitchD-erps-ring1] version v2
[~SwitchD-erps-ring2] version v2
[*SwitchD-erps-ring2] sub-ring

Switches
Step 4 Add the ports to ERPS rings and specify port roles. Configure 10GE 1/0/1 on
SwitchB and 10GE 1/0/1 on SwitchC as their respective RPL owner ports.
[*SwitchB-10GE1/0/1] erps ring 1 rpl owner
[*SwitchC-10GE1/0/1] erps ring 2 rpl owner
Step 5 Configure the topology change notification function and TC protection on SwitchA
and SwitchD (interconnecting nodes).

Switches
[~SwitchA-erps-ring1] tc-protection interval 200
[*SwitchA-erps-ring1] tc-protection threshold 60
[~SwitchA-erps-ring2] tc-notify erps ring 1
[~SwitchD-erps-ring1] tc-protection interval 200
[*SwitchD-erps-ring1] tc-protection threshold 60
[~SwitchD-erps-ring2] tc-notify erps ring 1
Step 6 Configure the Guard timers and WTR timers in the ERPS rings.
Step 7 Configure Layer 2 forwarding on SwitchA through SwitchD.

Switches
[~SwitchA] vlan batch 100 to 200 300 to 400
[*SwitchA] commit
[~SwitchA-10GE1/0/1] port trunk allow-pass vlan 100 to 200
[~SwitchA-10GE1/0/3] port trunk allow-pass vlan 300 to 400
[~SwitchB] vlan batch 100 to 200
[*SwitchB] commit
[~SwitchB-10GE1/0/1] port trunk allow-pass vlan 100 to 200
[~SwitchB-10GE1/0/2] port trunk allow-pass vlan 100 to 200
[~SwitchC] vlan batch 300 to 400
[*SwitchC] commit
[~SwitchC-10GE1/0/1] port trunk allow-pass vlan 300 to 400
[~SwitchC-10GE1/0/2] port trunk allow-pass vlan 300 to 400
[~SwitchD] vlan batch 100 to 200 300 to 400
[*SwitchD] commit
[~SwitchD-10GE1/0/1] port trunk allow-pass vlan 100 to 200
[~SwitchD-10GE1/0/3] port trunk allow-pass vlan 300 to 400
Step 8 Verify the configuration.

# After the network becomes stable, run the display erps command to check brief
information about the ERPS ring and ports added to the ERPS ring. SwitchB is used
as an example.
[~SwitchB] display erps
D : Discarding
F : Forwarding

Switches
R : RPL Owner
N : RPL Neighbour
FS : Forced Switch
MS : Manual Switch
Total number of rings configured = 1
Ring Control WTR Timer Guard Timer Port 1 Port 2
ID VLAN (min) (csec)
--------------------------------------------------------------------------------
1 10 6 100 (D,R)10GE1/0/1 (F)10GE1/0/2
--------------------------------------------------------------------------------
# Run the display erps verbose command to check detailed information about
the ERPS ring and ports added to the ERPS ring. SwitchB is used as an example.
[~SwitchB] display erps verbose
Ring ID :1
Control Vlan : 10
Ring State : Idle
RAPS_MEL :7
Version :2
Sub-ring : No
TC-Notify :-
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
10GE1/0/1 RPL Owner Discarding Non-failed
----End
Configuration Files
● SwitchA configuration file
#
sysname SwitchA
#
vlan batch 10 20 100 to 200 300 to 400
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
version v2
tc-protection interval 200
tc-protection threshold 60
#
erps ring 2
control-vlan 20

Switches
wtr-timer 6
guard-timer 100
version v2
sub-ring
tc-notify erps ring 1
#
interface 10GE1/0/1
port trunk allow-pass vlan 10 100 to 200
stp disable
erps ring 1
#
interface 10GE1/0/2
stp disable
erps ring 1
erps ring 2
#
interface 10GE1/0/3
stp disable
erps ring 2
#
return
● SwitchB configuration file
#
sysname SwitchB
#
vlan batch 10 100 to 200
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
version v2
#
interface 10GE1/0/1
stp disable
#
interface 10GE1/0/2
stp disable
erps ring 1
#
return
● SwitchC configuration file
#
sysname SwitchC
#
vlan batch 20 300 to 400
#
#
erps ring 2
control-vlan 20
wtr-timer 6

Switches
guard-timer 100
version v2
sub-ring
#
interface 10GE1/0/1
stp disable
#
interface 10GE1/0/2
stp disable
erps ring 2
#
return
● SwitchD configuration file

#
sysname SwitchD
#
vlan batch 10 20 100 to 200 300 to 400
#
#
erps ring 1
control-vlan 10
wtr-timer 6
guard-timer 100
version v2
tc-protection interval 200
tc-protection threshold 60
#
erps ring 2
control-vlan 20
wtr-timer 6
guard-timer 100
version v2
sub-ring
tc-notify erps ring 1
#
interface 10GE1/0/1
stp disable
erps ring 1
#
interface 10GE1/0/2
stp disable
erps ring 1
erps ring 2
#
interface 10GE1/0/3
stp disable
erps ring 2
#
return

Switches
12.10 Troubleshooting ERPS
12.10.1 Traffic Forwarding Fails in an ERPS Ring
Fault Description
After ERPS is configured, user traffic cannot be properly forwarded due to
abnormal ERPS ring status.
Procedure
Step 1 Check the port roles in the ERPS ring and status of each device in the ring.
In an ERPS ring, there should be only one RPL owner port. Other ports are
common ports or RPL neighbor ports.
Run the display erps [ ring ring-id ] verbose command in any view to check
whether the value of Ring State is Idle. (Perform this operation on each device in
the ERPS ring.)
If the ERPS ring is incomplete or its status is abnormal, perform the following
operations:
1. Verify that all nodes in the ERPS ring are added to the ERPS ring.
2. Check whether the ERPS ring configuration including the ERPS version
number and major ring/sub-ring on devices in the ERPS ring are the same.
3. Verify that port roles, control VLANs, and protected instances are correctly
configured on all nodes in the ERPS ring.
4. Verify that ports can allow packets of the specified VLANs to pass.
----End

01-12 ERPS (G 8032) Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01-12 ERPS (G 8032) Configuration

Uploaded by

Copyright:

Available Formats

CloudEngine 8800, 7800, 6800, and 5800 Series

12 ERPS (G.8032) Configuration

This chapter describes how to configure Ethernet Ring Protection Switching

12.1 Overview of ERPS

12.1 Overview of ERPS

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 638

● Multi-ring topologies, such as intersecting rings

Table 12-1 Ring network protocols supported by devices

Ring Network Advantage Disadvantage

STP/RSTP/MSTP ● Applies to all Layer 2 Provides low convergence

ERPS ● Provides fast Requires the network

ERPS, a standard ITU-T protocol, prevent loops on ring networks. It optimizes

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 639

● Provides fast convergence and carrier-class reliability.

12.2 Understanding ERPS

12.2.1 Basic ERPS Concepts

Figure 12-1 ERPS single-ring networking

ERPS can be deployed on the network shown in Figure 12-1.

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 640

Figure 12-2 ERPS major ring and sub-ring networking

Major Ring Sub-Ring

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 641

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 642

Revertive and Non-revertive Switching

Port Blocking Modes

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 643

Only ERPSv2 supports port blocking modes.

RAPS PDU Transmission Mode in a Sub-ring

Figure 12-3 Interconnected rings with a VC or NVC

Ethernet Ring Node

RPL owner Interface

RAPS Virtual Channel

When sub-ring links are incontiguous, VCs must be used.

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 644

Figure 12-4 VC networking

Ethernet Ring Node

RPL owner Interface

RAPS Virtual Channel

VC Applies to scenarios in Requires VC resource reservation and

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 645

RAPS Advantage Disadvantage

NVC Does not need to reserve Is not applicable to scenarios in

12.2.2 RAPS PDUs

Figure 12-5 RAPS PDU format

... R-APS Specific Information(32 octets)

Table 12-3 describes the fields in an RAPS PDU.

Table 12-3 Fields in an RAPS PDU

Field Leng Description

MEL 3 bits Identifies the maintenance entity group (MEG) level

Version 5 bits ● 0x00: ERPSv1

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 646

Field Leng Description

TLV Not Describes information to be loaded. The end TLV

Figure 12-6 Format of the R-APS Specific Information field in ERPSv1

Request Reserved Status Node ID(6 octets)

Reserved 2(24 octets)

Figure 12-7 Format of the R-APS Specific Information field in ERPSv2

Request Status Node ID(6 octets)

Reserved 2(24 octets)

Table 12-4 describes sub-fields in the R-APS Specific Information field.

Issue 09 (2021-06-03) Copyright © Huawei Technologies Co., Ltd. 647

Table 12-4 Sub-fields in the R-APS Specific Information field

Sub-Field Length Description

Reserved 4 bits Reserved 1 is used in ERPSv1 for message reply or