source: gpfs_3.1_ker2.6.20/share/man/man8/mmremotecluster.8 @ 16

.TH mmremotecluster 02/16/06
mmremotecluster Command
.SH "Name"
.PP
\fBmmremotecluster\fR - Manages the information about other GPFS
clusters that this cluster can access when mounting remote GPFS file
systems.
.SH "Synopsis"
.PP
\fBmmremotecluster\fR \fBadd \fR \fIRemoteClusterName\fR
[\fB-n\fR \fIContactNodes\fR] [\fB-k\fR
\fIKeyFile\fR]
.PP
Or,
.PP
\fBmmremotecluster\fR \fBupdate\fR \fIRemoteClusterName\fR
[\fB-C\fR \fINewClusterName\fR] [\fB-n\fR
\fIContactNodes\fR] [\fB-k\fR \fIKeyFile\fR]
.PP
Or,
.PP
\fBmmremotecluster\fR \fBdelete {\fR\fIRemoteClusterName\fR\fB |
all}\fR
.PP
Or,
.PP
\fBmmremotecluster\fR \fBshow\fR [\fIRemoteClusterName\fR\fB
| all\fR]
.SH "Description"
.PP
The \fBmmremotecluster\fR command is used to make remote GPFS clusters
known to the local cluster, and to maintain the attributes associated with
those remote clusters. The keyword appearing after
\fBmmremotecluster\fR determines which action is performed:
.PP
.RS +3
\fBadd
\fR
.RE
.RS +9
Adds a remote GPFS cluster to the set of remote clusters known to the
local cluster.
.RE
.PP
.RS +3
\fBdelete
\fR
.RE
.RS +9
Deletes the information for a remote GPFS cluster.
.RE
.PP
.RS +3
\fBshow
\fR
.RE
.RS +9
Displays information about a remote GPFS cluster.
.RE
.PP
.RS +3
\fBupdate
\fR
.RE
.RS +9
Updates the attributes of a remote GPFS cluster.
.RE
.PP
To be able to mount file systems that belong to some other GPFS cluster,
you must first make the nodes in this cluster aware of the GPFS cluster that
owns those file systems. This is accomplished with the
\fBmmremotecluster add\fR command. The information that the command
requires must be provided to you by the administrator of the remote GPFS
cluster. You will need this information:
.RS +3
.HP 3
\(bu The name of the remote cluster.
.HP 3
\(bu The names or IP addresses of a few nodes that belong to the remote GPFS
cluster.
.HP 3
\(bu The public key file generated by the administrator of the remote cluster
by running the
\fBmmauth genkey\fR command for the
remote cluster.
.RE
.PP
Since each cluster is managed independently, there is no automatic
coordination and propagation of changes between clusters like there is between
the nodes within a cluster. This means that once a remote cluster is
defined with the \fBmmremotecluster\fR command, the information about that
cluster is automatically propagated across all nodes that belong to this
cluster. But if the administrator of the remote cluster decides to
rename it, or deletes some or all of the contact nodes, or change the public
key file, the information in this cluster becomes obsolete. It is the
responsibility of the administrator of the remote GPFS cluster to notify you
of such changes so that you can update your information using the appropriate
options of the \fBmmremotecluster update\fR command.
.SH "Parameters"
.PP
.RS +3
\fB\fIRemoteClusterName\fR
\fR
.RE
.RS +9
Specifies the cluster name associated with the remote cluster that owns
the remote GPFS file system. The value \fBall\fR indicates all
remote clusters defined to this cluster, when using the \fBmmremotecluster
delete\fR or \fBmmremotecluster show \fR commands.
.RE
.PP
.RS +3
\fB-C \fINewClusterName\fR
\fR
.RE
.RS +9
Specifies the new cluster name to be associated with the remote
cluster.
.RE
.PP
.RS +3
\fB-k \fIKeyFile\fR
\fR
.RE
.RS +9
Specifies the name of the public key file provided to you by the
administrator of the remote GPFS cluster. This could be relative path
(therefore just a need to name the file) or an absolute path (need full path
name, but just file name).
.RE
.PP
.RS +3
\fB-n \fIContactNodes\fR
\fR
.RE
.RS +9
A comma separated list of nodes that belong to the remote GPFS cluster, in
this format:
.sp
.nf
[tcpPort=NNNN,]node1[,node2 ...]
.fi
.sp
.PP
where: 
.RS +3
.HP 3
\(bu tcpPort=NNNN is the TCP port number to be used by the local
GPFS daemon when contacting the remote cluster. If not specified, GPFS
will use the default TCP port number 1191.
.HP 3
\(bu node1[,node2 ...] is a list of nodes that
belong to the remote cluster. The nodes can be identified through their
host names or IP addresses.
.RE
.RE
.SH "Options"
.PP
None.
.SH "Exit status"
.PP
.PP
.RS +3
\fB0
\fR
.RE
.RS +9
Successful completion. After successful completion of the
\fBmmremotecluster\fR command, the new configuration information is
propagated to all nodes in the cluster.
.RE
.PP
.RS +3
\fBnonzero
\fR
.RE
.RS +9
A failure has occurred.
.RE
.SH "Security"
.PP
You must have root authority to run the \fBmmremotecluster\fR
command.
.PP
You may issue the \fBmmremotecluster\fR command from any node in the
GPFS cluster.
.SH "Examples"
.RS +3
.HP 3
1. This command adds remote cluster
\fBk164.kgn.ibm.com\fR to the set of remote clusters
known to the local cluster, specifying \fBk164n02\fR and \fBk164n03\fR
as remote contact nodes. File \fBk164.id_rsa.pub\fR is
the name of the public key file provided to you by the administrator of the
remote cluster.
.sp
.nf
mmremotecluster add k164.kgn.ibm.com -n k164n02,k164n03\\
 -k k164.id_rsa.pub
.fi
.sp
The output is similar to this:
.sp
.nf
mmremotecluster: 6027-1371 Propagating the changes to all\ 
affected nodes. This is an asynchronous process.
.fi
.sp
.HP 3
2. This command displays information for the remote cluster
\fBk164.kgn.ibm.com\fR.
.sp
.nf
mmremotecluster show k164.kgn.ibm.com
.fi
.sp
The output is similar to this:
.sp
.nf
Cluster name:    k164.kgn.ibm.com
Contact nodes:   k164n02,k164n03
SHA digest:      a3917c8282fca7a27d951566940768dcd241902b
File systems:    (none defined)
.fi
.sp
.sp
For more information on the SHA digest, see
\fIGeneral Parallel File System: Problem
Determination Guide\fR and search on \fISHA digest\fR.
.HP 3
3. This command updates information for the remote cluster
\fBk164.kgn.ibm.com\fR, changing the remote contact
nodes to \fBk164n02\fR and \fBk164n01\fR. The TCP port to be used
when contacting cluster \fBk164.kgn.ibm.com\fR is
defined to be 6667..
.sp
.nf
mmremotecluster update k164.kgn.ibm.com 
-n tcpPort=6667,k164n02,k164n01
.fi
.sp
The output is similar to this:
.sp
.nf
mmremotecluster: 6027-1371 Propagating the changes to all\ 
affected nodes. This is an asynchronous process.
.fi
.sp
.sp
The \fBmmremotecluster show\fR command can then be used to see
the changes.
.sp
.nf
mmremotecluster show k164.kgn.ibm.com
.fi
.sp
.sp
The output is similar to this:
.sp
.nf
Cluster name:    k164.kgn.ibm.com
Contact nodes: tcpPort=6667,k164n02,k164n01
SHA digest:      a3917c8282fca7a27d951566940768dcd241902b
File systems:    (none defined)
.fi
.sp
.sp
For more information on the SHA digest, see
\fIGeneral Parallel File System: Problem
Determination Guide\fR and search on \fISHA digest\fR.
.HP 3
4. This command deletes information for remote cluster
\fBk164.kgn.ibm.com\fR from the local cluster.
.sp
.nf
mmremotecluster delete k164.kgn.ibm.com
.fi
.sp
The output is similar to this:
.sp
.nf
mmremotecluster: 6027-1371 Propagating the changes to all\ 
affected nodes. This is an asynchronous process.
.fi
.sp
.RE
.SH "See also"
.PP
mmauth Command
.PP
mmremotefs Command
.PP
\fIAccessing GPFS file systems from other
GPFS clusters\fR in
\fIGeneral Parallel
File System: Advanced Administration Guide\fR.
.SH "Location"
.PP
\fB/usr/lpp/mmfs/bin\fR
.PP