Contents

1   Description

This instruction describes how to create and configure a Routing on Remote or Local Destination for the SCCP protocol using the Ericsson Command-Line Interface (ECLI).

The instructions below considers only configuring a Primary Destination, but can be applied for any other.

2   Procedure

2.1   View Available MOs for any MOC

Steps

1. Run show command

   >show -m MocName -r

   Where MocName is the name of the MOC to get available MOs for.

   The following is an example:

   show -m RemoteSignalingPoint -r

   ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=SccpRemoteSpInap remoteSignalingPointCode=100 reservedBy "ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=0,SccpSignalingPoint=SccpForInap,RemoteSap=SccpRemoteSpInap" "ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1,RkGrouping=1" ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=SccpRemoteSpSccpCl remoteSignalingPointCode=103 reservedBy "ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=3,SccpSignalingPoint=SccpForSccpCl,RemoteSap=SccpRemoteSpSccpCl" "ManagedElement=1,Ss7=1,M3ua=1,LocalAs=4,RkGrouping=1" ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=SccpRemoteSpSccpCo remoteSignalingPointCode=102 reservedBy "ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=2,SccpSignalingPoint=SccpForSccpCo,RemoteSap=SccpRemoteSpSccpCo" "ManagedElement=1,Ss7=1,M3ua=1,LocalAs=3,RkGrouping=1" ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=SccpRemoteSpTcap remoteSignalingPointCode=101 reservedBy "ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=SccpForTcap,RemoteSap=SccpRemoteSpTcap" "ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2,RkGrouping=1"

2.2   Configure Routing on Destination for current Local Node only

Prerequisites

• A Managed Object LocalSignalingPoint, representing Local Node, exists.
• A Managed Object SccpSignalingPoint under LocalSignalingPoint MO exists.
• A Managed Object, 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. Examples:
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=2"
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=2"
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,LocalSap=2"
   • (config-GtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1,SccpSignalingPoint=1,RemoteSap=2"
6. Change the CLI position to the parent MO (GtTranslator), for example:

   (config-GtDestination=1)>up

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

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

8. Set sane values for GtTranslator attributes. Example:

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

   (config-GtTranslator=1)>numberSeries=*

9. Commit the changes:

   >commit

2.3   Configure Routing on Destination for every Local Node in current Network

Prerequisites

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

Steps

1. Navigate to the SignalingNetwork MO, for example:

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

2. Enter Config mode:

   (SignalingNetwork=1)>configure

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

   (config-SignalingNetwork=1)>SharedGtTranslator=1

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

   (config-SharedGtTranslator=1)>SharedGtDestination=1

5. Define the DN of Destination MO to configure routing on (see: Section 2.1)
6. Set the value of the sap attribute. Examples:
   • (config-SharedGtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=1"
   • (config-SharedGtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,SharedRemoteSap=1"
   • (config-SharedGtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=3,SccpSignalingPoint=1,RemoteSap=2"
   • (config-SharedGtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=3,SccpSignalingPoint=1,LocalSap=1"
   • (config-SharedGtDestination=1)>sap="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1"
7. Change the CLI position to the parent MO (GtTranslator=1), for example:

   (config-SharedGtDestination=1)>up

8. Set the value of the primaryGtDestination attribute, for example:

   (config-SharedGtTranslator=1)>primaryGtDestination="SharedGtDestination=1"

9. Set sane values for SharedGtTranslator attributes. Example:

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

   (config-SharedGtTranslator=1)>numberSeries=*

10. Commit the changes:

    >commit

2.4   Configure Routing on Local Destination on the same Node

1. Define a Destination MO of LocalSap MOC: choose previously created one (see: Section 2.1) or create new one.
2. Perform steps from Section 2.2 with Destination MO defined on previous step.

2.5   Configure Routing on another Local Node

1. Define a Destination MO of LocalSignalingPoint MOC: choose previously created one (see: Section 2.1) or create new one.
2. Perform steps from Section 2.2 with Destination MO defined on previous step.

2.6   Configure Routing on Remote Destination by SPC and SSN

2.6.1   Configure Routing on Remote Destination for current Local Node only

1. Define a Destination MO of RemoteSap MOC: choose previously created one (see: Section 2.1) or create new one.
2. Perform steps from Section 2.2 with Destination MO defined on previous step.

2.6.2   Configure Routing on Remote Destination for every Local Node in current Network

1. Define a Destination MO of SharedRemoteSap MOC: choose previously created one (see: Section 2.1) or create new one.
2. Perform steps from Section 2.3 with Destination MO defined on previous step.

2.7   Configure Routing on Remote Destination by SPC only

1. Define a Destination MO of RemoteSignalingPoint MOC to configure routing on: choose previously created one (see: Section 2.1) or create new one.
2. Perform steps from Section 2.2 with Destination MO defined on previous step.

2.8   Configure Routing between Networks

1. Define a Destination MO of LocalSignalingPoint MOC from another network (SignalingNetwork) to configure routing on: choose previously created one (see: Section 2.1) or create new one. Example:

   ManagedElement=1,Ss7=1,SignalingNetwork=5,LocalSignalingPoint=2

   The LocalSignalingPoint=2 belongs to SignalingNetwork=5. An MO for GtDestination MOC belongs to SignalingNetwork=1.

2. Perform steps from Section 2.2 with Destination MO defined on previous step.