test

Sun Cluster 3.1 Software Installation Guide

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.