Bonjour Dejean.
Yes you can and mriyaz's answer is quite complete.
QinQ with 2300-C is what we use here to dived 250 various sites into 20 groups so each group have access to vlans 1-4094. Everything works fine and is reliable.
I'll just add to mriyaz's answer the solution we came with when confronted with a particular issue.
3 groups have traffic going through their designated QinQ tags (3925,3926,3927) , but there was a requirement that they share a particular common vlan for ip phones because all 3 groups shared the same iphone server owned by one group.
After implementing mriaz solution, we changed it to "extract" vlan 3492 by changing the encapsulation from encapsulation extended vlan-bridge to flexible ethernet service on every switch needing access.
So config for port 0 went
**********from ************
set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation extended-vlan-bridge
set interfaces ge-0/0/0 unit 3925 vlan-id-list 1-4094
set interfaces ge-0/0/0 unit 3925 input-vlan-map push
**********to **************
set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation flexible-ethernet-services
set interfaces ge-0/0/0 unit 3492 vlan-id 3492
set interfaces ge-0/0/0 unit 3925 encapsulation vlan-bridge
set interfaces ge-0/0/0 unit 3925 vlan-id-list 1-3491
set interfaces ge-0/0/0 unit 3925 vlan-id-list 3493-4094
set interfaces ge-0/0/0 unit 3925 input-vlan-map push
set interfaces ge-0/0/0 unit 3925 output-vlan-map pop
================================================================
config port 11 (my port ge-0/0/11 = your port xe-0/1/0) went
**********from*****************
set interfaces ge-0/0/11 vlan-tagging
set interfaces ge-0/0/11 mtu 1538
set interfaces ge-0/0/11 unit 3925 vlan-id 3925
**********to ******************
set interfaces ge-0/0/11 vlan-tagging
set interfaces ge-0/0/11 mtu 1538
set interfaces ge-0/0/11 unit 3925 vlan-id 3925
set interfaces ge-0/0/11 unit 3492 vlan-id 3492
========================================================
and Vlans went
*********** from *************
set vlans QinQ-3925 interface ge-0/0/0.3925
set vlans QinQ-3925 interface ge-0/0/11.3925
*********to ***********
set vlans QinQ-3925 interface ge-0/0/0.3925
set vlans QinQ-3925 interface ge-0/0/11.3925
set vlans Telephonie-3492 interface ge-0/0/0.3492
set vlans Telephonie-3492 interface ge-0/0/11.3492
when trying the same thing and keeping encapsulation to extended-vlan-bridge, the configuration would commit, but no traffic would go through on 3492.
Please also note that we changed the mtu only on the interface carrying the double tagged frames.
Challenge was to implement ithe whole QinQ design on an existing network without affecting traffic. Coup;e of tricks had to be done. J
Also note that the show Ethernet-switching table will only show you the QnQ vlans, not the inside tag. Basically, you loose the vision of the client vlans going into QinQ.
It is not shown here, but I suggest you keep the storm-control default on all interface.
Good luck , and have fun !
__________________________________________
Michel Lapointe