Troubleshooting Tools DX200

Troubleshooting
Tools in DX200
Platform
Nokia Siemens Networks
CN34042EN33GLN0
Objective
After this module, the student should know:
The SCN troubleshooting tools available in the DX200 platform
How to use QA Logging macro for first phase data collection
CN34042EN33GLN0
Maintenance System
SUPERVISION
SYSTEM
ALARM
SYSTEM
RECOVERY
SYSTEM
FAULT
LOCATING
SYSTEM
REPORT TO THE USER
CN34042EN33GLN0
Alarm system user interface

ZA ... ALARM SYSTEM ADMINISTRATION
ZAB
ZAC
ZAE
ZAH
ZAL
ZAO
ZAP
ZAR
ZAT
BLOCKED ALARMS HANDLING

ALARM CANCELLING
ERROR RATIO COUNTER HANDLING
ALARM HISTORY HANDLING
LAMP PANEL HANDLING
ALARM OPERATING INSTRUCTION HANDLING
ALARM PARAMETERS HANDLING
ALARM SYSTEM RULEBASE HANDLING
ALARM PRINTING HANDLING
CN34042EN33GLN0
Five Alarm Classes

Notices
*
Disturbances
Notices and Disturbances are additional information about the
situation in the exchange. Notices and disturbances do not require
actions from the user.
*
One star alarms
Should be fixed during normal maintenance hours.
**
Two star alarms
Should be fixed as soon as possible.
*** Three star alarms
Indicate a serious situation and require immediate action.
CN34042EN33GLN0
Alarms at One Instance of Time
A
l
a
r
m
A
l
a
r
m
A
l
a
r
m
A
l
a
r
m
A
l
a
r
m
AHP
5 Alarms
AHO
No alarm
CN34042EN33GLN0
Alarm printout examples
MSS01
**
ALARM
BSU-0
BSU-0
1B001-02
SWITCH
2004-08-06
15:37:51.71
IC2_SS
(0039) 2186 CALL CONTROL ANALYSIS MISSING

02 0002 00 07 04 59 19 D0 00 00 00 00 00 00 00
MSS01
**
ALARM
BSU-0
BSU-0
1B001-02
SWITCH
2004-08-06
15:38:45.22
IC2_SS
(0040) 2186 CALL CONTROL ANALYSIS MISSING

02 0002 00 07 04 51 98 D0 00 00 00 00 00 00 00
**
ALARM
MSS01
BSU-0
BSU
AIF_SS
(0055) 3200 UNKNOWN RNC

222 03 0002
CN34042EN33GLN0
SWITCH
2004-08-09
11:41:13.07
Alarm Print-Out
ALARM OBJECT
SOURCE COMPUTER
SOURCE SYSTEM
OBJECT COORDINATES
PRINT OUT TYPE
ALARM TYPE
DATE
MSS01
**
ALARM
(0033)
SIGU-0
SIGU-0
2186
1B001-00
SWITCH
2004-08-11
TIME
11:08:45.42
IC9_SX
CALL CONTROL ANALYSIS MISSING
RECOVERY ACTION
03 0002 00 08 00 00 07 0E 00 00 00 00
ALARM NAME
SUPPLEMENTARY INFORMATION FIELD
ALARM NUMBER
SOURCE PROCESS
CONSECUTIVE NUMBER
ALARM CLASS
CN34042EN33GLN0
Diagnostic MML
ZUD ... DIAGNOSTICS HANDLING
ZUDU START UNIT TEST/PARTIAL UNIT TEST

ZUDD START I/O DEVICE TEST
ZUDI INTERROGATE PARTIAL UNIT TESTS
ZUDL LIST FAULTY UNITS/PROCESSOR UNITS
ZUDQ INTERROGATE CURRENT TESTS
ZUDS STOP CURRENT TEST
CN34042EN33GLN0
Diagnostic Printout Example
MSCi
16:51:28
MSS01
2004-09-09
DIAGNOSTIC REPORT
CLAB-4
1B001-06
PARTIAL DIAGNOSIS
CLAB
DIAGNOSTIC PROGRAM
005F
DIAGNOSIS
3998
3998 DIAGNOSIS EXECUTED - UNIT NOT OK
10
CN34042EN33GLN0
Why Logical File?
DATA
Read / write
Logical
Logicalfile
file
Read
Read
Logical files buffer data between a network element and the end-user.
This is a good way to connect multiple users with only one source.
ALL I/O devices are hidden from the application. Therefore, it does not matter
whether they are available or out of line.
11
CN34042EN33GLN0
Logical files used in troubleshooting

