rsu

Nonstandard MaintenanceAccess

NM:RSU

A30828-X1170-N120-1-7620

2 A30828-X1170-N120-1-7620

NM:RSU Nonstandard MaintenanceAccess

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts may also have elevated operating temperatures.Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty 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 complywith the applicable safety standards.

The same text in German:Wichtiger Hinweis zur ProduktsicherheitIn elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teileknnen auch eine hohe Betriebstemperatur aufweisen.Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen undSachschden fhren.Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert undwartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gertemssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:All designations used in this document can be trademarks, the use of which by third parties for theirown purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2002.Issued by the Information and Communication Networks GroupHofmannstrae 51D-81359 Mnchen

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30828-X1170-N120-1-7620 3


NM:RSU

Reason for UpdateSummary: First Edition

Details:

Chapter/Section Reason for Update

Issue HistoryIssueNumber

Date of issue Reason for Update

4 A30828-X1170-N120-1-7620


A30828-X1170-N120-1-7620 5


NM:RSU

This document consists of a total of 71 pages. All pages are issue 1.

Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 References to Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Configuration, Diagnosis, Routine Test . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Routine test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Diagnosis Fault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Output mask of diagnosis fault report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1.1 Interpretation of the output mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Description of faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2.1 RSUC CURRENT CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2.2 RSUC BACKUP CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2.3 RSUC CHECKSUM ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2.4 RSUC MUNICH32 DEVICE DRIVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.5 RSUC MUNICH32 CHANNEL INTERNAL LOOP . . . . . . . . . . . . . . . . . . . 143.2.6 RSUC NOT RESPONDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.7 RSUC FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.8 MH CURRENT CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.9 MH BACKUP CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.10 MH MUNICH32 DEVICE DRIVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.11 MH MUNICH32 CHANNEL INTERNAL LOOP . . . . . . . . . . . . . . . . . . . . . . 153.2.12 MH NOT RESPONDING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.13 MH FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.14 COMMUNICATION WITH UNIT LOST AFTER RECOVERY. . . . . . . . . . . 163.2.15 UNIT CONFIGURATION CHANGED DURING DIAGNOSIS . . . . . . . . . . . 163.2.16 UNIT RECOVERY DURING DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.17 INVALID UNIT TRANSIENT STATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.18 INVALID UNIT SEMIPERMANENT STATE . . . . . . . . . . . . . . . . . . . . . . . . 163.2.19 INVALID TEST TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.20 DIAGNOSIS ALREADY RUNNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.21 DIU UP CORE TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.22 DIU BOOT FW CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.23 DIU BACKUP CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.24 DIU CURRENT CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.25 DIU RAM CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.26 DIU RAM READ/WRITE TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.27 DIU NOT RESPONDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.28 DIU CLOSE/OPEN LOOP REQUEST FAILURE . . . . . . . . . . . . . . . . . . . . 183.2.29 DIU/TSI CHANNEL LOOP TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.30 DIU FAILED TO START DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.31 DIU FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.32 TSIM CHANNEL LOOP TEST FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6 A30828-X1170-N120-1-7620


