Alm Rnc Diagnosis Reports

8/18/2019 Alm Rnc Diagnosis Reports

http://slidepdf.com/reader/full/alm-rnc-diagnosis-reports 1/61

Nokia Siemens Networks

WCDMA RAN, Rel. RU30,

Operating Documentation,Issue 01

IPA-RNC Diagnosis Reports (3700-3999)

DN99580889

Issue 07Approval Date 2010-12-09

Confidential



2 DN99580889

Issue 07


Id:0900d805807dba50

Confidential

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal

injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected

has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-

nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-

zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.



DN99580889

Issue 07

3


Id:0900d805807dba50

Confidential

Table of contentsThis document has 61 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 List of diagnosis reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 3725 DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITS. . . . . . . . . 8

3 3726 NO RESPONSE FROM UNIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 3727 COMMUNICATION ERROR WITH UNIT . . . . . . . . . . . . . . . . . . . 10

5 3728 UNIT ACCUSED BY RECOVERY - NO DIAGNOSTICS FOR UNIT

11

6 3734 INPUT DATA MISMATCH IN TEST PROGRAM . . . . . . . . . . . . . 12

7 3735 INTERNAL DATA MISMATCH IN TEST PROGRAM. . . . . . . . . . 13

8 3736 INTERNAL ERROR IN TEST PROGRAM . . . . . . . . . . . . . . . . . . 14

9 3749 HARDWARE CONFIGURATION MISMATCH . . . . . . . . . . . . . . . 15

10 3750 HARDWARE CONFIGURATION MISMATCH . . . . . . . . . . . . . . . 16

11 3752 UNIT TESTING PREVENTED - UNIT NOT IN TEST STATE SET BY

SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

12 3760 FAILURE IN MEMORY SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . 18

13 3761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIP-

MENT DATABASE DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

14 3764 FAILURE IN I/O SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

15 3780 ADDRESSING FAILURE IN MEMORY SPACE. . . . . . . . . . . . . . 21

16 3800 TIME OUT IN TEST PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . 22

17 3822 SCSI EQUIPMENT FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

18 3830 UNSUCCESSFUL HWILIB INQUIRY . . . . . . . . . . . . . . . . . . . . . . 25

19 3835 MODULE LOADING ERROR IN TEST PROGRAM. . . . . . . . . . . 26

20 3839 PLUG-IN UNIT IN WRONG TRACK. . . . . . . . . . . . . . . . . . . . . . . 28

21 3840 SEVERAL PLUG-IN UNITS NOT FOUND . . . . . . . . . . . . . . . . . . 29

22 3843 PARITY ERROR IN MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

23 3849 SCSI HARDWARE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

24 3851 HMILIB READ ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

25 3852 CABLE OR UNIT FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

26 3853 ABNORMAL EXCEPTION IN TEST PROGRAM . . . . . . . . . . . . . 35

27 3854 FAULTY UNIT IN HMILIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

28 3856 SYNCHRONIZATION INPUT FAILURE . . . . . . . . . . . . . . . . . . . . 37



4 DN99580889

Issue 07


Id:0900d805807dba50

Confidential

29 3857 FAILURE IN NETWORK INTERFACE UNIT. . . . . . . . . . . . . . . . . 38

30 3858 PLUG-IN UNIT NOT PRESENT . . . . . . . . . . . . . . . . . . . . . . . . . . 39

31 3862 CO-UNIT CONNECTION FAILURE. . . . . . . . . . . . . . . . . . . . . . . . 40

32 3863 OPTICAL MODULE FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

33 3864 UNIT IN WRONG ROLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

34 3865 ETHERNET CABLE UNPLUGGED. . . . . . . . . . . . . . . . . . . . . . . . 45

35 3875 PCIE CABLE IN WRONG POSITION . . . . . . . . . . . . . . . . . . . . . . 46

36 3876 HDS-C FAULT OR PCIE CABLE MISSING . . . . . . . . . . . . . . . . . 47

37 3877 CRC ERROR IN BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

38 3878 RAM ERROR IN APP3K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

39 3879 WATCHDOG ERROR IN TEST. . . . . . . . . . . . . . . . . . . . . . . . . . . 50

40 3990 DIAGNOSIS PATH FAILURE - DIAGNOSIS JOB ABORTED. . . . 51

41 3991 INTERRUPTED DIAGNOSIS JOB COMPLETED. . . . . . . . . . . . . 52

42 3992 DIAGNOSIS JOB ABORTED - UNIT NOT IN TEST STATE. . . . . 53

43 3993 DIAGNOSIS OF UNIT LEFT UNFINISHED. . . . . . . . . . . . . . . . . . 54

44 3994 DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED . . . . 55

45 3995 DIAGNOSIS PROGRAM TOTAL TIME OUT - DIAGNOSIS JOB

ABORTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

46 3996 PARTIAL DIAGNOSIS EXECUTED . . . . . . . . . . . . . . . . . . . . . . . 58

47 3997 PLUG IN UNIT DIAGNOSIS EXECUTED . . . . . . . . . . . . . . . . . . . 59

48 3998 DIAGNOSIS EXECUTED - UNIT NOT OK . . . . . . . . . . . . . . . . . . 60

49 3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK . . . . . . . . . . . . . . . . 61



DN99580889

Issue 07

5

IPA-RNC Diagnosis Reports (3700-3999) Summary of changes

Id:0900d805807dba4f

Confidential

Summary of changesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 06A and 07

New diagnosis reports

Modified diagnosis reports

Changes made between issues 06 and 06A

Modified diagnosis reports

Changes made between issues 5-0 and 06

New diagnosis reports

3875 3877 3879

