To Enable High Availability for the OTP Provisioning Service on the First OTP Host

Before You Begin

System management and provisioning services must be set up on the additional OTP hosts as described in the previous procedure.

1. Open a Web browser and log in to the external OTP installation server service provisioning service.

   Go to URL http://install server:9090 where install server is either the IP address or the fully-qualifed name of the external OTP installation server.

2. Click OEM OTP to display the Open Telecommunications Platform home page.

3. Click Step 5. OTP High Availability for Provisioning Service on First Host: Enable beneath Multi Cluster Setup in the central menu.

   The edit High Availability plan page appears.

4. Click run.

   The High Availability Plan Variables page appears. Scroll the page down to display the variables

   Figure 5–19 Clustered OTP Host High Availability Plan Variables Page: First OTP Host

   
   

   Type the information in the plan variables fields according to your Clustered OTP Host Plan Worksheet. Refer to the OTP System Plan Settings Descriptions for information about each variable.

   ---

   Caution –

   Set limit overall running time of plan and limit running time of native calls to 2 hours each.

   ---

5. Click run plan (includes preflight).

   The page refreshes, and a progress bar is displayed during the provisioning process.

   The provisioning process installs and enables the application provisioning service high availability agent.

   When the provisioning process completes, click done.

6. Log in as root on thefirst 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.

7. Configure and enable fail-over.

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

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

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

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

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

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

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

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

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

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

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

   This completes the Open Telecommunications Platform graphical user interface installation process for a clustered OTP system.