S8000 Fault Number Description

Wireless Service Provider Solutions
Fault Number Description

Volume 1 of 9: BSC and TCU
PE/DCL/DD/0101 15.101/EN Standard July 2005
411--9001--101
Copyright 1999--2005 Nortel Networks
< 101 > : Fault Number Description Volume 1 of 9:

Document number: PE/DCL/DD/0101
411--9001--101
Document status: Standard
Document issue:
15.101/EN
Product release:
GSM/BSS V15.1
Date:
July 2005
Copyright 1999--2005 Nortel Networks, All Rights Reserved

Originated in France
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and
shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only.
You may not reproduce, represent, or download through any means, the information contained herein in any way or in
any form without prior written consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo,
the NORTEL Globemark, UNIFIED NETWORKS, S2000, S4000, S8000. GSM is a trademark of France Telecom.
All other brand and product names are trademarks or registered trademarks of their respective holders.
Nortel Networks Confidential
Publication history
iii
PUBLICATION HISTORY
System release: GSM/BSS V15.1
July 2005
Issue 15.101/EN Standard
Removed information on BSC6000 due to EOL (End Of Life).
Updated the description of fault number 1502 (section 2.100)
Added the description of fault number 1503 (section 2.101)
Updated On--Line Help locators
April 2005
Issue 15.100/EN Preliminary
Removed occurrences of end of life (EOL) products: CPU66, CPU120, TCB1
boards.
System release: GSM/BSS V15.0.1 Maintenance Load

March 2005
Incorporated new BSC 3000 and TCU 3000 branding.
November 2004
Issue 15.39/EN Preliminary - CR 1008406 added new description to Fault 140
October 2004
Issue 15.08/EN Standard - CR Q001001293 added new description to Fault 1502
September 2004
August 2004
General infrastructure and catalog cleanup
August 2004
CR Q00940321 - Updated Fault number 1310.
CR Q00963455 - Updated Fault number 102.
iv
Publication history
June 2004
CR Q00937998 - Add Fault number 1315 and new description.
March 2004
System release: GSM/BSS V14.3

October 2003
Made corrections to links and references to other NTPs.
August 2003
Corrected CR Q00184679--02 by changing the 1074 fault number description into
indication of hardware in compatibility with activated features
April 2003
Corrected CR Q00585446 by adding Help section (1.3) to chapter 1 (How to use
this manual)
Created cross references (links) in both Alarm 1152 procedures
January 2003
Removed all references to BSC 6000
Corrected CR Q00499935 (Fault Number 1502: Access Attempt to a
non--operational cell)
Chapter name change: from Manual User Guide to How to use this manual
Minor editorial update
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Publication history
System release: GSM/BSS V13

November 2002
Updated manual to include the feature BSC support for Lb interface (multi SSN or
Tandem Hybrid) to Nortel SMLC through E///MSC
Corrected CR Q00499935 by adding Paragraph describing Fault Number 1502
August 2002
Changed to standard
Minor Editorial Update
July 2002
Issue 13.03/EN Draft
March 2002
Changed to Standard
July 2001
vi
Publication history
System release: GSM/BSS V12

September 2001
No update for V12.4C Customer Readiness release
June 2001
The following changes were made in individual chapters:
Chapter 2, BSC FAULT NUMBERS
updated for correction of title of 1152 fault number
updated for SR 30340376
September 2000
Minor Editorial update
June 2000
Minor Editorial update
Chapter 2 BSC fault numbers
updated BSC fault number treatment procedures
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Publication history
vii
November 1999
Chapter 2 BSC fault numbers
updated BSC fault number treatment procedures
September 1999
Creation
viii
Publication history
PAGE INTENTIONALLY LEFT BLANK
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Table of contents
How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 - 1-- 1
1.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1
1.2
Description of a fault number sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1
1.3
1.2.1
Header of the sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1
1.2.2
Main body of the sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--2
ix
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--3

1.3.1
Loading the CD--ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--3
BSC fault numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 - 2-- 1
2.1
Fault number: 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--1

2.1.1
Source: Software anomaly counter threshold . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--4
2.1.2
Source: CPUE (MPU) non present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--5
2.1.3
Source: CPUE (MPU) or CPUM (OMU) built--in self test failed . . . . . . . Vol. 1 -- 2--7
2.1.4
Source: CPUE (MPU) or CPUM (OMU) setup failed . . . . . . . . . . . . . . . . Vol. 1 -- 2--9
2.1.5
Source: Incorrect Multibus II card name . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--11
2.1.6
Source: No communication with CPUE (MPU) card . . . . . . . . . . . . . . . . Vol. 1 -- 2--13
2.1.7
Source: Error in BSC state machine handler (GAUT) . . . . . . . . . . . . . . . Vol. 1 -- 2--15
2.1.8
Source: Error in switchover sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--16
2.1.9
Source: BDA KO during switchover sequence . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--17
2.1.10
Source: Invalid mirror partitions after switchover on the new active

chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--18
2.1.11
Source: Loss of the duplex link detected on passive chain . . . . . . . . . . Vol. 1 -- 2--19
2.1.12
Source: Inconsistency between active and passive chain . . . . . . . . . . . Vol. 1 -- 2--20
2.1.13
Source: Context overflow for BSC (MDB) defense . . . . . . . . . . . . . . . . . Vol. 1 -- 2--21
2.1.14
Source: Switching while passive chain DP loading . . . . . . . . . . . . . . . . . Vol. 1 -- 2--22
2.1.15
Source: Error detected during check partition . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--23
2.1.16
Source: CPUE BOOT flashing failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--24
2.1.17
Source: Restart to take into account the new BSC customization . . . . Vol. 1 -- 2--25
2.1.18
Source: Degraded disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--26
2.1.19
Source: Cancellation of probative phase . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--28
2.1.20
Source: End of probative phase OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--29
2.1.21
Source: New BDA edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--30
2.1.22
Source: Preparation of a type 5 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--31
2.1.23
Source: Type 5 upgrade running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--32
2.1.24
Source: Old release running on passive chain . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--33
2.1.25
Source: Unsuccessful preparation of a type 5 upgrade . . . . . . . . . . . . . Vol. 1 -- 2--34
Table of contents
2.1.26
2.1.27
2.1.28
2.1.29
Source:
Source:
Source:
Source:
BDA inconsistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GES--MS / GES--SL are incoherent . . . . . . . . . . . . . . . . . . . . . .
Passive chain does not answer on RGA request . . . . . . . . . . .
Passive chain suicide on RGA request . . . . . . . . . . . . . . . . . . .
Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 --
2.1.30
2.1.31
2.1.32
Source: No communication with switching board . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--40

Source: No communication with ECI card or fault on ECI card . . . . . . Vol. 1 -- 2--42
Source: No communication with SICX card or fault on SICX card . . . . Vol. 1 -- 2--45
2.1.33
2.1.34
2.1.35
2.1.36
Source: No communication with slave switching board . . . . . . . . . . . . .

Source: No communication with SLS card or fault on SLS card . . . . .
Source: Operator request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source: Degraded REM link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.37
2.1.38
2.1.39
Source: No communication with SICD or RCB card or fault on SICD

or RCB card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--53
Source: SICD port selftests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--56
Source: No communication with CCS7 card or fault on CCS7 card . . Vol. 1 -- 2--58
2.1.40
2.1.41
2.1.42
Source: CCS7 port selftests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--60

Source: No communication with TCU card or fault on TCU card . . . . . Vol. 1 -- 2--62
Source: O&M bus self--tests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--65
Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 --
2--35
2--37
2--38
2--39
2--47
2--49
2--51
2--52
2.2
2.3
Fault number: 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--67

Fault number: 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--68
2.4
2.5
Fault number: 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--72

