Alarms Handling and Basic Troubleshooting

8/9/2019 Alarms Handling and Basic Troubleshooting

http://slidepdf.com/reader/full/alarms-handling-and-basic-troubleshooting 1/38

1 © Nokia Siemens Networks Presentation / Author / Date

For internal use

Troubleshooting trainingTools and methods for basic DX and IPA troubleshooting




For internal use

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

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 programblocks),- The cancellations of fault observations.

The distributed part sends the hypotheses (that have become certain on theunit level) and their cancellations to the alarm system's centralised partlocated in the maintenance computer of the system.

Alarm route: Units-> CLBU -> CLSU -> OMU

Related card: HWATThe Hardware Alarm Terminal (HWAT-A plug-in unit) conveys the internalhardware alarms of the DX 200 system to the Operation and MaintenanceUnit (OMU) and sends and receives the external alarms of the exchange. Italso performs the forced control of the changeover of the Group Switch(GSW) and the synchronization unit.




For internal use

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

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 MSC633 01 0001 01 0000

1/ type of alarm: standard, update printout, history2/name of NE4/computer sending alarm5/ alarm equipment type6/ date , time7/urgency8/printout type9/computer unit10/alarm number -> Check in NED !

11/alarm text12/suppelementary information -> Check in NED




For internal use

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;

/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:44 *//* 4 USI:COMP; *//* 4c COMMAND EXECUTED *//* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:44 */NEL;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:50 *//* 4 NEL; *//* 4c COMMAND EXECUTED *//* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:50 */

IGO:2006-01-26,10-00,2006-01-26,10-30:USERID=SYSTEM::;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:09:42 */COMMAND EXECUTED


http://slidepdf.com/reader/full/alarms-handling-and-basic-troubleshooting 7/387 © Nokia Siemens Networks Presentation / Author / Date

For internal use

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=250K=250 L=250 M=250 N=250 O=250 P=250 Q=250 R=250 S=250 T=250U=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

Find your VTP/VDU

ZQNS;

LOADI NG PROGRAM VERSI ON 12. 4- 0

MSCi MSS_880091 2006- 01- 26 16: 09: 07 PAGE 1

SYSTEM USERNAME USER USER MML SESSI ON

SYSTEM I / O- DEVI CENUMBER

880091 MSS_880091 SYSTEM 880091 MSS_880091 OMU- VTP20 J G 00021

SYSTEM 880091 MSS_880091 OMU- VTP19 QN 00020



For internal use

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:;

LOGI CAL FI LE MODI FI ED:

SYSTEM = MSS_880091 UNI T = OMU

PAGE 1LOG LOG SPARE PHYSI CAL OBJ SYSTEM UNI T DEVI CE/FI LE FI LE FI LE FI LE I ND NAME NAME LOGI CALNBR NAME & CLASS MODE NAME FI LE

5B DI AGNOS P 1 MSS_880091 OMU LPT- 12 MSS_880091 OMU VDU- 53 MSS_ 880091 OMU VTP-19



For internal use

Start diagnostics

Change Computer Unit state to TE-EX…

ZUSC:SIGU,2:TE;

Then start diagnostics…

ZUDU:SIGU,2;



For internal use

Diagnostics history

ZUDH:SIGU,2::;MSCi MSS_880091 2006- 01- 26 11: 35: 43

DI AGNOSTI C REPORT HI STORY

UNI T = SI GU- 2 REPORT- CLASS = ALL DATE = 2006- 01- 26 TI ME = 00: 00: 00

MSCi MSS_880091 2006- 01- 26 10: 42: 11

PARTI AL DI AGNOSI S EXECUTED SI GU- 2 POWER

MSCi MSS_880091 2006- 01- 26 10: 42: 35

PARTI AL DI AGNOSI S EXECUTED SI GU- 2 CPU

MSCi MSS_880091 2006- 01- 26 10: 42: 35

PARTI AL DI AGNOSI S EXECUTED SI GU- 2 RAM

MSCi MSS_880091 2006- 01- 26 10: 42: 40

PARTI AL DI AGNOSI S EXECUTED SI GU- 2 SYSB

MSCi MSS_880091 2006- 01- 26 10: 42: 40

DI AGNOSTI C REPORT

SI GU- 2

PARTI AL DI AGNOSI S TOTAL

DI AGNOSTI C PROGRAM 0000

DI AGNOSI S 3999

3999 TOTAL DI AGNOSI S EXECUTED - UNI T OK

END OF REPORT



For internal use

Clear Code Groups

Clear codes have been divided into four main classes:

