Web Management Guide-R04

Table Of Contents
Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 492 –
Control VLAN – A dedicated VLAN used for sending and receiving E-APS
protocol messages. (Range: 1-4094)
Configure one control VLAN for each ERPS ring. First create the VLAN to be used
as the control VLAN (see “Configuring VLAN Groups” on page 171), add the ring
ports for the east and west interface as tagged members to this VLAN (see
Adding Static Members to VLANs” on page 173), and then use this parameter
to add it to the ring.
The following restrictions are recommended to avoid creating a loop in the
network or other problems which may occur under some situations:
The Control VLAN must not be configured as a Layer 3 interface (with an IP
address), nor as a dynamic VLAN (with GVRP enabled).
In addition, only ring ports may be added to the Control VLAN. No other
ports can be members of this VLAN.
Also, the ring ports of the Control VLAN must be tagged.
Once the ring has been activated, the configuration of the control VLAN cannot
be modified. Use the Admin Status parameter to stop the ERPS ring before
making any configuration changes to the control VLAN.
Node State – Refer to the parameters for the Show page.
Node Type – Shows ERPS node type as one of the following:
None – Node is neither Ring Protection Link (RPL) owner nor neighbor.
(This is the default setting.)
RPL Owner – Specifies a ring node to be the RPL owner.
Only one RPL owner can be configured on a ring. The owner blocks
traffic on the RPL during Idle state, and unblocks it during Protection
state (that is, when a signal fault is detected on the ring or the
protection state is enabled with the Forced Switch or Manual Switch
commands on the Configure Operation page).
The east and west connections to the ring must be specified for all ring
nodes. When this switch is configured as the RPL owner, the west ring
port is automatically set as being connected to the RPL.
RPL Neighbor – Specifies a ring node to be the RPL neighbor.
The RPL neighbor node, when configured, is a ring node adjacent to
the RPL that is responsible for blocking its end of the RPL under normal
conditions (i.e., the ring is established and no requests are present in
the ring) in addition to the block at the other end by the RPL Owner
Node. The RPL neighbor node may participate in blocking or
unblocking its end of the RPL, but is not responsible for activating the
reversion behavior.