Versions Compared

Old Version 7

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
iconfalse
titleNote

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

Spacevars
0product
configuration using CLI:

Multiexcerpt include
MultiExcerptNameSBC SWe Cloud restore limitation
PageWithExcerptSaving the SBC Configuration using CLI

  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:

    Code Block
    languagenone
    titleExample
    % cd /home/bob/SBC01/config
% sftp -oPort=2024

...

  1. admin@SBC01a
Connecting to SBC01a

...

  1. admin@10:54:19.17's password: xxxxxxx
sftp> put config_SBC01_20170324_021127.tar.gz /var/log/sonus/sbx/config/

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

    Code Block
    languagenone
    titleExample
    admin@SBC01a> show table system savedConfigList 

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

 

Code Block
languagenone
titleExample
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

 

 

 

Info

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).

 

 

Warning
This command will restart application on both the servers and is service impacting.
Info
iconfalse
titleNote

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.

 

 

Pagebreak