User guide

Configuring Network Services Protection Switching-EPSR
541
AlliedView NMS Administration Guide
FIGURE 6-136 EPSR Domains table
Note that the domain name nms is not included for the .20 device for the Ctrl VID 300. Since the links and VLAN interface
do exist (according to the GUI maps), the problem must be that the .20 device is not protected by any EPSR Control ring
and is not part of a domain.
To resolve this problem, the user can bring up the VLAN Interfaces on .20 device (in this case the VID: 300) and select
Configure EPS Control Ring ...as shown below. This allows the user to associate the VLAN Interface with the domain used
by the Control VLAN.
FIGURE 6-137 Control Ring Misconfiguration
6.13.6.2 EPSR Activated (SP Port Now Used for Data Flow)
When any link in the ring is broken, except the link connected to the master's secondary port, the secondary port link is
unblocked so data can travel on the alternate path. Details of what is happening to the control messaging are explained in the
iMAP User Guide. At the AlliedView NMS, there are several windows that show pictorially what is happening.
Note: The following figures assume that port 11.1 on the .20 device has been disconnected or disabled.
• Control Ring - The following figure shows that the link between the .20 and .30 device is now blocked. The link between
.30 and .80, which was previously blocked, has now been opened so that traffic that used to go from .30 to .20 and then
to .80 is now going directly to the .20. Moreover, the Master and Transit labels are now red.