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.
I need to boot without any fancy routes set at all, then create
the Lustre filesystem, otherise the OSSs and MDS always reject the
traffic. this is with Lustre 1.6beta5.
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.
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
