How do S series switches implement fast switchover when RRPP is deployed

2

For S series switches, fast RRPP switchover is guaranteed by the switchover mechanism, which is irrelevant to the interval for sending Hello packets. Although the minimum interval for sending Hello packets is 1s, Hello packets are used only for loop detection.
The following is the switchover mechanism of an RRPP ring:
- If a link in the ring is faulty, the port directly connected to the link goes Down.
- The transit node immediately sends a Link-Down packet to the master node to report the link status change.
- When receiving the Link-Down packet, the master node considers that the ring fails, so it unblocks the secondary port and sends a packet to instruct other transit nodes to update Forwarding DataBases (FDBs).
- After other transit nodes refresh their FDBs, the data stream is switched to a link in the Up state.

Other related questions:
How do S series switches implement load balancing when RRPP is deployed
For S series switches, each RRPP ring supports only one blocked port, so load balancing cannot be implemented in each ring. You can configure two domains and add ports to the two domains so that different blocked ports in two domains are used, implementing load balancing.

How many devices at most can be deployed in an RRPP ring when RRPP is deployed on an S series switch
For S series switches, primary and secondary ports of the master node send Health packets. If the secondary port periodically receives Health packets, the master node considers the RRPP ring in Complete state and blocks the secondary port to eliminate loops. Health packets are forwarded through the chip, whose forwarding speed is high. Theoretically, an RRPP ring supports unlimited devices. However, when many devices are configured in an RRPP ring, it takes a long time to rectify any link or node fault. It is recommended that a maximum of 16 devices be configured in an RRPP ring.

RRPP switchover time of S series switches
Sorry, I can't answer this question. For details about product specifications and performance, click http://e.huawei.com/en/service-hotline to look up the contact method of your local customer service engineers.

Implementation and application of fast leave of S series switches
For an S series switch, the fast leave function is configured using the igmp-snooping prompt-leave command (for Layer 2 multicast) or the igmp prompt-leave command (for Layer 3 multicast). If this function is not configured, the switch sends a Group-Specific Query message in response to an IGMP Leave message to check whether there are other users in the group specified in the Leave message. After fast leave is configured, the switch directly deletes the interface that receives the IGMP Leave message from the multicast forwarding entry, and does not check whether there are still users in the group. The fast leave function is applicable only to interfaces with only one user attached. If fast leave is configured on an interface connecting to multiple users, multicast traffic of all users under the interface is interrupted when one user switches to another channel.

S series switch RRPP configuration methods
For details on how to configure RRPP on S series switches (except S1700), click S1720&S2700&S3700&S5700&S6700&S7700&S9700 Typical Configuration Examples . The configurations on S9300 are the same with those on other models.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top