000H - 3FFH: normal clearing400H - 7FFH: internal congestion800H - BFFH: external congestion

C00H - FFFH: subscriber errorsThe first main class 'normal clearing' (000H – 3FFH) consists of clear codes which have not been caused byan error in the exchange or by subscriber error, but which nevertheless leads to clearing of a call or to aninterruption in call set-up.The second main class, 'internal congestion' (400H - 7FFH) consists of cases in which a call or call set-up isinterrupted because of an error in the exchange. This group contains clear codes related mainly to filemanagement 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 isinterrupted because of an error outside the exchange. This group consists mainly of clear codes related tointer-exchange signalling.The fourth main class, 'subscriber error' (C00H - FFFH) includes the cases in which a call or call set-up isinterrupted by a subscriber's error or by a failure in the subsriber's equipment or by faulty subscriber signalling




For internal use

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

Clear Codes

ZTUS:CLR,60,0;

MSCi MSS_880091 2006- 01- 26 10: 16: 01

MODE: CLR

STATE: ACTI VERES. OUTPUT DAY:

MON 00: 00- 24: 00

TUE 00: 00- 24: 00WED 00: 00- 24: 00

THU 00: 00- 24: 00FRI 00: 00- 24: 00

START DATE: 2006- 01- 26 10: 16: 00STOP DATE: -

RES. ACC. PERIOD: 60OUTPUT DELAY: 0

COMMAND EXECUTED




For internal use

Clear Codes

ZTUT:CLR;

LOADING PROGRAM VERSION 14.17-0

SIGNALLING RING SPEECH CLEAR CODE0 0 235 000H NORMAL END OF THE CALL1 3 1 005H B-SUBSCRIBER BUSY2 0 0 00DH CALL TERMINATED BY OPER

22 7 1 015H NORMAL UNSPECIFIED

0 0 1 024H MAX DUR OF CALL EXCEEDED0 2 0 206H CALL REJECTED1 0 0 304H B-LINE OUT OF SERVICE

89 0 0 30AH A ONHOOK DURING SET UP51 143 0 30BH A ONHOOK DUR_WAIT ANSWER1 0 0 603H NO RESPONSE FROM CO-PROC4 0 0 706H CALL INTER REG ANALYSIS3 1 1 80FH CIRCUIT CONGESTION

491 0 0 812H MAP FAILURE2 1 1 B13H RADIO IF FAILURE

END OF REPORT




For internal use

Set trace on with specific Clear Code

ZIIS:,OMU:OBSFAILA,::DEV=VTP-19:;

ZTOF:S,:005:; (trace for B-Subscriber busy: 0005H)

SIGNALLING COMPLETE : 2006-01-26 16:11:08.21 STAT STATE : IDLE ANSWER : CLEAR CODE : 0005HCHARGING END : CLEAR INFO : AIF_SS 0003H 0B2FHPAGING TIME : 1280 CLEAR PART : SUB B

EXT CLEAR CODE : 0011H SIGNALLING : MS CC

Check details in NED

ClearCode

Additionalinformation fields




For internal use

Fast Subscriber Trace for ongoing calls only

ZMCJ:IMSI=260109900000001:::;

LOADI NG PROGRAM VERSI ON 8. 102- 0MSCi MSS_880091 2006- 01-26 16: 16: 42SEARCH CALL PATHLEG TYPE : ORI GI NALLEG CALL I D : 0014H-0015H-4004H-4132H-0009H-00H-0009H-00H

ORI G CALL I D :START : 2006- 01- 26 16: 16: 35 STAT STATE: AB SEI ZEDLATEST : 2006- 01- 26 16: 16: 41 D5C8A DI R NUMBER : I 48701000001B DI R NUMBER : N 701000002

MSRN : N 701000630OBJ ECT SUBSCRIBER A SUBSCRIBER B

I MSI : 260109900000001 260109900000002

CGR/ CRCT/ PCM- TSL/ STATE : 00300/ 00017/ - / R 00300/ 00018/ - / RMGW : MGW01V01 MGW01V01BNC CHAR : TDM TDM TDMTERMI D : 0002- 18 0002- 19 TERMI D : 40000052 40000053BACK/ FORW : /HO LI NK :ROAM LI NK : 0015H

I CC- PI D 4132H/ 0134H/ 0009H/ 00HSSI - PI D / / /SSO- PI D / / /AI FI - PI D 4132H/ 0132H/ 0012H/ 00HAI FO- PI D 4132H/ 0132H/ 0013H/ 00H

COMMAND EXECUTED




For internal use

Detailed Subscriber Trace

