Possible bug in bonding v3.30?

Hi folks.

I’m creating some practice labs with my mkt 433AH and a cisco switch (c2950).
In this lab I was enabling 802.3ad between this devices connected like this:

[MKT] [2950]
Ether1 ------- f0/4
Ether2 ------- f0/5

The 433 was provisioned with a “system reset-config” before this test.

[admin@MikroTik] /interface bonding> export

jan/02/1970 00:32:20 by RouterOS 3.30

/interface bonding
add arp=enabled arp-interval=100ms comment=“” disabled=no down-delay=0s
lacp-rate=30secs link-monitoring=none mii-interval=100ms mode=802.3ad
mtu=1500 name=bonding1 primary=none slaves=ether1,ether2
transmit-hash-policy=layer-2 up-delay=0s

And in the cisco:
!
lacp system-priority 40960
!
interface Port-channel1
switchport access vlan 90
switchport mode access
flowcontrol send off
!
interface FastEthernet0/4
switchport access vlan 90
switchport mode access
load-interval 30
no cdp enable
channel-group 1 mode passive
channel-protocol lacp
spanning-tree portfast
!
interface FastEthernet0/5
switchport access vlan 90
switchport mode access
load-interval 30
no cdp enable
channel-group 1 mode passive
channel-protocol lacp
spanning-tree portfast
!

So, the “bug” seems to be when I put a comment over the bonding interface, the whole bonding goes down and the link-aggregation needs to be negotiated again between the devices. The same problem appears when the name of the bonding interface changes (this could be acceptable, but not when I’m placing coments).

Best regards

Ariel Weher

how do you change comment? CLI, WinBox?

Winbox.

Regards

try to do that with CLI - maybe WinBox sends update notification not only on comment, so router thinks he should re-establish bonding with new parameters

I’ll try it.

Anyway, I can live without adding a comment to a bonding.
The post was entirely made to warn about the bug so it can be fixed in future releases.

Thanks for your feedback.