3876 3878

3851 3852 3853 3857

3865

3865



6 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

List of diagnosis reports

1 List of diagnosis reports3725 DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITS

3726 NO RESPONSE FROM UNIT3727 COMMUNICATION ERROR WITH UNIT

3728 UNIT ACCUSED BY RECOVERY - NO DIAGNOSTICS FOR UNIT

3734 INPUT DATA MISMATCH IN TEST PROGRAM

3735 INTERNAL DATA MISMATCH IN TEST PROGRAM

3736 INTERNAL ERROR IN TEST PROGRAM

3749 HARDWARE CONFIGURATION MISMATCH


3752 UNIT TESTING PREVENTED - UNIT NOT IN TEST STATE SET BY

SYSTEM3760 FAILURE IN MEMORY SPACE

3761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIPMENT

DATABASE DATA

3764 FAILURE IN I/O SPACE

3780 ADDRESSING FAILURE IN MEMORY SPACE

3800 TIME OUT IN TEST PROGRAM

3822 SCSI EQUIPMENT FAILURE

3830 UNSUCCESSFUL HWILIB INQUIRY

3835 MODULE LOADING ERROR IN TEST PROGRAM3839 PLUG-IN UNIT IN WRONG TRACK

3840 SEVERAL PLUG-IN UNITS NOT FOUND

3843 PARITY ERROR IN MEMORY

3849 SCSI HARDWARE FAILURE

3851 HMILIB READ ERROR

3852 CABLE OR UNIT FAILURE

3853 ABNORMAL EXCEPTION IN TEST PROGRAM

3854 FAULTY UNIT IN HMILIB

3856 SYNCHRONIZATION INPUT FAILURE

3857 FAILURE IN NETWORK INTERFACE UNIT

3858 PLUG-IN UNIT NOT PRESENT

3862 CO-UNIT CONNECTION FAILURE

3863 OPTICAL MODULE FAILURE

3864 UNIT IN WRONG ROLE

3865 ETHERNET CABLE UNPLUGGED

3875 PCIE CABLE IN WRONG POSITION

3876 HDS-C FAULT OR PCIE CABLE MISSING

3877 CRC ERROR IN BIOS



DN99580889

Issue 07

7

IPA-RNC Diagnosis Reports (3700-3999) List of diagnosis reports

Id:0900d805807dba4f

Confidential

3878 RAM ERROR IN APP3K

3879 WATCHDOG ERROR IN TEST

3990 DIAGNOSIS PATH FAILURE - DIAGNOSIS JOB ABORTED

3991 INTERRUPTED DIAGNOSIS JOB COMPLETED

3992 DIAGNOSIS JOB ABORTED - UNIT NOT IN TEST STATE

3993 DIAGNOSIS OF UNIT LEFT UNFINISHED

3994 DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED

3995 DIAGNOSIS PROGRAM TOTAL TIME OUT - DIAGNOSIS JOB

ABORTED

3996 PARTIAL DIAGNOSIS EXECUTED

3997 PLUG IN UNIT DIAGNOSIS EXECUTED

3998 DIAGNOSIS EXECUTED - UNIT NOT OK

3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK



8 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3725 DIAGNOSIS MESSAGE - ACCUSED PLUG-INUNITS

2 3725 DIAGNOSIS MESSAGE - ACCUSED

PLUG-IN UNITS

Meaning

A diagnosis report containing those plug-in units in which

a failure has been detected. In the diagnosis report, the

plug-in unit type, place of the subrack in the exchange and the

track number have been listed.

Supplementary information fields

Instructions

Description of the report is in the instructions on diagnostics

and testing.

Replace the plug-in units suspected faulty.

Cancelling

This is a diagnosis report, it is not cancelled.



DN99580889

Issue 07

9

IPA-RNC Diagnosis Reports (3700-3999) 3726 NO RESPONSE FROM UNIT

Id:0900d805807dba4f

Confidential

3 3726 NO RESPONSE FROM UNIT

Meaning

DGTPRO has not received any acknowledgement to the diagnosticprogram start-up message it has sent to the functional unit which

is the object of the report. The program block of the diagnostic

programs of the unit has not been created, or the unit is so faulty

that it cannot respond or the communications to the unit has been

disturbed by a fault in another unit.


Instructions

If the diagnostic job has been originated by the system

and unit in question is under monitoring (i.e. unit has MONI-

status on) system will run diagnostic again after a while. You

should wait if response is got this time.

If no response from unit report is printed again or the diagnostic

job has been originated by user, chech with command USI that the

state of the unit in question is TE-EX and reactivate the unit

diagnosis with the command UDU.

If this does not help, replace the plug-in unit of the functional

unit and run diagnostics for this unit. If there is a responsethis time the removed plug-in unit is most likely faulty.

If there is still no response, the removed plug-in unit might not

have any fault at all but the problem is elsewhere in the system.

You should start diagnosing other functional units of the system

such as switching, multiplexing and other units closely connected

to the functional unit originally diagnosed. This may also include

switchovers of the units, replacing plug-in units and possibly

cables and repeating the diagnostics also for the functional

unit originally diagnosed until a response is received.

Cancelling




10 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3727 COMMUNICATION ERROR WITH UNIT

4 3727 COMMUNICATION ERROR WITH UNIT

Meaning

An error in the message exchange between the DGTPRO program blockand diagnostic program (functional unit to be diagnosed).


Instructions

Restart the unit with the RESET button and reactivate the unit

diagnosis with the command UDU. If this does not help, locate the

failure by replacing the plug-in unit of the functional unit to

be diagnosed.

Cancelling




DN99580889

Issue 07

11

