search

jpirko / libteam

team netdevice library
GNU Lesser General Public License v2.1
230 stars 57 forks source link

Unable to get LACP runner working #38

Open davidchen7 opened 5 years ago

davidchen7 commented 5 years ago

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. Please share if you have any suggestions or pointers.

Thank you!

[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configure_a_network_team_using-the_command_line

stcheng commented 5 years ago

Maybe you need to check the configurations of the neighbor and use the tcpdump to check the LACP packets. With the given information, it is hard to tell if the neighbor's LAG is configured correctly.

davidchen7 commented 5 years ago

Thank you for the suggestion Shuotian! I will investigate more.

Best Regards, David

Shuotian Cheng notifications@github.com 於 2018年10月25日 上午6:51 寫道：

Maybe you need to check the configurations of the neighbor and use the tcpdump to check the LACP packets. With the given information, it is hard to tell if the neighbor's LAG is configured correctly.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.