Here at PNNL, we have been happy using the mode=4 option to the bonding driver to get 802.3ad aggregation. This option requires a switch that can do handle the type, and our Cisco switch does. If your HP switch supports it it would be interesting to see what you can get out of your configuration.
Evan > -----Original Message----- > From: Jeremy Mann [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 14, 2006 2:31 PM > To: Felix, Evan J > Cc: [email protected] > Subject: RE: [Lustre-discuss] Using Lustre on channel bonded > interfaces > > > Felix, Evan J wrote: > > Can you tell us more about the version of Lustre you are > using, that > > options to the bonding module are you setting, and possibly > what type of > > switch you are using? Those things may help. If you are > able to set > > up two separate networks on the two interfaces, it is > possible(correct > > me here guys if I have this wrong) that Lustre can just run > over the > > two interfaces and be just happy. For example, can you > make all the > > eth0 interfaces be on the 10.10.10.0/24 network, and all the eth1 > > interfaces on the 10.10.20.0/24 network. The just use the > lnet module > > parameters(>=1.4.6 only) to set two channels for traffic. > > We are using Lustre 1.6beta5 and no options for the bonding > driver and the switch is an HP ProCurve 2848 I wasn't aware > of the magnitude of options for bonding and now after reading > bonding.txt, I don't know what sort of trunking to use. > > -- > Jeremy Mann > [EMAIL PROTECTED] > > University of Texas Health Science Center Bioinformatics Core > Facility http://www.bioinformatics.uthscsa.edu > Phone: (210) 567-2672 > _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
