Contents

1   Description

This instruction describes how to configure additional Local Application Server (AS) in existing basic M3-IETF Application Server Process (ASP) - Signaling Gateway Process (SGP) configuration using the Ericsson Command-Line Interface (ECLI).

2   Procedure

2.1   Add Local AS in M3UA ASP-SGP Configuration

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
  • Basic ASP - SGP Configuration is configured.

Steps

1. Create Local AS.

   Note:  

   It is possible to use existing LocalAs MO. In this case current step should be skipped.

   
   
2. Link Existing ASP with New Local AS, see Section 2.3.

2.2   Create Local AS

Steps

1. Navigate to the M3ua MO, for example:

   >ManagedElement=1,Ss7=1,M3ua=1

2. Enter Config mode:

   (M3ua=1)>configure

3. Create the LocalAs MO, for example:

   (config-M3ua=1)>LocalAs=2

4. Set the value of the localSpc attribute, for example:

   (config-LocalAs=2)>localSpc="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1"

5. Set the value of the networkAppearance attribute, for example:

   (config-LocalAs=2)>networkAppearance=0

6. Set the value of the asProfile attribute, for example:

   (config-LocalAs=2)>asProfile="ManagedElement=1,Ss7=1,M3ua=1,AsProfile=1"

7. Create the RkGrouping MO, for example:

   (config-LocalAs=2)>RkGrouping=1

8. Set the value of the si attribute. Example:

   (config-RkGrouping=1)> si=[3,4]

9. Set the value of the localSpc attribute, for example:

   (config-RkGrouping=1)>localSpc=100

10. Set the value of the dpc attribute. Examples:

    (config-RkGrouping=1)>dpc=["ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=1"]

11. If several LocalAs MOs are served by one LocalAsp, then RoutingContexts must be configured for each of these LocalAs MOs. It means, that RoutingContext MO should be created for each LocalAs.
    1. Navigate to the LocalAs MO, for example:

       (config)>ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2

    2. Create the RoutingContext MO, for example:

       (config-LocalAs=2)>RoutingContext=1

12. Commit the changes:

    (config-RoutingContext=1)>commit

2.3   Link Existing ASP with New Local AS

Steps

1. Navigate to the LocaAsp MO, for example:

   >ManagedElement=1,Ss7=1,M3ua=1,LocalAsp=1

2. Enter Config mode:

   (LocalAsp=1)>configure

3. Link LocalAsp with several LocalAs MOs. Examples:
   • (config-LocalAsp=1)>localAs=["ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1","ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2"]
   • When square brackets are not used, specified LocalAs is added to current list of linked LocalAs MOs. So, if LocalAsp is already served LocalAs=1, following command will be equivalent with previous:

     (config-LocalAsp=1)>localAs="ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2"

4. If RemoteSgp connected with more than one LocalAs MOs referred by the appropriate LocalAsp. then RemoteSgp.routingContexts must include references to RoutingContexts, which identify LocalAs MOs which are served by connected LocalAsp:

   (config-RemoteSgp=1)>routingContexts=["ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1,RoutingContext=1","ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2,RoutingContext=2"]

5. Commit the changes:

   (config-RemoteSgp=1)>commit

   Note:  

   After successful "commit" all changed MOs are activated automatically. No additional actions are needed.