>>- svctask -- -- addnode -- -----------------------------------> >--+- -panelname -- -- panel_name -+-- -------------------------> '- -wwnodename -- -- wwnn_arg --' >--+----------------------------+-- ----------------------------> '- -name -- -- new_name_arg -' >-- -iogrp -- --+- iogroup_name -+----------------------------->< '- iogroup_id ---'
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.
Node addition completes asynchronously. This means while the node is in adding state, the WWPN is not known and will display as zeroes.
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:
| Attention: If the conditions listed above apply, then failure to follow the procedures documented here, may result in the corruption of all data managed by the cluster. |
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 re-added 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:
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 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.
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.
An invocation example
svctask addnode -wwnodename 210000e08b053564 -iogrp io_grp0
The resulting output
Node, id [6], successfully added