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

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 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).
Configuring BGP LSP Load Balancing

Configuring BGP LSP Load Balancing

Configuring BGP LSP load balancing improves network resource utilization and reduces network congestion.

Context

On large networks, there may be multiple valid routes to the same destination. BGP, however, advertises only the optimal route to its peers. This may result in unbalanced traffic on different routes.

Either of the following methods can be used to resolve the problem:
  • Use BGP policies for load balancing. For example, use a routing policy to modify the Local_Pref, AS_Path, Origin, or MED attribute of BGP routes to divert traffic to different forwarding paths for load balancing.
  • Use multiple paths for load balancing. To use this method, equal-cost routes must exist and you need to configure the maximum number of load-balancing routes.

In some BGP LSP scenarios, for example, in the scenario where BGP unicast routes are iterated to LSPs, or in the scenario where BGP LSPs can be iterated to multiple TE/LDP tunnels, traffic must be balanced to prevent network congestion. BGP LSP load balancing allows traffic to be balanced based on the maximum number of load-balancing routes configured on ingress and transit nodes of BGP LSPs when the traffic is forwarded along the BGP LSPs, which improves network resource utilization and reduces network congestion.

Pre-configuration Tasks

Before configuring BGP LSP load balancing, establish BGP LSPs.

Procedure

  • Configure ingress LSP load balancing on an ingress node.

    1. Run system-view

      The system view is displayed.

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

      The BGP view is displayed.

    3. (Optional) Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Run maximum load-balancing ingress-lsp number

      The maximum number of equal-cost BGP labeled routes is set for ingress LSP load balancing.

    5. Run commit

      The configuration is committed.

  • Configure transit LSP load balancing on a transit node.

    1. Run system-view

      The system view is displayed.

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

      The BGP view is displayed.

    3. (Optional) Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Run maximum load-balancing transit-lsp number

      The maximum number of equal-cost BGP labeled routes is set for transit LSP load balancing.

    5. Run commit

      The configuration is committed.

Checking the Configurations

  • After configuring ingress LSP load balancing, run the display mpls lsp protocol bgp command to check whether load balancing has taken effect on the ingress node.

  • After configuring transit LSP load balancing, run the display bgp routing-table and display ip routing-table commands to check whether load balancing has taken effect on the transit node. If the same destination IP address corresponds to more than one next hop, load balancing has taken effect.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 35584

Downloads: 53

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