Perform the following steps to restore the SBC configuration using CLI:

Note

Restoring the SBC configuration on a SBC SWe Cloud platform is not supported. Instead, load the saved configuration to a new SBC SWe Cloud instance.

  1. Log on to the remote server where you have copied the configuration files, as described in Saving the SBC Configuration.

  2. Execute the following commands to copy the files to your SBC system:

    Example
    % cd /home/bob/SBC01/config
% sftp -oPort=2024 admin@SBC01a
Connecting to SBC01a
admin@10:54:19.17's password: xxxxxxx
sftp> put config_SBC01_20170324_021127.tar.gz /var/log/sonus/sbx/config/

  3. To view the saved configuration files, use the following CLI command:

    Example
    admin@SBC01a> show table system savedConfigList 

INDEX          FILE NAME                        SIZE         
----------------------------------------------------------
1      config_SBC01_20170324_021127.tar.gz  1061 KBytes  
  4. Log on to SBC CLI, and load the configuration by executing the following CLI command:


Example
admin@SBC01a> request system admin SBC01 loadConfig fileName config_SBC01_20170324_021127.tar.gz
This command will load the last saved configuration and restart the applications on active/standby servers. Do you want to continue (yes/no) y
Proceeding
result success
reason Starting DB restoration from: config_<server name>_20170324_021127.tar.gz please check /var/log/messages for progress


You must follow the procedure below to activate the traffic profile during loadConfig scenarios; loadConfig does not activate the profile

To configure the required profiles you must first reset the profile to default, and then set desired profile.

1. Note the current active profile from CLI (xxx_profile).
2. After loadConfig is done, activate the default profile in the system because the system will be in default profile.
3. After the system comes up after a reboot, activate the old active profile (for example, xxx_profile).

Note

When you load config dump taken from SBC versions older than 8.0, the loadConfig process internally converts Oracle based policy dump to the Postgres format. This process takes approximately 25 minutes to complete.


This command will restart application on both the servers and is service impacting.
Note

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.