Configuring Multicast Source Cloning-based PIM FRR

This section describes how to configure multicast source cloning-based PIM fast reroute (FRR) to provide E2E node and link protection for multicast services.

Usage Scenario

Generally, PIM FRR and unicast route FRR can be deployed to implement multicast service switchover in a multicast link failure scenario. These two protection mechanisms, however, cannot provide E2E node and link protection for multicast services. Multicast source cloning-based PIM FRR can address this issue by allowing you to specify primary and backup RPF vector paths for transmitting cloned multicast traffic, implementing dual feed and selective receiving. Normally, a user-side device permits the multicast traffic on the primary link and discards that on the backup link. However, the device starts to permit the multicast traffic on the backup link immediately after the primary link fails, speeding up multicast traffic convergence.

Multicast source cloning-based PIM FRR applies only to IPv4 PIM-SM, IPv4 PIM-SSM, and Rosen MVPN scenarios.

Only NetEngine 8000 F1A supports multicast source cloning-based PIM FRR.

Pre-configuration Tasks

Before configuring multicast source cloning-based PIM FRR, complete the following tasks:

Configure a unicast routing protocol to ensure that devices are reachable.
Configure PIM.

Procedure

Enable PIM interfaces to send PIM Hello messages that carry the Join attribute.
1. Run system-view
  The system view is displayed.
2. Run pim [ vpn-instancevpn-instance-name ]
  The PIM view is displayed.
3. Run hello-option join-attribute enable
  PIM interfaces are enabled to send PIM Hello messages that carry the Join attribute.
4. Run commit
  The configuration is committed.
On the user-side multicast device (receiver PE): Enable the device to clone user-to-source multicast Join messages.
1. Run system-view
  The system view is displayed.
2. Run pim [ vpn-instancevpn-instance-name ]
  The PIM view is displayed.
3. Run rpf-frr [ policy { acl-number | acl-nameacl-name } ]
  PIM FRR is enabled.
4. Run rpf-frr clone join source-address to source-address1 and source-address2 masklen mask-length
  The function to clone user-to-source multicast Join messages is enabled.
5. (Optional) Run rpf-frr clone interface-inheritance
  Cloned (S, G) entries are enabled to inherit the outbound interfaces of (*, G) entries.
  
  If multicast user terminals running IGMPv2 exist on interfaces, you can run this command to enable cloned (S, G) entries to inherit the outbound interfaces of (*, G) entries, allowing the user terminals to receive two copies of the same multicast flow and speeding up multicast service restoration in fault scenarios.
6. Run quit
  Return to the system view.
7. (Optional) Run multicast frr revert disable
  Multicast FRR traffic switchback is disabled.
  
  This command prevents repeated multicast traffic switchovers and minimizes service loss if source-address1 is set to the same value as source-address.
8. Run commit
  The configuration is committed.
On the user-side multicast device (receiver PE): Specify an RPF vector path for a multicast source address.
1. Run system-view
  The system view is displayed.
2. Run multicast rpf-vector pathpath-name [ loose | strict ]
  A strict or loose RPF vector path is created.
3. Run next hop indexindexip-address
  A next hop IP address is set for each hop on the RPF vector path.
4. Run quit
  Return to the system view.
5. Run pim [ vpn-instancevpn-instance-name ]
  The PIM view is displayed.
6. Run rpf-vector destination ip-address masklen mask-length path path-name
  The RPF vector path is specified for a specified multicast source.
7. (Optional) Run rpf-vector compatible standard
  The device is configured to use the standard format to encapsulate Hello and Join/Prune messages that carry the vector attribute.
  
  This command prevents communication failures when the Huawei device interworks with a non-Huawei device that uses the standard format to encapsulate such messages.
8. Run commit
  The configuration is committed.
On the multicast source-side device (sender PE): Enable the function to clone the traffic of a multicast source.
1. Run system-view
  The system view is displayed.
2. Run pim [ vpn-instancevpn-instance-name ]
  The PIM view is displayed.
3. Run rpf-frr [ policy { acl-number | acl-nameacl-name } ]
  PIM FRR is enabled.
4. Run rpf-frr clone source source-address to source-address1 [ and source-address2 ] masklen mask-length
  The function to clone the traffic of a multicast source is enabled.
5. Run quit
  Return to the system view.
6. Run commit
  The configuration is committed.

Verifying the Configuration

After configuring multicast source cloning-based PIM FRR, run the display pim routing-table command to check whether the configuration is correct.

# Run the display pim routing-table command to view backup inbound interface information in the PIM routing table.