This page includes instructions for doing a live upgrade from an existing Rhino cluster that is receiving traffic through CGIN, to a new cluster that has the same configuration but different software versions (such as a new Rhino or CGIN version, or new service version if it can’t be done in a single cluster).
|
These procedures refer specifically to upgrading the CGIN component. They do not cover upgrading the underlying OpenCloud OCSS7 SGC stack or Mavenir Signalware stack. |
Below are general information about and then instructions for performing upgrades using STP redirection, OCSS7 In-place upgrade and Signalware In-place upgrade.
About cluster upgrades with CGIN
Below is a table of possible upgrade paths for clusters using the CGIN OCSS7 TCAP stack or Signalware TCAP stack:
| Old version | New version | Upgrade using STP redirect? | Upgrade in-place (Signalware)? | Upgrade in-place (OCSS7)? |
|---|---|---|---|---|
1.5.x |
2.0.x |
Yes |
Yes |
Yes |
2.0.x |
2.0.x |
Yes |
Yes |
Yes |
|
A warning about ETC/ARI dialog correlation
ETC/ARI dialog correlation arranges for inbound ARI dialogs to be directed to the same cluster node that sent the corresponding ETC. In general, dialog correlation can only happen within a single cluster. During an upgrade, there are two clusters present and receiving traffic. If an ARI dialog is received by the "wrong" cluster (a cluster that did not send the corresponding ETC), then correlation will fail, and the ARI will not be directed to the correct cluster node. If dialog correlation is used, then care should be taken to ensure that ARI dialogs are directed to the correct cluster — for example, by configuring the service deployed in the new cluster to send ETCs that direct the ARI dialogs to an SCP address associated with the new cluster only. |
