Alarms Guide

3AG 24197 ABAA Edition 02
1
Alcatel
1678MCC Rel.
3.1A
Metro Core Connect
ALARM REFERENCE GUIDE
3AG 24197 ABAA Edition 02 - April 2005
I
Table of Contents
1 Introduction 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General Information 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Purpose of the Handbook 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Target Audience 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Handbook Structure 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Product Release Handbooks 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Safety Norms and Labels 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 General on Alcatel Customer Documentation 4 . . . . . . . . . . . . . . . . . .
1.8 Symbols 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9 Registered Trademarks 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10 Service Information 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11 Terminology 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12 Handbook Change History 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Preview to Alarms 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Current Alarms Management 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Alarm Counter 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Alarm Information 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Perceived Severity 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Event Date & Time 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 Friendly Name 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 Event Type 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.5 Probable Cause 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6 Reservation Status 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.7 Clearing Status 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.8 Acknowledgement Status 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.9 Correlated Notification Flag 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.10 Repetition Counter 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
II
2.4 Alarm Severity Assignment Profile (ASAP) 14 . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Default and Freeuse ASAPs 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Service Dependency 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.3 Severity 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.4 Contents of Predefined ASAPs on the 1678MCC 17 . . . . . . . . . . . . . . . . . . . . .
2.5 Mapping Tables: TP Names on Craft Terminal 21 . . . . . . . . . . . . . . . . . .
3 Correlation Element Type - Event Type 23 . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Equipment Alarms/Processing Error Alarms 31 . . . . . . . . . . . . . . . . . . . . . .
4.1 Battery Failure (BF) 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Communications Subsystem Failure (CSF) 35 . . . . . . . . . . . . . . . . . . . . . .
4.3 Fuse Failure (FF) 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 High Temperature (HT) 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Internal Communication Problem (ICP) 44 . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Input Power Loss (IPL) 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 LAN Failure (LAN) 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 No RTC Synchronization (NRTCS) 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 Optical Connector Cover Open (OCCO) 52 . . . . . . . . . . . . . . . . . . . . . .
4.10 Pump Failure (PF) 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11 Resource Isolation (Q3) 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12 Redundant Clock Fail A/B (RCFA/B) 55 . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.13 Redundant Matrix A/B Failure (RMFA/B) 57 . . . . . . . . . . . . . . . . . . . . . . .
4.14 Replaceable Unit Missing (RUM) 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.15 Replaceable Unit Problem (RUP) 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.16 Replaceable Unit Type Mismatch (RUTM) 79 . . . . . . . . . . . . . . . . . . . . . . .
4.17 Software Download Failure (SDF) 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.18 Software Environment Problem (SEP) 82 . . . . . . . . . . . . . . . . . . . . . . . . . .
4.19 Timing Problem (TIP) 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
III
5 Communications Alarms/ Processing Error Alarms 85 . . . . . . . . . . . . . . . .
5.1 Abstract 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Alarm Indication Signal (AIS) 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Communication Protocol Error (CPE) 90 . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Degraded Signal (DS) 91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Loss of Alignment (LOA) 96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Loss of Frame (LOF) 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Loss of MultiFrame (LOM) 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Loss of Pointer (LOP) 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9 Loss of Signal (LOS) 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.10 Payload Type Mismatch (PLTM) 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11 Remote Defect Indication (RDI) 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12 Sequence (Number) Mismatch (SQM) 114 . . . . . . . . . . . . . . . . . . . . . . . . .
5.13 Server Signal Fail (SSF) 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.14 Trace Identifier Mismatch (TIM) 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.15 Transmitter Degraded (TD) 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.16 Transmitter Failure (TF) 125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.17 Unavailable Time (UAT) 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.18 Underlying Resource Unavailable (URU) 129 . . . . . . . . . . . . . . . . . . . . . . .
5.19 Unequipped (UNEQ) 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 Quality of Service Alarms 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1 Introduction
1.1 General Information
WARNING
Strict compliance with the instructions and procedures spe
cified in the product documentation (see product release
note for the complete list of applicable manuals) is the pre
condition of the enforceability of such warranty claims
against Alcatel.
Warranty claims which result from noncompliance with
the defined procedures, cannot be enforced against Alcatel.
NOTICE
The product specification and/or performance levels con
tained in this document are for information purposes only
and are subject to change without notice. They do not repre
sent any obligation on the part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of
ALCATEL and must not be copied, reproduced or disclosed
to a third party without written consent.
1.2 Purpose of the Handbook
This handbook refers to the Multiband Multiservice
Connect Alcatel 1678 Metro Core Connect (1678MCC)
which belongs to the Alcatel Intelligent Optical Networks
(ION) product family.
In general the system is referred to as 1678MCC or NE
(Network Element) only.
The aim of this handbook is to list all alarms coming from
the 1678MCC and being indicated by the Alarm Manager.
For each alarm the possible causes, its effects on service and
the ways to get out of the alarm situation are described.
The use of this handbook is indicated in the list of the
"Handbooks related to the specific software application",
in the Technical and Operator's Handbook of the Network
Element.
2
Being the document dedicated to a set of equipment,
screens are inserted as "example" and can be extracted
from any of the referred equipment.
This handbook must be used together with the associated
Technical and Operator's Handbooks and does not repli
cate information contained into them.
In particular, all cautions relevant to safety, rules for EMC
and ESD, as well as warnings regarding operations that
may cause damages to the equipment, are not duplicated
here, but must be retrieved from the Technical Handbook.
When using this handbook it is assumed that the Operators
knows:
- the structure (hardware composition) and all the
possible operating modes of the equipment
(productrelease) this handbook refers to.
- how to use the Craft Terminal (CT)
- how to use the dialog of the Alarm Surveillance
component (refer to 1330AS Rel 6.5 Operator's
Handbook", 3AG 88876 AAAA)
1.3 Target Audience
This handbook is intended for operator's concerned with
managing the 1678MCC.
1.4 Handbook Structure
This handbook is divided into the following main topics as
described in the table of contents:
- Introduction
containing general information about structure and
use of the handbook, and safety norms on using the
equipments.
- Preview to Alarms
providing general information on alarms and alarm
handling
- Correlation Element Type - Event Type
providing an overview on which alarm (i.e. event
3
type) is possibly reported for which board or
Termination Point (i.e. element type)
- Equipment Alarms / Processing Error Alarms
describing for each Equipment alarm the possible
causes, the effects on service and the ways to get out
of the alarm situation
- Communications Alarms / Processing Error Alarms
describing for each Communications alarm the
possible causes, the effects on service and the ways to
get out of the alarm situation
- Quality of Service Alarms
describing for each Quality of Service alarm the
possible causes, the effects on service and the ways to
get out of the alarm situation
1.5 Product Release Handbooks
Refer to the Technical Handbook for a list of the com
plete set of Customer Documentation.
1.6 Safety Norms and Labels
Refer to the Safety Instructions, 3AG 24198 AAAA, to
obtain the following information:
- FIRST AID FOR ELECTRIC SHOCK
- COMPLIANCE WITH EUROPEAN NORMS.
- SAFETY RULES
D General rules
D Harmful optical signals
D Risk of explosion
D Moving mechanical parts
D Heat-radiating Mechanical Parts
- ELECTROMAGNETIC COMPATIBILITY
- ELECTROSTATIC DISCHARGERS (ESD)
- EQUIPMENT LABELS
4
1.7 General on Alcatel Customer Documentation
Refer to the Technical Handbook to obtain the following
information:
- Definition of the terms Product, Product Release
and Version
- Handbook supply to Customers
- Aims of standard Customer Documentation
- Handbook Updating
- Customer Documentation supply on CD-ROM
1.8 Symbols
This handbook uses the following symbol:
This symbol is used to emphasize particularly important in
formation.
1.9 Registered Trademarks
Refer to the Technical Handbook for a list of registered
trademarks.
1.10 Service Information
In case of problems with the 1678MCC, please contact your
Customer Support Center for information.
1.11 Terminology
Refer to the Basic Operator's Handbook for abbrevia
tions and glossary.
5
1.12 Handbook Change History
Ed. 02:
The main updates for Ed.02 created in April, 2005 for prod
uct release 3.1A PL1. are:
- SLSks34818 -> added note in chapter SSF and
Correlation.
- Added Equipment Alarms for modules
- Updates for CT20.2.2 - 20.2.9
- Updates from Board Names list (Ed. 6A/1A)
Ed. 01:
Ed.01 created in December, 2004 is the first qualified and
release edition associated to product release 3.1A.
Edition 01 has been created based on ALCATEL 1678 MCC
Rel 3.0 Alarm Reference Guide, 3AG 24197 AAAA, Ed. 02.
- MSP alarms
- Assembler TP alarms (LAX40/20)
- Alarms for OED 1662 and GbE
6
7
2 Preview to Alarms
For the Alarm Management the Alarm Surveillance (AS),
which is a generic component of the ALMAP product, is
used. A complete user guide of the AS can be found in the
1330AS Rel. 6.5 Operator's Handbook", which is also
available as online help. To open the online help use the
Help" menu of the AS dialogs.
In this chapter only a short overview of the main functional
ity of the Alarm Management is provided.
2.1 Current Alarms Management
When an alarm is raised by a resource (or by a neighboring
one) detecting a fault, it is received by the Alarm Surveil
lance which stores it and warns the operator by ringing a
bell or by the appearance of a specific icon on the screen.
The alarm may be displayed as soon as it is signalled accord
ing to the operator needs.
During the whole period an alarm is considered to be
current (CLR or NCLR), its state is permanently realtime
refreshed so that any operator who displays the alarm is
informed if it has been reserved or not, if it has been
acknowledged or not, if a trouble ticket has been requested
for this alarm or not.
The alarm is cleared by the emitting resource as soon as
the problem is no longer present at the resource. Then the
alarm is no longer considered as a current alarm and as
soon as it is acknowledged by the operator it disappears
from the current alarm set and is archived to the set of
historical alarms.
Deleted alarms also disappear from the sublist (or Main
List) and are archived, if matching the archiving filter.
However, the problem to which the alarm is linked may not
be solved immediately. In such a case the alarm is repeated
after a while until the problem is solved. Alarm Surveillance
associates a repetition counter to each received alarm.
Furthermore, if the alarm is not cleared at all by the re
source which raised it before for any reason, the Alarm Sur
veillance offers the possibility to archive it manually on the
operator's request.
8
2.2 Alarm Counter
Available global information is displayed by counters that
show the number of alarms of a single severity level as well
as the total number of alarms in the sublist, and the number
of non acknowledged and cleared alarms. These counters
may be realtime refreshed (when the sublist is active) or
not (when the sublist is inactive).
After confirming unacknowledged alarms, the alarm
counter are changed as follows:
- NACK" is decreased according to the number of
confirmed alarms
- ACK" is increased according to the number of
confirmed alarms
Clear" is increased as soon as an alarm is cleared.
Figure 1 Example of Sublist Displaying Unacknowledged Alarms
9
Because of the overwrite behavior in the alarm lists (auto
matic deletion of old alarms by the system in order to create
new memory capacity) or after manual deletion of alarms
by the operator, an existing alarm correlation may not be
visible anymore, i.e. the begin alarm is deleted, but the cor
responding end alarm is still part of the unacknowledged
alarm list.
10
2.3 Alarm Information
Alarms or Alarm notifications consist in messages
emitted by resources that have detected problems or
failures. Information contained in the alarm includes
- information that identifies the resource which has
raised the alarm
- information that identifies the type of the problem
the alarm refers to.
Note that these pieces of information are mandatory in any
alarm notification, as well as the date and time the alarm
has been raised by the resource. Other optional information
such as the specific problems the alarm is linked to, the noti
fication identifier, etc., may also be present to help the
operator in the alarm management process.
The operator can create alarm sublists accustomed to his/
her preferences, including filtering and display of alarm in
formation. For more information about alarm management
and alarm (sub)lists refer to the 1330 AS Rel. 6.5 Opera
tor's Handbook.
To obtain more information about the element that has re
ported the alarm, it is possible to navigate to this element:
- Mark the alarm in the alarm list and select External
Application > emlusm" of the Navigation" menu.
Depending on the Event Type the Equipment or Transmis
sion View is opened and the affected element is selected (i.e.
framed in orange).
In these Views you can also access the Alarm Reference
Guide (this handbook) as online description:
- Select Tutorial" from the Help" menu.
- A confirmation box appears asking whether or not to
open Netscape. Confirm to open Netscape.
- When the Netscape window has opened, click on the
link Alarm Reference Guide" to navigate to the
table of contents. From there you can navigate to the
alarm for which you want detailed information.
11
2.3.1 Perceived Severity
The entry Perceived Severity indicates the severity level of
the problem when the alarm is raised. Malfunctions are
ranked into five severity levels:
- Critical,
when it is no longer possible to provide the service
requested by the user, e.g. it is applied for "server"
boards in cases where more than one "client" board
is affected by this failure (due to an underlying
serverclient relationship).
- Major,
- Minor,
- Warning, which means no impact is reported upon
the quality of service offered to the user,
- Indeterminate, if the severity level cannot be defined
by the resource which raises the alarm. (Possible
reason are incorrect ASAP settings.)
- Cleared, if the alarm is cleared by the resource which
has raised it before.
2.3.2 Event Date & Time
This entry indicates date and time when the alarm was
raised on the resource.
The data is displayed as YYYY/MM/DD hh:mm:ss
E.g. 2004/05/20 06:29:24 indicates an alarm that was risen
at 29 minutes and 24 seconds past six o'clock in the
morning, on the 20th of may 2004.
12
2.3.3 Friendly Name
With the help of the friendly name it is possible to locate the
element that has reported the alarm.
The friendly name includes information about the NE and
the location of the element where the alarm was risen. De
pending on the alarm's event type, the element type can
be a board or a TP. For equipment alarms the location is giv
en down to board level. Communication and quality of ser
vice alarms include a further entry identifying the port and
the TP. Quality of service alarms also provides an alarm
type giving threshold crossing information.
The general format of the friendly name equals
NE/rack#subrack#slot#/port#TP
If we take the marked entry from Figure 1 as an example:
Anlage84/r01sr2sl16/port#01ElRsCTP
indicates an alarm raised by ElRsCTP on port 1 of the board
on slot 16 in subrack 2 of rack 1of NE Anlage 84".
2.3.4 Event Type
The entry Event Type" indicates the alarm type taken out
of the following ones:
- Quality of Service
- Communications
- Processing Error
- Equipment
- Environmental Alarms
Hardware or control system errors are reasons for an
Equipment alarm, Environmental alarm or Process
ing Error alarm. Transmission errors are the reason for
Communication alarms. Threshold problems are the
reason for Quality of Service alarms.
2.3.5 Probable Cause
The probable cause indicates the error reason (e.g. Loss of
Frame).
13
2.3.6 Reservation Status
The operator can reserve a current alarm to make sure to
be the only responsible for this alarm. In this case the
reservation status of the selected alarm changes from
NRSV (non reserved) to RSV (reserved).
An alarm can only be unreserved by the operator who has
reserved it before.
2.3.7 Clearing Status
A current alarm that has not been solved is indicated as
NCLR (not cleared). As soon as the problem is no longer
present at the resource, its status changes to CLR
(cleared).
2.3.8 Acknowledgement Status
Unacknowledged alarms are marked NACK in the list and
can be confirmed by the operator. The statuses of the se
lected alarms change, passing from NACK (non acknowl
edged) to ACK (acknowledged).
Note that acknowledging a cleared alarm is an implicit
archiving action. Thus, the acknowledgement actually
archives the alarm and causes its disappearance from the
current alarm list.
2.3.9 Correlated Notification Flag
If a correlation notification is sent together with the re
ported alarm, this flag will be set to YES.
2.3.10 Repetition Counter
The repetition counter indicates the number of times an
alarm was sent by a resource.
14
2.4 Alarm Severity Assignment Profile (ASAP)
An ASAP is a list containing probable alarm causes to which
severities are assigned according to their service dependen
cy. Alarms are indicated at the CT according to the assigned
ASAP, displaying the assigned severity, or are not indicated
at all. I.e. the ASAP is used as an alarm filter.
2.4.1 Default and Freeuse ASAPs
There are two types of ASAPs:
- the predefined default ASAPs which include all
potential probable causes/severities raised by the NE.
These ASAPs are defined as readonly, i.e. it is not
possible to modify their contents and it is not
possible to remove them.
- the user defined ASAP created by the user. A user
defined ASAP can also be removed by the managing
system.
The number of severities and of probable causes is
fixed. Their characteristics cannot be modified. The
ASAP function only enables the modification of the se
verities assigned to the probable causes, it does not al
low the addition, removal or modification of the prob
able causes themselves.
The following five ASAPs are configured as default
ASAPs:
- ASAP: No Alarms
This ASAP inhibits the alarm indication.
This is the default ASAP for
D PPITTP
D VC4 TTP, VC12 TTP
D E4 CTP, E1 CTP,
D AU4 CTP and concatenated, AU3 CTP
D PTC
D VC4XV TTP
15
D VC-4V TTP
- ASAP: Primary Alarms
This ASAP enables the indication of all primary
communication alarms (AIS, SSF and RDI are
disabled) and equipment alarms.
This is the default ASAP for
D equipment alarms
D ESTTP, OSTTP
D RSTTP
D GMAUTTP
D P4CTP, P12 CTP
D TrailMonitor (POM)
D SupervisoryUnequippedMonitor (SUT)
D UAT Alarms
- ASAP: No Remote Alarms
This ASAP enables the indication of all primary
communication alarms plus SSF (AIS and RDI are
disabled) and equipment alarms.
- ASAP: All Alarms
This ASAP enables the indication of all alarms.
This is the default ASAP for MSTTP.
- ASAP: No Server Alarms
This ASAP enables the indication of all alarms except
SSF, Redundant Clock Fail A/B and Redundant
Matrix A/B Failure.
2.4.2 Service Dependency
Depending on its effect on service, each probable cause can
be assigned an alarm severity in the ASAP. This is called ser
vice dependency.
There are three service dependency types:
- Service Affecting
- Non Service Affecting
- Service Independent.
16
Some restrictions apply to the assignment of a severity to
service dependency. Table 1 lists all the different allowed
cases of severity assignment and service dependency.
Case Service Affecting Non Service Affecting Service Independent
1 critical or major
minor or warning or non
alarmed
not used
2 critical or major not used not used
3 not used
minor or warning or non
alarmed
not used
4 not used not used
critical or major or minor
or warning or non
alarmed
Table 1 Permissible Assignment of Service Dependency and Severity
Note, that the 1678MCC handles the service dependency
types service affecting" and non service affecting" only in
respect of Replaceable Unit Missing (RUM) alarms (plug
out of a board). All other alarms are handled with severity
type service independent". This means that when cloning
an ASAP, cases 1 to 3 of Table 1 can only be applied to RUM
alarms (it is recommended to use Case 1 if RUM should ap
pear as alarm and Case 3 if RUM should not appear as
alarm). All other alarms should be configured according to
Case 4.
2.4.3 Severity
Objects (TPs and Equipment) emitting alarms reference to
default ASAPs with exception of the following cases:
- Whenever an object cannot evaluate the ASAP, e.g.
due to a wrong provisioning of the manager, the
alarm is emitted with the severity indeterminate".
17
2.4.4 Contents of Predefined ASAPs on the 1678MCC
The 1678MCC handles the service dependency types ser
vice affecting" (SA) and non service affecting" (NSA) only
for replaceable unit missing (RUM) alarms (plug out of a
board). All other alarms are handled with severity type
service independent". Therefore, in the following tables,
SA and NSA severity dependency is only mentioned for this
alarm.
ASAP
Probable Cause
No Alarms Primary
Alarms
No
Remote
Alarms
All Alarms No Server
Alarm
Backplane Failure NAL MAJ MAJ MAJ MAJ
Internal Communication Prob-
lem
NAL WAR WAR WAR WAR
Lan Failure NAL MIN MIN MIN MIN
Replaceable Unit Missing (SA) NAL MAJ MAJ MAJ MAJ
Replaceable Unit Missing
(NSA)
NAL MIN MIN MIN MIN
Replaceable Unit Problem NAL MAJ MAJ MAJ MAJ
Replaceable Unit Type
Mismatch
NAL WAR WAR WAR WAR
Synchronization Source Mis-
match
NAL MIN MIN MIN MIN
Timing Problem NAL MAJ MAJ MAJ MAJ
Table 2 Equipment Alarms
18
ASAP
Probable Cause
No Alarms Primary
Alarms
No
Remote
Alarms
Alarms
Alarm Indication Signal NAL NAL NAL MAJ MAJ
Communications Protocol Error NAL MAJ MAJ MAJ MAJ
Connection Failed NAL MAJ MAJ MAJ MAJ
Degraded Protection Estab-
lished
NAL WAR WAR WAR WAR
Degraded Signal NAL MIN MIN MIN MIN
Loss Of Frame NAL MAJ MAJ MAJ MAJ
Loss Of Multiframe NAL MAJ MAJ MAJ MAJ
Loss Of Pointer NAL MAJ MAJ MAJ MAJ
Loss Of Signal NAL MAJ MAJ MAJ MAJ
Payload Type Mismatch NAL MAJ MAJ MAJ MAJ
Remote Defect Indication NAL NAL NAL WAR WAR
Sequence Mismatch NAL MAJ MAJ MAJ MAJ
Server Signal Failure NAL NAL MAJ MAJ NAL
Trace Identifier Mismatch NAL MAJ MAJ MAJ MAJ
Transmitter Degraded NAL WAR WAR WAR WAR
Transmitter Failure NAL MAJ MAJ MAJ MAJ
Underlying Resource Unavail-
able
NAL MAJ MAJ MAJ MAJ
Unavailable Time NAL MAJ MAJ MAJ MAJ
Unequipped NAL MAJ MAJ MAJ MAJ
frequencyOffset NAL MIN MIN MIN MIN
lossOfTimingSources NAL MIN MIN MIN MIN
Table 3 Communication Alarms
The alarms LOA (Loss of Alignment) and Sequence (Num
ber) Mismatch can not be configured via ASAP.
19
ASAP
Probable Cause
No Alarms Primary
Alarms
No
Remote
Alarms
Alarms
Connection Blocked NAL MIN MIN MIN MIN
Protection Blocked NAL MIN MIN MIN MIN
Sfwr Download Failure NAL MIN MIN MIN MIN
Sfwr Environment Problem NAL WAR WAR WAR WAR
Table 4 Processing Error Alarms
ASAP
Probable Cause
No Alarms Primary
Alarms
No
Remote
Alarms
Alarm
Battery Failure NAL MIN MIN MIN MIN
Cooling Fan Failure NAL MAJ MAJ MAJ MAJ
Fuse Failure NAL MIN MIN MIN MIN
High Temperature NAL MAJ MAJ MAJ MAJ
No RTC Synchronization NAL MIN MIN MIN MIN
Optical Connector Cover Open NAL MAJ MAJ MAJ MAJ
Pump Failure NAL MIN MIN MIN MIN
Redundant Clock Fail A NAL MIN MIN MIN MIN
Redundant Clock Fail B NAL MIN MIN MIN MIN
Redundant Matrix A Failure NAL MIN MIN MIN MIN
Redundant Matrix B Failure NAL MIN MIN MIN MIN
Unconfigured Equipment
Present
NAL WAR WAR WAR WAR
Table 5 Environmental Alarms
The following abbreviations are used in the tables:
CRI CRItical
MAJ MAJor
MIN MINor
NAL Non ALarmed
NSA Non Service Affecting
20
SA Service Affecting
WAR WARning
21
2.5 Mapping Tables: TP Names on Craft Terminal
The Termination Point (TP) names on the Craft Terminal
(CT) reflect the object model the user interface is based on.
Therefore they differ from the TP names given in the ITUT
recommendations. The following tables lists the TP names
mapping both conventions.
Craft Terminal ITUT
ElS ESTTP
OpS OSTTP
RST RSTTP
MST MSTTP
MSP MSP
Au4P AU4 CTP
Au4P/4c AU4-4c CTP
Au4P/16c AU4-16c CTP
Au4P/64c AU4-64c CTP
ModVc4 VC4 TTP
Tug3 TUG3
Tug2 TUG2
Tu3 TU3 CTP
Tu12 TU12 CTP
Table 6 SDH TPs
Craft Terminal ITUT
GMAU GMAU TTP
PTC PTC
VC4XV VC4XV TTP
VC4V VC4V TTP
Table 7 Gigabit Ethernet TPs
Craft Terminal ITUT
P PPITTP
E4 E4 CTP
P4 P4 CTP
22
Vc4 VC4 TTP
E1 E4 CTP
P12 P4 CTP
Vc12 VC12 TTP
Table 8 PDH TPs
23
3 Correlation Element Type - Event Type
The table below shows the Probable Causes for all boards
of the 1678MCC. Each board is only listed once. For exam
ple the board P4ES1 can be used within the 1670SM shelf
as well as within the 1662MC shelf, it is only listed once (see
Boards of 1670SM Shelf" below).
Equipment Alarm / Processing Error Alarm
Correlation Board Type - Probable Cause
BF CSF FF HT ICP IPL LAN NRTCS OCCO PF Q3
Boards of 1678MCC Main Shelf:
Matrix 640GBIT/S (MX640) X X X X X
Lower Order Adaptation/Matrix 40G(LAX40) X X X X X
Lower Order Adaptation/Matrix 20G(LAX20) X X X X X
FLCCONGI X X X X X
FLCSERVICE X X X X X
Power Supply/Filter (PSF) X X
Termination Bus
(BUSTERM)
X
16 x STM4/1 Port (P16S1S4) X X
16 x STM1 Port (P16S1S) X X
16 x STM16 Port (P16S16) X X
STM-64 MSA Port (S64M) X X
2 x STM-64 MSA Port (P2S64M) X X
4 x STM-64 MSA Port (P4S64M) X X
4 x STM-64 XFP Port (P2S64X) X X
2 x STM-64 XFP Port (P4S64X) X X
1678MCC Fan Unit (FAN78) X X X
16 x GE Port (P16GE) X X
Craft Terminal (CT) X
Boards of 1670SM Shelf:
Control & General I/F HC (CONGIHC) X X
Equipment Controller Card (EQUICO) X X
Matrix HI-CAP (HCMATRIX) X X
Termination Bus 1670 (BTERM)
1 x STM64 Link (MLINK)
4 x 140 Port (P4E4)
2 x 140 Adapter (A2E4)
4 x STM-1 Electrical Port (P4ES1)
24
Q3 PF OCCO NRTCS LAN IPL ICP HT FF CSF BF
4 x STM-1 Electrical (A4ES1)
High Speed Protection (HPROT)
16 x STM-1 Opt/El Port (P16S1)
16 x STM1 Electrical Access (A16ES1)
16 x High Speed Protection (HPROT16)
16 x STM-1 Optical Port Compact ( P16OS1)
12 x STM-1 Optical Access Compact (A12OS1)
4 x STM-4 Port (P4S4)
2 x STM-4 Access (A2S4)
FAN Unit for OED Shelf (FANC) X
Boards of 1662MC Shelf:
Control & General I/F HC (CONGI) X X
Compact STM-16 (SYNTH16) X X X
Termination Bus 1662 (TBUS)
63 x 2Mbit/s Port (P63E1)
63 x 2Mbit/s Port with retiming (P63E1NM4)
63 x 2 Mbit/s Prot. (75 Ohm) (A63E1-4TE)
63 x 2 Mbit/s Prot. (120 Ohm) (A63E1-120)
Low Speed Protection (LPROT)
Modules:
L64.2 MSA Optical Interface (ML642) X X X
V64.2 MSA Optical Interface (MV642) X X X
U64.2 MSA Optical Interface (MU642) X X X
Equipment Controller 1662 (EQUICO62) X X
Table 9 Equipment Alarms/Processing Error Alarms - 1
Legend of Table 9 and Table 10
BF Battery Failure
CSF Communication Subsystem Failure
FF Fuse Failure
HT High Temperature
ICP Internal Communication Problem
IPL Input Power Loss
LAN LAN failure
NRTCS No RTC Synchronization
OCCO Optical Connector Cover Open
25
PF Pump Failure
Q3 Resource Isolation
RCFA Redundant Clock Failure A
RCFB Redundant Clock Failure B
RMAF Redundant Matrix A Failure
RMBF Redundant Matrix B Failure
RUM Replaceable Unit Missing
RUP Replaceable Unit Problem
RUTM Replaceable Unit Type Mismatch
SDF Software Download Failure
SEP Software Environment Problem
TIP Timing Problem
Equipment Alarm / Processing Error Alarm
Correlation Board Type - Probable Cause
(continued)
RCFA RCFB RMAF RMBF RUM
a)
RUP RUTM
b)
SDF
c)
SEP TIP
Boards of 1678MCC Main Shelf:
Matrix 640GBIT/S (MX640) X X X X X X
Lower Order Adaptation/Matrix 40G(LAX40) X X X X
Lower Order Adaptation/Matrix 20G(LAX20) X X X X
FLCCONGI X X X X X
FLCSERVICE X X X X X
Power Supply/Filter (PSF) X X X
Termination Bus
(BUSTERM)
X X X
16 x STM4/1 Port (P16S1S4) X X X
16 x STM1 Port (P16S1S) X X X
16 x STM16 Port (P16S16) X X X
STM-64 MSA Port (S64M) X X X
2 x STM-64 MSA Port (P2S64M) X X X
4 x STM-64 MSA Port (P4S64M) X X X
4 x STM-64 XFP Port (P4S64X) X X X
26
TIP SEP SDF
c)
RUTM
b)
RUP RUM
a)
RMBF RMAF RCFB RCFA
2 x STM-64 XFP Port (P2S64X) X X X
1 x STM-64 XFP Port (S64X) X X X
1678MCC Fan Unit (FAN78) X X X
16 x GE Port (P16GE) X X X
Craft Terminal (CT)
Boards of 1670SM Shelf:
Control & General I/F HC (CONGIHC) X X X
Equipment Controller Card (EQUICO) X X X
Matrix HI-CAP (HCMATRIX) X X X X X X X X X
Termination Bus 1670 (BTERM) X X X
1 x STM64 Link (MLINK) X X X
4 x 140 Port (P4E4) X X X
2 x 140 Adapter (A2E4) X X X
4 x STM-1 Electrical Port (P4ES1) X X X
4 x STM-1 Electrical (A4ES1) X X X
High Speed Protection (HPROT) X X X
16 x STM-1 Opt/El Port (P16S1) X X X
16 x STM-1 Electrical Access (A16ES1) X X X
16 x High Speed Protection (HPROT16) X X X
16 x STM-1 Optical Port Compact ( P16OS1) X X X
12 x STM-1 Optical Access Compact (A12OS1) X X X
4 x STM-4 Port (P4S4) X X X
2 x STM-4 Access (A2S4) X X X
FAN Unit for OED Shelf (FANC) X
Boards of 1662MC Shelf:
Control & General I/F HC (CONGI) X X X
Compact STM-16 (SYNTH) X X X X X X X
Termination Bus 1662 (TBUS) X X X
63 x 2MBit/s Port (P63E1) X X X
63 x 2MBit/s Port with retiming (P63E1NM4) X X X
63 x 2MBit/s Prot. (75 OHM) (A63E1-4TE) X X X
63 x 2MBit/s Prot. (120 OHM) (A63E1-120) X X X
Low Speed Protection (LPROT) X X X
Modules:
All type of modules X X X
Table 10 Equipment Alarms/Processing Error Alarms - 2
27
Communication Alarm / Processing Error Alarm
Correlation Element Type - Probable Cause
Transmission broken
AIS LOA LOF LOM LOP LOS PLTM RDI SQM SSF TF TIM UNEQ
OSTTP X X X
ESTTP X X
RSTTP X X f)
MSTTP X X X i)
MSP X g) X X i)
AU-4 CTP X X X c) X c) X c) X c)
STM-1,
AU-3 CTP X X X c) X c) X c) X c)
STM-4,
STM-16
AU-4-4c CTP X X X c) X c) X c) X c)
STM-16
STM-64 AU-4-16c
CTP
X X X c) X c) X c) X c)
AU-4-64c
CTP
X X X c) X c) X c) X c)
modVC-4
TTP
X X X X X f) X
TU-3 CTP X X X c) X c) X c) X c)
TU-12 CTP X X X c) X c) X c) X c)
PPITTP X
E4 CTP
140MB
P4 CTP X
VC-4 TTP X X X f) X
GMAU TTP X
Gigabit
PTC X
Gigabit
Ethernet
VC-4XV TTP X X
VC-4V TTP X X X X f) X
PPITTP X
E1 CTP X X X X X
2MB
P12 CTP h ) X X X X X X
VC-12 TTP
h )
X X X f) X
Table 11 Communication Alarms - 1
Legend of Table 11 to Table 12
AIS Alarm Indication Signal
DS Degraded Signal
LOA Loss Of Alignment
LOF Loss Of Frame
LOM Loss Of Multiframe
28
LOP Loss Of Pointer
LOS Loss Of Signal
PLTM Payload Type Mismatch
RDI Remote Defect Indication
SQM Sequence (Number) Mismatch
SSF Server Signal Fail
TD Transmitter Degraded
TIM Trace Identifier Mismatch
TF Transmitter Failure
UAT FE Unavailable Time, Far End
UAT NE Unavailable Time, Near End
URU Underlying Resource Unavailable
UNEQ Unequipped
Communication Alarm / Processing Error Alarm
Correlation Element Type - Probable Cause
(continued)
Transm. broken (cont.) Transm. with errors Transm. ok
URU UAT NE
e)
UAT FE
e)
CPE DS TD
OSTTP X X
ESTTP X
RSTTP X
MSTTP X X X X
MSP
STM-1,
STM-4,
AU-4 CTP X X X c)
STM-4,
STM-16
AU-3 CTP X X X c)
STM64
AU-4-4c CTP X X X c)
modVc-4 TTP X X X
TU-3 CTP X X X c)
TU-12 CTP X X X c)
PPITTP X
E4 CTP
140MB
P4 CTP
VC-4 TTP X X X
29
GMAU TTP X
Gigabit
PTC
Gigabit
Ethernet
VC-4XV TTP
VC-4V TTP X X X
PPITTP X
E1 CTP h ) X X X
2MB
P12 CTP h ) X X X
VC-12 TTP X X X
Table 12 Communication Alarms - 2
Annotations of Table 9 to Table 12
a ) Replaceable Unit Missing" is alarmed with severity
MAJOR in case of not protected boards and with severi
ty MINOR in case of protected boards.
b ) The alarms Replaceable Unit Type Mismatch" and
Software Download Failure" occur with severity
WARNING in the context of board plugin or initializa
tion. Therefore this alarm should be seen as warning
that the board has to be exchanged in order to be taken
into operation. In that context no service is affected
(yet).
c ) Alarmed only, if POM/SUT is enabled .
d ) Alarmed only, if TTI check is enabled in the TP Config
uration dialog.
e ) Not alarmed at TP icons. Alarmed only in Alarm Sur
veillance (AS), if current data is created for perfor
mance monitoring and POM/SUT is enabled in case of
SDH TPs.
f ) Alarmed only, if TTI check is enabled in the TP Config
uration dialog.
g ) Alarmed only in alarm list, not at MSP icon in Port
View.
h ) Alarmed only, if Framed Mode is switched on. Only
PLTM is alarmed independent of Framed Mode.
i ) Alarmed only, if LOS, LOF and TIM are not disabled
in OED 1662 or 1670.
30
Quality of Service Alarm
Correlation Element Type - Counted Attributes
All quality of service alarms shown in the alarm list below
are threshold alarms.
A threshold crossing of the counted attributes is indicated
by the probable cause thresholdCrossed".
The E4 CTP and P4 CTP do not support PM and therefore
do not report any Threshold Crossing Alarms.
BBE ES SES FE BBE FE ES FE SES
RSTTP X X X
MSTTP X X X X X X
AU-4 CTP X X X X X X
AU-3 CTP X X X X X X
AU-4-4c CTP X X X X X X
modVC-4 TTP X X X X X X
TU-3 CTP X X X X X X
TU-12 CTP X X X X X X
VC-4 TTP X X X X X X
VC-4V TTP X X X X X X
VC-12 TTP X X X X X X
E1 CTP X X X
P12 CTP X X X
Table 13 Threshold Crossing Alarms
Legend of Table 13
BBE Block Bit Error
ES Errored Second
FE Far End
NE Near End
SES Severely Errored Second
31
4 Equipment Alarms/Processing Error Alarms
4.1 Battery Failure (BF)
The Battery Failure alarm situation is indicated by the
board state faulty", which implies that the equipment is
totally inoperable.
Event Type: Equipment alarm
Probable Cause: Battery Failure (BF)
Board Type: Control & General I/F HC (CONGIHC) ,
Control & General I/F (CONGI)
Condition causing indication:
Defective converter.
Effect on service:
The system is still operable and transmission is not af
fected, but the power supply system runs without redun
dancy in the respective subrack. If the second power con
verter in this subrack also fails, all traffic passing through
this subrack is affected.
Recommended action:
Replace the CONGI/ CONGIHC (. Technical Handbook)
that reports the Battery Failure . Alternatively call your lo
cal Customer Support Center for replacing the board.
32
Board Type: Power Supply/Filter (PSF)
Missing top rack unit battery voltage or defective PSF.
Effect on service:
dancy in the respective subrack. If the second PSF in this
subrack also fails, all traffic passing through this subrack
is affected.
Recommended action:
1 Check the presence of the relevant Station Power
Supply (BatteryA and BatteryB) on PSF units and
check that cable between top rack unit battery and
PSF card is plugged.
2 If the relevant Station Power Supply on the PSF
units are present and there is no cabling problem,
the PSF is defective.
Replace the PSF (. Technical Handbook) that
reports the Battery Failure. Alternatively call your
local Customer Support Center for replacing the PSF.
33
Board Type 1678MCC Fan Unit (FAN78)
Defective power connection of the the Fan Unit(e.g. connec
tion in the backpanel) or defective Fan Unit.
Effect on service:
No effect on transmission yet.
But because of the reduced FAN capacity there is the danger
of exceeding the maximum operation temperature within
the subrack. If the maximum operation temperature
exceeds, the system will overheat and therefore be
damaged.
Recommended action:
Make sure that the power connection of the Fan Unit is OK.
If the power connection of the FAN Unit is OK and the Bat
tery Failure alarm is still reported, immediately replace
the Fan Unit as quickly as possible (. Technical
Handbook).
If the problem cannot be solved, call your local Customer
Support Center for help.
34
Board Type FAN Unit for OED Shelf (FAN)
Missing connection to Top Rack Unit (TRU) or defective
FAN.
Effect on service:
No effect on transmission yet.
But because of the reduced FAN capacity there is the danger
of exceeding the maximum operation temperature within
the subrack.
Recommended action:
1 Check the cabling between TRU and FAN.
2 Check fuse of FAN at TRU.
3 If there is no cabling or fuse problem, call your local
Customer Support Center.
35
4.2 Communications Subsystem Failure (CSF)
Probable Cause: Communications Subsystem Failure
(CSF)
Board Type: Matrix 640GBIT/S (MX640),
Matrix 320GBIT/S (MX320),
LO Adaptation/Matrix 40G (LAX40),
Matrix HICAP (HCMATRIX),
Equip. Controller Card (EQUICO),
Equip. Controller 1662 (EQUICO62)
Compact STM-16 (SYNTH16)
No active controller available.
Effect on service:
- new configuration of equipment within the shelf is
not possible
- Performance Monitoring and Alarm Reporting is
suspended
- Communication within the shelf is suspended.
- Transmission not affected.
Recommended action:
- make sure that both redundant boards are plugged
- if both redundant boards are plugged, wait until one
of the controllers becomes active again. The CSF
alarm is cleared, after one of the controller is active.
36
4.3 Fuse Failure (FF)
The Fuse Failure alarm situation is indicated by the board
state faulty", which implies that the equipment is totally
inoperable.
The Fuse Failure alarm lights the red led on the card front
panel, like RUP alarm.
Probable Cause: Fuse Failure (FF)
Board Type: Power Supply/Filter (PSF)
The battery fuse of the PSF unit that reports the alarm is
broken.
Effect on service:
Recommended action:
The information about which fuse is broken inside the PSF
card, is provided by the specific problem number. The spe
cific problem indicates the SPIDER pin on which the prob
lem is detected.
Substitute the fuse of the affected PSF unit or substitute
the unit. Alternatively call your local Customer Support
Center for support.
Fuse Failure alarm cannot be raised on a PSF card, for
which top rack unit battery voltage is missing.
37
LO Adaptation/Matrix 40G(LAX40),
FLCCONGI,
FLCSERVICE,
Termination Bus (BUSTERM),
16 x STM4/1 Port (P16S1S4),
16 x STM16 Port (P16S16),
16 x STM1 Port (P16S1S),
STM64 MSA Port (S64M),
2 x STM64 MSA Port (P2S64M),
4 x STM-64 XFP Port (P4S64X),
16 x GE Port (P16GE),
8 x GE Port (P8GE),
4 x GE Port (P4GE)
The battery fuse of the board that reports the alarm is bro
ken.
Effect on service:
If the board is protected, transmission is not affected, but
there is no redundancy any more.
If the board is unprotected, transmission is affected.
Recommended action:
38
The information about the location of the affected battery
fuse (on branch of PSF A or on branch of PSF B) is provided
by the specific problem number. The specific problem indi
cates the SPIDER pin on which the problem is detected.
Substitute the fuse of the affected board or substitute the
board. Alternatively call your local Customer Support Cen
ter for support.
Fuse Failure alarm cannot be raised on a board, if battery
voltage is missing on the same branch where the fuse is bro
ken.
39
Board Type: 1678MCC Fan Unit (FAN78)
The battery fuse of the unit that reports the alarm is bro
ken.
Effect on service:
The Fan Unit does not work properly. There is the danger
of system overheat.
Recommended action:
The information about the location of the affected battery
fuse (on branch of PSF A or on branch of PSF B) is provided
by the specific problem number. The specific problem indi
cates the SPIDER pin on which the problem is detected.
Substitute the fuse of the affected unit or substitute the
unit. Alternatively call your local Customer Support Center
for support.
Fuse Failure alarm cannot be raised on a board, if battery
voltage is missing on the same branch where the fuse is bro
ken.
40
Control & General I/F (CONGI)
Defective fuse.
Effect on service:
Recommended action:
Replace the CONGI/ CONGIHC (. Technical Handbook).
Alternatively call your local Customer Support Center for
support.
41
4.4 High Temperature (HT)
Probable Cause: High Temperature (HT)
The subrack temperature exceeds the maximum operation
temperature.
- the Fan Unit is faulty.
- the air vents are covered.
The Fan Unit has three temperature sensors. The Tempera
ture High Temperature alarm is raised on a Fan Unit, if at
least one temperature sensor indicates a value greater than
the maximum temperature.
Effect on service:
No effect on transmission yet, but the Fan Unit does not
work properly. There is the danger of system over
heat.
Recommended action:
Check if the Fan Unit works properly and the air vents are
not covered.
If the air vents are not covered, but the Fan Unit does not
work properly, immediately replace the Fan Unit as
quickly as possible (. Technical Handbook).
42
Probable Cause: High Temperature (HT)
FLCCONGI,
FLCSERVICE,
16 x STM4/1 Port (P16S1S4),
16 x STM1 Port (P16S1S),
STM64 MSA Port (S64M),
16 x GE Port (P16GE),
8 x GE Port (P8GE),
4 x GE Port (P4GE)
The subrack temperature exceeds the maximum operation
temperature.
- the Fan Unit is faulty.
- the air vents are covered.
All boards have a temperature sensor. The Temperature
High Temperature alarm is raised, if the temperature sen
sor indicates a value greater than the maximum tempera
ture.
Effect on service:
No effect on transmission yet, but the Fan Unit does not
work properly. There is the danger of system overheat.
Recommended action:
43
Check if the Fan Unit works properly and the air vents are
not covered.
If the Fan Unit works properly and the air vents are not cov
ered replace the board (. Technical Handbook). Alterna
tively call your local Customer Support Center for support.
44
4.5 Internal Communication Problem (ICP)
Probable Cause: Internal Communication Problem
(ICP)
LO Adaptation/Matrix 20G (LAX20)
The ISSB connection between FLC and the matrix board
that reports the ICP alarm is lost.
Effect on service:
- If the connection to the active matrix board has been
lost, an automatic equipment protection switch has
been performed, that may cause a transmission hit
(<50ms).
- If the connection to the passive matrix board has
been lost, there is no effect on transmission, if no
second fault occurs.
In both cases matrix redundancy is not available anymore.
Recommended action:
Call your local Customer Support Center for support.
45
(ICP)
Board Type: Matrix HICAP (HCMATRIX),
Connection to the FLC in the 1678MCC main shelf is lost.
Effect on service:
- Transmission is not affected.
- Alarms are not reported anymore for the affected
subsystem (OED).
- Management operations or change of configuration
within the affected subsystem are not possible.
Recommended action:
46
(ICP)
Board Type: FLCCONGI,
FLCSERVICE
Communication between the active and passive FLC is lost.
Effect on service:
- No FLC redundancy.
- Transmission not affected.
Recommended action:
47
4.6 Input Power Loss (IPL)
Probable Cause: Input Power Loss (IPL)
Board Type: L64.2 MSA Optical Interface (ML642),
V64.2 MSA Optical Interface (MV642),
U64.2 MSA Optical Interface (MU642)
The input signal of the booster is faulty.
Effect on service:
Transmission is broken, output signal of the booster is
switched off.
Recommended action:
Check the cabling to the I/O board that provides the input
signal for the booster board.
If there is no cabling problem replace the I/O board
(. Technical Handbook) which is connected to the affected
booster board. Alternatively call your local Customer Sup
port Center for support.
48
4.7 LAN Failure (LAN)
Probable Cause: LAN Failure (LAN)
FLCSERVICE
The ISSB redundancy between the active and passive FLC
is lost.
Both FLCs generate this alarm.
Effect on service:
Traffic is not affected.
Recommended action:
Customer Support Center service personnel must be aware
that repairing the FLCFLC connection may lead to the
problem of having two active FLCs, if all interFLC cables
are lost. It is recommended to shut down the passive FLC
for any repair action on the interFLC cabling.
49
LO Adaptation/Matrix 20G (LAX20)
Failure of one of the redundant ISSB interfaces on the ma
trix board that reports the LAN failure.
Effect on service:
Traffic is not affected. No ISSB interface redundancy.
Recommended action:
Replace the matrix board which reports the LAN Failure.
Alternatively call your local Customer Support Center for
replacing the board.
50
Equip. Controller Card (EQUICO),
Equip. Controller 1662 (EQUICO62),
Failure of the ISSB interface in the backpanel. Backpanel
is defective.
Effect on service:
Recommended action:
51
4.8 No RTC Synchronization (NRTCS)
Probable Cause: No RTC Synchronization (NRTCS)
FLCSERVICE
The xntpdSupervision process, running on the active FLC
states a time source problem.
This may be due to a:
- Power Failure of the time server
- LAN communication problem to the time server
- NTP problem on the time server
Effect on service:
fected. Both FLCs change to local time selection with de
fined time drift. The time drift may influence the perfor
mance measurement accuracy.
The passive FLC does not reports the RTC alarm. In case
of an FLC switch,the alarm will not be moved to the new ac
tive FLC but still is bound to the new passive FLC.
Recommended action:
The NRTCS alarm is handled by the active NAU but not by
the standby NAU.
52
4.9 Optical Connector Cover Open (OCCO)
The Optical Connector Cover Open alarm situation is indi
cated by the board state faulty", which implies that the
equipment is totally inoperable.
Probable Cause: Optical Connector Cover Open
(OCCO)
The protection cap of the laser is pulled.
Effect on service:
Laser is automatically shut down.
Recommended action:
Fasten the laser protection cap and tighten it with the
screw.
53
4.10 Pump Failure (PF)
Probable Cause: Pump Failure (PF)
Optical booster is defective.
Effect on service:
Laser does not work.
Recommended action:
Replace the STM-64 board that supports the defect mod
ule (. Technical Handbook) or call your local Customer
Support Center for support.
54
4.11 Resource Isolation (Q3)
Probable Cause: Resource Isolation (Q3)
Board Type: Craft Terminal (CT)
Failure of the connection between the CT and the NE due
to
- defective cable connection
- failure of the QIA process
- failure of the MIB
Effect on service:
Recommended action:
1 Check the cabling between CT and NE
2 If there is no cabling problem, call your local
Customer Support Center
After a short interruption of the connection between the CT
and FLC (about 20 to 30 seconds), the CT reconnection at
tempts may be rejected by the FLC because the FLC does
not detect the interruption.
Make sure the LAN cable between the CT and FLC is inter
rupted for at least 30 seconds. The reconnection is then
handled correctly from both the CT and the FLC.
55
4.12 Redundant Clock Fail A/B (RCFA/B)
Probable Cause: Redundant Clock Fail A/B (RCFA/B)
Board Type: Matrix HICAP (HCMATRIX)
The HCMATRIX Board does not receive the redundant
clock signal.
Effect on service:
Transmission hit in some cases.
Recommended action:
Check whether only the single board or the entire system
is affected:
- if a single board is affected, replace the board or call
your local Customer Support Center for replacing the
board.
- otherwise, check the common elements of the clock
distribution hardware that provide redundant clock
signal for the affected subsystems, i.e. the MX640
boards, the LINK Board in position 21 for RCFA or
the LINK Board in position 22 for RCFB.
- occurs if the related link is disabled.
- if still no problem is detected, call your local
Customer Support Center for support.
56
Probable Cause: Redundant Clock Fail A/B (RCFA/B)
Board Type: Compact STM-16 (SYNTH16)
The SYNTH16 Board does not receive the redundant clock
signal.
Effect on service:
Transmission hit in some cases.
Recommended action:
Check whether only the single board or the entire system
is affected:
- if a single board is affected, replace the board or call
board.
57
4.13 Redundant Matrix A/B Failure (RMFA/B)
Probable Cause: Redundant Matrix A/B Failure
(RMAF/ RMBF)
Board Type: Matrix HICAP (HCMATRIX)
The board that reports the alarm does not receive a valid
signal from center stage matrix copy A/B.
If the signal of the active matrix copy has been affected, a
matrix EPS to the matrix with the good signal automatical
ly has been performed.
Effect on service:
Matrix redundancy is not available. No effect on transmis
sion, if no second fault occurs.
Recommended action:
Check the cable connections between the matrix and the
board that reports the alarm for failure.
58
Probable Cause: Redundant Matrix A/B Failure
(RMAF/ RMBF)
Matrix 160GBIT/S (MX160)
The signal between matrix and I/O board and is disturbed.
If the signal of the active matrix copy has been affected, a
matrix EPS to the matrix with the good signal automatical
ly has been performed.
Effect on service:
Matrix redundancy is not available. No effect on transmis
sion, if no second fault occurs.
Recommended action:
Call your local Customer Support Center for help.
59
4.14 Replaceable Unit Missing (RUM)
Probable Cause: Replaceable Unit Missing (RUM)
FLCSERVICE
The application processes running on the active FLC have
no contact to the remote database handler running on the
passive FLC.
This may be due to the
- application not running on the passive FLC
- passive FLC being in HALT state (no application
running)
- passive FLC having no power supply
- FLCs not being connected by LAN/Ethernet
- FLC cold start (alarm automatically disappears after
5 minutes)
Effect on service:
fected, but the FLC runs without redundancy (i.e. if active
FLC fails, the system is no longer operable).
Recommended action:
- check the LAN/Ethernet communication
- call your local Customer Support Center to reinstall
passive FLC
(. Installation and StartUp ManualFLC Software).
60
Control & General I/F (CONGI),
Power Supply/Filter (PSF)
The reasons for the alarm may be:
- the board is pulled out
- the fuse of the board is switched off
- a hardware failure of the board
Effect on service:
fected, but the power supply system in this subrack runs
without redundancy. If the second board in this partsystem
also fails, all traffic passing through this subrack will be
lost.
If a CONGI or CONGIHC reports a RUM alarm, additional
ly the LAN connection to the SC of the1678MCC main shelf
will be lost.
Recommended action:
- plug in the board
- switch on the fuse of the board
- replace the board (. Technical Handbook).
Alternatively call your local Customer Support
Center for replacing the board.
61
Board Type: Equip. Controller Card (EQUICO),
The requested element is not reachable.
Effect on service:
DCC communication is not possible for this subrack.
Recommended action:
- In case of EQUICO insert the Equipment Controller
Card correctly or replace it.
- In case of EQUICO62 insert the SYNTH16 board
correctly or replace it.
- Alternatively call your local Customer Support
Center for replacing the card.
62
Board Type: High Speed Protection (HPROT),
16 x High Speed Protection (HPROT16),
Effect on service:
Transmission is not affected unless the alarm is raised dur
ing I/O board protection switching. I/O board redundancy
is no longer available in the affected subrack.
Recommended action:
Insert the board correctly or replace it (. Technical Hand
book).
63
The reasons for the alarms are:
- the board is plugged out
- hardware failure of the matrix board (e.g. both ISSB
interfaces are defective)
Effect on service:
The board is protected automatically if the protection ma
trix board is available.
Recommended action:
- plug in the board
- replace the matrix Board. Alternatively call your
local Customer Support Center for replacing the
board.
64
Board Type: 1 x STM64 Link (S64MLINK)
The reasons for the alarms are:
- the board is plugged out
- hardware failure of the board
Effect on service:
The board is protected automatically, if the OED link is
MSP protected. If no the link is unprotected or both links
of a protection schema are defective, traffic may be aff
tected.
Recommended action:
Plug in or replace the board. Alternatively call your local
Customer Support Center for replacing the board.
65
Board Type: all protected I/O boards
Effect on service:
The board is protected automatically if protection is config
ured and enabled.
Recommended action:
book).
66
Board Type: all unprotected I/O boards,
all modules
Effect on service:
Transmission is broken.
Recommended action:
book).
67
Board Type: Termination Bus 1670 (BTERM),
Termination Bus (BUSTERM),
The requested element is not reachable. The board is not
correctly inserted or has to be replaced.
Effect on service:
Transmission is broken. No communication is possible
within this shelf.
Recommended action:
Replace the board. Alternatively call your local Customer
Support Center for replacing the board.
68
Effect on service:
Without Fan Unit the system will overheat. As a conse
quence boards will break down and transmission will be
lost.
Recommended action:
As soon as possible insert the board correctly or replace it
(. Technical Handbook). Alternatively call your local Cus
tomer Support Center for replacing the board.
69
4.15 Replaceable Unit Problem (RUP)
The Replaceable Unit Problem alarm situation is indicated
by the board state faulty", which implies that the equip
ment is totally inoperable.
Probable Cause: Replaceable Unit Problem (RUP)
FLCSERVICE
Hardware error.
This may be due to the:
- application not running on passive FLC
- passive FLC in HALT state (no application running)
- passive FLC having no power supply
- FLC cold start (alarm automatically disappears after
5 minutes)
Effect on service:
The system is still operable and transmission is not affected
but the FLC runs without redundancy (i.e. if active FLC
fails, the system is no longer operable).
Recommended action:
- call your local Customer Support Center to reinstall
the passive FLC.
70
Control & General I/F (CONGI),
Power Supply/Filter (PSF)
Board is defective.
Effect on service:
verter in this twin subrack also fails, all traffic passing
through this subrack is affected.
Recommended action:
Replace the board (. Technical Handbook). Alternatively
call your local Customer Support Center for replacing the
board.
71
Board Type: Equip. Controller Card (EQUICO),
Board is defective.
Effect on service:
Transmission is not affected. The DCC communication of
this subrack is disturbed.
Recommended action:
Replace the Equipment Controller Card or in case of the
EQUICO62 replace the SYNTH16 board. Alternatively call
board.
72
Board Type: High Speed Protection (HPROT),
16 x High Speed Protection (HPROT16),
Board is defective.
Effect on service:
Transmission is not affected unless the alarm is raised dur
ing I/O board protection switching. I/O board redundancy
is no longer available in the affected subrack.
This situation is indicated by the board state faulty".
Recommended action:
1 Reset both Matrix Boards in the subrack in which
the affected board is located.
2 In case action 1 is not successful, replace the board
(. Technical Handbook). Alternatively call your
local Customer Support Center for replacing the
board.
73
Board is defective.
Effect on service:
The previous configuration is still in service and the traffic
is not affected. A new configuration is not possible before
the fault is cleared.
Recommended action:
1 Reset the board.
2 In case action 1 is not succesful, replace the board.
74
Board Type: 1 x STM64 Link (S64MLINK)
Board is defective.
Effect on service:
Recommended action:
Replace the board (. Technical Handbook).
75
Board Type: all I/O boards,
all I/O modules
The board or module that reports the alarm is defective.
Effect on service:
Recommended action:
76
Board Type: 1678MCC Fan Unit (FAN78),
FAN Unit for OED Shelf (FAN)
The Fan Unit is defective.
Effect on service:
The Fan Unit does not work properly. There is the danger
of system overheat. As a consequence of system overheat
boards will break down and transmission will be lost.
Recommended action:
As soon as possible replace the Fan Unit (. Technical
Handbook). Alternatively call your local Customer Support
77
Board Type: Termination Bus (BUSTERM),
Termination Bus 1670 (BTERM),
Board is defective.
Effect on service:
Transmission is affected. No communication is possible
within this shelf. The board has to be replaced.
Recommended action:
Replace the Bus Termination Board. Alternatively call your
local Customer Support Center for replacing the board.
78
Board Type: OMSN Booster +10dBm (BST10),
OMSN Booster +15dBm (BST15),
10G Filter Preamplifier (PR64),
Variable Optical Attenuator (VOA)
Board is defective.
Effect on service:
The transmission passing through the board is affected.
Recommended action:
Replace the board (. Technical Handbook). Alternatively
call your local Customer Support Center for replacing the
board.
79
4.16 Replaceable Unit Type Mismatch (RUTM)
The Replaceable Unit Type Mismatch alarm situation is in
dicated by the board state faulty", which implies that the
equipment is totally inoperable.
Event Type: equipment alarm
Probable Cause: Replaceable Unit Type Mismatch
(RUTM)
Board Type: all boards except FANC,
all modules
The plugged in board or module that reports the RUTM
alarm is either of the wrong type or its version does not
match the current system configuration.
Effect on service:
It is not possible to configure this board or module.
Recommended action:
Plug in the correct board or module.
80
4.17 Software Download Failure (SDF)
Event Type: Processing error alarm
Probable Cause: Software Download Failure (SDF)
An attempt to configure the board failed due to a commu
nication overload and resulting configuration timeout or
due to erroneous configuration messages.
Effect on service:
None.
Recommended action:
1 Reset the board from the CT using menu option
Reset" from the Equipment View menu.
The board then enters the state downloading for
about 10 minutes and should change to in service
afterwards.
2 If step 1 fails and downloading is not completed after
about 10 minutes, contact your Customer Support
Center.
81
Probable Cause: Sfwr Download Failure (SDF)
Board Type: FLCCONGI
FLCSERVICE
An attempt to configure the board failed due to a commu
nication overload and resulting configuration timeout or
due to erroneous configuration messages.
Effect on service:
None.
Recommended action:
82
4.18 Software Environment Problem (SEP)
Probable Cause: Software Environment Problem
(SEP)
Board Type: FLCSERVICE,
FLCCONGI
The passive FLC runs in system recovery mode, i.e. the pas
sive FLC performs a file system recovery from the save area
(e.g. file system full, UNIX crash).
Effect on service:
Traffic is not affected, but there is no FLC redundancy
available during the recovery state.
Recommended action:
Wait until the recovery scenario has finished (this may take
some minutes). The alarm is then automatically cleared.
83
4.19 Timing Problem (TIP)
Probable Cause: Timing Problem (TIP)
- the Matrix Board receives no clock signal, or
- the Matrix Board cannot identify the frame start
indication within the selected clock signal.
Effect on service:
- transmission is interrupted
- automatic protection of the connection takes place if
enabled.
Recommended action:
Check whether the single board alone or the entire system
is affected:
- if just a single board is affected, replace it.
- otherwise, check the elements of the clock
distribution hardware that are common for the
affected subsystems, i.e. MX640 cables.
84
85
5 Communications Alarms/ Processing Error
Alarms
5.1 Abstract
All alarms are only reported on TPs where alarm reporting
is enabled. Alarm reporting on each TP can be
enabled/disabled separately.
Remark concerning Element Type:
TP names as shown on Craft Terminal (TP names accord
ing to ITUT in brackets)
86
5.2 Alarm Indication Signal (AIS)
Event Type: Communication alarm
Board Type: STM1/STM4/STM16/STM64 Board
Probable Cause: Alarm Indication Signal (AIS)
Element Type: MST (MSTTP)
Maintenance signal. There is a problem at connected SDH
equipment or at the link from connected SDH equipment
to the NE.
Effect on service:
Transmission from connected SDH equipment to the NE is
broken.
Recommended action:
Repair connected SDH equipment / link or activate a path
protection.