3.2.33 TSIM NOT RESPONDING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.34 TSIM TOTAL FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.35 TSIM PARTIAL FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.36 TSIM FEPROM FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 RSU Standard Fault Reports (STAFU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 RSU01-0000 BASE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 RSU02-0000 MH FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.3 RSU03-0000 AMUX FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.4 RSU04-0000 DIU FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.5 RSU05-0000 RSU ISOLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.6 RSU06-0000 MANUAL STAND ALONE SERVICE . . . . . . . . . . . . . . . . . . . 254.7 RSU08-0000 AUTONOMOUS SAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.8 RSU09-0000 TOTAL FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.9 RSU10-0000 UNIT UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.10 RSU11-0000 CLOCK FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.11 RSU12-0000 RAM FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.12 RSU13-0000 LAYER 3 LOOPBACK FAILURE . . . . . . . . . . . . . . . . . . . . . . 414.13 RSU14-0000 PERMANENT LOOPBACK FAILURE . . . . . . . . . . . . . . . . . . 444.14 RSU15-0000 SUBUNIT 2.1 RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . 464.15 RSU16-0000 SUBUNIT 2.2 RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . 484.16 RSU17-0000 LOAD FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.17 RSU18-0000 SOFTWARE EXCHANGE FAILURE . . . . . . . . . . . . . . . . . . . 524.18 RSU19-0000 UNIT FAILURE DURING RECOVERY . . . . . . . . . . . . . . . . . 544.19 RSU20-0000 RSU SIDEDOOR HSL ALARM . . . . . . . . . . . . . . . . . . . . . . . 554.20 RSU70-0000 MINOR SELF TEST FAILURE. . . . . . . . . . . . . . . . . . . . . . . . 564.21 RSU71-0000 TSIM CROSSWRITE FAILURE . . . . . . . . . . . . . . . . . . . . . . . 584.22 RSU72-0000 CLOCK SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.23 RSU73-0000 CROSS CHANNEL FAILURE . . . . . . . . . . . . . . . . . . . . . . . . 62

5 RSU74-0000 RSU PCM FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.1 Description of the PCM FAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.1 CARRIER FAULT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.2 FAULT MONITORING OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.3 AIS IN PULSE FRAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.4 LOSS OF PULSE FRAME ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.5 FAS ERR THRESH EXCE'D 10 EXP-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1.6 LOSS OF MULTI FRAME ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1.7 CODE VIOL. THRESHOLD EXCEEDED. . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1.8 LOSS OF INCOMING SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.9 AIS IN MULTI FRAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.10 SLIP THRESHOLD EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.11 REMOTE ALARM IN PULSE FRAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.12 REMOTE ALARM IN MULTI FRAME

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6 Fault Reports during Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.1 ABORT BY CONF-SCHEDULER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.2 NOT ALLOWED DUE TO LOSS OF REDUNDANCY . . . . . . . . . . . . . . . . . 70

A30828-X1170-N120-1-7620 7


NM:RSU

6.3 INVALID CURRENT CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.4 ABORT BY STOP COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716.5 NO RESPONSE FROM RSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716.6 HARDWARE FAULT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8 A30828-X1170-N120-1-7620


A30828-X1170-N120-1-7620 9


NM:RSU

1 Introduction

1.1 GeneralThe information in this manual, NM:RSU, is intended to support nonstandard mainte-nance in the event of RSU faults.An RSU hardware fault can normally be cleared using the procedures contained inmaintenance manual MMN:RSU. The Nonstandard Maintenance documents for RSUare not needed in any of these cases.Only if the aforementioned procedures are unsuccessful is it necessary for a systemspecialist to carry out fault clearance. To assist the specialist, NM:RSU contains addi-tional information on each type of fault.The documents listed in the next section are also important for nonstandard mainte-nance.

1.2 References to Additional Documentation Of particular importance for Nonstandard Maintenance is the manual Construction;

the section on Racks offers an overview of the racks containing RSU frames and thefuse assignments. The section on Frames shows the layout of RSU frames and thestandard cabling.

The Documentation Overview contains detailed information on all general aspectsof fault clearance.

When pulling or inserting modules and cables it is important to observe the valid reg-ulations relating to electrostatic-sensitive components and the Safety Instructions forpersonnel and products (EN60950/IEC60950).

10 A30828-X1170-N120-1-7620


2 Configuration, Diagnosis, Routine Test

2.1 ConfigurationThe RSU equipment that has to be configured (see Fig. 2.1) includes: RSUC AMUX MH DIU240 PDC

Fig. 2.1 Block diagram of the RSU

2.2 DiagnosisDiagnosis is used to confirm the fault-free operation of a module of the RSU equipment,as well as to confirm and identify faults down to module level.There are three diagnosis levels in the RSU: SELF CHECK, QUICK CHECK and ALLCHECK. A distinction is also made between automatic diagnosis and manual diagnosis.

Automatic diagnosis SELF CHECK

This is the 1st diagnosis level. Diagnosis is initiated by a processor recovery ofRSUC, MH, TSIM or DIU240. Runtime: 2 seconds.

QUICK CHECKThis is the 2nd diagnosis level. Diagnosis is initiated by a power-up on the module.This diagnosis includes the SELF CHECK and a memory check for RSUC, MH,TSIM or DIU240. Runtime: 30 seconds.

SN0

SN1

Side0

Side1

Side0

Side1

RTI HTI

TSI

TSI

TSI

TSI

DIU240

DIU240

DIU240

DIU240

RSU

CR

SUC

RSU

CR

SUC

MH

MH

MH MH

MH

MH

MH

MHl l l

l l

l

l l l

l l l

l

l

l

l

l

l

l

l

l

l l

ll

l l

LTG

LTG

l l

l

l l

ll

l l

AMUX

AMUX

AMUX

AMUX

AMUX

AMUX

AMUX

AMUX

TSIM

TSIM

TSIM

TSIM

RSU Host

l l l

A30828-X1170-N120-1-7620 11


NM:RSU

Manual diagnosis ALL CHECK

This is the 3rd diagnosis level. Diagnosis is started by command input on the OMT.The unit to be diagnosed must be out of service, i.e. it must be in operating stateMBL. This is the most comprehensive function test, including a test of all memories.The maximum runtime is 5 minutes.The following diagnoses are possible: Diag All. (entire RTI or HTI side Diag Base units. (RSUC, AMUX0 and TSIM) AMUX. (individual AMUXs from 1-7) MH. (individual MHs from 0-7) DIU240. (individual DIU240 from 0-23)

2.3 Routine testThe routine test is a periodic test of the RSU equipment units. It is controlled by the soft-ware and runs with lowest priority. The following tests are performed: RSUC PERIODIC CHECKSUM TEST RSU CORE PLANE PERIODIC LAYER 3 COMMUNICATION LOOP TEST RSU CORE PLANE PERMANENT LOOPBACK CHANNEL MONITOR TEST

12 A30828-X1170-N120-1-7620


3 Diagnosis Fault Report

3.1 Output mask of diagnosis fault reportFAULT IDENTIFICATION: @########################

FAULT LOCATION:

RSU NUMBER : @##RSU NAME : @#######RSU TYPE : @##RSU SIDE : @#

UNIT TYPE NUMBER PDC REASONS---------+------+----+---------------------------------------------

@####### @# @# @############################################

3.1.1 Interpretation of the output mask

FAULT IDENTIFICATION:BASE FAILURETSIM FAILUREAMUX FAILUREMH FAILUREDIU FAILUREPDC FAILURETSIM-AMUX 184 MBS FAILURECP FAILURE

REASONSRSUC fault RSUC CURRENT CHECKSUM RSUC BACKUP CHECKSUM RSUC CHECKSUM ERRORS RSUC MUNICH32 DEVICE DRIVER RSUC MUNICH32 CHANNEL INTERNAL LOOP RSUC NOT RESPONDING RSUC FAILUREMH fault MH CURRENT CHECKSUM MH BACKUP CHECKSUM MH MUNICH32 DEVICE DRIVER MH MUNICH32 CHANNEL INTERNAL LOOP MH NOT RESPONDING MH FAILUREDiagnosis aborted COMMUNICATION WITH UNIT LOST AFTER RECOVERY UNIT CONFIGURATION CHANGED DURING DIAGNOSIS UNIT RECOVERY DURING DIAGNOSIS

A30828-X1170-N120-1-7620 13


NM:RSU

INVALID UNIT TRANSIENT STATE INVALID UNIT SEMIPERMANENT STATE INVALID TEST TYPE DIAGNOSIS ALREADY RUNNINGDIU240 fault DIU UP CORE TEST DIU BOOT FW CHECKSUM DIU BACKUP CHECKSUM DIU CURRENT CHECKSUM DIU RAM CHECKSUM DIU RAM READ/WRITE TEST DIU NOT RESPONDING DIU CLOSE/OPEN LOOP REQUEST FAILURE DIU/TSI CHANNEL LOOP TEST DIU FAILED TO START DIAGNOSIS DIU DS1 FAILURE DIU FAILURETSI fault TSIM CHANNEL LOOP TEST FAILURE TSIM NOT RESPONDING TSIM TOTAL FAILURE TSIM PARTIAL FAILURE TSIM FEPROM FAILURE TSIM FAILURE

3.2 Description of faults

3.2.1 RSUC CURRENT CHECKSUMA checksum test is performed for the current online software. The checksum test formsnew checksums from the stored current online software and compares these with thestored checksums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:RSUC CURRENT CHECKSUM.

3.2.2 RSUC BACKUP CHECKSUMA checksum test is performed for the backup software. The checksum test forms newchecksums from the stored backup software and compares these with the stored check-sums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:RSUC BACKUP CHECKSUM.

3.2.3 RSUC CHECKSUM ERRORSA RAM checksum test is performed. The RAM checksum test forms new checksumsfrom the memory contents and compares these with the stored checksums. The newlycalculated checksums must match the stored checksums.

14 A30828-X1170-N120-1-7620


If a checksum error is detected, a diagnosis fault report is produced with the REASON:RSUC CHECKSUM ERRORS.

3.2.4 RSUC MUNICH32 DEVICE DRIVERAfter receipt of the command "CMD DRIVER TEST" this test is performed byMUNICH32X.The data in the readable MUNICH32 register is compared with the data stored in theRAM. The local data area is checked via CRC. The result of the diagnosis is reported inthe message "ACK DRIVER TEST". In the event of an error, a diagnosis fault report isproduced with the REASON: RSUC MUNICH32 DEVICE DRIVER.

3.2.5 RSUC MUNICH32 CHANNEL INTERNAL LOOPIf the driver test is completed without errors, an internal loop test is performed channelby channel on the 32 channels of MUNICH32x. A message is sent via a free channeland received again via the loop.

The information about the message sent is recorded in a descriptor and this is stored ina table of MUNICH32. A table is reserved for each of the 32 channels. There is also atable for the receive side. When a message is received, the information is entered in thistable. The data in the two tables is compared. In the event of an error a diagnosis faultreport is produced with the REASON: RSUC MUNICH32 CHANNEL INTERNAL LOOP.

3.2.6 RSUC NOT RESPONDINGAll tests, such as checksum tests, the driver test and the loop test of the channels ofMUNICH32 are monitored by timers. If these timers expire before a test result is re-ceived, a diagnosis fault report is produced with the REASON: RSUC NOT RESPOND-ING.

3.2.7 RSUC FAILUREErrors that are detected by RSUC diagnosis but cannot be clearly assigned lead to adiagnosis fault report with the REASON:RSUC FAILURE.

1

&enable loop forchannel x

RECEIVE DATA

TRANSMIT DATAl

A30828-X1170-N120-1-7620 15


NM:RSU

3.2.8 MH CURRENT CHECKSUMA checksum test is performed for the current online software. The checksum test formsnew checksums from the stored current online software and compares these with thestored checksums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:MH CURRENT CHECKSUM.

3.2.9 MH BACKUP CHECKSUMA checksum test is performed for the backup software. The checksum test forms newchecksums from the stored backup software and compares these with the stored check-sums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:MH BACKUP CHECKSUM.

3.2.10 MH MUNICH32 DEVICE DRIVERAfter receipt of the command "CMD DRIVER TEST" this test is performed byMUNICH32X.The data in the readable MUNICH32 register is compared with the data stored in theRAM. The local data area is checked via CRC. The result of the diagnosis is reported inthe message "ACK DRIVER TEST". In the event of an error, a diagnosis fault report isproduced with the REASON: MH MUNICH32 DEVICE DRIVER.

3.2.11 MH MUNICH32 CHANNEL INTERNAL LOOPIf the driver test is completed without errors, an internal loop test is performed channelby channel on the 32 channels of MUNICH32x. A message is sent via a free channeland received again via the loop.

The information about the message sent is recorded in a descriptor and this is stored ina table of MUNICH32. A table is reserved for each of the 32 channels. There is also atable for the receive side. When a message is received, the information is entered in thistable. The data in the two tables is compared. In the event of an error a diagnosis faultreport is produced with the REASON: MH MUNICH32 CHANNEL INTERNAL LOOP.

1

&enable loop forchannel x

RECEIVE DATA

TRANSMIT DATAl

16 A30828-X1170-N120-1-7620


3.2.12 MH NOT RESPONDINGThe checksum tests, the driver test and the loop test of the channels of MUNICH32 aremonitored by timers. If these timers expire before a test result is received, a diagnosisfault report is produced with the REASON: MH NOT RESPONDING.

3.2.13 MH FAILUREErrors that are detected by MH diagnosis but cannot be clearly assigned lead to a diag-nosis fault report with the REASON: MH FAILURE.

3.2.14 COMMUNICATION WITH UNIT LOST AFTER RECOVERYAfter an RSU recovery, communication was no longer possible between diagnosis con-trol and the unit to be diagnosed. Diagnosis is aborted and a diagnosis fault report isproduced with the REASON: COMMUNICATION WITH UNIT LOST AFTER RECOV-ERY

3.2.15 UNIT CONFIGURATION CHANGED DURING DIAGNOSISThe unit configuration was changed during diagnosis. Diagnosis is aborted and a diag-nosis fault report is produced with the REASON:UNIT CONFIGURATION CHANGEDDURING DIAGNOSIS

3.2.16 UNIT RECOVERY DURING DIAGNOSISRecovery was performed during diagnosis. Diagnosis is aborted and a diagnosis faultreport is produced with the REASON:UNIT RECOVERY DURING DIAGNOSIS

3.2.17 INVALID UNIT TRANSIENT STATEThe transient state of the unit to be diagnosed does not allow diagnosis. Diagnosis isaborted and a diagnosis fault report is produced with the REASON: INVALID UNITTRANSIENT STATE

3.2.18 INVALID UNIT SEMIPERMANENT STATEThe semipermanent state of the unit to be diagnosed does not allow diagnosis. Diagno-sis is aborted and a diagnosis fault report is produced with the REASON: INVALID UNITSEMIPERMANENT STATE

3.2.19 INVALID TEST TYPEInvalid test type for diagnosis. Diagnosis is aborted and a diagnosis fault report is pro-duced with the REASON: INVALID TEST TYPE

3.2.20 DIAGNOSIS ALREADY RUNNINGFor a hardware unit, only one diagnosis may be performed at a time. If diagnosis is al-ready in progress, a diagnosis fault report is produced with the REASON: DIAGNOSISALREADY RUNNING

A30828-X1170-N120-1-7620 17


NM:RSU

3.2.21 DIU UP CORE TESTIn diagnosis of the DIU240 an error was detected in the microprocessor core test. Diag-nosis is aborted and a diagnosis fault report is produced with the REASON: DIU UPCORE TEST

3.2.22 DIU BOOT FW CHECKSUMA checksum test is performed for the BOOT firmware. The checksum test forms newchecksums from the BOOT firmware and compares these with the stored checksums.The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:DIU BOOT FW CHECKSUM.

3.2.23 DIU BACKUP CHECKSUMA checksum test is performed for the backup firmware. The checksum test forms newchecksums from the stored backup firmware and compares these with the stored check-sums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:DIU BACKUP CHECKSUM.

3.2.24 DIU CURRENT CHECKSUMA checksum test is performed for the current firmware. The checksum test forms newchecksums from the stored current firmware and compares these with the stored check-sums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:DIU CURRENT CHECKSUM.

3.2.25 DIU RAM CHECKSUMA RAM checksum test is carried out. The RAM checksum test forms new checksumsfrom the memory contents and compares these with the stored checksums. The newlycalculated checksums must match the stored checksums..If a checksum error is detected, a diagnosis fault report is produced with the REASON:DIU RAM CHECKSUM.

3.2.26 DIU RAM READ/WRITE TESTA read/write test is performed for the RAM of the DIU240. For this purpose, test patternsare written into the memory, read out again and compared. The test patterns that areread out must match the original test patterns.If they do not match, a diagnosis fault report is produced with the REASON: DIU RAMREAD/WRITE TEST.

18 A30828-X1170-N120-1-7620


3.2.27 DIU NOT RESPONDINGAll tests, such as checksum tests, RAM test etc. are monitored by timers. If these timersexpire before a test result is received, a diagnosis fault report is produced with the REA-SON: DIU NOT RESPONDING.

3.2.28 DIU CLOSE/OPEN LOOP REQUEST FAILUREFor the DIU channel test, the command CMD_TS_LOOP is used to insert and then re-open loops for the channels that are to be tested. The commands are timed.In the event of an error a diagnosis fault report is produced with the REASON: DIUCLOSE/OPEN LOOP REQUEST FAILURE.

3.2.29 DIU/TSI CHANNEL LOOP TESTAfter the loop has been inserted for the channel to be tested, test patterns are sent overthe channel and received again via the loop. The transmitted and received test patternsmust match.If the patterns do not match, a diagnosis fault report is produced with the REASON:DIU/TSI CHANNEL LOOP TEST.

3.2.30 DIU FAILED TO START DIAGNOSISThe DIAG DIU request to DIU240 is timed. If the DIU does not respond before the timerexpires, a diagnosis fault report is produced with the REASON: DIU FAILED TO STARTDIAGNOSIS.

3.2.31 DIU FAILUREErrors that are detected by MH diagnosis but cannot be clearly assigned lead to a diag-nosis fault report with the REASON: DIU FAILURE.

3.2.32 TSIM CHANNEL LOOP TEST FAILUREIn the channel loop test, test patterns are sent via a selected channel to the DIU240. TheDIU240 sends these test patterns back to the TSIM via a loop. The test patterns sent bythe TSIM are compared with the received test patterns. If the patterns do not match, adiagnosis fault report is produced with the REASON: TSIM CHANNEL LOOP TESTFAILURE.

3.2.33 TSIM NOT RESPONDINGAll tests, such as checksum tests, RAM test etc. are timed. If these timers expire beforea test result is received, a diagnosis fault report is produced with the REASON: TSIMNOT RESPONDING.

3.2.34 TSIM TOTAL FAILUREA diagnosis fault report with the REASON: TSIM TOTAL FAILURE is produced in thefollowing cases:Checksum error in the RAM test.

A30828-X1170-N120-1-7620 19


NM:RSU

Failure of the RSU Clock Generator RCG.All HDLC links to the AMUXs are defective.ASIC defective.EMU defective, e.g. EMU inputs are defective.

3.2.35 TSIM PARTIAL FAILUREA diagnosis fault report with the REASON: TSIM PARTIAL FAILURE is produced in thefollowing cases:Failure of a single AMUX.Failure of individual 184 Mbit links between AMUX and TSIM.ASIC failure (central error message, error counter overflow).Modules (AMUX) described in the command but non-existent.

3.2.36 TSIM FEPROM FAILUREA checksum test is performed for the boot, backup and current firmware. The checksumtest forms new checksums from the stored firmware and compares these with the storedchecksums. The newly calculated checksums must match the stored checksums.If a checksum error is detected, a diagnosis fault report is produced with the REASON:TSIM FEPROM FAILURE.

20 A30828-X1170-N120-1-7620


4 RSU Standard Fault Reports (STAFU)4.1 RSU01-0000 BASE FAILURE

Fault report:

DEFAULT EQUIPMENT ALARM MMN:RSU01-0000 ORIGINAL ALARM MESSAGE WAS LOST.

ALARM PRIORITY: @####### PROBABLE CAUSE: PROCESSOR PROBLEM SPECIFIC PROBLEM: NOT AVAILABLE MESSAGE NUMBER: @#### ALARM IDENTIFICATION: CLASS=RSUBASE RSU=999 SIDE=9

System reactions: The fault is reported as a major alarm for the object SN. The fault is entered in the AM.ALARM.

Description:In abort situations and during resource bottlenecks, message loss may occur. This re-sults in inconsistencies between the signaling of alarms and advisories and the actualoperating state.In order to counteract this, after each new recovery, after transmission losses in the in-terface SAOUT and after overflow of the alarm file, verification of the alarm and advisorycontrol data, the AM.ALARM and the system status information is performed by com-parison with reference databases of the system alarming user.The absence of an alarm entry in the alarm control data is corrected by generating a de-fault alarm.In the present case, BASE FAILURE, one of the basic equipment units RSUC, AMUX0or TSIM, is out of service or faulty.In accordance with the entry CLASS=object and the logical address specified after it,fault clearance can be performed.Using the commandsDISP ALARMandSRCH ALARMfurther symptoms can be determined.

A30828-X1170-N120-1-7620 21


NM:RSU

4.2 RSU02-0000 MH FAILUREFault report:


ALARM PRIORITY: @####### PROBABLE CAUSE: PROCESSOR PROBLEM SPECIFIC PROBLEM: NOT AVAILABLE MESSAGE NUMBER: @#### ALARM IDENTIFICATION: CLASS=RSUMH RSU=999 UNITNO=99 SIDE=9


Description:In abort situations and during resource bottlenecks, message loss may occur. This leadsto inconsistencies between the signaling of alarms and advisories and the actual oper-ating state.In order to counteract this, after each new recovery, after transmission losses in the in-terface SAOUT and after overflow of the alarm file, verification of the alarm and advisorycontrol data, the AM.ALARM and the system status information is performed by com-parison with reference databases of the system alarming user.The absence of an alarm entry in the alarm control data is corrected by generating a de-fault alarm.In the present case, MH FAILURE, an RSU MH is out of service or faulty.In accordance with the entry CLASS=object and the logical address specified after it,fault clearance can be performed.Using the commandsDISP ALARMandSRCH ALARMfurther symptoms can be determined.

22 A30828-X1170-N120-1-7620


4.3 RSU03-0000 AMUX FAILUREFault report:


ALARM PRIORITY: @####### PROBABLE CAUSE: MULTIPLEXER PROBLEM SPECIFIC PROBLEM: NOT AVAILABLE MESSAGE NUMBER: @#### ALARM IDENTIFICATION: CLASS=RSUAMUX RSU=999 UNITNO=99 SIDE=9


Description:In abort situations and during resource bottlenecks, message loss may occur. This leadsto inconsistencies between the signaling of alarms and advisories and the actual oper-ating state.In order to counteract this, after each new recovery, after transmission losses in the in-terface SAOUT and after overflow of the alarm file, verification of the alarm and advisorycontrol data, the AM.ALARM and the system status information is performed by com-parison with reference databases of the system alarming user.The absence of an alarm entry in the alarm control data is corrected by generating a de-fault alarm.In the present case, AMUX FAILURE, an RSU AMUX is out of service or faulty.In accordance with the entry CLASS=object and the logical address specified after it,fault clearance can be performed.Using the commandsDISP ALARMandSRCH ALARMfurther symptoms can be determined.

A30828-X1170-N120-1-7620 23


NM:RSU

4.4 RSU04-0000 DIU FAILUREFault report:


ALARM PRIORITY: @####### PROBABLE CAUSE: TRUNK CARD PROBLEM SPECIFIC PROBLEM: NOT AVAILABLE MESSAGE NUMBER: @#### ALARM IDENTIFICATION: CLASS=RSUDIU RSU=999 UNITNO=99


Description:In abort situations and during resource bottlenecks, message loss may occur. This leadsto inconsistencies between the signaling of alarms and advisories and the actual oper-ating state.In order to counteract this, after each new recovery, after transmission losses in the in-terface SAOUT and after overflow of the alarm file, verification of the alarm and advisorycontrol data, the AM.ALARM and the system status information is performed by com-parison with reference databases of the system alarming user.The absence of an alarm entry in the alarm control data is corrected by generating a de-fault alarm.In the present case, RSU DIU FAILURE, an RSU DIU is out of service or faulty.In accordance with the entry CLASS=object and the logical address specified after it,fault clearance can be performed.Using the commandsDISP ALARMandSRCH ALARMfurther symptoms can be determined.

24 A30828-X1170-N120-1-7620


4.5 RSU05-0000 RSU ISOLATIONFault report:

DEFAULT COMMUNICATIONS ALARM MMN:RSU05-0000 ORIGINAL ALARM MESSAGE WAS LOST.

ALARM PRIORITY: @####### PROBABLE CAUSE: REMOTE NODE TRANSMISSION ERROR SPECIFIC PROBLEM: NOT AVAILABLE MESSAGE NUMBER: @#### ALARM IDENTIFICATION: CLASS=RSUISO RSU=999

System reactions: The fault is reported as a critical alarm for the object SN. The fault is entered in the AM.ALARM.

Description:In abort situations and during resource bottlenecks, message loss may occur. This leadsto inconsistencies between the signaling of alarms and advisories and the actual oper-ating state.In order to counteract this, after each new recovery, after transmission losses in the in-terface SAOUT and after overflow of the alarm file, verification of the alarm and advisorycontrol data, the AM.ALARM and the system status information is performed by com-parison with reference databases of the system alarming user.The absence of an alarm entry in the alarm control data is corrected by generating a de-fault alarm.In the present case, RSU ISOLATION, there is no longer a connection between CPand HTI or HTI and RTI.In accordance with the entry CLASS=object and the logical address specified after it,fault clearance can be performed.Using the commandsDISP ALARMandSRCH ALARMfurther symptoms can be determined.

A30828-X1170-N120-1-7620 25


NM:RSU

4.6 RSU06-0000 MANUAL STAND ALONE SERVICEFault report:

RSU ISOLATION ALARM MMN:RSU06-0000

THE FOLLOWING RSU HAS BEEN MANUALLY PLACED IN STANDALONE SERVICE

RSU NUMBER: @## RSU NAME: @#######


Description:The RSU specified in the fault report was configured to the status SAS (Stand AloneService) by MML command.The RSU must be configured back to operating state ACT by means of an MML com-mand.

26 A30828-X1170-N120-1-7620


4.7 RSU08-0000 AUTONOMOUS SASFault report:

RSU ISOLATION ALARM MMN:RSU08-0000

THE FOLLOWING RSU IS NOW IN STAND ALONE SERVICE

RSU NUMBER: @## RSU NAME: @#######


Description:The loss of communication between CP and HTI/RTI is detected by the FA (Fault Anal-ysis) in the CP. FA configures the affected HTI or RTI and the associated LTGs to NAC.SAS (Stand Alone Service) Maintenance detects Layer 3 loss between CP and RTI andinforms the SAS control. If the criteria for SAS are fulfilled, SAS Mode is entered for theaffected RTIs and associated LTGs.If Communication Maintenance detects HSL faults in the RTI, this is evaluated by RTIas a criterion for SAS. If a certain threshold has been reached, SAS Mode is entered bythe SAS control for the affected RTIs and the associated LTGs. The HTI informs the FAin the CP about the HSL faults, and this configures the affected HTIs or RTIs and theassociated LTGs to NAC.

A30828-X1170-N120-1-7620 27


NM:RSU

4.8 RSU09-0000 TOTAL FAILUREFault report:

RSU FAILURE WITH CONFIGURATION MMN:RSU09-0000

FAULT IDENTIFIER:

TOTAL FAILURE @#########

RSU NUMBER: @## RSU NAME: @####### TYPE: @## SIDE: @#

RSU UNIT: @######## UNIT NUMBER: @#

SUPPLEMENTARY INFORMATION:

H06B7aabb ccddeeff gghhiijj kkllxxxx Hxxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

Explanation of the bytes: aabb: processor number ccddee: not used ff: fault code gg: type 0 = HTI, 1-14 = RTI #0-13 hh: side ii: Unit Type:

1 = BASE UNIT 2 = RSUC 3 = TSIM 4 = AMUX 5 = MH 6 = DIU 7 = HSL

jj: Unit Number kk: not used ll: cause of fault

00 = no fault 01 = total fault 02 = unit not plugged 03 = clock error 04 = RAM error 05 = Recovery 2.1 error 06 = Recovery 2.2 error 07 = Recovery 2.1 request 08 = Recovery 2.2 request 09 = Layer 3, loop error 10 = Permanent loop error 11 = SAS entry 12 = X-write error 13 = XCH error

28 A30828-X1170-N120-1-7620


System reactions: The fault is reported as a deferred alarm for the object SN. The fault is entered in the AM.ALARM.

Description:The internal communication link to the RSU unit reporting a fault is disturbed. The com-munication links of the RSU are shown in Fig. 4.1.Possible causes:a) Flag loss Layer 2 protocol on the link to the RSU unit reporting a fault.

All frames start and end with a flag sequence consisting of the pattern 01111110(see Fig. 4.2). The MUNICH (Multi-Channel Network Interface Controller) for HDLCmonitors the frames and reports to the CPU whenever there is a change in the pat-tern. Faulty flags over a predefined period are reported to Communication Mainte-nance as loss of the Layer 2 protocol .

b) No response to transmitted data from the RSU unit.Whenever a frame is transmitted, a timer is started which monitors the arrival of theresponse. If the timer expires before the response arrives, this is reported to Com-munication Maintenance as loss of the Layer 2 protocol.

c) Faulty response to transmitted data from the RSU unit.Whenever a frame is received that does not comply with the protocol, this is reportedto Communication Maintenance as loss of the Layer 2 protocol.

A30828-X1170-N120-1-7620 29


NM:RSU

Fig. 4.1 Communication links of the RSUThere are nine types of communication links: MCH MB (CP) HTI/MH MCH MB (CP) HTI/RSUC MCH LTG RTI/MH CCH DIU RSUC XCH RSUC (Plane 0) RSUC (Plane 1) IHSL MH MH IHSL RSUC MH HSL HTI/MH RTI/MH

CP

TSIM

TSIM

MH

MH

RSUC

RSUC

DIU

DIU

MH

MH

DIU

DIU

MH

MH

RSUC

RSUC

MH

MH

TSIM

TSIM

LTG

LTG

HSL

HSL

HSL

HSL

IHSL

IHSL

IHSL

IHSL

IHSL

IHSL

IHSL IHSL

IHSL

IHSL

IHSL

IHSL

MCH

MCH

MCH

MCH MCH

MCH

MCH

MCH

MCH

MCH

XCH XCH

CCH

CCH

CCH

CCH

DCL

DCLDCL

DCL

HTI RTIPlane 0

Plane 1 Plane 1

Plane 0

30 A30828-X1170-N120-1-7620


