Provision Ethernet Ring Protection (ERP)
566
WebEML User Manual
53.3 General
Use the procedures in this chapter to configure ERP on every node in the ring. The
procedures are arranged in the sequence to correctly provision ERP
To provision a new ERP topology on ports with existing cross-connections and
VLANs, the cross-connections and VLANs must be deleted before creating the ERP
topology and re-entered according to this chapter. During this period of time all traffic
associated with these cross-connections and VLANs will be lost. Schedule
appropriate maintenance window prior to starting ERP provisioning on traffic barring
systems.
It is recommended to establish correct communication throughout the ring:
Protection Status is ‘Idle,’ Port Current statuses are ‘Normal,’ and Port Forward
status is Blocked for RPL Owner and Unblocked for all other ports prior to adding
traffic flows to the ring.
This chapter does not cover all aspects of Ethernet Ring design and assumes the
operator has a valid Ethernet Ring design.
ERP Switching is implemented according to ITU-T G.8032 recommendations.
53.4 Procedures
This section provides the following procedures:
• To provision an Ethernet ring topology
• To enable an ERP Instance
• To add a PDH Flow to an ERP Instance
• To add a radio flow to an ERP instance
• To add an Ethernet flow to an ERP instance
• Add VLAN flow to ERP instance
• To provision ETH OAM switching criteria (optional)
To provision an Ethernet ring topology
Caution: For radios to be associated with a new ERP topology which have existing cross-
connections and/or VLAN traffic provisioned, ERP topology provisioning is traffic affecting.
Release 7.0.0 3DB 19286 ACAA Issue 01
To Next Page
Loading...