This section applies in the case where the Rhino VoLTE TAS SGC has previously received its initial configuration and now requires reconfiguration.
Reconfiguration of the SGC requires a SMO or an SGC VM with version 4.0.0-9-1.0.0 or newer. Reconfiguration of the SGC component in older VMs is not supported.
Reconfiguring the SGC will cause a full SS7 outage in live deployments. |
You must carry out the process documented here exactly as documented. It should not be skipped or modified. |
What you need
-
❏ The
sgctool
utility (available on the SGC or SMO VM). -
❏ The IP address of one of the deployment’s TSN nodes (
<cds_address>
). -
❏ The deployment ID (
<deployment_id>
). -
❏ The group ID (
<group_id>
).
Process overview
Here is the high-level view of the required steps:
-
Stop the OCSS7 SGCs.
-
Verify that the OCSS7 SGCs are stopped.
-
Delete the OCSS7 SGCs.
-
Clear OCSS7 SGC-related state from the TSN nodes (CDS).
-
Apply the new configuration.
Process detail
1. Stop the OCSS7 SGCs
You need to stop every SGC in the cluster. On each SGC or SMO node, issue the following command:
$ sudo systemctl stop ocss7
The following message may be safely ignored:
|
2. Verify that the OCSS7 SGCs are stopped
-
Check the systemctl status of the
ocss7
service. On each SGC or SMO node issue the following command:
$ sudo systemctl status ocss7
Dec 22 15:45:28 tst-sgc-1 systemd[1]: Stopping Start the OCSS7 SGC...
Dec 22 15:45:28 tst-sgc-1 ocss7[5029]: Stopping processes:
Dec 22 15:45:28 tst-sgc-1 ocss7[5029]: SGC:2027
Dec 22 15:45:28 tst-sgc-1 ocss7[5029]: DAEMON:2017
Dec 22 15:45:28 tst-sgc-1 ocss7[5029]: Initiating graceful shutdown for [2027] ...
Dec 22 15:45:28 tst-sgc-1 ocss7[5029]: Sleeping for max 32 sec waiting for graceful shutdown to complete.
Dec 22 15:45:39 tst-sgc-1 ocss7[5029]: Graceful shutdown successful
Dec 22 15:45:39 tst-sgc-1 ocss7[5029]: Shutdown complete (graceful)
Dec 22 15:45:39 tst-sgc-1 systemd[1]: Stopped Start the OCSS7 SGC.
-
Check the OCSS7 SGC’s view of its own status. On each SGC or SMO node issue the following command:
$ ~/ocss7/<deployment_id>/<instance_id>/current/bin/sgc status
SGC is down
3. Delete the OCSS7 SGCs
On each SGC or SMO node, remove the OCSS7 SGC installation:
$ rm -rf /home/sentinel/ocss7/<deployment_id>/
Do not delete |
4. Clear OCSS7 SGC-related state from the TSN nodes (CDS)
Remove OCSS7 SGC configuration data that was persisted to the Cassandra Data Store (CDS). This only needs to be carried out once per SGC or SMO cluster.
-
Run the
sgctool
from one SGC or SMO VM:
$ /opt/tasvmruntime-py/bin/sgctool clear-config --cds-address <cds_address> --deployment-id <deployment_id> --group-id <group_id>
The CDS SGC state has been cleared
The |
5. Apply the new configuration
You may now apply the new configuration using rvtconfig
, as documented in
Declarative configuration.