[Lustre-discuss] Help! Newbie trying to set up Lustre network

[Xiang, Yang]

I tried that but on the server side, it is still refusing connection
because it came from the network on eth0:
LustreError: 120-3: Refusing connection from 39.80.8.8 for
39.80.8.9 at tcp: No matching NI

The server is actually running on eth2 on 192.168.0.2.

I added "lnet networks="tcp0(eth2)" to both /etc/modprobe.conf files on
the server and the client and rebooted.

Strange...

Yang


-----Original Message-----
From: D. Marc Stearman [mailto:marc at llnl.gov] 
Sent: Tuesday, February 22, 2011 3:54 PM
To: Xiang, Yang
Cc: Brian J. Murrell; lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] Help! Newbie trying to set up Lustre
network

Client LNET config is the same as the servers.  Add:

lnet networks="tcp0(eth2)"

to your client modprobe.conf.  That will tell the client to ONLY use  
eth2.  By default, lustre will use all network interfaces.

-Marc

----
D. Marc Stearman
Lustre Operations Lead
marc at llnl.gov
925.423.9670
Pager: 1.888.203.0641




On Feb 22, 2011, at 3:45 PM, Xiang, Yang wrote:

> I think my problem is that the client machine is also multihomed and  
> has
> 5 network interfaces. When it tries to mount, it uses the eth0 and can
> not reach the server.  I need to force it to use eth2 to talk to the
> server.  I don't know how to do that from the client configuration
> prospective.
>
> Thanks for any hint,
>
> Yang
>
>
> -----Original Message-----
> From: lustre-discuss-bounces at lists.lustre.org
> [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of Brian J.
> Murrell
> Sent: Tuesday, February 22, 2011 12:09 PM
> To: lustre-discuss at lists.lustre.org
> Subject: Re: [Lustre-discuss] Help! Newbie trying to set up Lustre
> network
>
> On 11-02-22 03:03 PM, Xiang, Yang wrote:
>> But my mount command is failing and that's the issue:
>> mount -t lustre 192.168.0.2 at tcp0:/temp /lustre
>> mount.lustre: mount 192.168.0.2 at tcp0:/temp at /lustre failed: No such
>> device
>> Are the lustre modules loaded?
>
> Right.  So, if after such a command, lsmod still shows no lustre  
> modules
> loaded, then it would seem your system is not loading the modules on
> demand, as it should.  Or that there is an issue in which they are
> failing to install correctly.
>
> You can try to manually load the modules before issuing the mount
> command with:
>
> # modprobe lustre
>
> Of course, if that fails, the syslog kernel target and/or dmesg should
> be informative of why.
>
> b.
>
> -- 
> Brian J. Murrell
> Senior Software Engineer
> Whamcloud, Inc.
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss