CGIN 3.1 :: CGIN Installation and Administration Guide :: Signalware In-place upgrade procedure

This upgrade process supports upgrades where the service in use may initiate outbound CGIN dialogs.
It is supported when using Signalware for upgrades from CGIN 1.5.x to 2.0.x and from 2.0.x to 2.0.x

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

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.

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

Start the new cluster

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

Initially, not much traffic will be load balanced to the new cluster. With the default settings, initially only 1% of traffic will be allocated to the new cluster; so at low call rates, it may take some time before traffic is processed by the new cluster.

Verify that the new cluster is processing calls correctly.

To roll back this step:

Reconfigure each CGIN resource adaptor entity in the new cluster to set the RA property signalware.base-weight to 0. For example:
```
updateraentityconfigproperties entityname signalware.base-weight=0
```
Wait for all dialogs in the new cluster to end.
Stop the new cluster — change the SLEE state to STOPPED.

Drain calls from the old cluster

For each CGIN RA entity in the old cluster, reconfigure the RA entity to set the RA property signalware.base-weight to 0:
```
updateraentityconfigproperties entityname signalware.base-weight=0
```

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.

Now the old cluster should be still connected to the CGIN backends, but completely idle — no traffic is being handled by the old cluster.

To roll back this step, for each CGIN RA entity in the "old" cluster, reconfigure the RA entity to restore the original value of signalware.base-weight, by default 100.

Stop the old cluster

Stop the SLEE using the stop management command.
Wait for the SLEE to reach the STOPPED state.

To roll back this step, start the SLEE.

Shut down the old cluster

Shut down the old cluster using the shutdown management command.

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

Schedule upgrade of old backends to the new version

(if needed)

Previous page Next page