DIAGNOS
An output logical file for all hardware diagnostic programs.
Receives detailed data from the ongoing test and the results
GSMME1PR
A GSM specific report file
All currently active subscriber trace information is available
via this logical file
OBSFAILA
Collects failed call information from call control software
when observation is active
12
CN34042EN33GLN0
Output Clear Codes reporting

ZTUT:CLR;
LOADING PROGRAM VERSION 14.17-0
SIGNALLING RING
0
0
1
3
2
0
22
7
0
0
1
0
89
0
51
143
1
0
4
0
3
0
491
0
2
1
END OF REPORT
13
CN34042EN33GLN0
SPEECH
235
1
0
1
1
0
0
0
0
0
0
0
1
CLEAR CODE
000H NORMAL END OF THE CALL
005H B-SUBSCRIBER BUSY
00DH CALL TERMINATED BY OPER
015H NORMAL UNSPECIFIED
024H MAX DUR OF CALL EXCEEDED
304H B-LINE OUT OF SERVICE
30AH A ONHOOK DURING SET UP
30BH A ONHOOK DUR_WAIT ANSWER
603H NO RESPONSE FROM CO-PROC
706H CALL INTER REG ANALYSIS
80FH CIRCUIT CONGESTION
812H MAP FAILURE
B13H RADIO IF FAILURE
Clear Code groups

Clear codes has been divided into four main classes:
000H - 3FFH:
400H - 7FFH:
800H - BFFH:
C00H - FFFH:
normal clearing
internal congestion
external congestion
subscriber errors
The first main class 'normal clearing' (000H 3FFH) consists of clear codes which have not been caused by an error in
the exchange or by subscriber error, but which nevertheless leads to clearing of a call or to an interruption in call setup.
The second main class, 'internal congestion' (400H - 7FFH) consists of cases in which a call or call set-up is interrupted
because of an error in the exchange. This group contains clear codes related mainly to file management and to
communication between program blocks and different units of the exchange.
The third main class, 'external congestion' (800H -BFFH) includes all the cases in which a call or call set-up is
interrupted because of an error outside the exchange. This group consists mainly of clear codes related to interexchange signalling.
The fourth main class, 'subscriber error' (C00H - FFFH) includes the cases in which a call or call set-up is interrupted
by a subscriber's error or by a failure in the subscriber's equipment or by faulty subscriber signalling
14
CN34042EN33GLN0
Circuit Group Measurements Example
DX 200
MSC KL
2001-10-12
16:00:35
TRAFFIC MEASUREMENT REPORT

TRACGRA
CGR
SOURCE: STU-1
OUTPUT INTERVAL: 60 MIN
SAMPLE DATE: 2001-10-12
NCGR
CGR
ECMFAST
187
FAXMO
191
BSC01
310
BSC02
320
CRTS DIR
26
IN
OUT
24 IN
OUT
636 IN
OUT
427 IN
OUT
Name & Nbr. of the CGR
AVECR
TC(%)
CC
CALLS
ACCEP
26.0
26.0
22.7
22.7
635.0
635.0
426.0
426.0
0.0
0.0
0.0
0.0
0
0
0
0
36
0
108
46
10569
6883
8284
5451
21
0
58
44
9236
6550
7071
5056
16:00:00
ANSW SFAIL IFAIL EFAIL

18
0
37
37
6115
4915
5000
3913
0
0
0
0
159
0
98
2
15
0
0
0
60
2
40
4
0
0
50
2
1114
331
1075
389
ERLANGS
0.5
0.0
1.0
0.8
130.3
129.4
97.5
96.5
Circuits in CGR
per direction
avg. available
(WO-EX) circuits
CALLS : All call attempts

ACCEP: Call attempts cleared normal,
but never reached a
conversation state
ANSW: All answered calls
Time (TC) and total (CC) calls congested.

