how to update LACP parameters of teamdev without rebuilding daemon？

[hustleige2003]

as far as I know，teamd is working as a control platform for LACP mode，which handles LACP pdu and maintains protocol status

so，Do we have any method to modify LACP attributions of the teamdev without rebuilding team link in kernel？

for example，when I want to change the fast_rate from default false to true，must I kill the daemon and rebuild it with new configuration command？

I have tried -o -r options which just take over or rebuild the team link but not rebuild the daemon，that leads to “file exists” failure.

[pavel-shirshov]

man teamdctl
or look it here
https://github.com/jpirko/libteam/tree/master/man

[hustleige2003]

man teamdctl
or look it here
https://github.com/jpirko/libteam/tree/master/man

thank you very much for your reply！
i have tried to use teamdctl but it can only modify LACP attributions for ports with “port config update”
but i can not set the same state/config item value ：
root@XX:/# teamdctl sg1 state item get runner.active
true
root@XX:/# teamdctl sg1 state item get runner.fast_rate
false
root@XX:/# teamdctl sg1 state item get runner.select_policy
lacp_prio
root@XX:/# teamdctl sg1 state item get runner.sys_prio
65535
root@XX:/#

root@XX:/# teamdctl sg1 state item set runner.fast_rate true
libteamdctl: cli_usock_process_msg: usock: Error message received: "OpNotSupp"
libteamdctl: cli_usock_process_msg: usock: Error message content: "Operation not supported."
command call failed (Invalid argument)
root@XX:/# teamdctl sg1 state item set runner.fallback true
libteamdctl: cli_usock_process_msg: usock: Error message received: "OpNotSupp"
libteamdctl: cli_usock_process_msg: usock: Error message content: "Operation not supported."
command call failed (Invalid argument)
root@XX:/# teamdctl sg1 state item set runner.select_policy lacp_prio_stable
libteamdctl: cli_usock_process_msg: usock: Error message received: "OpNotSupp"
libteamdctl: cli_usock_process_msg: usock: Error message content: "Operation not supported."
command call failed (Invalid argument)

[pavel-shirshov]

Yes. The operations are not supported.
I'd suggest to ask Jiri to add the operations to libteam.
[email protected]