[c-nsp] Cisco ASR 9k transporting QinQ traffic

[David Wilkinson]

We don't know what VLANs the customer is using within the QinQ.
I wonder if the 4948 is using 8100 for both the outer and inner tags, in 
which case using dot1ad wouldn't match. I will try with dot1q again.

Is "rewrite ingress tag pop [1|2] symmetrical" always required?
I thought it was only needed when you are waiting a layer 3 interface on 
on the bridge domain as the BVI doesn't support tagged packets.


On 14/07/2016 12:25, James Bensley wrote:
> Just a quick off-the-top-of-my-head response...
>
> Have you tried using (on the 9K):
>
> interface GigabitEthernet0/0/0/17.427 l2transport
>   encapsulation dot1q 427 second-dot1q ABC
>   ! and optionally
>   rewrite ingress tag pop [1|2] symmetrical
>
> Or if it is a range of C-VLANs "encapsulation dot1q 427 second-dot1q
> 10-50" ? This will assume both VLANs have Ethertype 8100.
>
> If you want to support 9100 or 9200 as the outter tag Ethertype then
> you need to set it on the physical interface:
>
> interface GigabitEthernet0/0/0/17
> dot1q tunneling ethertype [0x9100|0x9200]
>
> interface GigabitEthernet0/0/0/17.427 l2transport
>   encapsulation dot1q 427 second-dot1q ABC
>
>
> If you want Ethertype 88A8 on the outer tag you can use the following
> without anything on the main physical interface:
>
> interface GigabitEthernet0/0/0/17.427 l2transport
> encapsulation dot1ad 427second dot1q XXX
>
> Cheers,
> James.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/