Active-Active Geographical Redundancy
Ericsson Service-Aware Policy Controller

Contents
This instruction provides a guideline for configuring the SAPC for Active-Active geographical redundancy. This can be managed
using NETCONF or the ECLI to manipulate the MIB.
The following figure shows the different state transitions because
of geographical redundancy OAM procedures:
Figure 1 State transitions because of geographical redundancy OAM
procedures
The following figure shows the different state transitions taking
into account both SAPC peers:
Figure 2 State transitions in both SAPC peers because of geographical
redundancy OAM procedures
The following conditions must be fulfilled before the data presented
in this document is configured in an operational network:
CBA components are installed.
The SAPC product software has been installed.
Understand Geographical Redundancy functionality.
This procedure retrieves the geographical redundancy state of the SAPC.
During normal operation, it is expected that the SAPC is in Distributed state.
To monitor geographical redundancy state, do the following:
Steps
-
Connect to the SAPC and open an Ericsson
Command-Line Interface (CLI) session.
-
Navigate to
class GeoRedManager object:
>dn ManagedElementId=1,PolicyControlFunction=1,GeoRedManager=1
-
Execute action show:
(ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)>
show
-
Verify the values of currentState and previousState attributes.
To check geographical redundancy configuration, do the following:
Steps
-
Connect to the SAPC and open an Ericsson
Command-Line Interface (CLI) session.
-
Navigate to
class GeoRedManager object:
>dn ManagedElementId=1,PolicyControlFunction=1,GeoRedManager=1
-
Execute action showConfiguration:
(ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)>
showConfiguration
-
Verify the values of Local IP, Peer IP, and Role attributes.
To perform low-level maintenance activities on one of both SAPC
other than upgrading the version (such as hardware replacements),
it is recommended to disable the geographical redundancy and halt
the SAPC to be maintained. If the maintenance task is to be performed
in both SAPC, it is preferable to start with the one configured as Non Preferred. To do so follow these steps:
Steps
-
On the desired SAPC temporarily disable geographical redundancy
by following
Temporarily Disable Active-Active Geographical Redundancy. This procedure
stops the DBS replication and changes the state to Halted. The other SAPC passes to Active state.
-
On the other SAPC (it should be in Active state), execute the following command to disable DBS replication:
>immcfg -a isEnabled=0 dbsNetsharedConfigId=1
-
Perform the maintenance task on the Halted SAPC.
-
On the Active SAPC, enable
again the DBS replication by executing:
>immcfg -a isEnabled=1 dbsNetsharedConfigId=1
-
On the Halted SAPC, enable
again the geographical redundancy following the procedure Enable Active-Active
Geographical Redundancy documented at
Temporarily Disable Active-Active Geographical Redundancy.
-
Execute the following command and wait until all payload
processors (PLs) show idle state in both SAPC:
>clurun.sh -c netshared_state_dump
-
Repeat steps from 1 to 7 on the other SAPC if needed.
-
If desired, modify preferred roles by following
Change Preferred Role in Active-Active Geographical Redundancy.
The following is the list of alarms related to Geographical Redundancy:
The DBS ones are the following: