test

Sun Cluster 3.1 Software Installation Guide

Chapter 3 Upgrading Sun Cluster Software

This chapter provides step-by-step procedures to upgrade a Sun Cluster 3.0 configuration to Sun Cluster 3.1 software.

Note –

Upgrade from Solaris 8 to Solaris 9 software is not supported in a Sun Cluster configuration.

The following step-by-step instructions are in this chapter.

For overview information about planning your Sun Cluster 3.1 configuration, see Chapter 1, Planning the Sun Cluster Configuration. For a high-level description of the related procedures for Sun Cluster software upgrade, see Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software.

Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software

Perform the following tasks to upgrade your cluster from Sun Cluster 3.0 to Sun Cluster 3.1 software.

Table 3–1 Task Map: Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software

Task 

For Instructions, Go To … 

Read the upgrade guidelines. 

Overview of Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software

Take the cluster out of production, disable resources, and back up shared data and system disks.  

How to Prepare the Cluster for Upgrade

Upgrade the Solaris operating environment, if necessary. Optionally, upgrade VERITAS Volume Manager (VxVM).  

How to Upgrade the Solaris Operating Environment

Upgrade to Sun Cluster 3.1 framework and data services software. If necessary, upgrade applications. 

How to Upgrade Cluster Software

Finish the cluster software upgrade. If you upgraded VxVM, upgrade disk groups. Reregister resource types, enable resources, and bring resource groups online. 

How to Finish Upgrading Cluster Software

Overview of Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software

This section provides guidelines for upgrading from Sun Cluster 3.0 to Sun Cluster 3.1 software.

Upgrade Guidelines

Follow these guidelines to upgrade from Sun Cluster 3.0 to Sun Cluster 3.1 software:

How to Prepare the Cluster for Upgrade

Before you upgrade the software, perform the following steps to take the cluster out of production.

  1. Have available the CD-ROMs, documentation, and patches for all the software products you are upgrading before you begin to upgrade the cluster.

    • Solaris 8 or Solaris 9 operating environment

    • Sun Cluster 3.1 framework

    • Sun Cluster 3.1 data services (agents)

    • Applications managed by Sun Cluster 3.1 data-service agents

    • VERITAS Volume Manager

    See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of Sun patches and installation instructions.

  2. Have available your list of test IP addresses, one for each public network adapter in the cluster.

    A test IP address is required for each public network adapter in the cluster, regardless of whether the adapter is the active or the backup adapter in the group. The test IP addresses will be used to reconfigure the adapters to use IP Network Multipathing.

    Note –

    Each test IP address must be on the same subnet as the existing IP address used by the public network adapter.

    To list the public network adapters on a node, run the following command: 


    % pnmstat

    See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for more information about test IP addresses for IP Network Multipathing.

  3. Notify users that cluster services will be unavailable during upgrade.

  4. Ensure that the cluster is functioning normally.

    • To view the current status of the cluster, run the following command from any node. 


      % scstat

      See the scstat(1M) man page for more information.

    • Search the /var/adm/messages log on that node for unresolved error or warning messages.

  5. List the names of all resource types installed on your cluster before upgrade.


    % scrgadm -p | grep "Res Type"

    Keep this list for reference when you reregister the resource types at the end of the upgrade process.

  6. Become superuser on a node of the cluster.

  7. Disable all resources in the cluster.

    The disabling of resources during upgrade prevents the cluster from bringing the resources online automatically if a node is mistakenly rebooted into cluster mode.

    1. From any node, list all enabled resources in the cluster.


      # scrgadm -pv | grep "Res enabled"

    2. Use the scswitch command to disable each enabled resource in the cluster.


      scswitch -n -j resource
      -n

      Disables

      -j resource

      Specifies the resource

    Note –

    If you are upgrading from the Sun Cluster 3.0 5/02 release, you can use the scsetup(1M) utility instead of the command line. From the Main Menu, choose Resource Groups, then choose Enable/Disable Resources.

  8. Switch each resource group offline.


    # scswitch -F -g resource-group

    -F

    Switches a resource group offline

    -g resource-group

    Specifies the name of the resource group to take offline

  9. Move each resource group into the unmanaged state. 


    # scswitch -u -g resource-group

    -u

    Moves the specified resource group in the unmanaged state

    -g resource-group

    Specifies the name of the resource group to move into the unmanaged state

  10. Verify that all resources on all nodes are disabled and that all resource groups are in the unmanaged state.

    You do not need to be superuser to run this command.


    # scstat -g

  11. Stop all databases that are running on each node of the cluster.

  12. Back up all shared data.

  13. From one node, shut down the cluster.


    # scshutdown
