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 an Anycast-RP Peer

Configuring an Anycast-RP Peer

When sending a PIM Register message to all Anycast-Rendezvous Point (RP) peers, the local RP needs to use the peer addresses as the destination addresses of the Register message.

Context

The routers functioning as Anycast-RPs can be identified by the same logical address so that the RP in the PIM-SM domain is unique. However, the routers need to distinguish one another during the communication, so the Anycast-RP address cannot be used. To resolve this issue, configure Anycast-RP peers.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Configure a basic or an advanced ACL as needed.

    • Configure a basic ACL.

      1. Run acl [ number ] basic-acl-number [ match-order { auto | config } ]

        A basic ACL is created, and the basic ACL view is displayed.

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

        Rules are configured for the basic ACL.

    • Configure an advanced ACL.

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

      2. 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.

  3. Run quit

    Return to the system view.

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

    The PIM view is displayed.

  5. Run anycast-rp rp-address

    The Anycast-RP view is displayed.

  6. Run peer peer-address [ fwd-msdp-sa [ acl-number | acl-name acl-name ] ]

    An Anycast-RP peer is specified.

    • peer-address: specifies the local address of an Anycast-RP peer.

    • fwd-msdp-sa: enables a local RP to extract source and group information from received Multicast Source Discovery Protocol (MSDP) Source Active (SA) messages, encapsulate the information into Register messages, and send Register messages to Anycast-RP peers.

    • In a PIM-SM domain, all Anycast-RP-capable devices must be fully connected. Anycast-RP peer relationships must be configured between every two Anycast-RPs.

    NOTE:
    • If no ACL is configured, the local RP extracts source/group information from received MSDP SA messages, encapsulates the information into a Register message, and sends the Register message to Anycast-RP peers.
    • If an ACL is configured, the local RP uses configured ACL rules to filter multicast group addresses in MSDP SA messages to be forwarded.
      • If an MSDP SA message matches an ACL rule and the action is permit, the local RP forwards this message.
      • If an MSDP SA message matches an ACL rule and the action is deny, the local RP does not forward this message.
      • If an MSDP SA message does not match any ACL rule, the local RP does not forward this message.
      • If a specified ACL does not exist or does not contain rules, the local RP does not forward MSDP SA messages.

  7. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 40737

Downloads: 97

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