Ned Alarms

8/13/2019 Ned Alarms

1/37


2/37

es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 61List of Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 723725 DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITS.. . . . . . . 1033726 NO RESPONSE FROM UNIT. . . . . . . . . . . . . . . . . . .. . . . . . . . . 1143727 COMMUNICATION ERROR WITH UNIT. . . . . . . . . . . .. . . . . . . 1253728 UNIT ACCUSED BY RECOVERY - NO DIAGNOSTICS FOR UNIT 1363729PARITY ERROR BETWEEN SWIF AND SWCL . . . . . . . . . . . . . 1473730 PARITY ERROR BETWEEN SWTST AND SWCL. . . . . . . . . . . . 1583731 SWIF STATUS ERROR . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693733 CONTENTS OF SWCM NOT CORRECT . . . . . . . . . . . . . . . . . . 17103734 INPUT DATA MISMATCHIN TEST PROGRAM . . . . . . . . . . . . . 18113735 INTERNAL DATA MISMATCH IN TEST PROGRAM. . . . . . . . . . 19123736 INTERNAL ERROR IN TEST PROGRAM . . . . .. . . . . . . . . . . . . 20133746 HWALCO COMMUNICATION FAILURE . . . . . . . .. . . . . . . . . . . 21143747 AAL FAILURE. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . 22153749 HARDWARE CONFIGURATION MISMATCH . . . . . . . . . . . . . . . 23163750 HARDWARE CONFIGURATION MISMATCH . . .. . . . . . . . . . . . 24173760 FAILURE IN MEMORY SPACE . . . . . . . . . . . .. . . . . . . . . . . . . . 25183761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIP-MENT DATABASE DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 26193763 PARITY ERROR IN RAM UNIT . . . . . . . . . . . . . . . . .. . . . . . . . . 27203764 FAILURE IN I/O SPACE. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 28213765 FAILURE IN CPU SELF ACKNOWLEDGEMENT . .. . . . . . . . . . 29223766 TG IN MARKER OR PCM ACCUSED . . . . . . . . . . .. . . . . . . . . . 30233767 ET OR PCM ACCUSED. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . 31243768 MFCU OR PCM ACCUSED . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 33253769 PBRU OR PCM ACCUSED . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . 35263770 AONU OR PCM ACCUSED . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 37273771 SUB OR PCM ACCUSED.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39283772 CNFC OR PCMACCUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41293773 SWIPCM ACCUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

4DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0

900d805806fd901

303774 SSW PCM ACCUSED. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .45313775 GSW PCM ACCUSED. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .47323776 LSU OR PCM ACCUSED . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .49333777 DISTURBANCE ON LSU PCM . . . . . . . . . .. . . . . . . . . . . . . . . . .51343778 DIFFERENCE BETWEEN MUFILE AND PIPCMIFILES . . . . . . .53353780 ADDRESSING FAILURE IN MEMORY SPACE . . . . . . . . .. . . . .54363782 DMA TRANSFER FAILURE . . . . . . . . . . . . . . . . . . . .. . . . . . . . .55373784 BUSY PCM LINES. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .56383787 BLOCKED PCM LINES. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .57393790 MSG BUS FAILURE . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .58403791 NO RESPONSE B

EFORE RESET . . . . . . . . . . . . . . . . . . . . . . . .59413792 PCM FILE READ ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60423795 CONNECT ERROR IN SP LINE RECEIVER TEST . . . . . . . . . . .62433798 UNKNOWN ERRORIN SP LINE RECEIVER TEST. . . . . . . . . . .64443799 MESSAGE BUS FAILURE. . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .66453800 TIME OUT IN TESTPROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . .67463801 OTHER WO-EX UNIT NOT AVAILABLE. . . . . . . . . . . . . . . . . . . .68473802 TSUPRO ERROR INTIME SLOT BASED DEVICE TEST . . . . . .69483803 CLB FAILURE . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70493804 UNKNOWN FAULT IN HARDWARE. . . . . . . . . . . . . . . . . . . . . . .71503808 EXECUTION ER


3/37

ROR IN PREPROCESSOR TEST . . . . . . . . . . .73513809 UNSPECIFIED FAILURE IN PREPROCESSOR TEST . . . . . . . .74523810 EXTERNAL LOOP FAILURE IN PREPROCESSOR TEST. . . . . .75533814 LINE PRINTER FAILURE . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .76543815 VISUAL DISPLAY UNIT FAILURE . . . . . . . . . .. . . . . . . . . . . . . .77553818 SBUS FAILURE. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .78563819 CABLE MISSING. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80573821 PREPROCESSOR EXTERNAL LOOP FAILURE. . . . . . . . . . . . .81583822 SCSI EQUIPMENT FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . .83593823 PHASE LOCK FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85603824 DUAL PORT MEMORY FAILURE. . . . . . . . . . . . . . . . . . . . . . . . .86613825HWAT OR CLAB COMMUNICATION FAILURE. . . . . . . . . . . . . .87623826 CLOCK FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

DN99571044Issue 5-05Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)

Id:0900d805806fd901633827 PARTIAL POWER FAILURE . . . . . . . . . . . . . . . .. . . . . . . . . . . . 90643828 TOTAL POWER FAILURE IN CARTRIDGE. . . . . . . .. . . . . . . . . 91653829 CTU DIAGNOSTIC FAILURE. . . . . . . . . . . . . . .. . . . . . . . . . . . . 92663830 UNSUCCESSFUL HWILIB INQUIRY. . . . . . . . .. . . . . . . . . . . . . 94673832 MISSING DISK EQUIPMENT. . . . . . . . . . . .

. . . . . . . . . . . . . . . . 95683833 CLAB OR CABLE FAULTY. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . 96693834 CONNECT ERROR IN DIAGNOSIS PROGRAM. . . . . . . . . . . . . 97703835 MODULE LOADING ERROR IN TEST PROGRAM. .. . . . . . . . . 99713838 TCSM FAILURE . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . 101723839 PLUG-IN UNIT IN WRONG TRACK. . . . .. . . . . . . . . . . . . . . . . 102733840 SEVERAL PLUG-IN UNITS NOT FOUND . .. . . . . . . . . . . . . . . 103743843 PARITY ERROR IN MEMORY. . . . . . . . .. . . . . . . . . . . . . . . . . 104753844 SCSI EQUIPMENT FAILURE. . . . . . .. . . . . . . . . . . . . . . . . . . . 105763845 CTU DIAGNOSTIC FAILURE. . . .. . . . . . . . . . . . . . . . . . . . . . . 107773849 SCSI HARDWARE FAILURE.. . . . . . . . . . . . . . . . . . . . . . . . . . 109783852 CABLE OR UNIT FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111793853 ABNORMAL EXCEPTION IN TEST PROGRAM . . . . . . . . . . . . 112803856 SYNCHRONIZATION INPUT

FAILURE. . . . . . . . . . . . . . . . . . . 113813858 PLUG-IN UNIT NOT PRESENT. . . . . . . . . . . . . . . . . . . . . . . . . 114823860 PING FAILURE. . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115833864 UNIT IN WRONG ROLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116843988 RCXPRO/IOMANA BUSY. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 117853989 RCXPRO/IOMANA BUSY - DIAGNOSIS JOB ABORTED. . . . . 118863990 DIAGNOSIS PATH FAILURE - DIAGNOSIS JOB ABORTED . . 119873991 INTERRUPTED DIAGNOSISJOB COMPLETED . . . . . . . . . . . 120883992 DIAGNOSIS JOB ABORTED - UNIT NOTIN TEST STATE . . . 121893993 DIAGNOSIS OF UNIT LEFT UNFINISHED . . . . . . . .. . . . . . . . 122903994 DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED. . . 123913995 DIAGNOSIS PROGRAM TOTAL TIME OUT - DIAGNOSIS JOB ABORTED. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125923996 PARTIAL DIAGNOSIS EXECUTED. . . . . . . . . . . . . . . . . . . . . . 1269

33997 PLUG IN UNIT DIAGNOSIS EXECUTED. . . . . . . . . . . . . . . . . . 127943998 DIAGNOSIS EXECUTED - UNIT NOT OK. . . . . . . . . . . . . . . . . 128953999 TOTAL DIAGNOSIS EXECUTED - UNIT OK. . . . . . . . . . . . . . . 129

6DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8feSummary of changes


4/37

Summary of changesChanges between document issues are cumulative. Therefore, thelatest document issue contains all changes made to previous issues.Summary of ChangesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.Changes made in releaseSG70 CD4Document name changed.Changes made between issues 4-0 and 3-0New alarmsModified alarmsRemoved alarmsChanges made between issues 3-0 and 2-0Removed alarms385638583860386437263838374837513745

DN99571044Issue 5-07Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)List of Alarms

Id:0900d805806fd8fe1List of Alarms3725DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITS3726NO RESPONSE FROM UNIT3727COMMUNICATION ERROR WITH UNIT3728UNIT ACCUSED BY RECOVERY - NO DIAGNOSTICS FOR UNIT3729PARITY ERROR BETWEEN SWIF AND SWCL3730PARITYERROR BETWEEN SWTST AND SWCL3731SWIF STATUS ERROR3733CONTENTS OF SWCM NOT CORRECT3734INPUT DATA MISMATCH IN TEST PROGRAM3735INTERNAL DATA MISMATCH IN TEST PROGRAM3736INTERNAL ERROR IN TEST PROGRAM3746HWALCO COMMUNICATION FAILURE3747AAL FAILURE3749HARDWARE CONFIGURATION MISMATCH3750HARDWARE CONFIGURATION MISMATCH3760FAILURE IN MEMORY SPACE3761DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIPMENT DATABASE DATA3763PARITY ERROR IN RAM UNIT3764FAILURE IN I/O SPACE3765FAILURE IN CPU SELF ACKNOWLEDGEMENT3766TG IN MARKER OR PCM ACCUSED3767ET OR PCM ACCUSED3768MFCU O