87
Element Type: Au4P (AU4 CTP),
Au3P (AU3 CTP).
Au4/4c (AU44c CTP),
Au4/16c (AU416c CTP),
Au4/64c (AU464c CTP)
The incoming AU4/ AU3pointer is in AISstate (Annex C,
G.783). Problem at connected SDH equipment or at the link
from connected SDH equipment to the NE.
Effect on service:
broken.
Recommended action:
protection.

88
Element Type: Tu3 (TU3 CTP),
Tu12 (TU12 CTP)
The incoming TU3/ TU12pointer is in AISstate (Annex
C, G.783). Problem at connected SDH equipment or at the
link from connected SDH equipment to the NE.
Effect on service:
broken.
Recommended action:
protection.

89
Board Type: 64 x 2Mbit/ s Board
Element Type: E1 (E1 CTP),
P12 (P12 CTP)
The incoming signal is fixed at FF" ("All-ones"). Problem
at connected PDH equipment or at the link from connected
PDH equipment to the NE.
Effect on service:
Transmission from connected PDH equipment to the NE is
broken.
Recommended action:
Repair connected PDH equipment / link or activate a path
protection.

90
5.3 Communication Protocol Error (CPE)
Probable Cause: Communication Protocol Error
(CPE)
The received values of the K1/K2 used for MSP resp. MS
SPRING violate the rules defined for the protocol (unde
fined switch requests, not supported section number).
Effect on service:
The protection (MSP resp. MSSPRING) cannot operate
properly. Neither automatic switch requests nor operator
commands will (probably) be confirmed from the remote
side. Therefore the switch cannot be completed.
Recommended action:
Check the configuration of the remote side. The remote
protection group should operate in the same way as the lo
cal one. In particular, both sides should operate bidirec
tional (dual ended) using the same protocol.
If no access to the remote group is possible, the local group
should be configured to operate unidirectional (single en
ded). In the single ended mode, the received K1/K2 is ig
nored.
91
5.4 Degraded Signal (DS)
Probable Cause: Degraded Signal (DS)
B2error rate (MSOH) higher than threshold is detected at
the incoming signal. Problem at connected SDH equipment
or at the link from connected SDH equipment to the NE.
Effect on service:
Bit errors at the received payload.
Recommended action:
Repair connected SDH equipment/ link or activate a path
protection.