ok

  14. On each node, boot the node into non-cluster mode.


    ok boot -x

  15. Back up each system disk.

  16. Do you intend to upgrade the Solaris software?

    You must upgrade the Solaris operating environment if Sun Cluster 3.1 software does not support the update release of Solaris software that you currently run on your cluster.

    Note –

    Upgrade from Solaris 8 to Solaris 9 software is not supported in a Sun Cluster configuration.

How to Upgrade the Solaris Operating Environment

Perform this procedure on each node in the cluster to upgrade the Solaris operating environment to support Sun Cluster 3.1 software. However, if the cluster is already installed with a version of Solaris software supported by Sun Cluster 3.1 software and you do not intend to upgrade to a later compatible update of the Solaris software, you do not otherwise need to perform this procedure. Instead, go to How to Upgrade Cluster Software.

Note –

The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris 8 or Solaris 9 operating environment to support Sun Cluster 3.1 software. See “Supported Products” in Sun Cluster 3.1 Release Notes for more information.

Upgrade from Solaris 8 to Solaris 9 software is not supported in a Sun Cluster configuration.

  1. Become superuser on the cluster node to upgrade.

  2. Does your cluster use VxVM?

    • If no, go to Step 3.

    • If yes, follow upgrade procedures in your VxVM installation documentation, then return to Step 3 when the VxVM procedure says to upgrade Solaris software.

      Note –

      When instructed to boot into single-user mode, use the following command to reboot into single-user non-cluster mode:


      # boot -- -xs

  3. Determine whether the following Apache links already exist, and if so, whether the file names contain an uppercase K or S.


    /etc/rc0.d/K16apache        
/etc/rc1.d/K16apache        
/etc/rc2.d/K16apache        
/etc/rc3.d/S50apache        
/etc/rcS.d/K16apache

    If these links already exist and contain an uppercase K or S in the file name, no further action is necessary concerning these links. If these links do not exist, or if these links exist but contain lowercase k or s in the file name, you will move aside these links in Step 6.

  4. Upgrade the Solaris software.

    Note –

    Sun Cluster software does not support upgrade from Solaris 8 to Solaris 9 software.

    1. Do you intend to use the Maintenance Update method to upgrade the Solaris software?

      • If yes, go to Step b.

      • If no, make a record of all entries that are already commented out for later reference, then temporarily comment out all global device entries in the /etc/vfstab file.

        Do this to prevent the Solaris upgrade from attempting to mount the global devices. This step is not necessary if you use the Maintenance Update method to upgrade Solaris software.

    2. Follow upgrade instructions for the version of Solaris to which you will upgrade your cluster.

      Note –

      To reboot a node during Solaris software upgrade, always add the -x option to the command. This ensures that the node reboots into non-cluster mode. The following two commands boot a node into single-user non-cluster mode:


      # reboot -- -xs
ok boot -xs

    3. Did you comment out the global device entries in the /etc/vfstab file in Step a?

      • If no, go to Step 6.

      • If yes, uncomment all global device entries that you commented out in the /a/etc/vfstab file.

        Note –

        Leave commented out all entries that were already commented out before you performed Step a.

  5. Did you perform VxVM procedures in Step 2 to upgrade Solaris software?

    • If no, go to Step 6.

    • If yes, perform the remaining steps in the VxVM upgrade procedure you used, but do not reboot except into non-cluster mode.


      # reboot -- -x

  6. If the Apache links in Step 3 did not already exist or they contained a lowercase k or s in the file names before you upgraded the Solaris software, move aside the restored Apache links.

    Use the following commands to rename the files with a lowercase k or s.


    # mv /a/etc/rc0.d/K16apache /a/etc/rc0.d/k16apache        