Calculation based on
time (%) where no circuit in CGR is available during period
total amount of call attempts with no circuit available
15
CN34042EN33GLN0
SFAIL: Failed by Subscriber error

IFAIL : Failed by exchange internal error
EFAIL : Failed by trunk circuit
Trace example 1/3

MSCi
MSS01
2004-09-09
17:43:02
MSC OBSERVATION REPORT FROM STU-0
REPORTING TIME
: 2004-09-09
REPORT NUMBER
: 000230
TRACED IMSI
: 222039900000020
TRACE REFERENCE
: 00001
OMC ID
TRACE TYPE
: ALL, BASIC, UNPRIOR
TRACE TYPE USED
: ALL, BASIC, UNPRIOR
START TIME
: 2004-09-09
17:42:46.99
END TIME
: 2004-09-09
17:43:02.15
RECORDING ENTITY
: 39269000080
REPORT REASON
: EVENT
INVOKING EVENT
: SUBS(A)
CALL ID
: 0179H-017AH-4004H-4131H-00DCH-00H-00DCH-00H
CALL START
: 2004-09-09
SIGNALLING COMPLETE
16
: 2004-09-09
17:42:50.98
17:43:02.61
17:42:46.99
STAT STATE
CALL PHASE
: RELEASE
: IDLE
ANSWER
: 2004-09-09
17:42:53.10
CLEAR CODE : 0000H
CHARGING END
: 2004-09-09
17:43:02.15
CLEAR INFO : AIF_SS 0001H 0B2EH
PAGING TIME
: 1870
CLEAR PART
: SUB A
EXT CLEAR CODE
: 0010H
SIGNALLING
: MS CC
CN34042EN33GLN0
Trace example 2/3
MGW TRACE
: OK
EXTERNAL FORWARDING COUNTER
CALLING NUMBER
: I
392695550020
CALLED NUMBER
: N
2695550018
OUT PULSED NUMBER : I
392695550018
CONNECTED NUMBER
392695550018
: I
ROAMING NUMBER
: N
2698000163
ADDRESS NUMBER
: U
2695550018
IP TRUNK
: NOT USED IP TRUNK
OBJECT
17
: 0
SUBSCRIBER A (TRACED)
IMSI
: 222039900000020
IMEI
CN34042EN33GLN0
SUBSCRIBER B
222039900000018
Trace example 3/3

RADIO SYSTEM
: UMTS
UMTS
CGR/BSC/PCM-TSL
MCC/MNC
: 222 /03
222 /03
LAC/CI/CELL BAND
: 00932/00932/
00932/00932/
RNC ID
: 00002
00002
MGW INDEX
: 0
MGW NAME
: MGW2
MGW2
BNC CHAR
: AAL2
AAL2
UPD INDEX/NAME
: 0 /UPD0
0 /UPD0
TDM TERMID
CHANNEL RATE
: FR / HFR1 /
FR / HFR1 /
SPEECH VERSION
: FR3
FR3
PRIORITY
: 3
MS CLASSMARK
ECHO CANCELLING PARAMETERS

RECEIVED IEC / OEC
: INCLUDED / INCLUDED
SENT IEC / OEC
END OF REPORT
18
CN34042EN33GLN0
Testing number analysis
CATEGORY Test mobile created in the HLR
Test digit analysis tree with analysis
or
Test attribute analysis created
TEST ACTIVITY
YCH-MML
START TEST
YCS-MML
TEST CATEGORY 4
19
CN34042EN33GLN0
Testing number analysis

CATEGORY Test mobile created in the HLR
TE
TIME SLOT IN TEST STATE
TEST HUNTING
YC-MML
START TEST
YCS-MML
TEST CATEGORY 4
20
CN34042EN33GLN0
Loop Transmission
Typical problem
X
B3
2M
and solution
X
2M
21
CN34042EN33GLN0
MML LOG
ASWDIR
MMLLOG
MMDIRE
Active
BLCODE
LFILES
20040912.00
20040911.00
20040910.00
20040909.00
22
CN34042EN33GLN0
MML command log

