Table of Contents
Advertisement
Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
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 277 on page 420
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 277: 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
Configuration Guidelines for ERPS
1.
Create an ERPS ring
index in the G.8032 database.
2.
Configure the east and west interfaces
Each node on the ring connects to it through two ring ports. Configure one
port connected to the next node in the ring to the east (or clockwise direction)
and another port facing west in the ring.
3.
Configure the RPL owner
one node in the ring as the Ring Protection Link (RPL) owner. When this switch
is configured as the RPL owner, the west ring port is set as being connected to
the RPL. Under normal operations (Idle state), the RPL is blocked to ensure that
a loop cannot form in the ring. If a signal failure brings down any other link in
(Signal Fail Condition) illustrates a situation where
RPL Owner
Node
for ERP1
ring node B
ring node C
RPL Owner
Node
for ERP2
ring node F
(Configure Domain –
Add): The ring name is used as an
(Configure Domain – Configure
(Configure Domain – Configure
– 420 –
Signal Fail Condition
RPL
ring node A
ERP1
ring link
(ERP1)
ring node D
FAILURE
ERP2
ring node E
RPL
Details): Configure
RPL Owner
Node
for ERP1
RPL Owner
Node
for ERP2
Details):
Advertisement
Chapters
Table of Contents
