1 Description
This instruction describes how to create and configure basic M3UA IP Server Process - IP Server Process (IPSP - IPSP) configuration using the Ericsson Command-Line Interface (ECLI).
2 Procedure
2.1 Configure Basic 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.
- A Managed Object (MO) SctpProfile exists.
- A Managed Object (MO) LocalSignalingPoint exists.
- A Managed Object (MO) RemoteSignalingPoint exists.
- A Managed Object (MO) LocalSctpEndpoint exists.
- A Managed Object (MO) RemoteSpProfile exists.
- A Managed Object (MO) AsProfile exists.
Steps
There is recommended order of creating objects of basic IPSP-IPSP configuration:
- Create Remote Application Server, see Section 2.2.
- Create Local Application Server, see Section 2.3.
- Create Local IP Server Process, see Section 2.4.
- Create Remote IP Server Process, see Section 2.5.
2.2 Create Remote Application Server
Steps
- Navigate to the M3ua MO, for example:
>ManagedElement=1,Ss7=1,M3ua=1
- Enter Config mode:
(M3ua=1)>configure
- Create the RemoteAs MO, for example:
(config-M3ua=1)>RemoteAs=40001
- To see all attributes with values, run show command, for
example:
(config-RemoteAs=40001)>show -v
The following is an example output:
RemoteAs=40001 asProfile=[] remoteAsId=40001 reservedBy=[] routingContext=[]
- Set the value of the asProfile attribute, for example:
(config-RemoteAs=40001)>asProfile="ManagedElement=1,Ss7=1,M3ua=1,AsProfile=1"
- Set the value of the routingContext attribute, for example:
(config-RemoteAs=40001)>routingContext=1
2.3 Create Local Application Server
Steps
- Navigate to the M3ua MO, for example:
(config-RemoteAs=40001)>ManagedElement=1,Ss7=1,M3ua=1
- Create the LocalAs MO, for example:
(config-M3ua=1)>LocalAs=1
- To see all attributes with values, run show command, for
example:
(config-LocalAs=1)>show -v
The following is an example output:
LocalAs=1 asProfile=[] localAsId=1 localSpc=[] networkAppearance=[] remoteAs=[] reservedBy=[]
- Set the value of the localSpc attribute, for example:
(config-LocalAs=1)>localSpc="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=1"
- Set the value of the networkAppearance attribute, for
example:
(config-LocalAs=1)>networkAppearance=0
- Set the value of the remoteAs attribute, for example:
(config-LocalAs=1)>remoteAs="ManagedElement=1,Ss7=1,M3ua=1,RemoteAs=40001"
- Set the value of the asProfile attribute, for example:
(config-LocalAs=1)>asProfile="ManagedElement=1,Ss7=1,M3ua=1,AsProfile=1"
- Create the RkGrouping MO, for example:
(config-LocalAs=1)>RkGrouping=1
- To see all attributes with values, run show command, for
example:
(config-RkGrouping=1)>show -v
The following is an example output:
RkGrouping=1 dpc=[] localSpc=-1 rkGroupingId=1 si=[]
- Set the value of the si attribute. Examples:
- (config-RkGrouping=1)>si=3
- To set several values they are to be included in square
brackets and separated by comma, for example:
(config-RkGrouping=1)> si=[3,4]
- If si attribute is empty, it means all SIs are applicable.
To delete all configured SIs and make all SIs applicable, please use:
(config-RkGrouping=1)>no si
- Set the value of the localSpc attribute, for example:
(config-RkGrouping=1)>localSpc=100
- Set the value of the dpc attribute. Examples:
- (config-RkGrouping=1)>dpc=["ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=1"]
- To set several DPCs they are to be included in square
brackets and separated by comma, for example:
(config-RkGrouping=1)> dpc=["ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=1","ManagedElement=1,Ss7=1,SignalingNetwork=1,RemoteSignalingPoint=2"]
- If dpc attribute is empty, it means all DPCs are applicable.
To delete all configured DPCs and make all DPCs applicable, please
use:
(config-RkGrouping=1)>no dpc
- Create the RoutingContext MO, for example:
- Navigate to the LocalAs MO, for example:
(config-RkGrouping=1)>ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1
- Create the RoutingContext MO:
(config-LocalAs=1)>RoutingContext=1
- Note:
- Step is optional. RoutingContext may be not created if a LocalIpsp serves only one LocalAs MO.
- Navigate to the LocalAs MO, for example:
2.4 Create Local IP Server Process
Steps
- Navigate to the M3ua MO, for example:
(config-RoutingContext=1)>ManagedElement=1,Ss7=1,M3ua=1
- Create the LocalIpsp MO, for example:
(config-M3ua=1)>LocalIpsp=1
- To see all attributes with values, run show command, for
example:
(config-LocalIpsp=1)>show -v
The following is an example output:
LocalIpsp=1 localAs=[] localIpspId=1 sctpEndpoint=[]
- Set the value of the sctpEndpoint attribute, for example:
(config-LocalIpsp=1)>sctpEndpoint="ManagedElement=1,Ss7=1,M3ua=1,LocalSctpEndpoint=1"
- Set the value of the localAs attribute. Examples:
(config-LocalIpsp=1)>localAs=["ManagedElement=1,Ss7=1,M3ua=1,LocalAs=1"]
2.5 Create Remote IP Server Process
Steps
- Navigate to the LocalIpsp MO, for example:
(config-LocalIpsp=1)>ManagedElement=1,Ss7=1,M3ua=1,LocalIpsp=1
- Create the RemoteIpsp MO, for example:
(config-LocalIpsp=1)>RemoteIpsp=1
- To see all attributes with values, run show command, for
example:
(config-RemoteIpsp=1)>show -v
The following is an example output:
RemoteIpsp=1 aspIdentifier=0 aspIdentifierHandling=NO_ASP_ID exchangeMode=SINGLE_EXCHANGE_MODE localCongestionLevel=3 messageDiscardLevelShift=0 networkAppearanceHandling=OFF primaryLocalIpAddress=[] primaryRemoteIpAddress=[] remoteAddresses=[] remoteAs=[] remoteAspId=0 remoteIpspId=1 remotePortNumber=2905 remoteSctpProfile=[] remoteSpPriority=1 remoteSpProfile=[] routingContextHandling=RFC_4666_COMPLIANT routingContexts=[] sctpType=CLIENT_PEER spInStartAll=INCLUDE_IN_START_ALL
- Set the value of the remoteAddresses attribute. Examples:
- (config-RemoteIpsp=1)>remoteAddresses=1.1.1.1
- To create several addresses they are to be included
in square brackets and separated by comma, for example:
(config-RemoteIpsp=1)>remoteAddresses=[1.1.1.1,1.1.1.2]
- Set the value of the remotePortNumber attribute, for example:
(config-RemoteIpsp=1)>remotePortNumber=2906
- Set the value of the remoteAs attribute. Examples:
(config-RemoteIpsp=1)>remoteAs=["ManagedElement=1,Ss7=1,M3ua=1,RemoteAs=40001"]
- Set the value of the remoteSctpProfile attribute, for
example:
(config-RemoteIpsp=1)>remoteSctpProfile="ManagedElement=1,Transport=1,Sctp=1,SctpProfile=1"
- Set the value of the remoteSpProfile attribute, for example:
(config-RemoteIpsp=1)>remoteSpProfile="ManagedElement=1,Ss7=1,M3ua=1,RemoteSpProfile=1"
- Commit the changes:
(config-RemoteIpsp=1)>commit
- Note:
- After successful "commit" all recently added MOs (RemoteAs, LocalAs, LocalIpsp, RemoteIpsp) are activated automatically. No additional actions are needed.
Glossary
| AS |
| Application Server |
| ASP |
| Application Server Process |
| DPC |
| Destination Point Code |
| ECLI |
| Ericsson Command-Line Interface |
| IPSP |
| IP Server Process |
| MO |
| Managed Object |
| M3-IETF |
| SS7 MTPL3 & M3UA-IETF |
| RK |
| Routing Key |
| SGP |
| Signaling Gateway Process |
| SI |
| Service Indicator |
| SPC |
| Signalling Point Code |

Contents