I have a client that has an HP1810 l2 switch. I am installing a MicroTik 1100AH and it will be a router as well as an L3 switch. I believe I have configured the Mikrotik correctly but I cant seem to get the trunking port setup correctly between the MT and the HP switch.
Has anyone had any experience in setting up a trunk port between the MT and an HP switch?
What seems to be the problem? We have RB1100AHx2 connected to the HP Procurve 1800 via 802.3ad. Works as intended on RoS 5.25 here.
I have port5 on the HP set as a trunk port which is plugged into port1 on the MT, but I cant seem to ping the MT from the HP Switch. I am pinging it from the native vlan. Same config on a cisco switch works fine.
Native vlan is 21
/interface bridge
add l2mtu=1594 name=bridge-native
add l2mtu=1594 name=bridge-phones
add l2mtu=1594 name=bridge-workstations
add l2mtu=1594 name=bridge-san
add l2mtu=1594 name=bridge-lab
add l2mtu=1594 name=bridge-public
add l2mtu=1594 name=bridge-misc
/interface vlan
add interface=ether1 l2mtu=1594 name=vlan-workstations vlan-id=30
add interface=ether1 l2mtu=1594 name=vlan-native vlan-id=21
add interface=ether1 l2mtu=1594 name=vlan-phones vlan-id=10
add interface=ether1 l2mtu=1594 name=vlan-san vlan-id=20
add interface=ether1 l2mtu=1594 name=vlan-lab vlan-id=40
add interface=ether1 l2mtu=1594 name=vlan-public vlan-id=50
add interface=ether1 l2mtu=1594 name=vlan-misc vlan-id=60
add interface=ether2 l2mtu=1594 name=vlan-misc vlan-id=21
add interface=ether3 l2mtu=1594 name=vlan-misc vlan-id=21
add interface=ether4 l2mtu=1594 name=vlan-misc vlan-id=30
add interface=ether5 l2mtu=1594 name=vlan-misc vlan-id=30
add interface=ether7 l2mtu=1594 name=vlan-misc vlan-id=30
add interface=ether7 l2mtu=1594 name=vlan-misc vlan-id=60
/interface bridge port
add bridge=bridge-native interface=vlan-native
add bridge=bridge-phones interface=vlan-phones
add bridge=bridge-workstations interface=vlan-workstations
add bridge=bridge-san interface=vlan-san
add bridge=bridge-lab interface=vlan-lab
add bridge=bridge-public interface=vlan-public
add bridge=bridge-misc interface=vlan-misc
/ip address
add address=10.105.21.197/24 interface=bridge-native
add address=10.105.10.197/24 interface=bridge-phones
add address=10.105.30.197/24 interface=bridge-workstations
add address=10.105.20.197/24 interface=bridge-san
add address=10.105.40.197/24 interface=bridge-lab
add address=10.105.50.197/24 interface=bridge-public
add address=10.105.60.197/24 interface=bridge-misc
/ip dns
set allow-remote-requests=yes
In a popular brazillian mailing list (called GTER) I saw recently a guy complaining about a HP L2 switch that was deliberatly removing the VLAN tag from the passing packets. He contacted HP support and the response he got was something like: “If you want to use VLAN, you should buy a manageable switch that has VLAN support”. So it seems to me HP have implemented this anti-feature.
This part seems a bit odd.
You can’t create multiple interfaces with the same name.
So if you put the config in a script, it won’t fully load.
First make sure that each VLAN interface has a unique name.
Afterwards you should put all relevant VLAN interfaces into the correct bridge.
On the other hand, if the traffic flowing into the ether interfaces is untagged, and you want it to be tagged when leaving the trunk port, just put the ether interface into a bridge and put the desired VLAN interface of the trunk port into the same bridge.