[j-nsp] R: Re: QinQ interface configuration question

[dim0sal]

I meant having two subinterfaces with the four prospected scenarios.

Tks





-------- Messaggio originale --------
Da: sthaug at nethelp.no 
Data:  
A: dim0sal at hotmail.com 
Cc: juniper-nsp at puck.nether.net 
Oggetto: Re: [j-nsp] QinQ interface configuration question 
 
> I'm wondering if under a QinQ interface configuration it's accepted by the MX the same SVLAN (outer vlan) or the commit will fail.
> 
> The PE QinQ interface prospect configuration scenarios are:
> 
> 1) different SVLAN and CVLAN
> 2) different SVLAN and same CVLAN
> 3) same SVLAN and different CVLAN
> 4) same SVLAN and CVLAN
> 
> I'm sure 1) and 2) are accepted, not sure about 3) and 4).

Not 100% sure what you mean by the different examples, but let's try:

1) different SVLAN and CVLAN

vlan-tags outer a inner x

No problem.

2) different SVLAN and same CVLAN

vlan-tags outer a inner x
and
vlan-tags outer a inner y

No problem.

3) same SVLAN and different CVLAN

vlan-tags outer a inner x
and
vlan-tags outer b inner x

No problem.

4) same SVLAN and CVLAN

vlan-tags outer a inner a

No problem. We have this in production.

Regarding the comment in a different reply, "Having the same inner and
outer tag means there is no way to differentiate between the incoming
frames" - I'm afraid I don't see the problem. You lookup the outer
VLAN tag and then you lookup the inner VLAN tag.

Steinar Haug, Nethelp consulting, sthaug at nethelp.no