Expand all | Collapse all

L2Circuit VLabs

Jump to Best Answer
  • 1.  L2Circuit VLabs

    Posted 07-07-2020 10:47

    Hi everyone.


    Please, I have the following configurations:


    CE01 (VMX)

    set interfaces ge-0/0/2 vlan-tagging
    set interfaces ge-0/0/2 unit 600 vlan-id 600
    set interfaces ge-0/0/2 unit 600 family inet address



    set interfaces ge-0/0/2 vlan-tagging
    set interfaces ge-0/0/2 encapsulation vlan-ccc
    set interfaces ge-0/0/2 unit 600 encapsulation vlan-ccc
    set interfaces ge-0/0/2 unit 600 vlan-id 600


    But I didn't get ping from CE01 - CE02.


    The connection L2circuit is ok:



    jcluser@vMX1> show l2circuit connections :

    Legend for interface status
    Up -- operational
    Dn -- down
    Interface Type St Time last up # Up trans
    ge-0/0/2.600(vc 5) rmt Up Jul 7 16:49:23 2020 1
    Remote PE:, Negotiated control-word: Yes (Null)
    Incoming label: 299808, Outgoing label: 299808
    Negotiated PW status TLV: No
    Local interface: ge-0/0/2.600, Status: Up, Encapsulation: VLAN
    Flow Label Transmit: No, Flow Label Receive: No


    Is support in VLabs this configuration?




  • 2.  RE: L2Circuit VLabs

    Posted 07-07-2020 13:34

    Hi aljob.luis,


    Greetings, can you try adding the following command, then do a ping specifying the source


    [edit interfaces]
    user@switch# set ge-0/0/2 unit 0 family ccc

    If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/


    Lil Dexx
    JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

  • 3.  RE: L2Circuit VLabs
    Best Answer

    Posted 07-07-2020 23:02

    Hi aljob.luis,


    Good day!!



    In Figure, a Layer 2 circuit is established between routers PE1 and PE2 to deliver Layer 2 traffic between customer routers CE1 and CE2. A Layer 2 circuit VC connection is configured on the PE routers only. No special configuration is required on the CE routers, and the provider core P0 router only requires MPLS and LDP on the appropriate interfaces to enable labels to be shared between the PE routers.

    On Router CE1, configure the Fast Ethernet interface to handle VLAN traffic. Be sure to use the same VLAN ID both here and on the Fast Ethernet interface of Router CE2.

    Router CE1



    interfaces {

    fe-1/1/2 {

    description "to PE1 fe-1/1/0";


    unit 600 {

    vlan-id 600; # Be sure this VLAN ID matches the VLAN ID of your CE neighbor.

    family inet {








    On Router PE1, configure the Ethernet-based CE-facing interface with the CCC encapsulation type of your choice. If you use VLAN CCC, include the vlan-tagging statement at the [edit interfaces ethernet-interface-fpc/pic/port] hierarchy level. Also, include the encapsulation vlan-ccc statement at both the [edit interfaces ethernet-interface-fpc/pic/port] and [edit interfaces ethernet-interface-fpc/pic/port unit unit-number] hierarchy levels.


    Establish your Layer 2 circuit with configuration of the l2circuit statement at the [edit protocols] hierarchy level. Remember to include in your Layer 2 circuit configuration the IP address of your remote PE neighbor (usually the loopback address of the neighbor), the interface connected to the CE router, and a virtual circuit identifier for this VC. Then, configure MPLS, LDP, and an IGP (such as OSPF) to enable signaling for your Layer 2 circuit.


    Please refer below document for better understanding.


    Ethernet-Based Layer 2 Circuit Configuration 


    CCC, TCC, and Layer 2.5 Switching Configuration 


    Please mark "Accepted Solution" if this helps you solve your query. Kudos are always appreciated.