Sun Open Telecommunications Platform 2.0 Administration Guide

Upgrading Sun OTP Using Dual-Partition Upgrade

This section describes the procedure to upgrade Sun OTP using the dual-partition method. It includes both the GUI and CLI procedures, and details about how to prepare the hosts for dual-partition upgrade.

ProcedureTo Prepare Hosts for Dual-Partition Upgrade

You must perform this procedure before you upgrade Sun Open Telecommunications Platform using dual-partition upgrade.

  1. Set the resource group property to false.

    clresourcegroup set -p RG_system=false otp-system-rg

    Reset the value to true after completing the live upgrade.

  2. Set up the ssh login between the hosts in the cluster.

    Perform this step on all the hosts in the cluster.

    1. Type the following command.

      ssh-keygen -t rsa

    2. Accept the default values on all nodes.

    3. Append the contents of the /.ssh/id_rsa.pub file to the /.ssh/authorized_keys2 file from each host to all the cluster hosts.

    4. Edit the /etc/ssh/sshd_config file. Set the value of the PermitRootLogin variable to yes.

    5. Restart the ssh instance.

      svcadm restart svc:/network/ssh:default

    6. Verify you are able to log in between all the cluster hosts without typing the password.

  3. Set the system property for the otp-system-rg variable to false.

    /usr/cluster/bin/scrgadm -c -g otp-system-rg -y rg_system=FALSE

  4. Partition the cluster.

    1. On the first host, unzip the cluster bundle.

      unzip -d /tmp_dir 2.0_mediadir/solaris_sparc/components/cluster.zip

      2.0_mediadir is the fully-qualified path name to the Sun OTP 2.0 installation source directory.

    2. Type the following command.

      /tmp_dir/cluster/Solaris_sparc/Product/sun_cluster/Solaris_10/Tools/scinstall

    3. Select Option #3: Manage a dual-partition upgrade.

    4. Assign the manager host to the second partition, and the managed host to the first partition. The managed host on the first partition will be halted.


      Note –

      The first host or the manager host must remain in the second partition.


    5. Boot the hosts in the first partition in the non-cluster mode.

      ok boot -x


    Note –

    For installing and administering Sun Cluster using the GUI, refer to Chapter 12, Administering Sun Cluster With the Graphical User Interfaces, in Sun Cluster System Administration Guide for Solaris OS.


ProcedureTo Upgrade Sun OTP from 1.1 to 2.0 Using the GUI

Before You Begin
  1. Open a browser and log in to the Sun OTP application provisioning service on the Sun OTP provisioning server.

    Go to https://install server:9090 where install server is either the IP address or the fully qualified name of the Sun OTP provisioning server.

  2. Type the user name and password.

    The user name is otpadmin. The password is the password provided in the password file while setting up the Sun OTP provisioning server.

  3. Click OTP Upgrade in the left panel.

  4. Set up the configuration for upgrade by creating two variable sets.

    Run this plan on all the Sun OTP hosts.

    1. Click Set up Configuration and click run.

    2. Click select from list... corresponding to the /com/sun/OTP/Utilities/OTPConfig directory.

    3. Click create set to create a new variable set.

    4. Type a new variable set name in the Set Name field.

    5. Click the check boxes for the appropriate plan variables for which you want to enter the values.

    6. Type the values for the appropriate plan variables in the text fields. For description about the Sun OTP plan settings and the clustered Sun OTP host plan worksheet, see Appendix A Sun OTP Upgrade Plan Worksheet.


      Note –

      Do not specify the values for the zone-related variables and specify RAW for the spsRAConnectionType variable.


    7. Click save to save the variable set.

    8. Close the select variable setting from list... screen.

    9. Under variable settings, click the drop-down list corresponding to the /com/sun/OTP/Utilities/OTPConfig directory and choose the new variable set.

    10. Click select from list... corresponding to the /com/sun/OTPupgrade/Upgrade directory.

    11. Click create set to create a new variable set.

    12. Type a new variable set name in the Set Name field.

    13. Type the values for the following variables:

      logFile - Path of the log file that would contain the output of upgrade operation. For example, /var/OTP/OTPUpgrade.log.

      upgradeType - standard.

    14. Click save to save the variable set.

    15. Close the select variable setting from list... screen.

    16. Under variable settings, click the drop-down list corresponding to the /com/sun/OTPupgrade/Upgrade directory and choose the new variable set.

    17. Type the host name in the target host field.

    18. Enter and confirm the password.

      The password is the password provided in the password file while setting up the Sun OTP provisioning server. The password can be 8 to 12 alphanumeric characters. You need to use this password and the user name otpadmin as the access credentials for all Sun OTP components including Web SSO.

    19. Click run plan (includes preflight).

  5. Back up the Sun OTP system management data.

    Run this plan on the first Sun OTP host which is running the Sun OTP system management service.

    1. Click Backup Data and click run.

    2. Type the host name in the target host field.

    3. Click run plan (includes preflight).

  6. Upgrade the operating system.

    Run this plan simultaneously on all the hosts of the partition that are currently booted in the non-cluster mode.

    1. Click Upgrade OS and click run.

    2. Type the host name in the target host field.

    3. Click run plan (includes preflight).

      The plan completes after initiating the patch upgrade process. You need to monitor the consoles on all the hosts and wait until the completion of the patch upgrade cluster.

  7. Upgrade the Sun OTP high availability service.

    Run this plan simultaneously on all the hosts of the partition that are currently booted in the non-cluster mode.

    1. Click Upgrade HA Services.

    2. Click run plan (includes preflight).

  8. Upgrade the NEP application and the NEP application agent

    If a NFS agent is used as part of the hosted application, upgrade the NFS agent before activating Sun Cluster. You can upgrade the agents later too. For more details on upgrading Sun Cluster, see Chapter 8, Upgrading Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS.


    Note –

    The upgrade procedure is specific to the hosted application, and can be automated by NEP's end-to-end upgrade. See the application documentation for instructions.


  9. Activate the new cluster environment.

    1. On one of the hosts in the first partition, type the following command to activate the first partition.

      /usr/cluster/bin/scinstall

    2. Select Manage a dual-partition upgrade.

    3. Select Apply dual-partition upgrade changes.

      The hosts in the first partition are rebooted into the cluster mode. Once they are successfully booted as active cluster members, the hosts in the second partition are halted.

    4. Boot the hosts in the second partition in the non-cluster mode.

      ok boot -x

    5. On the second partition, run all the steps from upgrading the OS (Upgrade Operating System plan).

    6. Boot the second partition in cluster mode.

      1. Run /usr/cluster/bin/scinstall on the second partition.

      2. Select option #3 Manage a dual-partition upgrade.

      3. Select sub option #4 Apply dual-partition upgrade changes.

      4. Press enter to reboot the node to cluster mode.

  10. Perform the common steps for all the types of upgrade. See Upgrade Remaining Services and Install the Security Service.