R PCM ACCUSED3769PBRU OR PCM ACCUSED3770AONU OR PCM ACCUSED3771SUB OR PCM ACCUSED3772CNFC OR PCM ACCUSED3773SWI PCM ACCUSED3774SSW PCM ACCUSED3775GSW PCM ACCUSED3776LSU OR PCM ACCUSED3777DISTURBANCE ON LSU PCM3778DIFFERENCE BETWEEN MUFILE AND PIPCMI FILES3780ADDRESSING FAILURE IN MEMORY SPACE3782DMA TRANSFER FAILURE3784BUSY PCM LINES3787BLOCKED PCM LINES

8DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8feList of Alarms

3790MSG BUS FAILURE3791NO RESPONSE BEFORE RESET3792PCM FILE READ ERROR3795CONNEC

T ERROR IN SP LINE RECEIVER TEST3798UNKNOWN ERROR IN SP LINE RECEIVER TEST3799MESSAGE BUS FAILURE3800TIME OUT IN TEST PROGRAM3801OTHER WO-EX UNIT NOT AVAILABLE3802TSUPRO ERROR IN TIME SLOT BASED DEVICE TEST3803CLB FAILURE3804UNKNOWN FAULT IN HARDWARE3808EXECUTION ERROR IN PREPROCESSOR TEST3809UNSPECIFIED FAILURE IN PREPROCESSOR TEST3810EXTERNAL LOOP FAILURE IN PREPROCESSOR TEST3814LINE PRINTER FAILURE3815VISUAL DISPLAY UNIT FAILURE3818SBUS FAILURE3819CABLE MISSING3821PREPROCESSOR EXTERNAL LOOP FAILURE3822SCSI EQUIPMENT FAILURE3823PHASE LOCK FAILURE3824DUAL PORT MEMORY FAILURE3825HWAT OR CLAB COMMUNICATION FAILURE3826CLOCK FAILURE3827PARTIAL POWER FAILURE3828TOTAL POWER FAILURE IN CARTRIDGE3829CTU DIAGNOSTIC FAILURE3830UNSUCCESSFUL HWILIB INQUIRY3832MISSING DISK EQUIPMENT3833CLAB OR CABLE FAULTY3834CONNECT ERROR IN DIAGNOSIS PROGRAM3835MODULE LOADING ERROR IN TEST PROGRAM3838TCSM FAILURE3839PLUG-IN UNIT IN WRONG TRACK3840SEVERAL PLUG-IN UNITS NOTFOUND3843PARITY ERROR IN MEMORY3844SCSI EQUIPMENT FAILURE3845CTU DIAGNOSTIC FAIL

URE3849SCSI HARDWARE FAILURE

DN99571044Issue 5-09Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)List of Alarms

Id:0900d805806fd8fe3852CABLE OR UNIT FAILURE3853ABNORMAL EXCEPTION IN TEST PROGRAM3856SYNCHRONIZATION INPUT FAILURE3858PLUG-IN UNIT NOT PRESENT3860PING FAILURE3


5/37

864UNIT IN WRONG ROLE3988RCXPRO/IOMANA BUSY3989RCXPRO/IOMANA BUSY - DIAGNOSIS JOB ABORTED3990DIAGNOSIS PATH FAILURE - DIAGNOSIS JOB ABORTED3991INTERRUPTED DIAGNOSIS JOB COMPLETED3992DIAGNOSIS JOB ABORTED - UNIT NOT IN TEST STATE3993DIAGNOSIS OF UNIT LEFT UNFINISHED3994DATA MISMATCH IN FILES - DIAGNOSIS JOB ABORTED3995DIAGNOSIS PROGRAM TOTAL TIME OUT - DIAGNOSIS JOB ABORTED3996PARTIAL DIAGNOSIS EXECUTED3997PLUG IN UNIT DIAGNOSIS EXECUTED3998DIAGNOSIS EXECUTED - UNIT NOT OK3999TOTAL DIAGNOSIS EXECUTED - UNIT OK

10DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3725 DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITS

23725 DIAGNOSIS MESSAGE - ACCUSED PLUG-IN UNITSMeaningA diagnosis report containing those plug-in units in whicha failure has been detected. In the diagnosis report, theplug-in unit type, place of the subrack in the exchange and thetrack number have been listed.Supplementary information fieldsInstructionsDescription ofthe report is in the instructions on diagnosticsand testing.Replace the plug-in units suspected faulty.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-011Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3726 NO RESPONSE FROM UNIT

Id:0900d805806fd8fe33726 NO RESPONSE FROM UNITMeaningDGTPRO has not received anyacknowledgement to the diagnosticprogram start-up message it has sent to the functional unit whichis the object of the report. The program block of the diagnosticprograms of the unit has not been created, or the unit is so faultythat it cannot respond or the communications to the unit has beendisturbed by a fault in another unit.Supplementary information fieldsInstructionsIf the diagnostic job has been originated by the systemand unit in question is under monitoring (i.e. unit has MONI-status on) system will run diagnostic again after a while. Youshouldwait if response is got this time.If no response from unit report is printed ag

ain or the diagnosticjob has been originated by user, chech with command USI that thestate of the unit in question is TE-EX and reactivate the unitdiagnosis with the command UDU.If this does not help, replace the plug-in unit of the functionalunit 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 nothave any fault at all but the problem is elsewhere inthe system.You should start diagnosing other functional units of the systemsuchas switching, multiplexing and other units closely connectedto the functional unit originally diagnosed. This may also includeswitchovers of the units, replacing plug-in units and possiblycables and repeating the diagnostics also for the functionalunit originally diagnosed until a response is received.CancellingThis is a diagnosis report, it is not cancelled.

12DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3727 COMMUNICATION ERROR WITH UNIT

43727 COMMUNICATION ERROR WITH UNITMeaningAn error in the message exchange between the DGTPRO program blockand diagnostic program (functional unit to be diagnosed).Supplementary information fieldsInstructionsRestart the unit with the RESETbutton and reactivate the unitdiagnosis with the command UDU. If this does not h


6/37

elp, locate thefailure by replacing plug-in units MBIF-T and CPXXX.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-013Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3728 UNIT ACCUSED BY RECOVERY - NO DIAG-NOSTICS FOR UNIT

Id:0900d805806fd8fe53728 UNIT ACCUSED BY RECOVERY - NO DIAGNOSTICS FOR UNITMeaningThe RCXPRO program block has given to the DGTPRO program block adiagnosis command of such a unit which does not (yet) have anydiagnostic programs in the system. The recovery command is anormal action of automatic fault location.Supplementary information fieldsInstructionsDiagnose the unit by other means (for exampleby examining thealarm print-outs).CancellingThis is a diagnosis report, it is not cancelled.

14DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3729 PARITY ERROR BETWEEN SWIF AND SWCL

63729 PARITY ERROR BETWEEN SWIF AND SWCLMeaningThe switching network diagnostics

has detected a parity error ina message between SWIF - SWCL - SWCM. The error has beendetected in the phase where the message route has already beenfound to bein order. The error may have been caused by thefollowing:- in the plug-in unitsSWIF, SWCL, or SWTST there is a failurewhich occurs at random- in the plug-in units SWIF, SWCL, or SWTST there is a failurewhich the previous diagnostic program has not detected.Supplementary information fields1 002 00InstructionsRepeat the test. If the alarm remains the same, locate thefailure by replacing plug-in units SWIF, SWCL, and SWTST.CancellingThis is a diagnosis report, it is notcancelled.

DN99571044Issue 5-015Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3730 PARITY ERROR BETWEEN SWTST ANDSWCL

Id:0900d805806fd8fe73730 PARITY ERROR BETWEEN SWTST AND SWCLMeaningThe switchingnetwork diagnostics has detected a parity error ina message between plug-in units SWTST and SWCL. The error has beendetected in the phase where the route of the message mentionedabove has already been found to be in order. The error may havebeen caused by the following:- in the plug-in units SWTST, SWCL, or SWIF thereis a failurewhich occurs at random- in the plug-in units SWTST, SWCL, or SWIF there is a failurewhich the previous diagnostic program has not detected.Supplementary information fields1 002 00InstructionsRepeat the test. If the alarmremains the same, locate thefailure by replacing plug-in units SWTST, SWCL, andSWIF.CancellingThis is a diagnosis report, it is not cancelled.

16DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3731 SWIF STATUS ERROR

83731 SWIF STATUS ERRORMeaningThe switching network diagnostics has detected that the statedata of the SWIF plug-in unit is incorrect. The error has beendetected in the phase where the state register has already beenfound to be in order. Th


7/37

e error may have been caused by thefollowing:- an error occurring in the SWIF plug-in unit at random- an error in the SWIF plug-in unit not detected by the previousdiagnostic program.Supplementary information fields1 002 00InstructionsRepeat the test. If the alarm remains the same, replaceplug-in unit SWIF.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-017Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3733 CONTENTS OF SWCM NOT CORRECT

Id:0900d805806fd8fe93733 CONTENTS OF SWCM NOT CORRECTMeaningThe switching network diagnostics has detected that the contentsof the control memory (plug-in unitSWCM) are erroneous in thereading executed immediately after the writing (writereturn message).The error has been detected in the phase where the control memoryhas already been found to be in order. The error may have beencaused by the following:- in the plug-in units SWCM, SWCL, or SWIF there is a failurewhich occursat random- in the plug-in units SWCM, SWCL, or SWIF there is a failurewhich theprevious diagnostic program has not detected.Supplementary information fields1

002 00InstructionsRepeat the test. If the alarm remains the same, locate thefailure by replacing plug-in units SWCM, SWCL, and SWIF.CancellingThis is a diagnosis report, it is not cancelled.

18DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3734 INPUT DATA MISMATCH IN TEST PROGRAM

