Assigning the rpl owner role and setting the rpl – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 563
![background image](/manuals/361635/563/background.png)
Multi-Service IronWare Switching Configuration Guide
533
53-1003036-02
ERP commands
15
For proper operation you must configure the interfaces following the same manner on each ERN,
such as left/right, left/right, and so on.
In NetIron R05.3.00 the interface configuration commands have been enhanced to allow
configuration of ERP with ESI VLANs.
Syntax: [no] left-interface [vlan vlan-id | esi esi_name vlan vlan_id] e slot/number
Syntax: [no] right-interface [vlan vlan-id | esi esi_name vlan vlan_id] e slot/number ]
Use the no command to remove the configuration of each interface.
Assigning the RPL owner role and setting the RPL
Each ring needs to have one RPL owner for each ring. The RPL owner’s role is to block traffic on one
port when no failure exists in the ring. The blocked port will be the left interface that you initially
configured. After configuring the ERN to be the RPL owner, you next must set the RPL. To set the
RPL you need to specify the VLAN and Ethernet slot and port.
NOTE
When you assign the role of RPL owner, you must also configure the RPL.
Syntax: [no] rpl-owner
Syntax: [no] rpl [vlan vlan-id | esi esi_name vlan vlan_id] e slot/number
Enabling sub-rings for multi-ring and ladder topologies
In multi-ring and ladder topologies, you can enable the multi-ring feature.
Interconnected rings consists of one major ring and at least one sub-ring within the same VLAN or
different VLANs. A sub-ring is not a complete ring. Nodes within a sub-ring can be configured as a
one-arm ring. Each sub-ring must have its own RPL owner and RPL ports as appropriate.
RPL ports and the RPL owner also need to be configured in a sub-ring. All ERP features are
available in both major and sub-rings.
R-APS PDUs only flow in the nodes with same ring ID. The R-APS PDU can be forwarded through the
port in sub-ring blocking state.
Syntax: [no] sub-ring [parent-ring-id <erp-id>]
Parent-ring-id is used when there are different VLANs on the major ring and sub-ring. In such a
case, use the parent-ring-id configuration to determine the ring to which the sub-ring is connected.
The parent ring can be either another sub-ring or major ring connected to the sub-ring.
Use the no command to delete the sub-ring support.
If you have six nodes you can put them in one ring. The latency time for packet transport, however,
increases in big topologies even within the same VLAN, so it is better to separate them out.