Thu, Apr 11, 2024 at 10:11:34AM CEST, batmanustc@gmail.com wrote:
Hi all,
I'm using teamd-v1.31(tag v1.31) from source compile from https://github.com/jpirko/libteam .
This is my network topo:
teamd-1 | | veth11 veth01 | | | | veth10 veth00 | | teamd-0Which is run team-1 with veth11 and veth01, run team-2 with veth10 and veth00.
This is my conf:
### teamd-0 [root@centos8-20240407 public-libteam]# cat ../lacp-t0.conf { "device": "team0", "runner": { "name": "lacp", "sys_prio": 5, "agg_select_policy": "lacp_prio", "active": true, "tx_hash": ["eth", "ipv4", "ipv6"] }, "link_watch": {"name": "ethtool"}, "ports": { "veth00": {"lacp_prio": 30}, "veth10": {"lacp_prio": 20} } } ### teamd-1 [root@centos8-20240407 public-libteam]# cat ../lacp-t1.conf { "device": "team0", "runner": { "name": "lacp", "sys_prio": 66, "active": true, "tx_hash": ["eth", "ipv4", "ipv6"] }, "link_watch": {"name": "ethtool"}, "ports": { "veth01": {}, "veth11": {} } }In my opinion and code, I think this conf will cause this behavior:
- teamd-0 use lacp, use low system priority, use equal port priority.
- teamd-1 use lacp, use high system priority, use not euqal port priority.
- then veth11 and veth10 will UP, veth01 and veth00 will DOWN.
But in fact, veth11 and veth10 is UP, veth01 and veth00 is also UP.
What exactly do you mean by "UP" and "DOWN"?
So:
- What's wrong with my configure?
- How to configure use lacp port priority?
Simon Jones
-- _______________________________________________ libteam mailing list -- libteam@lists.fedorahosted.org To unsubscribe send an email to libteam-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/libteam@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue