Hi Anton,
Thank you for the answer.
Unfortunately that didin't work. During the commiting of your variant of configuration I've got the error:
A two tagged logical interface can not support push on input-vlan-map
And then I found out that according to https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/layer-2-services-vlans-and-vpls-routing-instances-configuring-vlan-ids-for-l2.html:
"Note: You cannot configure VLAN mapping using the input-vlan-map and output-vlan-map statements if you configure a normalizing VLAN identifier for a VLAN or VPLS routing instance using the vlan-id or vlan-tags statements."
The answer to your question is obvious - I have a lot of VLANs in my network and I have to pass through it a bunch of customer's VLANs with the same IDs as mine. I encapsulated C-VLANs (21-22 in this case) into S-VLAN 3174:
input-vlan-map {
push;
vlan-id 3174;
}
and I supposed it'd be sufficient to solve this task, - but it doesn't.. If a C-VLAN ID coinsides with a single-tagged VLAN ID which I use in my network, the traffic in a C-VLAN (encapsulated into an S-VLAN already) stops to run.
Kind regards.