Fault number: 11 (BSC 12000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--74
2.6
Fault number 11: (BSC 12000 HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--76
2.7
2.8
Fault number: 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--78

Fault number: 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--79
2.9
2.10
Fault number: 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--80

Fault number: 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--83
2.11
2.12
2.13
Fault number: 20 (BSC 12000 HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--86

Fault number: 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--87
2.14
2.15
Fault number: 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--89

Fault number: 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--90
2.16
Fault number: 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--91
2.17
2.18
Fault number: 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--92

Fault number: 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--93
2.19
2.20
Fault number: 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--94

Fault number: 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--95
2.21
Fault number: 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--99
2.22
Fault number: 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--100

2.22.1
Source: Cannot access to all working UTE . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--101
2.22.2
Source: O&M bus selftest not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--103
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Table of contents
xi
2.23
Fault number: 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--105
2.24
2.25
2.26
2.27
2.28
Fault number: 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--115
2.29
Fault number: 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--116
2.30
Fault number: 333 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--118
2.31
Fault number: 334 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--120
2.32
Fault number: 335 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--122
2.33
Fault number: 336 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--124
2.34
Fault number: 337 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--126
2.35
Fault number: 338 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--128
2.36
Fault number: 339 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--130
2.37
Fault number: 400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--132
2.38
Fault number: 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--134
2.39
Fault number: 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--136
2.40
Fault number: 403 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--139
2.41
Fault number: 404 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--142
2.42
Fault number: 405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--144
2.43
Fault number: 406 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--146
2.44
Fault number: 407 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--148
2.45
Fault number: 408 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--150
2.46
Fault number: 411 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--153
2.47
Fault number: 412 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--155
2.48
Fault number: 413 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--157
2.49
Fault number: 414 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--159
2.50
Fault number: 415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--161
2.51
Fault number: 417 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--163
2.52
Fault number: 419 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--165
2.53
Fault number: 420 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--167
2.54
Fault number: 422 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--169
2.55
Fault number: 494 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--171
2.56
Fault number: 497 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--173
2.57
Fault number: 520 (BSC 12000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--176
xii
Table of contents
2.58
Fault number: 520 (BSC 12000 HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--178
2.59
Fault number: 521 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--180
2.60
2.61
2.62
Fault number: 523 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--186
2.63
Fault number: 524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--187
2.64
2.65
2.66
2.67
2.68
Fault number: 617 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--197
2.69
2.70
2.71
Fault number: 633 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--203
2.72
2.73
2.74
2.75
2.76
Fault number: 649 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--211
2.77
Fault number: 656, 657 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--213
2.78
Fault number: 1074 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--214
2.79
Fault number: 1150 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--215
2.80
Fault number: 1151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--216
2.81
Fault number: 1152 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--217
2.82
Fault number: 1153 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--220
2.83
Fault number: 1154 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--222
2.84
Fault number: 1155 (BSC 12000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--224
2.85
Fault number: 1155 (BSC12000 HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--225
2.86
Fault number: 1164 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--226
2.87
Fault number: 1193 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--228
2.88
Fault number: 1201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--230
2.89
Fault number: 1211 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--232
2.90
Fault number: 1212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--233
2.91
Fault number: 1312 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--234
2.92
Fault number: 1315 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--236
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Table of contents
xiii
2.93
2.94
2.95
2.96
2.97
2.98
2.99
2.100
2.101
2.102
Fault number: 1366 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault number: 1470 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1472 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1483 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1484 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1486 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1490 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1502 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1503 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of software error descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCU fault numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 - 3-- 1
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21
3.22
3.23
3.24
3.25
3.26
3.27
3.28
3.29
3.30
Fault number: 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 493 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 497 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 523 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1150 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1152 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1157 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1159 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1160 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1163 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1165 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1170 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1171 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1172 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1173 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1174 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1184 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1185 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number: 1186 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1290 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1311 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1363 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault number 1364 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
Vol. 1
-----------
-------------------------------
2--239
2--240
2--242
2--243
2--244
2--245
2--246
2--247
2--249
2--250
3--1
3--6
3--8
3--10
3--13
3--16
3--17
3--18
3--19
3--21
3--22
3--23
3--25
3--27
3--28
3--29
3--31
3--34
3--37
3--41
3--44
3--48
3--50
3--52
3--54
3--56
3--58
3--60
3--61
3--63
xiv
List of tables
Table 2--1
Fault number 5 sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--3
Table 2--2
APE queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--96
Table 2--3
GES_SL queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--97
Table 2--4
Fault number 43 sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--100
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
List of fault numbers
xv
5
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
Source:
: Restart after chain suicide due to internal cause, or OMC . . . . . . . . . . . . . . . . . . .

(0) Software anomaly counter threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(1) CPUE (MPU) non present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(2) CPUE (MPU) or CPUM (OMU) built--in self test failed . . . . . . . . . . . . . . . . . . . . . .
(3) CPUE (MPU) or CPUM (OMU) setup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(4) Incorrect Multibus II card name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(5) No communication with CPUE (MPU) card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(8) Error in BSC state machine handler (GAUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(10) Error in switchover sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(11) BDA KO during switchover sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(12) Invalid mirror partitions after switchover on the new active chain . . . . . . . . . . . .
(14) Loss of duplex link detected on passive chain . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(15) Inconsistency between active and passive chains . . . . . . . . . . . . . . . . . . . . . . . . .
(16) Context overflow for BSC (MDB) defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(20) Switching while passive chain DP loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(21) Error detected during check partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(23) CPUE BOOT flashing failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(24) Restart to take into account the new BSC customization . . . . . . . . . . . . . . . . . . .
(25) Degraded disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(27) Cancellation of probative phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(28) End of probative phase OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(29) New BDA edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(30) Preparation of a type 5 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(31) Type 5 upgrade running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(32) Old release running on passive chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(33) Unsuccessful preparation of a type 5 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(50) BDA inconsistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(51) GES--MS / GES--SL are incoherent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(52) Passive chain does not answer on RGA request . . . . . . . . . . . . . . . . . . . . . . . . . .
(53) Passive chain suicide on RGA request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(101) No communication with switching board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(102) No communication with ECI card or fault on ECI card . . . . . . . . . . . . . . . . . . . .
(103) No communication with SICX card or fault on SICX card . . . . . . . . . . . . . . . . . .
(104) No communication with slave switching board . . . . . . . . . . . . . . . . . . . . . . . . . . .
(105) No communication with SLS card or fault on SLS card . . . . . . . . . . . . . . . . . . .
(106) Operator request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(107) Degraded REM link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(128) No communication with SICD or RCB card or fault on SICD or RCB card . . .
(129) SICD port selftests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(161) No communication with CCS7 card or fault on CCS7 card . . . . . . . . . . . . . . . .
(162) CCS7 port selftests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(176) No communication with TCU card or fault on TCU card . . . . . . . . . . . . . . . . . . .
(192) O&M bus selftests not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restart after chain suicide due to trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--67
Card monitoring failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--68
Negative built in self test result for card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--72
11
Restart after chain suicide due to NMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--74
Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 -Vol. 1 --
2--1
2--4
2--5
2--7
2--9
2--11
2--13
2--15
2--16
2--17
2--18
2--19
2--20
2--21
2--22
2--23
2--24
2--25
2--26
2--28
2--29
2--30
2--31
2--32
2--33
2--34
2--35
2--37
2--38
2--39
2--40
2--42
2--45
2--47
2--49
2--51
2--52
2--53
2--56
2--58
2--60
2--62
2--65
xvi
11
Restart after chain suicide due to NMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--76
13
Chain restart in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--78
14
Indication of chain restart cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--79
15
Chain restart due to intermediate card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--80
16
Fault on active/passive chains link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--83
20
Alarm on clockship of the SUP board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--85
20
Alarm on clockship of the SUP board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--86
21
Beginning of circular file pre--overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--87
22
End of circular file pre--overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--89
23
Beginning of BSC disk partition update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--90
24
End of BSC disk partition update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--91
26
Fault on BSC/OMC--R link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--92
33
Saturation on an internal file used for marking climb . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--93
34
Saturation on a storage zone for marking climb . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--94
41
Beginning of saturation of the event reporting process in the BSC . . . . . . . . . . . Vol. 1 -- 2--95
42
End of saturation of the event reporting process . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--99
43
: Loss of access to the equipment shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--100
Source: (0) Cannot access to all working UTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--101
Source: (1) O&M bus selftest not OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--103
44
Board UTE access problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--105
45
Partial hard disk degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--107
45
Partial hard disk degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--109
46
Total hard disk degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--111
46
Total hard disk degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--113
47
Cessation of active alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--115
332
External alarm loop 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--116
333
334
335
336
337
338
339
400
Breakdown of one power supply of the EQPD1 shelf . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--132
401
Breakdown of one power supply of the EQPD0 shelf . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--134
402
Fan fault on the MPU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--136
403
Fan fault on the MPU shelfs power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--139
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
xvii
404
RCB0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--142
405
RCB1 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--144
406
RCB2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--146
407
RCB3 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--148
408
Power supply fault to the fans of the MPU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--150
411
Power supply fault of the other chains MPU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--153
412
RCB4 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--155
413
Fault on the right MPU power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--157
414
Fan fault on EQPT and SWG shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--159
415
Power supply fault on SWG or SWT shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--161
417
Power supply fault on EQPT shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--163
419
Power supply fault on EQPI shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--165
420
Fan fault on the EQPI, EQPD0 and EQPD1 shelves . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--167
422
Power supply fault to the fans of the equipment cabinet . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--169
494
Fault on ECI alarm loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--171
497
New PCM selected as clock reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--173
Fault on switching matrix access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--176
520
Fault on switching matrix access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--178
521
Fault on switching matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--180
522
Switch supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--182
522
Switch supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--184
523
Fault on internal PCM (BSC, TCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--186
524
Slave switch board not present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--187
601
File management error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--189
601
607
Multibus II error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--193
607
617
SCSI bus controller error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--197
632
632
633
Disk driver error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--203
634
Mirror disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--205
634
Mirror disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--206
638
638
649
: SCSI protocol error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--211
656 and 657
:Ethernet controller chip error
Vol. 1 --- 2---213
xviii
1074
Indication of hardware in compatibility with activated features . . . . . . . . . . . . . . . Vol. 1 -- 2--214
1150
Loss of DDTI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--215
1151
PCM transmission fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--216
1152
PCM CRC attribute and DDTI CRC strap are not consistent . . . . . . . . . . . . . . . . Vol. 1 -- 2--217
1153
Negative test on passive chain LAPD channel (layer 2) . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--220
1154
Negative test on passive chain CCS7 signalling link (layer 2) . . . . . . . . . . . . . . . . Vol. 1 -- 2--222
1155
Fault on SLS card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--224
1155
Fault on SLS card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--225
1164
OMC access failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--226
1193
Clock alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--228
1201
Degraded active chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--230
1211
Unknown TEI in a LAPD message received by the XSCB card . . . . . . . . . . . . . . Vol. 1 -- 2--232
1212
xSCB card internal fifo congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--233
1312
MSC inaccessible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--234
1315
Path Information for calls released by TCU or BTS . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--236
1366
Indication of the SSN LCS state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--239
1470
Impossibility of storage of a general permanent observation message . . . . . . . . Vol. 1 -- 2--240
1472
Purge realized to store a general permanent observation message . . . . . . . . . . Vol. 1 -- 2--242
1483
Impossibility of storage of non prioritary records . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--243
1484
Impossibility of storage of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--244
1486
Call path tracing activity state change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--245
1490
BSC overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--246
1502
Access attempt to a non operational cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--247
1503
Access Attempt to an unknown BCCH or BSIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--249
101
Incorrect ZHCOM message area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
102
Incorrect ZDATA message area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
103
Unknown communication map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
104
Unknown family value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
105
Unknown operation code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
106
Unknown class value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
107
Unknown instance value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
120
Unexpected message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
121
Requested action already done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
122
Erroneous processing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
123
Erroneous internal data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--250
124
Erroneous external data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
125
Erroneous internal static table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
xix
126
Erroneous internal execution report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
127
Lack of internal resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
128
Problem during cold init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
130
Unexpected message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
131
Requested action already carried out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
132
Erroneous processing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
133
Erroneous internal data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
134
Erroneous external data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
135
Erroneous internal static table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
136
Erroneous internal execution report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
137
Lack of internal resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
138
Current task is stopped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
139
Load data KO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
140
No response from a software entity (minor software anomaly that is not filtered) Vol. 1 -- 2--251
150
No response from a software entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
151
No response from a hardware entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
160
System error: lack of timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
161
System error: I/O error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
162
System error: waiting queues (pre)overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--251
163
System error: stacks overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
164
Local overload defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
170
System error: FSM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
171
System error: exchange error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
172
System error: stack error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
173
System error: lack of FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
174
System error: system semaphore error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
190
UTE suicide due to SCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
191
UTE suicide due to application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
192
UTE suicide due to system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
200
Disk I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
201
File management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
202
Disk driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
203
Mirror disk: services and user functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
204
Mirror disk: state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
205
Mirror disk: transmission protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
206
Transport data link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
xx
207
Data link layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
208
Access to interconnection area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
209
Data transport layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
210
Access to multibus II management coprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
211
Switching matrix access and transmission protocol . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
212
Switching matrix access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
213
Protocol transmission layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--252
214
SUP card access management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
215
SCSI: bus management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
216
SCSI: units logical management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
217
SCSI: bus controller management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
218
SCSI: protocol management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
219
X25 layer 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
220
HDLC handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
221
LAPB layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
222
Passive chain restart inhibited to be manually activated . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
223
Debug complementary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
224
Instrumentation complementary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
225
Ethernet driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
226
229
System card transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
230
BSC capacity reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
231
Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
232
UC loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
233
Data loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
234
Remote SCO access loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
235
Local SGF access loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
236
C library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
237
Sympa station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
238
Load function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
239
State machine management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
240
Ethernet layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
241
STA bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
242
LDB bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
243
OMF86 loading through asynchronous link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
244
OMF processing function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
xxi
245
LDB CSP access cad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
246
Ethernet link access cad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--253
247
Disk I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
248
File management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
249
Disk driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
250
Mirror disk: services and user functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
251
Mirror disk: state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
252
Mirror disk: transmission protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
253
Transport data link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
254
Data link layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
255
Access to interconnection area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
256
Data transport layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
257
Access to multibus II management coprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
258
Switching matrix access and transmission protocol . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
259
Switching matrix access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
260
Protocol transmission layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
261
SUP card access management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
262
SCSI: bus management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
263
SCSI: units logical management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
264
SCSI: bus controler management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
265
SCSI: protocol management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
266
X25 layer 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
267
HDLC handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
268
LAPB layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
269
FSM debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
270
Tape drive management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
271
Disk/tape copy tools management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
272
273
276
277
278
Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
279
UC loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--254
280
Data loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
281
Remote SCO access loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
282
Local SGF access loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
xxii
283
C library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
284
Sympa station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
285
Load function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
286
State machine management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
287
Ethernet layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
288
STA bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
289
LDB bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
290
OMF86 loading through asynchronous link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
291
OMF processing function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
292
LDB CSP access cad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
293
Ethernet link access cad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
294
SGF access problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
295
Driver ram disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
296
SGF access problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
297
Driver ram disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
800
Ethernet management IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
801
Ethernet management UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
802
Ethernet management TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
803
Ethernet management RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
804
Ethernet management SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
805
Ethernet management IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
806
Ethernet management UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
807
Ethernet management TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
808
Ethernet management RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
809
Ethernet management SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--255
Card monitoring failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--1
Negative built in self test result for card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--6
47
Cessation of active alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--8
493
Failure on one of the TCUs clocking sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--10
497
New PCM selected as clock reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--13
523
Fault on internal PCM (BSC, TCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--16
1150
Loss of DDTI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--17
1151
PCM transmission fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--18
1152
PCM CRC attribute and DDTI CRC strap are not consistent . . . . . . . . . . . . . . . . Vol. 1 -- 3--19
1156
TCU downloading failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--21
1157
Loss of TCU remote layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--22
1159
Invalid message received on TCU--BSC interface . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--23
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
xxiii
1160
TCU negative acknowledgment indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--25
1163
Preemption of a terrestrial circuit by a signalling link . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--27
1165
iiiVAL_STP_ANO_TRC_BLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--28
1170
External alarm loop on TCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--29
1171
TCU power fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--31
1172
TCU fan board fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--34
1173
TCU fan fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--37
1174
TCU clock fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--41
1180
TCB downloading failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--44
1184
Internal TCB--2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--48
1185
TCB--2 synchronization failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--50
1186
External TCB--2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--52
1190
Restart after TCU suicide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--54
1290
Unacknowledged message on a interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--56
1310
A interface protocol error indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--58
1311
Reset downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--60
1363
SCCP protocol error indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--61
1364
MTP3 protocol error indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 3--63
About this document
Vol. 1 -- 0--1
ABOUT THIS DOCUMENT

This document contains the fault number description and the maintenance actions
required for the BSC and the TCU.
Applicability
This document is part of the BSS Nortel Networks Technical Publications (NTPs).
It is one of the nine volumes concerning the fault number description:
Volume 2 of 9: S2000/S2000E and S4000 BTS
Volume 3 of 9: S8000, S8002, and S8006 BTS
Volume 4 of 9: S2000 H/L and e--cell BTS
Volume 5 of 9: Advanced Maintenance Procedures
Volume 6 of 9: PCUSN
Volume 7 of 9: BSC/TCU 3000
Volume 8 of 9: S12000 BTS
Volume 9 of 9: BTS18000
This NTP applies to the V15.1 system release.
Audience
This document is intended for operations and maintenance personnel, and all those
who want to know the principles of the BSC and TCU corrective maintenance.
Prerequisites
It is recommended that the readers also become familiar with the following NTPs:
< 00 > : BSS Product Documentation Overview
< 01 >
: BSS Overview
< 39 >
: BSS Maintenance Principles
< 46 >
: S2000/S2000E BTS Maintenance Manual
< 47 >
: S4000 BTS Maintenance Manual
< 105 > : Fault Number Description - Volume 5 of 9: Advanced Maintenance

Procedures
< 124 > : BSS Parameter Dictionary
Vol. 1 -- 0--2
About this document
< 125 > : Observation Counter Dictionary

< 128 > : OMC--R User Manual - Volume 1 of 3: Object and Fault menus
< 129 > : OMC--R User Manual - Volume 2 of 3: Configuration, Performance,
and Maintenance menus
< 130 > : OMC--R User Manual - Volume 3 of 3: Security, Administration,
SMS--CB, and Help menus
Related documents
The NTPs listed in the above paragraph are quoted in the document.
How this document is organized

This document consists of 3 chapters:
Chapter 1, How to use this manual, describes how to use this maintenance
manual.
Chapter 2, BSC Fault Numbers, contains the fault number description and the
corrective maintenance procedures applicable to the BSC.
Chapter 3, TCU Fault Numbers, contains the fault number description and the
corrective maintenance procedures applicable to the TCU.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
About this document
Vol. 1 -- 0--3
Typographic conventions
Graphic conventions
The following symbols are used in flowcharts.
Start of the flowchart, showing a start point in the form of the

state of the subsystem or a fault number
Action to be taken before or after the test
Action to be taken by the operator
Condition
Pointer allowing the flowchart to be divided
Vocabulary conventions
The glossary is included in the NTP < 00 >.
Regulatory information
Refer to NTP < 01 >.
Vol. 1 -- 0--4
About this document
Safety regulations
Introduction
All the following steps must be taken during the various cabinet maintenance
procedures in order to guarantee personnel and equipment safety.
Account must be taken of the following aspects:
general personnel safety instructions
equipment safety instructions
Precautionary messages
Caution, warning, and danger messages indicate possible risks.
CAUTION
Impact on the service and on the equipment
DANGER
Electric shock
DANGER
Environment and personnel protection
CAUTION
ESDS handling precautions
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
How to use this manual
Vol. 1 -- 1--1
HOW TO USE THIS MANUAL

1.1
Introduction
This manual contains the fault number descriptions and the corrective maintenance
procedures applicable to the BSC and the TCU for GSM 850, 900, 1800, and 1900
digital wireless systems.
The general principles and messages required for BSS maintenance are described
in NTP < 39 >.
The network maintenance is based on the graphical supervision of the network.
It is also based on the identification and the replacement of faulty items of
equipment, using the alarms and the notifications.
This process is divided into two steps:
locating and identifying the faulty items of equipment, using information given
in this manual
replacing the faulty items of equipment, using the replacement procedures given
in the manuals that describe the on--site procedures
When a faulty item of equipment sends an alarm to the OMC--R, this alarm is
identified by a fault number. This manual gives the procedures associated with the
various fault numbers.
1.2
Description of a fault number sheet

A corrective maintenance sheet contains the following information:
the header
the main body composed of eight main paragraphs explaining the fault number
treatment
1.2.1
Header of the sheet

The header contains the following information:
the fault number and possibly the source
the alarm type
Vol. 1 -- 1--2
1.2.2
Main body of the sheet

The main body contains the following information:
Fault analysis
This paragraph describes the fault.
Reaction of the system
BSC defense
This paragraph describes the defense actions taken by the BSC.

Impact on the service
This paragraph describes the consequences of the alarm for the service.
Fault treatment
This paragraph gives the procedures to be followed to repair the fault and return
to operational conditions.
Preliminary checks
These checks are used to ensure that the fault is confirmed and that the
messages identifying a faulty element are in the OMC--R logs before the start
of repair work.
On--site maintenance (possibly using the OMC--R)
This paragraph is used to start the repair work and to bring the exchanged
element into correct operation.
Additional checks
This paragraph shows how to check that the fault has been cleared.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
1.3
Vol. 1 -- 1--3
Help
The system provides the user with help at any time. For an in--depth discussion of
Help, refer to NTP <130>.
There are two kinds of help available:
on--line help, available from the Help menu in the OMC--R Browser window, as
well as other windows
the Consult BSS Documentation option of the workstation workspace pop--up
menu provides access to on--line BSS documentation stored on CD--ROM.
Both are provided on the same CD--ROM.
1.3.1
Loading the CD-- ROM

To load the CD--ROM from the screen workspace menu, insert the CD--ROM in the
OMC--R server and/or workstation CD--ROM drive. Installation is complete when
the light on the CD--ROM drive is no longer lit.
Vol. 1 -- 1--4
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--1
BSC FAULT NUMBERS

2.1
Fault number: 5
III
Fault number:
5
: Restart after chain suicide due to internal cause, or OMC
Type : processingErrorAlarm
The following Table 2--1 indicates all the sources of the fault number 5. For more
information on each source and the associated corrective maintenance procedure,
refer to the sheet indicated in the right column.
Source
No.
Source wording
BSC
12000
BSC
12000
HC
Procedure
Software anomaly counter threshold
2.1.1
CPUE (MPU) non present
2.1.2
CPUE (MPU) or CPUM (OMU) built--in

self test failed
2.1.3
CPUE (MPU) or CPUM (OMU) setup

failed
2.1.4
Incorrect Multibus II card name
2.1.5
No communication with CPUE (MPU)

card
2.1.6
Error in BSC state machine handler

(GAUT)
2.1.7
10
Error in switchover sequence
2.1.8
11
BDA KO during the switchover

sequence
2.1.9
12
Invalid mirror partitions after switchover

on the new active chain
2.1.10
14
Loss of the duplex link detected on

passive chain
2.1.11
15
Inconsistency between active and

passive chains
2.1.12
16
Context overflow for BSC (MDB)

defense
2.1.13
Vol. 1 -- 2--2
BSC fault numbers
Source
No.
PE/DCL/DD/0101
411--9001--101
Source wording
BSC
12000
BSC
12000
HC
Procedure
20
Switching while passive chain DP

loading
2.1.14
21
Error detected during check partition
2.1.15
23
CPUE BOOT flashing failed
2.1.16
24
Restart to take into account the new

BSC customization
2.1.17
25
Degraded disk
2.1.18
27
Cancellation of probative phase
2.1.19
28
End of probative phase OK
2.1.20
29
New BDA edition
2.1.21
30
Preparation of a type 5 upgrade
2.1.22
31
Type 5 upgrade running
2.1.23
32
Old release running on passive chain
2.1.24
33
Unsuccessful preparation of a type 5

upgrade
2.1.25
50
BDA inconsistency
2.1.26
51
GES--MS/GES--SL are incoherent
2.1.27
52
Passive chain does not answer on RGA

request
2.1.28
53
Passive chain suicide on RGA request
2.1.29
101
No communication with switching board
2.1.30
102
No communication with ECI card or

fault on ECI card
2.1.31
103
No communication with SICX card or

fault on SICX card
2.1.32
104
No communication with slave switching

board
2.1.33
105
No communication with SLS card or

fault on SLS card
2.1.34
106
Operator request
2.1.35
Standard 15.101/EN
July 2005
BSC fault numbers
Source
No.
Source wording
Vol. 1 -- 2--3
BSC
12000
BSC
12000
HC
Procedure
107
Degraded REM link
2.1.36
128
No communication with SICD or RCB

card or fault on SICD or RCB card
2.1.37
129
SICD port self tests not OK
2.1.38
161
No communication with CCS7 card or

fault on CCS7 card
2.1.39
162
CCS7 port self tests not OK
2.1.40
176
No communication with TCU card or

fault on TCU card
2.1.41
192
O&M bus self tests not OK
2.1.42
Table 2--1
Fault number 5 sources
Vol. 1 -- 2--4
BSC fault numbers
2.1.1
Source: Software anomaly counter threshold

iii
Restart after chain suicide due to internal cause, or
OMC
Fault number 5
Source:
BSC model:
(0) Software anomaly counter threshold

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain restarted after the threshold (set to 40) of the software
anomaly counter was exceeded.
If the software anomaly counter threshold was exceeded on the active chain, a chain
switchover took place: the active chain committed suicide, and the passive chain
became active.
If the software anomaly counter threshold was exceeded on the passive chain, the
passive chain committed suicide and restarted.
The chain concerned sends this notification as soon as the duplex link is open.
The chain suicide allows the BSC to recover and reach its nominal state.
REACTION OF THE SYSTEM

BSC defense
None.

None, unless the counter exceeded the threshold on both chains. In this case, there is a
loss of service during the BSC restart.
FAULT TREATMENT
Send the software anomaly notifications to the manufacturer.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.2
BSC fault numbers
Vol. 1 -- 2--5
Source: CPUE (MPU) non present

iii
OMC
Fault number 5
(1) CPUE (MPU) non present

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because a CPUE
board (CPU--MPU or CPU--BIFP) is missing.
When a CPUE board is missing, the chain concerned commits suicide and restarts
cyclically.
Another notification with fault number 7 card monitoring failure must have been sent
before to report that a CPUE board is missing.

BSC defense
The BSC is in simplex mode. The other chain restarts cyclically.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the BSC, by performing a Display all command on the bsc
object.
If the value of the bsc field is duplex, this fault number indicates a transient
problem or a bad operation of the CPUE board.
i.
Clear the alarm. Go to step 4.
ii.
If the problem often happens, replace the CPUE board. Go to step 2.
If the value of the bsc field is simplex, look for other notifications with fault
number 7 card monitoring failure that indicate a problem on one CPUE board
of the chain that is out of order.
i.
Treat these notifications.
ii.
Then go to step 3.
Vol. 1 -- 2--6
BSC fault numbers
On--site maintenance
Step
Action
Replace the CPUE board (Field Replaceable Unit).
a. Refer to the replacement procedure (see NTP < 41 >.

b. The return to service operations are performed by the system. Go to step 3.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Check that the repaired chain does not commit suicide again. Warning notifications
(with fault number 13) confirm that the BSC restarts correctly.
If necessary, clear the alarm concerning the CPUE board.
The procedure is complete.
Standard 15.101/EN
July 2005
2.1.3
BSC fault numbers
Vol. 1 -- 2--7
Source: CPUE (MPU) or CPUM (OMU) built-- in self test failed

iii
OMC
Fault number 5
Source:
BSC model:
(2) CPUE (MPU) or CPUM (OMU) built--in self test failed

BSC12000 + BSC12000 HC
FAULT ANALYSIS
board (CPU--MPU or CPU--BIFP) or a CPUM board (CPU--OMU) had a bad built--in selftest
(BIST) result. The board is not operational. The chain concerned never reaches an
operational state.
When a CPUE or a CPUM board is missing, the chain concerned commits suicide and
restarts cyclically.

BSC defense
None. The BSC is in simplex mode.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Look for an alarm with fault number 8 Negative built--in self--test result for card
concerning a CPUE or CPUM board.
If there is such an alarm, treat it.
If not, go to step 2.
object.
problem or a bad operation of the CPUE or CPUM board.
i.
ii.
If the problem often happens, replace the CPUE or CPUM board. Go to

step 2.
Vol. 1 -- 2--8
BSC fault numbers
Step
Action (Continued)
number 7 card monitoring failure that indicate a problem on one CPUE or
CPUM board of the chain that is out of order.
i.
ii.
Then go to step 4.
Step
Action
Replace the CPUE or CPUM board (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
(with fault number 13) confirm that the BSC restarts correctly.
If necessary, clear the alarm concerning the CPUE or CPUM board.
Standard 15.101/EN
July 2005
2.1.4
BSC fault numbers
Vol. 1 -- 2--9
Source: CPUE (MPU) or CPUM (OMU) setup failed

iii
OMC
Fault number 5
Source:
BSC model:
(3) CPUE (MPU) or CPUM (OMU) setup failed

BSC12000 + BSC12000 HC
FAULT ANALYSIS
board (CPU--MPU or CPU--BIFP) or a CPUM board (CPU--OMU) is missing.
When a CPUE or a CPUM board is missing, the chain concerned commits suicide and
restarts cyclically, but the chain concerned never reaches the operational state.
Another notification with fault number 7 card monitoring failure must have been sent
before.

BSC defense

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
problem or a bad operation of the CPUM and CPUE board.
i.
ii.
If the problem often happens, replace the CPUE board. Go to step 2.
Vol. 1 -- 2--10
BSC fault numbers
Step
Action (Continued)
number 7 card monitoring failure that indicate a problem on one CPUM or
CPUE board of the chain that is out of order.
i.
ii.
Then go to step 3.
Step
Action
Replace the faulty board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
(with fault number 13) allow to know if the BSC restarts correctly.
If necessary, clear the alarm concerning the CPUE or CPUM board.
Standard 15.101/EN
July 2005
2.1.5
BSC fault numbers
Vol. 1 -- 2--11
Source: Incorrect Multibus II card name

II
OMC
Fault number 5
Source:
BSC model:
(4) Incorrect Multibus II card name

BSC12000 + BSC12000 HC
FAULT ANALYSIS
The notification indicates that a chain committed suicide and restarted because it detected
that there was a problem with one of its boards connected to the Multibus II. One board
connected is not according to the type of board indicated in the configuration.
The notification also indicates the name of the equipment that detected the fault.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Look for a notification or an alarm with fault number 7 Card monitoring failure
concerning a board connected to the Multibus II.
If an alarm concerning a board is in the list of current alarms, go to step 3.
Vol. 1 -- 2--12
BSC fault numbers
On--site maintenance using the OMC--R

Step
Action
Check that the boards connected are according to the types of boards of the
configuration.
If everything is incorrect, position the correct type of board. Go to step 6.

Go on site and check that the boards of the chain are correctly positioned. Check
the PROM as well.
If one or several boards are badly positioned, position it (them) correctly.

If the PROM of a board is not the right one, replace the board. Go to step 5.
If everything is correct, call the manufacturer.
4
Treat the notification(s). Then go to step 6.

on the BSC control cabinet:
CPUE boards (see NTP < 41 >)

CPUM board (see NTP < 41 >)
SICD boards (see NTP < 41 >)
CCS7 boards (see NTP < 41 >)
SLS board (see NTP < 41 >)
SICX board (see NTP < 41 >)
on the BSC equipment cabinet:
RCB boards (see NTP < 41 >)

SWE boards (see NTP < 41 >)
ECI board (see NTP < 41 >)
SWC board (see NTP < 41 >)
MSW boards (see NTP < 41 >)
Then go to step 6.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the replaced board.
Standard 15.101/EN
July 2005
2.1.6
BSC fault numbers
Vol. 1 -- 2--13
Source: No communication with CPUE (MPU) card

III
OMC
Fault number 5
Source:
BSC model:
(5) No communication with CPUE (MPU) card

BSC12000 + BSC12000 HC
FAULT ANALYSIS
The system indicates that a chain committed suicide and restarted because a CPUE board
is used during a period of overload.
If the concerned chain commits suicide and restarts cyclically, the CPUE board is faulty.
In the case of a SICD board, this anomaly occurs because the board does not acknowledge
the supervision protocol.
If the concerned chain commits suicide and restarts cyclically, the SICD board is faulty.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
If the value of the bsc field is duplex, check the state of the CPUE or SICD
boards in the result window of the Display all command.
If the CPUE or SICD boards state is working, clear the alarm. Go to step 4.
If the state of one of the CPUE or SICD boards is faulty, replace the faulty
board. Go to step 3.
If the value of the bsc field is simplex, go to step 2.
Vol. 1 -- 2--14
BSC fault numbers
Step
Action (Continued)
Look for a notification or an alarm (fault numbers 7) concerning the CPUE or SICD
board quoted in the restart notification.
If an alarm concerning the CPUE or SICD board is in the list of current alarms,
go to step 3.
If an alarm concerning the MSW, SWC or SWE board is in the list of current
alarms, do not take the source of this alarm (with fault number 5) into account.
Go to step 5.
Step
Action
Replace the CPUE or SICD board quoted in the beginning--of hardware fault
notification:
a. Refer to the replacement procedure given in NTP < 41 >.

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the CPUE or SICD board.
Standard 15.101/EN
July 2005
2.1.7
BSC fault numbers
Vol. 1 -- 2--15
Source: Error in BSC state machine handler (GAUT)

iii
OMC
Fault number 5
Source:
BSC model:
(8) Error in BSC state machine handler (GAUT)

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because it
encountered a software problem.

BSC defense
None.

None.
FAULT TREATMENT
No maintenance is required.
Vol. 1 -- 2--16
BSC fault numbers
2.1.8
Source: Error in switchover sequence

iii
OMC
Fault number 5
Source:
BSC model:
(10) Error in switchover sequence

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain that was becoming active committed suicide and
restarted. During the switchover sequence, the process corresponding to the switchover
is not finished for one board. A notification with fault number 7 card monitoring failure
indicates the faulty board.
The notification also indicates the equipment that detected the fault.

BSC defense
None.

None.
FAULT TREATMENT
Treat the anomaly concerning the notification with fault number 7.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.9
BSC fault numbers
Vol. 1 -- 2--17
Source: BDA KO during switchover sequence

iii
OMC
Fault number 5
(11) BDA KO during switchover sequence

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that the BDA of the new active chain after switchover is not valid.
A new switchover is performed to avoid mirroring or disk access problems.

BSC defense
None.
CAUTION
Service interruption
There is loss of service because of two chain switchovers.
FAULT TREATMENT
If the problem happens again, replace the disk of the faulty chain. Refer to the replacement
procedure of the MMU or MMU_IDE (see NTP < 41 >).
Vol. 1 -- 2--18
BSC fault numbers
2.1.10
Source: Invalid mirror partitions after switchover on the new active

chain
iii
OMC
Fault number 5
(12) Invalid mirror partitions after switchover on the new

active chain
BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that a BDA partition of the new active chain is not valid. A new
switchover is started.

BSC defense
None.
CAUTION
There is loss of service because of two chain switchovers.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.11
BSC fault numbers
Vol. 1 -- 2--19
Source: Loss of the duplex link detected on passive chain

iii
OMC
Fault number 5
Source:
BSC model:
(14) Loss of duplex link detected on passive chain

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that the passive chain committed suicide and restarted because
it detected the loss of the duplex link.
The active chain sends this notification as soon as the duplex link is open.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--20
BSC fault numbers
2.1.12
Source: Inconsistency between active and passive chain

iii
OMC
Fault number 5
Source:
BSC model:
(15) Inconsistency between active and passive chains

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that the passive chain restarted with a software version different
from the active chain. The passive chain starts being consistent with the active chain.
The passive chain sends this notification as soon as the duplex link is open.

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.13
BSC fault numbers
Vol. 1 -- 2--21
Source: Context overflow for BSC (MDB) defense

iii
OMC
Fault number 5
Source:
BSC model:
(16) Context overflow for BSC (MDB) defense

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because there was
an overflow of the number of BSC defense treatment contexts.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--22
BSC fault numbers
2.1.14
Source: Switching while passive chain DP loading

iii
OMC
Fault number 5
(20) Switching while passive chain DP loading

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that the BSC performed a chain switchover while downloading
the permanent data (DP) on the passive chain.
The BSC commits suicide and starts again so as to save data consistency. The BSC sends
this notification as soon as the duplex link is open.

BSC defense
None.
CAUTION
The service is lost.
FAULT TREATMENT
No maintenance is required. Look for the source of the first switchover.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.15
BSC fault numbers
Vol. 1 -- 2--23
Source: Error detected during check partition

iii
OMC
Fault number 5
Source:
BSC model:
(21) Error detected during check partition

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because an error
was detected during a partition check. The faulty partition is deleted.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--24
BSC fault numbers
2.1.16
Source: CPUE BOOT flashing failed

iii
OMC
Fault number 5
Source:
BSC model:
(23) CPUE BOOT flashing failed

BSC12000 + BSC12000 HC
FAULT ANALYSIS
or SICD BOOT flashing failed.

BSC defense
None.

None, if the problem appears for a passive chain.
FAULT TREATMENT
No maintenance is required. If the problem often happens, replace the CPUE or SICD
board. Refer to the replacement procedure given in NTP < 41 >.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.17
BSC fault numbers
Vol. 1 -- 2--25
Source: Restart to take into account the new BSC customization

iii
OMC
Fault number 5
Source:
BSC model:
(24) Restart to take into account the new BSC

customization
BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that the passive chain committed suicide and restarted to take
into account its new customization.
The customization data come from the active chain and they are copied to the new disk of
the passive chain:
the current partition number
the BSC number
the BSC type
the PCM type (to have access to the OMC--R)
The restart takes place after one of the following events:
disk maintenance
operator request
BSC software upgrade requiring a disk replacement
The restart of the passive chain is necessary to take into account the customization. It is
a normal behavior. Besides, the customization is really complete only when the passive
chain became active once.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--26
BSC fault numbers
2.1.18
Source: Degraded disk

iii
OMC
Fault number 5
Source:
BSC model:
(25) Degraded disk

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because its disk is
degraded: the number of erroneous access on the disk reaches the threshold activating the
anomaly. In the case of BSC simplex mode, this alarm may appear with a fault number 46
alarm.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
If the value of the bsc field is duplex, check the state of the MMU boards in
the result window of the Display all command.
If the MMU or MMU_IDE boards state is working, this fault number

indicates a transient problem or a bad operation of the board.
i.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--27
Action (Continued)
ii.
If this problem often happens, the replacement of the board must be

considered. Go to step 2.
If the state of one of the MMU or MMU_IDE boards state is partially

degraded, the replacement of the board must be considered. Go to step 2.
If the state of one of the MMU or MMU_IDE boards is degraded, replace

the faulty board. Go to step 2.
If the value of the bsc field is simplex, look for other notifications that would
confirm that there is a problem on the MMU or MMU_IDE board of the chain that
is out of order.
i.
ii.
Replace the faulty MMU or MMU_IDE board:
If the board has not been replaced, go to step2.

Step
2
Action
Replace the faulty MMU or MMU_IDE board (Field Replaceable Unit):
Additional checks
Step
Action
If necessary, clear the alarm concerning the MMU or MMU_IDE board.
Vol. 1 -- 2--28
BSC fault numbers
2.1.19
Source: Cancellation of probative phase

iii
OMC
Fault number 5
(27) Cancellation of probative phase

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the
operator cancelled the probative phase during a software upgrade. The operator cancelled
the new software version (type 5 software upgrade). The active chain of n+1 software
version committed suicide. The new active chain of n software version updates the
consistency of the passive chain. When the BSC is in duplex state, the two chains are in
n software version.

BSC defense
None.
CAUTION
During the network unconfiguration and reconfiguration, an outage
that lasted less than five minutes happened.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.20
BSC fault numbers
Vol. 1 -- 2--29
Source: End of probative phase OK

iii
OMC
Fault number 5
Source:
BSC model:
(28) End of probative phase OK

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that the passive chain committed suicide and restarted after the
successful ending of the probative phase during a type 5 software upgrade.
Toward the end of the probative phase, the two chains are in the following state:
the active chain displays 13 in the display panels of its SUP or SUP2 board, the n+1
software version is running, and its BDA is n+1 as well
the passive chain displays 10 in the display panels of its SUP or SUP2 board, the n+1
software version is installed, but its BDA is still n. Thats why the passive chain commits
suicide and restarts: to take into account the new BDA n+1 from the active chain.
When the BSC is in duplex state, the two chains are in n+1 software version.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--30
BSC fault numbers
2.1.21
Source: New BDA edition

iii
OMC
Fault number 5
(29) New BDA edition

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that the passive chain committed suicide and restarted to take
into account the new edition of the BDA, already built. This procedure is used for the
changes of frequency plans.
It is a normal behavior to update the data on the passive chain.

BSC defense
None.
CAUTION
During the update of the new BDA, an outage that lasted less than
five minutes happened.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.22
BSC fault numbers
Vol. 1 -- 2--31
Source: Preparation of a type 5 upgrade

iii
OMC
Fault number 5
Source:
BSC model:
(30) Preparation of a type 5 upgrade

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted to prepare for the
update of the BDA: the software compatible with the new version of the BDA are transferred
in the current partition and will be taken into account after the chain restart. The two chains
are started successively.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--32
BSC fault numbers
2.1.23
Source: Type 5 upgrade running

iii
OMC
Fault number 5
Source:
BSC model:
(31) Type 5 upgrade running

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted during a type 5
software upgrade. The passive chain restarts in n+1 software version. The active chain is
always in n software version.

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.24
BSC fault numbers
Vol. 1 -- 2--33
Source: Old release running on passive chain

iii
OMC
Fault number 5
Source:
BSC model:
(32) Old release running on passive chain

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted during a type 5
software upgrade. The passive chain restarts in n software version. The active chain is in
n+1 software version.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--34
BSC fault numbers
2.1.25
Source: Unsuccessful preparation of a type 5 upgrade

iii
OMC
Fault number 5
Source:
BSC model:
(33) Unsuccessful preparation of a type 5 upgrade

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the taking
into account of the software during a type 5 software upgrade was unsuccessful. The new
BDA can not been built.

BSC defense
The BSC takes into account the old software version and starts with the passive chain.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.26
BSC fault numbers
Vol. 1 -- 2--35
Source: BDA inconsistency

iii
OMC
Fault number 5
Source:
BSC model:
(50) BDA inconsistency

BSC 12000 + BSC 12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the BDA
was intrinsically inconsistent.

BSC defense
None.

None.
FAULT TREATMENT
Maintenance using the OMC--R
Step
1
Action
Reset the partitions at the OMC--R:
a. Select the bsc object in the OMC--R Browser window.
b. Select the On--line reset option in the BDA sub--menu of the Configuration
menu.
c. For more information, refer to NTP <034>. Then go to step 2.
Wait for the notification BSC requires a BDA on--line building. Then go to step 3.
Build the BDA:

b. Select the Build option in the BDA sub--menu of the Configuration menu.
c. For more information, refer to NTP <34>. Then go to step 4.
Vol. 1 -- 2--36
BSC fault numbers
Step
Action (Continued)
Execute a general audit to ensure that the BDE and the BDA are consistent:

b. Select the Audit option in the BDA sub--menu of the Configuration menu.
c. For more information, refer to NTP < 32 >.
If the BDA is operational, go to step 5.
If the BDA is not operational, call the manufacturer.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the incoherent BDA.
Standard 15.101/EN
July 2005
2.1.27
BSC fault numbers
Vol. 1 -- 2--37
Source: GES-- MS / GES-- SL are incoherent

iii
OMC
Fault number 5
Source:
BSC model:
(51) GES--MS / GES--SL are incoherent

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because GES--MS
and GES--SL are incoherent.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--38
BSC fault numbers
2.1.28
Source: Passive chain does not answer on RGA request

iii
OMC
Fault number 5
Source:
BSC model:
(52) Passive chain does not answer on RGA request

BSC12000 + BSC12000 HC
FAULT ANALYSIS
it did not answer the RGA request.

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.1.29
BSC fault numbers
Vol. 1 -- 2--39
Source: Passive chain suicide on RGA request

iii
OMC
Fault number 5
Source:
BSC model:
(53) Passive chain suicide on RGA request

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that the passive chain committed suicide and restarted following
an RGA request.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--40
BSC fault numbers
2.1.30
Source: No communication with switching board

iii
OMC
Fault number 5
Source:
BSC model:
(101) No communication with switching board

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because its CPUM
board (CPU--OMU) lost contact with an SWC board.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
If the value of the bsc field is simplex:
i.
Wait for the duplex state.
ii.
When the BSC is in duplex mode, go to step 2.
If the value of the bsc field is duplex, go to step 2.

2
Look for the following notifications:

fault number 520 fault on switching matrix access
fault number 521 fault on switching matrix
fault number 522 switch supervision failure
If there are alarms, go to step 3.

If there are not any alarms, this fault number indicates a transient problem
or a bad operation of the board concerned. Clear the alarm. Go to step 6. If

this problem often happens, the board replacement must be considered. Go
to step 4.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--41
Action (Continued)
Perform a Display chain information command to check the state of the SWC
board.
If the board state is working, this fault number indicates a transient problem
or a bad operation of the board concerned.
i.
ii.
If this problem often happens, the board replacement must be considered.

Go to step 4.
If the board state is faulty:

i.
Treat the alarm with fault number 520 or 521 or 522.
ii.
Then go to step 5.
Step
4
Action
Replace the SWC board quoted in the beginning--of hardware fault notification
(Field Replaceable Unit):
Additional checks
Step
Action
If necessary, clear the alarm concerning the SWC board.
Vol. 1 -- 2--42
BSC fault numbers
2.1.31
Source: No communication with ECI card or fault on ECI card

iii
OMC
Fault number 5
Source:
BSC model:
(102) No communication with ECI card or fault on ECI card

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the control
cabinet lost contact with the ECI board (through the SICX board).

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.

2
Look for the following notification: fault number 7 card monitoring failure
If there are not any alarms, this fault number indicates a transient problem or a
bad operation of the board concerned. Clear the alarm. Go to step 7. If this
problem often happens, the board replacement must be considered. Go to
step 4.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--43
Action (Continued)
Perform a Display chain information command to check the state of the ECI board.
i.
ii.

Go to step 4.

i.
Treat the alarm with fault number 7.
ii.
Then go to step 7.
Step
Action
Check the BIST of the ECI board:
a. Power off and then power on the chain containing the board concerned.
b. Look at the BIST LED on the front panel on the ECI board.
If the BIST LED is on for a few seconds, and then becomes off, the ECI board
is operational. Replace the SICX board. Go to step 6.
If the BIST LED remains on, the ECI board is not operational. Go to step 5.
Replace the ECI board quoted in the beginning--of hardware fault notification (Field
Replaceable Unit):
Replace the SICX board (Field Replaceable Unit):

Vol. 1 -- 2--44
BSC fault numbers
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the board.
Standard 15.101/EN
July 2005
2.1.32
BSC fault numbers
Vol. 1 -- 2--45
Source: No communication with SICX card or fault on SICX card

iii
OMC
Fault number 5
Source:
BSC model:
(103) No communication with SICX card or fault on SICX

card
BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because it lost
contact with the SICX board.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.

2
Look for the following notification: fault number 7 card monitoring failure
If there are not any alarms, this fault number indicates a transient problem or a
bad operation of the SICX board. Clear the alarm. Go to step 6. If this problem
often happens, the board replacement must be considered. Go to step 4.
Vol. 1 -- 2--46
BSC fault numbers
Step
Action (Continued)
Perform a Display chain information command to check the state of the SICX
board.
i.
ii.

Go to step 4.

i.
Treat the alarm with fault number 7.
ii.
Then go to step 5.
Step
Action
Replace the SICX board quoted in the beginning--of hardware fault notification:

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the SICX board.
Standard 15.101/EN
July 2005
2.1.33
BSC fault numbers
Vol. 1 -- 2--47
Source: No communication with slave switching board

5_10
OMC
Fault number 5
Source:
BSC model:
(104) No communication with slave switching board

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because it lost
contact with an SWE or MSW board.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
If the value of the bsc field is duplex, perform a Display chain information
command on the bsc object to check the state of the PCM links 0 to 63.
If one PCM link is faulty, treat the problem.

If at least 16 internal PCM links are faulty, the switching board is faulty. Go
to step 3.
Vol. 1 -- 2--48
BSC fault numbers
Step
Action (Continued)
Look for a notification or an alarm (with fault number 524 Slave switch board not
present) concerning the SWE board quoted in the restart notification.
a. Treat this notification.

b. Then go to step 4.
Step
Action
Replace the switching board quoted in the beginning--of hardware fault notification:

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the replaced switching board.
Standard 15.101/EN
July 2005
2.1.34
BSC fault numbers
Vol. 1 -- 2--49
Source: No communication with SLS card or fault on SLS card

iii
OMC
Fault number 5
Source:
BSC model:
(105) No communication with SLS card or fault on SLS card

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the SUP
or SUP2 lost contact with the SLS or SLS2 board.

BSC defense
None.

None, if the chain concerned is the passive chain.
If the chain concerned is the active chain, the link between the BSC and the OMC--R is lost,
but there is not any impact on the service either.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.
Vol. 1 -- 2--50
BSC fault numbers
Step
Action (Continued)
Look for the following notification:
fault number 1155 Fault on SLS card

or a bad operation of the SLS or SLS2 board. Clear the alarm. Go to step
6. If this problem often happens, the board replacement must be
considered. Go to step 4.
Perform a Display chain information command to check the state of the SLS or
SLS2 board.
or a bad operation of the board concerned. Clear the alarm. Go to step 6. If this
problem often happens, the board replacement must be considered. Go to step
4.
If the board state is faulty, treat the alarm with fault number 1155. Then go to
step 5.
Step
Action
Replace the SLS or SLS2 board quoted in the beginning--of hardware fault
notification:

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the SLS or SLS2 board.
Standard 15.101/EN
July 2005
2.1.35
BSC fault numbers
Vol. 1 -- 2--51
Source: Operator request

iii
OMC
Fault number 5
(106) Operator request

BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because the
operator requested it.

BSC defense
None.

None.
CAUTION
Nevertheless, there is a loss of service if the operator requests a
chain suicide while the other chain is unable to become active and
operational.
FAULT TREATMENT
Vol. 1 -- 2--52
BSC fault numbers
2.1.36
Source: Degraded REM link

ii
OMC
Fault number 5
Source:
BSC model:
(107) Degraded REM link

BSC12000 + BSC12000 HC
FAULT ANALYSIS
the REM link between the SUP2 board, SLS2 board, and the OMC--R is broken. The REM
link (between the SICX and the SLS2 board) is tested cyclically.

BSC defense
None.

None. If the passive chain becomes active, it will not be linked to the OMC--R.
FAULT TREATMENT
Preliminary checks
Step
Action
Look for a notification or an alarm with fault number 1164 OMC access failure.

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the REM link.
Standard 15.101/EN
July 2005
2.1.37
BSC fault numbers
Vol. 1 -- 2--53
Source: No communication with SICD or RCB card or fault on SICD

or RCB card
iii
OMC
Fault number 5
Source:
BSC model:
(128) No communication with SICD or RCB card or fault on

SICD or RCB card
BSC12000 + BSC12000 HC
FAULT ANALYSIS
its CPUM board (CPU--OMU) lost contact with a SICD or RCB board and the associated
internal PCM link.

BSC defense
None.

None. Only the passive chain is impacted.
Nevertheless, if the passive chain becomes active (after a chain switchover for instance),
it will already be degraded.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.
Vol. 1 -- 2--54
BSC fault numbers
Step
Action (Continued)
Look for the following notification:
with fault number 7 Card monitoring failure concerning the SICD board quoted
in the restart notification
with fault number 404 RCB0 failure concerning the RCB 0 board quoted in the
restart notification
with fault number 523 fault on internal PCM link (BSC, TCU) concerning the
internal PCM link quoted in the notification

or a bad operation of the SICD or RCB board or PCM link. Clear the alarm.
Go to step 7. If this problem often happens, the board replacement must be
considered. Go to step 4 or 5.
Perform a Display chain information command to check the state of the SICD and
RCB board and the associated internal PCM links 2 or 3.
If the state is working, this fault number indicates a transient problem or a bad
operation of the board concerned. Clear the alarm. Go to step 7. If this problem
often happens, the board replacement must be considered. Go to step 4 or 5.
If the state is faulty, treat the alarm(s). Then go to step 6.
Step
4
Action
Replace the SICD board quoted in the beginning--of hardware fault notification
(Field Replaceable Unit):
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--55
Action (Continued)
Replace the RCB board quoted in the beginning--of hardware fault notification (Field
Replaceable Unit):
Additional checks
Step
Action
Vol. 1 -- 2--56
BSC fault numbers
2.1.38
Source: SICD port selftests not OK

iii
OMC
Fault number 5
Source:
BSC model:
(129) SICD port selftests not OK

BSC12000 + BSC12000 HC
FAULT ANALYSIS
the SICD ports are not operational anymore. They are tested cyclically on the passive chain.

BSC defense
None.

None, as long as the chain remains passive.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
If the value of the bsc field is duplex, check the state of the SICD ports.
If the SICD ports are operational, clear the alarm. Go to step 4.

If the SICD ports are not operational, go to step 2.
2
Look for a notification or an alarm with fault number 1153 Negative test on passive
chain LAPD channel (layer 2).
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--57
Action (Continued)
Look for a notification or an alarm with fault number 8 Negative built--in self--test
for card concerning the SICD boards.
Additional checks
Step
Action
If necessary, clear the alarm concerning the SICD ports.
Vol. 1 -- 2--58
BSC fault numbers
2.1.39
Source: No communication with CCS7 card or fault on CCS7 card

iii
OMC
Fault number 5
Source:
BSC model:
(161) No communication with CCS7 card or fault on CCS7

card
BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because its CPUM
board (CPU--OMU) lost contact with a CCS7 board.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the BSC, by performing a Display command on the bsc object.
If the value of the bsc field is duplex, check the state of the CCS7 boards
and the associated internal PCM link 0 by looking again at the description
window that displays the result of the Display all command.
If the CCS7 boards state is working, clear the alarm. Go to step 4.

If the state of one of the CCS7 boards is faulty, replace the faulty board. Go
to step 3.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--59
Action (Continued)
Look for a notification or an alarm (with fault number 7 Card monitoring failure)
concerning the CCS7 board quoted in the restart notification, or fault number 523
fault on internal PCM (BSC, TCU) concerning the internal PCM link 0 quoted the
in restart notification.
Step
3
Action
Replace the CCS7 board quoted in the beginning--of hardware fault notification:
Additional checks
Step
Action
If necessary, clear the alarm concerning the replaced CCS7 board.
Vol. 1 -- 2--60
BSC fault numbers
2.1.40
Source: CCS7 port selftests not OK

iii
OMC
Fault number 5
Source:
BSC model:
(162) CCS7 port selftests not OK

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because its CCS7
ports are not operational anymore. They are tested cyclically on the passive chain.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the BSC, by performing a Display command on the bsc object.
If the value of the bsc field is duplex, check the state of the CCS7 ports.
If the CCS7 ports are operational, clear the alarm. Go to step 4.

If the CCS7 ports are not operational, go to step 2.
2
Look for a notification or an alarm with fault number 1154 Negative test on passive
chain CCS7 signalling link (layer 2).
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--61
Action (Continued)
Look for a notification or an alarm with fault number 8 Negative built--in self--test
for card concerning the CCS7 boards.
Additional checks
Step
Action
If necessary, clear the alarm concerning the CCS7 ports.
Vol. 1 -- 2--62
BSC fault numbers
2.1.41
Source: No communication with TCU card or fault on TCU card

iii
OMC
Fault number 5
(176) No communication with TCU card or fault on TCU

card
BSC12000 + BSC12000 HC
Source:
BSC model:
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because it cannot
access any TCU.
When one of the items of equipment related to the LAPD is faulty, the chain cannot
communicate with the TCUs anymore and commits suicide:
SICD boards
RCB boards
SWC boards
internal PCM links

BSC defense
None.

If only one chain could not access the TCUs, it is degraded: 32 must be displayed on
the display panels of the SUP board of the passive chain.
There is not any impact on the service as long as the active chain can access the TCU.
If both chains cannot access the TCUs, both chains are degraded: 32 must be
displayed on the display panels of the SUP boards of both chains. At the OMC--R, the
transcoder objects are disabled--dependency.
CAUTION
The network is not operational. There is no service.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--63
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.

2
Check the state of the following elements on the passive chain:

SICD boards
RCB boards
SWC boards
internal PCM links
If the boards state is working, clear the alarm. Go to step 5.
If the boards state is faulty, go to step 3.
Look for a notification or an alarm concerning the passive chain:

with fault number 7 Card monitoring failure or fault number 8 Negative built--in
self test result for card concerning the SICD board
with fault number 404 RCB0 failure concerning the RCB 0 board
with fault number 521 fault on switching matrix concerning the SWC board
with fault number 522 switch supervision failure concerning the SWC board
with fault number 523 fault on internal PCM link (BSC, TCU) concerning the
internal PCM link
Vol. 1 -- 2--64
BSC fault numbers
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the TCU access.
Standard 15.101/EN
July 2005
2.1.42
BSC fault numbers
Vol. 1 -- 2--65
Source: O&M bus self-- tests not OK

iii
OMC
Fault number 5
Source:
BSC model:
(192) O&M bus selftests not OK

BSC12000 + BSC12000 HC
FAULT ANALYSIS
the O&M bus is not operational anymore.
The O&M bus and all the UTE boards connected to it (ALA, DDTI, BSCB, and TSCB
boards) are tested on the passive chain: at every chain restart, and every 30 minutes.
When all the UTE boards are out of reach, the passive chain commits suicide and restarts.
The ECI board is involved in the problem.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
object.
i.
ii.
Vol. 1 -- 2--66
BSC fault numbers
Step
Action
Replace the ECI board (Field Replaceable Unit). For more information, refer to
NTP < 41 >. Then go to step 3.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the O&M bus.
Standard 15.101/EN
July 2005
2.2
BSC fault numbers
Vol. 1 -- 2--67
Fault number: 6
iii
Fault number:
6
: Restart after chain suicide due to trap
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because a software
error occurred.
If the active chain was concerned, a switchover took place.
If the passive chain was concerned, a suicide followed by a restart took place.

BSC defense
None.
CAUTION
None, except if the BSC was in simplex mode. In the latter case, an
outage took place.
FAULT TREATMENT
Send the traces to the manufacturer, to find out what happened.
Vol. 1 -- 2--68
BSC fault numbers
2.3
Fault number: 7
iii
Fault number:
7
: Card monitoring failure
Type : equipmentAlarm
FAULT ANALYSIS
This notification indicates that a board does not answer to the CPUM board or the ECI
board.
The type and the position of the board, and the TE number are given in the notification.
The boards concerned can be one of the following:
in the BSC control cabinet:
CCS7 boards
CPUE boards
SICX board
SICD boards
CPUM board
in the BSC equipment cabinet:
ECI board
UTE boards (ALA, TSCB, BSCB, DDTI boards)
BSC defense
If a CCS7, SICX, or SICD board of the active chain is concerned, the active chain may
commit suicide if the passive chain is in a better state than the active chain.
If a CPUE board is involved, the chain commits suicide cyclically.

If a control cabinet board or the ECI board is involved, there is not any impact on the service.
CAUTION
If an equipment cabinet board (UTE board) is concerned, then there
is a loss of service.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--69
FAULT TREATMENT
Preliminary checks
Step
1
Action
Identify the equipment concerned by the notification:
If the board quoted in the notification is a DDTI board, go to step 3.
If the board quoted in the notification is not a DDTI board, go to step 2.
Check the state of the BSC boards, by performing a Display all command on the
bsc object.
If the state of the board quoted in the notification is faulty, go on site to check
the faulty board. Go to step 5.
In the presence of a fault number 7 on a DDTI board, perform a Display all

command on the pcmCircuit object associated with the concerned DDTI board.
If the administrativeState of the pcmCircuit object is locked, unlock it.
If the administrativeState of the pcmCircuit object is unlocked, consider its
operationalState:
If the operationalState of the pcmCircuit object is enabled, go to step 4.

If the operationalState of the pcmCircuit object is disabled, the PCM link
concerned is not operational yet. Wait.
If the operationalState of the pcmCircuit object is disabled, and the

availabilityStatus is dependency, look for a problem concerning the internal
PCM link (with fault number 523).

availabilityStatus is failed, perform a Display all command on the bsc
object to check the state of the DDTI board.
If the state of the DDTI board is working. Clear the alarm. Go to step 8.
If the state of the DDTI board is faulty, replace the DDTI board. Go to
step 6.
4
Perform a Display all command on the pcmCircuit object to check the value of the
DDTIIntstate parameter.
If the value of the DDTIIntstate parameter is working, clear the alarm and look
for a problem concerning the PCM link (with fault number 1151 or 1067).
If the value of the DDTIIntstate parameter is faulty, the DDTI board must be
replaced. Go to step 6.
Vol. 1 -- 2--70
BSC fault numbers
Step
Action
Check that the boards of the chain are correctly positioned. Check the PROM as
well.
If one or several boards are badly positioned, position it (them) correctly.

If everything is correct, call the manufacturer.
If the PROM of a board is not the right one, replace the board. Go to step 6.
Replace the equipment mentioned in the notification (Field Replaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >:

boards located in the BSC control cabinet:
CCS7 boards
CPUE boards
SICX board
SICD or SICD8V boards
CPUM board
boards located in the BSC equipment cabinet:
DDTI boards
ALA board
ECI board
TSCB board
BSCB board
b. The operations for return to service are performed by the system.
c. Then go to step 7.
Additional checks
Step
7
Action
Check that the repaired chain is operational:
If a board in the equipment cabinet (the DDTI and ALA boards) has been
replaced, check the return to correct operation of the chain by a change of state
displayed at the OMC--R.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--71
Action (Continued)
If a board in the control cabinet or the ECI board has been replaced, check that
the repaired chain does not commit suicide again:
At the OMC--R, warning notifications (with fault number 13) allow to know if
the BSC restarts correctly.
On--site, check that 12 is displayed in the SUP board display panels after
the BSC start--up.
If necessary, clear the alarm.
Vol. 1 -- 2--72
BSC fault numbers
2.4
Fault number: 8
iii
Fault number:
8
: Negative built in self test result for card
FAULT ANALYSIS
At the initialization of a BSC board, a global result is sent. If the BISTs are not correct, the
board is unavailable.
The type and the position of the board, and the TE number are given in the notification.

BSC defense
If a CCS7, SICX, or SICD board of the active chain is concerned, the active chain may
commit suicide if the passive chain is in a better state than the active chain.
If a CPUE board is involved, the chain commits suicide cyclically.

If a control cabinet board or the ECI board is involved, there is not any impact on the service.
CAUTION
If an equipment cabinet board (UTE board) is concerned, then there
is a loss of service.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the BSC boards, by performing Display chain information and
Display all commands on the bsc object.
If the state of the board quoted in the notification is faulty, replace the faulty
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--73
Step
2
Action
Replace the board mentioned in the test result notification (Field Replaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >:
on the BSC control cabinet:
CPU133IE board
CCS7 boards
CPU133 boards
SICD or SICD8V boards
on the BSC equipment cabinet:
DDTI boards
ALA board
ECI board
TSCB board
BSCB board
SWC board
Additional checks
Step
3
Action
Check that the repaired chain is operational and does not commit suicide again:
At the OMC--R, warning notifications (with fault number 13) allow to know if the
BSC restarts correctly.
On--site, check that 12 is displayed in the SUP board display panels after the
BSC start--up.
Vol. 1 -- 2--74
BSC fault numbers
2.5
Fault number: 11 (BSC 12000)

iii
Fault number:
11
: Restart after chain suicide due to NMI
If the BSC 12000 HC is concerned, refer to Paragraph 2.6.
FAULT ANALYSIS
This notification indicates that a chain committed suicide because a Non Maskable Interrupt
(NMI) happened.
If it is the active chain, a switchover is performed, according to the state of the other chain.
If it is the passive chain, it starts again.
One of the Multibus II boards (CPUE, SICD8V, CCS7, SUP and CPUM (CPU66SE) boards)
supervised by the CPUM board did not answer and was reset by a NMI.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check that the chain concerned restarts correctly.
If the chain runs in nominal mode at the end of the restart (12 is displayed in
the SUP board display panels), go to step 9.
If the chain runs in degraded mode at the end of the restart (32 is displayed
in the SUP board display panels), go to step 2.
If the chain does not restart, go to step 3.
Note the name of the board given in the notification:

If the board quoted in the notification is a CPUE, SICD8V, CCS7, or SICX board,
go to step 4.
If the board quoted in the notification is the CPUM board (CPU66SE) or the SUP
board, go to step 3.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--75
Action (Continued)
To discover which board is faulty, observe the BSC behavior during the start--up.
If the start--up does not begin, the SUP board is faulty. Go to step 5.
If the start--up begins (see displays on the SUP board display panels) and then
stops, the CPUM board (CPU66SE) is faulty. Go to step 6.
Look for a notification with fault number 5 Restart after chain suicide due to internal
cause, or OMC, or fault number 7 Card monitoring failure that is still active after
the chain restarted.
a. Treat the notification.
Step
5
Action
Replace the faulty SUP board (Field Replaceable Unit):
b. The return to service operations are performed by the system. Then go to
step 7.
Replace the faulty CPUM board (CPU66SE) (Field Replaceable Unit):

step 7.
Additional checks
Step
7
Action
a. At the OMC--R, warning notifications (with fault number 13) allow to know if the
b. On--site, check that 12 is displayed in the SUP board display panels after the
BSC start--up.
Vol. 1 -- 2--76
BSC fault numbers
2.6
Fault number 11: (BSC 12000 HC)

iii
Fault number:
11
: Restart after chain suicide due to NMI
FAULT ANALYSIS
This notification indicates that a chain committed suicide because a Non Maskable Interrupt
(NMI) happened.
If it is the active chain, a switchover is performed, according to the state of the other chain.
One of the Multibus II boards (CPUE (CPU133), SICD8V, CCS7, SUP2 and CPUM
(CPU133IE) boards) supervised by the CPUM board did not answer and was reset by a
NMI.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check that the chain concerned restarts correctly.
If the chain runs in nominal mode at the end of the restart (12 is displayed in
the SUP2 board display panels), go to step 9.
If the chain runs in degraded mode at the end of the restart (32 is displayed
in the SUP2 board display panels), go to step 2.
If the chain does not restart, go to step 3.
Note the name of the board given in the notification:

If the board quoted in the notification is a CPUE (CPU133), SICD8V, CCS7, or
SICX board, go to step 4.
If the board quoted in the notification is the CPUM board (CPU133IE) or the
SUP2 board, go to step 3.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--77
Action (Continued)
To discover which board is faulty, observe the BSC behavior during the start--up.
If the start--up does not begin, the SUP2 board is faulty. Go to step 5.
If the start--up begins (see displays on the SUP2 board display panels) and then
stops, the CPUM board (CPU133IE) is faulty. Go to step 6.
Look for a notification with fault number 5 Restart after chain suicide due to internal
cause, or OMC, or fault number 7 Card monitoring failure that is still active after
the chain restarted.
a. Treat the notification.
Step
5
Action
Replace the faulty SUP2 board (Field Replaceable Unit):
step 7.
Replace the faulty CPUM board (CPU133IE) (Field Replaceable Unit):

step 7.
Additional checks
Step
7
Action
b. On--site, check that 12 is displayed in the SUP2 board display panels after the
BSC start--up.
Vol. 1 -- 2--78
BSC fault numbers
2.7
Fault number: 13
iii
Fault number:
13
: Chain restart in progress
FAULT ANALYSIS
This notification indicates the BSC state during the chain restart.
The Location field identifies the chain that is restarting, and which chain is the active one.
The operator must check the state of the BSC by performing a Display all command.
For more information, refer to NTP < 41 > (Description of a BSC start--up) to learn the
different restart phases of the BSC.
The values of the Restart phase field are:
Restart phase
Explanation
Beginning of restart
notification generated just after the

CPUM board started
Restart completed
notification generated just before the

permanent data downloading started
BSCs chain switchover completed
notification sent by the active chain just

after the switchover
Switch state is DUPLEX
notification sent by the active chain after

the dynamic data on the passive chain
have been updated
BSC software version change completed

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.8
BSC fault numbers
Vol. 1 -- 2--79
Fault number: 14
iii
Fault number:
14
: Indication of chain restart cause
FAULT ANALYSIS
This notification indicates the source of the restart of the chain.
The values of the Source field are:
Source No.
Source wording
126
Reset due to Watchdog NMI

(state: not operational)
190
External Reset
220
Manual NMI
(state: operational)
222
Software Reset
238
Manual NMI
(state: not operational)
246
Manual Reset
250
Reset due to watchdog NMI

(state: operational)
254
Reset on Power On
Explanation
Other notifications related to the chain

restart are sent as well.
No other notifications are sent.

This source is the only significant one.

BSC defense
None.

None.
ON--SITE MAINTENANCE
Vol. 1 -- 2--80
BSC fault numbers
2.9
Fault number: 15
iii
Fault number:
15
: Chain restart due to intermediate card
FAULT ANALYSIS
This notification indicates that the loss of a link (ECI, SICX) has led to the suicide of the
active chain.
The ECI board can send this notification during the chain restart, when it loses its link with
the SICX board.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check whether the fault number 15 was sent alone, or if there are other
notifications:
If there are other notifications, go to step 2.
Wait for the start--up end, and check that the chain is operational again.
If the chain is operational again, the following notifications must have been sent:
fault number 23 Beginning of BSC disk partition update

fault number 24 End of BSC disk partition update
fault number 13 Chain restart in progress sent several times with different
sources
If the passive chain does not restart:
either the passive chain is powered off: look for a notification with fault
number 411 Power supply fault of the other chains MPU shelf,
or one of the important boards (CPUM, CPUE, MMU and SUP) is faulty: look
for a notification concerning one of these boards.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
BSC fault numbers
Vol. 1 -- 2--81
Action (Continued)
The notification with fault number 15 was sent alone because the chain has been
powered off automatically, for one of the following reasons:
the ventilation system is faulty. Go to step 4.
one or several straps on the MPU backpanel are badly positioned or missing.
Go to step 5.
The chain restart stopped and 0B is displayed in the display panels of the SUP
board: the Ethernet link is faulty. Go to step 6.
one of the important boards (CPUM, CPUE, MMU and SUP) is faulty. Go to
step 7.

Step
4
Action
Look for a problem concerning the ventilation system: the power supply or the
VENT board may be faulty.
If the ventilation system is operational, go to step 5.
If the ventilation system is not operational, perform the necessary corrective
maintenance. Then go to step 8.
Check the straps on the MPU backpanel.

If some straps are badly positioned or missing, position them correctly on the
MPU backpanel. For more information, refer to the BSC Reference NTP . Then
go to step 8.
If the straps are operational, go to step 6.
Look for a problem concerning the Ethernet link:
the link between the CPUM board and the cabinet

the transceiver
the CPUM board
the cable between the MMU_IDE board and the cabinet
If all the equipment is operational, go to step 8.
If one of the items of equipment if faulty, perform the necessary corrective
maintenance. Concerning the transceiver, fix the passive chain first.
7
Look for a notification concerning the CPUM, CPUE, MMU and SUP boards, and
treat it. Then go to step 8.
Vol. 1 -- 2--82
BSC fault numbers
Additional checks
Step
8
Action
b. On--site, check that 12 is displayed in the SUP board display panels after the
BSC start--up.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.10
BSC fault numbers
Vol. 1 -- 2--83
Fault number: 16
iii
Fault number:
16
: Fault on active/passive chains link
FAULT ANALYSIS
This notification is sent by the current active chain, or the new active chain.
It indicates the loss of the link between the active chain and the passive chain. The possible
sources are as follows:
a chain switchover or a chain restart, and this notification is sent systematically during
these events
a problem on the link between the two chains
a problem on the active chain
a problem on the passive chain

BSC defense
The passive chain (not mentioned in the notification) restarts.

None.
FAULT TREATMENT
Preliminary checks
Step
Action
Monitor the different phases of the BSC restart. For more information, refer to
NTP < 41 > to know the different restart phases of the BSC.
Check that this alarm is automatically cleared 20 minutes later.
Check the BSC state by performing a Display all command on the bsc object.
Vol. 1 -- 2--84
BSC fault numbers
Step
Action (Continued)
If the BSC is operational is duplex mode:
If the link is reestablished during the chain switchover or chain restart, no

maintenance is required. Go to step 7.
If the problem occurs cyclically, out of a chain switchover or chain restart,

look for other alarms or notifications to identify the problem.
If the BSC is operational is simplex mode:

i.
Look for a notification indicating the restart of the passive chain.
ii.
Look for a message from the passive chain in the alarm history file.
If a notification is available, treat it.
If no message is available at the OMC--R, it is because one of the vital
boards of the chain (SUP or CPUM board) is out of service, or because
the Ethernet link between the active and the passive chain is faulty. As
a consequence, the chain did not have enough time to send a message.
Go to step 4.
Step
Action
Use the TML to identify the faulty board (s). Then go to step 5.
If necessary replace the faulty board(s). The operations for return to service are
performed by the system. Then go to step 6.
Additional checks
Step
6
Action
At the OMC--R, warning notifications (with fault number 13) allow to know if the
On--site, check that 12 is displayed in the SUP board display panels after the
BSC start--up.
Check that the fault has disappeared.

Look at the alarm history file to see if the notification has been transferred there.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.11
BSC fault numbers
Vol. 1 -- 2--85

iii
Fault number:
20
: Alarm on clockship of the SUP board
Type : communicationsAlarm
FAULT ANALYSIS
This notification indicates that there is a problem with the clockship of the SUP board of the
chain concerned.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Check the SW12 strap on SUP board (see NTP < 41 >).
If the strap is well positioned, go to step 2.
If the strap is badly positioned, go to step 3.
Replace the SUP board of the chain concerned by the fault (Field Replaceable Unit)
b. The operations for return to service are performed by the system. Then go to
step 4.
Position the SW12 strap correctly. Then go to step 4.
Additional checks
Step
Action
If necessary, clear the alarm concerning the SUP board.
Vol. 1 -- 2--86
BSC fault numbers
2.12
Fault number: 20 (BSC 12000 HC)

iii
Fault number:
20
: Alarm on clockship of the SUP board
FAULT ANALYSIS
This notification indicates that there is a problem with the clockship of the SUP2 board of
the chain concerned.

BSC defense
None.

None.
FAULT TREATMENT
Step
Action
Replace the SUP2 board of the chain concerned by the fault (Field Replaceable
Unit):

b. The operations for return to service are performed by the system. Then go to
step 2.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
If necessary, clear the alarm concerning the SUP2 board.
Standard 15.101/EN
July 2005
2.13
BSC fault numbers
Vol. 1 -- 2--87
Fault number: 21
iii
Fault number:
21
: Beginning of circular file pre--overflow
Type : qualityOfServiceAlarm
FAULT ANALYSIS
This notification is sent by the active chain and it indicates a pre--overflow beginning on one
of the BSC circular files.
The number of the file is shown in the warning notification.

BSC defense
None.

None.
Nevertheless, there is a risk of loss of data, depending on the circular file concerned
(observations, software anomalies, hardware fault notifications, software fault notifications,
state change notifications).
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the circular file. It must be open.
If the circular file is not open, perform an Open circular file command.
If the circular file is open, check the state of the BSC/OMC--R link:
If the link is unlocked, ensure that the influx of messages is not the result
of a problem concerning the BSS.
If the problem does not concern the BSS, clear the circular file.
If the problem concerns the BSS, go to step 2.
Vol. 1 -- 2--88
BSC fault numbers
Step
Action (Continued)
Check which type of circular file is mentioned in the notification (hardware fault
notifications, software anomalies, observation messages, event reports, etc.) to
identify which equipment of the BSS has a problem.
If a BTS is involved, perform the isolating procedure (lock the objects

concerned), and then treat the problem. Then go to step 3.
If a TCU is involved, perform the isolating procedure (lock the transcoder and
the transcoderBoard objects), and then treat the problem. Then go to step 3.
If the BSC is involved, call the manufacturer.
If the OMC--R is involved, delete the observation messages.
Additional checks
Step
3
PE/DCL/DD/0101
411--9001--101
Action
When the file is no longer saturated, a notification with fault number 22 (End of
circular file pre--overflow) appears in the notification window.
Standard 15.101/EN
July 2005
2.14
BSC fault numbers
Vol. 1 -- 2--89
Fault number: 22
iii
Fault number:
22
: End of circular file pre--overflow
FAULT ANALYSIS
This notification indicates the end of the overflow of the circular file specified in the fault
number 21.

BSC defense
None.

None.
FAULT TREATMENT
If this notification is not received quickly after the fault number 21 has been treated, check
the state of the network by performing a Display all command. As a matter of fact, the
transcoder, transcoderBoard, pcmCircuit (A, Abis, and Ater), lapdLink and signallingLink
objects may have undergone a state change.
Vol. 1 -- 2--90
BSC fault numbers
2.15
Fault number: 23
iii
Fault number:
23
: Beginning of BSC disk partition update
FAULT ANALYSIS
The chain that sends this notification is updating the partition on the other chain.
A partition is updated when a difference exists between a partition on the active chain and
the same partition on the passive chain.
The following partitions can be updated:
BDA
APE
EVT
BTS
COD 1 or COD 2
PRO 1 or PRO 2
MRQ
OBM
GPO
INSTAL
TCB
CALLTR
CALLPATH
LPB

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.16
BSC fault numbers
Vol. 1 -- 2--91
Fault number: 24
ooo
Fault number:
24
: End of BSC disk partition update
FAULT ANALYSIS
This notification indicates the end of the partition update.
The circular files are identical to those of fault number 23.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--92
BSC fault numbers
2.17
Fault number: 26
oo
Fault number:
26
: Fault on BSC/OMC--R link
FAULT LOCATION
This notification indicates that the level 2 was not established or was lost on the link with
the BSC.
Either the link itself or the OMC--R broke down. After the link between the OMC--R and the
BSC has been restored, the BSC sends this notification.
It indicates the date and time of the breakdown, and it can be used for investigation
purposes.

None.
BSC defense
None.
FAULT TREATMENT
None.
Just perform a Display all command to check the state of the bscMDInterface and the bsc
object itself. If they are enabled, clear the fault alarm.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.18
BSC fault numbers
Vol. 1 -- 2--93
Fault number: 33
ppp
Fault number:
33
: Saturation on an internal file used for marking climb
FAULT ANALYSIS
This notification indicates that an internal file is saturated.
The file name is a 14--character ASCII string that ends with the end--of--string character /O.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--94
BSC fault numbers
2.19
Fault number: 34
iii
Fault number:
34
: Saturation on a storage zone for marking climb
FAULT ANALYSIS
This notification indicates that a storage zone is saturated.
The zone name is a 14--character ASCII string that ends with the end--of--string
character /O.

BSC defense
None.

None.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.20
BSC fault numbers
Vol. 1 -- 2--95
Fault number: 41
ooo
Fault number:
41
: Beginning of saturation of the event reporting process in the
BSC
FAULT ANALYSIS
This notification indicates that the queue corresponding to the priority level of the event is
nearly full: the saturation is over 80%.
The queues act as buffers before the data are written on the BSC disk and the notifications
are sent to the OMC--R. They are described in Table 2--2 (APE queues) and Table 2--3
(GES_SL queues).
The number of the queue concerned is indicated in the notification.
Size
Saturation
mode:
overwriting
allowed
Saturation
threshold
msg type
255 b
yes
100%
build
60 Kb
yes
80%
chgt_etat
rep_diff
acq_tge
300 Kb
yes
80%
ctx_dem
msg_purge
180 Kb
yes
80%
an_lg_maj
an_lg_min
1 Kb
yes
80%
11
300 Kb
yes
80%
12
1200 Kb
yes
80%
chgt_etat
13
1300 Kb
yes
80%
alar_maj
alar_min
cr_test
sig_op
value_chg
sig_op_prio
ind_rgl_flux
16
100 Kb
NO
100%
grp_chgt_etat
Partition
Nb of
files
Files
id
0 (init)
mb_ape
1 (transat)
mb_ape
2 (report)
mb_evt
Queue
Priority
level
Vol. 1 -- 2--96
Queue
BSC fault numbers
Size
Saturation
mode:
overwriting
allowed
Saturation
threshold
msg type
1000 Kb
yes
80%
observations
64 Kb
yes
100%
obs_warning
obs permanente
100 Kb
yes
80%
call path
16000 Kb
yes
80%
call trace
Partition
Nb of
files
Files
id
mb_obm
3 (obs)
temporary
real time
Priority
level
4 (path, trace)
trace warning
warning priority
mb_evt
5 (sign, mark)
marking
mb_evt
10
100 Kb
yes
80%
signaling
6 (update)
mb_ape
14
255 b
yes
100%
build
15
20 Ko
yes
80%
chgt_etat
acq_tge
6 (update)
Table 2--2
APE queues
Queue
Content
Size
(in Kb)
Priority
level
WARNING
20
queue used
during BSC
start--up only
MSG_PURGE
50
0 (BSC
events)
INC_RES and CR_AUTOTEST

fault numbers for classes:
CAR_SIC_X25
DEM_SICD
DEM_SIC_CS7
DEM_CPUE
CAR_DMUX
CAR_UTE
CR_AUTOTEST fault number for
CAR_BRA
codano_min = ANO_DMUX_00
codano_max = ANO_DMUX_23
codano_MIN =
ANO_LBD_IOD_M
codano_max =
ANO_LDB_TRS_R2000G
64
1 (sites and
TCUs state
changes)
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Saturation
threshold
Acknowledgement
90%
No
Queue
Content
BSC fault numbers
Size
(in Kb)
Priority
level
CHGT_ETAT
VALUE_CHG
codano DESINIT and
CHGT_ETAT for classes:
SUP_SIT
SUP_TCU
SUP_PCM
SUP_PCMA
64
2 (other state
changes)
ALAR_MAJ
ALAR_MIN
CR_TEST
CTX_DEM
SIG_OP
SIG_OP_PRIO
codano DESINIT and
CHGT_ETAT for other classes
than:
SUP_SIT
SUP_TCU
SUP_PCM
SUP_PCMA
40
3 (alarms and
warnings)
REP_DIFF
AMP
AN_LG_MAJ
AN_LG_MIN
codano INC_RES and
CR_AUTOTEST for classes:
SUP_TCB
SUP_TCU
codano_min = ANO_ALA_00
codano_max = ANAO_ALA_47
codano_min =
VAL_SPT_ANO_ALA_70
codano_max =
VAL_SPT_ANO_ALA_74
10
4 (major and
minor software
anomalies)
SIG_MRQ
MARQUAGE
30
--
IND_RGL_FLUX
10
--
GRP_CHGT_ETAT
20
--
Table 2--3
Vol. 1 -- 2--97
Saturation
threshold
Acknowledgement
99%
Yes
GES_SL queues
Vol. 1 -- 2--98
BSC fault numbers
BSC defense
None.

None. Nevertheless, all the following notifications (if any) may be lost.
FAULT TREATMENT
Preliminary checks
Step
Action
Check which type of queue is mentioned in the notification (hardware fault
notifications, event reports, etc.):
If the queue concerns event reports, identify which equipment of the BSS has
a problem.
If a BTS is involved, perform the isolating procedure (lock the objects

concerned), and then treat the problem. Then go to step 2.
If a TCU is involved, perform the isolating procedure (lock the transcoder and
the transcoderBoard objects), and then treat the problem. Then go to step 2.
If the BSC is involved, call the manufacturer.

If the queue concerns state change notifications, check the state of the network
by performing a Display all command. As a matter of fact, the transcoder,
transcoderBoard, pcmCircuit (A, Abis, and Ater), lapdLink and signallingLink
objects may have undergone a state change.
Additional checks
Step
2
PE/DCL/DD/0101
411--9001--101
Action
When the queue is no longer saturated, a notification with fault number 42 (End
of saturation of the event reporting process) appears in the notification window.
Standard 15.101/EN
July 2005
2.21
BSC fault numbers
Vol. 1 -- 2--99
Fault number: 42
iii
Fault number:
42
: End of saturation of the event reporting process
FAULT ANALYSIS
This notification indicates that the queue is no longer saturated. The notification of
beginning of saturation (with fault number 41) previously signaled the saturation. All the
following notifications (if any) will be displayed at the OMC--R.

BSC defense
None.

None.
FAULT TREATMENT
Vol. 1 -- 2--100 BSC fault numbers
2.22
Fault number: 43
ooo
Fault number:
43
: Loss of access to the equipment shelf
The following Table 2--4 indicates the sources of the fault number 43. For more
information on each source and the associated corrective maintenance procedure,
refer to the sheet indicated in the right column.
Source
No.
Source wording
BSC
12000
HC
Procedure
Cannot access to all working UTE
2.22.1
O&M bus selftest not OK
2.22.2
Table 2--4
PE/DCL/DD/0101
411--9001--101
BSC
12000
Fault number 43 sources
Standard 15.101/EN
July 2005
2.22.1
BSC fault numbers Vol. 1 -- 2--101
Source: Cannot access to all working UTE

ooo
Loss of access to the equipment shelf
Fault number 43
Source:
BSC model:
(0) Cannot access to all working UTE

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification appears on the active chain if all the working UTE (slave processing units:
ALA, DDTI, BSCB, and TSCB boards) are inaccessible.

BSC defense
The active chain commits suicide and a chain switchover is performed. Besides, the
associated objects (pcmCircuit, etc.) are unconfigured.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check that all the boards are inaccessible by performing a Display all command
on the bsc object.
If they are inaccessible, go to step 2.
If not, clear the alarm.
Check that the ECI board is operational:

Look for a notification with fault number 7 Card monitoring failure concerning
the ECI board. It has been sent to the OMC--R either before or after fault
number 43.
Check the state of the ECI board by performing a Display all command on the
bsc object.
If the ECI board is operational, one of the DDTI, BSCB or TSCB boards is
faulty. Go to step 4.
If the ECI board is not operational, the DDTI, BSCB or TSCB boards cannot
be accessed anymore. Go to step 3.
Step
Action
Replace the ECI board (Field Replaceable Unit) (See NTP < 41 >).
Check that the DDTI, BSCB or TSCB boards are operational by performing a
Display all command on the bsc object.
If one of these boards is faulty, go to step 5.
If all the boards are operational, go to step 6.
Replace the faulty board (Field Replaceable Unit) by following the procedure in
NTP < 41 >:
BSCB board
TSCB board
DDTI board
Call the manufacturer.
Additional checks
Step
7
PE/DCL/DD/0101
411--9001--101
Action
End. The procedure is complete.
Standard 15.101/EN
July 2005
2.22.2
Source: O&M bus selftest not OK

o
Loss of access to the equipment shelf
Fault number 43
Source:
BSC model:
(1) O&M bus selftest not OK

BSC12000 + BSC12000 HC
FAULT ANALYSIS
This notification appears on the passive chain if all the access tests to the DDTI, BSCB,
and TSCB boards failed.
The O&M bus selftest is performed by the ECI board on the passive chain each time the
passive chain starts up, and also every 30 minutes.

BSC defense
When the selftest fails, the passive chain commits suicide, starts again, and also sends a
notification with fault number 5 Restart after chain suicide due to internal source, or OMC
and source 102 No communication with ECI card or fault on ECI card.

None.
FAULT TREATMENT
Step
1
Action
Check the state of the ECI board.
If the ECI board is operational, one of the DDTI, BSCB or TSCB boards is faulty.
Go to step 3.
If the ECI board is not operational, the DDTI, BSCB or TSCB boards cannot be
accessed anymore. Go to step 2.
Replace the ECI board (Field Replaceable Unit) (See NTP < 41 >).
Check that the DDTI, BSCB or TSCB boards are operational by performing a
Display all command on the bsc object.
If one of these boards is faulty, go to step 4.
If all the boards are operational, go to step 5.
Step
Action (Continued)
Replace the faulty board (Field Replaceable Unit), by following the correct
procedure in NTP < 41 >:
BSCB board
TSCB board
DDTI board
Additional checks
Step
6
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.23
Fault number: 44
p
Fault number:
44
: Board UTE access problem
FAULT ANALYSIS
This notification appears on the passive chain when the access test to one of the UTEs
(Slave Processing Units: DDTI, BSCB or TSCB boards) failed.
The O&M bus selftest is performed by the ECI board on the passive chain each time the
passive chain starts up, and also every 30 minutes.
The problem lies:
either with the link between the ECI board and the UTE boards
or with one of the UTE boards

BSC defense
None.

None.
However, after a switchover the board in question will be unavailable on the new active
chain.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Analyze the circumstances in which this notification with fault number 44 appeared.
If a UTE board was removed during a maintenance operation, go to step 2.
If there is a real fault on one of the UTE boards, go to step 3.
Step
Action (Continued)
Perform the following actions:
a. Do not clear the alarm.

b. After the UTE board has been reinserted:
wait for at least 30 minutes to see if the problem disappears or not
or, to avoid waiting, kill the chain from the OMC--R and check that the
problem does not appear during the chain restart.
If the problem disappeared, go to step 5.

If the problem persists, either the ECI board or the link between the ECI
board and the UTE boards is faulty. Go to step 4.
Step
Action
Replace the faulty board (Field Replaceable Unit) during a maintenance window;
follow the correct procedure in NTP < 41 >.
a. The board in question is one of the following:

DDTI boards
TSCB boards
BSCB boards
Replace the ECI board (Field Replaceable Unit):
a. Refer to the replacement procedure (See NTP < 41 >).

Additional checks
Step
5
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.24

iii
Fault number:
45
: Partial hard disk degradation
FAULT ANALYSIS
This notification indicates that the BSC disk of the chain considered is partially degraded.
The errors on disk access (reading and writing) are counted.
Beyond a first threshold, the disk performances are no more nominal: the chain is degraded.

BSC defense
When the threshold is exceeded on the passive chain, the passive chain commits suicide,
restarts, stops in the 0B phase of the start--up, and sends this notification.
When the threshold is exceeded on the active chain -- in simplex mode --, the chain commits
suicide, restarts, stops in the 0B phase of the start--up or sometimes further, and sends
this notification.

None, except on the active chain in simplex mode. The BSC is still operational.
Nevertheless, replacing the partially degraded disk must be considered and planned.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check which chain is impacted:
If the active chain is impacted, check the state of the passive chain.
If the passive chain is operational:

Perform a chain switchover from the OMC--R by performing a Kill active
chain command.
Then replace the MMU board on the new passive chain. Go to step 2.
Step
Action (Continued)
If the passive chain is not operational:

First fix the passive chain.
Then perform a chain switchover from the OMC--R by performing a Kill
active chain command.
Lastly, replace the MMU board on the new passive chain. Go to step 2.
If the two chains are impacted:

Lastly, replace the MMU board on the new passive chain. Go to step 2.
Step
Action
Replace the MMU board (Field Replaceable Unit):
a. For more information, refer to the replacement procedure (see NTP < 41 >).
Bring the new MMU board into service:
a. Install the BSC software on the new disk (see NTP < 41 >).
b. The automatic customization takes place (see NTP < 41 >).
c. If necessary, apply BSC patches (see NTP < 41 >).
Additional checks
Step
4
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.25

iii
Fault number:
45
: Partial hard disk degradation
FAULT ANALYSIS
Beyond a first threshold, the disk performances are no more nominal: the chain is degraded.

BSC defense
When the threshold is exceeded on the passive chain, the passive chain commits suicide,
restarts, stops in the 0B phase of the start--up, and sends this notification.
When the threshold is exceeded on the active chain -- in simplex mode --, the chain commits
suicide, restarts, stops in the 0B phase of the start--up or sometimes further, and sends
this notification.

None, except on the active chain in simplex mode. The BSC is still operational.
Nevertheless, replacing the partially degraded disk must be considered and planned.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check which chain is impacted:
If the active chain is impacted, check the state of the passive chain.
If the passive chain is operational:

Perform a chain switchover from the OMC--R by performing a Kill active
chain command.
Then replace the MMU_IDE board on the new passive chain. Go to
step 2.
Step
Action (Continued)
If the passive chain is not operational:

Lastly, replace the MMU_IDE board on the new passive chain. Go to
step 2.
If the two chains are impacted:

Lastly, replace the MMU_IDE board on the new passive chain. Go to step 2.
Step
Action
Replace the MMU_IDE board (Field Replaceable Unit):
Bring the new MMU_IDE board into service:
Additional checks
Step
4
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.26
BSC fault numbers
Vol. 1 -- 2--111

iii
Fault number:
46
: Total hard disk degradation
FAULT ANALYSIS
Beyond a first threshold, the disk performances are no more nominal: the chain is degraded
and an alarm with fault number 45 is emitted.
Beyond a second threshold, the utilization of the disk is prejudicial to the network.

BSC defense
When the second threshold is exceeded on the passive chain, the passive chain commits
suicide, restarts, stops in the 0B phase of the start--up, and sends this notification.
When the second threshold is exceeded on the active chain, the chain commits suicide,
does not restart, and sends this notification.
When the second threshold is exceeded on a single chain in simplex mode, the chain does
not commit suicide, and just sends this notification.

None.
CAUTION
The BSC is in simplex mode.
FAULT TREATMENT
Step
Action
Replace the MMU board (Field Replaceable Unit) immediately:
Then bring the new MMU board into service:
Additional checks
Step
3
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.27
BSC fault numbers
Vol. 1 -- 2--113

iii
Fault number:
46
: Total hard disk degradation
FAULT ANALYSIS
Beyond a first threshold, the disk performances are no more nominal: the chain is degraded
and an alarm with fault number 45 is emitted.
Beyond a second threshold, the utilization of the disk is prejudicial to the network.

BSC defense
When the second threshold is exceeded on the passive chain, the passive chain commits
suicide, restarts, stops in the 0B phase of the start--up, and sends this notification.
When the second threshold is exceeded on the active chain, the chain commits suicide,
does not restart, and sends this notification.
When the second threshold is exceeded on a single chain in simplex mode, the chain does
not commit suicide, and just sends this notification.

None.
CAUTION
The BSC is in simplex mode.
FAULT TREATMENT
Step
Action
Replace the MMU_IDE board (Field Replaceable Unit) immediately:
Then bring the new MMU_IDE board into service:
Additional checks
Step
3
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.28
BSC fault numbers
Vol. 1 -- 2--115
Fault number: 47
iii
Fault number:
47
: Cessation of active alarms
Type : communicationsAlarm, environmentalAlarm,
equipmentAlarm,
processingErrorAlarm, qualityOfServiceAlarm
FAULT ANALYSIS
The notification is sent during a BSC restart or a chain switchover. It indicates that old active
alarms (mentioning hardware faults) may be cleared by the OMC--R.
If the anomaly that triggered these alarms is still present after the BSC restart or the chain
switchover, new alarms will be sent to the OMC--R. Thus, no information is lost.
The notification concerns one alarm type (see the list given above in the title box).
The notification concerns one of the following objects: chain or bsc
The type of alarm clearing is displayed in the probableCause field of the notification.
probable
Cause No.
probableCause
wording
64
bscRequest
65
purgeOnSaturation
66
dailyPurge
Type of alarm clearing

-- notification sent by the BSC
-- purge performed by the BSC: consists in
sending a list of alarms which may be cleared
by the OMC--R if they are still active
-- notification sent by the MD
-- the defense purge consists in clearing the
oldest alarms. The threshold is fixed by the
static configuration.
-- notification sent by the MD
-- the daily purge consists in clearing the alarms
that are older than N days, every day. N is
fixed by the static configuration.

BSC defense
None.

None.
FAULT TREATMENT
2.29
Fault number: 332

ii
Fault number:
332 : External alarm loop 0
Type : environmentalAlarm
FAULT ANALYSIS
This notification indicates the state change of the external alarm.
This is an external alarm that can be programmed by the operator. The loop number is
indicated in the wording of the alarm.
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the value of the bscAlarmMask parameter, by performing a Display all
command on the bsc object.
If the external alarm is configured (1 is displayed), go to step 2, or set it to 0
if the external alarm loop is not used. Configure it by performing a Set
If the external alarm is not configured, 0 must be displayed. If not, configure
the alarm by performing a Set command on the bsc object. Then go to step 3.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--117
Step
2
Action
Perform the appropriate treatment. The operations for clearing this type of alarm
depend on how the alarm was programmed and thus they are determined by the
operator.
Additional checks
Step
Action
Check that an end--of--fault message is generated when the alarm has been
cleared.
2.30
Fault number: 333

ii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
BSC fault numbers
Vol. 1 -- 2--119
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.31
Fault number: 334

ii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.32
Fault number: 335

iii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.33
Fault number: 336

oo
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.34
Fault number: 337

iii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.35
Fault number: 338

iii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.36
Fault number: 339

iii
Fault number:
FAULT ANALYSIS
BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
operator.
Additional checks
Step
Action
cleared.
2.37
Fault number: 400

iii
Fault number:
400 : Breakdown of one power supply of the EQPD1 shelf
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: a
PSUE power supply located in the EQPD1 shelf.

BSC defense
None.

The system continues to operate normally if only one PSUE power supply failed.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Analyze the circumstances of the problem:
If the BSC is in duplex mode,check how many notifications with fault number 400
have been received at the OMC--R.
If there are two notifications (one for each chain, emitted by each ECI board),
the problem lies with the PSUE power supply. Go to step 6.
If there is only one notification, the problem lies with either the ECI board or
the cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or the
PSUE power supply or the cables. Go to step 2.
2
Perform a Display chain information command on the bsc object to check the ECI
board state.
If the internal DMUX state is faulty, look for a notification concerning the ECI
If the internal DMUX state is working, go to step 3.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)
Perform a Display chain information command on the bsc object to check the
PSUE power supply state.
If the EQPD1 converter state is at least one failed, go to step 4.
If the EQPD1 converter state is all working, go to step 7.
Step
4
Action
Confirm the failed PSUE power supply by using a voltmeter to measure the output
voltage on the front panel V test points (see NTP < 41 >).
The voltage must be 5.2 V (2%).
If the voltage is incorrect, the PSUE power supply must be replaced. Go to
step 6.
Perform the corrective maintenance associated with the notification concerning the
ECI board. Then go to step 8.
Replace the faulty PSUE power supply (Field Replaceable Unit) in the BSC
equipment cabinet:
Check the cables connected to the PSUE power supply.

If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 8.
Additional checks
Step
Action
Perform a Display chain information command to check that the equipment has
returned to correct operation.
Clear the alarm if necessary.
10
2.38
Fault number: 401

iii
Fault number:
401 : Breakdown of one power supply of the EQPD0 shelf
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: a
PSUE power supply located in the EQPD0 shelf.

BSC defense
None.

The system continues to operate normally if only one PSUE power supply failed.
FAULT TREATMENT
Preliminary checks
Step
1
Action
2
board state.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)
If the EQPD0 converter state is at least one failed, go to step 4.
If the EQPD0 converter state is all working, go to step 7.
Step
4
Action
Confirm the failed power supply by using a voltmeter to measure the output voltage
on the front panel V test points (see NTP < 41 >).
The voltage must be 5.2 V (2%).
If the voltage is incorrect, the PSUE power supply must be replaced. Go to
step 6.
Replace the faulty PSUE power supply (Field Replaceable Unit) in the BSC
equipment cabinet:

Additional checks
Step
Action
Clear the alarm if necessary.
10
2.39
Fault number: 402

iii
Fault number:
402 : Fan fault on the MPU shelf
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:
a MPU ventilation block located in the control cabinet.
The chain concerned (active or passive) is the chain that emitted this notification.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
If the chain concerned has not been powered off, there is a problem with the
detection of the faults concerning the ventilation blocks. The faulty item of
equipment can be one of the following:
Go to step 2.
the ECI board. Go to step 3.

the cables connected to the ventilation blocks and the ECI board. Go to
step 4.
If the chain concerned has been powered off, check that the ventilation blocks
are running: perform a Display chain information command to check their
state.
If their state is one faulty, replace the ventilation block. Go to step 8.

If their state is all working, go to step 5.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
MPU backpanel. For more information, refer to the BSC Reference NTP. Then
go to step 9.
board state.
If the internal DMUX state is faulty, replace the ECI board (Field
Replaceable Unit). Refer to the replacement procedure (see NTP < 41 >).
Then go to step 9.
Check the cables connected to the ventilation blocks and to the ECI board.
If they are operational, call the manufacturer.
Check the power fuse of the ventilation block, on the VENT board (see
NTP < 41 >).
Si the fuse is operational, replace the VENT board. Go to step 7.
Si the fuse is not operational, replace it. Go to step 6.
Replace the power fuse of the ventilation block, on the VENT board (Field
Replaceable Unit):
Replace the VENT board.

If the problem is over, go to step 9.
If the fault persists, replace the ventilation block. Go to step 8.
Replace the ventilation block (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
10
11
Standard 15.101/EN
July 2005
2.40
Fault number: 403

iii
Fault number:
403 : Fan fault on the MPU shelfs power supply
FAULT ANALYSIS
a PSUC ventilation block located in the control cabinet.
The chain concerned (active or passive) is the chain that emitted this notification.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Go to step 2.
the ECI board. Go to step 3.

step 4.
state.

Step
2
Action
MPU backpanel. For more information, refer to the BSC Reference NTP . Then
go to step 9.
board state.
Then go to step 9.
Check the power fuse of the ventilation block, on the EXTR board (see
NTP < 41 >).
If the fuse is operational, replace the EXTR board. Go to step 7.
If the fuse is not operational, replace it. Go to step 6.
Replace the power fuse of the ventilation block (Field Replaceable Unit):
Replace the EXTR board.


PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Additional checks
Step
Action
10
11
2.41
Fault number: 404

iii
Fault number:
404 : RCB0 failure
FAULT ANALYSIS
the RCB 0 board.

BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the other
chain.

None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step
1
Action
board state.
Perform a Display chain information command to check the state of the RCB0
board.
If the board state is absent, replace the RCB 0 board. Go to step 4.
If the board state is present, clear the alarm. Go to step 6.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action
Treat the notification concerning the ECI board. Then go to step 6.
Replace the RCB0 board (Field Replaceable Unit):

Additional steps
Step
5
Action
b. On--site, check that 12 is displayed in the SUP or SUP2 board display panels
after the BSC start--up.
If necessary, clear the alarm concerning the RCB0 board.
2.42
Fault number: 405

iii
Fault number:
405 : RCB1 failure
FAULT ANALYSIS
the RCB 1 board.

BSC defense
chain.

FAULT TREATMENT
Preliminary checks
Step
1
Action
board state.
Perform a Display chain information command to check the state of the RCB 1
board.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action
Replace the RCB 1 board (Field Replaceable Unit):

Additional steps
Step
5
Action
If necessary, clear the alarm concerning the RCB 1 board.
2.43
Fault number: 406

iii
Fault number:
406 : RCB2 failure
FAULT ANALYSIS
the RCB 2 board.

BSC defense
chain.

FAULT TREATMENT
Preliminary checks
Step
1
Action
board state.
board.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action

Additional steps
Step
5
Action
2.44
Fault number: 407

iii
Fault number:
407 : RCB3 failure
FAULT ANALYSIS
the RCB 3 board.

BSC defense
chain.

FAULT TREATMENT
Preliminary checks
Step
1
Action
board state.
board.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action

Additional steps
Step
5
Action
2.45
Fault number: 408

iii
Fault number:
408 : Power supply fault to the fans of the MPU shelf
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: the
power supply of the MPU ventilations blocks.

BSC defense
The ECI board switches off the two power supplies of the concerned chain.

FAULT TREATMENT
Preliminary checks
Step
1
Action
Go to step 2.
the ECI board is faulty. Go to step 3.

step 4.
state.

PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
MPU backpanel. For more information, refer to the BSC Maintenance NTP .
Then go to step 9.
board state.
Then go to step 9.
Check the general power supply fuse of the terminal block (VENT MPUA, or VENT
MPUB, see NTP < 41 >).
If the fuse is operational, go to step 6.
If not, replace it. Then go to step 9.
Check the power fuses of the fans (see NTP < 41 >). They are located on the
VENT board.
If the fuses are operational, replace the VENT board. Go to step 7.
If not, replace them. Then go to step 9.
Replace the VENT board.


Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Perform a Display chain information command on the bsc object to check that the
equipment has returned to correct operation.
10
11
Standard 15.101/EN
July 2005
2.46
Fault number: 411

iii
Fault number:
411 : Power supply fault of the other chains MPU shelf
FAULT ANALYSIS
This notification is emitted by the active chain only and it indicates that there is a problem
with the power supply units (PSUC) of the passive chain.
Location fields identify the object that detected the fault.

BSC defense
The passive chain is not supplied anymore. The BSC is in simplex mode.
However, if the ECI board misfunctioned and could not detect the fault on the ventilations
blocks, the chain has not been powered off and is still running.

FAULT TREATMENT
Preliminary checks
Step
1
Action
Perform a Display chain information command on the chain that detected the fault
to check the ECI board state.
board.
Step
2
Action
Check the general power supply fuse of the terminal block (see NTP < 41 >).
If not, replace it.
Step
Action (Continued)
Replace the power supply (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.47
Fault number: 412

iii
Fault number:
412 : RCB4 failure
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the faulty element: the
RCB 4 board.

BSC defense
chain.

FAULT TREATMENT
Preliminary checks
Step
1
Action
Perform a Display chain information command to check the ECI board state.
board.
Step
Action

Additional steps
Step
5
Action
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.48
Fault number: 413

iii
Fault number:
413 : Fault on the right MPU power supply
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: the
right power supply unit (PSUC) in the control cabinet.

BSC defense
The passive chain commits suicide and restarts cyclically because CPUE boards are no
longer supplied.

None.
However, some boards of the chain no longer receive power supply (SICD boards and
CPUE boards).
FAULT TREATMENT
Preliminary checks
Step
1
Action
If the chain concerned is operational, there is a problem with the detection of the
faults concerning the power supply. The faulty item of equipment can be one of
the following:
Go to step 2.
the ECI board of the chain that emitted this notification. Go to step 3.
If the chain concerned restarts cyclically, check that alarms concerning the
CPUE boards are emitted. Then go to step 2.
Step
Action
MPU backpanel. For more information, refer to the BSC Maintenance NTP .
Then go to step 9.
board state.
Then go to step 9.
Identify the faulty power supply unit (PSUC) using a voltmeter to measure the
output voltage at the front panel V test points (see NTP < 41 >).
If the voltage is correct, call the manufacturer.

If the voltage is incorrect, go to step 5.
Replace the power supply unit (PSUC) (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Check that an end--of--fault message is issued when the alarm is cleared.
Standard 15.101/EN
July 2005
2.49
Fault number: 414

iii
Fault number:
414 : Fan fault on EQPT and SWG shelf
FAULT ANALYSIS
The alarm identifies the object that has detected the fault and the suspected element: one
of the ventilation blocks of the equipment cabinet in the EQPT or SWG shelf.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check that:
the problem lies with the power supply. Go to step 3.
power supply or the cables. Go to step 2.
2
board state.
board. Then go to step 4.
Step
Action
Check the power fuse of the fan on the VENT board.

If the fuse is not operational, go to step 6.
4

Replace the fuse (Field Replaceable Unit):

Check the cables connected to the PSUE power supply and the ventilation blocks.

If not, fix them. Then go to step 8.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.50
Fault number: 415

iii
Fault number:
415 : Power supply fault on SWG or SWT shelf
FAULT ANALYSIS
the power supply unit (PSUE) in the SWG shelf in the equipment cabinet.

BSC defense
None.

None. The system continues to operate normally if only one PSUE failed.
FAULT TREATMENT
Preliminary checks
Step
1
Action
2
If the swd converter state is at least one failed, go to step 4.
If the swd converter state is all working, go to step 9.
Step
Action
Identify the faulty power supply unit (PSUE) using a voltmeter to measure the output
voltage at the front panel V test points (see NTP < 41 >).
The measured voltage must be between 5.2 V (2%).

If the voltage is correct, go to step 7.
5
Replace the power supply unit (PSUE) (Field Replaceable Unit):

Check the PSUE fuse.
If the fuse is operational, check the cables. Go to step 9.

If not, replace it. Go to step 8.
Replace the PSUE fuse (Field Replaceable Unit):


Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
10
11
12
Standard 15.101/EN
July 2005
2.51
Fault number: 417

iii
Fault number:
417 : Power supply fault on EQPT shelf
FAULT ANALYSIS
a power supply unit (PSUE) in the EQPT shelf, in the equipment cabinet.

BSC defense
None.

FAULT TREATMENT
Preliminary checks
Step
1
Action
2
If the eqpt converter state is at least one failed, go to step 4.
If the eqpt converter state is all working, go to step 9.
Step
Action

5




Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
10
11
12
Standard 15.101/EN
July 2005
2.52
Fault number: 419

iii
Fault number:
419 : Power supply fault on EQPI shelf
Type : Equipment alarm
FAULT ANALYSIS
the power supply unit (PSUE) in the EQPI shelf, in the equipment cabinet.

BSC defense
None.

FAULT TREATMENT
Preliminary checks
Step
1
Action
2
If the eqpi converter state is at least one failed, go to step 4.
If the eqpi converter state is all working, go to step 9.
Step
Action

5




Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
10
11
12
Standard 15.101/EN
July 2005
2.53
Fault number: 420

iii
Fault number:
420 : Fan fault on the EQPI, EQPD0 and EQPD1 shelves
FAULT ANALYSIS
a ventilation block in the equipment cabinet.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
2
Step
Action
Check the power fuse of the suspected ventilation block.
If the fuse is operational, replace the ventilation block. Go to step 5.

If not, replace the fuse. Go to step 6.
4

b. Then to go step 8.
Replace the fuse (Field Replaceable Unit):

b. Then to go step 8.

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.54
Fault number: 422

iii
Fault number:
422 : Power supply fault to the fans of the equipment cabinet
FAULT ANALYSIS
the power supply of the ventilation blocks in the equipment cabinet.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
If the BSC is in duplex mode, check how many notifications with fault number
420 have been received at the OMC--R.
2
Step
Action
Check the general power supply fuse of the terminal block (VENT.)

4
Check the power fuses of the fans.

If the power fuses are operational, replace the ventilation block. Go to step 8.
If not, replace the power fuses of the fans. Go to step 7.
Replace the fuse of the terminal block (VENT.):
a. Locate the fuse on the following figure (see NTP < 41 >). Replace it.
Replace the power fuses of the fans (Field Replaceable Unit):



If not, fix them. Then go to step 10.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
10
11
Clear the alarm.
12
Standard 15.101/EN
July 2005
2.55
Fault number: 494

iii
Fault number:
494 : Fault on ECI alarm loop
FAULT ANALYSIS
The location of the faulty board (ECI) is given in the notification.

BSC defense
All functions of the alarm loops on the ECI board are inhibited.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
If the internal DMUX state is faulty, go to step 2.
If the internal DMUX state is working, clear the alarm. Go to step 3.
Step
Action
Replace the ECI board (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Clear the alarm if it is still active.
Standard 15.101/EN
July 2005
2.56
Fault number: 497

iii
Fault number:
497 : New PCM selected as clock reference
FAULT ANALYSIS
By this notification, each chain indicates the new reference clock selected by the ECI board.
The previous clock and the new reference clock are specified in the PREVIOUS PCM and
NEW PCM fields of the notification.
The fields can take the following values:
field value
4
meaning
internal clock
explanation on
the NEW PCM field
No synchronizing PCM is available, so the
reference clock is derived from a local oscillator.
The problem may implicate the link between the
TCUs and the BSC, or the DDTI boards, or the
internal PCM links, or the TCUs.
clock from PCM 6
clock from PCM 4
clock from PCM 2
clock from PCM 0
Th BSC found
The
f
d a new reference
f
clock
l k issued
i
d
by a PCM.
The previous synchronizing PCM was faulty.
The reference clock is taken from one of the four even PCMs on the first four DDTI boards
(PCM 0, 2, 4, and 6) or the internal clock. The PCM 0, 2, 4 and 6 linked to the BSC are
reserved to the Ater interface. They cannot be used for the Abis interface.
The priority is given to the external clock coming from the TCU, then to the internal clock
coming from the TCU, then to the PCM links in service, and lastly to the internal clock.
This notification does not always require maintenance action. It only indicates the new
reference clock.

BSC defense
If the TCU now uses its local clock as a reference clock, the BSC cannot use this clock
anymore. So the BSC has to select another TCU whose reference clock is issued by a PCM
of the A interface. Then the BSC sends a fault number 497 to indicate its new reference
clock.

None.
FAULT TREATMENT
Preliminary checks
Step
Action
Check the state of the previous PCM link (not the new one), by performing a
Display all command on the pcmCircuit object (pcmAter).
If the administrativeState of the pcmCircuit object is locked, do not take the

alarm into account. Go to step 7.
If the operationalState of the pcmCircuit object is enabled, the fault is not
confirmed. Go to step 7. Nevertheless, if the interruption lasted less than five
seconds, the operationalState remained enabled even though there has been
a problem. This problem is associated with a PCM fault. Refer to NTP < 105 >.
availabilityStatus is dependency, look for a problem on the internal PCM link.
Look for a notification with fault number 523 Fault on internal PCM (BSC,
TCU).
availabilityStatus is failed, go to step 2.

Step
2
Action
Look for alarms or notifications concerning the following equipment:
pcmCircuit links (Ater)
DDTI boards
internal PCMs
TCUs
If there are alarms, treat them. Go to step 3.

If there are not any alarms, call the manufacturer.
3
Replace the equipment item(s) according to the other notifications:

a. Set the disabled--failed pcmCircuit object (external PCM or DDTI problem) or
disabled--dependency pcmCircuit object (internal PCM problem) to locked.
b. Replace the item(s) of equipment. For more information on the replacement of
the DDTI boards (Field Replaceable Unit), refer to the replacement procedure
in NTP < 41 >.
c. Set the pcmCircuit to unlocked.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Additional checks
Step
4
Action
Check the alarm state in the Current alarm list window.
If the alarm has disappeared, go to step 7.
If the alarm persists, go to step 5.
Check the state of the replaced equipment, by performing a Display all command
on the object concerned.
If the operationalState of the object is enabled, the fault is not confirmed. Go
to step 6.
If the operationalState of the object is disabled, and the availabilityStatus is
failed, call the manufacturer.
Clear the alarm.
2.57

iii
Fault number:
: Fault on switching matrix access
FAULT ANALYSIS
This notification indicates that there is a transmission problem between the CPU66SE
board (CPU--OMU) and the SWC board. The fault was detected by the CPU66SE board,
which supervises the SWC board through the SUP board (synchronous link).
The faulty element is the SWC board, or the SUP board, or the link between the boards.
The chain concerned (either the active or the passive one) is mentioned in the notification.

BSC defense
If the problem seldom happens, there is not any BSC defense.
If the problem often happens, the chain concerned commits suicide.
chain.
Then the chain concerned sends a notification with fault number 522 Switch supervision
failure as soon as the duplex link is open.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check whether the notification with fault number 520 is sent cyclically or not.
If not, the chain had a temporary problem. Go to step 5.
If the notification is sent cyclically, check that a notification with fault number 522
is emitted as well.
If not, call the manufacturer.

If yes, go to step 2.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
2
Action
Replace the SWC board (Field Replaceable Unit):
If the fault persists, go to step 2.
If the fault disappeared, go to step 3.
Replace the SUP board (Field Replaceable Unit):

Additional checks
Step
Action
When the problem has been resolved, clear the alarm if necessary.
2.58

ii
Fault number:
520 : Fault on switching matrix access
FAULT ANALYSIS
This notification indicates that there is a transmission problem between the CPU133IE
board (CPU--OMU) and the SWC board. The fault was detected by the CPU133IE board,
which supervises the SWC board through the SUP2 board (synchronous link).
The faulty element is the SWC board, or the SUP2 board, or the link between the boards.
The chain concerned (either the active or the passive one) is mentioned in the notification.

BSC defense
If the problem seldom happens, there is not any BSC defense.
If the problem often happens, the chain concerned commits suicide.
chain.
Then the chain concerned sends a notification with fault number 522 Switch supervision
failure as soon as the duplex link is open.

None.
FAULT TREATMENT
Step
1
Action
Check whether the notification with fault number 520 is sent cyclically or not.
If not, the chain had a temporary problem. Go to step 5.
If the notification is sent cyclically, check that a notification with fault number 522
is emitted as well.
If not, call the manufacturer.

If yes, go to step 2.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)

Replace the SUP2 board (Field Replaceable Unit):

Additional checks
Step
Action
When the problem has been resolved, clear the alarm if necessary.
2.59
Fault number: 521

iii
Fault number:
521 : Fault on switching matrix
FAULT ANALYSIS
This notification indicates that one of the components of the switching matrix is faulty and
that consequently the test on the connection memory is failed. This test is performed every
50 connections.
The faulty element is the MSW 0 or 1 board, or the SWC board.

BSC defense
chain.

None.
FAULT TREATMENT
Step
1
Action
Replace the MSW board (Field Replaceable Unit):
c. Check that the fault disappeared.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)

Additional checks
Step
Action
Check that the fault has disappeared (the alarm messages are transferred into the
alarm history file of the OMC--R).
2.60

Fault number:
522 : Switch supervision failure
FAULT ANALYSIS
The faulty element is the SWC board. The location is given by the notification.

BSC defense
chain.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Perform a Display all or a Display chain information command on the bsc object
to check the state of the SWC board.
If the SWC board state is faulty, replace it. Go to step 3.
If the SWC board state is working, go to step 2.
to check the state of the SUP board.
If the SUP board state is faulty, go to step 4.
If the SUP board state is working, clear the alarm. Go to step 6.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
3
Action
b. The operations for return to service are described in the replacement procedure.
Replace the SUP board (Field Replaceable Unit):

Refer to the replacement procedure (see NTP < 41 >).
Check the cable between the SUP board and the SWC board.
If the cable is badly connected or damaged, connect it correctly or replace it.
Then go to step 6.
If the cable is operational, call the manufacturer.
Additional checks
Step
Action
2.61

iii
Fault number:
522 : Switch supervision failure
FAULT ANALYSIS
The faulty element is the SWC board. The location is given by the notification.

BSC defense
chain.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
to check the state of the SWC board.
If the SWC board state is faulty, replace it. Go to step 3.
If the SWC board state is working, go to step 2.
to check the state of the SUP2 board.
If the SUP2 board state is faulty, go to step 4.
If the SUP2 board state is working, clear the alarm. Go to step 6.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
3
Action
b. The operations for return to service are described in the replacement procedure.
Replace the SUP2 board (Field Replaceable Unit):

Refer to the replacement procedure (see NTP < 41 >).
Check the cable between the SUP board and the SWC board.
If the cable is badly connected or damaged, connect it correctly or replace it.
Then go to step 6.
If the cable is operational, call the manufacturer.
Additional checks
Step
Action
2.62
Fault number: 523

iii
Fault number:
523 : Fault on internal PCM (BSC, TCU)
FAULT ANALYSIS
The beginning of fault indicates a negative cyclic test on the TS 0 of one of the internal PCM.
The internal PCM is no longer operational.
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.63
Fault number: 524

iii
Fault number:
524 : Slave switch board not present
FAULT ANALYSIS
The location of the board is given in the notification.

BSC defense
chain.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Perform a Display chain information command on the bsc object to check how
many PCM links are faulty.
If at least one PCM link is faulty, the SWE board must be replaced. Go to step 3.
If more than 16 PCM links are faulty, the MSW board must be replaced. Go to
step 2.
Step
Action
Replace the SWE board (Field Replaceable Unit):

b. The operations for return to service are described in the equipment replacement
procedure.
Replace the MSW board (Field Replaceable Unit):

b. The operations for return to service are described in the equipment replacement
procedure.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.64

iii
Fault number:
601 : File management error
FAULT ANALYSIS
If the problem persists, a site visit is required.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Replace the faulty MMU board (Field Replaceable Unit):
b. After replacing the MMU board, follow appropriate procedures in NTP < 41 > to
execute the maintenance procedure for the disk of a BSC:
i.
Install the BSC software on the new disk.
ii.
The automatic customization takes place.
iii.
If necessary, apply BSC patches.
If the file management error persists, go to step 2.

Step
Action (Continued)
Replace the CPUM board (CPU66SE) (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Clear the fault alarm manually if necessary.
Make sure that the repaired chain does not commit suicide again and check the
state of the display panels on the SUP board: 12 must be displayed if the chain
is operational.
Standard 15.101/EN
July 2005
2.65

oo
Fault number:
FAULT ANALYSIS

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Replace the faulty MMU_IDE board (Field Replaceable Unit):
b. After replacing the MMU board, follow appropriate procedures in NTP < 41 > to
execute the maintenance procedure for the disk of a BSC:
i.
Install the BSC software on the new disk.
ii.
The automatic customization takes place.
iii.
If necessary, apply BSC patches.
If the file management error persists, go to step 2.

Step
Action (Continued)
Replace the CPUM board (CPU133IE) (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
state of the display panels on the SUP2 board: 12 must be displayed if the chain
is operational.
Standard 15.101/EN
July 2005
2.66

iii
Fault number:
607 : Multibus II error
FAULT ANALYSIS
The fault is detected by the CPUM (CPU66SE) board, which indicates a minor problem
during initialization of the Multibus II. This fault may be due to malfunction of one of the
boards in the control cabinet.
If the problem persists, a site visit is required (call the manufacturer).

BSC defense
The system attempts to reinitialize the Multibus II cyclically.

None.
FAULT TREATMENT
Step
1
Action
a. Refer to the appropriate replacement procedure in NTP < 41 >:
CPUM (CPU66SE) board
CCS7 boards
CPUE boards
SICX board
SUP board
SICD8V boards
b. Concerning the boards linked to the Multibus II, the operations for return to
service are performed by the system.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Clear the fault alarm manually, if necessary.
is operational.
Standard 15.101/EN
July 2005
2.67

ii
Fault number:
FAULT ANALYSIS
The fault is detected by the CPUM (CPU133IE) board, which indicates a minor problem
during initialization of the Multibus II. This fault may be due to malfunction of one of the
boards in the control cabinet.
If the problem persists, a site visit is required (call the manufacturer).

BSC defense
The system attempts to reinitialize the Multibus II cyclically.

None.
FAULT TREATMENT
Step
1
Action
CPUM (CPU133IE) board
CCS7 boards
CPUE (CPU133) boards
SICX board
SUP2 board
SICD8V boards
b. Concerning the boards linked to the Multibus II, the operations for return to
service are performed by the system.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Clear the fault alarm manually, if necessary.
is operational.
Standard 15.101/EN
July 2005
2.68
Fault number: 617

iii
Fault number:
617 : SCSI bus controller error
FAULT ANALYSIS
The fault has been detected by the CPUM board, which indicated a minor problem during
initialization of the SCSI bus controller of the MMU board (SCSI disk).
This fault may be due to malfunction of:
the MMU board (SCSI disk) or
the CPUM (CPU66SE) board or
the back plane

BSC defense
The system cyclically attempts to reinitialize the bus controller between the MMU board
(SCSI disk) and the CPUM board (CPU66SE).

None.
FAULT TREATMENT
Step
1
Action
Check the state of the CPUM board (CPU66SE):
If the CPUM board is operational, go to step 3.
If the CPUM board is not operational, go to step 2.
Step
Action (Continued)

Check the state of the MMU board (SCSI disk):
If the MMU board is operational, go to step 5.

If the MMU board is not operational, go to step 4.
Replace the MMU board (SCSI disk) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >)

b. After having replaced the MMU board, perform the maintenance procedure for
the disk of a BSC (see NTP < 41 >) for return to service.
Check the state of the back panel:
If the backpanel is operational, go to step 7.

If the backpanel is not operational, go to step 6.
6
Repair the backpanel.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
10
Standard 15.101/EN
July 2005
2.69

iii
Fault number:
FAULT ANALYSIS
This notification indicates that there is a problem with file management on the BSC disk.
The faulty item of equipment is either the disk itself, on the MMU board, or the CPUM board
(CPU66SE).

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
b. After having replaced the MMU board, execute the maintenance procedure for
the disk of a BSC (see NTP < 41 >).
If the file management system problem is over, go to step 3.
If the problem persists, go to step 2.

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.70

oo
Fault number:
FAULT ANALYSIS
This notification indicates that there is a problem with file management on the BSC disk.
The faulty item of equipment is either the disk itself, on the MMU_IDE board, or the CPUM
board (CPU133IE).

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Replace the MMU_IDE board (Field Replaceable Unit):
b. After having replaced the MMU_IDE board, execute the maintenance procedure
for the disk of a BSC (see NTP < 41 >).
If the file management system problem is over, go to step 3.
Replace the CPUM board (CPU133IE) (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.71
Fault number: 633

iii
Fault number:
633 : Disk driver error
FAULT ANALYSIS
The responsible equipment cannot be identified from the notification.
The fault is detected by the CPUM board, which indicates a problem during initialization of
the SCSI bus controller of the MMU board (SCSI disk).
This fault may be due to malfunction of the following:
MMU board
CPUM board (CPU66SE)

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
b. After having replaced the MMU board, follow the maintenance procedure for the
disk of a BSC and, if necessary, for return to service (see NTP < 41 >).
If the disk driver problem is over, go to step 3.
Step
Action (Continued)

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.72

iii
Fault number:
634 : Mirror disk
FAULT ANALYSIS
This hardware anomaly can be issued by the active or passive chain. It is detected by the
SCSI controller.
The anomaly may indicate a hardware problem on the chain sending the anomaly:
5 V power supply (ondulation or value outside tolerance thresholds)
SCSI disk on the MMU board
2.73

oo
Fault number:
634 : Mirror disk
FAULT ANALYSIS
This hardware anomaly can be issued by the active or passive chain. It is detected by the
IDE controller.
The anomaly may indicate a hardware problem on the chain sending the anomaly:
IDE disk on the MMU_IDE board
CPUM board (CPU133IE)
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.74

iii
Fault number:
FAULT ANALYSIS
This notification indicates that there is a problem with the Multibus II, or with a board
connected to this bus.

BSC defense
This fault does not lead directly to chain suicide. One of the boards of the Multibus II will
become faulty (because of a problem on the Multibus II) and cause the suicide of the chain.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check for the presence of a chain suicide message.
Step
Action

CCS7 boards
CPUE boards
SICX board
SUP board
SICD8V boards
b. For all other boards linked to the Multibus II, the operations for return to service
are performed by the system. Then go to step 3.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.75

iii
Fault number:
FAULT ANALYSIS
This notification indicates that there is a problem with the Multibus II, or with a board
connected to this bus.

BSC defense
This fault does not lead directly to chain suicide. One of the boards of the Multibus II will
become faulty (because of a problem on the Multibus II) and cause the suicide of the chain.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check for the presence of a chain suicide message.
Step
Action

CPUM board (CPU133IE)
CCS7 boards
CPUE boards (CPU133)
SICX board
SUP2 board
SICD8V boards
b. For all other boards linked to the Multibus II, the operations for return to service
are performed by the system. Then go to step 3.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.76
BSC fault numbers
Vol. 1 -- 2--211
Fault number: 649

iii
Fault number:
649 : SCSI protocol error
FAULT ANALYSIS
The faulty equipment is the MMU board or the CPUM (CPU66SE) board.
The type and location of the board are indicated by the notification.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
b. After having replaced the MMU board, execute the maintenance procedure for
the disk of a BSC, then, if necessary, for return to service (see NTP < 41 >).
If the SCSI protocol problem is over, go to step 3.

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
is operational.
Standard 15.101/EN
July 2005
2.77
Fault number: 656, 657

iii
Fault number:
656 and 657 : Ethernet controller chip error
FAULT ANALYSIS
The faulty equipment is the CPUM board.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Additional checks
Step
Action
is operational.
2.78
Fault number: 1074

iii
Fault number:
1074 : Indication of hardware in compatibility with activated features
FAULT ANALYSIS
After a Display all command, the BSC sends a global notification per CPU--BIFP board
that lists all the TDMA which do not support a feature required.
FAULT TREATMENT
The notification shows the incompatibilities between the features configured by the
operator and the hardware possibilities.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.79
Fault number: 1150

iii
Fault number:
1150 : Loss of DDTI configuration
FAULT ANALYSIS
This alarm indicates that a DDTI board lost its configuration.
The type and position of the board are specified in the notification.

BSC defense
The system isolates the DDTI board that has lost its configuration.
CAUTION
The service is reduced (in a multiMIC configuration) or reduced (in
a monoMIC configuration).
FAULT TREATMENT
2.80
Fault number: 1151

iii
Fault number:
1151 : PCM transmission fault
FAULT ANALYSIS
This notification indicates a transmission problem with one of the PCM links.
The PCM number and the associated DDTI board are specified in the notification.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.81
Fault number: 1152

iii
Fault number:
1152 : PCM CRC attribute and DDTI CRC strap are not consistent
FAULT ANALYSIS
Note: For information on the 1152 alarm for the TDTI board, refer to
Paragraph 3.9.
This notification is sent by the BSC when an inconsistency is detected between the
hardware configuration of the DDTI board and the setting of the BSC.
The cRC attribute of the pcmCircuit object (bsc -- Abis or Ater) does not match the CS17
and CS18 jumpers configuration on the DDTI board.
This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.

BSC defense
The pcmCircuit object is failed. The children objects (btsSiteManager, bts,
transceiverEquipment, transceiver) are unconfigured.
CAUTION
The service is reduced or lost, depending on the configuration.
FAULT TREATMENT
Preliminary checks
Step
Action
Check the state of the PCM link, by performing a Display all command on the
pcmCircuit object.
If the pcmCircuit object is disabled, wait until it becomes enabled.

If the pcmCircuit object is disabled--dependency, look for a notification with
fault number 523 Fault on internal PCM (BSC, TCU).
If the pcmCircuit object is failed, go to step 2.
If the pcmCircuit object is enabled, clear the alarm. Go to step 6.
At the OMC--R, check the cRC attribute value by performing a Display command
on the pcmCircuit object.
If the cRC parameter value is used, go to step 3.

If the cRC parameter value is not used:
i.
set the pcmCircuit object to locked
ii.
set the cRC parameter to used
iii.
set the pcmCircuit object to unlocked.
iv. Then go to step 4.
Step
3
Action
On site, change the CS17 and CS18 jumpers on the DDTI board:
a. Set the pcmCircuit object to locked.
b. Change the CS17 and CS18 jumpers on the DDTI board. For more information
on the jumpers position, refer to the appropriate procedure in NTP < 41 > for
DDTI E1 -- GSM 900/1800 or DDTI T1 -- GSM 1900.
c. Set the pcmCircuit object to unlocked. Then go to step 4.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Additional checks
Step
4
Action
Check the state of the equipment, by performing a Display all command on the
bsc object.
Clear the alarm.
2.82
Fault number: 1153

iii
Fault number:
1153 : Negative test on passive chain LAPD channel (layer 2)
FAULT ANALYSIS
The passive chain tests the links between:
the SICD, RCB, SWC, MSW, SWE and DDTI boards (between BTSs and BSC), if there
is not any Abis concentration. The lapd test loops back in the DDTI boards, at the entry
of the internal PCM link.
the SICD, RCB, SWC, MSW, SWE boards and BSCB boards (between BTSs and BSC)
or TSCB boards (between TCUs and BSC), if there is Abis or Ater concentration.The
lapd test loops back in the BSCB or TSCB boards. Thus the passive link between the
DDTI and the BSCB (or TSCB) boards is not tested.
This test is performed by the passive chain each time the passive chain restarts, and the
number of failed tests is recorded.
The active chain compares the test results of the two chains when it has to choose between
the two chains after a chain suicide.
If all the equipment is operational, there is no global fault on a board, but a wiring problem
or an internal board problem (and not detected by the internal mechanism of the board).

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Analyze the circumstances in which the notification appears:
When the notification appears for a chain that becomes active, do not take it into
account. Go to step 3.
On a beginning--of--fault, perform a Display all command on the bsc object.
Check the value of the passive chain sic channels state attribute:
If the state is working, clear the alarm. Go to step 4.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)
If the state is faulty, there may be notifications concerning the SICD, RCB,
SWC, MSW, SWE, DDTI, BSCB or TSCB board.
If there is a notification, treat it.
Step
2
Action
Follow appropriate procedures in NTP < 41 > to replace the following boards, one
after the other (Field Replaceable Unit), to find out which one is faulty:
SICD board
RCB board
SWC boards
MSW 0 and 1 boards
SWE 0 and1 boards
DDTI boards
BSCB boards
TSCB boards
If the faulty board has been identified and replaced, go to step 4.
Check the inter--cabinet wiring, and the cables connecting the boards mentioned
above.
If the wiring is correct, call the manufacturer.
If the wiring is incorrect, reconnect it correctly, or repair it.
Additional checks
Step
Action
Perform a Display all command to check that the alarms disappeared.
If necessary, manually clear the alarm.
2.83
Fault number: 1154

iii
Fault number:
1154 : Negative test on passive chain CCS7 signalling link (layer 2)
FAULT ANALYSIS
The passive chain tests the links between the CCS7, SWC, and MSW0 boards. The ccs7
test loops back in the CCS7 boards, at the entry of the internal PCM link.
Source:
0 High error rate in service
1 Basic error correction mechanism
2 Excessive acknowledgement delay
3 SIOS, SIO or SIN frames received
4 Stopped by layer 3
5 Other layer 2 error
6 Remote processor outage
7 MSU test KO
8 No answer from CCS7 card
9 Timeout awaiting MSU ack
This test is performed by the passive chain each time the passive chain restarts, and the
number of failed tests is recorded.
The active chain compares the test results of the two chains when it has to choose between
the two chains after a chain suicide.
If all the equipment is operational, there is no global fault on a board, but a wiring problem
or an internal board problem (and not detected by the internal mechanism of the board).

BSC defense
None.

None.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
FAULT TREATMENT
Preliminary checks
Step
1
Action
Analyze the circumstances in which the notification appeared:
When the notification appears for a chain that becomes active, do not take it into
account. Go to step 3.
On a beginning--of--fault, perform a Display all command on the bsc object.
Check the value of the passive chain sic channels state:
If the state is working, clear the alarm. Go to step 4.

If the state of a board is faulty, there may be notifications concerning a
SWC, MSW or CCS7 board.
If there is a notification, treat it.

Step
2
Action
Follow appropriate procedures in NTP < 41 > to replace the following boards, one
after the other (Field Replaceable Unit), to find out which one is faulty:
SWC boards
MSW 0 board
CCS7 boards
If the faulty board has been identified and replaced, go to step 4.
Check the inter--cabinet wiring, and the cables connecting the boards mentioned
above.
If the wiring is correct, go to step 4.
If the wiring is incorrect, reconnect it correctly, or repair it.
Additional checks
Step
Action
Perform a Display all command to check that the alarms disappeared.
2.84

iii
Fault number:
1155 : Fault on SLS card
FAULT ANALYSIS
The position of the SLS board is given in the notification.

BSC defense
None.

None.
FAULT TREATMENT
Step
Action
Replace the faulty SLS board (Field Replaceable Unit):

Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Standard 15.101/EN
July 2005
2.85
Fault number: 1155 (BSC12000 HC)

oo
Fault number:
1155 : Fault on SLS card
FAULT ANALYSIS
The position of the SLS2 board is given in the notification.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Replace the faulty SLS2 board (Field Replaceable Unit):
Additional checks
Step
Action
2.86
Fault number: 1164

iii
Fault number:
1164 : OMC access failure
FAULT ANALYSIS
This notification indicates that the REM link selftest result is bad.
The degradation level is mentioned in the notification:
partial: when one of the two links allowing the OMC--R access (X25 network, or
A interface) is degraded
total: when the two links are degraded
The REM link selftest is performed:
on the passive chain:
On the A interface, the selftest starts two minutes after the end of the chain start--up
(12--12 phase). It is performed cyclically. The boards involved are the SICX, SWC
and MSW 0 boards. If an anomaly is detected, this notification with fault number
1164 is sent, and partial is displayed in the degradation level field.
On the X25 network, the selftest is performed every hour. The boards involved are
the SICX and SLS2 boards.The selftest loops back on the SLS2 board. If an anomaly
is detected, this notification with fault number 1164 is sent, and partial is displayed
in the degradation level field.
on the active chain:
The chain triggered the selftest. If the REM link is lost, this notification with fault
number 1164 is sent, and total is displayed in the degradation level field.

BSC defense
When the two links are degraded on the active chain (total is displayed in the degradation
level field), a switchover is performed.

None.
FAULT TREATMENT
Step
1
PE/DCL/DD/0101
411--9001--101
Action
Check which interface is involved:
Standard 15.101/EN
July 2005
Step
Action (Continued)
If the A interface is concerned, go to step 2.

If the X25 network is concerned, go to step 3.
2
Look for a notification with fault number 520 Fault on switching matrix access
concerning the SWC board, and a notification with fault number 523 Fault on
internal PCM involving the MSW 0 board.
If there are notifications, treat them. Then go to step 4.
If not, follow the appropriate procedures in NTP < 41 > to replace the following
boards, one after the other, to find out which one is faulty:
the SICX board (Field Replaceable Unit).

the SWC board (Field Replaceable Unit).
the MSW board (Field Replaceable Unit).
Then go to step 4.
3
Replace the following boards one after the other, to find out which one is faulty (Field
Replaceable Unit):
a. Refer to the appropriate replacement procedures in NTP < 41 >:
the SICX board.
the SLS2 board.
Additional checks
Step
Action
2.87
Fault number: 1193

iii
Fault number:
1193 : Clock alarm
FAULT ANALYSIS
The state change of one of the reference clocks is detected by the ECI board, and it
implicates the DDTI board or, the external PCM, or the ECI board itself. The object and the
instance in the alarm identify the suspected clock. The object concerned by this alarm is
the pcmCircuit object for the PCMs of the Ater interface.

BSC defense
This anomaly is sent by the BSC at each state change of a synchronizing clock supported
by a PCM of the Ater interface in service.
In case of synchronization problem, the ECI board looks for a new reference clock and
sends a notification with fault number 497 New PCM selected as clock reference.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check whether this notification is often sent to the OMC--R or not.
If yes, the problem may come from:
a transcoder object which is locked.

Find out why it is locked.
If it is unlocked, go to step 2.
an unstable PCM link. Go to step 2.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
Action (Continued)
To locate the fault, this anomaly must be associated with the following:
an operator warning with fault number 497 on the bsc object to identify the new
reference clock with the value of the New PCM field
a fault with fault number 1151 for the external PCM on the Ater interface.
Concerning the PCM faults, refer to NTP < 105 >.
a fault with fault number 7 for the DDTI boards
Treat the alarm(s). Then go to step 3.
Additional checks
Step
Action
Check the transmission network.
2.88
Fault number: 1201

iii
Fault number:
1201 : Degraded active chain
FAULT ANALYSIS
This message warns the operator that a BSC has just switched over onto a degraded chain.
The passive chain must be repaired to (at least) ensure nominal service.

BSC defense
None.

Both BSC chains are degraded.
FAULT TREATMENT
Preliminary checks
Step
Action
Wait for the end of the passive chain restart.
Look for other alarms or notifications indicating faulty elements (fault number 16,
15, 11, 7, 6, 5) on the passive chain. They must have been previously issued.
The alarm identifies the number of declared boards and the number of available
boards (ECI, SICX, SICD, CCS7, switching boards).
The alarm also indicates the disk state, in the disk status field:
0 partial hard disk degradation
1 total hard disk degradation
PE/DCL/DD/0101
411--9001--101
Repair the passive chain as indicated in the information found in step 2.
Standard 15.101/EN
July 2005
Step
Action (Continued)
When the passive chain is fixed, a chain switchover takes place because the BSC
always chooses the better chain as the active one.
Then look for other alarms or notifications indicating faulty elements (fault number
16, 15, 11, 7, 6, 5) on the new passive chain (that was previously the degraded
active chain). They must have been previously issued.
Repair the passive chain as indicated in the information found in step 5. Then go
to step 7.
Additional checks
Step
Action
Wait until the BSC comes back in duplex state.
Execute an active chain suicide by a provoked switchover on the OMC--R.
Make sure that the repaired chain becomes active again.
10
2.89
Fault number: 1211

ii
Fault number:
1211 : Unknown TEI in a LAPD message received by the XSCB card
FAULT ANALYSIS
A message with an unknown TEI was received on a TSCB or BSCB board.
This notification indicates a software problem.
The type of faulty board (either TSCB or BSCB), and its number are given in the notification.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.90
Fault number: 1212

iii
Fault number:
1212 : xSCB card internal fifo congestion
FAULT ANALYSIS
This notification indicates a TSCB or BSCB board load problem.

BSC defense
None.

None.
FAULT TREATMENT
Step
1
Action
Check how many alarms with Fault number 1212 have been received at the
OMC--R.
If this notification is exceptional, it corresponds to a transient overload. No
maintenance is required. Go to step 3.
If this notification is often received at the OMC--R, it corresponds to an
insufficient configuration. Go to step 2.
Change the configuration:

If possible, add a BSCB board. Then go to step 3.
If not, perform a reparenting so that sites and load are better distributed. Call the
manufacturer.
2.91
Fault number: 1312

iii
Fault number:
1312 : MSC inaccessible
FAULT ANALYSIS
This alarm is sent by the BSC after eight consecutive no response to the Reset command.

BSC defense
None.
CAUTION
The service is lost because the A interface is not available.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Perform a Display all interrogation on a signallingLink object.
If the object is unlocked--enabled and the resource is available, do not take this
Otherwise, go to step 2.
PE/DCL/DD/0101
411--9001--101
Look for alarms concerning the BSC, TCU, TCU/MSC link or BSC/TCU link.
Standard 15.101/EN
July 2005
Step
Action (Continued)
If alarms concern the BSC, TCU, or BSC/MSC link:

i.
ignore the alarm with fault number 1312
ii.
process the alarms on the faulty element
iii.
check that the alarm with fault number 1312 is not reissued, or
perform a Display all interrogation on the object.
When this notification with fault number 1312 appears alone, look for a problem
at the MSC level.
Additional checks
Step
Action
Clear the alarm if necessary and perform a Display all interrogation of the
signallingLink object.
2.92
Fault number: 1315

iii
Fault number:
1315 : Path Information for calls released by TCU or BTS
FAULT ANALYSIS
In cases where there is a loss of communication between the TCU and the BTS, the user
would hear only silence and would eventually terminate the call. The system now detects
these types of failures and releases the call automatically.
This warning notification is sent to indicate the path associated with the dropped call to
facilitate troubleshooting the problem.
The warning is subject to a threshold: 100 occurrences affecting the same path will result
in 1 warning at the OMC--R.
The quantity of calls dropped can be tracked by Counters:
C1164/28 -- Calls dropped by the TCU
C1164/32 -- Calls dropped by the BTS
The fault could be indicative of Transmission Line failure, Transmission Equipment failure
(i.e. DACS) or a failure within the BSC 3000 or TCU 3000 or BTS.

BSC defense
None.

Calls have been dropped.
FAULT TREATMENT
Preliminary checks
Step
1
PE/DCL/DD/0101
411--9001--101
Action
Monitor counter C1164 to determine the frequency of occurrence and which
transmission direction is affected:
Standard 15.101/EN
July 2005
Step
Action (Continued)
C1164/28: Indicates a failure in the path from BTS to TCU.

C1164/32: Indicates a failure in the path from TCU to BTS.
Note: Either one may be caused by a failure of either ABIS or ATER PCM.
2
Check for any notifications relating to the BSC, TCU or Transmission links (PCM),
treat these symptoms first then verify if counters are still incremented.
Call the manufacturer for help in decoding the failing path information which
appears in the Manufacturer Information part of the notification.
Optional further checks

These optional checks can only be done after contacting the manufacturer for help in
decoding the path of the failed calls.
Step
1
Action
Using the decoded path information provided by the manufacturer (see preliminary
check step 3):
Look for reoccurring instances of the same object (i.e. TRM, PCM, Timeslot.)
If the most commonly failing object is a PCM or Timeslot, determine if it is an
ATER or ABIS PCM.
Confirm failing path:

Try to physically swap PCMs, or lock one PCM at a time.
Try to lock impacted Radio Channels.
i.
Verify if counter C1164 is still incremented.
ii.
If counters are no longer incremented, fault is confirmed, go to step 3.
iii.
If counters are still incremented go to step 5
If either the ATER or ABIS PCM pass through intermediate equipment such as a
DACS:
Check the DACS board that manages the PCM and the DACS configuration.
The DACS (and many other types of transmission equipment) will often have
counters indicating errors, errored seconds, BPVs, slips, or Frame errors. Use
these to localize the source of the problem. Note that, depending on the type of
DACS, it may re--frame the signal, which would tend to mask alarms and some
types of errors (slips, notably).
Step
Action (Continued)
All transmission facilities should be configured to use appropriate zero--code

suppression (i.e., B8ZS for DS1 facilities).
PE/DCL/DD/0101
411--9001--101
Using suitable test equipment, perform end--to--end quality test of failing PCM.
Ensuring that all Timeslots are checked.
If the failing PCMs are associated with the same LSA perform a SWACT of the
associated IEM.
If failure is associated with the same TRM, replace the TRM.
If problem is not identified, Call the manufacturer.
Standard 15.101/EN
July 2005
2.93
Fault number: 1366

iii
Fault number:
1366 : Indication of the SSN LCS state
FAULT ANALYSIS
This notification is sent when a client of the SS7 protocol becomes available or becomes
unavailable (at each state change of the SSN LCS).

None.
FAULT TREATMENT
No maintenance action is required.
2.94
Fault number: 1470

iii
Fault number:
1470 : Impossibility of storage of a general permanent observation
message
FAULT ANALYSIS
This message means that there is a permanent observation file writing problem on the BSC
disk. This notification specifies the doubtful disk partition: GPO (General Permanent
Observation).
This message is emitted in the following conditions:
1) An observation file must be written on the BSC disk, in the GPO partition. Normally, the
file is then retrieved by the OMC--R, and then deleted.
2) But the GPO partition is full. This problem may occur if OMC--R does not retrieve the files
that contain observation results quickly, or when the link between the BSC and the OMC--R
has been lost for quite a long time (more than three days).
3) Then the GPO partition is automatically purged. A notification with fault number 1472
Purge realized to store a GPO message is sent.
4) Despite the purge, the partition is still full and the observation file cannot be stored on
the disk. The observation file is lost and this notification is emitted. The notification is
emitted for each lost file. This problem may occur if the files already stored on the disk
cannot be deleted for one of the following reasons:
they do not have the right format (tyyddhhmmss)
they are not old enough to be deleted:
OGS files (Observation General Statistic) must be older than 72 hours

OFS files (Observation Fast Statistic) must be older than 24 hours
ODIAG files (Observation Diagnostic) must be older than 24 hours
BSC defense
None.

None. The only effect is the loss of observation files but this does not affect system
operations.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
FAULT TREATMENT
Step
Action
Check the size and the content of the GPO partition since, in spite of purging, there
is not enough place on the disk.
If the partition size is normal, or if some files on the disk do not have the right format
(tyyddhhmmss), call the manufacturer.
2.95
Fault number: 1472

iii
Fault number:
1472 : Purge realized to store a general permanent observation
message
FAULT ANALYSIS
This message indicates an automatic permanent observation purging on the GPO partition
(General Permanent Observation).
This fault may occur if OMC--R does not retrieve the files that contain observation results
quickly, or when the link between the BSC and the OMC--R has been lost for quite a long
time (more than three days).
The file specified in the notification is the file generated by purging and not the name of the
purged file. Purging is performed before writing on the disk again.
The following files have been purged:
OGS files (Observation General Statistic) older than 72 hours
OFS files (Fast Statistic) older than 24 hours
ODIAG files (Observation Diagnostic) older than 24 hours
Some files can actually be much older than 72 hours, because purging is performed only
when the GPO partition is full.

BSC defense
None.

None. The only effect is the loss of observation files but this does not affect system
operations.
FAULT TREATMENT
Check that the observation files are retrieved by the OMC--R, and that the link between the
BSC and the OMC--R is operational.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.96
Fault number: 1483

iii
Fault number:
1483 : Impossibility of storage of non prioritary records
FAULT ANALYSIS
This notification indicates that it is impossible to store non prioritary records (or partial
records) associated with the CALL--TRACING function on the dedicated partition of the disk
of the BSC.
1) A radio observation file must be written on the BSC disk, in the dedicated partition.
2) But the partition is full, or does not have enough space left.
3) This notification (Beginning--of--fault) is sent, only once, even if several files cannot be
stored on the BSC disk.
4) Then the partition is automatically purged. All the radio observation files are deleted. Only
the management file is kept.
5) If the purge was successful, this notification is sent again as an End--of--fault. If the purge
failed (which never happens a priori), the partition is still full and the radio observation file
cannot be stored on the disk, and is lost.

BSC defense
None.

None. The only effect is the loss of radio observation files but this does not affect system
operations.
FAULT TREATMENT
If the purge failed, call the manufacturer.
2.97
Fault number: 1484

iii
Fault number:
1484 : Impossibility of storage of files
FAULT ANALYSIS
This notification indicates that it is impossible to store CALL PATH TRACING files on the
dedicated partition of the disk of the BSC.
1) A radio observation file must be written on the BSC disk, in the dedicated partition.
2) But the partition is full, or does not have enough space left.
3) This notification (Beginning--of--fault) is sent, only once, even if several files cannot be
stored on the BSC disk.
3) Then the partition is automatically purged. All the radio observation files are deleted. Only
the management file is kept.
4) If the purge was successful, this notification is sent again as an End--of--fault. If the purge
failed (which never happens a priori), the partition is still full and the radio observation file
cannot be stored on the disk, and is lost.

BSC defense
None.

None. The only effect is the loss of radio observation files but this does not affect system
operations.
FAULT TREATMENT
If the purge failed, call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.98
Fault number: 1486

iii
Fault number:
1486 : Call path tracing activity state change
FAULT ANALYSIS
This notification indicates a CALL PATH activity state change, associated with the
callPathTrace object.

BSC defense
None.

None.
FAULT TREATMENT
This notification is a warning. No maintenance is required.
2.99
Fault number: 1490

iii
Fault number:
1490 : BSC overload
Type :
FAULT ANALYSIS
This alarm indicates that calls are blocked because of a BSC overload. The overloaded
board(s) is(are) given in equipment type and equipment number fields.
This alarm can be sent during a chain start--up, and during a chain switchover.
It is first sent as a Beginning--of--fault alarm, when one BSC board has been in overload
level 3 for more than five seconds. The name of the board concerned is given in the
notification. Even if other boards have also been in overload level 3 for more than five
seconds, this beginning--of--fault alarm is sent only once.
This alarm is also sent as an End--of--fault alarm, when all the boards are under the overload
3 level again. The list of the boards concerned is given in the notification. These boards have
been in overload level 3 for more than one second. The end--of--fault alarm is sent only
once.

BSC defense
None.
CAUTION
Service reduction
The service is reduced, because new calls cannot be established.
FAULT TREATMENT
None, if the alarm corresponds to a transient increase of the traffic.
However, if the alarm is very often sent to the OMC--R, try to find out why (BSC/network
dimensioning, etc.). At the OMC--R, look at the counters signaling failed call establishment
(e.g.: 1835 counter). Call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.100 Fault number: 1502

iii
Fault number:
1502 : Access attempt to a non operational cell
FAULT ANALYSIS
This message warns the operator that an access attempt to a non operational cell has been
made. This can be due to:
an access attempt to a non--created cell
paging attempted on a cell in which paging is not authorized
paging on a cell in which all System Information messages have been acknowledged
This notification indicates a configuration problem.
When Cell is created, but not operational then the fault number 1502 is sent to the OMC--R.
This could happen when:
1. Cell has been created, attributed and then de--attributed.
After the creation of the cell, a cell in Operational state is attributed after receiving Sys Info
Acknowledgments from BTS.
A Cell in Operational state is de--attributed, when the cell is out of service in BSC.
Fault number 1502 is sent to OMC--R, after one of the following call flows occurs:
Call Flow 1
A Channel Required message is sent to the BSC (Traffic Management).
Traffic management issues fault number 1502.
Call Flow 2
An inter--cell handover is requested for a call setup on its destination cell (inter or intra BSC).
An Access Request message is sent to the BSC (Traffic Management).
Traffic management issues fault number 1502.
Fault number 1502 is issued for the following reason:
If the CCCH downlink channel is not initialized and if the BSC is in the active mode, fault
number 1502 is triggered. The warning is issued, if this scenario is executed more than 100
times. The limitation of 100 times exists because of a warning threshold present in RADCEL
warning management.
2. Cell has been created but not attributed.
The cell has not been attributed by SPR (Radio supervision), i.e., Sys Info Exchange has
not happened between BSC and BTS for this cell.
FIELD DESCRIPTION
Target CGI: cell parameters, mcc, LAC, mnc, ci
Cell Admin State:
0: not created
205: created
Cell Paging State:

0: not significant
1: not allowed because BCCH information
Not Acknowledged:
2: paging request allowed
Radio Data Consistency for TMG point of view:
0: consistent
1: inconsistent
TS Carrying Common Channel:
TS carrying common channel

BSC defense
None.
CAUTION
Service reduction
FAULT TREATMENT
Check the configuration against the information given in the notification.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
2.101 Fault number: 1503

iii
Fault number:
1503 : Access attempt to an unknown BCCH or BSIC
Type : CommunicationsAlarm
FAULT ANALYSIS
This anomaly is sent when a handover is required towards a (bsic,bcch) not belonging to
the neighbouring cells of the originated cell.
This alarm indicates that a mobile sents measurement reports with measures reported from
an unknown neighbor cell identified by the couple (BCCH, BSIC) which is not declared in
the adjacent handover cell list at the OMC--R.

BSC defense
None

None.
FAULT TREATMENT
To solve this problem, check the frequency plan and the frequency bands. For the cells
found in the Session Log, verify the accuracy of the datafill (BSIC/BCCH) for the impacted
cell (on the bts object) and its neighboring cells.
2.102 Table of software error descriptions

iii
The minor or major software anomaly messages inform users of faults detected
during BSC processing chain application software runs. The software anomalies are
only used by the manufacturer and do not require maintenance action.
In some cases, the software anomalies may indicate a configuration problem, a
database problem or a disk problem.
Minor software anomalies (level 5 priority messages) are filtered at MD level and
they are not displayed in notification windows at the OMC--R. They are displayed
in italics in the following list.
However, filtered notifications can be displayed using the BBS Faults Statistics
tool. For more information on this tool, refer to NTP < 39 >).
101
: Incorrect ZHCOM message area
102
: Incorrect ZDATA message area

