<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>Sorry for not being clear. The setup is of course a 3 Node Cluster where each node is a quorum node - 2 NSD Server and 1 TieBreaker/Quorum Buster node.<br></p><p>For me it was not clear if the Tiebreaker/Quorum Buster node - which does nothing in terms of data serving - must be part of the daemon/data network or not.<br></p><p>So i get the understanding that a Tiebreaker Node must be also part of the Daemon network.<br></p><p>Thx a lot to all<br></p><p>Hajo<br></p><p><br></p><p><br></p><blockquote><p>"Simon Thompson (IT Research Support)" <S.J.Thompson@bham.ac.uk> hat am 10. April 2017 um 19:26 geschrieben:</p><p>If you have network congestion, then a separate admin network is of benefit. Maybe less important if you have 10GbE networks, but if (for example), you normally rely on IB to talk data, and gpfs fails back to the Ethernet (which may be only 1GbE), then you may have cluster issues, for example missing gpfs pings.</p><p>Having a separate physical admin network can protect you from this.</p><p>Having been bitten by this several years back, it's a good idea IMHO to have a separate admin network.</p><p>Simon</p><p>________________________________________<br>From: gpfsug-discuss-bounces@spectrumscale.org [gpfsug-discuss-bounces@spectrumscale.org] on behalf of J. Eric Wonderley [eric.wonderley@vt.edu]<br>Sent: 10 April 2017 17:58<br>To: gpfsug main discussion list<br>Subject: Re: [gpfsug-discuss] GPFS Network Configuration - 1 Daemon Network , 1 Admin Network</p><p>1) You want more that one quorum node on your server cluster. The non-quorum node does need a daemon network interface exposed to the client cluster as does the quorum nodes.</p><p>2) No. Admin network is for intra cluster communications...not inter cluster(between clusters). Daemon interface(port 1191) is used for communications between clusters. I think there is little benefit gained by having designated an admin network...maybe someone can point out benefits of an admin network.</p><p>Eric Wonderley</p><p>On Mon, Apr 10, 2017 at 12:47 PM, Hans-Joachim Ehlers <service@metamodul.com<mailto:service@metamodul.com>> wrote:</p><p>My understanding of the GPFS networks is not quite clear.</p><p>For an GPFS setup i would like to use 2 Networks</p><p>1 Daemon (data) network using port 1191 using for example. 10.1.1.0/24<http://10.1.1.0/24></p><p>2 Admin Network using for example: 192.168.1.0/24<http://192.168.1.0/24> network</p><p>Questions</p><p>1) Thus in a 2+1 Cluster ( 2 GPFS Server + 1 Quorum Server ) Config - Does the Tiebreaker Node needs to have access to the daemon(data) 10.1.1. network or is it sufficient for the tiebreaker node to be configured as part of the admin 192.168.1 network ?</p><p>2) Does a remote cluster needs access to the GPFS Admin 192.168.1 network or is it sufficient for the remote cluster to access the 10.1.1 network ? If so i assume that remotecluster commands and ping to/from remote cluster are going via the Daemon network ?</p><p>Note:</p><p>I am aware and read <a href="https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/GPFS%20Network%20Communication%20Overview">https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General%20Parallel%20File%20System%20(GPFS)/page/GPFS%20Network%20Communication%20Overview</a></p><p>--</p><p>Unix Systems Engineer</p><p>--------------------------------------------------<br>MetaModul GmbH<br>Süderstr. 12<br>25336 Elmshorn<br>HRB: 11873 PI<br>UstID: DE213701983<br>Mobil: + 49 177 4393994<tel:+49%20177%204393994><br>Mail: service@metamodul.com<mailto:service@metamodul.com></p><p>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<http://spectrumscale.org><br><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></p><p>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></p></blockquote></body></html>