maximum load-balancing(BGP-VPN instance IPv4 address family view/BGP-labeled VPN instance IPv4 address family view)

Function

The maximum load-balancing ingress-lsp command sets the maximum number of equal-cost BGP labeled routes for ingress LSP load balancing.

The undo maximum load-balancing ingress-lsp command restores the maximum number of equal-cost BGP labeled routes to the default value 1.

The maximum load-balancing transit-lsp command sets the maximum number of equal-cost BGP labeled routes for transit LSP load balancing.

The undo maximum load-balancing transit-lsp command restores the maximum number of equal-cost BGP labeled routes to the default value 1.

By default, the maximum number of equal-cost BGP labeled routes is 1, and ingress LSP load balancing and transit LSP load balancing are not implemented.

Format

maximum load-balancing ingress-lsp ingressNumber

maximum load-balancing transit-lsp transitNumber

undo maximum load-balancing ingress-lsp

undo maximum load-balancing ingress-lsp ingressNumber

undo maximum load-balancing transit-lsp

undo maximum load-balancing transit-lsp transitNumber

Parameters

Parameter	Description	Value
transit-lsp transitNumber	Specifies the maximum number of equal-cost routes for load balancing.	The value is an integer that ranges from 1 to 16.
ingress-lsp ingressNumber	Specifies the maximum number of equal-cost routes for load balancing.	The value is an integer ranging from 1 to 16.

Parameter

Description

Value

transit-lsp transitNumber

Specifies the maximum number of equal-cost routes for load balancing.

The value is an integer that ranges from 1 to 16.

ingress-lsp ingressNumber

Specifies the maximum number of equal-cost routes for load balancing.

The value is an integer ranging from 1 to 16.

Views

BGP-labeled VPN instance IPv4 address family view, BGP-VPN instance IPv4 address family view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
bgp	write

Usage Guidelines

Usage Scenario

Multiple paths can be used for load balancing. To use this method, equal-cost routes must exist and you need to configure the maximum number of load-balancing routes.

After BGP load balancing is configured, the routes that meet the following conditions can implement load balancing as equal-cost routes:

The PrefVal attributes of the BGP routes are the same.
The Local_Pref attributes of the BGP routes are the same.
All the BGP routes are summary or non-summary routes.
The AS_Path lengths of the BGP routes are the same.
The origin types (IGP, EGP, or incomplete) of the BGP routes are the same.
The MED values of the BGP routes are the same.
All the BGP routes are EBGP or IBGP routes.
The IGP metric values of the BGP routes within an AS are the same.
The AS_Path attributes of the BGP routes are the same.
Original next-hop addresses of the BGP routes are different.
For BGP routes with the same prefix in a routing table:
If the optimal route and the routes selected for load balancing are all labeled routes, the number of routes used for load balancing depends on the maximum load-balancing ingress-lsp command and maximum load-balancing transit-lsp configuration.
If the optimal route and the routes selected for load balancing are all non-labeled routes, the number of routes used for load balancing depends on the maximum load-balancing command configuration.
If BGP labeled routes implement load balancing and the ingress LSP creation criteria are met, ingress LSPs are created for the labeled routes. If BGP labeled routes implement load balancing and the transit LSP creation criteria are met, transit LSPs are created for the labeled routes.

Precautions

The maximum load-balancing ingress-lsp and ingress-lsp protect-mode commands are mutually exclusive.

After configuring transit LSP load balancing, run the display bgp vpnv4 all routing-table commands to check whether load balancing has taken effect on the transit node.

If BGP labeled routes fail to recurse to tunnels, the routes cannot implement load balancing.

Example

# Set the maximum number of two equal-cost BGP IPv4 unicast labeled routes destined for the same IP address to implement ingress LSP load balancing.

<HUAWEI> system-view
[~HUAWEI] ip vpn-instance vpna
[*HUAWEI-vpn-instance-vpna] ipv4-family
[*HUAWEI-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[*HUAWEI-vpn-instance-vpna-af-ipv4] quit
[*HUAWEI-vpn-instance-vpna] quit
[*HUAWEI] bgp 100
[*HUAWEI-bgp] ipv4-family vpn-instance vpna
[*HUAWEI-bgp-vpna] maximum load-balancing ingress-lsp 2

# Set the maximum number of two equal-cost BGP IPv4 unicast labeled routes destined for the same IP address to implement transit LSP load balancing.

<HUAWEI> system-view
[~HUAWEI] ip vpn-instance vpna
[*HUAWEI-vpn-instance-vpna] ipv4-family
[*HUAWEI-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[*HUAWEI-vpn-instance-vpna-af-ipv4] quit
[*HUAWEI-vpn-instance-vpna] quit
[*HUAWEI] bgp 100
[*HUAWEI-bgp] ipv4-family vpn-instance vpna
[*HUAWEI-bgp-vpna] maximum load-balancing transit-lsp 2