Hello,
I would like to use a CCRS212-1G-10S-1S+IN to convert SFP to DWDM SFP without affecting the traffic including VLANs, cost and DSCP (just like 5 unmanaged switchs 2 ports unmanaged) and I think the best way to do this would be via QinQ, to add a S-VLAN on one port and remove it on the other.
Exemple:
SFP1 ingress add SVID 101 / egress remove SVID 101
SFP2 ingress add SVID 101 / egress remove SVID 101
SFP3 ingress add SVID 102 / egress remove SVID 102
SFP4 ingress add SVID 102 / egress remove SVID 102
SFP5 ingress add SVID 103 / egress remove SVID 103
SFP6 ingress add SVID 103 / egress remove SVID 103
SFP7 ingress add SVID 104 / egress remove SVID 104
SFP8 ingress add SVID 104 / egress remove SVID 104
SFP9 ingress add SVID 105 / egress remove SVID 105
SFP10 ingress add SVID 105 / egress remove SVID 105
So I look at the following exemple:
http://wiki.mikrotik.com/wiki/Manual:CRS_examples#VLAN_Tunneling_.28Q-in-Q.29
I try to figure out how I can configure this and the only thing that come to my mind is this:
/interface ethernet switch ingress-vlan-translation add new-service-vid=101 ports=sfp1-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=101 ports=sfp2-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=102 ports=sfp3-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=102 ports=sfp4-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=103 ports=sfp5-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=103 ports=sfp6-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=104 ports=sfp7-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=104 ports=sfp8-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=105 ports=sfp9-slave-local sa-learning=yes
/interface ethernet switch ingress-vlan-translation add new-service-vid=105 ports=sfp10-slave-local sa-learning=yes
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp1-slave-local vlan-id=101
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp2-slave-local vlan-id=101
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp1-slave-local vlan-id=102
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp2-slave-local vlan-id=102
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp1-slave-local vlan-id=103
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp2-slave-local vlan-id=103
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp1-slave-local vlan-id=104
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp2-slave-local vlan-id=104
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp1-slave-local vlan-id=105
/interface ethernet switch egress-vlan-tag add tagged-ports=sfp2-slave-local vlan-id=105
but a second egress ports for the same vlan id is refuse with this error:
failure: already have such switch egress vlan tag entry
Is the’re a other way to confiugre this ? Why a single egress ports by SVID ? A limitation of the switch ? Something I got wrong ?
Thanks
