Add CRG Device Entry (ADDCRGDEVE)

Where allowed to run: All environments (*ALL)
Threadsafe: Yes

The Add Cluster Resource Group Device Entry (ADDCRGDEVE) command is used to add one or more configuration objects representing resilient hardware devices to a device cluster resource group. All devices being added must be able to be switched from one cluster node to another. When the cluster resource group is switched over or failed over to the first backup system, all devices in the device list are moved to the backup system.

If the cluster resource group contains any members of an auxiliary storage pool group, it must contain all members before the cluster resource group can be started. All members do not have to be specified at once. Additional members can be added later. If the auxiliary storage pool group has previously been created and clustering can determine which members are in the group, a warning message is sent if some members of the group were not added.

If an exit program is specified for the cluster resource group, the cluster resource group exit program is called with an action code of Add Device Entry on all active nodes in the recovery domain. The cluster resource group status is set to Add Device Entry Pending. If the exit program completes successfully, the cluster resource group status is reset to its value at the time the command was called. If the exit program fails and the cluster resource group cannot be restored to its original condition, the cluster resource group status is set to Indoubt.

Restrictions:

You must have input/output system configuration (*IOSYSCFG) special authority on all nodes in the recovery domain to run this command.
This command cannot be called from a cluster resource group exit program.
Cluster Resource Services must be active on the node processing the request.
The number of configuration objects being added plus the number of configuration objects already in the cluster resource group cannot exceed 256.
The configuration objects being added cannot be specified in another cluster resource group.
If the primary node does not currently own the specified devices, the command fails with an error message.
All nodes in the recovery domain must be active.
For the configuration objects specified:
1. Only these configuration object types are supported. The cluster version must be 6 or greater for devices other than auxiliary storage pool devices. A cluster resource group with sites defined can only have auxiliary storage pool devices.
  1. An auxiliary storage pool device.
  2. An asynchronous communications device.
  3. A binary synchronous communications device.
  4. A cryptographic device.
  5. A distributed data interface communication line.
  6. An Ethernet communication line.
  7. A facsimile communication line.
  8. A network server device for a guest operating system (Linux) running in a logical partition.
  9. A network server device that uses an iSCSI connection.
  10. An integrated network server device.
  11. A local workstation controller.
  12. A network server host adapter device.
  13. An optical device.
  14. A point-to-point protocol communication line.
  15. A synchronous data link control communication line.
  16. A tape device.
  17. A token-ring line.
  18. A wireless local area network communication line.
  19. An X.25 communication line.
2. You must create the configuration object for the devices being added on all nodes in the recovery domain of the cluster resource group.
3. The resource name specified in the configuration object must be the same on all nodes in the recovery domain.
4. Devices attached to the same IOP or high-speed link I/O bridge can be specified for only one cluster resource group.
5. If devices attached to different IOPs or high-speed link I/O bridges are grouped such as for an auxiliary storage pool, all devices for the affected IOPs or high-speed link I/O bridges must be specified in the same cluster resource group.
6. The IOP or high-speed link I/O bridge controlling the devices specified in a cluster resource group must be accessible by all nodes in the cluster resource group's recovery domain. This is verified if sufficient hardware configuration has been performed so that all nodes are aware of the new hardware. If hardware configuration is incomplete, this is verified when the Start Cluster Resource Group (STRCRG) command is called.
7. If a data base name is specified in the configuration object, it must be the same on all nodes in the recovery domain.
8. If a new auxiliary storage pool group is added to an active cluster resource group, all members of the auxiliary storage pool group must be specified.
9. If a server takeover IP address is specified, it must exist on all nodes in the recovery domain if the cluster resource group is active. The server takeover IP address must be unique within the cluster. It can only be associated with a primary auxiliary storage pool. IP addresses created by IPv6 stateless address auto-configuration are not valid to be used as server takeover IP addresses.

Top

Parameters

Keyword	Description	Choices	Notes
CLUSTER	Cluster	Name	Required, Positional 1
CRG	Cluster resource group	Name	Required, Positional 2
CFGOBJ	Configuration object list	Values (up to 256 repetitions): Element list	Required, Positional 3
	Element 1: Configuration object	Name
	Element 2: Configuration object type	DEVD, CTLD, LIND, NWSD
	Element 3: Configuration object online	OFFLINE, ONLINE, *PRIMARY
	Element 4: Server takeover IP address	Character value, *NONE

