Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Networking Requirements

Figure 1.     ERPS Configuration Example

example intersect ring.png

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 1, taking the deployment of the interconnection ERPS ring as an example.

  • Switch A, Switch B, Switch C and Switch D form an ERPS major ring, ring ID is 1 and protected instance is 1; Switch B, Switch C and Switch E form a sub-ring, ring ID is 2 and protected instance is 2.

  • Configure the control VLAN ID of ERPS ring 1 to be 4001 and the control VLAN ID of ERPS ring 2 to be 4002. ERPS ring 1 and ring 2 transmit data packets for the same user VLAN 100 to 200.

  • Users wish to share the forwarding path between the intersecting rings for the data traffic, in such case, it is necessary to configure the control VLANs and data VLANs (VLAN 4001, 4002, 100 to 200) into the same protected instance to achieve data forwarding between the intersecting rings.

  • Configure network topology change notification on intersecting nodes Switch B and Switch C. The following configurations are required:

1. Configure the connect ring for a sub-ring on all intersecting nodes.

set protocols erps ring <ring-id> instance <instance-id> connect ring <ring-id> instance <instance-id>

2. Enable tcn-propagation function to advertise topology changes to the connect ring on all intersecting nodes.

NOTEs:

  • The ERPS port must be a trunk port and disable spanning tree protocol.

  • Different ERPS ring instances cannot use the same control VLAN.

  • The same control VLAN must be configured for all devices in the same ERPS ring instance.

Procedure

Switch A

Step 1          Disable spanning-tree protocol on the interface before configuring ERPS ring on the interface.

admin@SwitchA# set protocols spanning-tree interface te-1/1/1 enable false
admin@SwitchA# set protocols spanning-tree interface te-1/1/2 enable false

Step 2          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

Step 3          Configure VLAN and port mode.

admin@SwitchA# set interface gigabit-ethernet te-1/1/1 family ethernet-switching port-mode trunk
admin@SwitchA# set interface gigabit-ethernet te-1/1/1 family ethernet-switching vlan members 100-200,4001
admin@SwitchA# set interface gigabit-ethernet te-1/1/2 family ethernet-switching port-mode trunk
admin@SwitchA# set interface gigabit-ethernet te-1/1/2 family ethernet-switching vlan members 100-200,4001

Step 4          Enable ERPS function globally. By default, ERPS is disabled.

admin@SwitchA# set protocols erps enable true

Step 5          Create the ERPS ring with a given ID.

admin@SwitchA# set protocols erps ring 1

Step 6          Configure port0 and port1 of the ERPS ring.

admin@SwitchA# set protocols erps ring 1 port0 interface te-1/1/1
admin@SwitchA# set protocols erps ring 1 port1 interface te-1/1/2

Step 7          Create instance for the ERPS ring.

admin@SwitchA# set protocols erps ring 1 instance 1

Step 8          Configure port te-1/1/2 (port1) on Switch A as the RPL Owner Node for the ERPS ring 1 instance 1.

admin@SwitchA# set protocols erps ring 1 instance 1 rpl port1 owner

Step 9          Configure the control VLAN.

admin@SwitchA# set protocols erps ring 1 instance 1 control-vlan 4001

Step 10      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

Step 11      Commit the configurations.

admin@SwitchA# commit

Switch B

Step 1          Disable spanning-tree protocol on the interface before configuring ERPS ring on the interface.

admin@SwitchB# set protocols spanning-tree interface te-1/1/1 enable false
admin@SwitchB# set protocols spanning-tree interface te-1/1/4 enable false
admin@SwitchB# set protocols spanning-tree interface te-1/1/5 enable false

Step 2          Configure protected MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.

NOTE: Configure the control VLAN and data VLAN of ring 1 and ring 2 (VLAN 4001, 4002, 100 to 200) into the same protected instance to achieve data forwarding between the intersecting rings.

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 1 vlan 4002

Step 3          Configure VLAN and port mode.

admin@SwitchB# set interface gigabit-ethernet te-1/1/1 family ethernet-switching port-mode trunk
admin@SwitchB# set interface gigabit-ethernet te-1/1/1 family ethernet-switching vlan members 100-200,4001
admin@SwitchB# set interface gigabit-ethernet te-1/1/4 family ethernet-switching port-mode trunk
admin@SwitchB# set interface gigabit-ethernet te-1/1/4 family ethernet-switching vlan members 100-200,4001
admin@SwitchB# set interface gigabit-ethernet te-1/1/5 family ethernet-switching port-mode trunk
admin@SwitchB# set interface gigabit-ethernet te-1/1/5 family ethernet-switching vlan members 100-200,4002

