S8000 Fault Number Description

Wireless Service Provider Solutions

Fault Number DescriptionVolume 1 of 9: BSC and TCUPE/DCL/DD/0101 15.101/EN Standard July 2005411--9001--101

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

Wireless Service Provider Solutions

Fault Number DescriptionVolume 1 of 9: BSC and TCUDocument number: PE/DCL/DD/0101

411--9001--101Document status: StandardDocument issue: 15.101/ENProduct release: GSM/BSS V15.1Date: 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 inwriting by Nortel Networks, the holder of this document shall keep the information contained herein confidential andshall 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 inany 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.

Publication historyNortel Networks Confidential iii

Fault Number DescriptionCopyright © 1999--2005 Nortel Networks

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, TCB1boards.

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.

Publication history Nortel Networks Confidentialiv

PE/DCL/DD/0101411--9001--101

Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks

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 CRQ00585446 by adding “Help” section (1.3) to chapter 1 (“How to usethis 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 anon--operational cell)

Chapter name change: from “Manual User Guide” to “How to use this manual”

Minor editorial update

Publication historyNortel Networks Confidential v


System release: GSM/BSS V13

November 2002


Updated manual to include the feature BSC support for Lb interface (multi SSN orTandem 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



Publication history Nortel Networks Confidentialvi

PE/DCL/DD/0101411--9001--101


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

Publication historyNortel Networks Confidential vii


November 1999





Chapter 2 “BSC fault numbers”

• updated BSC fault number treatment procedures

September 1999


Creation

Publication history Nortel Networks Confidentialviii

PE/DCL/DD/0101411--9001--101


PAGE INTENTIONALLY LEFT BLANK

Table of contentsNortel Networks Confidential ix


1 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.2.1 Header of the sheet Vol. 1 -- 1--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

2 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 Nortel Networks Confidentialx

PE/DCL/DD/0101411--9001--101


2.1.26 Source: BDA inconsistency Vol. 1 -- 2--35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.27 Source: GES--MS / GES--SL are incoherent Vol. 1 -- 2--37. . . . . . . . . . . . . . . . . . . . . .

2.1.28 Source: Passive chain does not answer on RGA request Vol. 1 -- 2--38. . . . . . . . . . .

2.1.29 Source: Passive chain suicide on RGA request Vol. 1 -- 2--39. . . . . . . . . . . . . . . . . . .

2.1.30 Source: No communication with switching board Vol. 1 -- 2--40. . . . . . . . . . . . . . . . . .

2.1.31 Source: No communication with ECI card or fault on ECI card Vol. 1 -- 2--42. . . . . .

2.1.32 Source: No communication with SICX card or fault on SICX card Vol. 1 -- 2--45. . . .

2.1.33 Source: No communication with slave switching board Vol. 1 -- 2--47. . . . . . . . . . . . .

2.1.34 Source: No communication with SLS card or fault on SLS card Vol. 1 -- 2--49. . . . .

2.1.35 Source: Operator request Vol. 1 -- 2--51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.36 Source: Degraded REM link Vol. 1 -- 2--52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.37 Source: No communication with SICD or RCB card or fault on SICD

or RCB card Vol. 1 -- 2--53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.38 Source: SICD port selftests not OK Vol. 1 -- 2--56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.39 Source: No communication with CCS7 card or fault on CCS7 card Vol. 1 -- 2--58. .

2.1.40 Source: CCS7 port selftests not OK Vol. 1 -- 2--60. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.41 Source: No communication with TCU card or fault on TCU card Vol. 1 -- 2--62. . . . .

2.1.42 Source: O&M bus self--tests not OK Vol. 1 -- 2--65. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Fault number: 6 Vol. 1 -- 2--67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Fault number: 7 Vol. 1 -- 2--68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Fault number: 8 Vol. 1 -- 2--72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Fault number: 11 (BSC 12000) Vol. 1 -- 2--74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Fault number 11: (BSC 12000 “HC”) Vol. 1 -- 2--76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Fault number: 13 Vol. 1 -- 2--78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 Fault number: 14 Vol. 1 -- 2--79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.9 Fault number: 15 Vol. 1 -- 2--80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.10 Fault number: 16 Vol. 1 -- 2--83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2.12 Fault number: 20 (BSC 12000 “HC”) Vol. 1 -- 2--86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.13 Fault number: 21 Vol. 1 -- 2--87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.14 Fault number: 22 Vol. 1 -- 2--89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.15 Fault number: 23 Vol. 1 -- 2--90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.16 Fault number: 24 Vol. 1 -- 2--91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.17 Fault number: 26 Vol. 1 -- 2--92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.18 Fault number: 33 Vol. 1 -- 2--93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.19 Fault number: 34 Vol. 1 -- 2--94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.20 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contentsNortel Networks Confidential xi


2.23 Fault number: 44 Vol. 1 -- 2--105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contents Nortel Networks Confidentialxii

PE/DCL/DD/0101411--9001--101


2.58 Fault number: 520 (BSC 12000 “HC”) Vol. 1 -- 2--178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.59 Fault number: 521 Vol. 1 -- 2--180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



2.62 Fault number: 523 Vol. 1 -- 2--186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.63 Fault number: 524 Vol. 1 -- 2--187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





2.68 Fault number: 617 Vol. 1 -- 2--197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



2.71 Fault number: 633 Vol. 1 -- 2--203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contentsNortel Networks Confidential xiii


2.93 Fault number: 1366 Vol. 1 -- 2--239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.94 Fault number: 1470 Vol. 1 -- 2--240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.95 Fault number: 1472 Vol. 1 -- 2--242. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.96 Fault number: 1483 Vol. 1 -- 2--243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.97 Fault number: 1484 Vol. 1 -- 2--244. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.98 Fault number: 1486 Vol. 1 -- 2--245. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.99 Fault number: 1490 Vol. 1 -- 2--246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.100 Fault number: 1502 Vol. 1 -- 2--247. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.101 Fault number: 1503 Vol. 1 -- 2--249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.102 Table of software error descriptions Vol. 1 -- 2--250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 TCU fault numbers Vol. 1 -- 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1 Fault number: 7 Vol. 1 -- 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Fault number: 8 Vol. 1 -- 3--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Fault number: 47 Vol. 1 -- 3--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Fault number: 493 Vol. 1 -- 3--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Fault number: 497 Vol. 1 -- 3--13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Fault number: 523 Vol. 1 -- 3--16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7 Fault number: 1150 Vol. 1 -- 3--17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.8 Fault number: 1151 Vol. 1 -- 3--18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9 Fault number: 1152 Vol. 1 -- 3--19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10 Fault number: 1156 Vol. 1 -- 3--21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.11 Fault number: 1157 Vol. 1 -- 3--22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.12 Fault number: 1159 Vol. 1 -- 3--23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.13 Fault number: 1160 Vol. 1 -- 3--25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.14 Fault number: 1163 Vol. 1 -- 3--27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.15 Fault number: 1165 Vol. 1 -- 3--28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.16 Fault number: 1170 Vol. 1 -- 3--29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.17 Fault number: 1171 Vol. 1 -- 3--31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.18 Fault number: 1172 Vol. 1 -- 3--34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.19 Fault number: 1173 Vol. 1 -- 3--37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.20 Fault number: 1174 Vol. 1 -- 3--41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.21 Fault number: 1180 Vol. 1 -- 3--44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.22 Fault number: 1184 Vol. 1 -- 3--48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.23 Fault number: 1185 Vol. 1 -- 3--50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.24 Fault number: 1186 Vol. 1 -- 3--52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.25 Fault number 1190 Vol. 1 -- 3--54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.26 Fault number 1290 Vol. 1 -- 3--56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.27 Fault number 1310 Vol. 1 -- 3--58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.28 Fault number 1311 Vol. 1 -- 3--60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.29 Fault number 1363 Vol. 1 -- 3--61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.30 Fault number 1364 Vol. 1 -- 3--63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of tables Nortel Networks Confidentialxiv

PE/DCL/DD/0101411--9001--101


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbersNortel Networks Confidential xv


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbers Nortel Networks Confidentialxvi

PE/DCL/DD/0101411--9001--101


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .








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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbersNortel Networks Confidential 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


607 : Multibus II error Vol. 1 -- 2--193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


617 : SCSI bus controller error Vol. 1 -- 2--197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



633 : Disk driver error Vol. 1 -- 2--203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

634 : Mirror disk Vol. 1 -- 2--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

634 : Mirror disk Vol. 1 -- 2--206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



649 : SCSI protocol error Vol. 1 -- 2--211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .656 and 657 :Ethernet controller chip errorVol. 1 --- 2---213

List of fault numbers Nortel Networks Confidentialxviii

PE/DCL/DD/0101411--9001--101


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbersNortel Networks Confidential 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbers Nortel Networks Confidentialxx

PE/DCL/DD/0101411--9001--101


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbersNortel Networks Confidential 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbers Nortel Networks Confidentialxxii

PE/DCL/DD/0101411--9001--101


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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 : Card monitoring failure Vol. 1 -- 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 : 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. . . . . . . . . . . . . . . . . . . . . . . . . .

List of fault numbersNortel Networks Confidential 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 documentNortel Networks Confidential Vol. 1 -- 0--1


ABOUT THIS DOCUMENTThis document contains the fault number description and the maintenance actionsrequired 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 1 of 9: BSC and TCU

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 thosewho 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 MaintenanceProcedures

< 124 > : BSS Parameter Dictionary

About this document Nortel Networks ConfidentialVol. 1 -- 0--2

PE/DCL/DD/0101411--9001--101


< 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 maintenancemanual.

Chapter 2, “BSC Fault Numbers”, contains the fault number description and thecorrective maintenance procedures applicable to the BSC.

Chapter 3, “TCUFault Numbers”, contains the fault number description and thecorrective maintenance procedures applicable to the TCU.

About this documentNortel Networks Confidential 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 thestate of the subsystem or a fault number

Action to be taken by the operator

Condition

Action to be taken before or after the test

Pointer allowing the flowchart to be divided

Vocabulary conventions

The glossary is included in the NTP < 00 >.

Regulatory information

Refer to NTP < 01 >.

About this document Nortel Networks ConfidentialVol. 1 -- 0--4

PE/DCL/DD/0101411--9001--101


Safety regulations

Introduction

All the following steps must be taken during the various cabinet maintenanceprocedures 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.

CAUTIONImpact on the service and on the equipment

DANGERElectric shock

DANGEREnvironment and personnel protection

CAUTIONESDS handling precautions

How to use this manualNortel Networks Confidential Vol. 1 -- 1--1


1 HOW TO USE THIS MANUAL

1.1 Introduction

This manual contains the fault number descriptions and the correctivemaintenanceprocedures applicable to the BSC and the TCU for GSM 850, 900, 1800, and 1900digital wireless systems.

The general principles and messages required for BSS maintenance are describedin 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 ofequipment, using the alarms and the notifications.

This process is divided into two steps:

locating and identifying the faulty items of equipment, using information givenin this manual

replacing the faulty items of equipment, using the replacement procedures givenin the manuals that describe the on--site procedures

When a faulty item of equipment sends an alarm to the OMC--R, this alarm isidentified by a fault number. This manual gives the procedures associated with thevarious 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 numbertreatment

1.2.1 Header of the sheet

The header contains the following information:

the fault number and possibly the source

the alarm type

How to use this manual Nortel Networks ConfidentialVol. 1 -- 1--2

PE/DCL/DD/0101411--9001--101


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 returnto operational conditions.

• Preliminary checks

These checks are used to ensure that the fault is confirmed and that themessages identifying a faulty element are in the OMC--R logs before the startof repair work.

• On--site maintenance (possibly using the OMC--R)

This paragraph is used to start the repair work and to bring the exchangedelement into correct operation.

• Additional checks

This paragraph shows how to check that the fault has been cleared.

How to use this manualNortel Networks Confidential Vol. 1 -- 1--3


1.3 Help

The system provides the user with help at any time. For an in--depth discussion ofHelp, refer to NTP <130>.

There are two kinds of help available:

on--line help, available from theHelpmenu in the OMC--R Browser window, aswell as other windows

the Consult BSS Documentation option of the workstation workspace pop--upmenu 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 theOMC--R server and/or workstation CD--ROM drive. Installation is complete whenthe light on the CD--ROM drive is no longer lit.

How to use this manual Nortel Networks ConfidentialVol. 1 -- 1--4

PE/DCL/DD/0101411--9001--101



BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--1


2 BSC FAULT NUMBERS

2.1 Fault number: 5III

Fault number:5 : Restart after chain suicide due to internal cause, or OMCType : processingErrorAlarm

The following Table 2--1 indicates all the sources of the fault number 5. For moreinformation on each source and the associated corrective maintenance procedure,refer to the sheet indicated in the right column.

SourceNo. Source wording BSC

12000

BSC12000HC

Procedure

0 Software anomaly counter threshold x x 2.1.1

1 CPUE (MPU) non present x x 2.1.2

2 CPUE (MPU) or CPUM (OMU) built--inself test failed

x x 2.1.3

3 CPUE (MPU) or CPUM (OMU) setupfailed

x x 2.1.4

4 Incorrect Multibus II card name x x 2.1.5

5 No communication with CPUE (MPU)card

x x 2.1.6

8 Error in BSC state machine handler(GAUT)

x x 2.1.7

10 Error in switchover sequence x x 2.1.8

11 BDA KO during the switchoversequence

x x 2.1.9

12 Invalid mirror partitions after switchoveron the new active chain

x x 2.1.10

14 Loss of the duplex link detected onpassive chain

x x 2.1.11

15 Inconsistency between active andpassive chains

x x 2.1.12

16 Context overflow for BSC (MDB)defense

x x 2.1.13

BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--2

PE/DCL/DD/0101411--9001--101


SourceNo. Procedure

BSC12000HC

BSC12000Source wording

20 Switching while passive chain DPloading

x x 2.1.14

21 Error detected during check partition x x 2.1.15

23 CPUE BOOT flashing failed x x 2.1.16

24 Restart to take into account the newBSC customization

x x 2.1.17

25 Degraded disk x x 2.1.18

27 Cancellation of probative phase x x 2.1.19

28 End of probative phase OK x x 2.1.20

29 New BDA edition x x 2.1.21

30 Preparation of a type 5 upgrade x x 2.1.22

31 Type 5 upgrade running x x 2.1.23

32 Old release running on passive chain x x 2.1.24

33 Unsuccessful preparation of a type 5upgrade

x x 2.1.25

50 BDA inconsistency x x 2.1.26

51 GES--MS/GES--SL are incoherent x x 2.1.27

52 Passive chain does not answer on RGArequest

x x 2.1.28

53 Passive chain suicide on RGA request x x 2.1.29

101 No communication with switching board x x 2.1.30

102 No communication with ECI card orfault on ECI card

x x 2.1.31

103 No communication with SICX card orfault on SICX card

x x 2.1.32

104 No communication with slave switchingboard

x x 2.1.33

105 No communication with SLS card orfault on SLS card

x x 2.1.34

106 Operator request x x 2.1.35



SourceNo. Procedure

BSC12000HC

BSC12000Source wording

107 Degraded REM link x x 2.1.36

128 No communication with SICD or RCBcard or fault on SICD or RCB card

x x 2.1.37

129 SICD port self tests not OK x x 2.1.38

161 No communication with CCS7 card orfault on CCS7 card

x x 2.1.39

162 CCS7 port self tests not OK x x 2.1.40

176 No communication with TCU card orfault on TCU card

x x 2.1.41

192 O&M bus self tests not OK x x 2.1.42

Table 2--1 Fault number 5 sources


PE/DCL/DD/0101411--9001--101


2.1.1 Source: Software anomaly counter threshold

iii

Fault number 5 Restart after chain suicide due to internal cause, orOMC

Source: (0) Software anomaly counter thresholdBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain restartedafter the threshold (set to 40)of thesoftwareanomaly counter was exceeded.

If the software anomaly counter threshold was exceeded on the active chain, a chainswitchover took place: the active chain committed suicide, and the passive chainbecame active.

If the software anomaly counter threshold was exceeded on the passive chain, thepassive 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.

Impact on the service

None, unless the counter exceeded the threshold on both chains. In this case, there is aloss of service during the BSC restart.

FAULT TREATMENT

Send the software anomaly notifications to the manufacturer.



2.1.2 Source: CPUE (MPU) non present

iii


Source: (1) CPUE (MPU) non presentBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because a CPUEboard (CPU--MPU or CPU--BIFP) is missing.

When a CPUE board is missing, the chain concerned commits suicide and restartscyclically.


Another notification with fault number 7 “card monitoring failure” must have been sentbefore 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 Action

1 Check the state of the BSC, by performing a “Display all” command on the bscobject.

If the value of the “bsc” field” is “duplex”, this fault number indicates a transientproblem 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 faultnumber 7 “card monitoring failure” that indicate a problem on one CPUE boardof the chain that is out of order.

i. Treat these notifications.

ii. Then go to step 3.


PE/DCL/DD/0101411--9001--101


On--site maintenance

Step Action

2 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 Action

3 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) confirm that the BSC restarts correctly.

