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.

Configuration Guide - IP Unicast Routing
CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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 RIP to Filter Received Routes

Configuring RIP to Filter Received Routes


The filtering policy can be configured on the inbound interface by configuring the ACL and IP prefix list to filter received routes. Only the routes not filtered out by the filtering policy are added to the local routing table.


  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    The RIP view is displayed.

  3. Depending on type of desired filtering, run one of following commands to configure RIP to filter the received routes:

    • Run filter-policy { acl-number | acl-name acl-name } import [ interface-type interface-number ]

      The learned routing information is filtered based on an ACL.

    • Run filter-policy gateway ip-prefix-name import

      The routing information advertised by neighbors is filtered based on the IP prefix list.

    • Run filter-policy ip-prefix ip-prefix-name [ gateway ip-prefix-name ] import [ interface-type interface-number ]

      The routes learned by the specified interface are filtered based on the IP prefix list and neighbors.

  4. Run commit

    The configuration is committed.

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 291650

Downloads: 168

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next