103734 INPUT DATA MISMATCH IN TEST PROGRAMMeaningThe diagnostic program has detected that the data used in thetest start-up is erroneous. The data is contradictory eitherwith itself or with a parameter outside the test.Supplementary information fields1 002 00InstructionsRepeat the test. If the alarm remains unchanged, reload thefiles of the DGTPRO program block of the OMU or MSW from thedisk(DGFILE, DGSPRO, DGUTST, NURSES, LEQURI). Check theequipping of the exchange with the EQADMI MML program (commandWT). In connection with the DX 200 exchange, a

lso reload thePCM configuration files from the disk into the active centralmemory (CM). If the alarm remains unchanged after a new test,fill in a Problem Report.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-019Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3735 INTERNAL DATA MISMATCH IN TEST PRO-GRAM

Id:0900d805806fd8fe113735 INTERNAL DATA MISMATCH IN TEST PROGRAMMeaningThe diagnostic program has detected an error in its owninternal data tables. The data iscontradictory either withitself or with a parameter outside the test.Supplementa

ry information fields1 002 00InstructionsRepeat the test. If the alarm remains the same, fill ina Problem Report.CancellingThis is a diagnosis report, itis not cancelled.

20DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3736 INTERNAL ERROR IN TEST PROGRAM


8/37

123736 INTERNAL ERROR IN TEST PROGRAMMeaningThe diagnostic program has detectedan error in its internalfunction. The error has not been caused by the malfunction ofthe equipment tested, the external data used in the teststart-up, or the internal fixed data of the test program.Supplementary information fields1 00200InstructionsRepeat the test. If the alarm remains the same, fill ina Problem

Report.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-021Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3746 HWALCO COMMUNICATION FAILURE

Id:0900d805806fd8fe133746 HWALCO COMMUNICATION FAILUREMeaningThe Hardware AlarmCollection Program Block (HWALCO) has failedto send, within two time supervisionperiods, a reply message to thediagnostic program, or the reply sent was incorrect.Supplementary information fields1 002 00InstructionsReset the unit that is to be tested and run again the diagnosticprogram for wired alarms.CancellingThis is a diagnosis report, it is not cancelled.

22DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:

0900d805806fd8fe3747 AAL FAILURE143747 AAL FAILUREMeaningAn AAL plug-in unit of the OMU is faulty.Supplementaryinformation fields1 002 00InstructionsRestart the wired alarm diagnostic program: UDU:OMU:WAT;.Replace the AAL plug-in unit indicated by the diagnosisreport and start up the wired alarm diagnostic programwith the command UDU:OMU:WAT;.If the failure was removed,set the OMU into state WO, otherwise, fill in a ProblemReport.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-023Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)37

49 HARDWARE CONFIGURATION MISMATCH

Id:0900d805806fd8fe153749 HARDWARE CONFIGURATION MISMATCHMeaningThe diagnostic program is unable to obtain from the equipmentdatabase data on one or more plug-in units, or the search failsoutright.Supplementary information fields1 00200InstructionsUse the EQADMI MML program (command WT) to check if there areanysupernumerary plug-in units in the subrack. Restart the unitwith the USU command. Start a total diagnosis, using the UDUcommand. If the fault persists, fill ina Problem Report.CancellingThis is a diagnosis report, it is not cancelled.

24DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3750 HARDWARE CONFIGURATION MISMATCH

163750 HARDWARE CONFIGURATION MISMATCHMeaningThe diagnostic program is unable toobtain from the equipmentdatabase data on one or more plug-in units, or the search failsoutright.Supplementary information fields1 002 00InstructionsUsethe EQADMI MML program (command WT) to check if there areany supernumerary plug-in units in the subrack. Restart the unitwith the USU command. Start a total diagnosis, using the UDUcommand. If the fault persists, fill in a Problem Report.CancellingThis is a diagnosis report, it is not cancelled.


9/37

DN99571044Issue 5-025Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3760 FAILURE IN MEMORY SPACE

Id:0900d805806fd8fe173760 FAILURE IN MEMORY SPACEMeaningIn the RAM test, a failure has been detected in the unbanked memory.A RAM, ASS, AS7, or LSP plug-in unitidentifies an incorrectaddress, or a RAM plug-in unit does not identify its ownaddress, or an ASS plug-in unit is faulty, or the memoryconfiguration file (MUFILE) does not correspond to theconfiguration.Supplementary information fields1address in which the failure was detected (upper word)2 address in which thefailure was detected (lower word)InstructionsCheck the MUFILE file. Replace theRAM, AS7, ASS, and LSPplug-in units one by one, and after the replacing, restartthe RAM partial diagnosis with the command UDU.CancellingThis is a diagnosis report, it is not cancelled.

26DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIPMENT DATABASEDATA

183761 DIFFERENCE BETWEEN MEMORY SPACE AND THE EQUIPMENT DATABASE DATAMeaningThesize of the memory space obtained in the RAM test from theequipment database isinconsistent with the actual size of the memory.Supplementary information fields1 address where fault was detected (upper word)2 address where fault wasdetected (lower word)InstructionsCheck whether the memory space given in the equipment listcorresponds to the actually existing memory space (EQADMI MMLcommandWTI). If not, correct the error in the list and thenrestart the unit with the USU command. Finally start the RAMpartial diagnosis (again), using the UDU command.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-027Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3763 PARITY ERROR IN RAM UNIT

Id:0900d805806fd8fe193763 PARITY ERROR IN RAM UNITMeaningIn the RAM test, a parity error caused by a RAM plug-in unithas been detected.Supplementary informationfields1 index of the RAM plug-in unit suspected faulty2 lower word of memory address suspected faultyInstructionsRestart the RAM partial diagnosis with the command UDU. If the parityerror is repeated, replace the RAM plug-in units and the CPU plug-inunit one by one, and, after the replacing, restart the RAM partialdiagnosis.CancellingThis is a diagnosis report, it is not cancelled.

28DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3764 FAILURE IN I/O SPACE

203764 FAILURE IN I/O SPACEMeaningIn 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, anaddressing failure in a plug-in unit of the I/O space, or theunit's I/O address data does not correspond to the equipment database.Supplementary information fields1address in which the failure was detected2 00InstructionsCheck the contents o


10/37

f the equipment database with the EQADMIMML program (command WT). Check if thereare any extra plug-inunits in the subrack. Replace the plug-in units on the SYSBbus one by one (you can output the plug-in units withthe UDI command), and after having replaced each plug-inunit, start up the SYSB partial diagnosis with theUDU command.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-029Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3765 FAILURE IN CPU SELF ACKNOWLEDGEMENT

Id:0900d805806fd8fe213765 FAILURE IN CPU SELF ACKNOWL-EDGEMENTMeaningIn the CPUtest, a failure situation has been detected. The CPXXXplug-in unit is faulty, orthere is an addressing failure in aplug-in unit of the I/O space.Supplementaryinformation fields1 002 00InstructionsReplace the AAL, AAL-S, AFS-S, BEXT,CP386, DMADI, DMASI,MBIF-T, RAM1M, SERO, SWCOP, SWIF, SWTST, and TAPI plug-inunits one by one and after the replacing, start up the DMCpartial diagnosis with the command UDU.CancellingThis is a diagnosis report, it is not cancelled.


0900d805806fd8fe3766 TG IN MARKER OR PCM ACCUSED223766 TG IN MARKER OR PCM ACCUSEDMeaningThe SWCL picking logic test has been executed in the SSWnetwork. The tone generator or an internal PCM circuit may befaulty.Supplementary information fields1 002 00InstructionsFirst replace theplug-in units mentioned in the plug-in unit listone by one and execute the SMIpartial test of the SSU. If thefailure is repeated, replace the tone generator.If thereplacement does not help, an internal PCM circuit is faulty.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-031Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3767 ET OR PCM ACCUSED

Id:0900d805806fd8fe233767 ET OR PCM ACCUSEDMeaningThe diagnostic program of theserial-parallel converter linereceivers has detected that the frame alignment signal comingfrom the exchange terminal is erroneous. The fault is in theserial-parallel converter (S/P), exchange terminal (ET), orPCM circuit coming from the exchange terminal. A list ofplug-in units suspected faulty is usually also printedoutin connection with this diagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 00Instructions Action Note---------------------------------------------------------------------------- START o ! +---o 1

1. Was alarm number 3725 also received? ! ! a: yes o

a o b b: no ! ! o 2 ! 2. See the instructions givenin ! ! the alarm instructions. +---! ! !+---o 3 3. Was the alarm eliminated? ! ! a: yes o ao b b: no ! ! o ! END ! o 4 4. On the basis of the supplementary ! information field, check from

! which trunk circuit ET or remote ! subscriber stage ET the incorrect


11/37

32DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3767 ET OR PCM ACCUSED

! frame alignment signal is coming. ! Repair the unit or PCM circuit ! in question. o ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-033Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3768 MFCU OR PCM ACCUSED

Id:0900d805806fd8fe243768 MFCU OR PCM ACCUSEDMeaningThe diagnostic program of the serial-parallel converter linereceivers has detected that the control/identification wordcoming from the MFC unit is erroneous. The fault is in theserial-parallel converter (S/P), MFC unit (MFCU), or PCMcircuit coming from the MFC unit. Alist of plug-in unitssuspected faulty is usually also printed out in connectionwith this diagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 00Instructions Action

Note---------------------------------------------------------------------------- START o ! +---o 1 1. Was alarmnumber 3725 also received? ! ! a: yes o a o b b

: no ! ! o 2 ! 2. See the instructions given in 3725 ! !in Diagnosis Reports. +---! ! ! +---o 33. Was the alarm eliminated? ! ! a: yes o a o bb: no ! ! o ! END ! o 4 4. On the basis of the supplementary ! information field, check which !

MFC device is faulty. ! Repair the unit or PCM circuit! in question. o

34DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3768 MFCU OR PCM ACCUSED

ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-035Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3769 PBRU OR PCM ACCUSED