92
Board Type: STM1/STM4/STM16/STM64 Board,
Gigabit Ethernet Board (GETHM)
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP),
Tu12 (TU12CTP)
with POM/SUT on
B3/BIP2error rate (POH) higher than threshold is de
tected at the incoming signal. Problem at connected SDH
equipment or at the link from connected SDH equipment
to the NE.
Effect on service:
Recommended action:
protection.

93
Gigabit Ethernet Board (GETHM),
4 x 140/STM1O/E Board
Element Type: modVC4 (VC4 TTP),
Vc4V (VC4V TTP),
Vc4 (VC4 TTP)
B3error rate (POH) higher than threshold is detected at
the incoming signal. Problem at connected SDH equipment
or at the link from connected SDH equipment to the NE.
Effect on service:
Recommended action:
protection.

94
Board Type: 2 Mbit/s Board
P12 (P12 CTP)
The bit error rate of the incoming signal exceeds 10
5

(
10
6
if CRC4 mode ON). Problem at connected PDH equipment
or at the link from connected PDH equipment to the NE.
Effect on service:
Bit errors at the transmission from the connected PDH
equipment to the NE.
Recommended action:
Repair connected PDH equipment/ link or activate a path
protection.

95
Board Type: 63 x 2Mbit/s Board
Element Type: Vc12 (VC12 TTP)
BIP2error rate or tandem connection error rate greater
than threshold is detected at the incoming signal. Problem
at connected SDH equipment or at the link from connected
SDH equipment to the NE.
Effect on service:
Recommended action:
protection.

