Installation and Configuration Issues

This section describes known Open Telecommunications Platform installation and configuration issues.

Deletion of the OTP Plug-in Requires the Deletion of All Hosts (6458703)

Before you can delete the OTP plug in from an external OTP installation server or a production OTP host, you must first delete all hosts for which you ran Plans as follows.

1. Log in to the server from which you ran the Plans to add additional OTP hosts.

2. Delete all of the target hosts only for each host for which you ran Plans from the OTP plug-in.

3. Delete the OTP plug-in.

Resource Group otp_system_group and Resource N1SPSMS-HA Fails During Load Test on Memory (6507395)

During load test on memory, the resource group otp_system_group fails with the error message Error--stop failed, and the resource N1SPSMS-HA fails with the error message Stop failed Faulted.

Workaround:

1. Log in as root on the clustered OTP host on which the OTP system management service is installed and running, 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.

2. Type /usr/cluster/bin/scswitch -F -g otp-system-rg to take the remote group offline.

3. Type the following commands in the sequence shown to disable cluster resources.

   1. /usr/cluster/bin/scswitch -n -j otp-spsms-rs

   2. /usr/cluster/bin/scswitch -n -j otp-spsra-rs

   3. /usr/cluster/bin/scswitch -n -j otp-sps-hastorage-plus

   4. /usr/cluster/bin/scswitch -n -j otp-lhn

4. Type /usr/cluster/bin/scswitch -u -g otp-system-rg to put the remote group into the unmanaged state.

5. Type /usr/cluster/bin/scrgadm -c -j otp-spsra-rs -x Stop_signal="15" to change the Stop_signal property of the remote agent resource to 15.

6. Type /usr/cluster/bin/scrgadm -c -j otp-spsms-rs -x Stop_signal="15" to change the Stop_signal property of the management service resource to 15.

7. Type /usr/cluster/bin/scswitch -o -g otp-system-rg to put the remote group into the managed state.

8. Type /usr/cluster/bin/scswitch -Z -g otp-system-rg to bring the remote group back online.

Invalid Logical Host Name Causes OTP to Become Unstable (6515464)

The logical host name must be exactly the same logical host name for each host in a clustered OTP system. If you enter a different logical host name for one or more clustered OTP hosts than what you entered for the other clustered OTP hosts, then the OTP data service becomes unstable.

Workaround: Make certain to specify the exact same logical host name for each clustered OTP host when entering provisioning plan data.

OTP Does Not Validate All User Input During Installation (6515467)

When you enter invalid inputs during OTP installation, installation may succeed. However, OTP services may not be properly configured.

Workaround: Make certain that you provide valid values when entering OTP plan information. The Sun Open Telecommunications Platform 1.0 Installation and Administration Guide provides OTP Plan worksheets for you to record installation information for each host prior to the installation process, which you should then use during installation to ensure the data you provide is correct. Print a worksheet for each host and then record and verify the information for each host prior to installing OTP.

Invalid Entry for Management and Provisioning Interfaces Fills Up The Root Filesystem /(6485018)

If you specify an incorrect interface for either the management interface or the provisioning interface, the configuration process will loop endlessly trying to connect to the invalid interface. Each connect attempt creates an error log, which in turn causes the log file to fill up all available space.

Workaround: Before starting the installation process, print and fill out the Plan worksheets provided in the Sun Open Telecommunications Platform 1.0 Installation and Administration Guide and make certain that you have specified the correct interface .