test

Sun Cluster Software Installation Guide for Solaris OS

How to Prepare the Cluster for a Nonrolling Upgrade

Before you upgrade the software, perform the following steps to remove the cluster from production:

  1. Ensure that the configuration meets requirements for upgrade.

    See Upgrade Requirements and Support Guidelines.

  2. Have available the CD-ROMs, documentation, and patches for all software products you are upgrading.

    • Solaris 8 or Solaris 9 OS

    • Sun Cluster 3.1 9/04 framework

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

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

    • SPARC: VERITAS Volume Manager

    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 9/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 Cluster 3.1 9/04 CD-ROM to access installation instructions.

  4. If you are upgrading from Sun Cluster 3.0 software, have available your list of test IP addresses.

    Each public-network adapter in the cluster must have at least one test IP address. This requirement applies regardless of whether the adapter is the active adapter or the backup adapter in the group. The test IP addresses are 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 that is 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.

  5. Notify users that cluster services will be unavailable during the upgrade.

  6. 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 the same node for unresolved error messages or warning messages.

    • Check the volume-manager status.

  7. Become superuser on a node of the cluster.

  8. Start the scsetup(1m) utility.


    # scsetup

    The Main Menu displays.

  9. Switch each resource group offline.

    1. From the scsetup Main Menu, choose Resource groups.

    2. From the Resource Group Menu, choose Online/Offline or Switchover a resource group.

    3. Follow the prompts to take offline all resource groups and to put them in the unmanaged state.

    4. When all resource groups are offline, type q to return to the Resource Group Menu.

  10. Disable all resources in the cluster.

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

    1. From the Resource Group Menu, choose Enable/Disable a resource.

    2. Choose a resource to disable and follow the prompts.

    3. Repeat Step b for each resource.

    4. When all resources are disabled, type q to return to the Resource Group Menu.

  11. Exit the scsetup utility.

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

  12. Verify that all resources on all nodes are Offline and that all resource groups are in the Unmanaged state.


    # scstat -g

  13. If your cluster uses dual-string mediators for Solstice DiskSuite or Solaris Volume Manager software, unconfigure your mediators.

    See Configuring Dual-String Mediators for more information.

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


      # medstat -s setname
      -s setname

      Specifies the disk set 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.

      Save this information for when you restore the mediators during the procedure How to Finish a Nonrolling Upgrade to Sun Cluster 3.1 9/04 Software.

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


      # metaset -s setname -t
      -t

      Takes ownership of the disk set

    4. Unconfigure all mediators for the disk set.


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

      Specifies the disk set name

      -d

      Deletes from the disk set

      -m mediator-host-list

      Specifies the name of the node to remove as a mediator host for the disk set

      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 disk set that uses mediators.

  14. If not already installed, install Sun Web Console packages.

    Perform this step on each node of the cluster. These packages are required by Sun Cluster software, even if you do not use Sun Web Console.

    1. Insert the Sun Cluster 3.1 9/04 CD-ROM in the CD-ROM drive.

    2. Change to the /cdrom/cdrom0/Solaris_arch/Product/sun_web_console/2.1/ directory, where arch is sparc or x86.

    3. Run the setup command.


      # ./setup

      The setup command installs all packages to support Sun Web Console.

  15. For a two-node cluster, if the cluster uses Sun StorEdge Availability Suite software, ensure that the configuration data for availability services resides on the quorum disk.

    The configuration data must reside on a quorum disk to ensure the proper functioning of Sun StorEdge Availability Suite after you upgrade the cluster software.

    1. Become superuser on a node of the cluster that runs Sun StorEdge Availability Suite software.

    2. Identify the device ID and the slice that is used by the Sun StorEdge Availability Suite configuration file.


      # /usr/opt/SUNWscm/sbin/dscfg
/dev/did/rdsk/dNsS

      In this example output, N is the device ID and S the slice of device N.

    3. Identify the existing quorum device.


      # scstat -q
-- Quorum Votes by Device --
                     Device Name         Present Possible Status
                     -----------         ------- -------- ------
   Device votes:     /dev/did/rdsk/dQsS  1       1        Online

      In this example output, dQsS is the existing quorum device.

    4. If the quorum device is not the same as the Sun StorEdge Availability Suite configuration-data device, move the configuration data to an available slice on the quorum device.


      # dd if=`/usr/opt/SUNWesm/sbin/dscfg` of=/dev/did/rdsk/dQsS

      Note –

      You must use the name of the raw DID device, /dev/did/rdsk/, not the block DID device, /dev/did/dsk/.

    5. If you moved the configuration data, configure Sun StorEdge Availability Suite software to use the new location.

      As superuser, issue the following command on each node that runs Sun StorEdge Availability Suite software.


      # /usr/opt/SUNWesm/sbin/dscfg -s /dev/did/rdsk/dQsS

  16. Stop all applications that are running on each node of the cluster.

  17. Ensure that all shared data is backed up.

  18. From one node, shut down the cluster.


    # scshutdown -g0 -y

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

  19. Boot each node into noncluster mode.

    On SPARC based systems, perform the following command:


    ok boot -x

    On x86 based systems, perform the following commands:


    ...
                      <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b
Boot args:

Type  b [file-name] [boot-flags] <ENTER>    to boot with options
or    i <ENTER>                             to enter boot interpreter
or    <ENTER>                               to boot with defaults

                  <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -x

  20. Ensure that each system disk is backed up.

  21. Upgrade the Sun Cluster software or the Solaris operating system.