This fault occurs when an attempt is made to change the attributes of a bts
object when the BSC has not yet unconfigured the object. When this
happens, the notification Incorrect Z--data Message Area, or Fault
Number: 102 will be generated.
If either of these notifications is received, the operator should perform a
BDA audit on the BSC in question. If the audit passes with no differences,
then there is no problem. If the audit detects differences, then an On--Line
Reset and BDA Build must be performed inside the maintenance window.
All operators should perform the periodic maintenance of BDA audits
twice weekly to notify them of any inconsistencies.
103
: Unknown communication map
104
: Unknown family value
105
: Unknown operation code
106
: Unknown class value
107
: Unknown instance value
120
: Unexpected message
121
: Requested action already done
122
: Erroneous processing data
123
: Erroneous internal data

This software anomaly may indicate a database problem with the CGI or
inconsistency on the database between the BSC and the MSC when the cell
is unknown during handover (bad neighboring configuration).
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
124
: Erroneous external data
125
: Erroneous internal static table
126
: Erroneous internal execution report
127
: Lack of internal resources
128
: Problem during cold init
130
: Unexpected message
131
: Requested action already carried out
132
: Erroneous processing data
133
: Erroneous internal data
134
: Erroneous external data
135
: Erroneous internal static table
136
: Erroneous internal execution report
137
: Lack of internal resources
138
: Current task is stopped
139
: Load data KO
140
: No response from a software entity (minor software anomaly that is

not filtered)
The ABS Phase 2 mechanism detects object state inconsistencies within
BSC surveillance tasks. These inconsistencies usually occur while
performing lock/unlock or delete/create actions at the OMC--R. Once an
inconsistent state has been detected within internal BSC tables, ABS
Phase 2 correction begins by clearing the surveillance state machines and
initiating a passive chain restart. The restart allows the passive chain to
update and mirror itself to the active chain BDA.
An ABS Phase 2 is not a BSC failure, but a defense action. Each passive
chain suicide, due to ABS Phase 2, generates a dump file that, if reported,
can be collected and analyzed by Nortel Networks Technical Support. The
captured data provides information on BSC performance and offers
additional data which is used in patch and version creation.
150
: No response from a software entity
151
: No response from a hardware entity
160
: System error: lack of timer
161
: System error: I/O error
162
: System error: waiting queues (pre)overload
163
: System error: stacks overflow
164
: Local overload defense
170
: System error: FSM error
171
: System error: exchange error
172
: System error: stack error
173
: System error: lack of FSM
174
: System error: system semaphore error
190
: UTE suicide due to SCO
191
: UTE suicide due to application
192
: UTE suicide due to system
200
: Disk I/O
201
: File management system
202
: Disk driver
203
: Mirror disk: services and user functions

