<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=generator
content="HTML Tidy for Windows (vers 25 March 2009), see www.w3.org"></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>But.... if I configure the OST assigning to the first interface of the OSS
(bond0) and as failover OSS the second inteface of the OSS. If the bond0 network
down, the client will try to connect to the failover, that is the second
interface of the OSS.</DIV>
<DIV> </DIV>
<DIV>is it possible?</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=briano@sgi.com
href="mailto:briano@sgi.com">Brian O'Connor</A> </DIV>
<DIV><B>Sent:</B> Wednesday, June 26, 2013 1:09 AM</DIV>
<DIV><B>To:</B> <A title=alfonso.pardo@ciemat.es
href="mailto:alfonso.pardo@ciemat.es">'Alfonso Pardo'</A> ; <A
title=shuey@purdue.edu href="mailto:shuey@purdue.edu">'Michael Shuey'</A> </DIV>
<DIV><B>Cc:</B> <A title=WC-Discuss.Migration@intel.com
href="mailto:WC-Discuss.Migration@intel.com">'WC-Discuss'</A> ; <A
title=lustre-discuss@lists.lustre.org
href="mailto:lustre-discuss@lists.lustre.org">mailto:lustre-discuss@lists.lustre.org</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">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></DIV></DIV></DIV></BODY></HTML>