Id:0900d805806fd8fe253769 PBRU OR PCM ACCUSEDMeaningThe diagnostic program of the serial-to-parallel converter linereceivers has detected that the identification word coming fromthe Push Button Receiver Unit (PBRU) is erroneous.The fault isin the serial-to-parallel converter, in thePBRU or in the PCM circuit coming fr

om the PBRU.A list of plug-in units suspected faulty is usually alsoprinted outin connection with this diagnosis.Supplementary information fields1 number ofthe PCM circuit suspected faulty2 00Instructions Action

Note---------------------------------------------------------------------------- START o ! +---o 11. Was alarm number 3725 also received? ! ! a: yes o a ob b: no ! ! o 2 ! 2. See the instructions given in3725 ! ! in the document Diagnosis +---! Reports. ! ! +---o 3 3. Was the alarm eliminated? ! !

a: yes o a o b b: no ! ! o ! END !


12/37

o 4 4. On the basis of the supplementary ! information field, check ! which PBR device is faulty. !

Repair the unit or PCM circuit

36DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3769 PBRU OR PCM ACCUSED

! in question. ! o ENDCancellingThis isa diagnosis report, it is not cancelled.

DN99571044Issue 5-037Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3770 AONU OR PCM ACCUSED

Id:0900d805806fd8fe263770 AONU OR PCM ACCUSEDMeaningThe test program of the serial-to-parallel converter line receivershas detected that the control/identification word coming from theAON unit is erroneous or that the multifrequency character is aconstant character. The fault is in the serial-to-parallel converter,in the AON unit (AONU), or in the PCM circuit coming from the AON unit.A list of plu

g-in units suspected faulty is usually also printedout in connection with this diagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 number of the PCM circuit suspected faulty (00 no significance)Instructions Action Note---------------------------------------------------------------------------- START o ! +---o 1 1. Was alarm number 3725 also received? ! ! a: yes o a o b b: no ! ! o 2 !

2. See the instructions given in 3725 ! ! in the document Diagnosis Reports. +---! ! ! +---o 3 3. Was the alarm eliminated? ! ! a: yes o a o b b: no !! o ! END ! o 4 4. On the basis of the supplementary

! information field, check ! which AON unitis faulty.

38DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3770 AONU OR PCM ACCUSED

! Repair the unit or PCM circuit ! in question. o ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-039Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3771 SUB OR PCM ACCUSED

Id:0900d805806fd8fe273771 SUB OR PCM ACCUSEDMeaningThe diagnostic program of theserial-to-parallel converter linereceivers has detected that the constant signal sent by thetone generator in time slot T0 coming from the subscribermodule iserroneous. The fault is in the serial-to-parallelconverter, in the subscriber module (SUB), or in the PCM circuit comingfrom the subscriber module. A list of plug-in units suspectedfaulty is usually also printed out in connection with thisd


13/37

iagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 00Instructions Action

Note---------------------------------------------------------------------------- START o ! +---o 1 1. Was alarm number 3725 also received? ! ! a: yes o a o b b: no !! o 2 ! 2. See the instructions given in 3725 ! !in the document Diagnosis Reports. +---! ! ! +---o 33. Was the alarm eliminated? ! ! a: yes o a o bb: no ! ! o ! END ! o 4 4. On the basis of the su

pplementary ! information field, check !which subscriber module is faulty

40DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3771 SUB OR PCM ACCUSED

! and repair the unit or ! PCM circuitin question. ! ! ! ! ! o ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-041Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3772 CNFC OR PCM ACCUSED

Id:0900d805806fd8fe283772 CNFC OR PCM ACCUSEDMeaningThe diagnostic program of the serial-parallel converter linereceivers has detected that the signal coming from theconference circuit is erroneous. The fault is in theserial-parallel converter (S/P), conference circuit (CNFC),or PCM circuit coming from the conference circuit. A list ofplug-in units suspected faulty is usually also printed outin connection with this diagnosis.Supplementary information fields1 number of thePCM circuit suspected faulty2 00Instructions Action

Note---------------------------------------------------------------------------- START o ! +---o 1 1.

Was alarm number 3725 also received? ! ! a: yes o a o bb: no ! ! o 2 ! 2. See the instructions given in !! the alarm instructions +---! ! ! +---o 3

3. Was the alarm eliminated? ! ! a: yes o a o bb: no ! ! o ! END ! o 4 4. On the basis of the

supplementary ! information field, check !which conference circuit is faulty. ! Repair the unit an

d PCM circuit ! in question. o


0900d805806fd8fe3772 CNFC OR PCM ACCUSED


DN99571044Issue 5-043Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3773 SWI PCM ACCUSED


14/37

Id:0900d805806fd8fe293773 SWI PCM ACCUSEDMeaningThe diagnostic program of the serial-parallel converter linereceivers has detected that the signal sent by the tonegenerator (TG) in the internal call link is erroneous. The faultis in the serial-parallel converter (S/P), parallel-serialconverter (P/S_0) (line transmitters), or PCM circuit ofthe internal call link. A list of plug-in units suspectedfaulty is usually also printed out in connection with thisdiagnosis.Supplementaryinformation fields1 number of the PCM circuit suspected faulty2 00Instructions Action Note---------------------------------------------------------------------------- START

o ! +---o 1 1. Was alarm number 3725 also received? !! a: yes o a o b b: no ! ! o 2 ! 2. See the instructions given in 3725 ! ! in Diagnosis Reports. +---! ! ! +---o 3 3. Was the alarm eliminated? ! ! a: yes o a o b b: no ! ! o ! END !

o 4 4. On the basis of the supplementary ! information field, check ! which internal call link is faulty

! and repair the PCM circuit ! in question.

44DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3773 SWI PCM ACCUSED

o ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-045Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3774 SSW PCM ACCUSED

Id:0900d805806fd8fe303774 SSW PCM ACCUSEDMeaningThe diagnostic program of the serial-parallel converter linereceivers has detected that the signal sent by the tonegenerator (TG) in the PCM circuit of the SSW network iserroneous. The fault is in the serial-parallel converter (S/P),parallel-serial converter of the SSW (P

/S_0) (linetransmitters), or PCM circuit of the SSW network. A listof plug-in units suspected faulty is usually also printedout in connection with this diagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 00Instructions Action Note----------------------------------------------------------------------------

START o ! +---o 1 1. Was alarm number 3725 alsoreceived? ! ! a: yes o a o b b: no ! ! ! ! o 2 ! 2. See the instructions given in 3725 ! !

in Diagnosis Reports. +---! ! ! +---o 3 3. Was the alarm eliminated? ! ! a: yes o a o b b: no! ! o ! END ! o 4 4. On the basis of the supplementary ! information field, check which

46DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3774 SSW PCM ACCUSED

! PCM circuit in the subscriber stage !switch is faulty and repair ! the PCM circuit in question.



15/37

DN99571044Issue 5-047Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3775 GSW PCM ACCUSED

Id:0900d805806fd8fe313775 GSW PCM ACCUSEDMeaningThe diagnostic program of the serial-parallel converter linereceivers has detected that the signal sent by the tonegenerator (TG) in the PCM circuit of the GSW network iserroneous. The fault is in the serial-parallel converter(S/P), parallel-serial converters of the GSW (P/S) (linetransmitters), or PCM circuit of the GSW network. A listof plug-in units suspected faulty is usually also printedout in connection with this diagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty2 00Instructions Action Note----------------------------------------------------------------------------

START o ! +---o 1 1. Was alarm number 3725 also received? ! ! a: yes o a o b b: no ! ! o2 ! 2. See the instructions given in ! ! the alarm instructions. +---! ! ! +---o 3 3. Was the alarm eliminated? ! ! a: yes o a o b b: no ! ! o! END ! o 4 4. On the basis of the supplementary !

information field, check which ! PCM circuit in the group switch is ! faulty and repair the o

PCM circuit in question.

48DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3775 GSW PCM ACCUSED



76 LSU OR PCM ACCUSED

Id:0900d805806fd8fe323776 LSU OR PCM ACCUSEDMeaningThe diagnostic program of theserial-parallel converter linereceivers has detected that the multiframe alignment signalcoming from the line signalling unit is erroneous. The fault isin theserial-parallel converter (S/P), line signallingunit (LSU), or PCM circuit coming from the line signallingunit. A list of plug-in units suspected faulty is usuallyalso printed out in connection with this diagnosis.Supplementary informationfields1 number of the PCM circuit suspected faulty2 00Instructions

Action Note---------------------------------------------------------------------------- START o! +---o 1 1. Was alarm number 3725 also received? ! !

a: yes o a o b b: no ! ! o 2 ! 2. See the in

structions given in ! ! the alarm instructions. +---!! ! +---o 3 3. Was the alarm eliminated? ! !a: yes o a o b b: no ! ! o ! END ! o 44. On the basis of the supplementary ! information field

, check which ! LSU or LSA is faulty. Repair the !unit or PCM circuit in question.


16/37

50DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3776 LSU OR PCM ACCUSED


DN99571044Issue 5-051Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3777 DISTURBANCE ON LSU PCM

Id:0900d805806fd8fe333777 DISTURBANCE ON LSU PCMMeaningThe diagnostic program ofthe serial-parallel converter linereceivers has first detected that the multiframe alignmentsignal coming from the line signalling unit is erroneous ormissing,but it has received a correct multiframe alignmentsignal having made a new attempt. The line signal may bemissing for a while also during normal operation, butthefault may be in the serial-parallel converter (S/P), linesignalling unit (LSU), or PCM circuit coming from theline signalling unit. A list of plug-in unitssuspectedfaulty is usually also printed out in connection with thisdiagnosis.Supplementary information fields1 number of the PCM circuit suspected faulty200Instructions Action Note----------------------------------------------------------------------------START o ! o 1 1. Restart the SPLRT partialUDU:M,X:SPLRT; ! diagnosis. UDU

