On Fri, Dec 08, 2006 at 09:14:46AM -0800, Nathaniel Rutman wrote: >Eric Barton wrote: >>>On Tue, Nov 28, 2006 at 12:05:41PM -0700, Jim Albin wrote: >>>>On Tue, 2006-11-28 at 13:46 -0500, Aaron Knister wrote: >>>>>options lnet networks="tcp0(ethX)" >>>>That did the trick. Thanks Aaron! >>>> >>>if I have fancy routes setup up any time before I create the OST or >>>MGS/MDT then the above doesn't work for me... even if I ifdown and ifup >>>to clear all routes first it still doesn't work. >> >>The lustre debug logs and/or console messages should help determine why >>the connection attempts are being rejected. Do you have these? >> >When a 1.6 server mounts for the first time, it reports all its local >NIDs to the MGS for inclusion in the configuration logs. After the logs >are written, the NIDs in the logs are not changed (except by doing a >"writeconf" procedure.) So if your "fancy routes" setup leads to a >weird local NID, this will get stored in the logs.
trying things again now, I can't reproduce the same problem... I must have screwed up something simple :-/ sorry about that. however, your message makes me wonder if it's possible to get the MDS to respond on both of it's gigabit interfaces? this is my best guess as to how to configure it: options lnet networks=tcp0(eth0),tcp1(eth1) and 'lctl list_nids all' then says [EMAIL PROTECTED] [EMAIL PROTECTED] # eth0 [EMAIL PROTECTED] # eth1 is that close? without any network options at all I get lo and eth0. cheers, robin _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
