mpls
mpls ldp
interface atm 2/1.2
atm pvc 2 1 12 aal5snap
ip address 10.10.12.5 255.255.255.0
ip router isis
mpls
mpls ldp
router isis
net 47.0005.80FF.F800.0000.0000.0004.0000.F209.0505.00
mpls traffic-eng router-id loopback 0
mpls traffic-eng level-1
metric-style wide
!--------------------------------------------------------------------------
!Create MPLS tunnel from VR three to VR two. Route Frame Relay traffic via MPLS
tunnel.
!--------------------------------------------------------------------------
vir three
interface tunnel mpls:3
tunnel destination 222.9.1.2
interface serial 4/1:2/1.1
route interface tunnel mpls:3 45
vir two
interface tunnel mpls:2
tunnel destination 222.9.1.3
int ser 4/1:1/1.1
route interface tunnel mpls:2 45
Example: Configuring MPLS L2VPN Tunnel over VLAN over LAG
Figure 122 on page 547 shows a sample configuration scenario of an MPLS L2VPN or Martini
tunnel over VLAN over LAG. The sample topology shows a customer edge router, CE1,
connected to a provider edge router, PE1 using a stacked VLAN (S-VLAN) tunnel.
Two LAG bundles, LAG1 and LAG2, are created to group multiple Ethernet interfaces on
CE1 and PE1 respectively. 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 processed. After PE2 processes the layer 2 Ethernet frames, they are sent to
CE2, which is the customer edge device at the remote site.
Copyright © 2010, Juniper Networks, Inc.546
JunosE 11.2.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