The active chain issues this software anomaly when the passive chain has
not acknowledged a transaction on the mirror link.
The anomaly may indicate a hardware problem on the passive chain:
SCSI disk
CPUM board
rarely, an Ethernet problem
PE/DCL/DD/0101
411--9001--101
204
: Mirror disk: state machine
205
: Mirror disk: transmission protocol
206
: Transport data link
207
: Data link layer
208
: Access to interconnection area
209
: Data transport layer
210
: Access to multibus II management coprocessor
211
: Switching matrix access and transmission protocol
212
: Switching matrix access
213
: Protocol transmission layer 1
Standard 15.101/EN
July 2005
214
: SUP card access management
215
: SCSI: bus management
216
: SCSI: units logical management
217
: SCSI: bus controller management
218
: SCSI: protocol management
219
: X25 layer 1 and 2
220
: HDLC handler
221
: LAPB layer 2
222
: Passive chain restart inhibited to be manually activated
223
: Debug complementary information
224
: Instrumentation complementary information
225
: Ethernet driver
226
: Ethernet driver
229
: System card transmission
230
: BSC capacity reduction
231
: Loader
232
: UC loader
233
: Data loader
234
: Remote SCO access loader
235
: Local SGF access loader
236
: C library
237
: Sympa station
238
: Load function
239
: State machine management
240
: Ethernet layer 2
241
: STA bootstrap
242
: LDB bootstrap
243
: OMF86 loading through asynchronous link
244
: OMF processing function
245
: LDB CSP access cad
246
: Ethernet link access cad
PE/DCL/DD/0101
411--9001--101
247
: Disk I/O
248
: File management system
249
: Disk driver
250
: Mirror disk: services and user functions
251
: Mirror disk: state machine
252
: Mirror disk: transmission protocol
253
: Transport data link
254
: Data link layer
255
: Access to interconnection area
256
: Data transport layer
257
: Access to multibus II management coprocessor
258
: Switching matrix access and transmission protocol
259
: Switching matrix access
260
: Protocol transmission layer 1
261
: SUP card access management
262
: SCSI: bus management
263
: SCSI: units logical management
264
: SCSI: bus controler management
265
: SCSI: protocol management
266
: X25 layer 1 and 2
267
: HDLC handler
268
: LAPB layer 2
269
: FSM debug
270
: Tape drive management
271
: Disk/tape copy tools management
272
: Ethernet driver
273
: Ethernet driver
276
277
278
: Loader
279
: UC loader
Standard 15.101/EN
July 2005
280
: Data loader
281
: Remote SCO access loader
282
: Local SGF access loader
283
: C library
284
: Sympa station
285
: Load function
286
: State machine management
287
: Ethernet layer 2
288
: STA bootstrap
289
: LDB bootstrap
290
: OMF86 loading through asynchronous link
291
: OMF processing function
292
: LDB CSP access cad
293
: Ethernet link access cad
294
: SGF access problem
295
: Driver ram disk
296
: SGF access problem
297
: Driver ram disk
800
: Ethernet management IP
801
: Ethernet management UDP
802
: Ethernet management TCP
803
: Ethernet management RPC
804
: Ethernet management SNMP
805
: Ethernet management IP
806
: Ethernet management UDP
807
: Ethernet management TCP
808
: Ethernet management RPC
809
: Ethernet management SNMP
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--1
TCU FAULT NUMBERS

