Re-installing a SBC system from an ".iso" image followed by restoring SBC configuration from a tar.gz backup file may lead to loss of encrypted configuration parameters in the following scenarios:
- re-installing a standalone SBC from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file
- re-installing both nodes in an HA SBC pair from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file
Activities like replacing a single node in an HA pair (as an RMA for example) or re-installing a single node in an HA pair at a time are safe. The node that has just been re-installed will take the current configuration from the active node.
For details please refer to Sonus Warning: Warning-17-00022737.
Perform the following steps to restore the SBC configuration using CLI:
Log on to the remote server where you have copied the configuration files, as described in Saving the SBC Configuration.
Execute the following commands to copy the files to your SBC system:
To view the saved configuration files, use the following CLI command:
Log on to SBC CLI, and load the configuration by executing the following CLI command:This command will restart application on both the servers and is service impacting.
When reloading a saved configuration, make sure the standby server is stable or the server is reachable. If the standby is restarted or rebooted, wait until the server is stable before proceeding.
If the standby system crashes before the load config completes, stop the standby server and allow the original active server to come back online as active.