Connection drop every 60 sec (or random at load) on link (with VLAN)
Posted: Wed Apr 26, 2017 4:15 pm
Hi everbody,
I have a problem with 2 mikrotiks, the 2011UiAS and the 3011UiAS.
We have 2 datacenters that is connected with an NDIX, previously we used a sophos UTM to bridge the datacenters but we wanted to lower the load on the Sophos UTM.
So we have placed mikrotiks instead with the routing tables in place, except i`m getting a connection drop every 60 seconds, this problem was not present when using the Sophos UTM.
Router is in bridge mode, I have used the following commands to create the vlans on ether5;
/interface vlan add name=vlan-2667 vlan-id=2667 interface=ether5 disabled=no
/interface bridge add name=br-vlan2667 disabled=no
/interface bridge port add interface=vlan-2667 bridge="br-vlan2667" disabled=no
/interface bridge port add interface=ether5 bridge="br-vlan2667" disabled=no
After that I created the routing table so that the other networks are routed.
I`m using the latest firmware available, also tried the beta without any results.
What could be causing this issue?
I have a problem with 2 mikrotiks, the 2011UiAS and the 3011UiAS.
We have 2 datacenters that is connected with an NDIX, previously we used a sophos UTM to bridge the datacenters but we wanted to lower the load on the Sophos UTM.
So we have placed mikrotiks instead with the routing tables in place, except i`m getting a connection drop every 60 seconds, this problem was not present when using the Sophos UTM.
Router is in bridge mode, I have used the following commands to create the vlans on ether5;
/interface vlan add name=vlan-2667 vlan-id=2667 interface=ether5 disabled=no
/interface bridge add name=br-vlan2667 disabled=no
/interface bridge port add interface=vlan-2667 bridge="br-vlan2667" disabled=no
/interface bridge port add interface=ether5 bridge="br-vlan2667" disabled=no
After that I created the routing table so that the other networks are routed.
I`m using the latest firmware available, also tried the beta without any results.
What could be causing this issue?