Note

This upgrade process supports upgrades where the service in use may initiate outbound CGIN dialogs.
It is supported when using OCSS7 for upgrades from CGIN 1.5.x to 2.0.x and from 2.0.x to 2.0.x
The existing CGIN RA entity must be configured to connect to the SGCs using the ocss7.sgcs connection method.

1
Set up the new cluster

  • Install the new cluster. Ensure that the cluster ID used is different to that of the old cluster, and that files, databases, and ports used by the new cluster don’t overlap with the old cluster.

  • Boot the new cluster.

  • Ensure that Rhino is in the STOPPED state

  • Deploy and configure RAs and services. Configure CGIN RA entities in the same way as on the "old" cluster, pointing to the same SGC addresses.

Tip A Rhino export from the old cluster may be useful for this step.

Now you should have the "new" cluster configured, but STOPPED, so that it is not receiving traffic.

Caution To roll back this step, just discard your new cluster install. (No traffic is being processed by the new cluster yet.)

2
Start the new cluster

  • To start the "new" cluster, change the SLEE state to RUNNING. The new cluster RAs will connect to the same SGCs as the old cluster. New incoming traffic will be load balanced between the old and new clusters.

  • Verify that the new cluster is processing calls correctly.

Caution

To roll back this step:

  1. Reconfigure each CGIN resource adaptor entity in the new cluster to set the RA property ocss7.sgcs to an empty string. For example:

    updateraentityconfigproperties entityname ocss7.sgcs=

  2. Wait for all dialogs in the new cluster to end.

  3. Stop the new cluster — change the SLEE state to STOPPED.

3
Drain calls from the old cluster

  • For each CGIN RA entity in the old cluster, reconfigure the RA entity to set the ocss7.sgcs configuration property to be an empty string. For example:

    updateraentityconfigproperties entityname ocss7.sgcs=
Note If upgrading the cluster from CGIN 1.5.x.y the old cluster’s ocss7.sgcs property may not be set to empty. In this case it should be set to an address that does not correspond to a live SGC or other TCP service. For example: ocss7.sgcs=invalidhost:11111. The old CGIN RA will emit warnings and alarms about not being able to connect to that address. These are expected and can be ignored.

At this point, all new dialogs will be directed to the new cluster only. The old cluster will only continue to process existing dialogs established before the draining process started.

  • Wait for all dialogs in the old cluster to end.

Once all dialogs have ended the connections to the SGC cluster will terminate automatically. No traffic is handled by the old cluster.

Caution To roll back this step, for each CGIN RA entity in the "old" cluster, reconfigure the RA entity to restore the original value of ocss7.sgcs.

4
Stop the old cluster

  • Stop the SLEE using the stop management command.

  • Wait for the SLEE to reach the STOPPED state.

Caution To roll back this step, start the SLEE.

5
Shut down the old cluster

  • Shut down the old cluster using the shutdown management command.

Caution To roll back this step, restart the "old" cluster processes.

6
Schedule an upgrade of the SGC to the new version

(if needed)
Previous page Next page