Switching

Dear Experts,

I configured QinQ on two EX4200 switches. Both the switches are connected with each other via an EtherChannel. Etherchannel interface is a trunk & I added the qinq vlan on it too. While committing, it gives following error. Can't I transport qinq vlan alongwith other normal vlans over an Etherchannel?

|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Hi,

Pl configure the dot1q tunneling ether-type as 0x8100.

#set ethernet-switching-options dot1q-tunneling ether-type 0x8100

Note:

Note that Q-in-Q tunneling does not support most access port security features. There is no per-VLAN
(customer) policing or per-VLAN (outgoing) shaping and limiting with Q-in-Q tunneling unless you
configure these security features using firewall filters. For more information, refer to the technical
publications for your specific product. If Q-in-Q tunneling is configured, you will need to enable Q-in-Q
tunneling on all VLANs serviced by the trunk ports or alternatively change the Ethernet-type setting
as shown in the following sample output:
[edit]
user@switch# commit
error: Trunk interface <ge-0/0/10.0> can not be member of both dot1q-tunneling
enabled vlan <cust-1>, and a non dot1q-tunneled vlan <v11> when dot1q-tunneling
ethernet-type is not <0x8100>
error: configuration check-out failed

Dear ! with ox8100, how am I going to do QinQ? .... ox8100 means that the port will be accepting tagged packet while for QinQ the client end port is configured in access mode.

Not to despair! You will continue to learn the power of Juniper. Offer you multiple ways of achieving same goal and this is no different.

When enabling dot1q tunneling, the inner ether-type VLAN tag (C-TAG) uses the TPID value of 0x8100 while the outer ether-type VLAN tag (S-VLAN) uses the TPID value of 0x88A8. By default, a standard trunk interface understands the 0x8100 format and will not understand how to process a VLAN tag with the TPID value of 0x88A8. Because of this behavior, you must EITHER enable dot1q tunneling on all trunk interfaces that will be passing the S-VLAN tag OR you can set the dot1q tunneling VLAN tags to use the TPID value of 0x8100 by manually defining the dot1q tunneling ether-type value under the
[edit ethernet-switching-options] set dot1q-tunneling ether-type 0x8100. One or the other.

There is an awesome learning-byte that also illustrates Q-in-Q and it is awesome. Check it out.

https://learningportal.juniper.net/juniper/user_activity_info.aspx?id=5853

Thanks Lyndidon for help! Below is the working configuration from one of the switches.

ge-0/0/24 {

        unit 0 {

            family ethernet-switching {

                port-mode access;

            }

        }

    }

............................................

vlans

...................................................

ethernet-switching-options {

    dot1q-tunneling {

        ether-type 0x8100;

    }

    storm-control {

        interface all;

    }

}