Fault detection in split architecture

• MGw selection
• Detecting fault situations
• Finding messages sent/received on some protocols
 Axe parameters for MGw selection

dbtsp:tab=axepars,setname=OMSRF,name=MGS;
( 0 MA-node, 1 ATM/TDM mgs on, 2 IP mgs on)

dbtsp:tab=axepars,setname=GSMMSCF,name=COMBINODE;
( 0 Combinode off, 1 Combinode on)

dbtsp:tab=axepars,setname=GSM1APTC,name=MTCGSMPERCENT;
dbtsp:tab=axepars,setname=GSM1APTC,name=MTCUMTSPERCENT;
dbtsp:tab=axepars,setname=GSMMSSC,name=MOCGSMPERCENT;
dbtsp:tab=axepars,setname=GSMMSSC,name=MOCUMTSPERCENT;
( Indicates in percentage how many of calls should use remote MGw)
 Detecting fault situations

•Event reporting

•GCP decoder

•Protocol disturbances

•Call Flows

•Syrip events

•Forlop hangings

•Alarms
 Event reporting

• An easy way to see if something is not OK on the GCP I/f

•Exist of a number of “event numbers”

Each event number has a special meaning

•For GCP the numbers can be found in AI for GCPH.

1009 MGW DETECTED ERROR
1010 GCP PROTOCOL ERROR
1011 GCP TRANREPLY NOT RECEIVED
1012 GCP RESOURCE LIMITATION
 Event reporting

To define and activate it.

SAAII:SAE=500,BLOCK=EVREP,NI=1100;
ERESC:ENUM=1009,EMAX=40,LTYPE=WRAP;
ERESC:ENUM=1010,EMAX=40,LTYPE=WRAP;
ERESC:ENUM=1011,EMAX=40,LTYPE=WRAP;
ERESC:ENUM=1012,EMAX=40,LTYPE=WRAP;
EREPI:ENUM=ALL;

To print the report.

EREPP:ENUM=ALL;

To clear the report.

EREPE:ENUM=ALL;
EREPI:ENUM=ALL;
 Event reporting
EVENT REPORTING RESULT

ENUM HEADER BLOCK DATE TIME

1009 MGW DETECTED ERROR
NONE

ENUM HEADER BLOCK DATE TIME

1010 GCP PROTOCOL ERROR GCPH 030130 114515800

REMADDR STT DIR ERRCODE

2-2310 0 REC 430

ENUM HEADER BLOCK DATE TIME

1011 GCP TRANREPLY NOT RECEIVED
NONE

ENUM HEADER BLOCK DATE TIME

1012 GCP RESOURCE LIMITATION
NONE
END
 Event reporting

Where to find the definition of the error codes ?

• Error code 1 - 6, in the AI for GCPH
(2/155 18-CNT 301 0003)

• Error code 400 - 581, in the GCP Protocol Spec

(1/155 19-FAY 112 32/2, Annex L)

• Other values doesn’t exist (yet) for GCP

 Event reporting
Common error codes received
• 431, No TerminationID matched a wildcard ==> MSC send a request for a
terminationd ID that doesn’t exist in the MGw.
-Received after large restart in MSC if no calls ongoing in the SNT or
no idle devices in SNT.
(That is how the restart is implemented)

-If received in other cases then it’s a fault

• 500, Internal software failure in the MGw ==> similar to applerror in MSC.
Trace in MGw to find the fault.
 Event reporting
Common error codes received
• 510, Insufficient resources ==> Lack of HW-Resources in MGw
- Check the HW resources (related to your call case) in MGw
* If HW enabled then a fault => trace in resource access of MGw.
* If HW disabled then make them available.
- Congestion on AAL2 (STA2P)

514, Media Gateway cannot send the specified announcement.

- Announcement is not defined in MGw (most likely).
- Announcement is locked in MGw
- Announcement is disabled in MGw
- Or it is simply a fault in MGw
 Event reporting
Common error codes received
• 430, Unknown TerminationID
Most of time this is due to R-TDM SNT’s defined in MSC but not in MGW.
(Or SNT’s defined in MGw but not in MSC (at M-MGw restart))
- If that’s the case then Remove the SNT’s in MSC or ignore.
- If that’s NOT the case then there is a fault and has to be investigated.
 GCP decoder

Trace on block GCPH and use the tool GCP decoder

to decode the tracing.
(DOS version, only for UCN 2.0,
Unix version for UCN2.0 and UCN3.0)

• Define the tracing and store the trace in a file

TEST SYSTEM;
ON IN GCPH;
ON OU GCPH RP;
OFF IN GCPH H'1 H'2 H'3C; ! GCPH CAAZ 107 8616 R1A05!
TMSIZE 32000;
INIT;

