Asset ID: |
1-72-2249257.1 |
Update Date: | 2017-05-19 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2249257.1
:
Eagle Discards MSUs Containing a Network Appearance (NA) Value
Related Items |
- Oracle Communications EAGLE (Software)
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
|
In this Document
Created from <SR 3-14431622111>
Applies to:
Oracle Communications EAGLE (Software) - Version EAGLE 40.x and later
Information in this document applies to any platform.
Symptoms
The customer wants to create SIGTRAN links toward an international operator. This operator is sending MSUs with a specific NA value.
Question : How to use and set the NA parameter?
The customer has entered for example ent-na:type=itui:na=4 and if they want to enter ent-na:type=itui:na=5 STP doesn't allow to add this second one.
If they don't enter NA value for the international type, yet Eagle is discarding the MSUs. For which reason ?
Cause
It is normal Eagle is rejecting this additional entry
A valid NA is used to determine the proper MSU type and format for M3UA-to-SS7 conversion.
A unique network appearance value can be associated with ANSI, ITUI, 14-bit ITU-N, 24-bit ITU-N, ITUI spare, ITUN spare networks.
If the ITUDUPPC feature is turned on, and a value of ITUN or ITUNS is specified for the type, then the gc parameter (group code) must be specified.
Moreover, as soon as a NA parameter is defined for one type of traffic, Eagle will also make a lookup for the other received type of traffic. Meaning, that it will not ignore the incoming NA value if it is not empty in the incoming MSU.
Solution
Eagle will not ignore the NA value of the incoming MSU because of the presence of the other values in the NA table.
Even if the other NA values have been defined in the NA table for the ITU-N traffic only, when Eagle receives an MSU for ITU-I it will trigger the checking of the NA parameter because the Eagle NA table has values configured in it.
There are actually 2 options:
1. NA table completely empty (see below output), Eagle will ignore the NA value eventually present in the incoming MSUs
> rtrv-na
eaglestp 16-10-04 14:20:27 MST EAGLE 46.3.0.0.1-68.27.0
TYPE GC NA
Network Appearance ( 0 of 46) 0%
2. NA table with entries (like in the below example), Eagle will search for a match of the NA value in the incoming MSU with what is configured in its NA table.
In this case we must have all MSUs of a same type of traffic (Ansi, ITU-N, ITU-I, ...) having the exact same NA value as configured in the NA Eagle table for the type of traffic.
If one of the types of traffic does not have any NA configured in the NA table, then all incoming MSUs for this type of traffic which have a NA value will be discarded with the UIM 1333.
> rtrv-na
eaglestp 17-03-14 13:00:00 EST EAGLE5 46.2.0-67.10.0
TYPE GC NA
ITUN ab 3
Network Appearance ( 1 of 46) 2%
Example of UIM 1333 :
eaglestp 16-10-21 01:01:09 EST EAGLE5 46.0.3-65.26.29
7737.1333 CARD 3207,A6 INFO UA RCVD MSG DISCARDED
IP CONNECTION NAME=ch3207msssf16 ADPTR=M3UA
REASON=Invalid Network Appearance (Error Code=0x15)
DIAGNOSTIC=DATA Network Type Mismatch
Report Date:16-10-21 Time:01:01:09
Attachments
This solution has no attachment