Contents

1   Description

This instruction describes how to configure additional Application Servers (AS MOs) in existing basic M3-IETF IP Server Process - IP Server Process (IPSP-IPSP) configuration using the Ericsson Command-Line Interface (ECLI).

2   Procedure

2.1   Add ASes in M3UA IPSP - IPSP 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 IPSP - IPSP Configuration is configured.

Steps

1. Create Remote ASand Local ASMOs.

   Note:  

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

   
   
2. Create Local AS
3. Link Existing IPSP objects with New AS objects, see Section 2.3.

2.2   Create Remote 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 RemoteAs MO, for example:

   (config-M3ua=1)>RemoteAs=40002

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

   (config-RemoteAs=40002)>asProfile="ManagedElement=1,Ss7=1,M3ua=1,AsProfile=1"

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

   (config-RemoteAs=40002)>routingContext=1

2.3   Create Local AS

Steps

1. Navigate to the M3ua MO, for example:

   (config-RemoteAs=40002)>ManagedElement=1,Ss7=1,M3ua=1

2. Create the LocalAs MO, for example:

   (config-M3ua=1)>LocalAs=2

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

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

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

   (config-LocalAs=2)>networkAppearance=0

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

   (config-LocalAs=2)>remoteAs="ManagedElement=1,Ss7=1,M3ua=1,RemoteAs=40002"

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, for 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, for example:

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

11. If several LocalAs MOs are served by one LocalIpsp, 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-RkGrouping=1)>ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2

    2. Create the RoutingContext MO:

       (config-LocalAs=2)>RoutingContext=1

12. Commit the changes:

    (config-RoutingContext=1)>commit

2.4   Link Existing IPSP objects with New AS objects

Steps

1. Navigate to the LocaIpsp MO, for example:

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

2. Enter Config mode:

   (LocalIpsp=1)>configure

3. Link LocalIpsp with several LocalAs MOs. Examples:

   (config-LocalIpsp=1)>localAs=["ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1","ManagedElement=1,Ss7=1,M3ua=1,LocalAs=2"]

4. Navigate to the RemoteIpsp MO, for example:

   (config-LocalIpsp=1)>ManagedElement=1,Ss7=1,M3ua=1,LocalIpsp=1,RemoteIpsp=1

5. Link RemoteIpsp with several RemoteAs MOs. Examples:

   (config-RemoteIpsp=1)>remoteAs=["ManagedElement=1,Ss7=1,M3ua=1,RemoteAs=40001","ManagedElement=1,Ss7=1,M3ua=1,RemoteAs=40002"]

6. If RemoteIpsp is used by more than one RemoteAs, then RemoteIpsp.routingContexts must include references to RoutingContexts, which identify LocalAs MOs which are served by connected LocalIpsp:

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

7. Commit the changes:

   (config-RemoteIpsp=1)>commit

   Note:  

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