Tue, Mar 28, 2017 at 06:51:09PM CEST, gwilkie@brocade.com wrote:Hi, like to get your thoughts on this issue we are running into. Initially, running the lacp runner in teamd. This sends carrier changes to the kernel. Kernel sets "user_carrier_enabled" which blocks its normal carrier checks. Then change teamd runner from lacp to loadbalance. When lacp runner exits,Hmm. What exactly are you doing, could you send a list of commands? I suspect some oddities :)
carrier is set to down in kernel. lacp and loadbalance runners both use same kernel mode "loadbalance", so starting loadbalance runner does not change kernel mode. Kernel still has "user_carrier_enabled" and team interface stays down due to NO_CARRIER.Hmm. I think that the correct solution is to teach the runners not to depend on kernel defaults. So in this care the loadbalance runner would set user_carrier_enabled to false during init (not during takeover)
It seems the only way to clear kernel "user_carrier_enabled" is to change the mode. Should there be a new option that teamd can use to tell kernel to clear "user_carrier_enabled" when lacp runner terminates? Or any other suggestion? Thanks. _______________________________________________ libteam mailing list -- libteam@lists.fedorahosted.org To unsubscribe send an email to libteam-leave@lists.fedorahosted.org