Community discussions

MikroTik App
 
speedy
just joined
Topic Author
Posts: 4
Joined: Fri May 25, 2018 11:38 am

CRS328-24P-4S+RM LACP (802.3ad) Problem

Sat May 26, 2018 6:53 pm

I recently got a CRS328-24P-4S+RM, and have come across a very strange issue.

When I setup an LACP (802.3ad) bonding it works for some time and then suddenly stop forwarding some traffic.
I am using the latest stable RouterOS version 6.42.3, with all ports added to bridge and doing the vlan management there.
The bonding port (2x10G SFP+) is using vlan tagging, while the 1G test port I used was untagged.
The hw. offload is working on all ports, including the bonding interface.

I used this device 3-4 days with bonding, until I had to disconnect it from the network because of this traffic flow problem. Had to reboot it every day to keep traffic running.

I have done some iperf3 tests through the bonding interface which is 2x10G DAC SFP+, and into a single 1G port, it runs fine for around 18-19 hrs, then a port flap on one of the SFP+ ports happend (down/up), And shortly after, the traffic isn't flowing through anymore to the machine on the 1G port. It is not all traffic that just stops, as I can still manage the device through Winbox. Which is done on a bridge vlan on the bonded interface.

I did the same iperf3 test with the same 1G port, same SFP+ port, same cable, same machines just without bonding, and then it keeps running without problems.

There are no errors in the log or any other indication that it has run into a problem. So I suspect it is some kind of sw/hw bug.

After this problem I removed the bonding and just used one of the SFP+ ports, and have had no problem since, I use the same SFP+ port that did the flap, but without bonding it does not flap.
I have used sw LACP bonding (802.3ad) on routers with RouterOS for many years without any problems.

I would very much like to use the LACP hw bonding (802.3ad) function, so does anyone else have noticed this problem on these switches ?
You do not have the required permissions to view the files attached to this post.