96
5.5 Loss of Alignment (LOA)
Board Type: Gigabit Ethernet Board (GETHM)
Probable Cause: Loss of Alignment (LOA)
Element Type: PTC (PTC)
LOA alarm will be active, if the differential delay between
the fractions is too big and the vc4Virtual TTPs are without
errors (no SQM alarm, no LOM alarm, no SSF alarm).
Effect on service:
Recommended action:
None.
97
5.6 Loss of Frame (LOF)
Probable Cause: Loss of Frame (LOF)
Element Type: OpS (OSTTP),
ElS (ESTTP)
Incoming STM Frame Bytes A1.A1.A1.A2.A2.A2 of the
RSOH are wrong (not "XX.F6.F6.28.XX.XX"). Problem at
connected SDH equipment or at the link from connected
SDH equipment to NE.
Effect on service:
Transmission from connected SDH equipment to NE is
broken.
Recommended action:
protection.
According to ETS 300 417 and ITU G.783 all frame and
pointer errors have to be reported in the adaption layer
(CTP). In the information model the RSCTP is mapped
to the physical interface (ESTTP/OSTTP). Therefore the
LOF alarm is displayed:
- in the Alarm Management on the RSCTP.
- in the Transmission View/Port Details View on the
ElS/OpS.

98
Probable Cause: Loss of Frame (LOF)
P12 (P12 CTP)
The incoming frame alignment signal (FAS) is not equal to
'X001.1011'. Problem at connected PDH equipment or at
the link from connected PDH equipment to the NE.
Effect on service:
None.
Recommended action:
protection.
99
5.7 Loss of MultiFrame (LOM)
Probable Cause: Loss of MultiFrame (LOM)
Element Type: modVc4 (VC4 TTP)
The incoming Tandem Connection signal is corrupted or
the incoming POH H4 byte sequence is corrupted. The
problem relates to the connected SDH equipment or the
link from the connected SDH equipment to the NE.
Effect on service:
interrupted.
Recommended action:
Repair the connected SDH equipment/ link or activate path
protection switching.
100
Board Type: 63 x 2Mbit/sBoard
Probable Cause: Loss of MultiFrame (LOM)
P12 (P12 CTP)
The incoming 2 Mbit/s signal is not correct. The CRC4 sub
frame is missing.
Effect on service:
Transmission is not affected.
Recommended action:
Repair the connected 2 Mbit/s equipment/ link.
101
5.8 Loss of Pointer (LOP)
Probable Cause: Loss of Pointer (LOP)
Element Type: MSP (MSP)
Problem at the internal link from connected OED to
1678MCC main shelf.
Effect on service:
Transmission from connected OED shelf to 1678MCC main
shelf is broken.
Recommended action:
Repair the OED link or activate a path protection.