:CAC,X:SPLRT; ! +---o 2 2. Does the alarm recur? ! !a: yes o a o b b: no ! ! o ! END ! !+---o 3 3. Was alarm number 3725 also ! ! received?

o a o b a: yes ! ! b: no ! ! o 4 !4. See the instructions given in ! ! the alarm instructi

ons.

52DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3777 DISTURBANCE ON LSU PCM

! ! ! ! +---! ! +---o 5 5. Was the alarm eliminated? ! ! a: yes o a o b b: no ! ! o !END ! ! o 6 6. On basis of the supplementary !

information field, check which LSU ! or LSA is faulty. Repair the unit ! or PCM circuit in question.! o ENDCancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-053Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3778 DIFFERENCE BETWEEN MUFILE AND PIPCMIFILES

Id:0900d805806fd8fe343778 DIFFERENCE BETWEEN MUFILE AND PIPCMI FILESMeaningThe number of AS7 plug-in units is not the same in the MUFILE andPIPCMI files.Supplementary information fields1 002 00InstructionsCheck the files. Restart thetest after a possible modification.CancellingThis is a diagnosis report, it is not cancelled.



17/37

0900d805806fd8fe3780 ADDRESSING FAILURE IN MEMORY SPACE

353780 ADDRESSING FAILURE IN MEMORY SPACEMeaningIn the RAM test, an addressing failure has been detected.A CPU (RAM), ASS, AS7, LSP or RAM64M plug-in unit doesnotidentify its own address, identifies an incorrect address,is faulty, or the memory configuration file (MUFILE) doesnot correspond to the configuration.Supplementary information fields1 address in which the failure was detected (upperword)2 address in which the failure was detected (lower word)InstructionsCheck the MUFILE file. Replace the CPU (RAM), AS7, ASS, LSPand RAM64M plug-in unitsone by one, and after the replacing,restart the RAM partial diagnosis with the command UDU.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-055Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3782 DMA TRANSFER FAILURE

Id:0900d805806fd8fe363782 DMA TRANSFER FAILUREMeaningThe EDISKD program block ofthe STU has detected a DMASIplug-in unit of the STU to be faulty.The plug-in unit detected faulty is located in the active STU.Supplementary information fields1 error message2 00InstructionsMake a switchover with the MML command USC.Restart the diagnosticsof WDS. If the error is eliminated, change the DMASI plug-in unitin the passive STU that has the same index as that of the WDS beingtest

ed. Set the passive STU into state SP and make a switchover withthe MML commandUSC. Start the diagnostics of the WDS. If the erroris eliminated, set the WDS into state WO-BU. If the error stillpersists, check the cabling of the DMASI plug-in unit and that theplug-in unit is properly placed.CancellingThis is a diagnosis report, it is not cancelled.

56DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3784 BUSY PCM LINES

373784 BUSY PCM LINESMeaningThe diagnostic program of the serial-parallel conver

ter linereceivers has been executed, but part of the PCM circuits havenot been tested because of the load situation of the exchange.Supplementary information fields1 number of the PCM circuit suspected faulty2 number of the PCM circuit suspected faulty (00= no significance)InstructionsIf you wish to test allpossible PCM circuits, you will have towait for a period with less traffic. Otherwise no action isrequired.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-057Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3787 BLOCKED PCM LINES

Id:0900d805806fd8fe383787 BLOCKED PCM LINESMeaningThe diagnostic program of theserial-parallel converter linereceivers has been executed, but part of the PCM circuits havenot been tested because they were blocked from hunting duringthe test.Supplementary information fields1 number of the PCM circuit suspected faulty2 number of the PCM circuit suspected faulty (00= no significance)InstructionsIf you wish to test all possible PCM circuits, release the blockedcircuitsfor hunting and run the test again. Release all GSW, SSW,and CNFC PCM circuitsfor hunting. Otherwise no action is required.CancellingThis is a diagnosis report, it is not cancelled.


18/37

58DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3790 MSG BUS FAILURE

393790 MSG BUS FAILUREMeaningThe response test of a computer unit has detected amalfunctionin the operation of the message bus.Supplementary information fields1 additional diagnosis 01 response message of the unit is correct on the active message bus, distorted on the reserve bus 02 response message of the unit is correct on the active message bus, no response onthe reserve bus 03 response message of the unit is distorted on the active message bus, the reserve bus is in SEPARATED state 04 response message of the unit is distorted on the active message bus, correct on the reserve message bus 05 response message of the unit is distorted both on the active and reserve message buses 06 response message of theunit is distorted on the active message bus, no response on the reserve bus 07 response message of the unit is correct on the reserve message bus, no response on the active bus 08 response message of the unitis distorted on the reserve message bus, no response on the active bus

09 after unit restart, response message is distorted on the active message bus 10 after unit restart, response message is distorted on the

reserve message bus, no response on the active bus2 index of the MBI

F_T plug-in unit suspected faultyInstructionsNo action required.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-059Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3791 NO RESPONSE BEFORE RESET

Id:0900d805806fd8fe403791 NO RESPONSE BEFORE RESETMeaningThe computer unit doesnot respond unless restarted.Supplementary information fields1 additional diagnosis 01 active unit responds correctly after unit restart 02 passive unit responds correctly after unit restart, active unit does not res

pond2 00InstructionsNo action required.CancellingThis is a diagnosis report,it is not cancelled.

60DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3792 PCM FILE READ ERROR

413792 PCM FILE READ ERRORMeaningThe function of the diagnostic program has beeninterruptedbecause of a read error in the PCM Configuration File (PCMCON).Supplementary information fields1 error message returned by the library program located in the HWILIB library2 00Instructions Action

Note---------------------------------------------------------------------------- START o ! +---o 1 1. Check the exchange configuration ! ! with the EQADMI MML program. WTI o a o b a: in order ! ! b: outof order ! ! ! ! ! o 2 2. Repair the exchange configuration ! ! data with the EQADMI MML. WT ! ! +-->o 3 3. Restart the partial diagnosis UDU:M,X:SPLRT; !

(line receiver test as example) UDU:CAC,X:SPLRT; !UDU:SSU,X,X:SPLRT; +---o 4 4.

Did the alarm recur? ! ! a: yes o b o a b: no


19/37

! ! o ! END ! ! +---o 5 5. Check the condition ofthe ! ! central memory units. o a o b a: in order ! ! b: out of order

DN99571044Issue 5-061Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3792 PCM FILE READ ERROR

Id:0900d805806fd8fe ! ! ! ! ! o 6 6. Repair central memory units. ! ! +-->o 7 7. Restart the partial diagnosis. UDU:M,X:SPLRT; ! (line receiver test as example) UDU:CAC,X:SPLRT; ! UDU:SSU,X,X:SPLRT; +---o 8 8. Did the alarm recur? ! ! a: yes ob o a b: no ! ! o ! END ! ! o 9 9.Fill in a Problem Report. ! o ENDCancellingThis is a diagnosis report, it is not cancelled.

62DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3795 CONNECT ERROR IN SP LINE RECEIVER TEST

423795 CONNECT ERROR IN SP LINE RECEIVER TESTMeaningThe diagnostic program of the serial-parallel converter linereceivers is interrupted because the making of test connectionshas not succeeded. (SWICOP has answered with an erroracknowledgement.)Supplementary information fields1 002 00InstructionsAction Note----------------------------------

------------------------------------------ START o !o 1 1. Observe other incoming alarms. USU:M,X; !If the setting up of connections USU:CAC,X; ! is not s

uccessful in any of USU:SSU,X,X; ! the computers, restart the ! computer in question. ! ! o2 2. Restart the SPLRT partial UDU:M,X:SPLRT; !

diagnosis. UDU:CAC,X:SPLRT; !

UDU:SSU,X,X:SPLRT; +---o 3 3. Did the alarm recur? ! ! a: yes o b o a b: no! ! o ! END ! ! o 4 4. Fill in a Problem Report. ! o END

DN99571044Issue 5-063Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3795 CONNECT ERROR IN SP LINE RECEIVERTEST

Id:0900d805806fd8feCancellingThis is a diagnosis report, it is not cancelled.

64DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3798 UNKNOWN ERROR IN SP LINE RECEIVER TEST

433798 UNKNOWN ERROR IN SP LINE RECEIVER TESTMeaningThe test of serial-parallelconverter line receivers has beencompleted, but the exact specification of the fault has failed.The value in the error counters is logically impossible, forexample several simultaneous faults, hardware is missing in thePCM circuits defined


20/37

for use in the unit identifier file,or there is a fault in the additional wiringor cabling.Supplementary information fields1 002 00Instructions

Action Note--------------------------------------------------------------------------- START o !

o 1 1. Restart the SPLRT partial UDU:M,X:SPLRT;! diagnosis. UDU:CAC,X,SPLRT; !

UDU:SSU,X,X:SPLRT; +---o 22. Did the alarm recur? ! ! a: yes o b o a b

: no ! ! o ! 3. Check the cabling and additional END !wiring of the switching network. o 3 Check that the

PCM circuit data in ! the PCMCON file corresponds to the! exchange configuration, and that all ! t

he hardware is in place and in working ! condition. Make necessary repairs. ! ! o 4 4. Restart the SPLRT partial command as in ! diagnosis.

item 1 !

DN99571044Issue 5-065Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3798 UNKNOWN ERROR IN SP LINE RECEIVERTEST

Id:0900d805806fd8fe +---o 5 5. Did the alarm recur? ! !

a: yes o b o a b: no ! ! o ! 6. Replace one S/P plug-in unit command as in END ! at a time and restart the SPLRT item 1 +-->o 6 partial diagnosis after each! ! replacement. Put each plug-in unit ! ! thatproves to be in order back ! ! into place. ! ! +---o7 7. Continue replacing until all plug- ! in units have been replaced or until a o b a more precise diagnosis is obtained. ! a: plug-in units still to be replaced !

b: all plug-in units have been replaced. ! +---o 8 8.Has a more precise diagnosis been ! ! obtained? ! a o b

