Alarms Handling and Basic Troubleshooting

Troubleshooting training
Tools and methods for basic DX and IPA troubleshooting
For internal use

1
Nokia Siemens Networks
Presentation / Author / Date
Agenda
Alarms (ZAHO, ZAHP and alarm description in NED)
MML command log (ZIGO)
Unit diagnostics (ZUDU)
Clear Codes (ZTUT or CC trace ZTOF with OBSFAILA logical file)
Subscriber Trace (ZMCJ or ZMWC with GSMME1PR logical file)
Message monitoring
Monitor Computer Unit start-up
Output Computer Unit logs & Black Box
For internal use

2
Basic Tools for troubleshooting

Where to start? .... The ALARMS
Alarm system consists of centralized and distributed part.
The distributed part of the alarm system handles -on the unit level-:
- The fault and disturbance observations (set by the application program
blocks),
- The cancellations of fault observations.
The distributed part sends the hypotheses (that have become certain on the
unit level) and their cancellations to the alarm system's centralised part
located in the maintenance computer of the system.
Alarm route: Units-> CLBU -> CLSU -> OMU
Related card: HWAT
The Hardware Alarm Terminal (HWAT-A plug-in unit) conveys the internal
hardware alarms of the DX 200 system to the Operation and Maintenance
Unit (OMU) and sends and receives the external alarms of the exchange. It
also performs the forced control of the changeover of the Group Switch
(GSW) and the synchronization unit.
For internal use
3
Alarms
Always remember to check blocked alarms (ZABO;) (ZAFP; in MGW)
Active alarms:
ZAHO;
ZAAP; in MGW
ZAHP::NR=:2006-01-26,09-00-00:;
MSCi
MSS_880091
2006-01-26 10:03:20
ALARM HISTORY
<HIST> MSS_880091
OMU-0
SWITCH 2006-01-26 09:48:36.92
NOTICE VTP-22
IOMANA
0690 WORKING STATE CHANGE
BL-SY WO-BU 0000 0000 0000 0000 0000 0000
For internal use

4
Alarm description
Structure of the alarm:
2PAC
CMU-0
SWITCH 2007-11-04 20:27:34.13
*** ALARM CMU-0
1A001-02 CRM_SJ
(0054) 3184 RNC CONTINUOUSLY OUT OF SERVICE IN MSC
633 01 0001 01 0000
1/ type of alarm: standard, update printout, history
2/name of NE
4/computer sending alarm
5/ alarm equipment type
6/ date , time
7/urgency
8/printout type
9/computer unit
10/alarm number -> Check in NED !
11/alarm text
12/suppelementary information -> Check in NED
For internal use

5
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
For internal use

6
MML command log

ZIAI:USERID=ALL;
MGW
IPA2800
2009-04-21 09:55:06
USER ID: SYSTEM

PROFILE NAME: PROFILE
COMMAND CLASS AUTHORITIES:
A=250 B=250 C=250 D=250 E=250 F=250 G=250 H=250 I=250 J=250
K=250 L=250 M=250 N=250 O=250 P=250 Q=250 R=250 S=250 T=250
U=250 V=250 W=250 X=250 Y=250
PASSWORD VALIDITY TIME LEFT: PASSWORD NEVER EXPIRES
MML COMMAND LOG ACCESSIBILITY: COMPLETE
UNIQUE PROFILE: NO
MML SESSION IDLE TIME LIMIT: 15 MIN(S)
FTP ACCESSIBILITY: WRITE
For internal use

7
Find your VTP/VDU

ZQNS;

MSCi
MSS_880091
2006-01-26
SYSTEM
USERNAME USER
NUMBER
880091 MSS_880091
For internal use

8
SYSTEM
16:09:07 PAGE
USER
SYSTEM
880091 MSS_880091
OMU-VTP20
JG
SYSTEM
880091 MSS_880091
1
MML
SESSION
I/O-DEVICE
00021
OMU-VTP19
QN
00020
Using DIAGNOS logical file for diagnostic reports

If you want the diagnostic output to appear on your
screen then connect logical file to your VTP/VDU
ZIIS:,OMU:DIAGNOS,::DEV=VTP-19:;
LOGICAL FILE MODIFIED:
SYSTEM = MSS_880091
PAGE
LOG
FILE
NBR NAME
&
5B DIAGNOS
UNIT = OMU
1
LOG
FILE
CLASS MODE
SPARE
FILE
NAME
PHYSICAL
FILE
For internal use