ProcedureTo Upgrade Sun OTP from 1.1 to 2.0 Using CLI

Before You Begin
  1. Log in as root (su - root) to the Sun OTP provisioning server.

  2. Copy the input_otp.dat file to a NFS-mounted directory.

    cp /opt/SUNWotp/cli/templates/input_otp.dat /export/

  3. Edit the /export/input_otp.dat file.

    Type the values for each variable. For description about the Sun OTP plan settings and the clustered Sun OTP host plan worksheet, see Appendix A Sun OTP Upgrade Plan Worksheet.


    Note –

    Do not specify the values for the zone-related variables and specify RAW for the spsRAConnectionType variable.


    For each host, specify the values for the following upgrade-related variables.

    h1_UpgradelogFile - Path of the log file that would contain the output of upgrade operation. For example, /var/OTP/OTPUpgrade.log.

    upgradeType - standard.

  4. Set up the configuration for upgrade.

    /opt/SUNWotp/cli/deploy_otp -u S -f /export/input_otp.dat -o "-P passwordfile"

    passwordfile is the absolute path of the password file. You can create this file in your home directory. The password file must contain a line with a valid password for all Sun OTP components. The password can be 8 to 12 alphanumeric characters. You need to use this password and the user name otpadmin as the access credentials for all Sun OTP components including Web SSO.

  5. Back up the Sun OTP system management data.

    /opt/SUNWotp/cli/deploy_otp -u b -f /export/input_otp.dat -o "-B hostname"

    hostname is the first host name that is running the Sun OTP system management service.

  6. Upgrade the operating system.

    /opt/SUNWotp/cli/deploy_otp -u P -f /export/input_otp.dat -o "-T hostname"

    hostname is the name of the host in the partition currently booted in the non-cluster mode. This command needs to be run for every host in this partition.

    The command completes after initiating the patch upgrade process. You need to monitor the consoles on all the hosts and wait until the completion of the patch upgrade cluster.

  7. Upgrade Sun OTP high availability service.

    /opt/SUNWotp/cli/deploy_otp -u a -f /export/input_otp.dat -o "-T hostname"

    hostname is the name of the host in the partition currently booted in non-cluster mode. This command needs to be run for every host in this partition.

  8. Upgrade the NEP application and the NEP application agent

    If a NFS agent is used as part of the hosted application, upgrade the NFS agent before activating Sun Cluster. You can upgrade the agents later too. For more details on upgrading Sun Cluster, see Chapter 8, Upgrading Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS.


    Note –

    The upgrade procedure is specific to the hosted application, and can be automated by NEP's end-to-end upgrade. See the application documentation for instructions.


  9. Activate the new cluster environment.

    1. On one of the hosts in the first partition, type the following command to activate the first partition.

      /usr/cluster/bin/scinstall

    2. Select option #3 Manage a dual-partition upgrade.

    3. Select sub option #4 Apply dual-partition upgrade changes.

      The hosts in the first partition are rebooted into the cluster mode. Once they are successfully booted as the active cluster members, the hosts in the second partition are halted.

    4. Boot the hosts in the second partition in the non-cluster mode.

      ok boot -x

    5. On the second partition, run all the steps from upgrading the OS (Upgrade Operating System plan).

  10. Perform the common steps for all the types of upgrade. See Upgrade Remaining Services and Install the Security Service .