102
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Au4/64c (AU464c CTP)
The incoming AU4pointer is in LOPstate (Annex C,
G.783). Problem at connected SDH equipment or at the link
from connected SDH equipment to NE.
Effect on service:
broken.
Recommended action:
protection.

103
Tu12 (TU12 CTP)
The incoming TU3/ TU12pointer is in LOPstate (Annex
C, G.783). Problem at connected SDH equipment or at the
link from connected SDH equipment to NE.
Effect on service:
broken.
Recommended action:
protection.

104
5.9 Loss of Signal (LOS)
Probable Cause: Loss of Signal (LOS)
ElS (ESTTP),
MAU(GMAUTTP)
There is no incoming signal. Problem at connected SDH/
GBE equipment or at the link from connected SDH equip
ment to the NE.
Effect on service:
broken.
Recommended action:
protection.

105
Board Type: 4 x 140/STM1O/E Board,
63 x 2Mbit/s Board
Probable Cause: Loss of Signal (LOS)
Element Type: P (PPITTP)
There is no incoming signal. Problem at connected PDH
equipment or at the link from connected PDH equipment
to NE.
Effect on service:
Transmission from connected PDH equipment to NE is
broken.
Recommended action:
protection.

106
5.10 Payload Type Mismatch (PLTM)
STM1/STM4/STM16/STM64 Board,
Probable Cause: Payload Type Mismatch (PLTM)
Element Type: P4 (P4 CTP),
modVC4 (VC4 TTP)
There is a failure at the incoming C2byte (POH) which car
ries the Signal Label (SL). The SL of this NE (expected SL)
does not match the SL sent by the connected SDH equip
ment (received SL).
Effect on service:
Transmission from connected SDH equipment to this NE
is broken.
Recommended action:
Harmonize the expected Signal Label of this NE with the
transmitted Signal Label of the relevant SDHNE for this
path.