9
OBJ
SYSTEM
IND
UNIT
NAME
1 MSS_880091
DEVICE/
NAME
LOGICAL
FILE
OMU
LPT-1
2 MSS_880091 OMU
3 MSS_880091 OMU
VDU-5
VTP-19
Start diagnostics
Change Computer Unit state to TE-EX
ZUSC:SIGU,2:TE;
Then start diagnostics
ZUDU:SIGU,2;
For internal use

10
Diagnostics history
ZUDH:SIGU,2::;
MSCi
MSS_880091
2006-01-26
DIAGNOSTIC REPORT HISTORY

UNIT = SIGU-2
REPORT-CLASS = ALL
11:35:43
DATE = 2006-01-26
MSCi
MSS_880091
PARTIAL DIAGNOSIS EXECUTED
2006-01-26
SIGU-2
10:42:11
POWER
MSCi
MSS_880091
2006-01-26
SIGU-2
10:42:35
CPU
MSCi
MSS_880091
2006-01-26
SIGU-2
10:42:35
RAM
MSCi
MSS_880091
2006-01-26
SIGU-2
10:42:40
SYSB
MSCi
2006-01-26
10:42:40
MSS_880091
DIAGNOSTIC REPORT
SIGU-2
PARTIAL DIAGNOSIS
DIAGNOSTIC PROGRAM
DIAGNOSIS
TOTAL
0000
3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK

END OF REPORT
For internal use

11
TIME = 00:00:00
Clear Code Groups

Clear codes have 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 set-up.
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
inter-exchange 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 subsriber's equipment or by faulty subscriber signalling
For internal use

12
Clear Codes
About the Clear Codes (CC)
Clear codes helps greatly troubleshooting of a failed call.
Of course the call has to reach a certain level to get clear codes. (e.g.
call ID request).
1. Start the field reporting of clear codes:

ZTUS:CLR,60,0;
2. Output clear codes:

ZTUT:CLR;
For internal use

13
Clear Codes
ZTUS:CLR,60,0;
MSCi
MSS_880091
MODE:
STATE:
RES. OUTPUT DAY:
START DATE:
STOP DATE:
RES. ACC. PERIOD:
OUTPUT DELAY:
CLR
ACTIVE
MON 00:00-24:00
TUE 00:00-24:00
WED 00:00-24:00
THU 00:00-24:00
FRI 00:00-24:00
2006-01-26 10:16:00
60
0
COMMAND EXECUTED
For internal use

14
2006-01-26
10:16:01
Clear Codes
ZTUT:CLR;
SIGNALLING RING
0
0
235
1
3
1
2
22
0
0
1
0
1
89
51
143
0
1
0
0
4
3
491
2
1
1
END OF REPORT
For internal use

15
SPEECH
0
7
0
1
2
0
0
0
0
0
0
1
0
0
1
0
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
206H CALL REJECTED
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
Set trace on with specific Clear Code

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

16
Fast Subscriber Trace for ongoing calls only

ZMCJ:IMSI=260109900000001:::;
MSCi
MSS_880091
2006-01-26 16:16:42
SEARCH CALL PATH
LEG TYPE
: ORIGINAL
LEG CALL ID : 0014H-0015H-4004H-4132H-0009H-00H-0009H-00H
ORIG CALL ID :
START
: 2006-01-26 16:16:35
STAT STATE: AB SEIZED
LATEST
: 2006-01-26 16:16:41 D5C8
A DIR NUMBER
: I 48701000001
B DIR NUMBER
: N 701000002
MSRN
: N 701000630
OBJECT
SUBSCRIBER A
SUBSCRIBER B
IMSI
: 260109900000001
260109900000002
CGR/CRCT/PCM-TSL/STATE : 00300/00017/
- /R
00300/00018/
- /R
MGW
: MGW01V01
MGW01V01
BNC CHAR
: TDM
TDM
TDMTERMID
: 0002-18
0002-19
TERMID
: 40000052
40000053
BACK/FORW
:
/
HO LINK
:
ROAM LINK
:
0015H
ICC-PID 4132H/0134H/0009H/00H
SSI-PID
/
/
/
SSO-PID
/
/
/
AIFI-PID 4132H/0132H/0012H/00H
AIFO-PID 4132H/0132H/0013H/00H
COMMAND EXECUTED
For internal use

17
Detailed Subscriber Trace

