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


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


CLI-based Configuration Guide - IP Multicast

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document describes the principles and configurations of IP multicast, and provides configuration examples.
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).
(Optional) Configuring Static RPF Peers

(Optional) Configuring Static RPF Peers


MSDP peers have been configured. For details, see Configuring MSDP Peers.


The device does not perform reverse path forwarding (RPF) checks on SA messages received from static RPF peers. Therefore, Source-Active (SA) messages are not discarded.

If a device has only one remote MSDP peer, the remote MSDP peer automatically becomes the static RPF peer.


  1. Run:


    The system view is displayed.

  2. Run:

    msdp [ vpn-instance vpn-instance-name ]

    The MSDP view is displayed.

  3. Run:

    static-rpf-peer peer-address [ rp-policy ip-prefix-name ]

    The remote MSDP peer is specified as the RPF peer.

    • peer-address: specifies the address of the remote MSDP peer.

    • rp-policy ip-prefix-name: specifies a policy for filtering SA messages based on the source RP address.

      When you specify multiple static RPF peers for a router, pay attention to the following points:

      • If rp-policy is set for all peers, after receiving SA messages from multiple active static RPF peers, the local router filters the SA messages based on the configured rp-policy for each static RPF peer. Only the SA messages that match policy rules are accepted.

      • If no rp-policy is set for the peers, the router accepts all SA messages from the active static RPF peers.

Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 24838

Downloads: 408

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