Contents

1   Introduction

This document describes how to temporarily disable geographical redundancy in the SAPC.

1.1   Prerequisites

This section provides information of the prerequisites which must be fulfilled before using the procedure.

The following conditions must apply:

• Understand geographical redundancy functionality.
• Both SAPCs are in Active or Standby state.

2   Procedure

2.1   Disable Geographical Redundancy

To stop geographical redundancy, do the following:

1. Connect to the SAPC in which the administrative operation is executed and open an Ericsson Command-Line Interface (CLI) session:
2. Navigate to class GeoRedManager object:

   >dn ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1

3. Execute stop action:

   (ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)> stop

   If action was successfully executed, data replication stops until start command is executed.

   During this period, DBS, NR, Redundancy Disabled alarm is raised. Also, peer raises Policy Control, Geographical Redundancy Unable To Reach Peer alarm.

   If peer is in Standby state, it changes to Active state to takeover.

4. Verify the result of the action:

   (ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)>show

   Note:  

   Since this is a long-running operation, it can be required to enter show command several times until the final operation result is shown in the progress report.

   
   

   When the operation is successfully executed, it shows the following values:

   lastOperationExecuted=STOP

   lastOperationResult=ACTION_RESULT_OK

   To check the status of the node, verify that the attribute currentState is Halted

   If an error occurs during the execution of the operation, it shows the following values:

   lastOperationExecuted=STOP

   lastOperationResult=ACTION_RESULT_NOT_OK

   Attribute lastOperationDetailedInfo shows information about the error. It can take one of these values:

   • Already in Halted state
   • Not possible to execute stop action from <state> state
   • Not possible to execute stop action when peer is initial or halted state

2.2   Administrative Procedure

Execute the administrative procedure in the SAPC inHalted state.

2.3   Enable Geographical Redundancy

To enable again geographical redundancy, do the following:

1. Configure Active SAPC as Preferred and Halted SAPC as Non-Preferred (See Change Preferred Role in Geographical Redundancy). This guarantees that the data changes performed during the administrative procedure are not lost.
2. Connect to the Halted SAPC and open an Ericsson Command-Line Interface (CLI) session:
3. Navigate to class GeoRedManager object:

   >dn ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1

4. Execute start action:

   (ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)> start

   If action was successfully executed, data replication starts and the SAPC synchronizes with the peer.

   DBS, NR, Redundancy Disabled alarm is cleared. Peer clears Policy Control, Geographical Redundancy Unable To Reach Peer alarm.

5. Verify the result of the action:

   (ManagedElement=1,PolicyControlFunction=1,GeoRedManager=1)>show

   Note:  

   Since this is a long-running operation, it can be required to enter show command several times until the final operation result is shown in the progress report.

   
   

   When the operation is successfully executed, it shows the following values:

   lastOperationExecuted=START

   lastOperationResult=ACTION_RESULT_OK

   To check the status of the node, verify that the attribute currentState is not Halted.

   If an error occurs during the execution of the operation, it shows the following values:

   lastOperationExecuted=START

   lastOperationResult=ACTION_RESULT_NOT_OK

   Attribute lastOperationDetailedInfo shows information about the error. It can take one of these values:

   • Not possible to execute start action from <state> state
   • Parameter <parameter> not valid