ZIIS:,OMU:GSMME1PR,::DEV=VTP-19:;
ZMWC:MSISDN=48701000001:REF=1,:;
MSCi
MSS_880091
2006-01-26 16:13:44
MSC OBSERVATION REPORT FROM STU-0
REPORTING TIME
: 2006-01-26 16:13:43.52
REPORT NUMBER
: 000026
TRACED IMSI
: 260109900000002
TRACE REFERENCE
: 00001
OMC ID
:
TRACE TYPE
: ALL, BASIC, UNPRIOR
TRACE TYPE USED
: ALL, BASIC, UNPRIOR
START TIME
: 2006-01-26 16:13:36.95
END TIME
:
RECORDING ENTITY
: 48701000700
REPORT REASON
: EVENT
INVOKING EVENT
: SUBS(B)
CALL ID
: 0012H-0013H-4004H-4132H-0008H-00H-0008H-00H
CALL START
: 2006-01-26 16:13:33.33 CALL PHASE : CONVERSATION
For internal use

18
CALL ID
CALL ID : 0A9BH-AC8FH-401CH-4050H-0F61H-12H-0AF1H-57H
0A9BH: Record index of the call for SCALLF
AC8FH:Record index of the call for charging (LCALLF)
401CH: CPU identifier of the CHU computer that is handling charging for this call
4050H: CPU identifier of the RMAPRB that controls the call
0F61H: Hand ID of the RMAPRB that controls the call
12H: Focus of the hand process of the RMAPRB that control the call
0AF1H: Hand ID of XORPRB that controls the call
57H: Focus of the hand process of the XORPRB that controls the call
For internal use

19
Computer Logs
The Error log:
In case when alarms do not indicate enough information or there is no alarm at all,
the error logs can help.
The error logs do not necessary mean trouble or failure of the system or program
block. It gives a signal or message regarding certain state or output of the code.
Of course the error situations regarding configuration error or misbehavior of the
system. In order to gather the error logs of a certain computer unit, accessing the
service terminal is mandatory.
e.g: ZDDS:SIGU;
Using the command above will access the unit index 0.
- ZGSC shows the detailed error log printout,

