I’ve seen a curious problem… When I change the comment of a Trunk interface, or to any of the VLAN or VRRP interfaces which depend on it, the whole trunk stops responding (no ping, no traffic, I can’t even get the MAC address of the iface). The serial console gives some more information:
Then, when I disable the trunk interface, I get this messages and the trunk is NOT disabled… I can’t issue any command related to interfaces (print, enable, etc…):
bonding: bond0: Removing slave eth0
bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:0c:42:2e:b5:11 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
bonding: bond0: releasing active interface eth0
eth0: stop
eth0: open
eth0: phy speed: 100, fdx: 1
bonding: bond0: Removing slave eth1
bonding: bond0: Removing an active aggregator
bonding: bond0: releasing active interface eth1
bonding: bond0: Warning: clearing HW address of bond0 while it still has VLANs.
bonding: bond0: When re-adding slaves, make sure the bond's HW address matches its VLANs'.
bonding: bond0 is being deleted...
unregister_netdevice: waiting for vlan10 to become free. Usage count = 2
unregister_netdevice: waiting for vlan10 to become free. Usage count = 2
unregister_netdevice: waiting for vlan10 to become free. Usage count = 2
Then, I’m forced to restart the whole router from the serial console. I’ve tried with 3.22 and 3.23 with the same results.
I can reenable the iface, but I get no traffic at all through it and this dump is generated:
bonding: bond0 is being deleted...
bonding: bond0 is being created...
bonding: bond0: setting mode to 802.3ad (4).
bonding: bond0: Unable to set up delay as MII monitoring is disabled
bonding: bond0: Unable to set down delay as MII monitoring is disabled
bonding: bond0: Setting LACP rate to fast (1).
bonding: bond0: setting xmit hash policy to layer2 (0).
eth0: stop
bonding: bond0: Adding slave eth0.
eth0: open
eth0: phy speed: 100, fdx: 1
bonding: bond0: enslaving eth0 as a backup interface with an up link.
bonding: bond0: Adding slave eth1.
bonding: bond0: enslaving eth1 as a backup interface with an up link.
vrrp: add vrrp1 24 1
vrrp: vrrp1 owns vlan8
vrrp: register_netdev failed
vrrp: open vrrp1
vrrp: slave lost
vrrp: add vrrp0 25 2
vrrp: vrrp0 owns vlan10
vrrp: register_netdev failed
vrrp: open vrrp0
vrrp: slave lost
I must restart the router to get it working… but then, all the VRRP ifaces are shown in red, as if they had an error. To solve that, I have to disable the trunk and then reenable it again. Now I don’t get the error messages shown above and the trunk is disabled and reenabled correctly.
What’s going on with the trunking feature? Is it mature enough to be used in a production environment?
at this moment all of this information is completely useless because of few simple things:
1st - at start you did not provide what arch and hardware you are using
2nd - you do not state - what version you are using
3rd - what RouterBOOT version you are using
4th - on what version you have noticed the problem
5th - have you contacted support with supout.rif file attached from problematic routers. if not - upgrade to latest version of routers, see, if you still have the problem, create supout.rif file and contact support at mikrotik.com
I’m sorry for that… as I explained in a previous post, I’m using 4 different units of RouterBoard RB450
Yes, I did… RouterOS v3.22 and v3.23
Took a while to check that… I have RouterBOOT v2.15 on 2 units and v2.18 on the other two.
RouterOS v3.22 and 3.23. The unit with v3.23 has RouterBoot v2.15 and the one with v3.22 has RouterBoot 2.15
How may I upgrade RouterBoot? Should I do so?