ZIGO:2006-01-26,10-00,2006-01-26,10-30:USERID=SYSTEM::;
LOADING PROGRAM VERSION 4.8-0
/* MSS_880091 MSCi SYSTEM 2006-01-26 10:09:42 */
AHP::NR=:2006-01-26,09-00-00:;
/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:03:20 */
/* 4 AHP::NR=:2006-01-26,09-00-00:; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:03:20 */
USI:COMP;
/* 4 USI:COMP; */
NEL;
/* 4 NEL; */
IGO:2006-01-26,10-00,2006-01-26,10-30:USERID=SYSTEM::;
COMMAND EXECUTED
23
CN34042EN33GLN0
Service Terminal
DX200 SERVICE TERMINAL MAIN LEVEL COMMANDS:

? ..... MENU / HELP
A ..... ANALYZER
B ..... DEFINE ENVIRONMENT
C ..... COMMAND LANGUAGE UTILITIES
D ..... MEMORY AND I/O HANDLING
E ..... EXIT DEBUGGER SESSION
I .. .. GENERAL INFORMATION
L ..... EXTENSION HANDLING
O ..... OPERATING SYSTEM COMMANDS
R ..... REMOTE DEBUGGER HANDLING
S ..... SYSTEM MONITORING COMMANDS
T ..... TERMINAL HANDLING
EXTENSIONS:
G ..... COMPUTER LOG HANDLER (DEF)
U ..... RECOVERY DEBUGGER
M ..... MASS MEMORY HANDLING
INITIAL NAME: 00BE 0000 00

00-MAN>
24
CN34042EN33GLN0
CURRENT NAME: 00BE 0000 00
Traffic Flow in the MSC/MSS
HLR
CM
CM
CCSU
CCSU//
SIGU
SIGU
BSU
BSU
VLR
25
CN34042EN33GLN0
PSTN
QA Logging
First phase data collection macro
26
CN34042EN33GLN0
QA Logging Introduction
When abnormal situation occurs in customer network
Problem reported to NSN
Some obligatory information need to be collected for troubleshooting
In the first phase of troubleshooting, we required information about:

Detailed case description
SW versions
Generic configuration data from involved network elements
Based on collected information technical support engineer should be able to

determine the nature of the problem
Configuration error
SW defect
HW failure
27
CN34042EN33GLN0
QA Logging Faster troubleshooting

Provide essential information to get troubleshooting immediately
to right direction without any extra delays due to unnecessary info
requests
In later troubleshooting phase some extra SW monitoring or

configuration data might be needed, which is requested by a new
information request.
28
CN34042EN33GLN0
QA Logging Description
QA logging macro is made to execute this first phase data
collection
Macro is divided in two parts: questioning and data collection.

Questioning part is first executed to define the case description
Predefined problem areas (Call failures, unit restarts, site connectivity,)
If user cannot immediately answer to some questions, answers should be found
out before continuing to avoid unnecessary info requests.
Generic data collection for unidentified problems
Data collection based on given answers.
29
CN34042EN33GLN0
Preliminary actions
Use always latest QAL version available, getting by
send e-mail:
: ccts.qal.support@nsn.com
To
Subject: QAL_UPDATE
QA logging macro is made for HIT tool

HIT must be installed in users Windows PC
HIT 2.10-x or higher is required
Device connection for all involved network elements
need to be defined in HIT
QA logging include the following files which must

be included in same local directory in users PC
QAL_START.hit (macro file for execution)
QAL_FUNC.tel ( function library)
QAL.ini (logic for questioning phase)
30
CN34042EN33GLN0
QAL 2.1-3 MSS.zip
Execution
Start HIT tools and define device connection, if not exist yet
Open QAL_START.HIT and press start button
31
CN34042EN33GLN0
Execution
Select Problem area to start questioning phase
Full data collection is not for

first phase data collection. It
should be run only when
requested by NSN.
Questioning based on selected problem area, answer correctly to all questions
32
CN34042EN33GLN0
Execution
Select execution mode, single or multi-tasking mode
Select network element for data collection , execution start after devices are
selected
33
CN34042EN33GLN0
Results
Results are collected in case specific directories under execution directory.
There are subdirectories for all NE from where data was collected
Directory format: /QAL_<date>_<time>/
/QAL_<date>_<time>/<element name>/
Log files must be zipped to decrease size.

