Figure 123 shows a sample configuration scenario of an MPLS L2VPN or Martini tunnel over LAG. The topology is the same as the one described in MPLS L2VPN Tunnel over VLAN over LAG Configuration Example, with the exception of LAG bundles being used to transmit traffic from CE1 to PE1 instead of using a VLAN subinterface over a LAG bundle. Because the martini tunnel is configured directly over LAG in this case, only the source and destination MAC addresses are used in the hashing process to determine the physical link for forwarding the received packets.
Two LAG bundles, LAG1 and LAG2, are created to group multiple Ethernet interfaces from PE1 to CE1. A Martini tunnel from PE1 to PE2 is configured over LAG2 with a unique subinterface number assigned to the LAG bundle. The MPLS packets that are received on PE2, which is the remote router located at the other side of the service provider core, are checked to determine whether they need to be processed for MPLS labels. After PE2 processes the layer 2 Ethernet frames, they are sent to CE2, which is the customer edge device at the remote site.
Figure 123: MPLS L2VPN Tunnel over LAG Configuration Example
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |