CLI Reference Guide-R02

Chapter 19 | ERPS Commands
– 579 –
■
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 instance has been activated with the enable (instance) command, the
configuration of the control VLAN cannot be modified. Use the no enable (ring)
command to stop the ERPS instance before making any configuration changes
to the control VLAN.
Example
Console(config)#vlan database
Console(config-vlan)#vlan 2 name rdc media ethernet state active
Console(config-vlan)#exit
Console(config)#interface ethernet 1/12
Console(config-if)#switchport allowed vlan add 2 tagged
Console(config-if)#interface ethernet 1/11
Console(config-if)#switchport allowed vlan add 2 tagged
Console(config-if)#exit
Console(config)#erps vlan-group alpha add 2
Console(config)#erps instance rd1
Console(config-erps-inst)#control-vlan 2
Console(config-erps-inst)#
rpl owner This command configures a ring node to be the Ring Protection Link (RPL) owner.
Use the no form to restore the default setting.
Syntax
rpl owner
no rpl
Default Setting
None (that is, neither owner nor neighbor)
Command Mode
ERPS Instance Configuration
Command Usage
◆ Only one RPL owner can be configured on an instance. 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 instance or the protection state is
enabled with the erps forced-switch or erps manual-switch command).
◆ The east and west connections to the instance must be specified for all ring
nodes using the ring-port command. When this switch is configured as the RPL
owner, the west ring port is automatically set as being connected to the RPL.