Usually less than 1Mbits even several elements included.
Example:
/QAL_2009-12-02_13-44-27/
QAL_2009-12-02_13-44-27.ZIP
NOTE!
It is mandatory to include QA logging results in every problem case before
its escalated to level 3 in Resolve.
34
CN34042EN33GLN0
Result
QA_LOGGING
creates unique
case specific
directory under
execution
directory. Under
case directory
there are
subdirectories for
all network
elements from
where data was
collected.
35
CN34042EN33GLN0
Appendix
36
CN34042EN33GLN0
Find your VTP/VDU

ZQNS;
MSCi
MSS_880091
2006-05-20
14:28:31 PAGE
SYSTEM
USERNAME
USER
SYSTEM
USER
I/O-DEVICE
MML
SESSION
NUMBER
990095 MSC02
SYSTEM
SYSTEM
SYSTEM
880091 MSC02
880091 MSC02
880091 MSC02
OMU-VTP17
OMU-VTP19
OMU-VTP21
TU
QN
US
00602
00612
00607
COMMAND EXECUTED
37
CN34042EN33GLN0
Connect DIAGNOS logical file to your VTP

If you want the diagnostics output to appear on you screen then connect logical file
to your VTP/VDU
ZIIS:,OMU:DIAGNOS,::DEV=VTP-19:;
LOGICAL FILE MODIFIED:
SYSTEM = MSS_880091 UNIT = OMU
PAGE
1
LOG
LOG
SPARE PHYSICAL
FILE
FILE
FILE
FILE
NBR NAME & CLASS MODE NAME
5B DIAGNOS
38
OBJ SYSTEM
IND NAME
UNIT DEVICE/
NAME LOGICAL
FILE
1 MSS_880091 OMU
2 MSS_880091 OMU
3 MSS_880091 OMU
CN34042EN33GLN0
LPT-1
VDU-5
VTP-19
Start diagnostics
Change Computer Unit state to TE-EX
ZUSC:SIGU,2:TE;
Then start diagnostics
ZUDU:SIGU,2;
39
CN34042EN33GLN0
Diagnostics output
Press enter several times to get partial and total diagnostics report on your screen
MSCi
MSS_880091
2006-01-26 11:55:33
DIAGNOSTIC REPORT
SIGU-2
1B002-00
PARTIAL DIAGNOSIS
TOTAL
DIAGNOSTIC PROGRAM 0000
DIAGNOSIS
3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
If you didnt connect the logical file to your VTP/VDU then you can always check
diagnostics result from history (see next page)
40
CN34042EN33GLN0
Diagnostics history
ZUDH:SIGU,2::;
MSCi
MSS_880091
2006-01-26 11:35:43
DIAGNOSTIC REPORT HISTORY

UNIT = SIGU-2 REPORT-CLASS = ALL DATE = 2006-01-26 TIME = 00:00:00
MSCi
MSS_880091
2006-01-26 10:42:11
PARTIAL DIAGNOSIS EXECUTED
SIGU-2
POWER
MSCi
MSS_880091
2006-01-26 10:42:35
SIGU-2
CPU
MSCi
MSS_880091
2006-01-26 10:42:35
SIGU-2
RAM
MSCi
MSS_880091
2006-01-26 10:42:40
SIGU-2
SYSB
MSCi
MSS_880091
2006-01-26 10:42:40
DIAGNOSTIC REPORT
SIGU-2
PARTIAL DIAGNOSIS
TOTAL
DIAGNOSTIC PROGRAM 0000
DIAGNOSIS
3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
41
CN34042EN33GLN0
Set trace on Nokia Clear Code

ZIIS:,OMU:OBSFAILA,::DEV=VTP-19:;
ZTOF:S,:005:;
(trace for B-Subscriber busy: 0005H)
Clear
Code
SIGNALLING COMPLETE
ANSWER
CHARGING END
PAGING TIME
EXT CLEAR CODE
: 2006-01-26
:
:
: 1280
: 0011H
16:11:08.21
STAT STATE
CLEAR CODE
CLEAR INFO
CLEAR PART
SIGNALLING
:
:
:
:
:
IDLE
0005H
AIF_SS 0003H 0B2FH
SUB B
MS CC
Additional
information fields
Check details in NED
42
CN34042EN33GLN0
Connect logical file OBSFAILA to physical file on disk

