Alarms

Maintenance Information: Alarm Handling at the OMC-R
1994-2004 Motorola, Inc. All Rights Reserved
CONTROLLED INTRODUCTION
68P02901W26-Q 24 May 2004
Copyrights The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced 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, except for the rights that arise by operation of law in the sale of a product. Restrictions The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright 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. Accuracy While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola 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 does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others. Trademarks Motorola and the Motorola logo are registered trademarks of Motorola Inc. Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
24 May 2004
Table of Contents
Contents

Issue status of this manual General information . . . Reporting safety issues . Warnings and cautions . . General warnings . . . . General cautions . . . . Devices sensitive to static Motorola manual set . . . GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 7 8 10 14 15 16 17
Chapter 1: Introduction to alarm handling

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

0. ABSS: Last XBL Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. ABSS: RXCDR Detecting CIC Validation Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 2. ABSS: Circuit Configuration Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 2-4 2-6
Chapter 3: AXCDR alarms

Introduction to AXCDR alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. AXCDR: BSC Detecting CIC Validation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. AXCDR: AXCDR ID Mismatch with RXCDR Network Entity ID . . . . . . . . . . . . . . . . . . . 3-2 3-3 3-4
Chapter 4: BCUP alarms

Introduction to BCUP alarms. . . . . . 0. BCUP: Unexpected Board Type . . . 1. BCUP: Serial Bus Connection Failure 8. BCUP: Output Failure. . . . . . . . 68P02901W26-Q 24 May 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4-3 4-4 4-5
i
Contents
9. BCUP: Input Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10. BCUP: Over Temperature Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6 4-7
Chapter 5: BSP alarms

Introduction to BSP alarms. . . . . . . . . . . . . . . . . . . . . . . 1. BSP: EEPROM Flash Failure - No Valid Bootstrap Code Detected . . . 8. BSP: EEPROM Flash Object Failure . . . . . . . . . . . . . . . . . 17. BSP: EEPROM Flash Programming Failure . . . . . . . . . . . . . 21. BSP: EEPROM Flash Programming Failure . . . . . . . . . . . . . 22. BSP: SWFM Indication . . . . . . . . . . . . . . . . . . . . . . 30. BSP: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . . . 31. BSP: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . . . 32. BSP: TDM Interface Failure - Assigned Timeslot Counter Underflow . 33. BSP: TDM Interface Failure - Assigned Timeslot Counter Overflow . 34. BSP: TDM Interface Failure - TDM Parity Error . . . . . . . . . . . 35. BSP: LAN Connection Failure . . . . . . . . . . . . . . . . . . . 39. BSP: Software Failure . . . . . . . . . . . . . . . . . . . . . . . 40. BSP: Spurious Interrupt . . . . . . . . . . . . . . . . . . . . . . 47. BSP: Unexpected Board Type: GPROC2 or GPROC3 expected. . . . 48. BSP: Memory location is corrupt. Replace GPROC board. . . . . . . 50. BSP: EEPROM SW Flash Programming Failure. . . . . . . . . . . 51. BSP: EEPROM HW Flash Programming Failure. . . . . . . . . . . 231. BSP: TDM Interface Configuration Failure. . . . . . . . . . . . . 239. BSP: Process Safe Test Audit Failure . . . . . . . . . . . . . . . 254. BSP: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 5-4 5-6 5-8 5-9 5-10 5-11 5-13 5-15 5-17 5-19 5-21 5-23 5-25 5-27 5-29 5-30 5-31 5-32 5-34 5-36
Chapter 6: BSS alarms

Introduction to BSS alarms. . . . . . . . . . . . . . . . . . . . . 0. BSS: Last MTL Link Failure - Signalling Point Inaccessible . . . . 0. BSS: Paging Request From MSC Protocol Error - PM . . . . . . . 1. BSS: Call Processing Failure - MSC Detected SCCP Down . . . . 1. BSS: Routing Failure - Syntax Error Detected - PM . . . . . . . . 2. BSS: Call Processing Failure - MSC Detected BSSAP Down . . . 2. BSS: Routing Failure - Reason Unknown - PM . . . . . . . . . . 3. BSS: Call Processing Failure - BSS Detected BSSAP Down . . . . 5. BSS: No MSC Acknowledgement for Circuit Block . . . . . . . . 6. BSS: No MSC Acknowledgement for Circuit Unblock . . . . . . 7. BSS: No MSC Acknowledgement for Reset Circuit . . . . . . . . 7. BSS: Mobile Assignment Request From MSC Protocol Error - PM . 8. BSS: Unequipped Circuit at the MSC . . . . . . . . . . . . . . 9. BSS: No MSC Acknowledgement for Global Reset . . . . . . . . 10. BSS: Erroneous Layer 3 Message Received by the BSS . . . . . 11. BSS: Confusion Message Received from the MSC . . . . . . . . 12. BSS: Unequipped Circuit at the BSS . . . . . . . . . . . . . . 17. BSS: HO Request From the MSC Protocol Error - PM . . . . . . 18. BSS: Routing Failure - Syntax Error Detected (SMLC) - PM . . . 20. BSS: Paging Request from SMLC Protocol Error - PM . . . . . . 21. BSS: Trunk Major Threshold Exceeded . . . . . . . . . . . . . 22. BSS: Trunk Critical Threshold Exceeded . . . . . . . . . . . . 26. BSS: Received Page for Invalid Cell from MSC . . . . . . . . . 39.BSS: Circuit Fault Detected on Radio Channel . . . . . . . . . . 40. BSS: Circuit Fault Cleared on Radio Channel . . . . . . . . . . 41. BSS: Circuit Fault Detected On Ater Channel . . . . . . . . . . 42. BSS: Circuit Fault Cleared On Ater Channel . . . . . . . . . .
ii
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3 6-4 6-7 6-8 6-9 6-10 6-11 6-12 6-14 6-16 6-18 6-20 6-22 6-24 6-25 6-26 6-27 6-29 6-30 6-31 6-32 6-34 6-36 6-37 6-39 6-41 6-43
68P02901W26-Q 24 May 2004
Contents
43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 59.
BSS: Circuit Fault Detected on PCM Circuit . . . . . . . . BSS: Circuit Fault Cleared on PCM Circuit . . . . . . . . . BSS: Circuit Fault Detected on GPRS Circuit . . . . . . . . BSS: Circuit Fault Cleared on GPRS Circuit . . . . . . . . BSS: Circuit Fault Detected On PATH Channel . . . . . . . BSS: Circuit Fault Cleared on PATH Channel . . . . . . . . BSS: Last LMTL Link Failure - Signalling Point Inaccessible BSS: Call Processing Failure - SMLC Detected SCCP Down . BSS: Call Processing Failure - SMLC Detected BSSAP Down BSS: No SMLC Acknowledgement for Global Reset. . . . . BSS: Erroneous Layer 3 Message Received from SMLC . . . BSS: Confusion Message Received from the SMLC . . . . . BSS: Received Page for Invalid Cell from SMLC . . . . . . BSS: Last PCU Failed . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
6-45 6-47 6-48 6-50 6-51 6-53 6-55 6-58 6-60 6-62 6-63 6-64 6-65 6-66
Chapter 7: BTP alarms

Introduction to BTP alarms . . . . . . . . . . . . . . . . . . . . . . 1. BTP: EEPROM Flash Failure - No Valid Bootstrap Code Object Present 8. BTP: EEPROM Flash Object Failure . . . . . . . . . . . . . . . . . 17. BTP: EEPROM Flash Programming Failure . . . . . . . . . . . . . 21. BTP: EEPROM Flash Programming Failure . . . . . . . . . . . . . 22. BTP: SWFM Indication . . . . . . . . . . . . . . . . . . . . . . 30. BTP: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . . . 31. BTP: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . . . 32. BTP: TDM Interface Failure - Assigned Timeslot Counter Underflow . 33. BTP: TDM Interface Failure - Assigned Timeslot Counter Overflow . 34. BTP: TDM Interface Failure - TDM Parity Error. . . . . . . . . . . 35. BTP: LAN Connection Failure . . . . . . . . . . . . . . . . . . . 39. BTP: Software Failure . . . . . . . . . . . . . . . . . . . . . . . 40. BTP: Spurious Interrupt . . . . . . . . . . . . . . . . . . . . . . 42. BTP: Site Reset Occurred Due To Front Panel Reset . . . . . . . . . 47. BTP: Unexpected Board Type: GPROC2 or GPROC3 expected. . . . 48. BTP: Memory location is corrupt. Replace GPROC board . . . . . . 50. BTP: EEPROM SW Flash Programming Failure. . . . . . . . . . . 51. BTP: EEPROM HW Flash Programming Failure . . . . . . . . . . 231. BTP: TDM Interface Configuration Failure. . . . . . . . . . . . . 234. BTP: Active Link Connection Failure . . . . . . . . . . . . . . . 235. BTP: Standby Link Connection Failure . . . . . . . . . . . . . . 236. BTP: Slow Flash Failure . . . . . . . . . . . . . . . . . . . . . 237. BTP: Non-Volatile Memory Failure . . . . . . . . . . . . . . . . 239. BTP: Process Safe Test Audit Failure . . . . . . . . . . . . . . . 254. BTP: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 7-5 7-7 7-9 7-10 7-11 7-12 7-14 7-16 7-18 7-20 7-22 7-24 7-26 7-28 7-29 7-31 7-32 7-33 7-34 7-36 7-38 7-41 7-43 7-45 7-47
Chapter 8: CAB alarms

Introduction to CAB alarms . . . . . . . . . . . . . . . 25. CAB: External Power Booster Amplifier 1 Failure . . . 26. CAB: External Power Booster Amplifier 2 Failure . . . 27. CAB: External Power Booster Failure . . . . . . . . . 28. CAB: Database Configuration and Hardware Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 8-3 8-4 8-5 8-6
Chapter 9: CAGE alarms

Introduction to CAGE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.- 25. CAGE: CLKX Slot 2-7 Communication Failure . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W26-Q 24 May 2004 9-2 9-3
iii
Contents
26.- 27. CAGE: LANX Slot 19-20 Communication Failure. . . . . . . . . . . 28.- 30. CAGE: Power Supply Unit#1-3 Output Failure . . . . . . . . . . . . 31.- 33. CAGE: Power Supply Unit #1-3 - Not Detected . . . . . . . . . . . . 34.- 36 CAGE: Power Supply Unit #1-3 - Fan Failure . . . . . . . . . . . . . 37.- 39. CAGE: Power Supply Unit #1-3 - Over Temperature. . . . . . . . . . 40. CAGE: Over Temperature - Component Damage Imminent. . . . . . . . . 41.- 42. CAGE: Local KSWX/DSWX Slot 0-1 Communication Failure . . . . . 43.- 47. CAGE: Remote KSWX/DSWX Slot 2-6 Communication Failure . . . . 48.- 52. CAGE: Remote KSWX/DSWX Slot 24-28 Communication Failure. . . 53.- 55. CAGE: Expansion KSWX / DSWX Slot 7- 9 Communication Failure. . 56.- 58. CAGE: Expansion KSWX / DSWX Slot 21-23 Communication Failure . 59.- 76. CAGE: DSWX / KSWX Mismatch . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
9-6 9-9 9-11 9-12 9-13 9-15 9-17 9-20 9-23 9-26 9-29 9-32
Chapter 10: CBL alarms

Introduction to CBL alarms . . . . . . 0. CBL: Invalid Received Frames - PM . 1. CBL: FRMR-Frames - PM . . . . . 2. CBL: Expiration of N2 - PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 10-3 10-4 10-5
Chapter 11: CBUS alarms

Introduction to CBUS alarms. . . . . . . . . . . . . . 0. CBUS: Over 50% of Boards Detected Clock Failure. . 2. CBUS: Master CBUS Signal Provided By Slave GCLK 4. CBUS: Local KSWX/DSWX Clock Fibre Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 11-3 11-5 11-7
Chapter 12: CELL alarms

Introduction to CELL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. CELL: Flow control procedure has started barring normal calls from access classes 0-9 0. CELL: Radio Frequency Losses While Using an SDCCH - PM . . . . . . . . . . . 1. CELL: Cell Radio Timeslot Capacity Loss . . . . . . . . . . . . . . . . . . . . . 1. CELL: Attempt at Allocating an SDCCH Failed - PM . . . . . . . . . . . . . . . . 2. CELL: Radio Subsystem Software Error - Detected Page Overflow . . . . . . . . . 2. CELL: Channel Request From MS Blocked - PM . . . . . . . . . . . . . . . . . . 3. CELL: Last NS-VC Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. CELL: Classmark Update from MS Protocol Error - PM. . . . . . . . . . . . . . . 5. CELL: No Cell (BVC) Block Acknowledgement from the SGSN . . . . . . . . . . 6. CELL: Cipher Mode Cmd from MSC Failed - PM . . . . . . . . . . . . . . . . . 7. CELL: GPRS and baseband hopping configuration failure . . . . . . . . . . . . . . 8. CELL: GPRS unavailable - No PRP available. . . . . . . . . . . . . . . . . . . . 9. CELL: GPRS unavailable - No GDS available . . . . . . . . . . . . . . . . . . . 9. CELL: Intra-Cell Handover Failed & Recovered PM . . . . . . . . . . . . . . . . 10. CELL: GPRS unavailable - No Cell (BVC) Reset Ack from the SGSN . . . . . . . 10. CELL: Intra-Cell Handover Failed & Mobile Lost - PM . . . . . . . . . . . . . . 11. CELL: GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN . . . . . . 11. CELL: Intra-BSS HO Primary Target Cell Blocked - PM . . . . . . . . . . . . . . 12. CELL: GPRS unavailable - No PDCHs Available . . . . . . . . . . . . . . . . . 13. CELL: GPRS unavailable - No GPRS capable carriers available . . . . . . . . . . 13. CELL: Intra-BSS HO Failed and Recovered to Org Channel - PM . . . . . . . . . 14. CELL: Intra-BSS HO Failed and Mobile Lost - PM . . . . . . . . . . . . . . . . 14. CELL: GPRS unavailable - PBCCH timeslot out of sync . . . . . . . . . . . . . . 15. CELL: EGPRS unavailable - No EGPRS Carriers Available . . . . . . . . . . . . 15. CELL: Inter-BSS HO, MS HO Failed Message Received PM . . . . . . . . . . . . 17. CELL: EGPRS Unavailable - Insufficient GDS Available. . . . . . . . . . . . . .
iv
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
12-3 12-4 12-7 12-9 12-10 12-12 12-14 12-16 12-18 12-20 12-21 12-23 12-25 12-26 12-27 12-29 12-31 12-33 12-34 12-36 12-37 12-38 12-40 12-42 12-43 12-44 12-46
68P02901W26-Q 24 May 2004
Contents
18. 19. 20. 22. 23. 24. 25.
CELL: HO failure to the MSC due to all Possible Errors Except No Channels - PM CELL: Bad HO Reference Numbers from the MS - PM . . . . . . . . . . . . . CELL: Number of Calls Queued - PM . . . . . . . . . . . . . . . . . . . . . CELL: Mobile Assign Command to MS Blocked (No Channel Available) - PM . . CELL: Mobile Assignment Failure from MS - PM . . . . . . . . . . . . . . . . CELL: PCH Queue Page Discard - PM . . . . . . . . . . . . . . . . . . . . . CELL: Attempt at Allocating a TCH Failed - PM . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
12-47 12-49 12-51 12-53 12-55 12-57 12-59
Chapter 13: COMB alarms

Introduction to COMB alarms . . . . . . . . 0.- 4. COMB: Cavity 0- 4 Tuning Error . . . . 5. COMB: Link A Sanity Failure . . . . . . . 6. COMB: Link B Sanity Failure . . . . . . . 7. COMB: Power Feed A Failure . . . . . . . 8. COMB: Power Feed B Failure . . . . . . . 9. COMB: Full Reset . . . . . . . . . . . . 10. COMB: Partial Reset . . . . . . . . . . 11. COMB: Cavity 5 Tuning Error . . . . . . 12. COMB: Cavity Combining Block 0 Failure 13. COMB: Cavity Combining Block 1 Failure 14. COMB: Processor A Failure . . . . . . . 15. COMB: Processor B Failure . . . . . . . 254. COMB: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 13-3 13-5 13-7 13-9 13-11 13-13 13-16 13-18 13-20 13-22 13-24 13-26 13-28
Chapter 14: CSFP alarms

Introduction to CSFP alarms . . . . . . . . . . . . . . . . . . . 22. CSFP: SWFM Indication . . . . . . . . . . . . . . . . . . . 35. CSFP: LAN Connection Failure . . . . . . . . . . . . . . . 47. CSFP: Unexpected Board Type: GPROC2 or GPROC3 expected 48. CSFP: Memory location is corrupt. Replace GPROC board. . . 49. CSFP: Code Objects Unavailable . . . . . . . . . . . . . . . 50. CSFP: EEPROM SW Flash Programming Failure. . . . . . . . 51. CSFP: EEPROM HW Flash Programming Failure.. . . . . . . 240. CSFP: PCMCIA Card Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 14-3 14-4 14-6 14-7 14-8 14-10 14-11 14-12
Chapter 15: DHP alarms

Introduction to DHP alarms . . . . . . . . . . . . . . . . . . . . . . . . . 1. DHP: EEPROM Flash Failure - No Valid Bootstrap Code Object Present . . . 8. DHP: EEPROM Flash Object Failure . . . . . . . . . . . . . . . . . . . 17. DHP: EEPROM Flash Programming Failure. . . . . . . . . . . . . . . . 21. DHP: EEPROM Flash Programming Failure. . . . . . . . . . . . . . . . 22. DHP: SWFM Indication . . . . . . . . . . . . . . . . . . . . . . . . . 23. DHP: SYNC Lost Phase Lock to Master GCLK . . . . . . . . . . . . . . 24. DHP: Bad Clock Source or SYNC OCXO (oscillator) Replacement Required 25. DHP: SYNC Warmup Failure . . . . . . . . . . . . . . . . . . . . . . 26. DHP: SYNC Calibration Request . . . . . . . . . . . . . . . . . . . . . 27. DHP: SYNC Shutdown Request . . . . . . . . . . . . . . . . . . . . . 28. DHP: SYNC Clock Output Failure . . . . . . . . . . . . . . . . . . . . 29. DHP: SYNC Watchdog Timer Expired . . . . . . . . . . . . . . . . . . 30. DHP: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . . . . . . 31. DHP: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . . . . . . 32. DHP: TDM Interface Failure - Assigned Timeslot Counter Underflow. . . . 33. DHP: TDM Interface Failure - Assigned Timeslot Counter Overflow . . . . 68P02901W26-Q 24 May 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 15-4 15-6 15-8 15-9 15-10 15-11 15-13 15-15 15-16 15-18 15-20 15-22 15-24 15-26 15-27 15-29
v
Contents
34. DHP: TDM Interface Failure - TDM Parity Error . . . . . . . 35. DHP: LAN Connection Failure . . . . . . . . . . . . . . . . 39. DHP: Software Failure . . . . . . . . . . . . . . . . . . . . 40. DHP: Spurious Interrupt . . . . . . . . . . . . . . . . . . . 43. DHP: SYNC Not Operational. . . . . . . . . . . . . . . . . 44. DHP: SYNC Calibration via Firmware Initiated . . . . . . . . 45. DHP: SYNC Phase Lock Failure . . . . . . . . . . . . . . . 46. DHP: SYNC Invalid Mode . . . . . . . . . . . . . . . . . . 47. DHP: Unexpected Board Type: GPROC2 or GPROC3 expected 48. DHP: Memory location is corrupt. Replace GPROC board. . . . 50. DHP: EEPROM SW Flash Programming Failure. . . . . . . . 51. DHP: EEPROM SW Flash Programming Failure. . . . . . . . 231. DHP: TDM Interface Configuration Failure . . . . . . . . . 234. DHP: Active Link Connection Failure . . . . . . . . . . . . 239. DHP: Process Safe Test Audit Failure . . . . . . . . . . . . 254. DHP: Device Failure . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
15-31 15-33 15-35 15-37 15-39 15-41 15-42 15-44 15-46 15-48 15-49 15-50 15-51 15-53 15-55 15-57
Chapter 16: DPROC alarms

Introduction to DPROC alarms . . . . . . . . 0. DPROC: Processor Communication Failure 9. DPROC: DPROC Reset Detected . . . . . 22. DPROC: SWFM Indication . . . . . . . 39. DPROC: Software Failure . . . . . . . . 239. DPROC: Process Safe Test Audit Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 16-3 16-5 16-7 16-8 16-9
Chapter 17: DRI alarms

Introduction to DRI alarms. . . . . . . . . . . . . . . . . . . . . . 2. DRI: Internal Message Error - Pointer Misalignment . . . . . . . . 3. DRI: Internal Message Error - Dual-Port RAM Segment Full . . . . 5. DRI: Superframe Counter Error (Uplink) . . . . . . . . . . . . . . 6. DRI: Superframe Counter Error (Downlink) . . . . . . . . . . . . 9. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 10. DRI: Dual-Port RAM Error . . . . . . . . . . . . . . . . . . . 13. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 14. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 15. DRI: Initial Synchronization of Radio and GPRS channel failed. . . 16. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 17. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 18. DRI: Primary Message or Hardware Interrupt Error . . . . . . . . 19. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 20. DRI: Channel Coder Internal Message Error . . . . . . . . . . . . 21. DRI: Calibration in progress . . . . . . . . . . . . . . . . . . . 22. DRI: Radio Subsystem Software to DRI Communication Error . . . 23. DRI: Radio Subsystem Software to DRI Communication Failure . . 24. DRI: TDM Interface Failure - TDM Parity Error . . . . . . . . . . 25. DRI: TDM Interface Failure - Assigned Timeslot Counter Overflow 26. DRI: TDM Interface Failure - Assigned Timeslot Counter Underflow 27. DRI: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . . 28. DRI: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . . 29. DRI: Processor Failure . . . . . . . . . . . . . . . . . . . . . . 30. DRI: Transceiver Re-Initialized Unexpectedly . . . . . . . . . . . 31. DRI: Critical Resource Exhausted . . . . . . . . . . . . . . . . 32. DRI: RF Unit Primary Sync Signal Lost . . . . . . . . . . . . . 33. DRI: RF Unit HDSL Link Quality Error. . . . . . . . . . . . . .
vi
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
17-7 17-9 17-11 17-13 17-15 17-17 17-19 17-21 17-23 17-25 17-27 17-29 17-31 17-33 17-35 17-37 17-38 17-40 17-42 17-44 17-46 17-48 17-50 17-52 17-54 17-56 17-58 17-59
68P02901W26-Q 24 May 2004
Contents
34. DRI: RF Unit Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35. DRI: Reset Due To Recurring Fault . . . . . . . . . . . . . . . . . . . . . . . . 36. DRI: Front End Processor to Radio Subsystem Software Communication Failure. . . 37. DRI: Hard Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38. DRI: BSS INTERNAL ALARM ONLY - FWFM Displayed at EMON . . . . . . . 39. DRI: Synchronization Loss With MCU . . . . . . . . . . . . . . . . . . . . . . 40. - 47. DRI: Channel Coder Timeslot (0-7) Failure. . . . . . . . . . . . . . . . . . 48. DRI: Baseband Hopping Timeslot Counter Mismatch . . . . . . . . . . . . . . . 49. DRI: GSM Timeslot Counter Mismatch . . . . . . . . . . . . . . . . . . . . . . 50. DRI: Spurious GSM Timeslot Interrupt . . . . . . . . . . . . . . . . . . . . . . 51. DRI: Baseband Hopping TDM Link Error . . . . . . . . . . . . . . . . . . . . . 52. DRI: Baseband Hopping GSM Timeslot Misalignment . . . . . . . . . . . . . . . 53. DRI: Channel Coder 0 Failure - Demodulation Processor 0 Failure . . . . . . . . . 54. DRI: Channel Coder 0 Failure - Demodulation Processor 1 Failure . . . . . . . . . 55. DRI: Channel Coder 1 Failure - Demodulation Processor 0 Failure . . . . . . . . . 56. DRI: Channel Coder 1 Failure - Demodulation Processor 1 Failure . . . . . . . . . 57. DRI: Transceiver to DRI Communication Error . . . . . . . . . . . . . . . . . . 58. DRI: Transceiver to DRI Communication Error . . . . . . . . . . . . . . . . . . 59. DRI: Transceiver to DRI Burst Error . . . . . . . . . . . . . . . . . . . . . . . 60. DRI: Transceiver to DRI Burst Error . . . . . . . . . . . . . . . . . . . . . . . 61. DRI: Transceiver to DRI Communication Error . . . . . . . . . . . . . . . . . . 62. DRI: Transceiver to DRI Communication Error . . . . . . . . . . . . . . . . . . 63. DRI: Transceiver to DRI Communication Error . . . . . . . . . . . . . . . . . . 64. DRI: Unrecoverable Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65. DRI: Radio Subsystem Software to DRI Communication Error - Checksum Error . . 66. DRI: Superframe Counter Error. . . . . . . . . . . . . . . . . . . . . . . . . . 67. DRI: Radio Subsystem Software to DRI Communication Error - DRI Not Responding 70. DRI: Equalizer Control Processor Failure - Watchdog Timer Expired . . . . . . . . 71. DRI: Unexpected Communications Bus Interrupt . . . . . . . . . . . . . . . . . 72. DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73. DRI: Power Amplifier Error . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. DRI: Cell Transmit Power Unachievable . . . . . . . . . . . . . . . . . . . . . 76. DRI: Radio Subsystem Software to DRI Communication Error . . . . . . . . . . . 78. DRI: TX VSWR Antenna Fault . . . . . . . . . . . . . . . . . . . . . . . . . . 80. DRI: Transmitter Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . 81. DRI: Transmitter Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . 82. DRI: Transmitter Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . 83. DRI: Transmitter Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . 84. DRI: Transmitter Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . 85. DRI: Transmitter Failure - Output Power . . . . . . . . . . . . . . . . . . . . . 86. DRI: Transmitter Failure - Output Power . . . . . . . . . . . . . . . . . . . . . 87. DRI: Transmitter Failure - Output Power . . . . . . . . . . . . . . . . . . . . . 88. DRI: Power Amplifier Temperature High . . . . . . . . . . . . . . . . . . . . . 89. DRI: Power Amplifier Communication Failure . . . . . . . . . . . . . . . . . . 90. DRI: Transmitter Failure - Output Power . . . . . . . . . . . . . . . . . . . . . 91. DRI: Power Amplifier Power Low But Functioning . . . . . . . . . . . . . . . . 92. DRI: Power Amplifier Temperature High But Functioning . . . . . . . . . . . . . 93. DRI: Transmitter Failure - Output Power . . . . . . . . . . . . . . . . . . . . . 104-111. DRI: Timeslot 0-7 Configuration Failure . . . . . . . . . . . . . . . . . . 112. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 113. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 114. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 115. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 116. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 117. DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W26-Q 24 May 2004
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17-60 17-62 17-64 17-65 17-67 17-68 17-70 17-72 17-74 17-76 17-78 17-80 17-83 17-85 17-87 17-89 17-91 17-93 17-95 17-97 17-99 17-101 17-103 17-105 17-107 17-110 17-112 17-114 17-116 17-118 17-120 17-122 17-124 17-126 17-127 17-129 17-131 17-133 17-135 17-137 17-139 17-141 17-143 17-145 17-147 17-149 17-151 17-153 17-155 17-157 17-159 17-161 17-163 17-165 17-167
vii
Contents
118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 144. 146. 147. 148. 149. 150. 151. 152. 153. 154. 155. 156. 157. 158. 159. 160. 161. 162. 163. 164. 165. 166. 167. 168. 169. 170. 171. 176. 184. 192. 193. 203. 204. 205. 206. 207. 208. 210. 211. 212. 213. 214. 215. 216.
DRI: Receiver Synthesizer Failure . . . . . . . . . . . . . . . . DRI: Receiver Failure. . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Receiver Failure . . . . . . . . . . . . . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Receive Matrix Branch 1 Control Link Failure . . . . . . . DRI: Transceiver to Combiner Communication Failure . . . . . . DRI: Control Processor to Power Amplifier Communication Failure DRI: Control Processor to Equalizer Communication Failure . . . DRI: Power Supply Failure . . . . . . . . . . . . . . . . . . . DRI: Transceiver to DRI Communication Error. . . . . . . . . . DRI: Control Processor Message Queue Overflowed . . . . . . . DRI: Receiver Input Overflowed . . . . . . . . . . . . . . . . DRI: Receiver Input Overflowed . . . . . . . . . . . . . . . . DRI: Equalizer Output Overflowed . . . . . . . . . . . . . . . DRI: Equalizer Output Overflowed . . . . . . . . . . . . . . . DRI: Transmitter Out of Synchronization . . . . . . . . . . . . DRI: Receive Matrix Branch 2 Control Link Failure . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: Control Processor Firmware Failure . . . . . . . . . . . . DRI: Control Processor Configuration Mismatch . . . . . . . . . DRI: Equalizer Configuration Mismatch . . . . . . . . . . . . . DRI: Transceiver to DRI Communication Failure . . . . . . . . . DRI: M-Cell Micro Interconnect Failure . . . . . . . . . . . . . DRI: Invalid Calibration Data . . . . . . . . . . . . . . . . . . DRI: Equalizer Timeslot (0-7) Failure . . . . . . . . . . . . . . DRI: Equalizer Firmware Failure . . . . . . . . . . . . . . . . DRI: Baseband Hopping TDM Link Error . . . . . . . . . . . . DRI: Baseband Hopping GSM Timeslot Misalignment . . . . . . DRI: RF Unit Power Supply Unit - Input Failure . . . . . . . . . DRI: RF Unit Over Temperature . . . . . . . . . . . . . . . . DRI: RF Unit Low Voltage Disconnect Imminent . . . . . . . . DRI: RF Unit External Alarm Input . . . . . . . . . . . . . . . DRI: Internal Communication Error . . . . . . . . . . . . . . . DRI: Power Amplifier Temperature . . . . . . . . . . . . . . . DRI: Hopping DRI Failure . . . . . . . . . . . . . . . . . . . DRI: Front End Processor Failure . . . . . . . . . . . . . . . . DRI: Channel Coder Failure. . . . . . . . . . . . . . . . . . . DRI: Transceiver Processor Failure . . . . . . . . . . . . . . . DRI: Equalizer Failure . . . . . . . . . . . . . . . . . . . . . DRI: Power Amplifier Failure . . . . . . . . . . . . . . . . . . DRI: Transceiver Recovery Failure . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17-169 17-171 17-173 17-175 17-177 17-179 17-181 17-183 17-185 17-187 17-189 17-191 17-194 17-196 17-198 17-200 17-202 17-204 17-206 17-208 17-210 17-212 17-214 17-216 17-218 17-220 17-222 17-224 17-226 17-228 17-230 17-232 17-234 17-236 17-238 17-240 17-242 17-244 17-246 17-248 17-250 17-252 17-254 17-255 17-256 17-257 17-258 17-259 17-260 17-262 17-264 17-266 17-268 17-270 17-272
viii
68P02901W26-Q 24 May 2004
Contents
217. 218. 219. 221. 224. 231. 234. 235. 236. 237. 239. 241. 243. 254.
DRI: Transmission Suspended to Conserve Battery Power. . DRI: Invalid Transceiver Calibration Data . . . . . . . . . DRI: GPRS Not Supported by Radio. . . . . . . . . . . . DRI: Invalid in-call modification of destination channel type DRI: Safe Test Audit Failure . . . . . . . . . . . . . . . DRI: TDM Interface Configuration Failure . . . . . . . . . DRI: Active Link Connection Failure . . . . . . . . . . . DRI: Standby Link Connection Failure. . . . . . . . . . . DRI: Slow Flash Failure . . . . . . . . . . . . . . . . . DRI: Non-Volatile Memory Failure . . . . . . . . . . . . DRI: Process Safe Test Audit Failure . . . . . . . . . . . DRI: Standby Link Connected to Wrong Device . . . . . . DRI: Unlocked Device Not in Service . . . . . . . . . . . DRI: Device Failure . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
17-273 17-274 17-275 17-276 17-277 17-279 17-281 17-284 17-286 17-288 17-290 17-292 17-294 17-295
Chapter 18: EAS alarms

Introduction to EAS alarms . . . . . . . . . 0. EAS: Unexpected Board Type . . . . . . . 1. EAS: Serial Bus Connection Failure . . . . 8. EAS: EAS has detected Main Power Failure 16.-31. EAS: Optocoupler 1-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 18-3 18-5 18-7 18-9
Chapter 19: GBL alarms

Introduction to GBL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. GBL: Link Disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2 19-3
Chapter 20: GCLK alarms

Introduction to GCLK alarms . . . . . . . . . . . . . . . . . . . . . . 0. GCLK: Reference Distribution Module Failure . . . . . . . . . . . . . 2. GCLK: Clock Reference Failure . . . . . . . . . . . . . . . . . . . . 4. GCLK: Phase Lock Lost . . . . . . . . . . . . . . . . . . . . . . . 5. GCLK: 125s Reference Count Overflow . . . . . . . . . . . . . . . 6. GCLK: 60ms Reference Count Overflow . . . . . . . . . . . . . . . . 7. GCLK: 6.12s Reference Count Overflow . . . . . . . . . . . . . . . . 8. GCLK: Frequency Difference in Mate GCLK. . . . . . . . . . . . . . 9. GCLK: Hard Reset . . . . . . . . . . . . . . . . . . . . . . . . . . 11. GCLK: Long-Term-Average Values are Unstable . . . . . . . . . . . 12. GCLK: Unrecognized Hardware Revision Level . . . . . . . . . . . . 14. GCLK: Phase Lock Failure . . . . . . . . . . . . . . . . . . . . . . 15. GCLK: Watchdog Timer Expired . . . . . . . . . . . . . . . . . . . 16. GCLK: Clock Output Failure . . . . . . . . . . . . . . . . . . . . . 17. GCLK: SYNC Shutdown Request . . . . . . . . . . . . . . . . . . 18. GCLK: Not Operational . . . . . . . . . . . . . . . . . . . . . . . 19. GCLK: Warmup Failure . . . . . . . . . . . . . . . . . . . . . . . 20. GCLK: Invalid Mode . . . . . . . . . . . . . . . . . . . . . . . . 21. GCLK: Calibration In Progress . . . . . . . . . . . . . . . . . . . . 22. GCLK: Calibration via Firmware Initiated. . . . . . . . . . . . . . . 24. GCLK: Bad Clock Source or OCXO (oscillator) Replacement Required . 26. GCLK: GCLK Calibration Request . . . . . . . . . . . . . . . . . . 232. GCLK: Processor Bus Communication Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2 20-3 20-5 20-8 20-11 20-13 20-15 20-17 20-20 20-22 20-24 20-25 20-28 20-30 20-32 20-34 20-36 20-38 20-40 20-41 20-42 20-45 20-48
68P02901W26-Q 24 May 2004
ix
Contents
Chapter 21: GPROC alarms

Introduction to GPROC alarms . . . . . . . . . . . . . . . . . . . . . . . . . 1. GPROC: EEPROM Flash Failure - No Valid Bootstrap Code Object Present . . 8. GPROC: EEPROM Flash Object Failure . . . . . . . . . . . . . . . . . . . 17. GPROC: EEPROM Flash Programming Failure . . . . . . . . . . . . . . . 19. GPROC: RSL Links Congestion . . . . . . . . . . . . . . . . . . . . . . 21. GPROC: EEPROM Flash Programming Failure . . . . . . . . . . . . . . . 22. GPROC: SWFM Indication . . . . . . . . . . . . . . . . . . . . . . . . 23. GPROC: SYNC Lost Phase Lock to Master GCLK . . . . . . . . . . . . . 24. GPROC: Bad Clock Source or SYNC OCXO(oscillator) Replacement Required 25. GPROC: SYNC Warmup Failure . . . . . . . . . . . . . . . . . . . . . . 26. GPROC: SYNC Calibration Request . . . . . . . . . . . . . . . . . . . . 27. GPROC: SYNC Shutdown Request . . . . . . . . . . . . . . . . . . . . 28. GPROC: SYNC Clock Output Failure . . . . . . . . . . . . . . . . . . . 29. GPROC: SYNC Watchdog Timer Expired . . . . . . . . . . . . . . . . . 30. GPROC: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . . . . . 31. GPROC: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . . . . . 32. GPROC: TDM Interface Failure - Assigned Timeslot Counter Underflow . . . 33. GPROC: TDM Interface Failure - Assigned Timeslot Counter Overflow. . . . 34. GPROC: TDM Interface Failure - TDM Parity Error . . . . . . . . . . . . . 35. GPROC: LAN Connection Failure . . . . . . . . . . . . . . . . . . . . . 39. GPROC: Software Failure . . . . . . . . . . . . . . . . . . . . . . . . . 40. GPROC: Spurious Interrupt . . . . . . . . . . . . . . . . . . . . . . . . 42. GPROC: Site Reset Occurred Due To Front Panel Reset . . . . . . . . . . . 43. GPROC: SYNC Not Operational . . . . . . . . . . . . . . . . . . . . . . 44. GPROC: SYNC Calibration via Firmware Initiated . . . . . . . . . . . . . 45. GPROC: SYNC Phase Lock Failure . . . . . . . . . . . . . . . . . . . . 46. GPROC: SYNC Invalid Mode . . . . . . . . . . . . . . . . . . . . . . . 47. GPROC: Unexpected Board Type: GPROC2 or GPROC3 expected . . . . . . 48. GPROC: Memory location is corrupt. Replace GPROC board. . . . . . . . . 50. GPROC: EEPROM SW Flash Programming Failure. . . . . . . . . . . . . . 51. GPROC: EEPROM SW Flash Programming Failure. . . . . . . . . . . . . . 231. GPROC: TDM Interface Configuration Failure . . . . . . . . . . . . . . . 239. GPROC: Process Safe Test Audit Failure. . . . . . . . . . . . . . . . . . 254. GPROC: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3 21-4 21-6 21-8 21-9 21-10 21-11 21-12 21-13 21-14 21-15 21-16 21-17 21-18 21-19 21-21 21-23 21-25 21-27 21-29 21-31 21-33 21-35 21-36 21-37 21-38 21-39 21-40 21-42 21-43 21-44 21-45 21-47 21-49
Chapter 22: GSL alarms

Introduction to GSL alarms . . . . . . . . . . . . 0. GSL: Invalid Received Frames - PM . . . . . . . 1. GSL: FRMR-Frames - PM . . . . . . . . . . . 2. GSL: Expiration of N2 - PM . . . . . . . . . . . 10. GSL: Link Disconnected . . . . . . . . . . . . 11. GSL: LAPD Protocol Error. . . . . . . . . . . 13. GSL: LAPD Protocol Error Threshold Exceeded . 15. GSL: Too Many LAPD Protocol Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2 22-3 22-4 22-5 22-6 22-10 22-12 22-14
Chapter 23: IAS alarms

Introduction to IAS alarms . . . . . . 0. IAS: Unexpected Board Type . . . 1. IAS: Serial Bus Connection Failure 8. IAS: Power Supply Unit 0 Failure . 9. IAS: Power Supply Unit 1 Failure . 10. IAS: Power Supply Unit 2 Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4 23-5 23-6 23-9 23-11 23-13
68P02901W26-Q 24 May 2004
Contents
11. IAS: Power Supply Unit 3 Failure. . . . . . . . . . . . . . . . . . 12. IAS: Tx VSWR Antenna Fault . . . . . . . . . . . . . . . . . . . 13.-15. IAS: Preselector 1A-3A Fuse Failure . . . . . . . . . . . . . . 16. IAS: Matrix Control Main Fuse Failure . . . . . . . . . . . . . . . 17. IAS: Matrix Control Redundant Fuse Failure . . . . . . . . . . . . 18. IAS: Internal Combiner Main Fuse Failure . . . . . . . . . . . . . 19. IAS: Internal Combiner Redundant Fuse Failure . . . . . . . . . . . 20. IAS: External Combiner Main Fuse Failure . . . . . . . . . . . . . 21. IAS: External Combiner Redundant Fuse Failure . . . . . . . . . . 22. IAS: Multicoupler Main Fuse Failure . . . . . . . . . . . . . . . . 23. IAS: Multicoupler Redundant Fuse Failure . . . . . . . . . . . . . 24.-26. IAS: BCU Lower Cage Fan #0-#2 Fuse Failure . . . . . . . . . 27.-29. IAS: BCU Upper Cage Fan #3-#5 Fuse Failure. . . . . . . . . . 30. IAS: Spare Fuse Failure . . . . . . . . . . . . . . . . . . . . . . 31. IAS: DRAM Battery Backup Fuse Failure . . . . . . . . . . . . . . 32. IAS: IAS +27 V Power Fuse Failure . . . . . . . . . . . . . . . . 33.- 34. IAS: Battery Backup Fuse #1-#2 Failure . . . . . . . . . . . . 35.- 37. IAS: Lower Cage Fan #0-#2 Failure . . . . . . . . . . . . . . 38.- 40. IAS: Upper Cage Fan #3-#5 Failure . . . . . . . . . . . . . . 41. IAS: Multicoupler Failure . . . . . . . . . . . . . . . . . . . . . 46. IAS: Converter Failure . . . . . . . . . . . . . . . . . . . . . . . 47. IAS: Converter Overtemperature . . . . . . . . . . . . . . . . . . 48.-50. IAS: Preselector 1B-3B Fuse Failure . . . . . . . . . . . . . . 51. IAS: Duplexer Voltage Error . . . . . . . . . . . . . . . . . . . . 59. IAS: Battery Backup Output Failure . . . . . . . . . . . . . . . . 60. IAS: Battery Backup Input Failure . . . . . . . . . . . . . . . . . 61. IAS: RCU #5 Circuit Breaker Failure . . . . . . . . . . . . . . . . 62. IAS: DPSM 1 Failure . . . . . . . . . . . . . . . . . . . . . . . 63. IAS: DPSM 0 Failure . . . . . . . . . . . . . . . . . . . . . . . 64.- 65. IAS: Fan Power Converter 1-2 Failure . . . . . . . . . . . . . 66.- 70. IAS: RCU #0-#4 Circuit Breaker Failure . . . . . . . . . . . . 71.- 74. IAS: Converter #1-#4 Failure . . . . . . . . . . . . . . . . . 75. IAS: IAS +27 V DAB Power Fuse Failure . . . . . . . . . . . . . . 80. IAS: Power Supply Unit - Input Failure . . . . . . . . . . . . . . . 81. IAS: Power Supply Unit - Output Failure . . . . . . . . . . . . . . 82. IAS: BTS Cabinet Over Temperature . . . . . . . . . . . . . . . . 83. IAS: Low Voltage Disconnect Imminent. . . . . . . . . . . . . . . 84. IAS: Air Conditioning Unit Failure . . . . . . . . . . . . . . . . . 85. IAS: Heat Management System Unit Failure. . . . . . . . . . . . . 86. IAS: Cabinet Fan Failure . . . . . . . . . . . . . . . . . . . . . . 87. IAS: Ancillary Cabinet Over Temperature . . . . . . . . . . . . . . 88.- 90. IAS: Voltage Standing Wave Ratio Sector 1-3 Failure . . . . . . 91. IAS: Voltage Standing Wave Ratio Performance Low . . . . . . . . 92. IAS: Smoke Alarm . . . . . . . . . . . . . . . . . . . . . . . . 93. IAS: Door Open . . . . . . . . . . . . . . . . . . . . . . . . . . 94. IAS: No Connection to Alarms Board - connection broken . . . . . . 95. IAS: Low Noise Amplifier Fuse Failure . . . . . . . . . . . . . . . 96. IAS: No Redundant Connection to Alarms Board - connection broken . 97. IAS: No Connection to Alarm Board - Radio OOS . . . . . . . . . . 98. IAS: No Redundant Connection to Alarms Board - Radio OOS . . . . 99. IAS: No connection to alarm board - Alarm Board Removed . . . . . 100. IAS: Cabinet Protection System Failure . . . . . . . . . . . . . . 101. IAS: Power Supply Temperature High . . . . . . . . . . . . . . . 102. IAS: Mains A.C. Supply Failure . . . . . . . . . . . . . . . . . . 103. IAS: Fan Tray 0 Failure . . . . . . . . . . . . . . . . . . . . . . 68P02901W26-Q 24 May 2004
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23-15 23-17 23-18 23-20 23-21 23-22 23-23 23-24 23-25 23-26 23-27 23-28 23-29 23-30 23-31 23-32 23-33 23-35 23-37 23-39 23-41 23-43 23-45 23-46 23-47 23-49 23-51 23-53 23-55 23-57 23-58 23-60 23-61 23-62 23-64 23-66 23-68 23-70 23-71 23-73 23-75 23-77 23-79 23-81 23-83 23-85 23-87 23-89 23-91 23-93 23-94 23-96 23-98 23-100 23-102
xi
Contents
104. IAS: Fan Tray 1 Failure . . . . . . . . . . . . . . . . 105. IAS: Fan Tray 2 Failure . . . . . . . . . . . . . . . . 106. IAS: Rectifier Failure . . . . . . . . . . . . . . . . . 107. IAS: Battery Box Temperature High . . . . . . . . . . 108. IAS: Alarm Board Failed . . . . . . . . . . . . . . . 109. IAS: Auxiliary Alarm 1 . . . . . . . . . . . . . . . . 110. IAS: Urgent Critical Alarm . . . . . . . . . . . . . . 111. IAS: Cabinet Protection Board Fuse failure . . . . . . . 112 - 113. IAS: Heat Management System Unit Failure 1 & 2 114 - 115. IAS: Mains A.C. Supply Failure 1 & 2 . . . . . . 116 - 117. IAS: Rectifier Failure 1 & 2 . . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
23-104 23-105 23-107 23-109 23-111 23-113 23-114 23-116 23-117 23-118 23-119
Chapter 24: KSW alarms

Introduction to KSW alarms . . . . . . . . . . . . . . . . . . . . 0. KSW: Parity Highway 0 . . . . . . . . . . . . . . . . . . . . . 1. KSW: Parity Highway 1 . . . . . . . . . . . . . . . . . . . . . 2. KSW: Parity Highway 2 . . . . . . . . . . . . . . . . . . . . . 3. KSW: Parity Highway 3 . . . . . . . . . . . . . . . . . . . . . 4. KSW: Clock A Signal Loss . . . . . . . . . . . . . . . . . . . 5. KSW: Clock B Signal Loss . . . . . . . . . . . . . . . . . . . 6. KSW: 6.12 Second Reference Loss. . . . . . . . . . . . . . . . 7. KSW: Re-Initialized Unexpectedly . . . . . . . . . . . . . . . . 8. KSW: Hard Reset . . . . . . . . . . . . . . . . . . . . . . . . 9. KSW: Watchdog Timer Expired . . . . . . . . . . . . . . . . . 10. KSW: Lost Communication with KSW . . . . . . . . . . . . . 11. KSW: Local Cage KSW TDM Loopback Test Failure . . . . . . 18.- 21. KSW: Failure of Expanded Inbound TDM Highway . . . . . 22.- 24. KSW: KSWX / DSWX in Slot 7-9 Detected Expanded KSW . 25.- 27. KSW: KSWX/DSWX in Slot 21-23 Detected Expanded . . . 224. KSW: Safe Test Audit Failure . . . . . . . . . . . . . . . . . 225. KSW: Internal Loopback Audit Failure . . . . . . . . . . . . 232. KSW: Processor Bus Communication Failure. . . . . . . . . . 254. KSW: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2 24-4 24-8 24-10 24-12 24-14 24-18 24-22 24-24 24-27 24-29 24-32 24-35 24-38 24-41 24-43 24-45 24-47 24-50 24-52
Chapter 25: LAN alarms

Introduction to LAN alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. LAN: lan0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. LAN: LAN Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2 25-3 25-5
Chapter 26: LMTL alarms

Introduction to LMTL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 0. LMTL: Signalling Link Failure . . . . . . . . . . . . . . . . . . . . . . . . 0. LMTL: SL Failure - All Reasons - PM . . . . . . . . . . . . . . . . . . . . . 1. LMTL: SMLC Processor Outage. . . . . . . . . . . . . . . . . . . . . . . . 1. LMTL: Threshold Reached: SL Failure - Abnormal FIBR/BSNR - PM . . . . . . 2. LMTL: Threshold Reached: SL Failure - Excessive Delay of ACK - PM . . . . . 3. LMTL: Link Traffic Too High . . . . . . . . . . . . . . . . . . . . . . . . . 3. LMTL: Threshold Reached: SL Failure - Excessive Error Rate - PM . . . . . . . 4. LMTL: Threshold Reached: SL Failure - Excessive Duration of Congestion - PM . 5. LMTL: Threshold Reached: SL Alignment Failure - PM . . . . . . . . . . . . 6. LMTL: Threshold Reached: Number of Signal Units in Error - PM. . . . . . . . 7. LMTL: Threshold Reached: SL Number of Negative ACKs Received - PM. . . . 8. LMTL: Threshold Reached: Start of Remote Processor Outage - PM . . . . . . .
xii
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
26-2 26-3 26-6 26-8 26-10 26-12 26-14 26-16 26-18 26-20 26-22 26-24 26-26
68P02901W26-Q 24 May 2004
Contents
9. LMTL: Threshold Reached: Number of Octets Retransmitted - PM . . . . 10. LMTL: Threshold Reached: MSUs Discarded due to SL Congestion - PM. 11. LMTL: SL Congestion Events Resulting in Loss of MSUs - PM . . . . . 12. LMTL: Threshold Reached: SL Congestion Indications - PM . . . . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
26-28 26-29 26-30 26-31
Chapter 27: MMS alarms

Introduction to MMS alarms . . . . . . . . . . . . . . . . . . . . . . . 0. MMS: Synchronization Loss Daily Threshold Exceeded . . . . . . . . . 1. MMS: Synchronization Loss Hourly Threshold Exceeded . . . . . . . . 2. MMS: Synchronization Loss OOS Threshold Exceeded . . . . . . . . . 4. MMS: Remote Alarm Daily Threshold Exceeded . . . . . . . . . . . . 5. MMS: Remote Alarm Hourly Threshold Exceeded . . . . . . . . . . . 6. MMS: Remote Alarm OOS Threshold Exceeded . . . . . . . . . . . . 8. MMS: Frame Slip Daily Threshold Exceeded . . . . . . . . . . . . . . 9. MMS: Frame Slip Hourly Threshold Exceeded . . . . . . . . . . . . . 10. MMS: Frame Slip OOS Threshold Exceeded . . . . . . . . . . . . . 12. MMS: Bit Error Daily Threshold Exceeded . . . . . . . . . . . . . . 13. MMS: Bit Error Hourly Threshold Exceeded . . . . . . . . . . . . . 14. MMS: Bit Error OOS Threshold Exceeded . . . . . . . . . . . . . . 16. MMS: Synchronization Loss OOS Timer Expired . . . . . . . . . . . 18. MMS: Remote Alarm OOS Timer Expired . . . . . . . . . . . . . . 20. MMS: Red Alarm Daily Threshold Exceeded . . . . . . . . . . . . . 21. MMS: Red Alarm Hourly Threshold Exceeded . . . . . . . . . . . . 22. MMS: Red Alarm OOS Threshold Exceeded . . . . . . . . . . . . . 23. MMS: Red Alarm OOS Timer Expired . . . . . . . . . . . . . . . . 24. MMS: Modem to NIU Serial Channel Control Link Failure . . . . . . . 25. MMS: HDSL Modem Loop 0 Synch Loss Timer Expired. . . . . . . . 26. MMS: HDSL Modem Loop 1 Synch Loss Timer Expired. . . . . . . . 27. MMS: Master HDSL Modem Loop 0 SNR Daily Threshold Exceeded . 28. MMS: Master HDSL Modem Loop 1 SNR Daily Threshold Exceeded . 29. MMS: Slave HDSL Modem Loop 0 SNR Daily Threshold Exceeded . . 30. MMS: Slave HDSL Modem Loop 1 SNR Daily Threshold Exceeded . . 31. MMS: Master HDSL Modem Loop 0 SNR Hourly Threshold Exceeded . 32. MMS: Master HDSL Modem Loop 1 SNR Hourly Threshold Exceeded . 33. MMS: Slave HDSL Modem Loop 0 SNR Hourly Threshold Exceeded . 34. MMS: Slave HDSL Modem Loop 1 SNR Hourly Threshold Exceeded . 35. MMS: Master HDSL Modem Loop 0 SNR OOS Threshold Exceeded . . 36. MMS: Master HDSL Modem Loop 1 SNR OOS Threshold Exceeded . . 37. MMS: Slave HDSL Modem Loop 0 SNR OOS Threshold Exceeded . . 38. MMS: Slave HDSL Modem Loop 1 SNR OOS Threshold Exceeded . . 39. MMS: LTU Download Failure . . . . . . . . . . . . . . . . . . . . 40. MMS: LTU Configuration Failure . . . . . . . . . . . . . . . . . . 41. MMS: Connectivity Mismatch Between BSC and RXCDR . . . . . . . 42. MMS: DSW/DSWX Switching Hardware Required . . . . . . . . . . 253. MMS: Critical Alarm Threshold Exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3 27-6 27-8 27-10 27-13 27-15 27-17 27-20 27-22 27-24 27-25 27-27 27-29 27-32 27-35 27-38 27-40 27-42 27-45 27-48 27-50 27-53 27-56 27-58 27-60 27-62 27-64 27-66 27-68 27-70 27-72 27-75 27-78 27-81 27-84 27-86 27-87 27-89 27-90
Chapter 28: MSI alarms

Introduction to MSI alarms. . . . . . . . . . 0. MSI: Re-Initialized Unexpectedly . . . . . 1. MSI: Hard Reset . . . . . . . . . . . . . 2. MSI: Watchdog Timer Expired. . . . . . . 3. MSI: Clock B Signal Loss . . . . . . . . . 4. MSI: Clock A Signal Loss . . . . . . . . . 5. MSI: Assigned Timeslot Counter Underflow 68P02901W26-Q 24 May 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-2 28-4 28-6 28-8 28-10 28-11 28-12
xiii
Contents
6. MSI: Assigned Timeslot Counter Overflow . . 7. MSI: TDM Parity Error . . . . . . . . . . . 9. MSI: TRAU Frame Synchronization Loss . . 11.- 70. MSI: DSP Channel (0-59) Audit Failure 224. MSI: Safe Test Audit Failure . . . . . . . 231. MSI: TDM Interface Configuration Failure. 232. MSI: Processor Bus Communication Failure 234. MSI: Active Link Connection Failure . . . 254. MSI: Device Failure . . . . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
28-14 28-16 28-18 28-19 28-22 28-24 28-26 28-28 28-30
Chapter 29: MTL alarms

Introduction to MTL alarms . . . . . . . . . . . . . . . . . . 0. MTL: Signalling Link Failure . . . . . . . . . . . . . . . . 0. MTL: SL Failure - All Reasons - PM . . . . . . . . . . . . . 1. MTL: MSC Processor Outage . . . . . . . . . . . . . . . . 1. MTL: SL Failure - Abnormal FIBR/BSNR - PM . . . . . . . 2. MTL: SL Failure - Excessive Delay of ACK - PM . . . . . . 3. MTL: Link Traffic Too High. . . . . . . . . . . . . . . . . 3. MTL: SL Failure - Excessive Error Rate - PM . . . . . . . . 4. MTL: SL Failure - Excessive Duration of Congestion - PM . . 5. MTL: SL Alignment Failure - PM . . . . . . . . . . . . . . 6. MTL: Number of Signal Units in error - PM . . . . . . . . . 7. MTL: SL Number of Negative Acks Received - PM . . . . . . 8. MTL: Start of Remote Processor Outage - PM . . . . . . . . 9. MTL: Number of Octets Retransmitted - PM . . . . . . . . . 10. MTL: MSUs Discarded due to SL Congestion - PM . . . . . 11. MTL: SL Congestion Events Resulting in Loss of MSUs - PM 12. MTL: SL Congestion Indications - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-2 29-3 29-6 29-7 29-8 29-9 29-10 29-12 29-13 29-14 29-16 29-18 29-20 29-21 29-22 29-23 29-24
Chapter 30: OMC-R alarms

Introduction to OMC-R alarms . . . . . . . . . . 30000. OMC: downloadFailed . . . . . . . . . . 30001. OMC: uploadFailed . . . . . . . . . . . 30002. OMC: filexferFailed . . . . . . . . . . . 30003. OMC: x25CircuitDown. . . . . . . . . . 30004. OMC: parserDisconnectedTooLong . . . . 30005. OMC: NE Response Timeout . . . . . . . 30006. OMC: NE Error State . . . . . . . . . . 30007. OMC: PMDisconnectedFromDB . . . . . 30008. OMC: EMDisconnectedFromDB . . . . . 30009. OMC: dbCompressionFailed . . . . . . . 30010. OMC: Exceeds upper limit disk usage . . . 30011. OMC: Exceeds lower limit disk usage . . . 30012. OMC: Level 1/2/3 Failure . . . . . . . . 30014. OMC: Database exceeds upper limit . . . . 30015. OMC: pmProxyDisconnectedFromDB. . . 30016. OMC: osiStackError . . . . . . . . . . . 30017. OMC: CSFPdownloadFailed . . . . . . . 30018. OMC: dbUncompressionFailed . . . . . . 30019. OMC: Database exceeds lower limit . . . . 30020. OMC: VersionQueryFailed . . . . . . . . 30021. OMC: OMC Overloaded with Events . . . 30022. OMC: OMC Overloaded, Events Discarded 30023. OMC: downloadDisabled . . . . . . . . .
xiv
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
30-3 30-4 30-6 30-8 30-11 30-14 30-16 30-18 30-20 30-22 30-24 30-26 30-29 30-31 30-33 30-35 30-36 30-37 30-39 30-41 30-43 30-49 30-51 30-53
68P02901W26-Q 24 May 2004
Contents
30024. 30025. 30026. 30027. 30064. 30029. 30030. 30031. 30032. 30033. 30035. 30036. 30037. 30038. 30039. 30050. 30051. 30052. 30060.
OMC: CSFPSwapFailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: nmcAgentError . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: Neighbour statistics table exceeded the configured size. Operator must take action . OMC: supplDownloadFailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: Memory usage exceeds upper limit . . . . . . . . . . . . . . . . . . . . . . . OMC: Active Alarms exceed upper limit of 95% . . . . . . . . . . . . . . . . . . . . OMC: Received Maximum Corrupt NE Msgs, Closed OML . . . . . . . . . . . . . . OMC: Resync Timed Out, No Response From NE . . . . . . . . . . . . . . . . . . . OMC: Resync Timed Out, All Resync Events Not Received. . . . . . . . . . . . . . . OMC: Cannot create further event logfiles in /usr/gsm/ne_data. . . . . . . . . . . . . . OMC: Advisory Detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: Recovered Outage Detected . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: UPS condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: OMC Capacity Ceiling Violation, too many RTFs in MIB. . . . . . . . . . . . . OMC: OMC Capacity Ceiling Violation, too many NEs in MIB . . . . . . . . . . . . . OMC: Solaris2 Hardware Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: Corrupt NE File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: Corrupt SITE file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC: noActivityInTimeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
30-55 30-57 30-60 30-62 30-65 30-66 30-68 30-71 30-73 30-75 30-78 30-79 30-80 30-82 30-84 30-86 30-89 30-90 30-91
Chapter 31: OML alarms

Introduction to OML alarms . . . . . . 0. OML: Invalid Received Frames - PM 1. OML: FRMR-Frames - PM . . . . . 2. OML: Expiration of N2 - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-2 31-3 31-4 31-5
Chapter 32: PBUS alarms

Introduction to PBUS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254. PBUS: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-2 32-3
Chapter 33: PCU alarms

Introduction to PCU alarms . 0. PCU: Last GSL Failed . . 1. PCU: PCU Audit Failure . 2. PCU: Cell Mapping Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-2 33-3 33-5 33-7
Chapter 34: PPB alarms

Introduction to PPB alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. PPB: PCI Bridge Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-2 34-3
Chapter 35: PSP alarms

Introduction to PSP alarms . . . . . . . . 0. PSP: Communication Failure . . . . . 22. PSP: SWFM Indication . . . . . . . 39. PSP: Software Failure . . . . . . . . 239. PSP: Process Safe Test Audit Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-2 35-3 35-5 35-6 35-7
Chapter 36: RSL alarms

Introduction to RSL alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. RSL: Invalid Received Frames - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-2 36-3
68P02901W26-Q 24 May 2004
xv
Contents
1. RSL: FRMR-Frames - PM. . . . . . . . . . . . 2. RSL: Expiration of N2 - PM . . . . . . . . . . . 10. RSL: Link Disconnected . . . . . . . . . . . . 11. RSL: LAPD Protocol Error . . . . . . . . . . . 13. RSL: LAPD Protocol Error Threshold Exceeded . 14. RSL: Link Audit Failure . . . . . . . . . . . . 15. RSL: Too Many LAPD Protocol Errors . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
36-4 36-5 36-6 36-14 36-17 36-19 36-21
Chapter 37: SBUS alarms

Introduction of SBUS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254. SBUS: Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37-2 37-3
Chapter 38: SITE alarms

Introduction to SITE alarms . . . . . . . . . . . . . . . . . . . . . . 0. SITE: Last RSL Link Failure . . . . . . . . . . . . . . . . . . . . 2. SITE: BSC Detected MCU to MCU Communication Failure . . . . . . 3. SITE: Active Multiplexer 0 Loopback Failure. . . . . . . . . . . . . 4. SITE: Standby Multiplexer 0 Loopback Failure . . . . . . . . . . . . 5. SITE: Active Multiplexer 1 Loopback Failure. . . . . . . . . . . . . 6. SITE: Standby Multiplexer 1 Loopback Failure . . . . . . . . . . . . 7. SITE: Active Multiplexer 2 Loopback Failure. . . . . . . . . . . . . 8. SITE: Standby Multiplexer 2 Loopback Failure . . . . . . . . . . . . 9. SITE: Active Local FOX Failure . . . . . . . . . . . . . . . . . . . 10. SITE: Standby Local FOX Failure . . . . . . . . . . . . . . . . . 11. SITE: Active Remote FOX 0 Failure . . . . . . . . . . . . . . . . 12. SITE: Standby Remote FOX 0 Failure . . . . . . . . . . . . . . . 13. SITE: Active Remote FOX 1 Failure . . . . . . . . . . . . . . . . 14. SITE: Standby Remote FOX 1 Failure . . . . . . . . . . . . . . . 15. SITE: Active Remote FOX 2 Failure . . . . . . . . . . . . . . . . 16. SITE: Standby Remote FOX 2 Failure . . . . . . . . . . . . . . . 17. SITE: 16Kbps Switching Hardware Required . . . . . . . . . . . . 18. SITE: MIX Board (Slot 18) Communication Failure . . . . . . . . . 19. SITE: Unequipped GPROC has Entered the LAN . . . . . . . . . . 20. SITE: Unequipped GPROC Has Left the LAN . . . . . . . . . . . . 21. SITE: No Clock References Available. . . . . . . . . . . . . . . . 22. SITE: Active Alarm List Full . . . . . . . . . . . . . . . . . . . . 23. SITE: EMU Modem Card Failure . . . . . . . . . . . . . . . . . 24. SITE: Site Reset Request. . . . . . . . . . . . . . . . . . . . . . 25. SITE: External Power Booster Amplifier 1 Failure . . . . . . . . . . 26. SITE: External Power Booster Amplifier 2 Failure . . . . . . . . . . 27. SITE: External Power Booster Failure. . . . . . . . . . . . . . . . 28. SITE: Database Configuration and Arena Hardware Mismatch . . . . 29. SITE: EMU Download Failure . . . . . . . . . . . . . . . . . . . 30. SITE: NVM Board Failure . . . . . . . . . . . . . . . . . . . . . 31. SITE: Failure of PCMCIA Card 1 on NVM Board . . . . . . . . . . 32. SITE: Last GBL Failed. . . . . . . . . . . . . . . . . . . . . . . 33. SITE: BSSGP Status Message Received from the SGSN . . . . . . . 34. SITE: Erroneous BSSGP Message Received from the SGSN . . . . . 35. SITE: Network Service Status Message Received from the SGSN . . . 36. SITE: Erroneous Network Service Message Received from the SGSN . 37. SITE: No NS-VC Block Acknowledgement from the SGSN . . . . . 38. SITE: No NS-VC Unblock Acknowledgement from the SGSN . . . . 39. SITE: No NS-VC Alive Acknowledgement from the SGSN . . . . . 40. SITE: No NS-VC Reset Acknowledgement from the SGSN . . . . .
xvi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38-3 38-4 38-12 38-15 38-17 38-19 38-21 38-23 38-25 38-27 38-29 38-31 38-33 38-35 38-37 38-39 38-41 38-43 38-45 38-46 38-49 38-53 38-56 38-58 38-59 38-63 38-65 38-67 38-69 38-72 38-75 38-76 38-77 38-79 38-80 38-81 38-82 38-83 38-84 38-85 38-87
68P02901W26-Q 24 May 2004
Contents
41. 42. 43. 44. 45. 46.
SITE: Last NS-VC for the PCU failed. . . . . . . . . . . . . . . SITE: Last TRAU GDS Failed . . . . . . . . . . . . . . . . . . SITE: Last PRP DPROC Failed. . . . . . . . . . . . . . . . . . SITE: 50% of the PCU NS-VCs Failed . . . . . . . . . . . . . . SITE: No Signalling BVC Reset Acknowledgement from the SGSN SITE: DSW Switching Hardware Required at Site . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
38-89 38-91 38-92 38-93 38-94 38-95
Chapter 39: TBUS alarms

Introduction to TBUS alarms . . . . . . . . . 0. TBUS: Remote KSW Loopback Test Failure 3. TBUS: Local KSWX/DSWX TDM Error. . 4. TBUS: Remote KSWX/DSWX TDM Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-2 39-3 39-5 39-6
Chapter 40: TIMESLOT alarms

Introduction to TIMESLOT alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0. TIMESLOT: Radio Frequency Losses While Using a TCH - PM . . . . . . . . . . . . . . . . . . . . 1. TIMESLOT: Channel Request From MS Failed - PM . . . . . . . . . . . . . . . . . . . . . . . . . 40-2 40-3 40-5
Chapter 41: TRU alarms

Introduction to TRU alarms . . . . . . . 0. TRU: Door Open . . . . . . . . . . . 1. TRU: Power Supply Unit Failure . . . 2. TRU: Power Mains Failure . . . . . . 5.- 6. TRU: Customer Defined Alarm 1-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-2 41-3 41-4 41-6 41-8
Chapter 42: XBL alarms

Introduction to XBL alarms . . . . . . . . . . . . 0. XBL: Invalid Received Frames - PM . . . . . . . 1. XBL: FRMR-Frames - PM . . . . . . . . . . . 2. XBL: Expiration of N2 - PM . . . . . . . . . . 10. XBL: Link Disconnected . . . . . . . . . . . . 11. XBL: LAPD Protocol Error . . . . . . . . . . 13. XBL: LAPD Protocol Error Threshold Exceeded 15. XBL: Too Many LAPD Protocol Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-2 42-3 42-4 42-5 42-6 42-9 42-11 42-14
68P02901W26-Q 24 May 2004
xvii
Contents
This page intentionally left blank.
xviii
68P02901W26-Q 24 May 2004
List of Tables
List of Tables
Table 1: Manual version history . . . . . . . . . . . . . . . Table 2: Service requests resolved in this manual . . . . . . . Table 1-1: OMC-R consolidation variables . . . . . . . . . . Table 1-2: Device information fields . . . . . . . . . . . . . Table 1-3: Alarm categories . . . . . . . . . . . . . . . . . Table 1-4: Reconfiguration information fields . . . . . . . . . Table 1-5: Severity display colours . . . . . . . . . . . . . . Table 1-6: Functional unit impact colours . . . . . . . . . . . Table 5-1: BSP FRUs . . . . . . . . . . . . . . . . . . . . Table 5-2: Error codes . . . . . . . . . . . . . . . . . . . . Table 5-3: Site reset type. . . . . . . . . . . . . . . . . . . Table 6-1: If group_block_unblock_allowed = 0 . . . . . . . . Table 6-2: If group_block_unblock_allowed = 1 . . . . . . . . Table 6-3: If group_block_unblock_allowed = 0 . . . . . . . . Table 6-4: If group_block_unblock_allowed = 1 . . . . . . . . Table 6-5: Additional information field contents . . . . . . . . Table 6-6: Additional information field contents . . . . . . . . Table 6-7: Additional information field contents . . . . . . . . Table 6-8: Additional information field values. . . . . . . . . Table 6-9: Additional information field values. . . . . . . . . Table 7-1: BTP FRUs . . . . . . . . . . . . . . . . . . . . Table 7-2: Additional information field contents . . . . . . . . Table 7-3: Additional information field contents . . . . . . . . Table 8-1: CAB FRUs . . . . . . . . . . . . . . . . . . . . Table 9-1: Additional information field contents . . . . . . . . Table 9-2: Additional information field contents . . . . . . . . Table 9-3: Additional information field contents . . . . . . . . Table 9-4: Additional information field contents . . . . . . . . Table 9-5: Additional information field contents . . . . . . . . Table 9-6: Additional information field contents . . . . . . . . Table 9-7: Additional information field contents . . . . . . . . Table 12-1: Reason codes . . . . . . . . . . . . . . . . . . Table 12-2: Additional information field contents . . . . . . . Table 13-1: FRUs that may be equipped with the COMB device Table 13-2: Additional information field contents . . . . . . . Table 13-3: Additional information field contents . . . . . . . Table 13-4: Additional information field contents . . . . . . . Table 13-5: Additional information field contents . . . . . . . Table 13-6: Additional information field contents . . . . . . . Table 13-7: Additional information field contents . . . . . . . Table 13-8: Additional information field contents . . . . . . . Table 13-9: Additional information field contents . . . . . . . 68P02901W26-Q 24 May 2004
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 3 1-5 1-8 1-10 1-13 1-20 1-20 5-2 5-34 5-36 6-14 6-15 6-16 6-17 6-18 6-22 6-28 6-36 6-65 7-3 7-45 7-47 8-2 9-4 9-7 9-18 9-21 9-24 9-27 9-30 12-4 12-12 13-2 13-3 13-5 13-7 13-9 13-11 13-13 13-16 13-18
xix
List of Tables
Table 13-10: Additional information field contents . . . . . Table 13-11: Additional information field contents. . . . . . Table 13-12: Additional information field contents . . . . . Table 13-13: Additional information field contents . . . . . Table 14-1: FRUs that may be equipped with the CSFP device Table 15-1: FRUs that may be equipped with the DHP device Table 15-2: Error codesError codes . . . . . . . . . . . . . Table 15-3: Site reset type . . . . . . . . . . . . . . . . . Table 16-1: DPROC FRUs . . . . . . . . . . . . . . . . . Table 16-2: Reset type . . . . . . . . . . . . . . . . . . . Table 16-3: Error codes . . . . . . . . . . . . . . . . . . Table 17-1: FRUs that may be equipped with the DRI device . Table 17-2: Additional information field contents . . . . . . Table 17-3: Additional information field contents . . . . . . Table 17-4: Additional information field contents . . . . . . Table 17-5: Additional information field contents . . . . . . Table 17-6: Additional information field contents . . . . . . Table 17-7: Additional information field contents . . . . . . Table 17-8: Additional information field contents . . . . . . Table 17-9: Additional information field contents . . . . . . Table 17-10: Additional information field contents . . . . . Table 17-11: Additional information field contents. . . . . . Table 17-12: Additional information field contents . . . . . Table 17-13: Additional information field contents . . . . . Table 17-14: Additional information field contents . . . . . Table 17-15: Additional information field contents . . . . . Table 17-16: Additional information field contents . . . . . Table 17-17: Additional information field contents . . . . . Table 17-18: Additional information field contents . . . . . Table 17-19: Additional information field contents . . . . . Table 17-20: Additional information field contents . . . . . Table 17-21: Additional information field contents . . . . . Table 17-22: Additional information field contents . . . . . Table 17-23: Additional information field contents . . . . . Table 17-24: Additional information field contents . . . . . Table 17-25: Additional Information field contents . . . . . Table 17-26: Additional information field contents . . . . . Table 20-1: GCLK FRUs . . . . . . . . . . . . . . . . . Table 20-2: Additional information fields contents. . . . . . Table 20-3: Additional information fields contents. . . . . . Table 20-4: GCLK timer settings . . . . . . . . . . . . . . Table 20-5: Additional information field contents . . . . . . Table 20-6: LTA calibration limits . . . . . . . . . . . . . Table 21-1: GPROC FRUs . . . . . . . . . . . . . . . . . Table 21-2: Error codes . . . . . . . . . . . . . . . . . . Table 21-3: Site reset type . . . . . . . . . . . . . . . . . Table 22-1: Additional information field contents . . . . . . Table 22-2: Additional information field contents . . . . . . Table 22-3: LAPD error indications. . . . . . . . . . . . . Table 24-1: KSW FRUs . . . . . . . . . . . . . . . . . . Table 24-2: Additional information field contents . . . . . . Table 26-1: Additional information field contents . . . . . . Table 27-1: MMS FRUs . . . . . . . . . . . . . . . . . . Table 28-1: FRUs on which the MSI device may be equipped Table 28-2: Additional information field contents . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13-20 13-22 13-24 13-26 14-2 15-3 15-55 15-57 16-2 16-5 16-9 17-8 17-9 17-11 17-13 17-15 17-17 17-21 17-23 17-25 17-27 17-29 17-33 17-35 17-63 17-68 17-70 17-72 17-74 17-80 17-108 17-110 17-191 17-250 17-277 17-282 17-290 20-2 20-5 20-8 20-25 20-26 20-45 21-3 21-47 21-49 22-7 22-10 22-10 24-2 24-4 26-3 27-4 28-2 28-19
xx
68P02901W26-Q 24 May 2004
List of Tables
Table 29-1: Table 30-1: Table 30-2: Table 33-1: Table 35-1: Table 35-2: Table 36-1: Table 36-2: Table 36-3: Table 36-4: Table 36-5: Table 36-6: Table 38-1: Table 38-2: Table 38-3: Table 42-1: Table 42-2: Table 42-3:
Additional information field contents . OMC: UPS condition alarm severities. Additional information field contents . Additional information field contents . PSP FRUs . . . . . . . . . . . . . . Error codes . . . . . . . . . . . . . Additional information field contents . Additional information field contents . LAPD error codes . . . . . . . . . . Additional information field contents . Additional information field contents . Additional information field contents . Additional information field contents . Additional information field contents . Process identifier (PID) number. . . . Additional information field contents . LAPD error codes . . . . . . . . . . Additional information field contents .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
29-4 30-80 30-87 33-5 35-2 35-7 36-7 36-14 36-14 36-17 36-19 36-21 38-54 38-60 38-60 42-6 42-9 42-11
68P02901W26-Q 24 May 2004
xxi
List of Tables
xxii
68P02901W26-Q 24 May 2004
About This Manual
What is Covered In This Manual?

This document comprises a two-volume manual that 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.
68P02901W26-Q 24 May 2004
Issue status of this manual

The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue: Table 1 Manual version history Date of issue 03 Oct 1994 30 Dec 1994 01 Sep 1995 28 Mar 1997 29 Aug 1997 27 April 1998 12 Mar 1999 15 July 2000 31 Jul 2001 31 May 2002 20 Nov 2002 02 May 2003 13 Nov 2003 24 May 2004 Remarks Original issue - Software release GSR 1.2.2.X Issue A - Software release 1.2.3.x Issue C - Software release 1.4.0.x Issue D - Software release 1.4.1.x Issue E - GSM Software release 2 Issue F - GSM Software release 3 Issue G - GSM Software release 4 Issue H - GSM Software release 4.1 Issue J - GSM Software release 5 Issue K - GSM Software release 5.1 Issue L - GSM Software release 6 Issue M - GSM Software release 6 (Horizon II) Issue P - GSM Software release 7 Issue Q - GSM Software release 7 Half Rate (Controlled Introduction)
Manual issue O A C D E F G H J K L M P Q
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
68P02901W26-Q 24 May 2004
Table 2
Service requests resolved in this manual GMR Number N/A N/A Remarks Configuration options for alarm 253. MMS: Critical Alarm Threshold Exceeded, explained in more detail. Section on Alarm 26. BSS: Received Page for Invalid Cell from MSC amended. Instructions now included on how cell id can be derived from the Additional Information Field. Description on Alarm IAS 110 was perceived to be confusing. The description has been amended to remove confusion. DRI alarms 104 to 111 are not described. These alarms have now been described. Description of RSL(11) alarm did not include enough information to enable fault isolation. Extra notes have been added. Several BSS alarms had insufficient explanation for any Additional Data. This has been rectified.
Service Request 1065791 1065858
1073166
N/A
1071117 1064113
N/A N/A
1100183
N/A
68P02901W26-Q 24 May 2004
General information
General information
Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or any one acting on the customers behalf, to abide by the instructions, system parameters or recommendations made in this manual If this manual was obtained when attending a Motorola training course, it will not be 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 corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals, new and amended features are tagged to help users to assess the impact on installed networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with page references and hot links in electronic copy.
68P02901W26-Q 24 May 2004
General information
The tags have the format: {nnnn} or {nnnnn} Where: {nnnn} {nnnnn} The tags are positioned in text as follows: New and amended feature information New sentence/s or new or amended text. Complete new blocks of text as follows: Full sections under a main heading Full paragraphs under subheadings Tag position in text Immediately before the affected text. Immediately after the headings as follows: Main heading Subheading is: the RDB number the RDP number
New or amended complete Figures and Tables Warning, Caution and Note boxes. General command syntax, operator input or displays (in special fonts).
After the Figure or Table number and before the title text. Immediately before the affected text in the box. On a separate line immediately above the affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names. The references to external publications are shown in italics, chapter and section name cross references are emphasised blue in text. This manual is divided into uniquely identified and numbered chapters that, in turn, 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.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardised, or may not be present at all in some parts of the network in which it is normally implemented. The manual set, of which this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
68P02901W26-Q 24 May 2004
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CTRL-c ALT-f CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return key.
68P02901W26-Q 24 May 2004
Reporting safety issues
Reporting safety issues

Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: Procedure 1 1 2 3 Safety issue reporting Make the equipment concerned safe, for example by removing power. Make no further attempt to adjust or rectify the equipment. Report the problem directly to the Customer Network Resolution Centre, Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.
68P02901W26-Q 24 May 2004
Warnings and cautions

The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Cautions
A definition and example follow below:
68P02901W26-Q 24 May 2004
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date; arrange for calibration to be carried out.
68P02901W26-Q 24 May 2004
General warnings
General warnings
Observe the following specific warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals: Potentially hazardous voltage. Electric shock. RF radiation. Laser radiation. Heavy equipment. Parts substitution. Battery supplies. Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into procedures as applicable. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, in the illustrations and on the equipment.
10
68P02901W26-Q 24 May 2004
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single phase or 415 V a.c. three phase supply. To achieve isolation of the equipment from the a.c. supply, the a.c. input isolator must be set to off and locked. When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. In cases of low voltage electric shock (including public supply voltages), serious injuries and even death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It can also cause skin burns at the points of entry and exit of the current. In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained first aid or medical assistance arrives.
RF radiation
High RF potentials and electromagnetic fields are present in this equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders.
68P02901W26-Q 24 May 2004
11
General warnings
Relevant standards (USA and EC), to which regard should be paid 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 CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipment has to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Parts substitution
Do not install substitute parts or perform any unauthorized modification of equipment, because of the danger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety features are maintained.
12
68P02901W26-Q 24 May 2004
General warnings
Battery supplies
Do not wear earth straps when working with stand-by battery supplies. Use only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must not be removed or replaced. Any boards containing defective lithium batteries must be returned to Motorola for repair. Contact your local Motorola office for how to return defective lithium batteries.
68P02901W26-Q 24 May 2004
13
General cautions
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor (MOS) devices are susceptible to damage from electrostatic charge. See the section Devices sensitive to static in the preface of this manual for further information.
14
68P02901W26-Q 24 May 2004
Devices sensitive to static
Devices sensitive to static

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads short circuited together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are short circuited it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following precautions when handling the replacement: Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
68P02901W26-Q 24 May 2004
15
Motorola manual set
Motorola manual set

The Motorola manual sets provide the information needed to operate, install and maintain the Motorola equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media: Printed hard copy. Electronic, as fully navigable PDF files on: The Motorola customer support web site at: (https://mynetworksupport.motorola.com/index.asp). CD-ROM produced in support of a major system software release. Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release, together with current versions of appropriate hardware manuals, and has additional navigation facilities. A snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent point releases. The CD-ROM does not include Release Notes or documentation supporting specialist products such as MARS or COP.
Ordering manuals and CD-ROMs

Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs. All orders must be placed with your Motorola Local Office or Representative.
16
68P02901W26-Q 24 May 2004
GMR amendment
GMR amendment
Changes to a manual that occur after the printing date are incorporated into the manual using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue.
GMR availability
GMRs are published as follows: Printed hard copy - Complete replacement content or loose leaf pages with amendment list. Remove and replace pages in this manual, as detailed on the GMR instruction sheet. Motorola service web - Updated at the same time as hard copies. CD-ROM - Updated periodically as required.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to record the GMR. Retain the instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference.
68P02901W26-Q 24 May 2004
17
GMR amendment
GMR amendment record

Record the insertion of GMRs in this manual in the following table: GMR number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 Incorporated by (signature) Date
18
68P02901W26-Q 24 May 2004
Chapter
Introduction to alarm handling
This first chapter provides an overview of how alarms are organised 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-Q 24 May 2004
1-1
Manual introduction
Manual introduction
Manual organization
Chapters
Device alarms are presented in separate chapters and organized in alphabetical order by device name: ABSS, and then AXCDR, and then 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 use in resolving the alarm.
Performance Management (PM) alarms

PM alarms are generated by the PM subsystem and reported 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. This differentiates device and PM alarms that have the same numerical designation, for example: Device alarm 0: BSS: Last MTL Link Failure - Signalling Point Inaccessible PM alarm 0: BSS: Paging Request From MSC Protocol Error - PM
1-2
68P02901W26-Q 24 May 2004
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 are reported by the OMC-R, including alarm messages.
Alarm messages
An alarm message is generated in response to a fault condition in a device or function. A fault condition may occur 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 set up by the operator. Refer to the Operating Information: GSM System Operation (68P02901W01) manual for event and alarm handling procedures, including subscription creation.
68P02901W26-Q 24 May 2004
1-3
Alarm types
Alarm types
Untagged alarms
Throughout this manual new and amended features are tagged to help users 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 a device reconfiguration.
If alarms consolidation is not enabled, all alarms are displayed as untagged, including alarms that are associated with 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*. communicationFailureEvent - SITE - Trunk10: 20 SITE - 29/03/2000 14:25:03. [0] Last RSL Link Failure - FMIC Critical -/-.
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.
1-4
68P02901W26-Q 24 May 2004
Alarm types
Primary alarm
A primary alarm is the 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. The OMC-R CONSOLIDATION environment variable must be set to 1 to display secondary alarms.
Refer to the Operating Information: GSM System Operation (68P02901W01) manual 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 0 1 2 3 Descriptions Disable the alarms consolidation feature. Display both primary and secondary alarms Display only primary alarms. Display only primary alarms and select the subscriber mode as the default map display mode.
68P02901W26-Q 24 May 2004
1-5
Alarm types
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: #ID - State - Operator - Comment 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 Additional Information When a tagged alarm is initially reported, the device alarm information is displayed in an unexpanded format that includes the *More Details* identifier. The following example shows an unexpanded tagged alarm. #7 - SEEN - *NONE*. communicationFailureEvent - SITE - Trunk10: 20 SITE - 29/03/2000 14:25:03. [0] Last RSL Link Failure - FMIC - Critical -/-. *More Details*. Tagged alarms may be expanded to present reconfiguration information by highlighting the tagged alarm and then selecting Show from the Alarm Details option on the Alarms pop-up menu. The following example shows an expanded primary alarm. #7 - SEEN - *NONE*. communicationFailureEvent - 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-Q 24 May 2004
Alarm types
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. is slightly different than 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: #ID - State - Operator - Comment Alarm Category - Device Class - Device Instance - Date - Time Alarm Code - Clearing Type - Alarm Severity - Error Reason Additional Information 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 EquipmentFailure alarm. This prevents the loss of state change information. State change warning alarms are presented in the following format: #ID - State - Operator - Comment 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-Q 24 May 2004
1-7
Device alarm information
Device information
Device alarm information is provided for both tagged and untagged alarms. Table 1-2 lists the individual fields and possible values. Table 1-2 Device information fields Field #ID State Description Identifier associated with alarm. Operator Comment Alarm category NEW SEEN HANDLING DEFERRED CLEARED
Operator who is handling the alarm. Comment field to be checked for notes related previous instance of alarm. Communication Quality of service Processing Equipment Environment Link NHA Event
Device class Device instance Time Date Alarm code
Device generating the alarm. Site and device identifiers for the faulty device the alarm. Time and date the alarm occurred. The alarm number and text string.
1-8
68P02901W26-Q 24 May 2004
Table 1-2
Device information fields (Continued) Field Description Critical Major Minor Warning Investigate Clear FMIC Intermittent OIC
Alarm severity
Clearing types
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 alarms include the hardware version. 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.
Hardware Version Information Additional Information
Alarm states
The alarm state indicates the current status of each alarm in the Alarm window. This allows the operator to quickly determine what actions are required, if any, to clear the alarm.
NEW
When an alarm is received by the OMC-R, it is automatically assigned the NEW state. This indicates that the alarm was received but has not been acknowledged.
SEEN
When a NEW alarm is selected by an operator, its status is changed from NEW to SEEN. This indicates that the alarm has been acknowledged by an operator.
HANDLING
When an operator starts the alarm resolution process, the operator must change the alarm status to HANDLING. This indicates to anyone reviewing the Alarms window that action is being taken to clear the alarm.
68P02901W26-Q 24 May 2004
1-9
DEFERRED
When an alarm is deferred by the OMC-R operator, it is displayed for five 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 Communication Quality of Service Processing Equipment Environmental Link NHA Event OMC-R communicationFailureEvent qualityOfServiceFailureEvent processingFailureEvent equipmentFailureEvent environmentFailureEvent linkFailureEvent NHA-Event BSS Communication Quality of Service Processing Equipment Environmental Equipment 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.
Processing
A Processing alarm indicates a software or processing fault.
Equipment
An Equipment alarm indicates a hardware failure.
1-10
68P02901W26-Q 24 May 2004
Environmental
An Environmental alarm indicates a change occurred in a physical location.
Link
A Link alarm indicates a fault exists in the X.25 link connection between the OMC-R and a network element.
NHA Event
An NHA Event alarm indicates a network problem was detected by the NHA.
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, but should be resolved to avoid a more serious fault later.
Warning
A warning alarm indicates the existence of a non-service affecting fault condition. Warning alarms should be resolved to avoid a more serious fault later.
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 has been resolved.
Clearing types
After a fault condition is resolved, the alarm must be cleared at the OMC-R. There are three alarm clearing types.
68P02901W26-Q 24 May 2004
1-11
FMIC
FMIC alarms are automatically cleared by the BSS or OMC-R FM subsystem when the fault condition that caused the alarm is resolved. The system reports every occurrence of an FMIC alarm.
OIC
OIC alarms must be cleared by the OMC-R operator after the fault condition that caused the alarm is resolved. The system reports an OIC alarm only once.
Intermittent
Intermittent alarms are transient and not usually 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-Q 24 May 2004
Reconfiguration 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 as the result of a fault or an operator action.
Remote reconfiguration
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 Reconfiguration information fields Field Cause Description The reconfiguration was the result of one of the following events: Fault OMC request LMT request Initialization Restoration Remote
68P02901W26-Q 24 May 2004
1-13
Table 1-4 Operation
Reconfiguration information fields (Continued) Field Description The reconfiguration was performed by one of the following actions: Unequip Equip Unlock Lock Shutdown 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 that is 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. This is an optional field that is displayed only if the alarm is a secondary alarm. Secondary is the only value that is displayed in this field. This is a number used to identify the primary and all secondary alarms associated with a specific device reconfiguration.
Secondary
Config Tag
1-14
68P02901W26-Q 24 May 2004
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 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 BTP CBL CBUS COMB DHP EAS GCLK GPROC KSW MSI/MMS (circuit) MTL OML PATH RSL SITE TBUS TDM XBL
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-Q 24 May 2004
1-15
Impact list
Alarm impact
The impact of the device alarm for each FU indicates the affect 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 a loss of service alarm.
Loss of redundancy
This is a condition causing a loss of redundancy (back up devices) at a site that may or may not affect service to a site. Prompt action required to reduce the possibility of a more serious condition occurring.
1-16
68P02901W26-Q 24 May 2004
OOS device list
OOS device list
Device state
The Out of Service (OOS) device list displays all of the devices taken OOS as a result 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 taken OOS. A maximum of 20 devices may 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-Q 24 May 2004
1-17
Additional information field
Alarm handling
Some alarms reported by the BSS include additional information to assist the operator in alarm handling. Additional information may appear 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 may include error codes to identify the cause of an alarm.
When viewing the Additional Information Field, bytes displayed that are additional to those described in this manual should be ignored.
1-18
68P02901W26-Q 24 May 2004
OMC-R map display modes
OMC-R maps
OMC-R maps may display alarms in one of two modes: device and subscriber.
The CONSOLIDATION environment variable must be set to 1, 2, or 3 to permit alarms to be displayed on maps 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 on either the Impact on Devices or Impact on Subscriber option in the View drop-down menu.
Map display colours

Severity display colours
Colours indicate the severity for all alarms in the device mode and untagged alarms in the subscriber mode. Table 1-5 presents the default icon colours and corresponding alarm severities.
68P02901W26-Q 24 May 2004
1-19
Table 1-5
Severity display colours Icon colour Severity Critical Major Minor Warning Investigate Normal (Clear; no alarms)
Red Yellow Blue Pink Light Blue Green
Functional unit impact colours

Colours indicate the impact of an alarm on an FU in the subscriber mode. Table 1-6 presents the default icon colours and the corresponding alarm impacts. Table 1-6 Functional unit impact colours Icon colour Red Yellow Blue Pink Light Blue Green Loss of Service Loss of Capacity Loss of Redundancy Warning (untagged alarm) Investigate (untagged alarm) Normal (Clear; no alarms) Severity
1-20
68P02901W26-Q 24 May 2004
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-Q 24 May 2004
2-1
0. ABSS: Last XBL Link Failure

Clearing Type: Severity Level: Category: FMIC Critical 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 may attempt to use the blocked CIC resulting in no audio.

There is no additional information in the output for this alarm.
Possible cause(s)
The following are 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-Q 24 May 2004
Procedure
Procedure 2-1 1 Restore XBL to service
Attempt to restore the XBL identified in the alarm message to service If the XBL... Then...
returns to service... does not return to service... 2
No further action is required. Go to step 2.
Determine if any operator actions caused the alarm, such as locking an MSI, MMS, or the last XBL device. If operator action ... caused the alarm... Then... After the operator action is complete, return the XBL to service. If the XBL does not return to service, go to step 3. Go to step 3. Then... 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. Go to step 4. Then... Troubleshoot the XBL alarms. Go to step 5. Then... Troubleshoot the MMS alarms. 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.
did not cause the alarm... 3 If a BSC reset... occurred...
Review Events window to determine if a BSC reset occurred.
did not occur.. 4 If XBL alarms... are present... are not present... 5 If MMS alarms... are present... are not present...
Review the Events window for XBL alarms.
Review the Events window for alarms on the MMS on which the XBL is equipped.
68P02901W26-Q 24 May 2004
2-3
1. ABSS: RXCDR Detecting CIC Validation Failure

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. No calls are handled by the RXCDR from the BSC until the problem is resolved. CICs are not blocked at the MSC, but only certain CICs are actually capable of handling traffic. This may cause CERM alarms and high rates of incomplete calls.

Possible cause(s)
The following are possible causes for this alarm: LAPD errors on the XBL link. The XBL link or switching equipment between the BSC and the RXCDR is malfunctioning.
Procedure
Procedure 2-2 1 Restore ABSS to service
Attempt to restore the ABSS to service. If the ABSS... returns to service... Then... No further action is required.
2-4
68P02901W26-Q 24 May 2004
Procedure 2-2 2
Restore ABSS to service (Continued) Go to step 2. Then... Troubleshoot the XBL alarms. Go to step 3.
does not return to service... If XBL alarms... are present... are not present... 3
Review the Alarms window for XBL alarms.
A fault condition probably exists in the switching equipment between the BSC and the RXCDR. Troubleshoot the switching equipment fault and take the 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-Q 24 May 2004
2-5
2. ABSS: Circuit Configuration Problem
2. ABSS: Circuit Configuration Problem

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 still allowed to be set up by the BSC as the MSC requests. Since there is no proper switch connection for the CIC(s) at the RXCDR, there is no audio on the affected CIC(s).

The additional information field displays the number of affected CICs for a specific ABSS.
Possible cause(s)
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 1 2 3 Re-equip CICs with static Aters
Identify which CICs on the ABSS do not have static Aters. Unequip the CICs that do not have static Aters. 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-Q 24 May 2004
Chapter
AXCDR alarms
This chapter details OMC-R AXVDR Alarms and includes the following alarm procedures: "0. AXCDR: BSC Detecting CIC Validation Failure" on page 3-3 "1. AXCDR: AXCDR ID Mismatch with RXCDR Network Entity ID" on page 3-4
68P02901W26-Q 24 May 2004
3-1
Introduction to 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-Q 24 May 2004
0. AXCDR: BSC Detecting CIC Validation Failure
0. AXCDR: BSC Detecting CIC Validation Failure

Description
The RXCDR failed to respond to repeated attempts by the BSC to initiate the CIC validation procedure. The affect 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 cause(s)
The RXCDR has not been upgraded to a software release that supports CIC validation.
Procedure
Procedure 3-1 1 2 3 BSC Detecting CIC Validation Failure
Turn CIC validation off at the BSC for the affected RXCDR. Upgrade the affected RXCDR to a software release that supports CIC validation. Turn CIC validation on at the BSC for the affected RXCDR.
68P02901W26-Q 24 May 2004
3-3
1. AXCDR: AXCDR ID Mismatch with RXCDR Network Entity ID

Clearing Type: Severity Level: Category: FMIC Critical Equipment
Description
The BSC 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 cause(s)
The following are possible causes for this alarm: 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-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 3-2 1 AXCDR ID Mismatch with RXCDR Network Entity ID
Determine whether or not the AXCDR or RXCDR network identifiers are different. If network identifiers... Are the same... Are not the same... Then... Go to step 5. Go to step 2. Then... Go to step 3. Go to step 4.
Modify either the AXCDR or RXCDR network identifier. To modify the... AXCDR network identifier... RXCDR network identifier...
3 4
Modify the network identifier of the AXCDR or the RXCDR device to make the network identifiers the same. 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. Correct the linkage between the BSC and the RXCDR.
68P02901W26-Q 24 May 2004
3-5
3-6
68P02901W26-Q 24 May 2004
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-4 "8. BCUP: Output Failure" on page 4-5 "8. BCUP: Output Failure" on page 4-5 "9. BCUP: Input Failure" on page 4-6 "10. BCUP: Over Temperature Warning" on page 4-7
68P02901W26-Q 24 May 2004
4-1
Introduction to 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 may be equipped on power supply units specified for the hardware platform in use.
4-2
68P02901W26-Q 24 May 2004
0. BCUP: Unexpected Board Type
0. BCUP: Unexpected Board Type

Clearing Type: Severity Level: Category: OIC Investigate 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 cause(s)
The following are possible causes for this alarm: The power supply failed. There may be serial bus communications problems.
Procedure
Procedure 4-1 Unexpected Board Type
Send a field representative to replace the power supply module.
68P02901W26-Q 24 May 2004
4-3
1. BCUP: Serial Bus Connection Failure
1. BCUP: Serial Bus Connection Failure

Clearing Type: Severity Level: Category: FMIC Investigate Equipment
Description
The BCUP device has not responded to communication attempts by the Serial Bus (SBUS) processor.

Possible cause(s)
The following are possible causes for this alarm: The physical connection between the BCUP boards and the SBUS processor is broken. The SBUS signal line is faulty. The BCUP boards were improperly 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 the appropriate corrective action.
4-4
68P02901W26-Q 24 May 2004
8. BCUP: Output Failure
8. BCUP: Output Failure

Description
The BCUP output power failed.

Possible cause(s)
The following are possible causes for this alarm: The input power source is faulty. The output power source is faulty. The output power source is overloaded.
Procedure
Procedure 4-3 Output Failure
68P02901W26-Q 24 May 2004
4-5
9. BCUP: Input Failure
9. BCUP: Input Failure

Description
The BCUP input power has failed.

Possible cause(s)
The following are possible causes for this alarm: The input power source is faulty. The circuit breaker has tripped or failed.
Procedure
Procedure 4-4 Input Failure
4-6
68P02901W26-Q 24 May 2004
10. BCUP: Over Temperature Warning

Description
The temperature of the power supply module exceeded safe limits.

Possible cause(s)
The following are possible causes for this alarm: The airflow is restricted. The fan failed.
Procedure
Procedure 4-5 Over Temperature Warning
68P02901W26-Q 24 May 2004
4-7
4-8
68P02901W26-Q 24 May 2004
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 "21. BSP: EEPROM Flash Programming Failure" on page 5-9 "22. BSP: SWFM Indication" on page 5-10 "30. BSP: Clock A Signal Loss" on page 5-11 "31. BSP: Clock B Signal Loss" on page 5-13 "32. BSP: TDM Interface Failure - Assigned Timeslot Counter Underflow" on page 5-15 "33. BSP: TDM Interface Failure - Assigned Timeslot Counter Overflow" on page 5-17 "34. BSP: TDM Interface Failure - TDM Parity Error" on page 5-19 "35. BSP: LAN Connection Failure" on page 5-21 "39. BSP: Software Failure" on page 5-23 "40. BSP: Spurious Interrupt" on page 5-25 "47. BSP: Unexpected Board Type: GPROC2 or GPROC3 expected" on page 5-27 "48. BSP: Memory location is corrupt. Replace GPROC board." on page 5-29 "50. BSP: EEPROM SW Flash Programming Failure." on page 5-30 "51. BSP: EEPROM HW Flash Programming Failure." on page 5-31 "231. BSP: TDM Interface Configuration Failure" on page 5-32 "239. BSP: Process Safe Test Audit Failure" on page 5-34 "254. BSP: Device Failure" on page 5-36
68P02901W26-Q 24 May 2004
5-1
Introduction to BSP alarms
BSP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base Station Processor (BSP) device.
FRUs
A BSP device may be equipped on one of the FRUs shown in Table 5-1. Table 5-1 BSP FRUs FRU GPROC GPROC2 {4354} GPROC3 MCU MCUF MCUm ARENA (MCU) ARENA MAC (MCU) Description InCell GPROC board InCell GPROC2 board InCell GPROC3 board Micro Controller Unit board Micro Controller Unit Board with dual FMUX M-Cellmicro Micro Controller Unit board Horizonmicro (M-Cellarena) Micro Controller Unit board Horizoncompact (M-Cellarena Macro) Micro Controller Unit board Horizonmicro2 Micro Controller Unit board Horizoncompact2 Micro Controller Unit board
HORIZONMIC2 (MCU) HORIZONCOM2 (MCU)
Throughout this chapter, reference is made to InCell BTSs. Understand InCell BTS to mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
5-2
68P02901W26-Q 24 May 2004
At the BSC, the BSP can only be GPROC2 or GPROC3
68P02901W26-Q 24 May 2004
5-3
1. BSP: EEPROM Flash Failure - No Valid Bootstrap Code Detected

Clearing Type: Severity Level: Category: OIC Investigate Processing
Description
The Initialization Process (IP) 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 cause(s)
The following are possible causes for this alarm: The bootstrap code object (Object 15) at the site is corrupt. The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
5-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 5-1 1 EEPROM Flash Failure - No Valid Bootstrap Code Detected
Determine if this alarm is occurring at other BSSs or other sites within a single BSS. If this alarm is occurring at... other BSSs... other sites within a single BSS... Then... Go to step 2. Go to step 4. Then... No further action is required. Send a field representative to the site to replace the GPROC board.
Obtain a new OMC-R code bootstrap object. If the alarm... is cleared and does not recur... is not cleared or recurs...
Download the new object to the affected BSSs, and then attempt to clear the alarm. If the alarm... is cleared and does not recur... is not cleared or recurs... Then... No further action is required. Send a field representative to the site to replace the GPROC board.
Download the object to the BSC, and then attempt to clear the alarm.
A BSS-wide outage occurs when downloading to the BSC. If the alarm... is cleared and does not recur... is not cleared or recurs... Then... No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
5-5
8. BSP: EEPROM Flash Object Failure

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 cause(s)
The following are possible causes for this alarm: The bootstrap code object (Object 15) at the site is corrupt. The bootstrap code object (Object 15) was corrupted while downloading to the GPROC. The bootstrap code object (Object 15) was programmed incorrectly with regard to the GPROC EEPROM address space.
Procedure
Procedure 5-2 1 EEPROM Flash Object Failure
Determine if this alarm is occurring at other BSSs or other sites within a single BSS. If this alarm is occurring at... other BSSs... other sites within a single BSS... Then... Go to step 2. Go to step 4.
2 5-6
Obtain a new OMC-R code object. 68P02901W26-Q 24 May 2004
Procedure 5-2 3
EEPROM Flash Object Failure (Continued)
A BSS-wide outage occurs when downloading the object to the BSC. If the alarm... is cleared and does not recur... is not cleared or recurs... Then... No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
5-7
17. BSP: EEPROM Flash Programming Failure

Description
An attempt to erase bank 0 prior to 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 cause(s)
The flash EEPROM in bank 0 is faulty.
Procedure
Procedure 5-3 EEPROM Flash Programming Failure
Send a field representative to the site to replace the GPROC board.
5-8
68P02901W26-Q 24 May 2004

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 cause(s)
The flash EEPROM device is faulty.
Procedure
68P02901W26-Q 24 May 2004
5-9
22. BSP: SWFM Indication
22. BSP: SWFM Indication

Clearing Type: Severity Level: Category: Intermittent Warning Processing
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 cause(s)
A software processing error.
Procedure
Procedure 5-5 Clear the alarm. SWFM Indication
5-10
68P02901W26-Q 24 May 2004
30. BSP: Clock A Signal Loss

Clearing Type: Severity Level: Category: FMIC Major 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 may cause the site to go OOS.
The fault condition reported by this alarm may cause the site to go OOS.

Possible cause(s)
The following are possible causes for this alarm: The KSWX A clock extender card failed. The Clock A receive circuitry on the GPROC board is faulty. A fibre optic cable is faulty.
68P02901W26-Q 24 May 2004
5-11
Procedure
Procedure 5-6 1 Clock A Signal Loss
Determine the current administrative and operational state of the site. If Site is... busy-unlocked... not busy-unlocked... Then... Go to step 2. Send a field representative to the site to replace the Clock A GCLK.
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 Second Reference Loss Then... Go to step 4. Send a field representative to the site to replace the redundant GCLK. Go to step 5. Then... Force the BSP to swap to the redundant clock. no... The site resets when the clock is swapped. After the site reset is complete, go to step 5.
Verify that the redundant clock is in service and not reporting any alarms. If the redundant clock is... busy-unlocked with no alarms... not busy-unlocked or busy-unlocked with alarms... not equipped...
Are more than 50% of the devices in the same cage reporting clock alarms? If... yes...
Go to step 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... are present on more than 50% of other devices... are present only for the BSP... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the BSP. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
5-12
68P02901W26-Q 24 May 2004
31. BSP: Clock B Signal Loss

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 redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
The following are possible causes for this alarm: The KSWX B clock extender card failed. The Clock B receive circuitry on the GPROC board is faulty.
Procedure
Procedure 5-7 1 Clock B Signal Loss
Determine if the site is in service. If Site is... busy-unlocked... not busy-unlocked... Then... Go to step 2. Send a field representative to the site to replace the Clock B GCLK.
68P02901W26-Q 24 May 2004
5-13
Procedure 5-7 2
Clock B Signal Loss (Continued)
Determine if any of the following alarms were reported by other devices in the same cage as Clock B: Clock B Signal Loss 6.12 Second Reference Loss Then... Go to step 4. Send a field representative to the site to replace the redundant GCLK. Go to step 5. Then... Force the BSP to swap to the redundant clock. no... The site resets when the clock is swapped. After the site reset is complete, go to step 5.
Go to step 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... are present on more than 50% of other devices... are present only for the BSP... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the BSP. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
5-14
68P02901W26-Q 24 May 2004
32. BSP: TDM Interface Failure - Assigned Timeslot Counter Underflow

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 cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane are faulty. Assigned timeslot counter register failed.
Procedure
Procedure 5-8 1 TDM Interface Failure - Assigned Timeslot Counter Underflow
Determine the current state of the site. If site is... busy-unlocked... Then... The fault condition no longer exists. No further action is required.
68P02901W26-Q 24 May 2004
5-15
Procedure 5-8 2
TDM Interface Failure - Assigned Timeslot Counter Underflow (Continued) Go to step 2.
not busy-unlocked... Reset the BSP.
The site is reset. 3 Determine the state of the BSP after the reset is completed. If BSP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
5-16
68P02901W26-Q 24 May 2004
33. BSP: TDM Interface Failure - Assigned Timeslot Counter Overflow

Description
The BSP has determined that the TDM highway is overused. More switch-bound timeslots are driven onto the TDM bus than were allocated in the assigned timeslot counter register.

Possible cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane is faulty. Assigned timeslot counter register failed.
Procedure
Procedure 5-9 1 TDM Interface Failure - Assigned Timeslot Counter Overflow
68P02901W26-Q 24 May 2004
5-17
Procedure 5-9 2
TDM Interface Failure - Assigned Timeslot Counter Overflow (Continued) Go to step 2.
5-18
68P02901W26-Q 24 May 2004
34. BSP: TDM Interface Failure - TDM Parity Error

Clearing Type: Severity Level: Category: FMIC Major Communication
Description
An incorrect parity was detected on the inbound TDM highway.

Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 5-10 1 TDM Interface Failure - TDM Parity Error
Determine the current state of the site. If site is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
68P02901W26-Q 24 May 2004
5-19
Procedure 5-10 2
TDM Interface Failure - TDM Parity Error (Continued)
Reset the BSP.
5-20
68P02901W26-Q 24 May 2004
35. BSP: LAN Connection Failure

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 cause(s)
The following are possible causes for this alarm: The BSP was reset via software or the front panel on site. The GPROC is faulty. The LANX hardware is faulty.
Procedure
Procedure 5-11 1 LAN Connection Failure
68P02901W26-Q 24 May 2004
5-21
Procedure 5-11 2
LAN Connection Failure (Continued) Go to step 2.
5-22
68P02901W26-Q 24 May 2004
39. BSP: Software Failure

Clearing Type: Severity Level: Category: FMIC Critical Processing
Description
The BSP experienced an unrecoverable SWFM error.
SWFM is a debugging tool for Motorola engineering and is only reported if the SWFM indication is turned on at the BSS MMI.
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 only useful to programmers.
Possible cause(s)
The following are possible causes for this alarm: The BSP software is faulty. The GPROC is faulty.
68P02901W26-Q 24 May 2004
5-23
Procedure
Procedure 5-12 1 Software Failure
Determine the state of the site. If the site is... busy-unlocked... not busy-unlocked... Then... Go to step 3. Go to step 2.
2 3
Send a field representative to the site to replace the GPROC board. Determine the state of the BSP. If the BSP is... busy-unlocked... Then... The alarm was probably caused by a software error. Contact a Motorola representative to resolve the software error. Send a field representative to the site to replace the GPROC board.
not busy-unlocked...
5-24
68P02901W26-Q 24 May 2004
40. BSP: Spurious Interrupt

Clearing Type: Severity Level: Category: Intermittent Investigate Processing
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 cause(s)
The following are possible causes for this alarm: 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 other cause. The backplane connections to any of the MCAP boards are faulty.
Procedure
Procedure 5-13 1 Spurious Interrupt
Determine if the site was reset. If the site was... reset... Then... Go to step 2.
68P02901W26-Q 24 May 2004
5-25
Procedure 5-13 2
Spurious Interrupt (Continued) Go to step 3. Then... Go to step 3. Go to step 4. Then... The fault condition no longer exists. No further action is required. Go to step 4.
not reset... Determine the current state of the site. If the site is... busy-unlocked... not busy-unlocked... 3 If the BSP is... busy-unlocked... not busy-unlocked... 4
Determine the current state of the BSP.
5-26
68P02901W26-Q 24 May 2004
47. BSP: Unexpected Board Type: GPROC2 or GPROC3 expected

{4354} Clearing Type: Severity Level: Category: FMIC Critical Equipment
Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or GPROC3 board. BSPs at the RXCDR and BSC must be a GPROC2, GPROCs are not supported.

Possible cause(s)
If this occurs in an InCell site, the GPROC board does not come into service. The following are possible causes for this alarm: A GPROC board is installed instead of a required GPROC2 or GPROC3 board. A GPROC board is installed and the gproc_slots database parameter is set to 32.
Procedure
Procedure 5-14 1 Unexpected Board Type: GPROC2 or GPROC3 expected
Verify the value assigned to the gproc_slots database parameter. If the value is... Then...
68P02901W26-Q 24 May 2004
5-27
Procedure 5-14
Unexpected Board Type: GPROC2 or GPROC3 expected (Continued) Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board. Change the value of the gproc_slots database parameter to the correct value and then go to Step 2.
correct...
not correct...
Reset the BSP.
The site is reset. 3 Determine the state of the BSP after the reset is completed. If the BSP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board.
5-28
68P02901W26-Q 24 May 2004
48. BSP: Memory location is corrupt. Replace GPROC board.
48. BSP: Memory location is corrupt. Replace GPROC board.

{4354} Clearing Type: Severity Level: Category: FMIC Warning 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 cause(s)
The following are possible causes for this alarm: A single bit of the memory location is seized. Two address lines are cut short. Failure within SDRAM.
Procedure
Procedure 5-15 Memory location is corrupt. Replace GPROC board.
Immediate action is not necessary. Contact the Motorola Local Office and arrange to replace the GPROC board at an appropriate time.
68P02901W26-Q 24 May 2004
5-29
50. BSP: EEPROM SW Flash Programming Failure.
50. BSP: EEPROM SW Flash Programming Failure.

{4354} Clearing Type: Severity Level: Category: FMIC Investigate Equipment
Description
This is a generic flash programming error. A problem has occurred with the operating software.

Possible cause(s)
The following are possible causes for this alarm: The memory may be corrupt. An incorrect request made by an internal process. A static variable could be corrupt.
Procedure
Procedure 5-16 EEPROM SW Flash Programming Failure.
If the board does not reset automatically, a manual reset can be performed to reload the bootrom object.
5-30
68P02901W26-Q 24 May 2004
51. BSP: EEPROM HW Flash Programming Failure.
51. BSP: EEPROM HW Flash Programming Failure.

Description
This is a generic flash programming error.

Possible cause(s)
The following are possible causes for this alarm: The flash EEPROM device may be defective.
Procedure
Procedure 5-17 EEPROM HW Flash Programming Failure.
This alarm does not take the board out of service. To resolve the alarm, reset the BSP and continue use until it is possible to replace the GPROC3 board.
68P02901W26-Q 24 May 2004
5-31
231. BSP: TDM Interface Configuration Failure

Clearing Type: Severity Level: Category: FMIC Major Processing
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 cause(s)
The following are possible causes for this alarm: The GPROC board failed. A software error occurred. The GPROC device could not be programmed to the designated timeslot when swapping the TDM highways.
5-32
68P02901W26-Q 24 May 2004
Procedure
Procedure 5-18 1 TDM Interface Configuration Failure
Determine the state of the BSP. If BSP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
5-33
239. BSP: Process Safe Test Audit Failure

Clearing Type: Severity Level: Category: FMIC Investigate Communication
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 nine bytes containing process information, as shown in Table 5-2. Bytes one to eight are useful only to programmers. Byte nine is the error code for the alarm. Table 5-2 Error codes Byte nine Value (Hex) 00 01 02 Definition The process that failed the audit is in an infinite loop. The cause for the failure was not determined. Higher priority processes prevented the process that failed to run. The cause for the failure was not determined.
03
Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The GPROC board is faulty. A process running on the BSP failed a safe test audit.
5-34
68P02901W26-Q 24 May 2004
Procedure
Procedure 5-19 1 Process Safe Test Audit Failure
Determine the error code displayed in the additional information field. If the error code is... 2... 0, 1, or 3... Then... Go to step 2. Go to step 3. Then... Go to step 4. Contact a Motorola representative to resolve the software error.
Perform the safe test audit on the BSP If the BSP... passes the audit... fails the audit...
Reset the BSP.
The site is reset. 4 Determine the state of the BSP after the reset is completed. If the BSP... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
5-35
254. BSP: Device Failure

Description
The BSP is taken OOS by the GPROC Fault Management System.
System action
The site resets.

A single byte is displayed in the additional information field identifying the type of site reset, as shown in Table 5-3. Table 5-3 Site reset type Value (Hex) 01 02 Hard reset. Soft reset. Definition
Possible cause(s)
A fault translation by the GPROC Fault Management System.
5-36
68P02901W26-Q 24 May 2004
Procedure
Wait approximately 10 minutes after this alarm is received to allow the site to reset before using this procedure. Procedure 5-20 1 Device Failure
Determine the current state of the BSP. If the BSP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
Reset the BSP.
The site is reset. 3 Determine the state of the BSP after the reset is completed. If the BSP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
5-37
5-38
68P02901W26-Q 24 May 2004
Chapter
BSS alarms
This chapter details BSS Alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "0. BSS: Last MTL Link Failure - Signalling 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-11 "3. BSS: Call Processing Failure - BSS Detected BSSAP Down" on page 6-12 "5. BSS: No MSC Acknowledgement for Circuit Block" on page 6-14 "5. BSS: No MSC Acknowledgement for Circuit Block" on page 6-14 "6. BSS: No MSC Acknowledgement for Circuit Unblock" on page 6-16 "7. BSS: No MSC Acknowledgement for Reset Circuit" on page 6-18 "7. BSS: Mobile Assignment Request From MSC Protocol Error - PM" on page 6-20 "8. BSS: Unequipped Circuit at the MSC" on page 6-22 "9. BSS: No MSC Acknowledgement for Global Reset" on page 6-24 "10. BSS: Erroneous Layer 3 Message Received by the BSS" on page 6-25 "11. BSS: Confusion Message Received from the MSC" on page 6-26 "12. BSS: Unequipped Circuit at the BSS" on page 6-27 "17. BSS: HO Request From the MSC Protocol Error - PM" on page 6-29 "18. BSS: Routing Failure - Syntax Error Detected (SMLC) - PM" on page 6-30 "20. BSS: Paging Request from SMLC Protocol Error - PM" on page 6-31 "21. BSS: Trunk Major Threshold Exceeded" on page 6-32 "22. BSS: Trunk Critical Threshold Exceeded" on page 6-34 "26. BSS: Received Page for Invalid Cell from MSC" on page 6-36 6-1
"39.BSS: Circuit Fault Detected on Radio Channel" on page 6-37 "40. BSS: Circuit Fault Cleared on Radio Channel" on page 6-39 "42. BSS: Circuit Fault Cleared On Ater Channel " on page 6-43 "43. BSS: Circuit Fault Detected on PCM Circuit " on page 6-45 "44. BSS: Circuit Fault Cleared on PCM Circuit " on page 6-47 "45. BSS: Circuit Fault Detected on GPRS Circuit " on page 6-48 "46. BSS: Circuit Fault Cleared on GPRS Circuit " on page 6-50 "47. BSS: Circuit Fault Detected On PATH Channel " on page 6-51 "48. BSS: Circuit Fault Cleared on PATH Channel " on page 6-53 "49. BSS: Last LMTL Link Failure - Signalling Point Inaccessible" on page 6-55 "50. BSS: Call Processing Failure - SMLC Detected SCCP Down" on page 6-58 "51. BSS: Call Processing Failure - SMLC Detected BSSAP Down" on page 6-60 "52. BSS: No SMLC Acknowledgement for Global Reset" on page 6-62 "53. BSS: Erroneous Layer 3 Message Received from SMLC" on page 6-63 "54. BSS: Confusion Message Received from the SMLC" on page 6-64 "55. BSS: Received Page for Invalid Cell from SMLC" on page 6-65 "59. BSS: Last PCU Failed" on page 6-66
6-2
68P02901W26-Q 24 May 2004
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-Q 24 May 2004
6-3
0. BSS: Last MTL Link Failure - Signalling Point Inaccessible

Description
The signalling point code is inaccessible due to the failure of the last available MTL link. When this occurs, the BSS cannot support calls or send messages to the MSC.
This is a service-affecting fault condition.
MTL link configuration

A single MTL link provides a 64 kbit/s 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.

Possible cause(s)
The following are possible causes for this alarm: No signalling route is available to the MSC. The circuits are faulty. The circuit coaxial cable is faulty.
6-4
68P02901W26-Q 24 May 2004
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 acknowledgement 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 1 Last MTL Link Failure - Signalling Point Inaccessible
Determine if all MTL devices are OOS. If all MTL devices... are OOS... are not OOS... Then... Go to step 2. Go to step 3. Then... Wait until the MSC reboot is finished, and then go to step 3. Wait until the RXCDR reboot is finished, and then go to step 4. Go to step 4.
Determine if the MSC or RXCDR are rebooting. If... the MSC is rebooting... the RXCDR is rebooting... neither the MSC or RXCDR are rebooting...
Determine if the alarm is cleared. If the alarm is... cleared... Then... Determine the status of the MTLs and take the appropriate action to return all MTLs to service. The fault is probably at the MSC. Troubleshoot the MSC fault. Then... Determine the status of the MTLs and take the appropriate action to return all MTLs to service. Go to step 5.
not cleared... 4 Determine if the alarm is cleared. If the alarm is... cleared...
not cleared...
68P02901W26-Q 24 May 2004
6-5
Procedure 6-1 5
Last MTL Link Failure - Signalling Point Inaccessible (Continued) Then... Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... Determine the status of the MTLs and take the appropriate action to return all MTLs to service. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
Attempt to return one of the MTLs to service. If one of the MTLs... returns to service... does not return to service...
Determine if the alarm is cleared. If the alarm is... cleared...
not cleared...
6-6
68P02901W26-Q 24 May 2004
0. BSS: Paging Request From MSC Protocol Error - PM
0. BSS: Paging Request From MSC Protocol Error PM

Clearing Type: Severity Level: Category: Intermittent Warning Quality of Service
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 may occur due to protocol errors which may occur if the message is incorrectly formatted. A protocol error does not indicate paging success or failure. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The MSC experienced a protocol error.
Procedure
Procedure 6-2 Paging Request From MSC Protocol Error - PM
Initiate fault isolation and resolution procedures at the MSC. After the fault at the MSC is resolved, clear the alarm.
68P02901W26-Q 24 May 2004
6-7
1. BSS: Call Processing Failure - MSC Detected SCCP Down
1. BSS: Call Processing Failure - MSC Detected SCCP Down

Description
The BSS received a User Part Unavailable (UPU) message from the MSC indicating that the Signalling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the BSS cannot support calls.
This is a service-affecting fault condition. When the SCCP is down, the MSC may not accept SCCP messages from the BSS. This SSCP failure occurs at the MSC.

Possible cause(s)
The BSS received a UPU message from the MSC indicating the SCCP is unavailable.
Procedure
Procedure 6-3 Call Processing Failure - MSC Detected SCCP Down
Initiate fault isolation and resolution procedures at the MSC.
6-8
68P02901W26-Q 24 May 2004
1. BSS: Routing Failure - Syntax Error Detected - PM
1. BSS: Routing Failure - Syntax Error Detected - PM

Clearing Type: Severity Level: Category: Intermittent Warning Communication
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 signalling messages between the BSC and MSC. Excessive syntax errors can result in degraded SCCP performance. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The SCCP message had a syntax error.
Procedure
Procedure 6-4 Routing Failure - Syntax Error Detected - PM
68P02901W26-Q 24 May 2004
6-9
2. BSS: Call Processing Failure - MSC Detected BSSAP Down
2. BSS: Call Processing Failure - MSC Detected BSSAP Down

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.
This is a service-affecting fault condition. When the BSSAP is down, the MSC may not accept BSSAP messages from the BSS. This BSSAP failure occurs at the MSC.

Possible cause(s)
The BSS received a SSP message from the MSC indicating the BSSAP is unavailable.
Procedure
Procedure 6-5 Call Processing Failure - MSC Detected BSSAP Down
6-10
68P02901W26-Q 24 May 2004
2. BSS: Routing Failure - Reason Unknown - PM
2. BSS: Routing Failure - Reason Unknown - PM

Description
The ROUTING_UNKNOWN statistic threshold has been reached. This statistic tracks the number of invalid Signalling 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 correctly route the message. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The system is not capable of translating an SPC address. This specific SPC address are unrecognizable by the translation process.
Procedure
Procedure 6-6 Routing Failure - Reason Unknown - PM
68P02901W26-Q 24 May 2004
6-11
3. BSS: Call Processing Failure - BSS Detected BSSAP Down

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.
This is a service-affecting fault condition. When the BSSAP is down, the BSS does not accept BSSAP messages from the MSC. This BSSAP failure is at the BSS.

Possible cause(s)
All cells in the BSS are OOS.
6-12
68P02901W26-Q 24 May 2004
Procedure
Procedure 6-7 1 Call Processing Failure - BSS Detected BSSAP Down
Determine the state of the cells at the site. If... any of the cells are busy-unlocked... Then... The fault condition that caused this alarm no longer exists. Initiate fault isolation and resolution procedures for any cells and DRIs that are OOS. Go to step 2.
all of the cells are not busy-unlocked... 2 If... any of the DRIs are busy-unlocked...
Determine the state of the DRIs at the site. Then... The fault condition that caused this alarm no longer exists. Initiate fault isolation and resolution procedures for any cells and DRIs that are OOS. Initiate fault isolation and 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.
all of the DRIs are not busy-unlocked...
68P02901W26-Q 24 May 2004
6-13
5. BSS: No MSC Acknowledgement for Circuit Block

Description
The BSS has repeated the circuit block message the maximum number of times without receiving any acknowledgement from the MSC. When the BSS sends a circuit block message to the MSC, the BSS expects to receive an acknowledgement message from the MSC. If an acknowledgement message is not received, the BSS retransmits the circuit block message. This is repeated until the BSS receives an acknowledgement 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 first Value 01 Definition The element identifier of the first (or only) blocked terrestrial circuit. The CIC of the first (or only) blocked terrestrial circuit where the CIC is represented by two bytes. (For example, 00 A2.)
second and third
00 to FF and 00 to FF
The content of the additional information field is dependent upon the value assigned to the group_block_unblock_allowed parameter. Table 6-2 specifies the content for the non-zero value.
6-14
68P02901W26-Q 24 May 2004
Table 6-2
If group_block_unblock_allowed = 1 Byte first Value 01 Definition The element identifier of the first (or only) blocked terrestrial circuit. The CIC of the first (or only) blocked terrestrial circuit where the CIC is represented by two bytes. (For example, 00 A2.) If there is more than one blocked terrestrial circuit, this byte is set to 1E. The total number of bytes included in the additional information field. The range of CICs in the list. The range is the difference between the lowest CIC number and the highest CIC number. The CICs of the blocked terrestrial circuits, where each is represented by two bytes. (For example, 00 A3, 00 A4.)
second and third
00 to FF and 00 to FF 1E
fourth
fifth sixth
00 to FF 00 to FF
seventh and eighth to a maximum of 256 CICs
Possible cause(s)
The MSC does not recognize the circuit.
Procedure
Procedure 6-8 Clear the alarm. No MSC Acknowledgement for Circuit Block
68P02901W26-Q 24 May 2004
6-15
6. BSS: No MSC Acknowledgement for Circuit Unblock

Description
The BSS has repeated the circuit unblock message the maximum number of times without receiving any acknowledgement from the MSC. When the BSS sends a circuit unblock message to the MSC, the BSS expects to receive an acknowledgement message from the MSC. If an acknowledgement message is not received, the BSS retransmits the circuit unblock message. This is repeated until the BSS receives an acknowledgement 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-3 specifies the content for the zero value. Table 6-3 If group_block_unblock_allowed = 0 Byte first Value 01 Definition The element identifier of the first (or only) unblocked terrestrial circuit. The CIC of the first (or only) unblocked terrestrial circuit where the CIC is represented by two bytes. (For example, 00 A2.)
second and third
The content of the additional information field is dependent upon the value assigned to the group_block_unblock_allowed parameter. Table 6-4 specifies the content for the non-zero value.
6-16
68P02901W26-Q 24 May 2004
Table 6-4
If group_block_unblock_allowed = 1 Byte first Value 01 Definition The element identifier of the first (or only) unblocked terrestrial circuit. The CIC of the first (or only) unblocked terrestrial circuit where the CIC is represented by two bytes. (For example, 00 A2.) If there is more than one unblocked terrestrial circuit, this byte is set to 1E. The total number of bytes included in the additional information field. The range of CICs in the list. The range is the difference between the lowest CIC number and the highest CIC number. The CICs of the unblocked terrestrial circuits, where each is represented by two bytes. (For example, 00 A3, 00 A4.)
second and third
00 to FF and 00 to FF 1E
fourth
fifth sixth
00 to FF 00 to FF
seventh and eighth to a maximum of 256 CICs
Possible cause(s)
The MSC may not have recognized the circuit.
Procedure
Procedure 6-9 Clear the alarm. No MSC Acknowledgement for Circuit Unblock
68P02901W26-Q 24 May 2004
6-17
7. BSS: No MSC Acknowledgement for Reset Circuit

Clearing Type: Severity Level: Category: Intermittent Critical Communication
Description
The BSS has repeated the circuit unblock message the maximum number of times without receiving any acknowledgement from the MSC. The maximum number of times the message is repeated is defined by the max_rst_ckt_timer_exp parameter.
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 field contents Byte first second and third Value 00 to FF 00 to FF and 00 to FF Definition The element identifier of the terrestrial circuit that was reset. The Circuit Identity Code (CIC) of the first (or only) terrestrial circuit is represented by two 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 terrestrial circuit.
6-18
68P02901W26-Q 24 May 2004
Possible cause(s)
The MSC does not recognize the circuit.
Procedure
Procedure 6-10 Clear the alarm. No MSC Acknowledgement for Reset Circuit
68P02901W26-Q 24 May 2004
6-19
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. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: Incompatible database elements exists in the BSS and MSC. Assignment Request messages received from the MSC are incorrectly formatted.
Procedure
Procedure 6-11 1 Mobile Assignment Request From MSC Protocol Error - PM
Determine if there are incompatible database elements in the BSS and MSC. If there are... no incompatible database elements... Then... Go to step 2.
6-20
68P02901W26-Q 24 May 2004
Procedure 6-11
Mobile Assignment Request From MSC Protocol Error - PM (Continued) Make the appropriate database corrections. After the corrections are made, clear the alarm.
incompatible database elements...
Initiate procedures at the MSC to correct the Assignment Request message format. After format corrections are complete, clear the alarm.
68P02901W26-Q 24 May 2004
6-21
8. BSS: Unequipped Circuit at the MSC

Clearing Type: Severity Level: Category: Intermittent Investigate Communication
Description
The BSS 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.

The contents of the additional information field are shown in Table 6-6. Table 6-6 Additional information field contents Byte first Value 00 to FF Definition The element identifier of the terrestrial circuit that was identified as unequipped. The Circuit Identity Code (CIC) of the terrestrial circuit is represented by two 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 terrestrial circuit.
second and third
6-22
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The terrestrial circuit is not equipped at the MSC. The MSC and BSS databases show a different device state for the same terrestrial circuit.
Procedure
Procedure 6-12 1 2 Unequipped Circuit at the MSC
Determine if the terrestrial circuit is equipped in the BSS, and then go to step 2. Determine if the terrestrial circuit should be equipped. If the circuit should... be equipped... Then... Equip the circuit at the MSC. After equipping the circuit at the MSC, clear the alarm. Unequip the circuit from the BSS. After unequipping the circuit at the BSS, clear the alarm.
not be equipped...
68P02901W26-Q 24 May 2004
6-23
9. BSS: No MSC Acknowledgement for Global Reset
9. BSS: No MSC Acknowledgement for Global Reset

Description
The BSS repeated the global reset message the maximum number of times without receiving an acknowledgement from the MSC.

Possible cause(s)
The MSC did not acknowledge the global reset message.
Procedure
Procedure 6-13 Clear the alarm. No MSC Acknowledgement for Global Reset
6-24
68P02901W26-Q 24 May 2004
10. BSS: Erroneous Layer 3 Message Received by the BSS
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 the Confusion message.

The additional information field displays the erroneous Layer 3 message that was received by the BSS (from the MSC).
Possible cause(s)
The MSC sent an erroneous layer 3 message.
Procedure
Procedure 6-14 Clear the alarm. Erroneous Layer 3 Message Received by the BSS
68P02901W26-Q 24 May 2004
6-25
11. BSS: Confusion Message Received from the MSC
11. BSS: Confusion Message Received from the MSC

Description
The BSS received a Confusion message from the MSC.

The additional information field displays the confusion message that was received by the BSS from the MSC.
Possible cause(s)
The MSC did not understand a layer 3 message from the BSS.
Procedure
Procedure 6-15 Clear the alarm. Confusion Message Received from the MSC
6-26
68P02901W26-Q 24 May 2004
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 may have been generated because device states may not have been reconciled properly by the database. Each database (MSC and BSS) may show 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. Note that this information is displayed for the unequipped terrestrial circuit. Any additional bytes displayed should be ignored.
68P02901W26-Q 24 May 2004
6-27
Table 6-7
Additional information field contents Byte first Value 00 to FF Definition The element identifier of the terrestrial circuit that was identified as unequipped. The Circuit Identity Code (CIC) of the terrestrial circuit is represented by two 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 terrestrial circuit.
second and third
Possible cause(s)
The following are possible causes for this alarm: The terrestrial circuit is not equipped at the MSC. The MSC and BSS databases may show a different device state for the same terrestrial circuit.
Procedure
Procedure 6-16 1 2 Unequipped Circuit at the BSS
Determine if the terrestrial circuit is equipped in the BSS, then go to step 2. Determine if the terrestrial circuit should be equipped. If the circuit should... be equipped... Then... Equip the circuit at the BSS. After equipping the circuit at the BSS, clear the alarm. Unequip the circuit from the MSC. After unequipping the circuit at the MSC, clear the alarm.
not be equipped...
6-28
68P02901W26-Q 24 May 2004
17. BSS: HO Request From the MSC Protocol Error - PM
17. BSS: HO 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 may occur due to protocol errors that may occur if the message is badly formatted or incompatible database elements exist in the BSS and MSC. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The MSC experienced a protocol error. Incompatible database elements exist in the BSS and MSC.
Procedure
Procedure 6-17 HO Request From the MSC Protocol Error - PM
68P02901W26-Q 24 May 2004
6-29
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 signalling messages between the BSC and SMLC. Excessive syntax errors can result in degraded Lb-interface SCCP performance. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The Lb-interface SCCP message had a syntax error.
Procedure
Procedure 6-18 Routing Failure - Syntax Error Detected (SMLC) - PM
Initiate fault isolation and resolution procedures at the BSS-based SMLC. After the fault at the BSS-based SMLC is resolved, clear the alarm.
6-30
68P02901W26-Q 24 May 2004
20. BSS: Paging Request from SMLC Protocol Error - PM
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 may occur due to protocol errors which may occur if the message is incorrectly formatted. A protocol error does not indicate paging success or failure. For further information, consult the BSS statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The SMLC experienced a protocol error.
Procedure
Procedure 6-19 Paging Request from SMLC Protocol Error - PM
Initiate fault isolation and resolution procedures at the BSS-based SMLC. After the fault at the BSS-based SMLC is resolved, clear the alarm.
68P02901W26-Q 24 May 2004
6-31
21. BSS: Trunk Major Threshold Exceeded

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, consult the BSS statistics chapter in the manual, Technical Description: BSS Command Reference (68P02901W23).

Possible cause(s)
The following are possible causes for this alarm: 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 may be set too low.
6-32
68P02901W26-Q 24 May 2004
Procedure
Procedure 6-20 1 2 Trunk Major Threshold Exceeded
Review the Alarms window to identify the current CIC and RCI alarms. Initiate fault isolation and fault resolution procedures to restore the failed circuits.
68P02901W26-Q 24 May 2004
6-33
22. BSS: Trunk Critical Threshold Exceeded

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, consult the BSS statistics chapter in the manual, Technical Description: BSS Command Reference (68P02901W23).

Possible cause(s)
The following are possible causes for this alarm: 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 may be set too low.
6-34
68P02901W26-Q 24 May 2004
Procedure
Procedure 6-21 1 2 Trunk Critical Threshold Exceeded
Review the Alarms window to identify the current CIC and RCI alarms. Initiate fault isolation and fault resolution procedures to restore the failed circuits.
68P02901W26-Q 24 May 2004
6-35
26. BSS: Received Page for Invalid Cell from MSC
26. BSS: Received Page for Invalid Cell from MSC

Description
The MSC 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 field values Byte first second third fourth fifth sixth seventh eighth Value 00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF Definition The 8-byte ID of the invalid cell.
Any additional bytes displayed should be ignored. The cell id can be derived from the displayed fields by using the mmi_cell_id_format command (refer to manual 68P02901W23 Technical Description: BSS Command Reference).
Possible cause(s)
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-36
68P02901W26-Q 24 May 2004
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 that a device in the RCI path may 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 that is alarming. 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 additional alarm data section below. 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 which RCIs have active alarms on them. Whenever the OMC-R performs an alarm re-synchronization, 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 which the OMC-R does not show as active, require no immediate action since the BSS reissues these alarms at a later time. When the RCI Fault intermittent alarm is being used for resync, the Report Type of the alarm will be 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 BTS DRI DRI Fault for RCI 1 2 3 4 Site 2 ID 0 3 0 Timeslot 4
68P02901W26-Q 24 May 2004
6-37
Possible Cause(s)
A device in the RCI path may be faulty and in need of replacement.
Procedure
Procedure 6-23 Circuit Fault Detected on Radio Channel
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 may be in need of replacement. Send a field representative to the site to replace the faulty device.
6-38
68P02901W26-Q 24 May 2004
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 indicates that: the failure condition causing TRAU frames to be lost has cleared for the Radio Channel Interface in the alarm clear message. or, the Radio Channel Interface alarms should be cleared due to the Call Processing global reset or relevant RCI alarms should 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 Any additional bytes displayed should be ignored.
Possible Cause(s)
The associated failure condition has cleared.
Procedure
Procedure 6-24 Circuit Fault Cleared on Radio Channel
68P02901W26-Q 24 May 2004
6-39
Procedure 6-24
Circuit Fault Cleared on Radio Channel (Continued)
Because this intermittent alarm message indicates that a prior fault has cleared, no action is normally required. If there is a trend where a RCI toggles between 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 may be in need of replacement
6-40
68P02901W26-Q 24 May 2004
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 may be faulty and in need of replacement. None of the devices in the ACI path for the faulty ACI are taken Out Of Service (OOS) due to this alarm, which simply reports the devices contained in the ACI path that is alarming. Alarm throttling is not allowed for this alarm. The OMC-R is notified when a 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 additional alarm data section below. The OMC-R uses each ACI Fault intermittent alarm to keep track of which ACIs have alarms on them. The BSS alarm subsystem does not keep track of which ACIs have active alarms on them. Whenever the OMC-R performs an alarm re-synchronization, 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 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 which the OMC-R does not show as active, no immediate action is required, since the BSS reissues the alarms at a later time. When the ACI Fault intermittent alarm is being used for resync, the Report Type of the alarm will be resync alarm.
Additional information
The message Faulty ACI Alarm Set includes the following ACI path information: ACI. BSC-MMS device and 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-Q 24 May 2004
6-41
Possible Causes(s)
One or more devices in the ACI path may be faulty and in need of replacement.
Procedure
Procedure 6-25 Circuit Fault Detected On Ater Channel
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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-42
68P02901W26-Q 24 May 2004
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 that a device in the ACI path is no longer faulty. The OMC-R is notified anytime that a 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 a 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 each and every ACI. When the OMC-R receives a ACI Fault Clear intermittent alarm which has an ADI indicating Global Reset, the OMC-R will clear all of the ACI CERM alarms.
The message Faulty ACI Alarm Clear includes the ACI.
Possible Cause(s)
The failure causing TRAU Frame errors has cleared.
Procedure
Procedure 6-26 Circuit Fault Cleared On Ater Channel
68P02901W26-Q 24 May 2004
6-43
Procedure 6-26
Circuit Fault Cleared On Ater Channel (Continued)
Because this intermittent alarm message indicates that a prior fault has cleared, no action is normally required. If there is a trend where a ACI toggles between 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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-44
68P02901W26-Q 24 May 2004
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 may be 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 simply reports the devices contained in the CIC path that is alarming. 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 additional alarm data section below. 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 re-synchronization, the OMC-R receives a list of all the CICs for which the BSS has sent intermittent alarms (the BSS keeps track of which CICs have had alarms sent). 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 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 show as active alarms that are not in the resync list will be changed to the cleared state. If there are any new alarms in the list which the OMC-R does not show as active, no immediate action is required, since the BSS reissues the alarms at a later time. When the CIC Fault intermittent alarm is used for resync, the Report Type of the alarm will be resync alarm.
The message Faulty CIC Alarm Set includes the CIC when remote transcoding is used. The message Faulty CIC Alarm Set includes the following CIC related information when local transcoding is used: CIC, XCDR board id, and XCDR DSP. The CIC information is printed out in a format which is described the relevant area of the BSS Field Troubleshooting Manual 68P02901W51for this alarm. An example of a format for the CIC when remote transcoding is as follows:
CIC Fault for CIC 1 0
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
68P02901W26-Q 24 May 2004
6-45
Possible Cause(s)
One of the devices in the CIC path may be faulty and in need of replacement.
Procedure
Procedure 6-27 Circuit Fault Detected on PCM Circuit
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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-46
68P02901W26-Q 24 May 2004
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. Any additional bytes displayed should be ignored.
Possible Cause(s)
The failure causing TRAU Frame errors has cleared. Or, the CIC alarms should be cleared due to Call Processing global reset
Procedure
Procedure 6-28 Circuit Fault Cleared on PCM Circuit
Because this intermittent alarm message indicates that a prior fault has cleared, no action is normally required. If there is a trend where a CIC toggles between 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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
68P02901W26-Q 24 May 2004
6-47
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 may be 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 additional alarm data section below. The OMC-R uses each GCI Fault intermittent alarm to keep track of which GCIs 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 re-synchronization, the OMC will receive a list of all the GCIs for which the BSS has sent intermittent alarms (the BSS keeps track of which GCIs have had alarms sent). The OMC-R receives the GCI list in the additional alarm data field of one or more GCI Fault intermittent alarms. The OMC-R will know 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 which the OMC-R does not show as active, no immediate action is required since the BSS will reissue the alarms at a later time. When the GCI Fault at Remote BTS intermittent alarm is being used for resync, the Report Type of the alarm will be 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
6-48
68P02901W26-Q 24 May 2004
Possible Cause(s)
One of the devices in the GCI path to the PCU may be faulty and in need of replacement.
Procedure
Procedure 6-29 Circuit Fault Detected on GPRS Circuit
If there are multiple GCIs using the same devices that have Faulty GCI Alarms active, one of the devices is probably faulty and in need of replacement. Use the information contained in the Alarm report produced at the OMC-R to determine which device may be in need of replacement. Send a field representative to the site to replace the relevant device.
68P02901W26-Q 24 May 2004
6-49
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 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 displayed state of the alarm for the GCI in the intermittent alarm to cleared. This scheme produces a 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 each and every GCI.
The message Faulty GCI Alarm Clear includes the GCI.
Possible Cause(s)
The failure causing TRAU Frame errors has cleared for the GCI in the alarm clear message.
Procedure
Procedure 6-30 Circuit Fault Cleared on GPRS Circuit
Because this intermittent alarm message indicates that a prior fault has cleared, no action is normally required. If there is a trend where a GCI toggles between 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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-50
68P02901W26-Q 24 May 2004
47. BSS: Circuit Fault Detected On PATH Channel

Description
A particular PIC TRAU Frame sync loss error count has reached or exceeded the PIC error generation threshold indicating that a device in the PIC path may be faulty and need replacing. 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 is alarming. Alarm throttling is not allowed for the Faulty PIC Alarm Set alarm. The OMC-R is notified anytime 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 below. The OMC-R uses each PIC Fault intermittent alarm to keep track of which PICs have alarms on them. The BSS alarm subsystem does not keep track of which PICs have active alarms on them. Whenever the OMC-R performs an alarm re-synchronization, the OMC-R receives one or more lists of the PICs for which the BSS has sent intermittent alarms for (the BSS keeps track of which PICs have had alarms sent). 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 will be changed to the clear state. If there are any new alarms in the lists which the OMC-R does not show as active, no immediate action is required since the BSS will reissue the alarms at a later time. When the PIC Fault intermittent alarm is being used for resync, the Report Type of the alarm will be resync alarm.
Possible Cause(s)
One of the devices in the PIC path may be faulty and in need of replacement. The PIC information is printed out in an understandable customer format. 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
68P02901W26-Q 24 May 2004
6-51
Procedure
Procedure 6-31 Circuit Fault Detected On PATH Channel
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 which device may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-52
68P02901W26-Q 24 May 2004
48. BSS: Circuit Fault Cleared on PATH Channel

Description
A particular PIC TRAU Frame sync loss error count has reached or gone below the PIC error clear threshold indicating that a device in the PIC path is no longer faulty. This alarm is an intermittent alarm sent to the OMC-R and Man Machine Interface (MMI). The OMC-R is notified anytime 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 which 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 a 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 a PIC Fault Clear intermittent alarm which has an Additional Data Information (ADI) indicating Global Reset, the OMC-R clears all PIC CERM alarms.
The message Faulty PIC Alarm Clear is included in the PIC.
Possible Cause(s)
The failure causing TRAU Frame errors has cleared up for the PIC in the alarm clear message.
Procedure
Procedure 6-32 Circuit Fault Cleared on PATH Channel
68P02901W26-Q 24 May 2004
6-53
Procedure 6-32
Circuit Fault Cleared on PATH Channel (Continued)
Because this intermittent alarm message indicates that a prior fault has cleared, no action is normally required. If there is a trend where a PIC toggles between 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 may be in need of replacement. Send a field representative to the site to replace the relevant device.
6-54
68P02901W26-Q 24 May 2004
49. BSS: Last LMTL Link Failure - Signalling Point Inaccessible

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 0 alarm. See 0. BSS: Last MTL Link Failure - Signalling Point Inaccessible. The BSS reports a BSS: Last LMTL Link Failure - Signalling Point Inaccessible alarm when at least one LMTL has been equipped and yet no in-service LMTLs exist. The signalling 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 configuration

A single LMTL link provides a 64 kbit/s connection between the two pieces of equipment. One or more LMTL links can be configured between the following sites: BSC-to-Serving Mobile Location Centre (SMLC).

68P02901W26-Q 24 May 2004
6-55
Possible cause(s)
The following are possible causes for this alarm: No signalling 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, SIE) frames causing the link failure. The remote congestion timer expired causing the link failure. The MSU acknowledgement 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 1 Last LMTL Link Failure - Signalling Point Inaccessible
Determine if all LMTL devices are OOS. If all LMTL devices... are OOS... are not OOS... Then... Go to step 2. Go to step 3. Then... Wait until the MSC reboot is finished, and then go to step 3. Wait until the RXCDR reboot is finished, and then go to step 4. Go to step 4.
Determine if the MSC or RXCDR are rebooting. If... the MSC is rebooting... the RXCDR is rebooting... neither the MSC or RXCDR are rebooting...
Determine if the alarm is cleared. If the alarm is... cleared... Then... Determine the status of the LMTLs and take the appropriate action to return all LMTLs to service.
6-56
68P02901W26-Q 24 May 2004
Procedure 6-33
Last LMTL Link Failure - Signalling Point Inaccessible (Continued) The fault is probably at the SMLC. Troubleshoot the SMLC fault. Then... Determine the status of the LMTLs and take the appropriate action to return all LMTLs to service. Go to step 5. Then... Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... Determine the status of the LMTLs and take the appropriate action to return all LMTLs to service. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
not cleared... 4 Determine if the alarm is cleared. If the alarm is... cleared...
not cleared... 5 If one of the MTLs... returns to service... does not return to service...
Attempt to return one of the LMTLs to service.
Determine if the alarm is cleared. If the alarm is... cleared...
not cleared...
68P02901W26-Q 24 May 2004
6-57
50. BSS: Call Processing Failure - SMLC Detected SCCP Down

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 1 alarm. See 1. BSS: Call Processing Failure - MSC Detected SCCP Down. 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 Signalling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the BSS cannot support calls.
This is a service-affecting fault condition. 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.

Possible cause(s)
The BSS received a UPU message from the BSS-based SMLC indicating the SCCP is unavailable.
6-58
68P02901W26-Q 24 May 2004
Procedure
Procedure 6-34 Call Processing Failure - SMLC
68P02901W26-Q 24 May 2004
6-59
51. BSS: Call Processing Failure - SMLC Detected BSSAP Down

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 2 alarm. See 2. BSS: Call Processing Failure - MSC Detected BSSAP Down. The BSS reports a BSS Call Processing Failure - SMLC Detected BSSAP Down alarm when 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.
This is a service-affecting fault condition. When the BSSAP is down, the SMLC may 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.

Possible cause(s)
The BSS received a SSP message from the SMLC indicating the BSSAP is unavailable.
6-60
68P02901W26-Q 24 May 2004
Procedure
Procedure 6-35 Call Processing Failure - SMLC Detected BSSAP Down
Send a field representative to the site to resolve the alarm.
68P02901W26-Q 24 May 2004
6-61
52. BSS: No SMLC Acknowledgement for Global Reset
52. BSS: No SMLC Acknowledgement for Global Reset

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 9 alarm. See 9. No MSC Acknowledgement for Global Reset. The BSS reports a BSS No SMLC Acknowledgement for Global Reset alarm when the SMLC does not send the BSS a global reset acknowledgement message. The BSS repeated the global reset message the maximum number of times without receiving an acknowledgement from the SMLC.

Possible cause(s)
The SMLC did not acknowledge the global reset message.
Procedure
Procedure 6-36 No SMLC Acknowledgement for Global Reset
6-62
68P02901W26-Q 24 May 2004
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 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 was received by the BSS from the BSS-based SMLC.
Possible cause(s)
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-Q 24 May 2004
6-63
54. BSS: Confusion Message Received from the SMLC
54. BSS: Confusion Message Received from the SMLC

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 11 alarm. See 11. Confusion Message Received from the MSC. 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 was received by the BSS from the SMLC.
Possible cause(s)
The SMLC did not understand a layer 3 message from the BSS.
Procedure
Procedure 6-38 Clear the alarm. Confusion Message Received from the SMLC
6-64
68P02901W26-Q 24 May 2004
55. BSS: Received Page for Invalid Cell from SMLC
55. BSS: Received Page for Invalid Cell from SMLC

Description
This alarm relates to the Lb interface, but in all other respects is identical to the BSS 26 alarm. See 26. Received Page for Invalid Cell from MSC. 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 field values Byte first second third fourth fifth sixth seventh eighth Value 00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF00 to FF Definition The 8-byte ID of the invalid cell.
Possible cause(s)
The SMLC and BSS databases do not have matching cell ID lists.
Procedure
Procedure 6-39 Received Page for Invalid Cell from SMLC
Reconcile the differences in the SMLC and BSS databases. 68P02901W26-Q 24 May 2004 6-65
59. BSS: Last PCU Failed
59. BSS: Last PCU Failed

Description
The last PCU has gone out of service.

None.
Possible cause(s)
PCUs OOS.
Procedure
Procedure 6-40 Last PCU Failed
Determine why there are no PCUs available.
6-66
68P02901W26-Q 24 May 2004
Chapter
BTP alarms
This chapter details BTP Alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "1. BTP: EEPROM Flash Failure - No Valid Bootstrap Code Object Present" on page 7-5 "8. BTP: EEPROM Flash Object Failure" on page 7-7 "17. BTP: EEPROM Flash Programming Failure" on page 7-9 "21. BTP: EEPROM Flash Programming Failure" on page 7-10 "22. BTP: SWFM Indication" on page 7-11 "30. BTP: Clock A Signal Loss" on page 7-12 "31. BTP: Clock B Signal Loss" on page 7-14 "32. BTP: TDM Interface Failure - Assigned Timeslot Counter Underflow" on page 7-16 "33. BTP: TDM Interface Failure - Assigned Timeslot Counter Overflow" on page 7-18 "34. BTP: TDM Interface Failure - TDM Parity Error" on page 7-20 "35. BTP: LAN Connection Failure" on page 7-22 "39. BTP: Software Failure" on page 7-24 "40. BTP: Spurious Interrupt" on page 7-26 "42. BTP: Site Reset Occurred Due To Front Panel Reset" on page 7-28 "47. BTP: Unexpected Board Type: GPROC2 or GPROC3 expected" on page 7-29 "48. BTP: Memory location is corrupt. Replace GPROC board" on page 7-31 "50. BTP: EEPROM SW Flash Programming Failure." on page 7-32 "51. BTP: EEPROM HW Flash Programming Failure" on page 7-33 "231. BTP: TDM Interface Configuration Failure" on page 7-34 "234. BTP: Active Link Connection Failure" on page 7-36 "235. BTP: Standby Link Connection Failure" on page 7-38 "236. BTP: Slow Flash Failure" on page 7-41 "237. BTP: Non-Volatile Memory Failure" on page 7-43 7-1
Chapter 7: BTP Alarms
"239. BTP: Process Safe Test Audit Failure" on page 7-45 "254. BTP: Device Failure" on page 7-47
7-2
68P02901W26-Q 24 May 2004
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 may be equipped on one of the FRUs shown in Table 7-1. Table 7-1 BTP FRUs FRU GPROC2 {4354} GPROC3 H2SC MCU MCUF MCUm ARENAm (MCU) ARENA MAC (MCU) Description InCell GPROC2 board InCell GPROC3 board Horizon II macro Site Controller Micro Controller Unit board Micro Controller Unit board with dual FMUX M-Cellmicro Micro Controller Unit board Horizonmicro (M-Cellarena) Micro Controller Unit board Horizoncompact (M-Cellarena Macro) Micro Controller Unit board Horizonmicro2 Micro Controller Unit board Horizoncompact2 Micro Controller Unit board
HORIZONMIC2 (MCU) HORIZONCOM2 (MCU)
68P02901W26-Q 24 May 2004
7-3
At the BTS, the BTP can only be GPROC2 or GPROC3
7-4
68P02901W26-Q 24 May 2004
1. BTP: EEPROM Flash Failure - No Valid Bootstrap Code Object Present

Description

Possible cause(s)
Procedure
Procedure 7-1 1 EEPROM Flash Failure - No Valid Bootstrap Code Object Present
Determine if this alarm is occurring at other BSSs or other sites within a single BSS. If this alarm is occurring at... other BSSs other sites within a single BSS Then... Go to step 2. Go to step 4.
Obtain a new OMC-R code bootstrap object.
68P02901W26-Q 24 May 2004
7-5
Procedure 7-1 3
EEPROM Flash Failure - No Valid Bootstrap Code Object Present (Continued)
Download the new object to the affected BSSs, and then attempt to clear the alarm. If the alarm... is cleared and does not recur is not cleared or recurs Then... No further action is required. Send a field representative to the site to replace the GPROC board.
A BSS-wide outage occurs when downloading to the BSC. If the alarm... is cleared and does not recur is not cleared or recurs Then... No further action is required. Send a field representative to the site to replace the GPROC board.
7-6
68P02901W26-Q 24 May 2004
8. BTP: EEPROM Flash Object Failure

Description

Possible cause(s)
The following are possible causes for this alarm: The bootstrap code object (Object 15) at the site is corrupt. The bootstrap code object (Object 15) was corrupted while downloading to the GPROC. The bootstrap code object (Object 15) was incorrectly programmed with regard to the GPROC EEPROM address space.
Procedure
Determine if this alarm is occurring at other BSSs or other sites within a single BSS. If this alarm is occurring at... other BSSs other sites within a single BSS Then... Go to step 2. Go to step 4.
2 68P02901W26-Q 24 May 2004
Obtain a new OMC-R code object. 7-7
Procedure 7-2 3
Download the new object to the affected BSSs, and then attempt to clear the alarm. If the alarm... is cleared and does not recur is not cleared or recurs Then... No further action is required. Send a field representative to the site to replace the GPROC board.
A BSS-wide outage occurs when downloading to the BSC. If the alarm... is cleared and does not recur is not cleared or recurs Then... No further action is required. Send a field representative to the site to replace the GPROC board.
7-8
68P02901W26-Q 24 May 2004
17. BTP: EEPROM Flash Programming Failure

Description
This fault condition is not a problem unless the GPROC is being reset in which case the GPROC is rendered useless.

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
7-9

Description
This fault condition is not a problem unless the GPROC is being reset in which case the GPROC is rendered useless.

Possible cause(s)
Procedure
7-10
68P02901W26-Q 24 May 2004
22. BTP: SWFM Indication
22. BTP: SWFM Indication

Description
The system has detected a software processing error (SWFM) for a BTP.

Possible cause(s)
Procedure
Procedure 7-5 Clear the alarm. BTP: SWFM Indication
68P02901W26-Q 24 May 2004
7-11
30. BTP: Clock A Signal Loss

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 redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
7-12
68P02901W26-Q 24 May 2004
Procedure
Determine the current administrative and operational state of the site. If Site is... busy-unlocked... not busy-unlocked... Then... Go to step 2. Send a field representative to the site to replace the GCLK.
Determine if any of the following alarms were reported by other devices in the same cage as Clock A: Clock A Signal Loss 6.12 Second Reference Loss Then... Go to step 4. Send a field representative to the site to replace the redundant GCLK. Go to step 5. Then... 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. Go to step 5.
no... 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... are present on more than 50% of other devices... are present only for the BTP... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the BTP. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
68P02901W26-Q 24 May 2004
7-13
31. BTP: Clock B Signal Loss

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 redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
Procedure
Determine if the site is in service. If Site is... busy-unlocked not busy-unlocked Then... Go to step 2. Send a field representative to the site to replace the GCLK.
7-14
68P02901W26-Q 24 May 2004
Procedure 7-7 2
Determine if any of the following alarms were reported by other devices in the same cage as Clock B: Clock B Signal Loss 6.12 Second Reference Loss Then... Go to step 4. Send a field representative to the site to replace the redundant GCLK. Go to step 5. Then... 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. Go to step 5.
no... 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... are present on more than 50% of other devices... are present only for the BTP... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the BTP. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
68P02901W26-Q 24 May 2004
7-15
32. BTP: TDM Interface Failure - Assigned Timeslot Counter Underflow

Description
The BTP 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 cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane are faulty. The assigned timeslot counter register failed.
Procedure
7-16
68P02901W26-Q 24 May 2004
Procedure 7-8 2
not busy-unlocked... Reset the BTP.
The site is reset. 3 Determine the state of the BTP after the reset is completed. If BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
7-17
33. BTP: TDM Interface Failure - Assigned Timeslot Counter Overflow

Description
The BTP has determined that the TDM highway is overused. More switch-bound timeslots are driven onto the TDM bus than were allocated in the assigned timeslot counter register.

Possible cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane is faulty. The assigned timeslot counter register failed.
Procedure
7-18
68P02901W26-Q 24 May 2004
Procedure 7-9 2
not busy-unlocked... Reset the BTP.
68P02901W26-Q 24 May 2004
7-19
34. BTP: TDM Interface Failure - TDM Parity Error

Description

Possible cause(s)
Procedure
7-20
68P02901W26-Q 24 May 2004
Procedure 7-10 2
Reset the BTP.
68P02901W26-Q 24 May 2004
7-21
35. BTP: LAN Connection Failure

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 cause(s)
The following are possible causes for this alarm: The BTP was reset via software or the front panel on site. The GPROC is faulty. The LANX hardware is faulty.
Procedure
Determine the current state of the site. If site is... busy-unlocked... Then... Go to step 2.
7-22
68P02901W26-Q 24 May 2004
Procedure 7-11
LAN Connection Failure (Continued) Send a field representative to the site to replace the GPROC board.
not busy-unlocked... 2 Reset the BTP.
The site is reset. 3 Determine the state of the BTP after the reset is completed. If the BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
7-23
39. BTP: Software Failure

Description
The BTP experienced an unrecoverable SWFM error.
System action
If there is only one processor in the site, the site resets. 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 programmers.
Possible cause(s)
The following are possible causes for this alarm: The BTP software is faulty. The GPROC is faulty.
Procedure
7-24
68P02901W26-Q 24 May 2004
Procedure 7-12 2 3
Software Failure (Continued)
Send a field representative to the site to replace the GPROC board. Determine the state of the BTP. If the BTP is... busy-unlocked... Then... The alarm was probably caused by a software error. Contact a Motorola representative to resolve the software error. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
7-25
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 cause(s)
The following are possible causes for this alarm: The timer on the BTP 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 other cause. The backplane connections to any of the MCAP boards are faulty. The GPROC board is faulty.
7-26
68P02901W26-Q 24 May 2004
Procedure
Determine if the site was reset. If the site was... reset... not reset... Then... Go to step 2. Go to step 3. Then... Go to step 3. Go to step 4. Then... The fault condition no longer exists. No further action is required. Go to step 4.
Determine the current state of the site. If the site is... busy-unlocked... not busy-unlocked...
Determine the current state of the BTP. If the BTP is... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
7-27
42. BTP: Site Reset Occurred Due To Front Panel Reset
42. BTP: Site Reset Occurred Due To Front Panel Reset

Clearing Type: Severity Level: Category: Intermittent Warning 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-Cellmicro, Horizon and Horizon II macro sites.

Possible cause(s)
The reset switch on the front panel of the MCU was pressed.
Procedure
Procedure 7-14 Site Reset Occurred Due To Front Panel Reset
Investigate the reason for the front panel reset of the BTP MCU.
7-28
68P02901W26-Q 24 May 2004
47. BTP: Unexpected Board Type: GPROC2 or GPROC3 expected

{4354} Clearing Type: Severity Level: Category: Intermittent Warning Equipment
Description
A GPROC was detected in a slot where the system expected to find a GPROC2 or GPROC3. BTPs only exist at InCell sites, GPROC2s have been mandated there from GSR6 onwards. If this 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 can use 8, 16, or 32 timeslots.

Possible cause(s)
If this occurs in an InCell site, the GPROC board does not come into service.
68P02901W26-Q 24 May 2004
7-29
Procedure
Verify the value assigned to the gproc_slots database parameter. If the value is... correct... Then... Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board. Change the value of the gproc_slots database parameter to the correct value and then go to Step 2.
not correct...
Reset the BTP.
The site is reset. 3 Determine the state of the BTP after the reset is completed. If BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board.
7-30
68P02901W26-Q 24 May 2004
48. BTP: Memory location is corrupt. Replace GPROC board
48. BTP: Memory location is corrupt. Replace GPROC board

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 cause(s)
Procedure
Procedure 7-16 Memory location is corrupt. Replace GPROC board
68P02901W26-Q 24 May 2004
7-31
50. BTP: EEPROM SW Flash Programming Failure.
50. BTP: EEPROM SW Flash Programming Failure.

Description

Possible cause(s)
Procedure
7-32
68P02901W26-Q 24 May 2004
51. BTP: EEPROM HW Flash Programming Failure
51. BTP: EEPROM HW Flash Programming Failure

Description

Possible cause(s)
Procedure
Procedure 7-18 EEPROM HW Flash Programming Failure
This alarm does not take the board out of service. To resolve the alarm, reset the BTP and continue to use until it is possible to replace the GPROC3 board.
68P02901W26-Q 24 May 2004
7-33
231. BTP: TDM Interface Configuration Failure

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

Possible cause(s)
7-34
68P02901W26-Q 24 May 2004
Procedure
Determine the state of the BTP. If BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to Step 2
68P02901W26-Q 24 May 2004
7-35
234. BTP: Active Link Connection Failure

Description
The transceiver unit active link connection to the active BTP failed.
This alarm is reported for M-Cell2, M-Cell6, M-Cellmicro, Horizon and Horizon 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 may involve a combination of these hardware units: FOX, FMUX, MCU, XMUX or transceiver unit.

HDLC data only.
Possible cause(s)
The following are possible causes for this alarm: 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 fibre link failed. A backplane connection failed.
7-36
68P02901W26-Q 24 May 2004
Procedure
Procedure 7-20 1 Active Link Connection Failure
Determine if the Device Failure (BTP 254 or DRI 254) alarm was received. If this alarm is reported with... a DRI 254 alarm... a BTP 254 alarm... neither a DRI 254 alarm or a BTP 254 alarm... Then... Send a field representative to the site to replace the transceiver unit. Send a field representative to the site to replace the MCU. Go to step 2.
Determine the state of the DRI. If DRI is... busy-unlocked orenabledunlocked... not busy-unlocked or enabled-unlocked... Then... Go to step 4. Attempt to return the DRI to service, and then go to step 3. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the transceiver unit. Go to step 4. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Attempt to return the BTP to service, and then go to step 5. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Send a field representative to the site to replace the MCU.
Determine if the alarm is clear. If the alarm is... clear...
not clear... 4 Determine the state of the BTP. If BTP is... busy-unlocked orenabledunlocked...
not busy-unlocked or enabled-unlocked... 5 Determine if the alarm is clear. If the alarm is... clear...
not clear...
68P02901W26-Q 24 May 2004
7-37
235. BTP: Standby Link Connection Failure

Clearing Type: Severity Level: Category: FMIC Minor Equipment
Description
The transceiver unit standby link connection to the standby BTP failed.
This alarm is reported for M-Cell2, M-Cell6, M-Cellmicro, Horizon and Horizon 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 may involve a combination of these hardware units: FOX, FMUX, MCU, XMUX, or transceiver unit.

HDLC data only.
Possible cause(s)
When a Horizon II mini is used to expand from a Horizon I, Horizon II or Mcell 6 cabinet with redundancy, the alarm Standby Link Connection Failure will be 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 being expanded from. The following are possible causes for this alarm: The transceiver unit failed. The BTP failed.
7-38
68P02901W26-Q 24 May 2004
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 fibre link failed. A backplane connection failed.
68P02901W26-Q 24 May 2004
7-39
Procedure
Procedure 7-21 1 Standby Link Connection Failure
Determine if the Device Failure (BTP 254) alarm was also received. If a BTP 254 alarm... is received... is not received... Then... Send a field representative to the site to replace the MCU. Go to step 2. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Attempt to return the BTP to service, and then go to step 3. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Send a field representative to the site to replace the MCU.
Determine the state of the BTP. If BTP is... busy-unlocked orenabledunlocked...
not clear...
7-40
68P02901W26-Q 24 May 2004
236. BTP: Slow Flash Failure

Description
A failure to read or write to a slow flash EEPROM was detected for the transceiver unit

Possible cause(s)
The flash EEPROM on the transceiver unit is faulty.
Procedure
Procedure 7-22 1 Slow Flash Failure
Determine the state of the DRI. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
2 3
Reset the DRI. Determine the state of the DRI after the reset is completed. If the DRI is... Then...
68P02901W26-Q 24 May 2004
7-41
Procedure 7-22
Slow Flash Failure (Continued) The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit.
busy-unlocked... not busy-unlocked...
7-42
68P02901W26-Q 24 May 2004
237. BTP: Non-Volatile Memory Failure

Description
A failure to read or write to the Non-Volatile (NV) flash EEPROM was detected for the transceiver unit

Possible cause(s)
The NV flash EEPROM on the transceiver unit is faulty.
Procedure
Procedure 7-23 1 Non-Volatile Memory Failure
Determine the state of the DRI. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
2 3
Reset the DRI. Determine the state of the DRI after the reset is completed. If the DRI is... Then...
68P02901W26-Q 24 May 2004
7-43
Procedure 7-23
Non-Volatile Memory Failure (Continued) The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit.
7-44
68P02901W26-Q 24 May 2004
239. BTP: Process Safe Test Audit Failure

Description
The BTP failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

The additional information field includes nine bytes containing process information, as shown in Table 7-2. Bytes one through eight are useful only to programmers. Byte nine is the reason code for the alarm. Table 7-2 Additional information field contents Byte nine Value 00 01 02 Definition The process that failed the audit is in an infinite loop. The cause for the failure was not determined. Higher priority processes prevented the process that failed to run. The cause for the failure was not determined.
03
Possible cause(s)
The following are possible causes for this alarm: The GPROC board is faulty. A process running on the BTP failed a safe test audit.
68P02901W26-Q 24 May 2004
7-45
Procedure
Determine the reason code displayed in the additional information field. If the error code is... 2... 0, 1, or 3... Then... Go to step 2. Go to step 3. Then... Go to step 4. Contact a Motorola representative to resolve the software error.
Perform the safe test audit on the BTP If the BTP... passes the audit... fails the audit...
Reset the BTP.
7-46
68P02901W26-Q 24 May 2004
254. BTP: Device Failure

Description
The BTP was taken OOS by the GPROC Fault Management System.
System action
The site resets.

A single byte is displayed in the additional information field identifying the type of site reset, as shown in Table 7-3. Table 7-3 Additional information field contents Value 01 02 Hard reset. Soft reset. Definition
Possible cause(s)
68P02901W26-Q 24 May 2004
7-47
Procedure
Procedure 7-25 Device Failure
Wait approximately 10 minutes after this alarm is received to allow the site to reset before following this procedure.
Determine the current state of the BTP. If the BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
Reset the BTP.
The site is reset. 3 Determine the state of the BTP after the reset is completed. If the BTP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
7-48
68P02901W26-Q 24 May 2004
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-4 "27. CAB: External Power Booster Failure" on page 8-5 "28. CAB: Database Configuration and Hardware Mismatch" on page 8-6
68P02901W26-Q 24 May 2004
8-1
Introduction to 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 may be equipped on one of the FRUs shown in Table 8-1. Table 8-1 CAB FRUs FRU ARENA ARENA MACRO HORIZONMACRO HORIZONCOMPACT2 HORIZONMICRO2 MCELL TWO MCELL MICRO MCELL CITY MCELL SIX Description Horizonmicro (M-Cellarena) cabinet Horizoncompact (M-Cellarena Macro) cabinet Horizonmacro cabinet Horizoncompact2 cabinet Horizonmicro2 cabinet M-Cell2 cabinet M-Cellmicro cabinet M-Cellcity cabinet M-Cell6 cabinet
8-2
68P02901W26-Q 24 May 2004
25. CAB: External Power Booster Amplifier 1 Failure

Description
Amplifier 1 in the external power booster failed. When this occurs, the transmitted power to Channel 1 transmit antenna is reduced to approximately 0.8W. This power reduction adversely affects macro cell coverage.
This alarm is generated only for Horizoncompact2 equipment. However, the database CAB entry for the Horizoncompact2 can also be set to Horizonmicro2. Hence this alarm is supported for both Horizoncompact2 and Horizonmicro2 database entries.

Possible cause(s)
Amplifier 1 in the external power booster failed.
Procedure
Procedure 8-1 External Power Booster Amplifier 1 Failure
Send a field representative to the site to replace the external power booster.
68P02901W26-Q 24 May 2004
8-3

Description
Amplifier 2 in the external power booster failed. When this occurs, the transmitted power to Channel 2 transmit antenna is reduced to approximately 0.8W. This power reduction adversely affects macro cell coverage.

Possible cause(s)
Amplifier 2 in the external power booster failed.
Procedure
Procedure 8-2 External Power Booster Amplifier 2 Failure
Send a field representative to the site to replace the external power booster.
8-4
68P02901W26-Q 24 May 2004
27. CAB: External Power Booster Failure
27. CAB: External Power Booster Failure

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

Possible cause(s)
The following are possible causes for this alarm: The power supply or other hardware components of the external power booster failed. The external power booster is not present.
Procedure
Procedure 8-3 External Power Booster Failure
Send a field representative to the site to determine the cause of the failure and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
8-5
28. CAB: Database Configuration and Hardware Mismatch

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, Horizonmacro and Horizon II macro. The alarm is raised or cleared only if there are one or more in-service DRIs in the cabinet.

Possible cause(s)
The database configuration is not correct for the type of hardware at the site.
Procedure
Procedure 8-4 1 2 Database Configuration and Hardware Mismatch
Determine what type of hardware is supposed to be installed at the site. Send a field representative to the site to verify if the correct type of hardware is installed at the site. The hardware is... Then...
8-6
68P02901W26-Q 24 May 2004
Procedure 8-4
Database Configuration and Hardware Mismatch (Continued) The database configuration is incorrect. Update the database to match the correct hardware. Replace the installed hardware with the correct hardware.
correct...
not correct...
68P02901W26-Q 24 May 2004
8-7
8-8
68P02901W26-Q 24 May 2004
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 "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-12 "37.- 39. CAGE: Power Supply Unit #1-3 - Over Temperature" on page 9-13 "40. CAGE: Over Temperature - Component Damage Imminent" on page 9-15 "41.- 42. CAGE: Local KSWX/DSWX Slot 0-1 Communication Failure" on page 9-17 "43.- 47. CAGE: Remote KSWX/DSWX Slot 2-6 Communication Failure" on page 9-20 "48.- 52. CAGE: Remote KSWX/DSWX Slot 24-28 Communication Failure" on page 9-23 "53.- 55. CAGE: Expansion KSWX / DSWX Slot 7- 9 Communication Failure" on page 9-26 "56.- 58. CAGE: Expansion KSWX / DSWX Slot 21-23 Communication Failure" on page 9-29 "59.- 76. CAGE: DSWX / KSWX Mismatch" on page 9-32
68P02901W26-Q 24 May 2004
9-1
Introduction to 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-Q 24 May 2004
20.- 25. CAGE: CLKX Slot 2-7 Communication Failure

Description
The system either failed to communicate with the CLKX or detected the card in the slot specified in the alarm message is not a CLKX card. CLKX cards may be installed in slots 2 through 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
Because 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-Q 24 May 2004
9-3
Table 9-1
Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Definition The hardware revision number. Reserved (not applicable) KSWX local mode KSWX remote mode KSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
The following are possible causes for this alarm: 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.
9-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 9-1 CLKX Slot 2-7 Communication Failure
68P02901W26-Q 24 May 2004
9-5
26.- 27. CAGE: LANX Slot 19-20 Communication Failure

Description
The system either failed to communicate with the LANX or detected 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 properly function.
System action
When this alarm is reported, the associated LAN and PBUS is placed OOS.

9-6
68P02901W26-Q 24 May 2004
The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the LANX card. Table 9-2 Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Any additional bytes displayed should be ignored. Definition The hardware revision number. Reserved (not applicable) KSWX local mode KSWX remote mode KSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
9-7
Procedure
Procedure 9-2 CAGE: LANX Slot 19-20 Communication Failure
9-8
68P02901W26-Q 24 May 2004
28.- 30. CAGE: Power Supply Unit#1-3 Output Failure

Description
This alarm indicates that 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 may become overloaded. If the third PSU fails, it indicates a critical condition, since the boards in the cage will not be powered.
This alarm is cleared when the affected PSU becomes operational, or when the Not Detected alarm of the affected PSU is raised.

Possible cause(s)
There is a problem with the input power supply of the PCU cage. The PSU may have failed.
68P02901W26-Q 24 May 2004
9-9
Procedure
Procedure 9-3 Power Supply Unit#1-3 Output Failure
9-10
68P02901W26-Q 24 May 2004
31.- 33. CAGE: Power Supply Unit #1-3 - Not Detected
31.- 33. CAGE: Power Supply Unit #1-3 - Not Detected

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 cause(s)
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.
Procedure
Procedure 9-4 Power Supply Unit#1-3 - Not Detected
68P02901W26-Q 24 May 2004
9-11
34.- 36 CAGE: Power Supply Unit #1-3 - Fan Failure
34.- 36 CAGE: Power Supply Unit #1-3 - Fan Failure

Description
This alarm indicates that the fan housed in the related PSU has failed Reduced air cooling may result 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 cause(s)
A mechanical fault (such as an obstruction to the fan blade) may have occurred. The fan housed in the affected PSU may have failed.
Procedure
Procedure 9-5 Power Supply Unit#1-3 - Fan Failure
Send a field representative to the site to replace the relevant PSU.
9-12
68P02901W26-Q 24 May 2004
37.- 39. CAGE: Power Supply Unit #1-3 - Over Temperature

Description
This alarm indicates that the related PSU has failed 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 cause(s)
The fan housed in the affected PSU may have failed. Shutters of the fan housed in the affected PSU may have jammed. There may be an airflow blockage. The ambient room temperature may have risen.
68P02901W26-Q 24 May 2004
9-13
Procedure
Procedure 9-6 Power Supply Unit#1-3 - Over Temperature
9-14
68P02901W26-Q 24 May 2004
40. CAGE: Over Temperature - Component Damage Imminent

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 indicates a critical failure of the cooling system in the cage or an excessive rise in ambient temperature. There may be heat damage to the system components.
This alarm is cleared when the over-temperature condition is cleared.

Possible cause(s)
All the fans may have failed. There may be an airflow blockage. The ambient room temperature may have risen.
68P02901W26-Q 24 May 2004
9-15
Procedure
Procedure 9-7 Over Temperature - Component Damage Imminent
9-16
68P02901W26-Q 24 May 2004
41.- 42. CAGE: Local KSWX/DSWX Slot 0-1 Communication Failure

{4415} Clearing Type: Severity Level: Category: FMIC Minor Communication
Description
The system either failed to communicate with the KSWX/DSWX or detected the card in the slot specified in the alarm message is not a KSWX/DSWX card. Slots 0 and 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.

68P02901W26-Q 24 May 2004
9-17
The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the KSWX/DSWX card Table 9-3 Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Any additional bytes displayed should be ignored. Definition The hardware revision number. Reserved (not applicable) KSWX/DSWX local mode KSWX/DSWX remote mode KSWX/DSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
The following are possible causes for this alarm: 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-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 9-8 Local KSWX/DSWX Slot 0-1 Communication Failure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. If a faulty KSW is not installed in the same cage as the KSWX/DSWX, the TBUS and the CBUS is placed OOS. If a standby TBUS and CBUS are unavailable, the cage is disabled causing a site reset.
68P02901W26-Q 24 May 2004
9-19
43.- 47. CAGE: Remote KSWX/DSWX Slot 2-6 Communication Failure

Description
The system either failed to communicate with the KSWX/DSWX or detected the card in the slot specified in the alarm message is not a KSWX/DSWX card. Remote KSWX/DSWXcards may 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

The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the KSWX/DSWX card.
9-20
68P02901W26-Q 24 May 2004
Table 9-4
Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Definition The hardware revision number. Reserved (not applicable) KSWX/DSWX local mode KSWX/DSWX remote mode KSWX/DSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
68P02901W26-Q 24 May 2004
9-21
Procedure
Procedure 9-9 Remote KSWX/DSWX Slot 2-6 Communication Failure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Because 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-22
68P02901W26-Q 24 May 2004

Description
The system either failed to communicate with the KSWX/DSWX or detected the card in the slot specified in the alarm message is not a KSWX/DSWX card. Remote KSWX/DSWXcards may 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

The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the KSWX/DSWX card.
68P02901W26-Q 24 May 2004
9-23
Table 9-5
Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Definition The hardware revision number. Reserved (not applicable) KSWX/DSWX local mode KSWX/DSWX remote mode KSWX/DSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
9-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 9-10 Remote KSWX/DSWX Slot 24-28 Communication Failure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Because 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.
68P02901W26-Q 24 May 2004
9-25
53.- 55. CAGE: Expansion KSWX / DSWX Slot 7- 9 Communication Failure

Description
The system either failed to communicate with the KSWX / DSWX or detected the card in the slot specified in the alarm message is not a KSWX / DSWX card. KSWX / DSWX cards may be installed in slots 7 through 9 to expand the number of TDM timeslots by adding KSWs. KSW <-> Remote KSWX / DSWX<-> Local KSWX / DSWX<-> TBUS

The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the KSWX / DSWX card.
9-26
68P02901W26-Q 24 May 2004
Table 9-6
Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Definition The hardware revision number. Reserved (not applicable) KSWX / DSWX local mode KSWX / DSWX remote mode KSWX / DSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
9-27
Procedure
Procedure 9-11 Expansion KSWX / DSWX Slot 7-9 Communication Failure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Because 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-28
68P02901W26-Q 24 May 2004
56.- 58. CAGE: Expansion KSWX / DSWX Slot 21-23 Communication Failure
Description
The system either failed to communicate with the KSWX / DSWX or detected the card in the slot specified in the alarm message is not a KSWX / DSWX card. KSWX / DSWX cards may be installed in slots 21 through 23 to expand the number of TDM timeslots by adding KSWs. KSW <-> Remote KSWX / DSWX<-> Local KSWX / DSWX<-> TBUS

The value ff is displayed if a card is not inserted in the slot or if the polling software failed to communicate with the KSWX / DSWX card.
68P02901W26-Q 24 May 2004
9-29
Table 9-7
Additional information field contents Digit first second Value (digital) 0 to 2 0 1 2 3 4 5 6 7 8 9 a b c d e f Definition The hardware revision number. Reserved (not applicable) KSWX / DSWX local mode KSWX / DSWX remote mode KSWX / DSWX expanded mode EAS Parallel Interface Extender (PIX) Alarm Interface Board (AIB) Clock Extender (CLKX) Local Area Network Extender (LANX) Power Supply, +27V Power Supply, -48V/-60V DRIX (not used) Compact -48V/-60V Power Supply Power Alarm Board (PAB) (not used) Reserved (not applicable)
Possible cause(s)
The following are possible causes for this alarm: 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-30
68P02901W26-Q 24 May 2004
Procedure
Procedure 9-12 Expansion KSWX / DSWX Slot 21-23 Communication Failure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Because 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.
68P02901W26-Q 24 May 2004
9-31
59.- 76. CAGE: DSWX / KSWX Mismatch
59.- 76. CAGE: DSWX / KSWX Mismatch

Clearing Type: FMIC
Severity Level: Category:
Major Equipment
Description
The TDM device reporting this alarm will remain out of service while this condition exists.

Additional data is 2 bytes: Byte 1 = Cage, Byte 2 = Slot.
Possible cause(s)
The following are possible causes for this alarm: The KSWX in slot 0 has been partnered with a DSWX or vice versa.
Procedure
Procedure 9-13 DSWX / KSWX Mismatch
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Replace the mismatched card with the appropriate card to match its partner. A DSWX must be partnered with another DSWX and a KSWX must be partnered with another KSWX.
9-32
68P02901W26-Q 24 May 2004
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-4 "2. CBL: Expiration of N2 - PM" on page 10-5
Chapter
68P02901W26-Q 24 May 2004
10-1
Introduction to 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-Q 24 May 2004
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, consult the CBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An invalid frame was received on the X.25 link.
Procedure
Procedure 10-1 Invalid Received Frames - PM Then... Send a field representative to the site to check the X.25 link between the CBC and the BSC, and take the appropriate corrective action. Clear the alarm.
If this alarm is... persistently reported...
not persistently reported...
68P02901W26-Q 24 May 2004
10-3
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. For further information, consult the CBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A frame reject message was received on the X.25 link.
Procedure
Procedure 10-2 FRMR-Frames - PM Determine if this alarm is persistently reported.
Then... Send a field representative to the site to check the X.25 link and take the appropriate corrective action. Clear the alarm.
10-4
68P02901W26-Q 24 May 2004
2. CBL: Expiration of N2 - PM
Clearing Type: Severity Level: Category: Intermittent Minor Communication
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. For further information, consult the CBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
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-Q 24 May 2004
10-5
Procedure
Procedure 10-3 Expiration of N2 - PM Determine if this alarm is persistently reported.
Then... Send a field representative to the site to check the X.25 link between the CBC and the BSC, and take the appropriate corrective action. Clear the alarm.
10-6
68P02901W26-Q 24 May 2004
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 Fibre Failure" on page 11-7
Chapter
68P02901W26-Q 24 May 2004
11-1
Introduction to 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-Q 24 May 2004
0. CBUS: Over 50% of Boards Detected Clock Failure

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, the associated CAGE device must be disabled. This causes a site reset. After the site reset, if this fault condition is still present, the affected CAGE may remain 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 cause(s)
The following are possible causes for this alarm: The clock fibre link failed. The backplane connections are faulty. All boards that reported the problem have failed. This is very unlikely.
68P02901W26-Q 24 May 2004
11-3
Procedure
Procedure 11-1 Over 50% of Boards Detected Clock Failure
Determine the state of the affected CBUS using the state command in a TTY window. If the CBUS is... busy-unlocked... Then... The fault condition no longer exists. Monitor the system for a recurrence of this alarm. The system successfully swapped the CBUSs. This indicates there is an equipment problem. Go to step 2. The system did not successfully swap the CBUSs. A redundant CBUS may not be equipped or available. In this case the CAGE and all devices in the CAGE remain OOS. Go to step 2. Then... Resolve the individual alarms. The fault condition no longer exists. Monitor the system for a recurrence of this alarm.
disabled-unlocked...
not busy-unlocked or disabled-unlocked...
Determine if any of the devices in the affected CAGE reported an alarm. If any devices... reported an alarm... did not report an alarm...
11-4
68P02901W26-Q 24 May 2004
2. CBUS: Master CBUS Signal Provided By Slave GCLK

Clearing Type: Severity Level: Category: FMIC Warning Equipment
Description
The clock signal output on the master CBUS is being provided by the slave GCLK.
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 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 are reset due to a loss of the clock signal.

Possible cause(s)
The following are possible causes for this alarm: The master GCLK failed. The fibre link between the CLKX board and KSWX board is faulty. The CLKX or KSWX boards are missing. Backplane problems with the CBUS associated with the master GCLK.
68P02901W26-Q 24 May 2004
11-5
Procedure
Procedure 11-2 1 Master CBUS Signal Provided By Slave GCLK
Determine the state of the master GCLK. If an alarm is... reported for the master GCLK... Then... 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. Go to step 2.
not reported for the master GCLK... 2
For detail regarding on-site equipment and repair procedures consult Maintenance Information: BSS Field Troubleshooting (68P02901W51)
11-6
68P02901W26-Q 24 May 2004
4. CBUS: Local KSWX/DSWX Clock Fibre Failure

{4415} Clearing Type: Severity Level: Category: FMIC Minor 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, the associated CAGE device must be disabled. This causes a site reset. After the site reset, if this fault condition is still present, the affected CAGE may remain 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 cause(s)
The following are possible causes for this alarm: 68P02901W26-Q 24 May 2004 The CBUS fibre link is disconnected from the local KSWX/DSWX board. The CBUS fibre link is disconnected from the CLKX port. The CBUS fibre link is faulty. The CLKX board is removed. The CLKX fibre link or the fibre port on the CLKX is faulty. The fibre port on the local KSWX/DSWX board is faulty. 11-7
Procedure
Procedure 11-3 Local KSWX/DSWX Clock Fibre Failure
11-8
68P02901W26-Q 24 May 2004
12
CELL alarms
This chapter details CELL alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "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-7 "1. CELL: Cell Radio Timeslot Capacity Loss" on page 12-9 "1. CELL: Attempt at Allocating an SDCCH Failed - PM" on page 12-10 "2. CELL: Radio Subsystem Software Error - Detected Page Overflow" on page 12-12 "2. CELL: Channel Request From MS Blocked - PM" on page 12-14 "3. CELL: Last NS-VC Failed" on page 12-16 "4. CELL: Classmark Update from MS Protocol Error - PM" on page 12-18 "5. CELL: No Cell (BVC) Block Acknowledgement from the SGSN" on page 12-20 "6. CELL: Cipher Mode Cmd from MSC Failed - PM" on page 12-21 "7. CELL: GPRS and baseband hopping configuration failure" on page 12-23 "8. CELL: GPRS unavailable - No PRP available" on page 12-25 "9. CELL: GPRS unavailable - No GDS available" on page 12-26 "9. CELL: Intra-Cell Handover Failed & Recovered PM" on page 12-27 "10. CELL: GPRS unavailable - No Cell (BVC) Reset Ack from the SGSN" on page 12-29 "10. CELL: Intra-Cell Handover Failed & Mobile Lost - PM" on page 12-31 "11. CELL: GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN" on page 12-33 "11. CELL: Intra-BSS HO Primary Target Cell Blocked - PM" on page 12-34 "12. CELL: GPRS unavailable - No PDCHs Available" on page 12-36 "13. CELL: GPRS unavailable - No GPRS capable carriers available" on page 12-37 "13. CELL: Intra-BSS HO Failed and Recovered to Org Channel - PM" on page 12-38 "14. CELL: Intra-BSS HO Failed and Mobile Lost - PM" on page 12-40 "14. CELL: GPRS unavailable - PBCCH timeslot out of sync " on page 12-42 12-1
Chapter
Chapter 12: Cell Ala s rm
"15. CELL: EGPRS unavailable - No EGPRS Carriers Available" on page 12-43 "15. CELL: Inter-BSS HO, MS HO Failed Message Received PM" on page 12-44 "17. CELL: EGPRS Unavailable - Insufficient GDS Available" on page 12-46 "18. CELL: HO failure to the MSC due to all Possible Errors Except No Channels - PM" on page 12-47 "19. CELL: Bad HO 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
12-2
68P02901W26-Q 24 May 2004
Introduction to CELL alarms
Introduction to CELL alarms
CELL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CELL device.
68P02901W26-Q 24 May 2004
12-3
0. CELL: Flow control procedure has started barring normal calls from access classes 0-9
Clearing Type: Severity Level: Category: FMIC Warning Communication
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 to limit 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 Definition 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. The alarm was generated due to RACH or AGCH congestion. 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.
Reason Code 1
2 3
12-4
68P02901W26-Q 24 May 2004
Refer to the GSM manual, Technical Description: BSS Command Reference, (68P02901W23) for a description of the SSM and TCH parameters.
Possible cause(s)
The following are possible causes for this alarm: The call traffic volume within a cell reached a critical level. The BSS is congested.
68P02901W26-Q 24 May 2004
12-5
Procedure
Procedure 12-1 Flow control procedure has started barring normal calls from access classes 0-9 Determine the traffic level on the cell.
Determine the traffic level on the cell. is high...
Then... 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. A hardware problem probably exists on the system. Initiate isolation and corrective actions to return the hardware components to service.
12-6
68P02901W26-Q 24 May 2004
0. CELL: Radio Frequency Losses While Using an SDCCH - PM

Clearing Type: Severity Level: Category: Intermittent Major Quality of Service
Description
The RF_LOSSES_SD statistic threshold has been reached. This statistic counts the number of calls lost while using a SDCCH due to RF problems. If a TCH is reconfigured as a SDCCH, only the SDCCH statistics are configured. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: MS radio problems. System hardware faults.
68P02901W26-Q 24 May 2004
12-7
Procedure
Procedure 12-2 Radio Frequency Losses While Using an SDCCH - PM Determine if there are any currently active hardware alarms.
If there are ... currently active hardware alarms...
Then... Initiate isolation and corrective procedures for the current hardware alarms. After the hardware alarms are cleared, clear the alarm. MSs are probably experiencing radio problems. Clear the alarm.
no currently active hardware alarms...
12-8
68P02901W26-Q 24 May 2004
1. CELL: Cell Radio Timeslot Capacity Loss
1. CELL: Cell Radio Timeslot Capacity Loss

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.

There is no additional Information in the output for this alarm.
Possible cause(s)
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.
68P02901W26-Q 24 May 2004
12-9
1. CELL: Attempt at Allocating an SDCCH Failed - PM
1. CELL: Attempt at Allocating an SDCCH Failed PM

Description
CELL 1 PM alarm can be generated by the ALLOC_SD_FAIL and CHAN_REQ_MS_FAIL 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 has failed, an SDCCH reject message is sent to the MS in response to that channel request. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: An SDCCH channel may not have been 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 traffic congestion.
12-10
68P02901W26-Q 24 May 2004
1. CELL: Attempt at Allocating an SDCCH Failed - PM
Procedure
Procedure 12-4 Attempt at Allocating an SDCCH Failed - PM
Determine if there are any currently active hardware alarms.
68P02901W26-Q 24 May 2004
12-11
2. CELL: Radio Subsystem Software Error - Detected Page Overflow

Clearing Type: Severity Level: Category: FMIC Investigate Quality of Service
Description
The Radio Subsystem (RSS) detected a paging queue overflow for a specific paging group within the last five minutes.

The contents of the additional information field for this alarm are shown in Table 12-2. Table 12-2 Additional information field contents Byte first Value 0 to 81 Definition 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. 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.
second
00 to 255
12-12
68P02901W26-Q 24 May 2004
Possible cause(s)
The number of control channels allocated for the cell may have been insufficient to handle the paging traffic.
Procedure
Procedure 12-5 Radio Subsystem Software Error - Detected Page Overflow
There is no operator action required.
68P02901W26-Q 24 May 2004
12-13
2. CELL: Channel Request From MS Blocked - PM

Clearing Type: Severity Level: Category: Intermittent Minor Quality of Service
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). For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: An SDCCH channel may not have been 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 traffic congestion. A TCH may not have been available due to call traffic congestion.
12-14
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-6 Channel Request From MS Blocked - PM Then... Initiate isolation and corrective procedures for the current hardware alarms. After the hardware alarms are cleared, clear the alarm. The call volume exceeds the SDCCH and/or TCH for the cell. If this alarm recurs, the number of SDCCH and/or TCH channels may need to be increased. Clear the alarm.
68P02901W26-Q 24 May 2004
12-15
3. CELL: Last NS-VC Failed

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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: Frame Relay network problems. The SGSN blocked the NS-VC. An operator deleted the NS-VC.
12-16
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-7 Last NS-VC Failed
Initiate fault isolation and resolution procedures for the frame network connections.
68P02901W26-Q 24 May 2004
12-17
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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The MS equipment may have been changed without operator knowledge.
12-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-8 Classmark Update from MS Protocol Error - PM
Then... Initiate isolation and corrective procedures for the current hardware alarms. After the hardware alarms are cleared, clear the alarm. MSs are probably experiencing protocol problems. Clear the alarm.
68P02901W26-Q 24 May 2004
12-19
5. CELL: No Cell (BVC) Block Acknowledgement from the SGSN
5. CELL: No Cell (BVC) Block Acknowledgement from the SGSN

Clearing Type: Severity Level: Category: Intermittent Major Communication
Description
The PCU has repeated the Cell BSSGP Virtual Connection (BVC) Block message the maximum number of times without receiving an acknowledgement from the Serving GPRS Support Node (SGSN).

The GSM Cell Identifier is displayed in the alarm output in the additional information field. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: A protocol error occurred. An acknowledgement message was not sent by the SGSN. Frame Relay network problems are occurring.
Procedure
Procedure 12-9 No Cell (BVC) Block Acknowledgement from the SGSN
Initiate fault isolation and resolution procedures at the SGSN, including verification of the BVC end-to-end connections. After the fault at the SGSN is resolved, clear the alarm.
12-20
68P02901W26-Q 24 May 2004
6. CELL: Cipher Mode Cmd 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, consult the Cell statistics chapter in the Maintenance Information: GSM Statistics Application (68P02901W56) manual.

Possible cause(s)
The MS did not switch correctly into encrypted communication mode when commanded to do so.
68P02901W26-Q 24 May 2004
12-21
Procedure
Procedure 12-10 Cipher Mode Cmd from MSC Failed - PM
Then... Initiate isolation and corrective procedures for the current hardware alarms. After the hardware alarms are cleared, clear the alarm. MSs are probably experiencing protocol problems. Clear the alarm.
12-22
68P02901W26-Q 24 May 2004
7. CELL: GPRS and baseband hopping configuration failure

Description
The baseband hopping configuration has failed due to GPRS being 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,... Any additional bytes displayed should be ignored.
Possible cause(s)
Baseband hopping is enabled and all of the transceiver units in the cell do not support GPRS data.
Procedure
There are two procedures to resolve this alarm.
Replace transceiver units

Procedure 12-11 GPRS and baseband hopping configuration failure (Procedure 1)
Send a field representative to the site to replace all of the transceiver units that do not support GPRS with transceiver units that do support GPRS.
68P02901W26-Q 24 May 2004
12-23
Disable baseband hopping

Procedure 12-12 GPRS and baseband hopping configuration failure (Procedure 2)
If replacement is not possible, disable baseband hopping.
12-24
68P02901W26-Q 24 May 2004
8. CELL: GPRS unavailable - No PRP available
8. CELL: GPRS unavailable - No PRP available

Clearing Type: Severity Level: Category: FMIC Critical Service quality
Description
GPRS is unavailable in this cell, as there is no PRP available. 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 alarm.
Possible cause(s)
It is possible that the current In Service PRPs cannot support all equipped cells due to overload of the configured timeslots.
Procedure
Procedure 12-13 GPRS unavailable - No PRP available
Check if there are disabled PRPs in the system, or if the system needs more PRPs to be equipped.
68P02901W26-Q 24 May 2004
12-25
9. CELL: GPRS unavailable - No GDS available
9. CELL: GPRS unavailable - No GDS available

Description
GPRS is unavailable in this cell, as there is no GDS available. The alarm is cleared if the alarm condition is resolved, or if GPRS is disabled for the cell.

Possible cause(s)
It is possible that the current In Service GDSs cannot support all equipped cells due to overload of the configured timeslots.
Procedure
Procedure 12-14 GPRS unavailable - No GDS available
Check if there are disabled GDSs in the system, or if the system needs more GDSs to be equipped. Reconfigure as necessary.
12-26
68P02901W26-Q 24 May 2004
9. CELL: Intra-Cell Handover Failed & 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 that channel assignment failure messages are received by the BSS when an intra-cell handover failed, and the call was recovered by the origination cell. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
12-27
Procedure
Procedure 12-15 Intra-Cell Handover Failed & Recovered PM
Determine if the cell parameters are correct.
If the cell parameters... are correct... are not correct...
Then... Clear the alarm. Change the parameters as required, and then clear the alarm.
12-28
68P02901W26-Q 24 May 2004
10. CELL: GPRS unavailable - No Cell (BVC) Reset Ack from the SGSN
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 cause(s)
There is no ACK from the SGSN. This indicates Frame Relay/SGSN problems.
68P02901W26-Q 24 May 2004
12-29
Procedure
Procedure 12-16 GPRS unavailable - No Cell (BVC) Reset Ack from the SGSN
Investigate why BVC could not be reset.
12-30
68P02901W26-Q 24 May 2004
10. CELL: Intra-Cell Handover Failed & Mobile Lost - PM
10. CELL: Intra-Cell Handover Failed & 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The MS did not respond to the assignment command from the BSS prior to the expiration of the intra-cell handover timer.
68P02901W26-Q 24 May 2004
12-31
10. CELL: Intra-Cell Handover Failed & Mobile Lost - PM
Procedure
Procedure 12-17 Intra-Cell Handover Failed & Mobile Lost - PM
Determine if there are any currently active DRI alarms.
If there are ... currently active DRI alarms...
Then... Initiate isolation and corrective procedures for the current DRI alarms. After the DRI alarms are cleared, clear the alarm. Clear the alarm.
no currently active DRI alarms...
12-32
68P02901W26-Q 24 May 2004
11. CELL: GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN
11. CELL: GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN
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 cause(s)
No ACK from the SGSN. This indicates Frame Relay/SGSN problems.
Procedure
Procedure 12-18 GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN
Investigate why the BVC could not be unblocked. Take appropriate corrective action.
68P02901W26-Q 24 May 2004
12-33
11. CELL: Intra-BSS HO 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The SDCCH and/or TCH capacity for the cell is not large enough to handle the call volume.
12-34
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-19 Intra-BSS HO Primary Target Cell Blocked - PM
Determine if the number of SDCCH and/or TCH channels for the cell are correct.
68P02901W26-Q 24 May 2004
12-35
12. CELL: GPRS unavailable - No PDCHs Available
12. CELL: GPRS unavailable - No PDCHs Available

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 cause(s)
The PDCHs in the cell are out of service.
Procedure
Procedure 12-20 GPRS unavailable - No PDCHs Available
Investigate why the PDCHs are out of service and take corrective action.
12-36
68P02901W26-Q 24 May 2004
13. CELL: GPRS unavailable - No GPRS capable carriers available
13. CELL: GPRS unavailable - No GPRS capable carriers available

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

Possible cause(s)
There are two possible causes: No In Service (INS) GPRS capable carriers are 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
The two procedures, depending on the causes, are: Investigate why GPRS is no longer available in the cell, and take appropriate corrective action. Reset BCCH to be a GPRS carrier.
68P02901W26-Q 24 May 2004
12-37
13. CELL: Intra-BSS HO 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 were received by the BSS when an intra-BSS handover failed, and the call was recovered by the origination cell. 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The database may contain 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.
12-38
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-22 1 Intra-BSS HO Failed and Recovered to Org Channel - PM
Determine if the neighbour cell list to verify the originating cell contains valid data. If the neighbour cell list is... correct... not correct... Then... Go to step 2 Correct the originating cell data as required, and then go to step 2. Then... Clear the alarm. Change the parameters as required, and then clear the alarm.
Determine if the length of time specified for the wait period timer is correct. If the length of time... is correct... is not correct...
68P02901W26-Q 24 May 2004
12-39
14. CELL: Intra-BSS HO 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 were received by the BSS when an intra-BSS handover failed, but the call was not recovered by the origination cell. 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The database may contain 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 may have been too short.
12-40
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-23 1 Intra-BSS HO Failed and Mobile Lost - PM
Determine if the neighbour cell list to verify the originating cell contains valid data. If the neighbour cell list is... correct... not correct... Then... Go to step 2 Correct the originating cell data as required, and then go to step 2. Then... Clear the alarm. Change the parameters as required, and then clear the alarm.
Determine if the length of time specified for the wait period timer is correct. If the length of time... is correct... is not correct...
68P02901W26-Q 24 May 2004
12-41
14. CELL: GPRS unavailable - PBCCH timeslot out of sync
14. CELL: GPRS unavailable - PBCCH timeslot out of sync

Clearing Type: Severity Level: Category: An external process dictates when fault is cleared Critical Service quality
Description
GPRS is unavailable in this cell, because the Packet Broadcast Control Channel (PBCCH) timeslot is out of synchronization.

Possible cause(s)
The PBCCH timeslot is out of synchronization.
Procedure
Procedure 12-24 GPRS unavailable - PBCCH timeslot out of sync
Check why the PBCCH is out of synchronization, and take the necessary corrective action.
12-42
68P02901W26-Q 24 May 2004
15. CELL: EGPRS unavailable - No EGPRS Carriers Available
15. CELL: EGPRS unavailable - No EGPRS Carriers Available

{23658} Clearing Type: FMIC - This alarm is cleared when other EGPRS carriers come in-service or GPRS is disabled for the cell.. Critical Service quality
Severity Level: Category:
Description
EGPRS is unavailable in this cell because there are no EGPRS capable carriers available.

Possible cause(s)
Lack of available CTU2 single-density-equipped DRIs.
Procedure
Procedure 12-25 1 2 3 4 EGPRS unavailable No EGPRS Carriers Available
Physically equip single-density CTU2 DRIs. Fix any out-of-service single-density CTU2 DRIs. Reconfigure existing double-density CTU2 DRIs as single-density CTU2 DRIs. Systematically locking and unlocking the DRIs in an appropriate manner until EGPRS service is restored in the cell.
68P02901W26-Q 24 May 2004
12-43
15. CELL: Inter-BSS HO, MS HO 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 were received by the BSS during inter-BSS handover. This alarm does not imply that a call was lost, as it might be recovered by the BSS that attempted to hand the call off. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The cell designated for the inter-BSS handover may not have been 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 may have been too short.
12-44
68P02901W26-Q 24 May 2004
Procedure
Procedure 12-26 1 Inter-BSS HO, MS HO Failed Message Received PM Determine if the BSS where the target cell is equipped is experiencing traffic congestion. If the BSS is... experiencing traffic congestion... not experiencing traffic congestion... 2 If the length of time... is correct... is not correct... 3 Then... Wait for traffic levels to return to normal levels, and then clear the alarm. Go to step 2. Then... Go to step 3. Change the parameters as required, and then clear the alarm. Then... Clear the alarm. Add resources as required and then clear the alarm.
Determine if the length of time specified for the wait period timer is correct.
Determine if sufficient resources are available in the target cell. If the resources... are sufficient... are not sufficient...
68P02901W26-Q 24 May 2004
12-45
17. CELL: EGPRS Unavailable - Insufficient GDS Available
17. CELL: EGPRS Unavailable - Insufficient GDS Available

{23658} Clearing Type: Severity Level: Category: Alarm clears when the cell is configured for EGPRS service. Critical Service quality
Description
The cell has no EGPRS service due to lack of GDS available resources. This alarm is cleared for any of the following conditions: Last TRAU GDS OOS, last PRP OOS, last GBL OOS, last GSL OOS, Cell OOS, when the BTS loses contact with the BSC, etc.

Possible cause(s)
Lack of in-service GDS E1s.
Procedure
Procedure 12-27 EGPRS Unavailable - Insufficient GDS Available
Investigate the lack of GDS resource and take corrective action.
12-46
68P02901W26-Q 24 May 2004
18. CELL: HO 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 were sent to the MSC by the BSS, for causes other than no channel resources available. These handover failure messages were sent to notify the MSC that the BSS could not reserve the radio resource requested by the MSC. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The cell designated for the handover may not have been available for immediate assignment (allocation) due to 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 may have been too short.
68P02901W26-Q 24 May 2004
12-47
Procedure
Procedure 12-28 1 HO failure to the MSC due to all Possible Errors Except No Channels - PM Determine if the BSS where the target cell is equipped is experiencing traffic congestion. If the BSS is... experiencing traffic congestion... not experiencing traffic congestion... 2 If the length of time... is correct... is not correct... 3 Then... Wait for traffic levels to return to normal levels, and then clear the alarm. Go to step 2. Then... Go to step 3. Change the parameters as required, and then clear the alarm. Then... Clear the alarm. Add resources as required and then clear the alarm.
Determine if the length of time specified for the wait period timer is correct.
Determine if sufficient resources are available in the target cell. If the resources... are sufficient... are not sufficient...
12-48
68P02901W26-Q 24 May 2004
19. CELL: Bad HO 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 a 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 an unformatted 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The MS hardware may be faulty.
68P02901W26-Q 24 May 2004
12-49
Procedure
Procedure 12-29 Bad HO Reference Numbers from the MS - PM
12-50
68P02901W26-Q 24 May 2004
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 is being overused or does not have the capacity for the area it covers. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The Stand-alone Dedicated Control Channels (SDCCHs) may not have been available for immediate assignment due to call traffic congestion. The parameters that establish the rate for paging requests may not have been set appropriately for the paging traffic that is currently being received by that BSS. If TCH traffic is heavy, the Paging Channels (PCHs) may have overloaded the paging queue(s).
68P02901W26-Q 24 May 2004
12-51
Procedure
Procedure 12-30 Number of Calls Queued - PM Then... Clear the alarm. Change the parameters as required, and then clear the alarm.
12-52
68P02901W26-Q 24 May 2004
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 request that the BSS 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 to allocate in the BSS. When a channel request from the MSC is refused, an immediate channel assignment failure message is sent to the MSC with a cause of no radio resource available. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: An SDCCH channel may not have been available for immediate assignment due to call traffic congestion. A TCH may not have been available due to call traffic congestion.
68P02901W26-Q 24 May 2004
12-53
Procedure
Procedure 12-31 Mobile Assign Command to MS Blocked (No Channel Available) - PM
Determine if the number of SDCCH and/or TCH channels for the cell are correct.
12-54
68P02901W26-Q 24 May 2004
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 a 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. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: A software failure on a lower layer during a call-set up may have disrupted the channel assignment. A software failure on a lower layer during an intra-cell handover up may have disrupted the channel assignment.
68P02901W26-Q 24 May 2004
12-55
Procedure
Procedure 12-32 Mobile Assignment Failure from MS - PM
12-56
68P02901W26-Q 24 May 2004
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 occurs when the MSC sends the paging requests faster than they can be processed by the BSS. The BSS discards any new pages into the cell reporting the alarm. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The parameters that establish the rate for paging requests may not have been set appropriately for the paging traffic that is currently being received by that BSS. If Traffic Channel (TCH) traffic is heavy, the PCH may have overloaded the paging queue.
68P02901W26-Q 24 May 2004
12-57
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 actions provide the best results.
Modify the MSC paging strategy

Procedure 12-33 1. 2. PCH Queue Page Discard - PM (Procedure 1)
Modify the location area boundaries at the MSC to reduce the paging requests for a cell. Clear the alarm.
Change the CCCH Configuration

Procedure 12-34 1. 2. PCH Queue Page Discard - PM (Procedure 2)
Move SAACHs off the BCCH frequency to provide a higher concentration of CCCHs and therefore more PCHs. Clear the alarm.
12-58
68P02901W26-Q 24 May 2004
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 hand in. Cases involving Immediate Assignment Reject are also included in the count. For further information, consult the Cell statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: A radio may have gone OOS causing the traffic to shift to an in-service radio. This shift in traffic may have caused congestion on the TCH. If traffic is heavy, the result may be a delay in TCH allocation. The timeslot(s) related to the TCH may have gone OOS causing the traffic to shift to another in-service timeslot. This shift in traffic may have caused congestion on the timeslot(s). If traffic is heavy, the result may be a delay in TCH allocation. The TCH traffic is too heavy to allow TCH allocation.
68P02901W26-Q 24 May 2004
12-59
Procedure
Procedure 12-35 1 Attempt at Allocating a TCH Failed - PM Determine if the DRI is OOS. If the DRI is alarm... busy-unlocked... not busy-unlocked... 2 3 Reset the DRI. Determine the state of the DRI after the reset is completed. If the DRI is... busy-unlocked... not busy-unlocked... Then... Clear the alarm. Send a field representative to the site to replace the transceiver unit. Clear the alarm after the transceiver is replaced. Then... Clear the alarm. Go to step 2.
12-60
68P02901W26-Q 24 May 2004
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-5 "6. COMB: Link B Sanity Failure" on page 13-7 "7. COMB: Power Feed A Failure" on page 13-9 "8. COMB: Power Feed B Failure" on page 13-11 "9. COMB: Full Reset" on page 13-13 "10. COMB: Partial Reset" on page 13-16 "11. COMB: Cavity 5 Tuning Error" on page 13-18 "12. COMB: Cavity Combining Block 0 Failure" on page 13-20 "13. COMB: Cavity Combining Block 1 Failure" on page 13-22 "14. COMB: Processor A Failure" on page 13-24 "15. COMB: Processor B Failure" on page 13-26 "254. COMB: Device Failure" on page 13-28
Chapter
68P02901W26-Q 24 May 2004
13-1
Introduction to 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 may be equipped on one of the FRUs shown in Table 13-1. Table 13-1 FRUs that may be equipped with the COMB device FRU 900 RTC 900 CCB 1800 CCB 1900 CCB TC B0 TC B1 900 CCB0 1800 CCB0 1900 CCB0 900 CCB1 1800 CCB1 1900 CCB1 Description 900 MHz five cavity, remotely tunable combiner, type RTC hardware. 900 MHz six cavity, remotely tunable combiner, type CCB hardware. 1800 MHz six cavity, remotely tunable combiner, type CCB hardware. 1900 MHz six cavity, remotely tunable combiner, type CCB hardware. CCB Control Board 0. CCB Control Board 1. 900 MHz Cavity Combining Block 0. 1800 MHz Cavity Combining Block 0. 1900 MHz Cavity Combining Block 0. 900 MHz Cavity Combining Block 1. 1800 MHz Cavity Combining Block 1. 1900 MHz Cavity Combining Block 1.
13-2
68P02901W26-Q 24 May 2004
0.- 4. COMB: Cavity 0- 4 Tuning Error

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

The contents of the additional information field for this alarm are shown in Table 13-2. Table 13-2 Additional information field contents Byte first second third fourth fifth Value (Hex) 00 to FF 00 to FF00 to FF00 to FF00 to FF Definition The combiner address. The controlling DRI device ID.
Possible cause(s)
The following are possible causes for this alarm: The cavity tuning circuits failed. The combiner cavity is faulty. The antenna or antenna connections are faulty. The controlling DRI hardware is faulty.
68P02901W26-Q 24 May 2004
13-3
Procedure
Procedure 13-1 Cavity 0- 4 Tuning Error
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.
Determine if there were previous occurrences of this alarm. If... yes... Then... There may be an intermittent problem. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Go to step 2. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Go to step 3. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner or transceiver unit.
no... 2 Determine if the alarm has cleared. If the alarm is... clear...
not clear... 3 If the combiner... returns to service...
Attempt to restore the combiner to service.
does not return to service...
13-4
68P02901W26-Q 24 May 2004
5. COMB: Link A Sanity Failure

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.

The contents of the additional information field for this alarm are shown in Table 13-3. Table 13-3 Additional information field contents Byte first second third fourth fifth Value 00 to FF 00 to FF00 to FF00 to FF00 to FF Definition The combiner address. The controlling DRI device ID.
Possible cause(s)
Processor A on the RTC processor board failed.
68P02901W26-Q 24 May 2004
13-5
Procedure
Procedure 13-2 Link A Sanity Failure
Determine the status of the combiner. If... busy-unlocked... Then... No further action is required. If this alarm recurs, send a field representative to the site to replace the combiner or transceiver unit. Go to step 2. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner or transceiver unit.
not busy-unlocked... 2 If the combiner... returns to service...
13-6
68P02901W26-Q 24 May 2004
6. COMB: Link B Sanity Failure

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 transceivers connected to this RTC are placed OOS.

Possible cause(s)
Processor B on the RTC processor board failed.
68P02901W26-Q 24 May 2004
13-7
Procedure
Procedure 13-3 Link B Sanity Failure
Determine the status of the combiner. If... busy-unlocked... Then... No further action is required. If this alarm recurs, send a field representative to the site to replace the combiner or transceiver unit. Go to step 2. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner or transceiver unit.
not busy-unlocked... 2 If the combiner... returns to service...
13-8
68P02901W26-Q 24 May 2004
7. COMB: Power Feed A Failure

Description
The main power feed A to the combiner has failed. A combiner has two power feeds: 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.

68P02901W26-Q 24 May 2004
13-9
Possible cause(s)
The following are possible causes for this alarm: The DC power feed to the combiner failed. The RTC processor board failed. The TATI Control Board (TCB) failed. The external combiner fuse failed. A CCB/TCB fuse failed.
Procedure
Procedure 13-4 Power Feed A Failure
If IAS alarms are present from the site, investigate the IAS alarms before sending a field representative to the site.
13-10
68P02901W26-Q 24 May 2004
8. COMB: Power Feed B Failure

Description
The redundant power feed B to the combiner has failed. A combiner has two power feeds: 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.

68P02901W26-Q 24 May 2004
13-11
Possible cause(s)
The following are possible causes for this alarm: The DC power feed to the combiner failed. The RTC processor board failed. The TATI Control Board (TCB) failed. The external combiner fuse failed. A CCB/TCB fuse 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.
13-12
68P02901W26-Q 24 May 2004
9. COMB: Full Reset
9. COMB: Full Reset

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

68P02901W26-Q 24 May 2004
13-13
9. COMB: Full Reset
Possible cause(s)
The following are possible causes for this alarm: A momentary power outage occurred. The combiner autonomously forced a full reset. The reset switches on the combiner were placed into the full reset position.
Procedure
Procedure 13-6 Full Reset
Wait for at least 10 minutes after the alarm is initially reported to determine the state of the combiner. This allows sufficient time for the system to completely re-initialize the combiner, reset the DRIs, and retune the combiner cavities.
Determine if on-site maintenance is currently being performed. If on-site maintenance... is being performed... is not being performed... Then... Go to step 2. Go to step 4.
Contact on-site personnel to determine if any procedures were performed that would have affected the power to the combiner or the combiner itself. If on-site procedures... caused the alarm... did not cause the alarm... Then... Go to step 3. Go to step 4.
3 4
Wait until the on-site procedure is completed and the condition that caused the alarm no longer exists and then go to step 4. Determine the state of the combiner. If... busy-unlocked... Then... Go to step 5. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to determine the cause of the alarm and take the appropriate action.
13-14
68P02901W26-Q 24 May 2004
9. COMB: Full Reset
Procedure 13-6
Full Reset (Continued) Send a field representative to the site to check the power connections, combiner links, and/or replace the combiner. Then... The fault condition no longer exists. No further action is required. Troubleshoot the DRI fault condition.
Determine the state of the controlling DRIs. If... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
13-15
10. COMB: Partial Reset

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

Possible cause(s)
The following are possible causes for this alarm: The combiner autonomously forced a partial reset. The reset switches on the combiner were placed into a partial reset position.
13-16
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-7 Partial Reset
Wait for at least 2 minutes after the alarm is initially reported before continuing. This allows time for the combiner to complete the partial reset.
Determine if on-site maintenance is currently being performed. If on-site maintenance... is being performed... is not being performed... Then... Go to step 2. Go to step 4.
Contact on-site personnel to determine if any procedures were performed that would have affected the combiner. If on-site procedures... caused the alarm... did not cause the alarm... Then... Go to step 3. Go to step 4.
3 4
Wait until the on-site procedure is completed and the condition that caused the alarm no longer exists and then go to step 4. Determine the state of the combiner. If... busy-unlocked... Then... Go to step 5. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to determine the cause of the alarm and take the appropriate action. Send a field representative to the site to check the power connections, combiner links, and/or replace the combiner. Then... The fault condition no longer exists. No further action is required. Troubleshoot the DRI fault condition.
Determine the state of the controlling DRIs. If... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
13-17
11. COMB: Cavity 5 Tuning Error

Description
Combiner cavity 5 failed to tune correctly.

Possible cause(s)
The following are possible causes for this alarm: The cavity tuning circuit failed. The combiner cavity is faulty. The antenna or antenna connections are faulty. The controlling DRI hardware is faulty.
13-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-8 Cavity 5 Tuning Error
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 captivity.
Determine if there were previous occurrences of this alarm. If... yes... Then... There may be an intermittent problem. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Go to step 2. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Go to step 3. Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner or transceiver unit.
no... 2 Determine if the alarm has cleared. If the alarm is... clear...
not clear... 3 If the combiner... returns to service...
68P02901W26-Q 24 May 2004
13-19
12. COMB: Cavity Combining Block 0 Failure

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.

Possible cause(s)
The TATI COMB CCB 0 hardware failed.
13-20
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-9 Cavity Combining Block 0 Failure
If the combiner... returns to service...
Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner or transceiver unit.
68P02901W26-Q 24 May 2004
13-21

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.

Possible cause(s)
The TATI COMB CCB 1 hardware failed.
13-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-10 Cavity Combining Block 1 Failure
Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to replace the combiner.
68P02901W26-Q 24 May 2004
13-23
14. COMB: Processor A Failure

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

Possible cause(s)
The following are possible causes for this alarm: The TCB 0 board failed. The TCB 0 board was removed.
13-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-11 Processor A Failure
Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
13-25
15. COMB: Processor B Failure

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.

Possible cause(s)
The following are possible causes for this alarm: The TCB 1 board failed. The TCB 1 board was removed.
13-26
68P02901W26-Q 24 May 2004
Procedure
Procedure 13-12 Processor B Failure
Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
13-27
254. COMB: Device Failure

Description
The combiner was taken OOS by the Fault Management System.
When the transmit antenna is configured with multiple combiners, the loss of one of the combiners may cause a loss in output power for some frequencies.

Possible cause(s)
A fault translation by the Fault Management System.
Procedure
Procedure 13-13 1 Device Failure
Attempt to restore the combiner to service. If the combiner... returns to service... Then... No further action is required. If this alarm recurs, it indicates an intermittent fault exists at the site.
13-28
68P02901W26-Q 24 May 2004
Procedure 13-13 2
Device Failure (Continued) Go to step 2. Then... Go to step 3. Investigate and resolve the DRI alarms. If resolution of the DRI alarms does not clear this alarm, go to step 3.
does not return to service... If controlling DRIs are... busy-unlocked... not busy-unlocked...
Determine the state of the controlling DRIs.
68P02901W26-Q 24 May 2004
13-29
13-30
68P02901W26-Q 24 May 2004
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 GPROC3 expected" on page 14-6 "48. CSFP: Memory location is corrupt. Replace GPROC board." on page 14-7 "49. CSFP: Code Objects Unavailable" on page 14-8 "50. CSFP: EEPROM SW Flash Programming Failure." on page 14-10 "51. CSFP: EEPROM HW Flash Programming Failure." on page 14-11 "240. CSFP: PCMCIA Card Removed" on page 14-12
Chapter
68P02901W26-Q 24 May 2004
14-1
Introduction to 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 may be equipped on one of the FRUs shown in Table 14-1. Table 14-1 FRUs that may be equipped with the CSFP device FRU GPROC GPROC2* {4354} GPROC3* H2SC MCU Description BSC or InCell GPROC board. BSC or InCell GPROC2 board. BSC or InCell GPROC3 board. Horizon II macro Site Controller M-Cell main control unit. The CSFP hardware device supported by the CSFP software is the associated Personal Computer Memory Card International Association (PCMCIA). Horizonmacro main control unit with dual FMUX. The CSFP hardware device supported by the CSFP software is the associated PCMCIA. Horizoncompact or Horizoncompact2 or Horizonmicro or Horizonmicro2 main control unit micro. The CSFP hardware device supported by the CSFP software is the associated PCMCIA.
MCUF
MCUm
NOTE *At the BSC, CSFP can only be GPROC2 or GPROC3
14-2
68P02901W26-Q 24 May 2004
22. CSFP: SWFM Indication
22. CSFP: SWFM Indication

Description
The system has detected a software processing error (SWFM) for a CSFP.

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
14-3
35. CSFP: LAN Connection Failure

Description
The LAN connection between the master GPROC and any other equipped CSFP on the LAN failed.
System action
The system places the CSFP OOS.

Possible cause(s)
The following are possible causes for this alarm: The CSFP was reset via software or the front panel on site. A GPROC was reset by a SWFM with reason. The GPROC is faulty. The LANX hardware is faulty.
14-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 14-2 LAN Connection Failure
Determine the state of the CSFP after the reset is completed.
If the CSFP is... busy-unlocked... not busy-unlocked...
Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
14-5
47. CSFP: Unexpected Board Type: GPROC2 or GPROC3 expected
47. CSFP: Unexpected Board Type: GPROC2 or GPROC3 expected

Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or GPROC3 board. CSFPs at the BSC can only be GPROC2 or GPROC3s, everywhere else in the system they can be any board type.

Possible cause(s)
The following are possible causes for this alarm: A GPROC board is installed instead of a required GPROC2 or GPROC3 board. A GPROC board is installed and the gproc_slots database parameter is set to 32.
Procedure
Procedure 14-3 Unexpected Board Type: GPROC2 or GPROC3 expected
Send a field representative to the site to replace GPROC board with GPROC2 or GPROC3 board.
14-6
68P02901W26-Q 24 May 2004
48. CSFP: Memory location is corrupt. Replace GPROC board.
48. CSFP: Memory location is corrupt. Replace GPROC board.

Description

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
14-7
49. CSFP: Code Objects Unavailable

Description
One (or more) devices have failed to codeload 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 Horizonmacro 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, unsupported card present, faulty card present, or objects missing from card.
14-8
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: Removable flash media device is not present. Removable flash media device was inserted into BTS after the code download.
The code objects are only stored on the removable flash media device on the MCU/MCUF platforms.
Procedure
Procedure 14-5 Code Objects Unavailable
Insert a removable flash media device into the BTS and reset the BTS to download the required objects.
68P02901W26-Q 24 May 2004
14-9
50. CSFP: EEPROM SW Flash Programming Failure.
50. CSFP: EEPROM SW Flash Programming Failure.

Description

Possible cause(s)
Procedure
14-10
68P02901W26-Q 24 May 2004
51. CSFP: EEPROM HW Flash Programming Failure.
51. CSFP: EEPROM HW Flash Programming Failure.

Description

Possible cause(s)
Procedure
Procedure 14-7 EEPROM HW Flash Programming Failure.
This alarm does not take the board out of service. To resolve the alarm, reset the CSFP and continue use until it is possible to replace the GPROC3 board.
68P02901W26-Q 24 May 2004
14-11
240. CSFP: PCMCIA Card Removed

Description
The PCMCIA card was improperly removed from the slot on the MCU. The PCMCIA card contains the software and firmware objects required to properly 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 is a substantially slower process.

Possible cause(s)
The PCMCIA card was removed before the CSFP was locked.
14-12
68P02901W26-Q 24 May 2004
Procedure
Procedure 14-8 PCMCIA Card Removed
Determine if on-site maintenance is in progress at the site reporting the alarm.
If on-site maintenance is... being performed... not being performed...
Then... Contact the field representative that is on-site to reinsert the PCMCIA card. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
14-13
14-14
68P02901W26-Q 24 May 2004
15
DHP alarms
This chapter details DHP alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "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-9 "22. DHP: SWFM Indication" on page 15-10 "23. DHP: SYNC Lost Phase Lock to Master GCLK" on page 15-11 "24. DHP: Bad Clock Source or SYNC OCXO (oscillator) Replacement Required" on page 15-13 "25. DHP: SYNC Warmup Failure" on page 15-15 "26. DHP: SYNC Calibration Request" on page 15-16 "27. DHP: SYNC Shutdown Request" on page 15-18 "28. DHP: SYNC Clock Output Failure" on page 15-20 "29. DHP: SYNC Watchdog Timer Expired" on page 15-22 "30. DHP: Clock A Signal Loss" on page 15-24 "31. DHP: Clock B Signal Loss" on page 15-26 "32. DHP: TDM Interface Failure - Assigned Timeslot Counter Underflow" on page 15-27 "33. DHP: TDM Interface Failure - Assigned Timeslot Counter Overflow" on page 15-29 "34. DHP: TDM Interface Failure - TDM Parity Error" on page 15-31 "35. DHP: LAN Connection Failure" on page 15-33 "39. DHP: Software Failure" on page 15-35 "40. DHP: Spurious Interrupt" on page 15-37 "43. DHP: SYNC Not Operational" on page 15-39 "44. DHP: SYNC Calibration via Firmware Initiated" on page 15-41 "45. DHP: SYNC Phase Lock Failure" on page 15-42 15-1
Chapter
Chapter 15: DHP Alarms
"46. DHP: SYNC Invalid Mode" on page 15-44 "47. DHP: Unexpected Board Type: GPROC2 or GPROC3 expected" on page 15-46 "48. DHP: Memory location is corrupt. Replace GPROC board." on page 15-48 "50. DHP: EEPROM SW Flash Programming Failure." on page 15-49 "51. DHP: EEPROM SW Flash Programming Failure." on page 15-50 "231. DHP: TDM Interface Configuration Failure" on page 15-51 "234. DHP: Active Link Connection Failure" on page 15-53 "239. DHP: Process Safe Test Audit Failure" on page 15-55 "254. DHP: Device Failure" on page 15-57
15-2
68P02901W26-Q 24 May 2004
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 may be equipped on one of the FRUs shown in Table 15-1. Table 15-1 FRUs that may be equipped with the DHP device FRU GPROC GPROC2 {4354} GPROC3 MCU MCUF MCUm ARENAm (MCU) ARENA MAC (MCU) HORIZON MIC2 (MCU) HORIZONCOM2 (MCU) Description In-Cell GPROC board. In-Cell GPROC2 board. In-Cell GPROC3 board. Micro Control Unit board. Main Control Unit with dual FMUX. M-Cellmicro Main Control Unit board, micro. Horizonmicro (M-Cellarena) Main Control Unit. Horizoncompact (M-Cellarena Macro) Main Control Unit. Horizonmicro2 Main Control Unit. Horizoncompact2 Main Control Unit.
68P02901W26-Q 24 May 2004
15-3
1. DHP: EEPROM Flash Failure - No Valid Bootstrap Code Object Present

Description

Possible cause(s)
15-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-1 Reset the DHP. EEPROM Flash Failure - No Valid Bootstrap Code Object Present
If the alarm... is cleared and does not recur is not cleared or recurs
Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
15-5
8. DHP: EEPROM Flash Object Failure

Description

Possible cause(s)
15-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-2 Reset the DHP. EEPROM Flash Object Failure
Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the GPROC board.
68P02901W26-Q 24 May 2004
15-7
17. DHP: EEPROM Flash Programming Failure

Description
This fault condition is not a problem unless the GPROC is being reset, in which time the GPROC is rendered useless.

Possible cause(s)
Procedure
15-8
68P02901W26-Q 24 May 2004

Description

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
15-9
22. DHP: SWFM Indication
22. DHP: SWFM Indication

Description
The system has detected a software processing error (SWFM) for a DHP.

Possible cause(s)
Procedure
15-10
68P02901W26-Q 24 May 2004
23. DHP: SYNC Lost Phase Lock to Master GCLK

Description
The SYNC circuit in the MCU has lost phase lock to the master clock reference from the master MCU.
This alarm is generated only for Horizonmicro2 or Horizoncompact2 sites.

Possible cause(s)
The following are possible causes for this alarm: Noise on the HDLC link. The HDLC link is faulty.
68P02901W26-Q 24 May 2004
15-11
Procedure
Procedure 15-6 SYNC Lost Phase Lock to Master GCLK
Determine if any link alarms occurred at the same time that phase lock was lost.
If link alarms... occurred at the same time... did not occur at the same time...
Then... There is a link fault. Troubleshoot the link fault. Send a field representative to the site to replace the MCU.
15-12
68P02901W26-Q 24 May 2004
24. DHP: Bad Clock Source or SYNC OCXO (oscillator) Replacement Required
Description
One of 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.

Possible cause(s)
The following are possible causes for this alarm: The OCXO may have aged to the point where it may no longer be able to produce a valid system clock signal. An incoming clock signal is out of specification.
68P02901W26-Q 24 May 2004
15-13
Procedure
Procedure 15-7 Bad Clock Source or SYNC OCXO (oscillator) Replacement Required
If a link alarm... occurred at the same time... did not occur at the same time...
15-14
68P02901W26-Q 24 May 2004
25. DHP: SYNC Warmup Failure
25. DHP: SYNC Warmup Failure

Description
The SYNC circuitry in the MCU did not warm up to the required operating temperature within the specified warm-up time.

Possible cause(s)
SYNC circuit failure.
Procedure
Procedure 15-8 SYNC Warmup Failure
Send a field representative to the site to replace the MCU.
68P02901W26-Q 24 May 2004
15-15
26. DHP: SYNC Calibration Request

Description
The SYNC circuit requests a recalibration of the clock at the MCU.

Possible cause(s)
The following are possible causes for this alarm: Aging of clock circuitry. SYNC circuit failure.
15-16
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-9 SYNC Calibration Request
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... being powered up for the first time or was recalibrated during the previous 24-hour period...
Then... Wait 24 hours after the MCU was powered up or recalibrated. If the alarm is not cleared after 24 hours, send a field representative to the site to replace the MCU. Recalibrate the MCU GCLK. Wait 24 hours after the MCU was powered up or recalibrated. If the alarm is not cleared after 24 hours, send a field representative to the site to replace the MCU.
not being powered up for the first time or was recalibrated during the previous 24-hour period...
68P02901W26-Q 24 May 2004
15-17
27. DHP: SYNC Shutdown Request

Description
The SYNC circuit requests a shutdown. The MCU is reset.

Possible cause(s)
15-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-10 Reset the DHP. SYNC Shutdown Request
Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MCU.
68P02901W26-Q 24 May 2004
15-19
28. DHP: SYNC Clock Output Failure

Description
The SYNC circuit output clock failed. The MCU is reset.

Possible cause(s)
The following are possible causes for this alarm: SYNC circuit failure. Degraded output signal.
15-20
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-11 Reset the DHP. SYNC Clock Output Failure
68P02901W26-Q 24 May 2004
15-21
29. DHP: SYNC Watchdog Timer Expired

Description
The SYNC circuit generated a watchdog timer expiration. The MCU is reset.

Possible cause(s)
15-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-12 Reset the DHP. SYNC Watchdog Timer Expired
68P02901W26-Q 24 May 2004
15-23
30. DHP: Clock A Signal Loss

Description
The DHP 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 takes the site OOS.

Possible cause(s)
The Clock A receive circuitry is faulty.
15-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-13 Reset the DHP. Clock A Signal Loss
If the alarm... is cleared and does not recur... is not cleared or recurs...
68P02901W26-Q 24 May 2004
15-25
31. DHP: Clock B Signal Loss
31. DHP: Clock B Signal Loss

Description
The DHP detected a TDM Clock B failure. 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 internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
The Clock B receive circuitry is faulty.
Procedure
Procedure 15-14 Reset the DHP. Clock B Signal Loss
15-26
68P02901W26-Q 24 May 2004
32. DHP: TDM Interface Failure - Assigned Timeslot Counter Underflow

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 cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane are faulty. The assigned timeslot counter register failed. TDM interface problem.
68P02901W26-Q 24 May 2004
15-27
Procedure
Determine the current state of the DHP. If DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
Reset the DHP.
The site is reset. 3 Determine the state of the DHP after the reset is completed. If DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
15-28
68P02901W26-Q 24 May 2004
33. DHP: TDM Interface Failure - Assigned Timeslot Counter Overflow

Description
The DHP has determined that the TDM highway is overused. More switch-bound timeslots are driven onto the TDM bus than were allocated in the assigned timeslot counter register.

Possible cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane is faulty. The assigned timeslot counter register failed. TDM interface problem.
68P02901W26-Q 24 May 2004
15-29
Procedure
Reset the DHP.
15-30
68P02901W26-Q 24 May 2004
34. DHP: TDM Interface Failure - TDM Parity Error

Description

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
15-31
Procedure 15-17 2
Reset the DHP.
15-32
68P02901W26-Q 24 May 2004
35. DHP: LAN Connection Failure

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

Possible cause(s)
The following are possible causes for this alarm: The DHP was reset via software or the front panel on site. The GPROC is faulty. The LANX hardware is faulty.
Procedure
Determine the current state of the DHP. If DHP is... busy-unlocked... Then... Go to step 2.
68P02901W26-Q 24 May 2004
15-33
Procedure 15-18
not busy-unlocked... 2 Reset the DHP.
The site is reset. 3 Determine the state of the DHP after the reset is completed. If the DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
15-34
68P02901W26-Q 24 May 2004
39. DHP: Software Failure

Description
The DHP experienced an unrecoverable SWFM error.
System action

Possible cause(s)
The following are possible causes for this alarm: The DHP software is faulty. The GPROC is faulty.
Procedure
Determine the state of the DHP. If the DHP is... busy-unlocked... not busy-unlocked... Then... Go to step 3. Go to step 2.
68P02901W26-Q 24 May 2004
15-35
Procedure 15-19 2 3
Software Failure (Continued)
Send a field representative to the site to replace the GPROC board. Determine the state of the DHP. If the DHP is... busy-unlocked... Then... The alarm was probably caused by a software error. Contact a Motorola representative to resolve the software error. Send a field representative to the site to replace the GPROC board.
15-36
68P02901W26-Q 24 May 2004
40. DHP: Spurious Interrupt

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

Possible cause(s)
The following are possible causes for this alarm: The timer on the DHP 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 other cause. The backplane connections to any of the MCAP boards are faulty.
68P02901W26-Q 24 May 2004
15-37
Procedure
Reset the DHP.
The site is reset. 2 Determine the current state of the DHP after the reset is complete. If the DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
15-38
68P02901W26-Q 24 May 2004
43. DHP: SYNC Not Operational

Description
The SYNC circuit is still in the initializing state instead of the operational state after the initialization timer expired. The MCU is reset.

Possible cause(s)
Procedure
Procedure 15-21 1 SYNC Not Operational
Determine if the affected processor is the master processor. If the affected processor... is the master processor... is not the master processor... Then... Disable all of the DRI devices, and then go to step 2. Go to step 2.
68P02901W26-Q 24 May 2004
15-39
Procedure 15-21 2 3
SYNC Not Operational (Continued)
Reset the site. If this alarm recurs and the standby processor is now active, send a field representative to the site to replace the master MCU.
15-40
68P02901W26-Q 24 May 2004
44. DHP: SYNC Calibration via Firmware Initiated
44. DHP: SYNC Calibration via Firmware Initiated

Description
The OMC-R operator requested a firmware-directed calibration of GCLK Synchronization (SYNC) hardware.
This alarm is generated only for Horizonmicro2 or Horizoncompact2 sites. The calibration is performed on the MCU SYNC circuit. No call processing can occur on the affected MCU during the calibration process.

Possible cause(s)
The OMC-R operator requested the calibration.
Procedure
Procedure 15-22 SYNC Calibration via Firmware Initiated
This alarm condition does not require fault isolation/resolution. The MCU is automatically reset by the system after the calibration has been completed.
68P02901W26-Q 24 May 2004
15-41
45. DHP: SYNC Phase Lock Failure

Clearing Type: Severity Level: Category: FMIC Major Quality of Service
Description
The SYNC circuit has not phase locked to the master with a specified period of being set up in the slave mode.

Possible cause(s)
The following are possible causes for this alarm: Clock source lost. Calibration of SYNC circuit was initiated. Noise on the HDLC link. A faulty HDLC link.
15-42
68P02901W26-Q 24 May 2004
Procedure
Procedure 15-23 SYNC Phase Lock Failure
If a link alarm... occurred at the same time... did not occur at the same time...
68P02901W26-Q 24 May 2004
15-43
46. DHP: SYNC Invalid Mode

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 may not be able to continue normal operation.
This alarm is generated only for Horizonmicro2 or Horizoncompact2 sites. 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.
The SYNC circuitry needs to be replaced.

Possible cause(s)
The following are possible causes for this alarm: 15-44 Ageing of clock circuitry. SYNC circuitry malfunction. 68P02901W26-Q 24 May 2004
Procedure
Procedure 15-24 1 SYNC Invalid Mode
2 3
Reset the site. If this alarm recurs and the standby processor is now active, send a field representative to the site to replace the master MCU.
68P02901W26-Q 24 May 2004
15-45
47. DHP: Unexpected Board Type: GPROC2 or GPROC3 expected

Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or GPROC3 board. If this 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 board can use 8, 16, or 32 timeslots.

Possible cause(s)
If this occurs in an InCell site, the GPROC board does not come into service.
15-46
68P02901W26-Q 24 May 2004
Procedure
Verify the value assigned to the gproc_slots database parameter. If the value is... correct... Then... Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board. Change the value of the gproc_slots database parameter to the correct value and then go to Step 2.
not correct...
Reset the DHP.
The site is reset. 3 Determine the state of the DHP after the reset is completed. If DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board.
68P02901W26-Q 24 May 2004
15-47
48. DHP: Memory location is corrupt. Replace GPROC board.
48. DHP: Memory location is corrupt. Replace GPROC board.

Description

Possible cause(s)
Procedure
Immediate action is not necessary. Contact the Motorola Local Office and arrange to replace the GPROC3 board at an appropriate time.
15-48
68P02901W26-Q 24 May 2004
50. DHP: EEPROM SW Flash Programming Failure.

Description

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
15-49

Description

Possible cause(s)
Procedure
This alarm does not take the board out of service. To resolve the alarm, reset the DHP and continue use until it is possible to replace the GPROC3 board.
15-50
68P02901W26-Q 24 May 2004
231. DHP: TDM Interface Configuration Failure

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

Possible cause(s)
68P02901W26-Q 24 May 2004
15-51
Procedure
Procedure 15-29 TDM Interface Configuration Failure
Determine the state of the DHP.
If DHP is... busy-unlocked... not busy-unlocked...
15-52
68P02901W26-Q 24 May 2004
234. DHP: Active Link Connection Failure

Description
The HDLC link connection failed between the BTP on the master MCU and the DHP on the slave MCU.
This alarm is generated only for Horizonmicro2 and Horizoncompact2 sites.

Possible cause(s)
The following are possible causes for this alarm: Loss of clocking. HDLC disconnection.
Procedure
Determine if the Device Failure (DHP 254 or DRI 254) alarm was received. If this alarm is reported with... Then...
68P02901W26-Q 24 May 2004
15-53
Procedure 15-30
Active Link Connection Failure (Continued) Send a field representative to the site to replace the transceiver unit. Send a field representative to the site to replace the MCU. Go to step 2.
a DRI 254 alarm... a DHP 254 alarm... neither a DRI 254 alarm or a DHP 254 alarm... 2 Determine the state of the DRI. If DRI is... busy-unlocked orenabledunlocked... not busy-unlocked or enabled-unlocked... 3 Determine if the alarm is clear. If the alarm is... clear...
Then... Go to step 4. Attempt to return the DRI to service, and then go to step 3. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the transceiver unit. Go to step 4. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Attempt to return the DHP to service, and then go to step 5. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MCU. Send a field representative to the site to replace the MCU.
not clear... 4 Determine the state of the DHP. If DHP is... busy-unlocked orenabledunlocked...
not clear...
15-54
68P02901W26-Q 24 May 2004
239. DHP: Process Safe Test Audit Failure

Description
The DHP failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

The additional information field includes nine bytes containing process information, as shown in Table 15-2. Bytes one through eight are useful only to programmers. Byte nine is the error code for the alarm. Table 15-2 Error codesError codes Byte nine Value 00 01 02 Definition The process that failed the audit is in an infinite loop. The cause for the failure was not determined. Higher priority processes prevented the process that failed to run. The cause for the failure was not determined.
03
Possible cause(s)
The following are possible causes for this alarm: The GPROC board is faulty. A process running on the DHP failed a safe test audit.
68P02901W26-Q 24 May 2004
15-55
Procedure
Perform the safe test audit on the DHP If the DHP... passes the audit... fails the audit...
Reset the DHP.
15-56
68P02901W26-Q 24 May 2004
254. DHP: Device Failure

Description
The DHP was taken 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. Table 15-3 Site reset type Value 01 02 Hard reset. Soft reset. Definition
Possible cause(s)
68P02901W26-Q 24 May 2004
15-57
Procedure
Determine the current state of the DHP. If the DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
2 3
Reset the DHP. Determine the state of the DHP after the reset is completed. If the DHP is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
15-58
68P02901W26-Q 24 May 2004
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 "239. DPROC: Process Safe Test Audit Failure" on page 16-9
Chapter
68P02901W26-Q 24 May 2004
16-1
Introduction to 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 may be equipped on one of FRUs shown in Table 16-1. Table 16-1 DPROC FRUs FRU FORCE DPROC Unknown DPROC Description A Force DPROC processor board. A generic DPROC processor board.
16-2
68P02901W26-Q 24 May 2004
0. DPROC: Processor Communication Failure

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 cause(s)
The following are possible causes for this alarm: The DPROC board failed. The DPROC firmware is faulty. A board peripheral to the DPROC faulty.
68P02901W26-Q 24 May 2004
16-3
Procedure
Procedure 16-1 1 Processor Communication Failure
Determine the current state of the DPROC. If the DPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 2. Try to INS the DPROC. If this fails to resolve the alarm, send a field representative to the site to replace the DPROC board. Then... No further action is required. Return the devices that are not busy-unlocked to service. If any devices do not return to service, troubleshoot the individual devices.
Determine the current state of each of the devices supported by the DPROC. If the supported devices are... busy-unlocked... not busy-unlocked...
16-4
68P02901W26-Q 24 May 2004
9. DPROC: DPROC Reset Detected

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 shown in Table 16-2. Table 16-2 Reset type Value 00 02 Any additional bytes displayed should be ignored. Description Soft reset. Hard reset.
Possible cause(s)
The following are possible causes for this alarm: The DPROC board failed. The DPROC firmware is faulty. A board peripheral to the DPROC faulty.
68P02901W26-Q 24 May 2004
16-5
Procedure
Procedure 16-2 1 DPROC Reset Detected
Determine the current state of the DPROC. If the DPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 2. Send a field representative to the site to replace the DPROC board. Then... No further action is required. Return the devices that are not busy-unlocked to service. If any devices do not return to service, troubleshoot the individual devices.
Determine the current state of each of the devices supported by the DPROC. If the supported devices are... busy-unlocked... not busy-unlocked...
16-6
68P02901W26-Q 24 May 2004
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.

Possible cause(s)
A software error has occurred.
Procedure
Procedure 16-3 SWFM Indication
Clear the alarm. There is no additional OMC-R operator action required.
68P02901W26-Q 24 May 2004
16-7
39. DPROC: Software Failure
39. DPROC: Software Failure

Description
The DPROC experienced an unrecoverable SWFM error.
System action
The DPROC is reset.

Possible cause(s)
A critical software error has occurred.
Procedure
Procedure 16-4 Software Failure
There is no additional OMC-R operator action required.
16-8
68P02901W26-Q 24 May 2004
239. DPROC: Process Safe Test Audit Failure

Description
The DPROC failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

03
68P02901W26-Q 24 May 2004
16-9
Possible cause(s)
The following are possible causes for this alarm: The DPROC board is faulty. The DPROC software being audited may be faulty. The hardware being audited may be faulty. The DPROC cabling may be faulty.
Procedure
Determine the error code displayed in the additional information field. If the error code is... 2... 0, 1, or 3... Then... Go to step 3. Go to step 3. (The DPROC is reset by the system)
Reset the DPROC
The DPROC is reset. 3 Determine the state of the DPROC after the reset is completed. If the DPROC is... busy-unlocked... Then... The fault condition no longer exists for error codes 0, 1, 3. No further action is required. For error code 2, contact a Motorola representative to resolve the software error. If a manual reset has not been attempted, go to Step 2. Otherwise, send a field representative to the site to replace the DPROC board.
16-10
68P02901W26-Q 24 May 2004
17
DRI alarms
This chapter details DRI alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "2. DRI: Internal Message Error - Pointer Misalignment" on page 17-9 "3. DRI: Internal Message Error - Dual-Port RAM Segment Full" on page 17-11 "5. DRI: Superframe Counter Error (Uplink)" on page 17-13 "6. DRI: Superframe Counter Error (Downlink)" on page 17-15 "9. DRI: Channel Coder Internal Message Error" on page 17-17 "10. DRI: Dual-Port RAM Error" on page 17-19 "13. DRI: Channel Coder Internal Message Error" on page 17-21 "14. DRI: Channel Coder Internal Message Error" on page 17-23 "15. DRI: Initial Synchronization of Radio and GPRS channel failed" on page 17-25 "16. DRI: Channel Coder Internal Message Error" on page 17-27 "17. DRI: Channel Coder Internal Message Error" on page 17-29 "18. DRI: Primary Message or Hardware Interrupt Error" on page 17-31 "20. DRI: Channel Coder Internal Message Error" on page 17-35 "21. DRI: Calibration in progress" on page 17-37 "22. DRI: Radio Subsystem Software to DRI Communication Error" on page 17-38 "23. DRI: Radio Subsystem Software to DRI Communication Failure" on page 17-40 "24. DRI: TDM Interface Failure - TDM Parity Error" on page 17-42 "25. DRI: TDM Interface Failure - Assigned Timeslot Counter Overflow" on page 17-44 "26. DRI: TDM Interface Failure - Assigned Timeslot Counter Underflow" on page 17-46 "27. DRI: Clock A Signal Loss" on page 17-48 "28. DRI: Clock B Signal Loss" on page 17-50 "29. DRI: Processor Failure" on page 17-52 "30. DRI: Transceiver Re-Initialized Unexpectedly" on page 17-54 17-1
Chapter
17-2
"31. DRI: Critical Resource Exhausted" on page 17-56 "32. DRI: RF Unit Primary Sync Signal Lost " on page 17-58 "33. DRI: RF Unit HDSL Link Quality Error" on page 17-59 "34. DRI: RF Unit Reset " on page 17-60 "35. DRI: Reset Due To Recurring Fault" on page 17-62 "36. DRI: Front End Processor to Radio Subsystem Software Communication Failure" on page 17-64 "37. DRI: Hard Reset" on page 17-65 "38. DRI: BSS INTERNAL ALARM ONLY - FWFM Displayed at EMON " on page 17-67 "39. DRI: Synchronization Loss With MCU" on page 17-68 "40. - 47. DRI: Channel Coder Timeslot (0-7) Failure" on page 17-70 "48. DRI: Baseband Hopping Timeslot Counter Mismatch" on page 17-72 "49. DRI: GSM Timeslot Counter Mismatch" on page 17-74 "50. DRI: Spurious GSM Timeslot Interrupt" on page 17-76 "51. DRI: Baseband Hopping TDM Link Error" on page 17-78 "52. DRI: Baseband Hopping GSM Timeslot Misalignment" on page 17-80 "53. DRI: Channel Coder 0 Failure - Demodulation Processor 0 Failure" on page 17-83 "54. DRI: Channel Coder 0 Failure - Demodulation Processor 1 Failure" on page 17-85 "55. DRI: Channel Coder 1 Failure - Demodulation Processor 0 Failure" on page 17-87 "56. DRI: Channel Coder 1 Failure - Demodulation Processor 1 Failure" on page 17-89 "57. DRI: Transceiver to DRI Communication Error" on page 17-91 "58. DRI: Transceiver to DRI Communication Error" on page 17-93 "59. DRI: Transceiver to DRI Burst Error" on page 17-95 "60. DRI: Transceiver to DRI Burst Error" on page 17-97 "61. DRI: Transceiver to DRI Communication Error" on page 17-99 "62. DRI: Transceiver to DRI Communication Error" on page 17-101 "63. DRI: Transceiver to DRI Communication Error" on page 17-103 "64. DRI: Unrecoverable Error" on page 17-105 "65. DRI: Radio Subsystem Software to DRI Communication Error Checksum Error" on page 17-107 "66. DRI: Superframe Counter Error" on page 17-110 68P02901W26-Q 24 May 2004
Chapter 17: DRI Alarms
"67. DRI: Radio Subsystem Software to DRI Communication Error - DRI Not Responding" on page 17-112 "70. DRI: Equalizer Control Processor Failure - Watchdog Timer Expired" on page 17-114 "71. DRI: Unexpected Communications Bus Interrupt" on page 17-116 "72. DRI: Receiver Failure" on page 17-118 "73. DRI: Power Amplifier Error" on page 17-120 "74. DRI: Cell Transmit Power Unachievable" on page 17-122 "76. DRI: Radio Subsystem Software to DRI Communication Error " on page 17-124 "78. DRI: TX VSWR Antenna Fault" on page 17-126 "80. DRI: Transmitter Synthesizer Failure" on page 17-127 "81. DRI: Transmitter Synthesizer Failure" on page 17-129 "82. DRI: Transmitter Synthesizer Failure" on page 17-131 "83. DRI: Transmitter Synthesizer Failure" on page 17-133 "84. DRI: Transmitter Synthesizer Failure" on page 17-135 "85. DRI: Transmitter Failure - Output Power" on page 17-137 "86. DRI: Transmitter Failure - Output Power" on page 17-139 "87. DRI: Transmitter Failure - Output Power" on page 17-141 "88. DRI: Power Amplifier Temperature High" on page 17-143 "89. DRI: Power Amplifier Communication Failure" on page 17-145 "90. DRI: Transmitter Failure - Output Power" on page 17-147 "91. DRI: Power Amplifier Power Low But Functioning" on page 17-149 "92. DRI: Power Amplifier Temperature High But Functioning" on page 17-151 "93. DRI: Transmitter Failure - Output Power" on page 17-153 "104-111. DRI: Timeslot 0-7 Configuration Failure " on page 17-155 "112. DRI: Receiver Synthesizer Failure" on page 17-157 "113. DRI: Receiver Synthesizer Failure" on page 17-159 "114. DRI: Receiver Synthesizer Failure" on page 17-161 "115. DRI: Receiver Synthesizer Failure" on page 17-163 "116. DRI: Receiver Synthesizer Failure" on page 17-165 "117. DRI: Receiver Synthesizer Failure" on page 17-167
68P02901W26-Q 24 May 2004
17-3
Chapter 17 : DRI alarms
17-4
"118. DRI: Receiver Synthesizer Failure" on page 17-169 "119. DRI: Receiver Failure" on page 17-171 "120. DRI: Receiver Failure" on page 17-173 "121. DRI: Receiver Failure" on page 17-175 "122. DRI: Receiver Failure" on page 17-177 "123. DRI: Receiver Failure" on page 17-179 "124. DRI: Receiver Failure" on page 17-181 "125. DRI: Receiver Failure" on page 17-183 "126. DRI: Receiver Failure" on page 17-185 "127. DRI: Receiver Failure" on page 17-187 "128. DRI: Receiver Failure" on page 17-189 "144. DRI: Transceiver to DRI Communication Failure" on page 17-191 "146. DRI: Transceiver to DRI Communication Failure" on page 17-194 "147. DRI: Transceiver to DRI Communication Failure" on page 17-196 "148. DRI: Transceiver to DRI Communication Failure" on page 17-198 "149. DRI: Transceiver to DRI Communication Failure" on page 17-200 "150. DRI: Receive Matrix Branch 1 Control Link Failure" on page 17-202 "151. DRI: Transceiver to Combiner Communication Failure" on page 17-204 "152. DRI: Control Processor to Power Amplifier Communication Failure" on page 17-206 "153. DRI: Control Processor to Equalizer Communication Failure" on page 17-208 "154. DRI: Power Supply Failure" on page 17-210 "155. DRI: Transceiver to DRI Communication Error" on page 17-212 "156. DRI: Control Processor Message Queue Overflowed" on page 17-214 "157. DRI: Receiver Input Overflowed" on page 17-216 "158. DRI: Receiver Input Overflowed" on page 17-218 "159. DRI: Equalizer Output Overflowed" on page 17-220 "160. DRI: Equalizer Output Overflowed" on page 17-222 "161. DRI: Transmitter Out of Synchronization" on page 17-224 "162. DRI: Receive Matrix Branch 2 Control Link Failure" on page 17-226 "163. DRI: Transceiver to DRI Communication Failure" on page 17-228 68P02901W26-Q 24 May 2004
Chapter 17: DRI Alarms
68P02901W26-Q 24 May 2004
"164.
DRI: Transceiver to DRI Communication Failure" on page 17-230
"165. DRI: Transceiver to DRI Communication Failure" on page 17-232 "166. DRI: Control Processor Firmware Failure" on page 17-234 "167. DRI: Control Processor Configuration Mismatch" on page 17-236 "168. DRI: Equalizer Configuration Mismatch" on page 17-238 "169. DRI: Transceiver to DRI Communication Failure" on page 17-240 "170. DRI: M-Cell Micro Interconnect Failure" on page 17-242 "171. DRI: Invalid Calibration Data" on page 17-244 "176. DRI: Equalizer Timeslot (0-7) Failure" on page 17-246 "184. DRI: Equalizer Firmware Failure" on page 17-248 "192. DRI: Baseband Hopping TDM Link Error" on page 17-250 "193. DRI: Baseband Hopping GSM Timeslot Misalignment" on page 17-252 "203. DRI: RF Unit Power Supply Unit - Input Failure " on page 17-254 "204. DRI: RF Unit Over Temperature " on page 17-255 "205. DRI: RF Unit Low Voltage Disconnect Imminent " on page 17-256 "206. DRI: RF Unit External Alarm Input " on page 17-257 "207. DRI: Internal Communication Error " on page 17-258 "208. DRI: Power Amplifier Temperature" on page 17-259 "210. DRI: Hopping DRI Failure" on page 17-260 "211. DRI: Front End Processor Failure" on page 17-262 "212. DRI: Channel Coder Failure" on page 17-264 "213. DRI: Transceiver Processor Failure" on page 17-266 "214. DRI: Equalizer Failure" on page 17-268 "215. DRI: Power Amplifier Failure" on page 17-270 "216. DRI: Transceiver Recovery Failure" on page 17-272 "217. DRI: Transmission Suspended to Conserve Battery Power" on page 17-273 "218. DRI: Invalid Transceiver Calibration Data" on page 17-274 "219. DRI: GPRS Not Supported by Radio" on page 17-275 "221. DRI: Invalid in-call modification of destination channel type " on page 17-276 "224. DRI: Safe Test Audit Failure" on page 17-277 17-5
"231. DRI: TDM Interface Configuration Failure" on page 17-279 "234. DRI: Active Link Connection Failure" on page 17-281 "235. DRI: Standby Link Connection Failure" on page 17-284 "236. DRI: Slow Flash Failure" on page 17-286 "237. DRI: Non-Volatile Memory Failure" on page 17-288 "239. DRI: Process Safe Test Audit Failure" on page 17-290 "241. DRI: Standby Link Connected to Wrong Device" on page 17-292 "243. DRI: Unlocked Device Not in Service" on page 17-294 "254. DRI: Device Failure" on page 17-295
17-6
68P02901W26-Q 24 May 2004
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. 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. A number of 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 seconds, until an acknowledgement 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 will 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 or not the error was reported. All CCDSP alarm reporting must pass through the FEP.
68P02901W26-Q 24 May 2004
17-7
FRUs
A DRI device may be equipped on one of the FRUs shown in Table 17-1. Note that for micro BTS installations, the FRU is the complete micro BTS unit. Table 17-1 FRUs that may be equipped with the DRI device FRU DRIM ACM RF Unit TCU TCUm TCUm (MRC) TCUm (RFM) TCU HI PWR CTU CTU2 TCU-B ARENA ARENA MAC ARENA MAC (MRC) Horizoncompact Horizoncompact Horizoncompact (M-Cellarena Macro) Transceiver Control Unit Micro Radio Control Unit in a Horizoncompact (M-Cellarena Macro) Radio Frequency Module in a Horizoncompact (M-Cellarena Macro) Micro Radio Control Unit in a Horizonmicro2 Radio Frequency Module in a Horizoncompact2 M-Cell Horizon Horizon II macro M-Cell Transceiver Control Unit for GSM 1800 Transceiver Control Unit Transceiver Control Unit Transceiver Control Unit for TCU900-B series radio M-Cell Transceiver Control Unit for low power transceivers (up to 16W) InCell BTS Description Digital Radio Interface Extended Memory board
ARENA MAC (RFM)
Horizoncompact
HORIZONCOM2 (MRC) HORIZONCOM2 (RFM) HORIZONMIC2(RFM) HORIZONMIC2(MRC) HORIZONMIC2(SSN) HORIZONCOM2(MRC)
Horizoncompact2 Horizoncompact2
17-8
68P02901W26-Q 24 May 2004
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.

The contents of the additional information field are shown in Table 17-2. Table 17-2 Additional information field contents Byte first second third Value (Hex) 00 to 09 00 to 80 00 to 80 Definition The DPRAM segment number. The DPRAM offset address where the fault generating this alarm occurred.
68P02901W26-Q 24 May 2004
17-9
Possible cause(s)
The following are possible causes for this alarm: 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
Monitor the DRI, and react accordingly.
If these alarms continue at an unacceptable rate, the BSS: - Resets the DRI. - Generates DRI 35 alarm.
If... the BSS takes the DRI OOS (DRI goes disabled-unlocked), and generates the DRI 254 alarm... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked...
Then... Return the DRI to service (INS), and continue to monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
17-10
68P02901W26-Q 24 May 2004
3. DRI: Internal Message Error - Dual-Port RAM Segment Full

Clearing Type: Severity Level: Category: Intermittent Major Processing
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.

The contents of the additional information field are shown in Table 17-3. Table 17-3 Additional information field contents Byte first second third Value (Hex) 00 to 09 00 to 80 00 to 80 Definition The DPRAM segment number. The DPRAM offset address where the fault generating this alarm occurred.
68P02901W26-Q 24 May 2004
17-11
Possible cause(s)
The following are possible causes for this alarm: An overflow of the DPRAM may have occurred due to a large number of messages from either the CCDSPs or the transceiver unit. A backlog in the DPRAM may have occurred because the RSS software may have simply fallen behind the FEP. A high volume of call messages.
Procedure
Procedure 17-2 1 Internal Message Error - Dual-Port RAM Segment Full
Review the alarm logs to determine if other DRIs in the same cage are also reporting this alarm. If other DRIs are... reporting this alarm... not reporting this alarm... Then... The site may be overloaded. Analyze the call traffic on the site. Go to step 2. Go to step 3. Then... Go to step 3. The fault condition no longer exists.
Wait until the traffic volume returns to normal levels. If the alarm... recurs... did not recur...
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-12
68P02901W26-Q 24 May 2004
5. DRI: Superframe Counter Error (Uplink)

Description
The Channel Coding Digital Signal Processor (CCDSP) detected a mismatch in the uplink superframe counter value.


The contents of the additional information field are shown in Table 17-4. Table 17-4 Additional information field contents Byte first second Value (hex) 00 to FF 00 to FF Definition The CCDSP reporting the mismatch. Disregard this byte.
68P02901W26-Q 24 May 2004
17-13
Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 17-3 Superframe Counter Error (Uplink)
17-14
68P02901W26-Q 24 May 2004
6. DRI: Superframe Counter Error (Downlink)

Description
The Channel Coding Digital Signal Processor (CCDSP) detected a mismatch in the downlink superframe counter value.

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.

The contents of the additional information field are shown in Table 17-5. Table 17-5 Additional information field contents Byte first second Value 00 to FF 00 to FF Definition The CCDSP reporting the mismatch. Disregard this byte.
68P02901W26-Q 24 May 2004
17-15
Possible cause(s)
The following are possible causes for this alarm: 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)
17-16
68P02901W26-Q 24 May 2004
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-Q 24 May 2004
17-17
Possible cause(s)
The following are possible causes for this alarm: The current CCH message was received by the CCDSP before the first message was completely sent out. The previous CCH message arrived at the CCDSP late. Site is overloaded.
Procedure
Procedure 17-5 Channel Coder Internal Message Error
17-18
68P02901W26-Q 24 May 2004
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.

One byte identifying the DPRAM segment number. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The DPRAM data is corrupted. The DRI hardware failed. The FEP failed. The DHP is overloaded.
Procedure
Procedure 17-6 Dual-Port RAM Error
If there is a recurrence of this alarm, 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). 68P02901W26-Q 24 May 2004 17-19
Procedure 17-6
Dual-Port RAM Error (Continued)
If the alarm does not recur, the fault condition no longer exists.
17-20
68P02901W26-Q 24 May 2004

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 cause(s)
The message was lost on its way to the CCDSP.
68P02901W26-Q 24 May 2004
17-21
Procedure
17-22
68P02901W26-Q 24 May 2004

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


68P02901W26-Q 24 May 2004
17-23
Possible cause(s)
The following are possible causes for this alarm: The message was lost on its way to the CCDSP. A bad state change message was received by the CCSP.
Procedure
17-24
68P02901W26-Q 24 May 2004
15. DRI: Initial Synchronization of Radio and GPRS channel failed

Description
The initial synchronization of the transceiver unit and a GPRS channel failed.
All data for this alarm is in CTU2 format when reported by a CTU2.

The contents of the additional information field are shown in Table 17-9. Table 17-9 Additional information field contents Byte first Value 00 to FF Definition The Channel Coding Digital Signal Processor (CCDSP) reporting the mismatch. Disregard this byte.
second
00 to FF
Possible cause(s)
The following are possible causes for this alarm: There is a fault in the path from the radio to the PCU.
68P02901W26-Q 24 May 2004
17-25
Procedure
Procedure 17-9 Initial Synchronization of Radio and GPRS channel failed
Use the following procedure to resolve the alarm. 1. 2. Take appropriate corrective action to rectify any faults found. Check the communication links and the devices in the path from the radio to the PCU.
17-26
68P02901W26-Q 24 May 2004

Description
An error in the byte count of a channel coder internal message between the RSS and DRI was detected.


second
00 to FF
Possible cause(s)
The following are possible causes for this alarm: A message pointer was corrupted between the RSS and the DRI. The message was corrupted between the RSS and the DRI.
68P02901W26-Q 24 May 2004
17-27
Procedure
17-28
68P02901W26-Q 24 May 2004

Description
The checksum of the host message was invalid and corrupted the host port.


second
00 to FF
Possible cause(s)
The following are possible causes for this alarm: A message pointer was corrupted between the RSS and the DRI. The message was corrupted between the RSS and the DRI.
68P02901W26-Q 24 May 2004
17-29
Procedure
17-30
68P02901W26-Q 24 May 2004
18. DRI: Primary Message or Hardware Interrupt Error

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 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. Note that if the DRI is operating in dual carrier mode, both DRIs will be affected by the reset and OOS actions.

Possible cause(s)
The following are possible causes for this alarm: There is a hardware problem with one of the firmware critical interrupts. A firmware application fails to receive a critical message correctly.
68P02901W26-Q 24 May 2004
17-31
Procedure
Procedure 17-12 Primary Message or Hardware Interrupt Error
Monitor the DRI. The BSS resets the DRI if these alarms continue at an unacceptable rate. If the BSS takes the DRI OOS, the INS the DRI and monitor again. If the BSS takes the DRI OOS because of the same alarm, then replace the DRI.
17-32
68P02901W26-Q 24 May 2004

Description
A message has been received that is valid only for a de-activated subchannel, but the associated subchannel is not currently de-activated.


The contents of the information field are shown in Table 17-12. Table 17-12 Additional information field contents Byte first Value 00 to FF Definition The Channel Coding Digital Signal Processor (CCDSP) reporting the mismatch. Disregard this byte.
second
00 to FF
Possible cause(s)
An MPH-Deactivate Request message was lost on its way to the CCDSP.
68P02901W26-Q 24 May 2004
17-33
Procedure
17-34
68P02901W26-Q 24 May 2004

Description
A message has been received that is valid only for a activated subchannel, but the associated subchannel is not currently activated.


The contents of the information field are shown in Table 17-13. Table 17-13 Additional information field contents Byte first Value 00 to FF Definition The Channel Coding Digital Signal Processor (CCDSP) reporting the mismatch. Disregard this byte.
second
00 to FF
Possible cause(s)
A MPH-Activate Request message was lost on its way to the CCDSP.
68P02901W26-Q 24 May 2004
17-35
Procedure
17-36
68P02901W26-Q 24 May 2004
21. DRI: Calibration in progress
21. DRI: Calibration in progress

Clearing Type: Severity Level: Category: FMIC Warning Processing
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 cause(s)
The site engineer has entered a command for the DRI firmware to enter calibration test mode.
Procedure
Procedure 17-15 Calibration in progress
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.
68P02901W26-Q 24 May 2004
17-37
22. DRI: Radio Subsystem Software to DRI Communication Error

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 cause(s)
The DRI hardware failed.
17-38
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-16 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Radio Subsystem Software to DRI Communication Error Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-39
23. DRI: Radio Subsystem Software to DRI Communication Failure

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 cause(s)
The DRI hardware failed.
17-40
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-17 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Radio Subsystem Software to DRI Communication Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-41
24. DRI: TDM Interface Failure - TDM Parity Error

Description
A parity error was detected on the inbound TDM highway.
System action
The system action is to reset the DRI.

Two bytes are displayed in the additional information field containing internal software codes that are useful only to programmers. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The TDM interface circuitry on the DRI is faulty. The TDM bus interface on the KSW/KSWX failed. One or more of the signals of the TDM bus on the backplane failed.
17-42
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-18 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... TDM Interface Failure - TDM Parity Error Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the DRIM board.
68P02901W26-Q 24 May 2004
17-43
25. DRI: TDM Interface Failure - Assigned Timeslot Counter Overflow

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 cause(s)
The following are possible causes for this alarm: The TSA RAM failed. The ATC register does not have enough allocated timeslots. The MCAP interface failed. One or more of the MCAP data/address lines on the backplane failed.
17-44
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-19 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... TDM Interface Failure - Assigned Timeslot Counter Overflow Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the DRIM board.
68P02901W26-Q 24 May 2004
17-45
26. DRI: TDM Interface Failure - Assigned Timeslot Counter Underflow

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 cause(s)
The following are possible causes for this alarm: The TSA RAM failed. The ATC register does not have enough allocated timeslots. The MCAP interface failed. One or more of the MCAP data/address lines on the backplane failed.
17-46
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-20 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... TDM Interface Failure - Assigned Timeslot Counter Underflow Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the DRIM board.
68P02901W26-Q 24 May 2004
17-47
27. DRI: Clock A Signal Loss

Description
The DRI detected a TDM Clock A failure.

Possible cause(s)
The following are possible causes for this alarm: The DRI hardware failed.
17-48
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-21 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Clock A Signal Loss Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-49
28. DRI: Clock B Signal Loss

Description
The DRI detected a TDM Clock B failure.
This alarm may also be accompanied by a CBUS alarm.

Possible cause(s)
The following are possible causes for this alarm: The DRI hardware failed.
17-50
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-22 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Clock B Signal Loss Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-51
29. DRI: Processor Failure

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

Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The processor or the firmware failed.
17-52
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-23 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Processor Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-53
30. DRI: Transceiver Re-Initialized Unexpectedly

Description
The transceiver unit was reset.
System action taken

The affected DRI is soft reset when this alarm occurs.
Possible cause(s)
The following are possible causes for this alarm: The transceiver unit firmware submitted a RESET request to the RSS software. The front-panel RESET button on the transceiver was pressed.
17-54
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-24 Transceiver Re-Initialized Unexpectedly Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit.
busy-unlocked... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
17-55
31. DRI: Critical Resource Exhausted

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 resent and a DSP code load occurs. If a third indication received within ten minutes, the DRI is take OOS, resulting in a loss of capacity. If the radio is operating in Dual Carrier Mode, the associated DRI simultaneously under goes 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.
Possible cause(s)
The following are possible causes for this alarm: 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.
17-56
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-25 If... The alarm is restricted to one radio, then it is likely to be a hardware fault. This alarm is reported by other DRI devices, it is likely to be due to a software or firmware problem. Critical Resource Exhausted Then... If the BSS takes the DRI OOS; INS the DRI and monitor it. If the DRI is take OOS again due to the same alarm, replace the DRI. Reduce the call load and monitor the DRIs again.
68P02901W26-Q 24 May 2004
17-57
32. DRI: RF Unit Primary Sync Signal Lost
32. DRI: RF Unit Primary Sync Signal Lost

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 cause(s)
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-26 Check the following: Fibre Links The state of the upstream RF Units. RF Unit Primary Sync Signal Lost
17-58
68P02901W26-Q 24 May 2004
33. DRI: RF Unit HDSL Link Quality Error
33. DRI: RF Unit HDSL Link Quality Error

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 cause(s)
The quality of the HDSL link is being intermittently affected.
Procedure
Procedure 17-27 RF Unit HDSL Link Quality Error
Note the early warning condition.
68P02901W26-Q 24 May 2004
17-59
34. DRI: RF Unit Reset

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 cause(s)
Possible causes are: TDM Clock Failure. TDM Sync Failure. RSS Communication Failure. CCCP Watchdog Timeout. EQCP Watchdog Timeout.
17-60
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-28 RF Unit Reset
Replace the DRI if it does not come back into service.
68P02901W26-Q 24 May 2004
17-61
35. DRI: Reset Due To Recurring Fault

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

The contents of the additional information field are shown in Table 17-14.
17-62
68P02901W26-Q 24 May 2004
Table 17-14
Additional information field contents Byte first Value 02 Definition This value is the reset type that occurred as the result of a persistent fault alarm. The alarm code that caused the DRI to be reset.
second
02, 05, 06, 09, 13, 14, 16, 17,19, 20,39, 48, 49, 50, 57, 58, 59, 60, 61, 62, 63, 65, 66
Possible cause(s)
A persistent fault alarm affecting a specific DRI occurred six times.
Procedure
Procedure 17-29 Reset Due To Recurring Fault
Use the following procedure to resolve the alarm. 1. 2. Check the additional information field to identify the alarm code that caused the affected DRI to be reset. Refer to the description of the DRI alarm code that caused the DRI to be reset for the resolution procedure.
68P02901W26-Q 24 May 2004
17-63
36. DRI: Front End Processor to Radio Subsystem Software Communication Failure
36. DRI: Front End Processor to Radio Subsystem Software Communication Failure
Clearing Type: Severity Level: Category: Intermittent Major 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 two byte superframe count since the last sync message was received by the FEP is displayed in the additional information field. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The RSS failed to transmit the message. The physical link between the DRI and the RSS (MCAP) failed.
Procedure
Procedure 17-30 Front End Processor to Radio Subsystem Software Communication Failure
If the DRI is OOS, determine which alarm caused the DRI to go OOS, and refer to the description of that alarm for the solution procedure.
17-64
68P02901W26-Q 24 May 2004
37. DRI: Hard Reset
37. DRI: Hard Reset

Description
The DRI experienced a hard reset initiated by an operator or the DRI hardware.

Possible cause(s)
The following are possible causes for this alarm: The RESET switch on the DRIM board was pressed. A DRI hardware failure.
Procedure
Procedure 17-31 1 Hard Reset
Determine if the DRIM board was manually reset. If the DRI was... manually reset... Then... If the DRI was manually reset as part of a troubleshooting procedure for another alarm, no further action is required for this alarm.
Determine the state of the DRI.
68P02901W26-Q 24 May 2004
17-65
37. DRI: Hard Reset
Procedure 17-31
Hard Reset (Continued) Then... The fault condition no longer exists. No further action is required. Go to step 3.
If the DRI is... busy-unlocked... not busy-unlocked... 3 4 Reset the DRI.
Determine the state of the DRI after the reset is completed. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Send a field representative to the site to replace the DRIM board.
17-66
68P02901W26-Q 24 May 2004
38. DRI: BSS INTERNAL ALARM ONLY - FWFM Displayed at EMON
38. DRI: BSS INTERNAL ALARM ONLY - FWFM Displayed at EMON

Description
This is not reported to the operator. Its an internal alarm reported at the emon as a SWFM / FWFM.

N/A
Possible cause(s)
N/A
Procedure
Procedure 17-32 N/A BSS INTERNAL ALARM ONLY - FWFM Displayed at EMON
68P02901W26-Q 24 May 2004
17-67
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-Cellmicro, M-Cell2, M-Cell6, Horizonmicro, Horizonmicro2, and Horizoncompact2 sites.


The contents of the additional information field are shown in Table 17-15. Table 17-15 Additional information field contents Byte first Value DSP number Definition The unique identifier for the Channel Coding Digital Signal Processor (CCDSP). The FEP error code is expressed in the next two bytes displayed.
second and third
17-68
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The fibre optic cable is faulty. The cable connections is faulty. The communication link is faulty. The MCU is faulty. The DRI is faulty.
Procedure
Procedure 17-33 1 Synchronization Loss With MCU
If these alarms continue at an unacceptable rate, the BSS: - Resets the DRI. - Generates DRI 35 alarm. 2 Make the following checks: If... the BSS takes the DRI OOS (DRI goes disabled-unlocked), and generates the DRI 35 alarm... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Then... Return the DRI to service (INS), and continue to monitor the DRI. Send a field representative to the site to replace the transceiver unit.
68P02901W26-Q 24 May 2004
17-69
40. - 47. DRI: Channel Coder Timeslot (0-7) Failure

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.

The contents of the additional information field are shown in Table 17-16. Table 17-16 Additional information field contents Byte first and second third Value 00 to FF and 00 to FF 1 or 2 Definition FEP error code. The source of the alarm: 1 - The alarm was reported by firmware. 2 - The alarm was reported by software.
Possible cause(s)
The following are possible causes for this alarm: 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-70
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-34 Channel Coder Timeslot (0-7) Failure Then... During a low traffic period, and only then, reset the DRI. If the DRI does not return to service, send a field representative to the site to execute one of the following: is not busy-unlocked... For an InCell BTS, replace the DRIM board. For a non-InCell BTS, replace the transceiver unit.
If the DRI... is 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-Q 24 May 2004
17-71
48. DRI: Baseband Hopping Timeslot Counter Mismatch

Description
The Front End Processor (FEP) Base Band Hopping (BBH) counter was not reset to zero on the superframe boundary.


The contents of the additional information field are shown in Table 17-17. Table 17-17 Additional information field contents Byte first second third Value 00 to FF 00 to FF 00 to FF Definition Disregard this byte. Disregard this byte. The unique identifier for the Channel Coding Digital Signal Processor (CCDSP).
Possible cause(s)
The transceiver unit that generated the alarm may be faulty. 17-72 68P02901W26-Q 24 May 2004
Procedure
Procedure 17-35 Baseband Hopping Timeslot Counter Mismatch Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-73
49. DRI: GSM Timeslot Counter Mismatch

Description
The Front End Processor (FEP) DRI counter was not reset back to zero on the superframe boundary.


The contents of the additional information field are shown in Table 17-18. Table 17-18 Additional information field contents Byte first second third Value 00 to FF 00 to FF 00 to FF Definition Disregard this byte. Disregard this byte. The unique identifier for the DRI Channel Coding Digital Signal Processor (CCDSP).
Possible cause(s)
The transceiver unit that generated the alarm may be faulty.
17-74
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-36 GSM Timeslot Counter Mismatch Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-75
50. DRI: Spurious GSM Timeslot Interrupt

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

Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is OOS. The DRI baseband hopping interrupt feature is not functioning properly. The uplink portion of the transceiver unit fibre link is faulty. The transceiver unit that generates the GSM timeslot interrupt is faulty.
17-76
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-37 Spurious GSM Timeslot Interrupt Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-77
51. DRI: Baseband Hopping TDM Link Error

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 the third occurrence.

Possible cause(s)
The following are possible causes for this alarm: The TDM timeslot path connects were not configured at the KSW or the transceiver unit. The transceiver unit is faulty. The KSW hardware is faulty. The TDM hardware is faulty.
17-78
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-38 Baseband Hopping TDM Link Error Use the following procedure to resolve the alarm.
If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked...
Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-79
52. DRI: Baseband Hopping GSM Timeslot Misalignment

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


The contents of the additional information field are shown in Table 17-19. Table 17-19 Additional information field contents Byte first and second Value (hex) timeslot number Definition The TDM timeslot number on which the faulty affected by this BBH TDM link error. The hexadecimal representation of the detecting DRI device. Identifies a user-defined detecting DRI group at a site.
third fourth
05 00 to 05
17-80
68P02901W26-Q 24 May 2004
Table 17-19
Additional information field contents (Continued) Byte fifth sixth Value (hex) 00 to 18h 00 Definition Identifies a specific detecting DRI board. Serves as a placeholder for the detecting DRI.
Examples
The following are examples of how the additional information is displayed. 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 cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The TDM timeslot path connections are not correctly configured at the CCDSP. The CCDSP is faulty. The TDM link cables are faulty.
68P02901W26-Q 24 May 2004
17-81
Procedure
Procedure 17-39 Baseband Hopping GSM Timeslot Misalignment Use the following procedure to resolve the alarm.
17-82
68P02901W26-Q 24 May 2004
53. DRI: Channel Coder 0 Failure - Demodulation Processor 0 Failure

Description
The Channel Coder 0 failed as a result of the failure of demodulation processor 0.
This alarm is generated only for M-Cellmicro, MCellmacro, Horizonmicro, Horizonmicro2, and Horizoncompact2 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 the third occurrence.

Possible cause(s)
The demodulation processor 0 hardware is faulty.
Procedure
Procedure 17-40 Channel Coder 0 Failure - Demodulation Processor 0 Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-83
Procedure 17-40
Channel Coder 0 Failure - Demodulation Processor 0 Failure (Continued)
Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the transceiver unit.
17-84
68P02901W26-Q 24 May 2004

Description
System action taken


Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
17-85
Procedure 17-41
17-86
68P02901W26-Q 24 May 2004

Description
System action taken


Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
17-87
Procedure 17-42
17-88
68P02901W26-Q 24 May 2004

Description
System action taken


Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
17-89
Procedure 17-43
17-90
68P02901W26-Q 24 May 2004
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/message code for an uplink message destined for the RSS.


Possible Cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The transceiver unit firmware may have sent up an erroneous message.
Procedure
Procedure 17-44 Transceiver to DRI Communication Error Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-91
Procedure 17-44
Transceiver to DRI Communication Error (Continued)
Then... Return the DRI to service (INS), and continue to monitor the DRI. Send a field representative to the site to execute one of the following: For an InCell BTS, check the transceiver unit, the DRIM board, the DRIX board, and the fibre links. Replace each faulty item. For a non-InCell BTS, replace the transceiver unit .
17-92
68P02901W26-Q 24 May 2004

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 Cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty. The transceiver unit firmware may have sent up an erroneous message.
Procedure
68P02901W26-Q 24 May 2004
17-93
Procedure 17-45
17-94
68P02901W26-Q 24 May 2004
59. DRI: Transceiver to DRI Burst Error

Description
The first message from the transceiver unit was not the equalized data message.


Possible cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty. The transceiver unit firmware sent up an erroneous message.
Procedure
Procedure 17-46 Transceiver to DRI Burst Error Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-95
Procedure 17-46
Transceiver to DRI Burst Error (Continued)
17-96
68P02901W26-Q 24 May 2004

Description
A second equalized data message from the transceiver unit was detected within the same timeslot.


Possible cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty. The transceiver unit firmware sent up an erroneous message. The downlink baseband hopping interrupt hardware is faulty.
68P02901W26-Q 24 May 2004
17-97
Procedure
Procedure 17-47 Transceiver to DRI Burst Error Monitor the DRI, and react accordingly.
17-98
68P02901W26-Q 24 May 2004

Description
No data was sent to the Front End Processor (FEP). The FEP was expecting an equalized data message.


Possible Cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty.
Procedure
68P02901W26-Q 24 May 2004
17-99
Procedure 17-48
17-100
68P02901W26-Q 24 May 2004

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 cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty. The RCU firmware sent up an erroneous message.
68P02901W26-Q 24 May 2004
17-101
Procedure
17-102
68P02901W26-Q 24 May 2004

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 cause(s)
The following are possible causes for this alarm: The fibre link to the transceiver unit is faulty. The DRIX is faulty. The RCU firmware sent an erroneous message.
68P02901W26-Q 24 May 2004
17-103
Procedure
17-104
68P02901W26-Q 24 May 2004
64. DRI: Unrecoverable Error

Description
An unrecoverable 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.

Possible cause(s)
The following are possible causes for this alarm: Memory allocation error. Hardware failure.
68P02901W26-Q 24 May 2004
17-105
Procedure
Procedure 17-51 Unrecoverable Error
Monitor the DRI. The BSS resets the DRI if these alarms continue at an unacceptable rate. If the BSS takes the DRI OOS, the INS the DRI and monitor again. If the BSS takes the DRI OOS because of the same alarm, then replace the DRI.
17-106
68P02901W26-Q 24 May 2004
65. DRI: Radio Subsystem Software to DRI 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.


68P02901W26-Q 24 May 2004
17-107
Table 17-20
Additional information field contents Byte first Value (hex) 00 to FF Definition 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. Disregard this byte.
second
00 to FF
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 Cause(s)
The following are possible causes for this alarm: The message was corrupted by RSS software. The DPRAM is faulty.
Procedure
Procedure 17-52 Radio Subsystem Software to DRI Communication Error - Checksum Error Monitor the DRI, and react accordingly.
17-108
68P02901W26-Q 24 May 2004
Procedure 17-52 (Continued)
Radio Subsystem Software to DRI Communication Error - Checksum Error
68P02901W26-Q 24 May 2004
17-109
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.


The contents of the additional information field are shown in Table 17-21. Table 17-21 Additional information field contents Byte first Value (hex) 00 to FF Definition The Channel Coding Digital Signal Processor (CCDSP) reporting the mismatch. Disregard this byte.
second
00 to FF
17-110
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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-53 Superframe Counter Error Monitor the DRI, and react accordingly.
68P02901W26-Q 24 May 2004
17-111
67. DRI: Radio Subsystem Software to DRI Communication Error - DRI Not Responding
Description
The RSS is unable to communicate with the DRI because the DRI is not responding to higher layer messages.

Possible cause(s)
The following are possible causes for this alarm: The DRI hardware was unequipped in the system. The DRI hardware is faulty.
17-112
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-54 Radio Subsystem Software to DRI Communication Error - DRI Not Responding Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-113
70. DRI: Equalizer Control Processor Failure - Watchdog Timer Expired
70. DRI: Equalizer Control Processor Failure Watchdog Timer Expired

Description
The Equalizer Control Processor (EQCP) failed. The failure of the EQCP was indicated by the expiration of a watchdog timer.
System action taken


Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The EQCP firmware on the transceiver unit is faulty.
17-114
68P02901W26-Q 24 May 2004
70. DRI: Equalizer Control Processor Failure - Watchdog Timer Expired
Procedure
Procedure 17-55 Equalizer Control Processor Failure - Watchdog Timer Expired
Use the following procedure to resolve the alarm. If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-115
71. DRI: Unexpected Communications Bus Interrupt

Description
An intermittent hardware or message transport (PCI) error has occurred.. The master DSP has received more interrupts than messages delivered via the PCI bus.

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

Possible cause(s)
The following are possible causes for this alarm: The PCI driver is malfunctioning. There is a PCI bus hardware failure.
17-116
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-56 Unexpected Communications Bus Interrupt
Monitor the DRI. The BSS resets the DRI if these alarm indications continue at an unacceptable rate. If the BSS takes the DRI OOS because of the same alarm, then replace the DRI.
68P02901W26-Q 24 May 2004
17-117
72. DRI: Receiver Failure

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 ten minute period, the DRI is take OOS.

There is no additional information related to this alarm.
Possible Cause(s)
The following are possible causes for this alarm: IQ data was corrupted before it reached radio firmware.
17-118
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-57 Receiver Failure
Monitor the DRI. If the BSS takes the DRI OOS, reset the DRI (reset_device) and monitor again. If the BSS takes the DRI OOS because of the same alarm, then replace the DRI
68P02901W26-Q 24 May 2004
17-119
73. DRI: Power Amplifier Error

Description
A Power Amplifier (PA) phase detect or reverse power error has occurred due to one of the following: Phase detect: PA branches are no longer in phase. Reverse power: radio has too much power entering the primary output connector.
Output power may automatically be lowered as radio cannot handle full reverse power.

Possible cause(s)
The following are possible causes for this alarm: Temporary phase error may arise due to PA compression. Radio operating at full output power whilst no load is connected Faulty combiner setup such that output power of one radio is fed to the output connector of another.
17-120
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-58 Power Amplifier Error
Transmit power level may be reduced. If the alarm cannot be cleared, then the radio should be replaced.
68P02901W26-Q 24 May 2004
17-121
74. DRI: Cell Transmit Power Unachievable

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: Reason for failure: bts_txpwr_max_inner incorrect : database value = x, required value = y. Reason for failure: max_tx_bts incorrect: database value = x, required value = y. Reason for failure: combination of bts_txpwr_max_inner and Tx power offsets incorrect: database value = x, required value = y. Reason for failure: combination of max_tx_bts and Tx power offsets incorrect: database value = x, required value = y. Reason for failure:- 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.
17-122
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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-59 Cell Transmit Power Unachievable
There are two options to bring the OOS DRI INS: Use 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. 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. Note that this option must be used if the if the reason for failure is shown as Database Tx power offset out of range for this DRI type.
68P02901W26-Q 24 May 2004
17-123

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. Any additional bytes displayed should be ignored.

A one byte code representing the DPRAM segment number is displayed in the additional information field in the output for this alarm. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: 17-124 The transceiver unit is faulty. The communication link is faulty. The firmware on the transceiver unit is faulty. 68P02901W26-Q 24 May 2004
The RSS software is faulty. The BTP or DHP is faulty.
Procedure
Procedure 17-60 1 Radio Subsystem Software to DRI Communication Error
Determine if this is a recurrence of this alarm within the last 24 hours. If this alarm is... a recurrence... not a recurrence... Then... Send a field representative to the site to replace the transceiver unit. Go to step 2. Then... The fault condition no longer exists. Send a field representative to the site to replace the transceiver unit.
Determine the state of the DRI. If the DRI is... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
17-125
78. DRI: TX VSWR Antenna Fault
78. DRI: TX VSWR Antenna Fault

Description
One of the duplexer blocks has reported a transmit VSWR fault. This alarm indicates high reflected power level from TX antenna N (0-5). The additional data enumerates which duplexer block detected the failure.
Block number of problem duplexer and Firmware information.
Possible cause(s)
Broken or missing antenna/cable or poor connection to the antenna.
Procedure
Procedure 17-61 TX VSWR Antenna Fault
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. Send a service technician to troubleshoot the antenna connection.
17-126
68P02901W26-Q 24 May 2004
80. DRI: Transmitter Synthesizer Failure

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. 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 alarm translation procedure. DRI transitions are tagged to the initial alarm.

68P02901W26-Q 24 May 2004
17-127
Possible cause(s)
The following are possible causes for this alarm: 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-62 Transmitter Synthesizer Failure Use the following procedure to resolve the alarm.
17-128
68P02901W26-Q 24 May 2004

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

68P02901W26-Q 24 May 2004
17-129
Possible cause(s)
The following are possible causes for this alarm: The DC power to transmit synthesizer 2 was lost. The input reference frequency was lost. Transmit synthesizer 2 failed. The interconnect jumper is blocked. The Control Equalizer Board (CEB) failed. The RF cables are faulty.
Procedure
17-130
68P02901W26-Q 24 May 2004

Description
The output power of transmit synthesizer 1 is below the normal power range required for RF transmission.
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.

Possible cause(s)
The following are possible causes for this alarm: Transmit synthesizer 1 failed. The transmit synthesizer 1 switch failed. The transmit synthesizer 1 switch control circuits failed. The interconnect jumper to the synthesizer board is blocked. The Control Equalizer Board (CEB) failed.
68P02901W26-Q 24 May 2004
17-131
Procedure
17-132
68P02901W26-Q 24 May 2004

Description
The output power of transmit synthesizer 2 is below the normal power range required for RF transmission.
System action

Possible cause(s)
The following are possible causes for this alarm: Transmit synthesizer 2 failed. The transmit synthesizer 2 switch failed. The transmit synthesizer 2 switch control circuits failed. The interconnect jumper is blocked. The Control Equalizer Board (CEB) failed.
68P02901W26-Q 24 May 2004
17-133
Procedure
17-134
68P02901W26-Q 24 May 2004

Description
The transmit synthesizer switch failed. The transmit synthesizer switch fails when both transmit synthesizer 1 and transmit synthesizer 2 fail.
System action

Possible cause(s)
The following are possible causes for this alarm: The transmit synthesizer switch failed. The transmit synthesizer switch control circuits failed. The interconnect jumper is blocked. The transmit synthesizer 1 and transmit synthesizer 2 simultaneously failed.
68P02901W26-Q 24 May 2004
17-135
Procedure
17-136
68P02901W26-Q 24 May 2004
85. DRI: Transmitter Failure - Output Power

Description
The output power of the transmit exciter is below the power range required for RF transmission.
System action
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 the third occurrence.

Possible cause(s)
The following are possible causes for this alarm: 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 RF cables are faulty. The modulator failed.
68P02901W26-Q 24 May 2004
17-137
Procedure
Procedure 17-67 Transmitter Failure - Output Power Use the following procedure to resolve the alarm.
17-138
68P02901W26-Q 24 May 2004

Description
The output power of the transmit power amplifier is below the power range required to sustain RF transmission.
System action

68P02901W26-Q 24 May 2004
17-139
Possible cause(s)
The following are possible causes for this alarm: 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
17-140
68P02901W26-Q 24 May 2004

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

68P02901W26-Q 24 May 2004
17-141
Possible cause(s)
The power amplifier control circuits failed.
Procedure
17-142
68P02901W26-Q 24 May 2004
88. DRI: Power Amplifier Temperature High

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-Q 24 May 2004
17-143
Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 17-70 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Power Amplifier Temperature High Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the transceiver unit.
17-144
68P02901W26-Q 24 May 2004
89. DRI: Power Amplifier Communication Failure

Description
The transmit power amplifier watchdog timer expired.
System action

Possible cause(s)
The following are possible causes for this alarm: The power amplifier control processor failed due to corrupted software. The power amplifier control circuits lost DC power.
68P02901W26-Q 24 May 2004
17-145
Procedure
Procedure 17-71 Power Amplifier Communication Failure Use the following procedure to resolve the alarm.
17-146
68P02901W26-Q 24 May 2004

Description
The transmit RF modulator failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-147
Procedure
17-148
68P02901W26-Q 24 May 2004
91. DRI: Power Amplifier Power Low But Functioning

Description
The output power of the transmit power amplifier is marginally below specified limits, but calls may continue.

Possible cause(s)
The following are possible causes for this alarm: The power amplifier control circuits lost DC power. The exciter power output is low. The power amplifier components failed.
68P02901W26-Q 24 May 2004
17-149
Procedure
Procedure 17-73 Power Amplifier 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.
17-150
68P02901W26-Q 24 May 2004
92. DRI: Power Amplifier Temperature High But Functioning

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: -4dB from the set point or the minimum power level for a power amplifier.

68P02901W26-Q 24 May 2004
17-151
Possible cause(s)
The following are possible causes for this alarm: 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-74 Power Amplifier 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.
17-152
68P02901W26-Q 24 May 2004

Description
The transmitter board failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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 cables may be faulty. The power level reference (13 MHz) is lost.
68P02901W26-Q 24 May 2004
17-153
Procedure
17-154
68P02901W26-Q 24 May 2004
104-111. DRI: Timeslot 0-7 Configuration Failure

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 cause(s)
The following are possible causes for this alarm: The cell resource manager (CRM) may have been faulty. The middle man funnel (MMF) process may have been faulty. RSS may have been faulty. Front End Process(FEP) may have been faulty. Radio Channel Unit (RCU) may have been faulty.
68P02901W26-Q 24 May 2004
17-155
Procedure
Procedure 17-76 1 2 3 Timeslot 0-7 Configuration Failure
Review the DRI device alarm message for the device failed alarm: In a TTY window, enter the state command to check the operational and administrative status of the DRI. Send a field representative to the site to replace the DRI generating the alarm.
17-156
68P02901W26-Q 24 May 2004
112. DRI: Receiver Synthesizer Failure

Description
Receive 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 radios 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 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. 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 alarm translation procedure. DRI transitions are tagged to the initial alarm.

68P02901W26-Q 24 May 2004
17-157
Possible cause(s)
The following are possible causes for this alarm: 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-77 Receiver Synthesizer Failure Use the following procedure to resolve the alarm.
17-158
68P02901W26-Q 24 May 2004

Description
Receive 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
For a non-InCell BTS, the transceiver unit is reset. If the alarm occurrence has reached a 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. 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 alarm translation procedure. DRI transitions are tagged to the initial alarm.

68P02901W26-Q 24 May 2004
17-159
Possible cause(s)
The following are possible causes for this alarm: The dc power to the receive synthesizer 2 is lost. The input reference frequency is lost. The receive synthesizer 2 failed. The interconnect jumper to the receive synthesizer 2 board is blocked.
Procedure
17-160
68P02901W26-Q 24 May 2004

Description
Receive synthesizer 3 failed to maintain synchronization lock on the reference frequency.
System action
For a non-InCell BTS, the transceiver unit is reset. If the alarm occurrence has reached a 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.

Possible cause(s)
The following are possible causes for this alarm: The dc power to receive synthesizer 3 may is lost. The input reference frequency is lost. The receive synthesizer 3 failed. The interconnect jumper to the receive synthesizer 3 board is blocked.
68P02901W26-Q 24 May 2004
17-161
Procedure
17-162
68P02901W26-Q 24 May 2004

Description
The output power of receive synthesizer 1 is below the normal power range required for RF signal reception.
System action

Possible cause(s)
The following are possible causes for this alarm: The receive synthesizer 1 failed. The receive synthesizer switch failed. The receive synthesizer switch control circuits failed. The interconnect jumper to the synthesizer board is blocked. The Control Equalizer Board (CEB) failed.
68P02901W26-Q 24 May 2004
17-163
Procedure
17-164
68P02901W26-Q 24 May 2004

Description
System action

Possible Cause(s)
The following are possible causes for this alarm: The receive synthesizer 2 failed. The receive synthesizer switch failed. The receive synthesizer switch control circuits failed. The interconnect jumper to the synthesizer board is blocked. The Control Equalizer Board (CEB) failed.
68P02901W26-Q 24 May 2004
17-165
Procedure
17-166
68P02901W26-Q 24 May 2004

Description
System action

Two bytes are displayed in the additional information field containing internal software codes that are useful only to programmers. Any additional bytes displayed should be ignored. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The dc power to the synthesizer is lost. The input reference frequency is lost. The receive synthesizer failed. The interconnect jumper to the synthesizer board is blocked.
68P02901W26-Q 24 May 2004
17-167
Procedure
17-168
68P02901W26-Q 24 May 2004

Description
The receive synthesizer switch failed. The receive synthesizer switch fails when both receive synthesizer 1 and receive synthesizer 2 fail.
System action

Possible cause(s)
The following are possible causes for this alarm: The receive synthesizer switch failed. The receive synthesizer switch control circuits failed. The interconnect jumper is blocked. The simultaneous failure of receive synthesizer 1 and receive synthesizer 2. The Control Equalizer Board (CEB) failed.
68P02901W26-Q 24 May 2004
17-169
Procedure
17-170
68P02901W26-Q 24 May 2004

Description
The main receive intermediate frequency circuitry failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-171
Procedure
Procedure 17-84 Receiver Failure Use the following procedure to resolve the alarm.
17-172
68P02901W26-Q 24 May 2004

Description
The Receive Signal Strength Indicator (RSSI) branch failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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 mistuned.
68P02901W26-Q 24 May 2004
17-173
Procedure
17-174
68P02901W26-Q 24 May 2004

Description
The receiver front-end failed. This failure causes a serious loss of antenna gain.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-175
Procedure
17-176
68P02901W26-Q 24 May 2004

Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-177
Procedure
Procedure 17-87 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Receiver Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
17-178
68P02901W26-Q 24 May 2004

Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently underflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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 Q-Channel A/D converter is faulty.
68P02901W26-Q 24 May 2004
17-179
Procedure
Use the following procedure to resolve the alarm. Procedure 17-88 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Receiver Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
17-180
68P02901W26-Q 24 May 2004

Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
System action

Possible cause(s)
68P02901W26-Q 24 May 2004
17-181
Procedure
17-182
68P02901W26-Q 24 May 2004

Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently overflowed.
System action

Possible cause(s)
68P02901W26-Q 24 May 2004
17-183
Procedure
17-184
68P02901W26-Q 24 May 2004

Description
Receiver branch 1 failed. This failure causes a serious loss of receiver sensitivity.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-185
Procedure
17-186
68P02901W26-Q 24 May 2004

Description
Receiver branch 2 failed. This failure causes a serious loss of receiver sensitivity.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
17-187
Procedure
17-188
68P02901W26-Q 24 May 2004

Description
The Radio Frequency Module (RFM) receiver board at a M-Cellmicro site failed.
System action

Possible cause(s)
The following are possible causes for this alarm: The receiver board failed. The dc power to the receiver board is lost.
68P02901W26-Q 24 May 2004
17-189
Procedure
Use the following procedure to resolve the alarm. Procedure 17-93 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Receiver Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace the transceiver unit.
17-190
68P02901W26-Q 24 May 2004
144. DRI: Transceiver to DRI Communication Failure

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 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 the third occurrence. 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.

The contents of the additional information field in the output for this alarm are shown in Table 17-22. Table 17-22 Additional information field contents Byte first second Value (hex) 00 to FF 00 to FF Definition The transceiver unit fault group. The fault code reported by the transceiver unit. Refer to the table under Possible Cause(s).
68P02901W26-Q 24 May 2004
17-191
Possible cause(s)
The following are possible causes for this alarm: Fault Code Value (hex) 0 One of the following: 1 The PLL synthesizer failed. The 13 MHz synthesizer lost DC power. The fibre optic downlink path from the DRI is faulty. The input frequency reference to the 13 MHz PLL synthesizer was lost. Definition
One of the following: The PLL synthesizer failed. The 13 MHz synthesizer lost DC power. The fibre 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.
Procedure
Procedure 17-94 Transceiver to DRI Communication Failure Use the following procedure to resolve the alarm.
17-192
68P02901W26-Q 24 May 2004
Procedure 17-94
Transceiver to DRI Communication Failure (Continued)
68P02901W26-Q 24 May 2004
17-193

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 programmers. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The GSM timing chain failed. The timing failed. A momentary loss of synchronization occurred due to a noise burst in the communications link.
17-194
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-195

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 cause(s)
The following are possible causes for this alarm: Faulty data link. Data link noise. Intermittent data link failure. Faulty fibre optic interface circuit. Faulty data recovery circuit.
17-196
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-197

Description
The HDLC transmit FIFO to fibre links consistently underflows.
System action

Possible cause(s)
The following are possible causes for this alarm: Faulty transceiver timing chain. Faulty communications interface between the HDLC link and control processor. Faulty control circuits.
17-198
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-199

Description
The HDLC receive FIFO (First-In, First-Out) to fibre links consistently overflows.
System action

Possible cause(s)
The following are possible causes for this alarm: Faulty transceiver timing chain. Faulty communications interface between the HDLC link and control processor. Faulty control circuits.
17-200
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-201
150. DRI: Receive Matrix Branch 1 Control Link Failure

Description
The receive matrix control link failed.

Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 17-99 Receive Matrix Branch 1 Control Link Failure
17-202
68P02901W26-Q 24 May 2004
Procedure 17-99
Receive Matrix Branch 1 Control Link Failure (Continued)
68P02901W26-Q 24 May 2004
17-203
151. DRI: Transceiver to Combiner Communication Failure

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 cause(s)
The following are possible causes for this alarm: 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.
17-204
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-100 Transceiver to Combiner Communication Failure Determine the state of both combiners.
If... if both combiners are busy-unlocked... both combiners are disabled-unlocked or disabled-locked... one combiner is busy-unlocked and the other combiner is enabled-unlocked...
Then... No further action is required. If this alarm recurs, it indicates an intermittent fault. Send a field representative to the site to replace the combiners. Send a field representative to the site to check the combiner links. Before this, make an attempt to swap the redundant combiner.
68P02901W26-Q 24 May 2004
17-205
152. DRI: Control Processor to Power Amplifier Communication Failure

Description
The communications link between the Control Equalizer Board (CEB) and the power amplifier failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
17-206
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-101 Control Processor to Power Amplifier Communication Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-207
153. DRI: Control Processor to Equalizer Communication Failure

Description
The communications link between the Control Equalizer Board (CEB) host processor and the Equalizer Board (EQB) failed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
17-208
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-102 Control Processor to Equalizer Communication Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-209
154. DRI: Power Supply Failure

Description
A transceiver power supply failed.
System action
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 the third occurrence. 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.

17-210
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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
Procedure 17-103 Power Supply Failure Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
17-211

Description
An excessive number of byte count errors were detected.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
17-212
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-104 Transceiver to DRI Communication Error Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-213
156. DRI: Control Processor Message Queue Overflowed

Description
The Control Equalizer Board (CEB) message queue overflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: 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.
17-214
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-105 Control Processor Message Queue Overflowed Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-215
157. DRI: Receiver Input Overflowed

Description
The receiver I-Channel First-In, First-Out (FIFO) consistently overflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: Control circuits failed. Timing circuits failed.
17-216
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-106 Receiver Input Overflowed Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-217

Description
The receiver Q-Channel First-In, First-Out (FIFO) consistently overflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: Control circuits failed. Timing circuits failed.
17-218
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-107 Receiver Input Overflowed Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-219
159. DRI: Equalizer Output Overflowed

Description
The equalizer output data consistently overflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: CEB watchdog timer expired. Control circuit failure. Timing circuit failure.
17-220
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-108 Equalizer Output Overflowed Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-221

Description
The equalizer output control First-In, First-Out consistently overflowed.
System action

Possible cause(s)
The following are possible causes for this alarm: CEB watchdog timer expired. Control circuit failure. Timing circuit failure.
17-222
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-109 Equalizer Output Overflowed Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-223
161. DRI: Transmitter Out of Synchronization

Description
The modulator interface lost synchronization with the transceiver unit timing chain.
System action

Possible cause(s)
The following are possible causes for this alarm: Faulty CEB timing chain. Noise on the fibre link. 5-volt supply voltage low switched. Failure of 13 Mhz clock from slave PLL. Failure of the recovered clock on the fibre link to the transceiver unit. Timing circuit failure.
17-224
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-110 Transmitter Out of Synchronization Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-225

Description
The receive matrix branch 2 control link failed.

Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 17-111 Receive Matrix Branch 2 Control Link Failure
17-226
68P02901W26-Q 24 May 2004
Procedure 17-111
Receive Matrix Branch 2 Control Link Failure (Continued)
68P02901W26-Q 24 May 2004
17-227

Description
HDLC downlink communications between the higher level devices and the transceiver unit failed.
System action

Possible cause(s)
Communications lost between RSS and DRI.
Procedure
17-228
68P02901W26-Q 24 May 2004
Procedure 17-112
Transceiver to DRI Communication Failure (Continued)
68P02901W26-Q 24 May 2004
17-229

Description
The Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL) is Out of Lock with the E1/T1 reference clock.
System action

Possible cause(s)
The following are possible causes for this alarm: The PLL lost dc power. The Input reference to the PLL is lost.
17-230
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-231

Description
The output power of the 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 cause(s)
The following are possible causes for this alarm: The 40.96 MHz PLL lost dc power. DPC PLL synthesizer components failed.
17-232
68P02901W26-Q 24 May 2004
Procedure
68P02901W26-Q 24 May 2004
17-233
166. DRI: Control Processor Firmware Failure

Description
The control processor in the MCU experienced an unrecoverable software error.
System action

Possible cause(s)
The following are possible causes for this alarm: An internal exception generated by a DSP. An internal hardware or software exception generated on an M-Cellmicro.
17-234
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-115 Control Processor Firmware Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-235
167. DRI: Control Processor Configuration Mismatch

Description
The control processor in the MCU is in an improper operational state.
This alarm is generated only for an M-Cellmicro, MCellmacro, Horizonmicro, Horizonmicro2, and Horizoncompact2 sites.
System action

Possible cause(s)
The following are possible causes for this alarm: A corrupted BSS (or specific BTS) software load. A momentary fault experienced by the BSS software/firmware.
17-236
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-116 Control Processor Configuration Mismatch Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-237
168. DRI: Equalizer Configuration Mismatch

Description
One of the MCU equalizer processors is in an improper operational state.
System action

Possible cause(s)
The BSS (or specific BTS) software download failed.
Procedure
Procedure 17-117 Equalizer Configuration Mismatch Use the following procedure to resolve the alarm.
17-238
68P02901W26-Q 24 May 2004
Procedure 17-117
Equalizer Configuration Mismatch (Continued)
68P02901W26-Q 24 May 2004
17-239

Description
The Phase Lock Loop (PLL) synthesizer for the GSM timing chain is Out of Lock. Or, the output power from the13 MHz Phase Lock Loop (PLL) synthesizer for the GSM timing chain is out of limits.
System action

17-240
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The 13 MHz synthesizer lost dc power. PLL synthesizer components failed. A faulty fibre optic downlink path from the DRI. GSM timing chain failure. The input frequency reference to the 13 MHz synthesizer failed.
Procedure
68P02901W26-Q 24 May 2004
17-241
170. DRI: M-Cell Micro Interconnect Failure

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-Cellmicro, MCellmacro, Horizonmicro, Horizonmicro2, and Horizoncompact2 sites.
System action

Possible cause(s)
The following are possible causes for this alarm: Unequipped second DRI. Faulty EEPROM on the control processor. Faulty PDB. Faulty TRX hardware.
17-242
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-119 M-Cell Micro Interconnect Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-243
171. DRI: Invalid Calibration Data

Description
The calibration data cannot be used because it has been corrupted.
This alarm is generated only for M-Cellmicro, M-Cellmacro, Horizonmicro, Horizonmicro2, and Horizoncompact2, Horizonmacro, and Horizon II macro sites.
System action

17-244
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: Corrupted receive, transmit, or cabinet calibration data. Calibration data corrupted by OMC operator.
Procedure
Procedure 17-120 Invalid Calibration Data Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-245
176. DRI: Equalizer Timeslot (0-7) Failure

Description
A watchdog timer for an equalizer DSP (0-7) has expired.
System action
The affected DRI is soft reset when this alarm occurs.

Two bytes are displayed in the additional information field containing internal software codes that are only useful to programmers. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: Equalizer DSP hardware is faulty. CEB hardware is faulty. The equalizer DSP software is faulty.
17-246
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-121 Equalizer Timeslot (0-7) Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-247
184. DRI: Equalizer Firmware Failure

Description
The equalizer processor experienced an unrecoverable firmware error.
System action

Possible cause(s)
The following are possible causes for this alarm: The Digital Signalling 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.
17-248
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-122 Equalizer Firmware Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-249

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.

The contents of the additional information field are shown in Table 17-23. Table 17-23 Additional information field contents Byte first Value 00 to 07 Definition 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.
17-250
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The TDM timeslot path connections is not correctly configured at the MCU. The Equalizer Control Processor is faulty.
Procedure
Procedure 17-123 Baseband Hopping TDM Link Error Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-251

Description
The transceiver is unable to perform baseband hopping because the timeslot provided in the baseband hopping data misaligns 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. Any additional bytes displayed should be ignored.
If this alarm was raised on a CTU2 radio type, the additional data format is: Byte1: BBH error Byte2: invalid parameter
17-252
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The TDM timeslot path connections are not properly configured at the MCU. TDM hardware is faulty.
Procedure
Procedure 17-124 Baseband Hopping GSM Timeslot Misalignment 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.
68P02901W26-Q 24 May 2004
17-253
203. DRI: RF Unit Power Supply Unit - Input Failure
203. DRI: RF Unit Power Supply Unit - Input Failure

Description
Main Power Supply to RF Unit has been lost and the RF Unit is operating on the backup power supply.

Fault code.
Possible cause(s)
The following are possible causes for this alarm: Failure of the main AC supply into external AC/DC converter. Failure of supply fuse/opening of protective device. Failure of +25V DC feed into the RF Unit. Connector/ lead from the external AC/DC converter broken or removed from RF Unit input.
Procedure
Procedure 17-125 RF Unit Power Supply Unit - Input Failure
Investigate the loss of the main supply input.
17-254
68P02901W26-Q 24 May 2004
204. DRI: RF Unit Over Temperature
204. DRI: RF Unit Over Temperature

Description
AC/DC converter within the RF Head Unit has detected an Over Temperature" condition.

Fault code.
Possible cause(s)
The following are possible causes for this alarm: Failure of the building air conditioning system and subsequent increase of units ambient temperature (i.e greater than 45 degree centigrade) Incorrect positioning of RF Unit above/too close to external heat source. Blockage of air vent holes around RF Unit.
Procedure
Procedure 17-126 RF Unit Over Temperature
Investigate the cause of the over temperature condition and then INS the DRI.
68P02901W26-Q 24 May 2004
17-255
205. DRI: RF Unit Low Voltage Disconnect Imminent
205. DRI: RF Unit Low Voltage Disconnect Imminent

Description
Battery back-up voltage is nearing the point of initiating a disconnect of the load, i.e the RF Unit.

Fault code.
Possible cause(s)
The following are possible causes for this alarm: Failure of the main AC supply into external AC/DC converter. Failure of supply fuse/opening of protective device. Failure of +25V DC feed into the RF Unit. Connector/ lead from the external AC/DC converter broken or removed from RF Unit input.
Procedure
Procedure 17-127 RF Unit Low Voltage Disconnect Imminent
Investigate the cause of the loss of the +25V DC supply and after the power is restored INS the DRI.
17-256
68P02901W26-Q 24 May 2004
206. DRI: RF Unit External Alarm Input
206. DRI: RF Unit External Alarm Input

Clearing Type: Severity Level: Category: FMIC Investigate Environmental
Description
External Input has a short circuit" across its inputs.

Fault code.
Possible cause(s)
Input Circuit Failure.
Procedure
Procedure 17-128 RF Unit External Alarm Input
Investigate and clear the cause of the Input Short Circuit.
68P02901W26-Q 24 May 2004
17-257
207. DRI: Internal Communication Error
207. DRI: Internal Communication Error

Description
The CTU2s cascaded integral combiner (CIC) has lost synch with the direct digital synthesiser (DDS).

Fault code.
Possible cause(s)
Miscommunication between CIC and DDS.
Procedure
Procedure 17-129 Internal Communication Error
Monitor the DRI. If the BSS takes the DRI OOS, reset the DRI (reset_device) and monitor again. If the BSS takes the DRI OOS because of the same alarm then replace the DRI.
17-258
68P02901W26-Q 24 May 2004
208. DRI: Power Amplifier Temperature
208. DRI: Power Amplifier Temperature

Description
The temperature of the power amplifier has exceeded its acceptable operating temperature range.

Possible cause(s)
The following are possible causes for this alarm: 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.
Procedure
Procedure 17-130 Power Amplifier Temperature
68P02901W26-Q 24 May 2004
17-259
210. DRI: Hopping DRI Failure

Clearing Type: Severity Level: Category: Intermittent Investigate Equipment
Description
The DRI failed a baseband hopping attempt.

Possible cause(s)
The following are possible causes for this alarm: The DRI is OOS. The DRI is a hopping DRI.
17-260
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-131 If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Hopping DRI Failure Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
68P02901W26-Q 24 May 2004
17-261
211. DRI: Front End Processor Failure

Description
This alarm indicates that a DRI Front End Processor (FEP) failed.

Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The DRI software is faulty.
17-262
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-132 Front End Processor Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-263
212. DRI: Channel Coder Failure

Description
The DRI Channel Coding Digital Signal Processor (CCDSP) failed.

Possible cause(s)
The transceiver unit is faulty.
Procedure
Procedure 17-133 Channel Coder Failure Use the following procedure to resolve the alarm.
17-264
68P02901W26-Q 24 May 2004
Procedure 17-133
Channel Coder Failure (Continued)
68P02901W26-Q 24 May 2004
17-265
213. DRI: Transceiver Processor Failure

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

If this alarm is raised on a CTU2 radio type, the additional data format is: - Firmware Source Fault Zone. - Firmware Detector Fault Zone. - Fault code (of original failure). - Additional data bytes 1 to 4. - Timeslot. - Carrier. (This additional data is useful only to firmware engineerings.) For other platforms, the DRI alarm code related to the DRI CCDSP that triggered the device state check in the system displays.
17-266
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The Digital Radio Interface Extender (DRIX) board is faulty.
Procedure
Procedure 17-134 Transceiver Processor Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-267
214. DRI: Equalizer Failure

Description
The DRI Equalizer Digitized Signal Processor (EQDSP) failed.

Possible cause(s)
The following are possible causes for this alarm: The transceiver unit is faulty. The DRI software is faulty. The Radio SubSystem (RSS) software is faulty. The transceiver unit software is faulty.
17-268
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-135 Equalizer Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-269
215. DRI: Power Amplifier Failure

Description
The transceiver unit power amplifier failed.

A one-byte error code is displayed in the additional information field containing internal software codes that are useful only to programmers.
Possible cause(s)
The following are possible causes for this alarm: The power amplifier is faulty. The FM software is faulty. The DRI software is faulty. The Radio SubSystem (RSS) software is faulty. The transceiver unit software may is faulty.
17-270
68P02901W26-Q 24 May 2004
Procedure
Procedure 17-136 Power Amplifier Failure Use the following procedure to resolve the alarm.
68P02901W26-Q 24 May 2004
17-271
216. DRI: Transceiver Recovery Failure
216. DRI: Transceiver Recovery Failure

Description
The transceiver unit has failed.

A one-byte error code is displayed in the additional information field containing internal software codes that are useful only to programmers.
Possible cause(s)
The transceiver unit is faulty.
Procedure
Use the following procedure to resolve the alarm. If... the BSS takes the DRI OOS (DRI goes disabled-unlocked)... the DRI fails to go busy-unlocked after return to service... OR the BSS takes the DRI OOS again as a result of the same alarm after the DRI becomes busy-unlocked... Then... Return the DRI to service (INS), and monitor the DRI. Send a field representative to the site to replace one of the following: DRIM board for an InCell BTS Transceiver unit for a non-InCell BTS.
17-272
68P02901W26-Q 24 May 2004
217. DRI: Transmission Suspended to Conserve Battery Power
217. DRI: Transmission Suspended to Conserve Battery Power

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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The Main Power alarm sensor state changed since the last time the EAS was polled by the FM software. An user-defined environmental alarm is activated.
Procedure
Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Once the main power supply is running, the DRIs should return to service. If not, INS the DRI.
68P02901W26-Q 24 May 2004
17-273
218. DRI: Invalid Transceiver Calibration Data
218. DRI: Invalid Transceiver Calibration Data

Description
The antennas that are currently being used at a site cannot access any form of calibration data.

Possible cause(s)
The following are possible causes for this alarm: A transceiver unit was installed at a site without being calibrated. An uncalibrated transceiver unit was replaced. The calibration data was cleared. A transceiver unit was unlocked before being calibrated.
Procedure
Send a field representative to the site to calibrate the transceiver unit. This problem cannot be resolved from the OMC-R.
17-274
68P02901W26-Q 24 May 2004
219. DRI: GPRS Not Supported by Radio
219. DRI: GPRS Not Supported by Radio

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 cause(s)
The following are possible causes for this alarm: The transceiver unit is not able to support GPRS technology. The transceiver unit is faulty. The transceiver unit software or firmware may be faulty.
Procedure
Procedure 17-137 1 2 GPRS Not Supported by Radio
Replace the radio which can not support GPRS, with a version that can support GPRS. Assign the GPRS function to the a radio that can support GPRS.
68P02901W26-Q 24 May 2004
17-275
221. DRI: Invalid in-call modification of destination channel type
221. DRI: Invalid in-call modification of destination channel type

Clearing Type: Severity Level: Category: FMIC Warning (5) Processing
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.

2 bytes: First byte represents the CCDSP number reporting the mismatch, 2nd byte indicates the requested destination channel type.
Possible cause(s)
The following are possible causes for this alarm: Either the channel coder has received an invalid request or its internal channel type data stores have been corrupted.
Procedure
Procedure 17-138 Invalid in-call modification of destination channel type
Use the following procedure to resolve the alarm. Monitor the DRI. The BSS will reset the DRI if these alarms continue at an unacceptable rate. If the BSS takes the DRI OOS, then INS the DRI and monitor again. If the BSS takes the DRI OOS because of the same alarm then replace the DRI.
17-276
68P02901W26-Q 24 May 2004
224. DRI: Safe Test Audit Failure

Description
The DRI failed a safe test audit. 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 alarm translation procedure. DRI transitions are tagged to the initial alarm.

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. Table 17-24 Additional information field contents Second byte 00 CCDSP number 00 EQDSPnumber 00 00 Definition Front End Processor (FEP) failure. Channel Coding Digital Signal Processor (CCDSP) failure. Control Equalizer Board (CEB) failure. Equalizer Control Processor (EQDSP) failure. Power Amplifier (PA) failure. CTU2 processor failure
First byte 00 01 02 03 04 06
68P02901W26-Q 24 May 2004
17-277
Possible cause(s)
The following are possible causes for this alarm: 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-139 Safe Test Audit Failure Use the following procedure to resolve the alarm.
17-278
68P02901W26-Q 24 May 2004
231. DRI: TDM Interface Configuration Failure

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 cause(s)
The following are possible causes for this alarm: During a TDM swap, the DRI cannot be placed on the correct TDM. The MCAP bus is malfunctioning. The GPROC is malfunctioning.
68P02901W26-Q 24 May 2004
17-279
Procedure
Procedure 17-140 TDM Interface Configuration Failure Use the following procedure to resolve the alarm.
17-280
68P02901W26-Q 24 May 2004
234. DRI: Active Link Connection Failure

Description
One or more of the following active link connections between the transceiver unit and the BTP failed. A FOX-to-TCU connection (fibre link). An FMUX-to-remote FMUX connection (fibre link). A BTP-to-FOX connection (backplane). A BTP-to-FMUX connection (backplane). An MCUF (BTP)-to-remote XMUX connection (fibre link). FMUX-to-XMUX connection (fibre link).
This alarm is generated for M-Cell2, M-Cell6, M-Cellmicro , Horizonmacro, Horizon II macro extension equipment. 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 alarm translation procedure. DRI transitions are tagged to the initial alarm.

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.
68P02901W26-Q 24 May 2004
17-281
Table 17-25
Additional Information field contents Bytes five to eight 00 00 00 01 00 00 00 02 00 00 00 03 Description HDLC connect confirm. HDLC connect indication. HDLC disconnect indication. Loss of data on TCU link. Loss of synchronisation to TCU link. Uncorrected delay compensation. BBH routing data parity error.
Bytes one to four 00 00 00 01
00 00 00 02
00 00 01 00 00 00 02 00 00 00 04 00 00 00 08 00
Possible cause(s)
The following are possible causes for this alarm: The transceiver unit failed. 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 Fibre Optic Extender (FOX) board failed. This alarm does not occur if the entire FOX board has failed. A port on the active Fibre 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. The communication fibre link failed. A backplane connection failed.
Procedure
Determine the state of the DRI. If the DRI is... busy-unlocked... Then... The fault condition no longer exists. No further action is required.
17-282
68P02901W26-Q 24 May 2004
Procedure 17-141 2 3
Active Link Connection Failure (Continued) Go to step 2.
not busy-unlocked... Reset the DRI.
Determine the state of the DRI after the reset is completed. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit, or take corrective action for the failures listed in Possible cause(s).
68P02901W26-Q 24 May 2004
17-283
235. DRI: Standby Link Connection Failure

Description
One or more of the following standby link connections between the transceiver unit and the BTP failed. A FOX-to-TCU connection (fibre link). An FMUX-to-remote FMUX connection (fibre link). An MCU-to-FOX connection (backplane). An MCU-to-FMUX connection (backplane). {An MCUF (BTP)-to-remote XMUX connection (fibre link). FMUX-to-XMUX connection (fibre link). A BTP-to-XMUX connection (backplane).
This alarm is generated for M-Cell2, M-Cell6, M-Cellmicro , Horizonmacro, Horizon II macro extension equipment.

There is no additional information field in the output for this alarm.
17-284
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The transceiver unit failed. 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 Fibre Optic Extender (FOX) board failed. This alarm does not occur if the entire FOX board has failed. A port on the active Fibre Optic Multiplexer (FMUX) board failed. This alarm does not occur if the entire FMUX board has failed. The communication fibre link failed. A backplane connection failed.
Procedure
Procedure 17-142 Standby Link Connection Failure
Check all the connections as listed in the Description, and ensure that they are in proper order.
68P02901W26-Q 24 May 2004
17-285
236. DRI: Slow Flash Failure

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-Cellmicro, MCellmacro, Horizonmacro, Horizonmicro, Horizonmicro2, Horizoncompact and Horizoncompact2 sites.

Possible cause(s)
The flash EEPROM on the transceiver unit is faulty.
Procedure
Procedure 17-143 1 Determine the state of the DRI. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
17-286
68P02901W26-Q 24 May 2004
Procedure 17-143 2 3
(Continued)
Reset the DRI. Determine the state of the DRI after the reset is completed. If the DRI is... busy-unlocked... and the alarm has not cleared not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit.
68P02901W26-Q 24 May 2004
17-287
237. DRI: Non-Volatile Memory Failure

Description
A failure to read or write to the Non-Volatile (NV) flash EEPROM was detected for the transceiver unit.

Possible cause(s)
The NV flash EEPROM on the transceiver unit is faulty.
Procedure
Procedure 17-144 Non-Volatile Memory Failure Use the following procedure to resolve the alarm.
17-288
68P02901W26-Q 24 May 2004
Procedure 17-144
Non-Volatile Memory Failure (Continued)
68P02901W26-Q 24 May 2004
17-289
239. DRI: Process Safe Test Audit Failure

Description
The DRI failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

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. Table 17-26 Additional information field contents Byte one two, three four five - eight Value Definition Process id of the process being audited CPU number. Percentage of CPU utilization by the process being audited. Useful only to programmers.
17-290
68P02901W26-Q 24 May 2004
Table 17-26
Additional information field contents (Continued) Byte nine Value 00 01 02 Definition The process that failed the audit is in an infinite loop. The cause for the failure was not determined. Higher priority processes prevented the process that failed to run. The cause for the failure was not determined.
03
Possible cause(s)
A process executing on the DRI failed to respond to the System Audit Process.
Procedure
Perform the safe test audit on the DRI If the DRI... passes the audit... fails the audit...
3 4
Reset the DRI. Determine the state of the DRI after the reset is completed. If DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit.
68P02901W26-Q 24 May 2004
17-291
241. DRI: Standby Link Connected to Wrong Device

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, Horizonmacro, 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 (fibre link). A standby FMUX-to-XMUX connection (fibre link). A standby BTP-to-XMUX connection (backplane).

17-292
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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-146 1 Standby Link Connected to Wrong Device
Determine whether more than two separate DRI devices in a cabinet at a site are generating this alarm. If the number of DRIs generating this alarm is... three or more DRIs in a single cage Then... This fault is probably occurring in a standby FMUX-to-standby FMUX connection between two cabinets. Go to step 2. 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.
one or two DRIs in a single cage
Send a field representative to the site to check/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. Consult site specification documents to verify that the active as well as the standby cage connections are correct.
68P02901W26-Q 24 May 2004
17-293
243. DRI: Unlocked Device Not in Service
243. DRI: Unlocked Device Not in Service

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 cause(s)
The system failed to bring the device in service.
Procedure
Procedure 17-147 1 2 3 Unlocked Device Not in Service
Determine the state of the DRI. Reset the DRI. Determine the state of the DRI after the reset is completed. If the DRI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the transceiver unit (possibly DRI board).
17-294
68P02901W26-Q 24 May 2004
254. DRI: Device Failure

Description
The DRI was placed OOS after a fault caused it to report the Reset Due To Recurring Fault (DRI 35).

Possible cause(s)
Board removed from service due to a fault.
Procedure
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. If the alarm is raised on a CTU2 operating in dual carrier mode due to intermittent fault reporting, both carriers are taken OOS. Send a field representative to replace the DRI generating the alarm.
68P02901W26-Q 24 May 2004
17-295
17-296
68P02901W26-Q 24 May 2004
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
Chapter
68P02901W26-Q 24 May 2004
18-1
Introduction to 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 (using 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. The following are some examples of EAS alarm strings: Door open, High humidity, Low humidity, Fire, Intruder, etc.
18-2
68P02901W26-Q 24 May 2004
0. EAS: Unexpected Board Type

Description
A Parallel Interface Extender (PIX) board is not responding properly when polled by 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 cause(s)
The following are possible causes for this alarm: The PIX board is faulty. The slot specified for an PIX board is occupied by a board other than an PIX board.
68P02901W26-Q 24 May 2004
18-3
Procedure
Procedure 18-1 Unexpected Board Type Determine the state of the EAS device.
If the EAS is... busy-unlocked...
Then... The fault condition no longer exists. No further action is required. If this alarm recurs for the same device, the PIX board may have an intermittent fault. Send a field representative to the site to replace the PIX board. Send a field representative to determine the cause of the alarm and take the appropriate action.
18-4
68P02901W26-Q 24 May 2004
1. EAS: Serial Bus Connection Failure

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 EAS alarms.
System action
The system places the EAS device OOS.

Possible cause(s)
The following are possible causes for this alarm: The PIX board was improperly installed. The PIX board is faulty. The polling processor board is faulty.
68P02901W26-Q 24 May 2004
18-5
Procedure
Procedure 18-2 Serial Bus Connection Failure Attempt to restore the EAS board to service.
If the EAS board... returns to service...
Then... The fault condition no longer exists. No further action is 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. Send a field representative to determine the cause of the alarm and take the appropriate action.
18-6
68P02901W26-Q 24 May 2004
8. EAS: EAS has detected Main Power Failure

Clearing Type: Severity Level: Category: FMIC Major Environmental
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 on-line to the user-specified value of the carriers_ins_pwr_fail database parameter.
For a description of the carriers_ins_pwr_fail database parameter, see the Technical Description: BSS Command Reference (68P02901W23).

Possible cause(s)
The following are possible causes for this alarm: The main ac power source failed. The Main Power Failure environmental sensor failed.
68P02901W26-Q 24 May 2004
18-7
Procedure
Procedure 18-3 EAS has detected Main Power Failure Determine if there is a power failure.
If there is... a power failure...
Then... 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. Send a field representative to determine the cause of the alarm and take the appropriate action.
is not a power failure...
18-8
68P02901W26-Q 24 May 2004
16.-31. EAS: Optocoupler 1-16

Clearing Type: Severity Level: Category: FMIC Dependent upon the parameter monitored and the alarm threshold configured. Environmental
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, see the Technical Description: BSS Command Reference (68P02901W23).
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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
18-9
Procedure
Procedure 18-4 Optocoupler 1-16
Follow the procedures established for the resolution of the environmental condition indicated by the alarm.
18-10
68P02901W26-Q 24 May 2004
19
GBL alarms
This chapter details GBL alarms and includes the following alarm procedures: "0. GBL: Link Disconnected" on page 19-3
Chapter
68P02901W26-Q 24 May 2004
19-1
Introduction to GBL alarms
Introduction to GBL alarms
GBL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Packet Control Unit (PCU) Gb link (GBL) interface between the BSS and the Serving GPRS Support Node (SGSN).
19-2
68P02901W26-Q 24 May 2004
0. GBL: Link Disconnected

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 re-connect the link.
Last GBL link disconnected

In the event this alarm is generated for a GBL that 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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: 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 (E1 links, satellite links, microwave links, trunking equipment, etc) is faulty.
68P02901W26-Q 24 May 2004
19-3
Procedure
Procedure 19-1 Link Disconnected Attempt to return the GBL to service.
If the GBL... returns to service...
Then... No further action is required. If this alarm recurs, it indicates an intermittent link fault at the site. Send a field representative to the site to troubleshoot the link fault. Send a field representative to the site to troubleshoot the link fault.
19-4
68P02901W26-Q 24 May 2004
20
GCLK alarms
This chapter details GCLK alarms and includes the following alarm procedures: "0. GCLK: Reference Distribution Module Failure" on page 20-3 "2. GCLK: Clock Reference Failure" on page 20-5 "4. GCLK: Phase Lock Lost" on page 20-8 "5. GCLK: 125s Reference Count Overflow" on page 20-11 "6. GCLK: 60ms Reference Count Overflow" on page 20-13 "7. GCLK: 6.12s Reference Count Overflow" on page 20-15 "8. GCLK: Frequency Difference in Mate GCLK" on page 20-17 "9. GCLK: Hard Reset" on page 20-20 "11. GCLK: Long-Term-Average Values are Unstable" on page 20-22 "12. GCLK: Unrecognized Hardware Revision Level" on page 20-24 "14. GCLK: Phase Lock Failure" on page 20-25 "15. GCLK: Watchdog Timer Expired" on page 20-28 "16. GCLK: Clock Output Failure" on page 20-30 "17. GCLK: SYNC Shutdown Request" on page 20-32 "18. GCLK: Not Operational" on page 20-34 "19. GCLK: Warmup Failure" on page 20-36 "20. GCLK: Invalid Mode" on page 20-38 "21. GCLK: Calibration In Progress" on page 20-40 "22. GCLK: Calibration via Firmware Initiated" on page 20-41 "24. GCLK: Bad Clock Source or OCXO (oscillator) Replacement Required" on page 20-42 "26. GCLK: GCLK Calibration Request" on page 20-45 "232. GCLK: Processor Bus Communication Failure" on page 20-48
Chapter
68P02901W26-Q 24 May 2004
20-1
Introduction to 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 20-1. Table 20-1 GCLK FRUs FRU GCLK MCU MCUF MCUm ARENAm (MCU) Description Generic Clock board GCLK SYNC portion of an M-Cell Main Control Unit GCLK SYNC portion of an M-Cellmicro Main Control Unit GCLK SYNC portion of an M-Cellmicro Main Control Unit GCLK SYNC portion of an Horizonmicro (M-Cellarena) Main Control Unit GCLK SYNC portion of an Horizoncompact (M-Cellarena Macro) Main Control Unit
ARENA MAC (MCU)
Throughout this chapter, frequent reference is made to InCell and non-InCell (M-Cell) BTSs. Understand InCell BTS to mean a BTS4, BTS5, BTS6, ExCell, or TopCell. A non-InCell BTS refers to any other BTS than those defined by the term InCell BTS.
20-2
68P02901W26-Q 24 May 2004
0. GCLK: Reference Distribution Module Failure

Description
The Oven Controlled Crystal Oscillator (OCXO) on the GCLK board failed.
System action
The GCLK is placed OOS.
An MCAP interrupt is generated if interrupt is enabled. A master/redundant changeover occurs if no faults exist on the redundant GCLK.

The additional information field displays MCAP register values that are useful only to programmers.
Possible cause(s)
The following are possible causes for this alarm: The GCLK Reference Distribution Module (RDM) failed. The RDM failure detection circuitry malfunctioned.
68P02901W26-Q 24 May 2004
20-3
Procedure
Procedure 20-1 Reference Distribution Module Failure Determine the current operational and administrative states of the GCLK.
If the GCLK is... busy-unlocked... enabled-unlocked... disabled-unlocked...
Then... The fault condition no longer exists. Further fault isolation is not required. The alarm condition no longer exists. Further fault isolation is not required. Send a field representative to the site to replace the faulty GCLK.
20-4
68P02901W26-Q 24 May 2004
2. GCLK: Clock Reference Failure

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 the identifiers for the MMS device used for reference clock signal extraction, as shown in Table 20-2. Table 20-2 Additional information fields contents Byte first FF or 10 Value Definition The numeric representation of the MMS device that is equipped on an MSI board. device ID 1 - Identifies the MSI where the MMS is equipped. device ID 2 - Identifies the specific MMS on the MSI board. device ID 3 - Serves as a placeholder.
The MMS device identifiers are displayed in the next three bytes in the following order. second third fourth 00 to 32 or FF 0, 1, or FF 0 or FF
68P02901W26-Q 24 May 2004
20-5
Possible cause(s)
The following are possible causes for this alarm: E1/T1 link lines are faulty. No clock is being sent from an MSI/NIU. No clock is being sent from an XCDR. A GCLK reference clock detection circuit failed.
Procedure
Procedure 20-2 Clock Reference Failure 1 Determine if this is a recurrence of this alarm. If is... a recurrence... not a recurrence... 2 If an alternate MMS is... available... not available... 3 If the alarm... did not clear... cleared... Then... Send a field representative to the site to investigate the E1/T1 links. Go to step 2. Then... Go to step 3. Go to step 4. Then... Go to step 4. Send a field representative to the site to investigate the E1/T1 links and/or replace the faulty MSI board.
Determine if an alternate MMS is available for clock reference extraction.
Select an alternate MMS for clock reference signal extraction.
4 5
Reset the MSI. Determine if the alarm cleared after the MSI reset is complete. If the alarm... cleared... did not clear... Then... The fault condition no longer exists. No further action is required. Replace the MSI. If the alarm is not cleared by this action, go to step 6.
6 7
Reset the GCLK. Determine if the alarm cleared after the GCLK reset is complete.
20-6
68P02901W26-Q 24 May 2004
Procedure 20-2
Clock Reference Failure (Continued) Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GCLK.
If the alarm... cleared... did not clear...
68P02901W26-Q 24 May 2004
20-7
4. GCLK: Phase Lock Lost

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/T1 links. Normally, this alarm does not affect traffic or signalling 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
M-Cell site
The additional information field displays the identifiers for the MMS device used for clock reference signal extraction, as shown in Table 20-3. Table 20-3 Additional information fields contents Byte first FF or 10 Value Definition The numeric representation of the MMS device that is equipped on an MSI board. device ID 1 - Identifies the MSI where the MMS is equipped.
The MMS device identifiers are displayed in the next three bytes in the following order. second 00 to 32 or FF
20-8
68P02901W26-Q 24 May 2004
Table 20-3 third fourth
Additional information fields contents (Continued) Byte 0, 1, or FF 0 or FF Value Definition device ID 2 - Identifies the specific MMS on the MSI board. device ID 3 - Serves as a placeholder.
Possible cause(s)
The following are possible causes for this alarm: Wander/jitter on the E1/T1 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 20-3 1 2 Phase Lock Lost
Determine whether this alarm is intermittent: if so, send a field representative to site to check the link status, prepared to replace a faulty link, GCLK, or MCU. Determine if any two GCLKs report this alarm at the same time. If any two GCLKs... report this alarm... Then... This alarm was generated as the result of a link problem. Send a field representative to the site to resolve the E1/T1 link fault. Go to step 3. Then... This alarm was generated as the result of an MMS fault. Resolve the MMS alarm. If this alarm is not cleared after the MMS alarms are resolved, go to step 4.
do not report this alarm... 3 If there are... MMS alarms...
Determine if any MMS alarms are reported.
68P02901W26-Q 24 May 2004
20-9
Procedure 20-3 4
Phase Lock Lost (Continued) Go to step 4. Then... Troubleshoot the uplink site. Go to step 5. Then... There is a E1/T1 link fault. Send a field representative to the site to resolve the E1/T1 link fault. Go to step 6. Go to step 6. Then... Go to step 7. Go to step 8. Then... There is a E1/T1 link fault. Send a field representative to the site to resolve the E1/T1 link fault. Send a field representative to the site to calibrate the GCLK. If this alarms recurs after the GCLK is recalibrated, replace the GCLK. Then... 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 field representative to the site to resolve the E1/T1 link fault. Go to step 9.
no MMS alarms... If the uplink BTS... lost phase lock... did not lose phase lock... 5 If the site is... part of a star configuration where other sites in the star occasionally lose phase lock... part of a star configuration, but no other sites lost phase lock... not part of a star configuration... 6 If the site is... an InCell site... an MCU-based site... 7 If both GCLKs... are reporting the same alarm...
Determine if the uplink BTS lost phase lock.
Is the site reporting the alarm part of a star configuration?
Determine what type of site is reporting the alarm.
Determine if both GCLKs are reporting the same alarm.
are not reporting the same alarm...
Determine if there is a redundant MCU available. If a redundant MCU is.. available...
not available... 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/T1 link fault. If the alarm does not clear after resolving the link fault, replace the MCU.
20-10
68P02901W26-Q 24 May 2004
5. GCLK: 125s Reference Count Overflow
5. GCLK: 125s Reference Count Overflow

Description
The counter has been pre-loaded 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 seven seconds, the GCLK is placed OOS.

Possible cause(s)
The following are possible causes for this alarm: A GCLK swap. A GCLK hardware fault.
68P02901W26-Q 24 May 2004
20-11
5. GCLK: 125 s Reference Count Overflow
Procedure
Procedure 20-4 1 125s Reference Count Overflow
Determine if this is a recurrence of this alarm. If is... a recurrence... not a recurrence... Then... Send a field representative to the site to replace the faulty GCLK board. Go to step 2. Then... The alarm condition no longer exists. Further fault isolation is not required. The alarm condition no longer exists. Further fault isolation is not required. Send a field representative to the site to replace the faulty GCLK.
Determine the current operational and administrative states of the GCLK. If the GCLK is... busy-unlocked... enabled-unlocked... disabled-unlocked...
20-12
68P02901W26-Q 24 May 2004
6. GCLK: 60ms Reference Count Overflow

Description
The counter has been pre-loaded 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

Possible cause(s)
68P02901W26-Q 24 May 2004
20-13
Procedure
Procedure 20-5 1 60ms Reference Count Overflow
20-14
68P02901W26-Q 24 May 2004
7. GCLK: 6.12s Reference Count Overflow

Description
The counter pre-loaded with an illegally low value during synchronization, causing a delay of more than 6.12 seconds between consecutive 6.12 second reference pulses. This may cause 6.12 second reference failure reports on the other digital boards.
System action

Possible cause(s)
68P02901W26-Q 24 May 2004
20-15
Procedure
Procedure 20-6 1 6.12s Reference Count Overflow
20-16
68P02901W26-Q 24 May 2004
8. GCLK: Frequency Difference in Mate GCLK

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 cause(s)
One or both of the GCLKs may require recalibration.
68P02901W26-Q 24 May 2004
20-17
Procedure
Procedure 20-7 1 Frequency Difference in Mate GCLK
Determine if the Long-Term-Average Values are Unstable (GCLK 11) alarm was reported for either GCLK. If GCLK 11 alarm... was reported... Then... If there is a GCLK 4 alarm, a link problem exists. Send a field representative to the site to resolve the link problem. If this alarm recurs after the link problem is resolved, go to step 2. Go to step 2.
was not reported...
If GCLK 11 is reported, GCLK 4 ought also to be reported: both GCLKs mirror each other in normal working. When this is not so, the reason for the difference in behaviour needs investigation. 2 Determine if the Phase Lock Lost (GCLK 4) alarm was reported for either GCLK. If the GCLK 4 alarm... was reported... Then... Resolve the GCLK 4 alarm. If this alarm does not clear after the GCLK 4 alarm is resolved, go to step 3. Go to step 3.
was not reported... 3 4 Reset both GCLKs. Determine if the alarm is cleared. If the alarm is... cleared ... not cleared... 5 If the GCLK is... phase locked...
Then... The fault condition no longer exists. Further fault isolation is not required. Go to step 5. Then... Got to step 6.
Determine if the GCLK reporting the alarm is phased locked.
20-18
68P02901W26-Q 24 May 2004
Procedure 20-7
Frequency Difference in Mate GCLK (Continued) Send a field representative to the site to recalibrate the GCLK. If this alarm recurs after the GCLK is recalibrated, replace the GCLK.
not phase locked...
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-Q 24 May 2004
20-19
9. GCLK: Hard Reset
9. GCLK: Hard Reset

Description
The GCLK device is currently undergoing a hard reset.
System action
The system re-initializes the GCLK.

Possible cause(s)
The following are possible causes for this alarm: The device was reset using the front panel switch. The device was reset by the software.
Procedure
Procedure 20-8 1 GCLK: Hard Reset
Determine if this is a recurrence of this alarm. If this is... a recurrence... not a recurrence... Then... Send a field representative to the site to replace the faulty GCLK board. Go to step 2.
20-20
68P02901W26-Q 24 May 2004
9. GCLK: Hard Reset
Procedure 20-8
GCLK: Hard Reset (Continued)
Wait at least 1 minute after receiving the alarm report before continuing on to the next step. 2 Determine the current operational and administrative states of the GCLK. If the GCLK is... busy-unlocked... enabled-unlocked... disabled-unlocked... 3 4 Reset the GCLK. Determine the current operational and administrative states of the GCLK. If the GCLK is... busy-unlocked... enabled-unlocked... disabled-unlocked... Then... The alarm condition no longer exists. Further fault isolation is not required. The alarm condition no longer exists. Further fault isolation is not required. Send a field representative to the site to replace the GCLK. Then... The alarm condition no longer exists. Further fault isolation is not required. The alarm condition no longer exists. Further fault isolation is not required. Go to step 3.
68P02901W26-Q 24 May 2004
20-21
11. GCLK: Long-Term-Average Values are Unstable

Description
Of the values used to calculated 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 cause(s)
The following are possible causes for this alarm: 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/T1 links.
20-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-9 1 2 Long-Term-Average Values are Unstable
Check for the presence of other alarms that indicate a link fault. Determine if other sites are reporting this alarm. If other sites are... reporting this alarm... are not reporting this alarm... Then... The reference clock signal is faulty. Resolve the reference clock signal fault. Go to step 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.
68P02901W26-Q 24 May 2004
20-23
12. GCLK: Unrecognized Hardware Revision Level
12. GCLK: Unrecognized Hardware Revision Level

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 cause(s)
The revision level of the GCLK hardware is not recognized.
Procedure
Procedure 20-10 Unrecognized Hardware Revision Level
Check the hardware version number (HVN) and then call a Motorola representative.
20-24
68P02901W26-Q 24 May 2004
14. GCLK: Phase Lock Failure

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 time-out timer setting. The relevant settings are shown in Table 20-4. Table 20-4 GCLK timer settings Confirmation timer setting 10 minutes 2 minutes Time-out timer setting 6 hours 1 hour
GCLK hardware revision level 1-3 5-9
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.
68P02901W26-Q 24 May 2004
20-25
M-Cell
The contents of the additional information field for an M-Cell site are shown in Table 20-5. Table 20-5 Additional information field contents Byte first FF or 10 Value Definition The numeric representation of the MMS device that is equipped on an MSI board. device ID 1 - Identifies the MSI where the MMS is equipped. device ID 2 - Identifies the specific MMS on the MSI board. device ID 3 - Serves as a placeholder.
The MMS device identifiers are displayed in the next three bytes in the following order. second third fourth 00 to 32 or FF 0, 1, or FF 0 or FF
Any additional bytes displayed in this field should be ignored.
Possible cause(s)
The following are possible causes for this alarm: GCLK hardware failure. Clock reference source problem. E1/T1 link outside specification. GCLK calibration required.
Procedure
Procedure 20-11 1 Phase Lock Failure
Determine if other sites are reporting this alarm. If other sites are... reporting this alarm... Then... the reference clock signal or the associated E1/T1 link is faulty. Resolve the reference clock signal or link fault. For link troubleshooting procedures, refer to Maintenance Information: BSS Field Troubleshooting (68P02901W51).
20-26
68P02901W26-Q 24 May 2004
Procedure 20-11
Phase Lock Failure (Continued) go to step 2.
not reporting this alarm... 2 If the BTS... is InCell ... is InCell ... M-Cell...
The GCLK is faulty, or there is an associated link problem. and... there is a redundant GCLK ... there is no redundant GCLK ... there is a redundant MCU... Then... go to step 3. go to step 5. go to step 6.
Swap to the redundant GCLK. If... the alarm clears... the alarm persists... Then... replace the failed GCLK to restore redundancy. No further action is necessary. go to step 4.
Send a field representative to the site to check the link. If this is OK, the representative should recalibrate the GCLK. If... the alarm clears... the alarm persists... Then... no further action is necessary. assume that both GCLKs are faulty and replace them with equipment known to be good. Then... the alarm is due to a link problem. Send a field representative to the site to troubleshoot the E1/T1 link. 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/T1 link. Then... replace the failed MCU to restore redundancy. No further action is necessary. send a field representative to the site to check the E1/T1 link.
Check the DAC value. If the DAC value is... moving around... stuck at a limit...
Swap to the redundant MCU. If... the alarm clears... the alarm persists...
68P02901W26-Q 24 May 2004
20-27
15. GCLK: Watchdog Timer Expired

Description
The Synchronization (SYNC) process on the MCU board watchdog timer unexpectedly expired.
This alarm applies only to MCU-based sites.
System action

Possible cause(s)
The following are possible causes for this alarm: The SYNC firmware failed. The MCU board failed.
20-28
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-12 1 Watchdog Timer Expired
2 3
Reset the site. Determine if this alarm recurs after the reset. If the alarm... recurs... does not recur... Then... Send a field representative to the site to replace the MCU reporting the alarm. The alarm condition no longer exists. Further fault isolation is not required.
68P02901W26-Q 24 May 2004
20-29
16. GCLK: Clock Output Failure

Description
The GCLK Synchronization (SYNC) hardware is not generating the 16.384 MHz clock signal in the system.
System action

Possible cause(s)
The following are possible causes for this alarm: The SYNC firmware is faulty. The MCU board failed.
20-30
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-13 1 Clock Output Failure
2 3
68P02901W26-Q 24 May 2004
20-31
17. GCLK: SYNC Shutdown Request

Description
A GCLK Synchronization (SYNC) function has experienced a catastrophic failure causing a shutdown request to be issued.
System action

Possible cause(s)
The following are possible causes for this alarm: The SYNC firmware is faulty. The MCU board failed.
20-32
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-14 1 SYNC Shutdown Request
2 3
68P02901W26-Q 24 May 2004
20-33
18. GCLK: Not Operational

Description
The MCU Synchronization (SYNC) function did not complete the required initialization that prevents the GCLK from becoming operational.
System action

Possible cause(s)
The following are possible causes for this alarm: The operational SYNC firmware is corrupted. The SYNC hardware is faulty.
20-34
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-15 1 Not Operational
2 3
68P02901W26-Q 24 May 2004
20-35
19. GCLK: Warmup Failure

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.
This alarm applies only to MCU-based sites. 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 cause(s)
The following are possible causes for this alarm: 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.
20-36
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-16 1 Warmup Failure
2 3
68P02901W26-Q 24 May 2004
20-37
20. GCLK: Invalid Mode

Description
The MCU Synchronization (SYNC) function 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 may not be able to continue normal operation.
This alarm applies only to MCU-based sites. 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.

Possible cause(s)
The following are possible causes for this alarm: The operational SYNC firmware is corrupted. The boot portion of the firmware is probably not corrupted. The SYNC processor failed.
20-38
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-17 1 Invalid Mode
2 3
68P02901W26-Q 24 May 2004
20-39
21. GCLK: Calibration In Progress
21. GCLK: Calibration In Progress

Description
The OMC-R operator requested calibration of the GCLK Synchronization (SYNC) hardware.
This alarm applies only to MCU-based sites. The calibration is performed on the MCU SYNC circuit. No call processing can occur on the affected MCU during the calibration process. The MCU is reset after the GCLK SYNC calibration has been completed.

Possible cause(s)
The OMC-R operator request the calibration.
Procedure
Procedure 20-18 Calibration In Progress
This alarm condition does not require fault isolation/resolution. The MCU is automatically reset by the system after the calibration is completed.
20-40
68P02901W26-Q 24 May 2004
22. GCLK: Calibration via Firmware Initiated
22. GCLK: Calibration via Firmware Initiated

Description
The OMC-R operator requested a firmware-directed calibration of GCLK Synchronization (SYNC) hardware.
This alarm applies only to MCU-based sites. The calibration is performed on the MCU SYNC circuit. No call processing can occur on the affected MCU during the calibration process.

Possible cause(s)
The OMC-R operator requested the calibration.
Procedure
Procedure 20-19 Calibration via Firmware Initiated
This alarm condition does not require fault isolation/resolution. The MCU is automatically reset by the system after the calibration has been completed.
68P02901W26-Q 24 May 2004
20-41
24. GCLK: Bad Clock Source or OCXO (oscillator) Replacement Required

Description
The GCLK Synchronization (SYNC) firmware has detected that one of 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.

20-42
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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 20-20 1 Bad Clock Source or OCXO (oscillator) Replacement Required Determine if any link alarms occurred at the same time that phase lock was lost. If a link alarm... occurred at the same time... did not occur at the same time... 2 If the site is... an InCell site... an MCU-based site... 3 Then... There is a link fault. Troubleshoot the link fault. Go to step 2. Then... Go to step 3. Go to step 4.
Determine what type of site is reporting the alarm.
Determine if the Long-Term-Average Values are Unstable (GCLK 11) alarm was reported for the GCLK. If the GCLK 11 alarm was reported... was not reported... Then... Send a field representative to the site to recalibrate the GCLK. Send a field representative to the site to replace the GCLK. Then... Disable all of the DRI devices, and then go to step 5. Go to step 5.
Determine if the affected processor is the master processor. If the affected processor... is the master processor... is not the master processor...
5 6
Reset the site. Determine if this alarm recurs after the reset. If the alarm... Then...
68P02901W26-Q 24 May 2004
20-43
Procedure 20-20 recurs...
Bad Clock Source or OCXO (oscillator) Replacement Required (Continued) Send a field representative to the site to replace the MCU reporting the alarm. The alarm condition no longer exists. Further fault isolation is not required.
does not recur...
20-44
68P02901W26-Q 24 May 2004
26. GCLK: GCLK Calibration Request

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 20-6 provides both the low and high calibration limits as required by the specific GCLK hardware revision levels shown. Table 20-6 LTA calibration limits Low LTA calibration limit 38h (=56 dec) 38h (=56 dec) 38h (=56 dec) 1Ah (=26 dec) High LTA calibration limit E9h (=233 dec) E9h (=233 dec) E9h (=233 dec) E9h (=233 dec)
GCLK hardware revision level 1-3 5-7 8 9
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 an LTA calculated.
Phase locking must be enabled to calculate an LTA value.

68P02901W26-Q 24 May 2004
20-45
Possible cause(s)
The following are possible causes for this alarm: 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 20-21 1 GCLK Calibration Request
Determine what type of site is reporting the alarm. If the site is... an InCell site... an MCU-based site... Then... go to step 2. go to step 3.
With Phase Lock enabled, determine if the Long Term Average Values are Unstable (GCLK 11) alarm was reported for the GCLK. If the GCLK 11 alarm ... was reported... was not reported... Then... send a field representative to the site to check the E/T11 link. 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 50ppb, check the E1/T1 link.
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...
20-46
68P02901W26-Q 24 May 2004
Procedure 20-21
GCLK Calibration Request (Continued) wait 24 hours after the MCU was powered up or recalibrated. If the alarm is not cleared after 24 hours, send a field representative to the site to check the E1/T1 link. send a field representative to the site to recalibrate the GCLK.
being powered up for the first time...
not being powered up for the first time or was recalibrated during the previous 24 hour period, and phase lock is not enabled...
68P02901W26-Q 24 May 2004
20-47
232. GCLK: Processor Bus Communication Failure

Description
A GCLK board device has lost the ability to communicate to the GCLK via the MCAP bus. The GCLK is placed OOS.

Possible cause(s)
The following are possible causes for this alarm: The GCLK board was physically removed from the shelf. The part of the GCLK that supports the MCAP bus access failed.
20-48
68P02901W26-Q 24 May 2004
Procedure
Procedure 20-22 Processor Bus Communication Failure Determine the current operational and administrative states of the GCLK.
If the GCLK is... busy and unlocked...
Then... The alarm condition has ceased. Further fault isolation is not required. If this alarm recurs frequently, send a field representative to the site to replace the GCLK. Send a field representative to the site to replace the GCLK.
not busy and unlocked...
68P02901W26-Q 24 May 2004
20-49
20-50
68P02901W26-Q 24 May 2004
21
GPROC alarms
This chapter details GCLK alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "1. GPROC: EEPROM Flash Failure - No Valid Bootstrap Code Object Present" on page 21-4 "8. GPROC: EEPROM Flash Object Failure" on page 21-6 "17. GPROC: EEPROM Flash Programming Failure" on page 21-8 "21. GPROC: EEPROM Flash Programming Failure" on page 21-10 "22. GPROC: SWFM Indication" on page 21-11 "23. GPROC: SYNC Lost Phase Lock to Master GCLK " on page 21-12 "24. GPROC: Bad Clock Source or SYNC OCXO(oscillator) Replacement Required " on page 21-13 "25. GPROC: SYNC Warmup Failure" on page 21-14 "26. GPROC: SYNC Calibration Request " on page 21-15 "27. GPROC: SYNC Shutdown Request " on page 21-16 "28. GPROC: SYNC Clock Output Failure " on page 21-17 "29. GPROC: SYNC Watchdog Timer Expired " on page 21-18 "30. GPROC: Clock A Signal Loss" on page 21-19 "31. GPROC: Clock B Signal Loss" on page 21-21 "32. GPROC: TDM Interface Failure - Assigned Timeslot Counter Underflow" on page 21-23 "33. GPROC: TDM Interface Failure - Assigned Timeslot Counter Overflow" on page 21-25 "34. GPROC: TDM Interface Failure - TDM Parity Error" on page 21-27 "35. GPROC: LAN Connection Failure" on page 21-29 "39. GPROC: Software Failure" on page 21-31 "40. GPROC: Spurious Interrupt" on page 21-33 "42. GPROC: Site Reset Occurred Due To Front Panel Reset" on page 21-35 "43. GPROC: SYNC Not Operational " on page 21-36 21-1
Chapter
Chapter 21: GPROC Alarms
"44. GPROC: SYNC Calibration via Firmware Initiated " on page 21-37 "45. GPROC: SYNC Phase Lock Failure " on page 21-38 "46. GPROC: SYNC Invalid Mode " on page 21-39 "47. GPROC: Unexpected Board Type: GPROC2 or GPROC3 expected" on page 21-40 "48. GPROC: Memory location is corrupt. Replace GPROC board." on page 21-42 "50. GPROC: EEPROM SW Flash Programming Failure." on page 21-43 "51. GPROC: EEPROM SW Flash Programming Failure." on page 21-44 "231. GPROC: TDM Interface Configuration Failure" on page 21-45 "239. GPROC: Process Safe Test Audit Failure" on page 21-47 "254. GPROC: Device Failure" on page 21-49
21-2
68P02901W26-Q 24 May 2004
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 pre-defined 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 an 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 21-1. Table 21-1 GPROC FRUs FRU GPROC GPROC2 {4354} GPROC3 MCU MCUF MCUm ARENA (MCU) ARENA MAC (MCU) HORIZONMIC2 (MCU) HORIZONCOM2 (MCU) Description InCell GPROC board InCell GPROC2 board InCell GPROC3 board Main Control Unit Main Control Unit Main Control Unit Main Control Unit Main Control Unit Main Control Unit Main Control Unit
68P02901W26-Q 24 May 2004
21-3
1. GPROC: EEPROM Flash Failure - No Valid Bootstrap Code Object Present

Description
The Initialization Process (IP) determined that the bootstrap code object (Object 15) in the flash EEPROM does not exist or is corrupt.

Possible cause(s)
Procedure
Procedure 21-1 1 EEPROM Flash Failure - No Valid Bootstrap Code Object Present
Obtain a new OMC-R code bootstrap object.
21-4
68P02901W26-Q 24 May 2004
Procedure 21-1 3
EEPROM Flash Failure - No Valid Bootstrap Code Object Present (Continued)
68P02901W26-Q 24 May 2004
21-5
8. GPROC: EEPROM Flash Object Failure

Description

Possible cause(s)
Procedure
2 21-6
Obtain a new OMC-R code object. 68P02901W26-Q 24 May 2004
Procedure 21-2 3
68P02901W26-Q 24 May 2004
21-7
17. GPROC: EEPROM Flash Programming Failure

Description
This fault condition is not a problem unless the GPROC is being reset, at which time the GPROC is rendered useless.

Possible cause(s)
Procedure
21-8
68P02901W26-Q 24 May 2004
19. GPROC: RSL Links Congestion
19. GPROC: RSL Links Congestion

Clearing Type: Severity Level: Category:
FMIC Investigate Communication
Description
The flow of messages exceeds the transmittability of RSL links. Links congestion was detected on one or more RSL(s) on this GPROC.
Some paging messages may be discarded when this alarm is present. Hence, the associated services will not be provided. For example, some new calls may not be established. The user should select retry or wait a while to avoid peak usage of the system.

Possible cause(s)
Huge number of paging messages coming from the MSC. The transmittability of RSL is too low.
Procedure
Send a field representative to the site to determine whether or not it is necessary to expand network capability.
68P02901W26-Q 24 May 2004
21-9

Description

Possible cause(s)
Procedure
21-10
68P02901W26-Q 24 May 2004
22. GPROC: SWFM Indication
22. GPROC: SWFM Indication

Description
The system has detected a software processing error (SWFM) for a GPROC.

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
21-11
23. GPROC: SYNC Lost Phase Lock to Master GCLK
23. GPROC: SYNC Lost Phase Lock to Master GCLK

Clearing Type: Severity Level: Category: Intermittent Major Equipment
Description
This alarm indicates that having been in phase locked mode, the SYNC circuit has lost phase lock to the master.

Possible cause(s)
Noise on the HDLC link. Faulty HDLC link.
Procedure
Procedure 21-6 SYNC Lost Phase Lock to Master GCLK
Report that the fault requires HDLC/SYNC investigation.
21-12
68P02901W26-Q 24 May 2004
24. GPROC: Bad Clock Source or SYNC OCXO(oscillator) Replacement Required
24. GPROC: Bad Clock Source or SYNC OCXO(oscillator) Replacement Required

Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by replacing the FRU itself.

Possible cause(s)
Aging of clock circuitry. SYNC malfunctioning.
Procedure
Procedure 21-7 GPROC: Bad Clock Source or SYNC OCXO (oscillator) Replacement Required
Report that the SYNC circuit requires investigation. FRU replacement required. If FRU is not replaced, this could lead to other SYNC alarms being generated which can result in the reset of the FRU.
68P02901W26-Q 24 May 2004
21-13
25. GPROC: SYNC Warmup Failure
25. GPROC: SYNC Warmup Failure

Clearing Type: Severity Level: Category: Intermittent Critical 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 cause(s)
Procedure
Procedure 21-8 SYNC Warmup Failure
Report that the SYNC circuit (hence FRU) requires servicing.
21-14
68P02901W26-Q 24 May 2004
26. GPROC: SYNC Calibration Request
26. GPROC: SYNC Calibration Request

Description
This alarm indicates that the SYNC has requested calibration.

Possible cause(s)
Procedure
Procedure 21-9 SYNC Calibration Request
Report that the SYNC circuit requires investigation (clocking usually drifts with time).
68P02901W26-Q 24 May 2004
21-15
27. GPROC: SYNC Shutdown Request
27. GPROC: SYNC Shutdown Request

Description
This alarm indicates that the SYNC circuit has requested shutdown.

Possible cause(s)
Procedure
Procedure 21-10 SYNC Shutdown Request
Report that the SYNC circuit requires investigation.
21-16
68P02901W26-Q 24 May 2004
28. GPROC: SYNC Clock Output Failure
28. GPROC: SYNC Clock Output Failure

Description
This alarm indicates that the SYNC circuit output clock has failed.

Possible cause(s)
SYNC circuit failure. Degraded output signal.
Procedure
Procedure 21-11 SYNC Clock Output Failure
Report that the SYNC circuitry requires investigation.
68P02901W26-Q 24 May 2004
21-17
29. GPROC: SYNC Watchdog Timer Expired
29. GPROC: SYNC Watchdog Timer Expired

Description
This alarm indicates that the SYNC circuit generated a watchdog timer expire indication.

Possible cause(s)
SYNC circuit failure. Degraded output signal.
Procedure
Procedure 21-12 SYNC Watchdog Timer Expired
Report that the SYNC circuitry requires investigation.
21-18
68P02901W26-Q 24 May 2004
30. GPROC: Clock A Signal Loss

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 redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
68P02901W26-Q 24 May 2004
21-19
Procedure
Determine the current administrative and operational state of the site. If Site is... busy-unlocked... not busy-unlocked... Then... Go to step 2. Send a field representative to the site to replace the Clock A GCLK.
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 Second Reference Loss
Send a field representative to the site to perform one of the following procedures based on the results of step 2. If clock alarms... are present on more than 50% of other devices... are present only for the GPROC... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the GPROC. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
21-20
68P02901W26-Q 24 May 2004
31. GPROC: Clock B Signal Loss

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 redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference fails and may cause the site to go OOS.

Possible cause(s)
Procedure
Determine if the site is in service. If Site is... busy-unlocked... not busy-unlocked... Then... Go to step 2. Send a field representative to the site to replace the Clock B GCLK.
68P02901W26-Q 24 May 2004
21-21
Procedure 21-14 2
Determine if any of the following alarms were reported by other devices in the same cage as Clock B: Clock B Signal Loss 6.12 Second Reference Loss
Send a field representative to the site to perform one of the following procedures based on the results of step 2. If clock alarms... are present on more than 50% of other devices... are present only for the GPROC... are not present on other devices... Then... The GCLK failed. The CBUS 0 alarm is also reported and taken OOS. Replace the GCLK. Replace the GPROC. TDM Clock A detection circuitry on the MSI board failed. Replace the MSI board.
21-22
68P02901W26-Q 24 May 2004
32. GPROC: TDM Interface Failure - Assigned Timeslot Counter Underflow

Description
The GPROC 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 cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane are faulty. Assigned timeslot counter register failed.
Procedure
68P02901W26-Q 24 May 2004
21-23
Procedure 21-15 2
not busy-unlocked... Reset the GPROC.
The site is reset. 3 Determine the state of the GPROC after the reset is completed. If the GPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
21-24
68P02901W26-Q 24 May 2004
33. GPROC: TDM Interface Failure - Assigned Timeslot Counter Overflow

Description
The GPROC has determined that the TDM highway is overused. More switch-bound timeslots are driven onto the TDM bus than were allocated in the assigned timeslot counter register.

Possible cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane is faulty. Assigned timeslot counter register failed.
Procedure
68P02901W26-Q 24 May 2004
21-25
Procedure 21-16 2
not busy-unlocked... Reset the GPROC.
21-26
68P02901W26-Q 24 May 2004
34. GPROC: TDM Interface Failure - TDM Parity Error

Description
An incorrect parity was detected on the switch bound or outbound TDM highway.

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
21-27
Procedure 21-17 2
Reset the GPROC.
21-28
68P02901W26-Q 24 May 2004
35. GPROC: LAN Connection Failure

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 cause(s)
The following are possible causes for this alarm: The GPROC was reset via software or the front panel on site. The GPROC is faulty. The LANX hardware is faulty.
Procedure
Determine the current state of the site. If site is... busy-unlocked... Then... Go to step 2.
68P02901W26-Q 24 May 2004
21-29
Procedure 21-18
not busy-unlocked... 2 Reset the GPROC.
21-30
68P02901W26-Q 24 May 2004
39. GPROC: Software Failure

Description
The GPROC experienced an unrecoverable SWFM error.
SWFM is a debugging tool for Motorola engineering and is only reported if the SWFM indication is turned on at the BSS MMI.
System action

The additional information field includes process information that is only useful to programmers.
Possible cause(s)
The following are possible causes for this alarm: The GPROC software is faulty. The GPROC is faulty.
68P02901W26-Q 24 May 2004
21-31
Procedure
2 3
Send a field representative to the site to replace the GPROC board. Determine the state of the GPROC. If the GPROC is... busy-unlocked... Then... The alarm was probably caused by a software error. Contact a Motorola representative to resolve the software error. Send a field representative to the site to replace the GPROC board.
21-32
68P02901W26-Q 24 May 2004
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 cause(s)
The following are possible causes for this alarm: The timer on the GPROC 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 other cause. The backplane connections to any of the MCAP boards are faulty.
Procedure
Determine if the site was reset. If the site was... reset... Then... Go to step 2.
68P02901W26-Q 24 May 2004
21-33
Procedure 21-20 2
Spurious Interrupt (Continued) Go to step 3. Then... Go to step 3. Go to step 4. Then... The fault condition no longer exists. No further action is required. Go to step 4.
not reset... Determine the current state of the site. If the site is... busy-unlocked... not busy-unlocked... 3 If the GPROC is... busy-unlocked... not busy-unlocked... 4
Determine the current state of the GPROC.
21-34
68P02901W26-Q 24 May 2004
42. GPROC: Site Reset Occurred Due To Front Panel Reset
42. GPROC: Site Reset Occurred Due To Front Panel Reset

Description
The front panel reset switch was pressed on the BTP MCU and the site was reset.

Possible cause(s)
The front panel reset switch was pressed.
Procedure
Procedure 21-21 Site Reset Occurred Due To Front Panel Reset
There is no operator action necessary.
68P02901W26-Q 24 May 2004
21-35
43. GPROC: SYNC Not Operational
43. GPROC: SYNC Not Operational

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 cause(s)
Procedure
Procedure 21-22 SYNC Not Operational
Report that the SYNC circuit requires investigation.
21-36
68P02901W26-Q 24 May 2004
44. GPROC: SYNC Calibration via Firmware Initiated
44. GPROC: SYNC Calibration via Firmware Initiated

Description
This alarm indicates that SYNC calibration was requested via the SYNC firmware MMI.

Possible cause(s)
The operator has requested via the firmware MMI, a calibration of the SYNC circuit.
Procedure
Procedure 21-23 SYNC Calibration via Firmware Initiated
Wait for SYNC calibration completion.
68P02901W26-Q 24 May 2004
21-37
45. GPROC: SYNC Phase Lock Failure
45. GPROC: SYNC Phase Lock Failure

Clearing Type: Severity Level: Category: FMIC Major Service Quality
Description
This alarm indicates that the SYNC circuit has not phase locked to the master within a specified period of being set-up in the slave mode.

Possible cause(s)
Clock source lost. Calibration of SYNC circuit was initiated. Noise on HDLC link. Faulty HDLC link.
Procedure
Procedure 21-24 SYNC Phase Lock Failure
Report that the fault requires HDLC/SYNC investigation.
21-38
68P02901W26-Q 24 May 2004
46. GPROC: SYNC Invalid Mode
46. GPROC: SYNC Invalid Mode

Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by replacing the FRU itself.

Possible cause(s)
Procedure
Procedure 21-25 SYNC Invalid Mode
Report that the SYNC circuit requires investigation. FRU replacement required.
68P02901W26-Q 24 May 2004
21-39
47. GPROC: Unexpected Board Type: GPROC2 or GPROC3 expected

Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or GPROC3 board. If this 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 board can use 8, 16, or 32 timeslots.

Possible cause(s)
Procedure
Verify the value assigned to the gproc_slots database parameter. If the value is... Then...
21-40
68P02901W26-Q 24 May 2004
Procedure 21-26
Unexpected Board Type: GPROC2 or GPROC3 expected (Continued) Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board. Change the value of the gproc_slots database parameter to the correct value and then go to step 2.
correct...
not correct...
Reset the GPROC.
The site is reset. 3 Determine the state of the GPROC after the reset is completed. If the GPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board with a GPROC2 or GPROC3 board.
68P02901W26-Q 24 May 2004
21-41
48. GPROC: Memory location is corrupt. Replace GPROC board.
48. GPROC: Memory location is corrupt. Replace GPROC board.

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 cause(s)
Procedure
Procedure 21-27 Memory location is corrupt. Replace GPROC board
Immediate action is not necessary. Contact the Motorola Local Office and arrange to replace the GPROC3 board at an appropriate time.
21-42
68P02901W26-Q 24 May 2004
50. GPROC: EEPROM SW Flash Programming Failure.

Description

Possible cause(s)
Procedure
Procedure 21-28 EEPROM SW Flash Programming Failure
68P02901W26-Q 24 May 2004
21-43

Description

Possible cause(s)
Procedure
Procedure 21-29 EEPROM SW Flash Programming Failure
This alarm does not take the board out of service. To resolve the alarm, reset the GPROC3 and continue use until it is possible to replace the GPROC3 board.
21-44
68P02901W26-Q 24 May 2004
231. GPROC: TDM Interface Configuration Failure

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 cause(s)
68P02901W26-Q 24 May 2004
21-45
Procedure
Procedure 21-30 TDM Interface Configuration Failure Determine the state of the GPROC.
If the GPROC is... busy-unlocked... not busy-unlocked...
21-46
68P02901W26-Q 24 May 2004
239. GPROC: Process Safe Test Audit Failure

Description
The GPROC failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

03
Possible cause(s)
The following are possible causes for this alarm: The GPROC board is faulty. A process running on the GPROC failed a safe test audit.
68P02901W26-Q 24 May 2004
21-47
Procedure
Determine the error code displayed in the additional information field. If the error code is... 2... 0, 1, or 3... Then... Go to step 2. Go to step 3. Then... Go to step 4. Contact a Motorola representative to resolve the software error.
Perform the safe test audit on the GPROC If the GPROC... passes the audit... fails the audit...
Reset the GPROC.
21-48
68P02901W26-Q 24 May 2004
254. GPROC: Device Failure

Description
The GPROC is taken OOS by the GPROC Fault Management System.
System action
The site resets if it is the master GPROC.

A single byte is displayed in the additional information field identifying the type of site reset, as shown in Table 21-3. Table 21-3 Site reset type Definition Hard reset. Soft reset.
Value (Hex) 01 02
Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
21-49
Procedure 21-32
Device Failure (Continued)
Wait approximately 10 minutes after this alarm is received to allow the site to reset before using this procedure.
Determine the current state of the GPROC. If the GPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
2 3
Reset the GPROC. Determine the state of the GPROC after the reset is completed. If the GPROC is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the GPROC board.
21-50
68P02901W26-Q 24 May 2004
22
GSL alarms
This chapter details GSL alarms and includes the following alarm procedures: "0. GSL: Invalid Received Frames - PM" on page 22-3 "1. GSL: FRMR-Frames - PM" on page 22-4 "2. GSL: Expiration of N2 - PM" on page 22-5 "10. GSL: Link Disconnected" on page 22-6 "11. GSL: LAPD Protocol Error" on page 22-10 "13. GSL: LAPD Protocol Error Threshold Exceeded" on page 22-12 "15. GSL: Too Many LAPD Protocol Errors " on page 22-14
Chapter
68P02901W26-Q 24 May 2004
22-1
Introduction to GSL alarms
Introduction to GSL alarms
GSL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Packet Control Unit (PCU) GPRS Signalling Link (GSL) interface. The GSL carries the signalling link traffic between the BSC and a PCU site. The GSL uses the Multiple Serial Interface link (MMS: E1/T1 link) hardware as its underlying communication link medium.
22-2
68P02901W26-Q 24 May 2004
0. GSL: Invalid Received Frames - PM
0. GSL: Invalid Received Frames - PM

Description
The INVALID_FRAMES_RX statistic threshold has been reached. This statistic counts the number of invalid frames received on the LAPD link. For further information, consult the GSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The signalling link between the BSC and the PCU is faulty.
Procedure
Procedure 22-1 Invalid Received Frames - PM Determine if this alarm is persistently reported.
Then... Send a field representative to the site to check the LAPD link between the BSC and the PCU, and take the appropriate corrective action. Clear the alarm.
68P02901W26-Q 24 May 2004
22-3
1. GSL: FRMR-Frames - PM
1. GSL: FRMR-Frames - PM
Description
The FRMR statistic threshold has been reached. This statistic counts the number of frames on the LAPD link that were rejected because the frames were not correctable. For further information, consult the GSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Then... Send a field representative to the site to check the LAPD link and take the appropriate corrective action. Clear the alarm.
22-4
68P02901W26-Q 24 May 2004
2. GSL: Expiration of N2 - PM
2. GSL: 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. For further information, consult the GSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
22-5
10. GSL: Link Disconnected

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 will be 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 signalled 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 on 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.
22-6
68P02901W26-Q 24 May 2004

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 22-1 details the additional information field for this alarm. Table 22-1 Additional information field contents Byte first second third fourth Value 0A 00 to FF 00 to FF 00 to FF Definition MMS device type. MMS device identifiers.
Possible cause(s)
The following are possible causes for this alarm: A normal link disconnect. One side of the associated MMS is locked, causing the 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/T1 timeslot 0 is good. A GSL guard timer expired.
68P02901W26-Q 24 May 2004
22-7
Procedure
Procedure 22-4 Link Disconnected
Only an experienced operator should attempt to resolve this fault condition.
Determine the state of the GSL device. If the GSL is... busy and unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Continue to step 2. Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 3.
not busy and unlocked... 2 If the GSL... returns to service...
Attempt to restore the GSL device to service.
does not return to service... 3
Determine the state of the MMS device identified in the additional information field. If the MMS is... busy and unlocked... Then... The E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 4.
not busy and unlocked... 4
Determine the state of the parent MSI device for the MMS identified in the additional information field. If the MMS is... Then...
22-8
68P02901W26-Q 24 May 2004
Procedure 22-4
Link Disconnected (Continued) The MMS device is faulty. Review the Alarm/Event window for the MMS alarm and initiate the appropriate alarm handling procedures. The MSI device is faulty. Review the Alarm/Event window for the MSI alarm and initiate the appropriate alarm handling procedures.
busy and unlocked...
68P02901W26-Q 24 May 2004
22-9
11. GSL: LAPD Protocol Error

Description
The GSL detected a LAPD protocol error due to a problem on one of the T1/E1 links. Calls may be lost.

The contents of the additional information field are shown in Table 22-2. Table 22-2 Additional information field contents Byte first second third fourth fifth sixth Value 01 to 1F 00 to FF 0A 00 to FF00 to FF00 to FF Definition MMS timeslot. LAPD error code MMS device type. MMS device identifiers.
Possible cause(s)
The LAPD Error String in the additional information field corresponds to a possible cause for the alarm, as indicated in Table 22-3. Table 22-3 LAPD error indications String Link Timeout Sequence Error Frame Rejected Unexpected Response Frame
22-10
68P02901W26-Q 24 May 2004
Table 22-3
LAPD error indications (Continued) String
Bad Configuration SABM-Extended Received Bad Frame Link SABM-Extended Failure Link Disconnect Failure Link Status Query Failure.
Procedure
Procedure 22-5 1 LAPD Protocol Error
Determine if this is a recurrence of this alarm. If this is... a recurrence of this alarm... not a recurrence of this alarm... Then... Go to step 2. Clear the alarm. Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Review the Alarm/Event window for an MMS alarm and initiate the appropriate alarm handling procedures.
Determine the state of the MMS identified in the additional information field. If the MMS is... busy and unlocked...
68P02901W26-Q 24 May 2004
22-11
13. GSL: LAPD Protocol Error Threshold Exceeded

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

Possible cause(s)
A noisy transmission link.
Procedure
Procedure 22-6 1 LAPD Protocol Error Threshold Exceeded
Determine the state of the GSL device. If the GSL is... busy and unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Continue to step 2.
Attempt to restore the GSL device to service.
22-12
68P02901W26-Q 24 May 2004
Procedure 22-6
LAPD Protocol Error Threshold Exceeded (Continued) Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 3.
If the GSL... returns to service...
Determine the state of the parent MSI device for the MMS identified in the additional information field. If the MMS is... busy and unlocked... Then... The MMS device is faulty. Review the Alarm/Event window for the MMS alarm and initiate the appropriate alarm handling procedures. The MSI device is faulty. Review the Alarm/Event window for the MSI alarm and initiate the appropriate alarm handling procedures.
68P02901W26-Q 24 May 2004
22-13
15. GSL: Too Many LAPD Protocol Errors
15. GSL: Too Many LAPD Protocol Errors

Description
Too many LAPD Protocol errors have been received indicating poor link quality.

6 bytes: byte 1 -- MMS timeslot, byte 2 LAPD fault code, bytes 3-6 -- MMS device id.
Possible cause(s)
4 or more LAPD Protocol errors were received within 1 second indicating major problems with the GSL link.
Procedure
Procedure 22-7 Too Many LAPD Protocol Errors
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/replace it as necessary. Consult Alarm Handling at the OMC customer documentation. Investigate further the GSL if this keeps happening
22-14
68P02901W26-Q 24 May 2004
23
IAS alarms
This chapter details IAS alarms and includes the following alarm procedures: 68P02901W26-Q 24 May 2004 "0. IAS: Unexpected Board Type" on page 23-5 "1. IAS: Serial Bus Connection Failure" on page 23-6 "8. IAS: Power Supply Unit 0 Failure" on page 23-9 "9. IAS: Power Supply Unit 1 Failure" on page 23-11 "10. IAS: Power Supply Unit 2 Failure" on page 23-13 "11. IAS: Power Supply Unit 3 Failure" on page 23-15 "12. IAS: Tx VSWR Antenna Fault" on page 23-17 "13.-15. IAS: Preselector 1A-3A Fuse Failure" on page 23-18 "16. IAS: Matrix Control Main Fuse Failure" on page 23-20 "17. IAS: Matrix Control Redundant Fuse Failure" on page 23-21 "18. IAS: Internal Combiner Main Fuse Failure" on page 23-22 "19. IAS: Internal Combiner Redundant Fuse Failure" on page 23-23 "20. IAS: External Combiner Main Fuse Failure" on page 23-24 "21. IAS: External Combiner Redundant Fuse Failure" on page 23-25 "22. IAS: Multicoupler Main Fuse Failure" on page 23-26 "23. IAS: Multicoupler Redundant Fuse Failure" on page 23-27 "24.-26. IAS: BCU Lower Cage Fan #0-#2 Fuse Failure" on page 23-28 "27.-29. IAS: BCU Upper Cage Fan #3-#5 Fuse Failure" on page 23-29 "30. IAS: Spare Fuse Failure" on page 23-30 "31. IAS: DRAM Battery Backup Fuse Failure" on page 23-31 "32. IAS: IAS +27 V Power Fuse Failure" on page 23-32 "33.- 34. IAS: Battery Backup Fuse #1-#2 Failure" on page 23-33 "35.- 37. IAS: Lower Cage Fan #0-#2 Failure" on page 23-35 23-1
Chapter
Chapter 23: IAS Alarms
23-2
"38.- 40. IAS: Upper Cage Fan #3-#5 Failure" on page 23-37 "41. IAS: Multicoupler Failure" on page 23-39 "46. IAS: Converter Failure" on page 23-41 "47. IAS: Converter Overtemperature" on page 23-43 "48.-50. IAS: Preselector 1B-3B Fuse Failure" on page 23-45 "51. IAS: Duplexer Voltage Error" on page 23-46 "59. IAS: Battery Backup Output Failure" on page 23-47 "60. IAS: Battery Backup Input Failure" on page 23-49 "61. IAS: RCU #5 Circuit Breaker Failure" on page 23-51 "62. IAS: DPSM 1 Failure" on page 23-53 "63. IAS: DPSM 0 Failure" on page 23-55 "64.- 65. IAS: Fan Power Converter 1-2 Failure" on page 23-57 "66.- 70. IAS: RCU #0-#4 Circuit Breaker Failure" on page 23-58 "71.- 74. IAS: Converter #1-#4 Failure" on page 23-60 "75. IAS: IAS +27 V DAB Power Fuse Failure" on page 23-61 "80. IAS: Power Supply Unit - Input Failure" on page 23-62 "81. IAS: Power Supply Unit - Output Failure" on page 23-64 "82. IAS: BTS Cabinet Over Temperature" on page 23-66 "83. IAS: Low Voltage Disconnect Imminent" on page 23-68 "84. IAS: Air Conditioning Unit Failure" on page 23-70 "85. IAS: Heat Management System Unit Failure" on page 23-71 "86. IAS: Cabinet Fan Failure" on page 23-73 "87. IAS: Ancillary Cabinet Over Temperature" on page 23-75 "88.- 90. IAS: Voltage Standing Wave Ratio Sector 1-3 Failure" on page 23-77 "91. IAS: Voltage Standing Wave Ratio Performance Low" on page 23-79 "92. IAS: Smoke Alarm" on page 23-81 "93. IAS: Door Open" on page 23-83 "94. IAS: No Connection to Alarms Board - connection broken" on page 23-85 "95. IAS: Low Noise Amplifier Fuse Failure" on page 23-87 "96. IAS: No Redundant Connection to Alarms Board - connection broken" on page 23-89 68P02901W26-Q 24 May 2004
Chapter 23: IAS Alarms
"97. IAS: No Connection to Alarm Board - Radio OOS" on page 23-91 "98. IAS: No Redundant Connection to Alarms Board - Radio OOS" on page 23-93 "99. IAS: No connection to alarm board - Alarm Board Removed" on page 23-94 "100. IAS: Cabinet Protection System Failure " on page 23-96 "101. IAS: Power Supply Temperature High" on page 23-98 "102. IAS: Mains A.C. Supply Failure" on page 23-100 "103. IAS: Fan Tray 0 Failure" on page 23-102 "104. IAS: Fan Tray 1 Failure" on page 23-104 "105. IAS: Fan Tray 2 Failure" on page 23-105 "106. IAS: Rectifier Failure" on page 23-107 "107. IAS: Battery Box Temperature High" on page 23-109 "108. IAS: Alarm Board Failed" on page 23-111 "109. IAS: Auxiliary Alarm 1" on page 23-113 "110. IAS: Urgent Critical Alarm" on page 23-114 "111. IAS: Cabinet Protection Board Fuse failure" on page 23-116 "112 - 113. IAS: Heat Management System Unit Failure 1 & 2" on page 23-117 "114 - 115. IAS: Mains A.C. Supply Failure 1 & 2" on page 23-118 "116 - 117. IAS: Rectifier Failure 1 & 2" on page 23-119
68P02901W26-Q 24 May 2004
23-3
Introduction to 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.
23-4
68P02901W26-Q 24 May 2004
0. IAS: Unexpected Board Type
0. IAS: Unexpected Board Type

Description
The system detected an unexpected IAS board type.

Possible cause(s)
The following are possible causes for this alarm: The IAS board is faulty. The board is improperly fitted. The software needs updating to recognize the new board ID.
Procedure
Procedure 23-1 Unexpected Board Type
68P02901W26-Q 24 May 2004
23-5
1. IAS: Serial Bus Connection Failure

Description
The physical connection between the IAS board and the SBUS failed.

Possible cause(s)
The following are possible causes for this alarm: 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.
23-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-2 1 2 Serial Bus Connection Failure
Review the alarm report to determine cabinet from which the alarm is reported. 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. Cross-check the output from the command above to determine which cage(s) display IAS connected: YES. If... IAS connected: YES is displayed for both cages... If there is only one cage in the cabinet, go to step 6. If there are two cages, consult the following table. Then... The database is probably not configured correctly. The upper cage must be set to NO. Go to step 4. The database is probably not configured correctly. It is possible that the cages are equipped with the wrong settings. Go to step 4.
IAS connected: YES is displayed for one cage...and, IAS connected: NO is displayed for the other cage... 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 on-site. 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.
68P02901W26-Q 24 May 2004
23-7
Procedure 23-2 5
Serial Bus Connection Failure (Continued)
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.
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.
Consult the manual, Technical Description: BSS Command Reference (68P02901W23) for information regarding MMI commands. There are restrictions for using the referenced modify_value MMI commands.
23-8
68P02901W26-Q 24 May 2004
8. IAS: Power Supply Unit 0 Failure

Description
A failure of Power Supply Unit 0 has been detected due to one of the following: PSU input failure. PSU output failure. PSU overtemperature. PSU fan failure. PSU overvoltage.
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.
68P02901W26-Q 24 May 2004
23-9
Possible cause(s)
The following are possible causes for this alarm: Input voltage may be out of range. Environmental temperature may be too high. Input voltage may have been lost. Output supply cable may be faulty. A power supply fan may have failed. An overvoltage condition may have been detected on the PSU.
Procedure
Procedure 23-3 Power Supply Unit 0 Failure
If the alarm remains active, perform the following: Review the alarm report/event logs to determine the cause of this alarm. 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, prioritise the faults and consult the relevant section of this manual for the alarm descriptions and fault resolution procedures. 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 faulty equipment should be replaced.
This fault condition may be service-affecting if there is no PSU redundancy at the site.
23-10
68P02901W26-Q 24 May 2004

Description

68P02901W26-Q 24 May 2004
23-11
Possible cause(s)
Procedure
23-12
68P02901W26-Q 24 May 2004

Description

68P02901W26-Q 24 May 2004
23-13
Possible cause(s)
Procedure
23-14
68P02901W26-Q 24 May 2004

Description

68P02901W26-Q 24 May 2004
23-15
Possible cause(s)
Procedure
23-16
68P02901W26-Q 24 May 2004
12. IAS: Tx VSWR Antenna Fault
12. IAS: Tx VSWR Antenna Fault

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. Transmissions on the indicated antenna are not happening or are severely degraded. Traffic on the carriers being served by the antenna are likely to be dropped.

The following additional data enumerates which duplexer block detected the failure: Duplexer block number. Firmware Detector Fault Zone.
Possible cause(s)
The following are possible causes for this alarm: Broken or missing antenna/cable. Poor connect to antenna.
Procedure
Procedure 23-7 Tx VSWR Antenna Fault
68P02901W26-Q 24 May 2004
23-17
13.-15. IAS: Preselector 1A-3A Fuse Failure

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

23-18
68P02901W26-Q 24 May 2004
Possible cause(s)
The preselector fuse (1A, 2A, or 3A) was faulty/blown.
Procedure
Procedure 23-8 Preselector 1A-3A Fuse Failure
Send a field representative to the site to replace the bad fuse. While there, check the alarm boards, board installation, fuse connections, and cabling.
68P02901W26-Q 24 May 2004
23-19
16. IAS: Matrix Control Main Fuse Failure
16. IAS: Matrix Control Main Fuse Failure

Description
The +27 V matrix control main power fuse 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).

Possible cause(s)
The matrix control main power fuse was faulty/blown.
Procedure
Procedure 23-9 Matrix Control Main Fuse Failure
23-20
68P02901W26-Q 24 May 2004
17. IAS: Matrix Control Redundant Fuse Failure
17. IAS: Matrix Control Redundant Fuse Failure

Description
The +27 V matrix control redundant power supply fuse 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).

Possible cause(s)
The matrix control redundant fuse was faulty/blown.
Procedure
Procedure 23-10 Matrix Control Redundant Fuse Failure
68P02901W26-Q 24 May 2004
23-21
18. IAS: Internal Combiner Main Fuse Failure
18. IAS: Internal Combiner Main Fuse Failure

Description
The +27 V internal combiner main power fuse 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).

Possible cause(s)
The internal RTC main power fuse was faulty/blown.
Procedure
Procedure 23-11 Internal Combiner Main Fuse Failure
23-22
68P02901W26-Q 24 May 2004
19. IAS: Internal Combiner Redundant Fuse Failure
19. IAS: Internal Combiner Redundant Fuse Failure

Description
The +27 V internal combiner redundant power fuse 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).

Possible cause(s)
The internal RTC redundant power fuse blown was faulty/blown.
Procedure
Procedure 23-12 Internal Combiner Redundant Fuse Failure
68P02901W26-Q 24 May 2004
23-23
20. IAS: External Combiner Main Fuse Failure
20. IAS: External Combiner Main Fuse Failure

Description
The +27 V external combiner main power fuse 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).

Possible cause(s)
The external RTC main power fuse was faulty/blown.
Procedure
Procedure 23-13 External Combiner Main Fuse Failure
23-24
68P02901W26-Q 24 May 2004
21. IAS: External Combiner Redundant Fuse Failure
21. IAS: External Combiner Redundant Fuse Failure

Description
The +27 V redundant combiner power fuse 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).

Possible cause(s)
The external RTC redundant power fuse blown was faulty/blown.
Procedure
Procedure 23-14 External Combiner Redundant Fuse Failure
68P02901W26-Q 24 May 2004
23-25
22. IAS: Multicoupler Main Fuse Failure
22. IAS: Multicoupler Main Fuse Failure

Description
The +27 V multicoupler main power fuse 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).

Possible cause(s)
The multicoupler main power fuse was faulty/blown.
Procedure
Procedure 23-15 Multicoupler Main Fuse Failure
23-26
68P02901W26-Q 24 May 2004
23. IAS: Multicoupler Redundant Fuse Failure
23. IAS: Multicoupler Redundant Fuse Failure

Description
The +27 V multicoupler redundant power fuse 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).

Possible cause(s)
The multicoupler redundant fuse was faulty/blown.
Procedure
Procedure 23-16 Multicoupler Redundant Fuse Failure
68P02901W26-Q 24 May 2004
23-27
24.-26. IAS: BCU Lower Cage Fan #0-#2 Fuse Failure
24.-26. IAS: BCU Lower Cage Fan #0-#2 Fuse Failure

Description
One of the +27 V BCU lower cage fan power fuses (#0, #1, or #2) 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).

Possible cause(s)
The BCU lower cage fan fuse was faulty/blown causing the failure.
Procedure
Procedure 23-17 BCU Lower Cage Fan #0-#2 Fuse Failure
23-28
68P02901W26-Q 24 May 2004
27.-29. IAS: BCU Upper Cage Fan #3-#5 Fuse Failure
27.-29. IAS: BCU Upper Cage Fan #3-#5 Fuse Failure

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

Possible cause(s)
The BCU upper cage fan fuse was faulty/blown.
Procedure
Procedure 23-18 BCU Upper Cage Fan #3-#5 Fuse Failure
68P02901W26-Q 24 May 2004
23-29
30. IAS: Spare Fuse Failure
30. IAS: Spare Fuse Failure

Description
The +27 V power supply spare fuse 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).

Possible cause(s)
The spare fuse was faulty/blown.
Procedure
Procedure 23-19 Spare Fuse Failure
23-30
68P02901W26-Q 24 May 2004
31. IAS: DRAM Battery Backup Fuse Failure
31. IAS: DRAM Battery Backup Fuse Failure

Description
The +27 V DRAM battery backup power fuse 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).

Possible cause(s)
The following are possible causes for this alarm: The battery backup fuse was faulty/blown. The battery backup power supply may not have been connected causing the failure.
Procedure
Procedure 23-20 DRAM Battery Backup Fuse Failure
Send a field representative to the site to replace the bad fuse and check to see if the battery backup is connected.
68P02901W26-Q 24 May 2004
23-31
32. IAS: IAS +27 V Power Fuse Failure
32. IAS: IAS +27 V Power Fuse Failure

Description
The +27 V power supply fuse for the IAS alarm boards 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).

Possible cause(s)
The main +27 V dc power fuse was faulty/blown causing the failure.
Procedure
Procedure 23-21 IAS +27 V Power Fuse Failure
Send a field representative to the site to replace the bad fuse. While there, check the alarm boards, board installation, (fuse) connections, and cabling.
23-32
68P02901W26-Q 24 May 2004
33.- 34. IAS: Battery Backup Fuse #1-#2 Failure

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 cause(s)
The following are possible causes for this alarm: The power supply fuse(s) to the dc-to-dc converter may have been faulty/blown causing the failure. The dc-to-dc converter may have been faulty causing the failure. The battery backup power supply may not have been connected (to the cabinet) causing the failure.
68P02901W26-Q 24 May 2004
23-33
Procedure
Procedure 23-22 1 2 Battery Backup Fuse #1-#2 Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. 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. Then... The back up battery fuse #1 (or #2) on the PDB, PAB, or DAB must be replaced. Continue to the next step. The back up battery fuse #1 (or #2) on the PAB or DAB must be replaced. Continue to the next step.
Determine the type of cabinet where the alarm is occurring. If this is... a BTS5 cabinet...
not a BTS5 cabinet...
Send a field representative to the site to replace the bad fuse. While there, check the back up battery connections, power supply fuses, and the dc-to-dc converter.
23-34
68P02901W26-Q 24 May 2004
35.- 37. IAS: Lower Cage Fan #0-#2 Failure

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 cause(s)
The following are possible causes for this alarm: The power may not have been connected to the fan causing the failure. A mechanical fault may have occurred (for example, a fan blade was obstructed).
68P02901W26-Q 24 May 2004
23-35
Procedure
Procedure 23-23 1 2 Lower Cage Fan #0-#2 Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. Determine whether there are event messages for any fuse alarms. If a fuse is... generating an alarm... not generating an alarm... Then...
Send a field representative to the site to check to see if the fan is still functioning.
23-36
68P02901W26-Q 24 May 2004
38.- 40. IAS: Upper Cage Fan #3-#5 Failure

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 cause(s)
The following are possible causes for this alarm: The power may not have been connected to the fan causing the failure. A mechanical fault may have occurred (eg, fan blade was obstructed).
68P02901W26-Q 24 May 2004
23-37
Procedure
Procedure 23-24 1 2 Upper Cage Fan #3-#5 Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. Determine whether there are event messages for any fuse alarms. If a fuse is... generating an alarm... not generating an alarm... Then...
Send a field representative to the site to check to see if the fan is still functioning.
23-38
68P02901W26-Q 24 May 2004
41. IAS: Multicoupler Failure

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: 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).
If a multicoupler fails, the receiver sensitivity to the Receive (Rx) signal is degraded on the failed antenna path.

Possible cause(s)
One or more preselector fuses was faulty/blown causing the failure.
68P02901W26-Q 24 May 2004
23-39
Procedure
Use the following procedure to resolve the alarm. 1. 2. 3. Review the alarm report/event logs to determine the cause(s) of this alarm. Review the applicable device alarm message. Determine whether there are any active/current Voltage Standing Wave Radio (VSWR) alarms. If yes, perform fault diagnostics on the VSWR alarm. If no, VSWR alarms have been generated, continue to the next step. 4. Send a field representative to the site to replace the multicoupler module.
23-40
68P02901W26-Q 24 May 2004
46. IAS: Converter Failure

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 +12V dc for use by the digital boards.
This alarm applies only to the BTS4D configuration.

Possible cause(s)
The following are possible causes for this alarm: The dc-to-dc power converter may have been faulty. A fuse to the dc-to-dc power converter may have been faulty.
68P02901W26-Q 24 May 2004
23-41
Procedure
Procedure 23-25 1 2 3 Converter Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. Review the applicable device alarm message. Determine if the dc-to-dc power converter failed. If the dc-to-dc power converter... failed... did not fail... Then... Send a field representative to the site to replace the dc-to-dc converter module. There is a fuse failure. Send a field representative to the site to replace the faulty fuse.
23-42
68P02901W26-Q 24 May 2004
47. IAS: Converter Overtemperature

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

Possible cause(s)
The following are possible causes for this alarm: The dc-to-dc power converter may have been faulty causing the failure. A fuse to dc-to-dc power converter may have been faulty.
68P02901W26-Q 24 May 2004
23-43
Procedure
Procedure 23-26 1 2 3 4 Converter Overtemperature
Review the alarm report/event logs to determine the cause(s) of this alarm. Check the alarm report for other internal (cabinet) alarms as well as External Alarm System (EAS) alarms. After checking the report, determine whether the dc-to-dc converter failed. Determine whether the antenna is functioning at the site. If the antenna is... functioning... Then... Send a field representative to the site to check the following: not functioning... the connection between the antenna and the VSWR Bridge. the connection between the VSWR Bridge and the PAB board. Make any necessary adjustments.
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.
23-44
68P02901W26-Q 24 May 2004
48.-50. IAS: Preselector 1B-3B Fuse Failure
48.-50. IAS: Preselector 1B-3B Fuse Failure

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. 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
Note that 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 cause(s)
The preselector fuse (1B, 2B, or 3B) was faulty/blown causing the failure.
Procedure
Procedure 23-27 Preselector 1B-3B Fuse Failure Send a field representative to the site to replace the bad fuse. While there, check the alarm boards, board installation, (fuse) connections, and cabling.
68P02901W26-Q 24 May 2004
23-45
51. IAS: Duplexer Voltage Error
51. IAS: Duplexer Voltage Error

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 cause(s)
The following are possible causes for this alarm: A tripped circuit breaker in the cabinet A blown fuse in the duplexer.
Procedure
Procedure 23-28 Duplexer Voltage Error Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
23-46
68P02901W26-Q 24 May 2004
59. IAS: Battery Backup Output Failure

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)/Remote Transcoder Unit (RXU) in the event of a main power failure.

Possible cause(s)
The following are possible causes for this alarm: The power supply fuse(s) to the dc-to-dc converter may have been faulty/blown causing the failure. The dc-to-dc converter may have been faulty causing the failure. The battery backup power supply may not have been 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-Q 24 May 2004
23-47
Procedure
Procedure 23-29 1 2 Battery Backup Output Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. 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.
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. Continue to the next step. For a non-BTS5 cabinet, the battery fuse on the PAB, or DAB must be replaced. Continue to the next step.
Send a field representative to the site to determine if the battery backup is connected. While there, check the back up battery connections, power supply fuses, and the dc-to-dc converter.
23-48
68P02901W26-Q 24 May 2004
60. IAS: Battery Backup Input Failure

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)/Remote Transcoder Unit (RXU) in the event of a main power failure.

Possible cause(s)
The following are possible causes for this alarm: The fuse on the power alarm system may have been faulty/blown causing the failure. The battery backup power supply may not have been connected (to the power alarm system) causing the failure.
68P02901W26-Q 24 May 2004
23-49
Procedure
Procedure 23-30 1 2 Battery Backup Input Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. 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.
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. Continue to the next step. For a non-BTS5 cabinet, the battery fuse on the PAB, or DAB must be replaced. Continue to the next step.
Send a field representative to the site to determine if the battery backup is connected. While there, check the back up battery connections, power supply fuses, and the dc-to-dc converter.
23-50
68P02901W26-Q 24 May 2004
61. IAS: RCU #5 Circuit Breaker Failure

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 cause(s)
The following are possible causes for this alarm: The overcurrent protection trip may have been faulty. The circuit breaker may have failed. The circuit breaker may have been (accidentally) disconnected.
68P02901W26-Q 24 May 2004
23-51
Procedure
Procedure 23-31 1 2 RCU #5 Circuit Breaker Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. Send a field representative to the site to reset the breaker and/or replace the faulty hardware.
23-52
68P02901W26-Q 24 May 2004
62. IAS: DPSM 1 Failure

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 cause(s)
68P02901W26-Q 24 May 2004
23-53
Procedure
Procedure 23-32 1 2 DPSM 1 Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. 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.
23-54
68P02901W26-Q 24 May 2004

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 cause(s)
68P02901W26-Q 24 May 2004
23-55
Procedure
Procedure 23-33 1 2 DPSM 0 Failure
Review the alarm report/event logs to determine the cause(s) of this alarm. 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 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 0.
23-56
68P02901W26-Q 24 May 2004
64.- 65. IAS: Fan Power Converter 1-2 Failure
64.- 65. IAS: Fan Power Converter 1-2 Failure

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 cause(s)
Procedure
Procedure 23-34 Fan Power Converter 1-2 Failure
Send a field representative to the site to check the circuit breaker to determine whether it has failed, or has been disconnected. Reconnect or replace the faulty circuit breaker.
68P02901W26-Q 24 May 2004
23-57
66.- 70. IAS: RCU #0-#4 Circuit Breaker Failure

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 cause(s)
23-58
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-35 RCU #0-#4 Circuit Breaker Failure
Send a field representative to the site to reset or reconnect the circuit breaker or replace the faulty hardware.
68P02901W26-Q 24 May 2004
23-59
71.- 74. IAS: Converter #1-#4 Failure
71.- 74. IAS: Converter #1-#4 Failure

Description
This alarm indicates that the -48 V (or-60 V) dc-to-dc input power to a power converter module (1-4) via a circuit breaker was interrupted causing the converter to fail.

Possible cause(s)
Procedure
Procedure 23-36 Converter #1-#4 Failure
Send a field representative to the site to check the circuit breaker to determine whether it has failed, or has been disconnected. Reconnect or replace a faulty circuit breaker.
23-60
68P02901W26-Q 24 May 2004
75. IAS: IAS +27 V DAB Power Fuse Failure
75. IAS: IAS +27 V DAB Power Fuse Failure

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 applies/sustains power to the Distribution Alarm Board (DAB).

Possible cause(s)
Procedure
Procedure 23-37 IAS +27 V DAB Power Fuse Failure
Send a field representative to the site to check the circuit breaker to determine whether it has failed, or has been disconnected. Reconnect or replace a faulty circuit breaker.
68P02901W26-Q 24 May 2004
23-61
80. IAS: Power Supply Unit - Input Failure

Description
This alarm indicates that there has been a loss of ac power. Because of the 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-Cellmicro, M-Cellcity, Horizon II macro, Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarena macro) cabinets.
This fault condition is service-affecting.

Possible cause(s)
The following are possible causes for this alarm: For an indoor system: The input voltage may have been out of specification causing the failure. (In this case, the power supply units would operate for a small duration until the input voltage was completely out of range.)
For an outdoor system: The ac supply may have been faulty.
23-62
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-38 Power Supply Unit - Input Failure
Send a field representative to the site to determine if the input power source (equipment/cables) are faulty.
68P02901W26-Q 24 May 2004
23-63
81. IAS: Power Supply Unit - Output Failure

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 may have been interrupted (or discontinued) due to faulty equipment. This alarm applies only to M-Cell2, M-Cell6, Horizonmacro and Horizon II macro cabinets.
This fault condition can be service-affecting if there is no PSU redundancy at a site.

Possible cause(s)
The following are possible causes for this alarm: The input feed (voltage) may have been lost causing the output failure. The output power supply cable may have been faulty.
23-64
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-39 1 Power Supply Unit - Output Failure
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 consult this manual for the Alarm descriptions and fault resolution procedures. If other failures do not exist at that site, go to step 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.
68P02901W26-Q 24 May 2004
23-65
82. IAS: BTS Cabinet Over Temperature

Description
This alarm indicates that a Base Transceiver Station (BTS) cabinet ambient temperature has overheated to a level of 70 degrees 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. Horizon II macro

23-66
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The air passage ways (inlet, outlet, and air ways) may have been obstructed. The BTS Over Temperature thermostat may have been faulty. The PSU may have been malfunctioning. (This possible cause does not apply to Horizonmacro cabinets.) The BTS Heat Management System Over Temperature may have been faulty. (This possible cause applies only to outdoor cabinets.)
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. (On-site, 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 23-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.
68P02901W26-Q 24 May 2004
23-67
83. IAS: Low Voltage Disconnect Imminent

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 fault condition is service-affecting. 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-Cellmicro, M-Cellcity, Horizon II macro, Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarena macro) cabinets.

23-68
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The input feed (voltage) may have been lost causing the output failure. The PSU may have been malfunctioning.
Procedure
Procedure 23-41 1 2 3 Low Voltage Disconnect Imminent
Review the alarm report/event logs to determine the cause(s) of this alarm. Investigate the ac power failure. Send a field representative to the site to determine if the PSU, and/or the input power source (equipment/cables) are faulty.
68P02901W26-Q 24 May 2004
23-69
84. IAS: Air Conditioning Unit Failure
84. IAS: Air Conditioning Unit Failure

Description
This alarm indicates that a Base Transceiver Station (BTS), or ancillary cabinet Air Conditioning Unit has failed.
This fault condition is service-affecting. 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 cause(s)
The following are possible causes for this alarm: The air inlet vent to the air conditioning unit may have been blocked causing the unit to fail. The air outlet vent from the air conditioning unit may have been blocked causing the unit to fail. The air conditioning unit may have been faulty.
Procedure
Procedure 23-42 Air Conditioning Unit Failure
Send a field representative to the site to locate the failed unit, and determine if the inlet/outlet vents are blocked. 23-70 68P02901W26-Q 24 May 2004
85. IAS: Heat Management System Unit Failure

Description
This alarm indicates that Ancillary Heat Management Unit at a Base Transceiver Station (BTS) has failed.
This fault condition is service-affecting. 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, Horizonmacro and Horizon II macro cabinets.

Possible cause(s)
The following are possible causes for this alarm: The air inlet vent to the heat management unit may have been blocked causing the unit to fail. The air outlet vent from the heat management unit may have been blocked causing the unit to fail. The heat management unit may have been faulty.
68P02901W26-Q 24 May 2004
23-71
Procedure
Procedure 23-43 Heat Management System Unit Failure
Send a field service representative to the site to locate the failed unit, and determine if the inlet/outlet vents are blocked.
23-72
68P02901W26-Q 24 May 2004
86. IAS: Cabinet Fan Failure

Description
This alarm indicates that a Base Transceiver Station (BTS), or ancillary cabinet fan (or fans) has failed.
This fault condition is service-affecting. 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 cause(s)
The following are possible causes for this alarm: The air inlet vent to the fan unit may have been blocked causing the unit to fail. The air outlet vent from the fan unit may have been blocked causing the unit to fail. The airways may be obstructed causing the fan unit to fail. The Power Supply Unit (PSU) may have been malfunctioning causing the fan unit(s) to stop.
68P02901W26-Q 24 May 2004
23-73
Procedure
Procedure 23-44 Cabinet Fan Failure
Send a field representative to the site to locate the failed unit, and determine if the inlet/outlet vents, or air passage ways are blocked. Check the PSU as well.
23-74
68P02901W26-Q 24 May 2004
87. IAS: Ancillary Cabinet Over Temperature

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 fault condition is service-affecting. 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 cause(s)
The following are possible causes for this alarm: The air passage ways (inlet, outlet, and air ways) may have been obstructed. The Ancillary Over Temperature Thermostat may have been faulty. The PSU may have been malfunctioning. The Ancillary Heat Management System Over Temperature may have been faulty. (This applies only to outdoor cabinets.)
68P02901W26-Q 24 May 2004
23-75
Procedure
Procedure 23-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.
23-76
68P02901W26-Q 24 May 2004
88.- 90. IAS: Voltage Standing Wave Ratio Sector 1-3 Failure
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.

68P02901W26-Q 24 May 2004
23-77
Possible cause(s)
The following are possible causes for this alarm: The VSWR unit may have been faulty. The antenna may have been faulty. The Alarms (or the EAS or PIX) board may have been improperly connected to the VSWR Bridge. The Alarms board (or connectors on the board) may be faulty. (See Note.) The antenna may have been improperly connected to the VSWR Bridge.
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 23-46 Voltage Standing Wave Ratio Sector 1-3 Failure Send a field representative to the site to determine whether the equipment is faulty. The field representative must be prepared to check, repair or replace the following equipment, if necessary:
The VSWR unit (1-3). 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.
23-78
68P02901W26-Q 24 May 2004
91. IAS: Voltage Standing Wave Ratio Performance Low

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.

68P02901W26-Q 24 May 2004
23-79
Possible cause(s)
The following are possible causes for this alarm: The VSWR unit may be faulty. The antenna may be faulty due to weather conditions, external damage, errors in installation, etc. The Alarms (or the EAS or PIX) board (or connectors on the board) may be faulty. (See Note.) The antenna may have been improperly connected to the VSWR Bridge.
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 23-47 Voltage Standing Wave Ratio Performance Low Send a field representative to the site to determine whether the hardware is faulty. The field representative must check all connections, and be prepared to repair or replace the following hardware, if necessary:
The VSWR unit (1-3). 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).
23-80
68P02901W26-Q 24 May 2004
92. IAS: Smoke Alarm

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 may have 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. Horizon II macro

Possible cause(s)
The cause for the smoke alarm is fire which may have been caused by one of the following: The air passage ways (inlet, outlet, and air ways) may have been obstructed causing the equipment to overheat. The fan may have been malfunctioning causing the equipment to overheat. The PSU may have been malfunctioning/overheating. The air conditioning unit may have been faulty causing the equipment to overheat. The Ancillary Heat Management System may have been faulty causing the equipment to overheat. (This possible cause applies only to outdoor cabinets.)
68P02901W26-Q 24 May 2004
23-81
Procedure
Procedure 23-48 Smoke Alarm
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. Replace any defective (or damaged) equipment.
23-82
68P02901W26-Q 24 May 2004
93. IAS: Door Open
93. IAS: Door Open

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, Horizonmacro and Horizon II macro cabinets .

Possible cause(s)
The following are possible causes for this alarm: The cabinet door may not have been secured properly. The door latches may have been defective.
68P02901W26-Q 24 May 2004
23-83
93. IAS: Door Open
Procedure
Procedure 23-49 Door Open
Send a field representative to the site to close the door(s). While there, check the cabinet door latches; any defective latches must be replaced.
23-84
68P02901W26-Q 24 May 2004
94. IAS: No Connection to Alarms Board - connection broken
94. IAS: No Connection to Alarms Board connection broken

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.

68P02901W26-Q 24 May 2004
23-85
94. IAS: No Connection to Alarms Board - connection broken
Possible cause(s)
The following are possible causes for this alarm: The Alarms board link to a DRI (TCU) may not have been established. The Alarms board fibre link to a DRI (TCU) may be faulty. The Alarms board link may be connected to an Out Of Service (OOS) DRI (TCU). The Alarms board link may be connected to an Enabled-Unlocked DRI (TCU) that does not have an RTF equipped. The Alarms board may be faulty.
Procedure
Procedure 23-50 No Connection to Alarms Board - connection broken
23-86
68P02901W26-Q 24 May 2004
95. IAS: Low Noise Amplifier Fuse Failure

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 cause(s)
The following are possible causes for this alarm: The amplifier fuse may have been faulty. The cabling connecting the fuse panel and IADU board may be faulty. The IADU board (above the radios) may be faulty. The Alarms board may be faulty.
Procedure
Procedure 23-51 Low Noise Amplifier Fuse Failure
68P02901W26-Q 24 May 2004
23-87
Procedure 23-51
Low Noise Amplifier Fuse Failure (Continued)
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.
23-88
68P02901W26-Q 24 May 2004
96. IAS: No Redundant Connection to Alarms Board - connection broken

Description
This alarm indicates that BSS software has detected that the redundant (back up) radio connection to the Alarms board is not functioning. The redundant connection may not be functioning due to either a faulty cable or an on-site disconnection.
This alarm applies to M-Cell2 and M-Cell6 cabinets.

Possible cause(s)
The following are possible causes for this alarm: The redundant cable between the radio and Alarms board may have been disconnected. The redundant cable between the radio and Alarms board may be faulty.
Procedure
Procedure 23-52 No Redundant Connection to Alarms Board - connection broken
68P02901W26-Q 24 May 2004
23-89
Procedure 23-52
No Redundant Connection to Alarms Board - connection broken (Continued)
Send a field representative to the site to check the cabling from the Alarms board to the (radio) DRI (TCUs). Be prepared to reconnect or replace the cabling to the Alarms board, if necessary.
23-90
68P02901W26-Q 24 May 2004
97. IAS: No Connection to Alarm Board - Radio OOS

Description
This alarm indicates that 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 radio(s) (DRI (TCUs)) are faulty.

Possible cause(s)
The last (or only) radio DRI (TCU) is faulty.
68P02901W26-Q 24 May 2004
23-91
Procedure
Procedure 23-53 No Connection to Alarm Board - Radio OOS
Send a field representative to the site to check the radios (DRI (TCUs)) connected to the Alarms board. Attempt to restore the faulty DRI (TCUs) to service, and replace either or both DRI (TCUs), if necessary.
23-92
68P02901W26-Q 24 May 2004
98. IAS: No Redundant Connection to Alarms Board - Radio OOS
98. IAS: No Redundant Connection to Alarms Board - Radio OOS

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). Note that two radios (DRI (TCUs)) are connected to the Alarms board.

Possible cause(s)
One radio DRI (TCU) is faulty.
Procedure
Procedure 23-54 No Redundant Connection to Alarms Board - Radio OOS
Send a field representative to the site to check both radios (DRI (TCUs)) connected to the Alarms board; and thus, identify the faulty DRI (TCU). Attempt to restore the faulty (redundant) DRI (TCU) to service, and replace it, if necessary.
68P02901W26-Q 24 May 2004
23-93
99. IAS: No connection to alarm board - Alarm Board Removed

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 Horizonmacro and Horizon II macro cabinets.

23-94
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The Alarms board may not have been properly connected. The Alarms board may have been removed.
Procedure
Procedure 23-55 No connection to alarm board - Alarm Board Removed
Send a field representative to the site to determine whether the Alarms board has been physically removed or is not properly connected. Check the connections, attempt to reconnect the Alarms board, and replace it, if necessary.
68P02901W26-Q 24 May 2004
23-95
100. IAS: Cabinet Protection System Failure

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 will continue to operate. Otherwise, the power system will shutdown and require an on-site 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 cause(s)
The following are possible causes for this alarm: The control board may be faulty. The power supply to the control board may have been disconnected. The power supply to the control board may be faulty. The connection to the cabinet input circuity breaker may be faulty.
Procedure
Procedure 23-56 Cabinet Protection System Failure
23-96
68P02901W26-Q 24 May 2004
Procedure 23-56
Cabinet Protection System Failure (Continued)
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. Reset the power system after the fault condition has been resolved.
68P02901W26-Q 24 May 2004
23-97
101. IAS: Power Supply Temperature High

Description
This alarm indicates that BSS software has detected that one or more Power Supply Units (PSUs) in a Horizonmacro BTS has exceeded the established (safe) temperature range.

Possible cause(s)
The following are possible causes for this alarm: The PSU may be faulty. The environmental temperature may be too high. The Heat Management System (HMS) in an outdoor cabinet may be faulty.
23-98
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-57 1 Power Supply Temperature High
Review the alarm report/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 Horizonmacro 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.
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.
68P02901W26-Q 24 May 2004
23-99
102. IAS: Mains A.C. Supply Failure

Clearing Type: Severity Level: Category: FMIC INvestigate Equipment
Description
This alarm indicates that BSS software has detected that ac power to the back up battery box (connected to a Horizonmacro cabinet) is no longer available. As a result, ac power is not being sent through to the Horizonmacro BTS.

Possible cause(s)
The following are possible causes for this alarm: The ac circuit breaker may be in the off position due to a power surge. The cable from the rectifier to the external Horizonmacro alarm connector may not be properly connected. The cable (or connector on the cable) from the rectifier to the external Horizonmacro alarm connector may be faulty. A rectifier within the battery box may be faulty.
23-100
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-58 Mains A.C. Supply Failure
Send a field representative to the site to determine which equipment has caused this fault condition. Check the ac supply circuit breaker, the cable (rectifier-to-Horizonmacro alarm connector), and the battery box rectifiers. Replace any of the above, if necessary.
68P02901W26-Q 24 May 2004
23-101
103. IAS: Fan Tray 0 Failure

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 cause(s)
The following are possible causes for this alarm: A quad fan may be faulty. The fan fuses may be faulty. The fan tray may not be properly installed.
Procedure
Procedure 23-59 Fan Tray 0 Failure
Send a field representative to the site to determine which equipment has caused this fault condition.
23-102
68P02901W26-Q 24 May 2004
Procedure 23-59
Fan Tray 0 Failure (Continued)
Check the quad fans in fan tray 0, the tray connections, and fan fuses, and replace either the fan tray or fuses, if necessary.
68P02901W26-Q 24 May 2004
23-103

Description

Possible cause(s)
The following are possible causes for this alarm: A dual fan may be faulty. The fan fuses may be faulty. The fan tray may not be properly installed.
Procedure
Send a field representative to the site to determine which equipment has caused this fault condition. Check the dual fans in fan tray 1, the tray connections, and fan fuses, and replace either the fan tray or fuses, if necessary.
23-104
68P02901W26-Q 24 May 2004

Description

Possible cause(s)
The following are possible causes for this alarm: A dual fan may be faulty. The fan fuses may be faulty. The fan tray may not be properly installed.
Procedure
68P02901W26-Q 24 May 2004
23-105
Procedure 23-61
Fan Tray 2 Failure (Continued)
Send a field representative to the site to determine which equipment has caused this fault condition. 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.
23-106
68P02901W26-Q 24 May 2004
106. IAS: Rectifier Failure

Description
This alarm indicates that BSS software has detected that the output from a back up battery box has failed. This alarm is generated when the rectifier has failed or the cable from the battery box (rectifier)-to-Horizonmacro alarm connector is faulty; or when the cable is not properly connected.

Possible cause(s)
The following are possible causes for this alarm: The rectifier may be damaged or faulty. The cable from the rectifier to the external Horizonmacro alarm connector may not be properly connected. The cable (or connector on the cable) from the rectifier to the external Horizonmacro alarm connector may be faulty. The ac power may have failed.
68P02901W26-Q 24 May 2004
23-107
Procedure
Procedure 23-62 1 2 3 Rectifier Failure
Check the output LEDs on the rectifier front panel. Replace the rectifiers that are defective (if any) from the power cage. If no rectifiers are defective, check the cable from the rectifiers in the battery box to the external Horizonmacro 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.
23-108
68P02901W26-Q 24 May 2004
107. IAS: Battery Box Temperature High

Description
This alarm indicates that BSS software has detected that the temperature in the back up battery box has exceeded the established limits for safe operation of the equipment.

Possible cause(s)
The following are possible causes for this alarm: The air passage ways (inlet, outlet, and air ways) may have been obstructed causing the equipment to overheat. The thermostat may be faulty. The environmental temperature may be too high. The Heat Management System (HMS) in an outdoor cabinet may be faulty. The cable from the battery box to a cabinet may not be properly connected. The cable (or cable connectors) from the battery box to a cabinet may be faulty.
68P02901W26-Q 24 May 2004
23-109
Procedure
Procedure 23-63 Battery Box Temperature High
Send a field representative to the site to determine which equipment has caused this fault condition. 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.
23-110
68P02901W26-Q 24 May 2004
108. IAS: Alarm Board Failed

Description
This alarm indicates that BSS software has detected that the Alarms board in a Horizonmacro BTS has failed due to faulty (Alarms) board circuitry or board damage due to conditions in the field.

Possible cause(s)
The following are possible causes for this alarm: 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-Q 24 May 2004
23-111
Procedure
Procedure 23-64 1 Alarm Board Failed
Review the alarm report/event logs to determine the cabinet ID for the Horizonmacro cabinet where the Alarms board has failed. (Note that the cabinet ID is specified by the IAS device ID displayed in the alarm output.) Send a field representative to the site to replace the Alarms board.
23-112
68P02901W26-Q 24 May 2004
109. IAS: Auxiliary Alarm 1
109. IAS: Auxiliary Alarm 1

Description
This is a spare external alarm for the Horizonmacro BTS.

Possible cause(s)
Possible causes are not defined for this alarm.
Procedure
Procedure 23-65 Auxiliary Alarm 1
No clearing procedures are defined for this alarm.
68P02901W26-Q 24 May 2004
23-113
110. IAS: Urgent Critical Alarm

Description
This is a spare external alarm for the Horizonmacro BTS.
This alarm applies only to Horizonmacro and Horizon II macro cabinets. It is used as an external alarm, and is therefore site/customer specific. Alarm IAS 110 can be configured for periodic testing of the backup battery and in this situation the alarm text Urgent Critical Alarm is quite pertinent to the testing of the battery backup system. However, since the same alarm may be used for a variety of purposes by other operators, care must be taken when responding to this alarm. In the event that an operator does not wish to utilize the battery testing feature of alarm IAS110, simply disable the battery testing and the alarm will not occur.

Possible cause(s)
Possible causes are varied depending on what actions the alarm is tied to.
23-114
68P02901W26-Q 24 May 2004
Procedure
Procedure 23-66 Urgent Critical Alarm
Alarm IAS 110 is relative to the condition of the internally fitted batteries. The BSS is pre-programmed to initiate a battery conditioning test every 30 days. If the result of this test is that the expected battery back up time is < 5mins, the IAS 110 alarm will be raised (if enabled). Once raised, the IAS 110 alarm will remain active until a further battery test is completed. The alarm can be over ridden, but this is a manual switch operation on the Control and Alarm board. If the battery test is a feature that is not required, disconnect PL2 of the Alarm Interface board and disable the automated test by switching SW4 No 6 to ON. The battery test can still be performed manually during site visits using the front panel switch.
68P02901W26-Q 24 May 2004
23-115
111. IAS: Cabinet Protection Board Fuse failure
111. IAS: Cabinet Protection Board Fuse failure

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 cause(s)
The following are possible causes for this alarm: 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 23-67 Cabinet Protection Board Fuse failure
23-116
68P02901W26-Q 24 May 2004
112 - 113. IAS: Heat Management System Unit Failure 1 & 2
112 - 113. IAS: Heat Management System Unit Failure 1 & 2
Description
This alarm is generated if the Heat Management System (HMS) at a BTS cabinet fails.

Possible cause(s)
The following are possible causes for this alarm: Faulty HMS. Blocked air inlet or outlet vent. Excessive ambient temperature.
Procedure
Procedure 23-68 Heat Management System Unit Failure 1 & 2
68P02901W26-Q 24 May 2004
23-117
114 - 115. IAS: Mains A.C. Supply Failure 1 & 2
114 - 115. IAS: Mains A.C. Supply Failure 1 & 2

Description
This alarm indicates that the BSS software has detected that the main A.C. input power to the backup battery box is no longer available. This results in a loss of A.C. input power to the BTS.

Possible cause(s)
{4420} The following are possible causes for this alarm: The associated circuit breaker may be in the OFF position following a power surge. Faulty/disconnected cable between the rectifier and external alarm connector. A rectifier within the battery box may be faulty.
Procedure
Procedure 23-69 Mains A.C. Supply Failure 1 & 2
23-118
68P02901W26-Q 24 May 2004
116 - 117. IAS: Rectifier Failure 1 & 2

Description
This alarm indicates that the BSS software has detected that the rectifier output from a backup battery box has failed.

Possible cause(s)
The following are possible causes for this alarm: Damaged/failed rectifier Faulty/disconnected cable between the battery box (rectifier) and external alarm connector.
Procedure
Procedure 23-70 Rectifier Failure 1 & 2
68P02901W26-Q 24 May 2004
23-119
Procedure 23-70
Rectifier Failure 1 & 2 (Continued)
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 may be loose, not properly connected, or faulty, If so, connect it properly or replace if faulty.
23-120
68P02901W26-Q 24 May 2004
24
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 24-4 "1. KSW: Parity Highway 1" on page 24-8 "2. KSW: Parity Highway 2" on page 24-10 "3. KSW: Parity Highway 3" on page 24-12 "4. KSW: Clock A Signal Loss" on page 24-14 "5. KSW: Clock B Signal Loss" on page 24-18 "6. KSW: 6.12 Second Reference Loss" on page 24-22 "7. KSW: Re-Initialized Unexpectedly" on page 24-24 "8. KSW: Hard Reset" on page 24-27 "9. KSW: Watchdog Timer Expired" on page 24-29 "10. KSW: Lost Communication with KSW" on page 24-32 "11. KSW: Local Cage KSW TDM Loopback Test Failure" on page 24-35 "18.- 21. KSW: Failure of Expanded Inbound TDM Highway" on page 24-38 "22.- 24. KSW: KSWX / DSWX in Slot 7-9 Detected Expanded KSW" on page 24-41 "25.- 27. KSW: KSWX/DSWX in Slot 21-23 Detected Expanded" on page 24-43 "224. KSW: Safe Test Audit Failure" on page 24-45 "225. KSW: Internal Loopback Audit Failure" on page 24-47 "232. KSW: Processor Bus Communication Failure" on page 24-50 "254. KSW: Device Failure" on page 24-52
Chapter
68P02901W26-Q 24 May 2004
24-1
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: 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 via status registers on the MCAP bus, or by assertion of an interrupt (message) onto the MCAP bus. The GPROC software then reports the KSW alarm(s). Firmware alarms are generated due to fault conditions existing on: The Time Division Multiplex (TDM) highway(s). The KSW board.
Hardware alarms are generated due to fault conditions with the following: The Digital Signalling 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 24-1. Table 24-1 KSW FRUs FRU KSW TSW KSW-Old Description Kiloport Switch Timeslot Switch Kiloport Switch - Old version
24-2
68P02901W26-Q 24 May 2004
68P02901W26-Q 24 May 2004
24-3
0. KSW: Parity Highway 0

Description
This alarm indicates that a Kiloport Switch (KSW)/Timeslot Switch (TSW) has detected a parity error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway 0. Note that 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 24-2. Note that up to 33 bytes may be displayed in this field. Table 24-2 Additional information field contents Byte first second third Value 00 to 08 00 to 0300 to FF Definition The range (number) of timeslots affected by this fault condition. The specific timeslot number that indicates the beginning of the range. The number of consecutive timeslots within the specified range.
fourth fifth
00 to 0300 to FF
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.
24-4
68P02901W26-Q 24 May 2004
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.
Possible cause(s)
The following are possible causes for this alarm: 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 following devices: 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 24-1 1 2 Parity Highway 0
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW with the parity error. 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. Ensure that the following devices have been reviewed/checked as potential cause(s) for the KSW fault conditions: MSI/XCDR, DRI, GPROC, KSW. Determine whether the entire TDM highway is down, or only a block of timeslots. Then...
3 4
68P02901W26-Q 24 May 2004
24-5
Procedure 24-1
Parity Highway 0 (Continued) Acknowledge the alarms and monitor the alarm events/report to see if the alarm recurs. If yes, immediately switch to the redundant TDM highway (ie, switch to the redundant KSW). Send a field representative to the site to replace the faulty KSW after it has been established that the KSW is the only faulty hardware to be replaced. If no, continue with the next step of this procedure. Acknowledge the alarms and 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. Send a field representative to the site to replace the faulty KSW after it has been established that the KSW is the only faulty hardware to be replaced. If no, continue with the next step of this procedure.
the entire TDM highway is down...
only a block of timeslots are down...
Determine whether this alarm was followed by a 254. KSW: Device Failed alarm. If this alarm is followed by... a 254. KSW: Device Failed alarm... Then... The KSW device has failed. Swap to the redundant KSW. Send a field representative to the site to replace the KSW board (and any other faulty hardware). Review the parity set up for each of the timeslots. Establish the proper parity set up for any of the timeslots that are off. Continue to the next step. Then... 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 representative to the site to replace the KSW.
no device failed alarm...
Determine whether the KSW is BUSY-UNLOCKED. If the KSW is... busy and unlocked...
24-6
68P02901W26-Q 24 May 2004
Procedure 24-1 7 8 9
Parity Highway 0 (Continued) Continue to the next step.
From the Fault Mgt menu select the Lock option to place the faulty KSW (and any other faulty devices) Out Of Service (OOS). From the Fault Mgt menu select the Unlock option to bring the KSW (and the other devices) back In Service (INS). From the View menu again select State to check the operational and administrative state of the KSW and the TDM highway (0). If the KSW is... busy and unlocked... Then... 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 representative to the site to replace the KSW. Send a field representative to the site to replace the KSW.
Reset the site after replacing hardware (including cables).
68P02901W26-Q 24 May 2004
24-7

Description
This alarm indicates that a Kiloport Switch (KSW)/Timeslot Switch (TSW) has detected a parity 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 on the TDM highways, or fault conditions existing on the KSW board.

Possible cause(s)
The following are possible causes for this alarm: 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) may have been down or malfunctioning.
24-8
68P02901W26-Q 24 May 2004
Procedure
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW with the parity error. 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. Determine whether the KSWX is BUSY-UNLOCKED. If the Site is... busy and unlocked... Then... 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 representative to the site to locate and replace the fibre cable connecting the KSWXs and/or the KSWX board(s) if necessary. Send a field representative to the site to locate and replace the fibre 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-Q 24 May 2004
24-9

Description

Possible cause(s)
24-10
68P02901W26-Q 24 May 2004
Procedure
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW with the parity error. 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. Determine whether the KSWX is BUSY-UNLOCKED. If the Site is... busy and unlocked... Then... 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 representative to the site to locate and replace the fibre cable connecting the KSWXs and/or the KSWX board(s) if necessary. Send a field representative to the site to locate and replace the fibre cable connecting KSWXs and/or the KSWX board(s) if necessary.
68P02901W26-Q 24 May 2004
24-11

Description

Possible cause(s)
24-12
68P02901W26-Q 24 May 2004
Procedure
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW with the parity error. 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. Determine whether the KSWX is BUSY-UNLOCKED or not. If the Site is... busy and unlocked... Then... 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 representative to the site to locate and replace the fibre cable connecting the KSWXs and/or the KSWX board(s) if necessary. Send a field representative to the site to locate and replace the fibre cable connecting KSWXs and/or the KSWX board(s) if necessary.
68P02901W26-Q 24 May 2004
24-13
4. KSW: Clock A Signal Loss

Description
This alarm indicates that a Kiloport Switch (KSW)/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 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.
This fault may be service-affecting. When this fault condition occurs, it may cause the Site to go Out Of Service (OOS).

Possible cause(s)
The following are possible causes for this alarm: The GCLK KSW extender A card (GCLK/KSWX A) may have failed. The KSW may have faulty receive (Rx) circuitry.
24-14
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-5 1 2 Clock A Signal Loss
Refer to the alarm message report; determine the site number, device identifiers, and cage of the failed Clock A device(s). 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. 3 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. Determine whether the SITE device is in a BUSY-UNLOCKED device state. Use the table below to determine which troubleshooting procedure to follow. If Site is... BUSY-UNLOCKED... Not BUSY-UNLOCKED... Then... Go to the procedure: "Site is in a Busy-Unlocked state" on page 24-17. Go to the procedure: "Site is not in Busy-Unlocked state" on page 24-15.
4 5
Site is not in Busy-Unlocked state

Procedure 24-6 1 2 3 Site is not in Busy-Unlocked state
Wait 10 minutes and use the State option from the View menu to verify that the SITE device is In Service (INS). If the SITE is not INS, send a field representative to the site to determine where the hardware/cabling is faulty. 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. Note which cages, and the total number of cages that are Out of Service (OOS) at the site.
68P02901W26-Q 24 May 2004
24-15
Procedure 24-6 5
Site is not in Busy-Unlocked state (Continued)
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 Second Reference Loss alarm. See below. If Clock A failure is present on... other MCAP slave boards... Then... The GCLK/KSWX A has failed. Perform one of the following procedures: 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. The Clock A detection circuitry on the KSW has failed. Perform one of the following procedures: 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. Switch to the redundant KSW.
no other boards...
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, fibre cables, KSWXs, etc. 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 on-site equipment and repair procedures see Maintenance Information: BSS/RXCDR On Site (68P02901W38).
24-16
68P02901W26-Q 24 May 2004
Site is in a Busy-Unlocked state

Procedure 24-7 1 2 Site is in a Busy-Unlocked state
Verify that the cage is not Out Of Service (OOS). 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 following: DRI, KSW or TSW, MSI or XCDR, or GCLK. 3 Correlate any previous alarms for the devices within a cage. For example, if a cage experiences clock malfunction, all DRI, KSW (TSW), MSI/XCDR devices in that cage should report a Clock Failure and/or 6.12 Second Reference Loss alarm. If Clock A failure is present on... other MCAP slave boards... Then... The GCLK/KSWX A has failed. Perform one of the following procedures: 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. The Clock A detection circuitry on the KSW has failed. Perform one of the following procedures: 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. Switch to the redundant KSW.
no other boards...
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, fibre cables, KSWXs, etc. After replacing the hardware items, reset the site; then, verify that the site is In-Service (INS) and has resumed normal operation.
68P02901W26-Q 24 May 2004
24-17
5. KSW: Clock B Signal Loss

Description
This alarm indicates that a Kiloport Switch (KSW)/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 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.
This fault may be service-affecting. When this fault condition occurs, it may cause the Site to go Out Of Service (OOS).

Possible cause(s)
The following are possible causes for this alarm: The GCLK KSW extender B card (GCLK/KSWX B) may have failed. The KSW may have faulty receive (Rx) circuitry.
24-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-8 1 2 Clock B Signal Loss
Refer to the alarm message report; determine the site number, device identifiers, and cage of the failed Clock B device(s). 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 following: DRI, KSW or TSW, MSI or XCDR, or GCLK. 3 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. Determine whether the SITE device is in a BUSY-UNLOCKED device state. Use the table below to determine which troubleshooting procedure to follow. If Site is... BUSY-UNLOCKED... Not BUSY-UNLOCKED... Then... Go to the procedure: "Site is in a Busy-Unlocked state" on page 24-20. Go to the procedure: "Site is not in Busy-Unlocked state" on page 24-19.
4 5
Site is not in Busy-Unlocked state

Procedure 24-9 1 2 3 Site is not in Busy-Unlocked state
Wait 10 minutes and use the State option from the View menu to verify that the SITE device is In Service (INS). If the SITE is not INS, send a field representative to the site to determine where the hardware/cabling is faulty. 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. Note which cages, and the total number of cages that are Out of Service (OOS) at the site. 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 Second Reference Loss alarm. See below.
4 5
68P02901W26-Q 24 May 2004
24-19
Procedure 24-9
Site is not in Busy-Unlocked state (Continued) Then... The GCLK/KSWX B has failed. Perform one of the following procedures: Ensure no alarms exist on Clock A. Force the KSW to use the redundant GCLK/KSWX A if the hardware has not already executed the switch. Replace the GCLK/KSWX B at the site. The TDM Clock B detection circuitry on the MSI (or XCDR) has failed. Perform one of the following procedures: Ensure no alarms exist on Clock A. Force the KSW to use the redundant GCLK/KSWX A if the hardware has not already executed the switch. Switch to the redundant KSW.
If Clock B failure is present on... other MCAP slave boards...
no other boards...
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, fibre cables, KSWXs, etc. 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 on-site equipment and repair procedures see Maintenance Information: BSS Field Troubleshooting (68P02901W51).
Site is in a Busy-Unlocked state

Procedure 24-10 1 2 Site is in a Busy-Unlocked state
Verify that the cage is not Out Of Service (OOS). 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 following: DRI, KSW or TSW, MSI or XCDR, or GCLK.
24-20
68P02901W26-Q 24 May 2004
Procedure 24-10 3
Site is in a Busy-Unlocked state (Continued)
Correlate any previous alarms for the devices within a cage. For example, if a cage experiences clock malfunction, all DRI, KSW (TSW), MSI/XCDR devices in that cage should report a Clock Failure and/or 6.12 Second Reference Loss alarm. If Clock B failure is present on... other MCAP slave boards... Then... The GCLK/KSWX B has failed. Perform one of the following procedures: Ensure no alarms exist on Clock A. Force the KSW to use the redundant GCLK/KSWX A if the hardware has not already executed the switch. Replace the GCLK/KSWX B at the site. The TDM Clock B detection circuitry on the MSI (or XCDR) has failed. Perform one of the following procedures: Ensure no alarms exist on Clock A Force the KSW to use the redundant GCLK/KSWX A if the hardware has not already executed the switch. Switch to the redundant KSW.
no other boards...
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, fibre cables, KSWXs, etc. After replacing the hardware items, reset the site; then, verify that the site is In-Service (INS) and has resumed normal operation.
68P02901W26-Q 24 May 2004
24-21
6. KSW: 6.12 Second Reference Loss

Description
This alarm indicates that a Kiloport Switch (KSW)/Timeslot Switch (TSW) has detected that the time reference (6.12 second 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 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.
This fault may be service-affecting.

Possible cause(s)
The following are possible causes for this alarm: The GCLK KSW extender card (GCLK/KSWX) may have failed. The KSW clock detection may have malfunctioned. The physical connection (cabling) may have been down or malfunctioning.
24-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-11 1 2 3 6.12 Second Reference Loss
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the faulty GCLK/KSWX. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. 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. Determine whether the GCLK/KSWX is BUSY-UNLOCKED or not. If the Site is... busy and unlocked... Then... The alarm condition has ceased and further fault isolation is not required. Monitor this device for a recurrence of the alarm. If recurrence of the alarm is excessive, go to the next step. Swap to the redundant GCLK/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 the next step.
5 6
Send a field representative to the site to locate and replace the fibre cable connecting the GCLK/KSWXs, and/or the GCLK/KSWX(s) if necessary. 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-Q 24 May 2004
24-23
7. KSW: Re-Initialized Unexpectedly

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 (on-site) may have reset the device manually after performing system maintenance.

Possible cause(s)
The following are possible causes for this alarm: The KSW board may have been reset via the front panel switch, thus, causing the failure. The KSW board may have been 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.
24-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-12 Re-Initialized Unexpectedly
Wait at least 1 minute for the re-initialization to finish before continuing with this procedure.
1 2
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the re-initialized KSW device. From the Navigation Tree, open the Detailed View for the KSW. From the View menu select State to check the operational and administrative the state of the KSW. If the KSW is... busy and unlocked... Then... 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 representative to the site to replace the KSW. Wait for the re-initialization sequence to complete. Use the INS option from the Fault Mgt menu for the KSW. Continue on to the next step outside this table.
3 4 5
From the Fault Mgt menu select the Lock option to place the KSW Out Of Service (OOS). From the Fault Mgt menu select the Unlock option to bring the KSW back In Service (INS). From the View menu again select State to check the operational and administrative state of the KSW. If the KSW is... Then...
68P02901W26-Q 24 May 2004
24-25
Procedure 24-12
Re-Initialized Unexpectedly (Continued) 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 representative to the site to replace the KSW. Send a field representative to the site to replace the KSW. An additional alarm must have taken the KSW Out Of Service (OOS).
24-26
68P02901W26-Q 24 May 2004
8. KSW: Hard Reset
8. KSW: Hard Reset

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 cause(s)
The following are possible causes for this alarm: The KSW board may have been reset via the front panel switch, causing the failure. The KSW board may have been reset by the software, thus causing the failure.
68P02901W26-Q 24 May 2004
24-27
8. KSW: Hard Reset
Procedure
Procedure 24-13 Hard Reset
Wait at least 1 minute for the reset to finish before continuing with this procedure.
1 2
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the reset KSW device. From the Navigation Tree, open the Detailed View for the KSW. From the View menu select State to check the operational and administrative the state of the KSW. If the KSW is... busy and unlocked... Then... The alarm condition has ceased and further fault isolation is not required. Monitor this device for a recurrence of the alarm condition exceeding normal trends (high frequency and high volume). If recurrence of the alarm is excessive, send a field representative to the site to replace the KSW. Wait for the hard reset sequence to complete. Continue on to step 3.
3 4 5
From the Fault Mgt menu select the Lock option to place the KSW Out Of Service (OOS). From the Fault Mgt menu select the Unlock option to bring the KSW back In Service (INS). From the View menu again select State to check the operational and administrative state of the KSW. If the KSW is... busy and unlocked... Then... The alarm condition has ceased and further fault isolation is not required. Monitor this device for a recurrence of the alarm condition exceeding normal trends (high frequency and high volume). If recurrence of the alarm is excessive, send a field representative to the site to replace the KSW. Send a field representative to the site to replace the KSW.
24-28
68P02901W26-Q 24 May 2004
9. KSW: Watchdog Timer Expired

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 cause(s)
The following are possible causes for this alarm: The firmware may have failed. The processor may have failed. One of the peripheral boards related to the MMS may have failed.
68P02901W26-Q 24 May 2004
24-29
Procedure
Procedure 24-14 Watchdog Timer Expired
Wait at least 1 minute for the reset to finish before continuing with this procedure.
1 2
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW device. From the Navigation Tree, open the Detailed View for the KSW. From the View menu select State to check the operational and administrative the state of the KSW. If the KSW is... busy and unlocked... Then... The alarm condition has ceased and further fault isolation is not required. Monitor this device for a recurrence of the alarm condition exceeding normal trends (high frequency and high volume). If recurrence of the alarm is excessive, send a field representative to the site to replace the KSW board. Initiate a software reset sequence. Wait for the reset sequence to complete. Use the INS option from the Fault Mgt menu for the KSW.Continue on to step 3.
3 4 5
From the Fault Mgt menu select the Lock option to place the KSW Out Of Service (OOS). From the Fault Mgt menu select the Unlock option to bring the KSW back In Service (INS). From the View menu again select State to check the operational and administrative state of the KSW. If the KSW is... Then...
24-30
68P02901W26-Q 24 May 2004
Procedure 24-14
Watchdog Timer Expired (Continued) The alarm condition has ceased and further fault isolation is not required. Monitor this device for a recurrence of the alarm condition exceeding normal trends (high frequency and high volume). If recurrence of the alarm is excessive, send a field representative to the site to replace the KSW board. Switch to redundant KSW if fault condition still exists after the reset is completed. Send a field representative to the site to replace the faulty KSW board.
68P02901W26-Q 24 May 2004
24-31
10. KSW: Lost Communication with KSW

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. Also, note that 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 cause(s)
The following are possible reasons for this error: The KSW Extender (KSWX) card may have been 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.
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.
24-32
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-15 Lost Communication with KSW If the alarm occurs, perform the following:
1 2 3
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW device. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. 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 5
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. Determine if the site has been reset. If yes, wait for the reset to complete before continuing to the next step. If no, go to the step 8.
Determine whether the reset was successful by checking the SITE device state: In a TTY window, use the state 0 SITE <device ids> command.
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. Continue to the next step. Then... The faulty KSW should have automatically swapped to an inactive role. It is in a disabled_unlocked state at this point. Continue to the Note outside this table. The faulty KSW should have resumed normal service in a busy_unlocked state. Continue to the next step outside this table.
Is there a redundant KSW present at the site? If redundancy is... present...
not present...
68P02901W26-Q 24 May 2004
24-33
Procedure 24-15
Lost Communication with KSW (Continued)
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). 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). If the KSW is... busy_unlocked... Then... The master KSW is functioning properly. If a redundant KSW is present, it should be in an Enabled_Unlocked state. Is the redundant KSW 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 the correct device state. If the KSW does not come into an Enabled_Unlocked state, continue to the next step outside this table. 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. Is the master KSW 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 KSW into the correct device state. If the master KSW does not come into an Busy_Unlocked state, continue to the next step outside this table.
enabled_unlocked...
10
Send a field representative to the site to investigate and, if necessary, replace any faulty hardware: KSW, KSWX, GPROC, etc.
24-34
68P02901W26-Q 24 May 2004
11. KSW: Local Cage KSW TDM Loopback Test Failure

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 cause(s)
The following are possible reasons for this error: 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.
Procedure
Procedure 24-16 Local Cage KSW TDM Loopback Test Failure If the alarm occurs, perform the following:
68P02901W26-Q 24 May 2004
24-35
Procedure 24-16
Local Cage KSW TDM Loopback Test Failure (Continued)
1 2 3
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW device. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. 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 5
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. Is there a redundant KSW present at the site? If redundancy is... present... Then... The faulty KSW should have automatically swapped to an inactive role. It is in a disabled_unlocked state at this point. Continue to the Note outside this table. The faulty KSW should have resumed normal service in a busy_unlocked state. Continue to the next step outside this table.
not present...
Determine whether the KSW(s) are functioning properly. Use the state command to verIfy that the master KSW (and redundant, if present) are functioning in the proper device state(s). If the KSW is... busy_unlocked... Then... The master KSW is functioning properly. If a redundant KSW is present, it should be in an Enabled_Unlocked state. Is the redundant KSW 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 the correct device state. If the KSW does not come into an Enabled_Unlocked state, continue to the next step outside this table.
24-36
68P02901W26-Q 24 May 2004
Procedure 24-16
Local Cage KSW TDM Loopback Test Failure (Continued) 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. Is the master KSW 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 KSW into the correct device state. If the master KSW does not come into an Busy_Unlocked state, continue to the next step outside this table.
enabled_unlocked...
Send a field representative to the site to investigate and, if necessary, replace any faulty hardware: KSW, KSWX, GPROC, etc.
68P02901W26-Q 24 May 2004
24-37
18.- 21. KSW: Failure of Expanded Inbound TDM Highway

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 via 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. Use the swap_device command to switch the standby TDM into the active role (Busy-Unlocked). Then, proceed with the test.
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 as shown above.
24-38
68P02901W26-Q 24 May 2004

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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible reasons for this error: The (fibre) connections between expansion mode KSWXs may have been incorrectly set up (on-site). The expansion mode KSWX software configuration may be incorrect due to an erroneous value being entered for the Configuration Management (CM) ksw_config database parameter. The fibre connections between expansion mode KSWX cards may be faulty. An expansion mode KSWX card may be faulty. The KSW card may be 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
Procedure 24-17 KSW: Failure of Expanded Inbound TDM Highway If this alarm occurs, perform the following:
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). 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. If no, continue to the next step.
68P02901W26-Q 24 May 2004
24-39
Procedure 24-17 3
KSW: Failure of Expanded Inbound TDM Highway (Continued)
Use 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... CM database parameter setting(s) Then... Send a field representative 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 on-site configuration. This establishes whether the KSWX fibre and connections are correct. Send a field representative to the site to check board connections; reconfigure and/or replace any faulty equipment.
hardware or equipment
24-40
68P02901W26-Q 24 May 2004
22.- 24. KSW: KSWX / DSWX in Slot 7-9 Detected Expanded KSW
{4415} Clearing Type: Severity Level: Category: FMIC Major Communication
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. Fibre 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 fibre 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-Q 24 May 2004
24-41
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 as shown above.

Possible cause(s)
The following are possible reasons for this error: The fibre connections between KSWX / DSWX cards may have been faulty. The KSWX / DSWX card may be faulty. A corresponding KSWX / DSWX card in another cage may be faulty.
Clearing the alarm

Procedure
Procedure 24-18 KSWX / DSWX in Slot 7-9 Detected Expanded KSW If this alarm occurs, perform the following: 1 2 Refer to the alarm message report to check for the slot number of the KSWX / DSWX for which this alarm is being generated. Send a field representative to the site to check fibre cables, fibre connections, and/or faulty KSWX / DSWX cards. Verify that the toggle switch on the KSWX / DSWX is in the middle (enabled) position. Reinsert cards, reconnect, enable and/or replace faulty equipment when necessary.
This alarm clears within 10 seconds of correcting the fault condition.
24-42
68P02901W26-Q 24 May 2004
25.- 27. KSW: KSWX/DSWX in Slot 21-23 Detected Expanded

{4415} Clearing Type: Severity Level: Category: FMIC Major Communication
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. Fibre 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 fibre 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-Q 24 May 2004
24-43
KSWX/DSWX cards for slots 21 through 23 are described

This alarm description applies to the KSWX/DSWXmatrix 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 as shown above.

Possible cause(s)
The following are possible reasons for this error: The fibre connections between KSWX/DSWX cards may have been faulty. The KSWX/DSWX card may have been faulty. A corresponding KSWX/DSWX card in another cage may be faulty.
Clearing the alarm

Procedure
Procedure 24-19 KSWX/DSWX in Slot 21-23 Detected Expanded If this alarm occurs, perform the following: 1 2 Refer to the alarm message report to check for the slot number of the KSWX/DSWX for which this alarm is being generated. Send a field representative to the site to check fibre cables, fibre connections, and/or faulty KSWX/DSWX cards. Verify that the toggle switch on the KSWX/DSWX is in the middle (enabled) position. Reinsert cards, reconnect, enable and/or replace faulty equipment when necessary.
This alarm clears within 10 seconds of correcting the fault condition.
24-44
68P02901W26-Q 24 May 2004
224. KSW: Safe Test Audit Failure

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. As a result of this fault condition, FM places the failed KSW Out Of Service (OOS). 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 cause(s)
The following are the possible reasons for this error: The KSW board software may not have been functioning correctly. The MCAP interface software may not have been functioning correctly. The MCAP bus may have been 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.
68P02901W26-Q 24 May 2004
24-45
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
Procedure 24-20 Safe Test Audit Failure If the alarm occurs, perform the following: 1 2 3 Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the faulty KSW device. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. 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. If the KSW has... resumed normal functioning... Then... 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. Continue to the next step outside this table. Go to step 4. Then... 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 representative to the site to replace the faulty KSW board. Send a field representative to the site to replace the faulty KSW board.
not resumed normal functioning... 4 If the KSW is... busy and unlocked...
Determine whether the KSW is BUSY-UNLOCKED.
24-46
68P02901W26-Q 24 May 2004
225. KSW: Internal Loopback Audit Failure

Clearing Type: Severity Level: Category: OIC Investigate Communication
Description
This alarm indicates that a Kiloport Switch (KSW)/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. As a result of this fault condition, FM places the failed KSW/TSW Out Of Service (OOS). 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 (eg, 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. For further information, see the Alarm Overview chapter in the front of this manual.

68P02901W26-Q 24 May 2004
24-47
Possible cause(s)
The following are the possible reasons for this error: The KSW/TSW board software may not have been functioning correctly. The Time Division Multiplex Bus (TBUS) may have been 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.
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
Procedure 24-21 Internal Loopback Audit Failure If the alarm recurs, perform the following:
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 the next step.
2 3
Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the faulty KSW/TSW device. (Also, check to see if GPROCs alarms are being generated.) From the Navigation Tree, open the Detailed View for the KSW/TSW. From the View menu select State to check the operational and administrative state of the KSW/TSW. Use the cage_audit command to set up (schedule) another run of the internal loopback audit test. If the KSW/TSW loopback audit is... Then...
24-48
68P02901W26-Q 24 May 2004
Procedure 24-21
Internal Loopback Audit Failure (Continued) 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. Go to the next step . Go to the next step.
successful...
unsuccessful... 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.
68P02901W26-Q 24 May 2004
24-49
232. KSW: Processor Bus Communication Failure

Description
This alarm indicates that a Kiloport Switch (KSW) device has lost the ability to communicate to the GPROC via the Motorola Cellular Advanced Processor (MCAP) Bus.

Possible cause(s)
The following are possible reasons for this error: The KSW and/or the GPROC board may have been 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

Procedure
Procedure 24-22 Processor Bus Communication Failure If the alarm recurs, perform the following:
24-50
68P02901W26-Q 24 May 2004
Procedure 24-22
Processor Bus Communication Failure (Continued)
1 2
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the KSW device. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. If this alarm is received with... a 254. KSW: Device Failed alarm... Then... The KSW device has failed. In a TTY window, use the swap command to switch the redundant KSW to active status. Send a field representative to the site to replace the faulty KSW.
From the Navigation Tree, open the Detailed View for the KSW. From the View menu select State to check the operational and administrative the state of the KSW. Determine whether the KSW is BUSY-UNLOCKED. If the KSW is... busy and unlocked... Then... The alarm condition has ceased 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 field representative to the site to replace the KSW. 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 INS, the alarm condition has ceased and further fault isolation is not required. If the device remains OOS, go to the next step.
5 6
Use the swap command to switch the redundant KSW to active status. Send a field representative to the site to replace the faulty KSW board.
68P02901W26-Q 24 May 2004
24-51
254. KSW: Device Failure

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 cause(s)
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

24-52
68P02901W26-Q 24 May 2004
Procedure
Procedure 24-23 Device Failure If the alarm recurs, perform the following:
1 2 3
Refer to the alarm message report; determine the site number, device identifiers, slot number, and cage of the faulty KSW device. Initiate the appropriate data collection processes (Performance Management, etc.) for troubleshooting purposes. From the Navigation Tree, open the Detailed View for the KSW. From the View menu select State to check the operational and administrative the state of the KSW. Determine whether the KSW is BUSY-UNLOCKED or not. If the KSW is... busy and unlocked... Then... 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, go to step 5. Attempt to bring the KSW 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 INS, the alarm condition has ceased and further fault isolation is not required. If the device remains OOS, go to step 5.
5 6
Use the swap command to switch the redundant KSW to active status. Send a field representative to the site to replace the faulty KSW board.
68P02901W26-Q 24 May 2004
24-53
24-54
68P02901W26-Q 24 May 2004
25
LAN alarms
This chapter details LAN alarms and includes the following alarm procedures: "0. LAN: lan0" on page 25-3 "1. LAN: LAN Failure" on page 25-5
Chapter
68P02901W26-Q 24 May 2004
25-1
Introduction to 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.
25-2
68P02901W26-Q 24 May 2004
0. LAN: lan0
0. LAN: lan0
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 Cause(s)
The following are possible reasons for this error: The standby LAN was OOS when the active LAN failed. The LAN fibre optic cabling was cut.
68P02901W26-Q 24 May 2004
25-3
0. LAN: lan0
Procedure
Procedure 25-1 lan0
Wait approximately 10 minutes after this alarm is received to allow the site to reset before following this procedure. Determine the state of the site.
If the site is... busy-unlocked...
Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
25-4
68P02901W26-Q 24 May 2004
1. LAN: LAN Failure
1. LAN: LAN Failure

Description
This alarm indicates a loss of LAN redundancy at the time the alarm was generated. This can be caused by: 1. The redundant LAN device failed to respond when polled by the 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.
2.
In both cases, the OMC-R alarm logs will 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-Q 24 May 2004
25-5
1. LAN: LAN Failure
Possible Cause(s)
The following are possible reasons for this error: 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 fibre optic cabling was cut. LAN overloaded with messages at the time.
Procedure
Procedure 25-2 1 LAN Failure
Determine if the alarm was reported for the active LAN or the standby LAN. If the alarm is reported for the... active LAN... standby LAN... Then... Go to step 2. Go to step 3. Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
Determine the state of the active LAN device. If the LAN is... busy-unlocked...
not busy-unlocked
25-6
68P02901W26-Q 24 May 2004
26
LMTL alarms
The Local Message Transfer Link (LMTL) alarms are covered in this chapter and includes the following alarm procedures: "0. LMTL: Signalling Link Failure" on page 26-3 "0. LMTL: SL Failure - All Reasons - PM" on page 26-6 "1. LMTL: SMLC Processor Outage" on page 26-8 "1. LMTL: Threshold Reached: SL Failure - Abnormal FIBR/BSNR - PM" on page 26-10 "2. LMTL: Threshold Reached: SL Failure - Excessive Delay of ACK - PM" on page 26-12 "3. LMTL: Link Traffic Too High" on page 26-14 "3. LMTL: Threshold Reached: SL Failure - Excessive Error Rate - PM" on page 26-16 "4. LMTL: Threshold Reached: SL Failure - Excessive Duration of Congestion - PM" on page 26-18 "5. LMTL: Threshold Reached: SL Alignment Failure - PM" on page 26-20 "6. LMTL: Threshold Reached: Number of Signal Units in Error - PM" on page 26-22 "7. LMTL: Threshold Reached: SL Number of Negative ACKs Received - PM" on page 26-24 "8. LMTL: Threshold Reached: Start of Remote Processor Outage - PM" on page 26-26 "9. LMTL: Threshold Reached: Number of Octets Retransmitted - PM" on page 26-28 "10. LMTL: Threshold Reached: MSUs Discarded due to SL Congestion - PM" on page 26-29 "11. LMTL: SL Congestion Events Resulting in Loss of MSUs - PM" on page 26-30 "12. LMTL: Threshold Reached: SL Congestion Indications - PM" on page 26-31
Chapter
68P02901W26-Q 24 May 2004
26-1
Introduction to 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 Kbit/s connection between the SMLC and the BSC. The connection exists on a timeslot on the MMS device. The connection supports the ITU-TSS Signalling System 7 MTP (Message Transfer Part) and SCCP (Signalling Connection Control Part) protocols with the variations specified by GSM.
26-2
68P02901W26-Q 24 May 2004
0. LMTL: Signalling Link Failure

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 0 alarm. See 0. MTL: Signalling Link Failure. The BSS reports an LMTL Signalling 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 signalling 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 Signalling 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 - Signalling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS is placed OOS.

The contents of the additional information field are shown in Table 26-1. Table 26-1 Additional information field contents Byte first second third fourth fifth Value 00 to FF 0A 00 to FF00 to FF00 to FF Definition MMS timeslot. MMS device type. MMS device identifiers.
Any additional bytes displayed should be ignored. 68P02901W26-Q 24 May 2004 26-3
Possible cause(s)
The following are possible causes for this alarm: The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) causing the link failure. The remote congestion timer expired. The MSI acknowledgement timer expired. The sequence numbers may not be synchronized. The Signal Unit Error Rate Monitor (SUERM) detected an excessive signalling error rate.
Procedure
Procedure 26-1 Signalling Link Failure Use the following procedure to resolve the alarm.
Determine if the MSC or RXCDR are rebooting. If... the MSC is rebooting... the RXCDR is rebooting... neither the MSC or RXCDR are rebooting... Then... Wait until the MSC reboot is finished, and then go to step 2. Wait until the RXCDR reboot is finished, and then go to step 3. Go to step 4.
Determine if the alarm is cleared If the alarm is... cleared... not cleared... Then... The fault condition no longer exists.No further action is required. The fault is at the MSC.Contact the MSC to resolve the fault. Then... Go to step 4. Troubleshoot the RXCDR fault.
Determine if the RXCDR returned to service. If the RXCDR... returned to service... did not return to service...
4 5
Reset the LMTL device. Determine the state of the LMTL. If the LMTL is... Then...
26-4
68P02901W26-Q 24 May 2004
Procedure 26-1
Signalling Link Failure (Continued) The fault condition no longer exists. No further action is required. Go to step 5. Then... Resolve the MMS or MSI alarms. Send a field representative to the site to investigate the E1/T1 links.
busy-unlocked... not busy-unlocked... 6 If there are... MMS or MSI alarms... no MMS or MSI alarms...
Determine if there are alarms for the associated MMS or MSI devices.
68P02901W26-Q 24 May 2004
26-5
0. LMTL: SL Failure - All Reasons - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 0 alarm. 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 Signalling Link (SL) has failed for all causes excluding operator interaction using the MMI. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An MSI failed.
Procedure
Procedure 26-2 SL Failure - All Reasons - PM Determine if any MSI alarms are reported.
26-6
68P02901W26-Q 24 May 2004
Procedure 26-2
SL Failure - All Reasons - PM (Continued)
If MSI alarms are... reported... not reported...
Then... Resolve the MSI alarms, and then clear this alarm. Clear the alarm.
68P02901W26-Q 24 May 2004
26-7
1. LMTL: SMLC Processor Outage

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 1 alarm. See 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 signalling 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 cause(s)
The SMLC processor for the remote MTP layer 2 link(s) malfunctioned or failed.
26-8
68P02901W26-Q 24 May 2004
Procedure
Procedure 26-3 SMLC Processor Outage
Send a field representative to the site to replace the SMLC.
68P02901W26-Q 24 May 2004
26-9
1. LMTL: Threshold Reached: SL Failure - Abnormal FIBR/BSNR - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 1 alarm. See 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 Signalling 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). For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The BSN and FSN are being corrupted by the MSC.
Procedure
Procedure 26-4 Threshold Reached: SL Failure - Abnormal FIBR/BSNR - PM Determine if any BSN and FSN are being corrupted by the MSC.
26-10
68P02901W26-Q 24 May 2004
Procedure 26-4
Threshold Reached: SL Failure - Abnormal FIBR/BSNR - PM (Continued)
If the BSN and FSN are... being corrupted by the MSC... not being corrupted by the MSC...
Then... contact the MSC to resolve the problem, and then clear this alarm. clear the alarm.
68P02901W26-Q 24 May 2004
26-11
2. LMTL: Threshold Reached: SL Failure - Excessive Delay of ACK - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 2 alarm. See 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 Signalling Link (SL) was lost because the system failed to acknowledge a Message Signal Unit (MSU) before an internal Motorola-defined timer expired. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A signalling link failed and an MSU acknowledgement has not been sent.
Procedure
Procedure 26-5 Threshold Reached: SL Failure - Excessive Delay of ACK - PM Determine if the MSU is being sent by the MSC.
26-12
68P02901W26-Q 24 May 2004
Procedure 26-5
Threshold Reached: SL Failure - Excessive Delay of ACK - PM (Continued)
If the MSU is... being sent....
Then... a communication link may be faulty.Resolve the communications link fault, then clear this alarm. contact the MSC to resolve the problem, and then clear this alarm.
not being sent...
68P02901W26-Q 24 May 2004
26-13
3. LMTL: Link Traffic Too High

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 3 alarm. See 3. MTL: Link Traffic Too High. The BSS reports an LMTL Link Traffic Too High alarm when the LMTL software process becomes overly congested. Congestion is detected at either the local or remote end of the LMTL affecting the flow of the signalling 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 LMTL(s). A network congestion problem is probably causing the LMTL links to experience signalling 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 signalling 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 cause(s)
High traffic levels on the LMTL do not allow enough time for the device driver to process frames.
26-14
68P02901W26-Q 24 May 2004
Procedure
Procedure 26-6 Link Traffic Too High Use the following procedure to resolve the alarm.
Determine if any LMTL devices are OOS. If all LMTL devices... are OOS... are not OOS... Then... Go to step 2. Go to step 3. Then... The fault condition no longer exists. Clear the alarm. Resolve the Signalling Link Failure (LMTL 0) alarm for the LMTL device(s) that do not return to service, and then clear this alarm.
Reset each OOS LMTL device. If all LMTL devices... return to service... do not return to service...
Clear the alarm. The alarm is due to congestion. The capacity of the current LMTL links is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of LMTL links.
68P02901W26-Q 24 May 2004
26-15
3. LMTL: Threshold Reached: SL Failure - Excessive Error Rate - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 3 alarm. See 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 Signalling Link (SL) was lost because the Signal Unit Error Rate Monitor (SUERM) timer expired. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An MSI failed.
Procedure
Procedure 26-7 hreshold Reached: SL Failure - Excessive Error Rate - PM Determine if any MSI alarms are reported.
26-16
68P02901W26-Q 24 May 2004
Procedure 26-7
hreshold Reached: SL Failure - Excessive Error Rate - PM (Continued)
68P02901W26-Q 24 May 2004
26-17
4. LMTL: Threshold Reached: SL Failure - Excessive Duration of Congestion - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the LMTL 4 alarm. See 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 Signalling 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 an Message Signal Unit (MSU) are reached. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
Procedure 26-8 Threshold Reached: SL Failure - Excessive Duration of Congestion - PM
26-18
68P02901W26-Q 24 May 2004
Procedure 26-8 (Continued)
Threshold Reached: SL Failure - Excessive Duration of Congestion - PM
Clear the alarm. The alarm is due to the duration of a congestion condition that exceeds the capacity of the LMTL links to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of LMTL links.
68P02901W26-Q 24 May 2004
26-19
5. LMTL: Threshold Reached: SL Alignment Failure - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 5 alarm. See 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 Signalling 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. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: 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.
26-20
68P02901W26-Q 24 May 2004
Procedure
Procedure 26-9 Threshold Reached: SL Alignment Failure - PM Determine if other alarms associated with the SL were reported.
If other alarms are... reported... not reported...
Then... Resolve the the alarms, and then clear this alarm. Clear the alarm.
68P02901W26-Q 24 May 2004
26-21
6. LMTL: Threshold Reached: Number of Signal Units in Error - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 6 alarm. See 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 Signalling Unit (SU) is received on the Signalling Link (SL). For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The BSN and FSN are corrupted. A Multiple Serial Interface (MSI) failed. A Generic Clock (GCLK) failed.
26-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 26-10 Threshold Reached: Number of Signal Units in Error - PM Determine if any MSI alarms are reported.
68P02901W26-Q 24 May 2004
26-23
7. LMTL: Threshold Reached: SL Number of Negative ACKs Received - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 7 alarm. See 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. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The BSS and the MSC have incompatible software protocols. The BSS has faulty software. The MSC has faulty software.
26-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 26-11 Threshold Reached: SL Number of Negative ACKs Received - PM Use the following procedure to resolve the alarm.
Determine if the messages between the BSS and the MSC are out of sequence. If the messages are... not out of sequence... out of sequence... Then... The fault condition no longer exists. Clear the alarm. Go to step 2. Then... Contact the MSC to resolve the fault, and then clear the alarm. Send a field representative to the site to resolve the communication link fault, and then clear this alarm.
Determine if the MSC is sending the messages. If the MSC is... sending the messages... not sending the messages...
68P02901W26-Q 24 May 2004
26-25
8. LMTL: Threshold Reached: Start of Remote Processor Outage - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 8 alarm. See 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 signalling messages cannot be transferred. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A remote processor, at the BSS-based SMLC, failed.
Procedure
Procedure 26-12 Threshold Reached: Start of Remote Processor Outage - PM Use the following procedure to resolve the alarm.
26-26
68P02901W26-Q 24 May 2004
Procedure 26-12
Threshold Reached: Start of Remote Processor Outage - PM (Continued)
1 2 3
Determine which remote processor, at the BSS-based SMLC, is reporting the alarm. Initiate problem resolution procedures for the remote processor. After resolving the remote processor fault, clear this alarm.
68P02901W26-Q 24 May 2004
26-27
9. LMTL: Threshold Reached: Number of Octets Retransmitted - PM
9. LMTL: Threshold Reached: Number of Octets Retransmitted - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 9 alarm. See 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 re-transmitted to the BSS-based SMLC due to a request by the BSS-based SMLC. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The BSS retransmitted an excessive number of octets.
Procedure
Procedure 26-13 Threshold Reached: Number of Octets Retransmitted - PM
None: alarms are not cleared by the BSS, and cannot be cleared by the operator.
26-28
68P02901W26-Q 24 May 2004
10. LMTL: Threshold Reached: MSUs Discarded due to SL Congestion - PM
10. LMTL: Threshold Reached: MSUs Discarded due to SL Congestion - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 10 alarm. See 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 Signalling Link (SL). For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The number of LMTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
Procedure 26-14 Threshold Reached: MSUs Discarded due to SL Congestion - PM
None: alarms are not cleared by the BSS, and cannot be cleared by the operator. 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-Q 24 May 2004 26-29
11. LMTL: SL Congestion Events Resulting in Loss of MSUs - PM
11. LMTL: SL Congestion Events Resulting in Loss of MSUs - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 11 alarm. See 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 Signalling Link (SL) congestion event which results in Message Signal Units (MSUs) being lost. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 26-15 SL Congestion Events Resulting in Loss of MSUs - PM
None: alarms are not cleared by the BSS, and cannot be cleared by the operator. The alarm is due to congestion. The capacity of the current LMTLs is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of LMTLs.
26-30
68P02901W26-Q 24 May 2004
12. LMTL: Threshold Reached: SL Congestion Indications - PM

Description
This alarm relates to the Lb interface, but in all other respects is identical to the MTL 12 alarm. See 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 Signalling Link (SL) is congested with a high volume of calls. For further information, consult the LMTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 26-16 Threshold Reached: SL Congestion Indications - PM
None: alarms are not cleared by the BSS, and cannot be cleared by the operator. The alarm is due to congestion. The capacity of the current LMTLs is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of LMTLs.
68P02901W26-Q 24 May 2004
26-31
26-32
68P02901W26-Q 24 May 2004
27
MMS alarms
The Multiple Serial Interface Link (MMS) alarms are covered in this chapter and include the following procedures: 68P02901W26-Q 24 May 2004 "0. MMS: Synchronization Loss Daily Threshold Exceeded" on page 27-6 "1. MMS: Synchronization Loss Hourly Threshold Exceeded" on page 27-8 "2. MMS: Synchronization Loss OOS Threshold Exceeded" on page 27-10 "4. MMS: Remote Alarm Daily Threshold Exceeded" on page 27-13 "5. MMS: Remote Alarm Hourly Threshold Exceeded" on page 27-15 "6. MMS: Remote Alarm OOS Threshold Exceeded" on page 27-17 "8. MMS: Frame Slip Daily Threshold Exceeded" on page 27-20 "9. MMS: Frame Slip Hourly Threshold Exceeded" on page 27-22 "10. MMS: Frame Slip OOS Threshold Exceeded " on page 27-24 "12. MMS: Bit Error Daily Threshold Exceeded" on page 27-25 "13. MMS: Bit Error Hourly Threshold Exceeded" on page 27-27 "14. MMS: Bit Error OOS Threshold Exceeded" on page 27-29 "16. MMS: Synchronization Loss OOS Timer Expired" on page 27-32 "18. MMS: Remote Alarm OOS Timer Expired" on page 27-35 "20. MMS: Red Alarm Daily Threshold Exceeded" on page 27-38 "21. MMS: Red Alarm Hourly Threshold Exceeded" on page 27-40 "22. MMS: Red Alarm OOS Threshold Exceeded" on page 27-42 "23. MMS: Red Alarm OOS Timer Expired" on page 27-45 "24. MMS: Modem to NIU Serial Channel Control Link Failure" on page 27-48 "25. MMS: HDSL Modem Loop 0 Synch Loss Timer Expired" on page 27-50 "26. MMS: HDSL Modem Loop 1 Synch Loss Timer Expired" on page 27-53 "27. MMS: Master HDSL Modem Loop 0 SNR Daily Threshold Exceeded" on page 27-56 "28. MMS: Master HDSL Modem Loop 1 SNR Daily Threshold Exceeded" on page 27-58 27-1
Chapter
Chapter 27: MMS Alarms
"29. MMS: Slave HDSL Modem Loop 0 SNR Daily Threshold Exceeded" on page 27-60 "30. MMS: Slave HDSL Modem Loop 1 SNR Daily Threshold Exceeded" on page 27-62 "31. MMS: Master HDSL Modem Loop 0 SNR Hourly Threshold Exceeded" on page 27-64 "32. MMS: Master HDSL Modem Loop 1 SNR Hourly Threshold Exceeded" on page 27-66 "33. MMS: Slave HDSL Modem Loop 0 SNR Hourly Threshold Exceeded" on page 27-68 "34. MMS: Slave HDSL Modem Loop 1 SNR Hourly Threshold Exceeded" on page 27-70 "35. MMS: Master HDSL Modem Loop 0 SNR OOS Threshold Exceeded" on page 27-72 "36. MMS: Master HDSL Modem Loop 1 SNR OOS Threshold Exceeded" on page 27-75 "37. MMS: Slave HDSL Modem Loop 0 SNR OOS Threshold Exceeded" on page 27-78 "38. MMS: Slave HDSL Modem Loop 1 SNR OOS Threshold Exceeded" on page 27-81 "39. MMS: LTU Download Failure " on page 27-84 "40. MMS: LTU Configuration Failure " on page 27-86 "41. MMS: Connectivity Mismatch Between BSC and RXCDR" on page 27-87 "42. MMS: DSW/DSWX Switching Hardware Required " on page 27-89 "253. MMS: Critical Alarm Threshold Exceeded" on page 27-90
27-2
68P02901W26-Q 24 May 2004
Introduction to MMS alarms
MMS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the 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, Horizonmacro, Horizoncompact (M-Cellarena macro), Horizoncompact2 and micro site systems, which include M-Cellcity, M-Cellmicro, Horizonmicro (M-Cellarena), and Horizonmicro2).
MMS E1/T1 system configuration

Depending on the system software configuration, the MMS device can be configured as either E1 (2.048 Mbit/s) or T1 (1.544 Mbit/s) links. 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/T1 alarm exceptions

Some MMS alarms apply exclusively to either E1 or T1 links: The Synchronization MMS alarms (0, 1, 2, and 16) apply only to systems with an E1 link configuration. The Red MMS alarms (20-23) apply only to systems with a T1 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-Cellmicro, M-Cellcity, Horizonmicro (M-Cellarena), or Horizonmicro2 unit.
68P02901W26-Q 24 May 2004
27-3
Alarm reporting
The InCell MMS hardware alarms are reported to the GPROC by MSI, XCDR, and GDP boards via the MCAP bus. The M-Cell MMS hardware alarms are reported by the M-Cell processor. MMS alarms are generated due to fault conditions existing with: An E1 and/or T1 link cable or microwave link. The environmental factors - bad weather conditions may affect hardware. An MSI/MSI-2 board, MSI in an RF Unit , a XCDR (or GDP) board, or an Network Interface Unit (NIU) - on either side of the link. A remote system.
FRUs
A MMS device may be equipped on one of the FRUs shown in Table 27-1. Table 27-1 MMS FRUs FRU MSI XCDR GDP Description Multiple Serial Interface board. Transcoder board. Generic DSP Processor or Generic Downloadable Processor. Replacement for XCDR. M-Cell/Horizon Network Interface Unit with one or two links. M-Cell MSI that converts a link from E1 to T1 and from T1 to E1. M-Cell MSI configurable for E1 or T1 operation. External HDSL modem. Network interface unit for HDSL. Network interface unit for external HDSL. For GPRS PCU, MMS resides on Network Interface Board (NIB), which is mounted on the DPROC board. Horizonmacro (M-Cellmicro) NIU/MSI with one or two links.
NIU
MSI2-CONV MSI2 MSI-EXT-HDSL NIU-HDSL NIU-EXT-HDSL DPROC
NIUm
27-4
68P02901W26-Q 24 May 2004
Table 27-1
MMS FRUs (Continued) FRU Description Network interface unit for HDSL on Horizonmicro or Horizonmicro2. Network interface unit for external HDSL on Horizonmicro or Horizonmicro2. Horizonmicro (M-Cellarena) NIU/MSI. Horizoncompact (M-Cellarena Macro) NIU/MSI. Horizonmicro2 NIU. Horizoncompact2 NIU.
NIUm-HDSL
NIUm-EXT-HDSL
ARENA (NIU) ARENA MAC (NIU) HORIZONMIC2 (NIU) HORIZONCOM2 (NIU)
68P02901W26-Q 24 May 2004
27-5
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 cause(s)
The following are possible causes for this alarm: 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.
27-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-1 1 Synchronization Loss Daily Threshold Exceeded
Determine if this alarm is persistently reported. If this alarm is... persistently reported... not persistently reported... Then... Go to step 2. Clear the alarm. Then... Resolve the other MMS or MSI alarms, and then clear this alarm. Clear the alarm. This alarm does not merit invasive operator action to resolve this specific fault condition.
Determine if other MMS or MSI alarms were reported at the same time. If other MMS or MSI alarms are... reported... not reported...
68P02901W26-Q 24 May 2004
27-7
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 cause(s)
27-8
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-2 1 Synchronization Loss Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-9
2. MMS: Synchronization Loss OOS Threshold Exceeded

Description
The number of times the MMS receive signal lost synchronization exceeded the sync_loss_oos database element threshold.
System action
The MMS is placed OOS.

Possible cause(s)
27-10
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-3 1 Synchronization Loss OOS Threshold Exceeded
Determine if this alarm is occurring frequently. If this alarm is... occurring frequently... Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Go to step 2. Then... The fault condition no longer exists. Go to step 5. Reset the MMS. If the alarm clears, go to step 5. If the alarm does not clear, go to step 3. Then... The fault condition no longer exists. Go to step 5. Reset the MMS. If the alarm clears, go to step 5. If the alarm does not clear, go to step 3.
not occurring frequently... 2 Determine the state of the MMS. If the MMS is... busy-unlocked... not busy-unlocked...
Determine the state of the MSI. If the MSI is... busy-unlocked... not busy-unlocked...
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... MTLs and/or OMLs... Then... Go to step 5. Go to step 6.
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then...
Determine the state of the logical link devices assigned to the MMS. If...
68P02901W26-Q 24 May 2004
27-11
Procedure 27-3
Synchronization Loss OOS Threshold Exceeded (Continued) The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
all of the logical links are busy-unlocked... any of the logical links are enable-unlocked...
any of the logical links are disable-unlock... 7 If the device is... busy-unlocked... not busy-unlocked...
Determine the state of the logical link device after the reset is complete.
27-12
68P02901W26-Q 24 May 2004
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 cause(s)
The following are possible causes for this alarm: The transmit E1/T1 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-Q 24 May 2004
27-13
The transmit E1/T1 link is experiencing a high BER.
Procedure
Procedure 27-4 1 Remote Alarm Daily Threshold Exceeded
27-14
68P02901W26-Q 24 May 2004
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 cause(s)
The following are possible causes for this alarm: The transmit E1/T1 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. The transmit E1/T1 link is experiencing a high BER.
68P02901W26-Q 24 May 2004
27-15
Procedure
Procedure 27-5 1 Remote Alarm Hourly Threshold Exceeded
27-16
68P02901W26-Q 24 May 2004
6. MMS: Remote Alarm OOS Threshold Exceeded

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 cause(s)
The following are possible causes for this alarm: The transmit 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-Q 24 May 2004
27-17
Procedure
Procedure 27-6 1 Remote Alarm OOS Threshold Exceeded
Determine if this alarm is occurring frequently. If this alarm is... occurring frequently... Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Go to step 2. Then... The fault condition no longer exists. Go to step 4. Reset the MMS. If the alarm clears, go to step 4. If the alarm does not clear, go to step 3. Then... Go to step 4. Reset the MSI. If the alarm clears, go to step 4. If the alarm does not clear, send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
Determine the state of the logical link devices assigned to the MMS.
27-18
68P02901W26-Q 24 May 2004
Procedure 27-6 If...
Remote Alarm OOS Threshold Exceeded (Continued) Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-19
8. MMS: Frame Slip Daily Threshold Exceeded

Description
The number of frame slips on the E1/T1 link exceeded the slip_loss_daily database element threshold.

Possible cause(s)
The following are possible causes for this alarm: The E1/T1 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. The GCLK is not synchronized with this inbound E1/T1 link. The 0.8 Hz tolerance on the GCLK frequency was exceeded.
27-20
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-7 1 Frame Slip Daily Threshold Exceeded
Determine if this is a recurrence of this alarm. If this is... a recurrence... not a recurrence... Then... Go to step 2. Clear the alarm. Then... Troubleshoot the GCLK alarms. After resolving the GCLK alarms, clear the alarm. Go to step 3. Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Clear the alarm. This alarm does not merit invasive operator action to resolve this specific fault condition.
Determine if any GCLK alarms are also reported. If GCLK alarms... are reported...
are not reported... 3 If both MMS 8 and MMS 9 alarms are... reported...
Determine if the MMS 8 and MMS 9 alarms are reported at the same time.
not reported...
68P02901W26-Q 24 May 2004
27-21
9. MMS: Frame Slip Hourly Threshold Exceeded

Description
The number of frame slips on the E1/T1 link exceeded the slip_loss_hourly database element threshold.

Possible cause(s)
The following are possible causes for this alarm: The E1/T1 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. The GCLK is not synchronized with this inbound E1/T1 link. The 0.8 Hz tolerance on the GCLK frequency was exceeded.
27-22
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-8 1 Frame Slip Hourly Threshold Exceeded
Determine if this is a recurrence of this alarm. If this is... a recurrence... not a recurrence... Then... Go to step 2. Clear the alarm. Then... Troubleshoot the GCLK alarms. After resolving the GCLK alarms, clear the alarm. Go to step 3. Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Clear the alarm. This alarm does not merit invasive operator action to resolve this specific fault condition.
Determine if any GCLK alarms are also reported. If GCLK alarms... are reported...
are not reported... 3 If both MMS 8 and MMS 9 alarms are... reported...
Determine if the MMS 8 and MMS 9 alarms are reported at the same time.
not reported...
68P02901W26-Q 24 May 2004
27-23
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 cause(s)
The following are possible causes for this alarm: GCLK is not synchronised with this inbound megastream.
Procedure
Procedure 27-9 Frame Slip OOS Threshold Exceeded
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 the link interface board. Verify as necessary, that the MTL, OML or RSL links have been re-established and all SITEs have returned to service. 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.
27-24
68P02901W26-Q 24 May 2004
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 cause(s)
The following are possible causes for this alarm: The noise present on the receive signal caused the BER to exceed the threshold. The receive E1/T1 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-Q 24 May 2004
27-25
Procedure
Procedure 27-10 1 Bit Error Daily Threshold Exceeded
27-26
68P02901W26-Q 24 May 2004
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 cause(s)
The following are possible causes for this alarm: The noise present on the receive signal caused the BER to exceed the threshold. The receive E1/T1 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-Q 24 May 2004
27-27
Procedure
Procedure 27-11 1 Bit Error Hourly Threshold Exceeded
27-28
68P02901W26-Q 24 May 2004
14. MMS: Bit Error OOS Threshold Exceeded

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 cause(s)
The following are possible causes for this alarm: The noise present on the receive signal caused the BER to exceed the threshold. The trunking equipment that provides site-to-site interface is faulty. The link interface board is faulty. An MSI board is faulty.
Procedure
Procedure 27-12 1 Bit Error OOS Threshold Exceeded
Determine if this alarm is occurring frequently. If this alarm is... occurring frequently... Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-29
Procedure 27-12 2
Bit Error OOS Threshold Exceeded (Continued) Go to step 2. Then... The fault condition no longer exists. Go to step 4. Reset the MMS. If the alarm clears, go to step 4. If the alarm does not clear, go to step 3. Then... Go to step 4. Reset the MSI. If the alarm clears, go to step 4. If the alarm does not clear, send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
not occurring frequently... Determine the state of the MMS. If the MMS is... busy-unlocked... not busy-unlocked...
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action.
Determine the state of the logical link devices assigned to the MMS. If... all of the logical links are busy-unlocked... any of the logical links are enable-unlocked...
27-30
68P02901W26-Q 24 May 2004
Procedure 27-12
Bit Error OOS Threshold Exceeded (Continued) Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-31
16. MMS: Synchronization Loss OOS Timer Expired

Description
The length of time that the MMS lost synchronization exceeded the sync_time_oos database element threshold.

Possible cause(s)
The following are possible causes for this alarm: 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. The link interface board is faulty. The trunking equipment that provides site-to-site interface is faulty. An MSI board is faulty.
27-32
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-13 1 Synchronization Loss OOS Timer Expired
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... MTLs and/or OMLs... Then... Go to step 5. Go to step 7
68P02901W26-Q 24 May 2004
27-33
Synchronization Loss OOS Timer Expired (Continued) Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
any of the logical links are disable-unlocked... 7 If the device is... busy-unlocked... not busy-unlocked...
27-34
68P02901W26-Q 24 May 2004
18. MMS: Remote Alarm OOS Timer Expired

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 cause(s)
The following are possible causes for this alarm: 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. The link interface board is faulty. The trunking equipment that provides site-to-site interface is faulty. An MSI board is faulty.
68P02901W26-Q 24 May 2004
27-35
Procedure
Procedure 27-14 1 Remote Alarm OOS Timer Expired
27-36
68P02901W26-Q 24 May 2004
Remote Alarm OOS Timer Expired (Continued) Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-37
20. MMS: Red Alarm Daily Threshold Exceeded

Description
The number of times the T1 MMS signal lost synchronization exceeded the red_loss_daily database element threshold.

Possible cause(s)
The following are possible causes for this alarm: The noise present on the receive signal caused the BER to exceed the threshold. The receive T1 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.
27-38
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-15 1 Red Alarm Daily Threshold Exceeded
68P02901W26-Q 24 May 2004
27-39
21. MMS: Red Alarm Hourly Threshold Exceeded

Description
The number of times the T1 MMS signal lost synchronization exceeded the red_loss_hourly database element threshold.

Possible cause(s)
The following are possible causes for this alarm: The noise present on the receive signal caused the BER to exceed the threshold. The receive T1 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.
27-40
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-16 1 Red Alarm Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-41
22. MMS: Red Alarm OOS Threshold Exceeded

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 cause(s)
The following are possible causes for this alarm: The receive T1 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.
27-42
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-17 1 Red Alarm OOS Threshold Exceeded
Determine if this alarm is occurring frequently. If this alarm is... occurring frequently... Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Go to step 2. Then... The fault condition no longer exists. Go to step 4. Reset the MMS. If the alarm clears, go to step 4. If the alarm does not clear, go to step 3.
Determine the state of the MSI.
If the MSI is... busy-unlocked... not busy-unlocked...
Then... Go to step 4. Reset the MSI. If the alarm clears, go to step 4. If the alarm does not clear, send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... Then... The fault condition no longer exists. Go to step 6.
68P02901W26-Q 24 May 2004
27-43
Procedure 27-17
Red Alarm OOS Threshold Exceeded (Continued) Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
27-44
68P02901W26-Q 24 May 2004
23. MMS: Red Alarm OOS Timer Expired

Description
The length of time that the T1 MMS lost synchronization exceeded the red_time_oos database element threshold.
System action

Possible cause(s)
The following are possible causes for this alarm: The receive T1 signal is lost. The receive signal framing words are corrupted. The remote T1 link interface is incompatible.
68P02901W26-Q 24 May 2004
27-45
Procedure
Procedure 27-18 1 Red Alarm OOS Timer Expired
27-46
68P02901W26-Q 24 May 2004
Red Alarm OOS Timer Expired (Continued) Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-47
24. MMS: Modem to NIU Serial Channel Control Link Failure

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-Cellcity, Horizonmicro (M-Cellarena), Horizonmicro2, and Horizoncompact2 units.
System impact
This fault condition is potentially service affecting. If the modem continues to function, calls/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.

Possible cause(s)
The following are possible causes for this alarm: The HDSL modem is not responding and may be faulty. The Serial Channel Link is faulty.
27-48
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-19 Modem to NIU Serial Channel Control Link Failure
68P02901W26-Q 24 May 2004
27-49
25. MMS: HDSL Modem Loop 0 Synch Loss Timer Expired

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.

27-50
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: 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 27-20 1 HDSL Modem Loop 0 Synch Loss Timer Expired
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... Then... Go to step 5. 27-51
68P02901W26-Q 24 May 2004
Procedure 27-20 5
HDSL Modem Loop 0 Synch Loss Timer Expired (Continued)
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... The fault condition no longer exists. No further action is required. For RSL links, an MMS link interface failure occurred. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
27-52
68P02901W26-Q 24 May 2004

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 Network Interface Unit (NIU) that supports an internal HDSL modem.
System impact
The MMS and HDSL modem are placed OOS. HDSL modem loop 2 synch timer expired

Possible cause(s)
68P02901W26-Q 24 May 2004
27-53
Procedure
Procedure 27-21 1 HDSL Modem Loop 1 Synch Loss Timer Expired
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... Then... Go to step 5.
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then...
Determine the state of the logical link devices assigned to the MMS. If...
27-54
68P02901W26-Q 24 May 2004
Procedure 27-21
HDSL Modem Loop 1 Synch Loss Timer Expired (Continued) The fault condition no longer exists. No further action is required. For RSL links, an MMS link interface failure occurred. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
68P02901W26-Q 24 May 2004
27-55
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 Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-56
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-22 1 Master HDSL Modem Loop 0 SNR Daily Threshold Exceeded
68P02901W26-Q 24 May 2004
27-57
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop1 has exceeded the hdsl_snr_daily database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-58
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-23 1 MMS: Master HDSL Modem Loop 1 SNR Daily Threshold Exceeded
68P02901W26-Q 24 May 2004
27-59
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 hdsl_snr_daily database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-60
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-24 1 Slave HDSL Modem Loop 0 SNR Daily Threshold Exceeded
68P02901W26-Q 24 May 2004
27-61
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop1 has exceeded the hdsl_snr_daily database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-62
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-25 1 Slave HDSL Modem Loop 1 SNR Daily Threshold Exceeded
68P02901W26-Q 24 May 2004
27-63
31. MMS: Master HDSL Modem Loop 0 SNR Hourly Threshold Exceeded
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop 0 has exceeded the hdsl_snr_hourly database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-64
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-26 1 Master HDSL Modem Loop 0 SNR Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-65
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop1 has exceeded the hdsl_snr_hourly database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-66
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-27 1 Master HDSL Modem Loop 1 SNR Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-67
33. MMS: Slave HDSL Modem Loop 0 SNR Hourly Threshold Exceeded
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop 0 has exceeded the 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 cause(s)
27-68
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-28 1 Slave HDSL Modem Loop 0 SNR Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-69
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop1 has exceeded the hdsl_snr_hourly database element threshold. This alarm is generated only for an MMS on a Network Interface Unit (NIU) that supports an internal HDSL modem.

Possible cause(s)
27-70
68P02901W26-Q 24 May 2004
Procedure
Procedure 27-29 1 Slave HDSL Modem Loop 1 SNR Hourly Threshold Exceeded
68P02901W26-Q 24 May 2004
27-71
35. MMS: Master HDSL Modem Loop 0 SNR OOS Threshold Exceeded
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. Any additional bytes displayed should be ignored.
27-72
68P02901W26-Q 24 May 2004
Possible cause(s)
Procedure
Procedure 27-30 1 Master HDSL Modem Loop 0 SNR OOS Threshold Exceeded
68P02901W26-Q 24 May 2004
Procedure 27-30 5
Master HDSL Modem Loop 0 SNR OOS Threshold Exceeded (Continued)
27-74
68P02901W26-Q 24 May 2004
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem loop 1 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

68P02901W26-Q 24 May 2004
27-75
Possible cause(s)
Procedure
Procedure 27-31 1 Master HDSL Modem Loop 1 SNR OOS Threshold Exceeded
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... Then... Go to step 5. 68P02901W26-Q 24 May 2004
27-76
Procedure 27-31 5
Master HDSL Modem Loop 1 SNR OOS Threshold Exceeded (Continued)
68P02901W26-Q 24 May 2004
27-77
37. MMS: Slave HDSL Modem Loop 0 SNR OOS Threshold Exceeded
Description
The Signal-to-Noise Ratio (SNR) on the slave 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

27-78
68P02901W26-Q 24 May 2004
Possible cause(s)
Procedure
Procedure 27-32 1 Slave HDSL Modem Loop 0 SNR OOS Threshold Exceeded
68P02901W26-Q 24 May 2004
Procedure 27-32 5
Slave HDSL Modem Loop 0 SNR OOS Threshold Exceeded (Continued)
27-80
68P02901W26-Q 24 May 2004
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem loop 1 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

68P02901W26-Q 24 May 2004
27-81
Possible cause(s)
Procedure
Procedure 27-33 1 Slave HDSL Modem Loop 1 SNR OOS Threshold Exceeded
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS. If logical link devices assigned to the MMS include... RSLs... Then... Go to step 5. 68P02901W26-Q 24 May 2004
27-82
Procedure 27-33 5
Slave HDSL Modem Loop 1 SNR OOS Threshold Exceeded (Continued)
68P02901W26-Q 24 May 2004
27-83
39. MMS: LTU Download Failure

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 cancelled 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.
27-84
68P02901W26-Q 24 May 2004
Possible cause(s)
The firmware may have failed to upgrade due to: EMU did not accept download command. Timeout waiting for message from COM. Download cancelled 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 LTU slot number received. Specified LTU not detected in slot.
Procedure
Procedure 27-34 LTU Download Failure
The operator must analyze the download failure cause, correct the situation and then try to force a download, thereby downloading the correct firmware version/object.
68P02901W26-Q 24 May 2004
27-85
40. MMS: LTU Configuration Failure
40. MMS: LTU Configuration Failure

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. 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 cause(s)
The firmware may have failed to configure for reasons including: Xmodem unable to initialize the COM port.
Procedure
Procedure 27-35 LTU Configuration Failure
The operator must analyze the reconfiguration failure cause, correct the situation and then ins the MSI or force a download again, the success of which clears the alarm.
27-86
68P02901W26-Q 24 May 2004
41. MMS: Connectivity Mismatch Between BSC and RXCDR

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 cause(s)
The following are possible causes for this alarm: The connectivity information at the BSC is incorrect. The connectivity information at the RXCDR is incorrect.
Procedure
Procedure 27-36 1 2 Connectivity Mismatch Between BSC and RXCDR
Display the connectivity information for the BSC and the RXCDR. Compare the BSC and RXCDR connectivity information to the network plan.
68P02901W26-Q 24 May 2004
27-87
Procedure 27-36
Connectivity Mismatch Between BSC and RXCDR (Continued) Then... Correct the connectivity information at the BSC. Correct the connectivity information at the RXCDR.
If the network plan is different than... the connectivity information at the BSC... the connectivity information at the RXCDR...
27-88
68P02901W26-Q 24 May 2004
42. MMS: DSW/DSWX Switching Hardware Required
42. MMS: DSW/DSWX Switching Hardware Required

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.

Possible cause(s)
The following are possible causes for this alarm: KSW and KSWX switching hardware remains enabled in the site or enhanced capacity mode has not been enabled.
Procedure
Procedure 27-37 DSW/DSWX Switching Hardware Required
Use the following procedure to resolve the alarm. Replace all KSW and KSWX switching hardware with DSW and DSWX switching hardware and ensure enhanced capacity mode is enabled.
68P02901W26-Q 24 May 2004
27-89
253. MMS: Critical Alarm Threshold Exceeded

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 will override the stability wait time and bring the MMS back immediately. If the mms_cat_enable parameter is enabled, there is no threshold checking so alarms and clears are processed as they occur.

27-90
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: On-site environmental factors caused the fault. The trunking equipment that provides site-to-site interface are faulty. The link interface board is faulty. The E1/T1 link signal is fading in and out due to faulty cabling or connections to the T43/BIB board. An MSI board is faulty.
Procedure
Procedure 27-38 1 Critical Alarm Threshold Exceeded
In a TTY window, use the disp_mms_ts_usage command to display the logical link devices assigned to the MMS.
68P02901W26-Q 24 May 2004
27-91
Procedure 27-38
Critical Alarm Threshold Exceeded (Continued) Then... Go to step 5. Go to step 6.
If logical link devices assigned to the MMS include... RSLs... MTLs and/or OMLs... 5
Determine the state of each of the SITEs connected by the MMS reporting the alarm. If the SITEs are... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. Go to step 6. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Then... The fault condition no longer exists. No further action is required. This is normal for a standby OML link 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 the appropriate corrective action. Reset the link device, and then go to step 7. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
27-92
68P02901W26-Q 24 May 2004
28
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 28-4 "1. MSI: Hard Reset" on page 28-6 "2. MSI: Watchdog Timer Expired" on page 28-8 "3. MSI: Clock B Signal Loss" on page 28-10 "4. MSI: Clock A Signal Loss" on page 28-11 "5. MSI: Assigned Timeslot Counter Underflow" on page 28-12 "6. MSI: Assigned Timeslot Counter Overflow" on page 28-14 "7. MSI: TDM Parity Error" on page 28-16 "9. MSI: TRAU Frame Synchronization Loss" on page 28-18 "11.- 70. MSI: DSP Channel (0-59) Audit Failure" on page 28-19 "224. MSI: Safe Test Audit Failure" on page 28-22 "231. MSI: TDM Interface Configuration Failure" on page 28-24 "232. MSI: Processor Bus Communication Failure" on page 28-26 "234. MSI: Active Link Connection Failure" on page 28-28 "254. MSI: Device Failure" on page 28-30
Chapter
68P02901W26-Q 24 May 2004
28-1
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
A MSI device may be equipped on one of the FRUs shown in Table 28-1. Table 28-1 FRUs on which the MSI device may be equipped FRU ARENAm (NIU) ARENAm MAC (NIU) ARTESYN NIB FORCE NIB GDP MSI MSI2-CONV MSI2 NIU NIU-EXT-HDSL NIU-EXT-HDSL NIU-HDSL NIUm NIUm-HDSL Description Horizonmicro (M-Cellarena) NIU. Horizoncompact (M-Cellarena Macro) NIU. Artesyn NIB. Force NIB. Generic DSP Processor or Generic Downloadable Processor. Replacement for XCDR. Multiple Serial Interface Board. M-Cell MSI that converts a link from E1 to T1 and from T1 to E1. MSI configurable for E1 or T1 operation. M-Cell Network Interface Unit with one or two links. M-Cell MSI supporting external HDSL modems. M-Cell NIU supporting external HDSL modems. M-Cell NIU supporting integrated HDSL modems. M-Cellmicro NIU with one or two links. M-Cellmicro NIU supporting integrated HDSL modems. Only supported in E1 environment.
28-2
68P02901W26-Q 24 May 2004
Table 28-1
FRUs on which the MSI device may be equipped (Continued) FRU Description M-Cellmicro NIU supporting external HDSL modems. Only supported in E1 environment. Transcoder.
NIUm-EXT-HDSL XCDR
68P02901W26-Q 24 May 2004
28-3
0. MSI: Re-Initialized Unexpectedly

Description
The MSI board unexpectedly re-initialized or reset.

Possible cause(s)
The following are possible causes for this alarm: The front panel reset switch was pressed. The MSI board failed.
Procedure
Procedure 28-1 Re-Initialized Unexpectedly
Wait at least 1 minute after this alarm is reported before continuing with this procedure.
Determine the state of the MSI. If the MSI is... Then...
28-4
68P02901W26-Q 24 May 2004
Procedure 28-1
Re-Initialized Unexpectedly (Continued) The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MSI board. Go to step 2.
busy-unlocked...
not busy-unlocked... 2 3 Reset the MSI.
Determine the state of the MSI after the reset is completed. If the MSI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-5
1. MSI: Hard Reset
1. MSI: Hard Reset

Description
The MSI board reset.

Possible cause(s)
The following are possible causes for this alarm: The front panel reset switch was pressed. A software reset was initiated.
Procedure
Procedure 28-2 Hard Reset
Wait at least 1 minute after this alarm is reported before continuing with this procedure.
28-6
68P02901W26-Q 24 May 2004
1. MSI: Hard Reset
Procedure 28-2
Hard Reset (Continued) The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MSI board. Go to step 2.
busy-unlocked...
Determine the state of the MSI after the reset is completed. If the MSI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-7
2. MSI: Watchdog Timer Expired

Description
The MSI board watchdog timer expired.

Possible cause(s)
The following are possible causes for this alarm: The firmware failed. The processor failed.
Procedure
Procedure 28-3 1 Watchdog Timer Expired
Determine the state of the MSI. If the MSI is... busy-unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, send a field representative to the site to replace the MSI board. Go to step 2.
Determine the state of the MSI after the reset is completed.
28-8
68P02901W26-Q 24 May 2004
Procedure 28-3
Watchdog Timer Expired (Continued) Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
If the MSI is... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
28-9
3. MSI: Clock B Signal Loss
3. MSI: Clock B Signal Loss

Description
The MSI detected a loss of the Clock B signal.

Possible cause(s)
The following are possible causes for this alarm: The Clock B receive circuitry on the MSI board is faulty. The KSWX B clock extender card failed.
Procedure
Procedure 28-4 Reset the MSI. Clock B Signal Loss
If the alarm is... cleared... no cleared...
Then... The fault condition no longer exists. No further action is required. Send a field representative to the field to replace the MSI board.
28-10
68P02901W26-Q 24 May 2004
4. MSI: Clock A Signal Loss
4. MSI: Clock A Signal Loss

Description
The MSI detected a loss of the Clock A signal.

Possible cause(s)
The following are possible causes for this alarm: The Clock A receive circuitry on the MSI board is faulty. The KSWX A clock extender card failed.
Procedure
Procedure 28-5 Reset the MSI. Clock A Signal Loss
If the alarm is... cleared... no cleared...
Then... The fault condition no longer exists. No further action is required. Send a field representative to the field to replace the MSI board.
68P02901W26-Q 24 May 2004
28-11
5. MSI: Assigned Timeslot Counter Underflow

Description
The MSI 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 cause(s)
The following are possible causes for this alarm: The Timeslot Assignment RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane are faulty. Assigned timeslot counter register failed. TDM interface problem.
Procedure
Procedure 28-6 1 Assigned Timeslot Counter Underflow
Determine if this is a recurrence of this alarm. If this is... a recurrence... Then... Send a field representative to the site to replace the MSI board.
28-12
68P02901W26-Q 24 May 2004
Procedure 28-6 2
Assigned Timeslot Counter Underflow (Continued) Go to step 2. Then... The fault condition no longer exists. No further action is required. Go to step 3.
not a recurrence... If MSI is... busy-unlocked... not busy-unlocked... 3 4 Reset the MSI.
Determine the current state of the MSI.
Determine the state of the MSI after the reset is completed. If MSI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-13
6. MSI: Assigned Timeslot Counter Overflow

Description
The MSI has determined that the TDM highway is overused. More switch-bound timeslots are driven onto the TDM bus than were allocated in the assigned timeslot counter register.

Possible cause(s)
The following are possible causes for this alarm: The Timeslot Allocation RAM is faulty. The MCAP interface failed. One or more MCAP data/address lines on the backplane is faulty. Assigned timeslot counter register failed. TDM interface problem.
Procedure
Procedure 28-7 1 Assigned Timeslot Counter Overflow
Determine if this is a recurrence of this alarm. If this is... a recurrence... Then... Send a field representative to the site to replace the MSI board.
28-14
68P02901W26-Q 24 May 2004
Procedure 28-7 2
Assigned Timeslot Counter Overflow (Continued) Go to step 2. Then... The fault condition no longer exists. No further action is required. Go to step 3.
not a recurrence... If MSI is... busy-unlocked... not busy-unlocked... 3 4 Reset the MSI.
Determine the current state of the MSI.
Determine the state of the MSI after the reset is completed. If MSI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-15
7. MSI: TDM Parity Error

Description

Possible cause(s)
The following are possible causes for this alarm: The TDM interface circuitry on the MSI board failed. The TDM bus interface on a KSW/KSWX failed. One or more signals of the TDM bus on the backplane failed.
Procedure
Procedure 28-8 1 TDM Parity Error
Determine the current state of the MSI. If MSI is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 2.
2 3
Reset the MSI. Determine the state of the MSI after the reset is completed.
28-16
68P02901W26-Q 24 May 2004
Procedure 28-8
TDM Parity Error (Continued) Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the MSI board.
If BSP is... busy-unlocked... not busy-unlocked...
68P02901W26-Q 24 May 2004
28-17
9. MSI: TRAU Frame Synchronization Loss
9. MSI: TRAU Frame Synchronization Loss

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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: A device within the communications path between the DRI channel coder and the DSP has been disrupted for more than one second. The following devices may be in the communications path: RSL, MSI, MMS, KSW, XCDR, or GDP. The E1/T1 physical link on which the communication path resides is faulty. A BTS or BSC reset occurred.
Procedure
Procedure 28-9 TRAU Frame Synchronization Loss
Send a field representative to the site to replace the XCDR or GDP with the faulty DSP.
28-18
68P02901W26-Q 24 May 2004
11.- 70. MSI: DSP Channel (0-59) Audit Failure

{4415} Clearing Type: Severity Level: Category: FMIC Major 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 28-2: Table 28-2 Additional information field contents
68P02901W26-Q 24 May 2004
28-19
Byte first
Value (hex) 00 to 1D
Definition The logical channel displayed in the alarm string corresponds to a single physical DSP ID. Physical GDP logical XCDR logical DSP ID channels channels 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 24 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 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 Definition 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.
Byte second
Value (hex) 01, 02, 03
28-20
68P02901W26-Q 24 May 2004
Possible cause(s)
A DSP channel (0-59) on an XCDR or GDP board failed.
Procedure
Procedure 28-10 1 DSP Channel (0-59) Audit Failure
Determine the state of the MSI. If the MSI is... busy-unlockedReason code: No Reason... Busy-Unlocked, Reason code: DSP # Audit Failure... Busy-Unlocked, Reason code: Multiple DSPs OOS... disable-unlocked, Reason code: No Reason... Then... The alarm condition has ceased. No further action is required. A single DSP failed. Go to step 2. More than one DSP failed. Go to step 2. The XCDR or GDP board failed. Go to step 3. Then... The alarm condition has ceased. No further action is required. Go to step 3.
Reset the terrestrial circuits corresponding to the DSP channel(s) that failed. If the terrestrial circuit(s)... are successfully reset... did not successfully reset...
3 4
Reset the MSI. Determine the state of the MSI after the reset is complete. If the MSI is... busy-unlocked... not busy-unlocked... Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the XCDR or GDP board.
68P02901W26-Q 24 May 2004
28-21
224. MSI: Safe Test Audit Failure

Description
The MSI failed a process safe test audit. The process safe test audit verifies the proper operation of internal software processes.

Possible cause(s)
The following are possible causes for this alarm: A software error occurred. A MCAP interface software failure. The MCAP bus is faulty. The MSI board failed. The MSI board lost power.
Procedure
Procedure 28-11 1 Safe Test Audit Failure
Determine the state of the MSI. If the MSI is... busy-unlocked... Then... The alarm condition has ceased. No further action is required.
28-22
68P02901W26-Q 24 May 2004
Procedure 28-11 2 3
Safe Test Audit Failure (Continued) Go to step 2.
not busy-unlocked... Reset the MSI.
Determine the state of the MSI after the reset is complete. If the MSI is... busy-unlocked... not busy-unlocked... Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-23
231. MSI: TDM Interface Configuration Failure

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 cause(s)
The following are possible causes for this alarm: The MSI board failed. A software error occurred The MSI device could not be programmed to the designated timeslot when swapping the TDM highways.
Procedure
28-24
68P02901W26-Q 24 May 2004
Procedure 28-12
TDM Interface Configuration Failure (Continued) The alarm condition has ceased. No further action is required. Go to step 2.
busy-unlocked... not busy-unlocked... 2 3 Reset the MSI.
Determine the state of the MSI after the reset is complete. If the MSI is... busy-unlocked... not busy-unlocked... Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-25
232. MSI: Processor Bus Communication Failure

Description
The MSI board lost the capability to communicate with the GPROC using the MCAP bus.

Possible cause(s)
The following are possible causes for this alarm: The MSI board is removed. The portion of the MSI board that supports the MCAP bus access failed.
Procedure
Procedure 28-13 1 Processor Bus Communication Failure
Determine the state of the MSI. If the MSI is... busy-unlocked... not busy-unlocked... Then... The alarm condition has ceased. No further action is required. Go to step 2.
2 3
Reset the MSI. Determine the state of the MSI after the reset is complete. Then...
28-26
68P02901W26-Q 24 May 2004
Procedure 28-13
Processor Bus Communication Failure (Continued) The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-27
234. MSI: Active Link Connection Failure

Description
The MSI link connection to the active BTP failed.
This alarm is generated only for M-Cell2, M-Cell6, M-Cellmicro, Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarena macro) hardware.

Possible cause(s)
The following are possible causes for this alarm: 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.
28-28
68P02901W26-Q 24 May 2004
Procedure
2 3
Reset the MSI. Determine the state of the MSI after the reset is complete. If the MSI is... busy-unlocked... not busy-unlocked... Then... The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-29
254. MSI: Device Failure

Description
The MSI failed and was placed OOS.

Possible cause(s)
A fault translation process.
Procedure
Procedure 28-15 1 Device Failure
2 3
Reset the MSI. Determine the state of the MSI after the reset is complete. If the MSI is... Then...
28-30
68P02901W26-Q 24 May 2004
Procedure 28-15
Device Failure (Continued) The alarm condition has ceased. No further action is required. Send a field representative to the site to replace the MSI board.
68P02901W26-Q 24 May 2004
28-31
28-32
68P02901W26-Q 24 May 2004
29
MTL alarms
The Message Transfer Link (MTL) alarms are covered in this chapter and include the following procedures: "0. MTL: Signalling Link Failure" on page 29-3 "0. MTL: SL Failure - All Reasons - PM" on page 29-6 "1. MTL: MSC Processor Outage" on page 29-7 "1. MTL: SL Failure - Abnormal FIBR/BSNR - PM" on page 29-8 "2. MTL: SL Failure - Excessive Delay of ACK - PM" on page 29-9 "3. MTL: Link Traffic Too High" on page 29-10 "3. MTL: SL Failure - Excessive Error Rate - PM" on page 29-12 "4. MTL: SL Failure - Excessive Duration of Congestion - PM" on page 29-13 "5. MTL: SL Alignment Failure - PM" on page 29-14 "6. MTL: Number of Signal Units in error - PM" on page 29-16 "7. MTL: SL Number of Negative Acks Received - PM" on page 29-18 "8. MTL: Start of Remote Processor Outage - PM" on page 29-20 "9. MTL: Number of Octets Retransmitted - PM" on page 29-21 "10. MTL: MSUs Discarded due to SL Congestion - PM" on page 29-22 "11. MTL: SL Congestion Events Resulting in Loss of MSUs - PM" on page 29-23 "12. MTL: SL Congestion Indications - PM" on page 29-24
Chapter
68P02901W26-Q 24 May 2004
29-1
Introduction to MTL alarms
Introduction to MTL alarms
MTL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the Message Transfer Link (MTL) device. The MTL device provides the 64 kbit/s connection between the MSC and the BSC. The connection exists on a timeslot on the MMS device. The connection supports the ITU-TSS Signalling System 7 MTP (Message Transfer Part) and SCCP (Signalling Connection Control Part) protocols with the variations specified by GSM.
29-2
68P02901W26-Q 24 May 2004
0. MTL: Signalling Link Failure

Description
An MTL connection between the MSC and BSC failed. No signalling information is passed between the MSC and BSC over the disconnected link.
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 will be raised as the primary alarm, and you will not see a MTL 0 alarm. If MMS thresholds are configured such that the MTL fails before the MMS failure is signalled 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 on 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 - Signalling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS is placed OOS.

Table 29-1 shows the content displayed in additional information field for this alarm.
68P02901W26-Q 24 May 2004
29-3
Table 29-1
Additional information field contents Byte first second Value 00 to FF 0A 00 to FF00 to FF00 to FF Definition MMS timeslot. MMS device type. MMS device identifiers.
thirdfourthfifth
Possible cause(s)
The following are possible causes for this alarm: The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) causing the link failure. The remote congestion timer expired. The MSI acknowledgement timer expired. The sequence numbers may not be synchronized. The Signal Unit Error Rate Monitor (SUERM) detected an excessive signalling error rate. One side of associated MMS is locked, causing the 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 MTL timeslots only, for example when timeslot switching equipment is used, or faulty terminating equipment is present. MMS continues in service while the E1/T1 timeslot 0 is good.
Procedure
Procedure 29-1 1 Signalling Link Failure
Determine if the MSC or RXCDR are rebooting. If... the MSC is rebooting... the RXCDR is rebooting... neither the MSC or RXCDR are rebooting... Then... Wait until the MSC reboot is finished, and then go to step 2. Wait until the RXCDR reboot is finished, and then go to step 3. Go to step 4.
29-4
68P02901W26-Q 24 May 2004
Procedure 29-1 2
Signalling Link Failure (Continued) Then... The fault condition no longer exists. No further action is required. The fault is at the MSC. Contact the MSC to resolve the fault. Then... Go to step 4. Troubleshoot the RXCDR fault.
Determine if the alarm is cleared If the alarm is... cleared... not cleared...
Determine if the RXCDR returned to service. If the RXCDR... returned to service... did not return to service...
4 5
Reset the MTL device. Determine the state of the MTL. If the MTL is... busy-unlocked... not busy-unlocked... Then... The fault condition no longer exists. No further action is required. Go to step 5. Then... Resolve the MMS or MSI alarms. Send a field representative to the site to investigate the E1/T2 links.
Determine if there are alarms for the associated MMS or MSI devices. If there are... MMS or MSI alarms... no MMS or MSI alarms...
68P02901W26-Q 24 May 2004
29-5
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 Signalling Link (SL) has failed for all causes excluding operator interaction using the MMI. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An MSI failed.
Procedure
Procedure 29-2 SL Failure - All Reasons - PM Determine if any MSI alarms are reported.
29-6
68P02901W26-Q 24 May 2004
1. MTL: MSC Processor Outage
1. MTL: MSC Processor Outage

Description
The MSC processor is OOS. This processor failure causes the MTL link to be blocked. When the MTL link is blocked, no user signalling traffic can be exchanged.
This is a service-affecting fault.

Possible cause(s)
The MSC processor for the remote MTP layer 2 link(s) malfunctioned or failed.
Procedure
Procedure 29-3 MSC Processor Outage
Contact the MSC to resolve the problem.
68P02901W26-Q 24 May 2004
29-7
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 Signalling 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). For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The BSN and FSN are being corrupted by the MSC.
Procedure
Procedure 29-4 SL Failure - Abnormal FIBR/BSNR - PM Determine if any BSN and FSN are being corrupted by the MSC.
If the BSN and FSN are... being corrupted by the MSC... not being corrupted by the MSC...
Then... Contact the MSC to resolve the problem, and then clear this alarm. Clear the alarm.
29-8
68P02901W26-Q 24 May 2004
2. MTL: SL Failure - Excessive Delay of ACK - PM
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 Signalling Link (SL) was lost because the system failed to acknowledge a Message Signal Unit (MSU) before an internal Motorola-defined timer expired. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A signalling link failed and an MSU acknowledgement has not been sent.
Procedure
Procedure 29-5 SL Failure - Excessive Delay of ACK - PM Determine if the MSU is being sent by the MSC.
If the MSU is... being sent....
Then... A communication link may be faulty. Resolve the communications link fault, and then clear this alarm. Contact the MSC to resolve the problem, and then clear this alarm.
not being sent...
68P02901W26-Q 24 May 2004
29-9
3. MTL: Link Traffic Too High

Description
Congestion is detected at either the local or remote end of the MTL affecting the flow of the signalling 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 MTL(s). A network congestion problem is probably causing the MTL links to experience signalling 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 signalling 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 cause(s)
High traffic levels on the MTL do not allow enough time for the device driver to process frames.
29-10
68P02901W26-Q 24 May 2004
Procedure
Procedure 29-6 1 Link Traffic Too High
Determine if any MTL devices are OOS. If all MTL devices... are OOS... are not OOS... Then... Go to step 2. Go to step 3. Then... The fault condition no longer exists. Clear the alarm. Resolve the Signalling Link Failure (MTL 0) alarm for the MTL device(s) that do not return to service, and then clear this alarm.
Reset each OOS MTL device. If all MTL devices... return to service... do not return to service...
Clear the alarm. The alarm is due to congestion. The capacity of the current MTL links is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of MTL links.
68P02901W26-Q 24 May 2004
29-11
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 Signalling Link (SL) was lost because the Signal Unit Error Rate Monitor (SUERM) timer expired. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An MSI failed.
Procedure
Procedure 29-7 SL Failure - Excessive Error Rate - PM Determine if any MSI alarms are reported.
29-12
68P02901W26-Q 24 May 2004
4. MTL: SL Failure - Excessive Duration of Congestion - PM
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 Signalling 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 an Message Signal Unit (MSU) are reached. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 29-8 Clear the alarm. The alarm is due to the duration of a congestion condition that exceeds the capacity of the MTL links to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of MTL links. SL Failure - Excessive Duration of Congestion - PM
68P02901W26-Q 24 May 2004
29-13
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 Signalling 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. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: 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.
29-14
68P02901W26-Q 24 May 2004
Procedure
Procedure 29-9 SL Alignment Failure - PM Determine if other alarms associated with the SL were reported.
If other alarms are... reported... not reported...
Then... Resolve the the alarms, and then clear this alarm. Clear the alarm.
68P02901W26-Q 24 May 2004
29-15
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 Signalling Unit (SU) is received on the Signalling Link (SL). For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The BSN and FSN are corrupted. A Multiple Serial Interface (MSI) failed. A Generic Clock (GCLK) failed.
Procedure
Procedure 29-10 Number of Signal Units in error - PM Determine if any MSI alarms are reported.
29-16
68P02901W26-Q 24 May 2004
Procedure 29-10
Number of Signal Units in error - PM (Continued)
68P02901W26-Q 24 May 2004
29-17
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. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The following are possible causes for this alarm: The BSS and the MSC have incompatible software protocols. The BSS has faulty software. The MSC has faulty software.
Procedure
Procedure 29-11 1 SL Number of Negative Acks Received - PM
Determine if the messages between the BSS and the MSC are out of sequence. If the messages are... Then...
29-18
68P02901W26-Q 24 May 2004
Procedure 29-11
SL Number of Negative Acks Received - PM (Continued) The fault condition no longer exists. Clear the alarm. Go to step 2. Then... Contact the MSC to resolve the fault, and then clear the alarm. Send a field representative to the site to resolve the communication link fault, and then clear this alarm.
not out of sequence... out of sequence... 2 If the MSC is... sending the messages... not sending the messages...
Determine if the MSC is sending the messages.
68P02901W26-Q 24 May 2004
29-19
8. MTL: Start of Remote Processor Outage - PM
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 signalling messages cannot be transferred. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A remote processor failed.
Procedure
Procedure 29-12 1 2 3 Start of Remote Processor Outage - PM
Determine which remote processor is reporting the alarm. Initiate problem resolution procedures for the remote processor. After resolving the remote processor fault, clear this alarm.
29-20
68P02901W26-Q 24 May 2004
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 re-transmitted to the MSC due to a request by the MSC. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The BSS retransmitted an excessive number of octets.
Procedure
Procedure 29-13 Number of Octets Retransmitted - PM Determine if the MSC requested the retransmission due to a fault.
If the retransmission was... not due to a fault... due to a fault...
Then... Clear the alarm. Resolve the fault, and then clear this alarm.
68P02901W26-Q 24 May 2004
29-21
10. MTL: MSUs Discarded due to SL Congestion - PM
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 Signalling Link (SL). For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 29-14 MSUs Discarded due to SL Congestion - PM
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.
29-22
68P02901W26-Q 24 May 2004
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 Signalling Link (SL) congestion event which results in Message Signal Units (MSUs) being lost. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 29-15 Clear the alarm. The alarm is due to congestion. The capacity of the current MTL links is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of MTL links. SL Congestion Events Resulting in Loss of MSUs - PM
68P02901W26-Q 24 May 2004
29-23
12. MTL: SL Congestion Indications - PM
12. MTL: SL Congestion Indications - PM

Description
The SL_CONGESTION statistic threshold has been reached. This statistic counts the number of times that a Signalling Link (SL) is congested with a high volume of calls. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
Procedure
Procedure 29-16 Clear the alarm. The alarm is due to congestion. The capacity of the current MTL links is insufficient to handle the signalling traffic. If this alarm recurs, capacity must be increased by the addition of MTL links. SL Congestion Indications - PM
29-24
68P02901W26-Q 24 May 2004
30
OMC-R alarms
The Operations and Maintenance Centre (OMC-R) alarms are covered in this chapter and include the following procedures: 68P02901W26-Q 24 May 2004 "30000. OMC: downloadFailed" on page 30-4 "30001. OMC: uploadFailed" on page 30-6 "30002. OMC: filexferFailed" on page 30-8 "30003. OMC: x25CircuitDown" on page 30-11 "30004. OMC: parserDisconnectedTooLong" on page 30-14 "30005. OMC: NE Response Timeout" on page 30-16 "30006. OMC: NE Error State" on page 30-18 "30007. OMC: PMDisconnectedFromDB" on page 30-20 "30008. OMC: EMDisconnectedFromDB" on page 30-22 "30009. OMC: dbCompressionFailed" on page 30-24 "30010. OMC: Exceeds upper limit disk usage" on page 30-26 "30011. OMC: Exceeds lower limit disk usage" on page 30-29 "30012. OMC: Level 1/2/3 Failure" on page 30-31 "30014. OMC: Database exceeds upper limit" on page 30-33 "30015. OMC: pmProxyDisconnectedFromDB" on page 30-35 "30016. OMC: osiStackError" on page 30-36 "30017. OMC: CSFPdownloadFailed" on page 30-37 "30018. OMC: dbUncompressionFailed" on page 30-39 "30019. OMC: Database exceeds lower limit" on page 30-41 "30020. OMC: VersionQueryFailed" on page 30-43 "30021. OMC: OMC Overloaded with Events" on page 30-49 "30022. OMC: OMC Overloaded, Events Discarded" on page 30-51 "30023. OMC: downloadDisabled" on page 30-53 30-1
Chapter
Chapter 30: OMC-R Alarms
"30024. OMC: CSFPSwapFailed" on page 30-55 "30025. OMC: nmcAgentError" on page 30-57 "30026. OMC: Neighbour statistics table exceeded the configured size. Operator must take action" on page 30-60 "30027. OMC: supplDownloadFailed" on page 30-62 "30064. OMC: Memory usage exceeds upper limit" on page 30-65 "30029. OMC: Active Alarms exceed upper limit of 95%" on page 30-66 "30030. OMC: Received Maximum Corrupt NE Msgs, Closed OML" on page 30-68 "30031. OMC: Resync Timed Out, No Response From NE" on page 30-71 "30032. OMC: Resync Timed Out, All Resync Events Not Received." on page 30-73 "30033. OMC: Cannot create further event logfiles in /usr/gsm/ne_data." on page 30-75 "30035. OMC: Advisory Detected" on page 30-78 "30036. OMC: Recovered Outage Detected" on page 30-79 "30037. OMC: UPS condition" on page 30-80 "30038. OMC: OMC Capacity Ceiling Violation, too many RTFs in MIB." on page 30-82 "30039. OMC: OMC Capacity Ceiling Violation, too many NEs in MIB" on page 30-84 "30050. OMC: Solaris2 Hardware Failure" on page 30-86 "30051. OMC: Corrupt NE File" on page 30-89 "30052. OMC: Corrupt SITE file" on page 30-90 "30060. OMC: noActivityInTimeslot" on page 30-91
30-2
68P02901W26-Q 24 May 2004
Introduction to 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 interface hardware for this system is provided by the OMC-R.
Alarm reporting
OMC-R alarms are reported only by the OMC-R software.
68P02901W26-Q 24 May 2004
30-3
30000. OMC: downloadFailed

Description
A software download from the OMC-R failed.
It is normal to have single DownloadConnectedEvent and DownloadDisconnected messages generated at the the beginning of a download.

Possible cause(s)
The following are possible causes for this alarm: 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.
30-4
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-1 1 2 3 4 Download Failed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the omcaudit logs. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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 the next step. [In a TTY window, use 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 the next step]. 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.
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, etc. 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 using 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-Q 24 May 2004
30-5
30001. OMC: uploadFailed

Description
A software upload to the OMC-R from a BSS failed. Typically, a database object is uploaded.

Possible cause(s)
The following are possible causes for this alarm: The software protocol timed out. The X.25 link failed. 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 30-2 1 2 3 uploadFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the omcaudit logs. Review the alarm and event reports to determine whether this is a software or hardware fault condition.
30-6
68P02901W26-Q 24 May 2004
Procedure 30-2 4
uploadFailed (Continued)
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 X.25 link. If the link remains OOS, go to the next step. [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 the next step.] 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 the next step.
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, etc. 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 using the ins_device command for the (OOS) link, 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-Q 24 May 2004
30-7
30002. OMC: filexferFailed

Clearing Type: Severity Level: Category: Intermittent Major 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. Level123Failed indicating that the X.25 circuit software layers have failed.
Alarm category
This alarm may have been 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 2 hours. However, the time period for file transfer retries is user-configurable.

30-8
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The software protocol timed out. The X.25 link failed. The BSS is too busy to complete a file transfer. The transfer was aborted at the BSS. The BSS was reset.
Procedure
Procedure 30-3 1 2 3 4 filexferFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the omcaudit logs. 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. 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 may be faulty. The multiplexer/Transcoder (RXCDR) connections may be faulty. Check the software processing load on the BSS to determine whether the failure occurred at the BSS.
68P02901W26-Q 24 May 2004
30-9
Procedure 30-3 5
filexferFailed (Continued)
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 the next step. 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 X.25 link. If the link remains OOS, go to the next step. [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 the next step.]
30-10
68P02901W26-Q 24 May 2004
30003. OMC: x25CircuitDown

Clearing Type: Severity Level: Category: FMIC Critical 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
What is a 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 an 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 NE(s). As a result, an X.25 link fails.
Types of X.25 link failures

Link failures are usually 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.
68P02901W26-Q 24 May 2004
30-11
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. Note that Rlogin capability may 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 cause(s)
The following are possible causes for this alarm: 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 30-4 1 2 3 4 x25CircuitDown
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Notify the System Administrator that the X.25 circuit is Out Of Service (OOS). Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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).
30-12
68P02901W26-Q 24 May 2004
Procedure 30-4 5 6
x25CircuitDown (Continued)
Investigate any software faults detected. 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, etc. 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 the OOS link cannot be re-established by using 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.]
68P02901W26-Q 24 May 2004
30-13
30004. OMC: parserDisconnectedTooLong

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 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 cause(s)
The following are possible causes for this alarm: 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 may have been offline, or a system failure occurred.
30-14
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-5 1 2 3 parserDisconnectedTooLong
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the System Administrator to determine when the OMC-R database is reconnected. 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 shown above. 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, go to the next step.
Reconnecting the PM parser manually

After the omc_db_maint command has been executed when reconnecting the PM parser manually: 1. 2. 3. 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, the EM list manager needs to be reconnected. Enter the command, $DBMS_BIN/db disconnect connect em.
68P02901W26-Q 24 May 2004
30-15
30005. OMC: NE Response Timeout

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 (via 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 cause(s)
The following are possible causes for this alarm: 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.
30-16
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-6 1 2 3 NE Response Timeout
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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, use the state command and check the individual links.]
68P02901W26-Q 24 May 2004
30-17
30006. OMC: NE Error State

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 (via 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 cause(s)
The following are possible causes for this alarm: The BSS has an internal protocol error. The Central Authority (CA) did not respond. The BSS site is not fully functional.
30-18
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-7 1 2 3 NE Error State
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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, etc. 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. Use 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.
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, etc. 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 using 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.]
68P02901W26-Q 24 May 2004
30-19
30007. OMC: PMDisconnectedFromDB

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 cause(s)
The parser disconnected from the OMC-R database purposely for the maintenance procedure.
Procedure
Procedure 30-8 1 2 PMDisconnectedFromDB
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition.
30-20
68P02901W26-Q 24 May 2004
Procedure 30-8 3
PMDisconnectedFromDB (Continued)
Contact the System Administrator to determine when the OMC-R database are reconnected.
This alarm is just a warning. If the parser is disconnected too long, a Major alarm, 30004. parserDisconnectedTooLong is generated. 4 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.
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. If the command was not executed, and the OMC-R database maintenance is complete, enter the command shown above. 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, go to the next step.
68P02901W26-Q 24 May 2004
30-21
30008. OMC: EMDisconnectedFromDB

Description
The Event Manager (EM) list manager has been disconnected from the OMC-R database as part of the database maintenance procedure. Note 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 cause(s)
The EM list manager disconnected from the OMC-R database for the maintenance procedure.
Procedure
Procedure 30-9 1 2 EMDisconnectedFromDB
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine the cause(s) of this fault condition.
30-22
68P02901W26-Q 24 May 2004
Procedure 30-9 3
EMDisconnectedFromDB (Continued)
Contact the System Administrator to determine when the OMC-R 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. 4 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.
If the disk space allocated to the raw statistics files is full, uploading of the statistics files stops, and the system may fail. 5 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 shown above. 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, go to the next step.
Reconnecting the PM parser manually

After the omc_db_maint command has been executed when reconnecting the PM parser manually: 1. 2. 3. 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, the EM list manager needs to be reconnected. Enter the command, $DBMS_BIN/db disconnect connect em.
68P02901W26-Q 24 May 2004
30-23
30009. OMC: dbCompressionFailed

Clearing Type: Severity Level: Category: OIC Minor 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 may have been generated in any of the five following alarm categories: Communication. Quality of service. Processing. Equipment. Environmental.

Possible cause(s)
The following are possible causes for this alarm: 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.
30-24
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-10 1 2 3 dbCompressionFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the System Administrator to archive or remove log files from the system. Verify that the log file maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administration (68P02901W19).. Review disk space allocations to determine whether there is a disk space shortage. Determine where the disk space shortage is located. If there is not enough disk space, perform the following maintenance: Remove old event log files. Remove old software loads. Remove old backup databases.
4 5
Restart the upload after clearing out enough disk space for the compression and upload.
68P02901W26-Q 24 May 2004
30-25
30010. OMC: Exceeds upper limit disk usage

Clearing Type: Severity Level: Category: FMIC Critical Quality of Service
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 configuration file $OMC_TOP/config/global/FM_audit.CNFG, which can be modified by the System Administrator. 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 filenames 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.
30-26
68P02901W26-Q 24 May 2004

Possible cause(s)
The following are possible causes for this alarm: 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 30-11 1 2 3 4 Exceeds upper limit disk usage
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the System Administrator to archive or remove log files from the system. Check the disk usage of the /usr partition, or the partition to which the error relates. Verify that the log file maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administration (68P02901W19) 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%. Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed). If there is not enough disk space, perform the following maintenance: Remove old event log files. Remove old software loads. Remove old backup databases.
5 6 7
68P02901W26-Q 24 May 2004
30-27
Procedure 30-11 8 9
Exceeds upper limit disk usage (Continued)
Check the upper threshold of the following disk partitions to verify that they are no longer exceeded: 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 7 days down to 2 days old may be removed. But, 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 - Nothing is done. 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 Note the disk partition filenames differ from the names above. 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.
30-28
68P02901W26-Q 24 May 2004
30011. OMC: Exceeds lower limit disk usage

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 configuration file $OMC_TOP/config/global/FM_audit.CNFG, which can be modified by the System Administrator.

Possible cause(s)
The lower limit threshold of disk usage was lowered in the FM_audit.CNFG file.
Procedure
Procedure 30-12 1 2 3 4 Exceeds lower limit disk usage
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the System Administrator to archive or remove log files from the system. Check the disk usage of the /usr partition, or the partition to which the error relates. Verify that the log file maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administration (68P02901W19)
68P02901W26-Q 24 May 2004
30-29
Procedure 30-12 5 6 7
Exceeds lower limit disk usage (Continued)
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%. Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed). If there is not enough disk space, perform the following maintenance: Remove old event log files. Remove old software loads. Remove old backup databases.
8 9
Check the lower threshold of the following disk partitions to verify that they are no longer exceeded: 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.
30-30
68P02901W26-Q 24 May 2004
30012. OMC: Level 1/2/3 Failure

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 cause(s)
The following are possible causes for this alarm: The physical link was removed. (For example, the link may have been cut accidently.) There is a problem with the X.25 port indicated by the alarm.
68P02901W26-Q 24 May 2004
30-31
The X.25 hardware failed.
Procedure
Procedure 30-13 1 2 Level 1/2/3 Failure
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition. Check current event logs for other alarms which may indicate a link failure, communication failure, a hardware (board) failure, etc. If alarms are related, consult this manual for alarm descriptions and fault resolution procedures.
Check the X.25 hardware and link cabling into the System Processor computer. If any hardware or cabling is faulty, replace it. If not, continue to the next step.
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).
30-32
68P02901W26-Q 24 May 2004
30014. OMC: Database exceeds upper limit

Description
The upper threshold of database usage have been exceeded by the System Processor at the OMC-R. The database is completely 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 cause(s)
The following are possible causes for this alarm: 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.
68P02901W26-Q 24 May 2004
30-33
Procedure
Procedure 30-14 1 2 3 Database exceeds upper limit
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the database usage in the System Processor database to which the error relates. Verify that the database maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administrator (68P02901W19). Raise the value of the threshold database limit (if lower than 90%). Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed). Review database space allocations to determine whether there is a space shortage. Determine where the shortage is located. Check the upper/lower thresholds of the databases to verify that they are no longer exceeded.
4 5 6 7
30-34
68P02901W26-Q 24 May 2004
30015. OMC: pmProxyDisconnectedFromDB
30015. OMC: pmProxyDisconnectedFromDB

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 cause(s)
The PM proxy database was disconnected for administrative purposes.
Procedure
Procedure 30-15 1 2 pmProxyDisconnectedFromDB
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the OMC-R System Administrator to reconnect the PM proxy to the database.
68P02901W26-Q 24 May 2004
30-35
30016. OMC: osiStackError
30016. OMC: osiStackError

Clearing Type: Severity Level: Category: OIC Minor Communication
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 cause(s)
The OSI machine failed.
Procedure
Procedure 30-16 1 2 osiStackError
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the OMC-R System Administrator to check the OSI machine and investigate any hardware or software failures.
30-36
68P02901W26-Q 24 May 2004
30017. OMC: CSFPdownloadFailed

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 the beginning of a download.

Possible cause(s)
The following are possible causes for this alarm: The software protocol contained errors. The X.25 link failed. 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.
68P02901W26-Q 24 May 2004
30-37
Procedure
Procedure 30-17 1 2 3 4 CSFPdownloadFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the omcaudit logs. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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 the next step. [In a TTY window, use 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 the next step.] 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.
If it appears 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, etc. 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 using 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, the field representative should check for board failures that may relate to the functioning of the failed link.]
30-38
68P02901W26-Q 24 May 2004
30018. OMC: dbUncompressionFailed

Clearing Type: Severity Level: Category: OIC Minor 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 may have been generated in any of the five following alarm categories: Communication. Quality of service. Processing. Equipment. Environmental.

68P02901W26-Q 24 May 2004
30-39
Possible cause(s)
The following are possible causes for this alarm: 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 a uncompression/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 30-18 1 2 3 4 dbUncompressionFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine the cause of this fault condition. Check the backup database(s) for the NE on which the activate_db utility is running. If there is not enough disk space, perform the following maintenance: Remove old event log files. Remove old software loads. Remove old backup databases.
Restart the upload after clearing out enough disk space for the compression and upload.
30-40
68P02901W26-Q 24 May 2004
30019. OMC: Database exceeds lower limit

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

68P02901W26-Q 24 May 2004
30-41
Possible cause(s)
The following are possible causes for this alarm: 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 30-19 1 2 3 Database exceeds lower limit
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Check the database usage in the System Processor database to which the error relates. Verify that the database maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administration (68P02901W19). Raise the value of the threshold database limit (if lower than 90%). Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed). Review database space allocations to determine whether there is a space shortage. Determine where the shortage is located. Check the upper/lower thresholds of the databases to verify that they are no longer exceeded.
4 5 6 7
30-42
68P02901W26-Q 24 May 2004
30020. OMC: VersionQueryFailed

Clearing Type: Severity Level: Category: OIC/FMIC Critical/Major Processing
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.
Definitions
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 Signalling 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.
When is a version query initiated?

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.
Note that version queries are not always generated because of a fault condition.
68P02901W26-Q 24 May 2004
30-43
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 via 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 cause(s)
The following are possible causes for this alarm: 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.
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).
30-44
68P02901W26-Q 24 May 2004
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

Procedure 30-20 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.
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 on the Load Mgmt icon. Check the BSS software load versions and CSFP software load versions displayed.
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 info from the pull-down menu. A report showing the current database level number is displayed.
68P02901W26-Q 24 May 2004
30-45
Procedure 30-20 3
Procedure for FMIC - Major alarms (Continued)
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. [Use the disp_version command at the MMI prompt to determine what software load versions currently reside at that BSS.]
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... current software load version for a specific BSS is correct... and that specific BSS... current software load version does not match the (BSS) software version held at the OMC-R... then, before the alarm clears, the operator must... download the current (BSS) software version from the OMC-R to the BSS. The same BSS version must exist at both the OMC-R and the BSS. download the current CSFP software load version from the OMC-R to the BSS.
current CSFP software load version for a specific BSS exists and is correct...
current CSFP software load version does not exist,because that BSC is not yet initialized...orbecause the BSC is initialized, but does not have a CSFP In Service ...
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

Procedure 30-21 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.
30-46
68P02901W26-Q 24 May 2004
Procedure 30-21
Procedure for OIC - Major/Critical alarms (Continued)
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 on the Load Mgmt icon. Check the BSS software load versions and CSFP software load versions displayed.
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 info 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 shown.
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. [Use the disp_version command at the MMI prompt to determine what software load versions currently reside at that BSS.]
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 OIC version query failure fault condition. If the OMC-R... and that specific BSS... then, before clearing the alarm the operator must ... install the correct software load version at the OMC-R. If necessary, upload the associated database from the BSS. Then, from the Navigation Window, INS the OML to ensure that the correct software load is set at the BSS. install the correct CSFP software load version at the OMC-R. Perform a CSFP download in order to synchronize the databases.
current software load version for a specific BSS is incorrect (or does not exist)...
current software load version does not match the current (BSS) software load version held at the OMC-R...
See Note 1 following this table. current CSFP software load version for a specific BSS is incorrect (or does not exist)... current CSFP software load version exists, and, lanloading has been detected... To check for lanloading, review the output from the disp_version command. If BSP code version 1.0.0.0 is displayed, lanloading was used to load the BSS.
68P02901W26-Q 24 May 2004
30-47
If the OMC-R...
and that specific BSS...
then, before clearing the alarm the operator must ... download the correct BSS database from the OMC-R to the BSS. upload the correct BSS database from the BSS to the OMC-R. download the correct CSFP database to the BSS.
current database level number within the dbroot directory for a specific BSS is correct... current database level number within the dbroot directory for a specific BSS is incorrect... current CSFP database level number within the dbroot directory for a specific BSS is correct... See Note 2 following this table.
current database level number is incorrect... current database level number is correct... current CSFP database level number is incorrect...
Notes
The following items apply to the previous table.
Note 1 - 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.
Note 2 - This mismatch generally occurs during a system migration.
30-48
68P02901W26-Q 24 May 2004
30021. OMC: OMC Overloaded with Events

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 cause(s)
The following are possible causes for this alarm: 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-Q 24 May 2004
30-49
Procedure
Procedure 30-22 1 2 3 OMC Overloaded with Events
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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, consult the manual, Operating Information: GSM System Operation (68P02901W14). 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.
30-50
68P02901W26-Q 24 May 2004
30022. OMC: OMC Overloaded, Events Discarded

Clearing Type: Severity Level: Category: OIC Critical Processing
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 cause(s)
The following are possible causes for this alarm: 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-Q 24 May 2004
30-51
Procedure
Procedure 30-23 1 2 3 OMC Overloaded, Events Discarded
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine whether this is a software or hardware fault condition. 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, consult the manual, Operating Information: GSM System Operation (68P02901W14). 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.
30-52
68P02901W26-Q 24 May 2004
30023. OMC: downloadDisabled

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 to be generated at the the beginning of a download.

Possible cause(s)
The following are possible causes for this alarm: The download may have been disabled manually because the X.25 link was being reconfigured on the System Processor computer. The download may have been automatically disabled because a conventional download to an NE was aborted.
68P02901W26-Q 24 May 2004
30-53
Procedure
Procedure 30-24 1 2 3 downloadDisabled
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine what caused this fault condition. 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 the next step. If not, go to the next step.
4 5 6
Check to see if another operator has disabled downloading or has aborted a conventional download to an NE. When downloading can be restored, enable it through the Load Management GUI. Re-initiate the software download.
30-54
68P02901W26-Q 24 May 2004
30024. OMC: CSFPSwapFailed

Clearing Type: Severity Level: Category: OIC Major Processing
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 cause(s)
The following are possible causes for this alarm: 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 30-25 1 2 CSFPSwapFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine what caused this fault condition.
68P02901W26-Q 24 May 2004
30-55
Procedure 30-25 3 4
CSFPSwapFailed (Continued)
Check the OMC-R connection to the BSS involved in the swap. Check the BSS (software) for which the swap is being attempted to determine why the swap may have been rejected or timed out.
30-56
68P02901W26-Q 24 May 2004
30025. OMC: nmcAgentError

Clearing Type: Severity Level: Category: OIC Critical Processing/Communication
Description
A Network Management Centre (NMC) mediation device (agent) has encountered either an Open Systems Interconnection (OSI) error(s) 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 cause(s)
The following are possible causes for this alarm: 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 may not have been 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 may have been broken; or the address of the remote processor may have been incorrect. A Common Management Information Service Element (CMISE) service error may have been received: data received by remote processor may have been 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.
68P02901W26-Q 24 May 2004
30-57
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. 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 30-26 1 2 3 nmcAgentError
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Review the alarm and event reports to determine the cause(s) of this alarm. 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... (timer) time out... Then... Inform the Network Manager/administrator of the no response condition. Determine which is faulty: the host application or the machine. Inform the Network Manager/administrator of the communications error condition. Determine where the processor errors are occurring. Determine where the internal software errors in the OSI processor occurred: review the omcaudit file. Inform the Network Manager/administrator of the no information available condition.
communications error between two processors...
CMISE service error...
30-58
68P02901W26-Q 24 May 2004
If the reason for the error is... no information available... maximum number of retries...
Then... Inform the Motorola field representative of the condition. Inform the Network Manager/administrator of the communications error condition.
68P02901W26-Q 24 May 2004
30-59
30026. OMC: Neighbour statistics table exceeded the configured size. Operator must take action
30026. OMC: Neighbour statistics table exceeded the configured size. Operator must take action
Clearing Type: Severity Level: Category: OIC Critical Quality of Service
Description
The ErrorId related to the parser has detected that the number of statistics contained in the Neighbour Statistics table at the OMC-R exceeded the established limit.
The actual limit for the Neighbour Statistics table is set by way of the environmental variable, PM_MAX_NEIGHBOURS. The default value for this variable is 880.

Possible cause(s)
The neighbour statistics being generated within the system have become excessive.
30-60
68P02901W26-Q 24 May 2004
Maintenance Information: Alarm Handling at the OMC-R 30026. OMC: Neighbour statistics table exceeded the configured size. Operator must take action
Procedure
Procedure 30-27 Neighbour statistics table exceeded the configured size. Operator must take action 1 2 In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. 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: 4 Remove some neighbour statistics from the Neighbour Statistics table. Disable the neighbour statistics currently being uploaded.
Execute Performance Management (PM) database maintenance: Disconnect the parser from the database. Delete statistics from the Neighbour Statistics (nbr_statistics) table. Reconnect the parser to the database so that the system can resume collecting PM statistics.
68P02901W26-Q 24 May 2004
30-61
30027. OMC: supplDownloadFailed

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 may have been aborted by the operator, or a COLR may have been 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 cause(s)
The following are possible causes for this alarm: X.25 errors The X.25 board has been shutdown. The X.25 data cannot be read. The X.25 data cannot be written to.
30-62
68P02901W26-Q 24 May 2004
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.
68P02901W26-Q 24 May 2004
30-63
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 30-28 1 2 3 supplDownloadFailed
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Confirm that the X.25 link reconfiguration exists at the OMC-R, at the Packet Switch, and at the BSS. After determining which error reason was displayed in the alarm message, consult the fault isolation/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.
30-64
68P02901W26-Q 24 May 2004
30064. OMC: Memory usage exceeds upper limit
30064. OMC: Memory usage exceeds upper limit

Clearing Type: Severity Level: Category: FMIC Critical Quality of service
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.
Additional Information field

Possible cause(s)
The following are possible causes for this alarm: Memory usage by the System Processor has reached maximum capacity. The upper limit threshold of memory usage was lowered.
Procedure
Procedure 30-29 1 2 3 Memory usage exceeds upper limit
Check the memory usage on the System Processor. Monitor the alarm, and if it does not clear, carry out further investigations to see which processes are using too much memory. Raise the value of the threshold memory usage limit.
68P02901W26-Q 24 May 2004
30-65
30029. OMC: Active Alarms exceed upper limit of 95%

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 condition(s) causing them have been resolved. The active OIC alarms must be removed from the list by the operator after the fault condition(s) 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 cause(s)
The number of active alarms on the OMC-R active alarm list exceeded 95%.
30-66
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-30 1 2 Active Alarms exceed upper limit of 95%
OMC-R System Administrator: Determine why so many alarms are arriving at the OMC-R. When there are large numbers of similar alarms, consider throttling or blacklisting them.
68P02901W26-Q 24 May 2004
30-67
30030. OMC: Received Maximum Corrupt NE Msgs, Closed OML

Clearing Type: Severity Level: Category: OIC Critical 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
What is a 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 an 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 NE(s) thereby creating a link failure.
Types of X.25 link failures

Link failures are usually 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.
30-68
68P02901W26-Q 24 May 2004
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. Note that 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/connection to the NE fails.

Possible cause(s)
The Event Interface has received the maximum number of corrupt NE messages.
Procedure
Procedure 30-31 1 2 Received Maximum Corrupt NE Msgs, Closed OML
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. 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, etc. Monitor this fault condition. Investigate any potentially related software faults detected. If the alarm is automatically cleared, discontinue fault isolation. If the alarm does not clear, notify the System Administrator that the X.25 circuit is Out Of Service (OOS).
68P02901W26-Q 24 May 2004
30-69
Procedure 30-31 5
Received Maximum Corrupt NE Msgs, Closed OML (Continued)
Check the operational and administrative state of the the X.25 connections by opening an Rlogin window for the System Processor. Continue with the following: Rlogin to the System Processor as omcadmin using the command rlogin omc_splat -1 omcadmin. Determine the status of each of the X.25 ports (currently in use) by using the command /opt/SUNWconn/bin/x25stat -1 <portname>. (See the example after this procedure.)
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. If the fault condition persists after receiving the assistance of MCSC, send a field representative to the site to investigate.
Example
If the command, x25stat -1 port1a is entered, the output generated should be similar to the following:
PER LINK STATISTICS FOR X25 ---------------------------Link : 0 State : Connected and resolved DXE -----------------------------------------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.
30-70
68P02901W26-Q 24 May 2004
30031. OMC: Resync Timed Out, No Response From NE

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 cause(s)
The following are possible causes for this alarm: The Network Element may be too busy. The em_main may be overloaded with activity or alarms.
Procedure
Procedure 30-32 1 2 Resync Timed Out, No Response From NE
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. 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.
68P02901W26-Q 24 May 2004
30-71
Procedure 30-32 3 4
Resync Timed Out, No Response From NE (Continued)
Monitor this fault condition. Investigate any potentially related software faults detected. If the alarm clears, discontinue fault isolation. 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. [Use 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.
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.
Check the omcaudit 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 omcaudit file for error strings. For example, the operator could search for the strings: Error, error, failed, etc. Find the specific time within the omcaudit 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 omcaudit 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.
30-72
68P02901W26-Q 24 May 2004
30032. OMC: Resync Timed Out, All Resync Events Not Received.
Clearing Type: Severity Level: Category: OIC Major Processing
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 cause(s)
The Resync Controller may be faulty.
Procedure
Procedure 30-33 1 2 Resync Timed Out, All Resync Events Not Received.
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. 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.
68P02901W26-Q 24 May 2004
30-73
Procedure 30-33 3
Resync Timed Out, All Resync Events Not Received. (Continued)
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.
Check the omcaudit 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 omcaudit file for error strings. For example, the operator could search for the strings: Error, error, failed, etc. Find the specific time within the omcaudit 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 omcaudit file) using either of the methods above, continue to the next step.
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.
30-74
68P02901W26-Q 24 May 2004
30033. OMC: Cannot create further event logfiles in /usr/gsm/ne_data.

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 the existing thresholds. For more information, consult 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. Note that the ne_data disk partition is not intended to be used to store files belonging to individual users.
Where filenames 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-Q 24 May 2004 30-75

Possible cause(s)
The following are possible causes for this alarm: The directory /usr/gsm/ne_data has been allowed to fill up. The number of event log files present (in the directory) may be 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 may be excessive. The current event traffic may be so excessive that the number of event logs being created is higher than allowed causing the directory to fill up.
Procedure
Procedure 30-34 1 2 3 4 Cannot create further event logfiles in /usr/gsm/ne_data.
In the Alarm window, check the error reason field in the alarm message to determine the cause(s) of this alarm. Contact the System Administrator to archive or remove log files from the system. Check the disk usage of the /usr partition, or the partition to which the error relates. Verify that the log file maintenance procedures currently in operation comply with those recommended in the manual, Operating Information: OMC-R System Administration (68P02901W19). Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed).
30-76
68P02901W26-Q 24 May 2004
Procedure 30-34 6
Cannot create further event logfiles in /usr/gsm/ne_data. (Continued)
If there is no available disk space, perform the following maintenance: Remove old event log files. Remove old software loads. Remove old backup databases. Remove core files. Remove .tar files if not being stored for a significant purpose.
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-Q 24 May 2004
30-77
30035. OMC: Advisory Detected
30035. OMC: Advisory Detected

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 subsequently resurface as more serious fault conditions.

Possible cause(s)
Not applicable.
Procedure
Procedure 30-35 1 2 Advisory Detected
Monitor the reported condition. Investigate any potential faults.
30-78
68P02901W26-Q 24 May 2004
30036. OMC: Recovered Outage Detected
30036. OMC: Recovered Outage Detected

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 subsequently resurface as more serious fault conditions.

Possible cause(s)
Not applicable.
Procedure
Procedure 30-36 1 2 Recovered Outage Detected
Monitor the reported condition. Investigate any potential faults.
68P02901W26-Q 24 May 2004
30-79
30037. OMC: UPS condition

Clearing Type: Severity Level: Category: FMIC Clear/Major/Critical Equipment
Description
Support for the Uninterruptable 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 30-1. Table 30-1 OMC: UPS condition alarm severities. Alarm OMC now powered by mains OMC now powered by the UPS UPS battery low condition signalled Clear Major Critical Severity

Possible cause(s)
The following are possible causes for this alarm: The OMC-R is now being powered by the UPS. The UPS battery is running low.
30-80
68P02901W26-Q 24 May 2004
Procedure
Procedure 30-37 UPS condition
Inform the network manager or administrator of the condition.
68P02901W26-Q 24 May 2004
30-81
30038. OMC: OMC Capacity Ceiling Violation, too many RTFs in MIB.
Clearing Type: Severity Level: Category: Intermittent Major/Critical Processing
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. Any additional bytes displayed should be ignored.
Possible cause(s)
The number of RTFs on the network exceeds the number permitted by the license.
Procedure
Procedure 30-38 OMC Capacity Ceiling Violation, too many RTFs in MIB. Check the number of RTFs on the MIB using the script: /usr/gsm/current/sbin/Count_NEs_and_RTFs
30-82
68P02901W26-Q 24 May 2004
Procedure 30-38
OMC Capacity Ceiling Violation, too many RTFs in MIB. (Continued)
If... The number of RTFs on the MIB exceeds the license... The number of RTFs on the MIB does not exceed the license...
Then... Reduce the number of RTFs in the MIB. Check the installation of the license and reinstall the license if necessary. See the manual, Installation and Configuration: OMC-R Clean Install (68P02901W47). If there are problems with the license contact Motorola.
68P02901W26-Q 24 May 2004
30-83
30039. OMC: OMC Capacity Ceiling Violation, too many NEs in MIB
Clearing Type: Severity Level: Category: Intermittent Critical Processing
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. Any additional bytes displayed should be ignored.
Possible cause(s)
The number of NEs on the network exceeds the number permitted by the license.
Procedure
Procedure 30-39 OMC Capacity Ceiling Violation, too many NEs in MIB Check the number of NEs on the MIB using the script: /usr/gsm/current/sbin/Count_NEs_and_RTFs
30-84
68P02901W26-Q 24 May 2004
Procedure 30-39
OMC Capacity Ceiling Violation, too many NEs in MIB (Continued)
If... The number of NEs on the MIB exceeds the license... The number of NEs on the MIB does not exceed the license...
Then... Reduce the number of NEs in the MIB. Check the installation of the license and reinstall the license if necessary. See Installation and Configuration: OMC-R Clean Install Installation and Configuration: OMC-R Clean Install (68P02901W47). If there are problems with the license contact Motorola.
68P02901W26-Q 24 May 2004
30-85
30050. OMC: Solaris2 Hardware Failure

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/config/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 on-site. After the Solaris 2 hardware resumes functioning, this alarm is automatically cleared from the system.
FM audit definition and frequency

Note that 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.
30-86
68P02901W26-Q 24 May 2004
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. Table 30-2 Additional information field contents Description of the faulty Solaris 2 hardware component The CPU, where (x) is the number of the CPU. The hard disk, where (x) is the number of the disk. 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.
Text displayed in the Additional Info field cpu(x) (in SBUS slot (y)) is DOWN d(x) is DOWN hih(x) is DOWN
68P02901W26-Q 24 May 2004
30-87
Possible cause(s)
The following are possible causes for this alarm: 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 30-40 1 Solaris2 Hardware Failure
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. 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. 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

Note that 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
30-88
68P02901W26-Q 24 May 2004
30051. OMC: Corrupt NE File
30051. OMC: Corrupt NE File

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 cause(s)
The NE.MAP file is corrupt.
Procedure
Procedure 30-41 Corrupt NE File Manually inspect the file and verify the file format is correct.
If the file format is... correct... incorrect...
Then... Clear the alarm. Perform the appropriate corrective action and then clear the alarm.
68P02901W26-Q 24 May 2004
30-89
30052. OMC: Corrupt SITE file
30052. OMC: Corrupt SITE file

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 cause(s)
The SITE.MAP file is corrupt.
Procedure
Procedure 30-42 Corrupt SITE file Manually inspect the file and verify the file format is correct.
If the file format is... correct... incorrect...
Then... Clear the alarm. Perform the appropriate corrective action and then clear the alarm.
30-90
68P02901W26-Q 24 May 2004
30060. OMC: noActivityInTimeslot

Clearing Type: Severity Level: Category: OIC Warning Quality of service
Description
The Call Success Monitor has detected one or more timeslots on an RTF where there is no traffic.

Possible cause(s)
One or more timeslots within the RTF are not processing traffic: neither call originations nor handovers.
Procedure
Procedure 30-43 1 2 3 noActivityInTimeslot
Identify the RTF with sleeping timeslots. Determine which timeslots are sleeping. Clear the alarm manually.
68P02901W26-Q 24 May 2004
30-91
30-92
68P02901W26-Q 24 May 2004
31
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 31-3 "1. OML: FRMR-Frames - PM" on page 31-4 "2. OML: Expiration of N2 - PM" on page 31-5
Chapter
68P02901W26-Q 24 May 2004
31-1
Introduction to OML alarms
Introduction to OML alarms
OML alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the Operation and Maintenance Link (OML) alarms.
31-2
68P02901W26-Q 24 May 2004
0. OML: Invalid Received Frames - PM
0. OML: 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/LAPD link. For further information, consult the OML statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An invalid frame was received on the X.25/LAPD link.
Procedure
Then... Send a field representative to the site to check the X.25/LAPD link and take the appropriate corrective action. Clear the alarm.
68P02901W26-Q 24 May 2004
31-3
1. OML: FRMR-Frames - PM
1. OML: 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. For further information, consult the OML statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A frame reject message was received on the X.25/LAPD link.
Procedure
31-4
68P02901W26-Q 24 May 2004
2. OML: 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. For further information, consult the OML statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The X.25/LAPD link failed due to a hardware fault or repair action.
Procedure
68P02901W26-Q 24 May 2004
31-5
31-6
68P02901W26-Q 24 May 2004
32
PBUS alarms
The Processor Bus (PBUS) alarms are covered in this chapter and include the following procedures: "254. PBUS: Device Failure" on page 32-3
Chapter
68P02901W26-Q 24 May 2004
32-1
Introduction to PBUS alarms
Introduction to PBUS alarms
PBUS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with 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)/Transcoder (XCDR). Generic Clock (GCLK). Kiloport Switch (KSW). Digital Radio Interface (DRI)/DRI extended Memory (DRIM).
PBUS alarms apply only to BSC and InCell equipment.
32-2
68P02901W26-Q 24 May 2004
254. PBUS: Device Failure

Description
The PBUS device is placed OOS due to a LANX card failure.

Possible cause(s)
The LANX card performing arbitration for the MCAP bus failed.
Procedure
68P02901W26-Q 24 May 2004
32-3
32-4
68P02901W26-Q 24 May 2004
33
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 33-3 "1. PCU: PCU Audit Failure" on page 33-5 "2. PCU: Cell Mapping Failure " on page 33-7
Chapter
68P02901W26-Q 24 May 2004
33-1
Introduction to PCU alarms
Introduction to PCU alarms
PCU alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the Packet Control Unit (PCU) device.
33-2
68P02901W26-Q 24 May 2004
0. PCU: Last GSL Failed

Description
The last GSL between the PCU and the BSC failed.
System action
The PCU is placed OOS.

Possible cause(s)
The following are possible causes for this alarm: A protocol error occurred. A PCU processor board (PICP or PSP) is faulty.
68P02901W26-Q 24 May 2004
33-3
Procedure
Procedure 33-1 1 Last GSL Failed
Determine if there are any GSL alarms associated with the PCU that reported the alarm. If there are... no GSL alarms... GSL alarms... Then... Go to step 2. Resolve the GSL alarms. After resolving the GSL alarms, go to step 3.
2 3
Reset the PCU. Determine if the alarm cleared. If the alarm.. cleared... did not clear... Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to replace the PCU processor board.
33-4
68P02901W26-Q 24 May 2004
1. PCU: PCU Audit Failure

Clearing Type: Severity Level: Category: OIC Critical 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.

The contents of the additional information field are shown in Table 33-1. Table 33-1 Additional information field contents Byte first second Value (hex) 00 to FF 00 to FF Definition This byte specifies the number of messages sent. This byte specifies the number of messages received.
Possible cause(s)
The following are possible causes for this alarm: A PCU protocol error occurred. The GSLs between the PCU and the BSC are faulty, but remain in service.
68P02901W26-Q 24 May 2004
33-5
Procedure
Procedure 33-2 1 PCU Audit Failure
Determine if there are any GSL alarms associated with the PCU that reported the alarm. If there are... no GSL alarms... GSL alarms... Then... Go to step 2. Resolve the GSL alarms. After resolving the GSL alarms, go to step 3. Then... Send a field representative to the site to replace the DPROC/MPROC processor board. Go to step 3.
Determine if this is a recurrence of this alarm. If this is... a recurrence...
not a recurrence... 3 4 Clear the alarm. Reset the PCU.
33-6
68P02901W26-Q 24 May 2004
2. PCU: Cell Mapping Failure

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 cause(s)
Communication failure between BSC & PCU.
Procedure
Procedure 33-3 Cell Mapping Failure
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 & BSC or the PCU is failing without the GSLs going OOS. 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 PCUs emon prompt.
68P02901W26-Q 24 May 2004
33-7
33-8
68P02901W26-Q 24 May 2004
34
PPB alarms
The PPB alarms are covered in this chapter and include the following procedures: "0. PPB: PCI Bridge Failure " on page 34-3
Chapter
68P02901W26-Q 24 May 2004
34-1
Introduction to PPB alarms
Introduction to PPB alarms
PPB alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the PPB device.
34-2
68P02901W26-Q 24 May 2004
0. PPB: PCI Bridge Failure

Description
The bridge used to communicate to the redundant side of the cage has failed.

Possible cause(s)
Possible hardware/software processor problems.
Procedure
Procedure 34-1 Replace PPB board. PCI Bridge Failure
68P02901W26-Q 24 May 2004
34-3
34-4
68P02901W26-Q 24 May 2004
35
PSP alarms
The PCU System Processor (PSP) alarms are covered in this chapter and include the following procedures: "0. PSP: Communication Failure" on page 35-3 "22. PSP: SWFM Indication" on page 35-5 "39. PSP: Software Failure" on page 35-6 "239. PSP: Process Safe Test Audit Failure" on page 35-7
Chapter
68P02901W26-Q 24 May 2004
35-1
Introduction to PSP alarms
Introduction to PSP alarms
PSP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the 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 35-1. Table 35-1 PSP FRUs FRU Motorola MPROC Unknown MPROC Description A Motorola master system processor board. A generic master system processor board.
35-2
68P02901W26-Q 24 May 2004
0. PSP: Communication Failure

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 will 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(s)
The following are possible causes for this alarm: Undetectable software failure. MPROC removed from cage. HSC removed from cage. MPROC board failure. HSC board failure.
68P02901W26-Q 24 May 2004
35-3
Procedure
Procedure 35-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).
35-4
68P02901W26-Q 24 May 2004
22. PSP: SWFM Indication
22. PSP: SWFM Indication

Description
The system has detected a software processing error (SWFM) for a PSP.
Possible cause(s)
Procedure
68P02901W26-Q 24 May 2004
35-5
39. PSP: Software Failure
39. PSP: Software Failure

Description
This alarm indicates that the PSP has experienced an unrecoverable software error.

Possible cause(s)
A critical software error.
Procedure
Procedure 35-3 1 2 Software Failure
Reset the PSP. Determine the state of the PSP after the reset is completed. If the PSP is... busy-unlocked... Then... The alarm was probably caused by a software error. Contact a Motorola representative to resolve the software error. Send a field representative to the site to replace the GPROC board.
35-6
68P02901W26-Q 24 May 2004
239. PSP: Process Safe Test Audit Failure

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.

03
Possible cause(s)
The following are possible causes for this alarm: The PSP board is faulty. The PSP software being audited is faulty.
68P02901W26-Q 24 May 2004
35-7
Procedure
Determine the error code displayed in the additional information field. If the error code is... 2... 0, 1, or 3... Then... Contact a Motorola representative to resolve the software error. Go to step 2. Then... The fault condition no longer exists. No further action is required. Send a field representative to the site to attempt a manual reset, and if not successful, replace the PSP board.
Determine the state of the PSP after the PCU reset is completed. If the PSP is ... busy-unlocked... not busy-unlocked...
When the audit failure reason is 2 (when the board is not reset), the alarm can be cleared by manually resetting the PSP on/off hours as long as GPRS service is being properly provided.
35-8
68P02901W26-Q 24 May 2004
36
RSL alarms
The Radio Signalling Link (RSL) alarms are covered in this chapter and include the following procedures: "0. RSL: Invalid Received Frames - PM" on page 36-3 "1. RSL: FRMR-Frames - PM" on page 36-4 "2. RSL: Expiration of N2 - PM" on page 36-5 "10. RSL: Link Disconnected" on page 36-6 "11. RSL: LAPD Protocol Error" on page 36-14 "13. RSL: LAPD Protocol Error Threshold Exceeded" on page 36-17 "14. RSL: Link Audit Failure" on page 36-19 "15. RSL: Too Many LAPD Protocol Errors " on page 36-21
Chapter
68P02901W26-Q 24 May 2004
36-1
Introduction to RSL alarms
Introduction to RSL alarms
RSL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the Radio Signalling 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.
36-2
68P02901W26-Q 24 May 2004
0. RSL: Invalid Received Frames - PM
0. RSL: 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 LAPD link. For further information, consult the RSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An invalid frame was received on the LAPD link.
Procedure
Then... Send a field representative to the site to check the LAPD link, and take the appropriate corrective action. Clear the alarm.
68P02901W26-Q 24 May 2004
36-3
1. RSL: FRMR-Frames - PM
1. RSL: FRMR-Frames - PM
Description
The FRMR statistic threshold has been reached. This statistic counts the number of the frames on the LAPD link that were rejected because the frames were not correctable. For further information, consult the RSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A frame reject message was received on the LAPD link.
Procedure
36-4
68P02901W26-Q 24 May 2004
2. RSL: Expiration of N2 - PM
2. RSL: 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. For further information, consult the RSL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The LAPD link failed due to a hardware fault or repair action.
Procedure
68P02901W26-Q 24 May 2004
36-5
10. RSL: Link Disconnected

Description
An RSL disconnected on the MMS. No signalling information between the BSC and the BTS is passed over the disconnected link.
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 will be 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 signalled 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 on 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 than most. 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. 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.
36-6
68P02901W26-Q 24 May 2004
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. See Alarm handling priority in the Alarm Handling chapter for details.
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). And the following alarm is generated: 0. Site: Last RSL Link Failure. Note that 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.
See the CCITT Blue Book, Q.921 for details regarding the Data Link Layer.

Table 36-1 shows the content displayed in the additional information field for this alarm. Table 36-1 Additional information field contents Byte first second third fourth fifth sixth seventh Value 00 to FF 00 to FF 01 to 1F 0A 00 to FF 00 to FF 00 to FF Definition The first two bytes are the reason codes:00 = Normal disconnect. C6 = XBL guard timer expired. MMS timeslot. MMS device type. MMS device identifiers.
Possible cause(s)
The following are possible causes for this alarm: A normal link disconnect. An XBL guard timer expired.
68P02901W26-Q 24 May 2004
36-7
One side of associated MMS is locked, causing the 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 RSL timeslots only, for example when timeslot switching equipment is used, or faulty terminating equipment is present. MMS continues in service while the E1/T1 timeslot 0 is good. A GSL guard timer expired.
BSC-BTS Site configurations

For fault isolation and diagnostics, it is critical to determine which BSC-to-remote BTS site configuration is present at the site receiving the alarm(s).
Possible configurations: 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) configuration

A star (or spoke) consists of a number of BTS sites. Each BTS site is connected directly to the BSC by E1/T1 links. A minimum of one E1/T1 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 10 MMSs. The Star/spoke is treated as multiple open-ended daisy chains with one BTS site per chain.
Loop Configuration: opened or closed

A loop chain consists of a number of BTSs connected together in a chain with at least a single E1/T1 link between each remote BTS site. Multiple E1/T1 links (MMSs) can be used to support additional traffic capacity or redundancy. A single BTS site can have a maximum of 10 MMSs. There are two types of loop configurations: open and closed.
Opened 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.
36-8
68P02901W26-Q 24 May 2004
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 Configuration
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/T1 link between each remote BTS site. Multiple E1/T1 links (MMSs) can be used to support additional traffic capacity or redundancy. A single BTS site can have a maximum of 10 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, note 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/T1 link is used between each site. Every remote BTS site in the network must be equipped with at least one RSL. The RSL carries signalling 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 signalling 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. Note the following rules that 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. )
68P02901W26-Q 24 May 2004
36-9
Procedure
Procedure 36-4 Link Disconnected Wait at least 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.
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/T1 links that carries this RSL. 2 Determine whether this alarm has recurred repeatedly and consistently. If this alarm... has not recurred repeatedly over a short period of time... has recurred repeatedly over a short period of time... 3 Then... Monitor this fault condition. If this alarm recurs consistently over the next 10-30 minutes. Continue to step 3. The RSL is not functioning and may be faulty. Continue to step 3.
In a TTY window, use 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... busy and unlocked... not busy and unlocked... Then... The alarm condition has ceased. Further fault resolution is not required. The RSL is OOS. Attempt to re-establish the link by using the ins_device command for the RSL. If the RSL does not return to service, continue with the next step. Otherwise, discontinue fault resolution.
36-10
68P02901W26-Q 24 May 2004
Procedure 36-4 4
Link Disconnected (Continued)
Use the disp_equipment command to display the active equipment associated with the RSL and PATH devices. Use the disp_equipment RSL command for the RSL that generated this alarm; record the unique path identifier for the RSL device. (Note that the first RSL device ID displayed represents the terminating site of the path that the suspect RSL is using.) Use 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.
From the BSC, in a TTY window, use the state command to check the operational and administrative status of the PATH. If the PATH is... busy and unlocked... Then... Check the alarm report log for excessive alarms related to this fault condition. Go to the next step outside this table. The PATH is OOS. If there is an MMS failure alarm, go to the next step outside this table. If there is no MMS alarm, it is probable that the serial data transmission carrier is operating at a reduced quality. Go to the last step of this procedure.
Determine whether the MMS and/or SITE devices specified for the PATH device are Out Of Service (OOS). From the BSC, use 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... INS... and the SITE is... INS... Then... It is probable that the data path is operating at a reduced quality. Attempt to re-establish the link by using 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. It is possible that a device has failed. Check alarm reports and event logs for a site failure; consult alarm pages in this manual.
INS...
OOS...
68P02901W26-Q 24 May 2004
36-11
Procedure 36-4 OOS...
Link Disconnected (Continued) INS... It is possible that a hardware device has failed. Check alarm reports and event logs for an MMS failure; consult alarm pages in this manual. Determine which T43/BIB interconnect board is associated with the suspect MMS. (Refer to site-specific documentation.) It is possible that both devices have failed. Check alarm reports and event logs for MMS and site failures; consult 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.
OOS...
OOS...
Determine whether the BSC-related MMS in a Busy-Unlocked device state? If the MMS is... busy and unlocked... Then... It is possible that there is an equipment failure at the failed BTS. From the BSC, use 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.) Is 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 last step. Are the related MMS(s) Busy-Unlocked? Check for an MSI failure; consult alarm pages in this manual. 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.) 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). Note: 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.
36-12
68P02901W26-Q 24 May 2004
Procedure 36-4 8
Link Disconnected (Continued)
Send a field representative to the site in order to determine the quality of the link. Consult this manual for fault resolution procedure(s) regarding any alarm(s) related to this RSL fault condition. 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/T1 temperature sensor. If the E1/T1 sensor cable is faulty, it could be responsible for taking the RSL Out Of Service (OOS).
68P02901W26-Q 24 May 2004
36-13
11. RSL: LAPD Protocol Error

Description
The RSL detected a LAPD protocol error due to a problem on one of the T1/E1 links. Calls may be lost.

The contents of the additional information field are shown in Table 36-2. Table 36-2 Additional information field contents Byte first second third fourthfifthsixth Value 01 to 1F 00 to FF 0A 00 to FF00 to FF00 to FF Definition MMS timeslot. LAPD error code MMS device type. MMS device identifiers.
Possible cause(s)
The LAPD Error code included in the additional information field corresponds to a possible cause for the alarm, as shown in Table 36-3. Table 36-3 LAPD error codes
36-14
68P02901W26-Q 24 May 2004
Error code 0 or 4
Description The timeslot assignments are not correct. The connection to the physical link may have a different protoco l.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. The connection is invalid. The DACS link is physically connected to the wrong line. 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 of the media is faulty. The remote side of the link connection sent I-frames before the link was established. A physical link outage affected the local to remote direction.
2 or 3 5 or 8
6 7 or 9
Procedure
Determine if this is a recurrence of this alarm. If this is... a recurrence of this alarm... not a recurrence of this alarm... Then... Go to step 2. Clear the alarm.
Determine the state of the MMS identified in the additional information field.
If the MMS is... busy and unlocked...
Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Review the Alarm/Event window for an MMS alarm and initiate the appropriate alarm handling procedures.
Further tests
If the above procedure is not sufficient to isolate the problem, perform the following actions.
68P02901W26-Q 24 May 2004
36-15
First carry out link quality test, not just in TS0 but the whole link (32 Timeslots), use the standard link test patterns, run this end to end ensure, that over a 24 hour period, Frequency, BER and Code errors jitter and wander are within specifications. Use an LAPD Q.921 protocol tester on the RSL timeslot but bear in mind that we have a larger PDU length. To isolate RSL alarms first use ECT to determine where most impact can be found and target the big numbers first. Check the recent stats history for RSL and the link. Monitor link quality over an extended period using suitable test equipment and ensure the link(s) meets the specifications for GSM (ITU-T G.703/G.704) and correct any shortcomings. Monitor link and RSL stats and ECT to see if any changes made have had any affect. If alarms/stats are at an acceptable level move on to tackle the smaller alarms numbers. If not use LAPD protocol analyzer to track down the source of any RSL alarms.
36-16
68P02901W26-Q 24 May 2004
13. RSL: LAPD Protocol Error Threshold Exceeded

Description
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 36-4. The code indicates where the alarm was reported. Table 36-4 Additional information field contents Definition The alarm is reported by the BSC. The alarm is reported by the BTS
Value (hex) 01 05
Possible cause(s)
68P02901W26-Q 24 May 2004
36-17
Procedure
Procedure 36-6 1 LAPD Protocol Error Threshold Exceeded
Determine the state of the RSL device. If the RSL is... busy and unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Continue to step 2. Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 3.
not busy and unlocked... 2 If the RSL... returns to service...
Attempt to restore the RSL device to service.
In a TTY window, use the disp_equipment RSL command for the RSL that generated this alarm; record the unique path identifier for the RSL device. (Note that the first RSL device ID displayed represents the terminating site of the path that the suspect RSL is using.) Determine the state of the MMS device identified in step 3. If the MMS is... busy and unlocked... Then... The E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 5.
36-18
68P02901W26-Q 24 May 2004
14. RSL: Link Audit Failure

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.

The contents of the additional information field are shown in Table 36-5. Table 36-5 Additional information field contents Byte first second third fourth fifth sixth Value 01 to 1F 00 to FF00 to FF00 to FF 00 to FF 00 to FF Definition MMS timeslot. MMS device identifiers. Number of messages received. Number of messages sent.
Possible cause(s)
The following are possible causes for this alarm: A link failure previously undetected by the system. An RSL performance problem.
68P02901W26-Q 24 May 2004
36-19
Procedure
Procedure 36-7 Link Audit Failure Check the number of received replies.
The number of replies is... Zero... Not zero...
Then... Return the RSL to service. Send a field representative to the site to determine the quality of the link and take appropriate corrective action.
36-20
68P02901W26-Q 24 May 2004
15. RSL: Too Many LAPD Protocol Errors

Description

The contents of the additional information field are shown in Table 36-5. Table 36-6 Additional information field contents Byte first second third thru sixth Value 01 to 1F 00 to FF 00 to FF 00 to FF 00 to FF Definition MMS timeslot. LAPD fault code. MMS device id.
Possible cause(s)
4 or more LAPD Protocol errors were received within 1 second indicating major problems with the RSL link.
Procedure
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.
68P02901W26-Q 24 May 2004
36-21
Procedure 36-8
Too Many LAPD Protocol Errors (Continued)
A field representative may need to visit the site to determine the quality of the link and adjust/correct/replace it as necessary. Consult Alarm Handling at the OMC customer documentation. Investigate the RSL further if this keeps happening
36-22
68P02901W26-Q 24 May 2004
37
SBUS alarms
The Serial Bus (SBUS) alarms are covered in this chapter and include the following procedures: "254. SBUS: Device Failure" on page 37-3
Chapter
68P02901W26-Q 24 May 2004
37-1
Introduction of SBUS alarms
Introduction of SBUS alarms
SBUS alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the 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.
37-2
68P02901W26-Q 24 May 2004
254. SBUS: Device Failure

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 cause(s)
The following are possible causes for this alarm: 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-Q 24 May 2004
37-3
Procedure
37-4
68P02901W26-Q 24 May 2004
38
SITE alarms
The SITE alarms are covered in this chapter and include the following procedures: 68P02901W26-Q 24 May 2004 "0. SITE: Last RSL Link Failure" on page 38-4 "2. SITE: BSC Detected MCU to MCU Communication Failure" on page 38-12 "3. SITE: Active Multiplexer 0 Loopback Failure" on page 38-15 "4. SITE: Standby Multiplexer 0 Loopback Failure" on page 38-17 "5. SITE: Active Multiplexer 1 Loopback Failure" on page 38-19 "6. SITE: Standby Multiplexer 1 Loopback Failure" on page 38-21 "7. SITE: Active Multiplexer 2 Loopback Failure" on page 38-23 "8. SITE: Standby Multiplexer 2 Loopback Failure" on page 38-25 "9. SITE: Active Local FOX Failure" on page 38-27 "10. SITE: Standby Local FOX Failure" on page 38-29 "11. SITE: Active Remote FOX 0 Failure" on page 38-31 "12. SITE: Standby Remote FOX 0 Failure" on page 38-33 "13. SITE: Active Remote FOX 1 Failure" on page 38-35 "14. SITE: Standby Remote FOX 1 Failure" on page 38-37 "15. SITE: Active Remote FOX 2 Failure" on page 38-39 "16. SITE: Standby Remote FOX 2 Failure" on page 38-41 "17. SITE: 16Kbps Switching Hardware Required" on page 38-43 "18. SITE: MIX Board (Slot 18) Communication Failure " on page 38-45 "19. SITE: Unequipped GPROC has Entered the LAN" on page 38-46 "20. SITE: Unequipped GPROC Has Left the LAN" on page 38-49 "21. SITE: No Clock References Available" on page 38-53 "22. SITE: Active Alarm List Full" on page 38-56 "23. SITE: EMU Modem Card Failure " on page 38-58 38-1
Chapter
Chapter 38: SITE Alarms
"24. SITE: Site Reset Request" on page 38-59 "25. SITE: External Power Booster Amplifier 1 Failure" on page 38-63 "26. SITE: External Power Booster Amplifier 2 Failure" on page 38-65 "27. SITE: External Power Booster Failure" on page 38-67 "28. SITE: Database Configuration and Arena Hardware Mismatch" on page 38-69 "29. SITE: EMU Download Failure " on page 38-72 "30. SITE: NVM Board Failure" on page 38-75 "31. SITE: Failure of PCMCIA Card 1 on NVM Board" on page 38-76 "32. SITE: Last GBL Failed" on page 38-77 "33. SITE: BSSGP Status Message Received from the SGSN" on page 38-79 "34. SITE: Erroneous BSSGP Message Received from the SGSN" on page 38-80 "35. SITE: Network Service Status Message Received from the SGSN" on page 38-81 "36. SITE: Erroneous Network Service Message Received from the SGSN" on page 38-82 "37. SITE: No NS-VC Block Acknowledgement from the SGSN" on page 38-83 "38. SITE: No NS-VC Unblock Acknowledgement from the SGSN" on page 38-84 "39. SITE: No NS-VC Alive Acknowledgement from the SGSN" on page 38-85 "40. SITE: No NS-VC Reset Acknowledgement from the SGSN" on page 38-87 "41. SITE: Last NS-VC for the PCU failed" on page 38-89 "42. SITE: Last TRAU GDS Failed" on page 38-91 "43. SITE: Last PRP DPROC Failed" on page 38-92 "44. SITE: 50% of the PCU NS-VCs Failed" on page 38-93 "45. SITE: No Signalling BVC Reset Acknowledgement from the SGSN" on page 38-94 "46. SITE: DSW Switching Hardware Required at Site" on page 38-95
38-2
68P02901W26-Q 24 May 2004
Introduction to SITE alarms
Introduction to SITE alarms
SITE alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the 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-Cellmicro).
BSU-BTS alarms
The alarms contained in this chapter which apply to the BSU-based BTS cabinets are generated for the Last Radio Signalling 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), Fibre Multiplexer (FMUX) and the active Fibre 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 back-up 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-Q 24 May 2004
38-3
0. SITE: Last RSL Link Failure

Description
This alarm indicates that the last Radio Signalling 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 as well as diverse. See a description of each of the various contexts in which this alarm can be received on the next page under the section, Alarm contexts.
This is a service-affecting fault condition. If this alarm recurs repeatedly, the functionality of the RSL link carrying the DISC packet must be investigated. Use the CCITT Blue Book, Q.921 as a source for details regarding the Data Link Layer when pursuing this information.

38-4
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The site may have been in the process of resetting. All RSL connections to the BTS may have been Out Of Service (OOS) due to link or equipment problems. The last (functioning) RSL at a site may have been 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 alarm(s).
Possible configurations: BSC-to-BTS

There are three possible types of BSC-to-remote BTS site configurations: The Star (spoke) configuration. The Loop (opened or closed) configuration. The Fork configuration.
Star (spoke) configuration

A star (or spoke) consists of a number of BTS sites; each of which is connected directly to the BSC by E1/T1 links (MMSs). A minimum of one 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 10 MMSs. The Star/spoke is treated as multiple open-ended daisy chains with one BTS site per chain.
Loop Configuration: opened or closed

A loop chain consists of a number of BTSs connected together in a chain with at least a single E1/T1 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 10 MMSs. There are two types of loop configurations: open and closed.
Opened 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-Q 24 May 2004
38-5
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 Configuration
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/T1 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 10 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, note 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. And therefore, which particular E1/T1 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 signalling 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 signalling 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. Note the following rules that 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.
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. )
38-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 38-1 Last RSL Link Failure
Wait at least 10 minutes before continuing with this procedure. The site may be in the process of resetting.
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, continue to the next step.
If this alarm recurs, there may be a quality of service problem on one of the E1/T1 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 is... busy and unlocked... not busy and unlocked... 3 Then... The alarm condition has ceased. Further fault isolation is not required. Continue to the next step.
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 the next step. 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. 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. From the BSC, use the state command to check the operational and administrative states of the PATH device. If the PATH is... Then...
68P02901W26-Q 24 May 2004
38-7
Procedure 38-1
Last RSL Link Failure (Continued) Check the alarm log for the MMS alarms related to 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 continue to the next step. 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. Send a field representative to the site to continue the fault diagnosis.
The E1/T1 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. 7 Determine whether the MMS or SITE devices specified for the PATH device are OOS. From the BSC, use 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 is... INS... and the SITE is... INS... Then... 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 the next step outside this table. If the RSL link(s) does not resume normal service, go to the next step outside this table.
38-8
68P02901W26-Q 24 May 2004
Procedure 38-1 INS...
Last RSL Link Failure (Continued) 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. Consult the appropriate chapter in this manual for procedures to resolve the fault condition. 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.) Consult the appropriate chapter in this manual for procedures to resolve the fault condition. 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. Consult the appropriate chapter in this manual for procedures to resolve the fault condition.
OOS...
INS...
OOS...
OOS...
Continue fault diagnosis by checking the operational device state of the MMS. If the MMS is... Then...
68P02901W26-Q 24 May 2004
38-9
Procedure 38-1
Last RSL Link Failure (Continued) It is possible that there is an equipment failure at 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. Are the MMS(s) in a Busy-Unlocked state? If yes, check for MMS device alarms. Consult the MMS alarms chapter in this manual for fault resolution procedures. It is possible that a device has failed. Before 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.) Consult the MMS alarms chapter in this manual for fault resolution procedures. After completing fault diagnostics, check the next entry in this table.
38-10
68P02901W26-Q 24 May 2004
Procedure 38-1
Last RSL Link Failure (Continued) It is possible that the equipment has failed. Check the 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 (GCLKs, etc) failures. Consult this manual for fault resolution procedures for the alarms being displayed. After completing fault resolution from the OMC-R, go to the next step.
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) still does 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, etc, 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 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-Q 24 May 2004
38-11
2. SITE: BSC Detected MCU to MCU Communication Failure

Clearing Type: Severity Level: Category: FMIC Minor Communication
Description
This alarm is generated when the Base Station Controller (via 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. Note that 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.

38-12
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The fibre optic cable connecting the two BTPs (MCUs) may have been faulty. The fibre optic cable connecting the two BTPs (MCUs) may have been incorrectly connected. The (MSW) port (on a BTP (MCU)) that connects to the fibre optic cable may have been faulty. The software that assigns a BTP (MCU) to the role of Master BTP may have been faulty.
Procedure
Procedure 38-2 1 2 BSC Detected MCU to MCU Communication Failure
Review the alarm report/event logs to determine the site where this alarm is occurring. 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 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. Select the PATH device assigned to the BTP designated as the master, and select the lock option. 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. Determine whether the standby BTP has come into service. If the standby BTP (MCU) has ... Then...
4 5
68P02901W26-Q 24 May 2004
38-13
Procedure 38-2
BSC Detected MCU to MCU Communication Failure (Continued) 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 representative to the site to 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.
come into service...
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.
38-14
68P02901W26-Q 24 May 2004
3. SITE: Active Multiplexer 0 Loopback Failure

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 Horizonmacro and Horizonmacro2 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 multiplexer(s). 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 fibre cable connecting the two multiplexers is damaged or broken.
68P02901W26-Q 24 May 2004
38-15

Possible cause(s)
The following are possible causes for this alarm: The multiplexer on either side/end of the fibre optic cable may have been faulty. The multiplexer may have been removed from the backplane. A backplane connector may have been damaged. The fibre optic cable may have been faulty.
Procedure
Procedure 38-3 1 2 Active Multiplexer 0 Loopback Failure
Review the alarm report/event logs to determine the site where this alarm is occurring. 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 all of the DRIs (TCUs) connected to the multiplexer. They should all be Out Of Service (OOS). Send a field representative to the site to investigate a potential hardware fault within the multiplexer or the multiplexer link.
38-16
68P02901W26-Q 24 May 2004
4. SITE: Standby Multiplexer 0 Loopback Failure

Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot 0 of the standby MCU card frame, or its corresponding remote multiplexer, is disconnected. For Horizonmacro 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.
In both cases, the alarm is generated only if one or more in-service DRIs are connected to the multiplexer(s).
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 standby MCU card frame is disconnected from the backplane. The remote multiplexer board linked to the local standby multiplexer is disconnected from the backplane. The fibre cable connecting the two multiplexers is damaged or broken.

68P02901W26-Q 24 May 2004
38-17
Possible cause(s)
The following are possible causes for this alarm: The multiplexer on either side/end of the fibre optic may have been faulty. The multiplexer may have been removed from the backplane. A backplane connector may have been damaged. The fibre optic link may have been faulty.
Procedure
Procedure 38-4 1 2 Standby Multiplexer 0 Loopback Failure
38-18
68P02901W26-Q 24 May 2004

Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot 1 of the master MCU card frame, or its corresponding remote multiplexer, is disconnected. For Horizonmacro and Horizon II macro controlling cabinets, the alarm is generated when an integrated multiplexer on the master BTP, or its corresponding remote multiplexer, is disconnected.
TCU connection
68P02901W26-Q 24 May 2004
38-19

Possible cause(s)
Procedure
38-20
68P02901W26-Q 24 May 2004

Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot 1 of the standby MCU card frame, or its corresponding remote multiplexer, is disconnected. For Horizonmacro 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.
In both cases, the alarm is generated only if one or more in-service DRIs are connected to the multiplexer(s).
TCU connection

68P02901W26-Q 24 May 2004
38-21
Possible cause(s)
Procedure
38-22
68P02901W26-Q 24 May 2004

Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot 2 of the master MCU card frame, or its corresponding remote multiplexer, is disconnected. For Horizonmacro controlling cabinet, the alarm is generated when an 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.
TCU connection
68P02901W26-Q 24 May 2004
38-23

Possible cause(s)
Procedure
38-24
68P02901W26-Q 24 May 2004

Description
For an M-Cell controlling cabinet, this alarm is generated when the multiplexer residing in slot 2 of the standby MCU card frame, or its corresponding remote multiplexer, is disconnected. For Horizonmacro 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 multiplexer(s).
TCU connection

68P02901W26-Q 24 May 2004
38-25
Possible cause(s)
Procedure
38-26
68P02901W26-Q 24 May 2004
9. SITE: Active Local FOX Failure

Description
This alarm indicates that the M-Cell Fibre 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
Provided that 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.

68P02901W26-Q 24 May 2004
38-27
Possible cause(s)
The following are possible causes for this alarm: The FOX board may have been faulty. The FOX board may have been removed from the backplane. A backplane connector may have been damaged.
Procedure
Procedure 38-9 1 2 Active Local FOX Failure
Review the alarm report/event logs to determine the site where this alarm is occurring. 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.
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 all of the DRIs (TCUs) connected to the FOX. They should all be Out Of Service (OOS). Send a field representative to the site to replace the FOX board.
38-28
68P02901W26-Q 24 May 2004
10. SITE: Standby Local FOX Failure

Description
This alarm indicates that the M-Cell Fibre 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).
This alarm is valid only for M-Cell2 and M-Cell6 sites.
TCU connection
Provided that 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 cause(s)
68P02901W26-Q 24 May 2004
38-29
Procedure
Procedure 38-10 Standby Local FOX Failure
Send a field representative to the site to replace the FOX board.
38-30
68P02901W26-Q 24 May 2004
11. SITE: Active Remote FOX 0 Failure

Description
This alarm indicates that the remote M-Cell Fibre Optic Extender (FOX) board connected to the master MCU has failed. The connection is maintained using Fibre 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
Provided that 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. Also, note that all TCUs (INS) connected to the FOX is automatically disabled if this fault condition occurs.

68P02901W26-Q 24 May 2004
38-31
Possible cause(s)
Procedure
Procedure 38-11 Active Remote FOX 0 Failure
Send a field representative to the site(s) to check the backplane connection, and/or replace any of the following: the FMUX in slot 0, and/or the FOX board.
38-32
68P02901W26-Q 24 May 2004
12. SITE: Standby Remote FOX 0 Failure

Description
This alarm indicates that the remote M-Cell Fibre Optic Extender (FOX) board connected to the standby MCU has failed. The connection is maintained using Fibre 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
Provided that 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 1 is disconnected from the backplane.

68P02901W26-Q 24 May 2004
38-33
Possible cause(s)
Procedure
Procedure 38-12 Standby Remote FOX 0 Failure
38-34
68P02901W26-Q 24 May 2004

Description
TCU connection

68P02901W26-Q 24 May 2004
38-35
Possible cause(s)
Procedure
38-36
68P02901W26-Q 24 May 2004

Description
TCU connection

68P02901W26-Q 24 May 2004
38-37
Possible cause(s)
Procedure
38-38
68P02901W26-Q 24 May 2004

Description
TCU connection
This is a service-affecting fault condition. Also, note that all TCUs (INS) connected to the FOX is automatically be disabled if this fault condition occurs.

68P02901W26-Q 24 May 2004
38-39
Possible cause(s)
Procedure
38-40
68P02901W26-Q 24 May 2004

Description
TCU connection

68P02901W26-Q 24 May 2004
38-41
Possible cause(s)
Procedure
38-42
68P02901W26-Q 24 May 2004
17. SITE: 16Kbps Switching Hardware Required

Description
This alarm indicates that one of 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. (Note that Kilo-bits per second has two abbreviations: kbps and kbit/s.)
Switching capability
A Timeslot Switch (TSW) is not capable of 16 kbit/s switching for a BTS that is either equipped to use Radio Signalling Links (RSLs) or is configured to support dynamic allocation. Only a KSW can provide 16 kbit/s switching. Neither InCell TSW boards nor M-Cell switching hardware provide 16 kbit/s switching.
This is a service affecting fault condition. No calls can be completed at a BTS for which this alarm has been generated.

68P02901W26-Q 24 May 2004
38-43
Possible cause(s)
The following are possible causes for this alarm: 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 with16 kbit/s RSLs. The BTS site is configured for dynamic allocation, but the master cage does not contain the switching hardware to support it.
Procedure
Procedure 38-17 1 2 16Kbps Switching Hardware Required
Review the alarm report/event logs to determine the site where this alarm is occurring. From the Navigation Tree window, select the Display Menu and 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.
Consult the manual, Technical Description: BSS Command Reference (68P02901W23) for information regarding command entry.
38-44
68P02901W26-Q 24 May 2004
18. SITE: MIX Board (Slot 18) Communication Failure
18. SITE: MIX Board (Slot 18) Communication Failure

Description
The MIX board is not detected by the polling software or responds with a bad board identifier.

Possible cause(s)
The following are possible causes for this alarm: 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 38-18 MIX Board (Slot 18) Communication Failure
Insert a good MIX Board into the MIX slot (Slot 18).
68P02901W26-Q 24 May 2004
38-45
19. SITE: Unequipped GPROC has Entered the LAN

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. Note that a GPROC device must be fully equipped before it can be used by the system.
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 on-site maintenance action is occurring; or an operator or on-site 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. Any additional bytes displayed should be ignored.
38-46
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: The GPROC may not have been properly inserted into the correct slot. The GPROC may have been inserted into an incorrect slot within a cage. The GPROC may have been inserted into a CAGE before being equipped. The GPROC may have been reset before being equipped. A CAGE may not have been equipped before it was added to the LAN. The GPROC may have recently been unequipped after entering the LAN. The GPROC may be faulty.
Procedure
Procedure 38-19 1 2 Unequipped GPROC has Entered the LAN
Refer to the alarm message report. Check the Additional Info in the alarm output to determine the cage and slot numbers of the unequipped GPROC. 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. If this alarm has been generated for... A GPROC that is intentionally unequipped... A GPROC that is unexpectedly unequipped... Then... No fault resolution is required. Consider blacklisting this alarm until the GPROC is equipped. It is possible that the wrong cage 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. 3 From the Navigation Tree window, select the Display Menu and from it the Contained Devices option for the CAGE to show the cage (number) displayed in the Additional Info of this alarm. This verifies whether the correct cage has been equipped in the CM database.
68P02901W26-Q 24 May 2004
38-47
Procedure 38-19
Unequipped GPROC has Entered the LAN (Continued) Then... The GPROC may be in the wrong slot. Go to step 4. The CAGE needs to be equipped. Use the equip command for the CAGE device. Go to step 4.
If the CAGE device is... Equipped... Unequipped...
Determine whether the (GPROC) slot number shown in the Additional Info is valid. If the slot number is... within the range of 18-25 for BTS sites... within the range of 25-26 for RXCDR sites... not within one of the specified ranges... Then... The GPROC may be in the wrong slot. Go to step 5. The GPROC may be in the wrong slot. Go to step 5. The GPROC is either improperly inserted into a slot within the cage or the GPROC board is faulty. Go to step 7.
From the Navigation Tree window, select the Display Menu and from it the Contained Devices option for the GPROC to check for a GPROC that is Not on the LAN. If the command output... displays Not on the LAN for a GPROC... Then... The GPROC must be unequipped: Select the UNEQUIP option for the GPROC using the device ID displayed in the previous step. The same GPROC must be re-equipped correctly, go to step 6. displays the other processors only... The GPROC may not be equipped. Go to step 6.
6 7
Select the EQUIP option for the GPROC using the cage and slot numbers from the Additional Info of this alarm (19). 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 reinserting the GPROC into the correct cage and slot as designated in the CM database. Replace the GPROC board if this (19. SITE) alarm recurs.
38-48
68P02901W26-Q 24 May 2004
20. SITE: Unequipped GPROC Has Left the LAN

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. A GPROC device must be fully equipped before it can be used by the system.
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 on-site maintenance action is occurring; or an operator or on-site 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. Any additional bytes displayed should be ignored.
68P02901W26-Q 24 May 2004
38-49
Possible cause(s)
The following are possible causes for this alarm: The GPROC may have been removed from a CAGE before it (the GPROC) had been equipped. The GPROC may have been reset before being equipped. The GPROC may have been removed from an unequipped CAGE. The active LAN may have failed. The GPROC may be faulty.
Procedure
Procedure 38-20 1 2 Unequipped GPROC Has Left the LAN
Refer to the alarm message report. Check the Additional Info in the alarm output to determine the cage and slot numbers of the unequipped GPROC. 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 (20. SITE) occurs. If this alarm has been generated for... A GPROC that is intentionally unequipped... Then... No fault resolution is required. Consider blacklisting this alarm until the GPROC is equipped. It is possible that the wrong cage was equipped. Go to step 3.
A GPROC that is unexpectedly unequipped...
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.
38-50
68P02901W26-Q 24 May 2004
Procedure 38-20 3
Unequipped GPROC Has Left the LAN (Continued)
Refer to the alarm message report for LAN alarms. Determine whether the LAN connection has failed by checking the following. Have either of the following alarms been generated? 1. LAN: LAN Failure. 0. LAN: Active & Standby Failure.
If any LAN alarms have been generated, consult the appropriate alarm description in this manual for the necessary fault resolution procedure. If no LAN alarms have been generated, continue to the next step. 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 Info of this alarm (19). This verifies whether the correct cage has been equipped in the CM database. If the CAGE device is... Equipped... Then... The GPROC may be in the wrong slot. Go to step 6. Unequipped... The CAGE needs to be equipped. Use the equip command for the CAGE device. Go to step 4.
Determine whether the (GPROC) slot number shown in the Additional Info is valid. If the slot number is... within the range of 18-25 for BTS sites... within the range of 25-26 for RXCDR sites... not within one of the specified ranges... Then... The GPROC may be in the wrong slot. Go to step 7. The GPROC may be in the wrong slot. Go to step 7. The GPROC is either improperly inserted into a slot within the cage or the GPROC board is faulty. Go to step 9.
From the Navigation Tree window, select the Display Menu and 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...
68P02901W26-Q 24 May 2004
38-51
Procedure 38-20
Unequipped GPROC Has Left the LAN (Continued) That GPROC must be unequipped: Select the UNEQUIP option for the GPROC using the device ID displayed in the previous step. The same GPROC must be re-equipped correctly, go to step 8.
displays Not on the LAN for a GPROC...
displays the other processors only...
The GPROC may not be equipped. Go to step 8.
8 9
Select the EQUIP option for the GPROC using the cage and slot numbers from the Additional Info of this alarm (20). 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 reinserting the GPROC into the correct cage and slot as designated in the CM database. Replace the GPROC board if this (20. SITE) alarm recurs.
38-52
68P02901W26-Q 24 May 2004
21. SITE: No Clock References Available

Clearing Type: Severity Level: Category: FMIC Warning Quality of Service
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 (21) 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 usually affected only in the following ways: The GCLK is not able to phase lock. More frequent recalibrations are necessary.

68P02901W26-Q 24 May 2004
38-53
Table 38-1
Additional information field contents Byte first Value 00 to FF 00 to FF00 to FF00 to FF Definition The (MMS) timeslot allocated the RSL generating this alarm. 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.Note: If the MMS cannot be determined by the system, the values for bytes 2-5 are displayed as FF.
secondthirdfourth
Possible cause(s)
The following are possible causes for this alarm: An MSI link (MMS) connection may have failed. The MMS providing the clock reference source for the site may have been 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.
38-54
68P02901W26-Q 24 May 2004
Procedure
Procedure 38-21 1 No Clock References Available
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 Consult specific alarm pages in this manual for fault resolution procedures. Prioritize fault resolution accordingly. If there are no other failures, go to the next step.
Determine whether an MMS was defined for clock extraction when phase locking occurred. (Note that 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 (21) 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 step 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, re-check the Alarm window for MMS, MSI, XCDR (or GDP) alarms. Consult 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-Q 24 May 2004
38-55
22. SITE: Active Alarm List Full

Clearing Type: Severity Level: Category: FMIC Investigate Processing
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. Any additional bytes displayed should be ignored.
Possible cause(s)
The active alarm list is full because there are 120 active alarms at the site.
38-56
68P02901W26-Q 24 May 2004
Procedure
Procedure 38-22 1 Active Alarm List Full
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. 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-Q 24 May 2004
38-57
23. SITE: EMU Modem Card Failure
23. SITE: EMU Modem Card Failure

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. Any additional bytes displayed should be ignored.
Possible cause(s)
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 38-23 1 2 3 EMU Modem Card Failure
Check to see if the EMU card is in the modem shelf. Insert a good EMU card into the modem shelf if the EMU is not functioning. Check the possible causes.
38-58
68P02901W26-Q 24 May 2004
24. SITE: Site Reset Request

Description
This alarm indicates that either the system software, an OMC-R operator, or an on-site 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 via the BSS MMI or OMC-R GUI.
This fault condition is service-affecting. All Digital Radio Interface (DRI) radio units/RF Units go Out Of Service (OOS). As a result, calls are lost.

68P02901W26-Q 24 May 2004
38-59
Table 38-2
Additional information field contents Byte first Value (hex) 00 to FF Definition Specifies the Process Identifier (PID) number. The PID indicates the internal software process requesting the reset. (PID list in next section.) 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. 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 via 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 via the GUI. 28 - A hard reset requested from Rlogin or TTY window via an MMI command. 29 - Software requested an invalid operational state transition for a device.
second
00 or 01
third
00, 01, 02or27, 28, 29
Process Identifier (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 38-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 38-3 Process identifier (PID) number
38-60
68P02901W26-Q 24 May 2004
PID (dec/hex) 66/0x42
Abbreviated name CA
Description Central Authority (CA) Process has requested a site reset because an invalid operational state transition request was made to the CA. 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. Configuration Management (CM) has requested a BTS site reset because an operator has initiated a (BTS) reset via the OMC-R GUI. Network Management Application Service Element (NMASE) Process has requested a BSC site reset because an operator has initiated a (BSC) reset via the OMC-R GUI.
112/0x70
MMI
113/0x71
CM
118/0x76
NMASE
Possible cause(s)
The following are possible causes for this alarm: The system site reset request may have been due to a hardware fault. The system site reset request may have been due to a software fault: processing fault, inconsistent database, or invalid state transition requested for a device. The operator site reset attempted may have been due to a current fault (software or hardware) existing within the system.
Procedure
Procedure 38-24 1 Site Reset Request
Review the alarm report/event logs to determine the site where this alarm is occurring; and to check the Additional Info field in the alarm output for the possible cause for the alarm (and site reset). If a SITE reset has been initiated, wait for it to finish before continuing.
68P02901W26-Q 24 May 2004
38-61
Procedure 38-24 3
Site Reset Request (Continued)
After the reset, check to see if this alarm (SITE 24.) 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 (Performance Management, etc) for troubleshooting purposes and/or go to step 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. Consult other alarm descriptions and fault resolution procedures in this manual.
38-62
68P02901W26-Q 24 May 2004
25. SITE: External Power Booster Amplifier 1 Failure

Description
This alarm indicates that Transmitter Channel 1 Power Amplifier (PA) within the Horizoncompact (M-Cellarena 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 Horizoncompact (M-Cellarena macro) Booster units.
System impact
The result of this reduction in transmission power may have some general affects such as: significantly 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 is most likely be that call capacity is reduced provided the other PA remains fully functional. If the PA holding the BCCH fails, area of coverage is significantly reduced. In a low traffic area, if one PA fails, the loss of transmission power may be transparent if the Horizoncompact (M-Cellarena macro) site is not set up to function as sole coverage for the macro cell. However, if the unit provides sole coverage, call coverage may be significantly reduced.

68P02901W26-Q 24 May 2004
38-63
Possible cause(s)
The transmitter channel 1 Power Amplifier (PA) is defective.
Procedure
Procedure 38-25 1 2 External Power Booster Amplifier 1 Failure
Check the alarm report to determine the site for which the alarm was generated. Send a field representative to the site to replace the Horizoncompact (M-Cellarena macro) Booster containing the faulty PA. Note that the PA cannot be replaced on-site, the entire Booster unit must be replaced if faulty.
38-64
68P02901W26-Q 24 May 2004

Description
This alarm indicates that Transmitter Channel 2 Power Amplifier (PA) within the Horizoncompact (M-Cellarena 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 Horizoncompact (M-Cellarena macro) Booster units.
System impact

68P02901W26-Q 24 May 2004
38-65
Possible cause(s)
The transmitter channel 2 Power Amplifier (PA) is defective.
Procedure
Procedure 38-26 1 2 External Power Booster Amplifier 2 Failure
Check the alarm report to determine the site for which the alarm was generated. Send a field representative to the site to replace the Horizoncompact (M-Cellarena macro) Booster containing the faulty PA. Note that the PA cannot be replaced on-site, the entire Booster unit must be replaced if faulty.
38-66
68P02901W26-Q 24 May 2004
27. SITE: External Power Booster Failure

Description
This alarm indicates that the booster in the Horizoncompact (M-Cellarena macro) Base Transceiver Station (BTS) has failed. This alarm is generated when the system detects 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 Horizoncompact (M-Cellarena macro) site with a booster unit.
System impact

68P02901W26-Q 24 May 2004
38-67
Possible cause(s)
The following are possible causes for this alarm: A power supply or other device within the Horizoncompact ( M-Cellarena macro) Booster unit may be defective. The Horizoncompact macro Booster unit may have been disconnected. The Horizoncompact macro Booster unit may not be present at the site.
Procedure
Procedure 38-27 1 2 External Power Booster Failure
Check the alarm report to determine the site for which the alarm was generated. Send a field representative to the site to verify that the Horizoncompact macro Booster is present, and check the connections. If attempts to reconnect the Horizoncompact unit do not clear the alarm, replace the booster unit.
38-68
68P02901W26-Q 24 May 2004
28. SITE: Database Configuration and Arena Hardware Mismatch

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, Horizonmacro, or Horizonmacro2, but the database cabinet type does not match. If the site is Horizonmacro and the database is M-Cell6, the site will stay 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 Horizoncompact External Power Booster SITE alarms (25, 26, 27) can be generated if the Booster unit hardware becomes faulty.

68P02901W26-Q 24 May 2004
38-69
Possible cause(s)
The database configuration does not match the hardware present: The site may be standard Arena when database indicates Arena Macro or it may be Arena Macro when database shows standard Arena. If the BTS master cabinet is either M-Cell6, Horizonmacro, or Horizonmacro2, an invalid database cabinet type has been entered for this site.
Procedure
Procedure 38-28 1 2 3 Database Configuration and Arena Hardware Mismatch
Check the alarm report to determine the site for which the alarm was generated. Verify the site plan with Network OMC-R planners and administrators; determine which Horizon unit Cabinet Type should be at the site. 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 on-site. Go to step 5.
38-70
68P02901W26-Q 24 May 2004
Procedure 38-28 4
Database Configuration and Arena Hardware Mismatch (Continued)
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. The select Edit from the Edit menu to change the Cabinet Type at the site: M_CELLARENA represents an Horizonmicro unit. M_CELLARENA_MACRO represents an Horizoncompact Booster unit.
Send a field representative to the site to install the correct unit.
Consult the manual, Technical Description: BSS Command Reference (68P02901W23) for information regarding MMI commands. There are restrictions for using the enclosed modify_value MMI command.
68P02901W26-Q 24 May 2004
38-71
29. SITE: EMU Download Failure

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 cancelled 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 EMU slot number received.
Possible cause(s)
The firmware may have failed to upgrade due to: EMU did not accept download command. Timeout waiting for message from COM. Download cancelled 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.
38-72
68P02901W26-Q 24 May 2004
Invalid EMU slot number received.
68P02901W26-Q 24 May 2004
38-73
Procedure
Procedure 38-29 EMU Download Failure
The operator must analyze the download failure cause, correct the situation and then try to force a download, thereby downloading the correct firmware version/object.
38-74
68P02901W26-Q 24 May 2004
30. SITE: NVM Board Failure
30. SITE: NVM Board Failure

Description
The NVM board failed or was removed from the system. This alarm applies to BSC and RXCDR.

Possible cause(s)
The following are possible causes for this alarm: The NVM board failed. The NVM board was removed from the system.
Procedure
Procedure 38-30 NVM Board Failure
Send a field representative to the site to reinsert or replace the NVM board. 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-Q 24 May 2004
38-75
31. SITE: Failure of PCMCIA Card 1 on NVM Board
31. SITE: Failure of PCMCIA Card 1 on NVM Board

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 cause(s)
The following are possible causes for this alarm: The PCMCIA card failed. The PCMCIA card was removed from socket 1 of the NVM board.
Procedure
Procedure 38-31 Failure of PCMCIA Card 1 on NVM Board
Send a field representative to the site to reinsert or replace the NVM board. The NVM board with a PCMCIA card inserted in socket 1 is considered a single FRU.
38-76
68P02901W26-Q 24 May 2004
32. SITE: Last GBL Failed

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 cause(s)
The following are possible causes for this alarm: A protocol error occurred. The communications medium failed.
68P02901W26-Q 24 May 2004
38-77
Procedure
Procedure 38-32 1 2 Last GBL Failed
Review the Alarms window to identify the current GBL alarms. Initiate fault isolation and fault resolution procedures to restore the GBL communications links.
38-78
68P02901W26-Q 24 May 2004
33. SITE: BSSGP Status Message Received from the SGSN
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 an congestion condition at the SGSN. This condition is reported by the SGSN.

The BSSGP status message contents are displayed in the additional information field.
Possible cause(s)
The following are possible causes for this alarm: SGSN is unable to interpret a BSSGP status message sent by the BSS. There is a exception condition at the SGSN.
Procedure
Procedure 38-33 BSSGP Status Message Received from the SGSN
Initiate fault isolation and resolution procedures at the SGSN. After the fault at the SGSN is resolved, clear the alarm.
68P02901W26-Q 24 May 2004
38-79
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 cause(s)
The PCU is unable to interpret a BSSGP message sent by the SGSN.
Procedure
Procedure 38-34 Erroneous BSSGP Message Received from the SGSN
38-80
68P02901W26-Q 24 May 2004
35. SITE: Network Service Status Message Received from the SGSN
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 an exception condition occurred at the SGSN. This condition is reported by the SGSN.

The BSSGP status message contents are displayed in the additional information field.
Possible cause(s)
The following are possible causes for this alarm: The SGSN is unable to interpret a network service status message sent by the BSS. An exception condition may have occurred at the SGSN.
Procedure
Procedure 38-35 Network Service Status Message Received from the SGSN
68P02901W26-Q 24 May 2004
38-81
36. 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. This condition is reported by the SGSN.

The erroneous network service message contents are displayed in the additional information field.
Possible cause(s)
The PCU is unable to interpret a network service message sent by the SGSN.
Procedure
Procedure 38-36 Erroneous Network Service Message Received from the SGSN
38-82
68P02901W26-Q 24 May 2004
37. SITE: No NS-VC Block Acknowledgement from the SGSN
37. SITE: No NS-VC Block Acknowledgement from the SGSN

Description
The PCU has repeated the NS-VC (PVC) Block message the maximum number of times without receiving an acknowledgement 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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: An acknowledgement message was not received from SGSN. Frame Relay network problems are occurring.
Procedure
Procedure 38-37 No NS-VC Block Acknowledgement from the SGSN
Initiate fault isolation and resolution procedures at the SGSN, including verification of the PVC end-to-end connections. After the fault at the SGSN is resolved, clear the alarm.
68P02901W26-Q 24 May 2004
38-83
38. SITE: No NS-VC Unblock Acknowledgement from the SGSN
38. SITE: No NS-VC Unblock Acknowledgement from the SGSN

Description
The PCU has repeated the NS-VC(PVC) Unblock message the maximum number of times without receiving an acknowledgement 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. Any additional bytes displayed should be ignored.
Possible cause(s)
Procedure
Procedure 38-38 No NS-VC Unblock Acknowledgement from the SGSN
38-84
68P02901W26-Q 24 May 2004
39. SITE: No NS-VC Alive Acknowledgement from the SGSN

Description
The PCU has repeated the NS-VC (PVC) Alive message the maximum number of times without receiving an acknowledgement from the Serving GPRS Support Node (SGSN).
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. 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. Any additional bytes displayed should be ignored.
Possible cause(s)
Procedure
Procedure 38-39 No NS-VC Alive Acknowledgement from the SGSN
68P02901W26-Q 24 May 2004
38-85
Procedure 38-39
No NS-VC Alive Acknowledgement from the SGSN (Continued)
38-86
68P02901W26-Q 24 May 2004
40. SITE: No NS-VC Reset Acknowledgement from the SGSN

Description
The PCU has repeated the NS-VC (PVC) Reset message the maximum number of times without receiving an acknowledgement from the Serving GPRS Support Node (SGSN).
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. 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. Any additional bytes displayed should be ignored.
Possible cause(s)
Procedure
Procedure 38-40 No NS-VC Reset Acknowledgement from the SGSN
68P02901W26-Q 24 May 2004
38-87
Procedure 38-40
No NS-VC Reset Acknowledgement from the SGSN (Continued)
38-88
68P02901W26-Q 24 May 2004
41. SITE: Last NS-VC for the PCU failed

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. Any additional bytes displayed should be ignored.
Possible cause(s)
Frame Relay network problems are occurring.
Procedure
Procedure 38-41 Last NS-VC for the PCU failed Determine if the last GBL failed.
68P02901W26-Q 24 May 2004
38-89
Procedure 38-41
Last NS-VC for the PCU failed (Continued)
If the last GBL is... OOS...
Then... Initiate fault isolation and fault resolution procedures to restore the GBL communications links. Initiate fault isolation and resolution procedures for the frame network connections.
not OOS...
38-90
68P02901W26-Q 24 May 2004
42. SITE: Last TRAU GDS Failed
42. SITE: Last TRAU GDS Failed

Description
The last TRAU GDS data link failed. No data is carried between the BSC and the PCU.

Possible cause(s)
Link fault.
Procedure
Procedure 38-42 Last TRAU GDS Failed
Initiate fault isolation and resolution procedures for the TRAU GDS links.
68P02901W26-Q 24 May 2004
38-91
43. SITE: Last PRP DPROC Failed
43. SITE: Last PRP DPROC Failed

Description
This alarm indicates that the last PRP DPROC has gone out of service.

Possible cause(s)
The associated device has been taken out of service by an operator maintenance command, or there has been an equipment failure.
Procedure
Procedure 38-43 Last PRP DPROC Failed
First check the state of the failed devices using the command: dis_pr (site number) or state (site number) (dproc device numbers) 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 cause of the failure.
38-92
68P02901W26-Q 24 May 2004
44. SITE: 50% of the PCU NS-VCs Failed
44. SITE: 50% of the PCU NS-VCs Failed

Description
This alarm indicates that at least half, but not all of the equipped NS-VCs for the PCU have gone out of service. The alarm stays active until all the equipped NS-VCs for the PCU fail. If all the NS-VCs fail, the alarm is cleared.

Possible cause(s)
This alarm is typically due to frame relay network problems.
Procedure
Procedure 38-44 50% of the PCU NS-VCs Failed
Investigate the frame relay connections. This alarm is cleared immediately on receiving a clear indication. The alarm is also cleared if the last NS-VC has failed.
68P02901W26-Q 24 May 2004
38-93
45. SITE: No Signalling BVC Reset Acknowledgement from the SGSN
45. SITE: No Signalling BVC Reset Acknowledgement from the SGSN

Description
The PCU has repeated the BVC Reset message the maximum number of times for the signalling BVCI without receiving any acknowledgement from the SGSN.

Possible cause(s)
This alarm is typically due to frame relay network or SGSN problems.
Procedure
Procedure 38-45 No Signalling BVC Reset Acknowledgement from the SGSN
Investigate why a reset acknowledgement was not received from the SGSN for the signalling BVC.
38-94
68P02901W26-Q 24 May 2004
46. SITE: DSW Switching Hardware Required at Site

Clearing Type: Severity Level: Category:
FMIC Major Equipment
Description
{22064} Half rate calls on half rate capable RTFs that have 8kbps TRAU allowed will be blocked if 16kbps switching is in operation. If the RTF is configured for 8k 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 raised. The fix for this is to either swap out the KSWs for DSWs at the BSC (Procedure 1) or to re-configure to not require 8k backhaul and thus be consistent with the BSC (Procedure 2).

Possible cause(s)
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.
68P02901W26-Q 24 May 2004
38-95
Procedure
Procedure 38-46 DSW Switching Hardware Required at Site There are two procedures for clearing this alarm shown below: Procedure 1 DSW Hardware Required Swap out all KSWs for DSWs at the BSC Procedure 2 Re-configure Set all half rate enabled RTFs allow_8k_trau to "no"
Each half rate enabled RTF requires 2 additional E1 backhaul timeslots
38-96
68P02901W26-Q 24 May 2004
39
TBUS alarms
The TDM Bus (TBUS) alarms are covered in this chapter and include the following procedures: "0. TBUS: Remote KSW Loopback Test Failure" on page 39-3 "3. TBUS: Local KSWX/DSWX TDM Error" on page 39-5 "4. TBUS: Remote KSWX/DSWX TDM Error" on page 39-6
Chapter
68P02901W26-Q 24 May 2004
39-1
Introduction to TBUS alarms
Introduction to TBUS alarms
TBUS alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the 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 fibre optic cables interconnecting the KSWX cards. Each cage has two TBUS devices (one active and one redundant).
39-2
68P02901W26-Q 24 May 2004
0. TBUS: Remote KSW Loopback Test Failure

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 a fault exists with the TBUS and not 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 cause(s)
The following are possible causes for this alarm: A KSW Extender (KSWX) card failed. The KSWX fibre link failed. The TBUS fibre link failed. The TBUS backplane connections failed. The toggle switch on the KSWX card is in the down (disable) position.
68P02901W26-Q 24 May 2004
39-3
Procedure
Procedure 39-1 Remote KSW Loopback Test Failure
39-4
68P02901W26-Q 24 May 2004
3. TBUS: Local KSWX/DSWX TDM Error
3. TBUS: Local KSWX/DSWX TDM Error

Description
The local KSWX/DSWX card detected that it is no longer receiving data through the receive fibre.
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 cause(s)
The following are possible causes for this alarm: The fibre link between the local and remote KSWX/DSWX failed. The fibre link between the local and remote KSWX/DSWX was disconnected. A KSWX/DSWX card failed.
Procedure
Procedure 39-2 Local KSWX/DSWX TDM Error
68P02901W26-Q 24 May 2004
39-5
4. TBUS: Remote KSWX/DSWX TDM Error

Description
The remote KSWX/DSWX card detected that it is no longer receiving data through the receive fibre.
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. Any additional bytes displayed should be ignored.
Possible cause(s)
The following are possible causes for this alarm: The fibre link between the local and remote KSWX/DSWX failed. The fibre link between the local and remote KSWX/DSWX was disconnected. A KSWX/DSWX card failed.
39-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 39-3 Remote KSWX/DSWX TDM Error
68P02901W26-Q 24 May 2004
39-7
39-8
68P02901W26-Q 24 May 2004
40
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 40-3 "1. TIMESLOT: Channel Request From MS Failed - PM" on page 40-5
Chapter
68P02901W26-Q 24 May 2004
40-1
Introduction to TIMESLOT alarms
Introduction to TIMESLOT alarms
TIMESLOT alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the TIMESLOT alarms.
40-2
68P02901W26-Q 24 May 2004
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. For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The BTS has lost contact with the MS due to RF interference.
Procedure
Procedure 40-1 Radio Frequency Losses While Using a TCH - PM Determine if there are any currently active hardware alarms.
68P02901W26-Q 24 May 2004
40-3
Procedure 40-1
Radio Frequency Losses While Using a TCH - PM (Continued)
40-4
68P02901W26-Q 24 May 2004
1. TIMESLOT: Channel Request From MS Failed - PM

Description
The CHAN_REQ_MS_FAIL statistic threshold has been reached. This statistic counts the number of instances a BSS times out waiting for the MS to establish a call on a specific Stand-alone Dedicated Control Channel (SDCCH). For further information, consult the MTL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56). This may be 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 geographically clustered may indicate a hardware failure.

Possible cause(s)
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).
Procedure
Procedure 40-2 Channel Request From MS Failed - PM Determine if there are any currently active DRI alarms.
68P02901W26-Q 24 May 2004
40-5
Procedure 40-2
Channel Request From MS Failed - PM (Continued)
If there are ... currently active DRI alarms...
Then... Initiate isolation and corrective procedures for the current DRI alarms. After the DRI alarms are cleared, clear the alarm. MSs are probably experiencing radio problems. Clear the alarm.
no currently active DRI alarms...
40-6
68P02901W26-Q 24 May 2004
41
TRU alarms
The TopCell Radio Unit (TRU) alarms are covered in this chapter and include the following procedures: "0. TRU: Door Open" on page 41-3 "1. TRU: Power Supply Unit Failure" on page 41-4 "2. TRU: Power Mains Failure" on page 41-6 "5.- 6. TRU: Customer Defined Alarm 1-2" on page 41-8
Chapter
68P02901W26-Q 24 May 2004
41-1
Introduction to TRU alarms
Introduction to TRU alarms
TRU alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the TopCell Radio Unit (TRU).
41-2
68P02901W26-Q 24 May 2004
0. TRU: Door Open
0. TRU: Door Open

Description
A TRU cabinet door is open that should be closed.

Possible cause(s)
The following are possible causes for this alarm: The cabinet door was opened by a field engineer and was not properly secured when closed. The door latches are defective. An illegal entry.
Procedure
Procedure 41-1 Door Open
68P02901W26-Q 24 May 2004
41-3
1. TRU: Power Supply Unit Failure

Description
The TRU Power Supply Unit (PSU) lost dc power.
System action
The BSS software attempts to redirect calls to transceivers in neighbouring TRUs.

Possible cause(s)
The following are possible causes for this alarm: The dc output voltage is out of the specified operating range. The power supply failed.
Procedure
Procedure 41-2 Power Supply Unit Failure
41-4
68P02901W26-Q 24 May 2004
Procedure 41-2
Power Supply Unit Failure (Continued)
68P02901W26-Q 24 May 2004
41-5
2. TRU: Power Mains Failure

Description
The TRU lost ac power.
System action
The BSS software attempts to redirect calls to transceivers in neighbouring TRUs.

Possible cause(s)
The following are possible causes for this alarm: The ac power provided by the local electricity supplier is lost. The circuit breaker opened.
41-6
68P02901W26-Q 24 May 2004
Procedure
Procedure 41-3 1 Power Mains Failure
Contact the power company to determine whether there is an actual power failure. If there is... a power failure... not a power failure... Then... Go to step 2. field representative to the site to determine the cause of the alarm and take the appropriate corrective action.
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 back-up battery power can sustain the site.
68P02901W26-Q 24 May 2004
41-7
5.- 6. TRU: Customer Defined Alarm 1-2
5.- 6. TRU: Customer Defined Alarm 1-2

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 cause(s)
The following are possible causes for this alarm: An environmental sensor was activated. An environmental sensor failed.
Procedure
Procedure 41-4 Customer Defined Alarm 1-2
41-8
68P02901W26-Q 24 May 2004
42
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 42-3 "1. XBL: FRMR-Frames - PM" on page 42-4 "2. XBL: Expiration of N2 - PM" on page 42-5 "10. XBL: Link Disconnected" on page 42-6 "11. XBL: LAPD Protocol Error" on page 42-9 "13. XBL: LAPD Protocol Error Threshold Exceeded" on page 42-11 "15. XBL: Too Many LAPD Protocol Errors " on page 42-14
Chapter
68P02901W26-Q 24 May 2004
42-1
Introduction to XBL alarms
Introduction to XBL alarms
XBL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the remote Transcoder to BSS Link (XBL). The XBL carries the signalling link traffic between the BSC and a RXCDR site. The XBL uses the Multiple Serial Interface link (MMS: E1/T1 link) hardware as its underlying communication link medium.
42-2
68P02901W26-Q 24 May 2004
0. XBL: Invalid Received Frames - PM
0. XBL: 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/LAPD link. For further information, consult the XBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
An invalid frame was received on the X.25/LAPD link.
Procedure
68P02901W26-Q 24 May 2004
42-3
1. XBL: FRMR-Frames - PM
1. XBL: 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. For further information, consult the XBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
A frame reject message was received on the X.25/LAPD link.
Procedure
42-4
68P02901W26-Q 24 May 2004
2. XBL: Expiration of N2 - PM
2. XBL: 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. For further information, consult the XBL statistics chapter in the manual, Maintenance Information: GSM Statistics Application (68P02901W56).

Possible cause(s)
The X.25/LAPD link failed due to a hardware fault or repair action.
Procedure
68P02901W26-Q 24 May 2004
42-5
10. XBL: Link Disconnected

Description
An XBL disconnected on the MMS. No signalling information between the BSC and the RXCDR is passed over the disconnected link.

The contents of the additional information field are shown in Table 42-1. Table 42-1 Additional information field contents Byte first second third fourth fifth sixth seventh Value 00 to FF 00 to FF 01 to 1F 0A 00 to FF 00 to FF 00 to FF Definition The first two bytes are the reason codes:00 = Normal disconnect. C6 = XBL guard timer expired. MMS timeslot. MMS device type. MMS device identifiers.
42-6
68P02901W26-Q 24 May 2004
Possible cause(s)
The following are possible causes for this alarm: A normal link disconnect. A protocol or transmission problem. An XBL guard timer expired.
Procedure
Procedure 42-4 Link Disconnected
Wait at least 10 minutes after the alarm is reported before continuing with this procedure. If an RXCDR reboots, this allows sufficient time for the reboot process to complete.
Determine the state of the XBL device. If the XBL is... busy and unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Continue to step 2. Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 3.
not busy and unlocked... 2 If the XBL... returns to service...
Attempt to restore the XBL device to service.
Determine the state of the MMS device identified in the additional information field. If the MMS is... busy and unlocked... Then... The E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault.
68P02901W26-Q 24 May 2004
42-7
Procedure 42-4 4
Link Disconnected (Continued) Go to step 4.
42-8
68P02901W26-Q 24 May 2004
11. XBL: LAPD Protocol Error

Description
The XBL detected a LAPD protocol error due to a problem on one of the T1/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. Any additional bytes displayed should be ignored.
Possible cause(s)
The LAPD Error code in the additional information field corresponds to a possible cause for the alarm, as shown in Table 42-2. Table 42-2 LAPD error codes Error code 0 or 4 Description The timeslot assignments are not correct. The connection to the physical link may have a different protoco l.The physical media is faulty (for example, a noisy communication link). The external equipment experienced an outage. The physical frame droppe d.Out-of-sequence frames were received. The connection is invalid. The DACS link is physically connected to the wrong line.
2 or 3
68P02901W26-Q 24 May 2004
42-9
Table 42-2
LAPD error codes (Continued) Error code 5 or 8 Description 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. The remote side of the link connection sent I-frames before the link was established. A physical link outage affected the local to remote direction.
6 7 or 9
Procedure
Determine if this is a recurrence of this alarm. If this is... a recurrence of this alarm... not a recurrence of this alarm... Then... Go to step 2. Clear the alarm. Then... Send a field representative to the site to determine the cause of the alarm and take the appropriate corrective action. Review the Alarm/Event window for an MMS alarm and initiate the appropriate alarm handling procedures.
Determine the state of the MMS identified in the additional information field. If the MMS is... busy and unlocked...
42-10
68P02901W26-Q 24 May 2004
13. XBL: LAPD Protocol Error Threshold Exceeded

Description
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 42-3. The code indicates where the alarm was reported. Table 42-3 Additional information field contents Definition This alarm is caused by an excessive sequence of errors. This alarm is caused by an SABM extended received error.
Value (Hex) 01 05
Possible cause(s)
68P02901W26-Q 24 May 2004
42-11
Procedure
Procedure 42-6 LAPD Protocol Error Threshold Exceeded
Wait at least 10 minutes after the alarm is reported before continuing with this procedure. If an RXCDR reboots, this allows sufficient time for the reboot process to complete.
Determine the state of the XBL device. If the XBL is... busy and unlocked... Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Continue to step 2. Then... The fault condition no longer exists. If this is a recurrence of this alarm, the E1/T1 link is probably faulty. Send a field representative to the site to isolate and correct the link fault. Go to step 3.
not busy and unlocked... 2 If the XBL... returns to service...
Attempt to restore the XBL device to service.
Determine the state of the parent MSI device for the MMS identified in the additional information field. If the MMS is... Then...
42-12
68P02901W26-Q 24 May 2004
Procedure 42-6
LAPD Protocol Error Threshold Exceeded (Continued) The MMS device is faulty. Review the Alarm/Event window for the MMS alarm and initiate the appropriate alarm handling procedures. The MSI device is faulty. Review the Alarm/Event window for the MSI alarm and initiate the appropriate alarm handling procedures.
68P02901W26-Q 24 May 2004
42-13
15. XBL: Too Many LAPD Protocol Errors
15. XBL: Too Many LAPD Protocol Errors

Description

6 bytes: byte 1 -- MMS timeslot, byte 2 LAPD fault code, bytes 3-6 -- MMS device id.
Possible cause(s)
4 or more LAPD Protocol errors were received within 1 second indicating major problems with the XBL link.
Procedure
Check report logs for repeated occurrence of this alarm. If alarm occurs more than expected, monitor the state of 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/correct/replace it as necessary. Consult Alarm Handling at the OMC customer documentation. Investigate further the XBL if this keeps happening
42-14
68P02901W26-Q 24 May 2004
Index
Index
A
ABSS 0 alarm last XBL link failure . . . . . . . active & standby LAN failure LAN 0 alarm . . . . . . . . . . active alarm list full SITE 22 alarm . . . . . . . . . . active alarms exceed upper limit of OMC 30029 alarm . . . . . . . . active link connection failure BTP 234 alarm. . . . . . . . . . DHP 234 alarm . . . . . . . . . DRI 234 alarm . . . . . . . . . . MSI 234. . . . . . . . . . . . . active local FOX failure SITE 9 alarm . . . . . . . . . . active multiplexer 0 loopback failure SITE 3 alarm . . . . . . . . . . active multiplexer 1 loopback failure SITE 5 alarm . . . . . . . . . . active multiplexer 2 loopback failure SITE 7 alarm . . . . . . . . . . active remote FOX 0 failure SITE 11 alarm . . . . . . . . . . active remote FOX 1 failure SITE 13 alarm . . . . . . . . . . active remote FOX 2 failure SITE 15 alarm . . . . . . . . . . additional field information . . . . . . . . . . . advisory detected OMC 30035 alarm . . . . . . . . affected functional units . . . . . . air conditioning unit failure IAS 84 alarm . . . . . . . . . . alarm impact list . . . . . . . . . . . . alarm board failed IAS 108 alarm . . . . . . . . . . alarm categories communication . . . . . . . . . environmental . . . . . . . . . . equipment . . . . . . . . . . . . link . . . . . . . . . . . . . . . . . . . . . 2-2 alarm categories (contd.) NHA event . . . . . . . . . . . . processing . . . . . . . . . . . . . quality of service. . . . . . . . . . alarm clearing types . . . . . . . . . FMIC . . . . . . . . . . . . . . . Intermittent . . . . . . . . . . . . OIC . . . . . . . . . . . . . . . . alarm impact loss of capacity . . . . . . . . . . loss of redundancy . . . . . . . . . loss of service . . . . . . . . . . . alarm severities clear . . . . . . . . . . . . . . . critical . . . . . . . . . . . . . . investigate . . . . . . . . . . . . . major . . . . . . . . . . . . . . . minor . . . . . . . . . . . . . . . warning . . . . . . . . . . . . . . alarm states cleared . . . . . . . . . . . . . . deferred . . . . . . . . . . . . . . handling . . . . . . . . . . . . . . new . . . . . . . . . . . . . . . . seen . . . . . . . . . . . . . . . . alarm types tagged primary alarm . . . . . . . . . . secondary alarms . . . . . . . . untagged . . . . . . . . . . . . . alarms overview . . . . . . . . . . . . . ancillary cabinet overtemperature IAS 87 alarm . . . . . . . . . . . assigned timeslot counter overflow MSI 6 alarm . . . . . . . . . . . . assigned timeslot counter underflow MSI 5 alarm . . . . . . . . . . . . attempt at allocating a TCH failed CELL 25, PM alarm . . . . . . . . attempt at allocating an SDCCH failed CELL 1, PM alarm . . . . . . . . . auxiliary alarm 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 1-10 1-10 1-11 1-12 1-12 1-12
. . . . . . 25-3 . . . . . . . . . . . . . . . . . . . . . . . . . . 38-56 30-66
. . 7-36 . 15-53 . 17-281 . 28-28 38-27 38-15 38-19 38-23 38-31 38-35 38-39
. . . . . 1-16 . . . . . 1-16 . . . . . 1-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 1-11 1-11 1-11 1-11 1-11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. 1-10 . 1-10 . 1-9 . 1-9 . 1-9 1-5 1-5 1-4 1-3 23-75 28-14 28-12 12-59 12-10
. . . . . . 1-18 . . . . . 30-78 . . . . . . 1-15 . . . . . 23-70
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 1-15 . . . . . 23-111 . . . . . . . . . . . . . . . . . . . . . . . . 1-10 1-11 1-10 1-11
68P02901W26-Q 24 May 2004
IX-1
Index
auxiliary alarm 1 (contd.) IAS 109 alarm . . . . . . . . . . . . . . . 23-113 AXCDR 0 alarm BSC detecting CIC validation failure . . . . . 3-3
AXCDR 1 alarm AXCDR ID mismatch with RXCDR network entity ID . . . . . . . . . . . . . . . . . . . . . 3-4 AXCDR alarms introduction . . . . . . . . . . . . . . . . . 3-2 AXCDR ID mismatch with RXCDR network entity ID AXCDR 1 alarm . . . . . . . . . . . . . . . 3-4
B
bad clock source or SYNC OCXO (oscillator) replacement DHP 24 alarm . . . . . . . . . . . . . . . 15-13 bad HO reference numbers from the MS CELL 19, PM alarm . . . . . . . . . . . . 12-49 baseband hopping GSM timeslot misalignment DRI 193 alarm . . . . . . . . . . . . . . . 17-252 DRI 52 alarm . . . . . . . . . . . . . . . 17-80 baseband hopping TDM link error DRI 192 alarm . . . . . . . . . . . . . . . 17-250 DRI 51 alarm . . . . . . . . . . . . . . . 17-78 baseband hopping timeslot counter mismatch DRI 48 alarm . . . . . . . . . . . . . . . 17-72 battery backup input failure IAS 60 alarm . . . . . . . . . . . . . . . 23-49 battery backup output failure IAS 59 alarm . . . . . . . . . . . . . . . 23-47 battery box temperature high IAS 107 alarm . . . . . . . . . . . . . . . 23-109 BCUP 0 alarm unexpected board type . . . . . . . . . . . . 4-3 BCUP 1 alarm serial bus connection failure . . . . . . . . . 4-4 BCUP 10 alarm over temperature warning. . . . . . . . . . . 4-7 BCUP 8 alarm output failure . . . . . . . . . . . . . . . . 4-5 BCUP 9 alarm input failure . . . . . . . . . . . . . . . . . 4-6 BCUP alarms DPSM, EPSM, IPSM. . . . . . . . . . . . . 4-2 FRUs . . . . . . . . . . . . . . . . . . . . 4-2 bit error daily threshold exceeded MMS 12 alarm. . . . . . . . . . . . . . . 27-25 bit error hourly threshold exceeded MMS 13 alarm. . . . . . . . . . . . . . . 27-27 bit error OOS threshold exceeded MMS 14 alarm. . . . . . . . . . . . . . . 27-29 BSC detected MCU to MCU communication failure SITE 2 alarm . . . . . . . . . . . . . . . 38-12 BSC detecting CIC validation failure AXCDR 0 alarm . . . . . . . . . . . . . . . 3-3 BSP 1 alarm BSP 1 alarm (contd.) EEPROM flash failure - no valid bootstrap code object present . . . . . . . . . . . . . . . . . . . 5-4 BSP 17 alarm EEPROM flash programming failure . . . . . 5-8 BSP 21 alarm EEPROM flash programming failure . . . . . 5-9 BSP 22 alarm SWFM indication . . . . . . . . . . . . . . 5-10 BSP 231 alarm TDM interface configuration failure . . . . . . 5-32 BSP 239 alarm process safe test audit failure . . . . . . . . . 5-34 BSP 254 alarm device failure . . . . . . . . . . . . . . . . 5-36 BSP 30 alarm clock A signal loss . . . . . . . . . . . . . . 5-11 BSP 31 alarm clock B signal loss . . . . . . . . . . . . . . 5-13 BSP 32 alarm TDM interface failure - assigned timeslot counter underflow . . . . . . . . . . . . . . . . . . 5-15 BSP 33 alarm TDM interface failure - assigned timeslot counter overflow . . . . . . . . . . . . . . . . . . 5-17 BSP 34 alarm TDM interface failure - TDM parity error . . . 5-19 BSP 35 alarm LAN connection failure . . . . . . . . . . . 5-21 BSP 39 alarm software failure . . . . . . . . . . . . . . . 5-23 BSP 40 alarm spurious interrupt . . . . . . . . 5-25, 5-27, 5-29 BSP 8 alarm EEPROM flash object failure . . . . . . . . . 5-6 BSP alarms FRUs . . . . . . . . . . . . . . . . . . . . 5-2 introduction . . . . . . . . . . . . . . . . . 5-2 BSS 0 alarm last MTL link failure - signalling point inaccessible . . . . . . . . . . . . . . . . . 6-4 BSS 0 alarm, Last MTL Link Failure - Signalling Point Inaccessible
IX-2
68P02901W26-Q 24 May 2004
Index
BSS 0 alarm, Last MTL Link Failure - Signalling Point Inaccessible (contd.) BSS: Last MTL Link Failure - Signalling Point Inaccessible . . . . . . . . . . . . . . . . . 6-4 BSS 0, PM alarm pagingBSS 0, PM alarm . . . . . . . . . . . 6-7 BSS 1 alarm call processing failure - MSC detected SCCP down . . . . . . . . . . . . . . . . . . . . 6-8 BSS 1, PM alarm routeing failure - syntax error detected roueting failure - syntax error detected . . . 6-9 BSS 10 alarm erroneous Layer 3 message received by the BSS . . . . . . . . . . . . . . . . . . . . . 6-25 BSS 11 alarm confusion message received from the MSC . . 6-26 BSS 12 alarm unequipped circuit at the BSS . . . . . . . . . 6-27 BSS 17, PM alarm HO request from the MSC protocol error . . . 6-29 BSS 18, PM alarm routing failure - syntax error detected routing failure - syntax error detected . . . . 6-30 BSS 2 alarm call processing failure - MSC detected BSSAP down . . . . . . . . . . . . . . . . . . . . 6-10 BSS 2, PM alarm routeing failure - reason unknown . . . . . . . 6-11 BSS 20, PM alarm pagingBSS 20, PM alarm . . . . . . . . . . . 6-31 BSS 21 alarm trunk major threshold exceeded . . . . . . . . 6-32 BSS 22 alarm trunk critical threshold exceeded . . . . . . . 6-34 BSS 26 alarm received page for invalid cell from MSC . . . . 6-36 BSS 3 alarm call processing failure - BSS detected BSSAP down . . . . . . . . . . . . . . . . . . . . 6-12 BSS 39 alarm, Circuit Fault Detected on Radio Channel . . . . . . . . . . . . . . . . . . . . 6-37 BSS 40 alarm, Circuit Fault Cleared on Radio Channel BSS: Circuit Fault Cleared on Radio Channel . . . . . . . . . . . . . . . . . . . 6-39 BSS 41 alarm, Circuit Fault Detected On Ater Channel BSS: Circuit Fault Detected On Ater Channel . . . . . . . . . . . . . . . . . . . 6-41 BSS 42 alarm, Circuit Fault Cleared On Ater Channel BSS: Circuit Fault Cleared On Ater Channel . . 6-43 BSS 44 alarm, Circuit Fault Cleared on PCM Circuit BSS: Circuit Fault Cleared on PCM Circuit . . 6-47 BSS 45 alarm, Circuit Fault Detected on GPRS Circuit BSS: Circuit Fault Detected on GPRS Circuit . . . . . . . . . . . . . . . . . . . 6-48 68P02901W26-Q 24 May 2004
BSS 46 alarm, Circuit Fault Cleared on GPRS Circuit BSS: Circuit Fault Cleared on GPRS Circuit . . 6-50 BSS 46 alarm, Circuit Fault Detected On PATH Channel BSS: Circuit Fault Detected On PATH Channel . . . . . . . . . . . . . . . . . . . 6-51 BSS 48 alarm, Circuit Fault Cleared on PATH Channel . . . . . . . . . . . . . . . . . . . . 6-53 BSS 49 alarm last LMTL link failure - signalling point inaccessible . . . . . . . . . . . . . . . . . 6-55 BSS 49 alarm, Last LMTL Link Failure - Signalling Point Inaccessible BSS: Last LMTL Link Failure - Signalling Point Inaccessible . . . . . . . . . . . . . . . . . 6-55 BSS 5 alarm no MSC BSS 5 alarm. . . . . . . . . . . . . 6-14 BSS 5 alarm, No MSC Acknowledgement for Circuit Block BSS: No MSC Acknowledgement for Circuit Block . . . . . . . . . . . . . . . . . . . . 6-14 BSS 50 alarm call processing failure - SMLC detected SCCP down . . . . . . . . . . . . . . . . . . . . 6-58 BSS 51 alarm call processing failure - SMLC detected BSSAP down . . . . . . . . . . . . . . . . . . . . 6-60 BSS 52 alarm no SMLC acknowlegement for global reset . . 6-62 BSS 53 alarm erroneous Layer 3 message received by the SMLC. . . . . . . . . . . . . . . . . . . . 6-63 BSS 54 alarm confusion message received from the SMLC. . . . . . . . . . . . . . . . . . . . 6-64 BSS 55 alarm received page for invalid cell from SMLC . . . 6-65 BSS 6 alarm no MSC acknowledgement for circuit unblock . . . . . . . . . . . . . . . . . . . 6-16 BSS 7 alarm no MSC acknowledgement for reset circuit . . 6-18 BSS 7, PM alarm mobile assignment request from MSC protocol error . . . . . . . . . . . . . . . . . . . . 6-20 BSS 8 alarm unequipped circuit at the MSC . . . . . . . . 6-22 BSS 9 alarm no MSC acknowledgement for global reset. . . 6-24 BSS alarms introduction . . . . . . . . . . . . . . . . . 6-3 MSC to BSS Layer 3 . . . . . . . . . . . . . 6-3 BSSGP status message received from the SGSN . . . . . . . . . . . . . . . . . . . . 38-79
IX-3
Index
BTP 1 alarm EEPROM flash failure - no valid bootstrap code object present . . . . . . . . . . . . . . . . . . . 7-5 BTP 17 alarm EEPROM flash programming failure . . . . . 7-9 BTP 21 alarm EEPROM flash programming failure . . . . . 7-10 BTP 22 alarm SWFM indication . . . . . . . . . . . . . . 7-11 BTP 231 alarm TDM interface configuration failure . . . . . . 7-34 BTP 234 alarm active link connection failure . . . . . . . . . 7-36 BTP 235 alarm standby link connection failure . . . . . . . . 7-38 BTP 236 alarm slow flash failure. . . . . . . . . . . . . . . 7-41 BTP 237 alarm non-volatile memory failure . . . . . . . . . 7-43 BTP 239 alarm process safe test audit failure . . . . . . . . . 7-45 BTP 254 alarm device failure . . . . . . . . . . . . . . . . 7-47 BTP 30 alarm clock A signal loss . . . . . . . . . . . . . . 7-12 BTP 31 alarm
BTP 31 alarm (contd.) clock B signal loss . . . . . . . . . . . . . . 7-14 BTP 32 alarm TDM interface failure - assigned timeslot counter underflow . . . . . . . . . . . . . . . . . . 7-16 BTP 33 alarm TDM interface failure - assigned timeslot counter overflow . . . . . . . . . . . . . . . . . . 7-18 BTP 34 alarm TDM interface failure - TDM parity error . . . 7-20 BTP 35 alarm LAN connection failure . . . . . . . . . . . 7-22 BTP 39 alarm software failure . . . . . . . . . . . . . . . 7-24 BTP 40 alarm spurious interrupt . . . . . . . 7-26, 7-32 to 7-33 BTP 42 alarm site reset occurred due to front panel reset . . . 7-28 to 7-29, 7-31 BTP 8 alarm EEPROM flash object failure . . . . . . . . . 7-7 BTP alarms FRUs . . . . . . . . . . . . . . . . . . . . 7-3 introduction . . . . . . . . . . . . . . . . . 7-3 BTS cabinet overtemperature IAS 82 alarm . . . . . . . . . . . . . . . 23-66
C
CAB 25 alarm external power booster amplifier 1 failure CAB 26 alarm external power booster amplifier 2 failure CAB 27 alarm external power booster failure. . . . . . CAB 28 alarm database configuration and hardware mismatch . . . . . . . . . . . . . . . CAB alarms FRUs . . . . . . . . . . . . . . . . . introduction . . . . . . . . . . . . . . cabinet fan failure IAS 86 alarm . . . . . . . . . . . . . cabinet protection board fuse failure IAS 111 alarm . . . . . . . . . . . . . CAGE 20 alarm CLKX slot 2 communication failure . . . CAGE 21 alarm CLKX slot 3 communication failure . . . CAGE 22 alarm CLKX slot 4 communication failure . . . CAGE 23 alarm CLKX slot 5 communication failure . . . . . . . . . . . . . . . . . . . . . . . 8-3 8-4 8-5 8-6 8-2 8-2 23-73 CAGE 24 alarm CLKX slot 6 communication failure . CAGE 25 alarm CLKX slot 7 communication failure . CAGE 26 alarm LANX slot 19 communication failure CAGE 27 alarm LANX slot 20 communication failure CAGE 28 alarm power supply unit#1 output failure . CAGE 29 alarm power supply unit#2 output failure . CAGE 30 alarm power supply unit#3 output failure . CAGE 31 alarm power supply unit#1 not detected . . CAGE 32 alarm power supply unit#2 not detected . . CAGE 33 alarm power supply unit#3 not detected . . CAGE 34 alarm power supply unit#1 fan failure . . . CAGE 35 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 9-3 9-6 9-6 9-9 9-9 9-9
. . 23-116 . . . . . . . . . . . . 9-3 9-3 9-3 9-3
. . . . . 9-11 . . . . . 9-11 . . . . . 9-11 . . . . . 9-12
IX-4
68P02901W26-Q 24 May 2004
Index
CAGE 35 alarm (contd.) power supply unit#2 fan failure . . . . . . . . 9-12 CAGE 36 alarm power supply unit#3 fan failure . . . . . . . . 9-12 CAGE 37 alarm power supply unit#1 over-temperature . . . . . 9-13 CAGE 38 alarm power supply unit#2 over-temperature . . . . . 9-13 CAGE 39 alarm power supply unit#3 over-temperature . . . . . 9-13 CAGE 40 alarm over-temperature - component damage imminent . . . . . . . . . . . . . . . . . . 9-15 CAGE alarm 2 local KSWX slot 0 communication failure . . . 9-17 CAGE alarm 3 local KSWX slot 1 communication failure . . . 9-17 CAGE alarm 5 remote KSWX slot 3 communication failure . . . . . . . . . 9-20, 9-23, 9-26, 9-29, 9-32 CAGE alarm 6 remote KSWX slot 4 communication failure . . . . . . . . . 9-20, 9-23, 9-26, 9-29, 9-32 CAGE alarm 7 remote KSWX slot 5 communication failure . . . . . . . . . 9-20, 9-23, 9-26, 9-29, 9-32 CAGE alarm 8 remote KSWX slot 6 communication failure . . . . . . . . . 9-20, 9-23, 9-26, 9-29, 9-32 CAGE alarms introduction . . . . . . . . . . . . . . . . . 9-2 calibration in progress GCLK 21 alarm . . . . . . . . . . . . . . 20-40 calibration via firmware initiated GCLK 22 alarm . . . . . . . . . . . . . . 20-41 call processing failure - BSS detected BSSAP down BSS 3 alarm . . . . . . . . . . . . . . . . . 6-12 call processing failure - MSC detected BSSAP down BSS 2 alarm . . . . . . . . . . . . . . . . . 6-10 call processing failure - MSC detected SCCP down BSS 1 alarm . . . . . . . . . . . . . . . . . 6-8 call processing failure - SMLC detected BSSAP down BSS 51 alarm . . . . . . . . . . . . . . . . 6-60 call processing failure - SMLC detected SCCP down BSS 50 alarm . . . . . . . . . . . . . . . . 6-58 cavity 0 tuning error COMB 0 alarm . . . . . . . . . . . . . . . 13-3 cavity 1 tuning error COMB 1 alarm . . . . . . . . . . . . . . . 13-3 cavity 2 tuning error COMB 2 alarm . . . . . . . . . . . . . . . 13-3 cavity 3 tuning error COMB 3 alarm . . . . . . . . . . . . . . . 13-3 cavity 4 tuning error
cavity 4 tuning error (contd.) COMB 4 alarm . . . . . . . . . . . . . . . 13-3 cavity 5 tuning error COMB 11 alarm . . . . . . . . . . . . . . 13-18 cavity combining block 0 failure COMB 12 alarm . . . . . . . . . . . . . . 13-20 cavity combining block 1 failure COMB 13 alarm . . . . . . . . . . . . . . 13-22 CBL 0, PM alarm invalid received frames . . . . . . . . . . . . 10-3 CBL 1, PM alarm FRMR-frames . . . . . . . . . . . . . . . . 10-4 CBL 2, PM alarm expiration of N2 . . . . . . . . . . . . . . . 10-5 CBL alarms introduction . . . . . . . . . . . . . . . . . 10-2 CBUS 0 alarm over 50% of board detected clock failure. . . . 11-3 CBUS 2 alarm master CBUS signal provided by slave GCLK. . . . . . . . . . . . . . . . . . . . 11-5 CBUS 3 alarm local KSWX clock fibre failure . . . . . . . . 11-7 CBUS alarms introduction . . . . . . . . . . . . . . . . . 11-2 CCDSP alarms introduction . . . . . . . . . . . . . . . . . 17-7 CEL 3 alarm, Last NS-VC Failed CELL: Last NS-VC Failed . . . . . . . . . 12-16 CELL 0, PM alarm radio frequency losses while using an SDCCH . . . . . . . . . . . . . . . . . . . 12-7 CELL 1 alarm cell radio timeslot capacity loss . . . . . . . . 12-9 CELL 1, PM alarm attempt at allocating an SDCCH failed. . . . 12-10 CELL 10, PM alarm intra-cell handover failed & mobile lost . . . 12-31 CELL 11 alarm, GPRS unavailable - No Cell (BVC) Unblock Ack from the SGSN . . . . . . . . . 12-33 CELL 11, PM alarm intra-BSS HO primary target cell blocked . . 12-34 CELL 12 alarm, GPRS unavailable - No PDCHs Available . . . . . . . . . . . . . . . . . . 12-36 CELL 13 alarm GPRS unavailable - No GPRS capable carriers available . . . . . . . . . . . . . . . . . 12-37 CELL 13, PM alarm intra-BSS HO failed and recovered to org channel . . . . . . . . . . . . . . . . . . 12-38 CELL 14, PM alarm intra-BSS HO failed and mobile lost. . . . . 12-40, 12-42 CELL 15, PM alarm
68P02901W26-Q 24 May 2004
IX-5
Index
CELL 15, PM alarm (contd.) inter-BSS HO, MS HO failed message received . . . . . . . . . . . . . . . . . . 12-44 CELL 17 alarm EGPRS Unavailable - Insufficient GDS Available . . . . . . . . . . . . . . . . . 12-46 CELL 19, PM alarm bad HO reference numbers from the MS . . . 12-49 CELL 2, PM alarm channel request from MS blocked . . . . . . 12-14 CELL 20, PM alarm number of calls queued . . . . . . . . . . . 12-51 CELL 23, PM alarm mobile assignment failure from MS . . . . . 12-55 CELL 24, PM alarm PCH queue page discard . . . . . . . . . . 12-57 CELL 25, PM alarm attempt at allocating a TCH failed . . . . . . 12-59 CELL 4, PM alarm classmark update from MS protocol error . . 12-18 CELL 5 alarm no cell (BVC) block acknowledgement from the SGSN . . . . . . . . . . . . . . . . . . . 12-20 CELL 6, PM alarm cipher mode cmd from MSC failed . . . . . 12-21 CELL 7 alarm GPRS and baseband hopping configuration failure . . . . . . . . . . . . . . . . . . . 12-23 CELL 9 alarm, GPRS unavailable - No GDS available . . . . . . . . . . . . . . . . . . . 12-26 CELL 9, PM alarm intra-cell handover failed & recovered to org channel . . . . . . . . . . . . . . . . . . 12-27 CELL alarms introduction . . . . . . . . . . . . . . . . . 12-3 cell radio timeslot capacity loss CELL 1 alarm . . . . . . . . . . . . . . . . 12-9 cell transmit power unachievable DRI 74 alarm . . . . . . . . . . . . . . . 17-122 channel coder 0 failure - demodulation processor 0 failure DRI 53 alarm . . . . . . . . . . . . . . . 17-83 channel coder 0 failure - demodulation processor 1 failure DRI 54 alarm . . . . . . . . . . . . . . . 17-85 channel coder 1 failure - demodulation processor 0 failure DRI 55 alarm . . . . . . . . . . . . . . . 17-87 channel coder 1 failure - demodulation processor 1 failure DRI 56 alarm . . . . . . . . . . . . . . . 17-89 channel coder failure DRI 212 alarm . . . . . . . . . . . . . . . 17-264 channel coder internal message error
channel coder internal message error (contd.) DRI 13 alarm . . . . . . . . . . . . . . DRI 14 alarm . . . . . . . . . . . . . . DRI 16 alarm . . . . . . . . . . . . . . DRI 17 alarm . . . . . . . . . . . . . . DRI 19 alarm . . . . . . . . . . . . . . DRI 20 alarm . . . . . . . . . . . . . . DRI 9 alarm . . . . . . . . . . . . . . . channel coder timeslot 0 failure DRI 40 alarm . . . . . . . . . . . . . . channel coder timeslot 1 failure DRI 41 alarm . . . . . . . . . . . . . . channel coder timeslot 2 failure DRI 42 alarm . . . . . . . . . . . . . . channel coder timeslot 3 failure DRI 43 alarm . . . . . . . . . . . . . . channel coder timeslot 4 failure DRI 44 alarm . . . . . . . . . . . . . . channel coder timeslot 5 failure DRI 45 alarm . . . . . . . . . . . . . . channel coder timeslot 6 failure DRI 46 alarm . . . . . . . . . . . . . . channel coder timeslot 7 failure DRI 47 alarm . . . . . . . . . . . . . . channel request from MS blocked CELL 2, PM alarm . . . . . . . . . . . . channel request from MS failed TIMESLOT 1, PM alarm . . . . . . . . . cipher mode cmd from MSC failed CELL 6, PM alarm . . . . . . . . . . . . classmark update from MS protocol error CELL 4, PM alarm . . . . . . . . . . . . clearing types . . . . . . . . . . . . . . . FMIC . . . . . . . . . . . . . . . . . . Intermittent . . . . . . . . . . . . . . . OIC . . . . . . . . . . . . . . . . . . . CLKX slot 2 communication failure CAGE 20 alarm . . . . . . . . . . . . . CLKX slot 3 communication failure CAGE 21 alarm . . . . . . . . . . . . . CLKX slot 4 communication failure CAGE 22 alarm . . . . . . . . . . . . . CLKX slot 5 communication failure CAGE 23 alarm . . . . . . . . . . . . . CLKX slot 6 communication failure CAGE 24 alarm . . . . . . . . . . . . . CLKX slot 7 communication failure CAGE 25 alarm . . . . . . . . . . . . . clock A signal loss BSP 30 alarm . . . . . . . . . . . . . . BTP 30 alarm . . . . . . . . . . . . . . DHP 30 alarm . . . . . . . . . . . . . . GPROC 30 alarm . . . . . . . . . . . . MSI 4 alarm . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
17-21 17-23 17-27 17-29 17-33 17-35 17-17 17-70 17-70 17-70 17-70 17-70 17-70 17-70 17-70 12-14
. . 40-5 . . . . . . . . . . 12-21 12-18 1-11 1-12 1-12 1-12 9-3 9-3 9-3 9-3 9-3 9-3
. . . . . . . . . . . .
. . 5-11 . . 7-12 . 15-24 . 21-19 . 28-11
IX-6
68P02901W26-Q 24 May 2004
Index
Clock A Signal Loss DRI 27 alarm . . . . . . . . . clock B signal loss . . . . . . . . BSP 31 alarm . . . . . . . . . BTP 31 alarm . . . . . . . . . DHP 31 alarm . . . . . . . . . DRI 28 alarm . . . . . . . . . GPROC 31 alarm . . . . . . . KSW 5 alarm . . . . . . . . . MSI 3 alarm . . . . . . . . . . clock output failure GCLK 16 alarm . . . . . . . . clock reference failure GCLK 2 alarm . . . . . . . . . code objects unavailable CSFP 49 alarm. . . . . . . . . COMB 0 alarm cavity 0 tuning error . . . . . . COMB 1 alarm cavity 1 tuning error . . . . . . COMB 10 alarm partial reset . . . . . . . . . . COMB 11 alarm cavity 5 tuning error . . . . . . COMB 12 alarm cavity combining block 0 failure COMB 13 alarm cavity combining block 1 failure COMB 14 alarm processor A failure . . . . . . . COMB 15 alarm processor B failure . . . . . . . COMB 2 alarm cavity 2 tuning error . . . . . . COMB 254 alarm device failure . . . . . . . . . COMB 3 alarm cavity 3 tuning error . . . . . . COMB 4 alarm cavity 4 tuning error . . . . . . COMB 5 alarm link A sanity failure . . . . . . COMB 6 alarm link B sanity failure . . . . . . COMB 7 alarm power feed A failure . . . . . . COMB 8 alarm power feed B failure . . . . . . COMB 9 alarm full reset. . . . . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. 17-48 . 24-18 . . 5-13 . . 7-14 . 15-26 . 17-50 . 21-21 . 24-18 . 28-10 20-30
. . . . . .
. . . . . . . 20-5 . . . . 14-6, 14-8
. . . . . . . 13-3 . . . . . . . 13-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16 13-18 13-20 13-22 13-24 13-26
. . . . . . . 13-3 . . . . . . 13-28
. . . . . . . 13-3 . . . . . . . 13-3 . . . . . . . 13-5 . . . . . . . 13-7 . . . . . . . 13-9 . . . . . . . . . . . . 13-11 13-13
COMB alarms FRUs . . . . . . . . . . . . . . . . . . . . 13-2 introduction . . . . . . . . . . . . . . . . . 13-2 combiner alarms introduction . . . . . . . . . . . . . . . . . 13-2 confusion message received from the MSC BSS 11 alarm . . . . . . . . . . . . . . . . 6-26 confusion message received from the SMLC confusion message received from the MSC . . 6-64 connectivity mismatch between BSC and RXCDR MMS 41 alarm. . . . . . . . . . . . 27-87, 27-89 control processor configuration mismatch DRI 167 alarm . . . . . . . . . . . . . . . 17-236 control processor firmware failure DRI 166 alarm . . . . . . . . . . . . . . . 17-234 control processor message queue overflowed DRI 156 alarm . . . . . . . . . . . . . . . 17-214 control processor to equalizer communication failure DRI 153 alarm . . . . . . . . . . . . . . . 17-208 control processor to power amplifier communication failure DRI 152 alarm . . . . . . . . . . . . . . . 17-206 converter failure IAS 46 alarm . . . . . . . . . . . . . . . 23-41 converter overtemperature IAS 47 alarm . . . . . . . . . . . . . . . 23-43 corrupt NE file OMC 30051 alarm . . . . . . . . . . . . . 30-89 corrupt SITE file OMC 30052 alarm . . . . . . . . . . . . . 30-90 critical alarm threshold exceeded MMS 253 alarm . . . . . . . . . . . . . . 27-90 crtical resource exhausted DRI 31 alarm . . . . . . . . . . . . . . . 17-56 CSFP 22 alarm SWFM indication . . . . . . . . . . . . . . 14-3 CSFP 240 alarm PCMCIA card removed . . . . . . . . . . 14-12 CSFP 35 alarm LAN connection failure . . . . . . . . . . . 14-4 CSFP 49 alarm code objects unavailable . . . . . . . . 14-6, 14-8 CSFP alarms FRUs . . . . . . . . . . . . . . . . . . . . 14-2 introduction . . . . . . . . . . . . . . . . . 14-2 CSFPdownloadFailed OMC 30017 alarm . . . . . . . . . . . . . 30-37 CSFPSwapFailed OMC 30024 alarm . . . . . . . . . . . . . 30-55 Customer defined alarms . . . . . . . . . . . . 18-2
68P02901W26-Q 24 May 2004
IX-7
Index
D
database configuration and Arena hardware mismatch SITE 28 alarm . . . . . . . . . . . . 38-69, 38-72 database configuration and hardware mismatch CAB 28 alarm . . . . . . . . . . . . . . . . 8-6 database exceeds lower limit OMC 30019 alarm . . . . . . . . . . . . . 30-41 database exceeds upper limit OMC 30014 alarm . . . . . . . . . . . . . 30-33 dbCompressionFailed OMC 30009 alarm . . . . . . . . . . . . . 30-24 dbUncompressionFailed OMC 30018 alarm . . . . . . . . . . . . . 30-39 device alarm information . . . . . . . . . . . . . . . . . 1-8 device alarm information . . . . . . . . . . . . 1-8 device failure BSP 254 alarm . . . . . . . . . . . . . . . . 5-36 BTP 254 alarm. . . . . . . . . . . . . . . . 7-47 COMB 254 alarm . . . . . . . . . . . . . 13-28 DHP 254 alarm . . . . . . . . . . . . . . 15-57 DRI 254 alarm . . . . . . . . . . . . . . . 17-295 GPROC 254 alarm . . . . . . . . . . . . . 21-49 KSW 254 alarm . . . . . . . . . . . . . . 24-52 MSI 254 alarm . . . . . . . . . . . . . . . 28-30 PBUS 254 alarm . . . . . . . . . . . . . . . 32-3 SBUS 254 alarm . . . . . . . . . . . . . . . 37-3 DHP 1 alarm EEPROM flash failure - no valid bootstrap code object present . . . . . . . . . . . . . . . . . . . 15-4 DHP 17 alarm EEPROM flash programming failure . . . . . 15-8 DHP 21 alarm, EEPROM Flash Programming Failure DHP 21 alarm, EEPROM Flash Programming Failure . . . . . . . . . . . . . . . . . . . 15-9 DHP 22 alarm SWFM indication . . . . . . . . . . . . . 15-10 DHP 22 alarm, SWFM Indication . . . . . . . 15-10 DHP 23 alarm SYNC lost phase lock to master GCLK . . . 15-11 DHP 231 alarm TDM interface configuration failure . . . . . 15-51 DHP 234 alarm active link connection failure . . . . . . . . 15-53 DHP 239 alarm process safe test audit failure . . . . . . . . 15-55 DHP 24 alarm bad clock source or SYNC OCXO (oscillator) replacement . . . . . . . . . . . . . . . . 15-13 DHP 25 alarm SYNC warmup failure . . . . . . . . . . . 15-15 DHP 254 alarm device failure . . . . . . . . . . . . . . . 15-57 DHP 26 alarm SYNC calibration request. . . . . . . . . . 15-16 DHP 27 alarm SYNC shutdown request . . . . . . . . . . 15-18 DHP 28 alarm SYNC clock output failure . . . . . . . . . 15-20 DHP 29 alarm SYNC watchdog timer expired . . . . . . . 15-22 DHP 30 alarm clock A signal loss . . . . . . . . . . . . . 15-24 DHP 31 alarm clock B signal loss . . . . . . . . . . . . . 15-26 DHP 32 alarm TDM interface failure - assigned timeslot counter underflow . . . . . . . . . . . . . . . . . 15-27 DHP 33 alarm TDM interface failure - assigned timeslot counter overflow . . . . . . . . . . . . . . . . . 15-29 DHP 34 alarm TDM interface failure - TDM parity error . . 15-31 DHP 35 alarm LAN connection failure . . . . . . . . . . 15-33 DHP 39 alarm software failure . . . . . . . . . . . . . . 15-35 DHP 40 alarm spurious interrupt . . . . . . . . . . . . . 15-37 DHP 41 alarm unexpected board type: GPROC2 or GPROC3 is required . . . . . . . . 5-30 to 5-31, 14-7, 14-10 to 14-11, 15-48 to 15-50, 21-42 to 21-44 DHP 43 alarm SYNC not operational . . . . . . . . . . . 15-39 DHP 44 alarm SYNC calibration via firmware initiated . . . 15-41 DHP 45 alarm SYNC phase lock failure . . . . . . . . . . 15-42 DHP 46 alarm SYNC invalid mode . . . . . . . . . 15-44, 15-46 DHP 8 alarm EEPROM flash object failure . . . . . . . . . 15-6 DHP alarms FRUs . . . . . . . . . . . . . . . . . . . . 15-3 introduction . . . . . . . . . . . . . . . . . 15-3 display modes maps . . . . . . . . . . . . . . . . . . . . 1-19 door open IAS 93 alarm . . . . . . . . . . . . . . . 23-83 TRU 0 alarm. . . . . . . . . . . . . . . . . 41-3 downloadDisabled OMC 30023 alarm . . . . . . . . . . . . . 30-53 downloadFailed
IX-8
68P02901W26-Q 24 May 2004
Index
downloadFailed (contd.) OMC 30000 alarm . . . . . . . DPROC 0 alarm processor communication failure DPROC 22 alarm SWFM indication . . . . . . . DPROC 239 alarm process safe test audit failure . . DPROC 39 alarm software failure . . . . . . . . DPROC 9 alarm DPROC reset detected . . . . . DPROC alarms FRUs . . . . . . . . . . . . . introduction . . . . . . . . . . DPROC reset detected DPROC 9 alarm . . . . . . . . DPSM 0 failure IAS 63 alarm . . . . . . . . . DPSM 1 failure IAS 62 alarm . . . . . . . . . DPSM, power supply module BCUP alarms . . . . . . . . . DRAM battery backup fuse failure IAS 31 alarm . . . . . . . . . DRI 10 alarm dual-port RAM error . . . . . . DRI 112 alarm receiver synthesizer failure . . . DRI 113 alarm receiver synthesizer failure . . . DRI 114 alarm receiver synthesizer failure . . . DRI 115 alarm receiver synthesizer failure . . . DRI 116 alarm receiver synthesizer failure . . . DRI 117 alarm receiver synthesizer failure . . . DRI 118 alarm receiver synthesizer failure . . . DRI 119 alarm receiver failure. . . . . . . . . DRI 120 alarm receiver failure. . . . . . . . . DRI 121 alarm receiver failure. . . . . . . . . DRI 122 alarm receiver failure. . . . . . . . . DRI 123 alarm receiver failure. . . . . . . . . DRI 124 alarm receiver failure. . . . . . . . . DRI 125 alarm
. . . . . . . 30-4 . . . . . . . 16-3 . . . . . . . 16-7 . . . . . . . 16-9 . . . . . . . 16-8 . . . . . . . 16-5 . . . . . . . 16-2 . . . . . . . 16-2 . . . . . . . 16-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-55 23-53 4-2 23-31 17-19
. . . . . . 17-157 . . . . . . 17-159 . . . . . . 17-161 . . . . . . 17-163 . . . . . . 17-165 . . . . . . 17-167 . . . . . . 17-169 . . . . . . 17-171 . . . . . . 17-173 . . . . . . 17-175 . . . . . . 17-177 . . . . . . 17-179 . . . . . . 17-181
DRI 125 alarm (contd.) receiver failure. . . . . . . . . . . . . . . 17-183 DRI 126 alarm receiver failure. . . . . . . . . . . . . . . 17-185 DRI 127 alarm receiver failure. . . . . . . . . . . . . . . 17-187 DRI 128 alarm receiver failure. . . . . . . . . . . . . . . 17-189 DRI 13 alarm channel coder internal message error . . . . 17-21 DRI 14 alarm channel coder internal message error . . . . 17-23 DRI 15 alarm initial synchronization of radio and GPRS channel failed . . . . . . . . . . . . . . . . . . . 17-25 DRI 16 alarm channel coder internal message error . . . . 17-27 DRI 17 alarm channel coder internal message error . . . . 17-29 DRI 176 alarm . . . . . . . . . . . . . . . . 17-246 DRI 18 alarm primary message or hardware interrupt error . . . . . . . . . . . . . . . . . . . 17-31 DRI 184 alarm equalizer firmware failure . . . . . . . . . 17-248 DRI 19 alarm channel coder internal message error . . . . 17-33 DRI 192 alarm baseband hopping TDM link error. . . . . . 17-250 DRI 193 alarm baseband hopping GSM timeslot misalignment . . . . . . . . . . . . . . . . . . . 17-252 DRI 2 alarm internal message error - pointer misalignment . . . . . . . . . . . . . . . . . . . . 17-9 DRI 20 alarm channel coder internal message error . . . . 17-35 DRI 208 alarm power amplifier temperature . . . . . . . . 17-259 DRI 21 ALARM, Calibration in progress. . . . 17-37 DRI 210 alarm hopping DRI failure . . . . . . . . . . . . 17-260 DRI 211 alarm front end processor failure . . . . . . . . . 17-262 DRI 212 alarm channel coder failure . . . . . . . . . . . . 17-264 DRI 213 alarm transceiver processor failure . . . . . . . . 17-266 DRI 214 equalizer failure . . . . . . . . . . . . . . 17-268 DRI 215 alarm power amplifier failure . . . . . . . . . . . 17-270 DRI 216 alarm transceiver recovery failure . . . . . . . . . 17-272
68P02901W26-Q 24 May 2004
IX-9
Index
DRI 217 alarm transmission suspended to conserve battery power . . . . . . . . . . . . . . . . . . . 17-273 DRI 218 alarm invalid transceiver calibration data . . . . . 17-274 DRI 219 alarm GPRS not supported by radio . . . 17-275 to 17-276 DRI 224 alarm safe test audit failure . . . . . . . . . . . . 17-277 DRI 23 alarm radio subsystem software to DRI communication failure . . . . . . . . . . . . 17-37 to 17-38, 17-40 DRI 231 alarm TDM interface configuration failure . . . . . 17-279 DRI 234 alarm active link connection failure . . . . . . . . 17-281 DRI 235 alarm standby link connection failure . . . . . . . 17-284 DRI 236 alarm slow flash failure. . . . . . . . . . . . . . 17-286 DRI 237 alarm non-volatile memory failure . . . . . . . . 17-288 DRI 239 alarm process safe test audit failure . . . . . . . . 17-290 DRI 24 alarm TDM interface failure - TDM parity error . . 17-42 DRI 241 alarm standby link connected to wrong device . . . 17-292 DRI 243 alarm unlocked device not in service . . . . . . . 17-294 DRI 25 alarm TDM interface failure - assigned timeslot counter overflow . . . . . . . . . . . . . . . . . 17-44 DRI 254 alarm device failure . . . . . . . . . . . . . . . 17-295 DRI 26 alarm TDM interface failure - assigned timeslot counter underflow . . . . . . . . . . . . . . . . . 17-46 DRI 27 alarm, Clock A Signal Loss . . . . . . 17-48 DRI 28 alarm clock B signal loss . . . . . . . . . . . . . 17-50 DRI 29 alarm processor failure . . . . . . . . . . . . . . 17-52 DRI 3 alarm internal message error - dual-port RAM segment full . . . . . . . . . . . . . . . . . . . . 17-11 DRI 30 alarm transceiver re-initialized unexpectedly . . . . 17-54 DRI 31 alarm critical resource exhausted . . . . . . . . . 17-56 DRI 35 alarm reset due to recurring fault . . . . . . . . . 17-62 DRI 37 alarm hard reset . . . . . . . . . . . . . . . . . 17-65
DRI 39 alarm synchronization loss with MCU . . . . . . . 17-68 DRI 40 alarm channel coder timeslot 0 failure . . . . . . . 17-70 DRI 41 alarm channel coder timeslot 1 failure . . . . . . . 17-70 DRI 42 alarm channel coder timeslot 2 failure . . . . . . . 17-70 DRI 43 alarm channel coder timeslot 3 failure . . . . . . . 17-70 DRI 44 alarm channel coder timeslot 4 failure . . . . . . . 17-70 DRI 45 alarm channel coder timeslot 5 failure . . . . . . . 17-70 DRI 46 alarm channel coder timeslot 6 failure . . . . . . . 17-70 DRI 47 alarm channel coder timeslot 7 failure . . . . . . . 17-70 DRI 48 alarm baseband hopping timeslot counter mismatch . . . . . . . . . . . . . . . . . . . 17-72 DRI 49 alarm GSM timeslot counter mismatch . . . . . . 17-74 DRI 5 alarm super frame counter error . . . . . . . . . . 17-13 DRI 50 alarm spurious GSM timeslot interrupt . . . . . . 17-76 DRI 51 alarm baseband hopping TDM link error. . . . . . 17-78 DRI 52 alarm baseband hopping GSM timeslot misalignment . . . . . . . . . . . . . . . . . . . 17-80 DRI 53 alarm channel coder 0 failure - demodulation processor 0 failure . . . . . . . . . . . . . . . . . . . 17-83 DRI 54 alarm channel coder 0 failure - demodulation processor 1 failure . . . . . . . . . . . . . . . . . . . 17-85 DRI 55 alarm channel coder 1 failure - demodulation processor 0 failure . . . . . . . . . . . . . . . . . . . 17-87 DRI 56 alarm channel coder 1 failure - demodulation processor 1 failure . . . . . . . . . . . . . . . . . . . 17-89 DRI 57 alarm transceiver to DRI communication failure . . 17-91 DRI 58 alarm DRI 58 . . . . . . . . . . . . . . . . . . 17-93 DRI 59 alarm transceiver to DRI burst error . . . . . . . . 17-95 DRI 6 alarm superframe counter error . . . . . . . . . . 17-15 DRI 60 alarm transceiver to DRI burst error . . . . . . . . 17-97
IX-10
68P02901W26-Q 24 May 2004
Index
DRI 61 alarm transceiver to DRI communication error . . . 17-99 DRI 62 alarm transceiver to DRI communication error . . . 17-101 DRI 63 alarm transceiver to DRI communication error . . . 17-103 DRI 64 alarm unrecoverable error . . . . . . . . . . . . 17-105 DRI 65 alarm radio subsystem software to DRI communication error - checksum error . . . . . . . . . . . . . . 17-107 DRI 66 alarm superframe counter error . . . . . . . . . . 17-110 DRI 67 alarm radio subsystem software to DRI communication error - DRI not responding . . . . . . . . . . . . 17-112 DRI 70 alarm equalizer control processor failure - watchdog timer expired . . . . . . . . . . . . . . . . . . 17-114 DRI 71 alarm unexpected communications bus interrupt . . . . . . . . . . . . . . . . . . . . 17-116 DRI 72 alarm receiver failure. . . . . . . . . . . . . . . 17-118 DRI 73 alarm power amplifier error. . . . . . . . . . . . 17-120 DRI 74 alarm cell transmit power unachievable . . . . . . 17-122 DRI 80 alarm transceiver synthesizer failure . . . . . . . . 17-127 DRI 81 alarm transmitter synthesizer failure . . . . . . . . 17-129 DRI 82 alarm transmitter synthesizer failure . . . . . . . . 17-131 DRI 83 alarm transmitter synthesizer failure . . . . . . . . 17-133
DRI 84 alarm transmitter synthesizer failure . . . . . . . . 17-135 DRI 85 alarm transmitter failure - output power . . . . . . 17-137 DRI 86 alarm transmitter failure - output power . . . . . . 17-139 DRI 87 alarm transmitter failure - output power . . . . . . 17-141 DRI 88 alarm power amplifier temperature high . . . . . . 17-143 DRI 89 alarm power amplifier communication failure . . . 17-145 DRI 9 alarm channel coder internal message error . . . . 17-17 DRI 90 alarm transmitter failure - output power . . . . . . 17-147 DRI 91 alarm power amplifier power low but functioning . . . . . . . . . . . . . . . . . . . . 17-149 DRI 92 alarm power amplifier DRI 92 alarm . . . . . . . 17-151 DRI 92 alarm, Power Amplifier Temperature High But Functioning . . . . . . . . . . . . . . . . . 17-151 DRI 93 alarm transmitter failure - output power . . . . . . 17-153 DRI alarms FRUs . . . . . . . . . . . . . . . . . . . . 17-8 introduction . . . . . . . . . . . . . . . . . 17-7 DRI firmware . . . . . . . . . . . . . . . . 17-37 DSP channel audit failures MSI 11 - 40 alarms . . . . . . . . . . . . . 28-19 dual-port RAM error DRI 10 alarm . . . . . . . . . . . . . . . 17-19 duplexer voltage error IAS 51 alarm . . . . . . . . . . . . . . . 23-46
E
EAS 0 alarm unexpected board type . . . EAS 1 alarm serial bus connection failure EAS 16 alarm optocoupler 1 . . . . . . . EAS 17 alarm optocoupler 2 . . . . . . . EAS 18 alarm optocoupler 3 . . . . . . . EAS 19 alarm optocoupler 4 . . . . . . . EAS 20 alarm optocoupler 5 . . . . . . . . . . . . . . . . 18-3 . . . . . . . . . 18-5 . . . . . . . . . 18-9 . . . . . . . . . 18-9 . . . . . . . . . 18-9 . . . . . . . . . 18-9 . . . . . . . . . 18-9 EAS 21 alarm optocoupler 6 . EAS 22 alarm optocoupler 7 . EAS 23 alarm optocoupler 8 . EAS 24 alarm optocoupler 9 . EAS 26 alarm optocoupler 11 . EAS 27 alarm optocoupler 12 . EAS 28 alarm . . . . . . . . . . . . . . . 18-9 . . . . . . . . . . . . . . . 18-9 . . . . . . . . . . . . . . . 18-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10 18-10 18-10
68P02901W26-Q 24 May 2004
IX-11
Index
EAS 28 alarm (contd.) optocoupler 13 . . . . . . . . . . . . . . . 18-10 EAS 29 alarm optocoupler 14 . . . . . . . . . . . . . . . 18-10 EAS 30 alarm optocoupler 15 . . . . . . . . . . . . . . . 18-10 EAS 31 alarm optocoupler 16 . . . . . . . . . . . . . . . 18-10 EAS 8 alarm EAS has detected main power failure . . . . . 18-7 EAS alarms . . . . . . . . . . . . . . . . . . 18-2 EAS has detected main power failure EAS 8 alarm . . . . . . . . . . . . . . . . . 18-7 EEPROM flash failure - no valid bootstrap code object present BSP 1 alarm . . . . . . . . . . . . . . . . . 5-4 BTP 1 alarm . . . . . . . . . . . . . . . . . 7-5 DHP 1 alarm. . . . . . . . . . . . . . . . . 15-4 GPROC 1 alarm . . . . . . . . . . . . . . . 21-4 EEPROM flash object failure BSP 8 alarm . . . . . . . . . . . . . . . . . 5-6 BTP 8 alarm . . . . . . . . . . . . . . . . . 7-7 DHP 8 alarm. . . . . . . . . . . . . . . . . 15-6 GPROC 8 alarm . . . . . . . . . . . . . . . 21-6 EEPROM flash programming failure BSP 17 alarm . . . . . . . . . . . . . . . . 5-8 BSP 21 alarm . . . . . . . . . . . . . . . . 5-9 BTP 17 alarm . . . . . . . . . . . . . . . . 7-9 BTP 21 alarm . . . . . . . . . . . . . . . . 7-10 DHP 17 alarm . . . . . . . . . . . . . . . . 15-8 GPROC 17 alarm . . . . . . . . . . . . . . 21-8 GPROC 21 alarm . . . . . . . . . . . . . 21-10 EEPROM Flash Programming Failure DHP 21 alarm . . . . . . . . . . . . . . . . 15-9 EGPRS - Unavailable - Insufficient GDS Available CELL 17 alarm . . . . . . . . . . . . . . 12-46 EMDisconnectedFromDB OMC 30008 alarm . . . . . . . . . . . . . 30-22 environmental variables CONSOLIDATION . . . . . . . . . . . . . 1-5 EPSM, power supply module BCUP alarms . . . . . . . . . . . . . . . . 4-2 equalizer configuration mismatch DRI 168 alarm . . . . . . . . . . . . . . . 17-238
equalizer control processor failure - watchdog timer expired DRI 70 alarm . . . . . . . . . . . . . . . 17-114 equalizer failure DRI 214 . . . . . . . . . . . . . . . . . . 17-268 equalizer firmware failure DRI 184 alarm . . . . . . . . . . . . . . . 17-248 equalizer output overflowed DRI 159 alarm . . . . . . . . . . . . . . . 17-220 DRI 160 alarm . . . . . . . . . . . . . . . 17-222 equalizer timeslot 0 failure DRI 176 alarm . . . . . . . . . . . . . . . 17-246 erroneous BSSGP message received from the SGSN . . . . . . . . . . . . . . . . . . . . 38-80 erroneous Layer 3 message received by the BSS BSS 10 alarm . . . . . . . . . . . . . . . . 6-25 erroneous Layer 3 message received by the SMLC BSS 53 alarm . . . . . . . . . . . . . . . . 6-63 event management alarm messages . . . . . . . . . . . . . . . 1-3 event messages . . . . . . . . . . . . . . . 1-3 exceeds lower limit disk usage OMC 30011 alarm . . . . . . . . . . . . . 30-29 exceeds upper limit disk usage OMC 30010 alarm . . . . . . . . . . . . . 30-26 expiration of N2 CBL 2, PM alarm . . . . . . . . . . . . . . 10-5 GSL 2, PM alarm . . . . . . . . . . . . . . 22-5 OML 2, PM alarm . . . . . . . . . . . . . . 31-5 RSL 2, PM alarm . . . . . . . . . . . . . . 36-5 XBL 2, PM alarm . . . . . . . . . . . . . . 42-5 external combiner main fuse failure IAS 20 alarm . . . . . . . . . . . . . . . 23-24 external combiner redundant fuse failure IAS 21 alarm . . . . . . . . . . . . . . . 23-25 external power booster amplifier 1 failure CAB 25 alarm . . . . . . . . . . . . . . . . 8-3 SITE 25 alarm . . . . . . . . . . . . . . . 38-63 external power booster amplifier 2 failure CAB 26 alarm . . . . . . . . . . . . . . . . 8-4 SITE 26 alarm . . . . . . . . . . . . . . . 38-65 external power booster failure CAB 27 alarm . . . . . . . . . . . . . . . . 8-5 SITE 27 alarm . . . . . . . . . . . . . . . 38-67
F
F_BSS_ACI_FAULT . . . . . F_BSS_ACI_FAULT_CLEAR F_BSS_CIC_FAULT . . . . . F_BSS_FAULT_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 6-43 6-45 6-50 F_BSS_GCI_FAULT . . . . . F_BSS_PIC_FAULT . . . . . F_BSS_PIC_FAULT_CLEAR. F_BSS_RCI_FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48 6-51 6-53 6-37
IX-12
68P02901W26-Q 24 May 2004
Index
failure of PCMCIA Card 1 on NVM board SITE 31 alarm . . . . . . . . . . . . . . . 38-76 fan tray 0 failure IAS 103 alarm . . . . . . . . . . . . . . . 23-102 fan tray 1 failure IAS 104 alarm . . . . . . . . . . . . . . . 23-104 fan tray 2 failure IAS 105 alarm . . . . . . . . . . . . . . . 23-105 feature 23658 . . . . . . . . . . . . . . . . 12-43, 12-46 4354 . . 5-2, 5-27, 5-29 to 5-31, 7-3, 7-29, 7-31 to 7-33, 14-2, 14-6 to 14-7, 14-10 to 14-11, 15-3, 15-46, 15-48 to 15-50, 21-3, 21-40, 21-42 to 21-44 4415 . . . . . . 9-17, 9-20, 9-23, 9-26, 9-29, 11-7, 24-41, 24-43, 28-19, 39-5 to 39-6 FEP alarms introduction . . . . . . . . . . . . . . . . . 17-7 filexferFailed OMC 30002 alarm . . . . . . . . . . . . . . 30-8 flow control procedure has started barring normal calls from access classes 0-9 . . . . . . . . . . . . . 12-4 FMIC . . . . . . . . . . . . . . . . . . . . . 1-12 frame slip daily threshold exceeded MMS 8 alarm . . . . . . . . . . . . . . . 27-20 frame slip hourly threshold exceeded MMS 9 alarm . . . . . . . . . . . . 27-22, 27-24 frequency difference in mate GCLK GCLK 8 alarm . . . . . . . . . . . . . . . 20-17 FRMR-frames CBL 1, PM alarm . . . . . . . . . . . . . . 10-4 GSL 1, PM alarm . . . . . . . . . . . . . . 22-4
FRMR-frames (contd.) OML 1, PM alarm . . . . . . . . . . . . . . 31-4 RSL 1, PM alarm . . . . . . . . . . . . . . 36-4 XBL 1, PM alarm . . . . . . . . . . . . . . 42-4 front end processor failure DRI 211 alarm . . . . . . . . . . . . . . . 17-262 Front End Processor to Radio Subsystem Software Communication Failure DRI 36 alarm . . . . . . . . . . . . . . . 17-64 FRUs BCUP alarms . . . . . . . . . . . . . . . . 4-2 BSP alarms . . . . . . . . . . . . . . . . . 5-2 BTP alarms . . . . . . . . . . . . . . . . . 7-3 CAB alarms . . . . . . . . . . . . . . . . . 8-2 COMB alarms . . . . . . . . . . . . . . . . 13-2 CSFP alarms. . . . . . . . . . . . . . . . . 14-2 DHP alarms . . . . . . . . . . . . . . . . . 15-3 DPROC alarms . . . . . . . . . . . . . . . 16-2 DRI alarms . . . . . . . . . . . . . . . . . 17-8 GCLK alarms . . . . . . . . . . . . . . . . 20-2 GPROC alarms . . . . . . . . . . . . . . . 21-3 KSW alarms . . . . . . . . . . . . . . . . . 24-2 MMS alarms. . . . . . . . . . . . . . . . . 27-4 MSI alarms . . . . . . . . . . . . . . . . . 28-2 PSP alarms . . . . . . . . . . . . . . . . . 35-2 FU . . . . . . . . . . . . . . . . . . . . . . 1-15 full reset COMB 9 alarm . . . . . . . . . . . . . . 13-13 functional units cell . . . . . . . . . . . . . . . . . . . . . 1-15 site . . . . . . . . . . . . . . . . . . . . . 1-15
68P02901W26-Q 24 May 2004
IX-13
Index
G
GBL 0 alarm link disconnected . . . . . . . . . . GBL alarms introduction . . . . . . . . . . . . . GCLK 0 alarm reference distribution module failure . GCLK 11 alarm long-term -average values are unstable. GCLK 12 alarm unrecognized hardware revision level . GCLK 14 alarm phase lock failure . . . . . . . . . . GCLK 15 alarm watchdog timer expired. . . . . . . . GCLK 16 alarm clock output failure. . . . . . . . . . GCLK 17 alarm SYNC shutdown request . . . . . . . GCLK 18 alarm not operational . . . . . . . . . . . . GCLK 19 alarm warmup failure. . . . . . . . . . . . GCLK 2 alarm clock reference failure . . . . . . . . GCLK 20 alarm invalid mode. . . . . . . . . . . . . GCLK 21 alarm calibration in progress . . . . . . . . GCLK 22 alarm calibration via firmware initiated . . . GCLK 232 alarm processor bus communication failure . GCLK 26 alarm GCLK calibration request. . . . . . . GCLK 4 alarm phase lock lost . . . . . . . . . . . . GCLK 4 alarm, Phase Lock Lost . . . . GCLK 5 alarm 125us reference count overflow . . . . GCLK 6 alarm 60ms reference count overflow . . . . GCLK 7 alarm 6.12s reference count overflow . . . . GCLK 8 alarm frequency difference in mate GCLK . . GCLK 9 alarm hard reset . . . . . . . . . . . . . . GCLK alarms FRUs . . . . . . . . . . . . . . . . introduction . . . . . . . . . . . . . GCLK calibration request GCLK 26 alarm . . . . . . . . . . . . . . . 19-3 . . . . 19-2 . . . . 20-3 . . . . . . . . . . . . . . . . . . . . . . . . 20-22 20-24 20-25 20-28 20-30 20-32 20-34 20-36 GDP alarms . . . . . . . . . . . . . . . . . . 28-2 GPROC 1 alarm EEPROM flash failure - no valid bootstrap code object present . . . . . . . . . . . . . . . . . . . 21-4 GPROC 17 alarm EEPROM flash programming failure . . . . . 21-8 GPROC 19 alarm RSL Links Congestion . . . . . . . . . . . . 21-9 GPROC 21 alarm EEPROM flash programming failure . . . . 21-10 GPROC 22 alarm SWFM indication . . . . . . . . . 21-11 to 21-18 GPROC 231 alarm TDM interface configuration failure . . . . . 21-45 GPROC 239 alarm process safe test audit failure . . . . . . . . 21-47 GPROC 254 alarm device failure . . . . . . . . . . . . . . . 21-49 GPROC 30 alarm clock A signal loss . . . . . . . . . . . . . 21-19 GPROC 31 alarm clock B signal loss . . . . . . . . . . . . . 21-21 GPROC 32 alarm TDM interface failure - assigned timeslot counter underflow . . . . . . . . . . . . . . . . . 21-23 GPROC 33 alarm TDM interface failure - assigned timeslot counter overflow . . . . . . . . . . . . . . . . . 21-25 GPROC 34 alarm TDM interface failure - TDM parity error . . 21-27 GPROC 35 alarm LAN connection failure . . . . . . . . . . 21-29 GPROC 39 alarm software failure . . . . . . . . . . . . . . 21-31 GPROC 40 alarm spurious interrupt . . . . . . . . . . . . . 21-33 GPROC 42 alarm site reset occurred due to front panel reset . . 21-35, 21-40 GPROC 8 alarm EEPROM flash object failure . . . . . . . . . 21-6 GPROC alarms FRUs . . . . . . . . . . . . . . . . . . . . 21-3 introduction . . . . . . . . . . . . . . . . . 21-3 GPRS and baseband hopping configuration failure CELL 7 alarm . . . . . . . . . . . . . . . 12-23 GPRS not supported by radio DRI 219 alarm . . . . . . . . . . 17-275 to 17-276 GPRS unavailable - No GPRS capable carriers available CELL 13 alarm . . . . . . . . . . . . . . 12-37 GSL 0, PM alarm
. . . . 20-5 . . . . . . . . . . . . . . . 20-38 20-40 20-41 20-48 20-45
. . . . 20-8 . . . . 20-8 . . . . . . . . . . . . . . . 20-11 20-13 20-15 20-17 20-20
. . . . 20-2 . . . . 20-2 . . . 20-45
IX-14
68P02901W26-Q 24 May 2004
Index
GSL 0, PM alarm (contd.) invalid received frames . GSL 1, PM alarm FRMR-frames . . . . . GSL 10 alarm link disconnected . . . GSL 11 alarm LAPD protocol error . . GSL 13 alarm
. . . . . . . . . . . 22-3 . . . . . . . . . . . 22-4 . . . . . . . . . . . 22-6 . . . . . . . . . . 22-10
GSL 13 alarm (contd.) LAPD protocol error threshold exceeded. 22-14 GSL 2, PM alarm expiration of N2 . . . . . . . . . . . . GSL alarms introduction . . . . . . . . . . . . . . GSM timeslot counter mismatch DRI 49 alarm . . . . . . . . . . . . .
. . 22-12, . . . 22-5 . . . 22-2 . . 17-74
H
hard reset DRI 37 alarm . . . . . . . . . . . . . . GCLK 9 alarm . . . . . . . . . . . . . . KSW 8 alarm . . . . . . . . . . . . . . MSI 1 alarm . . . . . . . . . . . . . . . HDSL modem loop 0 synch loss timer expired MMS 25 alarm. . . . . . . . . . . . . . HDSL modem loop 2 synch timer expired . 17-65 . 20-20 . 24-27 . . 28-6 . 27-50 HDSL modem loop 2 synch timer expired (contd.) MMS 26 alarm. . . . . . . . . . . . . . . heat management system unit failure IAS 85 alarm . . . . . . . . . . . . . . . HO request from the MSC protocol error BSS 17, PM alarm . . . . . . . . . . . . . hopping DRI failure DRI 210 alarm . . . . . . . . . . . . . . . 27-53 23-71 . 6-29 17-260
68P02901W26-Q 24 May 2004
IX-15
Index
I
IAS +27 V DAB power fuse failure IAS 75 alarm . . . . . . . . . . . . . . . 23-61 IAS +27 V power fuse failure IAS 32 alarm . . . . . . . . . . . . . . . 23-32 IAS 0 alarm unexpected board type . . . . . . . . . . . . 23-5 IAS 1 alarm serial bus connection failure . . . . . . . . . 23-6 IAS 10 alarm power supply unit 2 failure . . . . . . . . . 23-13 IAS 101 alarm power supply temperature high . . . . . . . 23-98 IAS 102 alarm mains A.C. supply failure . . . . . . . . . . 23-100 IAS 103 alarm fan tray 0 failure . . . . . . . . . . . . . . 23-102 IAS 104 alarm fan tray 1 failure . . . . . . . . . . . . . . 23-104 IAS 105 alarm fan tray 2 failure . . . . . . . . . . . . . . 23-105 IAS 106 alarm rectifier failure . . . . . . . . . . . . . . . 23-107 IAS 107 alarm battery box temperature high . . . . . . . . 23-109 IAS 108 alarm alarm board failed . . . . . . . . . . . . . 23-111 IAS 109 alarm auxiliary alarm 1 . . . . . . . . . . . . . . 23-113 IAS 11 alarm power supply unit 3 failure . . . . . . . . . 23-15 IAS 110 alarm urgent critical alarm . . . . . . . . . . . . 23-114 IAS 111 alarm cabinet protection board fuse failure . . . . . 23-116 IAS 112-113 alarms, Heat Management System Unit Failure 1 & 2 IAS: Heat Management System Unit Failure 1 & 2 . . . . . . . . . . . . . . . . . . . . . 23-117 IAS 114-115 alarms, Mains A.C. Supply Failure 1 & 2 IAS: Mains A.C. Supply Failure 1 & 2. . . . 23-118 IAS 116-117 alarms, Rectifier Failure 1 & 2 IAS: Rectifier Failure 1 & 2. . . . . . . . . 23-119 IAS 12 alarm tx vswr antenna fault . . . . . . . . . . . . 23-17 IAS 16 alarm matrix main fuse failure . . . . . . . . . . 23-20 IAS 17 alarm matrix control redundant fuse failure . . . . 23-21 IAS 18 alarm internal combiner main fuse failure . . . . . 23-22 IAS 19 alarm internal combiner redundant fuse failure . . . 23-23 IAS 20 alarm external combiner main fuse failure . . . IAS 21 alarm external combiner redundant fuse failure. IAS 22 alarm multicoupler main fuse failure . . . . . IAS 23 alarm multicoupler redundant fuse failure . . . IAS 30 alarm spare fuse failure . . . . . . . . . . . . IAS 31 alarm DRAM battery backup fuse failure . . . IAS 32 alarm IAS +27 V power fuse failure . . . . . . IAS 37 alarm lower cage fan #2 failure . . . . . . . . IAS 41 alarm multicoupler failure . . . . . . . . . . IAS 46 alarm converter failure . . . . . . . . . . . . IAS 47 alarm converter overtemperature . . . . . . . IAS 51 alarm duplexer voltage error . . . . . . . . . IAS 59 alarm battery backup output failure . . . . . . IAS 60 alarm battery backup input failure . . . . . . . IAS 61 alarm RCU #5 circuit breaker failure . . . . . IAS 62 alarm DPSM 1 failure . . . . . . . . . . . . IAS 63 alarm DPSM 0 failure . . . . . . . . . . . . IAS 75 alarm IAS +27 V DAB power fuse failure . . . IAS 8 alarm power supply unit 0 failure . . . . . . . IAS 80 alarm power supply unit - input failure . . . . IAS 81 alarm power supply unit - output failure . . . . IAS 82 alarm BTS cabinet overtemperature . . . . . . IAS 83 alarm low voltage disconnect imminent . . . . IAS 84 alarm air conditioning unit failure . . . . . . . IAS 85 alarm heat management system unit failure . . IAS 86 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-24 23-25 23-26 23-27 23-30 23-31 23-32 23-35 23-39 23-41 23-43 23-46 23-47 23-49 23-51 23-53 23-55 23-61
. . . 23-9 . . . . . . . . . . . . 23-62 23-64 23-66 23-68 23-70 23-71
IX-16
68P02901W26-Q 24 May 2004
Index
IAS 86 alarm (contd.) cabinet fan failure . . . . . . . . . . . . . 23-73 IAS 87 alarm ancillary cabinet overtemperature . . . . . . 23-75 IAS 9 alarm power supply unit 1 failure . . . . . . . . . 23-11 IAS 91 alarm voltage standing wave ratio performance low . . . . . . . . . . . . . . . . . . . . 23-79 IAS 92 alarm smoke alarm . . . . . . . . . . . . . . . . 23-81 IAS 93 alarm door open . . . . . . . . . . . . . . . . . 23-83 IAS 94 alarm no connection tIAS 94 alarm . . . . . . . . 23-85 IAS 94 alarm, No Connection to Alarms Board connection broken . . . . . . . . . . . . . . 23-85 IAS 95 alarm low noise amplifier fuse failure . . . . . . . 23-87 IAS 97 alarm no connection to alarm board - radio OOS . . 23-91 IAS 98 alarm no redundant connection to alarms board - radio OOS . . . . . . . . . . . . . . . . . . . 23-93 IAS 99 alarm no connection to alarm board - alarm board removed . . . . . . . . . . . . . . . 23-94, 23-96 IAS alarms introduction . . . . . . . . . . . . . . . . . 23-4 IAS: BCU Upper Cage Fan #3-#5 Fuse Failure. . . . . . . . . . . . . . . . . . . . 23-29 impact list impact list format . . . . . . . . . . . . . . 1-15 information additional field. . . . . . . . . . . . . . . . 1-18 device alarm . . . . . . . . . . . . . . . . . 1-8 reconfiguration . . . . . . . . . . . . . . . 1-13 initial synchronization of radio and GPRS channel failed DRI 15 alarm . . . . . . . . . . . . . . . 17-25 input failure BCUP 9 alarm . . . . . . . . . . . . . . . . 4-6 inter-BSS HO, MS HO failed message received CELL 15, PM alarm . . . . . . . . . . . . 12-44 intermittent . . . . . . . . . . . . . . . . . . 1-12 internal combiner main fuse failure IAS 18 alarm . . . . . . . . . . . . . . . 23-22 internal combiner redundant fuse failure IAS 19 alarm . . . . . . . . . . . . . . . 23-23 internal loopback audit failure KSW 225 alarm . . . . . . . . . . . . . . 24-47 internal message error - dual-port RAM segment full DRI 3 alarm . . . . . . . . . . . . . . . . 17-11 internal message error - pointer misalignment DRI 2 alarm . . . . . . . . . . . . . . . . . 17-9
intra-BSS HO failed and mobile lost CELL 14, PM alarm . . . . . . . . . 12-40, 12-42 intra-BSS HO failed and recovered to org channel CELL 13, PM alarm . . . . . . . . . . . . 12-38 intra-BSS HO primary target cell blocked CELL 11, PM alarm . . . . . . . . . . . . 12-34 intra-cell handover failed & mobile lost CELL 10, PM alarm . . . . . . . . . . . . 12-31 intra-cell handover failed & recovered to org channel CELL 9, PM alarm . . . . . . . . . . . . . 12-27 introduction AXCDR alarms . . . . . . . . . . . . . . . 3-2 BSP alarms . . . . . . . . . . . . . . . . . 5-2 BSS alarms . . . . . . . . . . . . . . . . . 6-3 BTP alarms . . . . . . . . . . . . . . . . . 7-3 CAB alarms . . . . . . . . . . . . . . . . . 8-2 CAGE alarms . . . . . . . . . . . . . . . . 9-2 CBL alarms . . . . . . . . . . . . . . . . . 10-2 CBUS alarms . . . . . . . . . . . . . . . . 11-2 CCDSP alarms. . . . . . . . . . . . . . . . 17-7 CELL alarms . . . . . . . . . . . . . . . . 12-3 COMB alarms . . . . . . . . . . . . . . . . 13-2 combiner alarms . . . . . . . . . . . . . . . 13-2 CSFP alarms. . . . . . . . . . . . . . . . . 14-2 DHP alarms . . . . . . . . . . . . . . . . . 15-3 DPROC alarms . . . . . . . . . . . . . . . 16-2 DRI alarms . . . . . . . . . . . . . . . . . 17-7 FEP alarms . . . . . . . . . . . . . . . . . 17-7 GBL alarms . . . . . . . . . . . . . . . . . 19-2 GCLK alarms . . . . . . . . . . . . . . . . 20-2 GPROC alarms . . . . . . . . . . . . . . . 21-3 GSL alarms . . . . . . . . . . . . . . . . . 22-2 IAS alarms . . . . . . . . . . . . . . . . . 23-4 KSW alarms . . . . . . . . . . . . . . . . . 24-2 LAN alarms . . . . . . . . . . . . . . . . . 25-2 LMTL alarms . . . . . . . . . . . . . . . . 26-2 manual organization . . . . . . . . . . . . . 1-2 MCAP/TDM bus alarms . . . . . . . . . . . 17-7 MMS alarms. . . . . . . . . . . . . . . . . 27-3 MSI alarms . . . . . . . . . . . . . . . . . 28-2 MTL alarms . . . . . . . . . . . . . . . . . 29-2 OMC alarms . . . . . . . . . . . . . . . . . 30-3 OML alarms . . . . . . . . . . . . . . . . . 31-2 PBUS alarms . . . . . . . . . . . . . . . . 32-2 PCU alarms . . . . . . . . . . . . . . . . . 33-2 PSP alarms . . . . . . . . . . . . . . . . . 35-2 RSL alarms . . . . . . . . . . . . . . . . . 36-2 SBUS alarms . . . . . . . . . . . . . . . . 37-2 SITE alarms . . . . . . . . . . . . . . . . . 38-3 TBUS alarms . . . . . . . . . . . . . . . . 39-2 TIMESLOT alarms . . . . . . . . . . . . . 40-2 TRU alarms . . . . . . . . . . . . . . . . . 41-2 XBL alarms . . . . . . . . . . . . . . . . . 42-2 invalid calibration data
68P02901W26-Q 24 May 2004
IX-17
Index
invalid calibration data (contd.) DRI 171 alarm . . . . . . . invalid mode GCLK 20 alarm . . . . . . invalid received frames CBL 0, PM alarm . . . . . GSL 0, PM alarm . . . . . OML 0, PM alarm . . . . .
. . . . . . . . 17-244 . . . . . . . . 20-38
. . . . . . . . . 10-3 . . . . . . . . . 22-3 . . . . . . . . . 31-3
invalid received frames (contd.) RSL 0, PM alarm . . . . . . . XBL 0, PM alarm . . . . . . . invalid transceiver calibration data DRI 218 alarm . . . . . . . . . IPSM, power supply module BCUP alarms . . . . . . . . .
. . . . . . . 36-3 . . . . . . . 42-3 . . . . . . 17-274 . . . . . . . 4-2
K
KSW 0 alarm parity highway 0 . . . . . . . . . . . KSW 1 alarm parity highway 1 . . . . . . . . . . . KSW 10 alarm lost communication with KSW . . . . KSW 11 alarm local cage KSW TDM loopback test failure . . . . . . . . . . . . . . . . KSW 2 alarm parity highway 2 . . . . . . . . . . . KSW 224 alarm safe test audit failure . . . . . . . . . KSW 225 alarm internal loopback audit failure. . . . . KSW 232 alarm processor bus communication failure . . . . . 24-4 . . . . 24-8 . . . . . . . . . . . . . . . . . . 24-32 24-35 24-10 24-45 24-47 24-50 KSW 254 alarm device failure . . . . . . KSW 3 alarm parity highway 3 . . . . . KSW 4 alarm lock A signal loss . . . . KSW 6 alarm 6.12 second reference loss KSW 7 alarm re-initialized unexpectedly KSW 8 alarm hard reset . . . . . . . . KSW 9 alarm watchdog timer expired. . KSW alarms FRUs . . . . . . . . . . introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-52 24-12 24-14 24-22 24-24 24-27 24-29
. . . . . . . . . . 24-2 . . . . . . . . . . 24-2
L
LAN 0 alarm active & standby LAN failure . . . LAN 1 alarm LAN failure . . . . . . . . . . . LAN alarms introduction . . . . . . . . . . . LAN connection failure BSP 35 alarm . . . . . . . . . . BTP 35 alarm . . . . . . . . . . CSFP 35 alarm. . . . . . . . . . DHP 35 alarm . . . . . . . . . . GPROC 35 alarm . . . . . . . . LAN failure LAN 1 alarm . . . . . . . . . . LANX slot 19 communication failure CAGE 26 alarm . . . . . . . . . LANX slot 20 communication failure CAGE 27 alarm . . . . . . . . . LAPD protocol error GSL 11 alarm . . . . . . . . . . . . . . . . 25-3 . . . . . . 25-5 . . . . . . 25-2 . . . . . . . . . . . . . . . . . . . . . . 5-21 . . 7-22 . . 14-4 . 15-33 . 21-29 LAPD protocol error (contd.) RSL 11 alarm . . . . . . . . . . . . . . . 36-14 XBL 11 alarm . . . . . . . . . . . . . . . . 42-9 LAPD protocol error threshold exceeded GSL 13 alarm . . . . . . . . . . . . 22-12, 22-14 RSL 13 alarm . . . . . . . . . . . . . . . 36-17 XBL 13 alarm . . . . . . . . . . . . . . . 42-11 last GBL failed . . . . . . . . . . . . . . . . 38-77 last GSL failed PCU 0 alarm. . . . . . . . . . . . . . . . . 33-3 last LMTL link failure - signalling point inaccessible BSS 49 alarm . . . . . . . . . . . . . . . . 6-55 last MTL link failure - signalling point inaccessible BSS 0 alarm . . . . . . . . . . . . . . . . . 6-4 last NS-VC failed CELL 3 alarm . . . . . . . . . . . . . . . 12-16 last NS-VC for the PCU failed. . . . . . . . . 38-89 last RSL link failure SITE 0 alarm . . . . . . . . . . . . . . . . 38-4 last TRAU GDS failed . . . . . . . . . . . . 38-91
. . . . . . 25-5 . . . . . . . . . . . . . . . . . 9-6 9-6 22-10
IX-18
68P02901W26-Q 24 May 2004
Index
last XBL link failure ABSS 0 alarm . . . . . . . . . . . . . . . . 2-2 level 1/2/3 failure OMC 30012 alarm . . . . . . . . . . . . . 30-31 link A sanity failure COMB 5 alarm . . . . . . . . . . . . . . . 13-5 link audit failure RSL 14 alarm . . . . . . . . . . . . . . . 36-19 link B sanity failure COMB 6 alarm . . . . . . . . . . . . . . . 13-7 link disconnected GBL 0 alarm. . . . . . . . . . . . . . . . . 19-3 GSL 10 alarm . . . . . . . . . . . . . . . . 22-6 RSL 10 alarm . . . . . . . . . . . . . . . . 36-6 XBL 10 alarm . . . . . . . . . . . . . . . . 42-6 link traffic too high MTL 3 alarm . . . . . . . . . . . . 26-14, 29-10 XBL 12 alarm . . . . . . . . . . . . . . . 42-14 LMTL 0 alarm signalling link failure. . . . . . . . . . . . . 26-3 LMTL 0, PM alarm SL failure - all reasons . . . . . . . . . . . . 26-6 LMTL 1 alarm SMLC processor outage . . . . . . . . . . . 26-8 LMTL 1, PM alarm SL failure - abnormal FIBR/BSNR . . . . . 26-10 LMTL 11, PM alarm SL congestion events resulting in loss of MSUs . . . . . . . . . . . . . . . . . . . 26-30
LMTL 12, PM alarm SL congestion indications. . . . . . . . . LMTL 4, PM alarm SL failure - excessive duration of congestion . . . . . . . . . . . . . . . . . . . LMTL 5, PM alarm SL alignment failure . . . . . . . . . . . LMTL alarms introduction . . . . . . . . . . . . . . . local cage KSW TDM loopback test failure KSW 11 alarm . . . . . . . . . . . . . . local KSWX clock fibre failure CBUS 3 alarm . . . . . . . . . . . . . . local KSWX slot 0 communication failure 2. CAGE alarm . . . . . . . . . . . . . local KSWX slot 1 communication failure 3. CAGE alarm . . . . . . . . . . . . . local KSWX TDM error TBUS 1 alarm . . . . . . . . . . . . . . lock A signal loss KSW 4 alarm . . . . . . . . . . . . . . long-term -average values are unstable GCLK 11 alarm . . . . . . . . . . . . . lost communication with KSW KSW 10 alarm . . . . . . . . . . . . . . low noise amplifier fuse failure IAS 95 alarm . . . . . . . . . . . . . . low voltage disconnect imminent IAS 83 alarm . . . . . . . . . . . . . .
. . .
26-31 26-18 26-20
. . 26-2 . 24-35
. . 11-7 . . 9-17 . . 9-17 . . 39-5 . . . . . 24-14 20-22 24-32 23-87 23-68
M
M-Cell Micro interconnect failure DRI 170 alarm . . . . . . . . . . . . . . . 17-242 mains A.C. supply failure IAS 102 alarm . . . . . . . . . . . . . . . 23-100 manual organization introduction . . . . . . . . . . . . . . . . . 1-2 map display colours . . . . . . . . . . . . . . 1-19 master CBUS signal provided by slave GCLK CBUS 2 alarm . . . . . . . . . . . . . . . . 11-5 master HDSL modem loop 0 SNR daily threshold exceeded MMS 27 alarm. . . . . . . . . . . . . . . 27-56 master HDSL modem loop 0 SNR hourly threshold exceeded MMS 31 alarm. . . . . . . . . . . . . . . 27-64 master HDSL modem loop 0 SNR OOS threshold exceeded MMS 35 alarm. . . . . . . . . . . . . . . 27-72 master HDSL modem loop 1 SNR daily threshold exceeded MMS 28 alarm. . . . . . . . . . . . . . . 27-58 master HDSL modem loop 1 SNR hourly threshold exceeded MMS 32 alarm. . . . . . . . . . . . . . . 27-66 master HDSL modem loop 1 SNR OOS threshold exceeded MMS 36 alarm. . . . . . . . . . . . . . . 27-75 matrix control redundant fuse failure IAS 17 alarm . . . . . . . . . . . . . . . 23-21 matrix main fuse failure IAS 16 alarm . . . . . . . . . . . . . . . 23-20 MCAP/TDM bus alarms introduction . . . . . . . . . . . . . . . . . 17-7 Memory usage exceeds upper limit OMC 30064 alarm . . . . . . . . . . . . . 30-65 MMS 0 alarm synchronization loss daily threshold exceeded . . . . . . . . . . . . . . . . . . 27-6 MMS 1 alarm
68P02901W26-Q 24 May 2004
IX-19
Index
MMS 1 alarm (contd.) synchronization loss hourly threshold exceeded . . . . . . . . . . . . . . . . . . 27-8 MMS 12 alarm bit error daily threshold exceeded . . . . . . 27-25 MMS 13 alarm bit error hourly threshold exceeded . . . . . 27-27 MMS 14 alarm bit error OOS threshold exceeded . . . . . . 27-29 MMS 16 alarm synchronization loss OOS timer expired . . . 27-32 MMS 18 alarm remote alarm OOS timer expired . . . . . . 27-35 MMS 2 alarm synchronization loss OOS threshold exceeded . . . . . . . . . . . . . . . . . 27-10 MMS 20 alarm red alarm daily threshold exceeded . . . . . 27-38 MMS 21 alarm red alarm hourly threshold exceeded. . . . . 27-40 MMS 22 alarm red alarm OOS threshold exceeded . . . . . 27-42 MMS 23 alarm red alarm OOS timer expired . . . . . . . . 27-45 MMS 24 alarm modem to NIU serial channel control link failure . . . . . . . . . . . . . . . . . . . 27-48 MMS 25 alarm HDSL modem loop 0 synch loss timer expired . . . . . . . . . . . . . . . . . . 27-50 MMS 253 alarm critical alarm threshold exceeded . . . . . . 27-90 MMS 26 alarm HDSL modem loop 2 synch timer expired . . 27-53 MMS 27 alarm master HDSL modem loop 0 SNR daily threshold exceeded . . . . . . . . . . . . . . . . . 27-56 MMS 28 alarm master HDSL modem loop 1 SNR daily threshold exceeded . . . . . . . . . . . . . . . . . 27-58 MMS 29 alarm slave HDSL modem loop 0 SNR daily threshold exceeded . . . . . . . . . . . . . . . . . 27-60 MMS 30 alarm slave HDSL modem loop 1 SNR daily threshold exceeded . . . . . . . . . . . . . . . . . 27-62 MMS 31 alarm master HDSL modem loop 0 SNR hourly threshold exceeded . . . . . . . . . . . . . . . . . 27-64 MMS 32 alarm master HDSL modem loop 1 SNR hourly threshold exceeded . . . . . . . . . . . . . . . . . 27-66 MMS 33 alarm slave HDSL modem loop 0 SNR hourly threshold exceeded . . . . . . . . . . . . . . . . . 27-68 IX-20
MMS 34 alarm slave HDSL modem loop 1 SNR hourly threshold exceeded . . . . . . . . . . . . . . . . . 27-70 MMS 35 alarm master HDSL modem loop 0 SNR OOS threshold exceeded . . . . . . . . . . . . . . . . . 27-72 MMS 36 alarm master HDSL modem loop 1 SNR OOS threshold exceeded . . . . . . . . . . . . . . . . . 27-75 MMS 37 alarm slave HDSL modem loop 0 SNR OOS threshold exceeded . . . . . . . . . . . . . . . . . 27-78 MMS 38 alarm slave HDSL modem loop 1 SNR OOS threshold exceeded . . . . . . . . . . 27-81, 27-84, 27-86 MMS 4 alarm remote alarm daily threshold exceeded. . . . 27-13 MMS 41 alarm connectivity mismatch between BSC and RXCDR . . . . . . . . . . . . . . . 27-87, 27-89 MMS 5 alarm remote alarm hourly threshold exceeded . . . 27-15 MMS 6 alarm remote alarm OOS threshold exceeded. . . . 27-17 MMS 8 alarm frame slip daily threshold exceeded . . . . . 27-20 MMS 9 alarm frame slip hourly threshold exceeded . . . . 27-22, 27-24 MMS alarms FRUs . . . . . . . . . . . . . . . . . . . . 27-4 introduction . . . . . . . . . . . . . . . . . 27-3 mobile assignment failure from MS CELL 23, PM alarm . . . . . . . . . . . . 12-55 mobile assignment request from MSC protocol error BSS 7, PM alarm . . . . . . . . . . . . . . 6-20 Mobile Switching Centre (MSC) to BSS interface, layer 3 BSS alarms . . . . . . . . . . . . . . . . . 6-3 modem to NIU serial channel control link failure MMS 24 alarm. . . . . . . . . . . . . . . 27-48 MSC processor outage MTL 1 alarm . . . . . . . . . . . . . . . . 29-7 MSI 0 alarm re-initialized unexpectedly . . . . . . . . . . 28-4 MSI 1 alarm hard reset . . . . . . . . . . . . . . . . . . 28-6 MSI 11 - 40 alarms DSP channel audit failures . . . . . . . . . 28-19 MSI 2 alarm watchdog timer expired. . . . . . . . . . . . 28-8 MSI 224 alarm safe test audit failure . . . . . . . . . . . . 28-22
68P02901W26-Q 24 May 2004
Index
MSI 231 alarm TDM interface configuration failure . MSI 232 alarm processor bus communication failure MSI 234 active link connection failure . . . . MSI 254 alarm device failure . . . . . . . . . . . MSI 3 alarm clock B signal loss . . . . . . . . . MSI 4 alarm clock A signal loss . . . . . . . . . MSI 5 alarm assigned timeslot counter underflow . MSI 6 alarm assigned timeslot counter overflow . MSI 7 alarm TDM parity error. . . . . . . . . . MSI 9 alarm TRAU frame synchronization loss. . MSI alarms FRUs . . . . . . . . . . . . . . . introduction . . . . . . . . . . . . MSUs discarded due to SL congestion MTL 10, PM alarm. . . . . . . . . MTL 0 alarm signalling link failure. . . . . . . . MTL 0, PM alarm SL failure - all reasons . . . . . . . MTL 1 alarm MSC processor outage . . . . . . . MTL 1, PM alarm SL failure - abnormal FIBR/BSNR . MTL 10, PM alarm
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28-24 28-26 28-28 28-30 28-10 28-11 28-12 28-14 28-16 28-18
. . . . . 28-2 . . . . . 28-2 . . . . 29-22
. . . . . 29-3 . . . . . 29-6 . . . . . 29-7 . . . . . 29-8
MTL 10, PM alarm (contd.) MSUs discarded due to SL congestion . . . . 29-22 MTL 11, PM alarm SL congestion events resulting in loss of MSUs . . . . . . . . . . . . . . . . . . . 29-23 MTL 12, PM alarm SL congestion indications. . . . . . . . . . 29-24 MTL 2, PM alarm SL failure - excessive delay of ACK . . . . . . 29-9 MTL 3 alarm link traffic too high. . . . . . . . . . 26-14, 29-10 MTL 3, PM alarm SL failure - excessive error rate . . . . . . . 29-12 MTL 4, PM alarm SL failure - excessive duration of congestion . . . . . . . . . . . . . . . . . . . . 29-13 MTL 5, PM alarm SL alignment failure . . . . . . . . . . . . 29-14 MTL 6, PM alarm number of signal units in error . . . . . . . 29-16 MTL 7, PM alarm SLMTL 7, PM alarm . . . . . . . . . . . . 29-18 MTL 8, PM alarm start of remote processor outage . . . . . . . 29-20 MTL 9, PM alarm number of octets retransmitted . . . . . . . 29-21 MTL alarms introduction . . . . . . . . . . . . . . . . . 29-2 multicoupler failure IAS 41 alarm . . . . . . . . . . . . . . . 23-39 multicoupler main fuse failure IAS 22 alarm . . . . . . . . . . . . . . . 23-26 multicoupler redundant fuse failure IAS 23 alarm . . . . . . . . . . . . . . . 23-27
N
NE error state OMC 30006 alarm . . . . . . . . . . . . . 30-18 NE response timeout OMC 30005 alarm . . . . . . . . . . . . . 30-16 neighbour statistics table exceeded the configured size. Operator must take act . . . . . . . . . . . . 30-60 nmcAgentError OMC 30025 alarm . . . . . . . . . . . . . 30-57 no cell (BVC) block acknowledgement from the SGSN CELL 5 alarm . . . . . . . . . . . . . . . 12-20 no clock references available SITE 21 alarm . . . . . . . . . . . . . . . 38-53 no connection to alarm board - alarm board removed IAS 99 alarm . . . . . . . . . . . . 23-94, 23-96 no connection to alarm board - radio OOS IAS 97 alarm . . . . . . . . . . . . . . . 23-91 no connection to alarms board - connection broken IAS 94 alarm . . . . . . . . . . . . . . . 23-85 no MSC acknowledgement for circuit block BSS 5 alarm . . . . . . . . . . . . . . . . . 6-14 no MSC acknowledgement for circuit unblock BSS 6 alarm . . . . . . . . . . . . . . . . . 6-16 no MSC acknowledgement for global reset BSS 9 alarm . . . . . . . . . . . . . . . . . 6-24 no MSC acknowledgement for reset circuit BSS 7 alarm . . . . . . . . . . . . . . . . . 6-18 no NS-VC alive acknowledgement from the SGSN . . . . . . . . . . . . . . . . . . . . 38-85 no NS-VC Block acknowledgement from the SGSN . . . . . . . . . . . . . . . . . . . . 38-83
68P02901W26-Q 24 May 2004
IX-21
Index
no NS-VC reset acknowledgement from the SGSN . . . . . . . . . . . . . . . . . . . . 38-87 no NS-VC unblock acknowledgement from the SGSN . . . . . . . . . . . . . . . . . . . . 38-84 no redundant connection to alarms board - radio OOS IAS 98 alarm . . . . . . . . . . . . . . . 23-93 no SMLC acknowlegement for global reset BSS 52 alarm . . . . . . . . . . . . . . . . 6-62 noActivityInTimeslot OMC 30060 alarm . . . . . . . . . . . . . 30-91 non-volatile memory failure BTP 237 alarm. . . . . . . . . . . . . . . . 7-43
non-volatile memory failure (contd.) DRI 237 alarm . . . . . . . . . not operational GCLK 18 alarm . . . . . . . . number of calls queued CELL 20, PM alarm . . . . . . number of octets retransmitted MTL 9, PM alarm . . . . . . . number of signal units in error MTL 6, PM alarm . . . . . . . NVM board failure SITE 30 alarm . . . . . . . . .
. . . . . . 17-288 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-34 12-51 29-21 29-16 38-75
O
OIC . . . . . . . . . . . . . . OMC 30000 alarm downloadFailed . . . . . . . OMC 30001 alarm uploadFailed. . . . . . . . . OMC 30002 alarm filexferFailed . . . . . . . . OMC 30004 alarm parserDisconnectedTooLong . OMC 30005 alarm NE response timeout NE response tmeout . . . . OMC 30006 alarm NE error state . . . . . . . . OMC 30007 alarm PMDisconnectedFromDB . . OMC 30008 alarm EMDisconnectedFromDB . . OMC 30009 alarm dbCompressionFailed . . . . OMC 30010 alarm exceeds upper limit disk usage OMC 30011 alarm exceeds lower limit disk usage OMC 30012 alarm level 1/2/3 failure . . . . . . OMC 30014 alarm database exceeds upper limit . OMC 30015 alarm pmProxyDisconnectedFromDB OMC 30016 alarm osiStackError . . . . . . . . OMC 30017 alarm CSFPdownloadFailed . . . . OMC 30018 alarm dbUncompressionFailed . . . OMC 30019 alarm database exceeds lower limit . . . . . . . . . 1-12 . . . . . . . . 30-4 . . . . . . . . 30-6 . . . . . . . . 30-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-14 30-16 30-18 30-20 30-22 30-24 30-26 30-29 30-31 30-33 30-35 30-36 30-37 30-39 30-41 OMC 30020 alarm VersionQueryFailed . . . . . . . . . . . . OMC 30021 alarm OMC overloaded with events . . . . . . . . OMC 30022 alarm OMC overloaded, events discarded . . . . . OMC 30023 alarm downloadDisabled . . . . . . . . . . . . . OMC 30024 alarm CSFPSwapFailed . . . . . . . . . . . . . OMC 30025 alarm nmcAgentError . . . . . . . . . . . . . . OMC 30027 alarm supplDownloadFailed . . . . . . . . . . . OMC 30029 alarm active alarms exceed upper limit of . . . . . OMC 30030 alarm received maximum corrupt NE msgs, closed OML . . . . . . . . . . . . . . . . . . . OMC 30031 alarm resync timed out, no response from NE . . . OMC 30032 alarm resync timed out, all resync events not received . . . . . . . . . . . . . . . . . . OMC 30035 alarm advisory detected . . . . . . . . . . . . . OMC 30036 alarm recovered outage detected . . . . . . . . . OMC 30037 alarm UPS condition . . . . . . . . . . . . . . . OMC 30050 alarm Solaris2 hardware failure . . . . . . . . . . OMC 30051 alarm corrupt NE file . . . . . . . . . . . . . . . OMC 30052 alarm corrupt SITE file . . . . . . . . . . . . . . OMC 30060 alarm noActivityInTimeslot. . . . . . . . . . . . 30-43 30-49 30-51 30-53 30-55 30-57 30-62 30-66 30-68 30-71 30-73 30-78 30-79 30-80 30-86 30-89 30-90 30-91
IX-22
68P02901W26-Q 24 May 2004
Index
OMC 30064 alarm Memory usage exceeds upper limit . . . . . 30-65 OMC 3008 alarm, EMDisconnectedFromDB . . 30-22 OMC 3033 alarm. . . . . . . . . . . . . . . 30-75 OMC alarm formats . . . . . . . . . . . . . . 1-7 OMC alarms introduction . . . . . . . . . . . . . . . . . 30-3 OMC overloaded with events OMC 30021 alarm . . . . . . . . . . . . . 30-49 OMC overloaded, events discarded OMC 30022 alarm . . . . . . . . . . . . . 30-51 OMC-R map display modes device mode . . . . . . . . . . . . . . . . . 1-19 subscriber mode . . . . . . . . . . . . . . . 1-19 OML 0, PM alarm invalid received frames . . . . . . . . . . . . 31-3 OML 1, PM alarm FRMR-frames . . . . . . . . . . . . . . . . 31-4 OML 2, PM alarm expiration of N2 . . . . . . . . . . . . . . . 31-5 OML alarms introduction . . . . . . . . . . . . . . . . . 31-2 OOS device list . . . . . . . . . . . . . . . . 1-17 format. . . . . . . . . . . . . . . . . . . . 1-17 optocoupler 1 EAS 16 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 10 EAS 25 alarm . . . . . . . . . . . 18-9 to 18-10 optocoupler 11 EAS 26 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 12 EAS 27 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 13 EAS 28 alarm . . . . . . . . . . . . . . . . 18-9
optocoupler 14 EAS 29 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 15 EAS 30 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 16 EAS 31 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 2 EAS 17 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 3 EAS 18 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 4 EAS 19 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 5 EAS 20 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 6 EAS 21 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 7 EAS 22 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 8 EAS 23 alarm . . . . . . . . . . . . . . . . 18-9 optocoupler 9 EAS 24 alarm . . . . . . . . . . . . . . . . 18-9 osiStackError OMC 30016 alarm . . . . . . . . . . . . . 30-36 output failure BCUP 8 alarm . . . . . . . . . . . . . . . . 4-5 over 50% of board detected clock failure CBUS 0 alarm . . . . . . . . . . . . . . . . 11-3 over temperature warning BCUP 10 alarm . . . . . . . . . . . . . . . 4-7 over-temperature - component damage imminent CAGE 40 alarm . . . . . . . . . . . . . . . 9-15 overview alarms. . . . . . . . . . . . . . . . . . . . 1-3
P
paging request from MSC protocol error BSS 0, PM alarm . . . . . . . . . . paging request from SMLC protocol error BSS 20, PM alarm . . . . . . . . . . parity highway 0 KSW 0 alarm . . . . . . . . . . . . parity highway 1 KSW 1 alarm . . . . . . . . . . . . parity highway 2 KSW 2 alarm . . . . . . . . . . . . parity highway 3 KSW 3 alarm . . . . . . . . . . . . parserDisconnectedTooLong OMC 30004 alarm . . . . . . . . . . . . . . 6-7 partial reset COMB 10 alarm . . . PBUS 254 alarm device failure . . . . PBUS alarms introduction . . . . . PCH queue page discard CELL 24, PM alarm . PCMCIA card removed CSFP 240 alarm . . . PCU 0 alarm last GSL failed. . . . PCU 1 alarm PCU audit failure . . PCU alarms introduction . . . . . . . . . . . . . . . . 13-16
. . . . 6-31 . . . . 24-4 . . . . 24-8 . . . . . . . . . 24-10 24-12 30-14
. . . . . . . . . . . . 32-3 . . . . . . . . . . . . 32-2 . . . . . . . . . . . . . . . . . . . . . . 12-57 14-12
. . . . . . . . . . . . 33-3 . . . . . . . . . . . . 33-5 . . . . . . . . . . . . 33-2
68P02901W26-Q 24 May 2004
IX-23
Index
PCU audit failure PCU 1 alarm. . . . . . . . . . . . . . . . . 33-5 Performance Management (PM) alarms . . . . . 1-2 persistent fault . . . . . . . . . . . . . . . . 17-62 phase lock failure GCLK 14 alarm . . . . . . . . . . . . . . 20-25 phase lock lost GCLK 4 alarm . . . . . . . . . . . . . . . . 20-8 PMDisconnectedFromDB OMC 30007 alarm . . . . . . . . . . . . . 30-20 pmProxyDisconnectedFromDB OMC 30015 alarm . . . . . . . . . . . . . 30-35 power amplier error DRI 73 alarm . . . . . . . . . . . . . . . 17-120 power amplifier communication failure DRI 89 alarm . . . . . . . . . . . . . . . 17-145 power amplifier failure DRI 215 alarm . . . . . . . . . . . . . . . 17-270 power amplifier power low but functioning DRI 91 alarm . . . . . . . . . . . . . . . 17-149 power amplifier temperature DRI 208 alarm . . . . . . . . . . . . . . . 17-259 power amplifier temperature high DRI 88 alarm . . . . . . . . . . . . . . . 17-143 power amplifier temperature high but functioning DRI 92 alarm . . . . . . . . . . . . . . . 17-151 power feed A failure COMB 7 alarm . . . . . . . . . . . . . . . 13-9 power feed B failure COMB 8 alarm . . . . . . . . . . . . . . 13-11 power mains failure TRU 2 alarm. . . . . . . . . . . . . . . . . 41-6 power supply failure DRI 154 alarm . . . . . . . . . . . . . . . 17-210 power supply temperature high IAS 101 alarm . . . . . . . . . . . . . . . 23-98 power supply unit - input failure IAS 80 alarm . . . . . . . . . . . . . . . 23-62 power supply unit - output failure IAS 81 alarm . . . . . . . . . . . . . . . 23-64 power supply unit 0 failure IAS 1 alarm . . . . . . . . . . . . . . . . . 23-9 power supply unit 1 failure IAS 9 alarm . . . . . . . . . . . . . . . . 23-11 power supply unit 2 failure IAS 10 alarm . . . . . . . . . . . . . . . 23-13 power supply unit 3 failure IAS 11 alarm . . . . . . . . . . . . . . . 23-15 power supply unit failure TRU 1 alarm. . . . . . . . . . . . . . . . . 41-4 power supply unit#1 fan failure CAGE 34 alarm . . . . . . . . . . . . . . . 9-12 power supply unit#1 over-temperature CAGE 37 alarm . . . . . . . . . . . . . . . 9-13
power supply unit#1not detected CAGE 31 alarm . . . . . . . . . . . . power supply unit#1output failure CAGE 28 alarm . . . . . . . . . . . . power supply unit#2 fan failure CAGE 35 alarm . . . . . . . . . . . . power supply unit#2 not detected CAGE 32 alarm . . . . . . . . . . . . power supply unit#2 output failure CAGE 29 alarm . . . . . . . . . . . . power supply unit#2 over-temperature CAGE 38 alarm . . . . . . . . . . . . power supply unit#3 fan failure CAGE 36 alarm . . . . . . . . . . . . power supply unit#3 not detected CAGE 33 alarm . . . . . . . . . . . . power supply unit#3 output failure CAGE 30 alarm . . . . . . . . . . . . power supply unit#3 over-temperature CAGE 39 alarm . . . . . . . . . . . . primary alarm . . . . . . . . . . . . . . primary message or hardware interrupt error DRI 18 alarm . . . . . . . . . . . . . process safe test audit failure BSP 239 alarm . . . . . . . . . . . . . BTP 239 alarm. . . . . . . . . . . . . DHP 239 alarm . . . . . . . . . . . . DPROC 239 alarm . . . . . . . . . . . DRI 239 alarm . . . . . . . . . . . . . GPROC 239 alarm . . . . . . . . . . . PSP 239 alarm . . . . . . . . . . . . . processor A failure COMB 14 alarm . . . . . . . . . . . . processor B failure COMB 15 alarm . . . . . . . . . . . . processor bus communication failure GCLK 232 alarm. . . . . . . . . . . . KSW 232 alarm . . . . . . . . . . . . MSI 232 alarm . . . . . . . . . . . . . processor communication failure DPROC 0 alarm . . . . . . . . . . . . processor failure DRI 29 alarm . . . . . . . . . . . . . PSP 0 alarm, Communication Failure . . . PSP 22 alarm SWFM indication . . . . . . . . . . . PSP 239 alarm process safe test audit failure . . . . . . PSP 39 alarm software failure . . . . . . . . . . . . PSP alarms FRUs . . . . . . . . . . . . . . . . . introduction . . . . . . . . . . . . . .
. . . 9-11 . . . 9-9
. . . 9-12 . . . 9-11 . . . 9-9
. . . 9-13 . . . 9-12 . . . 9-11 . . . 9-9
. . . 9-13 . . . 1-5 . . . . . . . . . . . . . . . . 17-31 . 5-34 . 7-45 15-55 . 16-9 17-290 21-47 . 35-7 13-24 13-26 20-48 24-50 28-26
. . . . . . . . . .
. . . 16-3 . . 17-52 . . . 35-3 . . . 35-5 . . . 35-7 . . . 35-6 . . . 35-2 . . . 35-2
IX-24
68P02901W26-Q 24 May 2004
Index
Q
Q3 agent . . . . . . . . . . . . . . . . . . . . 1-7
R
radio frequency losses while using a TCH TIMESLOT 0, PM alarm . . . . . . . . . . . 40-3 radio frequency losses while using an SDCCH CELL 0, PM alarm . . . . . . . . . . . . . . 12-7 radio subsystem software to DRI communication error . . . . . . . . . . . . . . . . . . . . . 17-124 radio subsystem software to DRI communication error checksum error DRI 65 alarm . . . . . . . . . . . . . . . 17-107 radio subsystem software to DRI communication failure DRI 23 alarm . . . . . . . . 17-37 to 17-38, 17-40 RCU #5 circuit breaker failure IAS 61 alarm . . . . . . . . . . . . . . . 23-51 re-initialized unexpectedly KSW 7 alarm . . . . . . . . . . . . . . . 24-24 MSI 0 alarm . . . . . . . . . . . . . . . . . 28-4 receive matrix branch 1 control link failure DRI 150 alarm . . . . . . . . . . . . . . . 17-202 receive matrix branch 2 control link failure DRI 162 alarm . . . . . . . . . . . . . . . 17-226 received maximum corrupt NE msgs, closed OML OMC 30030 alarm . . . . . . . . . . . . . 30-68 received page for invalid cell from MSC BSS 26 alarm . . . . . . . . . . . . . . . . 6-36 received page for invalid cell from SMLC received page for invalid cell from SMLC MSC . . . . . . . . . . . . . . . . . . . . 6-65 receiver failure DRI 119 alarm . . . . . . . . . . . . . . . 17-171 DRI 120 alarm . . . . . . . . . . . . . . . 17-173 DRI 121 alarm . . . . . . . . . . . . . . . 17-175 DRI 122 alarm . . . . . . . . . . . . . . . 17-177 DRI 123 alarm . . . . . . . . . . . . . . . 17-179 DRI 124 alarm . . . . . . . . . . . . . . . 17-181 DRI 125 alarm . . . . . . . . . . . . . . . 17-183 DRI 126 alarm . . . . . . . . . . . . . . . 17-185 DRI 127 alarm . . . . . . . . . . . . . . . 17-187 DRI 128 alarm . . . . . . . . . . . . . . . 17-189 DRI 72 alarm . . . . . . . . . . . . . . . 17-118 receiver input overflowed DRI 157 alarm . . . . . . . . . . . . . . . 17-216 DRI 158 alarm . . . . . . . . . . . . . . . 17-218 receiver synthesizer failure DRI 112 alarm . . . . . . . . . . . . . . . 17-157 DRI 113 alarm . . . . . . . . . . . . . . . 17-159 DRI 114 alarm . . . . . . . . . . . . . . . 17-161 DRI 115 alarm . . . . . . . . . . . . . . . 17-163 68P02901W26-Q 24 May 2004 receiver synthesizer failure (contd.) DRI 116 alarm . . . . . . . . . . . . . . . 17-165 DRI 117 alarm . . . . . . . . . . . . . . . 17-167 DRI 118 alarm . . . . . . . . . . . . . . . 17-169 reconfiguration information . . . . . . . . . . . . . . . . . 1-13 recovered outage detected OMC 30036 alarm . . . . . . . . . . . . . 30-79 rectifier failure . . . . . . . . . . . . . . . . 23-119 IAS 106 alarm . . . . . . . . . . . . . . . 23-107 recurring fault . . . . . . . . . . . . . . . . 17-62 red alarm daily threshold exceeded MMS 20 alarm. . . . . . . . . . . . . . . 27-38 red alarm hourly threshold exceeded MMS 21 alarm. . . . . . . . . . . . . . . 27-40 red alarm OOS threshold exceeded MMS 22 alarm. . . . . . . . . . . . . . . 27-42 red alarm OOS timer expired MMS 23 alarm. . . . . . . . . . . . . . . 27-45 reference count overflow 125 us GCLK 5 alarm . . . . . . . . . . . . . . . 20-11 reference count overflow 6.12s GCLK 7 alarm . . . . . . . . . . . . . . . 20-15 reference count overflow 60ms GCLK 6 alarm . . . . . . . . . . . . . . . 20-13 reference distribution module failure GCLK 0 alarm . . . . . . . . . . . . . . . . 20-3 remote alarm daily threshold exceeded MMS 4 alarm . . . . . . . . . . . . . . . 27-13 remote alarm hourly threshold exceeded MMS 5 alarm . . . . . . . . . . . . . . . 27-15 remote alarm OOS threshold exceeded MMS 6 alarm . . . . . . . . . . . . . . . 27-17 remote alarm OOS timer expired MMS 18 alarm. . . . . . . . . . . . . . . 27-35 remote KSW loopback test failure TBUS 0 alarm . . . . . . . . . . . . . . . . 39-3 remote KSWX slot 2 communication failure 4. CAGE alarm . . . . 9-20, 9-23, 9-26, 9-29, 9-32 remote KSWX TDM error TBUS 2 alarm . . . . . . . . . . . . . . . . 39-6 reset due to recurring fault DRI 35 alarm . . . . . . . . . . . . . . . 17-62 reset, site requested alarm Process Identifier (PID) numbers list of . . . . . . . . . . . . . . . . . . 38-60
IX-25
Index
resync timed out, all resync events not received OMC 30032 alarm . . . . . . . . . . . . . resync timed out, no response from NE OMC 30031 alarm . . . . . . . . . . . . . routing failure - reason unknown BSS 2, PM alarm . . . . . . . . . . . . . routing failure - syntax error detected BSS 18, PM alarm . . . . . . . . . . . . . BSS1, PM alarm BSS 1, PM alarm . . . . . . . . . . . . RSL 0, PM alarm invalid received frames . . . . . . . . . . .
30-73 30-71 . 6-11 . 6-30 . 6-9
. 36-3
RSL 1, PM alarm FRMR-frames . . . . . . . . . . . . . RSL 10 alarm link disconnected . . . . . . . . . . . RSL 11 alarm LAPD protocol error . . . . . . . . . . RSL 13 alarm LAPD protocol error threshold exceeded. RSL 14 alarm link audit failure . . . . . . . . . . . . RSL 2, PM alarm expiration of N2 . . . . . . . . . . . . RSL alarms introduction . . . . . . . . . . . . . .
. . . 36-4 . . . 36-6 . . . . . . 36-14 36-17 36-19
. . . 36-5 . . . 36-2
S
safe test audit failure DRI 224 alarm . . . . . . . . . . . KSW 224 alarm . . . . . . . . . . MSI 224 alarm . . . . . . . . . . . SBUS 254 alarm device failure . . . . . . . . . . . SBUS alarms introduction . . . . . . . . . . . . second reference loss 6.12s KSW 6 alarm . . . . . . . . . . . secondary . . . . . . . . . . . . . . secondary alarms . . . . . . . . . . . serial bus connection failure BCUP 1 alarm . . . . . . . . . . . EAS 1 alarm . . . . . . . . . . . . IAS 1 alarm . . . . . . . . . . . . signalling link failure LMTL 0 alarm . . . . . . . . . . . MTL 0 alarm . . . . . . . . . . . SITE 0 alarm last RSL link failure . . . . . . . . SITE 10 alarm standby local FOX failure . . . . . SITE 11 alarm active remote FOX 0 failure . . . . SITE 12 alarm standby remote FOX 0 failure . . . . SITE 13 alarm active remote FOX 1 failure . . . . SITE 14 alarm standby remote FOX 1 failure . . . . SITE 15 alarm active remote FOX 2 failure . . . . SITE 16 alarm standby remote FOX 2 failure . . . . SITE 17 alarm 16Kbps switching hardware required IX-26 . . . . 17-277 . . . . 24-45 . . . . 28-22 . . . . . 37-3 . . . . . 37-2 . . . . 24-22 . . . . . 1-14 . . . . . 1-5 . . . . . 4-4 . . . . . 18-5 . . . . . 23-6 . . . . . 26-3 . . . . . 29-3 . . . . . 38-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38-29 38-31 38-33 38-35 38-37 38-39 38-41 38-43 SITE 19 alarm unequipped GPROC has entered the LAN . . 38-46 SITE 2 alarm BSC detected MCU to MCU communication failure . . . . . . . . . . . . . . . . . . . 38-12 SITE 20 alarm unequipped GPROC has left the LAN . . . . 38-49 SITE 21 alarm no clock references available . . . . . . . . 38-53 SITE 22 alarm active alarm list full . . . . . . . . . . . . 38-56 SITE 24 alarm site reset request . . . . . . . . . . . . . . 38-59 SITE 25 alarm external power booster amplifier 1 failure . . 38-63 SITE 26 alarm external power booster amplifier 2 failure . . 38-65 SITE 27 alarm external power booster failure. . . . . . . . 38-67 SITE 28 alarm database configuration and Arena hardware mismatch . . . . . . . . . . . . . . 38-69, 38-72 SITE 3 alarm active multiplexer 0 loopback failure . . . . 38-15 SITE 30 alarm NVM board failure . . . . . . . . . . . . . 38-75 SITE 31 alarm failure of PCMCIA Card 1 on NVM board . . 38-76 SITE 36 alarm, Erroneous Network Service Message Received... SITE: Erroneous Network Service Message Received... . . . . . . . . . . . . . . . . 38-82 SITE 4 alarm standby multiplexer 0 loopback failure. . . . 38-17 SITE 42 alarm, Last PRP DPROC Failed. . . . 38-92 SITE 5 alarm
68P02901W26-Q 24 May 2004
Index
SITE 5 alarm (contd.) active multiplexer 1 loopback failure . . . . 38-19 SITE 6 alarm standby multiplexer 1 loopback failure. . . . 38-21 SITE 7 alarm active multiplexer 2 loopback failure . . . . 38-23 SITE 8 alarm standby multiplexer 2 loopback failure. . . . 38-25 SITE 9 alarm active local FOX failure . . . . . . . . . . 38-27 SITE alarms introduction . . . . . . . . . . . . . . . . . 38-3 site reset occurred due to front panel reset BTP 42 alarm . . . . . . . . . 7-28 to 7-29, 7-31 GPROC 42 alarm . . . . . . . . . . 21-35, 21-40 site reset request SITE 24 alarm . . . . . . . . . . . . . . . 38-59 site reset requested Process Identifier (PID) numbers list of . . . . . . . . . . . . . . . . . . 38-60 SL alignment failure LMTL 5, PM alarm . . . . . . . . . . . . 26-20 MTL 5, PM alarm . . . . . . . . . . . . . 29-14 SL congestion events resulting in loss of MSUs LMTL 11, PM alarm . . . . . . . . . . . . 26-30 MTL 11, PM alarm. . . . . . . . . . . . . 29-23 SL congestion indications LMTL 12, PM alarm . . . . . . . . . . . . 26-31 MTL 12, PM alarm. . . . . . . . . . . . . 29-24 SL failure - abnormal FIBR/BSNR LMTL 1, PM alarm . . . . . . . . . . . . 26-10 MTL 1, PM alarm . . . . . . . . . . . . . . 29-8 SL failure - all reasons LMTL 0, PM alarm . . . . . . . . . . . . . 26-6 MTL 0, PM alarm . . . . . . . . . . . . . . 29-6 SL failure - excessive delay of ACK MTL 2, PM alarm . . . . . . . . . . . . . . 29-9 SL failure - excessive duration of congestion LMTL 4, PM alarm . . . . . . . . . . . . 26-18 MTL 4, PM alarm . . . . . . . . . . . . . 29-13 SL failure - excessive error rate MTL 3, PM alarm . . . . . . . . . . . . . 29-12 SL number of negative acks received MTL 7, PM alarm . . . . . . . . . . . . . 29-18 slave HDSL modem loop 0 SNR daily threshold exceeded MMS 29 alarm. . . . . . . . . . . . . . . 27-60 slave HDSL modem loop 0 SNR hourly threshold exceeded MMS 33 alarm. . . . . . . . . . . . . . . 27-68 slave HDSL modem loop 0 SNR OOS threshold exceeded MMS 37 alarm. . . . . . . . . . . . . . . 27-78 slave HDSL modem loop 1 SNR daily threshold exceeded 68P02901W26-Q 24 May 2004
slave HDSL modem loop 1 SNR daily threshold exceeded (contd.) MMS 30 alarm. . . . . . . . . . . . . . . 27-62 slave HDSL modem loop 1 SNR hourly threshold exceeded MMS 34 alarm. . . . . . . . . . . . . . . 27-70 slave HDSL modem loop 1 SNR OOS threshold exceeded MMS 38 alarm. . . . . . . . 27-81, 27-84, 27-86 slow flash failure BTP 236 alarm. . . . . . . . . . . . . . . . 7-41 DRI 236 alarm . . . . . . . . . . . . . . . 17-286 SMLC processor outage LMTL 1 alarm . . . . . . . . . . . . . . . . 26-8 smoke alarm IAS 92 alarm . . . . . . . . . . . . . . . 23-81 software failure BSP 39 alarm . . . . . . . . . . . . . . . . 5-23 BTP 39 alarm . . . . . . . . . . . . . . . . 7-24 DHP 39 alarm . . . . . . . . . . . . . . . 15-35 DPROC 39 alarm . . . . . . . . . . . . . . 16-8 GPROC 39 alarm . . . . . . . . . . . . . 21-31 PSP 39 alarm . . . . . . . . . . . . . . . . 35-6 Solaris2 hardware failure OMC 30050 alarm . . . . . . . . . . . . . 30-86 spare fuse failure IAS 30 alarm . . . . . . . . . . . . . . . 23-30 spurious GSM timeslot interrupt DRI 50 alarm . . . . . . . . . . . . . . . 17-76 spurious interrupt BSP 40 alarm . . . . . . . . . . 5-25, 5-27, 5-29 BTP 40 alarm . . . . . . . . . 7-26, 7-32 to 7-33 DHP 40 alarm . . . . . . . . . . . . . . . 15-37 GPROC 40 alarm . . . . . . . . . . . . . 21-33 standby link connected to wrong device DRI 241 alarm . . . . . . . . . . . . . . . 17-292 standby link connection failure BTP 235 alarm. . . . . . . . . . . . . . . . 7-38 DRI 235 alarm . . . . . . . . . . . . . . . 17-284 standby local FOX failure SITE 10 alarm . . . . . . . . . . . . . . . 38-29 standby multiplexer 0 loopback failure SITE 4 alarm . . . . . . . . . . . . . . . 38-17 standby multiplexer 1 loopback failure SITE 6 alarm . . . . . . . . . . . . . . . 38-21 standby multiplexer 2 loopback failure SITE 8 alarm . . . . . . . . . . . . . . . 38-25 standby remote FOX 0 failure SITE 12 alarm . . . . . . . . . . . . . . . 38-33 standby remote FOX 1 failure SITE 14 alarm . . . . . . . . . . . . . . . 38-37 standby remote FOX 2 failure SITE 16 alarm . . . . . . . . . . . . . . . 38-41 start of remote processor outage MTL 8, PM alarm . . . . . . . . . . . . . 29-20 IX-27
Index
state change warning alarms. . . . . . super frame counter error DRI 5 alarm . . . . . . . . . . . . superframe counter error DRI 6 alarm . . . . . . . . . . . . DRI 66 alarm . . . . . . . . . . . supplDownloadFailed OMC 30027 alarm . . . . . . . . . SWFM indication BSP 22 alarm . . . . . . . . . . . BTP 22 alarm . . . . . . . . . . . CSFP 22 alarm. . . . . . . . . . . DHP 22 alarm . . . . . . . . . . . DPROC 22 alarm . . . . . . . . . GPROC 22 alarm . . . . . . . . . PSP 22 alarm . . . . . . . . . . . switching hardware required kb/s switching hardware required 16kb/s . SYNC calibration request DHP 26 alarm . . . . . . . . . . . SYNC calibration via firmware initiated DHP 44 alarm . . . . . . . . . . . SYNC clock output failure DHP 28 alarm . . . . . . . . . . . SYNC invalid mode
. . . . . . . . .
1-7 17-13
. . . . 17-15 . . . . 17-110 . . . . . . . . . 30-62
. . . . 5-10 . . . . 7-11 . . . . 14-3 . . . 15-10 . . . . 16-7 21-11 to 21-18 . . . . . 35-5 . . . . . . . . . . . . . . . . 38-43 15-16 15-41 15-20
SYNC invalid mode (contd.) DHP 46 alarm . . . . . . . . . . . . 15-44, 15-46 SYNC lost phase lock to master GCLK DHP 23 alarm . . . . . . . . . . . . . . . 15-11 SYNC not operational DHP 43 alarm . . . . . . . . . . . . . . . 15-39 SYNC phase lock failure DHP 45 alarm . . . . . . . . . . . . . . . 15-42 SYNC shutdown request DHP 27 alarm . . . . . . . . . . . . . . . 15-18 GCLK 17 alarm . . . . . . . . . . . . . . 20-32 SYNC warmup failure DHP 25 alarm . . . . . . . . . . . . . . . 15-15 SYNC watchdog timer expired DHP 29 alarm . . . . . . . . . . . . . . . 15-22 synchronization loss daily threshold exceeded MMS 0 alarm . . . . . . . . . . . . . . . . 27-6 synchronization loss hourly threshold exceeded MMS 1 alarm . . . . . . . . . . . . . . . . 27-8 synchronization loss OOS threshold exceeded MMS 2 alarm . . . . . . . . . . . . . . . 27-10 synchronization loss OOS timer expired MMS 16 alarm. . . . . . . . . . . . . . . 27-32 synchronization loss with MCU DRI 39 alarm . . . . . . . . . . . . . . . 17-68
IX-28
68P02901W26-Q 24 May 2004
Index
T
tagged alarm format . . . . . . . . . . . . . . 1-6 TBUS 0 alarm remote KSW loopback test failure . . . . . . . 39-3 TBUS 1 alarm local KSWX TDM error . . . . . . . . . . . 39-5 TBUS 2 alarm remote KSWX TDM error . . . . . . . . . . 39-6 TBUS alarms introduction . . . . . . . . . . . . . . . . . 39-2 TDM interface configuration failure BSP 231 alarm. . . . . . . . . . . . . . . . 5-32 BTP 231 alarm. . . . . . . . . . . . . . . . 7-34 DHP 231 alarm . . . . . . . . . . . . . . 15-51 DRI 231 alarm . . . . . . . . . . . . . . . 17-279 GPROC 231 alarm . . . . . . . . . . . . . 21-45 MSI 231 alarm. . . . . . . . . . . . . . . 28-24 TDM interface failure - assigned timeslot counter overflow BSP 33 alarm . . . . . . . . . . . . . . . . 5-17 BTP 33 alarm . . . . . . . . . . . . . . . . 7-18 DHP 33 alarm . . . . . . . . . . . . . . . 15-29 DRI 25 alarm . . . . . . . . . . . . . . . 17-44 GPROC 33 alarm . . . . . . . . . . . . . 21-25 TDM interface failure - assigned timeslot counter underflow BSP 32 alarm . . . . . . . . . . . . . . . . 5-15 BTP 32 alarm . . . . . . . . . . . . . . . . 7-16 DHP 32 alarm . . . . . . . . . . . . . . . 15-27 DRI 26 alarm . . . . . . . . . . . . . . . 17-46 GPROC 32 alarm . . . . . . . . . . . . . 21-23 TDM interface failure - TDM parity error BSP 34 alarm . . . . . . . . . . . . . . . . 5-19 BTP 34 alarm . . . . . . . . . . . . . . . . 7-20 DHP 34 alarm . . . . . . . . . . . . . . . 15-31 DRI 24 alarm . . . . . . . . . . . . . . . 17-42 GPROC 34 alarm . . . . . . . . . . . . . 21-27 TDM parity error MSI 7 alarm . . . . . . . . . . . . . . . . 28-16 TIMESLOT 0, PM alarm radio frequency losses while using a TCH . . . 40-3 TIMESLOT 1, PM alarm channel request from MS failed . . . . . . . . 40-5 TIMESLOT alarms introduction . . . . . . . . . . . . . . . . . 40-2 transceiver processor failure DRI 213 alarm . . . . . . . . . . . . . . . 17-266 transceiver re-initialized unexpectedly DRI 30 alarm . . . . . . . . . . . . . . . 17-54 transceiver recovery failure DRI 216 alarm . . . . . . . . . . . . . . . 17-272 transceiver synthesizer failure DRI 80 alarm . . . . . . . . . . . . . . . 17-127 transceiver to combiner communication failure DRI 151 alarm . . . . . . . . . . . . . . . 17-204 transceiver to DRI burst error DRI 59 alarm . . . . . . . . . . . . . . . 17-95 DRI 60 alarm . . . . . . . . . . . . . . . 17-97 transceiver to DRI communication error DRI 58 alarm . . . . . . . . . . . . . . . 17-93 DRI 61 alarm . . . . . . . . . . . . . . . 17-99 DRI 62 alarm . . . . . . . . . . . . . . . 17-101 DRI 63 alarm . . . . . . . . . . . . . . . 17-103 transceiver to DRI communication failure DRI 144 alarm . . . . . . . . . . . . . . . 17-191 DRI 147 alarm . . . . . . . . . . . . . . . 17-196 DRI 148 alarm . . . . . . . . . . . . . . . 17-198 DRI 149 alarm . . . . . . . . . . . . . . . 17-200 DRI 155 alarm . . . . . . . . . . . . . . . 17-212 DRI 163 alarm . . . . . . . . . . . . . . . 17-228 DRI 164 alarm . . . . . . . . . . . . . . . 17-230 DRI 165 alarm . . . . . . . . . . . . . . . 17-232 DRI 169 alarm . . . . . . . . . . . . . . . 17-240 DRI 57 alarm . . . . . . . . . . . . . . . 17-91 Transceiver to DRI Communication Failure 169. DRI . . . . . . . . . . . . . . . . . 17-240 transceiver to DRI communications failure DRI 146 alarm . . . . . . . . . . . . . . . 17-194 transmission suspended to conserve battery power DRI 217 alarm . . . . . . . . . . . . . . . 17-273 transmitter failure - output power DRI 85 alarm . . . . . . . . . . . . . . . 17-137 DRI 86 alarm . . . . . . . . . . . . . . . 17-139 DRI 87 alarm . . . . . . . . . . . . . . . 17-141 DRI 90 alarm . . . . . . . . . . . . . . . 17-147 DRI 93 alarm . . . . . . . . . . . . . . . 17-153 transmitter out of synchronization DRI 161 alarm . . . . . . . . . . . . . . . 17-224 transmitter synthesizer failure DRI 81 alarm . . . . . . . . . . . . . . . 17-129 DRI 82 alarm . . . . . . . . . . . . . . . 17-131 DRI 83 alarm . . . . . . . . . . . . . . . 17-133 DRI 84 alarm . . . . . . . . . . . . . . . 17-135 TRAU frame synchronization loss MSI 9 alarm . . . . . . . . . . . . . . . . 28-18 TRU 0 alarm door open . . . . . . . . . . . . . . . . . . 41-3 TRU 1 alarm power supply unit failure . . . . . . . . . . . 41-4 TRU 2 alarm power mains failure . . . . . . . . . . . . . 41-6 TRU alarms introduction . . . . . . . . . . . . . . . . . 41-2 trunk critical threshold exceeded
68P02901W26-Q 24 May 2004
IX-29
Index
trunk critical threshold exceeded (contd.) BSS 22 alarm . . . . . . . . . . . . . . . . 6-34
trunk major threshold exceeded BSS 21 alarm . . . . . . . . . . . . . . . . 6-32 tx vswr antenna fault IAS 12 alarm . . . . . . . . . . . . . . . 23-17
U
unequipped circuit at the BSS BSS 12 alarm . . . . . . . . . . . . . . . . 6-27 unequipped circuit at the MSC BSS 8 alarm . . . . . . . . . . . . . . . . . 6-22 unequipped GPROC has entered the LAN SITE 19 alarm . . . . . . . . . . . . . . . 38-46 unequipped GPROC has left the LAN SITE 20 alarm . . . . . . . . . . . . . . . 38-49 unexpected board type BCUP 0 alarm . . . . . . . . . . . . . . . . 4-3 EAS 0 alarm . . . . . . . . . . . . . . . . . 18-3 IAS 0 alarm . . . . . . . . . . . . . . . . . 23-5 unexpected board type: GPROC2 or GPROC3 is required DHP 41 alarm . . . . . 5-30 to 5-31, 14-7, 14-10 to 14-11, 15-48 to 15-50, 21-42 to 21-44 unexpected communications bus interrupt DRI 71 alarm . . . . . . . . . . . . unlocked device not in service DRI 243 alarm . . . . . . . . . . . . unrecognized hardware revision level GCLK 12 alarm . . . . . . . . . . . unrecoverable error DRI 64 alarm . . . . . . . . . . . . untagged alarm format . . . . . . . . . uploadFailed OMC 30001 alarm . . . . . . . . . . UPS condition OMC 30037 alarm . . . . . . . . . . urgent critical alarm IAS 110 alarm . . . . . . . . . . . . . . . 17-116 . . . 17-294 . . . 20-24
. . . 17-105 . . . . 1-4 . . . . 30-6 . . . 30-80
. . . 23-114
V
VersionQueryFailed OMC 30020 alarm . . . . . . . . . . . . . 30-43 voltage standing wave ratio performance low IAS 91 alarm . . . . . . . . . . . . . . . 23-79
W
warmup failure GCLK 19 alarm . . . . . . . . . . . . . . 20-36 watchdog timer expired GCLK 15 alarm . . . . . . . . . . . . . . 20-28 KSW 9 alarm . . . . . . . . . . . . . . . 24-29 MSI 2 alarm . . . . . . . . . . . . . . . . . 28-8
X
x25CircuitDown OMC 30003 alarm . . . XBL 0, PM alarm invalid received frames . XBL 1, PM alarm FRMR-frames . . . . . XBL 10 alarm link disconnected . . . XBL 11 alarm LAPD protocol error . . . . . . . . . . . . 30-11 XBL 12 alarm link traffic too high. . . . . . . . . . . XBL 13 alarm LAPD protocol error threshold exceeded. XBL 2, PM alarm expiration of N2 . . . . . . . . . . . . XBL alarms introduction . . . . . . . . . . . . . . XCDR alarms . . . . . . . . . . . . . . . . . . 42-14 42-11
. . . . . . . . . . . 42-3 . . . . . . . . . . . 42-4 . . . . . . . . . . . 42-6 . . . . . . . . . . . 42-9
. . . 42-5 . . . 42-2 . . . 28-2
IX-30
68P02901W26-Q 24 May 2004

Alarms

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Alarms

Caricato da

Copyright:

Formati disponibili

Maintenance Information: Alarm Handling at the OMC-R

1994-2004 Motorola, Inc. All Rights Reserved

68P02901W26-Q 24 May 2004

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

9. BCUP: Input Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10. BCUP: Over Temperature Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5: BSP alarms

Chapter 6: BSS alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

Chapter 7: BTP alarms

Chapter 8: CAB alarms

Chapter 9: CAGE alarms

Chapter 10: CBL alarms

Chapter 11: CBUS alarms

Chapter 12: CELL alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

18. 19. 20. 22. 23. 24. 25.

12-47 12-49 12-51 12-53 12-55 12-57 12-59

Chapter 13: COMB alarms

Chapter 14: CSFP alarms

Chapter 15: DHP alarms

Chapter 16: DPROC alarms

Chapter 17: DRI alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

Chapter 18: EAS alarms

Chapter 19: GBL alarms

Chapter 20: GCLK alarms

68P02901W26-Q 24 May 2004

Chapter 21: GPROC alarms

Chapter 22: GSL alarms

Chapter 23: IAS alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

Chapter 24: KSW alarms

Chapter 25: LAN alarms

Chapter 26: LMTL alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

26-28 26-29 26-30 26-31

Chapter 27: MMS alarms

Chapter 28: MSI alarms

28-14 28-16 28-18 28-19 28-22 28-24 28-26 28-28 28-30

Chapter 29: MTL alarms

Chapter 30: OMC-R alarms

68P02901W26-Q 24 May 2004

Maintenance Information: Alarm Handling at the OMC-R

Chapter 31: OML alarms

Chapter 32: PBUS alarms

Chapter 33: PCU alarms

Chapter 34: PPB alarms

Chapter 35: PSP alarms

Chapter 36: RSL alarms

68P02901W26-Q 24 May 2004

36-4 36-5 36-6 36-14 36-17 36-19 36-21

Chapter 37: SBUS alarms