Step 4          Enable ERPS function globally. By default, ERPS is disabled.

admin@SwitchB# set protocols erps enable true

Step 5          Create the ERPS ring 1 and 2, and specify ring 2 as a sub-ring.

admin@SwitchB# set protocols erps ring 1
admin@SwitchB# set protocols erps ring 2 sub-ring true

Step 6          Configure port0 and port1 of the ERPS ring.

admin@SwitchB# set protocols erps ring 1 port0 interface te-1/1/1
admin@SwitchB# set protocols erps ring 1 port1 interface te-1/1/4
admin@SwitchB# set protocols erps ring 2 port0 interface te-1/1/5

Step 7          Configure port te-1/1/5 (port0) on Switch B as the RPL Owner Node for the ERPS ring 2 instance 2.

admin@SwitchB# set protocols erps ring 2 instance 2 rpl port0 owner

Step 8          Create instance for the ERPS ring.

admin@SwitchB# set protocols erps ring 1 instance 1
admin@SwitchB# set protocols erps ring 2 instance 2

Step 9          Configure the control VLAN.

admin@SwitchB# set protocols erps ring 1 instance 1 control-vlan 4001
admin@SwitchB# set protocols erps ring 2 instance 2 control-vlan 4002

Step 10      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 2 instance 2 protected-instance 1

Step 11      Configure the connect ring for sub-ring 2, and enable network topology change notification on intersecting nodes Switch B and Switch C.

admin@SwitchB# set protocols erps ring 2 instance 2 connect ring 1 instance 1
admin@SwitchB# set protocols erps tcn-propagation true

Step 12      Commit the configurations.

admin@SwitchB# commit

Switch C

Step 1          Disable spanning-tree protocol on the interface before configuring ERPS ring on the interface.

admin@SwitchC# set protocols spanning-tree interface te-1/1/3 enable false
admin@SwitchC# set protocols spanning-tree interface te-1/1/4 enable false
admin@SwitchC# set protocols spanning-tree interface te-1/1/6 enable false

Step 2          Configure MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.

NOTE: Configure the control VLAN and data VLAN of ring 1 and ring 2 (VLAN 4001, 4002, 100 to 200) into the same protected instance to enable data forwarding between the intersecting rings.

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 1 vlan 4002

Step 3          Configure VLAN and port mode.

admin@SwitchC# set interface gigabit-ethernet te-1/1/3 family ethernet-switching port-mode trunk
admin@SwitchC# set interface gigabit-ethernet te-1/1/3 family ethernet-switching vlan members 100-200,4001
admin@SwitchC# set interface gigabit-ethernet te-1/1/4 family ethernet-switching port-mode trunk
admin@SwitchC# set interface gigabit-ethernet te-1/1/4 family ethernet-switching vlan members 100-200,4001
admin@SwitchC# set interface gigabit-ethernet te-1/1/6 family ethernet-switching port-mode trunk
admin@SwitchC# set interface gigabit-ethernet te-1/1/6 family ethernet-switching vlan members 100-200,4002

Step 4          Enable ERPS function globally. By default, ERPS is disabled.

admin@SwitchC# set protocols erps enable true

Step 5          Create the ERPS ring with a given ID.

admin@SwitchC# set protocols erps ring 1
admin@SwitchC# set protocols erps ring 2 sub-ring true

Step 6          Configure port0 and port1 of the ERPS ring.

admin@SwitchC# set protocols erps ring 1 port0 interface te-1/1/3
admin@SwitchC# set protocols erps ring 1 port1 interface te-1/1/4
admin@SwitchC# set protocols erps ring 2 port0 interface te-1/1/6

Step 7          Create instance for the ERPS ring.

admin@SwitchC# set protocols erps ring 1 instance 1
admin@SwitchC# set protocols erps ring 2 instance 2

Step 8          Configure the control VLAN.

admin@SwitchC# set protocols erps ring 1 instance 1 control-vlan 4001
admin@SwitchC# set protocols erps ring 2 instance 2 control-vlan 4002

Step 9          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 2 instance 2 protected-instance 1

Step 10      Configure the connect ring for sub-ring 2, and enable network topology change notification on intersecting nodes Switch B and Switch C.

admin@SwitchC# set protocols erps ring 2 instance 2 connect ring 1 instance 1
admin@SwitchC# set protocols erps tcn-propagation true

Step 11      Commit the configurations.

admin@SwitchC# commit

Switch D

Step 1          Disable spanning-tree protocol on the interface before configuring ERPS ring on the interface.