- ZGL shows the operating system logs,
- ZGC will clear the logs in the unit accessed,
- ZGM will start logging, useful during troubleshooting,
- ZGD shows log directory.
For internal use
20
Computer Logs
Printout of SIGU-0`s error logs:
CALLER : 05E4 05F1 00 RETURN ADDRESS: 0940 (G0296).00000219
WRITE TIME: 2007-11-06 13:37:53.58
PARAMETERS: I-08 0938.00000021 00000075 0938.00000004
USER TEXT : LST: UNKNOWN MGW, SCTP IPv4:
USER DATA : mgw ip address version = 0
mgw ip address 1: 10.88.51.141
mgw ip address 2: 00.00.00.00
mgw ip port
= 8013
User text show description regarding the error situation.
User data contains the supplementary information
The caller is the process who sends the alarm.
Finding the process based on the id:
Enter service terminal with ZDDS
44-SYS>ZSXP:HTA
ID NAME
LDT
ATTR BP MP SI HGC MQ EH IS LP HP
05E4 HTAPRB 6D18 (G3491) 18FC 01 60 0014 0006 0A28 01 00 60 60
And vice versa, finding the process family based on the process ID:
4-MAN>ZSXPI:5E4
ID NAME
LDT
ATTR BP MP SI HGC MQ EH IS LP HP
05E4 HTAPRB 6D18 (G3491) 18FC 01 60 0014 0006 0A28 01 00 60 60
For internal use
21
Service Terminal Extensions

Service terminal extensions:
To directly access service terminal you have to connect to the J7 serial port of the working unit.
You can load several extensions these has to be copied under the BLCODE directory of the running
package.
MRS: in order to output DX error messages in details
ZLP:1,MRS
R:56
56 is the decimal error code. It will give detailed information regarding the error code.
RCB: Recovery..
Output and/or modify unit states, restart unit.
MAS: Mass memory handling:
File handling, copy/delete etc. e.g ZMXP:<PATH> shows the version of a file.
VIM: Vimmlagx -> MML session loading
00:MAN> ZLEL:1:0,W0-/VIMMLAGX.IMG
00:MAN> Z1C:0
For internal use

22
Output Computer Unit logs in Chorus units Short form

Log into chorus computer unit (Service Terminal e.g. ZDDS:NIS1,0;)
LOGS (Short form)
0008-$ clog -s
Contents of log:
001: CALLER: 3CB TIME: 00:00.39.01 USER TEXT: UXCPRB: INFO -- UX1 SYNC FOUND int
002: CALLER: 3CB TIME: 00:00.57.90 USER TEXT: UXCPRB: NOTICE -- SDxG interrupt o
s<number> print details of entry, n next page, any other key exit:
For internal use

23
Output Computer Unit logs in Chorus units Extended

form
LOGS (Extended form)
0008-$ clog -s -a
CALLER: 3CB TYPE: I-8 DATE: 01.01.1970 TIME: 00:00:39.01
USER TEXT: UXCPRB: INFO -- UX1 SYNC FOUND interrupt occurred
USER DATA: port = 2
utopia = 10
hw_block = 1
.
.
.
.
USER TEXT: UXCPRB: NOTICE -- SDxG interrupt occurred
USER DATA: port = 0, interface = 0
unit = UNKNOWN
USER TEXT: UXCPRB: NOTICE -- SDxG interrupt occurred
USER DATA: port = 0, interface = 0
unit = UNKNOWN
For internal use

24
Message monitoring
The message monitoring:
Deeper level troubleshooting method is the message monitoring gathering.
In order to find code error or possible configuration error (not that helpful) we are able to
execute different type of monitoring.
There is possibility to gather these logs from DMX( dx and ipa) and Chorus (ipa) units.
First of all here is the structure of the hex dump we call monitoring in DMX units:
MONITORING TIME: 2003-04-15
16:58:09.34
SENT BY: 04B4 001A 00

MONITORED MESSAGE: 0053 554D 049E 0000 00 09 0000 E3FE 0012
FF FF FF FF FF FF FF 03 02 10 00 00 00 00 00 00 01 00 00 00
08 00 00 02 00
05 21 01 21 01 21 01 21 01 29 29 29 29 FF FF FF FF FF FF FF
FF 00 FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00
For internal use

25
Deeper troubleshooting
1/1
Document Type
Author
Unit/Dept.
Document Title
Date, Version
For internal use
The message monitoring in DMX units:

MONITORING TIME: 2003-04-15 16:58:09.34
This message is monitored on 2003-04-15 16:58:09.34
SENT BY: 04B4 001A 00

04B4:
Process family ID (RM2 process).
001A:
Hand ID (Hand number 1A in the process family)
00:
Focus (reservation number of the hand, which is incremented after
every reservation and release of the hand).
Monitored messages consist of two parts: header and data. Below is the header of the
message.
MONITORED MESSAGE: 0053 554D 049E 0000 00 09 0000 E3FE 0012
0053:
Message length
554D:
Logical address (LGA) of the receiving computer unit (CACU).
049E:
Process family ID (LGM process family).
0000:
Hand ID (Hand number 0 is master process).
00:
Focus.
09:
Message attributes.
0000:
Message Number Group Identifier.
E3FE:
Message Number (leg_create_req_s).
0012:
Physical MB address of the sending unit (ISU-0).
The rest is data of the message. The data of the message can be visualized with IDA.
There are certain messages that could be analysed easily be seeing the hexadump.
For internal use
26
Message monitoring methods in DMX units:
The first, fastest and easiest way of message monitoring is the ZOQ command in service terminal. You need to access to
working unit of the monitored program block that is located in. (ZDDS)
ZOQ parameters:
FAM
PRO
DI
ID
GR
C_C
C_F
C_P
E_F
E_P
QL
Target process family (FFFF = any family)

Target process (FFFF = any process). If the target family is = FFFF, the parameter has no meaning)
Direction (0 = outgoing messages, 1 = incoming messages, 2 = outgoing and incoming messages)
Message identifier (FFFF = any message)
Message group identifier (FFFF = any)
Partner computer identifier (FFFF = any)
Partner family identifier (FFFF = any)
Partner process identifier (FFFF = any. If the partner family identifier = FFFF, the parameter has no meaning)
Excluded family identifier. If the partner family identifier = FFFF, this parameter can be used for excluding a
process family from the monitoring (FFFF = none)
Excluded process identifier (if the excluded family identifier = FFFF, the parameter has no significance)
Length of message queue (how many messages at the most can be in the monitor's message queue waiting for
handling.
The ZOQ monitoring will provide hex dump, decoding not needed.
For internal use

27
Message monitoring methods in Chorus units:
All messages sent between computer units are DMX messages regardless from or to which type (DMX or
Chorus) of unit they are sent. Therefore, in order to be able to send and receive DMX messages, Chorus
actors must register a DMX identity from the DMX messaging system. This identity contains the family,
process, and focus identifier, similar to the DMX processes.
Do not forget to use lower case when typing the commands in Chorus units!
In order to find out the family id of a thread you need to use command:
alist
It will list which family, process, focus are registered by DMX identity.
20000061 00000000 00000047 00000001 0071 SUP STARTED 001 yshell
It is possible that you need to load certain files before using them.
If you would like to use dmxmon or dmxshow, You need to load them with:
loadext dmxshow
loadext dmxmon
Dmxshow command will show the FAM for the related actor:
0011-$ dmxshow -m
FAM
PROC
FOCUS
actor
thread queue #
054C
0000
00
0054
0076
0000
0000
00
0023
000D
1
0F03
0000
00
0071
00BC
123
For internal use

28
pending
0
0
allocated
0
0
0
Starting the monitoring :
dmxmon f 54C l /bin/example.txt
it links the monitoring to a file
Press CNTRL-C to stop the monitoring
Command: cat will print the file out.
cat /bin/example.txt
After a successfull loading these extensions can be used.
For internal use

29
What is important in daily troubleshooting?
Focus points are:
User Plane
in MSS:
in MGW:
Control Plane (in MSS):
URQ, RMA (resource alloc.) , CIA (H.248)

BC2, RM2 (resource)
IC./OC. (call control), Aif (A interface)
1. Where do you have to take monitoring from?

e.g:
ZWQV::URQ%
2. What is the process ID?

e.g:
ZDDS:SIGU;
3. Take the monitoring....
For internal use

30
SIGU, BSU
ZSXP:<full path>URQ
05F5
Extended message monitoring:
It will provide possibility to monitor several program blocks (16) in several units (15) in the same time.
Always have to be taken from OMU!
The process is following:
1. Reserving memory for monitoring
ZOEBR:MB_address:reserved_memory_in_hex
e.g: ZOEBR:40:1000000
2. Create monitoring conditions
ZOEC:MB_address:SR:OFAM=process_id (SR means: sent, received)
e.g: ZOEC:40:SR:OFAM=132
3. Start monitoring: ZOEM:MB_address
4. Stop monitoring: ZOES:MB_address
5. Printout monitoring in hexadump to screen:
ZOEG:MB_address
ZOEGF:MB_address:W0-log.bin
It will save the log into log.bin file on W0. IDA can decode it depending on version. It is easier to print to
screen, decoding done automatically.
6. Kill monitoring conditions:
ZOEK - It will release the used buffers and delete the monitoring conditions in all units.
For internal use
31
How to read the monitoring LOGs???
The main troubleshooting tool is:
IDA2
IDA2 is an interactive and automatic off-line analysis and troubleshooting tool helping users to
analyze different kind of log files. IDA2 is well-suited to analyze log files interactively and
automatically for example from the DX platform containing objects such as error logs, test logs,
alarms, MML commands and responses and DX messages.
Although IDA2 has strong support for DX platform products it is also suitable for other platforms
as well.
Creating IDA2 extractors and decoders for different network products allows the browsing log
files and automated analysis.
IDA2 can be downloaded from:
https://confluence.inside.nokiasiemensnetworks.com/display/EE/EE+IDA2
For internal use

32
How can you find an exact call in a big log file?

1.
2.
3.
4.
5.
Set trace for test calls IMSI or MSISDN

Start trace
Set monitoring conditions
Start monitoring ...Stop it when the test call finished
Copy data (trace and logs)
From the trace check for CALL ID in that you will find the hand and the focus allocated to
the call. These two parameters are unique for MO an MT sides.
CALL ID
: 0CF6H-9327H-401CH-413EH-05D3H-F0H-05F1H-C4H
HAND
6.
FOCUS
The hand ID can be found in IDA under Process, the focus ID can be found under
focus. If you find it you can filter for that with a double click on process column header
button.
For internal use

33
CMREAD program block
The CMR is located in CM/CMM having tasks like digit-, barring analysis.
It can be decoded with IDA, but major segments can be seen easily.
Enter active CM/CMM`s service terminal:
ZDDS:<active CMM>;
ZOQE:<Process family ID>;
As it was described before, ZOQ can be set to certain message number. In this case it is 3215.
Set it to ID field using cursor.
Initiate the call...
For internal use

