Upgrading Sun OTP (Sun Open Telecommunications Platform 2.0 Administration Guide)

Sun Open Telecommunications Platform 2.0 Administration Guide

Upgrading Sun OTP

You can upgrade Sun OTP 1.1 to version 2.0 by using one of the following upgrades methods:

Standard upgrade. Shuts down the cluster before you upgrade the cluster nodes. You must return the cluster to production after all the nodes are fully upgraded.
Dual-partition upgrade. Divides the cluster into two groups of nodes. You must bring down one group of nodes and upgrade those nodes. The other group of nodes continue to provide services. After you complete the upgrade of the first group of nodes, switch services to the upgraded nodes. You can then upgrade the remaining nodes and boot them back to the rest of the cluster. The cluster outage time is limited to the amount of time needed for the cluster to switch over services to the upgraded partition.
Live upgrade. Maintains the previous cluster configuration until you have upgraded all nodes, and commit to the upgrade. If the upgraded configuration causes a problem, revert to your previous cluster configuration until you can rectify the problem.

Table 1–1 Task map: Description of various upgrade tasks


Task	Description
Upgrading Sun OTP 1.1 Provisioning Server to Version 2.0	This section describes the procedure to upgrade the provisioning server
Upgrading Sun OTP Using Standard Upgrade	This section describes the procedure to upgrade Sun OTP using the standard upgrade method. It includes both the GUI and CLI procedures, and details about how to upgrade the remaining service and install the security service.
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.
Upgrading Sun OTP Using Live Upgrade	This section describes the procedure to upgrade Sun OTP using the live upgrade method. It includes both the GUI and CLI procedures, and details about how to prepare the hosts for dual-partition upgrade.

To Upgrade Sun OTP 1.1 Provisioning Server to Version 2.0

Note –

You can directly use the Sun OTP 2.0 provisioning server to upgrade Sun OTP. Sun OTP 2.0 provisioning server has the SUNWotp, SUNWotpupdate, and SUNWotpupg packages installed.

Remove the packages.

pkgrm SUNWotp SUNWotpcli SUNWotputil

If the OSP plug-in along with the SUNWotpra custom package was used to install the Solaris OS on this system, remove the SUNWotpra package.

pkgrm SUNWotpra

Change to the following directory.

cd 2.0_mediadir/common/components/sunotp

2.0_mediadir is the fully qualified path name to the Sun Open Telecommunications Platform 2.0 installation source directory.

Add the following packages.

pkgadd -d . SUNWotp SUNWotpupdate SUNWotpupg

Reconfigure the Sun OTP application provisioning service on the Sun OTP 1.1 Sun OTP provisioning server.

/opt/SUNWotp/upgrade/n1sps_reconfigure.pl --run reconfig --nodetype none --params mediadir=2.0_mediadir

2.0_mediadir is the fully qualified path name to the Sun Open Telecommunications Platform 2.0 installation source directory.

Upgrading Sun OTP Using Standard Upgrade

This section describes the procedure to upgrade Sun OTP using the standard upgrade method. It includes both the GUI and CLI procedures, and details about how to upgrade the remaining service and install the security service.

To Upgrade Sun OTP from 1.1 to Sun OTP 2.0 Using the GUI

Before You Begin

Upgrade Sun OTP 1.1 Provisioning Server to Version 2.0

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

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

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.

Click OTP Upgrade in the left panel.

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 the select from list... option 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 type 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).

Back up the Sun OTP system management data.

Run this plan only on the first Sun OTP host that 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).

Upgrade the operating system.

Run this plan on all the Sun OTP hosts.
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 is complete after initiating the patch upgrade process. You need to monitor the consoles on all the hosts and wait until the completion of patch upgrade cluster.

Upgrade the Sun OTP high availability service.

Run this plan on all the Sun OTP hosts.
1. Click Upgrade HA Services and click run.
2. Type the host name in the target host field.
3. Click run plan (includes preflight).

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.

Activate the new cluster environment by rebooting all the Sun OTP hosts.

/usr/sbin/init 6

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

To Upgrade Remaining Services and Install the Security Service Using GUI

Upgrade the Sun OTP application provisioning service.

