How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling) (Sun Cluster Software Installation Guide for Solaris OS)

Sun Cluster Software Installation Guide for Solaris OS

How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)

Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.

Does your configuration use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
- If no, proceed to Step 3.
- If yes, restore the mediator configurations.
1. Determine which node has ownership of a diskset to which you will add the mediator hosts.
  # metaset -s setname
  -s setname
  
  Specifies the diskset name
2. If no node has ownership, take ownership of the diskset.
  # metaset -s setname -t
  -t
  
  Takes ownership of the diskset
3. Recreate the mediators.
  # metaset -s setname -a -m mediator-host-list
  -a
  
  Adds to the diskset
  
  -m mediator-host-list
  
  Specifies the names of the nodes to add as mediator hosts for the diskset
4. Repeat Step a through Step c for each diskset in the cluster that uses mediators.

Are you using Sun Management Center to monitor your Sun Cluster configuration?

If no, proceed to Step 4.
If yes, perform the following steps to upgrade the Sun Cluster-module software on the Sun Management Center server machine, help-server machine, and console machine.

Note –
Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.

If you intend to upgrade the Sun Management Center software itself, do not perform this step. Instead, proceed to Step 4 to finish Sun Cluster software upgrade. Then go to How to Upgrade Sun Management Center Software to upgrade Sun Management Center software and the Sun Cluster module.

As superuser, remove the existing Sun Cluster–module packages.

Use the pkgrm(1M) command to remove all Sun Cluster–module packages from all locations listed in the following table.

# pkgrm module-package

Location	Module Package to Remove
Sun Management Center console machine	`SUNWscscn`
Sun Management Center server machine	`SUNWscssv`
Sun Management Center help-server machine	`SUNWscshl`

Note –

Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.

As superuser, reinstall Sun Cluster–module packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to the locations listed in the following table.

In the CD-ROM path, the value for ver is 8 (for Solaris 8) or 9 (for Solaris 9).

# cd Solaris_sparc/Product/sun_cluster/Solaris_ver/Packages/
# pkgadd -d . module-package

Location	Module Package to Install
Sun Management Center console machine	`SUNWscshl`
Sun Management Center server machine	`SUNWscssv`
Sun Management Center help-server machine	`SUNWscshl`

You install the help-server package SUNWscshl on both the console machine and the help-server machine. You do not upgrade to a new SUNWscscn package on the console machine.

If you upgraded any data services that are not supplied on the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM or the Java Enterprise System Accessory CD 3 CD-ROM, register the new resource types for those data services.

Follow the documentation that comes with the data services.

From any node, start the scsetup(1M) utility.
# scsetup

Register the new resource types.
1. From the Main Menu, choose Resource groups.
2. Choose Resource type registration.
3. Choose Register all resource types which are not yet registered.
  
  The scsetup utility displays all resource types that are not registered.
  
  Follow the prompts to register the new resource types.

Migrate all eligible resources to the new version of its resource type.
1. From the Resource Group menu, choose Change properties of a resource.
2. Choose Manage resource versioning.
3. Choose Show versioning status.
  
  The scsetup utility displays all resources for which a new version of its resource type was installed during the upgrade. Make note of which new resource types you will upgrade the resources to.
4. Choose Re-version all eligible resources.
  
  Follow the prompts to upgrade eligible resources to the new version of its resource type.
5. Return to the Change properties of a resource menu.

Modify extension properties for new resource type versions.
1. For each new resource type that you migrated existing resources to, determine whether the new resource type requires additional modifications to its extension properties.
  
  Refer to each related data service manual for the requirements of each new resource type.
  
  Note –
  You do not need to change the Type_version property of a new resource type. That property was modified when you migrated resources to their new resource types in Step 7.
  - If no resource type requires additional modifications other than the Type_version property, go to Step 9.
  - If one or more resource types require additional modifications to extension properties, proceed to Step b.
2. From the Change properties of a resource menu, choose Change extension resource properties.
3. Follow the prompts to modify the necessary extension properties.
  
  Refer to your data service documentation for the names of extension properties and values to modify.
4. Repeat for each resource type that requires modifications.
5. Return to the Resource Groups menu.

Re-enable all disabled resources.
1. From the Resource Group Menu, choose Enable/Disable a resource.
2. Choose a resource to enable and follow the prompts.
3. Repeat Step b for each disabled resource.
4. When all resources are re-enabled, type q to return to the Resource Group Menu.

Bring each resource group back online.
1. From the Resource Group Menu, choose Online/Offline or Switchover a resource group.
2. Follow the prompts to put each resource group into the managed state and then bring the resource group online.

When all resource groups are back online, exit the scsetup utility.

Type q to back out of each submenu, or press Ctrl-C.

The cluster upgrade is complete. You can now return the cluster to production.

Restart any applications.

Follow the instructions that are provided in your third-party documentation.

The cluster upgrade is complete.