34
1/1 troubleshooting
Deeper
Document Type
Author
Unit/Dept.
Document Title
Date, Version
For internal use
CMREAD analysation:
FAM PRO DI ID GR C_C C_F C_P E_F E_P QL
FFFF FFFF FF 3215 FFFF FFFF FFFF FFFF FFFF FFFF FF
MONITORING TIME: 2007-11-09 17:02:06.15
RECEIVED BY: 0070 0000 00
MONITORED MESSAGE: 0054 4531 0134 0001 00 19 0000 3215 0045
00 00 02 00 00 00 00 00 00 00 FF FF FF 06 04 01 0A 0A 0A 0A 01 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 01
MONITORING TIME: 2007-11-09 17:02:06.16
RECEIVED BY: 0070 0000 00
MONITORED MESSAGE: 0054 4531 0294 0001 00 19 0000 3215 0045
00 00 32 00 00 00 00 00 00 00 FF FF FF 06 04 01 06 01 02 0A 0A 0A 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 01
RED:
the number of the TREE in hexadecimal format
GREEN: the digit being analized
BLUE: the TON (type of number)
For internal use
35
Blackbox
Blackbox:
Black box (boxana) is useful in case of unexpected unit restart or process exception.
In case of unexpected unit restart, tha alarm may not give relevant information regarding the
restart, only unit restarted alarm. Blackbox could provide detailed background of the event.
The loadable extension is : boxana.
1. Enter in the OMU service terminal: ZDDS;
2. Load the boxana extension: ZLP:1,BOX:
Commands:
A:
output the entire operating system log.
AE:
printout of error types
AS:
outputs statistical data
AP:
outputs only exceptions
L:
log file writing
I:
will show the reason for restart
U:
will output the entire black box
BBLOG in Chorus units:
loadext bblog
bblog -c -a x (default is 2 =previous restart) x can between 2-9
For internal use
36
Mini Debugger
a short turnout...
Mini debugger:
If there is continous unit restarts it is not possible to give commands in service terminal. In this case press
RST (reset) and DBG (debugger) button in the CPU card.
Keep them pressed for few seconds, then release RST and hold DBG unit debugger loaded message
appears on screen.
It can help analizing the failures in case of unexpected continous unit restarts.
For internal use

