Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 577)

Multi-Service IronWare Switching Configuration Guide 547
53-1003036-02
ERP support for PBB (Brocade MLX series and Brocade NetIron XMR)
15
• Each sub-ring will be connected to either a major ring or a sub-ring which is referred to as a
parent ring.
• In Figure 154 ERP instance 1 is the parent ring for sub-ring ERP instance 2 and ERP instance 2
is the parent ring for sub-ring ERP instance 3.
• If both the major ring and sub-ring are running on the same VLAN then the parent ring can be
identified based on the VLAN, However, if they are running on different VLANs (especially in
PB/PBB networks) with multiple ERP instances then the administrator must specify the parent
ring ID using the sub-ring parent-ring-id erp_id> command.
• The sub-ring parent-ring-id must be configured on the sub-ring ERP instance of an
interconnection node.
RAPS-propagate-tc
FIGURE 155 RAPS-propagate-tc
• The RAPS-propagate-tc command must be configured on the sub-ring ERP instance.
• When the raps-propagate-tc command is configured, any topology change on the sub-ring will
be communicated to the major ring by sending a R-APS(Flush event). This results in a FDB flush
on all the major ring nodes.
• The RAPS-propagate-tc configuration is required only when a node is present in between two
interconnection nodes (for example: Node-4 in above topology).
Node-3 Configuration for Major ring VLAN 100
!
vlan 100
tagged ethe 1/1 ethe 1/3
!
erp 100
left-interface vlan 100 ethe 1/3
right-interface vlan 100 ethe 1/1