So in first part of post spf1 is under tagged for vlan 1005 but in later output it is under untagged. It should be under untagged and PVID for the port is correct.
Can you do a full export under interface bridge?

So having a quick look while between meetings :) I can see that SFP1 is currently specified as a Tragged only port

Code: Select all

add bridge=BR1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=sfp1

You need to change this to

Code: Select all

add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=sfp1 pvid=1005

This sfp1 port has been repurposed to connect a data server with a new 10G interface.
OK. I see you use the "add" command rather than the "set" command. I thought that as sfp1 was already added to the bridge as a tagged trunk port, that in order to CHANGE the configuration I needed to use the "set" command to modify it. Is that also possible? Which is best?
Would the following also have done the same job by modifying the vlan table to have sfp2 as the only tagged port on all vlans (trunk)?

Code: Select all

/interface bridge vlan
set vlan-ids=22 tagged=sfp2
set vlan-ids=1005 tagged=sfp2
set vlan-ids=1030 tagged=sfp2
set vlan-ids=1006 tagged=sfp2
set vlan-ids=1015 tagged=sfp2

Then configure sfp1 as an access port on 1005:

Code: Select all

/interface bridge port
set bridge=BR1 interface=sfp1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes pvid=1005

I suppose my remaining questions are is, first what is the difference between using "set" and "add" when REconfiguring (not initial conifuration) and, second is my code suggestion correct?
Really appreciate your input as it means I can finally open up this 10G route to the server.

Generally I find it best not to include any untagged= membership entries under /interface bridge vlan as they will be dynamically added when interfaces are running/up based on the pvid= entries under /interface bridge port. If the untagged membership entries are present you have to remember to update both when changing PVID or weird connectivity issues may result.

I don't think you can change VLAN membership by interface as the configuration entries are indexed by VLAN IDs, so [ find interface=sfp1 ] has no meaning in this context. You would likely have to use [ find vlan-id=XX ] for each VLAN ID and change the membership from some-interface,sfp1,another-interface to some-interface,another-interface. Somone with a more in-depth knowledge of RouterOS scripting may be able to suggest a set of commands which would loop through all bridge VLAN definitions using regexp to match and update the membership for the interface of interest.