s8000 fault number description
DESCRIPTION
411-9001-101-15101TRANSCRIPT
Wireless Service Provider Solutions
Fault Number DescriptionVolume 1 of 9: BSC and TCUPE/DCL/DD/0101 15.101/EN Standard July 2005411--9001--101
Copyright © 1999--2005 Nortel Networks
< 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.
Copyright © 1999--2005 Nortel Networks
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
Issue 15.40/EN Preliminary
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
Issue 15.07/EN Standard
August 2004
Issue 15.06/EN Preliminary
General infrastructure and catalog cleanup
August 2004
Issue 15.05/EN Preliminary
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
Issue 15.04/EN Preliminary
CR Q00937998 -- Add Fault number 1315 and new description.
March 2004
Issue 15.01/EN Standard
System release: GSM/BSS V14.3
October 2003
Issue 14.04/EN Standard
Made corrections to links and references to other NTPs.
August 2003
Issue 14.03/EN Preliminary
Corrected CR Q00184679--02 by changing the 1074 fault number description into“indication of hardware in compatibility with activated features”
April 2003
Issue 14.02/EN Preliminary
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
Issue 14.01/EN Preliminary
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
System release: GSM/BSS V13
November 2002
Issue 13.07/EN Standard
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
Issue 13.05/EN Standard
Changed to standard
Issue 13.04/EN Preliminary
Minor Editorial Update
July 2002
Issue 13.03/EN Draft
Minor Editorial Update
March 2002
Issue 13.02/EN Standard
Changed to Standard
Minor Editorial Update
July 2001
Issue 13.01/EN Preliminary
Minor Editorial Update
Publication history Nortel Networks Confidentialvi
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
System release: GSM/BSS V12
September 2001
Issue 12.08/EN Standard
No update for V12.4C Customer Readiness release
June 2001
Issue 12.07/EN Preliminary
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
• updated for SR 30340599
• updated for SR 30343224
• updated for SR 30328937
September 2000
Issue 12.06/EN Standard
Minor Editorial update
June 2000
Issue 12.05/EN Preliminary
Minor Editorial update
Issue 12.04/EN Preliminary
The following changes were made in individual chapters:
Chapter 2 “BSC fault numbers”
• updated BSC fault number treatment procedures
Publication historyNortel Networks Confidential vii
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
November 1999
Issue 12.03/EN Standard
Minor Editorial Update
Issue 12.02/EN Standard
The following changes were made in individual chapters:
Chapter 2 “BSC fault numbers”
• updated BSC fault number treatment procedures
September 1999
Issue 12.01/EN Standard
Creation
Publication history Nortel Networks Confidentialviii
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
PAGE INTENTIONALLY LEFT BLANK
Table of contentsNortel Networks Confidential ix
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.11 Fault number: 20 (BSC 12000) Vol. 1 -- 2--85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.23 Fault number: 44 Vol. 1 -- 2--105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.24 Fault number: 45 (BSC 12000) Vol. 1 -- 2--107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.25 Fault number: 45 (BSC 12000 “HC”) Vol. 1 -- 2--109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.26 Fault number: 46 (BSC 12000) Vol. 1 -- 2--111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.27 Fault number: 46 (BSC 12000 “HC”) Vol. 1 -- 2--113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.58 Fault number: 520 (BSC 12000 “HC”) Vol. 1 -- 2--178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.59 Fault number: 521 Vol. 1 -- 2--180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.60 Fault number: 522 (BSC 12000) Vol. 1 -- 2--182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.61 Fault number: 522 (BSC 12000 “HC”) Vol. 1 -- 2--184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.62 Fault number: 523 Vol. 1 -- 2--186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.63 Fault number: 524 Vol. 1 -- 2--187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.64 Fault number: 601 (BSC 12000) Vol. 1 -- 2--189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.65 Fault number: 601 (BSC 12000 “HC”) Vol. 1 -- 2--191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.66 Fault number: 607 (BSC 12000) Vol. 1 -- 2--193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.67 Fault number: 607 (BSC 12000 “HC”) Vol. 1 -- 2--195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.68 Fault number: 617 Vol. 1 -- 2--197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.69 Fault number: 632 (BSC 12000) Vol. 1 -- 2--199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.70 Fault number: 632 (BSC 12000 “HC”) Vol. 1 -- 2--201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.71 Fault number: 633 Vol. 1 -- 2--203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.72 Fault number: 634 (BSC 12000) Vol. 1 -- 2--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.73 Fault number: 634 (BSC 12000 “HC”) Vol. 1 -- 2--206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.74 Fault number: 638 (BSC 12000) Vol. 1 -- 2--207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.75 Fault number: 638 (BSC 12000 “HC”) Vol. 1 -- 2--209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
11 : Restart after chain suicide due to NMI Vol. 1 -- 2--76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 : Chain restart in progress Vol. 1 -- 2--78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 : Indication of chain restart cause Vol. 1 -- 2--79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 : Chain restart due to intermediate card Vol. 1 -- 2--80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16 : Fault on active/passive chains link Vol. 1 -- 2--83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20 : Alarm on clockship of the SUP board Vol. 1 -- 2--85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20 : Alarm on clockship of the SUP board Vol. 1 -- 2--86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21 : Beginning of circular file pre--overflow Vol. 1 -- 2--87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 : End of circular file pre--overflow Vol. 1 -- 2--89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23 : Beginning of BSC disk partition update Vol. 1 -- 2--90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24 : End of BSC disk partition update Vol. 1 -- 2--91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26 : Fault on BSC/OMC--R link Vol. 1 -- 2--92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33 : Saturation on an internal file used for marking climb Vol. 1 -- 2--93. . . . . . . . . . . . . . . . . . . . . . .
34 : Saturation on a storage zone for marking climb Vol. 1 -- 2--94. . . . . . . . . . . . . . . . . . . . . . . . . . . .
41 : Beginning of saturation of the event reporting process in the BSC Vol. 1 -- 2--95. . . . . . . . . . .
42 : End of saturation of the event reporting process Vol. 1 -- 2--99. . . . . . . . . . . . . . . . . . . . . . . . . . .
43 : Loss of access to the equipment shelf Vol. 1 -- 2--100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Source: (0) Cannot access to all working UTE Vol. 1 -- 2--101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Source: (1) O&M bus selftest not OK Vol. 1 -- 2--103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44 : Board UTE access problem Vol. 1 -- 2--105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45 : Partial hard disk degradation Vol. 1 -- 2--107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45 : Partial hard disk degradation Vol. 1 -- 2--109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46 : Total hard disk degradation Vol. 1 -- 2--111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46 : Total hard disk degradation Vol. 1 -- 2--113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47 : Cessation of active alarms Vol. 1 -- 2--115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332 : External alarm loop 0 Vol. 1 -- 2--116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333 : External alarm loop 1 Vol. 1 -- 2--118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334 : External alarm loop 2 Vol. 1 -- 2--120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
335 : External alarm loop 3 Vol. 1 -- 2--122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
336 : External alarm loop 4 Vol. 1 -- 2--124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
337 : External alarm loop 5 Vol. 1 -- 2--126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338 : External alarm loop 6 Vol. 1 -- 2--128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
339 : External alarm loop 7 Vol. 1 -- 2--130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
404 : RCB0 failure Vol. 1 -- 2--142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
405 : RCB1 failure Vol. 1 -- 2--144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
406 : RCB2 failure Vol. 1 -- 2--146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
407 : RCB3 failure Vol. 1 -- 2--148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
408 : Power supply fault to the fans of the MPU shelf Vol. 1 -- 2--150. . . . . . . . . . . . . . . . . . . . . . . . . . .
411 : Power supply fault of the other chains MPU shelf Vol. 1 -- 2--153. . . . . . . . . . . . . . . . . . . . . . . . . .
412 : RCB4 failure Vol. 1 -- 2--155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
413 : Fault on the right MPU power supply Vol. 1 -- 2--157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
414 : Fan fault on EQPT and SWG shelf Vol. 1 -- 2--159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
415 : Power supply fault on SWG or SWT shelf Vol. 1 -- 2--161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
417 : Power supply fault on EQPT shelf Vol. 1 -- 2--163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
419 : Power supply fault on EQPI shelf Vol. 1 -- 2--165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
420 : Fan fault on the EQPI, EQPD0 and EQPD1 shelves Vol. 1 -- 2--167. . . . . . . . . . . . . . . . . . . . . . .
422 : Power supply fault to the fans of the equipment cabinet Vol. 1 -- 2--169. . . . . . . . . . . . . . . . . . . .
494 : Fault on ECI alarm loop Vol. 1 -- 2--171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
497 : New PCM selected as clock reference Vol. 1 -- 2--173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
: Fault on switching matrix access Vol. 1 -- 2--176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
520 : Fault on switching matrix access Vol. 1 -- 2--178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
521 : Fault on switching matrix Vol. 1 -- 2--180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
522 : Switch supervision failure Vol. 1 -- 2--182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
522 : Switch supervision failure Vol. 1 -- 2--184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
523 : Fault on internal PCM (BSC, TCU) Vol. 1 -- 2--186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
524 : Slave switch board not present Vol. 1 -- 2--187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
601 : File management error Vol. 1 -- 2--189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
601 : File management error Vol. 1 -- 2--191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
607 : Multibus II error Vol. 1 -- 2--193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
607 : Multibus II error Vol. 1 -- 2--195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
617 : SCSI bus controller error Vol. 1 -- 2--197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
632 : File management error Vol. 1 -- 2--199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
632 : File management error Vol. 1 -- 2--201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
633 : Disk driver error Vol. 1 -- 2--203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
634 : Mirror disk Vol. 1 -- 2--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
634 : Mirror disk Vol. 1 -- 2--206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
638 : Multibus II error Vol. 1 -- 2--207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
638 : Multibus II error Vol. 1 -- 2--209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
207 : Data link layer Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
208 : Access to interconnection area Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
209 : Data transport layer Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210 : Access to multibus II management coprocessor Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . .
211 : Switching matrix access and transmission protocol Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . .
212 : Switching matrix access Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213 : Protocol transmission layer 1 Vol. 1 -- 2--252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214 : SUP card access management Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215 : SCSI: bus management Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216 : SCSI: units logical management Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
217 : SCSI: bus controller management Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218 : SCSI: protocol management Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219 : X25 layer 1 and 2 Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220 : HDLC handler Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
221 : LAPB layer 2 Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222 : Passive chain restart inhibited to be manually activated Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . .
223 : Debug complementary information Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
224 : Instrumentation complementary information Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
225 : Ethernet driver Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
226 : 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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
245 : LDB CSP access cad Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
246 : Ethernet link access cad Vol. 1 -- 2--253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
247 : Disk I/O Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
248 : File management system Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249 : Disk driver Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250 : Mirror disk: services and user functions Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251 : Mirror disk: state machine Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
252 : Mirror disk: transmission protocol Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
253 : Transport data link Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
254 : Data link layer Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255 : Access to interconnection area Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
256 : Data transport layer Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257 : Access to multibus II management coprocessor Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . .
258 : Switching matrix access and transmission protocol Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . .
259 : Switching matrix access Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
260 : Protocol transmission layer 1 Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
261 : SUP card access management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
262 : SCSI: bus management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263 : SCSI: units logical management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
264 : SCSI: bus controler management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265 : SCSI: protocol management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
266 : X25 layer 1 and 2 Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267 : HDLC handler Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
268 : LAPB layer 2 Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
269 : FSM debug Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
270 : Tape drive management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
271 : Disk/tape copy tools management Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
272 : Ethernet driver Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
273 : Ethernet driver Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
276 : System card transmission Vol. 1 -- 2--254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
277 : System card transmission 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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
< 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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
PAGE INTENTIONALLY LEFT BLANK
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--1
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--3
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--4
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--5
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.2 Source: CPUE (MPU) non present
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
Another notification with fault number 7 “card monitoring failure” must have been sentbefore to report that a CPUE board is missing.
REACTION OF THE SYSTEM
BSC defense
The BSC is in simplex mode. The other chain restarts cyclically.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--6
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--7
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.3 Source: CPUE (MPU) or CPUM (OMU) built--in self test failed
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
REACTION OF THE SYSTEM
BSC defense
None. The BSC is in simplex mode.
Impact on the service
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.
2 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 or CPUM board.
i. Clear the alarm. Go to step 4.
ii. If the problem often happens, replace the CPUE or CPUM board. Go tostep 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--8
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
i. Treat these notifications.
ii. Then go to step 4.
On--site maintenance
Step Action
3 Replace the CPUE or CPUM 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 4.
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.
6 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--9
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.4 Source: CPUE (MPU) or CPUM (OMU) setup failed
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
REACTION OF THE SYSTEM
BSC defense
None. The BSC is in simplex mode.
Impact on the service
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 CPUM and CPUE board.
i. Clear the alarm. Go to step 4.
ii. If the problem often happens, replace the CPUE board. Go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--10
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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 CPUM orCPUE board of the chain that is out of order.
i. Treat these notifications.
ii. Then go to step 3.
On--site maintenance
Step Action
2 Replace the faulty 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) allow to know if the BSC restarts correctly.
4 If necessary, clear the alarm concerning the CPUE or CPUM board.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--11
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.5 Source: Incorrect Multibus II card name
II
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
If not, go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--12
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
5 Replace the faulty board (Field Replaceable Unit):
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
6 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
7 If necessary, clear the alarm concerning the replaced board.
8 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--13
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.6 Source: No communication with CPUE (MPU) card
III
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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”, 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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--14
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance
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 >.
b. The return to service operations are performed by the system. Go to step 4.
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the CPUE or SICD board.
6 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--15
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.7 Source: Error in BSC state machine handler (GAUT)
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--16
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.8 Source: Error in switchover sequence
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Treat the anomaly concerning the notification with fault number 7.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--17
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.9 Source: BDA KO during switchover sequence
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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 >).
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--18
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.10 Source: Invalid mirror partitions after switchover on the new activechain
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
There is loss of service because of two chain switchovers.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--19
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.11 Source: Loss of the duplex link detected on passive chain
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
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.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--20
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.12 Source: Inconsistency between active and passive chain
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--21
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.13 Source: Context overflow for BSC (MDB) defense
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
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.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--22
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.14 Source: Switching while passive chain DP loading
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
The service is lost.
FAULT TREATMENT
No maintenance is required. Look for the source of the first switchover.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--23
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.15 Source: Error detected during check partition
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
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.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--24
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.16 Source: CPUE BOOT flashing failed
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
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, 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 >.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--25
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.17 Source: Restart to take into account the new BSC customization
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (24) Restart to take into account the new BSCcustomization
BSC model: BSC12000 + BSC12000 “HC”
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--26
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.18 Source: Degraded disk
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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”, 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.
i. Clear the alarm. Go to step 4.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--27
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
i. Treat these notifications.
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.
On--site maintenance
Step Action
2 Replace the faulty MMU or MMU_IDE 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) allow to know if the BSC restarts correctly.
4 If necessary, clear the alarm concerning the MMU or MMU_IDE board.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--28
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.19 Source: Cancellation of probative phase
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
During the network unconfiguration and reconfiguration, an outagethat lasted less than five minutes happened.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--29
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.20 Source: End of probative phase OK
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--30
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.21 Source: New BDA edition
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
During the update of the new BDA, an outage that lasted less thanfive minutes happened.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--31
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.22 Source: Preparation of a type 5 upgrade
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--32
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.23 Source: Type 5 upgrade running
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--33
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.24 Source: Old release running on passive chain
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--34
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.25 Source: Unsuccessful preparation of a type 5 upgrade
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
The BSC takes into account the old software version and starts with the passive chain.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--35
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.26 Source: BDA inconsistency
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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:
a. Select the bsc object in the OMC--R Browser window.
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--36
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Execute a general audit to ensure that the BDE and the BDA are consistent:
a. Select the bsc object in the OMC--R Browser window.
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
5 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
6 If necessary, clear the alarm concerning the incoherent BDA.
7 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--37
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.27 Source: GES--MS / GES--SL are incoherent
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--38
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.28 Source: Passive chain does not answer on RGA request
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--39
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.29 Source: Passive chain suicide on RGA request
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--40
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.30 Source: No communication with switching board
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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 “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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--41
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
i. Clear the alarm. Go to step 6.
ii. If this problem often happens, the board replacement must be considered.Go to step 4.
If the board state is “faulty”:
i. Treat the alarm with fault number 520 or 521 or 522.
ii. Then go to step 5.
On--site maintenance
Step Action
4 Replace the SWC board quoted in the beginning--of hardware fault notification(Field Replaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 5.
Additional checks
Step Action
5 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
6 If necessary, clear the alarm concerning the SWC board.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--42
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.31 Source: No communication with ECI card or fault on ECI card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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).
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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 “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 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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--43
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Performa “Display chain information” command to check the state of theECIboard.
If the board state is “working”, this fault number indicates a transient problemor a bad operation of the board concerned.
i. Clear the alarm. Go to step 7.
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 7.
ii. Then go to step 7.
On--site maintenance
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):
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 7.
6 Replace the SICX board (Field Replaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 7.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--44
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
7 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
8 If necessary, clear the alarm concerning the board.
9 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--45
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.32 Source: No communication with SICX card or fault on SICX card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (103) No communication with SICX card or fault on SICXcard
BSC model: BSC12000 + BSC12000 “HC”
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because it lostcontact with the SICX board.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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 “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 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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--46
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Perform a “Display chain information” command to check the state of the SICXboard.
If the board state is “working”, this fault number indicates a transient problemor a bad operation of the board concerned.
i. Clear the alarm. Go to step 6.
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 7.
ii. Then go to step 5.
On--site maintenance
Step Action
4 Replace the SICX board quoted in the beginning--of hardware fault notification:
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 5.
Additional checks
Step Action
5 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
6 If necessary, clear the alarm concerning the SICX board.
7 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--47
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.33 Source: No communication with slave switching board
5_10
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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”, 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.
If the value of the “bsc” field” is “simplex”, go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--48
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance
Step Action
3 Replace the switching board quoted in the beginning--of hardware fault notification:
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 4.
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the replaced switching board.
6 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--49
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.34 Source: No communication with SLS card or fault on SLS card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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
1 Check the state of the BSC, by performing a “Display all” command on the bscobject.
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--50
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance
Step Action
4 Replace the SLS or SLS2 board quoted in the beginning--of hardware faultnotification:
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 5.
Additional checks
Step Action
5 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
6 If necessary, clear the alarm concerning the SLS or SLS2 board.
7 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--51
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.35 Source: Operator request
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (106) Operator requestBSC model: BSC12000 + BSC12000 “HC”
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because theoperator requested it.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
CAUTIONService interruption
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
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--52
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.36 Source: Degraded REM link
ii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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”.
a. Treat this notification.
b. Then go to step 2.
Additional checks
Step Action
2 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
3 If necessary, clear the alarm concerning the REM link.
4 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--53
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.37 Source: No communication with SICD or RCB card or fault on SICDor RCB card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (128) No communication with SICD or RCB card or fault onSICD or RCB card
BSC model: BSC12000 + BSC12000 “HC”
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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
1 Check the state of the BSC, by performing a “Display all” command on the bscobject.
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--54
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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 405 “RCB1 failure” concerning the RCB 1 board quoted in therestart notification
with fault number 406 “RCB2 failure” concerning the RCB 2 board quoted in therestart notification
with fault number 407 “RCB3 failure” concerning the RCB 3 board quoted in therestart notification
with fault number 412 “RCB4 failure” concerning the RCB 4 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.
On--site maintenance
Step Action
4 Replace the SICD board quoted in the beginning--of hardware fault notification(Field Replaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--55
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
5 Replace theRCBboardquoted in thebeginning--of hardware fault notification (FieldReplaceable Unit):
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 6.
Additional checks
Step Action
6 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
7 If necessary, clear the alarm concerning the replaced board.
8 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--56
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.38 Source: SICD port selftests not OK
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None, as long as the chain remains passive.
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”, 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.
If the value of the “bsc” field” is “simplex”, go to step 3.
2 Look for a notification or an alarm with fault number 1153 “Negative test on passivechain LAPD channel (layer 2)”.
a. Treat this notification.
b. Then go to step 4.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--57
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Look for a notification or an alarm with fault number 8 “Negative built--in self--testfor card” concerning the SICD boards.
a. Treat this notification.
b. Then go to step 4.
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the SICD ports.
6 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--58
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.39 Source: No communication with CCS7 card or fault on CCS7 card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (161) No communication with CCS7 card or fault on CCS7card
BSC model: BSC12000 + BSC12000 “HC”
FAULT ANALYSIS
This notification indicates that a chain committed suicide and restarted because its CPUMboard (CPU--OMU) lost contact with a CCS7 board.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
If the value of the “bsc” field” is “simplex”, go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--59
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
a. Treat this notification.
b. Then go to step 4.
On--site maintenance
Step Action
3 Replace the CCS7 board quoted in the beginning--of hardware fault notification:
a. Refer to the replacement procedure given in NTP < 41 >.
b. The return to service operations are performed by the system. Go to step 4.
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the replaced CCS7 board.
6 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--60
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.40 Source: CCS7 port selftests not OK
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
If the value of the “bsc” field” is “simplex”, go to step 3.
2 Look for a notification or an alarm with fault number 1154 “Negative test on passivechain CCS7 signalling link (layer 2)”.
a. Treat this notification.
b. Then go to step 4.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--61
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Look for a notification or an alarm with fault number 8 “Negative built--in self--testfor card” concerning the CCS7 boards.
a. Treat this notification.
b. Then go to step 4.
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the CCS7 ports.
6 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--62
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.1.41 Source: No communication with TCU card or fault on TCU card
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
Source: (176) No communication with TCU card or fault on TCUcard
BSC model: BSC12000 + BSC12000 “HC”
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
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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”.
CAUTIONService interruption
The network is not operational. There is no service.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--63
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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 “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 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 405 “RCB1 failure” concerning the RCB 1 board
with fault number 406 “RCB2 failure” concerning the RCB 2 board
with fault number 407 “RCB3 failure” concerning the RCB 3 board
with fault number 412 “RCB4 failure” concerning the RCB 4 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
a. Treat this notification.
b. Then go to step 4.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--64
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
4 Check that the repaired chain does not commit suicide again. Warning notifications(with fault number 13) allow to know if the BSC restarts correctly.
5 If necessary, clear the alarm concerning the TCU access.
6 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--65
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.1.42 Source: O&M bus self--tests not OK
iii
Fault number 5 Restart after chain suicide due to internal cause, orOMC
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.
The passive chain sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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 “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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--66
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
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
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 O&M bus.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--67
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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.
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
CAUTIONService interruption
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--68
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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)
REACTION OF THE SYSTEM
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.
The chain concerned sends this notification as soon as the duplex link is open.
Impact on the service
If a control cabinet board or the ECI board is involved, there is not any impact on the service.
CAUTIONService interruption
If an equipment cabinet board (UTEboard) is concerned, then thereis a loss of service.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--69
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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 boards state is “working”, clear the alarm. Go to step 8.
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--70
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--71
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
9 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--72
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
REACTION OF THE SYSTEM
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.
The chain concerned sends this notification as soon as the duplex link is open.
Impact on the service
If a control cabinet board or the ECI board is involved, there is not any impact on the service.
CAUTIONService interruption
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 boards state is “working”, clear the alarm. Go to step 4.
If the state of the board quoted in the notification is “faulty”, replace the faultyboard. Go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--73
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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
b. The operations for return to service are performed by the system.
c. Then go to step 3.
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.
4 If necessary, clear the alarm concerning the replaced board.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--74
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--75
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
b. Then go to step 7.
On--site maintenance
Step Action
5 Replace the faulty SUP board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
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):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The return to service operations are performed by the system. Then go tostep 7.
Additional checks
Step Action
7 Check that the repaired chain is operational and does not commit suicide again:
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.
8 If necessary, clear the alarm concerning the replaced board.
9 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--76
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
If it is the passive chain, it starts again.
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.
The chain concerned sends this notification as soon as the duplex link is open.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--77
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
b. Then go to step 7.
On--site maintenance
Step Action
5 Replace the faulty SUP2 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The return to service operations are performed by the system. Then go tostep 7.
6 Replace the faulty CPUM board (CPU133IE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The return to service operations are performed by the system. Then go tostep 7.
Additional checks
Step Action
7 Check that the repaired chain is operational and does not commit suicide again:
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 SUP2 board display panels after theBSC start--up.
8 If necessary, clear the alarm concerning the replaced board.
9 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--78
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--79
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.8 Fault number: 14
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
ON--SITE MAINTENANCE
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--80
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.9 Fault number: 15iii
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
If not, go to step 3.
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--81
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance using the OMC--R
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--82
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
8 Check that the repaired chain is operational and does not commit suicide again:
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.
9 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--83
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.10 Fault number: 16
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
REACTION OF THE SYSTEM
BSC defense
The passive chain (not mentioned in the notification) restarts.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--84
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance
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
6 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.
7 Check that the fault has disappeared.
Look at the alarm history file to see if the notification has been transferred there.
8 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--85
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.11 Fault number: 20 (BSC 12000)iii
Fault number:20 : Alarm on clockship of the SUP boardType : communicationsAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.12.
FAULT ANALYSIS
This notification indicates that there is a problemwith the clockship of the SUP board of thechain concerned.
REACTION OF THE SYSTEM
BSC defenseNone.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
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)
a. Refer to the replacement procedure (see NTP < 41 >).
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.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--86
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the SUP2 board of the chain concerned by the fault (Field ReplaceableUnit):
a. Refer to the replacement procedure (see NTP < 41 >).
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.
3 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--87
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.13 Fault number: 21
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--88
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--89
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.14 Fault number: 22
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--90
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.15 Fault number: 23
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
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--91
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.16 Fault number: 24
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--92
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.17 Fault number: 26
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.
REACTION OF THE SYSTEM
None.
BSC defense
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--93
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.18 Fault number: 33
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--94
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.19 Fault number: 34
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--95
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.20 Fault number: 41
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
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--96
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
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
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--97
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--98
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--99
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.21 Fault number: 42
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--100
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.22 Fault number: 43
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
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--101
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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.
REACTION OF THE SYSTEM
BSC defense
The active chain commits suicide and a chain switchover is performed. Besides, theassociated objects (pcmCircuit, etc.) are unconfigured.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--102
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--103
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
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.
REACTION OF THE SYSTEM
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”.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--104
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Replace the faulty board (Field Replaceable Unit), by following the correctprocedure in NTP < 41 >:
BSCB board
TSCB board
DDTI board
5 Call the manufacturer.
Additional checks
Step Action
6 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--105
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.23 Fault number: 44
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
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--106
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
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.
On--site maintenance
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
b. Then go to step 5.
4 Replace the ECI board (Field Replaceable Unit):
a. Refer to the replacement procedure (See NTP < 41 >).
b. Then go to step 5.
Additional checks
Step Action
5 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--107
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.24 Fault number: 45 (BSC 12000)
iii
Fault number:45 : Partial hard disk degradationType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.25.
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.
REACTION OF THE SYSTEM
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.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--108
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
• If the passive chain is not operational:
– First fix the passive chain.
– Then perform a chain switchover from the OMC--R by performing a “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.
On--site maintenance
Step Action
2 Replace the MMU board (Field Replaceable Unit):
a. For more information, refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
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
4 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--109
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.25 Fault number: 45 (BSC 12000 “HC”)
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.
REACTION OF THE SYSTEM
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.
Impact on the service
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.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--110
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
• If the passive chain is not operational:
– First fix the passive chain.
– Then perform a chain switchover from the OMC--R by performing a “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.
On--site maintenance
Step Action
2 Replace the MMU_IDE board (Field Replaceable Unit):
a. For more information, refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
3 Bring the new MMU_IDE 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
4 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--111
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.26 Fault number: 46 (BSC 12000)
iii
Fault number:46 : Total hard disk degradationType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.27.
FAULT ANALYSIS
This notification indicates that the BSC disk of the chain considered is partially degraded.
The errors on disk access (reading and writing) are counted.
Beyond a first threshold, the disk performances are 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.
REACTION OF THE SYSTEM
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.
Impact on the service
None.
CAUTIONService interruption
The BSC is in simplex mode.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--112
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU board (Field Replaceable Unit) immediately:
a. For more information, refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
2 Then 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
3 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--113
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.27 Fault number: 46 (BSC 12000 “HC”)
iii
Fault number:46 : Total 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.
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.
REACTION OF THE SYSTEM
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.
Impact on the service
None.
CAUTIONService interruption
The BSC is in simplex mode.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--114
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU_IDE board (Field Replaceable Unit) immediately:
a. For more information, refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
2 Then bring the new MMU_IDE 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
3 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--115
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.28 Fault number: 47
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--116
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.29 Fault number: 332
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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--117
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--118
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.30 Fault number: 333
ii
Fault number:333 : External alarm loop 1Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--119
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--120
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.31 Fault number: 334
ii
Fault number:334 : External alarm loop 2Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--121
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--122
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.32 Fault number: 335
iii
Fault number:335 : External alarm loop 3Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--123
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--124
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.33 Fault number: 336
oo
Fault number:336 : External alarm loop 4Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--125
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--126
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.34 Fault number: 337
iii
Fault number:337 : External alarm loop 5Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--127
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--128
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.35 Fault number: 338
iii
Fault number:338 : External alarm loop 6Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--129
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--130
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.36 Fault number: 339
iii
Fault number:339 : External alarm loop 7Type : 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.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
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.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--131
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
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.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--132
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.37 Fault number: 400
iii
Fault number:400 : Breakdown of one power supply of the EQPD1 shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: aPSUE power supply located in the EQPD1 shelf.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
The system continues to operate normally if only one PSUE power supply failed.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 400have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the PSUE power supply. Go to step 6.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thePSUE power supply or the cables. Go to step 2.
2 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 5.
If the “internal DMUX state” is “working”, go to step 3.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--133
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Perform a “Display chain information” command on the bsc object to check thePSUE power supply state.
If the “EQPD1 converter” state is “at least one failed”, go to step 4.
If the “EQPD1 converter” state is “all working”, go to step 7.
On--site maintenance
Step Action
4 Confirm the failed PSUE power supply by using a voltmeter to measure the outputvoltage on the front panel V test points (see NTP < 41 >).
The voltage must be 5.2 V (¦2%).
If the voltage is incorrect, the PSUE power supply must be replaced. Go tostep 6.
5 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 8.
6 Replace the faulty PSUE power supply (Field Replaceable Unit) in the BSCequipment cabinet:
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 8.
7 Check the cables connected to the PSUE power supply.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 8.
Additional checks
Step Action
8 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
9 Clear the alarm if necessary.
10 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--134
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.38 Fault number: 401
iii
Fault number:401 : Breakdown of one power supply of the EQPD0 shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: aPSUE power supply located in the EQPD0 shelf.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
The system continues to operate normally if only one PSUE power supply failed.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 401have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the PSUE power supply. Go to step 6.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thePSUE power supply or the cables. Go to step 2.
2 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 5.
If the “internal DMUX state” is “working”, go to step 3.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--135
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Perform a “Display chain information” command on the bsc object to check thePSUE power supply state.
If the “EQPD0 converter” state is “at least one failed”, go to step 4.
If the “EQPD0 converter” state is “all working”, go to step 7.
On--site maintenance
Step Action
4 Confirm the failed power supply by using a voltmeter to measure the output voltageon the front panel V test points (see NTP < 41 >).
The voltage must be 5.2 V (¦2%).
If the voltage is incorrect, the PSUE power supply must be replaced. Go tostep 6.
5 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 8.
6 Replace the faulty PSUE power supply (Field Replaceable Unit) in the BSCequipment cabinet:
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 8.
7 Check the cables connected to the PSUE power supply.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 8.
Additional checks
Step Action
8 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
9 Clear the alarm if necessary.
10 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--136
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.39 Fault number: 402
iii
Fault number:402 : Fan fault on the MPU shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:a MPU ventilation block located in the control cabinet.
The chain concerned (active or passive) is the chain that emitted this notification.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If the chain concerned has not been powered off, there is a problem with thedetection of the faults concerning the ventilation blocks. The faulty item ofequipment can be one of the following:
• one or several straps on theMPUbackpanel are badly positioned ormissing.Go to step 2.
• the ECI board. Go to step 3.
• the cables connected to the ventilation blocks and the ECI board. Go tostep 4.
If the chain concerned has been powered off, check that the ventilation blocksare running: perform a “Display chain information” command to check theirstate.
• If their state is “one faulty”, replace the ventilation block. Go to step 8.
• If their state is “all working”, go to step 5.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--137
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 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 BSC Reference NTP. Thengo to step 9.
If the straps are operational, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, replace the ECI board (FieldReplaceable Unit). Refer to the replacement procedure (see NTP < 41 >).Then go to step 9.
If the “internal DMUX state” is “working”, go to step 4.
4 Check the cables connected to the ventilation blocks and to the ECI board.
If they are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 9.
5 Check the power fuse of the ventilation block, on the VENT board (seeNTP < 41 >).
Si the fuse is operational, replace the VENT board. Go to step 7.
Si the fuse is not operational, replace it. Go to step 6.
6 Replace the power fuse of the ventilation block, on the VENT board (FieldReplaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 9.
7 Replace the VENT board.
If the problem is over, go to step 9.
If the fault persists, replace the ventilation block. Go to step 8.
8 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 9.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--138
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
9 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
10 If necessary, clear the alarm.
11 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--139
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.40 Fault number: 403
iii
Fault number:403 : Fan fault on the MPU shelfs power supplyType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:a PSUC ventilation block located in the control cabinet.
The chain concerned (active or passive) is the chain that emitted this notification.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If the chain concerned has not been powered off, there is a problem with thedetection of the faults concerning the ventilation blocks. The faulty item ofequipment can be one of the following:
• one or several straps on theMPUbackpanel are badly positioned ormissing.Go to step 2.
• the ECI board. Go to step 3.
• the cables connected to the ventilation blocks and the ECI board. Go tostep 4.
If the chain concerned has been powered off, check that the ventilation blocksare running: perform a “Display chain information” command to check theirstate.
• If their state is “one faulty”, replace the ventilation block. Go to step 8.
• If their state is “all working”, go to step 5.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--140
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 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 9.
If the straps are operational, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, replace the ECI board (FieldReplaceable Unit). Refer to the replacement procedure (see NTP < 41 >).Then go to step 9.
If the “internal DMUX state” is “working”, go to step 4.
4 Check the cables connected to the ventilation blocks and to the ECI board.
If they are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 9.
5 Check the power fuse of the ventilation block, on the EXTR board (seeNTP < 41 >).
If the fuse is operational, replace the EXTR board. Go to step 7.
If the fuse is not operational, replace it. Go to step 6.
6 Replace the power fuse of the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 9.
7 Replace the EXTR board.
If the problem is over, go to step 9.
If the fault persists, replace the ventilation block. Go to step 8.
8 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 9.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--141
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Additional checks
Step Action
9 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
10 If necessary, clear the alarm.
11 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--142
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.41 Fault number: 404
iii
Fault number:404 : RCB0 failureType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the RCB 0 board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 3.
If the “internal DMUX state” is “working”, go to step 2.
2 Perform a “Display chain information” command to check the state of the RCB0board.
If the board state is “absent”, replace the RCB 0 board. Go to step 4.
If the board state is “present”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--143
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Treat the notification concerning the ECI board. Then go to step 6.
4 Replace the RCB0 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional steps
Step Action
5 Check that the repaired chain is operational and does not commit suicide again:
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 or SUP2 board display panelsafter the BSC start--up.
6 If necessary, clear the alarm concerning the RCB0 board.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--144
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.42 Fault number: 405
iii
Fault number:405 : RCB1 failureType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the RCB 1 board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 3.
If the “internal DMUX state” is “working”, go to step 2.
2 Perform a “Display chain information” command to check the state of the RCB 1board.
If the board state is “absent”, replace the RCB 1 board. Go to step 4.
If the board state is “present”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--145
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Treat the notification concerning the ECI board. Then go to step 6.
4 Replace the RCB 1 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional steps
Step Action
5 Check that the repaired chain is operational and does not commit suicide again:
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 or SUP2 board display panelsafter the BSC start--up.
6 If necessary, clear the alarm concerning the RCB 1 board.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--146
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.43 Fault number: 406
iii
Fault number:406 : RCB2 failureType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the RCB 2 board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 3.
If the “internal DMUX state” is “working”, go to step 2.
2 Perform a “Display chain information” command to check the state of the RCB 2board.
If the board state is “absent”, replace the RCB 2 board. Go to step 4.
If the board state is “present”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--147
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Treat the notification concerning the ECI board. Then go to step 6.
4 Replace the RCB 2 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional steps
Step Action
5 Check that the repaired chain is operational and does not commit suicide again:
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 or SUP2 board display panelsafter the BSC start--up.
6 If necessary, clear the alarm concerning the RCB 2 board.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--148
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.44 Fault number: 407
iii
Fault number:407 : RCB3 failureType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the RCB 3 board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 3.
If the “internal DMUX state” is “working”, go to step 2.
2 Perform a “Display chain information” command to check the state of the RCB 3board.
If the board state is “absent”, replace the RCB 3 board. Go to step 4.
If the board state is “present”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--149
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Treat the notification concerning the ECI board. Then go to step 6.
4 Replace the RCB 3 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional steps
Step Action
5 Check that the repaired chain is operational and does not commit suicide again:
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 or SUP2 board display panelsafter the BSC start--up.
6 If necessary, clear the alarm concerning the RCB 3 board.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--150
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.45 Fault number: 408
iii
Fault number:408 : Power supply fault to the fans of the MPU shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: thepower supply of the MPU ventilations blocks.
REACTION OF THE SYSTEM
BSC defense
The ECI board switches off the two power supplies of the concerned chain.
Impact on the service
None. The BSC is in simplex mode.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If the chain concerned has not been powered off, there is a problem with thedetection of the faults concerning the ventilation blocks. The faulty item ofequipment can be one of the following:
• one or several straps on theMPUbackpanel are badly positioned ormissing.Go to step 2.
• the ECI board is faulty. Go to step 3.
• the cables connected to the ventilation blocks and the ECI board. Go tostep 4.
If the chain concerned has been powered off, check that the ventilation blocksare running: perform a “Display chain information” command to check theirstate.
• If their state is “one faulty”, replace the ventilation block. Go to step 8.
• If their state is “all working”, go to step 5.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--151
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 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 BSC Maintenance NTP .Then go to step 9.
If the straps are operational, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, replace the ECI board (FieldReplaceable Unit). Refer to the replacement procedure (see NTP < 41 >).Then go to step 9.
If the “internal DMUX state” is “working”, go to step 4.
4 Check the cables connected to the ventilation blocks and to the ECI board.
If they are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 9.
5 Check the general power supply fuse of the terminal block (VENT MPUA, or VENTMPUB, see NTP < 41 >).
If the fuse is operational, go to step 6.
If not, replace it. Then go to step 9.
6 Check the power fuses of the fans (see NTP < 41 >). They are located on theVENT board.
If the fuses are operational, replace the VENT board. Go to step 7.
If not, replace them. Then go to step 9.
7 Replace the VENT board.
If the problem is over, go to step 9.
If the fault persists, replace the ventilation block. Go to step 8.
8 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 9.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--152
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
9 Perform a “Display chain information” command on the bsc object to check that theequipment has returned to correct operation.
10 If necessary, clear the alarm.
11 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--153
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.46 Fault number: 411
iii
Fault number:411 : Power supply fault of the other chains MPU shelfType : equipmentAlarm
FAULT ANALYSIS
This notification is emitted by the active chain only and it indicates that there is a problemwith the power supply units (PSUC) of the passive chain.
Location fields identify the object that detected the fault.
REACTION OF THE SYSTEM
BSC defense
The passive chain is not supplied anymore. The BSC is in simplex mode.
However, if the ECI board misfunctioned and could not detect the fault on the ventilationsblocks, the chain has not been powered off and is still running.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the chain that detected the faultto check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard.
If the “internal DMUX state” is “working”, go to step 2.
On--site maintenance
Step Action
2 Check the general power supply fuse of the terminal block (see NTP < 41 >).
If the fuse is operational, go to step 3.
If not, replace it.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--154
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Replace the power supply (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 4.
Additional checks
Step Action
4 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
5 If necessary, clear the alarm.
6 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--155
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.47 Fault number: 412
iii
Fault number:412 : RCB4 failureType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the faulty element: theRCB 4 board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None, if the other chain is operational.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Go to step 3.
If the “internal DMUX state” is “working”, go to step 2.
2 Perform a “Display chain information” command to check the state of the RCB 4board.
If the board state is “absent”, replace the RCB 4 board. Go to step 4.
If the board state is “present”, clear the alarm. Go to step 6.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--156
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Treat the notification concerning the ECI board. Then go to step 6.
4 Replace the RCB 4 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional steps
Step Action
5 Check that the repaired chain is operational and does not commit suicide again:
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 or SUP2 board display panelsafter the BSC start--up.
6 If necessary, clear the alarm concerning the replaced board.
7 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--157
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.48 Fault number: 413
iii
Fault number:413 : Fault on the right MPU power supplyType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that detected the fault and the suspected element: theright power supply unit (PSUC) in the control cabinet.
REACTION OF THE SYSTEM
BSC defense
The passive chain commits suicide and restarts cyclically because CPUE boards are nolonger supplied.
Impact on the service
None.
However, some boards of the chain no longer receive power supply (SICD boards andCPUE boards).
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If the chain concerned is operational, there is a problemwith the detection of thefaults concerning the power supply. The faulty item of equipment can be one ofthe following:
• one or several straps on theMPUbackpanel are badly positioned ormissing.Go to step 2.
• the ECI board of the chain that emitted this notification. Go to step 3.
If the chain concerned restarts cyclically, check that alarms concerning theCPUE boards are emitted. Then go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--158
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 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 BSC Maintenance NTP .Then go to step 9.
If the straps are operational, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, replace the ECI board (FieldReplaceable Unit). Refer to the replacement procedure (see NTP < 41 >).Then go to step 9.
If the “internal DMUX state” is “working”, go to step 4.
4 Identify the faulty power supply unit (PSUC) using a voltmeter to measure theoutput voltage at the front panel V test points (see NTP < 41 >).
If the voltage is correct, call the manufacturer.
If the voltage is incorrect, go to step 5.
5 Replace the power supply unit (PSUC) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 5.
Additional checks
Step Action
6 Check that an end--of--fault message is issued when the alarm is cleared.
7 End. The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--159
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.49 Fault number: 414
iii
Fault number:414 : Fan fault on EQPT and SWG shelfType : equipmentAlarm
FAULT ANALYSIS
The alarm identifies the object that has detected the fault and the suspected element: oneof the ventilation blocks of the equipment cabinet in the EQPT or SWG shelf.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check that:
If theBSC is in duplexmode,check howmany notificationswith fault number 414have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thepower supply or the cables. Go to step 2.
2 Perform a “Display chain information” command on the bsc object to check the ECIboard state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 4.
If the “internal DMUX state” is “working”, go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--160
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Check the power fuse of the fan on the VENT board.
If the fuse is operational, go to step 5.
If the fuse is not operational, go to step 6.
4 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 8.
5 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 8.
6 Replace the fuse (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 8.
7 Check the cables connected to the PSUE power supply and the ventilation blocks.
If the cables are operational, call the manufacturer.
If not, fix them. Then go to step 8.
Additional checks
Step Action
8 Check that an end--of--fault message is issued when the alarm is cleared.
9 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--161
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.50 Fault number: 415iii
Fault number:415 : Power supply fault on SWG or SWT shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the power supply unit (PSUE) in the SWG shelf in the equipment cabinet.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The system continues to operate normally if only one PSUE failed.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 415have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the PSUE power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thePSUE power supply or the cables. Go to step 2.
2 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 5.
If the “internal DMUX state” is “working”, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check thePSUE power supply state.
If the “swd converter” state is “at least one failed”, go to step 4.
If the “swd converter” state is “all working”, go to step 9.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--162
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
4 Identify the faulty power supply unit (PSUE) usingavoltmeter tomeasure theoutputvoltage at the front panel V test points (see NTP < 41 >).
The measured voltage must be between 5.2 V (±2%).
If the voltage is correct, go to step 7.
If the voltage is incorrect, go to step 6.
5 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 10.
6 Replace the power supply unit (PSUE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
7 Check the PSUE fuse.
If the fuse is operational, check the cables. Go to step 9.
If not, replace it. Go to step 8.
8 Replace the PSUE fuse (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
9 Check the cables connected to the PSUE power supply.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 10.
Additional checks
Step Action
10 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
11 If necessary, clear the alarm.
12 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--163
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.51 Fault number: 417iii
Fault number:417 : Power supply fault on EQPT shelfType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:a power supply unit (PSUE) in the EQPT shelf, in the equipment cabinet.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The system continues to operate normally if only one PSUE failed.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 417have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the PSUE power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thePSUE power supply or the cables. Go to step 2.
2 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 5.
If the “internal DMUX state” is “working”, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check thePSUE power supply state.
If the “eqpt converter” state is “at least one failed”, go to step 4.
If the “eqpt converter” state is “all working”, go to step 9.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--164
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
4 Identify the faulty power supply unit (PSUE) usingavoltmeter tomeasure theoutputvoltage at the front panel V test points (see NTP < 41 >).
The measured voltage must be between 5.2 V (±2%).
If the voltage is correct, go to step 7.
If the voltage is incorrect, go to step 6.
5 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 10.
6 Replace the power supply unit (PSUE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
7 Check the PSUE fuse.
If the fuse is operational, check the cables. Go to step 9.
If not, replace it. Go to step 8.
8 Replace the PSUE fuse (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
9 Check the cables connected to the PSUE power supply.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 10.
Additional checks
Step Action
10 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
11 If necessary, clear the alarm.
12 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--165
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.52 Fault number: 419iii
Fault number:419 : Power supply fault on EQPI shelfType : Equipment alarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the power supply unit (PSUE) in the EQPI shelf, in the equipment cabinet.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The system continues to operate normally if only one PSUE failed.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 419have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the PSUE power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thePSUE power supply or the cables. Go to step 2.
2 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 5.
If the “internal DMUX state” is “working”, go to step 3.
3 Perform a “Display chain information” command on the bsc object to check thePSUE power supply state.
If the “eqpi converter” state is “at least one failed”, go to step 4.
If the “eqpi converter” state is “all working”, go to step 9.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--166
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
4 Identify the faulty power supply unit (PSUE) usingavoltmeter tomeasure theoutputvoltage at the front panel V test points (see NTP < 41 >).
The measured voltage must be between 5.2 V (±2%).
If the voltage is correct, go to step 7.
If the voltage is incorrect, go to step 6.
5 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 10.
6 Replace the power supply unit (PSUE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
7 Check the PSUE fuse.
If the fuse is operational, check the cables. Go to step 9.
If not, replace it. Go to step 8.
8 Replace the PSUE fuse (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
9 Check the cables connected to the PSUE power supply.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 10.
Additional checks
Step Action
10 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
11 If necessary, clear the alarm.
12 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--167
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.53 Fault number: 420
iii
Fault number:420 : Fan fault on the EQPI, EQPD0 and EQPD1 shelvesType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:a ventilation block in the equipment cabinet.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If theBSC is in duplexmode,check howmany notificationswith fault number 420have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thepower supply or the cables. Go to step 2.
2 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 4.
If the “internal DMUX state” is “working”, go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--168
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Check the power fuse of the suspected ventilation block.
If the fuse is operational, replace the ventilation block. Go to step 5.
If not, replace the fuse. Go to step 6.
4 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 8.
5 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then to go step 8.
6 Replace the fuse (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then to go step 8.
7 Check the cables connected to the PSUE power supply and the ventilation blocks.
If the cables are operational, call the manufacturer.
If not, connect them correctly, or replace them. Then go to step 8.
Additional checks
Step Action
8 Check that an end--of--fault message is issued when the alarm is cleared.
9 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--169
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.54 Fault number: 422
iii
Fault number:422 : Power supply fault to the fans of the equipment cabinetType : equipmentAlarm
FAULT ANALYSIS
The notification identifies the object that has detected the fault and the suspected element:the power supply of the ventilation blocks in the equipment cabinet.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances of the problem:
If the BSC is in duplex mode, check how many notifications with fault number420 have been received at the OMC--R.
• If there are two notifications (one for each chain, emitted by each ECI board),the problem lies with the power supply. Go to step 3.
• If there is only one notification, the problem lies with either the ECI board orthe cables. Go to step 2.
If the BSC is in simplex mode, the problem lies with either the ECI board or thepower supply or the cables. Go to step 2.
2 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, look for a notification concerning the ECIboard. Then go to step 4.
If the “internal DMUX state” is “working”, go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--170
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Check the general power supply fuse of the terminal block (VENT.)
If the fuse is operational, go to step 5.
If not, go to step 6.
4 Perform the correctivemaintenance associatedwith the notification concerning theECI board. Then go to step 10.
5 Check the power fuses of the fans.
If the power fuses are operational, replace the ventilation block. Go to step 8.
If not, replace the power fuses of the fans. Go to step 7.
6 Replace the fuse of the terminal block (VENT.):
a. Locate the fuse on the following figure (see NTP < 41 >). Replace it.
b. Then go to step 10.
7 Replace the power fuses of the fans (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
8 Replace the ventilation block (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 10.
9 Check the cables connected to the PSUE power supply and the ventilation blocks.
If the cables are operational, call the manufacturer.
If not, fix them. Then go to step 10.
Additional checks
Step Action
10 Perform a “Display chain information” command to check that the equipment hasreturned to correct operation.
11 Clear the alarm.
12 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--171
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.55 Fault number: 494
iii
Fault number:494 : Fault on ECI alarm loopType : equipmentAlarm
FAULT ANALYSIS
The location of the faulty board (ECI) is given in the notification.
REACTION OF THE SYSTEM
BSC defense
All functions of the alarm loops on the ECI board are inhibited.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command to check the ECI board state.
If the “internal DMUX state” is “faulty”, go to step 2.
If the “internal DMUX state” is “working”, clear the alarm. Go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--172
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the ECI board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
c. Then go to step 3.
Additional checks
Step Action
3 Clear the alarm if it is still active.
4 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--173
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.56 Fault number: 497iii
Fault number:497 : New PCM selected as clock referenceType : communicationsAlarm
FAULT ANALYSIS
By this notification, each chain indicates the new reference clock selected by the ECI board.
The previous clock and the new reference clock are specified in the “PREVIOUSPCM” and“NEW PCM” fields of the notification.
The fields can take the following values:
field value meaning explanation onthe “NEW PCM” field
4 internal clock No synchronizing PCM is available, so thereference clock is derived from a local oscillator.
The problem may implicate the link between theTCUs and the BSC, or the DDTI boards, or theinternal PCM links, or the TCUs.
3 clock from PCM 6Th BSC f d f l k i d
2 clock from PCM 4The BSC found a new reference clock issuedby a PCM.
1 clock from PCM 2by a PCM.The previous synchronizing PCM was faulty.
0 clock from PCM 0
The reference clock is taken from one of the four even PCMs on the first four DDTI boards(PCM 0, 2, 4, and 6) or the internal clock. The PCM 0, 2, 4 and 6 linked to the BSC arereserved to the Ater interface. They cannot be used for the Abis interface.
The priority is given to the external clock coming from the TCU, then to the internal clockcoming from the TCU, then to the PCM links in service, and lastly to the internal clock.
This notification does not always require maintenance action. It only indicates the newreference clock.
REACTION OF THE SYSTEM
BSC defense
If the TCU now uses its local clock as a reference clock, the BSC cannot use this clockanymore. So the BSChas to select another TCUwhose reference clock is issuedby aPCMof the A interface. Then the BSC sends a fault number 497 to indicate its new referenceclock.
Impact on the service
None.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--174
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the previous PCM link (not the new one), by performing a“Display all” command on the pcmCircuit object (pcmAter).
If the administrativeState of the pcmCircuit object is “locked”, do not take thealarm into account. Go to step 7.
If the operationalState of the pcmCircuit object is “enabled”, the fault is notconfirmed. Go to step 7. Nevertheless, if the interruption lasted less than fiveseconds, the operationalState remained “enabled” even though there has beena problem. This problem is associated with a PCM fault. Refer to NTP < 105 >.
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 problem on the internal PCM link.Look for a notification with fault number 523 “Fault on internal PCM (BSC,TCU)”.
If the operationalState of the pcmCircuit object is “disabled”, and theavailabilityStatus is “failed”, go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Look for alarms or notifications concerning the following equipment:
pcmCircuit links (Ater)
DDTI boards
internal PCMs
TCUs
• If there are alarms, treat them. Go to step 3.
• If there are not any alarms, call the manufacturer.
3 Replace the equipment item(s) according to the other notifications:
a. Set the ‘‘disabled--failed” pcmCircuit object (external PCM or DDTI problem) or‘‘disabled--dependency” pcmCircuit object (internal PCM problem) to “locked”.
b. Replace the item(s) of equipment. For more information on the replacement ofthe DDTI boards (Field Replaceable Unit), refer to the replacement procedurein NTP < 41 >.
c. Set the pcmCircuit to “unlocked”.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--175
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Additional checks
Step Action
4 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 7.
If the alarm persists, go to step 5.
5 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 6.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
6 Clear the alarm.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--176
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.57 Fault number: 520 (BSC 12000)iii
Fault number:: Fault on switching matrix access
Type : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.58.
FAULT ANALYSIS
This notification indicates that there is a transmission problem between the CPU66SEboard (CPU--OMU) and the SWC board. The fault was detected by the CPU66SE board,which supervises the SWC board through the SUP board (synchronous link).
The faulty element is the SWC board, or the SUP board, or the link between the boards.The chain concerned (either the active or the passive one) is mentioned in the notification.
REACTION OF THE SYSTEM
BSC defense
If the problem seldom happens, there is not any BSC defense.
If the problem often happens, the chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Then the chain concerned sends a notification with fault number 522 “Switch supervisionfailure” as soon as the duplex link is open.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check whether the notification with fault number 520 is sent cyclically or not.
If not, the chain had a temporary problem. Go to step 5.
If the notification is sent cyclically, check that a notification with fault number 522is emitted as well.
• If not, call the manufacturer.
• If yes, go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--177
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the SWC board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
If the fault persists, go to step 2.
If the fault disappeared, go to step 3.
3 Replace the SUP board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
Additional checks
Step Action
4 When the problem has been resolved, clear the alarm if necessary.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--178
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.58 Fault number: 520 (BSC 12000 “HC”)
ii
Fault number:520 : Fault on switching matrix accessType : equipmentAlarm
FAULT ANALYSIS
This notification indicates that there is a transmission problem between the CPU133IEboard (CPU--OMU) and the SWC board. The fault was detected by the CPU133IE board,which supervises the SWC board through the SUP2 board (synchronous link).
The faulty element is the SWC board, or the SUP2 board, or the link between the boards.The chain concerned (either the active or the passive one) is mentioned in the notification.
REACTION OF THE SYSTEM
BSC defense
If the problem seldom happens, there is not any BSC defense.
If the problem often happens, the chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Then the chain concerned sends a notification with fault number 522 “Switch supervisionfailure” as soon as the duplex link is open.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Check whether the notification with fault number 520 is sent cyclically or not.
If not, the chain had a temporary problem. Go to step 5.
If the notification is sent cyclically, check that a notification with fault number 522is emitted as well.
• If not, call the manufacturer.
• If yes, go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--179
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the SWC board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
If the fault persists, go to step 2.
If the fault disappeared, go to step 3.
3 Replace the SUP2 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
Additional checks
Step Action
4 When the problem has been resolved, clear the alarm if necessary.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--180
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.59 Fault number: 521
iii
Fault number:521 : Fault on switching matrixType : equipmentAlarm
FAULT ANALYSIS
This notification indicates that one of the components of the switching matrix is faulty andthat consequently the test on the connection memory is failed. This test is performed every50 connections.
The faulty element is the MSW 0 or 1 board, or the SWC board.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MSW board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
c. Check that the fault disappeared.
If the problem is over, go to step 4.
If not, go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--181
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the SWC board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
c. Then go to step 3.
Additional checks
Step Action
3 Check that the fault has disappeared (the alarmmessages are transferred into thealarm history file of the OMC--R).
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--182
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.60 Fault number: 522 (BSC 12000)
Fault number:522 : Switch supervision failureType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.61.
FAULT ANALYSIS
The faulty element is the SWC board. The location is given by the notification.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display all” or a “Display chain information” command on the bsc objectto check the state of the SWC board.
If the SWC board state is “faulty”, replace it. Go to step 3.
If the SWC board state is “working”, go to step 2.
2 Perform a “Display all” or a “Display chain information” command on the bsc objectto check the state of the SUP board.
If the SUP board state is “faulty”, go to step 4.
If the SUP board state is “working”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--183
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Replace the SWC board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Theoperations for return to service are described in the replacement procedure.
If the fault persists, go to step 4.
If the fault disappeared, go to step 6.
4 Replace the SUP board (Field Replaceable Unit):
Refer to the replacement procedure (see NTP < 41 >).
If the fault persists, go to step 5.
If the fault disappeared, go to step 6.
5 Check the cable between the SUP board and the SWC board.
If the cable is badly connected or damaged, connect it correctly or replace it.Then go to step 6.
If the cable is operational, call the manufacturer.
Additional checks
Step Action
6 Check that the fault has disappeared (the alarmmessages are transferred into thealarm history file of the OMC--R).
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--184
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.61 Fault number: 522 (BSC 12000 “HC”)
iii
Fault number:522 : Switch supervision failureType : equipmentAlarm
FAULT ANALYSIS
The faulty element is the SWC board. The location is given by the notification.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display all” or a “Display chain information” command on the bsc objectto check the state of the SWC board.
If the SWC board state is “faulty”, replace it. Go to step 3.
If the SWC board state is “working”, go to step 2.
2 Perform a “Display all” or a “Display chain information” command on the bsc objectto check the state of the SUP2 board.
If the SUP2 board state is “faulty”, go to step 4.
If the SUP2 board state is “working”, clear the alarm. Go to step 6.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--185
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
3 Replace the SWC board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Theoperations for return to service are described in the replacement procedure.
If the fault persists, go to step 4.
If the fault disappeared, go to step 6.
4 Replace the SUP2 board (Field Replaceable Unit):
Refer to the replacement procedure (see NTP < 41 >).
If the fault persists, go to step 5.
If the fault disappeared, go to step 6.
5 Check the cable between the SUP board and the SWC board.
If the cable is badly connected or damaged, connect it correctly or replace it.Then go to step 6.
If the cable is operational, call the manufacturer.
Additional checks
Step Action
6 Check that the fault has disappeared (the alarmmessages are transferred into thealarm history file of the OMC--R).
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--186
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.62 Fault number: 523
iii
Fault number:523 : Fault on internal PCM (BSC, TCU)Type : communicationsAlarm
FAULT ANALYSIS
Thebeginningof fault indicates anegative cyclic test on the TS0 of one of the internal PCM.
The internal PCM is no longer operational.
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--187
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.63 Fault number: 524
iii
Fault number:524 : Slave switch board not presentType : equipmentAlarm
FAULT ANALYSIS
The location of the board is given in the notification.
REACTION OF THE SYSTEM
BSC defense
The chain concerned commits suicide.
If it is the active chain, a switchover is performed, according to the state of the otherchain.
If it is the passive chain, it starts again.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display chain information” command on the bsc object to check howmany PCM links are faulty.
If at least one PCM link is faulty, the SWEboardmust be replaced.Go to step 3.
If more than 16 PCM links are faulty, the MSW board must be replaced. Go tostep 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--188
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the SWE board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are described in the equipment replacementprocedure.
c. Then go to step 4.
3 Replace the MSW board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are described in the equipment replacementprocedure.
c. Then go to step 4.
Additional checks
Step Action
4 Check that the fault has disappeared (the alarmmessages are transferred into thealarm history file of the OMC--R).
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--189
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.64 Fault number: 601 (BSC 12000)
iii
Fault number:601 : File management errorType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.65.
FAULT ANALYSIS
If the problem persists, a site visit is required.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty MMU board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. After replacing the MMU board, follow appropriate procedures in NTP < 41 > toexecute the maintenance procedure for the disk of a BSC:
i. Install the BSC software on the new disk.
ii. The automatic customization takes place.
iii. If necessary, apply BSC patches.
If the file management error persists, go to step 2.
If the problem disappeared, go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--190
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
c. Then go to step 3.
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--191
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.65 Fault number: 601 (BSC 12000 “HC”)
oo
Fault number:601 : File management errorType : equipmentAlarm
FAULT ANALYSIS
If the problem persists, a site visit is required.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty MMU_IDE board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. After replacing the MMU board, follow appropriate procedures in NTP < 41 > toexecute the maintenance procedure for the disk of a BSC:
i. Install the BSC software on the new disk.
ii. The automatic customization takes place.
iii. If necessary, apply BSC patches.
If the file management error persists, go to step 2.
If the problem disappeared, go to step 3.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--192
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the CPUM board (CPU133IE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP2 board: “12” must be displayed if the chainis operational.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--193
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.66 Fault number: 607 (BSC 12000)
iii
Fault number:607 : Multibus II errorType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.67.
FAULT ANALYSIS
The fault is detected by the CPUM (CPU66SE) board, which indicates a minor problemduring initialization of the Multibus II. This fault may be due to malfunction of one of theboards in the control cabinet.
If the problem persists, a site visit is required (call the manufacturer).
REACTION OF THE SYSTEM
BSC defense
The system attempts to reinitialize the Multibus II cyclically.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty board (Field Replaceable Unit):
a. Refer to the appropriate replacement procedure in NTP < 41 >:
CPUM (CPU66SE) board
CCS7 boards
CPUE boards
SICX board
SUP board
SICD8V boards
b. Concerning the boards linked to the Multibus II, the operations for return toservice are performed by the system.
c. Then go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--194
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
2 Clear the fault alarm manually, if necessary.
3 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
4 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--195
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.67 Fault number: 607 (BSC 12000 “HC”)
ii
Fault number:607 : Multibus II errorType : equipmentAlarm
FAULT ANALYSIS
The fault is detected by the CPUM (CPU133IE) board, which indicates a minor problemduring initialization of the Multibus II. This fault may be due to malfunction of one of theboards in the control cabinet.
If the problem persists, a site visit is required (call the manufacturer).
REACTION OF THE SYSTEM
BSC defense
The system attempts to reinitialize the Multibus II cyclically.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty board (Field Replaceable Unit):
a. Refer to the appropriate replacement procedure in NTP < 41 >:
CPUM (CPU133IE) board
CCS7 boards
CPUE (CPU133) boards
SICX board
SUP2 board
SICD8V boards
b. Concerning the boards linked to the Multibus II, the operations for return toservice are performed by the system.
c. Then go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--196
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
2 Clear the fault alarm manually, if necessary.
3 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP2 board: “12” must be displayed if the chainis operational.
4 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--197
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.68 Fault number: 617
iii
Fault number:617 : SCSI bus controller errorType : equipmentAlarm
FAULT ANALYSIS
The fault has been detected by the CPUM board, which indicated a minor problem duringinitialization of the SCSI bus controller of the MMU board (SCSI disk).
This fault may be due to malfunction of:
the MMU board (SCSI disk) or
the CPUM (CPU66SE) board or
the back plane
If the problem persists, a site visit is required.
REACTION OF THE SYSTEM
BSC defense
The system cyclically attempts to reinitialize the bus controller between the MMU board(SCSI disk) and the CPUM board (CPU66SE).
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Check the state of the CPUM board (CPU66SE):
If the CPUM board is operational, go to step 3.
If the CPUM board is not operational, go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--198
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
c. Then go to step 8.
3 Check the state of the MMU board (SCSI disk):
If the MMU board is operational, go to step 5.
If the MMU board is not operational, go to step 4.
4 Replace the MMU board (SCSI disk) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >)
b. After having replaced the MMU board, perform the maintenance procedure forthe disk of a BSC (see NTP < 41 >) for return to service.
5 Check the state of the back panel:
If the backpanel is operational, go to step 7.
If the backpanel is not operational, go to step 6.
6 Repair the backpanel.
7 Call the manufacturer.
Additional checks
Step Action
8 Clear the fault alarm manually if necessary.
9 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
10 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--199
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.69 Fault number: 632 (BSC 12000)
iii
Fault number:632 : File management errorType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.70.
FAULT ANALYSIS
This notification indicates that there is a problem with file management on the BSC disk.
The faulty item of equipment is either the disk itself, on the MMUboard, or the CPUMboard(CPU66SE).
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. After having replaced the MMU board, execute the maintenance procedure forthe disk of a BSC (see NTP < 41 >).
If the file management system problem is over, go to step 3.
If the problem persists, go to step 2.
2 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--200
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--201
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.70 Fault number: 632 (BSC 12000 “HC”)
oo
Fault number:632 : File management errorType : equipmentAlarm
FAULT ANALYSIS
This notification indicates that there is a problem with file management on the BSC disk.
The faulty item of equipment is either the disk itself, on the MMU_IDE board, or the CPUMboard (CPU133IE).
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU_IDE board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. After having replaced theMMU_IDEboard, execute themaintenanceprocedurefor the disk of a BSC (see NTP < 41 >).
If the file management system problem is over, go to step 3.
If the problem persists, go to step 2.
2 Replace the CPUM board (CPU133IE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--202
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP2 board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--203
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.71 Fault number: 633
iii
Fault number:633 : Disk driver errorType : equipmentAlarm
FAULT ANALYSIS
The responsible equipment cannot be identified from the notification.
The fault is detected by the CPUM board, which indicates a problem during initialization ofthe SCSI bus controller of the MMU board (SCSI disk).
This fault may be due to malfunction of the following:
MMU board
CPUM board (CPU66SE)
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. After having replaced theMMUboard, follow themaintenance procedure for thedisk of a BSC and, if necessary, for return to service (see NTP < 41 >).
If the disk driver problem is over, go to step 3.
If the problem persists, go to step 2.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--204
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--205
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.72 Fault number: 634 (BSC 12000)
iii
Fault number:634 : Mirror diskType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.73.
FAULT ANALYSIS
This hardware anomaly can be issued by the active or passive chain. It is detected by theSCSI controller.
The anomaly may indicate a hardware problem on the chain sending the anomaly:
5 V power supply (ondulation or value outside tolerance thresholds)
SCSI disk on the MMU board
CPUM board (CPU66SE)
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--206
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.73 Fault number: 634 (BSC 12000 “HC”)
oo
Fault number:634 : Mirror diskType : equipmentAlarm
FAULT ANALYSIS
This hardware anomaly can be issued by the active or passive chain. It is detected by theIDE controller.
The anomaly may indicate a hardware problem on the chain sending the anomaly:
5 V power supply (ondulation or value outside tolerance thresholds)
IDE disk on the MMU_IDE board
CPUM board (CPU133IE)
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--207
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.74 Fault number: 638 (BSC 12000)
iii
Fault number:638 : Multibus II errorType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.75.
FAULT ANALYSIS
This notification indicates that there is a problem with the Multibus II, or with a boardconnected to this bus.
REACTION OF THE SYSTEM
BSC defense
This fault does not lead directly to chain suicide. One of the boards of the Multibus II willbecome faulty (because of a problem on theMultibus II) and cause the suicide of the chain.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check for the presence of a chain suicide message.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--208
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the faulty board (Field Replaceable Unit):
a. Refer to the appropriate replacement procedure in NTP < 41 >:
CPUM board (CPU66SE)
CCS7 boards
CPUE boards
SICX board
SUP board
SICD8V boards
b. For all other boards linked to the Multibus II, the operations for return to serviceare performed by the system. Then go to step 3.
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--209
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.75 Fault number: 638 (BSC 12000 “HC”)
iii
Fault number:638 : Multibus II errorType : equipmentAlarm
FAULT ANALYSIS
This notification indicates that there is a problem with the Multibus II, or with a boardconnected to this bus.
REACTION OF THE SYSTEM
BSC defense
This fault does not lead directly to chain suicide. One of the boards of the Multibus II willbecome faulty (because of a problem on theMultibus II) and cause the suicide of the chain.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check for the presence of a chain suicide message.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--210
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the faulty board (Field Replaceable Unit):
a. Refer to the appropriate replacement procedure in NTP < 41 >:
CPUM board (CPU133IE)
CCS7 boards
CPUE boards (CPU133)
SICX board
SUP2 board
SICD8V boards
b. For all other boards linked to the Multibus II, the operations for return to serviceare performed by the system. Then go to step 3.
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP2 board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--211
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.76 Fault number: 649
iii
Fault number:649 : SCSI protocol errorType : equipmentAlarm
FAULT ANALYSIS
The faulty equipment is the MMU board or the CPUM (CPU66SE) board.
The type and location of the board are indicated by the notification.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the MMU board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >.
b. After having replaced the MMU board, execute the maintenance procedure forthe disk of a BSC, then, if necessary, for return to service (see NTP < 41 >).
If the SCSI protocol problem is over, go to step 3.
If the problem persists, go to step 2.
2 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--212
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
3 Clear the fault alarm manually if necessary.
4 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
5 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--213
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.77 Fault number: 656, 657
iii
Fault number:656 and 657 : Ethernet controller chip errorType : equipmentAlarm
FAULT ANALYSIS
The faulty equipment is the CPUM board.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the CPUM board (CPU66SE) (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. The operations for return to service are performed by the system.
Additional checks
Step Action
2 Clear the fault alarm manually if necessary.
3 Make sure that the repaired chain does not commit suicide again and check thestate of the display panels on the SUP board: “12” must be displayed if the chainis operational.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--214
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.78 Fault number: 1074
iii
Fault number:1074 : Indication of hardware in compatibility with activated featuresType : equipmentAlarm
FAULT ANALYSIS
After a “Display all” command, the BSC sends a global notification per CPU--BIFP boardthat lists all the TDMA which do not support a feature required.
FAULT TREATMENT
The notification shows the incompatibilities between the features configured by theoperator and the hardware possibilities.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--215
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.79 Fault number: 1150
iii
Fault number:1150 : Loss of DDTI configurationType : equipmentAlarm
FAULT ANALYSIS
This alarm indicates that a DDTI board lost its configuration.
The type and position of the board are specified in the notification.
REACTION OF THE SYSTEM
BSC defense
The system isolates the DDTI board that has lost its configuration.
Impact on the service
CAUTIONService interruption
The service is reduced (in a multiMIC configuration) or reduced (ina monoMIC configuration).
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--216
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.80 Fault number: 1151
iii
Fault number:1151 : PCM transmission faultType : communicationsAlarm
FAULT ANALYSIS
This notification indicates a transmission problem with one of the PCM links.
The PCM number and the associated DDTI board are specified in the notification.
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--217
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.81 Fault number: 1152
iii
Fault number:1152 : PCM CRC attribute and DDTI CRC strap are not consistentType : processingErrorAlarm
FAULT ANALYSIS
Note: For information on the 1152 alarm for the TDTI board, refer toParagraph 3.9.
This notification is sent by the BSC when an inconsistency is detected between thehardware configuration of the DDTI board and the setting of the BSC.
The “cRC” attribute of the pcmCircuit object (bsc -- Abis or Ater) does not match the CS17and CS18 jumpers configuration on the DDTI board.
This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.
REACTION OF THE SYSTEM
BSC defense
The pcmCircuit object is “failed”. The children objects (btsSiteManager, bts,transceiverEquipment, transceiver) are unconfigured.
Impact on the service
CAUTIONService interruption
The service is reduced or lost, depending on the configuration.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--218
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the PCM link, by performing a “Display all” command on thepcmCircuit object.
If the pcmCircuit object is “disabled”, wait until it becomes “enabled”.
If the pcmCircuit object is “disabled--dependency”, look for a notification withfault number 523 “Fault on internal PCM (BSC, TCU)”.
If the pcmCircuit object is “failed”, go to step 2.
If the pcmCircuit object is “enabled”, clear the alarm. Go to step 6.
2 At theOMC--R, check the “cRC” attribute valueby performinga “Display” commandon the pcmCircuit object.
If the “cRC” parameter value is “used”, go to step 3.
If the “cRC” parameter value is “not used”:
i. set the pcmCircuit object to “locked”
ii. set the “cRC” parameter to “used”
iii. set the pcmCircuit object to “unlocked”.
iv. Then go to step 4.
On--site maintenance
Step Action
3 On site, change the CS17 and CS18 jumpers on the DDTI board:
a. Set the pcmCircuit object to “locked”.
b. Change the CS17 and CS18 jumpers on the DDTI board. For more informationon the jumpers position, refer to the appropriate procedure in NTP < 41 > forDDTI E1 -- GSM 900/1800 or DDTI T1 -- GSM 1900.
c. Set the pcmCircuit object to “unlocked”. Then go to step 4.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--219
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Additional checks
Step Action
4 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 7.
If the alarm persists, go to step 5.
5 Check the state of the equipment, by performing a “Display all” command on thebsc object.
6 Clear the alarm.
7 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--220
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.82 Fault number: 1153iii
Fault number:1153 : Negative test on passive chain LAPD channel (layer 2)Type : communicationsAlarm
FAULT ANALYSIS
The passive chain tests the links between:
the SICD, RCB, SWC,MSW, SWEand DDTI boards (betweenBTSs andBSC), if thereis not any Abis concentration. The lapd test loops back in the DDTI boards, at the entryof the internal PCM link.
the SICD, RCB, SWC,MSW, SWEboards andBSCB boards (betweenBTSs andBSC)or TSCB boards (between TCUs and BSC), if there is Abis or Ater concentration.Thelapd test loops back in the BSCB or TSCB boards. Thus the passive link between theDDTI and the BSCB (or TSCB) boards is not tested.
This test is performed by the passive chain each time the passive chain restarts, and thenumber of failed tests is recorded.
The active chain compares the test results of the two chains when it has to choosebetweenthe two chains after a chain suicide.
If all the equipment is operational, there is no global fault on a board, but a wiring problemor an internal board problem (and not detected by the internal mechanism of the board).
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances in which the notification appears:
When the notification appears for a chain that becomes active, do not take it intoaccount. Go to step 3.
On a beginning--of--fault, perform a “Display all” command on the bsc object.Check the value of the “passive chain sic channels state” attribute:
• If the state is “working”, clear the alarm. Go to step 4.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--221
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
• If the state is “faulty”, there may be notifications concerning the SICD, RCB,SWC, MSW, SWE, DDTI, BSCB or TSCB board.
– If there is a notification, treat it.
– If not, go to step 2.
On--site maintenance
Step Action
2 Follow appropriate procedures in NTP < 41 > to replace the following boards, oneafter the other (Field Replaceable Unit), to find out which one is faulty:
SICD board
RCB board
SWC boards
MSW 0 and 1 boards
SWE 0 and1 boards
DDTI boards
BSCB boards
TSCB boards
If the faulty board has been identified and replaced, go to step 4.
If not, go to step 3.
3 Check the inter--cabinet wiring, and the cables connecting the boards mentionedabove.
If the wiring is correct, call the manufacturer.
If the wiring is incorrect, reconnect it correctly, or repair it.
Additional checks
Step Action
4 Perform a “Display all” command to check that the alarms disappeared.
5 If necessary, manually clear the alarm.
6 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--222
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.83 Fault number: 1154
iii
Fault number:1154 : Negative test on passive chain CCS7 signalling link (layer 2)Type : communicationsAlarm
FAULT ANALYSIS
The passive chain tests the links between the CCS7, SWC, and MSW0 boards. The ccs7test loops back in the CCS7 boards, at the entry of the internal PCM link.
Source:
0 High error rate in service
1 Basic error correction mechanism
2 Excessive acknowledgement delay
3 SIOS, SIO or SIN frames received
4 Stopped by layer 3
5 Other layer 2 error
6 Remote processor outage
7 MSU test KO
8 No answer from CCS7 card
9 Timeout awaiting MSU ack
This test is performed by the passive chain each time the passive chain restarts, and thenumber of failed tests is recorded.
The active chain compares the test results of the two chains when it has to choosebetweenthe two chains after a chain suicide.
If all the equipment is operational, there is no global fault on a board, but a wiring problemor an internal board problem (and not detected by the internal mechanism of the board).
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--223
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Analyze the circumstances in which the notification appeared:
When the notification appears for a chain that becomes active, do not take it intoaccount. Go to step 3.
On a beginning--of--fault, perform a “Display all” command on the bsc object.Check the value of the “passive chain sic channels state”:
• If the state is “working”, clear the alarm. Go to step 4.
• If the state of a board is “faulty”, there may be notifications concerning aSWC, MSW or CCS7 board.
– If there is a notification, treat it.
– If not, go to step 2.
On--site maintenance
Step Action
2 Follow appropriate procedures in NTP < 41 > to replace the following boards, oneafter the other (Field Replaceable Unit), to find out which one is faulty:
SWC boards
MSW 0 board
CCS7 boards
If the faulty board has been identified and replaced, go to step 4.
If not, go to step 3.
3 Check the inter--cabinet wiring, and the cables connecting the boards mentionedabove.
If the wiring is correct, go to step 4.
If the wiring is incorrect, reconnect it correctly, or repair it.
Additional checks
Step Action
4 Perform a “Display all” command to check that the alarms disappeared.
5 If necessary, manually clear the alarm.
6 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--224
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.84 Fault number: 1155 (BSC 12000)
iii
Fault number:1155 : Fault on SLS cardType : equipmentAlarm
If the BSC 12000 “HC” is concerned, refer to Paragraph 2.85.
FAULT ANALYSIS
The position of the SLS board is given in the notification.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty SLS board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
Additional checks
Step Action
2 If necessary, manually clear the alarm.
3 The procedure is complete.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--225
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.85 Fault number: 1155 (BSC12000 “HC”)
oo
Fault number:1155 : Fault on SLS cardType : equipmentAlarm
FAULT ANALYSIS
The position of the SLS2 board is given in the notification.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Replace the faulty SLS2 board (Field Replaceable Unit):
a. Refer to the replacement procedure (see NTP < 41 >).
b. Then go to step 3.
Additional checks
Step Action
2 If necessary, manually clear the alarm.
3 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--226
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.86 Fault number: 1164iii
Fault number:1164 : OMC access failureType : communicationsAlarm
FAULT ANALYSIS
This notification indicates that the REM link selftest result is bad.
The degradation level is mentioned in the notification:
“partial”: when one of the two links allowing the OMC--R access (X25 network, orA interface) is degraded
“total”: when the two links are degraded
The REM link selftest is performed:
on the passive chain:
• On the A interface, the selftest starts two minutes after the end of the chain start--up(“12--12” phase). It is performed cyclically. The boards involved are the SICX, SWCand MSW 0 boards. If an anomaly is detected, this notification with fault number1164 is sent, and “partial” is displayed in the “degradation level” field.
• On the X25 network, the selftest is performed every hour. The boards involved aretheSICXandSLS2boards.The selftest loops back on theSLS2 board. If an anomalyis detected, this notification with fault number 1164 is sent, and “partial” is displayedin the “degradation level” field.
on the active chain:
• The chain triggered the selftest. If the REM link is lost, this notification with faultnumber 1164 is sent, and “total” is displayed in the “degradation level” field.
REACTION OF THE SYSTEM
BSC defenseWhen the two links are degraded on the active chain (“total” is displayed in the “degradationlevel” field), a switchover is performed.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Check which interface is involved:
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--227
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
If the A interface is concerned, go to step 2.
If the X25 network is concerned, go to step 3.
2 Look for a notification with fault number 520 “Fault on switching matrix access”concerning the SWC board, and a notification with fault number 523 “Fault oninternal PCM” involving the MSW 0 board.
If there are notifications, treat them. Then go to step 4.
If not, follow the appropriate procedures in NTP < 41 > to replace the followingboards, one after the other, to find out which one is faulty:
• the SICX board (Field Replaceable Unit).
• the SWC board (Field Replaceable Unit).
• the MSW board (Field Replaceable Unit).
• Then go to step 4.
3 Replace the followingboards oneafter theother, to find out whichone is faulty (FieldReplaceable Unit):
a. Refer to the appropriate replacement procedures in NTP < 41 >:
the SICX board.
the SLS2 board.
b. Then go to step 4.
Additional checks
Step Action
4 If necessary, manually clear the alarm.
5 End. The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--228
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.87 Fault number: 1193
iii
Fault number:1193 : Clock alarmType : communicationsAlarm
FAULT ANALYSIS
The state change of one of the reference clocks is detected by the ECI board, and itimplicates the DDTI board or, the external PCM, or the ECI board itself. The object and theinstance in the alarm identify the suspected clock. The object concerned by this alarm isthe pcmCircuit object for the PCMs of the Ater interface.
REACTION OF THE SYSTEM
BSC defense
This anomaly is sent by the BSC at each state change of a synchronizing clock supportedby a PCM of the Ater interface in service.
In case of synchronization problem, the ECI board looks for a new reference clock andsends a notification with fault number 497 “New PCM selected as clock reference”.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check whether this notification is often sent to the OMC--R or not.
If not, go to step 4.
If yes, the problem may come from:
• a transcoder object which is “locked”.
– Find out why it is “locked”.
– If it is “unlocked”, go to step 2.
• an unstable PCM link. Go to step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--229
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 To locate the fault, this anomaly must be associated with the following:
an operator warning with fault number 497 on the bsc object to identify the newreference clock with the value of the “New PCM” field
a fault with fault number 1151 for the external PCM on the Ater interface.Concerning the PCM faults, refer to NTP < 105 >.
a fault with fault number 7 for the DDTI boards
Treat the alarm(s). Then go to step 3.
Additional checks
Step Action
3 Check the transmission network.
4 If necessary, manually clear the alarm.
5 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--230
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.88 Fault number: 1201
iii
Fault number:1201 : Degraded active chainType : equipmentAlarm
FAULT ANALYSIS
Thismessagewarns the operator that aBSChas just switchedover onto a degraded chain.
The passive chain must be repaired to (at least) ensure nominal service.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
Both BSC chains are degraded.
FAULT TREATMENT
Preliminary checks
Step Action
1 Wait for the end of the passive chain restart.
2 Look for other alarms or notifications indicating faulty elements (fault number 16,15, 11, 7, 6, 5) on the passive chain. They must have been previously issued.
The alarm identifies the number of declared boards and the number of availableboards (ECI, SICX, SICD, CCS7, switching boards).
The alarm also indicates the disk state, in the “disk status” field:
0 partial hard disk degradation
1 total hard disk degradation
3 Repair the passive chain as indicated in the information found in step 2.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--231
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 When the passive chain is fixed, a chain switchover takes place because the BSCalways chooses the better chain as the active one.
5 Then look for other alarms or notifications indicating faulty elements (fault number16, 15, 11, 7, 6, 5) on the new passive chain (that was previously the degradedactive chain). They must have been previously issued.
6 Repair the passive chain as indicated in the information found in step 5. Then goto step 7.
Additional checks
Step Action
7 Wait until the BSC comes back in duplex state.
8 Execute an active chain suicide by a provoked switchover on the OMC--R.
9 Make sure that the repaired chain becomes active again.
10 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--232
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.89 Fault number: 1211
ii
Fault number:1211 : Unknown TEI in a LAPD message received by the XSCB cardType : processingErrorAlarm
FAULT ANALYSIS
A message with an unknown TEI was received on a TSCB or BSCB board.
This notification indicates a software problem.
The typeof faulty board (either TSCB orBSCB), and its number are given in thenotification.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--233
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.90 Fault number: 1212
iii
Fault number:1212 : xSCB card internal fifo congestionType : qualityOfServiceAlarm
FAULT ANALYSIS
This notification indicates a TSCB or BSCB board load problem.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
On--site maintenance
Step Action
1 Check how many alarms with Fault number 1212 have been received at theOMC--R.
If this notification is exceptional, it corresponds to a transient overload. Nomaintenance is required. Go to step 3.
If this notification is often received at the OMC--R, it corresponds to aninsufficient configuration. Go to step 2.
2 Change the configuration:
If possible, add a BSCB board. Then go to step 3.
If not, perform a reparenting so that sites and load are better distributed. Call themanufacturer.
3 End. The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--234
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.91 Fault number: 1312
iii
Fault number:1312 : MSC inaccessibleType : communicationsAlarm
FAULT ANALYSIS
This alarm is sent by the BSC after eight consecutive no response to the Reset command.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
The service is lost because the A interface is not available.
FAULT TREATMENT
Preliminary checks
Step Action
1 Perform a “Display all” interrogation on a signallingLink object.
If the object is “unlocked--enabled” and the resource is available, donot take thisalarm into account. Go to step 4.
Otherwise, go to step 2.
2 Look for alarms concerning the BSC, TCU, TCU/MSC link or BSC/TCU link.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--235
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
If alarms concern the BSC, TCU, or BSC/MSC link:
i. ignore the alarm with fault number 1312
ii. process the alarms on the faulty element
iii. check that the alarm with fault number 1312 is not reissued, orperform a “Display all” interrogation on the object.
When this notification with fault number 1312 appears alone, look for a problemat the MSC level.
Additional checks
Step Action
3 Clear the alarm if necessary and perform a “Display all” interrogation of thesignallingLink object.
4 The procedure is complete.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--236
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.92 Fault number: 1315
iii
Fault number:1315 : Path Information for calls released by TCU or BTSType : communicationsAlarm
FAULT ANALYSIS
In cases where there is a loss of communication between the TCU and the BTS, the userwould hear only silence and would eventually terminate the call. The system now detectsthese types of failures and releases the call automatically.
This warning notification is sent to indicate the path associated with the dropped call tofacilitate troubleshooting the problem.
The warning is subject to a threshold: 100 occurrences affecting the same path will resultin 1 warning at the OMC--R.
The quantity of calls dropped can be tracked by Counters:
C1164/28 -- Calls dropped by the TCU
C1164/32 -- Calls dropped by the BTS
The fault could be indicative of Transmission Line failure, Transmission Equipment failure(i.e. DACS) or a failure within the BSC 3000 or TCU 3000 or BTS.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
Calls have been dropped.
FAULT TREATMENT
Preliminary checks
Step Action
1 Monitor counter C1164 to determine the frequency of occurrence and whichtransmission direction is affected:
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--237
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
C1164/28: Indicates a failure in the path from BTS to TCU.
C1164/32: Indicates a failure in the path from TCU to BTS.
Note: Either one may be caused by a failure of either ABIS or ATER PCM.
2 Check for any notifications relating to the BSC, TCU or Transmission links (PCM),treat these symptoms first then verify if counters are still incremented.
3 Call the manufacturer for help in decoding the failing path information whichappears in the Manufacturer Information part of the notification.
Optional further checks
These optional checks can only be done after contacting the manufacturer for help indecoding the path of the failed calls.
Step Action
1 Using the decoded path information provided by themanufacturer (see preliminarycheck step 3):
Look for reoccurring instances of the same object (i.e. TRM, PCM, Timeslot.)
If the most commonly failing object is a PCM or Timeslot, determine if it is anATER or ABIS PCM.
2 Confirm failing path:
Try to physically swap PCMs, or lock one PCM at a time.
Try to lock impacted Radio Channels.
i. Verify if counter C1164 is still incremented.
ii. If counters are no longer incremented, fault is confirmed, go to step 3.
iii. If counters are still incremented go to step 5
3 If either the ATER or ABIS PCM pass through intermediate equipment such as aDACS:
Check the DACS board that manages the PCM and the DACS configuration.
The DACS (and many other types of transmission equipment) will often havecounters indicating errors, errored seconds, BPV’s, slips, or Frame errors. Usethese to localize the source of the problem. Note that, depending on the type ofDACS, it may re--frame the signal, whichwould tend to ”mask” alarms andsometypes of errors (slips, notably).
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--238
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
All transmission facilities should be configured to use appropriate zero--codesuppression (i.e., B8ZS for DS1 facilities).
4 Using suitable test equipment, perform end--to--end quality test of failing PCM.Ensuring that all Timeslots are checked.
5 If the failing PCM’s are associated with the same LSA perform a SWACT of theassociated IEM.
6 If failure is associated with the same TRM, replace the TRM.
7 If problem is not identified, Call the manufacturer.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--239
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.93 Fault number: 1366
iii
Fault number:1366 : Indication of the SSN LCS stateType : qualityOfServiceAlarm
FAULT ANALYSIS
This notification is sent when a client of the SS7 protocol becomes available or becomesunavailable (at each state change of the SSN LCS).
REACTION OF THE SYSTEM
None.
FAULT TREATMENT
No maintenance action is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--240
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.94 Fault number: 1470
iii
Fault number:1470 : Impossibility of storage of a general permanent observation
messageType : qualityOfServiceAlarm
FAULT ANALYSIS
Thismessagemeans that there is a permanent observation file writing problem on the BSCdisk. This notification specifies the doubtful disk partition: GPO (General PermanentObservation).
This message is emitted in the following conditions:
1) An observation file must be written on the BSC disk, in the GPO partition. Normally, thefile is then retrieved by the OMC--R, and then deleted.
2) But theGPO partition is full. This problemmay occur if OMC--R does not retrieve the filesthat contain observation results quickly, or when the link between the BSCand theOMC--Rhas been lost for quite a long time (more than three days).
3) Then the GPO partition is automatically purged. A notification with fault number 1472“Purge realized to store a GPO message” is sent.
4) Despite the purge, the partition is still full and the observation file cannot be stored onthe disk. The observation file is lost and this notification is emitted. The notification isemitted for each lost file. This problem may occur if the files already stored on the diskcannot be deleted for one of the following reasons:
they do not have the right format (tyyddhhmmss)
they are not old enough to be deleted:
• OGS files (Observation General Statistic) must be older than 72 hours
• OFS files (Observation Fast Statistic) must be older than 24 hours
• ODIAG files (Observation Diagnostic) must be older than 24 hours
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The only effect is the loss of observation files but this does not affect systemoperations.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--241
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Maintenance using the OMC--R
Step Action
1 Check the size and the content of the GPO partition since, in spite of purging, thereis not enough place on the disk.
2 If the partition size is normal, or if some files on the disk do not have the right format(tyyddhhmmss), call the manufacturer.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--242
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.95 Fault number: 1472
iii
Fault number:1472 : Purge realized to store a general permanent observation
messageType : qualityOfServiceAlarm
FAULT ANALYSIS
Thismessage indicates an automatic permanent observation purging on the GPO partition(General Permanent Observation).
This fault may occur if OMC--R does not retrieve the files that contain observation resultsquickly, or when the link between the BSC and the OMC--R has been lost for quite a longtime (more than three days).
The file specified in the notification is the file generated by purging and not the name of thepurged file. Purging is performed before writing on the disk again.
The following files have been purged:
OGS files (Observation General Statistic) older than 72 hours
OFS files (Fast Statistic) older than 24 hours
ODIAG files (Observation Diagnostic) older than 24 hours
Some files can actually be much older than 72 hours, because purging is performed onlywhen the GPO partition is full.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The only effect is the loss of observation files but this does not affect systemoperations.
FAULT TREATMENT
Check that the observation files are retrieved by the OMC--R, and that the link between theBSC and the OMC--R is operational.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--243
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.96 Fault number: 1483
iii
Fault number:1483 : Impossibility of storage of non prioritary recordsType : qualityOfServiceAlarm
FAULT ANALYSIS
This notification indicates that it is impossible to store non prioritary records (or partialrecords) associatedwith theCALL--TRACING function on thededicatedpartition of thediskof the BSC.
This message is emitted in the following conditions:
1) A radio observation file must be written on the BSC disk, in the dedicated partition.
2) But the partition is full, or does not have enough space left.
3) This notification (Beginning--of--fault) is sent, only once, even if several files cannot bestored on the BSC disk.
4) Then thepartition is automatically purged. All the radio observation files are deleted.Onlythe management file is kept.
5) If the purgewas successful, this notification is sent again as an End--of--fault. If the purgefailed (which never happens a priori), the partition is still full and the radio observation filecannot be stored on the disk, and is lost.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The only effect is the loss of radio observation files but this does not affect systemoperations.
FAULT TREATMENT
If the purge failed, call the manufacturer.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--244
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.97 Fault number: 1484
iii
Fault number:1484 : Impossibility of storage of filesType : qualityOfServiceAlarm
FAULT ANALYSIS
This notification indicates that it is impossible to store CALL PATH TRACING files on thededicated partition of the disk of the BSC.
This message is emitted in the following conditions:
1) A radio observation file must be written on the BSC disk, in the dedicated partition.
2) But the partition is full, or does not have enough space left.
3) This notification (Beginning--of--fault) is sent, only once, even if several files cannot bestored on the BSC disk.
3) Then thepartition is automatically purged. All the radio observation files are deleted.Onlythe management file is kept.
4) If the purgewas successful, this notification is sent again as an End--of--fault. If the purgefailed (which never happens a priori), the partition is still full and the radio observation filecannot be stored on the disk, and is lost.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None. The only effect is the loss of radio observation files but this does not affect systemoperations.
FAULT TREATMENT
If the purge failed, call the manufacturer.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--245
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.98 Fault number: 1486
iii
Fault number:1486 : Call path tracing activity state changeType : qualityOfServiceAlarm
FAULT ANALYSIS
This notification indicates a CALL PATH activity state change, associated with thecallPathTrace object.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
This notification is a warning. No maintenance is required.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--246
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.99 Fault number: 1490
iii
Fault number:1490 : BSC overloadType :
FAULT ANALYSIS
This alarm indicates that calls are blocked because of a BSC overload. The overloadedboard(s) is(are) given in “equipment type” and “equipment number” fields.
This alarm can be sent during a chain start--up, and during a chain switchover.
It is first sent as a Beginning--of--fault alarm, when one BSC board has been in overloadlevel 3 for more than five seconds. The name of the board concerned is given in thenotification. Even if other boards have also been in overload level 3 for more than fiveseconds, this beginning--of--fault alarm is sent only once.
This alarm is also sent as anEnd--of--fault alarm,whenall the boards are under theoverload3 level again. The list of the boards concerned is given in thenotification. Theseboardshavebeen in overload level 3 for more than one second. The end--of--fault alarm is sent onlyonce.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService reduction
The service is reduced, because new calls cannot be established.
FAULT TREATMENT
None, if the alarm corresponds to a transient increase of the traffic.
However, if the alarm is very often sent to the OMC--R, try to find out why (BSC/networkdimensioning, etc.). At the OMC--R, look at the counters signaling failed call establishment(e.g.: 1835 counter). Call the manufacturer.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--247
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.100 Fault number: 1502
iii
Fault number:1502 : Access attempt to a non operational cellType : qualityOfServiceAlarm
FAULT ANALYSIS
Thismessagewarns the operator that an access attempt to a non operational cell has beenmade. This can be due to:
an access attempt to a non--created cell
paging attempted on a cell in which paging is not authorized
paging on a cell in which all System Information messages have been acknowledged
This notification indicates a configuration problem.
WhenCell is created, but not operational then the fault number 1502 is sent to theOMC--R.This could happen when:
1. Cell has been created, attributed and then de--attributed.After the creation of the cell, a cell in Operational state is attributed after receiving Sys InfoAcknowledgments from BTS.A Cell in Operational state is de--attributed, when the cell is out of service in BSC.
Fault number 1502 is sent to OMC--R, after one of the following call flows occurs:Call Flow 1A Channel Required message is sent to the BSC (Traffic Management).Traffic management issues fault number 1502.Call Flow 2An inter--cell handover is requested for a call setupon its destination cell (inter or intraBSC).An Access Request message is sent to the BSC (Traffic Management).Traffic management issues fault number 1502.
Fault number 1502 is issued for the following reason:If the CCCH downlink channel is not initialized and if the BSC is in the active mode, faultnumber 1502 is triggered. Thewarning is issued, if this scenario is executedmore than 100times. The limitation of 100 times exists becauseof awarning threshold present inRADCELwarning management.
2. Cell has been created but not attributed.The cell has not been attributed by SPR (Radio supervision), i.e., Sys Info Exchange hasnot happened between BSC and BTS for this cell.
FIELD DESCRIPTION
Target CGI: cell parameters, mcc, LAC, mnc, ci
Cell Admin State:0: not created205: created
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--248
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Cell Paging State:0: not significant1: not allowed because BCCH information
Not Acknowledged:2: paging request allowed
Radio Data Consistency for TMG point of view:
0: consistent1: inconsistent
TS Carrying Common Channel:TS carrying common channel
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService reduction
FAULT TREATMENT
Check the configuration against the information given in the notification.
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--249
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
2.101 Fault number: 1503
iii
Fault number:1503 : Access attempt to an unknown BCCH or BSICType : CommunicationsAlarm
FAULT ANALYSIS
This anomaly is sent when a handover is required towards a (bsic,bcch) not belonging tothe neighbouring cells of the originated cell.
This alarm indicates that amobile sentsmeasurement reports withmeasures reported froman unknown neighbor cell identified by the couple (BCCH, BSIC) which is not declared inthe adjacent handover cell list at the OMC--R.
REACTION OF THE SYSTEM
BSC defense
None
Impact on the service
None.
FAULT TREATMENT
To solve this problem, check the frequency plan and the frequency bands. For the cellsfound in the Session Log, verify the accuracy of the datafill (BSIC/BCCH) for the impactedcell (on the bts object) and its neighboring cells.
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--250
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
2.102 Table of software error descriptions
iiiType : processingErrorAlarm
The minor or major software anomaly messages inform users of faults detectedduringBSCprocessing chain application software runs. The software anomalies areonly used by the manufacturer and do not require maintenance action.
In some cases, the software anomalies may indicate a configuration problem, adatabase problem or a disk problem.
Minor software anomalies (level 5 priority messages) are filtered at MD level andthey are not displayed in notification windows at the OMC--R. They are displayedin italics in the following list.
However, filtered notifications can be displayed using the “BBS Faults Statistics”tool. For more information on this tool, refer to NTP < 39 >).
101 : Incorrect ZHCOM message area
102 : Incorrect ZDATA message area
This fault occurs when an attempt is made to change the attributes of a btsobject when the BSC has not yet “unconfigured” the object. When thishappens, the notification Incorrect Z--data Message Area, or FaultNumber: 102 will be generated.
If either of these notifications is received, the operator should perform aBDA audit on the BSC in question. If the audit passes with no differences,then there is no problem. If the audit detects differences, then an On--LineReset and BDABuildmust be performed inside themaintenancewindow.All operators should perform the periodic maintenance of BDA auditstwice weekly to notify them of any inconsistencies.
103 : Unknown communication map
104 : Unknown family value
105 : Unknown operation code
106 : Unknown class value
107 : Unknown instance value
120 : Unexpected message
121 : Requested action already done
122 : Erroneous processing data
123 : Erroneous internal data
This software anomaly may indicate a database problem with the CGI orinconsistencyon thedatabasebetween theBSCand theMSCwhen the cellis unknown during handover (bad neighboring configuration).
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--251
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
124 : Erroneous external data
125 : Erroneous internal static table
126 : Erroneous internal execution report
127 : Lack of internal resources
128 : Problem during cold init
130 : Unexpected message
131 : Requested action already carried out
132 : Erroneous processing data
133 : Erroneous internal data
134 : Erroneous external data
135 : Erroneous internal static table
136 : Erroneous internal execution report
137 : Lack of internal resources
138 : Current task is stopped
139 : Load data KO
140 : No response from a software entity (minor software anomaly that isnot filtered)
The ABS Phase 2 mechanism detects object state inconsistencies withinBSC surveillance tasks. These inconsistencies usually occur whileperforming lock/unlock or delete/create actions at the OMC--R. Once aninconsistent state has been detected within internal BSC tables, ABSPhase 2 correction begins by clearing the surveillance state machines andinitiating a passive chain restart. The restart allows the passive chain toupdate and mirror itself to the active chain BDA.
An ABS Phase 2 is not a BSC failure, but a defense action. Each passivechain suicide, due to ABS Phase 2, generates a dump file that, if reported,can be collected and analyzed byNortel NetworksTechnical Support. Thecaptured data provides information on BSC performance and offersadditional data which is used in patch and version creation.
150 : No response from a software entity
151 : No response from a hardware entity
160 : System error: lack of timer
161 : System error: I/O error
162 : System error: waiting queues (pre)overload
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--252
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
163 : System error: stacks overflow
164 : Local overload defense
170 : System error: FSM error
171 : System error: exchange error
172 : System error: stack error
173 : System error: lack of FSM
174 : System error: system semaphore error
190 : UTE suicide due to SCO
191 : UTE suicide due to application
192 : UTE suicide due to system
200 : Disk I/O
201 : File management system
202 : Disk driver
203 : Mirror disk: services and user functions
The active chain issues this software anomaly when the passive chain hasnot acknowledged a transaction on the mirror link.
The anomaly may indicate a hardware problem on the passive chain:
• 5 V power supply (ondulation or value outside tolerance thresholds)
• SCSI disk
• CPUM board
• rarely, an Ethernet problem
204 : Mirror disk: state machine
205 : Mirror disk: transmission protocol
206 : Transport data link
207 : Data link layer
208 : Access to interconnection area
209 : Data transport layer
210 : Access to multibus II management coprocessor
211 : Switching matrix access and transmission protocol
212 : Switching matrix access
213 : Protocol transmission layer 1
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--253
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
214 : SUP card access management
215 : SCSI: bus management
216 : SCSI: units logical management
217 : SCSI: bus controller management
218 : SCSI: protocol management
219 : X25 layer 1 and 2
220 : HDLC handler
221 : LAPB layer 2
222 : Passive chain restart inhibited to be manually activated
223 : Debug complementary information
224 : Instrumentation complementary information
225 : Ethernet driver
226 : Ethernet driver
229 : System card transmission
230 : BSC capacity reduction
231 : Loader
232 : UC loader
233 : Data loader
234 : Remote SCO access loader
235 : Local SGF access loader
236 : C library
237 : Sympa station
238 : Load function
239 : State machine management
240 : Ethernet layer 2
241 : STA bootstrap
242 : LDB bootstrap
243 : OMF86 loading through asynchronous link
244 : OMF processing function
245 : LDB CSP access cad
246 : Ethernet link access cad
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--254
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
247 : Disk I/O
248 : File management system
249 : Disk driver
250 : Mirror disk: services and user functions
251 : Mirror disk: state machine
252 : Mirror disk: transmission protocol
253 : Transport data link
254 : Data link layer
255 : Access to interconnection area
256 : Data transport layer
257 : Access to multibus II management coprocessor
258 : Switching matrix access and transmission protocol
259 : Switching matrix access
260 : Protocol transmission layer 1
261 : SUP card access management
262 : SCSI: bus management
263 : SCSI: units logical management
264 : SCSI: bus controler management
265 : SCSI: protocol management
266 : X25 layer 1 and 2
267 : HDLC handler
268 : LAPB layer 2
269 : FSM debug
270 : Tape drive management
271 : Disk/tape copy tools management
272 : Ethernet driver
273 : Ethernet driver
276 : System card transmission
277 : System card transmission
278 : Loader
279 : UC loader
BSC fault numbersNortel Networks Confidential Vol. 1 -- 2--255
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
280 : Data loader
281 : Remote SCO access loader
282 : Local SGF access loader
283 : C library
284 : Sympa station
285 : Load function
286 : State machine management
287 : Ethernet layer 2
288 : STA bootstrap
289 : LDB bootstrap
290 : OMF86 loading through asynchronous link
291 : OMF processing function
292 : LDB CSP access cad
293 : Ethernet link access cad
294 : SGF access problem
295 : Driver ram disk
296 : SGF access problem
297 : Driver ram disk
800 : Ethernet management IP
801 : Ethernet management UDP
802 : Ethernet management TCP
803 : Ethernet management RPC
804 : Ethernet management SNMP
805 : Ethernet management IP
806 : Ethernet management UDP
807 : Ethernet management TCP
808 : Ethernet management RPC
809 : Ethernet management SNMP
BSC fault numbers Nortel Networks ConfidentialVol. 1 -- 2--256
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
PAGE INTENTIONALLY LEFT BLANK
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--1
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3 TCU FAULT NUMBERS
3.1 Fault number: 7
iii
Fault number:7 : Card monitoring failureType : equipmentAlarm
FAULT ANALYSIS
This anomaly is sent to the BSC when a TCB2 or TDTI board is absent or faulty.
The following fields in the notification are useful to locate the boards:
the processor type
the processor number
the diagnosis
REACTION OF THE SYSTEM
BSC defense
The BSC unconfigures the object concerned by the notification:
the pcmCircuit object corresponding to a TDTI board, and possibly the signallingLinkobject (corresponding to the SS7 signaling channel on the A interface), and also the xtpobjects.
the transcoderBoard object corresponding to a TCB2 board, and also the xtp objects.
Impact on the service
CAUTIONService reduction
The service is reduced.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--2
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Identify the equipment concerned by the notification.
If a TCB2 board is concerned, go to step 2.
If a TDTI board is concerned, go to step 3.
2 Check the state of the TCB2 board concerned, by performing a “Display all”command on the transcoderBoard object concerned. The instance of thetranscoderBoard object concerned is given in the notification.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 13.
If the operationalState of the transcoderBoard object is “disabled”, the TCB2board concerned is not operational yet. Wait for the end of the softwaredownloading.
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either transcoder object, or ladpLink object, or bsc object, or pcmCircuit(pcmA) object).
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, the TCB2 board is faulty. Go to step 5.
3 Check the state of the TDTI board concerned, by performing a “Display all”command on the transcoder object concerned. The “processor” type given in thenotification is “TDTI”.
If the operationalState of the transcoder object is “enabled”, check which TDTIboard is concerned by the notification.
• If the TDTI board 0 is concerned, the fault is not confirmed. Clear the alarm.Go to step 13.
• If another TDTI board is concerned, check the state of the pcmCircuit object.Go to step 4.
If the operationalState of the transcoder object is “disabled”, the TDTI boardconcerned is not operational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object),or look for a fault number 1157 “Loss of TCU remote layer 2”.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--3
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Check the state of the PCM link, by performing a “Display all” command on thepcmCircuit object (pcmA).
If the operationalState of the pcmCircuit object is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 13.
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 problem on one of the parentobjects (either transcoder object, or ladpLink object, or bsc object).
If the operationalState of the pcmCircuit object is “disabled”, and theavailabilityStatus is “failed”, go to step 6.
On--site maintenance using the OMC--R
Step Action
5 Check the value of the “diagnosis” field in the notification.
If the “diagnosis” value is “no board”, a TCB2boardmust be installed. Go to step9.
If the “diagnosis” value is “negative self--test” , the TCB2 board must bereplaced. Go to step 9.
If the “diagnosis” value is “negative TCB hardware version check”, check thevalue of the “hardwareRef” parameter by performing a “Display” command onthe transcoderBoard object.
• If the value of the “hardwareRef” parameter is the same as the PROMnumber of the TCB2 board concerned, there is a problem with the board. Goto step 9.
• If the value of the “hardwareRef” parameter is different from the PROMnumber of the TCB2 board concerned, change the value of the“hardwareRef” parameter. Then go to step 11.
6 Check the value of the “transcoderIntPcmIntstate” parameter by performing a“Display all” command on the transcoder object.
If the value of the parameter is “working”, clear the alarm and look for aproblem on the PCM link, on site. Go to step 7.
If the value of the parameter is “faulty”, the TDTI board must be replaced. Goto step 10.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--4
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
7 Check the state of the children objects (transcoder and transcoderBoard) byperforming a “Display all” command.
If the operationalState of the objects is “enabled”, go to step 8.
If not, there is a problem with the PCM link. Call the transmission operator.
8 On site, put the jumpers on the TDTI board front panel in Local loopback position(LP). For more information, refer to NTP < 42 >.
If the LFA, AIS, RRA, NOS, FE, SKP, and CRC LEDs are on, the TDTI boardmust be replaced. Go to step 10.
If the LEDs are off, the problem does not lie with the TDTI board, but with thePCM link. Call the transmission operator.
9 Replace the TCB2 board (Field Replaceable Unit):
a. Set the transcoderBoard object (corresponding to the TCB2 board to bereplaced) to “locked”. The instance of the object is given in the notification.
b. Refer to the replacement procedure given in NTP < 42 > for TCB2.
c. Set the transcoderBoard object to “unlocked”. Then go to step 11.
10 Replace the TDTI board (Field Replaceable Unit):
a. Set the pcmCircuit object (corresponding to the TDTI board to be replaced andto the PCM link between the BSC and the TCU, or the TCU and the MSC) to“locked”. If necessary, set the pcmCircuit object (corresponding to the secondPCM link associatedwith this board) to “locked” too. The instance of the objectsis given in the notification.
b. To replace the TDTI board, refer to the replacement procedure given inNTP < 42 >.
c. Set the pcmCircuit object(s) to “unlocked”. Then go to step 11.
Additional checks
Step Action
11 Check the alarm state in the “Current alarm list” window at the OMC--R.
If the alarm has disappeared, go to step 14.
If the alarm persists, go to step 12.
12 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--5
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 13.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
13 Clear the alarm manually.
14 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--6
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.2 Fault number: 8
iii
Fault number:8 : Negative built in self test result for cardType : equipmentAlarm
FAULT ANALYSIS
This anomaly is sent to the BSC when a TCB2 board does not execute its self--testscorrectly.
The type and number of the board are specified in the notification.
REACTION OF THE SYSTEM
BSC defense
The BSC unconfigures the transcoderBoard object corresponding to the TCB2 board, andalso the xtp objects.
Impact on the service
CAUTIONService reduction
The service is reduced.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCB2 board concerned, by performing a “Display all”command on the transcoderBoard object concerned. The instance of thetranscoderBoard object concerned is given in the notification.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 5.
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, the TCB2 board is faulty. Go to step 2.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--7
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Replace the TCB2 board (Field Replaceable Unit):
a. Set the transcoderBoard object (corresponding to the TCB2 board to bereplaced) to “locked”. The instance of the object is given in the notification.
b. Note the values of the notification additional fields (if any), and give them to themanufacturer with the faulty board.
c. Refer to the replacement procedure given in NTP < 42 >.
d. Set the transcoderBoard object to “unlocked”. Then go to step 3.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 6.
If the alarm persists, go to step 4.
4 Check the state of the replacedTCB2board, by performinga “Display all” commandon the transcoderBoard object concerned.
If the operationalState of the transcoderBoard object object is “enabled”, thefault is not confirmed. Go to step 5.
If the operationalState of the transcoderBoard object object is “disabled”, andthe availabilityStatus is “failed”, call the manufacturer.
5 Clear the alarm.
6 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--8
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.3 Fault number: 47
iii
Fault number:47 : Cessation of active alarmsType : communicationsAlarm, environmentalAlarm, equipmentAlarm,
processingErrorAlarm, qualityOfServiceAlarm
FAULT ANALYSIS
Thenotification is sent during aTCU restart. It indicates that active alarms areautomaticallycleared. It concerns the transcoder object.
If the anomaly that triggered these alarms is still present after the TCU restart, new alarmswill be generated at the OMC--R. Thus, no information is lost.
The notification concerns one of these alarm type:
communicationsAlarm
environmentalAlarm
equipmentAlarm
processingErrorAlarm
qualityOfServiceAlarm
There are three types of alarm clearing:
The purge performed by the BSC consists in clearing the alarms linked to thenotifications. The BSC thus indicates that it is purging the notifications that have notbeen sent to the OMC--R yet.
The defense purge performed by the MD consists in clearing the oldest notifications.The threshold is fixed by the static configuration.
The daily purge performed by the MD consists in clearing the notifications that are olderthan N days, every day. N is fixed by the static configuration.
The type of alarm clearing is displayed in the “probableCause” field of the notification (seethe following table).
probableCause No. probableCause wording Type of alarm clearing
64 bscRequest Purge performed by the BSC
65 purgeOnSaturation Defense purge
66 dailyPurge Daily purge
REACTION OF THE SYSTEM
BSC defense
None.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--9
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Impact on the service
None.
FAULT TREATMENT
No maintenance is required.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--10
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.4 Fault number: 493
iii
Fault number:493 : Failure on one of the TCUs clocking sourcesType : communicationsAlarm
FAULT ANALYSIS
This anomaly is sent to the BSC at each state change of a synchronizing clock supportedby a PCM of the A interface in service or by the external clock.
The state change of one of the reference clocks is detected by the TUC board, and it mayimplicate one of the following:
the TUC board
the TDTI board
the external PCM
the external clock
The object and the instance in the alarm identify the suspected clock. The following objectsare concerned by this alarm:
the pcmCircuit object for the PCMs of the A interface
the transcoder object for the external clock
REACTION OF THE SYSTEM
When there is a problem with the clock used for synchronization, the TUC board looks fora new reference clock on one of the following items of equipment. The equipment isselected in the following order:
the external clock as a priority, or
the clocks generated by ‘‘enabled” pcmCircuit objects, or
the clocks generated by ‘‘disabled” pcmCircuit objects, or lastly
the local clock
BSC defense
None.
Impact on the service
None.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--11
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the external clock, by performing a “Display all” command on thetranscoder object concerned.
If the administrativeState of the transcoder object is “locked”, do not take thealarm in account. Go to step 8.
If the operationalState of the transcoder object is “enabled”, go to step 2.
If the operationalState of the transcoder object is “disabled”, the TDTI boardconcerned is not operational yet. Wait for the end of the software downloading.Clear the alarm. Go to step 7.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object),or look for a fault number 1157 “Loss of TCU remote layer 2”. Clear the alarm.Go to step 7.
On--site maintenance using the OMC--R
Step Action
2 This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.Tolocate the fault, look for the following information:
an operator warning with the fault number 497 on the transcoder object toidentify the new reference clock with the value of the “New PCM” field
a beginning--of--fault with the fault number 1151 for the external PCM on theA interface. Then treat the problem on the PCM link.
a beginning--of--fault with the fault number 7 for the TDTI boards. Then go tostep 3.
an operator action on the state of the external clock
3 Replace the TDTI board (Field Replaceable Unit):
a. Set the pcmCircuit object (corresponding to the TDTI board to be replaced andto the PCM link between the BSC and the TCU, or the TCU and the MSC) to“locked”.
b. To replace the TDTI board, refer to the replacement procedure givenin NTP < 42 >.
c. Set the pcmCircuit object(s) to “unlocked”. Then go to step 4.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--12
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
4 Check the network of transmission.
5 Check the alarm state in the “Current alarm list” window at the OMC--R.
If the alarm has disappeared, go to step 8.
If the alarm persists, go to step 6.
6 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 7.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
7 Clear the alarm.
8 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--13
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.5 Fault number: 497
iii
Fault number:497 : New PCM selected as clock referenceType : communicationsAlarm
FAULT ANALYSIS
By this notification, the TCU indicates the new internal PCM chosen as the new internalreference clock.
The transcoder object is the managed object that detects this modification.
The previous clock and the new reference clock are specified in the “PREVIOUSPCM” and“NEW PCM” fields of the notification.
The fields can take the following values:
Field value Meaning Explanation forthe “NEW PCM” field
4 internal clockNo synchronizing PCM is available,so the local clock is selected (see“BSC defense” below).
3 external clock
No PCM of the A interface can beused as a reference clock.The problem may implicate the MSC,the PCM links of the A interface, theTDTI boards, or the internal PCMlinks.
2 clock from the pcmA objectno. 3 The TCU found a new reference clock
1 clock from the pcmA objectno. 1
The TCU found a new reference clockissued by a PCM of the A interface.The previous synchronizing PCM was
0 clock from the pcmA objectno. 0
The previous synchronizing PCM wasfaulty.
REACTION OF THE SYSTEM
BSC defense
If the TCU now uses its local clock as a reference clock, the BSC cannot use this clockanymore. So the BSChas to select another TCUwhose reference clock is issuedby aPCMof the A interface. Then the BSC sends a fault number 497 to indicate its new referenceclock.
Impact on the service
None.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--14
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the PCM link, by performing a “Display all” command on thepcmCircuit objects (pcmA).
If the administrativeState of the pcmCircuit objects is “locked,” do not take thealarm into account. Go to step 7.
If the operationalState of the pcmCircuit object is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 6. Nevertheless, if the interruption lastedless than five minutes, the operationalState remained “enabled” even thoughthere has been a problem. This problem is possibly associatedwith a PCM fault.Refer to NTP < 105 >.
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 problem on one of the parentobjects (either transcoder object, or ladpLink object, or bsc object).
If the operationalState of the pcmCircuit object is “disabled”, and theavailabilityStatus is “failed”, go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Look for alarms or notifications concerning the following equipment:
pcmCircuit links
TDTI boards
internal PCMs
MSC
• If there are alarms, treat them. Go to step 3.
• If there are not any alarms, call the manufacturer.
3 Replace the equipment item(s) according to the other notifications:
a. Set the ‘‘disabled--failed” pcmCircuit (external PCM or TDTI problem) or‘‘disabled--dependency” pcmCircuit (internal PCM problem) to “locked”.
b. Replace the item(s) of equipment. For more information on the replacement ofthe TDTI boards (Field Replaceable Unit), refer to the replacement procedurein NTP < 42 >.
c. Set the pcmCircuit to “unlocked”.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--15
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Additional checks
Step Action
4 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 7.
If the alarm persists, go to step 5.
5 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 6.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
6 Clear the alarm.
7 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--16
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.6 Fault number: 523
iii
Fault number:523 : Fault on internal PCM (BSC, TCU)Type : communicationsAlarm
FAULT ANALYSIS
The beginning of the fault indicates a negative cyclic test made on TS0of oneof the internalPCMs.
The internal PCM is no longer operational.
FAULT TREATMENT
The maintenance procedure is described in NTP < 105 >.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--17
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.7 Fault number: 1150
iii
Fault number:1150 : Loss of DDTI configurationType : equipmentAlarm
FAULT ANALYSIS
This alarm indicates that a TDTI board lost its configuration.
The type and position of the board are specified in the notification.
REACTION OF THE SYSTEM
BSC defense
The system isolates the TDTI board that has lost its configuration.
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--18
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.8 Fault number: 1151
iii
Fault number:1151 : PCM transmission faultType : communicationsAlarm
FAULT ANALYSIS
This notification indicates a transmission problem with one of the PCM links.
The PCM number and the associated TDTI board are specified in the notification.
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--19
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.9 Fault number: 1152
iii
Fault number:1152 : PCM CRC attribute and DDTI CRC strap are not consistentType : processingErrorAlarm
FAULT ANALYSIS
Note: For information on the 1152 alarm for the DDTI board, refer toParagraph 2.81.
This notification is sent by the BSC when an inconsistency is detected between thehardware configuration of a TDTI board and the setting of the BSC.
The “cRC” attribute of the pcmCircuit object (transcoder -- A interface) does not match theCS17 and CS18 jumpers configuration on the TDTI board.
This problem is possibly associated with a PCM fault. Refer to NTP < 105 >.
REACTION OF THE SYSTEM
The system isolates the TDTI board.
Impact on the service
CAUTIONService interruption
The service is reduced or lost, depending on the configuration.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--20
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 At theOMC--R, check the “cRC” attribute valueby performinga “Display” commandon the pcmCircuit object.
If the “cRC” parameter value is “used”, go to step 2.
If the “cRC” parameter value is “not used”, set the pcmCircuit object to “locked”.Set the “cRC” parameter to “used”. Set the pcmCircuit object to “unlocked”.Then go to step 3.
On--site maintenance
Step Action
2 On site, change the CS17 and CS18 jumpers on the TDTI board:
a. Set the pcmCircuit object to “locked”.
b. Change the CS17 and CS18 jumpers on the TDTI board (TDTI E1 -- GSM900/1800) or (TDTI T1 -- GSM 1900). For more information on the jumperpositions, refer to NTP < 42 >.
c. Set the pcmCircuit object to “unlocked”. Then go to step 3.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 6.
If the alarm persists, go to step 4.
4 Check the state of the equipment, by performing a “Display all” command on thepcmCircuit object.
If the operationalState of the object is “enabled”, go to step 5.
If the operationalState of the object is “disabled”, call the manufacturer.
5 Clear the alarm.
6 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--21
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.10 Fault number: 1156
iii
Fault number:1156 : TCU downloading failureType : equipmentAlarm/communicationsAlarm
FAULT ANALYSIS
The BSC tries to download the TCB2 software to the TUC board twice at the maximum.
This notification is issued when the software downloading from the TCB2 board to the TUCboard failed.
The “Download Status” field in the notification indicates the source of the failure:
0 = File access error
1 = Failure on the second attempt of downloading
The downloading failure can be due to:
a transient transmission problem
the configuration data (software release, etc.)
the BSC
the PCM link between the BSC and the TCU (DDTI board, PCM, and TDTI board)
the TCB2 board
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--22
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.11 Fault number: 1157
iii
Fault number:1157 : Loss of TCU remote layer 2Type : communicationsAlarm
FAULT ANALYSIS
TheBSCdetects a loss of layer 2 to the TCUand sends this alarm to theOMC--R. TheTCUis completely isolated until the restoration of layer 2.
The TUC board resets itself every 30 seconds, then it resets the TDTI board. The PCM linkis cut off.
This alarm can indicate a configuration problem:
TEI value
PROM version of the TUC board
This alarm can also implicate the following equipment items:
BSC
link between the BSC and the TCU
TUC board
FAULT TREATMENT
This problem is associated with a PCM fault. Refer to NTP < 105 >.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--23
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.12 Fault number: 1159
iii
Fault number:1159 : Invalid message received on TCU--BSC interfaceType : communicationsAlarm
FAULT ANALYSIS
This warning notification is issued after a software fault.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService interruption
The service may be reduced, or even lost.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object.
If the operationalState of the transcoder object is “enabled”, go to step 2.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, go to step 4.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--24
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
2 Look for other fault numbers 1159.
If the fault number 1159 is seldomemitted, it is a transient problem.Go tostep 6.
If it is often emitted, call the manufacturer.
3 Look for other notifications concerning the TCU, and treat them. Then go to step 4.
Additional checks
Step Action
4 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 7.
If the alarm persists, go to step 5.
5 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 6.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
6 Clear the alarm.
7 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--25
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.13 Fault number: 1160
iii
Fault number:1160 : TCU negative acknowledgment indicationType : communicationsAlarm
FAULT ANALYSIS
This warning notification indicates a software anomaly or hardware fault.
The “Source” field can contain one of the following sources:
1 Downloading not expected
2 Block number out of window
3 Window out of range
4 Too many received blocks (number out of range)
5 Unknown file reference
6 Downloading already running
7 Unknown nature for downloading stop
64 TCU connection refusal
65 PCMA/TCB init or desinit refusal
74 Timer expiration: init/desinit TCB/PCMA
80 Timeout on reset timer, or init dialog timer
81 Timeout on downloading timer
82 Timeout on init/desinit/read PCMA or TCB
83 Timeout on connection timer
84 Mark block out of sequence, or timeout on mark timer
REACTION OF THE SYSTEM
BSC defense
None.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--26
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Impact on the service
If there is a software downloading problem (source 1 to 7), the operationalState of thetranscoder object remains “disabled”.
CAUTIONService interruption
The service is lost.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object.
If the operationalState of the transcoder object is “enabled”, go to step 5.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, go to step 2.
2 Look for other notifications concerning the TCU, and treat them. Then go to step 3.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 6.
If the alarm persists, go to step 4.
4 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 5.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
5 Clear the alarm.
6 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--27
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.14 Fault number: 1163
iii
Fault number:1163 : Preemption of a terrestrial circuit by a signalling linkType : processingErrorAlarm
FAULT ANALYSIS
The BSC reserves four terrestrial circuits to support a CCS7 or X25 signaling link to theMSC through the TCU. This action results in the transmission of four notifications and theswitching off of four LEDs of a TCB2 board, which no longer receives the data carried bythis time slot of the PCM of the Ater interface.
The fault number 1163 is sent when a signallingLink object is set to ‘‘unlocked” or ‘‘locked”,without the terrestrial circuits (carried by the TCB2 0 board) being put out of service first.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance operation is required.
The alarms stop when the corresponding terrestrial circuits are put out of service.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--28
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.15 Fault number: 1165
iii
Fault number:1165 : iiiVAL_STP_ANO_TRC_BLOCKEDType : processingError
FAULT ANALYSIS
The PCMA contains at least one hscsd blocked terrestrial circuit. This notification isgenerated when a first terrestrial circuit of a PCMA is preempted for HSCSD, and when thelast preempted terrestrial circuit of PCMA is unblocked.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
No maintenance operation is required.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--29
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.16 Fault number: 1170
iii
Fault number:1170 : External alarm loop on TCUType : environmentalAlarm
FAULT ANALYSIS
By this alarm, the TCU indicates the state change of the external alarm.
This alarm can be configured by the operator.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the value of the “transcoderAlarmMask” parameter, by performing aDisplayall” command on the transcoder object.
If the external alarm is configured, go to step 2.
If the external alarm is not configured, configure it by performing a “set”command on the transcoder object. Then go to step 3.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--30
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
On--site maintenance
Step Action
2 Perform the appropriate treatment. The operation to be executed to clear this typeof alarm depends on the alarm loop configuration defined by the operator. Then goto step 3.
Additional checks
Step Action
3 Check that an end--of--alarm notification is generated when the alarm is cleared.
4 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--31
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.17 Fault number: 1171
iii
Fault number:1171 : TCU power faultType : equipmentAlarm
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of a power supply unit.
The alarm indicates:
the object that detected the anomaly: the TUC board
the type of fault: “TCU power fault”
But this alarm does not indicate which power supply unit is faulty.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None, if only one power supply unit is faulty.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--32
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object concerned.
If the operationalState of the transcoder object is “enabled”, clear the alarm. Goto step 9.
If the operationalState of the transcoder object is “disabled”, the TCU is notoperational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, one or several power supply units are faulty. Go tostep 2.
On--site maintenance
Step Action
2 Perform an electrical test on the power supply units:
a. Locate the power supply units (PSU) in the shelf of the TCU cabinet.
b. Put the multimeter in DC voltage mode.
c. Perform the following test on each power supply unit:
i. Connect the “V” terminal of the multimeter to the red 5V terminal, and the“COM” terminal of the multimeter to the blue 5V terminal (seeNTP < 42 >).
ii. Check that the voltage measurement is 5.2V (±2%).
If the voltage is correct, go to step 7.
If the voltage is not correct, go to step 3.
3 Check the fuse of the power supply unit
a. Switch off the faulty power supply unit.
b. Locate the 4A fuse on the front panel of the power supply unit (seeNTP < 42 >).
c. Extract the fuse using a screwdriver.
d. Check the fuse with the multimeter.
If the fuse is operational, the power supply unit is out of order and it must bereplaced. Go to step 5.
If the fuse is not operational, it must be replaced. Go to step 4.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--33
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Replace the fuse of the power supply unit:
a. Insert a new fuse.
b. Switch on the power supply unit.
c. Go to step 7.
5 Replace the faulty power supply unit (Field Replaceable Unit)
a. For more information, refer to the replacement procedure (see NTP < 42 >).
b. Then go to step 7.
6 Call the manufacturer.
Additional checks
Step Action
7 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 10.
If the alarm persists, go to step 8.
8 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 9.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer. Go to step 6.
9 Clear the alarm.
10 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--34
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.18 Fault number: 1172
iii
Fault number:1172 : TCU fan board faultType : equipmentAlarm
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of the VENT board.
The alarm indicates:
the object that detected the anomaly: the TUC board
the type of fault: “TCU fan board fault”
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--35
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object concerned.
If the operationalState of the transcoder object is “enabled”, clear the alarm. Goto step 9.
If the operationalState of the transcoder object is “disabled”, the TCU is notoperational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, there is a problem with the VENT board. Go tostep 2.
On--site maintenance
Step Action
2 Safety instructions
CAUTIONESDS handling precautions
Wear the antistatic bracelet when performing the followingmaintenance procedure, especially when handling boards.
3 Check the power supply fuse (on the terminal block):
a. Open the mobile frame of the TCU cabinet.
b. Locate the terminal block at the bottom of the cabinet.
c. Locate the power supply fuse on the terminal block (see NTP < 42 >).
d. Extract the fuse.
e. Check it with a multimeter.
If the fuse is operational, go to step 4.
If the fuse is not operational, replace the fuse. Go to step 5.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--36
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Check the fuse of each faulty fan (on the VENT board)
a. Open the mobile frame of the TCU cabinet.
b. Locate the VENT board on the side of the mobile frame.
c. Locate the fuses (see NTP < 42 >).
d. Remove the board plastic cover.
e. Check the fuse(s) with a multimeter.
If the fuse(s) is/are operational, there is a problem with the VENT board. Goto step 6.
If one or several fuses are not operational, replace it/them. Go to step 5.
5 Replace the fuse
If the fuse is located on the terminal block, replace it. Then go to step 7.
If the fuse is located on the VENT board, replace it according to the correctivemaintenance procedure (see NTP < 42 >). Then go to step 7.
6 Replace the VENT board. Then go to step 7.
Additional checks
Step Action
7 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 10.
If the alarm persists, go to step 8.
8 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 9.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
9 Clear the alarm.
10 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--37
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.19 Fault number: 1173
iii
Fault number:1173 : TCU fan faultType : equipmentAlarm
FAULT ANALYSIS
By this alarm, the TCU indicates the operating state change of one or more fans.
The alarm indicates:
the object that detected the anomaly, i.e. the TUC board
the type of fault: “TCU fan fault”
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--38
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object concerned.
If the operationalState of the transcoder object is “enabled”, clear the alarm. Goto step 10.
If the operationalState of the transcoder object is “disabled”, the TCU is notoperational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, one or several fans are faulty. Go to step 2.
On--site maintenance
Step Action
2 Safety instructions
CAUTIONESDS handling precautions
Wear the antistatic bracelet when performing the followingmaintenance procedure, especially when handling boards.
3 Check how many fans are stopped in the ventilation block.
If all the fans in one ventilation block are not running, check the fuseof theVENTboard corresponding to this ventilation block. The fuse is located on the terminalblock. Go to step 4.
If one or two fans in one ventilation block are not running, check the fuse of eachfaulty fan. The fuses are located on the VENT board. Go to step 5.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--39
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
4 Check the fuse of the VENT board (on the terminal block)
a. Open the mobile frame of the TCU cabinet.
b. Locate the terminal block at the bottom of the cabinet.
c. Locate the fuse of the VENT board on the terminal block (see NTP < 42 >).
d. Extract the fuse.
e. Check it with a multimeter.
If the fuse is operational, replace the ventilation block. Go to step 7.
If the fuse is not operational, replace the fuse. Go to step 6.
5 Check the fuse of each faulty fan (on the VENT board)
a. Open the mobile frame of the TCU cabinet.
b. Locate the VENT board on the side of the mobile frame (see NTP < 42 >).
c. Locate the fuse of the faulty fan, using the following table and NTP < 42 >).
Fan (Note) Fuse Value(GSM 900/1800)
Value(GSM 1900)
Left F1 0.63 A 0.8 A
Middle F3 0.63 A 0.8 A
Right F5 0.63 A 0.8 A
Note: when looking at the front of the ventilation block.
d. Remove the board plastic cover.
e. Check the fuse with a multimeter.
If the fuse is operational, there is a problem with the ventilation block. Go tostep 7.
If the fuse is not operational, replace it. Go to step 6.
6 Replace the fuse
If the fuse is located on the terminal block, replace it. Then go to step 8.
If the fuse is located on the VENT board, replace it according to the correctivemaintenance procedure (see NTP < 42 >). Then go to step 8.
7 Replace the ventilation block (Field Replaceable Unit)
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--40
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
a. Replace the ventilation block that has (a) faulty fan(s) according to the correctivemaintenance procedure (see NTP < 42 >).
b. Then go to step 8.
Additional checks
Step Action
8 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 11.
If the alarm persists, go to step 9.
9 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 10.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
10 Clear the alarm.
11 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--41
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.20 Fault number: 1174
iii
Fault number:1174 : TCU clock faultType : communicationsAlarm
FAULT ANALYSIS
This alarm indicates a clock problem. The PLL of the TUC board is stopped.
The alarm indicates the TUC board that is responsible for the anomaly.
However, the synchronizing PCM link can be faulty too.
REACTION OF THE SYSTEM
BSC defense
If the BSC is synchronized by this TCU, the BTSs clock will drift.
Impact on the service
CAUTIONService interruption
Then the service is lost, or at least there are handover problems(intra BTS and inter BTS as well).
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--42
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU by performing a “Display all” command on thetranscoder object concerned.
If the operationalState of the transcoder object is “enabled”, clear the alarm. Goto step 8.
If the operationalState of the transcoder object is “disabled”, the TCU is notoperational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, the TCU clock is faulty. Go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Identify the synchronizing PCM link:
a. Look at the synchronization LEDs on the front panel of the TUC board (seeNTP < 42 >).
b. Change the position of the jumpers on the TDTI board front panel to perform aPCM link switchover. For more information, refer to NTP < 42 >.
c. Check that the alarm has disappeared, by performing a “Display all” commandon the transcoder object.
If the alarm has disappeared, the problem lies with the PCM link, or with theTUC board.
If the alarm has not disappeared, change the position of the jumpers on theTDTI board front panel to perform another PCM link switchover.
If the problem does not lie with the TUC board, the external clock (if there isone), or the MSCmay be faulty, or there is a general problem on all the PCMlinks.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--43
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
3 Check the clock of the selected PCM.
If the PCM is suspected, repair the PCM link. Go to step 4.
If not, replace the TUC board. Go to step 5.
4 Repair the PCM link.
5 Replace the TUC board (Field Replaceable Unit):
a. Perform a shutting down on all the xtp objects of the TCU.
b. At the OMC--R, set the transcoder object mentioned in the alarm to ‘‘locked”.
c. On site, to replace the TUC board, refer to the replacement procedure given inNTP <41>.
d. At the OMC--R, set the transcoder object mentioned in the alarm to ‘‘unlocked”.Then go to step 6.
Additional checks
Step Action
6 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 9.
If the alarm persists, go to step 7.
7 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 8.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
8 Clear the alarm.
9 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--44
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.21 Fault number: 1180
iii
Fault number:1180 : TCB downloading failureType : processingErrorAlarm
FAULT ANALYSIS
This notification indicates that the TCB2 software downloading failed.
The TUC board makes a maximum of two downloading attempts. If the second attemptfails, the TUC board informs the BSC.
The TCB2 board concerned is specified in the beginning--of--fault notification.
The additional field in the notification indicates the downloading state of the TCB2 board.The field can take the following values:
1 “Failure on the second attempt of downloading”
2 “No layer 1 synchronization for downloading”
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
The xtp objects cannot be used any more.
CAUTIONService reduction
The service is reduced.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--45
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCU, by performing a “Display all” command on thetranscoder object concerned.
If the operationalState of the transcoder object is “enabled”, clear the alarm. Goto step 11.
If the operationalState of the transcoder object is “disabled”, the TCU is notoperational yet. Wait for the end of the software downloading.
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either ladpLink object, or bsc object, or pcmCircuit (pcmAter) object).
If the operationalState of the transcoder object is “disabled”, and theavailabilityStatus is “failed”, the TCB software downloading failed. Go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Look at the additional field of the notification:
If the value is “Failure on the second attempt of downloading”, go to step 3.
If the value is “No layer 1 synchronization for downloading”, go to step 6.
3 Check the homogeneity of TCB2 boards in the shelf concerned.
If the TCB2 boards are homogeneous, go to step 4.
If the TCB2 boards are heterogeneous, replace the heterogeneous one(s). Goto step 7.
4 Check the version of the software to be installed on this TCB board in relation tothe PROM version:
a. Check the value of the “hardwareRef” parameter by performing a “Display”command on the transcoderBoard object.
• If the value of the “hardwareRef” parameter is the same as the PROMnumber of the TCB2 board concerned, go to step 4b.
• If the value of the “hardwareRef” parameter is different from the PROMnumber of the TCB2 board concerned, change the value of the“hardwareRef” parameter. Then go to step 9.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--46
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Step Action (Continued)
b. Check the value of the “sWVersionRunning” parameter by performing aDisplaycommand on the software object associated with the transcoderBoard object.
If the value of the “sWVersionRunning” parameter is consistent with therequired software release (see the operator software release documents),then there is a problem with the TCB software itself. Go to step 5.
If the value of the “sWVersionRunning” parameter is not consistent with therequired software release, modify the “sWVersionRunning” parameteraccordingly.
5 Check that the TCB software is installed in the OMC--R:
a. In the OMC--R “Browser window, select the md object.
b. Select the List option in the EFT submenu of the Configuration menu. The listof the EFTs installed in theOMC--R is then displayed in a “Session Log” window.
If the TCB software is installed in the OMC--R:
i. Download it again on the BSC disk. For more information, refer to NTP 34.
ii. Then, set the transcoderBoard object to “unlocked” to trigger the softwaredownloading in the board itself.
– If the software problem disappeared, go to step 9.
– If there is still a software problem, replace the TCB2 board. Go tostep 7.
If the TCB software is not installed in the OMC--R:
i. Install it on the OMC--R. For more information, refer to NTP 34 .
ii. Then download it on the BSC disk. For more information, refer to NTP 34.
iii. Then, set the transcoderBoard object to “unlocked” to trigger the softwaredownloading in the board itself.
– If the software problem disappeared, go to step 9.
– If there is still a software problem, replace the TCB2 board. Go tostep 7.
6 Check that there are no alarms concerning the internal PCM links between theTUCboard and the TCB2 board (fault number 523 “Fault on internal PCM (BSC, TCU)”).
If the problem does not concern the internal PCM links, go to step 7.
If there are alarms concerning the internal PCM links, refer to NTP < 105 >. Goto step 12.
7 Replace the TCB2 board (Field Replaceable Unit):
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--47
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
a. Set the transcoderBoard object to “locked”.
b. Replace the TCB2 board. For more information, refer to the replacementprocedure given in NTP < 42 >.
c. Set the transcoderBoard object to “unlocked”.
If there is still a software downloading problem, go to step 8.
If the software downloading problem has disappeared, go to step 9.
8 Replace the TUC board (Field Replaceable Unit)
a. Set the transcoder object to “locked”.
b. Replace the TUC board. For more information, refer to the replacementprocedure given in NTP < 42 >.
c. Set the transcoder object to “unlocked”. Then go to step 9.
Additional checks
Step Action
9 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 12.
If the alarm persists, go to step 10.
10 Check the state of the replaced equipment, by performing a “Display all” commandon the object concerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 11.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
11 Clear the alarm.
12 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--48
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.22 Fault number: 1184
iii
Fault number:1184 : Internal TCB--2 failureType : equipmentAlarm
FAULT ANALYSIS
The TCB2 board informs the TUC board of a serious anomaly on one or more SPUs. TheTUC board resets the TCB2 board.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService reduction
The service is reduced.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCB2 board concerned, by performing a “Display all”command on the transcoderBoard object concerned.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 5.
If the operationalState of the transcoderBoard object is “disabled”, the TCB2board concerned is not operational yet. Wait for the end of the softwaredownloading.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--49
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Step Action (Continued)
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either transcoder object, or ladpLink object, or bsc object, or pcmCircuit(pcmA) object).
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, the TCB2 board is faulty. Go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Replace the TCB2 board (Field Replaceable Unit):
a. Set the transcoderBoard object (corresponding to the TCB2 board to bereplaced) to “locked”. The instance of the object is given in the notification.
b. Refer to the replacement procedure given in NTP < 42 >.
c. Set the transcoderBoard object to “unlocked”. Then go to step 3.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 6.
If the alarm persists, go to step 4.
4 Check the state of the replacedTCB2board, by performinga “Display all” commandon the transcoderBoard object concerned.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Go to step 5.
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, call the manufacturer.
5 Clear the alarm.
6 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--50
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.23 Fault number: 1185
iii
Fault number:1185 : TCB--2 synchronization failureType : communicationsAlarm
FAULT ANALYSIS
The TCB2 board informs the TCU board of a synchronization failure on the Ater interfaceand/or the Abis interface (uplink, from the BTS to the TCB2 board).
This fault number indicates the number of loss of synchronization from the same TCB2board.
The alarm indicates a transient problem on a PCM link that is not supervised by the BSCor the BTS.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService reduction
The service quality is reduced.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--51
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
On--site maintenance using the OMC--R
Step Action
1 Look for an alarm concerning the PCM link (Abis or Ater), and the BTS.
If there are alarms, refer to NTP < 105 >.
If there is no alarm on the PCM link (Abis or Ater) or the BTS, go to step 2.
2 Check the continuity of the links between the BSC and the BTS:
the operation of the BTS (btsSiteManager and transceiverEquipment objects)
the link between the BSC and the BTS
the operation of the BSC
the link between the BSC and the TCU
the TUC and/or the TCB board of the TCU
• If there is a problem with one of these items of equipment, treat it. Then goto step 3.
• If all the items of equipment are operational, call the manufacturer.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 5.
If the alarm persists, go to step 4.
4 Call the manufacturer.
5 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--52
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.24 Fault number: 1186
iii
Fault number:1186 : External TCB--2 failureType : equipmentAlarm
FAULT ANALYSIS
The TCB2 board receives a type of frame that cannot be decoded and informs the TUCboard.
The TCB2 board returns an external anomaly and indicates the TRAUs in fault.
It is usually a transient transmission fault.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 Check the state of the TCB2 board concerned, by performing a “Display all”command on the transcoderBoard object concerned.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 5.
If the operationalState of the transcoderBoard object is “disabled”, the TCB2board concerned is not operational yet. Wait for the end of the softwaredownloading.
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “dependency”, look for a problem on one of the parentobjects (either transcoder object, or ladpLink object, or bsc object, or pcmCircuit(pcmA) object).
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, the TCB2 board is faulty. Go to step 2.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--53
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
On--site maintenance using the OMC--R
Step Action
2 Replace the TCB2 board (Field Replaceable Unit):
a. Set the transcoderBoard object (corresponding to the TCB2 board to bereplaced) to “locked”.
b. Refer to the replacement procedure given in NTP < 42 >.
c. Set the transcoderBoard object to “unlocked”. Then go to step 3.
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 6.
If the alarm persists, go to step 4.
4 Check the state of the replacedTCB2board, by performinga “Display all” commandon the transcoderBoard object concerned.
If the operationalState of the transcoderBoardobject is “enabled”, the fault is notconfirmed. Go to step 5.
If the operationalState of the transcoderBoard object is “disabled”, and theavailabilityStatus is “failed”, call the manufacturer.
5 Clear the alarm.
6 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--54
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.25 Fault number 1190
iii
Fault number:1190 : Restart after TCU suicideType : processingErrorAlarm
FAULT ANALYSIS
When this message is displayed at the OMC--R, the link between the BSC and the TCU(TUC board) is restored.
If there is a hardware problem, other beginning--of--fault alarms are present.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
CAUTIONService reduction
Some communications were lost during the TCU suicide.
FAULT TREATMENT
On--site maintenance
Step Action
1 Search for the source of the restart
If there are alarms indicating ahardwareproblem, treat them. Thengo to step 2.
If this fault number 1190 is often emitted, call the manufacturer.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--55
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
Additional checks
Step Action
2 Check the notification state in the “Current alarm list” window.
If the notification has disappeared, go to step 5.
If the notification persists, go to step 3.
3 Check the state of the TCU, by performing a “Display all” command on the objectconcerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 4.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
4 Clear the notification.
5 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--56
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.26 Fault number 1290
iii
Fault number:1290 : Unacknowledged message on a interfaceType : communicationsAlarm
FAULT ANALYSIS
This user message describes one of the following two situations:
The MSC did not answer after the BSC tried twice to send the same message on theA interface.
TheMSC answered to the BSC, but the BSC could not understand the message. In thelatter case, two fault numbers 1310 (”A interface protocol error indication”) are emitted.
The “message type” field indicates the GSM coding of the message that was repeated bythe BSC on the A interface without being acknowledged by the MSC:
Reset circuit
Block
Unblock
Circuit group block
Circuit group unblock
The “Circuit Identity Code” field contains the CIC coded number declared at the BSC levelbut unknown to the MSC.
REACTION OF THE SYSTEM
BSC defense
None. The TMG does not use these channels.
Impact on the service
The communication cannot be established on the considered channels.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--57
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Maintenance using the OMC--R
Step Action
1 Search for the reason why there is such an inconsistent configuration.
If it was configured this way on purpose, to prepare a network extension forinstance, this fault number emission is normal, and nomaintenance is required.Go to step 3.
If it was not configured this way on purpose, then there is an error in theconfiguration. Go to step 2.
2 Correct the inconsistent configuration in one of the following ways:
At the OMC--R, delete the CIC indicated in the notification, OR
At the OMC--S, create the equivalent CIC for the MSC.
Additional checks
Step Action
3 Check the notification state in the “Current alarm list” window.
If the notification has disappeared, go to step 5.
If the notification persists, go to step 3.
4 Check the state of the TCU, by performing a “Display all” command on the objectconcerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 4.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
5 Clear the notification.
6 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--58
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.27 Fault number 1310
iii
Fault number:1310 : A interface protocol error indicationType : communicationsAlarm
FAULT ANALYSIS
This warning notification is caused by a software anomaly on the A interface and the MSC.
The BSC receives an unknown message from the MSC. Most often there is anincompatibility between what the MSC sends and what the BSC knows.
The “Source” field of the notification can contain the following values:
10 --Unknown CIC (in this case, data length (lg_data) = 2, and the received CIC whichis incorrect is dumped. This dump is in hexadecimal representation and appears in aform similar to 0x0799).
26 --Unknown IEI
27 --Bad length of element
51 --Unknown message in this way
52 --Too short reserved length -- imperative reserved area
53 --Minimum length not respected
54 --Unknown message type
55 --Unknown message group
65 --Essential element missing
66 --Wrong mandatory element
The MSC version is incompatible with the BSC.
The “Circuit Identity Code” field contains the CIC coded number declared at the MSC levelbut unknown to the BSC. This is true for all of the 1310 fault.
REACTION OF THE SYSTEM
BSC defense
None. The TMG does not use these channels.
Impact on the service
The communication cannot be established on the considered channels.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--59
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
FAULT TREATMENT
Maintenance using the OMC--R
Step Action
1 Look at the source given in the “Source” field of the notification.
If the source is “10 Unknown CIC”, go to step 2.
If the source is “26”, “27”, “51”, “52”, “53”, “54”, “55”, “65”, or “66”, it is a transientproblem. If this notification is often emitted, call the manufacturer.
2 Search for the reason why there is such an inconsistent configuration.
If it was configured this way on purpose, to prepare a network extension forinstance, this fault number emission is normal, and nomaintenance is required.Go to step 4.
If it was not configured this way on purpose, then there is an error in theconfiguration. Go to step 3.
3 Correct the inconsistent configuration in one of the following ways:
At the OMC--S, delete the CIC indicated in the notification, OR
At the OMC--R, create the equivalent CIC for the BSC, and the xtp objects aswell.
Additional checks
Step Action
4 Check the notification state in the “Current alarm list” window.
If the notification has disappeared, go to step 7.
If the notification persists, go to step 5.
5 Check the state of the TCU, by performing a “Display all” command on the objectconcerned.
If the operationalState of the object is “enabled”, the fault is not confirmed. Goto step 6.
If the operationalState of the object is “disabled”, and the availabilityStatus is“failed”, call the manufacturer.
6 Clear the notification.
7 The procedure is complete.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--60
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
3.28 Fault number 1311
iii
Fault number:1311 : Reset downlinkType : communicationsAlarm
FAULT ANALYSIS
This warning notification indicates a state change of the traffic state of the MSC.
The possible values of the “MSC traffic state” field are:
0 = MSC traffic opened
1 = MSC traffic closed
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
When the value of the “MSC traffic state” is “MSC traffic closed”, no communication canbe established.
CAUTIONService interruption
The service is lost.
FAULT TREATMENT
This is a transient message. As soon as the A interface is operational, another message1311 is sent, with “MSC traffic opened” in the “MSC traffic state” field.
No maintenance is required.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--61
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.29 Fault number 1363
iii
Fault number:1363 : SCCP protocol error indicationType : communicationsAlarm
FAULT ANALYSIS
The problem lies in the A interface and the MSC. Most often, it is a transient problem.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 If this notification 1363 is often emitted, check the state of the SS7 signalingchannel, by performing a “Display all” command on the signallingLink objectconcerned.
If the operationalState of the signallingLink object is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 4.
If the operationalState of the signallingLink object is “disabled”, and theavailabilityStatus is “failed”, there is a problem with the SS7 signaling channel.Go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Look for alarms concerning the signallingLink object, and concerning the MSC aswell. Treat them and then go to step 3.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--62
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 5.
If the alarm persists, call the manufacturer.
4 Clear the alarm.
5 The procedure is complete.
TCU fault numbersNortel Networks Confidential Vol. 1 -- 3--63
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
3.30 Fault number 1364
iii
Fault number:1364 : MTP3 protocol error indicationType : communicationsAlarm
FAULT ANALYSIS
The problem lies in the A interface and the MSC. Most often it is a transient problem.
REACTION OF THE SYSTEM
BSC defense
None.
Impact on the service
None.
FAULT TREATMENT
Preliminary checks
Step Action
1 If this notification 1364 is often emitted, check the state of the SS7 signalingchannel, by performing a “Display all” command on the signallingLink objectconcerned.
If the operationalState of the signallingLink object is “enabled”, the fault is notconfirmed. Clear the alarm. Go to step 4.
If the operationalState of the signallingLink object is “disabled”, and theavailabilityStatus is “failed”, there is a problem with the SS7 signaling channel.Go to step 2.
On--site maintenance using the OMC--R
Step Action
2 Look for alarms concerning the signallingLink object, and concerning the MSC aswell. Treat them and then go to step 3.
TCU fault numbers Nortel Networks ConfidentialVol. 1 -- 3--64
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Additional checks
Step Action
3 Check the alarm state in the “Current alarm list” window.
If the alarm has disappeared, go to step 5.
If the alarm persists, call the manufacturer.
4 Clear the alarm.
5 The procedure is complete.
IndexNortel Networks Confidential Vol. 1 -- i
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
BBSC 120005 Restart after chain suicide due to internal cause, or OMC, Vol. 1 -- 2--1Source (0) Software anomaly counter threshold, Vol. 1 -- 2--4Source (1) CPUE (MPU) non present, Vol. 1 -- 2--5Source (2) CPUE (MPU) or CPUM (OMU) built--in self test failed, Vol. 1 -- 2--7Source (3) CPUE (MPU) or CPUM (OMU) setup failed , Vol. 1 -- 2--9Source (4) Incorrect Multibus II card name, Vol. 1 -- 2--11Source (5) No communication with CPUE (MPU) card, Vol. 1 -- 2--13Source (8) Error in BSC state machine handler (GAUT), Vol. 1 -- 2--15Source (10) Error in switchover sequence, Vol. 1 -- 2--16Source (11) BDA KO during switchover sequence, Vol. 1 -- 2--17Source (12) Invalid mirror partitions after switchover on the new active chain, Vol. 1 -- 2--18Source (14) Loss of duplex link detected on passive chain, Vol. 1 -- 2--19Source (15) Inconsistency between active and passive chains, Vol. 1 -- 2--20Source (16) Context overflow for BSC (MDB) defense, Vol. 1 -- 2--21Source (20) Switching while passive chain DP loading, Vol. 1 -- 2--22Source (21) Error detected during check partition, Vol. 1 -- 2--23Source (23) CPUE BOOT flashing failed, Vol. 1 -- 2--24Source (24) Restart to take into account the new BSC customization, Vol. 1 -- 2--25Source (25) Degraded disk, Vol. 1 -- 2--26Source (27) Cancellation of probative phase, Vol. 1 -- 2--28Source (28) End of probative phase OK, Vol. 1 -- 2--29Source (29) New BDA edition, Vol. 1 -- 2--30Source (30) Preparation of a type 5 upgrade, Vol. 1 -- 2--31Source (31) Type 5 upgrade running, Vol. 1 -- 2--32Source (32) Old release running on passive chain, Vol. 1 -- 2--33Source (33) Unsuccessful preparation of a type 5 upgrade, Vol. 1 -- 2--34Source (50) BDA inconsistency, Vol. 1 -- 2--35Source (51) GES--MS / GES--SL are incoherent, Vol. 1 -- 2--37Source (52) Passive chain does not answer on RGA request, Vol. 1 -- 2--38Source (53) Passive chain suicide on RGA request, Vol. 1 -- 2--39Source (101) No communication with switching board, Vol. 1 -- 2--40Source (102) No communication with ECI card or fault on ECI card, Vol. 1 -- 2--42Source (103) No communication with SICX card or fault on SICX card, Vol. 1 -- 2--45Source (104) No communication with slave switching board, Vol. 1 -- 2--47Source (105) No communication with SLS card or fault on SLS card, Vol. 1 -- 2--49Source (106) Operator request, Vol. 1 -- 2--51Source (107) Degraded REM link, Vol. 1 -- 2--52Source (128) No communication with SICD or RCB card or fault on SICD or RCB card, Vol. 1 -- 2--53Source (129) SICD port selftests not OK, Vol. 1 -- 2--56Source (161) No communication with CCS7 card or fault on CCS7 card, Vol. 1 -- 2--58Source (162) CCS7 port selftests not OK, Vol. 1 -- 2--60Source (176) No communication with TCU card or fault on TCU card, Vol. 1 -- 2--62Source (192) O&M bus selftests not OK, Vol. 1 -- 2--65
6 Restart after chain suicide due to trap, Vol. 1 -- 2--677 Card monitoring failure, Vol. 1 -- 2--688 Negative built in self test result for card, Vol. 1 -- 2--7211 Restart after chain suicide due to NMI, Vol. 1 -- 2--7413 Chain restart in progress, Vol. 1 -- 2--7814 Indication of chain restart cause, Vol. 1 -- 2--7915 Chain restart due to intermediate card, Vol. 1 -- 2--8016 Fault on active/passive chains link, Vol. 1 -- 14--83
Index Nortel Networks ConfidentialVol. 1 -- ii
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
20 Alarm on clockship of the SUP board, Vol. 1 -- 14--8521 Beginning of circular file pre--overflow, Vol. 1 -- 14--8722 End of circular file pre--overflow, Vol. 1 -- 14--8923 Beginning of BSC disk partition update, Vol. 1 -- 14--9024 End of BSC disk partition update, Vol. 1 -- 14--9126 Fault on BSC/OMC--R link, Vol. 1 -- 14--9233 Saturation on an internal file used for marking climb, Vol. 1 -- 14--9334 Saturation on a storage zone for marking climb, Vol. 1 -- 14--9441 Beginning of saturation of the event reporting process in the BSC, Vol. 1 -- 14--9542 End of saturation of the event reporting process, Vol. 1 -- 14--9943 Loss of access to the equipment shelf, Vol. 1 -- 14--100Source (0) Cannot access to all working UTE, Vol. 1 -- 14--101Source (1) O&M bus selftest not OK, Vol. 1 -- 14--103
44 Board UTE access problem, Vol. 1 -- 14--10545 Partial hard disk degradation, Vol. 1 -- 14--10746 Total hard disk degradation, Vol. 1 -- 14--11147 Cessation of active alarms, Vol. 1 -- 14--115332 External alarm loop 0, Vol. 1 -- 14--116333 External alarm loop 1, Vol. 1 -- 14--118334 External alarm loop 2, Vol. 1 -- 14--120335 External alarm loop 3, Vol. 1 -- 14--122336 External alarm loop 4, Vol. 1 -- 14--124337 External alarm loop 5, Vol. 1 -- 14--126338 External alarm loop 6, Vol. 1 -- 14--128339 External alarm loop 7, Vol. 1 -- 14--130400 Breakdown of one power supply of the EQPD1 shelf, Vol. 1 -- 14--132401 Breakdown of one power supply of the EQPD0 shelf, Vol. 1 -- 14--134402 Fan fault on the MPU shelf, Vol. 1 -- 14--136403 Fan fault on the MPU shelfs power supply, Vol. 1 -- 14--139404 RCB0 failure, Vol. 1 -- 14--142405 RCB1 failure, Vol. 1 -- 14--144406 RCB2 failure, Vol. 1 -- 14--146407 RCB3 failure , Vol. 1 -- 14--148408 Power supply fault to the fans of the MPU shelf, Vol. 1 -- 14--150411 Power supply fault of the other chains MPU shelf, Vol. 1 -- 14--153412 RCB4 failure, Vol. 1 -- 14--155413 Fault on the right MPU power supply, Vol. 1 -- 14--157414 Fan fault on EQPT and SWG shelf, Vol. 1 -- 14--159415 Power supply fault on SWG or SWT shelf, Vol. 1 -- 14--161417 Power supply fault on EQPT shelf, Vol. 1 -- 14--163419 Power supply fault on EQPI shelf, Vol. 1 -- 14--165420 Fan fault on the EQPI, EQPD0 and EQPD1 shelves, Vol. 1 -- 14--167422 Power supply fault to the fans of the equipment cabinet, Vol. 1 -- 14--169494 Fault on ECI alarm loop, Vol. 1 -- 14--171497 New PCM selected as clock reference, Vol. 1 -- 14--173520 Fault on switching matrix access, Vol. 1 -- 14--176521 Fault on switching matrix, Vol. 1 -- 14--180522 Switch supervision failure, Vol. 1 -- 14--182523 Fault on internal PCM, Vol. 1 -- 14--186524 Slave switch board not present, Vol. 1 -- 14--187
IndexNortel Networks Confidential Vol. 1 -- iii
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
601 File management error, Vol. 1 -- 14--189607 Multibus II error, Vol. 1 -- 14--193617 SCSI bus controller error, Vol. 1 -- 14--197632 File management error, Vol. 1 -- 14--199633 Disk driver error, Vol. 1 -- 14--203634 Mirror disk, Vol. 1 -- 14--205638 Multibus II error, Vol. 1 -- 14--207649 SCSI protocol error, Vol. 1 -- 14--211656 Ethernet controller chip error, Vol. 1 -- 14--213657 Ethernet controller chip error, Vol. 1 -- 14--2131074 Indication of non activated features on specific instances, Vol. 1 -- 14--2141150 Loss of DDTI configuration, Vol. 1 -- 14--2151151 PCM transmission fault, Vol. 1 -- 14--2161152 PCM CRC attribute and DDTI CRC strap are not consistent, Vol. 1 -- 14--2171153 Negative test on passive chain LAPD channel (layer 2), Vol. 1 -- 14--2201154 Negative test on passive chain CCS7 signalling link (layer 2), Vol. 1 -- 14--2221155 Fault on SLS card, Vol. 1 -- 14--2241164 OMC access failure, Vol. 1 -- 14--2261193 Clock alarm, Vol. 1 -- 14--2281201 Degraded active chain, Vol. 1 -- 14--2301211 Unknown TEI in a LAPD message received by the xSCB card, Vol. 1 -- 14--2321212 xSCB card internal fifo congestion, Vol. 1 -- 14--2331312 MSC inaccessible, Vol. 1 -- 14--2341315 Path information for calls released by TCU or BTS, Vol. 1 -- 14--2361366 Indication of the SSN LCS state, Vol. 1 -- 14--2391470 Impossibility of storage of a general permanent observation message, Vol. 1 -- 14--2401472 Purge realized to store a general permanent observation message, Vol. 1 -- 14--2421483 Impossibility of storage of non prioritary records, Vol. 1 -- 14--2431484 Impossibility of storage of files, Vol. 1 -- 14--2441486 Call path tracing activity state change, Vol. 1 -- 14--2451490 BSC overload, Vol. 1 -- 14--2461502 Access attempt to a non operational cell, Vol. 1 -- 14--247
BSC 12000 ”HC”5 Restart after chain suicide due to internal cause, or OMC, Vol. 1 -- 2--1Source (0) Software anomaly counter threshold, Vol. 1 -- 2--4Source (1) CPUE (MPU) non present, Vol. 1 -- 2--5Source (2) CPUE (MPU) or CPUM (OMU) built--in self test failed, Vol. 1 -- 2--7Source (3) CPUE (MPU) or CPUM (OMU) setup failed , Vol. 1 -- 2--9Source (4) Incorrect Multibus II card name, Vol. 1 -- 2--11Source (5) No communication with CPUE (MPU) card, Vol. 1 -- 2--13Source (8) Error in BSC state machine handler (GAUT), Vol. 1 -- 2--15Source (10) Error in switchover sequence, Vol. 1 -- 2--16Source (11) BDA KO during switchover sequence, Vol. 1 -- 2--17Source (12) Invalid mirror partitions after switchover on the new active chain, Vol. 1 -- 2--18Source (14) Loss of duplex link detected on passive chain, Vol. 1 -- 2--19Source (15) Inconsistency between active and passive chains, Vol. 1 -- 2--20Source (16) Context overflow for BSC (MDB) defense, Vol. 1 -- 2--21Source (20) Switching while passive chain DP loading, Vol. 1 -- 2--22Source (21) Error detected during check partition, Vol. 1 -- 2--23Source (23) CPUE BOOT flashing failed, Vol. 1 -- 2--24Source (24) Restart to take into account the new BSC customization, Vol. 1 -- 2--25
Index Nortel Networks ConfidentialVol. 1 -- iv
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
Source (25) Degraded disk, Vol. 1 -- 2--26Source (28) End of probative phase OK, Vol. 1 -- 2--29Source (29) New BDA edition, Vol. 1 -- 2--30Source (30) Preparation of a type 5 upgrade, Vol. 1 -- 2--31Source (31) Type 5 upgrade running, Vol. 1 -- 2--32Source (32) Old release running on passive chain, Vol. 1 -- 2--33Source (33) Unsuccessful preparation of a type 5 upgrade, Vol. 1 -- 2--34Source (50) BDA inconsistency, Vol. 1 -- 2--35Source (51) GES--MS / GES--SL are incoherent, Vol. 1 -- 2--37Source (52) Passive chain does not answer on RGA request, Vol. 1 -- 2--38Source (53) Passive chain suicide on RGA request, Vol. 1 -- 2--39Source (101) No communication with switching board, Vol. 1 -- 2--40Source (102) No communication with ECI card or fault on ECI card, Vol. 1 -- 2--42Source (103) No communication with SICX card or fault on SICX card, Vol. 1 -- 2--45Source (104) No communication with slave switching board, Vol. 1 -- 2--47Source (105) No communication with SLS card or fault on SLS card, Vol. 1 -- 2--49Source (106) Operator request, Vol. 1 -- 2--51Source (107) Degraded REM link, Vol. 1 -- 2--52Source (128) No communication with SICD or RCB card or fault on SICD or RCB card, Vol. 1 -- 2--53Source (129) SICD port selftests not OK, Vol. 1 -- 2--56Source (161) No communication with CCS7 card or fault on CCS7 card, Vol. 1 -- 2--58Source (162) CCS7 port selftests not OK, Vol. 1 -- 2--60Source (176) No communication with TCU card or fault on TCU card, Vol. 1 -- 2--62Source (192) O&M bus selftests not OK, Vol. 1 -- 2--65
6 Restart after chain suicide due to trap, Vol. 1 -- 2--677 Card monitoring failure, Vol. 1 -- 2--688 Negative built in self test result for card, Vol. 1 -- 2--7211 Restart after chain suicide due to NMI, Vol. 1 -- 2--7613 Chain restart in progress, Vol. 1 -- 2--7814 Indication of chain restart cause, Vol. 1 -- 2--7915 Chain restart due to intermediate card, Vol. 1 -- 2--8016 Fault on active/passive chains link, Vol. 1 -- 14--8320 Alarm on clockship of the SUP board, Vol. 1 -- 14--8621 Beginning of circular file pre--overflow, Vol. 1 -- 14--8722 End of circular file pre--overflow, Vol. 1 -- 14--8923 Beginning of BSC disk partition update, Vol. 1 -- 14--9024 End of BSC disk partition update, Vol. 1 -- 14--9126 Fault on BSC/OMC--R link, Vol. 1 -- 14--9233 Saturation on an internal file used for marking climb, Vol. 1 -- 14--9334 Saturation on a storage zone for marking climb, Vol. 1 -- 14--9441 Beginning of saturation of the event reporting process in the BSC, Vol. 1 -- 14--9542 End of saturation of the event reporting process, Vol. 1 -- 14--9943 Loss of access to the equipment shelf, Vol. 1 -- 14--100Source (0) Cannot access to all working UTE, Vol. 1 -- 14--101Source (1) O&M bus selftest not OK, Vol. 1 -- 14--103
44 Board UTE access problem, Vol. 1 -- 14--10545 Partial hard disk degradation, Vol. 1 -- 14--10946 Total hard disk degradation, Vol. 1 -- 14--11347 Cessation of active alarms, Vol. 1 -- 14--115332 External alarm loop 0, Vol. 1 -- 14--116333 External alarm loop 1, Vol. 1 -- 14--118334 External alarm loop 2, Vol. 1 -- 14--120
IndexNortel Networks Confidential Vol. 1 -- v
Fault Number DescriptionCopyright © 1999--2005 Nortel Networks
335 External alarm loop 3, Vol. 1 -- 14--122336 External alarm loop 4, Vol. 1 -- 14--124337 External alarm loop 5, Vol. 1 -- 14--126338 External alarm loop 6, Vol. 1 -- 14--128339 External alarm loop 7, Vol. 1 -- 14--130400 Breakdown of one power supply of the EQPD1 shelf, Vol. 1 -- 14--132401 Breakdown of one power supply of the EQPD0 shelf, Vol. 1 -- 14--134402 Fan fault on the MPU shelf, Vol. 1 -- 14--136403 Fan fault on the MPU shelfs power supply, Vol. 1 -- 14--139404 RCB0 failure, Vol. 1 -- 14--142405 RCB1 failure, Vol. 1 -- 14--144406 RCB2 failure, Vol. 1 -- 14--146407 RCB3 failure , Vol. 1 -- 14--148408 Power supply fault to the fans of the MPU shelf, Vol. 1 -- 14--150411 Power supply fault of the other chains MPU shelf, Vol. 1 -- 14--153412 RCB4 failure, Vol. 1 -- 14--155413 Fault on the right MPU power supply, Vol. 1 -- 14--157414 Fan fault on EQPT and SWG shelf, Vol. 1 -- 14--159415 Power supply fault on SWG or SWT shelf, Vol. 1 -- 14--161417 Power supply fault on EQPT shelf, Vol. 1 -- 14--163419 Power supply fault on EQPI shelf, Vol. 1 -- 14--165420 Fan fault on the EQPI, EQPD0 and EQPD1 shelves, Vol. 1 -- 14--167422 Power supply fault to the fans of the equipment cabinet, Vol. 1 -- 14--169494 Fault on ECI alarm loop, Vol. 1 -- 14--171497 New PCM selected as clock reference, Vol. 1 -- 14--173520 Fault on switching matrix access, Vol. 1 -- 14--178521 Fault on switching matrix, Vol. 1 -- 14--180522 Switch supervision failure, Vol. 1 -- 14--184523 Fault on internal PCM, Vol. 1 -- 14--186524 Slave switch board not present, Vol. 1 -- 14--187601 File management error, Vol. 1 -- 14--191607 Multibus II error, Vol. 1 -- 14--195617 SCSI bus controller error, Vol. 1 -- 14--197632 File management error, Vol. 1 -- 14--201633 Disk driver error, Vol. 1 -- 14--203634 Mirror disk, Vol. 1 -- 14--206638 Multibus II error, Vol. 1 -- 14--209649 SCSI protocol error, Vol. 1 -- 14--211656 Ethernet controller chip error, Vol. 1 -- 14--213657 Ethernet controller chip error, Vol. 1 -- 14--2131074 Indication of non activated features on specific instances, Vol. 1 -- 14--2141150 Loss of DDTI configuration, Vol. 1 -- 14--2151151 PCM transmission fault, Vol. 1 -- 14--2161152 PCM CRC attribute and DDTI CRC strap are not consistent, Vol. 1 -- 14--2171153 Negative test on passive chain LAPD channel (layer 2), Vol. 1 -- 14--2201154 Negative test on passive chain CCS7 signalling link (layer 2), Vol. 1 -- 14--2221155 Fault on SLS card, Vol. 1 -- 14--2251164 OMC access failure, Vol. 1 -- 14--2261193 Clock alarm, Vol. 1 -- 14--2281201 Degraded active chain, Vol. 1 -- 14--230
Index Nortel Networks ConfidentialVol. 1 -- vi
PE/DCL/DD/0101411--9001--101
Standard 15.101/EN July 2005 Copyright © 1999--2005 Nortel Networks
1211 Unknown TEI in a LAPD message received by the xSCB card, Vol. 1 -- 14--2321212 xSCB card internal fifo congestion, Vol. 1 -- 14--2331312 MSC inaccessible, Vol. 1 -- 14--2341315 Path information for calls released by TCU or BTS, Vol. 1 -- 14--2361470 Impossibility of storage of a general permanent observation message, Vol. 1 -- 14--2401472 Purge realized to store a general permanent observation message, Vol. 1 -- 14--2421483 Impossibility of storage of non prioritary records, Vol. 1 -- 14--2431484 Impossibility of storage of files, Vol. 1 -- 14--2441486 Call path tracing activity state change, Vol. 1 -- 14--2451490 BSC overload, Vol. 1 -- 14--2461503 Access Attempt to an unknown BCCH or BSIC, Vol. 1 -- 14--249
TTCU7 Card monitoring failure, Vol. 1 -- 3--18 Negative built in self test result for card, Vol. 1 -- 3--647 Cessation of active alarms, Vol. 1 -- 3--8493 Failure on one of the TCUs clocking sources, Vol. 1 -- 3--10497 New PCM selected as clock reference, Vol. 1 -- 3--13523 Fault on internal PCM (BSC, TCU), Vol. 1 -- 3--161150 Loss of DDTI configuration, Vol. 1 -- 3--171151 PCM transmission fault, Vol. 1 -- 3--181152 PCM CRC4 attribute and DDTI/TDTI CRC4 strap are not consistent, Vol. 1 -- 3--191156 TCU downloading failure, Vol. 1 -- 3--211157 Loss of TCU remote layer 2, Vol. 1 -- 3--221159 Invalid message received on TCU--BSC interface, Vol. 1 -- 3--231160 TCU negative acknowledgment indication, Vol. 1 -- 3--251163 Preemption of a terrestrial circuit by a signalling link, Vol. 1 -- 3--27, Vol. 1 -- 3--281165 VAL_STP_ANO_TRC_BLOCKED, Vol. 1 -- 3--281170 External alarm loop on TCU, Vol. 1 -- 3--291171 TCU power fault, Vol. 1 -- 3--311172 TCU fan board fault, Vol. 1 -- 3--341173 TCU fan fault, Vol. 1 -- 3--371174 TCU clock fault, Vol. 1 -- 3--411180 TCB downloading failure, Vol. 1 -- 3--441184 Internal TCB--2 failure, Vol. 1 -- 3--481185 TCB--2 synchronization failure, Vol. 1 -- 3--501186 External TCB--2 failure, Vol. 1 -- 3--521190 Restart after TCU suicide, Vol. 1 -- 3--541290 Unacknowledged message on a interface, Vol. 1 -- 3--561310 A interface protocol error indication, Vol. 1 -- 3--581311 Reset downlink, Vol. 1 -- 3--601363 SCCP protocol error indication, Vol. 1 -- 3--611364 MTP3 protocol error indication, Vol. 1 -- 3--63
Wireless Service Provider SolutionsFault Number Description
Copyright © 1999--2005 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of NortelNetworks. Except as specifically authorized in writing by NortelNetworks, the holder of this document shall keep the informationcontained herein confidential and shall protect same in whole or in partfrom 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, theinformation contained herein in any way or in any form without priorwritten consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTELNETWORKS, the NORTEL NETWORKS corporate logo, the NORTELGlobemark, UNIFIED NETWORKS, S2000, S4000, S8000.GSM is a trademark of France Telecom.All other brand and product names are trademarks or registredtrademarks of their respective holders.
Publication ReferencePE/DCL/DD/0101 411--9001--10115.101/ENJuly 2005Originated in France
For more information, please contact:
For all countries, except USA:
Documentation DepartmentParc d’activité de Magny--ChateaufortCHATEAUFORT78928 YVELINES CEDEX 9FRANCEEmail : [email protected] : (33) (1) 39--44--50--29
In the USA:
2221 Lakeside BoulevardRichardson TX 75082USATel: 1--800--4 NORTEL1--800--466--7838 or (972) 684--5935
Internet Address:
http://www.nortelnetworks.com