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

Configuration Guide - IP Unicast Routing

S1720, S2700, S5700, and S6720 V200R011C10

This document describes IP Unicast Routing configurations supported by the switch, including the principle and configuration procedures of IP Routing Overview, Static Route, RIP, RIPng, OSPF, OSPFv3, IS-IS(IPv4), IS-IS(IPv6), BGP, Routing Policy ,and PBR, 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).
Configuring IS-IS Route Leaking

Configuring IS-IS Route Leaking

Context

If multiple Level-1-2 devices in a Level-1 area are connected to devices in the Level-2 area, a Level-1 LSP sent by each Level-1-2 device carries an ATT flag bit of 1. This Level-1 area will have multiple routes to the Level-2 area and to other Level-1 areas.

By default, routes in a Level-1 area can be leaked into the Level-2 area so that Level-1-2 and Level-2 devices can determine the topology of the entire network. Devices in a Level-1 area are unaware of the entire network topology because they only maintain LSDBs in the local Level-1 area. Therefore, a device in a Level-1 area can forward traffic to a Level-2 device only through the nearest Level-1-2 device. The route used may not be the optimal route to the destination.

To enable a device in a Level-1 area to select the optimal route, configure IPv4 IS-IS route leaking so that specified routes in the Level-2 area can be leaked into the local Level-1 area.

Routes of services deployed only in the local Level-1 area do not need to be leaked into the Level-2 area. A policy can be configured to leak only desired routes into the Level-2 area.

Procedure

  • Specify routes in the Level-2 area and other Level-1 areas that can be leaked into the local Level-1 area.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run import-route isis level-2 into level-1 [ tag tag | filter-policy { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } | direct { allow-filter-policy | allow-up-down-bit } * ] *

      Routes that meet the specified conditions in the Level-2 areas are leaked into the local Level-1 area.

      By default, routes in the Level-2 area are not leaked into Level-1 areas.

      NOTE:

      The command is run on the Level-1-2 device that is connected to an external area.

  • Configure routes in Level-1 areas to leak into the Level-2 area.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run import-route isis level-1 into level-2 [ tag tag | filter-policy { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } | direct allow-filter-policy ] *

      Routes that meet the specified conditions in Level-1 areas are leaked into the Level-2 area.

      By default, all routes in a Level-1 area are leaked into the Level-2 area.

      NOTE:

      The command is run on the Level-1-2 device that is connected to an external area.

Translation
Download
Updated: 2019-10-21

Document ID: EDOC1000178171

Views: 315120

Downloads: 1110

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