No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C10SPC500 Configuration Guide - IP Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Multicast
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Multicast Source Cloning-based PIM FRR

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.

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

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

  1. 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-instance vpn-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.

  2. 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-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run rpf-frr [ policy { acl-number | acl-name acl-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-inheritence

      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

      The system view is displayed.

    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.

  3. 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 path path-name [ loose | strict ]

      A strict or loose RPF vector path is created.

    3. Run next hop index index ip-address

      A next hop IP address is set for each hop on the RPF vector path.

    4. Run quit

      The system view is displayed.

    5. Run pim [ vpn-instance vpn-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.

  4. 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-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run rpf-frr [ policy { acl-number | acl-name acl-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

      The system view is displayed.

    6. Run commit

      The configuration is committed.

Checking the Configurations

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.

# Run the display multicast forwarding-table command to view multicast forwarding entry information.

# Run the display multicast frr-table command to view multicast FRR entry information.

<HUAWEI> display pim routing-table
 VPN-Instance: VPNA
 Total 0 (*, G) entry; 3 (S, G) entries

  (10.3.4.2, 225.0.0.1)
     RP: 10.1.11.1 (local)
     Protocol: pim-sm, Flag: RPT SPT ACT SG_RCVR MFB
     UpTime: 00:16:04
     Upstream interface: MTunnel0
         RPF vector: 10.4.4.4
         Upstream neighbor: 10.4.4.4
         RPF prime neighbor: 10.4.4.4
     Original route: (10.3.13.1, 225.0.0.1)
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: clone-pseudo
             Protocol: clone, UpTime: 00:16:06, Expires: -

 (10.3.6.2, 225.0.0.1)
     RP: 10.1.11.1 (local)
     Protocol: pim-sm, Flag: RPT SPT ACT SG_RCVR MFB
     UpTime: 00:16:04
     Upstream interface: MTunnel0
         RPF vector: 10.6.6.6
         Upstream neighbor: 10.6.6.6
         RPF prime neighbor: 10.6.6.6
     Original route: (10.3.13.1, 225.0.0.1)
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: clone-pseudo
             Protocol: clone, UpTime: 00:16:06, Expires: -

 (10.3.13.1, 225.0.0.1)
     RP: 10.1.11.1 (local)
     Protocol: pim-sm, Flag: SPT 2MSDP ACT 2BGP
     UpTime: 00:16:04
     Upstream interface: clone
         Upstream neighbor: NULL
         RPF prime neighbor: NULL
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/2
             Protocol: static, UpTime: 00:16:06, Expires: -

     FSM information for non-downstream interfaces: none
<HUAWEI> display pim routing-table rpf-vector verbose
 VPN-Instance: public net
 Total 1 (S, G) entry 
 
 Total matched 0 (*, G) entry; 1 (S, G) entry
 
 (192.168.1.2, 232.0.0.1)
     Protocol: pim-ssm, Flag: 
     UpTime: 1d:16h
     Upstream interface: GigabitEthernet1/0/6
         Elected vector: 2.2.2.2
         RPF vector: 1.1.1.1
         Upstream neighbor: 10.0.0.1
         RPF prime neighbor: 10.0.0.1
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/0
             Protocol: pim-ssm, UpTime: 1d:16h, Expires: 00:03:15
             Attribute state: [SAFE] , Elected Vector: 2.2.2.2, Neighbor: 3.0.0.1 
             Total number of vectors: 1
                 1: vector: 2.2.2.2, neighbor: 3.0.0.1, Expires: 00:03:15 
<HUAWEI> display multicast forwarding-table
Multicast Forwarding Table of VPN-Instance: public_net
Total 1 entry, 1 matched

1.(1.1.3.2, 232.0.0.1)
     MID: 16, Flags: 1
     Uptime: 00:20:31, Timeout in: 00:00:00
     Incoming interface: GigabitEthernet1/0/4
     List of 1 outgoing interfaces:
       1: ClonePseudo
         Activetime: 00:20:31
     Matched rate: 0 packets/sec, 0 bits/sec
     Matched 0 packets(0 bytes), Wrong If 0 packets
     Forwarded 0 packets(0 bytes)
<HUAWEI> display multicast frr-table source 10.1.0.1 group 232.0.0.1
MID:19283, BakMID:17582, Status:Dynamic
Primary Sourceip: 10.1.1.1
Backup Sourceip:  10.1.2.1
Receive Sourceip: Primary
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44430

Downloads: 97

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next