1. Create new directory for the physical file on both disks
ZIWL:,OMU:WSB,DEF::PHYFILES,,,XY:;
2. Create physical file (OBSFAILALOG.TXT) on both disks
ZIWC:,OMU:WSB,DEF:PHYFILES,:OBSFAILALOG,TXT,999999,XY:;
(One CC observation needs about 2490 bytes. File size "999999" gives space for about 400 CC observations)
3. Link physical (as a ring file) file to logical file (OBSFAILA)
ZIII:,OMU:OBSFAILA,B:,PHYFILES,:OBSFAILALOG,TXT,,RF:;
4. Set logical file to write to both disks
ZIIS:,OMU:OBSFAILA,::DEV=WDU-SB:;
5. Set path to read file from system disk
ZIWY:S:UNIT=OMU,PATH=-PHYFILES,DRIVE=WDU-S;
6. Output physical file in ASCII format
ZIBT:WDU,S,OBSFAILALOG,TXT,,,,A,;
43
CN34042EN33GLN0
Fast Subscriber Trace for ongoing calls only

MCJ:IMSI=460100000000104::TYPE=D:;
MSCi
MSS04
2008-05-20
15:05:45
SEARCH CALL PATH

LEG TYPE
LEG CALL ID
ORIG CALL ID
CALL START
SIGN COMP
ANSWER
CHAR END
LAST MESSAGE
CLEAR CODE
UNIT ID
:
:
:
:
:
:
:
:
:
:
ORIGINAL
0004H-0000000BH-4004H-4131H-0003H-00H-4131H-0005H-00H
2008-05-20
2008-05-20
2008-05-20
....-..-..
2008-05-20
TARGET
CALL TYPE
CALL PHASE
STAT STATE
D5C8
:
:
:
:
MSC
/SCALLF
INTERNAL
CONVERSATION
AB SEIZED
BSU -001
CALLING NUMBER
CALLED NUMBER
OUTPULSED NUMBER
CONNECTED NUMBER
FORWARDED TO
ROAMING NUMBER
ADDRESS NUMBER
OBJECT
TRACING REF/TYPE
IMSI
IMEI
RADIO SYSTEM
CGR/PCM-TSL/STATE
BICC CIRCUIT
NET
SPC
CIC
MGW
BNC CHAR
TDMTERMID
TERMID
44
15:05:24
15:05:28
15:05:29
..:..:..
15:05:29
:
:
:
:
:
:
:
I
I
I
I
8622301000006
8612301000104
8612301000104
8612301000104
N
U
42300100006
12301000104
SUBSCRIBER A
:
/
: 460200000000006
:
: GSM
: 00531/2048-04/R
SUBSCRIBER B
00001/ALL EVENTS
460100000000104
GSM
00531/2048-05/R
:
:
:
: VMGW31
: TDM
: 00001-04
:
CN34042EN33GLN0
VMGW31
TDM
00001-05
Fast Subscriber Trace for ongoing calls only(Cont.)

CNTL TYPE/INDEX
MCC/MNC
BSC/LAC/CI
RNC
NAME/INTRA CI
LOCATION NUMBER
USED CODEC
CHANNEL RATE
SPEECH VERSION
LSA
USED CHANNEL CODINGS
PRIOR/CATEG
MS CLASSMARK
MS UMTS CAPABILITY
IN CATEGORY KEY
CAMEL CALL ADDRESS
CAMEL REF NUMBER
CTM TT CAPABLE
TEST CALL CATEGORY
PAGING TIME
BACK/FORW
HO LINK
ROAM LINK
INTERCONNECTING TDM
ANCHOR IC TDM
: BSU /00001
: 460 /30
: 00003/00300/00301
:
: BTS301
/00000
:
: G711 A
: FR /FR /FR
: FR1
:
:
:
/ORDINARY
: 3
:
:
:
:
: NO
:
:
:
:
:
:
:
-
ECHO CANCELLING PARAMETERS

