Moto68P02901W26 Alarm

Maintenance Information: Alarm
Handling at the OMC-R
68P02901W26-S Nov 2007
© 1994 - 2007 Motorola, Inc. All Rights Reserved

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Nov 2007
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Maintenance Information: Alarm Handling at the OMC-R

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1: Introduction to Alarm Handling

Manual introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Alarm types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Device alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Reconfiguration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Impact list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
OOS device list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Additional information field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
OMC-R map display modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Chapter 2: ABSS Alarms

0. ABSS: Last XBL link failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
1. ABSS: RXCDR detecting CIC validation failure . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2. ABSS: Circuit configuration problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Chapter 3: AXCDR Alarms

Introduction to AXCDR alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
0. AXCDR: BSC detecting CIC validation failure . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
0. AXCDR: Ater pre-emption failure statistic alarm - PM . . . . . . . . . . . . . . . . . . . . . 3-4
1. AXCDR: AXCDR ID mismatch with RXCDR network entity ID . . . . . . . . . . . . . . . . . 3-6
Chapter 4: BCUP Alarms

Introduction to BCUP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
0. BCUP: Unexpected board type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
1. BCUP: Serial bus connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
8. BCUP: Output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
9. BCUP: Input failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
68P02901W26-S i
Nov 2007
Contents
10. BCUP: Over temperature warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Chapter 5: BSP Alarms

Introduction to BSP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
1. BSP: EEPROM flash failure - No valid bootstrap code detected . . . . . . . . . . . . . . . . 5-4
8. BSP: EEPROM flash object failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
17. BSP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
20. BSP: LAPD controller failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
21. BSP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
22. BSP: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
30. BSP: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
31. BSP: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
32. BSP: TDM interface failure - Assigned timeslot counter underflow. . . . . . . . . . . . . . 5-20
33. BSP: TDM interface failure - Assigned timeslot counter overflow . . . . . . . . . . . . . . 5-22
34. BSP: TDM interface failure - TDM parity error . . . . . . . . . . . . . . . . . . . . . . . . 5-24
35. BSP: LAN connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
39. BSP: Software failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
40. BSP: Spurious interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
47. BSP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected . . . . . 5-32
48. BSP: Memory location fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
50. BSP: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 5-35
51. BSP: EEPROM HW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 5-36
52. BSP: BSP CPU Safe Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
53. BSP: BSP CPU critical overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
231. BSP: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
232. BSP: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
239. BSP: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
254. BSP: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Chapter 6: BSS Alarms

Introduction to BSS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
0. BSS: Last MTL link failure - Signaling point inaccessible . . . . . . . . . . . . . . . . . . . 6-4
0. BSS: Paging request from MSC protocol error - PM . . . . . . . . . . . . . . . . . . . . . . 6-7
1. BSS: Call processing failure - MSC detected SCCP down . . . . . . . . . . . . . . . . . . . 6-8
1. BSS: Routing failure - Syntax error detected - PM. . . . . . . . . . . . . . . . . . . . . . . 6-9
2. BSS: Call processing failure - MSC detected BSSAP down . . . . . . . . . . . . . . . . . . 6-10
2. BSS: Routing failure - Reason unknown - PM . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
3. BSS: Call processing failure - BSS detected BSSAP down . . . . . . . . . . . . . . . . . . . 6-13
5. BSS: No MSC acknowledgment for circuit block . . . . . . . . . . . . . . . . . . . . . . . 6-15
6. BSS: No MSC acknowledgment for circuit unblock . . . . . . . . . . . . . . . . . . . . . . 6-17
7. BSS: No MSC acknowledgment for reset circuit . . . . . . . . . . . . . . . . . . . . . . . 6-19
7. BSS: Mobile assignment request from MSC protocol error - PM . . . . . . . . . . . . . . . 6-21
8. BSS: Unequipped circuit at the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
9. BSS: No MSC acknowledgment for global reset . . . . . . . . . . . . . . . . . . . . . . . . 6-25
10. BSS: Erroneous layer 3 message received by the BSS . . . . . . . . . . . . . . . . . . . . 6-26
11. BSS: Confusion message received from the MSC . . . . . . . . . . . . . . . . . . . . . . 6-27
12. BSS: Unequipped circuit at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
17. BSS: Handover request from the MSC protocol error - PM . . . . . . . . . . . . . . . . . 6-30
18. BSS: Routing failure - Syntax error detected (SMLC) - PM. . . . . . . . . . . . . . . . . . 6-31
20. BSS: Paging request from SMLC protocol error- PM . . . . . . . . . . . . . . . . . . . . . 6-32
21. BSS: Trunk major threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
22. BSS: Trunk critical threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
23. BSS: Agent Buffer Space Overflow - Event Logs May Be Incomplete. . . . . . . . . . . . . 6-35
24. BSS: Agent Buffer Overflow - rlogin Session May Be Incomplete . . . . . . . . . . . . . . 6-36
26. BSS: Received page for invalid cell from MSC . . . . . . . . . . . . . . . . . . . . . . . . 6-38
39. BSS: Circuit fault detected on radio channel . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
ii 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
40. BSS: Circuit fault cleared on radio channel . . . . . . . . . . . . . . . . . . . . . . . . . 6-41

41. BSS: Circuit fault detected on Ater channel . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
42. BSS: Circuit fault cleared on Ater channel . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
43. BSS: Circuit fault detected on PCM circuit. . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
44. BSS: Circuit fault cleared on PCM circuit . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
45. BSS: Circuit fault detected on GPRS circuit . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
46. BSS: Circuit fault cleared on GPRS circuit . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
47. BSS: Circuit fault detected on PATH channel . . . . . . . . . . . . . . . . . . . . . . . . 6-55
48. BSS: Circuit fault cleared on PATH channel . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
49. BSS: Last LMTL link failure - Signaling point inaccessible . . . . . . . . . . . . . . . . . . 6-59
50. BSS: Call processing failure - SMLC detected SCCP down . . . . . . . . . . . . . . . . . . 6-62
51. BSS: Call processing failure - SMLC detected BSSAP down . . . . . . . . . . . . . . . . . 6-64
52. BSS: No SMLC acknowledgment for global reset . . . . . . . . . . . . . . . . . . . . . . 6-66
53. BSS: Erroneous layer 3 message received from SMLC . . . . . . . . . . . . . . . . . . . . 6-67
54. BSS: Confusion message received from the SMLC . . . . . . . . . . . . . . . . . . . . . . 6-68
55. BSS: Received page for invalid cell from SMLC . . . . . . . . . . . . . . . . . . . . . . . 6-69
59. BSS: Last PCU failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71
60. BSS: Circuit fault detected on GPRS circuit . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
61. BSS: Circuit fault cleared on GPRS circuit . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Chapter 7: BTP Alarms

Introduction to BTP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
1. BTP: EEPROM Flash failure - No valid bootstrap code object present . . . . . . . . . . . . . 7-4
8. BTP: EEPROM Flash object failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
17. BTP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
20. BTP: LAPD controller failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
21. BTP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
22. BTP: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
30. BTP: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
31. BTP: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
32. BTP: TDM interface failure - Assigned timeslot counter underflow. . . . . . . . . . . . . . 7-20
33. BTP: TDM interface failure - Assigned timeslot counter overflow . . . . . . . . . . . . . . 7-22
34. BTP: TDM interface failure - TDM parity error . . . . . . . . . . . . . . . . . . . . . . . . 7-24
35. BTP: LAN connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
39. BTP: Software failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
40. BTP: Spurious interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
42. BTP: Site reset occurred due to front panel reset . . . . . . . . . . . . . . . . . . . . . . 7-32
47. BTP: Unexpected board type: GPROC2 or GPROC3 expected . . . . . . . . . . . . . . . . 7-33
48. BTP: Memory location is corrupt. Replace GPROC board . . . . . . . . . . . . . . . . . . 7-35
50. BTP: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 7-36
51. BTP: EEPROM HW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 7-37
231. BTP: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
232. BTP: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
234. BTP: Active link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
235. BTP: Standby link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
236. BTP: Slow flash failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
237. BTP: Non-volatile memory failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
239. BTP: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
254. BTP: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Chapter 8: CAB Alarms

Introduction to CAB alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
25. CAB: External power booster amplifier 1 failure . . . . . . . . . . . . . . . . . . . . . . . 8-3
26. CAB: External power booster amplifier 2 failure . . . . . . . . . . . . . . . . . . . . . . . 8-5
27. CAB: External power booster failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
28. CAB: Database configuration and hardware mismatch . . . . . . . . . . . . . . . . . . . . 8-9
68P02901W26-S iii
Nov 2007
Contents
Chapter 9: CAGE Alarms

Introduction to CAGE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
20 - 25. CAGE: CLKX slot 2-7 communication failure . . . . . . . . . . . . . . . . . . . . . . 9-3
26 - 27. CAGE: LANX slot 19-20 communication failure . . . . . . . . . . . . . . . . . . . . . 9-6
28 - 30. CAGE: Power supply unit #1-3 - Output failure . . . . . . . . . . . . . . . . . . . . . 9-9
31 - 33. CAGE: Power supply unit #1-3 - Not detected . . . . . . . . . . . . . . . . . . . . . . 9-11
34 - 36 CAGE: Power supply unit #1-3 - Fan failure . . . . . . . . . . . . . . . . . . . . . . . 9-13
37 - 39. CAGE: Power supply unit #1-3 - Over temperature . . . . . . . . . . . . . . . . . . . 9-15
40. CAGE: Over temperature - Component damage imminent . . . . . . . . . . . . . . . . . . 9-17
41 - 42. CAGE: Local KSWX/DSWX slot 0-1 communication failure . . . . . . . . . . . . . . . 9-19
43 - 47. CAGE: Remote KSWX/DSWX slot 2-6 communication failure . . . . . . . . . . . . . . 9-22
48 - 52. CAGE: Remote KSWX/DSWX slot 24-28 communication failure . . . . . . . . . . . . . 9-25
53 - 55. CAGE: Expansion KSWX/DSWX slot 7- 9 communication failure. . . . . . . . . . . . . 9-28
56 - 58. CAGE: Expansion KSWX/DSWX slot 21-23 communication failure. . . . . . . . . . . . 9-31
59 - 76. CAGE: DSWX/KSWX mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Chapter 10: CBL Alarms

Introduction to CBL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
0. CBL: Invalid received frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
1. CBL: FRMR frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
2. CBL: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Chapter 11: CBUS Alarms

Introduction to CBUS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
0. CBUS: Over 50% of boards detected clock failure. . . . . . . . . . . . . . . . . . . . . . . 11-3
2. CBUS: Master CBUS signal provided by slave GCLK . . . . . . . . . . . . . . . . . . . . . 11-5
4. CBUS: Local KSWX/DSWX clock fiber failure . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Chapter 12: CELL Alarms

Introduction to CELL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
0. CELL: Flow control procedure has started barring normal calls from access classes 0-9 . . . 12-4
0. CELL: Radio frequency losses while using an SDCCH - PM . . . . . . . . . . . . . . . . . . 12-6
1. CELL: Cell radio timeslot capacity loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
1. CELL: Attempt at allocating an SDCCH failed - PM . . . . . . . . . . . . . . . . . . . . . . 12-9
2. CELL: Radio subsystem software error - Detected page overflow . . . . . . . . . . . . . . . 12-11
2. CELL: Channel request from MS blocked - PM . . . . . . . . . . . . . . . . . . . . . . . . 12-13
3. CELL: Last NS-VC failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
4. CELL: Classmark update from MS protocol error - PM . . . . . . . . . . . . . . . . . . . . 12-17
5. CELL: No cell (BVC) block acknowledgment from the SGSN . . . . . . . . . . . . . . . . . 12-19
6. CELL: Cipher mode Command from MSC failed - PM . . . . . . . . . . . . . . . . . . . . . 12-20
7. CELL: GPRS and baseband hopping configuration failure . . . . . . . . . . . . . . . . . . . 12-21
8. CELL: GPRS unavailable - No PRP available . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
9. CELL: GPRS unavailable - No GDS available . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
9. CELL: Intra-cell handover failed and recovered - PM . . . . . . . . . . . . . . . . . . . . . 12-25
10. CELL: GPRS unavailable - No cell (BVC) reset ack from the SGSN . . . . . . . . . . . . . 12-27
10. CELL: Intra-cell handover failed and mobile lost - PM . . . . . . . . . . . . . . . . . . . . 12-28
11. CELL: GPRS unavailable - No cell (BVC) unblock ack from the SGSN . . . . . . . . . . . . 12-30
11. CELL: Intra-BSS handover primary target cell blocked - PM . . . . . . . . . . . . . . . . . 12-31
12. CELL: GPRS unavailable - No PDCHs available . . . . . . . . . . . . . . . . . . . . . . . 12-32
13. CELL: GPRS unavailable - No GPRS capable carriers available . . . . . . . . . . . . . . . 12-33
13. CELL: Intra-BSS handover failed and recovered to org channel - PM . . . . . . . . . . . . 12-34
14. CELL: Intra-BSS handover failed and mobile lost - PM. . . . . . . . . . . . . . . . . . . . 12-36
14. CELL: GPRS unavailable - PBCCH timeslot out of sync . . . . . . . . . . . . . . . . . . . 12-38
15. CELL: EGPRS unavailable - No EGPRS carriers available . . . . . . . . . . . . . . . . . . 12-39
iv 68P02901W26-S
Nov 2007
15. CELL: Inter-BSS handover, MS handover failed message received PM. . . . . . . . . . . . 12-40
16. CELL: EGPRS unavailable - Insufficient GDS available. . . . . . . . . . . . . . . . . . . . 12-42
17. CELL: GPRS unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
18. CELL: Handover failure to the MSC due to all possible errors except no channels - PM . . . 12-45
18. CELL: EGPRS unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
19. CELL: EGPRS unavailable - No 64 K PDCHs available . . . . . . . . . . . . . . . . . . . . 12-48
19. CELL: Bad handover reference numbers from the MS - PM . . . . . . . . . . . . . . . . . 12-49
20. CELL: Number of calls queued - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
22. CELL: Mobile assign command to MS blocked (No channel available) - PM . . . . . . . . . 12-53
23. CELL: Mobile assignment failure from MS - PM . . . . . . . . . . . . . . . . . . . . . . . 12-55
24. CELL: PCH queue page discard - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
25. CELL: Attempt at allocating a TCH failed - PM . . . . . . . . . . . . . . . . . . . . . . . 12-59
28. CELL: TCH pre-emption failure - PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
Chapter 13: COMB Alarms

Introduction to COMB alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
0 - 4. COMB: Cavity 0 - 4 tuning error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
5. COMB: Link A sanity failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
6. COMB: Link B sanity failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
7. COMB: Power feed A failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
8. COMB: Power feed B failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
9. COMB: Full reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
10. COMB: Partial reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
11. COMB: Cavity 5 tuning error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
12. COMB: Cavity combining block 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
13. COMB: Cavity combining block 1 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
14. COMB: Processor A failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27
15. COMB: Processor B failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
254. COMB: Device failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
Chapter 14: CSFP Alarms

Introduction to CSFP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
22. CSFP: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
35. CSFP: LAN connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
47. CSFP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected. . . . . 14-6
48. CSFP: Memory location is corrupt. Replace GPROC board . . . . . . . . . . . . . . . . . 14-8
49. CSFP: Code objects unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
50. CSFP: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . 14-11
51. CSFP: EEPROM HW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . 14-12
240. CSFP: PCMCIA card removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Chapter 15: DHP Alarms

Introduction to DHP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
1. DHP: EEPROM flash failure - No valid bootstrap code object present . . . . . . . . . . . . . 15-4
8. DHP: EEPROM flash object failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
17. DHP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
21. DHP: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
22. DHP: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
23. DHP: SYNC lost phase lock to master GCLK . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
24. DHP: Bad clock source or SYNC OCXO (oscillator) replacement required . . . . . . . . . . 15-15
25. DHP: SYNC warm up failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17
26. DHP: SYNC calibration request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
27. DHP: SYNC shutdown request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21
28. DHP: SYNC clock output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23
29. DHP: SYNC watchdog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-25
68P02901W26-S v
Nov 2007
Contents
30. DHP: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-27

31. DHP: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-29
32. DHP: TDM interface failure - Assigned timeslot counter underflow . . . . . . . . . . . . . 15-31
33. DHP: TDM interface failure - Assigned timeslot counter overflow . . . . . . . . . . . . . . 15-33
34. DHP: TDM interface failure - TDM parity error . . . . . . . . . . . . . . . . . . . . . . . 15-35
35. DHP: LAN connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-37
39. DHP: Software failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-39
40. DHP: Spurious interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-41
43. DHP: SYNC not operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-43
44. DHP: Firmware initiated SYNC calibration. . . . . . . . . . . . . . . . . . . . . . . . . . 15-45
45. DHP: SYNC phase lock failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-46
46. DHP: SYNC invalid mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-48
47. DHP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected . . . . . 15-50
48. DHP: Memory location is corrupt. Replace GPROC board . . . . . . . . . . . . . . . . . . 15-52
50. DHP: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 15-53
51. DHP: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 15-54
231. DHP: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . 15-55
232. DHP: Processor bus communication failure. . . . . . . . . . . . . . . . . . . . . . . . . 15-57
234. DHP: Active link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-58
239. DHP: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-61
254. DHP: Device failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-63
Chapter 16: DPROC Alarms

Introduction to DPROC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
0. DPROC: Processor communication failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
9. DPROC: DPROC reset detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
22. DPROC: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
39. DPROC: Software failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
88. DPROC: Max temperature exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
92. DPROC: High temperature exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
239. DPROC: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Chapter 17: DRI Alarms

Introduction to DRI alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
2. DRI: Internal message error - Pointer misalignment . . . . . . . . . . . . . . . . . . . . . 17-10
3. DRI: Internal message error - Dual-port RAM segment full . . . . . . . . . . . . . . . . . . 17-13
5. DRI: Superframe counter error (Uplink) . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
6. DRI: Superframe counter error (Downlink) . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
9. DRI: Channel coder internal message error . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
10. DRI: Dual-port RAM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
13. DRI: Channel coder internal message error . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
15. DRI: Initial synchronization of radio and GPRS channel failed . . . . . . . . . . . . . . . . 17-30
18. DRI: Primary message or hardware interrupt error . . . . . . . . . . . . . . . . . . . . . 17-36
21. DRI: Calibration in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-42
22. DRI: Radio subsystem software to DRI communication error . . . . . . . . . . . . . . . . 17-43
23. DRI: Radio subsystem software to DRI communication failure . . . . . . . . . . . . . . . . 17-45
24. DRI: TDM interface failure - TDM parity error . . . . . . . . . . . . . . . . . . . . . . . . 17-47
25. DRI: TDM interface failure - Assigned timeslot counter overflow . . . . . . . . . . . . . . 17-49
26. DRI: TDM interface failure - Assigned timeslot counter underflow . . . . . . . . . . . . . . 17-51
27. DRI: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
28. DRI: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
vi 68P02901W26-S
Nov 2007
29. DRI: Processor failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57

30. DRI: Transceiver re-initialized unexpectedly . . . . . . . . . . . . . . . . . . . . . . . . . 17-59
31. DRI: Critical resource exhausted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
32. DRI: RF unit primary sync signal lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63
33. DRI: RF unit HDSL link quality error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-64
34. DRI: RF unit reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65
35. DRI: Reset due to recurring fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-67
36. DRI: Front end processor to radio subsystem software communication failure . . . . . . . 17-69
37. DRI: Hard reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
38. DRI: BSS internal alarm only - FWFM displayed at EMON . . . . . . . . . . . . . . . . . . 17-72
39. DRI: Synchronization loss with MCU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-73
40 - 47. DRI: Channel coder timeslot (0-7) failure . . . . . . . . . . . . . . . . . . . . . . . . 17-76
48. DRI: Baseband hopping timeslot counter mismatch . . . . . . . . . . . . . . . . . . . . . 17-78
49. DRI: GSM timeslot counter mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80
50. DRI: Spurious GSM timeslot interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-82
51. DRI: Baseband hopping TDM link error . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-84
52. DRI: Baseband hopping GSM timeslot misalignment. . . . . . . . . . . . . . . . . . . . . 17-86
53. DRI: Channel coder 0 failure - Demodulation processor 0 failure . . . . . . . . . . . . . . 17-89
54. DRI: Channel coder 0 Failure - Demodulation processor 1 failure . . . . . . . . . . . . . . 17-91
57. DRI: Transceiver to DRI communication error . . . . . . . . . . . . . . . . . . . . . . . . 17-97
59. DRI: Transceiver to DRI burst error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-101
60. DRI: Transceiver to DRI burst error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-103
64. DRI: Non recoverable error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-111
65. DRI: Radio subsystem software to DRI communication error - Checksum error . . . . . . . 17-113
66. DRI: Superframe counter error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-116
67. DRI: Radio subsystem software to DRI communication error - DRI not responding . . . . . 17-119
70. DRI: Equalizer control processor failure - Watchdog timer expired . . . . . . . . . . . . . 17-121
71. DRI: Unexpected communications bus interrupt . . . . . . . . . . . . . . . . . . . . . . . 17-123
72. DRI: Receiver failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-125
73. DRI: High reverse power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-127
74. DRI: Cell transmit power unachievable . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-129
76. DRI: Radio subsystem software to DRI communication error . . . . . . . . . . . . . . . . 17-132
78. DRI: TX VSWR antenna fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-134
80. DRI: Transmitter synthesizer failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-135
85. DRI: Transmitter failure - Output power . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-147
88. DRI: Power amplifier temperature high . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-153
89. DRI: Power amplifier communication failure . . . . . . . . . . . . . . . . . . . . . . . . . 17-156
91. DRI: Power amplifier power low but functioning . . . . . . . . . . . . . . . . . . . . . . . 17-160
92. DRI: Power amplifier temperature high but functioning . . . . . . . . . . . . . . . . . . . 17-162
104 - 111. DRI: Timeslot 0-7 configuration failure . . . . . . . . . . . . . . . . . . . . . . . . 17-166
112. DRI: Receiver synthesizer failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-168
68P02901W26-S vii
Nov 2007
Contents

119. DRI: Receiver failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-182
144. DRI: Transceiver to DRI communication failure . . . . . . . . . . . . . . . . . . . . . . 17-202
150. DRI: Receive matrix failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-213
151. DRI: Transceiver to combiner communication failure. . . . . . . . . . . . . . . . . . . . 17-215
152. DRI: Control processor to power amplifier communication failure . . . . . . . . . . . . . 17-217
153. DRI: Control processor to equalizer communication failure. . . . . . . . . . . . . . . . . 17-219
154. DRI: Power supply failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-221
155. DRI: Transceiver to DRI communication error . . . . . . . . . . . . . . . . . . . . . . . 17-223
156. DRI: Control processor message queue overflowed . . . . . . . . . . . . . . . . . . . . . 17-225
157. DRI: Receiver input overflowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-227
158. DRI: Receiver input overflowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-229
159. DRI: Equalizer output overflowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-231
160. DRI: Equalizer output overflowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-233
161. DRI: Transmitter out of synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . 17-235
162. DRI: Receive matrix branch 2 control link failure. . . . . . . . . . . . . . . . . . . . . . 17-237
166. DRI: Control processor firmware failure . . . . . . . . . . . . . . . . . . . . . . . . . . 17-245
167. DRI: Control processor configuration mismatch . . . . . . . . . . . . . . . . . . . . . . 17-247
168. DRI: Equalizer configuration mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-249
170. DRI: M-Cell micro interconnect failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-253
171. DRI: Invalid calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-255
176. DRI: Equalizer timeslot (0-7) failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-257
184. DRI: Equalizer firmware failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-259
192. DRI: Baseband hopping TDM link error . . . . . . . . . . . . . . . . . . . . . . . . . . 17-261
193. DRI: Baseband hopping GSM timeslot misalignment . . . . . . . . . . . . . . . . . . . . 17-263
203. DRI: RF unit power supply unit - Input failure . . . . . . . . . . . . . . . . . . . . . . . 17-265
204. DRI: RF unit over temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-266
205. DRI: RF unit low voltage disconnect imminent . . . . . . . . . . . . . . . . . . . . . . . 17-267
206. DRI: RF unit external alarm input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-268
207. DRI: Internal communication error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-269
208. DRI: Power amplifier temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-270
210. DRI: Hopping DRI failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-272
211. DRI: Front end processor failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-274
212. DRI: Channel coder failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-276
213. DRI: Transceiver processor failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-278
214. DRI: Equalizer failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-280
215. DRI: Power amplifier failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-282
216. DRI: Transceiver recovery failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-284
217. DRI: Transmission suspended to conserve battery power. . . . . . . . . . . . . . . . . . 17-286
viii 68P02901W26-S
Nov 2007
218. DRI: Invalid transceiver calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . 17-288

219. DRI: GPRS not supported by radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-290
221. DRI: Invalid in-call modification of destination channel type . . . . . . . . . . . . . . . . 17-291
224. DRI: Safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-293
231. DRI: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . 17-296
234. DRI: Active link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-298
235. DRI: Standby link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-301
236. DRI: Slow flash failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-303
237. DRI: Non-volatile memory failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-305
239. DRI: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-307
241. DRI: Standby link connected to wrong device . . . . . . . . . . . . . . . . . . . . . . . 17-310
243. DRI: Unlocked device not in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-313
254. DRI: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-315
Chapter 18: EAS Alarms

Introduction to EAS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
0. EAS: Unexpected board type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
1. EAS: Serial bus connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
8. EAS: EAS has detected main power failure . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
16 - 31. EAS: Optocoupler 1-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Chapter 19: ETH Alarms

0. ETH: Ethernet Link Disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
1. ETH: Excessive PSI_TRAU FILL FRAME TX . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
2. ETH: Excessive ETH RX ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
3. ETH: Excessive ETH TX ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
4. ETH: Unsupported Auto-Negotiated Signaling Rate . . . . . . . . . . . . . . . . . . . . . 19-7
5. ETH: DSW/DSWX Switching Hardware Required . . . . . . . . . . . . . . . . . . . . . . . 19-9
Chapter 20: GBL Alarms

Introduction to GBL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
0. GBL: Link disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
1. GBL: NSVC failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Chapter 21: GCLK Alarms

Introduction to GCLK alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
0. GCLK: Reference distribution module failure . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
2. GCLK: Clock reference failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
3. GCLK: Hardware Fault Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
4. GCLK: Phase lock lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
5. GCLK: 125 µs reference count overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
6. GCLK: 60 ms reference count overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15
7. GCLK: 6.12 seconds reference count overflow . . . . . . . . . . . . . . . . . . . . . . . . 21-17
8. GCLK: Frequency difference in mate GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19
9. GCLK: Hard reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-22
11. GCLK: Long term average values are unstable. . . . . . . . . . . . . . . . . . . . . . . . 21-25
12. GCLK: Unrecognized hardware revision level . . . . . . . . . . . . . . . . . . . . . . . . 21-27
14. GCLK: Phase lock failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-28
15. GCLK: Watchdog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-32
16. GCLK: Clock output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-34
17. GCLK: SYNC shutdown request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-36
18. GCLK: Not operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-38
19. GCLK: Warm up failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-40
20. GCLK: Invalid mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-42
68P02901W26-S ix
Nov 2007
Contents
21. GCLK: Calibration in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-44

22. GCLK: Firmware initiated calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-45
24. GCLK: Bad clock source or OCXO (oscillator) replacement required . . . . . . . . . . . . . 21-46
26. GCLK: GCLK calibration request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-49
232. GCLK: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . . 21-52
Chapter 22: GDS Alarms

0. GDS: All channels Out of Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
1. GDS: IP address mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
2. GDS: Protocol failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Chapter 23: GPROC Alarms

Introduction to GPROC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
1. GPROC: EEPROM flash failure - No valid bootstrap code object present . . . . . . . . . . . 23-4
8. GPROC: EEPROM flash object failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
17. GPROC: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 23-8
19. GPROC: RSL links congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10
20. GPROC: LAPD controller failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
21. GPROC: EEPROM flash programming failure . . . . . . . . . . . . . . . . . . . . . . . . 23-12
22. GPROC: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14
23. GPROC: SYNC lost phase lock to master GCLK . . . . . . . . . . . . . . . . . . . . . . . 23-15
24. GPROC: Bad clock source or SYNC OCXO(oscillator) replacement required . . . . . . . . . 23-16
25. GPROC: SYNC warm up failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-17
26. GPROC: SYNC calibration request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
27. GPROC: SYNC shutdown request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-19
28. GPROC: SYNC clock output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20
29. GPROC: SYNC watchdog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21
30. GPROC: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-22
31. GPROC: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-24
32. GPROC: TDM interface failure - Assigned timeslot counter underflow . . . . . . . . . . . . 23-26
33. GPROC: TDM interface failure - Assigned timeslot counter overflow. . . . . . . . . . . . . 23-28
34. GPROC: TDM interface failure - TDM parity error . . . . . . . . . . . . . . . . . . . . . . 23-30
35. GPROC: LAN connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-32
39. GPROC: Software failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-34
40. GPROC: Spurious interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-36
42. GPROC: Site reset occurred due to front panel reset . . . . . . . . . . . . . . . . . . . . 23-38
43. GPROC: SYNC not operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-39
44. GPROC: Firmware initiated SYNC calibration . . . . . . . . . . . . . . . . . . . . . . . . 23-40
45. GPROC: SYNC phase lock failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-41
46. GPROC: SYNC invalid mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-42
47. GPROC: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected . . . 23-43
48. GPROC: Memory location is corrupt. Replace GPROC board . . . . . . . . . . . . . . . . 23-45
50. GPROC: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . 23-46
51. GPROC: EEPROM SW flash programming failure . . . . . . . . . . . . . . . . . . . . . . 23-47
231. GPROC: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . 23-48
232. GPROC: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . 23-50
239. GPROC: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
254. GPROC: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-53
Chapter 24: GSL Alarms

Introduction to GSL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
0. GSL: Invalid received frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
1. GSL: FRMR frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
2. GSL: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
10. GSL: Link disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
x 68P02901W26-S
Nov 2007
11. GSL: LAPD protocol error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-13

13. GSL: LAPD protocol error threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . 24-15
15. GSL: Too many LAPD protocol errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-17
Chapter 25: IAS Alarms

Introduction to IAS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
0. IAS: Unexpected board type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5
1. IAS: Serial bus connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-7
8. IAS: Power supply unit 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-10
9. IAS: Power supply unit 1 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
10. IAS: Power supply unit 2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14
11. IAS: Power supply unit 3 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-16
13 – 15. IAS: Preselector 1A-3A fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-18
16. IAS: Matrix control main fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-20
17. IAS: Matrix control redundant fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . 25-22
18. IAS: Internal combiner main fuse failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 25-24
19. IAS: Internal combiner redundant fuse failure . . . . . . . . . . . . . . . . . . . . . . . . 25-26
20. IAS: External combiner main fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . 25-28
21. IAS: External combiner redundant fuse failure . . . . . . . . . . . . . . . . . . . . . . . 25-30
22. IAS: Multicoupler main fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-32
23. IAS: Multicoupler redundant fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . 25-34
24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure . . . . . . . . . . . . . . . . . . . . . . 25-36
27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure . . . . . . . . . . . . . . . . . . . . . . 25-38
30. IAS: Spare fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-40
31. IAS: DRAM battery backup fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-42
32. IAS: IAS +27 V power fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-44
33 - 34. IAS: Battery backup fuse #1 - #2 failure . . . . . . . . . . . . . . . . . . . . . . . . 25-46
35 - 37. IAS: Lower cage fan #0 - #2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-48
38 - 40. IAS: Upper cage fan #3 - #5 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-50
41. IAS: Multicoupler failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-52
46. IAS: Converter failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-54
47. IAS: Converter over temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-56
48 - 50. IAS: Preselector 1B-3B fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-59
51. IAS: Duplexer voltage error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-61
59. IAS: Battery backup output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-63
60. IAS: Battery backup input failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-65
61. IAS: RCU #5 circuit breaker failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-67
62. IAS: DPSM 1 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-69
63. IAS: DPSM 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-71
64 - 65. IAS: Fan power converter 1-2 failure . . . . . . . . . . . . . . . . . . . . . . . . . . 25-73
66 - 70. IAS: RCU #0 - #4 circuit breaker failure . . . . . . . . . . . . . . . . . . . . . . . . 25-75
71 - 74. IAS: Converter #1 - #4 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-77
75. IAS: IAS +27 V DAB power fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-79
80. IAS: Power supply unit - Input failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-81
81. IAS: Power supply unit - Output failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-83
82. IAS: BTS cabinet over temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-85
83. IAS: Low voltage disconnect imminent. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-87
84. IAS: Air conditioning unit failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-89
85. IAS: Heat management system unit failure . . . . . . . . . . . . . . . . . . . . . . . . . 25-91
86. IAS: Cabinet fan failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-93
87. IAS: Ancillary cabinet over temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-95
88 - 90. IAS: Voltage standing wave ratio sector 1-3 failure . . . . . . . . . . . . . . . . . . . 25-97
91. IAS: Voltage standing wave ratio performance low. . . . . . . . . . . . . . . . . . . . . . 25-99
92. IAS: Smoke alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-101
93. IAS: Door open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-103
94. IAS: No connection to alarms board - Connection broken . . . . . . . . . . . . . . . . . . 25-105
95. IAS: Low noise amplifier fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-107
68P02901W26-S xi
Nov 2007
Contents
96. IAS: No redundant connection to alarms board - Connection broken . . . . . . . . . . . . 25-109

97. IAS: No connection to alarm board - Radio OOS . . . . . . . . . . . . . . . . . . . . . . . 25-111
98. IAS: No redundant connection to alarms board - Radio OOS . . . . . . . . . . . . . . . . . 25-113
99. IAS: No connection to alarm board - Alarm board removed . . . . . . . . . . . . . . . . . 25-115
100. IAS: Cabinet protection system failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-117
101. IAS: Power supply temperature high . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-119
102. IAS: Mains ac supply failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-121
103. IAS: Fan tray 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-123
106. IAS: Rectifier failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-129
107. IAS: Battery box temperature high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-131
108. IAS: Alarm board failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-133
109. IAS: Auxiliary alarm 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-135
110. IAS: Urgent critical alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-136
111. IAS: Cabinet protection board fuse failure . . . . . . . . . . . . . . . . . . . . . . . . . 25-137
112 - 113. IAS: Heat management system unit failure 1 and 2 . . . . . . . . . . . . . . . . . . 25-139
114 - 115. IAS: Mains ac supply failure 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . 25-141
116 - 117. IAS: Rectifier failure 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-143
Chapter 26: KSW Alarms

Introduction to KSW alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
0. KSW: Parity highway 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-4
4. KSW: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14
5. KSW: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-19
6. KSW: 6.12 seconds reference loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-24
7. KSW: Re-initialized unexpectedly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-27
8. KSW: Hard reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-30
9. KSW: Watchdog timer expired. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-33
10. KSW: Lost communication with KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-36
11 KSW: Local cage KSW TDM loopback test failure . . . . . . . . . . . . . . . . . . . . . . . 26-41
18 - 21. KSW: Failure of expanded inbound TDM highway . . . . . . . . . . . . . . . . . . . . 26-45
22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure . . . . . . . . . 26-48
25 - 27. KSW: KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure . . . . . . . . 26-51
224. KSW: Safe test audit failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-54
225. KSW: Internal loopback audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-57
232. KSW: Processor bus communication failure. . . . . . . . . . . . . . . . . . . . . . . . . 26-60
254. KSW: Device failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-63
Chapter 27: LAN Alarms

Introduction to LAN alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2
0. LAN: Lan 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3
1. LAN: LAN failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-5
Chapter 28: LMTL Alarms

Introduction to LMTL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-2
0. LMTL: Signaling link failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-3
0. LMTL: SL failure - All reasons - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-6
1. LMTL: SMLC processor outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-8
1. LMTL: Threshold reached: SL failure - abnormal FIBR/BSNR - PM . . . . . . . . . . . . . . 28-10
2. LMTL: Threshold reached: SL failure - excessive delay of ACK - PM . . . . . . . . . . . . . 28-12
3. LMTL: Link traffic too high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-14
xii 68P02901W26-S
Nov 2007
3. LMTL: Threshold reached: SL failure - excessive error rate - PM . . . . . . . . . . . . . . . 28-16

4. LMTL: Threshold reached: SL failure - excessive duration of congestion - PM . . . . . . . . 28-18
5. LMTL: Threshold reached: SL alignment failure - PM . . . . . . . . . . . . . . . . . . . . . 28-20
6. LMTL: Threshold reached: Number of signal units in error - PM . . . . . . . . . . . . . . . 28-22
7. LMTL: Threshold reached: SL number of negative ACKs received - PM. . . . . . . . . . . . 28-24
8. LMTL: Threshold reached: Start of remote processor outage - PM . . . . . . . . . . . . . . 28-26
9. LMTL: Threshold reached: Number of octets retransmitted - PM . . . . . . . . . . . . . . . 28-28
10. LMTL: Threshold reached: MSUs discarded due to SL congestion - PM . . . . . . . . . . . 28-29
11. LMTL: SL congestion events resulting in loss of MSUs - PM . . . . . . . . . . . . . . . . . 28-30
12. LMTL: Threshold reached: SL congestion indications - PM . . . . . . . . . . . . . . . . . 28-32
Chapter 29: MMS Alarms

Introduction to MMS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3
0. MMS: Synchronization loss daily threshold exceeded . . . . . . . . . . . . . . . . . . . . . 29-5
1. MMS: Synchronization loss hourly threshold exceeded . . . . . . . . . . . . . . . . . . . . 29-7
2. MMS: Synchronization loss OOS threshold exceeded . . . . . . . . . . . . . . . . . . . . . 29-9
4. MMS: Remote alarm daily threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . 29-12
5. MMS: Remote alarm hourly threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . 29-14
6. MMS: Remote alarm OOS threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . 29-16
8. MMS: Frame slip daily threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . 29-19
9. MMS: Frame slip hourly threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . 29-21
10. MMS: Frame slip OOS threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . 29-23
12. MMS: Bit error daily threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . 29-24
13. MMS: Bit error hourly threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . 29-26
14. MMS: Bit error OOS threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . 29-28
16. MMS: Synchronization loss OOS timer expired . . . . . . . . . . . . . . . . . . . . . . . 29-31
18. MMS: Remote alarm OOS timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-34
20. MMS: Red alarm daily threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . 29-37
21. MMS: Red alarm hourly threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . 29-39
22. MMS: Red alarm OOS threshold exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . 29-41
23. MMS: Red alarm OOS timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-44
24. MMS: Modem to NIU serial channel control link failure . . . . . . . . . . . . . . . . . . . 29-47
25. MMS: HDSL modem loop 0 sync loss timer expired . . . . . . . . . . . . . . . . . . . . . 29-49
26. MMS: HDSL modem loop 1 sync loss timer expired . . . . . . . . . . . . . . . . . . . . . 29-53
27. MMS: Master HDSL modem loop 0 SNR daily threshold exceeded . . . . . . . . . . . . . 29-56
28. MMS: Master HDSL modem loop 1 SNR daily threshold exceeded . . . . . . . . . . . . . 29-58
29. MMS: Slave HDSL modem loop 0 SNR daily threshold exceeded . . . . . . . . . . . . . . 29-60
30. MMS: Slave HDSL modem loop 1 SNR daily threshold exceeded . . . . . . . . . . . . . . 29-62
31. MMS: Master HDSL modem loop 0 SNR hourly threshold exceeded . . . . . . . . . . . . . 29-64
32. MMS: Master HDSL modem loop 1 SNR hourly threshold exceeded . . . . . . . . . . . . . 29-66
33. MMS: Slave HDSL modem loop 0 SNR hourly threshold exceeded . . . . . . . . . . . . . 29-68
34. MMS: Slave HDSL modem loop 1 SNR hourly threshold exceeded . . . . . . . . . . . . . 29-70
35. MMS: Master HDSL modem loop 0 SNR OOS threshold exceeded. . . . . . . . . . . . . . 29-72
36. MMS: Master HDSL modem loop 1 SNR OOS threshold exceeded. . . . . . . . . . . . . . 29-76
37. MMS: Slave HDSL modem loop 0 SNR OOS threshold exceeded . . . . . . . . . . . . . . 29-80
38. MMS: Slave HDSL modem loop 1 SNR OOS threshold exceeded . . . . . . . . . . . . . . 29-84
39. MMS: LTU download failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-88
40. MMS: LTU configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-90
41. MMS: Connectivity mismatch between BSC and the RXCDR. . . . . . . . . . . . . . . . . 29-91
42. MMS: DSW/DSWX switching hardware required, BSC is now operating in Single Rate
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-93
253. MMS: Critical alarm threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . 29-94
Chapter 30: MSI Alarms

Introduction to MSI alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-2
0. MSI: Re-initialized unexpectedly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-3
68P02901W26-S xiii
Nov 2007
Contents
1. MSI: Hard reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-5

2. MSI: Watchdog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-7
3. MSI: Clock B signal loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-9
4. MSI: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-11
5. MSI: Assigned timeslot counter underflow . . . . . . . . . . . . . . . . . . . . . . . . . . 30-13
6. MSI: Assigned timeslot counter overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-15
7. MSI: TDM parity error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-17
9. MSI: TRAU frame synchronization loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-19
11 - 70. MSI: DSP channel (0-59) audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . 30-21
224. MSI: Safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-24
231. MSI: TDM interface configuration failure. . . . . . . . . . . . . . . . . . . . . . . . . . 30-26
232. MSI: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . . . 30-28
234. MSI: Active link connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-30
254. MSI: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-32
Chapter 31: MTL Alarms

Introduction to MTL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-2
0. MTL: Signaling link failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-3
0. MTL: SL failure - All reasons - PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-7
1. MTL: MSC processor outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-8
1. MTL: SL failure - Abnormal FIBR/BSNR - PM . . . . . . . . . . . . . . . . . . . . . . . . . 31-9
2. MTL: SL failure - Excessive delay of ACK - PM . . . . . . . . . . . . . . . . . . . . . . . . 31-10
3. MTL: Link traffic too high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-11
3. MTL: SL failure - Excessive error rate - PM . . . . . . . . . . . . . . . . . . . . . . . . . . 31-13
4. MTL: SL failure - Excessive duration of congestion - PM . . . . . . . . . . . . . . . . . . . 31-14
5. MTL: SL alignment failure - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-15
6. MTL: Number of signal units in error - PM . . . . . . . . . . . . . . . . . . . . . . . . . . 31-17
7. MTL: SL number of negative ACKS received - PM. . . . . . . . . . . . . . . . . . . . . . . 31-18
8. MTL: Start of remote processor outage - PM . . . . . . . . . . . . . . . . . . . . . . . . . 31-20
9. MTL: Number of octets retransmitted - PM . . . . . . . . . . . . . . . . . . . . . . . . . . 31-21
10. MTL: MSUs discarded due to SL congestion - PM . . . . . . . . . . . . . . . . . . . . . . 31-22
11. MTL: SL congestion events resulting in loss of MSUs - PM . . . . . . . . . . . . . . . . . 31-23
12. MTL: SL congestion indications - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-24
13. MTL: SL failure - Excessive error rate on HSP MTL - PM . . . . . . . . . . . . . . . . . . 31-25
Chapter 32: OMC-R Alarms

Introduction to OMC-R alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-4
30000. OMC: Download failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-5
30001. OMC: Upload failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-8
30002. OMC: File transfer failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-11
30003. OMC: X 25 circuit down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-14
30004. OMC: Parser disconnected too long . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-17
30005. OMC: NE response timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-20
30006. OMC: NE error state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-23
30007. OMC: PM disconnected from DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-26
30008. OMC: EM disconnected from DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-28
30009. OMC: DB compression failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-31
30010. OMC: Exceeds upper limit disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . 32-33
30011. OMC: Exceeds lower limit disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . 32-36
30012. OMC: Level 1/2/3 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-38
30014. OMC: Database exceeds upper limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-40
30015. OMC: PM proxy disconnected from DB . . . . . . . . . . . . . . . . . . . . . . . . . 32-42
30016. OMC: OSI stack error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-43
30017. OMC: CSFP download failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-44
30018. OMC: DB uncompression failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-47
30019. OMC: Database exceeds lower limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-49
xiv 68P02901W26-S
Nov 2007
30020. OMC: Version query failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-51

30021. OMC: OMC overloaded with events . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-57
30022. OMC: Events discarded due to OMC overloading . . . . . . . . . . . . . . . . . . . . 32-59
30023. OMC: Download disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-61
30024. OMC: CSFP swap failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-63
30025. OMC: NMC agent error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-64
30026. OMC: Neighbor statistics table exceeded the configured size . . . . . . . . . . . . . . 32-67
30027. OMC: Supplemental download failed. . . . . . . . . . . . . . . . . . . . . . . . . . . 32-69
30029. OMC: Active alarms exceed upper limit of 95% . . . . . . . . . . . . . . . . . . . . . 32-72
30030. OMC: Received maximum corrupt NE messages, closed OML . . . . . . . . . . . . . . 32-74
30031. OMC: Resync timed out, no response from NE . . . . . . . . . . . . . . . . . . . . . . 32-78
30032. OMC: Resync timed out, all resync events not received . . . . . . . . . . . . . . . . . 32-81
30033. OMC: Cannot create further event logfiles in /usr/gsm/ne_data . . . . . . . . . . . . . 32-83
30035. OMC: Advisory detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-86
30036. OMC: Recovered outage detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-87
30037. OMC: UPS condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-88
30038. OMC: OMC capacity ceiling violation, too many RTFs in MIB . . . . . . . . . . . . . . 32-89
30039. OMC: OMC capacity ceiling violation, too many NEs in MIB . . . . . . . . . . . . . . . 32-91
30050. OMC: Solaris 2 hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-93
30051. OMC: Corrupt NE file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-96
30052. OMC: Corrupt SITE file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-97
30058. OMC: Call success rate below threshold . . . . . . . . . . . . . . . . . . . . . . . . . 32-98
30059. OMC: No calls on cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-100
30060. OMC: No activity in timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-101
30061. OMC: CPU load exceeds lower limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-102
30062. OMC: CPU load exceeds upper limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-103
30063. OMC: Memory usage exceeds lower limit . . . . . . . . . . . . . . . . . . . . . . . . 32-104
30064. OMC: Memory usage exceeds upper limit . . . . . . . . . . . . . . . . . . . . . . . . 32-106
30065. OMC: Last MTL may have gone out of service . . . . . . . . . . . . . . . . . . . . . . 32-107
30066. OMC: Database unable to allocate fragment . . . . . . . . . . . . . . . . . . . . . . . 32-108
30067. OMC: No PM database fragment available . . . . . . . . . . . . . . . . . . . . . . . . 32-109
30069. OMC: Maximum number of RTFs in MIB above 90% of license limit . . . . . . . . . . . 32-110
30070. OMC: PM database is down. Unable to bring informix online . . . . . . . . . . . . . . 32-111
30071. OMC: License audit not available alarm . . . . . . . . . . . . . . . . . . . . . . . . . 32-113
30072. OMC: License file not available alarm . . . . . . . . . . . . . . . . . . . . . . . . . . 32-114
30073. OMC: License violation alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-115
30075. OMC: Invalid license file alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-116
30076. OMC: GSM/GPRS trace logs exceeds configured disk space . . . . . . . . . . . . . . . 32-117
50000/50001/50002 OMC: Field engineer password to be changed . . . . . . . . . . . . . . . 32-118
Chapter 33: OML Alarms

Introduction to OML alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-2
0. OML: Invalid received frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-3
1. OML: FRMR frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-5
2. OML: Expiration of N2 - PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-7
Chapter 34: PBUS Alarms

Introduction to PBUS alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-2
254. PBUS: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-3
Chapter 35: PCU Alarms

Introduction to PCU alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-2
0. PCU: Last GSL failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-3
1. PCU: PCU audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-5
2. PCU: Cell mapping failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-7
68P02901W26-S xv
Nov 2007
Contents
51. PCU: Software patch installation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-8
Chapter 36: PPB Alarms

Introduction to PPB alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-2
0. PPB: PCI bridge failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-3
Chapter 37: PPROC alarms

0. PPROC: Processor Communications Failure . . . . . . . . . . . . . . . . . . . . . . . . . . 37-2
9. PPROC: PPROC Reset Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37-3
22. PPROC: SWFM Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37-4
39. PPROC: Software failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37-5
239. PPROC: Process safe test Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 37-6
Chapter 38: PSI Alarms

0. PSI: Re-Initialized Unexpectedly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-3
1. PSI: Hard Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-4
2. PSI: Watchdog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-5
3. PSI: Clock B signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-6
4. PSI: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-7
5. PSI: Assigned timeslot counter underflow . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-8
6. PSI: Assigned timeslot counter overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-9
7. PSI: TDM parity error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-10
11. PSI: DSP 0 Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-11
21. PSI: DSP 10 Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-21
224. PSI: Safe test Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-27
231. PSI: TDM interface configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . 38-28
232. PSI: Processor bus communication failure . . . . . . . . . . . . . . . . . . . . . . . . . 38-29
Chapter 39: PSP Alarms

Introduction to PSP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-2
0. PSP: Communication failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-3
22. PSP: SWFM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-5
39. PSP: Software failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-6
239. PSP: Process safe test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-8
Chapter 40: RSL Alarms

Introduction to RSL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-2
0. RSL: Invalid received frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-3
1. RSL: FRMR frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-5
xvi 68P02901W26-S
Nov 2007
2. RSL: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-7

10. RSL: Link disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-9
11. RSL: LAPD protocol error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-18
13. RSL: LAPD protocol error threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . 40-22
14. RSL: Link audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-25
15. RSL: Too many LAPD protocol errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-27
Chapter 41: SBUS Alarms

Introduction of SBUS alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-2
254. SBUS: Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-3
Chapter 42: SITE Alarms

Introduction to SITE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-3
0. SITE: Last RSL link failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-4
2. SITE: BSC detected MCU to MCU communication failure. . . . . . . . . . . . . . . . . . . 42-12
3. SITE: Active multiplexer 0 loopback failure . . . . . . . . . . . . . . . . . . . . . . . . . . 42-15
4. SITE: Standby multiplexer 0 loopback failure . . . . . . . . . . . . . . . . . . . . . . . . . 42-17
9. SITE: Active local FOX failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-28
10. SITE: Standby local FOX failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-30
11. SITE: Active remote FOX 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-32
12. SITE: Standby remote FOX 0 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-34
17. SITE: 16 kbps switching hardware required . . . . . . . . . . . . . . . . . . . . . . . . . 42-44
18. SITE: MIX board (Slot 18) communication failure . . . . . . . . . . . . . . . . . . . . . . 42-46
19. SITE: Unequipped GPROC has entered the LAN . . . . . . . . . . . . . . . . . . . . . . . 42-47
20. SITE: Unequipped GPROC has left the LAN . . . . . . . . . . . . . . . . . . . . . . . . . 42-51
21. SITE: No clock references available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-55
22. SITE: Active alarm list full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-58
23. SITE: EMU modem card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-60
24. SITE: Site reset request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-61
25. SITE: External power booster amplifier 1 failure . . . . . . . . . . . . . . . . . . . . . . 42-64
26. SITE: External power booster amplifier 2 failure . . . . . . . . . . . . . . . . . . . . . . 42-66
27. SITE: External power booster failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-68
28. SITE: Database configuration and arena hardware mismatch . . . . . . . . . . . . . . . . 42-70
29. SITE: EMU download failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-73
30. SITE: NVM board failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-75
31. SITE: Failure of PCMCIA card 1 on NVM board . . . . . . . . . . . . . . . . . . . . . . . 42-77
32. SITE: Last GBL failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-79
33. SITE: BSSGP status message received from the SGSN. . . . . . . . . . . . . . . . . . . . 42-80
34. SITE: Erroneous BSSGP message received from the SGSN . . . . . . . . . . . . . . . . . 42-81
35. SITE: Network service status message received from the SGSN . . . . . . . . . . . . . . . 42-82
36. SITE: Erroneous network service message received from the SGSN . . . . . . . . . . . . . 42-83
37. SITE: No NS-VC block acknowledgment from the SGSN . . . . . . . . . . . . . . . . . . . 42-84
38. SITE: No NS-VC unblock acknowledgment from the SGSN . . . . . . . . . . . . . . . . . 42-85
39. SITE: No NS-VC alive acknowledgment from the SGSN . . . . . . . . . . . . . . . . . . . 42-86
40. SITE: No NS-VC reset acknowledgment from the SGSN . . . . . . . . . . . . . . . . . . . 42-88
41. SITE: Last NS-VC for the PCU failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-90
42. SITE: Last TRAU GDS failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-91
43. SITE: Last PRP or PXP failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-92
68P02901W26-S xvii
Nov 2007
Contents
45. SITE: No signaling BVC reset acknowledgment from the SGSN . . . . . . . . . . . . . . . 42-94
46. SITE: DSW switching hardware required at site . . . . . . . . . . . . . . . . . . . . . . . 42-95
50. SITE: Database corruption detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-97
51. SITE: Software patch installation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 42-98
Chapter 43: TBUS Alarms

Introduction to TBUS alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43-2
0. TBUS: Remote KSWl loopback test failure . . . . . . . . . . . . . . . . . . . . . . . . . . 43-3
3. TBUS: Local KSWX/DSWX TDM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43-5
4. TBUS: Remote KSWX/DSWX TDM error . . . . . . . . . . . . . . . . . . . . . . . . . . . 43-7
Chapter 44: TDM Alarms

Introduction to TDM alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-2
5. TDM: Bus swap could not be initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-3
229. TDM: Swap test audit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-4
Chapter 45: TIMESLOT Alarms

Introduction to TIMESLOT alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45-2
0. TIMESLOT: Radio frequency losses while using a TCH - PM . . . . . . . . . . . . . . . . . 45-3
1. TIMESLOT: Channel request from MS failed - PM . . . . . . . . . . . . . . . . . . . . . . 45-4
4. TIMESLOT: No Timeslot HealthInfo Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . 45-6
Chapter 46: TRU Alarms

Introduction to TRU alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46-2
0. TRU: Door open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46-3
1. TRU: Power supply unit failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46-5
2. TRU: Power mains failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46-7
5-6. TRU: Customer defined alarm 1-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46-9
Chapter 47: XBL Alarms

Introduction to XBL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-2
0. XBL: Invalid received frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-3
1. XBL: FRMR frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-5
2. XBL: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-7
10. XBL: Link disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-9
11. XBL: LAPD protocol error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-12
13. XBL: LAPD protocol error threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . 47-14
15. XBL: Too many LAPD protocol errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-17
16. XBL: HDLC channel open failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-18
xviii 68P02901W26-S
Nov 2007
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1-1: OMC-R consolidation variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Table 1-2: Device information fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Table 1-3: Alarm categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Table 1-4: Reconfiguration information fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Table 1-5: Severity display colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Table 1-6: Functional unit impact colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Table 5-1: BSP: LAPD controller failure second byte value description. . . . . . . . . . . . . . 5-10
Table 5-2: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Table 5-3: Site reset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Table 6-1: If group_block_unblock_allowed = 0 . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Table 6-5: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Table 6-8: Additional information field values . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
Table 6-9: Additional information field values . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
Table 7-1: BTP FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Table 7-2: BTP: LAPD controller failure second byte descriptions . . . . . . . . . . . . . . . . 7-10
Table 8-1: CAB FRUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Table 12-1: Reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Table 12-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Table 13-1: FRUs that can be equipped with the COMB device . . . . . . . . . . . . . . . . . 13-2
68P02901W26-S xix
Nov 2007
List of Tables
Table 14-1: FRUs that can be equipped with the CSFP device . . . . . . . . . . . . . . . . . . 14-2
Table 15-1: FRUs that can be equipped with the DHP device . . . . . . . . . . . . . . . . . . 15-3
Table 15-2: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-61
Table 16-1: DPROC FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Table 16-2: Reset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Table 17-1: FRUs that can be equipped with the DRI device . . . . . . . . . . . . . . . . . . . 17-8
Table 21-1: GCLK FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Table 21-2: Additional information fields contents . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Table 21-3: Additional information fields contents . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Table 21-4: GCLK timer settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-28
Table 21-6: LTA calibration limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-49
Table 23-1: GPROC FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Table 23-2: GPROC: LAPD controller failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
Table 26-1: KSW FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Table 28-1: Additional information field content . . . . . . . . . . . . . . . . . . . . . . . . . 28-3
Table 29-1: MMS FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Table 30-1: FRUs on which the MSI device may be equipped . . . . . . . . . . . . . . . . . . 30-2
Table 32-1: UPS condition alarm severities . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-88
Table 39-1: PSP FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-2
xx 68P02901W26-S
Nov 2007
List of Tables

Table 40-3: LAPD error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-19
Table 42-3: Process identifier (PID) number . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-62
Table 47-2: LAPD error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47-12
68P02901W26-S xxi
Nov 2007
List of Tables
xxii 68P02901W26-S
Nov 2007
About
This
Manual
Maintenance Information: Alarm Handling

at the OMC-R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is covered in this manual?
This manual provides descriptions and handling procedures for the alarms that can be reported
by the Motorola GSM system. The information in this manual is primarily intended for OMC-R
operators responsible for the resolution of BSS fault conditions.
The hard copy of this manual is presented in three volumes:

• Volume 1 contains Chapters 1 to 17 providing descriptions of alarms in alphabetical order
from ABSS to DRI.
• Volume 2 contains Chapters 18 to 25 providing descriptions of alarms in alphabetical

order from EAS to IAS.
• Volume 3 contains Chapters 26 to 47 providing descriptions of alarms in alphabetical

order from KSW to XBL.
Each volume has a full Contents list and an Index for the whole of the manual.
Background information
This manual should be used in conjunction with the Maintenance Information: BSS Field
Troubleshooting (68P02901W51) manual. The Alarms manual is used by OMC-R operators
to remotely identify the source of an alarm, and the Troubleshooting manual for field
representatives to refer to for onsite procedures. The two manuals should be considered as a
pair, and cross-reference each other through the use of the same alarm identifiers.
Many of the procedures identified in this manual end with the statement: Send field
representative to resolve the problem. Where this is encountered, reference should be
made to the Troubleshooting manual which identifies the actions to be taken when the field
representative reaches the site. These additional procedures help the field representative to
locate the source of the problem.
68P02901W26-S 1
Nov 2007
Revision history
Revision history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Issue Date of issue Remarks

Q Sep 2004 GSM Software release 7 Half Rate
R Nov 2006 GSM Software release 8 GMR-02
S Nov 2007 GSM Software release 9
Resolution of Service Requests
The following Service Requests are resolved in this document:
Service
CMBP Number Remarks
Request
NA NA
Incorporation of Change Notices
The following Change Notices (CN) are incorporated in this document:
CN Date CN Number Title
NA NA
2 68P02901W26-S
Nov 2007
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02901W26-S 3
Nov 2007
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.

Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences
Special key sequences are represented as follows:
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
¦ Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
4 68P02901W26-S
Nov 2007
Contacting Motorola
Contacting Motorola
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola appreciates feedback from the users of our documents.
24–hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Questions and comments
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
• The document type
• The document title, part number, and revision character
• The page number with the error
• A detailed description of the error and if possible the proposed solution
68P02901W26-S 5
Nov 2007
Security advice
Security advice
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.

The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
6 68P02901W26-S
Nov 2007
Warnings, cautions, and notes
Warnings, cautions, and notes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional

information to help the reader understand a topic or concept. A note has the following format:
Note text.
68P02901W26-S 7
Nov 2007
Safety
Safety
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
General safety
The following general safety guidelines apply to Motorola equipment:

• The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.
• Power down or unplug the equipment before servicing.
• Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
• Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
8 68P02901W26-S
Nov 2007
Caring for the environment
Caring for the environment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
Disposal of Motorola equipment
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging
European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’s
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02901W26-S 9
Nov 2007
CMM labeling and disclosure table
CMM labeling and disclosure table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The People’s Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.

• Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
• Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10 68P02901W26-S
Nov 2007
Motorola document set
Motorola document set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner denitions
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY — UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02901W26-S 11
Nov 2007
Data encryption
12 68P02901W26-S
Nov 2007
Chapter
Introduction to Alarm Handling

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter provides an overview of how alarms are organized in this manual and gives the
user a suggested approach to fault-finding using the OMC-R Alarms.
Information in this chapter is covered under the following headings:

• Manual introduction on page 1-2.
• About this chapter on page 1-3.
• Alarm types on page 1-4.
• Device alarm information on page 1-8.
• Reconfiguration information on page 1-13.
• Impact list on page 1-15.
• OOS device list on page 1-17.
• Additional information field on page 1-18.
• OMC-R map display modes on page 1-19.
68P02901W26-S 1-1
Nov 2007
Manual introduction Chapter 1: Introduction to Alarm Handling
Manual introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Manual organization
Chapters
Device alarms are presented in separate chapters and organized in alphabetical order by device
name: ABSS, AXCDR, BCUP, and so on.
Individual alarms
Individual alarms are presented in numerical order, numbered from 0 to 254. Some alarm
numbers are not currently assigned to an alarm and are omitted. The total number of alarms
for a specific device depends on its function and requirements. The following information
is included for each alarm:
• A description.
• A list of Possible causes for the alarm.
• A procedure for the OMC-R operator to resolve the alarm.
Performance Management (PM) alarms
The PM subsystem generates the PM alarms and reports when a statistical threshold is reached.
PM alarms are included in the chapter for the device generating the statistical data. PM alarms
are identified in this manual by the PM designation in the title. The PM designation differentiates
the device and the PM alarms that have the same numerical designation. For example:
Device alarm
0: BSS: Last MTL link failure - Signaling point inaccessible.
PM alarm
0: BSS: Paging request from MSC protocol error - PM.
1-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R About this chapter
About this chapter

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of alarms
This chapter provides an overview of the Motorola GSM system alarm messages reported
to the OMC-R.
Event management
The OMC-R event management subsystem monitors events and alarms generated by the
network. These events are displayed as event and alarm messages.
Event messages
An event is an activity affecting a device or function. Events generate various types of text
messages that the OMC-R reports, including alarm messages.
Alarm messages
An alarm message is generated in response to a fault condition in a device or function. A fault

condition occurs as the result of a hardware failure, a software error, or an operator action.
Alarms messages are displayed at the OMC-R, in alarm windows, based on criteria specified in
subscriptions setup by the operator.
Refer to the OMC-R Online Help, Network Operation for event and alarm handling procedures,
including subscription creation.
68P02901W26-S 1-3
Nov 2007
Alarm types Chapter 1: Introduction to Alarm Handling
Alarm types
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Untagged alarms
Throughout this manual, new and amended features are tagged to help the operators
assess the impact on installed networks. These editorial tags, described under
General Information - About This Manual, are used throughout the Motorola
document set. They have no relevance to the concept of tagged and untagged
alarms described in this section.
Untagged alarms are not associated with the device reconfiguration.
If alarms consolidation is not enabled, all alarms are displayed as untagged, including
the alarms that are associated with the device reconfigurations.
Untagged alarm format
Untagged alarms include device alarm information in the following format:
• #ID - State - Operator - Comment
• Alarm Category - Device Class - Device Instance - Time Date
• Alarm Code - Clearing Type - Alarm Severity Cage/Slot
• Hardware Version Information
• Additional Information
The following example shows an untagged SITE alarm:
#7 - SEEN - *NONE* communication Failure Event - SITE - Trunk 10: 20 SITE - 29/03/2000
14:25:03 [0] Last RSL Link Failure - FMIC Critical -/-
1-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Tagged alarms
Tagged alarms
Tagged alarms are associated with device reconfigurations and are assigned a configuration
tag. A configuration tag is a unique number, assigned by the BSS, that identifies the primary
alarm and all associated secondary alarms.
Primary alarm
A primary alarm is an alarm identified by the BSS Fault Management (FM) subsystem as the
cause of the reconfiguration.
Secondary alarms
Secondary alarms are related to the primary alarm that caused the reconfiguration. Primary
and secondary alarms are presented in the same format, but secondary alarms are identified
with secondary in the reconfiguration line of the tagged alarm message.
If a primary alarm is cleared and an associated secondary alarm is not cleared, the
secondary alarm is reported as an untagged alarm.
Set the OMC-R CONSOLIDATION environment variable to 1 to display secondary alarms.
Refer to the OMC-R Online Help, Network Operation for the procedures to change
environment variables.
The OMC-R consolidation environment variables are listed in Table 1-1.
Table 1-1 OMC-R consolidation variables
Value Descriptions
0 Disable the alarms consolidation feature.
1 Display both primary and secondary alarms.
2 Display only primary alarms.
3 Display only primary alarms and set the subscriber mode as
the default map display mode.
68P02901W26-S 1-5
Nov 2007
Tagged alarms Chapter 1: Introduction to Alarm Handling
Tagged alarm format
Both primary and secondary tagged alarms include the following information:
• Device alarm information.
• Reconfiguration information.
• Impact list.
• OOS device list.
• Additional information.
Tagged alarms use the following format:
• Alarm Category - Device Class - Device Instance - Time Date
• Alarm Code - Clearing Type - Alarm Severity Cage/Slot
• Cause - Operation - Outcome - (Outage) - (Secondary) - Config Tag
• Affected FU : Alarm impact
• OOS Device List
• Hardware Version Information
When a tagged alarm is initially reported, the device alarm information is displayed in a
non-expanded format that includes *More Details* identifier. The following example shows an
unexpanded tagged alarm:
#7 - SEEN - *NONE* communication failure event - SITE - Trunk10: 20 SITE - 29/03/2000

14:25:03 [0] Last RSL Link Failure - FMIC - Critical -/- *More Details*
Tagged alarms can be expanded to present reconfiguration information, by highlighting the

tagged alarm and then selecting show from the alarm details option on the alarms popup menu.
The following example shows an expanded primary alarm:
#7 - SEEN - *NONE* communication failure event - SITE - Trunk10: 20 SITE - 29/03/2000

14:25:03 [0] Last RSL Link Failure - FMIC - Critical -/- LMT request - Lock - RSL 0 20 - Alarm
- Config Tag 4.
At the time of the alarm, the subscriber impact was: SITE 20 : Loss of service
SITE 0 : Loss of service
RSL 0 20 - Enabled - Locked - NO REASON
SITE 20 - Disabled - Unlocked - NO REASON
PATH 0 20 - Disabled - Unlocked - NO REASON
1-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OMC alarm formats
OMC alarm formats
Standard OMC-R alarm format
The standard OMC-R alarm format includes a descriptive error reason in place of the Cage/Slot
information. This format is slightly different from the formats used for other devices. A
descriptive error reason is provided in place of the Cage/Slot information. OMC-R alarms are
presented in the following format:
• Alarm Category - Device Class - Device Instance - Date - Time
• Alarm Code - Clearing Type - Alarm Severity - Error Reason
The following example shows a standard OMC-R alarm:
#2 - NEW - *NONE* processingFailureEvent - BSS - BSS1009 - 31/07/2000 - 11:55:54 [30002]

fileexfFailed - Intermittent (0) - Major - Error getting X25 channel ID 1 - 1-17:0:0-28:7:2000
State change warning alarms
The Q3 Agent is an optional package available for the Motorola OMC-R. When the OMC-R
receives a state change notification for a device that is not visible to the Q3 interface, the
message is sent as an Equipment Failure alarm. This alarm prevents the loss of state change
information. State change warning alarms are presented in the following format:
• Alarm Category - Device Class - Device Instance - Date - Time
• Alarm Code -Old State - Old Reason - New State - New Reason
• Clearing Type - Alarms Severity

The following example shows a state change warning OMC-R alarm:
#3 - NEW - *NONE* equipmentFailureEvent - DRI - BSS1009: 0 DRI 1 - 31/07/2000 - 12:05:56

[30057] H/W Device StateChange - From: (undefined, undefined) - No reason to modify the state
further - To: (undefined, ShuttingDown) - No reason to modify the state further - OIC - Warning
68P02901W26-S 1-7
Nov 2007
Device alarm information Chapter 1: Introduction to Alarm Handling
Device alarm information

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Device information
Device alarm information is provided for both the tagged and untagged alarms. Table 1-2
lists the individual fields and possible values.
Table 1-2 Device information elds
Field Description
#ID Identifier associated with alarm.
State
• NEW
• SEEN
• HANDLING
• DEFERRED
• CLEARED
Operator Person who is handling the alarm.
Comment Comment field to be checked for notes related to previous
instance of the alarm.
Alarm category
• Communication
• Quality of Service
• Processing
• Equipment
• Environment
• Link
• NHA Event
Device class Device generating the alarm.
Device instance Site and device identifiers for the faulty device.
Time Date Time and date, the alarm occurred.
Alarm code The alarm number and text string.
Continued
1-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Alarm states
Table 1-2 Device information elds (Continued)

Field Description
Alarm severity
• Critical
• Major
• Minor
• Warning
• Investigate
• Clear
Clearing types
• FMIC
• Intermittent
• OIC
Cage and slot Hardware alarms includes the cage and slot placement in
the cabinet where the device generating alarm is located.
The field displays -/- for software alarms.
Hardware Version Information Hardware alarms include the hardware version.
Additional Information Some alarms reported by the BSS include additional
information to assist the operator in alarm handling.
Additional information, when included, is displayed at the
end of an alarm message at the OMC-R as one or more
untitled lines. The content and format of the additional
information depends on the reported alarm.
Alarm states
The alarm state indicates the status of each alarm in the Alarm window. This status allows the
operator to determine the actions required quickly, if any, to clear the alarm.
NEW
When the OMC-R receives an alarm, it is automatically assigned the NEW state. This status
indicates that the alarm was received but has not been acknowledged.
SEEN
When an operator selects a NEW alarm, its status is changed from NEW to SEEN. This status
indicates that the operator has acknowledged the alarm.
68P02901W26-S 1-9
Nov 2007
Alarm categories Chapter 1: Introduction to Alarm Handling
HANDLING
When an operator starts the alarm resolution process, the operator must change the alarm
status to HANDLING. This status indicates to anyone, reviewing the Alarms window, that action
is being taken to clear the alarm.
DEFERRED
When the OMC-R operator defers an alarm, it is displayed for 5 seconds as DEFERRED in
the Alarms window and then removed during the deferral period. Alarms that are currently
deferred are displayed only in the Deferred Alarms window.
CLEARED
When the condition that caused the alarm is resolved, the alarm status is changed to CLEARED.
The system automatically clears FMIC alarms. Other alarms require operator action to change
the status to CLEARED.
Alarm categories
Alarm categories identify the general area affected by an alarm.
The category names used in this manual are a simplified representation of the naming convention
used in the OMC-R. Minor differences exist in the naming conventions used in the OMC-R and
BSS. Table 1-3 displays the naming conventions used in this manual, the OMC-R, and the BSS.
Table 1-3 Alarm categories
Manual OMC-R BSS

Communication communicationFailureEvent Communication
Quality of Service qualityOfServiceFailureEvent Quality of Service
Processing processingFailureEvent Processing
Equipment equipmentFailureEvent Equipment
Environmental environmentFailureEvent Environmental
Link linkFailureEvent Equipment
NHA Event NHA-Event N/A
Communication
A communication alarm indicates a fault affecting the transfer of data from one point to another.
Quality of Service
A quality of service alarm indicates a degradation in the quality of service.
1-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Alarm severities
Processing
A processing alarm indicates a software or processing fault.
Equipment
An equipment alarm indicates a hardware failure.
Environmental
An environmental alarm indicates that a change has occurred in a physical location.
Link
A link alarm indicates that a fault exists in the X.25 link connection between the OMC-R and
a network element.
NHA Event
An NHA event alarm indicates that the NHA detects a network problem.
Alarm severities
Each alarm generated by the system is assigned a severity indicating the impact of the fault
condition. The alarm severity is used to establish fault handling priority.
Critical
A critical alarm indicates the existence of a fault condition that causes a loss of service and
requires immediate resolution.
Major
A major alarm indicates the existence of a fault condition that causes a loss of capacity. Major
alarms require immediate resolution, but with less urgency than a critical alarm.
Minor
A minor alarm indicates the existence of a fault condition that causes a loss of redundancy.
Minor alarms do not require immediate resolution. Resolve the minor alarms to avoid a more
serious fault in the future.
Warning
A warning alarm indicates the existence of a non-service affecting a fault condition. Resolve
warning alarms to avoid a more serious fault in the future.
68P02901W26-S 1-11
Nov 2007
Clearing types Chapter 1: Introduction to Alarm Handling
Investigate
An investigate alarm indicates the existence of a fault condition for which the severity cannot
be determined. Investigate alarms require operator analysis to determine the impact of the
fault causing the alarm.
Clear
This severity indicates the fault condition that caused a previously reported alarm, that has
been resolved.
Clearing types
Clear the alarm at the OMC-R, after a fault condition is resolved. There are three alarm
clearing types.
FMIC
The BSS or OMC-R FM subsystem automatically clears the FMIC alarms when the fault condition
that caused the alarm is resolved. The system reports every occurrence of an FMIC alarm.
OIC
The OMC-R operator must clear the OIC alarms after the fault condition that caused the alarm
is resolved. The system reports an OIC alarm only once.
Intermittent
Intermittent alarms are transient and are not associated with a serious fault condition. After the
intermittent alarms are displayed in the alarm window, the operator must handle and clear the
alarm. The system reports every occurrence of an intermittent alarm unless it is throttled.
1-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Reconguration information
Reconguration information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Device state change
Each primary and secondary tagged alarm includes information indicating the events that
resulted in a device state change. State changes occur due to a fault or some action by an
operator.
Remote reconguration
A reconfiguration at one site can result in reconfigurations at other sites. Reconfigurations at

remote sites are classified as remote reconfigurations.
Table 1-4 lists the individual fields and possible values.
Table 1-4 Reconguration information elds
Field Description
Cause The reconfiguration is the result of one of the following events:
• Fault
• OMC request
• LMT request
• Initialization
• Restoration
• Remote
Operation The reconfiguration was performed by one of the following
actions:
• Unequip
• Equip
• Unlock
• Lock
• Shutdown
Continued
68P02901W26-S 1-13
Nov 2007
Remote reconguration Chapter 1: Introduction to Alarm Handling
Table 1-4 Reconguration information elds (Continued)

Field Description
Operation
• Swap disable
• Enable
• Reset
• Lock-unlock
• Disable-enable-soft
• Disable-enable-hard
Outcome The reconfiguration causes one of the following system
responses:
• Alarm
• Recovered outage
• Advisory
• Clear
• Pending
Outage This is an optional field displayed if the SITE or CELL has
experienced an autonomously recovered outage with a
duration greater than 30 seconds. The value is the length of
the recovered outage.
Secondary This is an optional field displayed only if the alarm is a
secondary alarm. Secondary is the only value that is displayed
in this field.
Config Tag This is a number used to identify the primary and all secondary
alarms associated with a specific device reconfiguration.
1-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Impact list
Impact list
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Impact of the alarm
The list indicates the impact of the alarm on subscriber service.
Affected functional units
The impact is reported against a Functional Unit (FU). FUs are logical entities against which
related device alarms are reported. There are only two FUs: CELL and SITE.
CELL
An alarm reported against a CELL FU device affects only the subscribers on the cell. State
changes on the following devices are reported against CELL FUs:
CELL DRI
SITE
An alarm reported against a SITE FU device affects all subscribers on the site. State changes on
the following devices are reported against SITE FUs:
BSP DHP MSI/MMS (circuit) SITE

BTP EAS MTL TBUS
CBL GCLK OML TDM
CBUS GPROC PATH XBL
COMB KSW RSL
Impact list format
The following format is used for the impact list:
FU ID: Alarm impact
Examples
SITE 1: Loss of Capacity
CELL 543 21 00001 00001: Loss of Service
68P02901W26-S 1-15
Nov 2007
Alarm impact Chapter 1: Introduction to Alarm Handling
Alarm impact
The impact of the device alarm for each FU indicates the effect on subscriber service.
Loss of service
This is a critical service-affecting condition causing a loss of service at a site or cell. Immediate
resolution action is required.
Loss of capacity
This is a condition causing a loss of capacity (as in traffic channels), but not causing a loss of
service at the site. Immediate resolution action is required, but with less urgency than that
required for a loss of service alarm.
Loss of redundancy
This condition causes a loss of redundancy (backup devices) at a site that may or may not affect
service to a site. Prompt action is required to reduce the possibility of a more serious condition.
1-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OOS device list
OOS device list

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Device state
The Out of Service (OOS) device list displays all the OOS devices because of the alarm. The OOS
devices are listed in descending order of importance.
The list includes the operation and administrative states and a reason code for each device
rendered OOS. A maximum of 20 devices can be listed.
When a device on the list is returned to service, it is removed from the OOS device list.
OOS device list format
The following format is used for the OOS device list:
Device ID - Operation State - Administrative State - Time
Refer to the Maintenance Information: Device State Transitions (68P02901W57)

manual for detailed descriptions of the possible operation state, administrative state,
and reason values.
68P02901W26-S 1-17
Nov 2007
Additional information eld Chapter 1: Introduction to Alarm Handling
Additional information eld

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Alarm handling
Some alarms reported by the BSS include additional information to assist the operator in alarm
handling. Additional information appears in both tagged and untagged alarms.
Alarm message
Additional information, when included, is displayed at the end of an alarm message at the
OMC-R as one or more untitled lines. The content and format of the additional information
depends on the reported alarm. For example, the additional information include error codes
to identify the cause of an alarm.
When viewing the Additional information field, ignore the bytes displayed that are
additional to the bytes described in this manual.
1-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OMC-R map display modes
OMC-R map display modes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
OMC-R maps
OMC-R maps display alarms in one of two modes: device and subscriber.
Set the CONSOLIDATION environment variable to 1, 2 or 3 to permit the maps to

display the alarms in the subscriber mode.
Device mode
In the device mode, an alarm is displayed based on the severity of the fault on the specific
device reporting the alarm.
Subscriber mode
In the subscriber mode, an alarm is displayed based on the impact of the fault on subscriber
service. This mode presents a high-level view of the network using a set of icons representing
the Functional Units (FUs) in the network.
Selecting the map display mode
The display mode is selected on a Map window by clicking either the impact on devices or
impact on subscriber option in the view drop-down menu.
68P02901W26-S 1-19
Nov 2007
Map display colors Chapter 1: Introduction to Alarm Handling
Map display colors
Severity display colors
Colors indicate the severity for all alarms in the device mode and untagged alarms in the
subscriber mode. Table 1-5 presents the default icon colors and corresponding alarm severities.
Table 1-5 Severity display colors
Icon color Severity

Red Critical
Yellow Major
Blue Minor
Pink Warning
Light blue Investigate
Green Normal (Clear; no alarms)
Functional unit impact colors
Colors indicate the impact of an alarm on a FU in the subscriber mode. Table 1-6 presents the
default icon colors and the corresponding alarm impacts.
Table 1-6 Functional unit impact colors
Icon color Severity

Red Loss of Service
Yellow Loss of Capacity
Blue Loss of Redundancy
Pink Warning (untagged alarm)
Light blue Investigate (untagged alarm)
Green Normal (Clear; no alarms)
1-20 68P02901W26-S
Nov 2007
Chapter
ABSS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R ABSS Alarms and includes the following alarm procedures:
• 0. ABSS: Last XBL link failure on page 2-2.
• 1. ABSS: RXCDR detecting CIC validation failure on page 2-4.
• 2. ABSS: Circuit configuration problem on page 2-6.
68P02901W26-S 2-1
Nov 2007
0. ABSS: Last XBL link failure Chapter 2: ABSS Alarms
0. ABSS: Last XBL link failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Severity Level: Critical
Category: Communication
Description
The last communication link from the RXCDR to the specified BSS has gone OOS.
If CIC validation is enabled for the local RXCDR, the BSC blocks all CICs routed through the
RXCDR. No call traffic is possible between the specified BSS and the RXCDR.
If CIC validation is not enabled for the local RXCDR, the BSC does not block CICs and call traffic
is not immediately impacted. If the RXCDR experiences a fault condition causing the CIC to be
blocked, the BSC is not notified. In this case, traffic is impacted because the BSC attempts to
use the blocked CIC resulting in no audio.
There is no additional information in the output for this alarm.
Possible causes
The following are the Possible causes for this alarm:

• An equipment malfunction has taken the last XBL out of service.
• The MMS on the RXCDR or BSC, where the XBL is equipped, has failed.
• An operator action has taken the last XBL out of service.
• The BSC reset.
2-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Perform the following procedure to resolve the alarm.
Procedure 2-1 Restore XBL to service
1 Attempt to restore the XBL, identified in the alarm message, to service.

If the XBL... Then...
returns to service No further action is required.
does not return to service Go to step 2.
2 Determine if any operator actions caused the alarm, such as locking an
MSI, MMS or the last XBL device.
If operator action... Then...
caused the alarm After the operator action is complete,
return the XBL to service. If the
XBL does not return to service, go
to step 3.
did not cause the alarm Go to step 3.
3 Review Events window to determine if a BSC reset occurred.
If a BSC reset... Then...
occurred Wait until the reset is completed
and then determine if the
XBL returns to service.
If the XBL returns to service,
no further action is required.
If the XBL does not return to service,
go to step 4.
did not occur Go to step 4.
4 Review the Events window for XBL alarms.
If XBL alarms... Then...
are present Troubleshoot the XBL alarms.
are not present Go to step 5.
5 Review the Events window for alarms on the MMS on which the XBL
is equipped.
If MMS alarms... Then...
are present Troubleshoot the MMS alarms.
are not present The problem is not at the RXCDR.
A fault condition probably exists at
the BSS. Look for alarms or operator
actions at the BSS affecting the XBL,
MMS, MSI, or GPROC to which the
RXCDR was assigned at the BSC.
68P02901W26-S 2-3
Nov 2007
1. ABSS: RXCDR detecting CIC validation failure Chapter 2: ABSS Alarms
1. ABSS: RXCDR detecting CIC validation failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The ABSS was placed in the Busy-Unlocked state indicating that CIC validation is enabled at the
BSC, but the BSC did not initiate CIC validation for this RXCDR.
• All CICs going to the RXCDR are blocked at the MSC. The RXCDR does not handle any
calls from the BSC until the problem is resolved.
• CICs are not blocked at the MSC, but only certain CICs are capable of handling the traffic.
This causes CERM alarms and a high rate of incomplete calls.
Possible causes

• LAPD errors on the XBL link.
• The XBL link or switching equipment between the BSC and the RXCDR is malfunctioning.
2-4 68P02901W26-S
Nov 2007
Procedure
Procedure 2-2 Restore ABSS to service
1 Attempt to restore the ABSS to service.

If the ABSS... Then...
2 Review the Alarms window for XBL alarms.
If XBL alarms... Then...
are present Troubleshoot the XBL alarms.
are not present Go to step 3.
3 A fault condition probably exists in the switching equipment between the
BSC and the RXCDR. Troubleshoot the switching equipment fault and take
appropriate repair action.
If the problem is not resolved after troubleshooting the switching equipment, CIC
validation at the BSC could be disabled as a last resort.
68P02901W26-S 2-5
Nov 2007
2. ABSS: Circuit conguration problem Chapter 2: ABSS Alarms
2. ABSS: Circuit conguration problem

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The RXCDR is unable to make a proper connection for at least one CIC. The ABSS is in the
Disabled-Unlocked-No Validation state and there is at least one CIC with no static ater for
the ABSS.
All calls are set up by the BSC as the MSC requests. Since there is no proper switch connection
for the CICs at the RXCDR, there is no audio on the affected CICs.
The Additional information field displays the number of affected CICs for a specific ABSS.
Possible causes
One or more CICs were equipped with no static aters at the ABSS in Disabled-Unlocked-No
Validation state.
Procedure
Use one of the following procedures to resolve the alarm.
Procedure 2-3 Re-equip CICs with static aters
1 Identify which CICs on the ABSS do not have static aters.

2 Unequip the CICs that do not have static aters.
3 Re-equip the CICs with static aters.
Procedure 2-4 Change ABSS mode of operation
Change the ABSS mode of operation from backwards compatible to dynamic

mode or auto connect mode.
2-6 68P02901W26-S
Nov 2007
Chapter
AXCDR Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R AXCDR Alarms and includes the following alarm procedures:
• 0. AXCDR: BSC detecting CIC validation failure on page 3-3.
• 0. AXCDR: Ater pre-emption failure statistic alarm - PM on page 3-4.
• 1. AXCDR: AXCDR ID mismatch with RXCDR network entity ID on page 3-6.
68P02901W26-S 3-1
Nov 2007
Introduction to AXCDR alarms Chapter 3: AXCDR Alarms
Introduction to AXCDR alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
AXCDR alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Associated
Transcoder (AXCDR) device.
3-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. AXCDR: BSC detecting CIC validation failure
0. AXCDR: BSC detecting CIC validation failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The RXCDR failed to respond to repeated attempts by the BSC to initiate the CIC validation
procedure. The effect of this failure is that CIC validation is not performed between the BSC
and the RXCDR for the affected RXCDR. All CICs connected to the affected RXCDR are blocked.
Possible causes
The RXCDR has not been upgraded to a software release that supports CIC validation.
Procedure
Procedure 3-1 BSC detecting CIC validation failure
1 Turn CIC validation off at the BSC for the affected RXCDR.
2 Upgrade the affected RXCDR to a software release that supports
CIC validation.
3 Turn CIC validation on at the BSC for the affected RXCDR.
68P02901W26-S 3-3
Nov 2007
0. AXCDR: Ater pre-emption failure statistic alarm - PM Chapter 3: AXCDR Alarms
0. AXCDR: Ater pre-emption failure statistic alarm - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: Intermittent

Severity Level: Warning
Category: Quality of Service
Description
The ATER_PREEMPT_FAIL AXCDR statistic threshold has been reached. This statistic
represents the number of calls triggering the Ater pre-emption mechanism without being
allocated a resource.
When this alarm occurs, calls with pre-emption capabilities trigger pre-emption. Inability to
allocate terrestrial resources results in failure to establish calls within the BSS.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes

• Ater resources have been exhausted in the AXCDR and the AXCDR is full of calls of higher
priority calls or calls, which are not vulnerable to pre-emption.
• Ater resources selected for pre-emption was not available in time.
3-4 68P02901W26-S
Nov 2007
Procedure
Procedure 3-2 Ater pre-emption failure statistic alarm - PM
1 Re-evaluate the capacity of the affected AXCDR. This reduces the number of
pre-emption events within the cell and therefore, result in a lower level of
pegging of this alarm and a reduced chance of the alarm being raised.
2 Re-evaluate the priority level/PCI/PVI capabilities of call groups. If the
AXCDR experiences periods of overload of higher priority or pre-emption of
non-vulnerable calls, it is possible that this alarm is raised. This is due to
a particular network event or due to the priority level/PCI/PVI capabilities
of the call groups. If the network event is a regular occurrence, the alarm
threshold should be adjusted to account for this if applicable. Alternatively,
re-evaluation of the priority level/PCI/PVI capabilities of the call groups
may be required.
Priority level/PCI/PVI capabilities are controlled by the network,

not by the BSS.
68P02901W26-S 3-5
Nov 2007
1. AXCDR: AXCDR ID mismatch with RXCDR network entity ID Chapter 3: AXCDR Alarms
1. AXCDR: AXCDR ID mismatch with RXCDR network

entity ID
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSC has detected that the network identifier of the AXCDR at the BSC does not match the
corresponding RXCDR device at the RXCDR site.
No call traffic is possible between the BSS and the indicated AXCDR. All CICs through that
AXCDR are blocked.
Possible causes

• The network identifier of the AXCDR at the BSC does not match with the corresponding
RXCDR device ID at the RXCDR site.
• The linkage between the BSC and the RXCDR is incorrect.
3-6 68P02901W26-S
Nov 2007
Procedure
Procedure 3-3 AXCDR ID mismatch with RXCDR network entity ID
1 Determine whether the AXCDR or RXCDR network identifiers are

different.
If network identifiers... Then...
are the same Go to step 5.
are not the same Go to step 2.
2 Modify either the AXCDR or the RXCDR network identifier.
To modify the... Then...
AXCDR network identifier Go to step 3.
RXCDR network identifier Go to step 4.
3 Modify the network identifier of the AXCDR or the RXCDR device to
make the network identifiers the same.
4 Modify the RXCDR network identifier. When the RXCDR network
identifier is modified, all ABSS devices equipped at the RXCDR cycle
and all traffic routed through the RXCDR is dropped.
5 Correct the linkage between the BSC and the RXCDR.
68P02901W26-S 3-7
Nov 2007
Procedure Chapter 3: AXCDR Alarms
3-8 68P02901W26-S
Nov 2007
Chapter
BCUP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R BCUP Alarms and includes the following alarm procedures:
• 0. BCUP: Unexpected board type on page 4-3.
• 1. BCUP: Serial bus connection failure on page 4-5.
• 8. BCUP: Output failure on page 4-7.
• 9. BCUP: Input failure on page 4-9.
• 10. BCUP: Over temperature warning on page 4-11.
68P02901W26-S 4-1
Nov 2007
Introduction to BCUP alarms Chapter 4: BCUP Alarms
Introduction to BCUP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BCUP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base
Controller Unit Power supply (BCUP) device.
BCUP alarms are reported only for InCell BTS, BSC, and RXCDR hardware.
FRUs
The BCUP device is equipped on power supply units specified for the hardware platform in use.
4-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. BCUP: Unexpected board type
0. BCUP: Unexpected board type

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Severity Level: Investigate
Category: Equipment
Description
The system detected an unexpected BCUP board type. This alarm occurs only if the BCUP board
type suddenly changes without being removed and reinserted.
Possible causes

• The power supply has failed.
• Serial bus communication problems.
Procedure
Procedure 4-1 Unexpected board type
Send a field representative to the site to replace the power supply module.
68P02901W26-S 4-3
Nov 2007
Procedure Chapter 4: BCUP Alarms
Fault management is required at the BSS or RXCDR site.
On site support requires:
• Release-dependent customer document Maintenance Information: BSS Field

Troubleshooting (68P02901W51).
• The following details, as displayed in the alarm information on the OMC screen:
Fault code (device identifier, alarm number, and alarm description), so that
the relevant troubleshooting procedure can be quickly accessed.
Site data. For example, site number, the state of the device, the cage
number and slot numbers.
4-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. BCUP: Serial bus connection failure
1. BCUP: Serial bus connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BCUP device has not responded to the attempts for communication by the Serial Bus
(SBUS) processor.
Possible causes

• The physical connection between the BCUP boards and the SBUS processor is broken.
• The SBUS signal line is faulty.
• The BCUP boards were not properly installed.
Procedure
Procedure 4-2 Serial bus connection failure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action and resolve the alarm.
68P02901W26-S 4-5
Nov 2007

4-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. BCUP: Output failure
8. BCUP: Output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BCUP output power failed.
Possible causes

• The input power source is faulty.
• The output power source is faulty.
• The output power source is overloaded.
Procedure
Procedure 4-3 Output failure
and take appropriate action to resolve the alarm.
68P02901W26-S 4-7
Nov 2007

4-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. BCUP: Input failure
9. BCUP: Input failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BCUP input power has failed.
Possible causes

• The input power source is faulty.
• The circuit breaker has tripped or failed.
Procedure
Procedure 4-4 Input failure
68P02901W26-S 4-9
Nov 2007

4-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. BCUP: Over temperature warning
10. BCUP: Over temperature warning

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The temperature of the power supply module has exceeded safe limits.
Possible causes

• The airflow is restricted.
• The fan has failed.
Procedure
Procedure 4-5 Over temperature warning
68P02901W26-S 4-11
Nov 2007

4-12 68P02901W26-S
Nov 2007
Chapter
BSP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R BSP Alarms and includes the following alarm procedures:
• 1. BSP: EEPROM flash failure - No valid bootstrap code detected on page 5-4.
• 8. BSP: EEPROM flash object failure on page 5-6.
• 17. BSP: EEPROM flash programming failure on page 5-8.
• 20. BSP: LAPD controller failure on page 5-10.
• 21. BSP: EEPROM flash programming failure on page 5-11.
• 22. BSP: SWFM indication on page 5-13.
• 30. BSP: Clock A signal loss on page 5-14.
• 31. BSP: Clock B signal loss on page 5-17.
• 32. BSP: TDM interface failure - Assigned timeslot counter underflow on page 5-20.
• 33. BSP: TDM interface failure - Assigned timeslot counter overflow on page 5-22.
• 34. BSP: TDM interface failure - TDM parity error on page 5-24.
• 35. BSP: LAN connection failure on page 5-26.
• 39. BSP: Software failure on page 5-28.
• 40. BSP: Spurious interrupt on page 5-30.
• 47. BSP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected

on page 5-32.
• 48. BSP: Memory location fault on page 5-34.
• 50. BSP: EEPROM SW flash programming failure on page 5-35.
• 51. BSP: EEPROM HW flash programming failure on page 5-36.
• {23306}52. BSP: BSP CPU Safe Overload on page 5-37.
• {23306}53. BSP: BSP CPU critical overload on page 5-39.
68P02901W26-S 5-1
Nov 2007
Procedure Chapter 5: BSP Alarms
• 231. BSP: TDM interface configuration failure on page 5-41.
• 232. BSP: Processor bus communication failure on page 5-43.
• 239. BSP: Process safe test audit failure on page 5-44.
• 254. BSP: Device failure on page 5-46.
5-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BSP alarms
Introduction to BSP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base Station
Processor (BSP) device.
After the BSP switchover takes place, the following occurs:
• The alarm throttling time is restarted.
• Throttled alarms are recounted.
• The registration of processes for alarm notification is not kept. The registration is
recovered after the processes register again.
• The devices fault history is cleared and alarms handler for the devices creates new device
fault history.
Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS to
mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
At the BSC, the BSP can only be GPROC3/GPROC3-2.
68P02901W26-S 5-3
Nov 2007
1. BSP: EEPROM ash failure - No valid bootstrap code detected Chapter 5: BSP Alarms
1. BSP: EEPROM ash failure - No valid bootstrap code

detected
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Processing
Description
The Initialization Process (IP) has determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt. In this case, initialization is not permitted.
Possible causes

• The bootstrap code object (Object 15) at the site is corrupt.
• The bootstrap code object (Object 15) was corrupted while being downloaded at the
GPROC.
Procedure
Carry out the following procedure to resolve the alarm.
Procedure 5-1 EEPROM ash failure - No valid bootstrap code detected
1 Determine if this alarm is occurring at other BSSs or other sites

within a single BSS.
If this alarm is occurring Then...
at...
other BSSs Go to step 2.
other sites within a single BSS Go to step 4.
Continued
5-4 68P02901W26-S
Nov 2007
Procedure 5-1 EEPROM ash failure - No valid bootstrap code detected (Continued)
2 Obtain a new OMC-R code bootstrap object.
If the alarm... Then...
is cleared and does not recur No further action is required.
is not cleared or recurs Send a field representative to the
site to replace the GPROC board.
3 Download the new object to the affected BSSs and then attempt
to clear the alarm.
4 Download the object to the BSC and then attempt to clear the alarm.
A BSS-wide outage occurs when downloading to the BSC.


68P02901W26-S 5-5
Nov 2007
8. BSP: EEPROM ash object failure Chapter 5: BSP Alarms
8. BSP: EEPROM ash object failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The size of the user start address in the header information of the bootstrap code object (Object
15) is incorrect. As a result, reprogramming is not initiated.
Possible causes

• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is programmed incorrectly with regard to the
GPROC EEPROM address space.
5-6 68P02901W26-S
Nov 2007
Procedure
Procedure 5-2 EEPROM ash object failure

If this alarm is occurring Then...
at...
2 Obtain a new OMC-R code object.
to clear the alarm.
A BSS-wide outage occurs when downloading the object

to the BSC.

68P02901W26-S 5-7
Nov 2007
17. BSP: EEPROM ash programming failure Chapter 5: BSP Alarms
17. BSP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
An attempt to erase bank 0 before reprogramming a flash EEPROM was unsuccessful. Bank 0
contains a byte that can be reprogrammed after a bank erase.
This fault condition is not a problem unless the GPROC is being reset, at which time
the GPROC is rendered useless.
Possible causes
The flash EEPROM in bank 0 is faulty.
Procedure
Procedure 5-3 EEPROM ash programming failure
Send a field representative to the site replace the GPROC board.
5-8 68P02901W26-S
Nov 2007

68P02901W26-S 5-9
Nov 2007
20. BSP: LAPD controller failure Chapter 5: BSP Alarms
20. BSP: LAPD controller failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Severity Level: Minor
Description
The LAPD controller on the BSP has encountered a fatal error.
Two bytes are displayed. Ignore the first byte, the second byte has a value of 1 or 2. The second
byte value descriptions are shown in Table 5-1.
Table 5-1 BSP: LAPD controller failure second byte value description
Value Description
1 The LAPD controller has encountered a non recoverable internal fault.
2 The LAPD controller cannot open a new channel for RSL link.
Possible causes
• The micro code in the LAPD controller has encountered a fatal exception.
• The SRAM of the BSP could be faulty.
• The LAPD controller cannot open a new LAPD channel due to an internal error.
Procedure
Procedure 5-4 LAPD controller failure
1 Clear the alarm.

2 If the alarm recurs, replace the BSP.
5-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. BSP: EEPROM ash programming failure
21. BSP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
An attempt to program a byte on the EEPROM was unsuccessful.
This fault condition is not a problem until the GPROC is reset, at which time the
GPROC is rendered useless.
Possible causes
The flash EEPROM device is faulty.
Procedure
Send a field representative to the site to replace the GPROC board.
68P02901W26-S 5-11
Nov 2007

5-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. BSP: SWFM indication
22. BSP: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system has detected a software processing error (SWFM) for a BSP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
A software processing error.
Procedure
Perform the following step to resolve the alarm.
Procedure 5-6 SWFM indication
Clear the alarm.
68P02901W26-S 5-13
Nov 2007
30. BSP: Clock A signal loss Chapter 5: BSP Alarms
30. BSP: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC
Severity Level: Major

Category: Equipment
Description
The BSP detected a TDM Clock A failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BSP switches to the
redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference
fails and causes the site to go OOS.
The fault condition reported by this alarm cause the site to go OOS.
Possible causes

• The KSWX A clock extender card has failed.
• The Clock A receive circuitry on the GPROC board is faulty.
• A fiber optic cable is faulty.
5-14 68P02901W26-S
Nov 2007
Procedure
Procedure 5-7 Clock A signal loss
1 Determine the current administrative and operational state of the site.

If Site is... Then...
busy-unlocked Go to step 2.
not busy-unlocked Send a field representative to the
site to replace the Clock A GCLK.
2 Determine if any of the following alarms are reported by other devices

in the same cage as Clock A:
• Clock A Signal Loss.
• 6.12 seconds Reference Loss.

3 Verify that the redundant clock is in service and not reporting any
alarms.
If the redundant clock is... Then...
busy-unlocked with no alarms Go to step 4.
not busy-unlocked or Send a field representative to the
busy-unlocked with alarms site to replace the redundant GCLK.
not equipped Go to step 5.
4 Check if more than 50% of the devices in the same cage are reporting
clock alarms.
If... Then...
yes Force the BSP to swap to the
redundant clock.
• The site resets when the clock

is swapped.
• After the site reset is complete,

go to step 5.
no Go to step 5.
Continued
68P02901W26-S 5-15
Nov 2007
Procedure 5-7 Clock A signal loss (Continued)

5 Send a field representative to the site to perform one of the following
procedures based on the results of step 2.
If clock alarms... Then...
are present on more than 50% The GCLK failed. The CBUS 0 alarm
of the other devices is also reported and taken OOS.
Replace the GCLK.
are present only for the BSP Replace the BSP.
are not present on other devices TDM Clock A detection circuitry on
the MSI board failed. Replace the
MSI board.

5-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. BSP: Clock B signal loss
31. BSP: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSP detected a TDM Clock B failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BSP switches to the
Possible causes

• The KSWX B clock extender card failed.
• The Clock B receive circuitry on the GPROC board is faulty.
Procedure
Procedure 5-8 Clock B signal loss
1 Determine if the site is in service.

site to replace the Clock B GCLK.
Continued
68P02901W26-S 5-17
Nov 2007
Procedure 5-8 Clock B signal loss (Continued)

2 Determine if any of the following alarms are reported by other
devices in the same cage as Clock B:
• Clock B Signal Loss.

alarms.
not busy-unlocked or Send a field representative to
busy-unlocked with alarms the site to replace the redundant
GCLK.
4 Check if more than 50% of the devices in the same cage are reporting
clock alarms.
If... Then...
yes Force the BSP to swap to the
redundant clock.
• The site resets when the clock

is swapped.
• After the site reset is

complete, go to step 5.
no Go to step 5
are present on more than 50% The GCLK failed. The
of other devices CBUS 0 alarm is also
reported and taken OOS.
Replace the GCLK.
are present only for the BSP Replace the BSP.
are not present on other devices TDM Clock A detection circuitry on
the MSI board failed. Replace the
MSI board.
5-18 68P02901W26-S
Nov 2007

68P02901W26-S 5-19
Nov 2007
32. BSP: TDM interface failure - Assigned timeslot counter underow Chapter 5: BSP Alarms
32. BSP: TDM interface failure - Assigned timeslot

counter underow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSP has determined that the TDM highway is underused. Fewer switch-bound timeslots are
driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes

• The timeslot allocation RAM is faulty.
• The MCAP interface has failed.
• One or more MCAP data or address lines on the backplane are faulty.
• Assigned timeslot counter register has failed.
5-20 68P02901W26-S
Nov 2007
Procedure
Procedure 5-9 TDM interface failure - Assigned timeslot counter underow
1 Determine the current state of the site.

If site is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Go to step 2.
2 Reset the BSP.
The site is reset.

3 Determine the state of the BSP after the reset is completed.
If BSP is... Then...
required.

68P02901W26-S 5-21
Nov 2007
33. BSP: TDM interface failure - Assigned timeslot counter overow Chapter 5: BSP Alarms
33. BSP: TDM interface failure - Assigned timeslot

counter overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSP has determined that the TDM highway is overused. More switch-bound timeslots are
Possible causes

• The Timeslot Allocation RAM is faulty.
• Assigned timeslot counter register has failed.
5-22 68P02901W26-S
Nov 2007
Procedure
Procedure 5-10 TDM interface failure - Assigned timeslot counter overow

required.
2 Reset the BSP.
The site is reset.

required.

68P02901W26-S 5-23
Nov 2007
34. BSP: TDM interface failure - TDM parity error Chapter 5: BSP Alarms
34. BSP: TDM interface failure - TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An incorrect parity was detected on the inbound TDM highway.
Possible causes

• The TDM interface circuitry on GPROC failed.
• The TDM bus interface on a KSW/KSWX failed.
• One or more signals of the TDM bus on the backplane failed.
5-24 68P02901W26-S
Nov 2007
Procedure
Procedure 5-11 TDM interface failure - TDM parity error

required.
2 Reset the BSP.
The site is reset.

required.

68P02901W26-S 5-25
Nov 2007
35. BSP: LAN connection failure Chapter 5: BSP Alarms
35. BSP: LAN connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAN connection between the master GPROC and any other equipped BSP on the LAN failed.
System action
The system places the BSP OOS. If the BSP is the master GPROC, the site resets.
Possible causes

• The BSP was reset through software or the front panel on site.
• The GPROC is faulty.
• The LANX hardware is faulty.
5-26 68P02901W26-S
Nov 2007
Procedure
Procedure 5-12 LAN connection failure

required.
2 Reset the BSP.
The site is reset.

required.

68P02901W26-S 5-27
Nov 2007
39. BSP: Software failure Chapter 5: BSP Alarms
39. BSP: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BSP experienced a non-recoverable SWFM error.
System action
If there is only one processor in the site, the site is reset. If there is a redundant processor,
control is handed to the redundant processor.
The Additional information field includes process information that is useful only to the
programmers.
Possible causes

• The BSP software is faulty.
5-28 68P02901W26-S
Nov 2007
Procedure
Procedure 5-13 Software failure
1 Determine the state of the site.

If the site is... Then...
2 Send a field representative to the site to replace the GPROC board.
3 Determine the state of the BSP.
If the BSP is... Then...
busy-unlocked The alarm is caused
by a software error.
Contact a Motorola representative
to resolve the software error.

68P02901W26-S 5-29
Nov 2007
40. BSP: Spurious interrupt Chapter 5: BSP Alarms
40. BSP: Spurious interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSP received and acknowledged an interrupt message but did not receive a response from
the device generating the interrupt.
There is no additional information displayed in the output for this alarm.
Possible causes

• The timer on the BSP monitoring the MCAP Bus is faulty causing the wait timer to expire
before receiving the response message.
• An MCAP board is faulty.
• The MCAP Bus within a cage is faulty.
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or some
other cause.
• The backplane connections to any of the MCAP boards are faulty.
5-30 68P02901W26-S
Nov 2007
Procedure
Procedure 5-14 Spurious interrupt
1 Determine if the site was reset.

If the site was... Then...
reset Go to step 2.
not reset Go to step 3.
3 Determine the current state of the BSP.
required.
4 Send a field representative to the site to determine the cause of the
alarm and take appropriate action.

68P02901W26-S 5-31
Nov 2007
47. BSP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 5: BSP Alarms
47. BSP: Unexpected board type: GPROC2 or {28337}

GPROC3/GPROC3–2 expected
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
{28337} The BSC generates this alarm when it detects a GPROC/GPROC2 board in a slot in
place of GPROC3/GPROC3–2 board. BSPs at the RXCDR and BSC can be a GPROC2.
The BSC generates this alarm when it detects a GPROC board in a slot in place of GPROC2 or
{28337} GPROC3/GPROC3–2 board. BSPs at BSC must be at least GPROC3, BSPs at RXCDR
must be at least GPROC2.
Possible causes
If this alarm occurs in an InCell site, the GPROC board does not come into service.

• A GPROC board is installed instead of a required GPROC2 or {28337} GPROC3/GPROC3–2
board.
• A GPROC board is installed and the gproc_slots database parameter is set to 32.
5-32 68P02901W26-S
Nov 2007
Procedure
Procedure 5-15 Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected
1 Verify the value assigned to the gproc_slots database parameter.

If the value is... Then...
correct send a field representative to the
site to replace the GPROC board
with a GPROC2 or a {28337}
GPROC3/GPROC3–2 board.
not correct Change the value of the
gproc_slots database parameter
to the correct value and then go
to step 2.
2 Reset the BSP.
The site is reset.

busy-unlocked the fault condition no longer
required.
not busy-unlocked send a field representative to the
site to replace the GPROC board
with a GPROC2 or a {28337}

68P02901W26-S 5-33
Nov 2007
48. BSP: Memory location fault Chapter 5: BSP Alarms
48. BSP: Memory location fault

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm advises of a possible memory location fault. It is not an immediate problem as
the GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
is replaced at an appropriate time.
Possible causes

• A single bit of the memory location is seized.
• Two address lines are cut short.
• Failure within SDRAM.
Procedure
Procedure 5-16 Memory location fault
1 Immediate action is not necessary.

2 Contact the Motorola Local Office and arrange to replace the GPROC board
at an appropriate time.
5-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. BSP: EEPROM SW ash programming failure
50. BSP: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This is a generic flash programming error. A problem has occurred with the operating software.
Possible causes

• The memory is corrupt.
• An incorrect request made by an internal process.
• A static variable could be corrupt.
Procedure
Procedure 5-17 EEPROM SW ash programming failure
If the board does not reset automatically, a manual reset can be performed
to reload the bootrom object.
68P02901W26-S 5-35
Nov 2007
51. BSP: EEPROM HW ash programming failure Chapter 5: BSP Alarms
51. BSP: EEPROM HW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This is a generic flash programming error.
Possible causes
The flash EEPROM device is defective.
Procedure
Procedure 5-18 EEPROM HW ash programming failure
1 This alarm does not take the board out of service.

2 To resolve the alarm, reset the BSP and continue to use until it is possible to
replace the GPROC3 board.
5-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 52. BSP: BSP CPU Safe Overload
52. BSP: BSP CPU Safe Overload

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23306}
Clearing Type: FMIC

Category: Service Quality
Description
The BSS supports this alarm to indicate that the active BSP CPU is working in safe-overload
status and its utilization is over safe-overload threshold (BSP CPU utilization is 70%).
The Additional information field contains 11 bytes in the additional alarm codes.
Byte Denition
One, two The total CPU utilization of BSP
when the overload is detected.
Three, four and five The ids of the top three

processes which have the
highest CPU utilization.
Six, seven, eight, nine, ten The CPU utilization value of
and eleven these three processes.
Possible causes

• The CPU resources are exhausted due to processing of a large number of service requests
for handover and call setup or release.
• Large number of alarms are generated in BSS.
• A software fault in some BSP process causes high CPU utilization.
• Hardware fault.
• This alarm is raised and cleared whenever there is a DB update.
68P02901W26-S 5-37
Nov 2007
Procedure
Procedure 5-19 BSP CPU safe overload
Identify one of the causes for BSP CPU safe overload by using the
content of additional codes.
If... Then...
the highest CPU utilization is check the reason for large number
on Allocation Manager (AM) of service requests and review
and Switch Manager (SM) their network plan.
processes
For other causes, further troubleshooting is required to

identify the underlying cause.
5-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 53. BSP: BSP CPU critical overload
53. BSP: BSP CPU critical overload

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23306}
Clearing Type: FMIC

Description
The BSS supports this alarm to indicate that the active BSP CPU is working in critical-overload
status and its utilization is over critical-overload threshold (95% of BSP CPU is utilized).
The Additional information field contains 11 bytes in the additional alarm codes.
Byte Denition
One, two The total CPU utilization of BSP
when the overload is detected.
Three, four and five The ids of the top three

processes which have the
highest CPU utilization.
Six, seven, eight, nine, ten The CPU utilization value of
and eleven these three processes.
Possible causes

• The CPU resources are exhausted due to processing of a large number of service requests
for handover and call setup or release.
• Large number of alarms are generated in BSS.
• A software fault in some BSP process with priority higher than SM and AM causes high
CPU utilization.
• Hardware fault.
• This alarm is raised and cleared whenever there is a DB update.
68P02901W26-S 5-39
Nov 2007
Procedure
Procedure 5-20 BSP CPU critical overload
Identify one of the causes for a BSP CPU critical overload by using
the content of additional codes.
If... Then...
the highest CPU utilization are the overload control works and
on Allocation Manager (AM) the alarm is cleared when the BSP
and Switch Manager (SM) quits the critical-overload state.
processes
For other causes, further troubleshooting is required to

identify the underlying cause.
5-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 231. BSP: TDM interface conguration failure
231. BSP: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BSP cannot be programmed for a designated timeslot on the TBUS.
System action
The system automatically resets the BSP. If the alarm recurs, the BSP is placed OOS.
Possible causes

• The GPROC board has failed.
• A software error has occurred.
• The GPROC device could not be programmed to the designated timeslot when swapping
the TDM highways.
68P02901W26-S 5-41
Nov 2007
Procedure
Procedure 5-21 TDM interface conguration failure
Determine the state of the BSP.

required.

5-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. BSP: Processor bus communication failure
232. BSP: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSP has lost communication to the peripheral boards through the MCAP bus.
Possible causes

• The front panel switch was set to disable without the GPROC first being reset.
• The part of the BSP that supports the MCAP bus access has failed.
Clearing the alarm
The BSS attempts to clear this alarm automatically, through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
Procedure 5-22 Processor bus communication failure
1 Attempt to bring back the BSP In Service (INS). If the device is back in
service, the alarm condition has ceased and further fault isolation is not
required. If the device remains OOS, go to step 2.
2 Replace the BSP board.
68P02901W26-S 5-43
Nov 2007
239. BSP: Process safe test audit failure Chapter 5: BSP Alarms
239. BSP: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BSP failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes.
The Additional information field includes 9 bytes containing process information, as shown in
Table 5-2. Bytes one to eight are useful only to the programmers. Byte nine is the error code
for the alarm.
Table 5-2 Error codes
Byte Value (Hex) Denition

nine 00 The process that failed the audit is in an infinite loop.
01 The cause for the failure was not determined.
02 Higher priority processes prevented the process that failed
to run.
Ignore any additional bytes displayed.
Possible causes

• The GPROC board is faulty.
• A process running on the BSP failed a safe test audit.
Procedure
5-44 68P02901W26-S
Nov 2007
Procedure 5-23 Process safe test audit failure
1 Determine the error code displayed in the Additional information

field.
If the error code is... Then...
2 Go to step 2.
0, 1, or 3 Go to step 3.
2 Perform the safe test audit on the BSP.
If the BSP... Then...
passes the audit Go to step 4.
fails the audit Contact a Motorola representative
3 Reset the BSP.
The site is reset.

If the BSP... Then...
required.

68P02901W26-S 5-45
Nov 2007
254. BSP: Device failure Chapter 5: BSP Alarms
254. BSP: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSP is taken OOS by the GPROC fault management system. This alarm is FMIC. The alarm
is cleared when the failed BSP goes back to service.
If BSC is configured as bsc_type 1, this alarm is not shown on the OMC event window
upon BSP switchover. In BSS MMI, the alarm 254 can always be seen when BSP
switchover happens no matter bsc_type is 1 or 2.
System action
MCAP failure causes the BSC reset. BSP will switchover, if the redundant BSP is equipped and
unlocked. Otherwise, BSC resets. If BSC resets, alarm 254 is not raised. It is raised only when
BSP switchover happens.
A single byte is displayed in the Additional information field identifying the type of site reset, as
shown in Table 5-3.
5-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes

Table 5-3 Site reset type
Value (Hex) Denition

00 MCAP failure.
01 Communication between the two BSPs is lost. It is caused by former
master BSP (and BSP resets) after BSP switchover occurs.
02 Software bus fault is detected on former master BSP and BSP resets
after BSP switchover happens.
03 A NMI (Non Maskable Interrupt) happens on the former master BSP
and BSP resets after BSP switchover happens.
04 A generic hardware exception happens on the former master BSP and
BSP resets after BSP switchover happens.
05 When EMON command ‘reset’ is issued on former BSP, former BSP
resets after BSP switchover.
Possible causes
• A fault translation by the GPROC fault management system.
• This alarm can occur when the BSP switchover takes place.
Procedure
If the alarm is reported after BSP switchover, wait for the alarm being cleared when the faulty
BSP is reset to go to service by software, after switchover. If the faulty BSP cannot be reset to
go back into service by the software when BSP switchover finishes, try to install the faulty BSP.
This alarm is cleared if the faulty BSP goes back to service. If the failed BSP still cannot go to
service, replace the failed BSP and try bringing the BSP into service.
Wait approximately 10 minutes after this alarm is received to allow the site to reset,
before using this procedure.
68P02901W26-S 5-47
Nov 2007
Procedure 5-24 Device failure
1 Determine the current state of the BSP.

required.
2 Reset the BSP.
The site is reset.

required.

5-48 68P02901W26-S
Nov 2007
Chapter
BSS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details BSS Alarms and includes the following alarm procedures:
• 0. BSS: Last MTL link failure - Signaling point inaccessible on page 6-4.
• 0. BSS: Paging request from MSC protocol error - PM on page 6-7.
• 1. BSS: Call processing failure - MSC detected SCCP down on page 6-8.
• 1. BSS: Routing failure - Syntax error detected - PM on page 6-9.
• 2. BSS: Call processing failure - MSC detected BSSAP down on page 6-10.
• 2. BSS: Routing failure - Reason unknown - PM on page 6-12.
• 3. BSS: Call processing failure - BSS detected BSSAP down on page 6-13.
• 5. BSS: No MSC acknowledgment for circuit block on page 6-15.
• 6. BSS: No MSC acknowledgment for circuit unblock on page 6-17.
• 7. BSS: No MSC acknowledgment for reset circuit on page 6-19.
• 7. BSS: Mobile assignment request from MSC protocol error - PM on page 6-21.
• 8. BSS: Unequipped circuit at the MSC on page 6-23.
• 9. BSS: No MSC acknowledgment for global reset on page 6-25.
• 10. BSS: Erroneous layer 3 message received by the BSS on page 6-26.
• 11. BSS: Confusion message received from the MSC on page 6-27.
• 12. BSS: Unequipped circuit at the BSS on page 6-28.
• 17. BSS: Handover request from the MSC protocol error - PM on page 6-30.
• 18. BSS: Routing failure - Syntax error detected (SMLC) - PM on page 6-31.
• 20. BSS: Paging request from SMLC protocol error- PM on page 6-32.
• 21. BSS: Trunk major threshold exceeded on page 6-33.
• 22. BSS: Trunk critical threshold exceeded on page 6-34.
• 23. BSS: Agent Buffer Space Overflow - Event Logs May Be Incomplete on page 6-35.
• 24. BSS: Agent Buffer Overflow - rlogin Session May Be Incomplete on page 6-36.
• 26. BSS: Received page for invalid cell from MSC on page 6-38.
68P02901W26-S 6-1
Nov 2007
Procedure Chapter 6: BSS Alarms
• 39. BSS: Circuit fault detected on radio channel on page 6-39.
• 40. BSS: Circuit fault cleared on radio channel on page 6-41.
• 42. BSS: Circuit fault cleared on Ater channel on page 6-45.
• 43. BSS: Circuit fault detected on PCM circuit on page 6-47.
• 44. BSS: Circuit fault cleared on PCM circuit on page 6-49.
• 45. BSS: Circuit fault detected on GPRS circuit on page 6-51.
• 46. BSS: Circuit fault cleared on GPRS circuit on page 6-53.
• 47. BSS: Circuit fault detected on PATH channel on page 6-55.
• 48. BSS: Circuit fault cleared on PATH channel on page 6-57.
• 49. BSS: Last LMTL link failure - Signaling point inaccessible on page 6-59.
• 50. BSS: Call processing failure - SMLC detected SCCP down on page 6-62.
• 51. BSS: Call processing failure - SMLC detected BSSAP down on page 6-64.
• 52. BSS: No SMLC acknowledgment for global reset on page 6-66.
• 53. BSS: Erroneous layer 3 message received from SMLC on page 6-67.
• 54. BSS: Confusion message received from the SMLC on page 6-68.
• 55. BSS: Received page for invalid cell from SMLC on page 6-69.
• 59. BSS: Last PCU failed on page 6-71.
• 60. BSS: Circuit fault detected on GPRS circuit on page 6-72.
• 61. BSS: Circuit fault cleared on GPRS circuit on page 6-74.
6-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BSS alarms
Introduction to BSS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base Station
System (BSS) device.
68P02901W26-S 6-3
Nov 2007
0. BSS: Last MTL link failure - Signaling point inaccessible Chapter 6: BSS Alarms
0. BSS: Last MTL link failure - Signaling point

inaccessible
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The signaling point code is inaccessible due to the failure of the last available MTL link. When
this failure occurs, the BSS cannot support calls or send messages to the MSC.
This fault condition is service-affecting.
MTL link conguration
A single MTL link provides a 64 kbps connection between the two pieces of equipment. One or
more MTL links can be configured between the following sites:
• BSC-to-MSC.
• BSC-to-RXCDR-to-MSC.
6-4 68P02901W26-S
Nov 2007
Possible causes

• No signaling route is available to the MSC.
• The circuits are faulty.
• The circuit coaxial cable is faulty.
• The dc power to the MTL is lost.
• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) frames causing the
link failure.
• The remote congestion timer expired causing the link failure.
• The MSU acknowledgment timer expired causing the link failure.
• The sequence numbers are not synchronized causing the failure.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive error rate that caused
the failure.
Procedure
Procedure 6-1 Last MTL link failure - Signaling point inaccessible
1 Determine if all MTL devices are OOS.

If all MTL devices... Then...
are OOS Go to step 2.
are not OOS Go to step 3.
2 Determine if the MSC or RXCDR are rebooting.
If... Then...
the MSC is rebooting Wait until the MSC reboot is
finished and then go to step 3.
the RXCDR is rebooting Wait until the RXCDR reboot is
neither the MSC or RXCDR are Go to step 4.
rebooting
Continued
68P02901W26-S 6-5
Nov 2007
Procedure 6-1 Last MTL link failure - Signaling point inaccessible (Continued)
3 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the MTLs
and take the appropriate action to
return all MTLs to service.
not cleared The fault is probably at the MSC.
Troubleshoot the MSC fault.
and take the appropriate action to
not cleared Go to step 5.
5 Attempt to return one of the MTLs to service.
If one of the MTLs... Then...
returns to service Go to step 6.
does not return to service Send a field representative to the
site to determine the cause of the
and take appropriate action to
not cleared Send a field representative to the

6-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. BSS: Paging request from MSC protocol error - PM
0. BSS: Paging request from MSC protocol error - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PAGE_REQ_FROM_MSC_FAIl statistic threshold has been reached.
This statistic tracks the number of page request messages received from the MSC that fail
message validation. Validation failures occur due to protocol errors, which occurs if the message
is incorrectly formatted. A protocol error does not indicate paging success or failure.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Possible causes
The MSC experienced a protocol error.
Procedure
Procedure 6-2 Paging request from MSC protocol error - PM
1 Initiate fault isolation and resolution procedures at the MSC.

2 Clear the alarm after the fault at the MSC is resolved.
68P02901W26-S 6-7
Nov 2007
1. BSS: Call processing failure - MSC detected SCCP down Chapter 6: BSS Alarms
1. BSS: Call processing failure - MSC detected SCCP

down
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BSS received a User Part Unavailable (UPU) message from the MSC indicating that the
Signaling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the
BSS cannot support calls.
When the SCCP is down, the MSC does not accept SCCP messages from the BSS. This SSCP
failure occurs at the MSC.
Possible causes
The BSS received a UPU message from the MSC indicating that the SCCP is unavailable.
Procedure
Procedure 6-3 Call processing failure - MSC detected SCCP down

2 Clear the alarm.
6-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. BSS: Routing failure - Syntax error detected - PM
1. BSS: Routing failure - Syntax error detected - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The ROUTING_SYNTAX statistic threshold has been reached.
This statistic tracks the number of SCCP messages with syntax errors. SCCP is an SS7 protocol
used in transferring signaling messages between the BSC and MSC. Excessive syntax errors
can result in degraded SCCP performance.
Possible causes
The SCCP message had a syntax error.
Procedure
Procedure 6-4 Routing failure - Syntax error detected - PM

68P02901W26-S 6-9
Nov 2007
2. BSS: Call processing failure - MSC detected BSSAP down Chapter 6: BSS Alarms
2. BSS: Call processing failure - MSC detected BSSAP

down
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BSS received a Subsystem Prohibited (SSP) message from the MSC indicating that the
BSS Application Part (BSSAP) is down (unavailable). When this condition exists, the BSS
cannot support calls.
When the BSSAP is down, the MSC does not accept BSSAP messages from the BSS. This BSSAP
failure occurs at the MSC.
Possible causes
The BSS receives an SSP message from the MSC indicating that the BSSAP is unavailable.
6-10 68P02901W26-S
Nov 2007
Procedure
Procedure 6-5 Call processing failure - MSC detected BSSAP down

2 Clear the alarm.
68P02901W26-S 6-11
Nov 2007
2. BSS: Routing failure - Reason unknown - PM Chapter 6: BSS Alarms
2. BSS: Routing failure - Reason unknown - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The ROUTING_UNKNOWN statistic threshold has been reached.
This statistic tracks the number of invalid Signaling Point Codes (SPCs) that a BSC has received
from the MSC. An SPC is the destination address for a message routed by the networking
functions of the MTP3 protocol. If the BSC receives an incorrect SPC, it is not able to route
the message correctly.
Possible causes

• The system is not capable of translating an SPC address.
• This specific SPC address is not recognizable by the translation process.
Procedure
Procedure 6-6 Routing failure - Reason unknown - PM

6-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. BSS: Call processing failure - BSS detected BSSAP down
3. BSS: Call processing failure - BSS detected BSSAP

down
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The local BSS Application Part (BSSAP) is down (unavailable) due to the last cell at the BSS
going OOS. When this condition exists, the BSS cannot support calls.
When the BSSAP is down, the BSS does not accept BSSAP messages from the MSC. This BSSAP
failure is at the BSS.
Possible causes
All cells in the BSS are OOS.
68P02901W26-S 6-13
Nov 2007
Procedure
Procedure 6-7 Call processing failure - BSS detected BSSAP down
1 Determine the state of the cells at the site.

If... Then...
any of the cells are The fault condition that caused this
busy-unlocked alarm no longer exists. Initiate fault
isolation and resolution procedures
for any cells and DRIs that are OOS.
not all of the cells are Go to step 2.
busy-unlocked
2 Determine the state of the DRIs at the site.
If... Then...
any of the DRIs are The fault condition that caused this
busy-unlocked alarm no longer exists. Initiate fault
isolation and resolution procedures
for any cells and DRIs that are OOS.
not all of the DRIs are Initiate fault isolation and
busy-unlocked resolution procedures for
any DRIs that are OOS.
When a single DRI is returned
to service, the fault condition
that caused this alarm no longer
exists. Continue fault isolation and
resolution procedures for any cells
and DRIs that are OOS.
6-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. BSS: No MSC acknowledgment for circuit block
5. BSS: No MSC acknowledgment for circuit block

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS has repeated the circuit block message the maximum number of times without
receiving any acknowledgment from the MSC.
When the BSS sends a circuit block message to the MSC, the BSS expects to receive an
acknowledgment message from the MSC. If an acknowledgment message is not received, the
BSS retransmits the circuit block message. This transmission is repeated until the BSS receives
an acknowledgment message or the maximum number of retransmissions is reached.
The content of the Additional information field is dependent upon the value assigned to the
group_block_unblock_allowed parameter. Table 6-1 specifies the content for the zero value.
Table 6-1 If group_block_unblock_allowed = 0
Byte Value Denition

first 01 The element identifier of the first (or only)
blocked terrestrial circuit.
second and third 00 to FF The CIC of the first (or only) blocked terrestrial
and circuit where the CIC is represented by 2
00 to FF bytes. (For example, 00 A2).
group_block_unblock_allowed parameter. Table 6-2 specifies the content for the non-zero
value.
68P02901W26-S 6-15
Nov 2007
Possible causes Chapter 6: BSS Alarms

first 01 The element identifier of the first (or only)
blocked terrestrial circuit.
second and third 00 to FF The CIC of the first (or only) blocked terrestrial
and circuit where the CIC is represented by 2
00 to FF bytes. (For example, 00 A2).
fourth 1E If there is more than one blocked terrestrial
circuit, this byte is set to 1E.
fifth 00 to FF The total number of bytes included in the
Additional information field.
sixth 00 to FF The range of CICs in the list. The range is the
difference between the lowest CIC number and
the highest CIC number.
seventh and eighth to a 00 to FF The CICs of the blocked terrestrial circuits,
maximum of 256 CICs and where each is represented by 2 bytes. (For
00 to FF example, 00 A3, 00 A4).
Possible causes
The MSC does not recognize the circuit.
Procedure
Procedure 6-8 No MSC acknowledgment for circuit block
Clear the alarm.
6-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. BSS: No MSC acknowledgment for circuit unblock
6. BSS: No MSC acknowledgment for circuit unblock

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS has repeated the circuit unblock message the maximum number of times without
receiving any acknowledgment from the MSC.
When the BSS sends a circuit unblock message to the MSC, the BSS expects to receive an
acknowledgment message from the MSC. If an acknowledgment message is not received, the
BSS retransmits the circuit unblock message. This transmission is repeated until the BSS
receives an acknowledgment message or the maximum number of retransmissions is reached.
group_block_unblock_allowed parameter. Table 6-3 specifies the content for the zero value.

first 01 The element identifier of
the first (or only) unblocked
terrestrial circuit.
second and third 00 to FF The CIC of the first (or only)
and unblocked terrestrial circuit
00 to FF where the CIC is represented
by 2 bytes. (For example, 00
A2).
group_block_unblock_allowed parameter. Table 6-4 specifies the content for the non-zero
value.
68P02901W26-S 6-17
Nov 2007

first 01 The element identifier of
the first (or only) unblocked
second and third 00 to FF The CIC of the first (or only)
and unblocked terrestrial circuit
00 to FF where the CIC is represented
by 2 bytes. (For example, 00
A2).
fourth 1E If there is more than one
unblocked terrestrial circuit,
this byte is set to 1E.
fifth 00 to FF The total number of bytes
included in the Additional
information field.
sixth 00 to FF The range of CICs in the list.
The range is the difference
between the lowest CIC
number and the highest CIC
number.
seventh and eighth to a 00 to FF The CICs of the unblocked
maximum of 256 CICs and terrestrial circuits, where
00 to FF each is represented by 2
bytes. (For example, 00 A3,
00 A4).
Possible causes
Procedure
Procedure 6-9 No MSC acknowledgment for circuit unblock
Clear the alarm.
6-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. BSS: No MSC acknowledgment for reset circuit
7. BSS: No MSC acknowledgment for reset circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS has repeated the circuit unblock message the maximum number of times without
receiving any acknowledgment from the MSC. The parameter max_rst_ckt_timer_exp defines
the maximum number of times the message is repeated.
Refer to the manual, Technical Description: BSS Command Reference (68P02901W23)

for a description of max_rst_ckt_timer_exp parameter.
The contents of the Additional information field are shown in Table 6-5.
Table 6-5 Additional information eld contents

first 00 to FF The element identifier of the
terrestrial circuit that was
reset.
second and third 00 to FF The Circuit Identity Code
and (CIC) of the first (or
00 to FF only) terrestrial circuit is
represented by 2 bytes.
(For example, 00 A2).
The CIC uniquely identifies
each terrestrial circuit
existing between the MSC
and the BSS. The CIC is the
logical identifier (ID) for the
68P02901W26-S 6-19
Nov 2007
Possible causes
Procedure
Procedure 6-10 No MSC acknowledgment for reset circuit
Clear the alarm.
6-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. BSS: Mobile assignment request from MSC protocol error - PM
7. BSS: Mobile assignment request from MSC protocol

error - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MA_REQ_FROM_MSC_FAIL statistic threshold has been reached.
This statistic tracks the number of assignment request messages received from the MSC that
fail message validation.
Possible causes

• Incompatible database elements exist in the BSS and MSC.
• Assignment Request messages received from the MSC are incorrectly formatted.
68P02901W26-S 6-21
Nov 2007
Procedure
Procedure 6-11 Mobile assignment request from MSC protocol error - PM
1 Determine if there are incompatible database elements in the BSS

and MSC.
If there are... Then...
no incompatible database Go to step 2.
elements
incompatible database elements Make the appropriate
database corrections.
After the corrections are made,
clear the alarm.
2 Initiate procedures at the MSC to correct the Assignment Request
message format. After correcting the format, clear the alarm.
6-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. BSS: Unequipped circuit at the MSC
8. BSS: Unequipped circuit at the MSC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS had sent a message to the MSC with an invalid terrestrial circuit identifier. The MSC
responded to the BSS with the Unequipped Circuit Message for that terrestrial circuit.

identified as unequipped.
and (CIC) of the terrestrial
00 to FF circuit is represented by 2
bytes. (For example, 00 A2).
68P02901W26-S 6-23
Nov 2007
Possible causes

• The terrestrial circuit is not equipped at the MSC.
• The MSC and BSS database shows a different device state for the same terrestrial circuit.
Procedure
Procedure 6-12 Unequipped circuit at the MSC
1 Determine if the terrestrial circuit is equipped in the BSS and then

go to step 2.
2 Determine if the terrestrial circuit should be equipped.
If the circuit should... Then...
be equipped Equip the circuit at the MSC.
After equipping the circuit at the
MSC, clear the alarm.
not be equipped Unequip the circuit from the BSS.
After the circuit is unequipped at
the BSS, clear the alarm.
6-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. BSS: No MSC acknowledgment for global reset
9. BSS: No MSC acknowledgment for global reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS repeated the global reset message the maximum number of times without receiving
an acknowledgment from the MSC.
Possible causes
The MSC did not acknowledge the global reset message.
Procedure
Procedure 6-13 No MSC acknowledgment for global reset
Clear the alarm.
68P02901W26-S 6-25
Nov 2007
10. BSS: Erroneous layer 3 message received by the BSS Chapter 6: BSS Alarms
10. BSS: Erroneous layer 3 message received by the

BSS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS received an erroneous layer 3 message from the MSC and the MSC does not support
such message.
The Additional information field displays the erroneous layer 3 message that the BSS receives
(from the MSC).
Possible causes
The MSC sent an erroneous layer 3 message.
Procedure
Procedure 6-14 Erroneous layer 3 message received by the BSS
Clear the alarm.
6-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. BSS: Confusion message received from the MSC
11. BSS: Confusion message received from the MSC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS receives a confusion message from the MSC.
The Additional information field displays the confusion message that the BSS receives from
the MSC.
Possible causes
The MSC did not understand a layer 3 message from the BSS.
Procedure
Procedure 6-15 Confusion message received from the MSC
Clear the alarm.
68P02901W26-S 6-27
Nov 2007
12. BSS: Unequipped circuit at the BSS Chapter 6: BSS Alarms
12. BSS: Unequipped circuit at the BSS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS received a message from the MSC that contains an unknown circuit and the MSC does
not support the unequipped circuit message.
This alarm indicates that a Base Station System (BSS) received a message from the Mobile
Switching Centre (MSC) containing an invalid terrestrial circuit identifier. The BSS responded
to the MSC with the Unequipped Circuit Message for that terrestrial circuit.
This alarm is generated because the database does not properly reconcile the device states.
Each database (MSC and BSS) shows a different device state for the identical terrestrial
circuit device.
The terrestrial circuit (ID) specified continues to be invalid while it remains in an

UNEQUIPPED device state.
The Additional information field contents are shown in Table 6-7. This information is displayed
for the unequipped terrestrial circuit. Ignore any additional bytes displayed.
6-28 68P02901W26-S
Nov 2007

identified as unequipped.
and (CIC) of the terrestrial
00 to FF circuit is represented by 2
bytes. (For example, 00 A2).
Possible causes

• The terrestrial circuit is not equipped at the MSC.
• The MSC and BSS databases shows a different device state for the same terrestrial circuit.
Procedure
Procedure 6-16 Unequipped circuit at the BSS
1 Determine if the terrestrial circuit is equipped in the BSS, then go to

step 2.
2 Determine if the terrestrial circuit should be equipped.
If the circuit should... Then...
be equipped Equip the circuit at the BSS.
After equipping the circuit at the
BSS, clear the alarm.
not be equipped Unequip the circuit from the MSC.
After the circuit is unequipped at
the MSC, clear the alarm.
68P02901W26-S 6-29
Nov 2007
17. BSS: Handover request from the MSC protocol error - PM Chapter 6: BSS Alarms
17. BSS: Handover request from the MSC protocol error

- PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The HO_REQ_MSC_PROTO statistic threshold has been reached.
This statistic tracks the number of Handover Request messages received from the MSC that fail
message validation. Validation failure results due to protocol errors that occur if the message is
badly formatted or incompatible database elements exist in the BSS and MSC.
Possible causes

• The MSC experienced a protocol error.
• Incompatible database elements exist in the BSS and MSC.
Procedure
Procedure 6-17 Handover request from the MSC protocol error - PM

6-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 18. BSS: Routing failure - Syntax error detected (SMLC) - PM
18. BSS: Routing failure - Syntax error detected (SMLC)

- PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm relates to the Lb-interface, but in all other respects is identical to the BSS 1 alarm.
See 1. BSS: Routing Failure - Syntax Error Detected - PM.
The BSS reports a BSS Routing Failure - Syntax Error Detected (SMLC) - PM alarm when
the L_ROUTING_SYNTAX counter exceeds the specified threshold.
The L_ROUTING_SYNTAX statistic threshold has been reached.
This statistic tracks the number of Lb-interface SCCP messages with syntax errors. Lb-interface
SCCP is an SS7 protocol used in transferring signaling messages between the BSC and SMLC.
Excessive syntax errors can result in degraded Lb-interface SCCP performance.
Possible causes
The Lb-interface SCCP message had a syntax error.
Procedure
Procedure 6-18 Routing failure - Syntax error detected (SMLC) - PM
1 Initiate fault isolation and resolution procedures at the BSS-based SMLC.

2 Clear the alarm after the fault at the BSS-based SMLC is resolved.
68P02901W26-S 6-31
Nov 2007
20. BSS: Paging request from SMLC protocol error- PM Chapter 6: BSS Alarms
20. BSS: Paging request from SMLC protocol error- PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm relates to the Lb-interface, but in all other respects is identical to the BSS 0 alarm.
See 0. BSS: Paging Request from MSC Protocol Error - PM.
The BSS reports a BSS Paging Request from SMLC Protocol Error - PM alarm when the
PAGE_REQ_FROM_SMLC_FAIL counter exceeds the specified threshold.
The PAGE_REQ_FROM_SMLC_FAIL statistic threshold has been reached.
This statistic tracks the number of Page Request messages received from the BSS-based SMLC
that fail message validation. Validation failures occur due to protocol errors, which occur if the
message is incorrectly formatted. A protocol error does not indicate paging success or failure.
Possible causes
The SMLC experienced a protocol error.
Procedure
Procedure 6-19 Paging request from SMLC protocol error- PM
1 Initiate fault isolation and resolution procedures at the BSS-based SMLC.

2 Clear the alarm after the fault at the BSS-based SMLC is resolved.
6-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. BSS: Trunk major threshold exceeded
21. BSS: Trunk major threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the percentage of trunk capacity has exceeded the user-specified value
of the trunk_major_threshold database parameter.
For further information, refer to the BSS statistics chapter in the manual, Technical Description:
BSS Command Reference (68P02901W23).
Possible causes

• The percentage of utilized trunks is greater than the value of trunk_major_threshold
database parameter.
• The value of the trunk_major_threshold database parameter is set too low.

Procedure
Procedure 6-20 Trunk major threshold exceeded
1 Review the Alarms window to identify the current CIC and RCI
alarms.
2 Initiate fault isolation and fault resolution procedures to restore
the failed circuits.
68P02901W26-S 6-33
Nov 2007
22. BSS: Trunk critical threshold exceeded Chapter 6: BSS Alarms
22. BSS: Trunk critical threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the percentage of trunk capacity has exceeded the user-specified value
of the trunk_critical_threshold database parameter.
For further information, refer to the BSS statistics chapter in the manual, Technical Description:
BSS Command Reference (68P02901W23).
Possible causes

• The percentage of utilized trunks is greater than the value of trunk_critical_threshold
database parameter.
• The value of the trunk_critical_threshold database parameter is set too low.

Procedure
Procedure 6-21 Trunk critical threshold exceeded
1 Review the Alarms window to identify the current CIC and RCI
alarms.
2 Initiate fault isolation and fault resolution procedures to restore the
failed circuits.
6-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. BSS:
Agent Buffer Space Overow - Event Logs May Be Incomplete
23. BSS: Agent Buffer Space Overow - Event Logs May

Be Incomplete
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm indicates that there is no BSS Agent buffer space available. Event Log messages
(alarms, state changes, and other events) have been received, but cannot be stored. After the
buffer is full, the most recent messages are discarded. When active event messages are sent,
the related output sent to the OMC may be incomplete while this fault condition exists.
This alarm can be generated for any type of hardware.
There is no additional information for this alarm.
Possible causes
The following are the possible reasons for this error:

• One or more devices in a BSS are cycling in and out of service, generating excessive
alarm output.
• One or more devices in a BSS are generating continuous alarm output and device state
change messages.
Procedure
The operator must identify the devices that are generating the alarms or state changes that are
causing the event message overflow.
68P02901W26-S 6-35
Nov 2007
24. BSS: Agent Buffer Overow - rlogin Session May Be Incomplete Chapter 6: BSS Alarms
24. BSS: Agent Buffer Overow - rlogin Session May

Be Incomplete
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that there is no more BSS Agent buffer space available. A rlogin message or
data has been received, but cannot be stored. Until the fault condition is resolved, subsequent
rlogin message or data is stored at the Agent if space is available. When active messages or
data are sent from a rlogin session that is in progress, the related output sent to the BSC is
incomplete while this fault condition exists.
This alarm can be generated for any type of hardware.
Additional information
Possible causes

• One or more rlogin sessions to a BSC are generating excessive output from BSS MMI
commands. (For example, disp_bss).
• One or more rlogin sessions to a BSC are generating excessive output through transfer of
information through software filters.
• One or more rlogin sessions to a BSC are generating excessive output through transfer of
information through software IIRs.
6-36 68P02901W26-S
Nov 2007
Procedure
The BSS clears the alarm automatically through a Fault Management Initiated Clear (FMIC)
after 50% of the contents of the rlogin buffer in the Agent are cleared.
Operators must stop the output-intensive filters and/or IIRs if any are set, or provide more
specific parameters to the output-intensive commands, to limit the amount of text output they
generate.
68P02901W26-S 6-37
Nov 2007
26. BSS: Received page for invalid cell from MSC Chapter 6: BSS Alarms
26. BSS: Received page for invalid cell from MSC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The MSC has sent a paging message to a nonexistent cell in the BSS.
Table 6-8 shows the Additional information field values.
Table 6-8 Additional information eld values

first second third fourth fifth 00 to FF00 to FF00 to FF00 The 8 byte ID of the invalid
sixth seventh eighth to FF00 to FF00 to FF00 to cell.
FF00 to FF
Ignore any additional bytes displayed. The cell ID can be derived from the displayed fields by
using the mmi_cell_id_format command. Refer to the Technical Description: BSS Command
Reference (68P02901W23) manual.
Possible causes
The MSC and BSS databases do not have matching cell ID lists.
Procedure
Procedure 6-22 Received page for invalid cell from MSC
Reconcile the differences in the MSC and BSS databases.
6-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. BSS: Circuit fault detected on radio channel
39. BSS: Circuit fault detected on radio channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular Radio Channel Identifier (RCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the RCI error generation threshold, meaning
thereby, that a device in the RCI path could be faulty and need replacing. None of the devices in
the RCI path for the faulty RCI is taken Out Of Service (OOS) due to this alarm, which simply
reports the devices contained in the RCI path.
Alarm throttling is not allowed for this alarm. The OMC-R is notified when an RCI Fault
notification message has been sent to the alarms subsystem. The OMC-R receives a Faulty
RCI set intermittent alarm and the path information as described in the following additional
alarm data section.
The OMC-R uses each RCI Fault intermittent alarm to keep track of which RCIs have alarms on
them. The BSS alarm subsystem does not keep track of the RCIs that have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all
the RCIs for which the BSS has sent intermittent alarms (the BSS keeps track of which RCIs
have had alarms sent).
The OMC-R receives the RCI list in the additional alarm data field of one or more RCI Fault
intermittent alarms. The OMC-R knows it has received the entire list of RCIs when the OMC-R
receives the Generic Result message from the BSS. Any RCI alarms, which the OMC-R shows as
active alarms that are not in the resync list, are changed to the cleared state.
Any new alarms in the list that the OMC-R does not show as active, require no immediate action
since the BSS reissues these alarms later. When the RCI Fault intermittent alarm is being used
for resync, the Report Type of the alarm is resync alarm.
Additional Information
The message Faulty RCI Alarm Set includes the following RCI related information: RCI, Site,
Channel Coder Unit (CCU) device and CCU timeslot upon which the RCI exists.
The RCI information is presented in an understandable customer format.
An example of a format for the RCI when remote transcoding is as follows:
RCI Fault for RCI 1 2 3 4

BTS Site 2
DRI ID 0 3 0
DRI Timeslot 4
68P02901W26-S 6-39
Nov 2007
Possible causes
A device in the RCI path is faulty and in need of replacement.
Procedure
Procedure 6-23 Circuit fault detected on radio channel
1 Check the status of the devices in the RCI path. If there are additional
Faulty RCI Alarms for RCIs using the same path, one or more of the devices
in the path is probably faulty and should be replaced. Use the information
contained in the alarm report to determine which device needs replacement.
2 Send a field representative to the site to replace the faulty device.

6-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 40. BSS: Circuit fault cleared on radio channel
40. BSS: Circuit fault cleared on radio channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BSS sends a Faulty Radio Channel Identifier (RCI) Alarm Clear message to the OMC-R when
the error count on the RCI reaches or goes below the specified threshold and the alarm is
currently set. This message indicates that:
• The failure condition causing TRAU frames to be lost has cleared for the Radio Channel
Interface in the alarm clear message.
• The Radio Channel Interface alarms are to be cleared due to the Call Processing global
reset.
• Relevant RCI alarms are to be cleared due to the PCU OOS case.
For the non-Call Processing global reset case and the non-PCU OOS case, the additional data
contains the Radio Channel Interface path information, which includes the Additional Data
Identifier (1 byte) and the Radio Channel Interface (4 bytes). For the Call Processing reset case,
the additional data contains the Additional Data Indicator (1 byte), Field length (2 bytes) and a
list of circuits to notify the OMC that the Call Processing global reset has occurred and a CLEAR
should be initiated. For the PCU OOS case, the additional data contains the Additional Data
Indicator (1 byte), Field length (2 bytes) and a list of circuits to notify the OMC that the PCU
is OOS and a CLEAR should occur.
Possible causes
The associated failure condition has cleared.
68P02901W26-S 6-41
Nov 2007
Procedure
Procedure 6-24 Circuit fault cleared on radio channel
1 The intermittent alarm message indicates that a prior fault has been cleared;
so, no action is normally required. If there is a trend where an RCI toggles
between being faulty and cleared, action is required to identify and replace
the relevant device.
2 Use the information contained in the Alarm report to determine which
device is to be replaced.
6-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41. BSS: Circuit fault detected on Ater channel
41. BSS: Circuit fault detected on Ater channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular Ater Channel Identifier (ACI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the ACI error generation threshold, indicating
that a device in the ACI path is faulty and in need of replacement. None of the devices in the
ACI path for the faulty AC is taken Out Of Service (OOS) due to this alarm, which reports the
devices contained in the ACI path. Alarm throttling is not allowed for this alarm.
The OMC-R is notified when an ACI Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty ACI set intermittent alarm and the path information
as described in the following additional alarm data section. The OMC-R uses each ACI Fault
intermittent alarm to keep track of the ACIs that have alarms on them. The BSS alarm
subsystem does not keep track of the ACIs that have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all the
ACIs for which the BSS has sent intermittent alarms. The OMC-R receives the ACI list in the
additional alarm data field of one or more ACI Fault intermittent alarms. The OMC-R knows
it has received the entire list of ACIs when the OMC-R receives the Result message from the
BSS. Any ACI alarms which the OMC-R shows as active alarms, that are not in the resync
list, are changed to the cleared state. If there are any new alarms in the list that the OMC-R
does not show as active, no immediate action is required, since the BSS reissues these alarms
later. When the ACI Fault intermittent alarm is being used for resync, the Report Type of
the alarm is resync alarm.
The message Faulty ACI Alarm Set includes the following ACI path information:
• ACI.
• BSC-MMS device, timeslot, and group upon which the ACI exists.
The ACI information is printed out in an understandable customer format.
An example of a format for the ACI is as follows:
ACI Fault for ACI 0x01 0xfb

BSC-MMS Device 0 1 0
Timeslot: 31
Group: 3
68P02901W26-S 6-43
Nov 2007
Possible causes
One or more devices in the ACI path are faulty and in need of replacement.
Procedure
Procedure 6-25 Circuit fault detected on Ater channel
1 If there are multiple ACIs in a path that have Faulty ACI Alarms active, one
of the devices in the path is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine which device is
to be replaced.
2 Send a field representative to the site to replace the relevant device.

6-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 42. BSS: Circuit fault cleared on Ater channel
42. BSS: Circuit fault cleared on Ater channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular Ater Channel Identifiers (ACI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or gone below the ACI error clear threshold, meaning thereby,
that a device in the ACI path is no longer faulty.
The OMC-R is notified any time that an ACI Clear notification message has been sent to the
alarms subsystem. The OMC-R receives a Faulty ACI clear intermittent alarm containing the
ACI, which is being cleared. The OMC-R uses each ACI Fault Clear intermittent alarm to clear
the Faulty ACI alarm on the ACI given in the alarm.
When the OMC-R receives a Faulty ACI clear intermittent alarm, it changes the displayed state
of the alarm for the ACI in the intermittent alarm to cleared. This scheme produces an FMIC
type functionality using intermittent alarms at the OMC-R and not at the BSS.
Memory limitations prevent the BSS from implementing FMIC alarms for every ACI. When the
OMC-R receives an ACI Fault Clear intermittent alarm that has an ADI indicating Global Reset,
the OMC-R clears all of the ACI CERM alarms.
The message Faulty ACI Alarm Clear includes the ACI.
Possible causes
The failure causing TRAU Frame errors has cleared.
68P02901W26-S 6-45
Nov 2007
Procedure
Procedure 6-26 Circuit fault cleared on Ater channel
1 No action is normally required, because this intermittent alarm message

indicates that a prior fault has been cleared. If there is a trend where an
ACI toggles between faulty and cleared, action is required to identify and
replace the relevant device. Use the information contained in the Alarm
report to determine which device is to be replaced.

6-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 43. BSS: Circuit fault detected on PCM circuit
43. BSS: Circuit fault detected on PCM circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular Circuit Identity Code (CIC) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the CIC error generation threshold, indicating
that a device in the CIC path is faulty and need replacing. None of the devices in the CIC
path for the faulty CIC are taken Out Of Service (OOS) due to this alarm, which reports the
devices contained in the CIC path.
Alarm throttling is not allowed for this alarm. The OMC-R is notified when a CIC Fault
notification message has been sent to the alarms subsystem. The OMC-R receives a Faulty
CIC set intermittent alarm and the path information as described in the following additional
alarm data section.
The OMC-R uses each CIC Fault intermittent alarm to keep track of which CICs have alarms on
them. The BSS alarm subsystem does not keep track of which CICs have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all the
CICs for which the BSS has sent intermittent alarms (the BSS keeps track of the CICs that have
had alarms sent to them). The OMC-R receives the CIC list in the additional alarm data field of
one or more CIC Fault intermittent alarms. The OMC-R knows that it has received the entire list
of CICs when the OMC-R receives the Generic Result message from the BSS.
Any CIC alarms which the OMC-R shows as active alarms that are not in the resync list is
changed to the cleared state. If there are any new alarms in the list that the OMC-R does not
show as active, no immediate action is required, since the BSS reissues these alarms later.
When the CIC Fault intermittent alarm is used for resync, the Report Type of the alarm is
resync alarm.
The message Faulty CIC Alarm Set includes the CIC when remote transcoding is used. The
message Faulty CIC Alarm Set includes: CIC, XCDR board ID, and XCDR DSP information when
local transcoding is used.
The CIC information is printed out in a format which is described in the relevant area of the BSS
Field Troubleshooting Manual (68P02901W51) for this alarm. An example of a format for the
CIC when remote transcoding is as follows:
CIC Fault for CIC 1 0
68P02901W26-S 6-47
Nov 2007
An example of a format for the CIC when local transcoding is as follows:
CIC Fault for CIC 1 0

XCDR ID 3 1 0
XCDR DSP 3
Possible causes
One of the devices in the CIC path is faulty and is in need of replacement.
Procedure
Procedure 6-27 Circuit fault detected on PCM circuit
1 If there are multiple CICs in a path that have Faulty CIC Alarms active, one
of the devices in the path is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine which device is
to be replaced.

6-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 44. BSS: Circuit fault cleared on PCM circuit
44. BSS: Circuit fault cleared on PCM circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular CIC TRAU frame synchronization loss error count has reached or gone below the
CIC error clear threshold. This means that a previously alarmed device in the CIC path is no
longer faulty. This alarm report is also used in the Call Processing global reset.
For the non-Call Processing global reset case, the additional data contains the CIC path
information, which includes the ADI (1 byte) and the CIC (2 bytes). For the Call Processing
global reset case, the additional data contains the Additional Data Identifier (1 byte) to notify
the OMC that a Call Processing global reset has occurred and a CLEAR should be initiated.
Possible causes
The failure causing TRAU Frame errors has cleared. Alternatively, the CIC alarms should
be cleared by Call Processing global reset.
68P02901W26-S 6-49
Nov 2007
Procedure
Procedure 6-28 Circuit fault cleared on PCM circuit

indicates that a prior fault has been cleared. If there is a trend where a CIC
toggles between being faulty and cleared, action may be required to identify
and replace the relevant device. Use the information contained in the Alarm
report to determine which device requires to be replaced.

6-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 45. BSS: Circuit fault detected on GPRS circuit
45. BSS: Circuit fault detected on GPRS circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular GPRS Circuit Identifier (GCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the GCI error generation threshold, meaning
that a device in the GCI route to the PCU is faulty and in need of replacement. None of the
devices in the GCI path to the PCU for the faulty GCI are taken OOS due to this alarm, which
simply reports the devices contained in the GCI path that is alarming. Alarm throttling is not
allowed for the Faulty GCI Alarm Set alarm.
The OMC-R is notified when a GCI Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty GCI set intermittent alarm and additional GCI
information as described in the following additional alarm data section.
The OMC-R uses each GCI Fault intermittent alarm to keep track of the GCIs that have alarms
on them. The BSS alarm subsystem does not keep track of which GCIs have active alarms on
them. Whenever the OMC-R performs an alarm resynchronization, the OMC receives a list of
all the GCIs for which the BSS has sent intermittent alarms (the BSS keeps track of the GCIs
that have had alarms sent to them).
The OMC-R receives the GCI list in the additional alarm data field of one or more GCI Fault
intermittent alarms. The OMC-R knows that it has received the entire list of GCIs when the
OMC receives the Result message from the BSS. Any GCI alarms which the OMC-R show as
active alarms that are not in the resync list are changed to the cleared state. If there are any
new alarms in the list that the OMC-R does not show as active, no immediate action is required
since the BSS reissues these alarms later. When the GCI Fault at Remote BTS intermittent alarm
is being used for resync, the Report Type of the alarm is resync alarm.
The Additional information field includes the following GCI path information: GCI, BSC-MSI
device, BSC-MMS device, timeslot, and group upon which the GCI exists, PCU MSI and MMS
device.
The GCI information is printed out in an understandable customer format.
An example of a format for the GCI is as follows:
GCI Fault for GCI 3 1 4 1

BSC MMS 3 1 0
Timeslot 4
Group 1
PCU MMS 7 0 0
68P02901W26-S 6-51
Nov 2007
Possible causes
One of the devices in the GCI path to the PCU is faulty and is in need of replacement.
Procedure
Procedure 6-29 Circuit fault detected on GPRS circuit
1 If there are multiple GCIs using the same devices that have Faulty GCI
Alarms active, one of the devices is probably faulty and is in need of
replacement. Use the information, contained in the Alarm report produced
at the OMC-R, to determine which device requires replacement.

6-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 46. BSS: Circuit fault cleared on GPRS circuit
46. BSS: Circuit fault cleared on GPRS circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A particular GPRS Circuit Identifiers (GCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or gone below the GCI error clear threshold meaning thereby
that a device in the GCI path is no longer faulty. This alarm is an intermittent alarm sent to
the OMC-R and MMI.
The OMC-R is notified when a GCI Clear notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty GCI clear intermittent alarm containing the GCI,
which is being cleared. The OMC-R uses each GCI Fault Clear intermittent alarm to clear the
Faulty GCI alarm on the GCI given in the alarm.
When the OMC-R receives a Faulty GCI clear intermittent alarm, it changes the alarm for
the GCI in the intermittent alarm to cleared state. This scheme produces an FMIC type
functionality using intermittent alarms at the OMC-R and not at the BSS. Memory limitations at
the BSS prevent implementation of FMIC alarms for every GCI.
The message Faulty GCI Alarm Clear includes the GCI.
Possible causes
The failure causing TRAU frame errors have cleared for the GCI in the alarm clear message.
68P02901W26-S 6-53
Nov 2007
Procedure
Procedure 6-30 Circuit fault cleared on GPRS circuit

indicates that a prior fault has been cleared. If there is a trend where a GCI
toggles between being faulty and cleared, action is required to identify and
report to determine which device is to be replaced.

6-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 47. BSS: Circuit fault detected on PATH channel
47. BSS: Circuit fault detected on PATH channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The count of errors for a particular PIC TRAU frame sync loss has reached or exceeded the PIC
error generation threshold. This alarm indicates that a device in the PIC path is faulty and needs
replacement. None of the devices in the PIC path for the faulty PIC are taken Out Of Service
(OOS) due to this alarm, which simply reports the devices contained in the PIC path that are
responsible for the alarm. Alarm throttling is not allowed for the Faulty PIC Alarm Set alarm.
The OMC-R is notified any time that a PIC Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty PIC set intermittent alarm and the path information as
described in the additional alarm data section. The OMC-R uses each PIC Fault intermittent
alarm to keep track of the PICs which have alarms on them. The BSS alarm subsystem does
not keep track of the PICs which have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives one or more
lists of the PICs for which the BSS has sent intermittent alarms (the BSS keeps track of the PICs
which have had alarms sent to them). The OMC-R receives the PIC lists in the additional alarm
data field of one or more PIC Fault intermittent alarms. The OMC-R knows it has received the
entire list of PICs when the OMC receives the Generic Result message from the BSS.
Any PIC alarms, which the OMC-R shows as active alarms that are not in the resync lists, is
changed to the clear state. If there are any new alarms in the lists that the OMC-R does not
show as active, no immediate action is required, since the BSS reissues the alarms later.
When the PIC Fault intermittent alarm is being used for resync, the Report Type of the alarm is
resync alarm.
Possible causes
One of the devices in the PIC path is faulty and is in need of replacement.
The PIC information is printed out in an understandable customer format.
68P02901W26-S 6-55
Nov 2007
An example of a format for the PIC is as follows:
PIC Fault for PIC 0x03010401

Path 1 0 0
BSC MMS 3 1 0
Timeslot 4
Group 1
BTS MMS 4 0 0
Procedure
Procedure 6-31 Circuit fault detected on PATH channel
1 If there are multiple PICs that use the same device and have PIC Alarms
active, one of these devices is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine the device
which needs replacement.

6-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48. BSS: Circuit fault cleared on PATH channel
48. BSS: Circuit fault cleared on PATH channel

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The count of errors for a particular PIC TRAU frame sync loss has reached or exceeded the PIC
error generation threshold. This alarm indicates that a device in the PIC path is faulty and
needs replacement. This alarm is an intermittent alarm sent to the OMC-R and Man Machine
Interface (MMI).
The OMC-R is notified any time that a PIC Clear notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty PIC clear intermittent alarm containing the PIC that is
being cleared. The OMC-R uses each PIC Fault Clear intermittent alarm to clear the Faulty PIC
alarm on the PIC given in the alarm. When it receives a Faulty PIC set intermittent alarm, the
OMC-R marks the PIC as alarming. When the OMC-R receives a Faulty PIC clear intermittent
alarm, it changes the displayed state of the alarm for the PIC in the intermittent alarm to clear.
This scheme produces an FMIC type functionality using intermittent alarms at the OMC-R and
not at the BSS. There is not enough memory at the BSS to implement FMIC alarms for each and
every PIC. When the OMC-R receives an ACI Fault Clear intermittent alarm that has an ADI
indicating Global Reset, the OMC-R clears all of the ACI CERM alarms.
The message Faulty PIC Alarm Clear is included in the PIC.
Possible causes
The failure causing TRAU Frame errors has cleared up for the PIC in the alarm clear message.
68P02901W26-S 6-57
Nov 2007
Procedure
Procedure 6-32 Circuit fault cleared on PATH channel

indicates that a prior fault has been cleared. If there is a trend where a PIC
toggles between being faulty and cleared, action is required to identify and
report to determine the device which requires replacement.

6-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 49. BSS: Last LMTL link failure - Signaling point inaccessible
49. BSS: Last LMTL link failure - Signaling point

inaccessible
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 0 alarm.
See 0. BSS: Last MTL link failure - Signaling point inaccessible.
The BSS reports a BSS: Last LMTL link failure - Signaling point inaccessible alarm when
at least one LMTL has been equipped and yet no in-service LMTLs exist.
The signaling point code is inaccessible due to the failure of the last available LMTL link. When
this occurs, the BSS cannot support calls or send messages to the SMLC.
The alarm clears when there are no in-service LMTLs and at least one LMTL comes into service.
LMTL link conguration
A single LMTL link provides a 64 kbps connection between the two pieces of equipment. One or
more LMTL links can be configured at BSC-to-Serving Mobile Location Centre (SMLC).
68P02901W26-S 6-59
Nov 2007
Possible causes

• No signaling route is available to the BSS-based SMLC.
• The circuits are faulty.
• The circuit coaxial cable is faulty.
• The dc power to the LMTL is lost.
• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, and SIE) frames causing
the link failure.
• The remote congestion timer expired causing the link failure.
• The MSU acknowledgment timer expired causing the link failure.
• The sequence numbers are not synchronized causing the failure.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive error rate that caused
the failure.
Procedure
Procedure 6-33 Last LMTL link failure - Signaling point inaccessible
1 Determine if all LMTL devices are OOS.

If all LMTL devices... Then...
If... Then...
the MSC is rebooting Wait until the MSC reboot is finished and then
go to step 3.
the RXCDR is rebooting Wait until the RXCDR reboot is finished and
then go to step 4.
neither the MSC or the RXCDR Go to step 4.
are rebooting
Continued
6-60 68P02901W26-S
Nov 2007
Procedure 6-33 Last LMTL link failure - Signaling point inaccessible (Continued)
cleared Determine the status of the LMTLs and take
the appropriate action to return all LMTLs to
service.
not cleared The fault is probably at the SMLC.
Troubleshoot the SMLC fault.
service.
5 Attempt to return one of the LMTLs to service.
If one of the MTLs... Then...
returns to service Go to step 6.
does not return to service Send a field representative to the site to
determine the cause of the alarm and take
appropriate action.
service.
not cleared Send a field representative to the site to
appropriate action.

68P02901W26-S 6-61
Nov 2007
50. BSS: Call processing failure - SMLC detected SCCP down Chapter 6: BSS Alarms
50. BSS: Call processing failure - SMLC detected SCCP

down
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
See 1. BSS: Call processing failure - MSC detected SCCP down on page 6-8.
The BSS reports a BSS Call processing failure - SMLC detected SCCP down alarm when the
SMLC sends the BSS a User Part Unavailable (UPU) message.
The BSS received a User Part Unavailable (UPU) message from the MSC indicating that the
Signaling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the
BSS cannot support calls.
When the SCCP is down, the BSS continues to be able to support MS calls, but LMUs and
location attempts are out.
The alarm clears when the last LMTL goes down.
6-62 68P02901W26-S
Nov 2007
Possible causes
The BSS has received a UPU message from the BSS-based SMLC indicating that the SCCP
is unavailable.
Procedure
Procedure 6-34 Call processing failure - SMLC detected SCCP down

2 Clear the alarm after resolving the fault.
68P02901W26-S 6-63
Nov 2007
51. BSS: Call processing failure - SMLC detected BSSAP down Chapter 6: BSS Alarms
51. BSS: Call processing failure - SMLC detected BSSAP

down
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
See 2. BSS: Call processing failure - MSC detected BSSAP down on page 6-10.
The BSS reports a BSS Call processing failure - SMLC detected BSSAP down alarm when
the remote BSSAP layer is available.
The BSS received a Subsystem Prohibited (SSP) message from the SMLC indicating that
the BSS Application Part (BSSAP) is down (unavailable). When this condition exists, the BSS
cannot support calls.
When the BSSAP is down, the SMLC does not accept BSSAP messages from the BSS. This
BSSAP failure occurs at the SMLC.
The alarm clears when the remote BSSAP layer becomes available.
This alarm can clear when the last LMTL goes down.
6-64 68P02901W26-S
Nov 2007
Possible causes
The BSS has received an SSP message from the SMLC indicating that the BSSAP is unavailable.
Procedure
Procedure 6-35 Call processing failure - SMLC detected BSSAP down
Send a field representative to the site to take the appropriate action and
resolve the alarm.

68P02901W26-S 6-65
Nov 2007
52. BSS: No SMLC acknowledgment for global reset Chapter 6: BSS Alarms
52. BSS: No SMLC acknowledgment for global reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
See 9. BSS: No MSC acknowledgment for global reset on page 6-25.
The BSS reports a BSS No SMLC acknowledgment for global reset alarm when the SMLC
does not send the BSS a global reset acknowledgment message.
The BSS repeated the global reset message the maximum number of times without receiving an
acknowledgment from the SMLC.
Possible causes
The SMLC did not acknowledge the global reset message.
Procedure
Procedure 6-36 No SMLC acknowledgment for global reset

6-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 53. BSS: Erroneous layer 3 message received from SMLC
53. BSS: Erroneous layer 3 message received from

SMLC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm indicates that the BSS has received a layer 3 message from the BSS-based SMLC
that is inappropriate for the state of the specified connection (wrong message).
This field displays the erroneous layer 3 message that the BSS receives from the BSS-based
SMLC.
Possible causes
For a specified connection, an SCCP Connection Confirm message is expected, but one of
the following is received:
• An SCCP Connection Refused message.
• An SCCP Connection Released message.
Procedure
Procedure 6-37 Erroneous layer 3 message received from SMLC
No alarm clearance is necessary.
68P02901W26-S 6-67
Nov 2007
54. BSS: Confusion message received from the SMLC Chapter 6: BSS Alarms
54. BSS: Confusion message received from the SMLC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 11
alarm. See 11. BSS: Confusion message received from the MSC on page 6-27.
The BSS reports a BSS Confusion message received from the SMLC alarm when the SMLC
sends the BSS a BSSMAP Confusion message.
The BSS receives a BSSMAP Confusion message from the SMLC.
The Additional information field displays the BSSMAP Confusion message that the BSS
receives from the SMLC.
Possible causes
The SMLC did not understand a layer 3 message from the BSS.
Procedure
Procedure 6-38 Confusion message received from the SMLC
Clear the alarm.
6-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 55. BSS: Received page for invalid cell from SMLC
55. BSS: Received page for invalid cell from SMLC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 26
alarm. See 26. BSS: Received page for invalid cell from MSC on page 6-38.
The BSS reports a BSS Received page for invalid cell from SMLC alarm when the SMLC
sends the BSS a Paging message for an invalid cell.
The SMLC sends a Paging message to a nonexistent cell in the BSS.
Table 6-9 shows the Additional information field values.
Table 6-9 Additional information eld values

first second third fourth fifth 00 to FF00 to FF00 to FF00 The 8 byte ID of the invalid
sixth seventh eighth to FF00 to FF00 to FF00 to cell.
FF00 to FF
Possible causes
The SMLC and BSS databases do not have matching cell ID lists.
68P02901W26-S 6-69
Nov 2007
Procedure
Procedure 6-39 Received page for invalid cell from SMLC
Reconcile the differences in the SMLC and BSS databases.
6-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 59. BSS: Last PCU failed
59. BSS: Last PCU failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The last PCU has gone out of service.
None.
Possible causes
PCUs OOS.
Procedure
Procedure 6-40 Last PCU failed
Determine why there are no PCUs available.
68P02901W26-S 6-71
Nov 2007
60. BSS: Circuit fault detected on GPRS circuit Chapter 6: BSS Alarms
60. BSS: Circuit fault detected on GPRS circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm occurs when the PSI DSP's TRAU frame sync loss error count has reached or
exceeded the DSP error generation threshold as a device in the route of DSP to the PCU is
faulty and needs replacing.
For non-alarm resynch, the additional data contains the following GPRS Circuit Identifier
related information:
Byte Denition
First Additional Data Identifier, 0x2d
Second PSI DSP ID
Third, Fourth, Fifth and Sixth PSI ID
For alarm resynch, the additional data contains the following GPRS Circuit Identifier related
information:
Byte Denition
First Additional Data Identifier, 0xa8
Second and Third Field Length
After the first three bytes, many circuits are listed. For each circuit, the bytes are distributed
as follows:
Byte Denition
First PSI DSP ID
Second, Third, Fourth and Fifth PSI ID
6-72 68P02901W26-S
Nov 2007
Possible causes
DSPs in PSI are faulty and PSI requires replacement.
Procedure
Procedure 6-41 Circuit fault detected on GPRS circuit
Replace the faulty PSI.
68P02901W26-S 6-73
Nov 2007
61. BSS: Circuit fault cleared on GPRS circuit Chapter 6: BSS Alarms
61. BSS: Circuit fault cleared on GPRS circuit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm occurs when the PSI DSP's TRAU frame sync loss error count is less than or equal
to the DSP error clear threshold as a device in the DSP path is no longer faulty. This alarm
is sent to OMC and MMI.
For PCU OOS case:
Byte Denition
First Additional Data Identifier, 0x2c
Second PCU ID
For other cases:
Byte Denition
First Additional Data Identifier, 0x2d
Second PSI DSP ID
Third, Fourth, Fifth and Sixth PSI ID
Possible causes
Affected DSPs are restored.
6-74 68P02901W26-S
Nov 2007
Procedure
Procedure 6-42 Circuit fault cleared on GPRS circuit
No alarm clearance is necessary.
68P02901W26-S 6-75
Nov 2007
6-76 68P02901W26-S
Nov 2007
Chapter
BTP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details BTP Alarms and includes the following alarm procedures:
• 1. BTP: EEPROM Flash failure - No valid bootstrap code object present on page 7-4.
• 8. BTP: EEPROM Flash object failure on page 7-6.
• 17. BTP: EEPROM flash programming failure on page 7-8.
• 20. BTP: LAPD controller failure on page 7-10.
• 21. BTP: EEPROM flash programming failure on page 7-11.
• 22. BTP: SWFM indication on page 7-13.
• 30. BTP: Clock A signal loss on page 7-14.
• 31. BTP: Clock B signal loss on page 7-17.
• 32. BTP: TDM interface failure - Assigned timeslot counter underflow on page 7-20.
• 33. BTP: TDM interface failure - Assigned timeslot counter overflow on page 7-22.
• 34. BTP: TDM interface failure - TDM parity error on page 7-24.
• 35. BTP: LAN connection failure on page 7-26.
• 39. BTP: Software failure on page 7-28.
• 40. BTP: Spurious interrupt on page 7-30.
• 42. BTP: Site reset occurred due to front panel reset on page 7-32.
• 47. BTP: Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected on page 7-33.
• 48. BTP: Memory location is corrupt. Replace GPROC board on page 7-35.
• 50. BTP: EEPROM SW flash programming failure on page 7-36.
• 51. BTP: EEPROM HW flash programming failure on page 7-37.
• 231. BTP: TDM interface configuration failure on page 7-38.
• 232. BTP: Processor bus communication failure on page 7-40.
• 234. BTP: Active link connection failure on page 7-41.
• 235. BTP: Standby link connection failure on page 7-44.
• 236. BTP: Slow flash failure on page 7-47.
68P02901W26-S 7-1
Nov 2007
Procedure Chapter 7: BTP Alarms
• 237. BTP: Non-volatile memory failure on page 7-49.
• 239. BTP: Process safe test audit failure on page 7-51.
• 254. BTP: Device failure on page 7-53.
7-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BTP alarms
Introduction to BTP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BTP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base
Transceiver Processor (BTP) device.
FRUs
A BTP device can be equipped on one of the FRUs shown in Table 7-1.
Table 7-1 BTP FRUs
FRU Description
GPROC2 InCell GPROC2 board.
GPROC3/GPROC3-2 InCell GPROC3/GPROC3-2 board.
H2SC Horizon II macro Site Controller.
MCU Micro Controller Unit board.
MCUF Micro Controller Unit board with dual FMUX.
MCUm M-Cell micro Micro Controller Unit board.
ARENAm (MCU) Horizon micro (M-Cell arena) Micro Controller
Unit board.
ARENA MAC (MCU) Horizon compact (M-Cell arena) Macro) Micro
Controller Unit board.
HORIZONMIC2 (MCU) Horizon micro2 Micro Controller Unit board.
HORIZONCOM2 (MCU) Horizon compact2 Micro Controller Unit board.
• Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS
to mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
• At the BTS, the BTP can only be GPROC2 or GPROC3/GPROC3-2.
68P02901W26-S 7-3
Nov 2007
1. BTP: EEPROM Flash failure - No valid bootstrap code object present Chapter 7: BTP Alarms
1. BTP: EEPROM Flash failure - No valid bootstrap code

object present
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
Possible causes

7-4 68P02901W26-S
Nov 2007
Procedure
Procedure 7-1 EEPROM Flash failure - No valid bootstrap code object present

If this alarm is occurring at... Then...
to clear the alarm.


68P02901W26-S 7-5
Nov 2007
8. BTP: EEPROM Flash object failure Chapter 7: BTP Alarms
8. BTP: EEPROM Flash object failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
Possible causes

• The bootstrap code object (Object 15) is incorrectly programmed with regard to the
7-6 68P02901W26-S
Nov 2007
Procedure

to clear the alarm.


68P02901W26-S 7-7
Nov 2007
17. BTP: EEPROM ash programming failure Chapter 7: BTP Alarms
17. BTP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem unless the GPROC is being reset, in which case
Possible causes
7-8 68P02901W26-S
Nov 2007
Procedure

68P02901W26-S 7-9
Nov 2007
20. BTP: LAPD controller failure Chapter 7: BTP Alarms
20. BTP: LAPD controller failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAPD controller on the BTP has encountered a fatal error.
Two bytes are displayed. Ignore the first byte, the second byte has a value of 1 or 2. The second
Table 7-2 BTP: LAPD controller failure second byte descriptions
Value Description
Possible causes
• The SRAM of the BTP could be faulty.
Procedure
1 Clear the alarm.

2 If the alarm occurs again, replace the BTP.
7-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. BTP: EEPROM ash programming failure
21. BTP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem unless the GPROC is being reset; in which case
Possible causes
Procedure
68P02901W26-S 7-11
Nov 2007

7-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. BTP: SWFM indication
22. BTP: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system has detected a software processing error (SWFM) for a BTP.
Possible causes
Procedure
Clear the alarm.
68P02901W26-S 7-13
Nov 2007
30. BTP: Clock A signal loss Chapter 7: BTP Alarms
30. BTP: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BTP detected a TDM Clock A failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BTP switches to the
The fault condition reported by this alarm may cause the site to go OOS.
Possible causes

• The KSWX A clock extender card failed.
7-14 68P02901W26-S
Nov 2007
Procedure
1 Determine the current administrative and operational state of the

site.
site to replace the GCLK.
devices in the same cage as Clock A:

alarms.
GCLK.
4 Check if more than 50% of the devices in the same cage are
reporting clock alarms.
If... Then...
yes Force the BTP to swap to the
redundant clock. The site resets
when the clock is swapped. After
the site reset is complete, go to
step 5.
no Go to step 5.
Continued
68P02901W26-S 7-15
Nov 2007
Procedure 7-7 Clock A signal loss (Continued)

5 Send a field representative to the site to perform one of the
following procedures based on the results of step 2.
are present on more than 50% The GCLK failed. The CBUS 0
of other devices alarm is also reported and taken
OOS. Replace the GCLK.
are present only for the BTP Replace the BTP.
are not present on other devices TDM Clock A detection circuitry
on the MSI board failed.
Replace the MSI board.

7-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. BTP: Clock B signal loss
31. BTP: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BTP detected a TDM Clock B failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BTP switches to the
Possible causes

68P02901W26-S 7-17
Nov 2007
Procedure


alarms.
GCLK.
4 Check if more than 50% of the devices in the same cage are
reporting clock alarms.
If... Then...
yes Force the BTP to swap to the
redundant clock. The site resets
when the clock is swapped. After
the site reset is complete, go to
step 5.
no Go to step 5.
Continued
7-18 68P02901W26-S
Nov 2007
Procedure 7-8 Clock B signal loss (Continued)

are present only for the BTP Replace the BTP.
on the MSI board failed. Replace
the MSI board.

68P02901W26-S 7-19
Nov 2007
32. BTP: TDM interface failure - Assigned timeslot counter underow Chapter 7: BTP Alarms
32. BTP: TDM interface failure - Assigned timeslot

counter underow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BTP has determined that the TDM highway is underused. Fewer switch-bound timeslots are
Possible causes

• The MCAP interface failed.
• The assigned timeslot counter register failed.
7-20 68P02901W26-S
Nov 2007
Procedure
Procedure 7-9 TDM Interface Failure - Assigned timeslot counter underow

required.
2 Reset the BTP.
The site is reset.

3 Determine the state of the BTP after the reset is completed.
If BTP is... Then...
required.

68P02901W26-S 7-21
Nov 2007
33. BTP: TDM interface failure - Assigned timeslot counter overow Chapter 7: BTP Alarms
33. BTP: TDM interface failure - Assigned timeslot

counter overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BTP has determined that the TDM highway is overused. More switch-bound timeslots are
Possible causes

• The assigned timeslot counter register failed.
7-22 68P02901W26-S
Nov 2007
Procedure

required.
2 Reset the BTP.
The site is reset.

required.

68P02901W26-S 7-23
Nov 2007
34. BTP: TDM interface failure - TDM parity error Chapter 7: BTP Alarms
34. BTP: TDM interface failure - TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Possible causes

7-24 68P02901W26-S
Nov 2007
Procedure

required.
2 Reset the BTP.
The site is reset.

required.

68P02901W26-S 7-25
Nov 2007
35. BTP: LAN connection failure Chapter 7: BTP Alarms
35. BTP: LAN connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAN connection between the master GPROC and any other equipped BTP on the LAN failed.
System action
The system places the BTP OOS. If the BTP is the master GPROC, the site resets.
Possible causes

• The BTP was reset through software or the front panel on site.
7-26 68P02901W26-S
Nov 2007
Procedure
Procedure 7-12 LAN Connection Failure

2 Reset the BTP.
The site is reset.

If the BTP is... Then...
required.

68P02901W26-S 7-27
Nov 2007
39. BTP: Software failure Chapter 7: BTP Alarms
39. BTP: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BTP experienced a non recoverable SWFM error.
System action
If there is only one processor in the site, the site resets. If there is a redundant processor,
programmers.
Possible causes

• The BTP software is faulty.
7-28 68P02901W26-S
Nov 2007
Procedure

3 Determine the state of the BTP.
busy-unlocked The alarm is caused by a software
error. Contact a Motorola
representative to resolve the
software error.

68P02901W26-S 7-29
Nov 2007
40. BTP: Spurious interrupt Chapter 7: BTP Alarms
40. BTP: Spurious interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BTP received and acknowledged an interrupt message but did not receive a response from
the device generating the interrupt.
Possible causes

• The timer on the BTP monitoring the MCAP Bus is faulty causing the wait timer to expire
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or some
other cause.
7-30 68P02901W26-S
Nov 2007
Procedure

reset Go to step 2.
3 Determine the current state of the BTP.
required.

68P02901W26-S 7-31
Nov 2007
42. BTP: Site reset occurred due to front panel reset Chapter 7: BTP Alarms
42. BTP: Site reset occurred due to front panel reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The site was reset when the front switch on the MCU was pressed. This alarm is reported after
the site comes back into service after the reset is complete.
This alarm is reported for M-Cell2, M-Cell6, M-Cell micro, Horizon, and Horizon
II macro sites.
Possible causes
The reset switch on the front panel of the MCU was pressed.
Procedure
Procedure 7-15 Site reset occurred due to front panel reset
1 Investigate the reason for the front panel reset of the BTP MCU.
2 Clear the alarm.
7-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 47. BTP:
Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected
47. BTP: Unexpected board type: GPROC2 or

GPROC3/GPROC3-2 expected
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
A GPROC was detected in a slot where the system expected to find a GPROC2 or
GPROC3/GPROC3-2. BTPs exist only at InCell sites, where GPROC2 or GPROC3/GPROC3-2s
are mandatory.
If this condition occurs in an InCell site, the GPROC board does not come into service. The
maximum number of timeslots a GPROC can use is 16. A GPROC2 or GPROC3/GPROC3-2 can
use 8, 16 or 32 timeslots.
Possible causes
If this condition occurs in an InCell site, the GPROC board does not come into service.
68P02901W26-S 7-33
Nov 2007
Procedure
Procedure 7-16 Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected

correct Send a field representative to the site to
replace the GPROC board with a GPROC2 or
GPROC3/GPROC3-2 board.
not correct Change the value of the gproc_slots database
parameter to the correct value and then go to
step 2.
2 Reset the BTP.
The site is reset.

busy-unlocked The fault condition no longer exists. No further
action is required.
not busy-unlocked Send a field representative to the site to
replace the GPROC board with a GPROC2 or
GPROC3/GPROC3-2 board.

7-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48. BTP: Memory location is corrupt. Replace GPROC board
48. BTP: Memory location is corrupt. Replace GPROC

board
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Possible causes

Procedure
Procedure 7-17 Memory location is corrupt. Replace GPROC board

68P02901W26-S 7-35
Nov 2007
50. BTP: EEPROM SW ash programming failure Chapter 7: BTP Alarms
50. BTP: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes

Procedure
to reload the BOOTROM object.
7-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 51. BTP: EEPROM HW ash programming failure
51. BTP: EEPROM HW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm is a generic flash programming error.
Possible causes
Procedure

2 To resolve the alarm, reset the BTP and continue to use until it is possible to
replace the GPROC3 board.
68P02901W26-S 7-37
Nov 2007
231. BTP: TDM interface conguration failure Chapter 7: BTP Alarms
231. BTP: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BTP cannot be programmed for a designated timeslot on the TBUS.
System action
The system automatically resets the BTP. If the alarm recurs, the BTP is placed OOS.
Possible causes

• The GPROC board failed.
• A software error occurred.
the TDM highways.
7-38 68P02901W26-S
Nov 2007
Procedure

required.

68P02901W26-S 7-39
Nov 2007
232. BTP: Processor bus communication failure Chapter 7: BTP Alarms
232. BTP: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A BTP board device has lost the ability to communicate to the peripheral boards through the
MCAP bus.
Possible causes

• The front panel switch was disabled without the GPROC being reset first.
• The part of the BTP that supports the MCAP bus access failed.
Clearing the alarm
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
Procedure
1 Attempt to bring back the BTP In Service (INS). If the device is back in
2 Replace the BTP board.
7-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 234. BTP: Active link connection failure
234. BTP: Active link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver unit active link connection to the active BTP failed.
II macro sites.
This alarm is reported for each incorrect active link connection in a BTS or in an extender
cabinet. A link connection failure involves a combination of these hardware units: FOX, FMUX,
MCU, XMUX, or transceiver unit.
HDLC data only.
Possible causes

• The transceiver unit failed.
• The BTP failed.
• The DRI and/or BTP portion that supports active BTP link connection failed.
• A port of the active FOX and/or FMUX board failed.
• The communication fiber link failed.
• A backplane connection failed.
68P02901W26-S 7-41
Nov 2007
Procedure
Procedure 7-22 Active link connection failure
1 Determine if the Device Failure (BTP 254 or DRI 254) alarm was
received.
If this alarm is reported Then...
with...
a DRI 254 alarm Send a field representative to the
site to replace the transceiver unit.
a BTP 254 alarm Send a field representative to the
site to replace the MCU.
neither a DRI 254 alarm nor a Go to step 2.
BTP 254 alarm
2 Determine the state of the DRI.
If DRI is... Then...
busy-unlocked or Go to step 4.
enabled-unlocked
not busy-unlocked or Attempt to return the DRI to
enabled-unlocked service and then go to step 3.
3 Determine if the alarm is clear.
clear The fault condition no longer exists.
If there is a recurrence of this
alarm, send a field representative
to the site to replace the transceiver
unit.
not clear Go to step 4.
busy-unlocked or The fault condition no longer exists.
enabled-unlocked If there is a recurrence of this
to the site to replace the MCU.
not busy-unlocked or Attempt to return the BTP to
Continued
7-42 68P02901W26-S
Nov 2007
Procedure 7-22 Active link connection failure (Continued)

clear The fault condition no longer exists.
If this is a recurrence of this alarm,
send a field representative to the
not clear Send a field representative to the

68P02901W26-S 7-43
Nov 2007
235. BTP: Standby link connection failure Chapter 7: BTP Alarms
235. BTP: Standby link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The standby link connection from the transceiver unit to the standby BTP failed.
II macro sites.
This alarm is reported for each incorrect active link connection in a BTS or in an extender
cabinet. A link connection failure involves a combination of these hardware units: FOX, FMUX,
MCU, XMUX, or transceiver unit.
HDLC data only.
Possible causes

• The BTP failed.
• The DRI and/or BTP portion that supports active BTP link connection failed.
• A port of the active FOX and/or FMUX board failed.
7-44 68P02901W26-S
Nov 2007
When a Horizon II mini is expanded from a Horizon I, Horizon II or M-Cell6 cabinet

with redundancy, the alarm Standby Link Connection Failure is raised for radio in
the Horizon II mini cabinet. However, this alarm relates to the absence of redundancy
in the Horizon II mini and does not indicate a fault in the Horizon II mini or in the
macro BTS.
Procedure
Procedure 7-23 Standby link connection failure
1 Determine if the Device Failure (BTP 254) alarm was also received.
If a BTP 254 alarm... Then...
is received Send a field representative to the
is not received Go to step 2.
busy-unlocked or The fault condition no longer
enabled-unlocked exists. If there is a recurrence
of this alarm, send a field
representative to the site to
replace the MCU.
not busy-unlocked or Attempt to return the BTP to
clear The fault condition no longer
exists. If there is a recurrence
replace the MCU.
68P02901W26-S 7-45
Nov 2007

7-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 236. BTP: Slow ash failure
236. BTP: Slow ash failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A failure to read or write to a slow flash EEPROM was detected for the transceiver unit.
Possible causes
The flash EEPROM on the transceiver unit is faulty.
68P02901W26-S 7-47
Nov 2007
Procedure
Procedure 7-24 Slow ash failure

If the DRI is... Then...
required.
2 Reset the DRI.
3 Determine the state of the DRI after the reset is completed.
required.

7-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 237. BTP: Non-volatile memory failure
237. BTP: Non-volatile memory failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A failure to read or write to the Non-Volatile (NV) flash EEPROM was detected for the
transceiver unit.
Possible causes
The NV flash EEPROM on the transceiver unit is faulty.
68P02901W26-S 7-49
Nov 2007
Procedure
Procedure 7-25 Non-volatile memory failure

required.
2 Reset the DRI.
required.

7-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. BTP: Process safe test audit failure
239. BTP: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The BTP failed a process safe test audit. The process safe test audit verifies the proper operation
Table 7-3. Bytes one through eight is useful only to the programmers. Byte nine is the reason
code for the alarm.

02 Higher priority processes prevented the process that failed to run.
Possible causes

• A process running on the BTP failed a safe test audit.
Procedure
68P02901W26-S 7-51
Nov 2007
1 Determine the reason code displayed in the Additional information

field.
2 Go to step 2.
2 Perform the safe test audit on the BTP
If the BTP... Then...
3 Reset the BTP.
The site is reset.

required.

7-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. BTP: Device failure
254. BTP: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BTP was taken OOS by the GPROC Fault Management System.
System action
The site resets.
shown in Table 7-4.
Value Denition
01 Hard reset
02 Soft reset
Possible causes
A fault translation by the GPROC Fault Management System.
Procedure
68P02901W26-S 7-53
Nov 2007
Wait approximately 10 minutes after this alarm is received to allow the site to reset
before following this procedure.
1 Determine the current state of the BTP.

required.
2 Reset the BTP.
The site is reset.

required.

7-54 68P02901W26-S
Nov 2007
Chapter
CAB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CAB Alarms and includes the following alarm procedures:
• 25. CAB: External power booster amplifier 1 failure on page 8-3.
• 26. CAB: External power booster amplifier 2 failure on page 8-5.
• 27. CAB: External power booster failure on page 8-7.
• 28. CAB: Database configuration and hardware mismatch on page 8-9.
68P02901W26-S 8-1
Nov 2007
Introduction to CAB alarms Chapter 8: CAB Alarms
Introduction to CAB alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
CAB alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CAB device.
FRUs
A CAB device can be equipped on one of the FRUs shown in Table 8-1.
Table 8-1 CAB FRUs
FRU Description
ARENA MACRO Horizon compact (M-Cell arena Macro)
cabinet.
HORIZONMACRO Horizon macro cabinet.
HORIZONCOMPACT2 Horizon compact2 cabinet.
HORIZONMICRO2 Horizon micro2 cabinet.
MCELL TWO M-Cell2 cabinet.
MCELL MICRO M-Cell micro cabinet.
MCELL CITY M-Cell city cabinet.
MCELL SIX M-Cell6 cabinet.
8-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. CAB: External power booster amplier 1 failure
25. CAB: External power booster amplier 1 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Amplifier 1 in the external power booster failed. When this condition occurs, the transmitted
power to Channel 1 transmit antenna is reduced to approximately 0.8 W. This power reduction
adversely affects macro cell coverage.
This alarm is generated only for Horizon compact2 equipment. However, the database
CAB entry for the Horizon compact2 can also be set to Horizon micro2. Hence, this
alarm is supported for both Horizon compact2 and Horizon micro2 database entries.
Possible causes
Amplifier 1 in the external power booster failed.
68P02901W26-S 8-3
Nov 2007
Procedure Chapter 8: CAB Alarms
Procedure
Procedure 8-1 External power booster amplier 1 failure
Send a field representative to the site to replace the external power booster.

8-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. CAB: External power booster amplier 2 failure
26. CAB: External power booster amplier 2 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Amplifier 2 in the external power booster failed. When this condition occurs, the transmitted
power to Channel 2 transmit antenna is reduced to approximately 0.8 W. This power reduction
adversely affects macro cell coverage.
Possible causes
Amplifier 2 in the external power booster failed.
68P02901W26-S 8-5
Nov 2007
Procedure
Send a field representative to the site to replace the external power booster.

8-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. CAB: External power booster failure
27. CAB: External power booster failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The external power booster failed. When this occurs, the transmitted power to both transmit
antennae is reduced to approximately 0.8 W. This power reduction adversely affects macro
cell coverage.
Possible causes

• The power supply or other hardware components of the external power booster failed.
• The external power booster is not present.
68P02901W26-S 8-7
Nov 2007
Procedure
Procedure 8-3 External power booster failure
1 Send a field representative to the site to determine the cause of the failure.
Take appropriate action and resolve the alarm.

8-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. CAB: Database conguration and hardware mismatch
28. CAB: Database conguration and hardware

mismatch
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The database configuration is not correct for the type of hardware at the site. The system
continues to function and report valid External Power Booster alarms, if detected.
This alarm is generated for M-Cell2, M-Cell6, Horizon macro, and Horizon II macro. The alarm
is raised or cleared only if there are one or more in-service DRIs in the cabinet.
Examples of hardware mismatches are as follows:

• The database extension cabinet type is HORIZON2MINI_EXT and FRU type is not Horizon
II mini.
• The database extension cabinet type is of any type other than HORIZON2MINI_EXT and
FRU type is Horizon II mini.
The BSS clears this alarm if the database extension cabinet type is HORIZON2MINI_EXT and
FRU type is Horizon II mini.
Possible causes
The database configuration is not correct for the type of hardware at the site.
68P02901W26-S 8-9
Nov 2007
Procedure
Procedure 8-4 Database conguration and hardware mismatch
1 Determine what type of hardware is supposed to be installed at the

site.
2 Send a field representative to the site to verify if the correct type of
hardware is installed at the site.
If the hardware is... Then...
correct The database configuration is
incorrect. Update the database to
match the correct hardware.
not correct Replace the installed hardware
with the correct hardware.

8-10 68P02901W26-S
Nov 2007
Chapter
CAGE Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details Cage Alarms and includes the following alarm procedures:
• 20 - 25. CAGE: CLKX slot 2-7 communication failure on page 9-3.
• 26 - 27. CAGE: LANX slot 19-20 communication failure on page 9-6.
• 28 - 30. CAGE: Power supply unit #1-3 - Output failure on page 9-9.
• 31 - 33. CAGE: Power supply unit #1-3 - Not detected on page 9-11.
• 34 - 36 CAGE: Power supply unit #1-3 - Fan failure on page 9-13.
• 37 - 39. CAGE: Power supply unit #1-3 - Over temperature on page 9-15.
• 40. CAGE: Over temperature - Component damage imminent on page 9-17.
• 41 - 42. CAGE: Local KSWX/DSWX slot 0-1 communication failure on page 9-19.
• 43 - 47. CAGE: Remote KSWX/DSWX slot 2-6 communication failure on page 9-22.
• 48 - 52. CAGE: Remote KSWX/DSWX slot 24-28 communication failure on page 9-25.
• 53 - 55. CAGE: Expansion KSWX/DSWX slot 7- 9 communication failure on page 9-28.
• 56 - 58. CAGE: Expansion KSWX/DSWX slot 21-23 communication failure on page 9-31.
• 59 - 76. CAGE: DSWX/KSWX mismatch on page 9-34.
68P02901W26-S 9-1
Nov 2007
Introduction to CAGE alarms Chapter 9: CAGE Alarms
Introduction to CAGE alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
CAGE alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CAGE device.
CAGE alarms are generated for the half size cards used to extend clock and data signals from
one cabinet to another, and for power supply units in the PCU.
9-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20 - 25. CAGE: CLKX slot 2-7 communication failure
20 - 25. CAGE: CLKX slot 2-7 communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The system either failed to communicate with the CLKX or detected that the card in the slot
specified in the alarm message is not a CLKX card.
CLKX cards can be installed in slot 2 through slot 7 to extend the Clock Distribution Bus (CBUS)
to a cage in which a GCLK is not installed.
GCLK=>CLKX=>Local KSWX=>CBUS
System action
Since the faulty CLKX is in the CBUS pathway, a CLKX failure causes the CBUS to be placed
OOS. If a standby CBUS is unavailable, the cage is disabled causing a site reset.
A single byte is displayed in the Additional information field. The first digit is the hardware
revision number of the card in the slot. The second digit represents the board type. Table 9-1
shows the Additional information field values.
The value ff is displayed if a card is not inserted in the slot or if the polling software
failed to communicate with the CLKX card.
68P02901W26-S 9-3
Nov 2007
Possible causes Chapter 9: CAGE Alarms
Digit Value (digital) Denition

first 0 to 2 The hardware revision number
second 0 Reserved (not applicable)
1 KSWX local mode
2 KSWX remote mode
3 KSWX expanded mode
4 EAS Parallel Interface Extender (PIX)
5 Alarm Interface Board (AIB)
6 Clock Extender (CLKX)
7 Local Area Network Extender (LANX)
8 Power Supply, +27 V
9 Power Supply, -48 V/-60 V
a DRIX
b (not used)
c Compact -48 V/-60 V Power Supply
d Power Alarm Board (PAB)
e (not used)
f Reserved (not applicable)
Possible causes

• The CLKX card is not properly inserted in the CLKX slot.
• The card inserted in the slot is not a CLKX card.
• The CLKX card is faulty.
Procedure
Procedure 9-1 CLKX slot 2-7 communication failure
9-4 68P02901W26-S
Nov 2007

68P02901W26-S 9-5
Nov 2007
26 - 27. CAGE: LANX slot 19-20 communication failure Chapter 9: CAGE Alarms
26 - 27. CAGE: LANX slot 19-20 communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The system either failed to communicate with the LANX or detected that the card in the slot
specified in the alarm message is not a LANX card.
Hot pull of a busy LANX is not supported. If a hot pull of a LANX card is attempted,
the site resets.
LANX cards may be installed in slots 19 or 20 to extend the LAN to all other cages at a site.
A LANX is required for the MCAP Bus (PBUS) to function correctly.
System action
When this alarm is reported, the associated LAN and PBUS is placed OOS.
failed to communicate with the LANX card.
9-6 68P02901W26-S
Nov 2007

1 KSWX local mode
2 KSWX remote mode
3 KSWX expanded mode
a DRIX
b (not used)
e (not used)
Ignore any additional bytes displayed .
Possible causes

• The LANX card is properly inserted in the LANX slot.
• The card inserted in the slot is not a LANX card.
• The LANX card is faulty.
Procedure
Procedure 9-2 LANX slot 19-20 communication failure
68P02901W26-S 9-7
Nov 2007
Procedure Chapter 9: CAGE Alarms

9-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28 - 30. CAGE: Power supply unit #1-3 - Output failure
28 - 30. CAGE: Power supply unit #1-3 - Output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the power supplied by the PSU in the PCU cage is beyond the tolerance
limit of ±5% of the expected value.
If one PSU fails, there is a loss of redundancy.
If two PSUs fail, the last PSU has to drive all the boards in the cage and becomes overloaded.
If the third PSU fails, it indicates a critical condition, since the boards in the cage are not
powered.
This alarm is cleared when the affected PSU becomes operational or when the Not
Detected alarm of the affected PSU is raised.
Possible causes
• There is a problem with the input power supply of the PCU cage.
• The PSU has failed.
68P02901W26-S 9-9
Nov 2007
Procedure
Procedure 9-3 Power supply unit #1-3 - Output failure
Send a field representative to the site to take appropriate action and resolve
the alarm.

9-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31 - 33. CAGE: Power supply unit #1-3 - Not detected
31 - 33. CAGE: Power supply unit #1-3 - Not detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the related PSU is not present in the PCU cage.
There is a consequent loss of redundancy.
This alarm is cleared when the affected PSU is detected in its slot.
Possible causes
• A PSU is not present in the related slot of the PCU cage.
• A PSU is not correctly inserted in the related slot of the PCU cage.
68P02901W26-S 9-11
Nov 2007
Procedure
Procedure 9-4 Power supply unit #1-3 - Not detected
the alarm.

9-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34 - 36 CAGE: Power supply unit #1-3 - Fan failure
34 - 36 CAGE: Power supply unit #1-3 - Fan failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the fan housed in the related PSU has failed.
Reduced air cooling results in a rise in the PCU internal temperature.
This alarm is cleared when the fan housed in the affected PSU becomes operational
or when the Not Detected alarm for the related PSU is raised.
Possible causes
• A mechanical fault (such as an obstruction to the fan blade) occurred.
• The fan housed in the affected PSU failed.
68P02901W26-S 9-13
Nov 2007
Procedure
Procedure 9-5 Power supply unit #1-3 - Fan failure
Send a field representative to the site to replace the relevant PSU.

9-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 37 - 39. CAGE: Power supply unit #1-3 - Over temperature
37 - 39. CAGE: Power supply unit #1-3 - Over

temperature
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the related PSU has failed as it has detected a rise in the air
temperature to approximately 40 °C. This temperature is near the upper limits for components
in the system, but they are not in immediate danger of damage.
This alarm is cleared when the over-temperature condition is cleared or the Not
Detected alarm of the affected PSU is raised.
Possible causes
• The fan housed in the affected PSU failed.
• Shutters of the fan housed in the affected PSU is jammed.
• There is an airflow blockage.
• The ambient room temperature has risen.
68P02901W26-S 9-15
Nov 2007
Procedure
Procedure 9-6 Power supply unit #1-3 - Over temperature
the alarm.

9-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 40. CAGE: Over temperature - Component damage imminent
40. CAGE: Over temperature - Component damage

imminent
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that all PSUs present in the PCU cage have detected a rise in the air
temperature to approximately 50 °C. This temperature is beyond safe operating limits for
components in the system. This state indicates a critical failure of the cooling system in the
cage or an excessive rise in ambient temperature.
There may be damage due to heat the system components.
This alarm is cleared when the over-temperature condition is cleared.
Possible causes
• All the fans have failed.
• There is an airflow blockage.
• The ambient room temperature rises.
68P02901W26-S 9-17
Nov 2007
Procedure
Procedure 9-7 Over temperature - Component damage imminent
Send a field representative to the site and take appropriate action and
resolve the alarm.

9-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41 - 42. CAGE: Local KSWX/DSWX slot 0-1 communication failure
41 - 42. CAGE: Local KSWX/DSWX slot 0-1

communication failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
Slot 0 and slot 1 are reserved for KSWX/DSWX cards that provide one or both of the following
functions:
• Extend clock signals from a GCLK in another cage to the Clock Distribution Bus (CBUS) in
the cage where the KSWX/DSWX is installed.
GCLK=>CLKX=>Local KSWX/DSWX=>CBUS
• Extend the TDM Bus (TBUS) from an associated KSW installed in another cage to the TBUS
in the cage where the KSWX/DSWX is installed.
KSW <=> Remote KSWX/DSWX <=> Local KSWX/DSWX <=> TBUS
System action
The system takes one of the following actions:

• If a faulty KSW is installed in the same cage as the KSWX/DSWX, the CBUS is placed OOS.
• If a standby CBUS is unavailable, the cage is disabled causing a site reset.
failed to communicate with the KSWX/DSWX card.
68P02901W26-S 9-19
Nov 2007

1 KSWX/DSWX local mode
2 KSWX/DSWX remote mode
3 KSWX/DSWX expanded mode
a DRIX
b (not used)
e (not used)
Possible causes

• The KSWX/DSWX card is not properly inserted in the slot.
• The card inserted in the slot is not a KSWX/DSWX card.
• The KSWX/DSWX card is faulty.
9-20 68P02901W26-S
Nov 2007
Procedure
Procedure 9-8 Local KSWX/DSWX slot 0-1 communication failure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 If a faulty KSW is not installed in the same cage as the KSWX/DSWX, the
TBUS and the CBUS is placed OOS.
3 If a standby TBUS and CBUS are unavailable, the cage is disabled causing
a site reset.

68P02901W26-S 9-21
Nov 2007
43 - 47. CAGE: Remote KSWX/DSWX slot 2-6 communication failure Chapter 9: CAGE Alarms
43 - 47. CAGE: Remote KSWX/DSWX slot 2-6

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Remote KSWX/DSWX cards can be installed in slots 2 through 6, to extend the TDM Bus (TBUS)
from an associated KSW, installed in the same cage as the KSWX/DSWX to another cage.
KSW <=> Remote KSWX/DSWX<=> Local KSWX/DSWX<=> TBUS
9-22 68P02901W26-S
Nov 2007

a DRIX
b (not used)
e (not used)
Possible causes

68P02901W26-S 9-23
Nov 2007
Procedure
Procedure 9-9 Remote KSWX/DSWX slot 2-6 communication failure
2 Since the faulty KSWX/DSWX is in the TBUS pathway, the TBUS in the
extended cage is placed OOS. If a standby TBUS is unavailable, the cage is
disabled causing a site reset.

9-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48 - 52.
CAGE: Remote KSWX/DSWX slot 24-28 communication failure
48 - 52. CAGE: Remote KSWX/DSWX slot 24-28

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Remote KSWX/DSWX cards can be installed in slot 2 through slot 6, to extend the TDM Bus
(TBUS) from an associated KSW, installed in the same cage as the KSWX/DSWX to another cage.
68P02901W26-S 9-25
Nov 2007

a DRIX
b (not used)
e (not used)
Possible causes

9-26 68P02901W26-S
Nov 2007
Procedure
Procedure 9-10 Remote KSWX/DSWX slot 24-28 communication failure

68P02901W26-S 9-27
Nov 2007
53 - 55. CAGE: Expansion KSWX/DSWX slot 7- 9 communication failure Chapter 9: CAGE Alarms
53 - 55. CAGE: Expansion KSWX/DSWX slot 7- 9

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
KSWX/DSWX cards can be installed in slot 7 through slot 9 to expand the number of TDM
timeslots by adding KSWs.
9-28 68P02901W26-S
Nov 2007

a DRIX
b (not used)
e (not used)
Possible causes

68P02901W26-S 9-29
Nov 2007
Procedure
Procedure 9-11 Expansion KSWX/DSWX slot 7- 9 communication failure

9-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 56 - 58.
CAGE: Expansion KSWX/DSWX slot 21-23 communication failure
56 - 58. CAGE: Expansion KSWX/DSWX slot 21-23

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
KSWX/DSWX cards can be installed in slots 21 through 23 to expand the number of TDM
timeslots by adding KSWs.
68P02901W26-S 9-31
Nov 2007

a DRIX
b (not used)
e (not used)
Possible causes

9-32 68P02901W26-S
Nov 2007
Procedure
Procedure 9-12 Expansion KSWX/DSWX slot 21-23 communication failure

68P02901W26-S 9-33
Nov 2007
59 - 76. CAGE: DSWX/KSWX mismatch Chapter 9: CAGE Alarms
59 - 76. CAGE: DSWX/KSWX mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The TDM device reporting this alarm remains out of service while this condition exists.
Additional data is of 2 bytes: Byte 1 = Cage, Byte 2 = Slot.
Possible causes
The KSWX in slot 0 has been paired with a DSWX or the DSWX has been paired with the KSWX.
9-34 68P02901W26-S
Nov 2007
Procedure
Procedure 9-13 DSWX/KSWX mismatch
2 Replace the mismatched card with the appropriate card to match its partner.
3 A DSWX must be paired with another DSWX and a KSWX must be paired
with another KSWX.

68P02901W26-S 9-35
Nov 2007
9-36 68P02901W26-S
Nov 2007
Chapter
10
CBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CBL and includes the following alarm procedures:
• 0. CBL: Invalid received frames - PM on page 10-3.
• 1. CBL: FRMR frames - PM on page 10-5.
• 2. CBL: Expiration of N2 - PM on page 10-7.
68P02901W26-S 10-1
Nov 2007
Introduction to CBL alarms Chapter 10: CBL Alarms
Introduction to CBL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
CBL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Cell Broadcast
Link (CBL) alarms.
10-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. CBL: Invalid received frames - PM
0. CBL: Invalid received frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The INVALID_FRAMES_RX statistic threshold has been reached.
This statistic counts the number of the invalid frames received on the X.25 link.
For further information, refer to the CBL statistics chapter in the manual, Maintenance
Possible causes
An invalid frame was received on the X.25 link.
Procedure
Procedure 10-1 Invalid received frames - PM
If this alarm is... Then...

persistently reported Send a field representative to the
site to check the X.25 link between
the CBC and the BSC and take
appropriate action.
not persistently reported Clear the alarm.
68P02901W26-S 10-3
Nov 2007
Procedure Chapter 10: CBL Alarms

10-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. CBL: FRMR frames - PM
1. CBL: FRMR frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The FRMR statistic threshold has been reached.
This statistic counts the number of the frames on the X.25/LAPD link that were rejected because
the frames were not correctable.
Possible causes
A frame reject message was received on the X.25 link.
68P02901W26-S 10-5
Nov 2007
Procedure
Determine if this alarm is persistently reported. Perform the following procedure to resolve
the alarm.
Procedure 10-2 FRMR frames - PM

site to check the X.25 link and take
appropriate action.

10-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CBL: Expiration of N2 - PM
2. CBL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The N2_EXPIRY statistic threshold has been reached.
This statistic indicates that the maximum number of link alignment retries has been attempted
without success.
Possible causes
• The X.25 link between the CBC and the BSC failed due to a hardware fault or repair action.
• The link connection is broken.
• An MSC-OMC-R outage occurred.
• The link is OOS due to repair work.
• A hardware failure affecting the link occurred.
68P02901W26-S 10-7
Nov 2007
Procedure
Determine if this alarm is persistently reported. Perform the following procedure to resolve
the alarm.
Procedure 10-3 Expiration of N2 - PM

site to check the X.25 link between
the CBC and the BSC and take
appropriate action.

10-8 68P02901W26-S
Nov 2007
Chapter
11
CBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CBUS alarms and includes the following alarm procedures:
• 0. CBUS: Over 50% of boards detected clock failure on page 11-3.
• 2. CBUS: Master CBUS signal provided by slave GCLK on page 11-5.
• 4. CBUS: Local KSWX/DSWX clock fiber failure on page 11-7.
68P02901W26-S 11-1
Nov 2007
Introduction to CBUS alarms Chapter 11: CBUS Alarms
Introduction to CBUS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
CBUS alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Clock
Distribution Bus (CBUS) device.
The CBUS alarms are generated when a fault condition occurs within the link which carries the
Generic Clock (GCLK) signals to the devices in a cage.
11-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. CBUS: Over 50% of boards detected clock failure
0. CBUS: Over 50% of boards detected clock failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Over 50% of the GPROC and peripheral boards in a cage have reported clocking failures.
System action
When this alarm occurs, if the faulty CBUS is in a Busy-Unlocked device state, the system
automatically attempts to swap its functionality to the redundant CBUS. In order for a swap to
occur, a redundant CBUS (Enabled-Unlocked) must be available.
If a redundant CBUS is not available for a swap, disable the associated CAGE device. This
action causes a site reset. After the site reset, if this fault condition is still present, the affected
CAGE remains OOS, however, the site returns to service. Also, any devices located in the
disabled cage remain OOS.
If this alarm is generated for a redundant CBUS, no automatic CBUS swap can occur. In this
case, the faulty CBUS is disabled.
Possible causes

• The clock fiber link failed.
• The backplane connections are faulty.
• All boards that reported the problem have failed. This event is unlikely.
68P02901W26-S 11-3
Nov 2007
Procedure Chapter 11: CBUS Alarms
Procedure
Procedure 11-1 Over 50% of boards detected clock failure
1 Determine the state of the affected CBUS using the state command
in a TTY window.
If the CBUS is... Then...
exists. Monitor the system for a
recurrence of this alarm.
disabled-unlocked The system successfully
swapped the CBUSs. This
indicates an equipment problem.
Go to step 2.
not busy-unlocked or The system did not successfully
disabled-unlocked swap the CBUSs. A redundant
CBUS is not equipped or available.
In this case the CAGE and all
devices in the CAGE remain OOS.
Go to step 2.
2 Determine if any of the devices in the affected CAGE reported an
alarm.
If any devices... Then...
reported an alarm Resolve the individual alarms.
did not report an alarm The fault condition no longer
exists. Monitor the system for a
recurrence of this alarm.
11-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CBUS: Master CBUS signal provided by slave GCLK
2. CBUS: Master CBUS signal provided by slave GCLK

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The slave GCLK provides the clock signal output on the master CBUS.
This alarm is a warning that any action on the redundant GCLK is likely to have a
negative impact on one or more cages at a site. This impact is because the master
GCLK signal is fed through the slave GCLK board before it is extended to the master
CBUS. If the slave GCLK is physically removed from the cage, the site is reset due to
a loss of the clock signal.
Possible causes

• The master GCLK failed.
• The fiber link between the CLKX board and KSWX board is faulty.
• The CLKX or KSWX boards are missing.
• Backplane problems with the CBUS are associated with the master GCLK.
68P02901W26-S 11-5
Nov 2007
Procedure
To resolve the alarm, carry out the follow the following procedure.
Procedure 11-2 Master CBUS Signal Provided By Slave GCLK
1 Determine the state of the master GCLK.

If an alarm is... Then...
reported for the master GCLK Troubleshoot the alarm reported
for the master GCLK. Refer to
the description of the alarm
for the resolution procedure.
If this alarm is not cleared after
resolving the master GCLK alarm,
go to step 2.
not reported for the master Go to step 2.
GCLK
For the details regarding on site equipment and repair

procedures, refer to Maintenance Information: BSS Field

11-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. CBUS: Local KSWX/DSWX clock ber failure
4. CBUS: Local KSWX/DSWX clock ber failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The absence of a clock signal was detected while polling a KSWX/DSWX board.
System action
When this alarm occurs and the faulty CBUS is in a Busy-Unlocked device state, the system
automatically attempts to swap its functionality to the redundant CBUS. In order for a swap to
occur, a redundant CBUS (Enabled-Unlocked) must be available.
If a redundant CBUS is not available for a swap, disable the associated CAGE device. This
action causes a site reset. After the site reset, if this fault condition is still present, the affected
CAGE remains OOS; however, the site returns to service. Also, any devices located in the
disabled cage remain OOS.
If this alarm is generated for a redundant CBUS, no automatic CBUS swap can occur. In this
case, the faulty CBUS is disabled.
Possible causes

• The CBUS fiber link is disconnected from the local KSWX/DSWX board.
• The CBUS fiber link is disconnected from the CLKX port.
• The CBUS fiber link is faulty.
• The CLKX board is removed.
• The CLKX fiber link or the fiber port on the CLKX is faulty.
• The fiber port on the local KSWX/DSWX board is faulty.
68P02901W26-S 11-7
Nov 2007
Procedure
To resolve the alarm, perform the following procedure.
Procedure 11-3 Local KSWX/DSWX clock ber failure

11-8 68P02901W26-S
Nov 2007
Chapter
12
CELL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CELL alarms and includes the following alarm procedures:
• 0. CELL: Flow control procedure has started barring normal calls from access classes 0-9
on page 12-4.
• 0. CELL: Radio frequency losses while using an SDCCH - PM on page 12-6.
• 1. CELL: Cell radio timeslot capacity loss on page 12-8.
• 1. CELL: Attempt at allocating an SDCCH failed - PM on page 12-9.
• 2. CELL: Radio subsystem software error - Detected page overflow on page 12-11.
• 2. CELL: Channel request from MS blocked - PM on page 12-13.
• 3. CELL: Last NS-VC failed on page 12-15.
• 4. CELL: Classmark update from MS protocol error - PM on page 12-17.
• 5. CELL: No cell (BVC) block acknowledgment from the SGSN on page 12-19.
• 6. CELL: Cipher mode Command from MSC failed - PM on page 12-20.
• 7. CELL: GPRS and baseband hopping configuration failure on page 12-21.
• 8. CELL: GPRS unavailable - No PRP available on page 12-23.
• 9. CELL: GPRS unavailable - No GDS available on page 12-24.
• 9. CELL: Intra-cell handover failed and recovered - PM on page 12-25.
• 10. CELL: GPRS unavailable - No cell (BVC) reset ack from the SGSN on page 12-27.
• 10. CELL: Intra-cell handover failed and mobile lost - PM on page 12-28.
• 11. CELL: GPRS unavailable - No cell (BVC) unblock ack from the SGSN on page 12-30.
• 11. CELL: Intra-BSS handover primary target cell blocked - PM on page 12-31.
• 12. CELL: GPRS unavailable - No PDCHs available on page 12-32.
• 13. CELL: GPRS unavailable - No GPRS capable carriers available on page 12-33.
• 13. CELL: Intra-BSS handover failed and recovered to org channel - PM on page 12-34.
• 14. CELL: Intra-BSS handover failed and mobile lost - PM on page 12-36.
• 14. CELL: GPRS unavailable - PBCCH timeslot out of sync on page 12-38.
68P02901W26-S 12-1
Nov 2007
Procedure Chapter 12: CELL Alarms
• 15. CELL: EGPRS unavailable - No EGPRS carriers available on page 12-39.
• 15. CELL: Inter-BSS handover, MS handover failed message received PM on page 12-40.
• 16. CELL: EGPRS unavailable - Insufficient GDS available on page 12-42.
• 17. CELL: GPRS unavailable on page 12-43.
• 18. CELL: Handover failure to the MSC due to all possible errors except no channels -
PM on page 12-45.
• 18. CELL: EGPRS unavailable on page 12-47.
• 19. CELL: EGPRS unavailable - No 64 K PDCHs available on page 12-48.
• 19. CELL: Bad handover reference numbers from the MS - PM on page 12-49.
• 20. CELL: Number of calls queued - PM on page 12-51.
• 22. CELL: Mobile assign command to MS blocked (No channel available) - PM on page
12-53.
• 23. CELL: Mobile assignment failure from MS - PM on page 12-55.
• 24. CELL: PCH queue page discard - PM on page 12-57.
• 25. CELL: Attempt at allocating a TCH failed - PM on page 12-59.
• 28. CELL: TCH pre-emption failure - PM on page 12-61.
12-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to CELL alarms
Introduction to CELL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The BSS supports the following new cell alarms:

• GPRS Unavailable.
• EGPRS Unavailable.
This section describes Alarms requirements necessary to support Full GSM Cell ID.
The BSS sends Full GSM Cell ID (MCC, MNC, LAC, CI) over the OMC <=> BSS interface for
functional unit list involving a cell.
CELL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CELL device.
68P02901W26-S 12-3
Nov 2007
0. CELL: Flow control procedure has started barring normal calls from access classes 0-9 Chapter 12: CELL Alarms
0. CELL: Flow control procedure has started barring

normal calls from access classes 0-9
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The flow control procedure for a cell is initiated for MS access classes 0 through 9. Flow control
is initiated when the BSS is congested. The purpose of the procedure is limiting the number of
new calls from access classes 0 through 9.
System action
The access classes (0-9) are gradually barred from the affected cell. An update is broadcast
to the MSs using BCCH messages.
One of the reason codes shown in Table 12-1 appears in the Additional information field of
the alarm output.
Table 12-1 Reason codes
Reason Code Denition

1 The alarm was generated when the percentage of
call information blocks reached the user-specified
threshold of the ssm_normal_overload_threshold or
ssm_critical_overload_threshold SSM parameters.
2 The alarm was generated due to RACH or AGCH congestion.
3 The alarm was generated when the percentage usage of
traffic channels reached the user-specified threshold of the
tch_busy_norm_threshold or tch_busy_critical_threshold
TCH parameters.
12-4 68P02901W26-S
Nov 2007
Refer to the GSM manual, Technical Description: BSS Command Reference,

(68P02901W23) for a description of the SSM and TCH parameters.
Possible causes

• The call traffic volume within a cell reached a critical level.
• The BSS is congested.
Procedure
Determine the traffic level on the cell. Depending on the traffic level the following inferences
can be drawn:
Procedure 12-1 Flow control procedure has started barring normal calls from access
classes 0-9
If... Then...
high The system is operating correctly.
Wait until the traffic level falls
below the levels specified for the
levels specified for the congestion
threshold database parameters.
not busy-unlocked A hardware problem probably
exists on the system. Initiate
isolation and corrective actions to
return the hardware components
to service.
68P02901W26-S 12-5
Nov 2007
0. CELL: Radio frequency losses while using an SDCCH - PM Chapter 12: CELL Alarms
0. CELL: Radio frequency losses while using an SDCCH

- PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The RF_LOSSES_SD statistic threshold has been reached.
This statistic counts the number of calls lost while using an SDCCH due to RF problems. If a
TCH is reconfigured as an SDCCH, only the SDCCH statistics are configured.
Possible causes

• MS radio problems.
• System hardware faults.
12-6 68P02901W26-S
Nov 2007
Procedure
Determine if there are any currently active hardware alarms. To resolve the alarm, perform the
following procedure.
Procedure 12-2 Radio frequency losses while using an SDCCH - PM

currently active hardware Initiate isolation and
alarms corrective procedures for the
current hardware alarms.
After the hardware alarms are
cleared, clear the alarm.
no currently active hardware MSs are probably
alarms experiencing radio problems.
Clear the alarm.
68P02901W26-S 12-7
Nov 2007
1. CELL: Cell radio timeslot capacity loss Chapter 12: CELL Alarms
1. CELL: Cell radio timeslot capacity loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The first timeslot of a transceiver is placed OOS by operator action. This alarm notifies the
operator that the capacity of the cell has been reduced due to the action.
Possible causes
The first timeslot of a transceiver is placed OOS by operator action.
Procedure
Procedure 12-3 Cell radio timeslot capacity loss
There is no operator action required.
12-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. CELL: Attempt at allocating an SDCCH failed - PM
1. CELL: Attempt at allocating an SDCCH failed - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The ALLOC_SD_FAIL and CHAN_REQ_MS_FAIL. generate the CELL 1 PM alarm.
The ALLOC_SDCCH_FAIL statistic threshold has been reached.
This statistic counts the number of times that an attempt to seize a stand-alone Dedicated
Control Channel (SDCCH) was rejected because of SDCCH congestion.
When an attempt to allocate an SDCCH fails, an SDCCH reject message is sent to the MS in
response to that channel request.
Possible causes

• An SDCCH channel is not available for immediate assignment (allocation) due to call
traffic congestion.
• An SDCCH has not been designated as the destination SDCCH for a handover due to call
68P02901W26-S 12-9
Nov 2007
Procedure
Determine if there are any currently active hardware alarms. Perform the following procedure
to resolve the alarm:
Procedure 12-4 Attempt at allocating an SDCCH failed - PM

currently active hardware Initiate isolation and corrective
alarms procedures for the current
hardware alarms. After the
hardware alarms are cleared, clear
the alarm.
no currently active hardware MSs are probably experiencing
alarms radio problems. Clear the alarm.
12-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CELL: Radio subsystem software error - Detected page overow
2. CELL: Radio subsystem software error - Detected

page overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Radio Subsystem (RSS) detected a paging queue overflow for a specific paging group
within the last 5 minutes.
The contents of the Additional information field for this alarm are shown in Table 12-2.

first 0 – 81 The identifier of the paging group is expressed.
This identifier is derived from the IMSI of the
Mobile Station (MS) combined with the related
Common Control Channel (CCCH) configuration.
The entire paging group shares the same transmission block
of the CCCH for the purpose of receiving pages.
second 00 – 255 The number of pages that have been lost within the last
5 minutes due to a paging queue overflow for the paging
group identified in byte 1.
Possible causes
The number of control channels allocated for the cell is insufficient to handle the paging traffic.
68P02901W26-S 12-11
Nov 2007
Procedure
Perform the following step to resolve the alarm:
Procedure 12-5 Radio subsystem software error - Detected page overow
12-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CELL: Channel request from MS blocked - PM
2. CELL: Channel request from MS blocked - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MA_CMD_TO_MS_BLKD statistic threshold has been reached.
This statistic tracks the number of times an MS has been refused access to a traffic channel
(TCH). When a channel request from an MS is refused, an immediate assignment reject message
is sent to the MS on a Common Control Channel (CCCH).
Possible causes

• An SDCCH channel is not available for immediate assignment (allocation) due to call
• An SDCCH has not been designated as the destination SDCCH for a handover due to call
• A TCH is not available due to call traffic congestion.
68P02901W26-S 12-13
Nov 2007
Procedure
Depending upon the condition perform the following procedure.
Procedure 12-6 Channel request from MS blocked - PM

alarms procedures for the current hardware
alarms. After the hardware alarms
are cleared, clear the alarm.
no currently active hardware The call volume exceeds the SDCCH
alarms and/or TCH for the cell. If this
alarm recurs, the number of SDCCH
and/or TCH channels require to be
increased. Clear the alarm.
12-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. CELL: Last NS-VC failed
3. CELL: Last NS-VC failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The last NS-VC (PVC) in a Cell has failed.
This alarm is not reported if the associated Gb Link (GBL) between the BSS and the Serving
GPRS Support Node (SGSN) has failed.
This is a GPRS service affecting fault condition.
The GSM Cell Identifier is displayed in the alarm output in the Additional information field.
Possible causes

• Frame Relay network problems.
• The SGSN blocked the NS-VC.
• An operator deleted the NS-VC.
68P02901W26-S 12-15
Nov 2007
Procedure
Perform the following procedure to resolve the alarm:
Procedure 12-7 Last NS-VC failed
1 Initiate fault isolation and resolution procedures for the frame network
connections.
12-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. CELL: Classmark update from MS protocol error - PM
4. CELL: Classmark update from MS protocol error - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The CLASSMK_UPDATE_FAIL statistic threshold has been reached.
This statistic counts the number of classmark updates from the MS containing protocol errors.
Possible causes
The MS equipment is changed without the operator's knowledge.
68P02901W26-S 12-17
Nov 2007
Procedure
to resolve the alarm:
Procedure 12-8 Classmark update from MS protocol error - PM

hardware alarms are cleared,
clear the alarm.
alarms protocol problems. Clear the
alarm.
12-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. CELL: No cell (BVC) block acknowledgment from the SGSN
5. CELL: No cell (BVC) block acknowledgment from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU has repeated the Cell BSSGP Virtual Connection (BVC) Block message the maximum
number of times without receiving an acknowledgment from the Serving GPRS Support Node
(SGSN).
The GSM Cell Identifier is displayed in the alarm output in the Additional information field.
Possible causes

• A protocol error has occurred.
• The SGSN did not send an acknowledgment message.
• Frame Relay network problems are occurring.
Procedure
Perform the following steps:
Procedure 12-9 No cell (BVC) block acknowledgment from the SGSN
1 Initiate fault isolation and resolution procedures at the SGSN, including

verification of the BVC end-to-end connections.
2 After the fault at the SGSN is resolved, clear the alarm.
68P02901W26-S 12-19
Nov 2007
6. CELL: Cipher mode Command from MSC failed - PM Chapter 12: CELL Alarms
6. CELL: Cipher mode Command from MSC failed - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The CIPHER_MODE_FAIL statistic threshold has been reached.
This statistic uses a timer, in order to detect, when an MS has failed to respond properly to a
cipher mode command message from the BSS within the required period of time. This statistic
is incremented each time the internal Motorola-defined timer in the BSS has expired.
For further information, refer to the Cell statistics chapter in the Maintenance Information:
GSM Statistics Application (68P02901W56) manual.
Possible causes
The MS did not switch correctly into encrypted communication mode when instructed.
Procedure
Depending upon the condition perform the following procedure:
Procedure 12-10 Cipher mode command from MSC failed - PM

currently active hardware Initiate isolation and corrective procedures
alarms for the current hardware alarms. After
the hardware alarms are cleared, clear the
alarm.
no currently active hardware MSs are probably experiencing protocol
alarms problems. Clear the alarm.
12-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. CELL: GPRS and baseband hopping conguration failure
7. CELL: GPRS and baseband hopping conguration

failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The baseband hopping configuration has failed as the GPRS is enabled and some of the
transceiver units in the cell do not support GPRS data.
The GSM cell identifier and a list of the DRIs that do not support GPRS data is displayed in the
Additional information field. The format is shown in the following example.
Example: CELL ID: 001 01 1 1; DRI IDs: 0 0, 1 0, 2 0, and so on.
Possible causes
Baseband hopping is enabled and all of the transceiver units in the cell do not support GPRS
data.
68P02901W26-S 12-21
Nov 2007
Procedure
Procedure 12-11 and Procedure 12-12 explain the steps to resolve this alarm.
Procedure 12-11 Replace transceiver units
Send a field representative to the site to replace all the transceiver units
that do not support GPRS with the transceiver units that do support GPRS.

Procedure 12-12 Disable baseband hopping
If replacement is not possible, disable baseband hopping.
12-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. CELL: GPRS unavailable - No PRP available
8. CELL: GPRS unavailable - No PRP available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Service quality
Description
GPRS is unavailable in this cell, as there is no available PRP. The alarm is cleared if the alarm
condition is resolved or if GPRS is disabled for the cell.
Possible causes
It is possible that the current In Service PRPs cannot support all the equipped cells due to
overload of the configured timeslots.
Procedure
Perform the following procedure to replace the transceiver units:
Procedure 12-13 GPRS unavailable - No PRP available
1 Check if there are disabled PRPs in the system.

2 Check if the system needs more PRPs to be equipped.
68P02901W26-S 12-23
Nov 2007
9. CELL: GPRS unavailable - No GDS available Chapter 12: CELL Alarms
9. CELL: GPRS unavailable - No GDS available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
GPRS is unavailable in this cell, as no GDS is available. The alarm is cleared if the alarm
condition is resolved or if GPRS is disabled for the cell.
Possible causes
It is possible that the current In Service GDSs cannot support all the equipped cells due to
overload of the configured timeslots.
Procedure
Procedure 12-14 GPRS unavailable - No GDS available
1 Check if there are disabled GDSs in the system.

2 Check if the system needs more GDSs to be equipped.
12-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. CELL: Intra-cell handover failed and recovered - PM
9. CELL: Intra-cell handover failed and recovered - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The INTRA_CELL_HO_RETURN scenario for the INTRA_CELL_HO statistic threshold has

been reached.
This statistic counts the number of times the channel assignment failure messages the BSS
receives, when an intra-cell handover has failed and the origination cell recovers the call.
Possible causes

• The database contains an invalid data that causes an invalid cell to be specified for a
handover.
• The wait period set for the MS to move from the origination cell to the destination cell in
a handover is too short.
Procedure
Determine if the cell parameters are correct and perform the following procedure:
68P02901W26-S 12-25
Nov 2007
Procedure 12-15 Intra-cell handover failed and recovered PM
If the cell parameters... Then...

are correct Clear the alarm.
are not correct Change the parameters as
required and then clear the alarm.
12-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10.
CELL: GPRS unavailable - No cell (BVC) reset ack from the SGSN
10. CELL: GPRS unavailable - No cell (BVC) reset ack

from the SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
GPRS is unavailable in this cell, as there was a failure to reset point-to-point BVC with SGSN.
The alarm is cleared if the alarm condition is resolved or if GPRS is disabled for the cell.
Possible causes
There is no ACK from the SGSN. This error indicates Frame Relay or SGSN problems.
Procedure
Procedure 12-16 GPRS unavailable - No cell (BVC) reset ack from the SGSN
1 Investigate why BVC could not be reset.

2 Take appropriate action and resolve the alarm.
68P02901W26-S 12-27
Nov 2007
10. CELL: Intra-cell handover failed and mobile lost - PM Chapter 12: CELL Alarms
10. CELL: Intra-cell handover failed and mobile lost -

PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The INTRA_CELL_HO_LOSTMS cause for the INTRA_CELL_HO statistic threshold has

been reached.
This statistic counts the number of times an MS has failed to return to the origination cell to
resume service in the event that an intra-cell handover has failed. The call is lost before the
intra-cell handover timer has expired.
Possible causes
The MS did not respond to the assignment command from the BSS before the expiration of the
intra-cell handover timer.
12-28 68P02901W26-S
Nov 2007
Procedure
Determine if there are any currently active DRI alarms. Follow the steps as described in
Procedure 12-17:
Procedure 12-17 Intra-cell handover failed and mobile lost - PM

currently active DRI alarms Initiate isolation and corrective
procedures for the current DRI
alarms. After the DRI alarms are
no currently active DRI alarms Clear the alarm.
68P02901W26-S 12-29
Nov 2007
11. CELL: GPRS unavailable - No cell (BVC) unblock ack from the SGSN Chapter 12: CELL Alarms
11. CELL: GPRS unavailable - No cell (BVC) unblock

ack from the SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
GPRS is unavailable in this cell, as there was a failure to unblock point-to-point BVC with SGSN.
The alarm is cleared if the alarm condition is resolved or if GPRS is disabled for the cell.
There is no additional information for this field.
Possible causes
No ACK from the SGSN. This error indicates Frame Relay or SGSN problems.
Procedure
Procedure 12-18 GPRS unavailable - No cell (BVC) unblock ack from the SGSN
1 Investigate why the BVC could not be unblocked.

2 Take appropriate corrective action and resolve the alarm.
12-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. CELL: Intra-BSS handover primary target cell blocked - PM
11. CELL: Intra-BSS handover primary target cell

blocked - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The OUT_INTRA_BSS_HO_PRI_BLK cause for the OUT_INTRA_BSS_HO statistic threshold

has been reached.
This statistic counts the number of times the primary target for an intra-BSS handover was
blocked because no channels were available within the cell.
Possible causes
The SDCCH and/or TCH capacity for the cell is not large enough to handle the call volume.
Procedure
Determine if the number of SDCCH and/or TCH channels for the cell is correct. Perform the
following procedure as described in Procedure 12-19:
Procedure 12-19 Intra-BSS handover primary target cell blocked - PM

68P02901W26-S 12-31
Nov 2007
12. CELL: GPRS unavailable - No PDCHs available Chapter 12: CELL Alarms
12. CELL: GPRS unavailable - No PDCHs available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
GPRS is unavailable since all the PDCHs in the cell are out of service and/or the PDCHs are
out of sync.
None.
Possible causes
The PDCHs in the cell are out of service.
Procedure
Procedure 12-20 GPRS unavailable - No PDCHs available
1 Investigate why the PDCHs are out of service.

12-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. CELL: GPRS unavailable - No GPRS capable carriers available
13. CELL: GPRS unavailable - No GPRS capable carriers

available
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
GPRS is unavailable in this cell, as there was no available GPRS capable carriers. The alarm is
cleared if the alarm condition is resolved or if GPRS is disabled for the cell.
Possible causes
There are two Possible causes:

• In Service (INS) GPRS capable carriers are not available.
• GPRS BCCH carrier use is restricted and the BCCH is the only GPRS capable carrier
remaining in the cell.
Procedure
Procedure 12-21 GPRS unavailable - No PDCHs Available
1 Investigate why GPRS is no longer available in the cell and take appropriate
corrective action.
2 Reset BCCH to be a GPRS carrier.
68P02901W26-S 12-33
Nov 2007
13. CELL: Intra-BSS handover failed and recovered to org channel - PM Chapter 12: CELL Alarms
13. CELL: Intra-BSS handover failed and recovered to

org channel - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The OUT_INTRA_BSS_HO_RETURN cause for the OUT_INTRA_BSS_HO statistic threshold

has been reached.
This statistic counts the number of channel assignment failure messages that the BSS receives,
when an intra-BSS handover has failed and the origination cell recovers the call.
When an attempt to allocate a channel intended for an intra-BSS handover has failed, the MS
sends the BSS an assignment failure message, for a requested channel assignment.
Possible causes

• The database contains an invalid data that causes specifying an invalid cell for a handover.
12-34 68P02901W26-S
Nov 2007
Procedure
Procedure 12-22 Intra-BSS handover failed and recovered to org channel - PM
1 Determine if the neighbor cell list to verify that the originating cell
contains valid data.
If the neighbor cell list is... Then...
correct Go to step 2.
not correct Correct the originating cell data
as required and then go to step 2.
2 Determine if the length of time specified for the wait period timer
is correct.
If the length of time... Then...
is correct Clear the alarm.
is not correct Change the parameters as
68P02901W26-S 12-35
Nov 2007
14. CELL: Intra-BSS handover failed and mobile lost - PM Chapter 12: CELL Alarms
14. CELL: Intra-BSS handover failed and mobile lost -

PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The OUT_INTRA_BSS_HO_LOSTMS cause for the OUT_INTRA_BSS_HO statistic threshold

has been reached.
This statistic counts the number of channel assignment failure messages that the BSS receives,
when an intra-BSS handover has failed, but the origination cell does not recover the call.
When an attempt to allocate a channel intended for an intra-BSS handover has failed, the MS
sends the BSS an assignment failure message, for a requested channel assignment.
Possible causes

• The database contains an invalid data that causes specifying an invalid cell for a handover.
12-36 68P02901W26-S
Nov 2007
Procedure
Procedure 12-23 Intra-BSS handover failed and mobile lost - PM
1 Determine if the neighbor cell list to verify that the originating cell
contains valid data.
If the neighbor cell list is... Then...
correct Go to step 2.
not correct Correct the originating cell data
as required and then go to step 2.
is correct.
is correct Clear the alarm.
is not correct Change the parameters as
68P02901W26-S 12-37
Nov 2007
14. CELL: GPRS unavailable - PBCCH timeslot out of sync Chapter 12: CELL Alarms
14. CELL: GPRS unavailable - PBCCH timeslot out of

sync
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: An external process dictates when fault is

cleared
Description
GPRS is unavailable in this cell, because the Packet Broadcast Control Channel (PBCCH)
timeslot is out of synchronization.
Possible causes
The PBCCH timeslot is out of synchronization.
Procedure
Procedure 12-24 GPRS unavailable - PBCCH timeslot out of sync
1 Check why the PBCCH is out of synchronization.

2 Take the necessary corrective action and resolve the alarm.
12-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. CELL: EGPRS unavailable - No EGPRS carriers available
15. CELL: EGPRS unavailable - No EGPRS carriers

available
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC - This alarm is cleared when other

EGPRS carriers become in-service or GPRS is
disabled for the cell and if the cell is in-service
at the end of the reconfiguration, the alarm is
automatically cleared.
Category: Equipment
Description
EGPRS is unavailable in this cell because there are no EGPRS capable carriers.
Possible causes
Lack of available CTU2 DRIs.
Procedure
Resolve the alarm as follows:
Procedure 12-25 EGPRS unavailable – No EGPRS carriers available
1 Physically equip CTU2 DRIs.

2 Fix any out-of-service CTU2 DRIs.
3 Remove the single-density restriction on CTU2 with EGPRS service.
4 Systematically locking and unlocking the DRIs in an appropriate
manner until EGPRS service is restored in the cell.
68P02901W26-S 12-39
Nov 2007
15. CELL: Inter-BSS handover, MS handover failed message received PM Chapter 12: CELL Alarms
15. CELL: Inter-BSS handover, MS handover failed

message received PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The OUT_INTER_BSS_HO_LOSTMS cause for the OUT_INTER_BSS_HO statistic threshold

has been reached.
This statistic counts the number of times MS handover failure messages the BSS receives
during an inter-BSS handover.
This alarm does not imply that a call is lost, as the BSS that attempted to handover the call
recovers it.
Possible causes

• The cell designated for the inter-BSS handover is not available for immediate assignment,
due to call traffic congestion.
• The wait period set for the MS, to move from the origination cell to the destination cell in
a handover, is too short.
12-40 68P02901W26-S
Nov 2007
Procedure
Procedure 12-26 Inter-BSS handover, MS handover failed message received PM
1 Determine if the BSS, where the target cell is equipped, is

experiencing traffic congestion.
If the BSS is... Then...
experiencing traffic congestion Wait for traffic levels to return to
normal levels and then clear the
alarm.
not experiencing traffic Go to step 2.
congestion
is correct.
is correct Go to step 3.
is not correct Change the parameters as required
and then clear the alarm.
3 Determine if sufficient resources are available in the target cell.
If the resources... Then...
are sufficient Clear the alarm.
are not sufficient Add resources as required and
then clear the alarm.
68P02901W26-S 12-41
Nov 2007
16. CELL: EGPRS unavailable - Insufcient GDS available Chapter 12: CELL Alarms
16. CELL: EGPRS unavailable - Insufcient GDS

available
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: Alarm clears when the cell is configured for

EGPRS service
Description
The cell has no EGPRS service due to lack of available GDS resources.
This alarm is cleared for the following conditions such as last TRAU GDS OOS, last PRP OOS,
last GBL OOS, last GSL OOS, Cell OOS, when the BTS loses contact with the BSC, and so on.
Possible causes
Lack of in-service GDS E1s.
Procedure
Procedure 12-27 EGPRS unavailable - Insufcient GDS available
1 Investigate the lack of GDS resource.

2 Take corrective action and clear the alarm.
12-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 17. CELL: GPRS unavailable
17. CELL: GPRS unavailable

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The GPRS service is unavailable.
Try to find out the root cause of the problem as the recovery action for this alarm. If no other
GPRS Unavailable alarm (For example, No PRP available) is active, GPRS is toggled to attempt
to bring the GPRS back into service. The alarm clears if the GPRS then becomes available.
Possible causes
GPRS is not available due to a software problem. The problem is not one of the following:
• No PRP available.
• No GDS available.
• No Cell (BVC) Reset Ack from the SGSN.
• No Cell (BVC) Unblock Ack from the SGSN.
• No PDCHs available.
• No GPRS capable carriers available.
• PBCCH Timeslot Out of Sync.
• GPRS and base band hopping configuration failure.
68P02901W26-S 12-43
Nov 2007
Procedure
Procedure 12-28 GPRS unavailable
Send a field representative to the site to perform the fault diagnosis. Take
appropriate action and resolve the alarm.

12-44 68P02901W26-S
Nov 2007
CELL: Handover failure to the MSC due to all possible errors except no channels - PM
18. CELL: Handover failure to the MSC due to all

possible errors except no channels - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The HO_REQ_MSC_FAIL statistic threshold has been reached.
This statistic counts the number of times handover request failure messages the BSS sends to
the MSC, for causes other than the causes due to non-availability of channel resources.
These handover failure messages were sent to notify the MSC that the BSS could not reserve
the radio resource requested by the MSC.
Possible causes

• The cell designated for the handover is not available for immediate assignment (allocation)
due to the resource problems unrelated to the availability of traffic channels.
• The wait period (time) set for the MS to move from the origination cell to the destination
cell in a handover is too short.
68P02901W26-S 12-45
Nov 2007
Procedure
Procedure 12-29 Handover failure to the MSC due to all possible errors except
no channels - PM
1 Determine if the BSS where the target cell is equipped is

experiencing traffic congestion.
If the BSS is... Then...
experiencing traffic congestion Wait for traffic levels to return to
normal levels and then clear the
alarm.
not experiencing traffic Go to step 2.
congestion
is correct.
is correct Go to step 3.
is not correct Change the parameters as required
and then clear the alarm.
3 Determine if sufficient resources are available in the target cell.
If the resources... Then...
are sufficient Clear the alarm.
are not sufficient Add resources as required and
then clear the alarm.
12-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 18. CELL: EGPRS unavailable
18. CELL: EGPRS unavailable

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The EGPRS service is unavailable. The recovery action for this alarm involves finding out the
root cause of the problem. The alarm clears if EGPRS becomes available.
Possible causes
A software problem has caused EGPRS to be unavailable. The problem however is not one
of the following:
• No EGPRS capable carriers available.
• Insufficient GDS available.
Procedure
Procedure 12-30 EGPRS unavailable
Download the SWFM logs from all of the BTS, LCF, and PCU processors
to aid root cause analysis.
68P02901W26-S 12-47
Nov 2007
19. CELL: EGPRS unavailable - No 64 K PDCHs available Chapter 12: CELL Alarms
19. CELL: EGPRS unavailable - No 64 K PDCHs available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
EGPRS service is unavailable since all the 64 K PDCHs in the cell are out of service and/or
the 64 K PDCHs are out of synchronization.
Possible causes
The 64 K PDCHs in the cell are out of service.
Procedure
Perform the following step to resolve the alarm:
Procedure 12-31 EGPRS unavailable - No 64 K PDCHs available
Check the reason why 64 K PDCHs are unavailable and take necessary
action.
12-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 19. CELL: Bad handover reference numbers from the MS - PM
19. CELL: Bad handover reference numbers from the

MS - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The BAD_HO_REFNUM_MS statistic threshold has been reached.
This statistic counts the number of times that an MS has accessed a channel with a Handover
Reference Number which the BSS was not expecting.
When this alarm condition occurs, the Handover Reference Number field shows a non formatted
random number. The BSS compares only what it received with what it expected. The BSS can
make up to four comparisons for each logical handover detected for the Stand-alone Dedicated
Control Channel (SDCCH) processed at the BSS.
Possible causes
The MS hardware is faulty.
68P02901W26-S 12-49
Nov 2007
Procedure
Determine if there are any currently active hardware alarms. Resolve the alarm as follows:
Procedure 12-32 Bad handover reference numbers from the MS - PM

clear the alarm.
12-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. CELL: Number of calls queued - PM
20. CELL: Number of calls queued - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The CALLS_QUEUED statistic threshold has been reached.
This statistic counts the total number of calls queued for each cell on the BSS. Calls queued
count the channel assignment requests, but not the handovers. When this alarm occurs, one or
more cells are being overused or do not have the capacity for the area they cover.
Possible causes

• The Stand-alone Dedicated Control Channels (SDCCHs) is not available for immediate
assignment due to call traffic congestion.
• The parameters that establish the rate for paging requests is not set appropriately for the
paging traffic that the BSS currently receives.
• If TCH traffic is heavy, the Paging Channels (PCHs) have overloaded the paging queues.
Procedure
68P02901W26-S 12-51
Nov 2007
Procedure 12-33 Number of calls queued - PM

12-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. CELL:
Mobile assign command to MS blocked (No channel available) - PM
22. CELL: Mobile assign command to MS blocked (No

channel available) - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MA_CMD_TO_MS_BLKD statistic threshold has been reached.
This statistic counts the number of times the MSC requests, that the BSS should allocate radio
resources to an MS, has been refused.
When this alarm occurs, the request for a channel is not placed in queue at the BSS. And, the
assignment to a TCH is refused in the cell, because no radio resources are available in the BSS
for allocation.
When a channel request from the MSC is refused, an immediate channel assignment failure
message is sent to the MSC with the cause that no radio resource is available.
Possible causes

• An SDCCH channel is not available for immediate assignment due to call traffic congestion.
• A TCH is not available due to call traffic congestion.
68P02901W26-S 12-53
Nov 2007
Procedure
Determine if the number of SDCCH and/or TCH channels for the cell is correct. Resolve the
alarm as follows:
Procedure 12-34 Mobile assign command to MS blocked (No channel available) - PM

12-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. CELL: Mobile assignment failure from MS - PM
23. CELL: Mobile assignment failure from MS - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MA_FAIL_FROM_MS statistic threshold has been reached.
This statistic counts the number of times an MS has been refused channel assignment to a
TCH. This error occurs when the MS detects a lower software layer failure on the TCHs being
assigned before the Assignment Complete message is sent.
When a channel assignment for an MS is refused, an immediate assignment failure message is

sent to the BSS.
Possible causes

• A software failure on a lower layer during a call-set up has disrupted the channel
assignment.
• A software failure on a lower layer during an intra-cell handover up has disrupted the
channel assignment.
68P02901W26-S 12-55
Nov 2007
Procedure
Determine if there are any currently active hardware alarms as follows:
Procedure 12-35 Mobile assignment failure from MS - PM

clear the alarm.
12-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. CELL: PCH queue page discard - PM
24. CELL: PCH queue page discard - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCH_Q_PAGE_DISCARD statistic threshold has been reached.
The number of paging requests from the MSC has reached the maximum number of pages
permitted in the GSM Paging Channel (PCH) queue. This error occurs when the MSC sends the
paging requests faster than the requests the BSS can process. The BSS discards any new pages
into the cell and reports the alarm.
Possible causes

• The parameters that establish the rate for paging requests is not set appropriately for the
paging traffic that the BSS currently receives.
• If Traffic Channel (TCH) traffic is heavy, the PCH has overloaded the paging queue.
68P02901W26-S 12-57
Nov 2007
Procedure
The procedure to resolve this alarm may involve one or both of the following actions at the MSC
and the BSS. The operator must determine which of the actions provides the best results.
Modify the MSC paging strategy
Perform the following steps to resolve the alarm.
Procedure 12-36 Modify the MSC paging strategy
1 Modify the location area boundaries at the MSC to reduce the paging
requests for a cell.
2 Clear the alarm.
Change the CCCH Conguration
Procedure 12-37 Change the CCCH Conguration
1 Move SAACHs off the BCCH frequency to provide a higher concentration of

CCCHs and therefore more PCHs.
2 Clear the alarm.
12-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. CELL: Attempt at allocating a TCH failed - PM
25. CELL: Attempt at allocating a TCH failed - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The ALLOC_TCH_FAIL statistic threshold has been reached.
This statistic counts the number of unsuccessful allocations of a TCH within a cell for both call
origination and handover. Cases involving Immediate Assignment Reject are also included in
the count.
Possible causes

• A radio has gone OOS causing the traffic to shift to an in-service radio. This shift in
traffic causes congestion on the TCH. If the traffic is heavy, the result may cause a delay
in TCH allocation.
• The timeslots related to the TCH has gone OOS causing the traffic to shift to another
in-service timeslot. This shift in traffic causes congestion on the timeslots. If the traffic is
heavy, the result is a delay in TCH allocation.
• The TCH traffic is too heavy to allow TCH allocation.
68P02901W26-S 12-59
Nov 2007
Procedure
Procedure 12-38 Attempt at allocating a TCH failed - PM
1 Determine if the DRI is OOS.

If the DRI is alarm... Then...
busy-unlocked Clear the alarm.
2 Reset the DRI.
busy-unlocked Clear the alarm.
Clear the alarm after the
transceiver is replaced.

12-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. CELL: TCH pre-emption failure - PM
28. CELL: TCH pre-emption failure - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The TCH_PREEMPT_FAIL_NO_CAND statistic threshold has been reached. This statistic

measures the number of calls which can pre-empt and trigger pre-emption, but cannot find
a candidate to pre-empt.
When this alarm occurs, calls with pre-emption capabilities cannot be established within the cell.
Possible causes
The cell is full of HIGHER priority calls or calls which are not vulnerable to pre-emption.
68P02901W26-S 12-61
Nov 2007
Procedure
Procedure 12-39 TCH pre-emption failure - PM
1 Re-evaluate the capacity of the affected CELL. This reduces the number of
pre-emption events within the cell and therefore result in a lower level of
pegging of this alarm and a reduced chance of the alarm being raised.
2 Re-evaluate the priority level/PCI/PVI capabilities of the call groups. If the
CELL experiences periods of overload of higher priority or pre-emption of
non-vulnerable calls, it is possible that this alarm is raised. This is due to
a particular network event or due to the priority level/PCI/PVI capabilities
of the call groups. If the network event is a regular occurrence, the alarm
threshold should be adjusted to account for this, if applicable. Alternatively,
re-evaluation of the priority level/PCI/PVI capabilities of the call groups
is required.
Priority level/PCI/PVI capabilities are controlled by the network,

and not by the BSS.
12-62 68P02901W26-S
Nov 2007
Chapter
13
COMB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details Combiner alarms and includes the following alarm procedures:
• 0 - 4. COMB: Cavity 0 - 4 tuning error on page 13-3.
• 5. COMB: Link A sanity failure on page 13-6.
• 6. COMB: Link B sanity failure on page 13-8.
• 7. COMB: Power feed A failure on page 13-10.
• 8. COMB: Power feed B failure on page 13-12.
• 9. COMB: Full reset on page 13-14.
• 10. COMB: Partial reset on page 13-17.
• 11. COMB: Cavity 5 tuning error on page 13-20.
• 12. COMB: Cavity combining block 0 failure on page 13-23.
• 13. COMB: Cavity combining block 1 failure on page 13-25.
• 14. COMB: Processor A failure on page 13-27.
• 15. COMB: Processor B failure on page 13-29.
• 254. COMB: Device failure on page 13-31.
68P02901W26-S 13-1
Nov 2007
Introduction to COMB alarms Chapter 13: COMB Alarms
Introduction to COMB alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
COMB alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Remotely
Tuned Combiner (RTC) device and the Transmit Antenna-Transceiver Interface (TATI) Combiner
device.
FRUs
A COMB device can be equipped on one of the FRUs shown in Table 13-1.
Table 13-1 FRUs that can be equipped with the COMB device
FRU Description
900 RTC 900 MHz five cavity, remotely tunable combiner, type RTC hardware.
900 CCB 900 MHz six cavity, remotely tunable combiner, type CCB hardware.
TC B0 CCB Control Board 0.
TC B1 CCB Control Board 1.
900 CCB0 900 MHz Cavity Combining Block 0.
13-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0 - 4. COMB: Cavity 0 - 4 tuning error
0 - 4. COMB: Cavity 0 - 4 tuning error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the combiner cavities (0, 1, 2, 3 or 4) failed to tune correctly.

first 00 to FF The combiner address.
second third fourth fifth 00 to FF00 to FF00 to FF00 to The controlling DRI device
FF ID.
Possible causes

• The cavity tuning circuits failed.
• The combiner cavity is faulty.
• The antenna or antenna connections are faulty.
• The controlling DRI hardware is faulty.
68P02901W26-S 13-3
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiners. This delay allows sufficient time for the system to reset the DRI
and retune the combiner cavity.
Procedure 13-1 Cavity 0 - 4 tuning error
1 Determine if there are previous occurrences of this alarm.

If... Then...
yes There is an intermittent problem.
Send a field representative to the
no Go to step 2.
2 Determine if the alarm has cleared.
clear No further action is required.
If this alarm recurs, it indicates an
intermittent fault at the site.
3 Attempt to restore the combiner to service.
If the combiner... Then...
site to replace the combiner or the
transceiver unit.
13-4 68P02901W26-S
Nov 2007

68P02901W26-S 13-5
Nov 2007
5. COMB: Link A sanity failure Chapter 13: COMB Alarms
5. COMB: Link A sanity failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Watchdog timer in the master Combiner device Processor A expired, causing the link
from the transceiver to the RTC to stop functioning. This alarm is reported using a redundant
communications link.
This alarm applies only to the RTC.
When this alarm is reported, the processor has failed and the standby combiner controller takes
over as the active combiner controller. If both links fail, the combiner and all transceivers
connected to this RTC are placed OOS.

second third fourth fifth 00 to FF00 to FF00 to FF00 to The controlling DRI device
FF ID.
Possible causes
Processor A on the RTC processor board failed.
13-6 68P02901W26-S
Nov 2007
Procedure
Procedure 13-2 Link A sanity failure
1 Determine the status of the combiner.

If... Then...
busy-unlocked No further action is required.
If this alarm recurs, send a
field representative to the site
to replace the combiner or the
transceiver unit.
If this alarm recurs, it indicates
that an intermittent fault exists at
the site.
transceiver unit.

68P02901W26-S 13-7
Nov 2007
6. COMB: Link B sanity failure Chapter 13: COMB Alarms
6. COMB: Link B sanity failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Watchdog timer in the master Combiner device Processor B expired causing the link from
the transceiver to the RTC to stop functioning. This alarm is reported using a redundant
communications link.
This alarm applies only to the RTC.
When this alarm is reported, the processor has failed and the standby combiner controller takes
over as the active combiner controller. If both links fail, the combiner and all the transceivers
connected to this RTC are placed OOS.

second third fourth fifth 00 to FF00 to FF00 to FF00 The controlling DRI device ID.
to FF
Possible causes
Processor B on the RTC processor board failed.
13-8 68P02901W26-S
Nov 2007
Procedure
Procedure 13-3 Link B sanity failure
1 Determine the status of the combiner.

If... Then...
If this alarm recurs, send a
to replace the combiner or the
transceiver unit.
the site.
transceiver unit.

68P02901W26-S 13-9
Nov 2007
7. COMB: Power feed A failure Chapter 13: COMB Alarms
7. COMB: Power feed A failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The main power feed A to the combiner has failed.
A combiner has two power feeds. They are A (main) and B (redundant). The combiner continues
to operate as long as the redundant power feed is available.
System action
If both power feeds have failed, the combiner is placed OOS.

second third fourth fifth 00 to FF00 to FF00 to FF00 to The controlling DRI device ID.
FF
13-10 68P02901W26-S
Nov 2007
Possible causes

• The dc power feed to the combiner has failed.
• The RTC processor board has failed.
• The TATI Control Board (TCB) has failed.
• The external combiner fuse has failed.
• A CCB/TCB fuse has failed.
Procedure
Procedure 13-4 Power feed A failure
1 Send a field representative to the site to determine the cause of the alarm.
If IAS alarms are present from the site, investigate the IAS alarms
before sending a field representative to the site.

68P02901W26-S 13-11
Nov 2007
8. COMB: Power feed B failure Chapter 13: COMB Alarms
8. COMB: Power feed B failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The redundant power feed B to the combiner has failed.
A combiner has two power feeds. They are A (main) and B (redundant). The combiner continues
to operate as long as the main power feed is available.
System action
If both power feeds have failed, the combiner is placed OOS.

to FF
13-12 68P02901W26-S
Nov 2007
Possible causes

• The dc power feed to the combiner has failed.
• The RTC processor board has failed.
• The TATI Control Board (TCB) has failed.
• The external combiner fuse has failed.
• A CCB/TCB fuse has failed.
Procedure
Procedure 13-5 Power feed B failure
If IAS alarms are present from the site, investigate the IAS alarms
before sending a field representative to the site.

68P02901W26-S 13-13
Nov 2007
9. COMB: Full reset Chapter 13: COMB Alarms
9. COMB: Full reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The combiner experienced a full reset. This alarm applies to both RTCs and TATI combiners.
This alarm is not reported if an MMI command initiates the reset.

to FF
13-14 68P02901W26-S
Nov 2007
Possible causes

• A momentary power outage has occurred.
• The combiner autonomously has forced a full reset.
• The reset switches on the combiner were placed into the full reset position.
Procedure
of the combiner. This delay allows sufficient time for the system to re-initialize the
combiner, reset the DRIs, and retune the combiner cavities.
Procedure 13-6 Full reset
1 Determine if on site maintenance is currently being performed.

If on site maintenance... Then...
is being performed Go to step 2.
is not being performed Go to step 4.
2 Contact on site personnel to determine if any procedures were
performed that would have affected the power supply to the combiner
or the combiner itself.
If on site procedures... Then...
caused the alarm Go to step 3.
3 Wait until the on site procedure is completed and the condition that
caused the alarm no longer exists, and then go to step 4.
Continued
68P02901W26-S 13-15
Nov 2007
Procedure 13-6 Full reset (Continued)

4 Determine the state of the combiner.
If... Then...
If this alarm recurs, it
indicates that an intermittent fault
exists at the site. Send a field
representative to determine the cause
of the alarm and take appropriate
action.
site to check the power connections,
combiner links and/or replace the
combiner.
5 Determine the state of the controlling DRIs.
If... Then...
busy-unlocked The fault condition no longer exists.
No further action is required.
not busy-unlocked Troubleshoot the DRI fault condition.

13-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. COMB: Partial reset
10. COMB: Partial reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The combiner has experienced a partial reset. This alarm applies to the RTC only.

to FF
Possible causes

• The combiner autonomously forced a partial reset.
• The reset switches on the combiner were placed into a partial reset position.
68P02901W26-S 13-17
Nov 2007
Procedure
Wait for at least two minutes after the alarm is initially reported before continuing.
This delay allows time for the combiner to complete the partial reset.
Procedure 13-7 Partial reset
1 Determine if on site maintenance is currently being performed.

If on site maintenance... Then...
is being performed Go to step 2.
is not being performed Go to step 4.
2 Contact on site personnel to determine if any procedures were
performed that would have affected the combiner.
If on site procedures... Then...
caused the alarm Go to step 3.
3 Wait until the on site procedure is completed and the condition that
caused the alarm no longer exists and then go to step 4.
4 Determine the state of the combiner.
If... Then...
If this alarm recurs, it indicates that
an intermittent fault exists at the
site. Send a field representative to
determine the cause of the alarm
site to check the power connections,
combiner links and/or replace the
combiner.
If... Then...
not busy-unlocked Troubleshoot the DRI fault condition.
13-18 68P02901W26-S
Nov 2007

68P02901W26-S 13-19
Nov 2007
11. COMB: Cavity 5 tuning error Chapter 13: COMB Alarms
11. COMB: Cavity 5 tuning error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Combiner cavity 5 failed to tune correctly.

to FF
Possible causes

• The cavity tuning circuit has failed.
• The combiner cavity is faulty.
• The antenna or antenna connections are faulty.
• The controlling DRI hardware is faulty.
13-20 68P02901W26-S
Nov 2007
Procedure
Procedure 13-8 Cavity 5 tuning error
1 Determine if there are previous occurrences of this alarm.

If... Then...
yes There may be an intermittent
problem. Send a field
no Go to step 2.
2 Determine if the alarm has cleared.
clear No further action is required.
the site.
transceiver unit.
68P02901W26-S 13-21
Nov 2007

13-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 12. COMB: Cavity combining block 0 failure
12. COMB: Cavity combining block 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TATI combiner CCB 0 failed. CCB 0 controls combiner cavities 0, 1 and 2. This alarm applies to
TATI combiners only.
System action
The DRIs attached to the affected combiner cavities are placed OOS.

to FF
Possible causes
The TATI COMB CCB 0 hardware failed.
68P02901W26-S 13-23
Nov 2007
Procedure
Attempt to restore the combiner to service. Perform the following procedure:
Procedure 13-9 Cavity combining block 0 failure

transceiver unit.

13-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. COMB: Cavity combining block 1 failure
13. COMB: Cavity combining block 1 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TATI combiner CCB 1 failed. CCB 1 controls combiner cavities 3, 4 and 5. This alarm applies to
TATI combiners only.
System action
The DRIs attached to the affected combiner cavities are placed OOS.

to FF
Possible causes
The TATI COMB CCB 1 hardware has failed.
68P02901W26-S 13-25
Nov 2007
Procedure
Attempt to restore the combiner to service.
Procedure 13-10 Cavity combining block 1 failure

the site.
site to replace the combiner.

13-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 14. COMB: Processor A failure
14. COMB: Processor A failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TATI Processor A failed due to a failure of TATI Control Board 0 (TCB 0).
This alarm applies to the TATI combiner only.

to FF
68P02901W26-S 13-27
Nov 2007
Possible causes Chapter 13: COMB Alarms
Possible causes

• The TCB 0 board failed.
• The TCB 0 board was removed.
Procedure
Procedure 13-11 Processor A failure

the site.

13-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. COMB: Processor B failure
15. COMB: Processor B failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TATI Processor B failed due to a failure of TATI Control Board 1 (TCB 1). This alarm is reported
using the primary communication link.
This alarm applies to the TATI combiner only.

to FF
68P02901W26-S 13-29
Nov 2007
Possible causes Chapter 13: COMB Alarms
Possible causes

• The TCB 1 board has failed.
• The TCB 1 board has been removed.
Procedure
Procedure 13-12 Processor B failure

the site.

13-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. COMB: Device failure
254. COMB: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The combiner was taken OOS by the Fault Management System.
When the transmit antenna is congured with multiple combiners, the loss of one of
the combiners may cause a loss in output power for some frequencies.
Possible causes
A fault translation by the Fault Management System.
68P02901W26-S 13-31
Nov 2007
Procedure
Perform the following to resolve the alarm:

the site.

If controlling DRIs are... Then...
not busy-unlocked Investigate and resolve the DRI
alarms. If resolution of the DRI
alarms does not clear this alarm,
go to step 3.

13-32 68P02901W26-S
Nov 2007
Chapter
14
CSFP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CSFP alarms and includes the following alarm procedures:
• 22. CSFP: SWFM indication on page 14-3.
• 35. CSFP: LAN connection failure on page 14-4.
• 47. CSFP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected

on page 14-6.
• 48. CSFP: Memory location is corrupt. Replace GPROC board on page 14-8.
• 49. CSFP: Code objects unavailable on page 14-9.
• 50. CSFP: EEPROM SW flash programming failure on page 14-11.
• 51. CSFP: EEPROM HW flash programming failure on page 14-12.
• 240. CSFP: PCMCIA card removed on page 14-13.
68P02901W26-S 14-1
Nov 2007
Introduction to CSFP alarms Chapter 14: CSFP Alarms
Introduction to CSFP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
CSFP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Code Storage
Facility Processor (CSFP) device.
FRUs
A CSFP device can be equipped on one of the FRUs shown in Table 14-1.
Table 14-1 FRUs that can be equipped with the CSFP device
FRU Description
GPROC BSC or InCell GPROC board.

GPROC2* BSC or InCell GPROC2 board.
GPROC3/GPROC3–2*
BSC or InCell GPROC3/GPROC3–2 board.
H2SC Horizon II macro Site Controller.
MCU M-Cell main control unit. The CSFP hardware device supported
by the CSFP software is the associated Personal Computer
Memory Card International Association (PCMCIA).
MCUF Horizon macro main control unit with dual FMUX. The CSFP
hardware device supported by the CSFP software is the
associated PCMCIA.
MCUm Horizon compact or Horizon compact2 or Horizon micro or
Horizon micro2 main control unit micro. The CSFP hardware
device supported by the CSFP software is the associated
PCMCIA.
*At the BSC, CSFP can only be GPROC2 or GPROC3/GPROC3-2.
14-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. CSFP: SWFM indication
22. CSFP: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system has detected a software processing error (SWFM) for a CSFP.
Possible causes
Procedure
Clear the alarm.
68P02901W26-S 14-3
Nov 2007
35. CSFP: LAN connection failure Chapter 14: CSFP Alarms
35. CSFP: LAN connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAN connection between the master GPROC and any other equipped CSFP on the LAN
has failed.
System action
The system places the CSFP OOS.
Possible causes

• The CSFP was reset through software or the front panel on site.
• A GPROC was reset by an SWFM with reason.
14-4 68P02901W26-S
Nov 2007
Procedure
Determine the state of the CSFP after the reset is completed.
If the CSFP is... Then...

required.

68P02901W26-S 14-5
Nov 2007
47. CSFP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 14: CSFP Alarms
47. CSFP: Unexpected board type: GPROC2 or {28337}

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or {28337}
CSFPs at the BSC can only be either GPROC2 or {28337} GPROC3/GPROC3–2. Everywhere
else in the system there can be any type of board.
Possible causes

board.
Procedure
14-6 68P02901W26-S
Nov 2007
Procedure 14-3 Unexpected board type: GPROC2 or GPROC3 expected
Send a field representative to the site to replace GPROC board with GPROC2
or {28337} GPROC3/GPROC3-2 board.

68P02901W26-S 14-7
Nov 2007
48. CSFP: Memory location is corrupt. Replace GPROC board Chapter 14: CSFP Alarms
48. CSFP: Memory location is corrupt. Replace GPROC

board
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates a possible memory location fault. It is not an immediate problem as the
GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
Possible causes

Procedure

14-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 49. CSFP: Code objects unavailable
49. CSFP: Code objects unavailable

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One (or more) devices have failed to load the code due to the code objects for this device not
being available.
All affected devices remain out of service at this site, resulting in a loss of capacity. This alarm
is tagged to the state transitions of DRIs failing to code load.
This alarm is generated for M-Cell6 and Horizon macro master cabinets.
If a redundant BTP is present, it must also have a PCMCIA.
This alarm indicates the likely cause of the fault; that is, missing card, presence of unsupported
or faulty card or objects missing from card.
Possible causes

• Removable flash media device is not present.
• Removable flash media device was inserted into BTS after the code download.
The code objects are stored only on the removable flash media device on the
MCU/MCUF platforms.
68P02901W26-S 14-9
Nov 2007
Procedure Chapter 14: CSFP Alarms
Procedure
Procedure 14-5 Code objects unavailable
1 Insert a removable flash media device into the BTS.

2 Reset the BTS to download the required objects.
14-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. CSFP: EEPROM SW ash programming failure
50. CSFP: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This error is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes

• An internal process makes an incorrect request.
Procedure
68P02901W26-S 14-11
Nov 2007
51. CSFP: EEPROM HW ash programming failure Chapter 14: CSFP Alarms
51. CSFP: EEPROM HW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This error is a generic flash programming error.
Possible causes
Procedure

2 To resolve the alarm, reset the CSFP and continue using it until it is possible
to replace the GPROC3 board.
14-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 240. CSFP: PCMCIA card removed
240. CSFP: PCMCIA card removed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The PCMCIA card was improperly removed from the slot on the MCU.
The PCMCIA card contains the software and firmware objects required to initialize the MCU.
The PCMCIA card facilitates a quick, on site download. If the PCMCIA card is not inserted, the
software and firmware objects are downloaded from the BSC. This activity is a substantially
slower process.
Possible causes
The PCMCIA card was removed before the CSFP was locked.
Procedure
Determine if on site maintenance is in progress at the site reporting the alarm. Carry out
the following to resolve the alarm:
Procedure 14-8 PCMCIA Card Removed
If on site maintenance is... Then...

being performed Contact the field representative
that is on site to re-insert the
PCMCIA card.
not being performed Send a field representative to the
68P02901W26-S 14-13
Nov 2007
Procedure Chapter 14: CSFP Alarms

14-14 68P02901W26-S
Nov 2007
Chapter
15
DHP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DHP alarms and includes the following alarm procedures:
• 1. DHP: EEPROM flash failure - No valid bootstrap code object present on page 15-4.
• 8. DHP: EEPROM flash object failure on page 15-6.
• 17. DHP: EEPROM flash programming failure on page 15-8.
• 21. DHP: EEPROM flash programming failure on page 15-10.
• 22. DHP: SWFM indication on page 15-12.
• 23. DHP: SYNC lost phase lock to master GCLK on page 15-13.
• 24. DHP: Bad clock source or SYNC OCXO (oscillator) replacement required on page 15-15.
• 25. DHP: SYNC warm up failure on page 15-17.
• 26. DHP: SYNC calibration request on page 15-19.
• 27. DHP: SYNC shutdown request on page 15-21.
• 28. DHP: SYNC clock output failure on page 15-23.
• 29. DHP: SYNC watchdog timer expired on page 15-25.
• 30. DHP: Clock A signal loss on page 15-27.
• 31. DHP: Clock B signal loss on page 15-29.
• 32. DHP: TDM interface failure - Assigned timeslot counter underflow on page 15-31.
• 33. DHP: TDM interface failure - Assigned timeslot counter overflow on page 15-33.
• 34. DHP: TDM interface failure - TDM parity error on page 15-35.
• 35. DHP: LAN connection failure on page 15-37.
• 39. DHP: Software failure on page 15-39.
• 40. DHP: Spurious interrupt on page 15-41.
• 43. DHP: SYNC not operational on page 15-43.
• 44. DHP: Firmware initiated SYNC calibration on page 15-45.
• 45. DHP: SYNC phase lock failure on page 15-46.
• 46. DHP: SYNC invalid mode on page 15-48.
68P02901W26-S 15-1
Nov 2007
Procedure Chapter 15: DHP Alarms
• 47. DHP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected

on page 15-50.
• 48. DHP: Memory location is corrupt. Replace GPROC board on page 15-52.
• 50. DHP: EEPROM SW flash programming failure on page 15-53.
• 51. DHP: EEPROM SW flash programming failure on page 15-54.
• 231. DHP: TDM interface configuration failure on page 15-55.
• 232. DHP: Processor bus communication failure on page 15-57.
• 234. DHP: Active link connection failure on page 15-58.
• 239. DHP: Process safe test audit failure on page 15-61.
• 254. DHP: Device failure on page 15-63.
15-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to DHP alarms
Introduction to DHP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
DHP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Digital Radio
Host Processor (DHP) device.
FRUs
A DHP device can be equipped on one of the FRUs shown in Table 15-1.
Table 15-1 FRUs that can be equipped with the DHP device
FRU Description
GPROC InCell GPROC board.
MCU Micro Control Unit board.
MCUF Main Control Unit with dual FMUX.
MCUm M-Cell micro Main Control Unit board.
ARENAm (MCU) Horizon micro (M-Cell arena) Main Control
Unit.
ARENA MAC (MCU) Horizon compact (M-Cell arena Macro) Main
Control Unit.
HORIZON MIC2 (MCU) Horizon micro2 Main Control Unit.
HORIZONCOM2 (MCU) Horizon compact2 Main Control Unit.
68P02901W26-S 15-3
Nov 2007
1. DHP: EEPROM ash failure - No valid bootstrap code object present Chapter 15: DHP Alarms
1. DHP: EEPROM ash failure - No valid bootstrap code

object present
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
Possible causes

15-4 68P02901W26-S
Nov 2007
Procedure
Perform the following step to reset the DHP.
Procedure 15-1 EEPROM ash failure - No valid bootstrap code object present

is cleared and does not recur The alarm condition has ceased.

68P02901W26-S 15-5
Nov 2007
8. DHP: EEPROM ash object failure Chapter 15: DHP Alarms
8. DHP: EEPROM ash object failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
Possible causes

15-6 68P02901W26-S
Nov 2007
Procedure

is cleared and does not recur The alarm condition has ceased.

68P02901W26-S 15-7
Nov 2007
17. DHP: EEPROM ash programming failure Chapter 15: DHP Alarms
17. DHP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem unless the GPROC is being reset, during which
Possible causes
15-8 68P02901W26-S
Nov 2007
Procedure
Perform the following to resolve the alarm:

68P02901W26-S 15-9
Nov 2007
21. DHP: EEPROM ash programming failure Chapter 15: DHP Alarms
21. DHP: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem until the GPROC is reset, during which time
Possible causes
Procedure
15-10 68P02901W26-S
Nov 2007

68P02901W26-S 15-11
Nov 2007
22. DHP: SWFM indication Chapter 15: DHP Alarms
22. DHP: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system has detected a software processing error (SWFM) for a DHP.
Possible causes
Procedure
Clear the alarm
15-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. DHP: SYNC lost phase lock to master GCLK
23. DHP: SYNC lost phase lock to master GCLK

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit in the MCU has lost phase lock to the reference master clock from the master
MCU.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes

• Noise on the HDLC link.
• The HDLC link is faulty.
68P02901W26-S 15-13
Nov 2007
Procedure
Determine if any link alarms have occurred at the same time when the phase lock was lost.
Procedure 15-6 SYNC lost phase lock to master GCLK
If link alarms... Then...

occurred at the same time There is a link fault. Troubleshoot
the link fault.
did not occur at the same time Send a field representative to the

15-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. DHP:
Bad clock source or SYNC OCXO (oscillator) replacement required
24. DHP: Bad clock source or SYNC OCXO (oscillator)

replacement required
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the following two possible fault conditions has occurred:

• The GCLK SYNC Oven-Controlled Crystal Oscillator (OCXO) has reached a synchronization
limit which adversely affects system performance.
• The clock reference source signal is out of specification.
OCXO ageing
If this alarm was generated because of OCXO ageing, the OCXO is no longer able to produce a
valid system clock signal.
68P02901W26-S 15-15
Nov 2007
Possible causes Chapter 15: DHP Alarms
Possible causes

• The OCXO is be aged to the point where it is no longer able to produce a valid system
clock signal.
• An incoming clock signal is out of specification.
Procedure
Determine if any link alarm has occurred at the same time when the phase lock was lost. To
identify them perform this step.
Procedure 15-7 Bad clock source or SYNC OCXO (oscillator) replacement required
If a link alarm... Then...

the link fault.

15-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. DHP: SYNC warm up failure
25. DHP: SYNC warm up failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuitry in the MCU did not warm up to the required operating temperature within
the specified warm-up time.
Possible causes
SYNC circuit failure.
Procedure
68P02901W26-S 15-17
Nov 2007
Procedure 15-8 SYNC warm up failure
Send a field representative to the site to replace the MCU.

15-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. DHP: SYNC calibration request
26. DHP: SYNC calibration request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit requests a recalibration of the clock at the MCU.
Possible causes

• Aging of clock circuitry.
• SYNC circuit failure.
68P02901W26-S 15-19
Nov 2007
Procedure
Determine if the MCU is being powered up for the first time or was recalibrated during the
previous 24-hour period. Carry out the following to resolve the alarm:
Procedure 15-9 SYNC calibration request
If the MCU is... Then...

being powered up for the first Wait 24 hours after the MCU has
time or was recalibrated during been powered up or recalibrated.
the previous 24-hour period If the alarm is not cleared after 24
hours, send a field representative
not being powered up for the Recalibrate the MCU GCLK.
first time or was recalibrated Wait 24 hours after the MCU has
during the previous 24-hour been powered up or recalibrated.
period If the alarm is not cleared after 24
hours, send a field representative

15-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. DHP: SYNC shutdown request
27. DHP: SYNC shutdown request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit requests a shutdown. The MCU is reset.
Possible causes
68P02901W26-S 15-21
Nov 2007
Procedure
Procedure 15-10 SYNC shutdown request

is cleared and does not recur The alarm condition does not exist.

15-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. DHP: SYNC clock output failure
28. DHP: SYNC clock output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit output clock failed. The MCU is reset.
Possible causes

• Degraded output signal.
68P02901W26-S 15-23
Nov 2007
Procedure
Procedure 15-11 SYNC clock output failure

is cleared and does not recur The alarm condition no longer
required.

15-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. DHP: SYNC watchdog timer expired
29. DHP: SYNC watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit generated a watchdog timer expiration. The MCU is reset.
Possible causes
68P02901W26-S 15-25
Nov 2007
Procedure
Procedure 15-12 SYNC watchdog timer expired
is cleared and does not recur The alarm condition no longer exists.
is not cleared or recurs Send a field representative to the site
to replace the MCU.

15-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. DHP: Clock A signal loss
30. DHP: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DHP has detected a TDM Clock A failure.
System action
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the DHP switches to the
redundant clock. If the redundant clock cannot be accessed, the active clock reference fails
and renders the site OOS.
Possible causes
The Clock A receive circuitry is faulty.
68P02901W26-S 15-27
Nov 2007
Procedure

is cleared and does not recur The alarm condition no longer exists.
to replace the MCU.

15-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. DHP: Clock B signal loss
31. DHP: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DHP has detected a TDM Clock B failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the DHP switches to the
Possible causes
The Clock B receive circuitry is faulty.
Procedure
68P02901W26-S 15-29
Nov 2007

is cleared and does not The alarm condition no longer exists.
recur No further action is required.
to replace the MCU.

15-30 68P02901W26-S
Nov 2007
DHP: TDM interface failure - Assigned timeslot counter underow
32. DHP: TDM interface failure - Assigned timeslot

counter underow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DHP has determined that the TDM highway is underused. Fewer switch-bound timeslots
are driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes

• The assigned timeslot counter register has failed.
• TDM interface problem.
68P02901W26-S 15-31
Nov 2007
Procedure
1 Determine the current state of the DHP.

If DHP is... Then...
required.
2 Reset the DHP.
The site is reset.

3 Determine the state of the DHP after the reset is completed.
required.

15-32 68P02901W26-S
Nov 2007
DHP: TDM interface failure - Assigned timeslot counter overow
33. DHP: TDM interface failure - Assigned timeslot

counter overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DHP has determined that the TDM highway is overused. More switch-bound timeslots are
Possible causes

• The assigned timeslot counter register has failed.
68P02901W26-S 15-33
Nov 2007
Procedure

required.
2 Reset the DHP.
The site is reset.

required.

15-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. DHP: TDM interface failure - TDM parity error
34. DHP: TDM interface failure - TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Possible causes

• The TDM interface circuitry on GPROC has failed.
• The TDM bus interface on a KSW/KSWX has failed.
• One or more signals of the TDM bus on the backplane has failed.
68P02901W26-S 15-35
Nov 2007
Procedure

required.
2 Reset the DHP.
The site is reset.

required.

15-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 35. DHP: LAN connection failure
35. DHP: LAN connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAN connection between the master GPROC and any other equipped DHP on the LAN
has failed.
System action
The system places the DHP OOS. If the DHP is the master GPROC, the site resets.
Possible causes

• The DHP was reset through a software or the front panel on site.
68P02901W26-S 15-37
Nov 2007
Procedure

2 Reset the DHP.
The site is reset.

If the DHP is... Then...
required.

15-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. DHP: Software failure
39. DHP: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DHP experienced a non recoverable SWFM error.
System action
control is handed over to the redundant processor.
programmers.
Possible causes

• The DHP software is faulty.
68P02901W26-S 15-39
Nov 2007
Procedure
1 Determine the state of the DHP.

busy-unlocked The alarm is caused by a software error.
Contact a Motorola representative to
resolve the software error.
not busy-unlocked Send a field representative to the site
to replace the GPROC board.

15-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 40. DHP: Spurious interrupt
40. DHP: Spurious interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The DHP has received and acknowledged an interrupt message but has not received a response
from the device generating the interrupt.
Possible causes

• The timer on the DHP monitoring the MCAP Bus is faulty causing the wait timer to expire
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or other
cause.
68P02901W26-S 15-41
Nov 2007
Procedure
1 Reset the DHP.
The site is reset.

2 Determine the current state of the DHP after the reset is complete.
required.

15-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 43. DHP: SYNC not operational
43. DHP: SYNC not operational

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit is still in the initializing state instead of the operational state after the
initialization timer has expired. The MCU is reset.
Possible causes
68P02901W26-S 15-43
Nov 2007
Procedure
Procedure 15-21 SYNC not operational
1 Determine if the affected processor is the master processor.

If the affected processor... Then...
is the master processor Disable all of the DRI devices and
then go to step 2.
is not the master processor Go to step 2.
2 Reset the site.
3 If this alarm recurs and the standby processor is now active, send a
field representative to the site to replace the master MCU.

15-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 44. DHP: Firmware initiated SYNC calibration
44. DHP: Firmware initiated SYNC calibration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The OMC-R operator has requested a firmware-directed calibration of GCLK Synchronization

(SYNC) hardware.
The calibration is performed on the MCU SYNC circuit. No call processing can occur on the
affected MCU during the calibration process.
Possible causes
The OMC-R operator requested the calibration.
Procedure
Procedure 15-22 Firmware initiated SYNC calibration
1 This alarm condition does not require fault isolation or resolution.

2 The MCU is automatically reset by the system after the calibration has been
completed.
68P02901W26-S 15-45
Nov 2007
45. DHP: SYNC phase lock failure Chapter 15: DHP Alarms
45. DHP: SYNC phase lock failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The SYNC circuit has not phase locked to the master within a specified period of being set
up in the slave mode.
Possible causes

• Clock source is lost.
• Calibration of SYNC circuit was initiated.
• A faulty HDLC link.
15-46 68P02901W26-S
Nov 2007
Procedure
Determine if any link alarms occurred at the same time when phase lock was lost.
Procedure 15-23 SYNC phase lock failure

the link fault.

68P02901W26-S 15-47
Nov 2007
46. DHP: SYNC invalid mode Chapter 15: DHP Alarms
46. DHP: SYNC invalid mode

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SYNC circuit has completed hardware/firmware initialization and the warm-up of the MCU
GCLK. However, the SYNC function is reporting that the MCU GCLK is in an invalid operational
mode. As a result, the MCU GCLK cannot continue normal operation.
An automatic MCU hard reset is continuously attempted to try to bring the MCU GCLK module
in service.
Invalid operational modes
One of the following two invalid operational modes may be reported:

• The MCU GCLK is currently in a warm-up mode after it has already completed the warm-up.
• The standby MCU GCLK is in the fast tune state when a standby device should never
reach that mode.
Replace the SYNC circuitry.
15-48 68P02901W26-S
Nov 2007
Possible causes

• Ageing of clock circuitry.
• SYNC circuitry malfunction.
Procedure
Procedure 15-24 SYNC invalid mode

then go to step 2.
2 Reset the site.
3 If this alarm recurs and the standby processor is now active, send a
field representative to the site to replace the master MCU.

68P02901W26-S 15-49
Nov 2007
47. DHP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 15: DHP Alarms
47. DHP: Unexpected board type: GPROC2 or {28337}

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
If this error occurs in an InCell site, the GPROC board does not come into service. The maximum
number of timeslots a GPROC can use is 16. A GPROC2 or {28337} GPROC3/GPROC3–2 board
can use 8, 16 or 32 timeslots.
Possible causes

board.
If this error occurs in an InCell site, the GPROC board does not come into service.
15-50 68P02901W26-S
Nov 2007
Procedure
Procedure 15-25 Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2

expected

correct Send a field representative to
the site to replace the GPROC
board with a GPROC2 or {28337}
to step 2.
2 Reset the DHP.
The site is reset.

required.
not busy-unlocked Send a field representative to

68P02901W26-S 15-51
Nov 2007
48. DHP: Memory location is corrupt. Replace GPROC board Chapter 15: DHP Alarms
48. DHP: Memory location is corrupt. Replace GPROC

board
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates a possible memory location fault. It is not an immediate problem as the
GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
Possible causes

Procedure
Procedure 15-26 Memory location is corrupt. Replace GPROC board.

2 Contact the Motorola Local Office and arrange to replace the GPROC3
board at an appropriate time.
15-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. DHP: EEPROM SW ash programming failure
50. DHP: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This error is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes

• An internal process has made an incorrect request.
Procedure
to reload the BOOTROM object.
68P02901W26-S 15-53
Nov 2007
51. DHP: EEPROM SW ash programming failure Chapter 15: DHP Alarms
51. DHP: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This error is a generic flash programming error.
Possible causes
Procedure
1 This alarm does not render the board out of service.

2 To resolve the alarm, reset the DHP and continue using it until it is possible
15-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 231. DHP: TDM interface conguration failure
231. DHP: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DHP cannot be programmed for a designated timeslot on the TBUS.
System action
The system automatically resets the DHP. If the alarm recurs, the DHP is declared OOS.
Possible causes

• The GPROC board has failed.
• A software error has occurred.
the TDM highways.
68P02901W26-S 15-55
Nov 2007
Procedure
Determine the state of the DHP.

required.

15-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. DHP: Processor bus communication failure
232. DHP: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A DHP board device has lost the ability to communicate to the peripheral boards through
the MCAP bus.
Possible causes

• The front panel switch was disabled without the GPROC being reset.
• The part of the GPROC that supports the MCAP bus access has failed.
Clearing the alarm
Procedure
1 Attempt to bring back the DHP In Service (INS). If the device is back in
service, the alarm condition no longer exists and further fault isolation is not
required .If the device remains OOS, go to step 2.
2 Replace the DHP board.
68P02901W26-S 15-57
Nov 2007
234. DHP: Active link connection failure Chapter 15: DHP Alarms
234. DHP: Active link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The HDLC link connection has failed between the BTP on the master MCU and the DHP on
the slave MCU.
This alarm is generated only for Horizon micro2 and Horizon compact2 sites.
Possible causes

• Loss of clocking.
• HDLC disconnection.
15-58 68P02901W26-S
Nov 2007
Procedure
1 Determine if the Device Failure (DHP 254 or DRI 254) alarm was
received.
If this alarm is reported Then...
with...
a DRI 254 alarm Send a field representative to the
a DHP 254 alarm Send a field representative to the
neither a DRI 254 alarm nor a Go to step 2.
DHP 254 alarm
busy-unlocked or Go to step 4.
enabled-unlocked
not busy-unlocked or Attempt to return the DRI to
exists. If this is a recurrence
replace the transceiver unit.
busy-unlocked or The fault condition no longer
enabled-unlocked exists. If this is a recurrence of this
not busy-unlocked or Attempt to return the DHP to
Continued
68P02901W26-S 15-59
Nov 2007
Procedure 15-31 Active link connection failure (Continued)

exists. If this is a recurrence of this

15-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. DHP: Process safe test audit failure
239. DHP: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DHP has failed a process safe test audit. The process safe test audit verifies the proper
operation of internal software processes.
Table 15-2. Bytes one through eight is useful only to the programmers. Byte nine is the error
code for the alarm.

nine 00 The process that failed the audit is in an
infinite loop.
01 The cause for the failure was not
determined.
02 Higher priority processes prevented the
process that failed to run.
03 The cause for the failure was not
determined.
Possible causes

• A process running on the DHP has failed a safe test audit.
68P02901W26-S 15-61
Nov 2007
Procedure

field.
2 Go to step 2.
2 Perform the safe test audit on the DHP.
If the DHP... Then...
3 Reset the DHP.
The site is reset.

required.

15-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. DHP: Device failure
254. DHP: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DHP was rendered OOS by the GPROC Fault Management System, causing the site to reset.
A single byte is displayed in the Additional information field identifying the site reset type, as
shown in Table 15-3.
Value Denition
01 Hard reset.
02 Soft reset.
Possible causes
68P02901W26-S 15-63
Nov 2007
Procedure
Wait approximately 10 minutes after this alarm is received to allow the site to reset,

required.
2 Reset the DHP.
required.

15-64 68P02901W26-S
Nov 2007
Chapter
16
DPROC Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DPROC alarms and includes the following alarm procedures:
• 0. DPROC: Processor communication failure on page 16-3.
• 9. DPROC: DPROC reset detected on page 16-5.
• 22. DPROC: SWFM indication on page 16-7.
• 39. DPROC: Software failure on page 16-8.
• {28351} 88. DPROC: Max temperature exceeded on page 16-9.
• {28351} 92. DPROC: High temperature exceeded on page 16-10.
• 239. DPROC: Process safe test audit failure on page 16-11.
68P02901W26-S 16-1
Nov 2007
Introduction to DPROC alarms Chapter 16: DPROC Alarms
Introduction to DPROC alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
DPROC alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Packet
Control Unit (PCU) GPRS Data Processor (DPROC) device.
The DPROC is a non-system processor that can be configured as either a Packet Resource
Processor (PRP) or as a Packet Interface Control Processor (PICP).
FRUs
A DPROC device can be equipped on one of FRUs shown in Table 16-1.
Table 16-1 DPROC FRUs
FRU Description
FORCE DPROC A Force™ DPROC processor board.
Unknown DPROC A generic DPROC processor board.
16-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. DPROC: Processor communication failure
0. DPROC: Processor communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
No communications are possible with the DPROC board at the Packet Control Unit (PCU) within
the General Packet Radio Service (GPRS) system.
System action
When this alarm is reported, the DPROC is placed OOS and all devices supported by DPROC
are also placed OOS.
Possible causes

• The DPROC board has failed.
• The DPROC firmware is faulty.
• A board peripheral to the DPROC is faulty.
68P02901W26-S 16-3
Nov 2007
Procedure Chapter 16: DPROC Alarms
Procedure
Procedure 16-1 Processor communication failure
1 Determine the current state of the DPROC.

If the DPROC is... Then...
exists. Go to step 2.
not busy-unlocked Try to INS the DPROC. If this
fails to resolve the alarm, send a
field representative to the site to
replace the DPROC board.
2 Determine the current state of each of the devices supported by
the DPROC.
If the supported devices Then...
are...
not busy-unlocked Return the devices that are
not busy-unlocked to service.
If any devices do not return
to service, troubleshoot the
individual devices.

16-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. DPROC: DPROC reset detected
9. DPROC: DPROC reset detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The system detected a soft or hard reset of the DPROC board.
System action
When this alarm is reported, the DPROC is placed OOS and all devices supported by DPROC
are also placed OOS.
A single byte is displayed in the Additional information field indicating the reset type, as
Table 16-2 Reset type
Value Description
00 Soft reset
02 Hard reset
Possible causes

• The DPROC board has failed.
• The DPROC firmware is faulty.
• A board peripheral to the DPROC is faulty.
68P02901W26-S 16-5
Nov 2007
Procedure
Procedure 16-2 DPROC reset detected
1 Determine the current state of the DPROC.

site to replace the DPROC board.
2 Determine the current state of each of the devices supported by
the DPROC.
If the supported devices Then...
are...
not busy-unlocked Return the devices that are
not busy-unlocked to service.
If any devices do not return
to service, troubleshoot the
individual devices.

16-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. DPROC: SWFM indication
22. DPROC: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system detected a software processing error for a DPROC.
SWFM is a debugging tool for Motorola engineering.
The Additional information field includes process information useful only to the programmers.
Possible causes
A software error has occurred.
Procedure
1 Clear the alarm.

2 There is no additional OMC-R operator action required.
68P02901W26-S 16-7
Nov 2007
39. DPROC: Software failure Chapter 16: DPROC Alarms
39. DPROC: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DPROC has experienced a non recoverable SWFM error.
System action
The DPROC is reset.
{28351} The Additional information field includes the raw binary data of SWFM message
header and process information useful to the programmers. The Additional information field
length is 68.
Possible causes
A critical software error has occurred.
Procedure
There is no additional OMC-R operator action required.
16-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88. DPROC: Max temperature exceeded
88. DPROC: Max temperature exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28351}
Clearing Type: FMIC

Category: Enviroment
Description
This alarm is raised when the temperature of the DPROC exceeds the maximum temperature
threshold.
The additional information for this alarm is temperature data.
Possible causes
• Temperature of the cage environment is high.
• The load of the DPROC is heavy.
Procedure
Procedure 16-5 Max temperature exceeded
1 Remove airflow blockage to decrease the ambient room temperature.

2 Replace fault PSU/FAN units with the system operational document.
3 Remove some DPROCs from service (locking them).
68P02901W26-S 16-9
Nov 2007
92. DPROC: High temperature exceeded Chapter 16: DPROC Alarms
92. DPROC: High temperature exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28351}
Clearing Type: FMIC

Category: Environment
Denition
This alarm is generated when the temperature of the DPROC exceeds the high temperature
threshold.
The additional information is temperature data and the field length is 1.
Possible causes
• The fan housed in PSU has failed.
• Airflow blockage.
• Ambient room temperature is risen.
Procedure
Procedure 16-6
1 Remove airflow blockage to decrease the ambient room temperature.

2 Replace fault PSU/FAN units with the system operational document.
3 Remove some DPROCs from service (locking them).
16-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. DPROC: Process safe test audit failure
239. DPROC: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DPROC failed a process safe test audit. The process safe test audit verifies the proper
Table 16-3. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.

{28351} First The process ID of the process being audited.
Second and third The CPU number.
Fourth The percentage of CPU utilization by the
process being audited.
Fifth, Sixth, Seventh, The program counter which points to the
Eighth line of code the process was executing when
it failed the audit.
nine 00 The process that failed the audit is in an
infinite loop.
02 Higher priority processes prevented the
process that failed to run.
68P02901W26-S 16-11
Nov 2007
Possible causes Chapter 16: DPROC Alarms
Possible causes

• The DPROC board is faulty.
• The DPROC software being audited is faulty.
• The hardware being audited is faulty.
• The DPROC cabling is faulty.
Procedure

field.
2 Go to step 3.
0, 1, or 3 Go to step 3. (The DPROC is reset
by the system).
2 Reset the DPROC.
The DPROC is reset.

3 Determine the state of the DPROC after the reset is completed.
exists for error codes 0, 1, 3.
For error code 2, contact a
Motorola representative to resolve
the software error.
not busy-unlocked If a manual reset has not
been attempted, go to step 2.
Otherwise, send a field
replace the DPROC board.
16-12 68P02901W26-S
Nov 2007

68P02901W26-S 16-13
Nov 2007
16-14 68P02901W26-S
Nov 2007
Chapter
17
DRI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DRI alarms and includes the following alarm procedures:
• 2. DRI: Internal message error - Pointer misalignment on page 17-10.
• 3. DRI: Internal message error - Dual-port RAM segment full on page 17-13.
• 5. DRI: Superframe counter error (Uplink) on page 17-16.
• 6. DRI: Superframe counter error (Downlink) on page 17-18.
• 9. DRI: Channel coder internal message error on page 17-21.
• 10. DRI: Dual-port RAM error on page 17-24.
• 15. DRI: Initial synchronization of radio and GPRS channel failed on page 17-30.
• 18. DRI: Primary message or hardware interrupt error on page 17-36.
• 21. DRI: Calibration in progress on page 17-42.
• 22. DRI: Radio subsystem software to DRI communication error on page 17-43.
• 23. DRI: Radio subsystem software to DRI communication failure on page 17-45.
• 24. DRI: TDM interface failure - TDM parity error on page 17-47.
• 25. DRI: TDM interface failure - Assigned timeslot counter overflow on page 17-49.
• 26. DRI: TDM interface failure - Assigned timeslot counter underflow on page 17-51.
• 27. DRI: Clock A signal loss on page 17-53.
• 28. DRI: Clock B signal loss on page 17-55.
• 29. DRI: Processor failure on page 17-57.
• 30. DRI: Transceiver re-initialized unexpectedly on page 17-59.
68P02901W26-S 17-1
Nov 2007
Procedure Chapter 17: DRI Alarms
• 31. DRI: Critical resource exhausted on page 17-61.
• 32. DRI: RF unit primary sync signal lost on page 17-63.
• 33. DRI: RF unit HDSL link quality error on page 17-64.
• 34. DRI: RF unit reset on page 17-65.
• 35. DRI: Reset due to recurring fault on page 17-67.
• 36. DRI: Front end processor to radio subsystem software communication failure on page
17-69.
• 37. DRI: Hard reset on page 17-70.
• 38. DRI: BSS internal alarm only - FWFM displayed at EMON on page 17-72.
• 39. DRI: Synchronization loss with MCU on page 17-73.
• 40 - 47. DRI: Channel coder timeslot (0-7) failure on page 17-76.
• 48. DRI: Baseband hopping timeslot counter mismatch on page 17-78.
• 49. DRI: GSM timeslot counter mismatch on page 17-80.
• 50. DRI: Spurious GSM timeslot interrupt on page 17-82.
• 51. DRI: Baseband hopping TDM link error on page 17-84.
• 52. DRI: Baseband hopping GSM timeslot misalignment on page 17-86.
• 53. DRI: Channel coder 0 failure - Demodulation processor 0 failure on page 17-89.
• 54. DRI: Channel coder 0 Failure - Demodulation processor 1 failure on page 17-91.
• 57. DRI: Transceiver to DRI communication error on page 17-97.
• 59. DRI: Transceiver to DRI burst error on page 17-101.
• 60. DRI: Transceiver to DRI burst error on page 17-103.
• 64. DRI: Non recoverable error on page 17-111.
• 65. DRI: Radio subsystem software to DRI communication error - Checksum error on
page 17-113.
• 66. DRI: Superframe counter error on page 17-116.
17-2 68P02901W26-S
Nov 2007
• 67. DRI: Radio subsystem software to DRI communication error - DRI not responding on
page 17-119.
• 70. DRI: Equalizer control processor failure - Watchdog timer expired on page 17-121.
• 71. DRI: Unexpected communications bus interrupt on page 17-123.
• 72. DRI: Receiver failure on page 17-125.
• 73. DRI: High reverse power on page 17-127.
• 74. DRI: Cell transmit power unachievable on page 17-129.
• 76. DRI: Radio subsystem software to DRI communication error on page 17-132.
• 78. DRI: TX VSWR antenna fault on page 17-134.
• 80. DRI: Transmitter synthesizer failure on page 17-135.
• 85. DRI: Transmitter failure - Output power on page 17-147.
• 88. DRI: Power amplifier temperature high on page 17-153.
• 89. DRI: Power amplifier communication failure on page 17-156.
• 91. DRI: Power amplifier power low but functioning on page 17-160.
• 92. DRI: Power amplifier temperature high but functioning on page 17-162.
• 104 - 111. DRI: Timeslot 0-7 configuration failure on page 17-166.
• 112. DRI: Receiver synthesizer failure on page 17-168.
68P02901W26-S 17-3
Nov 2007
• 144. DRI: Transceiver to DRI communication failure on page 17-202.
• 150. DRI: Receive matrix failure on page 17-213.
• 151. DRI: Transceiver to combiner communication failure on page 17-215.
• 152. DRI: Control processor to power amplifier communication failure on page 17-217.
• 153. DRI: Control processor to equalizer communication failure on page 17-219.
• 154. DRI: Power supply failure on page 17-221.
• 156. DRI: Control processor message queue overflowed on page 17-225.
• 157. DRI: Receiver input overflowed on page 17-227.
• 158. DRI: Receiver input overflowed on page 17-229.
• 159. DRI: Equalizer output overflowed on page 17-231.
• 160. DRI: Equalizer output overflowed on page 17-233.
• 161. DRI: Transmitter out of synchronization on page 17-235.
• 162. DRI: Receive matrix branch 2 control link failure on page 17-237.
17-4 68P02901W26-S
Nov 2007
• 166. DRI: Control processor firmware failure on page 17-245.
• 167. DRI: Control processor configuration mismatch on page 17-247.
• 168. DRI: Equalizer configuration mismatch on page 17-249.
• 170. DRI: M-Cell micro interconnect failure on page 17-253.
• 171. DRI: Invalid calibration data on page 17-255.
• 176. DRI: Equalizer timeslot (0-7) failure on page 17-257.
• 184. DRI: Equalizer firmware failure on page 17-259.
• 192. DRI: Baseband hopping TDM link error on page 17-261.
• 193. DRI: Baseband hopping GSM timeslot misalignment on page 17-263.
• 203. DRI: RF unit power supply unit - Input failure on page 17-265.
• 204. DRI: RF unit over temperature on page 17-266.
• 205. DRI: RF unit low voltage disconnect imminent on page 17-267.
• 206. DRI: RF unit external alarm input on page 17-268.
• 207. DRI: Internal communication error on page 17-269.
• 208. DRI: Power amplifier temperature on page 17-270.
• 210. DRI: Hopping DRI failure on page 17-272.
• 211. DRI: Front end processor failure on page 17-274.
• 212. DRI: Channel coder failure on page 17-276.
• 213. DRI: Transceiver processor failure on page 17-278.
• 214. DRI: Equalizer failure on page 17-280.
• 215. DRI: Power amplifier failure on page 17-282.
• 216. DRI: Transceiver recovery failure on page 17-284.
• 217. DRI: Transmission suspended to conserve battery power on page 17-286.
• 218. DRI: Invalid transceiver calibration data on page 17-288.
• 219. DRI: GPRS not supported by radio on page 17-290.
• 221. DRI: Invalid in-call modification of destination channel type on page 17-291.
• 224. DRI: Safe test audit failure on page 17-293.
• 231. DRI: TDM interface configuration failure on page 17-296.
68P02901W26-S 17-5
Nov 2007
• 234. DRI: Active link connection failure on page 17-298.
• 235. DRI: Standby link connection failure on page 17-301.
• 236. DRI: Slow flash failure on page 17-303.
• 237. DRI: Non-volatile memory failure on page 17-305.
• 239. DRI: Process safe test audit failure on page 17-307.
• 241. DRI: Standby link connected to wrong device on page 17-310.
• 243. DRI: Unlocked device not in service on page 17-313.
• 254. DRI: Device failure on page 17-315.
17-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to DRI alarms
Introduction to DRI alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
DRI alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Digital Radio
Interface (DRI) device.
DRI alarms include both hardware and software alarms.
DRI alarms contain the full GSM Cell ID (MCC, MNC, LAC, CI) when transmitting cell
information. The hardware devices detect alarm conditions and report them to the GPROC
application software. In the GPROC software, the alarm indications are collected, translated
and the alarm messages are then sent to the OMC-R and/or the local MMI.
MCAP/TDM bus interface alarms and reporting
The DRIM is a Motorola Cellular Advanced Processor (MCAP) bus peripheral board with the
primary responsibility of channel encoding and decoding data. This data is transmitted to and
received from a Mobile Station (MS).
The direct control of a DRIM is through the MCAP bus. Inbound and outbound data use the
higher bandwidth Time Division Multiplex (TDM) bus. Many clock signals and counters are used
to maintain the integrity of these two buses.
FEP alarms and reporting
The alarm reporting protocol adopted by the Front End Processor (FEP) is to report the
alarm whenever a fault condition is detected. The DSP host interface and the dual-port RAM
messaging interfaces between the DRIM and the RSS are the reporting mechanisms used.
CCDSP alarms and reporting
The alarm reporting protocol adopted by the Channel Coding Digital Signal Processor (CCDSP)
is initially to report any error detected and to continue reporting that error every 6.12 s, until an
acknowledgment of the error is returned by the GPROC Fault Management (FM) software.
The duration between the reporting of CCDSP errors is one GSM superframe. However, the
reporting is not done on the actual superframe boundary. Once the error in question has been
acknowledged, the CCDSP does not report the error until explicitly instructed to do so by FM
software.
In any event, the TTY ports of all of the CCDSPs display a message when an error is detected;
the message states whether the error was reported. All CCDSP alarm reporting must pass
through the FEP.
68P02901W26-S 17-7
Nov 2007
FRUs Chapter 17: DRI Alarms
FRUs
For micro BTS installations, the FRU is the complete micro BTS unit.
A DRI device can be equipped on one of the FRUs shown in Table 17-1.
Table 17-1 FRUs that can be equipped with the DRI device
FRU BTS Description

DRIM InCell Digital Radio Interface Extended
Memory board.
ACM
RF Unit
TCU M-Cell Transceiver Control Unit for low
power transceivers (up to 16 W).
TCUm
TCUm (MRC)
TCUm (RFM)
TCU HI PWR M-Cell Transceiver Control Unit for
GSM 1800.
CTU Horizon Transceiver Control Unit.
CTU2 Horizon II macro Transceiver Control Unit.
TCU-B M-Cell Transceiver Control Unit for
TCU900-B series radio.
ARENA
ARENA MAC Horizon compact Horizon compact (M-Cell arena
Macro) Transceiver Control
Unit.
ARENA MAC (MRC) Horizon compact Micro Radio Control Unit in a
Horizon compact (M-Cell arena
Macro).
ARENA MAC (RFM) Horizon compact Radio Frequency Module in a
Horizon compact (M-Cell arena
Macro).
Continued
17-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R FRUs
Table 17-1 FRUs that can be equipped with the DRI device (Continued)
FRU BTS Description
HORIZONCOM2 (MRC) Horizon compact2 Micro Radio Control Unit in a
Horizon micro2.
HORIZONCOM2 (RFM) Horizon compact2 Radio Frequency Module in a
Horizon compact2.
HORIZONMIC2(RFM)
HORIZONMIC2(MRC)
HORIZONMIC2(SSN)
HORIZONCOM2(MRC)
68P02901W26-S 17-9
Nov 2007
2. DRI: Internal message error - Pointer misalignment Chapter 17: DRI Alarms
2. DRI: Internal message error - Pointer misalignment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The FEP detected that the DPRAM offset address contained in a Message Ready Indication
message did not match the address that the FEP was expecting. This action caused the RSS
and FEP software pointers to be misaligned.
This alarm is not reported.
Persistent fault alarm
If this alarm occurs six times within a certain time frame, it is classified as a persistent fault
alarm. The system resets the DRI generating the alarm and reports the Reset Due To Recurring
Fault (DRI 35) alarm.
If the condition to reset the DRI occurs three times within a 10 minute period, the system resets
the DRI and generates the DRI 35 alarm on the first two occurrences. On the third occurrence,
the system places the DRI OOS and generates the Device Failure (DRI 254) alarm.

first 00 - 09 The DPRAM segment number.
second 00 - 80 The DPRAM offset address where the
faultgenerating this alarm has occurred.
third 00 - 80
17-10 68P02901W26-S
Nov 2007
Possible causes

• A lost message.
• High call traffic causing DPRAM access rates to be different for the FEP and RSS.
Procedure
Procedure 17-1 Internal message error - Pointer misalignment
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
the BSS takes the DRI • Transceiver unit for a

OOS again as a result of the non-InCell BTS.
same alarm after the DRI
becomes busy-unlocked
If these alarms continue at an unacceptable rate, the BSS:
• Resets the DRI.

• Generates DRI 35 alarm.
68P02901W26-S 17-11
Nov 2007

17-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. DRI: Internal message error - Dual-port RAM segment full
3. DRI: Internal message error - Dual-port RAM

segment full
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The FEP has no more room in the specified DPRAM segment to place another RSS destined
message. The DPRAM is automatically reset when the alarm is generated.
If this alarm occurs frequently within a short period of time 1 - 6 hours), there may be a serious
fault condition.
This indicates the existence of a potentially service-affecting fault condition.

first 00 – 09 The DPRAM segment number.
second 00 – 80 The DPRAM offset address where
the fault generating this alarm has
third 00 – 80
occurred.
68P02901W26-S 17-13
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes

• An overflow of the DPRAM has occurred due to a large number of messages from either
the CCDSPs or the transceiver unit.
• A backlog in the DPRAM has occurred because the RSS software may have fallen behind
the FEP.
• A high volume of call messages.
Procedure
Procedure 17-2 Internal message error - Dual-port RAM segment full
1 Review the alarm logs to determine if other DRIs in the same cage
are also reporting this alarm.
If other DRIs are... Then...
reporting this alarm The site is overloaded. Analyze the
call traffic on the site. Go to step 2.
not reporting this alarm Go to step 3.
2 Wait until the traffic volume returns to normal levels.
recurs Go to step 3.
did not recur The fault condition no longer
exists.
3 Send a field representative to the site to replace the DRIM board (for
an InCell BTS) or the transceiver unit (for a non-InCell BTS).
17-14 68P02901W26-S
Nov 2007

68P02901W26-S 17-15
Nov 2007
5. DRI: Superframe counter error (Uplink) Chapter 17: DRI Alarms
5. DRI: Superframe counter error (Uplink)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Channel Coding Digital Signal Processor (CCDSP) detected a mismatch in the uplink
superframe counter value.
alarm. The system resets the DRI generating the alarm, and reports the Reset Due To Recurring
Byte Value (hex) Denition

first 00 to FF The CCDSP reporting the mismatch.
second 00 to FF Disregard this byte.
Possible causes

• The Superframe Synchronization message is not being sent to the FEP.
• The uplink equalizer data is being lost.
• The DRI baseband hopping interrupt feature is not working properly.
17-16 68P02901W26-S
Nov 2007
Procedure
Procedure 17-3 Superframe counter error (Uplink)
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS) and
goes disabled-unlocked) and continue to monitor the DRI.
the DRI fails to go Send a field representative to the site
busy-unlocked after to replace one of the following:
return to service
• DRIM board for an InCell BTS.
OR
• Transceiver unit for a non-InCell
the BSS takes the DRI BTS.
OOS again as a result of the
• Resets the DRI.


68P02901W26-S 17-17
Nov 2007
6. DRI: Superframe counter error (Downlink) Chapter 17: DRI Alarms
6. DRI: Superframe counter error (Downlink)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Channel Coding Digital Signal Processor (CCDSP) detected a mismatch in the downlink
superframe counter value.

17-18 68P02901W26-S
Nov 2007
Possible causes

• The Superframe Synchronization message is not being sent to the FEP.
• The downlink equalizer data is being lost.
• The DRI baseband hopping interrupt feature is not working properly.
Procedure
Procedure 17-4 Superframe counter error (Downlink)
If... Then...
return to service
OR
• Resets the DRI.

68P02901W26-S 17-19
Nov 2007

17-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. DRI: Channel coder internal message error
9. DRI: Channel coder internal message error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A channel control message for the specified subchannel or paging group (if applicable) is sent
to be encoded and transmitted by the Channel Coding Digital Signal Processor (CCDSP), but
the CCDSP already has a message pending for transmission.

68P02901W26-S 17-21
Nov 2007
Possible causes

• The CCDSP receives the current CCH message before the first message was sent out.
• The previous CCH message arrived at the CCDSP late.
• Site is overloaded.
Procedure
Procedure 17-5 Channel coder internal message error
If... Then...

return to service
OR BTS.

• Resets the DRI.

17-22 68P02901W26-S
Nov 2007

68P02901W26-S 17-23
Nov 2007
10. DRI: Dual-port RAM error Chapter 17: DRI Alarms
10. DRI: Dual-port RAM error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The RSS has identified a message from the DPRAM that contained an invalid number of bytes or
an invalid checksum.
System action
The system action is to reset the faulty Dual-Port RAM segment.
1 byte identifying the DPRAM segment number.
Possible causes

• The DPRAM data is corrupted.
• The DRI hardware has failed.
• The FEP has failed.
• The DHP is overloaded.
17-24 68P02901W26-S
Nov 2007
Procedure
Monitor the alarm condition and react accordingly.
Procedure 17-6 Dual-port RAM error
If... Then...
there is a recurrence of this Send a field representative to the
alarm site to replace the DRIM board (for
an InCell BTS) or the transceiver
unit (for a non-InCell BTS).
the alarm does not recur The fault condition no longer
exists.

68P02901W26-S 17-25
Nov 2007
13. DRI: Channel coder internal message error Chapter 17: DRI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A message with a valid checksum was received requesting a processing state change that is not
supported by the Channel Coding Digital Signal Processor (CCDSP).

Possible causes
The message was lost on its way to the CCDSP.
17-26 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-27
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A message with a valid checksum was received that cannot be processed due to the current
state of the Channel Coding Digital Signal Processor (CCDSP).

Possible causes

• The message was lost on its way to the CCDSP.
• CCSP received a bad state change message.
17-28 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR
• Resets the DRI.


68P02901W26-S 17-29
Nov 2007
15. DRI: Initial synchronization of radio and GPRS channel failed Chapter 17: DRI Alarms
15. DRI: Initial synchronization of radio and GPRS

channel failed
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The initial synchronization of the transceiver unit and a GPRS channel has failed.
All data for this alarm is in CTU2 format when reported by a CTU2.

first 00 to FF The Channel Coding Digital Signal Processor (CCDSP)
reporting the mismatch.
Possible causes
There is a fault in the path from the radio to the PCU.
17-30 68P02901W26-S
Nov 2007
Procedure
Procedure 17-9 Initial synchronization of radio and GPRS channel failed
1 Take appropriate corrective action to rectify any faults.

2 Check the communication links and the devices in the path from the
radio to the PCU.
68P02901W26-S 17-31
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
An error in the byte count of a channel coder internal message between the RSS and DRI
was detected.

first 00 to FF The Channel Coding Digital Signal Processor
(CCDSP) reporting the mismatch.
Possible causes

• A message pointer was corrupted between the RSS and the DRI.
• The message was corrupted between the RSS and the DRI.
17-32 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR
• Resets the DRI.


68P02901W26-S 17-33
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The checksum of the host message was invalid and corrupted the host port.

first 00 to FF The Channel Coding Digital Signal Processor
(CCDSP) reporting the mismatch.
Possible causes

• A message pointer was corrupted between the RSS and the DRI.
• The message was corrupted between the RSS and the DRI.
17-34 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-35
Nov 2007
18. DRI: Primary message or hardware interrupt error Chapter 17: DRI Alarms
18. DRI: Primary message or hardware interrupt error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The radio has either an interrupt failure or a primary message error.
AAI data for this alarm is in CTU2 format when reported by a CTU2.
If the DRI is operating in dual carrier mode, both DRIs are affected by the reset
and OOS actions.
17-36 68P02901W26-S
Nov 2007
Possible causes

• There is a hardware problem with one of the firmware critical interrupts.
• A firmware application fails to receive a critical message correctly.
Procedure
Procedure 17-12 Primary message or hardware interrupt error
1 Monitor the DRI.

2 The BSS resets the DRI if these alarms continue at an unacceptable rate.
3 If the BSS takes the DRI OOS, then INS the DRI and monitor again.
4 If the BSS takes the DRI OOS because of the same alarm, then replace the
DRI.
68P02901W26-S 17-37
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A message has been received that is valid only for a deactivated subchannel, but the associated
subchannel is not currently de-activated.
The contents of the information field are shown in Table 17-12.

first 00 to FF The Channel Coding Digital
Signal Processor (CCDSP)
reporting the mismatch.
Possible causes
An MPH-Deactivate Request message was lost on its way to the CCDSP.
17-38 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-39
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A message has been received that is valid only for an activated subchannel, but the associated
subchannel is not currently activated.
The contents of the information field are shown in Table 17-13.

first 00 to FF The Channel Coding Digital Signal
Processor (CCDSP) reporting the mismatch.
Possible causes
A MPH-Activate Request message was lost on its way to the CCDSP.
17-40 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-41
Nov 2007
21. DRI: Calibration in progress Chapter 17: DRI Alarms
21. DRI: Calibration in progress

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
DRI firmware has been put into test mode by a site engineer in order to calibrate the transceiver.
The alarm is a warning to the OMC-R operator not to implement MMI commands on the DRI
while the calibration is in progress. The site engineer is required to lock down all DRIs in the
cabinet before starting the calibration procedure. A transceiver is normally calibrated only once.
System action taken
The DRI transitions to enabled-unlocked (E-U). Subsequent alarms on the DRI are reported,
but not acted upon.
If the DRI is operating in Dual Carrier Mode, the associated DRI is shown. Firmware data is
also displayed which is of use only to firmware engineers: Source Fault Zone, Detector Fault
Zone, Fault Code, Additional data bytes 1-4, Timeslot, Carrier.
Possible causes
The site engineer has entered a command for the DRI firmware to enter calibration test mode.
To avoid occurrence of such alarm the following are to be observed:

• Do not lock, unlock, ins, or reset the DRI while calibration is in progress.
• During calibration, MMI commands should be performed on the DRI only by the site
engineer.
• It is the responsibility of the site engineer to return the DRI INS when the calibration is
complete, which clears the alarm.
17-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. DRI: Radio subsystem software to DRI communication error
22. DRI: Radio subsystem software to DRI

communication error
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An attempt to write to the host port was not successfully completed before reaching the
maximum retry count of 16.
System action taken
The affected DRI is reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is reset on the first two occurrences and then placed OOS on the
third occurrence.
Possible causes
The DRI hardware has failed.
68P02901W26-S 17-43
Nov 2007
Procedure
Procedure 17-15 Radio subsystem software to DRI communication error
If.... Then...
goes disabled-unlocked) and monitor the DRI.
return to service
OR BTS.


17-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. DRI: Radio subsystem software to DRI communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An attempt to write to the host port was not successfully completed before reaching the
maximum retry count of 16.
System action taken
The affected DRI is reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is reset on the first two occurrences and then placed OOS on the
third occurrence.
Possible causes
68P02901W26-S 17-45
Nov 2007
Procedure
Procedure 17-16 Radio subsystem software to DRI communication failure
If... Then...
return to service
OR BTS.


17-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. DRI: TDM interface failure - TDM parity error
24. DRI: TDM interface failure - TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A parity error was detected on the inbound TDM highway.
System action
The system action is to reset the DRI.
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes

• The TDM interface circuitry on the DRI is faulty.
• The TDM bus interface on the KSW/KSWX has failed.
• One or more of the signals of the TDM bus on the backplane has failed.
68P02901W26-S 17-47
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service
OR Send a field representative to the

site to replace the DRIM board.
the BSS takes the DRI

17-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. DRI: TDM interface failure - Assigned timeslot counter overow
25. DRI: TDM interface failure - Assigned timeslot

counter overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A timeslot counter overflow occurred because more switch-bound timeslots were driven onto
the TDM bus than were allocated in the ATC register.
Possible causes

• The TSA RAM has failed.
• The ATC register does not have enough allocated timeslots.
• One or more of the MCAP data or address lines on the backplane have failed.
68P02901W26-S 17-49
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-50 68P02901W26-S
Nov 2007
DRI: TDM interface failure - Assigned timeslot counter underow
26. DRI: TDM interface failure - Assigned timeslot

counter underow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A timeslot counter underflow occurred because fewer switch-bound timeslots were driven onto
the TDM bus than were allocated in the ATC register.
Possible causes

• The TSA RAM has failed.
• The ATC register does not have enough allocated timeslots.
• One or more of the MCAP data or address lines on the backplane have failed.
68P02901W26-S 17-51
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. DRI: Clock A signal loss
27. DRI: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI detected a TDM Clock A failure.
Possible causes
68P02901W26-S 17-53
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. DRI: Clock B signal loss
28. DRI: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI detected a TDM Clock B failure.
This alarm can also be accompanied by a CBUS alarm.
Possible causes
68P02901W26-S 17-55
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. DRI: Processor failure
29. DRI: Processor failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
• CTU2: A Digital Signal Processor on the radio has reset.
• Other DRI types: The DRI has gone OOS due to the failure of the FEP as shown by the
expiration of the watchdog timer. If a watchdog timer residing on a board or processor
fails, the associated board has failed.
This is a service-affecting fault condition.
System action taken
The affected DRI is hard reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is hard reset on the first two occurrences and then placed OOS on
the third occurrence.
68P02901W26-S 17-57
Nov 2007
Possible causes

• The transceiver unit is faulty.
• The processor or the firmware has failed.
Procedure
Procedure 17-22 Processor failure
If... Then...
return to service
OR BTS.


17-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. DRI: Transceiver re-initialized unexpectedly
30. DRI: Transceiver re-initialized unexpectedly

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver unit was reset.
System action taken
The affected DRI is soft reset when this alarm occurs.
Possible causes

• The transceiver unit firmware submitted a RESET request to the RSS software.
• The front-panel RESET button on the transceiver was pressed.
68P02901W26-S 17-59
Nov 2007
Procedure
Procedure 17-23 Transceiver re-initialized unexpectedly
If... Then...
required.

17-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. DRI: Critical resource exhausted
31. DRI: Critical resource exhausted

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
One of the following critical firmware resources is unavailable:

• The target processor is out of available memory.
• A firmware application has run out of time to complete a time-critical task.
• An outgoing PCI queue is full.
• The Shared Memory Unit is unable to find a free Data Buffer Descriptor.
System action taken
The DRI undergoes a soft reset. If the alarm indication is received for a second time, the DRI is
hard reset and a DSP code load occurs. If a third indication is received within 10 minutes, the
DRI is OOS, resulting in a loss of capacity.
If the radio is operating in Dual Carrier Mode, the associated DRI simultaneously undergoes the
same reset-OOS procedure. DRI transactions are tagged to the initial alarm.
If the radio is operating in Dual Carrier Mode, the associate DRI is noted in the Additional
information field.
68P02901W26-S 17-61
Nov 2007
Possible causes

• All buffers are full or there is a memory leak.
• A timing problem has occurred.
• More transactions were requested than the PCI driver can handle.
• An off-chip process is not consuming messages quickly enough to free Data Buffer
Descriptors or the Shared Memory Unit is lacking memory space.
Procedure
Procedure 17-24 Critical resource exhausted
If... Then...
the alarm is restricted to one If the BSS takes the DRI OOS; INS
radio, then it is likely to be a the DRI and monitor it. If the DRI
hardware fault is take OOS again due to the same
alarm, replace the DRI.
this alarm is reported by other Reduce the call load and monitor
DRI devices, it is likely to be the DRIs again.
due to a software or firmware
problem
17-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 32. DRI: RF unit primary sync signal lost
32. DRI: RF unit primary sync signal lost

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
RF Unit in the Slave Mode has lost the primary synchronization signal from the fiber link. The
RF Unit will switch to sync off of the HDSL link when this alarm is generated.
Fault code.
Possible causes
RF Unit has lost the primary synchronization signal from the fiber link and started to sync off
of the HDSL link. Only sync slave RF Units report this alarm. Sync master RF Unit always
uses sync signal from the HDSL link.
Procedure
Procedure 17-25 RF unit primary sync signal lost
1 Check the fiber links.

2 Check the state of the upstream RF Units.
68P02901W26-S 17-63
Nov 2007
33. DRI: RF unit HDSL link quality error Chapter 17: DRI Alarms
33. DRI: RF unit HDSL link quality error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The HDSL modem in the RF Unit has detected one of following errors:
• SNR (Signal to Noise Ratio) of the HDSL modem has dropped below the SNR hourly
threshold for longer than the SNR hourly threshold period during a one hour period.
• SNR of the HDSL modem has dropped below the SNR daily threshold longer than the SNR
daily threshold period during a 24 hour period.
Modem Error Cause - SNR Hourly or SNR Daily.
Possible causes
The quality of the HDSL link is being intermittently affected.
Procedure
Procedure 17-26 RF unit HDSL link quality error
Note the early warning condition.
17-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. DRI: RF unit reset
34. DRI: RF unit reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
RF Unit has been reset without resetting the RF Unit Modem.
Reset Cause Strings:

• TDM Clock Failure.
• TDM Sync Failure.
• RSS Communication Failure.
• CCCP Watchdog Timeout.
• EQCP Watchdog Timeout.
Possible causes

• TDM Clock Failure.
• TDM Sync Failure.
• RSS Communication Failure.
• CCCP Watchdog Timeout.
• EQCP Watchdog Timeout.
68P02901W26-S 17-65
Nov 2007
Procedure
Procedure 17-27 RF unit reset
Replace the DRI if it does not come back into service.
17-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 35. DRI: Reset due to recurring fault
35. DRI: Reset due to recurring fault

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm is reported against a group of DRI alarms classified as persistent fault alarms. When
this alarm is generated, it indicates that a persistent fault alarm has occurred six times within a
10 minute period and the affected DRI was reset.
Some alarms must occur 12 times instead of six times to be classified as persistent
alarms.
If this alarm is raised on a CTU2 operating in dual carrier mode due to intermittent fault
reporting, both carriers are reset.
If a DRI is reset twice due to a specific persistent fault alarm, and the persistent fault alarm
occurs another six times within the following 10 minutes, the system places the affected DRI
OOS and reports the Device Failure alarm (DRI 254).
The DRI alarm code identifying the persistent fault alarm is displayed in the Additional
information field. Refer to the description of the specific alarm to resolve the fault condition.
68P02901W26-S 17-67
Nov 2007
Additional information eld Chapter 17: DRI Alarms

first 02 This value is the reset type that occurred
as a result of a persistent fault alarm.
second 02, 05, 06, 09, 13, 14, 16, 17,19, The alarm code that caused the DRI to
20,39, 48, 49, 50, 57, 58, 59, 60, 61, be reset.
62, 63, 65, 66
Possible causes
A persistent fault alarm affecting a specific DRI has occurred six times.
Procedure
Procedure 17-28 Reset due to recurring fault
1 Check the Additional information field to identify the alarm code that caused
the affected DRI to be reset.
2 Refer to the description of the DRI alarm code that caused the DRI to be
reset for the resolution procedure.
17-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 36. DRI: Front
end processor to radio subsystem software communication failure
36. DRI: Front end processor to radio subsystem

software communication failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The Front End Processor (FEP) has not received the Superframe Synchronization Message for
the last five superframes. This failure can be a result of either a software or a link hardware
problem.
A 2 byte superframe count since the last sync message was received by the FEP is displayed
in the Additional information field.
Possible causes

• The RSS failed to transmit the message.
• The physical link between the DRI and the RSS (MCAP) has failed.
Procedure
Procedure 17-29 Front end processor to radio subsystem software communication

failure
1 If the DRI is OOS, determine which alarm caused the DRI to go OOS.
2 Refer to the description of that alarm for the solution procedure.
68P02901W26-S 17-69
Nov 2007
37. DRI: Hard reset Chapter 17: DRI Alarms
37. DRI: Hard reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI experienced a hard reset initiated by an operator or the DRI hardware.
Possible causes

• The RESET switch on the DRIM board was pressed.
• A DRI hardware failure.
17-70 68P02901W26-S
Nov 2007
Procedure
Procedure 17-30 Hard reset
1 Determine if the DRIM board was manually reset.

If the DRI was... Then...
manually reset If the DRI was manually reset
as part of a troubleshooting
procedure for another alarm, no
further action is required for this
alarm.
required.
3 Reset the DRI.
exists.

68P02901W26-S 17-71
Nov 2007
38. DRI: BSS internal alarm only - FWFM displayed at EMON Chapter 17: DRI Alarms
38. DRI: BSS internal alarm only - FWFM displayed at

EMON
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This is not reported to the operator. It is an internal alarm reported at the EMON as a SWFM
or FWFM.
N/A
Possible causes
N/A
Procedure
N/A
17-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. DRI: Synchronization loss with MCU
39. DRI: Synchronization loss with MCU

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The active communications link between the transceiver unit and the MCU is no longer
synchronized.
This alarm is generated only for an M-Cell micro, M-Cell2, M-Cell6, Horizon micro,
Horizon micro2 and Horizon compact2 sites.

first DSP number The unique identifier for the Channel Coding
Digital Signal Processor (CCDSP).
second and third 00 to FF and The FEP error code is expressed in the next
00 to FF two bytes displayed.
68P02901W26-S 17-73
Nov 2007
Possible causes

• The fiber optic cable is faulty.
• The cable connection is faulty.
• The communication link is faulty.
• The MCU is faulty.
• The DRI is faulty.
Procedure
Procedure 17-31 Synchronization loss with MCU
• Resets the DRI.

2 Make the following checks:

If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go
busy-unlocked after
return to service

17-74 68P02901W26-S
Nov 2007

68P02901W26-S 17-75
Nov 2007
40 - 47. DRI: Channel coder timeslot (0-7) failure Chapter 17: DRI Alarms
40 - 47. DRI: Channel coder timeslot (0-7) failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
One of the timeslots (0 through 7) on the Channel Coding Digital Signal Processor (CCDSP)
failed to respond to a Front End Processor (FEP).
As a result, the system takes the radio timeslot OOS. If the timeslot is the BCCH, the DRI is
reset. If the alarm occurs on a radio timeslot that is a BCCH for a third time within 10 minutes,
the DRI is taken OOS.

first and second 00 to FF and FEP error code.
00 to FF
third 1 or 2 The source of the alarm:
1 - The alarm was reported by firmware.
2 - The alarm was reported by software.
Possible causes

• The interface hardware between the FEP and the CCDSP is faulty.
• The code checksum routine, which is included as a part of the CCDSP initialization
process, failed.
17-76 68P02901W26-S
Nov 2007
Procedure
Procedure 17-32 Channel coder timeslot (0-7) failure
If the DRI... Then...

is busy-unlocked Only during a low traffic period, reset the DRI.
If the DRI does not return to service, send a
field representative to the site to execute one
of the following:
• For an InCell BTS, replace the DRIM

board.
• For a non-InCell BTS, replace the

transceiver unit.
is not busy-unlocked Reset the DRI. Check that the DRI and
the radio timeslot return to service.
If the DRI and the radio timeslot do not
return to service, send a field representative
to the site to execute one of the following:
• For an InCell BTS, replace the DRIM

board.
• For a non-InCell BTS, replace the

transceiver unit.

68P02901W26-S 17-77
Nov 2007
48. DRI: Baseband hopping timeslot counter mismatch Chapter 17: DRI Alarms
48. DRI: Baseband hopping timeslot counter mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The Front End Processor (FEP) Base Band Hopping (BBH) counter was not reset to zero on
the superframe boundary.

first 00 to FF Disregard this byte.
third 00 to FF The unique identifier for the Channel
Coding Digital Signal Processor (CCDSP).
Possible causes
The transceiver unit that generated the alarm is faulty.
17-78 68P02901W26-S
Nov 2007
Procedure
Procedure 17-33 Baseband hopping timeslot counter mismatch
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-79
Nov 2007
49. DRI: GSM timeslot counter mismatch Chapter 17: DRI Alarms
49. DRI: GSM timeslot counter mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The Front End Processor (FEP) DRI counter was not reset back to zero on the superframe
boundary.

first 00 to FF Disregard this byte.
third 00 to FF The unique identifier for the DRI Channel
Coding Digital Signal Processor (CCDSP).
Possible causes
The transceiver unit that generated the alarm is faulty.
17-80 68P02901W26-S
Nov 2007
Procedure
Procedure 17-34 GSM timeslot counter mismatch
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-81
Nov 2007
50. DRI: Spurious GSM timeslot interrupt Chapter 17: DRI Alarms
50. DRI: Spurious GSM timeslot interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
Two consecutive spurious interrupts were processed with equalized data bursts from the
transceiver unit.
If this alarm occurs 12 times within a certain time frame, it is classified as a persistent fault
Possible causes

• The transceiver unit is OOS.
• The DRI baseband hopping interrupt feature is not functioning properly.
• The uplink portion of the transceiver unit fiber link is faulty.
• The transceiver unit that generates the GSM timeslot interrupt is faulty.
17-82 68P02901W26-S
Nov 2007
Procedure
Procedure 17-35 Spurious GSM timeslot interrupt
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-83
Nov 2007
51. DRI: Baseband hopping TDM link error Chapter 17: DRI Alarms
51. DRI: Baseband hopping TDM link error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The TDM bus and the KSW failed to properly transfer channel-encoded modulator data to
the transceiver unit.
System action
This alarm is processed and reported only if this alarm condition occurs 18 times within a
two minute period.
The system then attempts to determine if a fault exists on the TDM bus. If a TDM bus fault is
not identified, the affected DRI is reset. If the condition to reset the DRI occurs three times
within a 10 minute period, the DRI is reset on the first two occurrences and then placed OOS on
Possible causes

• The TDM timeslot path connects were not configured at the KSW or the transceiver unit.
• The KSW hardware is faulty.
• The TDM hardware is faulty.
17-84 68P02901W26-S
Nov 2007
Procedure
Procedure 17-36 Baseband hopping TDM link error
If... Then...
return to service
OR BTS.


68P02901W26-S 17-85
Nov 2007
52. DRI: Baseband hopping GSM timeslot misalignment Chapter 17: DRI Alarms
52. DRI: Baseband hopping GSM timeslot misalignment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Channel Coding Digital Signal Processors (CCDSPs) were activated in the wrong GSM
timeslots.
A DRI different from the faulty DRI detects this alarm condition. The detecting DRI is
mentioned in the additional alarm information.
System action taken

first and second timeslot number The faulty TDM timeslot number affected by this BBH
TDM link error.
third 05 The hexadecimal representation of the detecting DRI
device.
fourth 00 to 05 Identifies a user-defined detecting DRI group at a site.
fifth 00 to 18h Identifies a specific detecting DRI board.
sixth 00 Serves as a placeholder for the detecting DRI.
17-86 68P02901W26-S
Nov 2007
Examples
The additional information is displayed as follows:

• 01 5a 05 01 02 00
TDM Timeslot Number is 015a (hex).
In this output, the ID of the detecting DRI is DRI 1 2 0.
• 00 74 ff ff ff ff
TDM Timeslot Number is 0074 (hex).
In this output, the ID of the detecting DRI is unknown (ff is displayed for unknown values
displayed in the Additional information fields).
Possible causes

• The TDM timeslot path connections are not correctly configured at the CCDSP.
• The CCDSP is faulty.
• The TDM link cables are faulty.
Procedure
Procedure 17-37 Baseband hopping GSM timeslot misalignment
If... Then...
return to service
OR BTS.

68P02901W26-S 17-87
Nov 2007

17-88 68P02901W26-S
Nov 2007
DRI: Channel coder 0 failure - Demodulation processor 0 failure
53. DRI: Channel coder 0 failure - Demodulation

processor 0 failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Channel Coder 0 failed as a result of the failure of demodulation processor 0.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
System action taken
The affected DRI is soft reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is soft reset on the first two occurrences and then placed OOS on
Possible causes
The demodulation processor 0 hardware is faulty.
68P02901W26-S 17-89
Nov 2007
Procedure
Procedure 17-38 Channel coder 0 failure - Demodulation processor 0 failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-90 68P02901W26-S
Nov 2007
DRI: Channel coder 0 Failure - Demodulation processor 1 failure
54. DRI: Channel coder 0 Failure - Demodulation

processor 1 failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
System action taken
Possible causes
68P02901W26-S 17-91
Nov 2007
Procedure
Procedure 17-39 Channel coder 0 Failure - Demodulation processor 1 failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-92 68P02901W26-S
Nov 2007

processor 0 failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
System action taken
Possible causes
68P02901W26-S 17-93
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-94 68P02901W26-S
Nov 2007

processor 1 failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Channel Coder 1 has failed as a result of the failure of demodulation processor 1.
System action taken
Possible causes
68P02901W26-S 17-95
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 57. DRI: Transceiver to DRI communication error
57. DRI: Transceiver to DRI communication error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Front End Processor (FEP) received a message from the transceiver unit that contains an
invalid header or message code for an uplink message destined for the RSS.
Possible causes

• The fiber link to the transceiver unit is faulty.
• The transceiver unit firmware sent an erroneous message.
68P02901W26-S 17-97
Nov 2007
Procedure
Procedure 17-42 Transceiver to DRI communication error
If... Then...
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
OR • For an InCell BTS, check the

transceiver unit, the DRIM
the BSS takes the DRI board, the DRIX board and
OOS again as a result of the the fiber links. Replace each
same alarm after the DRI faulty item.
• For a non-InCell BTS, replace
• Resets the DRI.


17-98 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Front End Processor (FEP) received a message from the transceiver unit that had a message
byte count greater than the maximum value.
Possible causes

• The DRIX is faulty.
68P02901W26-S 17-99
Nov 2007
Procedure
If... Then...

• Resets the DRI.


17-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 59. DRI: Transceiver to DRI burst error
59. DRI: Transceiver to DRI burst error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The first message from the transceiver unit was not the equalized data message.
Possible causes

68P02901W26-S 17-101
Nov 2007
Procedure
Procedure 17-44 Transceiver to DRI burst error
If... Then...

• Resets the DRI.


17-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 60. DRI: Transceiver to DRI burst error
60. DRI: Transceiver to DRI burst error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A second equalized data message from the transceiver unit was detected within the same
timeslot.
Possible causes

• The downlink baseband hopping interrupt hardware is faulty.
68P02901W26-S 17-103
Nov 2007
Procedure
Procedure 17-45 Transceiver to DRI burst error
If... Then...

• Resets the DRI.


17-104 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
No data was sent to the Front End Processor (FEP). The FEP was expecting an equalized data
message.
Possible causes

68P02901W26-S 17-105
Nov 2007
Procedure
If... Then...

• Resets the DRI.


17-106 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The data sent to the Front End Processor (FEP) was incomplete. The FEP was expecting three
bytes.
This is an application subsystem alarm.
Possible causes

• The RCU firmware sent an erroneous message.
68P02901W26-S 17-107
Nov 2007
Procedure
If... Then...

• Resets the DRI.


17-108 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The data sent to the Front End Processor (FEP) was incomplete. The FEP was expecting three
bytes.
This is an equipment malfunction alarm.
Possible causes

• The RCU firmware sent an erroneous message.
68P02901W26-S 17-109
Nov 2007
Procedure
If... Then...

• Resets the DRI.


17-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 64. DRI: Non recoverable error
64. DRI: Non recoverable error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A non recoverable error has occurred due to one of the following:

• DRI initialization has failed.
• PCI bus error.
• Digital Signal Processor failure.
The DRI is soft reset, hard reset, then taken OOS. If it is in dual carrier mode, both DRIs are
affected.
information field.
Possible causes

• Memory allocation error.
• Hardware failure.
68P02901W26-S 17-111
Nov 2007
Procedure
Procedure 17-49 Non recoverable error
1 Monitor the DRI.

2 The BSS resets the DRI if these alarms continue at an unacceptable rate.
DRI.
17-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 65. DRI: Radio
subsystem software to DRI communication error - Checksum error

communication error - Checksum error
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Front End Processor (FEP) identified a DPRAM message from the RSS that contains an
invalid checksum. The FEP discards the message.
If this alarm is raised on a CTU2 radio type, a message has been received with an invalid
checksum.
If this alarm is raised on a CTU2 radio type and the DRI is in Dual Carrier Mode, the associated
DRI simultaneously undergoes the same reset-OOS procedure. DRI transitions are tagged
to the initial alarm.

first 00 to FF If this alarm is reported by the FEP, this byte represents
the Channel Coding Digital Signal Processor (CCDSP).
If this alarm is reported by the firmware, this byte
represents the DPRAM that is reporting the mismatch
as a host message.
68P02901W26-S 17-113
Nov 2007
If this alarm is raised on a CTU2 radio type, the additional data format is:
• Firmware Source Fault Zone.

• Firmware Detector Fault Zone.
• Firmware fault code.
• Firmware alarm indication data bytes 1 to 4.
• Carrier.
• Timeslot.
(This information is useful only for firmware debugging purposes).
Possible causes

• The message was corrupted by RSS software.
• The DPRAM is faulty.
Procedure
Procedure 17-50 Radio subsystem software to DRI communication error - Checksum

error
If... Then...
return to service
OR BTS.

17-114 68P02901W26-S
Nov 2007
• Resets the DRI.


68P02901W26-S 17-115
Nov 2007
66. DRI: Superframe counter error Chapter 17: DRI Alarms
66. DRI: Superframe counter error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The value of the superframe software counter maintained by the Front End Processor (FEP)
does not match the superframe value that was most recently received in the superframe
synchronization message from the RSS.

first 00 to FF The Channel Coding Digital Signal
Processor (CCDSP) reporting the
mismatch.
17-116 68P02901W26-S
Nov 2007
Possible causes

• The RSS did not sent an updated superframe synchronization message.
• The superframe synchronization message arrived too late at the FEP.
• The GSM timeslot interrupt on the DRI is faulty.
Procedure
Procedure 17-51 Superframe counter error
If... Then...
return to service
OR BTS.

• Resets the DRI.


68P02901W26-S 17-117
Nov 2007
17-118 68P02901W26-S
Nov 2007
DRI: Radio subsystem software to DRI communication error - DRI not responding

communication error - DRI not responding
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The RSS is unable to communicate with the DRI because the DRI is not responding to higher
layer messages.
Possible causes

• The DRI hardware was unequipped in the system.
• The DRI hardware is faulty.
68P02901W26-S 17-119
Nov 2007
Procedure
Procedure 17-52 Radio subsystem software to DRI communication error - DRI

not responding
If... Then...
return to service
OR BTS.


17-120 68P02901W26-S
Nov 2007
DRI: Equalizer control processor failure - Watchdog timer expired
70. DRI: Equalizer control processor failure - Watchdog

timer expired
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Equalizer Control Processor (EQCP) failed. The failure of the EQCP was indicated by
the expiration of a watchdog timer.
System action taken
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
68P02901W26-S 17-121
Nov 2007
Possible causes

• The EQCP firmware on the transceiver unit is faulty.
Procedure
Procedure 17-53 Equalizer control processor failure - Watchdog timer expired
If... Then...
return to service
OR BTS.


17-122 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 71. DRI: Unexpected communications bus interrupt
71. DRI: Unexpected communications bus interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
An intermittent hardware or message transport (PCI) error has occurred. The master DSP has
received more interrupts than messages delivered through the PCI bus.
If the DRI is in Dual Carrier Mode, the associated DRI simultaneously undergoes the same
reset-OOS procedure. DRI transitions are tagged to the initial alarm.
information field.
68P02901W26-S 17-123
Nov 2007
Possible causes

• The PCI driver is malfunctioning.
• There is a PCI bus hardware failure.
Procedure
Procedure 17-54 Unexpected communications bus interrupt
1 Monitor the DRI.

2 The BSS resets the DRI if these alarm indications continue at an
unacceptable rate.
DRI.
17-124 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 72. DRI: Receiver failure
72. DRI: Receiver failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Alarm receiver (equalizer) detected a problem with the order of the in-phase and quadrature
(IQ) data stream.
The DRI is soft reset after the first and second time this alarm indication is received. If the
alarm occurs three times within a 10 minute period, the DRI is OOS.
There is no additional information related to this alarm.
Possible causes
IQ data was corrupted before it reached radio firmware.
68P02901W26-S 17-125
Nov 2007
Procedure
Procedure 17-55 Receiver failure
1 Monitor the DRI.

2 If the BSS takes the DRI OOS, reset the DRI (reset_device) and monitor
again.
DRI.
17-126 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 73. DRI: High reverse power
73. DRI: High reverse power

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
An excessive amount of reverse RF power is detected by the CTU2 radio. The purpose of
CTU2 reverse power detection alarm is to protect the CTU2 from physical damage due to an
excessive amount of reverse RF power. Therefore, the fault management software resets the
CTU2 immediately. If this alarm is repeated three times in 10 minutes, the software changes the
state of the radio to be inhibited.
If the radio is operating in Dual Carrier Mode, the associated DRI is noted in the Additional
information field.
Possible causes

• SMA cable to DUP, feeder cable, lightening arrester, or antenna.
• External RF combiner with poor RF performance in indoor distribution system.
• Loose or damaged connectors, such as the SMA on the CTU2 or DUP, and 7/16th
connectors.
• Faulty DUP.
• CTU2 Reverse power detection circuit.
68P02901W26-S 17-127
Nov 2007
Procedure
Procedure 17-56 High reverse power
1 Check if the SMA cable between Radio and DUP is loose or damaged.
2 Check the antenna system.
3 Change the SMA cable. Ensure that the connection is not loose or damaged.
Then check if the alarm clears.
4 If the alarm cannot be cleared, check the Radio TX SMA connector, DUP TX
SMA connector, and DUP ANT connector.
5 If the alarm still cannot be cleared, change the DUP of affected DRI or swap
the DUP of affected radio with another DUP.
6 If the alarm still exists, replace the CTU2.
17-128 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 74. DRI: Cell transmit power unachievable
74. DRI: Cell transmit power unachievable

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A radio cannot be brought into service because it cannot achieve the cell transmit power level.
If the DRI is in Dual Carrier Mode, the associated DRI simultaneously undergoes the same fault
translation action. The alarm is tagged to the DRI state transitions.
All affected DRI devices remain out of service at this cell, resulting in a loss of capacity.
This field will display one of the following, according to the reason for failure:
• bts_txpwr_max_inner incorrect:
database value = x
required value = y
• max_tx_bts incorrect:
database value = x
required value = y
• Combination of bts_txpwr_max_inner and Tx power offsets incorrect:

database value = x
required value = y
• Combination of max_tx_bts and Tx power offsets incorrect:

database value = x
required value = y
• Database Tx power offset out of range for this DRI type.
Where x and y are integers. The required value is the value that will enable the OOS DRI to
come INS.
68P02901W26-S 17-129
Nov 2007
Possible causes

• bts_txpwr_max_inner value is incorrect in the database.
• max_tx_bts value is incorrect in the database.
• during comparison of bts_txpwr_max_inner value and the DRI calibration data, software
determines the DRI cannot achieve the transmit power specified for the cell.
• during comparison of max_tx_bts value and the DRI calibration data, software determines
the DRI cannot achieve the transmit power specified for the cell.
• Tx power offsets for CTU2 have been applied to a legacy DRI type.
Procedure
Procedure 17-57 Cell transmit power unachievable
1 Execute the chg_ele command to change the database parameter to the

required value. This action will reduce the cell transmit power. Refer to
Maintenance Information: BSS Command Reference (68P02901W23).
Do not use this option if the reason for failure is shown as

Database Tx power offset out of range for this DRI type. If
database values are changed for this type of failure, other
transceivers at the site may not achieve the required transmit
power, in which case they will be taken OOS.
2 Send a field representative to re-calibrate the site. The site engineer is
required to lock down all DRIs in the cabinet before starting the calibration
procedure. Refer to the relevant hardware manual.
This option must be used if the reason for failure is shown as

Database Tx power offset out of range for this DRI type.
17-130 68P02901W26-S
Nov 2007

68P02901W26-S 17-131
Nov 2007
76. DRI: Radio subsystem software to DRI communication error Chapter 17: DRI Alarms

communication error
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The RSS detected the loss of uplink SACCH messages from the transceiver unit. If the uplink
SACCH messages are not detected by the RSS, in-progress calls are dropped.
System action
This alarm is not reported unless it occurs 10 times within a 24–hour period. If this alarm occurs
10 times within a 24–hour period, the DRI is hard reset.
A one byte code representing the DPRAM segment number is displayed in the Additional
information field in the output for this alarm.
17-132 68P02901W26-S
Nov 2007
Possible causes

• The communication link is faulty.
• The firmware on the transceiver unit is faulty.
• The RSS software is faulty.
• The BTP or DHP is faulty.
Procedure
Procedure 17-58 Radio subsystem software to DRI communication error
1 Determine if this is a recurrence of this alarm within the last 24

hours.
a recurrence Send a field representative to the
not a recurrence Go to step 2.
exists.

68P02901W26-S 17-133
Nov 2007
78. DRI: TX VSWR antenna fault Chapter 17: DRI Alarms
78. DRI: TX VSWR antenna fault

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the duplexer blocks has reported a transmit VSWR fault. This alarm indicates high
reflected power level from TX antenna N (0 to 5). The additional data enumerates which
duplexer block detected the failure.
Block number of problem duplexer and Firmware information.
Possible causes
Broken or missing antenna, cable or poor connection to the antenna.
Procedure
Modify the alarm and act accordingly.
Procedure 17-59 TX VSWR antenna fault
1 Send a service technician to the site.

2 Troubleshoot the antenna connection.
The duplexer can only detect VSWR problems when the radio is
transmitting above a certain power threshold. The range of values
are max_tx_bts between 0 and 6.
17-134 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 80. DRI: Transmitter synthesizer failure
80. DRI: Transmitter synthesizer failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Transmit synthesizer 1 failed to maintain synchronization lock on the reference frequency.
If this alarm is raised on a CTU2 radio type, a failure of one of the radio synthesizers has
occurred.
System action
For a non-InCell BTS, the transceiver unit is reset. If the alarm occurrence has reached a
threshold, the DRI is placed OOS.
For an InCell BTS, if the alarm condition clears within a specified time period, the transceiver
unit is reset. Otherwise, it is placed OOS.
DRI simultaneously undergoes the same alarm translation procedure. DRI transitions are
tagged to the initial alarm.

68P02901W26-S 17-135
Nov 2007

• Carrier.
• Timeslot.
Possible causes

• The dc power to transmit synthesizer 1 was lost.
• The input reference frequency was lost.
• Transmit synthesizer 1 failed.
• The interconnect jumper is blocked.
• The Control Equalizer Board (CEB) failed.
• The RF cables are faulty.
• The transceiver is not identified as NOT LOCKED.
Procedure
Procedure 17-60 Transmitter synthesizer failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service

17-136 68P02901W26-S
Nov 2007

68P02901W26-S 17-137
Nov 2007
81. DRI: Transmitter synthesizer failure Chapter 17: DRI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Transmit synthesizer 2 failed to maintain synchronization lock on the reference frequency.
If this alarm is raised on a CTU2 radio type, a failure of one of the radios synthesizers has
occurred.
System action
unit is reset. Otherwise it is placed OOS.

17-138 68P02901W26-S
Nov 2007
• Carrier.
• Timeslot.
Possible causes

• The dc power to transmit synthesizer 2 was lost.
• The input reference frequency was lost.
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service

68P02901W26-S 17-139
Nov 2007

17-140 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of transmit synthesizer 1 is below the normal power range required for
RF transmission.
System action
Possible causes

• The transmit synthesizer 1 switch failed.
• The transmit synthesizer 1 switch control circuits failed.
• The interconnect jumper to the synthesizer board is blocked.
68P02901W26-S 17-141
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-142 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of transmit synthesizer 2 is below the normal power range required for
RF transmission.
System action
Possible causes

• The transmit synthesizer 2 switch failed.
• The transmit synthesizer 2 switch control circuits failed.
68P02901W26-S 17-143
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-144 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transmit synthesizer switch failed. The transmit synthesizer switch fails when both transmit
synthesizer 1 and transmit synthesizer 2 fail.
System action
Possible causes

• The transmit synthesizer switch failed.
• The transmit synthesizer switch control circuits failed.
• The transmit synthesizer 1 and transmit synthesizer 2 simultaneously failed.
68P02901W26-S 17-145
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-146 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 85. DRI: Transmitter failure - Output power
85. DRI: Transmitter failure - Output power

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of the transmit exciter is below the power range required for RF transmission.
System action
Possible causes

• The transceiver synthesizer failed.
• The transceiver synthesizer switch failed.
• The dc power to exciter was lost.
• The exciter failed.
• The exciter control circuits failed.
• The interconnect jumper to exciter board is blocked.
• The RF stages on exciter board failed.
• The modulator failed.
68P02901W26-S 17-147
Nov 2007
Procedure
Procedure 17-65 Transmitter failure - Output power
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-148 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of the transmit power amplifier is below the power range required to sustain
RF transmission.
System action

• Carrier.
• Timeslot.
68P02901W26-S 17-149
Nov 2007
Possible causes

• The dc power to the power amplifier was lost.
• The exciter power output was lost.
• The power amplifier control circuits failed.
• The power amplifier components failed.
• The failed components resulted in spurious emissions (exceeding acceptable limits).
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service

• Release-dependent customer document 68P02901W51 Maintenance

Information: BSS Field Troubleshooting.
17-150 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of the transmit power amplifier is higher than the power range required to
sustain RF transmission.
At high power levels, the unit is removed from service to prevent damage to RF power
devices and to prevent the transmission of spurious emissions.
System action
that are useful only to the programmers. Any additional bytes displayed should be ignored

• Carrier.
• Timeslot.
68P02901W26-S 17-151
Nov 2007
Possible causes
The power amplifier control circuits failed.
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-152 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88. DRI: Power amplier temperature high
88. DRI: Power amplier temperature high

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The temperature of the transmit power amplifier is higher than the safe operating temperature
for the equipment.
At high temperature levels, the unit is removed from service to prevent damage to
RF power devices and other electronics.
System action
68P02901W26-S 17-153
Nov 2007

• Carrier.
• Timeslot.
Possible causes

• The air flow is blocked.
• The cooling fans failed.
• The ambient temperature is excessive.
• The power amplifier control circuits failed.
• The power amplifier voltage regulation circuits failed.
• The RF output connection failed.
• The DRI hardware is faulty.
17-154 68P02901W26-S
Nov 2007
Procedure
Procedure 17-68 Power amplier temperature high
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-155
Nov 2007
89. DRI: Power amplier communication failure Chapter 17: DRI Alarms
89. DRI: Power amplier communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The transmit power amplifier watchdog timer expired.
System action
Possible causes

• The power amplifier control processor failed due to corrupted software.
• The power amplifier control circuits lost dc power.
17-156 68P02901W26-S
Nov 2007
Procedure
Procedure 17-69 Power amplier communication failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-157
Nov 2007
90. DRI: Transmitter failure - Output power Chapter 17: DRI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The transmit RF modulator failed.
System action
Possible causes

• The modulator failed.
• The modulator lost dc power.
• The modulator output power is too low.
• The modulator is out of lock from receive synthesizer 3.
17-158 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-159
Nov 2007
91. DRI: Power amplier power low but functioning Chapter 17: DRI Alarms
91. DRI: Power amplier power low but functioning

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of the transmit power amplifier is marginally below specified limits, but
calls may continue.

• Carrier.
• Timeslot.
Possible causes

• The power amplifier control circuits lost dc power.
• The exciter power output is low.
• The power amplifier components failed.
17-160 68P02901W26-S
Nov 2007
Procedure
Monitor the DRI and act accordingly.
Procedure 17-71 Power amplier power low but functioning
If the power level remains low for an extended period of time (24 hours),
consider replacing the transceiver unit during low traffic periods.
68P02901W26-S 17-161
Nov 2007
92. DRI: Power amplier temperature high but functioning Chapter 17: DRI Alarms
92. DRI: Power amplier temperature high but

functioning
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The temperature of the transmit power amplifier is higher than the normal operating
temperature for the equipment. This fault condition is not considered critical because the power
amplifier temperature is not yet at a level that causes the power amplifier to cease functioning.
The power amplifier continues to function under this condition, but at reduced power to prevent
damage to the RF transistors. Reduced power is defined as the higher of the two following
values, such as -4 dB from the set point or the minimum power level for a power amplifier.

• Carrier.
• Timeslot.
17-162 68P02901W26-S
Nov 2007
Possible causes

• The air flow is blocked.
• The cooling fans failed.
• The ambient temperature is excessive.
• The transmit combiner failed.
• The RF element following the power amplifier in the transmit path power amplifier is faulty.
• The RF output connection failed.
Procedure
Procedure 17-72 Power amplier temperature high but functioning
If the temperature remains high for an extended period of time (24 hours),
consider replacing the transceiver unit during a low traffic period.
68P02901W26-S 17-163
Nov 2007
93. DRI: Transmitter failure - Output power Chapter 17: DRI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transmitter board failed.
System action
Possible causes

• The transmit synthesizers failed.
• The transmit board failed.
• The transmit control circuits failed.
• The dc power to the transmit board is lost.
• The interconnection to the transmit board is blocked.
• The RF cable is faulty.
• The power level reference (13 MHz) is lost.
17-164 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-165
Nov 2007
104 - 111. DRI: Timeslot 0-7 conguration failure Chapter 17: DRI Alarms
104 - 111. DRI: Timeslot 0-7 conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the Cell Resource Manager (CRM) has failed to configure a DRI
timeslot 0 for RF channel resource allocation for call processing.
There is no additional data for this alarm.
Possible causes

• The cell resource manager (CRM) is faulty.
• The Middle Man Funnel (MMF) process is faulty.
• RSS is faulty.
• Front End Process (FEP) is faulty.
• Radio Channel Unit (RCU) is faulty.
Procedure
Procedure 17-74 Timeslot 0-7 conguration failure
1 Review the DRI device alarm message for the device failed alarm.
2 In a TTY window, enter the state command to check the operational
and administrative status of the DRI.
3 Send a field representative to the site to replace the DRI generating
the alarm.
17-166 68P02901W26-S
Nov 2007

68P02901W26-S 17-167
Nov 2007
112. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
112. DRI: Receiver synthesizer failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Receive synthesizer 1 failed to maintain synchronization lock on the reference frequency.
occurred.
System action
threshold, the DRI is forced OOS.
For an InCell BTS, if the alarm condition clears within a specific time period, the transceiver
unit is reset. Otherwise it is forced OOS.
that are useful only to the programmers. Ignore any additional bytes displayed.

• Carrier.
• Timeslot.
17-168 68P02901W26-S
Nov 2007
Possible causes

• The dc power to the receive synthesizer 1 is lost.
• The input reference frequency is lost.
• The receive synthesizer 1 failed.
• The interconnect jumper to the receive synthesizer 2 board is blocked.
Procedure
Procedure 17-75 Receiver synthesizer failure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-169
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
occurred.
System action
that are useful only to the programmers. Ignore any additional bytes displayed.

• Carrier.
• Timeslot.
17-170 68P02901W26-S
Nov 2007
Possible causes

• The dc power to the receive synthesizer 2 is lost.
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-171
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
System action
Possible causes

• The dc power to receive synthesizer 3 is lost.
17-172 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-173
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power of receive synthesizer 1 is below the normal power range required for RF
signal reception.
System action
Possible causes

• The receive synthesizer switch failed.
• The receive synthesizer switch control circuits failed.
17-174 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-175
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
signal reception.
System action
Possible causes

17-176 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-177
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
signal reception.
System action
Possible causes

• The dc power to the synthesizer is lost.
• The receive synthesizer failed.
17-178 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-179
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receive synthesizer switch failed. The receive synthesizer switch fails when both receive
synthesizer 1 and receive synthesizer 2 fail.
System action
Possible causes

• The simultaneous failure of receive synthesizer 1 and receive synthesizer 2.
17-180 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-181
Nov 2007
119. DRI: Receiver failure Chapter 17: DRI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The main receive intermediate frequency circuitry failed.
System action
Possible causes

• The dc power voltage to the main intermediate frequency circuitry is out of the required
range.
• The dc power current drain of the main intermediate frequency circuitry is out of the
required range.
• The intermediate frequency circuit components failed.
17-182 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-183
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Receive Signal Strength Indicator (RSSI) branch failed.
System action
Possible causes

• The dc power voltage to RSSI branch is out of the required range.
• The dc power current drain of the RSSI branch is out of the required range.
• The RSSI branch components failed.
• The interconnect jumper to the RSSI board is blocked.
• The 10.7 MHz oscillator on the RSSI board is not tuned.
17-184 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-185
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver front-end failed. This failure causes a serious loss of antenna gain.
System action
Possible causes

• The dc power voltage to the front-end is out of the required range.
• The dc power current drain of the front-end is out of the required range.
• The intermediate frequency components failed.
• The interconnect jumper to the receiver front-end board is blocked.
17-186 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-187
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
System action
Possible causes

• The A/D converter failed.
• The AGC system failed.
• The RSSI branch failed.
• The main intermediate frequency circuitry failed.
• The Control Equalizer Board (CEB) interface to the I-Channel A/D converter is faulty.
17-188 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-189
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently underflowed.
System action
Possible causes

• The Control Equalizer Board (CEB) interface to the Q-Channel A/D converter is faulty.
17-190 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-191
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
System action
Possible causes

17-192 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-193
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently overflowed.
System action
Possible causes

17-194 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-195
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Receiver branch 1 failed. This failure causes a serious loss of receiver sensitivity.
System action
Possible causes

• The receiver board failed.
• The dc power to the receiver board is lost.
• The receiver board control circuits failed.
• The interconnect jumper to the receiver board is blocked.
17-196 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-197
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Receiver branch 2 failed. This failure causes a serious loss of receiver sensitivity.
System action
Possible causes

• The receiver board control circuits failed.
• The interconnect jumper to the receiver board is blocked.
17-198 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-199
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Radio Frequency Module (RFM) receiver board at an M-Cell micro site failed.
System action
Possible causes

17-200 68P02901W26-S
Nov 2007
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


68P02901W26-S 17-201
Nov 2007
144. DRI: Transceiver to DRI communication failure Chapter 17: DRI Alarms
144. DRI: Transceiver to DRI communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The 13 MHz Phase Lock Loop (PLL) synthesizer for GSM timing failed.
If this alarm was raised on a CTU2 radio type, the fault code is set to hex 68 (firmware fault
code for PLL Lock Alarm).
System action
The contents of the Additional information field in the output for this alarm are shown in
Table 17-22.

first 00 to FF The transceiver unit fault group.
second 00 to FF The fault code reported by the transceiver unit.
Refer to the table under Possible causes.
17-202 68P02901W26-S
Nov 2007

• Carrier.
• Timeslot.
Possible causes
Fault Code Value (hex) Denition

0 One of the following:
• The PLL synthesizer failed.
• The 13 MHz synthesizer lost dc power.
• The fiber optic downlink path from the DRI is faulty.
• The input frequency reference to the 13 MHz PLL

synthesizer was lost.
1 One of the following:
• The PLL synthesizer failed.
• The fiber optic downlink path from the DRI is faulty.
• The input frequency reference to the 13 MHz PLL

synthesizer was lost.
• The GSM timing chain failed.
68P02901W26-S 17-203
Nov 2007
Procedure
Procedure 17-92 Transceiver to DRI communication failure
If... Then...
return to service
OR BTS.


17-204 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 146. DRI: Transceiver to DRI communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GSM timing is out of sync with the higher software layers.
System action
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes

• The GSM timing chain failed.
• The timing failed.
• A momentary loss of synchronization occurred due to a noise burst in the communications

link.
68P02901W26-S 17-205
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-206 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The number of CRC errors on the data link exceeded the allowable limits.
System action
For MCU-based sites, if this alarm occurs three times within a 10 minute period, the DRI is
placed OOS on the third occurrence.
For InCell sites, the DRI is immediately taken OOS.
Possible causes

• Faulty data link.
• Data link noise.
• Intermittent data link failure.
• Faulty fiber optic interface circuit.
• Faulty data recovery circuit.
68P02901W26-S 17-207
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-208 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The HDLC transmit FIFO to fiber links consistently underflows.
System action
Possible causes

• Faulty transceiver timing chain.
• Faulty communications interface between the HDLC link and control processor.
• Faulty control circuits.
68P02901W26-S 17-209
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-210 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The HDLC receive FIFO (First-In First-Out) to fiber links consistently overflows.
System action
Possible causes

• Faulty transceiver timing chain.
• Faulty communications interface between the HDLC link and control processor.
• Faulty control circuits.
68P02901W26-S 17-211
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-212 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 150. DRI: Receive matrix failure
150. DRI: Receive matrix failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receive matrix control link failed.
Possible causes

• Faulty receive matrix.
• Faulty open circuit in the coaxial cable between the transceiver unit and the matrix.
• Short circuit in the coaxial cable between the transceiver unit and the matrix.
• Faulty control equalizer board control circuits.
• Open circuit in the front-end board matrix interface.
• Short circuit in the front-end board matrix interface.
68P02901W26-S 17-213
Nov 2007
Procedure
Procedure 17-97 Receive matrix failure
to take appropriate action and resolve the alarm.

17-214 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 151. DRI: Transceiver to combiner communication failure
151. DRI: Transceiver to combiner communication

failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The communication link between the transmit combiner and the transceiver unit failed.
System action
The combiner that fails is placed OOS and a switchover is made to a standby combiner. If both
combiners fail, all radios connected to them are placed OOS.
Possible causes

• Faulty transmit combiner.
• Lost dc power to the combiner.
• Open circuit in the coaxial cable between the transceiver unit and the combiner.
• Short circuit in the coaxial cable between the transceiver unit and the combiner.
• Faulty combiner circuit interface in the transceiver unit.
68P02901W26-S 17-215
Nov 2007
Procedure
Determine the state of both combiners.
Wait for at least 10 minutes after the alarm is initially reported to determine the
state of the combiners. This allows sufficient time for the system to completely reset
the DRI and retune the combiner cavity.
Procedure 17-98 Transceiver to combiner communication failure
If... Then...
if both combiners are No further action is required.
busy-unlocked If this alarm recurs, it indicates an
intermittent fault.
both combiners are Send a field representative to the
disabled-unlocked or site to replace the combiners.
disabled-locked
one combiner is busy-unlocked Send a field representative to the
and the other combiner is site to check the combiner links.
enabled-unlocked Before this, make an attempt to
swap the redundant combiner.

17-216 68P02901W26-S
Nov 2007
DRI: Control processor to power amplier communication failure
152. DRI: Control processor to power amplier

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The communications link between the Control Equalizer Board (CEB) and the power amplifier
failed.
System action
Possible causes

• Faulty CEB/PA control code.
• Noise on the CEB to power amplifier link.
• Faulty hardware link on either side of the CEB/PA control processors.
68P02901W26-S 17-217
Nov 2007
Procedure
Procedure 17-99 Control processor to power amplier communication failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-218 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 153. DRI: Control processor to equalizer communication failure
153. DRI: Control processor to equalizer

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The communications link between the Control Equalizer Board (CEB) host processor and the
Equalizer Board (EQB) failed.
System action
Possible causes

• Faulty communication link between the CEB and EQB.
• The communication link seized by one of the EQB processors.
• The communication link seized by the CEB processor.
68P02901W26-S 17-219
Nov 2007
Procedure
Procedure 17-100 Control processor to equalizer communication failure
If... Then...
return to service
OR BTS.


17-220 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 154. DRI: Power supply failure
154. DRI: Power supply failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A transceiver power supply failed.
System action

• Carrier.
• Timeslot.
68P02901W26-S 17-221
Nov 2007
Possible causes

• The dc supply voltages in the transceiver unit are out of the acceptable range.
• Faulty dc supply voltages in the transceiver unit.
• The external power source voltage is out of the acceptable range causing the power
supply to fail.
Procedure
Send a field representative to the site to determine the cause of the alarm and take appropriate
action.
Procedure 17-101 Power supply failure
If... Then...
return to service
OR BTS.


17-222 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An excessive number of byte count errors were detected.
System action
Possible causes

• Corrupted DRI software.
• Corrupted CEB software.
• Intermittent failure of the HDLC link to the DRI.
• Intermittent failure of the HDLC link to the transceiver unit.
68P02901W26-S 17-223
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-224 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 156. DRI: Control processor message queue overowed
156. DRI: Control processor message queue overowed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Control Equalizer Board (CEB) message queue overflowed.
System action
Possible causes

• The higher layer process sent an excessive number of messages too quickly.
• The CEB was not processing messages.
• Corrupted CEB software, DRI software, Fault Management (to BSS) software or faulty
CEB hardware.
68P02901W26-S 17-225
Nov 2007
Procedure
Procedure 17-103 Control processor message queue overowed
If... Then...
return to service
OR BTS.


17-226 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 157. DRI: Receiver input overowed
157. DRI: Receiver input overowed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver I-Channel First-In First-Out (FIFO) consistently overflowed.
System action
Possible causes

• Control circuits failed.
• Timing circuits failed.
68P02901W26-S 17-227
Nov 2007
Procedure
Procedure 17-104 Receiver input overowed
If... Then...
return to service
OR BTS.


17-228 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 158. DRI: Receiver input overowed
158. DRI: Receiver input overowed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receiver Q-Channel First-In First-Out (FIFO) consistently overflowed.
System action
Possible causes

• Control circuits failed.
• Timing circuits failed.
68P02901W26-S 17-229
Nov 2007
Procedure
Procedure 17-105 Receiver input overowed
If... Then...
return to service
OR BTS.


17-230 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 159. DRI: Equalizer output overowed
159. DRI: Equalizer output overowed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The equalizer output data consistently overflowed.
System action
Possible causes

• CEB watchdog timer expired.
• Control circuit failure.
• Timing circuit failure.
68P02901W26-S 17-231
Nov 2007
Procedure
Procedure 17-106 Equalizer output overowed
If... Then...
return to service
OR BTS.


17-232 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 160. DRI: Equalizer output overowed
160. DRI: Equalizer output overowed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The equalizer output control First-In First-Out consistently overflowed.
System action
Possible causes

• CEB watchdog timer expired.
• Control circuit failure.
68P02901W26-S 17-233
Nov 2007
Procedure
Procedure 17-107 Equalizer output overowed
If... Then...
return to service
OR BTS.


17-234 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 161. DRI: Transmitter out of synchronization
161. DRI: Transmitter out of synchronization

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The modulator interface lost synchronization with the transceiver unit timing chain.
System action
Possible causes

• Faulty CEB timing chain.
• Noise on the fiber link.
• 5-volt supply voltage low switched.
• Failure of 13 MHz clock from slave PLL.
• Failure of the recovered clock on the fiber link to the transceiver unit.
68P02901W26-S 17-235
Nov 2007
Procedure
Procedure 17-108 Transmitter out of synchronization
If... Then...
return to service
OR BTS.


17-236 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 162. DRI: Receive matrix branch 2 control link failure
162. DRI: Receive matrix branch 2 control link failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The receive matrix branch 2 control link failed.
Possible causes

• Faulty receive matrix.
• Faulty open circuit in the coaxial cable between the transceiver unit and the matrix.
• Short circuit in the coaxial cable between the transceiver unit and the matrix.
• Faulty CEB control circuits.
• Open circuit in the front-end board matrix interface.
• Short circuit in the front-end board matrix interface.
68P02901W26-S 17-237
Nov 2007
Procedure
Procedure 17-109 Receive matrix branch 2 control link failure
Send a field representative to the site to determine the cause of the alarm.

17-238 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
HDLC downlink communications between the higher level devices and the transceiver unit
failed.
System action
Possible causes
Communications lost between RSS and DRI.
68P02901W26-S 17-239
Nov 2007
Procedure
If... Then...
(DARE goes disabled-unlocked) and monitor the DRI.
return to service
OR BTS.


17-240 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL) is Out of Lock with the
E1 reference clock.
System action
Possible causes

• The PLL lost dc power.
• The Input reference to the PLL is lost.
68P02901W26-S 17-241
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-242 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The output power from the Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL)
synthesizer is out of limits.
System action
For MCU-based sites, if this alarm occurs three times within a 10 minute period, the DRI is
placed OOS on the third occurrence.
For InCell sites, the DRI is immediately placed OOS.
Possible causes

• The 40.96 MHz PLL lost dc power.
• DPC PLL synthesizer components failed.
68P02901W26-S 17-243
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


17-244 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 166. DRI: Control processor rmware failure
166. DRI: Control processor rmware failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The control processor in the MCU experienced a non recoverable software error.
System action
Possible causes

• An internal exception generated by a DSP.
• An internal hardware or software exception generated on an M-Cell micro.
68P02901W26-S 17-245
Nov 2007
Procedure
Procedure 17-113 Control processor rmware failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-246 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 167. DRI: Control processor conguration mismatch
167. DRI: Control processor conguration mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The control processor in the MCU is in an improper operational state.
This alarm is generated only for an M-Cell micro, M-Cell macro, Horizon micro,
System action
Possible causes

• A corrupted BSS (or specific BTS) software load.
• A momentary fault experienced by the BSS software or firmware.
68P02901W26-S 17-247
Nov 2007
Procedure
Procedure 17-114 Control processor conguration mismatch
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-248 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 168. DRI: Equalizer conguration mismatch
168. DRI: Equalizer conguration mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
One of the MCU equalizer processors is in an improper operational state.
This alarm is generated only for M-Cell micro, MCell macro, Horizon micro, Horizon
System action
Possible causes
The BSS (or specific BTS) software download failed.
68P02901W26-S 17-249
Nov 2007
Procedure
Procedure 17-115 Equalizer conguration mismatch
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-250 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Phase Lock Loop (PLL) synthesizer for the GSM timing chain is Out of Lock. Or, the output
power from the 13 MHz Phase Lock Loop (PLL) synthesizer for the GSM timing chain is out
of limits.
System action
68P02901W26-S 17-251
Nov 2007
Possible causes

• PLL synthesizer components failed.
• A faulty fiber optic downlink path from the DRI.
• GSM timing chain failure.
• The input frequency reference to the 13 MHz synthesizer failed.
Procedure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-252 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 170. DRI: M-Cell micro interconnect failure
170. DRI: M-Cell micro interconnect failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The interconnection between the transceiver unit and the EEPROM on the control processor,
Power Distribution Board (PDB) or Transceiver Frequency Module (TRX) failed.
This alarm is generated only for an M-Cell micro, M-Cell macro, Horizon micro,
System action
68P02901W26-S 17-253
Nov 2007
Possible causes

• Unequipped second DRI.
• Faulty EEPROM on the control processor.
• Faulty PDB.
• Faulty TRX hardware.
Procedure
Procedure 17-117 M-Cell micro interconnect failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-254 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 171. DRI: Invalid calibration data
171. DRI: Invalid calibration data

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The calibration data cannot be used because it has been corrupted.
micro2 and Horizon compact2, Horizon macro and Horizon II macro sites.
System action
software codes that are useful only to the programmers. Ignore any additional bytes displayed.

• Carrier.
• Timeslot.
68P02901W26-S 17-255
Nov 2007
Possible causes

• Corrupted receive, transmit or cabinet calibration data.
• Calibration data corrupted by OMC operator.
Procedure
Procedure 17-118 Invalid calibration data
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-256 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 176. DRI: Equalizer timeslot (0-7) failure
176. DRI: Equalizer timeslot (0-7) failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A watchdog timer for an equalizer DSP (0-7) has expired.
System action
The affected DRI is soft reset when this alarm occurs.
that are only useful to the programmers.
Possible causes

• Equalizer DSP hardware is faulty.
• CEB hardware is faulty.
• The equalizer DSP software is faulty.
68P02901W26-S 17-257
Nov 2007
Procedure
Procedure 17-119 Equalizer timeslot (0-7) failure
If... Then...
return to service
OR BTS.


17-258 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 184. DRI: Equalizer rmware failure
184. DRI: Equalizer rmware failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The equalizer processor experienced a non recoverable firmware error.
System action
A one-byte error code is displayed in the Additional information field containing internal
68P02901W26-S 17-259
Nov 2007
Possible causes

• The Digital Signaling Processor (DSP) generated an internal exception message.
• The equalizer hardware experienced a stack overflow or underflow.
• The DRI software experienced a stack overflow or underflow.
• The DRI software received an illegal internal software protocol instruction.
Procedure
Procedure 17-120 Equalizer rmware failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-260 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 192. DRI: Baseband hopping TDM link error
192. DRI: Baseband hopping TDM link error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The received baseband hopping data had an incorrect checksum.
This is a service affecting fault condition.
System action
The affected DRI is reset when this alarm occurs. If this alarm occurs three times, the DRI
is reset on the first two occurrences. If the alarm occurs within 20 minutes of the second
occurrence, the DRI is placed OOS.

first 00 to 07 The TDM timeslot number (0-7) affected by this
BBH TDM link error.
If this alarm was raised on a CTU2 radio type, the additional data format is:
Byte1: BBH error
68P02901W26-S 17-261
Nov 2007
Possible causes

• The TDM timeslot path connections is not correctly configured at the MCU.
• The Equalizer Control Processor is faulty.
Procedure
Procedure 17-121 Baseband hopping TDM link error
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-262 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 193. DRI: Baseband hopping GSM timeslot misalignment
193. DRI: Baseband hopping GSM timeslot

misalignment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver is unable to perform baseband hopping because the timeslot provided in the
baseband hopping data does not align with what the transceiver is expecting.
This is a service affecting fault condition.
System action
The affected DRI is reset when this alarm occurs. If this alarm occurs three times, the DRI
is reset on the first two occurrences. If the alarm occurs within 20 minutes of the second
occurrence, the DRI is placed OOS.
Two bytes corresponding to the GSM timeslot number are displayed in the Additional
information field in the output for this alarm.
If this alarm was raised on a CTU2 radio type, the additional data format is:
• Byte1: BBH error

• Byte2: Invalid parameter
68P02901W26-S 17-263
Nov 2007
Possible causes

• The TDM timeslot path connections are not properly configured at the MCU.
• TDM hardware is faulty.
Procedure
Review the event logs to determine the site where the transceiver unit causing the alarm is
located.
The actual transceiver unit at fault may not be the one that reported the alarm.
Procedure 17-122 Baseband hopping GSM timeslot misalignment
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-264 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 203. DRI: RF unit power supply unit - Input failure
203. DRI: RF unit power supply unit - Input failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Main Power Supply to RF Unit has been lost and the RF Unit is operating on the backup power
supply.
Fault code.
Possible causes

• Failure of the main ac supply into external AC/DC converter.
• Failure of supply fuse or opening of protective device.
• Failure of +25 V dc feed into the RF Unit.
• Connector or lead from the external AC/DC converter broken or removed from RF Unit
input.
Procedure
Procedure 17-123 RF unit power supply unit - Input failure
1 Investigate the loss of the main supply input.

68P02901W26-S 17-265
Nov 2007
204. DRI: RF unit over temperature Chapter 17: DRI Alarms
204. DRI: RF unit over temperature

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
AC/DC converter within the RF Head Unit has detected an Over Temperature condition.
Fault code.
Possible causes

• Failure of the building air conditioning system and subsequent increase of units ambient
temperature (greater than 45 degree centigrade).
• Incorrect positioning of RF Unit above or unit too close to external heat source.
• Blockage of air vent holes around RF Unit.
Procedure
Procedure 17-124 RF unit over temperature
1 Investigate the cause of the over temperature condition.

2 INS the DRI.
17-266 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 205. DRI: RF unit low voltage disconnect imminent
205. DRI: RF unit low voltage disconnect imminent

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Battery backup voltage is nearing the point of initiating a disconnect of the load, that is the RF
Unit.
Fault code.
Possible causes

• Failure of the main ac supply into external AC/DC converter.
• Failure of supply fuse or opening of protective device.
• Failure of +25 V dc feed into the RF Unit.
• Connector or lead from the external AC/DC converter broken or removed from RF Unit
input.
Procedure
Procedure 17-125 RF unit low voltage disconnect imminent
1 Investigate the cause of the loss of the +25 V dc supply.

2 After the power is restored, INS the DRI.
68P02901W26-S 17-267
Nov 2007
206. DRI: RF unit external alarm input Chapter 17: DRI Alarms
206. DRI: RF unit external alarm input

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Environmental
Description
External Input has a short circuit across its inputs.
Fault code.
Possible causes
Input circuit failure.
Procedure
Procedure 17-126 RF unit external alarm input
1 Investigate the cause of the input short circuit.

2 Clear the alarm.
17-268 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 207. DRI: Internal communication error
207. DRI: Internal communication error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The CTU2s cascaded integral combiner (CIC) has lost sync with the direct digital synthesizer
(DDS).
Fault code.
Possible causes
Miscommunication between CIC and DDS.
Procedure
Procedure 17-127 Internal communication error
1 Monitor the DRI.

2 If the BSS takes the DRI OOS, reset the DRI (reset_device) and monitor
again.
3 If the BSS takes the DRI OOS because of the same alarm then replace the
DRI.
68P02901W26-S 17-269
Nov 2007
208. DRI: Power amplier temperature Chapter 17: DRI Alarms
208. DRI: Power amplier temperature

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The temperature of the power amplifier has exceeded its acceptable operating temperature
range.
Possible causes

• Failure of the building air conditioner system and subsequent increase of the unit ambient
temperature.
• Cooling fans failed.
• The cable or connectors between the power amplifier output and the next RF element in
the transmit path is disconnected or broken.
17-270 68P02901W26-S
Nov 2007
Procedure
Procedure 17-128 Power amplier temperature
Take appropriate action to resolve the alarm.

68P02901W26-S 17-271
Nov 2007
210. DRI: Hopping DRI failure Chapter 17: DRI Alarms
210. DRI: Hopping DRI failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The DRI failed a baseband hopping attempt.
Possible causes

• The DRI is OOS.
• The DRI is a hopping DRI.
Procedure
Procedure 17-129 Hopping DRI failure
If... Then...
return to service
OR BTS.

17-272 68P02901W26-S
Nov 2007

68P02901W26-S 17-273
Nov 2007
211. DRI: Front end processor failure Chapter 17: DRI Alarms
211. DRI: Front end processor failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a DRI Front End Processor (FEP) failed.
Possible causes

• The DRI software is faulty.
17-274 68P02901W26-S
Nov 2007
Procedure
Procedure 17-130 Front end processor failure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-275
Nov 2007
212. DRI: Channel coder failure Chapter 17: DRI Alarms
212. DRI: Channel coder failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI Channel Coding Digital Signal Processor (CCDSP) failed.
Possible causes
The transceiver unit is faulty.
Procedure
Procedure 17-131 Channel coder failure
If... Then...
return to service
OR BTS.

17-276 68P02901W26-S
Nov 2007

68P02901W26-S 17-277
Nov 2007
213. DRI: Transceiver processor failure Chapter 17: DRI Alarms
213. DRI: Transceiver processor failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI Control Equalizer Board (CEB) failed.
On a CTU2, this alarm indicates the radio firmware has failed to respond to payload alive or
fault audit queries. For all other platforms, this alarm indicates that the Digital Radio Interface
(DRI) Radio Channel Unit (RCU) Control Equalizer Board (CEB) has failed.
System action
10 minute period, the DRI is soft reset, hard reset and then placed OOS on the third occurrence.
If this alarm is raised on a CTU2 operating in Dual Carrier Mode, the associated DRI
simultaneously undergoes the same reset-reset-OOS procedure. DRI state changes for both
DRIs are tagged to the initial alarm.
software codes that are useful only to the programmers. Ignore any additional bytes displayed.

• Fault code (of original failure).
• Additional data bytes 1 to 4.
• Timeslot.
• Carrier.
(This additional data is useful only to firmware engineering).
For other platforms, the DRI alarm code related to the DRI CCDSP that triggered the
device state check in the system displays.
17-278 68P02901W26-S
Nov 2007
Possible causes

• The Digital Radio Interface Extender (DRIX) board is faulty.
Procedure
Procedure 17-132 Transceiver processor failure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-279
Nov 2007
214. DRI: Equalizer failure Chapter 17: DRI Alarms
214. DRI: Equalizer failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI Equalizer Digitized Signal Processor (EQDSP) failed.
Possible causes

• The Radio SubSystem (RSS) software is faulty.
• The transceiver unit software is faulty.
17-280 68P02901W26-S
Nov 2007
Procedure
Procedure 17-133 Equalizer failure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-281
Nov 2007
215. DRI: Power amplier failure Chapter 17: DRI Alarms
215. DRI: Power amplier failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver unit power amplifier failed.
Possible causes

• The power amplifier is faulty.
• The FM software is faulty.
• The Radio SubSystem (RSS) software is faulty.
• The transceiver unit software is faulty.
17-282 68P02901W26-S
Nov 2007
Procedure
Procedure 17-134 Power amplier failure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-283
Nov 2007
216. DRI: Transceiver recovery failure Chapter 17: DRI Alarms
216. DRI: Transceiver recovery failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver unit has failed.
Possible causes
The transceiver unit is faulty.
Procedure
Procedure 17-135 Transceiver recovery failure
If... Then...
return to service
OR BTS.

17-284 68P02901W26-S
Nov 2007

68P02901W26-S 17-285
Nov 2007
217. DRI: Transmission suspended to conserve battery power Chapter 17: DRI Alarms
217. DRI: Transmission suspended to conserve battery

power
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The transceiver unit is not transmitting because the EAS has detected Main Power Failure (EAS
8) alarm was detected and the Battery Conservation feature is enabled.
The Additional information field displays the DRI device identifiers along with the EAS
opto-coupler number reporting the main power failure event.
Possible causes

• The Main Power alarm sensor state changed since the last time the EAS was polled by the
FM software.
• A user-defined environmental alarm is activated.
Procedure
17-286 68P02901W26-S
Nov 2007
Procedure 17-136 Transmission suspended to conserve battery power
2 Once the main power supply is running, the DRIs should return to service.
3 If not, INS the DRI.

68P02901W26-S 17-287
Nov 2007
218. DRI: Invalid transceiver calibration data Chapter 17: DRI Alarms
218. DRI: Invalid transceiver calibration data

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The antennas that are currently being used at a site cannot access any form of calibration data.
Possible causes

• A transceiver unit was installed at a site without being calibrated.
• A non calibrated transceiver unit was replaced.
• The calibration data was cleared.
• A transceiver unit was unlocked before being calibrated.
17-288 68P02901W26-S
Nov 2007
Procedure
Procedure 17-137 Invalid transceiver calibration data
Send a field representative to the site to calibrate the transceiver unit. This
problem cannot be resolved from the OMC-R.

68P02901W26-S 17-289
Nov 2007
219. DRI: GPRS not supported by radio Chapter 17: DRI Alarms
219. DRI: GPRS not supported by radio

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The transceiver unit is not equipped to support General Packet Radio Service (GPRS) system,
but the radio function assigned to the transceiver unit requires GPRS support.
Possible causes

• The transceiver unit is not able to support GPRS technology.
• The transceiver unit software or firmware is faulty.
Procedure
Procedure 17-138 GPRS not supported by radio
1 Replace the radio which can not support GPRS, with a version that
can support GPRS.
2 Assign the GPRS function to the a radio that can support GPRS.
17-290 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 221. DRI: Invalid in-call modication of destination channel type
221. DRI: Invalid in-call modication of destination

channel type
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Severity Level: Warning (5)
Description
From the firmware viewpoint, higher layers have lost track of the configuration state of the
channel coder. Whilst a call is activated as TCH/AHS, a ‘modify active channel request’ is sent to
the channel coder requesting the call be switched to TCH/FS, TCH/EFS or TCH/F(data).
This is not allowed as TRAU backhaul for the two call types are incompatible. The message
‘modify active channel request’ is only valid when TRAU rate remains the same.
Two bytes are displayed.

• First byte represents the CCDSP number reporting the mismatch.
• Second byte indicates the requested destination channel type.
Possible causes
• The channel coder has received an invalid request.
• The internal channel type data stores have been corrupted.
68P02901W26-S 17-291
Nov 2007
Procedure
Procedure 17-139 Invalid in-call modication of destination channel type
1 Monitor the DRI.

2 The BSS will reset the DRI if these alarms continue at an unacceptable rate.
4 If the BSS takes the DRI OOS because of the same alarm then replace the
DRI.
17-292 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 224. DRI: Safe test audit failure
224. DRI: Safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DRI failed a safe test audit.
Two bytes are displayed in the Additional information field, as shown in Table 17-24. The first
byte is the processor type that indicates the type of failure being reported. The second byte
is the processor number.
The following table presents the possible values.
First byte Second byte Denition

00 00 Front End Processor (FEP) failure.
01 CCDSP number Channel Coding Digital Signal Processor
(CCDSP) failure.
02 00 Control Equalizer Board (CEB) failure.
03 EQDSP number Equalizer Control Processor (EQDSP)
failure.
04 00 Power Amplifier (PA) failure.
06 00 CTU2 processor failure.
68P02901W26-S 17-293
Nov 2007
Possible causes

• DRI peripheral boards failed.
• The software is hung-up.
• The MCAP interface is malfunctioning.
• A transceiver unit hardware failure.
• Loss of power to the board.
• A transceiver peripheral board failure.
• A problem with the RSS-DRI interface.
• A faulty DRIX board.
• Faulty transceiver unit data cabling.
Procedure
Procedure 17-140 Safe test audit failure
If... Then...
return to service
OR BTS.

17-294 68P02901W26-S
Nov 2007

68P02901W26-S 17-295
Nov 2007
231. DRI: TDM interface conguration failure Chapter 17: DRI Alarms
231. DRI: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
During a TDM swap, the DRI cannot be placed on the correct TDM highway.
System action
If the alarm recurs when the board is reset for TBUS reconfiguration, the board is placed OOS.
Possible causes

• During a TDM swap, the DRI cannot be placed on the correct TDM.
• The MCAP bus is malfunctioning.
• The GPROC is malfunctioning.
17-296 68P02901W26-S
Nov 2007
Procedure
If... Then...
return to service
OR BTS.


68P02901W26-S 17-297
Nov 2007
234. DRI: Active link connection failure Chapter 17: DRI Alarms
234. DRI: Active link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One or more of the following active link connections between the transceiver unit and the
BTP failed.
• A FOX-to-TCU connection (fiber link).
• An FMUX-to-remote FMUX connection (fiber link).
• A BTP-to-FOX connection (backplane).
• A BTP-to-FMUX connection (backplane).
• An MCUF (BTP)-to-remote XMUX connection (fiber link).
• FMUX-to-XMUX connection (fiber link).
This alarm is generated for M-Cell2, M-Cell6, M-Cell micro, Horizon macro,
Horizon II macro extension equipment.
The Additional information field includes eight bytes, as shown in Table 17-25. The first four
bytes indicate the alarm context. The last four bytes indicate the error code.
17-298 68P02901W26-S
Nov 2007
Bytes one to four Bytes ve to eight Description

00 00 00 01 00 00 00 01 HDLC connect confirm.
00 00 00 02 HDLC connect indication.
00 00 00 03 HDLC disconnect indication.
00 00 00 02 00 00 01 00 Loss of data on TCU link.
00 00 02 00 Loss of synchronization to TCU link.
00 00 04 00 Uncorrected delay compensation.
00 00 08 00 BBH routing data parity error.
Possible causes

• The BTP device failed.
• The portion of the transceiver unit and/or the active BTP board that supports the active
BTP link connection failed.
• A port on the active Fiber Optic Extender (FOX) board failed. This alarm does not occur if
the entire FOX board has failed.
• A port on the active Fiber Optic Multiplexer (FMUX) board failed. This alarm does not
occur if the entire FMUX board has failed.
• A port on the active XMUX board failed. This alarm does not occur if the entire XMUX
board has failed.
68P02901W26-S 17-299
Nov 2007
Procedure

required.
2 Reset the DRI.
required.
site to replace the transceiver unit
or take corrective action for the
failures listed in Possible causes.

17-300 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 235. DRI: Standby link connection failure
235. DRI: Standby link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One or more of the following standby link connections between the transceiver unit and the
BTP failed.
• A FOX-to-TCU connection (fiber link).
• An FMUX-to-remote FMUX connection (fiber link).
• An MCU-to-FOX connection (backplane).
• An MCU-to-FMUX connection (backplane).
• An MCUF (BTP)-to-remote XMUX connection (fiber link).
• FMUX-to-XMUX connection (fiber link).
• A BTP-to-XMUX connection (backplane).
This alarm is generated for M-Cell2, M-Cell6, M-Cell micro, Horizon macro,
Horizon II macro extension equipment.
There is no Additional information field in the output for this alarm.
68P02901W26-S 17-301
Nov 2007
Possible causes

• The BTP device failed.
• The portion of the transceiver unit and/or the active BTP board that supports the active
BTP link connection failed.
• A port on the active Fiber Optic Extender (FOX) board failed. This alarm does not occur if
the entire FOX board has failed.
• A port on the active Fiber Optic Multiplexer (FMUX) board failed. This alarm does not
occur if the entire FMUX board has failed.
Procedure
Procedure 17-143 Standby link connection failure
1 Check all the connections as listed in the Description.

2 Ensure that they are in proper order.
17-302 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 236. DRI: Slow ash failure
236. DRI: Slow ash failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A failure to read or write to a slow flash EEPROM was detected for the transceiver unit.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon macro, Horizon
micro, Horizon micro2, Horizon compact and Horizon compact2 sites.
Possible causes
The flash EEPROM on the transceiver unit is faulty.
68P02901W26-S 17-303
Nov 2007
Procedure
Procedure 17-144 Slow ash failure

required.
2 Reset the DRI.
busy-unlocked and the alarm The fault condition no longer
has not cleared exists. No further action is
required.

17-304 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 237. DRI: Non-volatile memory failure
237. DRI: Non-volatile memory failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A failure to read or write to the Non-Volatile (NV) flash EEPROM was detected for the
transceiver unit.
Possible causes
The NV flash EEPROM on the transceiver unit is faulty.
68P02901W26-S 17-305
Nov 2007
Procedure
Procedure 17-145 Non-volatile memory failure
If... Then...
the DRI fails to go
busy-unlocked after
return to service


17-306 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. DRI: Process safe test audit failure
239. DRI: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The DRI failed a process safe test audit. The process safe test audit verifies the proper operation
The Additional information field includes nine bytes containing process information, as shown in
Table 17-26. Byte nine is the reason code for the alarm.

one Process ID of the process being audited.
two, three CPU number.
four Percentage of CPU utilization by the process
being audited.
five - eight Useful only to the programmers.
Continued
68P02901W26-S 17-307
Nov 2007
Table 17-26 Additional information eld contents (Continued)

nine 00 The process that failed the audit is in an infinite
loop.
02 Higher priority processes prevented the process
that failed to run.
Possible causes
A process executing on the DRI failed to respond to the System Audit Process.
Procedure

field.
2 Go to step 2.
2 Perform the safe test audit on the DRI.
If the DRI... Then...
Continued
17-308 68P02901W26-S
Nov 2007
Procedure 17-146 Process safe test audit failure (Continued)

3 Reset the DRI.
required.
site to replace the transceiver
unit.

68P02901W26-S 17-309
Nov 2007
241. DRI: Standby link connected to wrong device Chapter 17: DRI Alarms
241. DRI: Standby link connected to wrong device

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the standby link connections in a BTS or extended cabinet is incorrect. This alarm is
generated for each incorrect standby link connection that is identified.
This alarm is generated for M-Cell2, M-Cell6, Horizon macro, Horizon II macro
extension equipment.
Possible connection failures
One (or more) of the following connections may be incorrect:

• A standby FOX-to-TCU connection.
• A standby MCU-to-TCU connection.
• A standby FMUX-to-standby FMUX connection.
• A standby MCUF (BTP)-to-remote XMUX connection (fiber link).
• A standby FMUX-to-XMUX connection (fiber link).
• A standby BTP-to-XMUX connection (backplane).
17-310 68P02901W26-S
Nov 2007
Possible causes

• The standby FOX is connected to the wrong TCU port.
• The standby MCU is connected to the wrong TCU.
• The standby FMUX is placed in the wrong slot.
• The standby FMUX is connected to the wrong standby FMUX in another extended cabinet.
Procedure
Procedure 17-147 Standby link connected to wrong device
1 Determine whether more than two separate DRI devices in a cabinet

at a site are generating this alarm.
If the number of DRIs Then...
generating this alarm is...
three or more DRIs in a single This fault is probably occurring in
cage a standby FMUX-to-standby FMUX
connection between two cabinets.
Go to step 2.
one or two DRIs in a single cage The fault is probably occurring
within one (or more) connection(s)
or because a board has been
placed in the wrong slot:
• A standby FOX-to-TCU
connection.
• A standby MCU-to-TCU
connection.
• A standby FMUX board

currently resides in the
wrong slot.
Go to step 2.
Continued
68P02901W26-S 17-311
Nov 2007
Procedure 17-147 Standby link connected to wrong device (Continued)

2 Send a field representative to the site to check and verify the
configuration of all M-Cell2 and/or M-Cell6 cage and cabinet
connections. If necessary at site, reconfigure the connections as
shown in site specification documents.
The active and the standby cages within a cabinet

(and between extended cabinets) must have identical
connection configurations. Otherwise, this fault condition
occurs. Refer to the site specification documents to verify
that the active as well as the standby cage connections
are correct.

17-312 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 243. DRI: Unlocked device not in service
243. DRI: Unlocked device not in service

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
An unlocked DRI is OOS due an unspecified fault. This alarm is generated only if there is no
primary alarm active on the device.
Possible causes
The system failed to bring the device in service.
Procedure
68P02901W26-S 17-313
Nov 2007
Procedure 17-148 Unlocked device not in service

2 Reset the DRI.
required.
site to replace the transceiver unit
(possibly DRI board).

17-314 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. DRI: Device failure
254. DRI: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The DRI was placed OOS after a fault caused it to report the Reset Due To Recurring Fault
(DRI 35).
Possible causes
Board removed from service due to a fault.
Procedure
1 If this alarm occurs three times within a 10 minute period, the DRI is soft
reset on the first two occurrences and then placed OOS on the third.
2 If the alarm is raised on a CTU2 operating in dual carrier mode due to
intermittent fault reporting, both carriers are taken OOS.
3 Send a field representative to replace the DRI generating the alarm.
68P02901W26-S 17-315
Nov 2007

17-316 68P02901W26-S
Nov 2007
Chapter
18
EAS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details EAS alarms and includes the following alarm procedures:
• 0. EAS: Unexpected board type on page 18-3.
• 1. EAS: Serial bus connection failure on page 18-5.
• 8. EAS: EAS has detected main power failure on page 18-7.
• 16 - 31. EAS: Optocoupler 1-16 on page 18-9.
68P02901W26-S 18-1
Nov 2007
Introduction to EAS alarms Chapter 18: EAS Alarms
Introduction to EAS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
EAS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the External
Alarm System (EAS).
The interface hardware for this system is provided by the Parallel Interface Extender (PIX)
board. The EAS is responsible for the monitoring of all customer-defined environmental alarms.
The customer defines the alarm string and the severity of these alarms based on the individual
requirements of the BSS site.
When any of the following alarms are active:
• 94.IAS: No Connection to Alarms Board - Connection Broken.

• 97.IAS: No Connection to Alarms Board - Radio OOS.
• 99.IAS: No Connection to Alarms Board - Alarm Board Removed.
All other IAS and EAS alarms in the active list (execute disp_act <site #>
command) are not dependable.
EAS site requirements
The individual requirements for EAS alarms are determined relative to the specific environment
of the BSS site which is external to the cabinets. Cabinet alarms are typically classified under
Internal Alarm System (IAS) alarms. Some of the examples of EAS alarm strings are Door open,
High humidity, Low humidity, Fire and Intruder.
18-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. EAS: Unexpected board type
0. EAS: Unexpected board type

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A Parallel Interface Extender (PIX) board is not responding properly when polled by the FM
software. This alarm indicates that during the current polling of the EAS by the FM software,
the response from the PIX board was inappropriate.
System action
The system places the EAS device OOS.
Possible causes

• The PIX board is faulty.
• The slot specified for a PIX board is occupied by a board other than a PIX board.
68P02901W26-S 18-3
Nov 2007
Procedure Chapter 18: EAS Alarms
Procedure
Determine the state of the EAS device.
If the EAS is... Then...

required. If this alarm recurs for
the same device, the PIX board
may have an intermittent fault.
site to replace the PIX board.
and take the appropriate action.

18-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. EAS: Serial bus connection failure
1. EAS: Serial bus connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The physical connection between the Parallel Interface Extender (PIX) board and the SBUS
device is broken. When this occurs, the PIX is not able to communicate with the processor
to report the EAS alarms.
System action
The system places the EAS device OOS.
Possible causes

• The PIX board was improperly installed.
• The PIX board is faulty.
• The polling processor board is faulty.
68P02901W26-S 18-5
Nov 2007
Procedure
Attempt to restore the EAS board to service.
If the EAS board... Then...

returns to service The fault condition no longer
required. If this alarm recurs
for the same device, send a field
representative to determine the
cause of the alarm and take the
appropriate action.
does not return to service Send a field representative to

18-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. EAS: EAS has detected main power failure
8. EAS: EAS has detected main power failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The EAS has detected a main ac power failure.
System action
If the battery conservation feature is enabled, the system limits the number of transceivers that
are left online to the user-specified value of the carriers_ins_pwr_fail database parameter.
For a description of the carriers_ins_pwr_fail database parameter, refer to Technical

Description: BSS Command Reference (68P02901W23).
Possible causes

• The main ac power source failed.
• The main power failure environmental sensor failed.
68P02901W26-S 18-7
Nov 2007
Procedure
Determine if there is a power failure.
Procedure 18-3 EAS has detected main power failure
If there is... Then...

a power failure Follow normal power outage
response procedures. If this
alarm is not cleared when
power is restored, send a field
representative to determine the
cause of the alarm and take the
appropriate action.
is not a power failure Send a field representative to

18-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 16 - 31. EAS: Optocoupler 1-16
16 - 31. EAS: Optocoupler 1-16

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Severity Level: Dependent upon the parameter monitored
and the alarm threshold configured.
Description
The system detected a change in state of an EAS optocoupler sensor. Optocoupler sensors are
used to report user-defined environmental conditions at a site.
For commands and parameters related to EAS alarm configuration, refer to Technical
Description: BSS Command Reference (68P02901W23).
The BSS suppresses EAS alarms 28, 29, 30 and 31 where the cabinet type is Horizon II mini or
Horizon II mini extension.
An alphanumeric text string containing the user-specified EAS alarm text and the alarm index
number.
For example, Low Humidity (6).
In the example, Low Humidity is the user-specified environmental condition and 6 is the alarm
index number identifying the specific optocoupler that changed states. The index number
follows the alarm string name and is enclosed in parentheses.
68P02901W26-S 18-9
Nov 2007
Possible causes Chapter 18: EAS Alarms
Possible causes

• An environmental sensor may have changed due to a user-defined environmental (variable)
factor.
• An environmental sensor may have failed.
• A PIX card may have failed causing an environmental sensor to undergo a state change.
Procedure
Procedure 18-4 EAS: Optocoupler 1-16
1 Follow the procedures established for the resolution of the environmental

condition indicated by the alarm.
2 Clear the alarm.
18-10 68P02901W26-S
Nov 2007
Chapter
19
ETH Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details ETH alarms and includes the following alarm procedures:
{26740/28351}0. ETH: Ethernet Link Disconnected on page 19-2
{26740}1. ETH: Excessive PSI_TRAU FILL FRAME TX on page 19-4
{26740/28351}2. ETH: Excessive ETH RX ERRORS on page 19-5
{26740/28351}3. ETH: Excessive ETH TX ERRORS on page 19-6
{26740/28351}4. ETH: Unsupported Auto-Negotiated Signaling Rate on page 19-7
{26740}5. ETH: DSW/DSWX Switching Hardware Required on page 19-9
68P02901W26-S 19-1
Nov 2007
0. ETH: Ethernet Link Disconnected Chapter 19: ETH Alarms
0. ETH: Ethernet Link Disconnected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740/28351}
Clearing Type: FMIC

Description
This alarm indicates that an Ethernet link disconnection on the PSI or DPROC (PXP) is occurred.
Possible causes
• Disconnection of the Ethernet link on a PSI/DPROC (PXP) due to a normal disconnection

process.
• Problem with the protocol or medium causing an unexpected disconnection.
19-2 68P02901W26-S
Nov 2007
Procedure
Use this procedure to resolve the alarm.
Procedure 19-1 Ethernet Link Disconnected
If..... Then...
the available ETHs connecting wait for at least ten minutes before
to the same PCU/BSC are OOS taking any action as PCU/BSC may
be reset.
the alarm does not clear after check the status of the
PCU/BSC is back in-service corresponding PSI/DPROC
for this ETH.
the PSI/DPROC is OOS get it in-serviced by performing an
INS command on that device.
PSI/DPROC is INS and the change the Ethernet cable.
alarm does not clear
68P02901W26-S 19-3
Nov 2007
1. ETH: Excessive PSI_TRAU FILL FRAME TX Chapter 19: ETH Alarms
1. ETH: Excessive PSI_TRAU FILL FRAME TX

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}

Description
This alarm is only for the PSI to indicate the percentage of TRAU fill frames on PSI that exceeds
the threshold. This percentage will be on per ETH device basis. The database parameter
specifies the maximum allowable percentage of TRAU fill frames.
Additional data is of 1 byte: Byte 1: Value of PSI TRAU FILL FRAME TX.
Possible causes
The number of TRAU fill frames on PSI has exceeded the threshold.
Procedure
Procedure 19-2 Excessive PSI_TRAU FILL FRAME TX
1 Check if the alarm is precursor to serious fault conditions.

2 Check for high load on DPROC (PXP).
3 Check for congestion on link between PSI and DPROC (PXP).
19-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. ETH: Excessive ETH RX ERRORS
2. ETH: Excessive ETH RX ERRORS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740/28351}

Description
The alarm indicates the percentage of ETH receive errors that exceeds the threshold. It is per
ETH device basis on both the PSI and DPROC (PXP). The new database parameter specifies the
maximum allowable percentage of Ethernet frames received as error among all received frames.
Additional data is of 1 byte: Byte 1 = Value of ETH RX ERRORS.
Possible causes
The number of PSI/DPROC (PXP) receiving errors has exceeded the threshold.
Procedure
Procedure 19-3 Excessive ETH RX ERRORS

2 Check for congestion or noise on the Ethernet Link.
68P02901W26-S 19-5
Nov 2007
3. ETH: Excessive ETH TX ERRORS Chapter 19: ETH Alarms
3. ETH: Excessive ETH TX ERRORS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740/28351}

Description
This alarm indicates the percentage of ETH transmit errors that exceeds the threshold. The
percentage is on a per ETH device basis on both the PSI and DPROC (PXP). The new database
parameter specifies the maximum percentage of Ethernet transmit errors among all transmitted
frames.
Additional data is of 1 byte: Byte 1= Value of ETH TX ERRORS.
Possible causes
The number of PSI/DPROC (PXP) transmitting errors has exceeded the threshold.
Procedure
Procedure 19-4 Excessive ETH TX ERRORS

2 Check for congestion or noise on the Ethernet Link.
19-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. ETH: Unsupported Auto-Negotiated Signaling Rate
4. ETH: Unsupported Auto-Negotiated Signaling Rate

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740/28351}
Clearing Type: FMIC

Description
This alarm gives an indication whether the Ethernet link on the PSI/DPROC (PXP) is attempting
to operate in a mode other than 1000BASE-T or 100BASE-TX (full duplex).
Possible causes
Ethernet link on a PSI/DPROC (PXP) auto-negotiation failed due to incorrect configuration or

incorrect cable.
68P02901W26-S 19-7
Nov 2007
Procedure Chapter 19: ETH Alarms
Procedure
Use the following procedures to resolve the alarm.
Procedure 19-5 Unsupported Auto-Negotiated Signaling Rate for PSI
If..... Then...
the available ETHs connecting wait for at least 10 mins before
to the same PCU/BSC are OOS taking any action as PCU/BSC may
be resetting.
the alarm does not clear after check the status of the
PCU/BSC is back in-service corresponding PSI/DPROC
for this ETH.
the PSI/DPROC is OOS get it in-serviced by performing an
INS command on that device.
PSI/DPROC is INS and the change the Ethernet cable or
alarm does not clear check the equipment configuration
of the directly attached device.
19-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. ETH: DSW/DSWX Switching Hardware Required
5. ETH: DSW/DSWX Switching Hardware Required

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the BSS SW at the BSC determines that the enhanced capacity
mode is not available during site initialization. The alarm is generated for OOS ETH due to
Enhanced Capacity Mode unavailable with the reason DSW/DSWX Required.
This alarm is not applicable when the total number of TDM highway timeslots
allocated to the highway (including PSI) is less than 1024 and the BSC has no
extension cage.
Possible causes
KSW and KSWX switching hardware remains enabled in the site or enhanced capacity mode
has not been enabled.
68P02901W26-S 19-9
Nov 2007
Procedure Chapter 19: ETH Alarms
Procedure
Procedure 19-6 DSW/DSWX Switching Hardware Required
1 Replace all KSW and KSWX switching hardware with DSW and DSWX
switching hardware.
2 Ensure that the enhanced capacity mode is enabled.
19-10 68P02901W26-S
Nov 2007
Chapter
20
GBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GBL alarms and includes the following alarm procedures:
• 0. GBL: Link disconnected on page 20-3.
• 1. GBL: NSVC failure on page 20-5.
68P02901W26-S 20-1
Nov 2007
Introduction to GBL alarms Chapter 20: GBL Alarms
Introduction to GBL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GBL alarms
Control Unit (PCU) Gb Link (GBL) interface between the BSS and the Serving GPRS Support
Node (SGSN).
20-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. GBL: Link disconnected
0. GBL: Link disconnected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GBL interface between the BSS and the Serving GPRS Support Node (SGSN) was
disconnected. All resources supported by the GBL are removed from service. An attempt
is continuously made to reconnect the link.
This is a GPRS service-affecting fault condition.
Last GBL link disconnected
If this alarm generated for a GBL happens to be the last available link for service, the Last
GBL Link Failed (BSS 27) alarm is reported.
The MMS ID where the GBL is equipped is displayed. For example, the format is MMS 5 0 0.
Possible causes

• The GBL cable was physically disconnected.
• The link protocol caused an unexpected link disconnection to occur.
• The MMS on the MSI board is faulty.
• The physical media (For example, E1 links, satellite links, microwave links, trunking
equipment) is faulty.
68P02901W26-S 20-3
Nov 2007
Procedure Chapter 20: GBL Alarms
Procedure
Attempt to return the GBL to service.
Procedure 20-1 Link disconnected
If the GBL... Then...

intermittent link fault at the site.
site to troubleshoot the link fault.
site to troubleshoot the link fault.

20-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GBL: NSVC failure
1. GBL: NSVC failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm is reported when the first NSVC on a GBL fails. It can indicate that one or more
NSVCs have failed on this GBL.
The system will continue to attempt to bring the NSVCs into service.
Possible causes

• NSVC parameters do not match between PCU side and SGSN side.
• Problems with Frame Relay layer.
Procedure
Procedure 20-2 NSVC failure
1 Check connections and verify GBL timeslots match between PCU and
SGSN, correct NSVC parameters to match between PCU and SGSN sides
if not same.
2 Verify end-to-end frame relay parameters or connections.
68P02901W26-S 20-5
Nov 2007
Procedure Chapter 20: GBL Alarms
20-6 68P02901W26-S
Nov 2007
Chapter
21
GCLK Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GCLK alarms and includes the following alarm procedures:
• 0. GCLK: Reference distribution module failure on page 21-3.
• 2. GCLK: Clock reference failure on page 21-5.
• 3. GCLK: Hardware Fault Detected on page 21-8.
• 4. GCLK: Phase lock lost on page 21-9.
• 5. GCLK: 125 µs reference count overflow on page 21-13.
• 6. GCLK: 60 ms reference count overflow on page 21-15.
• 7. GCLK: 6.12 seconds reference count overflow on page 21-17.
• 8. GCLK: Frequency difference in mate GCLK on page 21-19.
• 9. GCLK: Hard reset on page 21-22.
• 11. GCLK: Long term average values are unstable on page 21-25.
• 12. GCLK: Unrecognized hardware revision level on page 21-27.
• 14. GCLK: Phase lock failure on page 21-28.
• 15. GCLK: Watchdog timer expired on page 21-32.
• 16. GCLK: Clock output failure on page 21-34.
• 17. GCLK: SYNC shutdown request on page 21-36.
• 18. GCLK: Not operational on page 21-38.
• 19. GCLK: Warm up failure on page 21-40.
• 20. GCLK: Invalid mode on page 21-42.
• 21. GCLK: Calibration in progress on page 21-44.
• 22. GCLK: Firmware initiated calibration on page 21-45.
• 24. GCLK: Bad clock source or OCXO (oscillator) replacement required on page 21-46.
• 26. GCLK: GCLK calibration request on page 21-49.
• 232. GCLK: Processor bus communication failure on page 21-52.
68P02901W26-S 21-1
Nov 2007
Introduction to GCLK alarms Chapter 21: GCLK Alarms
Introduction to GCLK alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GCLK alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Generic Clock
(GCLK) device, including GCLK Synchronization (SYNC) feature alarms.
FRUs
A GCLK device may be equipped on one of the FRUs shown in Table 21-1.
Table 21-1 GCLK FRUs
FRU Description
GCLK Generic Clock board.
MCU GCLK SYNC portion of an M-Cell Main Control Unit.
MCUF GCLK SYNC portion of an M-Cell micro Main Control
Unit.
MCUm GCLK SYNC portion of an M-Cell micro Main Control
Unit.
ARENAm (MCU) GCLK SYNC portion of an Horizon micro (M-Cell
arena) Main Control Unit.
ARENA MAC (MCU) GCLK SYNC portion of an Horizon compact (M-Cell
arena Macro) Main Control Unit.
Throughout this chapter, frequent reference is made to InCell and non-InCell (M-Cell)
BTSs. Assume InCell BTS to mean a BTS4, BTS5, BTS6, ExCell, or TopCell. A
non-InCell BTS refers to any BTS other than those defined by the term InCell BTS.
21-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. GCLK: Reference distribution module failure
0. GCLK: Reference distribution module failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Oven Controlled Crystal Oscillator (OCXO) on the GCLK board failed.
System action
The GCLK is placed OOS.
The MCAP interrupt is generated if interrupt is enabled. A master or redundant

change over occurs if no faults exist on the redundant GCLK.
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes

• The GCLK Reference Distribution Module (RDM) failed.
• The RDM failure detection circuitry malfunctioned.
68P02901W26-S 21-3
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
Determine the current operational and administrative states of the GCLK.
Procedure 21-1 Reference distribution module failure
If the GCLK is... Then...

exists. Further fault isolation is
not required.
enabled-unlocked The alarm condition no longer
not required.
disabled-unlocked Send a field representative to the
site to replace the faulty GCLK.

21-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. GCLK: Clock reference failure
2. GCLK: Clock reference failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The clock extracted by the MSI is lost.
System action
The system waits for the period specified in the wait_for_reselection database parameter to
determine if the MMS is in service. If the MMS is OOS after the wait period expires, the system
selects a new MMS for clock reference signal extraction if one is available.
If another MMS is not available for clock reference signal extraction, the GCLK is placed in the
set frequency mode.
The Additional information field displays MCAP register values and alarm source that are useful
only to programmers. The Additional information field also displays the identifiers for the MMS
device used for reference clock signal extraction, as shown in Table 21-2.
Table 21-2 Additional information elds contents

first FF or 10 The numeric representation of the MMS
device that is equipped on a MSI board.
The MMS device identifiers are displayed in the next three bytes in the following order.
second 00 to 32 or FF Device ID 1 - Identifies the MSI where the
MMS is equipped.
third 0, 1 or FF Device ID 2 - Identifies the specific MMS on
the MSI board.
fourth 0 or FF Device ID 3 - Serves as a placeholder.
fifth 1 or 2 Alarm source useful only to programmers.
68P02901W26-S 21-5
Nov 2007
Possible causes Chapter 21: GCLK Alarms
Possible causes

• E1 link lines are faulty.
• No clock is being sent from a MSI/NIU.
• No clock is being sent from an XCDR.
• A GCLK reference clock detection circuit failed.
Procedure
Procedure 21-2 Clock reference failure
1 Determine if this is a recurrence of this alarm.

If is... Then...
site to investigate the E1 links.
2 Determine if an alternate MMS is available for clock reference
extraction.
If an alternate MMS is... Then...
available Go to step 3.
not available Go to step 4.
3 Select an alternate MMS for clock reference signal extraction.
did not clear Go to step 4.
cleared Send a field representative to the
site to investigate the E1 links
and/or replace the faulty MSI
board.
4 Reset the MSI.
Continued
21-6 68P02901W26-S
Nov 2007
Procedure 21-2 Clock reference failure (Continued)

5 Determine if the alarm cleared after the MSI reset is complete.
cleared The fault condition no longer
required.
did not clear Replace the MSI. If the alarm is
not cleared by this action, go to
step 6.
6 Reset the GCLK.
7 Determine if the alarm cleared after the GCLK reset is complete.
required.
did not clear Send a field representative to the

68P02901W26-S 21-7
Nov 2007
3. GCLK: Hardware Fault Detected Chapter 21: GCLK Alarms
3. GCLK: Hardware Fault Detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the hardware has entered in an unrecoverable hardware state.
4 hex bytes of GCLK register values. The first byte contains the Interrupt Request Register
Value. The second byte contains the Status Register Value. The third byte contains Status H
Register value. The fourth byte contains Hardware Fault Register Value.
Possible causes
GCLK hardware has entered an invalid state within the hardware state machine design.
Procedure
Audit the GCLK device, if the alarm is still on, physically remove the board from the cage,
reinsert and INS the GCLK.
21-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. GCLK: Phase lock lost
4. GCLK: Phase lock lost

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Phase Lock Loop (PLL) circuit has lost phase lock to the incoming clock reference signal.
The frequency of this alarm is dependent on the quality of the E1 links. Normally, this alarm
does not affect traffic or signaling quality.
System action
The system attempts to lock on the existing MMS. If it cannot achieve lock, a new MMS is
selected as a reference source if one is available. The phase locking process is automatically
re-initiated for each MMS with a priority greater than zero.
If no more MMSs are available for clock reference signal extraction, the GCLK is placed in the
set frequency mode.
InCell site
68P02901W26-S 21-9
Nov 2007
M-Cell site
The Additional information field displays the identifiers for the MMS device used for clock
reference signal extraction, as shown in Table 21-3.
Table 21-3 Additional information elds contents

second 00 to 32 or FF Device ID 1 - Identifies the MSI where the
MMS is equipped.
third 0, 1 or FF Device ID 2 - Identifies the specific MMS
on the MSI board.
Possible causes

• Wander or jitter on the E1 link exceeded allowed G823, 824, 825 threshold causing the
loss of lock. This is the most likely cause.
• The clock reference source has failed or is out of specification.
• The GCLK hardware failed.
• The GCLK OCXO has aged significantly and can no longer follow the source clock.
Procedure
Procedure 21-3 Phase lock lost
1 Determine whether this alarm is intermittent: if so, send a field

representative to the site to check the link status, prepared to
replace a faulty link, GCLK or MCU.
Continued
21-10 68P02901W26-S
Nov 2007
Procedure 21-3 Phase lock lost (Continued)

2 Determine if any two Gulls report this alarm at the same time.
If any two GCLKs... Then...
report this alarm This alarm was generated as
the result of a link problem.
site to resolve the E1 link fault.
do not report this alarm Go to step 3.
3 Determine if any MMS alarms are reported.
MMS alarms This alarm was generated as
the result of a MMS fault.
Resolve the MMS alarm. If this
alarm is not cleared after the MMS
alarms are resolved, go to step 4.
no MMS alarms Go to step 4.
4 Determine if the uplink BTS lost phase lock.
If the uplink BTS... Then...
lost phase lock Troubleshoot the uplink site.
did not lose phase lock Go to step 5.
5 Determine if the site reporting the alarm is part of a star
configuration.
part of a star configuration There is an E1 link fault. Send a
where other sites in the star field representative to the site to
occasionally lose phase lock resolve the E1 link fault.
part of a star configuration, but Go to step 6.
no other sites lost phase lock
not part of a star configuration Go to step 6.
6 Determine what type of site is reporting the alarm.
an InCell site Go to step 7.
a MCU-based site Go to step 8.
Continued
68P02901W26-S 21-11
Nov 2007
Procedure 21-3 Phase lock lost (Continued)

7 Determine if both GCLKs are reporting the same alarm.
If both GCLKs... Then...
are reporting the same alarm There is an E1 link fault. Send a
resolve the E1 link fault.
are not reporting the same Send a field representative to
alarm the site to calibrate the GCLK.
If this alarms recurs after the
GCLK is recalibrated, replace the
GCLK.
8 Determine if there is a redundant MCU available.
If a redundant MCU is... Then...
available Force a swap to the redundant
MCU. If the alarm clears, send
a field representative to the site
to replace the faulty MCU. If
the alarm does not clear, send a
resolve the E1 link fault.
not available Go to step 9.
9 The problem is probably a bad link. Observe statistical data over a
24 hour period at the OMC to confirm bad link. If the link problem
still persists, send a field representative to the site to resolve the E1
link fault. If the alarm does not clear after resolving the link fault,
replace the MCU.

21-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. GCLK: 125 µs reference count overow
5. GCLK: 125 µs reference count overow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The counter has been preloaded with an illegally low value during synchronization, causing a
delay of more than 125 µs between consecutive 125 µs reference pulses. This may cause 125 µs
reference failure reports on the other digital boards.
This alarm occurs as the result of a swap and then clears automatically.
System action
If this alarm is reported twice within 7 seconds, the GCLK is placed OOS.
Possible causes

• A GCLK swap.
• A GCLK hardware fault.
68P02901W26-S 21-13
Nov 2007
Procedure
Procedure 21-4 125 µs reference count overow

If is... Then...
site to replace the faulty GCLK
board.
2 Determine the current operational and administrative states of the
GCLK.
busy-unlocked The alarm condition no longer
not required.
not required.

21-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. GCLK: 60 ms reference count overow
6. GCLK: 60 ms reference count overow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The counter has been preloaded with an illegally low value during synchronization, causing a
delay of more than 60 ms between consecutive 60 ms reference pulses. This may cause 60 ms
reference failure reports on the other digital boards.
System action
If this alarm is reported twice within seven seconds, the GCLK is placed OOS.
Possible causes

• A GCLK swap.
68P02901W26-S 21-15
Nov 2007
Procedure
Procedure 21-5 60 ms reference count overow

If is... Then...
board.
GCLK.
not required.
not required.

21-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. GCLK: 6.12 seconds reference count overow
7. GCLK: 6.12 seconds reference count overow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The counter preloaded with an illegally low value during synchronization, causing a delay of
more than 6.12 seconds between consecutive 6.12 seconds reference pulses. This may cause
6.12 seconds reference failure reports on the other digital boards.
System action
If this alarm is reported twice within 7 seconds, the GCLK is placed OOS.
Possible causes

• A GCLK swap.
68P02901W26-S 21-17
Nov 2007
Procedure
Procedure 21-6 6.12 seconds reference count overow

If is... Then...
board.
GCLK.
not required.
not required.

21-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. GCLK: Frequency difference in mate GCLK
8. GCLK: Frequency difference in mate GCLK

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A difference greater than 0.655 Hz exists between the two equipped GCLKs.
This alarm applies only to InCell sites.
MCAP
An MCAP interrupt is generated, if interrupt capability is enabled.
Possible causes
One or both of the GCLKs may require recalibration.
68P02901W26-S 21-19
Nov 2007
Procedure
Procedure 21-7 Frequency difference in mate GCLK
1 Determine if the Long-Term-Average Values are unstable (GCLK 11)

alarm is reported for either GCLK.
If GCLK 11 alarm... Then...
was reported If there is a GCLK 4 alarm, then
a link problem exists. Send a
to resolve the link problem.
If this alarm recurs after the link
problem is resolved, go to step 2.
was not reported Go to step 2.
If GCLK 11 is reported, GCLK 4 also ought to be reported:

both GCLKs mirror each other in normal working. When
this is not so, the reason for the difference in behavior
needs investigation.
2 Determine if the Phase Lock Lost (GCLK 4) alarm was reported for
either GCLK.
If the GCLK 4 alarm... Then...
was reported Resolve the GCLK 4 alarm. If this
alarm does not clear after the
GCLK 4 alarm is resolved, go to
step 3.
was not reported Go to step 3.
3 Reset both GCLKs.
cleared The fault condition
no longer exists.
Further fault isolation is not
required.
Continued
21-20 68P02901W26-S
Nov 2007
Procedure 21-7 Frequency difference in mate GCLK (Continued)

5 Determine if the GCLK reporting the alarm is phased locked.
phase locked Got to step 5.
not phase locked Send a field representative to the
site to recalibrate the GCLK. If this
alarm recurs after the GCLK is
recalibrated, replace the GCLK.
6 Send a field representative to the site to recalibrate the GCLK
not reporting the alarm. If this alarm recurs after the GCLK is
recalibrated, send a field representative to the site to replace the
GCLK.

68P02901W26-S 21-21
Nov 2007
9. GCLK: Hard reset Chapter 21: GCLK Alarms
9. GCLK: Hard reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GCLK device is currently undergoing a hard reset.
System action
The system re-initializes the GCLK.
Possible causes

• The device was reset using the front panel switch.
• The device was reset by the software.
21-22 68P02901W26-S
Nov 2007
Procedure

If this is... Then...
board.
Wait for one minute after receiving the alarm report

before continuing to step 2.
GCLK.
not required.
not required.
disabled-unlocked Go to step 3.
3 Reset the GCLK.
GCLK.
not required.
not required.
68P02901W26-S 21-23
Nov 2007

21-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. GCLK: Long term average values are unstable
11. GCLK: Long term average values are unstable

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Of the values used to calculate the Long-Term-Average (LTA), 25% or more exceed the alarm
range specified by the lta_alarm_range database parameter.
This alarm applies only to InCell sites.
Possible causes

• The sample values varied more than would normally be expected due to temperature
changes throughout the day.
• The reference clock signal wandered from its ideal frequency.
• Poor E1 links.
68P02901W26-S 21-25
Nov 2007
Procedure
Procedure 21-9 Long term average values are unstable
1 Check for the presence of other alarms that indicate a link fault.
2 Determine if other sites are reporting this alarm.
If other sites are... Then...
reporting this alarm The reference clock signal is faulty.
Resolve the reference clock signal
fault.
are not reporting this alarm Go to step 3.
3 Send a field representative to the site prepared to replace a faulty
link or GCLK:
• Investigate the link if other alarms also indicate a faulty link

and replace, if necessary.
• If no other alarms indicate a faulty link, replace the GCLK.

21-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 12. GCLK: Unrecognized hardware revision level
12. GCLK: Unrecognized hardware revision level

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GCLK board hardware revision level was unrecognized by the system.
The following effects occur as a result of an unrecognized hardware revision level.

• The GCLK is not able to synchronize and is placed in the set frequency mode.
• More frequent recalibrations is necessary.
• All GCLK Sync feature commands execute, but the GCLK is not placed in the closed loop
mode.
Possible causes
The revision level of the GCLK hardware is not recognized.
Procedure
Procedure 21-10 Unrecognized hardware revision level
1 Check the hardware version number (HVN).

2 Call a Motorola representative.
68P02901W26-S 21-27
Nov 2007
14. GCLK: Phase lock failure Chapter 21: GCLK Alarms
14. GCLK: Phase lock failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A GCLK has lost phase lock and repeated attempts to regain phase lock have failed.
InCell
Hardware timers on the GCLK board are used to determine the length of time for a GCLK
to achieve and maintain phase lock. The length of time for a specific GCLK is dependent on
the hardware revision of the GCLK board.
The GCLK must achieve phase lock within the period specified by the confirmation timer setting.
It must also maintain phase lock for the period specified by the timeout timer setting. The
relevant settings are shown in Table 21-4.
Table 21-4 GCLK timer settings
GCLK hardware revision level Conrmation timer setting Timeout timer setting
1 - 3 10 minutes 6 hours
5 - 9 2 minutes 1 hour
This alarm is generated if the GCLK does not achieve or maintain phase lock within the period
specified by the timer settings.
M-Cell
Hardware timers on the MCU are used to determine the length of time for a GCLK to maintain
phase lock.
InCell
There is no additional information for this alarm at an InCell site.
21-28 68P02901W26-S
Nov 2007
M-Cell
The contents of the Additional information field for an M-Cell site are shown in Table 21-5.

second 00 to 32 or FF Device ID 1 - Identifies the MSI where
the MMS is equipped.
third 0, 1 or FF Device ID 2 - Identifies the specific
MMS on the MSI board.
Ignore any additional bytes displayed in this field.be ignored.
Possible causes

• GCLK hardware failure.
• Clock reference source problem.
• E1 link outside specification.
• GCLK calibration required.
68P02901W26-S 21-29
Nov 2007
Procedure
Procedure 21-11 Phase lock failure
1 Determine if other sites are reporting this alarm.

If other sites are... Then...
reporting this alarm The reference clock signal or the associated E1
link is faulty. Resolve the reference clock signal
or link fault. For link troubleshooting procedures,
refer to Maintenance Information: BSS Field
not reporting this Go to step 2.
alarm
2 The GCLK is faulty or there is an associated link problem.
If the BTS... and... Then...
is InCell there is a redundant Go to step 3.
GCLK
is InCell there is no redundant Go to step 5.
GCLK
M-Cell there is a redundant Go to step 6.
MCU
3 Swap to the redundant GCLK.
If... Then...
the alarm clears Replace the failed GCLK to restore redundancy.
No further action is necessary.
the alarm persists Go to step 4.
4 Send a field representative to the site to check the link. If this is OK,
the representative should recalibrate the GCLK.
If... Then...
the alarm clears No further action is necessary.
the alarm persists Assume that both GCLKs are faulty and replace
them with equipment known to be good.
Continued
21-30 68P02901W26-S
Nov 2007
Procedure 21-11 Phase lock failure (Continued)

5 Check the DAC value.
If the DAC value Then...
is...
moving around The alarm is due to a link problem. Send a field
representative to the site to troubleshoot the E1
link.
stuck at a limit It is trying to lock. Send a field representative
to the site to recalibrate the clock. If this fails
to resolve the problem, the field representative
should troubleshoot the E1 link.
6 Swap to the redundant MCU.
If... Then...
the alarm clears Replace the failed MCU to restore redundancy.
No further action is necessary.
the alarm persists Send a field representative to the site to check
the E1 link.

68P02901W26-S 21-31
Nov 2007
15. GCLK: Watchdog timer expired Chapter 21: GCLK Alarms
15. GCLK: Watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The Synchronization (SYNC) process on the MCU board watchdog timer unexpectedly expired.
This alarm applies only to MCU-based sites.
System action
Possible causes

• The SYNC firmware failed.
• The MCU board failed.
21-32 68P02901W26-S
Nov 2007
Procedure
Procedure 21-12 Watchdog timer expired

then go to step 2.
2 Reset the site.
3 Determine if this alarm recurs after the reset.
recurs Send a field representative to the
site to replace the MCU reporting
the alarm.
does not recur The alarm condition no longer
not required.

68P02901W26-S 21-33
Nov 2007
16. GCLK: Clock output failure Chapter 21: GCLK Alarms
16. GCLK: Clock output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GCLK Synchronization (SYNC) hardware is not generating the 16.384 MHz clock signal
in the system.
System action
Possible causes

• The SYNC firmware is faulty.
21-34 68P02901W26-S
Nov 2007
Procedure
Procedure 21-13 Clock output failure

then go to step 2.
2 Reset the site.
the alarm.
not required.

68P02901W26-S 21-35
Nov 2007
17. GCLK: SYNC shutdown request Chapter 21: GCLK Alarms
17. GCLK: SYNC shutdown request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A GCLK Synchronization (SYNC) function has experienced a catastrophic failure causing

a shutdown request to be issued.
System action
Possible causes

• The SYNC firmware is faulty.
21-36 68P02901W26-S
Nov 2007
Procedure

then go to step 2.

2 Reset the site.
the alarm.
not required.

68P02901W26-S 21-37
Nov 2007
18. GCLK: Not operational Chapter 21: GCLK Alarms
18. GCLK: Not operational

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MCU Synchronization (SYNC) function did not complete the required initialization that
prevents the GCLK from becoming operational.
System action
Possible causes

• The operational SYNC firmware is corrupted.
• The SYNC hardware is faulty.
21-38 68P02901W26-S
Nov 2007
Procedure
Procedure 21-15 Not operational

then go to step 2.
2 Reset the site.
the alarm.
not required.

68P02901W26-S 21-39
Nov 2007
19. GCLK: Warm up failure Chapter 21: GCLK Alarms
19. GCLK: Warm up failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MCU Synchronization (SYNC) function completed the MCU GCLK initialization. But, the
SYNC function did not indicate that the warm up was completed so that it could begin normal
operation.
Fault Management (FM) expects that SYNC hardware takes less than 30 minutes to complete a
warm up.
An automatic MCU hard reset is continuously performed to try to bring the MCU GCLK module
in service.
Possible causes

• The operational SYNC hardware is faulty.
• The operational SYNC firmware is corrupted. The boot portion of the firmware is probably
not corrupted.
• The SYNC processor failed.
21-40 68P02901W26-S
Nov 2007
Procedure
Procedure 21-16 Warm up failure

then go to step 2.
2 Reset the site.
the alarm.
not required.

68P02901W26-S 21-41
Nov 2007
20. GCLK: Invalid mode Chapter 21: GCLK Alarms
20. GCLK: Invalid mode

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MCU Synchronization (SYNC) function completed hardware or firmware initialization and
the warm up of the MCU GCLK. However, the SYNC function is reporting that the MCU GCLK
is in an invalid operational mode. As a result, the MCU GCLK may not be able to continue
normal operation.
An automatic MCU hard reset is continuously attempted to try to bring the MCU GCLK module
in service.
Invalid operational modes
One of the following two invalid operational modes may be reported:

• The MCU GCLK is currently in a warm up mode after it has already completed the warm up.
• The standby MCU GCLK is in the fast tune state when a standby device should never
reach that mode.
21-42 68P02901W26-S
Nov 2007
Possible causes

• The operational SYNC firmware is corrupted. The boot portion of the firmware is probably
not corrupted.
• The SYNC processor failed.
Procedure
Procedure 21-17 Invalid mode

then go to step 2.
2 Reset the site.
the alarm.
not required.

68P02901W26-S 21-43
Nov 2007
21. GCLK: Calibration in progress Chapter 21: GCLK Alarms
21. GCLK: Calibration in progress

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The OMC-R operator requested calibration of the GCLK Synchronization (SYNC) hardware.
The MCU is reset after the GCLK SYNC calibration has been completed.
Possible causes
The OMC-R operator request the calibration.
Procedure
Procedure 21-18 Calibration in progress

2 The MCU is automatically reset by the system after the calibration is
completed.
21-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. GCLK: Firmware initiated calibration
22. GCLK: Firmware initiated calibration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The OMC-R operator requested a firmware-directed calibration of GCLK Synchronization

(SYNC) hardware.
Possible causes
The OMC-R operator requested the calibration.
Procedure
Procedure 21-19 Firmware initiated calibration

2 The MCU is automatically reset by the system after the calibration has been
completed.
68P02901W26-S 21-45
Nov 2007
24. GCLK: Bad clock source or OCXO (oscillator) replacement required Chapter 21: GCLK Alarms
24. GCLK: Bad clock source or OCXO (oscillator)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GCLK Synchronization (SYNC) firmware has detected that one of the following two possible
fault conditions has occurred:
• The GCLK SYNC Oven-Controlled Crystal Oscillator (OCXO) has reached a synchronization
limit which may adversely affect system performance.
• The clock reference source signal is out of specification.
OCXO ageing
If this alarm was generated because of OCXO ageing, the OCXO may no longer be able to
produce a valid system clock signal.
21-46 68P02901W26-S
Nov 2007
Possible causes

• The OCXO board may have aged to the point where it may not longer be able to produce a
valid system clock signal.
• An incoming clock signal is out of specification.
• Sync firmware failed.
Procedure
Procedure 21-20 Bad clock source or OCXO (oscillator) replacement required
1 Determine if any link alarms occurred at the same time that phase
lock was lost.
the link fault.
did not occur at the same time Go to step 2.
3 Determine if the Long-Term-Average Values are Unstable (GCLK 11)
alarm was reported for the GCLK.
was reported Send a field representative to the
site to recalibrate the GCLK.
was not reported Send a field representative to the
then go to step 5.
Continued
68P02901W26-S 21-47
Nov 2007
Procedure 21-20 Bad clock source or OCXO (oscillator) replacement required

(Continued)
5 Reset the site.
the alarm.
not required.

21-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. GCLK: GCLK calibration request
26. GCLK: GCLK calibration request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
InCell
Of the values used to calculate the LTA, 25% or more exceed the alarm range specified by
the lta_alarm_range database parameter.
Calibration values depend on the hardware revision of the GCLK board at the site. Table 21-6
provides both the low and high calibration limits as required by the specific GCLK hardware
revision levels.
Table 21-6 LTA calibration limits
GCLK hardware revision level Low LTA calibration limit High LTA calibration limit
1 - 3 38h (=56 dec) E9h (=233 dec)
5 - 7 38h (=56 dec) E9h (=233 dec)
8 38h (=56 dec) E9h (=233 dec)
9 1Ah (=26 dec) E9h (=233 dec)
M-Cell
The MCU GCLK has been unable to calculate an LTA value during 24 hour period within the last
year. This alarm may also be generated for an MCU that is being powered up for the first time
and has not been calibrated; and therefore, is unable to have the LTA calculated.
Phase locking must be enabled to calculate the LTA value.
68P02901W26-S 21-49
Nov 2007
Possible causes

• During normal operation and phase locking is not enabled, the GCLK has reached a point
where calibration is needed (InCell only).
• During normal operation and phase locking is not enabled, the calibration timer has
expired (M-Cell only).
• The clock reference signal has failed or is out of specification. This may be due to a bad E1
link.
• The MCU was powered up for the first time and may currently not be calibrated. In this
situation, the alarm will be displayed until it calculates a long-term average after 24 hours.
Procedure
Procedure 21-21 GCLK calibration request

2 With Phase Lock enabled, determine if the Long Term Average
Values are Unstable (GCLK 11) alarm was reported for the GCLK.
was reported Send a field representative to the
site to check the E1 link.
was not reported Send a field representative to
the site to measure the GCLK
frequency when locked. If this is
within 50 ppb, then recalibrate
the GCLK. If the frequency is not
within 50 ppb, check the E1 link.
Continued
21-50 68P02901W26-S
Nov 2007
Procedure 21-21 GCLK calibration request (Continued)

3 Determine if the MCU is being powered up for the first time or was
recalibrated during the previous 24 hour period.
If the MCU is... Then...
being powered up for the first Wait 24 hours after the MCU was
time powered up or recalibrated. If the
alarm is not cleared after 24 hours,
send a field representative to the
site to check the E1 link.
not being powered up for the Send a field representative to the
first time or was recalibrated site to recalibrate the GCLK.
during the previous 24 hour
period and phase lock is not
enabled

68P02901W26-S 21-51
Nov 2007
232. GCLK: Processor bus communication failure Chapter 21: GCLK Alarms
232. GCLK: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A GCLK board device has lost the ability to communicate to the GCLK through the MCAP bus.
Possible causes

• The GCLK board was physically removed from the shelf.
• The part of the GCLK that supports the MCAP bus access failed.
Procedure
Determine the current operational and administrative states of the GCLK.

busy and unlocked The alarm condition has ceased.
Further fault isolation is
not required. If this alarm
recurs frequently, send a field
replace the GCLK.
not busy and unlocked Send a field representative to the
21-52 68P02901W26-S
Nov 2007

68P02901W26-S 21-53
Nov 2007
21-54 68P02901W26-S
Nov 2007
Chapter
22
GDS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GDS alarms and includes the following alarm procedures:
• 0. GDS: All channels Out of Sync on page 22-2.
• {26740} 1. GDS: IP address mismatch on page 22-3.
• {26740} 2. GDS: Protocol failure on page 22-4.
68P02901W26-S 22-1
Nov 2007
0. GDS: All channels Out of Sync Chapter 22: GDS Alarms
0. GDS: All channels Out of Sync

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
All packet data channels on this GDS are Out of Service (out of synchronization).
The system tries to recover from this alarm condition by resetting the MSI board carrying
this GDS.
Possible causes
NIB has failed. A connection problem exists between PCU and radio at the BTS.
Procedure
Procedure 22-1 All channels Out of Sync
1 Reset the MSI and clear the problem.

2 If problem is not cleared, then end-to-end connections between the PCU and
the radio at the BTS needs to be verified.
22-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GDS: IP address mismatch
1. GDS: IP address mismatch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
The GDS over the Ethernet is disabled for the IP address mismatch.
The additional alarm codes include the mismatch IP address extracted from Alive ACK.
Variables are based on the size of the ASCII string (for example: 10.15.255.2).
Possible causes
The PSI’s IP address changes its PXP pair on PCU which, is not notified or miswired with PSI-PXP.
The PCU (PXP) receives unexpected BSC (PSI) Alive REQ message.
Procedure
Procedure 22-2 IP address mismatch
The operator checks and modifies the IP address, or reconfigures the PCU to
BSC Ethernet connection.
68P02901W26-S 22-3
Nov 2007
2. GDS: Protocol failure Chapter 22: GDS Alarms
2. GDS: Protocol failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm provides an indication that the GDS over Ethernet is OOS on the PSI/DPROC (PXP).
Possible causes
• The Alive protocol on PSI/DPROC (PXP) fails because of an unexpected problem which
causes GDS is OOS.
• The alarm is not raised on the parent devices of the GDS.
22-4 68P02901W26-S
Nov 2007
Procedure
Use the following procedures to resolve the alarm.
Procedure 22-3 GDS: Protocol failure for PSI
If... Then...
the available GDSs connecting to the same wait for at least 10 mins before taking any
PCU/BSC are also OOS, action as PCU/BSC is resetting.
the alarm does not clear after PCU/BSC is check the status of the corresponding
back in-service PSI/DPROC(PXP) for this GDS.
the PSI/DPROC(PXP) is OOS get that in-service by performing an INS
command on the device.
the PSI/DPROC(PXP) is INSed and the check the status of the corresponding
alarm does not clear ETH for this GDS.
the ETH is OOS get it in service.
the ETH is INSed and the alarm does not check the status of the GDS on the peer
clear entity.
68P02901W26-S 22-5
Nov 2007
Procedure Chapter 22: GDS Alarms
22-6 68P02901W26-S
Nov 2007
Chapter
23
GPROC Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GCLK alarms and includes the following alarm procedures:
• 1. GPROC: EEPROM flash failure - No valid bootstrap code object present on page 23-4.
• 8. GPROC: EEPROM flash object failure on page 23-6.
• 17. GPROC: EEPROM flash programming failure on page 23-8.
• 19. GPROC: RSL links congestion on page 23-10.
• 20. GPROC: LAPD controller failure on page 23-11.
• 21. GPROC: EEPROM flash programming failure on page 23-12.
• 22. GPROC: SWFM indication on page 23-14.
• 23. GPROC: SYNC lost phase lock to master GCLK on page 23-15.
• 24. GPROC: Bad clock source or SYNC OCXO(oscillator) replacement required on page
23-16.
• 25. GPROC: SYNC warm up failure on page 23-17.
• 26. GPROC: SYNC calibration request on page 23-18.
• 27. GPROC: SYNC shutdown request on page 23-19.
• 28. GPROC: SYNC clock output failure on page 23-20.
• 29. GPROC: SYNC watchdog timer expired on page 23-21.
• 30. GPROC: Clock A signal loss on page 23-22.
• 31. GPROC: Clock B signal loss on page 23-24.
• 32. GPROC: TDM interface failure - Assigned timeslot counter underflow on page 23-26.
• 33. GPROC: TDM interface failure - Assigned timeslot counter overflow on page 23-28.
• 34. GPROC: TDM interface failure - TDM parity error on page 23-30.
• 35. GPROC: LAN connection failure on page 23-32.
• 39. GPROC: Software failure on page 23-34.
• 40. GPROC: Spurious interrupt on page 23-36.
• 42. GPROC: Site reset occurred due to front panel reset on page 23-38.
68P02901W26-S 23-1
Nov 2007
Procedure Chapter 23: GPROC Alarms
• 43. GPROC: SYNC not operational on page 23-39.
• 44. GPROC: Firmware initiated SYNC calibration on page 23-40.
• 45. GPROC: SYNC phase lock failure on page 23-41.
• 46. GPROC: SYNC invalid mode on page 23-42.
• 47. GPROC: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected

on page 23-43.
• 48. GPROC: Memory location is corrupt. Replace GPROC board on page 23-45.
• 50. GPROC: EEPROM SW flash programming failure on page 23-46.
• 51. GPROC: EEPROM SW flash programming failure on page 23-47.
• 231. GPROC: TDM interface configuration failure on page 23-48.
• 232. GPROC: Processor bus communication failure on page 23-50.
• 239. GPROC: Process safe test audit failure on page 23-51.
• 254. GPROC: Device failure on page 23-53.
23-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to GPROC alarms
Introduction to GPROC alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GPROC alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Generic
Processor (GPROC) device.
GPROC devices are grouped into one of two categories based on functionally:
• Hard device - the functionality of a hard GPROC device is predefined and static. These
devices include the Base Site Processor (BSP), Base Transceiver Processor (BTP), Digital
Host Processor (DHP) and Code Storage Facility Processor (CSFP). Each of these devices
is documented separately.
• Soft device - the functionality of a soft GPROC device is dynamically assigned as part of a
N+M redundancy scheme. In this scheme, M is the number of available soft devices in a
pool of devices. N is the number of hard devices whose function may be assumed by
one of the pooled devices.
For example, if a CSFP device fails and a pool GPROC device is available, the pooled device
assumes the CSFP functionality.
Only soft GPROC device alarms are described in this chapter.
FRUs
A GPROC device may be equipped on one of the FRUs shown in Table 23-1.
Table 23-1 GPROC FRUs
FRU Description
GPROC InCell GPROC board
GPROC2 InCell GPROC2 board
GPROC3 InCell GPROC3 board
MCU Main Control Unit
MCUF Main Control Unit
MCUm Main Control Unit
ARENA (MCU) Main Control Unit
ARENA MAC (MCU) Main Control Unit
HORIZONMIC2 (MCU) Main Control Unit
HORIZONCOM2 (MCU) Main Control Unit
68P02901W26-S 23-3
Nov 2007
1. GPROC: EEPROM ash failure - No valid bootstrap code object present Chapter 23: GPROC Alarms
1. GPROC: EEPROM ash failure - No valid bootstrap

code object present
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The Initialization Process (IP) determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt.
Possible causes

23-4 68P02901W26-S
Nov 2007
Procedure
Procedure 23-1 EEPROM ash failure - No valid bootstrap code object present

to clear the alarm.


68P02901W26-S 23-5
Nov 2007
8. GPROC: EEPROM ash object failure Chapter 23: GPROC Alarms
8. GPROC: EEPROM ash object failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
Possible causes

23-6 68P02901W26-S
Nov 2007
Procedure

to clear the alarm.


68P02901W26-S 23-7
Nov 2007
17. GPROC: EEPROM ash programming failure Chapter 23: GPROC Alarms
17. GPROC: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem unless the GPROC is being reset, at which time
Possible causes
23-8 68P02901W26-S
Nov 2007
Procedure

68P02901W26-S 23-9
Nov 2007
19. GPROC: RSL links congestion Chapter 23: GPROC Alarms
19. GPROC: RSL links congestion

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The flow of messages exceeds the transmissibility of RSL links. Links congestion was detected
on one or more RSLs on this GPROC.
Some paging messages may be discarded when this alarm is present. Hence, the
associated services are not provided. For example, some new calls may not be
established. Select retry or wait a while to avoid peak usage of the system.
Possible causes
• Huge number of paging messages coming from the MSC.
• The transmissibility of RSL is too low.
Procedure
Procedure 23-4 RSL links congestion
1 Determine whether or not it is necessary to expand network capability.

Isolate occurrences of the alarm to specific BTS Sites or LCF processors to
determine if expansion or re-configuration is required.
2 Take appropriate action and clear the alarm.
23-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. GPROC: LAPD controller failure
20. GPROC: LAPD controller failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAPD controller on the GPROC has encountered a fatal error.
Two bytes are displayed. Ignore the first byte; the second byte has a value of 1 or 2. The second
Table 23-2 GPROC: LAPD controller failure
Value Description
Possible causes
• The SRAM of the GPROC is faulty.
Procedure
Perform the following step if the alarm re-occurs.
If the alarm re-occurs, replace the GPROC.
68P02901W26-S 23-11
Nov 2007
21. GPROC: EEPROM ash programming failure Chapter 23: GPROC Alarms
21. GPROC: EEPROM ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
This fault condition is not a problem until the GPROC is reset, at which time the
GPROC is rendered useless.
Possible causes
{28337} The flash EEPROM device is faulty or the user has a GPROC3/ GPROC3-2 board.
Procedure
23-12 68P02901W26-S
Nov 2007

68P02901W26-S 23-13
Nov 2007
22. GPROC: SWFM indication Chapter 23: GPROC Alarms
22. GPROC: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The system has detected a software processing error (SWFM) for a GPROC.
Possible causes
Procedure
Clear the alarm.
23-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. GPROC: SYNC lost phase lock to master GCLK
23. GPROC: SYNC lost phase lock to master GCLK

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that having been in phase locked mode, the SYNC circuit has lost phase
lock to the master.
Possible causes
The following are the Possible causes for the alarm:
• Faulty HDLC link.
Procedure
Procedure 23-8 SYNC lost phase lock to master GCLK
1 Report that the fault requires HDLC/SYNC investigation.

2 Take appropriate action and clear the alarm.
68P02901W26-S 23-15
Nov 2007
24. GPROC: Bad clock source or SYNC OCXO(oscillator) replacement required Chapter 23: GPROC Alarms
24. GPROC: Bad clock source or SYNC OCXO(oscillator)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by
replacing the FRU itself.
Possible causes
• SYNC malfunctioning.
Procedure
Procedure 23-9 GPROC: Bad clock source or SYNC OCXO(oscillator) replacement

required
1 Report that the SYNC circuit requires investigation.

2 FRU replacement required.
3 If FRU is not replaced, this could lead to other SYNC alarms being generated
which can result in the reset of the FRU.
23-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. GPROC: SYNC warm up failure
25. GPROC: SYNC warm up failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that the SYNC circuit has not warmed up to the required operating
temperature within the specified warm-up time.
Possible causes
Procedure
Procedure 23-10 SYNC warm up failure
Report that the SYNC circuit (hence FRU) requires servicing.
68P02901W26-S 23-17
Nov 2007
26. GPROC: SYNC calibration request Chapter 23: GPROC Alarms
26. GPROC: SYNC calibration request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that the SYNC has requested calibration.
Possible causes
Procedure
Procedure 23-11 SYNC calibration request
Report that the SYNC circuit requires investigation (clocking usually drifts
with time).
23-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. GPROC: SYNC shutdown request
27. GPROC: SYNC shutdown request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the SYNC circuit has requested shutdown.
Possible causes
Procedure
Report that the SYNC circuit requires investigation.
68P02901W26-S 23-19
Nov 2007
28. GPROC: SYNC clock output failure Chapter 23: GPROC Alarms
28. GPROC: SYNC clock output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the SYNC circuit output clock has failed.
Possible causes
Procedure
Procedure 23-13 SYNC clock output failure
23-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. GPROC: SYNC watchdog timer expired
29. GPROC: SYNC watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the SYNC circuit generated a watchdog timer expire indication.
Possible causes
Procedure
Procedure 23-14 SYNC watchdog timer expired
Report that the SYNC circuitry requires investigation.
68P02901W26-S 23-21
Nov 2007
30. GPROC: Clock A signal loss Chapter 23: GPROC Alarms
30. GPROC: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GPROC detected a TDM Clock A failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the GPROC switches to the
fails and may cause the site to go OOS.
Possible causes

Procedure
23-22 68P02901W26-S
Nov 2007
1 Determine the current administrative and operational state of the

site.
site to replace the Clock A GCLK.
devices in the same cage as Clock A:

are present only for the GPROC Replace the GPROC.
the MSI board.

68P02901W26-S 23-23
Nov 2007
31. GPROC: Clock B signal loss Chapter 23: GPROC Alarms
31. GPROC: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GPROC detected a TDM Clock B failure.
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the GPROC switches to the
fails and may cause the site to go OOS.
Possible causes

23-24 68P02901W26-S
Nov 2007
Procedure

site to replace the Clock B GCLK.
2 Determine if any of the following alarms were reported by other

are present only for the GPROC Replace the GPROC.
the MSI board.

68P02901W26-S 23-25
Nov 2007
32. GPROC: TDM interface failure - Assigned timeslot counter underow Chapter 23: GPROC Alarms
32. GPROC: TDM interface failure - Assigned timeslot

counter underow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GPROC has determined that the TDM highway is under used. Fewer switch-bound timeslots
Possible causes

• Assigned timeslot counter register failed.
23-26 68P02901W26-S
Nov 2007
Procedure

required.
2 Reset the GPROC.
The site is reset.

3 Determine the state of the GPROC after the reset is completed.
If the GPROC is... Then...
required.

68P02901W26-S 23-27
Nov 2007
33. GPROC: TDM interface failure - Assigned timeslot counter overow Chapter 23: GPROC Alarms
33. GPROC: TDM interface failure - Assigned timeslot

counter overow
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GPROC has determined that the TDM highway is overused. More switch-bound timeslots
Possible causes

23-28 68P02901W26-S
Nov 2007
Procedure

required.
2 Reset the GPROC.
The site is reset.

required.

68P02901W26-S 23-29
Nov 2007
34. GPROC: TDM interface failure - TDM parity error Chapter 23: GPROC Alarms
34. GPROC: TDM interface failure - TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An incorrect parity was detected on the switch bound or outbound TDM highway.
Possible causes

23-30 68P02901W26-S
Nov 2007
Procedure

required.
2 Reset the GPROC.
The site is reset.

required.

68P02901W26-S 23-31
Nov 2007
35. GPROC: LAN connection failure Chapter 23: GPROC Alarms
35. GPROC: LAN connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAN connection between the master GPROC and any other equipped GPROC on the LAN
failed.
System action
The system places the GPROC OOS. If the GPROC is the master GPROC, the site resets.
Possible causes

• The GPROC was reset through software or the front panel on site.
23-32 68P02901W26-S
Nov 2007
Procedure

2 Reset the GPROC.
The site is reset.

required.

68P02901W26-S 23-33
Nov 2007
39. GPROC: Software failure Chapter 23: GPROC Alarms
39. GPROC: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The GPROC experienced a non recoverable SWFM error.
System action
programmers.
Possible causes

• The GPROC software is faulty.
23-34 68P02901W26-S
Nov 2007
Procedure

3 Determine the state of the GPROC.
busy-unlocked The alarm was probably
caused by a software error.

68P02901W26-S 23-35
Nov 2007
40. GPROC: Spurious interrupt Chapter 23: GPROC Alarms
40. GPROC: Spurious interrupt

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The GPROC received and acknowledged an interrupt message but did not receive a response
from the device generating the interrupt.
Possible causes

• The timer on the GPROC monitoring the MCAP bus is faulty causing the wait timer to
expire before receiving the response message.
• One of the MCAP boards is faulty.
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or other
cause.
23-36 68P02901W26-S
Nov 2007
Procedure

reset Go to step 2.
3 Determine the current state of the GPROC.
required.

68P02901W26-S 23-37
Nov 2007
42. GPROC: Site reset occurred due to front panel reset Chapter 23: GPROC Alarms
42. GPROC: Site reset occurred due to front panel reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The front panel reset switch was pressed on the BTP MCU and the site was reset.
Possible causes
The front panel reset switch was pressed.
Procedure
Procedure 23-23 Site reset occurred due to front panel reset
There is no operator action necessary.
23-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 43. GPROC: SYNC not operational
43. GPROC: SYNC not operational

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
After the SYNC circuit begins initializing, a timer is set to wait for the SYNC circuit to become
operational. This alarm indicates that the SYNC circuit is still in the initializing state instead of
the operational state, after the timer expire period.
Possible causes
Procedure
Procedure 23-24 SYNC not operational
68P02901W26-S 23-39
Nov 2007
44. GPROC: Firmware initiated SYNC calibration Chapter 23: GPROC Alarms
44. GPROC: Firmware initiated SYNC calibration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that SYNC calibration was requested by the SYNC firmware MMI.
Possible causes
The operator has requested through the firmware MMI, a calibration of the SYNC circuit.
Procedure
Procedure 23-25 Firmware initiated SYNC calibration
Wait for SYNC calibration completion.
23-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 45. GPROC: SYNC phase lock failure
45. GPROC: SYNC phase lock failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the SYNC circuit has not phase locked to the master within a specified
period of being setup in the slave mode.
Possible causes
• Clock source lost.
• Calibration of SYNC circuit was initiated.
• Noise on HDLC link.
• Faulty HDLC link.
Procedure
Procedure 23-26 SYNC phase lock failure
Report that the fault requires HDLC/SYNC investigation.
68P02901W26-S 23-41
Nov 2007
46. GPROC: SYNC invalid mode Chapter 23: GPROC Alarms
46. GPROC: SYNC invalid mode

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by
replacing the FRU itself.
Possible causes
Procedure
Procedure 23-27 SYNC invalid mode
Report that the SYNC circuit requires investigation. FRU replacement

required.
23-42 68P02901W26-S
Nov 2007
GPROC: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected
47. GPROC: Unexpected board type: GPROC2 or

{28337} GPROC3/GPROC3–2 expected
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
If this occurs in an InCell site, the GPROC board will not come into service. The maximum
number of timeslots a GPROC can use is 16. A GPROC2 or {28337} GPROC3/GPROC3–2 board
can use 8, 16 or 32 timeslots.
Possible causes

board.
Procedure
68P02901W26-S 23-43
Nov 2007
Procedure 23-28 Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2

expected

correct Send a field representative to
to step 2.
2 Reset the GPROC.
The site is reset.

busy-unlocked The fault condition
no longer exists.

23-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48. GPROC: Memory location is corrupt. Replace GPROC board
48. GPROC: Memory location is corrupt. Replace

GPROC board
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
be replaced at an appropriate time.
Possible causes

Procedure

2 Contact the Motorola Local Office and arrange to replace the GPROC3
board at an appropriate time.
68P02901W26-S 23-45
Nov 2007
50. GPROC: EEPROM SW ash programming failure Chapter 23: GPROC Alarms
50. GPROC: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This is a generic flash programming error. A problem has occurred with the operating software.
Possible causes

• The memory could be corrupt.
• A static variable is corrupt.
Procedure
23-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 51. GPROC: EEPROM SW ash programming failure
51. GPROC: EEPROM SW ash programming failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This is a generic flash programming error.
Possible causes
Procedure

2 To resolve the alarm, reset the GPROC3 and continue use until it is possible
68P02901W26-S 23-47
Nov 2007
231. GPROC: TDM interface conguration failure Chapter 23: GPROC Alarms
231. GPROC: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Clearing Type: FMIC
Description
The GPROC cannot be programmed for a designated timeslot on the TBUS.
System action
The system automatically resets the GPROC. If the alarm recurs, the GPROC is placed OOS.
Possible causes

• The GPROC board failed.
• The GPROC device is not programmed to the designated timeslot when swapping the
TDM highways.
23-48 68P02901W26-S
Nov 2007
Procedure
Determine the state of the GPROC.

required.

68P02901W26-S 23-49
Nov 2007
232. GPROC: Processor bus communication failure Chapter 23: GPROC Alarms
232. GPROC: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A GPROC board device has lost the ability to communicate to the peripheral boards through
the MCAP bus.
Possible causes

• The front panel switch was set to disabled without the GPROC first being reset.
• The part of the GPROC that supports the MCAP bus access failed.
Clearing the alarm
Procedure
1 Attempt to bring the GPROC back In Service (INS). If the device is back in
2 Replace the GPROC board.
23-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. GPROC: Process safe test audit failure
239. GPROC: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The GPROC failed a process safe test audit. The process safe test audit verifies the proper
The Additional information field includes nine bytes containing process information, as shown
in Table 23-3. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.

02 Higher priority processes prevented the process that
failed to run.
Possible causes

• A process running on the GPROC failed a safe test audit.
Procedure
68P02901W26-S 23-51
Nov 2007

field.
2 Go to step 2.
2 Perform the safe test audit on the GPROC.
If the GPROC... Then...
3 Reset the GPROC.
The site is reset.

required.

23-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. GPROC: Device failure
254. GPROC: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The GPROC is taken OOS by the GPROC Fault Management System.
System action
The site resets if it is the master GPROC.
Value Denition
(Hex)
01 Hard reset
02 Soft reset
Possible causes
68P02901W26-S 23-53
Nov 2007
Procedure
before performing the steps.
1 Determine the current state of the GPROC.

required.
2 Reset the GPROC.
required.

23-54 68P02901W26-S
Nov 2007
Chapter
24
GSL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GSL alarms and includes the following alarm procedures:
• 0. GSL: Invalid received frames - PM on page 24-3.
• 1. GSL: FRMR frames - PM on page 24-5.
• 2. GSL: Expiration of N2 - PM on page 24-7.
• 10. GSL: Link disconnected on page 24-9.
• 11. GSL: LAPD protocol error on page 24-13.
• 13. GSL: LAPD protocol error threshold exceeded on page 24-15.
• 15. GSL: Too many LAPD protocol errors on page 24-17.
68P02901W26-S 24-1
Nov 2007
Introduction to GSL alarms Chapter 24: GSL Alarms
Introduction to GSL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GSL alarms
Control Unit (PCU) GPRS Signaling Link (GSL) interface.
The GSL carries the signaling link traffic between the BSC and a PCU site. The GSL uses
the Multiple Serial Interface link (MMS: E1 link) hardware as its underlying communication
link medium.
24-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. GSL: Invalid received frames - PM
0. GSL: Invalid received frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This statistic counts the number of invalid frames received on the LAPD link.
For further information, refer to the GSL statistics chapter in the manual, Maintenance
Possible causes
The signaling link between the BSC and the PCU is faulty.
Procedure
Determine if this alarm is persistently reported.

persistently reported Send a field representative to
the site to check the LAPD link
between the BSC and the PCU and
take appropriate action.
68P02901W26-S 24-3
Nov 2007
Procedure Chapter 24: GSL Alarms

24-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GSL: FRMR frames - PM
1. GSL: FRMR frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This statistic counts the number of frames on the LAPD link that were rejected because the
frames were not correctable.
Possible causes
Procedure
68P02901W26-S 24-5
Nov 2007

site to check the LAPD link and

24-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. GSL: Expiration of N2 - PM
2. GSL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
without success.
Possible causes
Procedure

68P02901W26-S 24-7
Nov 2007

24-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. GSL: Link disconnected
10. GSL: Link disconnected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that a GPRS Signaling Link (GSL) between the Packet Control Unit (PCU)
and the BSC has been disconnected.
This alarm may not be raised if the associated MMS fails, depending on the sequence
of events:
• If software determines the MMS link has failed first, an MMS alarm is raised as
the primary alarm and you will not see a GSL 10 alarm.
• If MMS thresholds are configured such that the GSL fails before the MMS
failure is signaled in software, you will first see the GSL 10 alarm, followed by
the MMS alarm.
• If the GSL fails due to a layer 2 issue only (LAPD) and the MMS is OK, you will
see the GSL alarm only. The operator can use the OMC to determine any devices
present on the MMS (including GSLs) by clicking the MMS alarm at the OMC.
Last GSL link disconnected
If this alarm is generated for a GSL link that is the last available link for service, all GSL
communication links go Out Of Service (OOS) and the following alarm is generated:
0. PCU: Last GSL link failed.
When this occurs, the PCU is placed OOS.
If the last GSL remains disconnected for more than 30 minutes, the PCU automatically
resets. Depending on the circumstances, this may clear associated alarms and return
the GSL to service.
68P02901W26-S 24-9
Nov 2007
Additional information eld Chapter 24: GSL Alarms
The Additional information field displays the reason code, followed by the timeslot and
associated MMS ID. For example:
Reason: Normal Disconnect; Timeslot: 1; MMS 500.
Table 24-1 details the Additional information field for this alarm.

first 0A MMS device type.
second 00 to FF
third 00 to FF MMS device identifiers.
fourth 00 to FF
Ignore any additional bytes displayed in this field.
Possible causes

• A normal link disconnect.
• One side of the associated MMS is locked, causing the remote end (not locked) to raise the
Link Disconnected alarm. This may occur when locking any higher level device (MMS,
MSI, GPROC, DPROC).
• LAPD link protocol detected failure to communicate with remote end.
• Link failure affecting GSL timeslots only, for example when timeslot switching equipment
is used or faulty terminating equipment is present. MMS continues in service while the E1
timeslot 0 is good.
• A GSL guard timer expired.
24-10 68P02901W26-S
Nov 2007
Procedure
1 Determine the state of the GSL device.

If the GSL is... Then...
busy and unlocked The fault condition no longer exists. If
this is a recurrence of this alarm, the
E1 link is probably faulty. Send a field
representative to the site to isolate and
correct the link fault.
not busy and unlocked Continue to step 2.
2 Attempt to restore the GSL device to service.
If the GSL... Then...
returns to service The fault condition no longer exists. If
this is a recurrence of this alarm, the
E1 link is probably faulty. Send a field
representative to the site to isolate and
correct the link fault.
3 Determine the state of the MMS device identified in the Additional
information field.
If the MMS is... Then...
busy and unlocked The E1 link is probably faulty.
Send a field representative to the site
to isolate and correct the link fault.
not busy and unlocked Go to step 4.
4 Determine the state of the parent MSI device for the MMS identified
busy and unlocked The MMS device is faulty.
Review the Alarm/Event window
for the MMS alarm and initiate
the appropriate alarm handling
procedures.
not busy and unlocked The MSI device is faulty.
for the MSI alarm and initiate
procedures.
68P02901W26-S 24-11
Nov 2007
Only an experienced operator should attempt to resolve this fault condition.

24-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. GSL: LAPD protocol error
11. GSL: LAPD protocol error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The GSL detected a LAPD protocol error due to a problem on one of the E1 links. Calls may
be lost.

first 01 to 1F MMS timeslot.
second 00 to FF LAPD error code.
third 0A MMS device type.
fourth fifth sixth 00 to FF00 to FF00 to FF MMS device identifiers.
Possible causes
The LAPD Error String in the Additional information field corresponds to a possible cause
for the alarm, as indicated below:
• Link Timeout.
• Sequence Error.
• Frame Rejected.
• Unexpected Response Frame.
• Bad Configuration.
68P02901W26-S 24-13
Nov 2007
• SABM-Extended Received.
• Bad Frame.
• Link SABM-Extended Failure.
• Link Disconnect Failure.
• Link Status Query Failure.
Procedure
Procedure 24-5 LAPD protocol error

a recurrence of this alarm Go to step 2.
not a recurrence of this alarm Clear the alarm.
2 Determine the state of the MMS identified in the Additional
information field.
busy and unlocked Send a field representative to the
not busy and unlocked Review the Alarm/Event window
for an MMS alarm and initiate
procedures.

24-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. GSL: LAPD protocol error threshold exceeded
13. GSL: LAPD protocol error threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one minute period.
System action taken
The system software resets the affected GSL.
Possible causes
A noisy transmission link.
Procedure
Procedure 24-6 LAPD protocol error threshold exceeded
1 Determine the state of the GSL device.

If the GSL is... Then...
busy and unlocked The fault condition no longer exists. If this is a
recurrence of this alarm, the E1 link is probably
faulty. Send a field representative to the site to
isolate and correct the link fault.
not busy and unlocked Continue to step 2.
Continued
68P02901W26-S 24-15
Nov 2007
Procedure 24-6 LAPD protocol error threshold exceeded (Continued)

2 Attempt to restore the GSL device to service.
If the GSL... Then...
returns to service The fault condition no longer exists. If this is a
recurrence of this alarm, the E1 link is probably
faulty. Send a field representative to the site to
3 Determine the state of the MMS device identified in the Additional information
field.
Send a field representative to the site to
4 Determine the state of the parent MSI device for the MMS identified in the
Additional information field.
Review the Alarm/Event window for
the MMS alarm and initiate the appropriate
alarm handling procedures.
Review the Alarm/Event window for
the MSI alarm and initiate the appropriate

24-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. GSL: Too many LAPD protocol errors
15. GSL: Too many LAPD protocol errors

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Too many LAPD protocol errors have been received indicating poor link quality.
There are six bytes. They are Byte 1 – MMS timeslot, Byte 2 – LAPD fault code, Bytes 3-6 –
MMS device ID.
Possible causes
Four or more LAPD Protocol errors were received within 1 second indicating major problems
with the GSL link.
Procedure
Procedure 24-7 GSL: Too many LAPD protocol errors
1 Check report logs for repeated occurrence of this alarm. If alarm occurs
more than expected, monitor the state of MMS related to the GSL and INS
the GSL device. A field representative may need to visit the site to determine
the quality of the link and adjust, correct or replace it as required.
2 Consult Alarm Handling at the OMC customer documentation. Investigate
further the GSL if this keeps happening.
68P02901W26-S 24-17
Nov 2007
24-18 68P02901W26-S
Nov 2007
Chapter
25
IAS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details IAS alarms and includes the following alarm procedures:
• 0. IAS: Unexpected board type on page 25-5.
• 1. IAS: Serial bus connection failure on page 25-7.
• 8. IAS: Power supply unit 0 failure on page 25-10.
• 13 – 15. IAS: Preselector 1A-3A fuse failure on page 25-18.
• 16. IAS: Matrix control main fuse failure on page 25-20.
• 17. IAS: Matrix control redundant fuse failure on page 25-22.
• 18. IAS: Internal combiner main fuse failure on page 25-24.
• 19. IAS: Internal combiner redundant fuse failure on page 25-26.
• 20. IAS: External combiner main fuse failure on page 25-28.
• 21. IAS: External combiner redundant fuse failure on page 25-30.
• 22. IAS: Multicoupler main fuse failure on page 25-32.
• 23. IAS: Multicoupler redundant fuse failure on page 25-34.
• 24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure on page 25-36.
• 27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure on page 25-38.
• 30. IAS: Spare fuse failure on page 25-40.
• 31. IAS: DRAM battery backup fuse failure on page 25-42.
• 32. IAS: IAS +27 V power fuse failure on page 25-44.
• 33 - 34. IAS: Battery backup fuse #1 - #2 failure on page 25-46.
• 35 - 37. IAS: Lower cage fan #0 - #2 failure on page 25-48.
• 38 - 40. IAS: Upper cage fan #3 - #5 failure on page 25-50.
• 41. IAS: Multicoupler failure on page 25-52.
68P02901W26-S 25-1
Nov 2007
Procedure Chapter 25: IAS Alarms
• 46. IAS: Converter failure on page 25-54.
• 47. IAS: Converter over temperature on page 25-56.
• 48 - 50. IAS: Preselector 1B-3B fuse failure on page 25-59.
• 51. IAS: Duplexer voltage error on page 25-61.
• 59. IAS: Battery backup output failure on page 25-63.
• 60. IAS: Battery backup input failure on page 25-65.
• 61. IAS: RCU #5 circuit breaker failure on page 25-67.
• 62. IAS: DPSM 1 failure on page 25-69.
• 63. IAS: DPSM 0 failure on page 25-71.
• 64 - 65. IAS: Fan power converter 1-2 failure on page 25-73.
• 66 - 70. IAS: RCU #0 - #4 circuit breaker failure on page 25-75.
• 71 - 74. IAS: Converter #1 - #4 failure on page 25-77.
• 75. IAS: IAS +27 V DAB power fuse failure on page 25-79.
• 80. IAS: Power supply unit - Input failure on page 25-81.
• 81. IAS: Power supply unit - Output failure on page 25-83.
• 82. IAS: BTS cabinet over temperature on page 25-85.
• 83. IAS: Low voltage disconnect imminent on page 25-87.
• 84. IAS: Air conditioning unit failure on page 25-89.
• 85. IAS: Heat management system unit failure on page 25-91.
• 86. IAS: Cabinet fan failure on page 25-93.
• 87. IAS: Ancillary cabinet over temperature on page 25-95.
• 88 - 90. IAS: Voltage standing wave ratio sector 1-3 failure on page 25-97.
• 91. IAS: Voltage standing wave ratio performance low on page 25-99.
• 92. IAS: Smoke alarm on page 25-101.
• 93. IAS: Door open on page 25-103.
• 94. IAS: No connection to alarms board - Connection broken on page 25-105.
• 95. IAS: Low noise amplifier fuse failure on page 25-107.
• 96. IAS: No redundant connection to alarms board - Connection broken on page 25-109.
• 97. IAS: No connection to alarm board - Radio OOS on page 25-111.
• 98. IAS: No redundant connection to alarms board - Radio OOS on page 25-113.
25-2 68P02901W26-S
Nov 2007
• 99. IAS: No connection to alarm board - Alarm board removed on page 25-115.
• 100. IAS: Cabinet protection system failure on page 25-117.
• 101. IAS: Power supply temperature high on page 25-119.
• 102. IAS: Mains ac supply failure on page 25-121.
• 103. IAS: Fan tray 0 failure on page 25-123.
• 106. IAS: Rectifier failure on page 25-129.
• 107. IAS: Battery box temperature high on page 25-131.
• 108. IAS: Alarm board failed on page 25-133.
• 109. IAS: Auxiliary alarm 1 on page 25-135.
• 110. IAS: Urgent critical alarm on page 25-136.
• 111. IAS: Cabinet protection board fuse failure on page 25-137.
• 112 - 113. IAS: Heat management system unit failure 1 and 2 on page 25-139.
• 114 - 115. IAS: Mains ac supply failure 1 and 2 on page 25-141.
• 116 - 117. IAS: Rectifier failure 1 and 2 on page 25-143.
68P02901W26-S 25-3
Nov 2007
Introduction to IAS alarms Chapter 25: IAS Alarms
Introduction to IAS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
IAS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Internal Alarm
System (IAS). These alarms are generated by the IAS in the BTS, RXCDR and BSC equipment.
The interface hardware for this system is provided by the power distribution and alarm system.
The IAS is responsible for monitoring all cabinet alarms at a BSS.
25-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. IAS: Unexpected board type
0. IAS: Unexpected board type

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
The system detected an unexpected IAS board type.
Possible causes

• The IAS board is faulty.
• The board is improperly fitted.
• The software needs updating to recognize the new board ID.
Procedure
68P02901W26-S 25-5
Nov 2007

25-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. IAS: Serial bus connection failure
1. IAS: Serial bus connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The physical connection between the IAS board and the SBUS failed.
Possible causes

• The cage(s) within a cabinet are not correctly configured in the database.
• The IAS alarms board is improperly installed.
• The IAS alarms board is faulty.
• The polling processor board is faulty.
Procedure
1 Review the alarm report to determine cabinet from which the alarm
is reported.
2 In a TTY window, use the disp_equipment <site> cage <cage_id>
command to determine the current database IAS board-to-cage
configuration for a cabinet.
Continued
68P02901W26-S 25-7
Nov 2007
Procedure 25-2 Serial bus connection failure (Continued)

3 Cross-check the output from the command above to determine
which cage(s) display IAS connected: YES.
• If there is only one cage in the cabinet, go to step 6.
• If there are two cages, refer to the following table.

If... Then...
IAS connected: YES is displayed The database is probably not
for both cages configured correctly. The
upper cage must be set to NO.
Go to step 4.
IAS connected: YES is displayed The database is probably not
for one cage and IAS connected: configured correctly. It is
NO is displayed for the other possible that the cages are
cage equipped with the wrong settings.
Go to step 4.
4 IAS alarms board connection settings
The upper cage in a cabinet must be set to IAS
connected: NO and the lower cage which is connected to the IAS
alarms board, must be set to YES. It is not possible to determine
which is the upper cage and which is the lower cage from the
OMC-R. It is only possible to determine the cage number assigned to
a cage by checking the cage LANX card switch setting onsite. The
switch setting shown on the lower cage LANX card displays the cage
number. Ensure it is set to IAS connected: YES. Ensure the setting
for the upper cage residing in the same cabinet is set to NO.
5 If it is suspected that the wrong cage is set to NO, change the setting
to YES as follows:
• Modify the database using the modify_value<site>

ias_connected yes cage <cage_id> command.
• If the alarm did not clear, change the setting back to NO.
(There could be a hardware problem rather than an incorrect
setting in the database).
• Go to step 6.
6 If the alarm is still active, send a field representative to the site
to check the IAS alarm board and SBUS connections and cabling
between the IAS board and the SBUS.
Refer the manual, Technical Description: BSS Command

Reference (68P02901W23) for information regarding
MMI commands. There are restrictions for executing the
referenced modify_value MMI commands.
25-8 68P02901W26-S
Nov 2007

68P02901W26-S 25-9
Nov 2007
8. IAS: Power supply unit 0 failure Chapter 25: IAS Alarms
8. IAS: Power supply unit 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A failure of Power Supply Unit 0 has been detected due to one of the following:
• PSU input failure
• PSU output failure
• PSU over temperature
• PSU fan failure
• PSU over voltage
This alarm can be raised only on a Horizon II macro or extension cabinet.
The following additional fields are displayed:

• Firmware Source Fault Zone
• Firmware Detector Fault Zone
• Failure type
Possible causes

• Input voltage is out of range.
• Environmental temperature is too high.
25-10 68P02901W26-S
Nov 2007
• Input voltage is lost.
• Output supply cable is faulty.
• A power supply fan may have failed.
• An over voltage condition is detected on the PSU.
Procedure
Procedure 25-3 Power supply unit 0 failure
1 Review the alarm report and event logs to determine the cause of this alarm.
2 Determine whether the PSU failure is related to other more serious fault
conditions. Check the alarm window for other failures at the site with the
PSU power failure. If other failures exist for the site, prioritize the faults
and refer to the relevant section of this manual for the alarm descriptions
and fault resolution procedures.
3 Send a field representative to the site to determine if the input power source
(equipment and/or cables) are faulty or the PSU equipment is faulty. Any
equipment, that is faulty should be replaced.
This fault condition may be service-affecting if there is no PSU

redundancy at the site.

68P02901W26-S 25-11
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
• PSU fan failure
This alarm can be raised only on a Horizon II macro or extension cabinet.

• Failure type
Possible causes

25-12 68P02901W26-S
Nov 2007
Procedure
faulty equipment should be replaced.


68P02901W26-S 25-13
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
• PSU fan failure
This alarm can be raised only on a Horizon II macro or an extension cabinet.

• Failure type
Possible causes

25-14 68P02901W26-S
Nov 2007
Procedure
faulty equipment should be replaced.


68P02901W26-S 25-15
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
• PSU fan failure
This alarm can be raised only on a Horizon II macro or an extension cabinet.

• Firmware source fault zone
• Firmware detector fault zone
• Failure type
Possible causes

25-16 68P02901W26-S
Nov 2007
Procedure
equipment, that is faulty should be replaced.


68P02901W26-S 25-17
Nov 2007
13 – 15. IAS: Preselector 1A-3A fuse failure Chapter 25: IAS Alarms
13 – 15. IAS: Preselector 1A-3A fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the +27 V preselector fuses (1A, 2A or 3A) on an alarm board failed.
The following are the alarm boards to which this fuse failure applies:
• The Power Distribution Unit (PDU) consisting of the Alarm Interface Board (AIB) and the
Power Distribution Board (PDB).
• Power Alarm Board (PAB).
• Distribution Alarm Board (DAB).
Standard diversity and non-diversity
If standard diversity is used and the preselector is OOS, the receiver sensitivity is reduced
when this alarm is present.
If non-diversity is used and the preselector is OOS, then no receive signal is present at the
related transceiver unit.
Possible causes
The preselector fuse (1A, 2A or 3A) is faulty or blown.
25-18 68P02901W26-S
Nov 2007
Procedure
Procedure 25-7 Preselector 1A-3A fuse failure
1 Send a field representative to the site to replace the bad fuse.

2 Check the alarm boards, board installation, fuse connections and cabling.

68P02901W26-S 25-19
Nov 2007
16. IAS: Matrix control main fuse failure Chapter 25: IAS Alarms
16. IAS: Matrix control main fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V matrix control main power fuse on an alarm board failed.
Possible causes
The matrix control main power fuse is faulty or blown.
Procedure
Procedure 25-8 Matrix control main fuse failure

25-20 68P02901W26-S
Nov 2007

68P02901W26-S 25-21
Nov 2007
17. IAS: Matrix control redundant fuse failure Chapter 25: IAS Alarms
17. IAS: Matrix control redundant fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V matrix control redundant power supply fuse on an alarm board failed.
Possible causes
The matrix control redundant fuse is faulty or blown.
Procedure
Procedure 25-9 Matrix control redundant fuse failure

25-22 68P02901W26-S
Nov 2007

68P02901W26-S 25-23
Nov 2007
18. IAS: Internal combiner main fuse failure Chapter 25: IAS Alarms
18. IAS: Internal combiner main fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V internal combiner main power fuse on an alarm board failed.
Possible causes
The internal RTC main power fuse is faulty or blown.
25-24 68P02901W26-S
Nov 2007
Procedure
Procedure 25-10 Internal combiner main fuse failure


68P02901W26-S 25-25
Nov 2007
19. IAS: Internal combiner redundant fuse failure Chapter 25: IAS Alarms
19. IAS: Internal combiner redundant fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V internal combiner redundant power fuse on an alarm board failed.
Possible causes
The internal RTC redundant power fuse blown is faulty or blown.
Procedure
Procedure 25-11 Internal combiner redundant fuse failure

25-26 68P02901W26-S
Nov 2007

68P02901W26-S 25-27
Nov 2007
20. IAS: External combiner main fuse failure Chapter 25: IAS Alarms
20. IAS: External combiner main fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V external combiner main power fuse on an alarm board failed.
Possible causes
The external RTC main power fuse is faulty or blown.
Procedure
Procedure 25-12 External combiner main fuse failure

25-28 68P02901W26-S
Nov 2007

68P02901W26-S 25-29
Nov 2007
21. IAS: External combiner redundant fuse failure Chapter 25: IAS Alarms
21. IAS: External combiner redundant fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V redundant combiner power fuse on an alarm board failed.
Possible causes
The external RTC redundant power fuse blown is faulty or blown.
Procedure
Procedure 25-13 External combiner redundant fuse failure

25-30 68P02901W26-S
Nov 2007

68P02901W26-S 25-31
Nov 2007
22. IAS: Multicoupler main fuse failure Chapter 25: IAS Alarms
22. IAS: Multicoupler main fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V multicoupler main power fuse on an alarm board failed.
Possible causes
The multicoupler main power fuse is faulty or blown.
Procedure
Procedure 25-14 Multicoupler main fuse failure

25-32 68P02901W26-S
Nov 2007

68P02901W26-S 25-33
Nov 2007
23. IAS: Multicoupler redundant fuse failure Chapter 25: IAS Alarms
23. IAS: Multicoupler redundant fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V multicoupler redundant power fuse on an alarm board failed.
Possible causes
The multicoupler redundant fuse is faulty or blown.
Procedure
Procedure 25-15 Multicoupler redundant fuse failure

25-34 68P02901W26-S
Nov 2007

68P02901W26-S 25-35
Nov 2007
24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure Chapter 25: IAS Alarms
24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the +27 V BCU lower cage fan power fuses (#0, #1 or #2) on an alarm board failed.
Possible causes
The BCU lower cage fan fuse is faulty or blown.
Procedure
Procedure 25-16 BCU lower cage fan #0 - #2 fuse failure

25-36 68P02901W26-S
Nov 2007

68P02901W26-S 25-37
Nov 2007
27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure Chapter 25: IAS Alarms
27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Base Station Control Unit (BCU) power fuse, on an alarm board, to
a fan in the (BCU) upper cage has failed. The fuse on the board is connected to the +27 V power
supply which goes to (and is connected to) the fan.
Possible causes
The BCU upper cage fan fuse is faulty or blown.
Procedure
Procedure 25-17 BCU upper cage fan #3 - #5 fuse failure

25-38 68P02901W26-S
Nov 2007

68P02901W26-S 25-39
Nov 2007
30. IAS: Spare fuse failure Chapter 25: IAS Alarms
30. IAS: Spare fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V power supply spare fuse on an alarm board failed.
Possible causes
The spare fuse is faulty or blown.
Procedure
Procedure 25-18 Spare fuse failure

25-40 68P02901W26-S
Nov 2007

68P02901W26-S 25-41
Nov 2007
31. IAS: DRAM battery backup fuse failure Chapter 25: IAS Alarms
31. IAS: DRAM battery backup fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V DRAM battery backup power fuse on an alarm board failed.
Possible causes

• The battery backup fuse is faulty or blown.
• The battery backup power supply is not connected causing the failure.
Procedure
Procedure 25-19 DRAM battery backup fuse failure

2 Check if the battery backup is connected.
25-42 68P02901W26-S
Nov 2007

68P02901W26-S 25-43
Nov 2007
32. IAS: IAS +27 V power fuse failure Chapter 25: IAS Alarms
32. IAS: IAS +27 V power fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The +27 V power supply fuse for the IAS alarm boards failed.
Possible causes
The main +27 V dc power fuse is faulty or blown causing the failure.
Procedure
Procedure 25-20 IAS +27 V power fuse failure

2 Check the alarm boards, board installation, (fuse) connections and cabling.
25-44 68P02901W26-S
Nov 2007

68P02901W26-S 25-45
Nov 2007
33 - 34. IAS: Battery backup fuse #1 - #2 failure Chapter 25: IAS Alarms
33 - 34. IAS: Battery backup fuse #1 - #2 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
DRAM dc-to-dc power converter fuse
This alarm indicates that the Dynamic Random Access Memory (DRAM) dc-to-dc power
converter output (power) fuse on the PDU alarm board has failed.
The fuse on the board is connected to the dc-to-dc power converter for the +27 V battery backup
power supply which sustains power to the Base Station Unit shelf (BSU)/Remote Transcoder
Unit (RXU) in the event of a main power failure.
DC-to-DC converter
This power converter is mounted on the back of the PDU. It converts +27 V dc to +5 V dc for
use by the digital boards in the event of main supply failure. In an emergency, it helps conserve
battery power while providing power to the digital boards required to continue to processing
calls.
Possible causes

• The power supply fuse to the dc-to-dc converter is faulty or blown causing the failure.
• The dc-to-dc converter is faulty causing the failure.
• The battery backup power supply is not connected (to the cabinet) causing the failure.
25-46 68P02901W26-S
Nov 2007
Procedure
Procedure 25-21 Battery backup fuse #1 - #2 failure
1 Review the alarm report and event logs to determine the cause(s)
of this alarm.
2 Is the battery backup option implemented due to a main power
failure.
• If yes, this alarm is expected. A main power failure is in

process. Field representatives should already be investigating
this fault condition. Verify this with field service office.
• If no, continue to the next step.

3 Determine the type of cabinet where the alarm is occurring.
a BTS5 cabinet The backup battery fuse #1 (or
#2) on the PDB, PAB or DAB must
be replaced. Go to step 4.
not a BTS5 cabinet The backup battery fuse #1 (or
#2) on the PAB or DAB must be
replaced. Go to step 4.
4 Send a field representative to the site to replace the bad fuse. While
there, check the backup battery connections, power supply fuses
and the dc-to-dc converter.

68P02901W26-S 25-47
Nov 2007
35 - 37. IAS: Lower cage fan #0 - #2 failure Chapter 25: IAS Alarms
35 - 37. IAS: Lower cage fan #0 - #2 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a fan in the lower cage has failed. A Transistor-to-Transistor Logic
(TTL) alarm has been generated indicating that a fan has failed.
Possible causes

• The power is not connected to the fan causing the failure.
• A mechanical fault may have occurred (For example, a fan blade was obstructed).
Procedure
Procedure 25-22 Lower cage fan #0 - #2 failure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Determine whether there are event messages for any fuse alarms.
3 Send a field representative to the site to check to see if the fan
is still functioning.
25-48 68P02901W26-S
Nov 2007

68P02901W26-S 25-49
Nov 2007
38 - 40. IAS: Upper cage fan #3 - #5 failure Chapter 25: IAS Alarms
38 - 40. IAS: Upper cage fan #3 - #5 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a fan in the upper cage has failed. A Transistor-to-Transistor Logic
(TTL) alarm has been generated indicating that a fan has failed.
Possible causes

• The power is not connected to the fan causing the failure.
• A mechanical fault may have occurred (For example, fan blade was obstructed).
Procedure
Procedure 25-23 Upper cage fan #3 - #5 failure
this alarm.
2 Determine whether there are event messages for any fuse alarms.
3 Send a field representative to the site to check to see if the fan
is still functioning.
25-50 68P02901W26-S
Nov 2007

68P02901W26-S 25-51
Nov 2007
41. IAS: Multicoupler failure Chapter 25: IAS Alarms
41. IAS: Multicoupler failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the multicoupler main power supply has failed causing the multicoupler
to fail. The internal preselector fuses on the alarm board malfunctioned causing the power flow
of the +27 V main dc power supply (which is connected to the multicoupler) to be interrupted.
The following are the alarm boards to which this failure may apply:
If a multicoupler fails, the receiver sensitive to the Receive (Rx) signal is degraded on
the failed antenna path.
Possible causes
One or more preselector fuses are faulty or blown causing the failure.
25-52 68P02901W26-S
Nov 2007
Procedure
Procedure 25-24 Multicoupler failure
1 Review the alarm report and event logs to determine the cause(s) of this
alarm.
2 Review the applicable device alarm message.
3 Determine whether there are any active or current Voltage Standing Wave
Radio (VSWR) alarms.
• If yes, perform fault diagnostics on the VSWR alarm.
• If no, VSWR alarms have been generated, go to step 4.

4 Send a field representative to the site to replace the multicoupler module.

68P02901W26-S 25-53
Nov 2007
46. IAS: Converter failure Chapter 25: IAS Alarms
46. IAS: Converter failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the dc-to-dc power converter has failed due to the current output
integrity (state) of the converter.
This power converter module converts -48 V or -60 V dc to +5 V dc and +12 V dc for use by the
digital boards.
This alarm applies only to the BTS 4D configuration.
Possible causes

• The dc-to-dc power converter is faulty.
• A fuse to the dc-to-dc power converter is faulty.
25-54 68P02901W26-S
Nov 2007
Procedure
Procedure 25-25 Converter failure
this alarm.
2 Review the applicable device alarm message.
3 Determine if the dc-to-dc power converter failed.
If the dc-to-dc power Then...
converter...
failed Send a field representative to
the site to replace the dc-to-dc
converter module.
did not fail There is a fuse failure.
Send a field representative to
the site to replace the faulty fuse.

68P02901W26-S 25-55
Nov 2007
47. IAS: Converter over temperature Chapter 25: IAS Alarms
47. IAS: Converter over temperature

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the dc-to-dc power converter has overheated to a temperature level
which is beyond the (safe) temperature range allowed for proper operation of equipment.
This alarm applies only to the BTS 4D configuration.
Possible causes

• The dc-to-dc power converter is faulty causing the failure.
• A fuse to dc-to-dc power converter is faulty.
25-56 68P02901W26-S
Nov 2007
Procedure
Procedure 25-26 Converter over temperature
of this alarm.
2 Check the alarm report for other internal (cabinet) alarms as well as
External Alarm System (EAS) alarms.
3 After checking the report, determine whether the dc-to-dc converter
failed.
4 Determine whether the antenna is functioning at the site.
If the antenna is... Then...
functioning Send a field representative to the
site to check the following:
• The connection between

the antenna and the VSWR
Bridge.
• The connection between the

VSWR Bridge and the PAB
board.
• Make any necessary

adjustments.
not functioning Send a field representative to the
site to check the following:
• Verify that the transceiver

associated with the antenna
no longer has channel traffic.
• Investigate for other

converter-related cabinet
problems (fuses, fan failures)
and/or environmental
factors.
68P02901W26-S 25-57
Nov 2007

25-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48 - 50. IAS: Preselector 1B-3B fuse failure
48 - 50. IAS: Preselector 1B-3B fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the preselector fuse (1B, 2B, or 3B) on an alarm board has failed. The
fuse on the board is connected to the +27 V power supply which goes to (and is connected
to) the preselector.
Standard diversity
If standard diversity is used and the preselector is Out Of Service (OOS), the receiver sensitivity
to the Receive (Rx) signal is reduced when this alarm is present.
Possible causes
The preselector fuse (1B, 2B, or 3B) is faulty or blown causing the failure.
68P02901W26-S 25-59
Nov 2007
Procedure
Procedure 25-27 Preselector 1B-3B fuse failure

2 Check the alarm boards, board installation, (fuse) connections and cabling.

25-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 51. IAS: Duplexer voltage error
51. IAS: Duplexer voltage error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
One of the duplexer blocks has a Duplexer Detect alarm. This alarm indicates that the VSWR
circuitry in the duplexer has no power. The additional data indicates which duplexer detected
the failure.
This alarm is reported for Horizon II macro only.
The following additional data enumerates which duplexer block detected the failure:
• Duplexer block number.
• Firmware detector fault zone.
Possible causes

• A tripped circuit breaker in the cabinet.
• A blown fuse in the duplexer.
68P02901W26-S 25-61
Nov 2007
Procedure
Procedure 25-28 Duplexer voltage error

25-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 59. IAS: Battery backup output failure
59. IAS: Battery backup output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the battery backup output power (connected to the DAB alarm board)
for the purpose of protecting the Dynamic Random Access Memory (DRAM) has failed.
This +27 V battery backup output power supply sustains power to the Base Station Unit shelf
(BSU) or Remote Transcoder Unit (RXU) in the event of a main power failure.
Possible causes

• The power supply fuse to the dc-to-dc converter is faulty or blown causing the failure.
• The dc-to-dc converter is faulty causing the failure.
• The battery backup power supply is not connected (to the cabinet) causing the failure.
• The output of the battery backup supply is in an overcurrent protection state thus causing
the output to fail.
68P02901W26-S 25-63
Nov 2007
Procedure
Procedure 25-29 Battery backup output failure
of this alarm.
failure.

process. Field representatives should be already investigating
this fault condition. Verify this with field service office.
• If no, go to step 3.
3 Determine the type of cabinet where the alarm is occurring:
• For a BTS5 cabinet, the battery fuse on the PDB, PAB or DAB
must be replaced. Go to step 4.
• For a non-BTS5 cabinet, the battery fuse on the PAB or DAB

must be replaced. step 4.
4 Send a field representative to the site to determine if the battery
backup is connected. While there, check the backup battery
connections, power supply fuses and the dc-to-dc converter.

25-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 60. IAS: Battery backup input failure
60. IAS: Battery backup input failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the battery backup input power (connected to the DAB alarm board)
for the purpose of protecting the Dynamic Random Access Memory (DRAM) has failed.
This +27 V battery backup input power supply helps sustain power to the Base Station Unit
shelf (BSU) or Remote Transcoder Unit (RXU) in the event of a main power failure.
Possible causes

• The fuse on the power alarm system is faulty or blown causing the failure.
• The battery backup power supply is not connected (to the power alarm system) causing
the failure.
68P02901W26-S 25-65
Nov 2007
Procedure
Procedure 25-30 Battery backup input failure
of this alarm.
failure.

process. Field representatives should be investigating this
fault condition. Verify this with field service office.
3 Determine the type of cabinet where the alarm is occurring:
• For a BTS5 cabinet, the battery fuse on the PDB, PAB or DAB
• For a non-BTS5 cabinet, the battery fuse on the PAB or DAB

4 Send a field representative to the site to determine if the battery
backup is connected. While there, check the backup battery
connections, power supply fuses and the dc-to-dc converter.

25-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 61. IAS: RCU #5 circuit breaker failure
61. IAS: RCU #5 circuit breaker failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the circuit breaker connected to the +27 V power supply for the sixth
transceiver 5 has failed, causing the power supply to the transceiver to be interrupted.
When the circuit breaker of the transceiver controlling the combiner fails, the cell is placed Out
Of Service (OOS). The fault must be cleared and the circuit breaker must be reset as soon as
possible to return the cell to service.
In a phased combiner system, only the combiner connected to the faulty transceiver is OOS,
rendering all transceivers attached to the combiner OOS.
Possible causes

• The overcurrent protection trip is faulty.
• The circuit breaker has failed.
• The circuit breaker is (accidentally) disconnected.
68P02901W26-S 25-67
Nov 2007
Procedure
Procedure 25-31 RCU #5 circuit breaker failure
this alarm.
2 Send a field representative to the site to reset the breaker and/or
replace the faulty hardware.

25-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 62. IAS: DPSM 1 failure
62. IAS: DPSM 1 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Digital Power Supply Module (DPSM) 1 has failed because the
current to the DPSM 1 was interrupted causing it to fail.
Possible causes

68P02901W26-S 25-69
Nov 2007
Procedure
Procedure 25-32 DPSM 1 failure
this alarm.
2 Determine whether the DPSM 1 power unit removed just before
the alarm was reported. (Also, determine if there are field
representatives currently at the site).
• If yes, this alarm is expected. It is cleared when a working

DSPM power supply module is inserted.
• If no, send a field representative to the site to locate the power

supply module and continue with fault diagnostics on DSPM 1.

25-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 63. IAS: DPSM 0 failure
63. IAS: DPSM 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Digital Power Supply Module (DPSM) 0 has failed because the
current to the DPSM 0 was interrupted causing it to fail.
Possible causes

• The circuit breaker may have failed.
68P02901W26-S 25-71
Nov 2007
Procedure
Procedure 25-33 DPSM 0 failure
this alarm.
2 Determine whether the DPSM (0) power unit removed just before
the alarm was reported. (Also, determine if there are field
representatives currently at the site).
• If yes, this alarm is expected. It is cleared when a working

DPSM power supply module is inserted.
• If no, send a field representative to the site to locate the power

supply module and continue with fault diagnostics on DPSM 0.

25-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 64 - 65. IAS: Fan power converter 1-2 failure
64 - 65. IAS: Fan power converter 1-2 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the -48 V dc-to-dc input power to the fan power converter (1 or 2)
was interrupted causing the converter to fail.
Possible causes

68P02901W26-S 25-73
Nov 2007
Procedure
Procedure 25-34 Fan power converter 1-2 failure
1 Send a field representative to the site to check the circuit breaker to

determine whether it has failed or has been disconnected.
2 Reconnect or replace the faulty circuit breaker.

25-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 66 - 70. IAS: RCU #0 - #4 circuit breaker failure
66 - 70. IAS: RCU #0 - #4 circuit breaker failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the circuit breaker connected to the +27 V power supply for the
transceiver 0-4 has failed, causing the power supply to the transceiver to be interrupted.
When the circuit breaker of the transceiver controlling the combiner fails, the cell is placed Out
Of Service (OOS). The fault must be cleared and the circuit breaker must be reset as soon as
possible to return the cell to service.
This fault is service-affecting.
In a phased combiner system, only the combiner connected to the faulty transceiver is OOS,
rendering all transceivers attached to the combiner OOS.
Possible causes

68P02901W26-S 25-75
Nov 2007
Procedure
Procedure 25-35 RCU #0 - #4 circuit breaker failure

2 Reconnect or replace a faulty circuit breaker.

25-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 71 - 74. IAS: Converter #1 - #4 failure
71 - 74. IAS: Converter #1 - #4 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the -48 V (or -60 V) dc-to-dc input power to a power converter module
(1-4) through a circuit breaker was interrupted, causing the converter to fail.
Possible causes

Procedure
Procedure 25-36 Converter #1 - #4 failure

68P02901W26-S 25-77
Nov 2007

25-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 75. IAS: IAS +27 V DAB power fuse failure
75. IAS: IAS +27 V DAB power fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Internal Alarm System (IAS) +27 Volt power fuse has failed.
The fuse is connected to the +27 V dc power supply which supplies or sustains power to the
Distribution Alarm Board (DAB).
Possible causes

68P02901W26-S 25-79
Nov 2007
Procedure
Procedure 25-37 IAS +27 V DAB power fuse failure


25-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 80. IAS: Power supply unit - Input failure
80. IAS: Power supply unit - Input failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that there has been a loss of ac power. Due to this power loss, the cabinet
has switched to the emergency battery backup input power supply.
This +27 V battery backup input power supply powers the BTS until the ac power can be
restored or until the battery voltage drops out of range.
This alarm applies only to M-Cell2, M-Cell6, M-Cell micro, M-Cell city, Horizon II macro, Horizon
micro (M-Cell arena) and Horizon compact (M-Cell arena macro) cabinets.
Possible causes
For an indoor system:

• The input voltage is out of specification causing the failure. (In this case, the power supply
units would operate for a small duration until the input voltage was out of range).
For an outdoor system:

• The ac supply is faulty.
68P02901W26-S 25-81
Nov 2007
Procedure
Procedure 25-38 Power supply unit - Input failure
Send a field representative to the site to determine if the input power source
(equipment/cables) are faulty.

25-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 81. IAS: Power supply unit - Output failure
81. IAS: Power supply unit - Output failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that there has been a loss of output power due to the failure of the Power
Supply Unit (PSU). It is also possible that the output power failure is due to the input feed
(voltage) which is interrupted (or discontinued) due to faulty equipment.
This alarm applies only to M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
This fault condition can be service-affecting, if there is no PSU redundancy at a site.
Possible causes

• The input feed (voltage) is lost causing the output failure.
• The output power supply cable is faulty.
68P02901W26-S 25-83
Nov 2007
Procedure
Procedure 25-39 Power supply unit - Output failure
1 Determine whether the PSU failure is related to other more serious

fault conditions. Check the Alarm window for other failures at the
site with the PSU power failure.
• If other failures exist for the site, prioritize the faults and refer
to this manual for the Alarm descriptions and fault resolution
procedures.
• If other failures do not exist at that site, go to step 2.

2 Send a field representative to the site to determine if the input power
source (equipment and/or cables) are faulty or the PSU equipment is
faulty. Replace any faulty equipment.

25-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 82. IAS: BTS cabinet over temperature
82. IAS: BTS cabinet over temperature

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Base Transceiver Station (BTS) cabinet ambient temperature has
overheated to a level of 70°C which is beyond the (safe) temperature range allowed for proper
operation of BTS equipment.
This internal cabinet condition has been detected by either the BTS Over Temperature
Thermostat or by the Power Supply Unit (PSU) which has overheated.
Possible causes

• The air passage ways (inlet, outlet, and air ways) is obstructed.
• The BTS over temperature thermostat is faulty.
• The PSU is malfunctioning. (This possible cause does not apply to Horizon macro cabinets).
• The BTS Heat Management System Over Temperature is faulty. (This possible cause
applies only to outdoor cabinets).
68P02901W26-S 25-85
Nov 2007
The following happens if a BTS cabinet over temperature condition has occurred
and the cabinet temperature has risen to 80 degrees C:
• The power to that BTS cabinet is shut off. (Onsite, a red LED lights on the
ASPM or the NSPM to indicate the fault condition).
• The system generates the alarm 10. RSL: Link disconnected because an
RSL link is disconnected when the power is shut off.
Procedure
Procedure 25-40 BTS cabinet over temperature
Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, thermostat or BTS heat management system
(outdoor cabinet) equipment is faulty.

25-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 83. IAS: Low voltage disconnect imminent
83. IAS: Low voltage disconnect imminent

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that there has been a loss of ac power or the Power Supply Unit (PSU) has
failed, causing a loss of input power from the backup battery.
This alarm is generated when the battery backup power (voltage) is nearing the point where it
starts initiating a disconnection of the BTS cabinets. This alarm applies only to outdoor cabinets.
This +27 V battery backup input power supply powers the BTS until the ac power can be
restored or until the battery voltage drops out of range.
This alarm applies only to M-Cell2, M-Cell6, M-Cell micro, M-Cell city, Horizon II
macro, Horizon micro (M-Cell arena) and Horizon compact (M-Cell arena macro)
cabinets.
68P02901W26-S 25-87
Nov 2007
Possible causes Chapter 25: IAS Alarms
Possible causes

• The input feed (voltage) is lost causing the output failure.
• The PSU is malfunctioning.
Procedure
Procedure 25-41 Low voltage disconnect imminent
this alarm.
2 Investigate the ac power failure.
3 Send a field representative to the site to determine if the PSU and/or
the input power source (equipment/cables) are faulty.

25-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 84. IAS: Air conditioning unit failure
84. IAS: Air conditioning unit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Base Transceiver Station (BTS) or ancillary cabinet Air Conditioning
Unit has failed.
This alarm is generated when an air conditioning (air) inlet or outlet is blocked causing the
equipment to fail. This alarm applies only to outdoor cabinets, M-Cell2 and M-Cell6 cabinets.
Possible causes

• The air inlet vent to the air conditioning unit is blocked causing the unit to fail.
• The air outlet vent from the air conditioning unit is blocked causing the unit to fail.
• The air conditioning unit is faulty.
68P02901W26-S 25-89
Nov 2007
Procedure
Procedure 25-42 Air conditioning unit failure
1 Send a field representative to the site to locate the failed unit.

2 Check if the inlet/outlet vents are blocked.

25-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 85. IAS: Heat management system unit failure
85. IAS: Heat management system unit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that Ancillary Heat Management Unit at a Base Transceiver Station (BTS)
has failed.
This alarm is generated when a heat management (air) inlet or outlet is blocked causing the
equipment to fail. This alarm applies only to outdoor cabinets.
This alarm may be received in conjunction with the alarm, 82. IAS: BTS Cabinet Over
Temperature.
This alarm applies only to, M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
Possible causes

• The air inlet vent to the heat management unit is blocked causing the unit to fail.
• The air outlet vent from the heat management unit is blocked causing the unit to fail.
• The heat management unit is faulty.
68P02901W26-S 25-91
Nov 2007
Procedure
Procedure 25-43 Heat management system unit failure
1 Send a field service representative to the site to locate the failed unit.
2 Check if the inlet/outlet vents are blocked.

25-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 86. IAS: Cabinet fan failure
86. IAS: Cabinet fan failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Base Transceiver Station (BTS) or ancillary cabinet fan (or fans)
has failed.
This alarm is generated when a fan has stopped functioning due to a power loss or an (air flow)
obstruction causing the equipment to stop. (The obstruction may have damaged the unit). This
alarm applies only to outdoor M-Cell2 and M-Cell6 cabinets.
Possible causes

• The air inlet vent to the fan unit is blocked causing the unit to fail.
• The air outlet vent from the fan unit is blocked causing the unit to fail.
• The airways is obstructed causing the fan unit to fail.
• The Power Supply Unit (PSU) is malfunctioning causing the fan units to stop.
68P02901W26-S 25-93
Nov 2007
Procedure
Procedure 25-44 Cabinet fan failure
1 Send a field representative to the site to locate the failed unit.

2 Check if the inlet/outlet vents or air passage ways are blocked.
3 Check the PSU as well.

25-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 87. IAS: Ancillary cabinet over temperature
87. IAS: Ancillary cabinet over temperature

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that an Ancillary cabinet ambient temperature has overheated to a level
which is beyond the (safe) temperature range allowed for proper operation of equipment.
This internal cabinet condition has been detected by either the Ancillary Over Temperature
Thermostat or by the Power Supply Unit (PSU) which has overheated. This alarm applies only to
M-Cell2, M-Cell6 and Horizon II macro cabinets.
Possible causes

• The air passage ways (inlet, outlet and air ways) is obstructed.
• The Ancillary Over Temperature Thermostat is faulty.
• The PSU is malfunctioning.
• The Ancillary heat management system over temperature is faulty. (This applies only to
outdoor cabinets).
68P02901W26-S 25-95
Nov 2007
Procedure
Procedure 25-45 Ancillary cabinet over temperature
Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, thermostat or Ancillary Heat Management
System (outdoor cabinet) equipment is faulty.

25-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88 - 90. IAS: Voltage standing wave ratio sector 1-3 failure
88 - 90. IAS: Voltage standing wave ratio sector 1-3

failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Voltage Standing Wave Ratio (VSWR) unit has failed in a
sector (1-3). This failure may affect the signal quality transmitted in a sector. If the ratio of
forward-to-reflected power is not maintained and there is an excessive reflected signal, the
quality of the signal transmitted is compromised.
This alarm applies only to M-Cell2 and M-Cell6 hardware.
Possible causes

• The VSWR unit is faulty.
• The antenna is faulty.
• The Alarms (or the EAS or PIX) board is improperly connected to the VSWR Bridge.
• The Alarms board (or connectors on the board) may be faulty.
• The antenna is improperly connected to the VSWR Bridge.
68P02901W26-S 25-97
Nov 2007
The VSWR unit is typically connected to the Alarms board or EAS (PIX)
depending on the type of platform. Therefore, the specific alarms or EAS (or
PIX) board or connections used may be the source of this fault condition. Ensure
that it is properly connected; check the connectors on the suspect board which
connect to the VSWR Bridge.
Procedure
Procedure 25-46 IAS: Voltage standing wave ratio sector 1-3 failure
1 Send a field representative to the site to determine whether the equipment

is faulty.
2 The field representative must be prepared to check, repair or replace the
following equipment, if necessary. The VSWR unit (1-3) are:
• The connection between the antenna and the VSWR Bridge.
• The connection between the VSWR Bridge and the Alarms board (or
the EAS or PIX board).
• The antenna.

25-98 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 91. IAS: Voltage standing wave ratio performance low
91. IAS: Voltage standing wave ratio performance low

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Voltage Standing Wave Ratio (VSWR) unit transmitted signal
quality has degraded in a sector (1-3). This alarm is generated when a problem has been
detected with a connection to the VSWR unit.
The ratio of forward-to-reflected power has been compromised. As a result, there is an excessive
reflected signal affecting the quality of the signal being transmitted.
This alarm applies only to M-Cell2 and M-Cell6 hardware.
Possible causes

• The VSWR unit is faulty.
• The antenna is faulty due to weather conditions, external damage, errors in installation
and so on.
• The Alarms (or the EAS or PIX) board (or connectors on the board) is faulty. (Refer Note).
• The antenna is improperly connected to the VSWR Bridge.
68P02901W26-S 25-99
Nov 2007
The VSWR unit is typically connected to the Alarms board or EAS (PIX) depending
on the type of platform. Therefore, the specific Alarms or EAS (or PIX) board or
connections used may be the source of this fault condition. Ensure that it is properly
connected; check the connectors on the suspect board which connect to the VSWR
Bridge.
Procedure
Procedure 25-47 Voltage standing wave ratio performance low
1 Send a field representative to the site to determine whether the hardware

is faulty.
2 The field representative must check all connections and be
prepared to repair or replace the following hardware, if necessary:
The VSWR unit (1-3) are
• The antenna.
• The Alarms board or EAS (or PIX) board.
• The link between the antenna and the VSWR Bridge.
• The link between the VSWR Bridge and the Alarms board (or EAS or
PIX board).

25-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 92. IAS: Smoke alarm
92. IAS: Smoke alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that smoke has been detected within either a Base Transceiver Station
(BTS) or an ancillary cabinet. This fault condition indicates that the cabinet is overheated to a
level which may damage the equipment inside.
This alarm was generated because an internal cabinet over temperature condition was detected
by either the BTS (or Ancillary) Over Temperature Thermostat or by a Power Supply Unit (PSU)
that has overheated.
Possible causes
The cause for the smoke alarm is fire which is caused by one of the following:
• The air passage ways (inlet, outlet and air ways) is obstructed causing the equipment to
overheat.
• The fan is malfunctioning causing the equipment to overheat.
• The PSU is malfunctioning or overheating.
• The air conditioning unit is faulty causing the equipment to overheat.
• The Ancillary Heat Management System is faulty causing the equipment to overheat. (This
possible cause applies only to outdoor cabinets).
68P02901W26-S 25-101
Nov 2007
Procedure
Procedure 25-48 Smoke alarm
1 Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, the thermostat, the fan(s), the air conditioning
unit or the Ancillary Heat Management System (outdoor cabinet) is faulty.
2 Replace any defective (or damaged) equipment.

25-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 93. IAS: Door open
93. IAS: Door open

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that at a site a cabinet door is open which should not be.
If one of the following doors is open, this alarm is generated:

• Base Transceiver Station (BTS) - door or hood.
• Ancillary cabinet - door or hood.
• Side cabinet door.
This alarm applies only to M-Cell2, M-Cell6, Horizon macro and Horizon II macro
cabinets.
Possible causes

• The cabinet door is not secured properly.
• The door latches are defective.
68P02901W26-S 25-103
Nov 2007
Procedure
Procedure 25-49 Door open
1 Send a field representative to the site to close the door(s).

2 Check the cabinet door latches; any defective latches must be replaced.

25-104 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 94. IAS: No connection to alarms board - Connection broken
94. IAS: No connection to alarms board - Connection

broken
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the connection between the radio (Transceiver Control Unit(s) TCUs)
and the Alarms board has been interrupted.
This alarm is generated when the Base Station System (BSS) software has detected that none
of the TCUs in a cabinet are connected to the Alarms board.
This alarm applies only to M-Cell2 and M-Cell6 cabinets.
When any of the following alarms are active, all other IAS and EAS alarms in the
active list (using disp_act <site #> command) are not dependable:

68P02901W26-S 25-105
Nov 2007
Possible causes

• The Alarms board link to a DRI (TCU) is not established.
• The Alarms board fiber link to a DRI (TCU) is faulty.
• The Alarms board link is connected to an Out Of Service (OOS) DRI (TCU).
• The Alarms board link is connected to an Enabled-Unlocked DRI (TCU) that does not
have an RTF equipped.
• The Alarms board is faulty.
Procedure
Procedure 25-50 No connection to alarms board - Connection broken

25-106 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 95. IAS: Low noise amplier fuse failure
95. IAS: Low noise amplier fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the low noise amplifier fuse in an M-Cell cabinet has failed. The fuses
are located in different places within each type of M-Cell cabinet: M-Cell2 and M-Cell6.
This alarm applies only to M-Cell2 and M-Cell6 cabinets.
Possible causes

• The amplifier fuse is faulty.
• The cabling connecting the fuse panel and IADU board is faulty.
• The IADU board (above the radios) is faulty.
• The Alarms board is faulty.
68P02901W26-S 25-107
Nov 2007
Procedure
Procedure 25-51 Low noise amplier fuse failure
Send a field representative to the site to check and replace the fuse, the
Alarms board, the IADU board and/or the cabling if necessary.

25-108 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 96. IAS:
No redundant connection to alarms board - Connection broken
96. IAS: No redundant connection to alarms board

- Connection broken
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the redundant (backup) radio
connection to the alarms board is not functioning. The redundant connection may not be
functioning due to either a faulty cable or an onsite disconnection.
This alarm applies to M-Cell2 and M-Cell6 cabinets.
Possible causes

• The redundant cable between the radio and alarms board is disconnected.
• The redundant cable between the radio and alarms board is faulty.
68P02901W26-S 25-109
Nov 2007
Procedure
Procedure 25-52 No redundant connection to alarms board - Connection broken
1 Send a field representative to the site to check the cabling from the Alarms
board to the (radio) DRI (TCUs).
2 Be prepared to reconnect or replace the cabling to the Alarms board, if
necessary.

25-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 97. IAS: No connection to alarm board - Radio OOS
97. IAS: No connection to alarm board - Radio OOS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the BSS software has detected that all radio (Transceiver Control Unit
(TCU)) connections to the alarms board are Out Of Service (OOS).
This alarm is generated when the last (final) radio connection goes OOS. In this case, there is no
connection because the radios (DRI (TCUs)) are faulty.
• This alarm applies to M-Cell2, M-Cell6, Horizon macro and Horizon II macro
cabinets.
• When any of the following alarms are active, all other IAS and EAS alarms in the
94.IAS: No Connection to Alarms Board - Connection Broken.
97.IAS: No Connection to Alarms Board - Radio OOS.
99.IAS: No Connection to Alarms Board - Alarm Board Removed.
Possible causes
The last (or only) radio DRI (TCU) is faulty.
68P02901W26-S 25-111
Nov 2007
Procedure
Procedure 25-53 No connection to alarm board - Radio OOS
1 Send a field representative to the site to check the radios (DRI (TCUs))
connected to the alarms board.
2 Attempt to restore the faulty DRI (TCUs) to service and replace either or
both DRI (TCUs), if necessary.

25-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 98. IAS: No redundant connection to alarms board - Radio OOS
98. IAS: No redundant connection to alarms board

- Radio OOS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the redundant radio (Transceiver
Control Unit (TCU)) connections to the alarms board are Out Of Service (OOS). The two radios
(DRI (TCUs)) are connected to the alarms board.
This alarm applies to M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
Possible causes
One radio DRI (TCU) is faulty.
Procedure
Procedure 25-54 No redundant connection to alarms board - Radio OOS
1 Send a field representative to the site to check both radios (DRI (TCUs))
connected to the alarms board.
2 Identify the faulty DRI (TCU).
3 Attempt to restore the faulty (redundant) DRI (TCU) to service and replace
it, if necessary.
68P02901W26-S 25-113
Nov 2007

25-114 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 99. IAS: No connection to alarm board - Alarm board removed
99. IAS: No connection to alarm board - Alarm board

removed
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the Alarms board has been physically
removed or has not been properly connected.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
When any of the following alarms are active, all other IAS and EAS alarms in the

68P02901W26-S 25-115
Nov 2007
Possible causes

• The Alarms board is not properly connected.
• The Alarms board is removed.
Procedure
Procedure 25-55 No connection to alarm board - Alarm board removed
1 Send a field representative to the site to determine whether the Alarms

board has been physically removed or is not properly connected.
2 Check the connections, attempt to reconnect the Alarms board and replace
it, if necessary.

25-116 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 100. IAS: Cabinet protection system failure
100. IAS: Cabinet protection system failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the internal cabinet protection system
has failed. When this alarm is generated, a timer is started. If the operator can resolve the fault
condition and have the alarm clear before the timer expires, the power system to the cabinet
continues to operate. Otherwise, the power system will shutdown and require an onsite visit to
reset the power system. The cabinet protection system monitors and reports the environmental
fault conditions:
• A cabinet over temperature condition - The internal cabinet temperature has exceeded
safe limits.
• A smoke condition - A fire has produced smoke that has either originated in or penetrated
into the cabinet.
Possible causes

• The control board is faulty.
• The power supply to the control board is disconnected.
• The power supply to the control board is faulty.
• The connection to the cabinet input circuity breaker is faulty.
68P02901W26-S 25-117
Nov 2007
Procedure
Procedure 25-56 Cabinet protection system failure
1 Check the power supply, control board and input circuit breaker connections,
attempt to reconnect them and be prepared to replace any of the above,
if necessary.
2 Reset the power system after the fault condition has been resolved.
25-118 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 101. IAS: Power supply temperature high
101. IAS: Power supply temperature high

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that one or more Power Supply Units
(PSUs) in a Horizon macro BTS has exceeded the established (safe) temperature range.
Possible causes

• The PSU is faulty.
• The environmental temperature is too high.
• The Heat Management System (HMS) in an outdoor cabinet is faulty.
68P02901W26-S 25-119
Nov 2007
Procedure
Procedure 25-57 Power supply temperature high
1 Review the alarm report and event logs to check for other alarms at
the same site.
• Check for alarm, 85. IAS: Heat management system unit

failure.
• If (IAS) alarm 85 is present at the Horizon macro site, it is

possible the failure of the HMS has caused this alarm (101).
Consult the alarm description and troubleshooting procedure
for the 85. IAS alarm in this manual.
2 Send a field representative to the site to determine which equipment
has caused this fault condition. Check the PSUs, environmental
conditions, the HMS and replace any of the above, if necessary.

25-120 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 102. IAS: Mains ac supply failure
102. IAS: Mains ac supply failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that ac power to the backup battery box
(connected to a Horizon macro cabinet) is no longer available. As a result, ac power is not
being sent through to the Horizon macro BTS.
Possible causes

• The ac circuit breaker is in the off position due to a power surge.
• The cable from the rectifier to the external Horizon macro alarm connector is not properly
connected.
• The cable (or connector on the cable) from the rectifier to the external Horizon macro
alarm connector is faulty.
• A rectifier within the battery box is faulty.
68P02901W26-S 25-121
Nov 2007
Procedure
Procedure 25-58 Mains ac supply failure
1 Send a field representative to the site to determine which equipment has

caused this fault condition.
2 Check the ac supply circuit breaker, the cable (rectifier to Horizon macro
alarm connector) and the battery box rectifiers.
3 Replace any of the above, if necessary.

25-122 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 103. IAS: Fan tray 0 failure
103. IAS: Fan tray 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that a fan within fan tray 0 has either failed
or has not been properly installed (connected).
Possible causes

• A quad fan is faulty.
• The fan fuse is faulty.
• The fan tray is not properly installed.
68P02901W26-S 25-123
Nov 2007
Procedure
Procedure 25-59 Fan tray 0 failure

2 Check the quad fans in fan tray 0, the tray connections and fan fuses and
replace either the fan tray or fuses, if necessary.

25-124 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Possible causes

• A dual fan is faulty.
68P02901W26-S 25-125
Nov 2007
Procedure

2 Check the dual fans in fan tray 1, the tray connections and fan fuses and
replace either the fan tray or fuses, if necessary.

25-126 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Possible causes

• A dual fan is faulty.
68P02901W26-S 25-127
Nov 2007
Procedure

2 Check the dual fans in fan tray 2, the tray connections and fan fuses and be
prepared to replace either the fan tray or fuses, if necessary.

25-128 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 106. IAS: Rectier failure
106. IAS: Rectier failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the output from a backup battery box
has failed. This alarm is generated when the rectifier has failed or the cable from the battery
box (rectifier)-to-Horizon macro alarm connector is faulty; or when the cable is not properly
connected.
Possible causes

• The rectifier is damaged or faulty.
• The cable from the rectifier to the external Horizon macro alarm connector is not properly
connected.
• The cable (or connector on the cable) from the rectifier to the external Horizon macro
alarm connector is faulty.
• The ac power may have failed.
68P02901W26-S 25-129
Nov 2007
Procedure
Procedure 25-62 Rectier failure
1 Check the output LEDs on the rectifier front panel.

2 Replace the rectifiers that are defective (if any) from the power cage.
3 If no rectifiers are defective, check the cable from the rectifiers in
the battery box to the external Horizon macro alarm connector:
• If the cable is loose, tighten the connection.
• If the cable is not properly connected, connect it properly.
• If the cable is faulty, replace it.
25-130 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 107. IAS: Battery box temperature high
107. IAS: Battery box temperature high

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the temperature in the backup battery
box has exceeded the established limits for safe operation of the equipment.
Possible causes

• The air passage ways (inlet, outlet, and air ways) is obstructed causing the equipment to
overheat.
• The thermostat is faulty.
• The environmental temperature is too high.
• The Heat Management System (HMS) in an outdoor cabinet is faulty.
• The cable from the battery box to a cabinet is not properly connected.
• The cable (or cable connectors) from the battery box to a cabinet is faulty.
68P02901W26-S 25-131
Nov 2007
Procedure
Procedure 25-63 Battery box temperature high

2 Check the air passage ways, the thermostat, the HMS, the cable (from the
battery box to the cabinet) and replace any of the above, if necessary.

25-132 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 108. IAS: Alarm board failed
108. IAS: Alarm board failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that BSS software has detected that the alarms board in a Horizon macro
BTS has failed due to faulty (Alarms) board circuitry or board damage due to conditions in
the field.
Possible causes

• The Alarms board may have failed due to damage caused by a power surge.
• The Alarms board may have failed due to faulty circuitry on the board.
68P02901W26-S 25-133
Nov 2007
Procedure
Procedure 25-64 Alarm board failed
1 Review the alarm report and event logs to determine the cabinet ID
for the Horizon macro cabinet where the alarms board has failed.
The cabinet ID is specified by the IAS device ID displayed

in the alarm output.
2 Send a field representative to the site to replace the alarms board.

25-134 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 109. IAS: Auxiliary alarm 1
109. IAS: Auxiliary alarm 1

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This is a spare external alarm for the Horizon macro BTS.
Possible causes
Possible causes are not defined for this alarm.
Procedure
No clearing procedures are defined for this alarm.
68P02901W26-S 25-135
Nov 2007
110. IAS: Urgent critical alarm Chapter 25: IAS Alarms
110. IAS: Urgent critical alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This is a customer or site-specific external alarm.
The IAS 110 alarm is a customer or site-specific external alarm. It is often configured
for Horizon macro and Horizon II macro battery backup testing, but it may be also
used for a variety of other purposes. Care must therefore be taken when responding
to this alarm.
Possible causes
Possible causes are varied depending on the actions to which the alarm is tied.
Procedure
If the IAS110 alarm is used for Horizon macro and Horizon II macro battery backup testing,
refer to the relevant service manual. For all other purposes, refer to local site procedures.
25-136 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 111. IAS: Cabinet protection board fuse failure
111. IAS: Cabinet protection board fuse failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The fuse (F23) feeding +27 V dc from the Distribution Alarm Board (DAB) to the Cabinet
Protection Board (CPB) has failed. The CPB continues to run on its redundant power supply.
No additional information is displayed in the output for this alarm.
Possible causes

• Faulty components on the +27 V dc input to the CPB.
• Fuse end-of-life failure.
• Short circuit on the +27 V dc feed cable.
• Short circuit on the wires from the DAB to the CPB.
• Faulty fuse (F23) detection circuitry on the DAB.
Procedure
Procedure 25-65 Cabinet protection board fuse failure
68P02901W26-S 25-137
Nov 2007

25-138 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 112 - 113. IAS: Heat management system unit failure 1 and 2
112 - 113. IAS: Heat management system unit failure 1

and 2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This alarm is generated if the Heat Management System (HMS) at a BTS cabinet fails.
Possible causes

• Faulty HMS.
• Blocked air inlet or outlet vent.
• Excessive ambient temperature.
Procedure
Procedure 25-66 Heat management system unit failure 1 and 2
68P02901W26-S 25-139
Nov 2007

25-140 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 114 - 115. IAS: Mains ac supply failure 1 and 2
114 - 115. IAS: Mains ac supply failure 1 and 2

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the BSS software has detected that the main ac input power to the
backup battery box is no longer available. This results in a loss of ac input power to the BTS.
Possible causes

• The associated circuit breaker is in the ‘OFF’ position following a power surge.
• Faulty or disconnected cable between the rectifier and the external alarm connector.
• A rectifier within the battery box is faulty.
Procedure
Procedure 25-67 Mains ac supply failure 1 and 2
68P02901W26-S 25-141
Nov 2007

25-142 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 116 - 117. IAS: Rectier failure 1 and 2
116 - 117. IAS: Rectier failure 1 and 2

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the BSS software has detected that the rectifier output from a backup
battery box has failed.
Possible causes

• Damaged or failed rectifier.
• Faulty or disconnected cable between the battery box (rectifier) and external alarm
connector.
68P02901W26-S 25-143
Nov 2007
Procedure
Procedure 25-68 Rectier failure 1 and 2
1 Send a field representative to the site to determine the cause of the failure
2 Check the output LEDs on the rectifier front panel and replace the rectifiers
that are defective from the power cage. If no rectifiers are defective,
check the cable from the rectifiers in the battery box to the external alarm
connector. It is loose, not properly connected or faulty, if so, connect it
properly or replace if faulty.

25-144 68P02901W26-S
Nov 2007
Chapter
26
KSW Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Kiloport Switch (KSW) and the KSW device subtype, Timeslot Switch (TSW) alarms covered
in this chapter are as follows:
• 0. KSW: Parity highway 0 on page 26-4.
• 4. KSW: Clock A signal loss on page 26-14.
• 5. KSW: Clock B signal loss on page 26-19.
• 6. KSW: 6.12 seconds reference loss on page 26-24.
• 7. KSW: Re-initialized unexpectedly on page 26-27.
• 8. KSW: Hard reset on page 26-30.
• 9. KSW: Watchdog timer expired on page 26-33.
• 10. KSW: Lost communication with KSW on page 26-36.
• 11 KSW: Local cage KSW TDM loopback test failure on page 26-41.
• 18 - 21. KSW: Failure of expanded inbound TDM highway on page 26-45.
• 22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure on page
26-48.
• 25 - 27. KSW: KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure on page
26-51.
• 224. KSW: Safe test audit failure on page 26-54.
• 225. KSW: Internal loopback audit failure on page 26-57.
• 232. KSW: Processor bus communication failure on page 26-60.
• 254. KSW: Device failure on page 26-63.
68P02901W26-S 26-1
Nov 2007
Introduction to KSW alarms Chapter 26: KSW Alarms
Introduction to KSW alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
KSW alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the
Kiloport Switch (KSW) and the KSW device subtype, Timeslot Switch (TSW) device.
The KSW alarms are comprised of Hardware and Firmware alarms. The hardware alarms
are categorized into two groups. They are Interrupt Generating alarms and MCAP Register
Reported Alarms.
The alarms in this chapter apply to InCell BSU-based systems (including ExCell and TopCell).
Alarm reporting
The KSW alarms are reported to the GPROC through status registers on the MCAP bus or by
assertion of an interrupt (message) onto the MCAP bus. The GPROC software then reports
the KSW alarms.
Firmware alarms are generated due to fault conditions existing on:

• The Time Division Multiplex (TDM) highways
• The KSW board
Hardware alarms are generated due to fault conditions with the following:
• The Digital Signaling Processor (DSP)
• The DSP peripherals on the KSW
• The MCAP or TDM interfaces
FRUs
A KSW device may be equipped on one of the FRUs shown in Table 26-1.
Table 26-1 KSW FRUs
FRU Description
KSW Kiloport Switch
TSW Timeslot Switch
KSW-Old Kiloport Switch - Old version
26-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R FRUs
68P02901W26-S 26-3
Nov 2007
0. KSW: Parity highway 0 Chapter 26: KSW Alarms
0. KSW: Parity highway 0

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected a parity
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway
0. The timeslots containing the parity error are masked until the alarm is acknowledged.
When this alarm occurs, two KSWs cannot communicate with each other. Each KSW (TSW) is
in a different cage.
This is a KSW firmware alarm and is therefore, generated according to fault conditions existing
on the TDM highways or fault conditions existing on the KSW board.
The contents of the Additional information field are shown in Table 26-2. Up to 33 bytes may
be displayed in this field.

first 00 to 08 The range (number) of timeslots affected by this
fault condition.
second third 00 to 0300 to FF The specific timeslot number that indicates the
beginning of the range.
fourth fifth 00 to 0300 to FF The number of consecutive timeslots within the
specified range.
Example
For example, second and third bytes of 02 41; fourth and fifth bytes of 00 03. This indicates a
timeslot range of three consecutive timeslots, beginning at timeslot 241, equal to a timeslot
range from 241 to 244.
If applicable, 6th to 9th, 10th to 13th, 14th to 17th, 18th to 21st, 22nd to 25th, 26th to 29th and
30th to 33rd bytes are handled in a similar way to the second and fifth bytes described above.
26-4 68P02901W26-S
Nov 2007
Possible causes

• Executing a swap of one GCLK for another may have caused the parity error.
• The entire TDM highway (0) may have failed.
• The KSW may have erroneously detected a problem with the parity bit on TDM highway 0.
• The block of parity error: the parity may have been off or incompatible on the other board.
• The TDM interface may have been experiencing problems on a board other than KSW.
(These problems can be caused by a reset, re-insertion, or physical removal of an active
board).
• A complete software download could have caused the parity error.
• The KSW may have experienced this parity error due to the failure of one or more of the
devices such as: MSI/XCDR, DRI, GDP, GPROC, KSW, RTF.
The KSW Parity Highway 0 alarms are detected by the KSW device. These
alarms frequently indicate that a different device (or devices) is causing a
problem on the TDM highway.
Procedure
Procedure 26-1 Parity highway 0
1 Refer to the alarm message report; determine the site number, device
identifiers, slot number and cage of the KSW with the parity error.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View menu select State to check the operational
and administrative state of the SITE device.
3 Ensure that the following devices have been reviewed and checked
as potential cause(s) for the KSW fault conditions such as MSI/XCDR,
DRI, GPROC, KSW.
Continued
68P02901W26-S 26-5
Nov 2007
Procedure Chapter 26: KSW Alarms
Procedure 26-1 Parity highway 0 (Continued)

4 Determine whether the entire TDM highway is down or only a block
of timeslots.
If... Then...
the entire TDM highway is down Acknowledge the alarms and
monitor the alarm events/report to
see if the alarm recurs.
If yes, immediately
switch to the redundant
TDM highway (switch
to the redundant KSW).
site to replace the faulty KSW
after it has been established
that the KSW is the only faulty
hardware to be replaced.
If no, go to step 5.
only a block of timeslots are Acknowledge the alarms and
down monitor the alarm events/report
to see if the alarm recurs. The
KSW device has failed.
If yes, determine which

board is responsible for
driving these timeslots. Then,
check the parity set up. If
the parity error recurs,
switch to the redundant KSW.
after it has been established
that the KSW is the only faulty
hardware to be replaced.
If no, go to step 5.
5 Determine whether this alarm was followed by a 254. KSW: Device
Failed alarm.
If this alarm is followed by... Then...
a 254. KSW: Device Failed The KSW device has failed. Swap
alarm to the redundant KSW. Send a
replace the KSW board (and any
other faulty hardware).
no device failed alarm Review the parity set up for each
of the timeslots. Establish the
proper parity set up for any of the
timeslots that are off. Go to step 6.
Continued
26-6 68P02901W26-S
Nov 2007
Procedure 26-1 Parity highway 0 (Continued)

6 Determine whether the KSW is busy_unlocked.
If the KSW is... Then...
busy_unlocked The alarm condition has ceased
and further fault isolation is not
required. Monitor this device
for a recurrence of the alarm
condition. If recurrence of the
alarm is excessive, send a field
replace the KSW.
not busy_unlocked Go to step 7.
7 From the Fault Mgt menu select the Lock option to place the faulty
KSW (and any other faulty devices) Out Of Service (OOS).
8 From the Fault Mgt menu select the Unlock option to bring the
KSW (and the other devices) back In Service (INS).
9 From the View menu again select State to check the operational and
administrative state of the KSW and the TDM highway (0).
replace the KSW.
not busy_unlocked Send a field representative to the
site to replace the KSW.
10 Reset the site after replacing hardware (including cables).

68P02901W26-S 26-7
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway 1.
When this alarm occurs, two KSWs cannot communicate with each other. Each KSW (TSW) is in
a different cage. After each occurrence of this alarm, the site reboots.
This is a KSW firmware alarm; and is therefore, generated according to fault conditions existing
Possible causes

• The KSW may have failed to generate the correct parity set up.
• The KSW may have erroneously detected a problem with the parity bit on TDM expansion
highway 1.
• The physical connection (cabling) is down or malfunctioning.
Procedure
26-8 68P02901W26-S
Nov 2007
1 Refer to the alarm message report; determine the site number,

device identifiers, slot number and cage of the KSW with the parity
error.
3 Determine whether the KSWX is busy_unlocked.
If the Site is... Then...
locate and replace the fiber cable
connecting the KSWXs and/or the
KSWX board(s) if necessary.
site to locate and replace the fiber
cable connecting KSWXs and/or
the KSWX board(s) if necessary.
These KSWXs are in the KSW expansion slots.

4 Reset the site after replacing the hardware (including cables).

68P02901W26-S 26-9
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

highway 2.
Procedure
26-10 68P02901W26-S
Nov 2007

error.
3 Determine whether the KSWX is busy_unlocked.


68P02901W26-S 26-11
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

highway 3.
Procedure
26-12 68P02901W26-S
Nov 2007

error.
3 Determine whether the KSWX is busy_unlocked or not.


68P02901W26-S 26-13
Nov 2007
4. KSW: Clock A signal loss Chapter 26: KSW Alarms
4. KSW: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has detected
a Clock A failure in the system. As a result, the internal (active) clock reference has failed and
may cause the Site to go Out Of Service (OOS) if the redundant clock (GCLK) cannot be accessed.
When this alarm is generated, the KSW switches to the redundant Clock B. However, if Clock
B is not clear of alarms or the clock has been forced to Clock A, the system does not switch
to Clock B.
This fault may be service-affecting. When this fault condition occurs, it may cause the
Site to go Out Of Service (OOS).
Possible causes

• The GCLK KSW extender A card (GCLK/KSWX A) failed.
• The KSW may have faulty receive (Rx) circuitry.
26-14 68P02901W26-S
Nov 2007
Procedure

device identifiers and cage of the failed Clock A device(s).
2 Check the MCAP status register to determine the cause of the
failure.
The failed Clock A device(s) may be one or more of the

following: DRI, KSW or TSW, MSI or XCDR or GCLK.
and administrative state of the SITE.
4 Determine whether the SITE device is in a to busy_unlocked
device state.
5 Determine the troubleshooting procedure as follows.
busy_unlocked Go to the procedure: Site is in a
state on page 26-17.
not busy_unlocked Go to the procedure: Site is not in
state on page 26-15.
Site is not in state
Perform the following procedure when site is not in state.
Procedure 26-6 Site is not in state
1 Wait 10 minutes and use the State option from the View menu to
verify that the SITE device is In Service (INS).
2 If the SITE is not INS, send a field representative to the site to
determine where the hardware or cabling is faulty.
3 If the SITE is INS, use the State option from the View menu to check
the operational and administrative state of all of the device(s) at a
site. Determine whether the site is fully operational.
Continued
68P02901W26-S 26-15
Nov 2007
Procedure 26-6 Site is not in state (Continued)

4 Check which cages and the total number of cages that are Out of
Service (OOS) at the site.
5 Correlate any previous alarms for the devices within a cage. For
example, if a cage experiences clock malfunction, all DRI, KSW
(TSW), MSI/XCDR and GPROC devices in that cage should report a
Clock Failure and/or 6.12 seconds Reference Loss alarm.
If Clock A failure is present Then...
on...
other MCAP slave boards The GCLK/KSWX A has failed.
Ensure no alarms exist on Clock
B.Force the KSW to use the
redundant GCLK/KSWX B if
the hardware has not already
executed the switch. Replace the
GCLK/KSWX A at the site.
no other boards The Clock A detection circuitry
on the KSW has failed.
Ensure no alarms exist on
Clock B. Force the KSW to use
the redundant GCLK/KSWX B if
executed the switch. Switch to the
redundant KSW.
6 Send a field representative to the site to complete the fault diagnosis
procedure on this alarm. Check various cabling, backplane
connections and link-related boards and connections. The remainder
of the procedure requires, replacing GCLKs, CLKXs, fiber cables,
KSWXs and so on.
7 After replacing the hardware items, reset the site; then, verify that
the site is In Service (INS) and has resumed normal operation.
For further detail regarding onsite equipment and repair

procedures see the Maintenance Information: BSS/RXCDR
On Site (68P02901W38) manual.
26-16 68P02901W26-S
Nov 2007

Site is in a state
Perform the following procedure when site is in a state.
Procedure 26-7 Site is in a state
1 Verify that the cage is not Out Of Service (OOS).

2 Refer to the alarm report to determine which cage has the failed
Clock A device(s) from the alarm report.
The failed Clock A device(s) may be one or more of the

(TSW), MSI/XCDR devices in that cage should report a Clock Failure
and/or 6.12 seconds Reference Loss alarm.
If Clock A failure is present Then...
on...
other MCAP slave boards The GCLK/KSWX A has failed.
Ensure no alarms exist on Clock B.
Force the KSW to the redundant
GCLK/KSWX B if the hardware has
not already executed the switch.
Replace the GCLK/KSWX A at the
site.
Continued
68P02901W26-S 26-17
Nov 2007
Procedure 26-7 Site is in a state (Continued)

no other boards The Clock A detection circuitry
on the KSW has failed.
Clock B. Force the KSW to use
the redundant GCLK/KSWX B if
redundant KSW.
KSWXs and so on.
the site is In-Service (INS) and has resumed normal operation.

26-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. KSW: Clock B signal loss
5. KSW: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has detected
a Clock B failure in the system. As a result, the internal (active) clock reference has failed and
may cause the Site to go Out Of Service (OOS) if the redundant clock (GCLK) cannot be accessed.
When this alarm is generated, the KSW switches to the redundant Clock A. However, if Clock
A is not clear of alarms or the clock has been forced to Clock B, the system does not switch
to Clock A.
This fault may be service-affecting. When this fault condition occurs, it may cause the
Site to go Out Of Service (OOS).
Possible causes

• The GCLK KSW extender B card (GCLK/KSWX B) may have failed.
• The KSW may have faulty receive (Rx) circuitry.
68P02901W26-S 26-19
Nov 2007
Procedure

device identifiers and cage of the failed Clock B device(s).
2 Check the MCAP status register to determine the cause of the failure.
The failed Clock B device(s) may be one or more of the

and administrative state of the SITE.
4 Determine whether the SITE device is in a device state.
5 Use the table below to determine which troubleshooting procedure
to follow.
busy_unlocked Go to the procedure: Site is in
a busy_unlocked state on page
26-22.
not busy_unlocked Go to the procedure: Site is not
in busy_unlocked state on page
26-20.
Site is not in busy_unlocked state
Perform the following procedure when site is not in busy_unlocked state.
Procedure 26-9 Site is not in busy_unlocked state
1 Wait 10 minutes and use the State option from the View menu to
verify that the SITE device is In Service (INS).
2 If the SITE is not INS, send a field representative to the site to
determine where the hardware or cabling is faulty.
Continued
26-20 68P02901W26-S
Nov 2007
Procedure 26-9 Site is not in busy_unlocked state (Continued)

3 If the SITE is INS, use the State option from the View menu to check
the operational and administrative state of all of the device(s) at a
site. Determine whether the site is fully operational.
4 Check the total number of cages that are Out of Service (OOS) at
the site.
(TSW), MSI/XCDR and GPROC devices in that cage should report a
Clock Failure and/or 6.12 seconds Reference Loss alarm.
If Clock B failure is present Then...
on...
other MCAP slave boards The GCLK/KSWX B has failed.
A. Force the KSW to use the
redundant GCLK/KSWX A if
GCLK/KSWX B at the site.
no other boards The TDM Clock B detection
circuitry on the MSI (or
XCDR) has failed. Ensure
no alarms exist on Clock A.
Force the KSW to use the
redundant KSW.
KSWXs and so on.
the site is In Service (INS) and has resumed normal operation.
For further detail regarding onsite equipment and repair

procedures see the Maintenance Information: BSS Field
Troubleshooting (68P02901W51) manual.
68P02901W26-S 26-21
Nov 2007

Site is in a busy_unlocked state
Perform the following procedure when site is in a busy_unlocked state.
Procedure 26-10 Site is in a busy_unlocked state
1 Verify that the cage is not Out Of Service (OOS).

2 Refer to the alarm report to determine which cage has the failed
Clock B device(s) from the alarm report.
The failed Clock B device(s) may be one or more of the

(TSW), MSI/XCDR devices in that cage should report a Clock Failure
and/or 6.12 seconds Reference Loss alarm.
If Clock B failure is present Then...
on...
other MCAP slave boards The GCLK/KSWX B has failed.
A. Force the KSW to use the
GCLK/KSWX B at the site.
Continued
26-22 68P02901W26-S
Nov 2007
Procedure 26-10 Site is in a busy_unlocked state (Continued)

no other boards The TDM Clock B detection
circuitry on the MSI
(or XCDR) has failed.
Clock A Force the KSW to use
the redundant GCLK/KSWX A if
redundant KSW.
KSWXs and so on.
the site is In-Service (INS) and has resumed normal operation.

68P02901W26-S 26-23
Nov 2007
6. KSW: 6.12 seconds reference loss Chapter 26: KSW Alarms
6. KSW: 6.12 seconds reference loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected that
the time reference (6.12 seconds reference pulse) has been lost on the Time Division Multiplex
(TDM) highway due to a failed KSW clock extender (GCLK/KSWX) board.
The KSW switches to the redundant clock. However, if the redundant clock is not clear of
alarms or the clock has been forced to the present clock, the system does not switch to the
redundant clock.
This fault may be service-affecting.
Possible causes

• The GCLK KSW extender card (GCLK/KSWX) may have failed.
• The KSW clock detection may have malfunctioned.
26-24 68P02901W26-S
Nov 2007
Procedure
Procedure 26-11 6.12 seconds reference loss

device identifiers, slot number and cage of the faulty GCLK/KSWX.
2 Initiate the appropriate data collection processes (For example,
Performance Management) for troubleshooting purposes.
4 Determine whether the GCLK/KSWX is busy_unlocked or not.
for a recurrence of the alarm.
If recurrence of the alarm is
excessive, go to step 5.
not busy_unlocked Swap to the redundant GCLK
or KSWX. Use the State option
from the View menu to check the
operational and administrative
state of the GCLK/KSWX. If
replacing the GCLK/KSWX did not
correct the fault, switch to the
redundant KSW. Go to step 5.
5 Send a field representative to the site to locate and replace the fiber
cable connecting the GCLK/KSWXs and/or the GCLK/KSWX(s) if
necessary.
6 If replacing the GCLK/KSWX card and cabling does not work, replace
the KSW after verifying that the redundant KSW had been switched
to active status.

68P02901W26-S 26-25
Nov 2007

26-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. KSW: Re-initialized unexpectedly
7. KSW: Re-initialized unexpectedly

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) device was unexpectedly re-initialized or
reset causing the board to fail in the system.
The re-initialization may have been necessary because the KSW may have been functioning
improperly. The software may have detected it or a field representative (onsite) may have reset
the device manually after performing system maintenance.
Possible causes

• The KSW board is reset through the front panel switch, thus, causing the failure.
• The KSW board is reset by the software, thus, causing the failure.
• The processor may have failed.
• One of the peripheral boards related to the MMS may have failed.
Procedure
Wait for a minute for the re-initialization to complete before continuing with this
procedure.
68P02901W26-S 26-27
Nov 2007
Procedure 26-12 Re-initialized unexpectedly
1 Refer to the alarm message report; determine the site number, device
identifiers, slot number and cage of the re-initialized KSW device.
2 From the Navigation Tree, open the Detailed View for the KSW.
From the View menu select State to check the operational and
administrative state of the KSW.
replace the KSW.
not busy_unlocked Wait for the re-initialization
sequence to complete. Use the
INS option from the Fault Mgt
menu for the KSW.
3 From the Fault Mgt menu select the Lock option to place the KSW
Out Of Service (OOS).
KSW back In Service (INS).
busy and unlocked The alarm condition has ceased
replace the KSW.
not busy and unlocked Send a field representative to
the site to replace the KSW. An
additional alarm must have taken
the KSW Out Of Service (OOS).
26-28 68P02901W26-S
Nov 2007

68P02901W26-S 26-29
Nov 2007
8. KSW: Hard reset Chapter 26: KSW Alarms
8. KSW: Hard reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) device is currently undergoing a hard reset
causing the board to fail in the system.
The reset may have been necessary because the KSW may have been functioning improperly.
The software may have detected it or a field representative (on site) may have reset the device
manually after performing system maintenance.
This alarm generates a Motorola Cellular Advanced Processor (MCAP) interrupt message if the
appropriate bit has been set in the interrupt enable register.
Possible causes

• The KSW board is reset through the front panel switch, causing the failure.
• The KSW board is reset by the software, causing the failure.
Procedure
The following procedure can be used to correct the fault and clear the alarm.
procedure.
26-30 68P02901W26-S
Nov 2007

device identifiers, slot number and cage of the reset KSW device.
condition exceeding normal
trends (high frequency and high
volume). If recurrence of the
replace the KSW.
not busy_unlocked Wait for the hard reset sequence
to complete. Go to step 3.
replace the KSW.
site to replace the KSW.
68P02901W26-S 26-31
Nov 2007

26-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. KSW: Watchdog timer expired
9. KSW: Watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) board watchdog timer unexpectedly expired
causing the KSW board to fail in the system.
This hardware alarm generates a Motorola Cellular Advanced Processor (MCAP) interrupt
message if the appropriate bit has been set in the interrupt enable register.
A software reset is required to bring the KSW back into service.
Possible causes

• The firmware may have failed.
• The processor may have failed.
• One of the peripheral boards related to the MMS may have failed.
68P02901W26-S 26-33
Nov 2007
Procedure
procedure.

device identifiers, slot number and cage of the KSW device.
replace the KSW board.
not busy_unlocked Initiate a software reset sequence.
Wait for the reset sequence to
complete. Use the INS option
from the Fault Mgt menu for the
KSW. Go to step 3.
Continued
26-34 68P02901W26-S
Nov 2007
Procedure 26-14 Watchdog timer expired (Continued)

replace the KSW board.
not busy_unlocked Switch to redundant KSW if
fault condition still exists after
the reset is completed. Send a
replace the faulty KSW board.

68P02901W26-S 26-35
Nov 2007
10. KSW: Lost communication with KSW Chapter 26: KSW Alarms
10. KSW: Lost communication with KSW

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) is not responding to Fault Management (FM)
software processes when it attempts to communicate with that KSW.
The system impact of this alarm varies depending on the site configuration. For example, if only
one KSW is equipped at a site, an automatic site reset (re-initialization) occurs.
However, if a site has both a master and a redundant KSW, the redundant device is swapped into
the master KSW role. While the faulty KSW then takes an (inactive) role.
If the (new) master KSW is not equipped in an expanded TDM configuration, calling
capacity for that site is reduced or the site is reset.
Possible causes

• The KSW Extender (KSWX) card is faulty.
• The Motorola Cellular Advanced Processor (MCAP) Bus on the backplane may have failed.
• The MCAP master Generic Processor (GPROC) may have failed.
• The KSW may have failed.
26-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Clearing the alarm
Clearing the alarm
Procedure
If the alarm occurs, perform the following procedure:
Procedure 26-15 Lost communication with KSW

3 Check for the presence of other related alarms at the same site:
• 232. KSW: Processor Bus Communication Failure.
• 232. GPROC: Processor Bus Communication Failure.

4 If other alarm(s) are present, follow the respective troubleshooting
procedure(s) in this manual to resolve any fault conditions related to
any of the alarms above.
5 Determine if the site has been reset.
• If yes, wait for the reset to complete before continuing to the

next step.
6 Determine whether the reset was successful by checking the SITE
device state:
• In a TTY window, execute the state 0 SITE <device ids>

command.
7 What is the device state displayed in the command output for the
state 0 SITE <device ids> command.
• If the SITE device state is busy_unlocked. Cease fault isolation

activities.
• If the SITE device state is disabled_unlocked. go to step 8.
Continued
68P02901W26-S 26-37
Nov 2007
Procedure 26-15 Lost communication with KSW (Continued)

8 Is there a redundant KSW present at the site.
If redundancy is... Then...
present The faulty KSW should
have automatically swapped
to an inactive role. It
is in a disabled_unlocked
state at this point.
Refer to the Note.
not present The faulty KSW should have
resumed normal service
in a busy_unlocked state.
In order for the faulty KSW to assume a redundant

role, the operator must try to bring the KSW into an
enabled_unlocked state after it has been swapped into an
inactive role. This can be accomplished by entering the
INS command for the KSW in the Alarm window to bring
the device back In Service (INS).
Continued
26-38 68P02901W26-S
Nov 2007
Procedure 26-15 Lost communication with KSW (Continued)

9 Determine whether the KSW(s) are functioning properly.
From the View menu select State to verify that the master KSW (and
redundant, if present) are functioning in the proper device state(s).
busy_unlocked The master KSW is functioning
properly. If a redundant KSW
is present, it should be in an
enabled_unlocked state. Check
if the redundant KSW is in
the correct device state.
If yes, cease fault

isolation activities.
If no, use the INS option

from the Fault Mgt menu to
bring the redundant KSW into
If the KSW does not

come into an enabled_unlocked
state, go to step 10.
enabled_unlocked The faulty KSW has been
swapped to the redundant role
and is functioning properly.
Or the master KSW is in an
incorrect device state. The
master should be busy_unlocked.
Check if the master KSW is in
If yes, cease fault isolation

activities.
If no, use the INS

option from the Fault Mgt
menu to bring the KSW into
If the master KSW does

not come into an busy_unlocked
10 Send a field representative to the site to investigate and, if necessary,
replace any faulty hardware such as KSW, KSWX, GPROC and so on.
68P02901W26-S 26-39
Nov 2007

26-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11 KSW: Local cage KSW TDM loopback test failure
11 KSW: Local cage KSW TDM loopback test failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that over 50% of the local cage Time Division Multiplex (TDM) loopback
tests that have been generated have failed. These loopback tests encompass all of the GPROCs
and the active KSW in the same (local) cage.
Possible causes

• The KSW may have failed.
• The TDM Bus may have failed.
Clearing the alarm
The BSS attempts to clear this alarm automatically through a Fault Management Initiated
Clear (FMIC) after the fault condition has been resolved. The KSW must be placed In Service
(INS) before this alarm can clear.
68P02901W26-S 26-41
Nov 2007
Procedure
Procedure 26-16 Local cage KSW TDM loopback test failure

3 Check for the presence of other related alarms at the same site:
• 232. KSW: Processor Bus Communication Failure.
• 232. GPROC: Processor Bus Communication Failure.

4 If other alarm(s) are present, follow the respective troubleshooting
procedure(s) in this manual to resolve any fault conditions related to
any of the alarms in step 3.
5 Check if there is a redundant KSW present at the site.
If redundancy is... Then...
present The faulty KSW should have
automatically swapped to
an inactive role. It is in a
disabled_unlocked state at this
point.
not present The faulty KSW should have
resumed normal service in a
busy_unlocked state.
Continued
26-42 68P02901W26-S
Nov 2007
Procedure 26-16 Local cage KSW TDM loopback test failure (Continued)
6 Determine whether the KSW(s) are functioning properly.
Execute the state command to verify that the master KSW (and
redundant, if present) are functioning in the proper device state(s).
busy_unlocked The master KSW is
functioning properly.
If a redundant KSW is
present, it should be in an
enabled_unlocked state.
Check if the redundant KSW is in
If yes, cease fault

If no, use the INS

option from the Fault Mgt menu
to bring the redundant KSW into
If the KSW does not

come into an enabled_unlocked
enabled_unlocked The faulty KSW has been
swapped to the redundant role
and is functioning properly.
Or the master KSW is in an
incorrect device state. The
master should be busy_unlocked.
Check if the redundant KSW is in
If yes, cease fault

If no, use the INS

option from the Fault Mgt
menu to bring the KSW into
If the master KSW does

not come into an busy_unlocked
7 Send a field representative to the site to investigate and, if necessary,
replace any faulty hardware such as KSW, KSWX, GPROC and so on.
68P02901W26-S 26-43
Nov 2007

26-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 18 - 21. KSW: Failure of expanded inbound TDM highway
18 - 21. KSW: Failure of expanded inbound TDM

highway
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the Expanded Time Division Multiplex (TDM) device test audit has
detected that a specific KSW has failed to communicate with the other KSW pairs through the
correct (expansion mode) KSWXs.
This fault condition adversely affects system performance within the Time Division Multiplex
(TDM) matrix. In this case, the inbound portion of the (active) expanded Time Division Multiplex
(TDM) highway (to the specific KSW) has been compromised.
This alarm is generated only for BSC and InCell equipment.
TDM matrix
Expansion mode is used to provide communication across the TDM matrix. The TDM matrix
consists of an array of all the KSWs and the respective (assigned) portions of the TDM Highway
displaying the interconnections between KSWs within the TDM Highway.
Expanded TDM test audit limitation
During initialization, the In Service (INS) TDM highway (matrix) is automatically tested for both
active and standby TDM highways.
After the initialization has been completed, the Expanded TDM highway can be tested by using
the device_audit command for the active TDM device.
To test the standby TDM highway after initialization, that (standby) TDM device must be
swapped into the active role. Execute the swap_device command to switch the standby TDM
into the active role (busy_unlocked). Then, proceed with the test.
68P02901W26-S 26-45
Nov 2007
Additional information eld Chapter 26: KSW Alarms
KSW pairs 0 through 3 are described
This alarm description applies to the Expanded Inbound TDM Highway failure alarms for the
four KSW pairs: 0, 1, 2 and 3. The alarm name displays the KSW pair number related to the
fault condition. There are four separate alarms.
The additional information in the output for this alarm displays the slot number of the KSW
Extender (KSWX) card to which the expanded inbound TDM highway is connected.
Possible causes

• The (fiber) connections between expansion mode KSWXs is incorrectly set up (onsite).
• The expansion mode KSWX software configuration is incorrect due to an erroneous value
being entered for the Configuration Management (CM) ksw_config database parameter.
• The fiber connections between expansion mode KSWX cards are faulty.
• An expansion mode KSWX card is faulty.
• The KSW card is faulty.
Clearing the alarm
The BSS attempts to clear this alarm automatically through a Fault Management Initiated
Clear (FMIC) after the fault condition has been resolved and a successful TDM device test
audit has been completed.
Procedure
If this alarm occurs, perform the following procedure:
Procedure 26-17 KSW: Failure of expanded inbound TDM highway
1 Refer to the alarm message report to check for other expansion

mode hardware alarms that may be related to this failure: Cage
alarms (14-19) or KSW alarms (12-17).
Continued
26-46 68P02901W26-S
Nov 2007
Procedure 26-17 KSW: Failure of expanded inbound TDM highway (Continued)

2 If any (expansion mode) KSW or CAGE alarms have been generated,
determine whether the KSWX related to the other fault condition
uses the same KSW pair that is shown to be related to this alarm.
• If yes, resolve the other (related) fault conditions before

continuing.
3 Execute the disp_element ksw_config command to verify that the
current ksw_config (CM) database parameter settings are correct.
If fault appears to be in... Then...
CM database parameter Send a field representative
setting(s) to the site to compare (and
contrast) CM parameter settings.
The settings displayed in the
output of the disp_element
ksw_config command must be
compared to the actual onsite
configuration. This establishes
whether the KSWX fiber and
connections are correct.
hardware or equipment Send a field representative to the
site to check board connections;
reconfigure and/or replace any
faulty equipment.

68P02901W26-S 26-47
Nov 2007
22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure Chapter 26: KSW Alarms
22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected

expanded KSW matrix failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that a Kiloport Switch Extender card (KSWX/DSWX) residing within the
specified Expansion mode slot (7-9) has detected that the expanded KSW matrix has failed.
This alarm is generated when the KSWX/DSWX is no longer receiving TDM data from another
expansion mode KSWX/DSWX. This fault condition adversely affects system performance within
the Time Division Multiplex (TDM) matrix.
Expansion mode
A KSWX/DSWX operating in Expansion mode is used to expand the TDM highway by connecting
two different KSWs that are controlling two distinct parts of the TDM Highway. Fiber optic
links are used.
The TDM Highway is divided into four portions. Each portion is controlled by a different KSW.
Each KSW is capable of operation independently of the other KSWs. However, it is necessary to
exchange data across the four portions of the TDM highway using fiber optic links.
As a result, expansion mode is used to provide communication across the TDM matrix. The TDM
matrix consists of an array of all the KSWs and the respective (assigned) portions of the TDM
Highway displaying the interconnections between KSWs within the TDM Highway.
The KSWX/DSWX expands the TDM highway from the associated KSW (in the same cage)
to the related KSWX/DSWX in an expanded cage. While in expansion mode, a KSWX/DSWX
is dependent upon its associated KSW (in either the same cage or the expanded cage) for
successful operation.
If the associated KSW goes Out Of Service (OOS), the KSWX/DSWX is not monitored for faults.
In addition, any alarms that are related to the KSWX/DSWX is not cleared from the system
even when a fault condition has been resolved.
26-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Additional information eld
KSWX/DSWX cards for slots 7 through 9 are described
This alarm description applies to the KSWX/DSWX matrix failure alarms for three KSWX/DSWX
cards in slots 7, 8 and 9. The alarm name displays the slot number of the KSWX/DSWX card
related to the fault condition. There are three separate alarms.
Possible causes

• The fiber connections between KSWX/DSWX cards is faulty.
• A corresponding KSWX/DSWX card in another cage is faulty.
Clearing the alarm
Procedure
Procedure 26-18 KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure
1 Refer to the alarm message report to check for the slot number of
the KSWX/DSWX for which this alarm is being generated.
2 Send a field representative to the site to check fiber cables, fiber
connections and/or faulty KSWX/DSWX cards. Verify that the toggle
switch on the KSWX/DSWX is in the middle (enabled) position.
Re-insert cards, reconnect, enable and/or replace faulty equipment
when necessary.
This alarm clears within 10 seconds of correcting the fault

condition.
68P02901W26-S 26-49
Nov 2007

26-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25 - 27. KSW:
KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure
25 - 27. KSW: KSWX/DSWX in Slot 21-23 detected

expanded KSW matrix failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that a Kiloport Switch Extender card (KSWX/DSWX) residing within the
specified Expansion mode slot (21-23) has detected that the expanded KSW matrix has failed.
This alarm is generated when the KSWX/DSWX is no longer receiving TDM data from another
expansion mode KSWX/DSWX. This fault condition adversely affects system performance within
the Time Division Multiplex (TDM) matrix.
Expansion mode
A KSWX/DSWX operating in Expansion mode is used to expand the TDM highway by connecting
two different KSWs that are controlling two distinct parts of the TDM Highway. Fiber optic
links are used.
The TDM Highway is divided into four portions. Each portion is controlled by a different KSW.
Each KSW is capable of operation independently of the other KSWs. However, it is necessary to
exchange data across the four portions of the TDM highway using fiber optic links.
As a result, expansion mode is used to provide communication across the TDM matrix. The TDM
matrix consists of an array of all the KSWs and the respective (assigned) portions of the TDM
Highway displaying the interconnections between KSWs within the TDM Highway.
The KSWX/DSWX expands the TDM highway from the associated KSW (in the same cage)
to the related KSWX/DSWX in an expanded cage. While in expansion mode, a KSWX/DSWX
is dependent upon its associated KSW (in either the same cage or the expanded cage) for
successful operation.
If the associated KSW goes Out Of Service (OOS), the KSWX/DSWX is not monitored for faults.
In addition, any alarms that are related to the KSWX/DSWX is not cleared from the system
even when a fault condition has been resolved.
68P02901W26-S 26-51
Nov 2007
Additional information eld Chapter 26: KSW Alarms
KSWX/DSWX cards for slots 21 through 23 are described
This alarm description applies to the KSWX/DSWX matrix failure alarms for three KSWX/DSWX
cards in slots 21, 22 and 23. The alarm name displays the slot number of the KSWX/DSWX card
related to the fault condition. There are three separate alarms.
Possible causes

• The fiber connections between KSWX/DSWX cards is faulty.
• A corresponding KSWX/DSWX card in another cage is faulty.
Clearing the alarm
Procedure
Procedure 26-19 KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure
1 Refer to the alarm message report to check for the slot number of
the KSWX/DSWX for which this alarm is being generated.
2 Send a field representative to the site to check fiber cables, fiber
connections land/or faulty KSWX/DSWX cards. Verify that the toggle
switch on the KSWX/DSWX is in the middle (enabled) position.
Re-insert cards, reconnect, enable and/or replace faulty equipment
when necessary.
This alarm clears within 10 seconds of correcting the fault

condition.
26-52 68P02901W26-S
Nov 2007

68P02901W26-S 26-53
Nov 2007
224. KSW: Safe test audit failure Chapter 26: KSW Alarms
224. KSW: Safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that a Kiloport Switch (KSW) board has failed the safe test audit generated
by the System Audit Process (SAP) portion of the Fault Management (FM) software in the system.
If the results of the audit reveal that the audit performed on the KSW was not completed,
this alarm is reported.
Safe Audit Tests use the inter-process messages to interrogate the target hardware device.
The tests determine the sanity of the processor in each of the intelligent boards and the
communication link which carries the audit messaging protocol (basic Ack handshake). These
tests are not service affecting.
Safe Test Audit does not take the device Out Of Service (OOS) or interrupt its primary
functionality.
Possible causes

• The KSW board software is not functioning correctly.
• The MCAP interface software is not functioning correctly.
• The MCAP bus is faulty.
• A hardware problem on the KSW board may have prevented the KSW from responding
properly to the audit.
• A Loss of power to the KSW board may have prevented it from responding to the audit.
26-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Clearing the alarm
Clearing the alarm
The BSS attempts to clear this alarm automatically through the Fault Management Initiated
Clear (FMIC) after this fault condition has been resolved.
Procedure

device identifiers, slot number and cage of the faulty KSW device.
If the KSW has... Then...
resumed normal functioning The alarm condition has
ceased and further fault
isolation is not required.
Monitor this device for a
recurrence of the alarm condition.
If the fault reappears, continue
with this procedure.
not resumed normal functioning Go to step 4.
busy_unlocked The alarm condition has
ceased and further fault
Monitor this device for a
If recurrence of the alarm
is excessive, send a field
replace the faulty KSW board.
board.
68P02901W26-S 26-55
Nov 2007

26-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 225. KSW: Internal loopback audit failure
225. KSW: Internal loopback audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has failed
the loopback test audit generated by the System Audit Process (SAP) portion of the Fault
Management (FM) software in the system.
If the results of the audit reveal that the audit performed on the KSW was not completed,
this alarm is reported. This alarm is generated as a result of the system audit KSW (TSW)
internal loopback failure.
This Loopback Test audit involves sending a command to a hardware entity instructing it,
to perform internal loopback tests (within itself). After completing the tests, the hardware
automatically returns the test result for fault handling (For example, local TDM bus loopback
through the KSW).
This alarm is not generated again even if the audit fails because Operator Initiated
Clear (OIC) alarms are reported only once by Fault Management software.
Possible causes

• The KSW/TSW board software is not functioning correctly.
• The Time Division Multiplex Bus (TBUS) is faulty.
• A hardware problem on KSW/TSW board may have prevented the KSW/TSW from
responding properly to the audit.
• A loss of power to KSW/TSW board may have prevented it from responding to the audit.
68P02901W26-S 26-57
Nov 2007
Clearing the alarm Chapter 26: KSW Alarms
Clearing the alarm
This is an Operator Initiated Clear (OIC) alarm that must be cleared by the operator after the
fault condition has been resolved.
Procedure
If the alarm recurs, perform the following procedure:
Procedure 26-21 Internal loopback audit failure
1 Check the alarm report or display the current event messages to

determine whether the alarm has ceased.
• If the alarm has ceased, discontinue further fault isolation.
• If the alarm is still active, go to step 2.

device identifiers, slot number and cage of the faulty KSW/TSW
device. (Also, check to see if GPROCs alarms are being generated).
4 From the Navigation Tree, open the Detailed View for the KSW/TSW.
administrative state of the KSW/TSW.
5 Execute the cage_audit command to set up (schedule) another run
of the internal loopback audit test.
If the KSW/TSW loopback Then...
audit is...
successful The alarm condition has ceased
required. Monitor this device for a
If the fault reappears, continue
with this procedure. Go to step 6.
unsuccessful Go to step 6.
6 Send a field representative to the site to locate and be prepared to
replace any of the following items: KSW/TSW board and GPROCs in
the KSW cage.
26-58 68P02901W26-S
Nov 2007

68P02901W26-S 26-59
Nov 2007
232. KSW: Processor bus communication failure Chapter 26: KSW Alarms
232. KSW: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that a Kiloport Switch (KSW) device has lost the ability to communicate to
the GPROC through the Motorola Cellular Advanced Processor (MCAP) Bus.
Possible causes

• The KSW and/or the GPROC board is removed from the shelf.
• The portion of the KSW and/or the GPROC board that supports the MCAP bus access
has failed.
Clearing the alarm
26-60 68P02901W26-S
Nov 2007
Procedure

If this alarm is received Then...
with...
254. KSW: Device Failed alarm The KSW device has failed.
In a TTY window, use the
swap command to switch the
redundant KSW to active status.
site to replace the faulty KSW.

and further fault isolation is
not required. Monitor this
device for a recurrence of the
alarm condition. If the alarm
recurrence is excessive, send a
replace the KSW.
Continued
68P02901W26-S 26-61
Nov 2007
Procedure 26-22 Processor bus communication failure (Continued)

not busy_unlocked Attempt to bring the KSW/TSW
back into service by locking and
unlocking the device:
• Use the Lock option from the

Fault Mgt menu to place the
KSW Out Of Service (OOS).
• Use the Unlock option from

the Fault Mgt menu to bring
the KSW back In Service
(INS).
• Use State from the View

menu to check the operational
and administrative state of
the faulty KSW.
If the device is back in
service the alarm condition
has ceased and further fault
If the device remains OOS,
go to step 5.
5 Execute the swap command to switch the redundant KSW to active
status.
6 Send a field representative to the site to replace the faulty KSW
board.

26-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. KSW: Device failure
254. KSW: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A functioning Kiloport Switch (KSW) device has failed.
The Fault Management (FM) software requested that this specific device be removed from
service. As a result, the KSW is automatically placed Out Of Service (OOS).
This fault can be service affecting. At all times, a site must have at least one
functioning KSW. Otherwise, the site goes OOS.
Possible causes
This device failed as a result of a problem (with this device) that was detected by another
device, which then reported the failure.
Clearing the alarm
68P02901W26-S 26-63
Nov 2007
Procedure

device identifiers, slot number and cage of the faulty KSW device.
4 Determine whether the KSW is busy_unlocked or not.
required. Monitor this device for a
If recurrence of the alarm is
excessive, go to step 5.
not busy_unlocked Attempt to bring the KSW/TSW
back into service by locking and
unlocking the device:
• Use the Lock option from the

Fault Mgt menu to place the
KSW Out Of Service (OOS).
• Use the Unlock option from

the Fault Mgt menu to bring
the KSW back In Service
(INS).
• Use State from the View

menu to check the operational
and administrative state of
the faulty KSW.
If the device is back in
service the alarm condition
has ceased and further fault
If the device remains OOS,
go to step 5.
5 Execute the swap command to switch the redundant KSW to active
status.
6 Send a field representative to the site to replace the faulty KSW
board.
26-64 68P02901W26-S
Nov 2007

68P02901W26-S 26-65
Nov 2007
26-66 68P02901W26-S
Nov 2007
Chapter
27
LAN Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details LAN alarms and includes the following alarm procedures:
• 0. LAN: Lan 0 on page 27-3.
• 1. LAN: LAN failure on page 27-5.
68P02901W26-S 27-1
Nov 2007
Introduction to LAN alarms Chapter 27: LAN Alarms
Introduction to LAN alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
LAN alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Local Area
Network (LAN) device.
The LAN alarms are generated when a fault condition occurs and is detected by the LAN
Monitor Process (LMP). The LMP is located on the Generic Processor (GPROC) that is connected
to the LAN.
27-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. LAN: Lan 0
0. LAN: Lan 0
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The LAN Monitor Process was unable to swap LAN devices when the active LAN device failed
because the standby LAN device was already OOS.
This fault is service affecting. It causes the site to reset.
Possible causes

• The standby LAN was OOS when the active LAN failed.
• The LAN fiber optic cabling was cut.
68P02901W26-S 27-3
Nov 2007
Procedure Chapter 27: LAN Alarms
Procedure
Determine the state of the site. Perform the following procedure to resolve the alarm.
Procedure 27-1 Lan 0

busy_unlocked The fault condition
no longer exists.
If this is a recurrence of this
to the site to determine the cause
action.

27-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. LAN: LAN failure
1. LAN: LAN failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates a loss of LAN redundancy at the time the alarm was generated. This can
be caused by:
• The redundant LAN device failed to respond when polled by the LAN Monitor Process
(LMP). In this situation the system tries to change the state of the device to re-establish
LAN redundancy. The LANX board remains OOS if a fault condition exists.
• The LMP detected that the active LAN device failed and a swap to the redundant LAN has
immediately been implemented. The failed LAN is now in the role of the redundant device
and the system therefore tries to change the state of the device to re-establish redundancy.
The LANX board remains OOS, if a fault condition exists.
In both cases, the OMC-R alarm logs reflect a state change for the redundant LAN device from
enabled unlocked (E/U) to disabled unlocked (D/U). If redundancy is successfully re-established,
the state then changes back to E/U.
System action
Depending on the circumstances described above, the system swaps the failed active LAN with
the standby LAN and/or tries to re-establish LAN redundancy.
68P02901W26-S 27-5
Nov 2007
Possible causes Chapter 27: LAN Alarms
Possible causes

• A GPROC failed causing the LAN to go OOS.
• A GPROC was reset by pressing the front panel switch or by software.
• A GPROC was removed from the cage.
• The LAN or LANX boards failed.
• The LAN fiber optic cabling was cut.
• LAN overloaded with messages at the time.
Procedure
Procedure 27-2 LAN failure
1 Determine if the alarm was reported for the active LAN or the
standby LAN.
If the alarm is reported for Then...
the...
active LAN Go to step 2.
standby LAN Go to step 3.
2 Determine the state of the active LAN device.
If the LAN is... Then...
to the site to determine the cause
action.
27-6 68P02901W26-S
Nov 2007

68P02901W26-S 27-7
Nov 2007
Procedure Chapter 27: LAN Alarms
27-8 68P02901W26-S
Nov 2007
Chapter
28
LMTL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Local Message Transfer Link (LMTL) alarms are covered in this chapter and includes the
following alarm procedures:
• 0. LMTL: Signaling link failure on page 28-3.
• 0. LMTL: SL failure - All reasons - PM on page 28-6.
• 1. LMTL: SMLC processor outage on page 28-8.
• 1. LMTL: Threshold reached: SL failure - abnormal FIBR/BSNR - PM on page 28-10.
• 2. LMTL: Threshold reached: SL failure - excessive delay of ACK - PM on page 28-12.
• 3. LMTL: Link traffic too high on page 28-14.
• 3. LMTL: Threshold reached: SL failure - excessive error rate - PM on page 28-16.
• 4. LMTL: Threshold reached: SL failure - excessive duration of congestion - PM on page

28-18.
• 5. LMTL: Threshold reached: SL alignment failure - PM on page 28-20.
• 6. LMTL: Threshold reached: Number of signal units in error - PM on page 28-22.
• 7. LMTL: Threshold reached: SL number of negative ACKs received - PM on page 28-24.
• 8. LMTL: Threshold reached: Start of remote processor outage - PM on page 28-26.
• 9. LMTL: Threshold reached: Number of octets retransmitted - PM on page 28-28.
• 10. LMTL: Threshold reached: MSUs discarded due to SL congestion - PM on page 28-29.
• 11. LMTL: SL congestion events resulting in loss of MSUs - PM on page 28-30.
• 12. LMTL: Threshold reached: SL congestion indications - PM on page 28-32.
68P02901W26-S 28-1
Nov 2007
Introduction to LMTL alarms Chapter 28: LMTL Alarms
Introduction to LMTL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
LMTL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the
Local Message Transfer Link (LMTL) device.
The LMTL device provides the 64 kbps connection between the SMLC and the BSC. The
connection exists on a timeslot on the MMS device. The connection supports the ITU-TSS
Signaling System 7 MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part)
protocols with the variations specified by GSM.
28-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. LMTL: Signaling link failure
0. LMTL: Signaling link failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 0 alarm.
See 0. MTL: Signaling Link Failure.
The BSS reports an LMTL Signaling Link Failure alarm when the E1 link supporting the LMTL
goes out of service. An LMTL connection between the SMLC and BSC has failed. No signaling
information is passed between the SMLC and BSC over the disconnected link.
This is a service-affecting fault if the last functioning LMTL link is placed OOS. If
another link exists, this is not a service-affecting fault.
The BSS clears an LMTL Signaling Link Failure alarm when the E1 link supporting the
LMTL returns to service.
Last LMTL link disconnected
If no other LMTL links are in service when this alarm is reported, the Last LMTL Link Failure
- Signaling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS
is placed OOS.
Table 28-1 Additional information eld content

first 00 to FF MMS timeslot.
second 0A MMS device type.
third fourth fifth 00 to FF00 to FF00 to MMS device
FF identifiers.
68P02901W26-S 28-3
Nov 2007
Possible causes Chapter 28: LMTL Alarms
Possible causes

• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) causing the link failure.
• The remote congestion timer expired.
• The MSI acknowledgment timer expired.
• The sequence numbers are not synchronized.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive signaling error rate.
Procedure
Procedure 28-1 Signaling link failure

If... Then...
rebooting
required.
not cleared The fault is at the MSC. Contact
the MSC to resolve the fault.
3 Determine if the RXCDR returned to service.
If the RXCDR... Then...
returned to service Go to step 4.
did not return to service Troubleshoot the RXCDR fault.
Continued
28-4 68P02901W26-S
Nov 2007
Procedure 28-1 Signaling link failure (Continued)

4 Reset the LMTL device.
5 Determine the state of the LMTL.
If the LMTL is... Then...
required.
6 Determine if there are alarms for the associated MMS or MSI
devices.
MMS or MSI alarms Resolve the MMS or MSI alarms.
no MMS or MSI alarms Send a field representative to the
site to investigate the E1 links.

68P02901W26-S 28-5
Nov 2007
0. LMTL: SL failure - All reasons - PM Chapter 28: LMTL Alarms
0. LMTL: SL failure - All reasons - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
See 0. MTL: SL Failure - All Reasons - PM.
The BSS reports an LMTL SL Failure - All Reasons - PM alarm when the LMTP_SL_FAIL
counter exceeds the specified threshold.
The LMTP_SL_FAIL statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) has failed for all causes excluding
operator interaction using the MMI.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Possible causes
An MSI failed.
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
28-6 68P02901W26-S
Nov 2007
Procedure 28-2 SL failure - All reasons - PM
If MSI alarms are... Then...

reported Resolve the MSI alarms and then
clear this alarm.
not reported Clear the alarm.
68P02901W26-S 28-7
Nov 2007
1. LMTL: SMLC processor outage Chapter 28: LMTL Alarms
1. LMTL: SMLC processor outage

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Refer 1. MSC Processor Outage.
The BSS reports an LMTL SMLC Processor Outage alarm when the remote SMLC processor
for the LMTL goes out of service.
The MSC processor is OOS. This processor failure causes the LMTL link to be blocked. When
the LMTL link is blocked, no user signaling traffic can be exchanged.
This is a service-affecting fault.
The BSS clears an LMTL SMLC Processor Outage alarm when the remote SMLC processor for
the LMTL comes back into service.
Possible causes
The SMLC processor for the remote MTP layer 2 link(s) malfunctioned or failed.
28-8 68P02901W26-S
Nov 2007
Procedure
Procedure 28-3 SMLC processor outage
Send a field representative to the site to replace the SMLC.

68P02901W26-S 28-9
Nov 2007
1. LMTL: Threshold reached: SL failure - abnormal FIBR/BSNR - PM Chapter 28: LMTL Alarms
1. LMTL: Threshold reached: SL failure - abnormal

FIBR/BSNR - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 1. MTL: SL Failure - FIBR/BSNR - PM.
The BSS reports an LMTL SL Failure - Abnormal FIBR/BSNR - PM alarm when the
LMTP_SL_FIBR counter exceeds the specified threshold.
The LMTP_SL_FIBR statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) is lost due to the detection of
an abnormal Forward Indicator Bit (FIB) caused by the de-synchronization of the Backward
Sequence Number (BSN) and Forward Sequence Number (FSN).
Possible causes
The BSN and FSN are being corrupted by the MSC.
28-10 68P02901W26-S
Nov 2007
Procedure
Determine if any BSN and FSN are being corrupted by the MSC. Perform the following
procedure to resolve the alarm.
Procedure 28-4 Threshold reached: SL failure - abnormal FIBR/BSNR - PM
If the BSN and FSN are... Then...

being corrupted by the MSC Contact the MSC to resolve the
problem and then clear this alarm.
not being corrupted by the MSC Clear the alarm.
68P02901W26-S 28-11
Nov 2007
2. LMTL: Threshold reached: SL failure - excessive delay of ACK - PM Chapter 28: LMTL Alarms
2. LMTL: Threshold reached: SL failure - excessive

delay of ACK - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 2. MTL: SL Failure - Excessive Delay of ACK - PM.
The BSS reports an LMTL SL Failure - Excessive Delay of ACK - PM alarm when the
LMTP_SL_ACK counter exceeds the specified threshold.
The LMTP_SL_ACK statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the system failed
to acknowledge a Message Signal Unit (MSU) before an internal Motorola defined timer expired.
Possible causes
A signaling link failed and an MSU acknowledgment has not been sent.
28-12 68P02901W26-S
Nov 2007
Procedure
Determine if the MSU is sent by the MSC. Perform the following procedure to resolve the alarm.
Procedure 28-5 Threshold reached: SL failure - excessive delay of ACK - PM
If the MSU is... Then...

being sent A communication link may
be faulty. Resolve the
communications link fault,
then clear this alarm.
not being sent Contact the MSC to resolve the
68P02901W26-S 28-13
Nov 2007
3. LMTL: Link trafc too high Chapter 28: LMTL Alarms
3. LMTL: Link trafc too high

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 3. MTL: Link Traffic Too High.
The BSS reports an LMTL Link Traffic Too High alarm when the LMTL software process
becomes over congested.
Congestion is detected at either the local or remote end of the LMTL affecting the flow of the
signaling traffic across MTP Layer 2.
This is potentially a service-affecting fault.
This alarm does not necessarily indicate that there is a physical problem with the LMTLs.
A network congestion problem is probably causing the LMTL links to experience signaling
congestion.
System action
After the alarm is reported, flow control procedures are started at the MTP Layer 2 level to
handle congestion. These procedures ensure that user messages are stored in an MTP Layer
2 buffer for transmission when the signaling traffic subsides and returns to a normal level of
activity. When MTP Layer 2 has used all of its buffer space, user messages are discarded.
Possible causes
High traffic levels on the LMTL do not allow enough time for the device driver to process frames.
28-14 68P02901W26-S
Nov 2007
Procedure
Procedure 28-6 Link trafc too high
1 Determine if any LMTL devices are OOS.

2 Reset each OOS LMTL device.
return to service The fault condition no longer
exists. Clear the alarm.
do not return to service Resolve the Signaling Link Failure
(LMTL 0) alarm for the LMTL
device(s) that do not return to
service and then clear this alarm.
3 Clear the alarm. The alarm is due to congestion. The capacity of the
current LMTL links is insufficient to handle the signaling traffic. If
this alarm recurs, capacity must be increased by the addition of
LMTL links.
68P02901W26-S 28-15
Nov 2007
3. LMTL: Threshold reached: SL failure - excessive error rate - PM Chapter 28: LMTL Alarms

error rate - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 3. LMTL: SL Failure - Excessive Error Rate - PM.
The BSS reports an LMTL SL Failure - Excessive Error Rate - PM alarm when the
LMTP_SL_ERROR_RATE counter exceeds the specified threshold.
The LMTP_SL_ERROR_RATE statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the Signal Unit
Error Rate Monitor (SUERM) timer expired.
Possible causes
An MSI failed.
28-16 68P02901W26-S
Nov 2007
Procedure
Procedure 28-7 Threshold reached: SL failure - excessive error rate - PM

clear this alarm.
68P02901W26-S 28-17
Nov 2007
4. LMTL: Threshold reached: SL failure - excessive duration of congestion - PM Chapter 28: LMTL Alarms

duration of congestion - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This alarm relates to the Lb-interface, but in all other respects is identical to the LMTL 4 alarm.
Refer 4. LMTL: SL Failure - Excessive Duration of Congestion - PM.
The BSS reports an LMTL SL Failure - Excessive Duration of Congestion - PM alarm when
the LMTP_REMOTE_SL_CONGESTION counter exceeds the specified threshold.
The LMTP_REMOTE_SL_CONGESTION statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the remove
congestion timer expired. This congestion condition occurs on the SL when the threshold levels
establishing the capacity of the transmission or re-transmission buffer of a Message Signal
Unit (MSU) are reached.
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
28-18 68P02901W26-S
Nov 2007
Procedure
Procedure 28-8 Threshold reached: SL failure - excessive duration of congestion

- PM
1 Clear the alarm.

2 The alarm is due to the duration of a congestion condition that exceeds the
capacity of the LMTL links to handle the signaling traffic.
3 If this alarm recurs, capacity must be increased by the addition of LMTL
links.
68P02901W26-S 28-19
Nov 2007
5. LMTL: Threshold reached: SL alignment failure - PM Chapter 28: LMTL Alarms
5. LMTL: Threshold reached: SL alignment failure - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 5. MTL: SL Alignment Failure - PM.
The BSS reports an LMTL SL Alignment Failure - PM alarm when the LMTP_SL_ALIGNMENT
counter exceeds the specified threshold.
The LMTP_SL_ALIGNMENT statistic threshold has been reached.
This statistic monitors the system to detect when a Signaling Link (SL) has attempted to align
with the A-Interface while the interface is OOS. This fault condition occurs when the alignment
has been lost.
Possible causes

• The A-interface physical connection is missing.
• A hardware failure caused a loss of the A-Interface.
• The MSC is experiencing a power outage caused the A-Interface to be lost.
• The SL is OOS.
28-20 68P02901W26-S
Nov 2007
Procedure
Determine if other alarms associated with the SL were reported. Perform the following
Procedure 28-9 Threshold reached: SL alignment failure - PM
If other alarms are... Then...

reported Resolve the alarms and then clear
this alarm.
68P02901W26-S 28-21
Nov 2007
6. LMTL: Threshold reached: Number of signal units in error - PM Chapter 28: LMTL Alarms
6. LMTL: Threshold reached: Number of signal units

in error - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 6. MTL: Number of Signals Units in Error - PM.
The BSS reports an LMTL Number of Signals Units in Error - PM alarm when the
LMTP_SU_ERROR counter exceeds the specified threshold.
The LMTP_SU_ERROR statistic threshold has been reached.
This statistic counts the number of times that an erroneous Signaling Unit (SU) is received
on the Signaling Link (SL).
Possible causes

• The BSN and FSN are corrupted.
• A Multiple Serial Interface (MSI) failed.
• A Generic Clock (GCLK) failed.
28-22 68P02901W26-S
Nov 2007
Procedure
Procedure 28-10 Threshold reached: Number of signal units in error - PM

clear this alarm.
68P02901W26-S 28-23
Nov 2007
7. LMTL: Threshold reached: SL number of negative ACKs received - PM Chapter 28: LMTL Alarms
7. LMTL: Threshold reached: SL number of negative

ACKs received - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 7. MTL: SL Number of Negative ACKs Received - PM.
The BSS reports an LMTL SL Number of Negative ACKs Received - PM alarm when the
LMTP_NEG_ACKS counter exceeds the specified threshold.
The LMTP_NEG_ACKS statistic threshold has been reached.
This statistic counts the number of times that the BSS detects messages between the BSS
and MSC that are out of sequence.
There is no additional information in the output for this alarm. Perform the following procedure
to resolve the alarm.
Possible causes

• The BSS and the MSC have incompatible software protocols.
• The BSS has faulty software.
• The MSC has faulty software.
28-24 68P02901W26-S
Nov 2007
Procedure
Procedure 28-11 Threshold reached: SL number of negative ACKs received - PM
1 Determine if the messages between the BSS and the MSC are out of
sequence.
If the messages are... Then...
not out of sequence The fault condition no longer
out of sequence Go to step 2.
2 Determine if the MSC is sending the messages.
If the MSC is... Then...
sending the messages Contact the MSC to resolve the
fault and then clear the alarm.
not sending the messages Send a field representative to the
site to resolve the communication
link fault and then clear this alarm.

68P02901W26-S 28-25
Nov 2007
8. LMTL: Threshold reached: Start of remote processor outage - PM Chapter 28: LMTL Alarms
8. LMTL: Threshold reached: Start of remote processor

outage - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 8. MTL: Start of Remote Processor Outage - PM.
The BSS reports an LMTL Start of Remote Processor Outage - PM alarm when the
LMTP_START_RPO counter exceeds the specified threshold.
This statistic counts each instance that a remote processor outage is identified. This remote
processor outage occurs when signaling messages cannot be transferred.
There is no additional information in the output for this alarm. Perform the following procedure
Possible causes
A remote processor, at the BSS-based SMLC, failed.
28-26 68P02901W26-S
Nov 2007
Procedure
Procedure 28-12 Threshold reached: Start of remote processor outage - PM
1 Determine which remote processor, at the BSS-based SMLC, is

reporting the alarm.
2 Initiate problem resolution procedures for the remote processor.
3 After resolving the remote processor fault, clear this alarm.
68P02901W26-S 28-27
Nov 2007
9. LMTL: Threshold reached: Number of octets retransmitted - PM Chapter 28: LMTL Alarms
9. LMTL: Threshold reached: Number of octets

retransmitted - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 9. MTL: Number of Octets Retransmitted - PM.
The BSS reports an LMTL Number of Octets Retransmitted - PM alarm when the
LMTP_RE_TX counter exceeds the specified threshold.
The LMTP_RE_TX statistic threshold has been reached.
This statistic counts the number of octets that the BSS has retransmitted to the BSS-based
SMLC due to a request by the BSS-based SMLC.
Possible causes
The BSS retransmitted an excessive number of octets. Perform the following procedure to
resolve the alarm.
Procedure
Procedure 28-13 Threshold reached: Number of octets retransmitted - PM
1 Alarms are not cleared by the BSS.

2 This alarm cannot be cleared by the operator.
28-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. LMTL:
Threshold reached: MSUs discarded due to SL congestion - PM
10. LMTL: Threshold reached: MSUs discarded due to

SL congestion - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 10. MTL: MSUs Discarded due to SL Congestion - PM.
The BSS reports an LMTL MSUs Discarded due to SL Congestion - PM alarm when the
LMTP_MSU_DISCARDED counter exceeds the specified threshold.
The LMTP_MSU_DISCARDED statistic threshold has been reached.
This statistic counts each instance that a Message Signal Unit (MSU) is discarded while there is
congestion on the Signaling Link (SL).
Possible causes
The number of LMTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
Procedure 28-14 Threshold reached: MSUs discarded due to SL congestion - PM
1 These alarms are not cleared by the BSS and cannot be cleared by the
operator.
2 If this alarm occurs continuously, the number of LMTLs for the BSS is not
adequate to handle the call volume. Increase the number of LMTLs for
the BSS.
68P02901W26-S 28-29
Nov 2007
11. LMTL: SL congestion events resulting in loss of MSUs - PM Chapter 28: LMTL Alarms
11. LMTL: SL congestion events resulting in loss of

MSUs - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 11. MTL: SL Congestion Events Resulting in Loss of MSUs - PM.
The BSS reports an LMTL SL Congestion Events Resulting in Loss of MSUs - PM alarm
when the LMTP_CONGESTION_LOST_MSU counter exceeds the specified threshold.
The LMTP_CONGESTION_LOST_MSU statistic threshold has been reached.
This statistic counts each Signaling Link (SL) congestion event which results in Message Signal
Units (MSUs) being lost.
Possible causes
28-30 68P02901W26-S
Nov 2007
Procedure
Procedure 28-15 SL congestion events resulting in loss of MSUs - PM
operator.
2 The alarm is due to congestion. The capacity of the current LMTLs is
insufficient to handle the signaling traffic. If this alarm recurs, capacity
must be increased by the addition of LMTLs.
68P02901W26-S 28-31
Nov 2007
12. LMTL: Threshold reached: SL congestion indications - PM Chapter 28: LMTL Alarms
12. LMTL: Threshold reached: SL congestion indications

- PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Refer 12. MTL: SL Congestion Indications - PM.
The BSS reports an LMTL SL Congestion Indications - PM alarm when the

LMTP_LOCAL_SL_CONGESTION counter exceeds the specified threshold.
The LMTP_LOCAL_SL_CONGESTION statistic threshold has been reached.
This statistic counts the number of times that a Signaling Link (SL) is congested with a high
volume of calls.
Possible causes
28-32 68P02901W26-S
Nov 2007
Procedure
Procedure 28-16 Threshold Reached: SL Congestion Indications - PM
operator.
2 The alarm is due to congestion. The capacity of the current LMTLs is
must be increased by the addition of LMTLs.
68P02901W26-S 28-33
Nov 2007
Procedure Chapter 28: LMTL Alarms
28-34 68P02901W26-S
Nov 2007
Chapter
29
MMS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Multiple Serial Interface Link (MMS) alarms are covered in this chapter and include the
following procedures:
• 0. MMS: Synchronization loss daily threshold exceeded on page 29-5.
• 1. MMS: Synchronization loss hourly threshold exceeded on page 29-7.
• 2. MMS: Synchronization loss OOS threshold exceeded on page 29-9.
• 4. MMS: Remote alarm daily threshold exceeded on page 29-12.
• 5. MMS: Remote alarm hourly threshold exceeded on page 29-14.
• 6. MMS: Remote alarm OOS threshold exceeded on page 29-16.
• 8. MMS: Frame slip daily threshold exceeded on page 29-19.
• 9. MMS: Frame slip hourly threshold exceeded on page 29-21.
• 10. MMS: Frame slip OOS threshold exceeded on page 29-23.
• 12. MMS: Bit error daily threshold exceeded on page 29-24.
• 13. MMS: Bit error hourly threshold exceeded on page 29-26.
• 14. MMS: Bit error OOS threshold exceeded on page 29-28.
• 16. MMS: Synchronization loss OOS timer expired on page 29-31.
• 18. MMS: Remote alarm OOS timer expired on page 29-34.
• 20. MMS: Red alarm daily threshold exceeded on page 29-37.
• 21. MMS: Red alarm hourly threshold exceeded on page 29-39.
• 22. MMS: Red alarm OOS threshold exceeded on page 29-41.
• 23. MMS: Red alarm OOS timer expired on page 29-44.
• 24. MMS: Modem to NIU serial channel control link failure on page 29-47.
• 25. MMS: HDSL modem loop 0 sync loss timer expired on page 29-49.
• 26. MMS: HDSL modem loop 1 sync loss timer expired on page 29-53.
• 27. MMS: Master HDSL modem loop 0 SNR daily threshold exceeded on page 29-56.
• 28. MMS: Master HDSL modem loop 1 SNR daily threshold exceeded on page 29-58.
68P02901W26-S 29-1
Nov 2007
Procedure Chapter 29: MMS Alarms
• 29. MMS: Slave HDSL modem loop 0 SNR daily threshold exceeded on page 29-60.
• 30. MMS: Slave HDSL modem loop 1 SNR daily threshold exceeded on page 29-62.
• 31. MMS: Master HDSL modem loop 0 SNR hourly threshold exceeded on page 29-64.
• 32. MMS: Master HDSL modem loop 1 SNR hourly threshold exceeded on page 29-66.
• 33. MMS: Slave HDSL modem loop 0 SNR hourly threshold exceeded on page 29-68.
• 34. MMS: Slave HDSL modem loop 1 SNR hourly threshold exceeded on page 29-70.
• 35. MMS: Master HDSL modem loop 0 SNR OOS threshold exceeded on page 29-72.
• 36. MMS: Master HDSL modem loop 1 SNR OOS threshold exceeded on page 29-76.
• 37. MMS: Slave HDSL modem loop 0 SNR OOS threshold exceeded on page 29-80.
• 38. MMS: Slave HDSL modem loop 1 SNR OOS threshold exceeded on page 29-84.
• 39. MMS: LTU download failure on page 29-88.
• 40. MMS: LTU configuration failure on page 29-90.
• 41. MMS: Connectivity mismatch between BSC and the RXCDR on page 29-91.
• 42. MMS: DSW/DSWX switching hardware required, BSC is now operating in Single
Rate mode on page 29-93.
• 253. MMS: Critical alarm threshold exceeded on page 29-94.
29-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to MMS alarms
Introduction to MMS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMS alarms
Multiple Serial Interface Link (MMS) device.
The alarms in this chapter apply to a variety of current hardware systems:

• InCell BSU-based systems (including ExCell and TopCell).
• M-Cell2, M-Cell6, Horizon macro, Horizon compact (M-Cell arena macro), Horizon
compact2 and micro site systems, which include M-Cell city, M-Cell micro, Horizon micro
(M-Cell arena) and Horizon micro2.
MMS E1 system conguration
Depending on the system software configuration, the MMS device can be configured as E1
(2.048 Mbps) link.
The hardware used determines whether the (MMS) links are located on either the InCell
Multiple Serial Interface (MSI) board or on the M-Cell/Horizon Network Interface Unit (NIU).
E1 alarm exceptions
The Synchronization MMS alarms (0, 1, 2 and 16) apply only to systems with an E1 link
configuration.
M-Cell alarms
The alarms contained in this chapter which apply to the M-Cell2, M-Cell6 and M-Cell micro site
system products are generated for the NIU.
The following is the M-Cell (NIU) hardware that can generate an MMS alarm:
• The NIU in either an M-Cell2 or an M-Cell6 cabinet.
• The NIUm in an M-Cell micro, M-Cell city, Horizon micro (M-Cell arena) or Horizon micro2
unit.
Alarm reporting
The InCell MMS hardware alarms are reported to the GPROC by MSI, XCDR, and GDP boards
through the MCAP bus. The M-Cell MMS hardware alarms are reported by the M-Cell processor.
68P02901W26-S 29-3
Nov 2007
FRUs Chapter 29: MMS Alarms
MMS alarms are generated due to fault conditions existing with:

• An E1 link cable or microwave link.
• The environmental factors - bad weather conditions may affect hardware.
• An MSI/MSI-2 board, MSI in an RF Unit, an XCDR (or GDP) board or a Network Interface
Unit (NIU) - on either side of the link.
• A remote system.
FRUs
An MMS device may be equipped on one of the FRUs shown in Table 29-1.
Table 29-1 MMS FRUs
FRU Description
MSI Multiple Serial Interface board.
XCDR Transcoder board.
GDP Generic DSP Processor or Generic Downloadable Processor.
Replacement for XCDR.
NIU M-Cell/Horizon Network Interface Unit with one or two links.
MSI2-CONV M-Cell MSI that converts a link from E1 to T1 and from T1 to E1.
MSI2 M-Cell MSI configurable for E1 operation.
MSI-EXT-HDSL External HDSL modem.
NIU-HDSL Network interface unit for HDSL.
NIU-EXT-HDSL Network interface unit for external HDSL.
DPROC For GPRS PCU, MMS resides on Network Interface Board (NIB),
which is mounted on the DPROC board.
NIUm Horizon macro (M-Cell micro) NIU/MSI with one or two links.
NIUm-HDSL Network interface unit for HDSL on Horizon micro or Horizon micro2.
NIUm-EXT-HDSL Network interface unit for external HDSL on Horizon micro or
Horizon micro2.
ARENA (NIU) Horizon micro (M-Cellarena) NIU/MSI.
ARENA MAC (NIU) Horizon compact (M-Cell arena Macro) NIU/MSI.
HORIZONMIC2 (NIU) Horizon micro2 NIU.
HORIZONCOM2 Horizon compact2 NIU.
(NIU)
29-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MMS: Synchronization loss daily threshold exceeded
0. MMS: Synchronization loss daily threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The number of times the MMS receive signal lost synchronization exceeded the sync_loss_daily
database element threshold.
This alarm may be a precursor to a serious fault condition.
Possible causes

• The receive E1 link signal is fading in and out due to faulty cabling or faulty connections to
the T43/BIB board.
• The trunking equipment that provides site-to-site interface malfunctioned.
• An MSI board is faulty.
68P02901W26-S 29-5
Nov 2007
Procedure
Procedure 29-1 Synchronization loss daily threshold exceeded
1 Determine if this alarm is persistently reported.

persistently reported Go to step 2.
2 Determine if other MMS or MSI alarms were reported at the same
time.
If other MMS or MSI alarms Then...
are...
reported Resolve the other MMS or MSI
alarms and then clear this alarm.
This alarm does not merit
invasive operator action to resolve
this specific fault condition.
29-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MMS: Synchronization loss hourly threshold exceeded
1. MMS: Synchronization loss hourly threshold

exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The number of times the MMS receive signal lost synchronization in a one hour period has
exceeded the sync_loss_hourly database element threshold.
Possible causes

the T43/BIB board.
68P02901W26-S 29-7
Nov 2007
Procedure
Procedure 29-2 Synchronization loss hourly threshold exceeded

time.
are...
29-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. MMS: Synchronization loss OOS threshold exceeded
2. MMS: Synchronization loss OOS threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The number of times the MMS receive signal lost synchronization exceeded the sync_loss_oos
System action
The MMS is placed OOS.
Possible causes

the T43/BIB board.
Procedure
68P02901W26-S 29-9
Nov 2007
Procedure 29-3 Synchronization loss OOS threshold exceeded
1 Determine if this alarm is occurring frequently.

occurring frequently Send a field representative to the site to
appropriate action.
not occurring frequently Go to step 2.
2 Determine the state of the MMS.
busy-unlocked The fault condition no longer exists. Go to
step 5.
not busy-unlocked Reset the MMS. If the alarm clears, go to
step 5. If the alarm does not clear, go to
step 3.
3 Determine the state of the MSI.
If the MSI is... Then...
step 5.
step 3.
4 In a TTY window, execute the disp_mms_ts_usage command to display the
logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
MTLs and/or OMLs Go to step 6.
5 Determine the state of each of the SITEs connected by the MMS reporting
the alarm.
If the SITEs are... Then...
step 6.
appropriate action.
Continued
29-10 68P02901W26-S
Nov 2007
Procedure 29-3 Synchronization loss OOS threshold exceeded (Continued)

6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer exists.
any of the logical links are This is normal for a standby OML link
enable-unlocked if the active OML link is busy-unlocked.
For MTL or RSL links, an MMS link
interface failure occurred. Send a field
representative to the site to determine the
cause of the alarm and take appropriate
action.
any of the logical links are Reset the link device and then go to step 7.
disable-unlock
7 Determine the state of the logical link device after the reset is complete.
If the device is... Then...
busy-unlocked The fault condition no longer exists. No
further action is required.
appropriate action.

68P02901W26-S 29-11
Nov 2007
4. MMS: Remote alarm daily threshold exceeded Chapter 29: MMS Alarms
4. MMS: Remote alarm daily threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This mechanism counts each occurrence of the Remote Loss OOS alarm remote_loss_oos.
When the remote Alarm Daily Threshold Exceeded remote_loss_daily threshold is reached
by this count, a warning alarm is generated.
Possible causes

• The transmit E1 link signal is fading in and out due to faulty cabling or faulty connections
to the T43/BIB board.
• The transmit E1 link is experiencing a high BER.
29-12 68P02901W26-S
Nov 2007
Procedure
Procedure 29-4 Remote alarm daily threshold exceeded

time.
are...
68P02901W26-S 29-13
Nov 2007
5. MMS: Remote alarm hourly threshold exceeded Chapter 29: MMS Alarms
5. MMS: Remote alarm hourly threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This mechanism counts each occurrence of the Remote Loss OOS Alarm (remote_loss_oos).
When the Remote Alarm Hourly Threshold Exceeded (remote_loss_hourly) threshold is
reached, a warning alarm is generated.
Possible causes

• The transmit E1 link is experiencing a high BER.
29-14 68P02901W26-S
Nov 2007
Procedure
Procedure 29-5 Remote alarm hourly threshold exceeded

time.
are...
68P02901W26-S 29-15
Nov 2007
6. MMS: Remote alarm OOS threshold exceeded Chapter 29: MMS Alarms
6. MMS: Remote alarm OOS threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This mechanism is a counter that is incremented each time warning alarm 4. MMS: Remote
Alarm Daily Threshold Exceeded is generated. When the remote_loss_OOS threshold is
reached, the MSS is placed OOS.
System action
Possible causes

Procedure
29-16 68P02901W26-S
Nov 2007
Procedure 29-6 Remote alarm OOS threshold exceeded

appropriate action.
step 4.
step 3.
not busy-unlocked Reset the MSI.
If the alarm clears, go to step 4.
If the alarm does not clear, send a field
action.
assigned to the MMS
include...
RSLs Go to step 5.
the alarm.
step 6.
appropriate action.
Continued
68P02901W26-S 29-17
Nov 2007
Procedure 29-6 Remote alarm OOS threshold exceeded (Continued)

If... Then...
all of the logical links are The fault condition no longer exists. No
busy-unlocked further action is required.
any of the logical links are This is normal for a standby OML link if the
enable-unlocked active OML link is busy-unlocked. For MTL
or RSL links, an MMS link interface failure
occurred. Send a field representative to the
site to determine the cause of the alarm and
disable-unlocked
appropriate action.

29-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. MMS: Frame slip daily threshold exceeded
8. MMS: Frame slip daily threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The number of frame slips on the E1 link exceeded the slip_loss_daily database element
threshold.
Possible causes

• The E1 link signal is fading in and out due to faulty cabling or faulty connections to the
T43/BIB board.
• The GCLK is not synchronized with this inbound E1 link.
• The 0.8 Hz tolerance on the GCLK frequency was exceeded.
Procedure
68P02901W26-S 29-19
Nov 2007
Procedure 29-7 Frame slip daily threshold exceeded

a recurrence Go to step 2.
not a recurrence Clear the alarm.
2 Determine if any GCLK alarms are also reported.
If GCLK alarms... Then...
are reported Troubleshoot the GCLK alarms.
After resolving the GCLK alarms,
clear the alarm.
are not reported Go to step 3.
3 Determine if the MMS 8 and MMS 9 alarms are reported at the
same time.
If both MMS 8 and MMS 9 Then...
alarms are...
reported Send a field representative to the

29-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. MMS: Frame slip hourly threshold exceeded
9. MMS: Frame slip hourly threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The number of frame slips on the E1 link exceeded the slip_loss_hourly database element
threshold.
Possible causes

• The E1 link signal is fading in and out due to faulty cabling or faulty connections to the
T43/BIB board.
• The GCLK is not synchronized with this inbound E1 link.
• The 0.8 Hz tolerance on the GCLK frequency was exceeded.
Procedure
68P02901W26-S 29-21
Nov 2007
Procedure 29-8 Frame slip hourly threshold exceeded

a recurrence Go to step 2.
not a recurrence Clear the alarm.
2 Determine if any GCLK alarms are also reported.
If GCLK alarms... Then...
are reported Troubleshoot the GCLK alarms.
After resolving the GCLK alarms,
clear the alarm.
are not reported Go to step 3.
3 Determine if the MMS 8 and MMS 9 alarms are reported at the
same time.
If both MMS 8 and MMS 9 Then...
alarms are...
reported Send a field representative to the

29-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. MMS: Frame slip OOS threshold exceeded
10. MMS: Frame slip OOS threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Number of Frame Slip alarm hits over a 24 hour period exceeded threshold (default: 255).
Possible causes
GCLK is not synchronized with this inbound mega stream.
Procedure
Procedure 29-9 Frame slip OOS threshold exceeded
1 If the MMS is D-U, check whether the MMS or MSI is faulty. If MMS/MSI is
faulty, replace board else check cabling, connections and the link interface
board.
2 Verify as necessary, that the MTL, OML or RSL links have been re-established
and all SITEs have returned to service.
3 In the case where the faulty device resides in a Horizon2 cabinet, the MMS
is part of the NIU2 which is onboard the Horizon2 Site Controller (H2SC). In
this case the FRU to be replaced should be the H2SC.
68P02901W26-S 29-23
Nov 2007
12. MMS: Bit error daily threshold exceeded Chapter 29: MMS Alarms
12. MMS: Bit error daily threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Bit Error Rate (BER) on the MMS receive signal exceeded the ber_loss_daily database
element threshold.
Possible causes

• The noise present on the receive signal caused the BER to exceed the threshold.
the T43/BIB board.
29-24 68P02901W26-S
Nov 2007
Procedure
Procedure 29-10 Bit error daily threshold exceeded

time.
are...
68P02901W26-S 29-25
Nov 2007
13. MMS: Bit error hourly threshold exceeded Chapter 29: MMS Alarms
13. MMS: Bit error hourly threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Bit Error Rate (BER) on the receive signal exceeded the ber_loss_hourly database element
threshold.
Possible causes

the T43/BIB board.
29-26 68P02901W26-S
Nov 2007
Procedure
Procedure 29-11 Bit error hourly threshold exceeded

time.
are...
68P02901W26-S 29-27
Nov 2007
14. MMS: Bit error OOS threshold exceeded Chapter 29: MMS Alarms
14. MMS: Bit error OOS threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This mechanism is a counter that is incremented each time warning alarm 12. MMS: Bit Error
Daily Threshold Exceeded is generated. When the Bit Error OOS Threshold Exceeded
(ber_loss_oos) threshold is reached, the MSS is placed OOS.
Possible causes

• The trunking equipment that provides site-to-site interface is faulty.
• The link interface board is faulty.
29-28 68P02901W26-S
Nov 2007
Procedure
Procedure 29-12 Bit error OOS threshold exceeded

appropriate action.
step 4.
step 3.
If the alarm does not clear, send a field
action.
assigned to the MMS
include...
RSLs Go to step 5.
the alarm.
step 6.
appropriate action.
Continued
68P02901W26-S 29-29
Nov 2007
Procedure 29-12 Bit error OOS threshold exceeded (Continued)

If... Then...
For MTL or RSL links, an MMS link interface
failure occurred. Send a field representative
to the site to determine the cause of the
disable-unlocked
appropriate action.

29-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 16. MMS: Synchronization loss OOS timer expired
16. MMS: Synchronization loss OOS timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The length of time that the MMS lost synchronization exceeded the sync_time_oos database
element threshold.
Possible causes

• The E1 link is faulty or disconnected.
• The receive E1 link signal faded out for a period exceeding the timer value due to faulty
cabling or faulty connections to the T43/BIB board.
• The receive signal framing words is corrupt.
• The remote E1 link interface is incompatible.
68P02901W26-S 29-31
Nov 2007
Procedure
Procedure 29-13 Synchronization loss OOS timer expired

appropriate action.
Go to step 4.
not busy-unlocked Reset the MMS. If the
alarm clears, go to step 4.
If the alarm does not clear, go to
step 3.
not busy-unlocked Reset the MSI. If the
If the alarm does not clear, send a
field representative to the site to determine
the cause of the alarm and take appropriate
action.
assigned to the MMS
include...
RSLs Go to step 5.
Continued
29-32 68P02901W26-S
Nov 2007
Procedure 29-13 Synchronization loss OOS timer expired (Continued)

the alarm.
step 6.
appropriate action.
If... Then...
disable-unlocked
appropriate action.

68P02901W26-S 29-33
Nov 2007
18. MMS: Remote alarm OOS timer expired Chapter 29: MMS Alarms
18. MMS: Remote alarm OOS timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The length of time that a remote alarm has been active exceeded the remote_time_oos
database element threshold. This condition is detected by the remote end of the link.
Possible causes

• The E1 link is faulty or disconnected.
• The receive E1 link signal faded out for a period exceeding the timer value due to faulty
cabling or faulty connections to the T43/BIB board.
• The receive signal framing words is corrupt.
29-34 68P02901W26-S
Nov 2007
Procedure
Procedure 29-14 Remote alarm OOS timer expired

appropriate action.
step 4.
step 3.
action.
assigned to the MMS
include...
RSLs Go to step 5.
the alarm.
step 6.
appropriate action.
Continued
68P02901W26-S 29-35
Nov 2007
Procedure 29-14 Remote alarm OOS timer expired (Continued)

If... Then...
disable-unlock
appropriate action.

29-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. MMS: Red alarm daily threshold exceeded
20. MMS: Red alarm daily threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The number of times the MMS signal lost synchronization exceeded the red_loss_daily
Possible causes

• The received E1 link signal is fading in and out due to faulty cabling or faulty connections
68P02901W26-S 29-37
Nov 2007
Procedure
Procedure 29-15 Red alarm daily threshold exceeded

time.
are...
29-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. MMS: Red alarm hourly threshold exceeded
21. MMS: Red alarm hourly threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
The number of times the MMS signal lost synchronization exceeded the red_loss_hourly
Possible causes

the T43/BIB board.
68P02901W26-S 29-39
Nov 2007
Procedure
Procedure 29-16 Red alarm hourly threshold exceeded

time.
are...
29-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. MMS: Red alarm OOS threshold exceeded
22. MMS: Red alarm OOS threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated if the number of times the MMS receive signal loses synchronization
exceeds the red_loss_oos database element threshold. This database element is a counter
that is incremented each time the Red Alarm Daily Threshold Exceeded warning alarm
(red_loss_daily) is generated. When the red_loss_OOS threshold is reached, the MSS is placed
OOS.
System action
Possible causes

the T43/BIB board.
68P02901W26-S 29-41
Nov 2007
Procedure
Perform the following procedure to resolve the alarms.
Procedure 29-17 Red alarm OOS threshold exceeded

appropriate action.
step 4.
not busy-unlocked Reset the MMS. If the alarm clears, go to step
4. If the alarm does not clear, go to step 3.
action.
assigned to the MMS
include...
RSLs Go to step 5.
the alarm.
step 6.
appropriate action.
Continued
29-42 68P02901W26-S
Nov 2007
Procedure 29-17 Red alarm OOS threshold exceeded (Continued)

If... Then...
disable-unlocked
appropriate action.

68P02901W26-S 29-43
Nov 2007
23. MMS: Red alarm OOS timer expired Chapter 29: MMS Alarms
23. MMS: Red alarm OOS timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The length of time that the MMS lost synchronization exceeded the red_time_oos database
element threshold.
System action
Possible causes

• The receive E1 signal is lost.
• The receive signal framing words are corrupted.
Procedure
29-44 68P02901W26-S
Nov 2007
Procedure 29-18 Red alarm OOS timer expired

appropriate action.
step 4.
step 3.
action.
assigned to the MMS
include...
RSLs Go to step 5.
the alarm.
step 6.
appropriate action.
Continued
68P02901W26-S 29-45
Nov 2007
Procedure 29-18 Red alarm OOS timer expired (Continued)

If... Then...
disable-unlocked
appropriate action.

29-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. MMS: Modem to NIU serial channel control link failure
24. MMS: Modem to NIU serial channel control link

failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The HDSL modem-to-NIU serial channel control link on an MMS failed. This alarm is generated
only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
This fault condition is potentially service affecting. If the modem continues to function, calls
or service are not affected. The purpose of this alarm is to provide notification of a possible
problem in the HDSL modem or the related NIU MMS link hardware.
68P02901W26-S 29-47
Nov 2007
Possible causes Chapter 29: MMS Alarms
Possible causes

• The HDSL modem is not responding and is faulty.
• The Serial Channel Link is faulty.
Procedure
Procedure 29-19 Modem to NIU serial channel control link failure

29-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. MMS: HDSL modem loop 0 sync loss timer expired
25. MMS: HDSL modem loop 0 sync loss timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The length of time that the HDSL modem lost the synchronization word on Loop 0 exceeded
the hdsl_losw_oos database element threshold. This alarm is generated only for an MMS on a
Network Interface Unit (NIU) that supports an internal HDSL modem.
System impact
The MMS and HDSL modem are placed OOS.
If there is no functioning redundant link, calls are dropped and data being transmitted
is lost. The site may lose service if the connection is lost.
68P02901W26-S 29-49
Nov 2007
Possible causes Chapter 29: MMS Alarms
Possible causes

• The length of the physical HDSL link is too long.
• The link cabling and/or connections are disconnected or damaged.
• Interference currently exists on the twisted pair.
• The HDSL modem failed.
Procedure
Procedure 29-20 HDSL modem loop 0 sync loss timer expired

occurring frequently Send a field representative to the
not busy-unlocked Reset the MMS. If the alarm clears,
go to step 5. If the alarm does not
clear, go to step 3.
Continued
29-50 68P02901W26-S
Nov 2007
Procedure 29-20 HDSL modem loop 0 sync loss timer expired (Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
required.
68P02901W26-S 29-51
Nov 2007

29-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. MMS: HDSL modem loop 1 sync loss timer expired
26. MMS: HDSL modem loop 1 sync loss timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The length of time that the HDSL modem lost the synchronization word on Loop 1 exceeded
the hdsl_losw_oos database element threshold. This alarm is generated only for an MMS on a
System impact
The MMS and HDSL modem are placed OOS. HDSL modem loop 2 sync timer expired.
Possible causes

68P02901W26-S 29-53
Nov 2007
Procedure
Procedure 29-21 HDSL modem loop 1 sync loss timer expired

assigned to the MMS
include...
RSLs Go to step 5.
Continued
29-54 68P02901W26-S
Nov 2007
Procedure 29-21 HDSL modem loop 1 sync loss timer expired (Continued)
If... Then...
required.
complete.
required.

68P02901W26-S 29-55
Nov 2007
27. MMS: Master HDSL modem loop 0 SNR daily threshold exceeded Chapter 29: MMS Alarms
27. MMS: Master HDSL modem loop 0 SNR daily

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop 0 has exceeded the
hdsl_snr_daily database element threshold. This alarm is generated only for an MMS on a
Possible causes

29-56 68P02901W26-S
Nov 2007
Procedure
Procedure 29-22 Master HDSL modem loop 0 SNR daily threshold exceeded

time.
are...
68P02901W26-S 29-57
Nov 2007
28. MMS: Master HDSL modem loop 1 SNR daily threshold exceeded Chapter 29: MMS Alarms
28. MMS: Master HDSL modem loop 1 SNR daily

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

29-58 68P02901W26-S
Nov 2007
Procedure
Procedure 29-23 Master HDSL modem loop 1 SNR daily threshold exceeded

time.
are...
68P02901W26-S 29-59
Nov 2007
29. MMS: Slave HDSL modem loop 0 SNR daily threshold exceeded Chapter 29: MMS Alarms
29. MMS: Slave HDSL modem loop 0 SNR daily

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop 0 has exceeded the
Possible causes

29-60 68P02901W26-S
Nov 2007
Procedure
Procedure 29-24 Slave HDSL modem loop 0 SNR daily threshold exceeded

time.
are...
68P02901W26-S 29-61
Nov 2007
30. MMS: Slave HDSL modem loop 1 SNR daily threshold exceeded Chapter 29: MMS Alarms
30. MMS: Slave HDSL modem loop 1 SNR daily

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

29-62 68P02901W26-S
Nov 2007
Procedure
Procedure 29-25 Slave HDSL modem loop 1 SNR daily threshold exceeded

time.
are...
68P02901W26-S 29-63
Nov 2007
31. MMS: Master HDSL modem loop 0 SNR hourly threshold exceeded Chapter 29: MMS Alarms
31. MMS: Master HDSL modem loop 0 SNR hourly

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
hdsl_snr_hourly database element threshold. This alarm is generated only for an MMS on a
Possible causes

29-64 68P02901W26-S
Nov 2007
Procedure
Procedure 29-26 Master HDSL modem loop 0 SNR hourly threshold exceeded

time.
are...
68P02901W26-S 29-65
Nov 2007
32. MMS: Master HDSL modem loop 1 SNR hourly threshold exceeded Chapter 29: MMS Alarms
32. MMS: Master HDSL modem loop 1 SNR hourly

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

29-66 68P02901W26-S
Nov 2007
Procedure
Procedure 29-27 Master HDSL modem loop 1 SNR hourly threshold exceeded

time.
are...
68P02901W26-S 29-67
Nov 2007
33. MMS: Slave HDSL modem loop 0 SNR hourly threshold exceeded Chapter 29: MMS Alarms
33. MMS: Slave HDSL modem loop 0 SNR hourly

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
hdsl_snr_hourly database element threshold. This alarm is only generated only for an MMS on
a Network Interface Unit (NIU) that supports an internal HDSL modem.
Possible causes

29-68 68P02901W26-S
Nov 2007
Procedure
Procedure 29-28 Slave HDSL modem loop 0 SNR hourly threshold exceeded

time.
are...
68P02901W26-S 29-69
Nov 2007
34. MMS: Slave HDSL modem loop 1 SNR hourly threshold exceeded Chapter 29: MMS Alarms
34. MMS: Slave HDSL modem loop 1 SNR hourly

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes

29-70 68P02901W26-S
Nov 2007
Procedure
Procedure 29-29 Slave HDSL modem loop 1 SNR hourly threshold exceeded

time.
are...
68P02901W26-S 29-71
Nov 2007
35. MMS: Master HDSL modem loop 0 SNR OOS threshold exceeded Chapter 29: MMS Alarms
35. MMS: Master HDSL modem loop 0 SNR OOS

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem loop 0 has exceeded the
hdsl_snr_oos database element threshold for a period longer than the length of time specified
for the hdsl_snr_hourly_mon_period database element. This alarm is generated only for an
MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.
System impact
The site ID where the master modem is physically located and the MMS ID associated with the
slave modem are displayed.
29-72 68P02901W26-S
Nov 2007
Possible causes

Procedure
Procedure 29-30 Master HDSL modem loop 0 SNR OOS threshold exceeded

Continued
68P02901W26-S 29-73
Nov 2007
(Continued)
assigned to the MMS
include...
RSLs Go to step 5.
If... Then...
required.
complete.
required.
29-74 68P02901W26-S
Nov 2007

68P02901W26-S 29-75
Nov 2007
36. MMS: Master HDSL modem loop 1 SNR OOS threshold exceeded Chapter 29: MMS Alarms
36. MMS: Master HDSL modem loop 1 SNR OOS

threshold exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem loop 1 has exceeded the
System impact
29-76 68P02901W26-S
Nov 2007
Possible causes

Procedure

Continued
68P02901W26-S 29-77
Nov 2007
(Continued)
assigned to the MMS
include...
RSLs Go to step 5.
If... Then...
required.
complete.
required.
29-78 68P02901W26-S
Nov 2007

68P02901W26-S 29-79
Nov 2007
37. MMS: Slave HDSL modem loop 0 SNR OOS threshold exceeded Chapter 29: MMS Alarms
37. MMS: Slave HDSL modem loop 0 SNR OOS threshold

exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem loop 0 has exceeded the
System impact
29-80 68P02901W26-S
Nov 2007
Possible causes

Procedure
Procedure 29-32 Slave HDSL modem loop 0 SNR OOS threshold exceeded

Continued
68P02901W26-S 29-81
Nov 2007
(Continued)
assigned to the MMS
include...
RSLs Go to step 5.
If... Then...
all of the logical links are The fault condition no longer exists.
complete.
29-82 68P02901W26-S
Nov 2007

68P02901W26-S 29-83
Nov 2007
38. MMS: Slave HDSL modem loop 1 SNR OOS threshold exceeded Chapter 29: MMS Alarms
38. MMS: Slave HDSL modem loop 1 SNR OOS threshold

exceeded
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem loop 1 has exceeded the
System impact
29-84 68P02901W26-S
Nov 2007
Possible causes

Procedure

Continued
68P02901W26-S 29-85
Nov 2007
(Continued)
assigned to the MMS
include...
RSLs Go to step 5.
If... Then...
required.
complete.
required.
29-86 68P02901W26-S
Nov 2007

68P02901W26-S 29-87
Nov 2007
39. MMS: LTU download failure Chapter 29: MMS Alarms
39. MMS: LTU download failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
LTU Firmware upgrade has failed. The alarm is raised against the MMS corresponding to
the LTU which failed to upgrade.
Download Failure error codes:

• 0x03 EMU did not accept download command.
• 0x05 Timeout waiting for message from COM.
• 0x06 Download canceled by the EMU.
• 0x10 Unable to put EMU in auto baud detect state.
• 0x11 XMOD does not have the MIX_BACK_TERM locked.
• 0x12 Unable to initiate a dialog with the COM.
• 0x13 Invalid LTU slot number received.
• 0x14 Specified LTU not detected in slot.
Possible causes
The firmware may have failed to upgrade due to:

• EMU did not accept download command.
• Timeout waiting for message from COM.
• Download canceled by the EMU.
• Unable to put EMU in auto baud detect state.
• XMOD does not have the MIX_BACK_TERM locked.
29-88 68P02901W26-S
Nov 2007
• Unable to initiate a dialog with the COM.
• Invalid LTU slot number received.
• Specified LTU not detected in slot.
Procedure
Procedure 29-34 LTU download failure
1 The operator must analyze the download failure cause.

2 Correct the situation and then try to force a download, thereby downloading
the correct firmware version or object.
68P02901W26-S 29-89
Nov 2007
40. MMS: LTU conguration failure Chapter 29: MMS Alarms
40. MMS: LTU conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Reconfiguration of LTU settings has failed. The alarm is raised against the MMS corresponding
to the LTU which failed the reconfiguration.
Configuration Failure error codes:

• 0x10 Unable to put EMU in autobaud detect state.
• 0x13 Invalid LTU slot number received.
• 0x14 Specified LTU not detected in slot.
Possible causes
The firmware may have failed to configure for reasons like Xmodem unable to initialize the
COM port.
Procedure
Procedure 29-35 LTU conguration failure
1 The operator must analyze the reconfiguration failure cause.

2 Correct the situation and then ins the MSI or force a download again, the
success of which clears the alarm.
29-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41. MMS: Connectivity mismatch between BSC and the RXCDR
41. MMS: Connectivity mismatch between BSC and the

RXCDR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The BSC detected a difference between the connectivity information in a BSC and the
connectivity information in an RXCDR.
The connectivity information consists of an MMS identifier at the BSC, the network identifier of
the RXCDR and an MMS identifier at the RXCDR.
This alarm is raised against the BSC MMS device where the mismatched CIC is equipped.
Possible causes

• The connectivity information at the BSC is incorrect.
• The connectivity information at the RXCDR is incorrect.
68P02901W26-S 29-91
Nov 2007
Procedure
Procedure 29-36 Connectivity mismatch between BSC and RXCDR
1 Display the connectivity information for the BSC and the RXCDR.
2 Compare the BSC and the RXCDR connectivity information to the
network plan.
If the network plan is Then...
different than...
the connectivity information at Correct the connectivity
the BSC information at the BSC.
the connectivity information at Correct the connectivity
the RXCDR information at the RXCDR.
29-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 42. MMS:
DSW/DSWX switching hardware required, BSC is now operating in Single Rate mode
42. MMS: DSW/DSWX switching hardware required,

BSC is now operating in Single Rate mode
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The alarm is FMIC. The alarm will be cleared once all KSW and KSWX switching hardware
is replaced by DSW and DSWX switching hardware and the operator has enabled enhanced
capacity mode. The alarm indicates that at least one CIC is blocked due for this reason.
{22168} The BSS supports the DSW2/DSWX switching hardware required alarm to
indicate that the MMS devices cannot go into service due to lack of DSW/DSWX.
Possible causes
KSW and KSWX switching hardware remains enabled in the site or enhanced capacity mode
has not been enabled.
Procedure
Procedure 29-37 DSW/DSWX switching hardware required, BSC is now operating in

Single Rate mode
1 Replace all KSW and KSWX switching hardware with DSW and DSWX
switching hardware.
2 Ensure enhanced capacity mode is enabled.
68P02901W26-S 29-93
Nov 2007
253. MMS: Critical alarm threshold exceeded Chapter 29: MMS Alarms
253. MMS: Critical alarm threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated if the MMS is unstable and the number of critical alarms received by an
MMS exceeds the threshold in a period of less than 10 minutes.
Threshold default value: 10. This value is not configurable.
If the mms_cat_enable database parameter is enabled, the MMS is taken OOS and
remains OOS until it is reset by the operator or if there are no critical MMS alarms
for 10 minutes (system brings the MMS back into service). If the mms_cat_enable
database parameter is disabled, the MMS returns to service when the alarm clears.
An operator reset overrides the stability wait time and bring back the MMS
immediately. If the mms_cat_enable parameter is enabled, there is no threshold
checking so alarms and clears are processed as they occur.
29-94 68P02901W26-S
Nov 2007
Possible causes

• Onsite environmental factors caused the fault.
• The trunking equipment that provides site-to-site interface are faulty.
• The E1 link signal is fading in and out due to faulty cabling or connections to the T43/BIB
board.
Procedure
Procedure 29-38 Critical alarm threshold exceeded

Continued
68P02901W26-S 29-95
Nov 2007
Procedure 29-38 Critical alarm threshold exceeded (Continued)

assigned to the MMS
include...
RSLs Go to step 5.
If... Then...
required.
any of the logical links are This is normal for a standby
enable-unlocked OML link if the active
OML link is busy-unlocked.
For MTL or RSL links, an MMS link
interface failure occurred. Send a
complete.
required.
29-96 68P02901W26-S
Nov 2007

68P02901W26-S 29-97
Nov 2007
29-98 68P02901W26-S
Nov 2007
Chapter
30
MSI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Multiple Serial Interface (MSI) alarms are covered in this chapter and include the following
procedures:
• 0. MSI: Re-initialized unexpectedly on page 30-3.
• 1. MSI: Hard reset on page 30-5.
• 2. MSI: Watchdog timer expired on page 30-7.
• 3. MSI: Clock B signal loss on page 30-9.
• 4. MSI: Clock A signal loss on page 30-11.
• 5. MSI: Assigned timeslot counter underflow on page 30-13.
• 6. MSI: Assigned timeslot counter overflow on page 30-15.
• 7. MSI: TDM parity error on page 30-17.
• 9. MSI: TRAU frame synchronization loss on page 30-19.
• 11 - 70. MSI: DSP channel (0-59) audit failure on page 30-21.
• 224. MSI: Safe test audit failure on page 30-24.
• 231. MSI: TDM interface configuration failure on page 30-26.
• 232. MSI: Processor bus communication failure on page 30-28.
• 234. MSI: Active link connection failure on page 30-30.
• 254. MSI: Device failure on page 30-32.
68P02901W26-S 30-1
Nov 2007
Introduction to MSI alarms Chapter 30: MSI Alarms
Introduction to MSI alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MSI alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with
the Multiple Serial Interface (MSI) device.
XCDR and GDP alarms
Transcoder (XCDR) and Generic DSP Processor (GDP) alarms are reported as MSI alarms. The
FRU field in the alarm report identifies XCDR and GDP alarms.
FRUs
An MSI device may be equipped on one of the FRUs shown in Table 30-1.
Table 30-1 FRUs on which the MSI device may be equipped
FRU Description
ARENAm (NIU) Horizon micro (M-Cell arena) NIU.
ARENAm MAC (NIU) Horizon compact (M-Cell arena Macro) NIU.
ARTESYN NIB Artesyn™ NIB.
FORCE NIB Force™ NIB.
GDP Generic DSP Processor or Generic Downloadable Processor.
Replacement for XCDR.
MSI Multiple Serial Interface Board.
MSI2-CONV M-Cell MSI that converts a link from E1 to T1 and from T1 to E1.
MSI2 MSI configurable for E1 operation.
NIU M-Cell Network Interface Unit with one or two links.
NIU-EXT-HDSL M-Cell MSI supporting external HDSL modems.
NIU-EXT-HDSL M-Cell NIU supporting external HDSL modems.
NIU-HDSL M-Cell NIU supporting integrated HDSL modems.
NIUm M-Cell micro NIU with one or two links.
NIUm-HDSL M-Cell micro NIU supporting integrated HDSL modems. Only
supported in E1 environment.
NIUm-EXT-HDSL M-Cell micro NIU supporting external HDSL modems. Only supported
in E1 environment.
XCDR Transcoder.
30-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MSI: Re-initialized unexpectedly
0. MSI: Re-initialized unexpectedly

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI board unexpectedly re-initialized or reset.
Possible causes

• The front panel reset switch was pressed.
• The MSI board failed.
Procedure
Wait for a minute after this alarm is reported before continuing with this procedure.
68P02901W26-S 30-3
Nov 2007
Procedure Chapter 30: MSI Alarms
Procedure 30-1 Re-initialized unexpectedly

to the site to replace the MSI
board.
2 Reset the MSI.
3 Determine the state of the MSI after the reset is completed.
required.
site to replace the MSI board.

30-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MSI: Hard reset
1. MSI: Hard reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI board reset.
Possible causes

• The front panel reset switch was pressed.
• A software reset was initiated.
Procedure
Wait for a minute after this alarm is reported before continuing with this procedure.
68P02901W26-S 30-5
Nov 2007

board.
2 Reset the MSI.
required.

30-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. MSI: Watchdog timer expired
2. MSI: Watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI board watchdog timer expired.
Possible causes

• The firmware failed.
• The processor failed.
68P02901W26-S 30-7
Nov 2007
Procedure

board.
2 Reset the MSI.
required.

30-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MSI: Clock B signal loss
3. MSI: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI detected a loss of the Clock B signal.
Possible causes

• The Clock B receive circuitry on the MSI board is faulty.
Procedure
Perform the following procedure to reset the MSI.

required.
no cleared Send a field representative to the
field to replace the MSI board.
68P02901W26-S 30-9
Nov 2007

30-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. MSI: Clock A signal loss
4. MSI: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI detected a loss of the Clock A signal.
Possible causes

• The Clock A receive circuitry on the MSI board is faulty.
Procedure
Perform the following procedure to reset the MSI.

required.
no cleared Send a field representative to the
field to replace the MSI board.
68P02901W26-S 30-11
Nov 2007

30-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. MSI: Assigned timeslot counter underow
5. MSI: Assigned timeslot counter underow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI has determined that the TDM highway is under used. Fewer switch-bound timeslots
Possible causes

• The Timeslot Assignment RAM is faulty.
Procedure
68P02901W26-S 30-13
Nov 2007
Procedure 30-6 Assigned timeslot counter underow

2 Determine the current state of the MSI.
If MSI is... Then...
required.
3 Reset the MSI.
required.

30-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. MSI: Assigned timeslot counter overow
6. MSI: Assigned timeslot counter overow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI has determined that the TDM highway is overused. More switch-bound timeslots are
Possible causes

Procedure
68P02901W26-S 30-15
Nov 2007
Procedure 30-7 Assigned timeslot counter overow

required.
3 Reset the MSI.
required.

30-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. MSI: TDM parity error
7. MSI: TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Possible causes

• The TDM interface circuitry on the MSI board failed.
68P02901W26-S 30-17
Nov 2007
Procedure
Procedure 30-8 TDM parity error

required.
2 Reset the MSI.
required.

30-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. MSI: TRAU frame synchronization loss
9. MSI: TRAU frame synchronization loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An XCDR or GDP DSP lost Transcoder Rate Adaptation Unit (TRAU) frame synchronization
during a call. The call is lost.
Up to seven bytes may be displayed in the additional inhumation field. Each byte identifies a
faulty DSP on the XCDR or GDP board.
Possible causes

• A device within the communications path between the DRI channel coder and the DSP has
been disrupted for more than one second.
The RSL, MSI, MMS, KSW, XCDR, or GDP devices can be in the communications path.
• The E1 physical link on which the communication path resides is faulty.
• A BTS or BSC reset occurred.
Procedure
Procedure 30-9 TRAU frame synchronization loss
Send a field representative to the site to replace the XCDR or GDP with
the faulty DSP.
68P02901W26-S 30-19
Nov 2007

30-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11 - 70. MSI: DSP channel (0-59) audit failure
11 - 70. MSI: DSP channel (0-59) audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
An XCDR or GDP DSP channel audit failed.
The DSP channel number (0-59) corresponds to a physical DSP on an XCDR or GDP board. An
XCDR has one channel per DSP; a GDP has two channels per DSP.
The contents of the Additional information field are shown in Table 30-2:

first 00 to 1D The logical channel displayed in the alarm string corresponds to a single
physical DSP ID as below:
Physical DSP GDP logical channels XCDR logical channels
ID
00 0 and 1 0
01 2 and 3 1
02 4 and 5 2
03 6 and 7 3
04 8 and 9 4
05 10 and 11 5
06 12 and 13 6
07 14 and 15 7
08 16 and 17 8
09 18 and 19 9
0a 20 and 21 10
0b 22 and 23 11
0c 4 and 25 12
0d 26 and 27 13
0e 28 and 29 14
0f 30 and 31 15
10 32 and 33 16
11 34 and 35 17
12 36 and 37 18
13 38 and 39 19
Continued
68P02901W26-S 30-21
Nov 2007
Possible causes Chapter 30: MSI Alarms

14 40 and 41 20
15 42 and 43 21
16 44 and 45 22
17 46 and 47 23
18 48 and 49 24
19 50 and 51 25
1a 52 and 53 26
1b 54 and 55 27
1c 56 and 57 28
1d 58 and 59 29
second 01, 02, 03 Specifies the process that detected the fault.
01 - SAP detected the fault during an audit.
02 - Firmware on the XCDR or GDP board detected the fault.
03 - Fault Management has detected the fault.
Possible causes
A DSP channel (0-59) on an XCDR or GDP board failed.
Procedure
Procedure 30-10 DSP channel (0-59) audit failure

busy-unlocked, Reason code: The alarm condition has ceased.
No Reason No further action is required.
Busy-Unlocked, Reason code: A single DSP failed.
DSP #Audit Failure Go to step 2.
Busy-Unlocked, Reason code: More than one DSP failed.
Multiple DSPs OOS Go to step 2.
disable-unlocked, Reason code: The XCDR or GDP board failed.
No Reason Go to step 3.
Continued
30-22 68P02901W26-S
Nov 2007
Procedure 30-10 DSP channel (0-59) audit failure (Continued)

2 Reset the terrestrial circuits corresponding to the DSP channel(s)
that failed.
If the terrestrial circuit(s)... Then...
are successfully reset The alarm condition has ceased.
did not successfully reset Go to step 3.
3 Reset the MSI.
4 Determine the state of the MSI after the reset is complete.
busy-unlocked The alarm condition has ceased.
site to replace the XCDR or GDP
board.

68P02901W26-S 30-23
Nov 2007
224. MSI: Safe test audit failure Chapter 30: MSI Alarms
224. MSI: Safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The MSI failed a process safe test audit. The process safe test audit verifies the proper operation
Possible causes

• An MCAP interface software failure.
• The MCAP bus is faulty.
• The MSI board lost power.
30-24 68P02901W26-S
Nov 2007
Procedure

2 Reset the MSI.

68P02901W26-S 30-25
Nov 2007
231. MSI: TDM interface conguration failure Chapter 30: MSI Alarms
231. MSI: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The MSI cannot be programmed for a designated timeslot on the TBUS.
System action
The system automatically resets the MSI. If the alarm occurs three times within a 10 minute
period, the MSI is placed OOS.
Possible causes

• The MSI device could not be programmed to the designated timeslot when swapping
the TDM highways.
30-26 68P02901W26-S
Nov 2007
Procedure

2 Reset the MSI.

68P02901W26-S 30-27
Nov 2007
232. MSI: Processor bus communication failure Chapter 30: MSI Alarms
232. MSI: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI board lost the capability to communicate with the GPROC using the MCAP bus.
Possible causes

• The MSI board is removed.
• The portion of the MSI board that supports the MCAP bus access failed.
30-28 68P02901W26-S
Nov 2007
Procedure

2 Reset the MSI.

68P02901W26-S 30-29
Nov 2007
234. MSI: Active link connection failure Chapter 30: MSI Alarms
234. MSI: Active link connection failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The MSI link connection to the active BTP failed.
This alarm is generated only for M-Cell2, M-Cell6, M-Cell micro, Horizon micro
(M-Cell arena) and Horizon compact (M-Cell arena macro) hardware.
Possible causes

• The MSI failed.
• The active BTP failed.
• The portion of the MSI board and/or the active BTP board that supports the BTP link
connection failed.
• The MSI backplane connection failed.
• The BTP backplane connection failed.
30-30 68P02901W26-S
Nov 2007
Procedure

2 Reset the MSI.

68P02901W26-S 30-31
Nov 2007
254. MSI: Device failure Chapter 30: MSI Alarms
254. MSI: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The MSI failed and was placed OOS.
Possible causes
A fault translation process.
Procedure

Continued
30-32 68P02901W26-S
Nov 2007
Procedure 30-15 Device failure (Continued)

2 Reset the MSI.

68P02901W26-S 30-33
Nov 2007
30-34 68P02901W26-S
Nov 2007
Chapter
31
MTL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Message Transfer Link (MTL) alarms are covered in this chapter and include the following
procedures:
• 0. MTL: Signaling link failure on page 31-3.
• 0. MTL: SL failure - All reasons - PM on page 31-7.
• 1. MTL: MSC processor outage on page 31-8.
• 1. MTL: SL failure - Abnormal FIBR/BSNR - PM on page 31-9.
• 2. MTL: SL failure - Excessive delay of ACK - PM on page 31-10.
• 3. MTL: Link traffic too high on page 31-11.
• 3. MTL: SL failure - Excessive error rate - PM on page 31-13.
• 4. MTL: SL failure - Excessive duration of congestion - PM on page 31-14.
• 5. MTL: SL alignment failure - PM on page 31-15.
• 6. MTL: Number of signal units in error - PM on page 31-17.
• 7. MTL: SL number of negative ACKS received - PM on page 31-18.
• 8. MTL: Start of remote processor outage - PM on page 31-20.
• 9. MTL: Number of octets retransmitted - PM on page 31-21.
• 10. MTL: MSUs discarded due to SL congestion - PM on page 31-22.
• 11. MTL: SL congestion events resulting in loss of MSUs - PM on page 31-23.
• 12. MTL: SL congestion indications - PM on page 31-24.
• {28337} 13. MTL: SL failure - Excessive error rate on HSP MTL - PM on page 31-25.
68P02901W26-S 31-1
Nov 2007
Introduction to MTL alarms Chapter 31: MTL Alarms
Introduction to MTL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MTL alarms
Message Transfer Link (MTL) device.
The MTL device provides the 64 kbps connection between the MSC and the BSC. The connection
exists on a timeslot on the MMS device. The connection supports the ITU-TSS Signaling System
7 MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part) protocols with
the variations specified by GSM.
31-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MTL: Signaling link failure
0. MTL: Signaling link failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An MTL connection between the MSC and BSC failed. No signaling information is passed
between the MSC and BSC over the disconnected link.
of events:
• If software determines the MMS link has failed first, an MMS alarm will be
raised as the primary alarm and you will not see an MTL 0 alarm.
• If MMS thresholds are configured such that the MTL fails before the MMS
failure is signaled in software, you will first see the MTL 0 alarm, followed by
the MMS alarm.
• If the MTL fails due to a layer 2 issue only (LAPD) and the MMS is OK, then
you will see the MTL alarm only. The operator can use the OMC to determine
any devices present on the MMS (including MTLs) by clicking the MMS alarm
at the OMC.
This is a service-affecting fault when the last functioning MTL link is placed OOS. If
another link exists, this is not a service-affecting fault.
Last MTL link disconnected
If no other MTL links are in service when this alarm is reported, the Last MTL Link Failure -
Signaling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS is placed
OOS.
68P02901W26-S 31-3
Nov 2007
Additional information eld Chapter 31: MTL Alarms
Table 31-1 shows the content displayed in Additional information field for this alarm.

first 00 to FF MMS timeslot.
second 0A MMS device type.
third fourth fifth 00 to FF00 to FF00 to FF MMS device identifiers.
Ignore any additional bytes displayed in this field.
Possible causes

• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) causing the link failure.
• The remote congestion timer expired.
• The MSI acknowledgment timer expired.
• The sequence numbers may not be synchronized.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive signaling error rate.
• One side of associated MMS is locked, causing the remote end (not locked) to raise the
MSI, GPROC, DPROC).
• Link failure affecting MTL timeslots only, for example when timeslot switching equipment
timeslot 0 is good.
31-4 68P02901W26-S
Nov 2007
Procedure
Procedure 31-1 Signaling link failure

If... Then...
rebooting
required.
not cleared The fault is at the MSC. Contact
the MSC to resolve the fault.
3 Determine if the RXCDR returned to service.
If the RXCDR... Then...
returned to service Go to step 4.
did not return to service Troubleshoot the RXCDR fault.
4 Reset the MTL device.
5 Determine the state of the MTL.
If the MTL is... Then...
required.
6 Determine if there are alarms for the associated MMS or MSI
devices.
MMS or MSI alarms Resolve the MMS or MSI alarms.
no MMS or MSI alarms Send a field representative to the
site to investigate the E1/T2 links.
68P02901W26-S 31-5
Nov 2007
Procedure Chapter 31: MTL Alarms

31-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MTL: SL failure - All reasons - PM
0. MTL: SL failure - All reasons - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_FAIL statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) has failed for all causes excluding
operator interaction using the MMI.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Possible causes
An MSI failed.
Procedure
Procedure 31-2 SL failure - All reasons - PM

clear this alarm.
68P02901W26-S 31-7
Nov 2007
1. MTL: MSC processor outage Chapter 31: MTL Alarms
1. MTL: MSC processor outage

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The MSC processor is OOS. This processor failure causes the MTL link to be blocked. When the
MTL link is blocked, no user signaling traffic can be exchanged.
This is a service-affecting fault.
Possible causes
The MSC processor for the remote MTP layer 2 links malfunctioned or failed.
Procedure
Procedure 31-3 MSC processor outage
Contact the MSC and resolve the problem.
31-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MTL: SL failure - Abnormal FIBR/BSNR - PM
1. MTL: SL failure - Abnormal FIBR/BSNR - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_FIBR statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) is lost due to the detection of
an abnormal Forward Indicator Bit (FIB) caused by the desynchronization of the Backward
Sequence Number (BSN) and Forward Sequence Number (FSN).
Possible causes
The BSN and FSN are corrupted by the MSC.
Procedure
Determine if any BSN and FSN are corrupted by the MSC. Perform the following procedure
Procedure 31-4 SL failure - Abnormal FIBR/BSNR - PM
If the BSN and FSN are... Then...

corrupted by the MSC Contact the MSC to resolve the
not corrupted by the MSC Clear the alarm.
68P02901W26-S 31-9
Nov 2007
2. MTL: SL failure - Excessive delay of ACK - PM Chapter 31: MTL Alarms
2. MTL: SL failure - Excessive delay of ACK - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_ACK statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the system failed
to acknowledge a Message Signal Unit (MSU) before an internal Motorola defined timer expired.
Possible causes
A signaling link failed and an MSU acknowledgment has not been sent.
Procedure
Determine if the MSU is being sent by the MSC. Perform the following procedure to resolve
the alarm.
Procedure 31-5 SL failure - Excessive delay of ACK - PM
If the MSU is... Then...

being sent A communication link may
be faulty. Resolve the
communications link fault and
then clear this alarm.
not being sent Contact the MSC to resolve the
31-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MTL: Link trafc too high
3. MTL: Link trafc too high

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Congestion is detected at either the local or remote end of the MTL affecting the flow of the
signaling traffic across MTP Layer 2.
This is potentially a service-affecting fault.
This alarm does not necessarily indicate that there is a physical problem with the MTLs.
A network congestion problem is probably causing the MTL links to experience signaling
congestion.
System action
After the alarm is reported, flow control procedures are started at the MTP Layer 2 level to
handle congestion. These procedures ensure that user messages are stored in an MTP Layer
2 buffer for transmission when the signaling traffic subsides and returns to a normal level of
activity. When MTP Layer 2 has used all of its buffer space, user messages are discarded.
Possible causes
High traffic levels on the MTL do not allow enough time for the device driver to process frames.
68P02901W26-S 31-11
Nov 2007
Procedure
Procedure 31-6 Link trafc too high
1 Determine if any MTL devices are OOS.

2 Reset each OOS MTL device.
return to service The fault condition no longer
do not return to service Resolve the Signaling Link Failure
(MTL 0) alarm for the MTL
device(s) that do not return to
service and then clear this alarm.
3 Clear the alarm.
The alarm is due to congestion. The capacity of the current MTL
links is insufficient to handle the signaling traffic. If this alarm
recurs, capacity must be increased by the addition of MTL links.
31-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MTL: SL failure - Excessive error rate - PM
3. MTL: SL failure - Excessive error rate - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_ERROR_RATE statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the Signal Unit
Error Rate Monitor (SUERM) timer expired.
Possible causes
An MSI failed.
Procedure
Procedure 31-7 SL failure - Excessive error rate - PM

clear this alarm.
68P02901W26-S 31-13
Nov 2007
4. MTL: SL failure - Excessive duration of congestion - PM Chapter 31: MTL Alarms
4. MTL: SL failure - Excessive duration of congestion -

PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_CONGESTION statistic threshold has been reached.
This statistic counts the number of times a Signaling Link (SL) was lost because the remove
congestion timer expired. This congestion condition occurs on the SL when the threshold levels
establishing the capacity of the transmission or re-transmission buffer of a Message Signal
Unit (MSU) are reached.
Possible causes
Procedure
Procedure 31-8 SL failure - Excessive duration of congestion - PM
1 Clear the alarm.

2 The alarm is due to the duration of a congestion condition that exceeds the
capacity of the MTL links to handle the signaling traffic. If this alarm recurs,
capacity must be increased by the addition of MTL links.
31-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. MTL: SL alignment failure - PM
5. MTL: SL alignment failure - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SL_ALIGNMENT statistic threshold has been reached.
This statistic monitors the system to detect when a Signaling Link (SL) has attempted to align
with the A-Interface while the interface is OOS. This fault condition occurs when the alignment
has been lost.
Possible causes

• The A-interface physical connection is missing.
• A hardware failure caused a loss of the A-Interface.
• The MSC is experiencing a power outage caused the A-Interface to be lost.
• The SL is OOS.
68P02901W26-S 31-15
Nov 2007
Procedure
Procedure 31-9 SL alignment failure - PM
If other alarms are... Then...

reported Resolve the alarms and then clear
this alarm.
31-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. MTL: Number of signal units in error - PM
6. MTL: Number of signal units in error - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_SU_ERROR statistic threshold has been reached.
This statistic counts the number of times that an erroneous Signaling Unit (SU) is received
on the Signaling Link (SL).
Possible causes

• The BSN and FSN are corrupted.
• A Multiple Serial Interface (MSI) failed.
• A Generic Clock (GCLK) failed.
Procedure
Procedure 31-10 Number of signal units in error - PM

clear this alarm.
68P02901W26-S 31-17
Nov 2007
7. MTL: SL number of negative ACKS received - PM Chapter 31: MTL Alarms
7. MTL: SL number of negative ACKS received - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_NEG_ACKS statistic threshold has been reached.
This statistic counts the number of times that the BSS detects messages between the BSS
and MSC that are out of sequence.
Possible causes

• The BSS and the MSC have incompatible software protocols.
• The BSS has faulty software.
• The MSC has faulty software.
31-18 68P02901W26-S
Nov 2007
Procedure
Procedure 31-11 SL number of negative ACKS received - PM
1 Determine if the messages between the BSS and the MSC are out of
sequence.
If the messages are... Then...
not out of sequence The fault condition no longer
out of sequence Go to step 2.
2 Determine if the MSC is sending the messages.
If the MSC is... Then...
sending the messages Contact the MSC to resolve the
fault and then clear the alarm.
not sending the messages Send a field representative to the
site to resolve the communication
link fault and then clear this alarm.

68P02901W26-S 31-19
Nov 2007
8. MTL: Start of remote processor outage - PM Chapter 31: MTL Alarms
8. MTL: Start of remote processor outage - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_START_RPO statistic threshold has been reached.
This statistic counts each instance that a remote processor outage is identified. This remote
processor outage occurs when signaling messages cannot be transferred.
Possible causes
A remote processor failed.
Procedure
Procedure 31-12 Start of remote processor outage - PM
1 Determine which remote processor is reporting the alarm.

2 Initiate problem resolution procedures for the remote processor.
3 After resolving the remote processor fault, clear this alarm.
31-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. MTL: Number of octets retransmitted - PM
9. MTL: Number of octets retransmitted - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MTP_RE_TX statistic threshold has been reached.
This statistic counts the number of octets that the BSS has retransmitted to the MSC due
to a request by the MSC.
Possible causes
The BSS retransmitted an excessive number of octets.
Procedure
Determine if the MSC requested the retransmission due to a fault. Perform the following
Procedure 31-13 Number of octets retransmitted - PM
If the retransmission was... Then...

not due to a fault Clear the alarm.
due to a fault Resolve the fault and then clear
this alarm.
68P02901W26-S 31-21
Nov 2007
10. MTL: MSUs discarded due to SL congestion - PM Chapter 31: MTL Alarms
10. MTL: MSUs discarded due to SL congestion - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The MSU_DISCARDED statistic threshold has been reached.
This statistic counts each instance that a Message Signal Unit (MSU) is discarded while there is
congestion on the Signaling Link (SL).
Possible causes
Procedure
Procedure 31-14 MSUs discarded due to SL congestion - PM
1 Clear the alarm.

2 If this alarm occurs continuously, the number of MTLs for the BSS is not
adequate to handle the call volume. Increase the number of MTL links for
the BSS.
31-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. MTL: SL congestion events resulting in loss of MSUs - PM
11. MTL: SL congestion events resulting in loss of MSUs

- PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The CONGESTION_LOST_MSU statistic threshold has been reached.
This statistic counts each Signaling Link (SL) congestion event which results in Message Signal
Units (MSUs) being lost.
Possible causes
Procedure
Procedure 31-15 SL congestion events resulting in loss of MSUs - PM
1 Clear the alarm.

2 The alarm is due to congestion. The capacity of the current MTL links is
must be increased by the addition of MTL links.
68P02901W26-S 31-23
Nov 2007
12. MTL: SL congestion indications - PM Chapter 31: MTL Alarms
12. MTL: SL congestion indications - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The SL_CONGESTION statistic threshold has been reached.
This statistic counts the number of times that a Signaling Link (SL) is congested with a high
volume of calls.
Possible causes
Procedure
Procedure 31-16 SL congestion indications - PM
1 Clear the alarm.

2 The alarm is due to congestion. The capacity of the current MTL links is
must be increased by the addition of MTL links.
31-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. MTL: SL failure - Excessive error rate on HSP MTL - PM
13. MTL: SL failure - Excessive error rate on HSP MTL -

PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28337}

Description
This alarm is generated when the MTP_SL_ERROR_RATE_HSP statistic threshold has been
reached. This Statistic counts the number of times a Signaling Link (SL) is lost due to the Error
internal monitoring threshold (TE) is exceeded.
Possible causes
• MSI error
• E1 line problem
Procedure
Procedure 31-17 SL failure - excessive error rate on HSP MTL - PM
If theMSI alarms are... Then...

reported resolve the fault and then clear
this alarm.
not reported clear this alarm.
68P02901W26-S 31-25
Nov 2007
31-26 68P02901W26-S
Nov 2007
Chapter
32
OMC-R Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Operations and Maintenance Centre (OMC-R) alarms are covered in this chapter and
include the following procedures:
• 30000. OMC: Download failed on page 32-5.
• 30001. OMC: Upload failed on page 32-8.
• 30002. OMC: File transfer failed on page 32-11.
• 30003. OMC: X 25 circuit down on page 32-14.
• 30004. OMC: Parser disconnected too long on page 32-17.
• 30005. OMC: NE response timeout on page 32-20.
• 30006. OMC: NE error state on page 32-23.
• 30007. OMC: PM disconnected from DB on page 32-26.
• 30008. OMC: EM disconnected from DB on page 32-28.
• 30009. OMC: DB compression failed on page 32-31.
• 30010. OMC: Exceeds upper limit disk usage on page 32-33.
• 30011. OMC: Exceeds lower limit disk usage on page 32-36.
• 30012. OMC: Level 1/2/3 failure on page 32-38.
• 30014. OMC: Database exceeds upper limit on page 32-40.
• 30015. OMC: PM proxy disconnected from DB on page 32-42.
• 30016. OMC: OSI stack error on page 32-43.
• 30017. OMC: CSFP download failed on page 32-44.
• 30018. OMC: DB uncompression failed on page 32-47.
• 30019. OMC: Database exceeds lower limit on page 32-49.
• 30020. OMC: Version query failed on page 32-51.
• 30021. OMC: OMC overloaded with events on page 32-57.
• 30022. OMC: Events discarded due to OMC overloading on page 32-59.
• 30023. OMC: Download disabled on page 32-61.
68P02901W26-S 32-1
Nov 2007
Procedure Chapter 32: OMC-R Alarms
• 30024. OMC: CSFP swap failed on page 32-63.
• 30025. OMC: NMC agent error on page 32-64.
• 30026. OMC: Neighbor statistics table exceeded the configured size on page 32-67.
• 30027. OMC: Supplemental download failed on page 32-69.
• 30029. OMC: Active alarms exceed upper limit of 95% on page 32-72.
• 30030. OMC: Received maximum corrupt NE messages, closed OML on page 32-74.
• 30031. OMC: Resync timed out, no response from NE on page 32-78.
• 30032. OMC: Resync timed out, all resync events not received on page 32-81.
• 30033. OMC: Cannot create further event logfiles in /usr/gsm/ne_data on page 32-83.
• 30035. OMC: Advisory detected on page 32-86.
• 30036. OMC: Recovered outage detected on page 32-87.
• 30037. OMC: UPS condition on page 32-88.
• 30038. OMC: OMC capacity ceiling violation, too many RTFs in MIB on page 32-89.
• 30039. OMC: OMC capacity ceiling violation, too many NEs in MIB on page 32-91.
• 30050. OMC: Solaris 2 hardware failure on page 32-93.
• 30051. OMC: Corrupt NE file on page 32-96.
• 30052. OMC: Corrupt SITE file on page 32-97.
• 30058. OMC: Call success rate below threshold on page 32-98.
• 30059. OMC: No calls on cell on page 32-100.
• 30060. OMC: No activity in timeslot on page 32-101.
• 30061. OMC: CPU load exceeds lower limit on page 32-102.
• 30062. OMC: CPU load exceeds upper limit on page 32-103.
• 30063. OMC: Memory usage exceeds lower limit on page 32-104.
• 30064. OMC: Memory usage exceeds upper limit on page 32-106.
• 30065. OMC: Last MTL may have gone out of service on page 32-107.
• 30066. OMC: Database unable to allocate fragment on page 32-108.
• 30067. OMC: No PM database fragment available on page 32-109.
• 30069. OMC: Maximum number of RTFs in MIB above 90% of license limit on page 32-110.
• 30070. OMC: PM database is down. Unable to bring informix online on page 32-111.
• 30071. OMC: License audit not available alarm on page 32-113.
32-2 68P02901W26-S
Nov 2007
• 30072. OMC: License file not available alarm on page 32-114.
• 30073. OMC: License violation alarm on page 32-115.
• 30075. OMC: Invalid license file alarm on page 32-116.
• 30076. OMC: GSM/GPRS trace logs exceeds configured disk space on page 32-117.
• {27508} 50000/50001/50002 OMC: Field engineer password to be changed on page

32-118.
68P02901W26-S 32-3
Nov 2007
Introduction to OMC-R alarms Chapter 32: OMC-R Alarms
Introduction to OMC-R alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
OMC-R alarms
This chapter describes the alarms and troubleshooting procedures associated with the
Operations and Maintenance Centre (OMC-R) internal alarms.
The OMC-R provides the interface hardware for this system.
Alarm reporting
OMC-R alarms are reported only by the OMC-R software.
32-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30000. OMC: Download failed
30000. OMC: Download failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A software download from the OMC-R failed.
It is normal to have single DownloadConnectedEvent and DownloadDisconnected

messages generated at the beginning of a download.
Possible causes

• The software protocol contains errors.
• The X.25 link failed.
• The Operations and Maintenance Link (OML) failed.
• The BSS is experiencing problems and cannot accept a download.
• The load file contains errors.
• The maximum number of downloads is already in progress.
68P02901W26-S 32-5
Nov 2007
Procedure
Procedure 32-1 Download failed
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the omc audit logs.
3 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
4 If it is a software problem, attempt to resolve the fault condition
at the OMC-R.
• From the Navigation Tree, open the Detailed View

for a link that is Out Of Service (OOS). Use the INS
option from the Fault Mgt menu to re-establish
a broken link. If the link remains OOS, go to step 5.
[In a TTY window, execute the ins_device command for a link

that is Out Of Service (OOS) to re-establish a broken link. If the
link remains OOS, go to step 5].
• Check for software load and protocol errors by examining

the audit files stored on the system processor in the file:
$OMC_TOP/logs/omcaudityymmdd
• Verify that x25_config file download X.25 addresses match the

DOWNLOAD X.25 addresses in the BSS Detailed View.
• Restart the download at a later time if the maximum number of

downloads were in progress at the time the failure occurred.
Continued
32-6 68P02901W26-S
Nov 2007
Procedure 32-1 Download failed (Continued)

5 If it appears that there is a hardware problem with a link or at a BSS
(BSC/BTS) site, check the operational and administrative state of
the suspect equipment.
• From the Navigation Tree, select the SITE. Select the

Display menu and select the Contained Device option
to determine if the problem is at the BTS level.
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
• If a link cannot be re-established by using the INS option from

the Fault Mgt menu for a link that is OOS, send a field
representative to the site to investigate and replace
the link cabling. While there, check for board failures
that may relate to the functioning of the failed link.
[If a link cannot be re-established by executing the ins_device

command for a link that is OOS, send a field representative to
the site to investigate and replace the link cabling. While
there, check for board failures that may relate to the
functioning of the failed link].

68P02901W26-S 32-7
Nov 2007
30001. OMC: Upload failed Chapter 32: OMC-R Alarms
30001. OMC: Upload failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A software upload to the OMC-R from a BSS failed. Typically, a database object is uploaded.
Possible causes

• The software protocol timed out.
• The Operations and Maintenance Link (OML) failed.
• The BSS is too busy to complete an upload.
• The transfer was aborted at the BSS.
Procedure
Procedure 32-2 Upload failed
Continued
32-8 68P02901W26-S
Nov 2007
Procedure 32-2 Upload failed (Continued)

at the OMC-R.

option from the Fault Mgt menu to re-establish a broken
X.25 link. If the link remains OOS, go to step 5.
[In a TTY window, use the ins_device command for a link that
is Out Of Service (OOS) to re-establish a broken X.25 link. If
the link remains OOS, go to step 5].
• Verify that x25_config file upload X.25 addresses match the

UPLOAD X.25 addresses in the BSS Detailed View.
• Check the software processing load on the BSS to determine

whether the failure occurred at the BSS.
• Restart the upload again at a later time if it appears the problem

was in the BSS software. However, if other alarms occurring
are indicating possible equipment problems, go to step 5.
5 If it appears that there is a hardware problem with a link or at a BSS

and so on.


command for the (OOS) link, send a field representative to the
site to investigate and replace the link cabling. While
68P02901W26-S 32-9
Nov 2007

32-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30002. OMC: File transfer failed
30002. OMC: File transfer failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Any category
Description
A software raw statistics file transfer from the OMC-R failed. This is an internal alarm.
Statistics and the actual file being transferred, are the only items affected by the fault. The fault
generating this alarm is non service-affecting.
Unused OMC-R ports may generate a 30003. x25CircuitDown alarm. Also, this alarm
may be related to the GPROC 30012. Level123 Failed indicating that the X.25 circuit
software layers have failed.
Alarm category
This alarm is generated in any of the following alarm categories: Communication, Quality of
Service, Processing, Equipment, and Environmental.
System action taken
When this file transfer failure appears, the OMC-R automatically attempts to transfer the files
(repeatedly) within a specified period of time until the transfer is successful or until the time
period has expired.
The default retries time period is two hours. However, the time period for file transfer retries
is user-configurable.
68P02901W26-S 32-11
Nov 2007
Possible causes Chapter 32: OMC-R Alarms
Possible causes

• The software protocol timed out.
• The BSS is too busy to complete a file transfer.
• The transfer was aborted at the BSS.
• The BSS was reset.
Procedure
Procedure 32-3 File transfer failed
3 Check to see if there are alarms related to the Possible causes
listed. This aids in fault isolation and help lead to the resolution of
this fault condition.
4 If an X.25 link-related problem caused the file transfer to fail, check
the following X.25 items from the OMC-R:
• The NE may have timed out because it was busy or recovering

from one of the following: a download, an upload or a remote
login (rlogin) session.
• Determine whether time out has occurred during a period when

there were a large number of file transfers.
• The X.25 parameter settings is faulty.
• The multiplexer or Transcoder (RXCDR) connections is faulty.
• Check the software processing load on the BSS to determine

whether the failure occurred at the BSS.
Continued
32-12 68P02901W26-S
Nov 2007
Procedure 32-3 File transfer failed (Continued)

5 Restart the file transfer again at a later time if it appears the problem
was with the BSS software. However, if other alarms occurring are
indicating possible equipment problems, go to step 6.

option from the Fault Mgt menu to re-establish a broken
X.25 link. If the link remains OOS, go to step 6.

that is Out Of Service (OOS) to re-establish a broken X.25 link.
If the link remains OOS, go to step 6].
6 If it appears that there is a hardware problem with a link or at a
BSS (BSC/BTS) site, check the operational and administrative state
of the suspect equipment.
• From the Navigation Tree, select the SITE. Choose the

and so on.


command for a link that is OOS, send a field representative to
the site to investigate and replace the link cabling. While

68P02901W26-S 32-13
Nov 2007
30003. OMC: X 25 circuit down Chapter 32: OMC-R Alarms
30003. OMC: X 25 circuit down

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Link
Description
An X.25 event Virtual Circuit (VC) at the Operations and Maintenance Centre (OMC-R) failed.
This alarm is generated when a disruption (or disconnection) within the OMC-R Network
Element (NE) Interface circuitry has caused an X.25 link failure.
This alarm may be related to the GPROC and cause the OMC-R to generate 30012.
Level123Failed; this indicates that the X.25 circuit software layers have failed.
Alarm category
This alarm (30003) is actually a communication failure which is denoted as a link failure. Other
link alarms are shown as communications failures within the system, not as link failures.
The category of Communication failures is a broad classification. It may include any number of
failures within the GSM network circuitry. It is possible to have communication failures within
the GSM circuitry that are independent of one another.
Link failures
Link failure
A link failure occurs when the virtual circuit has been broken. A virtual circuit creates and
maintains the X.25 link (connection) between the OMC-R and a NE.
Network Elements are responsible for maintaining communication functionality for alarms,
events, uploads, downloads, and rlogin. If the virtual circuit link is broken, the OMC-R is
disconnected from the NEs. As a result, an X.25 link fails.
Types of X.25 link failures
Link failures are related to the X.25 link. A link failure may be either partial or complete.
The link may be broken for one or more of the NE-related functions: alarms, events, uploads,
downloads, and rlogin.
The next section describes both types of link failures: partial and complete.
32-14 68P02901W26-S
Nov 2007
Partial link failure
Partial link failure for NE-related communication occurs when one or more NE-related functions
are lost while others remain.
For example, it is possible to have a link failure for alarms while retaining rlogin capabilities.
The reason this is possible is that more than one virtual circuit may exist simultaneously where
the alarm capability may be carried by one link. The rlogin capability can continue.
Complete link failure
Complete link failure for OMC-R to NE-related communication occurs when all NE-related
functions are lost.
For example, if the X.25 link on the OMC-R processor is stopped, every type of link to the NE
fails.
Possible causes

• The BSS was reset.
• The Operations and Maintenance Link (OML) is locked.
• The Multiple Serial Interface (MSI) or MSI link (MMS) used by the OML is locked.
• The X.25 link software on the system processor is faulty.
Procedure
Procedure 32-4 X 25 circuit down
2 Notify the System Administrator that the X.25 circuit is Out Of
Service (OOS).
Continued
68P02901W26-S 32-15
Nov 2007
Procedure 32-4 X 25 circuit down (Continued)

4 Check for related X.25 software layer (level) 1/2/3 errors (30012.
X.25 Level 1/2/3 Failed); or file transfer failure errors (30002.
filexferFailed).
5 Investigate any software faults detected.
6 If it appears that there is a hardware problem with a link or at a
BSS (BSC/BTS) site, check the operational and administrative state
of the suspect equipment.

and so on.

[If the OOS link cannot be re-established by executing the

ins_device command, send a field representative to the
site to investigate and replace the link cabling. While

32-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30004. OMC: Parser disconnected too long
30004. OMC: Parser disconnected too long

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The Performance Management (PM) parser has been disconnected from the OMC-R database
for too long a time period.
The environment variable PM_FP_DISCON_TO is used by the parser to monitor the length of
time that the parser has been disconnected from the database. After the period specified by
PM_FP_DISCON_TO has elapsed, the parser generates this alarm to inform the operator that it
(the parser) has been disconnected from the database for too long.
The parser has a default value of 10800 seconds (3 hours) and a valid range of 30 seconds to
36000 seconds. The default value is used if the environment variable is not set or an invalid
value is specified.
To modify the value for PM_FP_DISCON_TO refer to the manual, Operating

Information: OMC-R System Administration (68P02901W19).
Possible causes

• The parser was disconnected from the OMC-R database for longer than the time specified
by the environment variable PM_FP_DISCON_TO.
• The omc_db_maint script (which disconnects the PM parser) is still running.
• The database is offline or a system failure occurred.
68P02901W26-S 32-17
Nov 2007
Procedure
Procedure 32-5 Parser disconnected too long
2 Contact the System Administrator to determine when the OMC-R
database is reconnected.
3 Check the setting of the environment variable PM_FP_DISCON_TO.
If this variable has been set to a very short time period, the alarm
occurs before the maintenance procedures for the database have
been completed.
Modifications of environment variables on the system

processor take effect only after the OMC-R has been
stopped and restarted.
Reconnect the PM parser within a certain period of time. The

amount of time allowable for a disconnection depends on the disk
space allocated to the raw statistics files.
If the disk space allocated to the raw statistics files is full,

any uploading of the statistics files stop and the system
may crash.
4 Check the omc_db_maint logs to see if the
$DBMS_BIN/db_disconnect connect parser command was
executed.
• If the command was not executed and the OMC-R database

maintenance is complete, enter the command.
• If the command was executed, ensure that the PM parser has

been reconnected by the System Administrator. If it becomes
necessary for the OMC-R operator to reconnect the PM parser
manually, refer to Reconnecting the PM parser manually on
page 32-19.
32-18 68P02901W26-S
Nov 2007
Reconnecting the PM parser manually
After the omc_db_maint command has been executed when reconnecting the PM parser
manually:
• Connect the Event Manager (EM) at the same time.
• Verify that it has already been connected by attempting to create a subscription list. If
this fails, reconnect the EM list manager.
• Enter the command

$DBMS_BIN/db disconnect connect em
68P02901W26-S 32-19
Nov 2007
30005. OMC: NE response timeout Chapter 32: OMC-R Alarms
30005. OMC: NE response timeout

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A BSS failed to respond to an OMC-R request to send its status, within a given (response) time
period. This is part of the Periodic Supervision of Accessibility (PSA) feature.
Periodic Supervision of Accessibility (PSA) feature
PSA verifies that BSSs are functioning correctly by periodically sending a message to each of
the BSSs connected to the OMC-R (through the Alarm Virtual Circuit) requesting that the
BSS informs the OMC-R of its current state.
If a BSS does not respond to the OMC-R request for status, the OMC-R generates a response
time out alarm, for that BSS. This alarm indicates to the operator that the BSS failed to respond
to a message requesting its status and as such may be indicative of a problem at the BSS. The
OMC-R continues to send messages periodically to the BSS requesting its status.
On receipt of a response message from the BSS, the OMC-R generates a clear event (for that
BSS) that clears the previous alarm. The PSA feature is disabled, by default.
Possible causes

• The BSS failed and is OOS.
• The BSS Response Timeout setting in the PSA.CNFG file is too low.
• The communication link to the BSS is down.
Procedure
32-20 68P02901W26-S
Nov 2007
Procedure 32-6 NE response timeout
1 In the Alarm window, check the error reason field in the alarm message to
determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a software
or hardware fault condition.
3 If it is a software problem, attempt to resolve the fault condition at the OMC-R.
• Determine whether the settings of the PSA.CNFG file are as recommended

in the manual, Technical Description: OMC-RMIB Reference.
• Perform a remote login to check the software processing load on the BSS
to determine whether the failure occurred at the BSS.
• Check the communication links to determine if any have failed.

From the Navigation Tree use the State option from the View
Menu on the Detailed View to check individual links.
[Check the communication links to determine if any have failed. In a TTY

window, execute the state command and check the individual links].
4 If it appears that there is a hardware problem with a link or at a BSS (BSC/BTS)
site, check the operational and administrative state of the suspect equipment.
• From the Navigation Tree, select the SITE. Choose

the Display menu and select the Contained Device
option to determine if the problem is at the BTS level.
[In a TTY window, use the state command for the SITE device to
determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a link
failure, communication failure, a hardware (board) failure and so on.
• If a link cannot be re-established by using the INS option from the Fault
Mgt menu for a link that is OOS, send a field representative to the site
to investigate and replace the link cabling. While there, check for board
failures that may relate to the functioning of the failed link.
[If a link cannot be re-established by executing the ins_device command for
a link that is OOS, send a field representative to the site to investigate and
replace the link cabling. While there, check for board failures that may relate
to the functioning of the failed link].
68P02901W26-S 32-21
Nov 2007

32-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30006. OMC: NE error state
30006. OMC: NE error state

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A BSS responded to an OMC-R request to send its status. The response sent indicates that the
BSS is not functioning properly and is currently in an error state. This is part of the Periodic
Supervision of Accessibility (PSA) feature.
Periodic Supervision of Accessibility (PSA) feature
PSA verifies that BSSs are functioning correctly by periodically sending a message to each of
the BSSs connected to the OMC-R (through the Alarm Virtual Circuit) requesting that the
BSS informs the OMC-R of its current state.
The BSS responds to the OMC-R request for status, by either sending a good health indicator or
an alarm indicating that there is something wrong with the BSS.
If the BSS informs the OMC-R that it is not functioning correctly, the OMC-R generates an alarm
for that BSS. The OMC-R continues to send request for status messages periodically to the BSS.
And, when informed that the BSS has resumed normal operation, the OMC-R generates a clear
event (for that BSS) that clears the previous alarm.
Possible causes

• The BSS has an internal protocol error.
• The Central Authority (CA) did not respond.
• The BSS site is not fully functional.
Procedure
68P02901W26-S 32-23
Nov 2007
Procedure 32-7 NE error state
1 In the Alarm window, check the error reason field in the alarm message to
determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a software
or hardware fault condition.
3 If it is a software problem, attempt to resolve the fault condition from the
OMC-R.
• Perform a remote login to check the software processing load on the BSS
to determine whether the failure occurred at the BSS.
• From the Navigation Tree, select the SITE. Choose the Display menu and
select the Contained Device option to check the individual links.
[In a TTY window, check the communication links to determine if any have
failed. Execute the state command and check the individual links].
• A wait period may be specified by the system, before the BSS begins
functioning.
• After this wait period, reset the BSS using the reset_site command.
4 If it appears that there is a hardware problem with a link or at a BSS (BSC/BTS)
site, check the operational and administrative state of the suspect equipment.

[In a TTY window, execute the state command for the SITE device to
determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a link
failure, communication failure, a hardware (board) failure and so on.
• If a link cannot be re-established by using the INS option from the Fault
Mgt menu for a link that is OOS, send a field representative to the site
to investigate and replace the link cabling. While there, check for board
failures that may relate to the functioning of the failed link.
[If an OOS link cannot be re-established by executing the ins_device command,
send a field representative to the site to investigate and replace the link
cabling. While there, check for board failures that may relate to the functioning
of the failed link].
32-24 68P02901W26-S
Nov 2007

68P02901W26-S 32-25
Nov 2007
30007. OMC: PM disconnected from DB Chapter 32: OMC-R Alarms
30007. OMC: PM disconnected from DB

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Performance Management (PM) parser has been disconnected from the OMC-R database as
part of the database maintenance procedure.
During this time, no raw statistics files are parsed and inserted into the OMC-R database.
However, once the parser is reconnected to the database, all the raw statistics files that are
back logged are processed.
The default disconnect period is 10800 seconds (three hours).
Possible causes
The parser disconnected from the OMC-R database purposely for the maintenance procedure.
Procedure
Procedure 32-8 PM disconnected from DB
Continued
32-26 68P02901W26-S
Nov 2007
Procedure 32-8 PM disconnected from DB (Continued)

database are reconnected.
This alarm is just a warning. If the parser is

disconnected too long, a Major alarm, 30004.
parserDisconnectedTooLong is generated.
occurs before the maintenance procedures for the database have
been completed.


If the disk space allocated to the raw statistics files is full,

any uploading of the statistics files stops and the system
may crash.
5 Check the omc_db_maint logs to see if the $DBMS_BIN/db_disconnect
connect parser command was executed.


manually, go to Reconnecting the PM parser manually on page
32-19.
68P02901W26-S 32-27
Nov 2007
30008. OMC: EM disconnected from DB Chapter 32: OMC-R Alarms
30008. OMC: EM disconnected from DB

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Event Manager (EM) list manager has been disconnected from the OMC-R database as
part of the database maintenance procedure.
The following conditions that apply while the EM list manager is disconnected:
• Subscription lists can be opened (and assigned to event/alarm windows).
• Subscriptions that are currently assigned to subscription lists can be displayed.
• Neither subscriptions nor subscription lists can be created, modified, or deleted.
Possible causes
The EM list manager disconnected from the OMC-R database for the maintenance procedure.
32-28 68P02901W26-S
Nov 2007
Procedure
Procedure 32-9 EM disconnected from DB
2 Review the alarm and event reports to determine the cause(s) of
this fault condition.
database will be reconnected.
This alarm is just a warning. If the parser is

disconnected too long, a Major alarm, 30004.
parserDisconnectedTooLong is generated. If alarm
30004 is present, the EM list manager has usually not
been connected either.
occurs before the maintenance procedures for the database are
completed.


If the disk space allocated to the raw statistics files is

full, uploading of the statistics files stops and the system
may fail.
Continued
68P02901W26-S 32-29
Nov 2007
Procedure 32-9 EM disconnected from DB (Continued)

5 Check the omc_db_maint logs to see if the
$DBMS_BIN/db_disconnect connect parser command was
executed.


manually, go to Reconnecting the PM parser manually on page
32-30.
Reconnecting the PM parser manually
After the omc_db_maint command has been executed when reconnecting the PM parser
manually, proceed with Procedure 32-10.
Procedure 32-10 Reconnecting the PM parser manually
1 Connect the Event Manager (EM) at the same time.

2 Verify that it has already been connected by attempting to create a
subscription list. If this fails, reconnect the EM list manager.
3 Enter the command
$DBMS_BIN/db disconnect connect em
32-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30009. OMC: DB compression failed
30009. OMC: DB compression failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: any category
Description
A compression of the software database (db) during an upload of a database has failed. In this
case, a Network Element (NE) was uploading a database to the Operations and Maintenance
Centre (OMC-R) when the compression failed.
Alarm category
This alarm is generated in any of the five following alarm categories:

• Communication.
• Quality of service.
• Processing.
• Equipment.
• Environmental.
Possible causes

• The database object does not exist.
• The UNIX compress command is not present on the system.
• The path to the UNIX compress executable is not correctly set.
• There is not enough disk space currently to backup the database.
68P02901W26-S 32-31
Nov 2007
Procedure
Procedure 32-11 DB compression failed
2 Contact the System Administrator to archive or remove log files
from the system.
3 Verify that the log file maintenance procedures currently in
operation comply with those recommended in the manual, Operating
4 Review disk space allocations to determine whether there is a disk
space shortage. Determine where the disk space shortage is located.
5 If there is not enough disk space, perform the following maintenance:
• Remove old event log files.
• Remove old software loads.
• Remove old backup databases.

6 Restart the upload after clearing out enough disk space for the
compression and upload.
32-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30010. OMC: Exceeds upper limit disk usage
30010. OMC: Exceeds upper limit disk usage

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The upper threshold of disk partitions /root, /usr, /usr/gsm/ne_data and /home have been
exceeded at the OMC-R.
The threshold limit is set as percentage of disk used in the following configuration file and can
be modified by the System Administrator $OMC_TOP/config/global/FM_audit.CNFG.
Old log files are automatically removed by the system. The OMC-R System Administrator should
raise the value of the threshold limit and archive or remove old files from the system. The
ne_data disk partition is not intended to be used to store files belonging to individual users.
Only log files older than two days are removed during the disk partition clean up.
(Todays logs are considered to be one day old, yesterdays logs are two days old).
Where lenames are logged
If the disk usage exceeds the upper limit, log files and core files are removed:
When a log file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/log_files_removed.disk partition - Unix process ID.
When a core file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/core_files_removed.disk partition - Unix process ID.
The Unix process ID refers to the process that cleans up the partition. Each partition is cleaned
up by a different process; a process is generated by fm_audit every few minutes.
The filenames are placed in /usr/gsm/current/config/fm to prevent them from being removed
during routine OMC-R maintenance. Placing these files in a different partition preserves the
information for the user.
68P02901W26-S 32-33
Nov 2007
Additional information eld Chapter 32: OMC-R Alarms
Possible causes

• The various OMC-R log files are not maintained properly.
• The various OMC-R log files are filling up too quickly for the defined maintenance
procedures.
• The upper limit threshold of disk usage was lowered in the FM_audit.CNFG file.
Procedure
Procedure 32-12 Exceeds upper limit disk usage
from the system.
3 Check the disk usage of the /usr partition or the partition to which
the error relates.
5 Raise the value of the upper threshold limit (if lower than 90%) in
the FM_audit.CNFG file. Do not raise threshold limit above 90%.
6 Investigate the necessity of increasing the regularity (frequency)
with which the various maintenance and archive scripts are run (or
executed).

8 Check the upper threshold of the following disk partitions to verify
that they are no longer exceeded.
Continued
32-34 68P02901W26-S
Nov 2007
Procedure 32-12 Exceeds upper limit disk usage (Continued)

9 If the upper threshold is exceeded, the following applies to the disk
partitions.
• /usr/gsm, /usr/gsm/ne_data,
/usr/gsm/ne_data/raw_stats and /tmp -
files are removed until the disk partition usage upper threshold
is no longer exceeded. Older files are removed first, in
succession. Files less than 2 days old are not removed.
• /home - Core files found in any home directory are removed. If

a core file not generated by an omcadmin is found, an e-mail is
sent to notify the omcadmin of the file.
• / and /solbak - No action takes place.
Disk partition file removal

If a disk partition file was removed, the
file contains the character 1 and be shown:
/usr/gsm/current/bin/fm/logs_removed.disk partition
filename.
The disk partition filenames differ from the names.
The following filenames represent the disk partitions
respectively: usr_gsm, ne_data, root but not used, home,
raw_stats, tmp, solbak but not used.
The log files removed are stored in:
/usr/gsm/current/config/fm.
68P02901W26-S 32-35
Nov 2007
30011. OMC: Exceeds lower limit disk usage Chapter 32: OMC-R Alarms
30011. OMC: Exceeds lower limit disk usage

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The lower threshold of disk partitions /root, /usr, /usr/gsm/ne_data and /home have been
exceeded at the OMC-R.
The threshold limit is set as percentage of disk used in the following configuration
file and can be modified by the System Administrator.
$OMC_TOP/config/global/FM_audit.CNFG
Possible causes
The lower limit threshold of disk usage was lowered in the FM_audit.CNFG file.
Procedure
Procedure 32-13 Exceeds lower limit disk usage
from the system.
Continued
32-36 68P02901W26-S
Nov 2007
Procedure 32-13 Exceeds lower limit disk usage (Continued)

the error relates.
5 Raise the value of the lower threshold limit (if lower than 80%) in
the FM_audit.CNFG file. Do not raise threshold limit above 80%.
executed).

8 Check the lower threshold of the following disk partitions to verify
that they are no longer exceeded.
9 If the lower threshold is exceeded, the system does nothing to the
disk partitions. The system takes action only when the upper (disk
partition usage) threshold is exceeded.
68P02901W26-S 32-37
Nov 2007
30012. OMC: Level 1/2/3 failure Chapter 32: OMC-R Alarms
30012. OMC: Level 1/2/3 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
All X.25 communication has failed on a specified port at the OMC-R.
Software layers 1, 2 and 3 have failed to communicate on the X.25 link to the System Processor
computer due to a faulty port.
Possible causes

• The physical link was removed (For example, the link is cut accidentally).
• There is a problem with the X.25 port indicated by the alarm.
• The X.25 hardware failed.
32-38 68P02901W26-S
Nov 2007
Procedure
Procedure 32-14 Level 1/2/3 failure
and so on.
• If alarms are related, refer this manual for alarm descriptions

3 Check the X.25 hardware and link cabling into the System Processor
computer.
• If any hardware or cabling is faulty, replace it.
• If not, go to step 4.
4 Check the X.25 ports used at the OMC-R. There should be 4
redundant ports available for use.
• Switch the suspect X.25 cable to a different port.
• Reconfigure the X.25 port using the manual, Installation and

Configuration: GSM System Configuration (68P02901W17).
68P02901W26-S 32-39
Nov 2007
30014. OMC: Database exceeds upper limit Chapter 32: OMC-R Alarms
30014. OMC: Database exceeds upper limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The upper threshold of database usage has been exceeded by the System Processor at the
OMC-R. The database is full.
If the database space is full, action should be taken to free up space immediately. The OMC-R
may not function correctly if it cannot write into the database.
Possible causes

• The database usage by the System Processor caused the database to reach its maximum
capacity.
• The various OMC-R databases are not maintained properly.
• The various OMC-R databases are filling up too quickly for the defined maintenance
procedures.
• The upper limit threshold of database usage was lowered.
32-40 68P02901W26-S
Nov 2007
Procedure
Procedure 32-15 Database exceeds upper limit
2 Check the database usage in the System Processor database to
which the error relates.
3 Verify that the database maintenance procedures currently in
Information: OMC-R System Administrator (68P02901W19).
4 Raise the value of the threshold database limit (if lower than 90%).
executed).
6 Review database space allocations to determine whether there is a
space shortage. Determine where the shortage is located.
7 Check the upper/lower thresholds of the databases to verify that
they are no longer exceeded.
68P02901W26-S 32-41
Nov 2007
30015. OMC: PM proxy disconnected from DB Chapter 32: OMC-R Alarms
30015. OMC: PM proxy disconnected from DB

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Performance Management (PM) proxy has been disconnected from the database at
the OMC-R. This alarm is generated for the purpose of notifying the operator that system
administration must be performed to restore the proxy.
Possible causes
The PM proxy database was disconnected for administrative purposes.
Procedure
Procedure 32-16 PM proxy disconnected from DB
2 Contact the OMC-R System Administrator to reconnect the PM proxy
to the database.
32-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30016. OMC: OSI stack error
30016. OMC: OSI stack error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
A stack error within the Open Systems Interconnection (OSI) machine at the OMC-R has
occurred. This alarm is generated for the purpose of notifying the operator of the failure to send
a message or receive a reply from the Operator Services System (OSS).
Possible causes
The OSI machine failed.
Procedure
Procedure 32-17 OSI stack error
2 Contact the OMC-R System Administrator to check the OSI machine
and investigate any hardware or software failures.
68P02901W26-S 32-43
Nov 2007
30017. OMC: CSFP download failed Chapter 32: OMC-R Alarms
30017. OMC: CSFP download failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
A software download to the Code Storage Facility Processor (CSFP) has failed. The download
originated from the Configuration Management (CM) Management Information Base (MIB)
at the OMC-R.
It is normal to have single DownloadConnectedEvent and DownloadDisconnected

messages generated at the beginning of a download.
Possible causes

• The software protocol contained errors.
• The Operations and Maintenance Link (OML) was broken.
• The BSS is experiencing problems rendering it unable to accept a download.
• The load file contains errors.
• The maximum number of downloads is already in progress.
32-44 68P02901W26-S
Nov 2007
Procedure
Procedure 32-18 CSFP download failed
at the OMC-R.

option from the Fault Mgt menu to re-establish
a broken link. If the link remains OOS, go to step 5.

that is Out Of Service (OOS) to re-establish a broken link. If the
link remains OOS, go to step 5].
• Check for software load and protocol errors by examining

the audit files stored on the system processor in the file:
$OMC_TOP/logs/omcaudityymmdd
• Verify that x25_config file download X.25 addresses match the

DOWNLOAD X.25 addresses in the BSS Detailed View.
• Restart the download at a later time if the maximum number of

downloads were in progress at the time the failure occurred.
Continued
68P02901W26-S 32-45
Nov 2007
Procedure 32-18 CSFP download failed (Continued)

5 If it appears there is a hardware problem with a link or at a BSS

and so on.
• If a link cannot be re-established by using the INS option

from the Fault Mgt menu for a link that is OOS, send a field
representative to the site to investigate and replace the link
cabling. While there, check for board failures that may relate
to the functioning of the failed link.
command for a link that is OOS, send a field representative to the
site to investigate and replace the link cabling. While there, the field
representative should check for board failures that may relate to
the functioning of the failed link].

32-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30018. OMC: DB uncompression failed
30018. OMC: DB uncompression failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Any category
Description
An uncompression or recompression of the software database during an upload (of a database)

from a Network Element (NE) to the OMC-R has failed.
The activate_db utility could not uncompress or recompress a backup database for the selected
NE in $DBROOT/BSS/<BSSspecific>.
Alarm category
This alarm is generated in any of the five following alarm categories:

• Communication.
• Quality of Service.
• Processing.
• Equipment.
• Environmental.
68P02901W26-S 32-47
Nov 2007
Possible causes

• The activate_db utility checks (for the existence of a backup for the currently active
database of the NE in $DBROOT/BSS/<BSSspecific>).
• Each backup database is uncompressed, compared to the active database and

then, recompressed. If an uncompression or recompression of any backup
database fails, the following message is displayed on the xterm window:
Error: Unable to un(re)compress a backup database Unable to check if this is
a backup
• A processingFailureEvent (OMC-R alarm - Minor severity) is also sent to the Event

Management application and can be subscribed to by any operator.
• There is not enough disk space to backup the database causing the compression to fail.
Procedure
Procedure 32-19 DB uncompression failed
2 Review the alarm and event reports to determine the cause of this
fault condition.
3 Check the backup database(s) for the NE on which the activate_db
utility is running.

5 Restart the upload after clearing out enough disk space for the
compression and upload.
32-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30019. OMC: Database exceeds lower limit
30019. OMC: Database exceeds lower limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The lower threshold limits of database usage have been exceeded by the System Processor at
the OMC-R. Current database usage is high and requires that space be made available by
expanding the lower database limit.
This fault condition could occur if the database space usage is high. Action should be taken to
free up space in the database immediately. If the database becomes full, the OMC-R may not
function correctly because it may not have the ability to write into the database.
The databaseUpperlimit alarm indicates that the database is full.
68P02901W26-S 32-49
Nov 2007
Possible causes

• The database usage by the System Processor caused the database to reach its maximum
capacity.
• The various OMC-R databases are not being maintained properly.
• The various OMC-R databases are filling up too quickly for the defined maintenance
procedures.
• The upper limit threshold of database usage was lowered.
There is still room in the database. However, the OMC-R System Administrator
should keep a close watch on the space used.
Procedure
Procedure 32-20 Database exceeds lower limit
2 Check the database usage in the System Processor database to
which the error relates.
3 Verify that the database maintenance procedures currently in
4 Raise the value of the threshold database limit (if lower than 90%).
executed).
6 Review database space allocations to determine whether there is a
space shortage. Determine where the shortage is located.
7 Check the upper/lower thresholds of the databases to verify that
they are no longer exceeded.
32-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30020. OMC: Version query failed
30020. OMC: Version query failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC/FMIC

Severity Level: Critical/Major
Description
A software version inquiry (audit query) performed between a BSS and the OMC-R failed.
This alarm is generated when a software mismatch occurs between the current BSS software
versions residing at the OMC-R and the BSS during a software version query.
A variety of OMC-R-to-BSS software mismatches can occur causing this alarm to be generated.
This alarm applies to mismatches of the following software.
• The BSS software load version.
• The CSFP software load version.
• The BSS database level number.
• The CSFP database level number.
Denitions
Version query is a request from the OMC-R to the BSS for the current software load version
and the database level number.
Software load version is the version associated with the Code Storage and Facility Processor
(CSFP) or the Base Signaling Processor (BSP).
Database level number is a four digit hexadecimal value associated with the database at a
specific BSS site within a network. This BSS database level number is incremented each time a
change is made to a database at a specific site.
68P02901W26-S 32-51
Nov 2007
Version query initiation
A version query is initiated if there is a system configuration change. Any of the following state
changes can be related to this fault condition.
• An OML state change: to Busy-Unlocked.
• A CSFP state change: from Busy-Unlocked to another state, or from another state to
Busy-Unlocked.
The version queries are not always generated because of a fault condition.
For example, a version query is initiated for a CSFP when a CSFP transitions onto the LAN; or
when the Status CSFP window is opened through the Load Management window.
When the active BSP transitions to a Busy-Unlocked state and then, the OML comes into service.
Multiple alarm severities
Numerous fault conditions can cause the software version inquiry to fail. As a result, three
distinct 30020 alarms can be generated:
OIC - Critical or OIC - Major or FMIC - Major.
Possible causes

• A mismatch occurred between current software versions at the OMC-R and a specific BSS.
• A mismatch occurred between current CSFP software versions at the OMC-R and a BSS.
• A mismatch occurred between current software database level numbers at the OMC-R
and a BSS.
• A mismatch occurred between current CSFP software database level numbers at the
OMC-R and a BSS.
32-52 68P02901W26-S
Nov 2007
Error reason codes
One of the following error codes is displayed in the alarm output. The error code indicates the
fault condition that caused this alarm to be generated.
• Network element SW load does not exist at OMC-R (BSP).
• Network element SW load does not exist at OMC-R (CSFP).
• Current Software does not match BSP code version.
• OMC-R and NE database level number mismatch (BSP).
• Current CSFP Load does not match CSFP code version.
• OMC-R and NE database level number mismatch (CSFP).
• CSFP is not code loaded.
• No CSFP configured at NE but Current CSFP Load set at OMC-R.
• NE has CSFP but Current CSFP Load is not set at OMC-R.
• CSFP is code loaded but Current CSFP Load is not set at OMC-R.
Procedure
The following section provides two fault resolution procedures for the various fault conditions
that can cause the 30020 OMC-R alarm to occur. One procedure for the FMIC-Major 30020
alarm; the other for the OIC Critical or OIC Major 30020 alarm.
Before proceeding, check the 30020 alarm output message to determine the alarm type,
severity, and error reason code for this alarm.
Only an experienced OMC-R Operator or System Administrator should resolve the

following software version discrepancies using the procedures shown in this section.
Procedure for FMIC - Major alarms
In this case, either a BSS software version or the (BSS) CSFP software version has mismatched
with the version held at the OMC-R for that BSS. Perform the following procedure to resolve
the alarm.
68P02901W26-S 32-53
Nov 2007
Procedure 32-21 Procedure for FMIC - Major alarms
1 Check the software and CSFP load versions for the specific BSS at
both the OMC-R and the BSS site.
• Access the Load Management window by clicking the Load

Mgmt icon.
• Check the BSS software load versions and CSFP software load
versions displayed.
2 In the Load Management window, check the BSS database level
number for the specific BSS at both the OMC-R and the BSS site.
• From the top menu bar, select > Database > Database
information from the pull-down menu.
• A report showing the current database level number is

displayed.
3 Determine which type of software mismatch has occurred by
cross checking the software shown at the OMC-R with that
(software) shown at the BSS. From the Navigation Tree, open the
Detailed View for the BSS. In the Identification section, the
OMC/NE load version displays the software version at the BSS.
[Execute the disp_version command at the MMI prompt to

determine what software load versions currently reside at that BSS].
4 Using this table, determine the corrective action required to resolve
the software mismatch that caused this alarm.
The following table expresses OMC-R-to-BSS software mismatches and corrective action
required to resolve an FMIC version query failure fault condition.
If the OMC-R... and that specic BSS... then, before the alarm clears,
the operator must...
current software load version current software load version download the current (BSS)
for a specific BSS is correct does not match the (BSS) software version from
software version held at the the OMC-R to the BSS.
OMC-R. The same BSS version must
exist at both the OMC-R and
the BSS.
current CSFP software load current CSFP software download the current CSFP
version for a specific BSS load version does not exist, software load version from
exists and is correct because that BSC is not yet the OMC-R to the BSS.
initialized or because the BSC
is initialized, but does not
have a CSFP In Service.
32-54 68P02901W26-S
Nov 2007
Only an experienced OMC-R Operator or System Administrator should resolve the

following software version discrepancies using the procedures shown in this section.
Procedure for OIC - Major/Critical alarms
In this case, a BSS software load version or the (BSS) CSFP software version or the BSS
database level number or the CSFP database level number has mismatched with the (BSS)
version held at the OMC-R. Perform the following procedure to resolve the alarm.
Procedure 32-22 Procedure for OIC - Major/Critical alarms
1 Check the software and CSFP load versions for the specific BSS at
both the OMC-R and the BSS site.
• Access the Load Management window by clicking the Load

Mgmt icon.
• Check the BSS software load versions and CSFP software load
versions displayed.
2 In the Load Management window, check the BSS database level
number for the specific BSS at both the OMC-R and the BSS site.
• From the top menu bar, select Database > Database

information from the pull-down menu.
• A report showing the current database level number associated

with the most recent database audit performed for that BSS is
displayed.
3 Determine which type of software mismatch has occurred
by cross checking the software shown at the OMC-R with
that (software) shown at the BSS. From the Navigation Tree,
open the Detailed View for the BSS. In the Identification
section, the OMC/NE displays the software version at the BSS.
[Execute the disp_version command at the MMI prompt to

determine what software load versions currently reside at that BSS].
4 Using this table, determine the corrective action required to resolve
the software mismatch that caused this alarm.
68P02901W26-S 32-55
Nov 2007
The following table expresses OMC-R-to-BSS software mismatches and corrective action
required to resolve an OIC version query failure fault condition.
If the OMC-R... and that specic BSS... then, before clearing

the alarm the operator
must...
current software load version current software load version install the correct software
for a specific BSS is incorrect does not match the current load version at the OMC-R.
(or does not exist) (BSS) software load version If necessary, upload the
held at the OMC-R. associated database from
the BSS. Then, from the
Navigation Window, INS
Refer the Note the OML to ensure that the
following this table. correct software load is set at
the BSS.
current CSFP software load current CSFP software install the correct
version for a specific BSS is load version exists and, CSFP software load
incorrect (or does not exist) lanloading has been detected version at the OMC-R.
To check for lanloading, Perform a CSFP download
review the output from the in order to synchronize the
disp_version command. If databases.
BSP code version 1.0.0.0 is
displayed, lanloading was
used to load the BSS.
current database level current database level download the correct BSS
number within the dbroot number is incorrect. database from the OMC-R to
directory for a specific BSS is the BSS.
correct
current database level current database level upload the correct BSS
number within the dbroot number is correct. database from the BSS to the
directory for a specific BSS is OMC-R.
incorrect
current CSFP database level current CSFP database level download the correct CSFP
number within the dbroot number is incorrect. database to the BSS.
directory for a specific
BSS is correct
Refer the Note

following this table.
• If this software mismatch was caused by a single BSS software mismatch

between the OMC-R and a specific BSS, the 30020 alarm displays a severity level
of a Major. (Check for lanloading at that BSS, it may have caused the mismatch).
If however, the software mismatch has occurred because the software is not
installed at the OMC-R (or it does not exist), a Critical alarm results.
• This mismatch generally occurs during a system migration.
32-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30021. OMC: OMC overloaded with events
30021. OMC: OMC overloaded with events

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The pace (and quantity) of events arriving at the Event Router queue at the OMC-R is excessive.
As a result, a backlog of events is occurring and the OMC-R is becoming overloaded.
This alarm is generated to notify OMC-R software applications and operators that the Event
Router (group read) queue size has exceeded the established limit and is becoming overloaded
with events.
This Event Router group read queue size limit is comprised of a threshold which
may be set by the user.
Possible causes

• A babbling device in the network is overloading the OMC-R with events.
• There is a performance problem on the System Processor.
• There is a slow communication link to the Man Machine Interface (MMI).
68P02901W26-S 32-57
Nov 2007
Procedure
Procedure 32-23 OMC overloaded with events
3 OMC-R System Administrator: Determine why so many events
are arriving at the OMC-R. If there are a large number of similar
alarms, they could be throttled or blacklisted. See alarm handling
procedures in Chapter 3 of this manual. For details on blacklisting,
refer to the manual, OMC-R Online Help, Network Operation).
4 OMC-R System Administrator: Determine whether a slow
communication link to an MMI is causing a backlog of events.
Administrator: Check the performance of the System Processor.
32-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30022. OMC: Events discarded due to OMC overloading
30022. OMC: Events discarded due to OMC overloading

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The pace (and quantity) of events arriving at the OMC-R is so excessive that the OMC-R is
overloaded. As a result, the event messages are now being discarded.
This alarm is generated to notify OMC-R software applications and operators that the Event
Router (group read) queue size has exceeded the established limit and is currently overloaded
with events. When officially overloaded, all of the event messages in the group read queue
are discarded without processing or logging.
This Event Router group read queue size limit is comprised of a (configurable)
threshold which may be set by the user.
Possible causes

• A babbling device in the network is overloading the OMC-R with events.
• There is a performance problem on the System Processor.
• There is a slow communication link to the Man Machine Interface (MMI).
68P02901W26-S 32-59
Nov 2007
Procedure
Procedure 32-24 OMC overloaded, events discarded
3 OMC-R System Administrator: determine why so many events
are arriving at the OMC-R. If there are a large number of similar
alarms, they could be throttled or blacklisted. See alarm handling
procedures in Chapter 3 of this manual. For details on blacklisting,
refer to the manual, OMC-R Online Help, Network Operation.
4 OMC-R System Administrator: Determine whether a slow
communication link to an MMI is not causing a backlog of events.
Administrator: Check the performance of the System Processor.
32-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30023. OMC: Download disabled
30023. OMC: Download disabled

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A software download to the Network Element (NE) from the OMC-R has been disabled or
aborted. Either an OMC-R operator or an automatic downloader has disabled the ability to
download after a conventional download was aborted.
It is normal for a DownloadConnectedEvent and a DownloadDisconnected message to

be generated at the beginning of a download.
Possible causes

• The download is disabled manually because the X.25 link was being reconfigured on the
System Processor computer.
• The download is automatically disabled because a conventional download to a NE was

aborted.
68P02901W26-S 32-61
Nov 2007
Procedure
Procedure 32-25 Download disabled
2 Review the alarm and event reports to determine what caused this
fault condition.
3 Determine whether the X.25 link was being reconfigured on the
System Processor.
• If so, wait for the reconfiguration of the X.25 link to finish. Go

to step 4.
• If not, go to step 4.
4 Check to see if another operator has disabled downloading or has
aborted a conventional download to a NE.
5 When downloading can be restored, enable it through the Load
Management GUI.
6 Re-initiate the software download.
32-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30024. OMC: CSFP swap failed
30024. OMC: CSFP swap failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The OMC-R failed to execute a swap of a Code Storage Facility Processor (CSFP) at a BSS. The
CSFP swap was requested by the Base Station, but was not accepted and/or completed by the
OMC-R due to either a software or hardware problem.
Possible causes

• The BSS may have rejected the request for the swap.
• The swap request may have timed out in the system.
• The System Processor may have failed before the directory swap could be completed. (In
this case, the BSS would have accepted the swap request already).
Procedure
Procedure 32-26 CSFP swap failed
2 Review the alarm and event reports to determine what caused this
fault condition.
3 Check the OMC-R connection to the BSS involved in the swap.
4 Check the BSS (software) for which the swap is being attempted to
determine why the swap is rejected or timed out.
68P02901W26-S 32-63
Nov 2007
30025. OMC: NMC agent error Chapter 32: OMC-R Alarms
30025. OMC: NMC agent error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Processing/Communication
Description
A Network Management Centre (NMC) mediation device (agent) has encountered either an
Open Systems Interconnection (OSI) error or an error due to one or more timeouts received
while waiting for a response from the host processor.
Depending on the type of error that has occurred, either a Communication or Processing fault
condition is being generated when the NMC attempts to interact with the OMC-R.
Possible causes

• A no response condition may have resulted when either the host application process did not
respond properly to a message or the machine receiving the message is not able to respond.
A time out may have occurred (a timer may have expired) while awaiting a response
from the Operator Services System (OSS).
A maximum number of retries attempted for Quality of Service alarm.
• A Communications error between two processors may have occurred: the connection
between processors is broken; or the address of the remote processor is incorrect.
• A Common Management Information Service Element (CMISE) service error is received:

data received by remote processor is rejected due to CMISE error.
• A no information available condition may have occurred in the system: Internal software
errors in the Open Systems Interconnection (OSI) processor may have caused this
condition.
• A Software Object (Q3) condition may have occurred:

An attempt to delete a software object with Q3 children.
An attempt to create a software object with no Q3 parent.
32-64 68P02901W26-S
Nov 2007
A software object creation is waiting for a valid Q3 naming attribute value.
An attempt to change a naming attribute of an existing Q3 software object.
• An inability to transmit a notification to the Manager.
• The agent event queue may have overflowed.
• A disk space shortage may have occurred.
Procedure
Procedure 32-27 NMC agent error
2 Review the alarm and event reports to determine the cause(s) of
this alarm.
3 Follow a course of action highlighted for the errors featured below.
The table below suggests additional fault resolution actions for the
operator based on the reason received with this alarm. The operator
actions apply only to the reasons shown in the table.
Additional suggestions for fault resolution
The table below suggests additional fault resolution actions for the operator based on the reason
received with this alarm. The operator actions apply only to the reasons shown in the table.
If the reason for the error is... Then...

(timer) time out Inform the Network Manager or administrator
of the no response condition. Determine
which is faulty: the host application or the
machine.
communications error between two Inform the Network Manager or administrator
processors of the communications error condition.
Determine where the processor errors are
occurring.
Continued
68P02901W26-S 32-65
Nov 2007
If the reason for the error is... Then...

CMISE service error Determine where the internal software errors
in the OSI processor occurred. Review the
omc audit file. Inform the Network Manager
or administrator of the no information
available condition.
no information available Inform the Motorola field representative of
the condition.
maximum number of retries Inform the Network Manager or administrator
of the communications error condition.
32-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30026. OMC:
Neighbor statistics table exceeded the congured size
30026. OMC: Neighbor statistics table exceeded the

congured size
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The Error Id related to the parser has detected that the number of statistics contained in the
Neighbor Statistics table at the OMC-R exceeded the established limit.
The actual limit for the Neighbor Statistics table is set by way of the environmental
variable, PM_MAX_NEIGHBOURS. The default value for this variable is 880.
Possible causes
The neighbor statistics being generated within the system have become excessive.
68P02901W26-S 32-67
Nov 2007
Procedure
Procedure 32-28 Neighbor statistics table exceeded the congured size
2 Determine whether the environmental variable
(PM_MAX_NEIGHBOURS) is set to an appropriate level in
the system.
The environmental variable, PM_MAX_NEIGHBOURS

defaults to a value of 880.
3 Perform one of the following tasks to resolve this fault condition:
• Remove some neighbor statistics from the Neighbor Statistics

table.
• Disable the neighbor statistics currently being uploaded.

4 Execute Performance Management (PM) database maintenance:
• Disconnect the parser from the database.
• Delete statistics from the Neighbor Statistics (nbr_statistics)

table.
• Reconnect the parser to the database so that the system can

resume collecting PM statistics.
32-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30027. OMC: Supplemental download failed
30027. OMC: Supplemental download failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The attempted supplemental downloading to the Network Element (NE) has either been rejected
or has failed in progress at the OMC-R.
This fault condition may have occurred because the maximum number of downloads may already
be in progress. Other possibilities include that a (supplemental) download is aborted by the
operator or a COLR is received during the download causing it to fail.
Or one or more errors may have occurred in one of the software-related categories described
under the Possible causes section: X.25 link-related errors, database configuration errors,
Network Element (NE) errors, software protocol errors, or Inter-Process Communication (IPC)
errors.
This alarm applies only to BSSs using GSR2 (1.5.0.0) or previous releases.
Supplemental downloads are not performed for BSSs using GSR3 software and
beyond.
Possible causes

• X.25 errors.
The X.25 board has been shutdown.
The X.25 data cannot be read.
The X.25 data cannot be written.
68P02901W26-S 32-69
Nov 2007
• Configuration errors.
An Error in reading timeout configuration data has occurred.
The object database cannot be accessed.
A Memory allocation error has occurred.
An Unknown error has occurred.
A Downloader configuration error has occurred.
An error reading an object has occurred.
An error in block information has occurred.
An error in burst information has occurred.
An error in descriptor acknowledge message has occurred.
• NE errors.
The NE is requesting an object with bad version number.
The NE is requesting an unknown object.
The NE clears call in ROM.
Downloading disabled to this NE.
• Protocol errors.
A Protocol state violation has occurred.
A Software version conflict has occurred.
There are too many retries in protocol.
A protocol violation has occurred.
The protocol has timed out.
An invalid message was received by protocol.
The protocol manager cannot be contacted.
The protocol manager cannot be contacted for purpose of registering.
The protocol manager process cannot be contacted.
A Polling error has occurred.
32-70 68P02901W26-S
Nov 2007
• IPC errors.
A Failure to create IPC channel group has occurred.
An Error reported in IPC receive.
Error getting Configuration Manager (CM) channel ID.
Error sending IPC message to CM.
Error getting load details from CM.
• A supplemental download has been aborted.
• A COLR was received during a supplemental download.
Procedure
Procedure 32-29 Supplemental download failed
2 Confirm that the X.25 link reconfiguration exists at the OMC-R, at
the Packet Switch and at the BSS.
3 After determining which error reason was displayed in the alarm
message, refer to the fault isolation or resolution procedures in
the manual, Operating Information: OMC-R System Administration
(68P02901W19).
If the supplemental download is currently in progress,

retry the (supplemental) download upon its completion.
4 If this problem persists, contact Motorola Customer Network
Resolution Centre for assistance in resolving this fault condition.
68P02901W26-S 32-71
Nov 2007
30029. OMC: Active alarms exceed upper limit of 95% Chapter 32: OMC-R Alarms
30029. OMC: Active alarms exceed upper limit of 95%

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The number of alarms contained in the Active Alarm List (table) at the OMC-R has exceeded the
established upper threshold (limit) of 95%.
This alarm is generated when the capacity for OMC-R alarm entries on the active alarm list has
reached the upper threshold. At the upper threshold the OMC-R alarm list is 95% full. When the
list reaches 100% full, there are no more available entries in the list. Consequently, the alarm
list (table) does not have the capacity to accept any more alarms.
When this fault condition occurs, one (or more) of the alarms on the current OMC-R active
alarm list must be removed before the system can clear this alarm (30029). The active FMIC
alarms on the list are removed only as the fault conditions causing them have been resolved.
The active OIC alarms must be removed from the list by the operator after the fault conditions
causing them have been resolved.
The default for the upper threshold of the Active Alarm List table is 95% of the alarm
table capacity.
Possible causes
The number of active alarms on the OMC-R active alarm list exceeded 95%.
32-72 68P02901W26-S
Nov 2007
Procedure
Procedure 32-30 Active alarms exceed upper limit of 95%
1 OMC-R System Administrator: Determine why so many alarms are

arriving at the OMC-R.
2 When there are large numbers of similar alarms, consider throttling
or blacklisting them.
68P02901W26-S 32-73
Nov 2007
30030. OMC: Received maximum corrupt NE messages, closed OML Chapter 32: OMC-R Alarms
30030. OMC: Received maximum corrupt NE messages,

closed OML
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Link
Description
The Event Interface has received the maximum number of corrupt Network Element (NE)
messages from an X.25 event Virtual Circuit (VC) causing that Operations and Maintenance
Link (OML) to fail.
When this alarm occurs, the Event Interface clears the virtual circuit. Afterward, the NE opens
up a new circuit.
Under this condition, the OMC-R to Network Element (NE) Interface circuitry experiences
an X.25 link failure.
Alarm category
This alarm is actually a communication failure which is denoted as a link failure. Other link
alarms are shown as communication failures within the system, not as link failures.
The category of Communication failures is a broad classification. It may include any number of
failures within the GSM network circuitry. It is possible to have communication failures within
the GSM circuitry that are independent of one another.
Link failures
Link failure
A link failure occurs when the virtual circuit has been broken. A virtual circuit creates and
maintains the X.25 link (connection) between the OMC-R and a NE.
Network Elements are responsible for maintaining communication functionality for alarms,
events, uploads, downloads, and rlogin. If the virtual circuit link is broken, the OMC-R is
disconnected from the NEs thereby creating a link failure.
Types of X.25 link failures
Link failures are related to the X.25 link. A link failure may be either partial or complete.
The link may be broken for one or more of the NE-related functions: alarms, events, uploads,
downloads, and rlogin.
32-74 68P02901W26-S
Nov 2007
Partial link failure
Partial link failure for NE-related communication occurs when: one or more NE-related
functions are lost while others remain.
For example, it is possible to have a link failure for alarms while retaining rlogin capabilities.
The reason this is possible is that more than one virtual circuit may exist simultaneously; the
alarm capability may be carried by one link. The rlogin capability may continue.
Complete link failure
Complete link failure for OMC-R/NE-related communication occurs when: all NE-related
functions are lost.
For example, if the X.25 link on the OMC-R processor is stopped, every type of link or connection
to the NE fails.
Possible causes
The Event Interface has received the maximum number of corrupt NE messages.
Procedure
Procedure 32-31 Received maximum corrupt NE messages, closed OML
2 Review the alarm and event reports to determine whether this alarm
has occurred previously. Check current event logs for other alarms
which may indicate a link failure or a communication failure.
3 Monitor this fault condition. Investigate any potentially related
software faults detected. If the alarm is automatically cleared,
discontinue fault isolation.
Continued
68P02901W26-S 32-75
Nov 2007
Procedure 32-31 Received maximum corrupt NE messages, closed OML (Continued)

4 If the alarm does not clear, notify the System Administrator that the
X.25 circuit is Out Of Service (OOS).
5 Check the operational and administrative state of the X.25
connections by opening an rlogin window for the System Processor.
Continue with the following:
• rlogin to the System Processor as

omcadmin executing the command
rlogin omc_splat -1 omcadmin.
• Determine the status of each of the X.25 ports

(currently in use) by executing the command
/opt/SUNWconn/bin/x25stat -1 <portname>. (See
the example after this procedure).
6 Check the Packet Switch configuration to determine whether it has
been correctly configured (set up). If the operator(s) present do
not have sufficient information and/or expertise to determine this,
contact MCSC for assistance.
7 If the fault condition persists after receiving the assistance of MCSC,
send a field representative to the site to investigate.

Fault code (device identifier, alarm number, and alarm description), so that the
relevant troubleshooting procedure can be quickly accessed.
Site data. For example, site number, the state of the device, the cage number
and slot numbers.
Example
If the command, x25stat -1 port1a is entered, the output generated should be like the following:
PER LINK STATISTICS FOR X25

----------------------------
Link : 0
------------------------------------------
State : Connected and resolved DXE
------------------------------------------
32-76 68P02901W26-S
Nov 2007
Packet type TX RX
Call 2204 2672
Call accept 10 884
Restart 0 1
Restart confirm 1 0
RNR 0 0
RR 0 0
Resets 0 0
Reset confirms 0 0
Diagnostic 0 0
Interrupts 0 0
Registration 0 0
Reg confirm 0 0
Packets(total) 102566 52794
Bytes(total) 9720342 4971835
If the State of the link displayed in the output shows that the X.25 link is Connected, the link is
functional.
68P02901W26-S 32-77
Nov 2007
30031. OMC: Resync timed out, no response from NE Chapter 32: OMC-R Alarms
30031. OMC: Resync timed out, no response from NE

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The Event Interface (EI) has failed to return a response message from the BSS before the Resync
response timer expired. As a result, the requested resynchronization of the OMC-R failed.
Possible causes

• The Network Element is too busy.
• The em_main is overloaded with activity or alarms.
Procedure
Procedure 32-32 Resync timed out, no response from NE
2 Review the alarm and event reports to determine
whether this alarm has occurred previously.
Check current event logs for other alarms which may indicate a
processing failure.
3 Monitor this fault condition. Investigate any potentially related
software faults detected. If the alarm clears, discontinue fault
isolation.
Continued
32-78 68P02901W26-S
Nov 2007
Procedure 32-32 Resync timed out, no response from NE (Continued)

4 Verify that the version of the BSS software shown at the OMC-R
matches the version present at the BSS. From the BSS perspective,
check the BSS software version:
• From the Navigation Tree, open the Detailed View for the BSS.
In the Identification section, the OMC/NE load
version displays the software version at the BSS.
Execute the disp_version command to

display the software version at the BSS.
From the OMC-R perspective, check the BSS software version:
• Click on the Config Mgmt icon on the Front panel GUI.
• Select Navigation Form using the pull-down menu.
• On the Navigation Form, position the mouse pointer on the

BSS and click on BSS.
• On the Navigation Form, using the pull-down Edit menu,

select Detailed View of the BSS to display the current BSS
software version.
5 If the system does not display the software version information,
attempt a Resync.
• Click on the Admin icon on the Front panel GUI.
• From the Admin Options window, select Resync Scheduler

to display the status of the current (scheduled) Resyncs.
Continued
68P02901W26-S 32-79
Nov 2007
Procedure 32-32 Resync timed out, no response from NE (Continued)

6 Check the omc audit file on the OMC-R System Processor to
determine whether any errors have occurred. Use one of the
following methods.
• Edit and search through the omc audit file for error strings.
For example, the operator could search for the strings: Error,
error, failed and so on.
• Find the specific time within the omc audit file and search for
error messages. This method can be used only if the operator
knows the actual (or an approximate) time at which the error(s)
have occurred.
The operator must make note of this information (time/error
messages) in the event it is necessary to contact MCSC for
assistance.
• If no error(s) have been found (in the omc audit file) using
either of the methods above, attempt another Resync.
If the condition persists, it is recommended that the

operator contact MCSC for help in resolving the fault
condition.
32-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30032. OMC: Resync timed out, all resync events not received
30032. OMC: Resync timed out, all resync events not

received
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The Event Manager (EM) failed to send a response message indicating that EM had finished
processing the expected event messages before the Resync response timer expired.
This fault condition was generated because the EM did not receive the appropriate number of
Resync events. Consequently, the EM did not respond within the allotted time period. As a
result, the requested resynchronization of the OMC-R failed.
Possible causes
The resync controller is faulty.
Procedure
Procedure 32-33 Resync timed out, all resync events not received.
2 Review the alarm and event reports to determine whether this alarm
has occurred previously. Check current event logs for alarms which
may indicate a processing failure.
Continued
68P02901W26-S 32-81
Nov 2007
Procedure 32-33 Resync timed out, all resync events not received. (Continued)
3 Repeat the OMC-R resync.
• Click on the Admin icon on the Front panel GUI.
• Select Resync Scheduler from the Admin Options window to

display the status of the current (scheduled) resyncs.
4 Check the omc audit file on the OMC-R System Processor to
determine whether any errors have occurred. Use one of the
following methods.
• Edit and search through the omc audit file for error strings.
For example, the operator could search for the strings: Error,
error, failed and so on.
• Find the specific time within the omc audit file and search for
error messages. This method can be used only if the operator
knows the actual (or an approximate) time at which the error(s)
have occurred.
The operator must make note of this information (time/error
messages) in case it becomes necessary to contact MCSC for
assistance.
• If no errors have been found (in the omc audit file) using either
of the methods above, go to step 5.
5 Monitor this fault condition.
• If the alarm clears, discontinue fault isolation.
• If the alarm continues, contact MCSC as this fault condition

may indicate a software problem.
32-82 68P02901W26-S
Nov 2007
OMC: Cannot create further event logles in /usr/gsm/ne_data
30033. OMC: Cannot create further event logles in

/usr/gsm/ne_data
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Network Element (NE) database (ne_data) disk partition is full. The disk partition database
usage threshold has been exceeded to the point of filling the disk to maximum capacity (100%).
The directory /usr/gsm/ne_data is used to store the BSS databases at the OMC-R. It also stores
event logs in usr/gsm/ne_data/ev_logs. This alarm condition indicates that the directory
(/usr/gsm/ne_data) is full. As a result, it is no longer possible to write to the event logs
directory (ev_logs).
OMC-R directory maintenance
Directories must be maintained and cleaned up regularly. Otherwise, the disk space used
may exceed the existing thresholds.
For more information, refer to log file maintenance procedures in the manual, Operating
Information: OMC-R System Administrator (68P02901W19). Current log file maintenance
procedures must comply with those recommended in the System Administrator manual.
In accordance with current maintenance standards, log files older than three days are
automatically removed by the system during a disk partition clean up. The OMC-R System
Administrator must archive files that are meant to be preserved for later use or remove old files
from the system if they are no longer needed.
The ne_data disk partition is not intended to be used to store files belonging to
individual users.
68P02901W26-S 32-83
Nov 2007
Where lenames are logged
If the disk usage exceeds the upper limit, log files and core files are removed:
When a log file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/log_files_removed.disk partition - Unix process ID.
When a core file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/core_files_removed.disk partition - Unix process ID.
The Unix process ID refers to the process that cleans up the partition. Each partition is cleaned
up by a different process; a process is generated by fm_audit every few minutes.
The filenames are placed in /usr/gsm/current/config/fm to prevent them from being removed
during routine OMC-R maintenance. Placing these files in a different partition preserves the
information for the user.
Possible causes

• The directory /usr/gsm/ne_data has been allowed to fill up.
• The number of event log files present (in the directory) is excessive due to the lack of
regular directory and file (clean up) maintenance.
• The number of BSS Databases currently be maintained at the OMC-R is excessive.
• The current event traffic is so excessive that the number of event logs being created is
higher than allowed causing the directory to fill up.
Procedure
Procedure 32-34 Cannot create further event logles in /usr/gsm/ne_data
from the system.
Continued
32-84 68P02901W26-S
Nov 2007
Procedure 32-34 Cannot create further event logles in /usr/gsm/ne_data

(Continued)
the error relates.
executed).
6 If there is no available disk space, perform the following
maintenance:
• Remove core files.
• Remove tar files if not being stored for a significant purpose.

7 Check the upper and lower thresholds of the disk partitions: /root,
/usr, /usr/gsm/ne_data and /home to verify that they are no longer
exceeded.
68P02901W26-S 32-85
Nov 2007
30035. OMC: Advisory detected Chapter 32: OMC-R Alarms
30035. OMC: Advisory detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
These are failures that are recovered by the system and require no operator action. No alarm
is generated. Instead these autonomous recovery events are provided in the form of advisory
warnings to the operator.
These advisory warnings can highlight potential problems that may resurface as more serious
fault conditions.
Possible causes
N/A
Procedure
Procedure 32-35 Advisory detected
1 Monitor the reported condition.

2 Investigate any potential faults.
32-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30036. OMC: Recovered outage detected
30036. OMC: Recovered outage detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
These are failures that are recovered by the system and require no operator action. No alarm is
generated. Instead these autonomous recovery events are provided in the form of recovered
outage warnings to the operator.
These recovered outage warnings can highlight potential problems that may resurface as more
serious fault conditions.
Possible causes
N/A
Procedure
Procedure 32-36 Recovered outage detected
1 Monitor the reported condition.

2 Investigate any potential faults.
68P02901W26-S 32-87
Nov 2007
30037. OMC: UPS condition Chapter 32: OMC-R Alarms
30037. OMC: UPS condition

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Severity Level: Clear/Major/Critical
Category: Equipment
Description
Support for the Uninterrupted Power Supply (UPS) is an optional feature for the OMC-R
hardware. UPS conditions are reported to the OMC-R using alarms. The alarm severity is
dependent on the alarm. One of three alarms are reported to the OMC-R, as shown in Table 32-1.
Table 32-1 UPS condition alarm severities
Alarm Severity
OMC now powered by mains Clear
OMC now powered by the UPS Major
UPS battery low condition signaled Critical
Possible causes

• The OMC-R is now being powered by the UPS.
• The UPS battery is running low.
Procedure
Procedure 32-37 UPS condition
Inform the network manager or administrator of the condition.
32-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30038. OMC: OMC capacity ceiling violation, too many RTFs in MIB
30038. OMC: OMC capacity ceiling violation, too many

RTFs in MIB
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Severity Level: Major/Critical
Description
The number of RTFs in the MIB has exceeded the number allowed by the OMC-R license.
The alarm has a severity level of Major when the number of RTFs is greater than the RTF
Threshold: 90% of the RTF Limit as controlled by the license.
The alarm has a severity level of Critical when the number of RTFs is greater than the RTF
Limit as controlled by the license. When the alarm has critical status, a GUI dialogue message
appears saying that The OMC-R is exceeding its licensed RTF limit.
A GUI message appears with the text The OMC is exceeding its licensed RTF limit.
Possible causes
The number of RTFs on the network exceeds the number permitted by the license.
68P02901W26-S 32-89
Nov 2007
Procedure
Check the number of RTFs on the MIB using the script: /usr/gsm/cur-
rent/sbin/Count_NEs_and_RTFs. Perform the following procedure to resolve the alarm.
Procedure 32-38 OMC capacity ceiling violation, too many RTFs in MIB
If... Then...
The number of RTFs on the MIB Reduce the number of RTFs in the
exceeds the license MIB.
The number of RTFs on the MIB Check the installation of the
does not exceed the license license and reinstall the
license if necessary. Refer to
the manual, Installation and
Configuration: OMC-R Clean
Install (68P02901W47). If there
are problems with the license
contact Motorola.
32-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30039. OMC: OMC capacity ceiling violation, too many NEs in MIB
30039. OMC: OMC capacity ceiling violation, too many

NEs in MIB
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The number of Network Elements (NEs) in the MIB has exceeded the number allowed by the
OMC-R license.
A GUI message appears with the text The OMC is exceeding its licensed NE limit.
Possible causes
The number of NEs on the network exceeds the number permitted by the license.
68P02901W26-S 32-91
Nov 2007
Procedure
Check the number of NEs on the MIB using the script: /usr/gsm/cur-
rent/sbin/Count_NEs_and_RTFs. Perform the following procedure to resolve the alarm.
Procedure 32-39 OMC capacity ceiling violation, too many NEs in MIB
If... Then...
The number of NEs on the MIB Reduce the number of NEs in the
exceeds the license MIB.
The number of NEs on the MIB Check the installation of the
does not exceed the license license and reinstall the license
if necessary. Refer to Installation
and Configuration: OMC-R Clean
Install (68P02901W47). If there
are problems with the license
contact Motorola.
32-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30050. OMC: Solaris 2 hardware failure
30050. OMC: Solaris 2 hardware failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
A Fault Management (FM) audit has detected that a component within Solaris 2 hardware has
failed and is Out Of Service (OOS).
If a Solaris 2 hardware component has failed but has not been replaced, the alarm is not
reported again for the same failure. This alarm is reported for the first instance that a hardware
failure has been detected by the FM Hardware audit.
FM audit table and /usr/gsm/current/cong/fm/down
The FM Audit table is derived from the hardware_config_sun5 file. The FM audit table contains
a list of potentially faulty Solaris 2 hardware components.
The /usr/gsm/current/config/fm/down file stores the names of the Solaris 2 hardware

components detected as OOS in the previous FM Hardware audit.
If a Solaris 2 hardware component is detected as OOS in the current FM Hardware audit and
the name of that component is not listed in the /usr/gsm/current/config/fm/down file, this
alarm (30050) is generated.
If the name of that OOS component is listed in the /usr/gsm/current/config/fm/down file, this
means that the hardware component is still OOS. In this case, an alarm (30050) would have
been generated previously. Consequently, a second alarm is not generated for that same OOS
component.
This (30050) alarm remains active until the faulty hardware has been repaired or replaced
onsite. After the Solaris 2 hardware resumes functioning, this alarm is automatically cleared
from the system.
68P02901W26-S 32-93
Nov 2007
FM audit denition and frequency
The FM audit consists of four distinct audits that are set by way of the database parameters
contained in the FM_audit.CNFG file. These database parameters establish the frequency of the
audit. (That is, these parameters set how often each type of audit is generated).
The four parameters are represented:

• FM_DISK_AUD_CNT - Sets the frequency of the disk audit.
• FM_X25_AUD_CNT - Sets the frequency of the X.25 audit.
• FM_HARDWARE_AUD_CNT - Sets the frequency of the hardware audit.
• FM_DBASE_AUD_CNT - Sets the frequency of the database audit.
The default setting for the frequency of the FM Hardware audit is 2 minutes. Therefore, the FM
Hardware audit is automatically generated every 2 minutes.
It is recommended that the audit frequency be changed only if absolutely necessary. In

the event that one of the above parameters is modified, the OMC-R must be restarted.
The following is displayed in the additional information in the output for this alarm.
The Solaris 2 hardware components below are the only ones supported at the OMC-R.
Consequently, these are the only OOS components that can be displayed in the 30050 alarm
output.
Text displayed in the Additional information eld Description of the faulty Solaris 2
hardware component
cpu(x) (in SBUS slot (y)) is DOWN The CPU, where (x) is the number of the CPU.
d(x) is DOWN The hard disk, where (x) is the number of the
disk.
hih(x) is DOWN The X.25 card which is the High Speed Serial
Interface/Serial Bus (SBUS) card. Where (x)
is the number of the card and y is the number
of the slot where the SBUS is located.
32-94 68P02901W26-S
Nov 2007
Possible causes

• A Central Processing Unit (CPU) board failed.
• An X.25 port failed.
• An X.25 port is configured, but not connected to an X.25 cable.
• A hard disk failed.
Procedure
Procedure 32-40 Solaris 2 hardware failure
1 In the Alarm window, check the Additional information field in the

alarm message to determine the possible cause of this alarm; the
potentially faulty component is indicated with text format.
2 Review the previous FM Hardware audit reports to determine
whether this alarm has already occurred for the same (or another
part) of the Solaris 2 hardware.
3 Before sending a field representative to replace or connect (in the
case where the X.25 cable is not connected to a configured port) the
faulty hardware, identify the (OOS) component to be repaired.
Alarm output example
The OOS Solaris 2 hardware component is shown at the end of the third line of output as:
hih2 is DOWN.
#4 - SEEN - *NONE*.
equipmentFailureEvent - OMC - OMC0: 2 Sol2HsisHih2 - 17/02/1998 11:45:38.
[30050] Solaris2 hardware Failure - FMIC - Critical - hih2 is DOWN
68P02901W26-S 32-95
Nov 2007
30051. OMC: Corrupt NE le Chapter 32: OMC-R Alarms
30051. OMC: Corrupt NE le

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The OMC-R detected corruption in the NE.MAP file. This alarm is generated if either of the
following conditions exist:
• Wrong first character in the file.
The first character of this file must be either an * or a > character in the file.
• Incorrect number of fields in the file.
There must be 14 fields in the NE.MAP file.
Possible causes
The NE.MAP file is corrupt.
Procedure
Manually inspect the file and verify the file format is correct.
Procedure 32-41 Corrupt NE le
If the file format is... Then...

correct Clear the alarm.
incorrect Perform the appropriate corrective

action and then clear the alarm.
32-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30052. OMC: Corrupt SITE le
30052. OMC: Corrupt SITE le

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
The OMC-R detected corruption in the SITE.MAP file. This alarm is generated if either of the
following conditions exist:
• Wrong first character in the file.
The first character of this file must be either an * or a > character in the file.
• Incorrect number of fields in the file.
There must be six fields in the SITE.MAP file.
Possible causes
The SITE.MAP file is corrupt.
Procedure
Manually inspect the file and verify the file format is correct.
Procedure 32-42 Corrupt SITE le
If the file format is... Then...

correct Clear the alarm.
incorrect Perform the appropriate corrective
action and then clear the alarm.
68P02901W26-S 32-97
Nov 2007
30058. OMC: Call success rate below threshold Chapter 32: OMC-R Alarms
30058. OMC: Call success rate below threshold

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Call Success Monitor has detected a cell where the callSuccessRate statistic is below
the CALL_SUCCESS_THRESHOLD.
The CALL_SUCCESS_THRESHOLD is set at the OMC in the file /usr/omc/con-

fig/global/OMC.CNFG.
In a multiple carrier, one or more carriers may not be processing traffic, but handover
is possible. The architecture uses degradation in cell call success rate to determine a
problem.
Possible causes

• Carrier faulty.
• Switch problem.
• General radio problem.
There are a number of different reasons that can cause the decline in call success
rate other than a carrier problem.
32-98 68P02901W26-S
Nov 2007
Procedure
Procedure 32-43 Call success rate below threshold
1 Confirm that a sleeping carrier problem exists.

2 Identify the sleeping carrier.
3 Take appropriate corrective action.
68P02901W26-S 32-99
Nov 2007
30059. OMC: No calls on cell Chapter 32: OMC-R Alarms
30059. OMC: No calls on cell

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Call Success Monitor has detected a cell where there are no call setups, but call setups are
expected on that cell. That is, the cell is not a dummy and the cell is not barred.
Possible causes
The cell is a sleeping cell: no call setups are possible on the whole cell although handover is
possible.
Procedure
Procedure 32-44 No calls on cell
1 Identify the sleeping cell.

2 Determine whether the problem is in hardware or software.
3 Take appropriate corrective action.
32-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30060. OMC: No activity in timeslot
30060. OMC: No activity in timeslot

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Quality of service
Description
The Call Success Monitor has detected one or more timeslots on an RTF where there is no traffic.
Possible causes
One or more timeslots within the RTF are not processing traffic: neither call origination nor
handovers.
Procedure
Procedure 32-45 No activity in timeslot
1 Identify the RTF with sleeping timeslots.

2 Determine which timeslots are sleeping.
3 Clear the alarm manually.
68P02901W26-S 32-101
Nov 2007
30061. OMC: CPU load exceeds lower limit Chapter 32: OMC-R Alarms
30061. OMC: CPU load exceeds lower limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The lower threshold limits for CPU load have been exceeded by the System Processor at the
OMC-R. Current CPU load is high and requires that CPU activity is reduced by expanding the
lower CPU load limit. This fault condition could occur if the CPU load is high. Immediate
action must be taken to reduce CPU activity. If the CPU becomes overloaded, the OMC-R
may not function correctly.
Possible causes
• The CPU load on the System Processor has reached its maximum capacity.
• The upper limit threshold of CPU load was lowered.
Procedure
Procedure 32-46 CPU load exceeds lower limit
1 Check the CPU load on the System Processor.

2 Monitor the alarm and if it does not clear, carry out further
investigations to see which processes are using too much CPU.
3 Raise the value of the lower threshold limit
FM_CPU_LOAD_LOWER_LIMIT in the FM_audit.CNFG file. Do not
raise this threshold limit above the FM_CPU_LOAD_UPPER_LIMIT.
32-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30062. OMC: CPU load exceeds upper limit
30062. OMC: CPU load exceeds upper limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The upper threshold limit for CPU load has been exceeded by the System Processor at the
OMC-R. The CPU is completely overloaded. Immediate action must be taken to reduce CPU
activity.
Possible causes
• The CPU load on the System Processor has reached maximum capacity.
• The upper limit threshold of CPU load was lowered.
Procedure
Procedure 32-47 CPU load exceeds upper limit
1 Check the CPU load on the System Processor.

investigations to see which processes are using too much CPU.
3 Raise the value of the upper threshold limit
FM_CPU_LOAD_UPPER_LIMIT in the FM_audit.CNFG file.
68P02901W26-S 32-103
Nov 2007
30063. OMC: Memory usage exceeds lower limit Chapter 32: OMC-R Alarms
30063. OMC: Memory usage exceeds lower limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The lower threshold limits for memory usage have been exceeded by the System Processor at
the OMC-R. Current memory usage is high and requires that the memory is made available by
expanding the lower memory usage limit. This fault condition could occur if the memory usage
is high. Immediate action must be taken to free up memory. If memory usage is too high, the
OMC-R may not function correctly.
The memory usage exceeds upper limit alarm and indicates that the memory is
exhausted.
Possible causes
• The memory usage on the System Processor has reached its maximum capacity.
• The upper limit threshold of memory usage was lowered.
32-104 68P02901W26-S
Nov 2007
Procedure
Procedure 32-48 Memory usage exceeds lower limit
1 Check the memory usage on the System Processor.

investigations to see which processes are using too much memory.
3 Raise the value of the lower threshold limit
FM_MEM_USE_LOWER_LIMIT in the FM_audit.CNFG file. Do not
raise this threshold limit above the FM_MEM_USE_UPPER_LIMIT.
68P02901W26-S 32-105
Nov 2007
30064. OMC: Memory usage exceeds upper limit Chapter 32: OMC-R Alarms
30064. OMC: Memory usage exceeds upper limit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The upper threshold for memory usage has been exceeded by the System Processor at the
OMC-R. Memory is completely exhausted. Immediate action must be taken to free up memory.
Possible causes
• Memory usage by the System Processor has reached maximum capacity.
• The upper limit threshold of memory usage was lowered.
Procedure
Procedure 32-49 Memory usage exceeds upper limit
1 Check the memory usage on the System Processor.

investigations to see which processes are using too much memory.
3 Raise the value of the upper threshold limit
FM_MEM_USE_UPPER_LIMIT in the FM_audit.CNFG file.
32-106 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30065. OMC: Last MTL may have gone out of service
30065. OMC: Last MTL may have gone out of service

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
When the OML goes down, the OMC checks the state of the MTLs for the BSS in question. If the
only MTLs in a Busy Unlocked state are associated with this OML, then the alarm is generated.
Possible causes
The OML link to the BSS has gone down so the OMC no longer receives alarms. If the only MTLs
in a Busy Unlocked state are on this OML the alarm is generated.
Procedure
Procedure 32-50 Last MTL may have gone out of service
1 Check that the MTLS on this OML are not all Out of Service.
68P02901W26-S 32-107
Nov 2007
30066. OMC: Database unable to allocate fragment Chapter 32: OMC-R Alarms
30066. OMC: Database unable to allocate fragment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: OMC
Description
This alarm is raised by the Performance Management statistics parser if it finds it is unable to
insert statistics into the PM database because the overnight database maintenance has failed
to prepare a table fragment. The parser has stopped inserting new statistics and stores all
statistics files with a .no_db_storage extension until the problem is corrected.
Possible causes
The overnight database maintenance has failed to complete.
Procedure
Procedure 32-51 Database unable to allocate fragment
1 Check the database maintenance log file in

/usr/omc/logs/omc_db_maint.DD.MM.YYYY for possible reasons
why the maintenance has not completed.
2 Take corrective action and rerun the maintenance manually.
3 Once the problem has been corrected and the database maintenance
has run successfully, manually parse any statistics files with a
.no_db_storage extension.
32-108 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30067. OMC: No PM database fragment available
30067. OMC: No PM database fragment available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: OMC
Description
This alarm is raised by the pm_purge_check utility that runs every hour to check that the
database maintenance has run correctly. The alarm indicates that the database maintenance
did not complete successfully and that statistics parsing stops at midnight if no corrective
action is taken.
Possible causes
The overnight database maintenance has failed to complete.
Procedure
Procedure 32-52 No PM database fragment available
1 Check the database maintenance log file in

/usr/omc/logs/omc_db_maint.DD.MM.YYYY for possible reasons
why the maintenance has not completed.
2 Take corrective action and rerun the maintenance manually.
3 Once the problem has been corrected and the database
maintenance has run successfully, the alarm will clear the next time
pm_purge_check runs (hourly).
4 Alternatively the alarm can be cleared by the operator.
68P02901W26-S 32-109
Nov 2007
30069. OMC: Maximum number of RTFs in MIB above 90% of license limit Chapter 32: OMC-R Alarms
30069. OMC: Maximum number of RTFs in MIB above

90% of license limit
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Description
A warning message is displayed to indicate that the number of RTFs in the MIB has exceeded
90% of the Capacity Limit defined by the RTF License.
Possible causes
N/A
Procedure
N/A
32-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30070. OMC: PM database is down. Unable to bring informix online
30070. OMC: PM database is down. Unable to bring

informix online
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: OMC
Description
This alarm is raised by omc_db_maint program that runs every night to maintain the Performance
Management database. The alarm indicates that omc_db_maint brought Informix engine
offline and was unable to bring back the instance online. Until corrective action is taken, the
Performance Management database is not available for any application like parser and reports.
Possible causes
Unknown.
Procedure
Procedure 32-53 PM database is down. Unable to bring Informix online
1 As the user Informix, source the Performance Management

environment by typing omc_env on the command line.
2 Check the Informix online log in /usr/informix/online.log_OMC for
possible reasons why the instance has not started.
Continued
68P02901W26-S 32-111
Nov 2007
Procedure 32-53 PM database is down. Unable to bring Informix online (Continued)

3 In particular look for SQL and ISAM errors that describe any
problems the database has encountered.
4 Take corrective action and start the
instance by running the following command:
oninit
5 Check the instance is online by running the command below:
onstat -
6 Repeat this command until you see the status online.
7 Rerun the maintenance manually.
32-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30071. OMC: License audit not available alarm
30071. OMC: License audit not available alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: OMC
Description
This alarm is raised by the License Audit tool that is triggered by the OMC-R software at
preconfigured time intervals. The alarm indicates that either no license audit is installed on the
local OMC-R or that the license audit installed on the local OMC-R is not configured.
Possible causes
The license audit is either not installed and/or not configured on the local OMC-R.
Procedure
Procedure 32-54 License audit not available alarm
1 Correctly install and configure the license audit on the OMC-R.

2 The next invocation of FMON, either manually or through the OMC-R
software, will clear the alarm.
68P02901W26-S 32-113
Nov 2007
30072. OMC: License le not available alarm Chapter 32: OMC-R Alarms
30072. OMC: License le not available alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: OMC
Description
This alarm is raised by the License Audit tool that is triggered by the OMC-R software at
preconfigured time intervals. The alarm indicates that no license file is installed on the local
OMC-R.
Possible causes
The license file is not installed on the local OMC-R.
Procedure
Procedure 32-55 License le not available alarm
1 Correctly install the license file on the OMC-R.

32-114 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30073. OMC: License violation alarm
30073. OMC: License violation alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: OMC
Description
The alarm indicates that the RTF usage for any purchasable feature has exceeded the license
agreement.
Possible causes
RTF usage for any purchasable feature has exceeded the license agreement.
Procedure
Procedure 32-56 License violation alarm
1 Once the usage for the purchasable feature is within the license agreement,
the next invocation of FMON, either manually or through the OMC-R
2 The event actualRTFUsageEvent is displayed.
68P02901W26-S 32-115
Nov 2007
30075. OMC: Invalid license le alarm Chapter 32: OMC-R Alarms
30075. OMC: Invalid license le alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: OMC
Description
The alarm indicates that the license file is invalid or syntactically incorrect.
Possible causes
The license file is invalid or syntactically incorrect.
Procedure
Procedure 32-57 Invalid license le alarm
1 Correctly install the license file on the OMC-R.

32-116 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30076. OMC: GSM/GPRS trace logs exceeds congured disk space
30076. OMC: GSM/GPRS trace logs exceeds congured

disk space
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: OMC
Description
The alarm indicates that the trace logs exceeds the configured disk space.
Possible causes
Large volume of GSM/GPRS trace data received from BSSs.
Procedure
Procedure 32-58 GSM/GPRS trace logs exceeds congured disk space
1 Cleanup the trace logs.

2 Update CT1208DISKSPACE environment variable to the maximum space
available with $OMCTOP/ne_data.
3 Update cron job to specify reduced number of days for which trace logs
should be stored (default is 5 days).
68P02901W26-S 32-117
Nov 2007
50000/50001/50002 OMC: Field engineer password to be changed Chapter 32: OMC-R Alarms
50000/50001/50002 OMC: Field engineer password

to be changed
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{27508}
Clearing Type: OIC

Category: OMC
Description
This alarm is generated when the field engineer's password has not been changed for the
specified number of days.
Possible causes
Changing the field engineering password.
Procedure
Perform the following procedure to resolve this alarm.
Procedure 32-59 OMC: Field engineer password to be changed
1 Send an OMC operator (omcadmin) to change the field engineering

password.
32-118 68P02901W26-S
Nov 2007
Chapter
33
OML Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Operation and Maintenance Link (OML) alarms are covered in this chapter and include
the following procedures:
• 0. OML: Invalid received frames - PM on page 33-3.
• 1. OML: FRMR frames - PM on page 33-5.
• 2. OML: Expiration of N2 - PM on page 33-7.
68P02901W26-S 33-1
Nov 2007
Introduction to OML alarms Chapter 33: OML Alarms
Introduction to OML alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
OML alarms
Operation and Maintenance Link (OML) alarms.
33-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. OML: Invalid received frames - PM
0. OML: Invalid received frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This statistic counts the number of the invalid frames received on the X.25/LAPD link.
For further information, refer to the OML statistics chapter in the manual, Maintenance
Possible causes
An invalid frame was received on the X.25/LAPD link.
Procedure
Perform the following step to determine if this alarm is persistently reported.

site to check the X.25/LAPD link
68P02901W26-S 33-3
Nov 2007
Procedure Chapter 33: OML Alarms

33-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. OML: FRMR frames - PM
1. OML: FRMR frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Possible causes
A frame reject message was received on the X.25/LAPD link.
Procedure

68P02901W26-S 33-5
Nov 2007

33-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. OML: Expiration of N2 - PM
2. OML: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
without success.
Possible causes
The X.25/LAPD link failed due to a hardware fault or repair action.
Procedure

68P02901W26-S 33-7
Nov 2007

33-8 68P02901W26-S
Nov 2007
Chapter
34
PBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the Processor Bus (PBUS) alarm 254. PBUS: Device failure on page 34-3.
68P02901W26-S 34-1
Nov 2007
Introduction to PBUS alarms Chapter 34: PBUS Alarms
Introduction to PBUS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PBUS alarms
the Processor Bus (PBUS) device.
The PBUS is the software device representing the Motorola Cellular Advanced Processor
(MCAP) bus.
The MCAP transports data between the GPROCs and the following full-sized digital boards:
• Multiple Serial Interface (MSI) or Transcoder (XCDR).
• Generic Clock (GCLK).
• Kiloport Switch (KSW).
• Digital Radio Interface (DRI) or DRI extended Memory (DRIM).
PBUS alarms apply only to BSC and InCell equipment.
34-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. PBUS: Device failure
254. PBUS: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The PBUS device is placed OOS due to a LANX card failure.
Possible causes
The LANX card performing arbitration for the MCAP bus failed.
Procedure
68P02901W26-S 34-3
Nov 2007
Procedure Chapter 34: PBUS Alarms

34-4 68P02901W26-S
Nov 2007
Chapter
35
PCU Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Packet Control Unit (PCU) alarms are covered in this chapter and include the following
procedures:
• 0. PCU: Last GSL failed on page 35-3.
• 1. PCU: PCU audit failure on page 35-5.
• 2. PCU: Cell mapping failure on page 35-7.
• 51. PCU: Software patch installation failure on page 35-8.
68P02901W26-S 35-1
Nov 2007
Introduction to PCU alarms Chapter 35: PCU Alarms
Introduction to PCU alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PCU alarms
Packet Control Unit (PCU) device.
35-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PCU: Last GSL failed
0. PCU: Last GSL failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The last GSL between the PCU and the BSC failed.
System action
The PCU is placed OOS.
Possible causes

• A protocol error occurred.
• A PCU processor board (PICP or PSP) is faulty.
68P02901W26-S 35-3
Nov 2007
Procedure Chapter 35: PCU Alarms
Procedure
Procedure 35-1 Last GSL failed
1 Determine if there are any GSL alarms associated with the PCU
that reported the alarm.
no GSL alarms Go to step 2.
GSL alarms Resolve the GSL alarms. After
resolving the GSL alarms, go to
step 3.
2 Reset the PCU.
3 Determine if the alarm cleared.
required.
did not clear Send a field representative to the
site to replace the PCU processor
board.

35-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. PCU: PCU audit failure
1. PCU: PCU audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: OIC

Category: Equipment
Description
The BSC failed to receive replies for 90% of the audit messages sent to the PCU. This audit
identifies communication failures and performance problems between the BSC and PCU.

first 00 to FF This byte specifies the number of messages sent.
second 00 to FF This byte specifies the number of messages received.
Possible causes

• A PCU protocol error occurred.
• The GSLs between the PCU and the BSC are faulty, but remain in service.
68P02901W26-S 35-5
Nov 2007
Procedure Chapter 35: PCU Alarms
Procedure
Procedure 35-2 PCU audit failure
1 Determine if there are any GSL alarms associated with the PCU
that reported the alarm.
no GSL alarms Go to step 2.
GSL alarms Resolve the GSL alarms. After
resolving the GSL alarms, go to
step 3.
site to replace the DPROC/MPROC
processor board.
3 Clear the alarm.
4 Reset the PCU.

35-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. PCU: Cell mapping failure
2. PCU: Cell mapping failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The PCU has failed to acknowledge the cell mapping updates due to a failure in mapping cells
between PCUs.
There is no additional data for this alarm.
Possible causes
Communication failure between BSC and PCU.
Procedure
Procedure 35-3 Cell mapping failure
1 The system action of resetting the PCU should resolve the problem. If the
alarm continues to occur, check state of BSC -> PCU communication links as
there is some instability in the communication path between PCU and BSC,
or the PCU is failing without the GSLs going OOS.
2 If the system action does not bring the PCU INS, there might be a problem at
the PCU itself, so issue a reset hard command at this PCU's EMON prompt.
68P02901W26-S 35-7
Nov 2007
51. PCU: Software patch installation failure Chapter 35: PCU Alarms
51. PCU: Software patch installation failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Software patch installation has failed on PCU.
Possible causes
The possible cause for this alarm is software error.
Procedure
Procedure 35-4 Software patch installation failure
1 Carry out the software installation again.
When the alarm occurs, the BSS backs out the patch level to 0 within BSS.
35-8 68P02901W26-S
Nov 2007
Chapter
36
PPB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the PPB alarm 0. PPB: PCI bridge failure on page 36-3.
68P02901W26-S 36-1
Nov 2007
Introduction to PPB alarms Chapter 36: PPB Alarms
Introduction to PPB alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PPB alarms
the PPB device.
36-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PPB: PCI bridge failure
0. PPB: PCI bridge failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The bridge used to communicate to the redundant side of the cage has failed.
Possible causes
Possible hardware or software processor problems.
Procedure
Procedure 36-1 PCI bridge failure
Send a field representative to the site to replace PPB board.
68P02901W26-S 36-3
Nov 2007
Procedure Chapter 36: PPB Alarms

36-4 68P02901W26-S
Nov 2007
Chapter
37
PPROC alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter describes the alarm and OMC-R troubleshooting procedures associated with
the PPROC alarms.
{28351}0. PPROC: Processor Communications Failure on page 37-2.
{28351}9. PPROC: PPROC Reset Detected on page 37-3.
{28351}22. PPROC: SWFM Indication on page 37-4.
{26740}39. PPROC: Software failure on page 37-5.
{26740}239. PPROC: Process safe test Audit Failure on page 37-6.
68P02901W26-S 37-1
Nov 2007
0. PPROC: Processor Communications Failure Chapter 37: PPROC alarms
0. PPROC: Processor Communications Failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28351}
Clearing Type: FMIC

Category: Equipment
Description
This is an alarm which indicates that the communication with the baseboard is not possible.
No additional information is displayed for this alarm.
Possible causes
• Processor failure.
• Processor peripheral failure.
• Firmware failure.
Procedure
Procedure 37-1 Processor Communications Failure
If the PPROC does not come back into service then replace the whole board.
37-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. PPROC: PPROC Reset Detected
9. PPROC: PPROC Reset Detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28351}
Clearing Type: FMIC

Category: Equipment
Description
This is an alarm software which detects the Soft or Hard reset .
Additional information field is of one-byte of the PCI event.
Possible causes
Failure of processor.
Procedure
Procedure 37-2 PPROC Reset Detected
If the PPROC does not come back into service then replace the U-DPROC2
board.
68P02901W26-S 37-3
Nov 2007
22. PPROC: SWFM Indication Chapter 37: PPROC alarms
22. PPROC: SWFM Indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28351}

Description
This alarm provides SWFM indication on a U-DPROC2 board.
Additional information field is the raw binary data of SWFM message.
Max length of Additional information field is 256.
Possible causes
A software error has occurred.
Procedure
Procedure 37-3 SWFM Indication
Maintain logs and contact Motorola Service Center.
37-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. PPROC: Software failure
39. PPROC: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm provides Fatal SWFM indication on a PPROC board.
Additional information field is the raw binary data of SWFM message header.
Max length of Additional information field is 68.
Possible causes
An unrecoverable software error has occurred.
Procedure
Maintain logs and contact Motorola Service Center.
68P02901W26-S 37-5
Nov 2007
239. PPROC: Process safe test Audit Failure Chapter 37: PPROC alarms
239. PPROC: Process safe test Audit Failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This is an alarm which indicates a software process which exists on the device has failed an audit.
The additional data is of 9 bytes.
Byte Denition
first the process ID of the process being
audited.
second and third contain the CPU number.
fourth the percentage of CPU utilization by the
process being audited.
fifth, sixth, contain the program counter which

seventh and points to the line of code the process
eighth was executing when it failed the audit.
ninth contains the reason code.
Possible causes
Failure of software process.
37-6 68P02901W26-S
Nov 2007
Procedure
1 Monitor the alarm condition.
2 If the board stays D-U, INS or execute reset_device command to reset

the board.
68P02901W26-S 37-7
Nov 2007
Procedure Chapter 37: PPROC alarms
37-8 68P02901W26-S
Nov 2007
Chapter
38
PSI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Packet Subrate Interface (PSI) alarms are covered in this chapter and include the following
procedures:
{26740}0. PSI: Re-Initialized Unexpectedly on page 38-3.
{26740}1. PSI: Hard Reset on page 38-4.
{26740}2. PSI: Watchdog timer expired on page 38-5
{26740}3. PSI: Clock B signal loss on page 38-6.
{26740}4. PSI: Clock A signal loss on page 38-7.
{26740}5. PSI: Assigned timeslot counter underflow on page 38-8.
{26740}6. PSI: Assigned timeslot counter overflow on page 38-9.
{26740}7. PSI: TDM parity error on page 38-10.
{26740}11. PSI: DSP 0 Audit Failure on page 38-11.
{26740}224. PSI: Safe test Audit Failure on page 38-27.
68P02901W26-S 38-1
Nov 2007
Procedure Chapter 38: PSI Alarms
{26740}231. PSI: TDM interface configuration failure on page 38-28.
{26740}232. PSI: Processor bus communication failure on page 38-29.
38-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PSI: Re-Initialized Unexpectedly
0. PSI: Re-Initialized Unexpectedly

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the PSI board is unexpectedly re-initialized or reset.
Possible causes
• Failure of the processor.
• Software reset.
• Re-initialization or reset through the front panel switch.
Procedure
Procedure 38-1 Re-Initialized Unexpectedly
1 After the re-initialization sequence is completed.

2 If... then...
the PSI fails INS the device and attempt to bring it back
to become B-U into service.
(Busy-Unlocked)
the device fails to replace the PSI board.
become B-U
68P02901W26-S 38-3
Nov 2007
1. PSI: Hard Reset Chapter 38: PSI Alarms
1. PSI: Hard Reset

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the PSI board is reset.
Possible causes
• A software reset.
• Reset through the front panel switch.
Procedure
Procedure 38-2 Hard Reset
If... then...
the PSI fails INS the device and attempt to bring it back
to become B-U into service.
(Busy-Unlocked)
the device still fails replace the PSI board.
to become B-U
38-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. PSI: Watchdog timer expired
2. PSI: Watchdog timer expired

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the PSI board watchdog timer has timed out.
Possible causes
Failure of the firmware or the processor.
Procedure
1 After the initiation and completion of the software reset

sequence.
2 If... then...
the PSI fails to INS the device and attempt to bring it back
become B-U into service.
to become B-U
68P02901W26-S 38-5
Nov 2007
3. PSI: Clock B signal loss Chapter 38: PSI Alarms
3. PSI: Clock B signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the PSI detects the TDM clock B failure, that is, when the clock B
signals of the PSI board goes Out Of Sync (OOS).
Possible causes
• Failure of the GCLK KSW/DSW extender B card.
• Faulty circuitry within the PSI.
Procedure
1 If... then...
the alarm is check the GCLK - peripheral boards
reported on other communications path for faults and take
boards corrective action.
2 If the GCLK - replace the PSI module.
peripheral boards
are not faulty
38-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. PSI: Clock A signal loss
4. PSI: Clock A signal loss

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the PSI detects the TDM clock A failure, that is, when the clock A
signals of the PSI board go OOS.
Possible causes
• Failure of the GCLK KSW/DSW extender B card.
• Faulty circuit within the PSI.
Procedure
Procedure 38-5 Clock A Signal Loss
1 If... then...
the alarm is check the GCLK - peripheral boards
reported on other communications path for faults and take
boards corrective action.
2 If the GCLK - replace the PSI module.
peripheral boards
are not faulty
68P02901W26-S 38-7
Nov 2007
5. PSI: Assigned timeslot counter underow Chapter 38: PSI Alarms
5. PSI: Assigned timeslot counter underow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when fewer switch-bound timeslots than the ones allocated in the ATC
register are driven on the TDM bus.
Possible causes
• Failure of the TSA RAM.
• Failure of the ATC register.
• Failure of the MCAP interface.
• Failure of the MCAP data/address lines on the backplane.
Procedure
Procedure 38-6 Assigned timeslot counter underow
If... then...
the PSI fails to INS the device and attempt to
become B-U bring it back into service.
to become B-U
38-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. PSI: Assigned timeslot counter overow
6. PSI: Assigned timeslot counter overow

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when more switch-bound timeslots are driven on the TDM bus than the
ones allocated in the ATC register.
Possible causes
• Failure of the TSA RAM.
• Failure of the ATC register.
• Failure of the MCAP interface.
• Failure of the MCAP data/address lines on the backplane.
Procedure
Procedure 38-7 Assigned timeslot counter overow
If... then...
the PSI fails to ins the device and attempt to bring it
become B-U back into service.
to become B-U
68P02901W26-S 38-9
Nov 2007
7. PSI: TDM parity error Chapter 38: PSI Alarms
7. PSI: TDM parity error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm is generated when a parity error is detected on the in-bound TDM highway.
Possible causes
• Failure of the TDM interface circuitry on the PSI.
• Failure of the TDM bus interface on the KSW/KSWX/DSWX.
• Failure of the TBUS signals on the backplane.
Procedure
Procedure 38-8 TDM parity error
If... then...
the PSI fails to INS the device and attempt to bring it
become B-U back into service.
to become B-U
38-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. PSI: DSP 0 Audit Failure
11. PSI: DSP 0 Audit Failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when a message sent to DSP 0 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 0.
Procedure
Procedure 38-9 DSP 0 Audit Failure
68P02901W26-S 38-11
Nov 2007
12. PSI: DSP 1 Audit Failure Chapter 38: PSI Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 1.
Procedure
38-12 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC
Category: Equipment
Description
fails.
Possible causes
Failure of DSP 2.
Procedure
68P02901W26-S 38-13
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 3.
Procedure
38-14 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 4.
Procedure
68P02901W26-S 38-15
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 5.
Procedure
38-16 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 6.
Procedure
68P02901W26-S 38-17
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 7.
Procedure
38-18 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 8.
Procedure
68P02901W26-S 38-19
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
fails.
Possible causes
Failure of DSP 9.
Procedure
38-20 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when a message sent to DSP 10 on a PSI board to check the DSP
status fails.
Possible causes
Failure of DSP 10.
Procedure
68P02901W26-S 38-21
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
status fails.
Possible causes
Failure of DSP 11.
Procedure
38-22 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
status fails.
Possible causes
Failure of DSP 12.
Procedure
68P02901W26-S 38-23
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
status fails.
Possible causes
Failure of DSP 13.
Procedure
38-24 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
status fails.
Possible causes
Failure of DSP 14.
Procedure
68P02901W26-S 38-25
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
status fails.
Possible causes
Failure of DSP 15.
Procedure
38-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 224. PSI: Safe test Audit Failure
224. PSI: Safe test Audit Failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the BSS detects that the PSI does not respond to the interrogation
by an external process.
Possible causes
• PSI software is hung up.
• MCAP interface software is not functioning.
• MCAP bus fails.
• Hardware problem on board causing no response.
• Loss of power to board.
Procedure
Procedure 38-25 Safe test Audit Failure
If the PSI board does not become B-U or there is an excessive recurrence of
this alarm, replace the PSI board.
68P02901W26-S 38-27
Nov 2007
231. PSI: TDM interface conguration failure Chapter 38: PSI Alarms
231. PSI: TDM interface conguration failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Description
This alarm is generated when the BSS detects that an active PSI device is not configured for the
designated TDM highway.
Possible causes
• Failure of the device.
• Incorrect functioning of the device software.
• Device is not programmed to the designated TDM highway.
Procedure
If..... Then...
the alarm is received along with follow the instructions for the corresponding
PSI alarms 254, 0 or 1 alarm.
the PSI fails to become B-U INS the device and attempt to bring it back
into service.
the device still fails to become replace the PSI board.

B-U
38-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. PSI: Processor bus communication failure
232. PSI: Processor bus communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26740}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the BSS detects that a communication link between the PSI board
and the GPROC board through the MCAP bus is lost.
Possible causes
• Removal of the PSI and/or GPROC board.
• The failure of a portion of it supports the MCAP bus access.
Procedure
If... then...
the PSI fails to become INS the device and attempt to bring it
B-U back into service.
the device still fails to replace the PSI board.
become B-U
68P02901W26-S 38-29
Nov 2007
Procedure Chapter 38: PSI Alarms
38-30 68P02901W26-S
Nov 2007
Chapter
39
PSP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The PCU System Processor (PSP) alarms are covered in this chapter and include the following
procedures:
• 0. PSP: Communication failure on page 39-3.
• 22. PSP: SWFM indication on page 39-5.
• 39. PSP: Software failure on page 39-6.
• 239. PSP: Process safe test audit failure on page 39-8.
68P02901W26-S 39-1
Nov 2007
Introduction to PSP alarms Chapter 39: PSP Alarms
Introduction to PSP alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PSP alarms
Packet Control Unit (PCU) GPRS Master Processor (MPROC).
The MPROC is the system slot processor responsible for the Compact Peripheral Component
Interconnect (CPCI). It is assigned the logical device name of the PCU System Processor (PSP)
within BSS software.
FRUs
A PSP device may be equipped on one of the FRUs shown in Table 39-1.
Table 39-1 PSP FRUs
FRU Description
Motorola MPROC A Motorola master system processor board.
Unknown MPROC A generic master system processor board.
39-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PSP: Communication failure
0. PSP: Communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The ACTIVE PSP is no longer able to communicate with the STANDBY PSP, also the redundant
MPROC is missing. This alarm is either cleared when the PCU software re-establishes
communication with the PSP and comes back in service or when the PCU software detects that
a redundant MPROC has been inserted in the corresponding slot.
If, at a future point in time, the PCU resets without a standby PSP the recovery time will
be greater than if the standby were present. Furthermore, if the active PSP fails and is no
longer usable, the PCU does not return to service until a site visit is made to replace the failed
MPROC/HSC hardware.
Additional Alarm Data
No additional information is displayed for this alarm.
Possible causes

• Undetectable software failure.
• MPROC removed from cage.
• HSC removed from cage.
• MPROC board failure.
• HSC board failure.
68P02901W26-S 39-3
Nov 2007
Procedure Chapter 39: PSP Alarms
Procedure
Procedure 39-1 Communication failure
If the PSP does not automatically return to service, send a field

representative to the site to inspect and/or replace faulty hardware (MPROC,
HSC, transition module).

39-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. PSP: SWFM indication
22. PSP: SWFM indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The system has detected a software processing error (SWFM) for a PSP.
programmers.
Possible causes
Procedure
Clear the alarm.
68P02901W26-S 39-5
Nov 2007
39. PSP: Software failure Chapter 39: PSP Alarms
39. PSP: Software failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the PSP has experienced a non recoverable software error.
programmers.
Possible causes
A critical software error.
Procedure
1 Reset the PSP.

2 Determine the state of the PSP after the reset is completed.
If the PSP is... Then...
busy-unlocked The alarm was probably caused
by a software error.
39-6 68P02901W26-S
Nov 2007

68P02901W26-S 39-7
Nov 2007
239. PSP: Process safe test audit failure Chapter 39: PSP Alarms
239. PSP: Process safe test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The PSP failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes. This alarm is generated if the system does not receive a response
to an audit from a specified PSP processor within the GPRS system.
The Additional information field includes nine bytes containing process information, as shown
in Table 39-2. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.

02 Higher priority processes prevented the process that failed to run.
Possible causes

• The PSP board is faulty.
• The PSP software being audited is faulty.
• The GDBP Hard Drive is faulty.
39-8 68P02901W26-S
Nov 2007
Procedure

field.
2 Contact a Motorola representative
2 Determine the state of the PSP after the PCU reset is completed.
If the PSP is... Then...
required.
site to attempt a manual reset and
if not successful, replace the PSP
board.

When the audit failure reason is 2 (when the board is not reset), clear the alarm
manually by resetting the PSP on/off hours as long as GPRS service is being properly
provided.
68P02901W26-S 39-9
Nov 2007
Procedure Chapter 39: PSP Alarms
39-10 68P02901W26-S
Nov 2007
Chapter
40
RSL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Radio Signaling Link (RSL) alarms are covered in this chapter and include the following
procedures:
• 0. RSL: Invalid received frames - PM on page 40-3.
• 1. RSL: FRMR frames - PM on page 40-5.
• 2. RSL: Expiration of N2 - PM on page 40-7.
• 10. RSL: Link disconnected on page 40-9.
• 11. RSL: LAPD protocol error on page 40-18.
• 13. RSL: LAPD protocol error threshold exceeded on page 40-22.
• 14. RSL: Link audit failure on page 40-25.
• 15. RSL: Too many LAPD protocol errors on page 40-27.
68P02901W26-S 40-1
Nov 2007
Introduction to RSL alarms Chapter 40: RSL Alarms
Introduction to RSL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
RSL alarms
Radio Signaling Link (RSL) device.
The specific GPROC device type used depends on system configuration. The Link Control
Processor (LCP) and the Radio System Link Processor (RSLP) control the RSL functionality.
40-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. RSL: Invalid received frames - PM
0. RSL: Invalid received frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This statistic counts the number of the invalid frames received on the LAPD link.
For further information, refer to the RSL statistics chapter in the manual, Maintenance
Possible causes
An invalid frame was received on the LAPD link.
Procedure
Determine if this alarm is persistently reported. Perform the following procedure.

68P02901W26-S 40-3
Nov 2007
Procedure Chapter 40: RSL Alarms

40-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. RSL: FRMR frames - PM
1. RSL: FRMR frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
This statistic counts the number of the frames on the LAPD link that were rejected because
Possible causes
A frame reject message was received on the LAPD link.
Procedure

68P02901W26-S 40-5
Nov 2007

40-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. RSL: Expiration of N2 - PM
2. RSL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
without success.
Possible causes
The LAPD link failed due to a hardware fault or repair action.
Procedure

68P02901W26-S 40-7
Nov 2007

40-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. RSL: Link disconnected
10. RSL: Link disconnected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An RSL disconnected on the MMS. No signaling information between the BSC and the BTS is
passed over the disconnected link.
of events:
• If software determines the MMS link has failed first, an MMS alarm is raised as
the primary alarm and you will not see an RSL10 alarm.
• If MMS thresholds are configured such that the RSL fails before the MMS
failure is signaled in software, you will first see the RSL 10 alarm, followed by
the MMS alarm.
• If the RSL fails due to a layer 2 issue only (LAPD) and the MMS is OK, then
you will see the RSL alarm only. The operator can use the OMC to determine
any devices present on the MMS (including RSLs) by clicking the MMS alarm
at the OMC.
Alarm context
The context in which this alarm is generated determines the level of complexity of the isolation
and resolution of this fault condition. This situation is more complex.
The following factors have the greatest affect on the complexity of the tasks required: the site
configuration, other alarms occurring, and the RSL link availability.
68P02901W26-S 40-9
Nov 2007
Additional information eld Chapter 40: RSL Alarms
When this alarm occurs, the site configuration determines the initial approach to isolating the
fault condition. See a description of each of the various site configurations in a forthcoming
section.
In addition, this alarm is generated concurrently with other major alarms related to the RSL link
failure. Therefore, associated fault conditions must first be prioritized and then investigated.
Last RSL link disconnected
In the event this alarm is generated for an RSL link that happens to be the last available link for
service to a remote site, the (remote) site goes Out Of Service (OOS). The following alarm is
generated: 0. Site: Last RSL Link Failure.
If the last RSL link has failed, the resulting fault condition is one of the most complex. Only an
experienced operator should attempt to resolve this fault condition.
Refer to CCITT Blue Book, Q.921 for details regarding the Data Link Layer.
Table 40-1 shows the content displayed in the Additional information field for this alarm.

first 00 to FF The first two bytes are the
reason codes.
second 00 to FF
• 00 = Normal disconnect
• C6 = XBL guard timer

expired
third 01 to 1F MMS timeslot.
fourth 0A MMS device type.
fifth 00 to FF
sixth 00 to FF MMS device identifiers.
seventh 00 to FF
40-10 68P02901W26-S
Nov 2007
Possible causes

• An XBL guard timer expired.
• One side of associated MMS is locked, causing the remote end (not locked) to raise the
MSI, GPROC, DPROC).
• Link failure affecting RSL timeslots only, for example when timeslot switching equipment
timeslot 0 is good.
• A GSL guard timer expired.
BSC-BTS Site congurations
For fault isolation and diagnostics, it is critical to determine which BSC-to-remote BTS site
configuration is present at the site receiving the alarms.
Possible congurations: BSC-to-BTS
There are three possible types of BSC-to-remote BTS site configurations:

• Star (spoke) configuration.
• Loop (opened or closed) configuration.
• Fork configuration.
Star (spoke) conguration
A star (or spoke) consists of many BTS sites. Each BTS site is connected directly to the BSC by
E1 links. A minimum of one E1 link (MMS) is required for each BTS site.
Multiple MMSs can be used to support additional traffic capacity or redundancy. A single BTS
site can have a maximum of ten MMSs. The Star (spoke) is treated as multiple open-ended daisy
chains with one BTS site per chain.
Loop Conguration: opened or closed
A loop chain consists of many BTSs connected together in a chain with at least a single E1 link
between each remote BTS site. Multiple E1 links (MMSs) can be used to support additional
traffic capacity or redundancy. A single BTS site can have a maximum of ten MMSs. There are
two types of loop configurations: open and closed.
68P02901W26-S 40-11
Nov 2007
BSC-to-BTS topology Chapter 40: RSL Alarms
Open loop
Only one end of the (BTS) chain terminates at the BSC. The other end of the chain terminates at
a BTS site. An open loop can have a maximum of 10 remote BTS sites. In this configuration,
if a BTS site goes Out Of Service (OOS), all BTS sites downstream from the failed BTS, go
OOS as well.
Closed loop
Both ends of the (BTS) chain terminate at the BSC. A closed loop can have a maximum of
10 remote BTS sites. In this configuration, if a BTS site goes OOS, all other BTS sites in the
chain remain INS.
Fork Conguration
A fork consists of either a single BTS site or chain of BTS sites connected to an intermediate
BTS site in a chain that terminates at the BSC. Fork BTS sites are connected with at least a
single E1 link between each remote BTS site.
Multiple E1 links (MMSs) can be used to support additional traffic capacity or redundancy. A
single BTS site can have a maximum of ten MMSs. The fork can be open-ended or have a
redundant loop back to a chain that terminates at the BSC.
BSC-to-BTS topology
After determining the site configuration, record the following system characteristics before
beginning fault resolution.
System characteristics
The BSC-to-remote BTS topology is specified in terms of the continuous traffic routes between
the BSC and a terminating remote BTS site. This continuous route includes all intermediate
BTSs between the BSC and the remote BTS site generating the fault condition.
A particular traffic route is specified by a unique PATH device. (Every remote BTS site in the
network must be equipped with at least one PATH device). A PATH device specifies which SITE
devices and associated MSI/MMS devices define the route. And therefore, which particular
E1 link is used between each site.
Every remote BTS site in the network must be equipped with at least one RSL. The RSL carries
signaling traffic between the BSC and the remote BTS site. A maximum of eight RSLs can be
equipped between the BSC and a BTS site. The additional RSLs provide signaling traffic load
sharing (and depending on system configuration) may provide redundancy. An RSL for a specific
site is associated with a PATH device that terminates at that same site.
40-12 68P02901W26-S
Nov 2007
The following rules apply to the BSC-to-BTS relationship:

• If all RSLs between a BSC and a remote BTS site are OOS for more than 10 minutes,
the BTS site goes OOS.
• An RSL may be OOS as a result of the associated MMS being OOS.
• An MMS may be is OOS because an associated MSI, XCDR, or Network Interface Unit
(NIU) is OOS.
In the case of a BTS site that is part of an open loop or open-ended fork, the loss of RSLs at a
site may be caused by equipment failure downstream from the failed BTS site reporting the
alarm. (Recall that in this configuration, if a BTS site goes OOS, all BTS sites downstream
from the failed BTS, go OOS as well).
Procedure
1 Refer to several current alarm report logs to determine whether the same
RSL link has reported this specific RSL alarm repeatedly.
If this alarm recurs, there may be a quality of service problem

on one of the E1 links that carries this RSL.
2 Determine whether this alarm has recurred repeatedly and consistently.
If this alarm... Then...
has not recurred Monitor this fault condition.
repeatedly over a If this alarm recurs consistently over the
short period of time next 10-30 minutes. Continue to step 3.
has recurred The RSL is not functioning and may be faulty.
repeatedly over a Continue to step 3.
short period of time
Continued
68P02901W26-S 40-13
Nov 2007
Procedure 40-4 Link disconnected (Continued)

3 In a TTY window, execute the state command to check the operational
and administrative status of the RSL, SITE(s) and the MMS related to the
RSL device(s) showing excessive alarms.
If the RSL is... Then...
busy_unlocked The alarm condition has ceased.
Further fault resolution is not required.
not busy_unlocked The RSL is OOS.
Attempt to re-establish the link by
executing the ins_device command for the RSL. If
the RSL does not return to service, continue with
step 4, otherwise, discontinue fault resolution.
4 Execute the disp_equipment command to display the active equipment
associated with the RSL and PATH devices.
• Execute the disp_equipment RSL command for the RSL that

generated this alarm; record the unique path identifier for the RSL
device. The first RSL device ID displayed represents the terminating
site of the path that the suspect RSL is using.
• Execute the disp_equipment PATH command for the PATH

associated with the suspect RSL; record the identifiers for each site
and the MSI/MMSs as specified for the PATH.
5 From the BSC, in a TTY window, execute the state command to check the
operational and administrative status of the PATH.
If the PATH is... Then...
busy_unlocked Check the alarm report log for excessive alarms
related to this fault condition.
not busy_unlocked The PATH is OOS.
If there is an MMS failure alarm, go to step 6.
If there is no MMS alarm, it is probable that the
serial data transmission carrier is operating at a
reduced quality.
Continued
40-14 68P02901W26-S
Nov 2007

6 Determine whether the MMS and/or SITE devices specified
for the PATH device are Out Of Service (OOS). From the BSC,
execute the state command for the site-related MMS that is
specified for the PATH device. The following is the correct format:
state <site> MMS <MMS device ID>.
If the MMS is... and the SITE is... Then...
INS INS It is probable that the
data path is operating
at a reduced quality.
Attempt to re-establish
the link by executing
the ins_device
command for the RSL.
If the RSL link resumes
service, continue to monitor
the system for link alarms.
If this alarm consistently
recurs, repeat step 6 before
continuing.
INS OOS It is possible that a device has
failed. Check alarm reports
and event logs for a site
failure; refer alarm pages in
this manual.
OOS INS It is possible that a hardware
device has failed. Check
alarm reports and event logs
for an MMS failure; refer
alarm pages in this manual.
Determine which T43/BIB
interconnect board is
associated with the suspect
MMS. (Refer to site-specific
documentation).
OOS OOS It is possible that both devices
have failed. Check alarm
reports and event logs for
MMS and site failures; refer
to alarm pages in this manual.
Send a field representative to
the site to service the serial
data transmission carrier
related to the faulty RSL link.
Continued
68P02901W26-S 40-15
Nov 2007

7 Determine whether the BSC-related MMS in a busy-unlocked device state.
busy_unlocked It is possible that there is an equipment failure
at the failed BTS. From the BSC, execute the
state command for the BTS that is the next one
downstream from the failed BTS. (Downstream
refers to the BTS which is the next BTS away from
the BSC).
Check if the BTS (SITE) busy-unlocked.
If yes, use the state command for each

MMS associated with the Site. Check
upstream and downstream from the BSC.
If no, the BTS (SITE) is not In Service (INS), go

to the step 9. Check if the related MMS(s)
busy-unlocked and check for a MSI failure.
not busy_unlocked It is possible that a hardware device has failed.
Check alarm reports and event logs for an MMS
failure. Determine which T43/BIB interconnect
board is associated with the suspect MMS. (It may
be necessary to refer site specific documentation).
not busy_unlocked It is possible that the equipment has failed.
Check the alarm reports and event logs
for failures of GPROCs and/or KSWs.
Check the alarm reports for failures
of TDM Bus (TBUSs) and GCLK(s).
The failure of either a GPROC or a KSW

device causes the site to reset. Such a
reset, may appear to be caused by an
RSL failure when it is not.
8 Send a field representative to the site in order to determine the quality of

the link. refer to this manual for fault resolution procedure(s) regarding
any alarm(s) related to this RSL fault condition.
9 Send a field representative to the site in order to determine the quality
of the link.
While at the site, the field representative must check the

cabling to the E1 temperature sensor. If the E1 sensor cable is
faulty, it could be responsible for taking the RSL Out Of Service
(OOS).
40-16 68P02901W26-S
Nov 2007
Wait for 10 minutes before continuing with this procedure. After waiting, if the alarm is cleared
and the RSL connection is re-established, fault isolation and diagnostics is not necessary. If the
connection is not re-established, the system goes into a Continuous Retry mode in which case,
the system attempts to re-establish the link an infinite number of times.
Only an experienced operator should attempt to resolve this fault condition.

68P02901W26-S 40-17
Nov 2007
11. RSL: LAPD protocol error Chapter 40: RSL Alarms
11. RSL: LAPD protocol error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The RSL detected a LAPD protocol error due to a problem on one of the E1 links. Calls may
be lost.

second 00 to FF LAPD error code.
third 0A MMS device type.
fourth fifth sixth 00 to FF00 to FF00 to FF MMS device identifiers.
40-18 68P02901W26-S
Nov 2007
Possible causes
The LAPD Error code included in the Additional information field corresponds to a possible
cause for the alarm, as shown in Table 40-3.
Table 40-3 LAPD error codes
Error code Description

0 or 4 Link Timeout.
Bad Configuration.
The timeslot assignments are not correct.
The connection to the physical link may have a
different protocol.
1 Sequence Error.
The physical media is faulty (for example, a noisy
communication link).
The external equipment experienced an outage.
The physical frame dropped.
Out-of-sequence frames were received.
2 or 3 Frame Rejected.
Unexpected Response Frame.
The connection is invalid.
The DACS link is physically connected to the wrong line.
5 or 8 SABM-Extended Received Link Disconnect Failure.
The nailed connection is missing.
The connection may be correct for one direction, but incorrect
for the other direction.
The physical media in one direction is faulty.
6 Bad Frame.
The remote side of the link connection sent I-frames
before the link was established.
7 or 9 Link SABM-Extended Failure.
Link Status Query Failure.
A physical link outage affected the local to
remote direction.
Procedure
68P02901W26-S 40-19
Nov 2007

2 Determine the state of the MMS identified in the Additional
information field.
busy_unlocked Send a field representative to the
not busy_unlocked Review the Alarm/Event window
for an MMS alarm and initiate
procedures.
3 If… Then…
a single RSL 3 is affected Suspect an external source.
multiple RSLs are affected Go to step 4.
4 If… Then…
multiple RSLs on same LCF are Suspect LCF GPROC fault –
affected reassign sites to confirm.
multiple RSLs on multiple LCFs Suspect TDM highway. Check for
are affected other alarms, which would indicate
TDM fault (CERM alarms or TDM
highway associated alarms) – swap
TDM to confirm.

40-20 68P02901W26-S
Nov 2007
Further tests
If the above procedure is not sufficient to isolate the problem, perform the following actions.
Procedure 40-6 Further tests
1 Carry out an end-to-end link quality test for all the 32 Timeslots using the
standard link test patterns. Ensure that over a 24 hour period, frequency,
BER and Code errors jitter and wander are within specifications.
2 Use a LAPD Q.921 protocol tester on the RSL timeslot over a larger span
of the PDU.
3 The maximum length of the LAPD error string (including the header string)
allowed by Motorola is 576 bytes.
4 Use ECT to find the E1 links where the maximum number of alarms are raised
and isolate them. Check the recent statistics history for RSL, MMS and the
link.
5 Monitor the link quality over an extended period using suitable test
equipment. Ensure that the links meet the GSM specification GSM (ITU-T
G.703/G.704).
6 Monitor the link, RSL statistics and ECT to check if the changes are effected.
If the alarms/statistics are at an acceptable level, resolve the other alarms.
Otherwise use the LAPD protocol analyzer to track the source of any RSL
alarms.
68P02901W26-S 40-21
Nov 2007
13. RSL: LAPD protocol error threshold exceeded Chapter 40: RSL Alarms
13. RSL: LAPD protocol error threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one minute period.
System action taken
The system soft resets the affected RSL.
A one byte code is displayed in the Additional information field, as shown in Table 40-4. The
code indicates where the alarm was reported.
Value (hex) Denition

01 The alarm is reported by the BSC.
05 The alarm is reported by the BTS.
Possible causes
40-22 68P02901W26-S
Nov 2007
Procedure
1 Determine the state of the RSL device.

If the RSL is... Then...
busy_unlocked The fault condition no longer
exists. If this is a recurrence of
this alarm, the E1 link is probably
faulty. Send a field representative
to the site to isolate and correct
the link fault.
2 Attempt to restore the RSL device to service.
If the RSL... Then...
the link fault.
3 In a TTY window, execute the disp_equipment RSL command for
the RSL that generated this alarm; record the unique path identifier
for the RSL device.
The first RSL device ID displayed represents the

terminating site of the path that the suspect RSL is using.
4 Determine the state of the MMS device identified in step 3.
busy_unlocked The E1 link is probably faulty.
site to isolate and correct the link
fault.
Continued
68P02901W26-S 40-23
Nov 2007

busy_unlocked The MMS device is faulty.
procedures.
not busy_unlocked The MSI device is faulty.
procedures.

40-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 14. RSL: Link audit failure
14. RSL: Link audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The RSL failed or is experiencing a performance problem.
The audit sends several messages down the RSL and counts the number of replies that are
received. This alarm is generated if the number of replies is less than the number of messages
sent.

second third fourth 00 to FF00 to FF00 to FF MMS device identifiers.
fifth 00 to FF Number of messages
received.
sixth 00 to FF Number of messages sent.
Possible causes

• A link failure previously undetected by the system.
• An RSL performance problem.
68P02901W26-S 40-25
Nov 2007
Procedure
Check the number of received replies. Perform the following procedure to resolve the alarm.
Procedure 40-8 Link audit failure
The number of replies is... Then...

zero Return the RSL to service.
not zero Send a field representative to
the site to determine the quality
of the link and take appropriate
corrective action.

40-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. RSL: Too many LAPD protocol errors
15. RSL: Too many LAPD protocol errors

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Too many LAPD Protocol errors have been received indicating poor link quality.

second 00 to FF LAPD fault code.
third 00 to FF MMS device ID.
through 00 to FF
sixth 00 to FF
Possible causes
Four or more LAPD Protocol errors were received within one second indicating major problems
with the RSL link.
68P02901W26-S 40-27
Nov 2007
Procedure
Procedure 40-9 Too many LAPD protocol errors
1 Check report logs for repeated occurrence of this alarm. If alarm occurs
more than expected, monitor the state of MMS related to the RSL and INS
the RSL device. A field representative may need to visit the site to determine
the quality of the link and adjust, correct, or replace it as necessary.
2 Refer to Alarm Handling at the OMC customer documentation. Investigate
the RSL further if this keeps happening.
40-28 68P02901W26-S
Nov 2007
Chapter
41
SBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the Serial Bus (SBUS) alarm 254. SBUS: Device failure on page 41-3.
68P02901W26-S 41-1
Nov 2007
Introduction of SBUS alarms Chapter 41: SBUS Alarms
Introduction of SBUS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
SBUS alarms
Serial Bus (SBUS) device.
An SBUS is a logical device made up of the communication path between the GPROCs and LANX
cards in a cage. The communications path includes the half-sized cards installed in the cage.
Each cage has two SBUS devices (one active and one redundant).
SBUS alarms apply only to BSC and InCell BSU-based systems (including ExCell
and TopCell) hardware.
41-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. SBUS: Device failure
254. SBUS: Device failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The SBUS device failed causing the site to reset.
This alarm is generated only for InCell BSU-based hardware (including ExCell and
TopCell).
Possible causes

• The LANX card is not correctly inserted into the backplane.
• The LANX card failed.
• The GPROC board is faulty causing it to be incapable of communication on the SBUS.
• A Bus Terminator Card (BTC) is not plugged into the backplane causing signals on the
backplane to go out of the expected range.
• A half-size card is not correctly plugged into the backplane.
• The SBUS connections on the backplane are faulty.
68P02901W26-S 41-3
Nov 2007
Procedure Chapter 41: SBUS Alarms
Procedure

41-4 68P02901W26-S
Nov 2007
Chapter
42
SITE Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The SITE alarms are covered in this chapter and include the following procedures:
• 0. SITE: Last RSL link failure on page 42-4.
• 2. SITE: BSC detected MCU to MCU communication failure on page 42-12.
• 3. SITE: Active multiplexer 0 loopback failure on page 42-15.
• 4. SITE: Standby multiplexer 0 loopback failure on page 42-17.
• 9. SITE: Active local FOX failure on page 42-28.
• 10. SITE: Standby local FOX failure on page 42-30.
• 11. SITE: Active remote FOX 0 failure on page 42-32.
• 12. SITE: Standby remote FOX 0 failure on page 42-34.
• 17. SITE: 16 kbps switching hardware required on page 42-44.
• 18. SITE: MIX board (Slot 18) communication failure on page 42-46.
• 19. SITE: Unequipped GPROC has entered the LAN on page 42-47.
• 20. SITE: Unequipped GPROC has left the LAN on page 42-51.
• 21. SITE: No clock references available on page 42-55.
• 22. SITE: Active alarm list full on page 42-58.
• 23. SITE: EMU modem card failure on page 42-60.
• 24. SITE: Site reset request on page 42-61.
68P02901W26-S 42-1
Nov 2007
Procedure Chapter 42: SITE Alarms
• 25. SITE: External power booster amplifier 1 failure on page 42-64.
• 26. SITE: External power booster amplifier 2 failure on page 42-66.
• 27. SITE: External power booster failure on page 42-68.
• 28. SITE: Database configuration and arena hardware mismatch on page 42-70.
• 29. SITE: EMU download failure on page 42-73.
• 30. SITE: NVM board failure on page 42-75.
• 31. SITE: Failure of PCMCIA card 1 on NVM board on page 42-77.
• 32. SITE: Last GBL failed on page 42-79.
• 33. SITE: BSSGP status message received from the SGSN on page 42-80.
• 34. SITE: Erroneous BSSGP message received from the SGSN on page 42-81.
• 35. SITE: Network service status message received from the SGSN on page 42-82.
• 36. SITE: Erroneous network service message received from the SGSN on page 42-83.
• 37. SITE: No NS-VC block acknowledgment from the SGSN on page 42-84.
• 38. SITE: No NS-VC unblock acknowledgment from the SGSN on page 42-85.
• 39. SITE: No NS-VC alive acknowledgment from the SGSN on page 42-86.
• 40. SITE: No NS-VC reset acknowledgment from the SGSN on page 42-88.
• 41. SITE: Last NS-VC for the PCU failed on page 42-90.
• 42. SITE: Last TRAU GDS failed on page 42-91.
• 43. SITE: Last PRP or PXP failed on page 42-92.
• 45. SITE: No signaling BVC reset acknowledgment from the SGSN on page 42-94.
• 46. SITE: DSW switching hardware required at site on page 42-95.
• 50. SITE: Database corruption detected on page 42-97.
• 51. SITE: Software patch installation failure on page 42-98.
42-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to SITE alarms
Introduction to SITE alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
SITE alarms
SITE device. These alarms are generated for fault conditions that affect the state of the entire
Base Site Controller (BSC) or an entire Base Transceiver Station (BTS) site.
The SITE alarms are generated by GPROC software when a fault condition occurs. A fault
condition on a SITE device is detected by the specific SITE or the BSC software.
The alarms in this chapter apply to a variety of current hardware systems:

• BSU-based BTS systems (including BTS4, BTS5, BTS6, ExCell and TopCell).
• M-Cell2 and M-Cell6 systems.
• M-Cell micro site (M-Cell micro).
BSU-BTS alarms
The alarms contained in this chapter which apply to the BSU-based BTS cabinets are generated
for the Last Radio Signaling Link (RSL) failure and for a Site System Audits Processor (SSAP)
failure.
M-Cell alarms
The alarms contained in this chapter which apply to the M-Cell2 or M-Cell6 system products are
generated for the active Main Control Unit (MCU), Fiber Multiplexer (FMUX) and the active
Fiber Optic Extender (FOX) hardware devices at a site.
The standby alarms occur only in a situation where there are redundant devices present in a
standby frame to serve as a backup for the active ones at a site.
The fault conditions generated on the FMUX and FOX devices also affect the Digital Radio
Interface (DRI) software device. In an M-Cell2 or an M-Cell6 cabinet system, a DRI fault
condition is applied against the Transceiver Carrier Unit (TCU) hardware.
Alarm reporting
SITE alarms are reported by the software residing on the master GPROC.
68P02901W26-S 42-3
Nov 2007
0. SITE: Last RSL link failure Chapter 42: SITE Alarms
0. SITE: Last RSL link failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that the last Radio Signaling Link (RSL) on a Multiple Serial Interface
Link (MMS) at a Site has been disconnected.
Since an RSL link failure always affects call services, this alarm is sent concurrently with
other major alarms related to the link failure. The following RSL alarm should be received
concurrently: 10. RSL: Link disconnected.
In this case, the failed link happens to the last available link for service, the final link outage
occurs in a remote site.
The circumstances in which this alarm is received can be complex and diverse. Refer to the
description of each of the various contexts in which this alarm can be received on the next page
under the section, Alarm contexts on page 42-5.
If this alarm recurs repeatedly, investigate the functionality of the RSL link carrying the DISC
packet. Use the CCITT Blue Book, Q.921 as a source for details regarding the Data Link Layer
when pursuing this information.
42-4 68P02901W26-S
Nov 2007
Possible causes

• The site is in the process of resetting.
• All RSL connections to the BTS are Out Of Service (OOS) due to link or equipment
problems.
• The last (functioning) RSL at a site is locked.
Alarm contexts
Determine the context in which the alarm is being received. For fault isolation and
troubleshooting, it is critical to determine which BSC-to-remote BTS site configuration is
present at the site receiving the alarms.
Possible congurations: BSC-to-BTS
There are three possible types of BSC-to-remote BTS site configurations:

• The Star (spoke) configuration.
• The Loop (open or closed) configuration.
• The Fork configuration.
Star (spoke) conguration
A star (or spoke) consists of many BTS sites; each of which is connected directly to the BSC by
E1 links (MMSs). A minimum of one MMS is required for each BTS site.
site can have a maximum of ten MMSs. The Star (spoke) is treated as multiple open-ended daisy
chains with one BTS site per chain.
Loop Conguration: opened or closed
A loop chain consists of many BTSs connected together in a chain with at least a single E1 link
(MMS) between each remote BTS site. Multiple MMSs can be used to support additional traffic
capacity or redundancy. A single BTS site can have a maximum of ten MMSs. There are two
types of loop configurations: open and closed.
Open loop
Only one end of the (BTS) chain terminates at the BSC. The other end of the chain terminates on
a BTS site. An open loop can have a maximum of 10 remote BTS sites. In this configuration,
if a BTS site goes out Of Service (OOS), all BTS sites downstream from the failed BTS, go
OOS as well.
68P02901W26-S 42-5
Nov 2007
BSC-to-BTS topology Chapter 42: SITE Alarms
Closed loop
Both ends of the (BTS) chain terminate at the BSC. A closed loop can have a maximum of
10 remote BTS sites. In this configuration, if a BTS site goes OOS, all other BTS sites in the
chain remain INS.
Fork Conguration
A fork consists of either a single BTS site or chain of BTS sites connected to an intermediate
BTS site in a chain that terminates at the BSC. Fork BTS sites are connected with at least a
single E1 link (MMS) between each remote BTS site.
site can have a maximum of ten MMSs. The fork can be open-ended or have a redundant loop
back to a chain that terminates at the BSC.
BSC-to-BTS topology
After determining the site configuration, remember the following system characteristics before
beginning troubleshooting activities.
System characteristics
The BSC-to-remote BTS topology is specified in terms of the continuous traffic routes between
the BSC and a terminating remote BTS site. This continuous route includes all intermediate
BTSs between the BSC and the remote BTS site generating the fault condition.
A particular traffic route is specified by a unique PATH device. (Every remote BTS site in the
network must be equipped with at least one PATH device). A PATH device specifies which
SITE devices and associated MSI/MMS devices define the route. Therefore, which particular
E1 link is used between each SITE device.
Every remote BTS site in the network must be equipped with at least one RSL. The RSL carries
signaling traffic between the BSC and the remote BTS site. A maximum of 8 RSLs can be
equipped between the BSC and a BTS site. The additional RSLs provide signaling traffic load
sharing (and depending on system configuration) may provide redundancy. An RSL for a specific
site is associated with a PATH device that terminates at that same site.
The following rules apply to the BSC-to-BTS relationship:
• If all RSLs between a BSC and a remote BTS site are OOS for more than 10
minutes, the BTS site goes OOS.
• An RSL may be OOS as a result of the associated MMS being OOS.
• An MMS may be OOS because an associated MSI or XCDR is OOS.
42-6 68P02901W26-S
Nov 2007
In the case of a BTS site that is part of an open loop or open-ended fork, the loss of RSLs at a
site may be caused by equipment failure downstream from the failed BTS site reporting the
alarm. (Recall that in this configuration, if a BTS site goes Out Of Service (OOS), all BTS sites
downstream from the failed BTS, go OOS as well).
Procedure
Wait for 10 minutes before continuing with this procedure. The site may be in the
process of resetting.
Procedure 42-1 Last RSL link failure
1 Check to see if the alarm has been cleared and the RSL connection has
been re-established. If this is the case, fault isolation and resolution is not
necessary. If the alarm has not been cleared, go to step 2.
If this alarm recurs, there may be a quality of service problem

on one of the E1 links that carries this RSL.
2 Refer to the several current alarm report logs to determine if the particular
link (RSL) reports this RSL alarm in excess of the normal trends.
If the RSL Then...
is...
busy and The alarm condition has ceased. Further fault isolation
unlocked is not required.
not busy and Go to step 3.
unlocked
3 From the Navigation Tree, open the Detailed View for the link that is Out
Of Service (OOS). Use the INS option from the Fault Mgt menu to attempt
to re-establish the broken link. If the link remains OOS, go to step 4.
4 From the Navigation Tree window, select the Display Menu and from it
the Contained Devices option to display the active equipment associated
with the RSL. Record the unique PATH identifiers for the RSL device.
5 From the Navigation Tree window, select the Display Menu and from it
the Contained Devices option to display the active equipment associated
with the PATH. Record the device identifiers for each site and the
associated MMSs as specified for the PATH.
Continued
68P02901W26-S 42-7
Nov 2007
Procedure 42-1 Last RSL link failure (Continued)

6 From the BSC, execute the state command to check the operational and
administrative states of the PATH device.
If the PATH Then...
is...
busy and Check the alarm log for the MMS alarms related to
unlocked the PATH device; the MMSs carry the suspect RSL.
If there is an MMS alarm, follow the appropriate
procedure (in the MMS chapter of this manual) to
resolve the MMS fault condition and go to step 7.
However, if there is no MMS alarm, it is likely that the
serial data transmission carrier is operating but at a
reduced transmission quality.
Send a field representative to the site to determine the
quality of the link.
not busy and Send a field representative to the site to continue the fault
unlocked diagnosis.
The E1 link timeslot (0) carrying the LAPD link protocol

indicates the quality of service of the serial data transmission
carrier. If the LAPD link is failing, the serial data carrier
transmission quality is probably reduced. And if it does not
improve, adjust the transmission quality at the site.
Continued
42-8 68P02901W26-S
Nov 2007

7 Determine whether the MMS or SITE devices specified for the PATH
device are OOS. From the BSC, execute the state command for the
BSC-related MMS specified for the PATH device. The format is: state
0 MMS <MMS dev ID>.
If the MMS and the SITE Then...
is... is...
INS INS It is likely that the data path is operating
at a reduced quality. From the Navigation
Tree, open the Detailed View for the
link that is Out Of Service (OOS). Use
the INS option from the Fault Mgt
menu in an attempt to bring the RSL
back into service before sending
a field representative to the site.
If the RSL link(s) resume normal

service, continue to monitor the link
alarms at the OMC-R. If recurrence
becomes excessive again, go to step 8.
If the RSL link(s) does not resume normal
service, go to step 8.
INS OOS It is possible that a device has failed.
Before sending a field representative to
the site: Check the alarm reports for other
devices which may be causing the site to
fail. Refer to the appropriate chapter in
this manual for procedures to resolve the
fault condition.
OOS INS It is possible that a device
has failed. Before sending a
field representative to the site:
Check alarm reports for other device failed
alarm 254 for devices related to the MMS.
If possible, determine which T43/BIB
interconnect board connections and MMS
links are associated with the suspect MMS.
(Refer to site documentation). Refer to
the appropriate chapter in this manual for
procedures to resolve the fault condition.
OOS OOS It is possible that both devices have failed.
Before sending a field representative to
the site to service the serial data carrier:
Check alarm reports for other
device failed alarm 254 for devices
related to the MMS or SITE.
Refer to the appropriate chapter in
this manual for procedures to resolve the
fault condition.
Continued
68P02901W26-S 42-9
Nov 2007

8 Continue fault diagnosis by checking the operational device state of the
MMS.
If the MMS Then...
is...
busy and It is possible that there is an equipment failure at
unlocked the failed BTS. From the Navigation Tree, open the
Detailed View for the SITE device. From the
View Menu select State for the next BTS that is
downstream from the failed BTS. (Downstream refers to
the BTS which is farther away from the BSC).
Is the BTS (SITE) in a busy-unlocked state.
If yes, select State for each MMS associated with the Site.
Check the MMSs upstream and downstream from the BSC.
Check if the MMS(s) are in a busy-unlocked state. If yes,
check for MMS device alarms. Refer to Chapter 29 MMS
Alarms in this manual for fault resolution procedures.
not busy and It is possible that a device has failed. Before
unlocked sending a field representative to the site: Check
alarm reports for an MMS device alarms.
If possible, determine which T43/BIB interconnect

board connections and MMS links are associated
with the suspect MMS. (It may be necessary
to refer to site specific documentation).
Refer to Chapter 29 MMS Alarms in this manual for fault
resolution procedures. After completing fault diagnostics,
check the next entry in this table.
not busy and It is possible that the equipment has failed. Check the
unlocked alarm reports for failures of GPROCs and/or KSW/TSWs.
Failure of any of these devices causes the site to reset
which appears to be an RSL failure when it is not.
Check the alarm reports for failures of the TDM Bus

(TBUS) device and clocking (For example, GCLKs) failures.
Refer to this manual for fault resolution procedures for the
alarms being displayed. After completing fault resolution
from the OMC-R, go to step 9.
Continued
42-10 68P02901W26-S
Nov 2007

9 Send a field representative to the site to determine the quality of the
link and adjust, correct or replace it as necessary. If the RSL(s) do not
return to normal service after the quality of the link transmission has been
corrected, the field representative must manually reset the Multiple Serial
Interface (MSI) board related the failed RSL. If the reset is unsuccessful:
• Check for failed cabling, check board connections and so on and

replace the equipment, if necessary.
• Verify that the MSI board is functioning properly and replace the
MSI, if necessary.
If the RSL(s) return to normal service, cease further fault isolation.
Sometimes the link cannot be brought back into service

even after the link quality has been improved. In this
case, the Multiple Serial Interface (MSI) may need to be
physically reset at the site to bring the failed RSL(s) back
into service. This is usually the last resort.

68P02901W26-S 42-11
Nov 2007
2. SITE: BSC detected MCU to MCU communication failure Chapter 42: SITE Alarms
2. SITE: BSC detected MCU to MCU communication

failure
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm is generated when the Base Station Controller (through the SITE device) has
received communication-related messages from both (active and standby) Main Control Unit
(MCU) software devices at an M-Cell site.
The software devices that generate this fault condition are the BSP Generic Processors (BSP
GPROCs). Together, the active and the standby BSP GPROC software devices cause this fault
condition to occur. (The hardware that is affected by this fault condition are the MCUs).
This fault condition indicates that both BTP GPROCs (MCUs) are designated as the master BTP
within the system software. If two BTP GPROCs (MCUs) are employed at a site, one BTP (MCU)
must be master and the other must be the standby.
This condition does not reduce traffic capacity. However, it does reduce redundancy at a site
because the two BTPs (MCUs) cannot communicate.
This alarm can occur only in an M-Cell2 or an M-Cell6 site equipped with BTP (MCU)
redundancy.
42-12 68P02901W26-S
Nov 2007
Possible causes

• The fiber optic cable connecting the two BTPs (MCUs) is faulty.
• The fiber optic cable connecting the two BTPs (MCUs) is incorrectly connected.
• The (MSW) port (on a BTP (MCU)) that connects to the fiber optic cable is faulty.
• The software that assigns a BTP (MCU) to the role of Master BTP is faulty.
Procedure
Procedure 42-2 BSC detected MCU to MCU communication failure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
device. From the View Menu select State to check the operational
and administrative state of both of the BTP (MCU) devices.
When this alarm occurs, the system automatically assigns

the role of master to one BTP and standby (redundant)
to the other.
3 From the Navigation Tree window, select the Display Menu and
from it the Contained Devices option to determine which PATH
device on the BSC communicates with (is assigned to) each BTP.
4 Select the PATH device assigned to the BTP designated as the master
and select the lock option.
5 From the Navigation Tree, open the Detailed View for a link that is
Out Of Service (OOS). Use the INS option from the Fault Mgt menu
for the standby (redundant) BTP.
Continued
68P02901W26-S 42-13
Nov 2007
Procedure 42-2 BSC detected MCU to MCU communication failure (Continued)

6 Determine whether the standby BTP has come into service.
If the standby BTP (MCU) Then...
has...
come into service Watch for the occurrence of
the alarm, 234. Active Link
Connection Lost.
• If this alarm has been

received for the standby
BTP (MCU), send a field
verify that the BTP (MCU) is
functioning properly.
• If this alarm has not been

received for the standby BTP
(MCU), cease fault isolation
activities.
• Monitor the site for further

alarms.
not come into service There is a problem with the
standby BTP (MCU).
• Send a field representative

to the site to verify that the
BTP (MCU) is functioning
properly.
• If the BTP (MCU) is faulty,

replace it.

42-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. SITE: Active multiplexer 0 loopback failure
3. SITE: Active multiplexer 0 loopback failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot
0 of the master MCU card frame or its corresponding remote multiplexer, is disconnected.
For Horizon macro and Horizon macro2 controlling cabinets, the alarm is generated when
an integrated multiplexer on the master BTP or its corresponding remote multiplexer, is
disconnected.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexers.
The impact of this fault condition is that all TCUs connected to the multiplexer are removed from
service. The DRIs (TCUs) are no longer able to communicate with an MCU/BTP (GPROC). Thus,
the ability to handle system traffic is reduced at the site that is experiencing the fault condition.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
This alarm occurs when:

• The local multiplexer board residing in slot 0 of the master MCU card frame is disconnected
from the backplane.
• The remote multiplexer board linked to the local multiplexer is disconnected from the
backplane.
• The fiber cable connecting the two multiplexers is damaged or broken.
68P02901W26-S 42-15
Nov 2007
Additional information eld Chapter 42: SITE Alarms
Possible causes

• The multiplexer on either side or end of the fiber optic cable is faulty.
• The multiplexer is removed from the backplane.
• A backplane connector is damaged.
• The fiber optic cable is faulty.
Procedure
Procedure 42-3 Active multiplexer 0 loopback failure
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.

42-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. SITE: Standby multiplexer 0 loopback failure
4. SITE: Standby multiplexer 0 loopback failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
0 of the standby MCU card frame or its corresponding remote multiplexer, is disconnected.
For Horizon macro and Horizon II macro controlling cabinets, the alarm is generated when
an integrated multiplexer on the standby BTP or its corresponding remote multiplexer, is
disconnected.
This alarm is suppressed where FMUX0 supports a Horizon II extension cabinet.
TCU connection
does not occur.

• The local multiplexer board residing in slot 0 of the standby MCU card frame is
disconnected from the backplane.
• The remote multiplexer board linked to the local standby multiplexer is disconnected
from the backplane.
68P02901W26-S 42-17
Nov 2007
Possible causes Chapter 42: SITE Alarms
Possible causes

• The multiplexer on either side or end of the fiber optic is faulty.
• The fiber optic link is faulty.
Procedure
Procedure 42-4 Standby multiplexer 0 loopback failure

42-18 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
an integrated multiplexer on the master BTP or its corresponding remote multiplexer, is
disconnected.
TCU connection
does not occur.

from the backplane.
backplane.
68P02901W26-S 42-19
Nov 2007
Possible causes

Procedure

42-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. SITE: Standby multiplexer 1 loopback failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
an integrated multiplexer on the standby BTP or its corresponding remote multiplexer, is
disconnected.
connected to the multiplexer.
This alarm is suppressed where FMUX1 supports a Horizon II mini extension cabinet.
TCU connection
does not occur.

from the backplane.
68P02901W26-S 42-21
Nov 2007
Possible causes

Procedure

42-22 68P02901W26-S
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
For Horizon macro controlling cabinet, the alarm is generated when a multiplexer external to
the active MCUF or its corresponding remote multiplexer, is disconnected.
For a Horizon II macro controlling cabinet, the alarm is generated when an integrated
multiplexer on the master BTP or its corresponding remote multiplexer, is disconnected.
68P02901W26-S 42-23
Nov 2007
TCU connection
does not occur.

from the backplane.
backplane.
Possible causes

Procedure
Continued
42-24 68P02901W26-S
Nov 2007
Procedure 42-7 Active multiplexer 2 loopback failure (Continued)


68P02901W26-S 42-25
Nov 2007
8. SITE: Standby multiplexer 2 loopback failure Chapter 42: SITE Alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
For Horizon macro controlling cabinet, the alarm is generated when a multiplexer external to
the standby MCUF or its corresponding remote multiplexer, is disconnected.
For Horizon II macro controlling cabinet, the alarm is generated when an integrated multiplexer
on the standby BTP or its corresponding remote multiplexer, is disconnected.
This alarm is generated only if one or more in-service DRIs are connected to the
multiplexers.
This alarm is suppressed where FMUX2 supports a Horizon II mini extension cabinet.
TCU connection
does not occur.

from the backplane.
42-26 68P02901W26-S
Nov 2007
Possible causes

Procedure

68P02901W26-S 42-27
Nov 2007
9. SITE: Active local FOX failure Chapter 42: SITE Alarms
9. SITE: Active local FOX failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the M-Cell Fiber Optic Extender (FOX) board residing in the (active)
master MCU card frame has failed. It is generated after all of the DRI/Transceiver Control Units
(TCUs) supported by the FOX have lost the ability to communicate to the MCU/BTP (GPROC).
This local FOX failure alarm is generated when all In Service (INS) TCUs lose connection with
the MCU at the same time.
This alarm is valid only for M-Cell2 and M-Cell6 sites.
The impact of this fault condition is that all TCUs are removed from service. The DRIs (TCUs)
are no longer able to communicate with an MCU/BTP (GPROC). Thus, the ability to handle
system traffic is reduced at the site that is experiencing the fault condition.
TCU connection
If at least two TCUs are connected and INS, this alarm occurs when the local FOX board residing
in the master MCU card frame is disconnected from the backplane.
42-28 68P02901W26-S
Nov 2007
Possible causes

• The FOX board is faulty.
• The FOX board is removed from the backplane.
Procedure
Procedure 42-9 Active local FOX failure
2 In the Alarm window, determine whether the following DRI alarms
have been generated against the DRI (TCUs) connected to the FOX
that has failed:
• 234. DRI: Active Link Connection Lost.
• 235. DRI: Standby Link Connection Lost.

FOX. They should all be Out Of Service (OOS).
4 Send a field representative to the site to replace the FOX board.

68P02901W26-S 42-29
Nov 2007
10. SITE: Standby local FOX failure Chapter 42: SITE Alarms
10. SITE: Standby local FOX failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the M-Cell Fiber Optic Extender (FOX) board residing in the standby
MCU card frame has failed. It is generated after all of the DRI/Transceiver Control Units (TCUs)
supported by the FOX have lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and INS, this alarm occurs when the local FOX board residing
in the master MCU card frame is disconnected from the backplane.
Possible causes

42-30 68P02901W26-S
Nov 2007
Procedure
Procedure 42-10 Standby local FOX failure
Send a field representative to the site to replace the FOX board.

68P02901W26-S 42-31
Nov 2007
11. SITE: Active remote FOX 0 failure Chapter 42: SITE Alarms
11. SITE: Active remote FOX 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
master MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 0
of the (active) master MCU card frame; it is referred to as FMUX 0. The alarm is generated
after the FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 0 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-32 68P02901W26-S
Nov 2007
Possible causes

Procedure
Procedure 42-11 Active remote FOX 0 failure
1 Send a field representative to the site(s).

2 Check the backplane connection and/or replace any of the following: the
FMUX in slot 0 and/or the FOX board.

68P02901W26-S 42-33
Nov 2007
12. SITE: Standby remote FOX 0 failure Chapter 42: SITE Alarms
12. SITE: Standby remote FOX 0 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
standby MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 0
of the (standby) MCU card frame; it is referred to as FMUX 0. The alarm is generated after the
FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
42-34 68P02901W26-S
Nov 2007
Possible causes

Procedure
Procedure 42-12 Standby remote FOX 0 failure


68P02901W26-S 42-35
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TCU connection
42-36 68P02901W26-S
Nov 2007
Possible causes

Procedure


68P02901W26-S 42-37
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TCU connection
42-38 68P02901W26-S
Nov 2007
Possible causes

Procedure


68P02901W26-S 42-39
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TCU connection
42-40 68P02901W26-S
Nov 2007
Possible causes

Procedure


68P02901W26-S 42-41
Nov 2007

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
TCU connection
42-42 68P02901W26-S
Nov 2007
Possible causes

Procedure


68P02901W26-S 42-43
Nov 2007
17. SITE: 16 kbps switching hardware required Chapter 42: SITE Alarms
17. SITE: 16 kbps switching hardware required

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that one of the following two possible fault conditions has occurred:
• A BTS (SITE) currently contains a Timeslot Switch (TSW) rather than a Kiloport Switch
(KSW) in the master cage as required.
• A BTS (SITE) is configured for dynamic (timeslot) allocation, but the KSW in the master
cage is not configured to support it.
No calls are possible at this site.
Switching capability
A Timeslot Switch (TSW) is not capable of 16 kbps switching for a BTS that is either equipped to
use Radio Signaling Links (RSLs) or is configured to support dynamic allocation.
Only a KSW can provide 16 kbps switching. Neither InCell TSW boards nor M-Cell switching
hardware provide 16 kbps switching.
This is a service affecting fault condition. No calls can be completed at a BTS for
which this alarm has been generated.
42-44 68P02901W26-S
Nov 2007
Possible causes

• A TSW may currently reside in a KSW (master or redundant) slot in the master cage at a
BTS that has been equipped for use with 16 kbps RSLs.
• The BTS site is configured for dynamic allocation, but the master cage does not contain the
switching hardware to support it.
Procedure
Procedure 42-17 16 kbps switching hardware required
from it the Contained Devices option to determine for the KSW, the
FRU subtype, the cage and the slot number where the KSW (TSW)
is located.
Refer to the manual, Technical Description: BSS Command

Reference (68P02901W23) for information regarding
command entry.
68P02901W26-S 42-45
Nov 2007
18. SITE: MIX board (Slot 18) communication failure Chapter 42: SITE Alarms
18. SITE: MIX board (Slot 18) communication failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The polling software does not detect the MIX board or responds with a bad board identifier.
Possible causes

• The MIX board has been physically disconnected from the backplane.
• A board that is not MIX has been inserted in the MIX slot.
• Bad MIX board.
Procedure
Procedure 42-18 MIX board (Slot 18) communication failure
Insert a good MIX Board into the MIX slot (Slot 18).
42-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 19. SITE: Unequipped GPROC has entered the LAN
19. SITE: Unequipped GPROC has entered the LAN

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that Local Area Network (LAN) hardware has detected that a Generic
Processor (GPROC) device has accessed the LAN without being equipped in the Configuration
Management (CM) database.
Equip the GPROC device fully before the system can use it.
This alarm applies only to InCell hardware.
System impact
The system impact varies depending on the actual cause of the fault.
This alarm may indicate that either OMC-R or onsite maintenance action is occurring; or an
operator or onsite error has been made; or that a hardware failure has occurred.
The following is displayed in the Additional information field.
An alphanumeric text string is used to display the specific cage and slot occupied by the
unequipped GPROC.
Cage: “xx” Slot: “xx”
Where: ‘xx’ represents the decimal numbers associated with the cage and slot.
68P02901W26-S 42-47
Nov 2007
Possible causes

• The GPROC is not properly inserted into the correct slot.
• The GPROC is inserted into an incorrect slot within a cage.
• The GPROC is inserted into a CAGE before being equipped.
• The GPROC is reset before being equipped.
• A CAGE is not equipped before it was added to the LAN.
• The GPROC may have recently been unequipped after entering the LAN.
Procedure
Procedure 42-19 Unequipped GPROC has entered the LAN
1 Refer to the alarm message report. Check the Additional Information

in the alarm output to determine the cage and slot numbers of the
unequipped GPROC.
2 Determine whether the unequipped GPROC has been designated to
remain in an unequipped state and/or is due to be equipped for use
within the system. Check site configuration and maintenance plans
to verify whether the GPROC is located in a slot and cage designated
for an unequipped GPROC.
If this alarm has been Then...
generated for...
a GPROC that is intentionally No fault resolution is required.
unequipped Consider blacklisting this alarm
until the GPROC is equipped.
a GPROC that is unexpectedly It is possible that the wrong cage
unequipped was equipped. Go to step 3.
The cage and slot numbers entered in the enclosed MMI

commands must be from valid ranges. Cage 0-15; Slot
18-25 or 25-26.
Continued
42-48 68P02901W26-S
Nov 2007
Procedure 42-19 Unequipped GPROC has entered the LAN (Continued)

from it the Contained Devices option for the CAGE to show the
cage (number) displayed in the Additional Information of this alarm.
This verifies whether the correct cage has been equipped in the
CM database.
If the CAGE device is... Then...
equipped The GPROC may be in the wrong
slot. Go to step 4.
unequipped The CAGE needs to be equipped.
Execute the equip command for
the CAGE device. Go to step 4.
4 Determine whether the (GPROC) slot number shown in the Additional
Information is valid.
If the slot number is... Then...
within the range of 18-25 for The GPROC may be in the wrong
BTS sites slot. Go to step 5.
RXCDR sites slot. Go to step 5.
not within one of the specified The GPROC is either improperly
ranges inserted into a slot within the cage
or the GPROC board is faulty. Go
to step 7.
from it the Contained Devices option for the GPROC to check for a
GPROC that is Not on the LAN.
If the command output... Then...
displays Not on the LAN for a The GPROC must be unequipped:
GPROC Select the UNEQUIP option for
the GPROC using the device ID
displayed in step 4. The same
GPROC must be re-equipped
correctly, go to step 6.
displays the other processors The GPROC may not be equipped.
only Go to step 6.
Continued
68P02901W26-S 42-49
Nov 2007
Procedure 42-19 Unequipped GPROC has entered the LAN (Continued)

6 Select the EQUIP option for the GPROC using the cage and slot
numbers from the Additional Information of this alarm (19).
7 If the GPROC remains unequipped, send a field representative to the
site to perform the following as necessary:
• Verify whether the GPROC is functional by removing and

re-inserting the GPROC into the correct cage and slot as
designated in the CM database.
• Replace the GPROC board, if this (19. SITE) alarm recurs.

42-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. SITE: Unequipped GPROC has left the LAN
20. SITE: Unequipped GPROC has left the LAN

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Category: Equipment
Description
This alarm indicates that Local Area Network (LAN) hardware has detected that a Generic
Processor (GPROC) has left the LAN without being equipped in the Configuration Management
(CM) database.
Equip the GPROC device fully before the system can use it.
This alarm applies only to InCell hardware.
System impact
The system impact varies depending on the actual cause of the fault.
This alarm may indicate that either OMC-R or onsite maintenance action is occurring; or an
operator or onsite error has been made; or that a hardware failure has occurred.
The following is displayed in the Additional information field.
An alphanumeric text string is used to display the specific cage and slot occupied by the
unequipped GPROC.
Cage: “xx” Slot: “xx”
Where: ‘xx’ represents the decimal numbers associated with the cage and slot.
68P02901W26-S 42-51
Nov 2007
Possible causes

• The GPROC is removed from a CAGE before it (the GPROC) had been equipped.
• The GPROC is reset before being equipped.
• The GPROC is removed from an unequipped CAGE.
• The active LAN may have failed.
Procedure
Procedure 42-20 Unequipped GPROC has left the LAN
1 Refer to the alarm message report. Check the Additional Information

in the alarm output to determine the cage and slot numbers of the
unequipped GPROC.
2 Determine whether the unequipped GPROC has been designated
to remain in an unequipped state and/or is due to be equipped
for use within the system. Check site configuration and/or
maintenance plans to verify whether the GPROC is located
in a slot and cage designated for an unequipped GPROC.
Check for a previous instance of 19. SITE alarm for the same site. If
19. SITE is currently being resolved, this alarm occurs.
If this alarm has been Then...
generated for...
a GPROC that is intentionally No fault resolution is required.
unequipped Consider blacklisting this alarm
until the GPROC is equipped.
a GPROC that is unexpectedly It is possible that the
unequipped wrong cage was equipped.
Go to step 3.
Continued
42-52 68P02901W26-S
Nov 2007
Procedure 42-20 Unequipped GPROC has left the LAN (Continued)

3
The cage and slot numbers entered in the enclosed MMI

commands must be from valid ranges. Cage 0-15; Slot
18-25 or Slot 25-26.
Refer to the alarm message report for LAN alarms. Determine
whether the LAN connection has failed by checking the following.
If either of the following alarms have been generated.
• 1. LAN: LAN failure.
• 0. LAN: Active and standby failure.

4 If any LAN alarms have been generated, refer to the appropriate
alarm description in this manual for the necessary fault resolution
procedure. If no LAN alarms have been generated, go to step 5.
5 From the Navigation Tree window, select the Display menu and
from it the Contained Devices option for the CAGE of the (GPROC)
cage number displayed in the Additional Information of this alarm
(19). This verifies whether the correct cage has been equipped in
the CM database.
If the CAGE device is... Then...
equipped The GPROC may be in the wrong
slot. Go to step 6.
unequipped The CAGE needs to be equipped.
Execute the equip command for
the CAGE device. Go to step 4.
6 Determine whether the (GPROC) slot number shown in the Additional
Information is valid.
If the slot number is... Then...
BTS sites slot. Go to step 7.
RXCDR sites slot. Go to step 7.
not within one of the specified The GPROC is either improperly
ranges inserted into a slot within the
cage or the GPROC board is faulty.
Go to step 9.
Continued
68P02901W26-S 42-53
Nov 2007
Procedure 42-20 Unequipped GPROC has left the LAN (Continued)

from it the Contained Devices option for the GPROC to check for a
GPROC that is Not on the LAN.
If the command output... Then...
displays Not on the LAN for a That GPROC must be unequipped.
GPROC Select the UNEQUIP option for
the GPROC using the device ID
displayed in step 6. The same
GPROC must be re-equipped
correctly, go to step 8.
displays the other processors The GPROC may not be equipped.
only Go to step 8.
8 Select the EQUIP option for the GPROC using the cage and slot
numbers from the Additional Information of this alarm (20).
9 If the GPROC remains unequipped, send a field representative to the
site to perform the following as necessary:
• Verify whether the GPROC is functional by removing and

re-inserting the GPROC into the correct cage and slot as
designated in the CM database.
• Replace the GPROC board if this alarm recurs.

42-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. SITE: No clock references available
21. SITE: No clock references available

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
This alarm indicates that Fault Management (FM) has detected that the current Generic Clock
(GCLK) reference for clock extraction has failed within the system.
System impact
While this fault condition exists, service and capacity are not compromised unless this alarm is
the result of an equipment failure. If a failure occurs, other serious (Critical and Major) alarms
are generated for the Multiple Serial Interface link (MMS), Multiple Serial Interface (MSI), the
transcoder (XCDR) or Generic DSP Processor (GDP).
However, the system is affected only in the following ways:

• The GCLK is not able to phase lock.
• More frequent recalibrations are necessary.
68P02901W26-S 42-55
Nov 2007

first 00 to FF The (MMS) timeslot allocated
the RSL generating this
alarm.
second third fourth 00 to FF00 to FF00 to FF
• First byte - the device
identifiers of the MMS
containing the timeslot
(allocated to the RSL).
• Second byte - value.

A (hexadecimal)
represents the MMS
device.
• Third byte - the Multiple

Serial Interface (MSI)
board on which the MMS
resides.
• Fourth byte - the MMS

on the MSI board.
If the MMS cannot

be determined by
the system, the
values for bytes 2
to 5 are displayed
as FF.
Possible causes

• An MSI link (MMS) connection may have failed.
• The MMS providing the clock reference source for the site is locked by the operator.
• The last MMS providing a clock reference source for the site may have gone Out Of
Service (OOS).
• A connection on the backplane may have caused the failure.
42-56 68P02901W26-S
Nov 2007
Procedure
Procedure 42-21 No clock references available
1 Refer to the alarm message report. Check for related MMS, MSI, XCDR
or GDP (Critical) alarms at that site which indicate an MMS link or a
transcoding problem.
• Refer to specific alarm pages in this manual for fault resolution

procedures. Prioritize fault resolution accordingly.
• If there are no other failures, go to step 2.

2 Determine whether an MMS was defined for clock extraction when phase
locking occurred. The system selects the MMS for clock extraction. From
the Navigation Tree window, select the Display menu and from it the
Contained Devices option to display all the MMSs at the site for which this
alarm was generated with priority 0.
• If an MMS was defined for clock extraction, priority > 0 is displayed in

the command output, go to step 3.
• If no MMS at the site was defined for clock extraction, go to step 3.

3 From the View menu, select the State option for each MMS that has a
priority > 0 to determine the operational states of these MMSs.
• INS the MMS that displays the highest priority.
(For example, if four separate MMSs showed the priorities, 2, 4, 6, 8,

then INS the MMS with the priority of 8).
• Verify that the MMS has returned to a busy-unlocked device state. If

not, repeat the sub-step above until an MMS (with priority > 0) goes
into a busy-unlocked state. Go to step 4.
• If no MMSs return to service, recheck the Alarm window for MMS,

MSI, XCDR (or GDP) alarms. Refer to the alarm descriptions and fault
resolution procedures in this manual.
If an MMS (priority > 0) cannot return to service, it is likely

that the MMS, MSI, XCDR or GDP fault resolution procedure
in this manual require a field representative to go to the site
to investigate for a potential hardware fault.
4 An MMS resumes functioning as the clock source for the site. Cease fault
resolution.
68P02901W26-S 42-57
Nov 2007
22. SITE: Active alarm list full Chapter 42: SITE Alarms
22. SITE: Active alarm list full

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
A new alarm could not be added to the active alarm list because the alarm list for a specific
site on a BSS is full. The alarm list can contain a maximum of 120 active alarms for each site
on a BSS.
This alarm indicates a more serious problem may exist due to the number of active alarms.
After this alarm has been generated, any subsequent alarms generated are discarded.
They are not stored by the system.
This alarm does not affect the OMC-R because it has a different active alarm list.
A one-byte alarm code is displayed in the Additional information field identifies the new alarm
that triggered this alarm.
Possible causes
The active alarm list is full because there are 120 active alarms at the site.
42-58 68P02901W26-S
Nov 2007
Procedure
Procedure 42-22 Active alarm list full
1 Review the active alarms list to determine what

has caused the excessive number of alarms.
If a subscription containing active alarms does not exist, one must
be created.
2 Resolve the fault conditions that generated the excessive number of
alarms and clear the active alarms.
Alarms cannot be cleared from the active alarm list until

the related fault conditions are resolved.
68P02901W26-S 42-59
Nov 2007
23. SITE: EMU modem card failure Chapter 42: SITE Alarms
23. SITE: EMU modem card failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The EMU HDSL modem card is not detected by the polling software.
A one-byte alarm code is displayed in the Additional information field identifies the new alarm
that triggered this alarm.
Possible causes
Possible causes for this alarm are:

• The EMU card has been physically removed from the modem shelf.
• The EMU is not functioning.
• The EMU is in the middle of a reset.
• The RS232 cable between the MIX and EMU has been removed.
Procedure
Procedure 42-23 EMU modem card failure
1 Check to see if the EMU card is in the modem shelf.

2 Insert a good EMU card into the modem shelf if EMU is not functioning.
3 Check the Possible causes.
42-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. SITE: Site reset request
24. SITE: Site reset request

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that either the system software, an OMC-R operator, or an onsite field
representative has requested a SITE reset.
System software may require a reset due to the existence of a software or a hardware fault
condition. An operator or field representative may reset a site during maintenance or
troubleshooting through the BSS MMI or OMC-R GUI.
This fault condition is service-affecting. All Digital Radio Interface (DRI) radio units
or RF Units go Out Of Service (OOS). As a result, calls are lost.

first 00 to FF Specifies the Process Identifier (PID) number.
The PID indicates the internal software process
requesting the reset. (PID list in next section).
second 00 or 01 Indicates the type of reset requested.
00 - hard reset; a full reset of the device
hardware and software.
01 - soft reset; a reset of device
software only.
Continued
68P02901W26-S 42-61
Nov 2007

third 00, 01, 02 or 27, 28, 29 Indicates the general reason or circumstances
under which the reset happened.
If soft reset has occurred:

00 - A soft reset requested from rlogin or
TTY window through an MMI command.
01 - Software requested a reset due
to the detection of an inconsistent
database during SITE initialization.
02 - Source of reset unknown and variable
depending on process(es), actions
performed and/or conditions at the site.
If hard reset has occurred:

27 - OMC-R operator requested
a hard reset through the GUI.
28 - A hard reset requested from rlogin or
TTY window through an MMI command.
29 - Software requested an invalid operational
state transition for a device.
Process Identier (PID) number
The following is a list of PIDs that relate to the site reset request. PID numbers are shown in
the Additional information field for the purpose of highlighting which internal software process
has caused the reset.
Table 42-3 expresses the PID number, the abbreviated name of the software process and a brief
description of the process and why it is requesting a reset.
In addition, the Network Element (NE) for which the reset is requested is stated.
Table 42-3 Process identier (PID) number
PID (dec/hex) Abbreviated name Description

66/0x42 CA Central Authority (CA) Process has requested a
site reset because an invalid operational state
transition request was made to the CA.
112/0x70 MMI Man Machine Interface (MMI) process has
requested a BTS or BSC site reset because an MMI
reset command has been used in an rlogin or TTY
window.
113/0x71 CM Configuration Management (CM) has requested a
BTS site reset because an operator has initiated a
(BTS) reset through the OMC-R GUI.
118/0x76 NMASE Network Management Application Service Element
(NMASE) Process has requested a BSC site reset
because an operator has initiated a (BSC) reset
through the OMC-R GUI.
42-62 68P02901W26-S
Nov 2007
Possible causes

• The system site reset request is due to a hardware fault.
• The system site reset request is due to a software fault: processing fault, inconsistent
database, or invalid state transition requested for a device.
• The operator site reset attempted is due to a current fault (software or hardware) existing
within the system.
Procedure
Procedure 42-24 Site reset request
this alarm is occurring. Check the Additional information field in the
alarm output for the possible cause for the alarm (and site reset).
2 If a SITE reset has been initiated, wait for it to finish before
continuing.
3 After the reset, check to see if this alarm is automatically cleared in
the Alarm window.
• If the site reset did clear the alarm, cease fault resolution.
• If the site reset did not clear the alarm, initiate the appropriate
data collection processes (For example, Performance
Management) for troubleshooting purposes and/or go to step 4.
4 Check the alarm output for any OOS devices shown in the impacted
devices list.
• Prioritize fault resolution based on the order of the OOS devices

displayed. Fault resolution priority is displayed in order, going
from the top (highest priority) of the OOS devices list to the
bottom (lowest priority).
• Check the Alarm window for alarms related to the OOS devices
in the list. Refer to other alarm descriptions and fault resolution
procedures in this manual.
68P02901W26-S 42-63
Nov 2007
25. SITE: External power booster amplier 1 failure Chapter 42: SITE Alarms
25. SITE: External power booster amplier 1 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Transmitter Channel 1 Power Amplifier (PA) within the Horizon
compact (M-Cell arena macro) Base Transceiver Station (BTS) has failed.
The power transmitted to channel 1 transmit antenna is reduced to approximately 0.8 W.
This alarm applies only to Horizon compact (M-Cell arena macro) Booster units.
System impact
The result of this reduction in transmission power may have some general effects such as,
reduced area of coverage in the macro cell, reduced capacity in terms of calls that can be
handled, voice quality may be reduced on the edge of the cell, and calls originating outside
the coverage area may be dropped.
Other possible effects depend on whether the site is located in a high traffic or low traffic area
and how the surrounding cells are configured.
In a high traffic area, if the non-BCCH PA fails, the impact will most likely reduce the call
capacity if the other PA remains fully functional. If the PA holding the BCCH fails, area of
coverage is reduced.
In a low traffic area, if one PA fails, the loss of transmission power may be transparent if the
Horizon compact (M-Cell arena macro) site is not set up to provide sole coverage for the macro
cell. However, if the unit provides sole coverage, call coverage may be reduced.
42-64 68P02901W26-S
Nov 2007
Possible causes
The transmitter channel 1 Power Amplifier (PA) is defective.
Procedure
1 Check the alarm report to determine the site for which the alarm
was generated.
2 Send a field representative to the site to replace the Horizon compact
(M-Cell arena macro) Booster containing the faulty PA. The PA cannot
be replaced onsite, the entire Booster unit must be replaced if faulty.

68P02901W26-S 42-65
Nov 2007
26. SITE: External power booster amplier 2 failure Chapter 42: SITE Alarms
26. SITE: External power booster amplier 2 failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the Transmitter Channel 2 Power Amplifier (PA) within the Horizon
compact (M-Cell arena macro) Base Transceiver Station (BTS) has failed.
The transmitted power to both transmit antenna is reduced to approximately 2.0 W instead of
10 W.
This alarm applies only to Horizon compact (M-Cell arena macro) Booster units.
System impact
42-66 68P02901W26-S
Nov 2007
Possible causes
The transmitter channel 2 Power Amplifier (PA) is defective.
Procedure
was generated.
2 Send a field representative to the site to replace the Horizon
compact (M-Cell arena macro) Booster containing the faulty PA.
The PA cannot be replaced onsite, the entire Booster unit

must be replaced if faulty.

68P02901W26-S 42-67
Nov 2007
27. SITE: External power booster failure Chapter 42: SITE Alarms
27. SITE: External power booster failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the booster in the Horizon compact (M-Cell arena macro) Base
Transceiver Station (BTS) has failed. This alarm is generated when the system detects that the
booster is not functioning because it is either not installed, not connected (or not present)
or faulty.
The power transmitted to both transmit antennas is reduced to approximately 0.8 W per channel.
This alarm applies only to Horizon compact (M-Cell arena macro) site with a booster
unit.
System impact
42-68 68P02901W26-S
Nov 2007
Possible causes

• A power supply or other device within the Horizon compact (M-Cell arena macro) Booster
unit is defective.
• The Horizon compact macro Booster unit is disconnected.
• The Horizon compact macro Booster unit is not present at the site.
Procedure
Procedure 42-27 External power booster failure
was generated.
2 Send a field representative to the site to verify that the Horizon
compact macro Booster is present and check the connections. If
attempts to reconnect the Horizon compact unit do not clear the
alarm, replace the booster unit.

68P02901W26-S 42-69
Nov 2007
28. SITE: Database conguration and arena hardware mismatch Chapter 42: SITE Alarms
28. SITE: Database conguration and arena hardware

mismatch
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates one of the following:
• The hardware present is Arena Macro hardware but the database configuration is for
standard Arena hardware or vice versa.
• The BTS master cabinet is M-Cell6, Horizon macro, Horizon macro2 or Horizon micro2, but
the database cabinet type does not match. If the site is Horizon macro and the database is
M-Cell6, the site stays in service. In all other instances of this alarm the site is taken OOS.
System impact
No system impact to service occurs. The Horizon unit is fully operational despite the
database-to-hardware mismatch.
In addition, the Horizon compact External Power Booster SITE alarms (25, 26, 27) can be
generated if the Booster unit hardware becomes faulty.
System upgrade
The cabinet is equipped as a Horizon II mini as per the Horizon II mini feature (FR28565). The
operators configure the site to a configuration not supported by the hardware. To support the
Horizon II mini and Horizon II mini_extension, the cabinet types are changed:
cab_type 26 for Horizon II mini/Horizon II micro.
cab_type 27 for Horizon II mini_Extension/Horizon II micro_Extension.
Thus, for all Horizon II micro cabinets, the operator configures the site to a configuration not
supported by the hardware. For example, Horizon II mini site.
42-70 68P02901W26-S
Nov 2007
• The procedure applies to all the upgraded BSCs containing Horizon II micro
sites.
• To avoid any disruptions in network, carry out the procedure during those hours
of the day when the traffic is moderate or low.
Procedure 42-28 Procedure to equip Horizon II micro as Horizon II mini
1 Enter the lock_device command to lock all DRIs under the Horizon II micro
site.
2 Enter the unequip_device command to unequip all DRIs under the Horizon
II micro site.
3 Enter the modify_value command to modify the cabinet type from 24 to 26.
4 Enter the equip_device command to equip all DRIs again.
5 Enter the unlock_device command to unlock all DRIs under the Horizon II
micro site. (The new cabinet type will now be displayed as Horizon II mini)
Possible causes
The database configuration does not match the hardware present:

• The site is standard Arena when database indicates Arena Macro, when database shows
standard Arena.
• If the BTS master cabinet is either M-Cell6, Horizon macro or Horizon macro2, an invalid
database cabinet type has been entered for this site.
Procedure
Procedure 42-29 Database conguration and arena hardware mismatch
was generated.
2 Verify the site plan with Network OMC-R planners and
administrators; determine which Horizon unit Cabinet Type should
be at the site.
Continued
68P02901W26-S 42-71
Nov 2007
Procedure 42-29 Database conguration and arena hardware mismatch (Continued)

3 Determine whether the current database configuration for the
Horizon unit Cabinet type matches the type that should be there.
• From the Navigation Tree window with the SITE and cabinet
selected, select the Display menu and from it the Contained
Devices option to determine the current database configuration
set for the unit.
• The Cabinet Type displayed shows either the M_CELLARENA

or the M_CELLARENA_MACRO cabinet type.
• If the Cabinet Type is set for the wrong type of Horizon unit,
the Cabinet Type must be modified in the CM database. Go
to step 4.
• If the Cabinet Type is correctly set up, the wrong hardware is

probably installed onsite. Go to step 5.
4 At the BSC, a network management OMC-R operator must modify
the current Cabinet Type in the CM database for the Horizon
unit. With the cabinet selected, select the Edit menu and
from it the Detailed View option. Then select Edit from
the Edit menu to change the Cabinet Type at the site:
M_CELLARENA represents an Horizon micro unit.

M_CELLARENA_MACRO represents an Horizon compact
Booster unit.
5 Send a field representative to the site to install the correct unit.
Refer to the manual, Technical Description: BSS Command

Reference (68P02901W23) for information regarding MMI
commands. There are restrictions for using the enclosed
modify_value MMI command.

42-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. SITE: EMU download failure
29. SITE: EMU download failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
EMU Firmware upgrade has failed.
Download Failure error codes:

• 0x03 EMU did not accept download command.
• 0x05 Timeout waiting for message from COM.
• 0x06 Download canceled by the EMU.
• 0x10 Unable to put EMU in auto baud detect state.
• 0x13 Invalid EMU slot number received.
Possible causes
The firmware may have failed to upgrade due to:

• EMU did not accept download command.
• Timeout waiting for message from COM.
• Download canceled by the EMU.
• Unable to put EMU in auto baud detect state.
• XMOD does not have the MIX_BACK_TERM locked.
• Unable to initiate a dialog with the COM.
• Invalid EMU slot number received.
68P02901W26-S 42-73
Nov 2007
Procedure
Procedure 42-30 EMU download failure
1 The operator must analyze the download failure cause.

2 Correct the situation and then try to force a download, thereby downloading
the correct firmware version or object.
42-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. SITE: NVM board failure
30. SITE: NVM board failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The NVM board failed or was removed from the system. This alarm applies to BSC and RXCDR.
Possible causes

• The NVM board failed.
• The NVM board was removed from the system.
Procedure
Procedure 42-31 NVM board failure
1 Send a field representative to the site to reinsert or replace the NVM board.
2 The NVM board with a PCMCIA card inserted in socket 1 is considered a
single FRU.
This PCMCIA card inserted in socket 1 of the NVM board is not

interchangeable with PCMCIA cards used elsewhere in the BSS.
68P02901W26-S 42-75
Nov 2007

42-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. SITE: Failure of PCMCIA card 1 on NVM board
31. SITE: Failure of PCMCIA card 1 on NVM board

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The PCMCIA card failed or was removed from socket 1 on the NVM board.
This PCMCIA card inserted in socket 1 of the NVM board is not interchangeable with
PCMCIA cards used elsewhere in the BSS.
Possible causes

• The PCMCIA card failed.
• The PCMCIA card was removed from socket 1 of the NVM board.
Procedure
Procedure 42-32 Failure of PCMCIA card 1 on NVM board
1 Send a field representative to the site to re-insert or replace the NVM board.
2 The NVM board with a PCMCIA card inserted in socket 1 is considered a
single FRU.
68P02901W26-S 42-77
Nov 2007

42-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 32. SITE: Last GBL failed
32. SITE: Last GBL failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The last GBL communicating link between the BSS and the Serving GPRS Support Node (SGSN)
has failed. All GBL communication links are now OOS. The BSS notifies the OMC-R that the
final GBL has been disconnected.
Possible causes

• A protocol error occurred.
• The communications medium failed.
Procedure
Procedure 42-33 Last GBL failed
1 Review the Alarms window to identify the current GBL alarms.

2 Initiate fault isolation and fault resolution procedures to restore
the GBL communication links.
68P02901W26-S 42-79
Nov 2007
33. SITE: BSSGP status message received from the SGSN Chapter 42: SITE Alarms
33. SITE: BSSGP status message received from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU received a BSS GPRS Protocol (BSSGP) status message indicating that the Serving
GPRS Support Node (SGSN) received an invalid message. This alarm may also indicate a
congestion condition at the SGSN. SGSN reports this condition.
The BSSGP status message contents are displayed in the Additional information field.
Possible causes

• SGSN is unable to interpret a BSSGP status message sent by the BSS.
• There is an exceptional condition at the SGSN.
Procedure
Procedure 42-34 BSSGP Status message received from the SGSN
1 Initiate fault isolation and resolution procedures at the SGSN.

42-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. SITE: Erroneous BSSGP message received from the SGSN
34. SITE: Erroneous BSSGP message received from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU received an erroneous BSS GPRS Protocol (BSSGP) message from the Serving GPRS
Support Node (SGSN). After this alarm is generated, a status message is sent back to the SGSN.
The erroneous BSSGP message contents are displayed in the Additional information field.
Possible causes
The PCU is unable to interpret a BSSGP message sent by the SGSN.
Procedure
Procedure 42-35 Erroneous BSSGP message received from the SGSN

68P02901W26-S 42-81
Nov 2007
35. SITE: Network service status message received from the SGSN Chapter 42: SITE Alarms
35. SITE: Network service status message received

from the SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU received a network service status message indicating that the Serving GPRS Support
Node (SGSN) received an invalid message. This alarm may also indicate that an exceptional
condition occurred at the SGSN. SGSN reports this condition.
The BSSGP status message contents are displayed in the Additional information field.
Possible causes

• The SGSN is unable to interpret a network service status message sent by the BSS.
• An exceptional condition may have occurred at the SGSN.
Procedure
Procedure 42-36 Network service status message received from the SGSN

42-82 68P02901W26-S
Nov 2007
SITE: Erroneous network service message received from the SGSN
36. SITE: Erroneous network service message received

from the SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU received an erroneous network service message from the Serving GPRS Support
Node (SGSN). After this alarm is generated, a status message is sent back to the SGSN. SGSN
reports this condition.
The erroneous network service message contents are displayed in the Additional information
field.
Possible causes
The PCU is unable to interpret a network service message sent by the SGSN.
Procedure
Procedure 42-37 Erroneous network service message received from the SGSN

68P02901W26-S 42-83
Nov 2007
37. SITE: No NS-VC block acknowledgment from the SGSN Chapter 42: SITE Alarms
37. SITE: No NS-VC block acknowledgment from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU has repeated the NS-VC (PVC) Block message the maximum number of times without
receiving an acknowledgment from the Serving GPRS Support Node (SGSN).
The corresponding NS-VC identifier (NS-VCI) is displayed in the Additional information field.
The range of values for the NS-VCI is 0 to 65535. For example, NS-VC 87 is displayed in the
Additional information field as NS-VCI 87.
Possible causes

• An acknowledgment message was not received from the SGSN.
Procedure
Procedure 42-38 No NS-VC block acknowledgment from the SGSN

verification of the PVC end-to-end connections.
42-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 38. SITE: No NS-VC unblock acknowledgment from the SGSN
38. SITE: No NS-VC unblock acknowledgment from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU has repeated the NS-VC(PVC) Unblock message the maximum number of times without
The corresponding NS-VC identifier (NS-VCI) is displayed in the Additional information field.
Possible causes

Procedure
Procedure 42-39 No NS-VC unblock acknowledgment from the SGSN

68P02901W26-S 42-85
Nov 2007
39. SITE: No NS-VC alive acknowledgment from the SGSN Chapter 42: SITE Alarms
39. SITE: No NS-VC alive acknowledgment from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU has repeated the NS-VC (PVC) Alive message the maximum number of times without
System action
The PVC is OOS and blocked from GPRS use.
The corresponding NS-VC identifier (NS_VCI) is displayed in the Additional information field.
Possible causes

42-86 68P02901W26-S
Nov 2007
Procedure
Procedure 42-40 No NS-VC alive acknowledgment from the SGSN

68P02901W26-S 42-87
Nov 2007
40. SITE: No NS-VC reset acknowledgment from the SGSN Chapter 42: SITE Alarms
40. SITE: No NS-VC reset acknowledgment from the

SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The PCU has repeated the NS-VC (PVC) Reset message the maximum number of times without
System action
The PVC is OOS and blocked from GPRS use.
The corresponding NS-VC identifier (NS_VCI) is displayed in the Additional information field.
Possible causes

• An acknowledgment message was not received from SGSN.
42-88 68P02901W26-S
Nov 2007
Procedure
Procedure 42-41 No NS-VC reset acknowledgment from the SGSN

68P02901W26-S 42-89
Nov 2007
41. SITE: Last NS-VC for the PCU failed Chapter 42: SITE Alarms
41. SITE: Last NS-VC for the PCU failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The last NS-VC (PVC) for the PCU-SGSN link failed.
System action
All cells are notified that the GPRS is no longer available.
The BSSGP Virtual Connection identifier (BVCI) is displayed in the Additional information
field. The range of values for the BVCI is 0 to 65535. For example, BVC 87 is displayed in
the Additional information field as BVCI 87.
Possible causes
Frame Relay network problems are occurring.
Procedure
Determine if the last GBL failed. Perform the following procedure to resolve the alarm.
Procedure 42-42 Last NS-VC for the PCU failed
If the last GBL is... Then...

OOS Initiate fault isolation and fault
resolution procedures to restore
the GBL communications links.
not OOS Initiate fault isolation and
resolution procedures for the
frame network connections.
42-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 42. SITE: Last TRAU GDS failed
42. SITE: Last TRAU GDS failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The last TRAU GDS data link failed. No data is carried between the BSC and the PCU.
Possible causes
Link fault.
Procedure
Procedure 42-43 Last TRAU GDS failed
Initiate fault isolation and resolution procedures for the TRAU GDS links.
68P02901W26-S 42-91
Nov 2007
43. SITE: Last PRP or PXP failed Chapter 42: SITE Alarms
43. SITE: Last PRP or PXP failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
This alarm indicates that the last DPROC with PRP functionality (that is a PXP or PRP DPROC)
has gone out of service and the GPRS functionality is not available.
Possible causes
The associated device has been taken out of service by an operator maintenance command or
there has been an equipment failure.
Procedure
Procedure 42-44 Last PRP or PXP failed
1 First check the state of the failed devices using the command: dis_pr (site
number) or state (site number) (dproc device numbers).
2 Refer to Technical Description: BSS Command Reference (68P02901W23)
for more information. If the device state is not busy-unlocked, determine
if the device is currently taken out of service by a maintenance command.
If not, send a field representative to the site to determine the cause of the
failure.
42-92 68P02901W26-S
Nov 2007

68P02901W26-S 42-93
Nov 2007
45. SITE: No signaling BVC reset acknowledgment from the SGSN Chapter 42: SITE Alarms
45. SITE: No signaling BVC reset acknowledgment

from the SGSN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The PCU has repeated the BVC Reset message the maximum number of times for the signaling
BVCI without receiving any acknowledgment from the SGSN.
Possible causes
This alarm is typically due to frame relay network or SGSN problems.
Procedure
Procedure 42-45 No signaling BVC reset acknowledgment from the SGSN
1 Investigate why a reset acknowledgment was not received from the SGSN
for the signaling BVC.
2 Clear the alarm.
42-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 46. SITE: DSW switching hardware required at site
46. SITE: DSW switching hardware required at site

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Half rate calls on half rate capable RTFs that have 8 kbps TRAU allowed, will be blocked if 16
kbps switching is in operation. If the RTF is configured for 8 k backhaul, but the BSS does not
support this (BSC has KSWs present), then half rate is effectively disabled for this carrier, and
the Site[46] alarm is raised. The fix for this is to either swap out the KSWs for DSWs at the BSC,
or to reconfigure the RTF so as not to require 8 k backhaul and thus be consistent with the BSC.
Possible causes
A KSW has been found to exist in the system when the database was setup assuming that DSW
switches would be used throughout the BSC.
Procedure
Perform the following procedures to resolve the alarm.
Procedure 42-46 DSW Hardware Required
Swap out all KSWs for DSWs at the BSC.
68P02901W26-S 42-95
Nov 2007
Procedure 42-47 Re-congure
Set all half rate enabled RTFs allow_8k_trau to no.
Each half rate enabled RTF requires 2 additional E1 backhaul timeslots.
42-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. SITE: Database corruption detected
50. SITE: Database corruption detected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The database object at the site is invalid or corrupt.
6 bytes. Bytes 1, 2 – (UWORD) location, index of corruption in the database. Bytes 3 to 6 –

(ULONG) contents of the database at the location that caused the error.
Possible causes
Memory corruption or software error has rendered the database invalid at the site.
Procedure
Procedure 42-48 Database corruption detected
A valid database object is reloaded to the site.
68P02901W26-S 42-97
Nov 2007
51. SITE: Software patch installation failure Chapter 42: SITE Alarms
51. SITE: Software patch installation failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Software patch installation has failed on a specified site.
Possible causes
The possible cause for this alarm is software error.
Procedure
Procedure 42-49 Software patch installation failure
Carry out the patch installation again.
When the alarm occurs, the BSS backs out the patch level to 0 within the BSS.
42-98 68P02901W26-S
Nov 2007
Chapter
43
TBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TDM Bus (TBUS) alarms are covered in this chapter and include the following procedures:
• 0. TBUS: Remote KSWl loopback test failure on page 43-3.
• 3. TBUS: Local KSWX/DSWX TDM error on page 43-5.
• 4. TBUS: Remote KSWX/DSWX TDM error on page 43-7.
68P02901W26-S 43-1
Nov 2007
Introduction to TBUS alarms Chapter 43: TBUS Alarms
Introduction to TBUS alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
TBUS alarms
TDM Bus (TBUS) device.
A TBUS is a logical device made up of a KSW, the cage containing the TBUS, local and remote
KSWX cards (if used), and the fiber optic cables interconnecting the KSWX cards. Each cage
has two TBUS devices (one active and one redundant).
43-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TBUS: Remote KSWl loopback test failure
0. TBUS: Remote KSWl loopback test failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
Over 50% of the TDM loopback tests, between the GPROCs in an extended cage and the active,
remote KSW, have failed, but the remote KSW is tested successfully. This indicates that a fault
exists with the TBUS, and not with the KSW.
System action
The system swaps the faulty KSWX with the redundant KSWX. If both the KSWX reporting the
alarm and the redundant KSWX are OOS, the site resets.
Possible causes

• A KSW Extender (KSWX) card failed.
• The KSWX fiber link failed.
• The TBUS fiber link failed.
• The TBUS backplane connections failed.
• The toggle switch on the KSWX card is in the down (disable) position.
68P02901W26-S 43-3
Nov 2007
Procedure Chapter 43: TBUS Alarms
Procedure
Procedure 43-1 Remote KSW loopback test failure

43-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. TBUS: Local KSWX/DSWX TDM error
3. TBUS: Local KSWX/DSWX TDM error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The local KSWX/DSWX card detected that it is no longer receiving data through the receive fiber.
System action
The TBUS is placed OOS. The system swaps the faulty TBUS with the redundant TBUS. If both
the TBUS reporting the alarm and the redundant TBUS are OOS, the site resets.
Possible causes

• The fiber link between the local and remote KSWX/DSWX failed.
• The fiber link between the local and remote KSWX/DSWX was disconnected.
• A KSWX/DSWX card failed.
Procedure
Procedure 43-2 Local KSWX/DSWX TDM error
68P02901W26-S 43-5
Nov 2007

43-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. TBUS: Remote KSWX/DSWX TDM error
4. TBUS: Remote KSWX/DSWX TDM error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The remote KSWX/DSWX card detected that it is no longer receiving data through the receive
fiber.
System action
The TBUS is placed OOS. The system swaps the faulty TBUS with the redundant TBUS. If both
the TBUS reporting the alarm and the redundant TBUS are OOS, the site resets.
The additional information displays the cage and slot number of the remote KSWX card that
detected that it was not receiving data. The cage and slot are presented as hexadecimal values.
If the values 00 is displayed, a different KSWX/DSWX fault condition has been resolved. The
current remote KSWX/TDM fault condition still exists and must be resolved.
Possible causes

• The fiber link between the local and remote KSWX/DSWX failed.
• The fiber link between the local and remote KSWX/DSWX was disconnected.
• A KSWX/DSWX card failed.
68P02901W26-S 43-7
Nov 2007
Procedure
Procedure 43-3 Remote KSWX/DSWX TDM error

43-8 68P02901W26-S
Nov 2007
Chapter
44
TDM Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TDM alarms are covered in this chapter and include the following procedures:
• {25002} 5. TDM: Bus swap could not be initiated on page 44-3.
• {25002} 229. TDM: Swap test audit failure on page 44-4.
68P02901W26-S 44-1
Nov 2007
Introduction to TDM alarms Chapter 44: TDM Alarms
Introduction to TDM alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
TDM alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with
the TDM device.
44-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. TDM: Bus swap could not be initiated
5. TDM: Bus swap could not be initiated

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{25002}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated when the FM software detects that the redundant TDM is not available
when the active TDM needs to be swapped with the redundant TDM.
This alarm is reported against the TDM of the redundant bus.
Possible causes
The redundant TDM is unavailable due to missing or faulty hardware.
Procedure
Procedure 44-1 Bus swap could not be initiated
1 Determine the cause of redundant TDM failure.

2 If... Then...
the hardware is missing insert the missing hardware.
the hardware is faulty send a field representative to the site
to replace the faulty hardware.
68P02901W26-S 44-3
Nov 2007
229. TDM: Swap test audit failure Chapter 44: TDM Alarms
229. TDM: Swap test audit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{25002}
Clearing Type: FMIC

Category: Equipment
Description
This alarm is generated by the Audit process when either:

• A swap of the TDM device could not be attempted due to devices being out of service, or
• A swap of the TDM device had been attempted but failed and a recovery of swapping
back to the original device was performed.
This alarm is reported against the TDM of the redundant bus.
Possible causes

• Devices Out of service (TBUS, KSW, OML).
• Alarms were detected on the redundant upon swapping over to the redundant highway.
Procedure
Procedure 44-2 Swap test audit failure
Determine the cause of the unavailability of the redundant TDM

highway and take corrective action.
44-4 68P02901W26-S
Nov 2007
Chapter
45
TIMESLOT Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TIMESLOT alarms are covered in this chapter and include the following procedures:
• 0. TIMESLOT: Radio frequency losses while using a TCH - PM on page 45-3.
• 1. TIMESLOT: Channel request from MS failed - PM on page 45-4.
• 4. TIMESLOT: No Timeslot HealthInfo Alarm on page 45-6.
68P02901W26-S 45-1
Nov 2007
Introduction to TIMESLOT alarms Chapter 45: TIMESLOT Alarms
Introduction to TIMESLOT alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
TIMESLOT alarms
TIMESLOT alarms.
45-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TIMESLOT: Radio frequency losses while using a TCH - PM
0. TIMESLOT: Radio frequency losses while using a

TCH - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The RF_LOSSES_TCH statistic threshold has been reached.
This statistic counts the number of calls lost while using a Traffic Channel (TCH) due to RF
problems.
Possible causes
The BTS has lost contact with the MS due to RF interference.
Procedure
Procedure 45-1 Radio frequency losses while using a TCH - PM

alarms procedures for the current hardware
alarms. After the hardware alarms
are cleared, clear the alarm.
no currently active hardware MSs are probably experiencing radio
alarms problems. Clear the alarm.
68P02901W26-S 45-3
Nov 2007
1. TIMESLOT: Channel request from MS failed - PM Chapter 45: TIMESLOT Alarms
1. TIMESLOT: Channel request from MS failed - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The CHAN_REQ_MS_FAIL statistic threshold is reached.
This statistic counts the number of instances a BSS times out waiting for the MS to establish a
call on a specific Standalone Dedicated Control Channel (SDCCH).
This is considered a normal occurrence when an MS is moving out of range, is failing or is
switched off. However, frequent occurrences of this event within a short period of time and/or,
if geographically clustered, may indicate a hardware failure.
Possible causes
A hardware failure may have occurred, if a BSS has timed out before allowing an MS to establish
a call (when SDCCH resources are available for an immediate TCH assignment).
45-4 68P02901W26-S
Nov 2007
Procedure
Determine if there are any currently active DRI alarms. Perform the following procedure to
resolve the alarm.
Procedure 45-2 Channel request from MS failed - PM

currently active DRI alarms Initiate isolation and corrective
procedures for the current DRI
alarms. After the DRI alarms are
no currently active DRI alarms MSs are probably experiencing radio
problems. Clear the alarm.
68P02901W26-S 45-5
Nov 2007
4. TIMESLOT: No Timeslot HealthInfo Alarm Chapter 45: TIMESLOT Alarms
4. TIMESLOT: No Timeslot HealthInfo Alarm

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
Timeslot Health Information file has not been received for ((BAD_ALARM_INTERVAL_COUNT /
2) + 1) consecutive intervals.
None.
Possible causes
• OML out of service.
• TS Health Information collection disabled at BSS.
Procedure
Procedure 45-3 No Timeslot HealthInfo
1 Check the OML status.

2 Check the BSS flag enabling collection and reporting of TS Health
Information.
45-6 68P02901W26-S
Nov 2007
Chapter
46
TRU Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TopCell Radio Unit (TRU) alarms are covered in this chapter and include the following
procedures:
• 0. TRU: Door open on page 46-3.
• 1. TRU: Power supply unit failure on page 46-5.
• 2. TRU: Power mains failure on page 46-7.
• 5-6. TRU: Customer defined alarm 1-2 on page 46-9.
68P02901W26-S 46-1
Nov 2007
Introduction to TRU alarms Chapter 46: TRU Alarms
Introduction to TRU alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
TRU alarms
TopCell Radio Unit (TRU).
46-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TRU: Door open
0. TRU: Door open

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
If a TRU cabinet door is open, close it.
Possible causes

• The cabinet door opened by a field engineer may not be properly secured when closed.
• The door latches are defective.
• An illegal entry.
Procedure
Procedure 46-1 Door open
68P02901W26-S 46-3
Nov 2007
Procedure Chapter 46: TRU Alarms

46-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. TRU: Power supply unit failure
1. TRU: Power supply unit failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The TRU Power Supply Unit (PSU) lost dc power.
System action
The BSS software attempts to redirect the calls to transceivers in neighboring TRUs.
Possible causes

• The dc output voltage is out of the specified operating range.
• The power supply fails.
68P02901W26-S 46-5
Nov 2007
Procedure
Procedure 46-2 Power supply unit failure

46-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. TRU: Power mains failure
2. TRU: Power mains failure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Category: Equipment
Description
The TRU lost ac power.
System action
The BSS software attempts to redirect calls to the transceivers in neighboring TRUs.
Possible causes

• The ac power provided by the local electricity supplier is lost.
• The circuit breaker opened.
68P02901W26-S 46-7
Nov 2007
Procedure
Procedure 46-3 Power mains failure
1 Contact the power company to determine whether there is an actual

power failure.
If there is... Then...
a power failure Go to step 2.
not a power failure Send field representative to the
2 Determine the nature and seriousness of the power failure.
While waiting for power to be restored, send a field representative
to the site to determine how long the backup battery power can
sustain the site.

46-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5-6. TRU: Customer dened alarm 1-2
5-6. TRU: Customer dened alarm 1-2

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Each of the TRU alarms are related to a specific environmental factor or condition at a specific
site. These alarms are user-defined.
Possible causes

• An environmental sensor is activated.
• An environmental sensor failed.
Procedure
Procedure 46-4 Customer dened alarm 1-2
68P02901W26-S 46-9
Nov 2007

46-10 68P02901W26-S
Nov 2007
Chapter
47
XBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Transcoder to BSS Link (XBL) alarms are covered in this chapter and include the following
procedures:
• 0. XBL: Invalid received frames - PM on page 47-3.
• 1. XBL: FRMR frames - PM on page 47-5.
• 2. XBL: Expiration of N2 - PM on page 47-7.
• 10. XBL: Link disconnected on page 47-9.
• 11. XBL: LAPD protocol error on page 47-12.
• 13. XBL: LAPD protocol error threshold exceeded on page 47-14.
• 15. XBL: Too many LAPD protocol errors on page 47-17.
• 16. XBL: HDLC channel open failed on page 47-18.
68P02901W26-S 47-1
Nov 2007
Introduction to XBL alarms Chapter 47: XBL Alarms
Introduction to XBL alarms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
XBL alarms
remote transcoder to BSS Link (XBL).
The XBL carries the signaling link traffic between the BSC and the RXCDR site. The XBL uses
the Multiple Serial Interface link (MMS: E1 link) hardware as its underlying communication
link medium.
47-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. XBL: Invalid received frames - PM
0. XBL: Invalid received frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The INVALID_FRAMES_RX statistic threshold is reached.
This statistic counts the number of the invalid frames received on the X.25/LAPD link.
For further information, refer to XBL statistics chapter in the manual, Maintenance Information:
GSM Statistics Application (68P02901W56).
Possible causes
An invalid frame is received on the X.25/LAPD link.
Procedure

68P02901W26-S 47-3
Nov 2007
Procedure Chapter 47: XBL Alarms

47-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. XBL: FRMR frames - PM
1. XBL: FRMR frames - PM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The FRMR statistic threshold is reached.
the frames are not correctable.
Possible causes
A frame-reject message is received on the X.25/LAPD link.
Procedure

68P02901W26-S 47-5
Nov 2007

47-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. XBL: Expiration of N2 - PM
2. XBL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The N2_EXPIRY statistic threshold is reached.
This statistic indicates that the maximum number of link alignment retries is attempted without
success.
Possible causes
The X.25/LAPD link failed due to a hardware fault or repair action.
68P02901W26-S 47-7
Nov 2007
Procedure


47-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. XBL: Link disconnected
10. XBL: Link disconnected

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
An XBL is disconnected on the MMS. No signaling information between the BSC and the RXCDR
is passed over the disconnected link.

first 00 to FF The first two bytes are the reason codes.
second 00 to FF • 00 = Normal disconnect
• C6 = XBL guard timer expired

third 01 to 1F MMS timeslot.
fourth 0A MMS device type.
fifth 00 to FF MMS device identifiers.
sixth 00 to FF
seventh 00 to FF
68P02901W26-S 47-9
Nov 2007
Possible causes Chapter 47: XBL Alarms
Possible causes

• A protocol or transmission problem.
• An XBL guard timer expired.
Procedure
Wait for 10 minutes after the alarm is reported before continuing with this procedure.
If an RXCDR reboots, this delay allows sufficient time for the reboot process to
complete.
1 Determine the state of the XBL device.

If the XBL is... Then...
busy and unlocked The fault condition no longer exists.
If it is a recurrence of this alarm,
the E1 link is probably faulty. Send
a field representative to the site to
2 Attempt to restore the XBL device to service.
returns to service The fault condition no longer exists.
If this is a recurrence of this alarm,
the E1 link is probably faulty. Send
a field representative to the site to
Continued
47-10 68P02901W26-S
Nov 2007

information field.
site to isolate and correct the link
fault.
procedures.
procedures.

68P02901W26-S 47-11
Nov 2007
11. XBL: LAPD protocol error Chapter 47: XBL Alarms
11. XBL: LAPD protocol error

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Description
The XBL detected a LAPD protocol error due to a problem on one of the E1 links.
The MMS timeslot, the reason for the LAPD error and the MMS ID are displayed in the
Additional information field in the following format:
Timeslot: #; LAPD Error: #; MMS ###
Where # represents a decimal value.
Possible causes
The LAPD Error code in the Additional information field corresponds to a possible cause for
the alarm, as shown in Table 47-2.
Table 47-2 LAPD error codes

0 or 4 The timeslot assignments are not correct. The connection to
the physical link may have a different protocol. The physical
media is faulty (for example, a noisy communication link).
1 The external equipment experienced an outage. The physical
frame dropped. Out-of-sequence frames were received.
2 or 3 The connection is invalid. The DACS link is physically
connected to the wrong line.
Continued
47-12 68P02901W26-S
Nov 2007
Table 47-2 LAPD error codes (Continued)

5 or 8 The nailed connection is missing. The connection may be
correct for one direction, but is incorrect for the other
direction. The physical media in one direction of the media is
faulty.
6 The remote side of the link connection sent I-frames before
the link was established.
7 or 9 A physical link outage affected the local to remote direction.
Procedure

2 Determine the state of the MMS identified in the Additional information field.
busy and unlocked Send a field representative to the site to
appropriate action.
not busy and unlocked Review the alarm or event window for the
MMS alarm and initiate the appropriate

68P02901W26-S 47-13
Nov 2007
13. XBL: LAPD protocol error threshold exceeded Chapter 47: XBL Alarms
13. XBL: LAPD protocol error threshold exceeded

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one-minute period.
System action
The system soft resets the affected XBL.
A one-byte code is displayed in the Additional information field in the output for this alarm, as
shown in Table 47-3. The code indicates the cause for the alarm.
Value (Hex) Denition

01 This alarm is caused by an excessive sequence of errors.
05 This alarm is caused by a SABM extended received error.
Possible causes
47-14 68P02901W26-S
Nov 2007
Procedure
Wait for 10 minutes after the alarm is reported before continuing with this procedure.
If an RXCDR reboots, this delay allows sufficient time for the reboot process to
complete.
1 Determine the state of the XBL device.

If the XBL is... Then...
busy_unlocked The fault condition no longer
the link fault.
2 Attempt to restore the XBL device to service.

the link fault.
Continued
68P02901W26-S 47-15
Nov 2007

information field.
busy_unlocked The E1 link is probably faulty.
site to isolate and correct the
faulty link.
busy_unlocked The MMS device is faulty.
Review the alarm or event window
procedures.
not busy_unlocked The MSI device is faulty.
Review the alarm or event window
procedures.

47-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. XBL: Too many LAPD protocol errors
15. XBL: Too many LAPD protocol errors

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
Too many LAPD protocol errors are received indicating poor link quality.
6 bytes: byte 1 - MMS timeslot, byte 2 - LAPD fault code, bytes 3 to 6 - MMS device ID.
Possible causes
Four or more LAPD protocol errors are received within one second indicating major problems
with the XBL link.
Procedure
Procedure 47-7 Too many LAPD protocol errors
1 Check report logs for repeated occurrence of this alarm. If the alarm
occurs more than expected, monitor the state of the MMS related to the
XBL and INS the XBL device. A field representative may need to visit the
site to determine the quality of the link and adjust or correct or replace
it as necessary.
2 Refer alarm handling at the OMC customer documentation.
3 Investigate the XBL further if this keeps happening.
68P02901W26-S 47-17
Nov 2007
16. XBL: HDLC channel open failed Chapter 47: XBL Alarms
16. XBL: HDLC channel open failed

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Clearing Type: FMIC

Description
The Central Authority (CA) reports that the HDLC channel has failed to open.
1 byte - HDLC channel number.
Possible causes
The current HDLC channel is not available.
Procedure
Procedure 47-8 HDLC channel open failed
If... Then...
• Reset or replace BSP for

the XBL fails to become B-U bsc_type 1.
• Replace OMP for bsc_type 2.
47-18 68P02901W26-S
Nov 2007
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ABSS 0 alarm alarm categories (contd.)

last XBL link failure . . . . . . . . . . . . 2-2 processing . . . . . . . . . . . . . . . 1-11
active & standby LAN failure quality of service . . . . . . . . . . . . 1-10
LAN 0 alarm . . . . . . . . . . . . . . 27-3 alarm clearing types . . . . . . . . . . . 1-12
active alarm list full FMIC . . . . . . . . . . . . . . . . . . 1-12
SITE 22 alarm. . . . . . . . . . . . . . 42-58 Intermittent . . . . . . . . . . . . . . . 1-12
active alarms exceed upper limit of OIC . . . . . . . . . . . . . . . . . . . 1-12
OMC 30029 alarm . . . . . . . . . . . 32-72 alarm impact
active link connection failure loss of capacity . . . . . . . . . . . . . 1-16
BTP 234 alarm . . . . . . . . . . . . . 7-41 loss of redundancy . . . . . . . . . . . 1-16
DHP 234 alarm . . . . . . . . . . . . . 15-58 loss of service . . . . . . . . . . . . . . 1-16
DRI 234 alarm . . . . . . . . . . . . 17-298 alarm severities
MSI 234. . . . . . . . . . . . . . . . . 30-30 clear . . . . . . . . . . . . . . . . . . 1-12
active local FOX failure critical . . . . . . . . . . . . . . . . . 1-11
SITE 9 alarm . . . . . . . . . . . . . . 42-28 investigate . . . . . . . . . . . . . . . 1-12
active multiplexer 0 loopback failure major . . . . . . . . . . . . . . . . . . 1-11
SITE 3 alarm . . . . . . . . . . . . . . 42-15 minor . . . . . . . . . . . . . . . . . . 1-11
active multiplexer 1 loopback failure warning . . . . . . . . . . . . . . . . . 1-11
SITE 5 alarm . . . . . . . . . . . . . . 42-19 alarm states
active multiplexer 2 loopback failure cleared . . . . . . . . . . . . . . . . . 1-10
SITE 7 alarm . . . . . . . . . . . . . . 42-23 deferred. . . . . . . . . . . . . . . . . 1-10
active remote FOX 0 failure handling . . . . . . . . . . . . . . . . 1-10
SITE 11 alarm. . . . . . . . . . . . . . 42-32 new . . . . . . . . . . . . . . . . . . . . 1-9
active remote FOX 1 failure seen. . . . . . . . . . . . . . . . . . . . 1-9
SITE 13 alarm. . . . . . . . . . . . . . 42-36 alarm types
active remote FOX 2 failure tagged
SITE 15 alarm. . . . . . . . . . . . . . 42-40 primary alarm. . . . . . . . . . . . . . 1-5
additional field secondary alarms . . . . . . . . . . . . 1-5
information . . . . . . . . . . . . . . . 1-18 untagged . . . . . . . . . . . . . . . . . 1-4
advisory detected alarms
OMC 30035 alarm . . . . . . . . . . . 32-86 overview . . . . . . . . . . . . . . . . . 1-3
affected functional units . . . . . . . . . 1-15 ancillary cabinet overtemperature
Agent Buffer Overflow - Rlogin Session IAS 87 alarm . . . . . . . . . . . . . . 25-95
BSS 24 alarm . . . . . . . . . . . . . . 6-36 assigned timeslot counter overflow
air conditioning unit failure MSI 6 alarm. . . . . . . . . . . . . . . 30-15
IAS 84 alarm . . . . . . . . . . . . . . 25-89 assigned timeslot counter underflow
alarm MSI 5 alarm. . . . . . . . . . . . . . . 30-13
impact list. . . . . . . . . . . . . . . . 1-15 attempt at allocating a TCH failed
alarm board failed CELL 25, PM alarm . . . . . . . . . . . 12-59
IAS 108 alarm. . . . . . . . . . . . . 25-133 attempt at allocating an SDCCH failed
alarm categories CELL 1, PM alarm . . . . . . . . . . . 12-9
communication . . . . . . . . . . . . . 1-10 auxiliary alarm 1
environmental. . . . . . . . . . . . . . 1-11 IAS 109 alarm. . . . . . . . . . . . . 25-135
equipment . . . . . . . . . . . . . . . 1-11 AXCDR 0 alarm
link . . . . . . . . . . . . . . . . . . . 1-11 BSC detecting CIC validation failure . . . 3-3
NHA event . . . . . . . . . . . . . . . 1-11 AXCDR 1 alarm
68P02901W26-S IX-19
Nov 2007
Index
AXCDR 1 alarm (contd.) AXCDR ID mismatch with RXCDR network entity

AXCDR ID mismatch with RXCDR network ID
entity ID . . . . . . . . . . . . . . . . . 3-6 AXCDR 1 alarm . . . . . . . . . . . . . . 3-6
AXCDR alarms
introduction . . . . . . . . . . . . . . . . 3-2
bad clock source or SYNC OCXO (oscillator) BSP 1 alarm (contd.)

replacement EEPROM flash failure - no valid bootstrap code
DHP 24 alarm . . . . . . . . . . . . . . 15-15 object present. . . . . . . . . . . . . . . 5-4
Bad clock source or SYNC OCXO replacement BSP 17 alarm
required EEPROM flash programming failure . . . 5-8
GPROC 24 alarm . . . . . . . . . . . . 23-16 BSP 20 alarm
bad HO reference numbers from the MS LAPD controller failure . . . . . . . . . 5-10
CELL 19, PM alarm . . . . . . . . . . . 12-49 BSP 21 alarm
baseband hopping GSM timeslot misalignment EEPROM flash programming failure . . 5-11
DRI 193 alarm . . . . . . . . . . . . 17-263 BSP 22 alarm
DRI 52 alarm . . . . . . . . . . . . . . 17-86 SWFM indication . . . . . . . . . . . . 5-13
baseband hopping TDM link error BSP 231 alarm
DRI 192 alarm . . . . . . . . . . . . 17-261 TDM interface configuration failure. . . 5-41
DRI 51 alarm . . . . . . . . . . . . . . 17-84 BSP 232 alarm
baseband hopping timeslot counter mismatch processor bus communication failure . . 5-43
DRI 48 alarm . . . . . . . . . . . . . . 17-78 BSP 239 alarm
battery backup input failure process safe test audit failure . . . . . . 5-44
IAS 60 alarm . . . . . . . . . . . . . . 25-65 BSP 254 alarm
battery backup output failure device failure . . . . . . . . . . . . . . 5-46
IAS 59 alarm . . . . . . . . . . . . . . 25-63 BSP 30 alarm
battery box temperature high clock A signal loss. . . . . . . . . . . . 5-14
IAS 107 alarm. . . . . . . . . . . . . 25-131 BSP 31 alarm
BCUP 0 alarm clock B signal loss. . . . . . . . . . . . 5-17
unexpected board type . . . . . . . . . . 4-3 BSP 32 alarm
BCUP 1 alarm TDM interface failure - assigned timeslot
serial bus connection failure . . . . . . . 4-5 counter underflow . . . . . . . . . . . 5-20
BCUP 10 alarm BSP 33 alarm
over temperature warning . . . . . . . 4-11 TDM interface failure - assigned timeslot
BCUP 8 alarm counter overflow . . . . . . . . . . . . 5-22
output failure . . . . . . . . . . . . . . . 4-7 BSP 34 alarm
BCUP 9 alarm TDM interface failure - TDM parity
input failure. . . . . . . . . . . . . . . . 4-9 error . . . . . . . . . . . . . . . . . . 5-24
BCUP alarms BSP 35 alarm
DPSM, EPSM, IPSM . . . . . . . . . . . 4-2 LAN connection failure . . . . . . . . . 5-26
FRUs . . . . . . . . . . . . . . . . . . . 4-2 BSP 39 alarm
bit error daily threshold exceeded software failure . . . . . . . . . . . . . 5-28
MMS 12 alarm . . . . . . . . . . . . . 29-24 BSP 40 alarm
bit error hourly threshold exceeded spurious interrupt. . . . . . . . . . . . 5-30
bit error OOS threshold exceeded Unexpected board type . . . . . . . . . 5-32
BSC detected MCU to MCU communication Memory location fault. . . . . . . . . . 5-34
failure BSP 50 alarm
SITE 2 alarm . . . . . . . . . . . . . . 42-12 EEPROM SW flash programming fail
BSC detecting CIC validation failure ure . . . . . . . . . . . . . . . . . . . 5-35
AXCDR 0 alarm . . . . . . . . . . . . . . 3-3 BSP 51 alarm
BSP 1 alarm EEPROM SW flash programming fail
ure . . . . . . . . . . . . . . . . . . . 5-36
IX-20 68P02901W26-S
Nov 2007
Index
BSP 8 alarm BSS 40 alarm, Circuit Fault Cleared on Radio

EEPROM flash object failure . . . . . . . 5-6 Channel
BSP alarms BSS: Circuit Fault Cleared on Radio
introduction . . . . . . . . . . . . . . . . 5-3 Channel . . . . . . . . . . . . . . . . . 6-41
BSS 0 alarm BSS 41 alarm, Circuit Fault Detected On Ater
last MTL link failure - signalling point Channel
inaccessible . . . . . . . . . . . . . . . . 6-4 BSS: Circuit Fault Detected On Ater
BSS 0 alarm, Last MTL Link Failure - Signalling Channel . . . . . . . . . . . . . . . . . 6-43
Point Inaccessible BSS 42 alarm, Circuit Fault Cleared On Ater
BSS: Last MTL Link Failure - Signalling Point Channel
Inaccessible . . . . . . . . . . . . . . . . 6-4 BSS: Circuit Fault Cleared On Ater
BSS 0, PM alarm Channel . . . . . . . . . . . . . . . . . 6-45
paging BSS 0, PM alarm . . . . . . . . . 6-7 BSS 44 alarm, Circuit Fault Cleared on PCM
BSS 1 alarm Circuit
call processing failure - MSC detected SCCP BSS: Circuit Fault Cleared on PCM
down . . . . . . . . . . . . . . . . . . . 6-8 Circuit . . . . . . . . . . . . . . . . . 6-49
BSS 1, PM alarm BSS 45 alarm, Circuit Fault Detected on GPRS
routing failure - syntax error detected Circuit
routing failure - syntax error detected . . 6-9 BSS: Circuit Fault Detected on GPRS
BSS 10 alarm Circuit . . . . . . . . . . . . . . . . . 6-51
erroneous Layer 3 message received by the BSS 46 alarm, Circuit Fault Cleared on GPRS
BSS . . . . . . . . . . . . . . . . . . . 6-26 Circuit
BSS 11 alarm BSS: Circuit Fault Cleared on GPRS
confusion message received from the Circuit . . . . . . . . . . . . . . . . . 6-53
MSC . . . . . . . . . . . . . . . . . . 6-27 BSS 46 alarm, Circuit Fault Detected On PATH
BSS 12 alarm Channel
unequipped circuit at the BSS . . . . . 6-28 BSS: Circuit Fault Detected On PATH
BSS 17, PM alarm Channel . . . . . . . . . . . . . . . . . 6-55
HO request from the MSC protocol BSS 48 alarm, Circuit Fault Cleared on PATH
error . . . . . . . . . . . . . . . . . . 6-30 Channel . . . . . . . . . . . . . . . . . . 6-57
BSS 18, PM alarm BSS 49 alarm
routing failure - syntax error detected last LMTL link failure - signalling point
routing failure - syntax error de inaccessible . . . . . . . . . . . . . . . 6-59
tected . . . . . . . . . . . . . . . . . 6-31 BSS 49 alarm, Last LMTL Link Failure - Signalling
BSS 2 alarm Point Inaccessible
call processing failure - MSC detected BSSAP BSS: Last LMTL Link Failure - Signalling Point
down . . . . . . . . . . . . . . . . . . 6-10 Inaccessible . . . . . . . . . . . . . . . 6-59
BSS 2, PM alarm BSS 5 alarm
routing failure - reason unknown . . . . 6-12 no MSC BSS 5 alarm . . . . . . . . . . 6-15
BSS 20, PM alarm BSS 5 alarm, No MSC Acknowledgement for
paging BSS 20, PM alarm . . . . . . . . 6-32 Circuit Block
BSS 21 alarm BSS: No MSC Acknowledgement for Circuit
trunk major threshold exceeded . . . . 6-33 Block . . . . . . . . . . . . . . . . . . 6-15
BSS 22 alarm BSS 50 alarm
trunk critical threshold exceeded . . . . 6-34 call processing failure - SMLC detected SCCP
BSS 24 alarm down . . . . . . . . . . . . . . . . . . 6-62
Agent Buffer Overflow - Rlogin Ses BSS 51 alarm
sion . . . . . . . . . . . . . . . . . . . 6-36 call processing failure - SMLC detected BSSAP
BSS 26 alarm down . . . . . . . . . . . . . . . . . . 6-64
received page for invalid cell from BSS 52 alarm
MSC . . . . . . . . . . . . . . . . . . 6-38 no SMLC acknowlegement for global
BSS 3 alarm reset . . . . . . . . . . . . . . . . . . 6-66
call processing failure - BSS detected BSSAP BSS 53 alarm
down . . . . . . . . . . . . . . . . . . 6-13 erroneous Layer 3 message received by the
BSS 39 alarm, Circuit Fault Detected on Radio SMLC . . . . . . . . . . . . . . . . . . 6-67
Channel . . . . . . . . . . . . . . . . . . 6-39 BSS 54 alarm
68P02901W26-S IX-21
Nov 2007
Index
BSS 54 alarm (contd.) BTP 235 alarm (contd.)

confusion message received from the standby link connection failure . . . . . 7-44
SMLC . . . . . . . . . . . . . . . . . . 6-68 BTP 236 alarm
BSS 55 alarm slow flash failure . . . . . . . . . . . . 7-47
received page for invalid cell from BTP 237 alarm
SMLC . . . . . . . . . . . . . . . . . . 6-69 non-volatile memory failure . . . . . . . 7-49
BSS 6 alarm BTP 239 alarm
no MSC acknowledgement for circuit process safe test audit failure . . . . . . 7-51
unblock . . . . . . . . . . . . . . . . . 6-17 BTP 254 alarm
BSS 7 alarm device failure . . . . . . . . . . . . . . 7-53
no MSC acknowledgement for reset BTP 30 alarm
circuit . . . . . . . . . . . . . . . . . . 6-19 clock A signal loss. . . . . . . . . . . . 7-14
BSS 7, PM alarm BTP 31 alarm
mobile assignment request from MSC protocol clock B signal loss. . . . . . . . . . . . 7-17
error . . . . . . . . . . . . . . . . . . 6-21 BTP 32 alarm
BSS 8 alarm TDM interface failure - assigned timeslot
unequipped circuit at the MSC . . . . . 6-23 counter underflow . . . . . . . . . . . 7-20
BSS 9 alarm BTP 33 alarm
no MSC acknowledgement for global TDM interface failure - assigned timeslot
reset . . . . . . . . . . . . . . . . . . 6-25 counter overflow . . . . . . . . . . . . 7-22
BSS alarms BTP 34 alarm
introduction . . . . . . . . . . . . . . . . 6-3 TDM interface failure - TDM parity
MSC to BSS Layer 3 . . . . . . . . . . . 6-3 error . . . . . . . . . . . . . . . . . . 7-24
BSSGP status message received from the BTP 35 alarm
SGSN . . . . . . . . . . . . . . . . . . . 42-80 LAN connection failure . . . . . . . . . 7-26
BTP 1 alarm BTP 39 alarm
EEPROM flash failure - no valid bootstrap code software failure . . . . . . . . . . . . . 7-28
object present. . . . . . . . . . . . . . . 7-4 BTP 40 alarm
BTP 17 alarm spurious interrupt. . . . . . . . . . . . 7-30
EEPROM flash programming failure . . . 7-8 BTP 42 alarm
BTP 20 alarm site reset occurred due to front panel
LAPD controller failure . . . . . . . . . 7-10 reset . . . . . . . . . . . . . . . . . . 7-32
EEPROM flash programming failure . . 7-11 Unexpected board type . . . . . . . . . 7-33
SWFM indication . . . . . . . . . . . . 7-13 Memory location is corrupt . . . . . . . 7-35
TDM interface configuration failure. . . 7-38 EEPROM flash object failure . . . . . . . 7-6
BTP 232 alarm BTP alarms
processor bus communication failure . . 7-40 FRUs . . . . . . . . . . . . . . . . . . . 7-3
BTP 234 alarm introduction . . . . . . . . . . . . . . . . 7-3
active link connection failure . . . . . . 7-41 BTS cabinet overtemperature
BTP 235 alarm IAS 82 alarm . . . . . . . . . . . . . . 25-85
CAB 25 alarm CAB 28 alarm (contd.)

external power booster amplifier 1 database configuration and hardware
failure . . . . . . . . . . . . . . . . . . . 8-3 mismatch . . . . . . . . . . . . . . . . . 8-9
CAB 26 alarm CAB alarms
external power booster amplifier 2 FRUs . . . . . . . . . . . . . . . . . . . 8-2
failure . . . . . . . . . . . . . . . . . . . 8-5 introduction . . . . . . . . . . . . . . . . 8-2
CAB 27 alarm cabinet fan failure
external power booster failure . . . . . . 8-7 IAS 86 alarm . . . . . . . . . . . . . . 25-93
CAB 28 alarm cabinet protection board fuse failure
IX-22 68P02901W26-S
Nov 2007
Index
cabinet protection board fuse failure (contd.) CAGE alarm 6

IAS 111 alarm. . . . . . . . . . . . . 25-137 remote KSWX slot 4 communication
Cabinet protection system failure failure . . . . . . . . . . . . . . . . 9-22, 9-34
IAS 100 alarm. . . . . . . . . . . . . 25-117 CAGE alarm 7
CAGE 20 alarm remote KSWX slot 5 communication
CLKX slot 2 communication failure . . . . 9-3 failure . . . . . . . . . . . . . . . . 9-22, 9-34
CAGE 21 alarm CAGE alarm 8
CLKX slot 3 communication failure . . . . 9-3 remote KSWX slot 6 communication
CAGE 22 alarm failure . . . . . . . . . . . . . . . . 9-22, 9-34
CLKX slot 4 communication failure . . . . 9-3 CAGE alarms
CAGE 23 alarm introduction . . . . . . . . . . . . . . . . 9-2
CLKX slot 5 communication failure . . . . 9-3 calibration in progress
CAGE 24 alarm GCLK 21 alarm . . . . . . . . . . . . . 21-44
CLKX slot 6 communication failure . . . . 9-3 Calibration in progress
CAGE 25 alarm DRI 21 alarm . . . . . . . . . . . . . . 17-42
CLKX slot 7 communication failure . . . . 9-3 call processing failure - BSS detected BSSAP
CAGE 26 alarm down
LANX slot 19 communication failure . . . 9-6 BSS 3 alarm. . . . . . . . . . . . . . . 6-13
CAGE 27 alarm call processing failure - MSC detected BSSAP
LANX slot 20 communication failure . . . 9-6 down
CAGE 28 alarm BSS 2 alarm. . . . . . . . . . . . . . . 6-10
power supply unit#1 output failure . . . . 9-9 call processing failure - MSC detected SCCP down
CAGE 29 alarm BSS 1 alarm. . . . . . . . . . . . . . . . 6-8
power supply unit#2 output failure . . . . 9-9 call processing failure - SMLC detected BSSAP
CAGE 30 alarm down
power supply unit#3 output failure . . . . 9-9 BSS 51 alarm . . . . . . . . . . . . . . 6-64
CAGE 31 alarm call processing failure - SMLC detected SCCP
power supply unit#1 not detected . . . 9-11 down
CAGE 32 alarm BSS 50 alarm . . . . . . . . . . . . . . 6-62
power supply unit#2 not detected . . . 9-11 cavity 0 tuning error
CAGE 33 alarm COMB 0 alarm . . . . . . . . . . . . . 13-3
power supply unit#3 not detected . . . 9-11 cavity 1 tuning error
power supply unit#1 fan failure. . . . . 9-13 cavity 2 tuning error
power supply unit#1 over-tempera cavity 5 tuning error
ture . . . . . . . . . . . . . . . . . . . 9-15 COMB 11 alarm . . . . . . . . . . . . . 13-20
CAGE 38 alarm cavity combining block 0 failure
power supply unit#2 over-tempera COMB 12 alarm . . . . . . . . . . . . . 13-23
ture . . . . . . . . . . . . . . . . . . . 9-15 cavity combining block 1 failure
power supply unit#3 over-tempera CBL 0, PM alarm
ture . . . . . . . . . . . . . . . . . . . 9-15 invalid received frames . . . . . . . . . 10-3
CAGE 40 alarm CBL 1, PM alarm
over-temperature - component damage FRMR-frames . . . . . . . . . . . . . . 10-5
imminent . . . . . . . . . . . . . . . . 9-17 CBL 2, PM alarm
CAGE alarm 42 expiration of N2. . . . . . . . . . . . . 10-7
local KSWX slot 0 communication CBL alarms
failure . . . . . . . . . . . . . . . . . . 9-19 introduction . . . . . . . . . . . . . . . 10-2
local KSWX slot 1 communication CBUS 0 alarm
failure . . . . . . . . . . . . . . . . . . 9-19 over 50% of board detected clock
CAGE alarm 5 failure . . . . . . . . . . . . . . . . . . 11-3
remote KSWX slot 3 communication
failure . . . . . . . . . . . . . . . . 9-22, 9-34
68P02901W26-S IX-23
Nov 2007
Index
CBUS 2 alarm CELL 23, PM alarm

master CBUS signal provided by slave mobile assignment failure from MS . . . 12-55
GCLK . . . . . . . . . . . . . . . . . . 11-5 CELL 24, PM alarm
CBUS 4 alarm PCH queue page discard . . . . . . . . 12-57
local KSWX clock fibre failure. . . . . . 11-7 CELL 25, PM alarm
CBUS alarms attempt at allocating a TCH failed . . . 12-59
introduction . . . . . . . . . . . . . . . 11-2 CELL 28, PM alarm
CCDSP alarms TCH pre-emption failure alarm . . . . . 12-61
introduction . . . . . . . . . . . . . . . 17-7 CELL 4, PM alarm
CEL 3 alarm, Last NS-VC Failed classmark update from MS protocol
CELL: Last NS-VC Failed . . . . . . . . 12-15 error . . . . . . . . . . . . . . . . . . 12-17
CELL 0, PM alarm CELL 5 alarm
radio frequency losses while using an no cell (BVC) block acknowledgement from the
SDCCH . . . . . . . . . . . . . . . . . 12-6 SGSN . . . . . . . . . . . . . . . . . . 12-19
CELL 1 alarm CELL 6, PM alarm
cell radio timeslot capacity loss . . . . . 12-8 cipher mode cmd from MSC failed . . . 12-20
CELL 1, PM alarm CELL 7 alarm
attempt at allocating an SDCCH failed. . 12-9 GPRS and baseband hopping configuration
CELL 10, PM alarm failure . . . . . . . . . . . . . . . . . . 12-21
intra-cell handover failed & mobile CELL 9 alarm, GPRS unavailable - No GDS
lost . . . . . . . . . . . . . . . . . . . 12-28 available . . . . . . . . . . . . . . . . . 12-24
CELL 11 alarm, GPRS unavailable - No Cell (BVC) CELL 9, PM alarm
Unblock Ack from the SGSN . . . . . . . 12-30 intra-cell handover failed & recovered to org
CELL 11, PM alarm channel . . . . . . . . . . . . . . . . . 12-25
intra-BSS HO primary target cell CELL alarms
blocked . . . . . . . . . . . . . . . . . 12-31 introduction . . . . . . . . . . . . . . . 12-3
CELL 12 alarm cell radio timeslot capacity loss
GPRS unavailable - No PDCHs avail CELL 1 alarm . . . . . . . . . . . . . . 12-8
able . . . . . . . . . . . . . . . . . . . 12-32 cell transmit power unachievable
CELL 12 alarm, GPRS unavailable - No PDCHs DRI 74 alarm . . . . . . . . . . . . . 17-129
Available . . . . . . . . . . . . . . . . . 12-32 channel coder 0 failure - demodulation processor
CELL 13 alarm 1 failure
GPRS unavailable - No GPRS capable carriers DRI 54 alarm . . . . . . . . . . . . . . 17-91
available . . . . . . . . . . . . . . . . 12-33 channel coder 1 failure - demodulation processor
CELL 13, PM alarm 0 failure
intra-BSS HO failed and recovered to org DRI 55 alarm . . . . . . . . . . . . . . 17-93
channel . . . . . . . . . . . . . . . . . 12-34 channel coder 1 failure - demodulation processor
CELL 14, PM alarm 1 failure
GPRS unavailable - PBCCH timeslot out of DRI 56 alarm . . . . . . . . . . . . . . 17-95
sync . . . . . . . . . . . . . . . . . . . 12-38 channel coder failure
intra-BSS HO failed and mobile lost. . . 12-36 DRI 212 alarm . . . . . . . . . . . . 17-276
CELL 15, PM alarm channel coder internal message error
inter-BSS HO, MS HO failed message DRI 13 alarm . . . . . . . . . . . . . . 17-26
received. . . . . . . . . . . . . . . . . 12-40 DRI 14 alarm . . . . . . . . . . . . . . 17-28
CELL 17 alarm DRI 16 alarm . . . . . . . . . . . . . . 17-32
EGPRS Unavailable - Insufficient GDS DRI 17 alarm . . . . . . . . . . . . . . 17-34
Available . . . . . . . . . . . . . . . . 12-42 DRI 19 alarm . . . . . . . . . . . . . . 17-38
CELL 19 alarm DRI 20 alarm . . . . . . . . . . . . . . 17-40
EGPRS unavailable - No 64K PDCHs DRI 9 alarm . . . . . . . . . . . . . . . 17-21
available . . . . . . . . . . . . . . . . 12-48 channel coder timeslot 0 failure
CELL 19, PM alarm DRI 40 alarm . . . . . . . . . . . . . . 17-76
bad HO reference numbers from the channel coder timeslot 1 failure
MS . . . . . . . . . . . . . . . . . . . 12-49 DRI 41 alarm . . . . . . . . . . . . . . 17-76
CELL 2, PM alarm channel coder timeslot 2 failure
channel request from MS blocked. . . . 12-13 DRI 42 alarm . . . . . . . . . . . . . . 17-76
CELL 20, PM alarm channel coder timeslot 3 failure
number of calls queued . . . . . . . . . 12-51 DRI 43 alarm . . . . . . . . . . . . . . 17-76
IX-24 68P02901W26-S
Nov 2007
Index
channel coder timeslot 4 failure COMB 1 alarm

DRI 44 alarm . . . . . . . . . . . . . . 17-76 cavity 1 tuning error . . . . . . . . . . 13-3
DRI 45 alarm . . . . . . . . . . . . . . 17-76 partial reset . . . . . . . . . . . . . . . 13-17
DRI 46 alarm . . . . . . . . . . . . . . 17-76 cavity 5 tuning error . . . . . . . . . . 13-20
DRI 47 alarm . . . . . . . . . . . . . . 17-76 cavity combining block 0 failure . . . . 13-23
channel request from MS blocked COMB 13 alarm
CELL 2, PM alarm . . . . . . . . . . . 12-13 cavity combining block 1 failure . . . . 13-25
channel request from MS failed COMB 14 alarm
TIMESLOT 1, PM alarm. . . . . . . . . 45-4 processor A failure . . . . . . . . . . . 13-27
cipher mode cmd from MSC failed COMB 15 alarm
CELL 6, PM alarm . . . . . . . . . . . 12-20 processor B failure . . . . . . . . . . . 13-29
classmark update from MS protocol error COMB 2 alarm
CELL 4, PM alarm . . . . . . . . . . . 12-17 cavity 2 tuning error . . . . . . . . . . 13-3
clearing types . . . . . . . . . . . . . . . 1-12 COMB 254 alarm
FMIC . . . . . . . . . . . . . . . . . . 1-12 device failure . . . . . . . . . . . . . . 13-31
Intermittent . . . . . . . . . . . . . . . 1-12 COMB 3 alarm
OIC . . . . . . . . . . . . . . . . . . . 1-12 cavity 3 tuning error . . . . . . . . . . 13-3
CLKX slot 2 communication failure COMB 4 alarm
CAGE 20 alarm . . . . . . . . . . . . . . 9-3 cavity 4 tuning error . . . . . . . . . . 13-3
CAGE 21 alarm . . . . . . . . . . . . . . 9-3 link A sanity failure . . . . . . . . . . . 13-6
CAGE 22 alarm . . . . . . . . . . . . . . 9-3 link B sanity failure . . . . . . . . . . . 13-8
CAGE 23 alarm . . . . . . . . . . . . . . 9-3 power feed A failure . . . . . . . . . . 13-10
CAGE 24 alarm . . . . . . . . . . . . . . 9-3 power feed B failure . . . . . . . . . . 13-12
CAGE 25 alarm . . . . . . . . . . . . . . 9-3 full reset . . . . . . . . . . . . . . . . 13-14
clock A signal loss COMB alarms
BSP 30 alarm . . . . . . . . . . . . . . 5-14 FRUs . . . . . . . . . . . . . . . . . . 13-2
BTP 30 alarm . . . . . . . . . . . . . . 7-14 introduction . . . . . . . . . . . . . . . 13-2
DHP 30 alarm . . . . . . . . . . . . . . 15-27 combiner alarms
GPROC 30 alarm . . . . . . . . . . . . 23-22 introduction . . . . . . . . . . . . . . . 13-2
MSI 4 alarm. . . . . . . . . . . . . . . 30-11 confusion message received from the MSC
Clock A Signal Loss BSS 11 alarm . . . . . . . . . . . . . . 6-27
DRI 27 alarm . . . . . . . . . . . . . . 17-53 confusion message received from the SMLC
clock B signal loss. . . . . . . . . . . . . 26-19 confusion message received from the
BSP 31 alarm . . . . . . . . . . . . . . 5-17 MSC . . . . . . . . . . . . . . . . . . 6-68
BTP 31 alarm . . . . . . . . . . . . . . 7-17 connectivity mismatch between BSC and RXCDR
DHP 31 alarm . . . . . . . . . . . . . . 15-29 MMS 41 alarm . . . . . . . . . . . . . 29-91
DRI 28 alarm . . . . . . . . . . . . . . 17-55 control processor configuration mismatch
GPROC 31 alarm . . . . . . . . . . . . 23-24 DRI 167 alarm . . . . . . . . . . . . 17-247
KSW 5 alarm . . . . . . . . . . . . . . 26-19 control processor firmware failure
MSI 3 alarm. . . . . . . . . . . . . . . 30-9 DRI 166 alarm . . . . . . . . . . . . 17-245
clock output failure control processor message queue overflowed
GCLK 16 alarm . . . . . . . . . . . . . 21-34 DRI 156 alarm . . . . . . . . . . . . 17-225
clock reference failure control processor to equalizer communication
GCLK 2 alarm . . . . . . . . . . . . . . 21-5 failure
code objects unavailable DRI 153 alarm . . . . . . . . . . . . 17-219
CSFP 47 alarm . . . . . . . . . . . . . 14-6 control processor to power amplifier
CSFP 49 alarm . . . . . . . . . . . . . 14-9 communication failure
COMB 0 alarm DRI 152 alarm . . . . . . . . . . . . 17-217
cavity 0 tuning error . . . . . . . . . . 13-3 converter failure
68P02901W26-S IX-25
Nov 2007
Index
converter failure (contd.) CSFP 47 alarm

IAS 46 alarm . . . . . . . . . . . . . . 25-54 code objects unavailable . . . . . . . . 14-6
converter overtemperature CSFP 48 alarm
IAS 47 alarm . . . . . . . . . . . . . . 25-56 Memory location is corrupt . . . . . . . 14-8
corrupt NE file CSFP 49 alarm
OMC 30051 alarm . . . . . . . . . . . 32-96 code objects unavailable . . . . . . . . 14-9
corrupt SITE file CSFP 50 alarm
OMC 30052 alarm . . . . . . . . . . . 32-97 EEPROM SW flash programming fail
CPU load exceeds lower limit ure . . . . . . . . . . . . . . . . . . . 14-11
OMC 30061 alarm . . . . . . . . . . 32-102 CSFP 51 alarm
critical alarm threshold exceeded EEPROM SW flash programming fail
MMS 253 alarm . . . . . . . . . . . . . 29-94 ure . . . . . . . . . . . . . . . . . . . 14-12
crtical resource exhausted CSFP alarms
DRI 31 alarm . . . . . . . . . . . . . . 17-61 FRUs . . . . . . . . . . . . . . . . . . 14-2
CSFP 22 alarm introduction . . . . . . . . . . . . . . . 14-2
SWFM indication . . . . . . . . . . . . 14-3 CSFPdownloadFailed
CSFP 240 alarm OMC 30017 alarm . . . . . . . . . . . 32-44
PCMCIA card removed . . . . . . . . . 14-13 CSFPSwapFailed
CSFP 35 alarm OMC 30024 alarm . . . . . . . . . . . 32-63
LAN connection failure . . . . . . . . . 14-4 Customer defined alarms . . . . . . . . . 18-2
database configuration and Arena hardware DHP 1 alarm

mismatch EEPROM flash failure - no valid bootstrap code
SITE 28 alarm. . . . . . . . . . 42-70, 42-73 object present. . . . . . . . . . . . . . 15-4
database configuration and hardware mismatch DHP 17 alarm
CAB 28 alarm . . . . . . . . . . . . . . . 8-9 EEPROM flash programming failure . . 15-8
database exceeds lower limit DHP 21 alarm, EEPROM Flash Programming
OMC 30019 alarm . . . . . . . . . . . 32-49 Failure
database exceeds upper limit DHP 21 alarm, EEPROM Flash Programming
OMC 30014 alarm . . . . . . . . . . . 32-40 Failure . . . . . . . . . . . . . . . . . 15-10
Database unable to allocate fragment DHP 22 alarm
OMC 30066 alarm . . . . . . . . . . 32-108 SWFM indication . . . . . . . . . . . . 15-12
dbCompressionFailed DHP 22 alarm, SWFM Indication . . . . . 15-12
OMC 30009 alarm . . . . . . . . . . . 32-31 DHP 23 alarm
dbUncompressionFailed SYNC lost phase lock to master
OMC 30018 alarm . . . . . . . . . . . 32-47 GCLK . . . . . . . . . . . . . . . . . . 15-13
Demodulation processor 0 failure DHP 231 alarm
DRI 53 alarm . . . . . . . . . . . . . . 17-89 TDM interface configuration failure. . . 15-55
device alarm DHP 232 alarm
information . . . . . . . . . . . . . . . . 1-8 processor bus communication fail
device alarm information . . . . . . . . . . 1-8 ure . . . . . . . . . . . . . . . . . . . 15-57
device failure DHP 234 alarm
BSP 254 alarm . . . . . . . . . . . . . 5-46 active link connection failure . . . . . . 15-58
BTP 254 alarm . . . . . . . . . . . . . 7-53 DHP 239 alarm
COMB 254 alarm . . . . . . . . . . . . 13-31 process safe test audit failure . . . . . . 15-61
DHP 254 alarm . . . . . . . . . . . . . 15-63 DHP 24 alarm
DRI 254 alarm . . . . . . . . . . . . 17-315 bad clock source or SYNC OCXO (oscillator)
GPROC 254 alarm. . . . . . . . . . . . 23-53 replacement. . . . . . . . . . . . . . . 15-15
KSW 254 alarm . . . . . . . . . . . . . 26-63 DHP 25 alarm
MSI 254 alarm . . . . . . . . . . . . . 30-32 SYNC warmup failure . . . . . . . . . . 15-17
PBUS 254 alarm . . . . . . . . . . . . 34-3 DHP 254 alarm
SBUS 254 alarm . . . . . . . . . . . . 41-3 device failure . . . . . . . . . . . . . . 15-63
DHP 26 alarm
IX-26 68P02901W26-S
Nov 2007
Index
DHP 26 alarm (contd.) downloadDisabled (contd.)

SYNC calibration request . . . . . . . . 15-19 OMC 30023 alarm . . . . . . . . . . . 32-61
DHP 27 alarm downloadFailed
SYNC shutdown request . . . . . . . . 15-21 OMC 30000 alarm . . . . . . . . . . . 32-5
DHP 28 alarm DPROC 0 alarm
SYNC clock output failure. . . . . . . . 15-23 processor communication failure . . . . 16-3
SYNC watchdog timer expired . . . . . 15-25 SWFM indication . . . . . . . . . . . . 16-7
clock A signal loss. . . . . . . . . . . . 15-27 process safe test audit failure . . . . . . 16-11
clock B signal loss. . . . . . . . . . . . 15-29 software failure . . . . . . . . . . . . . 16-8
TDM interface failure - assigned timeslot DPROC reset detected . . . . . . . . . 16-5
counter underflow . . . . . . . . . . . 15-31 DPROC alarms
DHP 33 alarm FRUs . . . . . . . . . . . . . . . . . . 16-2
TDM interface failure - assigned timeslot introduction . . . . . . . . . . . . . . . 16-2
counter overflow . . . . . . . . . . . . 15-33 DPROC reset detected
DHP 34 alarm DPROC 9 alarm . . . . . . . . . . . . . 16-5
TDM interface failure - TDM parity DPSM 0 failure
error . . . . . . . . . . . . . . . . . . 15-35 IAS 63 alarm . . . . . . . . . . . . . . 25-71
DHP 35 alarm DPSM 1 failure
LAN connection failure . . . . . . . . . 15-37 IAS 62 alarm . . . . . . . . . . . . . . 25-69
DHP 39 alarm DPSM, power supply module
software failure . . . . . . . . . . . . . 15-39 BCUP alarms . . . . . . . . . . . . . . . 4-2
DHP 40 alarm DRAM battery backup fuse failure
spurious interrupt. . . . . . . . . . . . 15-41 IAS 31 alarm . . . . . . . . . . . . . . 25-42
DHP 43 alarm DRI 10 alarm
SYNC not operational . . . . . . . . . . 15-43 dual-port RAM error . . . . . . . . . . 17-24
Firmware initiated SYNC calibration . . 15-45 receiver synthesizer failure . . . . . . 17-168
SYNC phase lock failure . . . . . . . . 15-46 receiver synthesizer failure . . . . . . 17-170
SYNC invalid mode . . . . . . . . . . . 15-48 receiver synthesizer failure . . . . . . 17-172
Unexpected board type . . . . . . . . . 15-50 receiver synthesizer failure . . . . . . 17-174
Memory location is corrupt. Replace GPROC receiver synthesizer failure . . . . . . 17-176
board . . . . . . . . . . . . . . . . . . 15-52 DRI 117 alarm
DHP 50 alarm receiver synthesizer failure . . . . . . 17-178
EEPROM SW flash programming fail DRI 118 alarm
ure . . . . . . . . . . . . . . . . . . . 15-53 receiver synthesizer failure . . . . . . 17-180
EEPROM SW flash programming fail receiver failure . . . . . . . . . . . . 17-182
ure . . . . . . . . . . . . . . . . . . . 15-54 DRI 120 alarm
DHP 8 alarm receiver failure . . . . . . . . . . . . 17-184
EEPROM flash object failure . . . . . . 15-6 DRI 121 alarm
DHP alarms receiver failure . . . . . . . . . . . . 17-186
FRUs . . . . . . . . . . . . . . . . . . 15-3 DRI 122 alarm
introduction . . . . . . . . . . . . . . . 15-3 receiver failure . . . . . . . . . . . . 17-188
display modes DRI 123 alarm
maps . . . . . . . . . . . . . . . . . . 1-19 receiver failure . . . . . . . . . . . . 17-190
door open DRI 124 alarm
IAS 93 alarm . . . . . . . . . . . . . 25-103 receiver failure . . . . . . . . . . . . 17-192
TRU 0 alarm . . . . . . . . . . . . . . 46-3 DRI 125 alarm
downloadDisabled receiver failure . . . . . . . . . . . . 17-194
68P02901W26-S IX-27
Nov 2007
Index
DRI 126 alarm DRI 215 alarm

receiver failure . . . . . . . . . . . . 17-196 power amplifier failure . . . . . . . . 17-282
receiver failure . . . . . . . . . . . . 17-198 transceiver recovery failure . . . . . . 17-284
receiver failure . . . . . . . . . . . . 17-200 transmission suspended to conserve battery
DRI 13 alarm power . . . . . . . . . . . . . . . . . 17-286
channel coder internal message er DRI 218 alarm
ror . . . . . . . . . . . . . . . . . . . 17-26 invalid transceiver calibration data . . 17-288
channel coder internal message er GPRS not supported by radio . . . . . 17-290
ror . . . . . . . . . . . . . . . . . . . 17-28 DRI 22 alarm
DRI 15 alarm radio subsystem software to DRI communication
initial synchronization of radio and GPRS failure . . . . . . . . . . . . . . . . . . 17-43
channel failed . . . . . . . . . . . . . . 17-30 DRI 221 alarm
DRI 16 alarm Invalid in-call modification of destination
channel coder internal message er channel type . . . . . . . . . . . . . 17-291
ror . . . . . . . . . . . . . . . . . . . 17-32 DRI 224 alarm
DRI 17 alarm safe test audit failure . . . . . . . . . 17-293
ror . . . . . . . . . . . . . . . . . . . 17-34 radio subsystem software to DRI communication
DRI 176 alarm . . . . . . . . . . . . . 17-257 failure . . . . . . . . . . . . . . . . . . 17-45
primary message or hardware interrupt TDM interface configuration failure . . 17-296
error . . . . . . . . . . . . . . . . . . 17-36 DRI 234 alarm
DRI 184 alarm active link connection failure . . . . . 17-298
equalizer firmware failure . . . . . . 17-259 DRI 235 alarm
DRI 19 alarm standby link connection failure . . . . 17-301
ror . . . . . . . . . . . . . . . . . . . 17-38 slow flash failure . . . . . . . . . . . 17-303
baseband hopping TDM link error . . 17-261 non-volatile memory failure . . . . . . 17-305
baseband hopping GSM timeslot misalign process safe test audit failure . . . . . 17-307
ment . . . . . . . . . . . . . . . . . 17-263 DRI 24 alarm
DRI 2 alarm TDM interface failure - TDM parity
internal message error - pointer misalign error . . . . . . . . . . . . . . . . . . 17-47
ment . . . . . . . . . . . . . . . . . . 17-10 DRI 241 alarm
DRI 20 alarm standby link connected to wrong de
channel coder internal message er vice . . . . . . . . . . . . . . . . . . 17-310
ror . . . . . . . . . . . . . . . . . . . 17-40 DRI 243 alarm
DRI 208 alarm unlocked device not in service . . . . 17-313
power amplifier temperature . . . . . 17-270 DRI 25 alarm
DRI 21 alarm TDM interface failure - assigned timeslot
Calibration in progress . . . . . . . . . 17-42 counter overflow . . . . . . . . . . . . 17-49
DRI 21 ALARM, Calibration in DRI 254 alarm
progress . . . . . . . . . . . . . . . . . 17-42 device failure . . . . . . . . . . . . . 17-315
hopping DRI failure . . . . . . . . . . 17-272 TDM interface failure - assigned timeslot
DRI 211 alarm counter underflow . . . . . . . . . . . 17-51
front end processor failure . . . . . . 17-274 DRI 27 alarm, Clock A Signal Loss . . . . 17-53
channel coder failure . . . . . . . . . 17-276 clock B signal loss. . . . . . . . . . . . 17-55
transceiver processor failure . . . . . 17-278 processor failure . . . . . . . . . . . . 17-57
DRI 214 DRI 3 alarm
equalizer failure . . . . . . . . . . . 17-280
IX-28 68P02901W26-S
Nov 2007
Index
DRI 3 alarm (contd.) DRI 58 alarm

internal message error - dual-port RAM DRI 58 . . . . . . . . . . . . . . . . . 17-99
segment full. . . . . . . . . . . . . . . 17-13 DRI 59 alarm
DRI 30 alarm transceiver to DRI burst error . . . . 17-101
transceiver re-initialized unexpect DRI 6 alarm
edly . . . . . . . . . . . . . . . . . . . 17-59 superframe counter error . . . . . . . . 17-18
critical resource exhausted . . . . . . . 17-61 transceiver to DRI burst error . . . . 17-103
reset due to recurring fault . . . . . . . 17-67 transceiver to DRI communication
DRI 37 alarm error . . . . . . . . . . . . . . . . . 17-105
hard reset . . . . . . . . . . . . . . . . 17-70 DRI 62 alarm
DRI 39 alarm transceiver to DRI communication
synchronization loss with MCU . . . . . 17-73 error . . . . . . . . . . . . . . . . . 17-107
channel coder timeslot 0 failure. . . . . 17-76 transceiver to DRI communication
DRI 41 alarm error . . . . . . . . . . . . . . . . . 17-109
channel coder timeslot 1 failure. . . . . 17-76 DRI 64 alarm
DRI 42 alarm unrecoverable error. . . . . . . . . . 17-111
DRI 43 alarm radio subsystem software to DRI communication
channel coder timeslot 3 failure. . . . . 17-76 error - checksum error . . . . . . . . 17-113
channel coder timeslot 4 failure. . . . . 17-76 superframe counter error . . . . . . . 17-116
channel coder timeslot 5 failure. . . . . 17-76 radio subsystem software to DRI communication
DRI 46 alarm error - DRI not responding . . . . . . 17-119
DRI 47 alarm equalizer control processor failure - watchdog
channel coder timeslot 7 failure. . . . . 17-76 timer expired . . . . . . . . . . . . . 17-121
baseband hopping timeslot counter unexpected communications bus inter
mismatch . . . . . . . . . . . . . . . . 17-78 rupt . . . . . . . . . . . . . . . . . . 17-123
GSM timeslot counter mismatch . . . . 17-80 receiver failure . . . . . . . . . . . . 17-125
super frame counter error . . . . . . . 17-16 power amplifier error . . . . . . . . . 17-127
spurious GSM timeslot interrupt . . . . 17-82 cell transmit power unachievable . . . 17-129
baseband hopping TDM link error . . . 17-84 radio subsystem software to DRI communication
DRI 52 alarm error . . . . . . . . . . . . . . . . . 17-132
baseband hopping GSM timeslot misalign DRI 78 alarm
ment . . . . . . . . . . . . . . . . . . 17-86 TX VSWR antenna fault . . . . . . . . 17-134
Demodulation processor 0 failure . . . . 17-89 transceiver synthesizer failure . . . . 17-135
channel coder 0 failure - demodulation transmitter synthesizer failure . . . . 17-138
processor 1 failure . . . . . . . . . . . 17-91 DRI 82 alarm
DRI 55 alarm transmitter synthesizer failure . . . . 17-141
channel coder 1 failure - demodulation DRI 83 alarm
processor 0 failure . . . . . . . . . . . 17-93 transmitter synthesizer failure . . . . 17-143
channel coder 1 failure - demodulation transmitter synthesizer failure . . . . 17-145
processor 1 failure . . . . . . . . . . . 17-95 DRI 85 alarm
DRI 57 alarm
transceiver to DRI communication
failure . . . . . . . . . . . . . . . . . . 17-97
68P02901W26-S IX-29
Nov 2007
Index
DRI 85 alarm (contd.) DRI 92 alarm

transmitter failure - output power. . . 17-147 power amplifier DRI 92 alarm. . . . . 17-162
DRI 86 alarm DRI 92 alarm, Power Amplifier Temperature High
transmitter failure - output power. . . 17-149 But Functioning . . . . . . . . . . . . . 17-162
transmitter failure - output power. . . 17-151 transmitter failure - output power. . . 17-164
DRI 88 alarm DRI alarms
power amplifier temperature high . . 17-153 FRUs . . . . . . . . . . . . . . . . . . 17-8
DRI 89 alarm introduction . . . . . . . . . . . . . . . 17-7
power amplifier communication fail DRI firmware . . . . . . . . . . . . . . . 17-42
ure . . . . . . . . . . . . . . . . . . 17-156 DSP channel audit failures
DRI 9 alarm MSI 11 - 40 alarms . . . . . . . . . . . 30-21
channel coder internal message er dual-port RAM error
ror . . . . . . . . . . . . . . . . . . . 17-21 DRI 10 alarm . . . . . . . . . . . . . . 17-24
DRI 90 alarm duplexer voltage error
transmitter failure - output power. . . 17-158 IAS 51 alarm . . . . . . . . . . . . . . 25-61
DRI 91 alarm
power amplifier power low but function
ing . . . . . . . . . . . . . . . . . . 17-160
EAS 0 alarm EAS 8 alarm

unexpected board type . . . . . . . . . 18-3 EAS has detected main power failure . . 18-7
EAS 1 alarm EAS alarms . . . . . . . . . . . . . . . . 18-2
serial bus connection failure . . . . . . 18-5 EAS has detected main power failure
EAS 16 alarm EAS 8 alarm. . . . . . . . . . . . . . . 18-7
optocoupler 1 . . . . . . . . . . . . . . 18-9 EEPROM flash failure - no valid bootstrap code
EAS 17 alarm object present
optocoupler 2 . . . . . . . . . . . . . . 18-9 BSP 1 alarm. . . . . . . . . . . . . . . . 5-4
EAS 18 alarm BTP 1 alarm. . . . . . . . . . . . . . . . 7-4
optocoupler 3 . . . . . . . . . . . . . . 18-9 DHP 1 alarm . . . . . . . . . . . . . . 15-4
EAS 19 alarm GPROC 1 alarm . . . . . . . . . . . . . 23-4
optocoupler 4 . . . . . . . . . . . . . . 18-9 EEPROM flash object failure
EAS 20 alarm BSP 8 alarm. . . . . . . . . . . . . . . . 5-6
optocoupler 5 . . . . . . . . . . . . . . 18-9 BTP 8 alarm. . . . . . . . . . . . . . . . 7-6
EAS 21 alarm DHP 8 alarm . . . . . . . . . . . . . . 15-6
optocoupler 6 . . . . . . . . . . . . . . 18-9 GPROC 8 alarm . . . . . . . . . . . . . 23-6
EAS 22 alarm EEPROM flash programming failure
optocoupler 7 . . . . . . . . . . . . . . 18-9 BSP 17 alarm . . . . . . . . . . . . . . . 5-8
EAS 23 alarm BSP 21 alarm . . . . . . . . . . . . . . 5-11
optocoupler 8 . . . . . . . . . . . . . . 18-9 BTP 17 alarm . . . . . . . . . . . . . . . 7-8
EAS 24 alarm BTP 21 alarm . . . . . . . . . . . . . . 7-11
optocoupler 9 . . . . . . . . . . . . . . 18-10 DHP 17 alarm . . . . . . . . . . . . . . 15-8
EAS 26 alarm GPROC 17 alarm . . . . . . . . . . . . 23-8
optocoupler 11 . . . . . . . . . . . . . 18-10 GPROC 21 alarm . . . . . . . . . . . . 23-12
EAS 27 alarm EEPROM Flash Programming Failure
optocoupler 12 . . . . . . . . . . . . . 18-10 DHP 21 alarm . . . . . . . . . . . . . . 15-10
EAS 28 alarm EEPROM SW flash programming failure
optocoupler 13 . . . . . . . . . . . . . 18-10 BSP 50 alarm . . . . . . . . . . . . . . 5-35
EAS 29 alarm BSP 51 alarm . . . . . . . . . . . . . . 5-36
optocoupler 14 . . . . . . . . . . . . . 18-10 BTP 50 alarm . . . . . . . . . . . . . . 7-36
EAS 30 alarm BTP 51 alarm . . . . . . . . . . . . . . 7-37
optocoupler 15 . . . . . . . . . . . . . 18-10 CSFP 50 alarm . . . . . . . . . . . . . 14-11
EAS 31 alarm CSFP 51 alarm . . . . . . . . . . . . . 14-12
optocoupler 16 . . . . . . . . . . . . . 18-10
IX-30 68P02901W26-S
Nov 2007
Index
EEPROM SW flash programming failure (contd.) erroneous Layer 3 message received by the BSS
DHP 50 alarm . . . . . . . . . . . . . . 15-53 BSS 10 alarm . . . . . . . . . . . . . . 6-26
DHP 51 alarm . . . . . . . . . . . . . . 15-54 erroneous Layer 3 message received by the SMLC
GPROC 50 alarm . . . . . . . . . . . . 23-46 BSS 53 alarm . . . . . . . . . . . . . . 6-67
GPROC 51 alarm . . . . . . . . . . . . 23-47 event management
EGPRS - Unavailable - Insufficient GDS Available alarm messages . . . . . . . . . . . . . . 1-3
CELL 17 alarm . . . . . . . . . . . . . 12-42 event messages . . . . . . . . . . . . . . 1-3
EGPRS unavailable - No 64K PDCHs available exceeds lower limit disk usage
CELL 19 alarm . . . . . . . . . . . . . 12-48 OMC 30011 alarm . . . . . . . . . . . 32-36
EMDisconnectedFromDB exceeds upper limit disk usage
OMC 30008 alarm . . . . . . . . . . . 32-28 OMC 30010 alarm . . . . . . . . . . . 32-33
environmental variables expiration of N2
CONSOLIDATION. . . . . . . . . . . . . 1-5 CBL 2, PM alarm . . . . . . . . . . . . 10-7
EPSM, power supply module GSL 2, PM alarm . . . . . . . . . . . . 24-7
BCUP alarms . . . . . . . . . . . . . . . 4-2 OML 2, PM alarm . . . . . . . . . . . . 33-7
equalizer configuration mismatch RSL 2, PM alarm . . . . . . . . . . . . 40-7
DRI 168 alarm . . . . . . . . . . . . 17-249 XBL 2, PM alarm . . . . . . . . . . . . 47-7
equalizer control processor failure - watchdog external combiner main fuse failure
timer expired IAS 20 alarm . . . . . . . . . . . . . . 25-28
DRI 70 alarm . . . . . . . . . . . . . 17-121 external combiner redundant fuse failure
equalizer failure IAS 21 alarm . . . . . . . . . . . . . . 25-30
DRI 214 . . . . . . . . . . . . . . . . 17-280 external power booster amplifier 1 failure
equalizer firmware failure CAB 25 alarm . . . . . . . . . . . . . . . 8-3
DRI 184 alarm . . . . . . . . . . . . 17-259 SITE 25 alarm. . . . . . . . . . . . . . 42-64
equalizer output overflowed external power booster amplifier 2 failure
DRI 159 alarm . . . . . . . . . . . . 17-231 CAB 26 alarm . . . . . . . . . . . . . . . 8-5
DRI 160 alarm . . . . . . . . . . . . 17-233 SITE 26 alarm. . . . . . . . . . . . . . 42-66
equalizer timeslot 0 failure external power booster failure
DRI 176 alarm . . . . . . . . . . . . 17-257 CAB 27 alarm . . . . . . . . . . . . . . . 8-7
erroneous BSSGP message received from the SITE 27 alarm. . . . . . . . . . . . . . 42-68
SGSN . . . . . . . . . . . . . . . . . . . 42-81
F_BSS_ACI_FAULT . . . . . . . . . . . . 6-43 Firmware initiated SYNC calibration

F_BSS_ACI_FAULT_CLEAR . . . . . . . . 6-45 DHP 44 alarm . . . . . . . . . . . . . . 15-45
F_BSS_CIC_FAULT . . . . . . . . . . . . 6-47 flow control procedure has started barring normal
F_BSS_FAULT_CLEAR . . . . . . . . . . 6-53 calls from access classes 0-9 . . . . . . . 12-4
F_BSS_GCI_FAULT . . . . . . . . . . . . 6-51 FMIC . . . . . . . . . . . . . . . . . . . 1-12
F_BSS_PIC_FAULT . . . . . . . . . . . . 6-55 frame slip daily threshold exceeded
F_BSS_PIC_FAULT_CLEAR . . . . . . . . 6-57 MMS 8 alarm . . . . . . . . . . . . . . 29-19
F_BSS_RCI_FAULT . . . . . . . . . . . . 6-39 frame slip hourly threshold exceeded
failure of PCMCIA Card 1 on NVM board MMS 9 alarm . . . . . . . . . . . . . . 29-21
SITE 31 alarm. . . . . . . . . . . . . . 42-77 Frame slip OOS threshold exceeded
fan tray 0 failure MMS 10 alarm . . . . . . . . . . . . . 29-23
IAS 103 alarm. . . . . . . . . . . . . 25-123 frequency difference in mate GCLK
fan tray 1 failure GCLK 8 alarm . . . . . . . . . . . . . . 21-19
IAS 104 alarm. . . . . . . . . . . . . 25-125 FRMR-frames
fan tray 2 failure CBL 1, PM alarm . . . . . . . . . . . . 10-5
IAS 105 alarm. . . . . . . . . . . . . 25-127 GSL 1, PM alarm . . . . . . . . . . . . 24-5
FEP alarms OML 1, PM alarm . . . . . . . . . . . . 33-5
introduction . . . . . . . . . . . . . . . 17-7 RSL 1, PM alarm . . . . . . . . . . . . 40-5
filexferFailed XBL 1, PM alarm . . . . . . . . . . . . 47-5
OMC 30002 alarm . . . . . . . . . . . 32-11 front end processor failure
Firmware initiated calibration DRI 211 alarm . . . . . . . . . . . . 17-274
GCLK 22 alarm . . . . . . . . . . . . . 21-45
68P02901W26-S IX-31
Nov 2007
Index
Front End Processor to Radio Subsystem FRUs (contd.)

Software Communication Failure GPROC alarms . . . . . . . . . . . . . 23-3
DRI 36 alarm . . . . . . . . . . . . . . 17-69 KSW alarms . . . . . . . . . . . . . . . 26-2
FRUs MMS alarms . . . . . . . . . . . . . . 29-4
BCUP alarms . . . . . . . . . . . . . . . 4-2 MSI alarms . . . . . . . . . . . . . . . 30-2
BTP alarms . . . . . . . . . . . . . . . . 7-3 PSP alarms . . . . . . . . . . . . . . . 39-2
CAB alarms . . . . . . . . . . . . . . . . 8-2 FU . . . . . . . . . . . . . . . . . . . . 1-15
COMB alarms . . . . . . . . . . . . . . 13-2 full reset
CSFP alarms . . . . . . . . . . . . . . 14-2 COMB 9 alarm . . . . . . . . . . . . . 13-14
DHP alarms . . . . . . . . . . . . . . . 15-3 functional units
DPROC alarms . . . . . . . . . . . . . 16-2 cell . . . . . . . . . . . . . . . . . . . 1-15
DRI alarms . . . . . . . . . . . . . . . 17-8 site . . . . . . . . . . . . . . . . . . . 1-15
GCLK alarms . . . . . . . . . . . . . . 21-2
GBL 0 alarm GCLK 5 alarm

link disconnected . . . . . . . . . . . . 20-3 125us reference count overflow. . . . . 21-13
GBL alarms GCLK 6 alarm
introduction . . . . . . . . . . . . . . . 20-2 60ms reference count overflow . . . . . 21-15
GCLK 0 alarm GCLK 7 alarm
reference distribution module failure . . 21-3 6.12s reference count overflow . . . . . 21-17
GCLK 11 alarm GCLK 8 alarm
long-term -average values are unsta frequency difference in mate GCLK . . . 21-19
ble . . . . . . . . . . . . . . . . . . . 21-25 GCLK 9 alarm
GCLK 12 alarm hard reset . . . . . . . . . . . . . . . . 21-22
unrecognized hardware revision GCLK alarms
level. . . . . . . . . . . . . . . . . . . 21-27 FRUs . . . . . . . . . . . . . . . . . . 21-2
GCLK 14 alarm introduction . . . . . . . . . . . . . . . 21-2
phase lock failure . . . . . . . . . . . . 21-28 GCLK calibration request
GCLK 15 alarm GCLK 26 alarm . . . . . . . . . . . . . 21-49
watchdog timer expired . . . . . . . . . 21-32 GDP alarms . . . . . . . . . . . . . . . . 30-2
GCLK 16 alarm GPROC 1 alarm
clock output failure . . . . . . . . . . . 21-34 EEPROM flash failure - no valid bootstrap code
GCLK 17 alarm object present. . . . . . . . . . . . . . 23-4
SYNC shutdown request . . . . . . . . 21-36 GPROC 17 alarm
GCLK 18 alarm EEPROM flash programming failure . . 23-8
not operational . . . . . . . . . . . . . 21-38 GPROC 19 alarm
GCLK 19 alarm RSL Links Congestion. . . . . . . . . . 23-10
warmup failure . . . . . . . . . . . . . 21-40 GPROC 20 alarm
GCLK 2 alarm LAPD controller failure . . . . . . . . . 23-11
clock reference failure . . . . . . . . . 21-5 GPROC 21 alarm
GCLK 20 alarm EEPROM flash programming failure . . 23-12
invalid mode . . . . . . . . . . . . . . 21-42 GPROC 22 alarm
GCLK 21 alarm SWFM indication . . . . . . . . . . . . 23-14
calibration in progress . . . . . . . . . 21-44 GPROC 23 alarm
GCLK 22 alarm SYNC lost phase lock to master
Firmware initiated calibration . . . . . 21-45 GCLK . . . . . . . . . . . . . . . . . . 23-15
processor bus communication fail TDM interface configuration failure. . . 23-48
ure . . . . . . . . . . . . . . . . . . . 21-52 GPROC 232 alarm
GCLK 26 alarm processor bus communication fail
GCLK calibration request . . . . . . . . 21-49 ure . . . . . . . . . . . . . . . . . . . 23-50
phase lock lost . . . . . . . . . . . . . 21-9 process safe test audit failure . . . . . . 23-51
GCLK 4 alarm, Phase Lock Lost . . . . . . 21-9
IX-32 68P02901W26-S
Nov 2007
Index
GPROC 24 alarm GPROC 50 alarm (contd.)

Bad clock source or SYNC OCXO replacement EEPROM SW flash programming fail
required. . . . . . . . . . . . . . . . . 23-16 ure . . . . . . . . . . . . . . . . . . . 23-46
GPROC 25 alarm GPROC 51 alarm
SYNC warm up failure . . . . . . . . . 23-17 EEPROM SW flash programming fail
GPROC 254 alarm ure . . . . . . . . . . . . . . . . . . . 23-47
device failure . . . . . . . . . . . . . . 23-53 GPROC 8 alarm
GPROC 26 alarm EEPROM flash object failure . . . . . . 23-6
SYNC calibration request . . . . . . . . 23-18 GPROC alarms
GPROC 27 alarm FRUs . . . . . . . . . . . . . . . . . . 23-3
SYNC shutdown request . . . . . . . . 23-19 introduction . . . . . . . . . . . . . . . 23-3
GPROC 28 alarm GPRS and baseband hopping configuration failure
SYNC clock output failure. . . . . . . . 23-20 CELL 7 alarm . . . . . . . . . . . . . . 12-21
GPROC 29 alarm GPRS not supported by radio
SYNC watchdog timer expired . . . . . 23-21 DRI 219 alarm . . . . . . . . . . . . 17-290
GPROC 30 alarm GPRS unavailable - No GPRS capable carriers
clock A signal loss. . . . . . . . . . . . 23-22 available
GPROC 31 alarm CELL 13 alarm . . . . . . . . . . . . . 12-33
clock B signal loss. . . . . . . . . . . . 23-24 GPRS unavailable - No PDCHs available
GPROC 32 alarm CELL 12 alarm . . . . . . . . . . . . . 12-32
TDM interface failure - assigned timeslot GPRS unavailable - PBCCH timeslot out of sync
counter underflow . . . . . . . . . . . 23-26 CELL 14, PM alarm . . . . . . . . . . . 12-38
GPROC 33 alarm GSL 0, PM alarm
TDM interface failure - assigned timeslot invalid received frames . . . . . . . . . 24-3
counter overflow . . . . . . . . . . . . 23-28 GSL 1, PM alarm
GPROC 34 alarm FRMR-frames . . . . . . . . . . . . . . 24-5
TDM interface failure - TDM parity GSL 10 alarm
error . . . . . . . . . . . . . . . . . . 23-30 link disconnected . . . . . . . . . . . . 24-9
GPROC 35 alarm GSL 11 alarm
LAN connection failure . . . . . . . . . 23-32 LAPD protocol error . . . . . . . . . . 24-13
GPROC 39 alarm GSL 13 alarm
software failure . . . . . . . . . . . . . 23-34 LAPD protocol error threshold e
GPROC 40 alarm xceeded . . . . . . . . . . . . . . . . . 24-15
spurious interrupt. . . . . . . . . . . . 23-36 GSL 15 alarm
GPROC 42 alarm Too many LAPD protocol errors . . . . . 24-17
site reset occurred due to front panel GSL 2, PM alarm
reset . . . . . . . . . . . . . . . . . . 23-38 expiration of N2. . . . . . . . . . . . . 24-7
GPROC 48 alarm GSL alarms
Memory location is corrupt . . . . . . . 23-45 introduction . . . . . . . . . . . . . . . 24-2
GPROC 50 alarm GSM timeslot counter mismatch
DRI 49 alarm . . . . . . . . . . . . . . 17-80
hard reset HDSL modem loop 2 synch timer expired

DRI 37 alarm . . . . . . . . . . . . . . 17-70 MMS 26 alarm . . . . . . . . . . . . . 29-53
GCLK 9 alarm . . . . . . . . . . . . . . 21-22 heat management system unit failure
KSW 8 alarm . . . . . . . . . . . . . . 26-30 IAS 85 alarm . . . . . . . . . . . . . . 25-91
MSI 1 alarm. . . . . . . . . . . . . . . 30-5 HO request from the MSC protocol error
HDLC channel open failed BSS 17, PM alarm. . . . . . . . . . . . 6-30
XBL 16 alarm . . . . . . . . . . . . . . 47-18 hopping DRI failure
HDSL modem loop 0 synch loss timer expired DRI 210 alarm . . . . . . . . . . . . 17-272
MMS 25 alarm . . . . . . . . . . . . . 29-49
68P02901W26-S IX-33
Nov 2007
Index
IAS +27 V DAB power fuse failure IAS 20 alarm

IAS 75 alarm . . . . . . . . . . . . . . 25-79 external combiner main fuse failure. . . 25-28
IAS +27 V power fuse failure IAS 21 alarm
IAS 32 alarm . . . . . . . . . . . . . . 25-44 external combiner redundant fuse
IAS 0 alarm failure . . . . . . . . . . . . . . . . . . 25-30
unexpected board type . . . . . . . . . 25-5 IAS 22 alarm
IAS 1 alarm multicoupler main fuse failure . . . . . 25-32
serial bus connection failure . . . . . . 25-7 IAS 23 alarm
IAS 10 alarm multicoupler redundant fuse failure. . . 25-34
power supply unit 2 failure . . . . . . . 25-14 IAS 30 alarm
IAS 100 alarm spare fuse failure . . . . . . . . . . . . 25-40
Cabinet protection system failure . . . 25-117 IAS 31 alarm
IAS 101 alarm DRAM battery backup fuse failure . . . 25-42
power supply temperature high . . . . 25-119 IAS 32 alarm
IAS 102 alarm IAS +27 V power fuse failure . . . . . . 25-44
mains ac supply failure . . . . . . . . 25-121 IAS 37 alarm
IAS 103 alarm lower cage fan #2 failure . . . . . . . . 25-48
fan tray 0 failure . . . . . . . . . . . 25-123 IAS 41 alarm
IAS 104 alarm multicoupler failure . . . . . . . . . . . 25-52
IAS 105 alarm converter failure . . . . . . . . . . . . 25-54
IAS 106 alarm converter overtemperature . . . . . . . 25-56
rectifier failure . . . . . . . . . . . . 25-129 IAS 51 alarm
IAS 107 alarm duplexer voltage error . . . . . . . . . 25-61
battery box temperature high . . . . . 25-131 IAS 59 alarm
IAS 108 alarm battery backup output failure . . . . . . 25-63
alarm board failed . . . . . . . . . . 25-133 IAS 60 alarm
IAS 109 alarm battery backup input failure . . . . . . 25-65
auxiliary alarm 1 . . . . . . . . . . . 25-135 IAS 61 alarm
IAS 11 alarm RCU #5 circuit breaker failure . . . . . 25-67
power supply unit 3 failure . . . . . . . 25-16 IAS 62 alarm
IAS 110 alarm DPSM 1 failure . . . . . . . . . . . . . 25-69
urgent critical alarm . . . . . . . . . 25-136 IAS 63 alarm
IAS 111 alarm DPSM 0 failure . . . . . . . . . . . . . 25-71
cabinet protection board fuse fail IAS 75 alarm
ure . . . . . . . . . . . . . . . . . . 25-137 IAS +27 V DAB power fuse failure . . . 25-79
IAS 112-113 alarms, Heat Management System IAS 8 alarm
Unit Failure 1 & 2 power supply unit 0 failure . . . . . . . 25-10
IAS: Heat Management System Unit Failure 1 IAS 80 alarm
& 2 . . . . . . . . . . . . . . . . . . 25-139 power supply unit - input failure . . . . 25-81
IAS 114-115 alarms, Mains ac Supply Failure 1 IAS 81 alarm
&2 power supply unit - output failure . . . . 25-83
IAS: Mains ac Supply Failure 1 & 2 . . 25-141 IAS 82 alarm
IAS 116-117 alarms, Rectifier Failure 1 & 2 BTS cabinet overtemperature . . . . . . 25-85
IAS: Rectifier Failure 1 & 2 . . . . . . 25-143 IAS 83 alarm
IAS 16 alarm low voltage disconnect imminent . . . . 25-87
matrix main fuse failure. . . . . . . . . 25-20 IAS 84 alarm
IAS 17 alarm air conditioning unit failure . . . . . . . 25-89
matrix control redundant fuse failure . . 25-22 IAS 85 alarm
IAS 18 alarm heat management system unit fail
internal combiner main fuse failure . . . 25-24 ure . . . . . . . . . . . . . . . . . . . 25-91
IAS 19 alarm IAS 86 alarm
internal combiner redundant fuse cabinet fan failure. . . . . . . . . . . . 25-93
failure . . . . . . . . . . . . . . . . . . 25-26
IX-34 68P02901W26-S
Nov 2007
Index
IAS 87 alarm intra-BSS HO failed and recovered to org channel

ancillary cabinet overtemperature . . . 25-95 CELL 13, PM alarm . . . . . . . . . . . 12-34
IAS 9 alarm intra-BSS HO primary target cell blocked
power supply unit 1 failure . . . . . . . 25-12 CELL 11, PM alarm . . . . . . . . . . . 12-31
IAS 91 alarm intra-cell handover failed & mobile lost
voltage standing wave ratio performance CELL 10, PM alarm . . . . . . . . . . . 12-28
low . . . . . . . . . . . . . . . . . . . 25-99 intra-cell handover failed & recovered to org
IAS 92 alarm channel
smoke alarm . . . . . . . . . . . . . 25-101 CELL 9, PM alarm . . . . . . . . . . . 12-25
IAS 93 alarm introduction
door open . . . . . . . . . . . . . . . 25-103 AXCDR alarms . . . . . . . . . . . . . . 3-2
IAS 94 alarm BSP alarms . . . . . . . . . . . . . . . . 5-3
no connection tIAS 94 alarm . . . . . 25-105 BSS alarms . . . . . . . . . . . . . . . . 6-3
IAS 94 alarm, No Connection to Alarms Board - BTP alarms . . . . . . . . . . . . . . . . 7-3
connection broken . . . . . . . . . . . 25-105 CAB alarms . . . . . . . . . . . . . . . . 8-2
IAS 95 alarm CAGE alarms . . . . . . . . . . . . . . . 9-2
low noise amplifier fuse failure . . . . 25-107 CBL alarms . . . . . . . . . . . . . . . 10-2
IAS 97 alarm CBUS alarms . . . . . . . . . . . . . . 11-2
no connection to alarm board - radio CCDSP alarms . . . . . . . . . . . . . 17-7
OOS . . . . . . . . . . . . . . . . . . 25-111 CELL alarms . . . . . . . . . . . . . . 12-3
IAS 98 alarm COMB alarms . . . . . . . . . . . . . . 13-2
no redundant connection to alarms board - combiner alarms . . . . . . . . . . . . 13-2
radio OOS . . . . . . . . . . . . . . . 25-113 CSFP alarms . . . . . . . . . . . . . . 14-2
IAS 99 alarm DHP alarms . . . . . . . . . . . . . . . 15-3
no connection to alarm board - alarm board DPROC alarms . . . . . . . . . . . . . 16-2
removed . . . . . . . . . . . . . . . 25-115 DRI alarms . . . . . . . . . . . . . . . 17-7
IAS alarms FEP alarms . . . . . . . . . . . . . . . 17-7
introduction . . . . . . . . . . . . . . . 25-4 GBL alarms . . . . . . . . . . . . . . . 20-2
IAS: BCU Upper Cage Fan #3-#5 Fuse GCLK alarms . . . . . . . . . . . . . . 21-2
Failure . . . . . . . . . . . . . . . . . . 25-38 GPROC alarms . . . . . . . . . . . . . 23-3
impact list GSL alarms . . . . . . . . . . . . . . . 24-2
impact list format . . . . . . . . . . . . 1-15 IAS alarms . . . . . . . . . . . . . . . 25-4
information KSW alarms . . . . . . . . . . . . . . . 26-2
additional field . . . . . . . . . . . . . 1-18 LAN alarms . . . . . . . . . . . . . . . 27-2
device alarm . . . . . . . . . . . . . . . 1-8 LMTL alarms . . . . . . . . . . . . . . 28-2
reconfiguration . . . . . . . . . . . . . 1-13 manual organization . . . . . . . . . . . 1-2
initial synchronization of radio and GPRS channel MCAP/TDM bus alarms . . . . . . . . . 17-7
failed MMS alarms . . . . . . . . . . . . . . 29-3
DRI 15 alarm . . . . . . . . . . . . . . 17-30 MSI alarms . . . . . . . . . . . . . . . 30-2
input failure MTL alarms . . . . . . . . . . . . . . . 31-2
BCUP 9 alarm . . . . . . . . . . . . . . . 4-9 OMC alarms . . . . . . . . . . . . . . 32-4
inter-BSS HO, MS HO failed message received OML alarms . . . . . . . . . . . . . . . 33-2
CELL 15, PM alarm . . . . . . . . . . . 12-40 PBUS alarms . . . . . . . . . . . . . . 34-2
intermittent . . . . . . . . . . . . . . . . 1-12 PCU alarms . . . . . . . . . . . . . . . 35-2
internal combiner main fuse failure PSP alarms . . . . . . . . . . . . . . . 39-2
IAS 18 alarm . . . . . . . . . . . . . . 25-24 RSL alarms . . . . . . . . . . . . . . . 40-2
internal combiner redundant fuse failure SBUS alarms . . . . . . . . . . . . . . 41-2
IAS 19 alarm . . . . . . . . . . . . . . 25-26 SITE alarms . . . . . . . . . . . . . . . 42-3
internal loopback audit failure TBUS alarms . . . . . . . . . . . . . . 43-2
KSW 225 alarm . . . . . . . . . . . . . 26-57 TDM alarms . . . . . . . . . . . . . . . 44-2
internal message error - dual-port RAM segment TIMESLOT alarms . . . . . . . . . . . 45-2
full TRU alarms . . . . . . . . . . . . . . . 46-2
DRI 3 alarm . . . . . . . . . . . . . . . 17-13 XBL alarms . . . . . . . . . . . . . . . 47-2
internal message error - pointer misalignment invalid calibration data
DRI 2 alarm . . . . . . . . . . . . . . . 17-10 DRI 171 alarm . . . . . . . . . . . . 17-255
intra-BSS HO failed and mobile lost
CELL 14, PM alarm . . . . . . . . . . . 12-36
68P02901W26-S IX-35
Nov 2007
Index
Invalid in-call modification of destination channel invalid received frames (contd.)

type RSL 0, PM alarm . . . . . . . . . . . . 40-3
DRI 221 alarm . . . . . . . . . . . . 17-291 XBL 0, PM alarm . . . . . . . . . . . . 47-3
invalid mode invalid transceiver calibration data
GCLK 20 alarm . . . . . . . . . . . . . 21-42 DRI 218 alarm . . . . . . . . . . . . 17-288
invalid received frames invalidLicenseFileAlarm
CBL 0, PM alarm . . . . . . . . . . . . 10-3 OMC 300735alarm . . . . . . . . . . 32-116
GSL 0, PM alarm . . . . . . . . . . . . 24-3 IPSM, power supply module
OML 0, PM alarm . . . . . . . . . . . . 33-3 BCUP alarms . . . . . . . . . . . . . . . 4-2
KSW 0 alarm KSW 254 alarm

parity highway 0 . . . . . . . . . . . . 26-4 device failure . . . . . . . . . . . . . . 26-63
parity highway 1 . . . . . . . . . . . . 26-8 parity highway 3 . . . . . . . . . . . . 26-12
lost communication with KSW . . . . . 26-36 lock A signal loss . . . . . . . . . . . . 26-14
local cage KSW TDM loopback test 6.12 second reference loss . . . . . . . 26-24
failure . . . . . . . . . . . . . . . . . . 26-41 KSW 7 alarm
KSW 2 alarm re-initialized unexpectedly . . . . . . . 26-27
parity highway 2 . . . . . . . . . . . . 26-10 KSW 8 alarm
KSW 224 alarm hard reset . . . . . . . . . . . . . . . . 26-30
safe test audit failure . . . . . . . . . . 26-54 KSW 9 alarm
KSW 225 alarm watchdog timer expired . . . . . . . . . 26-33
internal loopback audit failure . . . . . 26-57 KSW alarms
KSW 232 alarm FRUs . . . . . . . . . . . . . . . . . . 26-2
processor bus communication fail introduction . . . . . . . . . . . . . . . 26-2
ure . . . . . . . . . . . . . . . . . . . 26-60
LAN 0 alarm LAPD protocol error (contd.)

active & standby LAN failure . . . . . . 27-3 XBL 11 alarm . . . . . . . . . . . . . . 47-12
LAN 1 alarm LAPD protocol error threshold exceeded
LAN failure . . . . . . . . . . . . . . . 27-5 GSL 13 alarm . . . . . . . . . . . . . . 24-15
LAN alarms RSL 13 alarm . . . . . . . . . . . . . . 40-22
introduction . . . . . . . . . . . . . . . 27-2 XBL 13 alarm . . . . . . . . . . . . . . 47-14
LAN connection failure last GBL failed . . . . . . . . . . . . . . 42-79
BSP 35 alarm . . . . . . . . . . . . . . 5-26 last GSL failed
BTP 35 alarm . . . . . . . . . . . . . . 7-26 PCU 0 alarm . . . . . . . . . . . . . . 35-3
CSFP 35 alarm . . . . . . . . . . . . . 14-4 last LMTL link failure - signalling point
DHP 35 alarm . . . . . . . . . . . . . . 15-37 inaccessible
GPROC 35 alarm . . . . . . . . . . . . 23-32 BSS 49 alarm . . . . . . . . . . . . . . 6-59
LAN failure last MTL link failure - signalling point inaccessible
LAN 1 alarm . . . . . . . . . . . . . . 27-5 BSS 0 alarm. . . . . . . . . . . . . . . . 6-4
LANX slot 19 communication failure Last MTL may have gone out of service
CAGE 26 alarm . . . . . . . . . . . . . . 9-6 OMC 30065 alarm . . . . . . . . . . 32-107
LANX slot 20 communication failure last NS-VC failed
CAGE 27 alarm . . . . . . . . . . . . . . 9-6 CELL 3 alarm . . . . . . . . . . . . . . 12-15
LAPD protocol error last NS-VC for the PCU failed . . . . . . . 42-90
GSL 11 alarm . . . . . . . . . . . . . . 24-13 last RSL link failure
RSL 11 alarm . . . . . . . . . . . . . . 40-18
IX-36 68P02901W26-S
Nov 2007
Index
last RSL link failure (contd.) LMTL 12, PM alarm

SITE 0 alarm . . . . . . . . . . . . . . 42-4 SL congestion indications . . . . . . . . 28-32
last TRAU GDS failed . . . 42-91, 42-97 to 42-98 LMTL 3 alarm
last XBL link failure link traffic too high . . . . . . . . . . . 28-14
ABSS 0 alarm . . . . . . . . . . . . . . . 2-2 LMTL 4, PM alarm
level 1/2/3 failure SL failure - excessive duration of
OMC 30012 alarm . . . . . . . . . . . 32-38 congestion . . . . . . . . . . . . . . . 28-18
LicenseAuditNotAvailableAlarm LMTL 5, PM alarm
OMC 30071 alarm . . . . . . . . . . 32-113 SL alignment failure . . . . . . . . . . 28-20
LicenseFileNotAvailableAlarm LMTL alarms
OMC 30072 alarm . . . . . . . . . . 32-114 introduction . . . . . . . . . . . . . . . 28-2
LicenseViolationAlarm local cage KSW TDM loopback test failure
OMC 30073 alarm . . . . . . . . . . 32-115 KSW 11 alarm. . . . . . . . . . . . . . 26-41
link A sanity failure local KSWX clock fibre failure
COMB 5 alarm . . . . . . . . . . . . . 13-6 CBUS 4 alarm . . . . . . . . . . . . . . 11-7
link audit failure local KSWX slot 0 communication failure
RSL 14 alarm . . . . . . . . . . . . . . 40-25 41 CAGE alarm . . . . . . . . . . . . . 9-19
link B sanity failure local KSWX slot 1 communication failure
COMB 6 alarm . . . . . . . . . . . . . 13-8 41 CAGE alarm . . . . . . . . . . . . . 9-19
link disconnected local KSWX TDM error
GBL 0 alarm . . . . . . . . . . . . . . 20-3 TBUS 3 alarm . . . . . . . . . . . . . . 43-5
GSL 10 alarm . . . . . . . . . . . . . . 24-9 lock A signal loss
RSL 10 alarm . . . . . . . . . . . . . . 40-9 KSW 4 alarm . . . . . . . . . . . . . . 26-14
XBL 10 alarm . . . . . . . . . . . . . . 47-9 long-term -average values are unstable
link traffic too high GCLK 11 alarm . . . . . . . . . . . . . 21-25
LMTL 3 alarm . . . . . . . . . . . . . . 28-14 lost communication with KSW
MTL 3 alarm . . . . . . . . . . . . . . 31-11 KSW 10 alarm. . . . . . . . . . . . . . 26-36
LMTL 0 alarm low noise amplifier fuse failure
signalling link failure . . . . . . . . . . 28-3 IAS 95 alarm . . . . . . . . . . . . . 25-107
LMTL 0, PM alarm low voltage disconnect imminent
SL failure - all reasons . . . . . . . . . 28-6 IAS 83 alarm . . . . . . . . . . . . . . 25-87
LMTL 1 alarm LTU configuration failure
SMLC processor outage. . . . . . . . . 28-8 MMS 40 alarm . . . . . . . . . . . . . 29-90
LMTL 1, PM alarm LTU download failure
SL failure - abnormal FIBR/BSNR . . . . 28-10 MMS 39 alarm . . . . . . . . . . . . . 29-88
LMTL 11, PM alarm
SL congestion events resulting in loss of
MSUs . . . . . . . . . . . . . . . . . . 28-30
M-Cell Micro interconnect failure master HDSL modem loop 0 SNR OOS threshold
DRI 170 alarm . . . . . . . . . . . . 17-253 exceeded
mains ac supply failure MMS 35 alarm . . . . . . . . . . . . . 29-72
IAS 102 alarm. . . . . . . . . . . . . 25-121 master HDSL modem loop 1 SNR daily threshold
manual organization exceeded
introduction . . . . . . . . . . . . . . . . 1-2 MMS 28 alarm . . . . . . . . . . . . . 29-58
map display colours . . . . . . . . . . . . 1-20 master HDSL modem loop 1 SNR hourly threshold
master CBUS signal provided by slave GCLK exceeded
CBUS 2 alarm . . . . . . . . . . . . . . 11-5 MMS 32 alarm . . . . . . . . . . . . . 29-66
master HDSL modem loop 0 SNR daily threshold master HDSL modem loop 1 SNR OOS threshold
exceeded exceeded
MMS 27 alarm . . . . . . . . . . . . . 29-56 MMS 36 alarm . . . . . . . . . . . . . 29-76
master HDSL modem loop 0 SNR hourly threshold matrix control redundant fuse failure
exceeded IAS 17 alarm . . . . . . . . . . . . . . 25-22
MMS 31 alarm . . . . . . . . . . . . . 29-64
68P02901W26-S IX-37
Nov 2007
Index
matrix main fuse failure MMS 26 alarm

IAS 16 alarm . . . . . . . . . . . . . . 25-20 HDSL modem loop 2 synch timer
Maximum number of RTFs in MIB above 90% of expired . . . . . . . . . . . . . . . . . 29-53
licence limit MMS 27 alarm
OMC 30069 alarm . . . . . . . . . . 32-110 master HDSL modem loop 0 SNR daily
MCAP/TDM bus alarms threshold exceeded . . . . . . . . . . . 29-56
introduction . . . . . . . . . . . . . . . 17-7 MMS 28 alarm
Memory location fault master HDSL modem loop 1 SNR daily
BSP 48 alarm . . . . . . . . . . . . . . 5-34 threshold exceeded . . . . . . . . . . . 29-58
Memory location is corrupt MMS 29 alarm
BTP 48 alarm . . . . . . . . . . . . . . 7-35 slave HDSL modem loop 0 SNR daily threshold
CSFP 48 alarm . . . . . . . . . . . . . 14-8 exceeded . . . . . . . . . . . . . . . . 29-60
GPROC 48 alarm . . . . . . . . . . . . 23-45 MMS 30 alarm
Memory location is corrupt. Replace GPROC slave HDSL modem loop 1 SNR daily threshold
board exceeded . . . . . . . . . . . . . . . . 29-62
DHP 48 alarm . . . . . . . . . . . . . . 15-52 MMS 31 alarm
Memory usage exceeds lower limit master HDSL modem loop 0 SNR hourly
OMC 30063 alarm . . . . . . . . . . 32-104 threshold exceeded . . . . . . . . . . . 29-64
Memory usage exceeds upper limit MMS 32 alarm
OMC 30064 alarm . . . . . . . . . . 32-106 master HDSL modem loop 1 SNR hourly
MMS 0 alarm threshold exceeded . . . . . . . . . . . 29-66
synchronization loss daily threshold MMS 33 alarm
exceeded . . . . . . . . . . . . . . . . 29-5 slave HDSL modem loop 0 SNR hourly threshold
MMS 1 alarm exceeded . . . . . . . . . . . . . . . . 29-68
synchronization loss hourly threshold MMS 34 alarm
exceeded . . . . . . . . . . . . . . . . 29-7 MMS 34 alarm . . . . . . . . . . . . . 29-70
MMS 10 alarm MMS 35 alarm
Frame slip OOS threshold exceeded . . 29-23 master HDSL modem loop 0 SNR OOS threshold
bit error daily threshold exceeded . . . 29-24 MMS 36 alarm
MMS 13 alarm master HDSL modem loop 1 SNR OOS threshold
bit error hourly threshold exceeded. . . 29-26 exceeded . . . . . . . . . . . . . . . . 29-76
bit error OOS threshold exceeded. . . . 29-28 slave HDSL modem loop 0 SNR OOS threshold
synchronization loss OOS timer e MMS 38 alarm
xpired . . . . . . . . . . . . . . . . . . 29-31 slave HDSL modem loop 1 SNR OOS threshold
remote alarm OOS timer expired . . . . 29-34 MMS 39 alarm
MMS 2 alarm LTU download failure . . . . . . . . . . 29-88
synchronization loss OOS threshold MMS 4 alarm
exceeded . . . . . . . . . . . . . . . . 29-9 remote alarm daily threshold e
MMS 20 alarm xceeded . . . . . . . . . . . . . . . . . 29-12
red alarm daily threshold exceeded . . . 29-37 MMS 40 alarm
MMS 21 alarm LTU configuration failure . . . . . . . . 29-90
red alarm hourly threshold exceeded . . 29-39 MMS 41 alarm
MMS 22 alarm connectivity mismatch between BSC and
red alarm OOS threshold exceeded . . . 29-41 RXCDR . . . . . . . . . . . . . . . . . 29-91
red alarm OOS timer expired . . . . . . 29-44 remote alarm hourly threshold e
modem to NIU serial channel control link MMS 6 alarm
failure . . . . . . . . . . . . . . . . . . 29-47 remote alarm OOS threshold e
HDSL modem loop 0 synch loss timer MMS 8 alarm
expired . . . . . . . . . . . . . . . . . 29-49 frame slip daily threshold exceeded. . . 29-19
MMS 253 alarm
critical alarm threshold exceeded . . . . 29-94
IX-38 68P02901W26-S
Nov 2007
Index
MMS 9 alarm MSI alarms

frame slip hourly threshold exceeded . . 29-21 FRUs . . . . . . . . . . . . . . . . . . 30-2
MMS alarms introduction . . . . . . . . . . . . . . . 30-2
FRUs . . . . . . . . . . . . . . . . . . 29-4 MSUs discarded due to SL congestion
introduction . . . . . . . . . . . . . . . 29-3 MTL 10, PM alarm . . . . . . . . . . . 31-22
mobile assignment failure from MS MTL 0 alarm
CELL 23, PM alarm . . . . . . . . . . . 12-55 signalling link failure . . . . . . . . . . 31-3
mobile assignment request from MSC protocol MTL 0, PM alarm
error SL failure - all reasons . . . . . . . . . 31-7
BSS 7, PM alarm . . . . . . . . . . . . 6-21 MTL 1 alarm
Mobile Switching Centre (MSC) to BSS interface, MSC processor outage . . . . . . . . . 31-8
layer 3 MTL 1, PM alarm
BSS alarms . . . . . . . . . . . . . . . . 6-3 SL failure - abnormal FIBR/BSNR . . . . 31-9
modem to NIU serial channel control link failure MTL 10, PM alarm
MMS 24 alarm . . . . . . . . . . . . . 29-47 MSUs discarded due to SL conges
MSC processor outage tion . . . . . . . . . . . . . . . . . . . 31-22
MTL 1 alarm . . . . . . . . . . . . . . 31-8 MTL 11, PM alarm
MSI 0 alarm SL congestion events resulting in loss of
re-initialized unexpectedly . . . . . . . 30-3 MSUs . . . . . . . . . . . . . . . . . . 31-23
MSI 1 alarm MTL 12, PM alarm
hard reset . . . . . . . . . . . . . . . . 30-5 SL congestion indications . . . . . . . . 31-24
MSI 11 - 40 alarms MTL 2, PM alarm
DSP channel audit failures . . . . . . . 30-21 SL failure - excessive delay of ACK . . . 31-10
MSI 2 alarm MTL 3 alarm
watchdog timer expired . . . . . . . . . 30-7 link traffic too high . . . . . . . . . . . 31-11
safe test audit failure . . . . . . . . . . 30-24 SL failure - excessive error rate . . . . . 31-13
TDM interface configuration failure. . . 30-26 SL failure - excessive duration of
MSI 232 alarm congestion . . . . . . . . . . . . . . . 31-14
processor bus communication fail MTL 5, PM alarm
ure . . . . . . . . . . . . . . . . . . . 30-28 SL alignment failure . . . . . . . . . . 31-15
MSI 234 MTL 6, PM alarm
active link connection failure . . . . . . 30-30 number of signal units in error . . . . . 31-17
device failure . . . . . . . . . . . . . . 30-32 SLMTL 7, PM alarm. . . . . . . . . . . 31-18
clock B signal loss. . . . . . . . . . . . 30-9 start of remote processor outage . . . . 31-20
clock A signal loss. . . . . . . . . . . . 30-11 number of octets retransmitted . . . . . 31-21
MSI 5 alarm MTL alarms
assigned timeslot counter underflow . . 30-13 introduction . . . . . . . . . . . . . . . 31-2
MSI 6 alarm multicoupler failure
assigned timeslot counter overflow . . . 30-15 IAS 41 alarm . . . . . . . . . . . . . . 25-52
MSI 7 alarm multicoupler main fuse failure
TDM parity error . . . . . . . . . . . . 30-17 IAS 22 alarm . . . . . . . . . . . . . . 25-32
MSI 9 alarm multicoupler redundant fuse failure
TRAU frame synchronization loss . . . . 30-19 IAS 23 alarm . . . . . . . . . . . . . . 25-34
NE error state neighbour statistics table exceeded the configured

OMC 30006 alarm . . . . . . . . . . . 32-23 size. Operator must take act . . . . . . . 32-67
NE response timeout nmcAgentError
OMC 30005 alarm . . . . . . . . . . . 32-20 OMC 30025 alarm . . . . . . . . . . . 32-64
68P02901W26-S IX-39
Nov 2007
Index
no cell (BVC) block acknowledgement from the no NS-VC reset acknowledgement from the
SGSN SGSN . . . . . . . . . . . . . . . . . . . 42-88
CELL 5 alarm . . . . . . . . . . . . . . 12-19 no NS-VC unblock acknowledgement from the
no clock references available SGSN . . . . . . . . . . . . . . . . . . . 42-85
SITE 21 alarm. . . . . . . . . . . . . . 42-55 No PM database fragment available
no connection to alarm board - alarm board OMC 30067 alarm . . . . . . . . . . 32-109
removed no redundant connection to alarms board - radio
IAS 99 alarm . . . . . . . . . . . . . 25-115 OOS
no connection to alarm board - radio OOS IAS 98 alarm . . . . . . . . . . . . . 25-113
IAS 97 alarm . . . . . . . . . . . . . 25-111 no SMLC acknowlegement for global reset
no connection to alarms board - connection BSS 52 alarm . . . . . . . . . . . . . . 6-66
broken noActivityInTimeslot
IAS 94 alarm . . . . . . . . . . . . . 25-105 OMC 30060 alarm . . . . . . 32-101, 32-103
no MSC acknowledgement for circuit block non-volatile memory failure
BSS 5 alarm. . . . . . . . . . . . . . . 6-15 BTP 237 alarm . . . . . . . . . . . . . 7-49
no MSC acknowledgement for circuit unblock DRI 237 alarm . . . . . . . . . . . . 17-305
BSS 6 alarm. . . . . . . . . . . . . . . 6-17 not operational
no MSC acknowledgement for global reset GCLK 18 alarm . . . . . . . . . . . . . 21-38
BSS 9 alarm. . . . . . . . . . . . . . . 6-25 number of calls queued
no MSC acknowledgement for reset circuit CELL 20, PM alarm . . . . . . . . . . . 12-51
BSS 7 alarm. . . . . . . . . . . . . . . 6-19 number of octets retransmitted
no NS-VC alive acknowledgement from the MTL 9, PM alarm . . . . . . . . . . . . 31-21
SGSN . . . . . . . . . . . . . . . . . . . 42-86 number of signal units in error
no NS-VC Block acknowledgement from the MTL 6, PM alarm . . . . . . . . . . . . 31-17
SGSN . . . . . . . . . . . . . . . . . . . 42-84 NVM board failure
SITE 30 alarm. . . . . . . . . . . . . . 42-75
OIC . . . . . . . . . . . . . . . . . . . . 1-12 OMC 30014 alarm

OMC 30000 alarm database exceeds upper limit . . . . . . 32-40
downloadFailed . . . . . . . . . . . . . 32-5 OMC 30015 alarm
OMC 30001 alarm pmProxyDisconnectedFromDB . . . . . 32-42
uploadFailed . . . . . . . . . . . . . . 32-8 OMC 30016 alarm
OMC 30002 alarm osiStackError . . . . . . . . . . . . . . 32-43
filexferFailed . . . . . . . . . . . . . . 32-11 OMC 30017 alarm
OMC 30004 alarm CSFPdownloadFailed . . . . . . . . . . 32-44
parserDisconnectedTooLong . . . . . . 32-17 OMC 30018 alarm
OMC 30005 alarm dbUncompressionFailed. . . . . . . . . 32-47
NE response timeout OMC 30019 alarm
NE response tmeout . . . . . . . . . 32-20 database exceeds lower limit . . . . . . 32-49
OMC 30006 alarm OMC 30020 alarm
NE error state . . . . . . . . . . . . . 32-23 VersionQueryFailed . . . . . . . . . . . 32-51
PMDisconnectedFromDB . . . . . . . . 32-26 OMC overloaded with events . . . . . . 32-57
EMDisconnectedFromDB . . . . . . . . 32-28 OMC overloaded, events discarded . . . 32-59
dbCompressionFailed . . . . . . . . . . 32-31 downloadDisabled. . . . . . . . . . . . 32-61
exceeds upper limit disk usage . . . . . 32-33 CSFPSwapFailed . . . . . . . . . . . . 32-63
exceeds lower limit disk usage . . . . . 32-36 nmcAgentError . . . . . . . . . . . . . 32-64
level 1/2/3 failure . . . . . . . . . . . . 32-38 supplDownloadFailed . . . . . . . . . . 32-69
IX-40 68P02901W26-S
Nov 2007
Index
OMC 30029 alarm OMC overloaded with events (contd.)

active alarms exceed upper limit of . . . 32-72 OMC 30021 alarm . . . . . . . . . . . 32-57
OMC 30030 alarm OMC overloaded, events discarded
received maximum corrupt NE msgs, closed OMC 30022 alarm . . . . . . . . . . . 32-59
OML . . . . . . . . . . . . . . . . . . 32-74 OMC-R map display modes
OMC 30031 alarm device mode. . . . . . . . . . . . . . . 1-19
resync timed out, no response from subscriber mode . . . . . . . . . . . . 1-19
NE . . . . . . . . . . . . . . . . . . . 32-78 OML 0, PM alarm
OMC 30032 alarm invalid received frames . . . . . . . . . 33-3
resync timed out, all resync events not OML 1, PM alarm
received. . . . . . . . . . . . . . . . . 32-81 FRMR-frames . . . . . . . . . . . . . . 33-5
OMC 30035 alarm OML 2, PM alarm
advisory detected . . . . . . . . . . . . 32-86 expiration of N2. . . . . . . . . . . . . 33-7
OMC 30036 alarm OML alarms
recovered outage detected . . . . . . . 32-87 introduction . . . . . . . . . . . . . . . 33-2
OMC 30037 alarm OOS device list . . . . . . . . . . . . . . 1-17
UPS condition . . . . . . . . . . . . . . 32-88 format. . . . . . . . . . . . . . . . . . 1-17
OMC 30050 alarm optocoupler 1
Solaris2 hardware failure . . . . . . . . 32-93 EAS 16 alarm . . . . . . . . . . . . . . 18-9
corrupt NE file . . . . . . . . . . . . . 32-96 EAS 25 alarm . . . . . . . . . . 18-9 to 18-10
corrupt SITE file . . . . . . . . . . . . 32-97 EAS 26 alarm . . . . . . . . . . . . . . 18-9
noActivityInTimeslot . . . . . 32-101, 32-103 EAS 27 alarm . . . . . . . . . . . . . . 18-9
CPU load exceeds lower limit . . . . . 32-102 EAS 28 alarm . . . . . . . . . . . . . . 18-9
Memory usage exceeds lower limit . . 32-104 EAS 29 alarm . . . . . . . . . . . . . . 18-9
Memory usage exceeds upper limit . . 32-106 EAS 30 alarm . . . . . . . . . . . . . . 18-9
Last MTL may have gone out of ser EAS 31 alarm . . . . . . . . . . . . . . 18-9
vice . . . . . . . . . . . . . . . . . . 32-107 optocoupler 2
OMC 30066 alarm EAS 17 alarm . . . . . . . . . . . . . . 18-9
Database unable to allocate frag optocoupler 3
ment . . . . . . . . . . . . . . . . . 32-108 EAS 18 alarm . . . . . . . . . . . . . . 18-9
No PM database fragment available . . 32-109 EAS 19 alarm . . . . . . . . . . . . . . 18-9
Maximum number of RTFs in MIB above 90% of EAS 20 alarm . . . . . . . . . . . . . . 18-9
licence limit . . . . . . . . . . . . . . 32-110 optocoupler 6
LicenseAuditNotAvailableAlarm. . . . 32-113 optocoupler 7
LicenseFileNotAvailableAlarm . . . . 32-114 optocoupler 8
LicenseViolationAlarm . . . . . . . . 32-115 optocoupler 9
invalidLicenseFileAlarm. . . . . . . . 32-116 osiStackError
OMC 3008 alarm, EMDisconnected OMC 30016 alarm . . . . . . . . . . . 32-43
FromDB . . . . . . . . . . . . . . . . . . 32-28 output failure
OMC 3033 alarm . . . . . . . . . . . . . 32-83 BCUP 8 alarm . . . . . . . . . . . . . . . 4-7
OMC alarm formats . . . . . . . . . . . . . 1-7 over 50% of board detected clock failure
OMC alarms CBUS 0 alarm . . . . . . . . . . . . . . 11-3
introduction . . . . . . . . . . . . . . . 32-4 over temperature warning
OMC overloaded with events BCUP 10 alarm . . . . . . . . . . . . . 4-11
68P02901W26-S IX-41
Nov 2007
Index
over-temperature - component damage imminent overview

CAGE 40 alarm . . . . . . . . . . . . . 9-17 alarms . . . . . . . . . . . . . . . . . . 1-3
paging request from MSC protocol error power amplifier temperature

BSS 0, PM alarm . . . . . . . . . . . . . 6-7 DRI 208 alarm . . . . . . . . . . . . 17-270
paging request from SMLC protocol error power amplifier temperature high
BSS 20, PM alarm. . . . . . . . . . . . 6-32 DRI 88 alarm . . . . . . . . . . . . . 17-153
parity highway 0 power amplifier temperature high but functioning
KSW 0 alarm . . . . . . . . . . . . . . 26-4 DRI 92 alarm . . . . . . . . . . . . . 17-162
parity highway 1 power feed A failure
KSW 1 alarm . . . . . . . . . . . . . . 26-8 COMB 7 alarm . . . . . . . . . . . . . 13-10
parity highway 2 power feed B failure
KSW 2 alarm . . . . . . . . . . . . . . 26-10 COMB 8 alarm . . . . . . . . . . . . . 13-12
parity highway 3 power mains failure
KSW 3 alarm . . . . . . . . . . . . . . 26-12 TRU 2 alarm . . . . . . . . . . . . . . 46-7
parserDisconnectedTooLong power supply failure
OMC 30004 alarm . . . . . . . . . . . 32-17 DRI 154 alarm . . . . . . . . . . . . 17-221
partial reset power supply temperature high
COMB 10 alarm . . . . . . . . . . . . . 13-17 IAS 101 alarm. . . . . . . . . . . . . 25-119
PBUS 254 alarm power supply unit - input failure
device failure . . . . . . . . . . . . . . 34-3 IAS 80 alarm . . . . . . . . . . . . . . 25-81
PBUS alarms power supply unit - output failure
introduction . . . . . . . . . . . . . . . 34-2 IAS 81 alarm . . . . . . . . . . . . . . 25-83
PCH queue page discard power supply unit 0 failure
CELL 24, PM alarm . . . . . . . . . . . 12-57 IAS 1 alarm . . . . . . . . . . . . . . . 25-10
PCMCIA card removed power supply unit 1 failure
CSFP 240 alarm. . . . . . . . . . . . . 14-13 IAS 9 alarm . . . . . . . . . . . . . . . 25-12
PCU 0 alarm power supply unit 2 failure
last GSL failed . . . . . . . . . . . . . 35-3 IAS 10 alarm . . . . . . . . . . . . . . 25-14
PCU 1 alarm power supply unit 3 failure
PCU audit failure . . . . . . . . . . . . 35-5 IAS 11 alarm . . . . . . . . . . . . . . 25-16
PCU alarms power supply unit failure
introduction . . . . . . . . . . . . . . . 35-2 TRU 1 alarm . . . . . . . . . . . . . . 46-5
PCU audit failure power supply unit#1 fan failure
PCU 1 alarm . . . . . . . . . . . . . . 35-5 CAGE 34 alarm . . . . . . . . . . . . . 9-13
Performance Management (PM) alarms . . . 1-2 power supply unit#1 over-temperature
persistent fault . . . . . . . . . . . . . . 17-67 CAGE 37 alarm . . . . . . . . . . . . . 9-15
phase lock failure power supply unit#1not detected
GCLK 14 alarm . . . . . . . . . . . . . 21-28 CAGE 31 alarm . . . . . . . . . . . . . 9-11
phase lock lost power supply unit#1output failure
GCLK 4 alarm . . . . . . . . . . . . . . 21-9 CAGE 28 alarm . . . . . . . . . . . . . . 9-9
PMDisconnectedFromDB power supply unit#2 fan failure
OMC 30007 alarm . . . . . . . . . . . 32-26 CAGE 35 alarm . . . . . . . . . . . . . 9-13
pmProxyDisconnectedFromDB power supply unit#2 not detected
OMC 30015 alarm . . . . . . . . . . . 32-42 CAGE 32 alarm . . . . . . . . . . . . . 9-11
power amplier error power supply unit#2 output failure
DRI 73 alarm . . . . . . . . . . . . . 17-127 CAGE 29 alarm . . . . . . . . . . . . . . 9-9
power amplifier communication failure power supply unit#2 over-temperature
DRI 89 alarm . . . . . . . . . . . . . 17-156 CAGE 38 alarm . . . . . . . . . . . . . 9-15
power amplifier failure power supply unit#3 fan failure
DRI 215 alarm . . . . . . . . . . . . 17-282 CAGE 36 alarm . . . . . . . . . . . . . 9-13
power amplifier power low but functioning power supply unit#3 not detected
DRI 91 alarm . . . . . . . . . . . . . 17-160
IX-42 68P02901W26-S
Nov 2007
Index
power supply unit#3 not detected (contd.) processor bus communication failure (contd.)
CAGE 33 alarm . . . . . . . . . . . . . 9-11 BSP 232 alarm . . . . . . . . . . . . . 5-43
power supply unit#3 output failure BTP 232 alarm . . . . . . . . . . . . . 7-40
CAGE 30 alarm . . . . . . . . . . . . . . 9-9 DHP 232 alarm . . . . . . . . . . . . . 15-57
power supply unit#3 over-temperature GCLK 232 alarm . . . . . . . . . . . . 21-52
CAGE 39 alarm . . . . . . . . . . . . . 9-15 GPROC 232 alarm. . . . . . . . . . . . 23-50
primary alarm. . . . . . . . . . . . . . . . 1-5 KSW 232 alarm . . . . . . . . . . . . . 26-60
primary message or hardware interrupt error MSI 232 alarm . . . . . . . . . . . . . 30-28
DRI 18 alarm . . . . . . . . . . . . . . 17-36 processor communication failure
process safe test audit failure DPROC 0 alarm . . . . . . . . . . . . . 16-3
BSP 239 alarm . . . . . . . . . . . . . 5-44 processor failure
BTP 239 alarm . . . . . . . . . . . . . 7-51 DRI 29 alarm . . . . . . . . . . . . . . 17-57
DHP 239 alarm . . . . . . . . . . . . . 15-61 PSP 0 alarm, Communication Failure . . . 39-3
DPROC 239 alarm. . . . . . . . . . . . 16-11 PSP 22 alarm
DRI 239 alarm . . . . . . . . . . . . 17-307 SWFM indication . . . . . . . . . . . . 39-5
GPROC 239 alarm. . . . . . . . . . . . 23-51 PSP 239 alarm
PSP 239 alarm . . . . . . . . . . . . . 39-8 process safe test audit failure . . . . . . 39-8
processor A failure PSP 39 alarm
COMB 14 alarm . . . . . . . . . . . . . 13-27 software failure . . . . . . . . . . . . . 39-6
processor B failure PSP alarms
COMB 15 alarm . . . . . . . . . . . . . 13-29 FRUs . . . . . . . . . . . . . . . . . . 39-2
processor bus communication failure introduction . . . . . . . . . . . . . . . 39-2
Q3 agent . . . . . . . . . . . . . . . . . . 1-7
radio frequency losses while using a TCH received maximum corrupt NE msgs, closed OML
TIMESLOT 0, PM alarm. . . . . . . . . 45-3 OMC 30030 alarm . . . . . . . . . . . 32-74
radio frequency losses while using an SDCCH received page for invalid cell from MSC
CELL 0, PM alarm . . . . . . . . . . . 12-6 BSS 26 alarm . . . . . . . . . . . . . . 6-38
radio subsystem software to DRI communication received page for invalid cell from SMLC
error received page for invalid cell from SMLC
DRI 76 alarm . . . . . . . . . . . . . 17-132 MSC . . . . . . . . . . . . . . . . . . 6-69
radio subsystem software to DRI communication receiver failure
error - checksum error DRI 119 alarm . . . . . . . . . . . . 17-182
DRI 65 alarm . . . . . . . . . . . . . 17-113 DRI 120 alarm . . . . . . . . . . . . 17-184
radio subsystem software to DRI communication DRI 121 alarm . . . . . . . . . . . . 17-186
failure DRI 122 alarm . . . . . . . . . . . . 17-188
DRI 22 alarm . . . . . . . . . . . . . . 17-43 DRI 123 alarm . . . . . . . . . . . . 17-190
RCU #5 circuit breaker failure DRI 125 alarm . . . . . . . . . . . . 17-194
IAS 61 alarm . . . . . . . . . . . . . . 25-67 DRI 126 alarm . . . . . . . . . . . . 17-196
re-initialized unexpectedly DRI 127 alarm . . . . . . . . . . . . 17-198
KSW 7 alarm . . . . . . . . . . . . . . 26-27 DRI 128 alarm . . . . . . . . . . . . 17-200
MSI 0 alarm. . . . . . . . . . . . . . . 30-3 DRI 72 alarm . . . . . . . . . . . . . 17-125
receive matrix branch 2 control link failure receiver input overflowed
DRI 162 alarm . . . . . . . . . . . . 17-237 DRI 157 alarm . . . . . . . . . . . . 17-227
receive matrix failure DRI 158 alarm . . . . . . . . . . . . 17-229
DRI 150 alarm . . . . . . . . . . . . 17-213 receiver synthesizer failure
DRI 112 alarm . . . . . . . . . . . . 17-168
68P02901W26-S IX-43
Nov 2007
Index
receiver synthesizer failure (contd.) remote KSW loopback test failure

DRI 113 alarm . . . . . . . . . . . . 17-170 TBUS 0 alarm . . . . . . . . . . . . . . 43-3
DRI 114 alarm . . . . . . . . . . . . 17-172 remote KSWX slot 2 communication failure
DRI 115 alarm . . . . . . . . . . . . 17-174 4. CAGE alarm . . . . . . . . . . . 9-22, 9-34
DRI 116 alarm . . . . . . . . . . . . 17-176 remote KSWX TDM error
DRI 117 alarm . . . . . . . . . . . . 17-178 TBUS 4 alarm . . . . . . . . . . . . . . 43-7
DRI 118 alarm . . . . . . . . . . . . 17-180 reset due to recurring fault
reconfiguration DRI 35 alarm . . . . . . . . . . . . . . 17-67
information . . . . . . . . . . . . . . . 1-13 reset, site requested alarm
recovered outage detected Process Identifier (PID) numbers
OMC 30036 alarm . . . . . . . . . . . 32-87 list of . . . . . . . . . . . . . . . . . 42-62
rectifier failure . . . . . . . . . . . . . 25-143 resync timed out, all resync events not received
IAS 106 alarm. . . . . . . . . . . . . 25-129 OMC 30032 alarm . . . . . . . . . . . 32-81
recurring fault . . . . . . . . . . . . . . 17-67 resync timed out, no response from NE
red alarm daily threshold exceeded OMC 30031 alarm . . . . . . . . . . . 32-78
MMS 20 alarm . . . . . . . . . . . . . 29-37 routing failure - reason unknown
red alarm hourly threshold exceeded BSS 2, PM alarm . . . . . . . . . . . . 6-12
MMS 21 alarm . . . . . . . . . . . . . 29-39 routing failure - syntax error detected
red alarm OOS threshold exceeded BSS 18, PM alarm. . . . . . . . . . . . 6-31
MMS 22 alarm . . . . . . . . . . . . . 29-41 BSS1, PM alarm
red alarm OOS timer expired BSS 1, PM alarm . . . . . . . . . . . . 6-9
MMS 23 alarm . . . . . . . . . . . . . 29-44 RSL 0, PM alarm
reference count overflow 125 us invalid received frames . . . . . . . . . 40-3
GCLK 5 alarm . . . . . . . . . . . . . . 21-13 RSL 1, PM alarm
reference count overflow 6.12s FRMR-frames . . . . . . . . . . . . . . 40-5
GCLK 7 alarm . . . . . . . . . . . . . . 21-17 RSL 10 alarm
reference count overflow 60ms link disconnected . . . . . . . . . . . . 40-9
reference distribution module failure LAPD protocol error . . . . . . . . . . 40-18
remote alarm daily threshold exceeded LAPD protocol error threshold e
MMS 4 alarm . . . . . . . . . . . . . . 29-12 xceeded . . . . . . . . . . . . . . . . . 40-22
remote alarm hourly threshold exceeded RSL 14 alarm
MMS 5 alarm . . . . . . . . . . . . . . 29-14 link audit failure . . . . . . . . . . . . 40-25
remote alarm OOS threshold exceeded RSL 2, PM alarm
MMS 6 alarm . . . . . . . . . . . . . . 29-16 expiration of N2. . . . . . . . . . . . . 40-7
remote alarm OOS timer expired RSL alarms
MMS 18 alarm . . . . . . . . . . . . . 29-34 introduction . . . . . . . . . . . . . . . 40-2
safe test audit failure serial bus connection failure (contd.)

DRI 224 alarm . . . . . . . . . . . . 17-293 IAS 1 alarm . . . . . . . . . . . . . . . 25-7
KSW 224 alarm . . . . . . . . . . . . . 26-54 signalling link failure
MSI 224 alarm . . . . . . . . . . . . . 30-24 LMTL 0 alarm . . . . . . . . . . . . . . 28-3
SBUS 254 alarm MTL 0 alarm . . . . . . . . . . . . . . 31-3
device failure . . . . . . . . . . . . . . 41-3 SITE 0 alarm
SBUS alarms last RSL link failure . . . . . . . . . . . 42-4
introduction . . . . . . . . . . . . . . . 41-2 SITE 10 alarm
second reference loss 6.12s standby local FOX failure . . . . . . . . 42-30
KSW 6 alarm . . . . . . . . . . . . . . 26-24 SITE 11 alarm
secondary . . . . . . . . . . . . . . . . . 1-14 active remote FOX 0 failure . . . . . . . 42-32
secondary alarms . . . . . . . . . . . . . . 1-5 SITE 12 alarm
serial bus connection failure standby remote FOX 0 failure . . . . . . 42-34
BCUP 1 alarm . . . . . . . . . . . . . . . 4-5 SITE 13 alarm
EAS 1 alarm. . . . . . . . . . . . . . . 18-5
IX-44 68P02901W26-S
Nov 2007
Index
SITE 13 alarm (contd.) SITE 7 alarm

active remote FOX 1 failure . . . . . . . 42-36 active multiplexer 2 loopback failure . . 42-23
SITE 14 alarm SITE 8 alarm
standby remote FOX 1 failure . . . . . . 42-38 standby multiplexer 2 loopback fail
SITE 15 alarm ure . . . . . . . . . . . . . . . . . . . 42-26
active remote FOX 2 failure . . . . . . . 42-40 SITE 9 alarm
SITE 16 alarm active local FOX failure . . . . . . . . . 42-28
standby remote FOX 2 failure . . . . . . 42-42 SITE alarms
SITE 17 alarm introduction . . . . . . . . . . . . . . . 42-3
16Kbps switching hardware re site reset occurred due to front panel reset
quired . . . . . . . . . . . . . . . . . . 42-44 BTP 42 alarm . . . . . . . . . . . . . . 7-32
SITE 19 alarm GPROC 42 alarm . . . . . . . . . . . . 23-38
unequipped GPROC has entered the site reset request
LAN . . . . . . . . . . . . . . . . . . . 42-47 SITE 24 alarm. . . . . . . . . . . . . . 42-61
SITE 2 alarm site reset requested
BSC detected MCU to MCU communication Process Identifier (PID) numbers
failure . . . . . . . . . . . . . . . . . . 42-12 list of . . . . . . . . . . . . . . . . . 42-62
SITE 20 alarm SL alignment failure
unequipped GPROC has left the LAN . . 42-51 LMTL 5, PM alarm . . . . . . . . . . . 28-20
SITE 21 alarm MTL 5, PM alarm . . . . . . . . . . . . 31-15
no clock references available . . . . . . 42-55 SL congestion events resulting in loss of MSUs
SITE 22 alarm LMTL 11, PM alarm . . . . . . . . . . . 28-30
active alarm list full . . . . . . . . . . . 42-58 MTL 11, PM alarm . . . . . . . . . . . 31-23
SITE 24 alarm SL congestion indications
site reset request . . . . . . . . . . . . 42-61 LMTL 12, PM alarm . . . . . . . . . . . 28-32
SITE 25 alarm MTL 12, PM alarm . . . . . . . . . . . 31-24
external power booster amplifier 1 SL failure - abnormal FIBR/BSNR
failure . . . . . . . . . . . . . . . . . . 42-64 LMTL 1, PM alarm . . . . . . . . . . . 28-10
external power booster amplifier 2 SL failure - all reasons
failure . . . . . . . . . . . . . . . . . . 42-66 LMTL 0, PM alarm . . . . . . . . . . . 28-6
external power booster failure . . . . . 42-68 SL failure - excessive delay of ACK
database configuration and Arena hardware SL failure - excessive duration of congestion
mismatch . . . . . . . . . . . . 42-70, 42-73 LMTL 4, PM alarm . . . . . . . . . . . 28-18
active multiplexer 0 loopback failure . . 42-15 SL failure - excessive error rate
NVM board failure . . . . . . . . . . . 42-75 SL number of negative acks received
failure of PCMCIA Card 1 on NVM slave HDSL modem
board . . . . . . . . . . . . . . . . . . 42-77 MMS 38 alarm . . . . . . . . . . . . . 29-84
SITE 36 alarm, Erroneous Network Service slave HDSL modem loop 0 SNR daily threshold
Message Received... exceeded
SITE: Erroneous Network Service Message MMS 29 alarm . . . . . . . . . . . . . 29-60
Received... . . . . . . . . . . . . . . . 42-83 slave HDSL modem loop 0 SNR hourly threshold
SITE 4 alarm exceeded
standby multiplexer 0 loopback fail MMS 33 alarm . . . . . . . . . . . . . 29-68
ure . . . . . . . . . . . . . . . . . . . 42-17 slave HDSL modem loop 0 SNR OOS threshold
SITE 42 alarm, Last PRP or PXP Failed . . 42-92 exceeded
SITE 5 alarm MMS 37 alarm . . . . . . . . . . . . . 29-80
active multiplexer 1 loopback failure . . 42-19 slave HDSL modem loop 1 SNR daily threshold
SITE 6 alarm exceeded
standby multiplexer 1 loopback fail MMS 30 alarm . . . . . . . . . . . . . 29-62
ure . . . . . . . . . . . . . . . . . . . 42-21
68P02901W26-S IX-45
Nov 2007
Index
slave HDSL modem loop 1 SNR hourly threshold superframe counter error
exceeded DRI 6 alarm . . . . . . . . . . . . . . . 17-18
MMS 34 alarm . . . . . . . . . . . . . 29-70 DRI 66 alarm . . . . . . . . . . . . . 17-116
slow flash failure supplDownloadFailed
BTP 236 alarm . . . . . . . . . . . . . 7-47 OMC 30027 alarm . . . . . . . . . . . 32-69
DRI 236 alarm . . . . . . . . . . . . 17-303 SWFM indication
SMLC processor outage BSP 22 alarm . . . . . . . . . . . . . . 5-13
LMTL 1 alarm . . . . . . . . . . . . . . 28-8 BTP 22 alarm . . . . . . . . . . . . . . 7-13
smoke alarm CSFP 22 alarm . . . . . . . . . . . . . 14-3
IAS 92 alarm . . . . . . . . . . . . . 25-101 DHP 22 alarm . . . . . . . . . . . . . . 15-12
software failure DPROC 22 alarm . . . . . . . . . . . . 16-7
BSP 39 alarm . . . . . . . . . . . . . . 5-28 GPROC 22 alarm . . . . . . . . . . . . 23-14
BTP 39 alarm . . . . . . . . . . . . . . 7-28 PSP 22 alarm . . . . . . . . . . . . . . 39-5
DHP 39 alarm . . . . . . . . . . . . . . 15-39 switching hardware required kb/s
DPROC 39 alarm . . . . . . . . . . . . 16-8 switching hardware required 16kb/s . . 42-44
GPROC 39 alarm . . . . . . . . . . . . 23-34 SYNC calibration request
PSP 39 alarm . . . . . . . . . . . . . . 39-6 DHP 26 alarm . . . . . . . . . . . . . . 15-19
Solaris2 hardware failure GPROC 26 alarm . . . . . . . . . . . . 23-18
OMC 30050 alarm . . . . . . . . . . . 32-93 SYNC clock output failure
spare fuse failure DHP 28 alarm . . . . . . . . . . . . . . 15-23
IAS 30 alarm . . . . . . . . . . . . . . 25-40 GPROC 28 alarm . . . . . . . . . . . . 23-20
spurious GSM timeslot interrupt SYNC invalid mode
DRI 50 alarm . . . . . . . . . . . . . . 17-82 DHP 46 alarm . . . . . . . . . . . . . . 15-48
spurious interrupt SYNC lost phase lock to master GCLK
BSP 40 alarm . . . . . . . . . . . . . . 5-30 DHP 23 alarm . . . . . . . . . . . . . . 15-13
BTP 40 alarm . . . . . . . . . . . . . . 7-30 GPROC 23 alarm . . . . . . . . . . . . 23-15
DHP 40 alarm . . . . . . . . . . . . . . 15-41 SYNC not operational
GPROC 40 alarm . . . . . . . . . . . . 23-36 DHP 43 alarm . . . . . . . . . . . . . . 15-43
standby link connected to wrong device SYNC phase lock failure
DRI 241 alarm . . . . . . . . . . . . 17-310 DHP 45 alarm . . . . . . . . . . . . . . 15-46
standby link connection failure SYNC shutdown request
BTP 235 alarm . . . . . . . . . . . . . 7-44 DHP 27 alarm . . . . . . . . . . . . . . 15-21
DRI 235 alarm . . . . . . . . . . . . 17-301 GCLK 17 alarm . . . . . . . . . . . . . 21-36
standby local FOX failure GPROC 27 alarm . . . . . . . . . . . . 23-19
SITE 10 alarm. . . . . . . . . . . . . . 42-30 SYNC warm up failure
standby multiplexer 0 loopback failure GPROC 25 alarm . . . . . . . . . . . . 23-17
SITE 4 alarm . . . . . . . . . . . . . . 42-17 SYNC warmup failure
standby multiplexer 1 loopback failure DHP 25 alarm . . . . . . . . . . . . . . 15-17
SITE 6 alarm . . . . . . . . . . . . . . 42-21 SYNC watchdog timer expired
standby multiplexer 2 loopback failure DHP 29 alarm . . . . . . . . . . . . . . 15-25
SITE 8 alarm . . . . . . . . . . . . . . 42-26 GPROC 29 alarm . . . . . . . . . . . . 23-21
standby remote FOX 0 failure synchronization loss daily threshold exceeded
SITE 12 alarm. . . . . . . . . . . . . . 42-34 MMS 0 alarm . . . . . . . . . . . . . . 29-5
standby remote FOX 1 failure synchronization loss hourly threshold exceeded
standby remote FOX 2 failure synchronization loss OOS threshold exceeded
start of remote processor outage synchronization loss OOS timer expired
MTL 8, PM alarm . . . . . . . . . . . . 31-20 MMS 16 alarm . . . . . . . . . . . . . 29-31
state change warning alarms . . . . . . . . 1-7 synchronization loss with MCU
super frame counter error DRI 39 alarm . . . . . . . . . . . . . . 17-73
DRI 5 alarm . . . . . . . . . . . . . . . 17-16
tagged alarm format . . . . . . . . . . . . 1-6
IX-46 68P02901W26-S
Nov 2007
Index
TBUS 0 alarm transceiver synthesizer failure

remote KSW loopback test failure. . . . 43-3 DRI 80 alarm . . . . . . . . . . . . . 17-135
TBUS 3 alarm transceiver to combiner communication failure
local KSWX TDM error . . . . . . . . . 43-5 DRI 151 alarm . . . . . . . . . . . . 17-215
TBUS 4 alarm transceiver to DRI burst error
remote KSWX TDM error . . . . . . . . 43-7 DRI 59 alarm . . . . . . . . . . . . . 17-101
TBUS alarms DRI 60 alarm . . . . . . . . . . . . . 17-103
introduction . . . . . . . . . . . . . . . 43-2 transceiver to DRI communication error
TCH pre-emption failure DRI 58 alarm . . . . . . . . . . . . . . 17-99
CELL 28, PM alarm . . . . . . . . . . . 12-61 DRI 61 alarm . . . . . . . . . . . . . 17-105
TDM alarms DRI 62 alarm . . . . . . . . . . . . . 17-107
introduction . . . . . . . . . . . . . . . 44-2 DRI 63 alarm . . . . . . . . . . . . . 17-109
TDM interface configuration failure transceiver to DRI communication failure
BSP 231 alarm . . . . . . . . . . . . . 5-41 DRI 144 alarm . . . . . . . . . . . . 17-202
BTP 231 alarm . . . . . . . . . . . . . 7-38 DRI 147 alarm . . . . . . . . . . . . 17-207
DHP 231 alarm . . . . . . . . . . . . . 15-55 DRI 148 alarm . . . . . . . . . . . . 17-209
DRI 231 alarm . . . . . . . . . . . . 17-296 DRI 149 alarm . . . . . . . . . . . . 17-211
GPROC 231 alarm. . . . . . . . . . . . 23-48 DRI 155 alarm . . . . . . . . . . . . 17-223
MSI 231 alarm . . . . . . . . . . . . . 30-26 DRI 163 alarm . . . . . . . . . . . . 17-239
TDM interface failure - assigned timeslot counter DRI 164 alarm . . . . . . . . . . . . 17-241
overflow DRI 165 alarm . . . . . . . . . . . . 17-243
BSP 33 alarm . . . . . . . . . . . . . . 5-22 DRI 169 alarm . . . . . . . . . . . . 17-251
BTP 33 alarm . . . . . . . . . . . . . . 7-22 DRI 57 alarm . . . . . . . . . . . . . . 17-97
DHP 33 alarm . . . . . . . . . . . . . . 15-33 Transceiver to DRI Communication Failure
DRI 25 alarm . . . . . . . . . . . . . . 17-49 169. DRI . . . . . . . . . . . . . . . 17-251
GPROC 33 alarm . . . . . . . . . . . . 23-28 transceiver to DRI communications failure
TDM interface failure - assigned timeslot counter DRI 146 alarm . . . . . . . . . . . . 17-205
underflow transmission suspended to conserve battery
BSP 32 alarm . . . . . . . . . . . . . . 5-20 power
BTP 32 alarm . . . . . . . . . . . . . . 7-20 DRI 217 alarm . . . . . . . . . . . . 17-286
DHP 32 alarm . . . . . . . . . . . . . . 15-31 transmitter failure - output power
DRI 26 alarm . . . . . . . . . . . . . . 17-51 DRI 85 alarm . . . . . . . . . . . . . 17-147
GPROC 32 alarm . . . . . . . . . . . . 23-26 DRI 86 alarm . . . . . . . . . . . . . 17-149
TDM interface failure - TDM parity error DRI 87 alarm . . . . . . . . . . . . . 17-151
BSP 34 alarm . . . . . . . . . . . . . . 5-24 DRI 90 alarm . . . . . . . . . . . . . 17-158
BTP 34 alarm . . . . . . . . . . . . . . 7-24 DRI 93 alarm . . . . . . . . . . . . . 17-164
DHP 34 alarm . . . . . . . . . . . . . . 15-35 transmitter out of synchronization
GPROC 34 alarm . . . . . . . . . . . . 23-30 transmitter synthesizer failure
TDM parity error DRI 81 alarm . . . . . . . . . . . . . 17-138
MSI 7 alarm. . . . . . . . . . . . . . . 30-17 DRI 82 alarm . . . . . . . . . . . . . 17-141
TIMESLOT 0, PM alarm DRI 83 alarm . . . . . . . . . . . . . 17-143
radio frequency losses while using a DRI 84 alarm . . . . . . . . . . . . . 17-145
TCH . . . . . . . . . . . . . . . . . . . 45-3 TRAU frame synchronization loss
TIMESLOT 1, PM alarm MSI 9 alarm. . . . . . . . . . . . . . . 30-19
channel request from MS failed . . . . . 45-4 TRU 0 alarm
TIMESLOT alarms door open . . . . . . . . . . . . . . . . 46-3
introduction . . . . . . . . . . . . . . . 45-2 TRU 1 alarm
Too many LAPD protocol errors power supply unit failure . . . . . . . . 46-5
GSL 15 alarm . . . . . . . . . . . . . . 24-17 TRU 2 alarm
XBL 15 alarm . . . . . . . . . . . . . . 47-17 power mains failure . . . . . . . . . . . 46-7
transceiver processor failure TRU alarms
DRI 213 alarm . . . . . . . . . . . . 17-278 introduction . . . . . . . . . . . . . . . 46-2
transceiver re-initialized unexpectedly trunk critical threshold exceeded
DRI 30 alarm . . . . . . . . . . . . . . 17-59 BSS 22 alarm . . . . . . . . . . . . . . 6-34
transceiver recovery failure trunk major threshold exceeded
DRI 216 alarm . . . . . . . . . . . . 17-284 BSS 21 alarm . . . . . . . . . . . . . . 6-33
68P02901W26-S IX-47
Nov 2007
Index
TX VSWR antenna fault

DRI 78 alarm . . . . . . . . . . . . . 17-134
unequipped circuit at the BSS unexpected communications bus interrupt

BSS 12 alarm . . . . . . . . . . . . . . 6-28 DRI 71 alarm . . . . . . . . . . . . . 17-123
unequipped circuit at the MSC unlocked device not in service
BSS 8 alarm. . . . . . . . . . . . . . . 6-23 DRI 243 alarm . . . . . . . . . . . . 17-313
unequipped GPROC has entered the LAN unrecognized hardware revision level
SITE 19 alarm. . . . . . . . . . . . . . 42-47 GCLK 12 alarm . . . . . . . . . . . . . 21-27
unequipped GPROC has left the LAN unrecoverable error
SITE 20 alarm. . . . . . . . . . . . . . 42-51 DRI 64 alarm . . . . . . . . . . . . . 17-111
unexpected board type untagged alarm format . . . . . . . . . . . 1-4
BCUP 0 alarm . . . . . . . . . . . . . . . 4-3 uploadFailed
EAS 0 alarm. . . . . . . . . . . . . . . 18-3 OMC 30001 alarm . . . . . . . . . . . 32-8
IAS 0 alarm . . . . . . . . . . . . . . . 25-5 UPS condition
Unexpected board type OMC 30037 alarm . . . . . . . . . . . 32-88
BSP 47 alarm . . . . . . . . . . . . . . 5-32 urgent critical alarm
BTP 47 alarm . . . . . . . . . . . . . . 7-33 IAS 110 alarm. . . . . . . . . . . . . 25-136
DHP 47 alarm . . . . . . . . . . . . . . 15-50
VersionQueryFailed voltage standing wave ratio performance low

OMC 30020 alarm . . . . . . . . . . . 32-51 IAS 91 alarm . . . . . . . . . . . . . . 25-99
warmup failure watchdog timer expired (contd.)

GCLK 19 alarm . . . . . . . . . . . . . 21-40 KSW 9 alarm . . . . . . . . . . . . . . 26-33
watchdog timer expired MSI 2 alarm. . . . . . . . . . . . . . . 30-7
GCLK 15 alarm . . . . . . . . . . . . . 21-32
x25CircuitDown XBL 13 alarm (contd.)

OMC 30003 alarm . . . . . . . . . . . 32-14 LAPD protocol error threshold e
XBL 0, PM alarm xceeded . . . . . . . . . . . . . . . . . 47-14
invalid received frames . . . . . . . . . 47-3 XBL 15 alarm
XBL 1, PM alarm Too many LAPD protocol errors . . . . . 47-17
FRMR-frames . . . . . . . . . . . . . . 47-5 XBL 16 alarm
XBL 10 alarm HDLC channel open failed . . . . . . . 47-18
link disconnected . . . . . . . . . . . . 47-9 XBL 2, PM alarm
XBL 11 alarm expiration of N2. . . . . . . . . . . . . 47-7
LAPD protocol error . . . . . . . . . . 47-12 XBL alarms
XBL 13 alarm introduction . . . . . . . . . . . . . . . 47-2
XCDR alarms . . . . . . . . . . . . . . . 30-2
IX-48 68P02901W26-S
Nov 2007
Standard Printing Instructions
Part Number 68P02901W26-S
Manual Title Maintenance Information: Alarm handling at the OMC-R
Date Nov 2007
A4 Ring Bound - GSD (UK)
Binder • 4 D-ring binder - A4 size (210mm x 297mm) white PVC.

• 40mm or 65mm capacity depending on the size of the manual.
• Clear pockets on front and spine.
Printing • Cover / spine text printed in colour.

• Body- printed double sided onto white A4 (210mm x 297mm) 80g
4 hole paper.
Finishing • A4 size (210mm x 297mm) clear PVC sheet front page for
protection.
• Bag wrapped with clear polythene.
If this is to be used by manufacturing as an Inbox document, then refer to appropriate

Materials or Methods Specification.
Maintenance Information
Alarm Handling at the OMC-R
Alarm Handling at the OMC-R
Maintenance Information
GSR9
NOV 2007
68P02901W26-S
GSR9
NOV 2007
68P02901W26-S
Cutting
datum point
Spine Front cover

Moto68P02901W26 Alarm

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Moto68P02901W26 Alarm

Uploaded by

Copyright:

Available Formats

Maintenance Information: Alarm

Handling at the OMC-R

68P02901W26-S Nov 2007

© 1994 - 2007 Motorola, Inc. All Rights Reserved

Maintenance Information: Alarm Handling at the OMC-R

Chapter 1: Introduction to Alarm Handling

Chapter 2: ABSS Alarms

Chapter 3: AXCDR Alarms

Chapter 4: BCUP Alarms

10. BCUP: Over temperature warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Chapter 5: BSP Alarms

Chapter 6: BSS Alarms

40. BSS: Circuit fault cleared on radio channel . . . . . . . . . . . . . . . . . . . . . . . . . 6-41

Chapter 7: BTP Alarms

Chapter 8: CAB Alarms

Chapter 9: CAGE Alarms

Chapter 10: CBL Alarms

Chapter 11: CBUS Alarms

Chapter 12: CELL Alarms

Chapter 13: COMB Alarms

Chapter 14: CSFP Alarms

Chapter 15: DHP Alarms

30. DHP: Clock A signal loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-27

Chapter 16: DPROC Alarms

Chapter 17: DRI Alarms

29. DRI: Processor failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57

116. DRI: Receiver synthesizer failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-176

218. DRI: Invalid transceiver calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . 17-288

Chapter 18: EAS Alarms

Chapter 19: ETH Alarms

Chapter 20: GBL Alarms

Chapter 21: GCLK Alarms

21. GCLK: Calibration in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-44

Chapter 22: GDS Alarms

Chapter 23: GPROC Alarms

Chapter 24: GSL Alarms

11. GSL: LAPD protocol error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-13

Chapter 25: IAS Alarms

96. IAS: No redundant connection to alarms board - Connection broken . . . . . . . . . . . . 25-109

Chapter 26: KSW Alarms

Chapter 27: LAN Alarms

Chapter 28: LMTL Alarms

3. LMTL: Threshold reached: SL failure - excessive error rate - PM . . . . . . . . . . . . . . . 28-16

Chapter 29: MMS Alarms

Chapter 30: MSI Alarms

1. MSI: Hard reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-5

Chapter 31: MTL Alarms

Chapter 32: OMC-R Alarms

30020. OMC: Version query failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-51

Chapter 33: OML Alarms

Chapter 34: PBUS Alarms

Chapter 35: PCU Alarms

51. PCU: Software patch installation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-8

Chapter 36: PPB Alarms

Chapter 37: PPROC alarms

Chapter 38: PSI Alarms

Chapter 39: PSP Alarms

Chapter 40: RSL Alarms

2. RSL: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40-7

Chapter 41: SBUS Alarms

Chapter 42: SITE Alarms

Chapter 43: TBUS Alarms

Chapter 44: TDM Alarms

Chapter 45: TIMESLOT Alarms