<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="HTML Tidy for Windows (vers 25 March 2009), see www.w3.org">
<title></title>
</head>
<body>
Unless something has changed in the new versions of lustre, I don't think lustre can do failover between nids on the same machine.<br>
<br>
It can choose the available nid at mount time, but if an active nid goes away after you are mounted then the client chooses the failover nid, and this must be on a different server.<br>
<br>
Check the archives for more discussion in this topic :)<br>
<br>
<br>
<br>
-----Original Message-----<br>
<b>From: </b>Alfonso Pardo [<a href="mailto:alfonso.pardo@ciemat.es">alfonso.pardo@ciemat.es</a>]<br>
<b>Sent: </b>Tuesday, June 25, 2013 07:23 AM Central Standard Time<br>
<b>To: </b>Michael Shuey<br>
<b>Cc: </b>WC-Discuss; lustre-discuss@lists.lustre.org<br>
<b>Subject: </b>Re: [Lustre-discuss] Lustre over two TCP interfaces<br>
<br>
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<div>thank Michael,</div>
<div> </div>
<div>This is my second step, I will change the lnet with “options lnet networks=tcp0(bond0,bond1)” because my machines has 4 nics. I have a bond0 and bond1 with LACP. I need to comunicate the clients with two network for HA network.</div>
<div> </div>
<div>If the bond0 network is down, the clients can reach the OSS by the second network bond1.</div>
<div> </div>
<div>If I change the modprobe with “options lnet networks=tcp0(bond0),tcp1(bond1)”, how the clients mount the filesystem to reach the OSS by two network?</div>
<div> </div>
<div> </div>
<div> </div>
<div style="FONT-SIZE: small; FONT-FAMILY: 'Calibri'; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; TEXT-DECORATION: none; DISPLAY: inline">
<div style="FONT: 10pt tahoma">
<div> </div>
<div style="BACKGROUND: #f5f5f5">
<div style="font-color: black"><b>From:</b> <a title="shuey@purdue.edu" href="mailto:shuey@purdue.edu">
Michael Shuey</a></div>
<div><b>Sent:</b> Tuesday, June 25, 2013 2:14 PM</div>
<div><b>To:</b> <a title="alfonso.pardo@ciemat.es" href="mailto:alfonso.pardo@ciemat.es">
Alfonso Pardo</a></div>
<div><b>Cc:</b> <a title="lustre-discuss@lists.lustre.org" href="mailto:lustre-discuss@lists.lustre.org">
lustre-discuss@lists.lustre.org</a> ; <a title="WC-Discuss.Migration@intel.com" href="mailto:WC-Discuss.Migration@intel.com">
WC-Discuss</a></div>
<div><b>Subject:</b> Re: [Lustre-discuss] Lustre over two TCP interfaces</div>
</div>
</div>
<div> </div>
</div>
<div style="FONT-SIZE: small; FONT-FAMILY: 'Calibri'; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; TEXT-DECORATION: none; DISPLAY: inline">
Different interfaces need to be declared with different LNET networks - something like "networks=tcp0(eth0),tcp1(eth1)". Of course, that assumes your clients are configured to use a mix of tcp0 and tcp1 for connections (with each client only using one of the
two). This is really only useful in corner cases, when you're doing something strange; if eth0 and eth1 are in the same subnet (as in your example), this is almost certainly not productive.
<div> </div>
<div>A better bet might be to use a single LNET, and bond the two interfaces together - either as an active/passive pair, or active/active (e.g., LACP). Then you'd declare networks=tcp0(bond0), give the bond a single IP address, and client traffic would be
split across the two members in the bond more like you probably expect (given the limits of the bond protocol you're using).<br>
<div>
<div> </div>
<div>--<br>
Mike Shuey</div>
<br>
<br>
<div class="gmail_quote">On Tue, Jun 25, 2013 at 8:06 AM, Alfonso Pardo <span dir="ltr">
<<a href="mailto:alfonso.pardo@ciemat.es" target="_blank">alfonso.pardo@ciemat.es</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div dir="ltr">
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'">
<div>hello friends,</div>
<div> </div>
<div>I need to comunicate my OSS by two ethernet TCP interfaces: eth0 and eth1.</div>
<div> </div>
<div>I have configured this feature in my modprobe.d with:</div>
<div> </div>
<div>“options lnet networks=tcp0(eth0,eth1)”</div>
<div> </div>
<div>And I can see two interfaces with:</div>
<div> </div>
<div>lctl --net tcp interface_list</div>
<div><a href="http://sa-d4-01.ceta-ciemat.es" target="_blank">sa-d4-01.ceta-ciemat.es</a>: (<a href="http://192.168.11.15/255.255.255.0" target="_blank">192.168.11.15/255.255.255.0</a>) npeer 0 nroute 2</div>
<div><a href="http://sa-d4-01.ceta-ciemat.es" target="_blank">sa-d4-01.ceta-ciemat.es</a>: (<a href="http://192.168.11.35/255.255.255.0" target="_blank">192.168.11.35/255.255.255.0</a>) npeer 0 nroute 0</div>
<div> </div>
<div>But, the clients only can communicate with the first interface:</div>
<div> </div>
<div>lctl ping 192.168.11.15</div>
<div>12345-0@lo</div>
<div>12345-192.168.11.15@tcp</div>
<div>lctl ping 192.168.11.35</div>
<div>failed to ping 192.168.11.35@tcp: Input/output error</div>
<div> </div>
<div> </div>
<div>Any suggestions how to “enable” the second interface?</div>
<div> </div>
<div> </div>
<div>thank in advance</div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'">
<p><i><span><span style="FONT-FAMILY: century gothic,sans-serif,10">Alfonso Pardo Diaz</span></span></i><br>
<i><b><span style="FONT-FAMILY: century gothic,sans-serif">System Administrator / Researcher</span></b></i><br>
<i><span style="FONT-FAMILY: century gothic,sans-serif">c/ Sola nº 1; 10200 TRUJILLO, SPAIN</span></i><br>
<i><span style="FONT-FAMILY: century gothic,sans-serif">Tel: <a href="tel:%2B34%20927%2065%2093%2017" target="_blank" value="+34927659317">
+34 927 65 93 17</a> Fax: +34 927 32 32 37</span></i></p>
<p><span><a href="http://www.ceta-ciemat.es/" target="_blank"><img border="0" alt="CETA-Ciemat logo" width="383" height="76"></a></span></p>
</div>
</div>
</div>
---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización,
divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucción. Disclaimer: This message and
its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and
may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ----------------------------</div>
<br>
_______________________________________________<br>
Lustre-discuss mailing list<br>
<a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
<br>
</blockquote>
</div>
<div> </div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>