addnode

You can use the addnode command to add a new (candidate) node to an existing cluster. You can enter this command any time after a cluster has been created.

Syntax

Read syntax diagramSkip visual syntax diagram>>- svcservicetask -- -- addnode -- ---------------------------->

>--+- -panelname -- -- panel_name -+-- ------------------------->
   '- -wwnodename -- -- wwnn_arg --'

>--+----------------------------+-- ---------------------------->
   '- -name -- -- new_name_arg -'

>-- -iogrp -- --+- iogroup_name -+-----------------------------><
                '- iogroup_id ---'

Parameters

-panelname panel_name
Identifies the node to be added by the name as it appears on the display panel. This argument is mutually exclusive with -wwnodename; only one is required to uniquely identify the node.
-wwnodename wwnn_arg
Identifies the node to add to the cluster by the worldwide node name (WWNN) of the node. This argument is mutually exclusive with -panelname; only one is required to uniquely identify the node.
-name new_name_arg
Optionally specifies a name for this node.
-iogrp iogroup_name | iogroup_id
Specifies the I/O group to which you want to add this node.

Description

This command adds a new node to the cluster. You can obtain a list of candidate nodes (those that are not already assigned to a cluster) by typing svcinfo lsnodecandidate.

If the compatibility check fails, the following message displays:
CMMVC6201E The node could not be added, because incompatible
software: status code [%1].

Prerequisites: Before adding a node to the cluster, check the following:

Adding a node: If you are adding the node into the cluster for the first time, you must record the node serial number, the WWNN, all WWPN's, and the I/O group to which it has been added. This can avoid a possible data corruption exposure if the node must be removed from and readded to the cluster.

When a node is added to the cluster using the svctask addnode command or using the SAN Volume Controller Console, if the node has previously been a member of the cluster then either:

When you add a node to the cluster, you must also specify the I/O group to which this node will belong. I/O groups are identifiers for a node pair. The node pairs will internally duplicate cache data for a given set of virtual disks for redundancy of the cache data. When a virtual disk is created, it is also assigned to an I/O group. All data that is destined for this virtual disk is then cached on the two nodes in the I/O group.

When you add a node, make sure that the nodes within an I/O group are attached to different uninterruptible power supplies. You can determine the uninterruptible power supply to which a node is attached from the output of the svcinfo lsnodecandidate (uninterruptible power supply_unique_ID). The svcinfo lsnodes command displays the uninterruptible power supply to which all nodes (uninterruptible power supply_unique_ID), in the cluster are attached.

If you attempt to add a node to the cluster, it results in two nodes being attached to the same uninterruptible power supply, being put in the same I/O group, the svcservicetask addnode command will fail with the following error:
CMMVC5777E The node could not be added to the I/O group, because
the other node in the I/O group is in the same power domain.

Optionally, you can assign a name to the new node. You can use this name in subsequent commands to refer to the node, instead of using the WWNN (node ID). If you assign a label, this label is displayed as the node name from then on. If you do not assign a label, the default label is nodeX, where X is the node ID.

Example: When 2 nodes of a 4 node cluster have been lost because of a complete failure of an uninterruptible power supply, the two lost nodes must be added back into the cluster using the svcservicetask addnode command or using the SAN Volume Controller Console.

Applications on a host system direct I/O operations to filesystems or logical volumes which are mapped by the operating system to vpaths, which are pseudo disk objects supported by the SDD driver. See the IBM TotalStorage Subsystem Device Driver: User's Guide for more information.

The SDD driver maintains an association between a vpath and a SAN Volume Controller VDisk. This association uses an identifier (UID), which is unique to the VDisk and is not reused. This enables the SDD driver to unambiguously associate vpaths with VDisks.

The SDD device driver operates within a protocol stack, which also contains disk and fibre-channel device drivers that enable it to communicate with the SAN Volume Controller using the SCSI protocol over fibre-channel as defined by the ANSI FCS standard. The addressing scheme provided by these SCSI and fibre-channel device drivers uses a combination of a SCSI logical unit number (LUN) and the world wide name for the fibre-channel node and ports.

In the event of errors occurring, error recovery procedures (ERPs) operate at various tiers in the protocol stack. Some of these ERPs cause I/O to be redriven using the same WWNN and LUN numbers which were previously used.

The SDD device driver does not check the association of the VDisk with the vpath on every I/O operation that it performs.

Possible failures

Examples

An invocation example

svcservicetask addnode -wwnodename 210000e08b053564 -iogrp io_grp0

The resulting output

Node, id [6], successfully added

(C) Copyright International Business Machines Corporation 2003, 2004