Sun Open Telecommunications Platform 1.0 Installation and Administration Guide

Installing the Open Telecommunications Platform On A Standalone OTP Host

Manual command-line installation and setup of the Open Telecommunications Platform on a standalone OTP host is comprised of the following steps:

This section discusses the following topics:

Caution –

Failure to perform the following procedures in sequence presented will result in Open Telecommunications Platform installation failure.
Manual installation requires the creation of several OTP system state files which contain key names and values used by the installation and configuration process. Do not change the key names. The key names are case sensitive. For example, mediaDirectory is valid, whereas MediaDirectory is not valid and will cause installation to fail. Providing incorrect values for a key name will cause installation to fail, or cause the installed OTP system to become unstable.

If installation fails, you must perform a complete reinstall of the Solaris 10 Update 2 OS, and then install the Open Telecommunications Platform again.

To Set Up the OTP High Availability Framework

Install the OTP CLI package.

Type pkgadd -d /net/OTP install directory/Products/packages -R / SUNWotpcli where OTP install directory is the installation source directory you created in Step 8 of the procedure To Download and Uncompress the OTP and Solaris OS Installation Zip Files.

For example, if the installation server name is otpinstall, and the NFS-mounted installation directory is /otp1.0, you would then type:
# pkgadd -d /net/otpinstall/otp1.0/Products/packages -R / SUNWotpcli
The directory /opt/SUNWotp10/CLI is created.

Create the standalone OTP host availability state file.
1. Change directory to /opt/SUNWotp10/CLI.
2. Type cp templates/setupAvailabilityServiceOnStandalone.dat /var/tmp/setupAvailabilityServiceOnStandalone.dat

Edit the file /var/tmp/setupAvailabilityServiceOnStandalone.dat as follows.
- mediaDirectory=OTP_Installation_directory: The fully qualified path name of the Open Telecommunications Platform installation directory, for example: /net/otpinstall/otp1.0
- clusterName=cluster_name: The name you have chosen for the clustered OTP system.
- allPatches=yes to install all patches.
  
  allPatches=no to install mandatory patches only.
- autoConfigureIPMP:
  
  autoConfigureIPMP=no if you do not want to set up IPMP.
  
  To set up IPMP, set autoConfigureIPMP=yes, and add the following three lines:
  - secondaryInterface=Ethernet interface 2
  - secondaryIP=111.112.113.114 where 111.112.113.114 is the IP address of Ethernet interface 2.
  - testIPAddress=111.112.113.222 where 111.112.113.222 is the IP address used for IPMP configuration.
Save and close the file.

The single-node availability state file should be similar to the following:
```
mediaDirectory=/net/otpinstall/otp1.0
clusterName=otp-standalone-host
allPatches=yes
autoConfigureIPMP=yes
secondaryInterface=bge1
secondaryIP=10.11.52.68
testIPAddress=10.11.52.74
```

Set up the availability service.

Type /opt/SUNWotp10/CLI/setupAvailabilityServiceOnStandalone /var/tmp/setupAvailabilityServiceOnStandalone.dat.

The setupAvailabilityServiceOnStandalone script performs the following tasks:
- Installs required Solaris OS patches
- Installs the OTP high availability framework
- Configures the OTP high availability framework
- Reboots the standalone OTP host
The setupAvailabilityServiceOnStandalone installation process logs to the file /var/tmp/OTPInstaller.log. You can use the tail -f command during installation to view the log file.

When the standalone OTP host has rebooted, log in as root again.

Run the setupAvailabilityServiceOnStandalone script again, specifying the same availability state file.

For example:
# /opt/SUNWotp10/CLI/setupAvailabilityServiceOnStandalone \ /var/tmp/setupAvailabilityServiceOnStandalone.dat
The setupAvailabilityServiceOnStandalone script verifies the OTP high availability framework installation and configuration.

Next Steps

Set up the OTP system management and application provisioning services as described in the next procedure.

To Set Up the OTP System Management and Application Provisioning Services

Create the standalone OTP host management and provisioning state file.
1. Change directory to /opt/SUNWotp10/CLI.
2. Type cp templates/setupManagementServicesOnStandalone.dat /var/tmp/setupManagementServicesOnStandalone.dat

Edit the file /var/tmp/setupManagementServicesOnStandalone.dat as follows.
- mediaDirectory=OTP_Installation_directory: The fully qualified path name of the Open Telecommunications Platform installation directory, for example: /net/otpinstall/otp1.0
- managementInterface=management interface name where management interface name is bge0 or bge1 or ce0 or ce1 depending on the interface you have chosen for the management interface, and on the platform type.
- provisioningInterface=provisioning interface name where provisinoing interface name is bge0 or bge1 or ce0 or ce1 depending on the interface you have chosen for the provisioning interface, and on the platform type.
- logicalHost=logical host name where logical host name is an unused logical host name on the same subnet as the standalone OTP host. If a logical host name that exists on a different subnet is specified, installation fails.
- logicalIPAddress=logical host IP address where logical host IP address is an unused IP address to be assigned to logicalHost
Save and close the file.

The single-node management and provisioning state file should be similar to the following:
```
mediaDirectory=/net/otpinstall/otp1.0
managementInterface=bge0
provisioningInterface=bge0
logicalHost=otpclient1-logicalhostname
logicalIPAddress=10.11.55.170
```

Set up the management and provisioning services.

Type /opt/SUNWotp10/CLI/setupManagementServicesOnStandalone /var/tmp/setupManagementServicesOnStandalone.dat.

The setupManagementServicesOnStandalone script performs the following tasks:
- Installs the Java Web console
- Installs the OTP system management service high availability agent
- Installs the OTP application provisioning service high availability agent
- Installs patches required by the Open Telecommunications Platform
- Installs and configures the OTP system management service
- Installs and configures the OTP application provisioning service
The setupManagementServicesOnStandalone installation process logs to the file /var/tmp/OTPInstaller.log. You can use the tail -f command during installation to view the log file.

Next Steps

Enable high availability on the standalone OTP host as described in the next procedure.

To Enable High Availability for the OTP Provisioning Service

Create the standalone OTP host high availability state file.
1. Change directory to /opt/SUNWotp10/CLI.
2. Type cp templates/enableManagementServicesHA.dat /var/tmp/templates/enableManagementServicesHA.dat

Edit the file /var/tmp/templates/enableManagementServicesHA.dat as follows.
- mediaDirectory=OTP_Installation_directory: The fully qualified path name of the Open Telecommunications Platform installation directory, for example: /net/otpinstall/otp1.0
- logicalHost=logical host name where logical host name is an unused logical host name on the same subnet as the standalone OTP host. If a logical host name that exists on a different subnet is specified, cluster installation fails.
Save and close the file.

The single-node high availability state file should be similar to the following:
```
mediaDirectory=/net/otpinstall/otp1.0
logicalHost=otpclient1-logicalhostname
```

Enable high availability for the OTP provisioning service.

Type /opt/SUNWotp10/CLI/enableManagementServicesHAOnStandalone /var/tmp/enableManagementServicesHA.dat

The enableManagementServicesHAOnStandalone script installs and enables the OTP application provisioning service high availability agent, and logs to the file /var/tmp/OTPInstaller.log.

This completes the Open Telecommunications Platform manual installation process for a standalone OTP host.

Log in as root on the standalone OTP host and restart the remote agent.

Type /etc/init.d/n1spsagent restart to restart the remote agent. If the remote agent is not restarted, then the service provisioning service on the first OTP host will not work properly.