37
Monitor Computer Unit start up

Connect a laptop to the lower connector (DX200=J7, IPA2800=J1) directly to the
computer unit you want to monitor.
Phase 1: Initial loading
The BOLERO loads the program codes and some system-release-specific files. At the end of
the phase, the Operating System Kernel (DMXRTE), the Operating System and Testing
Interface (service terminal program OSITUS) and the USAPRO are started up. Among other
things, the USAPRO creates and starts up the library managers, and initializes the work files.
Phase 2: Loading files
During phases 1 and 2, library managers and program blocks of the I/O and loading system are
created and started up. Furthermore, all files, computer address tables, and system variables
are loaded.
Phase 3: Starting up program blocks
The rest of the program blocks are created and started.
Warming up is not a phase of its own; it is carried out immediately after the third phase.
For internal use

38

Alarms Handling and Basic Troubleshooting

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Alarms Handling and Basic Troubleshooting

Hochgeladen von

Copyright:

Verfügbare Formate

Troubleshooting training

Tools and methods for basic DX and IPA troubleshooting

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

Basic Tools for troubleshooting

Presentation / Author / Date

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

MML command log

For internal use

Presentation / Author / Date

MML command log

USER ID: SYSTEM

For internal use

Presentation / Author / Date

Find your VTP/VDU

LOADING PROGRAM VERSION 12.4-0

For internal use

Presentation / Author / Date

Using DIAGNOS logical file for diagnostic reports

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

DIAGNOSTIC REPORT HISTORY

3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK

For internal use

Presentation / Author / Date

Clear Code Groups

For internal use

Presentation / Author / Date

1. Start the field reporting of clear codes:

2. Output clear codes:

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

Set trace on with specific Clear Code

Check details in NED

For internal use

Presentation / Author / Date

Fast Subscriber Trace for ongoing calls only

For internal use

Presentation / Author / Date

Detailed Subscriber Trace

For internal use

Presentation / Author / Date

For internal use

Presentation / Author / Date

- ZGSC shows the detailed error log printout,

Presentation / Author / Date

Presentation / Author / Date

Service Terminal Extensions

For internal use

Presentation / Author / Date

Output Computer Unit logs in Chorus units Short form

For internal use

Presentation / Author / Date