![Siklu EtherHaul Скачать руководство пользователя страница 104](http://html1.mh-extra.com/html/siklu/etherhaul/etherhaul_operation-and-maintenance-manual_1270492104.webp)
EtherHaul Operation, Administration and Maintenance Manual
Page 104
12
Ethernet Ring Protection (ERP)
This chapter describes the Ethernet Ring Protection functionality based on G.8032v2.
ERP is a licensed feature that requires license for operation. Before configuring it, verify
that license is available and enable the
L2 (resiliency
) license component.
12.1
Ethernet Ring Protection Description
Ethernet Ring Protection (ERP) is a network resiliency protocol defined in ITU -T G.8032.
The EtherHaul supports ERP G.8032v2, with backwards compatibility to previous
versions. ERP support enables protection for any point of failure in the network. This
means that network connectivity is maintained in the event that the Ethernet link, the
radio link, or even the entire EtherHaul fails. This provides resiliency for both Ethernet -
Ethernet rings that typically protect single site connectivity and Ethernet-RF rings that
typically protect against RF network failure.
ERP is a relatively simple protocol that operates at the network level on the set of nodes
that constitute the ring or set of rings. ERP monitors the Ethernet layer to discover and
identify Signal Failure (SF) conditions, and prevents loops within the ring by blocking
one of the links (either a pre-determined link or a failed link). ERP verifies at all times
the ring is closed that frames will not be looped. This is accomplished by ta king down a
Ring protection Link (RPL) whenever there is no failure in the ring.
Using ERP, EtherHaul provides protection and recovery switching within 50 mSec for
typical rings. The ERP mechanism uses a very small percentage of total available
bandwidth.
The following figure illustrates the basic ERP protection mechanism. In normal ring
operation, the RPL is blocked. In a failure condition, the failed link is blocked, R-APS
messages are sent from the nodes adjacent to the failed links in order to unblock t he
RPL, and an FDB flush is performed on all ring nodes as necessary.
Note:
ERP configuration and monitoring supported in the CLI only.