Sun Cluster 3.0 Installation Guide

How to Finish Upgrading Cluster Software

This procedure finishes the scinstall(1M) upgrade process begun in "How to Upgrade Cluster Software Packages". Perform these steps on each node of the cluster.

  1. Become superuser on each node of the cluster.

  2. Choose a shared disk to be the quorum device.

    You can use any disk shared by both nodes as a quorum device. From either node, use the scdidadm(1M) command to determine the shared disk's device ID (DID) name. You specify this device name in Step 5, in the -q globaldev=devicename option to scinstall.


    # scdidadm -L
    
  3. If your volume manager is VxVM, reinstall the VxVM software on each node of the cluster.


    Note -

    Whenever you must reboot, you must shut down the second node of the cluster before rebooting the first, or sponsor, node. After rebooting the first node, then bring the second node back up. Otherwise, rebooting the first node while the second node is still up will panic the second node because quorum votes have not yet been assigned.


    1. Install VxVM software, including any patches.

      Follow the procedures in "How to Install VERITAS Volume Manager Software".

    2. Configure VxVM.

      Follow the procedures listed in "Configuring VxVM for Sun Cluster Configurations".

  4. Insert the Sun Cluster 3.0 data services CD-ROM into the CD-ROM drive on the node.

    This step assumes that the volume daemon vold(1M) is running and configured to manage CD-ROM devices.

  5. Finish the cluster software upgrade on that node.


    # scinstall -u finish -q globaldev=devicename \
    -d /cdrom_image/scdataservices_3_0 -s srvc[,srvc]
    -q globaldev=devicename

    Specifies the name of the quorum device

    -d /cdrom_image/scdataservices_3_0

    Specifies the directory location of the CD-ROM image

    -s srvc

    Specifies the name of the data service to configure


    Note -

    An error message similar to the following might be generated. You can safely ignore it.



    ** Installing Sun Cluster - Highly Available NFS Server **
    Skipping "SUNWscnfs" - already installed
  6. Eject the CD-ROM.

  7. Repeat Step 4 through Step 6 on the other node.

    When completed on both nodes, the cluster is removed from install mode and all quorum votes are assigned.

  8. If your volume manager is Solstice DiskSuite, from either node bring pre-existing disk device groups online.


    # scswitch -z -D disk-device-group -h node
    
    -z

    Performs the switch

    -D disk-device-group

    Specifies the name of the disk device group, which for Solstice DiskSuite software is the same as the diskset name

    -h node

    Specifies the name of the cluster node that serves as the primary of the disk device group

  9. From either node, bring pre-existing data service resource groups online.

    At this point, Sun Cluster 2.2 logical hosts are converted to Sun Cluster 3.0 resource groups, and the names of logical hosts are appended with the suffix -lh. For example, a logical host named lhost-1 is upgraded to a resource group named lhost-1-lh. Use these converted resource group names in the following command.


    # scswitch -z -g resource-group -h node
    
    -g resource-group

    Specifies the name of the resource group to bring online

    You can use the scrgadm -p command to display a list of all resource types and resource groups in the cluster. The scrgadm -pv command displays this list with more detail.

  10. If you are using the Sun Management Center product to monitor your Sun Cluster configuration, install the Sun Cluster module for the Sun Management Center product.

    1. Ensure that you are using the most recent version of Sun Management Center software (formerly Sun Enterprise SyMON).

      Refer to the Sun Management Center documentation for installation or upgrade procedures.

    2. Follow guidelines and procedures in "Installation Requirements for Sun Management Center Software for Sun Cluster Monitoring" to install the Sun Cluster module packages.

Example--Upgrading From Sun Cluster 2.2 to Sun Cluster 3.0 Software - Finish Process

The following example shows the finish process of upgrading a two-node cluster upgraded from Sun Cluster 2.2 to Sun Cluster 3.0 software. The cluster node names are phys-schost-1 and phys-schost-2, the device group names are dg-schost-1 and dg-schost-2, and the data service resource group names are lh-schost-1 and lh-schost-2.


(Determine the DID of the shared quorum device:)
phys-schost-1# scdidadm -L
 
(Finish upgrade on each node:)
phys-schost-1# scinstall -u finish -q globaldev=d1 \
-d /cdrom/suncluster_3_0 -s nfs
phys-schost-2# scinstall -u finish -q globaldev=d1 \
-d /cdrom/suncluster_3_0 -s nfs
 
(Bring device groups and data service resource groups on each node online:)
phys-schost-1# scswitch -z -D dg-schost-1 -h phys-schost-1
phys-schost-1# scswitch -z -g lh-schost-1 -h phys-schost-1
phys-schost-1# scswitch -z -D dg-schost-2 -h phys-schost-2 
phys-schost-1# scswitch -z -g lh-schost-2 -h phys-schost-2

Where to Go From Here

To verify that all nodes have joined the cluster, go to "How to Verify Cluster Membership".