IPA-RNC Diagnosis Reports (3700-3999) 3728 UNIT ACCUSED BY RECOVERY - NO DIAG-NOSTICS FOR UNIT

Id:0900d805807dba4f

Confidential

5 3728 UNIT ACCUSED BY RECOVERY - NO

DIAGNOSTICS FOR UNIT

Meaning

The RCXPRO program block has given to the DGTPRO program block a

diagnosis command of such a unit which does not (yet) have any

diagnostic programs in the system. The recovery command is a

normal action of automatic fault location.


Instructions

Diagnose the unit by other means (for example by examining the

alarm print-outs).

Cancelling




12 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3734 INPUT DATA MISMATCH IN TEST PROGRAM

6 3734 INPUT DATA MISMATCH IN TEST

PROGRAM

Meaning

The diagnostic program has detected that the data used in the

test start-up is erroneous. The data is contradictory either

with itself or with a parameter outside the test.


1 N/A

2 N/A

Instructions

Repeat the test. If the alarm remains unchanged, reload the

files of the DGTPRO program block of the OMU or from the

disk (DGFILE, DGSPRO, DGUTST, NURSES, LEQURI,VIATON). Check the

equipping of the exchange with the EQFADM MML program (command

WF). If the alarm remains unchanged after a new test, fill in

a Problem Report.

Cancelling




DN99580889

Issue 07

13

IPA-RNC Diagnosis Reports (3700-3999) 3735 INTERNAL DATA MISMATCH IN TEST PRO-GRAM

Id:0900d805807dba4f

Confidential

7 3735 INTERNAL DATA MISMATCH IN TEST

PROGRAM

Meaning

The diagnostic program has detected an error in its own

internal data tables. The data is contradictory either with

itself or with a parameter outside the test.


1 N/A

2 N/A

Instructions

Repeat the test. If the alarm remains the same, fill in

a Problem Report.

Cancelling




14 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3736 INTERNAL ERROR IN TEST PROGRAM

8 3736 INTERNAL ERROR IN TEST PROGRAM

Meaning

The diagnostic program has detected an error in its internalfunction. The error has not been caused by the malfunction of

the equipment tested, the external data used in the test

start-up, or the internal fixed data of the test program.


1 N/A

2 N/A

Instructions

Repeat the test. If the alarm remains the same, fill in

a Problem Report.

Cancelling




DN99580889

Issue 07

15

IPA-RNC Diagnosis Reports (3700-3999) 3749 HARDWARE CONFIGURATION MISMATCH

Id:0900d805807dba4f

Confidential

9 3749 HARDWARE CONFIGURATION

MISMATCH

Meaning

The diagnostic program is unable to obtain from the equipment

database data on one or more plug-in units, or the search fails

outright.


1 N/A

2 N/A

Instructions

Use the EQFADM MML program (command WF) to check if there are

any supernumerary plug-in units in the subrack. Restart the unit

with the USU command. Start a total diagnosis, using the UDU

command. If the fault persists, fill in a Problem Report.

Cancelling




16 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential


10 3750 HARDWARE CONFIGURATION

MISMATCH

Meaning

The diagnostic program is unable to obtain from the equipment

database data on one or more plug-in units, or the search fails

outright.


1 N/A

2 N/A

Instructions

Use the EQFADM MML program (command WF) to check if there are

any supernumerary plug-in units in the subrack. Restart the unit

with the USU command. Start a total diagnosis, using the UDU

command. If the fault persists, fill in a Problem Report.

Cancelling




DN99580889

Issue 07

17

IPA-RNC Diagnosis Reports (3700-3999) 3752 UNIT TESTING PREVENTED - UNIT NOT INTEST STATE SET BY SYSTEM

Id:0900d805807dba4f

Confidential

11 3752 UNIT TESTING PREVENTED - UNIT NOT

IN TEST STATE SET BY SYSTEM

Meaning

Diagnostic program cannot test a functional unit because its

working state has not been changed to test state by the recovery

system.


Instructions

No special instructions.

Cancelling

This is a diagnostic report, it is not cancelled.



18 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3760 FAILURE IN MEMORY SPACE

12 3760 FAILURE IN MEMORY SPACE

Meaning

In the RAM test, a failure has been detected in the unbanked memory.


1 address in which the failure was detected (upper word)

2 address in which the failure was detected (lower word)

Instructions

Replace the CPU plug-in unit and after the replacing,

restart the RAM partial diagnosis with the command UDU.

Cancelling




DN99580889

Issue 07

19

IPA-RNC Diagnosis Reports (3700-3999) 3761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIPMENT DATABASE DATA

Id:0900d805807dba4f

Confidential

13 3761 DIFFERENCE BETWEEN MEMORY

SPACE AND THE EQUIPMENT DATABASE

DATAMeaning

The size of the memory space obtained in the RAM test from the

equipment database is inconsistent with the actual size of the memory.


1 address where fault was detected (upper word)

2 address where fault was detected (lower word)

Instructions

Check whether the memory space given in the equipment list

corresponds to the actually existing memory space (EQFADM MML

command WFI). If not, correct the error in the list and then

restart the unit with the USU command. Finally start the RAM

partial diagnosis (again), using the UDU command.

Cancelling




20 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3764 FAILURE IN I/O SPACE

14 3764 FAILURE IN I/O SPACE

Meaning

In the SYSB bus test, a failure has been detected in the I/Ospace. There is an extra plug-in unit in the I/O space, an

addressing failure in a plug-in unit of the I/O space, or the

unit's I/O address data does not correspond to the equipment database.


1 address in which the failure was detected

2 N/A

Instructions

Check the contents of the equipment database with the EQFADM

MML program (command WF). Check if there are any extra plug-in

