G.8032 is an International Telecommunication Union (ITU) standard for ERPS. It prevents loops on a per-VLAN basis with networks that are wired in a simple ring topology. The loops are prevented by blocking traffic on either a predetermined link or a failed link.

G.8032 Version 2 provides enhancements in support of multiple ring and ladder topologies. G.8032 offers a rapid detection and recovery time if a link or node.

This guide contains topologies and examples on how to configure g8032 ERPS configuration.

Figure 13-22 displays a sample Ring Protection topology on which protection switching is configured with four bridges. The Ring Protection Link (RPL) owner is the link between Bridge 3 and Bridge 4 (xe16), on which one side of the link is defined explicitly as RPL owner (Bridge 4) and RPL neighbor (Bridge 3). The rest of the bridges are explicitly configured RPL non owner to enable ERPS in the ring.

Configure below hardware-profile commands related to CFM in configuration mode and reboot the nodes.

An ethernet ring that is connected to a Major Ring at the Interconnection Nodes. By itself, the Sub-Ring does not constitute a closed ring. A Sub-Ring is connected to the Interconnection nodes on only one port which is configured as east-interface.

Figure 13-23 displays a sample Ring Protection topology on which protection switching is configured with six bridges. This constitutes of one major ring (Bridge2, Bridge3, Bridge4 and Bridge 5) and one sub-ring (Bridge2, Bridge1, Bridge6 and Bridge5).

Major ring’s RPL in enabled between Bridge 3(owner node) and Bridge 4(neighbor node) on xe4 and other devices are non-owner nodes for that ring. Sub-ring’s RPL is enabled between bridge 1(owner node) and bridge 2 (neighbor node) on link xe2 and other devices on the non-owner nodes. Bridge 2 and Bridge 5 are called interconnected nodes since they are common node between major ring and subring. Virtual channel is enabled for this Subring on interconnected nodes on vlan 100 and tcn propagation is enabled.

Figure 3 displays a sample Ring Protection topology on which protection switching is configured with 5 bridges on lag interfaces. The topology contains one major ring and one subring with non-virtual channel. The Ring Protection Link (RPL) for major ring is the link between Bridge 4 (owner) and Bridge 3 (neighbor) on lag interface po3. The subring is configured with no virtual channel and it’s RPL link is configured between bridge 1 (neighbor) and bridge 5 (owner) on lag interface po6. The rest of the bridges are explicitly configured RPL non owner to enable ERPS in the ring in both major and subring.

Figure 13-24 displays a sample Ethernet Ring Protection Switching topology.

An Ethernet ring that is connected to a Major Ring at the Interconnection Nodes. Non-Bridged AC-VLAN’s should follow the port state (block/forward) as ERPS data VLAN’s.

User can give control for non-bridged AC_Vlans by configuring "erps-instance <id|none>". In sub-interface, user can add “erps-instance (NAME | none)” CLI. This will exclude the sub-intf/lif’s to be processed by ERPS.

Erps-instance <name>, this sub-interface will follow specified erps-instance state for non-data vlan's.

This is useful in case of multiple instances, where one instance is in forward and another is block. So non-data vlan’s has to follow specific instance configured by user. Default is lower instance id, if not configured.

Erps-instance none, this sub-interface will not managed by ERPS. (It will be always in forward state with ERPS not controlling it).

No command specified in sub-intf mode, this sub-intf/lif will be managed by ERPS and default erps-instance id will be used for LIF/sub-intf to follow the ERPS block/forward state. Default value is lower configured instance-id