On 04/03/2017 02:14 PM, Jiri Pirko wrote:
Fri, Mar 31, 2017 at 06:01:46PM CEST, gwilkie(a)Brocade.com wrote:
>
> On 03/31/2017 04:01 PM, Jiri Pirko wrote:
>> Fri, Mar 31, 2017 at 01:41:08PM CEST, gwilkie(a)brocade.com wrote:
>>> On 03/30/2017 04:18 PM, Jiri Pirko wrote:
>>>> Tue, Mar 28, 2017 at 06:51:09PM CEST, gwilkie(a)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 :)
>>>>
>>> 1. start off in LACP mode - NO-CARRIER expected as no LACP on other side.
>>> root@debian9:~# teamd --team-dev team0 --daemon --no-quit-destroy
--take-over
>>> --config='{"runner":{"name":"lacp"}}'
>>> This program is not intended to be run as root.
>>> root@debian9:~# ip link set dev ens9 master team0
>>> root@debian9:~# ip link set dev ens10 master team0
>>> root@debian9:~# ip link set dev team0 up
>>> root@debian9:~# ip link show team0
>>> 8: team0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state
>>> DOWN mode DEFAULT group default qlen 1000
>>> link/ether 52:54:00:8b:12:a5 brd ff:ff:ff:ff:ff:ff
>>> root@debian9:~#
>>>
>>>
>>> 2. change to balanced mode - still NO-CARRIER
>>> root@debian9:~# ip link set dev team0 down
>>> root@debian9:~# ip link set dev ens9 nomaster
>>> root@debian9:~# ip link set dev ens10 nomaster
>>> root@debian9:~# teamd --team-dev team0 --kill
>>> root@debian9:~# teamd --team-dev team0 --daemon --no-quit-destroy
--take-over
>> I think that you might be missing the reason of existence of take over.
>> It suppose to "take over" the kernel team instance in case for example
>> the teamd segfaults or something. The intension was to run new teamd
>> instance taking over the kernel instance with exact same config.
>>
>> Why are you doing this?
>>
>>
> Want to change the teamd config without losing the interface config
> (addresses, vlans etc) - want to avoid deleting the team device when
> updating team config.
Is it like a regular runtime thing for you? I would expect that you just
do the configuration once and you use the same one forever.
I don't think I
could say it would be a regular thing done in production -
more like something you do during setup or troubleshooting.
Do you think this will get addressed or is it something we will have to
live with?
Thx.