Routing
Routing

Q-IN-Q Config Queston

‎02-14-2019 03:22 PM

I'm doing some basic Q-in-Q over a provider's network and had some questions around the different nobs for QinQ on the MX.

Goal is to add a new tag which will pass over the providers network, and keep my inner tag.  So this is the most simple config i have working:

 

root@MX1>show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.3/31;
    }
}

and on the other side:

root@MX2> show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.2/31;
    }
}

So this works fine.  the provider is expecting vlan35 and i have connectivity between my two devices across their network.

 

however, this config also works:

 

root@MX1>show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map push;
output-vlan-map pop;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.3/31;
    }
}



root@MX2> show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map push;
output-vlan-map pop;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.2/31;
    }
}

as does this:

 

root@MX1>show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map pop;
output-vlan-map push;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.3/31;
    }
}



root@MX2> show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map pop;
output-vlan-map push;
unit 12 {
    vlan-tags outer 35 inner 12;
    family inet {
        address 10.100.0.2/31;
    }
}

 as does this:

 

root@MX2> show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map pop;
output-vlan-map push;
unit 12 {
vlan-tags outer 35 inner 12;
input-vlan-map {
    push;
    vlan-id 35;
}
output-vlan-map {
    pop;
    inner-vlan-id 12;
}
family inet {
    address 10.100.0.2/31;
}

soooooo... which is the correct way?

6 REPLIES 6
Routing

Re: Q-IN-Q Config Queston

‎02-14-2019 05:14 PM

Hi rclimson!

 

This #JNPRAmbassador Insights article on Q-in-Q tunneling may help a bit... although not entirely the same issue as yours...

 

@paulclarke , can you help here?

 

- Jeremiah

J-Net Community Manager

Jeremiah
J-Net Community Manager
Routing

Re: Q-IN-Q Config Queston

‎02-14-2019 09:30 PM
Routing

Re: Q-IN-Q Config Queston

‎02-15-2019 01:03 AM

Hello,

"input-vlan-map" and "output-vlan-map" are not supported under physical interface, only under unit

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/input-vla...

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/output-vl...

So every config You posted that have "input-vlan-map"|"output-vlan-map" under ge-0/0/0, are invalid and I doubt that You actually saw then working - I was not able to commit any of Your configs EXCEPT the very first one on my lab router JUNOS 18.4R1.

But if we remove "input-vlan-map"|"output-vlan-map" from under ge-0/0/0, this leaves us with identical configs EXCEPT the very last one:

 

root@MX2> show configuration interfaces ge-0/0/0  
flexible-vlan-tagging;
input-vlan-map pop;
output-vlan-map push;
unit 12 {
vlan-tags outer 35 inner 12;
input-vlan-map {
    push;
    vlan-id 35;
}
output-vlan-map {
    pop;
    inner-vlan-id 12;
}
family inet {
    address 10.100.0.2/31;
}

 

This one I was able to commit and the operation it produces can be seen in "show interfaces ge-0/0/0" printout:

 

  Logical interface ge-0/0/0.12 (Index 336) (SNMP ifIndex 553)
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.35 0x8100.12 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 1                   

And this operation is identical to what Your very first config produces.

What this operation means in plain English is - when the frame with Ethertype 0x8100 and tags 35 + 12 comes into ge-0/0/0, the Ethertype & tags are stripped and underlying packet is checked for being IPv4. If not, then this frame is discarded with the reason "L3-incomplete". If yes, the IPv4 packet assuming it is routable (ttl>1, dst.Ip is not martian, etc) is routed further.

inference - use the very first config as it achieves desired result with less lines.

Hope this makes sense.

HTH

Thx
Alex

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Routing

Re: Q-IN-Q Config Queston

‎02-15-2019 01:40 PM

Thanks for the input.

 

would same configuration work on a QFX5100?  E.g. would the 

vlan-tags outer 35 inner 12

can QFX do that?

Routing

Re: Q-IN-Q Config Queston

‎02-15-2019 07:59 PM

Hello there,

Yes it can.

HTH

Thx

Alex

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Routing

Re: Q-IN-Q Config Queston

‎02-17-2019 10:19 AM

acording to https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/vlan-double-tagging-with... the outer and inner commands on a QFX should work.  However i have been able to actually make it work at all.

 

JTAC have said it is actually not supported and have escaled it to engineering... curious if anyone is able to get double tagging + logical L3 interface working on a QFX5100 as described in the link above