SONUS Documentation By Monesh.

How to take back up in Sonus SBC?

Saving the SBC Configuration using EMA

 
The SBC EMA provides the ability to generate a system backup file. The user can restore the
configuration files from the storage location. During this process, the system will restart and the user
has to re-login, once the system is up and running. This is useful if you upgrade the SBC EMA and
need to reload the old configurations.
The SBC stores up to 10 manual and seven automatic backup files.
Perform the following tasks to create a system backup file:

1. Select Administration > System Administration > Backup/Restore. Click Delete to

remove/delete any of the highlighted backup files.

Figure : System backup/Restore
2. Click Yes, to backup the current system.

Figure : Backup Current Software

3. Enter the File Name Suffix.

4. Click Save. Once the Backup for the system is created, the SBC displays the following

message:

Figure : BackupRestore - Successful Message

5. Click OK to complete the process.

Go to start of metadata

Saving the SBC Configuration using CLI

 
Perform the following steps to save the existing SBC configuration. The backup file created by this
procedure is used to restore the system configuration if reinstallation of the software is needed for any
reason.
To reload the SBC configuration, refer to Restoring SBC Configuration for guidance.
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 SBC CLI. Execute the following command to save the SBC configuration.

Command Syntax

% request system admin <SYSTEM NAME> saveConfig

2.

Command Example

3. Example:

admin@SBCSWE1A> request system admin SBCSWE1 saveConfig

This command will save the current configuration. Do you want to continue [no,yes] yes
result success
reason Configuration Saved as : config_SBCSWE1_20181004_191349.tar.gz

4. Note

5. This command saves the current configuration to a time-stamped zipped tar file located

in /var/log/sonus/sbx/config directory of SBC active server. 

6. Use SFTP to copy the configuration file from the active server to the remote server. Following

is an example to transfer the saved configuration file to a remote linux server.

Example:

# sftp -oPort=2024 admin@SBC01a:/var/log/sonus/sbx/config/config_SBC01_20110824_021127.ta

admin@SBC01a's password: <admin>
Connected to SBC01a.
Fetching /var/log/sonus/sbx/config/config_SBC01_20110824_021127.tar.gz to /home/bob/SBC01

Setting Up SBC 5400 Physical Connection

Between High Availability Nodes
Skip to end of metadata

Go to start of metadata

 
In an HA configuration, the two SBC 5400 platforms are connected to each other with two 1 Gb/s HA
links. The connection provides box-level redundancy.
Each of the HA peer SBC 5400 platforms has four management ports with their own addresses, and
these platforms can each be controlled through these addresses whether the platform is currently in
an Active or Standby state. Additionally, the user can assign a Logical Management address to the
HA pair (refer to Configuring Logical Management Interfaces). The user can control the Active HA
peer through this Logical Management address and When switchover occurs, the logical management
address follows the currently active server.
For the media ports, the MAC and IP addresses float between the HA pair (are replicated from Active
to Standby on HA peer switchover).
Connect HA cables between the HA pair as shown:
Active HA0<--------->Standby HA0
Active HA1<--------->Standby HA1
Note
The SBC 5400 fails to pair with a machine that is not operating with an identical configuration (for
example, same Media Port Speed setting for both SBC 5400 HA peers). Furthermore, an SBC 5400
can only pair with another SBC 5400 platform of the same type (for example, an SBC 5400 can only
pair with another SBC 5400). 
Figure : SBC 5400 HA Pair Set Up

Installing SBC 5400 ERE Standalone

Skip to end of metadata
 Go to start of metadata
Note
Windows and/or dialog boxes depicted in this section are intended as examples only and may not
reflect the actual software/firmware versions applicable to you. Refer to any associated
hardware/software requirements as well as the relevant release note for software/firmware version
details. 
The following procedure describes how to install the SBC 5400 application as a standalone
configuration: 

1. Launch the EMA. Refer to Logging on to EMA in Platform Mode for guidance.

2. Navigate to Administration > System Administration > Software Install/Upgrade tab.

The Packages screen is displayed.

3. Select the Package Name to install.

Figure : Selecting the SBC 5400 Application Package

4. Click Install Software.

The Install Software section expands and displays the Install Version, Management Ports (configured via

the BMC) and System Configuration details. It also verifies the software package.

Figure : Verifying the SBC 5400 Application

 Note

The signature file of the SBC package verifies the integrity of the package contents before proceeding

with the SBC installation. 

5. Enter the System Configuration details.

a. Select Standalone in the HA Configuration field.

b. Select System Name field and enter the system name.

c. Select Local Hostname and enter local hostname.

Note

For more information, refer to SBC 5400 - System Name and Hostname Conventions. 

Figure : SBC 5400 Configuration Screen

d. Choose the Active option for Server Role to designate the Active server as the one

you are configuring.

e. For SBC hardware type of installation, choose SBC Type as I-SBC.

For SBC Type, choose from the options listed:

SBC Description
Type

I-SBC Specifies an Integrated Signaling and Media network element (I-SBC). This is
applicable for SBC on hardware environment (SBC 5000 Series, SBC 7000
Series, and SBC 5400).

S-SBC Specifies the SBC type as Signaling. The S-SBC (Signaling SBC) is applicable
for SBC on Cloud environment.
 SBC Description
Type

M-SBC Specifies SBC type as Media. The M-SBC (Media SBC) is applicable for
SBCona cloud environment.

f. Select NTP Server IP field and enter the NTP server IP address. To identify your

NTP Server IP, refer to Configuring SBC 5400 NTP Server Settings.

g. Select NTP Server Time Zone field and enter the time zone.

6. Click Start Installation.

7. The installation process starts and displays the installation status on the Installation

Log section. The following actions are performed during the installation process:

a. Performs pre-install checks

Figure : Performing Pre-Install Checks

b. Extracts package contents

Figure : Extracting the Package Contents

c. Installs SBC 5400 service

Figure : Installing SBC Services

d. Initializes SBC 5400 service

Figure : Initializing SBC Service

e. Updates SBC 5400 Host Name

Figure : Updating the Host Name

f. Reboots the SBC 5400 system

Figure : Rebooting the SBC Application

8. Log on to EMA. The new SBC application version is displayed on

the Monitoring > Dashboard > System and Software Info window.

Figure : SBC 5400 System and Software Info

9. Verify the system status using Administration > System Administration > Platform

Management menu.

10. From the EMA, install the SBC licenses required in order to use SBC application and its

features. See Node-Locked Licensing for guidance.