3.1
Fault number: 7
iii
Fault number:
7
: Card monitoring failure
FAULT ANALYSIS
This anomaly is sent to the BSC when a TCB2 or TDTI board is absent or faulty.
The following fields in the notification are useful to locate the boards:
the processor type
the processor number
the diagnosis

BSC defense
The BSC unconfigures the object concerned by the notification:
the pcmCircuit object corresponding to a TDTI board, and possibly the signallingLink
object (corresponding to the SS7 signaling channel on the A interface), and also the xtp
objects.
the transcoderBoard object corresponding to a TCB2 board, and also the xtp objects.
CAUTION
Service reduction
The service is reduced.
Vol. 1 -- 3--2
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
1
Action
Identify the equipment concerned by the notification.
If a TCB2 board is concerned, go to step 2.
If a TDTI board is concerned, go to step 3.
Check the state of the TCB2 board concerned, by performing a Display all
command on the transcoderBoard object concerned. The instance of the
transcoderBoard object concerned is given in the notification.
If the operationalState of the transcoderBoard object is enabled, the fault is not
confirmed. Clear the alarm. Go to step 13.
If the operationalState of the transcoderBoard object is disabled, the TCB2
board concerned is not operational yet. Wait for the end of the software
downloading.
If the operationalState of the transcoderBoard object is disabled, and the
availabilityStatus is dependency, look for a problem on one of the parent
objects (either transcoder object, or ladpLink object, or bsc object, or pcmCircuit
(pcmA) object).
availabilityStatus is failed, the TCB2 board is faulty. Go to step 5.
Check the state of the TDTI board concerned, by performing a Display all
command on the transcoder object concerned. The processor type given in the
notification is TDTI.
If the operationalState of the transcoder object is enabled, check which TDTI
board is concerned by the notification.
If the TDTI board 0 is concerned, the fault is not confirmed. Clear the alarm.
Go to step 13.
If another TDTI board is concerned, check the state of the pcmCircuit object.
Go to step 4.
If the operationalState of the transcoder object is disabled, the TDTI board