admin@SwitchD# set protocols spanning-tree interface te-1/1/2 enable false
admin@SwitchD# set protocols spanning-tree interface te-1/1/3 enable false

Step 2          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

Step 3          Configure VLAN and port mode.

admin@SwitchD# set interface gigabit-ethernet te-1/1/2 family ethernet-switching port-mode trunk
admin@SwitchD# set interface gigabit-ethernet te-1/1/2 family ethernet-switching vlan members 100-200,4001
admin@SwitchD# set interface gigabit-ethernet te-1/1/3 family ethernet-switching port-mode trunk
admin@SwitchD# set interface gigabit-ethernet te-1/1/3 family ethernet-switching vlan members 100-200,4001

Step 4          Enable ERPS function globally. By default, ERPS is disabled.

admin@SwitchD# set protocols erps enable true

Step 5          Create the ERPS ring with a given ID.

admin@SwitchD# set protocols erps ring 1

Step 6          Configure port0 and port1 of the ERPS ring.

admin@SwitchD# set protocols erps ring 1 port0 interface te-1/1/2
admin@SwitchD# set protocols erps ring 1 port1 interface te-1/1/3

Step 7          Create instance for the ERPS ring.

admin@SwitchD# set protocols erps ring 1 instance 1

Step 8          Configure port te-1/1/2 (port0) on Switch D as the RPL Neighbor port for the ERPS ring 1 instance 1.

admin@SwitchD# set protocols erps ring 1 instance 1 rpl port0 neighbor

Step 9          Configure the control VLAN.

admin@SwitchD# set protocols erps ring 1 instance 1 control-vlan 4001

Step 10      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

Step 11      Commit the configurations.

admin@SwitchD# commit

Switch E

Step 1          Disable spanning-tree protocol on the interface before configuring ERPS ring on the interface.

admin@SwitchE# set protocols spanning-tree interface te-1/1/5 enable false
admin@SwitchE# set protocols spanning-tree interface te-1/1/6 enable false

Step 2          Configure the protected MSTP instance (ERPS protected-instance) and VLAN mapping before configuring ERPS.

admin@SwitchE# set protocols spanning-tree mstp msti 1 vlan 100-200
admin@SwitchE# set protocols spanning-tree mstp msti 1 vlan 4002

Step 3          Configure VLAN and port mode.

admin@SwitchE# set interface gigabit-ethernet te-1/1/5 family ethernet-switching port-mode trunk
admin@SwitchE# set interface gigabit-ethernet te-1/1/5 family ethernet-switching vlan members 100-200,4002
admin@SwitchE# set interface gigabit-ethernet te-1/1/6 family ethernet-switching port-mode trunk
admin@SwitchE# set interface gigabit-ethernet te-1/1/6 family ethernet-switching vlan members 100-200,4002

Step 4          Enable ERPS function globally. By default, ERPS is disabled.

admin@SwitchE# set protocols erps enable true

Step 5          Create the ERPS ring with a given ID.

admin@SwitchE# set protocols erps ring 2 sub-ring true

Step 6          Configure port0 and port1 of the ERPS ring.

admin@SwitchE# set protocols erps ring 2 port0 interface te-1/1/5
admin@SwitchE# set protocols erps ring 2 port1 interface te-1/1/6

Step 7          Create instance for the ERPS ring.

admin@SwitchE# set protocols erps ring 2 instance 2

Step 8          Configure port te-1/1/5 (port0) on Switch D as the RPL Neighbor port for the ERPS ring 2 instance 2.

admin@SwitchE# set protocols erps ring 2 instance 2 rpl port0 neighbor

Step 9          Configure the control VLAN.

admin@SwitchE# set protocols erps ring 2 instance 2 control-vlan 4002

Step 10      Configure the MSTP instance of VLANs that are protected by this ring instance.

admin@SwitchE# set protocols erps ring 2 instance 2 protected-instance 1

Step 11      Commit the configurations.

admin@SwitchE# 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 and Switch B 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/1(F)     te-1/1/2 (D,R)


admin@SwitchB# run show erps brief
Enable: Yes
Version: 2
Tcn-propagation: Yes

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/1(F)         te-1/1/4 (D,R)
2               2                 4002             te-1/1/5(D,R)       -
  • 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/1
Port1: te-1/1/2
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/1       Common          Forwarding     Non-failed
te-1/1/2       RPL Owner       Discarding     Non-failed

From the show result, we can see that port te-1/1/2 on Switch A is the Owner node in Instance 1, with the ERPS ring in the Idle state, the RPL port blocked, and the non-RPL port state is forwarding.

  • No labels