Hm, the ethernet FS is in tcp0 - MGS says its nids are MGS-IP@tcp. So not surprising it refuses that connection. On the other hand, > options lnet networks=tcp1(eth0),tcp(eth0:0) routes="o2ib > LNET-Router-IP@tcp1; tcp Default-Gateway-IP@tcp"
results in > Can't create route to tcp via Gateway-IP@tcp Cheers, Thomas On 06/14/2011 07:00 PM, Michael Shuey wrote: > Is your ethernet FS in tcp1, or tcp0? Your config bits indicate the > client is in tcp1 - do the servers agree? > > -- > Mike Shuey > > > > On Tue, Jun 14, 2011 at 12:23 PM, Thomas Roth <t.r...@gsi.de> wrote: > > Hi all, > > > > I'd like to mount two Lustre filesystems on one client. Issues with more > than one MGS set aside, > > the point here is that one of them is an Infiniband-cluster, the other is > ethernet-based. > > And my client is on the ethernet. > > I have managed to mount the o2ib-fs by setting up an LNET router, but now > this client's LNET doesn;t > > known how to reach the ethernet-fs. > > > > So the basic modprobe.conf reads > > > options lnet networks=tcp1(eth0) routes="o2ib LNET-Router-IP@tcp1" > > This mounts the MGS on the o2ib network. > > > > What do I have to add to get to the MGS on the tpc network? > > > > Meanwhile I have studied more posts here and came up with > > > options lnet networks=tcp1(eth0),tcp2(eth0:0) routes="o2ib > LNET-Router-IP@tcp1; tcp > > Default-Gateway-IP@tcp2" > > > > Doesn't work either, but I see in the log of the (tcp-)MGS: > > > LustreError: 120-3: Refusing connection from Client-IP for MGS-IP@tcp2: > No matching NI > > > > Somethings getting through ... > > > > Any ideas? > > > > Regards, > > Thomas > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss@lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss > > > _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss