Technical product manual - dct1900, Table 4–1 fault codes in service table – Nortel Networks DCT1900 User Manual
Page 375
Technical Product Manual - DCT1900
Maintenance, Service Messages
Maint-DCT1900/R8/mw
4-3
© 2000-2005
Table 4–1 Fault Codes in Service Table
Fault
Code
Service
class
Fault
Threshold
Description
1
2
5
Unexpected message/primitive. Message received but not within specified time
2
1
99
Board/CPU communication error or time out. Message corrupted or not received
3
2
99
Threshold fault counter or Reset counter exceeded
4
3
1
Board controller ROM error
5
3
1
Board controller RAM error
6
3
2
Internal loopback error
7
2
5
Peripheral state error
- State of peripheral differs from state listed in CPU data base
8
1
30
Base Station not present
- wiring fault or power lost
9
3
2
Peripheral ROM error
10
3
2
Peripheral RAM error
11
2
99
Peripheral status unknown. Two simultaneous faults: status can not be obtained
12/13
2
99
Board status unknown. No communication with board: status can not be obtained
14
2
5
Peripheral communication error or time out. Message corrupted or not received
15
2
2
Board signalling link was cut. When a board is not polled, it resets itself and after
communication has recovered it sends this message to CPU
16
1
10
Board controller poll response error
17
3
99
CPU main processor RAM error
18
3
99
CPU main processor ROM error
19
3
99
CPU EEPROM error
20
2
1
CPU real time clock test failed
21
3
2
CPU–poll processor (8031) RAM error
22
3
2
CPU–poll processor (8031) ROM error
23
1
2
CPU–poll processor communication error
26
2
5
CPU internal buffer overflow
27
2
99
Board controller watchdog reset
28
1
2
HSCX error. Serial communication controller on CPU of signalling highway
29
3
99
Signalling highway down. No communication between CPU and all other boards
33
1
1
Initialization procedure not successful. Due to e.g.: no communication with board
34
1
99
Portable Telephone related circuit not present. LTC or DTU–channel
35
2
30
Layer 1 fault at link with PBX: no physical connection or DTU error, L1 = MFG
- this fault may disappear automatically. CPU will set L1 and L2 to AVE again. The
service error message and general alarm remain and must be cleared manually
36
2
30
Layer 1 fault at link with PBX: Error in trunk unit of remote PBX (PBX did detect the
error), L1 = MFG - see note at fault 35
37
1
4
Layer 2 fault at link with PBX: No multiframe synchronization, L1=AVE, L2=MFG
- see note at fault 35
38
1
2
DTU or DLU hardware failure
39
1
99
PC communication error
- when statistics runs, logging is stopped. Statistics must be set "ON" again.
40
3
3
SPU parameters on board have wrong checksum
41
2
99
System Sync Delay hardware out of lock
50
1
*
Minimum configuration error, see Chapter 2, Paragrah 2.4.1, "Backplane Reset"
51
2
*
Subject is unreliable. Fault is not continuously present
52
2
*
Subject could not be tested after maintenance action due to a coincidence
- Subject must be verified if operational. It may be ‘AVE’ but not working. Reset subject
*Not handled by tam_dbas, so threshold is effectively infinite