RECEIVED IEC / OEC
SENT IEC / OEC
IEC STATE / OEC STATE :
/
ICC-PID
SSI-PID
SSO-PID
AIFI-PID
AIFO-PID
OCC-PID
CFO-PID
CTH1-PID
CTH2-PID
4131H/0134H/0003H/00H
/
/
/
/
/
/
4131H/0132H/002EH/00H
4131H/0132H/002FH/00H
4131H/0136H/0005H/00H
/
/
/
/
/
/
/
/
/
COMMAND EXECUTED
45
CN34042EN33GLN0
BSU /00001
460 /30
00003/00300/00301
BTS301
G711 A
FRP /FR
FR1
/00000
/FR
/ORDINARY
3
NO
01170 ms
/
0005
-
Detailed Subscriber Trace

ZIIS:,OMU:GSMME1PR,::DEV=VTP-19:;
ZMWC:MSISDN=460100000000104:REF=1,:;
MSCi
MSS04
2008-05-20 15:14:36
MSC OBSERVATION REPORT FROM OMU-0
REPORTING TIME
: 2008-05-20 15:14:36.97
REPORT NUMBER
: 000029
RECORDING ENTITY
: 8642300100
REPORT REASON
: EVENT
INVOKING EVENT
: FAIL
CALL ID
: 0008H-00000010H-4004H-4131H-0006H-00H-4131H-0009H-00H
CALL START
: 2008-05-20 15:14:24.22 CALL PHASE : RELEASE
SIGNALLING COMPLETE :
STAT STATE : IDLE
ANSWER
:
CLEAR CODE : 0874H
CHARGING END
:
CLEAR INFO : URQPRB 0E01H 0000H
PAGING TIME
:
CLEAR PART : SYSTEM
EXT CLEAR CODE
:
SIGNALLING : MGW TRACE
: OK
EXTERNAL FORWARDING COUNTER : 0
46
CN34042EN33GLN0
CALLING NUMBER
CALLED NUMBER
OUT PULSED NUMBER
CONNECTED NUMBER
ROAMING NUMBER
ADDRESS NUMBER
BIWF ADDRESS A
:
:
:
:
:
:
:
I
N
8612301000104
1022301000006
U 1022301000006
8632300300
DESTINATION: 14
SUBDEST
38
ROUTE
2100
OBJECT
IMSI
IMEI
RADIO SYSTEM
CGR/BSC/PCM-TSL
MCC/MNC
LAC/CI/CELL BAND
MGW INDEX
MGW NAME
BNC CHAR
TDM TERMID
NORMAL CTX ID
USED CODEC
CHANNEL RATE
SPEECH VERSION
PRIORITY
MS CLASSMARK
CTM TT CAPABILITY
RESULT
0874H
SUBSCRIBER A
: 460100000000104
:
: GSM
: 0531/0003/2048-08
: 460 /30
: 00300/00301/
: 0
: VMGW31
: TDM
: 1-8
: 524694
: G711 A
: FRP / FR
/ FR
: FR1
:
: 3
DUAL BAND
: NO
END OF REPORT
47
CN34042EN33GLN0
SUBSCRIBER B
/
/
/
/
Test calls
Test calls are done for two purposes:
test analysis - to test defined analyses
test hunting - to force-route a call on a certain circuit that is
put in
the TE state.
Test calls
Test analyses
48
CN34042EN33GLN0
Test hunting (forced routing)
Flow of test calls

Test case
A) Test analysis
definition
Not test phone
B) Test hunting
C) Test analysis and
Yes
Normal trunk
Test Hunting
1
Test
Test phone or
Normal traffic
origin
Test trunk
not test phone
matched
No
Normal trunk
5
Test phone
Exchange
0 test origin = normal cell

1 test origin = normal incoming circuit
Test mobile
2 test origin = test cell

3 test origin = incoming test circuit
Normal cell
4 test origin = test origin received in subscriber signalling

5 test origin = test origin received in incoming circuit signalling
49
CN34042EN33GLN0
Test mobile or
not test
mobile
Test cell
Not test mobile
Normal cell
Own MSC
Message Monitoring
1)
Check CM state ZUSI:CM,:; e.g. CM,0 WO-EX
2)
Connect service terminal - ZDDS:CM, 0:; ( 1 in case CM,1 is working).
3)
ZOQA:W,C=3215
4)
ZOQ:70
CCSU
BSU
3
1
3215
50
3215
4
CN34042EN33GLN0
CM
Monitoring attribute results

