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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

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 BGP ADD-PATH

Configuring BGP ADD-PATH

Usage Scenario

In a scenario with an RR and clients, if the RR has multiple routes to the same destination (with the same prefix), the RR selects an optimal route from these routes and then sends only the optimal route to its clients. Therefore, the clients have only one route to the destination. If a link along this route fails, route convergence takes a long time, which cannot meet the requirements for high reliability.

To address this issue, deploy the BGP ADD-PATH feature on the RR. With BGP ADD-PATH, the RR can send two or more routes with the same prefix to a specified IBGP peer. These routes can back up each other or load-balance traffic, which ensures high reliability in data transmission. The BGP ADD-PATH feature does not affect BGP route selection rules.

NOTE:

The RR can send ADD-PATH routes only to IBGP peers.

Enable BGP ADD-PATH on the RR, enable the RR to send ADD-PATH routes to a specified IBGP peer, configure the number of routes that the RR can send to the IBGP peer, and enable the IBGP peer to receive BGP ADD-PATH routes from the RR so that such routes are available to the IBGP peer. In Figure 9-17, you can enable BGP ADD-PATH on the RR and enable SwitchA to receive BGP ADD-PATH routes from the RR. Then SwitchA can receive two routes destined for 172.16.1.1/32, with next hops of 192.168.1.1 and 192.168.2.1. The two routes can back up each other or load-balance traffic.

Figure 9-17 Networking for configuring BGP ADD-PATH

Pre-configuration Tasks

Before configuring BGP ADD-PATH, configure basic BGP functions.

Procedure

  • Perform the following steps on the RR:
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run bestroute add-path path-number path-number

      BGP ADD-PATH is enabled, and the number of routes that the RR can select is configured.

    4. Run peer { ipv4-address1 | group-name1 } capability-advertise add-path send

      The RR is enabled to send ADD-PATH routes to the specified IBGP peer (SwitchA).

    5. Run peer { ipv4-address1 | group-name1 } advertise add-path path-number path-number

      The number of routes that the RR can send to the IBGP peer is configured.

    6. Run commit

      The configuration is committed.

  • Perform the following steps on SwitchA:
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer { ipv4-address2 | group-name2 } capability-advertise add-path receive

      SwitchA is enabled to receive ADD-PATH routes from the RR.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 55203

Downloads: 62

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