test

Sun Cluster Software Installation Guide for Solaris OS

How to Prepare the Cluster for Upgrade (Rolling)

Perform this procedure on one node at a time. The upgraded node is taken out of the cluster, while the remaining nodes continue to function as active cluster members.

Note –

Do not use any new features of the update release, install new data services, or issue any administrative configuration commands until all nodes of the cluster are successfully upgraded.

  1. Ensure that the configuration meets requirements for upgrade.

    See Upgrade Requirements and Restrictions.

  2. 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 4/04 framework

    • Sun Cluster 3.1 4/04 data services (agents)

    • Applications that are managed by Sun Cluster 3.1 4/04 data-service agents

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

  3. (Optional) Install Sun Cluster 3.1 4/04 documentation.

    Install the documentation packages on your preferred location, such as an administrative console or a documentation server. See the index.html file at the top level of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to access installation instructions.

  4. From any node, view the current status of the cluster.

    Save the output as a baseline for later comparison.


    % scstat
% scrgadm -pv[v]

    See the scstat(1M) and scrgadm(1M) man pages for more information.

  5. Become superuser on one node of the cluster to upgrade.

  6. Move all resource groups and device groups that are running on the node to upgrade.


    # scswitch -S -h from-node
    -S

    Moves all resource groups and device groups

    -h from-node

    Specifies the name of the node from which to move resource groups and device groups

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

  7. Verify that the move completed successfully.


    # scstat -g -D
    -g

    Show status for all resource groups

    -D

    Show status for all disk device groups

  8. Ensure that the system disk and data is backed up.

  9. Does your cluster use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?

    1. Run the following command to verify that no mediator data problems exist.


      # medstat -s setname
      -s setname

      Specifies the diskset name

      If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Fix Bad Mediator Data.

    2. List all mediators.

      Use this information for when you restore the mediators during the procedure How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling).

    3. For a diskset that uses mediators, take ownership of the diskset if no node already has ownership.


      # metaset -s setname -t
      -t

      Takes ownership of the diskset

    4. Unconfigure all mediators for the diskset.


      # metaset -s setname -d -m mediator-host-list
      -s setname

      Specifies the diskset name

      -d

      Deletes from the diskset

      -m mediator-host-list

      Specifies the name of the node ot remove as a mediator host for the diskset

      See the mediator(7D) man page for further information about mediator-specific options to the metaset command.

    5. Repeat Step c through Step d for each remaining diskset that uses mediators.

  10. Shut down the node that you want to upgrade and boot it into noncluster mode.


    # shutdown -y -g0
ok boot -x

    The other nodes of the cluster continue to function as active cluster members.

  11. Do you intend to upgrade the Solaris software to a Maintenance Update release?

    Note –

    The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris operating environment to support Sun Cluster 3.1 4/04 software. See the Sun Cluster Release Notes for Solaris OS for information about supported releases of the Solaris operating environment.