concerned is not operational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is disabled, and the
objects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object),
or look for a fault number 1157 Loss of TCU remote layer 2.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--3
Action (Continued)
pcmCircuit object (pcmA).
objects (either transcoder object, or ladpLink object, or bsc object).

Step
5
Action
Check the value of the diagnosis field in the notification.
If the diagnosis value is no board, a TCB2 board must be installed. Go to step
9.
If the diagnosis value is negative self--test , the TCB2 board must be
If the diagnosis value is negative TCB hardware version check, check the
value of the hardwareRef parameter by performing a Display command on
the transcoderBoard object.
If the value of the hardwareRef parameter is the same as the PROM
number of the TCB2 board concerned, there is a problem with the board. Go
to step 9.
If the value of the hardwareRef parameter is different from the PROM
number of the TCB2 board concerned, change the value of the

hardwareRef parameter. Then go to step 11.
Check the value of the transcoderIntPcmIntstate parameter by performing a

Display all command on the transcoder object.
If the value of the parameter is working, clear the alarm and look for a
problem on the PCM link, on site. Go to step 7.
If the value of the parameter is faulty, the TDTI board must be replaced. Go
to step 10.
Vol. 1 -- 3--4
TCU fault numbers
Step
Action (Continued)
Check the state of the children objects (transcoder and transcoderBoard) by

performing a Display all command.
If the operationalState of the objects is enabled, go to step 8.

If not, there is a problem with the PCM link. Call the transmission operator.
On site, put the jumpers on the TDTI board front panel in Local loopback position
(LP). For more information, refer to NTP < 42 >.
If the LFA, AIS, RRA, NOS, FE, SKP, and CRC LEDs are on, the TDTI board
must be replaced. Go to step 10.
If the LEDs are off, the problem does not lie with the TDTI board, but with the
PCM link. Call the transmission operator.
Replace the TCB2 board (Field Replaceable Unit):
a. Set the transcoderBoard object (corresponding to the TCB2 board to be

replaced) to locked. The instance of the object is given in the notification.
b. Refer to the replacement procedure given in NTP < 42 > for TCB2.
c. Set the transcoderBoard object to unlocked. Then go to step 11.
Replace the TDTI board (Field Replaceable Unit):
10
a. Set the pcmCircuit object (corresponding to the TDTI board to be replaced and
to the PCM link between the BSC and the TCU, or the TCU and the MSC) to
locked. If necessary, set the pcmCircuit object (corresponding to the second
PCM link associated with this board) to locked too. The instance of the objects
is given in the notification.
b. To replace the TDTI board, refer to the replacement procedure given in
NTP < 42 >.
c. Set the pcmCircuit object(s) to unlocked. Then go to step 11.
Additional checks
Step
11
Action
Check the alarm state in the Current alarm list window at the OMC--R.
12
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--5
Action (Continued)

to step 13.
13
Clear the alarm manually.
14
Vol. 1 -- 3--6
TCU fault numbers
3.2
Fault number: 8
iii
Fault number:
8
: Negative built in self test result for card
FAULT ANALYSIS
This anomaly is sent to the BSC when a TCB2 board does not execute its self--tests
correctly.
The type and number of the board are specified in the notification.

BSC defense
The BSC unconfigures the transcoderBoard object corresponding to the TCB2 board, and
also the xtp objects.
CAUTION
Service reduction
FAULT TREATMENT
Preliminary checks
Step
1
Action
command on the transcoderBoard object concerned. The instance of the
transcoderBoard object concerned is given in the notification.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--7
Step
2
Action
b. Note the values of the notification additional fields (if any), and give them to the
manufacturer with the faulty board.
c. Refer to the replacement procedure given in NTP < 42 >.
d. Set the transcoderBoard object to unlocked. Then go to step 3.
Additional checks
Step
3
Action
Check the state of the replaced TCB2 board, by performing a Display all command
on the transcoderBoard object concerned.
If the operationalState of the transcoderBoard object object is enabled, the
fault is not confirmed. Go to step 5.
If the operationalState of the transcoderBoard object object is disabled, and
the availabilityStatus is failed, call the manufacturer.
Clear the alarm.
Vol. 1 -- 3--8
TCU fault numbers
3.3
Fault number: 47
iii
Fault number:
47
: Cessation of active alarms
Type : communicationsAlarm, environmentalAlarm,
equipmentAlarm,
processingErrorAlarm, qualityOfServiceAlarm
FAULT ANALYSIS
The notification is sent during a TCU restart. It indicates that active alarms are automatically
cleared. It concerns the transcoder object.
If the anomaly that triggered these alarms is still present after the TCU restart, new alarms
will be generated at the OMC--R. Thus, no information is lost.
The notification concerns one of these alarm type:
communicationsAlarm
environmentalAlarm
equipmentAlarm
processingErrorAlarm
qualityOfServiceAlarm
There are three types of alarm clearing:
The purge performed by the BSC consists in clearing the alarms linked to the
notifications. The BSC thus indicates that it is purging the notifications that have not
been sent to the OMC--R yet.
The defense purge performed by the MD consists in clearing the oldest notifications.
The threshold is fixed by the static configuration.
The daily purge performed by the MD consists in clearing the notifications that are older
than N days, every day. N is fixed by the static configuration.
The type of alarm clearing is displayed in the probableCause field of the notification (see
the following table).
probableCause No.
probableCause wording
Type of alarm clearing
64
bscRequest
Purge performed by the BSC
65
purgeOnSaturation
Defense purge
66
dailyPurge
Daily purge

