[please, don't remove the libteam list from CC, others might find this discussion useful]
On Fri, 1 Jun 2012 00:26:15 +0800 Wenhua Zhang shiziwen@gmail.com wrote:
Hi Flavio, Can you show me your config file and the environment you use?
Sure, I have two configs currently working:
# cat team0-activebackup.cfg { "device": "team0", "hwaddr": "00:1C:C0:A3:7F:16", "runner": { "name": "activebackup" }, "link_watch": { "name": "ethtool" }, "ports": { "em1": { "prio": 100 }, "p11p1": { "prio": 100 } } } # cat team0-lacp.cfg { "device": "team0", "hwaddr": "00:1C:C0:A3:7F:16", "runner": { "name": "lacp", "active": 1, "fast_rate": 1, "tx_hash": ["eth", "ipv4", "ipv6"] }, "link_watch": { "name": "ethtool" }, "ports": { "em1": { "prio": 100 }, "p11p1": { "prio": 100 } } }
# uname -r 3.4.0-01622-g31a6710
# lsmod | grep team team_mode_loadbalance 1819 1 team_mode_activebackup 1690 0 team 18475 2 team_mode_loadbalance,team_mode_activebackup
I am confused about how to test the libteam, and I hope you can give me some advice. We plain to use libteam instead of bonding, and before that we need do some tests.
Certainly. I am testing 'teamd' here as well, so I appreciate any feedback you can give to us.
thanks, fbl
Thanks, Best Wishes.
2012/6/1 Flavio Leitner fbl@redhat.com:
On Thu, 31 May 2012 23:23:42 +0800 Wenhua Zhang shiziwen@gmail.com wrote:
Hi Flavio, Thanks for your help. I have build the latest net-next kernel and try again. There is still some problem, and I will try some other method to fix it.
I did those steps yesterday using net-next and I am now running active-backup on two different machines.
I had to clean the 'configure' caches from libnl and libteam as well in order to get updated binaries.
fbl
2012/5/31 Flavio Leitner fbl@redhat.com:
On Thu, 31 May 2012 11:36:43 +0800 Wenhua Zhang shiziwen@gmail.com wrote:
Hi all, When I try to test the libteam as Example in https://fedorahosted.org/libteam/wiki/InfrastructureSpecification, I got errors as blew: Failed to create team device. teamd_init() failed. Failed to start daemon: Operation not supported
The command is :teamd -f teamd2.conf -D The conf is : { "device": "team0", "runner": { "name": "lacp", "active": 1, "fast_rate": 1 }, "link_watch": {"name": "ethtool"}, "ports": {"eth1": {}, "eth2": {}} }
So, is there something wrong with my commands or conf file? Thanks for your help.
You didn't tell what kernel you are using. You need to have a kernel with libteam driver enabled.
After booting with that kernel, compile libnl, install it. Next compile libteam and install it.
That fixed the same issue here. fbl
2012/6/1 Flavio Leitner fbl@sysclose.org:
[please, don't remove the libteam list from CC, others might find this discussion useful]
On Fri, 1 Jun 2012 00:26:15 +0800 Wenhua Zhang shiziwen@gmail.com wrote:
Hi Flavio, Can you show me your config file and the environment you use?
Sure, I have two configs currently working:
# cat team0-lacp.cfg { "device": "team0", "hwaddr": "00:1C:C0:A3:7F:16", "runner": { "name": "lacp", "active": 1, "fast_rate": 1, "tx_hash": ["eth", "ipv4", "ipv6"] }, "link_watch": { "name": "ethtool" }, "ports": { "em1": { "prio": 100 }, "p11p1": { "prio": 100 } } }
When I use this conf to test libteam, the kernel panic... The commands as below: #teamd -f team0-lb.conf -g #ip addr add 192.168.24.2/24 dev team0 #ip link set team0 up When I make the team0 up, the kernel panic.
The /var/log/messages: Jun 7 10:23:52 debian-wenhzhan kernel: [ 376.208819] (unregistered net_device): Failed to send options change via netlink Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.240450] team0: Mode changed to "loadbalance" Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.245140] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.249121] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.249228] team0: Port device eth1 added Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.249252] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.258384] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.258656] team0: Port device eth2 added Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.260936] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Jun 7 10:23:53 debian-wenhzhan kernel: [ 376.261433] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Jun 7 10:26:29 debian-wenhzhan kernel: [ 532.802757] device lo entered promiscuous mode Jun 7 10:26:38 debian-wenhzhan kernel: [ 541.749591] device lo left promiscuous mode
And I you can more detail from the attachments.
Do you have any ideas about it ?
Thanks, Best Wishes, Wenhua
Hi Flavio, I have tried some other config definition and find that when I defined "runner" to be "lacp" and added "tx_hash" together, then make team0 up("ip link set team0 up"), the kernel will panic.
#uname -a Linux debian-wenhzhan 3.4.0-team+ #1 SMP Thu May 31 16:09:22 CST 2012 x86_64 GNU/Linux
The kernel is the latest net-next version.
Do you have any ideas about it ?
Thanks,
Best Wishes, Wenhua
libteam@lists.fedorahosted.org