[gpfsug-discuss] GPFS Network Configuration - 1 Daemon Network , 1 Admin Network

[Laurence Horrocks-Barlow]

All nodes in a GPFS cluster need to be able to communicate over the data 
and admin network with the exception of remote clusters which can have 
their own separate admin network (for their own cluster that they are a 
member of) but still require communications over the daemon network.

The networks can be routed and on different subnets, however the each 
member of the cluster will need to be able to communicate with every 
other member.

With this in mind:

1) The quorum node will need to be accessible on both the 10.1.1.0/24 
and 192.168.1.0/24 however again the network that the quorum node is on 
could be routed.
2) Remote clusters don't need access to the home clusters admin network, 
as they will use their own clusters admin network.

As Eric has mentioned I would double check your 2+1 cluster suggestion, 
do you mean 2 x Servers with NSD's (with a quorum role) and 1 quorum 
node without NSD's? which gives you 3 quorum, or are you only going to 
have 1 quorum?

If the latter that I would suggest using all 3 servers for quorum as 
they should be licensed as GPFS servers anyway due to their roles.

-- Lauz


On 10/04/2017 17:58, J. Eric Wonderley wrote:
> 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.
>
> 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.
>
>
>
> Eric Wonderley
>
> On Mon, Apr 10, 2017 at 12:47 PM, Hans-Joachim Ehlers 
> <service at metamodul.com <mailto:service at metamodul.com>> wrote:
>
>     My understanding of the GPFS networks is not quite clear.
>
>     For an GPFS setup i would like to use 2 Networks
>
>     1 Daemon (data)  network using port 1191 using for example.
>     10.1.1.0/24 <http://10.1.1.0/24>
>
>     2 Admin Network using for example: 192.168.1.0/24
>     <http://192.168.1.0/24> network
>
>     Questions
>
>     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 ?
>
>     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 ?
>
>     Note:
>
>     I am aware and read
>     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#%21/wiki/General%20Parallel%20File%20System%20%28GPFS%29/page/GPFS%20Network%20Communication%20Overview>
>
>     -- 
>     Unix Systems Engineer
>     --------------------------------------------------
>     MetaModul GmbH
>     Süderstr. 12
>     25336 Elmshorn
>     HRB: 11873 PI
>     UstID: DE213701983
>     Mobil: + 49 177 4393994 <tel:+49%20177%204393994>
>     Mail: service at metamodul.com <mailto:service at metamodul.com>
>
>
>     _______________________________________________
>     gpfsug-discuss mailing list
>     gpfsug-discuss at spectrumscale.org <http://spectrumscale.org>
>     http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>     <http://gpfsug.org/mailman/listinfo/gpfsug-discuss>
>
>
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170410/993178b8/attachment-0002.htm>