test

Sun Open Telecommunications Platform 2.0 Administration Guide

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 .