<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Thanks for the answers.. For fail over I believe we will want to keep it separate then. Next question. Is it licensed as a client or a server?
<br>
</p>
<br>
<div class="moz-cite-prefix">On 4/10/17 6:20 AM, McLaughlin, Sandra M wrote:<br>
</div>
<blockquote cite="mid:DB5PR04MB1463EFFEFCEC10D3BE417C4BE1010@DB5PR04MB1463.eurprd04.prod.outlook.com" type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I agree with Venkat.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I did exactly what you said below, enabled my NSD servers as gateways to get additional throughput (with both native gpfs protocol and NFS protocol),
which worked well; we definitely got the increased traffic. However, I wouldn’t do it again through choice. As Venkat says, if there is a problem with the remote cluster, that can affect any of the gateway nodes (if using gpfs protocol), but also, we had a
problem with one of the gateway nodes, where it kept crashing (which is now resolved) and then all filesets for which that node was the gateway had to failover to other gateway servers and this really messes everything up while the failover is taking place.
I am also, stupidly, serving NFS and samba from the NSD servers (via ctdb) which I also, would not do again !<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">It would be nice if there was a way to specify which gateway server is the primary gateway for a specific fileset.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Regards, Sandra<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">
<a class="moz-txt-link-abbreviated" href="mailto:gpfsug-discuss-bounces@spectrumscale.org">
gpfsug-discuss-bounces@spectrumscale.org</a> [<a class="moz-txt-link-freetext" href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a>]
<b>On Behalf Of </b>Venkateswara R Puvvada<br>
<b>Sent:</b> 10 April 2017 11:56<br>
<b>To:</b> gpfsug main discussion list <a class="moz-txt-link-rfc2396E" href="mailto:gpfsug-discuss@spectrumscale.org">
<gpfsug-discuss@spectrumscale.org></a><br>
<b>Subject:</b> Re: [gpfsug-discuss] AFM gateways<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">It is not recommended to make NSD servers as gateway nodes for native GPFS protocol. Unresponsive remote cluster mount might cause gateway node to hang on synchronous operations
(ex. Lookup, Read, Open etc..), this will affect NSD server functionality. More information is documented @</span><br>
<br>
<a moz-do-not-send="true" href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.2/com.ibm.spectrum.scale.v4r22.doc/bl1ins_NFSvsGPFSAFM.htm"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.2/com.ibm.spectrum.scale.v4r22.doc/bl1ins_NFSvsGPFSAFM.htm</span></a><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">~Venkat (<a moz-do-not-send="true" href="mailto:vpuvvada@in.ibm.com">vpuvvada@in.ibm.com</a>)</span><br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Matt Weil <<a moz-do-not-send="true" href="mailto:mweil@wustl.edu">mweil@wustl.edu</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">gpfsug main discussion list <<a moz-do-not-send="true" href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">04/07/2017 08:28 PM</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">[gpfsug-discuss] AFM gateways</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a moz-do-not-send="true" href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></span><o:p></o:p></p>
<div class="MsoNormal" style="text-align:center" align="center">
<hr style="color:#A0A0A0" align="center" noshade="noshade" size="2" width="100%">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">Hello,</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>any reason to not enable all NSD servers as gateway when using native</tt><br>
<tt>gpfs AFM? Will they all pass traffic?</tt><br>
<br>
<tt>Thanks</tt><br>
<br>
<tt>Matt</tt><br>
<br>
<br>
<tt>________________________________</tt><br>
<tt>The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any
action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.</tt><br>
<tt>_______________________________________________</tt><br>
<tt>gpfsug-discuss mailing list</tt><br>
<tt>gpfsug-discuss at spectrumscale.org</tt><br>
</span><a moz-do-not-send="true" href="https://clicktime.symantec.com/a/1/8aBOwOn_FKxazPLofFX3cA0dDfWXyb5axOe5dISv0MQ=?d=j_6XzU1IV9LQ-e532TEWOiD1RS4MpcmKAZyY2sOb5ZFKeKraYKzPKVQ4DFQQvcoLaFlXYvSpJrBNPXgTLo9lvlh_-tLXZz6eK3RvlxqOvMh7u61FPNKvX3imIyz4oKgEui5fq5PAZtfg30umWRmQiMC4IXcZP4tBPCofBgPeN1QnVLFzY9StBzIWmH1VXwf9-MBET1k5ltix5IHkz4Q7JkSDZjHbVjiq_zycxFUQ4u92eEKq-4RzX8jPpKXVMjL-HQPjf2Y8oGNZhDBbiAFrwI-vUSs9VLha4rRcdOn4k0gN4IrFgvtlJY6r65vqwyrYb50stU_BmJgIX94nHlh1AYUa-bDwHNn7aPX-MOHCgHM86sfnDwm_hzuia4YUXmzxcbU4NR00eyHApIKhXXAgxBfua-s25zX32om-i8jWCKpl_AOfX7CZqMuvSp48hzs%3D&u=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss"><tt><span style="font-size:10.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><br>
<br>
<o:p></o:p></p>
</div>
<hr>
<p class="{Imprint.UniqueID}" style="FONT-SIZE: 8pt"><font face="Arial">AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge,
CB2 0AA.</font></p>
<p class="{Imprint.UniqueID}" style="FONT-SIZE: 8pt"><font face="Arial">This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not
copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and
monitor communications, please see our privacy notice at <a moz-do-not-send="true" href="https://www.astrazeneca.com">
www.astrazeneca.com</a></font></p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p></o:p></span>
<p></p>
<div></div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended
recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone
or return mail.</span></p>
</body>
</html>