[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Load Balancing and Routing Policies

If you enable protocol-independent load balancing for Layer 3 VPNs by including the multipath statement and if you also include the load-balance per-packet statement in the routing policy configuration, packets are not load-balanced.

For example, a PE router has the following VRF routing instance configured:



[edit routing-instances]
load-balance-example {
instance-type vrf;
interface fe-0/1/1.0;
interface fe-0/1/1.1;
route-distinguisher 2222:2;
vrf-target target:2222:2;


routing-options {
multipath;
}




protocols {


bgp {


group group-example {
import import-policy;


family inet {
unicast;
}


export export-policy;
peer-as 4444;
local-as 3333;
multipath;
as-override;
neighbor 10.12.33.22;
}


}


}


}

The PE router also has the following policy statement configured:



[edit policy-options policy-statement export-policy]
from protocol bgp;
then {
load-balance per-packet;
}

When you include the multipath statement in the VRF routing instance configuration, the paths are no longer marked as BGP paths but are instead marked as multipath paths. Packets from the PE router are not load-balanced.

To ensure that VPN load-balancing functions as expected, do not include the from protocol statement in the policy statement configuration. The policy statement should be configured as follows:



[edit policy-options policy-statement export-policy]
then {
load-balance per-packet;
}

For more information on how to configure per-packet load balancing, see the JUNOS Policy Framework Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]