• Use the trace file as input for the decoder

gcpdtool [-r <2.0|3.0>] [-o <filename>] <inputfile>
 GCP decoder
Part from the input file
ON OUTSIG
GCPH IA H'652C
GCPH RPSIG ON THL TO RP 182 CM=0 INTADDRESS=H'00
SIGNO=H'10 WITH
H'FF, H'FF, H'00, H'18, H'56, H'00,
H'00, H'23, H'F6, H'19, H'1F, H'00,
H'18, H'00, H'07, H'FF, H'FF, H'FF,
H'FE, H'04, H'02, H'00, H'00, H'0F,
H'FF, H'FF, H'FF, H'0F, H'FF, H'FF,
H'FF, H'0F, H'FF, H'FF, H'FF, H'00,
H'00, H'03, H'00, H'00, H'00, H'0F,
H'FF, H'FF, H'FF, H'0F, H'FF, H'00

GCPH IA H'3B29
GCPH RPSIG ON THL TO RP 182 CM=0 INTADDRESS=H'00
SIGNO=H'11 WITH
H'01, H'8F, H'57, H'FF, H'FF, H'0F,
H'FF, H'FF, H'FF, H'0F, H'FF, H'FF,
H'FF, H'00, H'00, H'00, H'00, H'00,
H'59, H'28, H'00, H'00, H'00, H'00,
H'00, H'00, H'02, H'00, H'00, H'00,
H'0B, H'00, H'00, H'00, H'01, H'00,
H'11, H'00, H'01, H'24
 Output from the decoder ... Part from the output file
