On 2010-01-14, at 23:51, Dusty Marks wrote: > You are correct, there is information in messages. Following are the > entries related the lustre. The line that says 192.168....@tcp is > unreachable makes sense, but what exactly is the problem? I entered > the line "options lnet networks=tcp" in modprobe.conf on the oss and > mds. The only difference was, i entered that line AFTER i setup > lustre on the OSS. Could that be the problem? I don't see why that > would be the problem, as the oss is trying to reach the MDS/MGS, > which is 192.168.0.2. > > --------------------------------------- /var/log/messages > ----------------------------------------------------------- > Jan 14 22:41:07 oss kernel: Lustre: 2846:0:(linux-tcpip.c: > 688:libcfs_sock_connect()) Error -113 connecting 0.0.0.0/1023 -> > 192.168.0.2/988 > Jan 14 22:41:07 oss kernel: Lustre: 2846:0:(acceptor.c: > 95:lnet_connect_console_error()) Connection to 192.168....@tcp at > host 192.168.0.2 was unreachable: the network or that node may be > down, or Lustre may be misconfigured.
Please read the chapter in the manual about network configuration. I suspect the .0.2 network is not your eth0 network interface, and your modprobe.conf needs to be fixed. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
