The remote cluster name does not match the cluster name supplied by the mmremotecluster command
There are error messages that gets displayed when the remote cluster name does not match with the cluster name that is provided by the mmremotecluster command, and the courses of action you can take to correct the problem.
A mount command fails with a message similar to this:
Cannot mount gpfslx2:gpfs66: Network is unreachable
and the GPFS log
contains message similar to this: Mon Jun 25 12:47:18 2007: Waiting to join remote cluster gpfslx2
Mon Jun 25 12:47:18 2007: Command: mount gpfslx2:gpfs66 27226
Mon Jun 25 12:47:18 2007: Failed to join remote cluster gpfslx2
Mon Jun 25 12:47:18 2007: Command err 719: mount gpfslx2:gpfs66 27226
Perform these steps:
- Verify that the remote cluster name reported by the mmremotefs show command is the same name as reported by the mmlscluster command from one of the contact nodes.
- Verify the list of contact nodes against the list of nodes as shown by the mmlscluster command from the remote cluster.
In this example, the correct cluster name is gpfslx2.ibm.com and
not gpfslx2
mmlscluster
Output is similar to this:
GPFS cluster information
========================
GPFS cluster name: gpfslx2.ibm.com
GPFS cluster id: 649437685184692490
GPFS UID domain: gpfslx2.ibm.com
Remote shell command: /usr/bin/ssh
Remote file copy command: /usr/bin/scp
Repository type: CCR
GPFS cluster configuration servers:
-----------------------------------
Primary server: gpfslx2.ibm.com
Secondary server: (none)
Node Daemon node name IP address Admin node name Designation
---------------------------------------------------------------------------
1 gpfslx2 198.117.68.68 gpfslx2.ibm.com quorum