a: yes ! ! b: no ! ! o 9 ! 9. Follow the new instructions. ! ! o o 10 10. Fill in a Problem Report. END ! o ENDCancellingThis is a diagnosis report, it is not canc

elled.

66DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3799 MESSAGE BUS FAILURE

443799 MESSAGE BUS FAILUREMeaningA failure has been detected in the operation ofthe message bus.Supplementary information fields1 error code 01 message reception of one plug-in unit fails 02 message sending of one plug-in unit fails 03 message reception and message sending of one plug-inunit fails 04 message reception of more than one plug-in unit fails 05

message sending of more than one plug-in unit fails 06 message reception and message sending of more than one plug-in unit fails 07 message sending of all plug-in units fails 08 message reception of all plug-inunits fails 09 all message sending and message reception fails 10 unit identifies wrong message bus address 11 other failure affecting message sending when testing group addresses, the detected faults produce the above error codes plus 020H (21 ... 31)2 message bus addressInstructionsThe fault is either in the MBIF(-X) plug-in unit at the messagebus addressindicated in supplementary information field 2, orin the message bus itself. Replace the faulty plug-in unit andrerun the test to make sure the fault has been e


21/37

liminated.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-067Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3800 TIME OUT IN TEST PROGRAM

Id:0900d805806fd8fe453800 TIME OUT IN TEST PROGRAMMeaningThe diagnostic programdoes not receive a reply to the message ithas sent, which results in a time-out.Supplementary information fields1 message bus address2 family identifierInstructionsRestart the program block of the computer (supplementary informationfields 2 and 1 respectively), if this can be done without interferingwith the function of the exchange.CancellingThis is a diagnosis report, it is not cancelled.

68DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3801 OTHER WO-EX UNIT NOT AVAILABLE

463801 OTHER WO-EX UNIT NOT AVAILABLEMeaningNo other unit in the WO working state is available in the testconnection elementary test of a signalling unit.Supplementary information fields1 002 00InstructionsIf the other signalling unit

is in the BL, TE, or SE state, setthe unit in the WO state. Otherwise wait forsome time andrestart the diagnostic program with the command UDU.CancellingThisis a diagnosis report, it is not cancelled.

DN99571044Issue 5-069Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3802 TSUPRO ERROR IN TIME SLOT BASED DE-VICE TEST

Id:0900d805806fd8fe473802 TSUPRO ERROR IN TIME SLOT BASED DEVICE TESTMeaningTheTSUPRO program block functions erroneously in thetime slot based device test.Supplementary information fields1 error code returned by TSUPRO 08 test no

t permitted 09 test does not exist 0B connection release failure0C program block does not respond 0D path error 0E SSP does not respond 10 MTSWIS-GSW error 11 MTSWIS-SSW error 20 parameter error 40 ASS_LOOP_GSW error 41 ASS_LOOP_SSW error 80 program block reserved2 00InstructionsRestart the diagnostic program.CancellingThis is adiagnosis report, it is not cancelled.

70DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3803 CLB FAILURE

483803 CLB FAILUREMeaningBoth CLB plug-in units in the unit giving the alarm arefaulty.Supplementary information fields1 002 00InstructionsFirst try to restart the test. If this does not help, replacethe CLB plug-in unit of the unitbeing tested. If this does nothelp, perform a switchover and replace the plug-inunit of thestand-by unit. If the alarm is repeated, the fault is in thecablingbetween the CLSU (the CLOS plug-in units) and the CLB ofthe stage. Check the cabling. Change the faulty CLOS plug-in unit,see instructions for replacing plug-inunits.CancellingThis is a diagnosis report, it is not cancelled.


22/37

DN99571044Issue 5-071Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3804 UNKNOWN FAULT IN HARDWARE

Id:0900d805806fd8fe493804 UNKNOWN FAULT IN HARDWAREMeaningA type of fault unknown to the diagnostic program has been detected,for instance the co-occurrence ofmore than one faulty plug-in unitat the same time.Supplementary information fields1 plug-in unit index (SYSB test)2 00InstructionsThe SYSB test:The alarmis caused by the co-occurrence of more than one faulty plug-inunit of the same type in the I/O space, absence of plug-in units or anequipment database error. The type of the plug-in unit is listed inalarm number 3725. Supplementary information field 1 shows the index ofthe faulty plug-in unit first detected.Check the contents of the equipment database with the EQADMI MML program(command WT). Findout if there are extra plug-in units in the subrack.Replace plug-in units AAL, AFS, BEXT, DMADI, DMASI, DMAFC, SERO, SWIF,SWTST and TAPI one by one, and then restart the SYSB partial diagnosiswith the UDU command.The SUB test:The alarm is caused by the co-occurrence of more than one defective SLUor LI plug-in unit at the same time, absence of the EAL, LTEST or SMUCplug-in unit in the equipment database or by a type of fault unknown tothe diagnostic program.Check the contentsof the equipment database with the EQADMI MML program(command WT). Replace plug-in units SUC, SUD, SBMC, SLU and LI in thisorder, and then restart the SUB diagnosis.The GSW test:The alarm is caused by the co-occurrence of more than one defectiveSWCSM or SWSPS plug-in units at the same time, or by a type of faultunknown

to the diagnostic program.You can examine the fault by outputting table ERROR_CTR_TABLE from

72DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3804 UNKNOWN FAULT IN HARDWARE

the marker onto the service terminal with the command:ZOS:*,*,D9,,,1,,6034,,,1,,4A,,1,0.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-073Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3808 EXECUTION ERROR IN PREPROCESSORTEST

Id:0900d805806fd8fe503808 EXECUTION ERROR IN PREPROCES-SOR TESTMeaningAn execution error has occurred in the preprocessor test.Supplementary information fields1 index of preprocessor2 error in elementary diagnosis 00 external loop test 01 processor test 02 watchdog test 03 RAM address test 04 RAM data test 05 check sum test 06 clock signal test 07 timing signal test 08 initial alignment test 09 ROM test 0Ainterrupt test 0B internal loop test 0C dual port RAM test 0DHW filtration test 0E internal test 0F preprocessor cannot be test

edInstructionsReplace the plug-in unit. Restart the test.CancellingThis is a diagnosis report, it is not cancelled.

74DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3809 UNSPECIFIED FAILURE IN PREPROCESSOR TEST

513809 UNSPECIFIED FAILURE IN PREPRO-CESSOR TESTMeaningThe preprocessor has a fa


23/37

ilure which prevents it from answeringeven the first test message.Supplementaryinformation fields1 type of preprocessor: 03 AS7 04 ASS 10LSP 5D AS7_S 5E ASS_S 5F LSP_S 6C AS7_U C6 ET2EC7 ET2E_A C8 ET2E_V 3C5 AS7_A 135 IOCP_A2 index of prepro

cessorInstructionsRestart the test. If the failure recurs, replace the correspondingplug-in unit.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-075Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3810 EXTERNAL LOOP FAILURE IN PREPROCES-SOR TEST

Id:0900d805806fd8fe523810 EXTERNAL LOOP FAILURE IN PRE-PROCESSOR TESTMeaningTheexternal loop test has detected a fault.Supplementary information fields1 type of preprocessor: 03 AS7 04 ASS 10 LSP 5D AS7_S 6CAS7_U 5E ASS_S 5F LSP_S2 preprocessor indexInstructionsThe faul

t is either in one of the preprocessors mentioned in thesupplementary information fields, in the active switching networkinto which the connections have been made, in the PCM circuits, orin the Bus Extender (BEXT) plug-in unit, if equipped.CancellingThis is a diagnosis report, it is not cancelled.

76DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3814 LINE PRINTER FAILURE

533814 LINE PRINTER FAILUREMeaningThe diagnostic program has detected a failurein thealarm line printer unit.Supplementary information fields1 index of theSERO plug-in unit2 error code 01 SERO plug-in unit missing 02 printer cable not connected, printer off line, or printer power off 03 looping error in SERO plug-in unit 04 FIFO error in SERO plug-in unit

05 USART status error in SERO plug-in unit 06 data error in SERO plug-in unit 07 error in incoming interrupt of SERO plug-in unit 08 error in outgoing interrupt of SERO plug-in unitInstructionsError code 02: Check that the unit is connected to the mainssupply, power is on, the intermediate cable

has been correctlyconnected, and the printer is in the state ON LINE.Other errorcodes: Replace the SERO plug-in unit.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-077Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3815 VISUAL DISPLAY UNIT FAILURE

Id:0900d805806fd8fe543815 VISUAL DISPLAY UNIT FAILUREMeaningThe diagnostic program has detected a failure in thevisual display unit.Supplementary information fields1 index of the SERO plug-in unit2 error code 09 SERO plug-in uni

t missing 0A VDU cable not connected, VDU off line, or VDU poweroff 0B looping error in SERO plug-in unit 0C FIFO error in SERO plug-in unit 0D USART status error in SERO plug-in unit 0E data error inSERO plug-in unit 0F error in incoming interrupt of SERO plug-in unit10 error in outgoing interrupt of SERO plug-in unitInstructionsError code 0A:Check that the unit has been connected to the mainssupply, power is on, the intermediate cable has been correctlyconnected, and the VDU is in the state ON LINE.Other error codes: Replace the SERO plug-in unit.CancellingThis is a diagnosisreport, it is not cancelled.


24/37

78DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3818 SBUS FAILURE

553818 SBUS FAILUREMeaningThe own diagnostics of the SBUS supervision bus has detected a faultin the supervision bus, or the diagnostics of the HWAT plug-in unithas detected a fault in the test of the supervision bus.The faulty units can bethe CLAB, the HWAT, or the supervision bus.Supplementary information fields1index of the SBUS 0 = SBUS 0 1 = SBUS 1 2 = both SBUS are found faulty in the test of the supervision bus included in the HWAT test.2 The first byte gives the index of the faulty CLAB plug-in unit The last byte gives the following information of the fault: A1 one CLAB is faulty

