On Tue, 2007-01-30 at 08:03 +0100, Ulrich Windl wrote:
> On 29 Jan 2007 at 23:11, Tim Post wrote:
>
> > On Mon, 2007-01-29 at 13:45 +0100, Ulrich Windl wrote:
> > > On 27 Jan 2007 at 17:06, Dick Kniep wrote:
> > >
> > > > Hi list,
> > > >
> > > > We have some IBM xSeries with 2 NIC's. To make sure we have hardware
> > > > failover
> > > > and extra communication capacity, we want to bond the NIC's. So we did
> > > > the
> > > > following:
> > >
> > > In paravirtualization you lack functionality of ethtool (at least most
> > > of). Thus
> > > you are restricted to bonding modes that don't need ethtool capabilities.
> > > See the
> > > bonding docs.
> > >
> >
> > Do you happen to have a link to those? I have been digging on the Xen
> > wiki but haven't seen much, and didn't see mention of it in the 3.0.3
> > docs.
>
> It's Linux, not XEN: Look for "bonding.txt" in either the Linux sources, or
> in the
> Internet via Google or so.
I know what bonding is and how to do it. I've never used bonding with
xen with bridged networking before, however. The text I was looking for
was something discussing several options in depth with some examples,
and I have never been able to find it again.
My big questions are :
do you bond 2 nics on dom-0 and port them to a bridge, then assign the
guest vif to that bridge, or -
assign 2 nics (2 bridges) and bond inside the guest, or -
has anyone tried pciback nics, and bonding inside the guest.
Or is each appropriate, but for only certain situations?
Sorry for not being more specific.
Best,
--Tim
>
> >
> > If I'm simply snowblind after looking for it and missing the obvious so
> > many times, please be kind enough to nudge me in the right direction :)
> >
> > Thanks,
> > --Tim
> >
> > > Regards,
> > > Ulrich
> > >
> > >
> > > >
> > > > Added in /rws/etc/sysconfig/network-scripts/ifcfg-bond0
> > > >
> > > > containing:
> > > > -----snip------
> > > > DEVICE=bond0
> > > > BOOTPROTO=none
> > > > ONBOOT=yes
> > > > TYPE=Ethernet
> > > > NETMASK=255.255.255.0
> > > > IPADDR=192.168.200.31
> > > > GATEWAY=192.168.200.1
> > > > USERCTL=no
> > > > PEERDNS=no
> > > > check_link_down() { return 1 ; }~
> > > > -----snip------
> > > >
> > > > We modified ifcfg-eth0 and ifcfg-eth1 to
> > > >
> > > > -----snip------
> > > > DEVICE=eth0
> > > > BOOTPROTO=none
> > > > HWADDR=00:0d:60:eb:84:1a
> > > > ONBOOT=yes
> > > > TYPE=Ethernet
> > > > NETMASK=255.255.255.0
> > > > IPADDR=192.168.200.53
> > > > GATEWAY=192.168.200.1
> > > > PEERDNS=yes
> > > > ### Bonding of Nics
> > > > MASTER=bond0
> > > > SLAVE=yes
> > > > USERCTL=no
> > > > check_link_down() { return 1 ; }
> > > > -----snip------
> > > >
> > > > Next we loaded bonding by
> > > >
> > > > modprobe bond0.
> > > >
> > > > The the following messages appear:
> > > > Jan 27 10:51:46 CVix02 kernel: Ethernet Channel Bonding Driver: v3.0.1
> > > > (January 9, 2006)
> > > > Jan 27 10:51:46 CVix02 kernel: bonding: In ALB mode you might
> > > > experience
> > > > client disconnections upon reconnection of a link if the bonding module
> > > > updelay parameter (0 msec) is incompatible with the forwarding delay
> > > > time of
> > > > the switch
> > > > Jan 27 10:51:46 CVix02 kernel: bonding: MII link monitoring set to 1000
> > > > ms
> > > > Jan 27 10:51:57 CVix02 kernel: bonding: bond0: Error:
> > > > dev_set_mac_address of
> > > > dev eth0 failed! ALB mode requires that the base driver support setting
> > > > the
> > > > hw address also when the network device's interface is open
> > > > Jan 27 10:51:57 CVix02 kernel: bonding: bond0: Error:
> > > > dev_set_mac_address of
> > > > dev eth0 failed! ALB mode requires that the base driver support setting
> > > > the
> > > > hw address also when the network device's interface is open
> > > > Jan 27 10:51:57 CVix02 kernel: bonding: bond0: Error:
> > > > dev_set_mac_address of
> > > > dev eth1 failed! ALB mode requires that the base driver support setting
> > > > the
> > > > hw address also when the network device's interface is open
> > > > Jan 27 10:51:57 CVix02 kernel: bonding: bond0: Error:
> > > > dev_set_mac_address of
> > > > dev eth1 failed! ALB mode requires that the base driver support setting
> > > > the
> > > > hw address also when the network device's interface is open
> > > > Jan 27 10:56:01 CVix02 net.agent[19216]: remove event not handled
> > > > Jan 27 10:56:01 CVix02 net.agent[19235]: remove event not handled
> > > >
> > > > Obviously there is an error in the setting of the mac_address when the
> > > > interface is open. This is supposed to be a kernel configuration. I
> > > > hope
> > > > there is no need to rebuild the kernel for this?
> > > >
> > > > If anyone has seen this error before and knows a cure I would be a very
> > > > happy
> > > > man......
> > > >
> > > > D.Kniep
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> > >
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home