[gpfsug-discuss] mmauth/mmremotecluster wonkyness?

[Simon Thompson (IT Research Support)]

Um no, you are talking GPFS protocol between cluster nodes still in multicluster. Contact nodes are where the remote cluster goes to start with, but after that it's just normal node to node gpfs traffic (not just the contact nodes).

At least that is my understanding.

If you want traffic separation, you need something like AFM.

Simon
________________________________________
From: gpfsug-discuss-bounces at spectrumscale.org [gpfsug-discuss-bounces at spectrumscale.org] on behalf of valdis.kletnieks at vt.edu [valdis.kletnieks at vt.edu]
Sent: 30 November 2017 16:27
To: gpfsug-discuss at spectrumscale.org
Subject: [gpfsug-discuss] mmauth/mmremotecluster wonkyness?

We have a 10-node cluster running gpfs 4.2.2.3, where 8 nodes are GPFS contact
nodes for 2 filesystems, and 2 are protocol nodes doingNFS exports of the
filesystems.

But we see some nodes in remote clusters trying to GPFS connect to
the 2 protocol nodes anyhow.

My reading of the manpages is that the remote cluster is responsible
for setting '-n contactNodes' when they do the 'mmremotecluster add',
and there's no way to sanity check or enforce that at the local end, and
fail/flag connections to unintended non-contact nodes if the remote
admin forgets/botches the -n.

Is that actually correct?  If so, is it time for an RFE?