An update... the configuration below is almost working. I can ping everywhere except the client cannot ping the router. In other words, the tcp client can ping other nodes on o2ib, o2ib nodes (including the router nodes) can ping the tcp clients. The tcp client can ping the tcp side of the routers. It's just the tcp client cannot ping either of the o2ib side of the routers. What would cause this?
> -----Original Message----- > From: [email protected] [mailto:lustre-discuss- > [email protected]] On Behalf Of Frank Riley > Sent: Wednesday, May 23, 2012 1:49 PM > To: [email protected] > Subject: [Lustre-discuss] help with lnet routing > > I'm trying to set up lnet routing for our system, and it's a bit unique. I'm > not > sure how to do it. I am trying to route from workstation clients to the > internal > infiniband network of the cluster. Here is the setup: > > Lustre router: > 192.168.20.63 ib0 > 10.1.4.151 eth1 > > Client > 10.1.10.209 eth0 > > For non-Lustre tcp on the client, addresses 10.1.0.0/16 on eth0 route > through 10.1.0.1. > > My lustre lnet config is as follows: > > options lnet ip2nets="o2ib 192.168.20.*; tcp(eth1) 10.1.4.*; tcp(eth0) > 10.1.*.*" \ > routes="tcp 192.168.20.63@o2ib; o2ib 10.1.4.151@tcp" > > This of course isn't working. From the router, I can lctl ping 10.1.4.151@tcp, > but the client cannot ping the router. I'm guessing the routing from > 10.1.10.0/24 to 10.1.4.0/24 is causing the problem, but I don't know how to > make it work. Any suggestions? > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