Fig. 4.2 Layer 2 protocol format

FLAG01111110

BYTE 1

ADDRESS(high order byte)

BYTE 2

ADDRESS(low order byte)

BYTE 3

CONTROL BYTE BYTE 4

CONTROL BYTE BYTE 5

INFORMATION

BYTE 6.

.

.

BYTE N-3

FCS BYTE N-2

FCS BYTE N-1

FLAG01111110

BYTE N

A30828-X1170-N120-1-7620 31


NM:RSU

4.9 RSU10-0000 UNIT UNPLUGGEDFault report:


FAULT IDENTIFIER:

UNIT UNPLUGGED @#########









32 A30828-X1170-N120-1-7620


System reactions: The fault is reported as a deferred alarm for the object SN. The fault is entered in the AM.ALARM.

Description:The AMUX module collects the presence signals from eight modules in the F:RSU(see Fig. 4.3). These are the DIU modules, the MH modules and, in the basic frame, theRSUC modules (see Tab. 4.1). The collected data can be accessed from the TSIM. Themodule presence test of RSUC:FP sends the message STATREQ_PERIPHERY every10 seconds to the TSIM. The TSIM replies with the messageSTATREQ_PERIPHERY_REPLY, specifying which modules are present. The contentsof this message are compared with the contents of the previous message. If a moduleis missing, a fault report is sent.The TSIM module in the basic frame of the RSU monitors all AMUX modules of the RSU(see Fig. 4.4). If an active AMUX module is pulled, the AMUX presence signal changesfrom low to high, which results in an interrupt and therefore in a fault report.

