16-RRPP Configuration
Chapters Download (1.06 MB)
Table of Contents
Displaying and Maintaining RRPP
Single Ring Configuration Example
Intersecting Ring Configuration Example
Intersecting-Ring Load Balancing Configuration Example
When configuring RRPP, go to these sections for information you are interested in:
l RRPP Configuration Task List
l Displaying and Maintaining RRPP
The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy, and rapidly restore the communication paths between the nodes in the event that a link is disconnected on the ring.
Compared with the IEEE spanning tree protocols, RRPP features the following:
l Fast topology convergence
l Convergence time independent of Ethernet ring size
The Gigabit uplink ports of the H3C S3600 series EPON OLT switches support the RRPP protocol. By connecting these uplink ports to RRPP rings, you can improve the uplink reliability of the S3600 EPON OLT switches.
Currently, both Spanning Tree Protocol (STP) and RRPP can be used to eliminate Layer-2 loops. STP is mature; however, it takes several seconds to converge. RRPP is an Ethernet ring-specific data link layer protocol, and converges faster than STP. Additionally, the convergence time of RRPP is independent of the number of nodes in the Ethernet ring, and therefore, RRPP can be applied to large-diameter networks.
Figure 1-1 RRPP networking diagram
The interconnected devices with the same domain ID and control VLANs constitute an RRPP domain. An RRPP domain contains the following elements: primary ring, subring, control VLAN, master node, transit node, primary port, secondary port, common port, and edge port.
As shown in Figure 1-1, Domain 1 is an RRPP domain, including two RRPP rings: Ring 1 and Ring 2. All the nodes on the two RRPP rings belong to the RRPP domain.
A ring-shaped Ethernet topology is called an RRPP ring. RRPP rings fall into two types: primary ring and subring. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, while a subring is of level 1. An RRPP domain contains multiple RRPP rings, one serving as the primary ring and the others serving as subrings. As shown in Figure 1-1, Domain 1 contains two RRPP rings: Ring 1 and Ring 2. The level of Ring 1 is set to 0, that is, Ring 1 is configured as the primary ring; the level of Ring 2 is set to 1, that is, Ring 2 is configured as a subring.
A ring can be in one of the following two states:
l Health state: All the physical links on the Ethernet ring are connected.
l Disconnect state: Some physical links on the Ethernet ring are broken.
Each S3600 EPON OLT switch has only two Gigabit uplink combo ports that support RRPP. Because the ports are few, when configuring RRPP on an S3600 EPON OLT switch, you can configure only one RRPP ring in an RRPP domain.
1) Control VLAN
In an RRPP domain, a control VLAN is a VLAN dedicated to transferring RRPPDUs. On a device, the ports accessing an RRPP ring belong to the control VLANs of the ring, and only such ports can join the control VLANs.
An RRPP domain is configured with two control VLANs: one primary control VLAN, which is the control VLAN for the primary ring; one secondary control VLAN, which is the control VLAN for subrings. All subrings in the same RRPP domain share the same secondary control VLAN. After you specify a VLAN as the primary control VLAN, the system automatically configures the VLAN whose ID is the primary control VLAN ID plus one as the secondary control VLAN.
IP address configuration is prohibited on the control VLAN interfaces.
2) Data VLAN
A data VLAN is a VLAN dedicated to transferring data packets. Both RRPP ports and non-RRPP ports can be assigned to a data VLAN.
Each device on an RRPP ring is referred to as a node. The role of a node is configurable. There are the following node roles:
l Master node: Each ring has one and only one master node. The master node initiates the polling mechanism and determines the operations to be performed after a change in topology.
l Transit node: Transit nodes include all the nodes except the master node on the primary ring and all the nodes on subrings except the master nodes and the nodes where the primary ring intersects with the subrings. A transit node monitors the state of its directly-connected RRPP links and notifies the master node of the link state changes, if any. Based on the link state changes, the master node decides the operations to be performed.
l Edge node: A node residing on both the primary ring and a subring at the same time. An edge node is a special transit node that serves as a transit node on the primary ring and an edge node on the subring.
l Assistant-edge node: A node residing on both the primary ring and a subring at the same time. An assistant-edge node is a special transit node that serves as a transit node on the primary ring and an assistant-edge node on the subring. This node works in conjunction with the edge node to detect the integrity of the primary ring and perform loop guard.
As shown in Figure 1-1, Ring 1 is the primary ring and Ring 2 is a subring. Device A is the master node of Ring 1, Device B, Device C and Device D are the transit nodes of Ring 1. Device E is the master node of Ring 2, Device B is the edge node of Ring 2, and Device C is the assistant-edge node of Ring 2.
Because each S3600 EPON OLT switch has only two Gigabit uplink combo ports that support RRPP, you cannot configure an S3600 EPON OLT switch as an edge node or assistant-edge node of an RRPP ring. When configuring edge nodes or assistant-edge nodes of RRPP rings, select H3C switches of other series.
Each master node or transit node has two ports connected to an RRPP ring, one serving as the primary port and the other serving as the secondary port. You can determine the role of a port.
1) In terms of functionality, the difference between the primary port and the secondary port of a master node is:
l The primary port and the secondary port are designed to play the role of sending and receiving loop-detect packets respectively.
l When an RRPP ring is in Health state, the secondary port of the master node will logically deny data VLANs and permit only the packets of the control VLANs.
l When an RRPP ring is in Disconnect state, the secondary port of the master node will permit data VLANs, that is, forward packets of data VLANs.
2) In terms of functionality, there is no difference between the primary port and the secondary port of a transit node. Both are designed for transferring protocol packets and data packets over an RRPP ring.
As shown in Figure 1-1, Device A is the master node of Ring 1. Port 1 and Port 2 are the primary port and the secondary port of the master node on Ring 1 respectively. Device B, Device C, and Device D are the transit nodes of Ring 1. Their Port 1 and Port 2 are the primary port and the secondary port on Ring 1 respectively.
The ports connecting the edge node and assistant-edge node to the primary ring are common ports. The ports connecting the edge node and assistant-edge node only to the subrings are edge ports.
As shown in Figure 1-1, Device B and Device C lie on Ring 1 and Ring 2. Device B’s Port 1 and Port 2 and Device C’s Port 1 and Port 2 access the primary ring, so they are common ports. Device B’s Port 3 and Device C’s Port 3 access only the subring, so they are edge ports.
Because S3600 EPON OLT switches cannot be configured as edge nodes or assistant-edge nodes of RRPP rings, the ports of S3600 EPON OLT switches on RRPP rings cannot operate as common ports or edge ports.
Table 1-1 shows the types of RRPPDUs and their functions.
Table 1-1 RRPPDU types and their functions
|
Type |
Description |
|
Hello |
The master node initiates Hello packets to detect the integrity of a ring in a network. |
|
Link-Down |
The transit node, the edge node or the assistant-edge node initiates Link-Down packets to notify the master node of the disappearance of a ring in case of a link failure. |
|
Common-Flush-FDB |
The master node initiates Common-Flush-FDB packets to instruct the transit nodes to update their own MAC entries and ARP/ND entries when an RRPP ring transits to Disconnect state. |
|
Complete-Flush-FDB |
The master node initiates Complete-Flush-FDB packets to instruct the transit nodes to update their own MAC entries and ARP/ND entries, and release blocked ports from being blocked temporarily when an RRPP ring transits to Health state. |
|
Edge-Hello |
The edge node initiates Edge-Hello packets to examine the SRPTs between the edge node and the assistant-edge node. |
|
Major-Fault |
The assistant-edge node initiates Major-Fault packets to notify the edge node of SRPT failure when an SRPT between edge node and assistant-edge node is torn down. |
When RRPP checks the link state of an Ethernet ring, the master node sends Hello packets out the primary port according to the Hello timer and determines whether its secondary port receives the Hello packets based on the Fail timer.
l The Hello timer specifies the interval at which the master node sends Hello packets out the primary port.
l The Fail timer specifies the maximum delay between the master node sending Hello packets out the primary port and the secondary port receiving the Hello packets from the primary port. If the secondary port receives the Hello packets sent by the local master node before the Fail timer expires, the overall ring is in Health state. Otherwise, the ring transits into Disconnect state.
In an RRPP domain, a transit node learns the Hello timer value and the Fail timer value on the master node through the received Hello packets, ensuring that all nodes in the ring network are consistent in the two timer settings.
The polling mechanism is used by the master node of an RRPP ring to check the Health state of the ring network.
The master node sends Hello packets out its primary port periodically, and these Hello packets travel through each transit node on the ring in turn.
l If the ring is complete, the secondary port of the master node will receive Hello packets before the Fail timer expires and the master node will keep the secondary port blocked.
l If the ring is torn down, the secondary port of the master node will fail to receive Hello packets before the Fail timer expires. The master node will release the secondary port from blocking data VLANs while sending Common-Flush-FDB packets to instruct all transit nodes to update their own MAC entries and ARP/ND entries.
The transit node, the edge node or the assistant-edge node sends Link-Down packets to the master node immediately when they find any of its own ports belonging to an RRPP domain is down. Upon the receipt of a Link-Down packet, the master node releases the secondary port from blocking data VLANs while sending Common-Flush-FDB packet to instruct all the transit nodes, the edge nodes and the assistant-edge nodes to update their own MAC entries and ARP/ND entries. After each node updates its own entries, traffic is switched to the normal link.
The master node may find the ring is restored after a period of time after the ports belonging to the RRPP domain on the transit nodes, the edge nodes, or the assistant-edge nodes are brought up again. A temporary loop may arise in the data VLAN during this period. As a result, broadcast storm occurs.
To prevent temporary loops, non-master nodes block them immediately (and permit only the packets of the control VLAN to pass through) when they find their ports accessing the ring are brought up again. The blocked ports are activated only when the nodes are sure that no loop will be brought forth by these ports.
As shown in Figure 1-5, Ring 1 is the primary ring, and Ring 2 and Ring 3 are subrings. When the two SRPTs between the edge node and the assistant-edge node are down, the master nodes of Ring 2 and Ring 3 will open their respective secondary ports, and thus a loop among Device B, Device C, Device E, and Device F is generated. As a result, broadcast storm occurs.
In this case, to prevent generating this loop, the edge node will block the edge port temporarily. The blocked edge port is activated only when the edge node is sure that no loop will be brought forth when the edge port is activated.
In a ring network, maybe traffic of multiple VLANs is transmitted at the same time. RRPP can implement load balancing for the traffic by transmitting traffic of different VLANs along different paths.
By configuring an individual RRPP domain for transmitting the traffic of the specified VLANs (referred to as protected VLANs) in a ring network, traffic of different VLANs can be transmitted according to different topologies in the ring network. In this way, load balancing is achieved.
As shown in Figure 1-6, Ring 1 is configured as the primary ring of Domain 1 and Domain 2, which are configured with different protected VLANs. Device A is the master node of Ring 1 in Domain 1; Device B is the master node of Ring 1 in Domain 2. With such configurations, traffic of different VLANs can be transmitted on different links, and thus, load balancing is achieved in a single-ring network.
Here are several typical networking applications.
As shown in Figure 1-2, there is only a single ring in the network topology. In this case, you only need to define an RRPP domain.
Figure 1-2 Schematic diagram for a single-ring network
As shown in Figure 1-3, there are two or more rings in the network topology and only one common node between rings. In this case, you need to define an RRPP domain for each ring.
Figure 1-3 Schematic diagram for a tangent-ring network
As shown in Figure 1-4, there are two or more rings in the network topology and two common nodes between rings. In this case, you only need to define an RRPP domain, and configure one ring as the primary ring and the other rings as subrings.
Figure 1-4 Schematic diagram for an intersecting-ring network
As shown in Figure 1-5, there are two or more rings in the network topology and two similar common nodes between rings. In this case, you only need to define an RRPP domain, and configure one ring as the primary ring and the other rings as subrings.
Figure 1-5 Schematic diagram for a dual-homed-ring network
In a single-ring network, you can achieve load balancing by configuring multiple domains.
As shown in Figure 1-6, Ring 1 is configured as the primary ring of both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with different protected VLANs. In Domain 1, Device A is configured as the master node of Ring 1; in Domain 2, Device B is configured as the master node of Ring 1. Such configurations enable the ring to block different links based on VLANs. Thus, single-ring load balancing is achieved.
Figure 1-6 Schematic diagram for a single-ring load balancing network
As shown in Figure 1-7, Ring 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with different protected VLANs. Device A is configured as the master node of Ring 1 in Domain 1; Device D is configured as the master node of Ring 1 in Domain 2. Device E is configured as the master node of Ring 2 in both Domain 1 and Domain 2. However, different ports on Device E are blocked in Domain 1 and Domain 2. With the configurations, you can enable traffic of different VLANs to travel over different paths in the subring and primary ring, thus achieving intersecting-ring load balancing.
Figure 1-7 Schematic diagram for an intersecting-ring load balancing network
RFC 3619 Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1 is related to RRPP.
You need to design RRPP networks based on your service planning, determine the roles of devices on the RRPP networks, and make the following configurations based on your RRPP network designs.
Complete the following tasks to configure RRPP:
|
Task |
Remarks |
|
|
Required Perform this task on all nodes in the RRPP domain. |
||
|
Required Perform this task on all nodes in the RRPP domain. |
||
|
Required Perform this task on all nodes in the RRPP domain. |
||
|
Required Perform this task on all nodes in the RRPP domain. |
||
|
Required Perform this task on all nodes in the RRPP domain |
||
|
Required Perform this task on all nodes in the RRPP domain. |
||
|
Optional Perform this task on the master node in the RRPP domain. |
||
l RRPP does not have an auto election mechanism, so you must configure each node in the ring network properly for RRPP to monitor and protect the ring network.
l Before configuring RRPP, you need to construct a ring-shaped Ethernet topology physically.
l Follow this order when configuring RRPP: create an RRPP domain; configure the control VLANs and protected VLANs in the RRPP domain; configure the role of each ring in the RRPP domain and the role of each node on the rings; activate the RRPP domain.
When creating an RRPP domain, specify a domain ID, which uniquely identifies an RRPP domain. All devices in the same RRPP domain must be configured with the same domain ID.
Make this configuration on devices you want to configure as nodes in the RRPP domain.
Follow these steps to create an RRPP domain:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Create an RRPP domain and enter RRPP domain view |
rrpp domain domain-id |
Required |
Before configuring RRPP rings in an RRPP domain, configure the same control VLANs for all nodes in the RRPP domain first.
Perform this configuration on all nodes in the RRPP domain to be configured.
Follow these steps to configure control VLANs:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Specify the primary control VLAN for the RRPP domain |
control-vlan vlan-id |
Required |
l To ensure proper forwarding of RRPPDUs, do not enable QinQ or VLAN mapping on the control VLANs.
l To ensure that RRPPDUs can be sent and received correctly, do not configure the default VLAN of a port accessing an RRPP ring as the primary control VLAN or the secondary control VLAN.
l To transparently transmit RRPPDUs on a device not configured with RRPP, you must ensure only the two ports connecting the device to the RRPP ring permit the packets of the control VLANs. Otherwise, the packets from other VLANs may go into the control VLANs in transparent transmission mode and strike the RRPP ring.
Before configuring RRPP rings in an RRPP domain, configure the same protected VLANs for all nodes in the RRPP domain first. All VLANs that the RRPP ports are assigned to should be protected by the RRPP domains.
Perform this configuration on all nodes in the RRPP domain to be configured.
Follow these steps to configure protected VLANs:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Configure protected VLANs for the RRPP domain |
protected-vlan reference-instance instance-id-list |
Required By default, no protected VLAN is configured for an RRPP domain. |
When configuring load balancing, ensure that the protected VLANs configured for different RRPP domains are different.
The protected VLANs are specified by the MSTIs. You can use the display stp region-configuration command to check the VLANs corresponding to the specified MSTIs. For details, please refer to “MSTP Configuration”.
Before configuring rings for an RRPP domain, you can delete or modify the protected VLANs configured for the RRPP domain; after configuring rings for an RRPP domain, you can delete or modify the protected VLANs configured for the RRPP domain, however, you cannot delete all the protected VLANs configured for the domain.
When configuring an RRPP ring, you must make some configurations on the ports connecting each node to the RRPP ring before configuring the nodes.
l Each S3600 EPON OLT switch has only two Gigabit uplink combo ports that support RRPP. The ONU ports and OLT ports do not support RRPP.
l The link type of an RRPP port, that is, a port that connects a device to an RRPP ring, must be set to trunk and the RRPP port must allow packets of the protected VLANs of the current RRPP domain to pass through.
l RRPP ports cannot be Layer-2 aggregate interfaces, or member ports of any aggregation group, service loopback group, or smart link group.
l STP must be disabled on RRPP ports.
l You are recommended not to configure physical-link-state change suppression time on an RRPP port. This is to accelerate topology convergence. For details, refer to Port Configuration in this manual.
Perform this configuration on each node’s ports intended for accessing RRPP rings.
Follow these steps to configure RRPP ports:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet port view |
interface interface-type interface-number |
— |
|
Configure the link type of the Ethernet port as trunk |
port link-type trunk |
Required By default, the link type of an Ethernet port is access. |
|
Configure the port to allow packets of the protected VLANs of the current RRPP domain to pass through |
port trunk permit vlan { vlan-id-list | all } |
Required By default, a port only allows packets of its default VLAN to pass through. |
|
Disable STP |
undo stp enable |
Required Enabled by default |
l For detailed information about the port link-type trunk and port trunk permit command, refer to VLAN Commands in this manual.
l For detailed information about the undo stp enable command, refer to MSTP Commands in this manual.
l When configuring RRPP on an S3600 EPON OLT switch, you can configure only one RRPP ring in an RRPP domain. Hence, you cannot configure an S3600 EPON OLT switch as an edge node or assistant-edge node of an RRPP ring. When configuring edge nodes or assistant-edge nodes of RRPP rings, select H3C switches of other series.
l The node mode, RRPP port role, and ring level settings of an RRPP ring cannot be modified once they are configured. To modify the settings, you must first remove the present settings.
Perform this configuration on a device to be configured as a master node.
Follow these steps to specify a master node:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Specify the current device as the master node of the ring, and specify the primary port and the secondary port |
ring ring-id node-mode master [ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value |
Required |
Perform this configuration on a device to be configured as a transit node.
Follow these steps to specify a transit node:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Specify the current device as a transit node of the ring, and specify the primary port and the secondary port |
ring ring-id node-mode transit [ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value |
Required |
To activate an RRPP domain on the current device, enable the RRPP rings and RRPP protocol for the RRPP domain on the current device.
Perform this operation on all nodes in the RRPP domain.
Follow these steps to activate an RRPP domain:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Enable the specified RRPP ring |
ring ring-id enable |
Required Disabled by default |
|
Enter system view |
quit |
— |
|
Enable RRPP |
rrpp enable |
Required Disabled by default |
On an edge node or assistant-edge node, enable/disable the primary ring and subrings separately as follows:
l Enable the primary ring of an RRPP domain before enabling subrings of the RRPP domain.
l Disable the primary ring of an RRPP domain after disabling all subrings of the RRPP domain.
Perform this configuration on the master node of an RRPP domain.
Follow these steps to configure RRPP timers:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter RRPP domain view |
rrpp domain domain-id |
— |
|
Configure the Hello timer and Fail timer for the RRPP domain |
timer hello-timer hello-value fail-timer fail-value |
Required By default, the Hello timer value is 1 second and the Fail timer value is 3 seconds. |
l The Fail timer value must be equal to or greater than three times the Hello timer value.
l To avoid temporary loops when the primary ring fails in a dual-homed-ring network, ensure that the difference between the Fail timer value on the master node of the subring and that on the master node of the primary ring is greater than twice the Hello timer value of the master node of the subring.
|
To do… |
Use the command… |
Remarks |
|
Display brief RRPP information |
display rrpp brief |
Available in any view |
|
Display detailed RRPP information |
display rrpp verbose domain domain-id [ ring ring-id ] |
|
|
Display RRPP statistics |
display rrpp statistics domain domain-id [ ring ring-id ] |
|
|
Clear RRPP statistics |
reset rrpp statistics domain domain-id [ ring ring-id ] |
Available in user view |
l Device A, Device B, Device C, and Device D constitute RRPP domain 1, specify the primary control VLAN of RRPP domain 1 as VLAN 4092, and RPPP domain 1 protects all VLANs;
l Device A, Device B, Device C and Device D constitute primary ring 1;
l Specify Device A as the master node of primary ring 1, GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port;
l Specify Device B, Device C and Device D as the transit nodes of primary ring 1, their GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port;
Figure 1-8 Network diagram for single ring configuration
1) Configuration on Device A
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
<DeviceA> system-view
[DeviceA] interface gigabitethernet 1/1/1
[DeviceA-GigabitEthernet1/1/1] link-delay 0
[DeviceA-GigabitEthernet1/1/1] undo stp enable
[DeviceA-GigabitEthernet1/1/1] port link-type trunk
[DeviceA-GigabitEthernet1/1/1] port trunk permit vlan all
[DeviceA-GigabitEthernet1/1/1] quit
[DeviceA] interface gigabitethernet 1/1/3
[DeviceA-GigabitEthernet1/1/3] link-delay 0
[DeviceA-GigabitEthernet1/1/3] undo stp enable
[DeviceA-GigabitEthernet1/1/3] port link-type trunk
[DeviceA-GigabitEthernet1/1/3] port trunk permit vlan all
[DeviceA-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 15 as the protected VLANs of RRPP domain 1.
[DeviceA] rrpp domain 1
[DeviceA-rrpp-domain1] control-vlan 4092
[DeviceA-rrpp-domain1] protected-vlan reference-instance 0 to 15
# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceA-rrpp-domain1] ring 1 enable
[DeviceA-rrpp-domain1] quit
# Enable RRPP.
[DeviceA] rrpp enable
2) Configuration on Device B
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
<DeviceB> system-view
[DeviceB] interface gigabitethernet 1/1/1
[DeviceB-GigabitEthernet1/1/1] link-delay 0
[DeviceB-GigabitEthernet1/1/1] undo stp enable
[DeviceB-GigabitEthernet1/1/1] port link-type trunk
[DeviceB-GigabitEthernet1/1/1] port trunk permit vlan all
[DeviceB-GigabitEthernet1/1/1] quit
[DeviceB] interface gigabitethernet 1/1/3
[DeviceB-GigabitEthernet1/1/3] link-delay 0
[DeviceB-GigabitEthernet1/1/3] undo stp enable
[DeviceB-GigabitEthernet1/1/3] port link-type trunk
[DeviceB-GigabitEthernet1/1/3] port trunk permit vlan all
[DeviceB-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 15 as the protected VLANs of RRPP domain 1.
[DeviceB] rrpp domain 1
[DeviceB-rrpp-domain1] control-vlan 4092
[DeviceB-rrpp-domain1] protected-vlan reference-instance 0 to 15
# Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceB-rrpp-domain1] ring 1 enable
[DeviceB-rrpp-domain1] quit
# Enable RRPP.
[DeviceB] rrpp enable
3) Configuration on Device C
The configuration on Device C is similar to that on Device B and thus omitted here.
4) Configuration on Device D
The configuration on Device C is similar to that on Device B and thus omitted here.
After the above configuration, you can use the display command to view RRPP configuration and operational information on each device.
l Because each S3600 EPON OLT switch has only two Gigabit uplink combo ports that support RRPP, you cannot configure an S3600 EPON OLT switch as an edge node or assistant-edge node of an RRPP ring. When configuring edge nodes or assistant-edge nodes of RRPP rings, select H3C switches of other series. For detailed configurations, refer to the manuals delivered with the selected switches.
l On the network shown in Figure 1-9, Device A, Device D, and Device E can be S3600 EPON OLT switches.
As shown in Figure 1-9,
l Device A, Device B, Device C, Device D, and Device E constitute RRPP domain 1, VLAN 4092 is the primary control VLAN of RRPP domain 1, and RRPP domain 1 protects all the VLANs;
l Device A, Device B, Device C and Device D constitute primary ring 1, and Device B, Device C and Device E constitute subring 2;
l Device A is the master node of primary ring 1, GigabitEthernet 1/1/1 is the primary port and GigabitEthernet 1/1/3 is the secondary port;
l Device D is the transit node of primary ring 1, GigabitEthernet 1/1/1 is the primary port and GigabitEthernet 1/1/3 is the secondary port.
l Device E is the master node of subring 2, GigabitEthernet 1/1/1 is the primary port and GigabitEthernet 1/1/3 is the secondary port;
l Device B is the transit node of primary ring 1 and the edge node of subring 2;
l Device C is the transit node of primary ring 1 and the assistant-edge node of subring 1;
Figure 1-9 Network diagram for intersecting rings configuration
1) Configuration on Device A
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
<DeviceA> system-view
[DeviceA] interface gigabitethernet 1/1/1
[DeviceA-GigabitEthernet1/1/1] link-delay 0
[DeviceA-GigabitEthernet1/1/1] undo stp enable
[DeviceA-GigabitEthernet1/1/1] port link-type trunk
[DeviceA-GigabitEthernet1/1/1] port trunk permit vlan all
[DeviceA-GigabitEthernet1/1/1] quit
[DeviceA] interface gigabitethernet 1/1/3
[DeviceA-GigabitEthernet1/1/3] link-delay 0
[DeviceA-GigabitEthernet1/1/3] undo stp enable
[DeviceA-GigabitEthernet1/1/3] port link-type trunk
[DeviceA-GigabitEthernet1/1/3] port trunk permit vlan all
[DeviceA-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 15 as the protected VLANs of RRPP domain 1.
[DeviceA] rrpp domain 1
[DeviceA-rrpp-domain1] control-vlan 4092
[DeviceA-rrpp-domain1] protected-vlan reference-instance 0 to 15
# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceA-rrpp-domain1] ring 1 enable
[DeviceA-rrpp-domain1] quit
# Enable RRPP.
[DeviceA] rrpp enable
2) Configuration on Device D
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
<DeviceD> system-view
[DeviceD] interface gigabitethernet 1/1/1
[DeviceD-GigabitEthernet1/1/1] link-delay 0
[DeviceD-GigabitEthernet1/1/1] undo stp enable
[DeviceD-GigabitEthernet1/1/1] port link-type trunk
[DeviceD-GigabitEthernet1/1/1] port trunk permit vlan all
[DeviceD-GigabitEthernet1/1/1] quit
[DeviceD] interface gigabitethernet 1/1/3
[DeviceD-GigabitEthernet1/1/3] link-delay 0
[DeviceD-GigabitEthernet1/1/3] undo stp enable
[DeviceD-GigabitEthernet1/1/3] port link-type trunk
[DeviceD-GigabitEthernet1/1/3] port trunk permit vlan all
[DeviceD-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 15 as the protected VLANs of RRPP domain 1.
[DeviceD] rrpp domain 1
[DeviceD-rrpp-domain1] control-vlan 4092
[DeviceD-rrpp-domain1] protected-vlan reference-instance 0 to 15
# Configure Device D as the transit node of primary ring 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceD-rrpp-domain1] ring 1 enable
[DeviceD-rrpp-domain1] quit
# Enable RRPP.
[DeviceD] rrpp enable
3) Configuration on Device E
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
<DeviceE> system-view
[DeviceE] interface gigabitethernet 1/1/1
[DeviceE-GigabitEthernet1/1/1] link-delay 0
[DeviceE-GigabitEthernet1/1/1] undo stp enable
[DeviceE-GigabitEthernet1/1/1] port link-type trunk
[DeviceE-GigabitEthernet1/1/1] port trunk permit vlan all
[DeviceE-GigabitEthernet1/1/1] quit
[DeviceE] interface gigabitethernet 1/1/3
[DeviceE-GigabitEthernet1/1/3] link-delay 0
[DeviceE-GigabitEthernet1/1/3] undo stp enable
[DeviceE-GigabitEthernet1/1/3] port link-type trunk
[DeviceE-GigabitEthernet1/1/3] port trunk permit vlan all
[DeviceE-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 15 as the protected VLANs of RRPP domain 1.
[DeviceE] rrpp domain 1
[DeviceE-rrpp-domain1] control-vlan 4092
[DeviceE-rrpp-domain1] protected-vlan reference-instance 0 to 15
# Configure Device E as the master node of subring 2, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 2.
[DeviceE-rrpp-domain1] ring 2 node-mode master primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 1
[DeviceE-rrpp-domain1] ring 2 enable
[DeviceE-rrpp-domain1] quit
# Enable RRPP.
[DeviceE] rrpp enable
4) Verification
After the configuration, you can use the display command to view RRPP configuration and operational information on each device.
l Because each S3600 EPON OLT switch has only two Gigabit uplink combo ports that support RRPP, you cannot configure an S3600 EPON OLT switch as an edge node or assistant-edge node of an RRPP ring. When configuring edge nodes or assistant-edge nodes of RRPP rings, select H3C switches of other series. For detailed configurations, refer to the manuals delivered with the selected switches.
l On the network shown in Figure 1-10, Device A, Device D, Device E, and Device F can be S3600 EPON OLT switches.
As shown in Figure 1-10:
l Device A, Device B, Device C, Device D, and Device F constitute RRPP domain 1, and VLAN 100 is the primary control VLAN of the RRPP domain. Device A is the master node of the primary ring Ring 1; Device D is the transit node of the primary ring Ring 1; Device F is the master node of the subring Ring 3; Device C is the edge node of the subring Ring 3; Device B is the assistant-edge node of the subring Ring 3.
l Device A, Device B, Device C, Device D, and Device E constitute RRPP domain 2, and VLAN 105 is the primary control VLAN of the RRPP domain. Device A is the master node of the primary ring Ring 1; Device D is the transit node of the primary ring Ring 1; Device E is the master node of the subring Ring 2; Device C is the edge node of the subring Ring 2; Device B is the assistant-edge node of the subring Ring 2.
l Specify VLAN 10 as the protected VLAN of domain 1, and VLAN 20 as the protected VLAN of domain 2. Thus, you can achieve VLAN-based load balancing on the primary ring.
Figure 1-10 Network diagram for intersecting-ring load balancing configuration
1) Configuration on Device A
# Create VLANs 10 and 20, and map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2.
<DeviceA> system-view
[DeviceA] vlan 10
[DeviceA-vlan10] quit
[DeviceA] vlan 20
[DeviceA-vlan20] quit
[DeviceA] stp region-configuration
[DeviceA-mst-region] instance 1 vlan 10
[DeviceA-mst-region] instance 2 vlan 20
[DeviceA-mst-region] active region-configuration
[DeviceA-mst-region] quit
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
[DeviceA] interface gigabitethernet 1/1/1
[DeviceA-GigabitEthernet1/1/1] link-delay 0
[DeviceA-GigabitEthernet1/1/1] undo stp enable
[DeviceA-GigabitEthernet1/1/1] port link-type trunk
[DeviceA-GigabitEthernet1/1/1] undo port trunk permit vlan 1
[DeviceA-GigabitEthernet1/1/1] port trunk permit vlan 10 20
[DeviceA-GigabitEthernet1/1/1] quit
[DeviceA] interface gigabitethernet 1/1/3
[DeviceA-GigabitEthernet1/1/3] link-delay 0
[DeviceA-GigabitEthernet1/1/3] undo stp enable
[DeviceA-GigabitEthernet1/1/3] port link-type trunk
[DeviceA-GigabitEthernet1/1/3] undo port trunk permit vlan 1
[DeviceA-GigabitEthernet1/1/3] port trunk permit vlan 10 20
[DeviceA-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 100 as the primary control VLAN of RRPP domain 1, and configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.
[DeviceA] rrpp domain 1
[DeviceA-rrpp-domain1] control-vlan 100
[DeviceA-rrpp-domain1] protected-vlan reference-instance 1
# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceA-rrpp-domain1] ring 1 enable
[DeviceA-rrpp-domain1] quit
# Create RRPP domain 2, configure VLAN 105 as the primary control VLAN of RRPP domain 2, and configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.
[DeviceA] rrpp domain 2
[DeviceA-rrpp-domain2] control-vlan 105
[DeviceA-rrpp-domain2] protected-vlan reference-instance 2
# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/1/3 as the master port and GigabitEthernet 1/1/1 as the secondary port, and enable ring 1.
[DeviceA-rrpp-domain2] ring 1 node-mode master primary-port gigabitethernet 1/1/3 secondary-port gigabitethernet 1/1/1 level 0
[DeviceA-rrpp-domain2] ring 1 enable
[DeviceA-rrpp-domain2] quit
# Enable RRPP.
[DeviceA] rrpp enable
2) Configuration on Device D
# Create VLANs 10 and 20, and map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2.
<DeviceD> system-view
[DeviceD] vlan 10
[DeviceD-vlan10] quit
[DeviceD] vlan 20
[DeviceD-vlan20] quit
[DeviceD] stp region-configuration
[DeviceD-mst-region] instance 1 vlan 10
[DeviceD-mst-region] instance 2 vlan 20
[DeviceD-mst-region] active region-configuration
[DeviceD-mst-region] quit
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
[DeviceD] interface gigabitethernet 1/1/1
[DeviceD-GigabitEthernet1/1/1] link-delay 0
[DeviceD-GigabitEthernet1/1/1] undo stp enable
[DeviceD-GigabitEthernet1/1/1] port link-type trunk
[DeviceD-GigabitEthernet1/1/1] undo port trunk permit vlan 1
[DeviceD-GigabitEthernet1/1/1] port trunk permit vlan 10 20
[DeviceD-GigabitEthernet1/1/1] quit
[DeviceD] interface gigabitethernet 1/1/3
[DeviceD-GigabitEthernet1/1/3] link-delay 0
[DeviceD-GigabitEthernet1/1/3] undo stp enable
[DeviceD-GigabitEthernet1/1/3] port link-type trunk
[DeviceD-GigabitEthernet1/1/3] undo port trunk permit vlan 1
[DeviceD-GigabitEthernet1/1/3] port trunk permit vlan 10 20
[DeviceD-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 100 as the primary control VLAN of RRPP domain 1, and configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.
[DeviceD] rrpp domain 1
[DeviceD-rrpp-domain1] control-vlan 100
[DeviceD-rrpp-domain1] protected-vlan reference-instance 1
# Configure Device D as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceD-rrpp-domain1] ring 1 enable
[DeviceD-rrpp-domain1] quit
# Create RRPP domain 2, configure VLAN 105 as the primary control VLAN of RPPP domain 2, and configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.
[DeviceD] rrpp domain 2
[DeviceD-rrpp-domain2] control-vlan 105
[DeviceD-rrpp-domain2] protected-vlan reference-instance 2
# Configure Device D as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable ring 1.
[DeviceD-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 0
[DeviceD-rrpp-domain2] ring 1 enable
[DeviceD-rrpp-domain2] quit
# Enable RRPP.
[DeviceD] rrpp enable
3) Configuration on Device E
# Create VLAN 20, and map VLAN 20 to MSTI 2.
<DeviceE> system-view
[DeviceE] vlan 20
[DeviceE-vlan20] quit
[DeviceE] stp region-configuration
[DeviceE-mst-region] instance 2 vlan 20
[DeviceE-mst-region] active region-configuration
[DeviceE-mst-region] quit
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
[DeviceE] interface gigabitethernet 1/1/1
[DeviceE-GigabitEthernet1/1/1] link-delay 0
[DeviceE-GigabitEthernet1/1/1] undo stp enable
[DeviceE-GigabitEthernet1/1/1] port link-type trunk
[DeviceE-GigabitEthernet1/1/1] undo port trunk permit vlan 1
[DeviceE-GigabitEthernet1/1/1] port trunk permit vlan 20
[DeviceE-GigabitEthernet1/1/1] quit
[DeviceE] interface gigabitethernet 1/1/3
[DeviceE-GigabitEthernet1/1/3] link-delay 0
[DeviceE-GigabitEthernet1/1/3] undo stp enable
[DeviceE-GigabitEthernet1/1/3] port link-type trunk
[DeviceE-GigabitEthernet1/1/3] undo port trunk permit vlan 1
[DeviceE-GigabitEthernet1/1/3] port trunk permit vlan 20
[DeviceE-GigabitEthernet1/1/3] quit
# Create RRPP domain 2, configure VLAN 105 as the primary control VLAN, and configure the VLAN mapped to MSTI 2 as the protected VLAN.
[DeviceE] rrpp domain 2
[DeviceE-rrpp-domain2] control-vlan 105
[DeviceE-rrpp-domain2] protected-vlan reference-instance 2
# Configure Device E as the master mode of subring 2 in RRPP domain 2, with GigabitEthernet 1/1/3 as the primary port and GigabitEthernet 1/1/1 as the secondary port, and enable ring 2.
[DeviceE-rrpp-domain2] ring 2 node-mode master primary-port gigabitethernet 1/1/3 secondary-port gigabitethernet 1/1/1 level 1
[DeviceE-rrpp-domain2] ring 2 enable
[DeviceE-rrpp-domain2] quit
# Enable RRPP.
[DeviceE] rrpp enable
4) Configuration on Device F
# Create VLAN 10, and map VLAN 10 to MSTI 1.
<DeviceF> system-view
[DeviceF] vlan 10
[DeviceF-vlan10] quit
[DeviceF] stp region-configuration
[DeviceF-mst-region] instance 1 vlan 10
[DeviceF-mst-region] active region-configuration
[DeviceF-mst-region] quit
# Configure RRPP ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/3.
[DeviceF] interface gigabitethernet 1/1/1
[DeviceF-GigabitEthernet1/1/1] link-delay 0
[DeviceF-GigabitEthernet1/1/1] undo stp enable
[DeviceF-GigabitEthernet1/1/1] port link-type trunk
[DeviceF-GigabitEthernet1/1/1] undo port trunk permit vlan 1
[DeviceF-GigabitEthernet1/1/1] port trunk permit vlan 10
[DeviceF-GigabitEthernet1/1/1] quit
[DeviceF] interface gigabitethernet 1/1/3
[DeviceF-GigabitEthernet1/1/3] link-delay 0
[DeviceF-GigabitEthernet1/1/3] undo stp enable
[DeviceF-GigabitEthernet1/1/3] port link-type trunk
[DeviceF-GigabitEthernet1/1/3] undo port trunk permit vlan 1
[DeviceF-GigabitEthernet1/1/3] port trunk permit vlan 10
[DeviceF-GigabitEthernet1/1/3] quit
# Create RRPP domain 1, configure VLAN 100 as the primary control VLAN, and configure the VLAN mapped to MSTI 1 as the protected VLAN.
[DeviceF] rrpp domain 1
[DeviceF-rrpp-domain1] control-vlan 100
[DeviceF-rrpp-domain1] protected-vlan reference-instance 1
# Configure Device F as the master node of subring 3 in RRPP domain 1, with GigabitEthernet 1/1/1 as the primary port and GigabitEthernet 1/1/3 as the secondary port, and enable subring 3.
[DeviceF-rrpp-domain1] ring 3 node-mode master primary-port gigabitethernet 1/1/1 secondary-port gigabitethernet 1/1/3 level 1
[DeviceF-rrpp-domain1] ring 3 enable
[DeviceF-rrpp-domain1] quit
# Enable RRPP.
[DeviceF] rrpp enable
5) Verification
After the configuration, you can use the display command to view RRPP configuration and operational information on each device.
When the link state is normal, the master node cannot receive Hello packets, and the master node unblocks the secondary port.
The reasons may be:
l RRPP is not enabled on some nodes in the RRPP ring.
l The domain ID or primary control VLAN ID is not the same for the nodes in the same RRPP ring.
l Some ports are abnormal.
l Use the display rrpp brief command to check whether RRPP is enabled for all nodes. If not, use the rrpp enable command and the ring enable command to enable RRPP and RRPP rings for all nodes.
l Use the display rrpp brief command to check whether the domain ID and primary control VLAN ID are the same for all nodes. If not, set the same domain ID and primary control VLAN ID for the nodes.
l Use the display rrpp verbose command to check the link state of each port in each ring.
l Use the debugging rrpp command on each node to check whether a port receives or transmits Hello packets. If not, Hello packets are lost.