107
Element Type: Vc4XV (VC4XV TTP)
ment (received SL).
Effect on service:
Transmission in downstream direction is interrupted.
- 140Mbit/sAIS is sent to connected PDH equipment
no GBE at other end".
Recommended action:
Harmonize the expected Signal Label in the NE with the
path.

108
Board Type: 63 x 2 Mbit/s Board
Element Type: P12 (P12 CTP)
There is a failure at the incoming V5byte (POH) which car
ment (received SL).
Effect on service:
Recommended action:
Harmonize the expected Signal Label in the NE with the
path.

109
5.11 Remote Defect Indication (RDI)
Probable Cause: Remote Defect Indication (RDI)
Element Type: MST (MSTTP),
MSP (MSP)
The incoming MSOH (K2Byte) indicates a problem at the
connected SDH equipment or at the link from the con
nected SDH equipment to this NE.
Effect on service:
None.
Recommended action:
Repair the link or activate path protection switching.
Check transmission signal on Txside.

110
4 x 140/STM1O/E Board
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP)
with POM/SUT on,
modVc4 (VC4 TTP)
Bit 5 of the incoming G1 byte (POH) is 1. The problem is at
this NE or the link from this NE to the connected SDH
equipment.
Effect on service:
None.
Recommended action:
Repair the NE/ link or activate path protection switching.