BSC defense
None.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--9

None.
FAULT TREATMENT
Vol. 1 -- 3--10
TCU fault numbers
3.4
Fault number: 493

iii
Fault number:
493 : Failure on one of the TCUs clocking sources
FAULT ANALYSIS
This anomaly is sent to the BSC at each state change of a synchronizing clock supported
by a PCM of the A interface in service or by the external clock.
The state change of one of the reference clocks is detected by the TUC board, and it may
implicate one of the following:
the TUC board
the TDTI board
the external PCM
the external clock
The object and the instance in the alarm identify the suspected clock. The following objects
are concerned by this alarm:
the pcmCircuit object for the PCMs of the A interface
the transcoder object for the external clock

When there is a problem with the clock used for synchronization, the TUC board looks for
a new reference clock on one of the following items of equipment. The equipment is
selected in the following order:
the external clock as a priority, or
the clocks generated by enabled pcmCircuit objects, or
the clocks generated by disabled pcmCircuit objects, or lastly
the local clock
BSC defense
None.

None.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--11
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the external clock, by performing a Display all command on the
transcoder object concerned.
If the administrativeState of the transcoder object is locked, do not take the
alarm in account. Go to step 8.
If the operationalState of the transcoder object is enabled, go to step 2.
If the operationalState of the transcoder object is disabled, the TDTI board
concerned is not operational yet. Wait for the end of the software downloading.
objects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object),
or look for a fault number 1157 Loss of TCU remote layer 2. Clear the alarm.
Go to step 7.

Step
2
Action
This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.To
locate the fault, look for the following information:
an operator warning with the fault number 497 on the transcoder object to
identify the new reference clock with the value of the New PCM field
a beginning--of--fault with the fault number 1151 for the external PCM on the
A interface. Then treat the problem on the PCM link.
a beginning--of--fault with the fault number 7 for the TDTI boards. Then go to
step 3.
an operator action on the state of the external clock
Replace the TDTI board (Field Replaceable Unit):

a. Set the pcmCircuit object (corresponding to the TDTI board to be replaced and
to the PCM link between the BSC and the TCU, or the TCU and the MSC) to
locked.
b. To replace the TDTI board, refer to the replacement procedure given
in NTP < 42 >.
c. Set the pcmCircuit object(s) to unlocked. Then go to step 4.
Vol. 1 -- 3--12
TCU fault numbers
Additional checks
Step
Action
Check the network of transmission.
Check the alarm state in the Current alarm list window at the OMC--R.
to step 7.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
3.5
TCU fault numbers
Vol. 1 -- 3--13
Fault number: 497

iii
Fault number:
497 : New PCM selected as clock reference
FAULT ANALYSIS
By this notification, the TCU indicates the new internal PCM chosen as the new internal
reference clock.
The transcoder object is the managed object that detects this modification.
The previous clock and the new reference clock are specified in the PREVIOUS PCM and
NEW PCM fields of the notification.
The fields can take the following values:
Field value
Meaning
Explanation for
the NEW PCM field
internal clock
No synchronizing PCM is available,

so the local clock is selected (see
BSC defense below).
external clock
No PCM of the A interface can be

used as a reference clock.
The problem may implicate the MSC,
the PCM links of the A interface, the
TDTI boards, or the internal PCM
links.
clock from the pcmA object

no. 3

no. 1

no. 0
The TCU found a new reference clock

issued by a PCM of the A interface.
The previous synchronizing PCM was
faulty.

BSC defense
If the TCU now uses its local clock as a reference clock, the BSC cannot use this clock
anymore. So the BSC has to select another TCU whose reference clock is issued by a PCM
of the A interface. Then the BSC sends a fault number 497 to indicate its new reference
clock.

None.
Vol. 1 -- 3--14
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
Action
pcmCircuit objects (pcmA).
If the administrativeState of the pcmCircuit objects is locked, do not take the

confirmed. Clear the alarm. Go to step 6. Nevertheless, if the interruption lasted
less than five minutes, the operationalState remained enabled even though
there has been a problem. This problem is possibly associated with a PCM fault.
Refer to NTP < 105 >.
objects (either transcoder object, or ladpLink object, or bsc object).

Step
2
Action
Look for alarms or notifications concerning the following equipment:
pcmCircuit links
TDTI boards
internal PCMs
MSC
If there are alarms, treat them. Go to step 3.

If there are not any alarms, call the manufacturer.
3
Replace the equipment item(s) according to the other notifications:

a. Set the disabled--failed pcmCircuit (external PCM or TDTI problem) or
disabled--dependency pcmCircuit (internal PCM problem) to locked.
b. Replace the item(s) of equipment. For more information on the replacement of
the TDTI boards (Field Replaceable Unit), refer to the replacement procedure
in NTP < 42 >.
c. Set the pcmCircuit to unlocked.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--15
Additional checks
Step
4
Action
to step 6.
Clear the alarm.
Vol. 1 -- 3--16
TCU fault numbers
3.6
Fault number: 523

iii
Fault number:
523 : Fault on internal PCM (BSC, TCU)
FAULT ANALYSIS
The beginning of the fault indicates a negative cyclic test made on TS0 of one of the internal
PCMs.
The internal PCM is no longer operational.
FAULT TREATMENT
The maintenance procedure is described in NTP < 105 >.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
3.7
TCU fault numbers
Vol. 1 -- 3--17
Fault number: 1150

iii
Fault number:
1150 : Loss of DDTI configuration
FAULT ANALYSIS
This alarm indicates that a TDTI board lost its configuration.
The type and position of the board are specified in the notification.

BSC defense
The system isolates the TDTI board that has lost its configuration.
FAULT TREATMENT
Vol. 1 -- 3--18
TCU fault numbers
3.8
Fault number: 1151

iii
Fault number:
1151 : PCM transmission fault
FAULT ANALYSIS
This notification indicates a transmission problem with one of the PCM links.
The PCM number and the associated TDTI board are specified in the notification.
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
3.9
TCU fault numbers
Vol. 1 -- 3--19
Fault number: 1152

iii
Fault number:
1152 : PCM CRC attribute and DDTI CRC strap are not consistent
FAULT ANALYSIS
Note: For information on the 1152 alarm for the DDTI board, refer to
Paragraph 2.81.
This notification is sent by the BSC when an inconsistency is detected between the
hardware configuration of a TDTI board and the setting of the BSC.
The cRC attribute of the pcmCircuit object (transcoder -- A interface) does not match the
CS17 and CS18 jumpers configuration on the TDTI board.
This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.

The system isolates the TDTI board.
CAUTION
The service is reduced or lost, depending on the configuration.
Vol. 1 -- 3--20
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
Action
At the OMC--R, check the cRC attribute value by performing a Display command
on the pcmCircuit object.
If the cRC parameter value is used, go to step 2.

If the cRC parameter value is not used, set the pcmCircuit object to locked.
Set the cRC parameter to used. Set the pcmCircuit object to unlocked.
Then go to step 3.
Step
Action
On site, change the CS17 and CS18 jumpers on the TDTI board:
a. Set the pcmCircuit object to locked.

b. Change the CS17 and CS18 jumpers on the TDTI board (TDTI E1 -- GSM
900/1800) or (TDTI T1 -- GSM 1900). For more information on the jumper
positions, refer to NTP < 42 >.
c. Set the pcmCircuit object to unlocked. Then go to step 3.
Additional checks
Step
3
Action
Check the state of the equipment, by performing a Display all command on the
pcmCircuit object.
If the operationalState of the object is enabled, go to step 5.
If the operationalState of the object is disabled, call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
3.10
TCU fault numbers
Vol. 1 -- 3--21
Fault number: 1156

iii
Fault number:
1156 : TCU downloading failure
Type : equipmentAlarm/communicationsAlarm
FAULT ANALYSIS
The BSC tries to download the TCB2 software to the TUC board twice at the maximum.
This notification is issued when the software downloading from the TCB2 board to the TUC
board failed.
The Download Status field in the notification indicates the source of the failure:
0 = File access error
1 = Failure on the second attempt of downloading
The downloading failure can be due to:
a transient transmission problem
the configuration data (software release, etc.)
the BSC
the PCM link between the BSC and the TCU (DDTI board, PCM, and TDTI board)
the TCB2 board
FAULT TREATMENT
Vol. 1 -- 3--22
TCU fault numbers
3.11
Fault number: 1157

iii
Fault number:
1157 : Loss of TCU remote layer 2
FAULT ANALYSIS
The BSC detects a loss of layer 2 to the TCU and sends this alarm to the OMC--R. The TCU
is completely isolated until the restoration of layer 2.
The TUC board resets itself every 30 seconds, then it resets the TDTI board. The PCM link
is cut off.
This alarm can indicate a configuration problem:
TEI value
PROM version of the TUC board
This alarm can also implicate the following equipment items:
BSC
link between the BSC and the TCU
TUC board
FAULT TREATMENT
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
3.12
TCU fault numbers
Vol. 1 -- 3--23
Fault number: 1159

iii
Fault number:
1159 : Invalid message received on TCU--BSC interface
FAULT ANALYSIS
This warning notification is issued after a software fault.

BSC defense
None.
CAUTION
The service may be reduced, or even lost.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the state of the TCU, by performing a Display all command on the
transcoder object.
Vol. 1 -- 3--24
TCU fault numbers
Step
Action (Continued)
Look for other fault numbers 1159.
If the fault number 1159 is seldom emitted, it is a transient problem. Go to step 6.

If it is often emitted, call the manufacturer.
Look for other notifications concerning the TCU, and treat them. Then go to step 4.
Additional checks
Step
4
Action
to step 6.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
3.13
TCU fault numbers
Vol. 1 -- 3--25
Fault number: 1160

iii
Fault number:
1160 : TCU negative acknowledgment indication
FAULT ANALYSIS
This warning notification indicates a software anomaly or hardware fault.
The Source field can contain one of the following sources:
1 Downloading not expected
2 Block number out of window
3 Window out of range
4 Too many received blocks (number out of range)
5 Unknown file reference
6 Downloading already running
7 Unknown nature for downloading stop
64 TCU connection refusal
65 PCMA/TCB init or desinit refusal
74 Timer expiration: init/desinit TCB/PCMA
80 Timeout on reset timer, or init dialog timer
81 Timeout on downloading timer
82 Timeout on init/desinit/read PCMA or TCB
83 Timeout on connection timer
84 Mark block out of sequence, or timeout on mark timer

BSC defense
None.
Vol. 1 -- 3--26
TCU fault numbers

If there is a software downloading problem (source 1 to 7), the operationalState of the
transcoder object remains disabled.
CAUTION
FAULT TREATMENT
Preliminary checks
Step
Action
transcoder object.

Look for other notifications concerning the TCU, and treat them. Then go to step 3.
Additional checks
Step
3
Action
to step 5.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
3.14
TCU fault numbers
Vol. 1 -- 3--27
Fault number: 1163

iii
Fault number:
1163 : Preemption of a terrestrial circuit by a signalling link
FAULT ANALYSIS
The BSC reserves four terrestrial circuits to support a CCS7 or X25 signaling link to the
MSC through the TCU. This action results in the transmission of four notifications and the
switching off of four LEDs of a TCB2 board, which no longer receives the data carried by
this time slot of the PCM of the Ater interface.
The fault number 1163 is sent when a signallingLink object is set to unlocked or locked,
without the terrestrial circuits (carried by the TCB2 0 board) being put out of service first.

BSC defense
None.

None.
FAULT TREATMENT
No maintenance operation is required.
The alarms stop when the corresponding terrestrial circuits are put out of service.
Vol. 1 -- 3--28
TCU fault numbers
3.15
Fault number: 1165

iii
Fault number:
1165 : iiiVAL_STP_ANO_TRC_BLOCKED
Type : processingError
FAULT ANALYSIS
The PCMA contains at least one hscsd blocked terrestrial circuit. This notification is
generated when a first terrestrial circuit of a PCMA is preempted for HSCSD, and when the
last preempted terrestrial circuit of PCMA is unblocked.

BSC defense
None.

None.
FAULT TREATMENT
No maintenance operation is required.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
3.16
TCU fault numbers
Vol. 1 -- 3--29
Fault number: 1170

iii
Fault number:
1170 : External alarm loop on TCU
FAULT ANALYSIS
By this alarm, the TCU indicates the state change of the external alarm.
This alarm can be configured by the operator.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
Check the value of the transcoderAlarmMask parameter, by performing a Display
all command on the transcoder object.
If the external alarm is configured, go to step 2.
If the external alarm is not configured, configure it by performing a set
command on the transcoder object. Then go to step 3.
Vol. 1 -- 3--30
TCU fault numbers
Step
Action
Perform the appropriate treatment. The operation to be executed to clear this type
of alarm depends on the alarm loop configuration defined by the operator. Then go
to step 3.
Additional checks
Step
PE/DCL/DD/0101
411--9001--101
Action
Check that an end--of--alarm notification is generated when the alarm is cleared.
Standard 15.101/EN
July 2005
3.17
TCU fault numbers
Vol. 1 -- 3--31
Fault number: 1171

iii
Fault number:
1171 : TCU power fault
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of a power supply unit.
The alarm indicates:
the object that detected the anomaly: the TUC board
the type of fault: TCU power fault
But this alarm does not indicate which power supply unit is faulty.

BSC defense
None.

None, if only one power supply unit is faulty.
Vol. 1 -- 3--32
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
Action
If the operationalState of the transcoder object is enabled, clear the alarm. Go

to step 9.
If the operationalState of the transcoder object is disabled, the TCU is not
operational yet. Wait for the end of the software downloading.
objects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
availabilityStatus is failed, one or several power supply units are faulty. Go to
step 2.
Step
2
Action
Perform an electrical test on the power supply units:
a. Locate the power supply units (PSU) in the shelf of the TCU cabinet.
b. Put the multimeter in DC voltage mode.
c. Perform the following test on each power supply unit:
i.
Connect the V terminal of the multimeter to the red 5V terminal, and the
COM terminal of the multimeter to the blue 5V terminal (see NTP < 42 >).
ii.
Check that the voltage measurement is 5.2V (2%).

If the voltage is not correct, go to step 3.
Check the fuse of the power supply unit

a. Switch off the faulty power supply unit.
b. Locate the 4A fuse on the front panel of the power supply unit (see NTP < 42 >).
c. Extract the fuse using a screwdriver.
d. Check the fuse with the multimeter.
If the fuse is operational, the power supply unit is out of order and it must be
If the fuse is not operational, it must be replaced. Go to step 4.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--33
Action (Continued)
Replace the fuse of the power supply unit:

a. Insert a new fuse.
b. Switch on the power supply unit.
c. Go to step 7.
Replace the faulty power supply unit (Field Replaceable Unit)

Additional checks
Step
7
Action
to step 9.
failed, call the manufacturer. Go to step 6.
Clear the alarm.
10
Vol. 1 -- 3--34
TCU fault numbers
3.18
Fault number: 1172

iii
Fault number:
1172 : TCU fan board fault
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of the VENT board.
the object that detected the anomaly: the TUC board
the type of fault: TCU fan board fault

BSC defense
None.

None.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--35
FAULT TREATMENT
Preliminary checks
Step
1
Action
to step 9.
availabilityStatus is failed, there is a problem with the VENT board. Go to
step 2.
Step
2
Action
Safety instructions
CAUTION
Wear the antistatic bracelet when performing the following
maintenance procedure, especially when handling boards.
3
Check the power supply fuse (on the terminal block):

a. Open the mobile frame of the TCU cabinet.
b. Locate the terminal block at the bottom of the cabinet.
c. Locate the power supply fuse on the terminal block (see NTP < 42 >).
d. Extract the fuse.
e. Check it with a multimeter.
If the fuse is not operational, replace the fuse. Go to step 5.
Vol. 1 -- 3--36
TCU fault numbers
Step
Action (Continued)
Check the fuse of each faulty fan (on the VENT board)

b. Locate the VENT board on the side of the mobile frame.
c. Locate the fuses (see NTP < 42 >).
d. Remove the board plastic cover.
e. Check the fuse(s) with a multimeter.
If the fuse(s) is/are operational, there is a problem with the VENT board. Go
to step 6.
If one or several fuses are not operational, replace it/them. Go to step 5.
Replace the fuse
If the fuse is located on the terminal block, replace it. Then go to step 7.
If the fuse is located on the VENT board, replace it according to the corrective
maintenance procedure (see NTP < 42 >). Then go to step 7.
Replace the VENT board. Then go to step 7.
Additional checks
Step
7
Action
to step 9.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
10
Standard 15.101/EN
July 2005
3.19
TCU fault numbers
Vol. 1 -- 3--37
Fault number: 1173

iii
Fault number:
1173 : TCU fan fault
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of one or more fans.
the object that detected the anomaly, i.e. the TUC board
the type of fault: TCU fan fault

BSC defense
None.

None.
Vol. 1 -- 3--38
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
Action

to step 10.
availabilityStatus is failed, one or several fans are faulty. Go to step 2.
Step
2
Action
Safety instructions
CAUTION
Wear the antistatic bracelet when performing the following
maintenance procedure, especially when handling boards.
Check how many fans are stopped in the ventilation block.

If all the fans in one ventilation block are not running, check the fuse of the VENT
board corresponding to this ventilation block. The fuse is located on the terminal
block. Go to step 4.
If one or two fans in one ventilation block are not running, check the fuse of each
faulty fan. The fuses are located on the VENT board. Go to step 5.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--39
Action (Continued)
Check the fuse of the VENT board (on the terminal block)
b. Locate the terminal block at the bottom of the cabinet.
c. Locate the fuse of the VENT board on the terminal block (see NTP < 42 >).
d. Extract the fuse.
e. Check it with a multimeter.
If the fuse is operational, replace the ventilation block. Go to step 7.
If the fuse is not operational, replace the fuse. Go to step 6.
Check the fuse of each faulty fan (on the VENT board)
b. Locate the VENT board on the side of the mobile frame (see NTP < 42 >).
c. Locate the fuse of the faulty fan, using the following table and NTP < 42 >).
Fuse
Value
(GSM 900/1800)
Value
(GSM 1900)
Left
F1
0.63 A
0.8 A
Middle
F3
0.63 A
0.8 A
Right
F5
0.63 A
0.8 A
Fan (Note)
Note:
when looking at the front of the ventilation block.
d. Remove the board plastic cover.

e. Check the fuse with a multimeter.
If the fuse is operational, there is a problem with the ventilation block. Go to
step 7.
If the fuse is not operational, replace it. Go to step 6.
6
Replace the fuse

If the fuse is located on the terminal block, replace it. Then go to step 8.
If the fuse is located on the VENT board, replace it according to the corrective
maintenance procedure (see NTP < 42 >). Then go to step 8.
Replace the ventilation block (Field Replaceable Unit)
Vol. 1 -- 3--40
TCU fault numbers
Step
Action (Continued)
a. Replace the ventilation block that has (a) faulty fan(s) according to the corrective
maintenance procedure (see NTP < 42 >).
Additional checks
Step
8
Action
to step 10.
PE/DCL/DD/0101
411--9001--101
10
Clear the alarm.
11
Standard 15.101/EN
July 2005
3.20
TCU fault numbers
Vol. 1 -- 3--41
Fault number: 1174

iii
Fault number:
1174 : TCU clock fault
FAULT ANALYSIS
This alarm indicates a clock problem. The PLL of the TUC board is stopped.
The alarm indicates the TUC board that is responsible for the anomaly.
However, the synchronizing PCM link can be faulty too.

BSC defense
If the BSC is synchronized by this TCU, the BTSs clock will drift.
CAUTION
Then the service is lost, or at least there are handover problems
(intra BTS and inter BTS as well).
Vol. 1 -- 3--42
TCU fault numbers
FAULT TREATMENT
Preliminary checks
Step
Action
Check the state of the TCU by performing a Display all command on the

to step 8.
availabilityStatus is failed, the TCU clock is faulty. Go to step 2.

Step
2
Action
Identify the synchronizing PCM link:
a. Look at the synchronization LEDs on the front panel of the TUC board (see
NTP < 42 >).
b. Change the position of the jumpers on the TDTI board front panel to perform a
PCM link switchover. For more information, refer to NTP < 42 >.
c. Check that the alarm has disappeared, by performing a Display all command
on the transcoder object.
If the alarm has disappeared, the problem lies with the PCM link, or with the
TUC board.
If the alarm has not disappeared, change the position of the jumpers on the
TDTI board front panel to perform another PCM link switchover.
If the problem does not lie with the TUC board, the external clock (if there is
one), or the MSC may be faulty, or there is a general problem on all the PCM
links.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--43
Action (Continued)
Check the clock of the selected PCM.

If the PCM is suspected, repair the PCM link. Go to step 4.
If not, replace the TUC board. Go to step 5.
Repair the PCM link.
Replace the TUC board (Field Replaceable Unit):

a. Perform a shutting down on all the xtp objects of the TCU.
b. At the OMC--R, set the transcoder object mentioned in the alarm to locked.
c. On site, to replace the TUC board, refer to the replacement procedure given in
NTP <41>.
d. At the OMC--R, set the transcoder object mentioned in the alarm to unlocked.
Then go to step 6.
Additional checks
Step
6
Action
to step 8.
Clear the alarm.
Vol. 1 -- 3--44
TCU fault numbers
3.21
Fault number: 1180

iii
Fault number:
1180 : TCB downloading failure
FAULT ANALYSIS
This notification indicates that the TCB2 software downloading failed.
The TUC board makes a maximum of two downloading attempts. If the second attempt
fails, the TUC board informs the BSC.
The TCB2 board concerned is specified in the beginning--of--fault notification.
The additional field in the notification indicates the downloading state of the TCB2 board.
The field can take the following values:
1 Failure on the second attempt of downloading
2 No layer 1 synchronization for downloading

BSC defense
None.

The xtp objects cannot be used any more.
CAUTION
Service reduction
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--45
FAULT TREATMENT
Preliminary checks
Step
1
Action
to step 11.
availabilityStatus is failed, the TCB software downloading failed. Go to step 2.

Step
2
Action
Look at the additional field of the notification:
If the value is Failure on the second attempt of downloading, go to step 3.
If the value is No layer 1 synchronization for downloading, go to step 6.
Check the homogeneity of TCB2 boards in the shelf concerned.

If the TCB2 boards are homogeneous, go to step 4.
If the TCB2 boards are heterogeneous, replace the heterogeneous one(s). Go
to step 7.
Check the version of the software to be installed on this TCB board in relation to
the PROM version:
a. Check the value of the hardwareRef parameter by performing a Display
command on the transcoderBoard object.
If the value of the hardwareRef parameter is the same as the PROM

number of the TCB2 board concerned, go to step 4b.
If the value of the hardwareRef parameter is different from the PROM
number of the TCB2 board concerned, change the value of the

hardwareRef parameter. Then go to step 9.
Vol. 1 -- 3--46
TCU fault numbers
Step
Action (Continued)
b. Check the value of the sWVersionRunning parameter by performing a Display

command on the software object associated with the transcoderBoard object.
If the value of the sWVersionRunning parameter is consistent with the
required software release (see the operator software release documents),
then there is a problem with the TCB software itself. Go to step 5.
If the value of the sWVersionRunning parameter is not consistent with the
required software release, modify the sWVersionRunning parameter
accordingly.
5
Check that the TCB software is installed in the OMC--R:

a. In the OMC--R Browser window, select the md object.
b. Select the List option in the EFT submenu of the Configuration menu. The list
of the EFTs installed in the OMC--R is then displayed in a Session Log window.
If the TCB software is installed in the OMC--R:
i.
Download it again on the BSC disk. For more information, refer to NTP 34.
ii.
Then, set the transcoderBoard object to unlocked to trigger the software

downloading in the board itself.
If the software problem disappeared, go to step 9.
If there is still a software problem, replace the TCB2 board. Go to
step 7.
If the TCB software is not installed in the OMC--R:
i.
Install it on the OMC--R. For more information, refer to NTP 34 .
ii.
Then download it on the BSC disk. For more information, refer to NTP 34.
iii.
Then, set the transcoderBoard object to unlocked to trigger the software

downloading in the board itself.
If the software problem disappeared, go to step 9.
If there is still a software problem, replace the TCB2 board. Go to
step 7.
Check that there are no alarms concerning the internal PCM links between the TUC
board and the TCB2 board (fault number 523 Fault on internal PCM (BSC, TCU)).
If the problem does not concern the internal PCM links, go to step 7.
If there are alarms concerning the internal PCM links, refer to NTP < 105 >. Go
to step 12.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--47
Action (Continued)
a. Set the transcoderBoard object to locked.

b. Replace the TCB2 board. For more information, refer to the replacement
procedure given in NTP < 42 >.
c. Set the transcoderBoard object to unlocked.
If there is still a software downloading problem, go to step 8.
If the software downloading problem has disappeared, go to step 9.
8
Replace the TUC board (Field Replaceable Unit)

a. Set the transcoder object to locked.
b. Replace the TUC board. For more information, refer to the replacement
procedure given in NTP < 42 >.
c. Set the transcoder object to unlocked. Then go to step 9.
Additional checks
Step
9
Action
10
to step 11.
11
Clear the alarm.
12
Vol. 1 -- 3--48
TCU fault numbers
3.22
Fault number: 1184

iii
Fault number:
1184 : Internal TCB--2 failure
FAULT ANALYSIS
The TCB2 board informs the TUC board of a serious anomaly on one or more SPUs. The
TUC board resets the TCB2 board.

BSC defense
None.
CAUTION
Service reduction
FAULT TREATMENT
Preliminary checks
Step
1
Action
command on the transcoderBoard object concerned.
downloading.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Step
TCU fault numbers
Vol. 1 -- 3--49
Action (Continued)

(pcmA) object).

Step
2
Action
b. Refer to the replacement procedure given in NTP < 42 >.
Additional checks
Step
3
Action
confirmed. Go to step 5.
availabilityStatus is failed, call the manufacturer.
Clear the alarm.
Vol. 1 -- 3--50
TCU fault numbers
3.23
Fault number: 1185

iii
Fault number:
1185 : TCB--2 synchronization failure
FAULT ANALYSIS
The TCB2 board informs the TCU board of a synchronization failure on the Ater interface
and/or the Abis interface (uplink, from the BTS to the TCB2 board).
This fault number indicates the number of loss of synchronization from the same TCB2
board.
The alarm indicates a transient problem on a PCM link that is not supervised by the BSC
or the BTS.

BSC defense
None.
CAUTION
Service reduction
The service quality is reduced.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--51
FAULT TREATMENT
Step
1
Action
Look for an alarm concerning the PCM link (Abis or Ater), and the BTS.
If there are alarms, refer to NTP < 105 >.
If there is no alarm on the PCM link (Abis or Ater) or the BTS, go to step 2.
Check the continuity of the links between the BSC and the BTS:
the operation of the BTS (btsSiteManager and transceiverEquipment objects)
the link between the BSC and the BTS
the operation of the BSC
the link between the BSC and the TCU
the TUC and/or the TCB board of the TCU
If there is a problem with one of these items of equipment, treat it. Then go
to step 3.
If all the items of equipment are operational, call the manufacturer.
Additional checks
Step
3
Action
Vol. 1 -- 3--52
TCU fault numbers
3.24
Fault number: 1186

iii
Fault number:
1186 : External TCB--2 failure
FAULT ANALYSIS
The TCB2 board receives a type of frame that cannot be decoded and informs the TUC
board.
The TCB2 board returns an external anomaly and indicates the TRAUs in fault.
It is usually a transient transmission fault.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
command on the transcoderBoard object concerned.
downloading.
(pcmA) object).
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--53

Step
2
Action
replaced) to locked.
b. Refer to the replacement procedure given in NTP < 42 >.
Additional checks
Step
3
Action
confirmed. Go to step 5.
availabilityStatus is failed, call the manufacturer.
Clear the alarm.
Vol. 1 -- 3--54
TCU fault numbers
3.25
Fault number 1190

iii
Fault number:
1190 : Restart after TCU suicide
FAULT ANALYSIS
When this message is displayed at the OMC--R, the link between the BSC and the TCU
(TUC board) is restored.
If there is a hardware problem, other beginning--of--fault alarms are present.

BSC defense
None.
CAUTION
Service reduction
Some communications were lost during the TCU suicide.
FAULT TREATMENT
Step
1
Action
Search for the source of the restart
If there are alarms indicating a hardware problem, treat them. Then go to step 2.
If this fault number 1190 is often emitted, call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--55
Additional checks
Step
2
Action
Check the notification state in the Current alarm list window.
If the notification has disappeared, go to step 5.
If the notification persists, go to step 3.
Check the state of the TCU, by performing a Display all command on the object
concerned.
to step 4.
Clear the notification.
Vol. 1 -- 3--56
TCU fault numbers
3.26
Fault number 1290