Run this plan simultaneously on all the Sun OTP hosts.
1. Click OTP Upgrade in the left panel.
2. Click Upgrade Provisioning Services.
3. Type the host name in the target host field.
4. Click run plan (includes preflight).
  
  Monitor the debug log in the /var/OTP/SUNWotp-debug.log file and wait until the reconfiguration of Sun OTP application provisioning service before running the next plan.

Upgrade the Sun OTP system management service.

Run this plan on all the Sun OTP hosts.
1. Click Upgrade Management Service and click run.
2. Type the host name in the target host field.
3. Click run plan (includes preflight).

Install the Sun OTP security service.

Run this plan on all the Sun OTP hosts.
1. Click OTP Setup in the left panel.
2. Click Install Security Service and click run.
3. Type the host name in the target host field.
4. Click run plan (includes preflight).

Configure the Sun OTP AHE components as highly available services.

Run this plan only on the first Sun OTP host.
1. Click Configure Components and click run.
2. Type the host name in the target host field.
3. Click run plan (includes preflight).

Restore the Sun OTP system management data that was backed up.

Run this plan only on the first Sun OTP host.
1. Click OTP Upgrade in the left panel.
2. Click Restore Data and click run.
3. Type the host name in the target host field.
4. Click run plan (includes preflight).

Install Web SSO.

Run this plan on all the Sun OTP hosts.
1. Click OTP Setup in the left panel.
2. Click Install WebSSO and click run.
3. Type the host name in the target host field.
4. Click run plan (includes preflight).

To Upgrade Sun OTP from 1.1 to 2.0 Using CLI

Before You Begin

Upgrade Sun OTP 1.1 Provisioning Server to Version 2.0

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

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

Edit the /export/input_otp.dat file to add 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.

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.

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.

Upgrade the operating system.

/opt/SUNWotp/cli/deploy_otp -u P -f /export/input_otp.dat

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

Upgrade the Sun OTP high availability service.

/opt/SUNWotp/cli/deploy_otp -u a -f /export/input_otp.dat

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.

Activate the new cluster environment by rebooting all the Sun OTP hosts.

/usr/sbin/init 6

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

To Upgrade Remaining Services and Install the Security Service Using CLI

Upgrade the Sun OTP application provisioning service.

/opt/SUNWotp/cli/deploy_otp -u p -f /export/input_otp.dat

This command reconfigures the Sun OTP application provisioning service.

When the command is complete, monitor the debug log in the /var/OTP/SUNWotp-debug.log file and wait until the reconfiguration of the Sun OTP application provisioning service.

Upgrade the Sun OTP system management service.

/opt/SUNWotp/cli/deploy_otp -u m -f /export/input_otp.dat

Install the Sun OTP security service.

/opt/SUNWotp/cli/deploy_otp -i s -f /export/input_otp.dat

Configure the Sun OTP AHE components as highly available services.

/opt/SUNWotp/cli/deploy_otp -c h -f /export/input_otp.dat

Restore the Sun OTP system management data that was backed up.

/opt/SUNWotp/cli/deploy_otp -u r -f /export/input_otp.dat -o "-R hostname"

hostname is the first host name where Sun OTP system management data was backed up.

Install Web SSO.

/opt/SUNWotp/cli/deploy_otp --install websso --file /export/input_otp.dat

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.

To Prepare Hosts for Dual-Partition Upgrade

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

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.

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.

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

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.

To Upgrade Sun OTP from 1.1 to 2.0 Using the GUI

Before You Begin

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.

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.

Click OTP Upgrade in the left panel.

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).

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).

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.

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).

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.

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.

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

To Upgrade Sun OTP from 1.1 to 2.0 Using CLI

Before You Begin

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

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

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.

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.

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.

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.

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.

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.

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).

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

Upgrading Sun OTP Using Live Upgrade

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

To Prepare Hosts for Live Upgrade

You must perform this procedure before you upgrade Sun Open Telecommunications Platform by using live upgrade.

Create the live upgrade disk partition similar to the root disk.

For example, prtvtoc -h /dev/dsk/c0t0d0s2|fmthard -s "-" /dev/rdsk/c0t1d0s2

To Transfer Global Devices to a New Root Disk

You must perform this procedure before you upgrade Sun Open Telecommunications Platform using live upgrade.

Backup the /etc/vfstab file.

cp /etc/vfstab /etc/vfstab.old

Open the /etc/vfstab file for editing.

Locate the line that corresponds to /global/.device/node@N.

