|
Can you upgrade to the latest e100 and e1000 drivers from Intel?
Are you running one different speeds on the NICs (i.e., 100 on the e100
and 1000 on the e1000)?
On Thu, 2003-11-06 at 19:52, Nathan wrote:
> Bonding is being loaded when the box boots from modules.conf.
>
> eepro100 (one of the build in nic is a 10/100) and the e1000 driver.
>
> On Thu, 2003-11-06 at 17:39, Brian Tinsley wrote:
> > iANS config looks good. Options for the bonding driver look comparable.
> > More questions:
> >
> > 1. How are you loading the bonding driver at boot time?
> > 2. What NIC driver are you using?
> >
> >
> >
> > On Thu, 2003-11-06 at 19:31, Nathan wrote:
> >
> > > It's using the 2.4.20 kernel w/ a bonding patch don't remember which one
> > > exactly may be bonding-2.4.20-20030320. The switch the realserver and
> > > director are on uses tagged vlans.
> > >
> > > bonding options:
> > > options bonding miimon=100 mode=1
> > >
> > > ians config:
> > > TEAM ians
> > > TEAMING_MODE AFT
> > > VLAN_MODE off
> > > PROBE_ENABLE disabled
> > > MEMBER eth0
> > > PRIORITY primary
> > > MEMBER eth1
> > > PRIORITY secondary
> > > VADAPTER team0
> > >
> > >
> > > On Thu, 2003-11-06 at 17:17, Brian Tinsley wrote:
> > > > I use both iANS (Intel) and bonding in LVS clusters (on both load
> > > > balancers and real servers) and have never seen this type of problem.
> > > > Could you post your bonding driver options and iANS config file? Are you
> > > > using tagged VLANS? What kernel version are you using?
> > > >
> > > >
> > > >
> > > > > > I'm using lvs-dr and it works great, until I added a realserver that
> > > > > > used linux channel bonding. when I added it I could not connect to
> > > > > > the
> > > > > > service at all from outside the network. Switched the realserver
> > > > > > over to
> > > > > > Intel's teaming driver and the problem went away (also works when
> > > > > > using
> > > > > > just one nic). Anyone know what causes this or seen this before?
> > > > > >
> > > > > > _______________________________________________
> > > > > > LinuxVirtualServer.org mailing list -
> > > > > > lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > > > > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > > > > > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > > > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > > > > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> > > > _______________________________________________
> > > > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > > > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> > >
> > > _______________________________________________
> > > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> > _______________________________________________
> > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
