Univention Bugzilla – Bug 36340
Bonding configuration generates wrong miimon configuration
Last modified: 2014-12-04 12:22:16 CET
I guess it needs to be fixed for UCS 4.0 as well. +++ This bug was initially created as a clone of Bug #36339 +++ 2014102821000257 The UMC module does not set MII link monitoring frequency correctly: interfaces/bond0/options/2: miimon 100 should be: interfaces/bond0/options/2: bond-miimon 100 Therefore, in bond-modes like active-backup, the active slave is _never_ switched so the network is down when the active slave goes down! A fix should also correct all broken configurations in UCR. Workaround: 1) Set "bond-miimon <Frequency in milliseconds>" manually via "Additional bonding options" in UMC wizard. BUT: this would need to be manually removed when this bug is fixed because ifup complains about duplicate options /etc/network/interfaces:39: duplicate option ifup: couldn't read interfaces file "/etc/network/interfaces" 2) Correct UCR manually: ucr search --brief --non-empty '^interfaces/.*/options/' | \ sed -rne 's,(interfaces/.*/options/.*): (miimon .*)$,\1=bond-\2,p' | \ xargs -d '\n' --no-run-if-empty ucr set BUT: Re-running the UMC wizard for that interface will again break the configuration!
YAML: 2014-11-21-univention-system-setup.yaml
OK: r56050 OK: aptitude install '?source-package(univention-system-setup)?installed' OK: bond-miimon 101 OK: cat /sys/class/net/bond0/bonding/miimon OK: 2014-11-21-univention-system-setup.yaml
http://errata.univention.de/ucs/4.0/2.html