[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(a)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(a)redhat.com>:
> > On Thu, 31 May 2012 23:23:42 +0800
> > Wenhua Zhang <shiziwen(a)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(a)redhat.com>:
> >> > On Thu, 31 May 2012 11:36:43 +0800
> >> > Wenhua Zhang <shiziwen(a)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
> >> >
> >
On Fri, 1 Jun 2012 09:43:32 +0800
Wenhua Zhang <shiziwen(a)gmail.com> wrote:
> Hi Flavio,
> What do you mean "I had to clean the 'configure' caches from libnl and
> libteam as well
> in order to get updated binaries."?
> Can you give me some more information ?
yeah, if you modify the environment (adding team driver support in
kernel, for instance) and just run make, the previously cached data
will be used and the tool will report the same error.
You have to run 'make clean' or start with a fresh './autogen.sh'
to update everything.
fbl
>
> Thanks,
> Best Wishes,
> Wenhua
>
>
>
> 2012/6/1 Wenhua Zhang <shiziwen(a)gmail.com>:
> > Hi Flavio,
> > Can you show me your config file and the environment you use?
> > 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.
> >
> > Thanks,
> > Best Wishes.
> >
> >
> > 2012/6/1 Flavio Leitner <fbl(a)redhat.com>:
> >> On Thu, 31 May 2012 23:23:42 +0800
> >> Wenhua Zhang <shiziwen(a)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(a)redhat.com>:
> >>> > On Thu, 31 May 2012 11:36:43 +0800
> >>> > Wenhua Zhang <shiziwen(a)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
> >>> >
> >>
On Thu, 31 May 2012 23:23:42 +0800
Wenhua Zhang <shiziwen(a)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(a)redhat.com>:
> > On Thu, 31 May 2012 11:36:43 +0800
> > Wenhua Zhang <shiziwen(a)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
> >
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.