Fig. 4.3 Presence monitoring of DIU, MH and RSUC modules

Presencesignal

Monitored location

PRIN0_L DIU0

PRIN1_L DIU1

PRIN2_L DIU2

PRIN3_L DIU3

PRIN4_L DIU4

PRIN5_L DIU5

Tab. 4.1 Allocation of presence signals

l

l

l

l

l

l

l

l

l

l l

l

PRIN0_L

PRIN7_L

Backplane connector

SEL0..2

PRESENCE

PRE_CHANGE

A:MUX16

changedetect

8 in

MUX

P3V3

l

l

l

l

l

A30828-X1170-N120-1-7620 33


NM:RSU

Fig. 4.4 Presence monitoring of the AMUX modules

PRIN6_L MH0 / MH1 (M:MH) PRIN7_L RMH0 / RMH1 (M:MH or M:RSUC)

Presencesignal

Monitored location

Tab. 4.1 Allocation of presence signals

lPRAMUX1

PRAMUX2

AMUXpresence

Backplane connector

M:AMUX M:TSIM

34 A30828-X1170-N120-1-7620


4.10 RSU11-0000 CLOCK FAILUREFault report:


FAULT IDENTIFIER:

CLOCK FAILURE @#########









A30828-X1170-N120-1-7620 35


NM:RSU


Description:Clock distribution and supervision on the TSIM.The clock generator RCG of the RSU is located on module TSIM. The RCG synchroniz-es the system clocks in accordance with the external reference clocks.Reference clocks: HTI reference clocks:

CLK8 and FMB2 from SN0 or SN1 RTI reference clocks:

CLK 2.048 / 1.544 MHz of the PCM links of DIU240 / 0 or DIU240 / 4 BITS interface. External clock supply A or B CLK Master / Slave. Cross link between Master and Slave RCG of the RTI

The following clocks are distributed by the TSIM to the other modules of the HTI or RTI: CLK8 / FMB2

Clock CLK8 (8.192 MHz) and the synchronization signal FMB2 (2 kHz) for the SDCinterfaces. Internal SDC interfaces between AMUX and MH, RSUC and DIU240. External SDC interfaces between AMUX and SN (HTI) External SDC interfaces between AMUX and SN (RTI)

CLK92 / FMB92Clock CLK92 (92.16 MHz) and synchronization signal FMB92 (8 kHz) for ASICs ASIC EMU32 and TSC32 on the TSIM ASIC MUX16 on the AMUX

HCCLK_RClock HCCLK_R (2.048 MHz) is used for the communication link between TSIM andRSUC.

The monitoring circuits of the RCG detect clock errors and report these to the RSUC.The following errors are reported: Failure of a reference clock >30 seconds. The TSIM then synchronizes the RCG to

the other reference clock. RCG warm-up error, if the warm-up time of 6 minutes is exceeded. PLL alarms. PLL8 and PLL92.

36 A30828-X1170-N120-1-7620


Fig. 4.5 RCG functional overviewClock distribution and supervision on the RSUC / MHThe clock generation and supervision of the clocks is implemented with the chipMACH466 on the RSUC module or the MH modules. The 32 MHz clock used on theRSUC/MH is generated from the external master clocks of TSIM (2 MHz) and AMUX (8MHz). The supervision on the RSUC/MH detects and reports the following errors: failure of the external master clock (AMUX CLK, TSIM CLK) failure of the 32 MHz clock

BITS

A B

DIU240

DIU 0 DIU 4

Configuration

Supervision

Supervision

Supervision

Supervision

Supervision

Supervision

BITS_A BITS_B

DIU_A DIU_B

SYN_ASYN_A SYN_B

SYN_B

Supe

rvisi

on

RTI HTI

A B

Clock selection

Clock Aselection

Clock Bselection

Clock selection

Master/Slaveselection

RCG modeSelection

PLL

F_SYN

F_SYNSYN_A/B

PCM

M/S-MODMASREF

Rear connectorRCG conf. (HTI/RTI)

RCG warmed up

SYN fault

PLL8/PLL92 Alarm

cross connect clock

cross connectmaster / slave

SNCLK8/FMB2

TOL_A TOL_B

CLK8

FMB2

l

l

l

l

l

l

l

A30828-X1170-N120-1-7620 37


NM:RSU

Fig. 4.6 Clock supervision RSUC/MHClock distribution and supervision on the DIU240The clock distribution in the RSU is redundant. TSIM:RCG0 or TSIM:RCG1 supply thenecessary system clocks. The clock supervision and clock distribution on the DIU240selects the master clock CLK8 (8.192 MHz ) and synchronous pulse FMB2 (2 kHz) fromthe master side (normally side 0) of the RTI/HTI.

div. 2 div. 2 div. 2

div. 2

div. 2

div. 2

Phasedetector

Clock supervision

PLL

Clocksupervision

l l l

l

VCO 32 MHz

AMUX CLK

TSIM CLK

AMUX CLK ERROR

TSIM CLK ERROR

8 MHz CLK

M41 PWM

16 MHz CLK

38 A30828-X1170-N120-1-7620


Fig. 4.7 DIU240 clock supervision and clock distributionIf the supervision circuit detects clock failure or PLL alarm, the DIU takes the masterclock autonomously from the other side ( slave side) and reports this to the RSUC.If the DIU240 reports two or more clock switchovers within 10 seconds to the RSUC re-ferring to the same side, a fault report is sent.

l

l

l

l

l

Side 0

Side 1

CLK 8MHz

SYP 2kHz

CLK 8MHz

SYP 2kHz

CLK 8MHzSYP 2kHz

PLLsupervision

CLK / SYPSupervisionand divider

CLK / SYPSupervisionand divider