4 If necessary, clear the alarm concerning the CPUE board.

5 The procedure is complete.



2.1.3 Source: CPUE (MPU) or CPUM (OMU) built--in self test failed

iii


Source: (2) CPUE (MPU) or CPUM (OMU) built--in self test failedBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because a CPUEboard (CPU--MPUor CPU--BIFP) or a CPUMboard (CPU--OMU) had abad built--in selftest(BIST) result. The board is not operational. The chain concerned never reaches anoperational state.

When a CPUE or a CPUM board is missing, the chain concerned commits suicide andrestarts cyclically.


BSC defense

None. The BSC is in simplex mode.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 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.


If the value of the “bsc” field” is “duplex”, this fault number indicates a transientproblem or a bad operation of the CPUE or CPUM board.


ii. If the problem often happens, replace the CPUE or CPUM board. Go tostep 2.


PE/DCL/DD/0101411--9001--101


Step Action (Continued)

If the value of the “bsc” field” is “simplex”, look for other notifications with faultnumber 7 “card monitoring failure” that indicate a problem on one CPUE orCPUM board of the chain that is out of order.




Step Action

3 Replace the CPUE or CPUM board (Field Replaceable Unit):



Additional checks

Step Action

4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) confirm that the BSC restarts correctly.

5 If necessary, clear the alarm concerning the CPUE or CPUM board.




