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).
Directing Multicast Traffic out of a P2MP TE Tunnel

Directing Multicast Traffic out of a P2MP TE Tunnel

When a point-to-multipoint (P2MP) traffic engineering (TE) tunnel is used to carry multicast services, you must direct multicast traffic out of the P2MP TE tunnel on the tunnel egress so that the multicast traffic can be correctly forwarded after leaving the tunnel.

Context

When a P2MP TE tunnel is used to carry multicast services, you do not need to deploy the Protocol Independent Multicast (PIM) on the transit nodes of the tunnel. If an egress performs the Reverse Path Forwarding (RPF) check on a received multicast data packet, the RPF check fails. As a result, the multicast data packet cannot be forwarded to the next-hop device. To resolve this problem, disable each egress from performing the RPF check on received packets.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run acl { name advance-acl-name [ advance | [ advance ] number advance-acl-number ] | [ number ] advance-acl-number } [ match-order { config | auto } ]

    An advanced ACL is created, and the advanced ACL view is displayed.

  3. Run rule [ rule-id ] [ name rule-name ] { deny | permit } ip [ destination { destination-ip-address { destination-wildcard | 0 } | any } | source { source-ip-address { source-wildcard | 0 } | any } ] *

    Rules are configured for the advanced ACL.

    Run the rule command, set the source parameter to a multicast source address, and set the destination parameter to a multicast group address.

  4. Run quit

    Return to the system view.

  5. Run pim [ vpn-instance vpn-instance-name ]

    The PIM view is displayed.

  6. Run rpf disable { policy { advanced-acl-number | acl-name } | all }

    The RPF check on multicast entries is disabled.

    NOTE:
    • If a multicast entry matches an ACL rule and the action is permit, the device does not perform the RPF check on the entry.
    • If a multicast entry matches an ACL rule and the action is deny, the device performs the RPF check on the entry.
    • If a multicast entry does not match any ACL rule, the device performs the RPF check on the entry.
    • If a specified ACL does not exist or does not contain rules, the device performs the RPF check on all multicast entries.

  7. Run traffic select p2mp-te root-ip ip-address tunnel-id tunnel-id

    The multicast traffic from the specified P2MP TE tunnel is directed to the VPN.

  8. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 39077

Downloads: 96

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