How to Install and Register an Upgrade of a Resource Type

The instructions that follow explain how to use the scrgadm(1M) command to perform this task. However, you are not restricted to using the scrgadm command for this task. Instead of the scrgadm command, you can use SunPlex Manager or the Resource Group option of the scsetup(1M) command to perform this task.

Before You Begin

Consult the documentation for the resource type to determine what you must do before installing the upgrade package on a node. One action from the following list will be required:

• You must reboot the node in noncluster mode.

• You may leave the node running in cluster mode, but you must turn off monitoring of all instances of the resource type.

• You may leave the node running in cluster mode and leave monitoring turned on for all instances of the resource type.

If you must reboot the node in noncluster mode, prevent a loss of service by performing a rolling upgrade. In a rolling upgrade, you install the package on each node individually while leaving the remaining nodes running in cluster mode.

Steps

1. Become superuser or assume an equivalent role.

2. Install the package for the resource type upgrade on all cluster nodes where instances of the resource type are to be brought online.

3. Register the new version of the resource type.

   To ensure that the correct version of the resource type is registered, you must specify the following information:

   • The resource type name

   • The resource type registration (RTR) file that defines the resource type

   # scrgadm -a -t resource-type-name -f path-to-new-rtr-file

   The format of the resource type name is as follows:

   vendor-id.base-rt-name:rt-version
   

   For an explanation of this format, see Format of Resource Type Names.

4. Display the newly registered resource type.

   # scrgadm -pv -t resource-type-name

5. If necessary, set the Installed_nodes property to the nodes where the package for the resource type upgrade is installed.

   You must perform this step if the package for the resource type upgrade is not installed on all cluster nodes.

   The nodelist property of all resource groups that contain instances of the resource type must be a subset of the Installed_nodes property of the resource type.

   # scrgadm -c -t resource-type -h installed-node-list