Charging origin
Analysis tree
MONITORING TIME: 2004-03-28
Analysed digits
11:22:27.74
RECEIVED BY: 0070 0000 00

MONITORED MESSAGE: 0053 4532 0134 0113 00 19 0000 3215 0041
00 00 02 00 00 00 00 00 00 00 FF FF FF 06 04 09 0A 09 09 03 06 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 FF 04 06 00 64 00 00 00 00 00 00 00
Analysis type
TMR
TON
TMR
Type of Number in Messages:
Numbering Plan in Messages:
not_exist
not_allowed
unknown
reserved
unknown_numb
international
national
net_specific
subscriber
abbreviated
dedicated_pad
not_exist
not_allowed
unknown
reserved
unknown_plan
isdn_teleph
data
telex
nation_stand
private
51
0
1
2
3
4
5
6
7
8
9
A
CN34042EN33GLN0
0
1
2
3
4
5
6
7
8
9
255
do_not_care_c Do not care
10
khz3_1_c
3.1 kHz audio
kb64_pre_c
64 kbit/s preferred
kb64_unres_c 64 kbit/s unrestricted
kb1920_unres_c
Reserved for 1920 kbit/s unrestricted
kb1536_unres_c
speech_c
kb384_unres_c
kb2_64_unres_c
Reserved for 2 x 64 kbit/s unrestricted
sv_1_sv_2_c
Alternate 64 kbit/s unrestricted (service 1)/
sv_2_sv_1_c
Alternate speech (service 2)/
Speech
speech (service 2)
64 kbit/s unrestricted (service 1)

Troubleshooting Tools DX200

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Troubleshooting Tools DX200

Încărcat de

Drepturi de autor:

Formate disponibile

Troubleshooting

Nokia Siemens Networks

Nokia Siemens Networks

REPORT TO THE USER

Nokia Siemens Networks

Alarm system user interface

Nokia Siemens Networks

BLOCKED ALARMS HANDLING

Five Alarm Classes

Nokia Siemens Networks

Alarms at One Instance of Time

Nokia Siemens Networks

Alarm printout examples

(0039) 2186 CALL CONTROL ANALYSIS MISSING

(0040) 2186 CALL CONTROL ANALYSIS MISSING

(0055) 3200 UNKNOWN RNC

Nokia Siemens Networks

CALL CONTROL ANALYSIS MISSING

Nokia Siemens Networks

ZUD ... DIAGNOSTICS HANDLING

ZUDU START UNIT TEST/PARTIAL UNIT TEST

Nokia Siemens Networks

Diagnostic Printout Example

3998 DIAGNOSIS EXECUTED - UNIT NOT OK

Nokia Siemens Networks

Why Logical File?

Nokia Siemens Networks

Logical files used in troubleshooting

Nokia Siemens Networks

Output Clear Codes reporting

Nokia Siemens Networks

Clear Code groups

Nokia Siemens Networks

Circuit Group Measurements Example

TRAFFIC MEASUREMENT REPORT

Name & Nbr. of the CGR

ANSW SFAIL IFAIL EFAIL

CALLS : All call attempts

Time (TC) and total (CC) calls congested.

Nokia Siemens Networks

SFAIL: Failed by Subscriber error

Trace example 1/3

MSC OBSERVATION REPORT FROM STU-0

: ALL, BASIC, UNPRIOR

TRACE TYPE USED

: ALL, BASIC, UNPRIOR

CLEAR CODE : 0000H

CLEAR INFO : AIF_SS 0001H 0B2EH

EXT CLEAR CODE

Nokia Siemens Networks

Trace example 2/3

EXTERNAL FORWARDING COUNTER

OUT PULSED NUMBER : I

: NOT USED IP TRUNK

Nokia Siemens Networks

Trace example 3/3

ECHO CANCELLING PARAMETERS

SENT IEC / OEC

Nokia Siemens Networks

Testing number analysis

CATEGORY Test mobile created in the HLR

Test digit analysis tree with analysis

Test attribute analysis created

Nokia Siemens Networks