units in the subrack. Replace the plug-in units on the SYSB

bus one by one (you can output the plug-in units with

the UDI command), and after having replaced each plug-in

unit, start up the SYSB partial diagnosis with the UDU command.

Cancelling




DN99580889

Issue 07

21

IPA-RNC Diagnosis Reports (3700-3999) 3780 ADDRESSING FAILURE IN MEMORY SPACE

Id:0900d805807dba4f

Confidential

15 3780 ADDRESSING FAILURE IN MEMORY

SPACE

Meaning

In the RAM test, an addressing failure has been detected.

A CPU plug-in unit does not identify its own address or identifies

an incorrect address or is faulty.


1 address in which the failure was detected (upper word)

2 address in which the failure was detected (lower word)

Instructions

Replace the CPU plug-in unit and after the replacing,

restart the RAM partial diagnosis with the command UDU.

Cancelling




22 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3800 TIME OUT IN TEST PROGRAM

16 3800 TIME OUT IN TEST PROGRAM

Meaning

The diagnostic program does not receive a reply to the message ithas sent, which results in a time-out.


1 message bus address

2 family identifier

Instructions

Restart the program block of the computer (supplementary information

fields 2 and 1 respectively), if this can be done without interfering

with the function of the exchange.

Cancelling




DN99580889

Issue 07

23

IPA-RNC Diagnosis Reports (3700-3999) 3822 SCSI EQUIPMENT FAILURE

Id:0900d805807dba4f

Confidential

17 3822 SCSI EQUIPMENT FAILURE

Meaning

A diagnosis program has detected a fault in the terminalresistors of the SCSI bus, in the cable, or in the SCSIF

plug-in unit.


1 error code:

01 the presence signal, corresponding to the

SCSI address of the device, is passive

02 device does not respond

03 the fuse of the terminal resistor's supply voltage has blown

04 terminal resistor supply voltage overload

05 one or both terminal resistors are missing

2 number of the SCSI bus:

00 SCSI bus 0, upper connector on the SCSIF

01 SCSI bus 1, lower connector on the SCSIF

Instructions

If error code = 01:

Check that the strapping on the jumper group of the

Disk Drive Adapter (DDAD) is compatible with the SCSI

address of the device. Check also the address: 0 for

the WDU and 2 for the FDU.

If the addresses are correct, follow the instructions for

error code 02.

If error code = 02:

Check that the strappings on the jumper groups of all the Disk Drive Adapters (DDAD, WDAD, FDAD or CTAD) connected to

the SCSI bus concerned correspond to the SCSI address of the

device concerned.

If the fault persists, replace the terminal resistors

(SCSIT) of the SCSI bus.

If the fault still persists, replace the SCSI cable (CFH).

If the fault still persists, replace the mass memory unit.

If the fault still persists, replace the SCSIF plug-in unit,



24 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3822 SCSI EQUIPMENT FAILURE

see instructions for replacing plug-in units.

If error code = 03 or 04:

Replace both terminal resistors (SCSIT), the SCSI cable (CFH),

and the SCSIF plug-in unit, also in the backup computer unit

if it is a double one, see Instructions for Replacing

Plug-in Units.

If error code = 05:

Check that both terminal resistors are in place. If

the fault persists, proceed as instructed for error

code 02.

Cancelling




DN99580889

Issue 07

25

IPA-RNC Diagnosis Reports (3700-3999) 3830 UNSUCCESSFUL HWILIB INQUIRY

Id:0900d805807dba4f

Confidential

18 3830 UNSUCCESSFUL HWILIB INQUIRY

Meaning

The HWILIB inquiry was unsuccessful.


1 lower word of the status restored by HWILIB

2 upper word of the status restored by HWILIB

Instructions

Check that the plug-in units needed by partial diagnostics are

equipped correctly and exist in the equipment database.

Cancelling




26 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3835 MODULE LOADING ERROR IN TEST PRO-GRAM

19 3835 MODULE LOADING ERROR IN TEST

PROGRAM

Meaning

Loading a loadable test program has failed.


1 the most meaningful part of the error status of

message 0X0E164

2 the least meaningful part of the error status of

message 0X0E164

Instructions

Start the message monitoring of the DOCTOR process with the

service terminal command ZOQ:D9 and run the partial diagnosis

wanted.

Observe the field load_module_name, whose length is eight

ascii characters, of the message 0x837. This field contains

the name of the module to be loaded, without the extension.

For example, the module DISA71GX is presented in the message

in hexadecimals 44 49 53 41 37 31 47 58. All loadable modules

of the diagnostic programs should begin with the string DIS,i.e. the field load_module_name can be located in the message

by searching for the hexadecimals 44, 49 and 53.

Give the service terminal command ZMX:W0-BLCODE/DIS* to check

whether the name of the module found in the message, with the

extension IMG, is located on the disk W0 of the exchange.

Perform the same checking for disk W1.

If the disks do not contain a message with the same name as in

the message 0x837, fill in a Problem Report. The failure is

then located either in the file LEQURI, whose number is

07F10000, or on disks W0 or W1.

If the disks do contain a message with the same name as in the

message 0x837, but the text diagnosis 0x3835 is still given,

fill in a Problem Report. In that case the failure is in the

loading system.

The ascii characters representing decimals and upper-case

alphabets are presented in the following table in hexadecimals:

decimal ascii alphabet ascii alphabet ascii

0 0x30 A 0x41 N 0x4E 1 0x31 B 0x42 O 0x4F



DN99580889

Issue 07

27

IPA-RNC Diagnosis Reports (3700-3999) 3835 MODULE LOADING ERROR IN TEST PRO-GRAM

