Add Active-Active Geographical Redundancy to a Live SAPC
Ericsson Service-Aware Policy Controller

Contents
This document describes how to add Active-Active Geographical Redundancy
to a live SAPC, that is, how to add a second SAPC to a standalone
system. It also describes how to make the introduction of the second SAPC from
a network point of view.
Warning!
Only PNF deployments support Active-Active Geographical Redundancy.
This document is valid only for PNF deployments.
The following sections describe the documents, conditions, and
tools required before the procedure.
Interconnection SAPC1 and SAPC2
Customer Network supplies an external network for data
replication between SAPC1 and SAPC2
Geographical Redundancy Licenses
Upgrade the Installed Licenses with an extra License
Key File for SAPC1.
Order a complete License Key File for SAPC2.
Documents
Before starting this procedure, ensure that you have read the following
documents:
Application-specific documents describing the configuration
to be used in the new SAPC.
Check also the following documents:
For the installation of the new SAPC (required only on the new
site, SAPC2):
This section describes the installation procedure step-by-step.
Some steps must be coordinated between the two SAPC while others
can be performed independently. If coordination is required, it is
clearly stated in the relevant step.
Steps
-
Follow the installation instructions for the SAPC2 contained
in
SAPC PNF Deployment Instruction to configure the
Mated SAPC as non-preferred because live SAPC has to be configured
as preferred.
Results
Once the configuration is applied, the SAPC2 is in Initial State. That means that it is
ready to be started after the live SAPC has been configured as Active-Active Geographical
Redundancy SAPC.
Steps
-
Add Geographical Redundancy license in SAPC1.
-
Add the replication template in the BSP 8100, following the BSP 8100 Configuration
section in
SAPC PNF Deployment Instruction.
Attention!
At this stage, this step only applies to BSP.
-
Access to the <OAM-VIP> and
then the SC-1.
<InstallationServer>:#
ssh root@<OAM-VIP>
SC-<X>:#
ssh root@SC-1
-
Copy the following file:
SC-1:# cp /cluster/storage/no-backup/adapt/adapt_cluster.cfg.processed
/cluster/storage/no-backup/adapt/adapt_cluster.cfg
-
Update write permissions:
SC-1:# chmod u+w /cluster/storage/no-backup/adapt/adapt_cluster.cfg
-
Modify the adapt_cluster.cfg as follows:
-
Create ALB to configure new network to be
used for replication purpose, add the corresponding values in the [Network] section. For further details, refer to
Adapt Cluster Tool.
-
Add [GeoRed] section. For further details,
refer to
Adapt Cluster Tool:
[GeoRed]
ACT_ACT =
<true>
. To select
Active-Active Geographical redundancy solution.
PREFERRED =
<1>
. This
SAPC is
configured as preferred.
| Note: |
The SAPC configured as preferred maintains the database
to resolve some fault situations where is not possible to know which
of the SAPC clusters holds the most up-to-date database.
|
-
Execute the customizing tool command.
<SC-1>:#
adapt_cluster -f /cluster/storage/no-backup/adapt/adapt_cluster.cfg
geored
Once the tool finishes, the Geographical Redundancy configuration
is applied.
-
To check that everything has been successful, the following
file must contain the same info as adapt_cluster.cfg
<SC-1>:#
cat /cluster/storage/no-backup/adapt/adapt_cluster.cfg.processed_expansion
-
Once the configuration is applied, the SAPC1 is working
as preferred SAPC in Active state. Consider that SAPC1 arises
several alarms (
DBS, NR, Synchronization Needed and
DBS, NR, Connection Lost) until the SAPC2 starts
as non-preferred SAPC.
Steps
-
To start SAPC2, follow the
Start Active-Active Geographical Redundancy procedure.
-
Once SAPC2 is fully replicated and ready to process
traffic, update the neighbor peers configuration with the new SAPC2 VIP
addresses for traffic management and provisioning.