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.


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 a Route-policy

Configuring a Route-policy

A route-policy is used to filter routes.


A route-policy is used to match routes or route attributes, and to change route attributes when the matching rules are met.

Perform the following steps on the router that is configured as an MBGP peer:


This configuration is optional. By default, no route-policy is configured for route filtering.


  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run ipv4-family multicast

    The BGP-IPv4 multicast address family view is displayed.

  4. Run peer { group-name | peer-address } route-policy route-policy-name { import | export }

    A route-policy is configured to filter MBGP routes. Routes exchanged between the device and its remote MBGP peer can thus be controlled.

    • group-name: specifies an MBGP peer group.

    • peer-address: specifies the IP address of the remote MBGP peer.

    • route-policy-name: specifies the name of a route-policy.

    • import: filters routes received from a specified remote MBGP peer. Only the routes that pass the filtering will be permitted.

    • export: filters routes sent by a specified remote MBGP peer. Only the routes that pass the filtering will be sent out.

  5. Run commit

    The configuration is committed.

Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 43967

Downloads: 97

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