On Thu, Jun 11, 2009 at 10:51:01PM -0400, Erik Froese wrote: > OK here's where I am now. > > The public client can ping the routers public address but not the > private address. > > [r...@routed-client lnet]$ cat /etc/modprobe.conf > ...... > options lnet accept=all
This would allow connections from unprivileged ports, which is probably not what you want unless you have liblustre clients. The default "accept" setting should work fine. > ...... > [r...@routed-client lnet]$ lctl ping 10.1.255....@tcp > failed to ping 10.1.255....@tcp: Input/output error > I can see traffic between the routed-client and the router as well as > between the router and the MGS/MDS (10.1.255....@tcp) > > The mgs has the following config. > > [r...@mgs-0-0 lnet]# cat /etc/modprobe.conf > ...... > options lnet forwarding="enabled" Only needed for routers. > options lnet networks=tcp(eth0) routes="tcp1 10.1.255....@tcp" This looks good. > [r...@mgs-0-0 lnet]# lctl network up > LNET configured > But it doesn't see any routes or routers. Which was why the client couldn't ping the MGS - ping request arrived at the MGS, but the MGS didn't have a route to send back its reply to the client network. > [r...@mgs-0-0 lnet]# cat /proc/sys/lnet/routes > Routing disabled > net hops state router Could you try to unload and load the lnet module again? Or add quotes over in modprobe.conf around all options, or add the options directly at modprobe command line. Somehow the routes option seemed to be ignored. Thanks, Isaac _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