Clockselection

P

Time control

PLLSYNC

A30828-X1170-N120-1-7620 39


NM:RSU

4.11 RSU12-0000 RAM FAILUREFault report:


FAULT IDENTIFIER:

RAM FAILURE @#########









40 A30828-X1170-N120-1-7620



Description:The routine test requests a checksum test for RSUC and MH every 2 minutes.The checksum test is requested with the internal message CMD_CTRL_CKSUM_TESTto the RSUC or MH.In the checksum test, new checksums are calculated from the memory contents andcompared with the stored checksums. The newly calculated checksums must agree withthe stored checksums.If a checksum error is detected, this is reported to the fault processing (FP) of the RSUCand a fault report is sent.

A30828-X1170-N120-1-7620 41


NM:RSU

4.12 RSU13-0000 LAYER 3 LOOPBACK FAILUREFault report:


FAULT IDENTIFIER:

LAYER 3 LOOPBACK FAILURE @#########









42 A30828-X1170-N120-1-7620



Description:The periodic Layer 3 loopback test is used to check the internal communication linksfrom the RSUC to the DIU240, MH, TSIM and the partner RSUC.The test runs with lowest priority and is started by the routine test. If the RSU has SASstatus (Stand-Alone-Service), the test is not performed.The Layer 3 loopback test checks one of the following connections every 10 seconds: XCH communication link between RSUC side 0 and RSUC side 1. DCL communication link between RSUC and TSIM. IHSL communication link between RSUC and MH. CCH communication link between RSUC and DIU240.Links to units that are in operating state MBL or PLA are not tested.The Layer 3 loopback test is performed in the following steps: Check of the operating state of the destination unit. If the operating state is MBL or

PLAN the test is aborted. If the operating state is in order, the Layer 3 loopback test is started on this link. The

RSUC sends the command CMD_LAYER3_LOOP via the communication link to theunit that is to be tested. This unit responds with the acknowledgementACK_LAYER3_LOOP. The test is monitored by a 3-second timer.

If the response to the Layer 3 loopback test is received and confirmed by the desti-nation unit before the timer expires, the link is in order.

If the timer expires before this response is received, the test is repeated. If the re-peated test also produces a fault, this is reported to Fault Processing (FP) of theRSUC and a fault report is sent.

A30828-X1170-N120-1-7620 43


NM:RSU

Fig. 4.8 Overview of the communication paths

Side 0

Side 1

Multiplemodule

TSIM TSIMDIU240 DIU240

RSUC RSUC

MBMH MH LTG

MCH

MCH

DCL CCH CCHDCL

ISHL ISHL

ISHL ISHL

MCH

HTI RTI

XCH XCH

HSL

256 kbit/s

2 Mbit/s2 Mbit/s 64 kbit/s 64 kbit/s

64 kbit/s

64kbit/s

64kbit/s64kbit/s

64kbit/s

256 kbit/s

256 kbit/s 256 kbit/s

44 A30828-X1170-N120-1-7620


4.13 RSU14-0000 PERMANENT LOOPBACK FAILUREFault report:


FAULT IDENTIFIER:

PERMANENT LOOPBACK FAILURE @#########









A30828-X1170-N120-1-7620 45


NM:RSU


Description:The permanent loopback test checks all 32 channels of the HDLC and SDC links.RSUC ----> TSIM ----> AMUX ----> DIU240

Fig. 4.9 Permanent Loopback TestThe test runs with lowest priority and is started by the routine test every 30 seconds. Thetest is not performed if the RSUC has SAS status (Stand-Alone-Test).With the command SETUP_PATH_BIDIR to the TSIM the RSUC requests a COC(Cross Office Check) via one of the 32 HDLC channels. The test is monitored by a timer.The test result of the COC is reported to the RSUC with the messageSETUP_PATH_BIDIR_REPLAY.In response to the test request received from the RSUC the TSIM generates test pat-terns and sends them via a predefined TSI path in the direction of DIU240. The test pat-terns are sent back via a loop. The sent and received test patterns must match. The testresult is reported to the RSUC.If the test result indicates errors, or if the timer expires before the result arrives, this isreported to the fault processing (FP) of the RSUC and a fault report is sent.

DIU240

DIU240

DIU240

DIU240

DIU240

DIU240

0

1

2

21

22

23RSUC

RSUC

TSIM

TSIM

AMUX0

AMUX7

AMUX7

AMUX0

POOL

SIDE 0

SIDE 1

HDLC

HDLC

HDLC

HDLC

HDLC

HDLCSDC

SDC

SDC

SDC

46 A30828-X1170-N120-1-7620


4.14 RSU15-0000 SUBUNIT 2.1 RECOVERYFault report:

RSU FAILURE WITHOUT CONFIGURATION MMN:RSU15-0000

FAULT IDENTIFIER:

SUBUNIT 2.1 RECOVERY @#########









A30828-X1170-N120-1-7620 47


NM:RSU


Description:Recovery can be performed for the following RSU units: RSUC, MH, DIU and TSIM. Re-covery for the RSUC is controlled by the CP. Recovery for MH, DIU and TSIM is con-trolled by the RSUC.A SUBUNIT 2.1 RECOVERY is limited to the RSU unit concerned and is requested forthe following reasons: Automatic request in the event of software errors System recoveries (requested via RSUC command) Configuration (requested via RSUC command) Code mutilation in the RAM Detection of an endless loopThe following actions are performed for a SUBUNIT 2.1 RECOVERY : Software reset (processor and MUNICH) Copy code from the FEPROM into the RAM Restart of OS Initialization of all data Restart of all processes Optional loading of semipermanent dataThis recovery results in the loss of transient connections.If a fourth Recovery Level 2.1 occurs within 10 minutes, this results in escalation, i.e. aRecovery Level 2.2 is started.

48 A30828-X1170-N120-1-7620


4.15 RSU16-0000 SUBUNIT 2.2 RECOVERYFault report:


FAULT IDENTIFIER:

SUBUNIT 2.2 RECOVERY @#########









A30828-X1170-N120-1-7620 49


NM:RSU

System reactions: The fault is reported as a major alarm for the object REC. The fault is entered in the AM.ALARM.

Description:A SUBUNIT 2.2 RECOVERY is limited to the RSU unit concerned and is requested forthe following reasons: As a result of escalation of SUBUNIT 2.1 RECOVERY. Watch Dog event System recoveries (requested via RSUC command) Configuration (requested via RSUC command)The following actions are performed for a SUBUNIT 2.2 RECOVERY : Software reset (processor and ASIC) Formatting of free memory and data storage areas Conditional loading of code Copying of code from the FEPROM into the RAM Restart of OS Initialization of all data Restart of all processes Optional loading of semipermanent dataThis recovery results in the loss of all connections.If a third Recovery Level 2.2 occurs within 30 minutes and the recovery is not successful,the RSUC is configured to DST

50 A30828-X1170-N120-1-7620


4.16 RSU17-0000 LOAD FAILUREFault report:


FAULT IDENTIFIER:

LOAD FAILURE @#########









A30828-X1170-N120-1-7620 51


NM:RSU


Description:During recovery, configuration and initial cutover the firmware of the DIU and TSIM isnot loaded automatically. During recovery the code for TSIM and DIU is only activatedor loaded into the RAM.The firmware of the TSIM and DIU has to be reloaded on the following occasions: error correction new firmware feature after module replacement, if the firmware version on the new module does not

match that in the CP.If errors are detected while firmware is being loaded, e.g. checksum error, no acknowl-edgement, an error report is sent and the unit reporting the alarm is taken out of service.

52 A30828-X1170-N120-1-7620


4.17 RSU18-0000 SOFTWARE EXCHANGE FAILUREFault report:


FAULT IDENTIFIER:

SOFTWARE EXCHANGE FAILURE @#########









A30828-X1170-N120-1-7620 53


NM:RSU


Description:The FEPROMs on the RSUC and MH contain two versions of the online software, abackup version and an active version. Only the active version can be changed by meansof a patch, upgrade or downloading. The backup version is the software version sup-plied by the manufacturer.If an error occurs in the backup version, this means that in the event of an error in theactive version it is not possible to fall back on the backup version (golden load).

54 A30828-X1170-N120-1-7620


4.18 RSU19-0000 UNIT FAILURE DURING RECOVERYFault report:

REMOTE SWITCHING UNIT ALARM MMN:RSU19-0000

