29.01.2013 Views

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NodeDesc[,NodeDesc...]<br />

Specifies the list of nodes <strong>and</strong> node designations to be included in the <strong>GPFS</strong> cluster. Node<br />

descriptors are defined as:<br />

NodeName:NodeDesignations:AdminNodeName<br />

where:<br />

1. NodeName is the hostname or IP address to be used by the <strong>GPFS</strong> daemon for node to node<br />

communication.<br />

The hostname or IP address must refer to the communications adapter over which the <strong>GPFS</strong><br />

daemons communicate. Alias interfaces are not allowed. Use the original address or a name<br />

that is resolved by the host comm<strong>and</strong> to that original address. You may specify a node using<br />

any of these forms:<br />

Format Example<br />

Short hostname k145n01<br />

Long hostname k145n01.kgn.ibm.com<br />

IP address 9.119.19.102<br />

2. NodeDesignations is an optional, ’-’ separated list of node roles.<br />

mmcrcluster Comm<strong>and</strong><br />

v manager | client Indicates whether a node is part of the pool of nodes from which<br />

configuration managers, file system managers, <strong>and</strong> token managers are selected. The<br />

default is client.<br />

v quorum | nonquorum Indicates whether a node is counted as a quorum node. The default<br />

is nonquorum.<br />

3. AdminNodeName is an optional field that consists of a node name to be used by the<br />

administration comm<strong>and</strong>s to communicate between nodes.<br />

If AdminNodeName is not specified, the NodeName value is used.<br />

You must provide a descriptor for each node to be added to the <strong>GPFS</strong> cluster.<br />

-p PrimaryServer<br />

Specifies the primary <strong>GPFS</strong> cluster configuration server node used to store the <strong>GPFS</strong><br />

configuration data. This node must be a member of the <strong>GPFS</strong> cluster.<br />

-R RemoteFileCopy<br />

Specifies the fully-qualified path name for the remote file copy program to be used by <strong>GPFS</strong>. The<br />

default value is /usr/bin/rcp.<br />

The remote copy comm<strong>and</strong> must adhere to the same syntax format as the rcp comm<strong>and</strong>, but may<br />

implement an alternate authentication mechanism.<br />

-r RemoteShellComm<strong>and</strong><br />

Specifies the fully-qualified path name for the remote shell program to be used by <strong>GPFS</strong>. The<br />

default value is /usr/bin/rsh.<br />

The remote shell comm<strong>and</strong> must adhere to the same syntax format as the rsh comm<strong>and</strong>, but may<br />

implement an alternate authentication mechanism.<br />

-s SecondaryServer<br />

Specifies the secondary <strong>GPFS</strong> cluster configuration server node used to store the <strong>GPFS</strong> cluster<br />

data. This node must be a member of the <strong>GPFS</strong> cluster.<br />

It is suggested that you specify a secondary <strong>GPFS</strong> cluster configuration server to prevent the loss<br />

of configuration data in the event your primary <strong>GPFS</strong> cluster configuration server goes down.<br />

When the <strong>GPFS</strong> daemon starts up, at least one of the two <strong>GPFS</strong> cluster configuration servers<br />

must be accessible.<br />

Chapter 8. <strong>GPFS</strong> comm<strong>and</strong>s 115

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!