ON THIS PAGE
Example: Configuring Multicast Load Balancing over Aggregated Ethernet Links
This example shows how to configure point-to-multipoint LSPs to load balance across aggregated Ethernet links. The load balancing applies to all traffic types, including multicast. Feature parity for multicast load balancing of point-to-multipoint LSPs over aggregated Ethernet child links on the MX Series routers with MPCs or MICs is supported in Junos OS Releases 11.1R2, 11.2R2, and 11.4.
VPLS multicast load balancing requires Junos OS Release 14.1 or later.
Requirements
Before you begin:
Configure the router interfaces.
Configure an interior gateway protocol or static routing. See the Junos OS Routing Protocols Library.
Overview
This example shows a sample topology and configuration to perform the following tasks:
Load balancing VPLS multicast traffic over link aggregation
Load balancing point-to-multipoint multicast traffic over link aggregation
Re-load balancing after a change in the next-hop topology
Next-hop topology changes might include but are not limited to:
Layer 2 membership change in the link aggregation
Indirect next-hop change
Composite next-hop change
Load balancing is hash-based, so the higher the number of flows, the better. As is the case with unicast, you can also configure the hash key to be based on Layer 3 and Layer 4 information to achieve a better load-balancing result. There are a few exceptions that are specific to multicast traffic, which might lead to uneven load balancing—for example, when the outgoing interface list includes multiple aggregated interfaces with an unequal number of child links.
For Draft Rosen multicast VPNs (MVPNs), load balancing over aggregated Ethernet interfaces is uneven when the LAGs are all core interfaces. In the case of Next-Generation MBGP MPVNs, multicast traffic is sent over point-to-multipoint and RSVP, and the hash is computed up to the IP headers. In the Draft Rosen case, multicast traffic is tunneled over GRE tunnels, and the hash is used only on GRE tunnel headers. This is why load balancing is not even for Draft Rosen when the LAGs are all core interfaces.
Figure 1 shows the topology for this example. The example includes the configuration for Devices PE1 and PE2.