Id:0900d805807dba4f

Confidential

2 0x32 C 0x43 P 0x50

3 0x33 D 0x44 Q 0x51

4 0x34 E 0x45 R 0x52

5 0x35 F 0x46 S 0x53

6 0x36 G 0x47 T 0x54

7 0x37 H 0x48 U 0x55

8 0x38 I 0x49 V 0x56

9 0x39 J 0x4A W 0x57

K 0x4B X 0x58

L 0x4C Y 0x59

M 0x4D Z 0x5A

Cancelling




28 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3839 PLUG-IN UNIT IN WRONG TRACK

20 3839 PLUG-IN UNIT IN WRONG TRACK

Meaning

Diagnostic program has detected that a plug-in unit is not in thetrack indicated by the equipment database.


1 track where the plug-in unit is

2 plug-in unit type number

Instructions

Check the equipment description with the EQFADM MML, command class

WF. Move the plug-in unit into the right track.

Cancelling




DN99580889

Issue 07

29

IPA-RNC Diagnosis Reports (3700-3999) 3840 SEVERAL PLUG-IN UNITS NOT FOUND

Id:0900d805807dba4f

Confidential

21 3840 SEVERAL PLUG-IN UNITS NOT FOUND

Meaning

The diagnostic program has detected that two or moreplug-in units are missing or are not in the track

indicated by the equipment database.


1 the first track from where the diagnostic program

did not find the right kind of plug-in unit

2 N/A

Instructions

1. Check the equipment description using the WT command

group commands.

2. Install the plug-in units in right tracks.

3. Run the unit diagnostic program using the UDU command.

4. Repeat steps 2. and 3. if the system generates the diagnosis

3840 SEVERAL PLUG-IN UNITS NOT FOUND again.

Cancelling




30 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3843 PARITY ERROR IN MEMORY

22 3843 PARITY ERROR IN MEMORY

Meaning

The system has detected a parity error in a RAM test.


1 N/A

2 N/A

Instructions

Replace the CPU plug-in unit and then start the RAM partial

diagnosis with the MML command UDU.

Cancelling




DN99580889

Issue 07

31

IPA-RNC Diagnosis Reports (3700-3999) 3849 SCSI HARDWARE FAILURE

Id:0900d805807dba4f

Confidential

23 3849 SCSI HARDWARE FAILURE

Meaning

The diagnosis program has detected a fault in the terminalresistances, the cable, the mass memory unit or the CP plug-in

unit of the SCSI bus.


1 error code:

This is a general error code of the system. You can check its

meaning in General Error Messages of the System.

2 number of SCSI bus:

00 SCSI bus 0

01 SCSI bus 1

Instructions

Check that the terminal resistances and cables of the SCSI bus

are properly plugged.

Check that all the mass memory slots of the mass memory cartridge

contain a mass memory adapter.

Check the power supply of the mass memory unit.

If the fault is not cleared, change the terminal resistances of the

SCSI bus.

If the fault is not cleared, change the SCSI cable.

If the fault is not cleared, change the mass memory unit.

If the fault is not cleared, change the CP plug-in unit. Seeinstructions for changing plug-in units.

2.4.

Note that also some other piece of equipment in the SCSI bus can

be faulty and disturb the operation of the equipment in the bus.

This also applies to a faulty CP plug-in unit in the parallel

computer.

Cancelling




32 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3851 HMILIB READ ERROR

24 3851 HMILIB READ ERROR

Meaning

HMILIB has given nok status to hms_diagnostics call.HMILIB has not been able to allocate buffer or HMILIB has

not been able to read the hms system configuration.


1 lower word of the status restored by HMILIB

2 upper word of the status restored by HMILIB

Instructions

Check that the plug-in units needed by partial diagnostics are

equipped correctly and exist in the equipment database.

Cancelling

This is a diagnostic printout, it is not cancelled.



DN99580889

Issue 07

33

IPA-RNC Diagnosis Reports (3700-3999) 3852 CABLE OR UNIT FAILURE

Id:0900d805807dba4f

Confidential

25 3852 CABLE OR UNIT FAILURE

Meaning

The diagnosis program's interface test has detected a fault. According tofailure detection principles the system accuses the diagnosed unit of

being faulty. However, due to the character of the interface test, one

cannot be sure whether the fault lies in the cable, in the diagnosed unit

or in the remote end unit that is connected to the other end of the

cable.


1 meaning of this supplementary information depends on failed partial

diagnosis and functional unit

- IP unit's ATNI partial diagnosis:

bit mask of failed ports

- other partial diagnosis:

remote end functional unit type,

10C = MXU

151 = SFU

146 = NIS1

10F = NIS1P

118 = IPGO

119 = IPGOP 113 = IPFE

117 = IPFEP

114 = IPGE

115 = IPGEP

11E = NPS1

11F = NPS1P

11C = NPGE

11D = NPGEP

2 meaning of this supplementary information depends on failed partial

diagnosis and functional unit

- IP unit's partial diagnosis ATNI:

always 1


remote end functional unit index in hexadecimal form

Instructions

instruction depends on failed partial diagnosis and functional unit

- IP unit's partial diagnosis ATNI:



34 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3852 CABLE OR UNIT FAILURE

1. Check that the Ethernet cables connected to accused plug-in unit are in

working order and correctly installed at each ends

2. Replace the accused plug-in unit with a new one and repeat the test

3. Replace the remote end plug-in unit with a new one and repeat the test

4. Contact the local Nokia Customer Service Center if the fault can't be

solved


1. Check that the Network Element internal ATM cable is in working order

and correctly installed at each ends

2. Replace the remote end plug-in unit described in INFO_1 with a new one