Edit the global device entry as follows:
1. Change the DID names to the physical names.
2. Change /dev/did/{r}dsk/dYsZ to /dev/{r}dsk/cNtXdYsZ.
3. Remove global from the entry.
The following example shows the name of DID device d3s3, which corresponds to /global/.devices/node@s, changed to its physical device names and the global entry removed.

Original:

/dev/did/dsk/d3s3 /dev/did/rdsk/d3s3 /global/.devices/node@2 ufs 2 no global

Changed:

/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /global/.devices/node@2 ufs 2 no -

When the /etc/vfstab file is modified on all cluster nodes, run the OTP upgrade plan to upgrade the OS and cluster. See Upgrading Sun OTP Using Standard Upgrade.

After upgrading Sun OTP high availability service and before rebooting to the new boot environment (BE), restore the original /etc/vfstab file on each node of the un-upgraded BE.

cp /etc/vfstab.old /etc/vfstab

Mount the new Boot Environment (BE).

lumount sunotp1.1-sunotp2.0 /altroot

Locate the line that corresponds to /global/.devices/node@N and replace the dash (-) at the end of the entry with the word global.

/dev/dsk/cNtXdYsZ /dev/rdsk/cNtXdYsZ /global/.devices/node@N ufs 2 no global

Unmount the new BE.

luumount sunotp1.1-sunotp2.0

Check the BE status.

/usr/sbin/lustatus

Activate the BE.

/usr/sbin/luactivate BEname

BEname is the name of the boot environment variable.

Reboot the system.

/usr/sbin/init 6

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

To Upgrade Sun OTP Using the GUI

Before You Begin

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.

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.

Click OTP Upgrade in the left panel.

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 - live-upgrade.
  
  BEname - Name of the boot environment.
  
  diskLayout - Layout of the disk to be used for live upgrade.
  
  Syntax of diskLayout:
  
  mount1:disk_slice1-mount2:disk_slice2-mount3:disk_slice3
  
  Information for / (root), swap and /globaldevices is mandatory.
  
  Example:
  
  /:c2t3d0s0-swap:c2t3d0s1-/globaldevices:c2t3d0s3
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. Click run plan (includes preflight).

Back up Sun OTP system management data.

Run this plan only on the first Sun OTP host that 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).

Upgrade the operating system.

Run this plan on all the Sun OTP hosts.
1. Click Upgrade OS and click run.
2. Type the host name in the target host field.
3. Click run plan (includes preflight).
  
  Wait for the plan completion. The plan is upgraded on the alternate boot disk.

Upgrade Sun OTP high availability service.

Run this plan on all the Sun OTP hosts.
1. Click Upgrade HA Services and click run.
2. Type the host name in the target host field.
3. Click run plan (includes preflight).

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.

Activate the new cluster environment.

Run this step on all the Sun OTP hosts.
1. Check the boot environment.
  
  /usr/sbin/lustatus
2. Activate the boot environment.
  
  /usr/sbin/luactivate BEname
  
  BEname is the name of the boot environment.
3. Reboot all the Sun OTP hosts.
  
  /usr/sbin/init 6

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

To Upgrade Sun OTP Using CLI

Before You Begin

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

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

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 - live-upgrade.

h1_BEname - Name of the boot environment.

h1_diskLayout - Layout of the disk to be used for live upgrade.

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. 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.

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.

Upgrade the operating system.

/opt/SUNWotp/cli/deploy_otp -u P -f /export/input_otp.dat

Wait for the plan completion. The plan is upgraded on the alternate boot disk.

Upgrade the Sun OTP high availability service.

/opt/SUNWotp/cli/deploy_otp -u a -f /export/input_otp.dat

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.

Activate the new cluster environment.

Run this step on all the Sun OTP hosts.
1. Check the boot environment.
  
  /usr/sbin/lustatus
2. Activate the boot environment.
  
  /usr/sbin/luactivate BEname
  
  BEname is the name of the boot environment.
3. Reboot all the Sun OTP hosts.
  
  /usr/sbin/init 6

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

Troubleshooting

In case of a live upgrade failure, follow these steps to rollback the OS and Sun OTP availability service.

Activate the original boot environment.

/usr/sbin/luactivate old BE
Reboot to the selected boot environment.
Delete the failed upgrade partition.

ludelete new BE
Restart the upgrade process from OS.