Routing

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  L2circuit with QinQ

    Posted 06-26-2018 19:06
      |   view attached

    Hi All

     

    I have a problem about L2circuit with QinQ.

     

    I will connect from one switch of A to another switch of B via L2circuit with QinQ

    After referred to this website's example.  Still it always is shown no outgoing label.

    Neighbor: 103.198.146.2
           Interface                            Type  St     Time last up # Up t  rans
           ge-4/1/9.1012(vc 10012)   rmt    OL

     

     

    As follow is my structure diagram.

    螢幕快照 2018-06-27 上午10.07.44.pngAnd as attachment is my configuration. Can anyone give me some suggesstion how to modify it?

     

    Thanks

    Cloud 


    #l2circuit
    #QinQ

    Attachment(s)

    rtf
    L2curcuit sample.rtf   3 KB 1 version


  • 2.  RE: L2circuit with QinQ

    Posted 06-26-2018 21:56

    1) check if 173.198.146.2 and 172.54.131.10 present in inet.3 table
    2) check if session between these two MXs in operational state in "show ldp session"

     

    if session in 2nd option not present check your firewall on lo0.0 interface if traffic tcp port 646 is allowed for 173.198.146.2 and 172.54.131.10 .

     



  • 3.  RE: L2circuit with QinQ

    Posted 06-26-2018 22:22

    Hi 

     

    Many thanks for reminder.

    Yes, ldp session is not connecting ready . After modifed my firewall filter, it's up

     

    Router A> show ldp session
    Address State Connection Hold time Adv. Mode
    173.198.146.2 Connecting Opening 0 DU

     

    For QinQ, did I set up correctly ? I mean if customer have switches at two side for connecting to my routerA/B 

    Can use vlan-id 1012 for outer vlan ?

     

    Best regards,

    Cloud



  • 4.  RE: L2circuit with QinQ

    Posted 06-26-2018 22:58

    Yes, this configuration should work fine for QinQ



  • 5.  RE: L2circuit with QinQ

    Posted 06-26-2018 22:25

    Did you configure loopback 0 under LDP?

     

     



  • 6.  RE: L2circuit with QinQ

    Posted 06-26-2018 22:49

    Hi Kingsman

     

    Yes, my lo have joined into OSPF and LDP.

     

    Now L2circuit connection is up as follow.

    Neighbor: 173.198.146.2
    Interface Type St Time last up # Up trans
    ge-4/1/9.1012(vc 10012) rmt Up Jun 27 12:31:14 2018 1
    Remote PE: 173.198.146.2, Negotiated control-word: Yes (Null)
    Incoming label: 302176, Outgoing label: 302464
    Negotiated PW status TLV: Yes
    local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
    Local interface: ge-4/1/9.1012, Status: Up, Encapsulation: ETHERNET
    Flow Label Transmit: No, Flow Label Receive: No

     

    But i just confuse how to make sure QinQ working and verify it.

    I hope to set vlan 1012 for cross MPLS backbone. Then will be swapped to origin vlans.

     

    Cloud 



  • 7.  RE: L2circuit with QinQ

    Posted 06-26-2018 22:59

    from your current configuration, you the poping the vlan on incoming traffic and sending it out over l2circuit and pushing it again while sending it put to remote CE.

     

    root@mx480# run show interfaces ge-4/1/1.1012 extensive
    Logical interface ge-4/1/1.1012 (Index 370) (SNMP ifIndex 535) (Generation 179)
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1012 ] In(pop) Out(push 0x8100.1012) Encapsulation: VLAN-CCC
    Traffic statistics:
    Input bytes : 0

     

    if this is what you want then you are good. 



  • 8.  RE: L2circuit with QinQ

    Posted 06-27-2018 00:52

    Hi All

     

    BTW, how to set up the port of switch connectiing to my router ?

    If customer's vlan id is 1234, my router will pop 1234 and push 1012 for cross L2vpn, right ?

     

    thanks for your reply

     

    Best regards,

    Cloud



  • 9.  RE: L2circuit with QinQ
    Best Answer

    Posted 06-27-2018 12:06

    Hi,

     

    Please refer to the below document 

     

    Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface

     

    [KUDOS PLEASE! If you think I earned it!

    If this solution worked for you please flag my post as an "Accepted Solution" so others can benefit..]