<HTML dir=ltr><HEAD><TITLE>Re: [Lustre-discuss] How to configure routing</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText74303 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Ahhh, that might be the problem. I only defined a route on the gateway node. Is it possible to dynamically add a route? Since I'm dealing with a production file system, I can't really shut it down to play with the routing.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Ron.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Cliff White [mailto:Cliff.White@Sun.COM]<BR><B>Sent:</B> Wed 1/16/2008 6:07 PM<BR><B>To:</B> Jerome, Ron<BR><B>Cc:</B> Lustre-discuss@clusterfs.com<BR><B>Subject:</B> Re: [Lustre-discuss] How to configure routing<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Jerome, Ron wrote:<BR>> That's what I was hoping, but I'm still having trouble getting the<BR>> routing to work.<BR>><BR>> My MGS is at 192.168.0.200@tcp<BR>><BR>> On my gateway node, I have...<BR>><BR>> options lnet networks="tcp0(eth0),tcp1(eth1)" routes="tcp1<BR>> 192.168.0.2@tcp ;\<BR>> tcp0<BR>> 132.246.xxx.xxx@tcp1"<BR>><BR>> Then from the node solely connected to the public (132.246) network, I<BR>> try to mount<BR>><BR>> mount -t lustre 192.168.0.200@tcp:/data /mnt/data<BR>><BR>> but regrettably this does not work :-(<BR><BR>All nodes involved need to have routes defined, are the routes defined<BR>on the clients and servers also?<BR>cliffw<BR><BR>><BR>><BR>> Ron.<BR>><BR>>> -----Original Message-----<BR>>> From: Canon, Richard Shane [<A href="mailto:canonrs@ornl.gov">mailto:canonrs@ornl.gov</A>]<BR>>> Sent: January 16, 2008 10:03 AM<BR>>> To: Jerome, Ron<BR>>> Cc: He.Huang@Sun.COM; Lustre-discuss@clusterfs.com<BR>>> Subject: RE: [Lustre-discuss] How to configure routing<BR>>><BR>>><BR>>> Ron,<BR>>><BR>>> You don't have to rely on IP routing. You can use Lustre routing<BR>>> instead. You have the basic config line below. The external clients<BR>>> need to know about both networks and the routers. You should be able<BR>>> to<BR>>> use the same LNET module options everywhere. You would do a mount<BR>>> like...<BR>>><BR>>> mount -t lustre <mds ip>@tcp1:/lustre/client /mnt<BR>>><BR>>> Assuming the private network is tcp1 and tcp0 is the public network.<BR>>><BR>>><BR>>> --Shane<BR>>><BR>>> -----Original Message-----<BR>>> From: lustre-discuss-bounces@clusterfs.com<BR>>> [<A href="mailto:lustre-discuss-bounces@clusterfs.com">mailto:lustre-discuss-bounces@clusterfs.com</A>] On Behalf Of Balagopal<BR>>> Pillai<BR>>> Sent: Wednesday, January 16, 2008 9:27 AM<BR>>> To: Jerome, Ron<BR>>> Cc: He.Huang@Sun.COM; Lustre-discuss@clusterfs.com<BR>>> Subject: Re: [Lustre-discuss] How to configure routing<BR>>><BR>>> Hi,<BR>>><BR>>> Interesting scenario if routing between public and private<BR>>> subnets for mounting lustre filesystem is possible<BR>>> without disturbing the network admins for public subnet :-) One way<BR>>> around would be<BR>>> to build tunnels like ipip for example between the gateway machine on<BR>>> the cluster<BR>>> that has access to both nets and with other hosts on the public net.<BR>>> Then Lustre mount<BR>>> could work over the tunnel with static routes to access the<BR>> MGS/MDS/OST<BR>>> over the tunnel.<BR>>><BR>>> Regards<BR>>> Balagopal<BR>>><BR>>> Jerome, Ron wrote:<BR>>>> Hi Isaac,<BR>>>><BR>>>> Yes I had read the documentation prior to posting my question but a<BR>>>> couple of things were still unclear to me, but first a bit more<BR>>>> background... My lustre filesystem & my cluster reside on a private<BR>>>> (192.169.xxx.xxx) network I have a couple of machines which are<BR>>>> connected to both the private network and our public network and I<BR>>> would<BR>>>> like a machine which only has access to the public network to mount<BR>>> the<BR>>>> lustre filesystem on the private network via one of the nodes which<BR>>>> spans both.<BR>>>><BR>>>> So my questions are...<BR>>>><BR>>>> a) is it possible to route to and from a private (192.168.xxx.xxx)<BR>>>> Ethernet network to a public one (132.246.xxx.xxx)? The documents<BR>>> only<BR>>>> show routing between Ethernet and other networks such as elan,<BR>>> Myrinet<BR>>>> etc.<BR>>>><BR>>>> b) if this is possible, what is the correct syntax for the<BR>>> modprobe.conf<BR>>>> file? I currently have...<BR>>>><BR>>>> options lnet networks="tcp0(eth0),tcp1(eth1)" routes="tcp1<BR>>>> 192.168.0.2@tcp"<BR>>>><BR>>>> c) from a client on the public network what would the syntax be for<BR>>>> accessing (mounting) the mgs through the routing node?<BR>>>><BR>>>><BR>>>> Thanks very much,<BR>>>><BR>>>> Ron.<BR>>>><BR>>>><BR>>>>> -----Original Message-----<BR>>>>> From: He.Huang@Sun.COM [<A href="mailto:He.Huang@Sun.COM">mailto:He.Huang@Sun.COM</A>]<BR>>>>> Sent: January 16, 2008 8:25 AM<BR>>>>> To: Jerome, Ron<BR>>>>> Cc: Lustre-discuss@clusterfs.com<BR>>>>> Subject: Re: [Lustre-discuss] How to configure routing<BR>>>>><BR>>>>> On Tue, Jan 15, 2008 at 02:27:39PM -0500, Jerome, Ron wrote:<BR>>>>><BR>>>>>> I would like to use a client as a router between two tcp<BR>>> networks<BR>>>>> (eth0<BR>>>>><BR>>>>>> and eth1) but it is unclear to me how to configure this in<BR>>>>>> modprobe.conf.<BR>>>>>><BR>>>>>><BR>>>>>> Any suggestions would be greatly appreciated.<BR>>>>>><BR>>>>> <A href="http://manual.lustre.org/manual/LustreManual16_HTML/DynamicHTML-06-">http://manual.lustre.org/manual/LustreManual16_HTML/DynamicHTML-06-</A><BR>>>>> 1.html<BR>>>>><BR>>>>> Please read section 3.2.2.<BR>>>>><BR>>>>> Isaac<BR>>>>><BR>>>> _______________________________________________<BR>>>> Lustre-discuss mailing list<BR>>>> Lustre-discuss@clusterfs.com<BR>>>> <A href="https://mail.clusterfs.com/mailman/listinfo/lustre-discuss">https://mail.clusterfs.com/mailman/listinfo/lustre-discuss</A><BR>>>><BR>>> _______________________________________________<BR>>> Lustre-discuss mailing list<BR>>> Lustre-discuss@clusterfs.com<BR>>> <A href="https://mail.clusterfs.com/mailman/listinfo/lustre-discuss">https://mail.clusterfs.com/mailman/listinfo/lustre-discuss</A><BR>><BR>> _______________________________________________<BR>> Lustre-discuss mailing list<BR>> Lustre-discuss@clusterfs.com<BR>> <A href="https://mail.clusterfs.com/mailman/listinfo/lustre-discuss">https://mail.clusterfs.com/mailman/listinfo/lustre-discuss</A><BR><BR></FONT></P></DIV></BODY></HTML>