Example for Configuring ERPS (Single Ring)
Networking Requirements
Figure 1. ERPS Configuration Example
To solve the loop problem caused by redundant links in the network, ERPS protocol can be deployed on the devices that form the ring network. As shown in Figure 4, taking the deployment of a single-ring multi-instance ERPS ring as an example.
- Switch A, Switch B, Switch C and Switch D form an ERPS ring, on which two instances are configured.
- The RPL Owner Node of instance 1 is the interface te-1/1/19 (port1) on Switch A. The RPL is the link between Switch A and Switch D. The control VLAN is VLAN 4001 and the data VLANs are VLAN 100-200.
- The RPL Owner Node of instance 2 is the interface ge-1/1/5 (port0) on Switch C. Its RPL is the link between Switch B and Switch C. The control VLAN is VLAN 4002 and the data VLANs are VLANs 300-400.
NOTEs:
|
Procedure
Switch A
Step1 Disable spanning-tree protocol on the interface where you want to enable ERPS.
admin@SwitchA# set protocols spanning-tree interface te-1/1/3 enable false admin@SwitchA# set protocols spanning-tree interface te-1/1/19 enable false
Step2 Configure protected MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.
NOTE: The ERPS control VLAN must be in one of the protected MSTP instance.
admin@SwitchA# set protocols spanning-tree mstp msti 1 vlan 100-200 admin@SwitchA# set protocols spanning-tree mstp msti 1 vlan 4001 admin@SwitchA# set protocols spanning-tree mstp msti 2 vlan 300-400 admin@SwitchA# set protocols spanning-tree mstp msti 2 vlan 4002
Step3 Configure VLAN and port mode.
admin@SwitchA# set interface gigabit-ethernet te-1/1/3 family ethernet-switching port-mode trunk admin@SwitchA# set interface gigabit-ethernet te-1/1/3 family ethernet-switching vlan members 100-200,300-400,4001,4002 admin@SwitchA# set interface gigabit-ethernet te-1/1/19 family ethernet-switching port-mode trunk admin@SwitchA# set interface gigabit-ethernet te-1/1/19 family ethernet-switching vlan members 100-200,300-400,4001,4002
Step4 Enable ERPS function globally. By default, ERPS is disabled.
admin@SwitchA# set protocols erps enable true
Step5 Create the ERPS ring with a given ID.
admin@SwitchA# set protocols erps ring 1
Step6 Configure port0 and port1 of the ERPS ring.
admin@SwitchA# set protocols erps ring 1 port0 interface te-1/1/3 admin@SwitchA# set protocols erps ring 1 port1 interface te-1/1/19
Step7 Create instance for the ERPS ring.
admin@SwitchA# set protocols erps ring 1 instance 1 admin@SwitchA# set protocols erps ring 1 instance 2
Step8 Configure port te-1/1/19 (port1) on Switch A as the RPL Owner Node for ERPS ring 1 instance 1.
admin@SwitchA# set protocols erps ring 1 instance 1 rpl port1 owner
Step9 Configure the control VLAN.
admin@SwitchA# set protocols erps ring 1 instance 1 control-vlan 4001 admin@SwitchA# set protocols erps ring 1 instance 2 control-vlan 4002
Step10 Configure the MSTP instance of VLANs that are protected by this ring instance.
admin@SwitchA# set protocols erps ring 1 instance 1 protected-instance 1 admin@SwitchA# set protocols erps ring 1 instance 2 protected-instance 2
Step11 Commit the configurations.
admin@SwitchA# commit
Switch B
Step1 Disable spanning-tree protocol on the interface where you want to enable ERPS.
admin@SwitchB# set protocols spanning-tree interface ge-1/1/3 enable false admin@SwitchB# set protocols spanning-tree interface ge-1/1/5 enable false
Step2 Configure protected MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.
NOTE: The ERPS control VLAN must be in one of the protected MSTP instance.
admin@SwitchB# set protocols spanning-tree mstp msti 1 vlan 100-200 admin@SwitchB# set protocols spanning-tree mstp msti 1 vlan 4001 admin@SwitchB# set protocols spanning-tree mstp msti 2 vlan 300-400 admin@SwitchB# set protocols spanning-tree mstp msti 2 vlan 4002
Step3 Configure VLAN and port mode.
admin@SwitchB# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching port-mode trunk admin@SwitchB# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 100-200,300-400,4001,4002 admin@SwitchB# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching port-mode trunk admin@SwitchB# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching vlan members 100-200,300-400,4001,4002
Step4 Enable ERPS function globally. By default, ERPS is disabled.
admin@SwitchB# set protocols erps enable true
Step5 Create the ERPS ring with a given ID.
admin@SwitchB# set protocols erps ring 1
Step6 Configure port0 and port1 of the ERPS ring.
admin@SwitchB# set protocols erps ring 1 port0 interface ge-1/1/3 admin@SwitchB# set protocols erps ring 1 port1 interface ge-1/1/5
Step7 Create instance for the ERPS ring.
admin@SwitchB# set protocols erps ring 1 instance 1 admin@SwitchB# set protocols erps ring 1 instance 2
Step8 Configure port ge-1/1/5 (port1) on Switch C as the RPL Neighbor Node for ERPS ring 1 instance 2.
admin@SwitchB# set protocols erps ring 1 instance 2 rpl port1 neighbor
Step9 Configure the control VLAN.
admin@SwitchB# set protocols erps ring 1 instance 1 control-vlan 4001 admin@SwitchB# set protocols erps ring 1 instance 2 control-vlan 4002
Step10 Configure the MSTP instance of VLANs that are protected by this ring instance.
admin@SwitchB# set protocols erps ring 1 instance 1 protected-instance 1 admin@SwitchB# set protocols erps ring 1 instance 2 protected-instance 2
Step11 Commit the configurations.
admin@SwitchB# commit
Switch C
Step1 Disable spanning-tree protocol on the interface where you want to enable ERPS.
admin@SwitchC# set protocols spanning-tree interface te-1/1/7 enable false admin@SwitchC# set protocols spanning-tree interface ge-1/1/5 enable false
Step2 Configure MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.
NOTE: The ERPS control VLAN must be in one of the protected MSTP instance.
admin@SwitchC# set protocols spanning-tree mstp msti 1 vlan 100-200 admin@SwitchC# set protocols spanning-tree mstp msti 1 vlan 4001 admin@SwitchC# set protocols spanning-tree mstp msti 2 vlan 300-400 admin@SwitchC# set protocols spanning-tree mstp msti 2 vlan 4002
Step3 Configure VLAN and port mode.
admin@SwitchC# set interface gigabit-ethernet te-1/1/7 family ethernet-switching port-mode trunk admin@SwitchC# set interface gigabit-ethernet te-1/1/7 family ethernet-switching vlan members 100-200,300-400,4001,4002 admin@SwitchC# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching port-mode trunk admin@SwitchC# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching vlan members 100-200,300-400,4001,4002
Step4 Enable ERPS function globally. By default, ERPS is disabled.
admin@SwitchC# set protocols erps enable true
Step5 Create the ERPS ring with a given ID.
admin@SwitchC# set protocols erps ring 1
Step6 Configure port0 and port1 of the ERPS ring.
admin@SwitchC# set protocols erps ring 1 port0 interface ge-1/1/5 admin@SwitchC# set protocols erps ring 1 port1 interface te-1/1/7
Step7 Create instance for the ERPS ring.
admin@SwitchC# set protocols erps ring 1 instance 1 admin@SwitchC# set protocols erps ring 1 instance 2
Step8 Configure port ge-1/1/5 (port0) on Switch C as the RPL Owner Node for ERPS ring 1 instance 2.
admin@SwitchC# set protocols erps ring 1 instance 2 rpl port0 owner
Step9 Configure the control VLAN.
admin@SwitchC# set protocols erps ring 1 instance 1 control-vlan 4001 admin@SwitchC# set protocols erps ring 1 instance 2 control-vlan 4002
Step10 Configure the MSTP instance of VLANs that are protected by this ring instance.
admin@SwitchC# set protocols erps ring 1 instance 1 protected-instance 1 admin@SwitchC# set protocols erps ring 1 instance 2 protected-instance 2
Step11 Commit the configurations.
admin@SwitchC# commit
Switch D
Step1 Disable spanning-tree protocol on the interface where you want to enable ERPS.
admin@SwitchD# set protocols spanning-tree interface te-1/1/7 enable false admin@SwitchD# set protocols spanning-tree interface te-1/1/19 enable false
Step2 Configure the protected MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.
NOTE: The ERPS control VLAN must be in one of the protected MSTP instance.
admin@SwitchD# set protocols spanning-tree mstp msti 1 vlan 100-200 admin@SwitchD# set protocols spanning-tree mstp msti 1 vlan 4001 admin@SwitchD# set protocols spanning-tree mstp msti 2 vlan 300-400 admin@SwitchD# set protocols spanning-tree mstp msti 2 vlan 4002
Step3 Configure VLAN and port mode.
admin@SwitchD# set interface gigabit-ethernet te-1/1/7 family ethernet-switching port-mode trunk admin@SwitchD# set interface gigabit-ethernet te-1/1/7 family ethernet-switching vlan members 100-200,300-400,4001,4002 admin@SwitchD# set interface gigabit-ethernet te-1/1/19 family ethernet-switching port-mode trunk admin@SwitchD# set interface gigabit-ethernet te-1/1/19 family ethernet-switching vlan members 100-200,300-400,4001,4002
Step4 Enable ERPS function globally. By default, ERPS is disabled.
admin@SwitchD# set protocols erps enable true
Step5 Create the ERPS ring with a given ID.
admin@SwitchD# set protocols erps ring 1
Step6 Configure port0 and port1 of the ERPS ring.
admin@SwitchD# set protocols erps ring 1 port0 interface te-1/1/7 admin@SwitchD# set protocols erps ring 1 port1 interface te-1/1/19
Step7 Create instance for the ERPS ring.
admin@SwitchD# set protocols erps ring 1 instance 1 admin@SwitchD# set protocols erps ring 1 instance 2
Step8 Configure port te-1/1/19 (port1) on Switch D as the RPL Neighbor port for ERPS ring 1 instance 1.
admin@SwitchD# set protocols erps ring 1 instance 1 rpl port1 neighbor
Step9 Configure the control VLAN.
admin@SwitchD# set protocols erps ring 1 instance 1 control-vlan 4001 admin@SwitchD# set protocols erps ring 1 instance 2 control-vlan 4002
Step10 Configure the MSTP instance of VLANs that are protected by this ring instance.
admin@SwitchD# set protocols erps ring 1 instance 1 protected-instance 1 admin@SwitchD# set protocols erps ring 1 instance 2 protected-instance 2
Step11 Commit the configurations.
admin@SwitchD# commit
Verifying the Configuration
- The command run show erps brief can be used to check the brief configuration information of the ERPS ring. Take Switch A as an example:
admin@SwitchA# run show erps brief Enable: true Version: 2 Tcn-propagation: No D: Discarding F: Forwarding R: RPL Owner N: RPL Neighbour FS: Forced Switch MS: Manual Switch Ring ID Instance ID Control VLAN Port0 Port1 ------------------------------------------------------------------------------ 1 1 4001 te-1/1/3(F) te-1/1/19 (D,R) 1 2 4002 te-1/1/3(F) te-1/1/19(F)
- The command run show erps ring <ring-id> can be used to check the detailed information of the ERPS ring. Take Switch A as an example:
admin@SwitchA# run show erps ring 1 Ring ID: 1 Port0: te-1/1/3 Port1: te-1/1/19 Ring-MAC: false Sub-ring: No Virtual-channel: No Instance ID: 1 Enable: Yes Active: true Node state: Idle Description: Control VLAN: 4001 Protected instance: 1 Protected VLAN: 100-200 Guard timer: 500 ms Hold-off timer: 0 ms WTR timer: 5 min Revertive mode: Revertive R-APS level : 7 Connect(ring/instance): - Forced Switch Port: - Manual Switch Port: - Interface Port Role Port State Signal Failure ------------------------------------------------------------------------------- te-1/1/3 Common Forwarding Non-failed te-1/1/19 RPL Owner Discarding Non-failed Instance ID: 2 Enable: Yes Active: true Node state: Idle Description: Control VLAN: 4002 Protected instance: 2 Protected VLAN: 300-400 Guard timer: 500 ms Hold-off timer: 0 ms WTR timer: 5 min Revertive mode: Revertive R-APS level : 7 Connect(ring/instance): - Forced Switch Port: - Manual Switch Port: - Interface Port Role Port State Signal Failure ----------------------------------------------------------------- te-1/1/3 Common Forwarding Non-failed te-1/1/19 Common Forwarding Non-failed
From the show result, we can see that port te-1/1/19 on Switch A is the Owner node in Instance 1, with the ERPS ring in the Idle state, the RPL owner port blocked, and the port state of the non-RPL owner port is forwarding.
In Instance 2, port0 and port1 are Normal nodes, the ERPS ring is in the Idle state, and the port state of the non-RPL owner ports are forwarding.
Copyright © 2024 Pica8 Inc. All Rights Reserved.