The maximum load-balancing ingress-lsp command configures the maximum number of labeled BGP routes used for load balancing.
The undo maximum load-balancing ingress-lsp command restores the default configurations.
By default, the maximum number of labeled BGP routes for load balancing is 1.
| Parameter | Description | Value |
|---|---|---|
number |
Specifies the maximum number of equal-cost labeled routes in the BGP routing table. |
The value can be 1 or 2. |
Usage Scenario
After the maximum load-balancing ingress-lsp command is run on the ingress of a BGP LSP, labeled BGP routes can load-balance traffic as long as equal-cost labeled BGP routes exist, which improves network bandwidth utilization.
After BGP load balancing is configured, multiple BGP routes that meet the following conditions and have the same As_Path become equal-cost routes to load-balance traffic:
The PrefVal attributes of the BGP routes are the same.
The Local_Pref attributes of the BGP routes are the same.
The BGP routes are all summarized routes or none of them is a summarized route.
The BGP routes have the same AIGP value.
The lengths of the AS paths 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.
The BGP routes are either all EBGP or all IBGP routes.
The metric values of intra-AS IGP routes imported and converted to the BGP routes are the same.
The AS_Path attributes of the BGP routes are the same.
If the optimal route is a BGP labeled route, all routes with the same prefix that can load-balance traffic must be labeled routes, and the number of labeled routes used for load balancing is determined by the maximum load-balancing ingress-lsp command. If the optimal route is a non-labeled BGP route, all routes with the same prefix that can load-balance traffic must be non-labeled routes, and the number of non-labeled routes used for load balancing is determined by the maximum load-balancing command.
Precautions
If the maximum load-balancing ingress-lsp command is run more than once, the latest configuration overrides the previous one.