I am driving myself crazy, this should be simple, what am I doing wrong? I want to trunk between a Cloud Core Router on ethernet4 (Bridge2) and a Cloud Core Switch Ethernet1.
On the CCR I did the following:
/interface vlan
add interface=bridge2-Trunk name=vlan2 vlan-id=2
add interface=bridge2-Trunk name=vlan3 vlan-id=3
add interface=bridge2-Trunk name=vlan4 vlan-id=4
Add bridge for VLANs
/interface bridge
add name=bridge2-Trunk
Add VLAN interfaces to the corresponding bridge
/interface bridge port
add bridge=bridge2-Trunk interface=ether4
add bridge=bridge2-Trunk interface=ether5
add bridge=bridge2-Trunk interface=ether6
On the Cloud Router/Switch I created the Vlans based on this example:
/interface ethernet
set ether2 master-port=ether1
set ether3 master-port=ether1
set ether4 master-port=ether1
Add initial VLAN assignments (PVID) to VLAN access ports.
/interface ethernet switch ingress-vlan-translation
add ports=ether2 customer-vid=0 new-customer-vid=2 sa-learning=yes
add ports=ether3 customer-vid=0 new-customer-vid=3 sa-learning=yes
add ports=ether4 customer-vid=0 new-customer-vid=4 sa-learning=yes
Add VLAN 2, VLAN 3 and VLAN 4 tagging on ether1 port to create it as VLAN trunk port. Egress-VLAN-Tag entry is mandatory for every VLAN to make VLAN access ports work. If VLAN trunk port has not been chosen yet, Egress-VLAN-Tag entry has to be added with tagged-ports=“”.
/interface ethernet switch egress-vlan-tag
add tagged-ports=ether2 vlan-id=2
add tagged-ports=ether3 vlan-id=3
add tagged-ports=ether4 vlan-id=4
VLAN membership definitions in the VLAN table are required for proper isolation. Adding entries with VLAN id and ports makes that VLAN traffic valid on those ports.
/interface ethernet switch vlan
add ports=ether1,ether2 vlan-id=2 learn=yes
add ports=ether1,ether3 vlan-id=3 learn=yes
add ports=ether1,ether4 vlan-id=4 learn=yes
No Luck, anyone see an issue?