Contents

1   Description

This instruction describes how to create and configure a Load-sharing for the SCCP protocol using the Ericsson Command-Line Interface (ECLI).

2   Procedure

2.1   Configure SCCP Load-sharing between two Destinations

Prerequisites

• A Managed Object (MO) SccpSignalingPoint exists.
• A Managed Objects (MOs), representing Destination (Destination MO), exists. The Destination MO can be an instance of one of following MOCs:
  • LocalSignalingPoint
  • RemoteSignalingPoint
  • LocalSap
  • RemoteSap

Steps

1. Navigate to the SccpSignalingPoint MO, for example:

   >dn ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1

2. Enter Config mode:

   (SccpSignalingPoint=1)>configure

3. Create the MO for the GtTranslator MOC, for example:

   (config-SccpSignalingPoint=1)>GtTranslator=1

4. Create the first MO for the GtDestination MOC, for example:

   (config-GtTranslator=1)>GtDestination=1

5. Set the value of the sap attribute as a reference to an MO to configure routing on. Examples:
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=1"
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,RemoteSap=1"
6. Change the CLI position to the parent MO (GtTranslator), for example:

   (config-GtDestination=1)>up

7. Create the second MO for the GtDestination MOC, for example:

   (config-GtTranslator=1)>GtDestination=2

8. Set the value of the sap attribute as a reference to an MO to configure routing on. Examples:
   • (config-GtDestination=2)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=2"
   • (config-GtDestination=2)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,RemoteSap=2"
9. Change the CLI position to the parent MO (GtTranslator), for example:

   (config-GtDestination=1)>up

10. Set the value of the primaryGtDestination attribute to refer to one of previously created GtDestination MO, for example:

    (config-GtTranslator=1)>primaryGtDestination="GtDestination=1"

11. Set the value of the secondaryGtDestination attribute to refer to another one of previously created GtDestination MO, for example:

    (config-GtTranslator=1)>secondaryGtDestination="GtDestination=2"

12. Set the value of loadShareIndicator. Example:

    (config-GtDestination=2)>loadShareIndicator=LOAD_SHARING

13. Set sane values for GtTranslator attributes. Example:

    (config-GtTranslator=1)>translationType=-2

    (config-GtTranslator=1)>numberSeries=*

14. Commit the changes:

    >commit

2.2   Configure SCCP Extended Load-sharing

Prerequisites

• It is possible to configure 4, 8 or 16 GtDestination MOs under GtTranslator MOC instance for SCCP extended loadsharing.
• A Managed Object (MO) SccpSignalingPoint exists.
• A Managed Objects (MOs), representing Destination (Destination MO), exists. The Destination MO can be an instance of one of following MOCs:
  • LocalSignalingPoint
  • RemoteSignalingPoint
  • LocalSap
  • RemoteSap

Steps

1. Navigate to the SccpSignalingPoint MO, for example:

   >dn ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1

2. Enter Config mode:

   (SccpSignalingPoint=1)>configure

3. Create the MO for the GtTranslator MOC, for example:

   (config-SccpSignalingPoint=1)>GtTranslator=1

4. Create the MO for the GtDestination MOC, for example:

   (config-GtTranslator=1)>GtDestination=1

5. Set the value of the sap attribute as a reference to an MO to configure routing on. Example:

   (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=2"

6. Change the CLI position to the parent MO (GtTranslator), for example:

   (config-GtDestination=1)>up

7. Perform steps 4-6 from this chapter 3, 7 or 15 times to configure necessary number of destinations. Example:

   (config-GtTranslator=1)>GtDestination=2

   (config-GtDestination=2)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=1"

   (config-GtDestination=2)>up

   (config-GtTranslator=1)>GtDestination=3

   (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=2"

   (config-GtDestination=31)>up

   (config-GtTranslator=1)>GtDestination=4

   (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=3"

   (config-GtDestination=41)>up

8. Set the value of the primaryGtDestination attribute to refer to one of previously created GtDestination MO, for example:

   (config-GtTranslator=1)>primaryGtDestination="GtDestination=1"

9. Set the value of the secondaryGtDestination attribute to refer to another one of previously created GtDestination MO, for example:

   (config-GtTranslator=1)>secondaryGtDestination="GtDestination=3"

10. Set the value of loadShareIndicator. Example:

    (config-GtDestination=2)>loadShareIndicator=LOAD_SHARING

11. Set sane values for GtTranslator attributes. Example:

    (config-GtTranslator=1)>translationType=-2

    (config-GtTranslator=1)>numberSeries=*

12. Commit the changes:

    >commit