# mv /a/etc/rc1.d/K16apache /a/etc/rc1.d/k16apache
# mv /a/etc/rc2.d/K16apache /a/etc/rc2.d/k16apache
# mv /a/etc/rc3.d/S50apache /a/etc/rc3.d/s50apache
# mv /a/etc/rcS.d/K16apache /a/etc/rcS.d/k16apache

  7. Reboot the node in non-cluster mode, if you have not already done so.

    Include the double dashes (--) in the command.


    # reboot -- -x

  8. Install any Solaris software patches and hardware-related patches, and download any needed firmware contained in the hardware patches. For Solstice DiskSuite software, install any Solstice DiskSuite software patches.

    Note –

    Do not reboot after adding patches. You will reboot the node after you upgrade the Sun Cluster software.

    See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

  9. Upgrade to Sun Cluster 3.1 software.

    Go to How to Upgrade Cluster Software.

How to Upgrade Cluster Software

Perform this procedure on each node. You can perform this procedure on more than one node at a time.

  1. Become superuser on a node of the cluster.

  2. Insert the Sun Cluster 3.1 CD-ROM into the CD-ROM drive on the node.

    If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_1 directory.

  3. Upgrade the node to Sun Cluster 3.1 software.

    1. Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9 .

      The following example uses the path to the Solaris 8 version of Sun Cluster software.


      # cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_8/Tools

    2. Upgrade the cluster software framework.


      # ./scinstall -u update -S interact
      -S

      Specifies the test IP addresses to use to convert NAFO groups to IP Network Multipathing groups

      interact

      Specifies that scinstall will prompt the user for each test IP address needed

      If upgrade processing is interrupted, ensure that the node is in non-cluster mode, then restart the scinstall command.

      See the scinstall(1M) man page for more information. See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for information about test addresses for IP Network Multipathing.

      During upgrade processing, scinstall makes the following configuration changes:

      • Converts NAFO groups to IP Network Multipathing groups but keeps the original NAFO-group name

      • Renames the ntp.conf file to ntp.conf.cluster, if ntp.conf.cluster does not already exist on the node

      • Sets the local-mac-address? variable to true, if the variable is not already set to that value

    3. Change to the CD-ROM root directory and eject the CD-ROM.

    4. Install any Sun Cluster patches.

      See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

    Note –

    Do not reboot the node at this time.

  4. Upgrade applications and apply application patches as needed.

    See your application documentation for installation instructions. Follow these guidelines to upgrade applications in a Sun Cluster configuration:

    • If the applications are stored on shared disks, you must master the relevant disk groups and manually mount the relevant file systems before you upgrade the application.

    • If you must reboot the node during application upgrade, add the -x option to the boot command. This ensures that the node reboots into non-cluster mode. The following two commands boot a node into single-user non-cluster mode:


      # reboot -- -xs
ok boot -xs

  5. Upgrade data services to the Sun Cluster 3.1 software versions.

    Note –

    Only those data services provided on the Sun Cluster 3.1 Agents CD-ROM are automatically upgraded by scinstall(1M). You must manually upgrade any custom or third-party data services.

    1. Insert the Sun Cluster 3.1 Agents CD-ROM into the CD-ROM drive on the node to upgrade.

    2. Upgrade the data service software.


      # scinstall -u update -s all -d /cdrom/cdrom0

      -u update

      Specifies upgrade

      -s all

      Updates all Sun Cluster data services

      If upgrade processing is interrupted, ensure that the node is in non-cluster mode, then restart the scinstall command.

    3. Eject the CD-ROM.

    4. As needed, manually upgrade any custom data services that are not supplied on the Sun Cluster 3.1 Agents CD-ROM.

    5. Install any Sun Cluster data service patches.

      See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

    6. Repeat Step b through Step e on each node of the cluster.

  6. After all nodes are upgraded, reboot each node into the cluster.


    # reboot

  7. From any node, verify that all of the nodes are cluster members.


    # scstat