STATUS OF PERIPHERAL PROCESSOR UNIT CHANGED DURING SYSTEM-RECOVERY

UNIT : @############# OLD STATUS : @## NEW STATUS : @##


Description:An RSU unit that was in active status before the start of a recovery could not be restoredto this status during the recovery.These RSU units can be: BASE MH AMUX DIUFault clearance is performed with the aid of the appropriate diagnosis after the unit hasbeen configured to MBL .

A30828-X1170-N120-1-7620 55


NM:RSU

4.19 RSU20-0000 RSU SIDEDOOR HSL ALARMFault report:

RSU SIDEDOOR HSL ALARM MMN:RSU20-0000

RSU NUMBER: @## RSU NAME: @####### SIDE: @#


Description:The RSU SIDEDOOR HSL ALARM is issued whenever an RSU plane has an HSL overa sidedoor trunk.Configuring the HSL over a sidedoor trunk uses valuable call processing resources.The alarm is cleared when the RSU no longer uses a sidedoor HSL, or when the RSUplane goes to an out of service status.If an error occurs in the backup version, this means that in the event of an error in theactive version it is not possible to fall back on the backup version (golden load).

56 A30828-X1170-N120-1-7620


4.20 RSU70-0000 MINOR SELF TEST FAILUREFault report:


FAULT IDENTIFIER:

MINOR SELF TEST FAILURE @#########









A30828-X1170-N120-1-7620 57


NM:RSU

Description:Due to a recovery, the hardware of the reporting RSU unit was reset. This reset startedthe BordSelfTest, which found a fault on the module.

58 A30828-X1170-N120-1-7620


4.21 RSU71-0000 TSIM CROSSWRITE FAILUREFault report:


FAULT IDENTIFIER:

TSIM CROSSWRITE FAILURE @#########









A30828-X1170-N120-1-7620 59


NM:RSU

Description:This report states that the voice connections between a newly activated RSU platformand another active platform could not be synchronized. For nailed-up connections(NUC) call processing is informed so that reprovisioning can be performed.

60 A30828-X1170-N120-1-7620


4.22 RSU72-0000 CLOCK SWITCHFault report:


FAULT IDENTIFIER:

CLOCK SWITCH @#########









A30828-X1170-N120-1-7620 61


NM:RSU

Description:The clock distribution in the RSU is redundant. TSIM:RCG0 or TSIM:RCG1 provide therequired system clocks. The clock supervision and clock distribution on the DIU240 se-lects the master clock CLK8MHz and the 2kHz synchronous pulse from the master side(normally side 0) of the RTI/HTI.If the supervision circuit detects clock failure or PLL alarm, the DIU takes the masterclock autonomously from the other side (slave side) and reports this to the RSUC.

62 A30828-X1170-N120-1-7620


4.23 RSU73-0000 CROSS CHANNEL FAILUREFault report:


FAULT IDENTIFIER:

CROSS CHANNEL FAILURE @#########









A30828-X1170-N120-1-7620 63


NM:RSU

Description:A cross channel (XCH) connection is used for communication between the RSUC ofside 0 and the RSUC of side 1 via a DIU. In this case, the RSUC of side 0 is the masterRSUC and the RSUC of side 1 is the slave RSUC. A configuration change of an XCHwhich initiates reprovisioning has the effect that messages are retained, a new XCH iscreated and the messages are transmitted on the new XCH. The faulty CROSS CHAN-NEL is reported.

64 A30828-X1170-N120-1-7620


5 RSU74-0000 RSU PCM FAULTFault report:

RSU PCM FAULT - pcm-alarm-type - MMN:RSU74:0000

- fault identificator -

PCM LINK xxxxx CONNECTED FROM : RSUPDC RSUID --------+------- -

yyy-yy-y zzzzzzzz TO : yyy-yy-y zzzzzzzz

Explanation of the fault report:- pcm-alarm-type - : The alarm type is entered here. The following entries are possible:

a) / MAINTENANCE ALARMThis is a PCM maintenance alarm which triggers the following system responses: The associated PCM link is set to operating state DIS-MA. LED PDC is lit on the associated DIU240. The fault is reported as a major alarm for the object MAL. A message is sent to the CP so that connections are released and a block is set

against new seizures. The D-bit is set in the service word of the pulse frame. The fault report is entered in AM.ALARM.

b) / SERVICE ALARMThis is a PCM service alarm which triggers the following system responses: The associated PCM link is set to operating state DIS-SA. LED PDC is lit on the associated DIU240. The fault is reported as a major alarm for the object SAL. If the D-bit is received, a message is sent to the CP so that connections are re-

leased and a block is set against new seizures. The fault report is entered in AM.ALARM.

c) ENDThis is a PCM alarm end message which triggers the following system responses: The associated PCM link is set to operating state ACT. On the associated DIU240 the LED PDC goes out if all PCM links of this DIU are

fault-free. The alarm status is reset. The associated fault report in AM.ALARM is deleted. The ports of the link are released.

- fault identification - : The cause of the fault is entered here.See: 5.1 Description of the PCM FAULTS

PCM LINK xxxxx : The PCM LINK number is entered here.

yyy-yy-y : Equipment number of the PCM link:

A30828-X1170-N120-1-7620 65


NM:RSU

5.1 Description of the PCM FAULTS

5.1.1 CARRIER FAULT

Description:This PCM error message ia a control message from the RSU to call processing in theCP instructing it to release connections and to block all channels of the affected PCMlink against new calls.This control message from the RSU to the CP is sent in the following cases: When link failures persist for longer than 2 seconds (e.g. LOSS OF PULSE FRAME

ALIGNMENT, LOSS OF INCOMING SIGNAL etc.) When trouble messages are received from the remote end for longer than 2 seconds

(e.g. REMOTE ALARM IN PULSE FRAME)

5.1.2 FAULT MONITORING OVERFLOW

Description:The alarm monitoring overflows after the fifth fault report within 10 minutes. The fault re-port must have resulted in clear-down of all channels. Values can be modified via coun-try-specific software tables.If, after 10 minutes have elapsed, no fault occurs for another 10 minutes which wouldlead to release of all channels, the link is enabled again for call processing purposes.

5.1.3 AIS IN PULSE FRAME

Description:If a unit along the transmission path detects a fault, it sends an AIS, i.e. a permanentone in the whole pulse frame in the direction of transmission.The DIU240 checks all incoming pulse frames to determine whether there are two con-secutive pulse frames in which a maximum of one bit is set to 0.If this is the case, an AIS fault is sent to the RSUC. The RSUC then ignores all otheralarm reports.If AIS is detected for longer than 1 minute, an alarm is set for the object SAL and thefault is entered in the AM.ALARM.

5.1.4 LOSS OF PULSE FRAME ALIGNMENT

Description:1. Loss of frame alignment exists if at least:

yyy : Timeslot Interface Number 0-286.yy : DIU Number 0-23y : PCM Number 0-9

xxxxxxxx : The RSUID is entered here, e.g. : HTI1 or RTI3.

66 A30828-X1170-N120-1-7620


3 consecutive frame alignment words are incorrectly received. 3 consecutive service words are incorrectly received. 2 consecutive frame alignment words and 1 service word are incorrectly received. if the checksum supervision detects 16 errors within 4ms. This can also be

caused by failure of the data, clock and synchronous signals.2. Frame alignment is restored if the following conditions are fulfilled:

a correct frame alignment word is detected in channel 0 of the pulse frame. the service word is detected in channel 0 of the following pulse frame n+1. the frame alignment word is detected in channel 0 of the following pulse frame

n+2. if the number of errors detected by means of the checksum drops below the

threshold value of 16 in 4ms.3. In order to protect the frame error detection against simulated frame alignment, the

CRC4 method is provided for DIU240. This additional check takes place if pulseframe synchronism is achieved via the frame alignment word and the service word.The CRC4 multiframe consists of 16 pulse frames. It comprises 2 multiframe sec-tions, each containing 8 pulse frames. One 2048-bit multiframe section forms oneblock for the CRC4 method.The CRC4 method uses the bits 2 to the 7th (27) in the frame alignment word andthe service word. The resulting assignment of the frame alignment word and the ser-vice word is shown below (siehe Tabelle 5.1)

In the pulse frames with frame alignment words, bit 2 to the 7th contains the 4 CRC bits(C1, C2, C3 and C4) for a block of 8 pulse frames.