and repeat the test

3. Replace the accused plug-in unit with a new one and repeat the test

4. Contact the local Nokia Customer Service Center if the fault can't be

solved

Cancelling




DN99580889

Issue 07

35

IPA-RNC Diagnosis Reports (3700-3999) 3853 ABNORMAL EXCEPTION IN TEST PROGRAM

Id:0900d805807dba4f

Confidential

26 3853 ABNORMAL EXCEPTION IN TEST

PROGRAM

Meaning

The system cannot carry out the service request made by a

diagnosis program. This can be caused e.g. by a possible overload

situation or a NOK status in an acknowledgement message or

library call. The computer log may contain further information.


1 lower word of the status restored by HMILIB

2 upper word of the status restored by HMILIB

Instructions

1. Repeat the test.

2. Contact Customer Service Center if diagnostic interrupts again.

Collect WO-EX OMU's and test unit's logs.

Cancelling




36 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3854 FAULTY UNIT IN HMILIB

27 3854 FAULTY UNIT IN HMILIB

Meaning

The diagnostic program has found faulty unit in HMILIB


1 HMS address of piu, rack

2 HMS address of piu, subrack and position

Instructions

Replace the accused plug-in unit.

Cancelling

This is a diagnostic print-out, it is not cancelled.



DN99580889

Issue 07

37

IPA-RNC Diagnosis Reports (3700-3999) 3856 SYNCHRONIZATION INPUT FAILURE

Id:0900d805807dba4f

Confidential

28 3856 SYNCHRONIZATION INPUT FAILURE

Meaning

The diagnosis program's clock system test has detected a fault.The fault is not in the diagnosed unit but in one of the synchronization

inputs. In the case that the accused synchronization input has been

connected to the diagnosed unit, the unit under test can be faulty.

However, one cannot be sure whether the fault lies in the cable, in the

synchronization signal or in the signal receiver.


1 type of synchronization input:

5CB = EXT input of TSS3

5CD = SDH Exchange Terminal 5CE = PDH Exchange Terminal

14 = Exchange terminal

2 index of synchronization input

Instructions

1. Check that the cable is in working order and correctly installed.

2. Connect the accused synchronization signal to another connector of

the unit and repeat the test. Remember to modify the reference

parameters by using the DYM MML.

3. Check that the synchronization input that has a priority value is in working order and correctly installed. The missing synchronization

input cannot have entered parameters.

The synchronization input information can be checked by using the

DYI MML and the parameters of the synchronization inputs can be

modified by using the DYM MML.

4. Replace the plug-in unit delivering the accused synchronization input

to the network element and repeat the test.

5. If the alarm persists, make a problem report.

Cancelling

This is a diagnosis report. No cancelling.



38 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3857 FAILURE IN NETWORK INTERFACE UNIT

29 3857 FAILURE IN NETWORK INTERFACE

UNIT

Meaning

The diagnosis program's clock system test has detected a

fault. The fault is not in the diagnosed unit but in one

of the units that delivers the synchronisation inputs to

the network element.


1 type of network interface unit

2 index of network interface unit

Instructions

1. Replace the plug-in unit delivering the synchronisation

inputs to the network element and repeat the test.

2. If the alarm persists, make a problem report.

Cancelling

This is a diagnosis report. No cancelling.



DN99580889

Issue 07

39

IPA-RNC Diagnosis Reports (3700-3999) 3858 PLUG-IN UNIT NOT PRESENT

Id:0900d805807dba4f

Confidential

30 3858 PLUG-IN UNIT NOT PRESENT

Meaning

Diagnostic program has detected that the plug-in unit is not present insystem or HMS node of plug-in unit is broken.


1 Contains plug-in unit row position and subrack of hms address.

2 Contains rack position of hms address.

Instructions

In case of plug-in unit not present in system insert plug-in unit to

subrack.

In case of plug-in unit present in system replace plug-in unit.

Cancelling




40 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3862 CO-UNIT CONNECTION FAILURE

31 3862 CO-UNIT CONNECTION FAILURE

Meaning

The diagnosis program's co-unit connection test has detected a faultin the internal connection between the network interface units

protecting each other.


1 reason of the failure:

00 no reason available for failure

01 HW failure in the tested unit

02 HW failure in a co-unit

03 HW failure in both units 04 failure in protection switch cables between the tested unit

and a co-unit

05 incorrect cabling of protection switch cables between

the tested unit and a co-unit

06 number of bit errors in the connection is too high

2 additional information from the nature of the failure:

00 no additional information available

01 direction from the tested unit to a co-unit is not working

02 direction from a co-unit to the tested unit is not working

03 both directions are not working

Instructions

If the reason of the failure is 01, change the plug-in unit of

the tested functional unit. Re-run the fault diagnosis for

the functional unit.

If the reason of the failure is 02, change the plug-in unit of

the co-unit. Re-run the fault diagnosis for the functional unit.

If the reason of the failure is 03, change the plug-in units ofboth units. Re-run the fault diagnosis for both functional units.

If the reason of the failure is 04, make sure that the protection switch

cables are in place and that those are in order. If that does not help,

make sure that the backplane pins of both plug-in unit positions are

straight. Re-run the fault diagnosis for the functional unit.

If the reason of the failure is 05, make sure that the connectors of

the protection switch cables are correctly connected. Re-run the fault

diagnosis for the functional unit.

If the reason of the failure is 06, make sure that the connectors of



DN99580889

Issue 07

41

IPA-RNC Diagnosis Reports (3700-3999) 3862 CO-UNIT CONNECTION FAILURE

Id:0900d805807dba4f

Confidential

the protection switch cables are properly in place and that the contact