111
63 x 2Mbit/s Board
Element Type: Tu12 (TU12 CTP)
with POM/SUT on,
Vc12 (VC12 TTP)
Bit 8 of the incoming V5 byte (POH) is 1. The problem is at
this NE or the link from this NE to the connected SDH
equipment.
Effect on service:
None.
Recommended action:

112
Element Type: Vc4 (VC4 TTP),
Vc4V (VC4V TTP)
Bit 5 of the incoming G1 byte is equal to 1. The problem is
at the NE or the link from the NE to the connected SDH
equipment.
Effect on service:
None.
Recommended action:
Check transmission signal on Txside.
113
Board Type: 63 x 2 Mbit/s Board
P12 (P12 CTP)
The D bit received (urgent remote alarm) was detected as
`1'. The problem is at the NE or the link from the NE to the
connected PDH equipment.
Effect on service:
None
Recommended action:
Check the relevant NE port/ link or activate a path protec
tion.

114
5.12 Sequence (Number) Mismatch (SQM)
Probable Cause: Sequence (Number) Mismatch
(SQM)
Element Type: Vc4V (VC4V TTP)
In case of mismatch between received and expected fraction
number an SQM alarm is raised.
This indicates a wrong configuration in the network.
Effect on service:
Recommended action:
Correct the pathes of the mismatching Signal fractions in
the network.
115
5.13 Server Signal Fail (SSF)
Probable Cause: Server Signal Fail (SSF)
Element Type: RST (RSTTP)
MST (MSTTP),
MSP (MSP),
modVc4 (VC4 TTP)
All lower order TPs report an SSF alarm, if a higher order
alarm is active.
Effect on service:
is broken.
Recommended action:
Repair connected SDH equipment/ link.
There is the follwing restriction regarding SSF for MST and
MSP:
Disabling of LOS, LOF and TIM in OED 1662 or 1670 also
disables SSF for MST and MSP.

116
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP),
Tu12 (TU12 CTP)
with POM/SUT
before matrix on
All lower order TPs report an SSF alarm if a higher order
alarm is active.
Effect on service:
is broken.
Recommended action:
Repair connected SDH equipment/ link.

117
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP),
Tu12 (TU12 CTP)
with POM/SUT
after matrix on
The selected matrix copy provides an AIS.
Effect on service:
is broken.
Recommended action:
Repair connected SDH equipment/ link .

118
Element Type: Vc4XV (VC4XV TTP),
Vc4V (VC4V TTP)
SSF alarm is raised if the virtual PTC indicates SSF via con
sequent actions.
A primary alarm is active on one or more of the Server TPs.
Effect on service:
The Vc4XVirtual TTP terminates the Vc4Xv trail.
Recommended action:
Perform the recommended action for the primary alarm(s).

119
63 x 2Mbit/s Board
E1 (E1 CTP),
P12 (P12 CTP),
Vc12 (VC12 TTP)
The selected timing reference is lost.
Effect on service:
is broken.
Recommended action:
Repair connected SDH equipment / link.

120
5.14 Trace Identifier Mismatch (TIM)
Probable Cause: Trace Identifier Mismatch (TIM)
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP)
with POM/SUT on
There is a failure at the incoming J1byte (POH) which car
ries the Trace Identifier (TI). The TI of this NE (expected
TI) does not match the TI of the connected SDH equipment
(received TI).
Effect on service:
No effect on transmission.
Recommended action:
Harmonize the expected TI in this NE with the transmitted
TI of the relevant SDHNE for this path.

121
Element Type: RST (RSTTP),
modVc4 (VC4 TTP)
There is a failure at the incoming J0/J1byte (SOH/POH)
which carries the Trace Identifier TI. THe TI of this NE (ex
pected TI) does not match the TI of the connected SDH
equipment (received TI).
Effect on service:
is broken.
- AIS is sent to connected SDH equipment.
- Higher order RDI is sent to connected SDH
equipment.
Recommended action:

122
63 x 2Mbit/s Board
Element Type: Tu12 (TU3 CTP)
with POM/SUT on,
Vc12 (VC12 TTP)
There is a failure at the incoming J2byte (POH) which car
ries the Trace Identifier (TI). The TI of this NE (expected
TI) does not match the TI of the connected SDH equipment
(received TI).
Effect on service:
Recommended action:

123
Vc4V (VC4V TTP)
There is a failure at the incoming J1byte which carries the
Trace Identifier (TI). The TI at this NE (expected TI) does
not match the TI of the connected SDH equipment (re
ceived TI).
Effect on service:
- 140 Mbit/sAIS is sent to connected PDH equipment
- Higher order RDI is sent to connected SDH
equipment
Recommended action:
Harmonize the expected TI in the OMSG with the trans
mitted TI of the relevant SDHNE for this path.

124
5.15 Transmitter Degraded (TD)
Probable Cause: Transmitter Degraded (TD)
Element Type: OpS (OSTTP)
Laser is degraded.
Effect on service:
Bit errors may occur.
Recommended action:
Check state of the laser on I/O board and replace the board
(. Technical Handbook).
125
5.16 Transmitter Failure (TF)
Probable Cause: Transmitter Failure (TF)
Element Type: OpS (OSTTP)
Laser has failed.
Effect on service:
Recommended action:
Replace the I/O board (. Technical Handbook).
126
5.17 Unavailable Time (UAT)
Probable Cause: Unavailable Time ( UAT)
Element Type: RST (RSTTP),
MST (MSTTP)
modVc4 (Vc4 TTP)
with Performance Monitoring
activated
Unavailable Time was detected. UAT indicates UAS.
Effect on service:
Bit errors or alarms at the transmission between connected
SDH equipment and this NE.
Recommended action:
Repair connected equipment/ link or activate path protec
tion.
127
Probable Cause: Unavailable Time (UAT)
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP),
Tu12 (TU12 CTP),
with POM/SUT enabled and
and Performance Monitoring
activated
Effect on service:
High bit errors or alarms at the transmission between this
NE and connected SDH equipment.
Recommended action:
tion.
128
Board Type: 4 x 140/STM-1O/E Board,
63 x 2Mbit/s Board
Probable Cause: Unavailable Time ( UAT)
E1 (E1 CTP),
P12 (P12 CTP),
Vc12 (VC12 TTP),
Vc4V (VC4V TTP)
with Performance Monitoring
activated
Effect on service:
Bit errors or alarms at the transmission between connected
PDH equipment and this NE.
Recommended action:
tion.
129
5.18 Underlying Resource Unavailable (URU)
4 x 140/STM1O/E Board,
63 x 2Mbit/s Board,
Probable Cause: Underlying Resource Unavailable
(URU)
ElS (ESTTP),
P (PPITTP),
MAU(GMAUTTP)
- problem with original board/module and protection
board/module (equipment protection was not
possible), or
- both matrix boards are missing or faulty.
Effect on service:
Transmission interrupted.
Recommended action:

130
5.19 Unequipped (UNEQ)
Probable Cause: Unequipped (UNEQ)
Au3P (AU3 CTP),
Au4/4c (AU44c CTP),
Tu3 (TU3 CTP),
with POM/SUT before and after
matrix enabled,
modVc4 (VC4 TTP)
ries the Signal Label (SL). The received SL is "00".
Effect on service:
For modVc4 only: Transmission from connected SDH
equipment to the NE is interrupted.
Recommended action:
Harmonize the expected SL in this NE with the transmitted
SL of the relevant connected SDH equipment for this path.

131
Board Type: STM1/STM4/STM16/STM-64 Board
with POM/SUT before and after
matrix enabled
There is a failure at the incoming V5byte (POH) which car
ries the Signal Label (SL). The received SL is "00".
Effect on service:
Recommended action:

132
Vc4V (VC4V TTP)
The incoming C2byte carries the Signal Label (SL) 0", al
though a different SL is expected.
Effect on service:
- 140Mbit/sAIS is sent to connected PDH equipment
- Higher order RDI is sent to connected SDH equipment
Recommended action:
SL of the relevant SDH equipment for this path.

133
The incoming V5byte (POH) carries the Signal Label (SL)
0", although a different SL is expected.
Effect on service:
Recommended action:

135
6 Quality of Service Alarms
FriendlyName
Counted Primitives
Port Element Type Alarm Type *)
Counted Primitives
RST (1) B1 Block Errors
MST (1) + (2) B2 Block Errors
STM1/STM4/
STM16/STM64
Au4P, Au3P,
Au44c,
Au416c,
Au464c, Tu3
(1) + (2) + (3) B3 Block Errors
ModVc4 (1) + (2) B3 Block Errors
Tu12 (1) + (2) + (3) BIP2 Block Errors
Gigabit Ethernet Vc4V (1) + (2) B3 Block Errors
140MB Vc4 (1) + (2) B3 Block Errors
E2 (1) FAW2Mbit/s or CRC4
2MB P12 (1) CRC4
Vc12 (1) + (2) BIP2 Block Errors
*) For an explanation of the alarm type see below
Table 14 Correlation of Element Type and Alarm Type with Threshold Alarms
All quality of service alarms shown in the alarm list (see
Chapter 3, Table 13 ) are threshold alarms. As a precondi
tion for reporting threshold alarms, performance monitor
ing has to be enabled for the corresponding TPs. Threshold
alarms (15min and 24h) are reported if the preset thresh
olds are exceeded.
Threshold alarms (15 min.) are automatically cleared after
one error free 15min.interval. Threshold alarms of 24h
intervals are automatically cleared after midnight or have
to be cleared by the user.
Alarm type explanation:
The alarm type is part of the Friendly Name and indicates
the assignment of the threshold to near or far end attrib
utes and to a granulatity period (15 min. or 24h).
Threshold alarms of the following types are reported in the
alarm list if performance monitoring is enabled for the cor
responding element:
136
(1) Near End
NTR15 ThReshold 15 min.
N1d threshold 24 h
(2) Far End
FTR15 ThReshold 15 min.
F1d threshold 24 h
(3) Trail Monitor
(Near and FarEnd)
TMe after Matrix (egress)
TMi before Matrix (ingress)
SUT Supervisory Unequiped
Termination
Table 15 Threshold Alarm Types
137
The different alarm types that are shown in the alarm list
and the correlated element types are listed in Table 14 .
Probable cause, condition causing indication, effect on ser
vice and recommended action of all threshold alarms corre
spond with the description given below.
All threshold alarms can be described by the following
scheme:
Event Type: Quality of service alarm
Port Type: see Table 14
Probable Cause: Threshold Crossed
Element Type: see Table 14 and Table 15
The preset threshold was exceeded.
Effect on service:
The received signal is not error free.
Recommended action:
Please check the equipment on the far end and the link be
tween far end and near end.
138

Alarms Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarms Guide

Uploaded by

Copyright:

Available Formats

3AG 24197 ABAA Edition 02

You might also like