Edge-Core ECS3510-10PD Management Manual page 499

10-port layer 2
Table of Contents

Advertisement

not form a closed loop. A closed loop may be formed by the ring links of
ERP2 and the ring link between the interconnection nodes that is controlled
by ERP1. ERP2 is a sub-ring. Ring node A is the RPL owner node for ERP1,
and ring node E is the RPL owner node for ERP2. These ring nodes (A and
E) are responsible for blocking the traffic channel on the RPL for ERP1 and
ERP2 respectively. There is no restriction on which ring link on an ring may
be set as the RPL. For example the RPL of ERP1 could be set as the link
between ring node C and D.
Ring nodes C and D, that are common to both ERP1 and ERP2, are called
interconnection nodes. The ring link between the interconnection nodes are
controlled and protected by the ring it belongs to. In the example for the
Normal Condition, the ring link between ring nodes C and D is part of ERP1,
and, as such, are controlled and protected by ERP1. Ethernet characteristic
information traffic corresponding to the traffic channel may be transferred
over a common Ethernet connection for ERP1 and ERP2 through the
interconnection nodes C and D. Interconnection nodes C and D have
separate ERP Control Processes for each Ethernet Ring.
Figure 286 on page 499
protection switching has occurred due to an SF condition on the ring link
between interconnection nodes C and D. The failure of this ring link
triggers protection only on the ring to which it belongs, in this case ERP1.
The traffic and R-APS channels are blocked bi-directionally on the ports
where the failure is detected and bi-directionally unblocked at the RPL
connection point on ERP1. The traffic channels remain bi-directionally
blocked at the RPL connection point on ERP2. This prevents the formation
of a loop.
Figure 286: Ring Interconnection Architecture (Multi-ring/Ladder Network)
Normal Condition
RPL
ring node B
ring node A
ERP1
ring link
(ERP1)
ring node C
ring node D
ERP2
ring node F
ring node E
RPL
– 499 –
| Basic Administration Protocols
C
14
HAPTER
Ethernet Ring Protection Switching
(Signal Fail Condition) illustrates a situation where
Signal Fail Condition
RPL Owner
Node
for ERP1
ring node B
ring node C
RPL Owner
Node
for ERP2
ring node F
RPL Owner
Node
RPL
for ERP1
ring node A
ERP1
ring link
(ERP1)
ring node D
FAILURE
ERP2
RPL Owner
Node
for ERP2
ring node E
RPL

Advertisement

Table of Contents
loading

Table of Contents