Configuration
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
Device PE1
Device PE2
Step-by-Step Procedure
To configure Device PE1:
Configure Device PE1 interfaces.
[edit interfaces]user@PE1# set ge-0/0/6 gigether-options 802.3ad ae0user@PE1# set ge-0/1/6 gigether-options 802.3ad ae0user@PE1# set ge-0/2/2 encapsulation ethernet-vplsuser@PE1# set ge-0/2/2 unit 0 family vplsuser@PE1# set ge-0/2/3 gigether-options 802.3ad ae0user@PE1# set ge-0/2/6 gigether-options 802.3ad ae0user@PE1# set ge-0/3/0 gigether-options 802.3ad ae0user@PE1# set ge-0/3/1 gigether-options 802.3ad ae0user@PE1# set ge-0/3/6 gigether-options 802.3ad ae0user@PE1# set ge-1/0/6 gigether-options 802.3ad ae0user@PE1# set ge-1/2/6 unit 0 family inet address 13.1.1.2/30user@PE1# set ae0 unit 0 family inet address 11.11.11.1/30user@PE1# set ae0 unit 0 family isouser@PE1# set ae0 unit 0 family mplsOn Device PE1, configure the packet header data to be used for per-flow load balancing.
[edit forwarding-options hash-key family multiservice]user@PE1# set source-macuser@PE1# set destination-macuser@PE1# set payload ip layer-3Configure the routing policy on Device PE1.
[edit policy-options]user@PE1# set policy-statement exp-to-fwd term a from community grn-comuser@PE1# set policy-statement exp-to-fwd term a then install-nexthop lsp PE1-to-PE2user@PE1# set policy-statement exp-to-fwd term a then acceptuser@PE1# set policy-options community grn-com members target:65000:1Configure Device PE1 routing protocols and MPLS.
[edit protocols]user@PE1# set rsvp interface alluser@PE1# set rsvp interface fxp0.0 disableuser@PE1# set mpls label-switched-path PE1-to-PE2 to 10.255.19.77user@PE1# set mpls label-switched-path PE1-to-PE3 to 10.255.19.79user@PE1# set mpls interface alluser@PE1# set mpls interface fxp0.0 disableuser@PE1# set bgp group int type internaluser@PE1# set bgp group int local-address 10.255.71.214user@PE1# set bgp group int family inet anyuser@PE1# set bgp group int family l2vpn signalinguser@PE1# set bgp group int neighbor 10.255.19.77user@PE1# set bgp group int neighbor 10.255.19.79user@PE1# set ospf traffic-engineeringuser@PE1# set ospf area 0.0.0.0 interface alluser@PE1# set ospf area 0.0.0.0 interface fxp0.0 disableConfigure VPLS on Device PE1.
[edit routing-instances vpls]user@PE1# set instance-type vplsuser@PE1# set interface ge-0/2/2.0user@PE1# set route-distinguisher 65000:1user@PE1# set vrf-target target:65000:1user@PE1# set protocols vpls site-range 3user@PE1# set protocols vpls no-tunnel-servicesuser@PE1# set protocols vpls site asia site-identifier 1user@PE1# set protocols vpls site asia interface ge-0/2/2.0user@PE1# set protocols vpls vpls-id 100user@PE1# set protocols vpls bum-hashing
Step-by-Step Procedure
To configure Device PE2:
Configure Device PE2 interfaces.
[edit interfaces]user@PE2# set ge-0/0/7 gigether-options 802.3ad ae0user@PE2# set ge-0/1/7 gigether-options 802.3ad ae0user@PE2# set ge-0/2/3 gigether-options 802.3ad ae0user@PE2# set ge-0/2/7 gigether-options 802.3ad ae0user@PE2# set ge-2/0/0 gigether-options 802.3ad ae1user@PE2# set ge-2/0/1 gigether-options 802.3ad ae1user@PE2# set ge-2/0/2 gigether-options 802.3ad ae1user@PE2# set ge-2/0/4 encapsulation ethernet-vplsuser@PE2# set ge-2/0/4 unit 0 family vplsuser@PE2# set ge-2/0/7 gigether-options 802.3ad ae0user@PE2# set ge-2/0/9 unit 0 family inet address 1.1.1.1/30user@PE2# set ge-2/0/9 unit 0 family mplsuser@PE2# set ge-2/1/7 gigether-options 802.3ad ae0user@PE2# set ge-2/2/7 gigether-options 802.3ad ae0user@PE2# set ge-2/3/7 gigether-options 802.3ad ae0user@PE2# set ae0 unit 0 family inet address 11.11.11.2/30user@PE2# set ae0 unit 0 family isouser@PE2# set ae0 unit 0 family mplsuser@PE2# set ae1 unit 0 family inet address 10.1.1.1/30user@PE2# set ae1 unit 0 family mplsConfigure Device PE2 routing protocols and MPLS.
[edit protocols]user@PE2# set rsvp interface alluser@PE2# set rsvp interface fxp0.0 disableuser@PE2# set mpls label-switched-path PE2-to-PE3 from 10.255.19.77user@PE2# set mpls label-switched-path PE2-to-PE3 to 10.255.19.79user@PE2# set mpls label-switched-path PE2-to-PE1 to 10.255.71.214user@PE2# set mpls interface alluser@PE2# set mpls interface fxp0.0 disableuser@PE2# set bgp group int type internaluser@PE2# set bgp group int local-address 10.255.19.77user@PE2# set bgp group int family inet anyuser@PE2# set bgp group int family l2vpn signalinguser@PE2# set bgp group int neighbor 10.255.71.214user@PE2# set bgp group int neighbor 10.255.19.79user@PE2# set ospf traffic-engineeringuser@PE2# set ospf area 0.0.0.0 interface lo0.0user@PE2# set ospf area 0.0.0.0 interface ge-2/0/0.0user@PE2# set ospf area 0.0.0.0 interface ge-2/0/1.0user@PE2# set ospf area 0.0.0.0 interface ge-2/0/2.0user@PE2# set ospf area 0.0.0.0 interface ae0.0user@PE2# set ospf area 0.0.0.0 interface ae1.0user@PE2# set ospf area 0.0.0.0 interface alluser@PE2# set ospf area 0.0.0.0 interface fxp0.0 disableuser@PE2# set ldp interface alluser@PE2# set ldp interface fxp0.0 disableConfigure VPLS on Device PE2.
[edit routing-instances vpls]user@PE2# set instance-type vplsuser@PE2# set interface ge-2/0/4.0user@PE2# set route-distinguisher 65000:1user@PE2# set vrf-target target:65000:1user@PE2# set protocols vpls site-range 3user@PE2# set protocols vpls no-tunnel-servicesuser@PE2# set protocols vpls site 2 site-identifier 2user@PE2# set protocols vpls site 2 interface ge-2/0/4.0user@PE2# set protocols vpls vpls-id 100user@PE2# set protocols vpls bum-hashing
Results
From configuration mode, confirm your configuration by issuing the show forwarding-options, show interfaces, show protocols, show policy-options, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Device PE1
Device PE2
Verification
You can monitor the operation of the routing instance by running the show interfaces ae1.0 extensive and monitor interface traffic commands.
For troubleshooting, you can configure tracing operations for all of the protocols.