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 - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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 Device to Be Able to Iterate Non-labeled Public BGP Routes to LSPs

Configuring a Device to Be Able to Iterate Non-labeled Public BGP Routes to LSPs

By default, non-labeled public BGP routes can be iterated to outbound interfaces and next hops, but not to LSPs. You can configure the system to be able to iterate non-labeled public BGP routes to LSPs.

Usage Scenario

If an Internet user uses a carrier network that performs IP forwarding to access the Internet, core carrier devices on the forwarding path need to learn many Internet routes. This imposes a heavy load on core carrier devices and affects their performance. To solve this problem, configure the corresponding access device to be able to iterate non-labeled public BGP routes to LSPs, so that packets can be forwarded over a tunnel. This configuration frees core carrier devices from learning Internet routes, saving their routing table entries and CPU resources.

Pre-configuration Tasks

Before configuring the device to be able to iterate non-labeled public BGP routes to LSPs, complete the following tasks:

  • Configure the routing protocol or static routes.

  • Establish an MPLS LSP, BGP LSP, or MPLS local IfNet tunnel.

  • Configure an IP prefix list, tunnel selectoror tunnel policy to allow only desired non-labeled public BGP routes to be iterated to the LSP.

Procedure

  • Configure the device to be able to iterate non-labeled public BGP routes and static routes to LSPs.

    1. Run system-view

      The system view is displayed.

    2. Run route recursive-lookup tunnel [ ip-prefix ip-prefix-name ] [ tunnel-policy policy-name ]

      The system is configured to be able to iterate non-labeled public BGP routes and static routes to LSPs for MPLS forwarding.

      By default, non-labeled public BGP routes and static routes can be iterated only to outbound interfaces and next hops.

      This configuration iterates non-labeled public BGP routes and static routes to the following tunnels:
      • LDP LSP: Non-labeled public BGP routes and static routes can be iterated to LDP LSPs, supporting the bearer of unicast and multicast services.

      • BGP LSP: Non-labeled public BGP routes and static routes can be iterated to BGP LSPs, supporting the bearer of unicast services but not multicast services.

      • MPLS local IfNet tunnel: Only non-labeled public BGP routes can be iterated to MPLS local IfNet tunnels, supporting the bearer of unicast and multicast services.

      If neither ip-prefix ip-prefix-name or tunnel-policy policy-name is specified, all static routes and non-labeled public BGP routes are preferentially iterated to LSPs.

    3. Run commit

      The configuration is committed.

  • Configure the device to be able to iterate static routes to LSPs.

    1. Run system-view

      The system view is displayed.

    2. Run ip route-static recursive-lookup tunnel [ ip-prefix ip-prefix-name ] [ tunnel-policy policy-name ]

      The system is configured to be able to iterate static routes to LSPs for MPLS forwarding.

    3. Run commit

      The configuration is committed.

  • Configure the device to be able to iterate non-labeled public BGP routes to LSPs.

    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run unicast-route recursive-lookup tunnel [ tunnel-selector tunnel-selector-name ]

      The system is configured to be able to iterate non-labeled public BGP routes to LSPs for MPLS forwarding.

    4. Run commit

      The configuration is committed.

    NOTE:

    The ip route-static recursive-lookup tunnel and unicast-route recursive-lookup tunnel commands are mutually exclusive with the route recursive-lookup tunnel command. The ip route-static recursive-lookup tunnel and unicast-route recursive-lookup tunnel commands are not mutually exclusive.

Example

After configuring the system to be able to iterate non-labeled public BGP routes to LSPs, run the display bgp routing-table network command to view route iteration information.

# Run the display bgp routing-table network command. The command output shows the type of the relay tunnel.

<HUAWEI> display bgp routing-table 1.2.3.4
 BGP local router ID : 10.0.0.8
 Local AS number : 300
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 1.2.3.4/32:
 From: 10.0.0.12 (10.0.0.12)
 Route Duration: 0d00h00m38s
 Relay Tunnel Out-Interface: GigabitEthernet0/1/0
 Original nexthop: 10.0.0.12
 Qos information : 0x0
 AS-path Nil, origin incomplete, MED 0, localpref 100, pref-val 0, valid, intern
al, best, select, pre 255
 Advertised to such 2 peers:
    10.3.8.3
    10.4.8.4
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 36174

Downloads: 61

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