Multiframesection

Pulse frame Bit assignment of the frame alignment word (FAW)and the service word (SW)

27 26 25 24 23 22 21 20

Multiframe1

0 (FAW) C1 0 0 1 1 0 1 11 (SW) 0 1 D N Y1 Y2 Y3 Y42 (FAW) C2 0 0 1 1 0 1 13 (SW) 0 1 D N Y1 Y2 Y3 Y44(FAW) C3 0 0 1 1 0 1 15(SW) 1 1 D N Y1 Y2 Y3 Y46 (FAW) C4 0 0 1 1 0 1 17 (SW) 0 1 D N Y1 Y2 Y3 Y4

Mehrfach-rahmen 2

8 (FAW) C1 0 0 1 1 0 1 19 (SW) 1 1 D N Y1 Y2 Y3 Y410 (FAW) C2 0 0 1 1 0 1 111 (SW) 1 1 D N Y1 Y2 Y3 Y412 (FAW) C3 0 0 1 1 0 1 113 (SW) E1 1 D N Y1 Y2 Y3 Y414(FAW) C4 0 0 1 1 0 1 115 (SW) E2 1 D N Y1 Y2 Y3 Y4

Tab. 5.1 CRC4 multiframe

A30828-X1170-N120-1-7620 67


NM:RSU

n the pulse frames with service words, bit 2 to the 7th contains the alignment word forthe CRC4 multiframe with the value 001011 and 2 E-bits.When frame synchronism has been achieved, the CRC4 multiframe is searched for theCRC4 multiframe alignment word. CRC4 multiframe synchronism is achieved when atleast 2 CRC4 multiframe alignment words, 2 ms apart, are detected within 8 ms. If mul-tiframe synchronism is not achieved within a period of 100 ms, a message is sent to theRSUC.If loss of frame synchronism is detected for longer than 1 minute, or if the CRC4 multi-frame cannot be synchronized, an alarm is set for the object MAL and the fault is enteredin the AM.ALARM.

5.1.5 FAS ERR THRESH EXCE'D 10 EXP-3

Description:The frame alignment chip of DIU240 delivers an error pulse for each frame alignmentsignal detected as faulty, and these pulses are added by an error counter. The errorcounter level is transmitted to the RSUC every 4 seconds and the counter is reset.If the threshold set in the GP is exceeded (more than 35 errors within 4 seconds) overa period of more than 1 minute, a fault is reported.

5.1.6 LOSS OF MULTI FRAME ALIGNMENT

Description:The multiframe consists of 16 frames with the 4-bit signaling frame alignment word andthe 4-bit signaling frame service word in channel 16 of frame 0, as well as 15 times 2 4-bit signal words in channel 16 of frames 1 to 15.Multiframe alignment is considered lost if a faulty signaling frame alignment word is re-ceived twice in succession, or if the invalid bit pattern 0000 is received in a signal wordof the first half-byte in 2 consecutive multiframes.Multiframe alignment is restored when the signaling frame alignment word (0000 in thefirst half-byte of channel 16) is detected twice in succession and all other signal wordsdisplay a bit combination with at least one log. 1.If loss of multiframe alignment is detected for longer than 1 minute, a fault is reported.

5.1.7 CODE VIOL. THRESHOLD EXCEEDED

Description:DIU240 monitors the incoming PCM30 signal for HDB3 code violations. If these codeviolations exceed a threshold of 10 to the power of -3 (approx. 205 code violations within100 ms), this is reported to the RSUC.The counter for code violations on DIU30 is polled and reset every 100 ms. After everythree polling cycles the number of code violations is evaluated.If the threshold is exceeded for longer than 1 minute, a fault is reported.

68 A30828-X1170-N120-1-7620


5.1.8 LOSS OF INCOMING SIGNAL

Description:Loss of incoming PCM signal is detected if: during a measuring period of 250us (2 frames), less than 4 bits with log.1 are re-

ceived in 4 clock periods of the internal 2 MHz clock (CKA), not more than 1 clock period of

the line clock occurs.If loss of incoming PCM signal is detected for longer than 1 minute, a fault is reported.

5.1.9 AIS IN MULTI FRAME

Description:DIU240 monitors the incoming PCM signal for AIS (permanent one) in the signalingchannel. If the DIU240 detects AIS, it reports this to the RSUC.If AIS is detected for longer than 1 minute, a fault is reported:

5.1.10 SLIP THRESHOLD EXCEEDED

Description:Every 2Mbit/s interface monitors the 2Mbit/s transmission in the incoming direction forslip. The incoming data is transferred to the frame aligner buffer with a timing pattern ofthe receiving interface (DIU). If the timing pattern of the receiving unit (DIU) differs fromthe timing pattern of the transmitter, in the case of asynchronous network nodes, errorsoccur in the data transfer. If the frame alignment word of a PCM frame is not detected,the whole PCM frame is lost (frame slip).The first frame slip is detected in the DIU and reported to the CP (SLIP THRESHOLDEXCEEDED). The threshold value for slip is 1 (1 slip in 70 days). At the same time, a15-minute monitoring timer is started. All slips that occur subsequently result in a restartof the monitoring timer and an entry in the alarm statistics, but do not lead to a report tothe CP. Not until the monitoring timer expires, i.e. when no slip has occurred in 15 min-utes, does the next slip result in a report to the CP again.

5.1.11 REMOTE ALARM IN PULSE FRAME

Description:The PCM fault report REMOTE ALARM IN PULSE FRAME is a message from the dis-tant end.On account of a service alarm at the distant end (e.g. loss of frame alignment) the D-bit(D = critical alarm) was set in the service word of the frame. Fault clearance must there-fore be performed in the distant station.The fault is entered in AM.ALARM and displayed on the system panel if the D-bit is sentlonger than 1 minute.

A30828-X1170-N120-1-7620 69


NM:RSU

5.1.12 REMOTE ALARM IN MULTI FRAME

Description:This PCM fault report is sent in the following cases: Reception of D-bit in the service word of the signaling frame.

On account of a service alarm in the distant station (e.g. loss of signaling framealignment), the D-bit was set in the service word of the signaling frame. Fault clear-ance must therefore be performed in the distant station.The fault is reported if the D-bit is received for longer than 1 minute.Possible causes: Loss of signaling frame alignment in the distant station central fault in the signaling part of the distant station RSU failure in the distant station

Reception of N-bit in the service word of the signaling frame.The distant station sends a seizure and receives no acknowledgement. Because ofthe missing acknowledgement, the distant station sets the N-bit in the service wordof the signaling frame.An alarm is sent if the N-bit is received for longer than 1 minute.

70 A30828-X1170-N120-1-7620


6 Fault Reports during Configuration

6.1 ABORT BY CONF-SCHEDULER RSU CONFIGURATION FAILURE:

ABORT BY CONF-SCHEDULER

RSU UNIT SIDE OST ACTION --------+--------------+-------+-----------+---------

@### @########## @# @## @######

Description:The manual RSU configuration request CONF RSUEQ, was aborted by a higher-priorityconfiguration order from the system. The operator does not have to do any fault clear-ance. The manual configuration request must be repeated later on.

6.2 NOT ALLOWED DUE TO LOSS OF REDUNDANCY RSU CONFIGURATION FAILURE:

NOT ALLOWED DUE TO LOSS OF REDUNDANCY


@### @########## @# @## @######

Description:The manual RSU configuration request CONF RSUEQ, was rejected because if thecommand had been executed the RSU would have been Out Of Service.At least one RTI of the RSU must be in operating state ACT.

6.3 INVALID CURRENT CONDITIONS RSU CONFIGURATION FAILURE:

INVALID CURRENT CONDITIONS


@### @########## @# @## @######

Description:The manual RSU configuration request CONF RSUEQ, was rejected because the unitto be configured is in an operating state that does not allow the requested change instate, or the unit is already in this state.

A30828-X1170-N120-1-7620 71


NM:RSU

6.4 ABORT BY STOP COMMAND RSU CONFIGURATION FAILURE:

ABORT BY STOP COMMAND


@### @########## @# @## @######

Description:The manual RSU configuration request CONF RSUEQ, was rejected by manual inputof a stop command (STOP JOB).

6.5 NO RESPONSE FROM RSU RSU CONFIGURATION FAILURE:

NO RESPONSE FROM

Documents

rsu