User's Guide

© Copyright 2018 TRENDnet. All Rights Reserved.
TRENDnet User’s Guide
Managed Industrial L2 Switch
71
ERPS (Ethernet Ring Protection Switching)
The ITU-T G.8032 Ethernet Ring Protection Switching feature implements protection
switching mechanisms for Ethernet layer ring topologies. This feature uses the G.8032
Ethernet Ring Protection (ERP) protocol, defined in ITU-T G.8032, to provide protection
for Ethernet traffic in a ring topology, while ensuring that no loops are within the ring at
the Ethernet layer. The loops are prevented by blocking traffic on either a predetermined
link or a failed link.
The Ethernet ring protection functionality includes the following:
• Loop avoidance
• The use of learning, forwarding, and Filtering Database (FDB mechanisms
Loop avoidance in an Ethernet ring is achieved by guaranteeing that, at any time, traffic
may flow on all but one of the ring links. This particular link is called the ring protection
link (RPL) and under normal conditions this ring link is blocked, i.e., not used for service
traffic. One designated Ethernet ring node, the RPL owner node, is responsible to block
traffic at one end of the RPL. Under an Ethernet ring failure condition, the RPL owner
node is responsible for unblocking its end of the RPL, unless the RPL has failed, allowing
the RPL to be used for traffic. The other Ethernet ring node adjacent to the RPL, the RPL
neighbour node, may also participate in blocking or unblocking its end of the RPL.
The Ethernet rings could support a multi-ring/ladder network that consists of conjoined
Ethernet rings by one or more interconnection points. The protection switching
mechanisms and protocol defined in this Recommendation shall be applicable for a
multi-ring/ladder network, if the following principles are adhered to:
• R-APS channels are not shared across Ethernet ring interconnections;
• on each ring port, each traffic channel and each R-APS channel are controlled
(e.g., for blocking or flushing) by the Ethernet ring protection control process
(ERP control process) of only one Ethernet ring;
• Each major ring or sub-ring must have its own RPL.
In an Ethernet ring, without congestion, with all Ethernet ring nodes in the idle state
(i.e., no detected failure, no active automatic or external command and receiving only
"NR, RB" R-APS messages), with less than 1200 km of ring fibre circumference and fewer
than 16 Ethernet ring nodes, the switch completion time (transfer time as defined in
[ITU-T G.808.1]) for a failure on a ring link shall be less than 50 ms.
The ring protection architecture relies on the existence of an APS protocol to coordinate
ring protection actions around an Ethernet ring.
The Switch supports up to six rings.
Guard timer – All ERNs use a guard timer. The guard timer prevents the possibility of
forming a closed loop and prevents ERNs from applying outdated R-APS messages. The
guard timer activates when an ERN receives information about a local switching request,
such as after a switch fail (SF), manual switch (MS), or forced switch (FS). When this
timer expires, the ERN begins to apply actions from the R-APS it receives. This timer
cannot be manually stopped.
Wait to restore (WTR) timer – The RPL owner uses the WTR timer. The WTR timer
applies to the revertive mode to prevent frequent triggering of the protection switching
due to port flapping or intermittent signal failure defects. When this timer expires, the
RPL owner sends a R-APS (NR, RB) through the ring.
Wait to Block (WTB) timers – This wait-to-block timer is activated on the RPL owner.
The RPL owner uses WTB timers before initiating an RPL block and then reverting to the
idle state after operator-initiated commands, such as for FS or MS conditions, are
entered. Because multiple FS commands are allowed to co-exist in a ring, the WTB timer
ensures that the clearing of a single FS command does not trigger the re-blocking of the
RPL. The WTB timer is defined to be 5 seconds longer than the guard timer, which is
enough time to allow a reporting ERN to transmit two R-APS messages and allow the
ring to identify the latent condition. When clearing a MS command, the WTB timer
prevents the formation of a closed loop due to the RPL owner node applying an
outdated remote MS request during the recovery process.
Hold-off timer – Each ERN uses a hold-off timer to delay reporting a port failure. When
the timer expires, the ERN checks the port status. If the issue still exists, the failure is
reported. If the issue does not exist, nothing is reported.