A2 more than one CLAB is faulty A3 all CLABs are faultyInstructions Action Note----------------------------------------------------------------------------START o ! 1 2 A1 o---o-----o A1: 1. Replace theCLAB plug-in unit indicated ! ! ! in the supplementary information field 2. ! ! ! 2. Check the wiring and the connectors ! ! END of the supervision bus. ! END ! ! 1 2 3 A2 o---o-----o-----o A2: 1. Checkthe wiring and the connectors ! ! ! ! of the supervision bus. ! ! ! END 2. Replace the CLAB plug-in units, one by

! ! ! one, starting from the index given in the! ! END supplementary information field 2. ! END3. Replace the HWAT plug-in unit.

DN99571044Issue 5-079Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3818 SBUS FAILURE

Id:0900d805806fd8fe ! See instructions for replacing plug-in ! units. ! 1 2 3

A3 o---o-----o-----o A3. 1. Check the wiring and the connectors

! ! ! of the supervision bus. ! ! END 2.Replace the HWAT plug-in unit. ! END See instructions for replacing plug-in END units.

3. Replace the CLAB plug-in units in order.CancellingThis is adiagnosis report, it is not cancelled.

80DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3819 CABLE MISSING

563819 CABLE MISSINGMeaningA diagnostic program has discovered that no cable con

nectsthe DMADI or DMASI plug-in unit to the Winchester disk drive.Supplementaryinformation fields1 index of the plug-in unit2 00InstructionsCheck the cabling between the DMADI or DMASI plug-in unit andthe Winchester disk drive. Enterthe UDU command to restart thediagnostic program.CancellingThis is a diagnosisreport, it is not cancelled.



25/37

21 PREPROCESSOR EXTERNAL LOOP FAILURE

Id:0900d805806fd8fe573821 PREPROCESSOR EXTERNAL LOOP FAILUREMeaningA diagnosis program has detected a fault when testing a plug-inunit by means of an external loop-back. Loop-back is possibleonly with the coaxial Ethernet connector and willfail withother connectors.Supplementary information fields1 index of plug-inunit suspected faulty2 when the plug-in unit is an AC25-S the possible values of this field are: 1 ... 15 status returned by the HPC circuit

20 plug-in unit reset failure 30 the HPC circuitfailed to return an acknowledgement of the success of the

test within the time limitInstructions ActionNote-------------------------------------------

--------------------------------- START o ! ! +---o 1 1. Is the external loop-back device in place? ! !a: yes o a o b b: no ! ! ! o 2 2. Install the external loop-back device. ! ! ! ! ! o 3 3. Run the test again. ! ! ! END ! 4o 4. The tested plug-in unit is faulty.

82DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3821 PREPROCESSOR EXTERNAL LOOP FAILURE


DN99571044Issue 5-083Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3822 SCSI EQUIPMENT FAILURE

Id:0900d805806fd8fe583822 SCSI EQUIPMENT FAILUREMeaningA diagnosis program has detected a fault in the terminalresistors of the SCSI bus, in the cable, or in the SCSIFplug-in unit.Supplementary information fields1 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 missing2 number of theSCSI bus: 00 SCSI bus 0, upper connector on the SCSIF 01 SCSI bus 1, lower connector on the SCSIFInstructionsIf error code = 01: Check that thestrapping on the jumper group of the Disk Drive Adapter (DDAD) is compatiblewith the SCSI address of the device. Check also the address: 0 for the WDUand 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 jumpergroups 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).

84DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3822 SCSI EQUIPMENT FAILURE

If the fault still persists, replace the mass memory unit. If the fault still persists, replace the SCSIF plug-in unit, see instructions for replacingplug-in units.If error code = 03 or 04: Replace both terminal resistors (SCS


26/37

IT), 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.CancellingThisis a diagnosis report, it is not cancelled.

DN99571044Issue 5-085Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3823 PHASE LOCK FAILURE

Id:0900d805806fd8fe593823 PHASE LOCK FAILUREMeaningThe diagnostics of a plug-inunit has detected a fault in the basictiming signal's phase lock. The fault maybe either in the plug-inunit itself or in the basic timing unit.Supplementary information fields1 index of the plug-in unit2 00InstructionsReplace the plug-in unit accused by the diagnostics,and run the test again.CancellingThis is adiagnosis report, it is not cancelled.

86DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3824 DUAL PORT MEMORY FAILURE

603824 DUAL PORT MEMORY FAILUREMeaningDiagnostics has found that the dual port memory is faulty.The faulty plug-in unit may be either the one tested andsuspected faulty, or the one where the memory is locatedphysically (CPXXX).Supplementaryinformation fields1 type of plug-in unit suspected faulty2 index of plug-in unit suspected faultyInstructionsReplace the plug-in unit accused by the diagnosis, and ifnecessary also the CPXXX plug-in unit.Run the diagnostic program again.CancellingThis is a diagnosis report, it is not cancelled.


25 HWAT OR CLAB COMMUNICATION FAILURE

Id:0900d805806fd8fe613825 HWAT OR CLAB COMMUNICATION FAILUREMeaningHWALCO has not received a reply from the HWAT or the CLAB unit.Supplementary information fields1 002 00InstructionsRun the tests of the HWAT and CLAB plug-in units again. After the test,restart the unit, if it can be done without disturbing the functioningof the exchange.CancellingThis is a diagnosis report, it is not cancelled.


0900d805806fd8fe3826 CLOCK FAILURE

623826 CLOCK FAILUREMeaningThe clock signal in the plug-in unit issuing the alarm is faulty.The fault can be in the plug-in unit itself or in the incomingclocksignal.Supplementary information fields1 1 the faulty plug-in unit2 plug-in unit or cable missing2 00Instructions

Action Note---------------------------------------------------------------------------- START o ! +---o 1 1. Is the unit tested an MB? ! ! a: no o a ob b: yes ! ! ! ! ! ! 2 ! o----+ 2. Is there


27/37

a clock alarm in both ! ! ! MB units? ! o a o b a: no ! ! ! b: yes ! ! ! ! ! o 3 3. Check the clock unit. ! ! ! ! ! END ! ! ! o 4 4. Replace thefaulty MB unit. ! ! ! END ! o 5 5. Replace the plug-in unit which caused ! the alarm. END

DN99571044Issue 5-089Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3826 CLOCK FAILURE

Id:0900d805806fd8feCancellingThis is a diagnosis report, it is not cancelled.

90DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3827 PARTIAL POWER FAILURE

633827 PARTIAL POWER FAILUREMeaningThe HWAT unit notifies that one of the two power sources ofthe cartridge is faulty. The back-up unit, if any, has kicked in.Supplementary information fields1 0 the faulty plug-in unit 1plug-in unit or cable missing2 00InstructionsCheck that the power source of t

he unit is ON and, if the valueof supplementary information field 1 is 1, also that the unitexists and that the cabling is in order.If the value of the field is0, then the power source in questionmust be replaced.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-091Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3828 TOTAL POWER FAILURE IN CARTRIDGE

Id:0900d805806fd8fe643828 TOTAL POWER FAILURE IN CAR-TRIDGEMeaningThe HWAT unitserves notice that both power sources are downThe plug-in units in the cartridge

are without power.Supplementary information fields1 0 the faulty plug-in unit 1 plug-in unit or cable missing2 00InstructionsCheck that the power sources of the unit are ON and, if the valueof the supplementary information field is 1, also check that theunits exist and that the cabling is in order.If the field's value is 0, replace the power source.CancellingThis is a diagnosis report, it is not cancelled.

92DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3829 CTU DIAGNOSTIC FAILURE

653829 CTU DIAGNOSTIC FAILUREMeaningA diagnostic program has detected that thereis no tape cassette inthe tape drive, or that there is insufficient blank tapeleft on thecassette for the write/read test, or that the tape drive is missing.Supplementary information fields1 error code: 01 no cassette in the tapedrive 02 not enough room on the tape for the write/read test 03 device is not responding 04 faulty cable2 number of the SCSI bus 00SCSI bus 0, upper connector on SCSIF 01 SCSI bus 1, lower connector on SCSIFInstructionsIf the error code is 01: Place a cassette in the tape driveand wait till the tape has rewound to the beginning and the tape drive has changed to the "on-line" state.If the error code is 02: Replace


28/37

the cassette in the tape drive with a blank one.If the error code is 03:Check that the parameter in the jumper group on the Disk Drive Adapter (DDAD) corresponds to the SCSI address of the device. Check also the SCSIaddress of the device. Restart EDISKD_P, wait a moment and restart also TAPEDR_P. If the fault persists, replace the SCSI Bus Terminals. Ifthe fault persists, replace the SCSI cable. If the fault persists, replace the mass memory unit. If the fault persists, replace the SCSIF plug-inunit.

DN99571044Issue 5-093Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3829 CTU DIAGNOSTIC FAILURE

Id:0900d805806fd8fe See instructions for replacing plug-in units.If the error code is 04: Replace the SCSI cable. If the fault persists, replace the SCSIF plug-in unit. See instructions for replacing plug-in units.CancellingThis is a diagnosis report, it is not cancelled.


0900d805806fd8fe3830 UNSUCCESSFUL HWILIB INQUIRY663830 UNSUCCESSFUL HWILIB INQUIRYMeaningThe HWILIB inquiry was unsuccessful.Supplementary information fields1 lower word of the status restored by HWILIB2upper word of the status restored by HWILIBInstructionsCheck that the plug-in

units needed by partial diagnostics areequipped correctly and exist in the equipment database.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-095Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3832 MISSING DISK EQUIPMENT

Id:0900d805806fd8fe673832 MISSING DISK EQUIPMENTMeaningThe diagnostic program has noticed that a DMA plug-in unit,a cable or a disk unit is missing or faulty.Supplementary information fields1 general error code of the system 33H = NO_EQUIPMENT_EC2 no significanceInstructionsCheck that the DMADI or the DMASI plug-in unit is in place.Check that the CLH or the CLF cable is in place.Check the existence and power flow of the disk-unit.CancellingThis is a diagnosis report, it is not cancelled.


