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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

v A node being deleted cannot be the primary or backup NSD server for any disk in the <strong>GPFS</strong> cluster<br />

unless you intend to delete the entire cluster. Verify this by issuing the mmlsnsd comm<strong>and</strong>. If a node to<br />

be deleted is an NSD server for one or more disks, move the disks to nodes that will remain in the<br />

cluster <strong>and</strong> use the mmchnsd comm<strong>and</strong> to assign new NSD servers for those disks.<br />

v <strong>GPFS</strong> must be shut down on the nodes being deleted. Use the mmshutdown comm<strong>and</strong>.<br />

To delete the nodes listed in a file called nodes_to_delete, enter:<br />

mmdelnode -N /tmp/nodes_to_delete<br />

where nodes_to_delete contains the nodes k164n01 <strong>and</strong> k164n02. The system displays information<br />

similar to:<br />

Verifying <strong>GPFS</strong> is stopped on all affected nodes ...<br />

mmdelnode: Comm<strong>and</strong> successfully completed<br />

mmdelnode: 6027-1371 Propagating the cluster configuration data to<br />

all affected nodes. This is an asynchronous process.<br />

To confirm the deletion of the nodes, enter:<br />

mmlscluster<br />

The system displays information similar to:<br />

<strong>GPFS</strong> cluster information<br />

========================<br />

<strong>GPFS</strong> cluster name: cluster1.kgn.ibm.com<br />

<strong>GPFS</strong> cluster id: 680681562214606028<br />

<strong>GPFS</strong> UID domain: cluster1.kgn.ibm.com<br />

Remote shell comm<strong>and</strong>: /usr/bin/rsh<br />

Remote file copy comm<strong>and</strong>: /usr/bin/rcp<br />

<strong>GPFS</strong> cluster configuration servers:<br />

-----------------------------------<br />

Primary server: k164sn06.kgn.ibm.com<br />

Secondary server: k164n05.kgn.ibm.com<br />

Node Daemon node name IP address Admin node name Designation<br />

-------------------------------------------------------------------------------------<br />

1 k164n04.kgn.ibm.com 198.117.68.68 k164n04.kgn.ibm.com quorum<br />

2 k164n05.kgn.ibm.com 198.117.68.69 k164n05.kgn.ibm.com quorum<br />

3 k164n06.kgn.ibm.com 198.117.68.70 k164sn06.kgn.ibm.com quorum-manager<br />

See the “mmdelnode Comm<strong>and</strong>” on page 159 <strong>and</strong> the “mmlscluster Comm<strong>and</strong>” on page 198 for complete<br />

usage information.<br />

Exercise caution when shutting down <strong>GPFS</strong> on quorum nodes or deleting quorum nodes from the <strong>GPFS</strong><br />

cluster. If the number of remaining quorum nodes falls below the requirement for a quorum, you will be<br />

unable to perform file system operations. See the General Parallel File System: Concepts, Planning, <strong>and</strong><br />

Installation Guide <strong>and</strong> search on quorum.<br />

Changing the <strong>GPFS</strong> cluster configuration data<br />

Once your <strong>GPFS</strong> cluster has been configured (see the General Parallel File System: Concepts, Planning,<br />

<strong>and</strong> Installation Guide <strong>and</strong> the mmcrcluster comm<strong>and</strong>), you can change configuration attributes by issuing<br />

the mmchcluster or mmchconfig comm<strong>and</strong>s. Use the mmchcluster comm<strong>and</strong> to:<br />

v Change the name of the cluster.<br />

v Specify node interfaces to be used by the <strong>GPFS</strong> administration comm<strong>and</strong>s.<br />

6 <strong>GPFS</strong>: <strong>Administration</strong> <strong>and</strong> <strong>Programming</strong> <strong>Reference</strong>

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

Saved successfully!

Ooh no, something went wrong!