<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="-1">Anyone? </font><br>
<br>
<div class="moz-cite-prefix">On 10/07/15 11:07, Salvatore Di Nardo
wrote:<br>
</div>
<blockquote cite="mid:559F9960.7010509@ebi.ac.uk" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<font size="-1">Hello guys.<br>
Quite a while ago i mentioned that we have a big expel issue on
our gss ( first gen) and white a lot people suggested that the
root cause could be that we use the same interface for all the
traffic, and that we should split the data network from the
admin network. Finally we could plan a downtime and we are
migrating the data out so, i can soon safelly play with the
change, but looking what exactly i should to do i'm a bit
puzzled. Our mmlscluster looks like this:<br>
<br>
</font>
<blockquote>
<blockquote>
<blockquote><tt><font size="-1">GPFS cluster information</font></tt><tt><br>
</tt><tt><font size="-1">========================</font></tt><tt><br>
</tt><tt><font size="-1"> GPFS cluster name:
GSS.ebi.ac.uk</font></tt><tt><br>
</tt><tt><font size="-1"> GPFS cluster id:
17987981184946329605</font></tt><tt><br>
</tt><tt><font size="-1"> GPFS UID domain:
GSS.ebi.ac.uk</font></tt><tt><br>
</tt><tt><font size="-1"> Remote shell command:
/usr/bin/ssh</font></tt><tt><br>
</tt><tt><font size="-1"> Remote file copy command:
/usr/bin/scp</font></tt><tt><br>
</tt><tt><br>
</tt><tt><font size="-1">GPFS cluster configuration servers:</font></tt><tt><br>
</tt><tt><font size="-1">-----------------------------------</font></tt><tt><br>
</tt><tt><font size="-1"> Primary server:
gss01a.ebi.ac.uk</font></tt><tt><br>
</tt><tt><font size="-1"> Secondary server:
gss02b.ebi.ac.uk</font></tt><tt><br>
</tt><tt><br>
</tt><tt><font size="-1"> Node Daemon node name IP
address Admin node name Designation</font></tt><tt><br>
</tt><tt><font size="-1">-----------------------------------------------------------------------</font></tt><tt><br>
</tt><tt><font size="-1"> 1 gss01a.ebi.ac.uk
10.7.28.2 gss01a.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt><tt><font size="-1"> 2 gss01b.ebi.ac.uk
10.7.28.3 gss01b.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt><tt><font size="-1"> 3 gss02a.ebi.ac.uk
10.7.28.67 gss02a.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt><tt><font size="-1"> 4 gss02b.ebi.ac.uk
10.7.28.66 gss02b.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt><tt><font size="-1"> 5 gss03a.ebi.ac.uk
10.7.28.34 gss03a.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt><tt><font size="-1"> 6 gss03b.ebi.ac.uk
10.7.28.35 gss03b.ebi.ac.uk quorum-manager</font></tt><tt><br>
</tt></blockquote>
</blockquote>
</blockquote>
<font size="-1"><br>
It was my understanding that the "admin node" should use a
different interface ( a 1g link copper should be fine), while
the daemon node is where the data was passing , so should point
to the bonded 10g interfaces. but when i read the mmchnode man
page i start to be quite confused. It says:<br>
<br>
</font><font size="-1"><tt>
--daemon-interface={hostname | ip_address}</tt><tt><br>
</tt><tt> Specifies the host name or
IP address <u><b>to be used by the GPFS daemons for
node-to-node communication</b></u>. The host name or IP
address must refer to the communication adapter over which the
GPFS daemons communicate. <br>
Alias interfaces are not allowed. Use
the original address or a name that is resolved by the host
command to that original address.</tt><tt>
</tt><tt><br>
</tt><tt> </tt><tt><br>
</tt><tt> --admin-interface={hostname |
ip_address}</tt><tt><br>
</tt><tt> Specifies the name of the node
to be used by GPFS administration commands when communicating
between nodes. The admin node name must be specified as an IP
address or a hostname that is resolved by the host command <br>
to</tt><tt> </tt><tt>the desired IP
address. If the keyword DEFAULT is specified, the admin
interface for the node is set to be equal to the daemon
interface for the node.</tt><tt><br>
</tt></font><font size="-1"><br>
What exactly means "node-to node-communications" ? <br>
Means DATA or also the "lease renew", and the token
communication between the clients to get/steal the locks to be
able to manage concurrent write to thr same file? <br>
Since we are getting expells ( especially when several clients
contends the same file ) i assumed i have to split this type of
packages from the data stream, but reading the documentation it
looks to me that those internal comunication between nodes use
the daemon-interface wich i suppose are used also for the data.
so HOW exactly i can split them?<br>
</font><font size="-1"><br>
</font><font size="-1"><font size="-1"><font size="-1"><br>
Thanks in advance,<br>
Salvatore<br>
</font></font></font><font size="-1"><br>
</font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.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>
</body>
</html>