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 Import Routes

Configuring RIP to Import Routes


A RIP process can import the routes learned by other RIP processes or routing protocols.


  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    The RIP view is displayed.

  3. (Optional) Run default-cost cost

    The default metric for imported routes is set.

    If the metric of imported routes is not specified in step 4, the default metric is used.

  4. Run import-route bgp [ permit-ibgp ] [ cost { cost | transparent } | route-policy route-policy-name ] *

    Or run import-route { { static | direct } | { { rip | ospf | isis } [ process-id ] } } [ cost cost | route-policy route-policy-name ] *

    External routes are imported to RIP.


    When RIP imports IBGP routes, routing loops may occur. Configure this function with caution.

  5. (Optional) Run filter-policy { acl-number | acl-name acl-name | ip-prefix ip-prefix-name } export [ protocol [ process-id ] | interface-type interface-number ]

    The imported routes are filtered before being advertised.

    The routing information advertised by RIP may contain the routing information imported from other protocols. You can use the protocol parameter to filter the routing information imported from a specified routing protocol. If the protocol parameter is not used, all the routes advertised by RIP are filtered, including the imported routes and the local routes (direct routes).


    RIP-2 defines a 16-bit tag, while other routing protocols define 32-bit tags. If the routes of other protocols are imported to RIP and the tag is used in the routing policy, the tag value cannot exceed 65535. If the tag value exceeds 65535, the routing policy becomes invalid or the matching result is incorrect.

  6. Run commit

    The configuration is committed.

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 276544

Downloads: 161

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next