0900d805806fd8fe3833 CLAB OR CABLE FAULTY

683833 CLAB OR CABLE FAULTYMeaningA clock alarm is active on the SWCSM plug-in unit(s) of theswitching network.Supplementary information fields1 index of SWCOP-S plug-in unit2 index of SWCSM plug-in unitInstructionsCheck first the clock signal's cabling from the CLAB plug-in unitto the switching network. If it isin order, try replacing theCLAB plug-in unit. Run the test program again.CancellingThis is a diagnosis report, it is not cancelled.


29/37

DN99571044Issue 5-097Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3834 CONNECT ERROR IN DIAGNOSIS PROGRAM

Id:0900d805806fd8fe693834 CONNECT ERROR IN DIAGNOSIS PROGRAMMeaningThe diagnostic program has been interrupted because no successfultest connections were made (either S3RRAP or SWICOP has respondedwith an error acknowledgement).Supplementary information fields1 00002 0000Instructions Action Note---------------------------------------------------------------------------- START o ! +---o 1

1. Does the unit to be tested have ! ! a group switch? ! ! (e.g. M, CAC, ANCU, MCMU) o a o b a: no! ! b: yes ! ! ! ! o 2 ! 2. Check the routing of the plug-in ! ! unit that is tested. Check whether ! ! there is overload at the Marker (M). ! ! ! ! o 3! 3. Run the test again. ! ! ! ! END o 4 4. DX220: Start partial diagnosis GSW. UDU:M,X:GSW; ! Other: Startpartial diagnosis SWI. E.g. UDU:CAC,X:SWI; ! ! +---o 55. Is the result another diagnosis? ! ! a: yes, follow the instructions o a o b of the diagnosis in question.

98DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3834 CONNECT ERROR IN DIAGNOSIS PROGRAM

! ! b: no o ! END ! ! o 6 6. Fill in a Problem Report. ! o ENDCancellingThis is a diagnosisreport, it is not cancelled.

DN99571044Issue 5-099Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3835 MODULE LOADING ERROR IN TEST PRO-GRAM

Id:0900d805806fd8fe703835 MODULE LOADING ERROR IN TEST PROGRAMMeaningLoading a loadable test program has failed.Supplementary information fields1 the most meaningful part of the error status of message 0X0E1642 the least meaningful part of the error status of message 0X0E164InstructionsStart the message monitoring of the DOCTOR process with theservice terminal command ZOQ:D9 and runthe partial diagnosiswanted.Observe the field load_module_name, whose length iseightascii characters, of the message 0x837. This field containsthe name of themodule to be loaded, without the extension.For example, the module DISA71GX is presented in the messagein hexadecimals 44 49 53 41 37 31 47 58. All loadable modulesof the diagnostic programs should begin with the string DIS,i.e. the field load_module_name can be located in the messageby searching for the hexadecimals 44, 49 and 53.Give the service terminal command ZMX:W0-BLCODE/DIS* to checkwhethe

r the name of the module found in the message, with theextension IMG, is locatedon 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 inthe message 0x837, fill in aProblem Report. The failure isthen located either in the file LEQURI, whose number is07F10000, or on disks W0 or W1.If the disks do contain a message with thesame name as in themessage 0x837, but the text diagnosis 0x3835 is still given,fill in a Problem Report. In that case the failure is in theloading system.The ascii characters representing decimals and upper-casealphabets are presented in the following table in hexadecimals:


30/37

100DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3835 MODULE LOADING ERROR IN TEST PRO-GRAM

decimal ascii alphabet ascii alphabet ascii 0 0x30 A 0x41 N 0x4E 1 0x31 B 0x42 O 0x4F 2 0x32 C 0x43 P0x50 3 0x33 D 0x44 Q 0x51 40x34 E 0x45 R 0x52 5 0x35 F0x46 S 0x53 6 0x36 G 0x47 T0x54 7 0x37 H 0x48 U 0x55 80x38 I 0x49 V 0x56 9 0x39 J

0x4A W 0x57 K 0x4BX 0x58 L 0x4C Y 0x59

M 0x4D Z 0x5ACancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-0101Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3838 TCSM FAILURE

Id:0900d805806fd8fe713838 TCSM FAILUREMeaningThe diagnostic program run by the BSC has found the TCSM unit faulty.Supplementary information fields1 TCSM2 plug-in units: C6 'ET2E failure' D9 'ET2A failure' DA 'TRCO failure' DB 'TR12 failure' DC 'TR16 failure' EB 'ET2E failure' EC 'ET2E failure' ED 'ET2E failure' 142 'TRCO failure' 17C 'ET2E failure' 17D 'ET2E failure' 17E 'ET2A failure' TCSM3i plug-in units: E0 'CL3TG failure' 195 'TR3E failure' 196 'TR3A failure' 19B 'ET16 failure'2 index of the plug-in unit suspected.InstructionsFor instructions, seeInstructions for Replacing Plug-in Units.CancellingThis is a diagnosis report,it is not cancelled.

102DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3839 PLUG-IN UNIT IN WRONG TRACK

723839 PLUG-IN UNIT IN WRONG TRACKMeaningDiagnostic program has detected that aplug-in unit is not in thetrack indicated by the equipment database.Supplementary information fields1 track where the plug-in unit is2 plug-in unit type numberInstructionsCheck the equipment description with the EQADMI MML, command classWT. Move the plug-in unit into the right track.CancellingThis is a diagnosisreport, it is not cancelled.

DN99571044Issue 5-0103Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3840 SEVERAL PLUG-IN UNITS NOT FOUND

Id:0900d805806fd8fe733840 SEVERAL PLUG-IN UNITS NOT FOUNDMeaningThe diagnostic program has detected that two or moreplug-in units are missing or are not in thetrackindicated by the equipment database.Supplementary information fields1 the first track from where the diagnostic program did not find the right kindof plug-in unit2 00Instructions1. Check the equipment description using the W


31/37

T 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.CancellingThis is a diagnosis report, it is not cancelled.

104DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3843 PARITY ERROR IN MEMORY

743843 PARITY ERROR IN MEMORYMeaningThe system has detected a parity error in aRAM test.Supplementary information fields1 00002 0000InstructionsReplace the CPU plug-in unit and then start the RAM partialdiagnosis with the MML commandUDU.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-0105Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3844 SCSI EQUIPMENT FAILURE

Id:0900d805806fd8fe753844 SCSI EQUIPMENT FAILUREMeaningA diagnosis program has detected a fault in the terminalresistors of the SCSI bus, in the cable, or in th

e CPXXXplug-in unit.Supplementary information fields1 error code: 01 the presence signal, corresponding to the SCSI address of a mass memory device, is passive 02 a mass memory 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 missing2 number of the SCSI bus: 00 SCSI bus 0, upper SCSI connector onthe front panel of the CP5XX 01 SCSI bus 1, lower SCSI connectoron the front panel of the CP5XXInstructionsIf error code = 01: Checkthat the strapping on the jumper group of the disk adapters (DDAD, WDAD, orFDAD) 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, followthe instructions for error code 2.If error code = 02: Check that the strappings on the jumper groups of all mass memory adapters (DDAD, WDAD, FDAD and

CTAD) connected to the SCSI bus concerned correspond to the SCSI address ofthe device concerned. If the fault still persists, replace the terminal resistors (SCSIT) of the SCSI bus. If the fault still persists, replace the SCSI cable. If the fault still persists, replace the mass memory unit. If the fault still persists, replace the CPXXX plug-in unit. See instructions forreplacing plug-in units.

106DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3844 SCSI EQUIPMENT FAILURE

If error code = 03 or 04: Replace both terminal resistors (SCSIT), the SCSI cable, and the CPXXX 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.CancellingThis is a diagnosis report, it is not cancelled.


32/37

DN99571044Issue 5-0107Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3845 CTU DIAGNOSTIC FAILURE

Id:0900d805806fd8fe763845 CTU DIAGNOSTIC FAILUREMeaningA diagnosis program has detected that there is no tapecassette in the tape drive, or that there is insufficientblank tape left on the cassette for a write/read test, orthat the tape drive is missing.Supplementary information fields1 error code: 01 no cassette in the tape drive 02 not enough room on the tape for the write/read test 03 device is not responding 04 faulty cable2 number of the SCSI bus: 00 SCSI bus 0, upper connector on the CPXXX 01 SCSI bus 1, lower connector on the CPXXXInstructionsIf error code = 01: Insert a cassette into the drive and wait for the tape to rewind to the beginning and for the drive to come online.If error code = 02: Replace the cassette in the tape drivewith a blank one.If error code = 03: Check that the strappings on the jumpergroups of the Cassette Tape Adapter (CTAD) corresponds to the SCSI address of the device. Check also the SCSI address of the device. Restart EDISKD_P, wait for a while and restart also TAPEDR_P. If the fault persists, replace the terminal resistors (SCSIT) of the SCSI bus. If the fault still persists, replace the SCSI cable. If the fault still persists, replace the mass memory unit. If the fault still persists, replace the CPXXX plug-in unit. See instructions for replacing plug-in units.

108DN99571044Issue 5-0Nokia Siemens Networks SGSN Diagnosis Reports(3700-3999)Id:0900d805806fd8fe3845 CTU DIAGNOSTIC FAILURE

If error code = 04: Replace the SCSI cable. If the fault persists, replacethe CPXXX plug-in unit. See instructions for replacing plug-in units.CancellingThis is a diagnosis report, it is not cancelled.

DN99571044Issue 5-0109Nokia Siemens Networks SGSN Diagnosis Reports (3700-3999)3849 SCSI HARDWARE FAILURE

Id:0900d805806fd8fe773849 SCSI HARDWARE FAILUREMeaningThe diagnosis progr

Ned Alarms

Documents