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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 V800R010C10SPC500 Configuration Guide - IP Routing
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).
Applying Filters to Imported Routes

Applying Filters to Imported Routes

By applying filters of routing policies to routing protocols, you can filter the imported routes.

Usage Scenario

After defining a filter (such as the IP prefix list, ACL, or route-policy) of a routing policy, you need to apply the filter to routing protocols.

You can apply routing policies when you want to import external routes:

  • You can use the import-route command in the related protocol view, import the required external routes to the protocols, and apply a route-policy to filter imported routes.

  • After external routes are imported, you can run the filter-policy export command to filter the imported external routes. Only the routes that meet the matching rules are advertised.

NOTE:
  • BGP has the powerful filtering function. For the configuration of BGP routing policies, refer to "BGP Configuration."

  • For details of the filter-policy and import-route commands and their applications in RIP, OSPF, IS-IS, and BGP, refer to related configurations.

Pre-configuration Tasks

Before applying filters to imported routes, complete the following tasks:

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring RIP to Import External Routes

Routing Information Protocol (RIP) can import routes from other processes or other routing protocols to enrich the RIP routing table.

Context

On a large-scale network, different routing protocols may be configured for devices in different areas. In this situation, configure RIP to import routes from other processes or other routing protocols.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. (Optional) Run default-cost cost

    The default cost is set for imported routes.

    If you do not specify the cost for external routes, the value 0 takes effect.

  4. Import external routes.

    • To import direct, static, IS-IS, or OSPF routes, or routes of other RIP processes, run the import-route { direct | static | { isis | ospf | rip } [ process-id ] } [ cost cost | route-policy route-policy-name ] * command.
    • To import IBGP routes, run the import-route bgp permit-ibgp [ cost { cost | transparent } | route-policy route-policy-name ] * command.
    NOTE:

    Import of other routes in RIP process can lead to routing loops. You should take care of routing loops before configuring import-route command.

  5. Run commit

    The configuration is submitted.

Configuring OSPF to Import External Routes

Importing the routes discovered by other routing protocols can enrich OSPF routing information.

Context

OSPF can ensure loop-free intra-area routes and inter-area routes; however, OSPF cannot protect external routes against loops. Therefore, when configuring OSPF to import external routes, avoid the loops caused by manual configurations.

Do as follows on the ME device that functions as the ASBR running OSPF:

Procedure

  • Configuring OSPF to import the routes discovered by other protocols
    1. Run system-view

      The system view is displayed.

    2. Run ospf [ process-id ]

      The OSPF process view is displayed.

    3. Run import-route { bgp [ permit-ibgp ] | direct | rip [ process-id-rip ] | static | isis [ process-id-isis ] | ospf [ process-id-ospf ] } [ cost cost | route-policy route-policy-name | tag tag | type type ] *

      The routes discovered by other protocols are imported.

      • The parameter cost cost specifies the cost of a route.
      • The parameter type type specifies the type of a route. It can be 1 or 2.
      • The parameter tag tag specifies the tag in the external LSA.
      • The parameter route-policy route-policy-name indicates that the matching rules of the specified routing policy are applied.

    4. Run commit

      The configuration is committed.

  • Setting parameters for OSPF to import routes
    1. Run system-view

      The system view is displayed.

    2. Run ospf [ process-id ]

      The OSPF process view is displayed.

    3. Run default { cost | inherit-metric } | tag tag | type type } * limit limit

      • The parameter cost cost specifies the default metric of the external route imported by OSPF.
      • The parameter inherit-metric indicates that the cost of the imported route is the cost carried in the route. If the cost is not specified, the default cost set through the default command is used as the cost of the imported route.

      The route tag is used to identify the protocol-related information. For example, it can be used to differentiate AS numbers when OSPF receives BGP routes.

      NOTE:
      You can run one of the following commands to set the cost of the imported route. The following commands are listed in descending order of priority:
      • Run the apply cost command in a route-policy to set the cost of the imported route.
      • Run the import-route command for OSPF to set the cost of the imported route.
      • Run the default command to set the default cost of the imported route.

    4. Run commit

      The configuration is committed.

Configuring IS-IS to Import External Routes

By configuring IS-IS to import routes, you can enable IS-IS to learn routing information of other protocols or other IS-IS processes.

Context

IS-IS regards the routes discovered by other routing protocols or other IS-IS processes as external routes. You can specify default costs for imported routes.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    The IS-IS view is displayed.

  3. Configure IS-IS to import external routes.

    Before setting costs for the imported routes, run the import-route { direct | static | { ospf | rip | isis } [ process-id ] | bgp [ permit-ibgp ] } [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy | [ level-1 | level-2 | level-1-2 ] ] * command to import external routes.

    Before retaining the original costs of the imported routes, run the import-route { { ospf | rip | isis } [ process-id ] | bgp [ permit-ibgp ] | direct } inherit-cost [ { level-1 | level-2 | level-1-2 } | tag tag | route-policy route-policy ] * command to import external routes.

    NOTE:

    permit-ibgp takes effect only in the public network instance.

    When the cost type of IS-IS is narrow, the parameters cost-type { external | internal } will determine the cost of imported routes.
    • If you configure external, the cost of imported routes equals the original route cost plus 64.
    • If you configure internal, the cost of imported routes is the same as the original route cost.

    To better manage and maintain IS-IS networks, configure route-policy route-policy to import only required routes.

    If you do not specify level-1, level-2, or level-1-2 in the command, routes are imported to the Level-2 routing table by default.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of Applying Filters to the Imported Routes

After applying filters to the imported routes, verify information about the routing table of each protocol.

Prerequisites

Filters have been applied to the imported routes.

Procedure

  • Run the display rip process-id route command to check information about the RIP routing table.
  • Run the display ospf [ process-id ] routing command to check information about the OSPF routing table.
  • Run the display isis [ process-id ] route command to check information about the IS-IS routing table.
  • Run the display ip routing-table command to check information about the IP routing table.

    Run the display ip routing-table command on the local ME device, and you can view that the routes that meet the matching rules set on the neighbor are filtered or the actions defined by apply clauses are performed on these routes.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20596

Downloads: 15

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