interfaces are clean. Re-run the fault diagnosis for the functional

unit.

If the failure persists, contact the local Nokia Siemens Networks

representative.

Cancelling

This is a fault diagnosis report, it is not cancelled.



42 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3863 OPTICAL MODULE FAILURE

32 3863 OPTICAL MODULE FAILURE

Meaning

The diagnosis program's optical module test has detected faulty and/orwrong type of optical module or modules.


1 location information of failed optical module or modules:

The field is bit coded and it provides the information of which

optical modules have failed. A binary value 1 of a bit indicates

that there is a failure in an optical module. The position number

of the active bit from left to right (values from 1 to 16)

indicates the position number of the failed optical module from top to bottom.

2 location information of wrong type of optical module or modules:

The field is bit coded and it provides the information of which

optical modules are of wrong type. A binary value 1 of a bit

indicates that the type of an optical module is wrong. The position

number of the active bit from left to right (values from 1 to 16)

indicates the position number of the failed optical module from

top to bottom.

Instructions

Convert the hexadecimal values of the location information fields to

binary format. From the converted values you can see how many optical

modules have failed to pass the fault diagnosis or how many optical

modules are of wrong type (the total number of binary 1s will indicate

this). The location of the binary 1s in the value will tell which

optical module or modules should be changed (see more instructions about

the value interpretation from the field descriptions part). Change the

needed optical modules with new ones and rerun the fault diagnosis.

If the failure persists, contact the local Nokia Siemens Networksrepresentative.

For example: Hexadecimal value 84 of location information field of

failed optical module is in binary format 10000100. Because there are

two bits with value 1, it means that there are two failed optical

modules. The first bit from the left has value 1 which means that

the first optical module from the top has failed and should be

replaced with a new one. In the same way, the sixth bit from the left

has value 1 which means that the sixth optical module from the top has

failed and should be replaced with a new one.



DN99580889

Issue 07

43

IPA-RNC Diagnosis Reports (3700-3999) 3863 OPTICAL MODULE FAILURE

Id:0900d805807dba4f

Confidential

Cancelling




44 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3864 UNIT IN WRONG ROLE

33 3864 UNIT IN WRONG ROLE

Meaning

The unit which is to be diagnosed is in a wrong role


1 Role of the unit which is to be diagnosed

combi_c = 1;

mgw_c = 2;

stand_alone_c = 3;

remote_c = 4;

unknown_c = 0xf0;

init_c = 0xfe;

Instructions

The units, the role of which is info_1, cannot be diagnosed in this

release.

Cancelling




DN99580889

Issue 07

45

IPA-RNC Diagnosis Reports (3700-3999) 3865 ETHERNET CABLE UNPLUGGED

Id:0900d805807dba4f

Confidential

34 3865 ETHERNET CABLE UNPLUGGED

Meaning

The cable of the Ethernet interface in this unit is unplugged. In mostcases, 3240 alarm can be found when getting this diagnosis report.

See alarm 3240 instructions for more information about the failed

Ethernet interface.


Instructions

Check and plug the Ethernet interface cable.

Cancelling

This is a fault diagnosis report; it is not cancelled.



46 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3875 PCIE CABLE IN WRONG POSITION

35 3875 PCIE CABLE IN WRONG POSITION

Meaning

A diagnosis program has detected that location information of thePCIe cable between OMU and HDS-C unit does not match information in

the hardware configuration.


Instructions

Check that the PCIe port number in CPU and HDS-C unit matches the

port numbers in hardware configuration. If not, change the PCIe

cable location and hardware configuration to match each other.

Cancelling




DN99580889

Issue 07

47

IPA-RNC Diagnosis Reports (3700-3999) 3876 HDS-C FAULT OR PCIE CABLE MISSING

Id:0900d805807dba4f

Confidential

36 3876 HDS-C FAULT OR PCIE CABLE

MISSING

Meaning

A diagnosis program has detected that there is a problem in

connection between OMU and HDS-C unit.


Instructions

Check that the PCIe cable between OMU and HDS-C unit is attached

properly and its location matches the hardware configuration.

If the fault still persists, replace the PCIe cable.

If the fault still persists, replace the HDS-C unit

Cancelling




48 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3877 CRC ERROR IN BIOS

37 3877 CRC ERROR IN BIOS

Meaning

The diagnosis program's BIOS test has detected CRC error on eitherdefault BIOS or backup BIOS.


1 diagnosis result for BIOS0

0: BIOS0 has no CRC error

1: BIOS0 has CRC error

2 diagnostic result for BIOS1

0: BIOS1 has no CRC error

1: BIOS1 has CRC error

Instructions

The error can be caused by plug-in unit's HW fault or just BIOS image's

corruption.

User need investigate and fix the fault based on diagnostic report:

1. Check which BIOS has CRC error.

2. Update the corrupted BIOS via MML command group WD.

See instructions on BIOS update and recovery.

3. Re-run BIOS diagnosis on the functional unit via MML command UDU.

4. If the error persists, replace the plug-in unit with a new one and

re-run the BIOS diagnosis.

5. If the error persists, contact the local Nokia Siemens Networks

representative.

Cancelling




DN99580889

Issue 07

49

IPA-RNC Diagnosis Reports (3700-3999) 3878 RAM ERROR IN APP3K

Id:0900d805807dba4f

Confidential

38 3878 RAM ERROR IN APP3K

Meaning

The system has detected a ram error in a APP3K test.


1 N/A

2 N/A

Instructions

app3k diagnosis with the MML command UDU.

Cancelling




50 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3879 WATCHDOG ERROR IN TEST

39 3879 WATCHDOG ERROR IN TEST

Meaning