2.1.4 Source: CPUE (MPU) or CPUM (OMU) setup failed

iii


Source: (3) CPUE (MPU) or CPUM (OMU) setup failedBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because a CPUEboard (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 andrestarts cyclically, but the chain concerned never reaches the operational state.

Another notification with fault number 7 “card monitoring failure” must have been sentbefore.


BSC defense



None.

FAULT TREATMENT

Preliminary checks

Step Action


If the value of the “bsc” field” is “duplex”, this fault number indicates a transientproblem or a bad operation of the CPUM and CPUE board.


ii. If the problem often happens, replace the CPUE board. Go to step 2.


PE/DCL/DD/0101411--9001--101



If the value of the “bsc” field” is “simplex”, look for other notifications with faultnumber 7 “card monitoring failure” that indicate a problem on one CPUM orCPUE board of the chain that is out of order.




Step Action

2 Replace the faulty board (Field Replaceable Unit):

a. Refer to the replacement procedure (see NTP < 41 >).


Additional checks

Step Action

3 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.

4 If necessary, clear the alarm concerning the CPUE or CPUM board.




2.1.5 Source: Incorrect Multibus II card name

II


Source: (4) Incorrect Multibus II card nameBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

The notification indicates that a chain committed suicide and restarted because it detectedthat there was a problem with one of its boards connected to the Multibus II. One boardconnected 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 Action

1 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.



PE/DCL/DD/0101411--9001--101


On--site maintenance using the OMC--R

Step Action

2 Check that the boards connected are according to the types of boards of theconfiguration.

If everything is incorrect, position the correct type of board. Go to step 6.

3 Go on site and check that the boards of the chain are correctly positioned. Checkthe 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 Action


7 If necessary, clear the alarm concerning the replaced board.




2.1.6 Source: No communication with CPUE (MPU) card

III


Source: (5) No communication with CPUE (MPU) cardBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

The system indicates that a chain committed suicide and restarted because a CPUE boardis 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 acknowledgethe 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 Action


If the value of the “bsc” field” is “duplex”, check the state of the CPUE or SICDboards 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 faultyboard. Go to step 3.

If the value of the “bsc” field” is “simplex”, go to step 2.


PE/DCL/DD/0101411--9001--101



2 Look for a notification or an alarm (fault numbers 7) concerning the CPUE or SICDboard 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 currentalarms, do not take the source of this alarm (with fault number 5) into account.Go to step 5.


Step Action

3 Replace the CPUE or SICD board quoted in the beginning--of hardware faultnotification:

a. Refer to the replacement procedure given in NTP < 41 >.


Additional checks

Step Action


5 If necessary, clear the alarm concerning the CPUE or SICD board.




2.1.7 Source: Error in BSC state machine handler (GAUT)

iii


Source: (8) Error in BSC state machine handler (GAUT)BSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because itencountered a software problem.



BSC defense

None.


None.

FAULT TREATMENT

No maintenance is required.


PE/DCL/DD/0101411--9001--101


2.1.8 Source: Error in switchover sequence

iii


Source: (10) Error in switchover sequenceBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain that was becoming active committed suicide andrestarted. During the switchover sequence, the process corresponding to the switchoveris 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.



2.1.9 Source: BDA KO during switchover sequence

iii


Source: (11) BDA KO during switchover sequenceBSC model: BSC12000 + BSC12000 “HC”

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.


CAUTIONService 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 replacementprocedure of the MMU or MMU_IDE (see NTP < 41 >).


PE/DCL/DD/0101411--9001--101


2.1.10 Source: Invalid mirror partitions after switchover on the new activechain

iii


Source: (12) Invalid mirror partitions after switchover on the newactive chain

BSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a BDA partition of the new active chain is not valid. A newswitchover is started.



BSC defense

None.



There is loss of service because of two chain switchovers.

FAULT TREATMENT




2.1.11 Source: Loss of the duplex link detected on passive chain

iii


Source: (14) Loss of duplex link detected on passive chainBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becauseit 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



PE/DCL/DD/0101411--9001--101


2.1.12 Source: Inconsistency between active and passive chain

iii


Source: (15) Inconsistency between active and passive chainsBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain restarted with a software version differentfrom 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




2.1.13 Source: Context overflow for BSC (MDB) defense

iii


Source: (16) Context overflow for BSC (MDB) defenseBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because there wasan overflow of the number of BSC defense treatment contexts.




BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.14 Source: Switching while passive chain DP loading

iii


Source: (20) Switching while passive chain DP loadingBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the BSC performed a chain switchover while downloadingthe permanent data (DP) on the passive chain.

The BSC commits suicide and starts again so as to save data consistency. The BSC sendsthis notification as soon as the duplex link is open.


BSC defense

None.



The service is lost.

FAULT TREATMENT

No maintenance is required. Look for the source of the first switchover.



2.1.15 Source: Error detected during check partition

iii


Source: (21) Error detected during check partitionBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because an errorwas detected during a partition check. The faulty partition is deleted.




BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.16 Source: CPUE BOOT flashing failed

iii


Source: (23) CPUE BOOT flashing failedBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because a CPUEor 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 SICDboard. Refer to the replacement procedure given in NTP < 41 >.



2.1.17 Source: Restart to take into account the new BSC customization

iii


Source: (24) Restart to take into account the new BSCcustomization


FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted to takeinto account its new customization.

The customization data come from the active chain and they are copied to the new disk ofthe 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 isa normal behavior. Besides, the customization is really complete only when the passivechain became active once.



BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.18 Source: Degraded disk

iii


Source: (25) Degraded diskBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because its disk isdegraded: the number of erroneous access on the disk reaches the threshold activating theanomaly. In the case of BSC simplex mode, this alarm may appear with a fault number 46alarm.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action


If the value of the “bsc” field” is “duplex”, check the state of the MMU boards inthe result window of the “Display all” command.

• If the MMU or MMU_IDE boards state is “working”, this fault numberindicates a transient problem or a bad operation of the board.





ii. If this problem often happens, the replacement of the board must beconsidered. Go to step 2.

• If the state of one of the MMU or MMU_IDE boards state is “partiallydegraded”, 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”, replacethe faulty board. Go to step 2.

If the value of the “bsc” field” is “simplex”, look for other notifications that wouldconfirm that there is a problem on theMMUorMMU_IDE board of the chain thatis out of order.


ii. Replace the faulty MMU or MMU_IDE board:

• If the board has not been replaced, go to step2.

• If not, go to step 3.


Step Action

2 Replace the faulty MMU or MMU_IDE board (Field Replaceable Unit):



Additional checks

Step Action


4 If necessary, clear the alarm concerning the MMU or MMU_IDE board.



PE/DCL/DD/0101411--9001--101


2.1.19 Source: Cancellation of probative phase

iii


Source: (27) Cancellation of probative phaseBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because theoperator cancelled the probative phase during a software upgrade. The operator cancelledthe new software version (type 5 software upgrade). The active chain of n+1 softwareversion committed suicide. The new active chain of n software version updates theconsistency of the passive chain. When the BSC is in duplex state, the two chains are inn software version.



BSC defense

None.



During the network unconfiguration and reconfiguration, an outagethat lasted less than five minutes happened.

FAULT TREATMENT




2.1.20 Source: End of probative phase OK

iii


Source: (28) End of probative phase OKBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted after thesuccessful 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+1software 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+1software version is installed, but its BDA is still n. That’s why the passive chain commitssuicide 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



PE/DCL/DD/0101411--9001--101


2.1.21 Source: New BDA edition

iii


Source: (29) New BDA editionBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted to takeinto account the new edition of the BDA, already built. This procedure is used for thechanges of frequency plans.

It is a normal behavior to update the data on the passive chain.



BSC defense

None.



During the update of the new BDA, an outage that lasted less thanfive minutes happened.

FAULT TREATMENT




2.1.22 Source: Preparation of a type 5 upgrade

iii


Source: (30) Preparation of a type 5 upgradeBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted to prepare for theupdate of theBDA: the software compatiblewith thenew versionof theBDA are transferredin the current partition and will be taken into account after the chain restart. The two chainsare started successively.



BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.23 Source: Type 5 upgrade running

iii


Source: (31) Type 5 upgrade runningBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

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



BSC defense

None.


None.

FAULT TREATMENT




2.1.24 Source: Old release running on passive chain

iii


Source: (32) Old release running on passive chainBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

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



BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.25 Source: Unsuccessful preparation of a type 5 upgrade

iii


Source: (33) Unsuccessful preparation of a type 5 upgradeBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because the takinginto account of the software during a type 5 software upgrade was unsuccessful. The newBDA can not been built.



BSC defense

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


None.

FAULT TREATMENT




2.1.26 Source: BDA inconsistency

iii


Source: (50) BDA inconsistencyBSC model: BSC 12000 + BSC 12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because the BDAwas intrinsically inconsistent.



BSC defense

None.


None.

FAULT TREATMENT

Maintenance using the OMC--R

Step Action

1 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.

2 Wait for the notification “BSC requires a BDA on--line building”. Then go to step 3.

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.


PE/DCL/DD/0101411--9001--101



4 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 Action


6 If necessary, clear the alarm concerning the incoherent BDA.




2.1.27 Source: GES--MS / GES--SL are incoherent

iii


Source: (51) GES--MS / GES--SL are incoherentBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because GES--MSand GES--SL are incoherent.



BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.28 Source: Passive chain does not answer on RGA request

iii


Source: (52) Passive chain does not answer on RGA requestBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becauseit did not answer the RGA request.



BSC defense

None.


None.

FAULT TREATMENT




2.1.29 Source: Passive chain suicide on RGA request

iii


Source: (53) Passive chain suicide on RGA requestBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted followingan RGA request.



BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.30 Source: No communication with switching board

iii


Source: (101) No communication with switching boardBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because its CPUMboard (CPU--OMU) lost contact with an SWC board.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action


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 problemor a bad operation of the board concerned. Clear the alarm. Go to step 6. Ifthis problem often happens, the board replacement must be considered. Goto step 4.




3 Perform a “Display chain information” command to check the state of the SWCboard.

If the board state is “working”, this fault number indicates a transient problemor a bad operation of the board concerned.


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.



Step Action

4 Replace the SWC board quoted in the beginning--of hardware fault notification(Field Replaceable Unit):



Additional checks

Step Action


6 If necessary, clear the alarm concerning the SWC board.



PE/DCL/DD/0101411--9001--101


2.1.31 Source: No communication with ECI card or fault on ECI card

iii


Source: (102) No communication with ECI card or fault on ECI cardBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because the controlcabinet lost contact with the ECI board (through the SICX board).



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action






2 Look for the following notification: fault number 7 “card monitoring failure”

If there are alarms, go to step 3.

If there are not any alarms, this fault number indicates a transient problem or abad operation of the board concerned. Clear the alarm. Go to step 7. If thisproblem often happens, the board replacement must be considered. Go tostep 4.




3 Performa “Display chain information” command to check the state of theECIboard.





i. Treat the alarm with fault number 7.



Step Action

4 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 thenbecomes off, the ECI boardis 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.

5 Replace the ECI board quoted in the beginning--of hardware fault notification (FieldReplaceable Unit):



6 Replace the SICX board (Field Replaceable Unit):




PE/DCL/DD/0101411--9001--101


Additional checks

Step Action


8 If necessary, clear the alarm concerning the board.




2.1.32 Source: No communication with SICX card or fault on SICX card

iii


Source: (103) No communication with SICX card or fault on SICXcard


FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because it lostcontact with the SICX board.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action






2 Look for the following notification: fault number 7 “card monitoring failure”

If there are alarms, go to step 3.

If there are not any alarms, this fault number indicates a transient problem or abad operation of the SICX board. Clear the alarm. Go to step 6. If this problemoften happens, the board replacement must be considered. Go to step 4.


PE/DCL/DD/0101411--9001--101



3 Perform a “Display chain information” command to check the state of the SICXboard.





i. Treat the alarm with fault number 7.



Step Action

4 Replace the SICX board quoted in the beginning--of hardware fault notification:



Additional checks

Step Action


6 If necessary, clear the alarm concerning the SICX board.




2.1.33 Source: No communication with slave switching board

5_10


Source: (104) No communication with slave switching boardBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because it lostcontact with an SWE or MSW board.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action


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. Goto step 3.



PE/DCL/DD/0101411--9001--101



2 Look for a notification or an alarm (with fault number 524 “Slave switch board notpresent”) concerning the SWE board quoted in the restart notification.

a. Treat this notification.

b. Then go to step 4.


Step Action

3 Replace the switching board quoted in the beginning--of hardware fault notification:



Additional checks

Step Action


5 If necessary, clear the alarm concerning the replaced switching board.




2.1.34 Source: No communication with SLS card or fault on SLS card

iii


Source: (105)No communication withSLS card or fault on SLScardBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because the SUPor 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 BSCand theOMC--R is lost,but there is not any impact on the service either.

FAULT TREATMENT

Preliminary checks

Step Action







PE/DCL/DD/0101411--9001--101



2 Look for the following notification:

• fault number 1155 “Fault on SLS card”

– If there are alarms, go to step 3.

– If there are not any alarms, this fault number indicates a transient problemor a bad operation of the SLS or SLS2 board. Clear the alarm. Go to step6. If this problem often happens, the board replacement must beconsidered. Go to step 4.

3 Perform a “Display chain information” command to check the state of the SLS orSLS2 board.

If the board state is “working”, this fault number indicates a transient problemor a bad operation of the board concerned. Clear the alarm. Go to step 6. If thisproblem often happens, the board replacement must be considered. Go to step4.

If the board state is “faulty”, treat the alarm with fault number 1155. Then go tostep 5.


Step Action

4 Replace the SLS or SLS2 board quoted in the beginning--of hardware faultnotification:



Additional checks

Step Action


6 If necessary, clear the alarm concerning the SLS or SLS2 board.




2.1.35 Source: Operator request

iii


Source: (106) Operator requestBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because theoperator requested it.



BSC defense

None.


None.


Nevertheless, there is a loss of service if the operator requests achain suicide while the other chain is unable to become active andoperational.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101


2.1.36 Source: Degraded REM link

ii


Source: (107) Degraded REM linkBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becausethe REM link between the SUP2 board, SLS2 board, and the OMC--R is broken. The REMlink (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

1 Look for a notification or an alarm with fault number 1164 “OMC access failure”.



Additional checks

Step Action


3 If necessary, clear the alarm concerning the REM link.




2.1.37 Source: No communication with SICD or RCB card or fault on SICDor RCB card

iii


Source: (128) No communication with SICD or RCB card or fault onSICD or RCB card


FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becauseits CPUM board (CPU--OMU) lost contact with a SICD or RCB board and the associatedinternal 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 Action







PE/DCL/DD/0101411--9001--101



2 Look for the following notification:

with fault number 7 “Cardmonitoring failure” concerning the SICD board quotedin the restart notification

with fault number 404 “RCB0 failure” concerning the RCB 0 board quoted in therestart notification





with fault number 523 “fault on internal PCM link (BSC, TCU)” concerning theinternal PCM link quoted in the notification

• If there are alarms, go to step 3.

• If there are not any alarms, this fault number indicates a transient problemor 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 beconsidered. Go to step 4 or 5.

3 Perform a “Display chain information” command to check the state of the SICD andRCB board and the associated internal PCM links 2 or 3.

If the state is “working”, this fault number indicates a transient problem or a badoperation of the board concerned. Clear the alarm. Go to step 7. If this problemoften 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 Action

4 Replace the SICD board quoted in the beginning--of hardware fault notification(Field Replaceable Unit):






5 Replace theRCBboardquoted in thebeginning--of hardware fault notification (FieldReplaceable Unit):



Additional checks

Step Action





PE/DCL/DD/0101411--9001--101


2.1.38 Source: SICD port selftests not OK

iii


Source: (129) SICD port selftests not OKBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becausetheSICDports are not operational anymore. They are testedcyclically on thepassivechain.



BSC defense

None.


None, as long as the chain remains passive.

FAULT TREATMENT

Preliminary checks

Step Action


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 passivechain LAPD channel (layer 2)”.






3 Look for a notification or an alarm with fault number 8 “Negative built--in self--testfor card” concerning the SICD boards.



Additional checks

Step Action


5 If necessary, clear the alarm concerning the SICD ports.



PE/DCL/DD/0101411--9001--101


2.1.39 Source: No communication with CCS7 card or fault on CCS7 card

iii


Source: (161) No communication with CCS7 card or fault on CCS7card


FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because its CPUMboard (CPU--OMU) lost contact with a CCS7 board.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 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 boardsand the associated internal PCM link 0 by looking again at the descriptionwindow 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 theCCS7 boards is “faulty”, replace the faulty board. Goto step 3.





2 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 thein restart notification.




Step Action

3 Replace the CCS7 board quoted in the beginning--of hardware fault notification:



Additional checks

Step Action


5 If necessary, clear the alarm concerning the replaced CCS7 board.



PE/DCL/DD/0101411--9001--101


2.1.40 Source: CCS7 port selftests not OK

iii


Source: (162) CCS7 port selftests not OKBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because its CCS7ports are not operational anymore. They are tested cyclically on the passive chain.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 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 passivechain CCS7 signalling link (layer 2)”.






3 Look for a notification or an alarm with fault number 8 “Negative built--in self--testfor card” concerning the CCS7 boards.



Additional checks

Step Action


5 If necessary, clear the alarm concerning the CCS7 ports.



PE/DCL/DD/0101411--9001--101


2.1.41 Source: No communication with TCU card or fault on TCU card

iii


Source: (176) No communication with TCU card or fault on TCUcard


FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because it cannotaccess any TCU.

When one of the items of equipment related to the LAPD is faulty, the chain cannotcommunicate 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 onthe 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 bedisplayed on the display panels of the SUP boards of both chains. At the OMC--R, thetranscoder objects are “disabled--dependency”.


The network is not operational. There is no service.



FAULT TREATMENT

Preliminary checks

Step Action






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.

3 Look for a notification or an alarm concerning the passive chain:

with fault number 7 “Cardmonitoring failure” or fault number 8 “Negative built--inself 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 theinternal PCM link




PE/DCL/DD/0101411--9001--101


Additional checks

Step Action


5 If necessary, clear the alarm concerning the TCU access.




2.1.42 Source: O&M bus self--tests not OK

iii


Source: (192) O&M bus selftests not OKBSC model: BSC12000 + BSC12000 “HC”

FAULT ANALYSIS

This notification indicates that the passive chain committed suicide and restarted becausethe O&M bus is not operational anymore.

The O&M bus and all the UTE boards connected to it (ALA, DDTI, BSCB, and TSCBboards) 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 Action







PE/DCL/DD/0101411--9001--101



Step Action

2 Replace the ECI board (Field Replaceable Unit). For more information, refer toNTP < 41 >. Then go to step 3.

Additional checks

Step Action


4 If necessary, clear the alarm concerning the O&M bus.




2.2 Fault number: 6

iii

Fault number:6 : Restart after chain suicide due to trapType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates that a chain committed suicide and restarted because a softwareerror 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.



None, except if the BSCwas in simplex mode. In the latter case, anoutage took place.

FAULT TREATMENT

Send the traces to the manufacturer, to find out what happened.


PE/DCL/DD/0101411--9001--101


2.3 Fault number: 7

iii

Fault number:7 : Card monitoring failureType : equipmentAlarm

FAULT ANALYSIS

This notification indicates that a board does not answer to the CPUM board or the ECIboard.

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 maycommit 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.


If an equipment cabinet board (UTEboard) is concerned, then thereis a loss of service.



FAULT TREATMENT

Preliminary checks

Step Action

1 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.

2 Check the state of the BSC boards, by performing a “Display all” command on thebsc object.


If the state of the board quoted in the notification is “faulty”, go on site to checkthe faulty board. Go to step 5.

3 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 itsoperationalState:

• If the operationalState of the pcmCircuit object is “enabled”, go to step 4.

• If the operationalState of the pcmCircuit object is “disabled”, the PCM linkconcerned is not operational yet. Wait.

• If the operationalState of the pcmCircuit object is “disabled”, and theavailabilityStatus is “dependency”, look for a problemconcerning the internalPCM link (with fault number 523).

• If the operationalState of the pcmCircuit object is “disabled”, and theavailabilityStatus is “failed”, perform a “Display all” command on the bscobject 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 tostep 6.

4 Perform a “Display all” command on the pcmCircuit object to check the value of the“DDTIIntstate” parameter.

If the valueof the “DDTIIntstate” parameter is “working”, clear thealarmand lookfor 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 bereplaced. Go to step 6.


PE/DCL/DD/0101411--9001--101



Step Action

5 Check that the boards of the chain are correctly positioned. Check the PROM aswell.

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.

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 Action

7 Check that the repaired chain is operational:

If a board in the equipment cabinet (the DDTI and ALA boards) has beenreplaced, check the return to correct operation of the chain by a change of statedisplayed at the OMC--R.




If a board in the control cabinet or the ECI board has been replaced, check thatthe repaired chain does not commit suicide again:

• At the OMC--R, warning notifications (with fault number 13) allow to know ifthe BSC restarts correctly.

• On--site, check that “12” is displayed in the SUP board display panels afterthe BSC start--up.

8 If necessary, clear the alarm.



PE/DCL/DD/0101411--9001--101


2.4 Fault number: 8iii

Fault number:8 : Negative built in self test result for cardType : equipmentAlarm

FAULT ANALYSIS

At the initialization of a BSC board, a global result is sent. If the BISTs are not correct, theboard 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 maycommit 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.


If an equipment cabinet board (UTEboard) is concerned, then thereis a loss of service.

FAULT TREATMENT

Preliminary checks

Step Action

1 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 faultyboard. Go to step 2.




Step Action

2 Replace the boardmentioned in the test result notification (Field ReplaceableUnit):

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 Action

3 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 theBSC restarts correctly.

On--site, check that “12” is displayed in the SUP board display panels after theBSC start--up.




PE/DCL/DD/0101411--9001--101


2.5 Fault number: 11 (BSC 12000)iii

Fault number:11 : Restart after chain suicide due to NMIType : processingErrorAlarm

If the BSC 12000 “HC” is concerned, refer to Paragraph 2.6.

FAULT ANALYSIS

This notification indicates that a chain committed suicide becauseaNonMaskable 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.

Oneof theMultibus II boards (CPUE, SICD8V,CCS7, SUPandCPUM (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 Action

1 Check that the chain concerned restarts correctly.

If the chain runs in nominal mode at the end of the restart (“12” is displayed inthe SUP board display panels), go to step 9.

If the chain runs in degraded mode at the end of the restart (“32” is displayedin the SUP board display panels), go to step 2.

If the chain does not restart, go to step 3.

2 Note the name of the board given in the notification:

If the board quoted in the notification is a CPUE, SICD8V, CCS7, or SICXboard,go to step 4.

If the board quoted in the notification is theCPUMboard (CPU66SE) or theSUPboard, go to step 3.




3 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 thenstops, the CPUM board (CPU66SE) is faulty. Go to step 6.

4 Look for a notification with fault number 5 “Restart after chain suicide due to internalcause, or OMC”, or fault number 7 “Card monitoring failure” that is still active afterthe chain restarted.

a. Treat the notification.



Step Action

5 Replace the faulty SUP board (Field Replaceable Unit):


b. The return to service operations are performed by the system. Then go tostep 7.

6 Replace the faulty CPUM board (CPU66SE) (Field Replaceable Unit):



Additional checks

Step Action


a. At the OMC--R, warning notifications (with fault number 13) allow to know if theBSC restarts correctly.

b. On--site, check that “12” is displayed in the SUP board display panels after theBSC start--up.




PE/DCL/DD/0101411--9001--101


2.6 Fault number 11: (BSC 12000 “HC”)iii

Fault number:11 : Restart after chain suicide due to NMIType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates that a chain committed suicide becauseaNonMaskable 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 aNMI.



BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 Check that the chain concerned restarts correctly.

If the chain runs in nominal mode at the end of the restart (“12” is displayed inthe SUP2 board display panels), go to step 9.

If the chain runs in degraded mode at the end of the restart (“32” is displayedin the SUP2 board display panels), go to step 2.

If the chain does not restart, go to step 3.

2 Note the name of the board given in the notification:

If the board quoted in the notification is a CPUE (CPU133), SICD8V, CCS7, orSICX board, go to step 4.

If the board quoted in the notification is the CPUM board (CPU133IE) or theSUP2 board, go to step 3.




3 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 thenstops, the CPUM board (CPU133IE) is faulty. Go to step 6.

4 Look for a notification with fault number 5 “Restart after chain suicide due to internalcause, or OMC”, or fault number 7 “Card monitoring failure” that is still active afterthe chain restarted.

a. Treat the notification.



Step Action

5 Replace the faulty SUP2 board (Field Replaceable Unit):



6 Replace the faulty CPUM board (CPU133IE) (Field Replaceable Unit):



Additional checks

Step Action



b. On--site, check that “12” is displayed in the SUP2 board display panels after theBSC start--up.




PE/DCL/DD/0101411--9001--101


2.7 Fault number: 13

iii

Fault number:13 : Chain restart in progressType : processingErrorAlarm

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 thedifferent restart phases of the BSC.

The values of the “Restart phase” field are:

Restart phase Explanation

Beginning of restart notification generated just after theCPUM board started

Restart completed notification generated just before thepermanent data downloading started

BSC’s chain switchover completed notification sent by the active chain justafter the switchover

Switch state is DUPLEX notification sent by the active chain afterthe dynamic data on the passive chainhave been updated

BSC software version change completed


BSC defense

None.


None.

FAULT TREATMENT





iii

Fault number:14 : Indication of chain restart causeType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates the source of the restart of the chain.

The values of the “Source” field are:

Source No. Source wording Explanation

126 Reset due to Watchdog NMI(state: not operational)

190 External Reset

220 Manual NMI(state: operational)

222 Software Reset Other notifications related to the chainrestart are sent as well.

238 Manual NMI(state: not operational)

restart are sent as well.

246 Manual Reset

250 Reset due to watchdog NMI(state: operational)

254 Reset on Power On No other notifications are sent.This source is the only significant one.


BSC defense

None.


None.

ON--SITE MAINTENANCE



PE/DCL/DD/0101411--9001--101



Fault number:15 : Chain restart due to intermediate cardType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates that the loss of a link (ECI, SICX) has led to the suicide of theactive chain.

The ECI board can send this notification during the chain restart, when it loses its link withthe SICX board.


BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 Check whether the fault number 15 was sent alone, or if there are othernotifications:

If there are other notifications, go to step 2.


2 Wait for the start--up end, and check that the chain is operational again.

If the chain is operational again, the following notificationsmust 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 differentsources

If the passive chain does not restart:

• either the passive chain is powered off: look for a notification with faultnumber 411 “Power supply fault of the other chains MPU shelf”,

• or one of the important boards (CPUM, CPUE, MMUandSUP) is faulty: lookfor a notification concerning one of these boards.




3 The notification with fault number 15 was sent alone because the chain has beenpowered 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 SUPboard: the Ethernet link is faulty. Go to step 6.

one of the important boards (CPUM, CPUE, MMU and SUP) is faulty. Go tostep 7.


Step Action

4 Look for a problem concerning the ventilation system: the power supply or theVENT board may be faulty.

If the ventilation system is operational, go to step 5.

If the ventilation system is not operational, perform the necessary correctivemaintenance. Then go to step 8.

5 Check the straps on the MPU backpanel.

If some straps are badly positioned or missing, position them correctly on theMPU backpanel. For more information, refer to the BSCReference NTP . Thengo to step 8.

If the straps are operational, go to step 6.

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 correctivemaintenance. Concerning the transceiver, fix the passive chain first.

7 Look for a notification concerning the CPUM, CPUE, MMU and SUP boards, andtreat it. Then go to step 8.


PE/DCL/DD/0101411--9001--101


Additional checks

Step Action



b. On--site, check that “12” is displayed in the SUP board display panels after theBSC start--up.





iii

Fault number:16 : Fault on active/passive chains linkType : equipmentAlarm

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 possiblesources are as follows:

a chain switchover or a chain restart, and this notification is sent systematically duringthese 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

1 Monitor the different phases of the BSC restart. For more information, refer toNTP < 41 > to know the different restart phases of the BSC.

2 Check that this alarm is automatically cleared 20 minutes later.

3 Check the BSC state by performing a “Display all” command on the bsc object.


PE/DCL/DD/0101411--9001--101



If the BSC is operational is duplex mode:

• If the link is reestablished during the chain switchover or chain restart, nomaintenance 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 vitalboards of the chain (SUP or CPUM board) is out of service, or becausethe Ethernet link between the active and the passive chain is faulty. Asa consequence, the chain did not have enough time to send amessage.Go to step 4.


Step Action

4 Use the TML to identify the faulty board (s). Then go to step 5.

5 If necessary replace the faulty board(s). The operations for return to service areperformed by the system. Then go to step 6.

Additional checks

Step Action


At the OMC--R, warning notifications (with fault number 13) allow to know if theBSC restarts correctly.

On--site, check that “12” is displayed in the SUP board display panels after theBSC start--up.

7 Check that the fault has disappeared.

Look at the alarm history file to see if the notification has been transferred there.





Fault number:20 : Alarm on clockship of the SUP boardType : communicationsAlarm


FAULT ANALYSIS

This notification indicates that there is a problemwith the clockship of the SUP board of thechain concerned.


BSC defenseNone.


None.

FAULT TREATMENT


Step Action

1 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.

2 Replace the SUPboard of the chain concerned by the fault (Field ReplaceableUnit)


b. The operations for return to service are performed by the system. Then go tostep 4.

3 Position the SW12 strap correctly. Then go to step 4.

Additional checks

Step Action

4 If necessary, clear the alarm concerning the SUP board.



PE/DCL/DD/0101411--9001--101


2.12 Fault number: 20 (BSC 12000 “HC”)

iii

Fault number:20 : Alarm on clockship of the SUP boardType : communicationsAlarm

FAULT ANALYSIS

This notification indicates that there is a problem with the clockship of the SUP2 board ofthe chain concerned.


BSC defense

None.


None.

FAULT TREATMENT


Step Action

1 Replace the SUP2 board of the chain concerned by the fault (Field ReplaceableUnit):


b. The operations for return to service are performed by the system. Then go tostep 2.

Additional checks

Step Action

2 If necessary, clear the alarm concerning the SUP2 board.





iii

Fault number:21 : Beginning of circular file pre--overflowType : qualityOfServiceAlarm

FAULT ANALYSIS

This notification is sent by the active chain and it indicates a pre--overflow beginning on oneof 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 Action

1 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 resultof 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.


PE/DCL/DD/0101411--9001--101



2 Check which type of circular file is mentioned in the notification (hardware faultnotifications, software anomalies, observation messages, event reports, etc.) toidentify which equipment of the BSS has a problem.

If a BTS is involved, perform the isolating procedure (lock the objectsconcerned), and then treat the problem. Then go to step 3.

If a TCU is involved, perform the isolating procedure (lock the transcoder andthe 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 Action

3 When the file is no longer saturated, a notification with fault number 22 (“End ofcircular file pre--overflow”) appears in the notification window.




iii

Fault number:22 : End of circular file pre--overflowType : qualityOfServiceAlarm

FAULT ANALYSIS

This notification indicates the end of the overflow of the circular file specified in the faultnumber 21.


BSC defense

None.


None.

FAULT TREATMENT


If this notification is not received quickly after the fault number 21 has been treated, checkthe state of the network by performing a “Display all” command. As a matter of fact, thetranscoder, transcoderBoard, pcmCircuit (A, Abis, and Ater), lapdLink and signallingLinkobjects may have undergone a state change.


PE/DCL/DD/0101411--9001--101



iii

Fault number:23 : Beginning of BSC disk partition updateType : qualityOfServiceAlarm

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 andthe 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





ooo

Fault number:24 : End of BSC disk partition updateType : qualityOfServiceAlarm

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



PE/DCL/DD/0101411--9001--101



oo

Fault number:26 : Fault on BSC/OMC--R linkType : communicationsAlarm

FAULT LOCATION

This notification indicates that the level 2 was not established or was lost on the link withthe BSC.

Either the link itself or the OMC--R broke down. After the link between the OMC--R and theBSC has been restored, the BSC sends this notification.

It indicates the date and time of the breakdown, and it can be used for investigationpurposes.


None.

BSC defense


None.

FAULT TREATMENT

None.

Just perform a “Display all” command to check the state of the bscMDInterface and the bscobject itself. If they are “enabled”, clear the fault alarm.




ppp

Fault number:33 : Saturation on an internal file used for marking climbType : processingErrorAlarm

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



PE/DCL/DD/0101411--9001--101



iii

Fault number:34 : Saturation on a storage zone for marking climbType : processingErrorAlarm

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--stringcharacter /O.


BSC defense

None.


None.

FAULT TREATMENT





ooo

Fault number:41 : Beginning of saturation of the event reporting process in the

BSCType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates that the queue corresponding to the priority level of the event isnearly full: the saturation is over 80%.

The queues act as buffers before the data are written on the BSC disk and the notificationsare 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.

Queue Partition Nb offiles

Filesid

Prioritylevel Size

Saturationmode:

overwritingallowed

Saturationthreshold msg type

0 (init) mb_ape 1 1 255 b yes 100% build

1 (transat) mb_ape 1 6 60 Kb yes 80% chgt_etatrep_diffacq_tge

2 (report) mb_evt 7 2 0 300 Kb yes 80% ctx_demmsg_purge

3 4 180 Kb yes 80% an_lg_majan_lg_min

4 1 1 Kb yes 80%

11 2 300 Kb yes 80%

12 3 1200 Kb yes 80% chgt_etat

13 1300 Kb yes 80% alar_majalar_mincr_testsig_op

value_chgsig_op_prioind_rgl_flux

16 100 Kb NO 100% grp_chgt_etat


PE/DCL/DD/0101411--9001--101


Queue msg typeSaturationthreshold

Saturationmode:

overwritingallowed

SizePrioritylevel

Filesid

Nb offiles

Partition

3 (obs)temporary

mb_obm 2 5 1000 Kb yes 80% observationstemporaryreal time 7 64 Kb yes 100% obs_warning

obs permanente

4 (path, trace)trace warning

mb_evt 2 8 100 Kb yes 80% call pathtrace warningwarning priority 9 16000 Kb yes 80% call trace

5 (sign, mark)marking

mb_evt 1 10 100 Kb yes 80% signaling

6 (update) mb_ape 2 14 255 b yes 100% build

6 (update) 15 20 Ko yes 80% chgt_etatacq_tge

Table 2--2 APE queues

Queue Content Size(in Kb)

Prioritylevel

Saturationthreshold

Acknowledgement

0 WARNING 20 queue usedduring BSCstart--up only

1 MSG_PURGE 50 0 (BSCevents)

2 INC_RES and CR_AUTOTESTfault numbers for classes:CAR_SIC_X25DEM_SICDDEM_SIC_CS7DEM_CPUECAR_DMUXCAR_UTECR_AUTOTEST fault number forCAR_BRAcodano_min = ANO_DMUX_00codano_max = ANO_DMUX_23codano_MIN =ANO_LBD_IOD_Mcodano_max =ANO_LDB_TRS_R2000G

64 1 (sites andTCUs statechanges) 90% No



Queue AcknowledgementSaturationthreshold

Prioritylevel

Size(in Kb)

Content

3 CHGT_ETATVALUE_CHGcodano DESINIT andCHGT_ETAT for classes:SUP_SITSUP_TCUSUP_PCMSUP_PCMA

64 2 (other statechanges)

4 ALAR_MAJALAR_MINCR_TESTCTX_DEMSIG_OPSIG_OP_PRIOcodano DESINIT andCHGT_ETAT for other classesthan:SUP_SITSUP_TCUSUP_PCMSUP_PCMA

40 3 (alarms andwarnings)

5 REP_DIFFAMPAN_LG_MAJAN_LG_MINcodano INC_RES andCR_AUTOTEST for classes:SUP_TCBSUP_TCUcodano_min = ANO_ALA_00codano_max = ANAO_ALA_47codano_min =VAL_SPT_ANO_ALA_70codano_max =VAL_SPT_ANO_ALA_74

10 4 (major andminor softwareanomalies)

6 SIG_MRQMARQUAGE

30 --

7 IND_RGL_FLUX 10 --

8 GRP_CHGT_ETAT 20 -- 99% Yes

Table 2--3 GES_SL queues


PE/DCL/DD/0101411--9001--101



BSC defense

None.


None. Nevertheless, all the following notifications (if any) may be lost.

FAULT TREATMENT

Preliminary checks

Step Action

1 Check which type of queue is mentioned in the notification (hardware faultnotifications, event reports, etc.):

If the queue concerns event reports, identify which equipment of the BSS hasa problem.

• If a BTS is involved, perform the isolating procedure (lock the objectsconcerned), and then treat the problem. Then go to step 2.

• If a TCU is involved, perform the isolating procedure (lock the transcoder andthe transcoderBoard objects), and then treat theproblem. Thengo to step 2.

• If the BSC is involved, call the manufacturer.

If the queue concerns state change notifications, check the state of the networkby performing a “Display all” command. As a matter of fact, the transcoder,transcoderBoard, pcmCircuit (A, Abis, and Ater), lapdLink and signallingLinkobjects may have undergone a state change.

Additional checks

Step Action

2 When the queue is no longer saturated, a notification with fault number 42 (“Endof saturation of the event reporting process”) appears in the notification window.




iii

Fault number:42 : End of saturation of the event reporting processType : processingErrorAlarm

FAULT ANALYSIS

This notification indicates that the queue is no longer saturated. The notification ofbeginning of saturation (with fault number 41) previously signaled the saturation. All thefollowing notifications (if any) will be displayed at the OMC--R.


BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101



ooo

Fault number:43 : Loss of access to the equipment shelfType : equipmentAlarm

The following Table 2--4 indicates the sources of the fault number 43. For moreinformation on each source and the associated corrective maintenance procedure,refer to the sheet indicated in the right column.

SourceNo. Source wording BSC

12000

BSC12000HC

Procedure

0 Cannot access to all working UTE x x 2.22.1

1 O&M bus selftest not OK x x 2.22.2

Table 2--4 Fault number 43 sources



2.22.1 Source: Cannot access to all working UTE

ooo

Fault number 43 Loss of access to the equipment shelf

Source: (0) Cannot access to all working UTEBSC model: 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, theassociated objects (pcmCircuit, etc.) are unconfigured.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 Check that all the boards are inaccessible by performing a “Display all” commandon the bsc object.

If they are inaccessible, go to step 2.

If not, clear the alarm.

2 Check that the ECI board is operational:

Look for a notification with fault number 7 “Card monitoring failure” concerningthe ECI board. It has been sent to the OMC--R either before or after faultnumber 43.

Check the state of the ECI board by performing a “Display all” command on thebsc object.

• If the ECI board is operational, one of the DDTI, BSCB or TSCB boards isfaulty. Go to step 4.

• If the ECI board is not operational, the DDTI, BSCB or TSCB boards cannotbe accessed anymore. Go to step 3.


PE/DCL/DD/0101411--9001--101



Step Action

3 Replace the ECI board (Field Replaceable Unit) (See NTP < 41 >).

4 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.

5 Replace the faulty board (Field Replaceable Unit) by following the procedure inNTP < 41 >:

BSCB board

TSCB board

DDTI board

6 Call the manufacturer.

Additional checks

Step Action

7 End. The procedure is complete.



2.22.2 Source: O&M bus selftest not OK

o

Fault number 43 Loss of access to the equipment shelf

Source: (1) O&M bus selftest not OKBSC model: 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 thepassive chain starts up, and also every 30 minutes.


BSC defense

When the selftest fails, the passive chain commits suicide, starts again, and also sends anotification 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 Action

1 Check the state of the ECI board.

If the ECI board is operational, one of theDDTI, BSCB or TSCB boards is faulty.Go to step 3.

If the ECI board is not operational, the DDTI, BSCB or TSCB boards cannot beaccessed anymore. Go to step 2.

2 Replace the ECI board (Field Replaceable Unit) (See NTP < 41 >).

3 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.


PE/DCL/DD/0101411--9001--101



4 Replace the faulty board (Field Replaceable Unit), by following the correctprocedure in NTP < 41 >:

BSCB board

TSCB board

DDTI board


Additional checks

Step Action





p

Fault number:44 : Board UTE access problemType : equipmentAlarm

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 thepassive 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 activechain.

FAULT TREATMENT

Preliminary checks

Step Action

1 Analyze the circumstances in which this notification with fault number 44appeared.

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.


PE/DCL/DD/0101411--9001--101



2 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 theproblem 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 ECIboard and the UTE boards is faulty. Go to step 4.


Step Action

3 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


4 Replace the ECI board (Field Replaceable Unit):

a. Refer to the replacement procedure (See NTP < 41 >).


Additional checks

Step Action




2.24 Fault number: 45 (BSC 12000)

iii

Fault number:45 : Partial hard disk degradationType : equipmentAlarm


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.

Beyonda first threshold, the disk performances are nomorenominal: thechain isdegraded.


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 simplexmode --, the chain commitssuicide, restarts, stops in the “0B” phase of the start--up or sometimes further, and sendsthis 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 Action

1 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 activechain” command.

– Then replace the MMU board on the new passive chain. Go to step 2.


PE/DCL/DD/0101411--9001--101



• If the passive chain is not operational:

– First fix the passive chain.

– Then perform a chain switchover from the OMC--R by performing a “Killactive chain” command.

– Lastly, replace the MMU board on the new passive chain. Go to step 2.

If the two chains are impacted:

• First fix the passive chain.

• Then perform a chain switchover from the OMC--R by performing a “Killactive chain” command.

• Lastly, replace the MMU board on the new passive chain. Go to step 2.


Step Action

2 Replace the MMU board (Field Replaceable Unit):

a. For more information, refer to the replacement procedure (see NTP < 41 >).


3 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 Action





iii

Fault number:45 : Partial hard disk degradationType : equipmentAlarm

FAULT ANALYSIS



Beyonda first threshold, the disk performances are nomorenominal: thechain isdegraded.


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 simplexmode --, the chain commitssuicide, restarts, stops in the “0B” phase of the start--up or sometimes further, and sendsthis 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 Action

1 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 activechain” command.

– Then replace the MMU_IDE board on the new passive chain. Go tostep 2.


PE/DCL/DD/0101411--9001--101



• If the passive chain is not operational:

– First fix the passive chain.

– Then perform a chain switchover from the OMC--R by performing a “Killactive chain” command.

– Lastly, replace the MMU_IDE board on the new passive chain. Go tostep 2.

If the two chains are impacted:

• First fix the passive chain.

• Then perform a chain switchover from the OMC--R by performing a “Killactive chain” command.

• Lastly, replace the MMU_IDE board on the new passive chain. Go to step 2.


Step Action

2 Replace the MMU_IDE board (Field Replaceable Unit):



3 Bring the new MMU_IDE board into service:




Additional checks

Step Action





iii

Fault number:46 : Total hard disk degradationType : equipmentAlarm


FAULT ANALYSIS



Beyond a first threshold, the disk performances are nomorenominal: the chain is degradedand 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 commitssuicide, 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 doesnot commit suicide, and just sends this notification.


None.


The BSC is in simplex mode.


PE/DCL/DD/0101411--9001--101


FAULT TREATMENT


Step Action

1 Replace the MMU board (Field Replaceable Unit) immediately:



2 Then bring the new MMU board into service:




Additional checks

Step Action





iii

Fault number:46 : Total hard disk degradationType : equipmentAlarm

FAULT ANALYSIS



Beyond a first threshold, the disk performances are nomorenominal: the chain is degradedand 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 commitssuicide, 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 doesnot commit suicide, and just sends this notification.


None.


The BSC is in simplex mode.


PE/DCL/DD/0101411--9001--101


FAULT TREATMENT


Step Action

1 Replace the MMU_IDE board (Field Replaceable Unit) immediately:



2 Then bring the new MMU_IDE board into service:




Additional checks

Step Action





iii

Fault number:47 : Cessation of active alarmsType : communicationsAlarm, environmentalAlarm, equipmentAlarm,

processingErrorAlarm, qualityOfServiceAlarm

FAULT ANALYSIS

Thenotification is sent during aBSC restart or a chain switchover. It indicates that old activealarms (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 chainswitchover, 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.

probableCause No.

probableCausewording Type of alarm clearing

64 bscRequest -- notification sent by the BSC-- purge performed by the BSC: consists in

sending a list of alarms which may be clearedby the OMC--R if they are still active

65 purgeOnSaturation -- notification sent by the MD-- the defense purge consists in clearing the

oldest alarms. The threshold is fixed by thestatic configuration.

66 dailyPurge -- notification sent by the MD-- the daily purge consists in clearing the alarms

that are older than N days, every day. N isfixed by the static configuration.


BSC defense

None.


None.

FAULT TREATMENT



PE/DCL/DD/0101411--9001--101



ii

Fault number:332 : External alarm loop 0Type : 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 isindicated in the wording of the alarm.


BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action

1 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 0if the external alarm loop is not used. Configure it by performing a “Set”command on the bsc object.

If the external alarm is not configured, “0” must be displayed. If not, configurethe alarm by performing a “Set” command on the bsc object. Then go to step 3.




Step Action

2 Perform the appropriate treatment. The operations for clearing this type of alarmdepend on how the alarm was programmed and thus they are determined by theoperator.

Additional checks

Step Action

3 Check that an end--of--fault message is generated when the alarm has beencleared.



PE/DCL/DD/0101411--9001--101



ii


FAULT ANALYSIS




BSC defense

None.


None.

FAULT TREATMENT

Preliminary checks

Step Action