iii
Fault number:
1290 : Unacknowledged message on a interface
FAULT ANALYSIS
This user message describes one of the following two situations:
The MSC did not answer after the BSC tried twice to send the same message on the
A interface.
The MSC answered to the BSC, but the BSC could not understand the message. In the
latter case, two fault numbers 1310 (A interface protocol error indication) are emitted.
The message type field indicates the GSM coding of the message that was repeated by
the BSC on the A interface without being acknowledged by the MSC:
Reset circuit
Block
Unblock
Circuit group block
Circuit group unblock
The Circuit Identity Code field contains the CIC coded number declared at the BSC level
but unknown to the MSC.

BSC defense
None. The TMG does not use these channels.

The communication cannot be established on the considered channels.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--57
FAULT TREATMENT
Step
1
Action
Search for the reason why there is such an inconsistent configuration.
If it was configured this way on purpose, to prepare a network extension for
instance, this fault number emission is normal, and no maintenance is required.
Go to step 3.
If it was not configured this way on purpose, then there is an error in the
configuration. Go to step 2.
Correct the inconsistent configuration in one of the following ways:

At the OMC--R, delete the CIC indicated in the notification, OR
At the OMC--S, create the equivalent CIC for the MSC.
Additional checks
Step
3
Action
concerned.
to step 4.
Vol. 1 -- 3--58
TCU fault numbers
3.27
Fault number 1310

iii
Fault number:
1310 : A interface protocol error indication
FAULT ANALYSIS
This warning notification is caused by a software anomaly on the A interface and the MSC.
The BSC receives an unknown message from the MSC. Most often there is an
incompatibility between what the MSC sends and what the BSC knows.
The Source field of the notification can contain the following values:
10 --Unknown CIC (in this case, data length (lg_data) = 2, and the received CIC which
is incorrect is dumped. This dump is in hexadecimal representation and appears in a
form similar to 0x0799).
26 --Unknown IEI
27 --Bad length of element
51 --Unknown message in this way
52 --Too short reserved length -- imperative reserved area
53 --Minimum length not respected
54 --Unknown message type
55 --Unknown message group
65 --Essential element missing
66 --Wrong mandatory element
The MSC version is incompatible with the BSC.
The Circuit Identity Code field contains the CIC coded number declared at the MSC level
but unknown to the BSC. This is true for all of the 1310 fault.

BSC defense
None. The TMG does not use these channels.

The communication cannot be established on the considered channels.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
TCU fault numbers
Vol. 1 -- 3--59
FAULT TREATMENT
Step
1
Action
Look at the source given in the Source field of the notification.
If the source is 10 Unknown CIC, go to step 2.
If the source is 26, 27, 51, 52, 53, 54, 55, 65, or 66, it is a transient
problem. If this notification is often emitted, call the manufacturer.
Search for the reason why there is such an inconsistent configuration.

If it was configured this way on purpose, to prepare a network extension for
instance, this fault number emission is normal, and no maintenance is required.
Go to step 4.
If it was not configured this way on purpose, then there is an error in the
configuration. Go to step 3.
Correct the inconsistent configuration in one of the following ways:

At the OMC--S, delete the CIC indicated in the notification, OR
At the OMC--R, create the equivalent CIC for the BSC, and the xtp objects as
well.
Additional checks
Step
4
Action
concerned.
to step 6.
Vol. 1 -- 3--60
TCU fault numbers
3.28
Fault number 1311

iii
Fault number:
1311 : Reset downlink
FAULT ANALYSIS
This warning notification indicates a state change of the traffic state of the MSC.
The possible values of the MSC traffic state field are:
0 = MSC traffic opened
1 = MSC traffic closed

BSC defense
None.

When the value of the MSC traffic state is MSC traffic closed, no communication can
be established.
CAUTION
FAULT TREATMENT
This is a transient message. As soon as the A interface is operational, another message
1311 is sent, with MSC traffic opened in the MSC traffic state field.
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
3.29
TCU fault numbers
Vol. 1 -- 3--61
Fault number 1363

iii
Fault number:
1363 : SCCP protocol error indication
FAULT ANALYSIS
The problem lies in the A interface and the MSC. Most often, it is a transient problem.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
If this notification 1363 is often emitted, check the state of the SS7 signaling
channel, by performing a Display all command on the signallingLink object
concerned.
If the operationalState of the signallingLink object is enabled, the fault is not
If the operationalState of the signallingLink object is disabled, and the
availabilityStatus is failed, there is a problem with the SS7 signaling channel.
Go to step 2.

Step
2
Action
Look for alarms concerning the signallingLink object, and concerning the MSC as
well. Treat them and then go to step 3.
Vol. 1 -- 3--62
TCU fault numbers
Additional checks
Step
3
Action
If the alarm persists, call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
3.30
TCU fault numbers
Vol. 1 -- 3--63
Fault number 1364

iii
Fault number:
1364 : MTP3 protocol error indication
FAULT ANALYSIS
The problem lies in the A interface and the MSC. Most often it is a transient problem.

BSC defense
None.

None.
FAULT TREATMENT
Preliminary checks
Step
1
Action
If this notification 1364 is often emitted, check the state of the SS7 signaling
channel, by performing a Display all command on the signallingLink object
concerned.
If the operationalState of the signallingLink object is enabled, the fault is not
If the operationalState of the signallingLink object is disabled, and the
availabilityStatus is failed, there is a problem with the SS7 signaling channel.
Go to step 2.

Step
2
Action
Look for alarms concerning the signallingLink object, and concerning the MSC as
well. Treat them and then go to step 3.
Vol. 1 -- 3--64
TCU fault numbers
Additional checks
Step
3
Action
If the alarm persists, call the manufacturer.
PE/DCL/DD/0101
411--9001--101
Clear the alarm.
Standard 15.101/EN
July 2005
Index
Vol. 1 -- i
B
BSC 12000
5 Restart after chain suicide due to internal cause, or OMC, Vol. 1 -- 2--1
Source (0) Software anomaly counter threshold, Vol. 1 -- 2--4
Source (1) CPUE (MPU) non present, Vol. 1 -- 2--5
Source (2) CPUE (MPU) or CPUM (OMU) built--in self test failed, Vol. 1 -- 2--7
Source (3) CPUE (MPU) or CPUM (OMU) setup failed , Vol. 1 -- 2--9
Source (4) Incorrect Multibus II card name, Vol. 1 -- 2--11
Source (5) No communication with CPUE (MPU) card, Vol. 1 -- 2--13
Source (8) Error in BSC state machine handler (GAUT), Vol. 1 -- 2--15
Source (10) Error in switchover sequence, Vol. 1 -- 2--16
Source (11) BDA KO during switchover sequence, Vol. 1 -- 2--17
Source (12) Invalid mirror partitions after switchover on the new active chain, Vol. 1 -- 2--18
Source (14) Loss of duplex link detected on passive chain, Vol. 1 -- 2--19
Source (15) Inconsistency between active and passive chains, Vol. 1 -- 2--20
Source (16) Context overflow for BSC (MDB) defense, Vol. 1 -- 2--21
Source (20) Switching while passive chain DP loading, Vol. 1 -- 2--22
Source (21) Error detected during check partition, Vol. 1 -- 2--23
Source (23) CPUE BOOT flashing failed, Vol. 1 -- 2--24
Source (24) Restart to take into account the new BSC customization, Vol. 1 -- 2--25
Source (25) Degraded disk, Vol. 1 -- 2--26
Source (27) Cancellation of probative phase, Vol. 1 -- 2--28
Source (28) End of probative phase OK, Vol. 1 -- 2--29
Source (29) New BDA edition, Vol. 1 -- 2--30
Source (30) Preparation of a type 5 upgrade, Vol. 1 -- 2--31
Source (31) Type 5 upgrade running, Vol. 1 -- 2--32
Source (32) Old release running on passive chain, Vol. 1 -- 2--33
Source (33) Unsuccessful preparation of a type 5 upgrade, Vol. 1 -- 2--34
Source (50) BDA inconsistency, Vol. 1 -- 2--35
Source (51) GES--MS / GES--SL are incoherent, Vol. 1 -- 2--37
Source (52) Passive chain does not answer on RGA request, Vol. 1 -- 2--38
Source (53) Passive chain suicide on RGA request, Vol. 1 -- 2--39
Source (101) No communication with switching board, Vol. 1 -- 2--40
Source (102) No communication with ECI card or fault on ECI card, Vol. 1 -- 2--42
Source (103) No communication with SICX card or fault on SICX card, Vol. 1 -- 2--45
Source (104) No communication with slave switching board, Vol. 1 -- 2--47
Source (105) No communication with SLS card or fault on SLS card, Vol. 1 -- 2--49
Source (106) Operator request, Vol. 1 -- 2--51
Source (107) Degraded REM link, Vol. 1 -- 2--52
Source (128) No communication with SICD or RCB card or fault on SICD or RCB card, Vol. 1 -- 2--53
Source (129) SICD port selftests not OK, Vol. 1 -- 2--56
Source (161) No communication with CCS7 card or fault on CCS7 card, Vol. 1 -- 2--58
Source (162) CCS7 port selftests not OK, Vol. 1 -- 2--60
Source (176) No communication with TCU card or fault on TCU card, Vol. 1 -- 2--62
Source (192) O&M bus selftests not OK, Vol. 1 -- 2--65
6 Restart after chain suicide due to trap, Vol. 1 -- 2--67
7 Card monitoring failure, Vol. 1 -- 2--68
8 Negative built in self test result for card, Vol. 1 -- 2--72
11 Restart after chain suicide due to NMI, Vol. 1 -- 2--74
13 Chain restart in progress, Vol. 1 -- 2--78
14 Indication of chain restart cause, Vol. 1 -- 2--79
15 Chain restart due to intermediate card, Vol. 1 -- 2--80
16 Fault on active/passive chains link, Vol. 1 -- 14--83
Vol. 1 -- ii
Index
20 Alarm on clockship of the SUP board, Vol. 1 -- 14--85

21 Beginning of circular file pre--overflow, Vol. 1 -- 14--87
22 End of circular file pre--overflow, Vol. 1 -- 14--89
23 Beginning of BSC disk partition update, Vol. 1 -- 14--90
24 End of BSC disk partition update, Vol. 1 -- 14--91
26 Fault on BSC/OMC--R link, Vol. 1 -- 14--92
33 Saturation on an internal file used for marking climb, Vol. 1 -- 14--93
34 Saturation on a storage zone for marking climb, Vol. 1 -- 14--94
41 Beginning of saturation of the event reporting process in the BSC, Vol. 1 -- 14--95
42 End of saturation of the event reporting process, Vol. 1 -- 14--99
43 Loss of access to the equipment shelf, Vol. 1 -- 14--100
Source (0) Cannot access to all working UTE, Vol. 1 -- 14--101
Source (1) O&M bus selftest not OK, Vol. 1 -- 14--103
44 Board UTE access problem, Vol. 1 -- 14--105
45 Partial hard disk degradation, Vol. 1 -- 14--107
46 Total hard disk degradation, Vol. 1 -- 14--111
47 Cessation of active alarms, Vol. 1 -- 14--115
332 External alarm loop 0, Vol. 1 -- 14--116
400 Breakdown of one power supply of the EQPD1 shelf, Vol. 1 -- 14--132
402 Fan fault on the MPU shelf, Vol. 1 -- 14--136
403 Fan fault on the MPU shelfs power supply, Vol. 1 -- 14--139
404 RCB0 failure, Vol. 1 -- 14--142
405 RCB1 failure, Vol. 1 -- 14--144
406 RCB2 failure, Vol. 1 -- 14--146
407 RCB3 failure , Vol. 1 -- 14--148
408 Power supply fault to the fans of the MPU shelf, Vol. 1 -- 14--150
411 Power supply fault of the other chains MPU shelf, Vol. 1 -- 14--153
412 RCB4 failure, Vol. 1 -- 14--155
413 Fault on the right MPU power supply, Vol. 1 -- 14--157
414 Fan fault on EQPT and SWG shelf, Vol. 1 -- 14--159
415 Power supply fault on SWG or SWT shelf, Vol. 1 -- 14--161
417 Power supply fault on EQPT shelf, Vol. 1 -- 14--163
419 Power supply fault on EQPI shelf, Vol. 1 -- 14--165
420 Fan fault on the EQPI, EQPD0 and EQPD1 shelves, Vol. 1 -- 14--167
422 Power supply fault to the fans of the equipment cabinet, Vol. 1 -- 14--169
494 Fault on ECI alarm loop, Vol. 1 -- 14--171
497 New PCM selected as clock reference, Vol. 1 -- 14--173
520 Fault on switching matrix access, Vol. 1 -- 14--176
521 Fault on switching matrix, Vol. 1 -- 14--180
522 Switch supervision failure, Vol. 1 -- 14--182
523 Fault on internal PCM, Vol. 1 -- 14--186
524 Slave switch board not present, Vol. 1 -- 14--187
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Index
Vol. 1 -- iii
601 File management error, Vol. 1 -- 14--189

607 Multibus II error, Vol. 1 -- 14--193
617 SCSI bus controller error, Vol. 1 -- 14--197
633 Disk driver error, Vol. 1 -- 14--203
634 Mirror disk, Vol. 1 -- 14--205
649 SCSI protocol error, Vol. 1 -- 14--211
656 Ethernet controller chip error, Vol. 1 -- 14--213
1074 Indication of non activated features on specific instances, Vol. 1 -- 14--214
1150 Loss of DDTI configuration, Vol. 1 -- 14--215
1151 PCM transmission fault, Vol. 1 -- 14--216
1152 PCM CRC attribute and DDTI CRC strap are not consistent, Vol. 1 -- 14--217
1153 Negative test on passive chain LAPD channel (layer 2), Vol. 1 -- 14--220
1154 Negative test on passive chain CCS7 signalling link (layer 2), Vol. 1 -- 14--222
1155 Fault on SLS card, Vol. 1 -- 14--224
1164 OMC access failure, Vol. 1 -- 14--226
1193 Clock alarm, Vol. 1 -- 14--228
1201 Degraded active chain, Vol. 1 -- 14--230
1211 Unknown TEI in a LAPD message received by the xSCB card, Vol. 1 -- 14--232
1212 xSCB card internal fifo congestion, Vol. 1 -- 14--233
1312 MSC inaccessible, Vol. 1 -- 14--234
1315 Path information for calls released by TCU or BTS, Vol. 1 -- 14--236
1366 Indication of the SSN LCS state, Vol. 1 -- 14--239
1470 Impossibility of storage of a general permanent observation message, Vol. 1 -- 14--240
1472 Purge realized to store a general permanent observation message, Vol. 1 -- 14--242
1483 Impossibility of storage of non prioritary records, Vol. 1 -- 14--243
1484 Impossibility of storage of files, Vol. 1 -- 14--244
1486 Call path tracing activity state change, Vol. 1 -- 14--245
1490 BSC overload, Vol. 1 -- 14--246
1502 Access attempt to a non operational cell, Vol. 1 -- 14--247
BSC 12000 HC
5 Restart after chain suicide due to internal cause, or OMC, Vol. 1 -- 2--1
Source (0) Software anomaly counter threshold, Vol. 1 -- 2--4
Source (1) CPUE (MPU) non present, Vol. 1 -- 2--5
Source (2) CPUE (MPU) or CPUM (OMU) built--in self test failed, Vol. 1 -- 2--7
Source (3) CPUE (MPU) or CPUM (OMU) setup failed , Vol. 1 -- 2--9
Source (4) Incorrect Multibus II card name, Vol. 1 -- 2--11
Source (5) No communication with CPUE (MPU) card, Vol. 1 -- 2--13
Source (8) Error in BSC state machine handler (GAUT), Vol. 1 -- 2--15
Source (10) Error in switchover sequence, Vol. 1 -- 2--16
Source (11) BDA KO during switchover sequence, Vol. 1 -- 2--17
Source (12) Invalid mirror partitions after switchover on the new active chain, Vol. 1 -- 2--18
Source (14) Loss of duplex link detected on passive chain, Vol. 1 -- 2--19
Source (15) Inconsistency between active and passive chains, Vol. 1 -- 2--20
Source (16) Context overflow for BSC (MDB) defense, Vol. 1 -- 2--21
Source (20) Switching while passive chain DP loading, Vol. 1 -- 2--22
Source (21) Error detected during check partition, Vol. 1 -- 2--23
Source (23) CPUE BOOT flashing failed, Vol. 1 -- 2--24
Source (24) Restart to take into account the new BSC customization, Vol. 1 -- 2--25
Vol. 1 -- iv
Index
Source (25) Degraded disk, Vol. 1 -- 2--26

Source (28) End of probative phase OK, Vol. 1 -- 2--29
Source (29) New BDA edition, Vol. 1 -- 2--30
Source (30) Preparation of a type 5 upgrade, Vol. 1 -- 2--31
Source (31) Type 5 upgrade running, Vol. 1 -- 2--32
Source (32) Old release running on passive chain, Vol. 1 -- 2--33
Source (33) Unsuccessful preparation of a type 5 upgrade, Vol. 1 -- 2--34
Source (50) BDA inconsistency, Vol. 1 -- 2--35
Source (51) GES--MS / GES--SL are incoherent, Vol. 1 -- 2--37
Source (52) Passive chain does not answer on RGA request, Vol. 1 -- 2--38
Source (53) Passive chain suicide on RGA request, Vol. 1 -- 2--39
Source (101) No communication with switching board, Vol. 1 -- 2--40
Source (102) No communication with ECI card or fault on ECI card, Vol. 1 -- 2--42
Source (103) No communication with SICX card or fault on SICX card, Vol. 1 -- 2--45
Source (104) No communication with slave switching board, Vol. 1 -- 2--47
Source (105) No communication with SLS card or fault on SLS card, Vol. 1 -- 2--49
Source (106) Operator request, Vol. 1 -- 2--51
Source (107) Degraded REM link, Vol. 1 -- 2--52
Source (128) No communication with SICD or RCB card or fault on SICD or RCB card, Vol. 1 -- 2--53
Source (129) SICD port selftests not OK, Vol. 1 -- 2--56
Source (161) No communication with CCS7 card or fault on CCS7 card, Vol. 1 -- 2--58
Source (162) CCS7 port selftests not OK, Vol. 1 -- 2--60
Source (176) No communication with TCU card or fault on TCU card, Vol. 1 -- 2--62
Source (192) O&M bus selftests not OK, Vol. 1 -- 2--65
6 Restart after chain suicide due to trap, Vol. 1 -- 2--67
11 Restart after chain suicide due to NMI, Vol. 1 -- 2--76
13 Chain restart in progress, Vol. 1 -- 2--78
14 Indication of chain restart cause, Vol. 1 -- 2--79
15 Chain restart due to intermediate card, Vol. 1 -- 2--80
16 Fault on active/passive chains link, Vol. 1 -- 14--83
20 Alarm on clockship of the SUP board, Vol. 1 -- 14--86
21 Beginning of circular file pre--overflow, Vol. 1 -- 14--87
22 End of circular file pre--overflow, Vol. 1 -- 14--89
23 Beginning of BSC disk partition update, Vol. 1 -- 14--90
24 End of BSC disk partition update, Vol. 1 -- 14--91
26 Fault on BSC/OMC--R link, Vol. 1 -- 14--92
33 Saturation on an internal file used for marking climb, Vol. 1 -- 14--93
34 Saturation on a storage zone for marking climb, Vol. 1 -- 14--94
41 Beginning of saturation of the event reporting process in the BSC, Vol. 1 -- 14--95
42 End of saturation of the event reporting process, Vol. 1 -- 14--99
43 Loss of access to the equipment shelf, Vol. 1 -- 14--100
Source (0) Cannot access to all working UTE, Vol. 1 -- 14--101
Source (1) O&M bus selftest not OK, Vol. 1 -- 14--103
44 Board UTE access problem, Vol. 1 -- 14--105
45 Partial hard disk degradation, Vol. 1 -- 14--109
46 Total hard disk degradation, Vol. 1 -- 14--113
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005
Index
Vol. 1 -- v

402 Fan fault on the MPU shelf, Vol. 1 -- 14--136
403 Fan fault on the MPU shelfs power supply, Vol. 1 -- 14--139
404 RCB0 failure, Vol. 1 -- 14--142
405 RCB1 failure, Vol. 1 -- 14--144
406 RCB2 failure, Vol. 1 -- 14--146
407 RCB3 failure , Vol. 1 -- 14--148
408 Power supply fault to the fans of the MPU shelf, Vol. 1 -- 14--150
411 Power supply fault of the other chains MPU shelf, Vol. 1 -- 14--153
412 RCB4 failure, Vol. 1 -- 14--155
413 Fault on the right MPU power supply, Vol. 1 -- 14--157
414 Fan fault on EQPT and SWG shelf, Vol. 1 -- 14--159
415 Power supply fault on SWG or SWT shelf, Vol. 1 -- 14--161
417 Power supply fault on EQPT shelf, Vol. 1 -- 14--163
419 Power supply fault on EQPI shelf, Vol. 1 -- 14--165
420 Fan fault on the EQPI, EQPD0 and EQPD1 shelves, Vol. 1 -- 14--167
422 Power supply fault to the fans of the equipment cabinet, Vol. 1 -- 14--169
494 Fault on ECI alarm loop, Vol. 1 -- 14--171
520 Fault on switching matrix access, Vol. 1 -- 14--178
521 Fault on switching matrix, Vol. 1 -- 14--180
522 Switch supervision failure, Vol. 1 -- 14--184
523 Fault on internal PCM, Vol. 1 -- 14--186
524 Slave switch board not present, Vol. 1 -- 14--187
617 SCSI bus controller error, Vol. 1 -- 14--197
633 Disk driver error, Vol. 1 -- 14--203
634 Mirror disk, Vol. 1 -- 14--206
649 SCSI protocol error, Vol. 1 -- 14--211
1074 Indication of non activated features on specific instances, Vol. 1 -- 14--214
1152 PCM CRC attribute and DDTI CRC strap are not consistent, Vol. 1 -- 14--217
1153 Negative test on passive chain LAPD channel (layer 2), Vol. 1 -- 14--220
1154 Negative test on passive chain CCS7 signalling link (layer 2), Vol. 1 -- 14--222
1155 Fault on SLS card, Vol. 1 -- 14--225
1164 OMC access failure, Vol. 1 -- 14--226
1193 Clock alarm, Vol. 1 -- 14--228
1201 Degraded active chain, Vol. 1 -- 14--230
Vol. 1 -- vi
Index
1211 Unknown TEI in a LAPD message received by the xSCB card, Vol. 1 -- 14--232
1212 xSCB card internal fifo congestion, Vol. 1 -- 14--233
1312 MSC inaccessible, Vol. 1 -- 14--234
1315 Path information for calls released by TCU or BTS, Vol. 1 -- 14--236
1470 Impossibility of storage of a general permanent observation message, Vol. 1 -- 14--240
1472 Purge realized to store a general permanent observation message, Vol. 1 -- 14--242
1483 Impossibility of storage of non prioritary records, Vol. 1 -- 14--243
1484 Impossibility of storage of files, Vol. 1 -- 14--244
1486 Call path tracing activity state change, Vol. 1 -- 14--245
1490 BSC overload, Vol. 1 -- 14--246
1503 Access Attempt to an unknown BCCH or BSIC, Vol. 1 -- 14--249
T
TCU
493 Failure on one of the TCUs clocking sources, Vol. 1 -- 3--10
523 Fault on internal PCM (BSC, TCU), Vol. 1 -- 3--16
1152 PCM CRC4 attribute and DDTI/TDTI CRC4 strap are not consistent, Vol. 1 -- 3--19
1156 TCU downloading failure, Vol. 1 -- 3--21
1157 Loss of TCU remote layer 2, Vol. 1 -- 3--22
1159 Invalid message received on TCU--BSC interface, Vol. 1 -- 3--23
1160 TCU negative acknowledgment indication, Vol. 1 -- 3--25
1163 Preemption of a terrestrial circuit by a signalling link, Vol. 1 -- 3--27, Vol. 1 -- 3--28
1165 VAL_STP_ANO_TRC_BLOCKED, Vol. 1 -- 3--28
1170 External alarm loop on TCU, Vol. 1 -- 3--29
1171 TCU power fault, Vol. 1 -- 3--31
1172 TCU fan board fault, Vol. 1 -- 3--34
1173 TCU fan fault, Vol. 1 -- 3--37
1174 TCU clock fault, Vol. 1 -- 3--41
1180 TCB downloading failure, Vol. 1 -- 3--44
1184 Internal TCB--2 failure, Vol. 1 -- 3--48
1185 TCB--2 synchronization failure, Vol. 1 -- 3--50
1186 External TCB--2 failure, Vol. 1 -- 3--52
1190 Restart after TCU suicide, Vol. 1 -- 3--54
1290 Unacknowledged message on a interface, Vol. 1 -- 3--56
1310 A interface protocol error indication, Vol. 1 -- 3--58
1311 Reset downlink, Vol. 1 -- 3--60
1363 SCCP protocol error indication, Vol. 1 -- 3--61
1364 MTP3 protocol error indication, Vol. 1 -- 3--63
PE/DCL/DD/0101
411--9001--101
Standard 15.101/EN
July 2005

Copyright 1999--2005 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel
Networks. Except as specifically authorized in writing by Nortel
Networks, the holder of this document shall keep the information
contained herein confidential and shall protect same in whole or in part
from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only.
You may not reproduce, represent, or download through any means, the
information contained herein in any way or in any form without prior
written consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTEL
NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL
Globemark, UNIFIED NETWORKS, S2000, S4000, S8000.
GSM is a trademark of France Telecom.
All other brand and product names are trademarks or registred
trademarks of their respective holders.
Publication Reference
PE/DCL/DD/0101
411--9001--101
15.101/EN
July 2005
Originated in France
For more information, please contact:

For all countries, except USA:
Documentation Department
Parc dactivit de Magny--Chateaufort
CHATEAUFORT
78928 YVELINES CEDEX 9
FRANCE
Email : umts--gsm.ntp@nortelnetworks.com
Fax : (33) (1) 39--44--50--29
In the USA:
2221 Lakeside Boulevard
Richardson TX 75082
USA
Tel: 1--800--4 NORTEL
1--800--466--7838 or (972) 684--5935
Internet Address:
http://www.nortelnetworks.com

S8000 Fault Number Description

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

S8000 Fault Number Description

Hochgeladen von

Copyright:

Verfügbare Formate

Wireless Service Provider Solutions

Fault Number Description

Copyright 1999--2005 Nortel Networks

< 101 > : Fault Number Description Volume 1 of 9:

Wireless Service Provider Solutions

Fault Number Description

Copyright 1999--2005 Nortel Networks, All Rights Reserved

Copyright 1999--2005 Nortel Networks

Nortel Networks Confidential

System release: GSM/BSS V15.0.1 Maintenance Load

Copyright 1999--2005 Nortel Networks

Fault Number Description

Nortel Networks Confidential

System release: GSM/BSS V14.3

Copyright 1999--2005 Nortel Networks

Nortel Networks Confidential

System release: GSM/BSS V13

Copyright 1999--2005 Nortel Networks

Fault Number Description

Nortel Networks Confidential

System release: GSM/BSS V12

Copyright 1999--2005 Nortel Networks

Nortel Networks Confidential

Copyright 1999--2005 Nortel Networks

Fault Number Description

Nortel Networks Confidential

PAGE INTENTIONALLY LEFT BLANK

Copyright 1999--2005 Nortel Networks

Nortel Networks Confidential

How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 - 1-- 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1

Description of a fault number sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1

Header of the sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--1

Main body of the sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--2

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--3

Loading the CD--ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 1--3

BSC fault numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 - 2-- 1

Fault number: 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--1

Source: Software anomaly counter threshold . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--4

Source: CPUE (MPU) non present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--5

Source: CPUE (MPU) or CPUM (OMU) setup failed . . . . . . . . . . . . . . . . Vol. 1 -- 2--9

Source: Incorrect Multibus II card name . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--11

Source: No communication with CPUE (MPU) card . . . . . . . . . . . . . . . . Vol. 1 -- 2--13

Source: Error in BSC state machine handler (GAUT) . . . . . . . . . . . . . . . Vol. 1 -- 2--15

Source: Error in switchover sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--16

Source: BDA KO during switchover sequence . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--17

Source: Invalid mirror partitions after switchover on the new active

Source: Inconsistency between active and passive chain . . . . . . . . . . . Vol. 1 -- 2--20

Source: Context overflow for BSC (MDB) defense . . . . . . . . . . . . . . . . . Vol. 1 -- 2--21

Source: Switching while passive chain DP loading . . . . . . . . . . . . . . . . . Vol. 1 -- 2--22

Source: Error detected during check partition . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--23

Source: CPUE BOOT flashing failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--24

Source: Degraded disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--26

Source: Cancellation of probative phase . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--28

Source: End of probative phase OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--29

Source: New BDA edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--30

Source: Preparation of a type 5 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--31

Source: Type 5 upgrade running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--32

Source: Old release running on passive chain . . . . . . . . . . . . . . . . . . . . Vol. 1 -- 2--33

Source: Unsuccessful preparation of a type 5 upgrade . . . . . . . . . . . . . Vol. 1 -- 2--34

Copyright 1999--2005 Nortel Networks

Fault Number Description

Nortel Networks Confidential