The system has detected a watchdog error in test.


1 N/A

2 N/A

Instructions

watchdog diagnosis with the MML command UDU.

Cancelling




DN99580889

Issue 07

51

IPA-RNC Diagnosis Reports (3700-3999) 3990 DIAGNOSIS PATH FAILURE - DIAGNOSIS JOB ABORTED

Id:0900d805807dba4f

Confidential

40 3990 DIAGNOSIS PATH FAILURE - DIAGNO-

SIS JOB ABORTED

Meaning

Because of a diagnosis path error, the diagnosis has had to be

interrupted. The diagnosis path means those units which have

to be in order and in the same state for the duration of the

diagnosis.


Instructions

No action required.

Cancelling




52 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3991 INTERRUPTED DIAGNOSIS JOB COMPLETED

41 3991 INTERRUPTED DIAGNOSIS JOB COM-

PLETED

Meaning

An interrupted diagnosis task has been completed. DGTPRO is free to

execute the next task. The cause for the interruption was either a

user command or a decision of DGTPRO.


Instructions

No action required.

Cancelling




DN99580889

Issue 07

53

IPA-RNC Diagnosis Reports (3700-3999) 3992 DIAGNOSIS JOB ABORTED - UNIT NOT INTEST STATE

Id:0900d805807dba4f

Confidential

42 3992 DIAGNOSIS JOB ABORTED - UNIT NOT

IN TEST STATE

Meaning

DGTPRO refuses to test a functional unit that is not in test state.


Instructions

No action required.

CancellingThis is a diagnosis report, it is not cancelled.



54 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3993 DIAGNOSIS OF UNIT LEFT UNFINISHED

43 3993 DIAGNOSIS OF UNIT LEFT UNFINISHED

Meaning

DGTPRO was restarted during diagnosis.


Instructions

Set the unit whose diagnosis was interrupted into the test state

and initiate its total test with the command UDU.

Cancelling




DN99580889

Issue 07

55

IPA-RNC Diagnosis Reports (3700-3999) 3994 DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED

Id:0900d805807dba4f

Confidential

44 3994 DATA MISMATCH IN FILES - DIAGNO-

SIS JOB ABORTED

Meaning

Diagnostic files are in contradiction or otherwise erroneous.


1 failure code:

1 general file error

2 start-up error of diagnostic program

3 unit executing the diagnostic program is not found

4 program block executing diagnostic programs does not recognize

the diagnostic program

5 data on hardware not found in equipment database

6 exchange configuration does not include a diagnostic program to

be executed for the functional unit concerned

7 semantic error

2 main number of file

3 variant of file

Instructions

Action Note

---------------------------------------------------------------

-------------

START

o

!

+---o1 1. Reload diagnostic files from

DFM:OMU:104;

! ! disk.

DFM:OMU:105;

! !

DFM:OMU:107;

! !

DFM:OMU:7F0;

! !

DFM:OMU:7F1;

! !

DFM:OMU:8E0; ! !



56 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3994 DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED

! !

! o2 2. Restart the diagnostic task. UDU

! !

! o3 3. Does the alarm recur?

! ! a: no

oa ob b: yes

! !

o o4 4. Take the back-up disk into use

DFM:OMU:104;

END ! and repeat the file reload.

DFM:OMU:105;

!

DFM:OMU:107;

!

DFM:OMU:7F0;

!DFM:OMU:7F1;

!

DFM:OMU:8E0;

!

!

!

o5 5. Restart the diagnostic task. UDU

!

!

!

+---o6 6. Does the alarm recur? ! ! a: no

oa ob b: yes

! !

! o7 7. Fill in a Problem Report.

o !

END !

o

END




DN99580889

Issue 07

57

IPA-RNC Diagnosis Reports (3700-3999) 3995 DIAGNOSIS PROGRAM TOTAL TIME OUT - DI- AGNOSIS JOB ABORTED

Id:0900d805807dba4f

Confidential

45 3995 DIAGNOSIS PROGRAM TOTAL TIME

OUT - DIAGNOSIS JOB ABORTED

Meaning

The execution of the diagnostic program takes too long or

forever. The error may be in the files of the diagnostic

program family. It is also possible that the unit diagnosed

has restarted during diagnosis. This does not apply to the

restart caused by the watchdog timer test of the CPU

subdiagnosis.


Instructions

Fill in a Problem Report.

Cancelling




58 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3996 PARTIAL DIAGNOSIS EXECUTED

46 3996 PARTIAL DIAGNOSIS EXECUTED

Meaning

Normal intermediate output when no failure has been detected.


Instructions

No action required.

Cancelling




DN99580889

Issue 07

59

IPA-RNC Diagnosis Reports (3700-3999) 3997 PLUG IN UNIT DIAGNOSIS EXECUTED

Id:0900d805807dba4f

Confidential

47 3997 PLUG IN UNIT DIAGNOSIS EXECUTED

Meaning

This is a normal printout after a plug-in unit test, whenno fault has been found.


1 plug-in unit index

Instructions

No action required.

Cancelling




60 DN99580889

Issue 07


Id:0900d805807dba4f

Confidential

3998 DIAGNOSIS EXECUTED - UNIT NOT OK

48 3998 DIAGNOSIS EXECUTED - UNIT NOT OK

Meaning

Testing of the unit has been completed, and the unit has been foundfaulty.


Instructions

No action required.

Cancelling




IPA-RNC Diagnosis Reports (3700-3999) 3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK

49 3999 TOTAL DIAGNOSIS EXECUTED - UNIT

OK

Meaning

The total test has been completed. The unit is in working order.


Instructions

No action required.


Documents

Alm Rnc Diagnosis Reports