ZIIS:,OMU:GSMME1PR,::DEV=VTP-19:;

ZMWC:MSISDN=48701000001:REF=1,:;MSCi MSS_880091 2006- 01- 26 16: 13: 44MSC OBSERVATI ON REPORT FROM STU- 0REPORTI NG TI ME : 2006- 01- 26 16: 13: 43. 52REPORT NUMBER : 000026 TRACED I MSI : 260109900000002

TRACE REFERENCE : 00001OMC I D : TRACE TYPE : ALL, BASI C, UNPRI OR TRACE TYPE USED : ALL, BASI C, UNPRI ORSTART TI ME : 2006- 01- 26 16: 13: 36. 95END TI ME :RECORDI NG ENTI TY : 48701000700REPORT REASON : EVENTI NVOKI NG EVENT : SUBS( B)CALL I D : 0012H-0013H-4004H-4132H-0008H-00H-0008H-00H

CALL START : 2006- 01- 26 16: 13: 33. 33 CALL PHASE : CONVERSATI ON




For internal use

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

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 programblock. 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 thesystem. 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

Computer Logs

Printout of SIGU-0`s error logs:

CALLER : 05E4 05F1 00 RETURN ADDRESS: 0940 (G0296).00000219WRITE TIME: 2007-11-06 13:37:53.58PARAMETERS: I-08 0938.00000021 00000075 0938.00000004USER TEXT : LST: UNKNOWN MGW, SCTP IPv4:USER DATA : mgw ip address version = 0

mgw ip address 1: 10.88.51.141mgw ip address 2: 00.00.00.00mgw ip port = 8013

User text show description regarding the error situation.User data contains the supplementary informationThe caller is the process who sends the alarm.

Finding the process based on the id:

Enter service terminal with ZDDS44-SYS>ZSXP:HTAID NAME LDT ATTR BP MP SI HGC MQ EH IS LP HP05E4 HTAPRB 6D18 (G3491) 18FC 01 60 0014 0006 0A28 01 00 60 60

And vice versa, f inding the process family based on the process ID:

4-MAN>ZSXPI:5E4ID NAME LDT ATTR BP MP SI HGC MQ EH IS LP HP05E4 HTAPRB 6D18 (G3491) 18FC 01 60 0014 0006 0A28 01 00 60 60




For internal use

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 runningpackage.

MRS: in order to output DX error messages in details

ZLP:1,MRS

R:5656 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

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

Output Computer Unit logs in Chorus units – Extendedform

LOGS (Extended form)0008-$ clog -s -a

CALLER: 3CB TYPE: I-8 DATE: 01.01.1970 TIME: 00:00:39.01USER TEXT: UXCPRB: INFO -- UX1 SYNC FOUND interrupt occurredUSER DATA: port = 2utopia = 10hw_block = 1

..

.

.

CALLER: 3CB TYPE: I-8 DATE: 01.01.1970 TIME: 00:01:53.70USER TEXT: UXCPRB: NOTICE -- SDxG interrupt occurredUSER DATA: port = 0, interface = 0unit = UNKNOWN

CALLER: 3CB TYPE: I-8 DATE: 01.01.1970 TIME: 00:02:12.30USER TEXT: UXCPRB: NOTICE -- SDxG interrupt occurredUSER DATA: port = 0, interface = 0unit = UNKNOWN




For internal use

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 toexecute 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:

MONI TORI NG TI ME: 2003- 04- 15 16: 58: 09. 34

SENT BY: 04B4 001A 00

MONI TORED 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 0008 00 00 02 00

05 21 01 21 01 21 01 21 01 29 29 29 29 FF FF FF FF FF FF FFFF 00 FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00




For internal use

The message monitoring in DMX units:

1/1 Document Type AuthorUnit/Dept.

Document TitleDate, VersionFor internal use

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 themessage.

MONITORED MESSAGE: 0053 554D 049E 0000 00 09 0000 E3FE 0012

0053: Message length554D: 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.

Deeper troubleshooting




For internal use

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 toworking unit of the monitored program block that is located in. (ZDDS)

ZOQ parameters:

FAM Target process family (FFFF = any family)

PRO Target process (FFFF = any process). If the target family is = FFFF, the parameter has no meaning)

DI Direction (0 = outgoing messages, 1 = incoming messages, 2 = outgoing and incoming messages)

ID Message identifier (FFFF = any message)

GR Message group identifier (FFFF = any)

C_C Partner computer identifier (FFFF = any)

C_F Partner family identifier (FFFF = any)

C_P Partner process identifier (FFFF = any. If the partner family identifier = FFFF, the parameter has no meaning)

E_F Excluded family identifier. If the partner family identifier = FFFF, this parameter can be used for excluding aprocess family from the monitoring (FFFF = none)

E_P Excluded process identifier (if the excluded family identifier = FFFF, the parameter has no significance)QL 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


Message monitoring methods in Chorus units:

All messages sent between computer units are DMX messages regardless from or to which type (DMX orChorus) of unit they are sent. Therefore, in order to be able to send and receive DMX messages, Chorusactors 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 un its!

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 dmxshowloadext dmxmon

Dmxshow command will show the FAM for the related actor:0011-$ dmxshow -mFAM PROC FOCUS act or t hread queue # pendi ng al l ocat ed054C 0000 00 0054 0076 00000 0000 00 0023 000D 1 0 00F03 0000 00 0071 00BC 123 0 0




For internal use

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

What is important in “daily” troubleshooting?

Focus points are:

User Plane in MSS: URQ, RMA (resource alloc.) , CIA (H.248)

in MGW: BC2, RM2 (resource)

Control Plane (in MSS): IC./OC. (call control), Aif (A interface)

1. Where do you have to take monitoring from?

e.g: ZWQV::URQ% SIGU, BSU

2. What is the process ID?e.g: ZDDS:SIGU; ZSXP:<full path>URQ 05F5

3. Take the monitoring....





For internal use

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 monitoringZOEBR:MB_address:reserved_memory_in_hexe.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_addressZOEGF:MB_address:W0-log.binIt will save the log into log.bin file on W0. IDA can decode it depending on version. It is easier to print toscreen, decoding done automatically.

6. Kill monitoring conditions:ZOEK - It will release the used buffers and delete the monitoring conditions in all units.




32 © Nokia Siemens Networks Presentation / Author / DateFor internal use

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 toanalyze different kind of log files. IDA2 is well-suited to analyze log files interactively andautomatically 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 platformsas 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







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

1. Set trace for test call’s IMSI or MSISDN

2. Start trace3. Set monitoring conditions

4. Start monitoring ...Stop it when the test call finished

5. 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

6. 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 headerbutton.

HAND FOCUS




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...





CMREAD analysation:

1/1 Document Type AuthorUnit/Dept.

Document TitleDate, VersionFor internal use

FAM PRO DI ID GR C_C C_F C_P E_F E_P QLFFFF FFFF FF 3215 FFFF FFFF FFFF FFFF FFFF FFFF FF

MONITORING TIME: 2007-11-09 17:02:06.15RECEIVED BY: 0070 0000 00MONITORED MESSAGE: 0054 4531 0134 0001 00 19 0000 3215 004500 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 0000 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.16RECEIVED BY: 0070 0000 00MONITORED MESSAGE: 0054 4531 0294 0001 00 19 0000 3215 004500 00 32 00 00 00 00 00 00 00 FF FF FF 06 04 01 06 01 02 0A 0A 0A 00 00 0000 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 formatGREEN: the digit being analizedBLUE: the TON (type of number)


Bl kb




Blackbox

Blackbox:

Black box (boxana) is useful in case of unexpected uni t restart or process exception.In case of unexpected unit restart, tha alarm may not give relevant information regarding therestart, 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 exceptionsL: log file writingI: will show the reason for restart

U: will output the entire black box

BBLOG in Chorus units:

loadext bblogbblog -c -a x (default is 2 =previous restart) x can between 2-9

Mi i D b




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 pressRST (reset) and DBG (debugger) button in the CPU card.

Keep them pressed for few seconds, then release RST and hold DBG unit debugger loaded messageappears on screen.

It can help analizing the failures in case of unexpected continous unit restarts.

M it C t U it t t



For internal use

Monitor Computer Unit start up

Connect a laptop to the lower connector (DX200=J7, IPA2800=J1) directly to thecomputer unit you want to monitor.

Phase 1: Initial loading

The BOLERO loads the program codes and some system-release-specific files. At the end ofthe phase, the Operating System Kernel (DMXRTE), the Operating System and TestingInterface (service terminal program OSITUS) and the USAPRO are started up. Among otherthings, 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 arecreated and started up. Furthermore, all files, computer address tables, and system variablesare 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.

http://127.0.0.1:43231/NED/NED?action=retrieve&library=mschlr_rel_m14_3_v3_2009_02_05&identifier=dn60016686&edition=341&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=feb2211256271




Alarms Handling and Basic Troubleshooting

Documents

Transcript of Alarms Handling and Basic Troubleshooting