ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/addcrgnode.htm

290 lines
13 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Add CRG Node Entry (ADDCRGNODE)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="ADDCRGNODE.Top_Of_Page"></a>
<h2>Add CRG Node Entry (ADDCRGNODE)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#ADDCRGNODE.PARAMETERS.TABLE">Parameters</a><br>
<a href="#ADDCRGNODE.COMMAND.EXAMPLES">Examples</a><br>
<a href="#ADDCRGNODE.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="ADDCRGNODE"></a>
<p>The Add Cluster Resource Group Node Entry (ADDCRGNODE) command is used to add a new node to the recovery domain of an existing cluster resource group. This command results in the preferred recovery domain and the current recovery domain being updated.
</p>
<p>For primary-backup model cluster resource groups, the node can be added as another backup node, as a replicate node, or as the new primary node in the cluster resource group's recovery domain. A node can only be added as a primary node if the cluster resource group has a status of Inactive. When a new node is added as the primary, the old primary node becomes the last backup. If the cluster resource group has a status of Active, a node can be added as either a backup or a replicate.
</p>
<p>For peer model cluster resource groups, the node can be added as a peer node or a replicate node. If the cluster resource group has a status of Active (10) and a peer node is added, the node will be added as an active access point.
</p>
<p>A node can be added to a resilient device cluster resource group even if it has no device entries. Device entries must be added using the Add Cluster Resource Group Device Entry (ADDCRGDEVE) command before the cluster resource group can be started. If the node being added to a device cluster resource group is to become the new primary node, ownership of the devices specified are switched from the current primary to the new primary if none of the devices are varied on for the current primary. If any devices are varied on, an error message is returned. Devices are not varied on after the ownership is switched.
</p>
<p>If a node is being added to a resilient device cluster resource group recovery domain with a site name and data port IP address, the node will be added to the recovery domain and then the QcstChangeClusterResourceGroup API will be used to add the site name and data port IP address to the node. If there is a failure due to the QcstChangeClusterResourceGroup call, then the node will be removed from the recovery domain.
</p>
<p><b>Restrictions:</b>
</p>
<ol>
<li>You must have input/output system configuration (*IOSYSCFG) special authority to run this command.
</li>
<li>This command cannot be called from a cluster resource group exit program.
</li>
<li>The node being added to the recovery domain must not already be a member of this cluster resource group's recovery domain.
</li>
<li>For primary-backup model cluster resource groups, to add a node as the primary the cluster resource group must be Inactive.
</li>
<li>Cluster Resource Services must be active on the node processing the request.
</li>
<li>There must be at least one active node in the recovery domain.
</li>
<li>The node being added must be active in the cluster.
</li>
<li>The cluster resource group exit program must exist on each node in the recovery domain, including the node being added.
</li>
<li>The node being added must be unique in the recovery domain of the cluster resource group specified.
</li>
<li>If a node is being added to a resilient device cluster resource group:
<ol>
<li>A node can be added to a cluster resource group even if it has no device entries. Device entries must be added using the Add Cluster Resource Group Device Entry (ADDCRGDEVE) command before the cluster resource group can be started.
</li>
<li>The node must be in the same device domain as the other nodes in the recovery domain.
</li>
<li>The configuration objects for the device resources in the cluster resource group must exist on the node being added and the resource names in the configuration objects must be the same as the resource names used by the configuration objects on the existing nodes in the recovery domain. The node being added must be able to access the hardware resources represented by the configuration objects in the cluster resource group.
</li>
<li>If a data base name is specified in the configuration objects in the cluster resource group, it must be the same on the node being added.
</li>
<li>All members of an auxiliary storage pool group must be configured in the cluster resource group before ownership of the auxiliary storage pool can be changed.
</li>
<li>If a server takeover IP address is specified in the cluster resource group and the cluster resource group is active, the server takeover IP address must exist.
</li>
</ol>
</li>
</ol>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="ADDCRGNODE.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top"><a href="#ADDCRGNODE.CLUSTER"><b>CLUSTER</b></a></td>
<td valign="top">Cluster</td>
<td valign="top"><i>Name</i></td>
<td valign="top">Required, Positional 1</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCRGNODE.CRG"><b>CRG</b></a></td>
<td valign="top">Cluster resource group</td>
<td valign="top"><i>Name</i></td>
<td valign="top">Required, Positional 2</td>
</tr>
<tr>
<td valign="top" rowspan="6"><a href="#ADDCRGNODE.RCYDMN"><b>RCYDMN</b></a></td>
<td valign="top">Recovery domain node list</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="6">Required, Positional 3</td>
</tr>
<tr>
<td valign="top">Element 1: Node identifier</td>
<td valign="top">
<i>Name</i></td>
</tr>
<tr>
<td valign="top">Element 2: Node role</td>
<td valign="top">
<b><u>*CRGTYPE</u></b>, *PRIMARY, *BACKUP, *REPLICATE, *PEER</td>
</tr>
<tr>
<td valign="top">Element 3: Backup sequence number</td>
<td valign="top">
1-127, <b><u>*LAST</u></b></td>
</tr>
<tr>
<td valign="top">Element 4: Site name</td>
<td valign="top">
<i>Name</i>, <b><u>*NONE</u></b></td>
</tr>
<tr>
<td valign="top">Element 5: Data port IP address</td>
<td valign="top">
Single values: <b><u>*NONE</u></b><br>Other values (up to 4 repetitions): <i>Character value</i></td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="ADDCRGNODE.CLUSTER"></a>
<h3>Cluster (CLUSTER)</h3>
<p>Specifies the cluster where the cluster resource group exists.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the cluster where the cluster resource group exists.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCRGNODE.CRG"></a>
<h3>Cluster resource group (CRG)</h3>
<p>Specifies the cluster resource group that will have the new node added to its recovery domain.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the cluster resource group.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCRGNODE.RCYDMN"></a>
<h3>Recovery domain node list (RCYDMN)</h3>
<p>Specifies the node and role for the node being added to the recovery domain of the cluster resource group specified for the <b>Cluster resource group (CRG)</b> parameter.
</p>
<p>This is a required parameter.
</p>
<p><b>Element 1: Node identifier</b>
</p>
<p>Specifies the node being added.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the cluster node.
</dd>
</dl>
<p><b>Element 2: Node role</b>
</p>
<p>Specifies the role the node being added is to have in the recovery domain of the cluster resource group specified. For primary-backup model cluster resource groups a node can have one of three roles: primary, backup, or replicate. For peer model cluster resource groups a node can have one of two roles: peer or replicate. Any number of nodes can be designated as a peer or replicate. The following summarizes the valid values for the node being added:
</p>
<dl>
<dt><b><u>*CRGTYPE</u></b></dt>
<dd>The node role will be set based on the type of the cluster resource group. If the type of cluster resource group is *PEER the default for the node role will be *PEER. For any other type of cluster resource group the default will be *BACKUP.
</dd>
<dt><b>*PRIMARY</b></dt>
<dd>The new node will be added as the primary node. The cluster resource group must have a status of Inactive.
</dd>
<dt><b>*BACKUP</b></dt>
<dd>The new node will be added as a backup node.
</dd>
<dt><b>*REPLICATE</b></dt>
<dd>The new node will be added as a replicate. Replicates are not ordered and cannot become an access point unless changed to a proper role for the given cluster resource group type.
</dd>
<dt><b>*PEER</b></dt>
<dd>The new node will be added as a peer. Peer nodes are not ordered and can become an active access point for the cluster resources.
</dd>
</dl>
<p><b>Element 3: Backup sequence number</b>
</p>
<p>Specifies the backup order for a node with role of *BACKUP. If there is already a node with the same backup order, the new node is inserted in the position requested. At the completion of the request, the nodes with backup roles will be sequentially renumbered from the first backup to the last. The first backup will always be 1.
</p>
<dl>
<dt><b><u>*LAST</u></b></dt>
<dd>The new node will be added as the last backup in the recovery domain.
</dd>
<dt><b><i>1-127</i></b></dt>
<dd>Specify the backup sequence number to be used.
</dd>
</dl>
<p><b>Element 4: Site name</b>
</p>
<p>Specifies the site name of the recovery domain node. This is valid only for a device cluster resource group, specifically for geographic mirroring. A site contains a subset of recovery domain nodes in the same physical location. All nodes at a site have access to the same copy of auxiliary storage pool.
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>The recovery domain node does not have a site name.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the site name for a recovery domain node.
</dd>
</dl>
<p><b>Element 5: Data port IP address</b>
</p>
<p>Specifies the data port IP address for the recovery domain node. This is valid only for a device cluster resource group, specifically for geographic mirroring. The data port IP address is used to to send updates from a source node that owns the production copy of auxiliary storage pool to a target node that owns the mirror copy of auxiliary storage pool.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>The recovery domain node does not have a data port IP address.
</dd>
</dl>
<p><b>Other values (up to 4 repetitions)</b>
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the data port IP address for the recovery domain node.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDCRGNODE.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Adding a Backup Node to a CRG Recovery Domain</b>
</p>
<p>
<pre>
ADDCRGNODE CLUSTER(MYCLUSTER) CRG(MYCRG) RCYDMN(NODE1 *BACKUP 3)
</pre>
</p>
<p>This command adds node NODE1 to the recovery domain of cluster resource group MYCRG in the cluster called MYCLUSTER. The node is added as the third backup node. Any existing backup nodes will be renumbered sequentially.
</p>
<p><b>Example 2: Adding a Node with Multiple Dataport IP Addresses</b>
</p>
<p>
<pre>
ADDCRGNODE CLUSTER(MYCLUSTER) CRG(MYCRG)
RCYDMN(NODE1 *BACKUP *LAST MYSITE ('1.1.1.1' '2.2.2.2'))
</pre>
</p>
<p>This command adds node NODE1 to the recovery domain of cluster resource group MYCRG in the cluster called MYCLUSTER. The node is added as the last backup node in the site MYSITE with 2 data port IP addresses.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDCRGNODE.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF1999</b></dt>
<dd>Errors occurred on command.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCRGNODE.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>