Netonix Forums

We recently decided to create a LAG between the switch and our routers following some suggestions found here in the forums. Ever since we have been getting bombarded with:


LACP changed state to Active on port 1 (key 100) - from xxxxx-net-00 (xx.xx.xx.xx) .

And sometimes it will be port 2 (the other in the LAG group).

The switches are WS-24-400A and running firmware version 1.3.7 on both sides. They are connecting at both locations to a Mikrotik CCR1009-8G-1S running firmware 6.32.3 on them. The configuration at the switch is pretty simple: both ports enabled, key = 100, role - LACP-A, timeout = Fast, Priority = 32768.

On the Mikrotik we have created a bonding interface, MTU = 1500, mode = 802.03ad, transmit hash policy = layer 2 and layer 3, LACP rate = 1s, MII Interval = 100.

While it appears to be performing OK (we will find out more this evening) it is FLOODING my inbox.

Thoughts or suggestions? Thanks!

When you have an issue please upgrade to the latest stable version and it is always a good idea to review the release notes on any new releases including RV versions.

Please upgrade to v1.3.9rc13 and see if you still have an issue.

Release notes for v1.3.9rcX:
viewtopic.php?f=17&t=1232#p9169

Download latest firmware here:
viewtopic.php?f=17&t=240

v1.3.9rc6 - Released 12/02/2015
- Fixed Loop protection log entry refers to wrong port number
- Fixed Broadcast storm when using LACP and RSTP [Discovered by Thomas]
- Fixed Unable to change RSTP path cost for LAGs

I am NOT using RSTP on these switches and prefer NOT to use a RC firmware on production servers.

lweidig wrote:I am NOT using RSTP on these switches and prefer NOT to use a RC firmware on production servers.

There were changes to LACP to accommodate this, however v1.3.9rc13 is about to go final, I am running it at all my towers.

v1.3.7 is closed so if there is a bug in it we would not address it with a new v1.3.7 release.

v1.3.8 is also closed and would not address it in a new v1.3.8 release.

v1.3.9 is the current thread and it is about to be finalized but even if you find a bug in an older version and was not fixed already in the current version or RC version it would only be addressed in v1.3.9

All I am saying is if you find a bug in an older firmware you should first try the latest code to see if the bug is there then if it is open a support thread here.

I did put this RC on over night and it does seem to have resolved the issue. Thanks!