Top

Cluster (CLUSTER)

Specifies the cluster to which the cluster resource group belongs.

This is a required parameter.

name: Specify the name of the cluster which contains the cluster resource group.

Top

Cluster resource group (CRG)

Specifies the cluster resource group which is to contain the device entries.

This is a required parameter.

name: Specify the name of the cluster resource group.

Top

Configuration object list (CFGOBJ)

Specifies detailed information about the resilient devices to be added to the cluster resource group.

This is a required parameter.

Element 1: Configuration object

The name of the configuration object which can be switched between the nodes in the recovery domain. The configuration object can be specified in only one cluster resource group.

name: Specify the name of the configuration object.

Element 2: Configuration object type

Specifies the type of configuration object.

*DEVD: Configuration objects of type device description.
*CTLD: Configuration objects of type controller description.
*LIND: Configuration objects of type line description.
*NWSD: Configuration objects of type network server description.

Element 3: Configuration object online

Specifies what configuration action to take when the cluster resource group is switched over or failed over to a backup node. The configuration object can be varied on and start the server takeover IP address or leave the configuration object varied off and the server takeover IP address inactive and does not start or end the server takeover IP address when device ownership is moved to another node. This attribute does not vary the device on or off when the cluster resource group is started or ended. Switchover and failover completion may be delayed if the online attribute has a value of *YES for devices that may take a long time to vary on.

*OFFLINE: Do not vary the configuration object on and do not start the server takeover IP address.
*ONLINE: Vary the configuration object on and start the server takeover IP address.
*PRIMARY: This is a secondary ASP. Vary on processing is determined by the corresponding primary ASP for this ASP group.

Element 4: Server takeover IP address

Specifies a takeover IP address for servers associated with the relational database name in the device description for an auxiliary storage pool. This element is optional and can only be specified for a primary auxiliary storage pool. If specified, the takeover IP address may be an IPv4 address (for any cluster version) or IPv6 address (if current cluster version is 7 or greater). The specified address must exist on all nodes in the recovery domain if the cluster resource group is active.

An IPv4 internet address is specified in the form nnn.nnn.nnn.nnn, where nnn is a decimal number ranging from 0 through 255. An IPv4 internet address is not valid if it has a value of all binary ones or all binary zeros for the network identifier (ID) portion or the host portion of the address.

An IPv6 internet address must be a unicast address and must not contain an imbedded IPv4 address (compatibility or mapped). An IPv6 internet address is specified in the form x:x:x:x:x:x:x:x, where x is a hexadecimal number ranging from 0 through X'FFFF'. The "::" may be used once in the IPv6 address to indicate one or more groups of 16 bits of zeros. The "::" may be used to compress leading, imbedded, or trailing zeros in the address. IP addresses created by IPv6 stateless address auto-configuration are not valid to be used as server takeover IP addresses.

If the IP address is entered from the command line, the address must be enclosed in apostrophes.

The specified address must exist on all nodes in the recovery domain if the cluster resource group is active. If not specified, or for configuration objects other than a primary auxiliary storage pool, the element must be set to *NONE.

*NONE: There is no server takeover IP address associated with the relational database name in the device description.
character-value: Specify the server takeover IP address associated with the relational database name.

Top

Examples

ADDCRGDEVE   CLUSTER(MYCLUSTER)  CRG(MYCRG)
             CFGOBJ((IASP01 *DEVD *ONLINE
             '2001:0DB8:333:4444:5555:6666:7777:F888'))

This command adds an ASP device description object, IASP01, to the device list of the resilient device cluster resource group MYCRG in the cluster MYCLUSTER. If MYCRG is switched over or failed over to a backup node, the device will be varied on to the new primary. The server takeover IP address is 2001:0DB8:333:4444:5555:6666:7777:F888.

Top

Error messages

*ESCAPE Messages

HAE001F: Request to add device entries to cluster resource group &1 failed.

Top