Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

How to configure MPLS L2VPN on EX Series Switches

0

0

Article ID: KB14930 KB Last Updated: 20 Aug 2009Version: 1.0
Summary:
MPLS L2VPN provides Layer 2 VPN services on the MPLS network.  It allows carriers to establish L2VPNs on different data link layer protocols, including ATM, FR, VLAN, Ethernet and PPP.

The information below describes the configuration steps to create Circuit Cross Connect (CCC aka Kompella draft) over MPLS network
Symptoms:

Solution:
The information below describes the configuration steps to create Circuit Cross Connect (CCC aka Kompella draft) over 3 switches in the MPLS network topology.

TOPOLOGY:



  • pe-1 and pe-2 are customer edge (EX switches)
  • pe-1 and pe-2 has 1 core interfaces each, ge-5 and ae0 respectively
  • pe-1 and pe-2 has 1 customer facing interfaces each, which is ge-1
  • p-1 is the transit router

pe-1 Interface Configuration:

pe-1# show configuration
interfaces {
ge-0/0/1 {
unit 0 {
family ccc;
}
}
ge-0/0/5 {
unit 0 {
family inet {
address 4.4.4.2/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 1.1.1.1/32
}
}
}
}

pe-1 Protocol Configuration (PSVP and MPLS):
pe-1# show configurations
protocols {
rsvp {
interface ge-0/0/5.0;
interface lo0.0;
}
} mpls {
label-switched-path lsp_to_pe2_ge2 {
to 3.3.3.3;
}
interface ge-0/0/5.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/5.0;
interface lo0.0;
}
} connections {
remote-interface-switch xcon_ge2-to-pe2 {
interface ge-0/0/1.0;
transmit-lsp lsp_to_pe2_ge2;
receive-lsp lsp_to_pe1_ge1;
}
}
}


P-1 is the transit router with no customer facing interfaces:

p-1# show confiugurations
protocols {
rsvp {
interface ge-0/0/5.0;
interface ae0.0;
interface lo0.0;
}
}
mpls {
interface ge-0/0/5.0;
interface ae0.0;
} ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/5.0;
interface ae0.0;
interface lo0.0;
}
}
}

PE-2 has ge-2 interface towards the customer:

pe-2# show configuration
protocols {
rsvp {
interface ae0.0;
interface lo0.0;
}
} mpls {
label-switched-path lsp_to_pe1_ge1 {
to 1.1.1.1;
}
interface ae0.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ae0.0;
interface lo0.0;
}
} connections {
remote-interface-switch xcon_ge-1-to-pe1 {
interface ge-0/0/1.0;
transmit-lsp lsp_to_pe1_ge1;
receive-lsp lsp_to_pe2_ge2;
}
}
}

NOTE: Packets with destination of ge-2 in this application will go through the switch labeled path between PE-1 and PE-2


MPLS Show Commands:

  • show mpls interface
  • show route forwarding-table family mpls
  • show connections brief
  • show connections
  • show connections label
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search