chnode

Use the chnode command to change the name that is assigned to a node as well as other options. You can then use the new name when running subsequent commands. All parameters that are associated with this command are optional. However, you must specify one or more parameters.

Syntax

Read syntax diagramSkip visual syntax diagram chnode -iscsialiasalias-noiscsialias-failover-namenew_node_or_nodecanister_name-identifyyesno-sitesite_idsite_name-nositeobject_idobject_name

Parameters

-iscsialias alias
(Optional) Specifies the iSCSI name of the node. The maximum length is 79 characters. Do not use spaces for the iSCSI alias name.
Important: You can specify this parameter for online spares nodes.
-noiscsialias
(Optional) Clears any previously set iSCSI name for this node. This parameter cannot be specified with the iscsialias parameter.
Important: You can specify this parameter for online spares nodes.
-failover
(Optional) Specifies that the name or iSCSI alias being set is the name or alias of the partner node in the I/O group. When there is no partner node, the values set are applied to the partner node when it is added to the system. If this parameter is used when there is a partner node, the name or alias of that node changes.
Important: You can specify this parameter for online spares nodes.
-name new_node_or_nodecanister_name
(Optional) Specifies the name to assign to the node.
Note: Node names supplied with -name on chnode commands must not be in use already as node names or as node failover names.
Important: The iSCSI Qualified Name (IQN) for each node is generated using the clustered system and node names. If you are using the iSCSI protocol, changing either name also changes the IQN of all of the nodes in the clustered system and might require reconfiguration of all iSCSI-attached hosts.
-identify yes | no
(Optional) Allows you to control the light-emitting diode (LED) used on the node. The values are yes or no.
Important: You can specify this parameter for online spares nodes.
-site site_id | site_name
(Optional) Specifies the numeric site value or site name for the existing node. The value is 1 or 2.
-nosite
(Optional) Resets the site value.
object_id | object_name
(Required) Specifies the object name or ID that you want to modify. The variable that follows the parameter is either:
  • The object name that you assigned when you added the node to the clustered system
  • The object ID that is assigned to the node (not the worldwide node name)

Description

If the failover parameter is not specified, this command changes the name or iSCSI alias of the node. The name can then be used to identify the node in subsequent commands.

The failover parameter is used to specify values that are normally applied to the partner node in the I/O group. When the partner node is offline, the iSCSI alias and IQN are assigned to the remaining node in the I/O Group. The iSCSI host data access is then preserved. If the partner node is offline when these parameters are set, the node they are set on handles iSCSI I/O requests to the iSCSI alias specified, or the IQN that is created using the node name. If the partner node in the I/O group is online when these parameters are set, the partner node handles iSCSI requests to the iSCSI alias specified, and its node name and IQN change.

To change the name of the node (with I/O running) :
  1. Make sure the host system has active sessions with both node canisters in the I/O group (hosting the volume on which the I/O occurs).
  2. Change name of one node canister using chnode command.
  3. From the host system, log out of the node canister whose name changes.
  4. Rediscover the target iSCSI qualified name (IQN) from the host using the host operating system's discovery mechanism.
  5. Login with the new target IQN discovered on the host system, and make sure the login succeeds.
  6. Repeat steps 2-5 with the other node canister.
Note: When using VMware ESX, delete the static paths (in the iSCSI initiator properties) that contain the old target IQN.
This ensures that the node canister name change does not impact iSCSI I/O during events such as a target failover.

An invocation example

chnode -name newname -identify yes node8

The resulting output:

No feedback