jhtwu wrote:

jhtwu wrote:

visionmill wrote:
I have a 10gb fiber link to an outbuilding using SFP+ in both the 3910 and a Mikrotik 10gb switch (running SWOS). I've also tried this with a netgear 4250 with the same result

Vlan1 is untagged, vlan 2 and 3 are tagged on this link.

From a cold boot everything works correctly and will continue to work. If I turn off the Mikrotik over night and repower in the morning the link lights come on but I don't get any traffic / DHCP. A fast reboot of the 3910 doesn't fix the problem, but a normal reboot does. Rebooting the Mikrotik makes no difference.

I've just downloaded the logs and in the current, I have a lot of TX failed to port [4] .....failed ??? ret=0/1. I don't have anything connected to P4 on the 3910 - maybe that's something else and not related. Not sure what I would be looking for in the logs or if this is a 4.3.2 issue.

Seems not easy to identify the issue, I think it should be some bug of 3910 about vlan, you can call for DrayTek support with debug logs

Maybe you can check "Diagnostics >> ARP Cache Table", check if any wrong data for IP/MAC/VLAN/Port

visionmill wrote:

jhtwu wrote:

jhtwu wrote:


Seems not easy to identify the issue, I think it should be some bug of 3910 about vlan, you can call for DrayTek support with debug logs

Maybe you can check "Diagnostics >> ARP Cache Table", check if any wrong data for IP/MAC/VLAN/Port

Don't think anything is wrong in the ARP Cache.
Downgraded to 4.3.1 and there are no longer TX failed to port in the logs and the 10gbe link was restored fine this morning without having to reboot the 3910

service_bb wrote:
Corrected: An issue where an untagged PC got an IP from a network that had a VLAN tag.