Configuring P2MP TE FRR

Usage Scenario

P2MP TE FRR establishes a bypass tunnel to provide local link protection for the P2MP TE tunnel called the primary tunnel. The bypass tunnel is a P2P TE tunnel. The principles and concepts of P2MP TE FRR are similar to those of P2P TE FRR.

The NetEngine 8000 F supports FRR link protection, not node protection, over a P2MP TE tunnel. Therefore, path planning for the bypass tunnel is irrelevant to node protection. For example, in Figure 1, the bypass tunnel path planned for the link between P1 and P2 can provide link protection. However, the link between P3 and PE4 for which a bypass tunnel path is planned traverses the node P4 so that the bypass tunnel cannot be bound to the primary tunnel or provide link protection.

Figure 1 FRR link protection for a P2MP TE tunnel

P2P and P2MP TE tunnels can share a bypass tunnel. Therefore, when planning bandwidth for the bypass tunnel, ensure that the bypass tunnel bandwidth is equal to the total bandwidth of the bound P2P and P2MP tunnels.

If traffic is switched to a P2MP FRR tunnel, the forwarding performance deteriorates temporarily, and the impact is removed after traffic switches back to the primary tunnel.

In NG MVPN scenarios, when P2MP TE FRR protection is used, the interface of a primary P2MP tunnel needs to be enabled to delay in going Up. The delay is related to the number of VPN multicast groups over the tunnel. For 1000 multicast groups, set the delay time to 30s. Increase the delay time if more multicast groups are configured.

Pre-configuration Tasks

Before configuring P2MP TE FRR, complete the following task:

• Configure a P2MP TE tunnel.