Configuring Load Balancing Among IPv4 VPN Routes on the Backbone Network

This section describes how to configure load balancing of VPN traffic among multiple links on the backbone network of an IPv4 VPN.

Usage Scenario

Deploying load balancing among IPv4 VPN routes allows even distribution of VPN traffic to different links on the backbone network, improving the link usage.

A PE may receive multiple IPv4 VPN routes with the same prefix from different VPNv4 peers. Usually, the PE selects an optimal route and delivers it to the forwarding information base (FIB) to guide data forwarding. If load balancing is configured on the PE, it delivers multiple routes to the FIB. VPN data then can be distributed to different links on the backbone network in a packet-by-packet or session-by-session manner.

Pre-configuration Tasks

Before configuring load balancing among IPv4 VPN routes, complete the following tasks:

Configure a BGP/MPLS IP VPN.
Ensure that the PE receives IPv4 VPN routes with the same prefix from different VPNv4 peers.

Procedure

Run system-view
The system view is displayed.
Run bgp as-number
The BGP view is displayed.
Run ipv4-family vpn-instance vpn-instance-name
The BGP-VPN instance IPv4 address family view is displayed.
Run maximum load-balancing number
Load balancing among BGP routes is configured for the BGP VPN instance IPv4 address family.
Run commit
The configuration is committed.

Example

After completing the configurations, run the display ip routing-table vpn-instance vpn-instance-name ip-address [ mask-length ] [ longer-match ] [ verbose ] command on the PE. If the IPv4 VPN route has more than one next hop, load balancing among IPv4 VPN routes on the backbone network is configured.