Professional Documents
Culture Documents
Moto68P02901W26 Alarm
Moto68P02901W26 Alarm
Moto68P02901W26 Alarm
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Nov 2007
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02901W26-S i
Nov 2007
Contents
ii 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S iii
Nov 2007
Contents
iv 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
15. CELL: Inter-BSS handover, MS handover failed message received PM. . . . . . . . . . . . 12-40
16. CELL: EGPRS unavailable - Insufficient GDS available. . . . . . . . . . . . . . . . . . . . 12-42
17. CELL: GPRS unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
18. CELL: Handover failure to the MSC due to all possible errors except no channels - PM . . . 12-45
18. CELL: EGPRS unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
19. CELL: EGPRS unavailable - No 64 K PDCHs available . . . . . . . . . . . . . . . . . . . . 12-48
19. CELL: Bad handover reference numbers from the MS - PM . . . . . . . . . . . . . . . . . 12-49
20. CELL: Number of calls queued - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
22. CELL: Mobile assign command to MS blocked (No channel available) - PM . . . . . . . . . 12-53
23. CELL: Mobile assignment failure from MS - PM . . . . . . . . . . . . . . . . . . . . . . . 12-55
24. CELL: PCH queue page discard - PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
25. CELL: Attempt at allocating a TCH failed - PM . . . . . . . . . . . . . . . . . . . . . . . 12-59
28. CELL: TCH pre-emption failure - PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
68P02901W26-S v
Nov 2007
Contents
vi 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S vii
Nov 2007
Contents
viii 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S ix
Nov 2007
Contents
x 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S xi
Nov 2007
Contents
xii 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S xiii
Nov 2007
Contents
xiv 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S xv
Nov 2007
Contents
xvi 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Contents
68P02901W26-S xvii
Nov 2007
Contents
45. SITE: No signaling BVC reset acknowledgment from the SGSN . . . . . . . . . . . . . . . 42-94
46. SITE: DSW switching hardware required at site . . . . . . . . . . . . . . . . . . . . . . . 42-95
50. SITE: Database corruption detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42-97
51. SITE: Software patch installation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 42-98
xviii 68P02901W26-S
Nov 2007
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02901W26-S xix
Nov 2007
List of Tables
Table 14-1: FRUs that can be equipped with the CSFP device . . . . . . . . . . . . . . . . . . 14-2
Table 15-1: FRUs that can be equipped with the DHP device . . . . . . . . . . . . . . . . . . 15-3
Table 15-2: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-61
Table 15-3: Site reset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-63
Table 16-1: DPROC FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Table 16-2: Reset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Table 16-3: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Table 17-1: FRUs that can be equipped with the DRI device . . . . . . . . . . . . . . . . . . . 17-8
Table 17-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Table 17-3: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Table 17-4: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Table 17-5: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Table 17-6: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Table 17-7: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Table 17-8: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Table 17-9: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-30
Table 17-10: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-32
Table 17-11: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-34
Table 17-12: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-38
Table 17-13: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-40
Table 17-14: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Table 17-15: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-73
Table 17-16: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-76
Table 17-17: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-78
Table 17-18: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-80
Table 17-19: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-86
Table 17-20: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-113
Table 17-21: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-116
Table 17-22: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-202
Table 17-23: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-261
Table 17-24: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-293
Table 17-25: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-299
Table 17-26: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 17-307
Table 21-1: GCLK FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Table 21-2: Additional information fields contents . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Table 21-3: Additional information fields contents . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Table 21-4: GCLK timer settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-28
Table 21-5: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 21-29
Table 21-6: LTA calibration limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-49
Table 23-1: GPROC FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Table 23-2: GPROC: LAPD controller failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
Table 23-3: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
Table 23-4: Site reset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-53
Table 24-1: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 24-10
Table 24-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 24-13
Table 26-1: KSW FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Table 26-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 26-4
Table 28-1: Additional information field content . . . . . . . . . . . . . . . . . . . . . . . . . 28-3
Table 29-1: MMS FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Table 30-1: FRUs on which the MSI device may be equipped . . . . . . . . . . . . . . . . . . 30-2
Table 30-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 30-21
Table 31-1: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 31-4
Table 32-1: UPS condition alarm severities . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-88
Table 32-2: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 32-94
Table 35-1: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 35-5
Table 39-1: PSP FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-2
Table 39-2: Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-8
Table 40-1: Additional information field contents . . . . . . . . . . . . . . . . . . . . . . . . 40-10
xx 68P02901W26-S
Nov 2007
List of Tables
68P02901W26-S xxi
Nov 2007
List of Tables
xxii 68P02901W26-S
Nov 2007
About
This
Manual
This manual provides descriptions and handling procedures for the alarms that can be reported
by the Motorola GSM system. The information in this manual is primarily intended for OMC-R
operators responsible for the resolution of BSS fault conditions.
Each volume has a full Contents list and an Index for the whole of the manual.
Background information
This manual should be used in conjunction with the Maintenance Information: BSS Field
Troubleshooting (68P02901W51) manual. The Alarms manual is used by OMC-R operators
to remotely identify the source of an alarm, and the Troubleshooting manual for field
representatives to refer to for onsite procedures. The two manuals should be considered as a
pair, and cross-reference each other through the use of the same alarm identifiers.
Many of the procedures identified in this manual end with the statement: Send field
representative to resolve the problem. Where this is encountered, reference should be
made to the Troubleshooting manual which identifies the actions to be taken when the field
representative reaches the site. These additional procedures help the field representative to
locate the source of the problem.
68P02901W26-S 1
Nov 2007
Revision history
Revision history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Version information
The following table lists the supported versions of this manual in order of issue:
Service
CMBP Number Remarks
Request
NA NA
NA NA
2 68P02901W26-S
Nov 2007
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02901W26-S 3
Nov 2007
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Output
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
¦ Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
4 68P02901W26-S
Nov 2007
Contacting Motorola
Contacting Motorola
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
24–hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
• The document type
68P02901W26-S 5
Nov 2007
Security advice
Security advice
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
6 68P02901W26-S
Nov 2007
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
Caution text and consequence for not following the instructions in the caution.
Notes
Note text.
68P02901W26-S 7
Nov 2007
Safety
Safety
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
General safety
• Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
8 68P02901W26-S
Nov 2007
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’s
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02901W26-S 9
Nov 2007
CMM labeling and disclosure table
The People’s Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
• Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10 68P02901W26-S
Nov 2007
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY — UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02901W26-S 11
Nov 2007
Data encryption
12 68P02901W26-S
Nov 2007
Chapter
This chapter provides an overview of how alarms are organized in this manual and gives the
user a suggested approach to fault-finding using the OMC-R Alarms.
68P02901W26-S 1-1
Nov 2007
Manual introduction Chapter 1: Introduction to Alarm Handling
Manual introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Manual organization
Chapters
Device alarms are presented in separate chapters and organized in alphabetical order by device
name: ABSS, AXCDR, BCUP, and so on.
Individual alarms
Individual alarms are presented in numerical order, numbered from 0 to 254. Some alarm
numbers are not currently assigned to an alarm and are omitted. The total number of alarms
for a specific device depends on its function and requirements. The following information
is included for each alarm:
• A description.
The PM subsystem generates the PM alarms and reports when a statistical threshold is reached.
PM alarms are included in the chapter for the device generating the statistical data. PM alarms
are identified in this manual by the PM designation in the title. The PM designation differentiates
the device and the PM alarms that have the same numerical designation. For example:
Device alarm
PM alarm
1-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R About this chapter
Overview of alarms
This chapter provides an overview of the Motorola GSM system alarm messages reported
to the OMC-R.
Event management
The OMC-R event management subsystem monitors events and alarms generated by the
network. These events are displayed as event and alarm messages.
Event messages
An event is an activity affecting a device or function. Events generate various types of text
messages that the OMC-R reports, including alarm messages.
Alarm messages
Refer to the OMC-R Online Help, Network Operation for event and alarm handling procedures,
including subscription creation.
68P02901W26-S 1-3
Nov 2007
Alarm types Chapter 1: Introduction to Alarm Handling
Alarm types
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Untagged alarms
Throughout this manual, new and amended features are tagged to help the operators
assess the impact on installed networks. These editorial tags, described under
General Information - About This Manual, are used throughout the Motorola
document set. They have no relevance to the concept of tagged and untagged
alarms described in this section.
If alarms consolidation is not enabled, all alarms are displayed as untagged, including
the alarms that are associated with the device reconfigurations.
• Additional Information
The following example shows an untagged SITE alarm:
#7 - SEEN - *NONE* communication Failure Event - SITE - Trunk 10: 20 SITE - 29/03/2000
14:25:03 [0] Last RSL Link Failure - FMIC Critical -/-
1-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Tagged alarms
Tagged alarms
Tagged alarms are associated with device reconfigurations and are assigned a configuration
tag. A configuration tag is a unique number, assigned by the BSS, that identifies the primary
alarm and all associated secondary alarms.
Primary alarm
A primary alarm is an alarm identified by the BSS Fault Management (FM) subsystem as the
cause of the reconfiguration.
Secondary alarms
Secondary alarms are related to the primary alarm that caused the reconfiguration. Primary
and secondary alarms are presented in the same format, but secondary alarms are identified
with secondary in the reconfiguration line of the tagged alarm message.
If a primary alarm is cleared and an associated secondary alarm is not cleared, the
secondary alarm is reported as an untagged alarm.
Refer to the OMC-R Online Help, Network Operation for the procedures to change
environment variables.
Value Descriptions
0 Disable the alarms consolidation feature.
1 Display both primary and secondary alarms.
2 Display only primary alarms.
3 Display only primary alarms and set the subscriber mode as
the default map display mode.
68P02901W26-S 1-5
Nov 2007
Tagged alarms Chapter 1: Introduction to Alarm Handling
Both primary and secondary tagged alarms include the following information:
• Device alarm information.
• Reconfiguration information.
• Impact list.
• Additional information.
• Additional Information
When a tagged alarm is initially reported, the device alarm information is displayed in a
non-expanded format that includes *More Details* identifier. The following example shows an
unexpanded tagged alarm:
At the time of the alarm, the subscriber impact was: SITE 20 : Loss of service
1-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OMC alarm formats
The standard OMC-R alarm format includes a descriptive error reason in place of the Cage/Slot
information. This format is slightly different from the formats used for other devices. A
descriptive error reason is provided in place of the Cage/Slot information. OMC-R alarms are
presented in the following format:
• Additional Information
The following example shows a standard OMC-R alarm:
The Q3 Agent is an optional package available for the Motorola OMC-R. When the OMC-R
receives a state change notification for a device that is not visible to the Q3 interface, the
message is sent as an Equipment Failure alarm. This alarm prevents the loss of state change
information. State change warning alarms are presented in the following format:
• Alarm Code -Old State - Old Reason - New State - New Reason
68P02901W26-S 1-7
Nov 2007
Device alarm information Chapter 1: Introduction to Alarm Handling
Device information
Device alarm information is provided for both the tagged and untagged alarms. Table 1-2
lists the individual fields and possible values.
Field Description
#ID Identifier associated with alarm.
State
• NEW
• SEEN
• HANDLING
• DEFERRED
• CLEARED
Operator Person who is handling the alarm.
Comment Comment field to be checked for notes related to previous
instance of the alarm.
Alarm category
• Communication
• Quality of Service
• Processing
• Equipment
• Environment
• Link
• NHA Event
Device class Device generating the alarm.
Device instance Site and device identifiers for the faulty device.
Time Date Time and date, the alarm occurred.
Alarm code The alarm number and text string.
Continued
1-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Alarm states
• Major
• Minor
• Warning
• Investigate
• Clear
Clearing types
• FMIC
• Intermittent
• OIC
Cage and slot Hardware alarms includes the cage and slot placement in
the cabinet where the device generating alarm is located.
The field displays -/- for software alarms.
Hardware Version Information Hardware alarms include the hardware version.
Additional Information Some alarms reported by the BSS include additional
information to assist the operator in alarm handling.
Additional information, when included, is displayed at the
end of an alarm message at the OMC-R as one or more
untitled lines. The content and format of the additional
information depends on the reported alarm.
Alarm states
The alarm state indicates the status of each alarm in the Alarm window. This status allows the
operator to determine the actions required quickly, if any, to clear the alarm.
NEW
When the OMC-R receives an alarm, it is automatically assigned the NEW state. This status
indicates that the alarm was received but has not been acknowledged.
SEEN
When an operator selects a NEW alarm, its status is changed from NEW to SEEN. This status
indicates that the operator has acknowledged the alarm.
68P02901W26-S 1-9
Nov 2007
Alarm categories Chapter 1: Introduction to Alarm Handling
HANDLING
When an operator starts the alarm resolution process, the operator must change the alarm
status to HANDLING. This status indicates to anyone, reviewing the Alarms window, that action
is being taken to clear the alarm.
DEFERRED
When the OMC-R operator defers an alarm, it is displayed for 5 seconds as DEFERRED in
the Alarms window and then removed during the deferral period. Alarms that are currently
deferred are displayed only in the Deferred Alarms window.
CLEARED
When the condition that caused the alarm is resolved, the alarm status is changed to CLEARED.
The system automatically clears FMIC alarms. Other alarms require operator action to change
the status to CLEARED.
Alarm categories
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.
Communication
A communication alarm indicates a fault affecting the transfer of data from one point to another.
Quality of Service
1-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Alarm severities
Processing
Equipment
Environmental
Link
A link alarm indicates that a fault exists in the X.25 link connection between the OMC-R and
a network element.
NHA Event
An NHA event alarm indicates that the NHA detects a network problem.
Alarm severities
Each alarm generated by the system is assigned a severity indicating the impact of the fault
condition. The alarm severity is used to establish fault handling priority.
Critical
A critical alarm indicates the existence of a fault condition that causes a loss of service and
requires immediate resolution.
Major
A major alarm indicates the existence of a fault condition that causes a loss of capacity. Major
alarms require immediate resolution, but with less urgency than a critical alarm.
Minor
A minor alarm indicates the existence of a fault condition that causes a loss of redundancy.
Minor alarms do not require immediate resolution. Resolve the minor alarms to avoid a more
serious fault in the future.
Warning
A warning alarm indicates the existence of a non-service affecting a fault condition. Resolve
warning alarms to avoid a more serious fault in the future.
68P02901W26-S 1-11
Nov 2007
Clearing types Chapter 1: Introduction to Alarm Handling
Investigate
An investigate alarm indicates the existence of a fault condition for which the severity cannot
be determined. Investigate alarms require operator analysis to determine the impact of the
fault causing the alarm.
Clear
This severity indicates the fault condition that caused a previously reported alarm, that has
been resolved.
Clearing types
Clear the alarm at the OMC-R, after a fault condition is resolved. There are three alarm
clearing types.
FMIC
The BSS or OMC-R FM subsystem automatically clears the FMIC alarms when the fault condition
that caused the alarm is resolved. The system reports every occurrence of an FMIC alarm.
OIC
The OMC-R operator must clear the OIC alarms after the fault condition that caused the alarm
is resolved. The system reports an OIC alarm only once.
Intermittent
Intermittent alarms are transient and are not associated with a serious fault condition. After the
intermittent alarms are displayed in the alarm window, the operator must handle and clear the
alarm. The system reports every occurrence of an intermittent alarm unless it is throttled.
1-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Reconguration information
Reconguration information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Each primary and secondary tagged alarm includes information indicating the events that
resulted in a device state change. State changes occur due to a fault or some action by an
operator.
Remote reconguration
Field Description
Cause The reconfiguration is the result of one of the following events:
• Fault
• OMC request
• LMT request
• Initialization
• Restoration
• Remote
Operation The reconfiguration was performed by one of the following
actions:
• Unequip
• Equip
• Unlock
• Lock
• Shutdown
Continued
68P02901W26-S 1-13
Nov 2007
Remote reconguration Chapter 1: Introduction to Alarm Handling
• Enable
• Reset
• Lock-unlock
• Disable-enable-soft
• Disable-enable-hard
Outcome The reconfiguration causes one of the following system
responses:
• Alarm
• Recovered outage
• Advisory
• Clear
• Pending
Outage This is an optional field displayed if the SITE or CELL has
experienced an autonomously recovered outage with a
duration greater than 30 seconds. The value is the length of
the recovered outage.
Secondary This is an optional field displayed only if the alarm is a
secondary alarm. Secondary is the only value that is displayed
in this field.
Config Tag This is a number used to identify the primary and all secondary
alarms associated with a specific device reconfiguration.
1-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Impact list
Impact list
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The impact is reported against a Functional Unit (FU). FUs are logical entities against which
related device alarms are reported. There are only two FUs: CELL and SITE.
CELL
An alarm reported against a CELL FU device affects only the subscribers on the cell. State
changes on the following devices are reported against CELL FUs:
CELL DRI
SITE
An alarm reported against a SITE FU device affects all subscribers on the site. State changes on
the following devices are reported against SITE FUs:
Examples
68P02901W26-S 1-15
Nov 2007
Alarm impact Chapter 1: Introduction to Alarm Handling
Alarm impact
The impact of the device alarm for each FU indicates the effect on subscriber service.
Loss of service
This is a critical service-affecting condition causing a loss of service at a site or cell. Immediate
resolution action is required.
Loss of capacity
This is a condition causing a loss of capacity (as in traffic channels), but not causing a loss of
service at the site. Immediate resolution action is required, but with less urgency than that
required for a loss of service alarm.
Loss of redundancy
This condition causes a loss of redundancy (backup devices) at a site that may or may not affect
service to a site. Prompt action is required to reduce the possibility of a more serious condition.
1-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OOS device list
Device state
The Out of Service (OOS) device list displays all the OOS devices because of the alarm. The OOS
devices are listed in descending order of importance.
The list includes the operation and administrative states and a reason code for each device
rendered OOS. A maximum of 20 devices can be listed.
When a device on the list is returned to service, it is removed from the OOS device list.
68P02901W26-S 1-17
Nov 2007
Additional information eld Chapter 1: Introduction to Alarm Handling
Alarm handling
Some alarms reported by the BSS include additional information to assist the operator in alarm
handling. Additional information appears in both tagged and untagged alarms.
Alarm message
Additional information, when included, is displayed at the end of an alarm message at the
OMC-R as one or more untitled lines. The content and format of the additional information
depends on the reported alarm. For example, the additional information include error codes
to identify the cause of an alarm.
When viewing the Additional information field, ignore the bytes displayed that are
additional to the bytes described in this manual.
1-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R OMC-R map display modes
OMC-R maps
OMC-R maps display alarms in one of two modes: device and subscriber.
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.
The display mode is selected on a Map window by clicking either the impact on devices or
impact on subscriber option in the view drop-down menu.
68P02901W26-S 1-19
Nov 2007
Map display colors Chapter 1: Introduction to Alarm Handling
Colors indicate the severity for all alarms in the device mode and untagged alarms in the
subscriber mode. Table 1-5 presents the default icon colors and corresponding alarm severities.
Colors indicate the impact of an alarm on a FU in the subscriber mode. Table 1-6 presents the
default icon colors and the corresponding alarm impacts.
1-20 68P02901W26-S
Nov 2007
Chapter
ABSS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R ABSS Alarms and includes the following alarm procedures:
68P02901W26-S 2-1
Nov 2007
0. ABSS: Last XBL link failure Chapter 2: ABSS Alarms
Description
The last communication link from the RXCDR to the specified BSS has gone OOS.
If CIC validation is enabled for the local RXCDR, the BSC blocks all CICs routed through the
RXCDR. No call traffic is possible between the specified BSS and the RXCDR.
If CIC validation is not enabled for the local RXCDR, the BSC does not block CICs and call traffic
is not immediately impacted. If the RXCDR experiences a fault condition causing the CIC to be
blocked, the BSC is not notified. In this case, traffic is impacted because the BSC attempts to
use the blocked CIC resulting in no audio.
Possible causes
• The MMS on the RXCDR or BSC, where the XBL is equipped, has failed.
2-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 2-3
Nov 2007
1. ABSS: RXCDR detecting CIC validation failure Chapter 2: ABSS Alarms
Description
The ABSS was placed in the Busy-Unlocked state indicating that CIC validation is enabled at the
BSC, but the BSC did not initiate CIC validation for this RXCDR.
• All CICs going to the RXCDR are blocked at the MSC. The RXCDR does not handle any
calls from the BSC until the problem is resolved.
• CICs are not blocked at the MSC, but only certain CICs are capable of handling the traffic.
This causes CERM alarms and a high rate of incomplete calls.
Possible causes
• The XBL link or switching equipment between the BSC and the RXCDR is malfunctioning.
2-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If the problem is not resolved after troubleshooting the switching equipment, CIC
validation at the BSC could be disabled as a last resort.
68P02901W26-S 2-5
Nov 2007
2. ABSS: Circuit conguration problem Chapter 2: ABSS Alarms
Description
The RXCDR is unable to make a proper connection for at least one CIC. The ABSS is in the
Disabled-Unlocked-No Validation state and there is at least one CIC with no static ater for
the ABSS.
All calls are set up by the BSC as the MSC requests. Since there is no proper switch connection
for the CICs at the RXCDR, there is no audio on the affected CICs.
The Additional information field displays the number of affected CICs for a specific ABSS.
Possible causes
One or more CICs were equipped with no static aters at the ABSS in Disabled-Unlocked-No
Validation state.
Procedure
2-6 68P02901W26-S
Nov 2007
Chapter
AXCDR Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R AXCDR Alarms and includes the following alarm procedures:
68P02901W26-S 3-1
Nov 2007
Introduction to AXCDR alarms Chapter 3: AXCDR Alarms
AXCDR alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Associated
Transcoder (AXCDR) device.
3-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. AXCDR: BSC detecting CIC validation failure
Description
The RXCDR failed to respond to repeated attempts by the BSC to initiate the CIC validation
procedure. The effect of this failure is that CIC validation is not performed between the BSC
and the RXCDR for the affected RXCDR. All CICs connected to the affected RXCDR are blocked.
Possible causes
The RXCDR has not been upgraded to a software release that supports CIC validation.
Procedure
1 Turn CIC validation off at the BSC for the affected RXCDR.
2 Upgrade the affected RXCDR to a software release that supports
CIC validation.
3 Turn CIC validation on at the BSC for the affected RXCDR.
68P02901W26-S 3-3
Nov 2007
0. AXCDR: Ater pre-emption failure statistic alarm - PM Chapter 3: AXCDR Alarms
Description
The ATER_PREEMPT_FAIL AXCDR statistic threshold has been reached. This statistic
represents the number of calls triggering the Ater pre-emption mechanism without being
allocated a resource.
When this alarm occurs, calls with pre-emption capabilities trigger pre-emption. Inability to
allocate terrestrial resources results in failure to establish calls within the BSS.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
3-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Re-evaluate the capacity of the affected AXCDR. This reduces the number of
pre-emption events within the cell and therefore, result in a lower level of
pegging of this alarm and a reduced chance of the alarm being raised.
2 Re-evaluate the priority level/PCI/PVI capabilities of call groups. If the
AXCDR experiences periods of overload of higher priority or pre-emption of
non-vulnerable calls, it is possible that this alarm is raised. This is due to
a particular network event or due to the priority level/PCI/PVI capabilities
of the call groups. If the network event is a regular occurrence, the alarm
threshold should be adjusted to account for this if applicable. Alternatively,
re-evaluation of the priority level/PCI/PVI capabilities of the call groups
may be required.
68P02901W26-S 3-5
Nov 2007
1. AXCDR: AXCDR ID mismatch with RXCDR network entity ID Chapter 3: AXCDR Alarms
Description
The BSC has detected that the network identifier of the AXCDR at the BSC does not match the
corresponding RXCDR device at the RXCDR site.
No call traffic is possible between the BSS and the indicated AXCDR. All CICs through that
AXCDR are blocked.
Possible causes
3-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 3-7
Nov 2007
Procedure Chapter 3: AXCDR Alarms
3-8 68P02901W26-S
Nov 2007
Chapter
BCUP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R BCUP Alarms and includes the following alarm procedures:
68P02901W26-S 4-1
Nov 2007
Introduction to BCUP alarms Chapter 4: BCUP Alarms
BCUP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base
Controller Unit Power supply (BCUP) device.
BCUP alarms are reported only for InCell BTS, BSC, and RXCDR hardware.
FRUs
The BCUP device is equipped on power supply units specified for the hardware platform in use.
4-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. BCUP: Unexpected board type
Description
The system detected an unexpected BCUP board type. This alarm occurs only if the BCUP board
type suddenly changes without being removed and reinserted.
Possible causes
Procedure
Send a field representative to the site to replace the power supply module.
68P02901W26-S 4-3
Nov 2007
Procedure Chapter 4: BCUP Alarms
4-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. BCUP: Serial bus connection failure
Description
The BCUP device has not responded to the attempts for communication by the Serial Bus
(SBUS) processor.
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action and resolve the alarm.
68P02901W26-S 4-5
Nov 2007
Procedure Chapter 4: BCUP Alarms
4-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. BCUP: Output failure
Description
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action to resolve the alarm.
68P02901W26-S 4-7
Nov 2007
Procedure Chapter 4: BCUP Alarms
4-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. BCUP: Input failure
Description
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action to resolve the alarm.
68P02901W26-S 4-9
Nov 2007
Procedure Chapter 4: BCUP Alarms
4-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. BCUP: Over temperature warning
Description
The temperature of the power supply module has exceeded safe limits.
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action to resolve the alarm.
68P02901W26-S 4-11
Nov 2007
Procedure Chapter 4: BCUP Alarms
4-12 68P02901W26-S
Nov 2007
Chapter
BSP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details OMC-R BSP Alarms and includes the following alarm procedures:
• 1. BSP: EEPROM flash failure - No valid bootstrap code detected on page 5-4.
• 32. BSP: TDM interface failure - Assigned timeslot counter underflow on page 5-20.
• 33. BSP: TDM interface failure - Assigned timeslot counter overflow on page 5-22.
• 34. BSP: TDM interface failure - TDM parity error on page 5-24.
68P02901W26-S 5-1
Nov 2007
Procedure Chapter 5: BSP Alarms
5-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BSP alarms
BSP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base Station
Processor (BSP) device.
• The registration of processes for alarm notification is not kept. The registration is
recovered after the processes register again.
• The devices fault history is cleared and alarms handler for the devices creates new device
fault history.
Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS to
mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
68P02901W26-S 5-3
Nov 2007
1. BSP: EEPROM ash failure - No valid bootstrap code detected Chapter 5: BSP Alarms
Description
The Initialization Process (IP) has determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt. In this case, initialization is not permitted.
Possible causes
• The bootstrap code object (Object 15) was corrupted while being downloaded at the
GPROC.
Procedure
Continued
5-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure 5-1 EEPROM ash failure - No valid bootstrap code detected (Continued)
2 Obtain a new OMC-R code bootstrap object.
If the alarm... Then...
is cleared and does not recur No further action is required.
is not cleared or recurs Send a field representative to the
site to replace the GPROC board.
3 Download the new object to the affected BSSs and then attempt
to clear the alarm.
If the alarm... Then...
is cleared and does not recur No further action is required.
is not cleared or recurs Send a field representative to the
site to replace the GPROC board.
4 Download the object to the BSC and then attempt to clear the alarm.
68P02901W26-S 5-5
Nov 2007
8. BSP: EEPROM ash object failure Chapter 5: BSP Alarms
Description
The size of the user start address in the header information of the bootstrap code object (Object
15) is incorrect. As a result, reprogramming is not initiated.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is programmed incorrectly with regard to the
GPROC EEPROM address space.
5-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-7
Nov 2007
17. BSP: EEPROM ash programming failure Chapter 5: BSP Alarms
Description
An attempt to erase bank 0 before reprogramming a flash EEPROM was unsuccessful. Bank 0
contains a byte that can be reprogrammed after a bank erase.
This fault condition is not a problem unless the GPROC is being reset, at which time
the GPROC is rendered useless.
Possible causes
Procedure
5-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 5-9
Nov 2007
20. BSP: LAPD controller failure Chapter 5: BSP Alarms
Description
Two bytes are displayed. Ignore the first byte, the second byte has a value of 1 or 2. The second
byte value descriptions are shown in Table 5-1.
Table 5-1 BSP: LAPD controller failure second byte value description
Value Description
1 The LAPD controller has encountered a non recoverable internal fault.
2 The LAPD controller cannot open a new channel for RSL link.
Possible causes
• The micro code in the LAPD controller has encountered a fatal exception.
• The LAPD controller cannot open a new LAPD channel due to an internal error.
Procedure
5-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. BSP: EEPROM ash programming failure
Description
This fault condition is not a problem until the GPROC is reset, at which time the
GPROC is rendered useless.
Possible causes
Procedure
68P02901W26-S 5-11
Nov 2007
Procedure Chapter 5: BSP Alarms
5-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. BSP: SWFM indication
Description
The system has detected a software processing error (SWFM) for a BSP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
Procedure
68P02901W26-S 5-13
Nov 2007
30. BSP: Clock A signal loss Chapter 5: BSP Alarms
Description
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BSP switches to the
redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference
fails and causes the site to go OOS.
The fault condition reported by this alarm cause the site to go OOS.
Possible causes
5-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 5-15
Nov 2007
Procedure Chapter 5: BSP Alarms
5-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. BSP: Clock B signal loss
Description
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the BSP switches to the
redundant clock. If the redundant clock cannot be accessed, the internal (active) clock reference
fails and causes the site to go OOS.
Possible causes
Procedure
Continued
68P02901W26-S 5-17
Nov 2007
Procedure Chapter 5: BSP Alarms
5-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 5-19
Nov 2007
32. BSP: TDM interface failure - Assigned timeslot counter underow Chapter 5: BSP Alarms
Description
The BSP has determined that the TDM highway is underused. Fewer switch-bound timeslots are
driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes
• One or more MCAP data or address lines on the backplane are faulty.
5-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-21
Nov 2007
33. BSP: TDM interface failure - Assigned timeslot counter overow Chapter 5: BSP Alarms
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
5-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-23
Nov 2007
34. BSP: TDM interface failure - TDM parity error Chapter 5: BSP Alarms
Description
Possible causes
5-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-25
Nov 2007
35. BSP: LAN connection failure Chapter 5: BSP Alarms
Description
The LAN connection between the master GPROC and any other equipped BSP on the LAN failed.
System action
The system places the BSP OOS. If the BSP is the master GPROC, the site resets.
Possible causes
5-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-27
Nov 2007
39. BSP: Software failure Chapter 5: BSP Alarms
Description
SWFM is a debugging tool for Motorola engineering and is reported only 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 useful only to the
programmers.
Possible causes
5-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-29
Nov 2007
40. BSP: Spurious interrupt Chapter 5: BSP Alarms
Description
The BSP received and acknowledged an interrupt message but did not receive a response from
the device generating the interrupt.
Possible causes
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or some
other cause.
5-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-31
Nov 2007
47. BSP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 5: BSP Alarms
Description
{28337} The BSC generates this alarm when it detects a GPROC/GPROC2 board in a slot in
place of GPROC3/GPROC3–2 board. BSPs at the RXCDR and BSC can be a GPROC2.
The BSC generates this alarm when it detects a GPROC board in a slot in place of GPROC2 or
{28337} GPROC3/GPROC3–2 board. BSPs at BSC must be at least GPROC3, BSPs at RXCDR
must be at least GPROC2.
Possible causes
If this alarm occurs in an InCell site, the GPROC board does not come into service.
• A GPROC board is installed and the gproc_slots database parameter is set to 32.
5-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 5-33
Nov 2007
48. BSP: Memory location fault Chapter 5: BSP Alarms
Description
This alarm advises of a possible memory location fault. It is not an immediate problem as
the GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
is replaced at an appropriate time.
Possible causes
Procedure
5-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. BSP: EEPROM SW ash programming failure
Description
This is a generic flash programming error. A problem has occurred with the operating software.
Possible causes
Procedure
If the board does not reset automatically, a manual reset can be performed
to reload the bootrom object.
68P02901W26-S 5-35
Nov 2007
51. BSP: EEPROM HW ash programming failure Chapter 5: BSP Alarms
Description
Possible causes
Procedure
5-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 52. BSP: BSP CPU Safe Overload
{23306}
Description
The BSS supports this alarm to indicate that the active BSP CPU is working in safe-overload
status and its utilization is over safe-overload threshold (BSP CPU utilization is 70%).
The Additional information field contains 11 bytes in the additional alarm codes.
Byte Denition
One, two The total CPU utilization of BSP
when the overload is detected.
Possible causes
• Hardware fault.
68P02901W26-S 5-37
Nov 2007
Procedure Chapter 5: BSP Alarms
Procedure
Identify one of the causes for BSP CPU safe overload by using the
content of additional codes.
If... Then...
the highest CPU utilization is check the reason for large number
on Allocation Manager (AM) of service requests and review
and Switch Manager (SM) their network plan.
processes
5-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 53. BSP: BSP CPU critical overload
{23306}
Description
The BSS supports this alarm to indicate that the active BSP CPU is working in critical-overload
status and its utilization is over critical-overload threshold (95% of BSP CPU is utilized).
The Additional information field contains 11 bytes in the additional alarm codes.
Byte Denition
One, two The total CPU utilization of BSP
when the overload is detected.
Possible causes
• A software fault in some BSP process with priority higher than SM and AM causes high
CPU utilization.
• Hardware fault.
68P02901W26-S 5-39
Nov 2007
Procedure Chapter 5: BSP Alarms
Procedure
Identify one of the causes for a BSP CPU critical overload by using
the content of additional codes.
If... Then...
the highest CPU utilization are the overload control works and
on Allocation Manager (AM) the alarm is cleared when the BSP
and Switch Manager (SM) quits the critical-overload state.
processes
5-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 231. BSP: TDM interface conguration failure
Description
System action
The system automatically resets the BSP. If the alarm recurs, the BSP is placed OOS.
Possible causes
• The GPROC device could not be programmed to the designated timeslot when swapping
the TDM highways.
68P02901W26-S 5-41
Nov 2007
Procedure Chapter 5: BSP Alarms
Procedure
5-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. BSP: Processor bus communication failure
Description
The BSP has lost communication to the peripheral boards through the MCAP bus.
Possible causes
• The part of the BSP that supports the MCAP bus access has failed.
The BSS attempts to clear this alarm automatically, through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
1 Attempt to bring back the BSP In Service (INS). If the device is back in
service, the alarm condition has ceased and further fault isolation is not
required. If the device remains OOS, go to step 2.
2 Replace the BSP board.
68P02901W26-S 5-43
Nov 2007
239. BSP: Process safe test audit failure Chapter 5: BSP Alarms
Description
The BSP failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes.
The Additional information field includes 9 bytes containing process information, as shown in
Table 5-2. Bytes one to eight are useful only to the programmers. Byte nine is the error code
for the alarm.
Possible causes
Procedure
5-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 5-45
Nov 2007
254. BSP: Device failure Chapter 5: BSP Alarms
Description
The BSP is taken OOS by the GPROC fault management system. This alarm is FMIC. The alarm
is cleared when the failed BSP goes back to service.
If BSC is configured as bsc_type 1, this alarm is not shown on the OMC event window
upon BSP switchover. In BSS MMI, the alarm 254 can always be seen when BSP
switchover happens no matter bsc_type is 1 or 2.
System action
MCAP failure causes the BSC reset. BSP will switchover, if the redundant BSP is equipped and
unlocked. Otherwise, BSC resets. If BSC resets, alarm 254 is not raised. It is raised only when
BSP switchover happens.
A single byte is displayed in the Additional information field identifying the type of site reset, as
shown in Table 5-3.
5-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• This alarm can occur when the BSP switchover takes place.
Procedure
If the alarm is reported after BSP switchover, wait for the alarm being cleared when the faulty
BSP is reset to go to service by software, after switchover. If the faulty BSP cannot be reset to
go back into service by the software when BSP switchover finishes, try to install the faulty BSP.
This alarm is cleared if the faulty BSP goes back to service. If the failed BSP still cannot go to
service, replace the failed BSP and try bringing the BSP into service.
Wait approximately 10 minutes after this alarm is received to allow the site to reset,
before using this procedure.
68P02901W26-S 5-47
Nov 2007
Procedure Chapter 5: BSP Alarms
5-48 68P02901W26-S
Nov 2007
Chapter
BSS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details BSS Alarms and includes the following alarm procedures:
• 0. BSS: Last MTL link failure - Signaling point inaccessible on page 6-4.
• 1. BSS: Call processing failure - MSC detected SCCP down on page 6-8.
• 2. BSS: Call processing failure - MSC detected BSSAP down on page 6-10.
• 3. BSS: Call processing failure - BSS detected BSSAP down on page 6-13.
• 7. BSS: Mobile assignment request from MSC protocol error - PM on page 6-21.
• 10. BSS: Erroneous layer 3 message received by the BSS on page 6-26.
• 11. BSS: Confusion message received from the MSC on page 6-27.
• 17. BSS: Handover request from the MSC protocol error - PM on page 6-30.
• 18. BSS: Routing failure - Syntax error detected (SMLC) - PM on page 6-31.
• 20. BSS: Paging request from SMLC protocol error- PM on page 6-32.
• 23. BSS: Agent Buffer Space Overflow - Event Logs May Be Incomplete on page 6-35.
• 24. BSS: Agent Buffer Overflow - rlogin Session May Be Incomplete on page 6-36.
• 26. BSS: Received page for invalid cell from MSC on page 6-38.
68P02901W26-S 6-1
Nov 2007
Procedure Chapter 6: BSS Alarms
• 49. BSS: Last LMTL link failure - Signaling point inaccessible on page 6-59.
• 50. BSS: Call processing failure - SMLC detected SCCP down on page 6-62.
• 51. BSS: Call processing failure - SMLC detected BSSAP down on page 6-64.
• 53. BSS: Erroneous layer 3 message received from SMLC on page 6-67.
• 54. BSS: Confusion message received from the SMLC on page 6-68.
• 55. BSS: Received page for invalid cell from SMLC on page 6-69.
6-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BSS alarms
BSS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base Station
System (BSS) device.
68P02901W26-S 6-3
Nov 2007
0. BSS: Last MTL link failure - Signaling point inaccessible Chapter 6: BSS Alarms
Description
The signaling point code is inaccessible due to the failure of the last available MTL link. When
this failure occurs, the BSS cannot support calls or send messages to the MSC.
A single MTL link provides a 64 kbps connection between the two pieces of equipment. One or
more MTL links can be configured between the following sites:
• BSC-to-MSC.
• BSC-to-RXCDR-to-MSC.
6-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, SIE) frames causing the
link failure.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive error rate that caused
the failure.
Procedure
Continued
68P02901W26-S 6-5
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure 6-1 Last MTL link failure - Signaling point inaccessible (Continued)
3 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the MTLs
and take the appropriate action to
return all MTLs to service.
not cleared The fault is probably at the MSC.
Troubleshoot the MSC fault.
4 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the MTLs
and take the appropriate action to
return all MTLs to service.
not cleared Go to step 5.
5 Attempt to return one of the MTLs to service.
If one of the MTLs... Then...
returns to service Go to step 6.
does not return to service Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the MTLs
and take appropriate action to
return all MTLs to service.
not cleared Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. BSS: Paging request from MSC protocol error - PM
Description
This statistic tracks the number of page request messages received from the MSC that fail
message validation. Validation failures occur due to protocol errors, which occurs if the message
is incorrectly formatted. A protocol error does not indicate paging success or failure.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 6-7
Nov 2007
1. BSS: Call processing failure - MSC detected SCCP down Chapter 6: BSS Alarms
Description
The BSS received a User Part Unavailable (UPU) message from the MSC indicating that the
Signaling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the
BSS cannot support calls.
When the SCCP is down, the MSC does not accept SCCP messages from the BSS. This SSCP
failure occurs at the MSC.
Possible causes
The BSS received a UPU message from the MSC indicating that the SCCP is unavailable.
Procedure
6-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. BSS: Routing failure - Syntax error detected - PM
Description
This statistic tracks the number of SCCP messages with syntax errors. SCCP is an SS7 protocol
used in transferring signaling messages between the BSC and MSC. Excessive syntax errors
can result in degraded SCCP performance.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 6-9
Nov 2007
2. BSS: Call processing failure - MSC detected BSSAP down Chapter 6: BSS Alarms
Description
The BSS received a Subsystem Prohibited (SSP) message from the MSC indicating that the
BSS Application Part (BSSAP) is down (unavailable). When this condition exists, the BSS
cannot support calls.
When the BSSAP is down, the MSC does not accept BSSAP messages from the BSS. This BSSAP
failure occurs at the MSC.
Possible causes
The BSS receives an SSP message from the MSC indicating that the BSSAP is unavailable.
6-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 6-11
Nov 2007
2. BSS: Routing failure - Reason unknown - PM Chapter 6: BSS Alarms
Description
This statistic tracks the number of invalid Signaling Point Codes (SPCs) that a BSC has received
from the MSC. An SPC is the destination address for a message routed by the networking
functions of the MTP3 protocol. If the BSC receives an incorrect SPC, it is not able to route
the message correctly.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
6-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
When the BSSAP is down, the BSS does not accept BSSAP messages from the MSC. This BSSAP
failure is at the BSS.
Possible causes
68P02901W26-S 6-13
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. BSS: No MSC acknowledgment for circuit block
Description
The BSS has repeated the circuit block message the maximum number of times without
receiving any acknowledgment from the MSC.
When the BSS sends a circuit block message to the MSC, the BSS expects to receive an
acknowledgment message from the MSC. If an acknowledgment message is not received, the
BSS retransmits the circuit block message. This transmission is repeated until the BSS receives
an acknowledgment message or the maximum number of retransmissions is reached.
The content of the Additional information field is dependent upon the value assigned to the
group_block_unblock_allowed parameter. Table 6-1 specifies the content for the zero value.
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.
68P02901W26-S 6-15
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
Procedure
6-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. BSS: No MSC acknowledgment for circuit unblock
Description
The BSS has repeated the circuit unblock message the maximum number of times without
receiving any acknowledgment from the MSC.
When the BSS sends a circuit unblock message to the MSC, the BSS expects to receive an
acknowledgment message from the MSC. If an acknowledgment message is not received, the
BSS retransmits the circuit unblock message. This transmission is repeated until the BSS
receives an acknowledgment message or the maximum number of retransmissions is reached.
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.
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.
68P02901W26-S 6-17
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
Procedure
6-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. BSS: No MSC acknowledgment for reset circuit
Description
The BSS has repeated the circuit unblock message the maximum number of times without
receiving any acknowledgment from the MSC. The parameter max_rst_ckt_timer_exp defines
the maximum number of times the message is repeated.
The contents of the Additional information field are shown in Table 6-5.
68P02901W26-S 6-19
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
Procedure
6-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. BSS: Mobile assignment request from MSC protocol error - PM
Description
This statistic tracks the number of assignment request messages received from the MSC that
fail message validation.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• Assignment Request messages received from the MSC are incorrectly formatted.
68P02901W26-S 6-21
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. BSS: Unequipped circuit at the MSC
Description
The BSS had sent a message to the MSC with an invalid terrestrial circuit identifier. The MSC
responded to the BSS with the Unequipped Circuit Message for that terrestrial circuit.
The contents of the Additional information field are shown in Table 6-6.
68P02901W26-S 6-23
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
• The MSC and BSS database shows a different device state for the same terrestrial circuit.
Procedure
6-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. BSS: No MSC acknowledgment for global reset
Description
The BSS repeated the global reset message the maximum number of times without receiving
an acknowledgment from the MSC.
Possible causes
Procedure
68P02901W26-S 6-25
Nov 2007
10. BSS: Erroneous layer 3 message received by the BSS Chapter 6: BSS Alarms
Description
The BSS received an erroneous layer 3 message from the MSC and the MSC does not support
such message.
The Additional information field displays the erroneous layer 3 message that the BSS receives
(from the MSC).
Possible causes
Procedure
6-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. BSS: Confusion message received from the MSC
Description
The Additional information field displays the confusion message that the BSS receives from
the MSC.
Possible causes
The MSC did not understand a layer 3 message from the BSS.
Procedure
68P02901W26-S 6-27
Nov 2007
12. BSS: Unequipped circuit at the BSS Chapter 6: BSS Alarms
Description
The BSS received a message from the MSC that contains an unknown circuit and the MSC does
not support the unequipped circuit message.
This alarm indicates that a Base Station System (BSS) received a message from the Mobile
Switching Centre (MSC) containing an invalid terrestrial circuit identifier. The BSS responded
to the MSC with the Unequipped Circuit Message for that terrestrial circuit.
This alarm is generated because the database does not properly reconcile the device states.
Each database (MSC and BSS) shows a different device state for the identical terrestrial
circuit device.
The Additional information field contents are shown in Table 6-7. This information is displayed
for the unequipped terrestrial circuit. Ignore any additional bytes displayed.
6-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The MSC and BSS databases shows a different device state for the same terrestrial circuit.
Procedure
68P02901W26-S 6-29
Nov 2007
17. BSS: Handover request from the MSC protocol error - PM Chapter 6: BSS Alarms
Description
This statistic tracks the number of Handover Request messages received from the MSC that fail
message validation. Validation failure results due to protocol errors that occur if the message is
badly formatted or incompatible database elements exist in the BSS and MSC.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
6-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
This statistic tracks the number of Lb-interface SCCP messages with syntax errors. Lb-interface
SCCP is an SS7 protocol used in transferring signaling messages between the BSC and SMLC.
Excessive syntax errors can result in degraded Lb-interface SCCP performance.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 6-31
Nov 2007
20. BSS: Paging request from SMLC protocol error- PM Chapter 6: BSS Alarms
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.
This statistic tracks the number of Page Request messages received from the BSS-based SMLC
that fail message validation. Validation failures occur due to protocol errors, which occur if the
message is incorrectly formatted. A protocol error does not indicate paging success or failure.
For further information, refer to the BSS statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
6-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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, refer to the BSS statistics chapter in the manual, Technical Description:
BSS Command Reference (68P02901W23).
Possible causes
Procedure
1 Review the Alarms window to identify the current CIC and RCI
alarms.
2 Initiate fault isolation and fault resolution procedures to restore
the failed circuits.
68P02901W26-S 6-33
Nov 2007
22. BSS: Trunk critical threshold exceeded Chapter 6: BSS Alarms
Description
This alarm indicates that the percentage of trunk capacity has exceeded the user-specified value
of the trunk_critical_threshold database parameter.
For further information, refer to the BSS statistics chapter in the manual, Technical Description:
BSS Command Reference (68P02901W23).
Possible causes
Procedure
1 Review the Alarms window to identify the current CIC and RCI
alarms.
2 Initiate fault isolation and fault resolution procedures to restore the
failed circuits.
6-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. BSS:
Agent Buffer Space Overow - Event Logs May Be Incomplete
Description
This alarm indicates that there is no BSS Agent buffer space available. Event Log messages
(alarms, state changes, and other events) have been received, but cannot be stored. After the
buffer is full, the most recent messages are discarded. When active event messages are sent,
the related output sent to the OMC may be incomplete while this fault condition exists.
Possible causes
• One or more devices in a BSS are generating continuous alarm output and device state
change messages.
Procedure
The operator must identify the devices that are generating the alarms or state changes that are
causing the event message overflow.
68P02901W26-S 6-35
Nov 2007
24. BSS: Agent Buffer Overow - rlogin Session May Be Incomplete Chapter 6: BSS Alarms
Description
This alarm indicates that there is no more BSS Agent buffer space available. A rlogin message or
data has been received, but cannot be stored. Until the fault condition is resolved, subsequent
rlogin message or data is stored at the Agent if space is available. When active messages or
data are sent from a rlogin session that is in progress, the related output sent to the BSC is
incomplete while this fault condition exists.
Additional information
Possible causes
• One or more rlogin sessions to a BSC are generating excessive output through transfer of
information through software filters.
• One or more rlogin sessions to a BSC are generating excessive output through transfer of
information through software IIRs.
6-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
The BSS clears the alarm automatically through a Fault Management Initiated Clear (FMIC)
after 50% of the contents of the rlogin buffer in the Agent are cleared.
Operators must stop the output-intensive filters and/or IIRs if any are set, or provide more
specific parameters to the output-intensive commands, to limit the amount of text output they
generate.
68P02901W26-S 6-37
Nov 2007
26. BSS: Received page for invalid cell from MSC Chapter 6: BSS Alarms
Description
The MSC has sent a paging message to a nonexistent cell in the BSS.
Ignore any additional bytes displayed. The cell ID can be derived from the displayed fields by
using the mmi_cell_id_format command. Refer to the Technical Description: BSS Command
Reference (68P02901W23) manual.
Possible causes
The MSC and BSS databases do not have matching cell ID lists.
Procedure
6-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. BSS: Circuit fault detected on radio channel
Description
A particular Radio Channel Identifier (RCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the RCI error generation threshold, meaning
thereby, that a device in the RCI path could be faulty and need replacing. None of the devices in
the RCI path for the faulty RCI is taken Out Of Service (OOS) due to this alarm, which simply
reports the devices contained in the RCI path.
Alarm throttling is not allowed for this alarm. The OMC-R is notified when an RCI Fault
notification message has been sent to the alarms subsystem. The OMC-R receives a Faulty
RCI set intermittent alarm and the path information as described in the following additional
alarm data section.
The OMC-R uses each RCI Fault intermittent alarm to keep track of which RCIs have alarms on
them. The BSS alarm subsystem does not keep track of the RCIs that have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all
the RCIs for which the BSS has sent intermittent alarms (the BSS keeps track of which RCIs
have had alarms sent).
The OMC-R receives the RCI list in the additional alarm data field of one or more RCI Fault
intermittent alarms. The OMC-R knows it has received the entire list of RCIs when the OMC-R
receives the Generic Result message from the BSS. Any RCI alarms, which the OMC-R shows as
active alarms that are not in the resync list, are changed to the cleared state.
Any new alarms in the list that the OMC-R does not show as active, require no immediate action
since the BSS reissues these alarms later. When the RCI Fault intermittent alarm is being used
for resync, the Report Type of the alarm is resync alarm.
Additional Information
The message Faulty RCI Alarm Set includes the following RCI related information: RCI, Site,
Channel Coder Unit (CCU) device and CCU timeslot upon which the RCI exists.
68P02901W26-S 6-39
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
Procedure
1 Check the status of the devices in the RCI path. If there are additional
Faulty RCI Alarms for RCIs using the same path, one or more of the devices
in the path is probably faulty and should be replaced. Use the information
contained in the alarm report to determine which device needs replacement.
2 Send a field representative to the site to replace the faulty device.
6-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 40. BSS: Circuit fault cleared on radio channel
Description
The BSS sends a Faulty Radio Channel Identifier (RCI) Alarm Clear message to the OMC-R when
the error count on the RCI reaches or goes below the specified threshold and the alarm is
currently set. This message indicates that:
• The failure condition causing TRAU frames to be lost has cleared for the Radio Channel
Interface in the alarm clear message.
• The Radio Channel Interface alarms are to be cleared due to the Call Processing global
reset.
• Relevant RCI alarms are to be cleared due to the PCU OOS case.
Additional Information
For the non-Call Processing global reset case and the non-PCU OOS case, the additional data
contains the Radio Channel Interface path information, which includes the Additional Data
Identifier (1 byte) and the Radio Channel Interface (4 bytes). For the Call Processing reset case,
the additional data contains the Additional Data Indicator (1 byte), Field length (2 bytes) and a
list of circuits to notify the OMC that the Call Processing global reset has occurred and a CLEAR
should be initiated. For the PCU OOS case, the additional data contains the Additional Data
Indicator (1 byte), Field length (2 bytes) and a list of circuits to notify the OMC that the PCU
is OOS and a CLEAR should occur.
Possible causes
68P02901W26-S 6-41
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
1 The intermittent alarm message indicates that a prior fault has been cleared;
so, no action is normally required. If there is a trend where an RCI toggles
between being faulty and cleared, action is required to identify and replace
the relevant device.
2 Use the information contained in the Alarm report to determine which
device is to be replaced.
6-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41. BSS: Circuit fault detected on Ater channel
Description
A particular Ater Channel Identifier (ACI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the ACI error generation threshold, indicating
that a device in the ACI path is faulty and in need of replacement. None of the devices in the
ACI path for the faulty AC is taken Out Of Service (OOS) due to this alarm, which reports the
devices contained in the ACI path. Alarm throttling is not allowed for this alarm.
The OMC-R is notified when an ACI Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty ACI set intermittent alarm and the path information
as described in the following additional alarm data section. The OMC-R uses each ACI Fault
intermittent alarm to keep track of the ACIs that have alarms on them. The BSS alarm
subsystem does not keep track of the ACIs that have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all the
ACIs for which the BSS has sent intermittent alarms. The OMC-R receives the ACI list in the
additional alarm data field of one or more ACI Fault intermittent alarms. The OMC-R knows
it has received the entire list of ACIs when the OMC-R receives the Result message from the
BSS. Any ACI alarms which the OMC-R shows as active alarms, that are not in the resync
list, are changed to the cleared state. If there are any new alarms in the list that the OMC-R
does not show as active, no immediate action is required, since the BSS reissues these alarms
later. When the ACI Fault intermittent alarm is being used for resync, the Report Type of
the alarm is resync alarm.
Additional information
The message Faulty ACI Alarm Set includes the following ACI path information:
• ACI.
• BSC-MMS device, timeslot, and group upon which the ACI exists.
68P02901W26-S 6-43
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
One or more devices in the ACI path are faulty and in need of replacement.
Procedure
1 If there are multiple ACIs in a path that have Faulty ACI Alarms active, one
of the devices in the path is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine which device is
to be replaced.
2 Send a field representative to the site to replace the relevant device.
6-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 42. BSS: Circuit fault cleared on Ater channel
Description
A particular Ater Channel Identifiers (ACI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or gone below the ACI error clear threshold, meaning thereby,
that a device in the ACI path is no longer faulty.
The OMC-R is notified any time that an ACI Clear notification message has been sent to the
alarms subsystem. The OMC-R receives a Faulty ACI clear intermittent alarm containing the
ACI, which is being cleared. The OMC-R uses each ACI Fault Clear intermittent alarm to clear
the Faulty ACI alarm on the ACI given in the alarm.
When the OMC-R receives a Faulty ACI clear intermittent alarm, it changes the displayed state
of the alarm for the ACI in the intermittent alarm to cleared. This scheme produces an FMIC
type functionality using intermittent alarms at the OMC-R and not at the BSS.
Memory limitations prevent the BSS from implementing FMIC alarms for every ACI. When the
OMC-R receives an ACI Fault Clear intermittent alarm that has an ADI indicating Global Reset,
the OMC-R clears all of the ACI CERM alarms.
Additional information
Possible causes
68P02901W26-S 6-45
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 43. BSS: Circuit fault detected on PCM circuit
Description
A particular Circuit Identity Code (CIC) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the CIC error generation threshold, indicating
that a device in the CIC path is faulty and need replacing. None of the devices in the CIC
path for the faulty CIC are taken Out Of Service (OOS) due to this alarm, which reports the
devices contained in the CIC path.
Alarm throttling is not allowed for this alarm. The OMC-R is notified when a CIC Fault
notification message has been sent to the alarms subsystem. The OMC-R receives a Faulty
CIC set intermittent alarm and the path information as described in the following additional
alarm data section.
The OMC-R uses each CIC Fault intermittent alarm to keep track of which CICs have alarms on
them. The BSS alarm subsystem does not keep track of which CICs have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives a list of all the
CICs for which the BSS has sent intermittent alarms (the BSS keeps track of the CICs that have
had alarms sent to them). The OMC-R receives the CIC list in the additional alarm data field of
one or more CIC Fault intermittent alarms. The OMC-R knows that it has received the entire list
of CICs when the OMC-R receives the Generic Result message from the BSS.
Any CIC alarms which the OMC-R shows as active alarms that are not in the resync list is
changed to the cleared state. If there are any new alarms in the list that the OMC-R does not
show as active, no immediate action is required, since the BSS reissues these alarms later.
When the CIC Fault intermittent alarm is used for resync, the Report Type of the alarm is
resync alarm.
Additional information
The message Faulty CIC Alarm Set includes the CIC when remote transcoding is used. The
message Faulty CIC Alarm Set includes: CIC, XCDR board ID, and XCDR DSP information when
local transcoding is used.
The CIC information is printed out in a format which is described in the relevant area of the BSS
Field Troubleshooting Manual (68P02901W51) for this alarm. An example of a format for the
CIC when remote transcoding is as follows:
68P02901W26-S 6-47
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
One of the devices in the CIC path is faulty and is in need of replacement.
Procedure
1 If there are multiple CICs in a path that have Faulty CIC Alarms active, one
of the devices in the path is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine which device is
to be replaced.
2 Send a field representative to the site to replace the relevant device.
6-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
Additional information
For the non-Call Processing global reset case, the additional data contains the CIC path
information, which includes the ADI (1 byte) and the CIC (2 bytes). For the Call Processing
global reset case, the additional data contains the Additional Data Identifier (1 byte) to notify
the OMC that a Call Processing global reset has occurred and a CLEAR should be initiated.
Possible causes
The failure causing TRAU Frame errors has cleared. Alternatively, the CIC alarms should
be cleared by Call Processing global reset.
68P02901W26-S 6-49
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 45. BSS: Circuit fault detected on GPRS circuit
Description
A particular GPRS Circuit Identifier (GCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or exceeded the GCI error generation threshold, meaning
that a device in the GCI route to the PCU is faulty and in need of replacement. None of the
devices in the GCI path to the PCU for the faulty GCI are taken OOS due to this alarm, which
simply reports the devices contained in the GCI path that is alarming. Alarm throttling is not
allowed for the Faulty GCI Alarm Set alarm.
The OMC-R is notified when a GCI Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty GCI set intermittent alarm and additional GCI
information as described in the following additional alarm data section.
The OMC-R uses each GCI Fault intermittent alarm to keep track of the GCIs that have alarms
on them. The BSS alarm subsystem does not keep track of which GCIs have active alarms on
them. Whenever the OMC-R performs an alarm resynchronization, the OMC receives a list of
all the GCIs for which the BSS has sent intermittent alarms (the BSS keeps track of the GCIs
that have had alarms sent to them).
The OMC-R receives the GCI list in the additional alarm data field of one or more GCI Fault
intermittent alarms. The OMC-R knows that it has received the entire list of GCIs when the
OMC receives the Result message from the BSS. Any GCI alarms which the OMC-R show as
active alarms that are not in the resync list are changed to the cleared state. If there are any
new alarms in the list that the OMC-R does not show as active, no immediate action is required
since the BSS reissues these alarms later. When the GCI Fault at Remote BTS intermittent alarm
is being used for resync, the Report Type of the alarm is resync alarm.
Additional Information
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.
68P02901W26-S 6-51
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
One of the devices in the GCI path to the PCU is faulty and is in need of replacement.
Procedure
1 If there are multiple GCIs using the same devices that have Faulty GCI
Alarms active, one of the devices is probably faulty and is in need of
replacement. Use the information, contained in the Alarm report produced
at the OMC-R, to determine which device requires replacement.
2 Send a field representative to the site to replace the relevant device.
6-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 46. BSS: Circuit fault cleared on GPRS circuit
Description
A particular GPRS Circuit Identifiers (GCI) Transcoding and Rate Adaption Unit (TRAU) Frame
sync loss error count has reached or gone below the GCI error clear threshold meaning thereby
that a device in the GCI path is no longer faulty. This alarm is an intermittent alarm sent to
the OMC-R and MMI.
The OMC-R is notified when a GCI Clear notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty GCI clear intermittent alarm containing the GCI,
which is being cleared. The OMC-R uses each GCI Fault Clear intermittent alarm to clear the
Faulty GCI alarm on the GCI given in the alarm.
When the OMC-R receives a Faulty GCI clear intermittent alarm, it changes the alarm for
the GCI in the intermittent alarm to cleared state. This scheme produces an FMIC type
functionality using intermittent alarms at the OMC-R and not at the BSS. Memory limitations at
the BSS prevent implementation of FMIC alarms for every GCI.
Possible causes
The failure causing TRAU frame errors have cleared for the GCI in the alarm clear message.
68P02901W26-S 6-53
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 47. BSS: Circuit fault detected on PATH channel
Description
The count of errors for a particular PIC TRAU frame sync loss has reached or exceeded the PIC
error generation threshold. This alarm indicates that a device in the PIC path is faulty and needs
replacement. None of the devices in the PIC path for the faulty PIC are taken Out Of Service
(OOS) due to this alarm, which simply reports the devices contained in the PIC path that are
responsible for the alarm. Alarm throttling is not allowed for the Faulty PIC Alarm Set alarm.
The OMC-R is notified any time that a PIC Fault notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty PIC set intermittent alarm and the path information as
described in the additional alarm data section. The OMC-R uses each PIC Fault intermittent
alarm to keep track of the PICs which have alarms on them. The BSS alarm subsystem does
not keep track of the PICs which have active alarms on them.
Whenever the OMC-R performs an alarm resynchronization, the OMC-R receives one or more
lists of the PICs for which the BSS has sent intermittent alarms (the BSS keeps track of the PICs
which have had alarms sent to them). The OMC-R receives the PIC lists in the additional alarm
data field of one or more PIC Fault intermittent alarms. The OMC-R knows it has received the
entire list of PICs when the OMC receives the Generic Result message from the BSS.
Any PIC alarms, which the OMC-R shows as active alarms that are not in the resync lists, is
changed to the clear state. If there are any new alarms in the lists that the OMC-R does not
show as active, no immediate action is required, since the BSS reissues the alarms later.
When the PIC Fault intermittent alarm is being used for resync, the Report Type of the alarm is
resync alarm.
Possible causes
One of the devices in the PIC path is faulty and is in need of replacement.
68P02901W26-S 6-55
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
1 If there are multiple PICs that use the same device and have PIC Alarms
active, one of these devices is probably faulty and should be replaced. Use
the information contained in the Alarm report to determine the device
which needs replacement.
2 Send a field representative to the site to replace the relevant device.
6-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48. BSS: Circuit fault cleared on PATH channel
Description
The count of errors for a particular PIC TRAU frame sync loss has reached or exceeded the PIC
error generation threshold. This alarm indicates that a device in the PIC path is faulty and
needs replacement. This alarm is an intermittent alarm sent to the OMC-R and Man Machine
Interface (MMI).
The OMC-R is notified any time that a PIC Clear notification message has been sent to the alarms
subsystem. The OMC-R receives a Faulty PIC clear intermittent alarm containing the PIC that is
being cleared. The OMC-R uses each PIC Fault Clear intermittent alarm to clear the Faulty PIC
alarm on the PIC given in the alarm. When it receives a Faulty PIC set intermittent alarm, the
OMC-R marks the PIC as alarming. When the OMC-R receives a Faulty PIC clear intermittent
alarm, it changes the displayed state of the alarm for the PIC in the intermittent alarm to clear.
This scheme produces an FMIC type functionality using intermittent alarms at the OMC-R and
not at the BSS. There is not enough memory at the BSS to implement FMIC alarms for each and
every PIC. When the OMC-R receives an ACI Fault Clear intermittent alarm that has an ADI
indicating Global Reset, the OMC-R clears all of the ACI CERM alarms.
Additional information
Possible causes
The failure causing TRAU Frame errors has cleared up for the PIC in the alarm clear message.
68P02901W26-S 6-57
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 49. BSS: Last LMTL link failure - Signaling point inaccessible
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 0 alarm.
See 0. BSS: Last MTL link failure - Signaling point inaccessible.
The BSS reports a BSS: Last LMTL link failure - Signaling point inaccessible alarm when
at least one LMTL has been equipped and yet no in-service LMTLs exist.
The signaling point code is inaccessible due to the failure of the last available LMTL link. When
this occurs, the BSS cannot support calls or send messages to the SMLC.
The alarm clears when there are no in-service LMTLs and at least one LMTL comes into service.
A single LMTL link provides a 64 kbps connection between the two pieces of equipment. One or
more LMTL links can be configured at BSC-to-Serving Mobile Location Centre (SMLC).
68P02901W26-S 6-59
Nov 2007
Possible causes Chapter 6: BSS Alarms
Possible causes
• The remote layer 2 responded with bad LSSU (SIOS, SIO, SIN, and SIE) frames causing
the link failure.
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive error rate that caused
the failure.
Procedure
Continued
6-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure 6-33 Last LMTL link failure - Signaling point inaccessible (Continued)
3 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the LMTLs and take
the appropriate action to return all LMTLs to
service.
not cleared The fault is probably at the SMLC.
Troubleshoot the SMLC fault.
4 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the LMTLs and take
the appropriate action to return all LMTLs to
service.
not cleared Go to step 5.
5 Attempt to return one of the LMTLs to service.
If one of the MTLs... Then...
returns to service Go to step 6.
does not return to service Send a field representative to the site to
determine the cause of the alarm and take
appropriate action.
6 Determine if the alarm is cleared.
If the alarm is... Then...
cleared Determine the status of the LMTLs and take
the appropriate action to return all LMTLs to
service.
not cleared Send a field representative to the site to
determine the cause of the alarm and take
appropriate action.
68P02901W26-S 6-61
Nov 2007
50. BSS: Call processing failure - SMLC detected SCCP down Chapter 6: BSS Alarms
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 1 alarm.
See 1. BSS: Call processing failure - MSC detected SCCP down on page 6-8.
The BSS reports a BSS Call processing failure - SMLC detected SCCP down alarm when the
SMLC sends the BSS a User Part Unavailable (UPU) message.
The BSS received a User Part Unavailable (UPU) message from the MSC indicating that the
Signaling Connection Control Part (SCCP) is down (unavailable). When this condition exists, the
BSS cannot support calls.
When the SCCP is down, the BSS continues to be able to support MS calls, but LMUs and
location attempts are out.
6-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
The BSS has received a UPU message from the BSS-based SMLC indicating that the SCCP
is unavailable.
Procedure
68P02901W26-S 6-63
Nov 2007
51. BSS: Call processing failure - SMLC detected BSSAP down Chapter 6: BSS Alarms
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 2 alarm.
See 2. BSS: Call processing failure - MSC detected BSSAP down on page 6-10.
The BSS reports a BSS Call processing failure - SMLC detected BSSAP down alarm when
the remote BSSAP layer is available.
The BSS received a Subsystem Prohibited (SSP) message from the SMLC indicating that
the BSS Application Part (BSSAP) is down (unavailable). When this condition exists, the BSS
cannot support calls.
When the BSSAP is down, the SMLC does not accept BSSAP messages from the BSS. This
BSSAP failure occurs at the SMLC.
The alarm clears when the remote BSSAP layer becomes available.
This alarm can clear when the last LMTL goes down.
6-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
The BSS has received an SSP message from the SMLC indicating that the BSSAP is unavailable.
Procedure
Send a field representative to the site to take the appropriate action and
resolve the alarm.
68P02901W26-S 6-65
Nov 2007
52. BSS: No SMLC acknowledgment for global reset Chapter 6: BSS Alarms
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 9 alarm.
See 9. BSS: No MSC acknowledgment for global reset on page 6-25.
The BSS reports a BSS No SMLC acknowledgment for global reset alarm when the SMLC
does not send the BSS a global reset acknowledgment message.
The BSS repeated the global reset message the maximum number of times without receiving an
acknowledgment from the SMLC.
Possible causes
Procedure
6-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 53. BSS: Erroneous layer 3 message received from SMLC
Description
This alarm indicates that the BSS has received a layer 3 message from the BSS-based SMLC
that is inappropriate for the state of the specified connection (wrong message).
This field displays the erroneous layer 3 message that the BSS receives from the BSS-based
SMLC.
Possible causes
For a specified connection, an SCCP Connection Confirm message is expected, but one of
the following is received:
• An SCCP Connection Refused message.
Procedure
68P02901W26-S 6-67
Nov 2007
54. BSS: Confusion message received from the SMLC Chapter 6: BSS Alarms
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 11
alarm. See 11. BSS: Confusion message received from the MSC on page 6-27.
The BSS reports a BSS Confusion message received from the SMLC alarm when the SMLC
sends the BSS a BSSMAP Confusion message.
The Additional information field displays the BSSMAP Confusion message that the BSS
receives from the SMLC.
Possible causes
The SMLC did not understand a layer 3 message from the BSS.
Procedure
6-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 55. BSS: Received page for invalid cell from SMLC
Description
This alarm relates to the Lb-interface, but in all other respects it is identical to the BSS 26
alarm. See 26. BSS: Received page for invalid cell from MSC on page 6-38.
The BSS reports a BSS Received page for invalid cell from SMLC alarm when the SMLC
sends the BSS a Paging message for an invalid cell.
Possible causes
The SMLC and BSS databases do not have matching cell ID lists.
68P02901W26-S 6-69
Nov 2007
Procedure Chapter 6: BSS Alarms
Procedure
6-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 59. BSS: Last PCU failed
Description
None.
Possible causes
PCUs OOS.
Procedure
68P02901W26-S 6-71
Nov 2007
60. BSS: Circuit fault detected on GPRS circuit Chapter 6: BSS Alarms
{26740}
Description
This alarm occurs when the PSI DSP's TRAU frame sync loss error count has reached or
exceeded the DSP error generation threshold as a device in the route of DSP to the PCU is
faulty and needs replacing.
For non-alarm resynch, the additional data contains the following GPRS Circuit Identifier
related information:
Byte Denition
First Additional Data Identifier, 0x2d
For alarm resynch, the additional data contains the following GPRS Circuit Identifier related
information:
Byte Denition
First Additional Data Identifier, 0xa8
After the first three bytes, many circuits are listed. For each circuit, the bytes are distributed
as follows:
Byte Denition
First PSI DSP ID
6-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 6-73
Nov 2007
61. BSS: Circuit fault cleared on GPRS circuit Chapter 6: BSS Alarms
{26740}
Description
This alarm occurs when the PSI DSP's TRAU frame sync loss error count is less than or equal
to the DSP error clear threshold as a device in the DSP path is no longer faulty. This alarm
is sent to OMC and MMI.
Byte Denition
First Additional Data Identifier, 0x2c
Second PCU ID
Byte Denition
First Additional Data Identifier, 0x2d
Second PSI DSP ID
Possible causes
6-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 6-75
Nov 2007
Procedure Chapter 6: BSS Alarms
6-76 68P02901W26-S
Nov 2007
Chapter
BTP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details BTP Alarms and includes the following alarm procedures:
• 1. BTP: EEPROM Flash failure - No valid bootstrap code object present on page 7-4.
• 32. BTP: TDM interface failure - Assigned timeslot counter underflow on page 7-20.
• 33. BTP: TDM interface failure - Assigned timeslot counter overflow on page 7-22.
• 34. BTP: TDM interface failure - TDM parity error on page 7-24.
• 42. BTP: Site reset occurred due to front panel reset on page 7-32.
• 47. BTP: Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected on page 7-33.
• 48. BTP: Memory location is corrupt. Replace GPROC board on page 7-35.
68P02901W26-S 7-1
Nov 2007
Procedure Chapter 7: BTP Alarms
7-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to BTP alarms
BTP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Base
Transceiver Processor (BTP) device.
FRUs
A BTP device can be equipped on one of the FRUs shown in Table 7-1.
FRU Description
GPROC2 InCell GPROC2 board.
GPROC3/GPROC3-2 InCell GPROC3/GPROC3-2 board.
H2SC Horizon II macro Site Controller.
MCU Micro Controller Unit board.
MCUF Micro Controller Unit board with dual FMUX.
MCUm M-Cell micro Micro Controller Unit board.
ARENAm (MCU) Horizon micro (M-Cell arena) Micro Controller
Unit board.
ARENA MAC (MCU) Horizon compact (M-Cell arena) Macro) Micro
Controller Unit board.
HORIZONMIC2 (MCU) Horizon micro2 Micro Controller Unit board.
HORIZONCOM2 (MCU) Horizon compact2 Micro Controller Unit board.
• Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS
to mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
• At the BTS, the BTP can only be GPROC2 or GPROC3/GPROC3-2.
68P02901W26-S 7-3
Nov 2007
1. BTP: EEPROM Flash failure - No valid bootstrap code object present Chapter 7: BTP Alarms
Description
The Initialization Process (IP) has determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt. In this case, initialization is not permitted.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
7-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 7-1 EEPROM Flash failure - No valid bootstrap code object present
68P02901W26-S 7-5
Nov 2007
8. BTP: EEPROM Flash object failure Chapter 7: BTP Alarms
Description
The size of the user start address in the header information of the bootstrap code object (Object
15) is incorrect. As a result, reprogramming is not initiated.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is incorrectly programmed with regard to the
GPROC EEPROM address space.
7-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-7
Nov 2007
17. BTP: EEPROM ash programming failure Chapter 7: BTP Alarms
Description
An attempt to erase bank 0 before reprogramming a flash EEPROM was unsuccessful. Bank 0
contains a byte that can be reprogrammed after a bank erase.
This fault condition is not a problem unless the GPROC is being reset, in which case
the GPROC is rendered useless.
Possible causes
7-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-9
Nov 2007
20. BTP: LAPD controller failure Chapter 7: BTP Alarms
Description
Two bytes are displayed. Ignore the first byte, the second byte has a value of 1 or 2. The second
byte value descriptions are shown in Table 7-2.
Value Description
1 The LAPD controller has encountered a non recoverable internal fault.
2 The LAPD controller cannot open a new channel for RSL link.
Possible causes
• The micro code in the LAPD controller has encountered a fatal exception.
• The LAPD controller cannot open a new LAPD channel due to an internal error.
Procedure
7-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. BTP: EEPROM ash 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 causes
Procedure
68P02901W26-S 7-11
Nov 2007
Procedure Chapter 7: BTP Alarms
7-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. BTP: SWFM indication
Description
The system has detected a software processing error (SWFM) for a BTP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
Procedure
68P02901W26-S 7-13
Nov 2007
30. BTP: Clock A signal loss Chapter 7: BTP Alarms
Description
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 causes the site to go OOS.
The fault condition reported by this alarm may cause the site to go OOS.
Possible causes
7-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 7-15
Nov 2007
Procedure Chapter 7: BTP Alarms
7-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. BTP: Clock B signal loss
Description
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 causes the site to go OOS.
Possible causes
68P02901W26-S 7-17
Nov 2007
Procedure Chapter 7: BTP Alarms
Procedure
Continued
7-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 7-19
Nov 2007
32. BTP: TDM interface failure - Assigned timeslot counter underow Chapter 7: BTP Alarms
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
7-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-21
Nov 2007
33. BTP: TDM interface failure - Assigned timeslot counter overow Chapter 7: BTP Alarms
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
7-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-23
Nov 2007
34. BTP: TDM interface failure - TDM parity error Chapter 7: BTP Alarms
Description
Possible causes
7-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-25
Nov 2007
35. BTP: LAN connection failure Chapter 7: BTP Alarms
Description
The LAN connection between the master GPROC and any other equipped BTP on the LAN failed.
System action
The system places the BTP OOS. If the BTP is the master GPROC, the site resets.
Possible causes
7-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-27
Nov 2007
39. BTP: Software failure Chapter 7: BTP Alarms
Description
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 the
programmers.
Possible causes
7-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-29
Nov 2007
40. BTP: Spurious interrupt Chapter 7: BTP Alarms
Description
The BTP received and acknowledged an interrupt message but did not receive a response from
the device generating the interrupt.
Possible causes
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or some
other cause.
7-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-31
Nov 2007
42. BTP: Site reset occurred due to front panel reset Chapter 7: BTP Alarms
Description
The site was reset when the front switch on the MCU was pressed. This alarm is reported after
the site comes back into service after the reset is complete.
This alarm is reported for M-Cell2, M-Cell6, M-Cell micro, Horizon, and Horizon
II macro sites.
Possible causes
The reset switch on the front panel of the MCU was pressed.
Procedure
1 Investigate the reason for the front panel reset of the BTP MCU.
2 Clear the alarm.
7-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 47. BTP:
Unexpected board type: GPROC2 or GPROC3/GPROC3-2 expected
Description
A GPROC was detected in a slot where the system expected to find a GPROC2 or
GPROC3/GPROC3-2. BTPs exist only at InCell sites, where GPROC2 or GPROC3/GPROC3-2s
are mandatory.
If this condition occurs in an InCell site, the GPROC board does not come into service. The
maximum number of timeslots a GPROC can use is 16. A GPROC2 or GPROC3/GPROC3-2 can
use 8, 16 or 32 timeslots.
Possible causes
If this condition occurs in an InCell site, the GPROC board does not come into service.
68P02901W26-S 7-33
Nov 2007
Procedure Chapter 7: BTP Alarms
Procedure
7-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Procedure
68P02901W26-S 7-35
Nov 2007
50. BTP: EEPROM SW ash programming failure Chapter 7: BTP Alarms
Description
This alarm is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes
Procedure
If the board does not reset automatically, a manual reset can be performed
to reload the BOOTROM object.
7-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 51. BTP: EEPROM HW ash programming failure
Description
Possible causes
Procedure
68P02901W26-S 7-37
Nov 2007
231. BTP: TDM interface conguration failure Chapter 7: BTP Alarms
Description
System action
The system automatically resets the BTP. If the alarm recurs, the BTP is placed OOS.
Possible causes
• The GPROC device could not be programmed to the designated timeslot when swapping
the TDM highways.
7-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 7-39
Nov 2007
232. BTP: Processor bus communication failure Chapter 7: BTP Alarms
Description
A BTP board device has lost the ability to communicate to the peripheral boards through the
MCAP bus.
Possible causes
• The part of the BTP that supports the MCAP bus access failed.
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
1 Attempt to bring back the BTP In Service (INS). If the device is back in
service, the alarm condition has ceased and further fault isolation is not
required. If the device remains OOS, go to step 2.
2 Replace the BTP board.
7-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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-Cell micro, 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 involves a combination of these hardware units: FOX, FMUX,
MCU, XMUX, or transceiver unit.
Possible causes
• The DRI and/or BTP portion that supports active BTP link connection failed.
68P02901W26-S 7-41
Nov 2007
Procedure Chapter 7: BTP Alarms
Procedure
1 Determine if the Device Failure (BTP 254 or DRI 254) alarm was
received.
If this alarm is reported Then...
with...
a DRI 254 alarm Send a field representative to the
site to replace the transceiver unit.
a BTP 254 alarm Send a field representative to the
site to replace the MCU.
neither a DRI 254 alarm nor a Go to step 2.
BTP 254 alarm
2 Determine the state of the DRI.
If DRI is... Then...
busy-unlocked or Go to step 4.
enabled-unlocked
not busy-unlocked or Attempt to return the DRI to
enabled-unlocked service and then go to step 3.
3 Determine if the alarm is clear.
If the alarm is... Then...
clear The fault condition no longer exists.
If there is a recurrence of this
alarm, send a field representative
to the site to replace the transceiver
unit.
not clear Go to step 4.
4 Determine the state of the BTP.
If BTP is... Then...
busy-unlocked or The fault condition no longer exists.
enabled-unlocked If there is a recurrence of this
alarm, send a field representative
to the site to replace the MCU.
not busy-unlocked or Attempt to return the BTP to
enabled-unlocked service and then go to step 5.
Continued
7-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 7-43
Nov 2007
235. BTP: Standby link connection failure Chapter 7: BTP Alarms
Description
The standby link connection from the transceiver unit to the standby BTP failed.
This alarm is reported for M-Cell2, M-Cell6, M-Cell micro, 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 involves a combination of these hardware units: FOX, FMUX,
MCU, XMUX, or transceiver unit.
Possible causes
• The DRI and/or BTP portion that supports active BTP link connection failed.
7-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the Device Failure (BTP 254) alarm was also received.
If a BTP 254 alarm... Then...
is received Send a field representative to the
site to replace the MCU.
is not received Go to step 2.
2 Determine the state of the BTP.
If BTP is... Then...
busy-unlocked or The fault condition no longer
enabled-unlocked exists. If there is a recurrence
of this alarm, send a field
representative to the site to
replace the MCU.
not busy-unlocked or Attempt to return the BTP to
enabled-unlocked service and then go to step 3.
3 Determine if the alarm is clear.
If the alarm is... Then...
clear The fault condition no longer
exists. If there is a recurrence
of this alarm, send a field
representative to the site to
replace the MCU.
not clear Send a field representative to the
site to replace the MCU.
68P02901W26-S 7-45
Nov 2007
Procedure Chapter 7: BTP Alarms
7-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 236. BTP: Slow ash failure
Description
A failure to read or write to a slow flash EEPROM was detected for the transceiver unit.
Possible causes
68P02901W26-S 7-47
Nov 2007
Procedure Chapter 7: BTP Alarms
Procedure
7-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 7-49
Nov 2007
Procedure Chapter 7: BTP Alarms
Procedure
7-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 9 bytes containing process information, as shown in
Table 7-3. Bytes one through eight is useful only to the programmers. Byte nine is the reason
code for the alarm.
Possible causes
Procedure
68P02901W26-S 7-51
Nov 2007
Procedure Chapter 7: BTP Alarms
7-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. BTP: Device failure
Description
The BTP was taken OOS by the GPROC Fault Management System.
System action
A single byte is displayed in the Additional information field identifying the type of site reset, as
shown in Table 7-4.
Value Denition
01 Hard reset
02 Soft reset
Possible causes
Procedure
68P02901W26-S 7-53
Nov 2007
Procedure Chapter 7: BTP Alarms
Wait approximately 10 minutes after this alarm is received to allow the site to reset
before following this procedure.
7-54 68P02901W26-S
Nov 2007
Chapter
CAB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CAB Alarms and includes the following alarm procedures:
• 25. CAB: External power booster amplifier 1 failure on page 8-3.
68P02901W26-S 8-1
Nov 2007
Introduction to CAB alarms Chapter 8: CAB Alarms
CAB alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CAB device.
FRUs
A CAB device can be equipped on one of the FRUs shown in Table 8-1.
FRU Description
ARENA MACRO Horizon compact (M-Cell arena Macro)
cabinet.
HORIZONMACRO Horizon macro cabinet.
HORIZONCOMPACT2 Horizon compact2 cabinet.
HORIZONMICRO2 Horizon micro2 cabinet.
MCELL TWO M-Cell2 cabinet.
MCELL MICRO M-Cell micro cabinet.
MCELL CITY M-Cell city cabinet.
MCELL SIX M-Cell6 cabinet.
8-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. CAB: External power booster amplier 1 failure
Description
Amplifier 1 in the external power booster failed. When this condition occurs, the transmitted
power to Channel 1 transmit antenna is reduced to approximately 0.8 W. This power reduction
adversely affects macro cell coverage.
This alarm is generated only for Horizon compact2 equipment. However, the database
CAB entry for the Horizon compact2 can also be set to Horizon micro2. Hence, this
alarm is supported for both Horizon compact2 and Horizon micro2 database entries.
Possible causes
68P02901W26-S 8-3
Nov 2007
Procedure Chapter 8: CAB Alarms
Procedure
Send a field representative to the site to replace the external power booster.
8-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. CAB: External power booster amplier 2 failure
Description
Amplifier 2 in the external power booster failed. When this condition occurs, the transmitted
power to Channel 2 transmit antenna is reduced to approximately 0.8 W. This power reduction
adversely affects macro cell coverage.
This alarm is generated only for Horizon compact2 equipment. However, the database
CAB entry for the Horizon compact2 can also be set to Horizon micro2. Hence, this
alarm is supported for both Horizon compact2 and Horizon micro2 database entries.
Possible causes
68P02901W26-S 8-5
Nov 2007
Procedure Chapter 8: CAB Alarms
Procedure
Send a field representative to the site to replace the external power booster.
8-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. CAB: External power booster failure
Description
The external power booster failed. When this occurs, the transmitted power to both transmit
antennae is reduced to approximately 0.8 W. This power reduction adversely affects macro
cell coverage.
This alarm is generated only for Horizon compact2 equipment. However, the database
CAB entry for the Horizon compact2 can also be set to Horizon micro2. Hence, this
alarm is supported for both Horizon compact2 and Horizon micro2 database entries.
Possible causes
68P02901W26-S 8-7
Nov 2007
Procedure Chapter 8: CAB Alarms
Procedure
1 Send a field representative to the site to determine the cause of the failure.
Take appropriate action and resolve the alarm.
8-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. CAB: Database conguration 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, Horizon macro, and Horizon II macro. The alarm
is raised or cleared only if there are one or more in-service DRIs in the cabinet.
• The database extension cabinet type is of any type other than HORIZON2MINI_EXT and
FRU type is Horizon II mini.
The BSS clears this alarm if the database extension cabinet type is HORIZON2MINI_EXT and
FRU type is Horizon II mini.
Possible causes
The database configuration is not correct for the type of hardware at the site.
68P02901W26-S 8-9
Nov 2007
Procedure Chapter 8: CAB Alarms
Procedure
8-10 68P02901W26-S
Nov 2007
Chapter
CAGE Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details Cage Alarms and includes the following alarm procedures:
• 20 - 25. CAGE: CLKX slot 2-7 communication failure on page 9-3.
• 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.
• 37 - 39. CAGE: Power supply unit #1-3 - Over temperature on page 9-15.
• 41 - 42. CAGE: Local KSWX/DSWX slot 0-1 communication failure on page 9-19.
• 43 - 47. CAGE: Remote KSWX/DSWX slot 2-6 communication failure on page 9-22.
• 48 - 52. CAGE: Remote KSWX/DSWX slot 24-28 communication failure on page 9-25.
• 56 - 58. CAGE: Expansion KSWX/DSWX slot 21-23 communication failure on page 9-31.
68P02901W26-S 9-1
Nov 2007
Introduction to CAGE alarms Chapter 9: CAGE Alarms
CAGE alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CAGE device.
CAGE alarms are generated for the half size cards used to extend clock and data signals from
one cabinet to another, and for power supply units in the PCU.
9-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20 - 25. CAGE: CLKX slot 2-7 communication failure
Description
The system either failed to communicate with the CLKX or detected that the card in the slot
specified in the alarm message is not a CLKX card.
CLKX cards can be installed in slot 2 through slot 7 to extend the Clock Distribution Bus (CBUS)
to a cage in which a GCLK is not installed.
GCLK=>CLKX=>Local KSWX=>CBUS
System action
Since the faulty CLKX is in the CBUS pathway, a CLKX failure causes the CBUS to be placed
OOS. If a standby CBUS is unavailable, the cage is disabled causing a site reset.
A single byte is displayed in the Additional information field. The first digit is the hardware
revision number of the card in the slot. The second digit represents the board type. Table 9-1
shows the Additional information field values.
The value ff is displayed if a card is not inserted in the slot or if the polling software
failed to communicate with the CLKX card.
68P02901W26-S 9-3
Nov 2007
Possible causes Chapter 9: CAGE Alarms
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action and resolve the alarm.
9-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 9-5
Nov 2007
26 - 27. CAGE: LANX slot 19-20 communication failure Chapter 9: CAGE Alarms
Description
The system either failed to communicate with the LANX or detected that the card in the slot
specified in the alarm message is not a LANX card.
Hot pull of a busy LANX is not supported. If a hot pull of a LANX card is attempted,
the site resets.
LANX cards may be installed in slots 19 or 20 to extend the LAN to all other cages at a site.
System action
When this alarm is reported, the associated LAN and PBUS is placed OOS.
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-2
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 LANX card.
9-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action and resolve the alarm.
68P02901W26-S 9-7
Nov 2007
Procedure Chapter 9: CAGE Alarms
9-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28 - 30. CAGE: Power supply unit #1-3 - Output failure
Description
This alarm indicates that the power supplied by the PSU in the PCU cage is beyond the tolerance
limit of ±5% of the expected value.
If two PSUs fail, the last PSU has to drive all the boards in the cage and becomes overloaded.
If the third PSU fails, it indicates a critical condition, since the boards in the cage are not
powered.
This alarm is cleared when the affected PSU becomes operational or when the Not
Detected alarm of the affected PSU is raised.
Possible causes
• There is a problem with the input power supply of the PCU cage.
68P02901W26-S 9-9
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
Send a field representative to the site to take appropriate action and resolve
the alarm.
9-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31 - 33. CAGE: Power supply unit #1-3 - Not detected
Description
This alarm indicates that the related PSU is not present in the PCU cage.
This alarm is cleared when the affected PSU is detected in its slot.
Possible causes
• A PSU is not correctly inserted in the related slot of the PCU cage.
68P02901W26-S 9-11
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
Send a field representative to the site to take appropriate action and resolve
the alarm.
9-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34 - 36 CAGE: Power supply unit #1-3 - Fan failure
Description
This alarm indicates that the fan housed in the related PSU has failed.
This alarm is cleared when the fan housed in the affected PSU becomes operational
or when the Not Detected alarm for the related PSU is raised.
Possible causes
68P02901W26-S 9-13
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
9-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 37 - 39. CAGE: Power supply unit #1-3 - Over temperature
Description
This alarm indicates that the related PSU has failed as it has detected a rise in the air
temperature to approximately 40 °C. This temperature is near the upper limits for components
in the system, but they are not in immediate danger of damage.
This alarm is cleared when the over-temperature condition is cleared or the Not
Detected alarm of the affected PSU is raised.
Possible causes
68P02901W26-S 9-15
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
Send a field representative to the site to take appropriate action and resolve
the alarm.
9-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 state indicates a critical failure of the cooling system in the
cage or an excessive rise in ambient temperature.
Possible causes
68P02901W26-S 9-17
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
Send a field representative to the site and take appropriate action and
resolve the alarm.
9-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41 - 42. CAGE: Local KSWX/DSWX slot 0-1 communication failure
Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
Slot 0 and slot 1 are reserved for KSWX/DSWX cards that provide one or both of the following
functions:
• Extend clock signals from a GCLK in another cage to the Clock Distribution Bus (CBUS) in
the cage where the KSWX/DSWX is installed.
GCLK=>CLKX=>Local KSWX/DSWX=>CBUS
• Extend the TDM Bus (TBUS) from an associated KSW installed in another cage to the TBUS
in the cage where the KSWX/DSWX is installed.
System action
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-3
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 KSWX/DSWX card.
68P02901W26-S 9-19
Nov 2007
Possible causes Chapter 9: CAGE Alarms
Possible causes
9-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 If a faulty KSW is not installed in the same cage as the KSWX/DSWX, the
TBUS and the CBUS is placed OOS.
3 If a standby TBUS and CBUS are unavailable, the cage is disabled causing
a site reset.
68P02901W26-S 9-21
Nov 2007
43 - 47. CAGE: Remote KSWX/DSWX slot 2-6 communication failure Chapter 9: CAGE Alarms
Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
Remote KSWX/DSWX cards can be installed in slots 2 through 6, to extend the TDM Bus (TBUS)
from an associated KSW, installed in the same cage as the KSWX/DSWX to another cage.
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-4
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 KSWX/DSWX card.
9-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
68P02901W26-S 9-23
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Since the faulty KSWX/DSWX is in the TBUS pathway, the TBUS in the
extended cage is placed OOS. If a standby TBUS is unavailable, the cage is
disabled causing a site reset.
9-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 48 - 52.
CAGE: Remote KSWX/DSWX slot 24-28 communication failure
Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
Remote KSWX/DSWX cards can be installed in slot 2 through slot 6, to extend the TDM Bus
(TBUS) from an associated KSW, installed in the same cage as the KSWX/DSWX to another cage.
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-5
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 KSWX/DSWX card.
68P02901W26-S 9-25
Nov 2007
Possible causes Chapter 9: CAGE Alarms
Possible causes
9-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Since the faulty KSWX/DSWX is in the TBUS pathway, the TBUS in the
extended cage is placed OOS. If a standby TBUS is unavailable, the cage is
disabled causing a site reset.
68P02901W26-S 9-27
Nov 2007
53 - 55. CAGE: Expansion KSWX/DSWX slot 7- 9 communication failure Chapter 9: CAGE Alarms
Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
KSWX/DSWX cards can be installed in slot 7 through slot 9 to expand the number of TDM
timeslots by adding KSWs.
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-6
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 KSWX/DSWX card.
9-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
68P02901W26-S 9-29
Nov 2007
Procedure Chapter 9: CAGE Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Since the faulty KSWX/DSWX is in the TBUS pathway, the TBUS in the
extended cage is placed OOS. If a standby TBUS is unavailable, the cage is
disabled causing a site reset.
9-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 56 - 58.
CAGE: Expansion KSWX/DSWX slot 21-23 communication failure
Description
The system either failed to communicate with the KSWX/DSWX or detected that the card in the
slot specified in the alarm message is not a KSWX/DSWX card.
KSWX/DSWX cards can be installed in slots 21 through 23 to expand the number of TDM
timeslots by adding KSWs.
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-7
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 KSWX/DSWX card.
68P02901W26-S 9-31
Nov 2007
Possible causes Chapter 9: CAGE Alarms
Possible causes
9-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Since the faulty KSWX/DSWX is in the TBUS pathway, the TBUS in the
extended cage is placed OOS. If a standby TBUS is unavailable, the cage is
disabled causing a site reset.
68P02901W26-S 9-33
Nov 2007
59 - 76. CAGE: DSWX/KSWX mismatch Chapter 9: CAGE Alarms
Description
The TDM device reporting this alarm remains out of service while this condition exists.
Possible causes
The KSWX in slot 0 has been paired with a DSWX or the DSWX has been paired with the KSWX.
9-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Replace the mismatched card with the appropriate card to match its partner.
3 A DSWX must be paired with another DSWX and a KSWX must be paired
with another KSWX.
68P02901W26-S 9-35
Nov 2007
Procedure Chapter 9: CAGE Alarms
9-36 68P02901W26-S
Nov 2007
Chapter
10
CBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CBL and includes the following alarm procedures:
• 0. CBL: Invalid received frames - PM on page 10-3.
68P02901W26-S 10-1
Nov 2007
Introduction to CBL alarms Chapter 10: CBL Alarms
CBL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Cell Broadcast
Link (CBL) alarms.
10-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. CBL: Invalid received frames - PM
Description
This statistic counts the number of the invalid frames received on the X.25 link.
For further information, refer to the CBL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 10-3
Nov 2007
Procedure Chapter 10: CBL Alarms
10-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. CBL: FRMR frames - PM
Description
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, refer to the CBL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
68P02901W26-S 10-5
Nov 2007
Procedure Chapter 10: CBL Alarms
Procedure
Determine if this alarm is persistently reported. Perform the following procedure to resolve
the alarm.
10-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CBL: Expiration of N2 - PM
2. CBL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates that the maximum number of link alignment retries has been attempted
without success.
For further information, refer to the CBL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The X.25 link between the CBC and the BSC failed due to a hardware fault or repair action.
68P02901W26-S 10-7
Nov 2007
Procedure Chapter 10: CBL Alarms
Procedure
Determine if this alarm is persistently reported. Perform the following procedure to resolve
the alarm.
10-8 68P02901W26-S
Nov 2007
Chapter
11
CBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CBUS alarms and includes the following alarm procedures:
• 0. CBUS: Over 50% of boards detected clock failure on page 11-3.
68P02901W26-S 11-1
Nov 2007
Introduction to CBUS alarms Chapter 11: CBUS Alarms
CBUS alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Clock
Distribution Bus (CBUS) device.
The CBUS alarms are generated when a fault condition occurs within the link which carries the
Generic Clock (GCLK) signals to the devices in a cage.
11-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. CBUS: Over 50% of boards detected clock failure
Description
Over 50% of the GPROC and peripheral boards in a cage have reported clocking failures.
System action
When this alarm occurs, if the faulty CBUS is in a Busy-Unlocked device state, the system
automatically attempts to swap its functionality to the redundant CBUS. In order for a swap to
occur, a redundant CBUS (Enabled-Unlocked) must be available.
If a redundant CBUS is not available for a swap, disable the associated CAGE device. This
action causes a site reset. After the site reset, if this fault condition is still present, the affected
CAGE remains OOS, however, the site returns to service. Also, any devices located in the
disabled cage remain OOS.
If this alarm is generated for a redundant CBUS, no automatic CBUS swap can occur. In this
case, the faulty CBUS is disabled.
Possible causes
• All boards that reported the problem have failed. This event is unlikely.
68P02901W26-S 11-3
Nov 2007
Procedure Chapter 11: CBUS Alarms
Procedure
Wait approximately 10 minutes after this alarm is received to allow the site to reset
before following this procedure.
1 Determine the state of the affected CBUS using the state command
in a TTY window.
If the CBUS is... Then...
busy-unlocked The fault condition no longer
exists. Monitor the system for a
recurrence of this alarm.
disabled-unlocked The system successfully
swapped the CBUSs. This
indicates an equipment problem.
Go to step 2.
not busy-unlocked or The system did not successfully
disabled-unlocked swap the CBUSs. A redundant
CBUS is not equipped or available.
In this case the CAGE and all
devices in the CAGE remain OOS.
Go to step 2.
2 Determine if any of the devices in the affected CAGE reported an
alarm.
If any devices... Then...
reported an alarm Resolve the individual alarms.
did not report an alarm The fault condition no longer
exists. Monitor the system for a
recurrence of this alarm.
11-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CBUS: Master CBUS signal provided by slave GCLK
Description
The slave GCLK provides the clock signal output on the master CBUS.
This alarm is a warning that any action on the redundant GCLK is likely to have a
negative impact on one or more cages at a site. This impact is because the master
GCLK signal is fed through the slave GCLK board before it is extended to the master
CBUS. If the slave GCLK is physically removed from the cage, the site is reset due to
a loss of the clock signal.
Possible causes
• The fiber link between the CLKX board and KSWX board is faulty.
• Backplane problems with the CBUS are associated with the master GCLK.
68P02901W26-S 11-5
Nov 2007
Procedure Chapter 11: CBUS Alarms
Procedure
To resolve the alarm, carry out the follow the following procedure.
11-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. CBUS: Local KSWX/DSWX clock ber failure
Description
The absence of a clock signal was detected while polling a KSWX/DSWX board.
System action
When this alarm occurs and the faulty CBUS is in a Busy-Unlocked device state, the system
automatically attempts to swap its functionality to the redundant CBUS. In order for a swap to
occur, a redundant CBUS (Enabled-Unlocked) must be available.
If a redundant CBUS is not available for a swap, disable the associated CAGE device. This
action causes a site reset. After the site reset, if this fault condition is still present, the affected
CAGE remains OOS; however, the site returns to service. Also, any devices located in the
disabled cage remain OOS.
If this alarm is generated for a redundant CBUS, no automatic CBUS swap can occur. In this
case, the faulty CBUS is disabled.
Possible causes
• The CLKX fiber link or the fiber port on the CLKX is faulty.
68P02901W26-S 11-7
Nov 2007
Procedure Chapter 11: CBUS Alarms
Procedure
Send a field representative to the site to determine the cause of the alarm
and take appropriate action to resolve the alarm.
11-8 68P02901W26-S
Nov 2007
Chapter
12
CELL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CELL alarms and includes the following alarm procedures:
• 0. CELL: Flow control procedure has started barring normal calls from access classes 0-9
on page 12-4.
• 2. CELL: Radio subsystem software error - Detected page overflow on page 12-11.
• 5. CELL: No cell (BVC) block acknowledgment from the SGSN on page 12-19.
• 10. CELL: GPRS unavailable - No cell (BVC) reset ack from the SGSN on page 12-27.
• 10. CELL: Intra-cell handover failed and mobile lost - PM on page 12-28.
• 11. CELL: GPRS unavailable - No cell (BVC) unblock ack from the SGSN on page 12-30.
• 11. CELL: Intra-BSS handover primary target cell blocked - PM on page 12-31.
• 13. CELL: GPRS unavailable - No GPRS capable carriers available on page 12-33.
• 13. CELL: Intra-BSS handover failed and recovered to org channel - PM on page 12-34.
• 14. CELL: Intra-BSS handover failed and mobile lost - PM on page 12-36.
• 14. CELL: GPRS unavailable - PBCCH timeslot out of sync on page 12-38.
68P02901W26-S 12-1
Nov 2007
Procedure Chapter 12: CELL Alarms
• 15. CELL: Inter-BSS handover, MS handover failed message received PM on page 12-40.
• 18. CELL: Handover failure to the MSC due to all possible errors except no channels -
PM on page 12-45.
• 19. CELL: Bad handover reference numbers from the MS - PM on page 12-49.
• 22. CELL: Mobile assign command to MS blocked (No channel available) - PM on page
12-53.
12-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to CELL alarms
• EGPRS Unavailable.
This section describes Alarms requirements necessary to support Full GSM Cell ID.
The BSS sends Full GSM Cell ID (MCC, MNC, LAC, CI) over the OMC <=> BSS interface for
functional unit list involving a cell.
CELL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the CELL device.
68P02901W26-S 12-3
Nov 2007
0. CELL: Flow control procedure has started barring normal calls from access classes 0-9 Chapter 12: CELL Alarms
Description
The flow control procedure for a cell is initiated for MS access classes 0 through 9. Flow control
is initiated when the BSS is congested. The purpose of the procedure is limiting the number of
new calls from access classes 0 through 9.
System action
The access classes (0-9) are gradually barred from the affected cell. An update is broadcast
to the MSs using BCCH messages.
One of the reason codes shown in Table 12-1 appears in the Additional information field of
the alarm output.
12-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Determine the traffic level on the cell. Depending on the traffic level the following inferences
can be drawn:
Procedure 12-1 Flow control procedure has started barring normal calls from access
classes 0-9
If... Then...
high The system is operating correctly.
Wait until the traffic level falls
below the levels specified for the
levels specified for the congestion
threshold database parameters.
not busy-unlocked A hardware problem probably
exists on the system. Initiate
isolation and corrective actions to
return the hardware components
to service.
68P02901W26-S 12-5
Nov 2007
0. CELL: Radio frequency losses while using an SDCCH - PM Chapter 12: CELL Alarms
Description
This statistic counts the number of calls lost while using an SDCCH due to RF problems. If a
TCH is reconfigured as an SDCCH, only the SDCCH statistics are configured.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
12-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if there are any currently active hardware alarms. To resolve the alarm, perform the
following procedure.
68P02901W26-S 12-7
Nov 2007
1. CELL: Cell radio timeslot capacity loss Chapter 12: CELL Alarms
Description
The first timeslot of a transceiver is placed OOS by operator action. This alarm notifies the
operator that the capacity of the cell has been reduced due to the action.
Possible causes
Procedure
12-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. CELL: Attempt at allocating an SDCCH failed - PM
Description
This statistic counts the number of times that an attempt to seize a stand-alone Dedicated
Control Channel (SDCCH) was rejected because of SDCCH congestion.
When an attempt to allocate an SDCCH fails, an SDCCH reject message is sent to the MS in
response to that channel request.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• An SDCCH has not been designated as the destination SDCCH for a handover due to call
traffic congestion.
68P02901W26-S 12-9
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Determine if there are any currently active hardware alarms. Perform the following procedure
to resolve the alarm:
12-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CELL: Radio subsystem software error - Detected page overow
Description
The Radio Subsystem (RSS) detected a paging queue overflow for a specific paging group
within the last 5 minutes.
The contents of the Additional information field for this alarm are shown in Table 12-2.
Possible causes
The number of control channels allocated for the cell is insufficient to handle the paging traffic.
68P02901W26-S 12-11
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
12-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. CELL: Channel request from MS blocked - PM
Description
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, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• An SDCCH has not been designated as the destination SDCCH for a handover due to call
traffic congestion.
68P02901W26-S 12-13
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
12-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. CELL: Last NS-VC failed
Description
This alarm is not reported if the associated Gb Link (GBL) between the BSS and the Serving
GPRS Support Node (SGSN) has failed.
The GSM Cell Identifier is displayed in the alarm output in the Additional information field.
Possible causes
68P02901W26-S 12-15
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
1 Initiate fault isolation and resolution procedures for the frame network
connections.
2 Clear the alarm after resolving the fault.
12-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. CELL: Classmark update from MS protocol error - PM
Description
This statistic counts the number of classmark updates from the MS containing protocol errors.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
68P02901W26-S 12-17
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Determine if there are any currently active hardware alarms. Perform the following procedure
to resolve the alarm:
12-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. CELL: No cell (BVC) block acknowledgment from the SGSN
Description
The PCU has repeated the Cell BSSGP Virtual Connection (BVC) Block message the maximum
number of times without receiving an acknowledgment from the Serving GPRS Support Node
(SGSN).
The GSM Cell Identifier is displayed in the alarm output in the Additional information field.
Possible causes
Procedure
68P02901W26-S 12-19
Nov 2007
6. CELL: Cipher mode Command from MSC failed - PM Chapter 12: CELL Alarms
Description
This statistic uses a timer, in order to detect, when an MS has failed to respond properly to a
cipher mode command message from the BSS within the required period of time. This statistic
is incremented each time the internal Motorola-defined timer in the BSS has expired.
For further information, refer to the Cell statistics chapter in the Maintenance Information:
GSM Statistics Application (68P02901W56) manual.
Possible causes
The MS did not switch correctly into encrypted communication mode when instructed.
Procedure
12-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. CELL: GPRS and baseband hopping conguration failure
Description
The baseband hopping configuration has failed as the GPRS is enabled and some of the
transceiver units in the cell do not support GPRS data.
The GSM cell identifier and a list of the DRIs that do not support GPRS data is displayed in the
Additional information field. The format is shown in the following example.
Possible causes
Baseband hopping is enabled and all of the transceiver units in the cell do not support GPRS
data.
68P02901W26-S 12-21
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Procedure 12-11 and Procedure 12-12 explain the steps to resolve this alarm.
Send a field representative to the site to replace all the transceiver units
that do not support GPRS with the transceiver units that do support GPRS.
12-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. CELL: GPRS unavailable - No PRP available
Description
GPRS is unavailable in this cell, as there is no available PRP. The alarm is cleared if the alarm
condition is resolved or if GPRS is disabled for the cell.
Possible causes
It is possible that the current In Service PRPs cannot support all the equipped cells due to
overload of the configured timeslots.
Procedure
68P02901W26-S 12-23
Nov 2007
9. CELL: GPRS unavailable - No GDS available Chapter 12: CELL Alarms
Description
GPRS is unavailable in this cell, as no GDS is available. The alarm is cleared if the alarm
condition is resolved or if GPRS is disabled for the cell.
Possible causes
It is possible that the current In Service GDSs cannot support all the equipped cells due to
overload of the configured timeslots.
Procedure
12-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. CELL: Intra-cell handover failed and recovered - PM
Description
This statistic counts the number of times the channel assignment failure messages the BSS
receives, when an intra-cell handover has failed and the origination cell recovers the call.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The wait period set for the MS to move from the origination cell to the destination cell in
a handover is too short.
Procedure
Determine if the cell parameters are correct and perform the following procedure:
68P02901W26-S 12-25
Nov 2007
Procedure Chapter 12: CELL Alarms
12-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10.
CELL: GPRS unavailable - No cell (BVC) reset ack from the SGSN
Description
GPRS is unavailable in this cell, as there was a failure to reset point-to-point BVC with SGSN.
The alarm is cleared if the alarm condition is resolved or if GPRS is disabled for the cell.
Possible causes
There is no ACK from the SGSN. This error indicates Frame Relay or SGSN problems.
Procedure
Procedure 12-16 GPRS unavailable - No cell (BVC) reset ack from the SGSN
68P02901W26-S 12-27
Nov 2007
10. CELL: Intra-cell handover failed and mobile lost - PM Chapter 12: CELL Alarms
Description
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, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The MS did not respond to the assignment command from the BSS before the expiration of the
intra-cell handover timer.
12-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if there are any currently active DRI alarms. Follow the steps as described in
Procedure 12-17:
68P02901W26-S 12-29
Nov 2007
11. CELL: GPRS unavailable - No cell (BVC) unblock ack from the SGSN Chapter 12: CELL Alarms
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.
Possible causes
No ACK from the SGSN. This error indicates Frame Relay or SGSN problems.
Procedure
Procedure 12-18 GPRS unavailable - No cell (BVC) unblock ack from the SGSN
12-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. CELL: Intra-BSS handover primary target cell blocked - PM
Description
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, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The SDCCH and/or TCH capacity for the cell is not large enough to handle the call volume.
Procedure
Determine if the number of SDCCH and/or TCH channels for the cell is correct. Perform the
following procedure as described in Procedure 12-19:
68P02901W26-S 12-31
Nov 2007
12. CELL: GPRS unavailable - No PDCHs available Chapter 12: CELL Alarms
Description
GPRS is unavailable since all the PDCHs in the cell are out of service and/or the PDCHs are
out of sync.
None.
Possible causes
Procedure
12-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. CELL: GPRS unavailable - No GPRS capable carriers available
Description
GPRS is unavailable in this cell, as there was no available GPRS capable carriers. The alarm is
cleared if the alarm condition is resolved or if GPRS is disabled for the cell.
Possible causes
• GPRS BCCH carrier use is restricted and the BCCH is the only GPRS capable carrier
remaining in the cell.
Procedure
1 Investigate why GPRS is no longer available in the cell and take appropriate
corrective action.
2 Reset BCCH to be a GPRS carrier.
68P02901W26-S 12-33
Nov 2007
13. CELL: Intra-BSS handover failed and recovered to org channel - PM Chapter 12: CELL Alarms
Description
This statistic counts the number of channel assignment failure messages that the BSS receives,
when an intra-BSS handover has failed and the origination cell recovers the call.
When an attempt to allocate a channel intended for an intra-BSS handover has failed, the MS
sends the BSS an assignment failure message, for a requested channel assignment.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The wait period set for the MS to move from the origination cell to the destination cell in
a handover is too short.
12-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the neighbor cell list to verify that the originating cell
contains valid data.
If the neighbor cell list is... Then...
correct Go to step 2.
not correct Correct the originating cell data
as required and then go to step 2.
2 Determine if the length of time specified for the wait period timer
is correct.
If the length of time... Then...
is correct Clear the alarm.
is not correct Change the parameters as
required and then clear the alarm.
68P02901W26-S 12-35
Nov 2007
14. CELL: Intra-BSS handover failed and mobile lost - PM Chapter 12: CELL Alarms
Description
This statistic counts the number of channel assignment failure messages that the BSS receives,
when an intra-BSS handover has failed, but the origination cell does not recover the call.
When an attempt to allocate a channel intended for an intra-BSS handover has failed, the MS
sends the BSS an assignment failure message, for a requested channel assignment.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The wait period set for the MS to move from the origination cell to the destination cell in
a handover is too short.
12-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the neighbor cell list to verify that the originating cell
contains valid data.
If the neighbor cell list is... Then...
correct Go to step 2.
not correct Correct the originating cell data
as required and then go to step 2.
2 Determine if the length of time specified for the wait period timer
is correct.
If the length of time... Then...
is correct Clear the alarm.
is not correct Change the parameters as
required and then clear the alarm.
68P02901W26-S 12-37
Nov 2007
14. CELL: GPRS unavailable - PBCCH timeslot out of sync Chapter 12: CELL Alarms
Description
GPRS is unavailable in this cell, because the Packet Broadcast Control Channel (PBCCH)
timeslot is out of synchronization.
Possible causes
Procedure
12-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. CELL: EGPRS unavailable - No EGPRS carriers available
Description
EGPRS is unavailable in this cell because there are no EGPRS capable carriers.
Possible causes
Procedure
68P02901W26-S 12-39
Nov 2007
15. CELL: Inter-BSS handover, MS handover failed message received PM Chapter 12: CELL Alarms
Description
This statistic counts the number of times MS handover failure messages the BSS receives
during an inter-BSS handover.
This alarm does not imply that a call is lost, as the BSS that attempted to handover the call
recovers it.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The wait period set for the MS, to move from the origination cell to the destination cell in
a handover, is too short.
12-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 12-41
Nov 2007
16. CELL: EGPRS unavailable - Insufcient GDS available Chapter 12: CELL Alarms
Description
The cell has no EGPRS service due to lack of available GDS resources.
This alarm is cleared for the following conditions such as last TRAU GDS OOS, last PRP OOS,
last GBL OOS, last GSL OOS, Cell OOS, when the BTS loses contact with the BSC, and so on.
Possible causes
Procedure
12-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 17. CELL: GPRS unavailable
Description
Try to find out the root cause of the problem as the recovery action for this alarm. If no other
GPRS Unavailable alarm (For example, No PRP available) is active, GPRS is toggled to attempt
to bring the GPRS back into service. The alarm clears if the GPRS then becomes available.
Additional information
Possible causes
GPRS is not available due to a software problem. The problem is not one of the following:
• No PRP available.
• No GDS available.
• No PDCHs available.
68P02901W26-S 12-43
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Send a field representative to the site to perform the fault diagnosis. Take
appropriate action and resolve the alarm.
12-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 18.
CELL: Handover failure to the MSC due to all possible errors except no channels - PM
Description
This statistic counts the number of times handover request failure messages the BSS sends to
the MSC, for causes other than the causes due to non-availability of channel resources.
These handover failure messages were sent to notify the MSC that the BSS could not reserve
the radio resource requested by the MSC.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The wait period (time) set for the MS to move from the origination cell to the destination
cell in a handover is too short.
68P02901W26-S 12-45
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Procedure 12-29 Handover failure to the MSC due to all possible errors except
no channels - PM
12-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 18. CELL: EGPRS unavailable
Description
The EGPRS service is unavailable. The recovery action for this alarm involves finding out the
root cause of the problem. The alarm clears if EGPRS becomes available.
Additional information
Possible causes
A software problem has caused EGPRS to be unavailable. The problem however is not one
of the following:
Procedure
Download the SWFM logs from all of the BTS, LCF, and PCU processors
to aid root cause analysis.
68P02901W26-S 12-47
Nov 2007
19. CELL: EGPRS unavailable - No 64 K PDCHs available Chapter 12: CELL Alarms
Description
EGPRS service is unavailable since all the 64 K PDCHs in the cell are out of service and/or
the 64 K PDCHs are out of synchronization.
Additional information
Possible causes
Procedure
Check the reason why 64 K PDCHs are unavailable and take necessary
action.
12-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 19. CELL: Bad handover reference numbers from the MS - PM
Description
This statistic counts the number of times that an MS has accessed a channel with a Handover
Reference Number which the BSS was not expecting.
When this alarm condition occurs, the Handover Reference Number field shows a non formatted
random number. The BSS compares only what it received with what it expected. The BSS can
make up to four comparisons for each logical handover detected for the Stand-alone Dedicated
Control Channel (SDCCH) processed at the BSS.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
68P02901W26-S 12-49
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Determine if there are any currently active hardware alarms. Resolve the alarm as follows:
12-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. CELL: Number of calls queued - PM
Description
This statistic counts the total number of calls queued for each cell on the BSS. Calls queued
count the channel assignment requests, but not the handovers. When this alarm occurs, one or
more cells are being overused or do not have the capacity for the area they cover.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The parameters that establish the rate for paging requests is not set appropriately for the
paging traffic that the BSS currently receives.
• If TCH traffic is heavy, the Paging Channels (PCHs) have overloaded the paging queues.
Procedure
68P02901W26-S 12-51
Nov 2007
Procedure Chapter 12: CELL Alarms
12-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. CELL:
Mobile assign command to MS blocked (No channel available) - PM
Description
This statistic counts the number of times the MSC requests, that the BSS should allocate radio
resources to an MS, has been refused.
When this alarm occurs, the request for a channel is not placed in queue at the BSS. And, the
assignment to a TCH is refused in the cell, because no radio resources are available in the BSS
for allocation.
When a channel request from the MSC is refused, an immediate channel assignment failure
message is sent to the MSC with the cause that no radio resource is available.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
68P02901W26-S 12-53
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
Determine if the number of SDCCH and/or TCH channels for the cell is correct. Resolve the
alarm as follows:
12-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. CELL: Mobile assignment failure from MS - PM
Description
This statistic counts the number of times an MS has been refused channel assignment to a
TCH. This error occurs when the MS detects a lower software layer failure on the TCHs being
assigned before the Assignment Complete message is sent.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• A software failure on a lower layer during an intra-cell handover up has disrupted the
channel assignment.
68P02901W26-S 12-55
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
12-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. CELL: PCH queue page discard - PM
Description
The number of paging requests from the MSC has reached the maximum number of pages
permitted in the GSM Paging Channel (PCH) queue. This error occurs when the MSC sends the
paging requests faster than the requests the BSS can process. The BSS discards any new pages
into the cell and reports the alarm.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• If Traffic Channel (TCH) traffic is heavy, the PCH has overloaded the paging queue.
68P02901W26-S 12-57
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
The procedure to resolve this alarm may involve one or both of the following actions at the MSC
and the BSS. The operator must determine which of the actions provides the best results.
1 Modify the location area boundaries at the MSC to reduce the paging
requests for a cell.
2 Clear the alarm.
12-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. CELL: Attempt at allocating a TCH failed - PM
Description
This statistic counts the number of unsuccessful allocations of a TCH within a cell for both call
origination and handover. Cases involving Immediate Assignment Reject are also included in
the count.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The timeslots related to the TCH has gone OOS causing the traffic to shift to another
in-service timeslot. This shift in traffic causes congestion on the timeslots. If the traffic is
heavy, the result is a delay in TCH allocation.
68P02901W26-S 12-59
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
12-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. CELL: TCH pre-emption failure - PM
Description
When this alarm occurs, calls with pre-emption capabilities cannot be established within the cell.
For further information, refer to the Cell statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Additional information
Possible causes
The cell is full of HIGHER priority calls or calls which are not vulnerable to pre-emption.
68P02901W26-S 12-61
Nov 2007
Procedure Chapter 12: CELL Alarms
Procedure
1 Re-evaluate the capacity of the affected CELL. This reduces the number of
pre-emption events within the cell and therefore result in a lower level of
pegging of this alarm and a reduced chance of the alarm being raised.
2 Re-evaluate the priority level/PCI/PVI capabilities of the call groups. If the
CELL experiences periods of overload of higher priority or pre-emption of
non-vulnerable calls, it is possible that this alarm is raised. This is due to
a particular network event or due to the priority level/PCI/PVI capabilities
of the call groups. If the network event is a regular occurrence, the alarm
threshold should be adjusted to account for this, if applicable. Alternatively,
re-evaluation of the priority level/PCI/PVI capabilities of the call groups
is required.
12-62 68P02901W26-S
Nov 2007
Chapter
13
COMB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details Combiner alarms and includes the following alarm procedures:
• 0 - 4. COMB: Cavity 0 - 4 tuning error on page 13-3.
68P02901W26-S 13-1
Nov 2007
Introduction to COMB alarms Chapter 13: COMB Alarms
COMB alarms
This chapter describes the alarm and OMC-R troubleshooting procedures for the Remotely
Tuned Combiner (RTC) device and the Transmit Antenna-Transceiver Interface (TATI) Combiner
device.
FRUs
A COMB device can be equipped on one of the FRUs shown in Table 13-1.
Table 13-1 FRUs that can be equipped with the COMB device
FRU Description
900 RTC 900 MHz five cavity, remotely tunable combiner, type RTC hardware.
900 CCB 900 MHz six cavity, remotely tunable combiner, type CCB hardware.
1800 CCB 1800 MHz six cavity, remotely tunable combiner, type CCB hardware.
1900 CCB 1900 MHz six cavity, remotely tunable combiner, type CCB hardware.
TC B0 CCB Control Board 0.
TC B1 CCB Control Board 1.
900 CCB0 900 MHz Cavity Combining Block 0.
1800 CCB0 1800 MHz Cavity Combining Block 0.
1900 CCB0 1900 MHz Cavity Combining Block 0.
900 CCB1 900 MHz Cavity Combining Block 1.
1800 CCB1 1800 MHz Cavity Combining Block 1.
1900 CCB1 1900 MHz Cavity Combining Block 1.
13-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0 - 4. COMB: Cavity 0 - 4 tuning error
Description
The contents of the Additional information field for this alarm are shown in Table 13-2.
Possible causes
68P02901W26-S 13-3
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiners. This delay allows sufficient time for the system to reset the DRI
and retune the combiner cavity.
13-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 13-5
Nov 2007
5. COMB: Link A sanity failure Chapter 13: COMB Alarms
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.
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.
Possible causes
13-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiners. This delay allows sufficient time for the system to reset the DRI
and retune the combiner cavity.
68P02901W26-S 13-7
Nov 2007
6. COMB: Link B sanity failure Chapter 13: COMB Alarms
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.
When this alarm is reported, the processor has failed and the standby combiner controller takes
over as the active combiner controller. If both links fail, the combiner and all the transceivers
connected to this RTC are placed OOS.
The contents of the Additional information field for this alarm are shown in Table 13-4.
Possible causes
13-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiners. This delay allows sufficient time for the system to reset the DRI
and retune the combiner cavity.
68P02901W26-S 13-9
Nov 2007
7. COMB: Power feed A failure Chapter 13: COMB Alarms
Description
A combiner has two power feeds. They are A (main) and B (redundant). The combiner continues
to operate as long as the redundant power feed is available.
System action
The contents of the Additional information field for this alarm are shown in Table 13-5.
13-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
If IAS alarms are present from the site, investigate the IAS alarms
before sending a field representative to the site.
68P02901W26-S 13-11
Nov 2007
8. COMB: Power feed B failure Chapter 13: COMB Alarms
Description
A combiner has two power feeds. They are A (main) and B (redundant). The combiner continues
to operate as long as the main power feed is available.
System action
The contents of the Additional information field for this alarm are shown in Table 13-6.
13-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
If IAS alarms are present from the site, investigate the IAS alarms
before sending a field representative to the site.
68P02901W26-S 13-13
Nov 2007
9. COMB: Full reset Chapter 13: COMB Alarms
Description
The combiner experienced a full reset. This alarm applies to both RTCs and TATI combiners.
The contents of the Additional information field for this alarm are shown in Table 13-7.
13-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The reset switches on the combiner were placed into the full reset position.
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiner. This delay allows sufficient time for the system to re-initialize the
combiner, reset the DRIs, and retune the combiner cavities.
Continued
68P02901W26-S 13-15
Nov 2007
Procedure Chapter 13: COMB Alarms
13-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. COMB: Partial reset
Description
The combiner has experienced a partial reset. This alarm applies to the RTC only.
The contents of the Additional information field for this alarm are shown in Table 13-8.
Possible causes
• The reset switches on the combiner were placed into a partial reset position.
68P02901W26-S 13-17
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
Wait for at least two minutes after the alarm is initially reported before continuing.
This delay allows time for the combiner to complete the partial reset.
13-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 13-19
Nov 2007
11. COMB: Cavity 5 tuning error Chapter 13: COMB Alarms
Description
The contents of the Additional information field for this alarm are shown in Table 13-9.
Possible causes
13-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Wait for at least 10 minutes after the alarm is initially reported to determine the state
of the combiners. This delay allows sufficient time for the system to reset the DRI
and retune the combiner cavity.
68P02901W26-S 13-21
Nov 2007
Procedure Chapter 13: COMB Alarms
13-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The contents of the Additional information field for this alarm are shown in Table 13-10.
Possible causes
68P02901W26-S 13-23
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
13-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. COMB: Cavity combining block 1 failure
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.
The contents of the Additional information field for this alarm are shown in Table 13-11.
Possible causes
68P02901W26-S 13-25
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
13-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 14. COMB: Processor A failure
Description
TATI Processor A failed due to a failure of TATI Control Board 0 (TCB 0).
The contents of the Additional information field for this alarm are shown in Table 13-12.
68P02901W26-S 13-27
Nov 2007
Possible causes Chapter 13: COMB Alarms
Possible causes
Procedure
13-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The contents of the Additional information field for this alarm are shown in Table 13-13.
68P02901W26-S 13-29
Nov 2007
Possible causes Chapter 13: COMB Alarms
Possible causes
Procedure
13-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. COMB: Device failure
Description
When the transmit antenna is congured with multiple combiners, the loss of one of
the combiners may cause a loss in output power for some frequencies.
Possible causes
68P02901W26-S 13-31
Nov 2007
Procedure Chapter 13: COMB Alarms
Procedure
13-32 68P02901W26-S
Nov 2007
Chapter
14
CSFP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details CSFP alarms and includes the following alarm procedures:
• 22. CSFP: SWFM indication on page 14-3.
• 48. CSFP: Memory location is corrupt. Replace GPROC board on page 14-8.
68P02901W26-S 14-1
Nov 2007
Introduction to CSFP alarms Chapter 14: CSFP Alarms
CSFP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Code Storage
Facility Processor (CSFP) device.
FRUs
A CSFP device can be equipped on one of the FRUs shown in Table 14-1.
Table 14-1 FRUs that can be equipped with the CSFP device
FRU Description
14-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. CSFP: SWFM indication
Description
The system has detected a software processing error (SWFM) for a CSFP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
Procedure
68P02901W26-S 14-3
Nov 2007
35. CSFP: LAN connection failure Chapter 14: CSFP Alarms
Description
The LAN connection between the master GPROC and any other equipped CSFP on the LAN
has failed.
System action
Possible causes
14-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 14-5
Nov 2007
47. CSFP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 14: CSFP Alarms
Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or {28337}
GPROC3/GPROC3–2 board.
CSFPs at the BSC can only be either GPROC2 or {28337} GPROC3/GPROC3–2. Everywhere
else in the system there can be any type of board.
Possible causes
• A GPROC board is installed and the gproc_slots database parameter is set to 32.
Procedure
14-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Send a field representative to the site to replace GPROC board with GPROC2
or {28337} GPROC3/GPROC3-2 board.
68P02901W26-S 14-7
Nov 2007
48. CSFP: Memory location is corrupt. Replace GPROC board Chapter 14: CSFP Alarms
Description
This alarm indicates a possible memory location fault. It is not an immediate problem as the
GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
is replaced at an appropriate time.
Possible causes
Procedure
14-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 49. CSFP: Code objects unavailable
Description
One (or more) devices have failed to load the code due to the code objects for this device not
being available.
All affected devices remain out of service at this site, resulting in a loss of capacity. This alarm
is tagged to the state transitions of DRIs failing to code load.
This alarm is generated for M-Cell6 and Horizon macro master cabinets.
This alarm indicates the likely cause of the fault; that is, missing card, presence of unsupported
or faulty card or objects missing from card.
Possible causes
• Removable flash media device was inserted into BTS after the code download.
The code objects are stored only on the removable flash media device on the
MCU/MCUF platforms.
68P02901W26-S 14-9
Nov 2007
Procedure Chapter 14: CSFP Alarms
Procedure
14-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. CSFP: EEPROM SW ash programming failure
Description
This error is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes
Procedure
If the board does not reset automatically, a manual reset can be performed
to reload the bootrom object.
68P02901W26-S 14-11
Nov 2007
51. CSFP: EEPROM HW ash programming failure Chapter 14: CSFP Alarms
Description
Possible causes
Procedure
14-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 initialize the MCU.
The PCMCIA card facilitates a quick, on site download. If the PCMCIA card is not inserted, the
software and firmware objects are downloaded from the BSC. This activity is a substantially
slower process.
Possible causes
The PCMCIA card was removed before the CSFP was locked.
Procedure
Determine if on site maintenance is in progress at the site reporting the alarm. Carry out
the following to resolve the alarm:
68P02901W26-S 14-13
Nov 2007
Procedure Chapter 14: CSFP Alarms
14-14 68P02901W26-S
Nov 2007
Chapter
15
DHP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DHP alarms and includes the following alarm procedures:
• 1. DHP: EEPROM flash failure - No valid bootstrap code object present on page 15-4.
• 23. DHP: SYNC lost phase lock to master GCLK on page 15-13.
• 24. DHP: Bad clock source or SYNC OCXO (oscillator) replacement required on page 15-15.
• 32. DHP: TDM interface failure - Assigned timeslot counter underflow on page 15-31.
• 33. DHP: TDM interface failure - Assigned timeslot counter overflow on page 15-33.
• 34. DHP: TDM interface failure - TDM parity error on page 15-35.
68P02901W26-S 15-1
Nov 2007
Procedure Chapter 15: DHP Alarms
• 48. DHP: Memory location is corrupt. Replace GPROC board on page 15-52.
15-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to DHP alarms
DHP alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Digital Radio
Host Processor (DHP) device.
FRUs
A DHP device can be equipped on one of the FRUs shown in Table 15-1.
Table 15-1 FRUs that can be equipped with the DHP device
FRU Description
GPROC InCell GPROC board.
GPROC2 InCell GPROC2 board.
GPROC3 InCell GPROC3 board.
MCU Micro Control Unit board.
MCUF Main Control Unit with dual FMUX.
MCUm M-Cell micro Main Control Unit board.
ARENAm (MCU) Horizon micro (M-Cell arena) Main Control
Unit.
ARENA MAC (MCU) Horizon compact (M-Cell arena Macro) Main
Control Unit.
HORIZON MIC2 (MCU) Horizon micro2 Main Control Unit.
HORIZONCOM2 (MCU) Horizon compact2 Main Control Unit.
Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS to
mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
68P02901W26-S 15-3
Nov 2007
1. DHP: EEPROM ash failure - No valid bootstrap code object present Chapter 15: DHP Alarms
Description
The Initialization Process (IP) has determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt. In this case, initialization is not permitted.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is programmed incorrectly with regard to the
GPROC EEPROM address space.
15-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 15-1 EEPROM ash failure - No valid bootstrap code object present
68P02901W26-S 15-5
Nov 2007
8. DHP: EEPROM ash object failure Chapter 15: DHP Alarms
Description
The size of the user start address in the header information of the bootstrap code object (Object
15) is incorrect. As a result, reprogramming is not initiated.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is programmed incorrectly with regard to the
GPROC EEPROM address space.
15-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 15-7
Nov 2007
17. DHP: EEPROM ash programming failure Chapter 15: DHP Alarms
Description
An attempt to erase bank 0 before reprogramming a flash EEPROM was unsuccessful. Bank 0
contains a byte that can be reprogrammed after a bank erase.
This fault condition is not a problem unless the GPROC is being reset, during which
the GPROC is rendered useless.
Possible causes
15-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 15-9
Nov 2007
21. DHP: EEPROM ash programming failure Chapter 15: DHP Alarms
Description
This fault condition is not a problem until the GPROC is reset, during which time
the GPROC is rendered useless.
Possible causes
Procedure
15-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 15-11
Nov 2007
22. DHP: SWFM indication Chapter 15: DHP Alarms
Description
The system has detected a software processing error (SWFM) for a DHP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
Procedure
15-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. DHP: SYNC lost phase lock to master GCLK
Description
The SYNC circuit in the MCU has lost phase lock to the reference master clock from the master
MCU.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-13
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
Determine if any link alarms have occurred at the same time when the phase lock was lost.
Perform the following procedure to resolve the alarm:
15-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. DHP:
Bad clock source or SYNC OCXO (oscillator) replacement required
Description
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
OCXO ageing
If this alarm was generated because of OCXO ageing, the OCXO is no longer able to produce a
valid system clock signal.
68P02901W26-S 15-15
Nov 2007
Possible causes Chapter 15: DHP Alarms
Possible causes
Procedure
Determine if any link alarm has occurred at the same time when the phase lock was lost. To
identify them perform this step.
Procedure 15-7 Bad clock source or SYNC OCXO (oscillator) replacement required
15-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. DHP: SYNC warm up failure
Description
The SYNC circuitry in the MCU did not warm up to the required operating temperature within
the specified warm-up time.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
Procedure
68P02901W26-S 15-17
Nov 2007
Procedure Chapter 15: DHP Alarms
15-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. DHP: SYNC calibration request
Description
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-19
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
Determine if the MCU is being powered up for the first time or was recalibrated during the
previous 24-hour period. Carry out the following to resolve the alarm:
15-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. DHP: SYNC shutdown request
Description
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-21
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. DHP: SYNC clock output failure
Description
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-23
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. DHP: SYNC watchdog timer expired
Description
The SYNC circuit generated a watchdog timer expiration. The MCU is reset.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-25
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
is cleared and does not recur The alarm condition no longer exists.
No further action is required.
is not cleared or recurs Send a field representative to the site
to replace the MCU.
15-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. DHP: Clock A signal loss
Description
The fault condition reported by this alarm may cause the site to go OOS.
System action
If the fault is in the CBUS, the CBUS is taken OOS. Otherwise, the DHP switches to the
redundant clock. If the redundant clock cannot be accessed, the active clock reference fails
and renders the site OOS.
Possible causes
68P02901W26-S 15-27
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. DHP: Clock B signal loss
Description
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 causes the site to go OOS.
Possible causes
Procedure
68P02901W26-S 15-29
Nov 2007
Procedure Chapter 15: DHP Alarms
15-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 32.
DHP: TDM interface failure - Assigned timeslot counter underow
Description
The DHP has determined that the TDM highway is underused. Fewer switch-bound timeslots
are driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes
• One or more MCAP data or address lines on the backplane are faulty.
68P02901W26-S 15-31
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 33.
DHP: TDM interface failure - Assigned timeslot counter overow
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
68P02901W26-S 15-33
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. DHP: TDM interface failure - TDM parity error
Description
Possible causes
• One or more signals of the TDM bus on the backplane has failed.
68P02901W26-S 15-35
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 35. DHP: LAN connection failure
Description
The LAN connection between the master GPROC and any other equipped DHP on the LAN
has failed.
System action
The system places the DHP OOS. If the DHP is the master GPROC, the site resets.
Possible causes
68P02901W26-S 15-37
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. DHP: Software failure
Description
System action
If there is only one processor in the site, the site resets. If there is a redundant processor,
control is handed over to the redundant processor.
The Additional information field includes process information that is useful only to the
programmers.
Possible causes
68P02901W26-S 15-39
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 40. DHP: Spurious interrupt
Description
The DHP has received and acknowledged an interrupt message but has not received a response
from the device generating the interrupt.
Possible causes
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or other
cause.
68P02901W26-S 15-41
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 43. DHP: SYNC not operational
Description
The SYNC circuit is still in the initializing state instead of the operational state after the
initialization timer has expired. The MCU is reset.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
68P02901W26-S 15-43
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 44. DHP: Firmware initiated SYNC calibration
Description
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
The calibration is performed on the MCU SYNC circuit. No call processing can occur on the
affected MCU during the calibration process.
Possible causes
Procedure
68P02901W26-S 15-45
Nov 2007
45. DHP: SYNC phase lock failure Chapter 15: DHP Alarms
Description
The SYNC circuit has not phase locked to the master within a specified period of being set
up in the slave mode.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
Possible causes
15-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if any link alarms occurred at the same time when phase lock was lost.
68P02901W26-S 15-47
Nov 2007
46. DHP: SYNC invalid mode Chapter 15: DHP Alarms
Description
The SYNC circuit has completed hardware/firmware initialization and the warm-up of the MCU
GCLK. However, the SYNC function is reporting that the MCU GCLK is in an invalid operational
mode. As a result, the MCU GCLK cannot continue normal operation.
This alarm is generated only for Horizon micro2 or Horizon compact2 sites.
An automatic MCU hard reset is continuously attempted to try to bring the MCU GCLK module
in service.
• The standby MCU GCLK is in the fast tune state when a standby device should never
reach that mode.
15-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 15-49
Nov 2007
47. DHP: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected Chapter 15: DHP Alarms
Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or {28337}
GPROC3/GPROC3–2 board.
If this error occurs in an InCell site, the GPROC board does not come into service. The maximum
number of timeslots a GPROC can use is 16. A GPROC2 or {28337} GPROC3/GPROC3–2 board
can use 8, 16 or 32 timeslots.
Possible causes
• A GPROC board is installed and the gproc_slots database parameter is set to 32.
If this error occurs in an InCell site, the GPROC board does not come into service.
15-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 15-51
Nov 2007
48. DHP: Memory location is corrupt. Replace GPROC board Chapter 15: DHP Alarms
Description
This alarm indicates a possible memory location fault. It is not an immediate problem as the
GPROC3 is still able to function correctly. However, it is recommended that the GPROC3
is replaced at an appropriate time.
Possible causes
Procedure
15-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. DHP: EEPROM SW ash programming failure
Description
This error is a generic flash programming error. A problem has occurred with the operating
software.
Possible causes
Procedure
If the board does not reset automatically, a manual reset can be performed
to reload the BOOTROM object.
68P02901W26-S 15-53
Nov 2007
51. DHP: EEPROM SW ash programming failure Chapter 15: DHP Alarms
Description
Possible causes
Procedure
15-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 231. DHP: TDM interface conguration failure
Description
System action
The system automatically resets the DHP. If the alarm recurs, the DHP is declared OOS.
Possible causes
• The GPROC device could not be programmed to the designated timeslot when swapping
the TDM highways.
68P02901W26-S 15-55
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. DHP: Processor bus communication failure
Description
A DHP board device has lost the ability to communicate to the peripheral boards through
the MCAP bus.
Possible causes
• The part of the GPROC that supports the MCAP bus access has failed.
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
1 Attempt to bring back the DHP In Service (INS). If the device is back in
service, the alarm condition no longer exists and further fault isolation is not
required .If the device remains OOS, go to step 2.
2 Replace the DHP board.
68P02901W26-S 15-57
Nov 2007
234. DHP: Active link connection failure Chapter 15: DHP Alarms
Description
The HDLC link connection has failed between the BTP on the master MCU and the DHP on
the slave MCU.
This alarm is generated only for Horizon micro2 and Horizon compact2 sites.
Possible causes
• HDLC disconnection.
15-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the Device Failure (DHP 254 or DRI 254) alarm was
received.
If this alarm is reported Then...
with...
a DRI 254 alarm Send a field representative to the
site to replace the transceiver unit.
a DHP 254 alarm Send a field representative to the
site to replace the MCU.
neither a DRI 254 alarm nor a Go to step 2.
DHP 254 alarm
2 Determine the state of the DRI.
If DRI is... Then...
busy-unlocked or Go to step 4.
enabled-unlocked
not busy-unlocked or Attempt to return the DRI to
enabled-unlocked service and then go to step 3.
3 Determine if the alarm is clear.
If the alarm is... Then...
clear 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.
not clear Go to step 4.
4 Determine the state of the DHP.
If DHP is... Then...
busy-unlocked or The fault condition no longer
enabled-unlocked exists. If this is a recurrence of this
alarm, send a field representative
to the site to replace the MCU.
not busy-unlocked or Attempt to return the DHP to
enabled-unlocked service and then go to step 5.
Continued
68P02901W26-S 15-59
Nov 2007
Procedure Chapter 15: DHP Alarms
15-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. DHP: Process safe test audit failure
Description
The DHP has failed a process safe test audit. The process safe test audit verifies the proper
operation of internal software processes.
The Additional information field includes 9 bytes containing process information, as shown in
Table 15-2. Bytes one through eight is useful only to the programmers. Byte nine is the error
code for the alarm.
Possible causes
68P02901W26-S 15-61
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
15-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. DHP: Device failure
Description
The DHP was rendered OOS by the GPROC Fault Management System, causing the site to reset.
A single byte is displayed in the Additional information field identifying the site reset type, as
shown in Table 15-3.
Value Denition
01 Hard reset.
02 Soft reset.
Possible causes
68P02901W26-S 15-63
Nov 2007
Procedure Chapter 15: DHP Alarms
Procedure
Wait approximately 10 minutes after this alarm is received to allow the site to reset,
before following this procedure.
15-64 68P02901W26-S
Nov 2007
Chapter
16
DPROC Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DPROC alarms and includes the following alarm procedures:
• 0. DPROC: Processor communication failure on page 16-3.
68P02901W26-S 16-1
Nov 2007
Introduction to DPROC alarms Chapter 16: 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
FRU Description
FORCE DPROC A Force™ DPROC processor board.
Unknown DPROC A generic DPROC processor board.
16-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. DPROC: Processor communication failure
Description
No communications are possible with the DPROC board at the Packet Control Unit (PCU) within
the General Packet Radio Service (GPRS) system.
System action
When this alarm is reported, the DPROC is placed OOS and all devices supported by DPROC
are also placed OOS.
Possible causes
68P02901W26-S 16-3
Nov 2007
Procedure Chapter 16: DPROC Alarms
Procedure
16-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. DPROC: DPROC reset detected
Description
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.
Value Description
00 Soft reset
02 Hard reset
Possible causes
68P02901W26-S 16-5
Nov 2007
Procedure Chapter 16: DPROC Alarms
Procedure
16-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. DPROC: SWFM indication
Description
The Additional information field includes process information useful only to the programmers.
Possible causes
Procedure
68P02901W26-S 16-7
Nov 2007
39. DPROC: Software failure Chapter 16: DPROC Alarms
Description
System action
{28351} The Additional information field includes the raw binary data of SWFM message
header and process information useful to the programmers. The Additional information field
length is 68.
Possible causes
Procedure
16-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88. DPROC: Max temperature exceeded
{28351}
Description
This alarm is raised when the temperature of the DPROC exceeds the maximum temperature
threshold.
Possible causes
Procedure
68P02901W26-S 16-9
Nov 2007
92. DPROC: High temperature exceeded Chapter 16: DPROC Alarms
{28351}
Denition
This alarm is generated when the temperature of the DPROC exceeds the high temperature
threshold.
Possible causes
• Airflow blockage.
Procedure
Procedure 16-6
16-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The Additional information field includes 9 bytes containing process information, as shown in
Table 16-3. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.
68P02901W26-S 16-11
Nov 2007
Possible causes Chapter 16: DPROC Alarms
Possible causes
Procedure
16-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 16-13
Nov 2007
Procedure Chapter 16: DPROC Alarms
16-14 68P02901W26-S
Nov 2007
Chapter
17
DRI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details DRI alarms and includes the following alarm procedures:
• 2. DRI: Internal message error - Pointer misalignment on page 17-10.
• 3. DRI: Internal message error - Dual-port RAM segment full on page 17-13.
• 15. DRI: Initial synchronization of radio and GPRS channel failed on page 17-30.
• 22. DRI: Radio subsystem software to DRI communication error on page 17-43.
• 23. DRI: Radio subsystem software to DRI communication failure on page 17-45.
• 24. DRI: TDM interface failure - TDM parity error on page 17-47.
• 25. DRI: TDM interface failure - Assigned timeslot counter overflow on page 17-49.
• 26. DRI: TDM interface failure - Assigned timeslot counter underflow on page 17-51.
68P02901W26-S 17-1
Nov 2007
Procedure Chapter 17: DRI Alarms
• 36. DRI: Front end processor to radio subsystem software communication failure on page
17-69.
• 38. DRI: BSS internal alarm only - FWFM displayed at EMON on page 17-72.
• 53. DRI: Channel coder 0 failure - Demodulation processor 0 failure on page 17-89.
• 54. DRI: Channel coder 0 Failure - Demodulation processor 1 failure on page 17-91.
• 55. DRI: Channel coder 1 failure - Demodulation processor 0 failure on page 17-93.
• 56. DRI: Channel coder 1 failure - Demodulation processor 1 failure on page 17-95.
• 65. DRI: Radio subsystem software to DRI communication error - Checksum error on
page 17-113.
17-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 67. DRI: Radio subsystem software to DRI communication error - DRI not responding on
page 17-119.
• 70. DRI: Equalizer control processor failure - Watchdog timer expired on page 17-121.
• 76. DRI: Radio subsystem software to DRI communication error on page 17-132.
• 91. DRI: Power amplifier power low but functioning on page 17-160.
• 92. DRI: Power amplifier temperature high but functioning on page 17-162.
68P02901W26-S 17-3
Nov 2007
Procedure Chapter 17: DRI Alarms
• 152. DRI: Control processor to power amplifier communication failure on page 17-217.
• 162. DRI: Receive matrix branch 2 control link failure on page 17-237.
17-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 203. DRI: RF unit power supply unit - Input failure on page 17-265.
• 221. DRI: Invalid in-call modification of destination channel type on page 17-291.
68P02901W26-S 17-5
Nov 2007
Procedure Chapter 17: DRI Alarms
17-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 contain the full GSM Cell ID (MCC, MNC, LAC, CI) when transmitting cell
information. The hardware devices detect alarm conditions and report them to the GPROC
application software. In the GPROC software, the alarm indications are collected, translated
and the alarm messages are then sent to the OMC-R and/or the local MMI.
The DRIM is a Motorola Cellular Advanced Processor (MCAP) bus peripheral board with the
primary responsibility of channel encoding and decoding data. This data is transmitted to and
received from a Mobile Station (MS).
The direct control of a DRIM is through the MCAP bus. Inbound and outbound data use the
higher bandwidth Time Division Multiplex (TDM) bus. Many clock signals and counters are used
to maintain the integrity of these two buses.
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.
The alarm reporting protocol adopted by the Channel Coding Digital Signal Processor (CCDSP)
is initially to report any error detected and to continue reporting that error every 6.12 s, until an
acknowledgment of the error is returned by the GPROC Fault Management (FM) software.
The duration between the reporting of CCDSP errors is one GSM superframe. However, the
reporting is not done on the actual superframe boundary. Once the error in question has been
acknowledged, the CCDSP does not report the error until explicitly instructed to do so by FM
software.
In any event, the TTY ports of all of the CCDSPs display a message when an error is detected;
the message states whether the error was reported. All CCDSP alarm reporting must pass
through the FEP.
68P02901W26-S 17-7
Nov 2007
FRUs Chapter 17: DRI Alarms
FRUs
For micro BTS installations, the FRU is the complete micro BTS unit.
A DRI device can be equipped on one of the FRUs shown in Table 17-1.
Table 17-1 FRUs that can be equipped with the DRI device
Continued
17-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R FRUs
Table 17-1 FRUs that can be equipped with the DRI device (Continued)
FRU BTS Description
HORIZONCOM2 (MRC) Horizon compact2 Micro Radio Control Unit in a
Horizon micro2.
HORIZONCOM2 (RFM) Horizon compact2 Radio Frequency Module in a
Horizon compact2.
HORIZONMIC2(RFM)
HORIZONMIC2(MRC)
HORIZONMIC2(SSN)
HORIZONCOM2(MRC)
68P02901W26-S 17-9
Nov 2007
2. DRI: Internal message error - Pointer misalignment Chapter 17: DRI Alarms
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.
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.
17-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• High call traffic causing DPRAM access rates to be different for the FEP and RSS.
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-11
Nov 2007
Procedure Chapter 17: DRI Alarms
17-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. DRI: Internal message error - Dual-port RAM segment full
Category: 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.
The contents of the Additional information field are shown in Table 17-3.
68P02901W26-S 17-13
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• A backlog in the DPRAM has occurred because the RSS software may have fallen behind
the FEP.
Procedure
1 Review the alarm logs to determine if other DRIs in the same cage
are also reporting this alarm.
If other DRIs are... Then...
reporting this alarm The site is overloaded. Analyze the
call traffic on the site. Go to step 2.
not reporting this alarm Go to step 3.
2 Wait until the traffic volume returns to normal levels.
If the alarm... Then...
recurs Go to step 3.
did not recur The fault condition no longer
exists.
3 Send a field representative to the site to replace the DRIM board (for
an InCell BTS) or the transceiver unit (for a non-InCell BTS).
17-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-15
Nov 2007
5. DRI: Superframe counter error (Uplink) Chapter 17: DRI Alarms
Description
The Channel Coding Digital Signal Processor (CCDSP) detected a mismatch in the uplink
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-4.
Possible causes
17-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS) and
goes disabled-unlocked) and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the site
busy-unlocked after to replace one of the following:
return to service
• DRIM board for an InCell BTS.
OR
• Transceiver unit for a non-InCell
the BSS takes the DRI BTS.
OOS again as a result of the
same alarm after the DRI
becomes busy-unlocked
68P02901W26-S 17-17
Nov 2007
6. DRI: Superframe counter error (Downlink) Chapter 17: DRI Alarms
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.
17-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS) and
goes disabled-unlocked) and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the site
busy-unlocked after to replace one of the following:
return to service
• DRIM board for an InCell BTS.
OR
• Transceiver unit for a non-InCell
the BSS takes the DRI BTS.
OOS again as a result of the
same alarm after the DRI
becomes busy-unlocked
68P02901W26-S 17-19
Nov 2007
Procedure Chapter 17: DRI Alarms
17-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
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-6.
68P02901W26-S 17-21
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• Site is overloaded.
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
17-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-23
Nov 2007
10. DRI: Dual-port RAM error Chapter 17: DRI Alarms
Description
The RSS has identified a message from the DPRAM that contained an invalid number of bytes or
an invalid checksum.
System action
Possible causes
17-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
there is a recurrence of this Send a field representative to the
alarm site to replace the DRIM board (for
an InCell BTS) or the transceiver
unit (for a non-InCell BTS).
the alarm does not recur The fault condition no longer
exists.
68P02901W26-S 17-25
Nov 2007
13. DRI: Channel coder internal message error Chapter 17: DRI Alarms
Description
A message with a valid checksum was received requesting a processing state change that is not
supported by the Channel Coding Digital Signal Processor (CCDSP).
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-7.
Possible causes
17-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-27
Nov 2007
14. DRI: Channel coder internal message error Chapter 17: DRI Alarms
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).
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-8.
Possible causes
17-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS) and
goes disabled-unlocked) and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the site
busy-unlocked after to replace one of the following:
return to service
• DRIM board for an InCell BTS.
OR
• Transceiver unit for a non-InCell
the BSS takes the DRI BTS.
OOS again as a result of the
same alarm after the DRI
becomes busy-unlocked
68P02901W26-S 17-29
Nov 2007
15. DRI: Initial synchronization of radio and GPRS channel failed Chapter 17: DRI Alarms
Description
The initial synchronization of the transceiver unit and a GPRS channel has failed.
All data for this alarm is in CTU2 format when reported by a CTU2.
The contents of the Additional information field are shown in Table 17-9.
Possible causes
17-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 17-31
Nov 2007
16. DRI: Channel coder internal message error Chapter 17: DRI Alarms
Description
An error in the byte count of a channel coder internal message between the RSS and DRI
was detected.
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-10.
Possible causes
• The message was corrupted between the RSS and the DRI.
17-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS) and
goes disabled-unlocked) and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the site
busy-unlocked after to replace one of the following:
return to service
• DRIM board for an InCell BTS.
OR
• Transceiver unit for a non-InCell
the BSS takes the DRI BTS.
OOS again as a result of the
same alarm after the DRI
becomes busy-unlocked
68P02901W26-S 17-33
Nov 2007
17. DRI: Channel coder internal message error Chapter 17: DRI Alarms
Description
The checksum of the host message was invalid and corrupted the host port.
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-11.
Possible causes
• The message was corrupted between the RSS and the DRI.
17-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-35
Nov 2007
18. DRI: Primary message or hardware interrupt error Chapter 17: DRI Alarms
Description
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.
If the DRI is operating in dual carrier mode, both DRIs are affected by the reset
and OOS actions.
17-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 17-37
Nov 2007
19. DRI: Channel coder internal message error Chapter 17: DRI Alarms
Description
A message has been received that is valid only for a deactivated subchannel, but the associated
subchannel is not currently de-activated.
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.
Possible causes
17-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-39
Nov 2007
20. DRI: Channel coder internal message error Chapter 17: DRI Alarms
Description
A message has been received that is valid only for an activated subchannel, but the associated
subchannel is not currently activated.
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.
Possible causes
17-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-41
Nov 2007
21. DRI: Calibration in progress Chapter 17: DRI Alarms
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.
The DRI transitions to enabled-unlocked (E-U). Subsequent alarms on the DRI are reported,
but not acted upon.
If the DRI is operating in Dual Carrier Mode, the associated DRI is shown. Firmware data is
also displayed which is of use only to firmware engineers: Source Fault Zone, Detector Fault
Zone, Fault Code, Additional data bytes 1-4, Timeslot, Carrier.
Possible causes
The site engineer has entered a command for the DRI firmware to enter calibration test mode.
• During calibration, MMI commands should be performed on the DRI only by the site
engineer.
• It is the responsibility of the site engineer to return the DRI INS when the calibration is
complete, which clears the alarm.
17-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. DRI: Radio subsystem software to DRI communication error
Description
An attempt to write to the host port was not successfully completed before reaching the
maximum retry count of 16.
The affected DRI is reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is reset on the first two occurrences and then placed OOS on the
third occurrence.
Possible causes
68P02901W26-S 17-43
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If.... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The affected DRI is reset when this alarm occurs. If this alarm occurs three times within a
10 minute period, the DRI is reset on the first two occurrences and then placed OOS on the
third occurrence.
Possible causes
68P02901W26-S 17-45
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. DRI: TDM interface failure - TDM parity error
Description
System action
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
• One or more of the signals of the TDM bus on the backplane has failed.
68P02901W26-S 17-47
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. DRI: TDM interface failure - Assigned timeslot counter overow
Description
A timeslot counter overflow occurred because more switch-bound timeslots were driven onto
the TDM bus than were allocated in the ATC register.
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
• One or more of the MCAP data or address lines on the backplane have failed.
68P02901W26-S 17-49
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26.
DRI: TDM interface failure - Assigned timeslot counter underow
Description
A timeslot counter underflow occurred because fewer switch-bound timeslots were driven onto
the TDM bus than were allocated in the ATC register.
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
• One or more of the MCAP data or address lines on the backplane have failed.
68P02901W26-S 17-51
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. DRI: Clock A signal loss
Description
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
68P02901W26-S 17-53
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 28. DRI: Clock B signal loss
Description
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
68P02901W26-S 17-55
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. DRI: Processor failure
Description
• 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.
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.
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
68P02901W26-S 17-57
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. DRI: Transceiver re-initialized unexpectedly
Description
Additional Information
Possible causes
68P02901W26-S 17-59
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to replace the transceiver unit.
17-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 31. DRI: Critical resource exhausted
Description
• The Shared Memory Unit is unable to find a free Data Buffer Descriptor.
The DRI undergoes a soft reset. If the alarm indication is received for a second time, the DRI is
hard reset and a DSP code load occurs. If a third indication is received within 10 minutes, the
DRI is OOS, resulting in a loss of capacity.
If the radio is operating in Dual Carrier Mode, the associated DRI simultaneously undergoes the
same reset-OOS procedure. DRI transactions are tagged to the initial alarm.
If the radio is operating in Dual Carrier Mode, the associate DRI is noted in the Additional
information field.
68P02901W26-S 17-61
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• More transactions were requested than the PCI driver can handle.
• An off-chip process is not consuming messages quickly enough to free Data Buffer
Descriptors or the Shared Memory Unit is lacking memory space.
Procedure
If... Then...
the alarm is restricted to one If the BSS takes the DRI OOS; INS
radio, then it is likely to be a the DRI and monitor it. If the DRI
hardware fault is take OOS again due to the same
alarm, replace the DRI.
this alarm is reported by other Reduce the call load and monitor
DRI devices, it is likely to be the DRIs again.
due to a software or firmware
problem
17-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 32. DRI: RF unit primary sync signal lost
Description
RF Unit in the Slave Mode has lost the primary synchronization signal from the fiber link. The
RF Unit will switch to sync off of the HDSL link when this alarm is generated.
Fault code.
Possible causes
RF Unit has lost the primary synchronization signal from the fiber link and started to sync off
of the HDSL link. Only sync slave RF Units report this alarm. Sync master RF Unit always
uses sync signal from the HDSL link.
Procedure
68P02901W26-S 17-63
Nov 2007
33. DRI: RF unit HDSL link quality error Chapter 17: DRI Alarms
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.
Possible causes
Procedure
17-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. DRI: RF unit reset
Description
Possible causes
68P02901W26-S 17-65
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 has occurred six times within a
10 minute period and the affected DRI was reset.
Some alarms must occur 12 times instead of six times to be classified as persistent
alarms.
If this alarm is raised on a CTU2 operating in dual carrier mode due to intermittent fault
reporting, both carriers are reset.
If a DRI is reset twice due to a specific persistent fault alarm, and the persistent fault alarm
occurs another six times within the following 10 minutes, the system places the affected DRI
OOS and reports the Device Failure alarm (DRI 254).
The DRI alarm code identifying the persistent fault alarm is displayed in the Additional
information field. Refer to the description of the specific alarm to resolve the fault condition.
68P02901W26-S 17-67
Nov 2007
Additional information eld Chapter 17: DRI Alarms
The contents of the Additional information field are shown in Table 17-14.
Possible causes
A persistent fault alarm affecting a specific DRI has occurred six times.
Procedure
1 Check the Additional information field to identify the alarm code that caused
the affected DRI to be reset.
2 Refer to the description of the DRI alarm code that caused the DRI to be
reset for the resolution procedure.
17-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 36. DRI: Front
end processor to radio subsystem software communication failure
Description
The Front End Processor (FEP) has not received the Superframe Synchronization Message for
the last five superframes. This failure can be a result of either a software or a link hardware
problem.
A 2 byte superframe count since the last sync message was received by the FEP is displayed
in the Additional information field.
Possible causes
• The physical link between the DRI and the RSS (MCAP) has failed.
Procedure
1 If the DRI is OOS, determine which alarm caused the DRI to go OOS.
2 Refer to the description of that alarm for the solution procedure.
68P02901W26-S 17-69
Nov 2007
37. DRI: Hard reset Chapter 17: DRI Alarms
Description
The DRI experienced a hard reset initiated by an operator or the DRI hardware.
2 bytes are displayed in the Additional information field containing internal software codes that
are useful only to the programmers.
Possible causes
17-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 17-71
Nov 2007
38. DRI: BSS internal alarm only - FWFM displayed at EMON Chapter 17: DRI Alarms
Description
This is not reported to the operator. It is an internal alarm reported at the EMON as a SWFM
or FWFM.
N/A
Possible causes
N/A
Procedure
N/A
17-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. DRI: Synchronization loss with MCU
Description
The active communications link between the transceiver unit and the MCU is no longer
synchronized.
This alarm is generated only for an M-Cell micro, M-Cell2, M-Cell6, Horizon micro,
Horizon micro2 and Horizon compact2 sites.
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-15.
68P02901W26-S 17-73
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
17-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-75
Nov 2007
40 - 47. DRI: Channel coder timeslot (0-7) failure Chapter 17: DRI Alarms
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.
Possible causes
• The code checksum routine, which is included as a part of the CCDSP initialization
process, failed.
17-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 17-77
Nov 2007
48. DRI: Baseband hopping timeslot counter mismatch Chapter 17: DRI Alarms
Description
The Front End Processor (FEP) Base Band Hopping (BBH) counter was not reset to zero on
the superframe boundary.
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-17.
Possible causes
17-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-79
Nov 2007
49. DRI: GSM timeslot counter mismatch Chapter 17: DRI Alarms
Description
The Front End Processor (FEP) DRI counter was not reset back to zero on the superframe
boundary.
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-18.
Possible causes
17-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-81
Nov 2007
50. DRI: Spurious GSM timeslot interrupt Chapter 17: DRI Alarms
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 causes
• The transceiver unit that generates the GSM timeslot interrupt is faulty.
17-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-83
Nov 2007
51. DRI: Baseband hopping TDM link error Chapter 17: DRI Alarms
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 causes
17-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-85
Nov 2007
52. DRI: Baseband hopping GSM timeslot misalignment Chapter 17: DRI Alarms
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.
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.
The contents of the Additional information field are shown in Table 17-19.
17-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Examples
• 00 74 ff ff ff ff
In this output, the ID of the detecting DRI is unknown (ff is displayed for unknown values
displayed in the Additional information fields).
Possible causes
• The TDM timeslot path connections are not correctly configured at the CCDSP.
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-87
Nov 2007
Procedure Chapter 17: DRI Alarms
17-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 53.
DRI: Channel coder 0 failure - Demodulation processor 0 failure
Description
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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 causes
68P02901W26-S 17-89
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 54.
DRI: Channel coder 0 Failure - Demodulation processor 1 failure
Description
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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 causes
68P02901W26-S 17-91
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 55.
DRI: Channel coder 1 failure - Demodulation processor 0 failure
Description
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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 causes
68P02901W26-S 17-93
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 56.
DRI: Channel coder 1 failure - Demodulation processor 1 failure
Description
The Channel Coder 1 has failed as a result of the failure of demodulation processor 1.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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 causes
68P02901W26-S 17-95
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 57. DRI: Transceiver to DRI communication error
Description
The Front End Processor (FEP) received a message from the transceiver unit that contains an
invalid header or message code for an uplink message destined for the RSS.
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.
Possible causes
68P02901W26-S 17-97
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-98 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 58. DRI: Transceiver to DRI communication error
Description
The Front End Processor (FEP) received a message from the transceiver unit that had a message
byte count greater than the maximum 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.
Possible causes
68P02901W26-S 17-99
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 59. DRI: Transceiver to DRI burst error
Description
The first message from the transceiver unit was not the equalized data message.
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.
Possible causes
68P02901W26-S 17-101
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 60. DRI: Transceiver to DRI burst error
Description
A second equalized data message from the transceiver unit was detected within the same
timeslot.
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.
Possible causes
68P02901W26-S 17-103
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-104 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 61. DRI: Transceiver to DRI communication error
Description
No data was sent to the Front End Processor (FEP). The FEP was expecting an equalized data
message.
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.
Possible causes
68P02901W26-S 17-105
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-106 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 62. DRI: Transceiver to DRI communication error
Description
The data sent to the Front End Processor (FEP) was incomplete. The FEP was expecting three
bytes.
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.
Possible causes
68P02901W26-S 17-107
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-108 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 63. DRI: Transceiver to DRI communication error
Description
The data sent to the Front End Processor (FEP) was incomplete. The FEP was expecting three
bytes.
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.
Possible causes
68P02901W26-S 17-109
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DRI goes disabled-unlocked) and continue to monitor the DRI.
and generates the DRI 35 alarm
the DRI fails to go Send a field representative to
busy-unlocked after the site to execute one of the
return to service following:
17-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 64. DRI: Non recoverable error
Description
The DRI is soft reset, hard reset, then taken OOS. If it is in dual carrier mode, both DRIs are
affected.
AAI data for this alarm is in CTU2 format when reported by a CTU2.
If the radio is operating in Dual Carrier Mode, the associate DRI is noted in the Additional
information field.
Possible causes
• Hardware failure.
68P02901W26-S 17-111
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 65. DRI: Radio
subsystem software to DRI communication error - Checksum error
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.
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-20.
68P02901W26-S 17-113
Nov 2007
Possible causes Chapter 17: DRI Alarms
If this alarm is raised on a CTU2 radio type, the additional data format is:
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-114 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-115
Nov 2007
66. DRI: Superframe counter error Chapter 17: DRI Alarms
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.
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-21.
17-116 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and and continue to monitor the DRI.
generates the DRI 254 alarm
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-117
Nov 2007
Procedure Chapter 17: DRI Alarms
• The following details, as displayed in the alarm information on the OMC screen:
Fault code (device identifier, alarm number, and alarm description), so that
the relevant troubleshooting procedure can be quickly accessed.
Site data. For example, site number, the state of the device, the cage
number and slot numbers.
17-118 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 17-119
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-120 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
68P02901W26-S 17-121
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-122 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 through the PCI bus.
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.
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.
If the radio is operating in Dual Carrier Mode, the associate DRI is noted in the Additional
information field.
68P02901W26-S 17-123
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
17-124 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 10 minute period, the DRI is OOS.
AAI data for this alarm is in CTU2 format when reported by a CTU2.
Possible causes
68P02901W26-S 17-125
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-126 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 73. DRI: High reverse power
Description
An excessive amount of reverse RF power is detected by the CTU2 radio. The purpose of
CTU2 reverse power detection alarm is to protect the CTU2 from physical damage due to an
excessive amount of reverse RF power. Therefore, the fault management software resets the
CTU2 immediately. If this alarm is repeated three times in 10 minutes, the software changes the
state of the radio to be inhibited.
If the radio is operating in Dual Carrier Mode, the associated DRI is noted in the Additional
information field.
Possible causes
• Loose or damaged connectors, such as the SMA on the CTU2 or DUP, and 7/16th
connectors.
• Faulty DUP.
68P02901W26-S 17-127
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
1 Check if the SMA cable between Radio and DUP is loose or damaged.
2 Check the antenna system.
3 Change the SMA cable. Ensure that the connection is not loose or damaged.
Then check if the alarm clears.
4 If the alarm cannot be cleared, check the Radio TX SMA connector, DUP TX
SMA connector, and DUP ANT connector.
5 If the alarm still cannot be cleared, change the DUP of affected DRI or swap
the DUP of affected radio with another DUP.
6 If the alarm still exists, replace the CTU2.
17-128 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 74. DRI: Cell transmit power unachievable
Description
A radio cannot be brought into service because it cannot achieve the cell transmit power level.
If the DRI is in Dual Carrier Mode, the associated DRI simultaneously undergoes the same fault
translation action. The alarm is tagged to the DRI state transitions.
All affected DRI devices remain out of service at this cell, resulting in a loss of capacity.
This field will display one of the following, according to the reason for failure:
• bts_txpwr_max_inner incorrect:
database value = x
required value = y
• max_tx_bts incorrect:
database value = x
required value = y
required value = y
required value = y
Where x and y are integers. The required value is the value that will enable the OOS DRI to
come INS.
68P02901W26-S 17-129
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• 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
17-130 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-131
Nov 2007
76. DRI: Radio subsystem software to DRI communication error Chapter 17: DRI Alarms
Description
The RSS detected the loss of uplink SACCH messages from the transceiver unit. If the uplink
SACCH messages are not detected by the RSS, in-progress calls are dropped.
System action
This alarm is not reported unless it occurs 10 times within a 24–hour period. If this alarm occurs
10 times within a 24–hour period, the DRI is hard reset.
A one byte code representing the DPRAM segment number is displayed in the Additional
information field in the output for this alarm.
17-132 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 17-133
Nov 2007
78. DRI: TX VSWR antenna fault Chapter 17: DRI Alarms
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.
Additional Information
Possible causes
Procedure
The duplexer can only detect VSWR problems when the radio is
transmitting above a certain power threshold. The range of values
are max_tx_bts between 0 and 6.
17-134 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 80. DRI: Transmitter synthesizer failure
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-135
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-136 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-137
Nov 2007
81. DRI: Transmitter synthesizer failure Chapter 17: DRI Alarms
Description
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 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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
17-138 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
• Carrier.
• Timeslot.
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-139
Nov 2007
Procedure Chapter 17: DRI Alarms
17-140 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 82. DRI: Transmitter synthesizer failure
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
68P02901W26-S 17-141
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-142 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 83. DRI: Transmitter synthesizer failure
Description
The output power of transmit synthesizer 2 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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
68P02901W26-S 17-143
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-144 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 84. DRI: Transmitter synthesizer failure
Description
The transmit synthesizer switch failed. The transmit synthesizer switch fails when both transmit
synthesizer 1 and transmit synthesizer 2 fail.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
68P02901W26-S 17-145
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-146 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 85. DRI: Transmitter failure - Output power
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
68P02901W26-S 17-147
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-148 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 86. DRI: Transmitter failure - Output power
Description
The output power of the transmit power amplifier is below the power range required to sustain
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-149
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-150 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 87. DRI: Transmitter failure - Output power
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
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers. Any additional bytes displayed should be ignored
If this alarm is raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-151
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-152 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88. DRI: Power amplier 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
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
68P02901W26-S 17-153
Nov 2007
Possible causes Chapter 17: DRI Alarms
If this alarm is raised on a CTU2 radio type, the additional data format is:
Possible causes
17-154 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-155
Nov 2007
89. DRI: Power amplier communication failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-156 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-157
Nov 2007
90. DRI: Transmitter failure - Output power Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-158 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-159
Nov 2007
91. DRI: Power amplier power low but functioning Chapter 17: DRI Alarms
Description
The output power of the transmit power amplifier is marginally below specified limits, but
calls may continue.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
Possible causes
17-160 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If the power level remains low for an extended period of time (24 hours),
consider replacing the transceiver unit during low traffic periods.
68P02901W26-S 17-161
Nov 2007
92. DRI: Power amplier temperature high but functioning Chapter 17: DRI Alarms
Description
The temperature of the transmit power amplifier is higher than the normal operating
temperature for the equipment. This fault condition is not considered critical because the power
amplifier temperature is not yet at a level that causes the power amplifier to cease functioning.
The power amplifier continues to function under this condition, but at reduced power to prevent
damage to the RF transistors. Reduced power is defined as the higher of the two following
values, such as -4 dB from the set point or the minimum power level for a power amplifier.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
17-162 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The RF element following the power amplifier in the transmit path power amplifier is faulty.
Procedure
If the temperature remains high for an extended period of time (24 hours),
consider replacing the transceiver unit during a low traffic period.
68P02901W26-S 17-163
Nov 2007
93. DRI: Transmitter failure - Output power Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-164 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-165
Nov 2007
104 - 111. DRI: Timeslot 0-7 conguration failure Chapter 17: DRI Alarms
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.
Possible causes
• RSS is faulty.
Procedure
1 Review the DRI device alarm message for the device failed alarm.
2 In a TTY window, enter the state command to check the operational
and administrative status of the DRI.
3 Send a field representative to the site to replace the DRI generating
the alarm.
17-166 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-167
Nov 2007
112. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers. Ignore any additional bytes displayed.
If this alarm is raised on a CTU2 radio type, the additional data format is:
17-168 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-169
Nov 2007
113. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers. Ignore any additional bytes displayed.
If this alarm is raised on a CTU2 radio type, the additional data format is:
17-170 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-171
Nov 2007
114. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-172 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-173
Nov 2007
115. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
The output power of receive synthesizer 1 is below the normal power range required for RF
signal reception.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-174 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-175
Nov 2007
116. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
The output power of receive synthesizer 2 is below the normal power range required for RF
signal reception.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-176 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-177
Nov 2007
117. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
The output power of receive synthesizer 3 is below the normal power range required for RF
signal reception.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-178 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-179
Nov 2007
118. DRI: Receiver synthesizer failure Chapter 17: DRI Alarms
Description
The receive synthesizer switch failed. The receive synthesizer switch fails when both receive
synthesizer 1 and receive synthesizer 2 fail.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-180 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-181
Nov 2007
119. DRI: Receiver failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The dc power current drain of the main intermediate frequency circuitry is out of the
required range.
17-182 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-183
Nov 2007
120. DRI: Receiver failure Chapter 17: DRI Alarms
Description
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The dc power current drain of the RSSI branch is out of the required range.
17-184 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-185
Nov 2007
121. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The receiver front-end failed. This failure causes a serious loss of antenna gain.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The dc power current drain of the front-end is out of the required range.
17-186 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-187
Nov 2007
122. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The Control Equalizer Board (CEB) interface to the I-Channel A/D converter is faulty.
17-188 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-189
Nov 2007
123. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently underflowed.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The Control Equalizer Board (CEB) interface to the Q-Channel A/D converter is faulty.
17-190 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-191
Nov 2007
124. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The receiver I-Channel Analog to Digital (A/D) power has consistently underflowed.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The Control Equalizer Board (CEB) interface to the Q-Channel A/D converter is faulty.
17-192 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-193
Nov 2007
125. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The receiver Q-Channel Analog to Digital (A/D) power has consistently overflowed.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The Control Equalizer Board (CEB) interface to the Q-Channel A/D converter is faulty.
17-194 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-195
Nov 2007
126. DRI: Receiver failure Chapter 17: DRI Alarms
Description
Receiver branch 1 failed. This failure causes a serious loss of receiver sensitivity.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-196 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-197
Nov 2007
127. DRI: Receiver failure Chapter 17: DRI Alarms
Description
Receiver branch 2 failed. This failure causes a serious loss of receiver sensitivity.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-198 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-199
Nov 2007
128. DRI: Receiver failure Chapter 17: DRI Alarms
Description
The Radio Frequency Module (RFM) receiver board at an M-Cell micro site failed.
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.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
17-200 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
68P02901W26-S 17-201
Nov 2007
144. DRI: Transceiver to DRI communication failure Chapter 17: DRI Alarms
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.
17-202 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
If this alarm is raised on a CTU2 radio type, the additional data format is:
Possible causes
68P02901W26-S 17-203
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-204 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 146. DRI: Transceiver to DRI communication failure
Description
The GSM timing is out of sync with the higher software layers.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-205
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-206 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 147. DRI: Transceiver to DRI communication failure
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-207
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-208 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 148. DRI: Transceiver to DRI communication failure
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• Faulty communications interface between the HDLC link and control processor.
68P02901W26-S 17-209
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-210 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 149. DRI: Transceiver to DRI communication failure
Description
The HDLC receive FIFO (First-In First-Out) to fiber links consistently overflows.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• Faulty communications interface between the HDLC link and control processor.
68P02901W26-S 17-211
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-212 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 150. DRI: Receive matrix failure
Description
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• 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.
68P02901W26-S 17-213
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
Send a field representative to the site to determine the cause of the alarm
to take appropriate action and resolve the alarm.
17-214 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 151. DRI: Transceiver to combiner communication failure
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• 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.
68P02901W26-S 17-215
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
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.
If... Then...
if both combiners are No further action is required.
busy-unlocked If this alarm recurs, it indicates an
intermittent fault.
both combiners are Send a field representative to the
disabled-unlocked or site to replace the combiners.
disabled-locked
one combiner is busy-unlocked Send a field representative to the
and the other combiner is site to check the combiner links.
enabled-unlocked Before this, make an attempt to
swap the redundant combiner.
17-216 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 152.
DRI: Control processor to power amplier communication failure
Description
The communications link between the Control Equalizer Board (CEB) and the power amplifier
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-217
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-218 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 153. DRI: Control processor to equalizer communication failure
Description
The communications link between the Control Equalizer Board (CEB) host processor and the
Equalizer Board (EQB) 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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-219
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-220 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 154. DRI: Power supply failure
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
If this alarm is raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-221
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• The external power source voltage is out of the acceptable range causing the power
supply to fail.
Procedure
Send a field representative to the site to determine the cause of the alarm and take appropriate
action.
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-222 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 155. DRI: Transceiver to DRI communication error
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-223
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-224 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 156. DRI: Control processor message queue overowed
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• Corrupted CEB software, DRI software, Fault Management (to BSS) software or faulty
CEB hardware.
68P02901W26-S 17-225
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-226 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 157. DRI: Receiver input overowed
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-227
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-228 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 158. DRI: Receiver input overowed
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-229
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-230 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 159. DRI: Equalizer output overowed
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-231
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-232 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 160. DRI: Equalizer output overowed
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-233
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-234 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 161. DRI: Transmitter out of synchronization
Description
The modulator interface lost synchronization with the transceiver unit timing chain.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• Failure of the recovered clock on the fiber link to the transceiver unit.
68P02901W26-S 17-235
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-236 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 162. DRI: Receive matrix branch 2 control link failure
Description
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
• 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.
68P02901W26-S 17-237
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
Send a field representative to the site to determine the cause of the alarm.
Take appropriate action and resolve the alarm.
17-238 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 163. DRI: Transceiver to DRI communication failure
Description
HDLC downlink communications between the higher level devices and the transceiver unit
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-239
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS Return the DRI to service (INS)
(DARE goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-240 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 164. DRI: Transceiver to DRI communication failure
Description
The Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL) is Out of Lock with the
E1 reference clock.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-241
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-242 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 165. DRI: Transceiver to DRI communication failure
Description
The output power from the Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL)
synthesizer is out of limits.
System action
For MCU-based sites, if this alarm occurs three times within a 10 minute period, the DRI is
placed OOS on the third occurrence.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-243
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-244 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 166. DRI: Control processor rmware failure
Description
The control processor in the MCU experienced a non recoverable software error.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
System action
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-245
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-246 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 167. DRI: Control processor conguration mismatch
Description
This alarm is generated only for an M-Cell micro, M-Cell macro, Horizon micro,
Horizon micro2 and Horizon compact2 sites.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-247
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-248 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 168. DRI: Equalizer conguration mismatch
Description
This alarm is generated only for M-Cell micro, MCell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
68P02901W26-S 17-249
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-250 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 169. DRI: Transceiver to DRI communication failure
Description
The Phase Lock Loop (PLL) synthesizer for the GSM timing chain is Out of Lock. Or, the output
power from the 13 MHz Phase Lock Loop (PLL) synthesizer for the GSM timing chain is out
of limits.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
68P02901W26-S 17-251
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-252 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 170. DRI: M-Cell micro interconnect failure
Description
The interconnection between the transceiver unit and the EEPROM on the control processor,
Power Distribution Board (PDB) or Transceiver Frequency Module (TRX) failed.
This alarm is generated only for an M-Cell micro, M-Cell macro, Horizon micro,
Horizon micro2 and Horizon compact2 sites.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
68P02901W26-S 17-253
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• Faulty PDB.
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-254 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 171. DRI: Invalid calibration data
Description
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2, Horizon macro and Horizon II macro sites.
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers. Ignore any additional bytes displayed.
If this alarm is raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-255
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-256 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 176. DRI: Equalizer timeslot (0-7) failure
Description
System action
Two bytes are displayed in the Additional information field containing internal software codes
that are only useful to the programmers.
Possible causes
68P02901W26-S 17-257
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-258 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 184. DRI: Equalizer rmware failure
Description
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon micro, Horizon
micro2 and Horizon compact2 sites.
System action
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.
A one-byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
68P02901W26-S 17-259
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-260 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 192. DRI: Baseband hopping TDM link error
Description
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.
If this alarm was raised on a CTU2 radio type, the additional data format is:
Byte1: BBH error
68P02901W26-S 17-261
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-262 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 193. DRI: Baseband hopping GSM timeslot misalignment
Description
The transceiver is unable to perform baseband hopping because the timeslot provided in the
baseband hopping data does not align with what the transceiver is expecting.
System action
The affected DRI is reset when this alarm occurs. If this alarm occurs three times, the DRI
is reset on the first two occurrences. If the alarm occurs within 20 minutes of the second
occurrence, the DRI is placed OOS.
Two bytes corresponding to the GSM timeslot number are displayed in the Additional
information field in the output for this alarm.
If this alarm was raised on a CTU2 radio type, the additional data format is:
68P02901W26-S 17-263
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
Review the event logs to determine the site where the transceiver unit causing the alarm is
located.
The actual transceiver unit at fault may not be the one that reported the alarm.
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-264 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 203. DRI: RF unit power supply unit - Input failure
Description
Main Power Supply to RF Unit has been lost and the RF Unit is operating on the backup power
supply.
Fault code.
Possible causes
• Connector or lead from the external AC/DC converter broken or removed from RF Unit
input.
Procedure
68P02901W26-S 17-265
Nov 2007
204. DRI: RF unit over temperature Chapter 17: DRI Alarms
Description
AC/DC converter within the RF Head Unit has detected an Over Temperature condition.
Fault code.
Possible causes
• Incorrect positioning of RF Unit above or unit too close to external heat source.
Procedure
17-266 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 205. DRI: RF unit low voltage disconnect imminent
Description
Battery backup voltage is nearing the point of initiating a disconnect of the load, that is the RF
Unit.
Fault code.
Possible causes
• Connector or lead from the external AC/DC converter broken or removed from RF Unit
input.
Procedure
68P02901W26-S 17-267
Nov 2007
206. DRI: RF unit external alarm input Chapter 17: DRI Alarms
Description
Fault code.
Possible causes
Procedure
17-268 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 207. DRI: Internal communication error
Description
The CTU2s cascaded integral combiner (CIC) has lost sync with the direct digital synthesizer
(DDS).
Fault code.
Possible causes
Procedure
68P02901W26-S 17-269
Nov 2007
208. DRI: Power amplier temperature Chapter 17: DRI Alarms
Description
The temperature of the power amplifier has exceeded its acceptable operating temperature
range.
Two bytes are displayed in the Additional information field containing internal software codes
that are useful only to the programmers.
Possible causes
• The cable or connectors between the power amplifier output and the next RF element in
the transmit path is disconnected or broken.
17-270 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Send a field representative to the site to determine the cause of the alarm.
Take appropriate action to resolve the alarm.
68P02901W26-S 17-271
Nov 2007
210. DRI: Hopping DRI failure Chapter 17: DRI Alarms
Description
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-272 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-273
Nov 2007
211. DRI: Front end processor failure Chapter 17: DRI Alarms
Description
This alarm indicates that a DRI Front End Processor (FEP) failed.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
17-274 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-275
Nov 2007
212. DRI: Channel coder failure Chapter 17: DRI Alarms
Description
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-276 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-277
Nov 2007
213. DRI: Transceiver processor failure Chapter 17: DRI Alarms
Description
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.
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers. Ignore any additional bytes displayed.
If this alarm is raised on a CTU2 radio type, the additional data format is:
For other platforms, the DRI alarm code related to the DRI CCDSP that triggered the
device state check in the system displays.
17-278 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-279
Nov 2007
214. DRI: Equalizer failure Chapter 17: DRI Alarms
Description
A one byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
17-280 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-281
Nov 2007
215. DRI: Power amplier failure Chapter 17: DRI Alarms
Description
A one-byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
17-282 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-283
Nov 2007
216. DRI: Transceiver recovery failure Chapter 17: DRI Alarms
Description
A one-byte error code is displayed in the Additional information field containing internal
software codes that are useful only to the programmers.
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-284 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-285
Nov 2007
217. DRI: Transmission suspended to conserve battery power Chapter 17: DRI Alarms
Description
The transceiver unit is not transmitting because the EAS has detected Main Power Failure (EAS
8) alarm was detected and the Battery Conservation feature is enabled.
The Additional information field displays the DRI device identifiers along with the EAS
opto-coupler number reporting the main power failure event.
Possible causes
Procedure
17-286 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
1 Send a field representative to the site to determine the cause of the alarm
and take appropriate action.
2 Once the main power supply is running, the DRIs should return to service.
3 If not, INS the DRI.
68P02901W26-S 17-287
Nov 2007
218. DRI: Invalid transceiver calibration data Chapter 17: DRI Alarms
Description
The antennas that are currently being used at a site cannot access any form of calibration data.
AAI data for this alarm is in CTU2 format when reported by a CTU2.
Possible causes
17-288 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Send a field representative to the site to calibrate the transceiver unit. This
problem cannot be resolved from the OMC-R.
68P02901W26-S 17-289
Nov 2007
219. DRI: GPRS not supported by radio Chapter 17: DRI Alarms
Description
The transceiver unit is not equipped to support General Packet Radio Service (GPRS) system,
but the radio function assigned to the transceiver unit requires GPRS support.
Possible causes
Procedure
1 Replace the radio which can not support GPRS, with a version that
can support GPRS.
2 Assign the GPRS function to the a radio that can support GPRS.
17-290 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 221. DRI: Invalid in-call modication of destination channel type
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.
Possible causes
68P02901W26-S 17-291
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-292 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 224. DRI: Safe test audit failure
Description
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.
68P02901W26-S 17-293
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
17-294 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-295
Nov 2007
231. DRI: TDM interface conguration failure Chapter 17: DRI Alarms
Description
During a TDM swap, the DRI cannot be placed on the correct TDM highway.
System action
If the alarm recurs when the board is reset for TBUS reconfiguration, the board is placed OOS.
Possible causes
17-296 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go Send a field representative to the
busy-unlocked after site to replace one of the following:
return to service
• DRIM board for an InCell
OR BTS.
68P02901W26-S 17-297
Nov 2007
234. DRI: Active link connection failure Chapter 17: DRI Alarms
Description
One or more of the following active link connections between the transceiver unit and the
BTP failed.
• A FOX-to-TCU connection (fiber link).
This alarm is generated for M-Cell2, M-Cell6, M-Cell micro, Horizon macro,
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.
17-298 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The portion of the transceiver unit and/or the active BTP board that supports the active
BTP link connection failed.
• A port on the active Fiber Optic Extender (FOX) board failed. This alarm does not occur if
the entire FOX board has failed.
• A port on the active Fiber Optic Multiplexer (FMUX) board failed. This alarm does not
occur if the entire FMUX board has failed.
• A port on the active XMUX board failed. This alarm does not occur if the entire XMUX
board has failed.
68P02901W26-S 17-299
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-300 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 (fiber link).
This alarm is generated for M-Cell2, M-Cell6, M-Cell micro, Horizon macro,
Horizon II macro extension equipment.
68P02901W26-S 17-301
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
• The portion of the transceiver unit and/or the active BTP board that supports the active
BTP link connection failed.
• A port on the active Fiber Optic Extender (FOX) board failed. This alarm does not occur if
the entire FOX board has failed.
• A port on the active Fiber Optic Multiplexer (FMUX) board failed. This alarm does not
occur if the entire FMUX board has failed.
Procedure
17-302 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 236. DRI: Slow ash 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-Cell micro, M-Cell macro, Horizon macro, Horizon
micro, Horizon micro2, Horizon compact and Horizon compact2 sites.
Possible causes
68P02901W26-S 17-303
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
17-304 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon macro, Horizon
micro, Horizon micro2, Horizon compact and Horizon compact2 sites.
Possible causes
68P02901W26-S 17-305
Nov 2007
Procedure Chapter 17: DRI Alarms
Procedure
If... Then...
the BSS takes the DRI OOS (DRI Return the DRI to service (INS)
goes disabled-unlocked) and monitor the DRI.
the DRI fails to go
busy-unlocked after
return to service
17-306 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 239. DRI: Process safe test audit failure
Description
The DRI failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes.
This alarm is generated only for M-Cell micro, M-Cell macro, Horizon macro, Horizon
micro, Horizon micro2, Horizon compact and Horizon compact2 sites.
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.
Continued
68P02901W26-S 17-307
Nov 2007
Possible causes Chapter 17: DRI Alarms
Possible causes
A process executing on the DRI failed to respond to the System Audit Process.
Procedure
Continued
17-308 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 17-309
Nov 2007
241. DRI: Standby link connected to wrong device Chapter 17: DRI Alarms
Description
One of the standby link connections in a BTS or extended cabinet is incorrect. This alarm is
generated for each incorrect standby link connection that is identified.
This alarm is generated for M-Cell2, M-Cell6, Horizon macro, Horizon II macro
extension equipment.
17-310 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The standby FMUX is connected to the wrong standby FMUX in another extended cabinet.
Procedure
• A standby FOX-to-TCU
connection.
• A standby MCU-to-TCU
connection.
Continued
68P02901W26-S 17-311
Nov 2007
Procedure Chapter 17: DRI Alarms
17-312 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Procedure
68P02901W26-S 17-313
Nov 2007
Procedure Chapter 17: DRI Alarms
17-314 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Procedure
1 If this alarm occurs three times within a 10 minute period, the DRI is soft
reset on the first two occurrences and then placed OOS on the third.
2 If the alarm is raised on a CTU2 operating in dual carrier mode due to
intermittent fault reporting, both carriers are taken OOS.
3 Send a field representative to replace the DRI generating the alarm.
68P02901W26-S 17-315
Nov 2007
Procedure Chapter 17: DRI Alarms
17-316 68P02901W26-S
Nov 2007
Chapter
18
EAS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details EAS alarms and includes the following alarm procedures:
68P02901W26-S 18-1
Nov 2007
Introduction to EAS alarms Chapter 18: 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.
All other IAS and EAS alarms in the active list (execute disp_act <site #>
command) are not dependable.
The individual requirements for EAS alarms are determined relative to the specific environment
of the BSS site which is external to the cabinets. Cabinet alarms are typically classified under
Internal Alarm System (IAS) alarms. Some of the examples of EAS alarm strings are Door open,
High humidity, Low humidity, Fire and Intruder.
18-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. EAS: Unexpected board type
Description
A Parallel Interface Extender (PIX) board is not responding properly when polled by the FM
software. This alarm indicates that during the current polling of the EAS by the FM software,
the response from the PIX board was inappropriate.
System action
Possible causes
• The slot specified for a PIX board is occupied by a board other than a PIX board.
68P02901W26-S 18-3
Nov 2007
Procedure Chapter 18: EAS Alarms
Procedure
18-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 the EAS alarms.
System action
Possible causes
68P02901W26-S 18-5
Nov 2007
Procedure Chapter 18: EAS Alarms
Procedure
18-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. EAS: EAS has detected main power failure
Description
System action
If the battery conservation feature is enabled, the system limits the number of transceivers that
are left online to the user-specified value of the carriers_ins_pwr_fail database parameter.
Possible causes
68P02901W26-S 18-7
Nov 2007
Procedure Chapter 18: EAS Alarms
Procedure
18-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 16 - 31. EAS: Optocoupler 1-16
Description
The system detected a change in state of an EAS optocoupler sensor. Optocoupler sensors are
used to report user-defined environmental conditions at a site.
For commands and parameters related to EAS alarm configuration, refer to Technical
Description: BSS Command Reference (68P02901W23).
The BSS suppresses EAS alarms 28, 29, 30 and 31 where the cabinet type is Horizon II mini or
Horizon II mini extension.
Additional information
An alphanumeric text string containing the user-specified EAS alarm text and the alarm index
number.
In the example, Low Humidity is the user-specified environmental condition and 6 is the alarm
index number identifying the specific optocoupler that changed states. The index number
follows the alarm string name and is enclosed in parentheses.
68P02901W26-S 18-9
Nov 2007
Possible causes Chapter 18: EAS Alarms
Possible causes
• A PIX card may have failed causing an environmental sensor to undergo a state change.
Procedure
18-10 68P02901W26-S
Nov 2007
Chapter
19
ETH Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details ETH alarms and includes the following alarm procedures:
68P02901W26-S 19-1
Nov 2007
0. ETH: Ethernet Link Disconnected Chapter 19: ETH Alarms
{26740/28351}
Category: Communication
Description
This alarm indicates that an Ethernet link disconnection on the PSI or DPROC (PXP) is occurred.
Possible causes
19-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If..... Then...
the available ETHs connecting wait for at least ten minutes before
to the same PCU/BSC are OOS taking any action as PCU/BSC may
be reset.
the alarm does not clear after check the status of the
PCU/BSC is back in-service corresponding PSI/DPROC
for this ETH.
the PSI/DPROC is OOS get it in-serviced by performing an
INS command on that device.
PSI/DPROC is INS and the change the Ethernet cable.
alarm does not clear
68P02901W26-S 19-3
Nov 2007
1. ETH: Excessive PSI_TRAU FILL FRAME TX Chapter 19: ETH Alarms
{26740}
Description
This alarm is only for the PSI to indicate the percentage of TRAU fill frames on PSI that exceeds
the threshold. This percentage will be on per ETH device basis. The database parameter
specifies the maximum allowable percentage of TRAU fill frames.
Additional data is of 1 byte: Byte 1: Value of PSI TRAU FILL FRAME TX.
Possible causes
The number of TRAU fill frames on PSI has exceeded the threshold.
Procedure
19-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. ETH: Excessive ETH RX ERRORS
{26740/28351}
Description
The alarm indicates the percentage of ETH receive errors that exceeds the threshold. It is per
ETH device basis on both the PSI and DPROC (PXP). The new database parameter specifies the
maximum allowable percentage of Ethernet frames received as error among all received frames.
Possible causes
The number of PSI/DPROC (PXP) receiving errors has exceeded the threshold.
Procedure
68P02901W26-S 19-5
Nov 2007
3. ETH: Excessive ETH TX ERRORS Chapter 19: ETH Alarms
{26740/28351}
Description
This alarm indicates the percentage of ETH transmit errors that exceeds the threshold. The
percentage is on a per ETH device basis on both the PSI and DPROC (PXP). The new database
parameter specifies the maximum percentage of Ethernet transmit errors among all transmitted
frames.
Possible causes
The number of PSI/DPROC (PXP) transmitting errors has exceeded the threshold.
Procedure
19-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. ETH: Unsupported Auto-Negotiated Signaling Rate
{26740/28351}
Description
This alarm gives an indication whether the Ethernet link on the PSI/DPROC (PXP) is attempting
to operate in a mode other than 1000BASE-T or 100BASE-TX (full duplex).
Possible causes
68P02901W26-S 19-7
Nov 2007
Procedure Chapter 19: ETH Alarms
Procedure
If..... Then...
the available ETHs connecting wait for at least 10 mins before
to the same PCU/BSC are OOS taking any action as PCU/BSC may
be resetting.
the alarm does not clear after check the status of the
PCU/BSC is back in-service corresponding PSI/DPROC
for this ETH.
the PSI/DPROC is OOS get it in-serviced by performing an
INS command on that device.
PSI/DPROC is INS and the change the Ethernet cable or
alarm does not clear check the equipment configuration
of the directly attached device.
19-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. ETH: DSW/DSWX Switching Hardware Required
{26740}
Category: Equipment
Description
This alarm is generated when the BSS SW at the BSC determines that the enhanced capacity
mode is not available during site initialization. The alarm is generated for OOS ETH due to
Enhanced Capacity Mode unavailable with the reason DSW/DSWX Required.
This alarm is not applicable when the total number of TDM highway timeslots
allocated to the highway (including PSI) is less than 1024 and the BSC has no
extension cage.
Possible causes
KSW and KSWX switching hardware remains enabled in the site or enhanced capacity mode
has not been enabled.
68P02901W26-S 19-9
Nov 2007
Procedure Chapter 19: ETH Alarms
Procedure
1 Replace all KSW and KSWX switching hardware with DSW and DSWX
switching hardware.
2 Ensure that the enhanced capacity mode is enabled.
19-10 68P02901W26-S
Nov 2007
Chapter
20
GBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GBL alarms and includes the following alarm procedures:
68P02901W26-S 20-1
Nov 2007
Introduction to GBL alarms Chapter 20: 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).
20-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 reconnect the link.
If this alarm generated for a GBL happens to be the last available link for service, the Last
GBL Link Failed (BSS 27) alarm is reported.
The MMS ID where the GBL is equipped is displayed. For example, the format is MMS 5 0 0.
Possible causes
• The physical media (For example, E1 links, satellite links, microwave links, trunking
equipment) is faulty.
68P02901W26-S 20-3
Nov 2007
Procedure Chapter 20: GBL Alarms
Procedure
20-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GBL: NSVC failure
Description
This alarm is reported when the first NSVC on a GBL fails. It can indicate that one or more
NSVCs have failed on this GBL.
The system will continue to attempt to bring the NSVCs into service.
Additional information
Possible causes
Procedure
1 Check connections and verify GBL timeslots match between PCU and
SGSN, correct NSVC parameters to match between PCU and SGSN sides
if not same.
2 Verify end-to-end frame relay parameters or connections.
68P02901W26-S 20-5
Nov 2007
Procedure Chapter 20: GBL Alarms
20-6 68P02901W26-S
Nov 2007
Chapter
21
GCLK Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GCLK alarms and includes the following alarm procedures:
• 11. GCLK: Long term average values are unstable on page 21-25.
• 24. GCLK: Bad clock source or OCXO (oscillator) replacement required on page 21-46.
68P02901W26-S 21-1
Nov 2007
Introduction to GCLK alarms Chapter 21: GCLK Alarms
GCLK alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Generic Clock
(GCLK) device, including GCLK Synchronization (SYNC) feature alarms.
FRUs
A GCLK device may be equipped on one of the FRUs shown in Table 21-1.
FRU Description
GCLK Generic Clock board.
MCU GCLK SYNC portion of an M-Cell Main Control Unit.
MCUF GCLK SYNC portion of an M-Cell micro Main Control
Unit.
MCUm GCLK SYNC portion of an M-Cell micro Main Control
Unit.
ARENAm (MCU) GCLK SYNC portion of an Horizon micro (M-Cell
arena) Main Control Unit.
ARENA MAC (MCU) GCLK SYNC portion of an Horizon compact (M-Cell
arena Macro) Main Control Unit.
Throughout this chapter, frequent reference is made to InCell and non-InCell (M-Cell)
BTSs. Assume InCell BTS to mean a BTS4, BTS5, BTS6, ExCell, or TopCell. A
non-InCell BTS refers to any BTS other than those defined by the term InCell BTS.
21-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. GCLK: Reference distribution module failure
Description
The Oven Controlled Crystal Oscillator (OCXO) on the GCLK board failed.
System action
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes
68P02901W26-S 21-3
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
21-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. GCLK: Clock reference failure
Description
System action
The system waits for the period specified in the wait_for_reselection database parameter to
determine if the MMS is in service. If the MMS is OOS after the wait period expires, the system
selects a new MMS for clock reference signal extraction if one is available.
If another MMS is not available for clock reference signal extraction, the GCLK is placed in the
set frequency mode.
The Additional information field displays MCAP register values and alarm source that are useful
only to programmers. The Additional information field also displays the identifiers for the MMS
device used for reference clock signal extraction, as shown in Table 21-2.
68P02901W26-S 21-5
Nov 2007
Possible causes Chapter 21: GCLK Alarms
Possible causes
Procedure
Continued
21-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 21-7
Nov 2007
3. GCLK: Hardware Fault Detected Chapter 21: GCLK Alarms
Description
This alarm indicates that the hardware has entered in an unrecoverable hardware state.
4 hex bytes of GCLK register values. The first byte contains the Interrupt Request Register
Value. The second byte contains the Status Register Value. The third byte contains Status H
Register value. The fourth byte contains Hardware Fault Register Value.
Possible causes
GCLK hardware has entered an invalid state within the hardware state machine design.
Procedure
Audit the GCLK device, if the alarm is still on, physically remove the board from the cage,
reinsert and INS the GCLK.
21-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. GCLK: Phase lock lost
Category: Equipment
Description
The Phase Lock Loop (PLL) circuit has lost phase lock to the incoming clock reference signal.
The frequency of this alarm is dependent on the quality of the E1 links. Normally, this alarm
does not affect traffic or signaling quality.
System action
The system attempts to lock on the existing MMS. If it cannot achieve lock, a new MMS is
selected as a reference source if one is available. The phase locking process is automatically
re-initiated for each MMS with a priority greater than zero.
If no more MMSs are available for clock reference signal extraction, the GCLK is placed in the
set frequency mode.
InCell site
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
68P02901W26-S 21-9
Nov 2007
Possible causes Chapter 21: GCLK Alarms
M-Cell site
The Additional information field displays the identifiers for the MMS device used for clock
reference signal extraction, as shown in Table 21-3.
Possible causes
• The GCLK OCXO has aged significantly and can no longer follow the source clock.
Procedure
Continued
21-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 21-11
Nov 2007
Procedure Chapter 21: GCLK Alarms
21-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. GCLK: 125 µs reference count overow
Description
The counter has been preloaded with an illegally low value during synchronization, causing a
delay of more than 125 µs between consecutive 125 µs reference pulses. This may cause 125 µs
reference failure reports on the other digital boards.
This alarm occurs as the result of a swap and then clears automatically.
System action
If this alarm is reported twice within 7 seconds, the GCLK is placed OOS.
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes
68P02901W26-S 21-13
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
21-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. GCLK: 60 ms reference count overow
Description
The counter has been preloaded with an illegally low value during synchronization, causing a
delay of more than 60 ms between consecutive 60 ms reference pulses. This may cause 60 ms
reference failure reports on the other digital boards.
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.
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes
68P02901W26-S 21-15
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
21-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. GCLK: 6.12 seconds reference count overow
Description
The counter preloaded with an illegally low value during synchronization, causing a delay of
more than 6.12 seconds between consecutive 6.12 seconds reference pulses. This may cause
6.12 seconds reference failure reports on the other digital boards.
This alarm occurs as the result of a swap and then clears automatically.
System action
If this alarm is reported twice within 7 seconds, the GCLK is placed OOS.
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes
68P02901W26-S 21-17
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
21-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. GCLK: Frequency difference in mate GCLK
Description
A difference greater than 0.655 Hz exists between the two equipped GCLKs.
MCAP
The Additional information field displays MCAP register values and alarm source that are
useful only to programmers.
Possible causes
68P02901W26-S 21-19
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
Continued
21-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 21-21
Nov 2007
9. GCLK: Hard reset Chapter 21: GCLK Alarms
Description
System action
Possible causes
21-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-23
Nov 2007
Procedure Chapter 21: GCLK Alarms
21-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. GCLK: Long term average values are unstable
Description
Of the values used to calculate the Long-Term-Average (LTA), 25% or more exceed the alarm
range specified by the lta_alarm_range database parameter.
Possible causes
• Poor E1 links.
68P02901W26-S 21-25
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
1 Check for the presence of other alarms that indicate a link fault.
2 Determine if other sites are reporting this alarm.
If other sites are... Then...
reporting this alarm The reference clock signal is faulty.
Resolve the reference clock signal
fault.
are not reporting this alarm Go to step 3.
3 Send a field representative to the site prepared to replace a faulty
link or GCLK:
21-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 12. GCLK: Unrecognized hardware revision level
Description
The GCLK board hardware revision level was unrecognized by the system.
• All GCLK Sync feature commands execute, but the GCLK is not placed in the closed loop
mode.
Possible causes
Procedure
68P02901W26-S 21-27
Nov 2007
14. GCLK: Phase lock failure Chapter 21: GCLK Alarms
Description
A GCLK has lost phase lock and repeated attempts to regain phase lock have failed.
InCell
Hardware timers on the GCLK board are used to determine the length of time for a GCLK
to achieve and maintain phase lock. The length of time for a specific GCLK is dependent on
the hardware revision of the GCLK board.
The GCLK must achieve phase lock within the period specified by the confirmation timer setting.
It must also maintain phase lock for the period specified by the timeout timer setting. The
relevant settings are shown in Table 21-4.
GCLK hardware revision level Conrmation timer setting Timeout timer setting
1 - 3 10 minutes 6 hours
5 - 9 2 minutes 1 hour
This alarm is generated if the GCLK does not achieve or maintain phase lock within the period
specified by the timer settings.
M-Cell
Hardware timers on the MCU are used to determine the length of time for a GCLK to maintain
phase lock.
InCell
21-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
M-Cell
The contents of the Additional information field for an M-Cell site are shown in Table 21-5.
Possible causes
68P02901W26-S 21-29
Nov 2007
Procedure Chapter 21: GCLK Alarms
Procedure
Continued
21-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 21-31
Nov 2007
15. GCLK: Watchdog timer expired Chapter 21: GCLK Alarms
Description
The Synchronization (SYNC) process on the MCU board watchdog timer unexpectedly expired.
System action
Possible causes
21-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-33
Nov 2007
16. GCLK: Clock output failure Chapter 21: GCLK Alarms
Description
The GCLK Synchronization (SYNC) hardware is not generating the 16.384 MHz clock signal
in the system.
System action
Possible causes
21-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-35
Nov 2007
17. GCLK: SYNC shutdown request Chapter 21: GCLK Alarms
Description
System action
Possible causes
21-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-37
Nov 2007
18. GCLK: Not operational Chapter 21: GCLK Alarms
Description
The MCU Synchronization (SYNC) function did not complete the required initialization that
prevents the GCLK from becoming operational.
System action
Possible causes
21-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-39
Nov 2007
19. GCLK: Warm up failure Chapter 21: GCLK Alarms
Description
The MCU Synchronization (SYNC) function completed the MCU GCLK initialization. But, the
SYNC function did not indicate that the warm up was completed so that it could begin normal
operation.
Fault Management (FM) expects that SYNC hardware takes less than 30 minutes to complete a
warm up.
An automatic MCU hard reset is continuously performed to try to bring the MCU GCLK module
in service.
Possible causes
• The operational SYNC firmware is corrupted. The boot portion of the firmware is probably
not corrupted.
21-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 21-41
Nov 2007
20. GCLK: Invalid mode Chapter 21: GCLK Alarms
Description
The MCU Synchronization (SYNC) function completed hardware or firmware initialization and
the warm up of the MCU GCLK. However, the SYNC function is reporting that the MCU GCLK
is in an invalid operational mode. As a result, the MCU GCLK may not be able to continue
normal operation.
An automatic MCU hard reset is continuously attempted to try to bring the MCU GCLK module
in service.
• The standby MCU GCLK is in the fast tune state when a standby device should never
reach that mode.
21-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 21-43
Nov 2007
21. GCLK: Calibration in progress Chapter 21: GCLK Alarms
Description
The OMC-R operator requested calibration of the GCLK Synchronization (SYNC) hardware.
The calibration is performed on the MCU SYNC circuit. No call processing can occur on the
affected MCU during the calibration process.
The MCU is reset after the GCLK SYNC calibration has been completed.
Possible causes
Procedure
21-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. GCLK: Firmware initiated calibration
Description
The calibration is performed on the MCU SYNC circuit. No call processing can occur on the
affected MCU during the calibration process.
Possible causes
Procedure
68P02901W26-S 21-45
Nov 2007
24. GCLK: Bad clock source or OCXO (oscillator) replacement required Chapter 21: GCLK Alarms
Description
The GCLK Synchronization (SYNC) firmware has detected that one of the following two possible
fault conditions has occurred:
• The GCLK SYNC Oven-Controlled Crystal Oscillator (OCXO) has reached a synchronization
limit which may adversely affect system performance.
OCXO ageing
If this alarm was generated because of OCXO ageing, the OCXO may no longer be able to
produce a valid system clock signal.
21-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Determine if any link alarms occurred at the same time that phase
lock was lost.
If a link alarm... Then...
occurred at the same time There is a link fault. Troubleshoot
the link fault.
did not occur at the same time Go to step 2.
2 Determine what type of site is reporting the alarm.
If the site is... Then...
an InCell site Go to step 3.
a MCU-based site Go to step 4.
3 Determine if the Long-Term-Average Values are Unstable (GCLK 11)
alarm was reported for the GCLK.
If the GCLK 11 alarm... Then...
was reported Send a field representative to the
site to recalibrate the GCLK.
was not reported Send a field representative to the
site to replace the GCLK.
4 Determine if the affected processor is the master processor.
If the affected processor... Then...
is the master processor Disable all of the DRI devices and
then go to step 5.
is not the master processor Go to step 5.
Continued
68P02901W26-S 21-47
Nov 2007
Procedure Chapter 21: GCLK Alarms
21-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 21-6
provides both the low and high calibration limits as required by the specific GCLK hardware
revision levels.
GCLK hardware revision level Low LTA calibration limit High LTA calibration limit
1 - 3 38h (=56 dec) E9h (=233 dec)
5 - 7 38h (=56 dec) E9h (=233 dec)
8 38h (=56 dec) E9h (=233 dec)
9 1Ah (=26 dec) E9h (=233 dec)
M-Cell
The MCU GCLK has been unable to calculate an LTA value during 24 hour period within the last
year. This alarm may also be generated for an MCU that is being powered up for the first time
and has not been calibrated; and therefore, is unable to have the LTA calculated.
68P02901W26-S 21-49
Nov 2007
Possible causes Chapter 21: GCLK Alarms
Possible causes
• 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
Continued
21-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 21-51
Nov 2007
232. GCLK: Processor bus communication failure Chapter 21: GCLK Alarms
Description
A GCLK board device has lost the ability to communicate to the GCLK through the MCAP bus.
The GCLK is placed OOS.
Possible causes
• The part of the GCLK that supports the MCAP bus access failed.
Procedure
21-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 21-53
Nov 2007
Procedure Chapter 21: GCLK Alarms
21-54 68P02901W26-S
Nov 2007
Chapter
22
GDS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GDS alarms and includes the following alarm procedures:
• 0. GDS: All channels Out of Sync on page 22-2.
68P02901W26-S 22-1
Nov 2007
0. GDS: All channels Out of Sync Chapter 22: GDS Alarms
Description
All packet data channels on this GDS are Out of Service (out of synchronization).
The system tries to recover from this alarm condition by resetting the MSI board carrying
this GDS.
Additional information
Possible causes
NIB has failed. A connection problem exists between PCU and radio at the BTS.
Procedure
22-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GDS: IP address mismatch
{26740}
Description
The GDS over the Ethernet is disabled for the IP address mismatch.
Additional information
The additional alarm codes include the mismatch IP address extracted from Alive ACK.
Variables are based on the size of the ASCII string (for example: 10.15.255.2).
Possible causes
The PSI’s IP address changes its PXP pair on PCU which, is not notified or miswired with PSI-PXP.
The PCU (PXP) receives unexpected BSC (PSI) Alive REQ message.
Procedure
The operator checks and modifies the IP address, or reconfigures the PCU to
BSC Ethernet connection.
68P02901W26-S 22-3
Nov 2007
2. GDS: Protocol failure Chapter 22: GDS Alarms
{26740}
Description
This alarm provides an indication that the GDS over Ethernet is OOS on the PSI/DPROC (PXP).
Additional information
Possible causes
• The Alive protocol on PSI/DPROC (PXP) fails because of an unexpected problem which
causes GDS is OOS.
22-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
If... Then...
the available GDSs connecting to the same wait for at least 10 mins before taking any
PCU/BSC are also OOS, action as PCU/BSC is resetting.
the alarm does not clear after PCU/BSC is check the status of the corresponding
back in-service PSI/DPROC(PXP) for this GDS.
the PSI/DPROC(PXP) is OOS get that in-service by performing an INS
command on the device.
the PSI/DPROC(PXP) is INSed and the check the status of the corresponding
alarm does not clear ETH for this GDS.
the ETH is OOS get it in service.
the ETH is INSed and the alarm does not check the status of the GDS on the peer
clear entity.
68P02901W26-S 22-5
Nov 2007
Procedure Chapter 22: GDS Alarms
22-6 68P02901W26-S
Nov 2007
Chapter
23
GPROC Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GCLK alarms and includes the following alarm procedures:
• 1. GPROC: EEPROM flash failure - No valid bootstrap code object present on page 23-4.
• 23. GPROC: SYNC lost phase lock to master GCLK on page 23-15.
• 24. GPROC: Bad clock source or SYNC OCXO(oscillator) replacement required on page
23-16.
• 32. GPROC: TDM interface failure - Assigned timeslot counter underflow on page 23-26.
• 33. GPROC: TDM interface failure - Assigned timeslot counter overflow on page 23-28.
• 34. GPROC: TDM interface failure - TDM parity error on page 23-30.
• 42. GPROC: Site reset occurred due to front panel reset on page 23-38.
68P02901W26-S 23-1
Nov 2007
Procedure Chapter 23: GPROC Alarms
• 48. GPROC: Memory location is corrupt. Replace GPROC board on page 23-45.
23-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Introduction to GPROC alarms
GPROC alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Generic
Processor (GPROC) device.
GPROC devices are grouped into one of two categories based on functionally:
• Hard device - the functionality of a hard GPROC device is predefined and static. These
devices include the Base Site Processor (BSP), Base Transceiver Processor (BTP), Digital
Host Processor (DHP) and Code Storage Facility Processor (CSFP). Each of these devices
is documented separately.
• Soft device - the functionality of a soft GPROC device is dynamically assigned as part of a
N+M redundancy scheme. In this scheme, M is the number of available soft devices in a
pool of devices. N is the number of hard devices whose function may be assumed by
one of the pooled devices.
For example, if a CSFP device fails and a pool GPROC device is available, the pooled device
assumes the CSFP functionality.
FRUs
A GPROC device may be equipped on one of the FRUs shown in Table 23-1.
FRU Description
GPROC InCell GPROC board
GPROC2 InCell GPROC2 board
GPROC3 InCell GPROC3 board
MCU Main Control Unit
MCUF Main Control Unit
MCUm Main Control Unit
ARENA (MCU) Main Control Unit
ARENA MAC (MCU) Main Control Unit
HORIZONMIC2 (MCU) Main Control Unit
HORIZONCOM2 (MCU) Main Control Unit
68P02901W26-S 23-3
Nov 2007
1. GPROC: EEPROM ash failure - No valid bootstrap code object present Chapter 23: GPROC Alarms
Description
The Initialization Process (IP) determined that the bootstrap code object (Object 15) in the
flash EEPROM does not exist or is corrupt.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
23-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 23-1 EEPROM ash failure - No valid bootstrap code object present
68P02901W26-S 23-5
Nov 2007
8. GPROC: EEPROM ash object failure Chapter 23: GPROC Alarms
Description
The size of the user start address in the header information of the bootstrap code object (Object
15) is incorrect. As a result, reprogramming is not initiated.
Possible causes
• The bootstrap code object (Object 15) was corrupted while downloading to the GPROC.
• The bootstrap code object (Object 15) is programmed incorrectly with regard to the
GPROC EEPROM address space.
23-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-7
Nov 2007
17. GPROC: EEPROM ash programming failure Chapter 23: GPROC Alarms
Description
An attempt to erase bank 0 before reprogramming a flash EEPROM was unsuccessful. Bank 0
contains a byte that can be reprogrammed after a bank erase.
This fault condition is not a problem unless the GPROC is being reset, at which time
the GPROC is rendered useless.
Possible causes
23-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-9
Nov 2007
19. GPROC: RSL links congestion Chapter 23: GPROC Alarms
Description
The flow of messages exceeds the transmissibility of RSL links. Links congestion was detected
on one or more RSLs on this GPROC.
Some paging messages may be discarded when this alarm is present. Hence, the
associated services are not provided. For example, some new calls may not be
established. Select retry or wait a while to avoid peak usage of the system.
Possible causes
Procedure
23-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. GPROC: LAPD controller failure
Description
Two bytes are displayed. Ignore the first byte; the second byte has a value of 1 or 2. The second
byte value descriptions are shown in Table 23-2.
Value Description
1 The LAPD controller has encountered a non recoverable internal fault.
2 The LAPD controller cannot open a new channel for RSL link.
Possible causes
• The micro code in the LAPD controller has encountered a fatal exception.
• The LAPD controller cannot open a new LAPD channel due to an internal error.
Procedure
68P02901W26-S 23-11
Nov 2007
21. GPROC: EEPROM ash programming failure Chapter 23: GPROC Alarms
Description
This fault condition is not a problem until the GPROC is reset, at which time the
GPROC is rendered useless.
Possible causes
{28337} The flash EEPROM device is faulty or the user has a GPROC3/ GPROC3-2 board.
Procedure
23-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 23-13
Nov 2007
22. GPROC: SWFM indication Chapter 23: GPROC Alarms
Description
The system has detected a software processing error (SWFM) for a GPROC.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Possible causes
Procedure
23-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. GPROC: SYNC lost phase lock to master GCLK
Description
This alarm indicates that having been in phase locked mode, the SYNC circuit has lost phase
lock to the master.
Possible causes
Procedure
68P02901W26-S 23-15
Nov 2007
24. GPROC: Bad clock source or SYNC OCXO(oscillator) replacement required Chapter 23: GPROC Alarms
Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by
replacing the FRU itself.
Possible causes
• SYNC malfunctioning.
Procedure
23-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. GPROC: SYNC warm up failure
Description
This alarm indicates that the SYNC circuit has not warmed up to the required operating
temperature within the specified warm-up time.
Possible causes
Procedure
68P02901W26-S 23-17
Nov 2007
26. GPROC: SYNC calibration request Chapter 23: GPROC Alarms
Description
Possible causes
• SYNC malfunctioning.
Procedure
Report that the SYNC circuit requires investigation (clocking usually drifts
with time).
23-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 27. GPROC: SYNC shutdown request
Description
This alarm indicates that the SYNC circuit has requested shutdown.
Possible causes
Procedure
68P02901W26-S 23-19
Nov 2007
28. GPROC: SYNC clock output failure Chapter 23: GPROC Alarms
Description
This alarm indicates that the SYNC circuit output clock has failed.
Possible causes
Procedure
23-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. GPROC: SYNC watchdog timer expired
Description
This alarm indicates that the SYNC circuit generated a watchdog timer expire indication.
Possible causes
Procedure
68P02901W26-S 23-21
Nov 2007
30. GPROC: Clock A signal loss Chapter 23: GPROC Alarms
Description
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.
The fault condition reported by this alarm may cause the site to go OOS.
Possible causes
Procedure
23-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 23-23
Nov 2007
31. GPROC: Clock B signal loss Chapter 23: GPROC Alarms
Description
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 causes
23-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-25
Nov 2007
32. GPROC: TDM interface failure - Assigned timeslot counter underow Chapter 23: GPROC Alarms
Description
The GPROC has determined that the TDM highway is under used. Fewer switch-bound timeslots
are driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes
• One or more MCAP data or address lines on the backplane are faulty.
23-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-27
Nov 2007
33. GPROC: TDM interface failure - Assigned timeslot counter overow Chapter 23: GPROC Alarms
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
23-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-29
Nov 2007
34. GPROC: TDM interface failure - TDM parity error Chapter 23: GPROC Alarms
Description
An incorrect parity was detected on the switch bound or outbound TDM highway.
Possible causes
23-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-31
Nov 2007
35. GPROC: LAN connection failure Chapter 23: GPROC Alarms
Description
The LAN connection between the master GPROC and any other equipped GPROC on the LAN
failed.
System action
The system places the GPROC OOS. If the GPROC is the master GPROC, the site resets.
Possible causes
23-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-33
Nov 2007
39. GPROC: Software failure Chapter 23: GPROC Alarms
Description
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
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 the
programmers.
Possible causes
23-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-35
Nov 2007
40. GPROC: Spurious interrupt Chapter 23: GPROC Alarms
Description
The GPROC received and acknowledged an interrupt message but did not receive a response
from the device generating the interrupt.
Possible causes
• A power fluctuation occurred due to a faulty power supply, a lightning strike, or other
cause.
23-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-37
Nov 2007
42. GPROC: Site reset occurred due to front panel reset Chapter 23: GPROC Alarms
Description
The front panel reset switch was pressed on the BTP MCU and the site was reset.
Possible causes
Procedure
23-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Procedure
68P02901W26-S 23-39
Nov 2007
44. GPROC: Firmware initiated SYNC calibration Chapter 23: GPROC Alarms
Description
This alarm indicates that SYNC calibration was requested by the SYNC firmware MMI.
Possible causes
The operator has requested through the firmware MMI, a calibration of the SYNC circuit.
Procedure
23-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 45. GPROC: SYNC phase lock failure
Description
This alarm indicates that the SYNC circuit has not phase locked to the master within a specified
period of being setup in the slave mode.
Possible causes
Procedure
68P02901W26-S 23-41
Nov 2007
46. GPROC: SYNC invalid mode Chapter 23: GPROC Alarms
Description
This alarm indicates that the SYNC circuitry needs to be replaced. This can only be achieved by
replacing the FRU itself.
Possible causes
• SYNC malfunctioning.
Procedure
23-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 47.
GPROC: Unexpected board type: GPROC2 or {28337} GPROC3/GPROC3–2 expected
Description
A GPROC board was detected in a slot where the system expected to find a GPROC2 or {28337}
GPROC3/GPROC3–2 board.
If this occurs in an InCell site, the GPROC board will not come into service. The maximum
number of timeslots a GPROC can use is 16. A GPROC2 or {28337} GPROC3/GPROC3–2 board
can use 8, 16 or 32 timeslots.
Possible causes
• A GPROC board is installed and the gproc_slots database parameter is set to 32.
Procedure
68P02901W26-S 23-43
Nov 2007
Procedure Chapter 23: GPROC Alarms
23-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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
be replaced at an appropriate time.
Possible causes
Procedure
68P02901W26-S 23-45
Nov 2007
50. GPROC: EEPROM SW ash programming failure Chapter 23: GPROC Alarms
Description
This is a generic flash programming error. A problem has occurred with the operating software.
Possible causes
Procedure
If the board does not reset automatically, a manual reset can be performed
to reload the bootrom object.
23-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 51. GPROC: EEPROM SW ash programming failure
Description
Possible causes
Procedure
68P02901W26-S 23-47
Nov 2007
231. GPROC: TDM interface conguration failure Chapter 23: GPROC Alarms
Description
System action
The system automatically resets the GPROC. If the alarm recurs, the GPROC is placed OOS.
Possible causes
• The GPROC device is not programmed to the designated timeslot when swapping the
TDM highways.
23-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 23-49
Nov 2007
232. GPROC: Processor bus communication failure Chapter 23: GPROC Alarms
Description
A GPROC board device has lost the ability to communicate to the peripheral boards through
the MCAP bus.
Possible causes
• The part of the GPROC that supports the MCAP bus access failed.
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
1 Attempt to bring the GPROC back In Service (INS). If the device is back in
service, the alarm condition has ceased and further fault isolation is not
required. If the device remains OOS, go to step 2.
2 Replace the GPROC board.
23-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The Additional information field includes nine bytes containing process information, as shown
in Table 23-3. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.
Possible causes
Procedure
68P02901W26-S 23-51
Nov 2007
Procedure Chapter 23: GPROC Alarms
23-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. GPROC: Device failure
Description
System action
A single byte is displayed in the Additional information field identifying the type of site reset, as
shown in Table 23-4.
Value Denition
(Hex)
01 Hard reset
02 Soft reset
Possible causes
68P02901W26-S 23-53
Nov 2007
Procedure Chapter 23: GPROC Alarms
Procedure
Wait approximately 10 minutes after this alarm is received to allow the site to reset
before performing the steps.
23-54 68P02901W26-S
Nov 2007
Chapter
24
GSL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details GSL alarms and includes the following alarm procedures:
68P02901W26-S 24-1
Nov 2007
Introduction to GSL alarms Chapter 24: GSL Alarms
GSL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Packet
Control Unit (PCU) GPRS Signaling Link (GSL) interface.
The GSL carries the signaling link traffic between the BSC and a PCU site. The GSL uses
the Multiple Serial Interface link (MMS: E1 link) hardware as its underlying communication
link medium.
24-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. GSL: Invalid received frames - PM
Description
This statistic counts the number of invalid frames received on the LAPD link.
For further information, refer to the GSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The signaling link between the BSC and the PCU is faulty.
Procedure
68P02901W26-S 24-3
Nov 2007
Procedure Chapter 24: GSL Alarms
24-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. GSL: FRMR frames - PM
Description
This statistic counts the number of frames on the LAPD link that were rejected because the
frames were not correctable.
For further information, refer to the GSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The signaling link between the BSC and the PCU is faulty.
Procedure
68P02901W26-S 24-5
Nov 2007
Procedure Chapter 24: GSL Alarms
24-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. GSL: Expiration of N2 - PM
2. GSL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates that the maximum number of link alignment retries has been attempted
without success.
For further information, refer to the GSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The signaling link between the BSC and the PCU is faulty.
Procedure
68P02901W26-S 24-7
Nov 2007
Procedure Chapter 24: GSL Alarms
24-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 is raised as
the primary alarm and you will not see a GSL 10 alarm.
• If MMS thresholds are configured such that the GSL fails before the MMS
failure is signaled in software, you will first see the GSL 10 alarm, followed by
the MMS alarm.
• If the GSL fails due to a layer 2 issue only (LAPD) and the MMS is OK, you will
see the GSL alarm only. The operator can use the OMC to determine any devices
present on the MMS (including GSLs) by clicking the MMS alarm at the OMC.
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:
If the last GSL remains disconnected for more than 30 minutes, the PCU automatically
resets. Depending on the circumstances, this may clear associated alarms and return
the GSL to service.
68P02901W26-S 24-9
Nov 2007
Additional information eld Chapter 24: GSL Alarms
The Additional information field displays the reason code, followed by the timeslot and
associated MMS ID. For example:
Table 24-1 details the Additional information field for this alarm.
Possible causes
• One side of the associated MMS is locked, causing the remote end (not locked) to raise the
Link Disconnected alarm. This may occur when locking any higher level device (MMS,
MSI, GPROC, DPROC).
• Link failure affecting GSL timeslots only, for example when timeslot switching equipment
is used or faulty terminating equipment is present. MMS continues in service while the E1
timeslot 0 is good.
24-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 24-11
Nov 2007
Procedure Chapter 24: GSL Alarms
24-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. GSL: LAPD protocol error
Description
The GSL detected a LAPD protocol error due to a problem on one of the E1 links. Calls may
be lost.
The contents of the Additional information field are shown in Table 24-2.
Possible causes
The LAPD Error String in the Additional information field corresponds to a possible cause
for the alarm, as indicated below:
• Link Timeout.
• Sequence Error.
• Frame Rejected.
• Bad Configuration.
68P02901W26-S 24-13
Nov 2007
Procedure Chapter 24: GSL Alarms
• SABM-Extended Received.
• Bad Frame.
Procedure
24-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. GSL: LAPD protocol error threshold exceeded
Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one minute period.
Possible causes
Procedure
Continued
68P02901W26-S 24-15
Nov 2007
Procedure Chapter 24: GSL Alarms
24-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. GSL: Too many LAPD protocol errors
Description
Too many LAPD protocol errors have been received indicating poor link quality.
There are six bytes. They are Byte 1 – MMS timeslot, Byte 2 – LAPD fault code, Bytes 3-6 –
MMS device ID.
Possible causes
Four or more LAPD Protocol errors were received within 1 second indicating major problems
with the GSL link.
Procedure
1 Check report logs for repeated occurrence of this alarm. If alarm occurs
more than expected, monitor the state of MMS related to the GSL and INS
the GSL device. A field representative may need to visit the site to determine
the quality of the link and adjust, correct or replace it as required.
2 Consult Alarm Handling at the OMC customer documentation. Investigate
further the GSL if this keeps happening.
68P02901W26-S 24-17
Nov 2007
Procedure Chapter 24: GSL Alarms
24-18 68P02901W26-S
Nov 2007
Chapter
25
IAS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details IAS alarms and includes the following alarm procedures:
• 24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure on page 25-36.
• 27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure on page 25-38.
68P02901W26-S 25-1
Nov 2007
Procedure Chapter 25: IAS Alarms
• 75. IAS: IAS +27 V DAB power fuse failure on page 25-79.
• 88 - 90. IAS: Voltage standing wave ratio sector 1-3 failure on page 25-97.
• 91. IAS: Voltage standing wave ratio performance low on page 25-99.
• 96. IAS: No redundant connection to alarms board - Connection broken on page 25-109.
• 98. IAS: No redundant connection to alarms board - Radio OOS on page 25-113.
25-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 99. IAS: No connection to alarm board - Alarm board removed on page 25-115.
• 112 - 113. IAS: Heat management system unit failure 1 and 2 on page 25-139.
68P02901W26-S 25-3
Nov 2007
Introduction to IAS alarms Chapter 25: IAS Alarms
IAS alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Internal Alarm
System (IAS). These alarms are generated by the IAS in the BTS, RXCDR and BSC equipment.
The interface hardware for this system is provided by the power distribution and alarm system.
The IAS is responsible for monitoring all cabinet alarms at a BSS.
25-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. IAS: Unexpected board type
Description
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm.
Take appropriate action and resolve the alarm.
68P02901W26-S 25-5
Nov 2007
Procedure Chapter 25: IAS Alarms
25-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. IAS: Serial bus connection failure
Description
The physical connection between the IAS board and the SBUS failed.
Possible causes
Procedure
1 Review the alarm report to determine cabinet from which the alarm
is reported.
2 In a TTY window, use the disp_equipment <site> cage <cage_id>
command to determine the current database IAS board-to-cage
configuration for a cabinet.
Continued
68P02901W26-S 25-7
Nov 2007
Procedure Chapter 25: IAS Alarms
• If the alarm did not clear, change the setting back to NO.
(There could be a hardware problem rather than an incorrect
setting in the database).
• Go to step 6.
6 If the alarm is still active, send a field representative to the site
to check the IAS alarm board and SBUS connections and cabling
between the IAS board and the SBUS.
25-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-9
Nov 2007
8. IAS: Power supply unit 0 failure Chapter 25: IAS Alarms
Description
A failure of Power Supply Unit 0 has been detected due to one of the following:
• PSU input failure
• Failure type
Possible causes
25-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause of this alarm.
2 Determine whether the PSU failure is related to other more serious fault
conditions. Check the alarm window for other failures at the site with the
PSU power failure. If other failures exist for the site, prioritize the faults
and refer to the relevant section of this manual for the alarm descriptions
and fault resolution procedures.
3 Send a field representative to the site to determine if the input power source
(equipment and/or cables) are faulty or the PSU equipment is faulty. Any
equipment, that is faulty should be replaced.
68P02901W26-S 25-11
Nov 2007
9. IAS: Power supply unit 1 failure Chapter 25: IAS Alarms
Description
A failure of Power Supply Unit 1 has been detected due to one of the following:
• PSU input failure
• Failure type
Possible causes
25-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause of this alarm.
2 Determine whether the PSU failure is related to other more serious fault
conditions. Check the alarm window for other failures at the site with the
PSU power failure. If other failures exist for the site, prioritize the faults
and refer to the relevant section of this manual for the alarm descriptions
and fault resolution procedures.
3 Send a field representative to the site to determine if the input power source
(equipment and/or cables) are faulty or the PSU equipment is faulty. Any
faulty equipment should be replaced.
68P02901W26-S 25-13
Nov 2007
10. IAS: Power supply unit 2 failure Chapter 25: IAS Alarms
Description
A failure of Power Supply Unit 2 has been detected due to one of the following:
• PSU input failure
• Failure type
Possible causes
25-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause of this alarm.
2 Determine whether the PSU failure is related to other more serious fault
conditions. Check the alarm window for other failures at the site with the
PSU power failure. If other failures exist for the site, prioritize the faults
and refer to the relevant section of this manual for the alarm descriptions
and fault resolution procedures.
3 Send a field representative to the site to determine if the input power source
(equipment and/or cables) are faulty or the PSU equipment is faulty. Any
faulty equipment should be replaced.
68P02901W26-S 25-15
Nov 2007
11. IAS: Power supply unit 3 failure Chapter 25: IAS Alarms
Description
A failure of Power Supply Unit 3 has been detected due to one of the following:
• PSU input failure
• Failure type
Possible causes
25-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause of this alarm.
2 Determine whether the PSU failure is related to other more serious fault
conditions. Check the alarm window for other failures at the site with the
PSU power failure. If other failures exist for the site, prioritize the faults
and refer to the relevant section of this manual for the alarm descriptions
and fault resolution procedures.
3 Send a field representative to the site to determine if the input power source
(equipment and/or cables) are faulty or the PSU equipment is faulty. Any
equipment, that is faulty should be replaced.
68P02901W26-S 25-17
Nov 2007
13 – 15. IAS: Preselector 1A-3A fuse failure Chapter 25: IAS Alarms
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).
If standard diversity is used and the preselector is OOS, the receiver sensitivity is reduced
when this alarm is present.
If non-diversity is used and the preselector is OOS, then no receive signal is present at the
related transceiver unit.
Possible causes
25-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 25-19
Nov 2007
16. IAS: Matrix control main fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-21
Nov 2007
17. IAS: Matrix control redundant fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-23
Nov 2007
18. IAS: Internal combiner main fuse failure Chapter 25: IAS Alarms
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).
Possible causes
25-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 25-25
Nov 2007
19. IAS: Internal combiner redundant fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-27
Nov 2007
20. IAS: External combiner main fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-29
Nov 2007
21. IAS: External combiner redundant fuse failure Chapter 25: IAS Alarms
Description
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).
Possible causes
Procedure
25-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-31
Nov 2007
22. IAS: Multicoupler main fuse failure Chapter 25: IAS Alarms
Description
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).
Possible causes
Procedure
25-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-33
Nov 2007
23. IAS: Multicoupler redundant fuse failure Chapter 25: IAS Alarms
Description
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).
Possible causes
Procedure
25-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-35
Nov 2007
24 -26. IAS: BCU lower cage fan #0 - #2 fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-37
Nov 2007
27 -29. IAS: BCU upper cage fan #3 - #5 fuse failure Chapter 25: IAS Alarms
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).
Possible causes
Procedure
25-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-39
Nov 2007
30. IAS: Spare fuse failure Chapter 25: IAS Alarms
Description
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).
Possible causes
Procedure
25-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-41
Nov 2007
31. IAS: DRAM battery backup fuse failure Chapter 25: IAS Alarms
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).
Possible causes
• The battery backup power supply is not connected causing the failure.
Procedure
25-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-43
Nov 2007
32. IAS: IAS +27 V power fuse failure Chapter 25: IAS Alarms
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).
Possible causes
The main +27 V dc power fuse is faulty or blown causing the failure.
Procedure
25-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-45
Nov 2007
33 - 34. IAS: Battery backup fuse #1 - #2 failure Chapter 25: IAS Alarms
Description
This alarm indicates that the Dynamic Random Access Memory (DRAM) dc-to-dc power
converter output (power) fuse on the PDU alarm board has failed.
The fuse on the board is connected to the dc-to-dc power converter for the +27 V battery backup
power supply which sustains power to the Base Station Unit shelf (BSU)/Remote Transcoder
Unit (RXU) in the event of a main power failure.
DC-to-DC converter
This power converter is mounted on the back of the PDU. It converts +27 V dc to +5 V dc for
use by the digital boards in the event of main supply failure. In an emergency, it helps conserve
battery power while providing power to the digital boards required to continue to processing
calls.
Possible causes
• The battery backup power supply is not connected (to the cabinet) causing the failure.
25-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause(s)
of this alarm.
2 Is the battery backup option implemented due to a main power
failure.
68P02901W26-S 25-47
Nov 2007
35 - 37. IAS: Lower cage fan #0 - #2 failure Chapter 25: IAS Alarms
Description
This alarm indicates that a fan in the lower cage has failed. A Transistor-to-Transistor Logic
(TTL) alarm has been generated indicating that a fan has failed.
Possible causes
• A mechanical fault may have occurred (For example, a fan blade was obstructed).
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Determine whether there are event messages for any fuse alarms.
3 Send a field representative to the site to check to see if the fan
is still functioning.
25-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-49
Nov 2007
38 - 40. IAS: Upper cage fan #3 - #5 failure Chapter 25: IAS Alarms
Description
This alarm indicates that a fan in the upper cage has failed. A Transistor-to-Transistor Logic
(TTL) alarm has been generated indicating that a fan has failed.
Possible causes
• A mechanical fault may have occurred (For example, fan blade was obstructed).
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Determine whether there are event messages for any fuse alarms.
3 Send a field representative to the site to check to see if the fan
is still functioning.
25-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 25-51
Nov 2007
41. IAS: Multicoupler failure Chapter 25: IAS Alarms
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).
If a multicoupler fails, the receiver sensitive to the Receive (Rx) signal is degraded on
the failed antenna path.
Possible causes
One or more preselector fuses are faulty or blown causing the failure.
25-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause(s) of this
alarm.
2 Review the applicable device alarm message.
3 Determine whether there are any active or current Voltage Standing Wave
Radio (VSWR) alarms.
68P02901W26-S 25-53
Nov 2007
46. IAS: Converter failure Chapter 25: IAS Alarms
Description
This alarm indicates that the dc-to-dc power converter has failed due to the current output
integrity (state) of the converter.
This power converter module converts -48 V or -60 V dc to +5 V dc and +12 V dc for use by the
digital boards.
Possible causes
25-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Review the applicable device alarm message.
3 Determine if the dc-to-dc power converter failed.
If the dc-to-dc power Then...
converter...
failed Send a field representative to
the site to replace the dc-to-dc
converter module.
did not fail There is a fuse failure.
Send a field representative to
the site to replace the faulty fuse.
68P02901W26-S 25-55
Nov 2007
47. IAS: Converter over temperature Chapter 25: IAS Alarms
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.
Possible causes
25-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Review the alarm report and event logs to determine the cause(s)
of this alarm.
2 Check the alarm report for other internal (cabinet) alarms as well as
External Alarm System (EAS) alarms.
3 After checking the report, determine whether the dc-to-dc converter
failed.
4 Determine whether the antenna is functioning at the site.
If the antenna is... Then...
functioning Send a field representative to the
site to check the following:
68P02901W26-S 25-57
Nov 2007
Procedure Chapter 25: IAS Alarms
25-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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).
Standard diversity
If standard diversity is used and the preselector is Out Of Service (OOS), the receiver sensitivity
to the Receive (Rx) signal is reduced when this alarm is present.
Possible causes
The preselector fuse (1B, 2B, or 3B) is faulty or blown causing the failure.
68P02901W26-S 25-59
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
The following additional data enumerates which duplexer block detected the failure:
• Duplexer block number.
Possible causes
68P02901W26-S 25-61
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
25-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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) or Remote Transcoder Unit (RXU) in the event of a main power failure.
Possible causes
• The battery backup power supply is not connected (to the cabinet) causing the failure.
• The output of the battery backup supply is in an overcurrent protection state thus causing
the output to fail.
68P02901W26-S 25-63
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cause(s)
of this alarm.
2 Is the battery backup option implemented due to a main power
failure.
• If no, go to step 3.
3 Determine the type of cabinet where the alarm is occurring:
• For a BTS5 cabinet, the battery fuse on the PDB, PAB or DAB
must be replaced. Go to step 4.
25-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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) or Remote Transcoder Unit (RXU) in the event of a main power failure.
Possible causes
• The battery backup power supply is not connected (to the power alarm system) causing
the failure.
68P02901W26-S 25-65
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cause(s)
of this alarm.
2 Is the battery backup option implemented due to a main power
failure.
• If no, go to step 3.
3 Determine the type of cabinet where the alarm is occurring:
• For a BTS5 cabinet, the battery fuse on the PDB, PAB or DAB
must be replaced. Go to step 4.
25-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 25-67
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Send a field representative to the site to reset the breaker and/or
replace the faulty hardware.
25-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 62. IAS: DPSM 1 failure
Description
This alarm indicates that the Digital Power Supply Module (DPSM) 1 has failed because the
current to the DPSM 1 was interrupted causing it to fail.
Possible causes
68P02901W26-S 25-69
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Determine whether the DPSM 1 power unit removed just before
the alarm was reported. (Also, determine if there are field
representatives currently at the site).
25-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 63. IAS: DPSM 0 failure
Description
This alarm indicates that the Digital Power Supply Module (DPSM) 0 has failed because the
current to the DPSM 0 was interrupted causing it to fail.
Possible causes
68P02901W26-S 25-71
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Determine whether the DPSM (0) power unit removed just before
the alarm was reported. (Also, determine if there are field
representatives currently at the site).
25-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 25-73
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
In a phased combiner system, only the combiner connected to the faulty transceiver is OOS,
rendering all transceivers attached to the combiner OOS.
Possible causes
68P02901W26-S 25-75
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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) through a circuit breaker was interrupted, causing the converter to fail.
Possible causes
Procedure
68P02901W26-S 25-77
Nov 2007
Procedure Chapter 25: IAS Alarms
25-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 supplies or sustains power to the
Distribution Alarm Board (DAB).
Possible causes
68P02901W26-S 25-79
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 80. IAS: Power supply unit - Input failure
Description
This alarm indicates that there has been a loss of ac power. Due to this power loss, the cabinet
has switched to the emergency battery backup input power supply.
This +27 V battery backup input power supply powers the BTS until the ac power can be
restored or until the battery voltage drops out of range.
This alarm applies only to M-Cell2, M-Cell6, M-Cell micro, M-Cell city, Horizon II macro, Horizon
micro (M-Cell arena) and Horizon compact (M-Cell arena macro) cabinets.
Possible causes
68P02901W26-S 25-81
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
Send a field representative to the site to determine if the input power source
(equipment/cables) are faulty.
25-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 81. IAS: Power supply unit - Output failure
Description
This alarm indicates that there has been a loss of output power due to the failure of the Power
Supply Unit (PSU). It is also possible that the output power failure is due to the input feed
(voltage) which is interrupted (or discontinued) due to faulty equipment.
This alarm applies only to M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
Possible causes
68P02901W26-S 25-83
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
• If other failures exist for the site, prioritize the faults and refer
to this manual for the Alarm descriptions and fault resolution
procedures.
25-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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°C which is beyond the (safe) temperature range allowed for proper
operation of BTS equipment.
This internal cabinet condition has been detected by either the BTS Over Temperature
Thermostat or by the Power Supply Unit (PSU) which has overheated.
Possible causes
• The PSU is malfunctioning. (This possible cause does not apply to Horizon macro cabinets).
• The BTS Heat Management System Over Temperature is faulty. (This possible cause
applies only to outdoor cabinets).
68P02901W26-S 25-85
Nov 2007
Procedure Chapter 25: IAS Alarms
The following happens if a BTS cabinet over temperature condition has occurred
and the cabinet temperature has risen to 80 degrees C:
• The power to that BTS cabinet is shut off. (Onsite, a red LED lights on the
ASPM or the NSPM to indicate the fault condition).
• The system generates the alarm 10. RSL: Link disconnected because an
RSL link is disconnected when the power is shut off.
Procedure
Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, thermostat or BTS heat management system
(outdoor cabinet) equipment is faulty.
25-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 83. IAS: Low voltage disconnect imminent
Description
This alarm indicates that there has been a loss of ac power or the Power Supply Unit (PSU) has
failed, causing a loss of input power from the backup battery.
This alarm is generated when the battery backup power (voltage) is nearing the point where it
starts initiating a disconnection of the BTS cabinets. This alarm applies only to outdoor cabinets.
This +27 V battery backup input power supply powers the BTS until the ac power can be
restored or until the battery voltage drops out of range.
This alarm applies only to M-Cell2, M-Cell6, M-Cell micro, M-Cell city, Horizon II
macro, Horizon micro (M-Cell arena) and Horizon compact (M-Cell arena macro)
cabinets.
68P02901W26-S 25-87
Nov 2007
Possible causes Chapter 25: IAS Alarms
Possible causes
Procedure
1 Review the alarm report and event logs to determine the cause(s) of
this alarm.
2 Investigate the ac power failure.
3 Send a field representative to the site to determine if the PSU and/or
the input power source (equipment/cables) are faulty.
25-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 84. IAS: Air conditioning unit failure
Description
This alarm indicates that a Base Transceiver Station (BTS) or ancillary cabinet Air Conditioning
Unit has failed.
This alarm is generated when an air conditioning (air) inlet or outlet is blocked causing the
equipment to fail. This alarm applies only to outdoor cabinets, M-Cell2 and M-Cell6 cabinets.
Possible causes
• The air outlet vent from the air conditioning unit is blocked causing the unit to fail.
68P02901W26-S 25-89
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 alarm is generated when a heat management (air) inlet or outlet is blocked causing the
equipment to fail. This alarm applies only to outdoor cabinets.
This alarm may be received in conjunction with the alarm, 82. IAS: BTS Cabinet Over
Temperature.
This alarm applies only to, M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
Possible causes
• The air outlet vent from the heat management unit is blocked causing the unit to fail.
68P02901W26-S 25-91
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field service representative to the site to locate the failed unit.
2 Check if the inlet/outlet vents are blocked.
25-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 86. IAS: Cabinet fan failure
Description
This alarm indicates that a Base Transceiver Station (BTS) or ancillary cabinet fan (or fans)
has failed.
This alarm is generated when a fan has stopped functioning due to a power loss or an (air flow)
obstruction causing the equipment to stop. (The obstruction may have damaged the unit). This
alarm applies only to outdoor M-Cell2 and M-Cell6 cabinets.
Possible causes
• The air outlet vent from the fan unit is blocked causing the unit to fail.
• The Power Supply Unit (PSU) is malfunctioning causing the fan units to stop.
68P02901W26-S 25-93
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 internal cabinet condition has been detected by either the Ancillary Over Temperature
Thermostat or by the Power Supply Unit (PSU) which has overheated. This alarm applies only to
M-Cell2, M-Cell6 and Horizon II macro cabinets.
Possible causes
• The Ancillary heat management system over temperature is faulty. (This applies only to
outdoor cabinets).
68P02901W26-S 25-95
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, thermostat or Ancillary Heat Management
System (outdoor cabinet) equipment is faulty.
25-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 88 - 90. IAS: Voltage standing wave ratio sector 1-3 failure
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.
Possible causes
• The Alarms (or the EAS or PIX) board is improperly connected to the VSWR Bridge.
68P02901W26-S 25-97
Nov 2007
Procedure Chapter 25: IAS Alarms
The VSWR unit is typically connected to the Alarms board or EAS (PIX)
depending on the type of platform. Therefore, the specific alarms or EAS (or
PIX) board or connections used may be the source of this fault condition. Ensure
that it is properly connected; check the connectors on the suspect board which
connect to the VSWR Bridge.
Procedure
Procedure 25-46 IAS: Voltage standing wave ratio sector 1-3 failure
• The connection between the VSWR Bridge and the Alarms board (or
the EAS or PIX board).
• The antenna.
25-98 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 91. IAS: Voltage standing wave ratio performance low
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.
Possible causes
• The antenna is faulty due to weather conditions, external damage, errors in installation
and so on.
• The Alarms (or the EAS or PIX) board (or connectors on the board) is faulty. (Refer Note).
68P02901W26-S 25-99
Nov 2007
Procedure Chapter 25: IAS Alarms
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
• The antenna.
• The link between the VSWR Bridge and the Alarms board (or EAS or
PIX board).
25-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 92. IAS: Smoke alarm
Description
This alarm indicates that smoke has been detected within either a Base Transceiver Station
(BTS) or an ancillary cabinet. This fault condition indicates that the cabinet is overheated to a
level which may damage the equipment inside.
This alarm was generated because an internal cabinet over temperature condition was detected
by either the BTS (or Ancillary) Over Temperature Thermostat or by a Power Supply Unit (PSU)
that has overheated.
Possible causes
The cause for the smoke alarm is fire which is caused by one of the following:
• The air passage ways (inlet, outlet and air ways) is obstructed causing the equipment to
overheat.
• The Ancillary Heat Management System is faulty causing the equipment to overheat. (This
possible cause applies only to outdoor cabinets).
68P02901W26-S 25-101
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field representative to the site to determine if the air passage ways
are obstructed or if the PSU, the thermostat, the fan(s), the air conditioning
unit or the Ancillary Heat Management System (outdoor cabinet) is faulty.
2 Replace any defective (or damaged) equipment.
25-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 93. IAS: Door open
Description
This alarm indicates that at a site a cabinet door is open which should not be.
This alarm applies only to M-Cell2, M-Cell6, Horizon macro and Horizon II macro
cabinets.
Possible causes
68P02901W26-S 25-103
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-104 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
When any of the following alarms are active, all other IAS and EAS alarms in the
active list (using disp_act <site #> command) are not dependable:
68P02901W26-S 25-105
Nov 2007
Possible causes Chapter 25: IAS Alarms
Possible causes
• The Alarms board link is connected to an Out Of Service (OOS) DRI (TCU).
• The Alarms board link is connected to an Enabled-Unlocked DRI (TCU) that does not
have an RTF equipped.
Procedure
1 Send a field representative to the site to determine the cause of the failure.
2 Take appropriate action and resolve the alarm.
25-106 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 95. IAS: Low noise amplier 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.
Possible causes
• The cabling connecting the fuse panel and IADU board is faulty.
68P02901W26-S 25-107
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
Send a field representative to the site to check and replace the fuse, the
Alarms board, the IADU board and/or the cabling if necessary.
25-108 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 96. IAS:
No redundant connection to alarms board - Connection broken
Description
This alarm indicates that BSS software has detected that the redundant (backup) radio
connection to the alarms board is not functioning. The redundant connection may not be
functioning due to either a faulty cable or an onsite disconnection.
Possible causes
• The redundant cable between the radio and alarms board is faulty.
68P02901W26-S 25-109
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field representative to the site to check the cabling from the Alarms
board to the (radio) DRI (TCUs).
2 Be prepared to reconnect or replace the cabling to the Alarms board, if
necessary.
25-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 97. IAS: No connection to alarm board - Radio OOS
Description
This alarm indicates that the BSS software has detected that all radio (Transceiver Control Unit
(TCU)) connections to the alarms board are Out Of Service (OOS).
This alarm is generated when the last (final) radio connection goes OOS. In this case, there is no
connection because the radios (DRI (TCUs)) are faulty.
• This alarm applies to M-Cell2, M-Cell6, Horizon macro and Horizon II macro
cabinets.
• When any of the following alarms are active, all other IAS and EAS alarms in the
active list (using disp_act <site #> command) are not dependable:
94.IAS: No Connection to Alarms Board - Connection Broken.
97.IAS: No Connection to Alarms Board - Radio OOS.
99.IAS: No Connection to Alarms Board - Alarm Board Removed.
Possible causes
68P02901W26-S 25-111
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field representative to the site to check the radios (DRI (TCUs))
connected to the alarms board.
2 Attempt to restore the faulty DRI (TCUs) to service and replace either or
both DRI (TCUs), if necessary.
25-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 98. IAS: No redundant connection to alarms board - Radio OOS
Description
This alarm indicates that BSS software has detected that the redundant radio (Transceiver
Control Unit (TCU)) connections to the alarms board are Out Of Service (OOS). The two radios
(DRI (TCUs)) are connected to the alarms board.
This alarm applies to M-Cell2, M-Cell6, Horizon macro and Horizon II macro cabinets.
Possible causes
Procedure
1 Send a field representative to the site to check both radios (DRI (TCUs))
connected to the alarms board.
2 Identify the faulty DRI (TCU).
3 Attempt to restore the faulty (redundant) DRI (TCU) to service and replace
it, if necessary.
68P02901W26-S 25-113
Nov 2007
Procedure Chapter 25: IAS Alarms
25-114 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 Horizon macro and Horizon II macro cabinets.
When any of the following alarms are active, all other IAS and EAS alarms in the
active list (using disp_act <site #> command) are not dependable:
68P02901W26-S 25-115
Nov 2007
Possible causes Chapter 25: IAS Alarms
Possible causes
Procedure
25-116 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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
continues to operate. Otherwise, the power system will shutdown and require an onsite visit to
reset the power system. The cabinet protection system monitors and reports the environmental
fault conditions:
• A cabinet over temperature condition - The internal cabinet temperature has exceeded
safe limits.
• A smoke condition - A fire has produced smoke that has either originated in or penetrated
into the cabinet.
Possible causes
68P02901W26-S 25-117
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Check the power supply, control board and input circuit breaker connections,
attempt to reconnect them and be prepared to replace any of the above,
if necessary.
2 Reset the power system after the fault condition has been resolved.
25-118 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 101. IAS: Power supply temperature high
Description
This alarm indicates that BSS software has detected that one or more Power Supply Units
(PSUs) in a Horizon macro BTS has exceeded the established (safe) temperature range.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
68P02901W26-S 25-119
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to check for other alarms at
the same site.
25-120 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 102. IAS: Mains ac supply failure
Description
This alarm indicates that BSS software has detected that ac power to the backup battery box
(connected to a Horizon macro cabinet) is no longer available. As a result, ac power is not
being sent through to the Horizon macro BTS.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• The cable from the rectifier to the external Horizon macro alarm connector is not properly
connected.
• The cable (or connector on the cable) from the rectifier to the external Horizon macro
alarm connector is faulty.
68P02901W26-S 25-121
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-122 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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).
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
68P02901W26-S 25-123
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-124 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 104. IAS: Fan tray 1 failure
Description
This alarm indicates that BSS software has detected that a fan within fan tray 1 has either failed
or has not been properly installed (connected).
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
68P02901W26-S 25-125
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-126 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 105. IAS: Fan tray 2 failure
Description
This alarm indicates that BSS software has detected that a fan within fan tray 2 has either failed
or has not been properly installed (connected).
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
68P02901W26-S 25-127
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-128 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 106. IAS: Rectier failure
Description
This alarm indicates that BSS software has detected that the output from a backup battery box
has failed. This alarm is generated when the rectifier has failed or the cable from the battery
box (rectifier)-to-Horizon macro alarm connector is faulty; or when the cable is not properly
connected.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• The cable from the rectifier to the external Horizon macro alarm connector is not properly
connected.
• The cable (or connector on the cable) from the rectifier to the external Horizon macro
alarm connector is faulty.
68P02901W26-S 25-129
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-130 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 107. IAS: Battery box temperature high
Description
This alarm indicates that BSS software has detected that the temperature in the backup battery
box has exceeded the established limits for safe operation of the equipment.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• The cable from the battery box to a cabinet is not properly connected.
• The cable (or cable connectors) from the battery box to a cabinet is faulty.
68P02901W26-S 25-131
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
25-132 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 108. IAS: Alarm board failed
Description
This alarm indicates that BSS software has detected that the alarms board in a Horizon macro
BTS has failed due to faulty (Alarms) board circuitry or board damage due to conditions in
the field.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• The Alarms board may have failed due to faulty circuitry on the board.
68P02901W26-S 25-133
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Review the alarm report and event logs to determine the cabinet ID
for the Horizon macro cabinet where the alarms board has failed.
25-134 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 109. IAS: Auxiliary alarm 1
Description
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
Procedure
68P02901W26-S 25-135
Nov 2007
110. IAS: Urgent critical alarm Chapter 25: IAS Alarms
Description
The IAS 110 alarm is a customer or site-specific external alarm. It is often configured
for Horizon macro and Horizon II macro battery backup testing, but it may be also
used for a variety of other purposes. Care must therefore be taken when responding
to this alarm.
Possible causes
Possible causes are varied depending on the actions to which the alarm is tied.
Procedure
If the IAS110 alarm is used for Horizon macro and Horizon II macro battery backup testing,
refer to the relevant service manual. For all other purposes, refer to local site procedures.
25-136 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 111. IAS: Cabinet protection board fuse failure
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.
Possible causes
Procedure
1 Send a field representative to the site to determine the cause of the failure.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 25-137
Nov 2007
Procedure Chapter 25: IAS Alarms
25-138 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 112 - 113. IAS: Heat management system unit failure 1 and 2
Description
This alarm is generated if the Heat Management System (HMS) at a BTS cabinet fails.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
Procedure
1 Send a field representative to the site to determine the cause of the failure.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 25-139
Nov 2007
Procedure Chapter 25: IAS Alarms
25-140 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 114 - 115. IAS: Mains ac supply failure 1 and 2
Description
This alarm indicates that the BSS software has detected that the main ac input power to the
backup battery box is no longer available. This results in a loss of ac input power to the BTS.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• Faulty or disconnected cable between the rectifier and the external alarm connector.
Procedure
1 Send a field representative to the site to determine the cause of the failure.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 25-141
Nov 2007
Procedure Chapter 25: IAS Alarms
25-142 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 116 - 117. IAS: Rectier failure 1 and 2
Description
This alarm indicates that the BSS software has detected that the rectifier output from a backup
battery box has failed.
This alarm applies only to Horizon macro and Horizon II macro cabinets.
Possible causes
• Faulty or disconnected cable between the battery box (rectifier) and external alarm
connector.
68P02901W26-S 25-143
Nov 2007
Procedure Chapter 25: IAS Alarms
Procedure
1 Send a field representative to the site to determine the cause of the failure
and take appropriate action.
2 Check the output LEDs on the rectifier front panel and replace the rectifiers
that are defective from the power cage. If no rectifiers are defective,
check the cable from the rectifiers in the battery box to the external alarm
connector. It is loose, not properly connected or faulty, if so, connect it
properly or replace if faulty.
25-144 68P02901W26-S
Nov 2007
Chapter
26
KSW Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Kiloport Switch (KSW) and the KSW device subtype, Timeslot Switch (TSW) alarms covered
in this chapter are as follows:
• 11 KSW: Local cage KSW TDM loopback test failure on page 26-41.
• 22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure on page
26-48.
• 25 - 27. KSW: KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure on page
26-51.
68P02901W26-S 26-1
Nov 2007
Introduction to KSW alarms Chapter 26: KSW Alarms
KSW alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the
Kiloport Switch (KSW) and the KSW device subtype, Timeslot Switch (TSW) device.
The KSW alarms are comprised of Hardware and Firmware alarms. The hardware alarms
are categorized into two groups. They are Interrupt Generating alarms and MCAP Register
Reported Alarms.
The alarms in this chapter apply to InCell BSU-based systems (including ExCell and TopCell).
Alarm reporting
The KSW alarms are reported to the GPROC through status registers on the MCAP bus or by
assertion of an interrupt (message) onto the MCAP bus. The GPROC software then reports
the KSW alarms.
Hardware alarms are generated due to fault conditions with the following:
• The Digital Signaling Processor (DSP)
FRUs
A KSW device may be equipped on one of the FRUs shown in Table 26-1.
FRU Description
KSW Kiloport Switch
TSW Timeslot Switch
KSW-Old Kiloport Switch - Old version
26-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R FRUs
Throughout this chapter, reference is made to InCell BTSs. Assume InCell BTS to
mean a BTS4, BTS5, BTS6, ExCell, or TopCell.
68P02901W26-S 26-3
Nov 2007
0. KSW: Parity highway 0 Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected a parity
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway
0. The timeslots containing the parity error are masked until the alarm is acknowledged.
When this alarm occurs, two KSWs cannot communicate with each other. Each KSW (TSW) is
in a different cage.
This is a KSW firmware alarm and is therefore, generated according to fault conditions existing
on the TDM highways or fault conditions existing on the KSW board.
The contents of the Additional information field are shown in Table 26-2. Up to 33 bytes may
be displayed in this field.
Example
For example, second and third bytes of 02 41; fourth and fifth bytes of 00 03. This indicates a
timeslot range of three consecutive timeslots, beginning at timeslot 241, equal to a timeslot
range from 241 to 244.
If applicable, 6th to 9th, 10th to 13th, 14th to 17th, 18th to 21st, 22nd to 25th, 26th to 29th and
30th to 33rd bytes are handled in a similar way to the second and fifth bytes described above.
26-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• 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).
• The KSW may have experienced this parity error due to the failure of one or more of the
devices such as: MSI/XCDR, DRI, GDP, GPROC, KSW, RTF.
The KSW Parity Highway 0 alarms are detected by the KSW device. These
alarms frequently indicate that a different device (or devices) is causing a
problem on the TDM highway.
Procedure
1 Refer to the alarm message report; determine the site number, device
identifiers, slot number and cage of the KSW with the parity error.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View menu select State to check the operational
and administrative state of the SITE device.
3 Ensure that the following devices have been reviewed and checked
as potential cause(s) for the KSW fault conditions such as MSI/XCDR,
DRI, GPROC, KSW.
Continued
68P02901W26-S 26-5
Nov 2007
Procedure Chapter 26: KSW Alarms
If yes, immediately
switch to the redundant
TDM highway (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, go to step 5.
only a block of timeslots are Acknowledge the alarms and
down monitor the alarm events/report
to see if the alarm recurs. The
KSW device has failed.
If no, go to step 5.
5 Determine whether this alarm was followed by a 254. KSW: Device
Failed alarm.
If this alarm is followed by... Then...
a 254. KSW: Device Failed The KSW device has failed. Swap
alarm to the redundant KSW. Send a
field representative to the site to
replace the KSW board (and any
other faulty hardware).
no device failed alarm Review the parity set up for each
of the timeslots. Establish the
proper parity set up for any of the
timeslots that are off. Go to step 6.
Continued
26-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-7
Nov 2007
1. KSW: Parity highway 1 Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected a parity
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway 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 causes
• The KSW may have erroneously detected a problem with the parity bit on TDM expansion
highway 1.
Procedure
26-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-9
Nov 2007
2. KSW: Parity highway 2 Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected a parity
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway 2.
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 causes
• The KSW may have erroneously detected a problem with the parity bit on TDM expansion
highway 2.
Procedure
26-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-11
Nov 2007
3. KSW: Parity highway 3 Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected a parity
error occurring on one (or more) timeslots comprising Time Division Multiplex (TDM) highway 3.
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 causes
• The KSW may have erroneously detected a problem with the parity bit on TDM expansion
highway 3.
Procedure
26-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-13
Nov 2007
4. KSW: Clock A signal loss Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has detected
a Clock A failure in the system. As a result, the internal (active) clock reference has failed and
may cause the Site to go Out Of Service (OOS) if the redundant clock (GCLK) cannot be accessed.
When this alarm is generated, the KSW switches to the redundant Clock B. However, if Clock
B is not clear of alarms or the clock has been forced to Clock A, the system does not switch
to Clock B.
This 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 causes
26-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Wait 10 minutes and use the State option from the View menu to
verify that the SITE device is In Service (INS).
2 If the SITE is not INS, send a field representative to the site to
determine where the hardware or cabling is faulty.
3 If the SITE is INS, use the State option from the View menu to check
the operational and administrative state of all of the device(s) at a
site. Determine whether the site is fully operational.
Continued
68P02901W26-S 26-15
Nov 2007
Procedure Chapter 26: KSW Alarms
26-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Site is in a state
Continued
68P02901W26-S 26-17
Nov 2007
Procedure Chapter 26: KSW Alarms
26-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. KSW: Clock B signal loss
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has detected
a Clock B failure in the system. As a result, the internal (active) clock reference has failed and
may cause the Site to go Out Of Service (OOS) if the redundant clock (GCLK) cannot be accessed.
When this alarm is generated, the KSW switches to the redundant Clock A. However, if Clock
A is not clear of alarms or the clock has been forced to Clock B, the system does not switch
to Clock A.
This 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 causes
68P02901W26-S 26-19
Nov 2007
Procedure Chapter 26: KSW Alarms
Procedure
1 Wait 10 minutes and use the State option from the View menu to
verify that the SITE device is In Service (INS).
2 If the SITE is not INS, send a field representative to the site to
determine where the hardware or cabling is faulty.
Continued
26-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-21
Nov 2007
Procedure Chapter 26: KSW Alarms
Continued
26-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-23
Nov 2007
6. KSW: 6.12 seconds reference loss Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) has detected that
the time reference (6.12 seconds reference pulse) has been lost on the Time Division Multiplex
(TDM) highway due to a failed KSW clock extender (GCLK/KSWX) board.
The KSW switches to the redundant clock. However, if the redundant clock is not clear of
alarms or the clock has been forced to the present clock, the system does not switch to the
redundant clock.
This 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 causes
26-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 26-25
Nov 2007
Procedure Chapter 26: KSW Alarms
26-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 (onsite) may have reset
the device manually after performing system maintenance.
Possible causes
• The KSW board is reset by the software, thus, causing the failure.
• One of the peripheral boards related to the MMS may have failed.
Procedure
Wait for a minute for the re-initialization to complete before continuing with this
procedure.
68P02901W26-S 26-27
Nov 2007
Procedure Chapter 26: KSW Alarms
1 Refer to the alarm message report; determine the site number, device
identifiers, slot number and cage of the re-initialized KSW device.
2 From the Navigation Tree, open the Detailed View for the KSW.
From the View menu select State to check the operational and
administrative state of the KSW.
If the KSW is... Then...
busy_unlocked The alarm condition has ceased
and further fault isolation is not
required. Monitor this device
for a recurrence of the alarm
condition. If recurrence of the
alarm is excessive, send a field
representative to the site to
replace the KSW.
not busy_unlocked Wait for the re-initialization
sequence to complete. Use the
INS option from the Fault Mgt
menu for the KSW.
3 From the Fault Mgt menu select the Lock option to place the KSW
Out Of Service (OOS).
4 From the Fault Mgt menu select the Unlock option to bring the
KSW back In Service (INS).
5 From the View menu again select State to check the operational and
administrative state of the KSW.
If the KSW is... Then...
busy and unlocked The alarm condition has ceased
and further fault isolation is not
required. Monitor this device
for a recurrence of the alarm
condition. If recurrence of the
alarm is excessive, send a field
representative to the site to
replace the KSW.
not busy and unlocked Send a field representative to
the site to replace the KSW. An
additional alarm must have taken
the KSW Out Of Service (OOS).
26-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-29
Nov 2007
8. KSW: Hard reset Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) device is currently undergoing a hard reset
causing the board to fail in the system.
The reset may have been necessary because the KSW may have been functioning improperly.
The software may have detected it or a field representative (on site) may have reset the device
manually after performing system maintenance.
This alarm generates a Motorola Cellular Advanced Processor (MCAP) interrupt message if the
appropriate bit has been set in the interrupt enable register.
Possible causes
Procedure
The following procedure can be used to correct the fault and clear the alarm.
Wait for a minute for the re-initialization to complete before continuing with this
procedure.
26-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-31
Nov 2007
Procedure Chapter 26: KSW Alarms
26-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
Possible causes
• One of the peripheral boards related to the MMS may have failed.
68P02901W26-S 26-33
Nov 2007
Procedure Chapter 26: KSW Alarms
Procedure
Wait for a minute for the re-initialization to complete before continuing with this
procedure.
Continued
26-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-35
Nov 2007
10. KSW: Lost communication with KSW Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) is not responding to Fault Management (FM)
software processes when it attempts to communicate with that KSW.
The system impact of this alarm varies depending on the site configuration. For example, if only
one KSW is equipped at a site, an automatic site reset (re-initialization) occurs.
However, if a site has both a master and a redundant KSW, the redundant device is swapped into
the master KSW role. While the faulty KSW then takes an (inactive) role.
If the (new) master KSW is not equipped in an expanded TDM configuration, calling
capacity for that site is reduced or the site is reset.
Possible causes
• The Motorola Cellular Advanced Processor (MCAP) Bus on the backplane may have failed.
26-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Clearing the alarm
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
• If no, go to step 8.
6 Determine whether the reset was successful by checking the SITE
device state:
Continued
68P02901W26-S 26-37
Nov 2007
Procedure Chapter 26: KSW Alarms
Continued
26-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-39
Nov 2007
Procedure Chapter 26: KSW Alarms
26-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
The BSS attempts to clear this alarm automatically through a Fault Management Initiated
Clear (FMIC) after the fault condition has been resolved. The KSW must be placed In Service
(INS) before this alarm can clear.
68P02901W26-S 26-41
Nov 2007
Procedure Chapter 26: KSW Alarms
Procedure
Continued
26-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure 26-16 Local cage KSW TDM loopback test failure (Continued)
6 Determine whether the KSW(s) are functioning properly.
Execute the state command to verify that the master KSW (and
redundant, if present) are functioning in the proper device state(s).
If the KSW is... Then...
busy_unlocked The master KSW is
functioning properly.
If a redundant KSW is
present, it should be in an
enabled_unlocked state.
Check if the redundant KSW is in
the correct device state.
68P02901W26-S 26-43
Nov 2007
Procedure Chapter 26: KSW Alarms
26-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 through the
correct (expansion mode) KSWXs.
This fault condition adversely affects system performance within the Time Division Multiplex
(TDM) matrix. In this case, the inbound portion of the (active) expanded Time Division Multiplex
(TDM) highway (to the specific KSW) has been compromised.
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.
During initialization, the In Service (INS) TDM highway (matrix) is automatically tested for both
active and standby TDM highways.
After the initialization has been completed, the Expanded TDM highway can be tested by using
the device_audit command for the active TDM device.
To test the standby TDM highway after initialization, that (standby) TDM device must be
swapped into the active role. Execute the swap_device command to switch the standby TDM
into the active role (busy_unlocked). Then, proceed with the test.
68P02901W26-S 26-45
Nov 2007
Additional information eld Chapter 26: KSW Alarms
This alarm description applies to the Expanded Inbound TDM Highway failure alarms for the
four KSW pairs: 0, 1, 2 and 3. The alarm name displays the KSW pair number related to the
fault condition. There are four separate alarms.
The additional information in the output for this alarm displays the slot number of the KSW
Extender (KSWX) card to which the expanded inbound TDM highway is connected.
Possible causes
• The expansion mode KSWX software configuration is incorrect due to an erroneous value
being entered for the Configuration Management (CM) ksw_config database parameter.
• The fiber connections between expansion mode KSWX cards are faulty.
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
Continued
26-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• If no, go to step 3.
3 Execute the disp_element ksw_config command to verify that the
current ksw_config (CM) database parameter settings are correct.
If fault appears to be in... Then...
CM database parameter Send a field representative
setting(s) to the site to compare (and
contrast) CM parameter settings.
The settings displayed in the
output of the disp_element
ksw_config command must be
compared to the actual onsite
configuration. This establishes
whether the KSWX fiber and
connections are correct.
hardware or equipment Send a field representative to the
site to check board connections;
reconfigure and/or replace any
faulty equipment.
68P02901W26-S 26-47
Nov 2007
22 - 24. KSW: KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch Extender card (KSWX/DSWX) residing within the
specified Expansion mode slot (7-9) has detected that the expanded KSW matrix has failed.
This alarm is generated when the KSWX/DSWX is no longer receiving TDM data from another
expansion mode KSWX/DSWX. This fault condition adversely affects system performance within
the Time Division Multiplex (TDM) matrix.
Expansion mode
A KSWX/DSWX operating in Expansion mode is used to expand the TDM highway by connecting
two different KSWs that are controlling two distinct parts of the TDM Highway. Fiber optic
links are used.
The TDM Highway is divided into four portions. Each portion is controlled by a different KSW.
Each KSW is capable of operation independently of the other KSWs. However, it is necessary to
exchange data across the four portions of the TDM highway using fiber optic links.
As a result, expansion mode is used to provide communication across the TDM matrix. The TDM
matrix consists of an array of all the KSWs and the respective (assigned) portions of the TDM
Highway displaying the interconnections between KSWs within the TDM Highway.
The KSWX/DSWX expands the TDM highway from the associated KSW (in the same cage)
to the related KSWX/DSWX in an expanded cage. While in expansion mode, a KSWX/DSWX
is dependent upon its associated KSW (in either the same cage or the expanded cage) for
successful operation.
If the associated KSW goes Out Of Service (OOS), the KSWX/DSWX is not monitored for faults.
In addition, any alarms that are related to the KSWX/DSWX is not cleared from the system
even when a fault condition has been resolved.
26-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Additional information eld
This alarm description applies to the KSWX/DSWX matrix failure alarms for three KSWX/DSWX
cards in slots 7, 8 and 9. The alarm name displays the slot number of the KSWX/DSWX card
related to the fault condition. There are three separate alarms.
Possible causes
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
Procedure 26-18 KSWX/DSWX in Slot 7-9 detected expanded KSW matrix failure
1 Refer to the alarm message report to check for the slot number of
the KSWX/DSWX for which this alarm is being generated.
2 Send a field representative to the site to check fiber cables, fiber
connections and/or faulty KSWX/DSWX cards. Verify that the toggle
switch on the KSWX/DSWX is in the middle (enabled) position.
Re-insert cards, reconnect, enable and/or replace faulty equipment
when necessary.
68P02901W26-S 26-49
Nov 2007
Procedure Chapter 26: KSW Alarms
26-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25 - 27. KSW:
KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure
Description
This alarm indicates that a Kiloport Switch Extender card (KSWX/DSWX) residing within the
specified Expansion mode slot (21-23) has detected that the expanded KSW matrix has failed.
This alarm is generated when the KSWX/DSWX is no longer receiving TDM data from another
expansion mode KSWX/DSWX. This fault condition adversely affects system performance within
the Time Division Multiplex (TDM) matrix.
Expansion mode
A KSWX/DSWX operating in Expansion mode is used to expand the TDM highway by connecting
two different KSWs that are controlling two distinct parts of the TDM Highway. Fiber optic
links are used.
The TDM Highway is divided into four portions. Each portion is controlled by a different KSW.
Each KSW is capable of operation independently of the other KSWs. However, it is necessary to
exchange data across the four portions of the TDM highway using fiber optic links.
As a result, expansion mode is used to provide communication across the TDM matrix. The TDM
matrix consists of an array of all the KSWs and the respective (assigned) portions of the TDM
Highway displaying the interconnections between KSWs within the TDM Highway.
The KSWX/DSWX expands the TDM highway from the associated KSW (in the same cage)
to the related KSWX/DSWX in an expanded cage. While in expansion mode, a KSWX/DSWX
is dependent upon its associated KSW (in either the same cage or the expanded cage) for
successful operation.
If the associated KSW goes Out Of Service (OOS), the KSWX/DSWX is not monitored for faults.
In addition, any alarms that are related to the KSWX/DSWX is not cleared from the system
even when a fault condition has been resolved.
68P02901W26-S 26-51
Nov 2007
Additional information eld Chapter 26: KSW Alarms
This alarm description applies to the KSWX/DSWX matrix failure alarms for three KSWX/DSWX
cards in slots 21, 22 and 23. The alarm name displays the slot number of the KSWX/DSWX card
related to the fault condition. There are three separate alarms.
Possible causes
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
Procedure
Procedure 26-19 KSWX/DSWX in Slot 21-23 detected expanded KSW matrix failure
1 Refer to the alarm message report to check for the slot number of
the KSWX/DSWX for which this alarm is being generated.
2 Send a field representative to the site to check fiber cables, fiber
connections land/or faulty KSWX/DSWX cards. Verify that the toggle
switch on the KSWX/DSWX is in the middle (enabled) position.
Re-insert cards, reconnect, enable and/or replace faulty equipment
when necessary.
26-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-53
Nov 2007
224. KSW: Safe test audit failure Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) board has failed the safe test audit generated
by the System Audit Process (SAP) portion of the Fault Management (FM) software in the system.
If the results of the audit reveal that the audit performed on the KSW was not completed,
this alarm is reported.
Safe Audit Tests use the inter-process messages to interrogate the target hardware device.
The tests determine the sanity of the processor in each of the intelligent boards and the
communication link which carries the audit messaging protocol (basic Ack handshake). These
tests are not service affecting.
Safe Test Audit does not take the device Out Of Service (OOS) or interrupt its primary
functionality.
Possible causes
• A hardware problem on the KSW board may have prevented the KSW from responding
properly to the audit.
• A Loss of power to the KSW board may have prevented it from responding to the audit.
26-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Clearing the alarm
The BSS attempts to clear this alarm automatically through the Fault Management Initiated
Clear (FMIC) after this fault condition has been resolved.
Procedure
68P02901W26-S 26-55
Nov 2007
Procedure Chapter 26: KSW Alarms
26-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 225. KSW: Internal loopback audit failure
Description
This alarm indicates that a Kiloport Switch (KSW) or Timeslot Switch (TSW) board has failed
the loopback test audit generated by the System Audit Process (SAP) portion of the Fault
Management (FM) software in the system.
If the results of the audit reveal that the audit performed on the KSW was not completed,
this alarm is reported. This alarm is generated as a result of the system audit KSW (TSW)
internal loopback failure.
This Loopback Test audit involves sending a command to a hardware entity instructing it,
to perform internal loopback tests (within itself). After completing the tests, the hardware
automatically returns the test result for fault handling (For example, local TDM bus loopback
through the KSW).
This alarm is not generated again even if the audit fails because Operator Initiated
Clear (OIC) alarms are reported only once by Fault Management software.
Possible causes
• A hardware problem on KSW/TSW board may have prevented the KSW/TSW from
responding properly to the audit.
• A loss of power to KSW/TSW board may have prevented it from responding to the audit.
68P02901W26-S 26-57
Nov 2007
Clearing the alarm Chapter 26: KSW Alarms
This is an Operator Initiated Clear (OIC) alarm that must be cleared by the operator after the
fault condition has been resolved.
Procedure
26-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-59
Nov 2007
232. KSW: Processor bus communication failure Chapter 26: KSW Alarms
Description
This alarm indicates that a Kiloport Switch (KSW) device has lost the ability to communicate to
the GPROC through the Motorola Cellular Advanced Processor (MCAP) Bus.
Possible causes
• The portion of the KSW and/or the GPROC board that supports the MCAP bus access
has failed.
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
26-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 26-61
Nov 2007
Procedure Chapter 26: KSW Alarms
26-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. KSW: Device failure
Description
The Fault Management (FM) software requested that this specific device be removed from
service. As a result, the KSW is automatically placed Out Of Service (OOS).
This fault can be service affecting. At all times, a site must have at least one
functioning KSW. Otherwise, the site goes OOS.
Possible causes
This device failed as a result of a problem (with this device) that was detected by another
device, which then reported the failure.
The BSS attempts to clear this alarm automatically through a Fault Management Initiated Clear
(FMIC) after the fault condition has been resolved.
68P02901W26-S 26-63
Nov 2007
Procedure Chapter 26: KSW Alarms
Procedure
26-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 26-65
Nov 2007
Procedure Chapter 26: KSW Alarms
26-66 68P02901W26-S
Nov 2007
Chapter
27
LAN Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details LAN alarms and includes the following alarm procedures:
• 0. LAN: Lan 0 on page 27-3.
68P02901W26-S 27-1
Nov 2007
Introduction to LAN alarms Chapter 27: LAN Alarms
LAN alarms
This chapter describes the alarms and OMC-R troubleshooting procedures for the Local Area
Network (LAN) device.
The LAN alarms are generated when a fault condition occurs and is detected by the LAN
Monitor Process (LMP). The LMP is located on the Generic Processor (GPROC) that is connected
to the LAN.
27-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. LAN: Lan 0
0. LAN: Lan 0
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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.
Possible causes
68P02901W26-S 27-3
Nov 2007
Procedure Chapter 27: LAN Alarms
Procedure
Determine the state of the site. Perform the following procedure to resolve the alarm.
Wait approximately 10 minutes after this alarm is received to allow the site to reset
before following this procedure.
27-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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:
• The redundant LAN device failed to respond when polled by the LAN Monitor Process
(LMP). In this situation the system tries to change the state of the device to re-establish
LAN redundancy. The LANX board remains OOS if a fault condition exists.
• The LMP detected that the active LAN device failed and a swap to the redundant LAN has
immediately been implemented. The failed LAN is now in the role of the redundant device
and the system therefore tries to change the state of the device to re-establish redundancy.
The LANX board remains OOS, if a fault condition exists.
In both cases, the OMC-R alarm logs reflect a state change for the redundant LAN device from
enabled unlocked (E/U) to disabled unlocked (D/U). If redundancy is successfully re-established,
the state then changes back to E/U.
System action
Depending on the circumstances described above, the system swaps the failed active LAN with
the standby LAN and/or tries to re-establish LAN redundancy.
68P02901W26-S 27-5
Nov 2007
Possible causes Chapter 27: LAN Alarms
Possible causes
Procedure
1 Determine if the alarm was reported for the active LAN or the
standby LAN.
If the alarm is reported for Then...
the...
active LAN Go to step 2.
standby LAN Go to step 3.
2 Determine the state of the active LAN device.
If the LAN is... Then...
busy-unlocked 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 appropriate
action.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
3 Send a field representative to the site to determine the cause of the
alarm and take appropriate action.
27-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 27-7
Nov 2007
Procedure Chapter 27: LAN Alarms
27-8 68P02901W26-S
Nov 2007
Chapter
28
LMTL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Local Message Transfer Link (LMTL) alarms are covered in this chapter and includes the
following alarm procedures:
• 0. LMTL: Signaling link failure on page 28-3.
• 10. LMTL: Threshold reached: MSUs discarded due to SL congestion - PM on page 28-29.
68P02901W26-S 28-1
Nov 2007
Introduction to LMTL alarms Chapter 28: LMTL Alarms
LMTL alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the
Local Message Transfer Link (LMTL) device.
The LMTL device provides the 64 kbps connection between the SMLC and the BSC. The
connection exists on a timeslot on the MMS device. The connection supports the ITU-TSS
Signaling System 7 MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part)
protocols with the variations specified by GSM.
28-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. LMTL: Signaling link failure
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 0 alarm.
See 0. MTL: Signaling Link Failure.
The BSS reports an LMTL Signaling Link Failure alarm when the E1 link supporting the LMTL
goes out of service. An LMTL connection between the SMLC and BSC has failed. No signaling
information is passed between the SMLC and BSC over the disconnected link.
This is a service-affecting fault if the last functioning LMTL link is placed OOS. If
another link exists, this is not a service-affecting fault.
The BSS clears an LMTL Signaling Link Failure alarm when the E1 link supporting the
LMTL returns to service.
If no other LMTL links are in service when this alarm is reported, the Last LMTL Link Failure
- Signaling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS
is placed OOS.
The contents of the Additional information field are shown in Table 28-1.
68P02901W26-S 28-3
Nov 2007
Possible causes Chapter 28: LMTL Alarms
Possible causes
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive signaling error rate.
Procedure
Continued
28-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 28-5
Nov 2007
0. LMTL: SL failure - All reasons - PM Chapter 28: LMTL Alarms
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.
This statistic counts the number of times a Signaling Link (SL) has failed for all causes excluding
operator interaction using the MMI.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
An MSI failed.
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
28-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 28-7
Nov 2007
1. LMTL: SMLC processor outage Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 1 alarm.
Refer 1. MSC Processor Outage.
The BSS reports an LMTL SMLC Processor Outage alarm when the remote SMLC processor
for the LMTL goes out of service.
The MSC processor is OOS. This processor failure causes the LMTL link to be blocked. When
the LMTL link is blocked, no user signaling traffic can be exchanged.
The BSS clears an LMTL SMLC Processor Outage alarm when the remote SMLC processor for
the LMTL comes back into service.
Possible causes
The SMLC processor for the remote MTP layer 2 link(s) malfunctioned or failed.
28-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 28-9
Nov 2007
1. LMTL: Threshold reached: SL failure - abnormal FIBR/BSNR - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 1 alarm.
Refer 1. MTL: SL Failure - FIBR/BSNR - PM.
The BSS reports an LMTL SL Failure - Abnormal FIBR/BSNR - PM alarm when the
LMTP_SL_FIBR counter exceeds the specified threshold.
This statistic counts the number of times a Signaling Link (SL) is lost due to the detection of
an abnormal Forward Indicator Bit (FIB) caused by the de-synchronization of the Backward
Sequence Number (BSN) and Forward Sequence Number (FSN).
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
28-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if any BSN and FSN are being corrupted by the MSC. Perform the following
procedure to resolve the alarm.
68P02901W26-S 28-11
Nov 2007
2. LMTL: Threshold reached: SL failure - excessive delay of ACK - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 2 alarm.
Refer 2. MTL: SL Failure - Excessive Delay of ACK - PM.
The BSS reports an LMTL SL Failure - Excessive Delay of ACK - PM alarm when the
LMTP_SL_ACK counter exceeds the specified threshold.
This statistic counts the number of times a Signaling Link (SL) was lost because the system failed
to acknowledge a Message Signal Unit (MSU) before an internal Motorola defined timer expired.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
A signaling link failed and an MSU acknowledgment has not been sent.
28-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if the MSU is sent by the MSC. Perform the following procedure to resolve the alarm.
68P02901W26-S 28-13
Nov 2007
3. LMTL: Link trafc too high Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 3 alarm.
Refer 3. MTL: Link Traffic Too High.
The BSS reports an LMTL Link Traffic Too High alarm when the LMTL software process
becomes over congested.
Congestion is detected at either the local or remote end of the LMTL affecting the flow of the
signaling traffic across MTP Layer 2.
This alarm does not necessarily indicate that there is a physical problem with the LMTLs.
A network congestion problem is probably causing the LMTL links to experience signaling
congestion.
System action
After the alarm is reported, flow control procedures are started at the MTP Layer 2 level to
handle congestion. These procedures ensure that user messages are stored in an MTP Layer
2 buffer for transmission when the signaling traffic subsides and returns to a normal level of
activity. When MTP Layer 2 has used all of its buffer space, user messages are discarded.
Possible causes
High traffic levels on the LMTL do not allow enough time for the device driver to process frames.
28-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 28-15
Nov 2007
3. LMTL: Threshold reached: SL failure - excessive error rate - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 3 alarm.
Refer 3. LMTL: SL Failure - Excessive Error Rate - PM.
The BSS reports an LMTL SL Failure - Excessive Error Rate - PM alarm when the
LMTP_SL_ERROR_RATE counter exceeds the specified threshold.
This statistic counts the number of times a Signaling Link (SL) was lost because the Signal Unit
Error Rate Monitor (SUERM) timer expired.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
An MSI failed.
28-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
68P02901W26-S 28-17
Nov 2007
4. LMTL: Threshold reached: SL failure - excessive duration of congestion - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the LMTL 4 alarm.
Refer 4. LMTL: SL Failure - Excessive Duration of Congestion - PM.
The BSS reports an LMTL SL Failure - Excessive Duration of Congestion - PM alarm when
the LMTP_REMOTE_SL_CONGESTION counter exceeds the specified threshold.
This statistic counts the number of times a Signaling Link (SL) was lost because the remove
congestion timer expired. This congestion condition occurs on the SL when the threshold levels
establishing the capacity of the transmission or re-transmission buffer of a Message Signal
Unit (MSU) are reached.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
28-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 28-19
Nov 2007
5. LMTL: Threshold reached: SL alignment failure - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 5 alarm.
Refer 5. MTL: SL Alignment Failure - PM.
The BSS reports an LMTL SL Alignment Failure - PM alarm when the LMTP_SL_ALIGNMENT
counter exceeds the specified threshold.
This statistic monitors the system to detect when a Signaling Link (SL) has attempted to align
with the A-Interface while the interface is OOS. This fault condition occurs when the alignment
has been lost.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The SL is OOS.
28-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if other alarms associated with the SL were reported. Perform the following
procedure to resolve the alarm.
68P02901W26-S 28-21
Nov 2007
6. LMTL: Threshold reached: Number of signal units in error - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 6 alarm.
Refer 6. MTL: Number of Signals Units in Error - PM.
The BSS reports an LMTL Number of Signals Units in Error - PM alarm when the
LMTP_SU_ERROR counter exceeds the specified threshold.
This statistic counts the number of times that an erroneous Signaling Unit (SU) is received
on the Signaling Link (SL).
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
28-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
68P02901W26-S 28-23
Nov 2007
7. LMTL: Threshold reached: SL number of negative ACKs received - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 7 alarm.
Refer 7. MTL: SL Number of Negative ACKs Received - PM.
The BSS reports an LMTL SL Number of Negative ACKs Received - PM alarm when the
LMTP_NEG_ACKS counter exceeds the specified threshold.
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, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
There is no additional information in the output for this alarm. Perform the following procedure
to resolve the alarm.
Possible causes
28-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the messages between the BSS and the MSC are out of
sequence.
If the messages are... Then...
not out of sequence The fault condition no longer
exists. Clear the alarm.
out of sequence Go to step 2.
2 Determine if the MSC is sending the messages.
If the MSC is... Then...
sending the messages Contact the MSC to resolve the
fault and then clear the alarm.
not sending the messages Send a field representative to the
site to resolve the communication
link fault and then clear this alarm.
68P02901W26-S 28-25
Nov 2007
8. LMTL: Threshold reached: Start of remote processor outage - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 8 alarm.
Refer 8. MTL: Start of Remote Processor Outage - PM.
The BSS reports an LMTL Start of Remote Processor Outage - PM alarm when the
LMTP_START_RPO counter exceeds the specified threshold.
This statistic counts each instance that a remote processor outage is identified. This remote
processor outage occurs when signaling messages cannot be transferred.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
There is no additional information in the output for this alarm. Perform the following procedure
to resolve the alarm.
Possible causes
28-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 28-27
Nov 2007
9. LMTL: Threshold reached: Number of octets retransmitted - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 9 alarm.
Refer 9. MTL: Number of Octets Retransmitted - PM.
The BSS reports an LMTL Number of Octets Retransmitted - PM alarm when the
LMTP_RE_TX counter exceeds the specified threshold.
This statistic counts the number of octets that the BSS has retransmitted to the BSS-based
SMLC due to a request by the BSS-based SMLC.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The BSS retransmitted an excessive number of octets. Perform the following procedure to
resolve the alarm.
Procedure
28-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. LMTL:
Threshold reached: MSUs discarded due to SL congestion - PM
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 10 alarm.
Refer 10. MTL: MSUs Discarded due to SL Congestion - PM.
The BSS reports an LMTL MSUs Discarded due to SL Congestion - PM alarm when the
LMTP_MSU_DISCARDED counter exceeds the specified threshold.
This statistic counts each instance that a Message Signal Unit (MSU) is discarded while there is
congestion on the Signaling Link (SL).
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of LMTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
1 These alarms are not cleared by the BSS and cannot be cleared by the
operator.
2 If this alarm occurs continuously, the number of LMTLs for the BSS is not
adequate to handle the call volume. Increase the number of LMTLs for
the BSS.
68P02901W26-S 28-29
Nov 2007
11. LMTL: SL congestion events resulting in loss of MSUs - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 11 alarm.
Refer 11. MTL: SL Congestion Events Resulting in Loss of MSUs - PM.
The BSS reports an LMTL SL Congestion Events Resulting in Loss of MSUs - PM alarm
when the LMTP_CONGESTION_LOST_MSU counter exceeds the specified threshold.
This statistic counts each Signaling Link (SL) congestion event which results in Message Signal
Units (MSUs) being lost.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of LMTLs allotted for the BSS is insufficient to handle the volume of calls.
28-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 These alarms are not cleared by the BSS and cannot be cleared by the
operator.
2 The alarm is due to congestion. The capacity of the current LMTLs is
insufficient to handle the signaling traffic. If this alarm recurs, capacity
must be increased by the addition of LMTLs.
68P02901W26-S 28-31
Nov 2007
12. LMTL: Threshold reached: SL congestion indications - PM Chapter 28: LMTL Alarms
Description
This alarm relates to the Lb-interface, but in all other respects is identical to the MTL 12 alarm.
Refer 12. MTL: SL Congestion Indications - PM.
This statistic counts the number of times that a Signaling Link (SL) is congested with a high
volume of calls.
For further information, refer to the LMTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of LMTLs allotted for the BSS is insufficient to handle the volume of calls.
28-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 These alarms are not cleared by the BSS and cannot be cleared by the
operator.
2 The alarm is due to congestion. The capacity of the current LMTLs is
insufficient to handle the signaling traffic. If this alarm recurs, capacity
must be increased by the addition of LMTLs.
68P02901W26-S 28-33
Nov 2007
Procedure Chapter 28: LMTL Alarms
28-34 68P02901W26-S
Nov 2007
Chapter
29
MMS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Multiple Serial Interface Link (MMS) alarms are covered in this chapter and include the
following procedures:
• 0. MMS: Synchronization loss daily threshold exceeded on page 29-5.
• 24. MMS: Modem to NIU serial channel control link failure on page 29-47.
• 25. MMS: HDSL modem loop 0 sync loss timer expired on page 29-49.
• 26. MMS: HDSL modem loop 1 sync loss timer expired on page 29-53.
• 27. MMS: Master HDSL modem loop 0 SNR daily threshold exceeded on page 29-56.
• 28. MMS: Master HDSL modem loop 1 SNR daily threshold exceeded on page 29-58.
68P02901W26-S 29-1
Nov 2007
Procedure Chapter 29: MMS Alarms
• 29. MMS: Slave HDSL modem loop 0 SNR daily threshold exceeded on page 29-60.
• 30. MMS: Slave HDSL modem loop 1 SNR daily threshold exceeded on page 29-62.
• 31. MMS: Master HDSL modem loop 0 SNR hourly threshold exceeded on page 29-64.
• 32. MMS: Master HDSL modem loop 1 SNR hourly threshold exceeded on page 29-66.
• 33. MMS: Slave HDSL modem loop 0 SNR hourly threshold exceeded on page 29-68.
• 34. MMS: Slave HDSL modem loop 1 SNR hourly threshold exceeded on page 29-70.
• 35. MMS: Master HDSL modem loop 0 SNR OOS threshold exceeded on page 29-72.
• 36. MMS: Master HDSL modem loop 1 SNR OOS threshold exceeded on page 29-76.
• 37. MMS: Slave HDSL modem loop 0 SNR OOS threshold exceeded on page 29-80.
• 38. MMS: Slave HDSL modem loop 1 SNR OOS threshold exceeded on page 29-84.
• 41. MMS: Connectivity mismatch between BSC and the RXCDR on page 29-91.
• 42. MMS: DSW/DSWX switching hardware required, BSC is now operating in Single
Rate mode on page 29-93.
29-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
• M-Cell2, M-Cell6, Horizon macro, Horizon compact (M-Cell arena macro), Horizon
compact2 and micro site systems, which include M-Cell city, M-Cell micro, Horizon micro
(M-Cell arena) and Horizon micro2.
Depending on the system software configuration, the MMS device can be configured as E1
(2.048 Mbps) link.
The hardware used determines whether the (MMS) links are located on either the InCell
Multiple Serial Interface (MSI) board or on the M-Cell/Horizon Network Interface Unit (NIU).
E1 alarm exceptions
The Synchronization MMS alarms (0, 1, 2 and 16) apply only to systems with an E1 link
configuration.
M-Cell alarms
The alarms contained in this chapter which apply to the M-Cell2, M-Cell6 and M-Cell micro site
system products are generated for the NIU.
The following is the M-Cell (NIU) hardware that can generate an MMS alarm:
• The NIU in either an M-Cell2 or an M-Cell6 cabinet.
• The NIUm in an M-Cell micro, M-Cell city, Horizon micro (M-Cell arena) or Horizon micro2
unit.
Alarm reporting
The InCell MMS hardware alarms are reported to the GPROC by MSI, XCDR, and GDP boards
through the MCAP bus. The M-Cell MMS hardware alarms are reported by the M-Cell processor.
68P02901W26-S 29-3
Nov 2007
FRUs Chapter 29: MMS Alarms
• An MSI/MSI-2 board, MSI in an RF Unit, an XCDR (or GDP) board or a Network Interface
Unit (NIU) - on either side of the link.
• A remote system.
FRUs
An MMS device may be equipped on one of the FRUs shown in Table 29-1.
FRU Description
MSI Multiple Serial Interface board.
XCDR Transcoder board.
GDP Generic DSP Processor or Generic Downloadable Processor.
Replacement for XCDR.
NIU M-Cell/Horizon Network Interface Unit with one or two links.
MSI2-CONV M-Cell MSI that converts a link from E1 to T1 and from T1 to E1.
MSI2 M-Cell MSI configurable for E1 operation.
MSI-EXT-HDSL External HDSL modem.
NIU-HDSL Network interface unit for HDSL.
NIU-EXT-HDSL Network interface unit for external HDSL.
DPROC For GPRS PCU, MMS resides on Network Interface Board (NIB),
which is mounted on the DPROC board.
NIUm Horizon macro (M-Cell micro) NIU/MSI with one or two links.
NIUm-HDSL Network interface unit for HDSL on Horizon micro or Horizon micro2.
NIUm-EXT-HDSL Network interface unit for external HDSL on Horizon micro or
Horizon micro2.
ARENA (NIU) Horizon micro (M-Cellarena) NIU/MSI.
ARENA MAC (NIU) Horizon compact (M-Cell arena Macro) NIU/MSI.
HORIZONMIC2 (NIU) Horizon micro2 NIU.
HORIZONCOM2 Horizon compact2 NIU.
(NIU)
29-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MMS: Synchronization loss daily threshold exceeded
Description
The number of times the MMS receive signal lost synchronization exceeded the sync_loss_daily
database element threshold.
Possible causes
68P02901W26-S 29-5
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
29-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MMS: Synchronization loss hourly threshold exceeded
Description
The number of times the MMS receive signal lost synchronization in a one hour period has
exceeded the sync_loss_hourly database element threshold.
Possible causes
68P02901W26-S 29-7
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
29-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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
Possible causes
Procedure
68P02901W26-S 29-9
Nov 2007
Procedure Chapter 29: MMS Alarms
Continued
29-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-11
Nov 2007
4. MMS: Remote alarm daily threshold exceeded Chapter 29: MMS Alarms
Description
This mechanism counts each occurrence of the Remote Loss OOS alarm remote_loss_oos.
When the remote Alarm Daily Threshold Exceeded remote_loss_daily threshold is reached
by this count, a warning alarm is generated.
Possible causes
29-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 29-13
Nov 2007
5. MMS: Remote alarm hourly threshold exceeded Chapter 29: MMS Alarms
Description
This mechanism counts each occurrence of the Remote Loss OOS Alarm (remote_loss_oos).
When the Remote Alarm Hourly Threshold Exceeded (remote_loss_hourly) threshold is
reached, a warning alarm is generated.
Possible causes
29-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 29-15
Nov 2007
6. MMS: Remote alarm OOS threshold exceeded Chapter 29: MMS Alarms
Description
This mechanism is a counter that is incremented each time warning alarm 4. MMS: Remote
Alarm Daily Threshold Exceeded is generated. When the remote_loss_OOS threshold is
reached, the MSS is placed OOS.
System action
Possible causes
Procedure
29-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 29-17
Nov 2007
Procedure Chapter 29: MMS Alarms
29-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 8. MMS: Frame slip daily threshold exceeded
Description
The number of frame slips on the E1 link exceeded the slip_loss_daily database element
threshold.
Possible causes
Procedure
68P02901W26-S 29-19
Nov 2007
Procedure Chapter 29: MMS Alarms
29-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. MMS: Frame slip hourly threshold exceeded
Description
The number of frame slips on the E1 link exceeded the slip_loss_hourly database element
threshold.
Possible causes
Procedure
68P02901W26-S 29-21
Nov 2007
Procedure Chapter 29: MMS Alarms
29-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. MMS: Frame slip OOS threshold exceeded
Description
Number of Frame Slip alarm hits over a 24 hour period exceeded threshold (default: 255).
Possible causes
Procedure
1 If the MMS is D-U, check whether the MMS or MSI is faulty. If MMS/MSI is
faulty, replace board else check cabling, connections and the link interface
board.
2 Verify as necessary, that the MTL, OML or RSL links have been re-established
and all SITEs have returned to service.
3 In the case where the faulty device resides in a Horizon2 cabinet, the MMS
is part of the NIU2 which is onboard the Horizon2 Site Controller (H2SC). In
this case the FRU to be replaced should be the H2SC.
68P02901W26-S 29-23
Nov 2007
12. MMS: Bit error daily threshold exceeded Chapter 29: MMS Alarms
Description
The Bit Error Rate (BER) on the MMS receive signal exceeded the ber_loss_daily database
element threshold.
Possible causes
• The receive E1 link signal is fading in and out due to faulty cabling or faulty connections to
the T43/BIB board.
29-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 29-25
Nov 2007
13. MMS: Bit error hourly threshold exceeded Chapter 29: MMS Alarms
Description
The Bit Error Rate (BER) on the receive signal exceeded the ber_loss_hourly database element
threshold.
Possible causes
• The receive E1 link signal is fading in and out due to faulty cabling or faulty connections to
the T43/BIB board.
29-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 29-27
Nov 2007
14. MMS: Bit error OOS threshold exceeded Chapter 29: MMS Alarms
Description
This mechanism is a counter that is incremented each time warning alarm 12. MMS: Bit Error
Daily Threshold Exceeded is generated. When the Bit Error OOS Threshold Exceeded
(ber_loss_oos) threshold is reached, the MSS is placed OOS.
Possible causes
29-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 29-29
Nov 2007
Procedure Chapter 29: MMS Alarms
29-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
• 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.
68P02901W26-S 29-31
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
Continued
29-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-33
Nov 2007
18. MMS: Remote alarm OOS timer expired Chapter 29: MMS Alarms
Description
The length of time that a remote alarm has been active exceeded the remote_time_oos
database element threshold. This condition is detected by the remote end of the link.
Possible causes
• The 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.
29-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 29-35
Nov 2007
Procedure Chapter 29: MMS Alarms
29-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 20. MMS: Red alarm daily threshold exceeded
Description
The number of times the MMS signal lost synchronization exceeded the red_loss_daily
database element threshold.
Possible causes
• The received E1 link signal is fading in and out due to faulty cabling or faulty connections
to the T43/BIB board.
68P02901W26-S 29-37
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
29-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. MMS: Red alarm hourly threshold exceeded
Description
The number of times the MMS signal lost synchronization exceeded the red_loss_hourly
database element threshold.
Possible causes
• The receive E1 link signal is fading in and out due to faulty cabling or faulty connections to
the T43/BIB board.
68P02901W26-S 29-39
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
29-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 29-41
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
Continued
29-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-43
Nov 2007
23. MMS: Red alarm OOS timer expired Chapter 29: MMS Alarms
Description
The length of time that the MMS lost synchronization exceeded the red_time_oos database
element threshold.
System action
Possible causes
Procedure
29-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 29-45
Nov 2007
Procedure Chapter 29: MMS Alarms
29-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
This fault condition is potentially service affecting. If the modem continues to function, calls
or service are not affected. The purpose of this alarm is to provide notification of a possible
problem in the HDSL modem or the related NIU MMS link hardware.
68P02901W26-S 29-47
Nov 2007
Possible causes Chapter 29: MMS Alarms
Possible causes
Procedure
Send a field representative to the site to determine the cause of the alarm.
Take appropriate action and resolve the alarm.
29-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. MMS: HDSL modem loop 0 sync 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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
If there is no functioning redundant link, calls are dropped and data being transmitted
is lost. The site may lose service if the connection is lost.
68P02901W26-S 29-49
Nov 2007
Possible causes Chapter 29: MMS Alarms
Possible causes
Procedure
Continued
29-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure 29-20 HDSL modem loop 0 sync loss timer expired (Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
reporting the alarm.
If the SITEs are... Then...
busy-unlocked The fault condition no longer
exists. Go to step 6.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
68P02901W26-S 29-51
Nov 2007
Procedure Chapter 29: MMS Alarms
29-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 26. MMS: HDSL modem loop 1 sync loss timer expired
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
The MMS and HDSL modem are placed OOS. HDSL modem loop 2 sync timer expired.
Possible causes
68P02901W26-S 29-53
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
Continued
29-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure 29-21 HDSL modem loop 1 sync loss timer expired (Continued)
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
68P02901W26-S 29-55
Nov 2007
27. MMS: Master HDSL modem loop 0 SNR daily threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-22 Master HDSL modem loop 0 SNR daily threshold exceeded
68P02901W26-S 29-57
Nov 2007
28. MMS: Master HDSL modem loop 1 SNR daily threshold exceeded Chapter 29: MMS Alarms
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop 1 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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-23 Master HDSL modem loop 1 SNR daily threshold exceeded
68P02901W26-S 29-59
Nov 2007
29. MMS: Slave HDSL modem loop 0 SNR daily threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-24 Slave HDSL modem loop 0 SNR daily threshold exceeded
68P02901W26-S 29-61
Nov 2007
30. MMS: Slave HDSL modem loop 1 SNR daily threshold exceeded Chapter 29: MMS Alarms
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop 1 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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-25 Slave HDSL modem loop 1 SNR daily threshold exceeded
68P02901W26-S 29-63
Nov 2007
31. MMS: Master HDSL modem loop 0 SNR hourly threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-26 Master HDSL modem loop 0 SNR hourly threshold exceeded
68P02901W26-S 29-65
Nov 2007
32. MMS: Master HDSL modem loop 1 SNR hourly threshold exceeded Chapter 29: MMS Alarms
Description
The Signal-to-Noise Ratio (SNR) on the master HDSL modem on loop 1 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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-27 Master HDSL modem loop 1 SNR hourly threshold exceeded
68P02901W26-S 29-67
Nov 2007
33. MMS: Slave HDSL modem loop 0 SNR hourly threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-28 Slave HDSL modem loop 0 SNR hourly threshold exceeded
68P02901W26-S 29-69
Nov 2007
34. MMS: Slave HDSL modem loop 1 SNR hourly threshold exceeded Chapter 29: MMS Alarms
Description
The Signal-to-Noise Ratio (SNR) on the slave HDSL modem on loop 1 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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
Possible causes
29-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Procedure 29-29 Slave HDSL modem loop 1 SNR hourly threshold exceeded
68P02901W26-S 29-71
Nov 2007
35. MMS: Master HDSL modem loop 0 SNR OOS threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
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.
The site ID where the master modem is physically located and the MMS ID associated with the
slave modem are displayed.
29-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Procedure 29-30 Master HDSL modem loop 0 SNR OOS threshold exceeded
Continued
68P02901W26-S 29-73
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure 29-30 Master HDSL modem loop 0 SNR OOS threshold exceeded
(Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
reporting the alarm.
If the SITEs are... Then...
busy-unlocked The fault condition no longer
exists. Go to step 6.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
29-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-75
Nov 2007
36. MMS: Master HDSL modem loop 1 SNR OOS threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
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.
The site ID where the master modem is physically located and the MMS ID associated with the
slave modem are displayed.
29-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Procedure 29-31 Master HDSL modem loop 1 SNR OOS threshold exceeded
Continued
68P02901W26-S 29-77
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure 29-31 Master HDSL modem loop 1 SNR OOS threshold exceeded
(Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
reporting the alarm.
If the SITEs are... Then...
busy-unlocked The fault condition no longer
exists. Go to step 6.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
29-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-79
Nov 2007
37. MMS: Slave HDSL modem loop 0 SNR OOS threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
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.
The site ID where the master modem is physically located and the MMS ID associated with the
slave modem are displayed.
29-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Procedure 29-32 Slave HDSL modem loop 0 SNR OOS threshold exceeded
Continued
68P02901W26-S 29-81
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure 29-32 Slave HDSL modem loop 0 SNR OOS threshold exceeded
(Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
reporting the alarm.
If the SITEs are... Then...
busy-unlocked The fault condition no longer
exists. Go to step 6.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer exists.
busy-unlocked No further action is required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer exists.
No further action is required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
29-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-83
Nov 2007
38. MMS: Slave HDSL modem loop 1 SNR OOS threshold exceeded Chapter 29: MMS Alarms
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.
This alarm applies only to M-Cell city, Horizon micro (M-Cell arena), Horizon micro2
and Horizon compact2 units.
System impact
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.
The site ID where the master modem is physically located and the MMS ID associated with the
slave modem are displayed.
29-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
Procedure 29-33 Slave HDSL modem loop 1 SNR OOS threshold exceeded
Continued
68P02901W26-S 29-85
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure 29-33 Slave HDSL modem loop 1 SNR OOS threshold exceeded
(Continued)
4 In a TTY window, execute the disp_mms_ts_usage command to
display the logical link devices assigned to the MMS.
If logical link devices Then...
assigned to the MMS
include...
RSLs Go to step 5.
5 Determine the state of each of the SITEs connected by the MMS
reporting the alarm.
If the SITEs are... Then...
busy-unlocked The fault condition no longer
exists. Go to step 6.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
6 Determine the state of the logical link devices assigned to the MMS.
If... Then...
all of the logical links are The fault condition no longer
busy-unlocked exists. No further action is
required.
any of the logical links are For RSL links, an MMS link
enable-unlocked interface failure occurred. Send a
field representative to the site to
determine the cause of the alarm
and take appropriate action.
any of the logical links are Reset the link device and then go
disable-unlocked to step 7.
7 Determine the state of the logical link device after the reset is
complete.
If the device is... Then...
busy-unlocked The fault condition no longer
exists. No further action is
required.
not busy-unlocked Send a field representative to the
site to determine the cause of the
alarm and take appropriate action.
29-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-87
Nov 2007
39. MMS: LTU download failure Chapter 29: MMS Alarms
Description
LTU Firmware upgrade has failed. The alarm is raised against the MMS corresponding to
the LTU which failed to upgrade.
Possible causes
29-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 29-89
Nov 2007
40. MMS: LTU conguration failure Chapter 29: MMS Alarms
Description
Reconfiguration of LTU settings has failed. The alarm is raised against the MMS corresponding
to the LTU which failed the reconfiguration.
Possible causes
The firmware may have failed to configure for reasons like Xmodem unable to initialize the
COM port.
Procedure
29-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 41. MMS: Connectivity mismatch between BSC and the 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 causes
68P02901W26-S 29-91
Nov 2007
Procedure Chapter 29: MMS Alarms
Procedure
1 Display the connectivity information for the BSC and the RXCDR.
2 Compare the BSC and the RXCDR connectivity information to the
network plan.
If the network plan is Then...
different than...
the connectivity information at Correct the connectivity
the BSC information at the BSC.
the connectivity information at Correct the connectivity
the RXCDR information at the RXCDR.
29-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 42. MMS:
DSW/DSWX switching hardware required, BSC is now operating in Single Rate mode
Description
The alarm is FMIC. The alarm will be cleared once all KSW and KSWX switching hardware
is replaced by DSW and DSWX switching hardware and the operator has enabled enhanced
capacity mode. The alarm indicates that at least one CIC is blocked due for this reason.
{22168} The BSS supports the DSW2/DSWX switching hardware required alarm to
indicate that the MMS devices cannot go into service due to lack of DSW/DSWX.
Possible causes
KSW and KSWX switching hardware remains enabled in the site or enhanced capacity mode
has not been enabled.
Procedure
1 Replace all KSW and KSWX switching hardware with DSW and DSWX
switching hardware.
2 Ensure enhanced capacity mode is enabled.
68P02901W26-S 29-93
Nov 2007
253. MMS: Critical alarm threshold exceeded Chapter 29: MMS Alarms
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.
If the mms_cat_enable database parameter is enabled, the MMS is taken OOS and
remains OOS until it is reset by the operator or if there are no critical MMS alarms
for 10 minutes (system brings the MMS back into service). If the mms_cat_enable
database parameter is disabled, the MMS returns to service when the alarm clears.
An operator reset overrides the stability wait time and bring back the MMS
immediately. If the mms_cat_enable parameter is enabled, there is no threshold
checking so alarms and clears are processed as they occur.
29-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The E1 link signal is fading in and out due to faulty cabling or connections to the T43/BIB
board.
Procedure
Continued
68P02901W26-S 29-95
Nov 2007
Procedure Chapter 29: MMS Alarms
29-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 29-97
Nov 2007
Procedure Chapter 29: MMS Alarms
29-98 68P02901W26-S
Nov 2007
Chapter
30
MSI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Multiple Serial Interface (MSI) alarms are covered in this chapter and include the following
procedures:
• 0. MSI: Re-initialized unexpectedly on page 30-3.
68P02901W26-S 30-1
Nov 2007
Introduction to MSI alarms Chapter 30: MSI Alarms
MSI alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with
the Multiple Serial Interface (MSI) device.
Transcoder (XCDR) and Generic DSP Processor (GDP) alarms are reported as MSI alarms. The
FRU field in the alarm report identifies XCDR and GDP alarms.
FRUs
An MSI device may be equipped on one of the FRUs shown in Table 30-1.
FRU Description
ARENAm (NIU) Horizon micro (M-Cell arena) NIU.
ARENAm MAC (NIU) Horizon compact (M-Cell arena Macro) NIU.
ARTESYN NIB Artesyn™ NIB.
FORCE NIB Force™ NIB.
GDP Generic DSP Processor or Generic Downloadable Processor.
Replacement for XCDR.
MSI Multiple Serial Interface Board.
MSI2-CONV M-Cell MSI that converts a link from E1 to T1 and from T1 to E1.
MSI2 MSI configurable for E1 operation.
NIU M-Cell Network Interface Unit with one or two links.
NIU-EXT-HDSL M-Cell MSI supporting external HDSL modems.
NIU-EXT-HDSL M-Cell NIU supporting external HDSL modems.
NIU-HDSL M-Cell NIU supporting integrated HDSL modems.
NIUm M-Cell micro NIU with one or two links.
NIUm-HDSL M-Cell micro NIU supporting integrated HDSL modems. Only
supported in E1 environment.
NIUm-EXT-HDSL M-Cell micro NIU supporting external HDSL modems. Only supported
in E1 environment.
XCDR Transcoder.
30-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MSI: Re-initialized unexpectedly
Description
Possible causes
Procedure
Wait for a minute after this alarm is reported before continuing with this procedure.
68P02901W26-S 30-3
Nov 2007
Procedure Chapter 30: MSI Alarms
30-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MSI: Hard reset
Description
Possible causes
Procedure
Wait for a minute after this alarm is reported before continuing with this procedure.
68P02901W26-S 30-5
Nov 2007
Procedure Chapter 30: MSI Alarms
30-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. MSI: Watchdog timer expired
Description
Possible causes
68P02901W26-S 30-7
Nov 2007
Procedure Chapter 30: MSI Alarms
Procedure
30-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MSI: Clock B signal loss
Description
Possible causes
Procedure
68P02901W26-S 30-9
Nov 2007
Procedure Chapter 30: MSI Alarms
30-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. MSI: Clock A signal loss
Description
Possible causes
Procedure
68P02901W26-S 30-11
Nov 2007
Procedure Chapter 30: MSI Alarms
30-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. MSI: Assigned timeslot counter underow
Description
The MSI has determined that the TDM highway is under used. Fewer switch-bound timeslots
are driven onto the TDM bus than were allocated in the assigned timeslot counter register.
Possible causes
• One or more MCAP data or address lines on the backplane are faulty.
Procedure
68P02901W26-S 30-13
Nov 2007
Procedure Chapter 30: MSI Alarms
30-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. MSI: Assigned timeslot counter overow
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 causes
• One or more MCAP data or address lines on the backplane are faulty.
Procedure
68P02901W26-S 30-15
Nov 2007
Procedure Chapter 30: MSI Alarms
30-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. MSI: TDM parity error
Description
Possible causes
68P02901W26-S 30-17
Nov 2007
Procedure Chapter 30: MSI Alarms
Procedure
30-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
Possible causes
The RSL, MSI, MMS, KSW, XCDR, or GDP devices can be in the communications path.
Procedure
Send a field representative to the site to replace the XCDR or GDP with
the faulty DSP.
68P02901W26-S 30-19
Nov 2007
Procedure Chapter 30: MSI Alarms
30-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11 - 70. MSI: DSP channel (0-59) audit failure
Description
The DSP channel number (0-59) corresponds to a physical DSP on an XCDR or GDP board. An
XCDR has one channel per DSP; a GDP has two channels per DSP.
The contents of the Additional information field are shown in Table 30-2:
Continued
68P02901W26-S 30-21
Nov 2007
Possible causes Chapter 30: MSI Alarms
Possible causes
Procedure
Continued
30-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 30-23
Nov 2007
224. MSI: Safe test audit failure Chapter 30: MSI Alarms
Description
The MSI failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes.
Possible causes
30-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 30-25
Nov 2007
231. MSI: TDM interface conguration failure Chapter 30: MSI Alarms
Description
System action
The system automatically resets the MSI. If the alarm occurs three times within a 10 minute
period, the MSI is placed OOS.
Possible causes
• The MSI device could not be programmed to the designated timeslot when swapping
the TDM highways.
30-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 30-27
Nov 2007
232. MSI: Processor bus communication failure Chapter 30: MSI Alarms
Description
The MSI board lost the capability to communicate with the GPROC using the MCAP bus.
Possible causes
• The portion of the MSI board that supports the MCAP bus access failed.
30-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 30-29
Nov 2007
234. MSI: Active link connection failure Chapter 30: MSI Alarms
Description
This alarm is generated only for M-Cell2, M-Cell6, M-Cell micro, Horizon micro
(M-Cell arena) and Horizon compact (M-Cell arena macro) hardware.
Possible causes
• The portion of the MSI board and/or the active BTP board that supports the BTP link
connection failed.
30-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 30-31
Nov 2007
254. MSI: Device failure Chapter 30: MSI Alarms
Description
Possible causes
Procedure
Continued
30-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 30-33
Nov 2007
Procedure Chapter 30: MSI Alarms
30-34 68P02901W26-S
Nov 2007
Chapter
31
MTL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Message Transfer Link (MTL) alarms are covered in this chapter and include the following
procedures:
• 0. MTL: Signaling link failure on page 31-3.
• {28337} 13. MTL: SL failure - Excessive error rate on HSP MTL - PM on page 31-25.
68P02901W26-S 31-1
Nov 2007
Introduction to MTL alarms Chapter 31: MTL Alarms
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 kbps connection between the MSC and the BSC. The connection
exists on a timeslot on the MMS device. The connection supports the ITU-TSS Signaling System
7 MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part) protocols with
the variations specified by GSM.
31-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MTL: Signaling link failure
Description
An MTL connection between the MSC and BSC failed. No signaling 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 an MTL 0 alarm.
• If MMS thresholds are configured such that the MTL fails before the MMS
failure is signaled in software, you will first see the MTL 0 alarm, followed by
the MMS alarm.
• If the MTL fails due to a layer 2 issue only (LAPD) and the MMS is OK, then
you will see the MTL alarm only. The operator can use the OMC to determine
any devices present on the MMS (including MTLs) by clicking the MMS alarm
at the OMC.
This is a service-affecting fault when the last functioning MTL link is placed OOS. If
another link exists, this is not a service-affecting fault.
If no other MTL links are in service when this alarm is reported, the Last MTL Link Failure -
Signaling Point Inaccessible (BSS 0) alarm is also reported. When this occurs, the BSS is placed
OOS.
68P02901W26-S 31-3
Nov 2007
Additional information eld Chapter 31: MTL Alarms
Table 31-1 shows the content displayed in Additional information field for this alarm.
Possible causes
• The Signal Unit Error Rate Monitor (SUERM) detected an excessive signaling error rate.
• One side of associated MMS is locked, causing the remote end (not locked) to raise the
Link Disconnected alarm. This may occur when locking any higher level device (MMS,
MSI, GPROC, DPROC).
• 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
timeslot 0 is good.
31-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 31-5
Nov 2007
Procedure Chapter 31: MTL Alarms
31-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. MTL: SL failure - All reasons - PM
Description
This statistic counts the number of times a Signaling Link (SL) has failed for all causes excluding
operator interaction using the MMI.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
An MSI failed.
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
68P02901W26-S 31-7
Nov 2007
1. MTL: MSC processor outage Chapter 31: MTL Alarms
Description
The MSC processor is OOS. This processor failure causes the MTL link to be blocked. When the
MTL link is blocked, no user signaling traffic can be exchanged.
Possible causes
The MSC processor for the remote MTP layer 2 links malfunctioned or failed.
Procedure
31-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. MTL: SL failure - Abnormal FIBR/BSNR - PM
Description
This statistic counts the number of times a Signaling Link (SL) is lost due to the detection of
an abnormal Forward Indicator Bit (FIB) caused by the desynchronization of the Backward
Sequence Number (BSN) and Forward Sequence Number (FSN).
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
Determine if any BSN and FSN are corrupted by the MSC. Perform the following procedure
to resolve the alarm.
68P02901W26-S 31-9
Nov 2007
2. MTL: SL failure - Excessive delay of ACK - PM Chapter 31: MTL Alarms
Description
This statistic counts the number of times a Signaling Link (SL) was lost because the system failed
to acknowledge a Message Signal Unit (MSU) before an internal Motorola defined timer expired.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
A signaling link failed and an MSU acknowledgment has not been sent.
Procedure
Determine if the MSU is being sent by the MSC. Perform the following procedure to resolve
the alarm.
31-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MTL: Link trafc too high
Description
Congestion is detected at either the local or remote end of the MTL affecting the flow of the
signaling traffic across MTP Layer 2.
This alarm does not necessarily indicate that there is a physical problem with the MTLs.
A network congestion problem is probably causing the MTL links to experience signaling
congestion.
System action
After the alarm is reported, flow control procedures are started at the MTP Layer 2 level to
handle congestion. These procedures ensure that user messages are stored in an MTP Layer
2 buffer for transmission when the signaling traffic subsides and returns to a normal level of
activity. When MTP Layer 2 has used all of its buffer space, user messages are discarded.
Possible causes
High traffic levels on the MTL do not allow enough time for the device driver to process frames.
68P02901W26-S 31-11
Nov 2007
Procedure Chapter 31: MTL Alarms
Procedure
31-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. MTL: SL failure - Excessive error rate - PM
Description
This statistic counts the number of times a Signaling Link (SL) was lost because the Signal Unit
Error Rate Monitor (SUERM) timer expired.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
An MSI failed.
Procedure
Determine if any MSI alarms are reported. Perform the following procedure to resolve the alarm.
68P02901W26-S 31-13
Nov 2007
4. MTL: SL failure - Excessive duration of congestion - PM Chapter 31: MTL Alarms
Description
This statistic counts the number of times a Signaling Link (SL) was lost because the remove
congestion timer expired. This congestion condition occurs on the SL when the threshold levels
establishing the capacity of the transmission or re-transmission buffer of a Message Signal
Unit (MSU) are reached.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
31-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. MTL: SL alignment failure - PM
Description
This statistic monitors the system to detect when a Signaling Link (SL) has attempted to align
with the A-Interface while the interface is OOS. This fault condition occurs when the alignment
has been lost.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
• The SL is OOS.
68P02901W26-S 31-15
Nov 2007
Procedure Chapter 31: MTL Alarms
Procedure
31-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. MTL: Number of signal units in error - PM
Description
This statistic counts the number of times that an erroneous Signaling Unit (SU) is received
on the Signaling Link (SL).
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 31-17
Nov 2007
7. MTL: SL number of negative ACKS received - PM Chapter 31: MTL Alarms
Description
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, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
31-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Determine if the messages between the BSS and the MSC are out of
sequence.
If the messages are... Then...
not out of sequence The fault condition no longer
exists. Clear the alarm.
out of sequence Go to step 2.
2 Determine if the MSC is sending the messages.
If the MSC is... Then...
sending the messages Contact the MSC to resolve the
fault and then clear the alarm.
not sending the messages Send a field representative to the
site to resolve the communication
link fault and then clear this alarm.
68P02901W26-S 31-19
Nov 2007
8. MTL: Start of remote processor outage - PM Chapter 31: MTL Alarms
Description
This statistic counts each instance that a remote processor outage is identified. This remote
processor outage occurs when signaling messages cannot be transferred.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
31-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. MTL: Number of octets retransmitted - PM
Description
This statistic counts the number of octets that the BSS has retransmitted to the MSC due
to a request by the MSC.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
Determine if the MSC requested the retransmission due to a fault. Perform the following
procedure to resolve the alarm.
68P02901W26-S 31-21
Nov 2007
10. MTL: MSUs discarded due to SL congestion - PM Chapter 31: MTL Alarms
Description
This statistic counts each instance that a Message Signal Unit (MSU) is discarded while there is
congestion on the Signaling Link (SL).
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
31-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. MTL: SL congestion events resulting in loss of MSUs - PM
Description
This statistic counts each Signaling Link (SL) congestion event which results in Message Signal
Units (MSUs) being lost.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
68P02901W26-S 31-23
Nov 2007
12. MTL: SL congestion indications - PM Chapter 31: MTL Alarms
Description
This statistic counts the number of times that a Signaling Link (SL) is congested with a high
volume of calls.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
The number of MTLs allotted for the BSS is insufficient to handle the volume of calls.
Procedure
31-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. MTL: SL failure - Excessive error rate on HSP MTL - PM
{28337}
Description
This alarm is generated when the MTP_SL_ERROR_RATE_HSP statistic threshold has been
reached. This Statistic counts the number of times a Signaling Link (SL) is lost due to the Error
internal monitoring threshold (TE) is exceeded.
Possible causes
• MSI error
• E1 line problem
Procedure
68P02901W26-S 31-25
Nov 2007
Procedure Chapter 31: MTL Alarms
31-26 68P02901W26-S
Nov 2007
Chapter
32
OMC-R Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Operations and Maintenance Centre (OMC-R) alarms are covered in this chapter and
include the following procedures:
• 30000. OMC: Download failed on page 32-5.
68P02901W26-S 32-1
Nov 2007
Procedure Chapter 32: OMC-R Alarms
• 30026. OMC: Neighbor statistics table exceeded the configured size on page 32-67.
• 30029. OMC: Active alarms exceed upper limit of 95% on page 32-72.
• 30030. OMC: Received maximum corrupt NE messages, closed OML on page 32-74.
• 30032. OMC: Resync timed out, all resync events not received on page 32-81.
• 30033. OMC: Cannot create further event logfiles in /usr/gsm/ne_data on page 32-83.
• 30038. OMC: OMC capacity ceiling violation, too many RTFs in MIB on page 32-89.
• 30039. OMC: OMC capacity ceiling violation, too many NEs in MIB on page 32-91.
• 30065. OMC: Last MTL may have gone out of service on page 32-107.
• 30069. OMC: Maximum number of RTFs in MIB above 90% of license limit on page 32-110.
• 30070. OMC: PM database is down. Unable to bring informix online on page 32-111.
32-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 30076. OMC: GSM/GPRS trace logs exceeds configured disk space on page 32-117.
68P02901W26-S 32-3
Nov 2007
Introduction to OMC-R alarms Chapter 32: 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.
Alarm reporting
32-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30000. OMC: Download failed
Description
Possible causes
68P02901W26-S 32-5
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the omc audit logs.
3 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
4 If it is a software problem, attempt to resolve the fault condition
at the OMC-R.
Continued
32-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
68P02901W26-S 32-7
Nov 2007
30001. OMC: Upload failed Chapter 32: OMC-R Alarms
Description
A software upload to the OMC-R from a BSS failed. Typically, a database object is uploaded.
Possible causes
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the omc audit logs.
3 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
Continued
32-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
[In a TTY window, use the ins_device command for a link that
is Out Of Service (OOS) to re-establish a broken X.25 link. If
the link remains OOS, go to step 5].
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
68P02901W26-S 32-9
Nov 2007
Procedure Chapter 32: OMC-R Alarms
32-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30002. OMC: File transfer failed
Description
A software raw statistics file transfer from the OMC-R failed. This is an internal alarm.
Statistics and the actual file being transferred, are the only items affected by the fault. The fault
generating this alarm is non service-affecting.
Unused OMC-R ports may generate a 30003. x25CircuitDown alarm. Also, this alarm
may be related to the GPROC 30012. Level123 Failed indicating that the X.25 circuit
software layers have failed.
Alarm category
This alarm is generated in any of the following alarm categories: Communication, Quality of
Service, Processing, Equipment, and Environmental.
When this file transfer failure appears, the OMC-R automatically attempts to transfer the files
(repeatedly) within a specified period of time until the transfer is successful or until the time
period has expired.
The default retries time period is two hours. However, the time period for file transfer retries
is user-configurable.
68P02901W26-S 32-11
Nov 2007
Possible causes Chapter 32: OMC-R Alarms
Possible causes
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the omc audit logs.
3 Check to see if there are alarms related to the Possible causes
listed. This aids in fault isolation and help lead to the resolution of
this fault condition.
4 If an X.25 link-related problem caused the file transfer to fail, check
the following X.25 items from the OMC-R:
Continued
32-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
68P02901W26-S 32-13
Nov 2007
30003. OMC: X 25 circuit down Chapter 32: OMC-R Alarms
Description
An X.25 event Virtual Circuit (VC) at the Operations and Maintenance Centre (OMC-R) failed.
This alarm is generated when a disruption (or disconnection) within the OMC-R Network
Element (NE) Interface circuitry has caused an X.25 link failure.
This alarm may be related to the GPROC and cause the OMC-R to generate 30012.
Level123Failed; this indicates that the X.25 circuit software layers have failed.
Alarm category
This alarm (30003) is actually a communication failure which is denoted as a link failure. Other
link alarms are shown as communications failures within the system, not as link failures.
The category of Communication failures is a broad classification. It may include any number of
failures within the GSM network circuitry. It is possible to have communication failures within
the GSM circuitry that are independent of one another.
Link failures
Link failure
A link failure occurs when the virtual circuit has been broken. A virtual circuit creates and
maintains the X.25 link (connection) between the OMC-R and a NE.
Network Elements are responsible for maintaining communication functionality for alarms,
events, uploads, downloads, and rlogin. If the virtual circuit link is broken, the OMC-R is
disconnected from the NEs. As a result, an X.25 link fails.
Link failures are related to the X.25 link. A link failure may be either partial or complete.
The link may be broken for one or more of the NE-related functions: alarms, events, uploads,
downloads, and rlogin.
The next section describes both types of link failures: partial and complete.
32-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Additional information eld
Partial link failure for NE-related communication occurs when one or more NE-related functions
are lost while others remain.
For example, it is possible to have a link failure for alarms while retaining rlogin capabilities.
The reason this is possible is that more than one virtual circuit may exist simultaneously where
the alarm capability may be carried by one link. The rlogin capability can continue.
Complete link failure for OMC-R to NE-related communication occurs when all NE-related
functions are lost.
For example, if the X.25 link on the OMC-R processor is stopped, every type of link to the NE
fails.
Possible causes
• The Multiple Serial Interface (MSI) or MSI link (MMS) used by the OML is locked.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Notify the System Administrator that the X.25 circuit is Out Of
Service (OOS).
Continued
68P02901W26-S 32-15
Nov 2007
Procedure Chapter 32: OMC-R Alarms
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
32-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30004. OMC: Parser disconnected too long
Description
The Performance Management (PM) parser has been disconnected from the OMC-R database
for too long a time period.
The environment variable PM_FP_DISCON_TO is used by the parser to monitor the length of
time that the parser has been disconnected from the database. After the period specified by
PM_FP_DISCON_TO has elapsed, the parser generates this alarm to inform the operator that it
(the parser) has been disconnected from the database for too long.
The parser has a default value of 10800 seconds (3 hours) and a valid range of 30 seconds to
36000 seconds. The default value is used if the environment variable is not set or an invalid
value is specified.
Possible causes
68P02901W26-S 32-17
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the System Administrator to determine when the OMC-R
database is reconnected.
3 Check the setting of the environment variable PM_FP_DISCON_TO.
If this variable has been set to a very short time period, the alarm
occurs before the maintenance procedures for the database have
been completed.
32-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
After the omc_db_maint command has been executed when reconnecting the PM parser
manually:
• Connect the Event Manager (EM) at the same time.
• Verify that it has already been connected by attempting to create a subscription list. If
this fails, reconnect the EM list manager.
68P02901W26-S 32-19
Nov 2007
30005. OMC: NE response timeout Chapter 32: OMC-R Alarms
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.
PSA verifies that BSSs are functioning correctly by periodically sending a message to each of
the BSSs connected to the OMC-R (through the Alarm Virtual Circuit) requesting that the
BSS informs the OMC-R of its current state.
If a BSS does not respond to the OMC-R request for status, the OMC-R generates a response
time out alarm, for that BSS. This alarm indicates to the operator that the BSS failed to respond
to a message requesting its status and as such may be indicative of a problem at the BSS. The
OMC-R continues to send messages periodically to the BSS requesting its status.
On receipt of a response message from the BSS, the OMC-R generates a clear event (for that
BSS) that clears the previous alarm. The PSA feature is disabled, by default.
Possible causes
• The BSS Response Timeout setting in the PSA.CNFG file is too low.
Procedure
32-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
1 In the Alarm window, check the error reason field in the alarm message to
determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a software
or hardware fault condition.
3 If it is a software problem, attempt to resolve the fault condition at the OMC-R.
• Perform a remote login to check the software processing load on the BSS
to determine whether the failure occurred at the BSS.
[In a TTY window, use the state command for the SITE device to
determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a link
failure, communication failure, a hardware (board) failure and so on.
• If a link cannot be re-established by using the INS option from the Fault
Mgt menu for a link that is OOS, send a field representative to the site
to investigate and replace the link cabling. While there, check for board
failures that may relate to the functioning of the failed link.
[If a link cannot be re-established by executing the ins_device command for
a link that is OOS, send a field representative to the site to investigate and
replace the link cabling. While there, check for board failures that may relate
to the functioning of the failed link].
68P02901W26-S 32-21
Nov 2007
Procedure Chapter 32: OMC-R Alarms
32-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
PSA verifies that BSSs are functioning correctly by periodically sending a message to each of
the BSSs connected to the OMC-R (through the Alarm Virtual Circuit) requesting that the
BSS informs the OMC-R of its current state.
The BSS responds to the OMC-R request for status, by either sending a good health indicator or
an alarm indicating that there is something wrong with the BSS.
If the BSS informs the OMC-R that it is not functioning correctly, the OMC-R generates an alarm
for that BSS. The OMC-R continues to send request for status messages periodically to the BSS.
And, when informed that the BSS has resumed normal operation, the OMC-R generates a clear
event (for that BSS) that clears the previous alarm.
Possible causes
Procedure
68P02901W26-S 32-23
Nov 2007
Procedure Chapter 32: OMC-R Alarms
1 In the Alarm window, check the error reason field in the alarm message to
determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a software
or hardware fault condition.
3 If it is a software problem, attempt to resolve the fault condition from the
OMC-R.
• Perform a remote login to check the software processing load on the BSS
to determine whether the failure occurred at the BSS.
• From the Navigation Tree, select the SITE. Choose the Display menu and
select the Contained Device option to check the individual links.
[In a TTY window, check the communication links to determine if any have
failed. Execute the state command and check the individual links].
• A wait period may be specified by the system, before the BSS begins
functioning.
• After this wait period, reset the BSS using the reset_site command.
4 If it appears that there is a hardware problem with a link or at a BSS (BSC/BTS)
site, check the operational and administrative state of the suspect equipment.
[In a TTY window, execute the state command for the SITE device to
determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a link
failure, communication failure, a hardware (board) failure and so on.
• If a link cannot be re-established by using the INS option from the Fault
Mgt menu for a link that is OOS, send a field representative to the site
to investigate and replace the link cabling. While there, check for board
failures that may relate to the functioning of the failed link.
[If an OOS link cannot be re-established by executing the ins_device command,
send a field representative to the site to investigate and replace the link
cabling. While there, check for board failures that may relate to the functioning
of the failed link].
32-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 32-25
Nov 2007
30007. OMC: PM disconnected from DB Chapter 32: OMC-R Alarms
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.
Possible causes
The parser disconnected from the OMC-R database purposely for the maintenance procedure.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
Continued
32-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 32-27
Nov 2007
30008. OMC: EM disconnected from DB Chapter 32: OMC-R Alarms
Description
The Event Manager (EM) list manager has been disconnected from the OMC-R database as
part of the database maintenance procedure.
The following conditions that apply while the EM list manager is disconnected:
• Subscription lists can be opened (and assigned to event/alarm windows).
Possible causes
The EM list manager disconnected from the OMC-R database for the maintenance procedure.
32-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine the cause(s) of
this fault condition.
3 Contact the System Administrator to determine when the OMC-R
database will be reconnected.
Continued
68P02901W26-S 32-29
Nov 2007
Procedure Chapter 32: OMC-R Alarms
After the omc_db_maint command has been executed when reconnecting the PM parser
manually, proceed with Procedure 32-10.
32-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30009. OMC: DB compression failed
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
• Quality of service.
• Processing.
• Equipment.
• Environmental.
Possible causes
68P02901W26-S 32-31
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the System Administrator to archive or remove log files
from the system.
3 Verify that the log file maintenance procedures currently in
operation comply with those recommended in the manual, Operating
Information: OMC-R System Administration (68P02901W19).
4 Review disk space allocations to determine whether there is a disk
space shortage. Determine where the disk space shortage is located.
5 If there is not enough disk space, perform the following maintenance:
32-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30010. OMC: Exceeds upper limit disk usage
Description
The upper threshold of disk partitions /root, /usr, /usr/gsm/ne_data and /home have been
exceeded at the OMC-R.
The threshold limit is set as percentage of disk used in the following configuration file and can
be modified by the System Administrator $OMC_TOP/config/global/FM_audit.CNFG.
Old log files are automatically removed by the system. The OMC-R System Administrator should
raise the value of the threshold limit and archive or remove old files from the system. The
ne_data disk partition is not intended to be used to store files belonging to individual users.
Only log files older than two days are removed during the disk partition clean up.
(Todays logs are considered to be one day old, yesterdays logs are two days old).
If the disk usage exceeds the upper limit, log files and core files are removed:
When a log file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/log_files_removed.disk partition - Unix process ID.
When a core file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/core_files_removed.disk partition - Unix process ID.
The Unix process ID refers to the process that cleans up the partition. Each partition is cleaned
up by a different process; a process is generated by fm_audit every few minutes.
The filenames are placed in /usr/gsm/current/config/fm to prevent them from being removed
during routine OMC-R maintenance. Placing these files in a different partition preserves the
information for the user.
68P02901W26-S 32-33
Nov 2007
Additional information eld Chapter 32: OMC-R Alarms
Possible causes
• The various OMC-R log files are 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
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the System Administrator to archive or remove log files
from the system.
3 Check the disk usage of the /usr partition or the partition to which
the error relates.
4 Verify that the log file maintenance procedures currently in
operation comply with those recommended in the manual, Operating
Information: OMC-R System Administration (68P02901W19).
5 Raise the value of the upper threshold limit (if lower than 90%) in
the FM_audit.CNFG file. Do not raise threshold limit above 90%.
6 Investigate the necessity of increasing the regularity (frequency)
with which the various maintenance and archive scripts are run (or
executed).
7 If there is not enough disk space, perform the following maintenance:
Continued
32-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• /usr/gsm, /usr/gsm/ne_data,
/usr/gsm/ne_data/raw_stats and /tmp -
files are removed until the disk partition usage upper threshold
is no longer exceeded. Older files are removed first, in
succession. Files less than 2 days old are not removed.
68P02901W26-S 32-35
Nov 2007
30011. OMC: Exceeds lower limit disk usage Chapter 32: OMC-R Alarms
Description
The lower threshold of disk partitions /root, /usr, /usr/gsm/ne_data and /home have been
exceeded at the OMC-R.
The threshold limit is set as percentage of disk used in the following configuration
file and can be modified by the System Administrator.
$OMC_TOP/config/global/FM_audit.CNFG
Possible causes
The lower limit threshold of disk usage was lowered in the FM_audit.CNFG file.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the System Administrator to archive or remove log files
from the system.
Continued
32-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 32-37
Nov 2007
30012. OMC: Level 1/2/3 failure Chapter 32: OMC-R Alarms
Description
Software layers 1, 2 and 3 have failed to communicate on the X.25 link to the System Processor
computer due to a faulty port.
Possible causes
32-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
• If not, go to step 4.
4 Check the X.25 ports used at the OMC-R. There should be 4
redundant ports available for use.
68P02901W26-S 32-39
Nov 2007
30014. OMC: Database exceeds upper limit Chapter 32: OMC-R Alarms
Description
The upper threshold of database usage has been exceeded by the System Processor at the
OMC-R. The database is full.
If the database space is full, action should be taken to free up space immediately. The OMC-R
may not function correctly if it cannot write into the database.
Possible causes
• The various OMC-R databases are filling up too quickly for the defined maintenance
procedures.
32-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the database usage in the System Processor database to
which the error relates.
3 Verify that the database maintenance procedures currently in
operation comply with those recommended in the manual, Operating
Information: OMC-R System Administrator (68P02901W19).
4 Raise the value of the threshold database limit (if lower than 90%).
5 Investigate the necessity of increasing the regularity (frequency)
with which the various maintenance and archive scripts are run (or
executed).
6 Review database space allocations to determine whether there is a
space shortage. Determine where the shortage is located.
7 Check the upper/lower thresholds of the databases to verify that
they are no longer exceeded.
68P02901W26-S 32-41
Nov 2007
30015. OMC: PM proxy disconnected from DB Chapter 32: OMC-R Alarms
Description
The Performance Management (PM) proxy has been disconnected from the database at
the OMC-R. This alarm is generated for the purpose of notifying the operator that system
administration must be performed to restore the proxy.
Possible causes
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the OMC-R System Administrator to reconnect the PM proxy
to the database.
32-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30016. OMC: OSI stack error
Description
A stack error within the Open Systems Interconnection (OSI) machine at the OMC-R has
occurred. This alarm is generated for the purpose of notifying the operator of the failure to send
a message or receive a reply from the Operator Services System (OSS).
Possible causes
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the OMC-R System Administrator to check the OSI machine
and investigate any hardware or software failures.
68P02901W26-S 32-43
Nov 2007
30017. OMC: CSFP download failed Chapter 32: OMC-R Alarms
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.
Possible causes
32-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the omc audit logs.
3 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
4 If it is a software problem, attempt to resolve the fault condition
at the OMC-R.
Continued
68P02901W26-S 32-45
Nov 2007
Procedure Chapter 32: OMC-R Alarms
[In a TTY window, execute the state command for the SITE
device to determine if the problem is at the BTS level].
• Check current event logs for other alarms which may indicate a
link failure, communication failure, a hardware (board) failure
and so on.
32-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30018. OMC: DB uncompression failed
Description
The activate_db utility could not uncompress or recompress a backup database for the selected
NE in $DBROOT/BSS/<BSSspecific>.
Alarm category
• Quality of Service.
• Processing.
• Equipment.
• Environmental.
68P02901W26-S 32-47
Nov 2007
Possible causes Chapter 32: OMC-R Alarms
Possible causes
• There is not enough disk space to backup the database causing the compression to fail.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine the cause of this
fault condition.
3 Check the backup database(s) for the NE on which the activate_db
utility is running.
4 If there is not enough disk space, perform the following maintenance:
32-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
68P02901W26-S 32-49
Nov 2007
Possible causes Chapter 32: OMC-R Alarms
Possible causes
• The various OMC-R databases are filling up too quickly for the defined maintenance
procedures.
There is still room in the database. However, the OMC-R System Administrator
should keep a close watch on the space used.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Check the database usage in the System Processor database to
which the error relates.
3 Verify that the database maintenance procedures currently in
operation comply with those recommended in the manual, Operating
Information: OMC-R System Administration (68P02901W19).
4 Raise the value of the threshold database limit (if lower than 90%).
5 Investigate the necessity of increasing the regularity (frequency)
with which the various maintenance and archive scripts are run (or
executed).
6 Review database space allocations to determine whether there is a
space shortage. Determine where the shortage is located.
7 Check the upper/lower thresholds of the databases to verify that
they are no longer exceeded.
32-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30020. OMC: Version query failed
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.
Denitions
Version query is a request from the OMC-R to the BSS for the current software load version
and the database level number.
Software load version is the version associated with the Code Storage and Facility Processor
(CSFP) or the Base Signaling Processor (BSP).
Database level number is a four digit hexadecimal value associated with the database at a
specific BSS site within a network. This BSS database level number is incremented each time a
change is made to a database at a specific site.
68P02901W26-S 32-51
Nov 2007
Additional information eld Chapter 32: OMC-R Alarms
A version query is initiated if there is a system configuration change. Any of the following state
changes can be related to this fault condition.
• An OML state change: to Busy-Unlocked.
• A CSFP state change: from Busy-Unlocked to another state, or from another state to
Busy-Unlocked.
The version queries are not always generated because of a fault condition.
For example, a version query is initiated for a CSFP when a CSFP transitions onto the LAN; or
when the Status CSFP window is opened through the Load Management window.
When the active BSP transitions to a Busy-Unlocked state and then, the OML comes into service.
Numerous fault conditions can cause the software version inquiry to fail. As a result, three
distinct 30020 alarms can be generated:
Possible causes
• A mismatch occurred between current CSFP software versions at the OMC-R and a BSS.
• A mismatch occurred between current software database level numbers at the OMC-R
and a BSS.
• A mismatch occurred between current CSFP software database level numbers at the
OMC-R and a BSS.
32-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
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.
• 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.
In this case, either a BSS software version or the (BSS) CSFP software version has mismatched
with the version held at the OMC-R for that BSS. Perform the following procedure to resolve
the alarm.
68P02901W26-S 32-53
Nov 2007
Procedure Chapter 32: OMC-R Alarms
1 Check the software and CSFP load versions for the specific BSS at
both the OMC-R and the BSS site.
• Check the BSS software load versions and CSFP software load
versions displayed.
2 In the Load Management window, check the BSS database level
number for the specific BSS at both the OMC-R and the BSS site.
• From the top menu bar, select > Database > Database
information from the pull-down menu.
The following table expresses OMC-R-to-BSS software mismatches and corrective action
required to resolve an FMIC version query failure fault condition.
If the OMC-R... and that specic BSS... then, before the alarm clears,
the operator must...
current software load version current software load version download the current (BSS)
for a specific BSS is correct does not match the (BSS) software version from
software version held at the the OMC-R to the BSS.
OMC-R. The same BSS version must
exist at both the OMC-R and
the BSS.
current CSFP software load current CSFP software download the current CSFP
version for a specific BSS load version does not exist, software load version from
exists and is correct because that BSC is not yet the OMC-R to the BSS.
initialized or because the BSC
is initialized, but does not
have a CSFP In Service.
32-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
In this case, a BSS software load version or the (BSS) CSFP software version or the BSS
database level number or the CSFP database level number has mismatched with the (BSS)
version held at the OMC-R. Perform the following procedure to resolve the alarm.
1 Check the software and CSFP load versions for the specific BSS at
both the OMC-R and the BSS site.
• Check the BSS software load versions and CSFP software load
versions displayed.
2 In the Load Management window, check the BSS database level
number for the specific BSS at both the OMC-R and the BSS site.
68P02901W26-S 32-55
Nov 2007
Procedure Chapter 32: OMC-R Alarms
The following table expresses OMC-R-to-BSS software mismatches and corrective action
required to resolve an OIC version query failure fault condition.
32-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
68P02901W26-S 32-57
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
3 OMC-R System Administrator: Determine why so many events
are arriving at the OMC-R. If there are a large number of similar
alarms, they could be throttled or blacklisted. See alarm handling
procedures in Chapter 3 of this manual. For details on blacklisting,
refer to the manual, OMC-R Online Help, Network Operation).
4 OMC-R System Administrator: Determine whether a slow
communication link to an MMI is causing a backlog of events.
Administrator: Check the performance of the System Processor.
32-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30022. OMC: Events discarded due to OMC overloading
Description
The pace (and quantity) of events arriving at the OMC-R is so excessive that the OMC-R is
overloaded. As a result, the event messages are now being discarded.
This alarm is generated to notify OMC-R software applications and operators that the Event
Router (group read) queue size has exceeded the established limit and is currently overloaded
with events. When officially overloaded, all of the event messages in the group read queue
are discarded without processing or logging.
This Event Router group read queue size limit is comprised of a (configurable)
threshold which may be set by the user.
Possible causes
68P02901W26-S 32-59
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this is a
software or hardware fault condition.
3 OMC-R System Administrator: determine why so many events
are arriving at the OMC-R. If there are a large number of similar
alarms, they could be throttled or blacklisted. See alarm handling
procedures in Chapter 3 of this manual. For details on blacklisting,
refer to the manual, OMC-R Online Help, Network Operation.
4 OMC-R System Administrator: Determine whether a slow
communication link to an MMI is not causing a backlog of events.
Administrator: Check the performance of the System Processor.
32-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30023. OMC: Download disabled
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.
Possible causes
68P02901W26-S 32-61
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine what caused this
fault condition.
3 Determine whether the X.25 link was being reconfigured on the
System Processor.
• If not, go to step 4.
4 Check to see if another operator has disabled downloading or has
aborted a conventional download to a NE.
5 When downloading can be restored, enable it through the Load
Management GUI.
6 Re-initiate the software download.
32-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30024. OMC: CSFP swap failed
Description
The OMC-R failed to execute a swap of a Code Storage Facility Processor (CSFP) at a BSS. The
CSFP swap was requested by the Base Station, but was not accepted and/or completed by the
OMC-R due to either a software or hardware problem.
Possible causes
• The 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
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine what caused this
fault condition.
3 Check the OMC-R connection to the BSS involved in the swap.
4 Check the BSS (software) for which the swap is being attempted to
determine why the swap is rejected or timed out.
68P02901W26-S 32-63
Nov 2007
30025. OMC: NMC agent error Chapter 32: OMC-R Alarms
Description
A Network Management Centre (NMC) mediation device (agent) has encountered either an
Open Systems Interconnection (OSI) error or an error due to one or more timeouts received
while waiting for a response from the host processor.
Depending on the type of error that has occurred, either a Communication or Processing fault
condition is being generated when the NMC attempts to interact with the OMC-R.
Possible causes
• A Communications error between two processors may have occurred: the connection
between processors is broken; or the address of the remote processor is incorrect.
• 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.
32-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine the cause(s) of
this alarm.
3 Follow a course of action highlighted for the errors featured below.
The table below suggests additional fault resolution actions for the
operator based on the reason received with this alarm. The operator
actions apply only to the reasons shown in the table.
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.
Continued
68P02901W26-S 32-65
Nov 2007
Procedure Chapter 32: OMC-R Alarms
32-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30026. OMC:
Neighbor statistics table exceeded the congured size
Description
The Error Id related to the parser has detected that the number of statistics contained in the
Neighbor Statistics table at the OMC-R exceeded the established limit.
The actual limit for the Neighbor Statistics table is set by way of the environmental
variable, PM_MAX_NEIGHBOURS. The default value for this variable is 880.
Possible causes
The neighbor statistics being generated within the system have become excessive.
68P02901W26-S 32-67
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Determine whether the environmental variable
(PM_MAX_NEIGHBOURS) is set to an appropriate level in
the system.
32-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30027. OMC: Supplemental download failed
Description
The attempted supplemental downloading to the Network Element (NE) has either been rejected
or has failed in progress at the OMC-R.
This fault condition may have occurred because the maximum number of downloads may already
be in progress. Other possibilities include that a (supplemental) download is aborted by the
operator or a COLR is received during the download causing it to fail.
Or one or more errors may have occurred in one of the software-related categories described
under the Possible causes section: X.25 link-related errors, database configuration errors,
Network Element (NE) errors, software protocol errors, or Inter-Process Communication (IPC)
errors.
This alarm applies only to BSSs using GSR2 (1.5.0.0) or previous releases.
Supplemental downloads are not performed for BSSs using GSR3 software and
beyond.
Possible causes
68P02901W26-S 32-69
Nov 2007
Possible causes Chapter 32: OMC-R Alarms
• Configuration errors.
An Error in reading timeout configuration data has occurred.
• NE errors.
The NE is requesting an object with bad version number.
• Protocol errors.
A Protocol state violation has occurred.
32-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• IPC errors.
A Failure to create IPC channel group has occurred.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Confirm that the X.25 link reconfiguration exists at the OMC-R, at
the Packet Switch and at the BSS.
3 After determining which error reason was displayed in the alarm
message, refer to the fault isolation or resolution procedures in
the manual, Operating Information: OMC-R System Administration
(68P02901W19).
68P02901W26-S 32-71
Nov 2007
30029. OMC: Active alarms exceed upper limit of 95% Chapter 32: OMC-R Alarms
Description
The number of alarms contained in the Active Alarm List (table) at the OMC-R has exceeded the
established upper threshold (limit) of 95%.
This alarm is generated when the capacity for OMC-R alarm entries on the active alarm list has
reached the upper threshold. At the upper threshold the OMC-R alarm list is 95% full. When the
list reaches 100% full, there are no more available entries in the list. Consequently, the alarm
list (table) does not have the capacity to accept any more alarms.
When this fault condition occurs, one (or more) of the alarms on the current OMC-R active
alarm list must be removed before the system can clear this alarm (30029). The active FMIC
alarms on the list are removed only as the fault conditions causing them have been resolved.
The active OIC alarms must be removed from the list by the operator after the fault conditions
causing them have been resolved.
The default for the upper threshold of the Active Alarm List table is 95% of the alarm
table capacity.
Possible causes
The number of active alarms on the OMC-R active alarm list exceeded 95%.
32-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 32-73
Nov 2007
30030. OMC: Received maximum corrupt NE messages, closed OML Chapter 32: OMC-R Alarms
Description
The Event Interface has received the maximum number of corrupt Network Element (NE)
messages from an X.25 event Virtual Circuit (VC) causing that Operations and Maintenance
Link (OML) to fail.
When this alarm occurs, the Event Interface clears the virtual circuit. Afterward, the NE opens
up a new circuit.
Under this condition, the OMC-R to Network Element (NE) Interface circuitry experiences
an X.25 link failure.
Alarm category
This alarm is actually a communication failure which is denoted as a link failure. Other link
alarms are shown as communication failures within the system, not as link failures.
The category of Communication failures is a broad classification. It may include any number of
failures within the GSM network circuitry. It is possible to have communication failures within
the GSM circuitry that are independent of one another.
Link failures
Link failure
A link failure occurs when the virtual circuit has been broken. A virtual circuit creates and
maintains the X.25 link (connection) between the OMC-R and a NE.
Network Elements are responsible for maintaining communication functionality for alarms,
events, uploads, downloads, and rlogin. If the virtual circuit link is broken, the OMC-R is
disconnected from the NEs thereby creating a link failure.
Link failures are related to the X.25 link. A link failure may be either partial or complete.
The link may be broken for one or more of the NE-related functions: alarms, events, uploads,
downloads, and rlogin.
32-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Additional information eld
Partial link failure for NE-related communication occurs when: one or more NE-related
functions are lost while others remain.
For example, it is possible to have a link failure for alarms while retaining rlogin capabilities.
The reason this is possible is that more than one virtual circuit may exist simultaneously; the
alarm capability may be carried by one link. The rlogin capability may continue.
Complete link failure for OMC-R/NE-related communication occurs when: all NE-related
functions are lost.
For example, if the X.25 link on the OMC-R processor is stopped, every type of link or connection
to the NE fails.
Possible causes
The Event Interface has received the maximum number of corrupt NE messages.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this alarm
has occurred previously. Check current event logs for other alarms
which may indicate a link failure or a communication failure.
3 Monitor this fault condition. Investigate any potentially related
software faults detected. If the alarm is automatically cleared,
discontinue fault isolation.
Continued
68P02901W26-S 32-75
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Example
If the command, x25stat -1 port1a is entered, the output generated should be like the following:
32-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Packet type TX RX
Call 2204 2672
Call accept 10 884
Restart 0 1
Restart confirm 1 0
RNR 0 0
RR 0 0
Resets 0 0
Reset confirms 0 0
Diagnostic 0 0
Interrupts 0 0
Registration 0 0
Reg confirm 0 0
Packets(total) 102566 52794
Bytes(total) 9720342 4971835
If the State of the link displayed in the output shows that the X.25 link is Connected, the link is
functional.
68P02901W26-S 32-77
Nov 2007
30031. OMC: Resync timed out, no response from NE Chapter 32: OMC-R Alarms
Description
The Event Interface (EI) has failed to return a response message from the BSS before the Resync
response timer expired. As a result, the requested resynchronization of the OMC-R failed.
Possible causes
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine
whether this alarm has occurred previously.
Check current event logs for other alarms which may indicate a
processing failure.
3 Monitor this fault condition. Investigate any potentially related
software faults detected. If the alarm clears, discontinue fault
isolation.
Continued
32-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 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.
Continued
68P02901W26-S 32-79
Nov 2007
Procedure Chapter 32: OMC-R Alarms
• Edit and search through the omc audit file for error strings.
For example, the operator could search for the strings: Error,
error, failed and so on.
• Find the specific time within the omc audit file and search for
error messages. This method can be used only if the operator
knows the actual (or an approximate) time at which the error(s)
have occurred.
The operator must make note of this information (time/error
messages) in the event it is necessary to contact MCSC for
assistance.
• If no error(s) have been found (in the omc audit file) using
either of the methods above, attempt another Resync.
32-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30032. OMC: Resync timed out, all resync events not received
Description
The Event Manager (EM) failed to send a response message indicating that EM had finished
processing the expected event messages before the Resync response timer expired.
This fault condition was generated because the EM did not receive the appropriate number of
Resync events. Consequently, the EM did not respond within the allotted time period. As a
result, the requested resynchronization of the OMC-R failed.
Possible causes
Procedure
Procedure 32-33 Resync timed out, all resync events not received.
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Review the alarm and event reports to determine whether this alarm
has occurred previously. Check current event logs for alarms which
may indicate a processing failure.
Continued
68P02901W26-S 32-81
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure 32-33 Resync timed out, all resync events not received. (Continued)
3 Repeat the OMC-R resync.
• Edit and search through the omc audit file for error strings.
For example, the operator could search for the strings: Error,
error, failed and so on.
• Find the specific time within the omc audit file and search for
error messages. This method can be used only if the operator
knows the actual (or an approximate) time at which the error(s)
have occurred.
The operator must make note of this information (time/error
messages) in case it becomes necessary to contact MCSC for
assistance.
• If no errors have been found (in the omc audit file) using either
of the methods above, go to step 5.
5 Monitor this fault condition.
32-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30033.
OMC: Cannot create further event logles 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).
Directories must be maintained and cleaned up regularly. Otherwise, the disk space used
may exceed the existing thresholds.
For more information, refer to log file maintenance procedures in the manual, Operating
Information: OMC-R System Administrator (68P02901W19). Current log file maintenance
procedures must comply with those recommended in the System Administrator manual.
In accordance with current maintenance standards, log files older than three days are
automatically removed by the system during a disk partition clean up. The OMC-R System
Administrator must archive files that are meant to be preserved for later use or remove old files
from the system if they are no longer needed.
The ne_data disk partition is not intended to be used to store files belonging to
individual users.
68P02901W26-S 32-83
Nov 2007
Additional information eld Chapter 32: OMC-R Alarms
If the disk usage exceeds the upper limit, log files and core files are removed:
When a log file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/log_files_removed.disk partition - Unix process ID.
When a core file is removed, the filename is logged and stored in:
• /usr/gsm/current/config/fm/core_files_removed.disk partition - Unix process ID.
The Unix process ID refers to the process that cleans up the partition. Each partition is cleaned
up by a different process; a process is generated by fm_audit every few minutes.
The filenames are placed in /usr/gsm/current/config/fm to prevent them from being removed
during routine OMC-R maintenance. Placing these files in a different partition preserves the
information for the user.
Possible causes
• The number of event log files present (in the directory) is excessive due to the lack of
regular directory and file (clean up) maintenance.
• The current event traffic is so excessive that the number of event logs being created is
higher than allowed causing the directory to fill up.
Procedure
1 In the Alarm window, check the error reason field in the alarm
message to determine the cause(s) of this alarm.
2 Contact the System Administrator to archive or remove log files
from the system.
Continued
32-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 32-85
Nov 2007
30035. OMC: Advisory detected Chapter 32: OMC-R Alarms
Description
These are failures that are recovered by the system and require no operator action. No alarm
is generated. Instead these autonomous recovery events are provided in the form of advisory
warnings to the operator.
These advisory warnings can highlight potential problems that may resurface as more serious
fault conditions.
Possible causes
N/A
Procedure
32-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 resurface as more
serious fault conditions.
Possible causes
N/A
Procedure
68P02901W26-S 32-87
Nov 2007
30037. OMC: UPS condition Chapter 32: OMC-R Alarms
Description
Support for the Uninterrupted Power Supply (UPS) is an optional feature for the OMC-R
hardware. UPS conditions are reported to the OMC-R using alarms. The alarm severity is
dependent on the alarm. One of three alarms are reported to the OMC-R, as shown in Table 32-1.
Alarm Severity
OMC now powered by mains Clear
OMC now powered by the UPS Major
UPS battery low condition signaled Critical
Possible causes
Procedure
32-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30038. OMC: OMC capacity ceiling violation, too many RTFs in MIB
Description
The number of RTFs in the MIB has exceeded the number allowed by the OMC-R license.
The alarm has a severity level of Major when the number of RTFs is greater than the RTF
Threshold: 90% of the RTF Limit as controlled by the license.
The alarm has a severity level of Critical when the number of RTFs is greater than the RTF
Limit as controlled by the license. When the alarm has critical status, a GUI dialogue message
appears saying that The OMC-R is exceeding its licensed RTF limit.
A GUI message appears with the text The OMC is exceeding its licensed RTF limit.
Possible causes
The number of RTFs on the network exceeds the number permitted by the license.
68P02901W26-S 32-89
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
Check the number of RTFs on the MIB using the script: /usr/gsm/cur-
rent/sbin/Count_NEs_and_RTFs. Perform the following procedure to resolve the alarm.
Procedure 32-38 OMC capacity ceiling violation, too many RTFs in MIB
If... Then...
The number of RTFs on the MIB Reduce the number of RTFs in the
exceeds the license MIB.
The number of RTFs on the MIB Check the installation of the
does not exceed the license license and reinstall the
license if necessary. Refer to
the manual, Installation and
Configuration: OMC-R Clean
Install (68P02901W47). If there
are problems with the license
contact Motorola.
32-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30039. OMC: OMC capacity ceiling violation, too many NEs in MIB
Description
The number of Network Elements (NEs) in the MIB has exceeded the number allowed by the
OMC-R license.
A GUI message appears with the text The OMC is exceeding its licensed NE limit.
Possible causes
The number of NEs on the network exceeds the number permitted by the license.
68P02901W26-S 32-91
Nov 2007
Procedure Chapter 32: OMC-R Alarms
Procedure
Check the number of NEs on the MIB using the script: /usr/gsm/cur-
rent/sbin/Count_NEs_and_RTFs. Perform the following procedure to resolve the alarm.
Procedure 32-39 OMC capacity ceiling violation, too many NEs in MIB
If... Then...
The number of NEs on the MIB Reduce the number of NEs in the
exceeds the license MIB.
The number of NEs on the MIB Check the installation of the
does not exceed the license license and reinstall the license
if necessary. Refer to Installation
and Configuration: OMC-R Clean
Install (68P02901W47). If there
are problems with the license
contact Motorola.
32-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30050. OMC: Solaris 2 hardware failure
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.
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.
If a Solaris 2 hardware component is detected as OOS in the current FM Hardware audit and
the name of that component is not listed in the /usr/gsm/current/config/fm/down file, this
alarm (30050) is generated.
If the name of that OOS component is listed in the /usr/gsm/current/config/fm/down file, this
means that the hardware component is still OOS. In this case, an alarm (30050) would have
been generated previously. Consequently, a second alarm is not generated for that same OOS
component.
This (30050) alarm remains active until the faulty hardware has been repaired or replaced
onsite. After the Solaris 2 hardware resumes functioning, this alarm is automatically cleared
from the system.
68P02901W26-S 32-93
Nov 2007
Additional information eld Chapter 32: OMC-R Alarms
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 default setting for the frequency of the FM Hardware audit is 2 minutes. Therefore, the FM
Hardware audit is automatically generated every 2 minutes.
The following is displayed in the additional information in the output for this alarm.
The Solaris 2 hardware components below are the only ones supported at the OMC-R.
Consequently, these are the only OOS components that can be displayed in the 30050 alarm
output.
Text displayed in the Additional information eld Description of the faulty Solaris 2
hardware component
cpu(x) (in SBUS slot (y)) is DOWN The CPU, where (x) is the number of the CPU.
d(x) is DOWN The hard disk, where (x) is the number of the
disk.
hih(x) is DOWN The X.25 card which is the High Speed Serial
Interface/Serial Bus (SBUS) card. Where (x)
is the number of the card and y is the number
of the slot where the SBUS is located.
32-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
The OOS Solaris 2 hardware component is shown at the end of the third line of output as:
hih2 is DOWN.
#4 - SEEN - *NONE*.
equipmentFailureEvent - OMC - OMC0: 2 Sol2HsisHih2 - 17/02/1998 11:45:38.
[30050] Solaris2 hardware Failure - FMIC - Critical - hih2 is DOWN
68P02901W26-S 32-95
Nov 2007
30051. OMC: Corrupt NE le Chapter 32: OMC-R Alarms
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.
Possible causes
Procedure
Manually inspect the file and verify the file format is correct.
32-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30052. OMC: Corrupt SITE le
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.
Possible causes
Procedure
Manually inspect the file and verify the file format is correct.
68P02901W26-S 32-97
Nov 2007
30058. OMC: Call success rate below threshold Chapter 32: OMC-R Alarms
Description
The Call Success Monitor has detected a cell where the callSuccessRate statistic is below
the CALL_SUCCESS_THRESHOLD.
In a multiple carrier, one or more carriers may not be processing traffic, but handover
is possible. The architecture uses degradation in cell call success rate to determine a
problem.
Possible causes
• Switch problem.
There are a number of different reasons that can cause the decline in call success
rate other than a carrier problem.
32-98 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 32-99
Nov 2007
30059. OMC: No calls on cell Chapter 32: OMC-R Alarms
Description
The Call Success Monitor has detected a cell where there are no call setups, but call setups are
expected on that cell. That is, the cell is not a dummy and the cell is not barred.
Possible causes
The cell is a sleeping cell: no call setups are possible on the whole cell although handover is
possible.
Procedure
32-100 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30060. OMC: No activity in timeslot
Description
The Call Success Monitor has detected one or more timeslots on an RTF where there is no traffic.
Possible causes
One or more timeslots within the RTF are not processing traffic: neither call origination nor
handovers.
Procedure
68P02901W26-S 32-101
Nov 2007
30061. OMC: CPU load exceeds lower limit Chapter 32: OMC-R Alarms
Description
The lower threshold limits for CPU load have been exceeded by the System Processor at the
OMC-R. Current CPU load is high and requires that CPU activity is reduced by expanding the
lower CPU load limit. This fault condition could occur if the CPU load is high. Immediate
action must be taken to reduce CPU activity. If the CPU becomes overloaded, the OMC-R
may not function correctly.
Possible causes
• The CPU load on the System Processor has reached its maximum capacity.
Procedure
32-102 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30062. OMC: CPU load exceeds upper limit
Description
The upper threshold limit for CPU load has been exceeded by the System Processor at the
OMC-R. The CPU is completely overloaded. Immediate action must be taken to reduce CPU
activity.
Possible causes
• The CPU load on the System Processor has reached maximum capacity.
Procedure
68P02901W26-S 32-103
Nov 2007
30063. OMC: Memory usage exceeds lower limit Chapter 32: OMC-R Alarms
Description
The lower threshold limits for memory usage have been exceeded by the System Processor at
the OMC-R. Current memory usage is high and requires that the memory is made available by
expanding the lower memory usage limit. This fault condition could occur if the memory usage
is high. Immediate action must be taken to free up memory. If memory usage is too high, the
OMC-R may not function correctly.
The memory usage exceeds upper limit alarm and indicates that the memory is
exhausted.
Possible causes
• The memory usage on the System Processor has reached its maximum capacity.
32-104 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 32-105
Nov 2007
30064. OMC: Memory usage exceeds upper limit Chapter 32: OMC-R Alarms
Description
The upper threshold for memory usage has been exceeded by the System Processor at the
OMC-R. Memory is completely exhausted. Immediate action must be taken to free up memory.
Possible causes
Procedure
32-106 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30065. OMC: Last MTL may have gone out of service
Description
When the OML goes down, the OMC checks the state of the MTLs for the BSS in question. If the
only MTLs in a Busy Unlocked state are associated with this OML, then the alarm is generated.
Possible causes
The OML link to the BSS has gone down so the OMC no longer receives alarms. If the only MTLs
in a Busy Unlocked state are on this OML the alarm is generated.
Procedure
1 Check that the MTLS on this OML are not all Out of Service.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 32-107
Nov 2007
30066. OMC: Database unable to allocate fragment Chapter 32: OMC-R Alarms
Description
This alarm is raised by the Performance Management statistics parser if it finds it is unable to
insert statistics into the PM database because the overnight database maintenance has failed
to prepare a table fragment. The parser has stopped inserting new statistics and stores all
statistics files with a .no_db_storage extension until the problem is corrected.
Possible causes
Procedure
32-108 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30067. OMC: No PM database fragment available
Description
This alarm is raised by the pm_purge_check utility that runs every hour to check that the
database maintenance has run correctly. The alarm indicates that the database maintenance
did not complete successfully and that statistics parsing stops at midnight if no corrective
action is taken.
Possible causes
Procedure
68P02901W26-S 32-109
Nov 2007
30069. OMC: Maximum number of RTFs in MIB above 90% of license limit Chapter 32: OMC-R Alarms
Description
A warning message is displayed to indicate that the number of RTFs in the MIB has exceeded
90% of the Capacity Limit defined by the RTF License.
Possible causes
N/A
Procedure
N/A
32-110 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30070. OMC: PM database is down. Unable to bring informix online
Description
This alarm is raised by omc_db_maint program that runs every night to maintain the Performance
Management database. The alarm indicates that omc_db_maint brought Informix engine
offline and was unable to bring back the instance online. Until corrective action is taken, the
Performance Management database is not available for any application like parser and reports.
Possible causes
Unknown.
Procedure
Continued
68P02901W26-S 32-111
Nov 2007
Procedure Chapter 32: OMC-R Alarms
32-112 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30071. OMC: License audit not available alarm
Description
This alarm is raised by the License Audit tool that is triggered by the OMC-R software at
preconfigured time intervals. The alarm indicates that either no license audit is installed on the
local OMC-R or that the license audit installed on the local OMC-R is not configured.
Possible causes
The license audit is either not installed and/or not configured on the local OMC-R.
Procedure
68P02901W26-S 32-113
Nov 2007
30072. OMC: License le not available alarm Chapter 32: OMC-R Alarms
Description
This alarm is raised by the License Audit tool that is triggered by the OMC-R software at
preconfigured time intervals. The alarm indicates that no license file is installed on the local
OMC-R.
Possible causes
Procedure
32-114 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30073. OMC: License violation alarm
Description
The alarm indicates that the RTF usage for any purchasable feature has exceeded the license
agreement.
Possible causes
RTF usage for any purchasable feature has exceeded the license agreement.
Procedure
1 Once the usage for the purchasable feature is within the license agreement,
the next invocation of FMON, either manually or through the OMC-R
software, will clear the alarm.
2 The event actualRTFUsageEvent is displayed.
68P02901W26-S 32-115
Nov 2007
30075. OMC: Invalid license le alarm Chapter 32: OMC-R Alarms
Description
The alarm indicates that the license file is invalid or syntactically incorrect.
Possible causes
Procedure
32-116 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30076. OMC: GSM/GPRS trace logs exceeds congured disk space
Description
The alarm indicates that the trace logs exceeds the configured disk space.
Possible causes
Procedure
68P02901W26-S 32-117
Nov 2007
50000/50001/50002 OMC: Field engineer password to be changed Chapter 32: OMC-R Alarms
{27508}
Category: OMC
Description
This alarm is generated when the field engineer's password has not been changed for the
specified number of days.
Possible causes
Procedure
32-118 68P02901W26-S
Nov 2007
Chapter
33
OML Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Operation and Maintenance Link (OML) alarms are covered in this chapter and include
the following procedures:
• 0. OML: Invalid received frames - PM on page 33-3.
68P02901W26-S 33-1
Nov 2007
Introduction to OML alarms Chapter 33: OML Alarms
OML alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the
Operation and Maintenance Link (OML) alarms.
33-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. OML: Invalid received frames - PM
Description
This statistic counts the number of the invalid frames received on the X.25/LAPD link.
For further information, refer to the OML statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 33-3
Nov 2007
Procedure Chapter 33: OML Alarms
33-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. OML: FRMR frames - PM
Description
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, refer to the OML statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 33-5
Nov 2007
Procedure Chapter 33: OML Alarms
33-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. OML: Expiration of N2 - PM
2. OML: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates that the maximum number of link alignment retries has been attempted
without success.
For further information, refer to the OML statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 33-7
Nov 2007
Procedure Chapter 33: OML Alarms
33-8 68P02901W26-S
Nov 2007
Chapter
34
PBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the Processor Bus (PBUS) alarm 254. PBUS: Device failure on page 34-3.
68P02901W26-S 34-1
Nov 2007
Introduction to PBUS alarms Chapter 34: PBUS Alarms
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) or Transcoder (XCDR).
34-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. PBUS: Device failure
Description
Possible causes
The LANX card performing arbitration for the MCAP bus failed.
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 34-3
Nov 2007
Procedure Chapter 34: PBUS Alarms
34-4 68P02901W26-S
Nov 2007
Chapter
35
PCU Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Packet Control Unit (PCU) alarms are covered in this chapter and include the following
procedures:
• 0. PCU: Last GSL failed on page 35-3.
68P02901W26-S 35-1
Nov 2007
Introduction to PCU alarms Chapter 35: PCU Alarms
PCU alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the
Packet Control Unit (PCU) device.
35-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PCU: Last GSL failed
Description
The last GSL between the PCU and the BSC failed.
System action
Possible causes
68P02901W26-S 35-3
Nov 2007
Procedure Chapter 35: PCU Alarms
Procedure
1 Determine if there are any GSL alarms associated with the PCU
that reported the alarm.
If there are... Then...
no GSL alarms Go to step 2.
GSL alarms Resolve the GSL alarms. After
resolving the GSL alarms, go to
step 3.
2 Reset the PCU.
3 Determine if the alarm cleared.
If the alarm... Then...
cleared The fault condition no longer
exists. No further action is
required.
did not clear Send a field representative to the
site to replace the PCU processor
board.
35-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. PCU: PCU audit failure
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 35-1.
Possible causes
• The GSLs between the PCU and the BSC are faulty, but remain in service.
68P02901W26-S 35-5
Nov 2007
Procedure Chapter 35: PCU Alarms
Procedure
1 Determine if there are any GSL alarms associated with the PCU
that reported the alarm.
If there are... Then...
no GSL alarms Go to step 2.
GSL alarms Resolve the GSL alarms. After
resolving the GSL alarms, go to
step 3.
2 Determine if this is a recurrence of this alarm.
If this is... Then...
a recurrence Send a field representative to the
site to replace the DPROC/MPROC
processor board.
not a recurrence Go to step 3.
3 Clear the alarm.
4 Reset the PCU.
35-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. PCU: Cell mapping failure
Description
The PCU has failed to acknowledge the cell mapping updates due to a failure in mapping cells
between PCUs.
Possible causes
Procedure
1 The system action of resetting the PCU should resolve the problem. If the
alarm continues to occur, check state of BSC -> PCU communication links as
there is some instability in the communication path between PCU and BSC,
or the PCU is failing without the GSLs going OOS.
2 If the system action does not bring the PCU INS, there might be a problem at
the PCU itself, so issue a reset hard command at this PCU's EMON prompt.
68P02901W26-S 35-7
Nov 2007
51. PCU: Software patch installation failure Chapter 35: PCU Alarms
Description
Possible causes
Procedure
When the alarm occurs, the BSS backs out the patch level to 0 within BSS.
35-8 68P02901W26-S
Nov 2007
Chapter
36
PPB Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the PPB alarm 0. PPB: PCI bridge failure on page 36-3.
68P02901W26-S 36-1
Nov 2007
Introduction to PPB alarms Chapter 36: PPB Alarms
PPB alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with
the PPB device.
36-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PPB: PCI bridge failure
Description
The bridge used to communicate to the redundant side of the cage has failed.
Possible causes
Procedure
68P02901W26-S 36-3
Nov 2007
Procedure Chapter 36: PPB Alarms
36-4 68P02901W26-S
Nov 2007
Chapter
37
PPROC alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter describes the alarm and OMC-R troubleshooting procedures associated with
the PPROC alarms.
68P02901W26-S 37-1
Nov 2007
0. PPROC: Processor Communications Failure Chapter 37: PPROC alarms
{28351}
Category: Equipment
Description
This is an alarm which indicates that the communication with the baseboard is not possible.
Possible causes
• Processor failure.
• Firmware failure.
Procedure
If the PPROC does not come back into service then replace the whole board.
37-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 9. PPROC: PPROC Reset Detected
{28351}
Description
Possible causes
Failure of processor.
Procedure
If the PPROC does not come back into service then replace the U-DPROC2
board.
68P02901W26-S 37-3
Nov 2007
22. PPROC: SWFM Indication Chapter 37: PPROC alarms
{28351}
Description
Possible causes
Procedure
37-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 39. PPROC: Software failure
{26740}
Category: Processing
Description
Additional information field is the raw binary data of SWFM message header.
Possible causes
Procedure
68P02901W26-S 37-5
Nov 2007
239. PPROC: Process safe test Audit Failure Chapter 37: PPROC alarms
{26740}
Category: Communication
Description
This is an alarm which indicates a software process which exists on the device has failed an audit.
Byte Denition
first the process ID of the process being
audited.
second and third contain the CPU number.
fourth the percentage of CPU utilization by the
process being audited.
Possible causes
37-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 37-7
Nov 2007
Procedure Chapter 37: PPROC alarms
37-8 68P02901W26-S
Nov 2007
Chapter
38
PSI Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Packet Subrate Interface (PSI) alarms are covered in this chapter and include the following
procedures:
68P02901W26-S 38-1
Nov 2007
Procedure Chapter 38: PSI Alarms
38-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PSI: Re-Initialized Unexpectedly
{26740}
Description
This alarm is generated when the PSI board is unexpectedly re-initialized or reset.
Possible causes
• Software reset.
Procedure
68P02901W26-S 38-3
Nov 2007
1. PSI: Hard Reset Chapter 38: PSI Alarms
{26740}
Description
Possible causes
• A software reset.
Procedure
If... then...
the PSI fails INS the device and attempt to bring it back
to become B-U into service.
(Busy-Unlocked)
the device still fails replace the PSI board.
to become B-U
38-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. PSI: Watchdog timer expired
{26740}
Description
This alarm is generated when the PSI board watchdog timer has timed out.
Possible causes
Procedure
68P02901W26-S 38-5
Nov 2007
3. PSI: Clock B signal loss Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when the PSI detects the TDM clock B failure, that is, when the clock B
signals of the PSI board goes Out Of Sync (OOS).
Possible causes
Procedure
1 If... then...
the alarm is check the GCLK - peripheral boards
reported on other communications path for faults and take
boards corrective action.
2 If the GCLK - replace the PSI module.
peripheral boards
are not faulty
38-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. PSI: Clock A signal loss
{26740}
Description
This alarm is generated when the PSI detects the TDM clock A failure, that is, when the clock A
signals of the PSI board go OOS.
Possible causes
Procedure
1 If... then...
the alarm is check the GCLK - peripheral boards
reported on other communications path for faults and take
boards corrective action.
2 If the GCLK - replace the PSI module.
peripheral boards
are not faulty
68P02901W26-S 38-7
Nov 2007
5. PSI: Assigned timeslot counter underow Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when fewer switch-bound timeslots than the ones allocated in the ATC
register are driven on the TDM bus.
Possible causes
Procedure
If... then...
the PSI fails to INS the device and attempt to
become B-U bring it back into service.
the device still fails replace the PSI board.
to become B-U
38-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. PSI: Assigned timeslot counter overow
{26740}
Description
This alarm is generated when more switch-bound timeslots are driven on the TDM bus than the
ones allocated in the ATC register.
Possible causes
Procedure
If... then...
the PSI fails to ins the device and attempt to bring it
become B-U back into service.
the device still fails replace the PSI board.
to become B-U
68P02901W26-S 38-9
Nov 2007
7. PSI: TDM parity error Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a parity error is detected on the in-bound TDM highway.
Possible causes
Procedure
If... then...
the PSI fails to INS the device and attempt to bring it
become B-U back into service.
the device still fails replace the PSI board.
to become B-U
38-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 11. PSI: DSP 0 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 0 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 0.
Procedure
68P02901W26-S 38-11
Nov 2007
12. PSI: DSP 1 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 1 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 1.
Procedure
38-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 13. PSI: DSP 2 Audit Failure
{26740}
Category: Equipment
Description
This alarm is generated when a message sent to DSP 2 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 2.
Procedure
68P02901W26-S 38-13
Nov 2007
14. PSI: DSP 3 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 3 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 3.
Procedure
38-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. PSI: DSP 4 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 4 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 4.
Procedure
68P02901W26-S 38-15
Nov 2007
16. PSI: DSP 5 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 5 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 5.
Procedure
38-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 17. PSI: DSP 6 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 6 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 6.
Procedure
68P02901W26-S 38-17
Nov 2007
18. PSI: DSP 7 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 7 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 7.
Procedure
38-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 19. PSI: DSP 8 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 8 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 8.
Procedure
68P02901W26-S 38-19
Nov 2007
20. PSI: DSP 9 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 9 on a PSI board to check the DSP status
fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Failure of DSP 9.
Procedure
38-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. PSI: DSP 10 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 10 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
68P02901W26-S 38-21
Nov 2007
22. PSI: DSP 11 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 11 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
38-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 23. PSI: DSP 12 Audit Failure
{26740}
Description
This alarm is generated when a message sent to DSP 12 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
68P02901W26-S 38-23
Nov 2007
24. PSI: DSP 13 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 13 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
38-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 25. PSI: DSP 14 Audit Failure
{26740}
Category: Equipment
Description
This alarm is generated when a message sent to DSP 14 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
68P02901W26-S 38-25
Nov 2007
26. PSI: DSP 15 Audit Failure Chapter 38: PSI Alarms
{26740}
Description
This alarm is generated when a message sent to DSP 15 on a PSI board to check the DSP
status fails.
Additional data is of 2 bytes: Byte 1 = Physical DSP ID, Byte 2 = Alarm originating entity.
Possible causes
Procedure
38-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 224. PSI: Safe test Audit Failure
{26740}
Description
This alarm is generated when the BSS detects that the PSI does not respond to the interrogation
by an external process.
Possible causes
Procedure
If the PSI board does not become B-U or there is an excessive recurrence of
this alarm, replace the PSI board.
68P02901W26-S 38-27
Nov 2007
231. PSI: TDM interface conguration failure Chapter 38: PSI Alarms
{26740}
Category: Processing
Description
This alarm is generated when the BSS detects that an active PSI device is not configured for the
designated TDM highway.
Possible causes
Procedure
If..... Then...
the alarm is received along with follow the instructions for the corresponding
PSI alarms 254, 0 or 1 alarm.
the PSI fails to become B-U INS the device and attempt to bring it back
into service.
38-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 232. PSI: Processor bus communication failure
{26740}
Description
This alarm is generated when the BSS detects that a communication link between the PSI board
and the GPROC board through the MCAP bus is lost.
Possible causes
Procedure
If... then...
the PSI fails to become INS the device and attempt to bring it
B-U back into service.
the device still fails to replace the PSI board.
become B-U
68P02901W26-S 38-29
Nov 2007
Procedure Chapter 38: PSI Alarms
38-30 68P02901W26-S
Nov 2007
Chapter
39
PSP Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The PCU System Processor (PSP) alarms are covered in this chapter and include the following
procedures:
• 0. PSP: Communication failure on page 39-3.
68P02901W26-S 39-1
Nov 2007
Introduction to PSP alarms Chapter 39: 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 39-1.
FRU Description
Motorola MPROC A Motorola master system processor board.
Unknown MPROC A generic master system processor board.
39-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. PSP: Communication failure
Description
The ACTIVE PSP is no longer able to communicate with the STANDBY PSP, also the redundant
MPROC is missing. This alarm is either cleared when the PCU software re-establishes
communication with the PSP and comes back in service or when the PCU software detects that
a redundant MPROC has been inserted in the corresponding slot.
If, at a future point in time, the PCU resets without a standby PSP the recovery time will
be greater than if the standby were present. Furthermore, if the active PSP fails and is no
longer usable, the PCU does not return to service until a site visit is made to replace the failed
MPROC/HSC hardware.
Possible causes
68P02901W26-S 39-3
Nov 2007
Procedure Chapter 39: PSP Alarms
Procedure
39-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 22. PSP: SWFM indication
Description
The system has detected a software processing error (SWFM) for a PSP.
SWFM is a debugging tool for Motorola engineering and is reported only if the SWFM
indication is turned on at the BSS MMI.
Additional information
The Additional information field includes process information that is useful only to the
programmers.
Possible causes
Procedure
68P02901W26-S 39-5
Nov 2007
39. PSP: Software failure Chapter 39: PSP Alarms
Description
This alarm indicates that the PSP has experienced a non recoverable software error.
The Additional information field includes process information that is useful only to the
programmers.
Possible causes
Procedure
39-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 39-7
Nov 2007
239. PSP: Process safe test audit failure Chapter 39: PSP Alarms
Description
The PSP failed a process safe test audit. The process safe test audit verifies the proper operation
of internal software processes. This alarm is generated if the system does not receive a response
to an audit from a specified PSP processor within the GPRS system.
The Additional information field includes nine bytes containing process information, as shown
in Table 39-2. Bytes one to eight are useful only to the programmers. Byte nine is the error
code for the alarm.
Possible causes
39-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
When the audit failure reason is 2 (when the board is not reset), clear the alarm
manually by resetting the PSP on/off hours as long as GPRS service is being properly
provided.
68P02901W26-S 39-9
Nov 2007
Procedure Chapter 39: PSP Alarms
39-10 68P02901W26-S
Nov 2007
Chapter
40
RSL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Radio Signaling Link (RSL) alarms are covered in this chapter and include the following
procedures:
• 0. RSL: Invalid received frames - PM on page 40-3.
68P02901W26-S 40-1
Nov 2007
Introduction to RSL alarms Chapter 40: RSL Alarms
RSL alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the
Radio Signaling Link (RSL) device.
The specific GPROC device type used depends on system configuration. The Link Control
Processor (LCP) and the Radio System Link Processor (RSLP) control the RSL functionality.
40-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. RSL: Invalid received frames - PM
Description
This statistic counts the number of the invalid frames received on the LAPD link.
For further information, refer to the RSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 40-3
Nov 2007
Procedure Chapter 40: RSL Alarms
40-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. RSL: FRMR frames - PM
Description
This statistic counts the number of the frames on the LAPD link that were rejected because
the frames were not correctable.
For further information, refer to the RSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 40-5
Nov 2007
Procedure Chapter 40: RSL Alarms
40-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. RSL: Expiration of N2 - PM
2. RSL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates that the maximum number of link alignment retries has been attempted
without success.
For further information, refer to the RSL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 40-7
Nov 2007
Procedure Chapter 40: RSL Alarms
40-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. RSL: Link disconnected
Description
An RSL disconnected on the MMS. No signaling 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 is raised as
the primary alarm and you will not see an RSL10 alarm.
• If MMS thresholds are configured such that the RSL fails before the MMS
failure is signaled in software, you will first see the RSL 10 alarm, followed by
the MMS alarm.
• If the RSL fails due to a layer 2 issue only (LAPD) and the MMS is OK, then
you will see the RSL alarm only. The operator can use the OMC to determine
any devices present on the MMS (including RSLs) by clicking the MMS alarm
at the OMC.
Alarm context
The context in which this alarm is generated determines the level of complexity of the isolation
and resolution of this fault condition. This situation is more complex.
The following factors have the greatest affect on the complexity of the tasks required: the site
configuration, other alarms occurring, and the RSL link availability.
68P02901W26-S 40-9
Nov 2007
Additional information eld Chapter 40: RSL Alarms
When this alarm occurs, the site configuration determines the initial approach to isolating the
fault condition. See a description of each of the various site configurations in a forthcoming
section.
In addition, this alarm is generated concurrently with other major alarms related to the RSL link
failure. Therefore, associated fault conditions must first be prioritized and then investigated.
In the event this alarm is generated for an RSL link that happens to be the last available link for
service to a remote site, the (remote) site goes Out Of Service (OOS). The following alarm is
generated: 0. Site: Last RSL Link Failure.
If the last RSL link has failed, the resulting fault condition is one of the most complex. Only an
experienced operator should attempt to resolve this fault condition.
Refer to CCITT Blue Book, Q.921 for details regarding the Data Link Layer.
Table 40-1 shows the content displayed in the Additional information field for this alarm.
40-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• One side of associated MMS is locked, causing the remote end (not locked) to raise the
Link Disconnected alarm. This may occur when locking any higher level device (MMS,
MSI, GPROC, DPROC).
• 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
timeslot 0 is good.
For fault isolation and diagnostics, it is critical to determine which BSC-to-remote BTS site
configuration is present at the site receiving the alarms.
• Fork configuration.
A star (or spoke) consists of many BTS sites. Each BTS site is connected directly to the BSC by
E1 links. A minimum of one E1 link (MMS) is required for each BTS site.
Multiple MMSs can be used to support additional traffic capacity or redundancy. A single BTS
site can have a maximum of ten MMSs. The Star (spoke) is treated as multiple open-ended daisy
chains with one BTS site per chain.
A loop chain consists of many BTSs connected together in a chain with at least a single E1 link
between each remote BTS site. Multiple E1 links (MMSs) can be used to support additional
traffic capacity or redundancy. A single BTS site can have a maximum of ten MMSs. There are
two types of loop configurations: open and closed.
68P02901W26-S 40-11
Nov 2007
BSC-to-BTS topology Chapter 40: RSL Alarms
Open loop
Only one end of the (BTS) chain terminates at the BSC. The other end of the chain terminates at
a BTS site. An open loop can have a maximum of 10 remote BTS sites. In this configuration,
if a BTS site goes Out Of Service (OOS), all BTS sites downstream from the failed BTS, go
OOS as well.
Closed loop
Both ends of the (BTS) chain terminate at the BSC. A closed loop can have a maximum of
10 remote BTS sites. In this configuration, if a BTS site goes OOS, all other BTS sites in the
chain remain INS.
Fork Conguration
A fork consists of either a single BTS site or chain of BTS sites connected to an intermediate
BTS site in a chain that terminates at the BSC. Fork BTS sites are connected with at least a
single E1 link between each remote BTS site.
Multiple E1 links (MMSs) can be used to support additional traffic capacity or redundancy. A
single BTS site can have a maximum of ten MMSs. The fork can be open-ended or have a
redundant loop back to a chain that terminates at the BSC.
BSC-to-BTS topology
After determining the site configuration, record the following system characteristics before
beginning fault resolution.
System characteristics
The BSC-to-remote BTS topology is specified in terms of the continuous traffic routes between
the BSC and a terminating remote BTS site. This continuous route includes all intermediate
BTSs between the BSC and the remote BTS site generating the fault condition.
A particular traffic route is specified by a unique PATH device. (Every remote BTS site in the
network must be equipped with at least one PATH device). A PATH device specifies which SITE
devices and associated MSI/MMS devices define the route. And therefore, which particular
E1 link is used between each site.
Every remote BTS site in the network must be equipped with at least one RSL. The RSL carries
signaling traffic between the BSC and the remote BTS site. A maximum of eight RSLs can be
equipped between the BSC and a BTS site. The additional RSLs provide signaling traffic load
sharing (and depending on system configuration) may provide redundancy. An RSL for a specific
site is associated with a PATH device that terminates at that same site.
40-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• An MMS may be is OOS because an associated MSI, XCDR, or Network Interface Unit
(NIU) is OOS.
In the case of a BTS site that is part of an open loop or open-ended fork, the loss of RSLs at a
site may be caused by equipment failure downstream from the failed BTS site reporting the
alarm. (Recall that in this configuration, if a BTS site goes OOS, all BTS sites downstream
from the failed BTS, go OOS as well).
Procedure
1 Refer to several current alarm report logs to determine whether the same
RSL link has reported this specific RSL alarm repeatedly.
Continued
68P02901W26-S 40-13
Nov 2007
Procedure Chapter 40: RSL Alarms
Continued
40-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 40-15
Nov 2007
Procedure Chapter 40: RSL Alarms
40-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Wait for 10 minutes before continuing with this procedure. After waiting, if the alarm is cleared
and the RSL connection is re-established, fault isolation and diagnostics is not necessary. If the
connection is not re-established, the system goes into a Continuous Retry mode in which case,
the system attempts to re-establish the link an infinite number of times.
68P02901W26-S 40-17
Nov 2007
11. RSL: LAPD protocol error Chapter 40: RSL Alarms
Description
The RSL detected a LAPD protocol error due to a problem on one of the E1 links. Calls may
be lost.
The contents of the Additional information field are shown in Table 40-2.
40-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
The LAPD Error code included in the Additional information field corresponds to a possible
cause for the alarm, as shown in Table 40-3.
Procedure
68P02901W26-S 40-19
Nov 2007
Procedure Chapter 40: RSL Alarms
40-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Further tests
If the above procedure is not sufficient to isolate the problem, perform the following actions.
1 Carry out an end-to-end link quality test for all the 32 Timeslots using the
standard link test patterns. Ensure that over a 24 hour period, frequency,
BER and Code errors jitter and wander are within specifications.
2 Use a LAPD Q.921 protocol tester on the RSL timeslot over a larger span
of the PDU.
3 The maximum length of the LAPD error string (including the header string)
allowed by Motorola is 576 bytes.
4 Use ECT to find the E1 links where the maximum number of alarms are raised
and isolate them. Check the recent statistics history for RSL, MMS and the
link.
5 Monitor the link quality over an extended period using suitable test
equipment. Ensure that the links meet the GSM specification GSM (ITU-T
G.703/G.704).
6 Monitor the link, RSL statistics and ECT to check if the changes are effected.
If the alarms/statistics are at an acceptable level, resolve the other alarms.
Otherwise use the LAPD protocol analyzer to track the source of any RSL
alarms.
68P02901W26-S 40-21
Nov 2007
13. RSL: LAPD protocol error threshold exceeded Chapter 40: RSL Alarms
Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one minute period.
A one byte code is displayed in the Additional information field, as shown in Table 40-4. The
code indicates where the alarm was reported.
Possible causes
40-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Continued
68P02901W26-S 40-23
Nov 2007
Procedure Chapter 40: RSL Alarms
40-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 14. RSL: Link audit failure
Description
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 40-5.
Possible causes
68P02901W26-S 40-25
Nov 2007
Procedure Chapter 40: RSL Alarms
Procedure
Check the number of received replies. Perform the following procedure to resolve the alarm.
40-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. RSL: Too many LAPD protocol errors
Description
Too many LAPD Protocol errors have been received indicating poor link quality.
The contents of the Additional information field are shown in Table 40-6.
Possible causes
Four or more LAPD Protocol errors were received within one second indicating major problems
with the RSL link.
68P02901W26-S 40-27
Nov 2007
Procedure Chapter 40: RSL Alarms
Procedure
1 Check report logs for repeated occurrence of this alarm. If alarm occurs
more than expected, monitor the state of MMS related to the RSL and INS
the RSL device. A field representative may need to visit the site to determine
the quality of the link and adjust, correct, or replace it as necessary.
2 Refer to Alarm Handling at the OMC customer documentation. Investigate
the RSL further if this keeps happening.
40-28 68P02901W26-S
Nov 2007
Chapter
41
SBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the Serial Bus (SBUS) alarm 254. SBUS: Device failure on page 41-3.
68P02901W26-S 41-1
Nov 2007
Introduction of SBUS alarms Chapter 41: SBUS Alarms
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.
41-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 254. SBUS: Device failure
Description
This alarm is generated only for InCell BSU-based hardware (including ExCell and
TopCell).
Possible causes
• A Bus Terminator Card (BTC) is not plugged into the backplane causing signals on the
backplane to go out of the expected range.
68P02901W26-S 41-3
Nov 2007
Procedure Chapter 41: SBUS Alarms
Procedure
Send a field representative to the site to determine the cause of the alarm.
Take appropriate action and resolve the alarm.
41-4 68P02901W26-S
Nov 2007
Chapter
42
SITE Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The SITE alarms are covered in this chapter and include the following procedures:
• 0. SITE: Last RSL link failure on page 42-4.
• 18. SITE: MIX board (Slot 18) communication failure on page 42-46.
• 19. SITE: Unequipped GPROC has entered the LAN on page 42-47.
• 20. SITE: Unequipped GPROC has left the LAN on page 42-51.
68P02901W26-S 42-1
Nov 2007
Procedure Chapter 42: SITE Alarms
• 28. SITE: Database configuration and arena hardware mismatch on page 42-70.
• 33. SITE: BSSGP status message received from the SGSN on page 42-80.
• 34. SITE: Erroneous BSSGP message received from the SGSN on page 42-81.
• 35. SITE: Network service status message received from the SGSN on page 42-82.
• 36. SITE: Erroneous network service message received from the SGSN on page 42-83.
• 37. SITE: No NS-VC block acknowledgment from the SGSN on page 42-84.
• 38. SITE: No NS-VC unblock acknowledgment from the SGSN on page 42-85.
• 39. SITE: No NS-VC alive acknowledgment from the SGSN on page 42-86.
• 40. SITE: No NS-VC reset acknowledgment from the SGSN on page 42-88.
• 41. SITE: Last NS-VC for the PCU failed on page 42-90.
• 45. SITE: No signaling BVC reset acknowledgment from the SGSN on page 42-94.
42-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
BSU-BTS alarms
The alarms contained in this chapter which apply to the BSU-based BTS cabinets are generated
for the Last Radio Signaling Link (RSL) failure and for a Site System Audits Processor (SSAP)
failure.
M-Cell alarms
The alarms contained in this chapter which apply to the M-Cell2 or M-Cell6 system products are
generated for the active Main Control Unit (MCU), Fiber Multiplexer (FMUX) and the active
Fiber Optic Extender (FOX) hardware devices at a site.
The standby alarms occur only in a situation where there are redundant devices present in a
standby frame to serve as a backup for the active ones at a site.
The fault conditions generated on the FMUX and FOX devices also affect the Digital Radio
Interface (DRI) software device. In an M-Cell2 or an M-Cell6 cabinet system, a DRI fault
condition is applied against the Transceiver Carrier Unit (TCU) hardware.
Alarm reporting
SITE alarms are reported by the software residing on the master GPROC.
68P02901W26-S 42-3
Nov 2007
0. SITE: Last RSL link failure Chapter 42: SITE Alarms
Description
This alarm indicates that the last Radio Signaling Link (RSL) on a Multiple Serial Interface
Link (MMS) at a Site has been disconnected.
Since an RSL link failure always affects call services, this alarm is sent concurrently with
other major alarms related to the link failure. The following RSL alarm should be received
concurrently: 10. RSL: Link disconnected.
In this case, the failed link happens to the last available link for service, the final link outage
occurs in a remote site.
The circumstances in which this alarm is received can be complex and diverse. Refer to the
description of each of the various contexts in which this alarm can be received on the next page
under the section, Alarm contexts on page 42-5.
If this alarm recurs repeatedly, investigate the functionality of the RSL link carrying the DISC
packet. Use the CCITT Blue Book, Q.921 as a source for details regarding the Data Link Layer
when pursuing this information.
42-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• All RSL connections to the BTS are Out Of Service (OOS) due to link or equipment
problems.
Alarm contexts
Determine the context in which the alarm is being received. For fault isolation and
troubleshooting, it is critical to determine which BSC-to-remote BTS site configuration is
present at the site receiving the alarms.
A star (or spoke) consists of many BTS sites; each of which is connected directly to the BSC by
E1 links (MMSs). A minimum of one MMS is required for each BTS site.
Multiple MMSs can be used to support additional traffic capacity or redundancy. A single BTS
site can have a maximum of ten MMSs. The Star (spoke) is treated as multiple open-ended daisy
chains with one BTS site per chain.
A loop chain consists of many BTSs connected together in a chain with at least a single E1 link
(MMS) between each remote BTS site. Multiple MMSs can be used to support additional traffic
capacity or redundancy. A single BTS site can have a maximum of ten MMSs. There are two
types of loop configurations: open and closed.
Open loop
Only one end of the (BTS) chain terminates at the BSC. The other end of the chain terminates on
a BTS site. An open loop can have a maximum of 10 remote BTS sites. In this configuration,
if a BTS site goes out Of Service (OOS), all BTS sites downstream from the failed BTS, go
OOS as well.
68P02901W26-S 42-5
Nov 2007
BSC-to-BTS topology Chapter 42: SITE Alarms
Closed loop
Both ends of the (BTS) chain terminate at the BSC. A closed loop can have a maximum of
10 remote BTS sites. In this configuration, if a BTS site goes OOS, all other BTS sites in the
chain remain INS.
Fork Conguration
A fork consists of either a single BTS site or chain of BTS sites connected to an intermediate
BTS site in a chain that terminates at the BSC. Fork BTS sites are connected with at least a
single E1 link (MMS) between each remote BTS site.
Multiple MMSs can be used to support additional traffic capacity or redundancy. A single BTS
site can have a maximum of ten MMSs. The fork can be open-ended or have a redundant loop
back to a chain that terminates at the BSC.
BSC-to-BTS topology
After determining the site configuration, remember the following system characteristics before
beginning troubleshooting activities.
System characteristics
The BSC-to-remote BTS topology is specified in terms of the continuous traffic routes between
the BSC and a terminating remote BTS site. This continuous route includes all intermediate
BTSs between the BSC and the remote BTS site generating the fault condition.
A particular traffic route is specified by a unique PATH device. (Every remote BTS site in the
network must be equipped with at least one PATH device). A PATH device specifies which
SITE devices and associated MSI/MMS devices define the route. Therefore, which particular
E1 link is used between each SITE device.
Every remote BTS site in the network must be equipped with at least one RSL. The RSL carries
signaling traffic between the BSC and the remote BTS site. A maximum of 8 RSLs can be
equipped between the BSC and a BTS site. The additional RSLs provide signaling traffic load
sharing (and depending on system configuration) may provide redundancy. An RSL for a specific
site is associated with a PATH device that terminates at that same site.
• If all RSLs between a BSC and a remote BTS site are OOS for more than 10
minutes, the BTS site goes OOS.
• An RSL may be OOS as a result of the associated MMS being OOS.
• An MMS may be OOS because an associated MSI or XCDR is OOS.
42-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
In the case of a BTS site that is part of an open loop or open-ended fork, the loss of RSLs at a
site may be caused by equipment failure downstream from the failed BTS site reporting the
alarm. (Recall that in this configuration, if a BTS site goes Out Of Service (OOS), all BTS sites
downstream from the failed BTS, go OOS as well).
Procedure
Wait for 10 minutes before continuing with this procedure. The site may be in the
process of resetting.
1 Check to see if the alarm has been cleared and the RSL connection has
been re-established. If this is the case, fault isolation and resolution is not
necessary. If the alarm has not been cleared, go to step 2.
Continued
68P02901W26-S 42-7
Nov 2007
Procedure Chapter 42: SITE Alarms
Continued
42-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 42-9
Nov 2007
Procedure Chapter 42: SITE Alarms
If yes, select State for each MMS associated with the Site.
Check the MMSs upstream and downstream from the BSC.
Check if the MMS(s) are in a busy-unlocked state. If yes,
check for MMS device alarms. Refer to Chapter 29 MMS
Alarms in this manual for fault resolution procedures.
not busy and It is possible that a device has failed. Before
unlocked sending a field representative to the site: Check
alarm reports for an MMS device alarms.
Continued
42-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
• 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.
68P02901W26-S 42-11
Nov 2007
2. SITE: BSC detected MCU to MCU communication failure Chapter 42: SITE Alarms
Description
This alarm is generated when the Base Station Controller (through the SITE device) has
received communication-related messages from both (active and standby) Main Control Unit
(MCU) software devices at an M-Cell site.
The software devices that generate this fault condition are the BSP Generic Processors (BSP
GPROCs). Together, the active and the standby BSP GPROC software devices cause this fault
condition to occur. (The hardware that is affected by this fault condition are the MCUs).
This fault condition indicates that both BTP GPROCs (MCUs) are designated as the master BTP
within the system software. If two BTP GPROCs (MCUs) are employed at a site, one BTP (MCU)
must be master and the other must be the standby.
This condition does not reduce traffic capacity. However, it does reduce redundancy at a site
because the two BTPs (MCUs) cannot communicate.
This alarm can occur only in an M-Cell2 or an M-Cell6 site equipped with BTP (MCU)
redundancy.
42-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The fiber optic cable connecting the two BTPs (MCUs) is incorrectly connected.
• The (MSW) port (on a BTP (MCU)) that connects to the fiber optic cable is faulty.
• The software that assigns a BTP (MCU) to the role of Master BTP is faulty.
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of both of the BTP (MCU) devices.
Continued
68P02901W26-S 42-13
Nov 2007
Procedure Chapter 42: SITE Alarms
42-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 Horizon macro and Horizon macro2 controlling cabinets, the alarm is generated when
an integrated multiplexer on the master BTP or its corresponding remote multiplexer, is
disconnected.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexers.
The impact of this fault condition is that all TCUs connected to the multiplexer are removed from
service. The DRIs (TCUs) are no longer able to communicate with an MCU/BTP (GPROC). Thus,
the ability to handle system traffic is reduced at the site that is experiencing the fault condition.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local multiplexer is disconnected from the
backplane.
68P02901W26-S 42-15
Nov 2007
Additional information eld Chapter 42: SITE Alarms
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.
42-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. SITE: Standby multiplexer 0 loopback failure
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 Horizon macro and Horizon II macro controlling cabinets, the alarm is generated when
an integrated multiplexer on the standby BTP or its corresponding remote multiplexer, is
disconnected.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexers.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local standby multiplexer is disconnected
from the backplane.
68P02901W26-S 42-17
Nov 2007
Possible causes Chapter 42: SITE Alarms
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.
42-18 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. SITE: Active multiplexer 1 loopback failure
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 Horizon macro 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.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexers.
The impact of this fault condition is that all TCUs connected to the multiplexer are removed from
service. The DRIs (TCUs) are no longer able to communicate with an MCU/BTP (GPROC). Thus,
the ability to handle system traffic is reduced at the site that is experiencing the fault condition.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local multiplexer is disconnected from the
backplane.
68P02901W26-S 42-19
Nov 2007
Additional information eld Chapter 42: SITE Alarms
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.
42-20 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 6. SITE: Standby multiplexer 1 loopback failure
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 Horizon macro and Horizon II macro controlling cabinets, the alarm is generated when
an integrated multiplexer on the standby BTP or its corresponding remote multiplexer, is
disconnected.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexer.
This alarm is suppressed where FMUX1 supports a Horizon II mini extension cabinet.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local standby multiplexer is disconnected
from the backplane.
68P02901W26-S 42-21
Nov 2007
Possible causes Chapter 42: SITE Alarms
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.
42-22 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 7. SITE: Active multiplexer 2 loopback failure
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 Horizon macro controlling cabinet, the alarm is generated when a multiplexer external to
the active MCUF or its corresponding remote multiplexer, is disconnected.
For a Horizon II macro controlling cabinet, the alarm is generated when an integrated
multiplexer on the master BTP or its corresponding remote multiplexer, is disconnected.
In both cases, the alarm is generated only if one or more in-service DRIs are
connected to the multiplexers.
The impact of this fault condition is that all TCUs connected to the multiplexer are removed from
service. The DRIs (TCUs) are no longer able to communicate with an MCU/BTP (GPROC). Thus,
the ability to handle system traffic is reduced at the site that is experiencing the fault condition.
68P02901W26-S 42-23
Nov 2007
Additional information eld Chapter 42: SITE Alarms
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local multiplexer is disconnected from the
backplane.
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
Continued
42-24 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 42-25
Nov 2007
8. SITE: Standby multiplexer 2 loopback failure Chapter 42: SITE Alarms
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 Horizon macro controlling cabinet, the alarm is generated when a multiplexer external to
the standby MCUF or its corresponding remote multiplexer, is disconnected.
For Horizon II macro controlling cabinet, the alarm is generated when an integrated multiplexer
on the standby BTP or its corresponding remote multiplexer, is disconnected.
This alarm is generated only if one or more in-service DRIs are connected to the
multiplexers.
This alarm is suppressed where FMUX2 supports a Horizon II mini extension cabinet.
TCU connection
If one or more TCUs are In-Service (INS), the alarm occurs. If no TCUs are INS, the alarm
does not occur.
• The remote multiplexer board linked to the local standby multiplexer is disconnected
from the backplane.
42-26 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 From the Navigation Tree, open the Detailed View for the SITE
device. From the View Menu select State to check the operational
and administrative state of all of the DRIs (TCUs) connected to the
multiplexer. They should all be Out Of Service (OOS).
3 Send a field representative to the site to investigate a potential
hardware fault within the multiplexer or the multiplexer link.
68P02901W26-S 42-27
Nov 2007
9. SITE: Active local FOX failure Chapter 42: SITE Alarms
Description
This alarm indicates that the M-Cell Fiber Optic Extender (FOX) board residing in the (active)
master MCU card frame has failed. It is generated after all of the DRI/Transceiver Control Units
(TCUs) supported by the FOX have lost the ability to communicate to the MCU/BTP (GPROC).
This local FOX failure alarm is generated when all In Service (INS) TCUs lose connection with
the MCU at the same time.
The impact of this fault condition is that all TCUs are removed from service. The DRIs (TCUs)
are no longer able to communicate with an MCU/BTP (GPROC). Thus, the ability to handle
system traffic is reduced at the site that is experiencing the fault condition.
TCU connection
If at least two TCUs are connected and INS, this alarm occurs when the local FOX board residing
in the master MCU card frame is disconnected from the backplane.
42-28 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 In the Alarm window, determine whether the following DRI alarms
have been generated against the DRI (TCUs) connected to the FOX
that has failed:
68P02901W26-S 42-29
Nov 2007
10. SITE: Standby local FOX failure Chapter 42: SITE Alarms
Description
This alarm indicates that the M-Cell Fiber Optic Extender (FOX) board residing in the standby
MCU card frame has failed. It is generated after all of the DRI/Transceiver Control Units (TCUs)
supported by the FOX have lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and INS, this alarm occurs when the local FOX board residing
in the master MCU card frame is disconnected from the backplane.
Possible causes
42-30 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 42-31
Nov 2007
11. SITE: Active remote FOX 0 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
master MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 0
of the (active) master MCU card frame; it is referred to as FMUX 0. The alarm is generated
after the FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 0 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-32 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-33
Nov 2007
12. SITE: Standby remote FOX 0 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
standby MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 0
of the (standby) MCU card frame; it is referred to as FMUX 0. The alarm is generated after the
FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 1 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-34 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-35
Nov 2007
13. SITE: Active remote FOX 1 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
master MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 1
of the (active) master MCU card frame; it is referred to as FMUX 1. The alarm is generated
after the FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 1 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-36 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-37
Nov 2007
14. SITE: Standby remote FOX 1 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
standby MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 1
of the (standby) MCU card frame; it is referred to as FMUX 1. The alarm is generated after the
FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 1 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-38 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-39
Nov 2007
15. SITE: Active remote FOX 2 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
master MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 2
of the (active) master MCU card frame; it is referred to as FMUX 2. The alarm is generated
after the FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 2 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-40 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-41
Nov 2007
16. SITE: Standby remote FOX 2 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the remote M-Cell Fiber Optic Extender (FOX) board connected to the
standby MCU has failed. The connection is maintained using Fiber Multiplexer (FMUX) in slot 2
of the (standby) MCU card frame; it is referred to as FMUX 2. The alarm is generated after the
FOX has lost the ability to communicate to the MCU/BTP (GPROC).
TCU connection
If at least two TCUs are connected and In Service (INS), this alarm occurs when the remote FOX
board connected to the master MCU by way of FMUX 1 is disconnected from the backplane.
This is a service-affecting fault condition. If this fault condition occurs, all TCUs (INS)
connected to the FOX are automatically disabled.
42-42 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
68P02901W26-S 42-43
Nov 2007
17. SITE: 16 kbps switching hardware required Chapter 42: SITE Alarms
Description
This alarm indicates that one of the following two possible fault conditions has occurred:
• A BTS (SITE) currently contains a Timeslot Switch (TSW) rather than a Kiloport Switch
(KSW) in the master cage as required.
• A BTS (SITE) is configured for dynamic (timeslot) allocation, but the KSW in the master
cage is not configured to support it.
Switching capability
A Timeslot Switch (TSW) is not capable of 16 kbps switching for a BTS that is either equipped to
use Radio Signaling Links (RSLs) or is configured to support dynamic allocation.
Only a KSW can provide 16 kbps switching. Neither InCell TSW boards nor M-Cell switching
hardware provide 16 kbps switching.
This is a service affecting fault condition. No calls can be completed at a BTS for
which this alarm has been generated.
42-44 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The BTS site is configured for dynamic allocation, but the master cage does not contain the
switching hardware to support it.
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring.
2 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.
68P02901W26-S 42-45
Nov 2007
18. SITE: MIX board (Slot 18) communication failure Chapter 42: SITE Alarms
Description
The polling software does not detect the MIX board or responds with a bad board identifier.
Possible causes
• A board that is not MIX has been inserted in the MIX slot.
Procedure
Insert a good MIX Board into the MIX slot (Slot 18).
42-46 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 19. SITE: Unequipped GPROC has entered the LAN
Description
This alarm indicates that Local Area Network (LAN) hardware has detected that a Generic
Processor (GPROC) device has accessed the LAN without being equipped in the Configuration
Management (CM) database.
Equip the GPROC device fully before the system can use it.
System impact
The system impact varies depending on the actual cause of the fault.
This alarm may indicate that either OMC-R or onsite maintenance action is occurring; or an
operator or onsite error has been made; or that a hardware failure has occurred.
An alphanumeric text string is used to display the specific cage and slot occupied by the
unequipped GPROC.
Where: ‘xx’ represents the decimal numbers associated with the cage and slot.
68P02901W26-S 42-47
Nov 2007
Possible causes Chapter 42: SITE Alarms
Possible causes
• The GPROC may have recently been unequipped after entering the LAN.
Procedure
Continued
42-48 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 42-49
Nov 2007
Procedure Chapter 42: SITE Alarms
42-50 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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.
Equip the GPROC device fully before the system can use it.
System impact
The system impact varies depending on the actual cause of the fault.
This alarm may indicate that either OMC-R or onsite maintenance action is occurring; or an
operator or onsite error has been made; or that a hardware failure has occurred.
An alphanumeric text string is used to display the specific cage and slot occupied by the
unequipped GPROC.
Where: ‘xx’ represents the decimal numbers associated with the cage and slot.
68P02901W26-S 42-51
Nov 2007
Possible causes Chapter 42: SITE Alarms
Possible causes
Procedure
Continued
42-52 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Continued
68P02901W26-S 42-53
Nov 2007
Procedure Chapter 42: SITE Alarms
42-54 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 21. SITE: No clock references available
Description
This alarm indicates that Fault Management (FM) has detected that the current Generic Clock
(GCLK) reference for clock extraction has failed within the system.
System impact
While this fault condition exists, service and capacity are not compromised unless this alarm is
the result of an equipment failure. If a failure occurs, other serious (Critical and Major) alarms
are generated for the Multiple Serial Interface link (MMS), Multiple Serial Interface (MSI), the
transcoder (XCDR) or Generic DSP Processor (GDP).
68P02901W26-S 42-55
Nov 2007
Additional information eld Chapter 42: SITE Alarms
The contents of the Additional information field are shown in Table 42-1.
Possible causes
• The MMS providing the clock reference source for the site is locked by the operator.
• The last MMS providing a clock reference source for the site may have gone Out Of
Service (OOS).
42-56 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
1 Refer to the alarm message report. Check for related MMS, MSI, XCDR
or GDP (Critical) alarms at that site which indicate an MMS link or a
transcoding problem.
68P02901W26-S 42-57
Nov 2007
22. SITE: Active alarm list full Chapter 42: SITE Alarms
Description
A new alarm could not be added to the active alarm list because the alarm list for a specific
site on a BSS is full. The alarm list can contain a maximum of 120 active alarms for each site
on a BSS.
This alarm indicates a more serious problem may exist due to the number of active alarms.
After this alarm has been generated, any subsequent alarms generated are discarded.
They are not stored by the system.
This alarm does not affect the OMC-R because it has a different active alarm list.
A one-byte alarm code is displayed in the Additional information field identifies the new alarm
that triggered this alarm.
Possible causes
The active alarm list is full because there are 120 active alarms at the site.
42-58 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 42-59
Nov 2007
23. SITE: EMU modem card failure Chapter 42: SITE Alarms
Description
The EMU HDSL modem card is not detected by the polling software.
A one-byte alarm code is displayed in the Additional information field identifies the new alarm
that triggered this alarm.
Possible causes
• The RS232 cable between the MIX and EMU has been removed.
Procedure
42-60 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 24. SITE: Site reset request
Description
This alarm indicates that either the system software, an OMC-R operator, or an onsite field
representative has requested a SITE reset.
System software may require a reset due to the existence of a software or a hardware fault
condition. An operator or field representative may reset a site during maintenance or
troubleshooting through the BSS MMI or OMC-R GUI.
This fault condition is service-affecting. All Digital Radio Interface (DRI) radio units
or RF Units go Out Of Service (OOS). As a result, calls are lost.
The contents of the Additional information field are shown in Table 42-2.
Continued
68P02901W26-S 42-61
Nov 2007
Additional information eld Chapter 42: SITE Alarms
The following is a list of PIDs that relate to the site reset request. PID numbers are shown in
the Additional information field for the purpose of highlighting which internal software process
has caused the reset.
Table 42-3 expresses the PID number, the abbreviated name of the software process and a brief
description of the process and why it is requesting a reset.
In addition, the Network Element (NE) for which the reset is requested is stated.
42-62 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The system site reset request is due to a software fault: processing fault, inconsistent
database, or invalid state transition requested for a device.
• The operator site reset attempted is due to a current fault (software or hardware) existing
within the system.
Procedure
1 Review the alarm report and event logs to determine the site where
this alarm is occurring. Check the Additional information field in the
alarm output for the possible cause for the alarm (and site reset).
2 If a SITE reset has been initiated, wait for it to finish before
continuing.
3 After the reset, check to see if this alarm is automatically cleared in
the Alarm window.
• If the site reset did clear the alarm, cease fault resolution.
• If the site reset did not clear the alarm, initiate the appropriate
data collection processes (For example, Performance
Management) for troubleshooting purposes and/or go to step 4.
4 Check the alarm output for any OOS devices shown in the impacted
devices list.
• Check the Alarm window for alarms related to the OOS devices
in the list. Refer to other alarm descriptions and fault resolution
procedures in this manual.
68P02901W26-S 42-63
Nov 2007
25. SITE: External power booster amplier 1 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the Transmitter Channel 1 Power Amplifier (PA) within the Horizon
compact (M-Cell arena macro) Base Transceiver Station (BTS) has failed.
The power transmitted to channel 1 transmit antenna is reduced to approximately 0.8 W.
This alarm applies only to Horizon compact (M-Cell arena macro) Booster units.
System impact
The result of this reduction in transmission power may have some general effects such as,
reduced area of coverage in the macro cell, reduced capacity in terms of calls that can be
handled, voice quality may be reduced on the edge of the cell, and calls originating outside
the coverage area may be dropped.
Other possible effects depend on whether the site is located in a high traffic or low traffic area
and how the surrounding cells are configured.
In a high traffic area, if the non-BCCH PA fails, the impact will most likely reduce the call
capacity if the other PA remains fully functional. If the PA holding the BCCH fails, area of
coverage is reduced.
In a low traffic area, if one PA fails, the loss of transmission power may be transparent if the
Horizon compact (M-Cell arena macro) site is not set up to provide sole coverage for the macro
cell. However, if the unit provides sole coverage, call coverage may be reduced.
42-64 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Check the alarm report to determine the site for which the alarm
was generated.
2 Send a field representative to the site to replace the Horizon compact
(M-Cell arena macro) Booster containing the faulty PA. The PA cannot
be replaced onsite, the entire Booster unit must be replaced if faulty.
68P02901W26-S 42-65
Nov 2007
26. SITE: External power booster amplier 2 failure Chapter 42: SITE Alarms
Description
This alarm indicates that the Transmitter Channel 2 Power Amplifier (PA) within the Horizon
compact (M-Cell arena macro) Base Transceiver Station (BTS) has failed.
The transmitted power to both transmit antenna is reduced to approximately 2.0 W instead of
10 W.
This alarm applies only to Horizon compact (M-Cell arena macro) Booster units.
System impact
The result of this reduction in transmission power may have some general effects such as,
reduced area of coverage in the macro cell, reduced capacity in terms of calls that can be
handled, voice quality may be reduced on the edge of the cell, and calls originating outside
the coverage area may be dropped.
Other possible effects depend on whether the site is located in a high traffic or low traffic area
and how the surrounding cells are configured.
In a high traffic area, if the non-BCCH PA fails, the impact will most likely reduce the call
capacity if the other PA remains fully functional. If the PA holding the BCCH fails, area of
coverage is reduced.
In a low traffic area, if one PA fails, the loss of transmission power may be transparent if the
Horizon compact (M-Cell arena macro) site is not set up to provide sole coverage for the macro
cell. However, if the unit provides sole coverage, call coverage may be reduced.
42-66 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
Procedure
1 Check the alarm report to determine the site for which the alarm
was generated.
2 Send a field representative to the site to replace the Horizon
compact (M-Cell arena macro) Booster containing the faulty PA.
68P02901W26-S 42-67
Nov 2007
27. SITE: External power booster failure Chapter 42: SITE Alarms
Description
This alarm indicates that the booster in the Horizon compact (M-Cell arena macro) Base
Transceiver Station (BTS) has failed. This alarm is generated when the system detects that the
booster is not functioning because it is either not installed, not connected (or not present)
or faulty.
The power transmitted to both transmit antennas is reduced to approximately 0.8 W per channel.
This alarm applies only to Horizon compact (M-Cell arena macro) site with a booster
unit.
System impact
The result of this reduction in transmission power may have some general effects such as,
reduced area of coverage in the macro cell, reduced capacity in terms of calls that can be
handled, voice quality may be reduced on the edge of the cell, and calls originating outside
the coverage area may be dropped.
Other possible effects depend on whether the site is located in a high traffic or low traffic area
and how the surrounding cells are configured.
In a high traffic area, if the non-BCCH PA fails, the impact will most likely reduce the call
capacity if the other PA remains fully functional. If the PA holding the BCCH fails, area of
coverage is reduced.
In a low traffic area, if one PA fails, the loss of transmission power may be transparent if the
Horizon compact (M-Cell arena macro) site is not set up to provide sole coverage for the macro
cell. However, if the unit provides sole coverage, call coverage may be reduced.
42-68 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
Possible causes
• The Horizon compact macro Booster unit is not present at the site.
Procedure
1 Check the alarm report to determine the site for which the alarm
was generated.
2 Send a field representative to the site to verify that the Horizon
compact macro Booster is present and check the connections. If
attempts to reconnect the Horizon compact unit do not clear the
alarm, replace the booster unit.
68P02901W26-S 42-69
Nov 2007
28. SITE: Database conguration and arena hardware mismatch Chapter 42: SITE Alarms
Description
• The hardware present is Arena Macro hardware but the database configuration is for
standard Arena hardware or vice versa.
• The BTS master cabinet is M-Cell6, Horizon macro, Horizon macro2 or Horizon micro2, but
the database cabinet type does not match. If the site is Horizon macro and the database is
M-Cell6, the site stays in service. In all other instances of this alarm the site is taken OOS.
System impact
No system impact to service occurs. The Horizon unit is fully operational despite the
database-to-hardware mismatch.
In addition, the Horizon compact External Power Booster SITE alarms (25, 26, 27) can be
generated if the Booster unit hardware becomes faulty.
System upgrade
The cabinet is equipped as a Horizon II mini as per the Horizon II mini feature (FR28565). The
operators configure the site to a configuration not supported by the hardware. To support the
Horizon II mini and Horizon II mini_extension, the cabinet types are changed:
Thus, for all Horizon II micro cabinets, the operator configures the site to a configuration not
supported by the hardware. For example, Horizon II mini site.
42-70 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Possible causes
• The procedure applies to all the upgraded BSCs containing Horizon II micro
sites.
• To avoid any disruptions in network, carry out the procedure during those hours
of the day when the traffic is moderate or low.
1 Enter the lock_device command to lock all DRIs under the Horizon II micro
site.
2 Enter the unequip_device command to unequip all DRIs under the Horizon
II micro site.
3 Enter the modify_value command to modify the cabinet type from 24 to 26.
4 Enter the equip_device command to equip all DRIs again.
5 Enter the unlock_device command to unlock all DRIs under the Horizon II
micro site. (The new cabinet type will now be displayed as Horizon II mini)
Possible causes
• If the BTS master cabinet is either M-Cell6, Horizon macro or Horizon macro2, an invalid
database cabinet type has been entered for this site.
Procedure
1 Check the alarm report to determine the site for which the alarm
was generated.
2 Verify the site plan with Network OMC-R planners and
administrators; determine which Horizon unit Cabinet Type should
be at the site.
Continued
68P02901W26-S 42-71
Nov 2007
Procedure Chapter 42: SITE Alarms
• 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.
• 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.
42-72 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 29. SITE: EMU download failure
Description
Possible causes
68P02901W26-S 42-73
Nov 2007
Procedure Chapter 42: SITE Alarms
Procedure
42-74 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 30. SITE: NVM board failure
Description
The NVM board failed or was removed from the system. This alarm applies to BSC and RXCDR.
Possible causes
Procedure
1 Send a field representative to the site to reinsert or replace the NVM board.
2 The NVM board with a PCMCIA card inserted in socket 1 is considered a
single FRU.
68P02901W26-S 42-75
Nov 2007
Procedure Chapter 42: SITE Alarms
42-76 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
• The PCMCIA card was removed from socket 1 of the NVM board.
Procedure
1 Send a field representative to the site to re-insert or replace the NVM board.
2 The NVM board with a PCMCIA card inserted in socket 1 is considered a
single FRU.
68P02901W26-S 42-77
Nov 2007
Procedure Chapter 42: SITE Alarms
42-78 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Procedure
68P02901W26-S 42-79
Nov 2007
33. SITE: BSSGP status message received from the SGSN Chapter 42: SITE Alarms
Description
The PCU received a BSS GPRS Protocol (BSSGP) status message indicating that the Serving
GPRS Support Node (SGSN) received an invalid message. This alarm may also indicate a
congestion condition at the SGSN. SGSN reports this condition.
The BSSGP status message contents are displayed in the Additional information field.
Possible causes
Procedure
42-80 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 34. SITE: Erroneous BSSGP message received from the SGSN
Description
The PCU received an erroneous BSS GPRS Protocol (BSSGP) message from the Serving GPRS
Support Node (SGSN). After this alarm is generated, a status message is sent back to the SGSN.
The erroneous BSSGP message contents are displayed in the Additional information field.
Possible causes
Procedure
68P02901W26-S 42-81
Nov 2007
35. SITE: Network service status message received from the SGSN Chapter 42: SITE Alarms
Description
The PCU received a network service status message indicating that the Serving GPRS Support
Node (SGSN) received an invalid message. This alarm may also indicate that an exceptional
condition occurred at the SGSN. SGSN reports this condition.
The BSSGP status message contents are displayed in the Additional information field.
Possible causes
Procedure
Procedure 42-36 Network service status message received from the SGSN
42-82 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 36.
SITE: Erroneous network service message received from the SGSN
Description
The PCU received an erroneous network service message from the Serving GPRS Support
Node (SGSN). After this alarm is generated, a status message is sent back to the SGSN. SGSN
reports this condition.
The erroneous network service message contents are displayed in the Additional information
field.
Possible causes
The PCU is unable to interpret a network service message sent by the SGSN.
Procedure
Procedure 42-37 Erroneous network service message received from the SGSN
68P02901W26-S 42-83
Nov 2007
37. SITE: No NS-VC block acknowledgment from the SGSN Chapter 42: SITE Alarms
Description
The PCU has repeated the NS-VC (PVC) Block message the maximum number of times without
receiving an acknowledgment from the Serving GPRS Support Node (SGSN).
The corresponding NS-VC identifier (NS-VCI) is displayed in the Additional information field.
The range of values for the NS-VCI is 0 to 65535. For example, NS-VC 87 is displayed in the
Additional information field as NS-VCI 87.
Possible causes
Procedure
42-84 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 38. SITE: No NS-VC unblock acknowledgment from the SGSN
Description
The PCU has repeated the NS-VC(PVC) Unblock message the maximum number of times without
receiving an acknowledgment from the Serving GPRS Support Node (SGSN).
The corresponding NS-VC identifier (NS-VCI) is displayed in the Additional information field.
The range of values for the NS-VCI is 0 to 65535. For example, NS-VC 87 is displayed in the
Additional information field as NS-VCI 87.
Possible causes
Procedure
68P02901W26-S 42-85
Nov 2007
39. SITE: No NS-VC alive acknowledgment from the SGSN Chapter 42: SITE Alarms
Description
The PCU has repeated the NS-VC (PVC) Alive message the maximum number of times without
receiving an acknowledgment from the Serving GPRS Support Node (SGSN).
System action
The corresponding NS-VC identifier (NS_VCI) is displayed in the Additional information field.
The range of values for the NS-VCI is 0 to 65535. For example, NS-VC 87 is displayed in the
Additional information field as NS-VCI 87.
Possible causes
42-86 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 42-87
Nov 2007
40. SITE: No NS-VC reset acknowledgment from the SGSN Chapter 42: SITE Alarms
Description
The PCU has repeated the NS-VC (PVC) Reset message the maximum number of times without
receiving an acknowledgment from the Serving GPRS Support Node (SGSN).
System action
The corresponding NS-VC identifier (NS_VCI) is displayed in the Additional information field.
The range of values for the NS-VCI is 0 to 65535. For example, NS-VC 87 is displayed in the
Additional information field as NS-VCI 87.
Possible causes
42-88 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 42-89
Nov 2007
41. SITE: Last NS-VC for the PCU failed Chapter 42: SITE Alarms
Description
System action
The BSSGP Virtual Connection identifier (BVCI) is displayed in the Additional information
field. The range of values for the BVCI is 0 to 65535. For example, BVC 87 is displayed in
the Additional information field as BVCI 87.
Possible causes
Procedure
Determine if the last GBL failed. Perform the following procedure to resolve the alarm.
42-90 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 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 causes
Link fault.
Procedure
Initiate fault isolation and resolution procedures for the TRAU GDS links.
68P02901W26-S 42-91
Nov 2007
43. SITE: Last PRP or PXP failed Chapter 42: SITE Alarms
Description
This alarm indicates that the last DPROC with PRP functionality (that is a PXP or PRP DPROC)
has gone out of service and the GPRS functionality is not available.
Possible causes
The associated device has been taken out of service by an operator maintenance command or
there has been an equipment failure.
Procedure
1 First check the state of the failed devices using the command: dis_pr (site
number) or state (site number) (dproc device numbers).
2 Refer to Technical Description: BSS Command Reference (68P02901W23)
for more information. If the device state is not busy-unlocked, determine
if the device is currently taken out of service by a maintenance command.
If not, send a field representative to the site to determine the cause of the
failure.
42-92 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 42-93
Nov 2007
45. SITE: No signaling BVC reset acknowledgment from the SGSN Chapter 42: SITE Alarms
Description
The PCU has repeated the BVC Reset message the maximum number of times for the signaling
BVCI without receiving any acknowledgment from the SGSN.
Possible causes
Procedure
1 Investigate why a reset acknowledgment was not received from the SGSN
for the signaling BVC.
2 Clear the alarm.
42-94 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 46. SITE: DSW switching hardware required at site
Description
Half rate calls on half rate capable RTFs that have 8 kbps TRAU allowed, will be blocked if 16
kbps switching is in operation. If the RTF is configured for 8 k backhaul, but the BSS does not
support this (BSC has KSWs present), then half rate is effectively disabled for this carrier, and
the Site[46] alarm is raised. The fix for this is to either swap out the KSWs for DSWs at the BSC,
or to reconfigure the RTF so as not to require 8 k backhaul and thus be consistent with the BSC.
Possible causes
A KSW has been found to exist in the system when the database was setup assuming that DSW
switches would be used throughout the BSC.
Procedure
68P02901W26-S 42-95
Nov 2007
Procedure Chapter 42: SITE Alarms
42-96 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 50. SITE: Database corruption detected
Description
Possible causes
Memory corruption or software error has rendered the database invalid at the site.
Procedure
68P02901W26-S 42-97
Nov 2007
51. SITE: Software patch installation failure Chapter 42: SITE Alarms
Description
Possible causes
Procedure
When the alarm occurs, the BSS backs out the patch level to 0 within the BSS.
42-98 68P02901W26-S
Nov 2007
Chapter
43
TBUS Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TDM Bus (TBUS) alarms are covered in this chapter and include the following procedures:
• 0. TBUS: Remote KSWl loopback test failure on page 43-3.
68P02901W26-S 43-1
Nov 2007
Introduction to TBUS alarms Chapter 43: 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 fiber optic cables interconnecting the KSWX cards. Each cage
has two TBUS devices (one active and one redundant).
43-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TBUS: Remote KSWl loopback test failure
Description
Over 50% of the TDM loopback tests, between the GPROCs in an extended cage and the active,
remote KSW, have failed, but the remote KSW is tested successfully. This indicates that a fault
exists with the TBUS, and not with the KSW.
System action
The system swaps the faulty KSWX with the redundant KSWX. If both the KSWX reporting the
alarm and the redundant KSWX are OOS, the site resets.
Possible causes
• The toggle switch on the KSWX card is in the down (disable) position.
68P02901W26-S 43-3
Nov 2007
Procedure Chapter 43: TBUS Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
43-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 3. TBUS: Local KSWX/DSWX TDM error
Description
The local KSWX/DSWX card detected that it is no longer receiving data through the receive fiber.
System action
The TBUS is placed OOS. The system swaps the faulty TBUS with the redundant TBUS. If both
the TBUS reporting the alarm and the redundant TBUS are OOS, the site resets.
Possible causes
• The fiber link between the local and remote KSWX/DSWX was disconnected.
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 43-5
Nov 2007
Procedure Chapter 43: TBUS Alarms
43-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 4. TBUS: Remote KSWX/DSWX TDM error
Description
The remote KSWX/DSWX card detected that it is no longer receiving data through the receive
fiber.
System action
The TBUS is placed OOS. The system swaps the faulty TBUS with the redundant TBUS. If both
the TBUS reporting the alarm and the redundant TBUS are OOS, the site resets.
The additional information displays the cage and slot number of the remote KSWX card that
detected that it was not receiving data. The cage and slot are presented as hexadecimal values.
If the values 00 is displayed, a different KSWX/DSWX fault condition has been resolved. The
current remote KSWX/TDM fault condition still exists and must be resolved.
Possible causes
• The fiber link between the local and remote KSWX/DSWX was disconnected.
68P02901W26-S 43-7
Nov 2007
Procedure Chapter 43: TBUS Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
43-8 68P02901W26-S
Nov 2007
Chapter
44
TDM Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TDM alarms are covered in this chapter and include the following procedures:
• {25002} 5. TDM: Bus swap could not be initiated on page 44-3.
68P02901W26-S 44-1
Nov 2007
Introduction to TDM alarms Chapter 44: TDM Alarms
TDM alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with
the TDM device.
44-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5. TDM: Bus swap could not be initiated
{25002}
Description
This alarm is generated when the FM software detects that the redundant TDM is not available
when the active TDM needs to be swapped with the redundant TDM.
Possible causes
Procedure
68P02901W26-S 44-3
Nov 2007
229. TDM: Swap test audit failure Chapter 44: TDM Alarms
{25002}
Description
• A swap of the TDM device had been attempted but failed and a recovery of swapping
back to the original device was performed.
Possible causes
• Alarms were detected on the redundant upon swapping over to the redundant highway.
Procedure
44-4 68P02901W26-S
Nov 2007
Chapter
45
TIMESLOT Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TIMESLOT alarms are covered in this chapter and include the following procedures:
• 0. TIMESLOT: Radio frequency losses while using a TCH - PM on page 45-3.
68P02901W26-S 45-1
Nov 2007
Introduction to TIMESLOT alarms Chapter 45: TIMESLOT Alarms
TIMESLOT alarms
This chapter describes the alarm and OMC-R troubleshooting procedures associated with the
TIMESLOT alarms.
45-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TIMESLOT: Radio frequency losses while using a TCH - PM
Description
This statistic counts the number of calls lost while using a Traffic Channel (TCH) due to RF
problems.
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
Possible causes
Procedure
Determine if there are any currently active hardware alarms. Perform the following procedure
to resolve the alarm.
68P02901W26-S 45-3
Nov 2007
1. TIMESLOT: Channel request from MS failed - PM Chapter 45: TIMESLOT Alarms
Description
This statistic counts the number of instances a BSS times out waiting for the MS to establish a
call on a specific Standalone Dedicated Control Channel (SDCCH).
For further information, refer to the MTL statistics chapter in the manual, Maintenance
Information: GSM Statistics Application (68P02901W56).
This is considered a normal occurrence when an MS is moving out of range, is failing or is
switched off. However, frequent occurrences of this event within a short period of time and/or,
if geographically clustered, may indicate a hardware failure.
Possible causes
A hardware failure may have occurred, if a BSS has timed out before allowing an MS to establish
a call (when SDCCH resources are available for an immediate TCH assignment).
45-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Determine if there are any currently active DRI alarms. Perform the following procedure to
resolve the alarm.
68P02901W26-S 45-5
Nov 2007
4. TIMESLOT: No Timeslot HealthInfo Alarm Chapter 45: TIMESLOT Alarms
Description
Timeslot Health Information file has not been received for ((BAD_ALARM_INTERVAL_COUNT /
2) + 1) consecutive intervals.
None.
Possible causes
Procedure
45-6 68P02901W26-S
Nov 2007
Chapter
46
TRU Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TopCell Radio Unit (TRU) alarms are covered in this chapter and include the following
procedures:
• 0. TRU: Door open on page 46-3.
68P02901W26-S 46-1
Nov 2007
Introduction to TRU alarms Chapter 46: TRU Alarms
TRU alarms
This chapter describes the alarms and OMC-R troubleshooting procedures associated with the
TopCell Radio Unit (TRU).
46-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. TRU: Door open
Description
Possible causes
• An illegal entry.
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 46-3
Nov 2007
Procedure Chapter 46: TRU Alarms
46-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. TRU: Power supply unit failure
Description
System action
The BSS software attempts to redirect the calls to transceivers in neighboring TRUs.
Possible causes
68P02901W26-S 46-5
Nov 2007
Procedure Chapter 46: TRU Alarms
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
46-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. TRU: Power mains failure
Description
System action
The BSS software attempts to redirect calls to the transceivers in neighboring TRUs.
Possible causes
68P02901W26-S 46-7
Nov 2007
Procedure Chapter 46: TRU Alarms
Procedure
46-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 5-6. TRU: Customer dened 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 causes
Procedure
1 Send a field representative to the site to determine the cause of the alarm.
2 Take appropriate action and resolve the alarm.
68P02901W26-S 46-9
Nov 2007
Procedure Chapter 46: TRU Alarms
46-10 68P02901W26-S
Nov 2007
Chapter
47
XBL Alarms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Transcoder to BSS Link (XBL) alarms are covered in this chapter and include the following
procedures:
• 0. XBL: Invalid received frames - PM on page 47-3.
68P02901W26-S 47-1
Nov 2007
Introduction to XBL alarms Chapter 47: 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 signaling link traffic between the BSC and the RXCDR site. The XBL uses
the Multiple Serial Interface link (MMS: E1 link) hardware as its underlying communication
link medium.
47-2 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 0. XBL: Invalid received frames - PM
Description
This statistic counts the number of the invalid frames received on the X.25/LAPD link.
For further information, refer to XBL statistics chapter in the manual, Maintenance Information:
GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 47-3
Nov 2007
Procedure Chapter 47: XBL Alarms
47-4 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 1. XBL: FRMR frames - PM
Description
This statistic counts the number of the frames on the X.25/LAPD link that were rejected because
the frames are not correctable.
For further information, refer to XBL statistics chapter in the manual, Maintenance Information:
GSM Statistics Application (68P02901W56).
Possible causes
Procedure
68P02901W26-S 47-5
Nov 2007
Procedure Chapter 47: XBL Alarms
47-6 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 2. XBL: Expiration of N2 - PM
2. XBL: Expiration of N2 - PM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates that the maximum number of link alignment retries is attempted without
success.
For further information, refer to XBL statistics chapter in the manual, Maintenance Information:
GSM Statistics Application (68P02901W56).
Possible causes
68P02901W26-S 47-7
Nov 2007
Procedure Chapter 47: XBL Alarms
Procedure
47-8 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 10. XBL: Link disconnected
Description
An XBL is disconnected on the MMS. No signaling information between the BSC and the RXCDR
is passed over the disconnected link.
The contents of the Additional information field are shown in Table 47-1.
68P02901W26-S 47-9
Nov 2007
Possible causes Chapter 47: XBL Alarms
Possible causes
Procedure
Wait for 10 minutes after the alarm is reported before continuing with this procedure.
If an RXCDR reboots, this delay allows sufficient time for the reboot process to
complete.
Continued
47-10 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
68P02901W26-S 47-11
Nov 2007
11. XBL: LAPD protocol error Chapter 47: XBL Alarms
Description
The XBL detected a LAPD protocol error due to a problem on one of the E1 links.
The MMS timeslot, the reason for the LAPD error and the MMS ID are displayed in the
Additional information field in the following format:
Possible causes
The LAPD Error code in the Additional information field corresponds to a possible cause for
the alarm, as shown in Table 47-2.
Continued
47-12 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
68P02901W26-S 47-13
Nov 2007
13. XBL: LAPD protocol error threshold exceeded Chapter 47: XBL Alarms
Description
The LAPD Layer 2 protocol error threshold was exceeded 30 times during a one-minute period.
System action
A one-byte code is displayed in the Additional information field in the output for this alarm, as
shown in Table 47-3. The code indicates the cause for the alarm.
Possible causes
47-14 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R Procedure
Procedure
Wait for 10 minutes after the alarm is reported before continuing with this procedure.
If an RXCDR reboots, this delay allows sufficient time for the reboot process to
complete.
Continued
68P02901W26-S 47-15
Nov 2007
Procedure Chapter 47: XBL Alarms
47-16 68P02901W26-S
Nov 2007
Maintenance Information: Alarm Handling at the OMC-R 15. XBL: Too many LAPD protocol errors
Description
Too many LAPD protocol errors are received indicating poor link quality.
6 bytes: byte 1 - MMS timeslot, byte 2 - LAPD fault code, bytes 3 to 6 - MMS device ID.
Possible causes
Four or more LAPD protocol errors are received within one second indicating major problems
with the XBL link.
Procedure
1 Check report logs for repeated occurrence of this alarm. If the alarm
occurs more than expected, monitor the state of the MMS related to the
XBL and INS the XBL device. A field representative may need to visit the
site to determine the quality of the link and adjust or correct or replace
it as necessary.
2 Refer alarm handling at the OMC customer documentation.
3 Investigate the XBL further if this keeps happening.
68P02901W26-S 47-17
Nov 2007
16. XBL: HDLC channel open failed Chapter 47: XBL Alarms
Description
The Central Authority (CA) reports that the HDLC channel has failed to open.
Possible causes
Procedure
If... Then...
47-18 68P02901W26-S
Nov 2007
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02901W26-S IX-19
Nov 2007
Index
IX-20 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-21
Nov 2007
Index
IX-22 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-23
Nov 2007
Index
IX-24 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-25
Nov 2007
Index
IX-26 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-27
Nov 2007
Index
IX-28 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-29
Nov 2007
Index
IX-30 68P02901W26-S
Nov 2007
Index
EEPROM SW flash programming failure (contd.) erroneous Layer 3 message received by the BSS
DHP 50 alarm . . . . . . . . . . . . . . 15-53 BSS 10 alarm . . . . . . . . . . . . . . 6-26
DHP 51 alarm . . . . . . . . . . . . . . 15-54 erroneous Layer 3 message received by the SMLC
GPROC 50 alarm . . . . . . . . . . . . 23-46 BSS 53 alarm . . . . . . . . . . . . . . 6-67
GPROC 51 alarm . . . . . . . . . . . . 23-47 event management
EGPRS - Unavailable - Insufficient GDS Available alarm messages . . . . . . . . . . . . . . 1-3
CELL 17 alarm . . . . . . . . . . . . . 12-42 event messages . . . . . . . . . . . . . . 1-3
EGPRS unavailable - No 64K PDCHs available exceeds lower limit disk usage
CELL 19 alarm . . . . . . . . . . . . . 12-48 OMC 30011 alarm . . . . . . . . . . . 32-36
EMDisconnectedFromDB exceeds upper limit disk usage
OMC 30008 alarm . . . . . . . . . . . 32-28 OMC 30010 alarm . . . . . . . . . . . 32-33
environmental variables expiration of N2
CONSOLIDATION. . . . . . . . . . . . . 1-5 CBL 2, PM alarm . . . . . . . . . . . . 10-7
EPSM, power supply module GSL 2, PM alarm . . . . . . . . . . . . 24-7
BCUP alarms . . . . . . . . . . . . . . . 4-2 OML 2, PM alarm . . . . . . . . . . . . 33-7
equalizer configuration mismatch RSL 2, PM alarm . . . . . . . . . . . . 40-7
DRI 168 alarm . . . . . . . . . . . . 17-249 XBL 2, PM alarm . . . . . . . . . . . . 47-7
equalizer control processor failure - watchdog external combiner main fuse failure
timer expired IAS 20 alarm . . . . . . . . . . . . . . 25-28
DRI 70 alarm . . . . . . . . . . . . . 17-121 external combiner redundant fuse failure
equalizer failure IAS 21 alarm . . . . . . . . . . . . . . 25-30
DRI 214 . . . . . . . . . . . . . . . . 17-280 external power booster amplifier 1 failure
equalizer firmware failure CAB 25 alarm . . . . . . . . . . . . . . . 8-3
DRI 184 alarm . . . . . . . . . . . . 17-259 SITE 25 alarm. . . . . . . . . . . . . . 42-64
equalizer output overflowed external power booster amplifier 2 failure
DRI 159 alarm . . . . . . . . . . . . 17-231 CAB 26 alarm . . . . . . . . . . . . . . . 8-5
DRI 160 alarm . . . . . . . . . . . . 17-233 SITE 26 alarm. . . . . . . . . . . . . . 42-66
equalizer timeslot 0 failure external power booster failure
DRI 176 alarm . . . . . . . . . . . . 17-257 CAB 27 alarm . . . . . . . . . . . . . . . 8-7
erroneous BSSGP message received from the SITE 27 alarm. . . . . . . . . . . . . . 42-68
SGSN . . . . . . . . . . . . . . . . . . . 42-81
68P02901W26-S IX-31
Nov 2007
Index
IX-32 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-33
Nov 2007
Index
IX-34 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-35
Nov 2007
Index
IX-36 68P02901W26-S
Nov 2007
Index
M-Cell Micro interconnect failure master HDSL modem loop 0 SNR OOS threshold
DRI 170 alarm . . . . . . . . . . . . 17-253 exceeded
mains ac supply failure MMS 35 alarm . . . . . . . . . . . . . 29-72
IAS 102 alarm. . . . . . . . . . . . . 25-121 master HDSL modem loop 1 SNR daily threshold
manual organization exceeded
introduction . . . . . . . . . . . . . . . . 1-2 MMS 28 alarm . . . . . . . . . . . . . 29-58
map display colours . . . . . . . . . . . . 1-20 master HDSL modem loop 1 SNR hourly threshold
master CBUS signal provided by slave GCLK exceeded
CBUS 2 alarm . . . . . . . . . . . . . . 11-5 MMS 32 alarm . . . . . . . . . . . . . 29-66
master HDSL modem loop 0 SNR daily threshold master HDSL modem loop 1 SNR OOS threshold
exceeded exceeded
MMS 27 alarm . . . . . . . . . . . . . 29-56 MMS 36 alarm . . . . . . . . . . . . . 29-76
master HDSL modem loop 0 SNR hourly threshold matrix control redundant fuse failure
exceeded IAS 17 alarm . . . . . . . . . . . . . . 25-22
MMS 31 alarm . . . . . . . . . . . . . 29-64
68P02901W26-S IX-37
Nov 2007
Index
IX-38 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-39
Nov 2007
Index
no cell (BVC) block acknowledgement from the no NS-VC reset acknowledgement from the
SGSN SGSN . . . . . . . . . . . . . . . . . . . 42-88
CELL 5 alarm . . . . . . . . . . . . . . 12-19 no NS-VC unblock acknowledgement from the
no clock references available SGSN . . . . . . . . . . . . . . . . . . . 42-85
SITE 21 alarm. . . . . . . . . . . . . . 42-55 No PM database fragment available
no connection to alarm board - alarm board OMC 30067 alarm . . . . . . . . . . 32-109
removed no redundant connection to alarms board - radio
IAS 99 alarm . . . . . . . . . . . . . 25-115 OOS
no connection to alarm board - radio OOS IAS 98 alarm . . . . . . . . . . . . . 25-113
IAS 97 alarm . . . . . . . . . . . . . 25-111 no SMLC acknowlegement for global reset
no connection to alarms board - connection BSS 52 alarm . . . . . . . . . . . . . . 6-66
broken noActivityInTimeslot
IAS 94 alarm . . . . . . . . . . . . . 25-105 OMC 30060 alarm . . . . . . 32-101, 32-103
no MSC acknowledgement for circuit block non-volatile memory failure
BSS 5 alarm. . . . . . . . . . . . . . . 6-15 BTP 237 alarm . . . . . . . . . . . . . 7-49
no MSC acknowledgement for circuit unblock DRI 237 alarm . . . . . . . . . . . . 17-305
BSS 6 alarm. . . . . . . . . . . . . . . 6-17 not operational
no MSC acknowledgement for global reset GCLK 18 alarm . . . . . . . . . . . . . 21-38
BSS 9 alarm. . . . . . . . . . . . . . . 6-25 number of calls queued
no MSC acknowledgement for reset circuit CELL 20, PM alarm . . . . . . . . . . . 12-51
BSS 7 alarm. . . . . . . . . . . . . . . 6-19 number of octets retransmitted
no NS-VC alive acknowledgement from the MTL 9, PM alarm . . . . . . . . . . . . 31-21
SGSN . . . . . . . . . . . . . . . . . . . 42-86 number of signal units in error
no NS-VC Block acknowledgement from the MTL 6, PM alarm . . . . . . . . . . . . 31-17
SGSN . . . . . . . . . . . . . . . . . . . 42-84 NVM board failure
SITE 30 alarm. . . . . . . . . . . . . . 42-75
IX-40 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-41
Nov 2007
Index
IX-42 68P02901W26-S
Nov 2007
Index
power supply unit#3 not detected (contd.) processor bus communication failure (contd.)
CAGE 33 alarm . . . . . . . . . . . . . 9-11 BSP 232 alarm . . . . . . . . . . . . . 5-43
power supply unit#3 output failure BTP 232 alarm . . . . . . . . . . . . . 7-40
CAGE 30 alarm . . . . . . . . . . . . . . 9-9 DHP 232 alarm . . . . . . . . . . . . . 15-57
power supply unit#3 over-temperature GCLK 232 alarm . . . . . . . . . . . . 21-52
CAGE 39 alarm . . . . . . . . . . . . . 9-15 GPROC 232 alarm. . . . . . . . . . . . 23-50
primary alarm. . . . . . . . . . . . . . . . 1-5 KSW 232 alarm . . . . . . . . . . . . . 26-60
primary message or hardware interrupt error MSI 232 alarm . . . . . . . . . . . . . 30-28
DRI 18 alarm . . . . . . . . . . . . . . 17-36 processor communication failure
process safe test audit failure DPROC 0 alarm . . . . . . . . . . . . . 16-3
BSP 239 alarm . . . . . . . . . . . . . 5-44 processor failure
BTP 239 alarm . . . . . . . . . . . . . 7-51 DRI 29 alarm . . . . . . . . . . . . . . 17-57
DHP 239 alarm . . . . . . . . . . . . . 15-61 PSP 0 alarm, Communication Failure . . . 39-3
DPROC 239 alarm. . . . . . . . . . . . 16-11 PSP 22 alarm
DRI 239 alarm . . . . . . . . . . . . 17-307 SWFM indication . . . . . . . . . . . . 39-5
GPROC 239 alarm. . . . . . . . . . . . 23-51 PSP 239 alarm
PSP 239 alarm . . . . . . . . . . . . . 39-8 process safe test audit failure . . . . . . 39-8
processor A failure PSP 39 alarm
COMB 14 alarm . . . . . . . . . . . . . 13-27 software failure . . . . . . . . . . . . . 39-6
processor B failure PSP alarms
COMB 15 alarm . . . . . . . . . . . . . 13-29 FRUs . . . . . . . . . . . . . . . . . . 39-2
processor bus communication failure introduction . . . . . . . . . . . . . . . 39-2
Q3 agent . . . . . . . . . . . . . . . . . . 1-7
radio frequency losses while using a TCH received maximum corrupt NE msgs, closed OML
TIMESLOT 0, PM alarm. . . . . . . . . 45-3 OMC 30030 alarm . . . . . . . . . . . 32-74
radio frequency losses while using an SDCCH received page for invalid cell from MSC
CELL 0, PM alarm . . . . . . . . . . . 12-6 BSS 26 alarm . . . . . . . . . . . . . . 6-38
radio subsystem software to DRI communication received page for invalid cell from SMLC
error received page for invalid cell from SMLC
DRI 76 alarm . . . . . . . . . . . . . 17-132 MSC . . . . . . . . . . . . . . . . . . 6-69
radio subsystem software to DRI communication receiver failure
error - checksum error DRI 119 alarm . . . . . . . . . . . . 17-182
DRI 65 alarm . . . . . . . . . . . . . 17-113 DRI 120 alarm . . . . . . . . . . . . 17-184
radio subsystem software to DRI communication DRI 121 alarm . . . . . . . . . . . . 17-186
failure DRI 122 alarm . . . . . . . . . . . . 17-188
DRI 22 alarm . . . . . . . . . . . . . . 17-43 DRI 123 alarm . . . . . . . . . . . . 17-190
DRI 23 alarm . . . . . . . . . . . . . . 17-45 DRI 124 alarm . . . . . . . . . . . . 17-192
RCU #5 circuit breaker failure DRI 125 alarm . . . . . . . . . . . . 17-194
IAS 61 alarm . . . . . . . . . . . . . . 25-67 DRI 126 alarm . . . . . . . . . . . . 17-196
re-initialized unexpectedly DRI 127 alarm . . . . . . . . . . . . 17-198
KSW 7 alarm . . . . . . . . . . . . . . 26-27 DRI 128 alarm . . . . . . . . . . . . 17-200
MSI 0 alarm. . . . . . . . . . . . . . . 30-3 DRI 72 alarm . . . . . . . . . . . . . 17-125
receive matrix branch 2 control link failure receiver input overflowed
DRI 162 alarm . . . . . . . . . . . . 17-237 DRI 157 alarm . . . . . . . . . . . . 17-227
receive matrix failure DRI 158 alarm . . . . . . . . . . . . 17-229
DRI 150 alarm . . . . . . . . . . . . 17-213 receiver synthesizer failure
DRI 112 alarm . . . . . . . . . . . . 17-168
68P02901W26-S IX-43
Nov 2007
Index
IX-44 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-45
Nov 2007
Index
slave HDSL modem loop 1 SNR hourly threshold superframe counter error
exceeded DRI 6 alarm . . . . . . . . . . . . . . . 17-18
MMS 34 alarm . . . . . . . . . . . . . 29-70 DRI 66 alarm . . . . . . . . . . . . . 17-116
slow flash failure supplDownloadFailed
BTP 236 alarm . . . . . . . . . . . . . 7-47 OMC 30027 alarm . . . . . . . . . . . 32-69
DRI 236 alarm . . . . . . . . . . . . 17-303 SWFM indication
SMLC processor outage BSP 22 alarm . . . . . . . . . . . . . . 5-13
LMTL 1 alarm . . . . . . . . . . . . . . 28-8 BTP 22 alarm . . . . . . . . . . . . . . 7-13
smoke alarm CSFP 22 alarm . . . . . . . . . . . . . 14-3
IAS 92 alarm . . . . . . . . . . . . . 25-101 DHP 22 alarm . . . . . . . . . . . . . . 15-12
software failure DPROC 22 alarm . . . . . . . . . . . . 16-7
BSP 39 alarm . . . . . . . . . . . . . . 5-28 GPROC 22 alarm . . . . . . . . . . . . 23-14
BTP 39 alarm . . . . . . . . . . . . . . 7-28 PSP 22 alarm . . . . . . . . . . . . . . 39-5
DHP 39 alarm . . . . . . . . . . . . . . 15-39 switching hardware required kb/s
DPROC 39 alarm . . . . . . . . . . . . 16-8 switching hardware required 16kb/s . . 42-44
GPROC 39 alarm . . . . . . . . . . . . 23-34 SYNC calibration request
PSP 39 alarm . . . . . . . . . . . . . . 39-6 DHP 26 alarm . . . . . . . . . . . . . . 15-19
Solaris2 hardware failure GPROC 26 alarm . . . . . . . . . . . . 23-18
OMC 30050 alarm . . . . . . . . . . . 32-93 SYNC clock output failure
spare fuse failure DHP 28 alarm . . . . . . . . . . . . . . 15-23
IAS 30 alarm . . . . . . . . . . . . . . 25-40 GPROC 28 alarm . . . . . . . . . . . . 23-20
spurious GSM timeslot interrupt SYNC invalid mode
DRI 50 alarm . . . . . . . . . . . . . . 17-82 DHP 46 alarm . . . . . . . . . . . . . . 15-48
spurious interrupt SYNC lost phase lock to master GCLK
BSP 40 alarm . . . . . . . . . . . . . . 5-30 DHP 23 alarm . . . . . . . . . . . . . . 15-13
BTP 40 alarm . . . . . . . . . . . . . . 7-30 GPROC 23 alarm . . . . . . . . . . . . 23-15
DHP 40 alarm . . . . . . . . . . . . . . 15-41 SYNC not operational
GPROC 40 alarm . . . . . . . . . . . . 23-36 DHP 43 alarm . . . . . . . . . . . . . . 15-43
standby link connected to wrong device SYNC phase lock failure
DRI 241 alarm . . . . . . . . . . . . 17-310 DHP 45 alarm . . . . . . . . . . . . . . 15-46
standby link connection failure SYNC shutdown request
BTP 235 alarm . . . . . . . . . . . . . 7-44 DHP 27 alarm . . . . . . . . . . . . . . 15-21
DRI 235 alarm . . . . . . . . . . . . 17-301 GCLK 17 alarm . . . . . . . . . . . . . 21-36
standby local FOX failure GPROC 27 alarm . . . . . . . . . . . . 23-19
SITE 10 alarm. . . . . . . . . . . . . . 42-30 SYNC warm up failure
standby multiplexer 0 loopback failure GPROC 25 alarm . . . . . . . . . . . . 23-17
SITE 4 alarm . . . . . . . . . . . . . . 42-17 SYNC warmup failure
standby multiplexer 1 loopback failure DHP 25 alarm . . . . . . . . . . . . . . 15-17
SITE 6 alarm . . . . . . . . . . . . . . 42-21 SYNC watchdog timer expired
standby multiplexer 2 loopback failure DHP 29 alarm . . . . . . . . . . . . . . 15-25
SITE 8 alarm . . . . . . . . . . . . . . 42-26 GPROC 29 alarm . . . . . . . . . . . . 23-21
standby remote FOX 0 failure synchronization loss daily threshold exceeded
SITE 12 alarm. . . . . . . . . . . . . . 42-34 MMS 0 alarm . . . . . . . . . . . . . . 29-5
standby remote FOX 1 failure synchronization loss hourly threshold exceeded
SITE 14 alarm. . . . . . . . . . . . . . 42-38 MMS 1 alarm . . . . . . . . . . . . . . 29-7
standby remote FOX 2 failure synchronization loss OOS threshold exceeded
SITE 16 alarm. . . . . . . . . . . . . . 42-42 MMS 2 alarm . . . . . . . . . . . . . . 29-9
start of remote processor outage synchronization loss OOS timer expired
MTL 8, PM alarm . . . . . . . . . . . . 31-20 MMS 16 alarm . . . . . . . . . . . . . 29-31
state change warning alarms . . . . . . . . 1-7 synchronization loss with MCU
super frame counter error DRI 39 alarm . . . . . . . . . . . . . . 17-73
DRI 5 alarm . . . . . . . . . . . . . . . 17-16
IX-46 68P02901W26-S
Nov 2007
Index
68P02901W26-S IX-47
Nov 2007
Index
IX-48 68P02901W26-S
Nov 2007
Standard Printing Instructions
Finishing • A4 size (210mm x 297mm) clear PVC sheet front page for
protection.
• Bag wrapped with clear polythene.
Maintenance Information
GSR9
NOV 2007
68P02901W26-S
GSR9
NOV 2007
68P02901W26-S
Cutting
datum point