value MegacoMessage ::=
{
Sending node descriptors
mess {
version 2, {
mId mtpAddress : '000023F6'H, mediaDescriptor :
messageBody transactions : { {
transactionRequest : { streams oneStream :
transactionId 4070834196, {
actions { localControlDescriptor
{ {
contextId 4294967294, streamMode sendRecv,
commandRequests { propertyParms
{ {
command addReq : { {
terminationID { name '001E0001'H,
{ value
wildcard { {
Termination ID '0A0105'H
},
id '4800B015'H }
}
}, (Bearer Characteristic = TDM)
Look into GCPHSE spec to find the meaning.
15519-FAY 201 709/1
 Decoding of Termination id
Termination ID = H'4800 B015
Bits 29 - 31 = 010 For TDM access
Bits 26 - 28 = TDM transport (010 for 2 Mbit/s)
Bits 5 - 25 = PCM system number
Bits 0 - 4 = Individual

Match with SNT in MSC and

H'4800 B015 = 010 0 10 00 0000 0000 1011 0000 000 1 0101 Termination groups in MGw

TDM Individual 21
2 Mbit/s PCM system number 1408

NTCOP:snt=all; 
SNT SNTV DEV EXTP MG
:
RTDMA-29 0 MRALT-160&&-191 2-2-1408 CMGW3
:
END
 Decoding of mtp adress in message

mId mtpAddress = xxxx..xxxxx|yy where yy= NI and x = PointCode

example: 000023F6 = 100011111101 10 ==> PC= 100011111101 = 2301

Ni= 10 =2
PC NI

mId mtpAddress : '000023F6'H = 2-2301

mId mtpAddress : '0000241A'H = 2-2310
mId mtpAddress : '000028A6'H = 2-2601
mId mtpAddress : '000028CA'H = 2-2610
 GCP decoder

Where to find the decoder ?

CN3.0 version :
http://eed.ericsson.se/CNIC/eed-s-n/s-np/proj/gcpdtool/index.html
 Protocol Disturbance
•The disturbance recording function provides the ability to record
protocol disturbances on routes.

•Routes of interest:
BICC routes (incoming and outgoing)
PODRI:R=BIA600O,DTYPE=ALL;
PODRI:R=BIA600I,DTYPE=ALL;

•To get the recorded result

PODRE:R= BIA600I;
 Protocol Disturbance
podre:r=A2310I;
PROTOCOL DISTURBANCE RECORDING RESULT
R DATE TIME TDH TDM DTYPE DNUM ADDINFO
2310I 030314 1044 CONT 1 4 H'7
3 1 H'7 H'2
3 1 H'7 H'2
1 4 H'7
3 1 H'7 H'2

END Call phase complete : Active

Message type 7 = Release Request

 Protocol Disturbance

Which documents to use to find what printout says ?

•BICC
AI (2/155 18-CNT 212 2687) for BID gives info on meaning of
DTYPE, DNUM and ADDINFO on BICC routes.
FS (2/155 17-FAY 112 003/2) for BICC protocol to find the
coding of BICC Message type.
 Call flows
•Specifies the order of GCP messages sent between MSC and M-MGw for different
scenarios

•Specifies what the GCP messages should contain

s.ericsson.se/SystemManagement/Projects/SMProjectCN40/SystemL1/ call_flows_index_new.htm#CN%203.0%20call%2
•Syrip events
- SYRIP:SURVEY;

•Hanging forlopps
- SYFAP;

•Alarms
-ALLIP;
Finding messages sent/received on some protocols

•RANAP

•DTAP/NAS

•ISUP

•BICC
 Iu Interface - RANAP message
To find out which RANAP messages sent and received,
trace in/out of MUAMCO, the info is in the signal
RCVRANAPCO sent from MUAMH (for messages sent to the MSC)
SENDRANAPCO sent to MUAMH (for messages sent from the MSC)

ON IN MUAMCO RCVRANAPCO;
ON OUT MUAMCO SENDRANAPCO;

for RCVRANAPCO for SENDRANAPCO

D6: MESSAGE TYPE D5 MESSAGE TYPE

0-64 = RESERVED 0-63 = SPARE

65 = RAB ASSIGNMENT RESPONSE 64 = RAB ASSIGNMENT REQUEST
66 = RAB RELEASE REQUEST 65 = SPARE
67 = IU RELEASE REQUEST 66 = SPARE
68 = RESERVED 67 = SPARE
: :
 DTAP (A-i/f) / NAS (Iu-i/f) message
To find out which DTAP/NAS messages sent and received,
trace in/out of MCCMH, the info is in the signal
RECEIVERNMSG1 sent from MCCMH (for messages sent to the MSC)
SENDRNMSG1 sent to MCCMH (for messages sent from the MSC)

Depending on side of call it's either MTACC or MTBCC that communicates

with MCCMH.

ON IN MCCMH SENDRNMSG1;
ON OUT MCCMH RECEIVERNMSG1;
for RECEIVERNMSG1 and SENDRNMSG1
D3 : 0 = UNKNOWN
1 = SETUP
2 = EMERGENCY SETUP
3 = CALL CONFIRMED
4 = CALL PROCEEDING
:
 ISUP
To find out which ISUP messages sent received, use the function
ISUP MESSAGE MONITOR
•Block all devices except 16 on the ISUP link
(limitations in this feature to 16 devices per user)
BLODI:DEV=UPD-161&&-174;
•Order the monitoring of devices on the link
UPMTI:DEV=UPD-175&&-189&-191;
•Printout is generated automatically at traffic
 ISUP
Example of printout:
ISUP MESSAGE MONITOR RESULT

USER SI CIC SP DEV CALLREF

AT-7 ISUP4 27 2-350 UPD-187

TIME MSG DIR DATA

10:52:03:3 IAM S 85 5E 01 4B 20 1B 00 01 00 60
01 0A 00 02 08 06 83 90 17 09
00 02 0A 07 03 17 71 12 13 09
38 08 01 00 1D 03 80 90 A3 31
02 00 5A 3A 06 43 04 90 00 00
FF 3F 06 00 1F 94 71 32 20 39
06 31 D0 3A D0 3F D0 00

TIME MSG DIR DATA

10:52:03:4 ACM R 85 2C 81 57 20 1B 00 06 06 01
00
 BICC
To find out which BICC messages sent received, use the function

Bearer Independent Call Control, Monitoring

•Switch on the BICC monitoring feature
TAB=AXEPARS,SETNAME=TSSF,NAME=BICCMON,VALUE=1
•Increase sae 701 in block BIMON
SAAII:sae=701,block=BIMON,ni=100;
• Block all devices except 16 on the BICC link
(limitations in this feature to 16 devices per user)
BLODI:DEV=BID-144&&-159;
•Order the monitoring of devices on the link
BIMTI:DEV=BID-128&&-143;
•Printout is generated automatically at traffic
 BICC
Example of printout:
BICC MESSAGE MONITOR RESULT

USER BCIC DEV ROUTE TSTCALL

AT-3 1 BID-129 BIA300O NO

TIME MSG DIR DATA

16:22:45:0 IAM R 01 00 00 00 01 08 60 01 0A 00
02 0A 08 04 10 94 71 62 80 79
84 0A 07 03 17 71 12 13 09 42
08 01 00 31 02 00 5A 3A 06 43
04 90 00 00 FF 1D 03 80 90 A3
78 28 85 81 C0 00 00 01 82 83
01 02 85 83 00 00 1F 43 03 8A
83 45 49 15 20 00 30 03 00 0F
07 82 83 02 0A 86 83 00 06 09
00 00 39 06 78 83 31 D0 3A D0
00