-- Cluster Nodes --
                   Node name      Status
                   ---------      ------
  Cluster node:    phys-schost-1  Online
  Cluster node:    phys-schost-2  Online

    See the scstat(1M) man page for more information about displaying cluster status.

  8. Finish the upgrade.

    Go to How to Finish Upgrading Cluster Software.

Example—Upgrading From Sun Cluster 3.0 to Sun Cluster 3.1 Software

The following example shows the process of upgrading a two-node cluster from Sun Cluster 3.0 to Sun Cluster 3.1 software on the Solaris 8 operating environment. The cluster node names are phys-schost-1 and phys-schost-2.


(On the first node, upgrade framework software from the Sun Cluster 3.1 CD-ROM)
phys-schost-1# cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_8/Tools
phys-schost-1# ./scinstall -u update -S interact
 
(On the first node, upgrade data services from the Sun Cluster 3.1 Agents CD-ROM)
phys-schost-1# ./scinstall -u update -s all -d /cdrom/cdrom0
 
(On the second node, upgrade framework software from the Sun Cluster 3.1 CD-ROM)
phys-schost-2# cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_8/Tools
phys-schost-2# ./scinstall -u update -S interact
 
(On the second node, upgrade data services from the Sun Cluster 3.1 Agents CD-ROM)
phys-schost-2# ./scinstall -u update -s all -d /cdrom/cdrom0
 
(Reboot each node into the cluster)
phys-schost-1# reboot
phys-schost-2# reboot
 
(Verify cluster membership)
# scstat

How to Finish Upgrading Cluster Software

Perform these steps after you have upgraded software on each node of the cluster and all nodes are booted into the cluster.

  1. Did you upgrade VxVM?

    • If no, go to Step 2.

    • If yes, upgrade all disk groups.

      To upgrade a disk group to the highest version supported by the VxVM release you installed, run the following command from the primary node of the disk group:


      # vxdg upgrade dgname

      See your VxVM administration documentation for more information about upgrading disk groups.

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

    • If yes, install the Sun Cluster 3.1 module packages for Sun Management Center on the server machine and help server machine.

    1. Ensure that all Sun Management Center core packages are installed on the appropriate machines.

      This step includes installing Sun Management Center agent packages on each cluster node. See your Sun Management Center documentation for installation instructions.

    2. Become superuser on the Sun Management Center server machine

    3. Insert the Sun Cluster 3.1 CD-ROM into the CD-ROM drive.

    4. Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .

      The following example uses the path to the Solaris 8 version of Sun Cluster software.


      # cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_8/Packages

    5. Install the Sun Cluster module server package SUNWscssv.


      # pkgadd -d . SUNWscssv

    6. Change to the CD-ROM root directory and eject the CD-ROM.

    7. Become superuser on the Sun Management Center help server machine

    8. Install the Sun Cluster module help server package SUNWscshl.

      Use the same procedure as in Step c through Step f.

  3. Reregister all resource types which received a new version from the upgrade, then re-enable resources and bring resource groups online.

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


      # scsetup

    2. To work with resource groups, type 2 (Resource groups).

    3. To register resource types, type 4 (Resource type registration).

      Type yes when prompted to continue.

    4. Type 1 (Register all resource types which are not yet registered).

      The scsetup utility displays all resource types which are not registered. Type yes to continue to register these resource types.

    5. Type 8 (Change properties of a resource).

      Type yes to continue.

    6. Type 3 (Manage resource versioning).

      Type yes to continue.

    7. Type 1 (Show versioning status).

      The scsetup utility displays what resources you can upgrade to new versions of the same resource type, and the state that the resource should be in before the upgrade can begin.

      Type yes to continue.

    8. Type 4 (Re-version all eligible resources).

      Type yes to continue when prompted.

    9. Return to the Resource Group Menu.

    10. To enable resources, type 6 (Enable/Disable a resource).

      Type yes to continue when prompted.

    11. Select a resource to enable and follow the prompts. Repeat for each disabled resource.

    12. When all resources are re-enabled, type q to return to the Resource Group Menu.

    13. Type 5 (Online/Offline or Switchover a resource group).

      Type yes to continue when prompted.

    14. Follow the prompts to bring each resource group online.

    15. Exit the scsetup utility.

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

    Note –

    To upgrade future versions of resource types, see “Upgrading a Resource Type” in Sun Cluster 3.1 Data Service Planning and Administration Guide.

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

