Hi Jamie,
Thanks for your comments. The switch is borrowed from a colleague, not sure if it’s
configured correctly. I will ask for admin access tomorrow and check the settings.
Best Regards,
David
> Jamie Bainbridge <jamie.bainbridge(a)gmail.com> 於 2018年10月25日 上午9:43 寫道:
>
>> On Thu, 25 Oct 2018 at 08:48, David Chen <david0813(a)gmail.com> wrote:
>> Hi,
>>
>> I followed Redhat teaming configuration guide [1] to configure NIC teaming,
except LACP runner, others work as expected.
>> Here is my config file (from example lacp_1.conf):
>> { "device": "team0", "runner": { "name":
"lacp", "active": true, "fast_rate": true,
"tx_hash": ["eth", "ipv4", "ipv6"] },
"link_watch": {"name": "ethtool"}, "ports":
{"eth0": {}, "eth1": {}} }
>> I can create LACP team interface, "teamdctl team0 state" shows
correctly, but after I perform:
>> $ ip link set up dev team0
>>
>> $ ip a shows NO-CARRIER and state is DOWN for team interface.
>> dmesg shows both eth0 and eth1 link are ready, but team0 is not.
>>
>> Also, I see messages saying, "eth0 port seems to be loop backed to the same
team device".
>>
>> I am working on a POC project, please share if you have any suggestions or
pointers for me to setup a working LACP runner.
>>
>> Thank you!
>>
>> [1]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...
>
> This isn't quite clear. Are you saying the "teamdctl team0 state"
> command shows the team running and LACP negotiated properly, then you
> set the team up again and the team virtual interface goes down?
>
> Can you show the "teamdctl team0 state" command before running "ip
> link set up dev team0"?
>
> Is your switch configured with a port group in LACP Fast mode?
>
> Jamie