5-7
RRPP ring group
In an edge node RRPP ring group, only an activated subring with the lowest domain ID and ring
ID can send Edge-Hello packets. In an assistant-edge node RRPP ring group, any activated
subring that has received Edge-Hello packets will forward these packets to the other activated
subrings. With an edge node RRPP ring group and an assistant-edge node RRPP ring group
configured, only one subring sends Edge-Hello packets on the edge node, and only one subring
receives Edge-Hello packets on the assistant-edge node, thus reducing CPU workload.
As shown in
, Device B is the edge node of Ring 2 and Ring 3, and Device C is the
assistant-edge node of Ring 2 and Ring 3. Device B and Device C need to send or receive
Edge-Hello packets frequently. If more subrings are configured or load balancing is configured
for more multiple domains, Device B and Device C will send or receive a mass of Edge-Hello
packets.
To reduce Edge-Hello traffic, you can assign Ring 2 and Ring 3 to an RRPP ring group
configured on the edge node Device B, and assign Ring 2 and Ring 3 to an RRPP ring group
configured on Device C. After such configurations, if all rings are activated, only Ring 2 on
Device B sends Edge-Hello packets.
Typical RRPP Networking
Here are several typical networking applications.
Single ring
As shown in
, there is only a single ring in the network topology. In this case, you only
need to define an RRPP domain.
Figure 5-2
Schematic diagram for a single-ring network
Tangent rings
As shown in
, 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.