Sun Management Center Software Upgrade

This section describes how to upgrade from Sun Management Center 2.1.1 to Sun Management Center 3.0 software or from Sun Management Center 2.1.1 to Sun Management Center 3.5 software on a Sun Cluster 3.1 configuration.

How to Upgrade Sun Management Center Software

Perform this procedure to upgrade from Sun Management Center 2.1.1 to Sun Management Center 3.0 software or from Sun Management Center 2.1.1 to Sun Management Center 3.0 software on a Sun Cluster 3.1 configuration.

  1. Have available the following items.

    • Sun Cluster 3.1 CD-ROM or the path to the CD-ROM image. You will use the CD-ROM to reinstall the Sun Cluster module packages after you upgrade Sun Management Center software.

    • Sun Management Center documentation.

    • Sun Management Center patches and Sun Cluster module patches, if any. See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

  2. Stop any Sun Management Center processes.

    1. If the Sun Management Center console is running, exit the console.

      In the console window, select File>Exit from the menu bar.

    2. On each Sun Management Center agent machine (cluster node), stop the Sun Management Center agent process.


      # /opt/SUNWsymon/sbin/es-stop -a

    3. On the Sun Management Center server machine, stop the Sun Management Center server process.


      # /opt/SUNWsymon/sbin/es-stop -S

  3. As superuser, remove Sun Cluster module packages from the locations listed in Table 3–2.

    You must remove all Sun Cluster module packages from all locations. Otherwise, the Sun Management Center software upgrade might fail because of package dependency problems. After you upgrade Sun Management Center software, you will reinstall these packages in Step 5.


    # pkgrm module-package

    Table 3–2 Locations to Remove Sun Cluster Module Packages

    Location 

    Package to Remove 

    Each cluster node 

    SUNWscsam, SUNWscsal

    Sun Management Center console machine 

    SUNWscscn

    Sun Management Center server machine 

    SUNWscssv

    Sun Management Center help server machine 

    SUNWscshl

  4. Upgrade the Sun Management Center software.

    Follow the upgrade procedures in your Sun Management Center documentation.

  5. As superuser, reinstall Sun Cluster module packages to the locations listed in Table 3–3.

    For Sun Management Center software, you install the help server package SUNWscshl on the console machine as well as on the help server machine. 


    # cd /cdrom/suncluster_3_1/SunCluster_3.1/Packages
# pkgadd module-package

    Table 3–3 Locations to Install Sun Cluster Module Packages

    Location 

    Package to Install 

    Each cluster node 

    SUNWscsam, SUNWscsal

    Sun Management Center console machine 

    SUNWscshl

    Sun Management Center server machine 

    SUNWscssv

    Sun Management Center help server machine 

    SUNWscshl

  6. Apply any Sun Management Center patches and any Sun Cluster module patches to each node of the cluster.

  7. Restart Sun Management Center agent, server, and console processes on all involved machines.

    Follow procedures in How to Start Sun Management Center.

  8. Load the Sun Cluster module.

    Follow procedures in How to Load the Sun Cluster Module.

    If the Sun Cluster module was previously loaded, unload the module and then reload it to clear all cached alarm definitions on the server. To unload the module, from the console's Details window select Module>Unload Module.